Problem with Korean

PStadler · Post by **PStadler** » Sun Apr 15, 2007 5:16 pm

Hello,
Currently I have translations in 17 languages.

I have all my translations in an
Excel-File. When I import this file, although I have defined the right charsets,
Sileditor always proposes some wrong Charsets, for example for Greek
I define GREEK_CHARSET, but Sileditor proposes DEFAULT_CHARSET.
For most languages everything is fine if I correct the Sileditor proposals,
and they are shown ok in Sileditor. Also Chinese, Japanese and Arabic.
But not for Korean.

I defined
HANGEUL_CHARSET in the Excel-File, Sileditor proposes DEFAULT_CHARSET, I correct to
HANGEUL_CHARSET, but in Sileditor then are shown garbage signs.

In my Excel-File the Korean is perfectly visible. So what can be the reason?

Sincerely Peter Stadler

Post by **isiticov** » Mon Apr 16, 2007 2:11 am

Hello,

Do you have defined settings for Korean under Default Fonts (menu Tools | Default Fonts) as well?

PStadler · Post by **PStadler** » Mon Apr 16, 2007 5:49 am

Hello,
I have changed the default fonts. Now in Sileditor everything is ok.

But if i load the sil-Projektfile in TsilangExpert, the Korean chars are still garbage.

Sincerely
Peter

Post by **isiticov** » Mon Apr 16, 2007 6:40 am

Do you have the settings under Fonts and Charsets for Korean?

PStadler · Post by **PStadler** » Tue Apr 17, 2007 5:59 am

Hello,

In Sileditor Korean Defaultfont is set to Times New Roman and HANGEUL_CHARSET. If I load the projectfile (*.sil) in TsilExpert, then
again all Korean chars are garbage. So what is the problem?

Sincerely Peter

Post by **isiticov** » Tue Apr 17, 2007 6:22 am

Where do you see the garbage characters? Inside Translation Editor or when running your application? If you see the garbage inside Translation Editor then please go to Fonts section in Translation Editor (please see left-side tree-view) and setup font for Korean and the same with Charsets section to setup Charset for Korean. Also please note: I would recommend to use Tahoma font instead of Times New Roman.

PStadler · Post by **PStadler** » Wed Apr 18, 2007 6:04 am

Hello,

Finally I found the reason, why Korean not worked. In my translation database I had written HANGUEL_CHARSET instead of HANGEUL_CHARSET.
So now everything works fine, also with Korean language.

Sincerely

Peter