Aidan Kehoe <kehoea(a)parhasard.net> さんは書きました:
Ar an naoú lá déag de mí Eanair, scríobh Mike FABIAN:
> It is probably not possible to handle U+00B1 as double width in XEmacs
> and handle German Umlauts as single width at the same time.
“Handle” is a bit ambiguous there. All the following characters are distinct
within XEmacs, but identical in Unicode (select the expression and press C-x
C-e to see how your XEmacs displays them):
(format "%c %c %c %c %c %c %c %c"
(make-char 'latin-iso8859-1 #xfc)
(make-char 'latin-iso8859-14 #xfc)
(make-char 'latin-iso8859-15 #xfc)
(make-char 'latin-iso8859-2 #xfc)
(make-char 'latin-iso8859-3 #xfc)
(make-char 'latin-iso8859-9 #xfc)
(make-char 'chinese-gb2312 #x28 #x39)
(make-char 'japanese-jisx0212 #x2b #x64))
So you can certainly have a double-width ü at the same time as a
single-width ü, within a single XEmacs :-) .
Yes, I know. Of course I already noticed. This causes *very* strange
effects. Before I forced all German Umlauts to single width using
'set-language-unicode-precedence-list' as you kindly explained to me,
I had the following strange behavior:
- an 'ü' typed via the X11 Compose mechanism was inserted as single
width
- an 'ü' typed via XIM using SCIM as the XIM server and
selecting M17N-t-latn-pre as the input method was inserted as
double width.
On top of that of course it often happens that People have various
kinds of 'ü' in a buffer, some read from a file and some just typed
via whatever input method which happens to insert another variant of
'ü'. and when searching for 'ü' with C-s only some of them are
matched, although they may be displayed with the same font and are
visually indistinguishable.
Now, it’s evident that the first six should be unified,
YES!
but less so that a Japanese X11 user will prefer that the system’s
ISO 8859-1 font(s) be used for the character, if the available JISX
0212 fonts are more comprehensive and aesthetically pleasing than
the available ISO 8859-1 fonts, or if the character is in the middle
of a stretch of Japanese text.
I don't think so in case of a German 'ü'. Usually 'ü' doesn't
come
alone, usually it is part of a German word. It looks awkward if the ü
and the ß in "Grüße" are double width and the neighboring ASCII
characters are double width.
No such problem with Greek and Russian because for Greek and Russian
all characters *could* be handled as double width. But I think one
gets more aesthetically pleasing results by embedding them as single
width into Japanese text. When writing with a plain text editor
optionally using a single width space at the borders between Japanese
and foreign text. When looking at Japanese printed material, the
foreign words embedded into the Japanese text are usually printed
using a proportional font where the glyphs are much narrower than a
Japanese kanji, i.e. which is much closer to single width than to
double width. When editing a plain text using an editor with a
monospaced font, you are much closer to the appearance of typical
printed Japanese by using single width fonts for the foreign words.
When trying to embed "Grüße" completely as double width into Japanese
plain text edited in XEmacs, one you could achieve that only by using
the double width forms of the English characters (U+FF21 to U+FF5A in
Unicode) and combine these with the 'ü' and 'ß'. If you save such a
file is saved and then displayed with any other program than XEmacs,
one would see single width 'ü' and 'ß' in between the double width
English characters, which is not nice at all.
I think an ü is an ü is an ü and one is already more than enough,
there should be no different variants of ü's.
--
Mike FABIAN <mfabian(a)suse.de>
http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。