Bug#379107: Reasoning behind 'encoding'/'termencoding' differences

[James Vega]

On Thu, Apr 03, 2008 at 07:23:53PM +0200, Kurt Roeckx wrote:
> To restate my problem:
> - I want to be able to edit files that are not written in whatever my
>   environment says and that it properly interpretes and shows that file
>   to me.  This does not happen with the default values.

This is the default if you're working in a utf8 environment.

>   So that means that I want I want fileencodings to contain something so
>   that it looks what encoding the file is so it can properly set
>   fileencoding.
> 
>   With the settings I use now, and what I really want, is:
>   ucs-bom,utf-8,default,latin1

This is the default if you're working in a utf8 environment.

>   The default value without changing settings is: ucs-bom

This is because you're not running Vim in a utf8 environment.

>   For this to work, it needs to be able to convert from fileencoding
>   to termencoding.  For this to work, it needs to internally work in an
>   "encoding" that supports both.  The most logical choise for that is
>   unicode / utf-8.

This is the default if you're working in a utf8 environment.

Not to beat a dead horse, but it sounds like the real solution here is
to use a utf8 locale for your environment.  You're choosing not to use a
utf8 locale and therefore need to configure Vim to know how to convert
between your locale and the encoding you want Vim to use.

I'll talk to upstream about decoupling 'termencoding' from 'encoding'
but this isn't something that I'll differ from upstream on.  That would
pretty much require to always default 'encoding' to utf8.

-- 
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <jamessan at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20080403/cd627e5e/attachment.pgp