From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: `mm-mule-charset-to-mime-charset' don't use iso-2022-jp-2
Date: 04 Jul 1999 04:52:52 +0200 [thread overview]
Message-ID: <m3wvwhktx7.fsf@quimbies.gnus.org> (raw)
In-Reply-To: "Petersen Jens-Ulrik's message of "24 Jun 1999 16:57:15 +0900"
"Petersen Jens-Ulrik (NRC/Tokyo)" <jens-ulrik.petersen@nokia.com> writes:
> I think iso-2022-jp-2 should be replaced by iso-2022-jp in
> `mm-mule-charset-to-mime-charset'? I think that is the right thing to
> do. I believe mew also uses iso-2022-jp, which is the standard
> charset for mail/news in Japan.
Err... I just applied a patch that did it the other way around --
iso-2022-jp-2 replaced iso-2022-jp. I don't know one way or the
other.
Help?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-07-04 2:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-24 7:57 Petersen Jens-Ulrik (NRC/Tokyo)
1999-07-04 2:52 ` 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=m3wvwhktx7.fsf@quimbies.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).