0

The glossaries and acronyms are not showing up at \printglossaries. Bear with me, as I hopefully sufficiently explain the structure. I'm using Windows 7 with Sublime Text 3 and MikTeX 2.9. I installed Perl manually and added it to path.

I'm having my document divided into multiple files:

  • main.tex (which I compile)

    \documentclass{book}
    \input{header}
    \begin{document}
    \include{chapter} 
    % ...
    \include{ending}
    \end{document}
    
  • header.tex

    % ...
    \usepackage[xindy={language=english,codepage=utf8},%
             acronym,nopostdot,description]{glossaries}
    \makeglossaries
    \glstoctrue
    \loadglsentries{<path_to_glossaries_file>}
    % ...
    
  • chapter.tex (multiple of those) - inside I use the \gls{<>}

  • ending.tex

    % ...
    \printglossaries
    \printglossaries[type=\acronymtype]
    % ...
    

In my glossaries file, I define the elements with both \newacronym{code}{acr}{desc} and \newglossaryentry{code}{name={},description={}}

I compile the main document with a LaTeXTools script invoking:

pdflatex
bibtex
perl makeglossaries
pdflatex
pdflatex

always with the main name as parameter. I get the .acn, .glo and .xdy files produced, just the final list is not in the .pdf. So, what am I doing wrong?

  • It's difficult to say without more information, but you could try using this diagnostic method. – Nicola Talbot Aug 19 '16 at 10:20
  • @NicolaTalbot What information would be useful? I'll provide it gladly ... And thanks for the tip about the diagnostic method. – Pjanc Matuzl Aug 20 '16 at 17:01
  • Please format code blocks using indentation rather than back ticks, which should be reserved for inline code. – cfr Aug 21 '16 at 0:54
1

I used the diagnostic method suggested by @NikolaTalbot . After a while I observed, that the tool adds some files automatically (.acr, .gls to name some). After some playing around, I removed the perl command in front of the makeglossaries command, and now it works!

The answer is posted, so nobody will try to find one. I know - this answer is not very informative, but I don't have a better one to offer.

  • 1
    @cfr I don't think perl makeglossaries is equivalent to perl perl ... on any OS. On *nix systems makeglossaries (without an extension) starts with #!/usr/bin/env perl so bash will automatically execute perl with the makeglossaries file, but on Windows it's makeglossaries.exe that executes perl (makeglossaries used as an argument doesn't assume an extension). I'm guessing that perl makeglossaries actually resulted in the error Can't open perl script "makeglossaries": No such file or directory because perl didn't find the file makeglossaries in the current directory. – Nicola Talbot Aug 22 '16 at 11:13
  • 1
    @Pjanc Your answer is correct. Either omit perl if makeglossaries can automatically invoke it or use perl followed by the full path to the makeglossaries script. The first option (as in your answer) is by far the simplest. – Nicola Talbot Aug 22 '16 at 11:15
  • @NicolaTalbot You are surely right. – cfr Aug 22 '16 at 13:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.