W3C home > Mailing lists > Public > ietf-charsets@w3.org > January to March 1999

RE: draft-hoffman-utf16-01.txt available

From: Martin J. Duerst <duerst@w3.org>
Date: Thu, 04 Feb 1999 17:51:55 +0900
To: Francois Yergeau <yergeau@alis.com>
Cc: medavis2@us.ibm.com, Larry Masinter <masinter@parc.xerox.com>, Paul Hoffman / IMC <phoffman@imc.org>, MURATA Makoto <murata@apsdc.ksp.fujixerox.co.jp>, ietf-charsets@iana.org
Message-id: <199902041624.BAA23283@sh.w3.mag.keio.ac.jp>
At 16:33 99/02/03 -0500, Francois Yergeau wrote:
> タ 00:10 04/02/99 +0900, Martin J. Duerst a 馗rit :

> >I agree. But I think going the other way would be equally fatal:
> >Not defining things clear enough, and just do handwaving.
> It's not mere handwaving, the basic distinction between UTF-16 and
> UTF-16BE/LE is that the former doesn't tell you byte order while the latter
> does.  The BOM issue is secondary, is unclear and will probably remain
> soemwhat unclear because of the fact that the BOM does double-duty with the

I disagree. Whether you tell the byte order or not is obviously
very related to whether you need the BOM or not.

If we start with the premise that the BOM is unclear and then
write the document, we will have a self-fulfilling promize.
We can have the same self-fulfilling promize if we separate
things clearly.

And exactly because of the double-duty of the BOM and the ZWNBSP,
it is very helpful to say exactly where we expect a BOM and where not.

Regards,   Martin.

#-#-#  Martin J. Du"rst, World Wide Web Consortium
#-#-#  mailto:duerst@w3.org   http://www.w3.org
Received on Thursday, 4 February 1999 13:46:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:52:16 UTC