Re: Disturbing IE 4.0pp2 behavior for lang="en"

=?iso-8859-1?Q?Martin_J=2E_D=FCrst?= (mduerst@ifi.unizh.ch)
Fri, 22 Aug 1997 14:46:07 +0200 (MET DST)


Date: Fri, 22 Aug 1997 14:46:07 +0200 (MET DST)
From: =?iso-8859-1?Q?Martin_J=2E_D=FCrst?= <mduerst@ifi.unizh.ch>
To: "E. Stephen Mack" <estephen@emf.net>
cc: www-html@w3.org
In-Reply-To: <3.0.3.32.19970822035913.00fe8914@emf.net>
Message-ID: <Pine.SUN.3.96.970822144255.703m-100000@enoshima>
Subject: Re: Disturbing IE 4.0pp2 behavior for lang="en"

On Fri, 22 Aug 1997, E. Stephen Mack wrote:

> Side issue -- given the hugeness of the Unicode character set
> and the convenience of named entities, I predict that future
> versions of HTML may add new named entities.  Perhaps the
> HTML 4.0 spec could add a section telling user agents how to
> treat unrecognized named entities.

I think this is already dealt with in SGML. Just displaying them
verbatim is correct. So at least Netscape is correct in this
respect.


> If HTML 5.0 introduces the &foo; named entity, how should a
> pre-HTML 5.0 browser treat &foo; if it sees it?  Displaying
> the literal sequence "&foo;" strikes me as a less-than optimal
> solution.
> 
> (Perhaps a universal fallback mechanism to access a central W3C
> standard library of entities, with images of the correct glyphs
> if no font is available?)

That mechanism is almost in place (as far as characters are
concerned; not for the glyphs, anyway). If you use an URL
in the DOCTYPE to refer to the W3C DTD, an apprpriately
constructed system will included the definitions for these
named entities, and convert them first to numeric character
references and then to the characters themselves.

Regards,	Martin.