>>>>> "Ben" == Ben Wing <ben(a)666.com&gt; writes: Ben> "Michael Sperber [Mr. Preprocessor]" wrote: >> I apologize for missing this earlier. >> >> >>>>> "Yoshiki" == Yoshiki Hayashi <yoshiki(a)xemacs.org&gt; writes: >> Yoshiki> Andreas Jaeger <aj(a)suse.de&gt; writes: >> >> >> Have a look at cvs-status.el: >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> >> ;; chars sets. Ripped from cvstree >> >> (defvar cvstree-dstr-2byte-ready >> >> (when (featurep 'mule) >> >> (if (boundp 'current-language-environment) >> >> (string= current-language-environment "Japanese") >> >> t)) ; mule/emacs-19 >> >> "*Variable that specifies characters set used in cvstree tree graph. >> >> If non-nil, 2byte (Japanese?) characters set is used. >> >> If nil, 1byte characters set is used. >> >> 2byte characters might be available with Mule or Emacs with Mule extension.") >> >> >> >> (defconst cvstree-dstr-char-space >> >> (if cvstree-dstr-2byte-ready "ESC$B!!ESC(B" " ")) >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> >> >> >> There's nothing I can do to satisfy Mule and Non-Mule users. Or do >> >> you know about any solution? >> Yoshiki> How about this patch? I haven't tested it but it should Yoshiki> work. I changed JIS X 0208 characters to make-char call and Yoshiki> strings to characters. >> >> It would help if someone could explain what exactly the problem is so >> I can communicate with Stefan. As it stands, not knowing MULE, I >> don't know what exactly this patch fixes. Ben> the xemacs byte compiler adds (require 'mule) if it detects Ben> extended chars in the file. Forgive me: So what again is the *problem*?