unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Manual PDF and translation (modular texlive?)
Date: Tue, 27 Oct 2020 11:34:06 +0100	[thread overview]
Message-ID: <87wnzc0xgh.fsf@elephly.net> (raw)
In-Reply-To: <87zh488uuo.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> 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!

Hah, when I originally added the code to build the fmt files this
problem did stick out to me, but I thought it would be solved eventually
by modifying search paths in the configuration file.

It’s odd that the file cannot be found when it is already part of the
texlive-union and the search paths include all sub-directories.  But I
don’t want to investigate further when patching gets us to the correct
output faster :)

>> 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.

I used strace as well before I found that the log files are kept in the
temporary build directory under doc/guix.de.t2p.  Later I found that
“make V=1 doc/guix.de.pdf” shows the TeX output, which is also helpful.
Still, it’s very noisy and it’s not clear which of the many messages
correspond to the fatal error.  Oh well.

The .pk files are bitmap fonts that are generated when T1 fonts are not
found.  Adding texlive-cm-super to the union avoids generation of bitmap
fonts for the CM fonts (which are the default when no other fonts are
found), so that solves most of the problems and allows me to remove all
of those (setenv "HOME" "/tmp") hacks in packages that use the
texlive-union.  That’s now implemented on the wip-texlive branch.

The French manual can be built in PDF format, so I’m suspecting a
problem with the German texi sources that turns fatal when building the
PDF.

-- 
Ricardo


  reply	other threads:[~2020-10-27 10:32 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
2020-10-27 10:34                     ` Ricardo Wurmus [this message]
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=87wnzc0xgh.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --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).