GNU bug report logs -
#6866
mule-cmds.el just _assumes_ all of Taiwan uses Big5 and not UTF-8
Previous Next
Reported by: jidanni <at> jidanni.org
Date: Mon, 16 Aug 2010 12:03:02 UTC
Severity: normal
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #34 received at 6866-done <at> debbugs.gnu.org (full text, mbox):
> From: jidanni <at> jidanni.org
> Date: Mon, 16 Aug 2010 21:39:10 +0800
> Cc: 6866 <at> debbugs.gnu.org
>
> Well anyway, for our locale me and my friends all use zh_TW.UTF-8 and
> stopped using zh_TW.big5 years ago. So at least it looks very dumb there
> in mule-cmds.el that the zh_CN people can use UTF-8, but the HK and TW
> are locked in the dark ages:
>
> ("zh_HK" . "Chinese-Big5")
> ("zh_TW" . "Chinese-Big5")
> ("zh_CN.UTF-8" . "Chinese-GBK")
> ("zh_CN" . "Chinese-GB")
Are you sure you understand what this data base is used for in Emacs?
The function within mule-cmds.el which uses this data has this
comment:
;; locale-language-names specify both lang-env and coding.
;; But, what specified in locale-preferred-coding-systems
;; has higher priority.
Thus, if you specify UTF-8 as the preferred encoding (e.g., via
LC_ALL), it overrules the Big5 default.
> The only big5 thing I apparently sometimes still use is
> $ GET http://jidanni.org/comp/configuration/.emacs | grep -i b5
> (setq default-input-method 'chinese-py-punct-b5))));no 'utf' ones
You are confused: an input method can produce Big5 characters, but
that won't prevent Emacs from encoding them in UTF-8 if that's your
preference.
I'm closing this bug.
This bug report was last modified 14 years and 343 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.