From 2a62139c9c5e9ae2cf691e316bf2176114e0a3c5 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Fri, 10 Jun 2016 21:46:03 +0000 Subject: glossaries (10jun16) git-svn-id: svn://tug.org/texlive/trunk@41343 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf-dist/doc/latex/glossaries/CHANGES | 29 + Master/texmf-dist/doc/latex/glossaries/README | 4 +- .../doc/latex/glossaries/glossaries-code.pdf | Bin 1145409 -> 1159914 bytes .../doc/latex/glossaries/glossaries-user.html | 10545 ++++++++++--------- .../doc/latex/glossaries/glossaries-user.pdf | Bin 747359 -> 757969 bytes .../doc/latex/glossaries/glossaries-user.tex | 274 +- .../doc/latex/glossaries/glossariesbegin.html | 392 +- .../doc/latex/glossaries/glossariesbegin.pdf | Bin 155729 -> 156546 bytes .../doc/latex/glossaries/glossariesbegin.tex | 17 +- .../doc/latex/glossaries/glossary2glossaries.html | 4 +- .../doc/latex/glossaries/glossary2glossaries.pdf | Bin 142444 -> 142444 bytes .../doc/latex/glossaries/glossary2glossaries.tex | 2 +- .../samples/glossary-lipsum-examples.pdf | Bin 252930 -> 252930 bytes .../doc/latex/glossaries/samples/minimalgls.pdf | Bin 49969 -> 49969 bytes .../doc/latex/glossaries/samples/mwe-acr-desc.pdf | Bin 37969 -> 37969 bytes .../doc/latex/glossaries/samples/mwe-acr.pdf | Bin 33661 -> 33661 bytes .../doc/latex/glossaries/samples/mwe-gls.pdf | Bin 29951 -> 29951 bytes .../doc/latex/glossaries/samples/sample-FnDesc.pdf | Bin 58829 -> 58829 bytes .../glossaries/samples/sample-chap-hyperfirst.pdf | Bin 54834 -> 54834 bytes .../latex/glossaries/samples/sample-crossref.pdf | Bin 53468 -> 53468 bytes .../glossaries/samples/sample-custom-acronym.pdf | Bin 82200 -> 82200 bytes .../latex/glossaries/samples/sample-dot-abbr.pdf | Bin 52723 -> 52723 bytes .../doc/latex/glossaries/samples/sample-dual.pdf | Bin 36467 -> 36467 bytes .../latex/glossaries/samples/sample-entrycount.pdf | Bin 36851 -> 36851 bytes .../latex/glossaries/samples/sample-entryfmt.pdf | Bin 34916 -> 34916 bytes .../latex/glossaries/samples/sample-font-abbr.pdf | Bin 50715 -> 50715 bytes .../latex/glossaries/samples/sample-ignored.pdf | Bin 31821 -> 31821 bytes .../doc/latex/glossaries/samples/sample-index.pdf | Bin 43388 -> 43388 bytes .../doc/latex/glossaries/samples/sample-inline.pdf | Bin 147062 -> 147100 bytes .../latex/glossaries/samples/sample-langdict.pdf | Bin 38866 -> 38866 bytes .../latex/glossaries/samples/sample-newkeys.pdf | Bin 39209 -> 39209 bytes .../glossaries/samples/sample-noidxapp-utf8.pdf | Bin 96013 -> 96013 bytes .../latex/glossaries/samples/sample-noidxapp.pdf | Bin 67092 -> 67092 bytes .../glossaries/samples/sample-nomathhyper.pdf | Bin 41759 -> 41759 bytes .../latex/glossaries/samples/sample-numberlist.pdf | Bin 41990 -> 41990 bytes .../doc/latex/glossaries/samples/sample-prefix.pdf | Bin 43273 -> 43273 bytes .../doc/latex/glossaries/samples/sample-si.pdf | Bin 21722 -> 21722 bytes .../samples/sample-storage-abbr-desc.pdf | Bin 39905 -> 39905 bytes .../glossaries/samples/sample-storage-abbr.pdf | Bin 37671 -> 37671 bytes .../doc/latex/glossaries/samples/sample.pdf | Bin 102731 -> 102765 bytes .../doc/latex/glossaries/samples/sample4col.pdf | Bin 43333 -> 43333 bytes .../doc/latex/glossaries/samples/sampleAcr.pdf | Bin 65517 -> 65517 bytes .../doc/latex/glossaries/samples/sampleAcrDesc.pdf | Bin 65625 -> 65625 bytes .../latex/glossaries/samples/sampleCustomAcr.pdf | Bin 93623 -> 93623 bytes .../doc/latex/glossaries/samples/sampleDB.pdf | Bin 47055 -> 47055 bytes .../doc/latex/glossaries/samples/sampleDesc.pdf | Bin 48407 -> 48407 bytes .../doc/latex/glossaries/samples/sampleEq.pdf | Bin 155610 -> 155768 bytes .../doc/latex/glossaries/samples/sampleEqPg.pdf | Bin 169071 -> 169225 bytes .../latex/glossaries/samples/sampleFnAcrDesc.pdf | Bin 91354 -> 91354 bytes .../doc/latex/glossaries/samples/sampleNtn.pdf | Bin 98697 -> 98727 bytes .../doc/latex/glossaries/samples/samplePeople.pdf | Bin 47470 -> 47470 bytes .../doc/latex/glossaries/samples/sampleSec.pdf | Bin 65680 -> 65680 bytes .../doc/latex/glossaries/samples/sampleSort.pdf | Bin 95077 -> 95108 bytes .../doc/latex/glossaries/samples/sampleaccsupp.pdf | Bin 41167 -> 41167 bytes .../latex/glossaries/samples/sampleacronyms.pdf | Bin 37213 -> 37213 bytes .../doc/latex/glossaries/samples/sampletree.pdf | Bin 66925 -> 66925 bytes .../doc/latex/glossaries/samples/sampleutf8.pdf | Bin 44951 -> 44951 bytes .../doc/latex/glossaries/samples/samplexdy.pdf | Bin 178688 -> 178814 bytes .../doc/latex/glossaries/samples/samplexdy2.pdf | Bin 68412 -> 68412 bytes 59 files changed, 6012 insertions(+), 5255 deletions(-) (limited to 'Master/texmf-dist/doc/latex/glossaries') diff --git a/Master/texmf-dist/doc/latex/glossaries/CHANGES b/Master/texmf-dist/doc/latex/glossaries/CHANGES index c31ec8da62a..9fd001d8ea1 100644 --- a/Master/texmf-dist/doc/latex/glossaries/CHANGES +++ b/Master/texmf-dist/doc/latex/glossaries/CHANGES @@ -1,5 +1,34 @@ glossaries change log: +v4.25: + + * glossaries.sty: + + - bug fix + http://www.dickimaw-books.com/cgi-bin/bugtracker.cgi?action=view&key=111 + +v4.24: + + * glossaries.sty: + + - added debug and seenoindex option + + - added \GlsSetWriteIstHook and \GlsSetQuote + + - added \@gls@extramakeindexopts for makeglossaries + and makeglossaries-lite.lua (allow makeindex -g + for German documents) + + * makeglossaries (2.19): + + - Improved check in &parse_for_xindy_nosort + + - Added check for \@gls@extramakeindexopts + + * makeglossaries-lite.lua (1.2): + + - Added check for nil codepage + v4.23 * glossaries.sty: diff --git a/Master/texmf-dist/doc/latex/glossaries/README b/Master/texmf-dist/doc/latex/glossaries/README index 97dedef1eec..b90ca7f2629 100644 --- a/Master/texmf-dist/doc/latex/glossaries/README +++ b/Master/texmf-dist/doc/latex/glossaries/README @@ -1,6 +1,6 @@ -LaTeX Package : glossaries v4.23 +LaTeX Package : glossaries v4.25 -Last Modified : 2016-04-30 +Last Modified : 2016-06-09 Author : Nicola Talbot diff --git a/Master/texmf-dist/doc/latex/glossaries/glossaries-code.pdf b/Master/texmf-dist/doc/latex/glossaries/glossaries-code.pdf index d2587c180d1..e72684ba528 100644 Binary files a/Master/texmf-dist/doc/latex/glossaries/glossaries-code.pdf and b/Master/texmf-dist/doc/latex/glossaries/glossaries-code.pdf differ diff --git a/Master/texmf-dist/doc/latex/glossaries/glossaries-user.html b/Master/texmf-dist/doc/latex/glossaries/glossaries-user.html index 3b0beb53267..94b4699fca1 100644 --- a/Master/texmf-dist/doc/latex/glossaries/glossaries-user.html +++ b/Master/texmf-dist/doc/latex/glossaries/glossaries-user.html @@ -10,7 +10,7 @@ - + -

-

+

-

+

-

-

User Manual for glossaries.sty v4.23 +

+

User Manual for glossaries.sty v4.25

-

2016-04-30

+

2016-06-09

-

+

-

-

+

Abstract

-

The

The glossaries package provides a means to define terms or abbreviations or symbols that can be referenced within your document. Sorted lists with collated locations can be generated either using TEX or using a supplementary indexing application. -

Additional features not provided here may be available through the supplemental package +

Additional features not provided here may be available through the supplemental package glossaries-extra which, if required, needs to be installed separately. New features will be added to glossaries-extra. Any new versions of the glossaries package after v4.21 will be just bug +class="cmss-10">glossaries-extra. Versions of the glossaries package after v4.21 will mostly be just bug fixes. -

+

-

If you require multilingual support you must also separately install the relevant language +

If you require multilingual support you must also separately install the relevant language module. Each language module is called glossaries-language⟩, where ⟨§1.3 Multi-Lingual Support for further details. -

The

The glossaries package requires a number of other packages including, but not limited to, tracklangEX distribution? or Updating TEX on Linux.) -

Documents have wide-ranging styles when it comes to presenting glossaries or lists of +

Documents have wide-ranging styles when it comes to presenting glossaries or lists of terms or notation. People have their own preferences and to a large extent this is determined by the kind of information that needs to go in the glossary. They may just have symbols with terse descriptions or they may have long technical @@ -341,15 +341,15 @@ words with complicated descriptions. The glossaries package is flexible enough to accommodate such varied requirements, but this flexibility comes at a price: a big manual. -

😱 If you’re freaking out at the size of this manual, start with

😱 If you’re freaking out at the size of this manual, start with glossariesbegin.pdf (“The glossaries package: a guide for beginnners”). You should find it in the same directory as this document or try texdoc glossariesbegin.pdf. Once you’ve got to grips with the basics, then come back to this manual to find out how to adjust the settings.

-

-

The

+

The glossaries bundle comes with the following documentation:

glossaries-code.pdf
Advanced users wishing to know more about the inner workings of all the packages provided in the glossaries bundle should read “Documented - Code for glossaries v4.23”. + Code for glossaries v4.25”.
INSTALL
Change log. class="cmbx-10">README
Package summary.
-

Related resources:

+

Related resources:

-

If you use

If you use hyperref and glossaries, you must load doc’s changes glossary.) -

If you are using

If you are using hyperref, it’s best to use pdflatexpdflatex deals with hyperlinks much better. If you use th problems where you have long hyperlinks or hyperlinks in subscripts or superscripts. This is an issue with the DVI format not with glossaries.

-

+

@@ -921,7 +921,8 @@ class="newline" />A Java GUI alternative to makeglossaries that also provides diagnostic tools. - Available separately on CTAN.
CTAN.

o. Depending on the font, the backslash character may appear as a dash when used in the main document text, so \foo will appear as: —foo. -

Earlier versions of

Earlier versions of glossaries used this technique to write information to the files used by the indexing applications to prevent problems caused by fragile commands. @@ -1042,9 +1043,9 @@ href="#glo:indexingapp">indexing application with multilingual support writt class="newline" /> -

1.

1. Introduction

-

The

The glossaries package is provided to assist generating lists of terms, symbols or abbreviations (glossaries). It has a certain amount of flexibility, allowing the user to customize the format of the glossary and define multiple glossaries. It also supports glossary @@ -1054,7 +1055,7 @@ used1.1 in the document will be added to the glossary. -

This package replaces the glossary package which is now obsolete. Please see the document “Upgrading from the glossary package to the glossaries package” for assistance in upgrading. -

One of the strengths of this package is its flexibility, however the drawback of this is the +

One of the strengths of this package is its flexibility, however the drawback of this is the necessity of having a large manual that covers all the various settings. If you are daunted by the size of the manual, try starting off with the much shorter guide for beginners. -

There’s a common misconception that you have to have Perl installed in order to use +

There’s a common misconception that you have to have Perl installed in order to use the glossaries package. Perl is not a requirement but it does increase the available @@ -1075,8 +1076,8 @@ options, particularly if you use an extended Latin alphabet or a non-Latin alphabet.
-

-

The basic idea behind the

+

The basic idea behind the glossaries package is that you first define your entries (terms, symbols or abbreviations). Then you can reference these within your document (like \cite or @@ -1090,7 +1091,7 @@ class="description">Option 1: -

This is the simplest option but it’s slow and if you want a sorted list, it doesn’t +

This is the simplest option but it’s slow and if you want a sorted list, it doesn’t work well for extended Latin alphabets or non-Latin alphabets. However, if you @@ -1109,7 +1110,7 @@ class="cmss-10">sanitizesort=false\’elite if sanitizesort=true is used. -

This option works best with the

This option works best with the sort=def setting. For any other setting, be prepared for a long document build time, especially if you have a lot of entries @@ -1126,9 +1127,9 @@ href="#sec:newglosentry">Defining Glossary Entries



\printnoidxglossary

-

+

where you want your list of entries to appear (described in §10 Option 2: -

This option uses a 

This option uses a command line interface (CLI) application called makeindexmakeindexLATEX then reads this file in on the next run. -

This option works best if you want to sort entries according to the English alphabet and +

This option works best if you want to sort entries according to the English alphabet and you don’t want to install Perl.

  1. Add \makeglossaries to your preamble (before you start defining your - entries, as described in If you want to use makeindex’s -g option you must change the quote character + using \GlsSetQuote. For example: + + +
    + \GlsSetQuote{+} +
    +

    This must be used before \makeglossaries. Note that if you are using + babel, the shorthands aren’t enabled until the start of the document, + so you won’t be able to use the shorthands in definitions made in the + preamble. +

  2. +
  3. Add \makeglossaries to your preamble (before you start defining your entries, as + described in §4 Defining Glossary Entries).
  4. Put -


    Put +


    \printglossary

    -

    +

    where you want your list of entries to appear (described in §10 Displaying a glossary).

  5. Run LATRun LATEX on your document. This creates files with the extensions .glo and myDoc.ist). If you look at your yet.
  6. Run Run makeindex with the with the .glo file as the input file and the .ist file as the style so that it creates an output file with the extension .gls. If you have access to a command: -
    +
    makeindex -s myDoc.ist -o myDoc.gls myDoc.glo
    -

    (Replace

    (Replace myDoc with the base name of your LATEX document file. Avoid spaces in the file name.) If you don’t know how to use the command prompt, then you can probably access makeindex via your text editor, but each editor has a different + id="dx1-4035"> via your text editor, but each editor has a different method of doing this, so I can’t give a general description. You will have to check your editor’s manual. -

    The default sort is word order (“sea lion” comes before “seal”). If you want letter +

    The default sort is word order (“sea lion” comes before “seal”). If you want letter ordering you need to add the -l switch: +class="cmtt-10">-l switch:

    -
    +
    makeindex -l -s myDoc.ist -o myDoc.gls myDoc.glo
    -

    (See

    (See §1.4.4 Using makeindex explicitly (Option 2) for further details on using + id="dx1-4037"> explicitly (Option 2) for further details on using makeindex explicitly.) + id="dx1-4038"> explicitly.)

  7. Once you have successfully completed the previous step, you can now run + class="enumerate" id="x1-4040x6">Once you have successfully completed the previous step, you can now run LATEX on your document again.
-

This is the default option (although you still need to use

This is the default option (although you still need to use \makeglossaries to ensure the glossary files are created).

@@ -1269,11 +1294,11 @@ class="description">Option 3: -

This option uses a 

This option uses a CLI application called xindy to sort the entries. This application is + id="dx1-4041"> to sort the entries. This application is more flexible than makeindex and is able to sort extended Latin alphabets or @@ -1281,48 +1306,48 @@ href="#glo:exlatinalph">extended Latin alphabets or href="#glo:nonlatinalph">non-Latin alphabets. The xindy application comes with T application comes with TEX Live but not with MiKTEX. Since xindy is a Perl script, if you are using MiKT is a Perl script, if you are using MiKTEX you will not only need to install xindy, you will also need to install Perl. In a similar way to + id="dx1-4044">, you will also need to install Perl. In a similar way to Option 2, this option involves making LATEX write the glossary information to a temporary file which xindy reads. Then reads. Then xindy writes a new file containing + id="dx1-4046"> writes a new file containing the code to typeset the glossary. LATEX then reads this file in on the next run. -

This is the best option if you want to sort according to a language other than English or +

This is the best option if you want to sort according to a language other than English or if you want non-standard location lists.

  1. Add the Add the xindy option to the option to the glossaries package option list: -
    +
    \usepackage[xindy]{glossaries}
    -

    +

  2. Add Add \makeglossaries to your preamble (before you start defining your entries, as described in §4 Defining Glossary Entries).
  3. Run LATRun LATEX on your document. This creates files with the extensions .glo and myDoc.xdy). If you look at your yet.
  4. Run Run xindy with the with the .glo file as the input file and the .xdy file as a module so that it creates an output file with the extension .gls. You also need to set the line): -
    +
    xindy -L english -C utf8 -I xindy -M myDoc  
    -t myDoc.glg -o myDoc.gls myDoc.glo
    -

    (Replace

    (Replace myDoc with the base name of your LATEX document file. Avoid spaces in the file name. If necessary, also replace english with the name of your language and utf8 with your input encoding, for example, -L german -C din5007-utf8.) If +class="cmtt-10">-L german -C din5007-utf8.) If you don’t know how to use the command prompt, then you can probably access xindy via your text editor, but each editor has a different method of doing this, so + id="dx1-4059"> via your text editor, but each editor has a different method of doing this, so I can’t give a general description. You will have to check your editor’s manual. -

    The default sort is word order (“sea lion” comes before “seal”). If you want letter +

    The default sort is word order (“sea lion” comes before “seal”). If you want letter ordering you need to add the order=letter package option: + id="dx1-4060"> package option:

    -
    +
    \usepackage[xindy,order=letter]{glossaries}
    -

    (and return to the previous step.) See

    (and return to the previous step.) See §1.4.3 Using xindy explicitly (Option 3) for + id="dx1-4061"> explicitly (Option 3) for further details on using xindy explicitly. + id="dx1-4062"> explicitly.

  5. Once you have successfully completed the previous step, you can now run + class="enumerate" id="x1-4064x5">Once you have successfully completed the previous step, you can now run LATEX on your document again.
-

For Options 

For Options 2 and 3, it can be difficult to remember all the parameters required for makeindex or or xindy, so the , so the glossaries package provides a Perl script called makeglossaries + id="dx1-4067"> that reads the .aux file to determine what settings you have used and will then run makeindex or or xindy. Again, this is a command line application and can be run in a terminal + id="dx1-4069">. Again, this is a command line application and can be run in a terminal or command prompt. For example, if your LATEX document is in the file myDoc.tex, then @@ -1434,10 +1463,10 @@ run:

-
+
makeglossaries myDoc
-

(Replace

(Replace myDoc with the base name of your LATEX document file. Avoid spaces in the file name.) This is described in more detail in §1.4 Generating the Associated Glossary Files. -

If you don’t have Perl installed you can use the Lua script instead: +

If you don’t have Perl installed you can use the Lua script instead:

-
+
makeglossaries-lite.lua myDoc
-

This script doesn’t have the full functionality of the Perl script, but since modern +

This script doesn’t have the full functionality of the Perl script, but since modern TEX distributions come with Lua, you shouldn’t need to install anything extra to make it run. Remember that since xindy is also a Perl script, if you want to use is also a Perl script, if you want to use xindy you’ll + id="dx1-4071"> you’ll need Perl installed anyway, so there’s no point using this Lua script if you’re using xindy. -

The . +

The .gls and .glo are temporary files created to help build your document. You should not edit or explicitly input them. However, you may need to delete them if something goes wrong and you need to do a fresh build.
-

-

An overview of these three options is given in

+

An overview of these three options is given in table 1.1.

-


Table 1.1: Glossary Options: Pros and Cons
+class="content">Glossary Options: Pros and Cons

OptionOption 3

Requires +class="td11">

Requires an external application?

Requires +class="td11">

Requires Perl?

Can +class="td11">

Can sort extended @@ -1553,7 +1582,7 @@ class="td11">

Efficient +class="td11">

Efficient sort algorithm?

Can +class="td11">

Can use a different @@ -1581,7 +1610,7 @@ class="td11">

Can +class="td11">

Can form ranges in @@ -1596,7 +1625,7 @@ class="td11">

Can +class="td11">

Can have non-standard locations @@ -1612,7 +1641,7 @@ class="td11">

Maximum +class="td11">

Maximum hierarchical depth

Unlimited 3 Unlimited

\glsdisplaynumberlist + id="dx1-4074"> reliable?

\newglossaryentry + id="dx1-4075"> restricted to preamble?

Requires +class="td11">

Requires additional write registers?

Default +class="td11">

Default value of sanitizesort + id="dx1-4076"> package option

true
-

Strips standard LATEX accents (that is, accents generated by core LATEX commands) so, for example, \AA is treated the same as A. + id="dx1-4077"> is treated the same as A.


-

This document uses the

This document uses the glossaries package. For example, when viewing the PDF version of this document in a hyperlinked-enabled PDF viewer (such as Adobe Reader or Okular) if you click on the word “xindy” you’ll be taken to the entry in the glossary where there’s a brief + id="dx1-4078">” you’ll be taken to the entry in the glossary where there’s a brief description of the term “xindy”. -

The remainder of this introductory section covers the following:

+ id="dx1-4079">”. +

The remainder of this introductory section covers the following:

-

Top

1.1 Sample Documents

-

The

The glossaries package is provided with some sample documents that illustrate the various functions. These should be located in the samples subdirectory (folder) @@ -1736,14 +1765,14 @@ href="http://www.dickimaw-books.com/latex/novices/html/terminal.html" >terminal
texdoc -l glossaries
-

+

This should display a list of all the files in the glossaries documentation directory with their full pathnames. -

If you can’t find the sample files on your computer, they are also available from your nearest +

If you can’t find the sample files on your computer, they are also available from your nearest CTAN mirror at http://mirror.ctan.org/macros/latex/contrib/glossaries/samples/. -

The sample documents are as follows

The sample documents are as follows1.2:

@@ -1762,7 +1791,7 @@ class="E">EX either by typing latex minimalgls -

+

in a terminal or by using the relevant button or menu item in your text editor or front-end. This will create the required associated files but you will not see the glossary. If you use PDFLATEX you will also get warnings about non-ex

-
+
pdfTeX warning (dest): name{glo:aca} has been  
referenced but does not exist,  
replaced by a fixed one
-

These warnings may be ignored on the first run. -

If you get a

These warnings may be ignored on the first run. +

If you get a Missing \begin{document} error, then it’s most likely that your version of Generating the Associated Glossary Files). This can be done on a terminal either by typing
makeglossaries minimalgls
-

+

or by typing
perl makeglossaries minimalgls
-

+

If your system doesn’t recognise the command perl then it’s likely you don’t have Perl installed. In which case you will need to use makeindexmakeindex -s minimalgls.ist -t minimalgls.glg -o minimalgls.gls minimalgls.glo -

+

(See §1.4.4 makeindexmakeindex explicitly.) -

Note that if you need to specify the full path and the path contains +

Note that if you need to specify the full path and the path contains spaces, you will need to delimit the file names with the double-quote character.

@@ -1833,10 +1862,10 @@ class="cmtt-10">makeindexRun minimalgls.tex through LATEX again (as step 1) -

You should now have a complete document. The number following each entry in the +

You should now have a complete document. The number following each entry in the glossary is the location number. By default, this is the page number where the entry was referenced. -

There are three other files that can be used as a

There are three other files that can be used as a minimal working example: mwe-gls.tex, Option 1). To create the complete document, you need class="cmtt-10">latex sample-noidx
latex sample-noidx -

+

sample-noidx-utf8.tex
inputenclatex sample-noidx-utf8
latex sample-noidx-utf8 -

+

sample4col.tex
latex sample4col class="cmtt-10">makeglossaries sample4col
latex sample4col -

+

As before, if you don’t have Perl installed, you will need to use makeindexmakeglossaries sampleAcr class="cmtt-10">latex sampleAcr
latex sampleAcr -

+

sampleAcrDesc.tex
makeglossaries sampleAcrDesc class="cmtt-10">latex sampleAcrDesc
latex sampleAcrDesc -

+

sampleDesc.tex
makeglossaries sampleDesc class="cmtt-10">latex sampleDesc
latex sampleDesc -

+

sampleCustomAcr.tex
makeglossaries sampleCustomAcr class="cmtt-10">latex sampleCustomAcr
latex sampleCustomAcr -

+

sampleFnAcrDesc.tex
makeglossaries sampleFnAcrDesc class="cmtt-10">latex sampleFnAcrDesc
latex sampleFnAcrDesc -

+

@@ -2009,7 +2038,7 @@ class="cmtt-10">latex sample-FnDesc class="cmtt-10">makeglossaries sample-FnDesc
latex sample-FnDesc -

+

sample-custom-acronym.tex
latex sample-custom-acronym class="cmtt-10">makeglossaries sample-custom-acronym
latex sample-custom-acronym -

+

sample-crossref.tex
latex sample-crossref class="cmtt-10">makeglossaries sample-crossref
latex sample-crossref -

+

sampleDB.tex
latex sampleDB class="cmtt-10">makeglossaries sampleDB
latex sampleDB -

+

The glossary definitions are stored in the accompanying files database1.tex and makeglossariesmakeindex -s sampleDB.ist -t sampleDB.glg -o sampleDB.gls sampleDB.glo -

+

  • Create the secondary glossary (all on one line): @@ -2084,7 +2113,7 @@ class="cmtt-10">sampleDB.glo class="cmtt-10">makeindex -s sampleDB.ist -t sampleDB.nlg -o sampleDB.not sampleDB.ntn -

    +

  • latex sampleEq class="cmtt-10">makeglossaries sampleEq
    latex sampleEq -

    +

    sampleEqPg.tex
    makeglossaries sampleEqPg class="cmtt-10">latex sampleEqPg
    latex sampleEqPg -

    +

    sampleSec.tex
    makeglossaries sampleSec class="cmtt-10">latex sampleSec
    latex sampleSec -

    +

    sampleNtn.tex
    makeglossaries sampleNtn class="cmtt-10">latex sampleNtn
    latex sampleNtn -

    +

    Note that if you don’t have Perl installed, you will need to use makeindexmakeglossariesmakeindex -s sampleNtn.ist -t sampleNtn.glg -o sampleNtn.gls sampleNtn.glo -

    +

  • Create the secondary glossary (all on one line): @@ -2186,7 +2215,7 @@ class="cmtt-10">sampleNtn.glo class="cmtt-10">makeindex -s sampleNtn.ist -t sampleNtn.nlg -o sampleNtn.not sampleNtn.ntn -

    +

  • makeglossaries sample class="cmtt-10">latex sample
    latex sample -

    +

    You can see the difference between word and letter ordering if you substitute order=wordmakeglossariesmakeindex explicitly, you will need to use the -l switch to +class="cmtt-10">-l switch to indicate letter ordering.) @@ -2229,16 +2259,16 @@ class="cmtt-10">-l switch to sample-inline.tex

    This document is like This document is like sample.tex, above, but uses the inline glossary + id="dx1-5062"> glossary style to put the glossary in a footnote.
    sampletree.tex
    This document illustrates a hierarchical glossary structure where child + id="x1-5063r20"> This document illustrates a hierarchical glossary structure where child entries have different names to their corresponding parent entry. To create the document do:
    latex sampletree class="cmtt-10">makeglossaries sampletree

    latex sampletree -

    +

    sample-dual.tex
    This document illustrates how to define an entry that both appears in + id="x1-5064r21"> This document illustrates how to define an entry that both appears in the list of acronyms and in the main glossary. To create the document do:
    latex sample-dual class="cmtt-10">makeglossaries sample-dual

    latex sample-dual -

    +

    sample-langdict.tex
    This document illustrates how to use the glossaries package to create + id="x1-5065r22"> This document illustrates how to use the glossaries package to create English to French and French to English dictionaries. To create the document do:
    latex sample-langdict class="cmtt-10">makeglossaries sample-langdict

    latex sample-langdict -

    +

    samplexdy.tex
    This document illustrates how to use the This document illustrates how to use the glossaries package with xindy + id="dx1-5067"> instead of makeindex. The document uses UTF8 encoding (with the . The document uses UTF8 encoding (with the inputenc package). + id="dx1-5069"> package). The encoding is picked up by makeglossaries. By default, this document will + id="dx1-5070">. By default, this document will create a xindy style file called style file called samplexdy.xdy, but if you uncomment the lines -
    +
    \setStyleFile{samplexdy-mc}  
    \noist  
    \GlsSetXdyLanguage{}
    -

    it will set the style file to

    it will set the style file to samplexdy-mc.xdy instead. This provides an additional letter group for entries starting with “Mc” or “Mac”. If you use makeglossaries, you don’t + id="dx1-5072">, you don’t need to supply any additional information. If you don’t use makeglossaries, you will + id="dx1-5073">, you will need to specify the required information. Note that if you set the style file to samplexdy-mc.xdy you must also specify \noist, otherwise the , otherwise the glossaries package will overwrite samplexdy-mc.xdy and you will lose the “Mc” letter group. -

    To create the document do: +

    To create the document do:
    latex samplexdy
    makeglossaries samplexdy
    latex samplexdy
    -

    +

    If you don’t have Perl installed, you will have to call xindy explicitly instead of using + id="dx1-5075"> explicitly instead of using makeglossaries. If you are using the default style file . If you are using the default style file samplexdy.xdy, then do (no line breaks):
    xindy -L english -C utf8 -I xindy -M samplexdy -t samplexdy.glg -o samplexdy.gls samplexdy.glo
    -

    +

    otherwise, if you are using samplexdy-mc.xdy, then do (no line breaks):
    xindy -I xindy -M samplexdy-mc -t samplexdy.glg -o samplexdy.gls samplexdy.glo
    -

    +

    samplexdy2.tex
    This document illustrates how to use the This document illustrates how to use the glossaries package where the location numbers don’t follow a standard format. This example will only work with xindy. To create the document do: + id="dx1-5078">. To create the document do:
    pdflatex samplexdy2
    makeglossaries samplexdy2
    pdflatex samplexdy2
    -

    +

    If you can’t use makeglossaries then you need to do (all on one line): + id="dx1-5079"> then you need to do (all on one line):
    xindy -L english -C utf8 -I xindy -M samplexdy2 -t samplexdy2.glg -o samplexdy2.gls samplexdy2.glo
    -

    +

    See §11.2 Locations and Number lists< sampleutf8.tex

    This is another example that uses This is another example that uses xindy. Unlike . Unlike makeindex, , xindy can + id="dx1-5083"> can cope with non-Latin characters. This document uses UTF8 encoding. To create the + id="dx1-5084">s. This document uses UTF8 encoding. To create the document do:
    latex sampleutf8 @@ -2413,23 +2443,23 @@ class="cmtt-10">latex sampleutf8
    class="cmtt-10">makeglossaries sampleutf8
    latex sampleutf8 -

    +

    If you don’t have Perl installed, you will have to call xindy explicitly instead of using + id="dx1-5085"> explicitly instead of using makeglossaries (no line breaks): + id="dx1-5086"> (no line breaks):
    xindy -L english -C utf8 -I xindy -M sampleutf8 -t sampleutf8.glg -o sampleutf8.gls sampleutf8.glo
    -

    -

    If you remove the

    +

    If you remove the xindy option from option from sampleutf8.tex and do:
    latex sampleutf8 @@ -2437,34 +2467,34 @@ class="cmtt-10">latex sampleutf8
    class="cmtt-10">makeglossaries sampleutf8

    latex sampleutf8 -

    +

    you will see that the entries that start with an extended Latin character now appear in + id="dx1-5088"> now appear in the symbols group, and the word “manœuvre” is now after “manor” instead of before it. If you are unable to use makeglossaries, the call to , the call to makeindex is as follows (no line + id="dx1-5090"> is as follows (no line breaks):
    makeindex -s sampleutf8.ist -t sampleutf8.glg -o sampleutf8.gls sampleutf8.glo
    -

    +

    sample-index.tex
    This document uses the This document uses the glossaries package to create both a glossary and an index. This requires two makeglossaries calls to ensure the document is up to date: + id="dx1-5092"> calls to ensure the document is up to date:
    latex sample-index @@ -2476,33 +2506,33 @@ class="cmtt-10">latex sample-index
    class="cmtt-10">makeglossaries sample-index

    latex sample-index -

    +

    sample-newkeys.tex
    This document illustrates how add custom keys (using This document illustrates how add custom keys (using \glsaddkey).
    sample-storage-abbr.tex
    This document illustrates how add custom storage keys (using + id="x1-5094r28"> This document illustrates how add custom storage keys (using \glsaddstoragekey).
    sample-storage-abbr-desc.tex
    An extension of the previous example where the user + id="x1-5095r29"> An extension of the previous example where the user needs to provide a description.
    sample-chap-hyperfirst.tex
    This document illustrates how to add a custom key using + id="x1-5096r30"> This document illustrates how to add a custom key using \glsaddstoragekey and hook into the \glstext-like mechanism used to sample-font-abbr.tex

    This document illustrates how to different fonts for abbreviations + id="x1-5097r31"> This document illustrates how to different fonts for abbreviations within the style.
    sample-numberlist.tex
    This document illustrates how to reference the This document illustrates how to reference the number list in the + id="dx1-5099"> in the document text. This requires an additional LATEX run:
    makeglossaries sample-numberlist class="cmtt-10">latex sample-numberlist

    latex sample-numberlist -

    +

    samplePeople.tex
    This document illustrates how you can hook into the standard sort + id="x1-5100r33"> This document illustrates how you can hook into the standard sort mechanism to adjust the way the sort key is set. This requires an additional run to ensure the table of contents is up-to-date:
    makeglossaries samplePeople class="cmtt-10">latex samplePeople

    latex samplePeople -

    +

    sampleSort.tex
    This is another document that illustrates how to hook into the standard + id="x1-5101r34"> This is another document that illustrates how to hook into the standard sort mechanism. An additional run is required to ensure the table of contents is up-to-date: @@ -2567,28 +2597,28 @@ class="cmtt-10">makeglossaries sampleSort class="cmtt-10">latex sampleSort
    latex sampleSort -

    +

    sample-nomathhyper.tex
    This document illustrates how to selectively enable and disable + id="x1-5102r35"> This document illustrates how to selectively enable and disable entry hyperlinks in \glsentryfmt. + id="dx1-5103">.
    sample-entryfmt.tex
    This document illustrates how to change the way an entry is + id="x1-5104r36"> This document illustrates how to change the way an entry is displayed in the text.
    sample-prefix.tex
    This document illustrates the use of the This document illustrates the use of the glossaries-prefix package. + id="dx1-5106"> package. An additional run is required to ensure the table of contents is up-to-date:
    makeglossaries sample-prefix class="cmtt-10">latex sample-prefix

    latex sample-prefix
    -

    +

    sampleaccsupp.tex
    This document uses the experimental This document uses the experimental glossaries-accsupp package. The + id="dx1-5108"> package. The symbol is set to the replacement text. Note that some PDF viewers don’t use the accessibility support. Information about the glossaries-accsupp package can be found in @@ -2618,17 +2648,17 @@ href="#sec:accsupp">Accessibility Support. sample-ignored.tex
    This document defines an ignored glossary for common terms that + id="x1-5109r39"> This document defines an ignored glossary for common terms that don’t need a definition.
    sample-entrycount.tex
    This document uses This document uses \glsenableentrycount and and \cgls (described + id="dx1-5112"> (described in §14.1 Counting the Number of Times an Entry has been Used acronyms.
    -

    +

    -

    Top

    1.2 Dummy Entries for Testing

    -

    In addition to the sample files described above,

    In addition to the sample files described above, glossaries also provides some files containing lorum ipsum dummy entries. These are provided for testing purposes and are on TThese entries use the user1 key to store an URL associated with the entry. -

    The sample file

    The sample file glossary-lipsum-examples.tex in the doc/latex/glossaries/samples directory uses all these files. See also http://www.dickimaw-books.com/gallery/#glossaries. -

    +

    -

    Top

    1.3 Multi-Lingual Support

    -

    As from version 1.17, the

    As from version 1.17, the glossaries package can now be used with xindy -

    +
    \documentclass[frenchb]{article}  
    \usepackage[utf8]{inputenc}  
    \usepackage[T1]{fontenc}  
    \usepackage{babel}  
    \usepackage[xindy]{glossaries}
    -

    -

    Note that although a 

    +

    Note that although a non-Latin character, such as é, looks like a plain character in your tex file, with standard LATEX it’s actually a macro and problems. You may need to switch off the field expansions with \glsnoexpandfields. This issue doesn’t occur with XeLaTeX. -

    If you use a 

    If you use a non-Latin character (or other expandable) character at the start of an entry name, you must place it in a group, or it will cause a problem for commands that convert the @@ -2812,11 +2842,11 @@ class="cmtt-10"> or class}}

    -

    +

    (For further details, see the section “UTF-8” section in the mfirstuc user manual.) -

    If you use the

    If you use the inputenc package, xindymakeglossaries, you may need to specify the encoding using the -C option. Read the -C option. Read the xindy manual for further + id="dx1-7017"> manual for further details. -

    +

    As from v4.24, if you are writing in German (for example, using the ngerman package or +babel with the ngerman package option), and you want to use makeindex’s -g option, you’ll +need to change makeindex’s quote character using: +


    \GlsSetQuote  \GlsSetQuote{character}

    +

    +Note that ⟨character⟩ may not be one of ? (question mark), | (pipe) or ! (exclamation mark). +For example: + + +

    +
    +\GlsSetQuote{+} +
    +

    This must be done before \makeglossaries and any entry definitions. It’s only applicable +for makeindex. This option in conjunction with ngerman will also cause makeglossaries to +use the -g switch when invoking makeindex. +

    Be careful of babel’s shorthands. These aren’t switched on until the start of the +document, so any entries defined in the preamble won’t be able to use those shorthands. +However, if you define the entries in the document and any of those shorthands happen to be +special characters for makeindex or xindy (such as the double-quote) then this will interfere +with code that tries to escape any of those characters that occur in the sort key. +
    +

    +

    In general, it’s best not to use babel’s shorthands in entry definitions. For example: + +

    -

    +\documentclass{article} + 
    \usepackage[ngerman]{babel} + 
    \usepackage{glossaries} + 
    \GlsSetQuote{+} + 
    \makeglossaries + 
    \newglossaryentry{rna}{name={ribonukleins\"aure}, + 
      sort={ribonukleins"aure}, + 
      description={eine Nukleins\"aure}} + 
    \begin{document} + 
    \gls{rna} + 
    \printglossaries + 
    \end{document} +

    +

    +

    The ngerman package has the shorthands on in the preamble, so they can be used if +\GlsSetQuote has changed the makeindex quote character. Example: + + +

    +
    +\documentclass{article} + 
    \usepackage[ngerman]{babel} + 
    \usepackage{glossaries} + 
    \GlsSetQuote{+} + 
    \makeglossaries + 
    \newglossaryentry{rna}{name={ribonukleins"aure}, + 
      description={eine Nukleins"aure}} + 
    \begin{document} + 
    \gls{rna} + 
    \printglossaries + 
    \end{document} +
    +

    +

    +

    +

    Top

    1.3.1 Changing the Fixed Names

    -

    The fixed names are produced using the commands listed in

    The fixed names are produced using the commands listed in table 1.2. If you aren’t using a language package such as babeltranslate=babel -

    +
    \documentclass[english,french]{article}  
    \usepackage{babel}  
    \usepackage[translate=babel]{glossaries}
    -

    and then use

    and then use babel’s caption hook mechanism. Note that if you pass the language options directly to babel -


    @@ -2931,22 +3077,22 @@ id="TBL-3-3" />Command Name

    Translator Key Word

    Purpose

    \glossaryname

    Glossary

    Title +class="td10">

    Title of the main @@ -2956,9 +3102,9 @@ class="td10">

    Title class="td01">\acronymname

    Acronyms

    Title +class="td10">

    Title of the list @@ -2977,11 +3123,11 @@ class="cmss-10">acronym\entryname

    Notation (glossaries)

    Header +class="td10">

    Header for first column @@ -3003,11 +3149,11 @@ class="td10">

    Header class="td01">\descriptionname

    Description (glossaries)

    Header +class="td10">

    Header for second column @@ -3029,11 +3175,11 @@ class="td10">

    Header class="td01">\symbolname

    Symbol (glossaries)

    Header +class="td10">

    Header for symbol column @@ -3052,13 +3198,13 @@ class="td10">

    Header class="td01">\pagelistname

    Page List (glossaries)

    Header +class="td10">

    Header for page list @@ -3077,11 +3223,11 @@ class="td10">

    Header class="td01">\glssymbolsgroupname

    Symbols (glossaries)

    Header +class="td10">

    Header for symbols section @@ -3100,11 +3246,11 @@ class="td10">

    Header class="td01">\glsnumbersgroupname

    Numbers (glossaries)

    Header +class="td10">

    Header for numbers section @@ -3125,7 +3271,7 @@ class="td10">

    Header


    -

    As from version 4.12, multilingual support is provided by separate language modules that +

    As from version 4.12, multilingual support is provided by separate language modules that need to be installed in addition to installing the glossaries package. You only need to install the modules for the languages that you require. If the language module has an @@ -3139,7 +3285,7 @@ class="cmss-10">glossaries are now provided by the appropriate language module. For further details about information specific to a given language, please see the documentation for that language module. -

    Examples of use:

    +

    Examples of use:

    -

    Due to the varied nature of glossaries, it’s likely that the predefined translations may not +

    Due to the varied nature of glossaries, it’s likely that the predefined translations may not be appropriate. If you are using the babel package and the \deftranslation) and load it using \usedictionary. -

    Note that the

    Note that the translator dictionaries are loaded at the beginning of the document, so it won’t have any effect if you put translatorbeamer documentation.)
    -

    -

    Your custom dictionary doesn’t have to be just a translation from English to another +

    +

    Your custom dictionary doesn’t have to be just a translation from English to another language. You may prefer to have a dictionary for a particular type of document. For example, suppose your institution’s in-house reports have to have the glossary labelled as “Nomenclature” and the page list should be labelled “Location”, then you can create a file @@ -3233,32 +3379,32 @@ called, say,

    -
    +
    myinstitute-glossaries-dictionary-English.dict
    -

    that contains the following: +

    that contains the following:

    -
    +
    \ProvidesDictionary{myinstitute-glossaries-dictionary}{English}  
    \deftranslation{Glossary}{Nomenclature}  
    \deftranslation{Page List (glossaries)}{Location}
    -

    You can now load it using: +

    You can now load it using:

    -
    +
    \usedictionary{myinstitute-glossaries-dictionary}
    -

    (Make sure that

    (Make sure that myinstitute-glossaries-dictionary-English.dict can be found by TEX.) If you want to share your custom dictionary, you can upload it to CTAN. -

    If you are using

    If you are using babel and don’t want to use the translatortranslate=babel -

    + -

    -

    Note that

    +

    Note that xindy provides much better multi-lingual support than Xindy (Option 3) for further

    Creating a New Language Module
    -

    The

    The glossaries package now uses the tracklang package to determine which language modules @@ -3306,7 +3452,7 @@ need to be loaded. If you want to create a new language module, you should first tracklang documentation. -

    To create a new language module, you need to at least create two files:

    To create a new language module, you need to at least create two files: glossaries-lang.ldf @@ -3322,12 +3468,12 @@ class="cmss-10">translator (for example, English). -

    Here’s an example of

    Here’s an example of glossaries-dictionary-English.dict:

    -
    +
    \ProvidesDictionary{glossaries-dictionary}{English}  
    \providetranslation{Glossary}{Glossary}  
    \providetranslation{Acronyms}{Acronyms} @@ -3338,7 +3484,7 @@ class="cmtt-10">glossaries-dictionary-English.dict:  
    \providetranslation{Symbols (glossaries)}{Symbols}  
    \providetranslation{Numbers (glossaries)}{Numbers}
    -

    You can use this as a template for your dictionary file. Change

    You can use this as a template for your dictionary file. Change English to the translator name @@ -3349,12 +3495,12 @@ class="cmtt-10">.dict) and, for each \providetranslation, change the second argument to the appropriate translation. -

    Here’s an example of

    Here’s an example of glossaries-english.ldf:

    -
    +
    \ProvidesGlossariesLang{english}  
    \glsifusedtranslatordict{English}  
    {% @@ -3413,7 +3559,7 @@ class="cmtt-10">glossaries-english.ldf:  
    \renewcommand*{\glsacrpluralsuffix}{\glspluralsuffix}  
    \renewcommand*{\glsupacrpluralsuffix}{\glstextup{\glspluralsuffix}}
    -

    This is a somewhat longer file, but again you can use it as a template. Replace

    This is a somewhat longer file, but again you can use it as a template. Replace English with the translatorlang⟩. Within the definition of \glossariescaptionslang⟩, replace the English text (such as “Glossaries”) with the appropriate translation. -

    Note: the suffixes used to generate the plural forms when the plural hasn’t been specified are given by \glspluralsuffix (for general entries) and \glsacrpluralsuffix for other acronym styles. These comma set before the entry is defined and so the definitions aren’t included in the caption mechanism as that’s not switched on until the start of the document. This means that the suffix in effect will be for the last loaded language. -

    If you want to add a regional variation, create a file called

    If you want to add a regional variation, create a file called glossaries-iso lang- -

    +
     \ProvidesGlossariesLang{en-GB}  
     \RequireGlossariesLang{english}  
     \glsifusedtranslatordict{British} @@ -3474,20 +3620,20 @@ make the appropriate changes, for example:  
       }%  
     }
    -

    -

    If the translations includes

    +

    If the translations includes non-Latin characters, it’s necessary to provide code that’s independent of the input encoding. Remember that while some users may use UTF-8, others may use Latin-1 or any other supported encoding, but while users won’t appreciate you enforcing your preference on them, it’s useful to provide a UTF-8 version for XeLaTeX users. -

    The

    The glossaries-irish.ldf file provides this as follows:

    -
    +
    \ProvidesGlossariesLang{irish}  
    \glsifusedtranslatordict{Irish}  
    {% @@ -3523,16 +3669,16 @@ class="cmtt-10">glossaries-irish.ldf file provides this as follows:  
      \glossariescaptionsirish  
    }
    -

    (Again you can use this as a template. Replace

    (Again you can use this as a template. Replace irish with your root language label and Irish with the translator dictionary label.) -

    There are now two extra files:

    There are now two extra files: glossaries-irish-noenc.ldf and glossaries-irish-utf8.ldf. -

    These both define

    These both define \glossariescaptionsirish but the *-noenc.ldf uses LATEX accent @@ -3540,7 +3686,7 @@ commands:

    -
    +
    \@ifpackageloaded{polyglossia}%  
    {%  
      \newcommand*{\glossariescaptionsirish}{% @@ -3567,15 +3713,15 @@ commands:  
      }%  
    }
    -

    whereas the

    whereas the *-utf8.ldf replaces the accent commands with the appropriate UTF-8 characters. -

    +

    -

    Top

    1.4 Generating the Associated Glossary Files

    -

    This section is only applicable if you have chosen Options 

    This section is only applicable if you have chosen Options 2 or 3. You can ignore this section if you have chosen name contains any LATEX commands.
    -

    -

    If this section seriously confuses you, and you can’t work out how to run

    +

    If this section seriously confuses you, and you can’t work out how to run makeglossaries or @@ -3603,7 +3749,7 @@ class="cmsy-10">§2.4 Sorting Options, but you will need TEX’s shell escape enabled. -

    In order to generate a sorted glossary with compact

    In order to generate a sorted glossary with compact number lists, it is necessary to use an @@ -3644,7 +3790,7 @@ href="#sec:xindy">§11 Xindy (Option 3). -

    This is a multi-stage process, but there are methods of automating +

    This is a multi-stage process, but there are methods of automating document compilation using applications such as latexmk and ararahttp://www.dickimaw-books.com/latex/thesis/html/build.html for more information.
    -

    -

    The

    +

    The glossaries package comes with the Perl script makeglossarieshttp://www.perl.org/about.html and MiKTeX and Perl scripts (and one Python script). -

    The advantages of using

    The advantages of using makeglossaries:

      @@ -3749,20 +3895,29 @@ class="cmtt-10">makeglossaries when makeindex is used. -
    + id="dx1-10038"> is used. (xindy uses the order of the attributes + list to determine which format should take precedence. See \GlsAddXdyAttribute -

    As from version 4.16, the §11.2 Locations and Number lists.) + +

    As from version 4.16, the glossaries package also comes with a Lua script called makeglossaries-lite.lua. This is a . This is a trimmed-down alternative to the makeglossaries Perl + id="dx1-10041"> Perl script. It doesn’t have some of the options that the Perl version has and it doesn’t attempt to diagnose any problems, but since modern TEX distributions come with LuaTmakeglossaries-lite.lua so it’s an alternative to so it’s an alternative to makeglossaries if you want to use + id="dx1-10043"> if you want to use Option 2 (makeindex). -

    Whilst I strongly recommended that you use the ). +

    If things go wrong and you can’t work out why your glossaries aren’t being generated +correctly, you can use makeglossariesgui as a diagnostic tool. Once you’ve fixed the +problem, you can then go back to using makeglossaries or makeglossaries-lite.lua. +

    Whilst I strongly recommended that you use the makeglossaries Perl script or the + id="dx1-10048"> Perl script or the makeglossaries-lite.lua Lua script, it is possible to use the Lua script, it is possible to use the glossaries package without using those applications. However, note that some commands and package options have no effect if you explicitly run makeindex//xindy. These are listed in + id="dx1-10051">. These are listed in table 1.3. -

    If you are choosing not to use

    If you are choosing not to use makeglossaries because you don’t want to install Perl, + id="dx1-10052"> because you don’t want to install Perl, you will only be able to use makeindex as as xindy also requires Perl. (Other useful Perl + id="dx1-10054"> also requires Perl. (Other useful Perl scripts include epstopdf and latexmk, so it’s well-worth the effort to install Perl.)
    -

    -

    Note that if any of your entries use an entry that is not referenced outside +

    +

    Note that if any of your entries use an entry that is not referenced outside the glossary, you will need to do an additional makeglossaries, , makeindex or + id="dx1-10056"> or xindy run, as appropriate. For example, suppose you have defined the following + id="dx1-10057"> run, as appropriate. For example, suppose you have defined the following entries:1.4 + id="x1-10058f4">

    -
    +
    \newglossaryentry{citrusfruit}{name={citrus fruit},  
    description={fruit of any citrus tree. (See also  
    \gls{orange})}}  
    \newglossaryentry{orange}{name={orange},  
    description={an orange coloured fruit.}}
    -

    and suppose you have

    and suppose you have \gls{citrusfruit} in your document but don’t reference the orange entry, then the orange entry won’t appear in your glossary until yo first create the glossary and then do another run of makeglossaries, , makeindex + id="dx1-10061"> or xindy. For example, if the document is called . For example, if the document is called myDoc.tex, then you must do:
    latex myDoc class="cmtt-10">makeglossaries myDoc

    latex myDoc
    -

    +

    (Note that if you use glossaries-extra, this will be done automatically for you if @@ -3873,29 +4040,29 @@ the indexcrossrefs feature is enabled. See the glossaries-extra user guide for further details.) -

    Likewise, an additional

    Likewise, an additional makeglossaries and LAT and LATEX run may be required if the document pages shift with re-runs. For example, if the page numbering is not reset after the table of contents, the insertion of the table of contents on the second LATEX run may push glossary entries across page boundaries, which means that the number lists in the glossary + id="dx1-10064">s in the glossary may need updating. -

    The examples in this document assume that you are accessing

    The examples in this document assume that you are accessing makeglossaries, , xindy or + id="dx1-10066"> or makeindex via a terminal. Windows users can use the MSDOS Prompt which is usually + id="dx1-10067"> via a terminal. Windows users can use the MSDOS Prompt which is usually accessed via the Start->All Programs->Accessories menu. -

    Alternatively, your text editor may have the facility to create a function that will call the +

    Alternatively, your text editor may have the facility to create a function that will call the required application. The article “Glossaries, Nomenclature, List of Symbols and Acronyms” in the “Using EX to Write a PhD Thesis” describes how to do it for TeXWorks. For other editors see the editor’s user manual for further details. -

    If any problems occur, remember to check the transcript files (e.g. 

    If any problems occur, remember to check the transcript files (e.g. .glg or or .alg) for + id="dx1-10069">) for messages.

    -


    @@ -3942,11 +4109,11 @@ messages. class="content">Commands and package options that have no effect when using xindy or + id="dx1-10071"> or makeindex explicitly
    + id="dx1-10072"> explicitly
    Command or Package Option + id="dx1-10074"> +class="cmtt-10">-Mord/letorder
    makeindex xindy
    order=letter use -l -l use -M ord/letorder
    order=word default default
    xindy=={language=langcode} N/A use -L -Llang-C -Ccode
    \GlsSetXdyLanguage{lang} N/A use -L -Llang
    \GlsSetXdyCodePage{code} N/A use -C -Ccode

    -

    Top

    1.4.1 Using the makeglossaries Perl Script

    -

    The

    The makeglossaries script picks up the relevant information from the auxiliary (latex myDoc class="cmtt-10">makeglossaries myDoc
    latex myDoc -

    +

    You may need to explicitly load makeglossaries into Perl:
    perl makeglossaries myDoc
    -

    -

    Windows users: TeX Live on Windows has its own internal Perl interpreter and provides +

    +

    Windows users: TeX Live on Windows has its own internal Perl interpreter and provides makeglossaries.exe as a convenient wrapper for the makeglossaries.) -

    The

    The makeglossaries script attempts to fork the makeglossaries on an operating system that doesn’t support this form of redirection, then you can use the -Q switch to suppress this warning or you can use the -k switch to +class="cmtt-10">-Q switch to suppress this warning or you can use the -k switch to make makeglossaries automatically use the fallback method without attempting + id="dx1-11018"> automatically use the fallback method without attempting the redirection. Without this redirection, the -q (quiet) switch doesn’t work as +class="cmtt-10">-q (quiet) switch doesn’t work as well. -

    You can specify in which directory the

    You can specify in which directory the .aux, , .glo etc files are located using the etc files are located using the -d switch. For example:
    pdflatex -output-directory myTmpDir myDoc class="cmtt-10">makeglossaries -d myTmpDir myDoc
    -

    +

    Note that makeglossaries assumes by default that assumes by default that makeindex//xindy is on your operating + id="dx1-11024"> is on your operating system’s path. If this isn’t the case, you can specify the full pathname using -m +class="cmtt-10">-mpath/to/makeindex⟩ for makeindex or -x or -xpath/to/xindy⟩ for xindy. -

    As from . +

    As from makeglossaries v2.18, if you are using v2.18, if you are using makeindex, there’s a check for + id="dx1-11030">, there’s a check for makeindex’s multiple encap warning. This is where different encap values (location formats) + id="dx1-11031">’s multiple encap warning. This is where different encap values (location formats) are used on the same location for the same entry. For example:

    -
    +
    \documentclass{article}  
    \usepackage{glossaries}  
    \makeglossaries @@ -4187,50 +4366,50 @@ are used on the same location for the same entry. For example:  
    \printglossaries  
    \end{document}
    -

    If you explicitly use

    If you explicitly use makeindex, this will cause a warning and the location list + id="dx1-11032">, this will cause a warning and the location list will be “1, 1”. That is, the page number will be repeated with each format. As from v2.18, makeglossaries will check for this warning and, if found, will attempt + id="dx1-11033"> will check for this warning and, if found, will attempt to correct the problem by removing duplicate locations and retrying. There’s no similar check for xindy as as xindy won’t produce any warning and will simply discard + id="dx1-11035"> won’t produce any warning and will simply discard duplicates. -

    The

    The makeglossaries script contains POD (Plain Old Documentation). If you want, you + id="dx1-11036"> script contains POD (Plain Old Documentation). If you want, you can create a man page for makeglossaries using using pod2man and move the resulting file onto + id="dx1-11038"> and move the resulting file onto the man path. Alternatively do makeglossaries --help for a list of all options or makeglossaries --version for the version number. -

    When upgrading the

    When upgrading the glossaries package, make sure you also upgrade your version of makeglossaries. The current version is 2.18.
    -

    -

    + id="dx1-11039">. The current version is 2.19.

    +

    +

    -

    Top

    1.4.2 Using the makeglossaries-lite.lua Lua Script

    -

    The Lua alternative to the

    The Lua alternative to the makeglossaries Perl script requires a Lua interpreter, which @@ -4247,15 +4426,16 @@ available to the makeglossaries Perl script aren’t available here. (In particular the -d +class="cmtt-10">-d option.) -

    The

    The makeglossaries-lite.lua script can be invoked in the same way as script can be invoked in the same way as makeglossaries + id="dx1-12006"> but you need to remember the .lua extension. For example, if your document is called myDoc.tex, then do makeglossaries-lite.lua myDoc -

    -

    +

    Some of the options available with makeglossaries are also available with + id="dx1-12007"> are also available with makeglossaries-lite.lua. For a complete list of available options, do + id="dx1-12008">. For a complete list of available options, do
    makeglossaries-lite.lua --help
    -

    -

    +

    +

    -

    Top

    1.4.3 Using xindy explicitly (Option 3)

    -

    Xindy comes with THow to use Xindy with MikTeX on TEX on StackExchange. -

    If you want to use

    If you want to use xindy to process the glossary files, you must make sure you have used @@ -4305,10 +4485,10 @@ class="cmss-10">xindy -

    +
    \usepackage[xindy]{glossaries}
    -

    This is required regardless of whether you use

    This is required regardless of whether you use xindy explicitly or whether it’s called @@ -4322,15 +4502,18 @@ class="cmtt-10">makeglossariesguixindy format, so you need to use -I xindy -I xindy not -I +class="cmtt-10">-I tex. -

    To run

    To run xindy type the following in your terminal (all on one line): + id="dx1-13010"> type the following in your terminal (all on one line):
    xindy -L language.glsbase.glo
    -

    +

    where ⟨language⟩ is the required language name, ⟨encoding⟩ is the encoding, ⟨base⟩ is the name of the document without the .tex extension and ⟨ extension and ⟨style⟩ is the name of the xindy style file + id="dx1-13012"> style file without the .xdy extension. The default name for this style file is ⟨ extension. The default name for this style file is ⟨base.xdy but can be + id="dx1-13014"> but can be changed via \setStyleFile{style}. You may need to specify the full path name depending on the current working directory. If any of the file names contain spaces, you must delimit them using double-quotes. -

    For example, if your document is called

    For example, if your document is called myDoc.tex and you are using UTF8 encoding in English, then type the following in your terminal:
    xindy -L english -C utf8 -I xindy -M myDoc -t myDoc.glg -o myDoc.gls myDoc.glo
    -

    -

    Note that this just creates the main glossary. You need to do the same for each of +

    +

    Note that this just creates the main glossary. You need to do the same for each of the other glossaries (including the list of acronyms if you have used the acronym + id="dx1-13016"> package option), substituting .glg, , .gls and and .glo with the relevant extensions. For + id="dx1-13019"> with the relevant extensions. For example, if you have used the acronym package option, then you would need to do: + id="dx1-13020"> package option, then you would need to do:
    xindy -L english -C utf8 -I xindy -M myDoc -t myDoc.alg -o myDoc.acr myDoc.acn
    -

    +

    For additional glossaries, the extensions are those supplied when you created the glossary with \newglossary. -

    Note that if you use . +

    Note that if you use makeglossaries instead, you can replace all those calls to instead, you can replace all those calls to xindy + id="dx1-13023"> with just one call to makeglossaries: + id="dx1-13024">:
    makeglossaries myDoc
    -

    +

    Note also that some commands and package options have no effect if you use xindy explicitly + id="dx1-13025"> explicitly instead of using makeglossaries. These are listed in . These are listed in table 1.3. -

    +

    -

    Top

    1.4.4 Using makeindex explicitly (Option 2)

    -

    If you want to use

    If you want to use makeindex explicitly, you must make sure that you haven’t used the base.gls base.glo -

    +

    where ⟨base⟩ is the name of your document without the .tex\setStyleFile{⟨style}. Note that there are other options, such as -l (letter ordering). See +class="cmtt-10">-l (letter ordering). See the makeindex manual for further details. -

    For example, if your document is called manual for further details. +

    For example, if your document is called myDoc.tex, then type the following at the terminal:
    makeindex -s myDoc.ist -t myDoc.glg -o myDoc.gls myDoc.glo
    -

    +

    Note that this only creates the main glossary. If you have additional glossaries (for example, if you have used the acronym package option) then you must call package option) then you must call makeindex for each glossary, + id="dx1-14012"> for each glossary, substituting .glg, , .gls and and .glo with the relevant extensions. For example, if you have used + id="dx1-14015"> with the relevant extensions. For example, if you have used the acronym package option, then you need to type the following in your terminal: + id="dx1-14016"> package option, then you need to type the following in your terminal:
    makeindex -s myDoc.ist -t myDoc.alg -o myDoc.acr myDoc.acn
    -

    +

    For additional glossaries, the extensions are those supplied when you created the glossary with \newglossary. -

    Note that if you use . +

    Note that if you use makeglossaries instead, you can replace all those calls to instead, you can replace all those calls to makeindex + id="dx1-14019"> with just one call to makeglossaries: + id="dx1-14020">:
    makeglossaries myDoc
    -

    +

    Note also that some commands and package options have no effect if you use makeindex + id="dx1-14021"> explicitly instead of using makeglossaries. These are listed in . These are listed in table 1.3. -

    +

    -

    Top

    1.4.5 Note to Front-End and Script Developers

    -

    The information needed to determine whether to use

    The information needed to determine whether to use xindy or

    The file extensions used by each defined glossary are given by -


    The file extensions used by each defined glossary are given by +


    \@newglossary  out-ext}{in-ext}

    -

    +

    where ⟨in-ext⟩ is the extension of the -

    +
    \@newglossary{main}{glg}{gls}{glo}
    -

    -

    The

    +

    The indexing application’s style file is specified by -



    \@istfilename  \@istfilename{filename}

    -

    +

    The file extension indicates whether to use makeindex.xdy

    Word or letter ordering is specified by: -


    Word or letter ordering is specified by: +


    \@glsorder  \@glsorder{order}

    -

    +

    where ⟨order⟩ can be either word or letter. -

    If

    If xindy should be used, the language and code page for each glossary is specified by -



    \@xdylanguage label}{code}

    -

    +

    where ⟨label⟩ identifies the glossary, ⟨language⟩ is the root language (e.g. makeindex should be used. -

    If

    If Option 1 has been used, the .aux file will contain -



    \@gls@reference{type}{label}{location}

    -

    +

    for every time an entry has been referenced.

    -

    -

    +

    Top

    2. Package Options

    -

    This section describes the available

    This section describes the available glossaries package options. You may omit the =true for boolean options. (For example, acronym is equivalent to acronym=true). -

    Note that ⟨

    Note that ⟨key⟩=⟨value⟩ package options can’t be passed via the document class options. (This includes options where the ⟨value⟩ (such as makeindex) may be passed via the document class options.
    -

    +

    -

    Top

    2.1 General Options

    @@ -4716,11 +4900,14 @@ class="cmss-10">glossaries package. Don’t use this class="cmss-10">glossaries as the warnings are designed to help detect common mistakes (such as forgetting to use \makeglossaries). + id="dx1-17002">). Note that the + debug=true will override this option.
    noredefwarn
    If you load glossaries with a class or another package that already defines glossary related commands, by default glossaries with that suppress those warnings. Other warnings will still be issued unless you use the nowarn option described above. + id="dx1-17005"> option described above. +
    +debug
    Introduced in version 4.24, this boolean option switches on the debug mode. Note that + the debug mode will automatically cancel the nowarn option. Consider the following + example document: + + +
    + \documentclass{article} +  
    \usepackage{glossaries} +  
    \newglossaryentry{sample1}{name={sample1},description={example}} +  
    \newglossaryentry{sample2}{name={sample2},description={example}} +  
    \glsadd{sample2} +  
    \makeglossaries +  
    \begin{document} +  
    \gls{sample1}. +  
    \printglossaries +  
    \end{document} +
    +

    Here, only the sample1 entry has been indexed, even though \glsadd{sample2} + appears in the source code. This is because the associated file is opened by + \makeglossaries, but \glsadd{sample2} has been used before this command. Since + the file isn’t open yet, the information can’t be written to it, which is why the sample2 + entry doesn’t appear in the glossary. +

    This situation doesn’t cause any errors or warnings as it’s perfectly legitimate for a user + to want to use glossaries to format the entries (e.g. abbreviation expansion) but not + display any lists of terms, abbreviations, symbols etc. Without \makeglossaries (or + \makenoidxglossaries) the indexing is suppressed but, other than that, commands + like \gls behave as usual. +

    The debug mode, enabled with the debug option, will write information to the log file + when the indexing can’t occur because the associated file isn’t open. The message is + written in the form +

    +

    Package glossaries Info: wrglossary(⟨type⟩)(⟨line⟩) on input line ⟨line + number⟩.

    +

    where ⟨type⟩ is the glossary label and ⟨line⟩ is the line of text that would’ve been written to + the associated file if it had been open. So if any entries haven’t appeared in the glossary + but you’re sure you used commands like \glsadd or \glsaddall, try switching + on the debug option and see if any information has been written to the log + file. +

    +seenoindex
    Introduced in version 4.24, this option may take one of three values: error, warn or + ignore. The see key automatically indexes the cross-referenced entry using \glsadd. This + means that it suffers from the same problem as the above. If used before + the relevant glossary file has been opened, the indexing can’t be performed. + Since this is easy to miss, the glossaries package by default issues an error + message if the see key is used before \makeglossaries. This option allows + + + you to change the error into just a warning (seenoindex=warn) or ignore it + (seenoindex=ignore).
    nomain
    This suppresses the creation of the main glossary and associated .glo file, if - unrequired. Note that if you use this option, you must create another glossary in - which to put all your entries (either via the acronym (or (or acronyms) package option - described in ) package option described in + §2.5 Acronym Options or via the symbols, , numbers or or index options - described in options described + in §2.6 Other Options or via \newglossary described in described in §12 Defining - New Glossaries). -

    If you don’t use the main glossary and you don’t use this option, Defining New + Glossaries). +

    If you don’t use the main glossary and you don’t use this option, makeglossaries will + id="dx1-17023"> will produce the following warning:

     in glossary
    ’main’? - -
    Remember to glossary.
    If you did actually want to use the main glossary and you see this warning, check that you have referenced the entries in that glossary via commands such as \gls. + id="dx1-17024">.
    -

    +

    sanitizesort
    This is a boolean option that determines whether or not to sanitize the sort + id="dx1-17026"> the sort value when writing to the external glossary file. For example, suppose you define an entry as follows: -
    +
    \newglossaryentry{hash}{name={\#},sort={#},  
     description={hash symbol}}
    -

    The sort value (

    The sort value (#) must be sanitized before writing it to the glossary file, otherwise LATEX will try to interpret it as a parameter reference. If, on the other hand, you @@ -4839,75 +5118,75 @@ class="E">EX will try to interpret it as a parameter

    -
    +
    \newcommand{\mysortvalue}{AAA}  
    \newglossaryentry{sample}{%  
      name={sample},  
      sort={\mysortvalue},  
      description={an example}}
    -

    and you actually want

    and you actually want \mysortvalue expanded, so that the entry is sorted according to AAA, then use the package option sanitizesort=false. -

    The default for Options . +

    The default for Options 2 and 3 is sanitizesort=true, and the default for , and the default for Option 1 is sanitizesort=false. + id="dx1-17029">.

    savewrites
    This is a boolean option to minimise the number of write registers used by the glossaries package. (Default is savewrites=false.) There are only a limited number of + id="dx1-17031">.) There are only a limited number of write registers, and if you have a large number of glossaries or if you are using a class or other packages that create a lot of external files, you may exceed the maximum number of available registers. If savewrites is set, the glossary information will be + id="dx1-17032"> is set, the glossary information will be stored in token registers until the end of the document when they will be written to the external files. If you run out of token registers, you can use etex. -

    This option can significantly slow document compilation. As an alternative, you can + id="dx1-17033">. +

    This option can significantly slow document compilation. As an alternative, you can use the scrwfile package (part of the KOMA-Script bundle) and not use this option. + id="dx1-17034"> package (part of the KOMA-Script bundle) and not use this option.
    -

    -

    You can also reduce the number of write registers by using

    +

    You can also reduce the number of write registers by using Option 1 or by ensuring you define all your glossary entries in the preamble. -

    If you want to use T

    If you want to use TEX’s \write18 mechanism to call mechanism to call makeindex or or xindy from + id="dx1-17037"> from your document and use savewrites, you must create the external files with + id="dx1-17038">, you must create the external files with \glswritefiles before you call makeindex//xindy. Also set . Also set \glswritefiles to nothing or \relax before the end of the document to avoid rewriting the files. For @@ -4915,109 +5194,109 @@ class="cmtt-10">\relax before the end of the document to avoid rewriting

    -
    +
    \glswritefiles  
    \write18{makeindex -s \istfilename\space  
    -t \jobname.glg -o \jobname.gls \jobname}  
    \let\glswritefiles\relax
    -

    -

    +

    +

    translate
    This can take the following values:
    translate=true
    If babel has been loaded and the has been loaded and the translator package is installed, + id="dx1-17044"> package is installed, translator will be loaded and the translations will be provided by the will be loaded and the translations will be provided by the translator + id="dx1-17046"> package interface. You can modify the translations by providing your own dictionary. If the translator package isn’t installed and package isn’t installed and babel is loaded, the + id="dx1-17048"> is loaded, the glossaries-babel package will be loaded and the translations will be provided + id="dx1-17049"> package will be loaded and the translations will be provided using babel’s \addto\captionlanguage⟩ mechanism. If polyglossia has been + id="dx1-17050"> has been loaded, glossaries-polyglossia will be loaded. + id="dx1-17051"> will be loaded.
    translate=false
    Don’t provide translations, even if babel or or polyglossia has been + id="dx1-17054"> has been loaded. (Note that babel provides the command provides the command \glossaryname so that will + id="dx1-17056"> so that will still be translated if you have loaded babel.) + id="dx1-17057">.)
    translate=babel
    Don’t load the translator package. Instead load package. Instead load glossaries-babel. -

    I recommend you use . +

    I recommend you use translate=babel if you have any problems with the + id="dx1-17061"> if you have any problems with the translations or with PDF bookmarks, but to maintain backward compatibility, if babel has been loaded the default is has been loaded the default is translate=true.
    -

    + id="dx1-17063">.

    +

    -

    If

    If translate is specified without a value, is specified without a value, translate=true is assumed. If is assumed. If translate isn’t + id="dx1-17066"> isn’t specified, translate=true is assumed if is assumed if babel, , polyglossia or or translator have been loaded. + id="dx1-17070"> have been loaded. Otherwise translate=false is assumed. -

    See is assumed. +

    See §1.3.1 Changing the Fixed Names for further details. @@ -5026,41 +5305,41 @@ href="#sec:fixednames">Changing the Fixed Names

    The values must be fully expanded, so

    The values must be fully expanded, so don’t try nohypertypes=\acronymtype. You + id="dx1-17076">. You may also use -



    \GlsDeclareNoHyperList{list}

    -

    +

    instead or additionally. See §6 Links to Glossary Entries

    hyperfirst
    This is a boolean option that specifies whether each term has a hyperlink on first use. The default is hyperfirst=true (terms on (terms on first use have a hyperlink, unless explicitly suppressed using starred versions of commands such as \gls* or + id="dx1-17080"> or by identifying the glossary with nohypertypes, described above). Note that + id="dx1-17081">, described above). Note that nohypertypes overrides overrides hyperfirst=true. This option only affects commands that + id="dx1-17083">. This option only affects commands that check the first use flag, such as the \gls-like commands (for example, \gls or + id="dx1-17084"> or \glsdisp), but not the ), but not the \glstext-like commands (for example, \glslink or + id="dx1-17086"> or \glstext). -

    The ). +

    The hyperfirst setting applies to all glossary types (unless identified by setting applies to all glossary types (unless identified by nohypertypes or + id="dx1-17089"> or defined with \newignoredglossary). It can be overridden on an individual basis by + id="dx1-17090">). It can be overridden on an individual basis by explicitly setting the hyper key when referencing an entry (or by using the plus or + id="dx1-17091"> key when referencing an entry (or by using the plus or starred version of the referencing command). -

    It may be that you only want to apply this to just the acronyms (where the first use +

    It may be that you only want to apply this to just the acronyms (where the first use explains the meaning of the acronym) but not for ordinary glossary entries (where the first use is identical to subsequent uses). In this case, you can use hyperfirst=false + id="dx1-17092"> and apply \glsunsetall to all the regular (non-acronym) glossaries. For example:

    -
    +
     \usepackage[acronym,hyperfirst=false]{glossaries}  
     % acronym and glossary entry definitions  
     % at the end of the preamble  
     \glsunsetall[main]
    -

    -

    Alternatively you can redefine the hook -


    +

    Alternatively you can redefine the hook +


    \glslinkcheckfirsthyperhook  \glslinkcheckfirsthyperhook

    -

    +

    which is used by the commands that check the first use flag, such as \gls. Within the + id="dx1-17094">. Within the definition of this command, you can use \glslabel to reference the entry label and + id="dx1-17095"> to reference the entry label and \glstype to reference the glossary type. You can also use to reference the glossary type. You can also use \ifglsused to determine if + id="dx1-17097"> to determine if the entry has been used. You can test if an entry is an acronym by checking if it has the long key set using key set using \ifglshaslong. For example, to switch off the hyperlink on first use + id="dx1-17099">. For example, to switch off the hyperlink on first use just for acronyms:

    -
    +
    \renewcommand*{\glslinkcheckfirsthyperhook}{%  
     \ifglsused{\glslabel}{}%  
     {% @@ -5169,14 +5448,14 @@ class="cmtt-10">\ifglshaslong }%  
    }
    -

    -

    Note that this hook isn’t used by the commands that don’t check the

    +

    Note that this hook isn’t used by the commands that don’t check the first use flag, such as \glstext. (You can, instead, redefine . (You can, instead, redefine \glslinkpostsetkeys, which is used by both + id="dx1-17101">, which is used by both the \gls-like and \glstext-like commands.)

    indexonlyfirst
    This is a boolean option that specifies whether to only add information to the external glossary file on first use. The default is indexonlyfirst=false, which will add a + id="dx1-17103">, which will add a line to the file every time one of the \gls-like or \glstext-like commands are used. Note that \glsadd will always add information to the external glossary + id="dx1-17104"> will always add information to the external glossary file2.1 (since + id="x1-17105f1"> (since that’s the purpose of that command). -

    You can customise this by redefining -


    You can customise this by redefining +


    \glswriteentry  \glswriteentry{label}{wr-code}

    -

    +

    where ⟨label⟩ is the entry’s label and ⟨wr-code⟩ is the code that writes the entry’s @@ -5223,7 +5502,7 @@ class="cmtt-10">\glswriteentry

    -
    +
    \newcommand*{\glswriteentry}[2]{%  
      \ifglsindexonlyfirst  
        \ifglsused{#1}{}{#2}% @@ -5232,57 +5511,57 @@ class="cmtt-10">\glswriteentry  
      \fi  
    }
    -

    This checks the

    This checks the indexonlyfirst package option (using package option (using \ifglsindexonlyfirst) and does ⟨wr-code⟩ if this is false otherwise it only does ⟨wr-code⟩ of the entry hasn’t been used. -

    For example, suppose you only want to index the first use for entries in the

    For example, suppose you only want to index the first use for entries in the acronym glossary and not in the main (or any other) glossary:

    -
    +
    \renewcommand*{\glswriteentry}[2]{%  
     \ifthenelse{\equal{\glsentrytype{#1}}{acronym}}  
     {\ifglsused{#1}{}{#2}}%  
     {#2}%  
    }
    -

    Here I’ve used

    Here I’ve used \ifthenelse to ensure the arguments of \equal are fully expanded before the comparison is made.

    savenumberlist
    This is a boolean option that specifies whether or not to gather and store the number list for each entry. The default is for each entry. The default is savenumberlist=false. (See + id="dx1-17110">. (See \glsentrynumberlist and and \glsdisplaynumberlist in in §9 Using Glossary Terms Without Links.) This is always true if you use Option 1.
    -

    +

    -

    Top

    2.2 Sectioning, Headings and TOC Options

    @@ -5293,19 +5572,19 @@ class="description">Add the glossaries to the table of contents. Note that an ex class="E">EX run is required with this option. Alternatively, you can switch this function on and off using -



    \glstoctrue  \glstoctrue

    -

    +

    and -



    \glstocfalse  \glstocfalse

    -

    +

    numberlinevalue⟩ option. Its value should be the name of a s Unnumbered sectional units will be used by default. Example: -
    +
    \usepackage[section=subsection]{glossaries}
    -

    You can omit the value if you want to use sections, i.e.  +

    You can omit the value if you want to use sections, i.e. 

    -
    +
    \usepackage[section]{glossaries}
    -

    is equivalent to +

    is equivalent to

    -
    +
    \usepackage[section=section]{glossaries}
    -

    You can change this value later in the document using -


    You can change this value later in the document using +


    \setglossarysection  \setglossarysection{name}

    -

    +

    where ⟨name⟩ is the sectional unit. -

    The start of each glossary adds information to the page header via -


    The start of each glossary adds information to the page header via +


    \glsglossarymark  \glsglossarymark{glossary title}

    -

    +

    By default this uses \@mkboth2.22.2 -

    +
    \renewcommand{\glsglossarymark}[1]{\markright{#1}}
    -

    or to prevent it from changing the headers: +

    or to prevent it from changing the headers:

    -
    +
    \renewcommand{\glsglossarymark}[1]{}
    -

    If you want

    If you want \glsglossarymark to use \MakeUppercase in the header, use the ucmark option described below. -

    Occasionally you may find that another package defines

    Occasionally you may find that another package defines \cleardoublepage when it is not required. This may cause an unwanted blank page to appear before each glossary. This can be fixed by redefining \glsclearpage:

    -
    +
    \renewcommand*{\glsclearpage}{\clearpage}
    -

    +

    ucmark\MakeTextUppercase2.3. You can test whether this option has been set or not using -



    \ifglsucmark  true part\else false part\fi

    -

    +

    For example:

    -
    +
    \renewcommand{\glsglossarymark}[1]{%  
      \ifglsucmark  
        \markright{\MakeTextUppercase{#1}}% @@ -5460,7 +5739,7 @@ class="cmtt-10">\fi

     
        \markright{#1}%  
      \fi}
    -

    If

    If memoir has been loaded and ucfirst\section) and is assigned a label (via \label). The label is formed from -



    \glsautoprefix  \glsautoprefix type

    -

    +

    where ⟨type⟩ is the label identifying that glossary. The default value of glossaries using:

    -
    +
    \usepackage[section,numberedsection=autolabel]  
      {glossaries}
    -

    then each glossary will appear in a numbered section, and can be referenced using +

    then each glossary will appear in a numbered section, and can be referenced using something like:

    -
    -

    +

    -

    Top

    2.3 Glossary Appearance Options

    @@ -5623,19 +5902,19 @@ class="cmtt-9"> glossaryentry. -

    If you use this option, you can reference the entry number within the document +

    If you use this option, you can reference the entry number within the document using -



    \glsrefentry  \glsrefentry{label}

    -

    +

    where ⟨label⟩ is the label associated with that glossary entry. -

    If you use

    If you use \glsrefentry, you must run LATEX twice after creating the glossary files using xindy to ensure the cross-references are up-to-date.
    -

    +

    counterwithinglossaryentry counter will be reset every time ⟨value⟩ is incremented. -

    The

    The glossaryentry counter isn’t automatically reset at the start of each glossary, except when glossary section numbering is on and the counter used by counterwithin is the same as the counter used in the glossary’s sectioning command.
    -

    -

    If you want the counter reset at the start of each glossary, you can redefine +

    +

    If you want the counter reset at the start of each glossary, you can redefine \glossarypreamble to use -



    \glsresetentrycounter  \glsresetentrycounter

    -

    +

    which sets glossaryentry to zero:

    -
    +
    \renewcommand{\glossarypreamble}{%  
      \glsresetentrycounter  
    }
    -

    or if you are using

    or if you are using \setglossarypreamble, add it to each glossary preamble, as required. For example:

    -
    +
    \setglossarypreamble[acronym]{%  
      \glsresetentrycounter  
      The preamble text here for the list of acronyms. @@ -5713,7 +5992,7 @@ class="cmtt-10">\setglossarypreamble  The preamble text here for the main glossary.  
    }
    -

    +

    subentrycounterglossary-superglossary-tree. Alternatively, you can set the style using -



    \setglossarystyle{style name}

    -

    +

    (See §15 \printglossary. Example: -

    +
    \usepackage[nostyles]{glossaries}  
    \usepackage{glossary-mcols}  
    \setglossarystyle{mcoltree}
    -

    +

    nonumberlisttrue, this option suppresses the default vertical gap bet class="cmss-10">nogroupskip=false.
    -

    +

    -

    Top

    2.4 Sorting Options

    @@ -5979,7 +6258,7 @@ class="cmss-10">sort=use
    if you want to set this sort method for all your glossaries. -

    This is a ⟨

    This is a ⟨key⟩=⟨value⟩ option where ⟨value⟩ may be one of the following:

    @@ -6012,19 +6291,19 @@ class="cmss-10">usesort key in \newglossaryentry is ignored). -

    Both

    Both sort=def and sort=use set the sort key to a six digit number via -



    \glssortnumberfmt  \glssortnumberfmt{number}

    -

    +

    (padded with leading zeros, where necessary). This can be redefined, if required, before the entries are defined (in the case of sort=defsort=defsort=use).

    -

    Note that the group styles (such as

    Note that the group styles (such as listgroup) are incompatible with the sort=usesort=usesort=def options. -

    The default is

    The default is sort=standard. When the standard sort option is in use, you can hook into the sort mechanism by redefining: -



    \glsprestandardsort  type}{label}

    -

    +

    where ⟨sort cs⟩ is a temporary control sequence that stores the sort value (which was either explicitly set via the xindy special characters is performed. By default \glsprestandardsort just does: -



    \glsdosanitizesort  \glsdosanitizesort

    -

    +

    which sanitizes ⟨sanitizesortsanitizesort=false is used). -

    The other arguments, ⟨

    The other arguments, ⟨type⟩ and ⟨label⟩, are the glossary type and the entry label for the current entry. Note that ⟨\newglossaryentry. -

    Redefining

    Redefining \glsprestandardsort won’t affect any entries that have already been defined and will have no effect at all if you are using sort=defsort=defsort=use.
    -

    +

    -

    Example 1 (Mixing Alphabetical and Order of Definition Sorting) -

    Suppose I have three glossaries:

    Suppose I have three glossaries: main, acronym and notation, and let’s suppose I want @@ -6124,7 +6403,7 @@ class="cmtt-10">main and acronym glossaries to be sorted alphabetically, but the notation type should be sorted in order of definition. -

    For

    For Option 1, I just need to set the sort key in the optional argument of @@ -6134,13 +6413,13 @@ class="cmtt-10">\printnoidxglossary -

    +
    \printnoidxglossary[sort=word]  
    \printnoidxglossary[type=acronym,sort=word]  
    \printnoidxglossary[type=notation,sort=def]
    -

    -

    For Options 

    +

    For Options 2 or 3, I can set the sort to standard (which is the default, but can be @@ -6160,22 +6439,22 @@ class="cmti-10">sort cs⟩ if ⟨type⟩ is notation. -

    The first option can be achieved as follows: +

    The first option can be achieved as follows:

    -
    +
    \newcounter{sortcount}  
    \renewcommand{\glsprestandardsort}[3]{%  
      \stepcounter{sortcount}%  
      \edef#1{\glssortnumberfmt{\arabic{sortcount}}}%  
    }
    -

    The second option can be achieved as follows: +

    The second option can be achieved as follows:

    -
    +
    \newcounter{sortcount}  
    \renewcommand{\glsprestandardsort}[3]{%  
      \ifdefstring{#2}{notation}% @@ -6188,26 +6467,26 @@ class="cmtt-10">notation.  
      }%  
    }
    -

    (

    (\ifdefstring is defined by the etoolbox package.) For a complete document, see the sample file sampleSort.tex.

    -

    -

    ____________________________

    +

    +

    ____________________________

    -

    Example 2 (Customizing Standard Sort (Options 2 or 3)) -

    Suppose you want a glossary of people and you want the names listed as ⟨

    Suppose you want a glossary of people and you want the names listed as ⟨first-name⟩ ⟨surname⟩ in the glossary, but you want the names sorted by ⟨name\name while the sort value is being set. -

    First, define two commands to set the person’s name: +

    First, define two commands to set the person’s name:

    -
    +
    \newcommand{\sortname}[2]{#2, #1}  
    \newcommand{\textname}[2]{#1 #2}
    -

    and

    and \name needs to be initialised to \textname:

    -
    +
    \let\name\textname
    -

    Now redefine

    Now redefine \glsprestandardsort so that it temporarily sets \name to \sortname @@ -6255,7 +6534,7 @@ class="cmti-10">surname⟩ in the text:

    -
    +
    \renewcommand{\glsprestandardsort}[3]{%  
     \let\name\sortname  
     \edef#1{\expandafter\expandonce\expandafter{#1}}% @@ -6263,26 +6542,26 @@ class="cmti-10">surname⟩ in the text:  
     \glsdosanitizesort  
    }
    -

    (The somewhat complicate use of

    (The somewhat complicate use of \expandafter etc helps to protect fragile commands, but care is still needed.) -

    Now the entries can be defined: +

    Now the entries can be defined:

    -
    orderword or letter. The default is word ordering. -

    makeindexxindy.ist extension. -

    You may omit this package option if you are using

    You may omit this package option if you are using Option 2 as this is the default. It’s available in case you need to override the effect of an earlier occurrence of xindymakeindex.xdy extension. -

    This package option may additionally have a value that is a ⟨

    This package option may additionally have a value that is a ⟨key⟩=⟨value⟩ comma-separated list to override the language and codepage. For example:

    -
    +
    \usepackage[xindy={language=english,codepage=utf8}]  
      {glossaries}
    -

    You can also specify whether you want a number group in the glossary. This defaults to +

    You can also specify whether you want a number group in the glossary. This defaults to true, but can be suppressed. For example:

    -
    +
    \usepackage[xindy={glsnumbers=false}]{glossaries}
    -

    If no value is supplied to this package option (either simply writing

    If no value is supplied to this package option (either simply writing xindy or writing xindy={}) then the language, codepage and number group settings are unchanged. See @@ -6462,7 +6741,7 @@ class="E">EX distributions disable it completely, in which case this option won’t have an effect. (If this option doesn’t appear to work, search the log file for “runsystem” and see if it is followed by “enabled” or “disabled”.) -

    Some distributions allow

    Some distributions allow \write18 in a restricted mode. This mode has a limited number of trusted applications, which usually includes makeindexxindy. -

    However even in unrestricted mode this option may not work with

    However even in unrestricted mode this option may not work with xindy as xindymakeglossariesLATEX runs to ensure the document is up-to-date with this setting. -

    Since this package option attempts to run the

    Since this package option attempts to run the indexing application on every LATEX run, its use should be considered a last resort for those who can’t work out @@ -6507,9 +6786,9 @@ class="cmss-10">automake=false -

    +

    -

    Top

    2.5 Acronym Options

    @@ -6521,18 +6800,18 @@ class="cmtt-10">acronym. This is equivalent to: -
    +
    \newglossary[alg]{acronym}{acr}{acn}{\acronymname}
    -

    It will also define -


    It will also define +


    \printacronyms  \printacronyms[options]

    -

    +

    that’s equivalent to

    ] package option compatible-3.07 is used). -

    If you are using

    If you are using Option 1, you need to use

    options]
    to display the list of acronyms. -

    If the

    If the acronym package option is used, \acronymtype\newacronym\acronymtype, unless another glossary is explicitly specified. -

    Remember to use the

    Remember to use the nomain package option if you’re only interested in using this acronym glossary. (That is, you don’t intend to use the main glossary.)
    -

    +

    acronymsmain glossary to also contain a list of acronyms, you can do: -
    +
    \usepackage[acronym,acronymlists={main}]{glossaries}
    -

    No check is performed to determine if the listed glossaries exist, so you can add +

    No check is performed to determine if the listed glossaries exist, so you can add glossaries you haven’t defined yet. For example:

    -
    +
    \usepackage[acronym,acronymlists={main,acronym2}]  
      {glossaries}  
    \newglossary[alg2]{acronym2}{acr2}{acn2}%  
      {Statistical Acronyms}
    -

    You can use -


    You can use +


    \DeclareAcronymList  \DeclareAcronymList{list}

    -

    +

    instead of or in addition to the acronymlists option. This will add the glossaries given in ⟨list⟩ to the list of glossaries that are identified as lists of acronyms. To replace the list of acronym lists with a new list use: -



    \SetAcronymLists  \SetAcronymLists{list}

    -

    -

    You can determine if a glossary has been identified as being a list of acronyms +

    +

    You can determine if a glossary has been identified as being a list of acronyms using: -



    \glsIfListOfAcronyms  }{false part}

    -

    +

    shortcuts§13 Acronyms and Other Abbreviations for further details. Alternatively you can use: -



    \DefineAcronymSynonyms  \DefineAcronymSynonyms

    -

    +

    -

    +

    -

    Top

    2.5.1 Deprecated Acronym Style Options

    -

    The package options listed in this section are now deprecated but are kept for +

    The package options listed in this section are now deprecated but are kept for backward-compatibility. Use \setacronymstyle instead. See \newacronym +

    -

    or (with

    or (with smallcaps)

    -
    +
    \setacronymstyle{long-sc-short-desc}
    -

    or (with

    or (with smaller)

    -
    +
    \setacronymstyle{long-sm-short-desc}
    -

    or (with

    or (with footnote)

    -
    +
    \setacronymstyle{footnote-desc}
    -

    or (with

    or (with footnote and smallcapssmallcaps -

    smallcaps\newacronym +
    \setacronymstyle{long-sc-short}
    -

    or (with

    or (with description)

    -
    +
    \setacronymstyle{long-sc-short-desc}
    -

    or (with

    or (with description and footnotefootnote -

    smallerThis option changes the definition of \newacronym and the way that acronyms are displayed. -

    If you use this option, you will need to include the

    If you use this option, you will need to include the relsize package or otherwise define \textsmaller or redefine \acronymfont.
    -

    +

    This option may be replaced by:

    -
    +
    \setacronymstyle{long-sm-short}
    -

    or (with

    or (with description)

    -
    +
    \setacronymstyle{long-sm-short-desc}
    -

    or (with

    or (with description and footnotefootnote -

    footnote\newacronym +
    \setacronymstyle{footnote}
    -

    or (with

    or (with smallcaps)

    -
    +
    \setacronymstyle{footnote-sc}
    -

    or (with

    or (with smaller)

    -
    +
    \setacronymstyle{footnote-sm}
    -

    or (with

    or (with description)

    -
    +
    \setacronymstyle{footnote-desc}
    -

    or (with

    or (with smallcaps and descriptiondescription -

    dua\newacronym +
    \setacronymstyle{dua}
    -

    or (with

    or (with description)

    -
    +
    \setacronymstyle{dua-desc}
    -

    +

    -

    +

    -

    Top

    2.6 Other Options

    -

    Other available options that don’t fit any of the above categories are: +

    Other available options that don’t fit any of the above categories are:

    symbolsThis option defines a new glossary type with the label symbols via -
    +
    \newglossary[slg]{symbols}{sls}{slo}{\glssymbolsgroupname}
    -

    It also defines -


    It also defines +


    \printsymbols  \printsymbols[options]

    -

    +

    which is a synonym for

    options]
    -

    If you use

    If you use Option 1, you need to use:

    options]
    to display the list of symbols. -

    Remember to use the

    Remember to use the nomain package option if you’re only interested in using this symbols glossary and don’t intend to use the main glossary.
    -

    +

    numbersThis option defines a new glossary type with the label numbers via -
    +
    \newglossary[nlg]{numbers}{nls}{nlo}{\glsnumbersgroupname}
    -

    It also defines -


    It also defines +


    \printnumbers  \printnumbers[options]

    -

    +

    which is a synonym for

    options]
    -

    If you use

    If you use Option 1, you need to use:

    options]
    to display the list of numbers. -

    Remember to use the

    Remember to use the nomain package option if you’re only interested in using this numbers glossary and don’t intend to use the main glossary.
    -

    +

    indexThis option defines a new glossary type with the label index via -
    +
    \newglossary[ilg]{index}{ind}{idx}{\indexname}%
    -

    It also defines -


    It also defines +


    \newterm  options]{term}

    -

    +

    which is a synonym for

    options]
    and -



    \printindex  \printindex[options]

    -

    +

    which is a synonym for

    options]
    -

    If you use

    If you use Option 1, you need to use:

    options]
    to display this glossary. -

    Remember to use the

    Remember to use the nomain package option if you’re only interested in using this glossaries without the index package option.)
    -

    +

    -

    Since the index isn’t designed for terms with descriptions, you might also want to +

    Since the index isn’t designed for terms with descriptions, you might also want to disable the hyperlinks for this glossary using the package option nohypertypes=index or @@ -7132,8 +7411,8 @@ class="cmtt-10">\GlsDeclareNoHyperList{index}
    -

    The example file

    The example file sample-index.tex illustrates the use of the index package @@ -7151,22 +7430,22 @@ class="cmssbx-10">compatible-3.07Compatibility mode for old documents created using version 3.07 or below.

    -

    +

    -

    Top

    2.7 Setting Options After the Package is Loaded

    -

    Some of the options described above may also be set after the

    Some of the options described above may also be set after the glossaries package has been loaded using -



    \setupglossaries  \setupglossaries{key-val list}

    -

    +

    The following package options can’t be used in \setupglossaries: \GlsSetXdyLanguage§11 Xindy (Option 3) for further details). -

    If you need to use this command, use it as soon as possible after loading

    If you need to use this command, use it as soon as possible after loading glossaries otherwise you might end up using it too late for the change to take effect. For example, if you try changing the acronym styles (such as smallcaps -

    +

    -

    -

    +

    Top

    3. Setting Up

    -

    In the preamble you need to indicate whether you want to use

    In the preamble you need to indicate whether you want to use Option 1, Option 2 or Option 3. It’s not possible to mix these options within a document.

    -

    Top

    3.1 Option 1

    -

    The command -


    The command +


    \makenoidxglossaries  \makenoidxglossaries

    -

    +

    must be placed in the preamble. This sets up the internal commands required to make Option 1 work. \makenoidxglossaries none of the glossaries will be displayed. -

    +

    -

    Top

    3.2 Options 2 and 3

    -

    The command -


    The command +


    \makeglossaries  \makeglossaries

    -

    +

    must be placed in the preamble in order to create the customised makeindex\makeglossaries none of the glossary files will be created. -

    Note that some of the commands provided by the

    Note that some of the commands provided by the glossaries package must not be used after \makeglossaries as they are required when creating the customised style file. If you attempt to use those commands after \makeglossaries you will generate an error. -

    Similarly, there are some commands that must not be used before

    Similarly, there are some commands that must not be used before \makeglossaries.

    -

    -

    You can suppress the creation of the customised

    +

    You can suppress the creation of the customised xindy or makeindex style file using -



    \noist  \noist

    -

    +

    That this command must not be used after \makeglossaries. -

    Note that if you have a custom

    Note that if you have a custom .xdy file created when using glossaries version 2.07 or below, you will need to use the compatible-2.07 package option with it.
    -

    -

    The default name for the customised style file is given by

    +

    The default name for the customised style file is given by \jobname.ist.xdyOption 3). This name may be changed using: -



    \setStyleFile  \setStyleFile{name}

    -

    +

    where ⟨name⟩ is the name of the style file without the extension. Note that this command must not be used after \makeglossaries. -

    Each glossary entry is assigned a

    Each glossary entry is assigned a number list that lists all the locations in the document where that entry was used. By default, the location refers to the page number but this may @@ -7352,34 +7631,34 @@ class="cmss-10">counter package option. The default form of the location number assumes a full stop compositor (e.g. 1.2), but if your location numbers use a different compositor (e.g. 1-2) you need to set this using -



    \glsSetCompositor  \glsSetCompositor{symbol}

    -

    +

    For example:

    -
    +
    \glsSetCompositor{-}
    -

    This command must not be used after

    This command must not be used after \makeglossaries. -

    If you use

    If you use Option 3, you can have a different compositor for page numbers starting with an upper case alphabetical character using: -



    \glsSetAlphaCompositor  \glsSetAlphaCompositor{symbol}

    -

    +

    This command has no effect if you use Option 2. For example, if you want number list -

    -

    +

    Top

    4. Defining Glossary Entries

    -

    All glossary entries must be defined before they are used, so it is better to define them in +

    All glossary entries must be defined before they are used, so it is better to define them in the preamble to ensure this. In fact, some commands such as \longnewglossaryentry may only be used in the preamble. See §4.10 Drawbacks With Defining Entries in the Document Environment for a discussion of the problems with defining entries within the document instead of in the preamble. -

    Option 1 enforces the preamble-only restriction on \newglossaryentry.
    -

    -

    Only those entries that are referenced in the document (using any of the commands +

    +

    Only those entries that are referenced in the document (using any of the commands described in §6 §10 Displaying a glossary to find out how to display the glossary. -

    New glossary entries are defined using the command: -


    New glossary entries are defined using the command: +


    \newglossaryentry  label}{key=value list}

    -

    +

    This is a short command, so values in ⟨key-val list⟩ can’t contain any paragraph breaks. If you have a long description that needs to span multiple paragraphs, use -



    \longnewglossaryentry  long description}

    -

    +

    instead. Note that this command may only be used in the preamble. Be careful of unwanted spaces. \longnewglossaryentry will remove trailing spaces in the description (via \unskip) but won’t remove leading spaces (otherwise it would interfere with commands like \Glsentrydesc). -

    There are also commands that will only define the entry if it hasn’t already been +

    There are also commands that will only define the entry if it hasn’t already been defined: -



    \provideglossaryentry  }{key=value list}

    -

    +

    and -

    \longprovideglossaryentry  -



    \longprovideglossaryentry{label}{}{long description}

    -

    +

    (These are both preamble-only commands.) -

    For all the above commands, the first argument, ⟨

    For all the above commands, the first argument, ⟨label⟩, must be a unique label with which -to identify this entry. This can’t contain any non-expandable commands or active -characters. -

    Note that although an This can’t contain any non-expandable commands +or active characters. The reason for this restriction is that the label is used to +construct internal commands that store the associated information (similarly to +commands like \label) and therefore must be able to expand to a valid control sequence +name. +

    Note that although an extended Latin character or other non-Latin character, such as é or ß, looks like a plain character in your .tex file, it’s actually a macro (an active character) + + and therefore can’t be used in the label. (This applies to LATEX rather than XeLaTeX.) Also be careful of babel: or -) to active characters.
    - - -

    -

    The second argument, ⟨

    +

    The second argument, ⟨key=value list⟩, is a ⟨key⟩=⟨value⟩ list that supplies the relevant @@ -7549,37 +7834,37 @@ class="description">The name of the entry (as it will appear in the glossary). I and the parent key is supplied, this value will be the same as the parent’s name. -

    If the

    If the name key contains any commands, you must also use the sort key (described below) if you intend sorting the entries alphabetically, otherwise the entries can’t be sorted correctly.
    -

    +

    description
    A brief description of this term (to appear in the glossary). Within this value, you can use -



    \nopostdesc  \nopostdesc

    -

    +

    to suppress the description terminator for this entry. For example, if this entry is a parent entry that doesn’t require a description, you can do description={\nopostdesc}. If you want a paragraph break in the description use -



    \glspar  \glspar

    -

    +

    or, better, use \longnewglossaryentry. However, note that not all glossary styles support multi-line descriptions. If you are using one of the tabular-like glossary styles @@ -7612,12 +7897,12 @@ class="cmssbx-10">textHow this entry will appear in the document text when using \gls (or one of its + + upper case variants). If this field is omitted, the value of the name key is used. - -

    firstfirstplural\glspl. -

    Note: prior to version 1.13, the default value of firstplural was always taken by @@ -7765,7 +8050,7 @@ class="cmtt-10">\glsprestandardsort§2.4 Sorting Options). -

    Option 1 by default strips the standard LATEX accents (that is, accents generated by @@ -7780,40 +8065,40 @@ href="#option1">Option 1:

    -
    +
    \newglossaryentry{elite}{%  
      name={{\’e}lite},  
      description={select group of people}  
    }
    -

    This is equivalent to: +

    This is equivalent to:

    -
    +
    \newglossaryentry{elite}{%  
      name={{\’e}lite},  
      description={select group of people},  
      sort={elite}  
    }
    -

    Unless you use the package option

    Unless you use the package option sanitizesort=true, in which case it’s equivalent to:

    -
    +
    \newglossaryentry{elite}{%  
      name={{\’e}lite},  
      description={select group of people},  
      sort={\’elite}  
    }
    -

    This will place the entry before the “A” letter group since the sort value starts with a +

    This will place the entry before the “A” letter group since the sort value starts with a symbol. -

    Similarly if you use the

    Similarly if you use the inputenc package:

    @@ -7900,7 +8185,7 @@ class="cmtt-10">}
    Again, this will place the entry before the “A” group. -

    With Options 

    With Options 2 and 3, the default value of sortnamesanitizesort=false). -

    Take care with

    Take care with xindy (name={\alpha}). -

    Take care if you use

    Take care if you use Option 1 and the name contains fragile commands. You will either @@ -7949,7 +8234,7 @@ class="cmss-10">sanitizesort=truedef or use sort methods).

    -

    +

    type§8 Cross-Referencing Entries. -

    This key essentially provides a convenient shortcut that performs

    +

    This key essentially provides a convenient shortcut that performs

    @@ -8065,7 +8350,7 @@ class="cmitt-10"> list⟩}
    after the entry has been defined. -

    For Options 

    For Options 2 and 3, \makeglossariesseedocument environment.
    -

    -

    If you use the

    +

    If you use the see key, you may want to consider using the supplementary glossaries-extra package.

    -

    The following keys are reserved for

    The following keys are reserved for \newacronym (see §4.3 Additional Keys). -

    Avoid using any of the

    -

    -

    Note that if the name starts with

    +

    Note that if the name starts with non-Latin character, you must group the character, otherwise it will cause a problem for commands like -

    +
    \newglossaryentry{elite}{name={{\’e}lite},  
    description={select group or class}}
    -

    Note that the same applies if you are using the

    Note that the same applies if you are using the inputenc package:

    @@ -8184,7 +8469,7 @@ class="cmss-10">fontspecmfirstuc user manual.) -

    Note that in both of the above examples, you will also need to supply the

    Note that in both of the above examples, you will also need to supply the sort key if you are using sanitizesort=true.

    -

    Top

    4.1 Plurals

    -

    You may have noticed from above that you can specify the plural form when you define a +

    You may have noticed from above that you can specify the plural form when you define a term. If you omit this, the plural will be obtained by appending -



    \glspluralsuffix  \glspluralsuffix

    -

    +

    to the singular form. This command defaults to the letter “s”. For example:

    -
    +
    \newglossaryentry{cow}{name=cow,description={a fully grown  
    female of any bovine animal}}
    -

    defines a new entry whose singular form is “cow” and plural form is “cows”. However, if you +

    defines a new entry whose singular form is “cow” and plural form is “cows”. However, if you are writing in archaic English, you may want to use “kine” as the plural form, in which case you would have to do:

    -
    +
    \newglossaryentry{cow}{name=cow,plural=kine,  
    description={a fully grown female of any bovine animal}}
    -

    -

    If you are writing in a language that supports multiple plurals (for a given term) then use +

    +

    If you are writing in a language that supports multiple plurals (for a given term) then use the plural key for one of them and one of the user keys to specify the other plural form. For @@ -8242,24 +8527,24 @@ example:

    -
    +
    \newglossaryentry{cow}{%  
      name=cow,%  
      description={a fully grown female of any bovine animal  
                   (plural cows, archaic plural kine)},%  
      user1={kine}}
    -

    You can then use

    You can then use \glspl{cow} to produce “cows” and \glsuseri{cow} to produce “kine”. You can, of course, define an easy to remember synonym. For example:

    -
    +
    \let\glsaltpl\glsuseri
    -

    Then you don’t have to remember which key you used to store the second plural. +

    Then you don’t have to remember which key you used to store the second plural. Alternatively, you can define your own keys using \glsaddkey, described in §4.3 Additional Keys. -

    If you are using a language that usually forms plurals by appending a different letter, or +

    If you are using a language that usually forms plurals by appending a different letter, or sequence of letters, you can redefine \glspluralsuffix as required. However, this must be done pluralfirstplural key where necessary). -

    +

    -

    Top

    4.2 Other Grammatical Constructs

    -

    You can use the six user keys to provide alternatives, such as participles. For example: +

    You can use the six user keys to provide alternatives, such as participles. For example:

    -
    +
    \let\glsing\glsuseri  
    \let\glsd\glsuserii  
    \newcommand*{\ingkey}{user1} @@ -8301,41 +8586,41 @@ href="#top">Top

      }%  
    }

    -

    With the above definitions, I can now define terms like this: +

    With the above definitions, I can now define terms like this:

    -
    +
    \newword{play}{to take part in activities for enjoyment}  
    \newword[\edkey={ran},\ingkey={running}]{run}{to move fast using  
    the legs}
    -

    and use them in the text: +

    and use them in the text:

    -
    +
    Peter is \glsing{play} in the park today.  
    Jane \glsd{play} in the park yesterday.  
    Peter and Jane \glsd{run} in the park last week.
    -

    -

    Alternatively, you can define your own keys using

    +

    Alternatively, you can define your own keys using \glsaddkey, described below in §4.3 Additional Keys. -

    +

    -

    Top

    4.3 Additional Keys

    -

    You can now also define your own custom keys using the commands described in this section. +

    You can now also define your own custom keys using the commands described in this section. There are two types of keys: those for use within the document and those to store information used behind the scenes by other commands. -

    For example, if you want to add a key that indicates the associated unit for a term, you +

    For example, if you want to add a key that indicates the associated unit for a term, you might want to reference this unit in your document. In this case use \glsaddkey described in §4.5 Storage Keys. -

    In both cases, a new command ⟨

    In both cases, a new command ⟨no link cs⟩ will be defined that can be used to access the value of this key (analogous to commands such as \glsentrytext). This can be used in an @@ -8358,13 +8643,13 @@ The new keys must be added using \glsaddkey or \glsaddstoragekey before glossary entries are defined. -

    +

    -

    Top

    4.4 Document Keys

    -

    A custom key that can be used in the document is defined using: -


    A custom key that can be used in the document is defined using: +


    \glsaddkey  link ucfirst cs}{link allcaps cs}

    -

    +

    where:

    link allcaps cs
    is the control sequence to use analogous to commands like \GLStext.
    -

    The starred version of

    The starred version of \glsaddkey switches on expansion for this key. The unstarred version doesn’t override the current expansion setting. -

    Example 3 (Defining Custom Keys) -

    Suppose I want to define two new keys,

    Suppose I want to define two new keys, ed and ing, that default to the entry text followed by “ed” and “ing”, respectively. The default value will need expanding in both cases, so I @@ -8455,7 +8740,7 @@ need to use the starred form:

    -
    +
     % Define "ed" key:  
     \glsaddkey*  
      {ed}% key @@ -8475,11 +8760,11 @@ need to use the starred form:  
      {\Glsing}% command analogous to \Glstext  
      {\GLSing}% command analogous to \GLStext
    -

    Now I can define some entries: +

    Now I can define some entries:

    -
    +
     % No need to override defaults for this entry:  
     \newglossaryentry{jump}{name={jump},description={}}  
     % Need to override defaults on these entries: @@ -8492,30 +8777,30 @@ need to use the starred form:  
       ing={waddling},%  
       description={}}
    -

    -

    These entries can later be used in the document: +

    +

    These entries can later be used in the document:

    -
    +
    The dog \glsed{jump} over the duck.  
    The duck was \glsing{waddle} round the dog.  
    The dog \glsed{run} away from the duck.
    -

    For a complete document, see the sample file

    For a complete document, see the sample file sample-newkeys.tex.

    -

    -

    ____________________________

    -

    +

    +

    ____________________________

    +

    -

    Top

    4.5 Storage Keys

    -

    A custom key that can be used for simply storing information is defined using: -


    A custom key that can be used for simply storing information is defined using: +


    \glsaddstoragekey  }{no link cs}

    -

    +

    where the arguments are as the first three arguments of \glsaddkey, described above in §4.4 Document Keys. -

    This is essentially the same as

    This is essentially the same as \glsaddkey except that it doesn’t define the additional commands. You can access or update the value of your new field using the commands described in §16.3 Fetching and Updating the Value of a Field. -

    Example 4 (Defining Custom Storage Key (Acronyms and Initialisms)) -

    Suppose I want to define acronyms and other forms of abbreviations, such as initialisms, but I +

    Suppose I want to define acronyms and other forms of abbreviations, such as initialisms, but I want them all in the same glossary and I want the acronyms on first use to be displayed with the short form followed by the long form in parentheses, but the opposite way round for other forms of abbreviations.4.1 -

    Here I can define a new key that determines whether the term is actually an acronym +

    Here I can define a new key that determines whether the term is actually an acronym rather than some other form of abbreviation. I’m going to call this key abbrtype (since type @@ -8563,19 +8848,19 @@ already exists):

    -
    +
    \glsaddstoragekey  
     {abbrtype}% key/field name  
     {word}% default value if not explicitly set  
     {\abbrtype}% custom command to access the value if required
    -

    -

    Now I can define a style that looks up the value of this new key to determine how to +

    +

    Now I can define a style that looks up the value of this new key to determine how to display the full form:

    -
    +
    \newacronymstyle  
     {mystyle}% style name  
     {% Use the generic display @@ -8647,31 +8932,31 @@ display the full form:  
      \renewcommand*{\acrpluralsuffix}{\glspluralsuffix}%  
     }
    -

    Remember that the new style needs to be set before defining any terms: +

    Remember that the new style needs to be set before defining any terms:

    -
    +
    \setacronymstyle{mystyle}
    -

    -

    Since it’s a bit confusing to use

    +

    Since it’s a bit confusing to use \newacronym for something that’s not technically an acronym, let’s define a new command for initialisms:

    -
    +
    \newcommand*{\newinitialism}[4][]{%  
      \newacronym[abbrtype=initialism,#1]{#2}{#3}{#4}%  
    }
    -

    Now the entries can all be defined: +

    Now the entries can all be defined:

    -
    +
    \newacronym{radar}{radar}{radio detecting and ranging}  
    \newacronym{laser}{laser}{light amplification by stimulated  
    emission of radiation} @@ -8680,19 +8965,19 @@ acronym, let’s define a new command for initialisms:  
    \newinitialism{dsp}{DSP}{digital signal processing}  
    \newinitialism{atm}{ATM}{automated teller machine}
    -

    On

    On first use, \gls{radar} will produce “radar (radio detecting and ranging)” but \gls{dsp} will produce “DSP (digital signal processing)”. -

    For a complete document, see the sample file

    For a complete document, see the sample file sample-storage-abbr.tex.

    -

    -

    ____________________________

    -

    In the above example, if

    +

    ____________________________

    +

    In the above example, if \newglossaryentry is explicitly used (instead of through \newacronym) the abbrtype field. -

    Example 5 (Defining Custom Storage Key (Acronyms and Non-Acronyms with Descriptions)) -

    The previous example can be modified if the

    The previous example can be modified if the description also needs to be provided. Here I’ve changed “word” to “acronym”:

    -
    +
    \glsaddstoragekey  
     {abbrtype}% key/field name  
     {acronym}% default value if not explicitly set  
     {\abbrtype}% custom command to access the value if required
    -

    This may seem a little odd for non-abbreviated entries defined using

    This may seem a little odd for non-abbreviated entries defined using \newglossaryentry directly, but \ifglshaslong can be used to determine whether or not to reference the value of this new abbrtype field. -

    The new acronym style has a minor modification that forces the user to specify a +

    The new acronym style has a minor modification that forces the user to specify a description. In the previous example, the line:

    -
    +
       \renewcommand*{\GenericAcronymFields}{description={\the\glslongtok}}%
    -

    needs to be changed to: +

    needs to be changed to:

    -
    +
       \renewcommand*{\GenericAcronymFields}{}%
    -

    Additionally, to accommodate the change in the default value of the

    Additionally, to accommodate the change in the default value of the abbrtype key, all instances of

    -
    +
        \ifglsfieldeq{##1}{abbrtype}{word}
    -

    need to be changed to: +

    need to be changed to:

    -
    +
        \ifglsfieldeq{##1}{abbrtype}{acronym}
    -

    -

    Once this new style has been set, the new acronyms can be defined using the optional +

    +

    Once this new style has been set, the new acronyms can be defined using the optional argument to set the description:

    -
    +
    \newacronym[description={system for detecting the position and  
    speed of aircraft, ships, etc}]{radar}{radar}{radio detecting  
    and ranging}
    -

    -

    No change is required for the definition of

    +

    No change is required for the definition of \newinitialism but again the optional argument is required to set the description:

    -
    +
    \newinitialism[description={mathematical manipulation of an  
    information signal}]{dsp}{DSP}{digital signal processing}
    -

    -

    We can also accommodate contractions in a similar manner to the initialisms: +

    +

    We can also accommodate contractions in a similar manner to the initialisms:

    -
    +
    \newcommand*{\newcontraction}[4][]{%  
      \newacronym[abbrtype=contraction,#1]{#2}{#3}{#4}%  
    }
    -

    The contractions can similarly been defined using this new command: +

    The contractions can similarly been defined using this new command:

    -
    +
    \newcontraction[description={front part of a ship below the  
    deck}]{focsle}{fo’c’s’le}{forecastle}
    -

    -

    Since the custom acronym style just checks if

    +

    Since the custom acronym style just checks if abbrtype is acronym, the contractions will be treated the same as the initialisms, but the style could be modified by a further test of the abbrtype value if required. -

    To test regular non-abbreviated entries, I’ve also defined a simple word: +

    To test regular non-abbreviated entries, I’ve also defined a simple word:

    -
    +
    \newglossaryentry{apple}{name={apple},description={a fruit}}
    -

    -

    Now for a new glossary style that provides information about the abbreviation (in +

    +

    Now for a new glossary style that provides information about the abbreviation (in addition to the description):

    -
    +
    \newglossarystyle  
     {mystyle}% style name  
     {% base it on the "list" style @@ -8837,53 +9122,53 @@ addition to the description):  
           \glossentrydesc{##1}\glspostdescription\space ##2}%  
     }
    -

    This uses

    This uses \ifglshaslong to determine whether or not the term is an abbreviation. If it has an abbreviation, the full form is supplied in parentheses and \abbrtype (defined by \glsaddstoragekey earlier) is used to indicate the type of abbreviation. -

    With this style set, the

    With this style set, the apple entry is simply displayed in the glossary as

    apple
    a fruit.
    -

    but the abbreviations are displayed in the form +

    but the abbreviations are displayed in the form

    laser
    (acronym: light amplification by stimulated emission of radiation) device that creates a narrow beam of intense light.
    -

    (for acronyms) or +

    (for acronyms) or

    DSP
    (initialism: digital signal processing) mathematical manipulation of an information signal.
    -

    (for initalisms) or +

    (for initalisms) or

    fo’c’s’le
    (contraction: forecastle) front part of a ship below the deck.
    -

    (for contractions). -

    For a complete document, see the sample file

    (for contractions). +

    For a complete document, see the sample file sample-storage-abbr-desc.tex.

    -

    -

    ____________________________

    +

    +

    ____________________________

    -

    +

    -

    Top

    4.6 Expansion

    -

    When you define new glossary entries expansion is performed by default, except for the

    When you define new glossary entries expansion is performed by default, except for the name, sort keys (these keys all have expansion suppressed via \glssetnoexpandfield). -

    You can switch expansion on or off for individual keys using -


    You can switch expansion on or off for individual keys using +


    \glssetexpandfield  \glssetexpandfield{field}

    -

    +

    or -



    \glssetnoexpandfield  \glssetnoexpandfield{field}

    -

    +

    respectively, where ⟨field⟩ is the field tag corresponding to the key. In most cases, this is the same as the name of the key except for those listed in table 4.1.

    -


    @@ -9031,31 +9316,31 @@ class="cmtt-10">shortpl

    -

    Any keys that haven’t had the expansion explicitly set using

    Any keys that haven’t had the expansion explicitly set using \glssetexpandfield or \glssetnoexpandfield are governed by -



    \glsexpandfields  \glsexpandfields

    -

    +

    and -



    \glsnoexpandfields  \glsnoexpandfields

    -

    -

    If your entries contain any fragile commands, I recommend you switch off expansion via +

    +

    If your entries contain any fragile commands, I recommend you switch off expansion via \glsnoexpandfields. (This should be used before you define the entries.)

    -

    Top

    4.7 Sub-Entries

    -

    As from version 1.17, it is possible to specify sub-entries. These may be used to order the +

    As from version 1.17, it is possible to specify sub-entries. These may be used to order the glossary into categories, in which case the sub-entry will have a different name to its parent entry, or it may be used to distinguish different definitions for the same word, in which case the sub-entries will have the same name as the parent entry. Note that not all @@ -9074,7 +9359,7 @@ href="#sec:pkgopts-printglos">§2.3 Glossary Appearance Options for further details). -

    Note that the parent entry will automatically be added to the glossary if any of its child +

    Note that the parent entry will automatically be added to the glossary if any of its child entries are used in the document. If the parent entry is not referenced in the document, it will not have a number listmakeindex has a restriction on the maximum sub-entry depth. -

    +

    -

    Top

    4.7.1 Hierarchical Categories

    -

    To arrange a glossary with hierarchical categories, you need to first define the category and +

    To arrange a glossary with hierarchical categories, you need to first define the category and then define the sub-entries using the relevant category entry as the value of the parent key. -

    Example 6 (Hierarchical Categories—Greek and Roman Mathematical Symbols) -

    Suppose I want a glossary of mathematical symbols that are divided into Greek letters +

    Suppose I want a glossary of mathematical symbols that are divided into Greek letters and Roman letters. Then I can define the categories as follows:

    -
    +
    \newglossaryentry{greekletter}{name={Greek letters},  
    description={\nopostdesc}}  
    \newglossaryentry{romanletter}{name={Roman letters},  
    description={\nopostdesc}}
    -

    -

    Note that in this example, the category entries don’t need a description so I have set the +

    +

    Note that in this example, the category entries don’t need a description so I have set the descriptions to \nopostdesc. This gives a blank description and suppresses the description terminator. -

    I can now define my sub-entries as follows: +

    I can now define my sub-entries as follows:

    -
    +
    \newglossaryentry{pi}{name={\ensuremath{\pi}},sort={pi},  
    description={ratio of the circumference of a circle to  
    the diameter}, @@ -9133,19 +9418,19 @@ terminator.  
    description={Euler’s constant},  
    parent=romanletter}
    -

    For a complete document, see the sample file

    For a complete document, see the sample file sampletree.tex.

    -

    -

    ____________________________

    -

    +

    +

    ____________________________

    +

    -

    Top

    4.7.2 Homographs

    -

    Sub-entries that have the same name as the parent entry, don’t need to have the +

    Sub-entries that have the same name as the parent entry, don’t need to have the name key. For example, the word “glossary” can mean a list of technical words or a @@ -9154,20 +9439,20 @@ entry:

    -
    +
    \newglossaryentry{glossary}{name=glossary,  
    description={\nopostdesc},  
    plural={glossaries}}
    -

    Again, the parent entry has no description, so the description terminator needs to be +

    Again, the parent entry has no description, so the description terminator needs to be suppressed using \nopostdesc. -

    Now define the two different meanings of the word: +

    Now define the two different meanings of the word:

    -
    +
    \newglossaryentry{glossarylist}{  
    description={list of technical words},  
    sort={1}, @@ -9177,7 +9462,7 @@ class="cmtt-10">\nopostdescsort={2},  
    parent={glossary}}
    -

    Note that if I reference the parent entry, the location will be added to the parent’s

    Note that if I reference the parent entry, the location will be added to the parent’s number list, whereas if I reference any of the child entries, the location will be added to the child @@ -9200,7 +9485,7 @@ href="#sec:pkgopts-printglos">§2.3 Glossary Appearance Options for further details. -

    In the above example, the plural form for both of the child entries is the same as the +

    In the above example, the plural form for both of the child entries is the same as the parent entry, so the plural key was not required for the child entries. However, if the @@ -9208,7 +9493,7 @@ sub-entries have different plurals, they will need to be specified. For example:

    -
    +
    \newglossaryentry{bravo}{name={bravo},  
    description={\nopostdesc}}  
    \newglossaryentry{bravocry}{description={cry of approval @@ -9222,14 +9507,14 @@ sub-entries have different plurals, they will need to be specified. For example:  
    plural={bravoes},  
    parent=bravo}
    -

    -

    +

    +

    -

    Top

    4.8 Loading Entries From a File

    -

    You can store all your glossary entry definitions in another file and use: -


    You can store all your glossary entry definitions in another file and use: +


    \loadglsentries  type]{filename}

    -

    +

    where ⟨filename⟩ is the name of the file containing all the \newglossaryentry\glsdefaulttype\newglossaryentry uses by default). -

    This is a preamble-only command. You may also use

    This is a preamble-only command. You may also use \input to load the file but don’t use \include. -

    If you want to use

    If you want to use \AtBeginDocument to \input all your entries automatically at the @@ -9284,21 +9569,21 @@ href="#sec:docdefs">§4.10 Drawbacks With Defining Entries in the Document Environment.)
    -

    +

    -

    Example 7 (Loading Entries from Another File) -

    Suppose I have a file called

    Suppose I have a file called myentries.tex which contains:

    -
    +
    \newglossaryentry{perl}{type=main,  
    name={Perl},  
    description={A scripting language}} @@ -9308,14 +9593,14 @@ class="cmtt-10">myentries.tex which contains:  
    name={html},  
    description={A mark up language}}
    -

    and suppose in my document preamble I use the command: +

    and suppose in my document preamble I use the command:

    -
    +
    \loadglsentries[languages]{myentries}
    -

    then this will add the entries

    then this will add the entries tex and html to the glossary whose type is given by main.

    -

    -

    ____________________________

    -

    +

    ____________________________

    +

    Note: if you use \newacronym (see myacronyms.tex contains:

    -
    +
    \newacronym{aca}{aca}{a contrived acronym}
    -

    then (supposing I have defined a new glossary type called

    then (supposing I have defined a new glossary type called altacronym)

    -
    +
    \loadglsentries[altacronym]{myacronyms}
    -

    will add

    will add aca to the glossary type acronym, if the package option acronymacronym4.2 -

    If you have used the

    If you have used the acronym package option, there are two possible solutions to this problem: @@ -9375,35 +9660,35 @@ problem: class="cmtt-10">myacronyms.tex so that entries are defined in the form: -

    +
    \newacronym[type=\glsdefaulttype]{aca}{aca}{a  
    contrived acronym}
    -

    and do: +

    and do:

    -
    +
    \loadglsentries[altacronym]{myacronyms}
    -

    +

  • Temporarily change \acronymtype to the target glossary: -
    +
    \let\orgacronymtype\acronymtype  
    \renewcommand{\acronymtype}{altacronym}  
    \loadglsentries{myacronyms}  
    \let\acronymtype\orgacronymtype
    -

  • -

    Note that only those entries that have been used in the text will appear in the relevant +

    +

    Note that only those entries that have been used in the text will appear in the relevant glossaries. Note also that \loadglsentries may only be used in the preamble. -

    Remember that you can use

    Remember that you can use \provideglossaryentry rather than \newglossaryentryterms.tex) contains:

    -
    +
    \provideglossaryentry{mallard}{name=mallard,  
     description={a type of duck}}
    -

    but suppose your document requires a more detailed description, you can do: +

    but suppose your document requires a more detailed description, you can do:

    -
    +
    \usepackage{glossaries}  
    \makeglossaries  
    \newglossaryentry{mallard}{name=mallard,  
     description={a dabbling duck where the male has a green head}}  
    \loadglsentries{terms}
    -

    Now the

    Now the mallard definition in the terms.tex file will be ignored. -

    +

    -

    Top

    4.9 Moving Entries to Another Glossary

    -

    As from version 3.02, you can move an entry from one glossary to another using: -


    As from version 3.02, you can move an entry from one glossary to another using: +


    \glsmoveentry  label}{target glossary label}

    -

    +

    where ⟨label⟩ is the unique label identifying the required entry and ⟨target glossary label⟩ is the unique label identifying the glossary in which to put the entry. -

    Note that no check is performed to determine the existence of the target glossary. If +

    Note that no check is performed to determine the existence of the target glossary. If you want to move an entry to a glossary that’s skipped by \printglossaries, @@ -9469,15 +9754,15 @@ href="#sec:newglossary">§12 Defining New Glossaries.) -

    Unpredictable results may occur if you move an entry to a different glossary from its +

    Unpredictable results may occur if you move an entry to a different glossary from its parent or children.
    -

    -

    +

    +

    -

    Top

    4.10 Drawbacks With Defining Entries in the Document Environment

    -

    Originally,

    Originally, \newglossaryentry (and \newacronym3 but provides a package option to allow document definitions.) -

    +

    -

    Top

    4.10.1 Technical Issues

    -

    +

    1. If you define an entry mid-way through your document, but subsequently shuffle @@ -9541,7 +9826,7 @@ class="cmtt-10">= character should not be active when using class="cmti-10">key⟩=⟨value⟩ arguments.
    -

    To overcome the first two problems, as from version 4.0 the

    To overcome the first two problems, as from version 4.0 the glossaries package modifies the definition of \newglossaryentry at the beginning of the document environment if it doesn’t already exist. This means that the entry can now be looked up in the glossary, even if the glossary occurs at the beginning of the document. -

    There are drawbacks to this mechanism: if you modify an entry definition, you need a +

    There are drawbacks to this mechanism: if you modify an entry definition, you need a second run to see the effect of your modification; this method requires an extra \newwrite, which may exceed T.glsdefs file when it’s created at the end of the document (and therefore won’t be present on subsequent runs). -

    +

    -

    Top

    4.10.2 Good Practice Issues

    -

    The above section covers technical issues that can cause your document to have compilation +

    The above section covers technical issues that can cause your document to have compilation errors or produce incorrect output. This section focuses on good writing practice. The main reason cited by users wanting to define entries within the document

    When you write technical documents, regardless of whether it’s a PhD thesis or an article +

    When you write technical documents, regardless of whether it’s a PhD thesis or an article for a journal or proceedings, you must plan what you write in advance. If you plan in advance, you should have a fairly good idea of the type of terminology that your document will contain, so while you are planning, create a new file with all your @@ -9600,11 +9885,11 @@ definition.

    -

    -

    +

    Top

    5. Number lists

    -

    Each entry in the glossary has an associated

    Each entry in the glossary has an associated number list. By default, these numbers refer to the pages on which that entry has been used (using any of the commands described in counter package option. The number list is also referred to as the location list. -

    Each location in the

    Each location in the number list is encapsulated with a command. (The encapnumber list with the same location repeated in different fonts. -

    This is something you need to be careful about, but if you use the +

    This is something you need to be careful about, but if you use the makeglossariesxindy\glsnumberformat encap will always have the least precedence. Other conflicting encaps will have the last one override earlier ones for the same location. -

    Due to the asynchronous nature of T

    Due to the asynchronous nature of TEX’s output routine (see, for example, Finding if you’re on an odd or an even page) the xindy preferable.) -

    To compensate, the

    To compensate, the glossaries package has to make some adjustments to ensure the location number is correct for this situation. By default, the adjustments only affect the counter styles: \internal cs name\c@page you need to use: -



    \glsaddprotectedpagefmt  }

    -

    +

    Note that the backslash must be omitted from ⟨internal cs name⟩ and the corresponding command must be able to process a count register as the (sole) argument. -

    For example, suppose you have a style

    For example, suppose you have a style samplenum that is implemented as follows:

    -
    +
     \newcommand*{\samplenum}[1]{%  
       \expandafter\@samplenum\csname c@#1\endcsname}  
     \newcommand*{\@samplenum}[1]{\two@digits{#1}}
    -

    (That is, it displays the value of the counter as a two-digit number.) Then to ensure the +

    (That is, it displays the value of the counter as a two-digit number.) Then to ensure the location is correct for entries in page-spanning paragraphs, you need to do:

    -
    +
    \glsaddprotectedpagefmt{@samplenum}
    -

    (If you are using a different counter for the location, such as

    (If you are using a different counter for the location, such as section or equation, you don’t need to worry about this.) -

    If the inner macro (as given by

    If the inner macro (as given by \internal cs name⟩) contains non-expandable commands then you may need to redefine -

    +
     \newcommand*{\samplenum}[1]{%  
      \expandafter\@samplenum\csname c@#1\endcsname}  
     \newcommand*{\@samplenum}[1]{\textsc{\romannumeral#1}}
    -

    Again, the inner macro needs to be identified using: +

    Again, the inner macro needs to be identified using:

    -
    +
    \glsaddprotectedpagefmt{@samplenum}
    -

    However, since

    However, since \textsc isn’t fully expandable, the location is written to the file as \textsc -

    +
    \renewcommand*{\gls@samplenumpage}{\romannumeral\c@page}
    -

    While this modification means that the location list in the glossary won’t exactly match the +

    While this modification means that the location list in the glossary won’t exactly match the format of the page numbers (displaying lower case Roman numbers instead of small cap Roman numerals) this method will at least work correctly for both xindy -

    +
     \renewcommand*{\gls@samplenumpage}{%  
       \glsbackslash\string\textsc{\romannumeral\c@page}}
    -

    combined with +

    combined with

    -
    +
    \GlsAddXdyLocation{romansc}{:sep "\string\textsc\glsopenbrace"  
     "roman-numbers-lowercase" :sep "\glsclosebrace"}
    -

    will now have lowercase Roman numerals in the location list. (This option may cause +

    will now have lowercase Roman numerals in the location list. (This option may cause problems if your locations should be hyperlinks.) -

    Another possibility that will work with both

    Another possibility that will work with both makeindex and -

    +
      \renewcommand*{\gls@samplenumpage}{\number\c@page}  
      \renewcommand*{\glsnumberformat}[1]{\textsc{\romannumeral#1}}
    -

    -

    If you redefine

    +

    If you redefine \glsinternal cs namepage, you must make sure that \c@page is expanded when it’s written to the file. (So don’t, for example, hide \c@page inside a robust command.)
    -

    -

    The mechanism that allows this to work temporarily redefines

    +

    The mechanism that allows this to work temporarily redefines \the and \number while it processes the location. If this causes a problem you can disallow it using -



    \glswrallowprimitivemodsfalse  \glswrallowprimitivemodsfalse

    -

    -

    Both

    +

    Both makeindex and } where ⟨n⟩ is either an integer or the keyword none which indicates that there should be no range formation. -

    Note that

    -

    -

    With both

    +

    With both makeindex and xindy2 and 3), you can replace the separator and the closing number in the range using: -



    \glsSetSuffixF  \glsSetSuffixF{suffix}

    -

    -


    +


    \glsSetSuffixFF  \glsSetSuffixFF{suffix}

    -

    +

    where the former command specifies the suffix to use for a 2 page list and the latter specifies the suffix to use for longer lists. For example:

    -
    +
    \glsSetSuffixF{f.}  
    \glsSetSuffixFF{ff.}
    -

    Note that if you use

    Note that if you use xindy ( -

    +
    \GlsSetXdyMinRangeLength{1}
    -

    Note that if you use the

    Note that if you use the hyperref package, you will need to use \nohyperpage -

    +
    \glsSetSuffixF{\nohyperpage{f.}}  
    \glsSetSuffixFF{\nohyperpage{ff.}}
    -

    -

    Note that

    +

    -

    -

    +

    Option 1 doesn’t form ranges. However, with this option you can iterate over an entry’s number list using: -



    \glsnumberlistloop  }{xr handler cs}

    -

    +

    where ⟨label⟩ is the entry’s label and ⟨handler cs⟩ is a handler control sequence of the form: -



    handler cs{prefixformat}{location}

    -

    +

    where ⟨prefix⟩ is the hyperreftextbf) and ⟨location⟩ is the location. The third argument is the control sequence to use for any cross-references in the list. This handler should have the syntax: -



    xr handler cs[tag]{xr list}

    -

    +

    where ⟨tag⟩ is the cross-referenced text (e.g. “see”) and ⟨xr list⟩ is a comma-separated list of labels. (This actually has a third argument but it’s always empty when used with Option 1.) -

    For example, if on page 12 I have used +

    For example, if on page 12 I have used

    -
    +
    \gls[format=textbf]{apple}
    -

    and on page 18 I have used +

    and on page 18 I have used

    -
    +
    \gls[format=emph]{apple}
    -

    then +

    then

    -
    +
    \glsnumberlistloop{apple}{\myhandler}
    -

    will be equivalent to: +

    will be equivalent to:

    -
    +
    \myhandler{}{page}{textbf}{12}%  
    \myhandler{}{page}{emph}{18}%
    -

    There is a predefined handler that’s used to display the

    There is a predefined handler that’s used to display the number list in the glossary: -



    \glsnoidxdisplayloc  }{location}

    -

    +

    The predefined handler used for the cross-references in the glossary is: -



    \glsseeformat[tag]{xr list}{location}

    -

    +

    which is described in §8.1 Customising Cross-reference Text. -

    \glsnumberlistloop is not available for Options 2 and 3.
    -

    +

    +

    As from version 4.24, there’s a hook that’s used near the end of \writeist before the file +is closed. You can set the code to be performed then using: +


    \GlsSetWriteIstHook  \GlsSetWriteIstHook{code}

    +

    +If you want the ⟨code⟩ to write any information to the file, you need to use +


    \glswrite  \write\glswrite{style information}

    +

    +Make sure you use the correct format within ⟨style information⟩. For example, if you are using +makeindex: + + +

    +
    +\GlsSetWriteIstHook{% + 
     \write\glswrite{page_precedence "arnAR"}% + 
     \write\glswrite{line_max 80}% + 
    } +
    +

    This changes the page type precedence and the maximum line length used by +makeindex. +

    Remember that if you switch to xindy, this will no longer be valid code.

    -

    -

    +

    Top

    6. Links to Glossary Entries

    -

    Once you have defined a glossary entry using

    Once you have defined a glossary entry using \newglossaryentry or \newacronymOption 1. If you don’t use \makeglossaries these external files won’t be created. -

    Note that repeated use of these commands for the same entry can cause the

    Note that repeated use of these commands for the same entry can cause the number list to become quite long, which may not be particular helpful to the reader. In this case, @@ -10195,10 +10524,10 @@ href="#glo:glossaries-extra">glossaries-extra package, which provides a means to suppress the automated indexing of the commands listed in this chapter. -

    I strongly recommend that you don’t use the commands defined in this chapter in the +

    I strongly recommend that you don’t use the commands defined in this chapter in the arguments of sectioning or caption commands or any other command that has a moving argument. -

    Aside from problems with expansion issues, PDF bookmarks and possible nested +

    Aside from problems with expansion issues, PDF bookmarks and possible nested hyperlinks in the table of contents (or list of whatever) any use of the commands described in \gls-Like Commands (First Use Flag Queried)

    -

    The above warning is particularly important if you are using the

    +

    The above warning is particularly important if you are using the glossaries package in conjunction with the hyperref -

    +
    \chapter{An overview of \glsentrytext{perl}}  
    \chapter[An overview of Perl]{An overview of \gls{perl}}  
    \chapter{An overview of \texorpdfstring{\gls{perl}}{Perl}}
    -

    If you want to retain the formatting that’s available through commands like

    If you want to retain the formatting that’s available through commands like \acrshort (for example, if you are using one of the small caps styles), then you might want to consider the glossaries-extra package which provides commands for this purpose. -

    If you want the

    If you want the link text to produce a hyperlink to the corresponding entry details in the glossary, you should load the link text, you can click on the word or phrase and it will take you to a brief description in this document’s glossary. -

    If you use the

    If you use the hyperref package, I strongly recommend you use pdflatex

    These are limitations of the DVI format not of the

    These are limitations of the DVI format not of the glossaries package.

    -

    -

    It may be that you only want terms in certain glossaries to have hyperlinks, but not for +

    +

    It may be that you only want terms in certain glossaries to have hyperlinks, but not for other glossaries. In this case, you can use the package option nohypertypes to identify the @@ -10291,27 +10620,27 @@ href="#sec:pkgopts-general">§2.1 General Options for further details. -

    The way the

    The way the link text is displayed depends on -



    \glstextformat  \glstextformat{text}

    -

    +

    For example, to make all link text appear in a sans-serif font, do:

    -
    +
    \renewcommand*{\glstextformat}[1]{\textsf{#1}}
    -

    Further customisation can be done via

    Further customisation can be done via \defglsentryfmt or by redefining \glsentryfmt\glsentryfmt§6.3 Changing the format of the link text for further details. -

    Each entry has an associated conditional referred to as the

    Each entry has an associated conditional referred to as the first use flag. Some of the commands described in this chapter automatically unset this flag and can also use it to determine what text should be displayed. These types of commands are the @@ -10347,7 +10676,7 @@ href="#sec:glsunset">Unsetting and Resetting Entry Flags

    The

    The \gls-like and glossaries-extra package provides the option to add a third custom variant. -

    Avoid nesting these commands. For example don’t do

    Avoid nesting these commands. For example don’t do \glslink{label}symbol key if you intend to use \glssymbol.)
    -

    -

    The following keys are available for the optional argument: +

    +

    The following keys are available for the optional argument:

    hyperitalic) you will need to create a command that applies bo e.g.  -
    +
    \newcommand*{\textbfem}[1]{\textbf{\emph{#1}}}
    -

    and use that command. -

    In this document, the standard formats refer to the standard text block commands such +

    and use that command. +

    In this document, the standard formats refer to the standard text block commands such as \textbf or \emph or any of the commands listed in table 6.1. -

    If you use

    If you use xindy instead of xindy - -

    -

    If you are using hyperlinks and you want to change the font of the hyperlinked location, +

    +

    If you are using hyperlinks and you want to change the font of the hyperlinked location, don’t use \hyperpage (provided by the glossaries package provides number formats listed in href="#tab:hyperxx">table 6.1.

    -


    emphasized hyperlink

    -

    Note that if the

    Note that if the \hyperlink command hasn’t been defined, the hyper\hyperbsf -

    counterlocal=true, the change to the first use flag will be localised to the current scope. The default is local=false.
    -

    The

    The glossaries-extra package provides an additional key. Please see the glossaries-extra user manual for further details. -

    The

    The link text isn’t scoped by default. Any unscoped declarations in the link text may affect subsequent text.
    -

    +

    -

    Top

    6.1 The \gls-Like Commands (First Use Flag Queried)

    -

    This section describes the commands that unset (mark as used) the

    This section describes the commands that unset (mark as used) the first use flag on completion, and in most cases they use the current state of the flag to determine the text to be displayed. As described above, these commands all have a star-variant (hyper=true) and have an optional first argument that is a class="cmti-10">key⟩=⟨value⟩ list. -

    These commands use

    These commands use \glsentryfmt or the equivalent definition provided by §6.3 Changing the format of the link text). -

    Apart from

    Apart from \glsdisp, the commands described in this section also have a final optional argument ⟨insert⟩ which may be used to insert material into the automatically generated text. -

    Since the commands have a final optional argument, take care if you actually want to +

    Since the commands have a final optional argument, take care if you actually want to display an open square bracket after the command when the final optional argument is absent. Insert an empty set of braces {} immediately before the opening square bracket to @@ -10702,19 +11031,19 @@ prevent it from being interpreted as the final argument. For example:

    -
    +
    \gls{sample} {}[Editor’s comment]
    -

    -

    Don’t use any of the

    +

    Don’t use any of the \gls-like or \glstext-like commands in the ⟨insert⟩ argument.

    -

    -


    +


    \gls  label}[insert]

    -

    +

    This command typically determines the link text from the values of the long or short keys. -

    There are two upper case variants: -


    There are two upper case variants: +


    \Gls  label}[insert]

    -

    +

    and -



    \GLS  label}[insert]

    -

    +

    which make the first letter of the link text or all the link text upper case, respectively. For the former, the uppercasing of the first letter is performed by \makefirstuc. -

    The first letter uppercasing command

    The first letter uppercasing command \makefirstuc has limitations which must be taken into account if you use \Gls or any of the other commands that convert the first letter to uppercase.
    -

    +

    The upper casing is performed as follows:

    -

    (Note the use of the

    (Note the use of the sort key in the above examples.) -

    There are hundreds of LAT

    There are hundreds of LATEX packages that altogether define thousands of commands with various syntax and it’s impossible for mfirstuclink textmfirstuc’s assumptions then things are likely to go wrong. -

    For example, starting with a math-shift symbol: +

    For example, starting with a math-shift symbol:

    -
    +
    \newglossaryentry{sample}{  
      name={$a$},  
      sort={a},  
      description={an example}  
    }
    -

    This falls into case 2 above, so the

    This falls into case 2 above, so the link text will be set to

    -
    +
    \MakeUppercase $a$
    -

    This attempts to uppercase the math-shift

    This attempts to uppercase the math-shift $, which will go wrong. In this case it’s not appropriate to perform any case-changing, but it may be that you want to use \Gls @@ -10897,25 +11226,25 @@ solution is to insert an empty brace at the start:

    -
    +
    \newglossaryentry{sample}{  
      name={{}$a$},  
      sort={a},  
      description={an example}  
    }
    -

    Now the

    Now the link text will be set to

    -
    +
    \MakeUppercase{}$a$
    -

    and the

    and the \uppercase becomes harmless. -

    Another issue occurs when the

    Another issue occurs when the link text starts with a command followed by an argument (case 1) but the argument is a label, identifier or something else that shouldn’t have a @@ -10934,7 +11263,7 @@ example:

    -
    +
    \newglossaryentry{sample}{name={sample},description={an example}}  
    \newglossaryentry{sample2}{  
       name={\glsentrytext{sample} two}, @@ -10942,16 +11271,16 @@ example:  
       description={another example}  
     }
    -

    Now the

    Now the link text will be set to:

    -
    +
    \glsentrytext{\MakeUppercase sample} two
    -

    This will generate an error because there’s no entry with the label given by +

    This will generate an error because there’s no entry with the label given by \MakeUppercase sample. The best solution here is to write the term out in the name -

    + -

    -

    If the

    +

    If the link text starts with a command that has an optional argument or with multiple arguments where the actual text isn’t in the first argument, then -

    +
    \newglossaryentry{sample}{  
     name={\textcolor{blue}{sample} phrase},  
     sort={sample phrase},  
     description={an example}}
    -

    Now the

    Now the link text will be set to:

    -
    +
    \textcolor{\MakeUppercase blue}{sample} phrase
    -

    This won’t work because

    This won’t work because \MakeUppercase blue isn’t a recognised colour name. In this case you will have to define a helper command where the first argument is the text. For @@ -11010,32 +11339,32 @@ example:

    -
    +
    \newglossaryentry{sample}{  
    \newcommand*{\blue}[1]{\textcolor{blue}{#1}}  
     name={\blue{sample} phrase},  
     sort={sample phrase},  
     description={an example}}
    -

    In fact, since the whole design ethos of LAT

    In fact, since the whole design ethos of LATEX is the separation of content and style, it’s better to use a semantic command. For example:

    -
    +
    \newglossaryentry{sample}{  
    \newcommand*{\keyword}[1]{\textcolor{blue}{#1}}  
     name={\keyword{sample} phrase},  
     sort={sample phrase},  
     description={an example}}
    -

    For further details see the

    For further details see the mfirstuc user manual. -

    There are plural forms that are analogous to

    There are plural forms that are analogous to \gls: -



    \glspl  label}[insert]

    -

    -


    +


    \Glspl  label}[insert]

    -

    -


    +


    \GLSpl  label}[insert]

    -

    +

    These typically determine the link text from the plural or longplural or shortplural keys. -

    Be careful when you use glossary entries in math mode especially if you are using

    Be careful when you use glossary entries in math mode especially if you are using hyperref as it can affect the spacing of subscripts and superscripts. For example, suppose you have @@ -11093,18 +11422,18 @@ defined the following entry:

    -
    +
    \newglossaryentry{Falpha}{name={F_\alpha},  
    description=sample}
    -

    and later you use it in math mode: +

    and later you use it in math mode:

    -
    +
    $\gls{Falpha}^2$
    -

    This will result in

    This will result in Fα2 instead of insert⟩ optional argument:

    -
    +
    $\gls{Falpha}[^2]$
    -

    -

    -


    +

    +


    \glsdisp  label}{link text}

    -

    +

    This behaves in the same way as the above commands, except that the ⟨link text⟩ is explicitly set. There’s no final optional argument as any inserted material can be added to the ⟨link text⟩ argument. -

    Don’t use any of the

    Don’t use any of the \gls-like or \glstext-like commands in the ⟨link text⟩ argument of \glsdisp.
    -

    -

    +

    +

    -

    Top

    6.2 The \glstext-Like Commands (First Use Flag Not Queried)

    -

    This section describes the commands that don’t change or reference the

    This section describes the commands that don’t change or reference the first use flag. As described above, these commands all have a star-variant (hyper=false) @@ -11171,7 +11500,7 @@ href="#sec:glsdisplay">§6.3 Changing the format of the link text). -

    Apart from

    Apart from \glslink, the commands described in this section also have a final @@ -11183,7 +11512,7 @@ class="cmsy-10">§6.1 The \gls-Like Commands (First Use Flag Queried). -



    \glslink  label}{link text}

    -

    +

    This command explicitly sets the link text as given in the final argument. -

    Don’t use any of the

    -

    -


    +


    \glstext  label}[insert]

    -

    +

    This command always uses the value of the text key as the link text. -

    There are also analogous commands: +

    There are also analogous commands: -



    \Glstext  text}[insert]

    -

    -


    +


    \GLStext  text}[insert]

    -

    +

    These convert the first character or all the characters to uppercase, respectively. See the note on \Gls above for details on the limitations of converting the first letter to upper case. -

    There’s no equivalent command for title-casing, but you can use the more generic +

    There’s no equivalent command for title-casing, but you can use the more generic command \glsentrytitlecase in combination with \glslink. For example:

    -
    +
    \glslink{sample}{\glsentrytitlecase{sample}{text}}
    -

    (See

    (See §9 Using Glossary Terms Without Links.) -



    \glsfirst  label}[insert]

    -

    +

    This command always uses the value of the first key as the link text. -

    There are also analogous uppercasing commands: -


    There are also analogous uppercasing commands: +


    \Glsfirst  text}[insert]

    -

    -


    +


    \GLSfirst  text}[insert]

    -

    -

    The value of the

    +

    The value of the first key (and firstplural\gls or \glspl on subsequent use.)
    -

    -


    +


    \glsplural  label}[insert]

    -

    +

    This command always uses the value of the plural key as the link text. -

    There are also analogous uppercasing commands: -


    There are also analogous uppercasing commands: +


    \Glsplural  text}[insert]

    -

    -


    +


    \GLSplural  text}[insert]

    -

    -


    +


    \glsfirstplural  label}[insert]

    -

    +

    This command always uses the value of the firstplural key as the link text. -

    There are also analogous uppercasing commands: -


    There are also analogous uppercasing commands: +


    \Glsfirstplural  text}[insert]

    -

    -


    +


    \GLSfirstplural  text}[insert]

    -

    -


    +


    \glsname  insert]

    -

    +

    This command always uses the value of the name key as the \glstext or \glsfirst instead of \glsname. -

    There are also analogous uppercasing commands: -


    There are also analogous uppercasing commands: +


    \Glsname  text}[insert]

    -

    -


    +


    \GLSname  text}[insert]

    -

    -

    In general it’s best to avoid

    +

    In general it’s best to avoid \Glsname with acronyms. Instead, consider using \Acrlong, \Acrshort or \Acrfull.
    -

    -


    +


    \glssymbol  label}[insert]

    -

    +

    This command always uses the value of the symbol key as the link text. -

    There are also analogous uppercasing commands: -


    There are also analogous uppercasing commands: +


    \Glssymbol  text}[insert]

    -

    -


    +


    \GLSsymbol  text}[insert]

    -

    -


    +


    \glsdesc  label}[insert]

    -

    +

    This command always uses the value of the description key as the link text. -

    There are also analogous uppercasing commands: -


    There are also analogous uppercasing commands: +


    \Glsdesc  text}[insert]

    -

    -


    +


    \GLSdesc  text}[insert]

    -

    -

    If you want the title case version you can use +

    +

    If you want the title case version you can use

    -
    +
    \glslink{sample}{\glsentrytitlecase{sample}{desc}}
    -

    -


    +


    \glsuseri  label}[insert]

    -

    +

    This command always uses the value of the user1 key as the link text. -

    There are also analogous uppercasing commands: -


    There are also analogous uppercasing commands: +


    \Glsuseri  text}[insert]

    -

    -


    +


    \GLSuseri  text}[insert]

    -

    -


    +


    \glsuserii  text}[insert]

    -

    +

    This command always uses the value of the user2 key as the link text. -

    There are also analogous uppercasing commands: -


    There are also analogous uppercasing commands: +


    \Glsuserii  text}[insert]

    -

    -


    +


    \GLSuserii  text}[insert]

    -

    -


    +


    \glsuseriii  text}[insert]

    -

    +

    This command always uses the value of the user3 key as the link text. -

    There are also analogous uppercasing commands: -


    There are also analogous uppercasing commands: +


    \Glsuseriii  text}[insert]

    -

    -


    +


    \GLSuseriii  text}[insert]

    -

    -


    +


    \glsuseriv  text}[insert]

    -

    +

    This command always uses the value of the user4 key as the link text. -

    There are also analogous uppercasing commands: -


    There are also analogous uppercasing commands: +


    \Glsuseriv  text}[insert]

    -

    -


    +


    \GLSuseriv  insert]

    -

    -


    +


    \glsuserv  text}[insert]

    -

    +

    This command always uses the value of the user5 key as the link text. -

    There are also analogous uppercasing commands: -


    There are also analogous uppercasing commands: +


    \Glsuserv  text}[insert]

    -

    -


    +


    \GLSuserv  text}[insert]

    -

    -


    +


    \glsuservi  text}[insert]

    -

    +

    This command always uses the value of the user6 key as the link text. -

    There are also analogous uppercasing commands: -


    There are also analogous uppercasing commands: +


    \Glsuservi  text}[insert]

    -

    -


    +


    \GLSuservi  text}[insert]

    -

    -

    +

    +

    -

    Top

    6.3 Changing the format of the link text

    -

    The default format of the

    The default format of the link text for the \gls-like commands is governed by6.2: -



    \glsentryfmt  \glsentryfmt

    -

    +

    This may be redefined but if you only want the change the display style for a given glossary, then you need to use -



    \defglsentryfmt  type]{definition}

    -

    +

    instead of redefining \glsentryfmt. The optional first argument ⟨type⟩ is the glossary type. @@ -11870,7 +12199,7 @@ This defaults to \glsdefaulttype if omitted. The second argument is the entry format definition. -

    Note that

    Note that \glsentryfmt is the default display format for entries. Once the display format has been changed for an individual glossary using \defglsentryfmtAcronym Options

    -

    Within the ⟨

    +

    Within the ⟨definition⟩ argument of \defglsentryfmt, or if you want to redefine \glsentryfmt, you may use the following commands: -



    \glslabel  \glslabel

    -

    +

    This is the label of the entry being referenced. As from version 4.08, you can also access the glossary entry type using: -



    \glstype  \glstype

    -

    +

    This is defined using \edef so the replacement text is the actual glossary type rather than \glsentrytype{\glslabel}. -



    \glscustomtext  \glscustomtext

    -

    +

    This is the custom text supplied in \glsdisp. It’s always empty for \glsetoolbox\ifdefempty to determine if \glscustomtext is empty.) -



    \glsinsert  \glsinsert

    -

    +

    The custom text supplied in the final optional argument to \gls, \glspl and their upper case variants. -



    \glsifplural  true text}{false text}

    -

    +

    If \glspl, \Glspl or true text⟩ otherwise it does ⟨false text⟩. -



    \glscapscase  first uc}{all caps}

    -

    +

    If \gls, \glspl or first uc⟩. If \GLS or \GLSpl were used, this does ⟨all caps⟩. -



    \glsifhyperon  hyper true}{hyper false}

    -

    +

    This will do ⟨hyper true⟩ if the hyperlinks are on for the current reference, otherwise it will do ⟨nohypertypes) or because it’s the first use and the hyperlinks have been suppressed on first use. -

    Note that

    Note that \glsifhyper is now deprecated. If you want to know if the command used to reference this entry was used with the star or plus variant, you can use: -



    \glslinkvar  star}{plus}

    -

    +

    This will do ⟨unmodified⟩ if the unmodified version was used, or will do ⟨star⟩ if the starred @@ -12042,7 +12371,7 @@ command shouldn’t be used to guess whether or not the hyperlink is on for reference. -

    Note that you can also use commands such as

    Note that you can also use commands such as \ifglsused within the definition of \glsentryfmt (see §14 Unsetting and Resetting Entry Flags). -

    The commands

    The commands \glslabel, \glstype\glspostlinkhook\glslinkpostsetkeys. -

    This means that using commands like

    -

    -

    If you only want to make minor modifications to

    +

    If you only want to make minor modifications to \glsentryfmt, you can use -



    \glsgenentryfmt  \glsgenentryfmt

    -

    +

    This uses the above commands to display just the first, pluralfirstplural keys (or the custom text) with the insert text appended. -

    Alternatively, if want to change the entry format for abbreviations (defined via +

    Alternatively, if want to change the entry format for abbreviations (defined via \newacronym) you can use: -



    \glsgenacfmt  \glsgenacfmt

    -

    +

    This uses the values from the long, firstfirstplural keys. The first use singular text is obtained via: -



    \genacrfullformat  label}{insert}

    -

    +

    instead of from the first key, and the first use plural text is obtained via: -



    \genplacrfullformat  label}{insert}

    -

    +

    instead of from the firstplural key. In both cases, ⟨\firstacronymfont. There are also first letter upper case versions: -



    \Genacrfullformat  label}{insert}

    -

    +

    and -



    \Genplacrfullformat  label}{insert}

    -

    +

    By default these perform a protected expansion on their no-case-change equivalents and then use \makefirstuc§13 Acronyms and Other Abbreviations for further details on changing the style of acronyms. -

    Note that

    Note that \glsentryfmt (or the formatting given by \defglsentryfmt) is not used by the \glstext-like commands.
    -

    -

    As from version 4.16, both the

    +

    As from version 4.16, both the \gls-like and \glstext-like commands use -



    \glslinkpostsetkeys  \glslinkpostsetkeys

    -

    +

    after the ⟨options⟩ are set. This macro does nothing by default but can be redefined. (For example, to switch off the hyperlink under certain conditions.) This version also introduces -



    \glspostlinkhook  \glspostlinkhook

    -

    +

    which is done after the link text has been displayed and also after the first use flag has been @@ -12264,23 +12593,23 @@ unset (see example 24). -

    Example 8 (Custom Entry Display in Text) -

    Suppose you want a glossary of measurements and units, you can use the

    Suppose you want a glossary of measurements and units, you can use the symbol key to store the unit:

    -
    +
    \newglossaryentry{distance}{name=distance,  
    description={The length between two points},  
    symbol={km}}
    -

    and now suppose you want

    and now suppose you want \gls{distance} to produce “distance (km)” on first use, then you can redefine \glsentryfmt -

    +
    \renewcommand*{\glsentryfmt}{%  
      \glsgenentryfmt  
      \ifglsused{\glslabel}{}{\space (\glsentrysymbol{\glslabel})}%  
    }
    -

    -

    (Note that I’ve used

    +

    (Note that I’ve used \glsentrysymbol rather than \glssymbol to avoid nested hyperlinks.) -

    Note also that all of the

    Note also that all of the link text will be formatted according to \glstextformat\glstextformat -

    -

    Example 9 (Custom Format for Particular Glossary) -

    Suppose you have created a new glossary called

    Suppose you have created a new glossary called notation and you want to change the way the entry is displayed on first use so that it includes the symbol, you can @@ -12342,64 +12671,64 @@ do:

    -
    +
    \defglsentryfmt[notation]{\glsgenentryfmt  
     \ifglsused{\glslabel}{}{\space  
       (denoted \glsentrysymbol{\glslabel})}}
    -

    Now suppose you have defined an entry as follows: +

    Now suppose you have defined an entry as follows:

    -
    +
    \newglossaryentry{set}{type=notation,  
      name=set,  
      description={A collection of objects},  
      symbol={$S$}  
    }
    -

    The

    The first time you reference this entry it will be displayed as: “set (denoted S)” (assuming \gls was used). -

    Alternatively, if you expect all the symbols to be set in math mode, you can +

    Alternatively, if you expect all the symbols to be set in math mode, you can do:

    -
    +
    \defglsentryfmt[notation]{\glsgenentryfmt  
     \ifglsused{\glslabel}{}{\space  
       (denoted $\glsentrysymbol{\glslabel}$)}}
    -

    and define entries like this: +

    and define entries like this:

    -
    +
    \newglossaryentry{set}{type=notation,  
      name=set,  
      description={A collection of objects},  
      symbol={S}  
    }
    -

    +

    -

    -

    ____________________________

    -

    Remember that if you use the

    +

    ____________________________

    +

    Remember that if you use the symbol key, you need to use a glossary style that displays the symbol, as many of the styles ignore it. -

    +

    -

    Top

    6.4 Enabling and disabling hyperlinks to glossary entries

    -

    If you load the

    If you load the hyperref or htmlhypernohypertypes package option). -

    You can disable or enable links using: -


    You can disable or enable links using: +


    \glsdisablehyper  \glsdisablehyper

    -

    +

    and -



    \glsenablehyper  \glsenablehyper

    -

    +

    respectively. The effect can be localised by placing the commands within a group. Note that you should only use \glsenablehyper if the commands \hypertargethyperref package). -

    You can disable just the

    You can disable just the first use links using the package option hyperfirst=false. Note @@ -12451,11 +12780,11 @@ href="#glo:firstuseflag">first use flag. -

    Example 10 (First Use With Hyperlinked Footnote Description) -

    Suppose I want the first use to have a hyperlink to the description in a footnote instead of +

    Suppose I want the first use to have a hyperlink to the description in a footnote instead of hyperlinking to the relevant place in the glossary. First I need to disable the hyperlinks on first use via the package option hyperfirst=falsehyperfirst=false -

    +
    \usepackage[hyperfirst=false]{glossaries}
    -

    Now I need to redefine

    Now I need to redefine \glsentryfmt (see ):

    -
    +
    \renewcommand*{\glsentryfmt}{%  
      \glsgenentryfmt  
      \ifglsused{\glslabel}{}{\footnote{\glsentrydesc{\glslabel}}}%  
    }
    -

    -

    Now the first use won’t have hyperlinked text, but will be followed by a footnote. See the +

    +

    Now the first use won’t have hyperlinked text, but will be followed by a footnote. See the sample file sample-FnDesc.tex for a complete document.

    -

    -

    ____________________________

    -

    Note that the

    +

    ____________________________

    +

    Note that the hyperfirst option applies to all defined glossaries. It may be that you only want to disable the hyperlinks on hyperfirst -

    Example 11 (Suppressing Hyperlinks on First Use Just For Acronyms) -

    Suppose I want to suppress the hyperlink on

    Suppose I want to suppress the hyperlink on first use for acronyms but not for entries in the main glossary. I can load the glossaries package using:

    -
    +
    \usepackage[hyperfirst=false,acronym]{glossaries}
    -

    Once all glossary entries have been defined I then do: +

    Once all glossary entries have been defined I then do:

    -
    +
    \glsunsetall[main]
    -

    +

    -

    -

    ____________________________

    -

    For more complex requirements, you might find it easier to switch off all hyperlinks via +

    +

    ____________________________

    +

    For more complex requirements, you might find it easier to switch off all hyperlinks via \glsdisablehyper and put the hyperlinks (where required) within the definition of @@ -12556,11 +12885,11 @@ class="cmsy-10">§9 href="#sec:glsnolink">Using Glossary Terms Without Links). -

    Example 12 (Only Hyperlink in Text Mode Not Math Mode) -

    This is a bit of a contrived example, but suppose, for some reason, I only want the +

    This is a bit of a contrived example, but suppose, for some reason, I only want the \gls-like commands to have hyperlinks when used in text mode, but not in math mode. @@ -12571,7 +12900,7 @@ class="cmtt-10">\glsentryfmt -

    + -

    Note that this doesn’t affect the

    Note that this doesn’t affect the \glstext-like commands, which will have the hyperlinks off unless they’re forced on using the plus variant. -

    See the sample file

    See the sample file sample-nomathhyper.tex for a complete document.

    -

    -

    ____________________________

    +

    +

    ____________________________

    -

    Example 13 (One Hyper Link Per Entry Per Chapter) -

    Here’s a more complicated example that will only have the hyperlink on the first time an +

    Here’s a more complicated example that will only have the hyperlink on the first time an entry is used per chapter. This doesn’t involve resetting the first use flag. Instead it adds a new key using -

    +
    \glsaddstoragekey{chapter}{0}{\glschapnum}
    -

    This creates a new user command called

    This creates a new user command called \glschapnum that’s analogous to \glsentrytext. The default value for this key is 0. I then define my glossary entries as usual. -

    Next I redefine the hook

    Next I redefine the hook \glslinkpostsetkeys (see \glsifhyperon.

    - -

    -

    +

    Top

    7. Adding an Entry to the Glossary Without Generating Text

    -

    It is possible to add a line to the glossary file without generating any text at that point in +

    It is possible to add a line to the glossary file without generating any text at that point in the document using: -



    \glsadd  options]{label}

    -

    +

    This is similar to the \glstext-like commands, only it doesn’t produce any text (so @@ -12707,21 +13036,21 @@ class="cmtt-10">set:

    -
    +
    \glsadd[format=(]{set}  
    Lots of text about sets spanning many pages.  
    \glsadd[format=)]{set}
    -

    -

    To add all entries that have been defined, use: -


    +

    To add all entries that have been defined, use: +


    \glsaddall  \glsaddall[options]

    -

    +

    The optional argument is the same as for \glsadd, except there is also a key typesnotation) then you can do:

    -
    +
    \glsaddall[types={\acronymtype,notation}]
    -

    -

    Note that

    +

    -

    -

    There is now a variation of

    +

    There is now a variation of \glsaddall that skips any entries that have already been used: -



    \glsaddallunused  \glsaddallunused[list]

    -

    +

    This command uses \glsadd[format=@gobble] which will ignore this location in the number list. The optional argument ⟨list⟩ is a comma-separated list of glossary types. If omitted, it defaults to the list of all defined glossaries. -

    If you want to use

    If you want to use \glsaddallunused, it’s best to place the command at the end of the document to ensure that all the commands you intend to use have already been used. Otherwise you could end up with a spurious comma or dash in the location list. -

    Example 14 (Dual Entries) -

    The example file

    The example file sample-dual.tex makes use of \glsadd to allow for an entry that should appear both in the main glossary and in the list of acronyms. This example sets up the @@ -12793,14 +13122,14 @@ class="cmss-10">acronym -

    +
    \usepackage[acronym]{glossaries}
    -

    A new command is then defined to make it easier to define dual entries: +

    A new command is then defined to make it easier to define dual entries:

    -
    + -

    This has the following syntax:

    +

    Top

    8. Cross-Referencing Entries

    -

    You must use

    -

    -

    There are several ways of cross-referencing entries in the glossary: +

    +

    There are several ways of cross-referencing entries in the glossary:

    1. You can use commands such as \gls in the entries description. For example: -
      +
      \newglossaryentry{apple}{name=apple,  
      description={firm, round fruit. See also \gls{pear}}}
      -

      Note that with this method, if you don’t use the cross-referenced term in the main part +

      Note that with this method, if you don’t use the cross-referenced term in the main part of the document, you will need two runs of makeglossariesmakeglossaries -

    2. As described in see +
      \newglossaryentry{MaclaurinSeries}{name={Maclaurin  
      series},  
      description={Series expansion},  
      see={TaylorsTheorem}}
      -

      Note that in this case, the entry with the

      Note that in this case, the entry with the see key will automatically be added to the glossary, but the cross-referenced entry won’t. You therefore need to ensure that you @@ -12923,7 +13252,7 @@ href="#sec:glsadd">§7 Adding an Entry to the Glossary Without Generating Text. -

      The “see” tag is produce using

      The “see” tag is produce using \seename, but can be overridden in specific instances using square brackets at the start of the see -

    3. After you have defined the entry, use -


    -

    In both cases 2 and 3 above, the cross-referenced information appears in the

    In both cases 2 and 3 above, the cross-referenced information appears in the number list, whereas in case 1, the cross-referenced information appears in the description. (See the @@ -13032,15 +13361,15 @@ class="cmss-10">seeautonumberlist package option.

    -

    Top

    8.1 Customising Cross-reference Text

    -

    When you use either the

    When you use either the see key or the command \glssee, the cross-referencing information will be typeset in the glossary according to: -



    \glsseeformat  label-list}{location}

    -

    +

    The default definition of \glsseeformat is:
    8.2 -

    +
    \renewcommand*{\glsseeformat}[3][\seename]{\textbf{#1}  
     \glsseelist{#2}}
    -

    -

    The list of labels is dealt with by

    +

    The list of labels is dealt with by \glsseelist, which iterates through the list and typesets each entry in the label. The entries are separated by -



    \glsseesep  \glsseesep

    -

    +

    or (for the last pair) -



    \glsseelastsep  \glsseelastsep

    -

    +

    These default to “,\space” and “\space\andname\space” respectively. The list entry text is displayed using: -



    \glsseeitemformat  \glsseeitemformat{label}

    -

    +

    This defaults to \glsentrytext -

    +
    \renewcommand{\glsseeitemformat}[1]{%  
      \textsc{\glsentrytext{#1}}}
    -

    -

    -

    +

    Top

    9. Using Glossary Terms Without Links

    -

    The commands described in this section display entry details without adding any +

    The commands described in this section display entry details without adding any information to the glossary. They don’t use \glstextformat, they don’t have any optional @@ -13156,7 +13485,7 @@ href="#glo:firstuseflag">first use flag and, apart from \glshyperlink, they don’t produce hyperlinks. -

    Commands that aren’t expandable will be ignored by PDF bookmarks, so you will need +

    Commands that aren’t expandable will be ignored by PDF bookmarks, so you will need to provide an alternative via hyperref’s hyperref -

    -

    If you want to title case a field, you can use: -


    +

    If you want to title case a field, you can use: +


    \glsentrytitlecase  label}{field}

    -

    +

    where ⟨label⟩ is the label identifying the glossary entry, ⟨field⟩ is the field label (see -

    +
    \glsentrytitlecase{sample}{desc}
    -

    (If you want title-casing in your glossary style, you might want to investigate the +

    (If you want title-casing in your glossary style, you might want to investigate the glossaries-extra package.) -

    Note that this command has the same limitations as

    Note that this command has the same limitations as \makefirstuc which is used by commands like \Gls and §6.1 The \gls-Like Commands (First Use Flag Queried)). -



    \glsentryname  \glsentryname{label}

    -

    -


    +


    \Glsentryname  \Glsentryname{label}

    -

    +

    These commands display the name of the glossary entry given by ⟨label⟩, as specified by the \glsentrytext or \glsentryfirst instead of \glsentryname. -

    In general it’s best to avoid

    In general it’s best to avoid \Glsentryname with abbreviations. Instead, consider using \Glsentrylong, \Glsentryshort or \Glsentryfull.
    -

    -


    +


    \glossentryname  \glossentryname{label}

    -

    +

    This is like \glsnamefont{ -

    +
    \renewcommand*{\glsnamefont}[1]{\textmd{\sffamily #1}}
    -

    -


    +


    \Glossentryname  \Glossentryname{label}

    -

    +

    This is like \glossentryname but makes the first letter of the name upper case. -



    \glsentrytext  \glsentrytext{label}

    -

    -


    +


    \Glsentrytext  \Glsentrytext{label}

    -

    +

    These commands display the subsequent use text for the glossary entry given by ⟨label⟩, as specified by the \Glsentrytext makes the first letter upper case. The firs expandable (unless the text contains unexpandable commands). The second form is not expandable. Neither checks for the existence of ⟨label⟩. -



    \glsentryplural  \glsentryplural{label}

    -

    -


    +


    \Glsentryplural  \Glsentryplural{label}

    -

    +

    These commands display the subsequent use plural text for the glossary entry given by ⟨label⟩, as specified by the label⟩. -



    \glsentryfirst  \glsentryfirst{label}

    -

    -


    +


    \Glsentryfirst  \Glsentryfirst{label}

    -

    +

    These commands display the first use text for the glossary entry given by ⟨label⟩, @@ -13363,22 +13692,22 @@ The first form is expandable (unless the value of that key contains unexpandable commands). The second form is not expandable. Neither checks for the existence of ⟨label⟩. -



    \glsentryfirstplural  \glsentryfirstplural{label}

    -

    -


    +


    \Glsentryfirstplural  \Glsentryfirstplural{label}

    -

    +

    These commands display the plural form of the first use text for the glossary entry given by ⟨label⟩. -



    \glsentrydesc  \glsentrydesc{label}

    -

    -


    +


    \Glsentrydesc  \Glsentrydesc{label}

    -

    +

    These commands display the description for the glossary entry given by ⟨label⟩. \Glsentrydesc @@ -13415,14 +13744,14 @@ makes the first letter upper case. The first form is expandable (unless the valu contains unexpandable commands). The second form is not expandable. Neither checks for the existence of ⟨label⟩. -



    \glossentrydesc  \glossentrydesc{label}

    -

    +

    This is like \glsentrydesc{label} but also checks for the existence of ⟨label⟩. This command is not expandable. It’s used in the predefined glossary styles to display the description. -



    \Glossentrydesc  \Glossentrydesc{label}

    -

    +

    This is like \glossentrydesc but converts the first letter to upper case. This command is not expandable. -



    \glsentrydescplural  \glsentrydescplural{label}

    -

    -


    +


    \Glsentrydescplural  \Glsentrydescplural{label}

    -

    +

    These commands display the plural description for the glossary entry given by ⟨label⟩. \Glsentrydescplural makes the first letter upper case. Th the value of that key contains unexpandable commands). The second form is not expandable. Neither checks for the existence of ⟨label⟩. -



    \glsentrysymbol  \glsentrysymbol{label}

    -

    -


    +


    \Glsentrysymbol  \Glsentrysymbol{label}

    -

    +

    These commands display the symbol for the glossary entry given by ⟨label⟩. \Glsentrysymbol @@ -13487,7 +13816,7 @@ makes the first letter upper case. The first form is expandable (unless the valu contains unexpandable commands). The second form is not expandable. Neither checks for the existence of ⟨label⟩. -



    \glsletentryfield  label}{field}

    -

    +

    This command doesn’t display anything. It merely fetches the value associated with the given field (where the available field names are listed in table 4.1) and stores the result in the @@ -13509,18 +13838,18 @@ class="cmtt-10">\tmp:

    -
    +
    \glsletentryfield{\tmp}{apple}{desc}
    -

    -


    +


    \glossentrysymbol  \glossentrysymbol{label}

    -

    +

    This is like \glsentrysymbol{label} but also checks for the existence of ⟨label⟩. This command is not expandable. It’s used in some of the predefined glossary styles to display the symbol. -



    \Glossentrysymbol  \Glossentrysymbol{label}

    -

    +

    This is like \glossentrysymbol but converts the first letter to upper case. This command is not expandable. -



    \glsentrysymbolplural  \glsentrysymbolplural{label}

    -

    -


    +


    \Glsentrysymbolplural  \Glsentrysymbolplural{label}

    -

    +

    These commands display the plural symbol for the glossary entry given by ⟨label⟩. \Glsentrysymbolplural makes the first letter upper case. (unless the value of that key contains unexpandable commands). The second form is not expandable. Neither checks for the existence of ⟨label⟩. -



    \glsentryuseri  \glsentryuseri{label}

    -

    -


    +


    \Glsentryuseri  \Glsentryuseri{label}

    -

    -


    +


    \glsentryuserii  \glsentryuserii{label}

    -

    -


    +


    \Glsentryuserii  \Glsentryuserii{label}

    -

    -


    +


    \glsentryuseriii  \glsentryuseriii{label}

    -

    -


    +


    \Glsentryuseriii  \Glsentryuseriii{label}

    -

    -


    +


    \glsentryuseriv  \glsentryuseriv{label}

    -

    -


    +


    \Glsentryuseriv  label}

    -

    -


    +


    \glsentryuserv  \glsentryuserv{label}

    -

    -


    +


    \Glsentryuserv  \Glsentryuserv{label}

    -

    -


    +


    \glsentryuservi  \glsentryuservi{label}

    -

    -


    +


    \Glsentryuservi  \Glsentryuservi{label}

    -

    +

    These commands display the value of the user keys for the glossary entry given by ⟨label⟩. The lower case forms are expandable (unless the value of the key contains unexpandable @@ -13667,7 +13996,7 @@ commands). The commands beginning with an upper case letter convert the first le required value to upper case and are not expandable. None of these commands check for the existence of ⟨label⟩. -



    \glshyperlink  link text]{label}

    -

    +

    This command provides a hyperlink to the glossary entry given by ⟨labelbut does not add @@ -13697,7 +14026,7 @@ class="cmtt-10">\glsdisablehyperhyperref package. -

    If you use

    If you use \glshyperlink, you need to ensure that the relevant entry has been added to the glossary using any of the commands described in §7 Adding an Entry to the Glossary Without Generating Text otherwise you will end up with an undefined link.
    -

    -

    The next two commands are only available with

    +

    The next two commands are only available with Option 1 or with the savenumberlist package option: -



    \glsentrynumberlist  \glsentrynumberlist{label}

    -

    -


    +


    \glsdisplaynumberlist  \glsdisplaynumberlist{label}

    -

    +

    Both display the number list for the entry given by ⟨xindy) followed by one or two runs of LATEX is required. -

    The first command,

    The first command, \glsentrynumberlist, simply displays the number list as is. The second command, \glsdisplaynumberlist, formats the list using: -



    \glsnumlistsep  \glsnumlistsep

    -

    +

    as the separator between all but the last two elements and -



    \glsnumlistlastsep  \glsnumlistlastsep

    -

    +

    between the final two elements. The defaults are ,␣ and ␣\&␣, respectively. -

    \glsdisplaynumberlist is fairly experimental. It works with Option 1, but for Options hyperref, \glsentrynumberlist will be used instead.
    -

    -

    For further information see “Displaying entry details without adding information to the +

    +

    For further information see “Displaying entry details without adding information to the glossary” in the documented code (glossaries-code.pdf).

    -

    -

    +

    Top

    10. Displaying a glossary

    @@ -13810,12 +14139,12 @@ class="cmbx-10">Option 1:
    -



    \printnoidxglossaries  \printnoidxglossaries

    -

    +

    (Must be used with \makenoidxglossaries in the preamble.) @@ -13831,16 +14160,16 @@ href="#option3">3:

    -



    \printglossaries  \printglossaries

    -

    +

    (Must be used with \makeglossaries in the preamble.)

    -

    These commands will display all the glossaries in the order in which they were defined. +

    These commands will display all the glossaries in the order in which they were defined. Note that, in the case of Options 2 and 3, no glossaries will appear until you have either used @@ -13866,7 +14195,7 @@ class="cmtt-10">\null for each missing glossary to assist dictionary style documents that just use \glsaddall without inserting any text.) -

    If the glossary still does not appear after you re-LAT

    If the glossary still does not appear after you re-LATEX your document, check the makeindexEX runs to make the glossaries appear, but number lists up-to-date. -

    An individual glossary can be displayed using: +

    An individual glossary can be displayed using:

    Option 1:
    -



    \printnoidxglossary  \printnoidxglossary[options]

    -

    +

    (Must be used with \makenoidxglossaries in the preamble.) @@ -13910,24 +14239,24 @@ href="#option3">3:

    -



    \printglossary  \printglossary[options]

    -

    +

    (Must be used with \makeglossaries in the preamble.)

    -

    where ⟨

    where ⟨options⟩ is a ⟨key⟩=⟨value⟩ list of options. (Again, when the associated external file is missing, \null is inserted into the document.) -

    The following keys are available: +

    The following keys are available:

    typeThe value of this key specifies which glossary to print. If assumed. For example, to print the list of acronyms: -
    +
    \printglossary[type=\acronymtype]
    -

    Note that you can’t display an ignored glossary, so don’t try setting

    Note that you can’t display an ignored glossary, so don’t try setting type to the name of a glossary that was defined using def (order of definition) nocase (case-insensitive) or case (case-sensitive). -

    If you use the

    If you use the use or def values make sure that you select a glossary style that doesn’t have a visual indicator between groups, as the grouping no longer makes sense. Consider using the nogroupskip option.
    -

    -

    The +

    +

    The word and letter @@ -14119,7 +14448,7 @@ class="cmss-10">datatool

    If you don’t get an error with

    If you don’t get an error with sort=use and sort=def but you do get an error with one of the other sort options, then you probably need to use the sanitizesort=truesort field.

    -

    By default, the glossary is started either by

    By default, the glossary is started either by \chapter* or by \section*numberedsection package option. Each glossary sets the page header via the command -



    \glsglossarymark  \glsglossarymark{⟨title}

    -

    +

    If this mechanism is unsuitable for your chosen class file or page style package, you will need to redefine \glsglossarymark§2.2 Sectioning, Headings and TOC Options. -

    Information can be added to the start of the glossary (after the title and before the main +

    Information can be added to the start of the glossary (after the title and before the main body of the glossary) by redefining -



    \glossarypreamble  \glossarypreamble

    -

    +

    For example:

    -
    +
    \renewcommand{\glossarypreamble}{Numbers in italic  
    indicate primary definitions.}
    -

    This needs to be done before the glossary is displayed. -

    If you want a different preamble per glossary you can use -


    This needs to be done before the glossary is displayed. +

    If you want a different preamble per glossary you can use +


    \setglossarypreamble  type]{preamble text}

    -

    +

    If ⟨type⟩ is omitted, \glsdefaulttype is used. -

    For example: +

    For example:

    -
    +
    \setglossarypreamble{Numbers in italic  
    indicate primary definitions.}
    -

    This will print the given preamble text for the main glossary, but not have any preamble text +

    This will print the given preamble text for the main glossary, but not have any preamble text for any other glossaries. -

    There is an analogous command to

    There is an analogous command to \glossarypreamble called -



    \glossarypostamble  \glossarypostamble

    -

    +

    which is placed at the end of each glossary. -

    Example 15 (Switch to Two Column Mode for Glossary) -

    Suppose you are using the

    Suppose you are using the superheaderborder style -

    +
    \renewcommand*{\glossarysection}[2][]{%  
      \twocolumn[{\chapter*{#2}}]%  
      \setlength\glsdescwidth{0.6\linewidth}% @@ -14239,21 +14568,21 @@ back to one column mode, you could do:  
    }  
    \renewcommand*{\glossarypostamble}{\onecolumn}
    -

    +

    -

    -

    ____________________________

    -

    Within each glossary, each entry name is formatted according to -


    +

    ____________________________

    +

    Within each glossary, each entry name is formatted according to +


    \glsnamefont  \glsnamefont{name}

    -

    +

    which takes one argument: the entry name. This command is always used regardless of the glossary style. By default, \glsnamefont simply displays its argument in whatever the @@ -14272,34 +14601,39 @@ hierarchical glossary styles (defined in the glossary-tree style file) also set the name in bold. +

    If you want to change the font for the description, or if you only want to change the name +font for some types of entries but not others, you might want to consider using the +glossaries-extra package. -

    +

    Example 16 (Changing the Font Used to Display Entry Names in the Glossary) -

    Suppose you want all the entry names to appear in medium weight small caps in your + id="x1-53078"> +

    Suppose you want all the entry names to appear in medium weight small caps in your glossaries, then you can do:

    -
    +
    \renewcommand{\glsnamefont}[1]{\textsc{\mdseries #1}}
    -

    +

    -

    -

    ____________________________

    +

    +

    ____________________________

    -

    -

    +

    Top

    11. Xindy (Option 3)

    -

    If you want to use

    If you want to use xindy to sort the glossary, you must use the package option @@ -14309,13 +14643,13 @@ class="cmss-10">xindy -

    +
    \usepackage[xindy]{glossaries}
    -

    This ensures that the glossary information is written in

    This ensures that the glossary information is written in xindy syntax. -

    §1.4 Generating the Associated Glossary Files covers how to use the external xindy style file (.xdy) and parameters. -

    To assist writing information to the

    To assist writing information to the xindy style file, the glossaries package provides the following commands: -



    \glsopenbrace  \glsopenbrace

    -

    -


    +


    \glsclosebrace  \glsclosebrace

    -

    +

    which produce an open and closing brace. (This is needed because \{ and \} don’t expand to a simple brace character when written to a file.) Similarly, you can write a percent character using: -



    \glspercentchar  \glspercentchar

    -

    +

    and a tilde character using: -



    \glstildechar  \glstildechar

    -

    +

    For example, a newline character is specified in a xindy~n so you can use class="cmtt-10">\glstildechar n to write this correctly (or you can do \string~n). A backslash can be written to a file using -



    \glsbackslash  \glsbackslash

    -

    -

    In addition, if you are using a package that makes the double quote character active (e.g. +

    +

    In addition, if you are using a package that makes the double quote character active (e.g. ngerman) you can use: -



    \glsquote  \glsquote{text}

    -

    +

    which will produce "text\string" to write the double-quote character. This document assumes that the double quote character has not been made active, so the examples just use " for clarity. -

    If you want greater control over the

    If you want greater control over the xindy style file than is available through the @@ -14429,10 +14763,10 @@ class="cmtt-10">http://xindy.sourceforge.net/mailing-list.html).

    -

    Top

    11.1 Language and Encodings

    -

    When you use

    When you use xindy, you need to specify the language and encoding used (unless you @@ -14454,7 +14788,7 @@ language given your document settings, but in the event that it gets it wrong or class="cmtt-10">xindy doesn’t support that language, then you can specify the required language using: -



    \GlsSetXdyLanguage  glossary type]{language}

    -

    +

    where ⟨language⟩ is the name of the language. The optional argument can be used if you have multiple glossaries in different languages. If ⟨glossary type⟩ is omitted, it will be applied to a glossaries, otherwise the language setting will only be applied to the glossary given by ⟨glossary type⟩. -

    If the

    If the inputenc package is used, the encoding will be obtained from the value of \inputencodingname. Alternatively, you can specify the encoding using: -



    \GlsSetXdyCodePage  \GlsSetXdyCodePage{code}

    -

    +

    where ⟨code⟩ is the name of the encoding. For example:

    -
    +
    \GlsSetXdyCodePage{utf8}
    -

    -

    Note that you can also specify the language and encoding using the package option +

    +

    Note that you can also specify the language and encoding using the package option xindy={language=lang}. For example:

    -
    +
    \usepackage[xindy={language=english,codepage=utf8}]{glossaries}
    -

    -

    If you write your own custom

    +

    If you write your own custom xindy style file that includes the language settings, you need @@ -14516,13 +14850,13 @@ to set the language to nothing:

    -
    +
    \GlsSetXdyLanguage{}
    -

    (and remember to use

    (and remember to use \noist to prevent the style file from being overwritten). -

    The commands

    The commands \GlsSetXdyLanguage and \GlsSetXdyCodePage have no effect if you don’t use xindymakeglossaries you need to remember to set the language and encoding using the -L and -C switches. +class="cmtt-10">-L and -C switches.
    -

    -

    +

    +

    -

    Top

    11.2 Locations and Number lists

    -

    If you use

    If you use xindy, the glossaries package needs to know which counters you will be using in the @@ -14570,17 +14906,17 @@ class="cmti-10">before \makeglossaries using: -



    \GlsAddXdyCounters  \GlsAddXdyCounters{counter list}

    -

    +

    where ⟨counter list⟩ is a comma-separated list of counter names. -

    The most likely attributes used in the

    The most likely attributes used in the format key (textrmxindy style file, but if you want to use another attribute, you need to add it using: -



    \GlsAddXdyAttribute  \GlsAddXdyAttribute{name}

    -

    +

    where ⟨name⟩ is the name of the attribute, as used in the format key. +

    Take care if you have multiple instances of the same location with different formats. The +duplicate locations will be discarded according to the order in which the attributes are +listed. Consider defining semantic commands to use for primary references. For +example: + + +

    +
    +\newcommand*{\primary}[1]{\textbf{#1}} + 
    \GlsAddXdyAttribute{primary} +
    +

    Then in the document: + + +

    +
    +A \gls[format=primary]{duck} is an aquatic bird. + 
    There are lots of different types of \gls{duck}. +
    +

    This will give the format=primary instance preference over the next use that doesn’t use the +format key. -

    +

    Example 17 (Custom Font for Displaying a Location) -

    Suppose I want a bold, italic, hyperlinked location. I first need to define a command that + id="x1-56018"> +

    Suppose I want a bold, italic, hyperlinked location. I first need to define a command that will do this:

    -
    +
    \newcommand*{\hyperbfit}[1]{\textit{\hyperbf{#1}}}
    -

    but with

    but with xindy, I also need to add this as an allowed attribute: + id="dx1-56019">, I also need to add this as an allowed attribute:

    -
    +
    \GlsAddXdyAttribute{hyperbfit}
    -

    Now I can use it in the optional argument of commands like

    Now I can use it in the optional argument of commands like \gls: + id="dx1-56020">:

    -
    +
    Here is a \gls[format=hyperbfit]{sample} entry.
    -

    (where

    (where sample is the label of the required entry).

    -

    -

    ____________________________

    -

    Note that

    +

    ____________________________

    +

    Note that \GlsAddXdyAttribute has no effect if \noist is used or if is used or if \makeglossaries is + id="dx1-56022"> is omitted. \GlsAddXdyAttribute must be used before \makeglossaries. Additionally, + id="dx1-56023">. Additionally, \GlsAddXdyCounters must come before \GlsAddXdyAttribute.
    -

    -

    If the location numbers include formatting commands, then you need to add a location +

    +

    If the location numbers include formatting commands, then you need to add a location style in the appropriate format using -



    \GlsAddXdyLocation  \GlsAddXdyLocation[prefix-location]{}{definition}

    -

    +

    where ⟨name⟩ is the name of the format and ⟨definition⟩ is the xindy definition. The optional + id="dx1-56025"> definition. The optional argument ⟨prefix-location⟩ is needed if \theH\thecounter⟩. (See also \glsaddprotectedpagefmt described in described in §5 Number lists.) -

    Note that

    Note that \GlsAddXdyLocation has no effect if \noist is used or if is used or if \makeglossaries is + id="dx1-56028"> is omitted. \GlsAddXdyLocation must be used before \makeglossaries.
    -

    + id="dx1-56029">.

    +

    -

    +

    Example 18 (Custom Numbering System for Locations) -

    Suppose I decide to use a somewhat eccentric numbering system for sections where I + id="x1-56031"> +

    Suppose I decide to use a somewhat eccentric numbering system for sections where I redefine \thesection as follows:

    -
    +
    \renewcommand*{\thesection}{[\thechapter]\arabic{section}}
    -

    If I haven’t done

    If I haven’t done counter=section in the package option, I need to specify that the counter will be used as a location number:

    -
    +
    \GlsAddXdyCounters{section}
    -

    Next I need to add the location style (

    Next I need to add the location style (\thechapter is assumed to be the standard \arabic{chapter}):

    -
    +
    \GlsAddXdyLocation{section}{:sep "[" "arabic-numbers" :sep "]"  
      "arabic-numbers"  
    }
    -

    Note that if I have further decided to use the

    Note that if I have further decided to use the hyperref package and want to redefine + id="dx1-56032"> package and want to redefine \theHsection as:

    -
    +
    \renewcommand*{\theHsection}{\thepart.\thesection}  
    \renewcommand*{\thepart}{\Roman{part}}
    -

    then I need to modify the

    then I need to modify the \GlsAddXdyLocation code above to:

    -
    +
    \GlsAddXdyLocation["roman-numbers-uppercase"]{section}{:sep "["  
      "arabic-numbers" :sep "]" "arabic-numbers"  
    }
    -

    Since

    Since \Roman will result in an empty string if the counter is zero, it’s a good idea to add an + id="dx1-56033"> will result in an empty string if the counter is zero, it’s a good idea to add an extra location to catch this:

    -
    +
    \GlsAddXdyLocation{zero.section}{:sep "["  
      "arabic-numbers" :sep "]" "arabic-numbers"  
    }
    -

    This example is illustrated in the sample file

    This example is illustrated in the sample file samplexdy2.tex.

    -

    -

    ____________________________

    +

    +

    ____________________________

    -

    +

    Example 19 (Locations as Words not Digits) -

    Suppose I want the page numbers written as words rather than digits and I use the + id="x1-56035"> +

    Suppose I want the page numbers written as words rather than digits and I use the fmtcount package to do this. I can redefine package to do this. I can redefine \thepage as follows: + id="dx1-56037"> as follows:

    -
    +
    \renewcommand*{\thepage}{\Numberstring{page}}
    -

    This gets expanded to

    This gets expanded to \protect \Numberstringnum  -

    +
    \GlsAddXdyLocation{Numberstring}{:sep "\string\protect\space  
      \string\Numberstringnum\space\glsopenbrace"  
      "arabic-numbers" :sep "\glsclosebrace"}
    -

    Note that it’s necessary to use

    Note that it’s necessary to use \space to indicate that spaces also appear in the format, since, unlike TEX, xindy doesn’t ignore spaces after control sequences. -

    Note that doesn’t ignore spaces after control sequences. +

    Note that \GlsAddXdyLocation{name}{definition} will define commands in the form: -



    \glsXcounterXHprefix}{location}

    -

    +

    for each counter that has been identified either by the counter package option, the ⟨ package option, the ⟨counter⟩ option for \newglossary or in the argument of or in the argument of \GlsAddXdyCounters. -

    The first argument ⟨. +

    The first argument ⟨Hprefix⟩ is only relevant when used with the hyperref package and + id="dx1-56042"> package and indicates that \theHcounter⟩ is given by .\thecounter⟩. The sample file samplexdy.tex, which comes with the glossaries package, uses the default page counter for + id="dx1-56043"> counter for locations, and it uses the default \glsnumberformat and a custom and a custom \hyperbfit format. A new xindy location called location called Numberstring, as illustrated above, is defined to make the page numbers appear as “One”, “Two”, etc. In order for the location numbers to hyperlink to the relevant pages, I need to redefine the necessary -

    +
    \renewcommand{\glsXpageXglsnumberformat}[2]{%  
     \linkpagenumber#2%  
    } @@ -14893,14 +15253,14 @@ commands:  
    }  
    \newcommand{\linkpagenumber}[3]{\hyperlink{page.#3}{#1#2{#3}}}
    -

    +

    -

    -

    ____________________________

    -

    In the

    +

    ____________________________

    +

    In the number list, the locations are sorted according to type. The default + id="dx1-56046">, the locations are sorted according to type. The default ordering is: roman-page-numbers (e.g. i), arabic-page-numbers (e.g. 1), @@ -14908,7 +15268,7 @@ class="cmtt-10">arabic-page-numbers (e.g. 1), class="cmtt-10">arabic-section-numbers (e.g. 1.1 if the compositor is a full stop or 1-1 if the compositor is a hyphen11.1), + id="x1-56047f1">), alpha-page-numbers (e.g. a), Roman-page-numbers (e.g. I), Alpha-page-numbers (e.g. A), class="cmtt-10">Appendix-page-numbers (e.g. A.1 if the Alpha compositor is a full stop or A-1 if the Alpha compositor is a hyphen11.2), + id="x1-56049f2">), user defined location names (as specified by \GlsAddXdyLocation in the order in which + id="dx1-56051"> in the order in which they were defined), see (cross-referenced entries). This ordering can be changed using: -

    \GlsSetXdyLocationClassOrder  -


    +


    \GlsSetXdyLocationClassOrder{location names}

    -

    +

    where each location name is delimited by double quote marks and separated by white space. For example:

    -
    +
    \GlsSetXdyLocationClassOrder{  
      "arabic-page-numbers"  
      "arabic-section-numbers" @@ -14950,69 +15310,69 @@ For example:  
      "see"  
    }
    -

    -

    Note that

    +

    Note that \GlsSetXdyLocationClassOrder has no effect if \noist is used or if + id="dx1-56053"> is used or if \makeglossaries is omitted. is omitted. \GlsSetXdyLocationClassOrder must be used before \makeglossaries.
    -

    -

    If a .

    +

    +

    If a number list consists of a sequence of consecutive numbers, the range will be + id="dx1-56056"> consists of a sequence of consecutive numbers, the range will be concatenated. The number of consecutive locations that causes a range formation defaults to 2, but can be changed using: -

    \GlsSetXdyMinRangeLength  -


    +


    \GlsSetXdyMinRangeLength{n}

    -

    +

    For example:

    -
    +
    \GlsSetXdyMinRangeLength{3}
    -

    The argument may also be the keyword

    The argument may also be the keyword none, to indicate that there should be no range formations. See the xindy manual for further details on range formations. -

    Note that manual for further details on range formations. +

    Note that \GlsSetXdyMinRangeLength has no effect if \noist is used or if + id="dx1-56059"> is used or if \makeglossaries is omitted. is omitted. \GlsSetXdyMinRangeLength must be used before \makeglossaries.
    -

    -

    See .

    +

    +

    See §5 Number lists for further details.

    -

    Top

    11.3 Glossary Groups

    -

    The glossary is divided into groups according to the first letter of the sort key. The

    The glossary is divided into groups according to the first letter of the sort key. The glossaries package also adds a number group by default, unless you suppress it in the xindy -

    +
    \usepackage[xindy={glsnumbers=false}]{glossaries}
    -

    Any entry that doesn’t go in one of the letter groups or the number group is placed in the +

    Any entry that doesn’t go in one of the letter groups or the number group is placed in the default group. -

    If you have a number group, the default behaviour is to locate it before the “A” letter +

    If you have a number group, the default behaviour is to locate it before the “A” letter group. If you are not using a Roman alphabet, you can change this using: -

    \GlsSetXdyFirstLetterAfterDigits  -



    \GlsSetXdyFirstLetterAfterDigits{letter}

    -

    -

    Note that

    +

    Note that \GlsSetXdyFirstLetterAfterDigits has no effect if \noist is used or if @@ -15049,16 +15409,16 @@ class="cmtt-10">\GlsSetXdyFirstLetterAfterDigits must be used before class="cmtt-10">\makeglossaries.
    -

    +

    -

    -

    +

    Top

    12. Defining New Glossaries

    -

    A new glossary can be defined using: -


    A new glossary can be defined using: +


    \newglossary  title}[counter]

    -

    +

    where ⟨name⟩ is the label to assign to this glossary. The arguments ⟨in-ext⟩ and ⟨log-ext⟩, ⟨in-ext⟩ and ⟨out-ext⟩ arguments are ignored. -

    The glossary label ⟨

    The glossary label ⟨name⟩ must not contain any active characters. It’s generally best to stick with just characters that have category code 11 (typically the non-extended Latin characters for standard LATEX).
    -

    -

    There is also a starred version (new to v4.08): -


    +

    There is also a starred version (new to v4.08): +


    \newglossary*  title}[counter]

    -

    +

    which is equivalent to

    counter]
    or you can also use: -



    \altnewglossary  title}[counter]

    -

    +

    which is equivalent to

    counter]
    -

    It may be that you have some terms that are so common that they don’t need to be listed. +

    It may be that you have some terms that are so common that they don’t need to be listed. In this case, you can define a special type of glossary that doesn’t create any associated files. This is referred to as an “ignored glossary” and it’s ignored by commands that iterate over all the glossaries, such as \printglossaries. To define an ignored glossary, use -



    \newignoredglossary  \newignoredglossary{name}

    -

    +

    where ⟨name⟩ is the name of the glossary (as above). This glossary type will automatically be @@ -15213,11 +15573,11 @@ added to the nohypertypes list, since there are no hypertargets for the entries in an ignored glossary. (The sample file sample-entryfmt.tex defines an ignored glossary.) -

    You can test if a glossary is an ignored one using: -


    You can test if a glossary is an ignored one using: +


    \ifignoredglossary  true}{false}

    -

    +

    This does ⟨true⟩ if ⟨name⟩ was defined as an ignored glossary, otherwise it does ⟨false⟩. -

    Note that the main (default) glossary is automatically created as: +

    Note that the main (default) glossary is automatically created as:

    -
    +
    \newglossary{main}{gls}{glo}{\glossaryname}
    -

    so it can be identified by the label

    so it can be identified by the label main (unless the nomain package option is used). Using @@ -15250,10 +15610,10 @@ class="cmss-10">acronym -

    +
    \newglossary[alg]{acronym}{acr}{acn}{\acronymname}
    -

    so it can be identified by the label

    so it can be identified by the label acronym. If you are not sure whether the acronym @@ -15272,44 +15632,44 @@ acronyms, you need to declare it as a list of acronyms using the package option acronymlists. -

    The

    The symbols package option creates a new glossary with the label symbols using:

    -
    +
    \newglossary[slg]{symbols}{sls}{slo}{\glssymbolsgroupname}
    -

    The

    The numbers package option creates a new glossary with the label numbers using:

    -
    +
    \newglossary[nlg]{numbers}{nls}{nlo}{\glsnumbersgroupname}
    -

    The

    The index package option creates a new glossary with the label index using:

    -
    +
    \newglossary[ilg]{index}{ind}{idx}{\indexname}
    -

    -

    Options 

    +

    Options 2 and 3: all glossaries must be defined before \makeglossaries to ensure that the relevant output files are opened. -

    See

    See §1.3.1 Changing the Fixed Names if you want to redefine \indexname, just follow the advice in How to change LaTeX’s “fixed names”.

    -

    +

    -

    -

    +

    Top

    13. Acronyms and Other Abbreviations

    -

    Note that although this chapter uses the term “acronym”, you can also use the +

    Note that although this chapter uses the term “acronym”, you can also use the commands described here for initialisms or contractions (as in the case of some of the examples given below). If the glossary title is no longer applicable (for example, it should be “Abbreviations” rather than “Acronyms”) then you can change the title @@ -15357,8 +15717,8 @@ class="cmss-10">glossaries-extra package which defines \newabbreviation and treats acronyms (e.g. “laser”) differently from other forms of abbreviations (e.g. “html”).
    -

    -

    You may have noticed in

    +

    You may have noticed in §4 Defining Glossary Entries that when you specify a new entry, @@ -15367,7 +15727,7 @@ href="#glo:firstuse">first used in the document. This provides a useful means to define abbreviations. For convenience, the glossaries package defines the command: -



    \newacronym  abbrv}{long}

    -

    -

    This uses

    +

    This uses \newglossaryentry to create an entry with the given label in the glossary given by shortplural\newglossaryentry to store the long and abbreviated forms and their plurals. -

    If you haven’t identified the specified glossary type as a list of acronyms (via +

    Note that the same restrictions on the entry ⟨label⟩ in \newglossaryentry also apply to +\newacronym (see §4 Defining Glossary Entries). +

    If you haven’t identified the specified glossary type as a list of acronyms (via the package option acronymlists or the command or the command \DeclareAcronymList, see , see §2.5 \newacronym will add it to the list and reset the display style for that glossary via \defglsentryfmt. If you have a mixture of acronyms and + id="dx1-59016">. If you have a mixture of acronyms and regular entries within the same glossary, care is needed if you want to change the display style: you must first identify that glossary as a list of acronyms and then use \defglsentryfmt (not redefine (not redefine \glsentryfmt) before defining your entries. + id="dx1-59018">) before defining your entries.
    -

    -

    The optional argument

    +

    The optional argument {key-val list} allows you to specify keys such as description (when + id="dx1-59019"> (when used with one of the styles that require a description, described in §13.1 ) or you can overri class="cmti-10">abbrv⟩ or ⟨long⟩ using the shortplural or + id="dx1-59020"> or longplural keys. For example: + id="dx1-59021"> keys. For example:

    -
    +
    \newacronym[longplural={diagonal matrices}]%  
      {dm}{DM}{diagonal matrix}
    -

    If the

    If the first use uses the plural form, \glspl{dm} will display: diagonal matrices (DMs). If you want to use the longplural or or shortplural keys, I recommend you use + id="dx1-59023"> keys, I recommend you use \setacronymstyle to set the display style rather than using one of the pre-version 4.02 + id="dx1-59024"> to set the display style rather than using one of the pre-version 4.02 acronym styles. -

    Since

    Since \newacronym uses uses \newglossaryentry, you can use commands like , you can use commands like \gls and + id="dx1-59027"> and \glsreset as with any other glossary entry. -

    Since as with any other glossary entry. +

    Since \newacronym sets type=\acronymtype, if you want to load a file containing acronym definitions using \loadglsentries[type]{type=\glsdefaulttype in the optional argument to \newacronym. See . See §4.8 Loading Entries From a File.
    -

    +

    -

    +

    Example 20 (Defining an Abbreviation) -

    The following defines the abbreviation IDN: + id="x1-59032"> +

    The following defines the abbreviation IDN:

    -
    +
    \newacronym{idn}{IDN}{identification number}
    -

    \gls{idn} will produce “identification number (IDN)” on first use and “IDN” on subsequent uses. If you want to use one of the smallcaps acronym styles, described in -

    +

    Recall from the warning in §4 Defining Glossary Entries that you should avoid using the @@ -15549,74 +15918,74 @@ class="cmtt-10">\gls-like and \glstext-like commands within the value of keys like text and and first due to + id="dx1-59034"> due to complications arising from nested links. The same applies to abbreviations defined using \newacronym. -

    For example, suppose you have defined: +

    For example, suppose you have defined:

    -
    +
    \newacronym{ssi}{SSI}{server side includes}  
    \newacronym{html}{HTML}{hypertext markup language}
    -

    you may be tempted to do: +

    you may be tempted to do:

    -
    +
    \newacronym{shtml}{S\gls{html}}{\gls{ssi} enabled \gls{html}}
    -

    Don’t! This will break the case-changing commands, such as \Gls, it will cause + id="dx1-59035">, it will cause inconsistencies on first use, and, if hyperlinks are enabled, will cause nested hyperlinks. It will also confuse the commands used by the entry formatting (such as \glslabel). -

    Instead, consider doing: + id="dx1-59036">). +

    Instead, consider doing:

    -
    +
    \newacronym  
     [description={\gls{ssi} enabled \gls{html}}]  
     {shtml}{SHTML}{SSI enabled HTML}
    -

    or +

    or

    -
    +
    \newacronym  
     [description={\gls{ssi} enabled \gls{html}}]  
     {shtml}{SHTML}  
     {server side includes enabled hypertext markup language}
    -

    Similarly for the

    Similarly for the \glstext-like commands. -

    The commands described below are similar to the

    The commands described below are similar to the \glstext-like commands in that they don’t modify the first use flag. However, their display is governed by \defentryfmt with + id="dx1-59037"> with \glscustomtext set as appropriate. All caveats that apply to the set as appropriate. All caveats that apply to the \glstext-like commands also apply to the following commands. (Including the warning immediately above this box.)
    -

    -

    The optional arguments are the same as those for the

    +

    The optional arguments are the same as those for the \glstext-like commands, and there are similar star and plus variants that switch off or on the hyperlinks. @@ -15624,14 +15993,14 @@ As with the \glstext-like commands, the link text is placed in the argument of + id="dx1-59039"> is placed in the argument of \glstextformat. -


    . +


    \acrshort  \acrshort[options]{label}[insert]

    -

    +

    This sets the link text to the short form (within the argument of to the short form (within the argument of \acronymfont) for the entry + id="dx1-59043">) for the entry given by ⟨label⟩. The short form is as supplied by the short key, which key, which \newacronym implicitly + id="dx1-59045"> implicitly sets. -

    There are also analogous upper case variants: -


    There are also analogous upper case variants: +


    \Acrshort  \Acrshort[options]{label}[insert]

    -

    -


    +


    \ACRshort  \ACRshort[options]{label}[insert]

    -

    +

    There are also plural versions: -



    \acrshortpl  \acrshortpl[options]{label}[insert]

    -

    -


    +


    \Acrshortpl  \Acrshortpl[options]{label}[insert]

    -

    -


    +


    \ACRshortpl  \ACRshortpl[options]{label}[insert]

    -

    +

    The short plural form is as supplied by the shortplural key, which key, which \newacronym implicitly + id="dx1-59052"> implicitly sets. -



    \acrlong  \acrlong[options]{label}[insert]

    -

    +

    This sets the link text to the long form for the entry given by ⟨ to the long form for the entry given by ⟨label⟩. The long form is as supplied by the long key, which key, which \newacronym implicitly sets. + id="dx1-59056"> implicitly sets. -

    There are also analogous upper case variants: -


    There are also analogous upper case variants: +


    \Acrlong  \Acrlong[options]{label}[insert]

    -

    -


    +


    \ACRlong  \ACRlong[options]{label}[insert]

    -

    +

    Again there are also plural versions: -



    \acrlongpl  \acrlongpl[options]{label}[insert]

    -

    -


    +


    \Acrlongpl  \Acrlongpl[options]{label}[insert]

    -

    -


    +


    \ACRlongpl  \ACRlongpl[options]{label}[insert]

    -

    +

    The long plural form is as supplied by the longplural key, which key, which \newacronym implicitly + id="dx1-59063"> implicitly sets. -

    The commands below display the full form of the acronym, but note that this isn’t +

    The commands below display the full form of the acronym, but note that this isn’t necessarily the same as the form used on first use. These full-form commands are shortcuts that use the above commands, rather than creating the link text from the complete full form. + id="dx1-59064"> from the complete full form. These full-form commands have star and plus variants and optional arguments that are passed to the above commands. -



    \acrfull  \acrfull[options]{label}[insert]

    -

    +

    This is a shortcut for -



    \acrfullfmt  \acrfullfmt{options}{label}{insert}

    -

    +

    which by default does

    }}
    where -



    \acrfullformat  \acrfullformat{long}{short}

    -

    +

    by default does ⟨long⟩ (⟨short⟩). (For further details of these format commands see the documented code, glossaries-code.pdf.) -

    There are also analogous upper case variants: -


    There are also analogous upper case variants: +


    \Acrfull  \Acrfull[options]{label}[insert]

    -

    -


    +


    \ACRfull  \ACRfull[options]{label}[insert]

    -

    +

    and plural versions: -



    \acrfullpl  \acrfullpl[options]{label}[insert]

    -

    -


    +


    \Acrfullpl  \Acrfullpl[options]{label}[insert]

    -

    -


    +


    \ACRfullpl  \ACRfullpl[options]{label}[insert]

    -

    -

    If you find the above commands too cumbersome to write, you can use the

    +

    If you find the above commands too cumbersome to write, you can use the shortcuts + id="dx1-59073"> package option to activate the shorter command names listed in table 13.1.

    -


    @@ -15966,7 +16335,7 @@ href="#tab:shortcuts">table 13.1.
    Table 13.1: Synonyms provided by the package option shortcuts
    +class="cmss-10">shortcuts
    Equivalent Command style="vertical-align:baseline;" id="TBL-7-2-"> + id="dx1-59076"> + id="dx1-59078"> + id="dx1-59080"> + id="dx1-59082"> + id="dx1-59084"> + id="dx1-59086"> + id="dx1-59088"> + id="dx1-59090"> + id="dx1-59092"> + id="dx1-59094"> + id="dx1-59096"> + id="dx1-59098"> + id="dx1-59100"> + id="dx1-59102"> + id="dx1-59104">
    \acs \acrshort
    \Acs \Acrshort
    \acsp \acrshortpl
    \Acsp \Acrshortpl
    \acl \acrlong
    \Acl \Acrlong
    \aclp \acrlongpl
    \Aclp \Acrlongpl
    \acf \acrfull
    \Acf \Acrfull
    \acfp \acrfullpl
    \Acfp \Acrfullpl
    \ac \gls
    \Ac \Gls
    \acp \glspl
    \Acp \Glspl
    + id="dx1-59106">

    -

    It is also possible to access the long and short forms without adding information to the +

    It is also possible to access the long and short forms without adding information to the glossary using commands analogous to \glsentrytext (described in (described in §9 Using Glossary Terms Without Links). -

    The commands that convert the first letter to upper case come with the same caveats as +

    The commands that convert the first letter to upper case come with the same caveats as those for analogous commands like \Glsentrytext (non-expandable, can’t be used in PDF + id="dx1-59108"> (non-expandable, can’t be used in PDF bookmarks, care needs to be taken if the first letter is an accented character etc). See §9 Using Glossary Terms Without Links.
    -

    -

    The long form can be accessed using: -


    +

    The long form can be accessed using: +


    \glsentrylong  \glsentrylong{label}

    -

    +

    or, with the first letter converted to upper case: -



    \Glsentrylong  \Glsentrylong{label}

    -

    +

    Plural forms: -



    \glsentrylongpl  \glsentrylongpl{label}

    -

    -


    +


    \Glsentrylongpl  \Glsentrylongpl{label}

    -

    -

    Similarly, to access the short form: -


    +

    Similarly, to access the short form: +


    \glsentryshort  \glsentryshort{label}

    -

    +

    or, with the first letter converted to upper case: -



    \Glsentryshort  \Glsentryshort{label}

    -

    +

    Plural forms: -



    \glsentryshortpl  \glsentryshortpl{label}

    -

    -


    +


    \Glsentryshortpl  \Glsentryshortpl{label}

    -

    -

    And the full form can be obtained using: -


    +

    And the full form can be obtained using: +


    \glsentryfull  \glsentryfull{label}

    -

    -


    +


    \Glsentryfull  \Glsentryfull{label}

    -

    -


    +


    \glsentryfullpl  \glsentryfullpl{label}

    -

    -


    +


    \Glsentryfullpl  \Glsentryfullpl{label}

    -

    +

    These again use \acrfullformat by default, but the format may be redefined by the + id="dx1-59121"> by default, but the format may be redefined by the acronym style.

    -

    Top

    13.1 Changing the Abbreviation Style

    -

    It may be that the default style doesn’t suit your requirements in which case you can switch +

    It may be that the default style doesn’t suit your requirements in which case you can switch to another styles using -



    \setacronymstyle  \setacronymstyle{style name}

    -

    +

    where ⟨style name⟩ is the name of the required style. -

    You must use

    You must use \setacronymstyle before you define the acronyms with \newacronym. If @@ -16262,8 +16631,8 @@ class="cmtt-10">\setacronymstyle after using \DeclareAcronymList.
    -

    -

    The

    +

    The glossaries package has the restriction that only one style may be in use that applies to all entries defined with \newacronym. If you need multiple abbreviation @@ -16271,7 +16640,7 @@ styles, then try using the glossaries-extra package, which has better abbreviation management. -

    Note that unlike the default behaviour of

    Note that unlike the default behaviour of \newacronym, the styles used via \setacronymstyle don’t use the \glsgenacfmt\genacrfullformat. -

    Note that when you use

    Note that when you use \setacronymstyle the name key is set to -



    \acronymentry  \acronymentry{label}

    -

    +

    and the sort key is set to -



    \acronymsort  short}{long}

    -

    +

    These commands are redefined by the acronym styles. However, you can redefine them again after the style has been set but before you use \newacronym. Protected expansion is performed on \acronymsort when the entry is defined. -

    +

    -

    Top

    13.1.1 Predefined Acronym Styles

    -

    The

    The glossaries package provides a number of predefined styles. These styles apply -



    \firstacronymfont  \firstacronymfont{text}

    -

    +

    to the short form on first use and -



    \acronymfont  \acronymfont{text}

    -

    +

    on subsequent use. The styles modify the definition of \acronymfont as required, but \firstacronymfont independently of the acronym style. -

    The predefined styles that contain

    The predefined styles that contain sc in their name (for example long-sc-short) redefine @@ -16378,9 +16747,9 @@ class="cmtt-10">\acronymfont to use \textsc, which means that the short form needs to be specified in lower case. -

    -

    Some fonts don’t support bold smallcaps, so you may need to redefine

    Some fonts don’t support bold smallcaps, so you may need to redefine \glsnamefont (see \textsc.
    -

    -

    The predefined styles that contain

    +

    The predefined styles that contain sm in their name (for example long-sm-short) redefine @@ -16400,9 +16769,9 @@ class="cmss-10">long-sm-short\acronymfont to use \textsmaller. -

    -

    Note that the

    Note that the glossaries package doesn’t define or load any package that defines \textsmallerrelsize package or otherwise define \textsmaller.
    -

    -

    The remaining predefined styles redefine

    +

    The remaining predefined styles redefine \acronymfont{text} to simply do its argument ⟨text⟩. -

    In most cases, the predefined styles adjust

    In most cases, the predefined styles adjust \acrfull and \glsentryfullduafootnote styles (and their variants).
    -

    -

    The following styles are supplied by the

    +

    The following styles are supplied by the glossaries package:

    • long-sm-short, long-sp-short: -

      With these three styles, acronyms are displayed in the form -


      With these three styles, acronyms are displayed in the form +


      long(\firstacronymfont{short})

      -

      +

      on first use and -



      \acronymfont{short}

      -

      +

      on subsequent use. They also set \acronymsort{short\acronymfont) and the description key is set to the long form. -

      The

      The long-sp-short style was introduced in version 4.16 and uses -



      \glsacspace  \glsacspace{label}

      -

      +

      for the space between the long and short forms. This defaults to a non-breakable space (~) if (}) is less than 3em, otherwise it uses a normal sp

      -
      +
      \renewcommand*{\glsacspace}[1]{~}
      -

      +

    • short-longsc-short-long, sm-short-long: -

      These three styles are analogous to the above three styles, except the display order is +

      These three styles are analogous to the above three styles, except the display order is swapped to -



      \firstacronymfont{short} (long)

      -

      +

      on first use. -

      Note, however, that

      Note, however, that \acronymsort and \acronymentrylong-sm-short-desc, long-sp-short-desc: -

      These are like the

      These are like the long-short, long-sc-shortsc-short-long-desc, sm-short-long-desc: -

      These styles are analogous to the above three styles, but the first use display style +

      These styles are analogous to the above three styles, but the first use display style is: -



      \firstacronymfont{short} (long)

      -

      +

      The definitions of \acronymsort and \acronymentry are the same as those for @@ -16614,7 +16983,7 @@ class="cmss-10">dua-desc: -

      With these styles, the

      With these styles, the \gls-like commands always display the long form regardless of whether the entry has been used or not. However, footnote-sc, footnote-sm: -

      With these three styles, on first use the

      With these three styles, on first use the \gls-like commands display: -



      \firstacronymfont{short}\footnote}\footnote{⟨long}

      -

      +

      However, \acrfull and short} (⟨long⟩). On subsequent use the display is: -



      \acronymfont{short}

      -

      +

      The sort and namedescription is set to the long form. -

      In order to avoid nested hyperlinks on

      In order to avoid nested hyperlinks on first use the footnote styles automatically implement hyperfirst=false for the acronym lists.
      -

      +

    • footnote-descfootnote-sc-desc, footnote-sm-desc: -

      These three styles are similar to the previous three styles, but the description +

      These three styles are similar to the previous three styles, but the description has to be supplied in the optional argument of \newacronym. The altlist

    -

    Example 21 (Adapting a Predefined Acronym Style) -

    Suppose I want to use the

    Suppose I want to use the footnote-sc-desc style, but I want the namefootnote-sc-desc -

    +
    \setacronymstyle{footnote-sc-desc}
    -

    and then redefine

    and then redefine \acronymsort and \acronymentry\acronymentry -

    +
    \renewcommand*{\acronymsort}[2]{#1}% sort by short form  
    \renewcommand*{\acronymentry}[1]{%  
      \acronymfont{\glsentryshort{#1}}\space (\glsentrylong{#1})}%
    -

    (I’ve used

    (I’ve used \space for extra clarity, but you can just use an actual space instead.) -

    Since the default Computer Modern fonts don’t support bold smallcaps, I’m also going to +

    Since the default Computer Modern fonts don’t support bold smallcaps, I’m also going to redefine \acronymfont so that it always switches to medium weight to ensure the smallcaps @@ -16766,27 +17135,27 @@ setting is used:

    -
    +
    \renewcommand*{\acronymfont}[1]{\textmd{\scshape #1}}
    -

    This isn’t necessary if you use a font that supports bold smallcaps. -

    The sample file

    This isn’t necessary if you use a font that supports bold smallcaps. +

    The sample file sampleFnAcrDesc.tex illustrates this example.

    -

    -

    ____________________________

    -

    +

    +

    ____________________________

    +

    -

    Top

    13.1.2 Defining A Custom Acronym Style

    -

    You may find that the predefined acronyms styles that come with the

    You may find that the predefined acronyms styles that come with the glossaries package don’t suit your requirements. In this case you can define your own style using: -



    \newacronymstyle  }{definitions}

    -

    +

    where ⟨style name⟩ is the name of the new style (avoid active characters). The second argument, ⟨ -

    +
    \ifglshaslong{\glslabel}{\glsgenacfmt}{\glsgenentryfmt}%
    -

    (You can use

    (You can use \ifglshasshort instead of \ifglshaslong to test if the entry is an acronym if you prefer.) -

    The third argument, ⟨

    The third argument, ⟨definitions⟩, can be used to redefine the commands that affect the display style, such as \acronymfont\glsgenacfmt, \genacrfullformat and its variants. -

    Note that

    Note that \setacronymstyle redefines \glsentryfulldua\newacronymstyle should redefine these commands within ⟨definitions⟩. -

    Within

    Within \newacronymstyle’s ⟨definitions⟩ argument you can also redefine -



    \GenericAcronymFields  \GenericAcronymFields

    -

    +

    This is a list of additional fields to be set in \newacronym. You can use the following token @@ -16910,11 +17279,11 @@ does:

    -
    +
    \renewcommand*{\GenericAcronymFields}{%  
       description={\the\glslongtok}}%
    -

    which sets the

    which sets the description field to the long form of the acronym whereas the long-short-desc -

    +
    \renewcommand*{\GenericAcronymFields}{}%
    -

    since the description needs to be specified by the user. -

    It may be that you want to define a new acronym style that’s based on an existing style. +

    since the description needs to be specified by the user. +

    It may be that you want to define a new acronym style that’s based on an existing style. Within ⟨display⟩ you can use -

    \GlsUseAcrEntryDispStyle  -



    \GlsUseAcrEntryDispStyle{style name}

    -

    +

    to use the ⟨display⟩ definition from the style given by ⟨style name⟩. Within ⟨definitions⟩ you can use -



    \GlsUseAcrStyleDefs  \GlsUseAcrStyleDefs{style name}

    -

    +

    to use the ⟨definitions⟩ from the style given by ⟨style name⟩. For example, the definitions⟩):

    -
    +
    \newacronymstyle{long-sc-short}%  
    {% use the same display as "long-short"  
      \GlsUseAcrEntryDispStyle{long-short}% @@ -16979,7 +17348,7 @@ class="cmti-10">definitions⟩):  
      \renewcommand*{\acrpluralsuffix}{\glstextup{\glspluralsuffix}}%  
    }
    -

    (

    (\glstextup ms.) -

    Example 22 (Defining a Custom Acronym Style) -

    Suppose I want my acronym on

    Suppose I want my acronym on first use to have the short form in the text and the long form with the description in a footnote. Suppose also that I want the short form to be put in small caps in the main body of the document, but I want it in normal capitals in the list of @@ -17046,17 +17415,17 @@ class="cmti-10">long⟩ (⟨short⟩) ⟨description
    -

    Let’s suppose it’s possible that I may have a mixed glossary. I can check this in the second +

    Let’s suppose it’s possible that I may have a mixed glossary. I can check this in the second argument of \newacronymstyle using:

    -
    +
    \ifglshaslong{\glslabel}{\glsgenacfmt}{\glsgenentryfmt}%
    -

    This will use

    This will use \glsgenentryfmt if the entry isn’t an acronym, otherwise it will use #):

    -
    +
     % No case change, singular first use:  
      \renewcommand*{\genacrfullformat}[2]{%  
       \firstacronymfont{\glsentryshort{##1}}##2% @@ -17098,12 +17467,12 @@ class="cmtt-10">#):  
       \footnote{\glsentrylongpl{##1}: \glsentrydesc{##1}}%  
      }%
    -

    If you think it inappropriate for the short form to be capitalised at the start of a sentence +

    If you think it inappropriate for the short form to be capitalised at the start of a sentence you can change the above to:

    -
    +
     % No case change, singular first use:  
      \renewcommand*{\genacrfullformat}[2]{%  
       \firstacronymfont{\glsentryshort{##1}}##2% @@ -17117,7 +17486,7 @@ you can change the above to:  
     \let\Genacrfullformat\genacrfullformat  
     \let\Genplacrfullformat\genplacrfullformat
    -

    Another variation is to use

    Another variation is to use \Glsentrylong and \Glsentrylongpl\glsentrylong and \glsentrylongpl. -

    Now let’s suppose that commands such as

    Now let’s suppose that commands such as \glsentryfull and \acrfull\glsentryfull, \acrfullfmt and their plural and upper case variants. -

    First, the non-linking commands: +

    First, the non-linking commands:

    -
    +
      \renewcommand*{\glsentryfull}[1]{%  
        \glsentrylong{##1}\space  
          (\acronymfont{\glsentryshort{##1}})% @@ -17162,11 +17531,11 @@ variants.  
          (\acronymfont{\glsentryshortpl{##1}})%  
      }%
    -

    Now for the linking commands: +

    Now for the linking commands:

    -
    +
      \renewcommand*{\acrfullfmt}[3]{%  
        \glslink[##1]{##2}{%  
         \glsentrylong{##2}##3\space @@ -17208,40 +17577,40 @@ variants.  
        }%  
      }%
    -

    (This may cause problems with long hyperlinks, in which case adjust the definitions so that, +

    (This may cause problems with long hyperlinks, in which case adjust the definitions so that, for example, only the short form is inside the argument of \glslink.) -

    The style also needs to redefine

    The style also needs to redefine \acronymsort so that the acronyms are sorted according to the long form:

    -
    +
      \renewcommand*{\acronymsort}[2]{##2}%
    -

    If you prefer them to be sorted according to the short form you can change the above +

    If you prefer them to be sorted according to the short form you can change the above to:

    -
    +
      \renewcommand*{\acronymsort}[2]{##1}%
    -

    The acronym font needs to be set to

    The acronym font needs to be set to \textsc and the plural suffix adjusted so that the “s” suffix in the plural short form doesn’t get converted to smallcaps:

    -
    +
      \renewcommand*{\acronymfont}[1]{\textsc{##1}}%  
      \renewcommand*{\acrpluralsuffix}{\glstextup{\glspluralsuffix}}%
    -

    There are a number of ways of dealing with the format in the list of acronyms. The simplest +

    There are a number of ways of dealing with the format in the list of acronyms. The simplest way is to redefine \acronymentry to the long form followed by the upper case short form in @@ -17249,18 +17618,18 @@ parentheses:

    -
    +
     \renewcommand*{\acronymentry}[1]{%  
       \Glsentrylong{##1}\space  
         (\MakeTextUppercase{\glsentryshort{##1}})}%
    -

    (I’ve used

    (I’ve used \Glsentrylong instead of \glsentrylong to capitalise the name in the glossary.) -

    An alternative approach is to set

    An alternative approach is to set \acronymentry to just the long form and redefine -

    +
     \renewcommand*{\acronymentry}[1]{\Glsentrylong{##1}}%  
     \renewcommand*{\GenericAcronymFields}{%  
        symbol={\protect\MakeTextUppercase{\the\glsshorttok}}}%
    -

    I’m going to use the first approach and set

    I’m going to use the first approach and set \GenericAcronymFields to do nothing:

    -
    +
     \renewcommand*{\GenericAcronymFields}{}%
    -

    -

    Finally, this style needs to switch off hyperlinks on first use to avoid nested +

    +

    Finally, this style needs to switch off hyperlinks on first use to avoid nested links:

    -
    +
     \glshyperfirstfalse
    -

    Putting this all together: +

    Putting this all together:

    -
    +
    \newacronymstyle{custom-fn}% new style name  
    {%  
      \ifglshaslong{\glslabel}{\glsgenacfmt}{\glsgenentryfmt}% @@ -17394,29 +17763,29 @@ links:  
         (\MakeTextUppercase{\glsentryshort{##1}})}%  
    }
    -

    -

    Now I need to specify that I want to use this new style: +

    +

    Now I need to specify that I want to use this new style:

    -
    +
    \setacronymstyle{custom-fn}
    -

    I also need to use a glossary style that suits this acronym style, for example

    I also need to use a glossary style that suits this acronym style, for example altlist:

    -
    +
    \setglossarystyle{altlist}
    -

    -

    Once the acronym style has been set, I can define my acronyms: +

    +

    Once the acronym style has been set, I can define my acronyms:

    -
    +
    \newacronym[description={set of tags for use in  
    developing hypertext documents}]{html}{html}{Hyper  
    Text Markup Language} @@ -17424,26 +17793,26 @@ class="cmss-10">altlistlayout of a document written in a markup language}]{css}  
    {css}{Cascading Style Sheet}
    -

    -

    The sample file

    +

    The sample file sample-custom-acronym.tex illustrates this example.

    -

    -

    ____________________________

    +

    +

    ____________________________

    -

    Example 23 (Italic and Upright Abbreviations) -

    Suppose I want to have some abbreviations in italic and some that just use the +

    Suppose I want to have some abbreviations in italic and some that just use the surrounding font. Hard-coding this into the ⟨short⟩ argument of \newacronym can cause complications. -

    This example uses

    This example uses \glsaddstoragekey to add an extra field that can be used to store the formatting declaration (such as \em).

    -
    +
    \glsaddstoragekey{font}{}{\entryfont}
    -

    This defines a new field/key called

    This defines a new field/key called font, which defaults to nothing if it’s not explicitly set. This also defines a command called \entryfont that’s analogous to \glsentrytext. A new style is then created to format abbreviations that access this field. -

    There are two ways to do this. The first is to create a style that doesn’t use

    There are two ways to do this. The first is to create a style that doesn’t use \glsgenacfmt but instead provides a modified version that doesn’t use \genacrfullformat need to be similarly adjusted. For exam

    -
    +
      \renewcommand*{\genacrfullformat}[2]{%  
       \glsentrylong{##1}##2\space  
       ({\entryfont{##1}\glsentryshort{##1}})%  
      }%
    -

    This will deal with commands like

    This will deal with commands like \gls but not commands like \acrshort -

    +
    \renewcommand*{\acronymfont}[1]{{\entryfont{\glslabel}#1}}%
    -

    So the new style can be defined as: +

    So the new style can be defined as:

    -
    +
    \newacronymstyle{long-font-short}  
    {%  
      \GlsUseAcrEntryDispStyle{long-short}% @@ -17541,23 +17910,23 @@ now:  
      \renewcommand*{\acronymentry}[1]{{\entryfont{##1}\glsentryshort{##1}}}%  
    }
    -

    Remember the style needs to be set before defining the entries: +

    Remember the style needs to be set before defining the entries:

    -
    +
    \setacronymstyle{long-font-short}
    -

    -

    The complete document is contained in the sample file

    +

    The complete document is contained in the sample file sample-font-abbr.tex.

    -

    -

    ____________________________

    -

    Some writers and publishing houses have started to drop full stops (periods) from upper +

    +

    ____________________________

    +

    Some writers and publishing houses have started to drop full stops (periods) from upper case initials but may still retain them for lower case abbreviations, while others may still use them for both upper and lower case. This can cause complications. Chapter 12 of (back slash space) in place of jus inter-word mid-sentence space and use \@ before the full stop to indicate the end of the sentence. -

    For example: +

    For example:

    -
    +
    I was awarded a B.Sc. and a Ph.D. (From the same place.)
    -

    is typeset as +

    is typeset as
    I was awarded a B.Sc. and a Ph.D. (From the same place.)
    The spacing is more noticeable with the typewriter font:

    -
    +
    \ttfamily  
    I was awarded a B.Sc. and a Ph.D. (From the same place.)
    -

    is typeset as +

    is typeset as
    I was awarded a B.Sc. and a Ph.D. (From the same place.)
    @@ -17608,11 +17977,11 @@ These can be corrected:

    -
    +
    I was awarded a B.Sc.\ and a Ph.D\@. (From the same place.)
    -

    -

    This situation is a bit problematic for

    +

    This situation is a bit problematic for glossaries. The full stops can form part of the ⟨short⟩ argument of \@ before the full stop. -

    The next example shows one way of achieving this. (Note that the supplemental +

    The next example shows one way of achieving this. (Note that the supplemental glossaries-extra package provides a much simpler way of doing this, which you may prefer to use.) -

    Example 24 (Abbreviations with Full Stops (Periods)) -

    As from version 4.16, there’s now a hook (

    As from version 4.16, there’s now a hook (\glspostlinkhook) that’s called at the very end of the amsgen documentation.) -

    It’s possible that I may also want acronyms or contractions in my document, so I need +

    It’s possible that I may also want acronyms or contractions in my document, so I need some way to differentiate between them. Here I’m going to use the same method as in example 4 where a new field is defined to indicate the type of abbreviation:

    -
    +
    \glsaddstoragekey{abbrtype}{word}{\abbrtype}  
    \newcommand*{\newabbr}[1][]{\newacronym[abbrtype=initials,#1]}
    -

    Now I just use

    Now I just use \newacronym for the acronyms, for example,

    -
    +
    \newacronym{laser}{laser}{light amplification by stimulated  
    emission of radiation}
    -

    and my new command

    and my new command \newabbr for initials, for example,

    -
    +
    \newabbr{eg}{e.g.}{exempli gratia}  
    \newabbr{ie}{i.e.}{id est}  
    \newabbr{bsc}{B.Sc.}{Bachelor of Science}  
    \newabbr{ba}{B.A.}{Bachelor of Arts}  
    \newabbr{agm}{A.G.M.}{annual general meeting}
    -

    Within

    Within \glspostlinkhook the entry’s label can be accessed using \glslabel and @@ -17699,7 +18068,7 @@ class="cmtt-10">abbrtype field set to “initials”. If it doesn’t, then nothing needs to happen, but if it does, a check is performed to see if the next character is a full stop. If it is, this signals the end of a sentence otherwise it’s mid-sentence. -

    Remember that internal commands within the document file (rather than in a class or +

    Remember that internal commands within the document file (rather than in a class or package) need to be placed between \makeatletter and \makeatother -

    + -

    In the event that a full stop is found

    In the event that a full stop is found \doendsentence is performed but it will be followed by the full stop, which needs to be discarded. Otherwise \doendword will be done but it won’t be @@ -17726,11 +18095,11 @@ are:

    -
    +
    \newcommand{\doendsentence}[1]{\spacefactor=10000{}}  
    \newcommand{\doendword}{\spacefactor=1000{}}
    -

    Now, I can just do

    Now, I can just do \gls{bsc} mid-sentence and \gls{phd}. at the end of the sentence. The terminating full stop will be discarded in the latter case, but it won’t be @@ -17738,7 +18107,7 @@ discarded in, say, \gls{laser}. as that doesn’t have the abbrtype field set to “initials”. -

    This also works on first use when the style is set to one of the ⟨

    This also works on first use when the style is set to one of the ⟨long⟩ (⟨short⟩) styles but it will fail with the ⟨first use flag and define a macro that can then be used in \glspostlinkhook. -

    The other thing to consider is what to do with plurals. One possibility is to check for +

    The other thing to consider is what to do with plurals. One possibility is to check for plural use within \doendsentence (using \glsifplural) and put the full stop back if the plural has been used. -

    The complete document is contained in the sample file

    The complete document is contained in the sample file ??.

    -

    -

    ____________________________

    -

    +

    +

    ____________________________

    +

    -

    Top

    13.2 Displaying the List of Acronyms

    -

    The list of acronyms is just like any other type of glossary and can be displayed on its own +

    The list of acronyms is just like any other type of glossary and can be displayed on its own using:

    [type=\acronymtype]
    -

    (If you use the

    (If you use the acronym package option you can also use

    @@ -17845,7 +18214,7 @@ href="#sec:pkgopts-acronym">§2.5 Acronym Options.) -

    Alternatively the list of acronyms can be displayed with all the other glossaries using: +

    Alternatively the list of acronyms can be displayed with all the other glossaries using:

    :
    \printglossaries
    -

    However, care must be taken to choose a glossary style that’s appropriate to your acronym +

    However, care must be taken to choose a glossary style that’s appropriate to your acronym style. Alternatively, you can define your own custom style (see §15.2 Defining your own glossary style for further details). -

    +

    -

    Top

    13.3 Upgrading From the glossary Package

    -

    Users of the obsolete

    Users of the obsolete glossary package may recall that the syntax used to define new acronyms has changed with the replacement acr-name⟩ when defining the acronym class="cmti-10">acr-name⟩. -

    In order to facilitate migrating from the old package to the new one, the

    In order to facilitate migrating from the old package to the new one, the glossaries package13.1 provides the command: -



    \oldacronym  long}{key-val list}

    -

    +

    This uses the same syntax as the glossary package’s method of defining acronyms. It is @@ -17967,7 +18336,7 @@ class="cmtt-10">\gls\Gls to change the settings. -

    Recall that, in general, LAT

    Recall that, in general, LATEX ignores spaces following command names consisting of alphabetical characters. This is also true for \xspace.13.2
    -

    +

    -

    The

    The glossaries package doesn’t load the xspace package since there are both advantages @@ -18006,14 +18375,14 @@ you can’t use the optional argument to insert text (you will have to expli \gls). -

    To illustrate this, suppose I define the acronym “abc” as follows: +

    To illustrate this, suppose I define the acronym “abc” as follows:

    -
    +
    \oldacronym{abc}{example acronym}{}
    -

    This will create the command

    This will create the command \abc and its starred version \abc*. Table 13.2 illustrates the @@ -18029,7 +18398,7 @@ optional argument from being recognised.

    -


    @@ -18095,11 +18464,11 @@ class="td11"> abc’s xyz
    -

    -

    +

    Top

    14. Unsetting and Resetting Entry Flags

    -

    When using the

    When using the \gls-like commands it is possible that you may want to use the value given by the text key, even though you haven’t used the glossary entry. The former can be achieved by one of the following commands: -



    \glsreset  \glsreset{label}

    -

    -


    +


    \glslocalreset  \glslocalreset{label}

    -

    +

    while the latter can be achieved by one of the following commands: -



    \glsunset  \glsunset{label}

    -

    -


    +


    \glslocalunset  \glslocalunset{label}

    -

    +

    You can also reset or unset all entries for a given glossary or list of glossaries using: -



    \glsresetall  \glsresetall[glossary list]

    -

    -


    +


    \glslocalresetall  \glslocalresetall[glossary list]

    -

    -


    +


    \glsunsetall  \glsunsetall[glossary list]

    -

    -


    +


    \glslocalunsetall  \glslocalunsetall[glossary list]

    -

    +

    where ⟨glossary list⟩ is a comma-separated list of glossary labels. If omitted, all defined glossaries are assumed (except for the ignored ones). For example, to reset all entries in the @@ -18184,13 +18553,13 @@ main glossary and the list of acronyms:

    -
    +
    \glsresetall[main,acronym]
    -

    -

    You can determine whether an entry’s

    +

    You can determine whether an entry’s first use flag is set using: -



    \ifglsused  true part}{false part}

    -

    +

    where ⟨label⟩ is the label of the required entry. If the entry has been used, ⟨true part⟩ will be done, otherwise ⟨false part⟩ will be done. -

    Be careful when using

    Be careful when using \gls-like commands within an environment or command argument that gets processed multiple times as it can cause unwanted side-effects when the first use displayed text is different from subsequent use.
    -

    -

    For example, the

    +

    For example, the frame environment in beamerfirst use flag will be unset on the first overlay and subsequent overlays will use the non-first use form. -

    Consider the following example: +

    Consider the following example:

    -
    +
    \documentclass{beamer}  
    \usepackage{glossaries}  
    \newacronym{svm}{SVM}{support vector machine} @@ -18240,22 +18609,22 @@ will use the non-first use form.  
    \end{frame}  
    \end{document}
    -

    -

    On the first overlay,

    +

    On the first overlay, \gls{svm} produces “support vector machine (SVM)” and then unsets the first use flag. When the second overlay is processed, \gls{svm} now produces “SVM”, which is unlikely to be the desired effect. I don’t know anyway around this and I can only offer two suggestions. -

    Firstly, unset all acronyms at the start of the document and explicitly use

    Firstly, unset all acronyms at the start of the document and explicitly use \acrfull when you want the full version to be displayed:

    -
    +
    \documentclass{beamer}  
    \usepackage{glossaries}  
    \newacronym{svm}{SVM}{support vector machine} @@ -18270,12 +18639,12 @@ you want the full version to be displayed:  
    \end{frame}  
    \end{document}
    -

    -

    Secondly, explicitly reset each acronym on first use: +

    +

    Secondly, explicitly reset each acronym on first use:

    -
    +
    \begin{frame}  
     \frametitle{Frame 1}  
     \begin{itemize} @@ -18284,7 +18653,7 @@ you want the full version to be displayed:  
     \end{itemize}  
    \end{frame}
    -

    These are non-optimal, but the

    These are non-optimal, but the beamer class is too complex for me to provide a programmatic solution. Other potentially problematic environments are some @@ -18297,7 +18666,7 @@ class="cmss-10">tabular itself) that process the contents in order to work out the column widths and then reprocess the contents to do the actual typesetting. -

    The

    The amsmath environments, such as alignalignglossaries package now checks for this.

    -

    Top

    14.1 Counting the Number of Times an Entry has been Used (First Use Flag Unset)

    -

    As from version 4.14, it’s now possible to keep track of how many times an entry is used. +

    As from version 4.14, it’s now possible to keep track of how many times an entry is used. That is, how many times the first use flag is unset. Note that the supplemental glossaries-extra package improves this function and also provides per-unit counting, which isn’t available with the glossaries package. -

    This function is disabled by default as it adds extra overhead to the document build time +

    This function is disabled by default as it adds extra overhead to the document build time and also switches \newglossaryentry (and therefore \newacronym) into a preamble-only command.
    -

    -

    To enable this function, use -


    +

    To enable this function, use +


    \glsenableentrycount  \glsenableentrycount

    -

    +

    before defining your entries. This adds two extra (internal) fields to entries: currcount and prevcount. -

    The

    The currcount field keeps track of how many times \glsunset is used within the document. A local unset (using \glsreset and \glslocalreset reset this field back to zero (where \glslocalreset performs a local change). -

    The

    The prevcount field stores the final value of the currcount field from the previous run. @@ -18361,8 +18730,8 @@ class="cmtt-10">.aux file at the beginning of the document environment. -

    You can access these fields using -


    You can access these fields using +


    \glsentrycurrcount  label}

    -

    +

    for the currcount field, and -



    \glsentryprevcount  \glsentryprevcount{label}

    -

    +

    for the prevcount field. These commands are only defined if you have used \glsenableentrycount. -

    For example: +

    For example:

    -
    +
    \documentclass{article}  
    \usepackage{glossaries}  
    \makeglossaries @@ -18405,7 +18774,7 @@ class="cmbx-10">.  
    Number of times apple has been used: \glsentrycurrcount{apple}.  
    \end{document}
    -

    On the first LAT

    On the first LATEX run, \glsentryprevcount{apple} produces 0. At the end of the document, \glsentryprevcount{apple} now produces� class="cmtt-10">currcount field for the apple entry at the end of the document on the previous run. -

    When you enable the entry count using

    When you enable the entry count using \glsenableentrycount, you also enable the following commands: -



    \cgls  label}[insert]

    -

    +

    (no case-change, singular) -



    \cglspl  label}[insert]

    -

    +

    (no case-change, plural) -



    \cGls  label}[insert]

    -

    +

    (first letter uppercase, singular), and -



    \cGlspl  label}[insert]

    -

    +

    (first letter uppercase, plural). These all have plus and starred variants like the analogous \gls, \glspl, \Gls and \Glspl commands. -

    If you don’t use

    If you don’t use \glsenableentrycount, these commands behave like \gls, \glspl, \cgls, \cglspl, \cGls or \cGlspl. -



    \cglsformat  label}{insert}

    -

    +

    This command is used by \cgls and defaults to

    @@ -18555,7 +18924,7 @@ class="cmtt-10">}⟨insert
    otherwise. -



    \cglsplformat  label}{insert}

    -

    +

    This command is used by \cglspl and defaults to

    @@ -18584,7 +18953,7 @@ class="cmtt-10">}⟨insert
    otherwise. -



    \cGlsformat  label}{insert}

    -

    +

    This command is used by \cGls and defaults to

    @@ -18615,7 +18984,7 @@ class="cmtt-10">}⟨insert
    otherwise. -



    \cGlsplformat  label}{insert}

    -

    +

    This command is used by \cGlspl and defaults to

    @@ -18644,7 +19013,7 @@ class="cmtt-10">}⟨insert
    otherwise. -

    This means that if the previous count for the given entry was 1, the entry won’t be +

    This means that if the previous count for the given entry was 1, the entry won’t be hyperlinked with the \cgls-like commands and they won’t add a line to the external glossary file. If you haven’t used any of the other commands that add information to glossary file (such @@ -18653,7 +19022,7 @@ class="cmtt-10">\glsadd or the \glstext-like commands) then the entry won’t appear in the glossary. -

    Remember that since these commands use

    Remember that since these commands use \glsentryprevcount you need to run LATEX twice to ensure they work correctly. The document build order is now (at least): @@ -18664,17 +19033,17 @@ class="cmtt-10">makeglossaries, (pdf)latex. -

    Example 25 (Don’t index entries that are only used once) -

    In this example, the abbreviations that have only been used once (on the previous run) +

    In this example, the abbreviations that have only been used once (on the previous run) only have their long form shown with \cgls.

    -
    +
    \documentclass{article}  
    \usepackage[colorlinks]{hyperref}  
    \usepackage[acronym]{glossaries} @@ -18695,7 +19064,7 @@ class="cmtt-10">\cgls.  
    \printglossaries  
    \end{document}
    -

    After a complete document build (

    After a complete document build (latex, latex, makeglossaries,

    -

    -

    ____________________________

    -

    Remember that if you don’t like typing

    +

    ____________________________

    +

    Remember that if you don’t like typing \cgls you can create a synonym. For example

    -
    +
    \let\ac\cgls
    -

    +

    -

    -

    +

    Top

    15. Glossary Styles

    -

    Glossaries vary from lists that simply contain a symbol with a terse description to lists of +

    Glossaries vary from lists that simply contain a symbol with a terse description to lists of terms or phrases with lengthy descriptions. Some glossaries may have terms with associated symbols. Some may have hierarchical entries. There is therefore no single style that fits every type of glossary. The Defining your own glossary style

    The glossary style can be set using the

    The glossary style can be set using the style key in the optional argument to \printglossary2 and 3) or using the command: -



    \setglossarystyle  \setglossarystyle{style-name}

    -

    +

    (before the glossary is displayed). -

    Some of the predefined glossary styles may also be set using the

    Some of the predefined glossary styles may also be set using the style package option, it depends if the package in which they are defined is automatically loaded by the glossaries package. -

    You can use the lorum ipsum dummy entries provided in the accompanying +

    You can use the lorum ipsum dummy entries provided in the accompanying example-glossaries-*.tex files (described in §1.2 Dummy Entries for Testing) to test the different styles.

    -

    Top

    15.1 Predefined Styles

    -

    The predefined styles can accommodate numbered level 0 (main) and level 1 entries. See the +

    The predefined styles can accommodate numbered level 0 (main) and level 1 entries. See the package options entrycounter, table 15.1. You can view samples of all the predefined styles at http://www.dickimaw-books.com/gallery/glossaries-styles/. -

    Note that the group styles (such as

    Note that the group styles (such as listgroup) will have unexpected results if used with the nogroupskip package option to prevent odd vertical gaps appearing.
    -

    -

    The group title is obtained using

    +

    The group title is obtained using \glsgetgrouptitle{label}, which is described in Defining your own glossary style


    @@ -19006,7 +19375,7 @@ class="td11">

    -

    The tabular-like styles that allow multi-line descriptions and page lists use the length +

    The tabular-like styles that allow multi-line descriptions and page lists use the length \glsdescwidth \newline instead of \\. -

    Note that if you use the

    Note that if you use the style key in the optional argument to \printnoidxglossary -

    +
    \renewcommand*{\glsgroupskip}{}  
    \printglossary[style=long]
    -

    then the new definition of

    then the new definition of \glsgroupskip will not have an affect for this glossary, as -

    +
    \renewcommand*{\glsgroupskip}{}  
    \setglossarystyle{long}
    -

    will reset

    will reset \glsgroupskip back to its default definition for the named glossary style (long -

    +
    \setglossarystyle{long}  
    \renewcommand*{\glsgroupskip}{}
    -

    As from version 3.03, you can now use the package option

    As from version 3.03, you can now use the package option nogroupskip to suppress the gap between groups for the default styles instead of redefining \glsgroupskip. -

    All the styles except for the three- and four-column styles and the

    All the styles except for the three- and four-column styles and the listdotted style use the command -



    \glspostdescription  \glspostdescription

    -

    +

    after the description. This simply displays a full stop by default. To eliminate this full stop (or replace it with something else, say, a comma) you will need to redefine \glspostdescription before the glossary is displayed. Alt a given entry by placing \nopostdesc in the entry’s description. -

    As from version 3.03 you can now use the package option

    As from version 3.03 you can now use the package option nopostdot to suppress this full stop. This is the better option if you want to use the glossaries-extra package.

    -

    Top

    15.1.1 List Styles

    -

    The styles described in this section are all defined in the package

    The styles described in this section are all defined in the package glossary-list. Since they all use the EX to ensure the group information is up to date. In the navigation line, each group is separated by -



    \glshypernavsep  \glshypernavsep

    -

    +

    which defaults to a vertical bar with a space on either side. For example, to simply have a space separating each group, do:

    -
    +
    \renewcommand*{\glshypernavsep}{\space}
    -

    -

    Note that the hyper-navigation line is now (as from version 1.14) set inside the optional +

    +

    Note that the hyper-navigation line is now (as from version 1.14) set inside the optional argument to \item instead of after it to prevent a spurious space at the start. This can cause a problem if the navigation line is too long. As from v4.22, if you need to adjust this, you can redefine -



    \glslistnavigationitem  \glslistnavigationitem{navigation line}

    -

    +

    The default definition is \item[navigation line] but may be redefined independently of

    -
    +
    \renewcommand*{\glslistnavigationitem}[1]{\item \textbf{#1}}
    -

    -

    You may prefer to use the tree-like styles, such as

    +

    You may prefer to use the tree-like styles, such as treehypergroup instead.

    @@ -19283,12 +19652,12 @@ class="cmtt-10">\item[], followed by the name followed by a href="#glo:numberlist">number list and the symbol. The length -



    \glslistdottedwidth  \glslistdottedwidth

    -

    +

    governs where the description should start. This is a flat style, so child entries are formatted in the same way as the parent entries.

    @@ -19301,14 +19670,14 @@ class="cmss-10">listdottedlistdotted. -

    +

    -

    Top

    15.1.2 Longtable Styles

    -

    The styles described in this section are all defined in the package

    The styles described in this section are all defined in the package glossary-long. Since they all use the altlong4colheaderborderlong4colheaderborder but allows multi-line descriptions and page lists. -

    +

    -

    Top

    15.1.3 Longtable Styles (Ragged Right)

    -

    The styles described in this section are all defined in the package

    The styles described in this section are all defined in the package glossary-longragged. These styles are analogous to those defined in glossary-longragged -

    +
    \usepackage{glossaries}  
    \usepackage{glossary-longragged}
    -

    Note that you can’t set these styles using the

    Note that you can’t set these styles using the style package option since the styles aren’t defined until after the altlongragged4colheaderborderaltlongragged4colheader but has horizontal and vertical lines around it. -

    +

    -

    Top

    15.1.4 Longtable Styles (booktabs)

    -

    The styles described in this section are all defined in the package

    The styles described in this section are all defined in the package glossary-longbooktabs. -

    Since these styles all use the

    Since these styles all use the longtable environment, they are governed by the same @@ -19724,16 +20093,16 @@ class="cmss-10">glossary-longbooktabs -

    +
    \usepackage{glossaries}  
    \usepackage{glossary-longbooktabs}
    -

    Note that you can’t set these styles using the

    Note that you can’t set these styles using the style package option since the styles aren’t defined until after the glossaries package has been loaded. -

    These styles are similar to the “header” styles in the

    These styles are similar to the “header” styles in the glossary-long and glossary-ragged\printglossary. (The nogroupskip package option is checked by these styles.) -

    Alternatively, you can restore the original

    Alternatively, you can restore the original longtable behaviour with: -



    \glsrestoreLToutput  \glsrestoreLToutput

    -

    +

    For more information about the patch, see the documented code (glossaries-code.pdf).

    @@ -19840,12 +20209,12 @@ class="cmss-10">altlongragged4colheader style but adds rules as above.
    -

    +

    -

    Top

    15.1.5 Supertabular Styles

    -

    The styles described in this section are all defined in the package

    The styles described in this section are all defined in the package glossary-super. Since they all use the super4colheaderborder but allows multi-line descriptions and page lists. -

    +

    -

    Top

    15.1.6 Supertabular Styles (Ragged Right)

    -

    The styles described in this section are all defined in the package

    The styles described in this section are all defined in the package glossary-superragged. These styles are analogous to those defined in glossary-superragged -

    +
    \usepackage{glossaries}  
    \usepackage{glossary-superragged}
    -

    Note that you can’t set these styles using the

    Note that you can’t set these styles using the style package option since the styles aren’t defined until after the altsuperragged4colheaderborderaltsuperragged4colheader but has horizontal and vertical lines around it. -

    +

    -

    Top

    15.1.7 Tree-Like Styles

    -

    The styles described in this section are all defined in the package

    The styles described in this section are all defined in the package glossary-tree. These styles are designed for hierarchical glossaries but can also be used with glossaries that don’t have @@ -20242,14 +20611,14 @@ class="cmss-10">notreenostyles package options. These styles all format the entry name using: -



    \glstreenamefmt  \glstreenamefmt{name}

    -

    +

    This defaults to \textbf{name\glstreenamefont may be counteracted by another font chan class="cmtt-10">\glsnamefont (or in \acronymfont). The tree-like styles that also display the header use -



    \glstreegroupheaderfmt  \glstreegroupheaderfmt{text}

    -

    +

    to format the heading. This defaults to \glstreenamefmt{textindexhypergroup), format the navigation line using -



    \glstreenavigationfmt  text}

    -

    +

    which defaults to \glstreenamefmt{textalttreetree style except that the indentation for each level is determined by the width of the text specified by -



    \glssetwidest  level]{text}

    -

    +

    The optional argument ⟨level⟩ indicates the level, where 0 indicates the top-most level, 1 indicates the first level sub-entries, etc. If \glssetwidest hasn’t been used for a given sub-level, the level 0 widest text is used instead. If ⟨level⟩ is omitted, 0 is assumed. -

    As from v4.22, the

    As from v4.22, the glossary-tree package also provides -



    \glsfindwidesttoplevelname  \glsfindwidesttoplevelname[glossary list]

    -

    +

    This iterates over all parentless entries in the given glossary lists and determines the widest entry. If the optional argument is omitted, all glossaries are assumed (as per \forallglossaries). -

    For example, to have the same name width for all glossaries: +

    For example, to have the same name width for all glossaries:

    -
    +
    \glsfindwidesttoplevelname  
    \setglossarystyle{alttree}  
    \printglossaries
    -

    Alternatively, to compute the widest entry for each glossary before it’s displayed: +

    Alternatively, to compute the widest entry for each glossary before it’s displayed:

    -
    +
    \renewcommand{\glossarypreamble}{%  
      \glsfindwidesttoplevelname[\currentglossary]}  
    \setglossarystyle{alttree}  
    \printglossaries
    -

    -

    These commands only affects the

    +

    These commands only affects the alttree styles, including those listed below and the ones in the glossary-mcols package. If you forget to set the widest entry name, the description will overwrite the name.
    -

    -

    For each level, the name is placed to the left of the paragraph block containing the +

    +

    For each level, the name is placed to the left of the paragraph block containing the symbol (optional) and the description. If the symbol is present, it is placed in parentheses before the description. -

    The name is placed inside a left-aligned

    The name is placed inside a left-aligned \makebox. As from v4.19, this can now be adjusted by redefining -



    \glstreenamebox  width}{text}

    -

    +

    where ⟨width⟩ is the width of the box and ⟨text⟩ is the contents of the box. For example, to @@ -20514,12 +20883,12 @@ class="cmti-10">text⟩ is the contents of the box. For example, to

    -
    +
    \renewcommand*{\glstreenamebox}[2]{%  
      \makebox[#1][r]{#2}%  
    }
    -

    +

    alttreegroup
    listhypergroup, described above.
    -

    +

    -

    Top

    15.1.8 Multicols Style

    -

    The

    The glossary-mcols package provides tree-like styles that are in the multicols\glstreenavigationfmt are all used by the corresponding glossary-mcols styles. -

    Note that

    Note that glossary-mcols is not loaded by glossaries. If you want to use any of the multicol @@ -20594,29 +20963,29 @@ class="cmtt-10">\usepackage and set the required glossary style using \setglossarystyle.
    -

    -

    The default number of columns is 2, but can be changed by redefining -


    +

    The default number of columns is 2, but can be changed by redefining +


    \glsmcols  \glsmcols

    -

    +

    to the required number. For example, for a three column glossary:

    -
    +
    \usepackage{glossary-mcols}  
    \renewcommand*{\glsmcols}{3}  
    \setglossarystyle{mcolindex}
    -

    +

    -


    @@ -20742,7 +21111,7 @@ class="cmss-10">alttreehypergroup
    -

    The styles with a navigation line, such as

    The styles with a navigation line, such as mcoltreehypergroup, now have a variant (as from v4.22) with “hypergroup” replaced with “spannav” in the style name. The original @@ -20753,10 +21122,10 @@ class="cmss-10">multicols environment so that it spans across all the columns.

    -

    Top

    15.1.9 In-Line Style

    -

    This section covers the

    This section covers the glossary-inline package that supplies the inlinenumber list. -

    You will most likely need to redefine

    You will most likely need to redefine \glossarysection with this style. For example, suppose you are required to have your glossaries and list of acronyms in a footnote, you can @@ -20773,13 +21142,13 @@ do:

    -
    +
     \usepackage{glossary-inline}  
     \renewcommand*{\glossarysection}[2][]{\textbf{#1}: }  
     \setglossarystyle{inline}
    -

    -

    Note that you need to include

    +

    Note that you need to include glossary-inline with \usepackage as it’s not automatically @@ -20788,55 +21157,55 @@ class="cmss-10">glossaries package and then set the style using \setglossarystyle.
    -

    -

    Where you need to include your glossaries as a footnote you can do: +

    +

    Where you need to include your glossaries as a footnote you can do:

    -
    +
    \footnote{\printglossaries}
    -

    -

    The

    +

    The inline style is governed by the following: -



    \glsinlineseparator  \glsinlineseparator

    -

    +

    This defaults to “; ” and is used between main (i.e. level 0) entries. -



    \glsinlinesubseparator  \glsinlinesubseparator

    -

    +

    This defaults to “, ” and is used between sub-entries. -



    \glsinlineparentchildseparator  \glsinlineparentchildseparator

    -

    +

    This defaults to “: ” and is used between a parent main entry and its first sub-entry. -



    \glspostinline  \glspostinline

    -

    +

    This defaults to “; ” and is used at the end of the glossary. -



    \glsinlinenameformat  label}{name}

    -

    +

    This is used to format the entry name and defaults to \glstarget{label -

    +
    \renewcommand*{\glsinlinenameformat}[2]{\glstarget{#1}{\textsc{#2}}}
    -

    Sub-entry names are formatted according to -


    Sub-entry names are formatted according to +


    \glsinlinesubnameformat  label}{name}

    -

    +

    This defaults to \glstarget{label}{} so the sub-entry name is ignored. -

    If the description has been suppressed (according to

    If the description has been suppressed (according to \ifglsdescsuppressed) then -



    \glsinlineemptydescformat  }{number list}

    -

    +

    (which defaults to nothing) is used, otherwise the description is formatted according to -



    \glsinlinedescformat  }{number list}

    -

    +

    This defaults to just \spacedescription⟩ so the symbol and location list are ignored. If the @@ -20917,16 +21286,16 @@ description is missing (according to \ifglshasdesc), then \glsinlineemptydescformat is used instead. -

    For example, if you want a colon between the name and the description: +

    For example, if you want a colon between the name and the description:

    -
    +
    \renewcommand*{\glsinlinedescformat}[3]{: #1}
    -

    -

    The sub-entry description is formatted according to: -


    +

    The sub-entry description is formatted according to: +


    \glsinlinesubdescformat  number list}

    -

    +

    This defaults to just ⟨description⟩. -

    +

    -

    Top

    15.2 Defining your own glossary style

    -

    If the predefined styles don’t fit your requirements, you can define your own style +

    If the predefined styles don’t fit your requirements, you can define your own style using: -



    \newglossarystyle  name}{definitions}

    -

    +

    where ⟨name⟩ is the name of the new glossary style (to be used in \setglossarystyle). The second argument ⟨definitions⟩ needs to redefine all of the following: -



    theglossary  theglossary

    -

    +

    This environment defines how the main body of the glossary should be typeset. Note that this does not include the section heading, the glossary preamble (defined by \glossarypreambledescription environment. -



    \glossaryheader  \glossaryheader

    -

    +

    This macro indicates what to do at the start of the main body of the glossary. Note that this is not the same as \glossarypreamblelongheader glossary style redefines \glossaryheader to do a header row. -



    \glsgroupheading  \glsgroupheading{label}

    -

    +

    This macro indicates what to do at the start of each logical block within the main body of the glossary. If you use xindy

    Note that the argument to

    Note that the argument to \glsgroupheading is a label not the group title. The group title can be obtained via -



    \glsgetgrouptitle  \glsgetgrouptitle{label}

    -

    +

    This obtains the title as follows: if ⟨label⟩ consists of a single non-active character or ⟨label⟩ is @@ -21081,8 +21450,8 @@ to just ⟨label⟩. You can redefine \glsgetgrouptitle if this is unsuitable for your document. -

    A navigation hypertarget can be created using -


    A navigation hypertarget can be created using +


    \glsnavhypertarget  label}{text}

    -

    +

    This typically requires \glossaryheader to be redefined to use -



    \glsnavigation  \glsnavigation

    -

    +

    which displays the navigation line. -

    For further details about

    For further details about \glsnavhypertarget, see the documented code (glossaries-code.pdf). -

    Most of the predefined glossary styles redefine

    Most of the predefined glossary styles redefine \glsgroupheading to simply ignore its argument. The listhypergroup\glsgroupheading as follows:

    -
    +
    \renewcommand*{\glsgroupheading}[1]{%  
    \item[\glsnavhypertarget{##1}{\glsgetgrouptitle{##1}}]}
    -

    See also

    See also \glsgroupskip below. (Note that command definitions within \newglossarystyle must use ##1 instead of #1 etc.) -



    \glsgroupskip  \glsgroupskip

    -

    +

    This macro determines what to do after one logical group but before the header for the next logical group. The list\indexspace, whereas the tabular-like styles redefine \glsgroupskip to produce a blank row. -

    As from version 3.03, the package option

    As from version 3.03, the package option nogroupskip can be used to suppress this default gap for the predefined styles. -



    \glossentry  label}{number list}

    -

    +

    This macro indicates what to do for each top-level (level 0) glossary entry. The entry label is given by ⟨label⟩ and the associated §9 Using Glossary Terms Without Links for further details.) You can also use the following commands: -



    \glsentryitem  \glsentryitem{label}

    -

    +

    This macro will increment and display the associated counter for the main (level 0) entries if the entrycounter\glossentry before \glstarget. The format of the counter is controlled by the macro -



    \glsentrycounterlabel  \glsentrycounterlabel

    -

    -

    Each time you use a glossary entry it creates a hyperlink (if hyperlinks are enabled) to the +

    +

    Each time you use a glossary entry it creates a hyperlink (if hyperlinks are enabled) to the relevant line in the glossary. Your new glossary style must therefore redefine \glossentry to set the appropriate target. This is done using -



    \glstarget  label}{text}

    -

    +

    where ⟨label⟩ is the entry’s label. Note that you don’t need to worry about whether the hyperref\glstarget won’t create a target if \hypertarget hasn’t been defined. -

    For example, the

    For example, the list style defines \glossentry as follows:

    -
    +
      \renewcommand*{\glossentry}[2]{%  
        \item[\glsentryitem{##1}%  
              \glstarget{##1}{\glossentryname{##1}}]  
           \glossentrydesc{##1}\glspostdescription\space ##2}
    -

    -

    Note also that ⟨

    +

    Note also that ⟨number list⟩ will always be of the form -



    \glossaryentrynumbers{{number(s)}}

    -

    +

    where ⟨number(s)⟩ may contain \delimNnonumberlist package option. -



    \subglossentry  label}{number list}

    -

    +

    This is used to display sub-entries. The first argument, ⟨level⟩, indicates the sub-entry level. This must be an integer from 1 (first sub-level) onwards. The remaining arguments are analogous to those for \glossentry described above. -



    \glssubentryitem  \glssubentryitem{label}

    -

    +

    This macro will increment and display the associated counter for the level 1 entries if the subentrycounter\subglossentry before \glstarget. The format of the counter is controlled by the macro -



    \glssubentrycounterlabel  \glssubentrycounterlabel

    -

    -

    Note that

    +

    Note that \printglossary (which \printglossaries calls) sets -



    \currentglossary  \currentglossary

    -

    +

    to the current glossary label, so it’s possible to create a glossary style that varies according to the glossary type. -

    For further details of these commands, see “Displaying the glossary” in the documented +

    For further details of these commands, see “Displaying the glossary” in the documented code (glossaries-code.pdf). -

    Example 26 (Creating a completely new style) -

    If you want a completely new style, you will need to redefine all of the commands and the +

    If you want a completely new style, you will need to redefine all of the commands and the environment listed above. -

    For example, suppose you want each entry to start with a bullet point. This +

    For example, suppose you want each entry to start with a bullet point. This means that the glossary should be placed in the itemize -

    +
     \newglossarystyle{mylist}{%  
     % put the glossary in the itemize environment:  
     \renewenvironment{theglossary}% @@ -21427,7 +21796,7 @@ follows:  
       \glossentry{##2}{##3}}%  
     }
    -

    Note that this style creates a flat glossary, where sub-entries are displayed in exactly the +

    Note that this style creates a flat glossary, where sub-entries are displayed in exactly the same way as the top level entries. It also hasn’t used \glsentryitem or counterwithinsubentrycounter package options. -

    Variations:

    +

    Variations:

    • You might want the entry name to be capitalised, in which case use §16 href="#sec:utilities">Utilities): -
      +
       \renewcommand*{\glossentry}[2]{%  
       \item % bullet point  
       \glstarget{##1}{\glossentryname{##1}}% the entry name @@ -21473,20 +21842,20 @@ href="#sec:utilities">Utilities):  
       \space [##2]% the number list in square brackets  
       }%
      -

    +

    -

    -

    ____________________________

    +

    +

    ____________________________

    -

    Example 27 (Creating a new glossary style based on an existing style) -

    If you want to define a new style that is a slightly modified version of an existing style, +

    If you want to define a new style that is a slightly modified version of an existing style, you can use \setglossarystyle within the second argument of -

    +
    \newglossarystyle{mylist}{%  
    \setglossarystyle{list}% base this style on the list style  
    \renewcommand{\glsgroupskip}{}% make nothing happen  
                                  % between groups  
    }
    -

    (In this case, you can actually achieve the same effect using the

    (In this case, you can actually achieve the same effect using the list style in combination with the package option nogroupskip.)

    -

    -

    ____________________________

    +

    +

    ____________________________

    -

    Example 28 (Example: creating a glossary style that uses the user1user6 keys) -

    Suppose each entry not only has an associated symbol, but also units (stored in

    Suppose each entry not only has an associated symbol, but also units (stored in user1) and dimension (stored in longtable -

    -

    -

    +

    Top

    16. Utilities

    -

    This section describes some utility commands. Additional commands can be found in the +

    This section describes some utility commands. Additional commands can be found in the documented code (glossaries-code.pdf).

    -

    Top

    16.1 Loops

    -

    Some of the commands described here take a comma-separated list as an argument. As with +

    Some of the commands described here take a comma-separated list as an argument. As with LATEX’s \@for command, make sure your list doesn’t have any unwanted spaces in it as @@ -21613,8 +21982,8 @@ href="http://www.dickimaw-books.com/latex/admin/html/docsvlist.shtml#spacesinlis class="cmsy-10">§2.7.2 of “LATEX for Administrative Work”.)
    -

    -


    +


    \forallglossaries  cs}{body}

    -

    +

    This iterates through ⟨glossary list⟩, a comma-separated list of glossary labels (as supplied when the glossary was defined). At each iteration ⟨body⟩ is performed. If ⟨glossary list⟩ is omitted, the default is to iterate over all glossaries (except the ignored ones). -



    \forallacronyms  cs}{body}

    -

    +

    This is like \forallglossaries but only iterates over the lists of acronyms (that have previously been declared using acronymlists\forallglossaries. -



    \forglsentries  cs}{body}

    -

    +

    This iterates through all entries in the glossary given by ⟨glossary label⟩. At each iteration ⟨cs⟩ @@ -21677,7 +22046,7 @@ class="cmti-10">glossary label⟩ is omitted, \glsdefaulttype (usually the main glossary) is used. -



    \forallglsentries  cs}{body}

    -

    +

    This is like \forglsentries but for each glossary in ⟨glossary list⟩ (a comma-separated list of @@ -21703,12 +22072,12 @@ class="cmti-10">cs⟩} within ⟨body⟩.) -

    +

    -

    Top

    16.2 Conditionals

    -



    \ifglossaryexists  true part⟩⟨false part

    -

    +

    This checks if the glossary given by ⟨label⟩ exists. If it does ⟨true part⟩ is performed, otherwise ⟨false part⟩. -



    \ifglsentryexists  \ifglsentryexistslabel⟩⟨true part⟩⟨false part

    -

    +

    This checks if the glossary entry given by ⟨label⟩ exists. If it does ⟨true part⟩ is performed, @@ -21750,7 +22119,7 @@ href="#sec:techissues">§4.10.1 Technical Issues for further details.) -



    \glsdoifexists  label}{code}

    -

    +

    Does ⟨code⟩ if the entry given by ⟨label⟩ exists. If it doesn’t exist, an error is generated. (This command uses \ifglsentryexists.) -



    \glsdoifnoexists  label}{code}

    -

    +

    Does the reverse of \glsdoifexists. (This command uses \ifglsentryexists.) -



    \glsdoifexistsorwarn  label}{code}

    -

    +

    As \glsdoifexists but issues a warning rather than an error if the entry doesn’t exist. -



    \glsdoifexistsordo  code}{else code}

    -

    +

    Does ⟨code⟩ if the entry given by ⟨label⟩ exists otherwise generate an error and do ⟨else code⟩. -



    \glsdoifnoexistsordo  code}{else code}

    -

    +

    Does ⟨code⟩ if the entry given by ⟨label⟩ doesn’t exist otherwise generate an error and do ⟨else code⟩. -



    \ifglsused  \ifglsusedlabel⟩⟨true part⟩⟨false part

    -

    +

    See §14 Unsetting and Resetting Entry Flags. -



    \ifglshaschildren  \ifglshaschildrenlabel⟩⟨true part⟩⟨false part

    -

    +

    This checks if the glossary entry given by ⟨label⟩ has any sub-entries. If it does, ⟨true part⟩ is performed, otherwise ⟨false part⟩. -



    \ifglshasparent  \ifglshasparentlabel⟩⟨true part⟩⟨false part

    -

    +

    This checks if the glossary entry given by ⟨label⟩ has a parent entry. If it does, ⟨true part⟩ is performed, otherwise ⟨false part⟩. -



    \ifglshassymbol  true part}{false part}

    -

    +

    This checks if the glossary entry given by ⟨label⟩ has had the symbolsymboltrue part⟩ is performed, otherwise ⟨false part⟩. -



    \ifglshaslong  false part}

    -

    +

    This checks if the glossary entry given by ⟨label⟩ has had the longfalse part⟩. This should be true for any entry tha class="cmtt-10">\newacronym. There is no check for the existence of ⟨label⟩. -



    \ifglshasshort  true part}{false part}

    -

    +

    This checks if the glossary entry given by ⟨label⟩ has had the shortfalse part⟩. This should be true for any entry tha class="cmtt-10">\newacronym. There is no check for the existence of ⟨label⟩. -



    \ifglshasdesc  true part}{false part}

    -

    +

    This checks if the description field is non-empty for the entry given by ⟨label⟩. If it has, ⟨true part⟩ is performed, otherwise ⟨false part⟩. Compare with: -



    \ifglsdescsuppressed  }{false part}

    -

    +

    This checks if the description field has been set to just true part⟩ is performed, otherwise ⟨false part⟩. There is no check for the existence of ⟨label⟩. -

    For all other fields you can use: -


    For all other fields you can use: +


    \ifglshasfield  }{false part}

    -

    +

    This tests the value of the field given by ⟨field⟩ for the entry identified by ⟨label⟩. If the value is @@ -22006,14 +22375,14 @@ class="cmti-10">false part⟩ is performed and a warning is issued. Unlike the above commands, such as \ifglshasshort, an error occurs if the entry is undefined. -

    As from version 4.23, within ⟨

    As from version 4.23, within ⟨true part⟩ you can use -



    \glscurrentfieldvalue  \glscurrentfieldvalue

    -

    +

    to access the field value. This command is initially defined to nothing but has no relevance outside ⟨true part⟩. This saves re-accessing the field if the test is true. For @@ -22021,16 +22390,16 @@ example:

    -
    +
    \ifglshasfield{useri}{sample}{, \glscurrentfieldvalue}{}
    -

    will insert a comma, space and the field value if the

    will insert a comma, space and the field value if the user1 key has been set for the entry whose label is sample. -

    You can test if the value of the field is equal to a given string using: -


    You can test if the value of the field is equal to a given string using: +


    \ifglsfieldeq  }{false}

    -

    +

    In this case the ⟨field⟩ must be the field name not the key (see table 4.1). If the @@ -22058,12 +22427,12 @@ class="cmtt-10">\ifcsstring to perform the comparison. The string is not expanded during the test. -

    The result may vary depending on whether or not expansion is on for the given field +

    The result may vary depending on whether or not expansion is on for the given field (when the entry was defined). For example:

    -
    +
    \documentclass{article}  
    \usepackage{glossaries}  
    \newcommand*{\foo}{FOO} @@ -22076,25 +22445,25 @@ class="cmti-10">test.  
    \ifglsfieldeq{sample2}{useri}{FOO}{TRUE}{FALSE}.  
    \end{document}
    -

    This will produce “TRUE” in both cases since expansion is on, so

    This will produce “TRUE” in both cases since expansion is on, so \foo was expanded to “FOO” when sample2 was defined. If the tests are changed to:

    -
    +
    \ifglsfieldeq{sample1}{useri}{\foo}{TRUE}{FALSE}.  
    \ifglsfieldeq{sample2}{useri}{\foo}{TRUE}{FALSE}.
    -

    then this will produce “FALSE” in both cases. Now suppose expansion is switched off for the +

    then this will produce “FALSE” in both cases. Now suppose expansion is switched off for the user1 key:

    -
    +
    \documentclass{article}  
    \usepackage{glossaries}  
    \newcommand*{\foo}{FOO} @@ -22108,14 +22477,14 @@ class="cmss-10">user1\ifglsfieldeq{sample2}{useri}{FOO}{TRUE}{FALSE}.  
    \end{document}
    -

    This now produces “TRUE” for the first case (comparing “FOO” with “FOO”) and +

    This now produces “TRUE” for the first case (comparing “FOO” with “FOO”) and “FALSE” for the second case (comparing “\foo” with “FOO”). -

    The reverse happens in the following: +

    The reverse happens in the following:

    -
    +
    \documentclass{article}  
    \usepackage{glossaries}  
    \newcommand*{\foo}{FOO} @@ -22129,14 +22498,14 @@ class="cmtt-10">\foo” with “FOO”).  
    \ifglsfieldeq{sample2}{useri}{\foo}{TRUE}{FALSE}.  
    \end{document}
    -

    This now produces “FALSE” for the first case (comparing “FOO” with “

    This now produces “FALSE” for the first case (comparing “FOO” with “\foo”) and “TRUE” for the second case (comparing “\foo” with “\foo”). -

    You can test if the value of a field is equal to the replacement text of a command +

    You can test if the value of a field is equal to the replacement text of a command using: -



    \ifglsfielddefeq  }{false}

    -

    +

    This internally uses etoolbox’s \ifdefstrequal command to perform the comparison. The argument ⟨command⟩ must be a macro. -

    For example: +

    For example:

    -
    +
    \documentclass{article}  
    \usepackage{glossaries}  
    \newcommand*{\foo}{FOO} @@ -22177,14 +22546,14 @@ class="cmti-10">command⟩ must be a macro.  
    \ifglsfielddefeq{sample2}{useri}{\foo}{TRUE}{FALSE}.  
    \end{document}
    -

    Here, the first case produces “TRUE” since the value of the

    Here, the first case produces “TRUE” since the value of the useri field (“FOO”) is the same as the replacement text (definition) of \foo (“FOO”). We have the result “FOO” is equal to “FOO”. -

    The second case produces “FALSE” since the value of the

    The second case produces “FALSE” since the value of the useri field (“\foo”) is not the same as the replacement text (definition) of useri field. We have the result “\foo” is not equal to “FOO”. -

    If we add: +

    If we add:

    -
    +
    \newcommand{\FOO}{\foo}  
    \ifglsfielddefeq{sample2}{useri}{\FOO}{TRUE}{FALSE}.
    -

    we now get “TRUE” since the value of the

    we now get “TRUE” since the value of the useri field (“\foo”) is the same as the replacement text (definition) of \foo”). We have the result “\foo” is equal to “\foo”. -

    There is a similar command that requires the control sequence name (without the leading +

    There is a similar command that requires the control sequence name (without the leading backslash) instead of the actual control sequence: -



    \ifglsfieldcseq  }{false}

    -

    +

    This internally uses etoolbox’s \ifcsstrequal command instead of \ifdefstrequal. -

    +

    -

    Top

    16.3 Fetching and Updating the Value of a Field

    -

    You can fetch the value of a given field and store it in a control sequence using: -


    You can fetch the value of a given field and store it in a control sequence using: +


    \glsfieldfetch  field}{cs}

    -

    +

    where ⟨label⟩ is the label identifying the glossary entry, ⟨field⟩ is the field label (see @@ -22265,7 +22634,7 @@ that field in the argument of \newglossaryentry (or the optional argument of \newacronym). -

    You can change the value of a given field using one of the following commands. Note that +

    You can change the value of a given field using one of the following commands. Note that these commands only change the value of the given field. They have no affect on any related field. For example, if you change the value of the textplural, first or any other related key. -

    In all the four related commands below, ⟨

    In all the four related commands below, ⟨label⟩ and ⟨field⟩ are as above and ⟨definition⟩ is the new value of the field. -



    \glsfielddef  field}{definition}

    -

    +

    This uses \def to change the value of the field (so it will be localised by any grouping). -



    \glsfieldedef  field}{definition}

    -

    +

    This uses \edef to change the value of the field (so it will be localised by any grouping). Any fragile commands contained in the ⟨definition⟩ must be protected. -



    \glsfieldgdef  field}{definition}

    -

    +

    This uses \gdef to change the value of the field. -



    \glsfieldxdef  field}{definition}

    -

    +

    This uses \xdef to change the value of the field. Any fragile commands contained in the ⟨definition⟩ must be protected.

    -

    -

    +

    Top

    17. Prefixes or Determiners

    -

    The

    The glossaries-prefix package that comes with the glossaries package provides additional @@ -22360,7 +22729,7 @@ keys that can be used as prefixes. For example, if you want to specify determine class="cmss-10">glossaries-prefix package automatically loads the glossaries package and has the same package options. -

    The extra keys for

    The extra keys for \newglossaryentry are as follows:

    @@ -22399,20 +22768,20 @@ class="cmss-10">prefixplural key.
    -

    Example 29 (Defining Determiners) -

    Here’s the start of my example document: +

    Here’s the start of my example document:

    -
    +
    documentclass{article}  
    \usepackage[colorlinks]{hyperref}  
    \usepackage[toc,acronym]{glossaries-prefix}
    -

    Note that I’ve simply replaced

    Note that I’ve simply replaced glossaries from previous sample documents with glossaries-prefix. Now for a sample definition17.1

    -
    +
    \newglossaryentry{sample}{name={sample},%  
      description={an example},%  
      prefix={a~},%  
      prefixplural={the\space}%  
    }
    -

    Note that I’ve had to explicitly insert a space after the prefix. This allows for the possibility +

    Note that I’ve had to explicitly insert a space after the prefix. This allows for the possibility of prefixes that shouldn’t have a space, such as:

    -
    +
    \newglossaryentry{oeil}{name={oeil},  
      plural={yeux},  
      description={eye},  
      prefix={l’},  
      prefixplural={les\space}}
    -

    Where a space is required at the end of the prefix, you must use a spacing command, such as +

    Where a space is required at the end of the prefix, you must use a spacing command, such as \space, \␣ (backslash space) or ~ due to the automatic spacing trimming per ⟨key⟩=⟨value⟩ options. -

    The prefixes can also be used with acronyms. For example: +

    The prefixes can also be used with acronyms. For example:

    -
    +
    \newacronym  
     [%  
       prefix={an\space},prefixfirst={a~}%  
     ]{svm}{SVM}{support vector machine}
    -

    +

    -

    -

    ____________________________

    -

    The

    +

    ____________________________

    +

    The glossaries-prefix package provides convenient commands to use these prefixes with commands such as §6 Links to Glossary Entries for further details.) -



    \pgls  label}[insert]

    -

    +

    This is inserts the value of the prefix key (or label}[insert]. -



    \Pgls  label}[insert]

    -

    +

    If the prefix key (or label}[insert]. -



    \PGLS  label}[insert]

    -

    +

    As \pgls but converts the prefix to upper case and uses \GLS instead of \gls. -



    \pglspl  label}[insert]

    -

    +

    This is inserts the value of the prefixplural key (or label}[insert]. -



    \Pglspl  label}[insert]

    -

    +

    If the prefixplural key (or label}[insert]. -



    \PGLSpl  label}[insert]

    -

    +

    As \pglspl but converts the prefix to upper case and uses \GLSpl\glspl. -

    Example 30 (Using Prefixes) -

    Continuing from Example 

    Continuing from Example 29, now that I’ve defined my entries, I can use them in the text via the above commands:

    -
    +
    First use: \pgls{svm}. Next use: \pgls{svm}.  
    Singular: \pgls{sample}, \pgls{oeil}.  
    Plural: \pglspl{sample}, \pglspl{oeil}.
    -

    which produces: +

    which produces:

    -

    First use: a support vector machine (SVM). Next use: an SVM. Singular: +

    First use: a support vector machine (SVM). Next use: an SVM. Singular: a sample, l’oeil. Plural: the samples, les yeux.

    -

    For a complete document, see

    For a complete document, see sample-prefix.tex.

    -

    -

    ____________________________

    -

    This package also provides the commands described below, none of which perform any +

    +

    ____________________________

    +

    This package also provides the commands described below, none of which perform any check to determine the entry’s existence. -



    \ifglshasprefix  true part}{false part}

    -

    +

    Does ⟨true part⟩ if the entry identified by ⟨label⟩ has a non-empty value for the prefix key. -

    This package also provides the following commands: -


    This package also provides the following commands: +


    \ifglshasprefixplural  }{false part}

    -

    +

    Does ⟨true part⟩ if the entry identified by ⟨label⟩ has a non-empty value for the prefixplural key. -



    \ifglshasprefixfirst  }{false part}

    -

    +

    Does ⟨true part⟩ if the entry identified by ⟨label⟩ has a non-empty value for the prefixfirst key. -

    \ifglshasprefixfirstplural  -



    \ifglshasprefixfirstplural{label}{true part}{false part}

    -

    +

    Does ⟨true part⟩ if the entry identified by ⟨label⟩ has a non-empty value for the prefixfirstplural key. -



    \glsentryprefix  \glsentryprefix{label}

    -

    +

    Displays the value of the prefix key for the entry given by ⟨label⟩. -



    \glsentryprefixfirst  \glsentryprefixfirst{label}

    -

    +

    Displays the value of the prefixfirst key for the entry given by ⟨label⟩. -



    \glsentryprefixplural  \glsentryprefixplural{label}

    -

    +

    Displays the value of the prefixplural key for the entry given by ⟨label⟩. (No check is performed to determine if the entry exists.) -

    \glsentryprefixfirstplural  -



    \glsentryprefixfirstplural{label}

    -

    +

    Displays the value of the prefixfirstplural key for the entry given by ⟨label⟩. (No check is performed to determine if the entry exists.) -

    There are also variants that convert the first letter to upper +

    There are also variants that convert the first letter to upper case17.2: -



    \Glsentryprefix  \Glsentryprefix{label}

    -

    -


    +


    \Glsentryprefixfirst  \Glsentryprefixfirst{label}

    -

    -


    +


    \Glsentryprefixplural  \Glsentryprefixplural{label}

    -

    -

    +

    \Glsentryprefixfirstplural  -



    \Glsentryprefixfirstplural{label}

    -

    -

    As with analogous commands such as

    +

    As with analogous commands such as \Glsentrytext, these commands aren’t expandable so can’t be used in PDF bookmarks.
    -

    +

    -

    Example 31 (Adding Determiner to Glossary Style) -

    You can use the above commands to define a new glossary style that uses the determiner. +

    You can use the above commands to define a new glossary style that uses the determiner. For example, the following style is a slight modification of the list style that inserts the prefix @@ -22853,7 +23222,7 @@ before the name:

    -
    +
    \newglossarystyle{plist}{%  
      \setglossarystyle{list}%  
      \renewcommand*{\glossentry}[2]{% @@ -22863,18 +23232,18 @@ before the name:  
           \glossentrydesc{##1}\glspostdescription\space ##2}%  
    }
    -

    +

    -

    -

    ____________________________

    +

    +

    ____________________________

    -

    -

    +

    Top

    18. Accessibility Support

    -

    Limited accessibility support is provided by the accompanying

    Limited accessibility support is provided by the accompanying glossaries-accsupp package, but note that this package is experimental and it requires the shortplural\newacronym). -

    For example: +

    For example:

    -
    +
    \newglossaryentry{tex}{name={\TeX},description={Document  
    preparation language},access={TeX}}
    -

    Now

    Now \gls{tex} will be equivalent to

    -
    +
    \BeginAccSupp{ActualText=TeX}\TeX\EndAccSupp{}
    -

    The sample file

    The sample file sampleaccsupp.tex illustrates the glossaries-accsupp package. -

    See the documented code (

    See the documented code (glossaries-code.pdf) for further details. I recommend that you also read the accsuppaccsupp -

    -

    +

    Top

    19. Troubleshooting

    -

    The

    The glossaries package comes with some minimal example files, minimalgls.tex, LATEX code is available at http://www.dickimaw-books.com/latex/minexample/. -

    If you have any problems, please first consult the

    If you have any problems, please first consult the glossaries FAQ. If that doesn’t help, try posting your query to somewhere like the 6, 7
    \ACRfull  8
    \Acrfull  9
    \acrfull  10
    \acrfullfmt  11
    \acrfullformat  12
    \ACRfullpl  13
    \Acrfullpl  14
    \acrfullpl  15
    \ACRlong  16
    \Acrlong  17
    \acrlong  18
    \ACRlongpl  19
    \Acrlongpl  20
    \acrlongpl  21
    acronym styles:
        70
    \ACRshort  71
    \Acrshort  72
    \acrshort  73
    \ACRshortpl  74
    \Acrshortpl  75
    \acrshortpl  76
    \altnewglossary  84
    class="cmbx-10">B
    babel package  85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107
    +href="glossaries-user.html#dx1-4025" >85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111
    beamer class  108, 109
    +href="glossaries-user.html#dx1-65014" >112, 113
    beamer package  110
    +href="glossaries-user.html#dx1-8046" >114
    booktabs package  111, 112, 113
    +href="glossaries-user.html#dx1-70006" >115, 116, 117

    C \cGls  114
    +class="cmti-10">118
    \cgls  115
    +class="cmti-10">119
    \cGlsformat  116
    +class="cmti-10">120
    \cglsformat  117
    +class="cmti-10">121
    \cGlspl  118
    +class="cmti-10">122
    \cglspl  119
    +class="cmti-10">123
    \cGlsplformat  120
    +class="cmti-10">124
    \cglsplformat  121
    +class="cmti-10">125
    \currentglossary  122
    +class="cmti-10">126

    D datatool package  123, 124, 125, 126, 127
    +href="glossaries-user.html#dx1-9" >127, 128, 129, 130, 131
    datatool-base package  128
    +href="glossaries-user.html#dx1-8" >132
    \DeclareAcronymList  129
    +class="cmti-10">133
    \defglsentryfmt  130
    +class="cmti-10">134
    \DefineAcronymSynonyms  131
    +class="cmti-10">135
    doc package  132, 133, 134
    +href="glossaries-user.html#dx1-14" >136, 137, 138

    E encap  135
    +href="glossaries-user.html#dx1-43006" >139
    entry location  136
    +class="cmbx-10">140
    environments:
        theglossary  137
    +class="cmti-10">141
    etex package  138
    +href="glossaries-user.html#dx1-17033" >142
    etoolbox package  139, 140, 141, 142, 143, 144
    +href="glossaries-user.html#dx1-4" >143, 144, 145, 146, 147, 148
    Extended Latin Alphabet  145
    +class="cmbx-10">149
    extended Latin character  146, 150, 147, 148, 149, 150, 151, 152
    +class="cmbx-10">151, 152, 153, 154, 155, 156

    F file types
        .alg  153
    +href="glossaries-user.html#dx1-10069" >157
        .aux  154, 155, 156
    +href="glossaries-user.html#dx1-11002" >158, 159, 160
        .glg  157, 158, 159
    +href="glossaries-user.html#dx1-10068" >161, 162, 163
        .glg2  160
    +href="glossaries-user.html#dx1-18" >164
        .glo  161, 162, 163
    +href="glossaries-user.html#dx1-11021" >165, 166, 167
        .gls  164, 165
    +href="glossaries-user.html#dx1-13018" >168, 169
        .glsdefs  166, 167
    +href="glossaries-user.html#dx1-41013" >170, 171
        .ist  168, 169, 170, 171, 172, 173
    +href="glossaries-user.html#dx1-14005" >172, 173, 174, 175, 176, 177
        .tex  174, 175
    +href="glossaries-user.html#dx1-13011" >178, 179
        .xdy  176, 177, 178, 179, 180, 181, 182, 183
    +href="glossaries-user.html#dx1-13013" >180, 181, 182, 183, 184, 185, 186, 187
        glo2  184
    +href="glossaries-user.html#dx1-17" >188
        gls2  185
    +href="glossaries-user.html#dx1-16" >189
    first use  186
    +href="glossaries-user.html#dx1-3009" >190
        flag  187
    +href="glossaries-user.html#dx1-3017" >191
        text  188
    +href="glossaries-user.html#dx1-3018" >192
    \firstacronymfont  189
    +class="cmti-10">193
    flowfram package  190
    +href="glossaries-user.html#dx1-73011" >194
    fmtcount package  191
    +href="glossaries-user.html#dx1-56036" >195
    fontspec package  192
    +href="glossaries-user.html#dx1-28139" >196
    \forallacronyms  193
    +class="cmti-10">197
    \forallglossaries  194
    +class="cmti-10">198
    \forallglsentries  195
    +class="cmti-10">199
    \forglsentries  196
    +class="cmti-10">200

    G \Genacrfullformat  197
    +class="cmti-10">201
    \genacrfullformat  198
    +class="cmti-10">202
    \GenericAcronymFields  199
    +class="cmti-10">203
    \Genplacrfullformat  200
    +class="cmti-10">204
    \genplacrfullformat  201
    +class="cmti-10">205
    glossaries package  202, 203, 204, 205, 206
    +href="glossaries-user.html#dx1-6001" >206, 207, 208, 209, 210
    glossaries-accsupp package  207, 208, 209, 210, 211
    +href="glossaries-user.html#dx1-5108" >211, 212, 213, 214, 215
    glossaries-babel package  212, 213
    +href="glossaries-user.html#dx1-17049" >216, 217
    glossaries-extra package  214, 215
    +href="glossaries-user.html#dx1-52006" >218, 219, 220
    glossaries-polyglossia package  216
    +href="glossaries-user.html#dx1-17051" >221
    glossaries-prefix package  217, 218, 219, 220, 221
    +href="glossaries-user.html#dx1-5106" >222, 223, 224, 225, 226
    glossary counters:
        glossaryentry  222
    +class="cmti-10">227
        glossarysubentry  223
    +class="cmti-10">228
    glossary package  224, 225, 226, 227, 228
    +href="glossaries-user.html#dx1-11" >229, 230, 231, 232, 233
    glossary styles:
        altlist  229, 230, 231, 232, 233
    +href="glossaries-user.html#dx1-61047" >234, 235, 236, 237, 238
        altlistgroup  234, 235
    +href="glossaries-user.html#dx1-69024" >239, 240
        altlisthypergroup  236
    +href="glossaries-user.html#dx1-69026" >241
        altlong4col  237, 238, 239
    +href="glossaries-user.html#dx1-68022" >242, 243, 244
        altlong4col-booktabs  240
    +href="glossaries-user.html#dx1-72031" >245
        altlong4colborder  241
    +href="glossaries-user.html#dx1-70043" >246
        altlong4colheader  242, 243
    +href="glossaries-user.html#dx1-70045" >247, 248
        altlong4colheaderborder  244
    +href="glossaries-user.html#dx1-70047" >249
        altlongragged4col  245, 246, 247
    +href="glossaries-user.html#dx1-71030" >250, 251, 252
        altlongragged4col-booktabs  248
    +href="glossaries-user.html#dx1-72037" >253
        altlongragged4colborder  249
    +href="glossaries-user.html#dx1-71034" >254
        altlongragged4colheader  250, 251, 252
    +href="glossaries-user.html#dx1-71036" >255, 256, 257
        altlongragged4colheaderborder  253
    +href="glossaries-user.html#dx1-71038" >258
        altsuper4col  254, 255, 256
    +href="glossaries-user.html#dx1-68023" >259, 260, 261
        altsuper4colborder  257
    +href="glossaries-user.html#dx1-73048" >262
        altsuper4colheader  258
    +href="glossaries-user.html#dx1-73050" >263
        altsuper4colheaderborder  259
    +href="glossaries-user.html#dx1-73052" >264
        altsuperragged4col  260, 261, 262
    +href="glossaries-user.html#dx1-74032" >265, 266, 267
        altsuperragged4colborder  263
    +href="glossaries-user.html#dx1-74034" >268
        altsuperragged4colheader  264, 265
    +href="glossaries-user.html#dx1-74036" >269, 270
        altsuperragged4colheaderborder  266
    +href="glossaries-user.html#dx1-74038" >271
        alttree  267, 268, 269, 270, 271
    +href="glossaries-user.html#dx1-75022" >272, 273, 274, 275, 276
        alttreegroup  272, 273, 274
    +href="glossaries-user.html#dx1-75043" >277, 278, 279
        alttreehypergroup  275, 276
    +href="glossaries-user.html#dx1-75045" >280, 281
        index  277, 278, 279, 280, 281
    +href="glossaries-user.html#dx1-75010" >282, 283, 284, 285, 286
        indexgroup  282, 283, 284
    +href="glossaries-user.html#dx1-75012" >287, 288, 289
        indexhypergroup  285, 286, 287
    +href="glossaries-user.html#dx1-75007" >290, 291, 292
        inline  288, 289, 290
    +href="glossaries-user.html#dx1-5062" >293, 294, 295
        list  291, 292, 293, 294, 295, 296, 297, 298, 299, 300, 301, 302, 303
    +href="glossaries-user.html#dx1-19041" >296, 297, 298, 299, 300, 301, 302, 303, 304, 305, 306, 307, 308
        listdotted  304, 305, 306
    +href="glossaries-user.html#dx1-68034" >309, 310, 311
        listgroup  307, 308, 309, 310
    +href="glossaries-user.html#dx1-20020" >312, 313, 314, 315
        listhypergroup  311, 312, 313, 314, 315, 316, 317, 318
    +href="glossaries-user.html#dx1-69014" >316, 317, 318, 319, 320, 321, 322, 323
        long  319, 320, 321, 322, 323
    +href="glossaries-user.html#dx1-68030" >324, 325, 326, 327, 328
        long-booktabs  324, 325
    +href="glossaries-user.html#dx1-72024" >329, 330
        long3col  326, 327, 328, 329, 330
    +href="glossaries-user.html#dx1-68009" >331, 332, 333, 334, 335
        long3col-booktabs  331
    +href="glossaries-user.html#dx1-72026" >336
        long3colborder  332, 333
    +href="glossaries-user.html#dx1-68011" >337, 338
        long3colheader  334, 335, 336, 337
    +href="glossaries-user.html#dx1-68010" >339, 340, 341, 342
        long3colheaderborder  338, 339
    +href="glossaries-user.html#dx1-68012" >343, 344
        long4col  340, 341, 342, 343, 344
    +href="glossaries-user.html#dx1-68020" >345, 346, 347, 348, 349
        long4col-booktabs  345
    +href="glossaries-user.html#dx1-72029" >350
        long4colborder  346, 347
    +href="glossaries-user.html#dx1-70033" >351, 352
        long4colheader  348, 349, 350, 351
    +href="glossaries-user.html#dx1-70035" >353, 354, 355, 356
        long4colheaderborder  352, 353
    +href="glossaries-user.html#dx1-70037" >357, 358
        longborder  354
    +href="glossaries-user.html#dx1-70013" >359
        longheader  355, 356, 357, 358
    +href="glossaries-user.html#dx1-70015" >360, 361, 362, 363
        longheaderborder  359, 360
    +href="glossaries-user.html#dx1-70017" >364, 365
        longragged  361, 362, 363, 364
    +href="glossaries-user.html#dx1-71010" >366, 367, 368, 369
        longragged-booktabs  365
    +href="glossaries-user.html#dx1-72033" >370
        longragged3col  366, 367, 368, 369
    +href="glossaries-user.html#dx1-71019" >371, 372, 373, 374
        longragged3col-booktabs  370
    +href="glossaries-user.html#dx1-72035" >375
        longragged3colborder  371
    +href="glossaries-user.html#dx1-71024" >376
        longragged3colheader  372, 373, 374
    +href="glossaries-user.html#dx1-71026" >377, 378, 379
        longragged3colheaderborder  375
    +href="glossaries-user.html#dx1-71028" >380
        longraggedborder  376
    +href="glossaries-user.html#dx1-71013" >381
        longraggedheader  377, 378, 379
    +href="glossaries-user.html#dx1-71015" >382, 383, 384
        longraggedheaderborder  380
    +href="glossaries-user.html#dx1-71017" >385
        mcolalttree  381
    +href="glossaries-user.html#dx1-76039" >386
        mcolalttreegroup  382
    +href="glossaries-user.html#dx1-76041" >387
        mcolalttreehypergroup  383
    +href="glossaries-user.html#dx1-76043" >388
        mcolalttreespannav  384
    +href="glossaries-user.html#dx1-76044" >389
        mcolindex  385, 386
    +href="glossaries-user.html#dx1-76005" >390, 391
        mcolindexgroup  387
    +href="glossaries-user.html#dx1-76020" >392
        mcolindexhypergroup  388
    +href="glossaries-user.html#dx1-76022" >393
        mcolindexspannav  389
    +href="glossaries-user.html#dx1-76023" >394
        mcoltree  390
    +href="glossaries-user.html#dx1-76025" >395
        mcoltreegroup  391
    +href="glossaries-user.html#dx1-76027" >396
        mcoltreehypergroup  392, 393
    +href="glossaries-user.html#dx1-76029" >397, 398
        mcoltreenoname  394
    +href="glossaries-user.html#dx1-76032" >399
        mcoltreenonamegroup  395
    +href="glossaries-user.html#dx1-76034" >400
        mcoltreenonamehypergroup  396
    +href="glossaries-user.html#dx1-76036" >401
        mcoltreenonamespannav  397
    +href="glossaries-user.html#dx1-76037" >402
        mcoltreespannav  398
    +href="glossaries-user.html#dx1-76030" >403
        super  399, 400, 401, 402
    +href="glossaries-user.html#dx1-73012" >404, 405, 406, 407
        super3col  403, 404, 405, 406
    +href="glossaries-user.html#dx1-73024" >408, 409, 410, 411
        super3colborder  407
    +href="glossaries-user.html#dx1-73029" >412
        super3colheader  408, 409
    +href="glossaries-user.html#dx1-73031" >413, 414
        super3colheaderborder  410
    +href="glossaries-user.html#dx1-73033" >415
        super4col  411, 412, 413, 414, 415
    +href="glossaries-user.html#dx1-68021" >416, 417, 418, 419, 420
        super4colborder  416, 417
    +href="glossaries-user.html#dx1-73038" >421, 422
        super4colheader  418, 419, 420
    +href="glossaries-user.html#dx1-73040" >423, 424, 425
        super4colheaderborder  421, 422
    +href="glossaries-user.html#dx1-73042" >426, 427
        superborder  423
    +href="glossaries-user.html#dx1-73018" >428
        superheader  424, 425
    +href="glossaries-user.html#dx1-73020" >429, 430
        superheaderborder  426, 427
    +href="glossaries-user.html#dx1-53066" >431, 432
        superragged  428, 429, 430, 431
    +href="glossaries-user.html#dx1-74009" >433, 434, 435, 436
        superragged3col  432, 433, 434, 435
    +href="glossaries-user.html#dx1-74021" >437, 438, 439, 440
        superragged3colborder  436
    +href="glossaries-user.html#dx1-74026" >441
        superragged3colheader  437, 438
    +href="glossaries-user.html#dx1-74028" >442, 443
        superragged3colheaderborder  439
    +href="glossaries-user.html#dx1-74030" >444
        superraggedborder  440
    +href="glossaries-user.html#dx1-74015" >445
        superraggedheader  441, 442
    +href="glossaries-user.html#dx1-74017" >446, 447
        superraggedheaderborder  443
    +href="glossaries-user.html#dx1-74019" >448
        tree  444, 445, 446, 447, 448, 449
    +href="glossaries-user.html#dx1-62066" >449, 450, 451, 452, 453, 454
        treegroup  450, 451, 452
    +href="glossaries-user.html#dx1-75023" >455, 456, 457
        treehypergroup  453, 454, 455
    +href="glossaries-user.html#dx1-69019" >458, 459, 460
        treenoname  456, 457, 458
    +href="glossaries-user.html#dx1-75028" >461, 462, 463
        treenonamegroup  459, 460, 461
    +href="glossaries-user.html#dx1-75030" >464, 465, 466
        treenonamehypergroup  462, 463
    +href="glossaries-user.html#dx1-75032" >467, 468
    glossary-inline package  464, 465
    +href="glossaries-user.html#dx1-77001" >469, 470
    glossary-list package  466, 467, 468, 469, 470
    +href="glossaries-user.html#dx1-19026" >471, 472, 473, 474, 475
    glossary-long package  471, 472, 473, 474, 475, 476, 477, 478
    +href="glossaries-user.html#dx1-19027" >476, 477, 478, 479, 480, 481, 482, 483
    glossary-longbooktabs package  479, 480, 481
    +href="glossaries-user.html#dx1-72001" >484, 485, 486
    glossary-longragged package  482, 483, 484, 485
    +href="glossaries-user.html#dx1-71001" >487, 488, 489, 490
    glossary-mcols package  486, 487, 488, 489, 490, 491, 492
    +href="glossaries-user.html#dx1-19047" >491, 492, 493, 494, 495, 496, 497
    glossary-ragged package  493
    +href="glossaries-user.html#dx1-72010" >498
    glossary-super package  494, 495, 496, 497, 498, 499
    +href="glossaries-user.html#dx1-19028" >499, 500, 501, 502, 503, 504
    glossary-superragged package  500, 501, 502
    +href="glossaries-user.html#dx1-74001" >505, 506, 507
    glossary-tree package  503, 504, 505, 506, 507, 508, 509
    +href="glossaries-user.html#dx1-19029" >508, 509, 510, 511, 512, 513, 514
    glossaryentry (counter)  510, 511, 512, 513
    +class="cmti-10">515, 516, 517, 518
    \glossaryheader  514
    +class="cmti-10">519
    \glossarypostamble  515
    +class="cmti-10">520
    \glossarypreamble  516
    +class="cmti-10">521
    glossarysubentry (counter)  517
    +class="cmti-10">522
    \glossentry  518
    +class="cmti-10">523
    \Glossentrydesc  519
    +class="cmti-10">524
    \glossentrydesc  520
    +class="cmti-10">525
    \Glossentryname  521
    +class="cmti-10">526
    \glossentryname  522
    +class="cmti-10">527
    \Glossentrysymbol  523
    +class="cmti-10">528
    \glossentrysymbol  524
    +class="cmti-10">529
    \GLS  525
    +class="cmti-10">530
    \Gls  526
    +class="cmti-10">531
    \gls  527
    +class="cmti-10">532
    \glsacspace  528
    +class="cmti-10">533
    \glsadd  529
    +class="cmti-10">534
    \glsaddall  530
    +class="cmti-10">535
    \glsaddall options
        types  531
    +href="glossaries-user.html#dx1-49004" >536
    \glsaddallunused  532
    +class="cmti-10">537
    \glsaddkey  533
    +class="cmti-10">538
    \glsaddprotectedpagefmt  534
    +class="cmti-10">539
    \glsaddstoragekey  535
    +class="cmti-10">540
    \GlsAddXdyAttribute  536
    +class="cmti-10">541
    \GlsAddXdyCounters  537
    +class="cmti-10">542
    \GlsAddXdyLocation  538
    +href="glossaries-user.html#dx1-56024" >543
    \glsautoprefix  539
    +class="cmti-10">544
    \glsbackslash  540
    +class="cmti-10">545
    \glscapscase  541
    +class="cmti-10">546
    \glsclearpage  542
    +class="cmti-10">547
    \glsclosebrace  543
    +class="cmti-10">548
    \glscurrentfieldvalue  544
    +class="cmti-10">549
    \glscustomtext  545
    +class="cmti-10">550
    \GLSdesc  546
    +class="cmti-10">551
    \Glsdesc  547
    +class="cmti-10">552
    \glsdesc  548
    +class="cmti-10">553
    \glsdescwidth  549
    +class="cmti-10">554
    \glsdisablehyper  550
    +class="cmti-10">555
    \glsdisp  551
    +class="cmti-10">556
    \glsdisplaynumberlist  552
    +class="cmti-10">557
    \glsdoifexists  553
    +class="cmti-10">558
    \glsdoifexistsordo  554
    +class="cmti-10">559
    \glsdoifexistsorwarn  555
    +class="cmti-10">560
    \glsdoifnoexists  556
    +class="cmti-10">561
    \glsdoifnoexistsordo  557
    +class="cmti-10">562
    \glsdosanitizesort  558
    +class="cmti-10">563
    \glsenableentrycount  559
    +class="cmti-10">564
    \glsenablehyper  560
    +class="cmti-10">565
    \glsentrycounterlabel  561
    +class="cmti-10">566
    \glsentrycurrcount  562
    +class="cmti-10">567
    \Glsentrydesc  563
    +class="cmti-10">568
    \glsentrydesc  564
    +class="cmti-10">569
    \Glsentrydescplural  565
    +class="cmti-10">570
    \glsentrydescplural  566
    +class="cmti-10">571
    \Glsentryfirst  567
    +class="cmti-10">572
    \glsentryfirst  568
    +class="cmti-10">573
    \Glsentryfirstplural  569
    +class="cmti-10">574
    \glsentryfirstplural  570
    +class="cmti-10">575
    \glsentryfmt  571
    +class="cmti-10">576
    \Glsentryfull  572
    +href="glossaries-user.html#dx1-59118" >577
    \glsentryfull  573
    +href="glossaries-user.html#dx1-59117" >578
    \Glsentryfullpl  574
    +href="glossaries-user.html#dx1-59120" >579
    \glsentryfullpl  575
    +href="glossaries-user.html#dx1-59119" >580
    \glsentryitem  576
    +class="cmti-10">581
    \Glsentrylong  577
    +href="glossaries-user.html#dx1-59110" >582
    \glsentrylong  578
    +href="glossaries-user.html#dx1-59109" >583
    \Glsentrylongpl  579
    +href="glossaries-user.html#dx1-59112" >584
    \glsentrylongpl  580
    +href="glossaries-user.html#dx1-59111" >585
    \Glsentryname  581
    +class="cmti-10">586
    \glsentryname  582
    +class="cmti-10">587
    \glsentrynumberlist  583
    +class="cmti-10">588
    \Glsentryplural  584
    +class="cmti-10">589
    \glsentryplural  585
    +class="cmti-10">590
    \Glsentryprefix  586
    +class="cmti-10">591
    \glsentryprefix  587
    +class="cmti-10">592
    \Glsentryprefixfirst  588
    +class="cmti-10">593
    \glsentryprefixfirst  589
    +class="cmti-10">594
    \Glsentryprefixfirstplural  590
    +class="cmti-10">595
    \glsentryprefixfirstplural  591
    +class="cmti-10">596
    \Glsentryprefixplural  592
    +class="cmti-10">597
    \glsentryprefixplural  593
    +class="cmti-10">598
    \glsentryprevcount  594
    +class="cmti-10">599
    \Glsentryshort  595
    +href="glossaries-user.html#dx1-59114" >600
    \glsentryshort  596
    +href="glossaries-user.html#dx1-59113" >601
    \Glsentryshortpl  597
    +href="glossaries-user.html#dx1-59116" >602
    \glsentryshortpl  598
    +href="glossaries-user.html#dx1-59115" >603
    \Glsentrysymbol  599
    +class="cmti-10">604
    \glsentrysymbol  600
    +class="cmti-10">605
    \Glsentrysymbolplural  601
    +class="cmti-10">606
    \glsentrysymbolplural  602
    +class="cmti-10">607
    \Glsentrytext  603
    +class="cmti-10">608
    \glsentrytext  604
    +class="cmti-10">609
    \glsentrytitlecase  605
    +class="cmti-10">610
    \Glsentryuseri  606
    +class="cmti-10">611
    \glsentryuseri  607
    +class="cmti-10">612
    \Glsentryuserii  608
    +class="cmti-10">613
    \glsentryuserii  609
    +class="cmti-10">614
    \Glsentryuseriii  610
    +class="cmti-10">615
    \glsentryuseriii  611
    +class="cmti-10">616
    \Glsentryuseriv  612
    +class="cmti-10">617
    \glsentryuseriv  613
    +class="cmti-10">618
    \Glsentryuserv  614
    +class="cmti-10">619
    \glsentryuserv  615
    +class="cmti-10">620
    \Glsentryuservi  616
    +class="cmti-10">621
    \glsentryuservi  617
    +class="cmti-10">622
    \glsexpandfields  618
    +class="cmti-10">623
    \glsfielddef  619
    +class="cmti-10">624
    \glsfieldedef  620
    +class="cmti-10">625
    \glsfieldfetch  621
    +class="cmti-10">626
    \glsfieldgdef  622
    +class="cmti-10">627
    \glsfieldxdef  623
    +class="cmti-10">628
    \glsfindwidesttoplevelname  624
    +class="cmti-10">629
    \GLSfirst  625
    +class="cmti-10">630
    \Glsfirst  626
    +class="cmti-10">631
    \glsfirst  627
    +class="cmti-10">632
    \GLSfirstplural  628
    +class="cmti-10">633
    \Glsfirstplural  629
    +class="cmti-10">634
    \glsfirstplural  630
    +class="cmti-10">635
    \glsgenacfmt  631
    +class="cmti-10">636
    \glsgenentryfmt  632
    +class="cmti-10">637
    \glsgetgrouptitle  633
    +class="cmti-10">638
    \glsglossarymark  634, 639, 635
    +class="cmti-10">640
    \glsgroupheading  636
    +class="cmti-10">641
    \glsgroupskip  637
    +class="cmti-10">642
    \glshyperlink  638
    +class="cmti-10">643
    \glshypernavsep  639
    +class="cmti-10">644
    \glsifhyperon  640
    +class="cmti-10">645
    \glsIfListOfAcronyms  641
    +class="cmti-10">646
    \glsifplural  642
    +class="cmti-10">647
    \glsinlinedescformat  643
    +class="cmti-10">648
    \glsinlineemptydescformat  644
    +class="cmti-10">649
    \glsinlinenameformat  645
    +class="cmti-10">650
    \glsinlineparentchildseparator  646
    +class="cmti-10">651
    \glsinlineseparator  647
    +class="cmti-10">652
    \glsinlinesubdescformat  648
    +class="cmti-10">653
    \glsinlinesubnameformat  649
    +class="cmti-10">654
    \glsinlinesubseparator  650
    +class="cmti-10">655
    \glsinsert  651
    +class="cmti-10">656
    \glslabel  652
    +class="cmti-10">657
    \glslabeltok  653
    +class="cmti-10">658
    \glsletentryfield  654
    +class="cmti-10">659
    \glslink  655
    +class="cmti-10">660
    \glslink options
        counter  656, 657
    +href="glossaries-user.html#dx1-44069" >661, 662
        format  658, 659, 660, 661, 662, 663
    +href="glossaries-user.html#dx1-43008" >663, 664, 665, 666, 667, 668, 669
        hyper  664, 665, 666, 667, 668, 669, 670
    +href="glossaries-user.html#dx1-17091" >670, 671, 672, 673, 674, 675, 676
        local  671
    +href="glossaries-user.html#dx1-44070" >677
    \glslinkcheckfirsthyperhook  672
    +href="glossaries-user.html#dx1-17093" >678
    \glslinkpostsetkeys  673
    +class="cmti-10">679
    \glslinkvar  674
    +class="cmti-10">680
    \glslistdottedwidth  675
    +class="cmti-10">681
    \glslistnavigationitem  676
    +class="cmti-10">682
    \glslocalreset  677
    +class="cmti-10">683
    \glslocalresetall  678
    +class="cmti-10">684
    \glslocalunset  679
    +class="cmti-10">685
    \glslocalunsetall  680
    +class="cmti-10">686
    \glslongtok  681
    +class="cmti-10">687
    \glsmcols  682
    +class="cmti-10">688
    \glsmoveentry  683
    +class="cmti-10">689
    \GLSname  684
    +class="cmti-10">690
    \Glsname  685
    +class="cmti-10">691
    \glsname  686
    +class="cmti-10">692
    \glsnamefont  687
    +class="cmti-10">693
    \glsnavhypertarget  688
    +class="cmti-10">694
    \glsnavigation  689
    +class="cmti-10">695
    \glsnoexpandfields  690
    +class="cmti-10">696
    \glsnoidxdisplayloc  691
    +class="cmti-10">697
    \glsnumberlistloop  692
    +class="cmti-10">698
    \glsnumlistlastsep  693
    +class="cmti-10">699
    \glsnumlistsep  694
    +class="cmti-10">700
    \glsopenbrace  695
    +class="cmti-10">701
    \glspagelistwidth  696
    +class="cmti-10">702
    \glspar  697
    +class="cmti-10">703
    \glspercentchar  698
    +class="cmti-10">704
    \GLSpl  699
    +class="cmti-10">705
    \Glspl  700
    +class="cmti-10">706
    \glspl  701
    +class="cmti-10">707
    \GLSplural  702
    +class="cmti-10">708
    \Glsplural  703
    +class="cmti-10">709
    \glsplural  704
    +class="cmti-10">710
    \glspluralsuffix  705
    +class="cmti-10">711
    \glspostdescription  706
    +class="cmti-10">712
    \glspostinline  707
    +class="cmti-10">713
    \glspostlinkhook  708
    +class="cmti-10">714
    \glsprestandardsort  709
    +class="cmti-10">715
    \glsquote  710
    +class="cmti-10">716
    \glsrefentry  711
    +class="cmti-10">717
    \glsreset  712
    +class="cmti-10">718
    \glsresetall  713
    +class="cmti-10">719
    \glsresetentrycounter  714
    +class="cmti-10">720
    \glsrestoreLToutput  715
    +class="cmti-10">721
    \glssee  716
    +class="cmti-10">722
    \glsseeformat  717
    +class="cmti-10">723
    \glsseeitemformat  718
    +class="cmti-10">724
    \glsseelastsep  719
    +class="cmti-10">725
    \glsseesep  720
    +class="cmti-10">726
    \glsSetAlphaCompositor  721
    +class="cmti-10">727
    \glsSetCompositor  722
    +class="cmti-10">728
    \glssetexpandfield  723
    +class="cmti-10">729
    \glssetnoexpandfield  724
    +class="cmti-10">730
    +\GlsSetQuote  731
    \glsSetSuffixF  725
    +class="cmti-10">732
    \glsSetSuffixFF  726
    +class="cmti-10">733
    \glssetwidest  727
    +class="cmti-10">734
    +\GlsSetWriteIstHook  735
    \GlsSetXdyCodePage  728
    +class="cmti-10">736
    \GlsSetXdyFirstLetterAfterDigits  729
    +class="cmti-10">737
    \GlsSetXdyLanguage  730
    +class="cmti-10">738
    \GlsSetXdyLocationClassOrder  731
    +href="glossaries-user.html#dx1-56052" >739
    \GlsSetXdyMinRangeLength  732
    +href="glossaries-user.html#dx1-56057" >740
    \glsshorttok  733
    +class="cmti-10">741
    \glssortnumberfmt  734
    +class="cmti-10">742
    \glssubentrycounterlabel  735
    +class="cmti-10">743
    \glssubentryitem  736
    +class="cmti-10">744
    \GLSsymbol  737
    +class="cmti-10">745
    \Glssymbol  738
    +class="cmti-10">746
    \glssymbol  739
    +class="cmti-10">747
    \glstarget  740
    +class="cmti-10">748
    \GLStext  741
    +class="cmti-10">749
    \Glstext  742
    +class="cmti-10">750
    \glstext  743
    +class="cmti-10">751
    \glstextformat  744
    +class="cmti-10">752
    \glstextup  745
    +class="cmti-10">753
    \glstildechar  746
    +class="cmti-10">754
    \glstocfalse  747
    +class="cmti-10">755
    \glstoctrue  748
    +class="cmti-10">756
    \glstreegroupheaderfmt  749
    +class="cmti-10">757
    \glstreeindent  750
    +class="cmti-10">758
    \glstreenamebox  751
    +class="cmti-10">759
    \glstreenamefmt  752
    +class="cmti-10">760
    \glstreenavigationfmt  753
    +class="cmti-10">761
    \glstype  754
    +class="cmti-10">762
    \glsunset  755
    +class="cmti-10">763
    \glsunsetall  756
    +class="cmti-10">764
    \GlsUseAcrEntryDispStyle  757
    +class="cmti-10">765
    \GlsUseAcrStyleDefs  758
    +class="cmti-10">766
    \GLSuseri  759
    +class="cmti-10">767
    \Glsuseri  760
    +class="cmti-10">768
    + + \glsuseri  761
    +class="cmti-10">769
    \GLSuserii  762
    - - +class="cmti-10">770
    \Glsuserii  763
    +class="cmti-10">771
    \glsuserii  764
    +class="cmti-10">772
    \GLSuseriii  765
    +class="cmti-10">773
    \Glsuseriii  766
    +class="cmti-10">774
    \glsuseriii  767
    +class="cmti-10">775
    \GLSuseriv  768
    +class="cmti-10">776
    \Glsuseriv  769
    +class="cmti-10">777
    \glsuseriv  770
    +class="cmti-10">778
    \GLSuserv  771
    +class="cmti-10">779
    \Glsuserv  772
    +class="cmti-10">780
    \glsuserv  773
    +class="cmti-10">781
    \GLSuservi  774
    +class="cmti-10">782
    \Glsuservi  775
    +class="cmti-10">783
    \glsuservi  776
    +class="cmti-10">784
    \glswrallowprimitivemodsfalse  777
    +class="cmti-10">785
    +\glswrite  786
    \glswriteentry  778
    +href="glossaries-user.html#dx1-17106" >787

    H html package  779
    +href="glossaries-user.html#dx1-48002" >788
    hyperref package  780, 781, 782, 783, 784, 785, 786, 787, 788, 789, 790, 791, 792, 793, 794, 795, 796, 797, 798, 799, 800, 801, 802
    +href="glossaries-user.html#dx1-12" >789, 790, 791, 792, 793, 794, 795, 796, 797, 798, 799, 800, 801, 802, 803, 804, 805, 806, 807, 808, 809, 810, 811

    I \ifglossaryexists  803
    +class="cmti-10">812
    \ifglsdescsuppressed  804
    +class="cmti-10">813
    \ifglsentryexists  805
    +class="cmti-10">814
    \ifglsfieldcseq  806
    +class="cmti-10">815
    \ifglsfielddefeq  807
    +class="cmti-10">816
    \ifglsfieldeq  808
    +class="cmti-10">817
    \ifglshaschildren  809
    +class="cmti-10">818
    \ifglshasdesc  810
    +class="cmti-10">819
    \ifglshasfield  811
    +class="cmti-10">820
    \ifglshaslong  812
    +class="cmti-10">821
    \ifglshasparent  813
    +class="cmti-10">822
    \ifglshasprefix  814
    +class="cmti-10">823
    \ifglshasprefixfirst  815
    +class="cmti-10">824
    \ifglshasprefixfirstplural  816
    +class="cmti-10">825
    \ifglshasprefixplural  817
    +class="cmti-10">826
    \ifglshasshort  818
    +class="cmti-10">827
    \ifglshassymbol  819
    +class="cmti-10">828
    \ifglsucmark  820
    +class="cmti-10">829
    \ifglsused  821, 830, 822
    +class="cmti-10">831
    + + \ifignoredglossary  823
    +class="cmti-10">832
    imakeidx package  824
    +href="glossaries-user.html#dx1-23022" >833
    index package  825
    - - +href="glossaries-user.html#dx1-23021" >834
    inputenc package  826, 827, 828, 829, 830, 831
    +href="glossaries-user.html#dx1-5016" >835, 836, 837, 838, 839, 840

    L latex  832, 833
    +href="glossaries-user.html#dx1-22" >841, 842
    latexmk  834
    +href="glossaries-user.html#dx1-10014" >843
    Latin alphabet  835, 836, 837
    +class="cmbx-10">844, 845, 846
    Latin character  838, 839, 840, 841, 847, 848, 849, 850, 842, 843, 844
    +class="cmbx-10">851, 852, 853
    link text  845, 846, 847, 848, 849, 850, 851, 852, 853, 854, 855, 856, 857, 858, 859, 860, 861, 862, 863, 864, 865, 866, 867, 868, 869, 870, 871, 872, 873, 874, 875, 876, 877, 878, 879, 880, 881, 882, 883, 884, 885, 886, 887, 888, 889, 890, 891, 892, 893
    +class="cmbx-10">854, 855, 856, 857, 858, 859, 860, 861, 862, 863, 864, 865, 866, 867, 868, 869, 870, 871, 872, 873, 874, 875, 876, 877, 878, 879, 880, 881, 882, 883, 884, 885, 886, 887, 888, 889, 890, 891, 892, 893, 894, 895, 896, 897, 898, 899, 900, 901, 902
    \loadglsentries  894
    +class="cmti-10">903
    location list  see number list
    \longnewglossaryentry  896
    +class="cmti-10">905
    \longprovideglossaryentry  897
    +class="cmti-10">906
    longtable package  898, 899
    +href="glossaries-user.html#dx1-19032" >907, 908

    M makeglossaries  900, 901, 902, 903, 904, 905, 906, 907, 908, 909, 910, 911, 912, 913, 914, 915, 916, 917, 918, 919, 920, 921, 922, 923, 924, 925, 926, 927, 928, 929, 930, 931, 932, 933, 934, 935, 936, 937, 938, 939, 940, 941, 942, 943, 944, 945, 946, 947, 948, 949, 950, 951, 952, 953, 954, 955, 956, 957, 958, 959, 960, 961, 962, 963, 964, 965, 966, 967, 968, 969, 970, 971, 972, 973, 974, 975, 976, 977, 978, 979, 980, 981, 982
    +class="cmbx-10">909, 910, 911, 912, 913, 914, 915, 916, 917, 918, 919, 920, 921, 922, 923, 924, 925, 926, 927, 928, 929, 930, 931, 932, 933, 934, 935, 936, 937, 938, 939, 940, 941, 942, 943, 944, 945, 946, 947, 948, 949, 950, 951, 952, 953, 954, 955, 956, 957, 958, 959, 960, 961, 962, 963, 964, 965, 966, 967, 968, 969, 970, 971, 972, 973, 974, 975, 976, 977, 978, 979, 980, 981, 982, 983, 984, 985, 986, 987, 988, 989, 990, 991, 992, 993
    +    -d  994
    +    -k  995
    +    -m  996
    +    -Q  997
    +    -q  998
    +    -x  999
    \makeglossaries  983
    +class="cmti-10">1000
    makeglossaries-lite.lua  984, 985, 986, 987, 988, 989, 990, 991
    +class="cmbx-10">1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009
    makeglossariesgui  992, 993
    +class="cmbx-10">1010, 1011, 1012
    makeidx package  994
    +href="glossaries-user.html#dx1-23020" >1013
    makeindex  995, 996, 997, 1014, 1015, 1016, 998, 999, 1000, 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009, 1010, 1011, 1012, 1013, 1014, 1015, 1016, 1017, 1018, 1019, 1020, 1021, 1022, 1023, 1024, 1025, 1026, 1027, 1028, 1029, 1030, 1031, 1032, 1033, 1034, 1035, 1036, 1037, 1038, 1039, 1040, 1041, 1042, 1043, 1044, 1045, 1046, 1047, 1048, 1049, 1050, 1051, 1052, 1053, 1054, 1055, 1056, 1057, 1058, 1059, 1060, 1061, 1062, 1063, 1064, 1065, 1066, 1067, 1068, 1069, 1070, 1071, 1072, 1073, 1074, 1075, 1076, 1077, 1078, 1079, 1080, 1081, 1082, 1083, 1084, 1085, 1086, 1087, 1088, 1089, 1090, 1091, 1092
    +class="cmbx-10">1017, 1018, 1019, 1020, 1021, 1022, 1023, 1024, 1025, 1026, 1027, 1028, 1029, 1030, 1031, 1032, 1033, 1034, 1035, 1036, 1037, 1038, 1039, 1040, 1041, 1042, 1043, 1044, 1045, 1046, 1047, 1048, 1049, 1050, 1051, 1052, 1053, 1054, 1055, 1056, 1057, 1058, 1059, 1060, 1061, 1062, 1063, 1064, 1065, 1066, 1067, 1068, 1069, 1070, 1071, 1072, 1073, 1074, 1075, 1076, 1077, 1078, 1079, 1080, 1081, 1082, 1083, 1084, 1085, 1086, 1087, 1088, 1089, 1090, 1091, 1092, 1093, 1094, 1095, 1096, 1097, 1098, 1099, 1100, 1101, 1102, 1103, 1104, 1105, 1106, 1107, 1108, 1109, 1110, 1111, 1112, 1113, 1114, 1115, 1116, 1117, 1118, 1119, 1120
    +    -g  1121, 1122, 1123
    +    -l  1124, 1125, 1126, 1127
    \makenoidxglossaries  1093
    +class="cmti-10">1128
    memoir class  1094, 1095, 1096, 1097
    +href="glossaries-user.html#dx1-18021" >1129, 1130, 1131, 1132
    mfirstuc package  1098, 1099, 1100, 1101, 1102, 1103, 1104
    +href="glossaries-user.html#dx1-3" >1133, 1134, 1135, 1136, 1137, 1138, 1139
    multicol package  1105
    +href="glossaries-user.html#dx1-76004" >1140
    mwe package  1106
    +href="glossaries-user.html#dx1-6006" >1141

    N nameref package  1107
    +href="glossaries-user.html#dx1-18049" >1142
    \newacronym  1108
    +class="cmti-10">1143
    + + \newacronymstyle  1109
    +class="cmti-10">1144
    \newglossary  1110
    +class="cmti-10">1145
    \newglossary*  1111
    +class="cmti-10">1146
    \newglossaryentry  1112
    +class="cmti-10">1147
    \newglossaryentry options
        access  1113
    +href="glossaries-user.html#dx1-84003" >1148
        description  1114, 1115, 1116, 1117, 1118, 1119, 1120, 1121, 1122, 1123, 1124, 1125, 1126, 1127, 1128, 1129, 1130, 1131
    +href="glossaries-user.html#dx1-6007" >1149, 1150, 1151, 1152, 1153, 1154, 1155, 1156, 1157, 1158, 1159, 1160, 1161, 1162, 1163, 1164, 1165, 1166
        descriptionaccess  1132
    +href="glossaries-user.html#dx1-84017" >1167
        descriptionplural  1133, 1134, 1135, 1136
    +href="glossaries-user.html#dx1-28022" >1168, 1169, 1170, 1171
        descriptionpluralaccess  1137
    +href="glossaries-user.html#dx1-84019" >1172
        entrycounter  1138, 1139
    - - +href="glossaries-user.html#dx1-53035" >1173, 1174
        first  1140, 1141, 1142, 1143, 1144, 1145, 1146, 1147, 1148, 1149, 1150, 1151, 1152, 1153, 1154, 1155, 1156, 1157, 1158, 1159, 1160, 1161, 1162, 1163, 1164
    +href="glossaries-user.html#dx1-3019" >1175, 1176, 1177, 1178, 1179, 1180, 1181, 1182, 1183, 1184, 1185, 1186, 1187, 1188, 1189, 1190, 1191, 1192, 1193, 1194, 1195, 1196, 1197, 1198, 1199
        firstaccess  1165
    +href="glossaries-user.html#dx1-84007" >1200
        firstplural  1166, 1167, 1168, 1169, 1170, 1171, 1172, 1173, 1174, 1175, 1176, 1177, 1178, 1179, 1180, 1181, 1182
    +href="glossaries-user.html#dx1-3020" >1201, 1202, 1203, 1204, 1205, 1206, 1207, 1208, 1209, 1210, 1211, 1212, 1213, 1214, 1215, 1216, 1217
        firstpluralaccess  1183
    +href="glossaries-user.html#dx1-84011" >1218
        format  1184
    +href="glossaries-user.html#dx1-44067" >1219
        long  1185, 1186, 1187, 1188, 1189, 1190, 1191, 1192, 1193, 1194, 1195, 1196, 1197
    +href="glossaries-user.html#dx1-17098" >1220, 1221, 1222, 1223, 1224, 1225, 1226, 1227, 1228, 1229, 1230, 1231, 1232
        longaccess  1198
    +href="glossaries-user.html#dx1-84021" >1233
        longplural  1199, 1200, 1201, 1202, 1203, 1204, 1205, 1206, 1207
    +href="glossaries-user.html#dx1-28124" >1234, 1235, 1236, 1237, 1238, 1239, 1240, 1241, 1242
        longpluralaccess  1208
    +href="glossaries-user.html#dx1-84027" >1243
        name  1209, 1210, 1211, 1212, 1213, 1214, 1215, 1216, 1217, 1218, 1219, 1220, 1221, 1222, 1223, 1224, 1225, 1226, 1227, 1228, 1229, 1230, 1231, 1232, 1233, 1234, 1235, 1236, 1237, 1238, 1239, 1240, 1241, 1242, 1243
    +href="glossaries-user.html#dx1-6009" >1244, 1245, 1246, 1247, 1248, 1249, 1250, 1251, 1252, 1253, 1254, 1255, 1256, 1257, 1258, 1259, 1260, 1261, 1262, 1263, 1264, 1265, 1266, 1267, 1268, 1269, 1270, 1271, 1272, 1273, 1274, 1275, 1276, 1277, 1278
        nonumberlist  1244
    +href="glossaries-user.html#dx1-28105" >1279
        parent  1245, 1246, 1247, 1248
    +href="glossaries-user.html#dx1-28011" >1280, 1281, 1282, 1283
        plural  1249, 1250, 1251, 1252, 1253, 1254, 1255, 1256, 1257, 1258, 1259, 1260, 1261, 1262, 1263
    +href="glossaries-user.html#dx1-28037" >1284, 1285, 1286, 1287, 1288, 1289, 1290, 1291, 1292, 1293, 1294, 1295, 1296, 1297, 1298
        pluralaccess  1264
    +href="glossaries-user.html#dx1-84009" >1299
        prefix  1265, 1266, 1267, 1268, 1269, 1270, 1271
    +href="glossaries-user.html#dx1-83003" >1300, 1301, 1302, 1303, 1304, 1305, 1306
        prefixfirst  1272, 1273, 1274, 1275, 1276
    +href="glossaries-user.html#dx1-83007" >1307, 1308, 1309, 1310, 1311
        prefixfirstplural  1277, 1278, 1279, 1280, 1281
    +href="glossaries-user.html#dx1-83010" >1312, 1313, 1314, 1315, 1316
        prefixplural  1282, 1283, 1284, 1285, 1286, 1287
    +href="glossaries-user.html#dx1-83005" >1317, 1318, 1319, 1320, 1321, 1322
        see  1288, 1289, 1290, 1291, 1292, 1293, 1294, 1295, 1296, 1297, 1298, 1299, 1300, 1301
    +href="glossaries-user.html#dx1-17012" >1323, 1324, 1325, 1326, 1327, 1328, 1329, 1330, 1331, 1332, 1333, 1334, 1335, 1336, 1337, 1338
        short  1302, 1303, 1304, 1305, 1306, 1307, 1308, 1309, 1310, 1311, 1312
    +href="glossaries-user.html#dx1-28125" >1339, 1340, 1341, 1342, 1343, 1344, 1345, 1346, 1347, 1348, 1349
        shortaccess  1313
    +href="glossaries-user.html#dx1-84024" >1350
        shortplural  1314, 1315, 1316, 1317, 1318, 1319, 1320, 1321, 1322
    +href="glossaries-user.html#dx1-28126" >1351, 1352, 1353, 1354, 1355, 1356, 1357, 1358, 1359
        shortpluralaccess  1323
    +href="glossaries-user.html#dx1-84030" >1360
        sort  1324, 1325, 1326, 1327, 1328, 1329, 1330, 1331, 1332, 1333, 1334, 1335, 1336, 1337, 1338, 1339, 1340, 1341, 1342, 1343, 1344, 1345, 1346, 1347, 1348, 1349, 1350, 1351, 1352, 1353, 1354
    +href="glossaries-user.html#dx1-3049" >1361, 1362, 1363, 1364, 1365, 1366, 1367, 1368, 1369, 1370, 1371, 1372, 1373, 1374, 1375, 1376, 1377, 1378, 1379, 1380, 1381, 1382, 1383, 1384, 1385, 1386, 1387, 1388, 1389, 1390, 1391, 1392
        subentrycounter  1355
    +href="glossaries-user.html#dx1-53036" >1393
        symbol  1356, 1357, 1358, 1359, 1360, 1361, 1362, 1363, 1364, 1365, 1366, 1367
    +href="glossaries-user.html#dx1-6004" >1394, 1395, 1396, 1397, 1398, 1399, 1400, 1401, 1402, 1403, 1404, 1405
        symbolaccess  1368
    +href="glossaries-user.html#dx1-84013" >1406
        symbolplural  1369, 1370, 1371
    +href="glossaries-user.html#dx1-28061" >1407, 1408, 1409
        symbolpluralaccess  1372
    +href="glossaries-user.html#dx1-84015" >1410
        text  1373, 1374, 1375, 1376, 1377, 1378, 1379, 1380, 1381, 1382, 1383, 1384, 1385, 1386, 1387, 1388, 1389, 1390, 1391, 1392, 1393
    +href="glossaries-user.html#dx1-28024" >1411, 1412, 1413, 1414, 1415, 1416, 1417, 1418, 1419, 1420, 1421, 1422, 1423, 1424, 1425, 1426, 1427, 1428, 1429, 1430, 1431
        textaccess  1394
    +href="glossaries-user.html#dx1-84005" >1432
    + +     type  1395, 1396, 1397
    +href="glossaries-user.html#dx1-28093" >1433, 1434, 1435
        user1  1398, 1399, 1400, 1401, 1402, 1403, 1404, 1405, 1406, 1407, 1408
    +href="glossaries-user.html#dx1-6005" >1436, 1437, 1438, 1439, 1440, 1441, 1442, 1443, 1444, 1445, 1446
        user2  1409, 1410, 1411, 1412
    +href="glossaries-user.html#dx1-28097" >1447, 1448, 1449, 1450
        user3  1413, 1414, 1415
    +href="glossaries-user.html#dx1-28098" >1451, 1452, 1453
        user4  1416, 1417, 1418
    +href="glossaries-user.html#dx1-28099" >1454, 1455, 1456
        user5  1419, 1420, 1421
    +href="glossaries-user.html#dx1-28100" >1457, 1458, 1459
        user6  1422, 1423, 1424, 1425
    +href="glossaries-user.html#dx1-28096" >1460, 1461, 1462, 1463
    \newglossarystyle  1426
    +class="cmti-10">1464
    \newignoredglossary  1427
    +class="cmti-10">1465
    \newterm  1428
    +class="cmti-10">1466
    ngerman package  1429, 1430
    - - +href="glossaries-user.html#dx1-7018" >1467, 1468, 1469, 1470, 1471
    \noist  1431
    +class="cmti-10">1472
    Non-Latin Alphabet  1432
    +class="cmbx-10">1473
    non-Latin character  1433, 1434, 1474, 1475, 1435, 1436, 1437, 1438, 1439, 1440, 1441, 1442, 1443
    +class="cmbx-10">1476, 1477, 1478, 1479, 1480, 1481, 1482, 1483, 1484
    \nopostdesc  1444
    +class="cmti-10">1485
    number list  1445, 1446, 1447, 1448, 1449, 1450, 1451, 1452, 1453, 1454, 1455, 1456, 1457, 1458, 1459, 1460, 1461, 1462, 1463, 1464, 1465, 1466, 1467, 1468, 1469, 1470, 1471, 1472, 1473, 1474, 1475, 1476, 1477, 1478, 1479, 1480, 1481, 1482, 1483, 1484, 1485, 1486, 1487, 1488, 1489, 1490, 1491, 1492, 1493, 1494
    +class="cmbx-10">1486, 1487, 1488, 1489, 1490, 1491, 1492, 1493, 1494, 1495, 1496, 1497, 1498, 1499, 1500, 1501, 1502, 1503, 1504, 1505, 1506, 1507, 1508, 1509, 1510, 1511, 1512, 1513, 1514, 1515, 1516, 1517, 1518, 1519, 1520, 1521, 1522, 1523, 1524, 1525, 1526, 1527, 1528, 1529, 1530, 1531, 1532, 1533, 1534, 1535

    O \oldacronym  1495
    +class="cmti-10">1536

    P package options:
        acronym  1496, 1497, 1498, 1499, 1500, 1501, 1502, 1503, 1504, 1505, 1506, 1507, 1508, 1509, 1510, 1511, 1512, 1513, 1514, 1515, 1516, 1517, 1518, 1519
    +href="glossaries-user.html#dx1-8026" >1537, 1538, 1539, 1540, 1541, 1542, 1543, 1544, 1545, 1546, 1547, 1548, 1549, 1550, 1551, 1552, 1553, 1554, 1555, 1556, 1557, 1558, 1559, 1560
            true  1520, 1521
    +href="glossaries-user.html#dx1-16002" >1561, 1562
        acronymlists  1522, 1523, 1524, 1525, 1526, 1527, 1528
    +href="glossaries-user.html#dx1-21019" >1563, 1564, 1565, 1566, 1567, 1568, 1569
        acronyms  1529, 1530
    +href="glossaries-user.html#dx1-17018" >1570, 1571
        automake  1531, 1532, 1533
    +href="glossaries-user.html#dx1-10005" >1572, 1573, 1574
            false  1534
    +href="glossaries-user.html#dx1-20088" >1575
        compatible-2.07  1535, 1536, 1537
    +href="glossaries-user.html#dx1-23027" >1576, 1577, 1578
        compatible-3.07  1538, 1539, 1540
    +href="glossaries-user.html#dx1-21004" >1579, 1580, 1581
        counter  1541, 1542, 1543, 1544, 1545
    +href="glossaries-user.html#dx1-19063" >1582, 1583, 1584, 1585, 1586
            page  1546
    +href="glossaries-user.html#dx1-19064" >1587
        counterwithin  1547, 1548, 1549, 1550, 1551
    +href="glossaries-user.html#dx1-19009" >1588, 1589, 1590, 1591, 1592
    +    debug  1593, 1594, 1595
    +        true  1596
        description  1552, 1553, 1554, 1555, 1556, 1557, 1558, 1559, 1560
    +href="glossaries-user.html#dx1-22002" >1597, 1598, 1599, 1600, 1601, 1602, 1603, 1604, 1605
        dua  1561, 1562
    +href="glossaries-user.html#dx1-22011" >1606, 1607
        entrycounter  1563, 1564, 1565, 1566, 1567
    +href="glossaries-user.html#dx1-19001" >1608, 1609, 1610, 1611, 1612
            false  1568
    +href="glossaries-user.html#dx1-19002" >1613
            true  1569
    +href="glossaries-user.html#dx1-19010" >1614
        footnote  1570, 1571, 1572, 1573, 1574, 1575
    +href="glossaries-user.html#dx1-22006" >1615, 1616, 1617, 1618, 1619, 1620
        hyperfirst  1576, 1577, 1578, 1579
    +href="glossaries-user.html#dx1-17078" >1621, 1622, 1623, 1624
    + +         false  1580, 1581, 1582, 1583, 1584
    +href="glossaries-user.html#dx1-17092" >1625, 1626, 1627, 1628, 1629
            true  1585, 1586
    +href="glossaries-user.html#dx1-17079" >1630, 1631
        index  1587, 1588, 1589, 1590, 1591
    +href="glossaries-user.html#dx1-17021" >1632, 1633, 1634, 1635, 1636
        indexonlyfirst  1592, 1593
    +href="glossaries-user.html#dx1-17102" >1637, 1638
            false  1594
    +href="glossaries-user.html#dx1-17103" >1639
        makeindex  1595, 1596, 1597
    +href="glossaries-user.html#dx1-16004" >1640, 1641, 1642
    +    ngerman  1643
        nogroupskip  1598, 1599, 1600, 1601, 1602, 1603, 1604, 1605
    +href="glossaries-user.html#dx1-5020" >1644, 1645, 1646, 1647, 1648, 1649, 1650, 1651
            false  1606
    +href="glossaries-user.html#dx1-19069" >1652
        nohypertypes  1607, 1608, 1609, 1610, 1611, 1612, 1613, 1614, 1615
    +href="glossaries-user.html#dx1-17074" >1653, 1654, 1655, 1656, 1657, 1658, 1659, 1660, 1661
            index  1616
    +href="glossaries-user.html#dx1-23024" >1662
        nolist  1617, 1618, 1619
    +href="glossaries-user.html#dx1-19038" >1663, 1664, 1665
        nolong  1620, 1621, 1622, 1623
    +href="glossaries-user.html#dx1-19030" >1666, 1667, 1668, 1669
        nomain  1624, 1625, 1626, 1627, 1628, 1629, 1630, 1631
    - - +href="glossaries-user.html#dx1-17016" >1670, 1671, 1672, 1673, 1674, 1675, 1676, 1677
        nonumberlist  1632, 1633, 1634, 1635, 1636, 1637, 1638, 1639
    +href="glossaries-user.html#dx1-3047" >1678, 1679, 1680, 1681, 1682, 1683, 1684, 1685
        nopostdot  1640, 1641
    +href="glossaries-user.html#dx1-19066" >1686, 1687
            false  1642
    +href="glossaries-user.html#dx1-19067" >1688
        noredefwarn  1643
    +href="glossaries-user.html#dx1-17004" >1689
        nostyles  1644, 1645, 1646, 1647, 1648, 1649, 1650
    +href="glossaries-user.html#dx1-19046" >1690, 1691, 1692, 1693, 1694, 1695, 1696
        nosuper  1651, 1652, 1653, 1654
    +href="glossaries-user.html#dx1-19034" >1697, 1698, 1699, 1700
        notranslate  1655, 1656, 1657
    +href="glossaries-user.html#dx1-8010" >1701, 1702, 1703
        notree  1658, 1659, 1660, 1661
    +href="glossaries-user.html#dx1-19043" >1704, 1705, 1706, 1707
        nowarn  1662, 1663
    +href="glossaries-user.html#dx1-17001" >1708, 1709, 1710
        numberedsection  1664, 1665, 1666, 1667, 1668
    +href="glossaries-user.html#dx1-18035" >1711, 1712, 1713, 1714, 1715
            autolabel  1669, 1670
    +href="glossaries-user.html#dx1-18039" >1716, 1717
            false  1671
    +href="glossaries-user.html#dx1-18037" >1718
            nameref  1672
    +href="glossaries-user.html#dx1-18045" >1719
            nolabel  1673
    +href="glossaries-user.html#dx1-18038" >1720
        numberline  1674, 1675
    +href="glossaries-user.html#dx1-18004" >1721, 1722
        numbers  1676, 1677, 1678
    +href="glossaries-user.html#dx1-17020" >1723, 1724, 1725
        order  1679, 1680, 1681
    +href="glossaries-user.html#dx1-20045" >1726, 1727, 1728
            letter  1682, 1683, 1684, 1685
    +href="glossaries-user.html#dx1-4060" >1729, 1730, 1731, 1732
            word  1686, 1687, 1688
    +href="glossaries-user.html#dx1-5056" >1733, 1734, 1735
        sanitizesort  1689, 1690, 1691
    +href="glossaries-user.html#dx1-4076" >1736, 1737, 1738
            false  1692, 1693, 1694, 1695, 1696, 1697
    +href="glossaries-user.html#dx1-4006" >1739, 1740, 1741, 1742, 1743, 1744
            true  1698, 1699, 1700, 1701, 1702, 1703, 1704, 1705
    +href="glossaries-user.html#dx1-4008" >1745, 1746, 1747, 1748, 1749, 1750, 1751, 1752
        savenumberlist  1706, 1707
    +href="glossaries-user.html#dx1-17108" >1753, 1754
            false  1708
    +href="glossaries-user.html#dx1-17110" >1755
        savewrites  1709, 1710, 1711
    +href="glossaries-user.html#dx1-17030" >1756, 1757, 1758
            false  1712
    +href="glossaries-user.html#dx1-17031" >1759
        section  1713, 1714
    +href="glossaries-user.html#dx1-18011" >1760, 1761
        seeautonumberlist  1715, 1716, 1717, 1718
    +href="glossaries-user.html#dx1-19054" >1762, 1763, 1764, 1765
    +    seenoindex  1766
    +        ignore  1767
    +        warn  1768
        shortcuts  1719, 1720
    +href="glossaries-user.html#dx1-21026" >1769, 1770
    + +     smallcaps  1721, 1722, 1723, 1724, 1725, 1726
    +href="glossaries-user.html#dx1-22004" >1771, 1772, 1773, 1774, 1775, 1776
        smaller  1727, 1728, 1729, 1730, 1731
    +href="glossaries-user.html#dx1-22005" >1777, 1778, 1779, 1780, 1781
        sort  1732
    +href="glossaries-user.html#dx1-20001" >1782
            def  1733, 1734, 1735, 1736, 1737, 1738, 1739, 1740, 1741, 1742
    +href="glossaries-user.html#dx1-4009" >1783, 1784, 1785, 1786, 1787, 1788, 1789, 1790, 1791, 1792
            standard  1743, 1744, 1745
    +href="glossaries-user.html#dx1-20006" >1793, 1794, 1795
            use  1746, 1747, 1748, 1749, 1750, 1751, 1752, 1753, 1754
    +href="glossaries-user.html#dx1-20005" >1796, 1797, 1798, 1799, 1800, 1801, 1802, 1803, 1804
        style  1755, 1756, 1757, 1758, 1759, 1760, 1761, 1762
    +href="glossaries-user.html#dx1-19024" >1805, 1806, 1807, 1808, 1809, 1810, 1811, 1812
            list  1763
    +href="glossaries-user.html#dx1-19025" >1813
        subentrycounter  1764, 1765, 1766, 1767, 1768, 1769
    +href="glossaries-user.html#dx1-19018" >1814, 1815, 1816, 1817, 1818, 1819
            false  1770
    +href="glossaries-user.html#dx1-19019" >1820
        symbols  1771, 1772, 1773
    +href="glossaries-user.html#dx1-17019" >1821, 1822, 1823
        toc  1774, 1775, 1776, 1777, 1778
    +href="glossaries-user.html#dx1-18001" >1824, 1825, 1826, 1827, 1828
        translate  1779, 1780, 1781, 1782
    +href="glossaries-user.html#dx1-17041" >1829, 1830, 1831, 1832
            babel  1783, 1784, 1785, 1786, 1787, 1788
    +href="glossaries-user.html#dx1-8012" >1833, 1834, 1835, 1836, 1837, 1838
            false  1789, 1790, 1791, 1792
    +href="glossaries-user.html#dx1-8011" >1839, 1840, 1841, 1842
            true  1793, 1794, 1795, 1796
    +href="glossaries-user.html#dx1-17042" >1843, 1844, 1845, 1846
        ucfirst  1797
    - - +href="glossaries-user.html#dx1-18032" >1847
        ucmark  1798, 1799
    +href="glossaries-user.html#dx1-18017" >1848, 1849
            false  1800
    +href="glossaries-user.html#dx1-18020" >1850
            true  1801
    +href="glossaries-user.html#dx1-18022" >1851
        xindy  1802, 1803, 1804, 1805, 1806, 1807, 1808, 1809, 1810, 1811, 1812, 1813, 1814, 1815
    +href="glossaries-user.html#dx1-4049" >1852, 1853, 1854, 1855, 1856, 1857, 1858, 1859, 1860, 1861, 1862, 1863, 1864, 1865
        xindygloss  1816, 1817
    +href="glossaries-user.html#dx1-20070" >1866, 1867
        xindynoglsnumbers  1818, 1819
    +href="glossaries-user.html#dx1-20074" >1868, 1869
    page (counter)  1820
    +href="glossaries-user.html#dx1-56043" >1870
    +page type precedence  1871
    pdflatex  1821, 1822
    +href="glossaries-user.html#dx1-21" >1872, 1873
    \PGLS  1823
    +class="cmti-10">1874
    \Pgls  1824
    +class="cmti-10">1875
    \pgls  1825
    +class="cmti-10">1876
    \PGLSpl  1826
    +class="cmti-10">1877
    \Pglspl  1827
    +class="cmti-10">1878
    \pglspl  1828
    +class="cmti-10">1879
    pod2man  1829
    +href="glossaries-user.html#dx1-11038" >1880
    polyglossia package  1830, 1831, 1832, 1833, 1834, 1835, 1836
    +href="glossaries-user.html#dx1-8002" >1881, 1882, 1883, 1884, 1885, 1886, 1887
    \printacronyms  1837
    +class="cmti-10">1888
    \printglossaries  1838
    +class="cmti-10">1889
    \printglossary  1839
    +class="cmti-10">1890
    \printglossary options
        entrycounter  1840
    +href="glossaries-user.html#dx1-53032" >1891
        nogroupskip  1841
    +href="glossaries-user.html#dx1-53030" >1892
        nonumberlist  1842
    +href="glossaries-user.html#dx1-53029" >1893
        nopostdot  1843
    +href="glossaries-user.html#dx1-53031" >1894
        numberedsection  1844
    +href="glossaries-user.html#dx1-53026" >1895
        style  1845, 1846, 1847, 1848, 1849
    +href="glossaries-user.html#dx1-19050" >1896, 1897, 1898, 1899, 1900
        subentrycounter  1850
    +href="glossaries-user.html#dx1-53034" >1901
        title  1851, 1852, 1853
    +href="glossaries-user.html#dx1-53019" >1902, 1903, 1904
    + +     toctitle  1854
    +href="glossaries-user.html#dx1-53020" >1905
        type  1855, 1856
    +href="glossaries-user.html#dx1-53016" >1906, 1907
    \printindex  1857
    +class="cmti-10">1908
    \printnoidxglossaries  1858
    +class="cmti-10">1909
    \printnoidxglossary  1859
    +class="cmti-10">1910
    \printnoidxglossary options
        sort  1860, 1861, 1862, 1863
    +href="glossaries-user.html#dx1-20002" >1911, 1912, 1913, 1914
    \printnumbers  1864
    +class="cmti-10">1915
    \printsymbols  1865
    +class="cmti-10">1916
    \provideglossaryentry  1866
    +class="cmti-10">1917

    R relsize package  1867, 1868
    +href="glossaries-user.html#dx1-22019" >1918, 1919

    S sanitize  1869, 1870, 1871, 1872, 1873
    - - +class="cmbx-10">1920, 1921, 1922, 1923, 1924
    scrwfile package  1874
    +href="glossaries-user.html#dx1-17034" >1925
    \SetAcronymLists  1875
    +class="cmti-10">1926
    \setacronymstyle  1876
    +class="cmti-10">1927
    \setglossarypreamble  1877
    +class="cmti-10">1928
    \setglossarysection  1878
    +class="cmti-10">1929
    \setglossarystyle  1879
    +class="cmti-10">1930
    \setStyleFile  1880
    +class="cmti-10">1931
    \setupglossaries  1881
    +class="cmti-10">1932
    \subglossentry  1882
    +class="cmti-10">1933
    supertabular package  1883, 1884, 1885
    +href="glossaries-user.html#dx1-19036" >1934, 1935, 1936

    T textcase package  1886, 1887, 1888
    +href="glossaries-user.html#dx1-6" >1937, 1938, 1939
    theglossary (environment)  1889
    +class="cmti-10">1940
    tracklang package  1890, 1891, 1892
    +href="glossaries-user.html#dx1-2" >1941, 1942, 1943
    translator package  1893, 1894, 1895, 1896, 1897, 1898, 1899, 1900, 1901, 1902, 1903, 1904, 1905, 1906, 1907, 1908, 1909, 1910, 1911, 1912, 1913, 1914, 1915, 1916, 1917
    +href="glossaries-user.html#dx1-8009" >1944, 1945, 1946, 1947, 1948, 1949, 1950, 1951, 1952, 1953, 1954, 1955, 1956, 1957, 1958, 1959, 1960, 1961, 1962, 1963, 1964, 1965, 1966, 1967, 1968

    X xfor package  1918
    +href="glossaries-user.html#dx1-7" >1969
    xindy  1919, 1920, 1921, 1970, 1971, 1972, 1922, 1923, 1924, 1925, 1926, 1927, 1928, 1929, 1930, 1931, 1932, 1933, 1934, 1935, 1936, 1937, 1938, 1939, 1940, 1941, 1942, 1943, 1944, 1945, 1946, 1947, 1948, 1949, 1950, 1951, 1952, 1953, 1954, 1955, 1956, 1957, 1958, 1959, 1960, 1961, 1962, 1963, 1964, 1965, 1966, 1967, 1968, 1969, 1970, 1971, 1972, 1973, 1974, 1975, 1976, 1977, 1978, 1979, 1980, 1981, 1982, 1983, 1984, 1985, 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025, 2026, 2027, 2028, 2029, 2030, 2031, 2032, 2033, 2034, 2035, 2036, 2037, 2038, 2039, 2040, 2041, 2042, 2043, 2044, 2045, 2046, 2047, 2048, 2049, 2050, 2051, 2052, 2053, 2054, 2055
    +class="cmbx-10">1973, 1974, 1975, 1976, 1977, 1978, 1979, 1980, 1981, 1982, 1983, 1984, 1985, 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025, 2026, 2027, 2028, 2029, 2030, 2031, 2032, 2033, 2034, 2035, 2036, 2037, 2038, 2039, 2040, 2041, 2042, 2043, 2044, 2045, 2046, 2047, 2048, 2049, 2050, 2051, 2052, 2053, 2054, 2055, 2056, 2057, 2058, 2059, 2060, 2061, 2062, 2063, 2064, 2065, 2066, 2067, 2068, 2069, 2070, 2071, 2072, 2073, 2074, 2075, 2076, 2077, 2078, 2079, 2080, 2081, 2082, 2083, 2084, 2085, 2086, 2087, 2088, 2089, 2090, 2091, 2092, 2093, 2094, 2095, 2096, 2097, 2098, 2099, 2100, 2101, 2102, 2103, 2104, 2105, 2106, 2107, 2108, 2109
    +    -C  2110, 2111, 2112, 2113, 2114
    +    -I  2115, 2116
    +    -L  2117, 2118, 2119, 2120
    +    -M  2121
    + + xkeyval package  2056, 2057, 2058
    +href="glossaries-user.html#dx1-5" >2122, 2123, 2124
    xspace package  2059, 2060, 2061, 2062, 2063, 2064, 2065
    +href="glossaries-user.html#dx1-64014" >2125, 2126, 2127, 2128, 2129, 2130, 2131

    - - -

    1.1That is, if the term has been referenced using any of the commands described in commands such as \acrshort.

    -

    1.2Note that although I’ve written latex the reasons given earlier.

    -

    1.3Added to version makeglossaries 2.18.

    -

    1.4As from v3.01 \gls is no longer fragile and doesn’t need protecting.

    -

    2.1bug fix in v4.16 has corrected the code to ensure this.

    -

    2.2unless memoirmemoiris loaded, which case it uses \markboth

    -

    2.3Actually it uses \mfirstucMakeUppercasepackage is automatically loaded by glossaries.)

    -

    2.4Actually it sets \acronymtypeunless the nomain option has been used.

    -

    4.1The glossaries-extra package provides a simpler way of achieving this.

    -

    4.2This is because \acronymtypeacronym package option is not used.

    used.

    5.1This feature was introduced in makeglossaries version 2.18.

    -

    6.1I’ve used \MakeUppercase in all the examples for clarity, but it will actually use \mfirstucMakeUppercase.

    -

    6.2\glsdisplayfirst but you may need to use the compatible-3.07 option

    -

    8.1makeindex will always assign a location number, even if it’s not needed, so it needs to be discarded.

    discarded.

    8.2If you redefine \glsseeformat[\seename] in the output file if no optional argument is given.

    -

    8.3In versions before 3.0, \glsentryname key was href="#glo:sanitize">sanitized.

    .

    9.1versions before 3.0 used \glsentrynamebeen sanitized.

    .

    10.1you can’t use the longheaderborderlongtable environment in two column mode.

    two column mode.

    11.1see \setCompositor described in §3 Setting Up

    -

    11.2see \setAlphaCompositor described in §3 Setting Up

    -

    13.1as from version 1.18

    as from version 1.18

    13.2See David Carlisle’sexplanation in http://tex.stackexchange.com/questions/86565/drawbacks-of-xspace

    -

    15.1These lengths will not be available if you use both the nolonguse the nostyles package option unless you explicitly load the relevant package.

    -

    15.2This style was supplied by Axel Menzel.

    -

    15.3e.g. with the flowfram package.

    -

    17.1Single letter words, such as “a” and “I” should typically not appear at the end of a line, hence the non-breakable space after “a” in the prefix field.

    -

    17.2The earlier caveats about initial non-Latin characters apply.

    diff --git a/Master/texmf-dist/doc/latex/glossaries/glossaries-user.pdf b/Master/texmf-dist/doc/latex/glossaries/glossaries-user.pdf index b1026f069d8..e40c4d642ec 100644 Binary files a/Master/texmf-dist/doc/latex/glossaries/glossaries-user.pdf and b/Master/texmf-dist/doc/latex/glossaries/glossaries-user.pdf differ diff --git a/Master/texmf-dist/doc/latex/glossaries/glossaries-user.tex b/Master/texmf-dist/doc/latex/glossaries/glossaries-user.tex index c955082e67c..8ef6883f0ad 100644 --- a/Master/texmf-dist/doc/latex/glossaries/glossaries-user.tex +++ b/Master/texmf-dist/doc/latex/glossaries/glossaries-user.tex @@ -151,7 +151,8 @@ text={\appfmt{makeglossariesgui}\iapp{makeglossariesgui}}% }% {% A Java GUI alternative to \gls{makeglossaries} that - also provides diagnostic tools. Available separately on CTAN. + also provides diagnostic tools. Available separately on + \href{http://ctan.org/pkg/makeglossariesgui}{CTAN}. } \newglossaryentry{numberlist}{% @@ -359,6 +360,12 @@ and~\hyperlink{option#2}{#2}} \newcommand*{\locfmt}[1]{\texttt{#1}\SpecialMainIndex{#1}} \newcommand*{\mkidxspch}{\index{makeindex=\appfmt{makeindex}>special characters|hyperpage}} +\newcommand*{\mkidxopt}[1]{\texttt{-#1}\index{makeindex=\appfmt{makeindex}>#1=\texttt{-#1}|hyperpage}} + +\newcommand*{\xdyopt}[1]{\texttt{-#1}\index{xindy=\appfmt{xindy}>#1=\texttt{-#1}|hyperpage}} + +\newcommand*{\mkglsopt}[1]{\texttt{-#1}\index{makeglossaries=\appfmt{makeglossaries}>#1=\texttt{-#1}|hyperpage}} + \newcommand*{\igloskey}[2][newglossaryentry]{\icsopt{#1}{#2}} \newcommand*{\gloskey}[2][newglossaryentry]{\csopt{#1}{#2}} @@ -388,11 +395,11 @@ and~\hyperlink{option#2}{#2}} \MakeShortVerb{"} \DeleteShortVerb{\|} - \title{User Manual for glossaries.sty v4.23} + \title{User Manual for glossaries.sty v4.25} \author{Nicola L.C. Talbot\\% \url{http://www.dickimaw-books.com/}} - \date{2016-04-30} + \date{2016-06-09} \maketitle \begin{abstract} @@ -404,8 +411,8 @@ generated either using \TeX\ or using a supplementary \gls{indexingapp}. Additional features not provided here may be available through the supplemental package \gls{glossaries-extra} which, if required, needs to be installed separately. New features will be added to -\gls*{glossaries-extra}. Any new versions of the \styfmt{glossaries} -package after v4.21 will be just bug fixes. +\gls*{glossaries-extra}. Versions of the \styfmt{glossaries} +package after v4.21 will mostly be just bug fixes. \end{abstract} If you require multilingual support you must also separately install @@ -470,7 +477,7 @@ package. \item[\url{glossaries-code.pdf}] Advanced users wishing to know more about the inner workings of all the packages provided in the \styfmt{glossaries} bundle should read -\qt{Documented Code for glossaries v4.23}. +\qt{Documented Code for glossaries v4.25}. \item[INSTALL] Installation instructions. @@ -622,6 +629,17 @@ option is intended as a last resort for alphabetical sorting.} English alphabet and you don't want to install Perl. \begin{enumerate} + \item If you want to use \gls{makeindex}['s] \mkidxopt{g} option + you must change the quote character using \ics{GlsSetQuote}. For +example: +\begin{verbatim} +\GlsSetQuote{+} +\end{verbatim} + This must be used before \cs{makeglossaries}. + Note that if you are using \sty{babel}, the shorthands aren't + enabled until the start of the document, so you won't be able to use + the shorthands in definitions made in the preamble. + \item Add \cs{makeglossaries} to your preamble (before you start defining your entries, as described in \sectionref{sec:newglosentry}). @@ -658,7 +676,7 @@ makeindex -s myDoc.ist -o myDoc.gls myDoc.glo The default sort is word order (\qt{sea lion} comes before \qt{seal}). - If you want letter ordering you need to add the \texttt{-l} + If you want letter ordering you need to add the \mkidxopt{l} switch: \begin{verbatim} makeindex -l -s myDoc.ist -o myDoc.gls myDoc.glo @@ -723,8 +741,8 @@ xindy -L english -C utf8 -I xindy -M myDoc (Replace \texttt{myDoc} with the base name of your \LaTeX\ document file. Avoid spaces in the file name. If necessary, also replace \texttt{english} with the name of your language and \texttt{utf8} - with your input encoding, for example, \texttt{-L german -C - din5007-utf8}.) If you don't know + with your input encoding, for example, + \xdyopt{L}\texttt{ german }\xdyopt{C}\texttt{ din5007-utf8}.) If you don't know how to use the command prompt, then you can probably access \gls{xindy} via your text editor, but each editor has a different method of doing this, so I~can't give a~general @@ -1145,7 +1163,7 @@ You can see the difference between word and letter ordering if you substitute \pkgopt[word]{order} with \pkgopt[letter]{order}. (Note that this will only have an effect if you use \gls{makeglossaries}. If you use \gls{makeindex} explicitly, -you will need to use the \texttt{-l} switch to indicate letter +you will need to use the \mkidxopt{l} switch to indicate letter ordering.) \exitem{-inline} This document is @@ -1462,9 +1480,85 @@ description=\verb|{select group or class}}| If you use the \sty{inputenc} package, \gls{makeglossaries} will pick up the encoding from the auxiliary file. If you use \gls{xindy} explicitly instead of via \gls*{makeglossaries}, -you may need to specify the encoding using the \texttt{-C} +you may need to specify the encoding using the \xdyopt{C} option. Read the \gls*{xindy} manual for further details. +As from v4.24, if you are writing in German (for example, using the \sty{ngerman} +package or \sty{babel} with the \pkgopt{ngerman} package option), +and you want to use \gls{makeindex}['s] \mkidxopt{g} option, you'll +need to change \gls{makeindex}['s] quote character using: +\begin{definition}[\DescribeMacro\GlsSetQuote] +\cs{GlsSetQuote}\marg{character} +\end{definition} +Note that \meta{character} may not be one of \verb"?" (question +mark), \verb"|" (pipe) or \verb"!" (exclamation mark). +For example: +\begin{verbatim} +\GlsSetQuote{+} +\end{verbatim} +This must be done before \ics{makeglossaries} and any entry +definitions. It's only applicable for \app{makeindex}. This option +in conjunction with \sty{ngerman} will also cause +\app{makeglossaries} to use the \mkidxopt{g} switch when invoking +\app{makeindex}. + +\begin{important} +Be careful of \sty{babel}'s shorthands. These aren't switched +on until the start of the document, so any entries defined +in the preamble won't be able to use those shorthands. +However, if you define the entries in the document and any +of those shorthands happen to be special characters for +\gls{makeindex} or \gls{xindy} (such as the double-quote) +then this will interfere with code that tries to escape +any of those characters that occur in the \gloskey{sort} key. +\end{important} + +In general, it's best not to use \sty{babel}'s shorthands +in entry definitions. For example: +\begin{verbatim} +\documentclass{article} + +\usepackage[ngerman]{babel} +\usepackage{glossaries} + +\GlsSetQuote{+} + +\makeglossaries + +\newglossaryentry{rna}{name={ribonukleins\"aure}, + sort={ribonukleins"aure}, + description={eine Nukleins\"aure}} + +\begin{document} +\gls{rna} + +\printglossaries +\end{document} +\end{verbatim} + +The \sty{ngerman} package has the shorthands on in the preamble, so +they can be used if \cs{GlsSetQuote} has changed the \gls{makeindex} +quote character. Example: +\begin{verbatim} +\documentclass{article} + +\usepackage[ngerman]{babel} +\usepackage{glossaries} + +\GlsSetQuote{+} + +\makeglossaries + +\newglossaryentry{rna}{name={ribonukleins"aure}, + description={eine Nukleins"aure}} + +\begin{document} +\gls{rna} + +\printglossaries +\end{document} +\end{verbatim} + \subsection{Changing the Fixed Names} \label{sec:fixednames} @@ -1938,6 +2032,9 @@ file and see if you can work it out from the \gls*{makeindex} or problem.\footnote{Added to version \gls{makeglossaries} 2.18.} Since \gls{xindy} doesn't warn about this, this correction is only provided by \gls{makeglossaries} when \gls{makeindex} is used. +(\gls{xindy} uses the order of the attributes list to determine +which format should take precedence. See \cs{GlsAddXdyAttribute} in +\sectionref{sec:xindyloc}.) \end{itemize} @@ -1951,6 +2048,12 @@ a~Lua interpreter) you don't need to install anything else in order to use \gls{makeglossaries-lite.lua} so it's an alternative to \gls{makeglossaries} if you want to use \opt2 (\gls{makeindex}). +If things go wrong and you can't work out why your glossaries +aren't being generated correctly, you can use +\gls{makeglossariesgui} as a diagnostic tool. Once you've +fixed the problem, you can then go back to using +\gls{makeglossaries} or \gls{makeglossaries-lite.lua}. + Whilst I strongly recommended that you use the \gls{makeglossaries} Perl script or the \gls{makeglossaries-lite.lua} Lua script, it is possible to use the \styfmt{glossaries} package without using those @@ -2041,15 +2144,15 @@ using \gls{xindy} or \gls{makeindex} explicitly} \begin{tabular}{@{}lll@{}} \bfseries Command or Package Option & \gls{makeindex} & \gls{xindy}\\ -\pkgopt[letter]{order} & use \texttt{-l} & - use \texttt{-M ord/letorder}\\ +\pkgopt[letter]{order} & use \mkidxopt{l} & + use \xdyopt{M}\texttt{ ord/letorder}\\ \pkgopt[word]{order} & default & default\\ \pkgopt{xindy}=\{\pkgoptfmt{language=}\meta{lang}\pkgoptfmt{,codename=}\meta{code}\} & -N/A & use \texttt{-L} \meta{lang} \texttt{-C} \meta{code}\\ +N/A & use \xdyopt{L} \meta{lang} \xdyopt{C} \meta{code}\\ \ics{GlsSetXdyLanguage}\marg{lang} & N/A & -use \texttt{-L} \meta{lang}\\ +use \xdyopt{L} \meta{lang}\\ \ics{GlsSetXdyCodePage}\marg{code} & N/A & -use \texttt{-C} \meta{code} +use \xdyopt{C} \meta{code} \end{tabular} \par \end{table} @@ -2103,10 +2206,10 @@ help diagnose problems. If this method fails \gls{makeglossaries} will print an \qt{Unable to fork} warning and will retry without redirection. If you run \gls{makeglossaries} on an operating system that doesn't support this form of redirection, then you can use the -\texttt{-Q} switch to suppress this warning or you can use the -\texttt{-k} switch to make \gls{makeglossaries} automatically use +\mkglsopt{Q} switch to suppress this warning or you can use the +\mkglsopt{k} switch to make \gls{makeglossaries} automatically use the fallback method without attempting the redirection. Without this -redirection, the \texttt{-q} (quiet) switch doesn't work as well. +redirection, the \mkglsopt{q} (quiet) switch doesn't work as well. You can specify in which directory the \filetype{.aux}, \filetype{.glo} etc files are located using the \texttt{-d} switch. @@ -2118,8 +2221,8 @@ makeglossaries -d myTmpDir myDoc Note that \gls*{makeglossaries} assumes by default that \gls*{makeindex}\slash\gls*{xindy} is on your operating system's path. If this isn't the case, you can specify the full pathname -using \texttt{-m} \meta{path/to/makeindex} for \gls*{makeindex} -or \texttt{-x} \meta{path/to/xindy} for \gls*{xindy}. +using \mkglsopt{m} \meta{path/to/makeindex} for \gls*{makeindex} +or \mkglsopt{x} \meta{path/to/xindy} for \gls*{xindy}. As from \gls{makeglossaries} v2.18, if you are using \gls{makeindex}, there's a check for \gls*{makeindex}['s] multiple @@ -2156,7 +2259,7 @@ resulting file onto the man path. Alternatively do \begin{important} When upgrading the \styfmt{glossaries} package, make sure you also upgrade your version of \gls{makeglossaries}. The current version is -2.18. +2.19. \end{important} \subsection{Using the makeglossaries-lite.lua Lua Script} @@ -2170,7 +2273,7 @@ light-weight it doesn't have the full-functionality of heavy-weight scripting languages, such as Perl. The \gls{makeglossaries-lite.lua} script is therefore limited by this and some of the options available to the \gls{makeglossaries} Perl script aren't available -here. (In particular the \texttt{-d} option.) +here. (In particular the \mkglsopt{d} option.) The \gls{makeglossaries-lite.lua} script can be invoked in the same way as \gls{makeglossaries} but you need to remember the \texttt{.lua} @@ -2208,7 +2311,7 @@ This is required regardless of whether you use \gls{xindy} explicitly or whether it's called implicitly via applications such as \gls{makeglossaries} or \gls{makeglossariesgui}. This causes the glossary entries to be written in raw \gls*{xindy} format, so you need to -use \texttt{-I xindy} \emph{not} \texttt{-I tex}. +use \xdyopt{I}\texttt{ xindy} \emph{not} \xdyopt{I}\texttt{ tex}. To run \gls{xindy} type the following in your terminal (all on one line): @@ -2274,7 +2377,7 @@ where \meta{base} is the name of your document without the name of the \gls{makeindex} style file. By default, this is \meta{base}\filetype{.ist}, but may be changed via \ics{setStyleFile}\marg{style}. Note that there are other options, -such as \texttt{-l} (letter ordering). See the \gls*{makeindex} +such as \mkidxopt{l} (letter ordering). See the \gls*{makeindex} manual for further details. For example, if your document is called \texttt{myDoc.tex}, then @@ -2393,6 +2496,7 @@ package. Options that aren't \meta{key}=\meta{value} (such as the \styfmt{glossaries} package. Don't use this option if you're new to using \styfmt{glossaries} as the warnings are designed to help detect common mistakes (such as forgetting to use \ics{makeglossaries}). +Note that the \pkgopt[true]{debug} will override this option. \item[\pkgopt{noredefwarn}] If you load \styfmt{glossaries} with a~class or another package that already defines glossary related @@ -2403,6 +2507,65 @@ want to be warned about it, use this option to suppress those warnings. Other warnings will still be issued unless you use the \pkgopt{nowarn} option described above. +\item[\pkgopt{debug}] Introduced in version 4.24, this boolean +option switches on the debug mode. Note that the debug mode will automatically +cancel the \pkgopt{nowarn} option. Consider the following example +document: +\begin{verbatim} +\documentclass{article} +\usepackage{glossaries} +\newglossaryentry{sample1}{name={sample1},description={example}} +\newglossaryentry{sample2}{name={sample2},description={example}} +\glsadd{sample2} +\makeglossaries +\begin{document} +\gls{sample1}. +\printglossaries +\end{document} +\end{verbatim} +Here, only the \texttt{sample1} entry has been indexed, even +though \verb|\glsadd{sample2}| appears in the source code. +This is because the associated file is opened by +\ics{makeglossaries}, but \verb|\glsadd{sample2}| has been used +before this command. Since the file isn't open yet, the +information can't be written to it, which is why the +\texttt{sample2} entry doesn't appear in the glossary. + +This situation doesn't cause any errors or warnings as it's +perfectly legitimate for a user to want to use \styfmt{glossaries} +to format the entries (e.g.\ abbreviation expansion) but not display +any lists of terms, abbreviations, symbols etc. +Without \cs{makeglossaries} (or \cs{makenoidxglossaries}) +the indexing is suppressed but, other than that, commands +like \cs{gls} behave as usual. + +The debug mode, enabled with the \pkgopt{debug} option, +will write information to the log file when the indexing +can't occur because the associated file isn't open. +The message is written in the form +\begin{quote} +Package glossaries Info: wrglossary(\meta{type})(\meta{line}) on +input line \meta{line number}. +\end{quote} +where \meta{type} is the glossary label and \meta{line} is the line +of text that would've been written to the associated file if +it had been open. So if any entries haven't appeared in the +glossary but you're sure you used commands like \cs{glsadd} +or \cs{glsaddall}, try switching on the \pkgopt{debug} option +and see if any information has been written to the log file. + +\item[\pkgopt{seenoindex}] Introduced in version 4.24, this option +may take one of three values: \pkgoptfmt{error}, \pkgoptfmt{warn} or +\pkgoptfmt{ignore}. The \gloskey{see} key automatically indexes the +cross-referenced entry using \cs{glsadd}. This means that it suffers +from the same problem as the above. If used before the relevant +glossary file has been opened, the indexing can't be performed. +Since this is easy to miss, the \styfmt{glossaries} package by +default issues an error message if the \gloskey{see} key is used +before \cs{makeglossaries}. This option allows you to change the +error into just a warning (\pkgopt[warn]{seenoindex}) or +ignore it (\pkgopt[ignore]{seenoindex}). + \item[\pkgopt{nomain}] This suppresses the creation of the main glossary and associated \texttt{.glo} file, if unrequired. Note that if you use this option, you must create another glossary in which to @@ -3768,8 +3931,12 @@ list}\marg{long description} (These are both preamble-only commands.) For all the above commands, the first argument, \meta{label}, must be -a~unique label with which to identify this entry. This can't contain -any non-expandable commands or active characters. +a~unique label with which to identify this entry. \textbf{This can't contain +any non-expandable commands or active characters.} The reason for +this restriction is that the label is used to construct internal commands +that store the associated information (similarly to commands +like \cs{label}) and therefore must be able to expand to a valid +control sequence name. \begin{important} Note that although an \gls{exlatinchar} or other \gls{nonlatinchar}, @@ -5216,6 +5383,31 @@ which is described in \sectionref{sec:customxr}. \cs{glsnumberlistloop} is not available for \optsand23. \end{important} +As from version 4.24, there's a hook that's used near the end of +\ics{writeist} before the file is closed. You can set the code +to be performed then using: +\begin{definition}[\DescribeMacro\GlsSetWriteIstHook] +\cs{GlsSetWriteIstHook}\marg{code} +\end{definition} +If you want the \meta{code} to write any information to the +file, you need to use +\begin{definition}[\DescribeMacro\glswrite] +\cs{write}\cs{glswrite}\marg{style information} +\end{definition} +Make sure you use the correct format within \meta{style +information}. For example, if you are using \app{makeindex}: +\begin{verbatim} +\GlsSetWriteIstHook{% + \write\glswrite{page_precedence "arnAR"}% + \write\glswrite{line_max 80}% +} +\end{verbatim} +This changes the page type precedence\index{page type precedence} and the maximum line length +used by \app{makeindex}. + +Remember that if you switch to \app{xindy}, this will no longer be +valid code. + \chapter{Links to Glossary Entries} \label{sec:glslink} @@ -7220,6 +7412,11 @@ will appear in the normal font. The hierarchical glossary styles (defined in the \sty{glossary-tree} style file) also set the name in bold. +If you want to change the font for the description, or if you +only want to change the name font for some types of entries +but not others, you might want to consider using the +\sty{glossaries-extra} package. + \begin{example}{Changing the Font Used to Display Entry Names in the Glossary}{ex:glsnamefont} Suppose you want all the entry names to appear in @@ -7349,7 +7546,7 @@ The commands \cs{GlsSetXdyLanguage} and \cs{GlsSetXdyCodePage} have no effect if you don't use \gls{makeglossaries}. If you call \gls{xindy} without \gls*{makeglossaries} you need to remember to set the language and encoding using the -\texttt{-L} and \texttt{-C} switches. +\xdyopt{L} and \xdyopt{C} switches. \end{important} \section{Locations and Number lists} @@ -7378,6 +7575,23 @@ attribute, you need to add it using: where \meta{name} is the name of the attribute, as used in the \gloskey[glslink]{format} key. +Take care if you have multiple instances of the same location with +different formats. The duplicate locations will be discarded +according to the order in which the attributes are listed. Consider +defining semantic commands to use for primary references. For +example: +\begin{verbatim} +\newcommand*{\primary}[1]{\textbf{#1}} +\GlsAddXdyAttribute{primary} +\end{verbatim} +Then in the document: +\begin{verbatim} +A \gls[format=primary]{duck} is an aquatic bird. +There are lots of different types of \gls{duck}. +\end{verbatim} +This will give the \verb|format=primary| instance preference over +the next use that doesn't use the \gloskey[glslink]{format} key. + \begin{example}{Custom Font for Displaying a Location}{ex:hyperbfit} Suppose I want a bold, italic, hyperlinked location. I first need to define a command that will do this: @@ -7764,6 +7978,10 @@ argument. The \cs{newacronym} command also uses the \gloskey{long}, in \cs{newglossaryentry} to store the long and abbreviated forms and their plurals. +Note that the same restrictions on the entry \meta{label} +in \ics{newglossaryentry} also apply to \cs{newacronym} +(see \sectionref{sec:newglosentry}). + \begin{important} If you haven't identified the specified glossary type as a list of acronyms (via the package option diff --git a/Master/texmf-dist/doc/latex/glossaries/glossariesbegin.html b/Master/texmf-dist/doc/latex/glossaries/glossariesbegin.html index 35bb2428f90..eda478fcee2 100644 --- a/Master/texmf-dist/doc/latex/glossaries/glossariesbegin.html +++ b/Master/texmf-dist/doc/latex/glossaries/glossariesbegin.html @@ -10,7 +10,7 @@ - +