You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After cloning the repository and changing to doc/, make latex works fine (i.e. finishes with just a few warnings), but changing to the created _build/latex and running make all-pdf fails with several hundred errors. Running this command is weirdly abridged so that the error messages are not always clearly visible. This can partly be remedied by running latexmk messageix.tex instead, though that seems to cause a different error message. Unfortunately, chaning the latex_engine from lualatex to xelatex did not help.
Expected result
The docs should be built successfully as a single PDF file which could then easily be shared.
Problem description
The build process stops with the following message and asks about what it should do with it. Running make all-pdf:
! Undefined control sequence.
\hyper@@link ->\let \Hy@reserved@a
\relax \@ifnextchar [{\hyper@link@ }{\hyp...
l.544 ...asis{ix} mathematical model formulation.}
\label{\detokenize{framewo...
?
My first guess was that the double {{ might cause the error here, but as per explanation in this Slack thread, this is fine (also tried removing brackets manually). Adjusting the doc/conf.py to read
did not help, neither did manually including the hyperref package. It is very unlikely that this is due to my tex installation as this is up-to-date and a test build on a different system (thanks, @Findus23) did not work either.
Notably, we have set on ReadTheDocs that a PDF and EPUB version should be created with each build. However, I cannot find any PDF build logs or available for download newer than of version 2.0.0.
For completeness' sake, there are also several warnings of the sort
LaTeX Warning: Hyper reference `contributing::doc' on page 5 undefined on input line 452.
And things like
Package hyperref Warning: You have enabled option `breaklinks'.(hyperref) But driver `hdvips.def' does not suppport this.(hyperref) Expect trouble with the link areas of broken links.
or
------------
Run number 1 of rule 'latex'
------------
------------
Running 'lualatex --output-format=dvi -recorder "messageix.tex"'
------------
This is LuaHBTeX, Version 1.17.0 (TeX Live 2023)
restricted system commands enabled.
(./messageix.tex
LaTeX2e <2023-06-01> patch level 1
L3 programming layer <2023-06-16>
(/usr/local/texlive/2023/texmf-dist/tex/generic/luatex85/luatex85.sty)
(./sphinxmanual.cls
Document Class: sphinxmanual 2019/12/01 v2.3.0 Document class (Sphinx manual)
(/usr/local/texlive/2023/texmf-dist/tex/latex/base/report.cls
Document Class: report 2023/05/17 v1.4n Standard LaTeX document class
(/usr/local/texlive/2023/texmf-dist/tex/latex/base/size10.clo)))
(/usr/local/texlive/2023/texmf-dist/tex/latex/cmap/cmap.sty
Package cmap Warning: pdftex in DVI mode - exiting.
) (/usr/local/texlive/2023/texmf-dist/tex/latex/fontspec/fontspec.sty
Having spent the last two days hunting these errors unsuccessfully, I have come to doubt that anyone is missing the option to build the LaTeX-PDF locally. If it was missing, there would have been more support requests for exactly that over the last three years. For the time being, I will therefore stop this project.
If you are missing this option, please let us know by upvoting this issue and updating it with information on your system and the error messages you receive.
The text was updated successfully, but these errors were encountered:
The supported image types for the sphinx LaTeXBuilder include both PNG and PDF despite the sphinx image docs claiming that LaTeX prefers PDF over PNG. Either way, we are also trying to include JPG, WEBP, and SVG files, which do not seem to be supported by LaTeX in sphinx. Note that when providing multiple formats of the same image, including it as image_name.* allows sphinx to choose the format it prefers for the current builder. Also note that the onlydirective allows you to write code that is used only for LaTeX or only for HTML.
In the past, some people reported having to follow a certain order in which LaTeX packages are imported. However, moving all of the packages that are reported after hyperref by us manually before it (one by one) did not change anything (those were sphinxmessages, unicode-math, and graphicx). This problem might also be about expansion but I'm not aware of any config settings there and we are not manually adding expansion commands where we should not.
For good measure, find here the sphinx docs on LaTeX customization.
Code sample or context
After cloning the repository and changing to
doc/
,make latex
works fine (i.e. finishes with just a few warnings), but changing to the created_build/latex
and runningmake all-pdf
fails with several hundred errors. Running this command is weirdly abridged so that the error messages are not always clearly visible. This can partly be remedied by runninglatexmk messageix.tex
instead, though that seems to cause a different error message. Unfortunately, chaning thelatex_engine
fromlualatex
toxelatex
did not help.Expected result
The docs should be built successfully as a single PDF file which could then easily be shared.
Problem description
The build process stops with the following message and asks about what it should do with it. Running
make all-pdf
:Running
latexmk messageix.tex
:My first guess was that the double
{{
might cause the error here, but as per explanation in this Slack thread, this is fine (also tried removing brackets manually). Adjusting thedoc/conf.py
to readdid not help, neither did manually including the hyperref package. It is very unlikely that this is due to my tex installation as this is up-to-date and a test build on a different system (thanks, @Findus23) did not work either.
Notably, we have set on ReadTheDocs that a PDF and EPUB version should be created with each build. However, I cannot find any PDF build logs or available for download newer than of version 2.0.0.
For completeness' sake, there are also several warnings of the sort
And things like
or
Versions
Output of message-ix show-versions
Conclusion
Having spent the last two days hunting these errors unsuccessfully, I have come to doubt that anyone is missing the option to build the LaTeX-PDF locally. If it was missing, there would have been more support requests for exactly that over the last three years. For the time being, I will therefore stop this project.
If you are missing this option, please let us know by upvoting this issue and updating it with information on your system and the error messages you receive.
The text was updated successfully, but these errors were encountered: