# Tag Info

5

Table 15.1 in the glossaries user manual shows which of the predefined styles support hierarchical entries. You need to find one which has at least 2 or — (unlimited) in the maximum level column. The glossaries gallery of predefined styles shows samples of all the available styles. Those provided by the glossary-tree and glossary-mcols packages are the best ...

3


3

This seems to be a problem with the way xindy sorts sub-entries. It isn't specific to the glossaries package. Analysis The following is a simpler illustration: \documentclass{article} \usepackage{fontspec} \usepackage{makeidx} \setmainfont{Liberation Serif} \makeindex \newcommand*{\lettergroupDefault}[1]{\lettergroup{#1}} \begin{document} α\index{α} ω\...

2

nonumberlist can also be added to items. E.g. \newglossaryentry{ex}{% name={Example},% description={An example},% nonumberlist,% }%

2

\defglsentryfmt has an optional argument that indicates which glossary this format should govern. If omitted, main is assumed, so you also need to do the same for the new glossary: \defglsentryfmt[symbolslist]{% \let\orgglsarg\glsarg \ifdefempty\glsinsert {}% {% \let\glsarg\glsinsert \let\glsinsert\relax }% \glsgenentryfmt \let\glsarg\...

2

tocloft does only hook into ToC, LoF,LoT and the \listof... types that were defined with tocloft's \newlistof command. The glossaries package uses \printglossary[title=...] to change the optical appearance of the glossary title. Using \protect\centering\glossaryname works for the book class. \documentclass{book} \usepackage{glossaries} \...

2

\glsnamefont only affects how the entry name appears in the glossary. For the default long-short acronym style, only the short form appears in the name field. The long form is put in the description field. Is there an easy way without having to introduce a custom glossary format? Not for the base glossaries package unless you simply put the entire ...

2

Nicola Talbot implemented this fix in the package glosssaries-extra \usepackage[nomain,acronym,xindy,style=long]{glossaries} \usepackage{glossaries-extra}

1

glossaries chokes when sorting; add the sort key. \documentclass{book} \usepackage[nonumberlist,acronyms,section]{glossaries} \makenoidxglossaries \newacronym{svm}{svm}{support vector machine} \newacronym{yw}{yw}{support vector machine} \newglossaryentry{v} { name={$\mathbf{v}$}, sort={v}, description={velocity [km/s]}, } \newglossaryentry{r} {...

1

This issue is related to this issue, where they link to a bug report. The suggested workaround is to add \usepackage{glossaries-extra}. The complete code is then: \documentclass{scrbook} \usepackage{glossaries} \usepackage{glossaries-extra} \makenoidxglossaries \newglossaryentry{lorem}{name={lorem},description={ipsum}} \newglossaryentry{dolor}{name={dolor}...

1

The quick and easy method is to just add the automake option: \documentclass{article} \usepackage{filecontents} \usepackage[acronym,automake]{glossaries} \usepackage[backend=bibtex,bibencoding=ascii]{biblatex} \begin{filecontents*}{example_bib.bib} @ARTICLE{a_reference, author = {A, Name}, title = {A Title}, volume = {1}, pages = {1--2}, ...

1


1

I realise that you've managed to create a MWE and posted that as a separate question, but I thought it might help to answer your question "What can interfere with glossaries to prevent printing?" in a more general way that might be useful to others. There's a Java GUI diagnostic tool called makeglossariesgui that can be used to analyse a document that uses ...

Only top voted, non community-wiki answers of a minimum length are eligible