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: Thu, 22 Oct 2020 22:28:12 +0200 [thread overview]
Message-ID: <87k0vit38j.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ3r3JzjvnE_Gk3SpsO5hVX=EEjFow4BZvRA-GOgp4V1sA@mail.gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> On Thu, 22 Oct 2020 at 21:51, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> ;; XXX: We can't build all formats at this point, nor are they
>> ;; part of the LaTeX base, so we disable them. Actually, we
>> ;; should be running this all in a profile hook, so that only
>> ;; selected formats and hyphenation patterns are included, but it
>> ;; takes long and TeX Live isn't designed to be modular like
>> ;; that. Everything operates on a shared directory, which we
>> ;; would only have at profile generation time.
>> (let ((disabled-formats
>> '("aleph aleph" "lamed aleph" "uptex uptex" "euptex euptex"
>> "eptex eptex" "ptex ptex" "pdfxmltex pdftex" "platex eptex"
>> "csplain pdftex" "mf mf-nowin" "mex pdftex" "pdfmex pdftex"
>> "luacsplain luatex"
>> "cont-en xetex" "cont-en pdftex" "pdfcsplain xetex"
>> "pdfcsplain pdftex" "pdfcsplain luatex" "cslatex pdftex"
>> "mptopdf pdftex" "uplatex euptex" "jadetex pdftex"
>> "amstex pdftex" "pdfcslatex pdftex" "lollipop tex"
>> "xmltex pdftex" "pdfjadetex pdftex" "eplain pdftex"
>> "texsis pdftex" "mltex pdftex" "utf8mex pdftex")))
>
> [...]
>
>> I suspect that the build environment doesn’t have locales set up so the
>> format dumping tool assumes that we want to us Latin-1 encoding for
>> everything. (Roughly speaking, the fmt files are like dumped Lisp
>> images as I understand it.)
>
> I am totally naive here. Is it not one of these disabled formats
> which should not be?
No, the pdftex formats are:
--8<---------------cut here---------------start------------->8---
# from pdftex:
pdftex pdftex language.def -translate-file=cp227.tcx *pdfetex.ini
etex pdftex language.def -translate-file=cp227.tcx *etex.ini
pdfetex pdftex language.def -translate-file=cp227.tcx *pdfetex.ini
--8<---------------cut here---------------end--------------->8---
That’s copied from fmtutil.cfg. The first word on each line is the
format name, the second is the TeX engine. In the list of disabled
formats you see a whole bunch of formats that use the pdftex engine, but
they do not result in pdftex.fmt.
--
Ricardo
next prev parent reply other threads:[~2020-10-22 20:26 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 [this message]
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=87k0vit38j.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 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).