-
Notifications
You must be signed in to change notification settings - Fork 2
Rules/Recommendations for a Glossary/Terminology #71
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
Labels
Comments
Some guidelines could be added to "Glossary" under Outline of a manual > Books. |
for the sake of automatic alphabetical ordering for the translations, please advise to use |
Closing this as the changes have been merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A glossary (or glossary list) is a part in our documents that defines unknown, ambiguous, or overloaded terms. However, this is not clearly defined in our styleguide nor do we have some good recommendations.
It would be nice if we could have a set of common rules. I would propose:
glosssee
/glossseealso
or inside the definition withxref
? When should we use one or the other?glosssee
orglossseealso
.glosssee
is mostly used for synonyms (Link, see soft link) whereasglossseealso
is used as some related terms (link, see also file system).glossseealso
references should be sorted alphabetically.glossdiv
for higher ordering?The text was updated successfully, but these errors were encountered: