The codes given in the blogspot are not compilant with
http://support.esri.com/en/knowledgebase/techarticles/detail/21106
Karlis
Alexander Bruy wrote:
Try to replace 65001 with utf-8. Seems on some platforms
65001 don't work as expected
2012/3/23 Koos Hagghagg.k...@gmail.com:
Well, I have a
Am 23.03.12 09:38, schrieb Koos Hagg:
Yes I have. right now I have 1.9.0-2
I just tried to downgrade GDAL to 1.8 (in the OSGeo4W installer) but
GDAL 1.9 is a depencency for many things...
I guess I'll just wait a bit until the bugs get worked out or is there
something else I can do (aside from
Well, I have a liking to always getting the nightly builds... :)
I found this:
http://ssrebelious.blogspot.com/2012/03/qgis-and-gdal19-encoding-issue.html
a blog post which talks about this workaround:
The workaround I'm currently using is creating additional
.cpg-file, that contains the ID
Try to replace 65001 with utf-8. Seems on some platforms
65001 don't work as expected
2012/3/23 Koos Hagg hagg.k...@gmail.com:
Well, I have a liking to always getting the nightly builds... :)
I found this:
http://ssrebelious.blogspot.com/2012/03/qgis-and-gdal19-encoding-issue.html
a blog
