Katsumi Yamaoka writes:
Stephen J. Turnbull wrote:
> You probably shouldn't do that, although
> (push (file-name-as-directory (expand-file-name "mule" lispdir)))
> in site-start.el will do the trick.
I tried it. Thanks. But it doesn't help XEmacs 21.5-b29 that
runs with the -no-autoloads option in the Japanese locale.
Why are you running with -no-autoloads in a Japanese locale? I think
this is a very bad idea, anyway. The kinds of situations where
-no-autoloads makes sense (ie, building XEmacs or the packages) really
ought to be running in the POSIX locale, and using only Mule
facilities for internationalization.
How about moving japan-util.el in mule-base to XEmacs 21.4? ;-)
Talk to Vin about that, but I think it's a bad idea. We should fix
the thing and move it back out of 21.5. It's really ugly that any
language-specific support is in the core, IMO. In 21.5, we should
suppress locale-based language environment setting when running
-vanilla, as well as other user settings like the init file. It's
reasonable to set various coding systems to match the locale, but
that's as far as it should go until we get localized messages.
I think it is desirable that the packages are usable with both
XEmacs 21.4 and 21.5.
The packages in general do work with both if compiled by 21.4. The
current problem is due to a bad design decision to try to support the
same module in two different places in the same XEmacs, not to
packages failing to work in both.
XEmacs-Beta mailing list