pyshapelib branch

[Bernhard Reiter]

On Wednesday 14 March 2007 01:30, Didrik Pinte wrote:
> The good way to handle this is to use the user's locale... For example,
> i'm using fr_BE at UTF-8 locales but some systems here are still
> fr_BE at ISO-8859-1 .

It depends on what input you would want to convert.
I do not know for sure, but I have a feeling that most .dbf files
will not be unicode (utf-8, utf-16 or similiar), but rather latin1 or 
similiar.

So for a dbf file, if you do not know more, I think trying to convert from
"latin1" is reasonable.

> Considering Thuban, it has an internal encoding that should be full
> utf-8 (Bernhard, correct me if i'm wrong) 

Well, string_representation.txt describes the plan to fully switch to unicode 
Python "objects" in all cases. Currently I think Thuban can run with several 
different internal encodings.

> Looking at 
> thuban/Doc/technotes/string_representation.txt and
> thuban/Thuban/__init__.py, it's not already the case.

_internal_encoding can be "unicode".

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/20070314/d495748e/attachment.bin