Even,
Thank you for the quick reply. And it appears that using a .CPG file does
not make a difference in this. Is that correct?
Roger
On Fri, Nov 7, 2014 at 3:00 PM, Even Rouault even.roua...@spatialys.com
wrote:
Le vendredi 07 novembre 2014 23:53:09, Roger André a écrit :
Hello List,
I see. So the output will default to ISO-8859-1 - regardless of the input
.CPG - if the ENCODING flag isn't used.
On Fri, Nov 7, 2014 at 3:08 PM, Even Rouault even.roua...@spatialys.com
wrote:
Le samedi 08 novembre 2014 00:03:22, Roger André a écrit :
Even,
Thank you for the quick reply.
Le vendredi 07 novembre 2014 23:53:09, Roger André a écrit :
Hello List,
I am very curious why after installing GDAL 1.11, I now need to use the
-lco ENCODING=UTF-8 option when using ogr2ogr on any of my already UTF-8
encoded shapefiles? Failure to do so results in this error,
Warning 1:
Hello List,
I am very curious why after installing GDAL 1.11, I now need to use the
-lco ENCODING=UTF-8 option when using ogr2ogr on any of my already UTF-8
encoded shapefiles? Failure to do so results in this error,
Warning 1: One or several characters couldn't be converted correctly from
Le samedi 08 novembre 2014 00:03:22, Roger André a écrit :
Even,
Thank you for the quick reply. And it appears that using a .CPG file does
not make a difference in this. Is that correct?
You have to realize that the input and output side of ogr2ogr are completely
isolated from each
