Opened 7 weeks ago

Closed 6 days ago

Last modified 2 days ago

#7065 closed defect (fixed)

Issue on Windows with non-ASCII characters and command line utilities

Reported by: kobahiro Owned by: warmerdam
Priority: normal Milestone: 2.3.0
Component: Utilities Version: unspecified
Severity: normal Keywords:
Cc:

Description

gdaladdo can create pyramid with 1-byte file name gdaladdo can not create pyramid with 2-byte file name

Attachments (1)

GDAL_05.gif (32.0 KB) - added by kobahiro 7 weeks ago.

Download all attachments as: .zip

Change History (10)

Changed 7 weeks ago by kobahiro

Attachment: GDAL_05.gif added

comment:1 Changed 7 weeks ago by Even Rouault

Summary: gdaladdo does not create pyramid if file name includes 2-byte charactersIssue on Windows with non-ASCII characters and command line utilities

This is probably an issue with the code page of your Windows terminal.

You might try to add "--config GDAL_FILENAME_IS_UTF8 NO" to your command line, to specify that the filename is in the current code page of your terminal

Alternatively you could try to modify the code page of your terminal to be UTF-8

comment:2 Changed 7 weeks ago by kobahiro

Thank you Rouault. I could create pyramid (overlay) with "--config GDAL_FILENAME_IS_UTF8 NO" Thanks again!

comment:3 Changed 8 days ago by hansw

I will leave my comment here, as my ticket 7142 was closed with a referral to this ticket.

My issue could not be solved using the "GDAL_FILENAME_IS_UTF8" parameter. This option only refers to path parameters and not to the rest of the command line values. Non ASCII characters (not uncommon in most languages) can occur in every feature source name, layer name and attribute name.

This seems quite an issue for quite a share of command line users under Windows.

Maybe this comment about the Unicode Windows API helps?

comment:4 Changed 6 days ago by Even Rouault

In 40692:

netCDF: support UTF-8 filenames on Windows (refs #7065)

comment:5 Changed 6 days ago by Even Rouault

Resolution: fixed
Status: newclosed

In 40693:

Command line utilities: use Unicode main on Windows to avoid issues with non-ASCII characters (fixes #7065, fixes #7142)

comment:6 Changed 6 days ago by Even Rouault

Component: defaultUtilities
Milestone: 2.3.0

comment:7 Changed 4 days ago by Even Rouault

In 40698:

Command line utilities: really use unicode main with MSVC (refs #7065)

comment:8 Changed 4 days ago by Even Rouault

In 40699:

Fix previous commit on non-Windows builds (refs #7065)

comment:9 in reply to:  8 Changed 2 days ago by hansw

@Even Rouault Thanks you very much for the changes! In my case 7142 special characters are working now.

Note: See TracTickets for help on using tickets.