glossaries package FAQ
Why doesn’t the new glossaries package create command names for the acronyms like the old glossary package?
There are a number of reasons:
- The new way of accessing terms using commands like
\glsis more compatible with standard LaTeX syntax.
- Each term would require a command for the single as well as plural term, as well as commands to generate the upper case versions. For a large glossary that can amount to a lot of extra commands.
- Provision would also be needed to allow for the optional arguments, which is awkward as commands such as
\glshave 2 optional arguments, one before and one after the mandatory argument. Without the mandatory argument, you would need to use an empty optional first argument if you want to use the second argument, which is a nuisance.
- You need to explicitly add a space after a command name that doesn’t have a mandatory argument. (Don’t rely on xspace, there are issues with that package that have led David Carlisle, the package author, to deprecate its use.)
\oldacronymwhich emulates the old glossary package’s syntax, but be aware of the drawbacks. See the section Upgrading From the glossaries Package in the glossaries documentation.
Alternative link: https://www.dickimaw-books.com/faq.php?itemlabel=oldacronym