Open
Bug 287414
Opened 19 years ago
Updated 17 years ago
Use entities to describe menus and dialogs in help documentation
Categories
(SeaMonkey :: Help Documentation, defect)
SeaMonkey
Help Documentation
Tracking
(Not tracked)
NEW
People
(Reporter: iannbugzilla, Assigned: prometeo.bugs)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
11.62 KB,
text/html
|
Details |
See bug 247595 for details but this is something that could be useful for the Suite as well.
Assignee | ||
Comment 1•19 years ago
|
||
Comment 2•19 years ago
|
||
Hmm, would it be better to use entities for the entries in help-toc and help-index1 instead/also? We could then move those files to /content. Using entities in those files would also ensure that entries in .rdf files and headings in xhtml files match. The issues I can think of is the readability and that the amount of entities could affect loading time (guessing). Thoughts?
Comment 3•19 years ago
|
||
(In reply to comment #2) > Hmm, would it be better to use entities for the entries in help-toc and > help-index1 instead/also? We could then move those files to /content. Using > entities in those files would also ensure that entries in .rdf files and > headings in xhtml files match. The issues I can think of is the readability and > that the amount of entities could affect loading time (guessing). Actually, that might even help more than the stuff here (which is a nice idea though as well), as those .rdf are nasty for translation compared to some DTDs ;-) Should be a different bug though, IMO.
Comment 4•19 years ago
|
||
The problem is when someone installs/build the suite without one component. For instance, not installing Composer will produce errors in the Composer files that are in Help.
Updated•17 years ago
|
Component: Help Viewer → Help
Product: Documentation → Mozilla Application Suite
Version: unspecified → Trunk
You need to log in
before you can comment on or make changes to this bug.
Description
•