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

[Kurt Roeckx]

On Thu, Apr 03, 2008 at 02:08:51PM -0400, James Vega wrote:
> 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.
[...]
> This is the default if you're working in a utf8 environment.
[...]
> This is because you're not running Vim in a utf8 environment.
[...]
> 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 know that using an utf8 locale would fix this problem.  But I don't
want to have to play with the state of the terminal + enviroment all the
time, so I'm currently stuck with an latin1 terminal.

It's not because I'm still using an latin1 terminal that I should go
and configure vim to tell that I really have a latin1 terminal.


Kurt