(character) Conversion error (in vi) ?

Ronald F. Guilmette rfg at tristatelogic.com
Sun May 17 03:23:12 UTC 2020

In message <ec8735ff-fcf1-7ee4-1aed-4aa9b87c655c at fastmail.com>, 
Yuri Pankov <ypankov at fastmail.com> wrote:

>No, it's not that bug after all.  The issue is that (n)vi now (for quite 
>some time :-) defaults to UTF-8 when it can't reliably detect the file 
>encoding, so you'll just have to help it a bit adding the following to 
>set fileencoding=iso8859-1
>This way (n)vi will check if file encoding looks like UTF-8, and if not, 
>it will use ISO8859-1 as fallback.

Ahhhhhh... I did what you said and yes, that fixed it!

Thanks ever so much!  This has been bugging me fofr quite awile.

And my apologies for being to lazy/preoccupied to dredge deeply
enough into the man pages to be able to find this solution on
my own.

If you were my fairy godmother, then I'd ask you to grant me
one more wish, which would be to have (n)vi always be able to
automagically correctly detect the content encoding in any given
file it is asked to load.  But you're not, so I won't. :-)

Still, it seems like it out to be possible to do.  It appears
that a hnuman (you) didn't have much trouble figuring out the
correct encoding type in this instance, so one would think
that this one piece of software might be able to do a better
job in this particular guessing game.  (Should I bother to
submit a PR / enhancement request for that?)


More information about the freebsd-questions mailing list