Ar an deichiú lá de mí Eanair, scríobh Stephen J. Turnbull: Tomato, tomato :-) . echo '(define-coding-system-alias 'file-name 'utf-8) ' >> ~/.xemacs/init.el As I said, I don’t have access to an OS X machine. Having a system-specific hard-coding of the file-name coding-system alias is the right thing to do there, but if I implement it without being able to test it, I’ll get it wrong. And as I said in lisp/mule-cmds.el and in email, ;; On Unix--with the exception of Mac OS X--there is no way to ;; know for certain what coding system to use for file names, and ;; the environment is the best guess. If a particular user's ;; preferences differ from this, then that particular user needs ;; to edit ~/.xemacs/init.el. Aidan Kehoe, Sun Nov 26 18:11:31 CET ;; 2006. OS X uses an almost-normal-form version of UTF-8. As I followed up to Wulf, I was wrong in that. What seems to have happened is that the improved POSIX locale handling picked up that de_DE.UTF-8 was a German locale where it didn’t before, and mule-packages/locale just payed attention to that. If his LC_CTYPE had been de_DE all along, he would have had his menus in incompletely-translated German all along. Our language environment model is not as fine-grained as that of POSIX. For working out which language to use on Unix, we pay attention to LC_CTYPE and nothing else. If you can suggest a better approach to this, that is also compatible with language environment treatment on Windows, where the granularity is different, have at it. -- When I was in the scouts, the leader told me to pitch a tent. I couldn't find any pitch, so I used creosote. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta