XEmacs doesn't support windows-1252

[Mike FABIAN]

Aidan Kehoe <kehoea at parhasard.net> さんは書きました:

> For what you’re looking for,
> it is enough to put a call to that function in startup.el, after the call to
> init-mule-at-startup and before the window system initialisation code. For
> reference, the patch I tested that with is below; I tested it with an XEmacs
> that had a windows-1252 coding system with the non-Latin-1 characters mapped
> into the jit-ucs-charset-0 character set.

This patch works well for me.

I still get

    (split-char ?”) 
    (latin-iso8859-16 53) 

when typing ” into a terminal frame (gnuclient -nw) but in
an X-frame I now get 

    (split-char ?”)
    (jit-ucs-charset-0 33 88)

and I get the same result when displaying e-mails using
charset=windows-1252 with Gnus.

Therefore, the problem that ” was treated as a double width character
and caused problems when typing in a terminal (which treated is as
single width) is gone, ” is always treated as single width now.

> (If you’re planning on distributing code with that Windows-1252 coding
> system, by the way, you will also want the change in
> http://mid.gmane.org/18091.3408.152729.823883@parhasard.net )

Thank you!

> Index: startup.el
> ===================================================================
> RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/startup.el,v
> retrieving revision 1.58
> diff -u -u -r1.58 startup.el
> --- startup.el	2007/05/25 15:47:56	1.58
> +++ startup.el	2007/07/28 09:08:23
> @@ -713,6 +713,9 @@
>        (when (featurep 'mule)
>  	(declare-fboundp (init-mule-at-startup)))
>  
> +      (set-language-unicode-precedence-list  
> +       '(ascii latin-iso8859-1 latin-iso8859-2 latin-iso8859-3 latin-iso8859-4 jit-ucs-charset-0 thai-tis620 greek-iso8859-7 arabic-iso8859-6 hebrew-iso8859-8 katakana-jisx0201 latin-jisx0201 cyrillic-iso8859-5 latin-iso8859-9 latin-iso8859-15 composite control-1 japanese-jisx0208-1978 chinese-gb2312 japanese-jisx0208 korean-ksc5601 japanese-jisx0212 chinese-cns11643-1 chinese-cns11643-2 chinese-big5-1 chinese-big5-2 arabic-digit arabic-1-column arabic-2-column chinese-sisheng latin-iso8859-16 indian-is13194 lao latin-iso8859-14 ipa vietnamese-viscii-upper vietnamese-viscii-lower jit-ucs-charset-0 chinese-cns11643-3 chinese-cns11643-4 chinese-cns11643-5 chinese-cns11643-6 chinese-cns11643-7 chinese-isoir165 ethiopic indian-2-column indian-1-column japanese-jisx0213-1 japanese-jisx0213-2 thai-xtis tibetan tibetan-1-column))
> +
>        (if (featurep 'toolbar)
>  	  (if (featurep 'infodock)
>  	      (require 'id-x-toolbar)

Is there any disadvantage of doing that?

Will that be committed to CVS?

-- 
Mike FABIAN   <mfabian at suse.de>   http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
I � Unicode