The help system should be XUL-ified and the entitites (e.g. paragraphs and headings) externalized, so that it will be easier to localize. This will also make it easier to change 'Mozilla' and other trademarks and Netscape-specific names (e.g. Sidebar --> My Sidebar) for Netscape. As an added bonus, the help files will also look more "native", i.e., will look like the rest of Mozilla, even when you change themes.
Adding keyword l12y. Changing QA contact to email@example.com.
QA Contact: andreasb → ylong
Reassigned to oeschger.
Assignee: rchen → oeschger
What does this mean? That the help content should be in XUL? Or do you mean the table of contents, which is currently in RDF?
The actual help pages should be in XUL, and all text externalized to entities (with perhaps one entity per paragraph).
Accepting. Doing this right now--for localization and so that we can resolve some problems we are having (Cf. 81991 and others) with RDF in the table of contents
Status: NEW → ASSIGNED
Summary: The help system should be XUL-ified → The help system should be XUL-ified and all text externalized to entities
removing nsbranch keyword. It would be nuts to make the help pages themselves XUL, and the xul-ification of the TOC, though a good idea, is going to have to wait a while longer.
Not XULifying the help, but the issues would be addressed by using XHTML. Cf. bug 95770.
Status: ASSIGNED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.