From: David Kastrup <dak@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-pretest-bug@gnu.org,
Patrick Drechsler <patrick@pdrechsler.de>,
Miles Bader <miles@gnu.org>
Subject: Re: 23.0.60; [nxml] BOM and utf-8
Date: Sun, 18 May 2008 11:14:46 +0200 [thread overview]
Message-ID: <85y768ug6x.fsf@lola.goethe.zz> (raw)
In-Reply-To: <87k5hsfdvd.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Sun, 18 May 2008 13:13:58 +0900")
"Stephen J. Turnbull" <stephen@xemacs.org> writes:
> So pop up a warning to the effect that the BOM was stripped per the
> Unicode standard, and that if it needs to be preserved, set
> UNICODE_ME_SOFTLY in the environment or bind `unicode-me-softly'
> around the codec.
It would be sufficient to use an encoding variation which adds the bom
back on writing.
I am actually surprised that this is not done right now: I thought we
had a discussion about having the BOM-encodings early in the automatic
encoding detections.
> Alternatively, sabotage the Microsoft users by silently eating the BOM
> on the way in, and writing the file in GNU substandard[1] format on
> the way out.
Emacs developers are not nonchalant about having Emacs write a byte
sequence differing from what it read in (apart from where it can't help
it, like with non-canonically encoded valid texts in shift character
based encodings) in my impression, and it is one of the better features.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2008-05-18 9:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 12:31 23.0.60; [nxml] BOM and utf-8 Patrick Drechsler
2008-05-17 14:13 ` Lennart Borgman (gmail)
2008-05-17 16:57 ` Patrick Drechsler
2008-05-17 20:38 ` Mark A. Hershberger
2008-05-21 22:20 ` Patrick Drechsler
2008-05-21 22:37 ` Patrick Drechsler
2008-05-22 1:33 ` Mark A. Hershberger
2008-05-22 14:43 ` Tom Tromey
2008-05-22 21:24 ` Miles Bader
2008-05-22 4:17 ` tomas
2008-05-22 4:33 ` Miles Bader
2008-05-22 8:28 ` Jason Rumney
2008-05-27 8:22 ` tomas
2008-05-22 17:34 ` Stephen J. Turnbull
2008-05-23 9:05 ` tomas
2008-05-23 21:23 ` Stephen J. Turnbull
2008-05-27 8:20 ` tomas
2008-05-18 2:29 ` Stephen J. Turnbull
2008-05-18 2:30 ` Miles Bader
2008-05-18 3:19 ` Eli Zaretskii
2008-05-18 4:19 ` Stephen J. Turnbull
2008-05-18 8:56 ` Jason Rumney
2008-05-18 11:00 ` Patrick Drechsler
2008-05-19 3:11 ` Stephen J. Turnbull
2008-05-19 14:32 ` Patrick Drechsler
2008-05-19 18:56 ` Eli Zaretskii
2008-05-20 15:16 ` Patrick Drechsler
2008-05-18 15:19 ` joakim
2008-05-18 4:13 ` Stephen J. Turnbull
2008-05-18 5:40 ` Miles Bader
2008-05-18 9:14 ` David Kastrup [this message]
2008-05-19 3:05 ` Stephen J. Turnbull
2008-05-18 23:40 ` David Kastrup
2008-05-19 20:34 ` Stephen J. Turnbull
2008-05-19 20:57 ` David Kastrup
2008-05-19 23:36 ` Stephen J. Turnbull
2008-05-20 7:13 ` David Kastrup
2008-05-30 2:47 ` Kenichi Handa
2008-05-30 3:44 ` Miles Bader
2008-05-30 3:59 ` Kenichi Handa
2008-05-19 6:32 ` Lennart Borgman (gmail)
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=85y768ug6x.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=miles@gnu.org \
--cc=patrick@pdrechsler.de \
--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).