From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Manual PDF and translation (modular texlive?)
Date: Mon, 26 Oct 2020 23:50:55 +0100 [thread overview]
Message-ID: <87zh488uuo.fsf@gnu.org> (raw)
In-Reply-To: <87blgq36oa.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 25 Oct 2020 12:07:33 +0100")
Hi!
Ricardo Wurmus <rekado@elephly.net> skribis:
> This patch fixes it:
[...]
> + (("translate-file=cp227")
> + (format #f "translate-file=~a/share/texmf-dist/web2c/cp227"
> + (assoc-ref inputs "texlive-kpathsea")))))
Woow, thumbs up. Not something one could have guessed!
> With this patch the German PDF manual has no more encoding problems.
> This should go to core-updates or a new texlive-upgrade branch, because
> it results in countless rebuilds.
OK.
> There are still remaining problems when using make doc/guix.de.pdf:
>
> * kpathsea causes mktexpk to be run for a number of fonts that already
> exist in the union (e.g. ecrm1200). Why aren’t they found? Perhaps
> that’s because TeX Live only includes the font metrics (.tfm), but not
> the .pk files. I wonder why the .pk files are used at all.
>
> * despite successfully generating the PDF file in the temporary build
> directory, make aborts:
>
> /gnu/store/mw4llmn2l617gf5zakfk1l154f19lxbm-profile/bin/texi2dvi: pdftex exited with bad status, quitting.
> make: *** [Makefile:4375: doc/guix.de.pdf] Error 1
‘texi2dvi’ swallows error messages; I’m not sure it can be made more
verbose, but I remember debugging it through strace (!) where I could
see the underlying messages, which sometimes contain hints if you’re
able to read between the lines.
Kudos on the progress you made!
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-10-26 22:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 14:50 Manual PDF and translation (modular texlive?) zimoun
2020-10-16 19:28 ` Ricardo Wurmus
2020-10-16 20:10 ` Ricardo Wurmus
2020-10-17 20:09 ` zimoun
2020-10-17 21:57 ` Ricardo Wurmus
2020-10-17 22:18 ` zimoun
2020-10-18 6:47 ` Ricardo Wurmus
2020-10-21 10:24 ` Ludovic Courtès
2020-10-21 22:10 ` Ricardo Wurmus
2020-10-22 12:02 ` Ricardo Wurmus
2020-10-22 12:50 ` Ricardo Wurmus
2020-10-22 19:52 ` Ricardo Wurmus
2020-10-22 20:20 ` zimoun
2020-10-22 20:28 ` Ricardo Wurmus
2020-10-22 20:37 ` zimoun
2020-10-22 20:36 ` Ricardo Wurmus
2020-10-22 20:40 ` zimoun
2020-10-22 20:46 ` zimoun
2020-10-22 21:59 ` Ricardo Wurmus
2020-10-25 11:07 ` Ricardo Wurmus
2020-10-26 22:50 ` Ludovic Courtès [this message]
2020-10-27 10:34 ` Ricardo Wurmus
2020-12-11 18:24 ` Giovanni Biscuolo
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=87zh488uuo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).