comparison etc/PROBLEMS @ 51316:ce710f8e5a48

Correct Unicode stuff.
author Dave Love <fx@gnu.org>
date Thu, 29 May 2003 18:15:21 +0000
parents cd3aedd0c69b
children 12371b18ce00
comparison
equal deleted inserted replaced
51315:7156fc3b3571 51316:ce710f8e5a48
13 problems with the unexec code and its interaction with libSystem.B. 13 problems with the unexec code and its interaction with libSystem.B.
14 14
15 * Characters from the mule-unicode charsets aren't displayed under X. 15 * Characters from the mule-unicode charsets aren't displayed under X.
16 16
17 XFree86 4 contains many fonts in iso10646-1 encoding which have 17 XFree86 4 contains many fonts in iso10646-1 encoding which have
18 minimal character repertoires (whereas the encoding is meant to be a 18 minimal character repertoires (whereas the encoding part of the font
19 reasonable indication of the repertoire). Emacs may choose one of 19 name is meant to be a reasonable indication of the repertoire
20 these to display characters from the mule-unicode charsets and then 20 according to the XLFD spec). Emacs may choose one of these to display
21 typically won't be able to find the glyphs to display many characters. 21 characters from the mule-unicode charsets and then typically won't be
22 (Check with C-u C-x = .) To avoid this, you may need to use a fontset 22 able to find the glyphs to display many characters. (Check with C-u
23 which sets the font for the mule-unicode sets explicitly. E.g. to use 23 C-x = .) To avoid this, you may need to use a fontset which sets the
24 GNU unifont, include in the fontset spec: 24 font for the mule-unicode sets explicitly. E.g. to use GNU unifont,
25 include in the fontset spec:
25 26
26 mule-unicode-2500-33ff:-gnu-unifont-*-iso10646-1,\ 27 mule-unicode-2500-33ff:-gnu-unifont-*-iso10646-1,\
27 mule-unicode-e000-ffff:-gnu-unifont-*-iso10646-1,\ 28 mule-unicode-e000-ffff:-gnu-unifont-*-iso10646-1,\
28 mule-unicode-0100-24ff:-gnu-unifont-*-iso10646-1 29 mule-unicode-0100-24ff:-gnu-unifont-*-iso10646-1
29 30
30 * Encoding some characters as Unicode (UTF-8/16) is rejected by Emacs. 31 * The UTF-8/16/7 coding systems don't encode CJK (Far Eastern) characters.
31 32
32 Emacs currently, by default, only supports the parts of the BMP whose 33 Emacs by default only supports the parts of the Unicode BMP whose code
33 codepoints are in the ranges 0000-33ff and e000-ffff. This excludes 34 points are in the ranges 0000-33ff and e000-ffff. This excludes: most
34 CJK, Yi, Music, Maths, Private Use Area, Gothic, and Old Italic. 35 of CJK, Yi and Hangul, as well as everything outside the BMP.
35 36
36 If you try to save a file containing characters with code points 37 If you read UTF-8 data with code points outside these ranges, the
37 outside this range, Emacs will suggest other compatible coding 38 characters appear in the buffer as raw bytes of the original UTF-8
38 systems. 39 (composed into a single quasi-character) and they will be written back
39 40 correctly as UTF-8, assuming you don't break the composed sequences.
40 By turning Utf-Translate-Cjk mode on, many more CJK characters are 41 If you read such characters from UTF-16 or UTF-7 data, they are
41 included in the support. 42 substituted with the Unicode `replacement character', and you lose
43 information.
44
45 To edit such UTF data, turn on Utf-Translate-Cjk mode, which makes
46 many common CJK characters available for encoding and decoding and can
47 be extended by updating the tables it uses. This also allows you to
48 save as UTF buffers containing characters decoded by the chinese-,
49 japanese- and korean- coding systems, e.g. cut and pasted from
50 elsewhere.
42 51
43 * Problems with file dialogs in Emacs built with Open Motif. 52 * Problems with file dialogs in Emacs built with Open Motif.
44 53
45 When Emacs 21 is built with Open Motif 2.1, it can happen that the 54 When Emacs 21 is built with Open Motif 2.1, it can happen that the
46 graphical file dialog boxes do not work properly. The "OK", "Filter" 55 graphical file dialog boxes do not work properly. The "OK", "Filter"