|
From: | David De La Harpe Golden |
Subject: | Re: X11 Compound Text vs ISO 2022 |
Date: | Wed, 07 Jul 2010 02:15:03 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100620 Icedove/3.0.5 |
On 07/07/10 00:38, David De La Harpe Golden wrote:
> A number of characters are output in '^[$-1'; such as: > (encode-coding-string "ℜ" 'compound-text) ; U+211C BLACK-LETTER CAPITAL R > "^[$-1\365\334^[-A" > (encode-coding-string "ʻ" 'compound-text) ; U+02BB MODIFIER LETTER TURNED COMMA > "^[$-1\244\333^[-A" > That is encoded in mule-unicode-0100-24ff, essentially unknown outside > Emacs. But actually I think emacs should be using using coding system compound-text-with-extensions by default, not coding system compound-text? At least if you haven't customized selection-coding-system.
Well, that probably "solves" one thing, but what about the use of JIS X 0213The definition of coding systems compound-text and compound-text-with-extensions say (around line 1445 of lisp/international/mule-conf.el):
:charset-list 'iso-2022Which accoding to define-coding-system doc means it thinks compound-text supports "all iso-2022 charsets"...
So maybe it could/should be trimmed to only those iso-2022 charsets in the compound text spec, though I'm not sure that naively adjusting :charset-list will work right, especially for compound-text-with-extensions (I just managed to segfault emacs playing with it).
[Prev in Thread] | Current Thread | [Next in Thread] |