From: "Alex Bennée" <alex.bennee@linaro.org>
To: virtio-comment@lists.linux.dev
Cc: Michael S. Tsirkin <mst@redhat.com>,
Cornelia Huck <cornelia.huck@redhat.com>,
Bill Mills <bill.mills@linaro.org>
Subject: Use of LaTeX for the specification
Date: Mon, 29 Sep 2025 15:41:18 +0100 [thread overview]
Message-ID: <87ms6dl3sh.fsf@draig.linaro.org> (raw)
Hi,
I recently updated my distro to Trixie and found that HTML generation is
broken. As far as I can tell this comes down to the use of \cline as
shown in this minimal example:
\documentclass{article}
\usepackage{hhline}
\begin{document}
\begin{tabular}{ |l||l|l| }
\hline
Bits & Device Specific & Purpose \\
\cline{1-2}
Read / Write & Device Specific & \\
\cline{1-2}
Purpose & Device Specific & \\
\hline
\end{tabular}
\end{document}
which results in TeX ending early:
! Undefined control sequence.
\f:HBorder ...border-top:1px solid \#\hline:color
;"></td>
l.8 R
ead / Write & Device Specific & \\
?
! Emergency stop.
I'm liaising with Debian and the TexLive authors to try and figure out
whats going on. However it does raise a bigger question for the
specification - why do we use LaTeX?
I don't doubt that is a powerful typesetting system but its arcane
syntax is a bit of a barrier to entry especially for casual
contributors. With the recent breakage I wonder if I'm the canary in the
coal mine and this will potentially be a problem for everyone else once
their TeX setups upgrade.
I'd like to augment the repo with some GitHub actions so we can keep an
upto date rendered draft available as well as some lint checks so we can
avoid introducing dodgy markup. But firstly I want to ask is LaTeX the
right source format for the spec going forward? Is this something
mandated by OASIS or just an accident of history?
Thanks,
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next reply other threads:[~2025-09-29 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 14:41 Alex Bennée [this message]
2025-09-29 16:51 ` Use of LaTeX for the specification Parav Pandit
2025-09-29 18:22 ` Alex Bennée
2025-09-30 12:23 ` Michael S. Tsirkin
2025-09-30 8:03 ` Matias Ezequiel Vara Larsen
2025-09-30 10:14 ` Alex Bennée
2025-09-30 12:16 ` Michael S. Tsirkin
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=87ms6dl3sh.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=bill.mills@linaro.org \
--cc=cornelia.huck@redhat.com \
--cc=mst@redhat.com \
--cc=virtio-comment@lists.linux.dev \
/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