Hot answers tagged

8

\capitialisewords works by applying \makefirstuc to each space-separated element of its argument. In the case of \capitalisewords{\gls{src}}, there are no spaces in the argument, so it simply does \makefirstuc{\gls{src}}. \makefirstuc applies a set of rules when deciding how to change the case: If the argument starts with a command and that command is ...


4

Using titlecaps package. \documentclass{article} \usepackage{glossaries} \usepackage{titlecaps} \newacronym{srs}{SRS}{spaced repetition system} \begin{document} \titlecap{\glsentrylong{srs}} \end{document} Note that one can use the \Addlcwords{} feature that excludes specified words from being upper-cased. Additionally, it automatically masks out ...


4

Try \setglossarysection{section}, i.e. each glossaries is an unnumbered section instead of a chapter (since book class) is used. The \printnoidxglossaries command might need a \clearpage before, to the the glossaries on a new page (but all of them on the same page) \newcommand{\TWOorONESIDE}{oneside} % According to above twoside/oneside ...


4

\newacronym sets type=\acronymtype unless overridden in the optional argument. The default value of \acronymtype is \glsdefaulttype (usually the main glossary) unless the acronym package option is used, in which case \acronymtype is set to acronym. Since you're manually defining the acronym glossary using \newglossary, the acronyms are put in the main ...


3

Do you mean something like this? If yes, this can be achieved with \defglsentryfmt[type]{...}, whereas the type argument means the glossary type (acronym, main glossary, etc.) and the mandatory argument is used for the typesetting command. For me information on this, see section 6.3 of the glossaries-user manual. \documentclass{book} ...


3

There's no need to keep the glossary entries in the main file -- they can be defined in any file, loaded with \loadglsentries Even \makeglossaries can be written in another file, as long as this file is \input before the document body, however, I prefer \makeglossaries in the real document preamble. foosettings.tex \makeglossaries ...


2

There's no \gls{DRX} or \glsaddall command in the document, that's why no glossaries is printed (and glossaries complains about an empty glossary!) \documentclass[a4paper,openright,12pt]{book} \usepackage{fancyhdr} \usepackage{emptypage} \usepackage{xpatch} \usepackage{float} \fancypagestyle{plain}{\renewcommand{\headrulewidth}{0.5pt} ...


2

Create a document (glosario.tex) with all the definitions, for me most of them are acronyms so I have defined them the following way: \acro{CCTV}{\emph{Close Circuit Television}} You seem to be mixing up packages. glossaries doesn't define \acro. \usepackage[toc]{glossaries} % Load the package with the acronym option This isn't loading the ...


2

To summarise the comments, the original problem (using @gobble as a page style) stems from makeindex not excepting a blank location. Using an empty page style to suppress the page numbering instead will satisfy makeindex but will confuse readers who try to look up the location's entry list since they might have trouble identifying the referenced page number. ...


2

The command \glssetwidest is only provided for the alttree styles (see Tree-Like Styles). The glossary-mcols package provides analogous styles to those in glossary-tree, so \glssetwidest can also be used with the mcolalttree styles, but not with any of the other styles. The simplest solution is to just replace mcolindex with mcolalttree: ...


2

Running on the command line makeglossaries --help one can see the options it knows. Beside other the -d switch: So add -d auxiliaries to the call.


2

I was also looking for a way to make glossaries work with TeXworks (and XeLaTeX in my case). The short answer You can define a new processing tool in TeXworks by Edit > Preferences > Typesetting tab > Processing tools. Click on the + to give it a name like “makeglossaries”. Under “Program” simply enter makeglossaries and as arguments add one by clicking on ...


2

This isn't merging, but moving from one glossary to another one with \glsmoveentry{label}{target glossary}. Since there is more than one entry (most likely) one could use the \forallglsentries[operator]{\localfoo}{\glsmoveentry{\localfoo}{symbol}} command, to move all entries from, say, operator to symbol. The \localfoo is an 'arbitrary' command ...


1

Another approach is to get makeindex to merge them. For example, suppose the following document is called test.tex: \documentclass{article} \usepackage[T1]{fontenc} \usepackage[nomain,nonumberlist]{glossaries} \newglossary[sog]{symbol}{soi}{soo}{Symbols} \newglossary[fog]{operator}{foi}{foo}{Operators} \makeglossaries ...


1

Remove the spaces in the sort key values: \documentclass{report} \usepackage{lipsum} \usepackage[]{hyperref} \usepackage[acronym,nogroupskip,nonumberlist,nopostdot,toc]{glossaries} \makenoidxglossaries \newglossaryentry{thetab} {% name={$\Theta_{b}$}, description={temperature coefficient for b}, sort=temperaturecoefficientforb, } ...


1

I'm not sure why the standard sort order isn't working, but it works fine if you switch to letter: \documentclass{report} \usepackage{lipsum} \usepackage[]{hyperref} \usepackage[acronym,nogroupskip,nonumberlist,nopostdot,toc]{glossaries} \makenoidxglossaries \newglossaryentry{thetab} {% name={$\Theta_{b}$}, description={temperature coefficient for b}, ...


1

glossaries redefines \number locally (probably not a really good idea) and this breaks the farsi numbers. You can get around it like this (but I don't know if this will give the correct output in the glossaries). But imho you should make a bug report for glossaries, quite a number of languages try to change the number format and rely on the \number ...


1

No \gls{foo} or \glsaddall → no displayed glossary entry for this key. Use nonumberlist to suppress the page number at the end of the displayed glossary entry. \documentclass{article} \usepackage[acronym,nomain,nonumberlist]{glossaries} \makeglossaries \newacronym{ny}{NY}{New York} \newacronym{la}{LA}{Los Angeles} \newacronym{un}{UN}{United Nations} ...



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