all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Manual PDF and translation (modular texlive?)
Date: Fri, 16 Oct 2020 22:10:39 +0200	[thread overview]
Message-ID: <87r1pyvsn4.fsf@elephly.net> (raw)
In-Reply-To: <87tuuuvum5.fsf@elephly.net>


Ricardo Wurmus <rekado@elephly.net> writes:

> zimoun <zimon.toutoune@gmail.com> writes:
>
>> Currently it is not easy to produce the PDF of the manual.  For
>> reference, see [1].  There are 2 issues:
>>
>>  a) the ’texlive’ package.
>>  b) the fonts about Russian or Chinese.
>>
>> About the a), it is really painful to download the *big* texlive package
>> to be able to compile TeX.  Especially when we have modular texlive
>> packages.  However, it is not clear to me which packages I have to use.
>> Any help is welcome. :-)
>
> I tried this:
>
>     guix environment --pure guix --ad-hoc -e '(begin (use-modules (gnu packages tex))(texlive-union (list texlive-epsf texlive-fonts-ec texlive-amsfonts)))'
>
> This allows me to build doc/guix.pdf, but it chokes on the French and
> German versions (at least).  Frustratingly, texi2dvi swallows all errors
> and just prints:
>
>     pdftex exited with bad status, quitting.
>
> Thanks, I guess.

I can now build the French and the German manuals in this environment:

    guix environment --pure guix --ad-hoc -e '(begin (use-modules (gnu packages tex))(texlive-union (list texlive-epsf texlive-fonts-ec texlive-amsfonts texlive-tex-texinfo)))'

Unfortunately, the accents and umlauts in the table of contents are
still wrong, but they are fine everywhere else.

-- 
Ricardo


  reply	other threads:[~2020-10-16 20:09 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1pyvsn4.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.