From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Manual PDF and translation (modular texlive?)
Date: Sat, 17 Oct 2020 22:09:21 +0200 [thread overview]
Message-ID: <86k0voaa32.fsf@gmail.com> (raw)
In-Reply-To: <87r1pyvsn4.fsf@elephly.net>
Hi Ricardo,
Thank you for looking at this.
On Fri, 16 Oct 2020 at 22:10, Ricardo Wurmus <rekado@elephly.net> wrote:
> 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.
Working on fixing this –– at least the French one ;-) –– I notice that:
guix environment -C --ad-hoc texinfo -- texi2dvi --help
raises an error about ’sed’ is missing. Adding ’sed’, it still raises
an error about ’cat’ (coreutils, right?). These 2 dependencies should
be added as ’propagated-inputs’, right?
Well, back to the real issue. I do not know if the issue comes from TeX
configuration or from ’makeinfo’. For example,
--8<---------------cut here---------------start------------->8---
mkdir -p /tmp/test && cd /tmp/test
cp ~/guix/doc/{guix.fr,os-*,fdl-1.3,contributing.fr,version-fr}.texi .
cp -R ~/guix/doc/images images
cp ~/guix/doc/environment-gdb.scm .
cp ~/guix/doc/package-hello.{scm,json} .
guix environment guix -C \
--ad-hoc texlive-base texlive-fonts-ec texlive-epsf texlive-tex-texinfo \
-- makeinfo --pdf guix.fr.texi
--8<---------------cut here---------------end--------------->8---
lead to incorrect Table of Contents but the rest is good (at least what
I checked). It seems as ’makeinfo’ incorrectly deal with the unicode in
the master menu. On the other hand,
guix environment guix -C --ad-hoc texlive -- makeinfo --pdf guix.fr.pdf
works correctly. Hum? I do not know…
All the best,
simon
next prev parent reply other threads:[~2020-10-17 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
2020-10-17 20:09 ` zimoun [this message]
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
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=86k0voaa32.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--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).