Hi! Am 03.03.2009 06:40, James Vega schrieb: > [...] >> 2) Vim compiled with the --disable-multibyte configure option cannot use >> UTF-8, or any other multibyte encoding; in fact it doesn't even accept >> the 'encoding' option as valid. > > Is there a reason to allow building Vim without multibyte support? > Always having multibyte support would make the code simpler/smaller.
It would make the code smaller but compiling without multibyte support probably makes the resulting binary smaller. That can make a big difference for users on resource constrained systems. >> 3) 'termencoding' (the encoding used for the keyboard and, in Console >> mode, for the display) defaults to empty (which means, fall back to >> 'encoding') except when running in GUI mode with GTK2. This means that, >> by default, communication between Vim and the user is done in the system >> locale. > > Unless 'encoding' is set in the user's ~/.vimrc, which in my experience is > pretty common. I'm not sure how closely that aligns with the overall usage > patterns, though. > [...] FWIW, I don't explicitly set it in my .vimrc. My Ubuntu (8.10) system uses an UTF-8 locale and Vim detects it. Because this just works I suppose it's not that common to set it explicitly. Dennis Benzinger --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
