WIP-pyshapelib-Unicode issues

[Bernhard Reiter]

On Wednesday 09 January 2008 20:33, Bram de Greve wrote:
> TERMINOLOGY ISSUE.  I've been using the term code page for whatever the
> DBF file thinks is the code page.  That's either an LDID constant or the
> content of the .cpg file.

Maybe I do not know enough about how this all works.
I am only trying to help you by asking questions and suggesting general 
things. 

My conception is that there are .dbf files (or group of files within a 
"shapefile") that we do not know the encoding of.
For them we need the selection button, 
because Thuban cannot determine the encoding by itself.

As for the default of what to create, I think we make it a logic
coming out of the current language from the locale and what is most commonly 
created by other up-todate .shp and .dbf tools.
The user should be able to override the default by setting a variable
in thubanstart.py, I agree.

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/20080110/f89d532a/attachment.bin