Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Huh...? euc-jp...?
Date: Fri, 24 Feb 2006 20:37:08 +0900	[thread overview]
Message-ID: <b4mk6blq97f.fsf@jpl.org> (raw)
In-Reply-To: <87oe0x5fb5.fsf@dod.no>

>>>>> In <v964n5sqsr.fsf@marauder.physik.uni-ulm.de> Reiner Steib wrote:

> As Emacs 21 cannot do CJK->UTF-8 unification, Emacs is unable to
> convert the chars to UTF-8.  There's nothing Gnus can do about this.

I could reproduce the euc-jp problem using Emacs 21 in the
German language environment, and probably I could solve it using
Mule-UCS[1] and setting the `mm-coding-system-priorities'
variable as follows:

(setq mm-coding-system-priorities '(iso-8859-1 utf-8)) ;; [2]

> In Emacs 22 it works correctly (see `utf-translate-cjk-mode' in the
> NEWS file):

Yes, I think it is better to use Emacs 22 and I don't recommend
Mule-UCS so aggressively (note that Mule-UCS is generally
useless and somewhat harmful to Emacs 22).

[1] The official release is:
  ftp://ftp.m17n.org/pub/mule/Mule-UCS/Mule-UCS-0.84.tar.gz

The following one might not be latest but is pretty new:
  http://www.jpl.org/ftp/pub/tmp/Mule-UCS-0.85-20040906.tar.gz
  or ftp://ftp.jpl.org/pub/tmp/Mule-UCS-0.85-20040906.tar.gz

[2] Perhaps it is necessary to use a better value than that.

>>>>> In <87oe0x5fb5.fsf@dod.no> Steinar Bang wrote:

> Hm... ubuntu, which I'm using, is a variant of debian.

Emacsen I'm using are the ones all I built by myself in the
Fedora Core 4 system.



      reply	other threads:[~2006-02-24 11:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23 20:57 Steinar Bang
2006-02-23 21:34 ` Reiner Steib
2006-02-24  8:30   ` Steinar Bang
2006-02-24 11:37     ` Katsumi Yamaoka [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=b4mk6blq97f.fsf@jpl.org \
    --to=yamaoka@jpl.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).