; * etc/PROBLEMS: Add entry about XIM problems (bug#65205).
This commit is contained in:
parent
03e897c08f
commit
99367078e5
1 changed files with 10 additions and 37 deletions
47
etc/PROBLEMS
47
etc/PROBLEMS
|
@ -1177,43 +1177,6 @@ do anything about it.
|
|||
|
||||
** International characters aren't displayed under X.
|
||||
|
||||
*** Missing X fonts
|
||||
|
||||
XFree86 4 contains many fonts in iso10646-1 encoding which have
|
||||
minimal character repertoires (whereas the encoding part of the font
|
||||
name is meant to be a reasonable indication of the repertoire
|
||||
according to the XLFD spec). Emacs may choose one of these to display
|
||||
characters from the mule-unicode charsets and then typically won't be
|
||||
able to find the glyphs to display many characters. (Check with C-u
|
||||
C-x = .) To avoid this, you may need to use a fontset which sets the
|
||||
font for the mule-unicode sets explicitly. E.g. to use GNU unifont,
|
||||
include in the fontset spec:
|
||||
|
||||
mule-unicode-2500-33ff:-gnu-unifont-*-iso10646-1,\
|
||||
mule-unicode-e000-ffff:-gnu-unifont-*-iso10646-1,\
|
||||
mule-unicode-0100-24ff:-gnu-unifont-*-iso10646-1
|
||||
|
||||
** The UTF-8/16/7 coding systems don't encode CJK (Far Eastern) characters.
|
||||
|
||||
Emacs directly supports the Unicode BMP whose code points are in the
|
||||
ranges 0000-33ff and e000-ffff, and indirectly supports the parts of
|
||||
CJK characters belonging to these legacy charsets:
|
||||
|
||||
GB2312, Big5, JISX0208, JISX0212, JISX0213-1, JISX0213-2, KSC5601
|
||||
|
||||
The latter support is done in Utf-Translate-Cjk mode (turned on by
|
||||
default). Which Unicode CJK characters are decoded into which Emacs
|
||||
charset is decided by the current language environment. For instance,
|
||||
in Chinese-GB, most of them are decoded into chinese-gb2312.
|
||||
|
||||
If you read UTF-8 data with code points outside these ranges, the
|
||||
characters appear in the buffer as raw bytes of the original UTF-8
|
||||
(composed into a single quasi-character) and they will be written back
|
||||
correctly as UTF-8, assuming you don't break the composed sequences.
|
||||
If you read such characters from UTF-16 or UTF-7 data, they are
|
||||
substituted with the Unicode 'replacement character', and you lose
|
||||
information.
|
||||
|
||||
** Accented ISO-8859-1 characters are displayed as | or _.
|
||||
|
||||
Try other font set sizes (S-mouse-1). If the problem persists with
|
||||
|
@ -1251,6 +1214,16 @@ In your ~/.Xresources file, then run
|
|||
|
||||
And restart Emacs.
|
||||
|
||||
** Emacs hangs when using XIM
|
||||
|
||||
This is due to an old bug in the implementation of the X protocol's
|
||||
XIM transport: when an input method crashes for some reason, Xlib
|
||||
cannot recover. Emacs cannot do anything about this except wait for
|
||||
the I-Bux developers to fix their crashes. You can work around these
|
||||
problems by disabling XIM in your X resources:
|
||||
|
||||
Emacs.useXIM: false
|
||||
|
||||
** On Haiku, BeCJK doesn't work properly with Emacs
|
||||
|
||||
Some popular Haiku input methods such BeCJK are known to behave badly
|
||||
|
|
Loading…
Add table
Reference in a new issue