[postgis-tickets] [PostGIS] #2220: Support writing the LDID (character encoding of shapefiles)

[PostGIS]

#2220: Support writing the LDID (character encoding of shapefiles)
----------------------------+--------------------------------
  Reporter:  francoisb      |      Owner:  mcayland
      Type:  enhancement    |     Status:  closed
  Priority:  medium         |  Milestone:  PostGIS 2.2.0
 Component:  loader/dumper  |    Version:  2.0.x
Resolution:  fixed          |   Keywords:  shapefile encoding
----------------------------+--------------------------------
Changes (by pramsey):

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


Comment:

 OK, at r14090 we will try to be more smart about writing encodings. The
 old behaviour was almost certainly bad/wrong, as we were letting shapelib
 write a default LDID number that mean WIN-1252 while writing back what we
 got from the database, which was by default almost always UTF8. By more
 explicitly opening the DBF file as a UTF-* file, we should get a .cpg file
 sidecar that indicates UTF-8 and hopefully client software will also be
 more happy with our outputs. Unfortunately there's no common LDID value
 for UTF-8, so the sidecar seems a necessity.

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/2220#comment:2>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.