[fdo-trac] #455: OGR Provider: Investigate switching string conversion functions to always assume UTF-8 enocded strings

[FDO]

#455: OGR Provider: Investigate switching string conversion functions to always
assume UTF-8  enocded strings
----------------------------+-----------------------------------------------
   Reporter:  traianstanev  |       Owner:  traianstanev
       Type:  defect        |      Status:  new         
   Priority:  major         |   Milestone:              
  Component:  OGR Provider  |     Version:  3.4.0       
   Severity:  3             |    Keywords:              
External_id:                |  
----------------------------+-----------------------------------------------
 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.

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/455>
FDO <http://fdo.osgeo.org/>
Feature Data Objects