[fdo-users] RE: FDO OGR 3.6+3.7 and UTF-8 problem

[Hans Milling]

I agree, FOD should always output strings in UTF-8 format as this is somewhat
standard these days.
If detecting the format of the data source is not possible I think that this
should be an option on the FDO provider to set. Then in Maestro or the like
where the FDO provider is used, the option could look something like this:
http://osgeo-org.1803224.n2.nabble.com/file/n7167171/DataSource.gif 

However Mapinfo files has the information needed to detect this in the .TAB
file. In my case the tab file states:
Type NATIVE Charset "WindowsLatin1"

The OGR provider should detect this and read the strings correctly
(converting them to UTF-8 on the go)
Mapinfo files does not support UTF-8 format at all. It only supports the
following character encodings according to the internal help:
http://www.kxcad.net/MapInfo/MapInfo_Professional/MapInfow-28-33.html
The best solution would be for the code itself to detect the encoding from
the .TAB file. E.g. if you have an OGR Datasource in MGOS that just points
to a folder, the different files could have different encodings, then an
option to set the encoding would not work properly.

Best regards Hans Milling...


--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/FDO-OGR-3-6-3-7-and-UTF-8-problem-tp7158330p7167171.html
Sent from the FDO Users mailing list archive at Nabble.com.