- -*-text-*-
+ -*-mode: text; coding: latin-1;-*-
Problems, fixmes and other issues in the emacs-unicode branch
-------------------------------------------------------------
(Editing support is mostly orthogonal to the internal representation.)
* SINGLE_BYTE_CHAR_P returns true for Latin-1 characters, which has
- undesirable effects.
+ undesirable effects. E.g.:
+ (multibyte-string-p (let ((s "x")) (aset s 0 ?£) s)) => nil
+ (multibyte-string-p (concat [?£])) => nil
+ (text-char-description ?£) => "M-#"
+
+ These examples are all fixed by the change of 2002-10-14, but
+ there still exist questionalble SINGLE_BYTE_CHAR_P in the
+ code (keymap.c and print.c).
* Rationalize character syntax and its relationship to the Unicode
- database. Specifically, the latin-N.el files aren't consistent for
- common characters (and obviously have redundancies except in
- unibyte mode).
+ database. (Applies mainly to symbol an punctuation syntax.)
* Fontset handling and customization needs work. We want to relate
fonts to scripts, probably based on the Unicode blocks. The
presence of small-repertoire 10646-encoded fonts in XFree 4 is a
pain, not currently worked round.
+ With the change on 2002-07-26, multiple fonts can be
+ specified in a fontset for a specific range of characters.
+ Each range can also be specified by script. Before using
+ ISO10646 fonts, Emacs checks their repertories to avoid such
+ fonts that don't have a glyph for a specific character.
+
+ fx has worked on fontset customization, but was stymied by
+ basic problems with the way the default face is dealt with
+ (and something else, I think). This needs revisiting.
+
* Work is also needed on charset and coding system priorities.
* The relevant bits of latin1-disp.el need porting (and probably
re-naming/updating). See also cyril-util.el.
- * Quail files need more work now the encoding is irrelevant.
+ * Quail files need more work now the encoding is largely irrelevant.
* What to do with the old coding categories stuff?
- * Syntax for symbols &c in characters.el needs looking at.
-
* The preferred-coding-system property of charsets should probably be
junked unless it can be made more useful now.
- * find-coding-systems-for-charsets needs re-writing or removing.
-
* find-multibyte-characters needs looking at.
- * Implement Korean cp949/UHC and any other important missing
+ * Implement Korean cp949/UHC, BIG5-HKSCS and any other important missing
charsets.
- * Check up on definitions of tcvn and alternativnj.
-
* Lazy-load tables for unify-charset somehow?
+ Actually, Emacs clear out all charset maps and unify-map just
+ before dumping, and their are loaded again on demand the
+ dumped emacs. But, those maps (char tables) generated while
+ temacs is running can't be get rid of from the dumped emacs.
+
* Translation tables for {en,de}code currently aren't supported.
+ This should be fixed by the changes of 2002-10-14.
+
* Defining CCL coding systems currently doesn't work.
+ This should be fixed by the changes of 2003-01-30.
+
* iso-2022 charsets get unified on i/o.
+ With the change on 2003-01-06, decoding routines put `charset'
+ property to decoded text, and iso-2022 encoder pay attention
+ to it. Thus, for instance, reading and writing by
+ iso-2022-7bit preserve the original designation sequences.
+ The property name `preferred-charset' may be better?
+
+ We may have to utilize this property to decide a font.
+
* Revisit locale processing: look at treating the language and
charset parts separately. (Language should affect things like
speling and calendar, but that's not a Unicode issue.)
* Bidi is a separate issue with no support currently.
- * DTRT with X keysyms. We should get the right unicode for a given
- keysym, not decode raw bytes in some ill-defined coding system.
- (fx has some data on keysyms v. unicodes.)
-
* We need tabular input methods, e.g. for maths symbols. (Not
specific to Unicode.)
* Need multibyte text in menus, e.g. for the above. (Not specific to
- Unicode.)
-
- * Still can't have case pairs which have different byte lengths --
- can that be fixed for Turkish, at least?
+ Unicode -- see Emacs etc/TODO, but now mostly works with gtk.)
* There's currently no support for Unicode normalization.
* Emacs 20/21 .elc files are currently not loadable. It may or may
not be possible to do this properly.
- * Encoding issues in babyl files/rmail need sorting out.
+ With the change on 2002-07-24, elc files generated by Emacs
+ 20.3 and later are correctly loaded (including those
+ containing multibyte characters and compressed). But, elc
+ files generated by 20.2 and the primer are still not loadable.
+ Is it really worth working on it?
+
+ * Rmail won't work with non-ASCII text. Encoding issues for Babyl
+ files need sorting out, but rms says Babyl will go before this is
+ released.
* Gnus still needs some attention, and we need to get changes
accepted by Gnus maintainers...
+ * There are type errors lurking, e.g. in
+ Fcheck_coding_systems_region. Define ENABLE_CHECKING to find them.
+
* You can grep the code for lots of fixmes.
+
+ * Old auto-save files, and similar files, such as Gnus drafts,
+ containing non-ASCII characters probably won't be re-read correctly.