New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a document index #2726
Add a document index #2726
Conversation
Note that another search possibility would be as described in: |
Yes, that's definitely a related issue worth mention. I think there are good use cases for both ways of searching the document. If we are talking about some more sophisticated global document search where we can add search markup similar to the index terms – allowing search to produce intelligent results for things like "Real", "der", or "+" – then I think it could work well for the HTML versions. The PDF, however, would still benefit from an old-school document index. |
Although both terms seems to be in use, 'escape sequence' seems to be the more generally recognized one.
What you see is related to #2713, but to avoid getting a dependency on #2713 being fixed in general, I'll resolve this particular case as part of this PR in favor of base-clock partition. |
To me, these are different enough that I find it natural to not have them all under class. |
Besides not being a first use, it seems like we are generally not using \emph or \willintroduce in this introductory section.
Fixed. These are now grouped under either |
OK, I've now use a non-normative mention of |
Having addressed or responded to all review comments, made a grouping sweep through the index myself, and not having any ideas for how to make the HTML index more accessible without attacking the LaTeXML XSLT files, I am now removing the Draft state to indicate that I don't plan to add anything substantial unless requested by reviewers. |
Well, that entire chapter is about connections and connector so I think it's fine to reference a use in the non-normative introduction. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems ok in general.
There are some minor details that we can improve later, but better to have it in place.
Could now merge except for the conflicts. |
Ready. |
Despite recent work on styling the HTML, my colleagues still refuse to use it in their daily work due to the lack of document search. The PDF document, on the other hand, can be searched with varying degree of success depending on choice of PDF reader. Still, many of the most important terms to search for have so many occurrences in the text that it is hard even for a good document search function to guid the reader to the most important places in the document.
With this PR, I'd like to explore the possibility to address this by adding a document index. To start with, I plan to cover these categories of terms:
\firstuse{…}
Real
,StateSelect
, …)sin
,fill
, …)Inline
,Dialog
, …), but not their member names to avoid index clutterstart
,stateSelect
, …)Language constructs (start value, when-clause, …)Misc: deprecated, quality of implementation, translation, simulator (or remove uses)Then, I plan to somehow make the index easily accessible (ideally more accessible than listed at the end of the table of contents) when reading the HTML, so that it can act as some sort of replacement for a document search function.