support for decomposed Korean in Unicode?

support for decomposed Korean in Unicode?

[Werner LEMBERG]

[-- Attachment #1: Type: Text/Plain, Size: 660 bytes --]


In Unicode, Korean syllables can either be encoded as composite, for
example

  은

or decomposed into elements, Jamo:

  은

This process doesn't require big lookup tables since the former can be
derived from the latter, and vice versa (the Unicode book holds the
algorithm).

It would be great if Emacs supported this, perhaps similar to the
tibetan-compose-xxx functions: If a jamo character code is detected in
a buffer, try to automatically compose it to a complete hangul
syllable -- again, this process is described in the Unicode book.

If you want to see this in practice, have a look at the Yudit editor.


    Werner

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

Re: support for decomposed Korean in Unicode?

[Andreas Schwab]

Werner LEMBERG <wl@gnu.org> writes:

> If you want to see this in practice, have a look at the Yudit editor.

Another way to see this is to visit your mail in an Emacs running in
xterm, which does this composition as well.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: support for decomposed Korean in Unicode?

[Kenichi Handa]

In article <20060106.115007.108803724.wl@gnu.org>, Werner LEMBERG <wl@gnu.org> writes:

> [1  <text/plain; utf-8 (base64)>]
> In Unicode, Korean syllables can either be encoded as composite, for
> example

>   은

> or decomposed into elements, Jamo:

>   은

> This process doesn't require big lookup tables since the former can be
> derived from the latter, and vice versa (the Unicode book holds the
> algorithm).

Yes, I know about that.  I'm going to implement it in
emacs-unicode-2 because it supports all all Korean syllables
in Unicode and thus easier to implement.

---
Kenichi Handa
handa@m17n.org