From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: rfc2047-default-charset?
Date: 17 Oct 1998 23:48:32 +0200 [thread overview]
Message-ID: <m3zpauvozz.fsf@sparky.gnus.org> (raw)
In-Reply-To: Simon Josefsson's message of "16 Oct 1998 17:01:49 +0200"
Simon Josefsson <jas@pdc.kth.se> writes:
> rfc2047-default-charset defaults to 'iso-8859-1, which result in
> headers containing characters with this encoding is not rfc2047
> ("encoded word") encoded.
>
> What are the reasoning behind the default?
People in some locales will want to use a local character set as the
default character set. This logic is a bit sketchy to me at this
point, and I don't think this belongs in the rfc2047-* realm, in any
case, so I'll probably move this out somewhere else after thinking
some more about these things.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-10-17 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-16 15:01 rfc2047-default-charset? Simon Josefsson
1998-10-17 21:48 ` Lars Magne Ingebrigtsen [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=m3zpauvozz.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).