OGR Provider: Investigate switching string conversion functions to always assume UTF-8 enocded strings
|Reported by:||traianstanev||Owned by:||traianstanev|
The OGR provider is currently using locale-dependent string conversion routines to go from OGR (char*) to FDO (wchar_t*). This task is to check if it makes sense to switch the code to always assume OGR strings are UTF8 and use UTF8->UTF16/32 conversion when exposing OGR strings via the FDO provider. The current code produces incorrect results when the provider is used against PostGIS for example, but some other sources (like SHP) could produce wrong results if we assume UTF8 encoding. However, reading SHP with the OGR provider is not a priority, since there is the dedicated SHP provider.