Re: [iso-latin-1] Coding system problem.

Aidan Kehoe <kehoea(a)parhasard.net&gt; writes: I've been bitten by the same problem again, this time with mule-utf-8-unix. Really, I should think you have to decide for one of four courses: a) add aliases for everything for which you have a different name everywhere b) add alias handling local to the desktop package that translates when loading and saving to the GNU Emacs equivalents. Or that c) simply removes the buffer coding system from what gets saved and restored. d) tell people that they might just as well forget sharing a desktop file between Emacs and XEmacs. In case c), you need to provide a mechanism by which the desktop package will use a file name different from the file name Emacs uses. But it does not make sense to wait for a new bug report every time and then add a single alias. Version d) would be a permanent and probably the cleanest as well as easiest solution with the obvious (and in my opinion tolerable) drawback that you can't share desktops when switching editors. Version b) would be considerable work, version c) is not optimal, but a file that does not get identified correctly when reloading without the desktop package could be expected to do the same with it. Version a) would turn your own choice of encoding names into a mockery since then it would become quite hard to enforce _your_ names as long as all the aliases stay around. It would also fail to bring across the message to third party package authors that they better use the XEmacs encoding names or else. Anyway, I am not the only person that is going to run into trouble with that, I believe, and so you really should not wait for the next bug report before agreeing on a strategy. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum