Search found 3 matches

by aluaces
Fri May 15, 2020 5:28 pm
Forum: MakeIndex, Nomenclature, Glossaries and Acronyms
Topic: ERROR: Missing number, treated as zero when defining a custom glossary
Replies: 3
Views: 22910

ERROR: Missing number, treated as zero when defining a custom glossary

Bartman wrote: You get your error message because you use the commands \glsdescripES and \glsunit when changing \glossentry instead of \glsentrydescripES and \glsentryunit.
Sorry, I don't know how I could misread your post so badly. Of course using "entry" solves the problem, thanks a lot!
by aluaces
Fri May 15, 2020 5:12 pm
Forum: MakeIndex, Nomenclature, Glossaries and Acronyms
Topic: ERROR: Missing number, treated as zero when defining a custom glossary
Replies: 3
Views: 22910

ERROR: Missing number, treated as zero when defining a custom glossary

Thanks for your time, Bartman!

With respect to reproducing the issue, I tried to see if I could replicate it on overleaf, but I could not be able to trigger the indexing, both as is or with automake present.

I tried to use both

\glssetnoexpandfield{descripES}
\glssetnoexpandfield{unit}

and ...
by aluaces
Fri May 15, 2020 1:51 pm
Forum: MakeIndex, Nomenclature, Glossaries and Acronyms
Topic: ERROR: Missing number, treated as zero when defining a custom glossary
Replies: 3
Views: 22910

ERROR: Missing number, treated as zero when defining a custom glossary

Hi, I have reduced my problem with a customized glossary to a minimal example.

I get some errors of the following type when using my glossary.


ERROR: Missing number, treated as zero.

--- TeX said ---
<to be read again>
\gls@numberpage
l.5 ...etentrycounter[]{page}\glsnumberformat{1}}}


If ...