Stephen J. Turnbull wrote:
>>>> "Uwe" == Uwe Brauer
Uwe> After years I tried again using Mule, since this way I can
Uwe> even read math symbols in mails, using the x-symbol package.
x-symbol causes lots of problem reports with XEmacs/Mule.
Stephen, if that is so, you should forward them to me. (If
XEmacs/Mule causes the problems, too -- I could then put a note into the
manual -- I already have some...all have been mentioned on xemacs-beta.)
Uwe> However there is a annoying feature a latex buffer gets
Uwe> during the save-buffers-kill-emacs operation corrupted in
Uwe> such a way that all greek symbols like \alpha are then
Uwe> replaced by ~.
I don't understand. "\alpha" is an ASCII string. Do
you mean that
x-symbol replaces the "\alpha" with a in the buffer, and allows you
to try to save that?
X-Symbol decodes \alpha to a character of a new charset in the buffer
and encodes it when saving. Uwe, if the encoding does not work for you
(of course, X-Symbol must have been enabled in that buffer), you should
send a bug report as described in the manual.
Uwe> According to Christoph in GNU emacs there is something like
Uwe> "safe encoding" a feature which is missing here.
Well, the mechanism would have just told you that you are trying to save
the private characters (please note that only the head revision of Emacs
uses the correct sequence format-annotate/encode -- choose-save-encoding).
Safe charsets prevents you from saving the buffer when charsets that
are not savable in the current encoding are present. You can get a
similar effect by enabling the latin-unity package, but it's limited
(I think) to extended Latin characters.
Well, it might be similar, but not very, and it would not prevent the ~
for the character `alpha'.
 v4.4.4 will handle the situtation where different buffer would have
different `buffer-file-coding-system's. It will also rename all local
variables named `values' which is necessary in XEmacs (but nowhere
mentioned -- and extremely annoying...)
 assume the default encoding is latin-9 and a file containing latin-2
* with latin-unity: XEmacs would still store a latin-9 encoded file,
latin-unity would remap a latin-2 zcaron to a latin-9 zcaron, i.e.,
store a byte with value 184 and XEmacs would fail to store a zacute
(with a single byte)
* with a safe-encoding mechanism: XEmacs would suggest to store a
latin-2 encoded file (where a zcaron would be stored as a byte with