hangul conversion

[dolphyo]

Hello, at present I''m running OpenOffice.org 1.1.4 Dutch version. It is absolutely unclear to me how the Hangul/Hanja conversion function works. It simply doesn't. However much I push the converison button, Korean script is not accepted, neither when typing it, nor after copy and paste from an external source. Nor is there any mentioning of it in the Help pages. Is this a bug, or am I doing something wrong, or do I need to download anything?


Regards,

dolphyo

[Robert Tucker]

If OpenOffice is not displaying Korean fonts, it may be helpful if you state which system you are using (Microsoft, Mac or Linux) and which distribution in the case of Linux, what fonts you have installed and if any other applications you have can work with these fonts.

[dolphyo]

I'm running Windows XP. I'm having a long list of fonts installed, but usually my hangul is in Times New Roman. My CJK program is NJ Star.

[cwchia]

Why not try out the OOo Korean Language page at:

http://ko.openoffice.org/

Good luck and have fun.

[Robert Tucker]

Hopefully you have obtain the information you require on the Korean pages (I currently use Debian Linux and my use of non-Roman fonts usually stops at Cyrillic if not Modern Greek).

It's still not clear to me if you are actually getting Korean fonts to display, let alone convert from Hangul to Hanja.

Besides references to 'i18n' and 'grid display systems' I came across:


NJStar Communicator 2.30

You may need to force Unicode output to type CJK in applications like AbiWord or OpenOffice.org. Click on the rightmost button on the input bar and change the default output code to Unicode:

at: http://zsigri.tripod.com/fontboard/cjk/uniapps.html


Possibly someone using Korean fonts and the conversion facility will know exactly what the problem you have encountered is. As an outsider, it looks as if there may be a number of pitfalls.

[dolphyo]

thanks for trying to help me out, but that's one of the usual solutions I would try first, and indeed, it didn't work out. I'm running NJStar Communicator 2.51, btw, sorry for not being complete. Yet, as it seems from other postings, the problem is a more general problem to 1.1.4. It did not exist in 1.1.2, I'm quite sure. The solution of turning to Korean version is interesting, but then again, I may expect any version I download to function according to standards, wouldn't it be? I do hope the issue gets resolved, or maybe someone does come up with a solution. In the meantime I'll have to stick with good old Microsoft for writing Korean text. Hope it gets resolved.

[multi-lingual_ooo]