On Fri, Nov 14, 2008 at 11:04:02AM +0000, Julian Bradfield wrote:
Nothing, and that was my first thought. But then I thought that
would have the advantage of making it easy to load the translation tables
on demand - why should I have 20MB (or however much it is) of
translation tables in main memory of every XEmacs instance, when my
typical instance only ever sees Latin-1 and maybe few dozen hanzi?
If memory is your problem, I'm pretty sure that you can dump them to C
and make them fit in less than a read-only, shareable, load-on-demand
megabyte without any special effort. The iso-8859, jisx, gb, cns etc
mappings are not going to change any time soon once they're
The #1 problem I've seen with real unicode support on unix is the
rendering, specifically the font selection, especially when you want
to still be able to reach the bitmap fonts. I don't think
fontconfig/xft allows to reach them, it's written by
anti-aliased-vector-fonts integrists who consider their use is the
only one relevant. And that documentation is for wimps, and
"deprecated" and "stubbed" are synonyms.
 I can't work without
-Misc-MiscFixed-Medium-R-Normal--10-100-75-75-C-60-*, but I can stand
using a different name as long as the glyph rendering is identical.
XEmacs-Beta mailing list