testing WIP-pyshapelib-Unicode

[Bernhard Reiter]

On Thursday 03 January 2008 02:07, Bram de Greve wrote:
> - 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 ;)

I wonder what should be the default.
Is it possible to switch to old behaviour?
Are ut-8 dbf files standard with shapefiles now?

> - 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 ...

What does "bork" mean in this context?
We probably should take at least a little effort to not make Thuban break 
completely when it encounters strange stuff, so where is the problem coming 
from?

Bernhard

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20080103/5f13e7ea/attachment.bin