unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: tomas@tuxteam.de
To: "Stephen J. Turnbull" <turnbull@sk.tsukuba.ac.jp>
Cc: emacs-pretest-bug@gnu.org,
	Patrick Drechsler <patrick@pdrechsler.de>,
	tomas@tuxteam.de, emacs-devel@gnu.org
Subject: Re: 23.0.60; [nxml] BOM and utf-8
Date: Fri, 23 May 2008 11:05:11 +0200	[thread overview]
Message-ID: <20080523090511.GA12796@tomas> (raw)
In-Reply-To: <87mymixmx5.fsf@uwakimon.sk.tsukuba.ac.jp>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, May 23, 2008 at 02:34:46AM +0900, Stephen J. Turnbull wrote:
> tomas@tuxteam.de writes:
> 
>  > > > ,----[ http://www.w3.org/TR/2006/REC-xml-20060816/#charencoding ]
>  > > > | Entities encoded in UTF-16 MUST and entities encoded in UTF-8 MAY
>  > > > | begin with the Byte Order Mark [...]
>  > > > |        [...]  XML processors MUST be able to use this character to
>  > > > | differentiate between UTF-8 and UTF-16 encoded documents.
>  > > > `----
>  > 
>  > ...and how are the XML processors supposed to achieve that? Is there a
>  > second variant of BOM, indicating UTF-8?
> 
> Well, note that the BOM is three octets in UTF-8 but only two in
> UTF-16.  Dead giveaway, there.

Duh. Thanks. That's what I was missing.

[...]

>  > Am I completely whacko, or are they?
> 
> Neither.  You live in a relatively sane world, they live in a world
> which contains the sovereign nations of Japan and Microsoft.

Thanks for your kind words :-)

As for whether Emacs or nxml has the burden of skipping the BOM -- that
would correspond to whether nxml "within" Emacs is "seeing" a piece of
XML or a whole XML document, right?

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFINojHBcgs9XrR2kYRAtieAJsEoakhvgRrjisQ9XhIjAap5mISBACaAjrk
7IuDZQjZvvdFoadb90lSygE=
=022X
-----END PGP SIGNATURE-----




  reply	other threads:[~2008-05-23  9:05 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 [this message]
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
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=20080523090511.GA12796@tomas \
    --to=tomas@tuxteam.de \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=patrick@pdrechsler.de \
    --cc=turnbull@sk.tsukuba.ac.jp \
    /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).