JFYI
GRASS is also hit hard by recent GDAL/OGR ESRI Shapefile encoding
saga. Importing ESRI Shapefile with non-latin text most likely will
corrupt Your text.
Symptoms - even when setting correct encoding for wxgui in
preferences, non-latin letters are shown grabbled and doubled (two
garbage symbols instead of a single letter).
Solution - create a .cpg file and pray or downgrade GDAL/OGR on
pre-1.9.0 version (not an option for WinGRASS users).
Note - if Your data are corrupted during import with v.in.ogr, there's
no easy way how to correct it.*
* find/replace in LO Calc might do the trick for DBF file.
This sounds a like a truly horrible problem.
Thanks for raising awareness of this.
Are there any other sources on the web where
it would be possible to get more information
about this?
Have you tried downgrading only the Shapefile
drivers in the GDAL 1.9.x release?
Best,
Ben
On 02/15/2013 05:01 PM, Maris Nartiss wrote:
JFYI
GRASS is also hit hard by recent GDAL/OGR ESRI Shapefile encoding
saga. Importing ESRI Shapefile with non-latin text most likely will
corrupt Your text.
Symptoms - even when setting correct encoding for wxgui in
preferences, non-latin letters are shown grabbled and doubled (two
garbage symbols instead of a single letter).
Solution - create a .cpg file and pray or downgrade GDAL/OGR on
pre-1.9.0 version (not an option for WinGRASS users).
Note - if Your data are corrupted during import with v.in.ogr, there's
no easy way how to correct it.*
* find/replace in LO Calc might do the trick for DBF file.
JFYI
GRASS is also hit hard by recent GDAL/OGR ESRI Shapefile encoding
saga. Importing ESRI Shapefile with non-latin text most likely will
corrupt Your text.
take a look on new parameter 'encoding' in `v.in.ogr` [1]. This could help.