Tuesday, September 25, 2012

Re: E670: Mix of help file encodings within a language

On 25/09/12 14:32, Marco wrote:
> 2012-09-25 Tony Mechelynck <antoine.mechelynck@gmail.com>:
>
> Hi Tony!
>
>> Does the new helpfile have a BOM? If it does, try removing it.
>>
>> :e ~/.vim/doc/foobar.txt " replacing "foobar" by the filename
>> :verbose setlocal bomb?
>
> nobomb
>
>> :setlocal nobomb
>> :w
>> :helptags ~/.vim/doc
>
> E670: Mix of help file encodings within a language
>
>> If that doesn't work, check your 'encoding':
>>
>> :verbose set encoding?
>
> encoding=utf-8
>
>> Mine is UTF-8, and it sees almost all helpfiles shipped with VIM as
>> UTF-8 (eval.txt is an exception). But if a file contains as few as one
>> character which is invalid for UTF-8, the file won't be seen as UTF-8
>> even if the rest of it is OK
>>
>> :setl fenc?
>
> fileencoding=utf-8
>
>> 8g8
>
> The cursor does not move. If I set fileencoding=latin1, then it
> moves to a non-ascii character, but I guess that's expected.
>
>
> Marco
>
>
Well, is there a bomb on another helpfile?

:vimgrep /\%1l/ ~/.vim/*.txt
:setl fenc? bomb? " watch for "utf-8" together with "bomb"
" or for anything other than utf-8 or latin1
:cn|setl fenc? bomb?
:cn|setl fenc? bomb?
:cn|setl fenc? bomb?
etc.

You may of course use mapping to ease your typing:

:map <F2> :cn|setl fenc? bomb?
:map <S-F2> :cN|setl fenc? bomb?

Best regards,
Tony.
--
Harvard Law:
Under the most rigorously controlled conditions of pressure,
temperature, volume, humidity, and other variables, the organism will
do as it damn well pleases.

--
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

No comments: