Opened 12 years ago
Last modified 12 years ago
#4739 closed enhancement
Is LDID/87 appropriate as default encoding of the Shapefile driver dataset creation? — at Initial Version
| Reported by: | akaginch | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | OGR_SF | Version: | unspecified |
| Severity: | normal | Keywords: | Shapefile, Language Driver ID |
| Cc: |
Description
When 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.
Non-zero LDID seems to be exclusively for other specified code page in some cases. For example:
QGIS #4343 Shapefile, created in Qgis, encoding not recognized by Esri ArcGIS 10
SHAPEWORKSPACE - ArcXML Programmer's Reference
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.
Therefore, I think that LDID/0 will be more appropriate than LDID/87 as a default.
