From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: mail back to UTF-8 before save to HD
Date: Sat, 06 Feb 2016 15:23:01 +0100 [thread overview]
Message-ID: <874mdlsyt6.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87oabumvmr.fsf@debian.uxu>
Emanuel writes:
> asjo@koldfront.dk (Adam Sjøgren) writes:
>>> Only the Subject is now =?utf-8?B?w6XDpMO2IMOFw4TDlg==?
>> 8-bit is not allowed in headers; rfc2047 specifies
>> how to encode non-ascii values in headers - the
>> result is what you see.
> Then the only issue left is why the UTF-8 don't show
> up in the raw article mode.
They won't, because the standards (RFCs) do not allow 8-bit characters
in headers, as I just wrote above. "Raw" headers must be encoded, in the
way specified in rfc2047.
It is then up to the program displaying (or indexing, or searching) them
to decode the representation.
Best regards,
Adam
--
"I am still twitching at the idea that you need to Adam Sjøgren
load code into the kernel in order to re-map a asjo@koldfront.dk
mouse button."
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2016-02-06 14:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 3:37 Emanuel Berg
2016-02-04 7:45 ` Peter Münster
2016-02-04 21:32 ` Emanuel Berg
2016-02-05 18:42 ` Emanuel Berg
2016-02-05 18:59 ` Teemu Likonen
2016-02-06 0:20 ` Emanuel Berg
2016-02-06 2:11 ` Adam Sjøgren
2016-02-06 2:15 ` Emanuel Berg
2016-02-06 14:23 ` Adam Sjøgren [this message]
2016-02-06 21:47 ` Emanuel Berg
2016-02-06 21:56 ` Adam Sjøgren
2016-02-06 22:17 ` Emanuel Berg
2016-02-06 22:34 ` Adam Sjøgren
2016-02-07 3:21 ` Emanuel Berg
2016-02-07 3:31 ` Emanuel Berg
2016-02-06 6:57 ` Teemu Likonen
2016-02-06 21:36 ` Emanuel Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mdlsyt6.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=info-gnus-english@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).