Jump to content
Sign in to follow this  
hariasa

Viewing and editing non-unicode in ArcGIS

Recommended Posts

I have a shapefile with Chinese characters in it. When I edit the shapefile and put an english translation, the chinese characters dissappear because of the encoding my system uses. 

 

I could change the system locale, but this is to me a last resort. Is there a way to force ArcGIS to read things in a certain encoding? (for example messing with the DBF header?)

 

QGIS demonstrates how it is done; it just accepts CPG files.

 

Thanks!

  • Like 1

Share this post


Link to post
Share on other sites

I had a similar experience once. My odesk client wanted to do something out of a Hebrew shape file. Try these,

 

- add Chinese as secondary system language at your os. This will add a language changer app to the status bar. Use google translate to do the rest.

- there is another technique to change attribute table character encoding format I forgot. -_-   

Share this post


Link to post
Share on other sites

This solution does not work. I have added the registry key with the Chinese Simplified codepage (936), and when saving the shapefile after editing all chinese characters revert to gobbledygook.

 

 

I had a similar experience once. My odesk client wanted to do something out of a Hebrew shape file. Try these,

 

- add Chinese as secondary system language at your os. This will add a language changer app to the status bar. Use google translate to do the rest.

- there is another technique to change attribute table character encoding format I forgot. -_-   

 

Step 1: Did not work for me, same issues as above, all characters after editing revert to nonsense. 

 

Step 2: Sounds interesting! Hopefully it will get back to you because this issue is really annoying. Why doesn't ArcGIS simply accept CPG files???

 

Thanks for helping though, if you or anyone else has more ideas, let me know :)

 

P.S.: by the way, to translate a DBF from a shapefile more efficiently, open in OpenOffice, select appropriate Codepage, Save as XLS format, upload to Google Documents, make a new column in Google spreadsheets, apply a formula such as =GoogleTranslate(<cell-to-be-translated>,"de","en") and drag down, download as XLS format, save as DBF format replacing your existing DBF file. Note that the column name should be of the same format as the other column names or it won't work! (Do this with open office because Excel does not allow codepages to be set). Long procedure, but if you have like 50.000 entries it's much faster than translating every single one of them manually...

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.