From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: Re: bug: incorrect encoding of user-full-name
Date: 14 Sep 1998 16:39:58 -400 [thread overview]
Message-ID: <oq1zpetom9.fsf@icule.progiciels-bpi.ca> (raw)
In-Reply-To: "=?iso-8859-5?b?stvQ1Njc2OAgst7b3tLY5w==?="'s message of "14 Sep 1998 22:21:23 +0400"
"Владимир Волович" <vvv@vvv.vsu.ru> writes:
> Best regards, -- Vladimir.
I do not know exactly why, but I love seeing foreign characters in the
author field of the summary buffer. People have the right to their own
name, expressed according to their own culture.
P.S. - This message is also a test. I stopped forcing Latin-1 in MIME
headers, curious to know what pgnus 0.31 will do about it :-)
P.P.S. - Oops! I got "Can't encode messages with multiple charsets (yet)"
Let's try without my signature...
prev parent reply other threads:[~1998-09-14 20:39 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
1998-09-14 18:21 ` Владимир Волович
1998-09-14 20:39 ` François Pinard [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=oq1zpetom9.fsf@icule.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
--cc=ding@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).