From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: mail back to UTF-8 before save to HD
Date: Sat, 06 Feb 2016 22:36:30 +0100 [thread overview]
Message-ID: <87d1s9frmp.fsf@debian.uxu> (raw)
In-Reply-To: <87zivel41q.fsf@iki.fi>
Teemu Likonen <tlikonen@iki.fi> writes:
>> Only the Subject is now
>> =?utf-8?B?w6XDpMO2IMOFw4TDlg==?
>
> And that's how it should be. Headers must be "Q" or
> "B" coded (quoted printable or base64,
> respectively).
>
> It is actually possible to make headers unencoded
> with variable gnus-group-posting-charset-alist BUT
> DON'T DO IT. Your messages will be broken in other
> people's mail agents and you'll be instructed to fix
> your configuration. Headers must be in
> =?charset?encoding?...?= format if there is anything
> other than Ascii characters.
Actually changing the transfer encoding at all wasn't
my original idea. Instead to do a conversion
after-send prior to the actual archiving on the disk.
But UTF-8 is pretty much standard as well, aye? So why
not.
This seems to be the best solution because now not
only are the messages archived in a form that is
searchable and readable, they are also still messages
that don't need to be "converted back" if used in
a mail setting again.
--
underground experts united
http://user.it.uu.se/~embe8573
prev parent reply other threads:[~2016-02-06 21:36 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
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 [this message]
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=87d1s9frmp.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--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).