[Fdo-trac] [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:  closed
 Priority:  major         |    Milestone:
Component:  OGR Provider  |      Version:  3.4.0
 Severity:  3             |   Resolution:  fixed
 Keywords:                |  External ID:
--------------------------+----------------------------
Changes (by jng):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"7670" 7670]:
 {{{
 #!CommitTicketReference repository="" revision="7670"
 Replace wchar_t <-> char conversion routines in the OGR provider with
 calls to GDAL's CPLRecodeXXX family of string conversion functions
 instead. In addition, add support for a new optional "DataSourceEncoding"
 connection parameter that allows a user to declare the encoding for a data
 source where such encoding cannot be inferred by the underlying OGR
 driver. When set, this declares the encoding of the [char] side of any
 wchar_t <-> char conversion. If not set, the [char] encoding defaults to
 UTF-8.

 New unit tests have been added (with a test MapInfo tab file graciously
 provided by Geograf A/S) to verify that TAB files with unicode characters
 in property names and property values are not scrambled when connecting
 with the encoding (ISO-8859-1 for this tab file) specified up front. All
 other existing tests still pass with this change.

 Special thanks to Hans Milling of Geograf A/S for testing, review of these
 changes and providing the test data to add to the ever growing test suite
 for the OGR provider.

 Fixes #455
 Fixes #66
 }}}

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