pyshapelib unicode saga

[Bram de Greve]

On 4/11/07, Bram de Greve <bram.degreve at gmail.com> wrote:
>
> I've made an attempt to add (partial) Unicode support to dbflib.  Partial,
> because strings still need to be encoded to a subset.  But this is of course
> how the DBF databases are designed.   The language driver ID (LDID) in the
> DBF header is used to specify this encoding.  Unfortunately there's not
> UTF-8 LDID ...
>
>
I've just found this page on the ESRI website:
http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow&d=21106
At the bottom it says ESRI can save Shapefiles in UTF-8 format if you
specify the correct dbfDefault in the registry.  If we can identify which
LDID value is used for these files, we can support those files as well.
Currently, I'm unable to create such a shapefile though ...

PS: Currently Unicode support in pyshapelib is only applied to string
values, NOT the field names!  It's just that would know.  This will of
course change in the near future. (OK, mea culpa, I just did forget about it
;)

Bramz

-- 
hi, i'm a signature viruz, plz set me as your signature and help me spread
:)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.intevation.de/pipermail/thuban-devel/attachments/20070411/85e29b0a/attachment.html