From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Masaharu Noguchi <nogunix@gmail.com>,
jaegeuk@kernel.org, chao@kernel.org
Cc: corbet@lwn.net, linux-f2fs-devel@lists.sourceforge.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
akiyks@gmail.com
Subject: Re: [PATCH v2] Documentation: f2fs: wrap tables in literal code blocks
Date: Mon, 10 Nov 2025 16:36:25 +0700 [thread overview]
Message-ID: <aRGyGTIyUfQGo1kH@archie.me> (raw)
In-Reply-To: <20251109095416.2428351-1-nogunix@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
On Sun, Nov 09, 2025 at 06:54:16PM +0900, Masaharu Noguchi wrote:
> Sphinx LaTeX builder fails with the following error when it tries to
> turn the ASCII tables in f2fs.rst into nested longtables:
>
> Markup is unsupported in LaTeX:
> filesystems/f2fs:: longtable does not support nesting a table.
>
> Wrap the tables in literal code blocks so that Sphinx renders them as
> verbatim text instead. This prevents the LaTeX builder from attempting
> unsupported table nesting and fixes the pdfdocs build.
>
> Akira Yokosawa pointed out that the in-development Sphinx 8.3 latex
> builder already handles these nested tables. I still want to fix the
> current documentation because Sphinx 8.3 is not released yet, and the
> LaTeX build on the stable 8.2.x series (which also requires
> "docutils<0.22" for now) remains broken without this change.
Acked-by: Bagas Sanjaya <bagasdotme@gmail.com>
When Sphinx >=8.3 becomes ubiquitous, we can revisit this and revert
it to restore nested tables.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-11-10 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 9:54 [PATCH v2] Documentation: f2fs: wrap tables in literal code blocks Masaharu Noguchi
2025-11-10 9:36 ` Bagas Sanjaya [this message]
2025-11-10 11:05 ` Akira Yokosawa
2025-11-11 3:28 ` Akira Yokosawa
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=aRGyGTIyUfQGo1kH@archie.me \
--to=bagasdotme@gmail.com \
--cc=akiyks@gmail.com \
--cc=chao@kernel.org \
--cc=corbet@lwn.net \
--cc=jaegeuk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nogunix@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.
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).