From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: ng0 <contact.ng0@cryptolab.net>, 26604@debbugs.gnu.org
Subject: bug#26604: documentation: pdf generation is broken
Date: Fri, 16 Oct 2020 13:16:07 +0200 [thread overview]
Message-ID: <CAJ3okZ2Cy=LBssFueXEhVi9SZyyL+yt5VGnS5KHKFXpjfo2-AA@mail.gmail.com> (raw)
In-Reply-To: <87362e8onb.fsf@gnu.org>
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
next prev parent reply other threads:[~2020-10-16 11:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 11:09 bug#26604: documentation: pdf generation is broken ng0
2017-04-23 4:14 ` Chris Marusich
2017-04-23 16:15 ` ng0
2017-04-23 18:42 ` Chris Marusich
2017-05-05 18:53 ` Ludovic Courtès
2020-09-28 19:57 ` zimoun
2020-09-28 21:15 ` Andreas Enge
2020-10-16 10:13 ` Ludovic Courtès
2020-10-16 11:16 ` zimoun [this message]
2021-05-03 14:06 ` Ricardo Wurmus
2021-05-04 8:02 ` zimoun
2021-05-04 10:04 ` Ricardo Wurmus
2021-05-04 11:28 ` zimoun
2021-05-23 15:17 ` Marius Bakke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ2Cy=LBssFueXEhVi9SZyyL+yt5VGnS5KHKFXpjfo2-AA@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=26604@debbugs.gnu.org \
--cc=contact.ng0@cryptolab.net \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).