bug-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#26604: documentation: pdf generation is broken


From: zimoun
Subject: bug#26604: documentation: pdf generation is broken
Date: Fri, 16 Oct 2020 13:16:07 +0200

Hi,

On Fri, 16 Oct 2020 at 12:13, Ludovic Courtès <ludo@gnu.org> wrote:
> Andreas Enge <andreas@enge.fr> skribis:

> > On Mon, Sep 28, 2020 at 09:57:43PM +0200, zimoun wrote:
> >> [env]$ make doc/guix.pdf
> >
> > try this instead:
> >     make V=1 pdf
> > which will print what happens.

Thanks for the tip.


> > I have the monolithic texlive package in my profile and building the pdf
> > "almost worked":
> > ...
> > doc/images/coreutils-size-map.png>
> > !pdfTeX error: /home/andreas/.guix-profile/bin/pdftex (file 
> > doc/images/coreutils-graph.png): reading image file failed
> >  ==> Fatal error occurred, no output PDF file produced!
> >
> > It turns out there are a bunch of empty .png files in doc/images/, with
> > corresponding non-empty .dot files. I deleted them and installed graphviz
> > into my profile in the hope that "make pdf" would create the missing
> > .png files, but it does not.
> >
> > However, the following "almost almost" worked:
> > - remove the empty .png files and install graphviz
> > - "make"
> > - "make pdf"
> > I obtained the English, German, French and Spanish pdf documentation, but
> > then a lot of complaints about unicode characters for the Russian
> > documentation (and "make doc/guix.zh_CN.pdf" also has unicode problems).
>
> Simon, can you close the issue if this is fine on your side as well?

Well, it is not satisfactory for me, yet.  It is still "almost almost"
and needs some wizardies to work.  At least the doc should be updated
and maybe a manifest file with the correct TeX packages.  I mean we
have modular texlive and we recommend to use it but we do not use it
for our own infrastructure and then we rely on the BIG texlive
package.  Hum?! :-)

> Maybe it’s a matter (as usual…) of choosing the right texlive-* packages.

They should be documented at least.  (How to find them is another story. ;-))


All the best,
simon





reply via email to

[Prev in Thread] Current Thread [Next in Thread]