Nick> Reading your patch I found that you decided not to define Nick> `string-as-unibyte' and `string-as-multibyte' functions. Nick> Could you explain your idea, please? May be these functions Nick> should be defined in mule core for compatibility reasons? I don't think so. They cannot be defined compatibly in XEmacs (well, they can, but we don't want to do so---it would involve completely undoing the character/string abstraction we use). If we just hack them up for whatever use we encounter first, we will inevitably find they do the wrong thing later. What we should do is figure out what these functions are used to implement, define _that_ as a function, and try to get the FSF to either use our implementation, or to do (defalias #'ps-print-some-internal-function #'string-as-multibyte) -- 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."