Michael Albinus writes: XEmacs doesn't have unibyte buffers; it only has buffers of characters. Emacs's *-as-unibyte functions are dangerous and, AFAICS, unnecessary. XEmacs has `file-name-coding-system' for handling file names. This is initialized to something sane for the local file system; if you need something else for a particular operation, bind it. I'm not sure how it would interact with file handlers offhand. XEmacs has `default-network-coding-system' and `default-process-coding-system' for handling I/O. I think probably only the latter is relevant to Tramp since it uses external processes (ssh, ftp) to access remote systems. Like `file-name-coding-system' they are initialized to something sane for the local operating system. If the defaults are inappropriate for some operation, bind `coding-system-for-read' or `coding-system-for-write' as appropriate I can't recommend anything for Windows, I don't know how it would behave as a remote system accessed via external network protocols like ssh. For remote Unix systems, it's always possible to get correct results by using the 'binary coding system (but you have to manage the decoding yourself, which is not fun even if you know what you're doing). _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta