W3C home > Mailing lists > Public > www-validator@w3.org > July 2001

Re: German_Umlauts

From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
Date: Mon, 2 Jul 2001 19:40:31 +0100 (BST)
To: Martin Duerst <duerst@w3.org>
cc: www-validator <www-validator@w3.org>
Message-ID: <Pine.GSO.4.21.0107021931480.1205-100000@phaestos.ee.surrey.ac.uk>
On Mon, 2 Jul 2001, Martin Duerst wrote:

> At 17:11 01/06/30 +0100, Lloyd Wood wrote:
> >On Fri, 29 Jun 2001, Liam Quinn wrote:
> >
> > > There's nothing wrong with using the 8-bit ISO-8859-1 encoding of a letter
> > > with an umlaut as long as you specify your charset as ISO-8859-1.
> >
> >but if you can, surely using available &entity; increases
> >understandability for displays using other charsets?
> Good browsers now display an enormous number of scripts and
> characters, and get better and better.

and the legacy degradation is pretty poor...

> And the number of
> browsers that don't support iso-8859-1 (when properly told
> that the file is in that encoding) is extremely small.
> So using entities should really not be necessary.

I do think relying on an encoding is Bad Practice. It's raising the
legacy bar.

> Nobody would use &UpperCaseA; just to write an 'A', or would they?

actually, it has always bothered me that entities are case-sensitive;
&Ouml; vs &ouml;. Yes, it's an obvious mapping to the content, but
it just bugs me.

> >Even if they
> >don't translate it but display it raw, the reader has a chance to
> >figure out meaning.
> For the Latin-1 case, which is covered by the character entities
> in HTML, guessing D?rst (or just reading over it) is in most cases
> easier than reading D&uuml;rst.

Beg to differ; how far can you trust context? imagine &emdash; versus
seeing a ?; it might be a smart quote or a dash of some length, hard
to be sure. I'd quite like browsers to display (or make it an option
to display) everything they don't understand, so that the reader will
not be misled.


Received on Monday, 2 July 2001 14:40:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 14:17:30 UTC