From: Miles Bader <miles.bader@necel.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org,
"Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>,
Edward O'Connor <hober0@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: 23.0.60; Defaut encoding for XML files should be undefined (instead of utf-8)
Date: Mon, 18 Feb 2008 15:40:20 +0900 [thread overview]
Message-ID: <buo63wmwywb.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <87ablyye32.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Mon, 18 Feb 2008 15:26:57 +0900")
"Stephen J. Turnbull" <stephen@xemacs.org> writes:
> > The discussion is about what to do when visiting a file, not saving
> > it.
>
> Do the same thing at visit time by default. It's not like the
> implementation would differ, it's just it would be a post-visit hook
> instead of a pre-save hook.
That isn't going to fly. What are willing to put up with when saving a
file is very different from what they're willing to put up when visiting
one. [It might be useful as an configurable _option_, of course, for
those people who need it.]
> > For visiting, I rather like what I suggested earlier, changing Emacs'
> > format-specific-coding mechanisms to support format-specific coding
> > _preferences_ as well as "absolute codings".
>
> IMO, users who know enough about coding systems and the various
> formats to use such a facility would be just as happy to use
> `file-coding-system-alist'. Learning about it will be a burden for
> the "naive" users who want things to "just work". And maintaining a
> database of defaults will be a burden on maintainers disproportionate
> to the benefit.
I think maybe you misunderstood my proposal.
Emacs currently, for xml and related files, has various mechanisms that
_force_ the encoding to be utf-8 when reading (visiting) the file. [If
the file has no coding: tag.]
I'm suggesting these mechanisms have the ability to be "softer", so that
instead of forcing the encoding to utf-8, utf-8 is merely pushed to the
front of the coding priority list for coding recognition, as if by the
`prefer-coding-system' function (while reading that file), and Emacs'
normal automagic recognition allowed to do its stuff. This "preference"
is _not_ set by the user, but rather by the same emacs magic that
currently sets an "absolute" utf-8 coding [on non-tagged files].
That would mean that "proper" xml files would continue to work just as
now, using utf-8 (with no danger of being screwed up due to the user's
language environment), but that "improper" xml files would stand a much
better chance of showing up in the user's buffer as something readable
rather than gibberish. [This doesn't guarantee that other apps will do
the right thing of course -- though in the case being discussed, the
would have -- but while in Emacs, things tend to make a lot more sense
if the file was read as something reasonable.]
-Miles
--
Consult, v.i. To seek another's disapproval of a course already decided on.
next prev parent reply other threads:[~2008-02-18 6:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 9:06 23.0.60; Defaut encoding for XML files should be undefined (instead of utf-8) Sébastien Vauban
2008-02-15 22:32 ` Edward O'Connor
2008-02-15 22:54 ` Jason Rumney
2008-02-15 23:24 ` Miles Bader
2008-02-15 23:34 ` Jason Rumney
2008-02-15 23:42 ` Miles Bader
2008-02-16 3:42 ` Miles Bader
2008-02-18 2:49 ` Jason Rumney
2008-02-18 3:01 ` Jason Rumney
2008-02-16 4:03 ` Stefan Monnier
2008-02-16 7:17 ` Stephen J. Turnbull
2008-02-16 9:58 ` Jason Rumney
2008-02-16 11:23 ` Stephen J. Turnbull
2008-02-16 12:07 ` Lennart Borgman (gmail)
2008-02-17 3:52 ` Stephen J. Turnbull
2008-02-17 14:31 ` Lennart Borgman (gmail)
2008-02-17 22:24 ` Stephen J. Turnbull
2008-02-17 22:27 ` Miles Bader
2008-02-18 0:07 ` Stephen J. Turnbull
2008-02-18 3:16 ` Miles Bader
2008-02-18 6:26 ` Stephen J. Turnbull
2008-02-18 6:40 ` Miles Bader [this message]
2008-02-19 7:17 ` Stephen J. Turnbull
2008-02-19 7:19 ` Miles Bader
2008-02-19 21:03 ` Stephen J. Turnbull
2008-02-19 22:47 ` Jason Rumney
2008-02-19 22:58 ` Miles Bader
2008-02-20 0:43 ` Stephen J. Turnbull
2008-02-19 15:50 ` Stefan Monnier
2008-02-19 22:02 ` Stephen J. Turnbull
2008-02-18 14:59 ` Projects and multi-file documents (was: 23.0.60; Defaut encoding for XML files should be undefined (instead of utf-8)) Stefan Monnier
2008-02-18 18:51 ` Projects and multi-file documents Ralf Angeli
2008-02-18 16:35 ` 23.0.60; Defaut encoding for XML files should be undefined (instead of utf-8) Lennart Borgman (gmail)
2008-02-16 17:03 ` Jason Rumney
2008-02-16 17:31 ` David Kastrup
2008-02-17 3:53 ` Stephen J. Turnbull
2008-02-18 3:22 ` Miles Bader
2008-02-18 6:01 ` Stephen J. Turnbull
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=buo63wmwywb.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=hober0@gmail.com \
--cc=lennart.borgman@gmail.com \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stephen@xemacs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).