From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: bug: incorrect encoding of user-full-name
Date: Sun, 20 Oct 2002 23:16:55 +0000 (UTC) [thread overview]
Message-ID: <m367esqq1l.fsf@sparky.gnus.org> (raw)
In-Reply-To: "=?iso-8859-5?b?stvQ1Njc2OAgst7b3tLY5w==?="'s message of "13 Sep 1998 13:28:33 +0400"
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 908 bytes --]
"²ÛÐÔØÜØà ²ÞÛÞÒØç" <vvv@vvv.vsu.ru> writes:
> Well, i think that the From header (and other headers) should be
> created after encoding. For example, when i do
> (setq message-from-style 'angles), my From header looks like:
>
> From: "=?iso-8859-5?b?stvQ1Njc2OAgst7b3tLY5w==?=" <vvv@vvv.vsu.ru>
Uhm. And this isn't even valid, since one can't have encoded-words
inside qouted-strings. *sigh*
Er.
I really want to generate the headers first, and then encode then
afterwards; it makes things a whole lot easier.
Perhaps the encoder should treat qouted-strings as one word, and if it
contains something that is to be encoded, then it should remove the
quotes and then encode the rest? Would that be correct under all
circumstances? I guess \"-s inside the strings would have to be
undone first...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2002-10-20 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-12 12:58 vvv
1998-09-13 5:30 ` Lars Magne Ingebrigtsen
1998-09-13 9:28 ` Владимир Волович
2002-10-20 23:16 ` Lars Magne Ingebrigtsen [this message]
1998-09-14 18:21 ` Владимир Волович
1998-09-14 20:39 ` François Pinard
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=m367esqq1l.fsf@sparky.gnus.org \
--to=larsi@gnus.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).