<br><br><div><span class="gmail_quote">On 4/11/07, <b class="gmail_sendername">Bram de Greve</b> <<a href="mailto:bram.degreve@gmail.com">bram.degreve@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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 ...
<br><br></blockquote></div><br>I've just found this page on the ESRI website: <a href="http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow&d=21106">http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow&d=21106
</a><br>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 ...
<br><br>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 ;)
<br><br>Bramz<br clear="all"><br>-- <br>hi, i'm a signature viruz, plz set me as your signature and help me spread :)