Open
Bug 74172
Opened 24 years ago
Updated 3 years ago
include XHTML1-defined entities for use in xpfe
Categories
(Core :: XUL, enhancement)
Core
XUL
Tracking
()
NEW
People
(Reporter: dr, Unassigned)
References
Details
XHTML 1.0 defines general entities for commonly-used unicode characters:
http://www.w3.org/TR/html/DTD/xhtml-lat1.ent: Latin-1 characters
http://www.w3.org/TR/html/DTD/xhtml-special.ent: "Special" characters
http://www.w3.org/TR/html/DTD/xhtml-symbol.ent: Symbols
These should be in the tree and referenceable through chrome urls. For example:
<!ENTITY % HTMLspecial PUBLIC
"-//W3C//ENTITIES Special for XHTML//EN"
"chrome:///entities/xhtml-special.ent">
%HTMLspecial;
The front-end should be able to make use of these. For example:
<!ENTITY titleSeperator.label " – ">
as in bug 22871.
So where should these files go?
ok, they're going in xpfe/global/resources/content. they'll be referenceable as
chrome://global/content/whatever.ent. patch on the way...
Sounds a cousin of bug 44458 which has a list of XHTML entities in DTD form.
Comment 4•24 years ago
|
||
Do we really need these? Most localizations use non-ASCII characters and there
have been no problems using UTF-8 for these.
->moz0.9.1, per triage
Target Milestone: mozilla0.9 → mozilla0.9.1
->future (this is easily done, but there's no point in doing it until we have
74753 fixed).
Target Milestone: mozilla0.9.1 → Future
[spam] dr@netscape.com's bugs subject to redistribution by chofmann. R!
Assignee: dr → chofmann
Status: ASSIGNED → NEW
Priority: P4 → --
Target Milestone: Future → ---
Updated•16 years ago
|
QA Contact: brendan → xptoolkit.widgets
Comment 10•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.
Assignee: chofmann → nobody
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•