Issues compiling documentation (MiKTeX)

[skiasaurus]

As requested:

When I compile documentation\lilyglyphs.tex, I get a whole mess of errors:

line 1428: I can't find file `lilyglyphs.aux' \end{document}
line 1428: Emergency stop \end{document}
: No file lilyglyphs.aux.
: Rerun to get /PageLabels entry.
line 58: Reference `sec:installation' on page 2 undefined
line 63: Font shape `EU1/LiberationMono(0)/bx/n' undefined(Font) using `EU1/LiberationMono(0)/m/n' instead
line 63: Font shape `EU1/LiberationMono(0)/m/it' undefined(Font) using `EU1/LiberationMono(0)/m/n' instead
line 80: Reference `chap:list_predefined_commands' on page 2 undefined
line 82: Overfull \hbox (41.838pt too wide) in paragraph
line 93: Reference `sec:generic_access_commands' on page 2 undefined
line 93: Reference `sec:generating_commands_image' on page 2 undefined
: \float@addtolists detected!(scrreprt) You should use the features of package `tocbasic'(scrreprt) instead of \float@addtolists.
line 133: Reference `chap:python_scripts' on page 4 undefined
line 218: Overfull \hbox (0.21019pt too wide) in paragraph
line 225: Suppressing link with empty target
line 302: Overfull \hbox (3.17104pt too wide) in paragraph
line 348: Reference `sec:howto_predefined_commands' on page 11 undefined
line 343: Overfull \hbox (2.79442pt too wide) in paragraph
line 368: Overfull \hbox (5.02388pt too wide) in paragraph
line 404: Reference `tab:singlenotes' on page 13 undefined
line 439: Column widths have changed(longtable) in table 3.1
line 450: Reference `tab:beamedNotes' on page 14 undefined
line 473: Reference `tab:clefs' on page 15 undefined
line 487: Suppressing link with empty target
line 520: Reference `tab:accidentals' on page 17 undefined
line 542: Reference `tab:rests' on page 17 undefined
line 544: Reference `sec:dotted_symbols' on page 17 undefined
line 569: Reference `tab:singleDynLetters' on page 18 undefined
line 584: Reference `tab:combinedDynLetters' on page 18 undefined
line 598: Reference `tab:dynamicSigns' on page 19 undefined
line 624: Reference `tab:scripts' on page 20 undefined
line 653: Suppressing link with empty target
line 667: Reference `sec:directory_structure' on page 22 undefined
line 765: Suppressing link with empty target
line 762: Overfull \hbox (4.86406pt too wide) in paragraph
line 771: Suppressing link with empty target
line 798: Suppressing link with empty target
line 831: Reference `chap:contributing' on page 26 undefined
line 878: Suppressing link with empty target
line 890: Suppressing link with empty target
line 893: Reference `sec:dynamic_text' on page 27 undefined
line 909: Reference `subsec:private_directory_structure' on page 28 undefined
line 911: Suppressing link with empty target
line 987: Underfull \hbox (badness 10000) in paragraph
line 1004: Reference `subsubsec:commands_single-glyphs' on page 31 undefined
line 1024: Suppressing link with empty target
line 1080: Suppressing link with empty target
line 1100: Suppressing link with empty target
line 1164: Suppressing link with empty target
line 1170: Suppressing link with empty target
line 1191: Overfull \hbox (32.43652pt too wide) in paragraph
line 1203: Overfull \hbox (20.3764pt too wide) in paragraph
line 1221: Suppressing link with empty target
line 1351: Reference `subsec:GGC_fine-tuning' on page 39 undefined
line 1351: Reference `subsec:GGC_finishing_off' on page 39 undefined
line 1400: Token not allowed in a PDF string (Unicode):(hyperref) removing `\lilyglyphs'
: Table widths have changed. Rerun LaTeX.

Additionally, the PDF output has blank space wherever a lilyglyph should be.

[uliska]

OK, I can't really make anything useful from that, sorry.

I assume, that the majority of errors are consequences of a small number of errors happendd earlier. Could you please provide the full logfile? If you can't upload and link it anywhere please send it by email.

[skiasaurus]

Here ya go.

[uliska]

https://code.google.com/p/texworks/issues/detail?id=342 indicates spaces in the file path to be a possible issue.

Before trying to mess around with your installation ("C:\Local TeX Files\") you could try copying lilyglyphs.tex to a location without spaces and try. If it should compile there you should repeat the "installation" of the local TeX tree at a different location (probably it should be enough to rename "Local TeX Files" and change the setting in the MiKTeX settings dialog).

[skiasaurus]

It won't compile correctly at another location. Different log, same results. Use the Dropbox link above again; I've uploaded a new version of the log file.

I notice that your link is from TeXworks; if it makes a difference, I'm using TeXstudio.

[uliska]

What exactly do you mean with "compile correctly"?

The log is very different. Previously it complained about not finding lilyglyphs.aux, followed by an "emergency stop". (Actually I don't see that a PDF should have been created at all previously.)

Now nothing seems wrong with lilyglyphs.aux (so the issue with spaces in the file name is valid and you should rename your "Local TeX Files" directory), and the log ends with "Output written on lilyglyphs.pdf (42 pages)."

So what is the state exactly now?

Would you please try to compile the example document from the first page of the manual and tell me about the results?

[skiasaurus]

The example compiles error-free.

I have to take back what I said before about there being blank space wherever a lilyglyph should be—actually, the only thing for which I have blank space is the lilyglyphs logo (\lilyglyphs).

Here's how it looks now.

[uliska]

That's strange.

First thing I'd say is it has something to do with the way your LaTeX is searching directories recursively. Please try both of the following things:

• Move the file lilyglyphs_logo.pdf from the documentation\lilyglyphs_logo directory to the root directory
• Add the path to the definition of the \lilyglyphs command:
  Make the second to last line in lilyglyphs.sty
\lilyPrintImage[#1]{documentation/lilyglyphs_logo/lilyglyphs_logo}%

---

On the other hand I doubt that is the reason. a) I don't see an error about not finding the file, b) I wonder why the space it takes is about right. So it does seem the PDF is found, but somehow printed white or such. Strange ...

[skiasaurus]

Nope, neither of those worked.

A new development: I tried compiling with LuaTeX instead of XeTeX, just to see if it would make a difference, and I got a whole different set of errors. I'm going to email you the log instead of uploading it.

[skiasaurus]

OK, now this is weird.

I just tried compiling this code using both XeTeX and LuaTeX:

\documentclass{article}
\usepackage{fontspec}
\usepackage{lilyglyphs}
\begin{document}
    \lilyglyphs{}
\end{document}

XeTeX: output, log LuaTeX: output, log

[uliska]

Thanks for taking your time for this. Hopefully it will be worth it ;-)

I notice interesting differences in the log files:

XeTeX:

ABD: EveryShipout initializing macros
File: lilyglyphs_logo.pdf Graphic file (type QTm)
 <use  "lilyglyphs_logo.pdf" > [1

]

LuaLaTeX:

 ABD: EveryShipout initializing macros
<lilyglyphs_logo.pdf, id=4, 40.40294pt x 14.79527pt>
File: lilyglyphs_logo.pdf Graphic file (type pdf)
 <use lilyglyphs_logo.pdf>
Package pdftex.def Info: lilyglyphs_logo.pdf used on input line 5.
(pdftex.def)             Requested size: 39.1908pt x 14.35138pt.

[1

{C:/Users/Daniel/AppData/Local/MiKTeX/2.9/pdftex/config/pdftex.map} <C:/local-t
ex-files/tex/latex/lilyglyphs/documentation/lilyglyphs_logo/lilyglyphs_logo.pdf
>] (C:/Users/Daniel/Desktop/lilyglyphs-docs/luatex.aux) )

Seeing the luatex log it seems obvious that xetex doesn't really use the file. But I have an idea: IISC you have copied the lilyglyphs.tex manual file to a location without spaces in the path, but not the package itself (-> ... pdftex.map} <C:/local-tex-files/tex/latex/...)

I can imagine that luatex can deal better with this than xelatex. So could you please

• rename C:/Local TeX Files to something without spaces (a good LaTeX-y name would be C:\texmf) and
• update the MiKTeX settings accordingly?

[skiasaurus]

I did that already, actually. It's now C:\local-tex-files. Those were my results when I compiled lilyglyphs.tex in situ.

[uliska]

Ah, I see. I thought that was some normalizing magic on luatex's behalf.

Hm. Currently I don't know where to look further. I think I'll ask about this on the tex.stackexchange site.

In the meantime, could you please try to compile the file documentation\lilyglyphs_logo\lilyglyphs_logo.tex? (Attention: In order not to create confusion with your Git repository you should probably copy that file out of the repo first.)

[skiasaurus]

I had to install another font that was missing (Gentium), but otherwise it compiles error-free.

[uliska]

Please take the previous example file, save it directly in the root directory (of course you can remove it later so it doesn't get into your Git repository). Then replace \lilyglyphs{} with \includegraphics{documentation/lilyglyphs_logo/lilyglyphs_logo}. I'd like to see if the issue originates in the command or in the file itself.

[uliska]

Ah, sorry, that should end with lilyglyphs_logo.pdf} so you won't get fooled by the .png file.

[skiasaurus]

Results here.

Interestingly, the unaltered example file (using \lilyglyphs{} and in its original location) now compiles error-free using XeTeX, and with just one error (below) and the correct output using LuaTeX.

File: genericAccess.inp
Type: error
Line: line 133
Message: ambiguous syntax (function call x new statement) near '('. \end{luacode}

[uliska]

The error messag in xetex.png doesn't point to an issue with the content of the file or the package but with your file itself. What I'm wondering about is that "xetex".tex. Are you sure everything was right with your file, filename, location etc.?

The other error message is quite known to me by now, but I don't understand why it pops up now. These "ambiguous syntax" errors usually mean that you're using an outdated version of luatex (I don't know exactly what is necessary, but you need a quite recent version). It's strange though, that this happens now, after a number of successful compilations ...

[skiasaurus]

I've created a new branch in my fork, debug-logo, that shows the state of the example files.

As for the LuaTeX version, I can't figure out how to update it within MiKTeX, which comes with version beta-0.70.2-2012060719. I tried downloading the latest stable binary and replacing the existing ones (located at C:\Program Files\MiKTeX 2.9\miktex\bin\luatex.exe and C:\Program Files\MiKTeX 2.9\miktex\bin\lualatex.exe) with it, but when I tried compiling again the log still gave the old version number.

[uliska]

OK, I've looked at the files, and (apart from the fact that you wouldn't need separate files except maybe for the output filename) everything looks right here, I can compile both with both luatex and xetex. The "xetex".tex seems to be correct, I see that too.

In my log I have LuaTeX, Version beta-0.76.0-2013070317 (rev 4627) (format=lualatex 2013.10.17). Your version from 2012 should definitely be too old, but I find it strange that you had been already able to compile files before.

Unfortunately I can't tell you anything about how you can update packages in MiKTeX. There should be some cleaner way than replacing exe files.

Regarding the "Can't start" error you might try not to use the "Build & View" command but select XeLaTeX directly from Tools->Commands.

[skiasaurus]

you wouldn't need separate files except maybe for the output filename

That's exactly why I did it that way. :-)

Unfortunately I can't tell you anything about how you can update packages in MiKTeX.

I just asked tex.stackexchange.com; maybe they can.

Regarding the "Can't start" error you might try not to use the "Build & View" command but select XeLaTeX directly from Tools->Commands.

Same result.

[uliska]

Hm. And it displays the logo? What about the logo inside the manual? Did that change too?

One thing would be interesting: Maybe the underscore in the filename is a problem (although I'd expect this to be ubiquitous if it had been the reason). Maybe try even one more thing: Renaming the logo file, say, replace the underscore by a hyphen and the includegraphics command accordingly?

[skiasaurus]

Hm. And it displays the logo?

By "same result" I meant that I still get a "can't start" error—but this is only for the file located in the repository. The copy that I made on my desktop still compiles error-free and with the correct output. Similarly...

What about the logo inside the manual? Did that change too?

Compiling the manual in situ gets me blank spaces where the logo should be, but compiling a copy of it outside the repository gets it done correctly.

Maybe try even one more thing: Renaming the logo file, say, replace the underscore by a hyphen and the includegraphics command accordingly?

Can you be more specific about exactly what you want me to do?

[uliska]

Compiling the manual /in situ/ gets me blank spaces where the logo should be, but compiling a copy of it outside the repository gets it done correctly.

Very strange, indeed. Maybe something about permissions? Although I don't see why anything should be written inside the directory. I mean, the other temp files are written too without problems.

[uliska]

Just to make sure we don't miss any combination: Try to compile

• xetex.tex
• inside the repository
• not with \lilyglyphs{} but with \includegraphics
• remove the two \include statements but include graphicx instead.

[skiasaurus]

Now I'm really confused... remove the two \include statements from where? xetex.tex doesn't have any \include statements...

[ghost]

Am 13.12.2013 17:31, schrieb Daniel Rosen:

Now I'm really confused... remove the two |\include| statements from where? |xetex.tex| doesn't have any |\include| statements...

Sorry, my fault. I meant the \usepackage statements for fontspec and lilyglyphs

[skiasaurus]

I tried it, and while I got the same two error messages as before ("Could not start Build & View" and "Log File not found!"), I also got a message in TeXstudio saying that there was indeed a permission issue with something or other (not sure whether that was the first time it ever appeared or if it was just the first time I noticed it).

I tried it again running TeXstudio as an administrator and it compiled, but with the same blank spaces and a couple of errors:

File	Type	Line	Message
xetex.tex	error	line 5	I can't find file `xetex.aux' \end{document}
xetex.tex	error	line 5	Emergency stop \end{document}
xetex.tex	warning		No file xetex.aux.

[skiasaurus]

I successfully updated LuaTeX to the latest version, and luatex.tex now compiles error-free, with correct output, both inside and outside the repo.

[ghost]

Am 13.12.2013 18:11, schrieb Daniel Rosen:

I successfully updated LuaTeX to the latest version, and |luatex.tex| now compiles error-free, with correct output, both inside and outside the repo.

That's nice to hear. The manual too?

If yes, then I can keep from this experiment that you have to

• manually update luatex because MiKTeX 2.9 doesn't already have the right version
• store the package in a directory without spaces in the path

[skiasaurus]

Ugh. Now I'm having an issue with the selnolig package, I think because I updated all my packages when I updated LuaTeX. Nothing's compiling now.

[skiasaurus]

That's over with. No idea what happened...

The manual now compiles using LuaTeX with the logo appearing as it should, both inside and outside the repo, but there are still some errors in both cases. Logs here.

Here are the errors as TeXstudio has them:

File	Type	Line	Message
lilyglyphs.tex	warning		\float@addtolists detected!(scrreprt) You should use the features of package `tocbasic'(scrreprt) instead of \float@addtolists.
lilyglyphs.tex	warning	line 318	Font shape `EU2/DejaVuSansMono(0)/m/it' undefined(Font) using `EU2/DejaVuSansMono(0)/m/n' instead
lilyglyphs.tex	bad box	line 988	Overfull \hbox (0.79332pt too wide) in paragraph
lilyglyphs.tex	bad box	line 988	Underfull \hbox (badness 10000) in paragraph
lilyglyphs.tex	bad box	line 988	Overfull \hbox (26.68513pt too wide) in paragraph
lilyglyphs.tex	warning	line 1401	Token not allowed in a PDF string (PDFDocEncoding):(hyperref) removing `\lilyglyphs'
lilyglyphs.tex	warning		Some font shapes were not available, defaults substituted.

[skiasaurus]

Using XeTeX, I get similar results, except that there are different errors—and a lot more—and there are still blank spaces where the logo should be when I compile it within the repo (outside the repo the logo appears as it should).

Logs here.

File	Type	Line	Message
lilyglyphs.tex	bad box	line 82	Overfull \hbox (40.14099pt too wide) in paragraph
lilyglyphs.tex	warning		\float@addtolists detected!(scrreprt) You should use the features of package `tocbasic'(scrreprt) instead of \float@addtolists.
lilyglyphs.tex	bad box	line 218	Overfull \hbox (0.21019pt too wide) in paragraph
lilyglyphs.tex	warning	line 248	Font shape `EU1/DejaVuSansMono(0)/bx/n' undefined(Font) using `EU1/DejaVuSansMono(0)/m/n' instead
lilyglyphs.tex	bad box	line 302	Overfull \hbox (3.10161pt too wide) in paragraph
lilyglyphs.tex	bad box	line 343	Overfull \hbox (0.84135pt too wide) in paragraph
lilyglyphs.tex	bad box	line 368	Overfull \hbox (4.40825pt too wide) in paragraph
lilyglyphs.tex	bad box	line 763	Overfull \hbox (4.86404pt too wide) in paragraph
lilyglyphs.tex	bad box	line 988	Underfull \hbox (badness 10000) in paragraph
lilyglyphs.tex	bad box	line 1192	Overfull \hbox (31.73642pt too wide) in paragraph
lilyglyphs.tex	bad box	line 1204	Overfull \hbox (19.84648pt too wide) in paragraph
lilyglyphs.tex	warning	line 1401	Token not allowed in a PDF string (Unicode):(hyperref) removing `\lilyglyphs'
lilyglyphs.tex	bad box	line 1416	Overfull \hbox (4.4604pt too wide) in paragraph
lilyglyphs.tex	warning		Some font shapes were not available, defaults substituted.