On Tue, 24 Feb 2004, Derek Martin wrote:
Hi Derek,
> On Tue, Feb 24, 2004 at 08:43:09PM +0900, Jungshik Shin wrote:
> > Please, read what I wrote more carefully. I did write that deleting
> > the last letter is more useful when you're in the middle of typing a
> > sequence of letter to form a syllable.
>
> I think we're talking past eachother here... I noted that and I agree
> with it. It's specifically the fact that once I type the third
> character of a hangeul glyph, I can't backspace and change ONLY that
> last character, that annoys me. You say that most Koreans prefer that
> behavior, and I believe you. But I can't for the life of me
> understand why... ;-) To me, it seems unnatural and inefficient.
Sorry for my misunderstanding. As you may know by now, The Korean script
has several different facets. It's alphabetic, syllabic and featural
all at the same time. Therefore, different implementations at different
times on different platforms take different approaches when it comes to
representing and processing the Korean script on computer. Because you
live in Korea now, you must have seen the keypad of Korean mobile phones
and may have learned how to type Korean. It uses three keys for vowels
and 6 keys for consonants. See how consonants are grouped and you may
understand why the Korean script is featural.
> Almost invariably once I've committed an erroneous syllable, it's not
> the whole syllable I need to replace, but only the last character
> which I flubbed. Otherwise, if I made a mistake before the syllable
Anyway, I understand where you're coming from. Your complaint
is perfectly valid. What you want can and must be implemented Actually,
Nabi may already have implemented it because its input automata is based
on U+1100 Hangul Jamos. In addition, I have the same complaint about
the most popular Korean mobile phone keypad. It takes a lot more key
storkes to enter a single syllable and it's annoying to find 'backspace'
delete the whole syllable instead of the last letter typed. However,
9th graders on the street don't seem to have a problem at all because
they can type Korean so fast with the keypad that having to enter a
syllable from the beginning doesn't appear to matter to them.
So, I guess your problem would go away as you get more familiar with your
Korean keyboard and input method.
> > However, incremental search needs to be done with individual letters
> > as unit instead of syllables. I think Indian people have similar
> > needs.
Incremental search with letters as units was implemented
in only one program (Korean Emacs : Hanemacs by KIM Kang-hee) as far
as I know. It would be great if it's implemented in Mozilla's 'type as
you find'.
> > LANG=en_US.UTF-8 (or en_GB.UTF-8, en_CA.UTF-8)
> > LC_CTYPE=ko_KR.UTF-8
> > LC_MESSAGES=en_US.UTF-8 # not necessary unless LC_ALL is set, but
> > LC_TIME=en_US.UTF-8 # just to be sure.
> > -----------
>
>
> # .profile (or whatever)
> LANG=en_US.UTF-8
> LC_COLLATE=C # I like ASCII sorting for most applications...
> ...
> export LANG LC_COLLATE ...
>
> Then, when I start up an application where I want to type Korean, I
> originally tried startiing it like this:
>
> $ LANG=ko_KR.UTF-8 LC_COLLATE=ko_KR.UTF-8 LC_MESSAGES=en_US.UTF-8 gedit&
> 2. Hangeul input via ami simply didn't work.
There's one missing piece here. Sorry I forgot to tell you. You have
to set XMODIFIERS to '@im=Ami'. If you log on with the Korean locale
selected in KDM/GDM, this variable is automatically set for you on
most Linux distributions. However, apparently you don't so that you have
to set it manually.
> 1. Menus were in Korean
Really? Hmm, you may have set 'LINGUA' or something like
that (non-standard GNU extension) set to Korean. Make sure it's unset.
> As it happens, until recently the most common case I want to do this
> was with mozilla. It wasn't a major problem then, because my
> installation of Mozilla had no Korean. But as my Korean improves, I
> have more and more cases where I want to do this. Of course, I'm also
> better able to navigate the menus, but that's beside the point... :)
Actually, Mozilla language packs work independently of the locale. No
matter what your locale is, you can have Mozilla's menu in any
language for which you have installed the language pack. However,
Ami works with Mozilla only if Mozilla is launched with LC_CTYPE (or
equivalent) set to ko_KR.UTF-8/ko_KR.EUC-KR. BTW, it should be fixed
to work with any UTF-8 locales. Hmm, I'm gonna add it to the TODO list.
Jungshik
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
