Re: mhfixmsg character set conversion

[Steven Winikoff]

>>    - run ~smw/bin/decode_headers using $source as stdin (this explicitly
>>      decodes headers which are RFC 2047-encoded, and passes the body
>>      through unchanged)
>
>This sounds like the kind of thing which might insert bytes which alter
>vim's idea of the ‘fileencoding’.  Given
>
>    To: =?ISO-8859-1?Q?Keld_J=F8rn_Simonsen?= <keld@dkuug.dk>
>
>as taken from RFC 2047, is it going to put in a byte 0xf8 for ISO 8859-1
>encoding, or 0xc3 0xb8 for UTF-8?

I didn't know, so I just tried it.  Here's what happens:

   # decode_headers < rfc2407_test_header > converted_rfc2407_header
   # cat converted_rfc2407_header
   To: Keld Jørn Simonsen <keld@dkuug.dk>

   # hexdump -C converted_rfc2407_header
   00000000  54 6f 3a 20 4b 65 6c 64  20 4a c3 b8 72 6e 20 53  |To: Keld J..rn 
S|
   00000010  69 6d 6f 6e 73 65 6e 20  3c 6b 65 6c 64 40 64 6b  |imonsen 
<keld@dk|
   00000020  75 75 67 2e 64 6b 3e 0a                           |uug.dk>.|
   00000028

...so it writes 0xc3 0xb8, which I believe is what it should be doing.

     - Steven
-- 
___________________________________________________________________________
Steven Winikoff      | "The most exciting phrase to hear in
Montreal, QC, Canada |  science, the one that heralds new
smw@smwonline.ca     |  discoveries, is not 'Eureka!' (I found
http://smwonline.ca  |  it!), but 'That's funny...'"
                     |                         - Isaac Asimov