Hi Borys,
I agree to specify the ENCODING option. LDID/87 does not have definite
meaning (depending on the environment), so avoiding to write shapefile
with the value would be nice. If the output encoding is UTF-8,
QGIS/OGR will generate cpg file that contains UTF-8. This behavior
must be ideal.
Similarly, how about specifying the ENCODING when creating new
shapefile (in createEmptyDataSource())?
Done
In QgsVectorFileWriter, how about always using SHAPE_ENCODING= ? It
will solve the problem and never make any encoding conversion failure
with current encoding listbox.
You're right,
Hi,
Thanks to all for the feedback :) I'm really not very familar with all the OGR
encoding stuff. I applied my pull request [1] to allow wider testing.
Many thanks to Minoru Akagi for two other patches. One of them is applied[2],
the second not, because my patch covers this isue too. Your
I do care a lot as is it essential for Chinese user to have a software
able to read and write utf8 and gb2312 encoding without any issue. It
seems QGis Master already mostly solved the issues I met with QGis 1.8,
but I willing to help to make QGis 2.0 better in this aspect. What is
the exact
On 04/12/2013 01:30 PM, Borys Jurgiel wrote:
Hi All,
As most of us know, QGIS 1.8 and 1.9 *in fact doesn't support Shapefiles*
with
encodings other than Latin-1. Assuming that all recent QGIS versions use GDAL
1.9, *the last usable version was 1.7.3* (at least for windows users in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 16/04/2013 06:21, Sanghee Shin ha scritto:
Dear Borys,
Most of all thanks for your efforts.
Actually that encoding issue highly affected Korean QGIS users
badly and reduced usability. I'm not a developer, however I can
help you by testing
Dear Borys,
Most of all thanks for your efforts.
Actually that encoding issue highly affected Korean QGIS users badly and
reduced usability. I'm not a developer, however I can help you by testing and
giving you test files. Also I'll share your efforts with Korean developers as
well.
Thanks
Hi All,
As most of us know, QGIS 1.8 and 1.9 *in fact doesn't support Shapefiles* with
encodings other than Latin-1. Assuming that all recent QGIS versions use GDAL
1.9, *the last usable version was 1.7.3* (at least for windows users in
Poland). Thanks to the 'ignore shapefile encoding'
Hi Borys!
Once I finish the case studies I join you and try to get some test files
from unusual encodings
werner
On Fri, Apr 12, 2013 at 1:30 PM, Borys Jurgiel li...@borysjurgiel.plwrote:
Hi All,
As most of us know, QGIS 1.8 and 1.9 *in fact doesn't support Shapefiles*
with
encodings