Loading ...
Sorry, an error occurred while loading the content.
 

Re: Character encoding errors from latin-1 to utf-8

Expand Messages
  • Matt Wozniski
    ... To quote the help: An entry for an 8-bit encoding (e.g., latin1 ) should be the last, because Vim cannot detect an error, thus the encoding is always
    Message 1 of 8 , May 31, 2009
      On Sun, May 31, 2009 at 2:30 AM, pansz wrote:
      >
      > Tony Mechelynck 写道:
      >>> Remember, as long as "cp1250" is *before* latin1 in fencs, it is like
      >>> latin1 is not even there, since cp1250 will always succeed.
      >>
      >> Exactly, so it's better to have at most one 8-bit encoding in
      >> 'fileencodings' (plural), and only in the last position, because
      >> anything after the first 8-bit encoding will never even be tried.
      >
      > Are you sure?
      >
      > cp936 is a 16-bit encoding, I've been told that cp936 will always
      > succeed and it make no sense adding anything in 'fencs' beyond cp936,
      > but that's not true, since vim will recognize invalid characters and try
      > things beyond cp936. (e.g. put gb18030 after cp936 works for my gb18030
      > file)
      >
      > For 8-bit encodings I'm not sure, but it may happen that some characters
      > are invalid for some particular 8-bit encoding so having more than one
      > 8-bit encoding may be useful.

      To quote the help:

      An entry for an 8-bit encoding (e.g., "latin1") should be the last,
      because Vim cannot detect an error, thus the encoding is always
      accepted.

      ~Matt

      --~--~---------~--~----~------------~-------~--~----~
      You received this message from the "vim_use" maillist.
      For more information, visit http://www.vim.org/maillist.php
      -~----------~----~----~----~------~----~------~--~---
    Your message has been successfully submitted and would be delivered to recipients shortly.