W3C home > Mailing lists > Public > www-html@w3.org > November 2001

RE: Indicating browser support for XHTML1.0

From: Christian Wolfgang Hujer <Christian.Hujer@itcqis.com>
Date: Thu, 22 Nov 2001 23:40:50 +0100
To: "William F. Hammond" <hammond@csc.albany.edu>
Cc: "Monostory Miklos" <dkmm@axelero.hu>, "www-html" <www-html@w3.org>
Message-ID: <000901c173a6$bc778780$1595e23e@andromeda>
Hello Wiliam F. Hammond, dear list members,

> -----Original Message-----
> From: William F. Hammond [mailto:hammond@csc.albany.edu]
> Sent: Thursday, November 22, 2001 11:21 PM
> To: Christian Wolfgang Hujer
> Cc: Monostory Miklos; www-html
> Subject: Re: Indicating browser support for XHTML1.0
> "Christian Wolfgang Hujer" <Christian.Hujer@itcqis.com> writes:
> > > So, in this language there are many "special character",
> whats are well
> > > represented in iso-8859-2,
> > > but quite slow to type their etnities.
> >
> > which is of no interest because you simple use an XSLT copy
> transformation
> > that reads iso-8859-2 and writes ASCII. It's all so simple :)
>                                    ^^^^^
> I assume that you mean UTF-8, not ASCII.

No, i meant ASCII. ASCII documents are UTF-8 documents and ISO-8859-1
documents at the same time, since it is their basis and denominator.

UTF-8 requires an additional charset information in HTML4 (and causes
problems in some browsers), while ISO-8859-1 requires an additional charset
information in XHTML 1.0 (the XML declaration, which causes problems in some
browsers), so to be safe, simple use their denominator, which is US-ASCII-7
(which works in really all browsers).

> The use of an XSLT engine for this might be viewed as "overkill".
I don't think so, since it also can be used for solving several other site
related tasks like adding layout to content.

> It is not unreasonable to expect that one's editing interface has
> provision for keyboard entry of the user's local character set with
> saving in UTF-8.  Another approach would be using a parser that reads
> the local character set and re-writes the document in XML form under
> UTF-8.  (SP can do this.)
the topic was wether to generate HTML 4 and XHTML seperately or if one can
be safe generating XHTML only. Saving UTF-8 is not a solution, saving
anything else isn't, but ASCII is.


Received on Thursday, 22 November 2001 17:42:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:58 UTC