Bug report #5900

QGIS 1.8.0 windows standalone ships with GDAL version that causes new attribute data loss in Shapefiles

Added by marisn - about 7 years ago. Updated about 7 years ago.

Status:Rejected
Priority:High
Assignee:-
Category:Build/Install
Affected QGIS version:master Regression?:No
Operating System: Easy fix?:No
Pull Request or Patch supplied:No Resolution:upstream
Crashes QGIS or corrupts data:Yes Copied to github as #:15349

Description

Steps to reproduce issue on Windows:
1) Create a new Shapefile with a text attribute;
2) In "Save As" dialog leave encoding as-is = "system";
3) Add a vector feature with text attribute value "āšņļ";
4) Stop editing and save edits.

Results:
1) In layer properties, General tab under "provider specific options" encoding is set to "UTF-8" => WRONG! On my system "system" encoding equals "windows-1257";
2) In attribute table text has turned into "????" and thus content has been lost. Reopening dataset with "system" encoding doesn't help a lot.

Creating dataset with "UTF-8" encoding doesn't fix problem. (Read: encoding "system" is not the issue)

As all mentioned bug reports are closed as "fixed" or "use specific Linux installator" or "downgrade GDAL" all of which doesn't apply to Standalone installer, this is Windows packaging bug that can cause data corruption or loss and thus currently renders QGIS on Windows to be unusable for any non-latin language using user. I hope, that it will be fixed soon, as currently the last fully operational QGIS version on Windows is 1.6.0!

Probably also related to OSGeo4W #294


Related issues

Related to QGIS Application - Bug report #5508: DBF encoding and cyrillic values Closed 2012-04-26
Related to QGIS Application - Bug report #5255: Wrong codepage of shapefile Closed 2012-03-29
Related to QGIS Application - Bug report #5911: Language Driver ID in dbf file of new shapefile Closed 2012-06-30

History

#1 Updated by Alexander Bruy about 7 years ago

  • Resolution set to upstream
  • Status changed from Open to Rejected

This is not packaging bug

#2 Updated by marisn - about 7 years ago

Alexander Bruy wrote:

This is not packaging bug

Shipping QGIS package with known broken GDAL/OGR library that causes data loss is not a packaging bug?!? Then what it is?!? Sabotage?

#3 Updated by Jürgen Fischer about 7 years ago

marisn - wrote:

Alexander Bruy wrote:

This is not packaging bug

Shipping QGIS package with known broken GDAL/OGR library that causes data loss is not a packaging bug?!? Then what it is?!? Sabotage?

The packaging would have a bug, if it would introduce new bugs, that the packaged software doesn't have. As the standalone installer is based on OSGeo4W and the bug is there too (OSGeo4W #294), this strictly isn't a packaging bug.

#4 Updated by Minoru Akagi about 7 years ago

There will be a bug that LDID value of new Shapefile is set to 0x57(ANSI) regardless of selected encoding.

At present, you will be able to re-choose codepage in "provider specific options" if you set LDID of dbf file to "0" before you start editting new Shapefile. DBF file resaved with OpenOffice.org Calc has "0" in LDID field.

#5 Updated by Minoru Akagi about 7 years ago

I've created a ticket(Bug #5911).

Also available in: Atom PDF