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: Thu, 22 Oct 2020 00:10:05 +0200 [thread overview]
Message-ID: <878sbzut6q.fsf@elephly.net> (raw)
In-Reply-To: <87lffz6fmc.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> 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.
>
> Yeah, ‘doc/build.scm’ has this comment:
>
> ;; FIXME: This union works, except for the table of contents of non-English
> ;; manuals, which contains escape sequences like "^^ca^^fe" instead of
> ;; accented letters.
> ;;
> ;; (define texlive
> ;; (texlive-union (list texlive-tex-texinfo
> ;; texlive-generic-epsf
> ;; texlive-fonts-ec)))
>
> What’s interesting is that it breaks accents in the table of contents,
> but not elsewhere.
These double caret sequences are representations of multi-byte
characters. “^^c3^^b6”, for example, is a lowercase a with umlaut.
The TeX log file contains a whole bunch of these messages:
l.139: Unicode char @u8:^^e5^^8f^^82 not defined for Texinfo
Then later things like this:
Missing character: There is no ^^c3 in font cmr10!
Missing character: There is no ^^9f in font cmr10!
Missing character: There is no ^^c3 in font cmr10!
Missing character: There is no ^^9f in font cmr10!
Missing character: There is no ^^c3 in font cmr10!
Missing character: There is no ^^a4 in font cmr10!
I’m not sure this is correct, because it seems to me that “^^c3” is only
part of a longer multi-byte sequence, but this error indicates that
individual bytes are looked up in the font.
--
Ricardo
next prev parent reply other threads:[~2020-10-21 22:08 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 [this message]
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=878sbzut6q.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).