On 29 Jan 2004, stephen(a)xemacs.org wrote:
>>>>> "Uwe" == Uwe Brauer
<oub(a)mat.ucm.es> writes:
Uwe> I try to talk to the debian package manager and ask him about
Uwe> his reasons.
That's simple. More Debian users exchange files with Windows
systems than edit "binary" files that look like text. Most people
only edit text files, and they consider files with embedded control
characters other than tabs and whatever the system newline
convention is to be already corrupted. The defaults are set up for
"most people."
If you want to turn it off personally at runtime, you just do
(setq file-coding-system-alist '(("" . binary)))
in your init file.
But all you're really doing by turning off file-coding or mule is
guaranteeing that the large set of users who need/want mule or
file-coding will never be able to rely on x-symbol, and you won't be
able to support them.
This is true and sad. Don't get me wrong, I think that mule is
important. However since it can corrupt files (I remember others
(Hrvoje?) to complain as well) and besides my attempts to track the
problem down and to communicate with Christoph about it, it seems sort
of hopeless.