>>>> "Ben" == Ben Wing <ben(a)666.com>
Ben>  what do we do about translating the stuff into the
Ben> internal format when we read it in?
> We don't worry about it.
Ben> What I'm concerned about is Mule, not non-Mule. If we have
Ben> UTF-8 elisp files, then what do we do when we read in a UTF-8
Ben> string in a .elc file under Mule? Which charset do we
I still think this is basically a non-problem. If it's Asian, assume
Japanese, since (with the exception of ./etc/hello and the input
methods) I don't think we distribute anything that's non-Japanese with
kanji in it.
In the input method files, we do a set-unicode-priority or whatever
that API is, this should work for everything in LEIM. But most
non-Asian language users use window-system input methods where
Ben> If we switch to UTF-8 internally, this problem goes away.
Yes, for the elisp, but then we have to deal with the larger domain
where we don't have a font model for Unicode yet, except on MS
BTW, savannah is down, at least from here, so I don't know when I'll
get a look at the emacs-unicode branch.
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.