[postgis-devel] [PostGIS] #467: shp2pgsql: command line option to cope with broken strings in dbf files

[PostGIS]

#467: shp2pgsql: command line option to cope with broken strings in dbf files
----------------------+-----------------------------------------------------
  Reporter:  agnat    |       Owner:  strk         
      Type:  patch    |      Status:  assigned     
  Priority:  medium   |   Milestone:  PostGIS 1.5.2
 Component:  postgis  |     Version:  1.5.X        
Resolution:           |    Keywords:  shp2pgsql    
----------------------+-----------------------------------------------------
Comment (by agnat):

 patch3 does not expose iconvs transliterate option on the command line
 anymore. First i thought it's a good idea to expose all error policies for
 maximum flexibility. However, on a second thought I can not come up with a
 real use-case for the transliterate policy. That's because the target
 format is always utf-8 and there really is no need to transliterate to
 utf-8.

 If anybody has a use-case that requires transliteration we can easily add
 this option back.

 Although strk already fixed things for broken utf-8 input this patch is
 still useful when dealing with non utf-8 data. For example the
 [http://www.gadm.org gadm shapefiles] contain garbled strings in windows-
 1252 encoding. To import these files and just ignore characters that don't
 have a utf-8 representation set the -C option.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/467#comment:3>
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.