Re: 21.4.10-mule codings problem, ~ appears
Stephen J. Turnbull writes:
>>>>> "Uwe" == Uwe Brauer
<oub(a)ucmail.ucm.es> writes:
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.
Ups to bad, this was one
of the package which made me switch from GNU
emacs to xemacs, years ago.
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 รก in the buffer, and allows you to
try to save that?
Ok I don't know how x-symbol replaces \alpha while editing,
the point
is of course one sees an greek alpha not the ASCII string \alpha; I
ask christoph about.
Uwe> According to Christoph in GNU emacs there is something like
Uwe> "safe encoding" a feature which is missing here.
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. You could also set the
buffer-file-coding-system to 'utf-8 (if you have Mule-UCS enabled) or
to 'iso-2022-7. This will prevent corruption, but your files will not
be readable by TeX.
Ups to bad, this would not help at all. Besides I still use
good old
iso-accents-mode for writing iso-8859-1 chars. I suppose if I use
latin-unity, I cannot use the same init files for mule and no mule
version, since latin-unity seems not to make any sense in no mule.