From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: ÆØÅ -- QP in subject
Date: 19 Apr 2001 17:03:29 +0200 [thread overview]
Message-ID: <rju23lylry.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <87zodd5506.fsf@ait.uran.ru> (Dmitry Paduchih's message of "19 Apr 2001 20:38:33 +0600")
Dmitry Paduchih <paduch@imm.uran.ru> writes:
> Well, probably it is a bad idea... But it would be worse idea to use
> unencoded UTF8 in the newsgroup or a mailing list where nobody uses it...
Yes, in the transition period using MIME encoded headers is the least
bad option.
next prev parent reply other threads:[~2001-04-19 15:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 10:25 Thomas Skogestad
2001-04-19 10:44 ` Kai Großjohann
2001-04-19 11:04 ` Thomas Skogestad
2001-04-19 11:09 ` Kai Großjohann
2001-04-19 11:47 ` Per Abrahamsen
2001-04-19 14:38 ` Dmitry Paduchih
2001-04-19 15:03 ` Per Abrahamsen [this message]
2001-04-19 16:00 ` Dmitry Paduchih
2001-04-20 1:30 ` Doug Alcorn
2001-04-20 14:19 ` Charles Sebold
2001-04-19 13:12 ` Dmitry Paduchih
2001-04-19 14:02 ` Kai Großjohann
2001-04-19 11:57 ` Bjørn Mork
2001-04-19 12:08 ` Thomas Skogestad
2001-04-19 12:32 ` Florian Weimer
2001-04-19 16:42 ` Dmitry Paduchih
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=rju23lylry.fsf@ssv2.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).