FAQ: How does ArcPad read and write Shapefiles/DBF files encoded in various code pages?
How does ArcPad read and write Shapefiles/DBF files encoded in various code pages?
ArcPad searches various places to determine the code page to use when reading and writing attributes and displaying labels for a particular shapefile. The decision is made when loading the Shapefile.
ArcPad prioritizes the code pages as follows:
Special Note: In versions 6.0, 6.0.1, and 6.0.2, priorities 1 and 2 below are reversed. That is the LDID has the highest priority, while with version 6.0.3, the .CPG file has the highest priority.
1. ArcPad views the Shapefile's .CPG file. The code page identified in the .CPG file is used. The .CPG file has the same file name as the Shapefile, but uses a .CPG extension, for example:
2. If the Shapefile does not contain a .CPG file, ArcPad checks if the Shapefile's DBF table contains a valid Language Driver ID (LDID) value in its header. If so, the corresponding code page is used. If the LDID value is 0x57, ArcPad uses the ANSI code page associated with the locale set in the Locale page of the ArcPad Options dialog box, for example:
3. If the LDID value is 0 or not valid, ArcPad uses the code page specified in the Shapefile's APL file (the codepage attribute of the LOCALE element). For example:
4. If no code page is specified in the Shapefile's APL file, ArcPad defaults to the code page associated with the locale set in the Locale page of the ArcPad Options dialog box; for example: