HTML 4.01 named character support tracker

RESOLVED INCOMPLETE

Status

RESOLVED INCOMPLETE
17 years ago
2 years ago

People

(Reporter: hsivonen, Assigned: jshin1987)

Tracking

({html4, meta})

Trunk
html4, meta
Dependency tree / graph
Bug Flags:
wanted1.9.2 ?

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

17 years ago
Mozilla does a *very* good job in supporting nearly all the characters that are
named in HTML 4.01 spec. However, there are still a few unsupported named chars.
This a tracker for 100% named char support.
(Reporter)

Updated

17 years ago
Blocks: 7954
Depends on: 86098
(Reporter)

Updated

17 years ago
Depends on: 88795
Keywords: meta
(Reporter)

Updated

17 years ago
Depends on: 88804

Updated

17 years ago
Status: NEW → ASSIGNED
It looks as if bug 9101 and bug 36163 should also be dependencies...
(Reporter)

Updated

17 years ago
Depends on: 9101, 36163

Comment 2

17 years ago
Just out of interest, exactly which signs aren't supported?
I made a page many months ago of the HTML spec signs and every sign has
something show up since at least then (even some that won't show in the original
URL for this bug).

http://members.nbci.com/_XMCM/huszics/wa/tecken.html

Or is this a bug about potentially wrongly displayed/working signs ?
(Reporter)

Comment 3

17 years ago
This is a tracker bug. The specific problems are filed as bugs depending on this
one. The char support has per-platform differences. On Mac OS X, I see the same
problems with the both test pages.

Comment 4

17 years ago
meta bug, mark as future. 
Target Milestone: --- → Future

Updated

17 years ago
Target Milestone: Future → mozilla1.0

Updated

17 years ago
Keywords: mozilla1.0

Comment 5

17 years ago
tracking bug go m1.1
Target Milestone: mozilla1.0 → mozilla1.1

Comment 6

17 years ago
move all my "tracking" bug to "M1"
Target Milestone: mozilla1.1 → M1

Comment 7

17 years ago
Adding dependency on bug 116990, "Vulgar Fraction entities don't use real glyphs
when available."
Depends on: 116990

Comment 8

17 years ago
Is my bug 144810 ("Named entities in HTML documents are converted to numbered
entities by Composer") a valid dependency for this one?
(Reporter)

Comment 9

17 years ago
No, this bug doesn't depend on bug 144810. This one is about displaying the
characters.

Comment 10

16 years ago
One of my pet peeves: writing that something exists on the web, but neglecting
to give a link directly to it.

"all the characters that are named in HTML 4.01 spec":
http://www.w3.org/TR/html401/sgml/entities.html

Thanks for the test URI that actually (tries to) render all those entities. When
I look at that URI, I still see (using Mozilla 1.1a build 2002061104 on Win98)
Mozilla render several of entities as a question mark "?" (such as "hArr").
There are a few (such as "ensp"emsp") that don't have the question mark, but are
still rendered incorrectly (see bug 70610).

Comment 11

14 years ago
what a hack. I have not touch mozilla code for 2 years. I didn't read these bugs
for 2 years. And they are still there. Just close them as won't fix to clean up.
Status: ASSIGNED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WONTFIX

Comment 12

14 years ago
Mass Reassign Please excuse the spam
Assignee: ftang → nobody

Comment 13

14 years ago
Mass Re-opening Bugs Frank Tang Closed on Wensday March 02 for no reason, all
the spam is his fault feel free to tar and feather him
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---

Comment 14

14 years ago
Reassigning Franks old bugs to Jungshik Shin for triage - Sorry for spam
Assignee: nobody → jshin1987
Status: REOPENED → NEW

Updated

9 years ago
Flags: wanted1.9.2?

Comment 15

2 years ago
Marking all tracking bugs which haven't been updated since 2014 as INCOMPLETE.
If this bug is still relevant, please reopen it and move it into a bugzilla component related to the work
being tracked. The Core: Tracking component will no longer be used.
Status: NEW → RESOLVED
Last Resolved: 14 years ago2 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.