Thank you both Tony and Kyungjoon for the detailed explanation. I understand that setting 'encode' globally is recommended (or rather the right thing to do) and so I did it. I've also set fileencodings as suggested y Tony. This seems to works fine.
The whole set of options (encoding, fileencoding, fileencodings), the different way to set them (set, localset, globalset) and the various possible places at which the setting can be done (vim config. files, filtype.vim, etc) makes the subject very difficult to handle. More over, the different treatments depending on the platform (unix vs. win32, terminal vs GUI, win32 native vs Cygwin, GTK or not, etc.). I couldn't find any reasonable explanation of what each setting means in each context; the vim helps is more of a dictionary than of a tutorial, so it is difficult to find a natural path. Some statements seems to be done implicitly assuming a unix system, some other seems related to terminals but it is not that clear whether the same is relevant for GUI. Fundamentally I'm missing a high level description of which encodings and which conversions come at which moment into play (vim startup, loading from memory, input from user, writing to disk, internal representation, whatever) On a related note: is it possible to set different fonts in different vim windows/tabs within a single application window? (I could define an autocommand to restore the default font, but there is another situation in which this would not be a solution). -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
