Gnus development mailing list
 help / color / mirror / Atom feed
From: SL Baur <steve@xemacs.org>
Subject: Re: ~~~ in Pterodactyl Gnus
Date: 29 Aug 1998 16:36:56 -0700	[thread overview]
Message-ID: <m267fbpdgn.fsf@altair.xemacs.org> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "30 Aug 1998 01:14:54 +0200"

[-- Attachment #1: Type: text/plain, Size: 687 bytes --]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes in ding@gnus.org:
> Content-Type: text/plain; charset=iso-8859-1

This should be `iso-2022-jp' as the message contains iso-2022-jp
encoded characters.  Automagically figuring out the charset is one
area that tm is very strong at, so there's probably some code there
to be reused.

The way I composed this message was to add `text/plain' tags around
the line containing Japanese and tm autodetected what charsets to put
in the MIME headers.

> SL Baur <steve@xemacs.org> writes:
>> Subject lines don't appear to be getting the funky MIME quoting, and
>> all I'm seeing the body are tildes.  I'm running XEmacs/Mule in a
>> Japanese locale.

[-- Attachment #2: Type: text/plain, Size: 70 bytes --]

>> In both cases, the three tildes should have read 「日本語」.

[-- Attachment #3: Type: text/plain, Size: 407 bytes --]

> Heh.  In my summary buffer (as well as the Subject line in the article
> buffer), I got three glorious Japanese glyphs, while the last line
> quoted has a jumble of weird characters.  (16 of them.)

Hmm.  The three Japanese glyphs spell `nihongo', Japanese for `Japanese'.
The garbled one is the same, bracketed by square brackets.  Cutting
and pasting the text into Emacs 20.3 works.

Off to try 0.6 ...

  reply	other threads:[~1998-08-29 23:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-29 22:56 日本語 " SL Baur
1998-08-29 23:14 ` ~~~ " Lars Magne Ingebrigtsen
1998-08-29 23:36   ` SL Baur [this message]
1998-08-30 10:02     ` Lars Magne Ingebrigtsen
1998-08-30 15:40 ` 日本語 " Lars Magne Ingebrigtsen

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=m267fbpdgn.fsf@altair.xemacs.org \
    --to=steve@xemacs.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).