Re: detecting encoding for Japanese

[Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> So, I recommend Japanese Gnus users customize the option
> `mm-coding-system-priorities' to have popular Japanese charsets
> as follows:
>
> (setq mm-coding-system-priorities
>       '(iso-2022-jp iso-2022-jp-2 japanese-shift-jis utf-8))

Why are euc-jp and euc-jisx0213 missing from this list?  (Maybe they
are different names for an encoding already in the above list?)

Also, if the above change is good for Japanese users, why isn't it
good for everybody else, too?  Do you think that there are
non-Japanese out there who prefer the current behavior?

Maybe it is a good idea to put your change in Gnus.

(Hm.  I wonder what happens for Chinese.  I think that nothing much
will happen, but in case that a Chinese sends their messages in a
Japanese encoding, they would be surprised :-)  I think that Mule
cannot unify Chinese and Japanese characters, so this can never
happen.  But I'm not so sure about Mule, so I'd better ask.)

Another thought: Mule itself also has a priority list of encodings.
So I wonder why does Gnus need another priority list?  Normally, I'd
guess that Japanese would normally configure their Emacs for the right
priorities, and then Gnus should do the right thing automatically.
There could be two reasons why this is not happening: (1) Japanese use
a different encoding in email than in editing files, or (2) the
priorities that Emacs sets up normally do not propagate properly to
Gnus, or (3) Emacs does not set itself up for the right priorities at
all when users setup a Japanese language environment.  Yes, I can't
count...

kai (no email access over the weekend)
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)