Hello, I'm trying to figure out how to configure vim on my system. I'm running Windows XP (English menus, but with Japanese support enabled) and would like to...
Rick Frankum
frankum@...
Oct 4, 2003 6:09 pm
987
... Hello. I have only some of the answers you are looking for. Probably someone else will jump in to fill in what I didn't know. ... +multi_byte_ime/dyn means...
Tony Mechelynck
antoine.mechelynck@...
Oct 4, 2003 6:41 pm
988
... I appreciate it! ... To update: the vim I have is indeed multibyte-enabled. The big problem appears to be that I'm not editing S-JIS files but in fact...
Rick Frankum
frankum@...
Oct 5, 2003 4:13 pm
989
... You need iconv.dll to handle euc-jp. You also need to change "fileencoding", not "encoding". "encoding" represents the internal representation, and should...
Glenn Maynard
glenn@...
Oct 5, 2003 8:42 pm
990
Hi, (vim 6.2, WinXP) If I use the UTF-8 encoding, and enter non-ascii characters in filenames, they also use the UTF-8 encoding. That's clearly wrong on...
Camillo Särs
ged@...
Oct 10, 2003 12:16 pm
991
Hmm. My reply appears to have vanished without a trace. I'd attached os_win32.c (not noticing that it was an extremely oversized source file--over 100k); I'm...
Glenn Maynard
glenn@...
Oct 12, 2003 7:48 pm
992
Glenn Maynard <glenn@...> wrote: [...] ... [...] There are more problems than just printing. As long as 'fileencoding', 'printencoding' and (most...
Tony Mechelynck
antoine.mechelynck@...
Oct 12, 2003 8:44 pm
993
... This is a trivial fix, which I already proposed many months ago: the defaults in Windows should be the results of exe "set fileencodings=ucs-bom,utf-8,cp"...
Glenn Maynard
glenn@...
Oct 12, 2003 9:39 pm
994
... Trivial or not, my opinion is that handling files and keypresses as per the locale shouldn't be a "fix", it should be the (program) default. The "minor ...
Tony Mechelynck
antoine.mechelynck@...
Oct 13, 2003 12:41 am
995
... My suggestion was that these be the default settings in Windows, not be settings that the user has to fix. ... This sounds like a bug. The input from...
Glenn Maynard
glenn@...
Oct 13, 2003 1:29 am
996
... I understood you as meaning that the program-default setting should be Unicode. I beg to differ, however. Or maybe I misunderstood what you were saying....
Tony Mechelynck
antoine.mechelynck@...
Oct 13, 2003 3:21 am
997
... I believe that the *internal* encoding ("encoding") can, if the various bugs are fixed, reasonably be UTF-8, unless there's outcry about memory usage. I...
Glenn Maynard
glenn@...
Oct 13, 2003 4:16 am
998
... so, IIUC, if we want to keep keyboard input, printer output, and file creation to operate by default according to the geographic locale, then one thing...
Tony Mechelynck
antoine.mechelynck@...
Oct 13, 2003 5:28 am
999
... That's what I was suggesting originally, I just wasn't clear enough. ... (Right, but the difference is significant, so I just wanted to make it clear that...
Glenn Maynard
glenn@...
Oct 13, 2003 5:44 am
1000
... Correct. Additionally, you can always enter any unicode character code directly from the keyboard. All that is needed is the numeric keypad in numlock...
Camillo Särs
ged@...
Oct 13, 2003 7:24 am
1001
... They don't break down, they're just imperfect. ... Vim should support UTF-8 in 9x, too. ... It works well for many uses; I use enc=utf-8 exclusively, to...
Glenn Maynard
glenn@...
Oct 13, 2003 7:47 am
1002
... The default that Vim starts with is 'encoding' set to the active codepage and 'fileencoding' set to "ucs-bom". This means it falls back to 'encoding' when...
Bram Moolenaar
Bram@...
Oct 13, 2003 9:38 am
1003
... Well, if I can't write a filename the way I need to write it, I have a problem. Fortunately this is mostly theoretic for me, but for some users resorting...
Camillo Särs
ged@...
Oct 13, 2003 10:00 am
1004
... On Windows NT/XP there are also restrictions, especially when using non-NTFS filesystems. There was a discussion about this in the Linux UTF-8 maillist a...
Bram Moolenaar
Bram@...
Oct 13, 2003 10:55 am
1005
... Right, I forgot about those. AFAIK, the fuctions do not fail silently in those cases, so it's just (yet) more work. Essentially, file names then come...
Camillo Särs
ged@...
Oct 13, 2003 11:51 am
1006
... Because every fopen(), stat() etc. will have to be changed. ... This only means extra work, since an "if (encoding == ...)" has to be added to select...
Bram Moolenaar
Bram@...
Oct 13, 2003 12:23 pm
1007
... Right. You're not using Windows apis, of course. But to do things correctly, you would have to make sure that the fopen() etc. implementations [in...
Camillo Särs
ged@...
Oct 13, 2003 12:59 pm
1008
... [...] ... [...] Glenn Maynard wants 'encoding' to default to "utf-8" regardless of the active codepage. IMHO this would require 'termencoding' to default,...
Tony Mechelynck
antoine.mechelynck@...
Oct 13, 2003 3:39 pm
1009
... [...] ... Took me some figuring too. A few hours ago I uploaded my solution to vim-onlline (set_utf8.vim, ...
Tony Mechelynck
antoine.mechelynck@...
Oct 13, 2003 3:52 pm
1010
... A file name may appear in a file (e.g., a list of files in a README file). And I don't know what happens with file names on removable media (e.g., a CD)....
Bram Moolenaar
Bram@...
Oct 13, 2003 6:47 pm
1011
Note that I've upgraded, and I'm not having problems with files saving incorrectly in enc=utf-8. The remaining problems are mostly cosmetic, except for not...
Glenn Maynard
glenn@...
Oct 13, 2003 9:58 pm
1012
... Both floppies, CDs and network file systems are mounted by windows, and "some" translation of file names happens. AFAIK, you should be able to access all...
Camillo Särs
ged@...
Oct 14, 2003 5:54 am
1013
... So, what you suggest is to keep using the ordinary file system functions. But we must make sure that the file name is then in the active codepage...
Bram Moolenaar
Bram@...
Oct 14, 2003 12:19 pm
1014
... While that may sound attractive at first, I would strongly dissuade from that solution. I consider it to be a myth that using multilingual filenames on...
Camillo Särs
ged@...
Oct 14, 2003 12:51 pm
1015
... Vim not only supports Unicode but also many other encodings. When Vim would only use Unicode it would be simple, but that's not the situation. And above...