Saluton Tuomas :) On Fri 22 May 2009 18:26 +0200, Tuomas Pyyhtiä <[email protected]> dixit: > 'Fileencodings' setting in my gvimrc is set as: set > fileencodings=ucs-bom,utf-8,latin1 When I do :fileencoding? after have > opened the file, I get latin1 as should.
Of course, because cp1250 is a monobyte encoding and although 0x0095 has not a glyph in latin1, it is not an invalid character. 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". The problem with the monobyte encodings is that all of them cover the characters from 0x00 to 0xff, so there is no way of telling which encoding the file really has except by using a human brain and try to read it ;)) -- Raúl "DervishD" Núñez de Arenas Coronado Linux Registered User 88736 | http://www.dervishd.net It's my PC and I'll cry if I want to... RAmen! --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
