W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2004

RE: [Serial] I18N WG last call comments

From: Michael Kay <mhk@mhk.me.uk>
Date: Thu, 6 May 2004 17:52:53 +0100
To: "'Martin Duerst'" <duerst@w3.org>, "'Henry Zongaro'" <zongaro@ca.ibm.com>, <w3c-i18n-ig@w3.org>
Cc: <public-qt-comments@w3.org>
Message-Id: <20040506165331.C506FA14C7@frink.w3.org>

> > > I worry that we will get many complaints from users who 
> are misusing
> > > these codepoints if we do this.
> How are they misusing these code points? The case we know is that
> bytes in the rage 0x80-0x9F are used e.g. in iso-8859-1 but with
> the intent of giving them the windows-1252 semantics.

This was the case I had in mind. People create documents in cp1252 and
declare them as iso-8859-1. And it all works, because the errors cancel each
other out. If we oblige processors to detect this situation we will be
asking users to pay for the extra processing cost, and in return the
application that worked before will stop working. Will they thank us?
Because if they won't, we shouldn't do it.

> In some way just a detail, but: There is currently no XSLT 2.0
> code that will stop working. XSTL 1.0 doesn't have the XHTML
> output method.

I may have lost the thread, but I thought we were discussing the HTML output

> > [20] 6.4 HTML Output Method: Writing Character Data: "Certain

Michael Kay
Received on Thursday, 6 May 2004 12:53:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:56:57 UTC