Hex numeric character references don't work yet. These are entities of the form &#xHH; where HH is a hexadecimal number.
Here is an internal URL: http://warp/employees/erik/tests/cers/html40/charset-num.cgi?iso-8859-1
Subject: Re: HTML 4.0 Entity Tests Resent-Date: Tue, 22 Dec 1998 05:57:41 -0800 (PST) Resent-From: email@example.com Date: Tue, 22 Dec 1998 08:58:22 -0500 From: Liam Quinn <firstname.lastname@example.org> Organization: Web Design Group To: email@example.com Newsgroups: netscape.public.mozilla.layout References: <firstname.lastname@example.org> David Gardiner wrote: > > I've created this page originally to test what HTML Entities were > supported > by various browsers, but it occurs to me that it might be useful in > testing > Mozilla's entity support too. > > The original lives at > http://bananas.underdale.unisa.edu.au/Resources/entity2.htm , but > Mozilla > likes it, I would prefer the attached copy be put into the mozilla > source > somewhere and that used instead. Don't forget about hexadecimal character references as well. I've included these in my list of HTML 4.0 Entities at <http://www.htmlhelp.com/reference/html40/entities/>, which could also be used for testing purposes. -- Liam Quinn, Web Design Group http://www.htmlhelp.com/
Fixed by small mods in nsHTMLTOkens and nsString.
3/9/99 build Win98, Mac PPC Notable characters missing entirely are these: Π Π † † ∠ ∠ Many others show incorrectly, for example Latin capital ligature OE renders as an "R", the Greek capitol letter for omega renders a copyright symbol, etc.
No, those are different problems. The original bug was the fact that hex numeric character references such as ÿ were being rendered as xFF or something like that. This bug has been fixed. The bug you are referring to is a separate issue, down in the font engine (not the parser). Those characters are being rendered as boxes, right? Please open a separate bug for those, and assign Windows and Unix to me, Mac to ftang.
Ok. The original bug said "hex numeric character references don't work" which I interpreted as... well, that they didn't work. Anyway, I will close and verify this bug and open new bugs for the other problems.