Is there a command similar to nocite(*) for gls (glossaries) and is there a glossary package similar to...
up vote
1
down vote
favorite
I use the class memoir and compile in XeLaTeX.
I would like to print glossaries in a separated file and to ignore all gls. I do not write any gls in anywhere. Similar to nocite{*}. Also similar to Tobias Oetiker's acronym.sty.
Imagine like:
documentclass{memoir}
usepackage{glossaries}
begin{document}
nogls(*)
include{gloassries.tex}
end{document}
The separated file glossaries.tex:
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs operating-system-level virtualization, also known as "containerization".}
}
Derived from Tobias' acronym.sty, imagine like:
documentclass{memoir}
usepackage{glossaries}
begin{document}
include{gloassries.tex}
end{document}
The separated file glossaries.tex
chapter*{Glossaries}
addcontentsline{toc}{chapter}{Glossaries}
markboth{GLOSSARIES}{GLOSSARIES}
begin{glossary}
{small
glo{Cloud}{shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
glo{Docker}{a computer program that performs operating-system-level virtualization, also known as "containerization".}
}
end{glossary}
Is it possible?
Update
Because I searched for the questions, tried all the codes and they did not work. Here is the MWE:
documentclass[12pt, a4paper, oneside, oldfontcommands, dvipsnames]{memoir}
usepackage{acronym}
usepackage{glossaries}
makeglossaries
begin{document}
tableofcontents
include{acronimos}
clearpage
glsaddall
input{capitulos/glossario.tex}
printglossaries
backmatter
nocite{*}
begin{raggedright}
printbibliography
end{raggedright}
end{document}
Update 2
I also have moved to the preamble but it did not work:
documentclass[12pt, a4paper, oneside, oldfontcommands, dvipsnames]{memoir}
usepackage{acronym}
usepackage{glossaries}
makeglossaries
input{capitulos/glossario.tex}
begin{document}
tableofcontents
include{acronimos}
clearpage
glsaddall
printglossaries
backmatter
nocite{*}
begin{raggedright}
printbibliography
end{raggedright}
end{document}
xetex memoir glossaries
|
show 8 more comments
up vote
1
down vote
favorite
I use the class memoir and compile in XeLaTeX.
I would like to print glossaries in a separated file and to ignore all gls. I do not write any gls in anywhere. Similar to nocite{*}. Also similar to Tobias Oetiker's acronym.sty.
Imagine like:
documentclass{memoir}
usepackage{glossaries}
begin{document}
nogls(*)
include{gloassries.tex}
end{document}
The separated file glossaries.tex:
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs operating-system-level virtualization, also known as "containerization".}
}
Derived from Tobias' acronym.sty, imagine like:
documentclass{memoir}
usepackage{glossaries}
begin{document}
include{gloassries.tex}
end{document}
The separated file glossaries.tex
chapter*{Glossaries}
addcontentsline{toc}{chapter}{Glossaries}
markboth{GLOSSARIES}{GLOSSARIES}
begin{glossary}
{small
glo{Cloud}{shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
glo{Docker}{a computer program that performs operating-system-level virtualization, also known as "containerization".}
}
end{glossary}
Is it possible?
Update
Because I searched for the questions, tried all the codes and they did not work. Here is the MWE:
documentclass[12pt, a4paper, oneside, oldfontcommands, dvipsnames]{memoir}
usepackage{acronym}
usepackage{glossaries}
makeglossaries
begin{document}
tableofcontents
include{acronimos}
clearpage
glsaddall
input{capitulos/glossario.tex}
printglossaries
backmatter
nocite{*}
begin{raggedright}
printbibliography
end{raggedright}
end{document}
Update 2
I also have moved to the preamble but it did not work:
documentclass[12pt, a4paper, oneside, oldfontcommands, dvipsnames]{memoir}
usepackage{acronym}
usepackage{glossaries}
makeglossaries
input{capitulos/glossario.tex}
begin{document}
tableofcontents
include{acronimos}
clearpage
glsaddall
printglossaries
backmatter
nocite{*}
begin{raggedright}
printbibliography
end{raggedright}
end{document}
xetex memoir glossaries
1
glsaddall, see the documentation. And better don't use include but input.
– Ulrike Fischer
Nov 29 at 13:16
Then it does not work either.
– Gustavo Reis
Nov 29 at 13:25
Do you load the glossaries definitions before the command?
– Ulrike Fischer
Nov 29 at 13:31
Yes, it does. I will upload the post
– Gustavo Reis
Nov 29 at 13:33
1
And now you will have to runxelatex > biber > makeglossaries > xelatex(if you want some sorting, for simpler output variants see Nicola's answer and the documentation).
– Ulrike Fischer
Nov 29 at 13:59
|
show 8 more comments
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I use the class memoir and compile in XeLaTeX.
I would like to print glossaries in a separated file and to ignore all gls. I do not write any gls in anywhere. Similar to nocite{*}. Also similar to Tobias Oetiker's acronym.sty.
Imagine like:
documentclass{memoir}
usepackage{glossaries}
begin{document}
nogls(*)
include{gloassries.tex}
end{document}
The separated file glossaries.tex:
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs operating-system-level virtualization, also known as "containerization".}
}
Derived from Tobias' acronym.sty, imagine like:
documentclass{memoir}
usepackage{glossaries}
begin{document}
include{gloassries.tex}
end{document}
The separated file glossaries.tex
chapter*{Glossaries}
addcontentsline{toc}{chapter}{Glossaries}
markboth{GLOSSARIES}{GLOSSARIES}
begin{glossary}
{small
glo{Cloud}{shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
glo{Docker}{a computer program that performs operating-system-level virtualization, also known as "containerization".}
}
end{glossary}
Is it possible?
Update
Because I searched for the questions, tried all the codes and they did not work. Here is the MWE:
documentclass[12pt, a4paper, oneside, oldfontcommands, dvipsnames]{memoir}
usepackage{acronym}
usepackage{glossaries}
makeglossaries
begin{document}
tableofcontents
include{acronimos}
clearpage
glsaddall
input{capitulos/glossario.tex}
printglossaries
backmatter
nocite{*}
begin{raggedright}
printbibliography
end{raggedright}
end{document}
Update 2
I also have moved to the preamble but it did not work:
documentclass[12pt, a4paper, oneside, oldfontcommands, dvipsnames]{memoir}
usepackage{acronym}
usepackage{glossaries}
makeglossaries
input{capitulos/glossario.tex}
begin{document}
tableofcontents
include{acronimos}
clearpage
glsaddall
printglossaries
backmatter
nocite{*}
begin{raggedright}
printbibliography
end{raggedright}
end{document}
xetex memoir glossaries
I use the class memoir and compile in XeLaTeX.
I would like to print glossaries in a separated file and to ignore all gls. I do not write any gls in anywhere. Similar to nocite{*}. Also similar to Tobias Oetiker's acronym.sty.
Imagine like:
documentclass{memoir}
usepackage{glossaries}
begin{document}
nogls(*)
include{gloassries.tex}
end{document}
The separated file glossaries.tex:
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs operating-system-level virtualization, also known as "containerization".}
}
Derived from Tobias' acronym.sty, imagine like:
documentclass{memoir}
usepackage{glossaries}
begin{document}
include{gloassries.tex}
end{document}
The separated file glossaries.tex
chapter*{Glossaries}
addcontentsline{toc}{chapter}{Glossaries}
markboth{GLOSSARIES}{GLOSSARIES}
begin{glossary}
{small
glo{Cloud}{shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
glo{Docker}{a computer program that performs operating-system-level virtualization, also known as "containerization".}
}
end{glossary}
Is it possible?
Update
Because I searched for the questions, tried all the codes and they did not work. Here is the MWE:
documentclass[12pt, a4paper, oneside, oldfontcommands, dvipsnames]{memoir}
usepackage{acronym}
usepackage{glossaries}
makeglossaries
begin{document}
tableofcontents
include{acronimos}
clearpage
glsaddall
input{capitulos/glossario.tex}
printglossaries
backmatter
nocite{*}
begin{raggedright}
printbibliography
end{raggedright}
end{document}
Update 2
I also have moved to the preamble but it did not work:
documentclass[12pt, a4paper, oneside, oldfontcommands, dvipsnames]{memoir}
usepackage{acronym}
usepackage{glossaries}
makeglossaries
input{capitulos/glossario.tex}
begin{document}
tableofcontents
include{acronimos}
clearpage
glsaddall
printglossaries
backmatter
nocite{*}
begin{raggedright}
printbibliography
end{raggedright}
end{document}
xetex memoir glossaries
xetex memoir glossaries
edited Nov 29 at 13:46
asked Nov 29 at 13:05
Gustavo Reis
505
505
1
glsaddall, see the documentation. And better don't use include but input.
– Ulrike Fischer
Nov 29 at 13:16
Then it does not work either.
– Gustavo Reis
Nov 29 at 13:25
Do you load the glossaries definitions before the command?
– Ulrike Fischer
Nov 29 at 13:31
Yes, it does. I will upload the post
– Gustavo Reis
Nov 29 at 13:33
1
And now you will have to runxelatex > biber > makeglossaries > xelatex(if you want some sorting, for simpler output variants see Nicola's answer and the documentation).
– Ulrike Fischer
Nov 29 at 13:59
|
show 8 more comments
1
glsaddall, see the documentation. And better don't use include but input.
– Ulrike Fischer
Nov 29 at 13:16
Then it does not work either.
– Gustavo Reis
Nov 29 at 13:25
Do you load the glossaries definitions before the command?
– Ulrike Fischer
Nov 29 at 13:31
Yes, it does. I will upload the post
– Gustavo Reis
Nov 29 at 13:33
1
And now you will have to runxelatex > biber > makeglossaries > xelatex(if you want some sorting, for simpler output variants see Nicola's answer and the documentation).
– Ulrike Fischer
Nov 29 at 13:59
1
1
glsaddall, see the documentation. And better don't use include but input.– Ulrike Fischer
Nov 29 at 13:16
glsaddall, see the documentation. And better don't use include but input.– Ulrike Fischer
Nov 29 at 13:16
Then it does not work either.
– Gustavo Reis
Nov 29 at 13:25
Then it does not work either.
– Gustavo Reis
Nov 29 at 13:25
Do you load the glossaries definitions before the command?
– Ulrike Fischer
Nov 29 at 13:31
Do you load the glossaries definitions before the command?
– Ulrike Fischer
Nov 29 at 13:31
Yes, it does. I will upload the post
– Gustavo Reis
Nov 29 at 13:33
Yes, it does. I will upload the post
– Gustavo Reis
Nov 29 at 13:33
1
1
And now you will have to run
xelatex > biber > makeglossaries > xelatex (if you want some sorting, for simpler output variants see Nicola's answer and the documentation).– Ulrike Fischer
Nov 29 at 13:59
And now you will have to run
xelatex > biber > makeglossaries > xelatex (if you want some sorting, for simpler output variants see Nicola's answer and the documentation).– Ulrike Fischer
Nov 29 at 13:59
|
show 8 more comments
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
This is the simplest method if you want to list all defined terms in the order of definition:
documentclass{memoir}
usepackage[sort=none]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
begin{document}
printunsrtglossaries
end{document}

If you want an abbreviation list as well:
documentclass{memoir}
usepackage[sort=none,abbreviations]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
newabbreviation{html}{HTML}{hypertext markup language}
newabbreviation{xml}{XML}{extensible markup language}
begin{document}
printunsrtglossaries
end{document}
If you want to change the style or the order that the lists are displayed, you need to use printunsrtglossary for each list:
documentclass{memoir}
usepackage[sort=none,abbreviations]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
newabbreviation{html}{HTML}{hypertext markup language}
newabbreviation{xml}{XML}{extensible markup language}
begin{document}
printunsrtglossary % default: style=list, type=main
printunsrtglossary[type=abbreviations,style=long]
end{document}
There are lots of predefined styles.
If your definitions are in an external file, use input not include in the preamble.
The above examples don't perform any sorting. If you want the lists sorted automatically then you need to use one of the indexing methods described in the manual and incorporate the appropriate external tool into your document build, as mentioned in the comments.
Lists sorted automatically... do you mean sort alphabetically?
– Gustavo Reis
Nov 29 at 14:11
@GustavoReis I meant automatically sorting the lists in alphabetical order :-) (Rather than just listing the terms in the order in which you defined them.)
– Nicola Talbot
Nov 29 at 14:18
Sorry, @nicola-talbot, I received an error when I wrotename=Google Cloud Container Registry. I see that the glossaries-extra accepts only one word and not more than two words.
– Gustavo Reis
Nov 29 at 15:50
@GustavoReis That should work as long as the value doesn't contain a comma or braces, but try grouping the value:name={Google Cloud Container Registry}. What's the error message?
– Nicola Talbot
Nov 29 at 17:49
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
This is the simplest method if you want to list all defined terms in the order of definition:
documentclass{memoir}
usepackage[sort=none]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
begin{document}
printunsrtglossaries
end{document}

If you want an abbreviation list as well:
documentclass{memoir}
usepackage[sort=none,abbreviations]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
newabbreviation{html}{HTML}{hypertext markup language}
newabbreviation{xml}{XML}{extensible markup language}
begin{document}
printunsrtglossaries
end{document}
If you want to change the style or the order that the lists are displayed, you need to use printunsrtglossary for each list:
documentclass{memoir}
usepackage[sort=none,abbreviations]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
newabbreviation{html}{HTML}{hypertext markup language}
newabbreviation{xml}{XML}{extensible markup language}
begin{document}
printunsrtglossary % default: style=list, type=main
printunsrtglossary[type=abbreviations,style=long]
end{document}
There are lots of predefined styles.
If your definitions are in an external file, use input not include in the preamble.
The above examples don't perform any sorting. If you want the lists sorted automatically then you need to use one of the indexing methods described in the manual and incorporate the appropriate external tool into your document build, as mentioned in the comments.
Lists sorted automatically... do you mean sort alphabetically?
– Gustavo Reis
Nov 29 at 14:11
@GustavoReis I meant automatically sorting the lists in alphabetical order :-) (Rather than just listing the terms in the order in which you defined them.)
– Nicola Talbot
Nov 29 at 14:18
Sorry, @nicola-talbot, I received an error when I wrotename=Google Cloud Container Registry. I see that the glossaries-extra accepts only one word and not more than two words.
– Gustavo Reis
Nov 29 at 15:50
@GustavoReis That should work as long as the value doesn't contain a comma or braces, but try grouping the value:name={Google Cloud Container Registry}. What's the error message?
– Nicola Talbot
Nov 29 at 17:49
add a comment |
up vote
3
down vote
accepted
This is the simplest method if you want to list all defined terms in the order of definition:
documentclass{memoir}
usepackage[sort=none]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
begin{document}
printunsrtglossaries
end{document}

If you want an abbreviation list as well:
documentclass{memoir}
usepackage[sort=none,abbreviations]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
newabbreviation{html}{HTML}{hypertext markup language}
newabbreviation{xml}{XML}{extensible markup language}
begin{document}
printunsrtglossaries
end{document}
If you want to change the style or the order that the lists are displayed, you need to use printunsrtglossary for each list:
documentclass{memoir}
usepackage[sort=none,abbreviations]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
newabbreviation{html}{HTML}{hypertext markup language}
newabbreviation{xml}{XML}{extensible markup language}
begin{document}
printunsrtglossary % default: style=list, type=main
printunsrtglossary[type=abbreviations,style=long]
end{document}
There are lots of predefined styles.
If your definitions are in an external file, use input not include in the preamble.
The above examples don't perform any sorting. If you want the lists sorted automatically then you need to use one of the indexing methods described in the manual and incorporate the appropriate external tool into your document build, as mentioned in the comments.
Lists sorted automatically... do you mean sort alphabetically?
– Gustavo Reis
Nov 29 at 14:11
@GustavoReis I meant automatically sorting the lists in alphabetical order :-) (Rather than just listing the terms in the order in which you defined them.)
– Nicola Talbot
Nov 29 at 14:18
Sorry, @nicola-talbot, I received an error when I wrotename=Google Cloud Container Registry. I see that the glossaries-extra accepts only one word and not more than two words.
– Gustavo Reis
Nov 29 at 15:50
@GustavoReis That should work as long as the value doesn't contain a comma or braces, but try grouping the value:name={Google Cloud Container Registry}. What's the error message?
– Nicola Talbot
Nov 29 at 17:49
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
This is the simplest method if you want to list all defined terms in the order of definition:
documentclass{memoir}
usepackage[sort=none]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
begin{document}
printunsrtglossaries
end{document}

If you want an abbreviation list as well:
documentclass{memoir}
usepackage[sort=none,abbreviations]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
newabbreviation{html}{HTML}{hypertext markup language}
newabbreviation{xml}{XML}{extensible markup language}
begin{document}
printunsrtglossaries
end{document}
If you want to change the style or the order that the lists are displayed, you need to use printunsrtglossary for each list:
documentclass{memoir}
usepackage[sort=none,abbreviations]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
newabbreviation{html}{HTML}{hypertext markup language}
newabbreviation{xml}{XML}{extensible markup language}
begin{document}
printunsrtglossary % default: style=list, type=main
printunsrtglossary[type=abbreviations,style=long]
end{document}
There are lots of predefined styles.
If your definitions are in an external file, use input not include in the preamble.
The above examples don't perform any sorting. If you want the lists sorted automatically then you need to use one of the indexing methods described in the manual and incorporate the appropriate external tool into your document build, as mentioned in the comments.
This is the simplest method if you want to list all defined terms in the order of definition:
documentclass{memoir}
usepackage[sort=none]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
begin{document}
printunsrtglossaries
end{document}

If you want an abbreviation list as well:
documentclass{memoir}
usepackage[sort=none,abbreviations]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
newabbreviation{html}{HTML}{hypertext markup language}
newabbreviation{xml}{XML}{extensible markup language}
begin{document}
printunsrtglossaries
end{document}
If you want to change the style or the order that the lists are displayed, you need to use printunsrtglossary for each list:
documentclass{memoir}
usepackage[sort=none,abbreviations]{glossaries-extra}
newglossaryentry{Cloud}
{
name=Cloud,
description={shared pools of configurable computer system resources and higher-level services that can be rapidly provisioned with minimal management effort, often over the Internet.}
}
newglossaryentry{Docker}
{
name=Docker,
description={a computer program that performs
operating-system-level virtualization, also known as
``containerization''.}
}
newabbreviation{html}{HTML}{hypertext markup language}
newabbreviation{xml}{XML}{extensible markup language}
begin{document}
printunsrtglossary % default: style=list, type=main
printunsrtglossary[type=abbreviations,style=long]
end{document}
There are lots of predefined styles.
If your definitions are in an external file, use input not include in the preamble.
The above examples don't perform any sorting. If you want the lists sorted automatically then you need to use one of the indexing methods described in the manual and incorporate the appropriate external tool into your document build, as mentioned in the comments.
edited Nov 29 at 14:08
answered Nov 29 at 13:54
Nicola Talbot
33.7k257104
33.7k257104
Lists sorted automatically... do you mean sort alphabetically?
– Gustavo Reis
Nov 29 at 14:11
@GustavoReis I meant automatically sorting the lists in alphabetical order :-) (Rather than just listing the terms in the order in which you defined them.)
– Nicola Talbot
Nov 29 at 14:18
Sorry, @nicola-talbot, I received an error when I wrotename=Google Cloud Container Registry. I see that the glossaries-extra accepts only one word and not more than two words.
– Gustavo Reis
Nov 29 at 15:50
@GustavoReis That should work as long as the value doesn't contain a comma or braces, but try grouping the value:name={Google Cloud Container Registry}. What's the error message?
– Nicola Talbot
Nov 29 at 17:49
add a comment |
Lists sorted automatically... do you mean sort alphabetically?
– Gustavo Reis
Nov 29 at 14:11
@GustavoReis I meant automatically sorting the lists in alphabetical order :-) (Rather than just listing the terms in the order in which you defined them.)
– Nicola Talbot
Nov 29 at 14:18
Sorry, @nicola-talbot, I received an error when I wrotename=Google Cloud Container Registry. I see that the glossaries-extra accepts only one word and not more than two words.
– Gustavo Reis
Nov 29 at 15:50
@GustavoReis That should work as long as the value doesn't contain a comma or braces, but try grouping the value:name={Google Cloud Container Registry}. What's the error message?
– Nicola Talbot
Nov 29 at 17:49
Lists sorted automatically... do you mean sort alphabetically?
– Gustavo Reis
Nov 29 at 14:11
Lists sorted automatically... do you mean sort alphabetically?
– Gustavo Reis
Nov 29 at 14:11
@GustavoReis I meant automatically sorting the lists in alphabetical order :-) (Rather than just listing the terms in the order in which you defined them.)
– Nicola Talbot
Nov 29 at 14:18
@GustavoReis I meant automatically sorting the lists in alphabetical order :-) (Rather than just listing the terms in the order in which you defined them.)
– Nicola Talbot
Nov 29 at 14:18
Sorry, @nicola-talbot, I received an error when I wrote
name=Google Cloud Container Registry. I see that the glossaries-extra accepts only one word and not more than two words.– Gustavo Reis
Nov 29 at 15:50
Sorry, @nicola-talbot, I received an error when I wrote
name=Google Cloud Container Registry. I see that the glossaries-extra accepts only one word and not more than two words.– Gustavo Reis
Nov 29 at 15:50
@GustavoReis That should work as long as the value doesn't contain a comma or braces, but try grouping the value:
name={Google Cloud Container Registry}. What's the error message?– Nicola Talbot
Nov 29 at 17:49
@GustavoReis That should work as long as the value doesn't contain a comma or braces, but try grouping the value:
name={Google Cloud Container Registry}. What's the error message?– Nicola Talbot
Nov 29 at 17:49
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f462376%2fis-there-a-command-similar-to-nocite-for-gls-glossaries-and-is-there-a-glos%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
glsaddall, see the documentation. And better don't use include but input.– Ulrike Fischer
Nov 29 at 13:16
Then it does not work either.
– Gustavo Reis
Nov 29 at 13:25
Do you load the glossaries definitions before the command?
– Ulrike Fischer
Nov 29 at 13:31
Yes, it does. I will upload the post
– Gustavo Reis
Nov 29 at 13:33
1
And now you will have to run
xelatex > biber > makeglossaries > xelatex(if you want some sorting, for simpler output variants see Nicola's answer and the documentation).– Ulrike Fischer
Nov 29 at 13:59