|--==> "SJT" == Stephen J Turnbull <stephen(a)xemacs.org> writes:
>>>>>"SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
SY> This also fixes some horrible bogosity
introduced because this
SY> file's coding system was set to "MSW UTF8". OMG, M$ Win is a
SY> truly evil abomination.
SJT> All that means is that the UTF-8 signature is prepended to the file.
SJT> This is _not Microsoft_,
[...]
Fair enough. Mind you, I have absolutely no idea what a "UTF-8
signature" is, but I trust you on this. :-)
SJT> This needs to be fixed
OK, how?
I did a...
(add-to-list 'file-coding-system-alist '("offending-file" .
iso-8859-1))
Which fixed(?) it for "offending-file", but that doesn't seem to be
the right work around, and...
(add-to-list 'file-coding-system-alist '(t . iso-8859-1))
...hardly seems practical.
Could I hang something off 'find-file-hooks' to change the coding
system if it's "MSW UTF8"?
Is it my XEmacs that is adding the "UTF-8 signature" when I visit a
file edited by someone else? Or is it coming from the person who
edited the file before me?
What do we do about this, Steve? It looks like this bug needs a
fairly high priority to get fixed. When it bit me this time it wasn't
so bad, just damn annoying. But...
There are a couple of files in the Oort Gnus lisp directory that have
these "UTF-8 signatures". I usually run a Mule-enabled XEmacs and if
I byte-compile these files with a Mule-XEmacs I can't load them with a
non-Mule one. I get a "can't open load file: mule" error. These
files _don't_ need Mule.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|