From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] Documentation/process/changes: Escape --options to fix Sphinx output
Date: Sun, 23 Apr 2023 09:55:20 -0600 [thread overview]
Message-ID: <87leiioaon.fsf@meer.lwn.net> (raw)
In-Reply-To: <7e3b424d-2aba-3326-29c8-2ccdbfb12f70@gmail.com>
Akira Yokosawa <akiyks@gmail.com> writes:
> Whereas the summary reads "docs: turn off "smart quotes" in the HTML build",
> the change is also effective in the LaTeX/PDF build.
True...so the title is a bit off, but it is a fix for that build too,
right?
> BTW, Jon, don't you test build pdfdocs these days?
I will confess that I don't do it as often as I should. As you may have
noticed, it takes a little while to run, and the interest in PDF output
is pretty low these days.
> The fix to the pdfdocs build error from Tomi [1] is not yet picked up
> either by Mauro or you ... :-/
>
> [1] https://lore.kernel.org/linux-doc/29380b3e-1daa-3aef-1749-dbd9960ba620@gmail.com/
Media docs patches normally go through the media tree, just like the
original bug did; I had assumed that would happen here as well.
Seemingly not, so I've just picked those patches up into docs-next.
> I waited to see if there is anybody else who hits this build error.
> It looks like I am alone!
>
> If there is so few interest in pdfdocs, it might not be worth keeping
> kernel documentation compatible with PDF build.
Interest is low, but not zero, and I'd prefer to keep it working. It
really helps when somebody tells me that it breaks (it is rather
fragile, alas)!
One of these days I would really like to make a serious attempt to see
if rst2pdf has any hope of ever working for us. Taking latex out of the
picture would simplify so many things.
Thanks,
jon
prev parent reply other threads:[~2023-04-23 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 10:21 [PATCH] Documentation/process/changes: Escape --options to fix Sphinx output Zipeng Zhang
2023-04-20 13:51 ` Jonathan Corbet
2023-04-20 15:40 ` Jonathan Corbet
2023-04-20 17:16 ` Miguel Ojeda
2023-04-22 3:39 ` Akira Yokosawa
2023-04-23 15:55 ` Jonathan Corbet [this message]
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=87leiioaon.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).