comparison README.unicode @ 89332:2ffdae6aec84

*** empty log message ***
author Kenichi Handa <handa@m17n.org>
date Mon, 06 Jan 2003 12:24:13 +0000
parents d2c6faa9211a
children b185a90cd78f
comparison
equal deleted inserted replaced
89331:1892a75ffcac 89332:2ffdae6aec84
70 70
71 * Defining CCL coding systems currently doesn't work. 71 * Defining CCL coding systems currently doesn't work.
72 72
73 * iso-2022 charsets get unified on i/o. 73 * iso-2022 charsets get unified on i/o.
74 74
75 With the change on 2003-01-06, decoding routines put `charset'
76 property to decoded text, and iso-2022 encoder pay attention
77 to it. Thus, for instance, reading and writing by
78 iso-2022-7bit preserve the original designation sequences.
79 The property name `preferred-charset' may be better?
80
81 We may have to utilize this property to decide a font.
82
75 * Revisit locale processing: look at treating the language and 83 * Revisit locale processing: look at treating the language and
76 charset parts separately. (Language should affect things like 84 charset parts separately. (Language should affect things like
77 speling and calendar, but that's not a Unicode issue.) 85 speling and calendar, but that's not a Unicode issue.)
78 86
79 * Handle Unicode combining characters usefully, e.g. diacritics, and 87 * Handle Unicode combining characters usefully, e.g. diacritics, and