From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: mail@nicolasgoaziou.fr, 54220@debbugs.gnu.org, bauermann@kolabnow.com
Subject: [bug#54220] [PATCH] doc: Add "Using TeX and LaTeX" chapter.
Date: Wed, 02 Mar 2022 12:40:25 +0100 [thread overview]
Message-ID: <877d9c37me.fsf_-_@gnu.org> (raw)
In-Reply-To: <87pmn41wh9.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 02 Mar 2022 11:12:46 +0100")
Hi!
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> It’s a top-level chapter, because I couldn’t find any better place, but
>> I think it’s fine.
>
> Hmm, maybe in (possibly renamed) “Application Setup”?
“Application Setup” is about configuration on a foreign distro, so I
don’t think it’s the right place.
Perhaps we need a more general chapter on using things under Guix, where
we could also have (say) a “Working with Python” section, and perhaps we
could move “Installing Debugging Files” there? I thought I’d leave that
for later.
>> +@cindex @TeX{} packages
>> +@cindex @LaTeX{} packages
>> +Guix provides packages for the @TeX{} and @LaTeX{} typesetting systems,
>> +taken from the @uref{https://www.tug.org/texlive/, @TeX{} Live
>> +distribution}. However, because @TeX{} Live is so huge and because
>> +finding your way in this maze is tricky, we thought that you, dear user,
>> +would welcome guidance on how to deploy the relevant packages so you can
>> +compile your @TeX{} and @LaTeX{} documents.
>
> Why single out TeX in particular?
You mean LaTeX, right?
> TeX Live also includes ConTeXt, Xe(La)TeX, Lua(La)TeX etc. I guess
> LaTeX is the most widely known and TeX is the common basis of them
> all, so maybe that’s good enough a reason.
Yeah, I think to most people it’s all the same :-) and LaTeX is by far
the most famous one.
Maybe we could phrase it differently, like “Using TeX, LaTeX, and
Related Tools”?
>> +the features you need---@code{texlive-latex-listings} for the
>> +@code{listings} package, @code{texlive-hyperref} for @code{hyperref},
>> +@code{texlive-beamer} for Beamer, @code{texlive-latex-pgf} for PGF/TikZ,
>
> I’d very much like to avoid giving the old names visibility.
> “texlive-latex-listings” is old as is “texlive-latex-pgf”. It really
> should be “texlive-listings” and “texlive-pgf”.
[...]
Yeah, I can rename at least these two packages in a first patch (I will
have to check the number of rebuilds) and adjust the text to refer to
the new names.
>> +@xref{Invoking guix package, @option{--manifest}}, for more on
>> +manifests. In the future, we plan to provide packages for @TeX{} Live
>> +@dfn{collections}---``meta-packages'' such as @code{fontsrecommended},
>> +@code{humanities}, or @code{langarabic} that provide the set of packages
>> +needed in this particular domain. That will allow you to list fewer
>> +packages.
>
> Working on it!
Yay!
> Perfect!
Thanks, I’m glad it makes sense!
Ludo’.
next prev parent reply other threads:[~2022-03-02 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 9:55 [bug#54220] [PATCH] doc: Add "Using TeX and LaTeX" chapter Ludovic Courtès
2022-03-02 10:12 ` Ricardo Wurmus
2022-03-02 11:40 ` Ludovic Courtès [this message]
2022-03-02 12:11 ` Ricardo Wurmus
2022-03-02 13:45 ` zimoun
2022-03-02 18:28 ` bug#54220: " Ludovic Courtès
2022-03-02 13:42 ` [bug#54220] " zimoun
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=877d9c37me.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=54220@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
--cc=mail@nicolasgoaziou.fr \
--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).