Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vincent Lefevre <vincent@vinc17.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Provide papersize for refcard.dvi
Date: Thu, 7 Aug 2025 00:28:47 +0200	[thread overview]
Message-ID: <20250806222847.GZ2576@qaa.vinc17.org> (raw)
In-Reply-To: <86ikj0s27w.fsf@gnu.org>

On 2025-08-06 22:02:27 +0300, Eli Zaretskii wrote:
> Doesn't PDF generation go through DVI?

No, nowadays, PDF is generated directly with pdfTeX.
Only PostScript is generated through DVI.

> And if it doesn't, then why should we care about DVI nowadays?

Because the file is generated and installed. In the Makefile file:

all-doc: info man dvi ps pdf html

> Anyway, I feel we should take this discussion to the Texinfo list,
> where we will find people who know about TeX and DVI much more than I
> do, and could give some useful advice.

I think that the Texinfo list is mainly about the Texinfo format
and generation from this format. refcard.tex is in plain TeX.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)

  reply	other threads:[~2025-08-06 22:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06 14:53 Vincent Lefevre
2025-08-06 15:33 ` Eli Zaretskii
2025-08-06 16:00   ` Vincent Lefevre
2025-08-06 16:30     ` Eli Zaretskii
2025-08-06 16:47       ` Vincent Lefevre
2025-08-06 19:02         ` Eli Zaretskii
2025-08-06 22:28           ` Vincent Lefevre [this message]
2025-08-07  5:50             ` Eli Zaretskii
2025-08-07  9:05               ` Vincent Lefevre
2025-08-07  9:55                 ` Eli Zaretskii
2025-08-08 16:15                   ` Eli Zaretskii
2025-08-08 17:25                     ` Vincent Lefevre
2025-08-08 17:48                       ` Eli Zaretskii

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=20250806222847.GZ2576@qaa.vinc17.org \
    --to=vincent@vinc17.net \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox