Skip to main content
Solved

Automatic Language Change while Writing


Forum|alt.badge.img
Hi,

 

 

I have a shapefile and I am writing the output according to the according to the attributr name of the input shapefile. The input shapefile has korean language. Now, if I export the according to the attribute, language is not getting exported correctly by FME. How can we resolve this issue !!

Best answer by lenaatsafe

Hi @dewan

 

there might be two possible causes of this problem:

 

  • maybe the source data is not in UTF-8 and when you set the Shape Reader Character Encoding to UTF-8 the Reader interprets the data incorrectly
please inspect your your source data with Data Inspector, set the Shape Reader Characters Encoding to UTF-8 and confirm that the data does look OK;

 

if the data looks garbled please try to set the Reader Character encoding to <nothing> to let the Reader get the encoding information from the data (if available);

 

AND/OR

 

  • maybe your Shape Writer has an incorrect Character Encoding setting
by default, the Shape Writer Character Encoding is set to SYSTEM which means system locale default encoding - this will work if your system locale is set to Korean(Korea);

 

you might want to set the Writer Character Encoding to <nothing> to let the Writer preserve the encoding as is.

 

If these steps do not help please follow up with support@safe.com as @daleatsafe suggested above.

 

View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

7 replies

david_r
Evangelist
  • 8313 replies
  • October 19, 2015
Hi

 

 

Which character encoding(s) did you specify when creating the reader and the writer?

 

 

David

 

 

Forum|alt.badge.img
  • Author
  • 39 replies
  • October 19, 2015
Hi David.

 

No. It was default encoding. Yet, I tried using utf-8 and many others, but none of them worked. !!

david_r
Evangelist
  • 8313 replies
  • October 19, 2015
I think the most important thing is to verify that the encoding is set exactly the same way on both the reader and the writer.

 

 

UTF-8 would normally be a good bet, although I must admit I do not know anything about the korean character sets.

 

 

David

 

 

Forum|alt.badge.img
  • Author
  • 39 replies
  • October 19, 2015
I tried using utf-8 in both reader and writer, but it didn't work properly. Its not particulary about Korean d/s, I have many European d/s as well which have different languages.

 

Are there any other methods to solve the issue.

fmelizard
Contributor
Forum|alt.badge.img+17
  • Contributor
  • 3725 replies
  • October 31, 2015
@dewan -- please do follow up with support@safe.com -- this should work. We'll need the workspace and the data and ideally also your log file.

mark2atsafe
Safer
Forum|alt.badge.img+43
  • Safer
  • 2493 replies
  • November 2, 2015

What locale is the computer set up as? If the source is a Korean encoding, then I doubt telling FME it is UTF8 would help, nor would using the default encoding if you're not on a Korean system.


Forum|alt.badge.img
  • 275 replies
  • Best Answer
  • November 2, 2015
Hi @dewan

 

there might be two possible causes of this problem:

 

  • maybe the source data is not in UTF-8 and when you set the Shape Reader Character Encoding to UTF-8 the Reader interprets the data incorrectly
please inspect your your source data with Data Inspector, set the Shape Reader Characters Encoding to UTF-8 and confirm that the data does look OK;

 

if the data looks garbled please try to set the Reader Character encoding to <nothing> to let the Reader get the encoding information from the data (if available);

 

AND/OR

 

  • maybe your Shape Writer has an incorrect Character Encoding setting
by default, the Shape Writer Character Encoding is set to SYSTEM which means system locale default encoding - this will work if your system locale is set to Korean(Korea);

 

you might want to set the Writer Character Encoding to <nothing> to let the Writer preserve the encoding as is.

 

If these steps do not help please follow up with support@safe.com as @daleatsafe suggested above.

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings