Changes between Version 2 and Version 3 of Ticket #4739


Ignore:
Timestamp:
Sep 8, 2012, 1:35:02 AM (12 years ago)
Author:
akaginch
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4739 – Description

    v2 v3  
    11When creating Shapefile dataset without "ENCODING" option in layer creation options, the Language Driver ID of dbf file is set to LDID/87 (ISO-8859-1) now.
    22
    3 Non-zero LDID seems to be exclusively for other specified code page in some cases. For example: [[BR]]
    4 [http://hub.qgis.org/issues/4343 QGIS #4343 Shapefile, created in Qgis, encoding not recognized by Esri ArcGIS 10]
    5 [http://webhelp.esri.com/arcims/9.3/general/mergedprojects/arcxmlguide/elements/shapeworkspace.htm SHAPEWORKSPACE - ArcXML Programmer's Reference]
     3Non-zero LDID seems to be exclusive for other specified code page in some cases. For example: [[BR]]
     4[http://hub.qgis.org/issues/4343 QGIS #4343 Shapefile, created in Qgis, encoding not recognized by Esri ArcGIS 10][[BR]]
     5
     6[http://webhelp.esri.com/arcims/9.3/general/mergedprojects/arcxmlguide/elements/shapeworkspace.htm SHAPEWORKSPACE - ArcXML Programmer's Reference][[BR]]
     7
    68
    79In the first case, when the dataset that has non-zero LDID not corresponding to encoding of the table contents will be used, the user have to set correct LDID with binary editor beforehand. Otherwise the user have to set zero to LDID by saving with OpenOffice.org Calc and create cpg file with any text editor. Compared to them, it's easier to add a cpg file to the dataset created with LDID/0 as a default.