Re: Bug report: mapping fails with a few characters (i.e.: « :imap ’ foo » fails)

2007-03-02 Thread thomas

2007/3/2, A.J.Mechelynck [EMAIL PROTECTED]:

 Mapping seems to be buggy with some characters.
 For instance:

 :imap ' foo

 does not work (the apostrophe is U+2019).

What is 'encoding' set to? Using multibyte characters (e.g. in a mapping) will
only work if 'encoding' (which defines how characters are represented
internally in Vim memory) is set to an appropriate multibyte setting
beforehand


The encoding is set to utf-8. My point is, mapping works with some
multibyte characters, but not all of them. For example:

:imap ∀ foo

... that is, mapping the forall symbol (U+2200), works.

Since I can map some multibyte characters, there is in my opinion no
issue with the encoding.
The question is: why is it possible to map U+2200 but not U+2019?

Regards,
thomas


Re: Bug report: mapping fails with a few characters (i.e.: « :imap ’ foo » fails)

2007-03-02 Thread A.J.Mechelynck

thomas wrote:

2007/3/2, A.J.Mechelynck [EMAIL PROTECTED]:

 Mapping seems to be buggy with some characters.
 For instance:

 :imap ' foo

 does not work (the apostrophe is U+2019).

What is 'encoding' set to? Using multibyte characters (e.g. in a 
mapping) will

only work if 'encoding' (which defines how characters are represented
internally in Vim memory) is set to an appropriate multibyte setting
beforehand


The encoding is set to utf-8. My point is, mapping works with some
multibyte characters, but not all of them. For example:

:imap ∀ foo

... that is, mapping the forall symbol (U+2200), works.

Since I can map some multibyte characters, there is in my opinion no
issue with the encoding.
The question is: why is it possible to map U+2200 but not U+2019?

Regards,
thomas



Hm. It just might be a bug, but Bram would be better able than me to check this.

I can map Char-0x2019 but I cannot really test that it works (I can just see 
that it is represented correctly in the list of mappings), because that 
character is not on my keyboard.


U+2019 is encoded as E2 80 99 while U+2200 is E2 88 80. I wonder if the 
presence of a 0x80 in the middle might cause a bug in gvim.


Did you try the code snippet in my previous post? If it works, then we can 
start digging why your previous method didn't work. If it doesn't, we should 
have a clear-cut testcase for others to try and reproduce.



Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
80. At parties, you introduce your spouse as your service provider.