Document UTF-8 versus Windows-1252 encoding change on site

[nvkelso]

http://support.esri.com/en/knowledgebase/techarticles/detail/21106

http://earth-info.nga.mil/gns/html/gns_services.html

[mbostock]

Funny, I was just going to ask you about this because I can't figure out how to read GeoDB files using ogr2ogr. I can read UTF-8 encoded shapefiles just fine, though, using ogr2ogr -lco ENCODING=UTF-8. Are you planning on switching to UTF-8 for 2.1? Because that would be welcome!

[nvkelso]

Yes, UTF-8 for the 3.x series. Normally adm-1 changes would get a 0.x
increment in Natural Earth but the data model is changing a little (making
it more standard field names with rest of project) and the character
encoding will break things for some people. It's surmountable, but going
UTF-8 can cause as many problems as it fixes.

_n

On Thu, Mar 7, 2013 at 2:54 PM, Mike Bostock notifications@git.luolix.topwrote:

Funny, I was just going to ask you about this because I can't figure out
how to read GeoDB files using ogr2ogr. I can read UTF-8 encoded shapefiles
just fine, though, using ogr2ogr -lco ENCODING=UTF-8. Are you planning on
switching to UTF-8 for 2.1? Because that would be welcome!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/89#issuecomment-14591851
.

[nvkelso]

Published at http://www.naturalearthdata.com/features/.

[nvkelso]

See also: http://www.naturalearthdata.com/corrections/admin/admin_ticket.php?track=4RUN1M5S75&Refresh=70330