Reputation
Top tag
Next privilege 15,000 Rep.
Protect questions
Badges
31 50
Newest
 Good Answer
Impact
~242k people reached

Jun
30
awarded  Good Answer
Jun
29
comment LaTeX Error: File datatool-base.sty not found
@usernumber The full user manual is glossaries-user.pdf (texdoc glossaries-user or just texdoc glossaries) but as that covers all high-level commands it's very long and complicated (but not nearly as complicated as the documented code glossaries-code.pdf). "The glossaries package: a guide for beginners" (glossariesbegin.pdf) is much shorter and makes a better starting point.
Jun
29
comment LaTeX Error: File datatool-base.sty not found
@usernumber It's part of the glossaries documentation so you can just use texdoc (texdoc glossariesbegin), or you can download it from CTAN
Jun
28
comment Undefined Control Sequence?
Can you recheck the case of the letters L, T and X in \LaTeX? Those three letters all have to be upper case.
Jun
28
comment Creating figures in LaTeX
In addition to the above mentioned TiKZ editors and inkscape, there's also flowframtk which can export to pgf code. This can be input into a LaTeX document using \input (with \usepackage{pgf}).
Jun
26
comment Am I over exerting the glossaries package?
@EngBIRD No, those issues shouldn't affect \newentry. Those drawbacks arise to compensate for documents where there's a glossary (or list of acronyms, etc) in the front matter. Since you said you're not interested in that, I don't see a problem with using \newentry within the document environment. You'll get an error if you attempt to use an entry before it's been defined, but then you just need to move \newentry to just before the first instance where it's used. I don't know how much it will help to undefine an entry when you no longer need it.
Jun
25
answered errors with makeindex: Conflicting entries: multiple encaps for the same page under same key
Jun
25
comment Am I over exerting the glossaries package?
@EngBIRD If you're already loading the etoolbox package, then I don't think there's a significant difference in using the first method over the second. \csuse does marginally more than \@nameuse as it uses the conditional \ifcsname which \@nameuse doesn't, but I don't think there's much in that. I think it might be worth seeing if you can cut down on non-essential packages or use a light-weight class. Also, if you haven't already, have a look at Component's of (La)TeX's Memory Usage.
Jun
24
answered Am I over exerting the glossaries package?
Jun
24
comment Dictionary English-French-Arabic with glossaries package
I don't have the required fonts installed, so I can't test your document, but have you tried the multi-column glossary styles described in the "Multicols Styles" section of the manual?
Jun
24
comment Specify custom plural form in glossaries does not work
Regarding defining entries in the preamble instead of the document environment, please see Drawbacks With Defining Entries in the Document Environment.
Jun
24
comment Specify custom plural form in glossaries does not work
Since the question has been closed I can't answer it yet, but I've added a minimal working example to your question. Please copy and paste it into a test file and say what output this produces. For me it produces "polygon meshes".
Jun
24
revised Specify custom plural form in glossaries does not work
Added proper mwe
Jun
24
awarded  Revival
Jun
24
awarded  Enlightened
Jun
24
awarded  Nice Answer
Jun
23
answered Equivalent of `newdateformat` in `datetime2`?
Jun
23
answered Does termcal work with datetime?
Jun
23
comment Specify custom plural form in glossaries does not work
You have an old version of glossaries. It may be related to Acronyms defined in document body result in wrong firstplural. Move \newglossaryentry to the preamble (before \begin{document}) and try again. (And possibly also update your version of glossaries.sty.)
Jun
23
comment Specify custom plural form in glossaries does not work
You can find the version number from the log file. (Search for glossaries.sty, or add \listfiles to your document and it will add all the version information at the end of the transcript.) It would help if you could add \documentclass, \makeglossaries and \begin{document}\glspl{polymesh}\end{document} to the code you posted to make it a minimal working example that illustrates the problem. That way we know we're both working with the same code.