Re: [gdal-dev] Usage of GDAL_FILENAME_IS_UTF8 config option

2017-01-13 Thread Ray Gardener
Just to add a small note regarding OS X (and iOS) and UTF-8 filenames: The HFS+ filesystem stores accented characters in decomposed form, which can differ from the filename given to an API that creates the file such as fopen(..., "wb"). Applications that store a filename (e.g. into a preferenc

Re: [gdal-dev] Usage of GDAL_FILENAME_IS_UTF8 config option

2017-01-09 Thread Damian Dixon
Hi Victor, If you set GDAL_FILENAME_IS_UTF8 to YES then you need to pass in filenames and paths encoded as UTF8. This means that on Windows you will need to do additional work to convert from MBCS or UTF16/UCS2 to UTF8. If your application is built as MBCS then what you essentially have is a mul

[gdal-dev] Usage of GDAL_FILENAME_IS_UTF8 config option

2017-01-09 Thread Poughon Victor
Hi, We are using GDAL in OTB and recently we had a bug report about opening non ASCII filenames on Windows 10 [0]. They suggest a fix using: > CPLSetConfigOption("GDAL_FILENAME_IS_UTF8","NO"); The test case is GDALOpen() on a file named 你好.tif, which I confirmed works fine on Linux, but not on W