Received: by 10.36.106.2 with SMTP id e2mr3104004nzc.1186155107260;
        Fri, 03 Aug 2007 08:31:47 -0700 (PDT)
Return-Path: <ben.peter...@riskcare.com>
Received: from MAILONE.riskcare.com (gateway.riskcare.com [81.3.93.70])
        by mx.google.com with ESMTP id v28si811790nzb.2007.08.03.08.31.46;
        Fri, 03 Aug 2007 08:31:47 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of ben.peter...@riskcare.com designates 81.3.93.70 as permitted sender)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: Fwd: VIM 7.1 compilation error
Date: Fri, 3 Aug 2007 16:31:50 +0100
Message-ID: <A70226A35219F24CB5AC282C89D2699101D151A3@xtranetserver>
In-Reply-To: <bcbc1a860708030823m638667djda0fa306c358eade@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Fwd: VIM 7.1 compilation error
Thread-Index: AcfV4kgRoPXUGzSKTQilCcwku1iGfwAAPLRw
References: <22316227.444471186129992559.JavaMail.nabble@isper.nabble.com> <bcbc1a860708030216t75721c7fvd98954995a06da0f@mail.gmail.com> <46B3149A.1060109@gmail.com> <bcbc1a860708030742y4da084a5hf8a763d9deb107eb@mail.gmail.com> <46B34524.9070701@gmail.com> <bcbc1a860708030823m638667djda0fa306c358eade@mail.gmail.com>
From: "Ben Peterson" <ben.peter...@riskcare.com>
To: <vim_multibyte@googlegroups.com>,
	<vim_dev@googlegroups.com>
Cc: "Bram Moolenaar" <b...@moolenaar.net>,
	"vim-dev" <vim-...@vim.org>,
	<vim-multib...@vim.org>,
	<um.ki...@gmail.com>

Hi,

  Wouldn't hangul be a very big keymap?  If the keymap was for individual jamo it would be manageable but I'm not sure how vim would then combine the jamo.  If it is for all hangul characters it will be very large -- unless I am missing something.

  On the other hand, it should also be relatively easy to generate the keymap automatically...

  Benjamin

-----Original Message-----
From: vim_multibyte@googlegroups.com [mailto:vim_multibyte@googlegroups.com] On Behalf Of Edward L. Fox
Sent: 03 August 2007 16:23
To: vim_dev@googlegroups.com
Cc: Bram Moolenaar; vim-dev; vim-multib...@vim.org; um.ki...@gmail.com
Subject: Re: Fwd: VIM 7.1 compilation error


Hi Shawn Kim,

On 8/3/07, Shawn Kim <orchis...@gmail.com> wrote:
> [...]
> In those system, I don't seem to have many choices.
> I MUST compile vim enabling hangulinput feature and then use it to
> type in Hangul.
> It would never be enough to stress the necessity and the importance of
> that feature for Koreans.
> I would be devastated if that feature is to removed :'O

OK, I see. But I'm still wondered that could this feature be
implemented as a keymap? Like this:

1. :set keymap=kana

2. Type "ohayougozaimasu" will produce:

 $B$*$O$h$&$4$6$$$^$9!# (J

If we could implement the Hangul input as a keymap, we can simply drop
the Hangul automata without any difficulty then.

>
> Regards,
> Shawn.
>
> P.S. Personally, using XIM with vim is kind of confusing.
> If you were typing Hangul in input mode, and then you escape from that
> mode by pressing upon ESC,
> XIM is still in Hangul input mode. So, any of your comands won't work
> until you switch to English input mode by
> pressing Shift+Space. It is very unconvinient and confusing.
> As it seems that I can seem to control XIM out of it, like sending
> signal or something, for me,
> it is just more appreciated using hangulinput feature. :-)

Just type ":help imactivatekey" and read this part of the manual,
maybe it's useful for you. :-)

>
> [...]


In peace,

Edward L. Fox

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_multibyte" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---