W3C home > Mailing lists > Public > public-css-testsuite@w3.org > June 2005

Re: t0805-c5520-brdr-b-01-e.htm

From: Edward Reid <edward@paleo.org>
Date: Tue, 07 Jun 2005 08:45:39 -0400
Message-Id: <6.0.0.22.2.20050607082852.0539ec30@mail.messagingengine.com>
To: public-css-testsuite@w3.org

At 01:10 PM 06/07/2005 +0200, Bjoern Hoehrmann wrote:
>I guess he would prefer character references for non-ASCII characters.

Correct.

>As discussed in <http://www.w3.org/TR/charmod/#C047>, this would not be
>a good idea (except for "characters" like &nbsp;).

That section says

>Escapes SHOULD only be used [...] or when the visual representation of the 
>character is unclear.

My experience with this page was:

1) Opening it in iCab 3.0.280 under Mac OS 9.1 resulted in different 
characters being displayed from those intended.

2) Opening the source in Page Spinner 3.1.2 under Max OS 9.1 resulted in 
three garbage characters where the arrows should be.

3) Opening the source in TextPad under Windows XP SP2 resulted in TextPad 
claiming these characters are non-ASCII and replacing them with question marks.

4) Opening the source in HTML-Kit under Windows XP SP2 resulted in display 
of three garbage characters where the arrows should be.

5) Opera 8.0 under Windows XP SP2 displayed the arrows as intended. So did 
Microsoft Word 2002 and Mozilla FireFox 1.0.2.

I got similar results for other pages using the arrows.

So whether or not there is a technical specification for these characters, 
in practice they are highly ambiguous using software in widespread use today.

Edward Reid
Art Works by Melynda Reid: http://paleo.org
Received on Tuesday, 7 June 2005 12:46:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 20 September 2010 17:51:54 GMT