all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: zimoun <zimon.toutoune@gmail.com>,
	54220-done@debbugs.gnu.org, mail@nicolasgoaziou.fr,
	bauermann@kolabnow.com
Subject: bug#54220: [PATCH] doc: Add "Using TeX and LaTeX" chapter.
Date: Wed, 02 Mar 2022 19:28:53 +0100	[thread overview]
Message-ID: <87y21syzru.fsf_-_@gnu.org> (raw)
In-Reply-To: <87lexs1rin.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 02 Mar 2022 13:11:05 +0100")

Ricardo Wurmus <rekado@elephly.net> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:

[...]

>>> Why single out TeX in particular?
>>
>> You mean LaTeX, right?
>
> Heh, see: that shows how subjective it is :) No, I did mean TeX, because
> in my experience it is extremely uncommon to use TeX directly.

Ah!  I mentioned TeX because technically it’s the basis of everything.

> Nah, it’s fine.  By the time I wrote the last sentence you quoted above
> I had convinced myself that it’s fine to mention TeX (because it’s the
> foundation) and LaTeX (because it’s the most popular).

Alright.

I went ahead and pushed an updated version as
f0efa6afc5f180f778eb320631a71f42bf1b211f.  I kept the section title, but
explicitly mentioned ConTeXt and LuaTeX in the first paragraph.

This is a starting point anyway, so everyone please feel free to update
it as you see fit or when things change.

Thanks for the quick feedback!

Ludo’.




  parent reply	other threads:[~2022-03-02 18:38 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
2022-03-02 12:11     ` Ricardo Wurmus
2022-03-02 13:45       ` zimoun
2022-03-02 18:28       ` Ludovic Courtès [this message]
2022-03-02 13:42   ` 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

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

  git send-email \
    --in-reply-to=87y21syzru.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=54220-done@debbugs.gnu.org \
    --cc=bauermann@kolabnow.com \
    --cc=mail@nicolasgoaziou.fr \
    --cc=rekado@elephly.net \
    --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.