From: "Sébastien Vauban" <zthjwsqqafhv@spammotel.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs refusing to switch to iso-latin-1
Date: Thu, 14 Feb 2008 10:03:44 +0100 [thread overview]
Message-ID: <87hcgbucy7.fsf@mundaneum.com> (raw)
In-Reply-To: 85hcgern5n.fsf@lola.goethe.zz
Hi David and all,
>>>>> BTW, here's a sample file (let's call it `test.xml') that
>>>>> exhibits the described problem:
>>>>>
>>>>> <enumType name="test">
>>>>> <pair value="0">- Sélectionner -</pair>
>>>>> <pair value="11">Dû à l'entreprise</pair>
>>>>> <pair value="12">Stagiaire occupé</pair>
>>>>> <pair value="13">Autres</pair>
>>>>> </enumType>
>>>>>
>>>>> Thanks for your help!
>>>>
>>>> Huh? That file does not contain an encoding header, and so
>>>> according to the XML standard, it _has_ to be encoded in
>>>> utf-8. Emacs gets this right.
>>
>> I did not know about that.
>>
>> But, for me, this does not explain why my request to "use
>> iso-latin-1-unix for saving this buffer" is not respected.
>
> Because your file does not start with
> <?xml version="1.0" encoding="ISO-8859-1"?>
>
> Is that so hard to understand?
I'm quite surprised, yes, because it's one of the first time
Emacs does something in my back, without my knowledge.
I'm not surprised by such behaviors from all the other tools, in
particular the MS ones, but here... yes I am.
> XML without such a header is encoded in utf-8, period. Any
> conforming XML interpreter will _barf_ if you were able to
> save in latin-1.
OK, but this annoys me, still. It's not because that file has a
`.xml' extension that it has to be complete. I would never give
it to a parser like that.
That file, along with others, is part of a correct XML file
that's created by a process, from different sub-sources. The
file I'm editing is one of these sources. So, I can't put a
header in there, otherwise it would appear everywhere in the
resulting XML file.
OK, maybe I can add "local variables" comments in every
sub-file, yes, but I didn't expect from Emacs to take decisions
away from me - but for a default coding system when nothing is
specified (and, even then, it's under my knowledge). Sorry.
Seb
--
Sébastien Vauban
next prev parent reply other threads:[~2008-02-14 9:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 11:25 Emacs refusing to switch to iso-latin-1 Sébastien Vauban
2008-02-11 13:44 ` Peter Dyballa
[not found] ` <mailman.7278.1202737459.18990.help-gnu-emacs@gnu.org>
2008-02-11 14:54 ` Sébastien Vauban
2008-02-11 16:02 ` Peter Dyballa
2008-02-11 16:18 ` Peter Dyballa
2008-02-11 16:28 ` Sven Joachim
2008-02-11 16:38 ` David Kastrup
2008-02-11 16:55 ` Lennart Borgman (gmail)
[not found] ` <mailman.7290.1202748969.18990.help-gnu-emacs@gnu.org>
2008-02-12 12:11 ` Sébastien Vauban
2008-02-12 19:27 ` David Kastrup
2008-02-14 9:03 ` Sébastien Vauban [this message]
2008-02-14 20:58 ` Stefan Monnier
2008-02-15 9:09 ` Sébastien Vauban
2008-02-14 19:58 ` Stefan Monnier
2008-02-15 8:45 ` Emacs refusing to switch to iso-latin-1 (on the way to be SOLVED) Sébastien Vauban
[not found] ` <mailman.7285.1202745751.18990.help-gnu-emacs@gnu.org>
2008-02-12 11:27 ` Emacs refusing to switch to iso-latin-1 Sébastien Vauban
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hcgbucy7.fsf@mundaneum.com \
--to=zthjwsqqafhv@spammotel.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).