From: Yoshiki Hayashi <yoshiki@xemacs.org>
Cc: Gnus List <ding@gnus.org>
Subject: Re: detecting encoding for Japanese
Date: Wed, 11 Sep 2002 19:40:46 +0900 [thread overview]
Message-ID: <87n0qoolld.fsf@u.sanpo.t.u-tokyo.ac.jp> (raw)
In-Reply-To: <iluit1smxu2.fsf@latte.josefsson.org> (Simon Josefsson's message of "Fri, 30 Aug 2002 12:43:01 +0200")
Simon Josefsson <jas@extundo.com> writes:
>>> Or where you asking for a new feature where Gnus used Emacs' builtin
>>> AI to guess what encoding untagged data? That could perhaps work,
>>> but I don't know how to implement it.
>>
>> Probably that is indeed what I was asking for. GNU Emacs indeed seems
>> to know how to guess encoding when a file is visited. The 1g command
>> suggested by you (and Kai, thanks) helps, but presumes I know the
>> encoding before switching. As time permits, I'll have a look at the
>> "builtin AI".
>
> Yes, using the builtin AI for untagged messages seems like the best
> compromise.
I haven't used Oort so I may be missing something but can't
you simply specify 'undecided' in gnus-group-charset-alist
instead of iso-2022-jp?
--
Yoshiki Hayashi
prev parent reply other threads:[~2002-09-11 10:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 5:48 Hal Snyder
2002-08-29 10:00 ` Kai Großjohann
2002-08-29 12:04 ` Simon Josefsson
2002-08-29 14:08 ` Hal Snyder
2002-08-29 16:01 ` Simon Josefsson
2002-08-29 16:24 ` Hal Snyder
2002-08-29 16:59 ` Kai Großjohann
2002-08-30 0:05 ` Katsumi Yamaoka
2002-08-30 12:23 ` Kai Großjohann
2002-09-02 12:16 ` Katsumi Yamaoka
2002-09-02 17:31 ` Kai Großjohann
2002-09-02 22:38 ` Katsumi Yamaoka
2002-09-03 1:52 ` Katsumi Yamaoka
2002-09-03 2:03 ` Katsumi Yamaoka
2002-09-03 6:19 ` Katsumi Yamaoka
2002-09-03 6:43 ` Katsumi Yamaoka
2002-09-03 21:43 ` Hal Snyder
2002-09-03 22:09 ` Kai Großjohann
2002-08-30 10:43 ` Simon Josefsson
2002-08-30 12:25 ` Kai Großjohann
2002-08-30 22:58 ` Hal Snyder
2002-09-11 10:40 ` Yoshiki Hayashi [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=87n0qoolld.fsf@u.sanpo.t.u-tokyo.ac.jp \
--to=yoshiki@xemacs.org \
--cc=ding@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).