-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues compiling documentation (MiKTeX) #83
Comments
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. |
https://code.google.com/p/texworks/issues/detail?id=342 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. |
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. |
What exactly do you mean with "compile correctly"? The log is very different. Previously it complained about not finding Now nothing seems wrong with 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? |
The example compiles error-free. I have to take back what I said before about there being blank space wherever a Here's how it looks now. |
That's strange. First thing I'd say is it has something to do with the way your LaTeX is searching directories recursively.
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. |
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. |
Thanks for taking your time for this. Hopefully it will be worth it ;-) I notice interesting differences in the log files: XeTeX:
LuaLaTeX:
Seeing the luatex log it seems obvious that xetex doesn't really use the file. I can imagine that luatex can deal better with this than xelatex.
|
I did that already, actually. It's now |
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 |
I had to install another font that was missing (Gentium), but otherwise it compiles error-free. |
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 |
Ah, sorry, that should end with |
Results here. Interestingly, the unaltered example file (using
|
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. 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). |
I've created a new branch in my fork, 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 |
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. In my log I have 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 |
That's exactly why I did it that way. :-)
I just asked tex.stackexchange.com; maybe they can.
Same result. |
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). |
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...
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.
Can you be more specific about exactly what you want me to do? |
|
Just to make sure we don't miss any combination:
|
Now I'm really confused... remove the two |
Am 13.12.2013 17:31, schrieb Daniel Rosen:
|
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:
|
I successfully updated LuaTeX to the latest version, and |
Am 13.12.2013 18:11, schrieb Daniel Rosen:
If yes, then I can keep from this experiment that you have to
|
Ugh. Now I'm having an issue with the |
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:
|
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.
|
As requested:
When I compile
documentation\lilyglyphs.tex
, I get a whole mess of errors:Additionally, the PDF output has blank space wherever a
lilyglyph
should be.The text was updated successfully, but these errors were encountered: