[postgis-users] pgsql2shp dbf file encoding

[Paul Ramsey]

And that DBF field dates from the Time Before UTF-8, so there won't be
a "UTF8" number to put in it, in any event.  DBF files with UTF in
them (OSM!) are scary scary scary (for example, should your code for
reading a CHAR(8) field in DBF expect 8 bytes, or 8 characters? yay!)
It would be nice to support transcoding down to the code pages that
*are* supported in that field, I suppose. I wonder how much software
actually supports it.

P.

On Mon, Oct 25, 2010 at 9:57 AM, Mark Cave-Ayland
<mark.cave-ayland at siriusit.co.uk> wrote:
> Denis Rykov wrote:
>
>> I don't quite understand why pgsql2shp is writing this encoding to our
>> shapes, our database is in UTF-8 and we never use win1252
>
> Well pgsql2shp has never contained any code to set the encoding field
> (mainly because until recently the version of shapelib included with PostGIS
> didn't support the encoding field), so I guess WIN1252 must be the shapelib
> default.
>
>
> ATB,
>
> Mark.
>
> --
> Mark Cave-Ayland - Senior Technical Architect
> PostgreSQL - PostGIS
> Sirius Corporation plc - control through freedom
> http://www.siriusit.co.uk
> t: +44 870 608 0063
>
> Sirius Labs: http://www.siriusit.co.uk/labs
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>