all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Miles Bader <miles@gnu.org>
Cc: emacs-pretest-bug@gnu.org,
	"Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>,
	Edward O'Connor <hober0@gmail.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: 23.0.60; Defaut encoding for XML files should be undefined (instead of utf-8)
Date: Mon, 18 Feb 2008 15:26:57 +0900	[thread overview]
Message-ID: <87ablyye32.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <buomypzvtrf.fsf@dhapc248.dev.necel.com>

Miles Bader writes:
 > "Stephen J. Turnbull" <stephen@xemacs.org> writes:
 > > What's ungraceful about C-x C-s responding with
 > >     Warning:  This XML document does not seem to conform to XML
 > >     charset declaration rules.  Would you like to
 > >     (1) add an XML processor instruction (coding cookie)
 > >     (2) link to a parent document which specifies the encoding
 > >     (3) create a dummy parent document (available only to your sessions)
 > >     (4) save as is in the [buffer-file-coding-system] encoding?
 > 
 > 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.

 > [Whether the above sort of "extreme nannying"

"Extreme nannying"?  It's just an extension of the idea of providing a
document skeleton for a single file to multi-file documents.

 > knowing Emacs, users, it seems a good bet some would chaff
 > at the presumption.]

Let them chafe, and provide some lotion in the form of configurability
for those who know what they're doing and why.  But here, we're
talking about defaults.

 > 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.

Also, I appealed to PSGML and AUCTeX for a reason.  There are many
cases now where multi-file documents are the norm.  I think that not
only DTP files, but also multi-file source programs could benefit from
these techniques, over and above what we get from tag tables already.

As users get used to thinking of it as a general facility rather than
a property of just one mode, they'll generate neat ideas about what to
do with it.




  reply	other threads:[~2008-02-18  6:26 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 [this message]
2008-02-18  6:40                           ` Miles Bader
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ablyye32.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --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 \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.