From: Simon Josefsson <simon@josefsson.org>
To: Karl Chen <quarl@cs.berkeley.edu>
Cc: ding@gnus.org
Subject: Re: charset ANSI_x3.4-1968, et al
Date: Mon, 19 Mar 2007 09:45:12 +0100 [thread overview]
Message-ID: <87hcshwrjb.fsf@mocca.josefsson.org> (raw)
In-Reply-To: <quack.20070318T1657.lthzm6ayujj@roar.cs.berkeley.edu> (Karl Chen's message of "Sun\, 18 Mar 2007 16\:57\:20 -0700")
Karl Chen <quarl@cs.berkeley.edu> writes:
>>>>>> On 2007-03-18 12:54 PDT, Simon Josefsson writes:
>
> Simon> RFC 1345 is not standards-track, but the IANA registry
> Simon> is used by the standards-track MIME.
>
> Good point about standards-track-ness. But, regardless of whether
> it's officially "okay", I would recommend /accepting/ (not
> sending) the ANSI_x3.4-1968 string: "Be liberal in what you
> accept, conservative in what you send." There are already
> implementations "in the wild" sending it (perhaps incorrectly, but
> still, it's out there) -- Fedora, Debian, and presumably their
> derivatives.
Yes, I agree.
> >> [1] This is now happening on multiple systems (which are
> >> all Debian). cron appears to be using the default locale
> >> name. On Linux, you can get the string ANSI_x3.4-1968 if
> >> you run "LC_CTYPE=C locale charmap".
>
> Simon> I think this should be reported as a bug.
>
> Yup, on the "conservative in what you send" side of it, I also
> sent them patch after I emailed ding@.
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=415302
Thanks!
/Simon
prev parent reply other threads:[~2007-03-19 8:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 1:41 Karl Chen
2007-03-18 19:54 ` Simon Josefsson
2007-03-18 22:54 ` Reiner Steib
2007-03-19 0:02 ` Karl Chen
2007-03-19 8:43 ` Simon Josefsson
2007-03-20 7:50 ` Karl Chen
2007-03-20 8:35 ` Simon Josefsson
2007-03-21 4:06 ` Karl Chen
2007-03-18 23:57 ` Karl Chen
2007-03-19 8:45 ` Simon Josefsson [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=87hcshwrjb.fsf@mocca.josefsson.org \
--to=simon@josefsson.org \
--cc=ding@gnus.org \
--cc=quarl@cs.berkeley.edu \
/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).