Re: [Mutt] #1317: wish $edit_charset

[Mutt <fleas@xxxxxxxx>]

#1317: wish $edit_charset
------------------------------------------------+---------------------------
  Reporter:  Tony Leneis <tony@xxxxxxxxxxxxxx>  |       Owner:  mutt-dev
      Type:  enhancement                        |      Status:  new     
  Priority:  minor                              |   Milestone:          
 Component:  charset                            |     Version:  1.4i    
Resolution:                                     |    Keywords:          
------------------------------------------------+---------------------------

Comment(by Kurt Roeckx):

 {{{
 On Wed, Jul 01, 2009 at 03:04:34PM -0000, Mutt wrote:

 My terminal is set up to use to latin1 encoding.  It supports
 everything I need to be able to read/write.  Not all the
 applications I use support an UTF-8 encoding.

 However, I want files that I edit to be in stored in UTF-8, so
 I've configured vim to default to UTF-8.  Vim will detect that
 a file is not encoded in UTF-8 and try latin1 in that case.

 If I reply to a mail, that uses more than just plain ASCII,
 I actually never have a problem, mutt will give it to vim in
 latin1, and vim will see that it's latin1 and keep it that way.

 The problem is when it's either an empty file or one that's just
 plain ASCII.  It could be either UTF-8 or latin1, and vim will
 default to UTF-8.  So when I type something non-ASCII and save
 it and go back to mutt, mutt will think it's a latin1 file,
 while vim saved it as a UTF-8 file, and I end up mailing
 something that claims a wrong encoding.

 I've now configured vim to use a file encoding of latin1
 for mails and my mails end up with a proper encoding now.  Both
 programs now think it's a latin1 file, so things work.

 However, there are a few small problems with it, like for instance
 the name of someone might not be something I can represent in
 latin1, and I end up sending a reply with a slightly different
 name.  Note that I can properly write his name in vim even when
 the encoding of my terminal can't represent it.


 I'm guessing you either only use 1 encoding, UTF-8, or you really
 change your locale settings and then end up being unable to
 read/write files using an other encoding.


 Kurt
 }}}

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/1317#comment:>
Mutt <http://www.mutt.org/>
The Mutt mail user agent