Re: Attention Mule users...

Please don't remove any code you don't understand, just comment it out. (That seems to be what you're doing anyway, but I' like to encourage it. Also if when you comment something out, it would help if you leave an "; XEmacs change - Your Name <user(a)org.tld&gt;&quot; comment there so I can ask later why something was done if it's not clear. It'll be a while before I can take a close look at the Mule stuff here. :-( Jan> [What was the exact problem here (I don't have a mule-build Jan> handy). :-( Jan> Is "mule-version" not defined on our mule build does Jan> it not have the right value] We don't have the variable. I don't know what it means, anyway; it's not discussed on the public Mule lists. Jan> Ok, we simply have no Ethoipic support Not entirely true. But I'll take care of it later; please don't remove the code, that's all. Jan> Hmm.. Do we have a slight API incompatibility here, i.e. can Jan> we not take a coding system name in encode-coding-string? Jan> Anyway, it just another minor problem. I'll look at this. Jan> I think is again just a misguided FSF-specific mule test This bothers me; that variable should exist and always be true in Mule, always false in no-mule. I think we should enforce this. Jan> I think was the essential bit... FSF Emacs has a whole bunch Jan> of different names for coding systems. Sigh. I wish they would cut this out. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."