Comment on PEP 263 - Defining Python Source Code Encodings

Robin Becker robin at jessikat.fsnet.co.uk
Sun May 12 14:45:32 EDT 2002


In article <j4adr5e1dt.fsf at informatik.hu-berlin.de>, Martin v. Löwis
<loewis at informatik.hu-berlin.de> writes
>Robin Becker <robin at jessikat.fsnet.co.uk> writes:
>
>> I already knew that in fact it seems to be the encoding flag that
>> determines things. I think fileencoding is used for possible conversion
>> of the file into the required encoding. Thus both 
>> gvim --cmd="set encoding=utf8" aaaa.txt
>> gvim --cmd="set encoding=utf8" aaaa.txt


>
>Did you mean to use fileencoding in one of these lines?
>

yes exactly.

>> display a utf8 file, aaaa.txt, correctly, but the latter has actually
>> converted the characters to latin1 (at least for me).
>
.......
>Still, if you put 'fileencoding=' *inside* the file, it won't work, in
>any released version of vim. That's a bug though, and hopefully fixed
>some day.
>
>Regards,
>Martin
yes I found that out.
-- 
Robin Becker



More information about the Python-list mailing list