On Wed, Feb 10, 2016 at 11:40 AM, Erik Christiansen
<dvalin@internode.on.net> wrote:
> On 09.02.16 15:19, Nikolay Aleksandrovich Pavlov wrote:
>> 2016-02-09 14:48 GMT+03:00 Erik Christiansen <dvalin@internode.on.net>:
>> > Thank you for the hints, Tony, but nothing tried so far is making any
>> > difference. Vim still won't display Cyrillic, Greek, or Russian.
>> >
>> > But is this a clue? My immediate prior post, containing åæø, came back
>> > from the list server with those three characters now displaying in vim
>> > as -C3-A5-C3-A6-C3-B8, despite the header: "X-NotAscii: charset=utf-8".
>> > (Again, s/-/==/g) In vim, encoding, fileencoding, and termencoding are
>> > all utf-8.
>> >
>> >
>> > Is our list server not sending utf-8, despite the header claim?
>>
>> It is sending a proper UTF-8. You must use a client which correctly
>> decodes the message: you should see those equals signs if
>> Content-Transfer-Encoding is [quoted-printable][1], but message body
>> was not decoded.
>
> OK, so after a post with e.g. Cyrillic characters is correctly displayed
> by mutt in a utf-8_capable xterm, these high valued 8-bit characters
> become unreadable when the post is opened in vim for composing a reply,
> because the MUA only decodes for display. It does not alter the received
> email.
>
> ...
>> See also https://en.wikipedia.org/wiki/Unicode_and_email.
>>
>> [1]: https://en.wikipedia.org/wiki/Quoted-printable
>
> Thank you for your advice and the links. Both have crystallised the
> problem. I apparently now need to either have postfix or procmail invoke
> a quoted-printable to utf-8 decoder on all incoming emails, or have mutt
> invoke the same when passing the quoted text to vim for composing a
> reply.
Ah, yes. Vim would presumably display a message in utf-8 with no
trouble if its Content-Transfer-Encoding were 7bit (us-ascii
compatible) or 8bit, but not quoted-printable (everything above
U+007F, even Latin1 accented characters, would be replaced by two or
more =xx groups, with xx being hex digits) and of course a message in
base64 would be even less understandable. You could try pasting from
the mail reader to Vim (using a different program or terminal if
necessary to remember the "* X selection, since IIUC the xterm, unlike
konsole, cannot access the "+ clipboard): that should keep everything
as you see it. But I suppose it wouldn't copy the headers.
Best regards,
Tony.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment