Flask: Unable to generate the PDF version of the documentation

Created on 9 Nov 2017  Â·  5Comments  Â·  Source: pallets/flask

commit rev: 470112dd6e708a18eb4ec1daa10c4ea276620dbf
python: 3.6.2

in the docs directory, just execute make latexpdf, there are issues with \maketitle and an unicode char.

(/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/gettitlestring.sty))
! Undefined control sequence.
\maketitle ...tnoterule \relax \ifsphinxpdfoutput 
                                                  \begingroup \def \\{, } \p...
l.66 \maketitle

? 
! Package inputenc Error: Unicode char 🎉 (U+1F389)
(inputenc)                not set up for use with LaTeX.

See the inputenc package documentation for explanation.
Type  H <return>  for immediate help.
 ...                                              

l.20767 Celebrate 🎉

? 
Collected error summary (may duplicate other messages):
  pdflatex: Command for 'pdflatex' gave return code 1
      Refer to 'Flask.log' for details
Latexmk: Use the -f option to force complete processing,
 unless error was exceeding maximum runs of latex/pdflatex.
make[1]: *** [Makefile:33: Flask.pdf] Error 12
make[1] : on quitte le répertoire « /home/stephane/src/github.com/pallets/flask/docs/_build/latex »
make: *** [Makefile:101: latexpdf] Error 2

All 5 comments

I run into this and other Latex issues constantly when building new docs. We can't run the automatic doc builder because it gets stuck, so I have to manually run it on new releases and skip through all the error prompts. We are switching to Read The Docs (pallets/meta#15), but if anyone understands Latex and wants to take a look before then it would be appreciated.

We shouldn't care about things like this.

@mitsuhiko is there a certain reason that we don't use RTD?

There is some internal discussion going on about that, but I'd still like to fix it.

This should be working now :)

Ok I will try ;-)

On 9 May 2018, at 12:37, David Lord notifications@github.com wrote:

Closed #2514.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ghostbod99 picture ghostbod99  Â·  4Comments

westonplatter picture westonplatter  Â·  3Comments

davidhariri picture davidhariri  Â·  3Comments

wadegilmer picture wadegilmer  Â·  4Comments

xliiv picture xliiv  Â·  3Comments