testing WIP-pyshapelib-Unicode

Bram de Greve bram.degreve at gmail.com
Thu Jan 3 02:07:30 CET 2008


Hi all,

as far as I can tell, I've implemented all "scheduled" pyshapelib
features WIP-pyshapelib-Unicode.
As far as pyshapelib is concerned, it now should fully support unicode,
both for filenames as textual content.

Can you please test this branch?  Apart from pyshapelib, it should be
identical to the trunk.

a few notes:
- when creating a new shapefile in Thuban, it now automatically will
create an UTF-8 encoded DBF file.  You will see this by an accompanying
.CPG file.  This is necessary, as the UTF-8 encoding cannot be set by
the LDID field in the DBF file itself.  ArcView should understand this
.CPG file though (they're the ones using it ;)
- all strings read from shapefiles are now passed to Thuban as unicode
strings.  But when viewing shapefiles with exotic UTF-8 content (and I
mean _exotic_ ;) things bork.  Be warned ...

Cheers,
Bramz




More information about the Thuban-devel mailing list

This site is hosted by Intevation GmbH (Datenschutzerklärung und Impressum | Privacy Policy and Imprint)