First, thanks for the answer, Tony. OK, I think I've put it into wrong words. Probably it is not a multibyte problem. I can enter digraphs with Ctrl-K or Ctrl-V. But I cannot enter characters using the alt-Key, those ones with Alt-Gr work. On another machine running Suse 9.3 this works, e.g. entering Alt-q in insert mode produces the same character that Ctrl-k n?. The problem is that I cannot use mappings with Alt!
I tried different givm Versions, I even compiled the latest stable version from vim.org on my own. But the described effect remains. The Alt-Key itself works, e.g. in xterm or firefox. I can also handle the gvim installed at that other machine via ssh, and there as mentioned alt-mappings do what they should. Any further hints? Cheers Christian A.J.Mechelynck wrote: > Christian Brehm wrote: >> Hi, >> >> I just installed gvim at SuSe 10.1 (Version 6.4, 2005 Oct, 15th, >> compiled May 2006). >> multi_byte and multi_lang is enabled. >> But still I cannot use any multibyte characters. At all, every command >> containing the 'Alt' key doesn't work... >> I've set the language to [EMAIL PROTECTED], but others like C do not change >> the >> behavior. encoding is set to iso-8859-15. >> >> Can anyone help me or give some hints? >> >> Thanks, >> >> Christian >> > > Entering characters by numeric value in Vim doesn't use the Alt key, see > ":help i_CTRL-V_digit". The method described there works also in > Command-line mode, even though the help tag starts with i_ > > ...and if you use Ctrl-V to paste, replace it by Ctrl-Q wherever it is > mentioned in the Vim documentation. > > For special characters, don't use the plain Alt key (left of the space > bar) but Alt-Gr (right of the space bar). AltGr-e should for instance > give € (the euro sign) if your current 'encoding' knows it, if your > 'termencoding' is set to what your keyboard driver sends (usually the > value of 'encoding' at Vim startup), and if you have a "modern" keyboard > driver which knows about the Euro sign. > > Note that ISO-8859-15 is _not_ a multibyte encoding (only 256 values, > 0x00 to 0xFF, are defined in that encoding). > > To really test myltibyte functions, try setting 'encoding' to Unicode as > follows: > > if &encoding !~? '^u' > if &termencoding == '' > let &termencoding = &encoding > endif > set encoding=utf-8 > set fileencodings=ucs-bom,utf-8,default > setglobal bomb " optional line > endif > > In UTF-8, all codepoints above U+007F are multi-byte. > > > Best regards, > Tony.
