-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
non-ASCII character corruption in shapefile #15614
Comments
Author Name: Leyan Ouyang (Leyan Ouyang) Everything seems to work much better if I choose the option "Ignore shapefile encoding". What does this new option do exactly ? |
Author Name: Leyan Ouyang (Leyan Ouyang) This is the option "Ignore shapefile encoding" I mentioned in the first comment, and it does seem to solve the issue. However, the bug is not fixed in my opinion as the default setting will lead to loss of data. This option should be checked by default while the issues with GDAL are not sorted out. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Borys Jurgiel (@borysiasty) Fixed in 4fb9879
|
…precision and width so as to make QgsVectorLayerEditBuffer::commitChanges() API Fixes qgis#15614
Author Name: Leyan Ouyang (Leyan Ouyang)
Original Redmine Issue: 6327
Affected QGIS version: master
The non-ASCII characters seem to be corrupted on a new shapefile. Steps to reproduce:
The text of the attribute is replaced by "??"
This does not happen when loading an existing UTF8 shapefile, it can even be modified and saved. "Save as", however, is also affected.
I use QGis master and latest GDAL build from SVN. I am using ArchLinux with a en_US.UTF-8 locale.
I am aware of the previous issues between QGIS and GDAL, but Alexander Bruy told me they were mostly solved now and this problem looks different, hence this new bug report.
The text was updated successfully, but these errors were encountered: