W3C home > Mailing lists > Public > www-amaya@w3.org > April to June 2001

Re: Entities

From: Patrick T. Rourke <ptrourke@mediaone.net>
Date: Tue, 29 May 2001 16:48:20 -0400
Message-ID: <002501c0e880$b1f427c0$82519318@Rourke.ne.mediaone.net>
To: <www-amaya@w3.org>
Apologies for sending this in UTF-8, but it's the best way to show it.

Unicode has two methods of representing composite characters like:
precomposed characters and combining diacriticals.  The two methods would be
used as follows for the character in question:

(U+0063 + U+0301; represented as entities as &#x0063;&#x0301;)

(U+0107; represented as an entity as &#x0107;)

(Note that these are HEXADECIMAL values!)

The former is that defined in Normalization Form D; the latter, in
Normalization Form C (the preferred form for web documents according the
draft of the W3C Character Model I last read).

In Windows ME, Mozilla 2001052708, IE5.5, and Netscape 4.77 [!] all can
manage both forms in UTF-8 (what I tested), though the combination is poorly
spaced in the Moz/Net browsers (not surprising).  In Mozilla and IE (but not
Netscape 4.x), entities do work.  I have managed to get both to work before
in Linux with Mozilla (later than M17) with a font that included the correct
combining diacriticals characters, though such a font is not currently
available; and it might work in Konqueror as well.

> I would prefer tricks like that rather than introducing unicode.

The suggestion that rather than supporting Unicode-based technologies Amaya
should kludge together its own method of supporting only those character
combinations that are requested by users is I would think counter to the
spirit of standards support.

Patrick Rourke

----- Original Message -----
From: "Dave J Woolley" <david.woolley@bts.co.uk>
To: <www-amaya@w3.org>
Sent: Tuesday, May 29, 2001 2:37 PM
Subject: RE: Entities

> > From: Christian Mondrup [SMTP:scancm@biobase.dk]
> >
> > Somewat related to the question: is it possible with some kind of
> > backspace entity to force accents on letters which are else not
> [DJW:]
> In theory, you can use UTF-8 (-16 etc) or numeric
> character entities to introduce the Unicode characters
> for non-spacing accents (or the actual accented characters).
> I'd be surprised to find a browser that supports this,
> although it might be worth trying IE 5.5 or IE 6 using the
> full Unicode font from Office 2000.
> In almost all cases, using the Unicode accented characters is
> going to be a better approach than using non-spacing accents.
> --
> --------------------------- DISCLAIMER ---------------------------------
> Any views expressed in this message are those of the individual sender,
> except where the sender specifically states them to be the views of BTS.
> >
Received on Tuesday, 29 May 2001 16:51:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:30:33 UTC