#882 closed enhancement (fixed)
Unicode support in OGR Shape/DBF
Reported by: | Owned by: | warmerdam | |
---|---|---|---|
Priority: | normal | Milestone: | 1.9.0 |
Component: | OGR_SF | Version: | unspecified |
Severity: | normal | Keywords: | Shape |
Cc: | Markus Neteler, alexbruy, gislab, Jeff McKenna |
Description (last modified by )
Attachments (1)
Change History (14)
comment:3 by , 18 years ago
(From update of attachment 296) sorry, submitted to the wrong bug number. Please delete here.
comment:5 by , 17 years ago
Description: | modified (diff) |
---|---|
Priority: | high → normal |
Severity: | major → normal |
Type: | defect → enhancement |
An RFC is under development to address this:
Adding Andrey as a cc: in case the infrormation in this report is helpful.
Reclassifying as an enhancement.
comment:6 by , 17 years ago
Description: | modified (diff) |
---|
comment:7 by , 15 years ago
The relevant RFCs are now here:
comment:8 by , 14 years ago
I propose this patch to solve this issue. It is proposed that the programmer should perform character set conversion by himself.
comment:9 by , 14 years ago
Cc: | added |
---|
comment:10 by , 13 years ago
Keywords: | Shape added |
---|---|
Milestone: | → 1.9.0 |
Summary: | Unicode support in OGR → Unicode support in OGR Shape/DBF |
I am working on incorporation of support for shapefile encoding, including some ability to override encodings when they are not specified.
comment:11 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I have made a preliminary pass implementing support for converting to UTF-8 on read, and from UTF-8 on write in trunk (r22176). Note that LDID/87 (the default) is treated as ISO8859_1 currently rather than "local encoding" which is apparently what it should be. The SHAPE_ENCODING configuration variable can be used to override the interpretation. CPG values are not used as I don't know what would appear in the CPG file. It would be nice if we could at least handle UTF-8 via CPG.
Test welcome!
comment:12 by , 13 years ago
Cc: | added |
---|
comment:13 by , 13 years ago
Description: | modified (diff) |
---|
comment:14 by , 13 years ago
Description: | modified (diff) |
---|
The CPG file is a last chance for user to set needed encoding. Because if the producer set encoding to default (LDID/87), but data is in other encoding (some local data), it's much easier to create simple CPG file, than encode whole dbf. So the CPG file should be preferable encoding on others (internal ones).