It looks like a bit early to discuss GooGyeul at this point. I will
contact someone who are actively working for Non-standard character
registration in Korea and will be back.
Thanks
SeuksooS
-----Original Message-----
From: Jungshik Shin [mailto:jshin@mailaps.org]
Sent: Tuesday, July 24, 2001 4:53 PM
To: Seuk Soo Sung
Cc: Unicode Mailing List
Subject: Korean GooGyeol (was RE: Wordprocessors in Korean)
Thanks a lot for your kind and detailed answer. I'm very glad that
Microsoft set an example of Old Hangul support with dynamic glyph
composition (as opposed to pre-composed glyphs) and made it clear that
Hangul should be treated as a complex script along with Indic/Thai/Lao
scripts to be fully supported. I'll get back to you with more questions
later :-). For the moment, I'll digress a bit from Hangul and begin a
new thread about encoding Googyeol characters in Unicode.
On Tue, 24 Jul 2001, Seuk Soo Sung wrote:
> On Tue, 17 Jul 2001, Jungshik Shin wrote:
JS> Again, how do you represent 255 Gugyeol characters in both MS Word
JS> 2000 and 2002?
JS> Do you use PUA here again?
SS> Yes. GooGyeul is assigned in PUA for both MS Word2000 and MS
SS> Word2002 because they are not in Unicode yet. If you want to use
SS> GooGyeul in your document and publish it on the Web, you should have
SS> proper fonts, too. MS Word made GooGyeul and fonts, and published
SS> them. Of course, you can also get these font files from
SS> http://www.korean.go.kr.
This point (about GooGyeol characters not encoded in Unicode yet) may
be debatable and I like to seek opinions of Unicode experts(John Jenkins
and others) as well as yours (and some Korean linguists you
consulted) on this issue. I put up a screenshot of glyphs for GooGyeol
characters included in one of fonts mentioned above at
http://jshin.net/~jungshik/i18n/googyeol.png
I haven't extensively checked them against Chinese characters and
Kangxi radicals encoded in Unicode 3.1, but it seems to me obvious (just
from casually looking at them) that most of them have been already
encoded (certainly there are some characters not likely to be encoded in
Unicode 3.1). For instance, a character at row 4 and column 1 is
U+6597 and a character at row 2 and column 1 is U+2F89 (or U+826E).
Their usages and semantics are different from Chinese characters and
radicals with similar (or almost identical) shapes, but could that be a
sufficient ground for giving them distinct code points? It may or may
not. Kangxi radical block at U+2F00/U+2E80 have a lot of overlaps with
Chinese characters elsewhere and some Bopomofo letters are almost
identical in shape to Kangxi radicals (e.g. U+3114 is similar in shape
to
U+2F3B and U+5F73). However, morphological similarities didn't prevent
them from being granted distinct code points. (yet another example along
this line is Kanbun characters at U+3190 - U+319F). So, what's to be
done with GooGyeol characters?
Have you heard of any plan for the Korean liason to IRG (or Nat'l
Language Res. Inst. of South Korea ) to submit a proposal to encode them
in Unicode/ISO 10646 separately? IIRC, there was no proposal a few
months ago when I visited the IRG web page.
I believe any input from members of this list would be appreciated by
(a) prospective author(s) of a proposal (if necessary) to add
GooGyeol
characters.
Jungshik Shin
This archive was generated by hypermail 2.1.2 : Thu Jul 26 2001 - 09:47:01 EDT
