On Fri, Nov 6, 2009 at 4:31 PM, Paolo Baruffa <[email protected]> wrote:
> > > to winterTTr: > > > What's the value for the option "encoding" ? > > querying ":set", encoding doesn't appear - maybe because I don't setted it > in .vimrc... > > querying "set encoding", answer is "latin1" (which is correct) > > > >> refreshing the file on the other editor > >> I see the same coding > Maybe i know the reason. Because the sequence of setting you set to the fileencodings. When a file is read , vim try to read the file via the each one you set to the "fileencodings" until he find the one with which the file could be read in correctly. Then vim will set the fileencoding to the one he find. You set "utf-8" before "latin1" in fileencodings as below : :set fileencodings=ucs-bom,utf-8,latin1 " autosense coding so when the vim try to read a file , he will try to use the encoding utf8 to read the file , and success. So ,the fileencoding is always set to utf8 . # Latin1 never has the change to be used. > > What do you mean for the "The same coding "? > > pls, forget this point: > GVim is latin1, other editor is ANSI. > GVim convert to utf-8: refreshing other editor shows "utf-8 w/signature". > GVim convert to latin1: refreshing other editor it DID show again utf-8... > I don't know why... now it works... > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
