Issue 19822 - pre-1933 orthography Korean support with U+1100 Hangul Jamos and opentype fonts for Korean
Summary: pre-1933 orthography Korean support with U+1100 Hangul Jamos and opentype fon...
Alias: None
Product: Internationalization
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC4
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2003-09-20 01:18 UTC by shinjs
Modified: 2013-08-07 15:00 UTC (History)
2 users (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description shinjs 2003-09-20 01:18:25 UTC
Korean Hangul is a complex script that requires rendering with opentype fonts
and caret movement based on syllables. 

MS Office XP has a full support of over 1.5 million Hangul syllables made up of
sequences of Hangul Jamos (in U+1100, )

Mozilla can render all those HAngul syllables as well
( , ,

There's a patch to Pango for this ( ,

Now that we have a free opentype font 
  (, openoffice has to support 
Korean (supporting only pre-composed syllable can hardly be regarded as full
Korean support). Perhaps, an easy way to do that is to port my patches for
Mozilla and Pango to ICU layout engine because I heard that openoffice already
makes use of ICU layout engine to support Indic scripts.
Comment 1 Dieter.Loeschky 2003-09-29 11:50:17 UTC
DL->HDU: Would you please takeover?
Comment 2 2003-09-29 15:25:58 UTC
The first task is to enable OpenType processing for Hangul Jamo. This
fix is easy, I could easily put it into OOo 1.1.1 or SO7pp1.

The problem with a 1.1.1 target would be, that the fix mentioned above
would only work on XP, but not yet for our unix platforms, because the
OOo 1.1.x version will still have ICU 2.2, which does not do process
OpenType for Hangul scripts.

For OOo 2.0 we will use ICU >= 2.6, which does Hangul OpenType
processing. Could you assess if the quality of ICU's 2.6 layout engine
is sufficient to properly layout complex Hangul?

Is the OOo 2.0 target ok for you, or is this target too late? If not,
I could apply the fix mentioned at the top of this comment which would
fix the behaviour on XP immediately. For the unix platforms we could
submit a followup issuezilla task to implement or backport Hangul
OpenType processing to ICU's 2.2 layout engine. Since you are the
expert in this field I'd love if you volunteered for it. What do you
Comment 3 shinjs 2003-09-30 16:27:04 UTC
Thank you for your kind explanation. However, I'm afraid I'm at loss
because as far as I can tell, even the CVS trunk of ICU layout engine
doesn't support (pre-1933 orthography) Hangul rendering with Hangul
Opentype fonts. ICU's layout/LETypes.h has three enum values for
'ljmo', 'vjmo', and 'tjmo' defined, but that's about it. The cvs log
doesn't have any trace of it, either. That's why I filed ICU bug 3274
( If I'm
mistaken about Hangul opentype support in ICU 2.6 or later, I'd be
glad to stand corrected. 

As for Hangul opentype support on Windows XP (with the latest
Uniscribe) or Win2k(with MS IE 6 that comes along with the latest
Uniscribe), it's not perfect but acceptable. With some
'pre-processing' added
(, it'd be better
(i.e OpenOffice can support Hangul better than MS Office XP).

As for 2.0 target, I think it's reasonable given that ICU doesn't yet
support Hangul rendering with ljmo/vjmo/tjmo GSUB features (assuming I
am not missing anything). 
Comment 4 2003-09-30 17:08:16 UTC
I see now that just an upgrade to a new ICU version is not sufficient,
thank you.

Do you agree that the next step would be to implement the required
Hangul processing in ICU? Once this is done we just need to enable
complex layout processing for Hangul Jamo in
vcl/source/gdi/outdev3.cxx's OuputDevice::ImplLayout(...) method:
  if( ((*pStr >= 0x0590) && (*pStr < 0x10A0))
+ ||  ((*pStr >= 0x1100) && (*pStr < 0x1200))   // hangul jamo
  ||  ((*pStr >= 0x1700) && (*pStr < 0x1900))

In the meantime I'm assigning this issue back to you for the work on
ICU's HangulLayoutEngine. Thank you very much for volunteering. When
it is done please reassign this issue back to me, so we can integrate
it all into OOo.
Comment 5 shinjs 2003-10-01 06:34:28 UTC
Yes, I agree that the pre-requisite to fixing this bug is to add
Hangul opentype support to ICU's layout engine. Because I'm not
familar with ICU's LE, I need some initial help about its overall
structure and inner working to take off.  I sent Eric Mader  an email
about the issue  in addition to filing a bug at Jitterbug and am
hoping to hear back from him soon. Once I'm done with Hangul OT
support in ICU LE (which could take pretty long), I'll let you know
and assign this bug back to you.

Comment 6 shinjs 2003-11-09 13:29:18 UTC
taking. I'm still waiting for a reply from Eric Mader. Perhaps, I have 
to write to him once more.
Comment 7 2003-11-11 16:35:26 UTC
Pointer issue 14640: Adding Hangul Jamo to scripts needing CTL processing.
Comment 8 thorsten.ziehm 2004-09-02 15:50:30 UTC
Due to missing resources, this task has to be set the target 'OOo later'.
If we do not get any responce in the next 4 weeks, we will close this enhancement.
Comment 9 fllotsaam2 2004-09-03 16:07:49 UTC
I would like to see work on this issue done.  Not having good hangul font
rendering and importation of Hangul Office files make Openoffice much not a
possiblity when dealing with documents written in Hangul.  It like having not
being able to import doc files here.  Yes they are two diffrent issues but they
work togeather to form a major block on use here.
Comment 10 shinjs 2004-09-03 17:31:19 UTC
Thanks for your interest. However, this issue should not prevent you from
importing MS Office files in _modern_ Korean. This issue has to do with
supporting pre-1933 orthography Korean text. It depends on implementing U+1100
Hangul Jamo rendering support in ICU rendering engine, but I have yet to hear
back from Eric Mader. I'll try once more to ask him for some help with which I
hope I'll be able  to implement rendering Hangul (Jamos) with opentype fonts. 
Comment 11 Rob Weir 2013-07-30 02:20:22 UTC
Reset assignee on issues not touched by assignee in more than 2000 days.