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

[kobahiro]

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

[Even Rouault]

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

[kobahiro]

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

[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?

[Even Rouault]

In 40692:

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

[Even Rouault]

In 40693:

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

[Even Rouault]

In 40698:

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

[Even Rouault]

In 40699:

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

[hansw]

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

[Jukka Rahkonen]

Fixes also #6447 and #4376