On Fri, 22 May 2009 21:07:15 +0300, Raúl Núñez de Arenas Coronado <[email protected]> wrote:
> > Saluton Tuomas :) Terve Raúl! >> To open it correctly (and it worked for me), I launched Vim and issued >> ":e ++enc=cp1250 AE.txt". I don't know how to do this on the command >> line, but if you have to work with a lot of cp1250 files you would have >> to add "cp1250" to the list in "fileencodings", before "latin1". Thanks, enforcing encoding cp1250 to that AE.txt did it. And for the time being, I'm going to add cp1250 to filencodings in my .gvimrc and make a mental note it's there. > Easy: "vim --cmd "set fileencodings=cp1250" AE.txt > > Please, note the "s", it's fileencodingS, not fileencoding. > > If you only have a monobyte encoding in "fencs" (alias for > "fileencodings") it will always success, no matter what. So, by telling > vim in fencs that only "cp1250" is available, it will use that encoding. > > The problem is that, in that Vim session, if you open a latin1 file it > will be opened using cp1250, so I prefer the first method I told you, > using ":e ++enc". And I thought all the time this *was* a latin-1 encoded file (as this is the encoding my friend uses, and I think Vim win32 binaries are compiled with that encoding enabled by default.) Few questions: How am I able in the future to define what encoding the file uses? i.e. How did you see what encoding to enforce? Do I have to make my best guess and blindly enforce different encodings and proof read the file every time, or what's the best approach solving encoding horrors if I ever get into them again? --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
