|
88740
|
1 -*-text-*-
|
|
|
2
|
|
|
3 Problems, fixmes and other issues in the emacs-unicode branch
|
|
|
4
|
|
88836
|
5 Notes by fx to record various things of variable importance. handa
|
|
|
6 needs to check them -- don't take too seriously, especially with
|
|
|
7 regard to completeness.
|
|
88740
|
8
|
|
88836
|
9 _Do take seriously that you don't want this CVS branch unless you're
|
|
|
10 actually working on it; you'd risk your data._ If you just want to
|
|
|
11 edit Unicode and/or unify iso-8859 et al, see the existing support and
|
|
|
12 the extra stuff at <URL:ftp://dlpx1.dl.ac.uk/fx/emacs/Mule>. Editing
|
|
|
13 support is mostly orthogonal to the internal representation.
|
|
88740
|
14
|
|
|
15 * SINGLE_BYTE_CHAR_P returns true for Latin-1 characters.
|
|
|
16
|
|
|
17 * Grok UTF-8 surrogates.
|
|
|
18
|
|
|
19 * Rationalize character syntax and its relationship to the Unicode
|
|
|
20 database. Specifically, the latin-N.el files aren't consistent for
|
|
|
21 common characters.
|
|
|
22
|
|
|
23 * Fontset handling and customization needs work.
|
|
|
24
|
|
|
25 * Likewise for charset and coding system priorities.
|
|
|
26
|
|
|
27 * The relevant bits of latin1-disp.el need porting (and probably
|
|
|
28 re-naming/updating). See also cyril-util.el.
|
|
|
29
|
|
|
30 * Quail files need work now the encoding is irrelevant. E.g. make
|
|
|
31 unified Latin pre- and post- methods.
|
|
|
32
|
|
|
33 * What to do with the old coding categories stuff?
|
|
|
34
|
|
|
35 * Syntax for symbols &c in characters needs looking at.
|
|
|
36
|
|
|
37 * The preferred-coding-system property of charsets should probably be
|
|
|
38 junked unless it can be made more useful now.
|
|
|
39
|
|
|
40 * find-coding-systems-for-charsets needs re-writing.
|
|
|
41
|
|
|
42 * find-multibyte-characters needs looking at.
|
|
|
43
|
|
|
44 * Implement Korean cp949/UHC and any other important missing
|
|
|
45 charsets.
|
|
|
46
|
|
|
47 * Check up on tcvn and alternativnj.
|
|
|
48
|
|
|
49 * Lazy-load tables for unify-charset somehow?
|
|
|
50
|
|
88836
|
51 * Translation tables for {en,de}code currently aren't supported.
|
|
88740
|
52
|
|
|
53 * Defining CCL coding systems currently doesn't work.
|
|
|
54
|
|
|
55 * iso-2022 charsets get unified on i/o.
|
|
|
56
|
|
|
57 * Revisit locale processing: look at treating the language and
|
|
|
58 charset parts separately. (Language should affect things like
|
|
|
59 speling and calendar, but that's not a Unicode issue.)
|
|
|
60
|
|
|
61 * Handle Unicode combining characters usefully, e.g. diacritics, and
|
|
|
62 handle more scripts specifically (á la Devanagari). There are
|
|
|
63 issues with canonicalization.
|
|
|
64
|
|
88836
|
65 * Bidi is a separate issue with no support currently.
|
|
88740
|
66
|
|
|
67 * DTRT with X keysyms. We should get the right unicode for a given
|
|
|
68 keysym, not decode raw bytes in some ill-defined coding system.
|
|
|
69 (fx has some data on keysyms v. unicodes.)
|
|
|
70
|
|
|
71 * We need tabular input methods, e.g. for maths symbols. (Not
|
|
|
72 specific to Unicode.)
|
|
|
73
|
|
|
74 * Need multibyte text in menus, e.g. for the above. (Not specific to
|
|
|
75 Unicode.)
|
|
88836
|
76
|
|
|
77 * Still can't have case pairs which have different byte lengths --
|
|
|
78 can that be fixed for Turkish, at least?
|
|
|
79
|
|
|
80 * There's currently no support for Unicode normalization.
|
|
|
81
|
|
|
82 * You can grep the code for lots of fixmes.
|
