Re: [Vim-latex-devel] buggish: vim-latex and multibyte character input

[Srinath A. <sr...@fa...>]

Hi Kihwang,

On Tue, 14 Oct 2003, Kihwang Lee wrote:

> I use Linux (tailored RedHat 7.1), gvim (6.1.165) and a XIM server
> called Ami for Korean input.  The thing is that when I use vim-latex
> with Ami, I can't input Korean characters (euc-kr) properly. It is
> hard to describe. Korean and many other scripts belong to so-called
> composite characters: you have to input several (more than 2) key
> strokes to make a meaningful unit (sort of a character, but not
> necessarily a word). I don't know about

I am assuming that the problem you are having is that in the presence of
latex-suite, you are unable to compose characters using multiple
letters. Is that right?

I am not really sure what could be going on. The way latex-suite
accomplishes most of its mappings is to map lots of characters (actually
it maps every printable characters i.e with ascii code <= 127). If for
example, after opening a tex file (so latex-suite is activated) you do:

	:imap a

you should see something like:

i  a           * <C-R>=<SNR>11_LookupCharacter("a")<CR>

The s:LookupCharacter() function resides in imaps.vim. In the normal
course of events it should just return the string 'a' when you type a. I
have a feeling that the problem is being caused by this intermediate
mapping...

Just to pinpoint the problem, do the following.

Suppose you use the sequence of characters 'ka' to type a composite
character. In the normal course of events, you would be able to open up
a non-tex file (so latex-suite is not activated) and type 'ka' get a
single composite character, right?

Now in that non-tex file (so latex-suite is not triggered), issue the
following commands:

inoremap k k
inoremap a a

Then type ka. Does the composition occur? If so, then the problem is
something else and we need to debug further. If the problem appears (i.e
composition does not happen), then the problem is with VIM itself and
not with latex-suite and you will have to submit a bug-report to
vi...@vi... or vi...@vi......

Srinath