public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: tex-live@tug.org
Cc: virtio-comment@lists.linux.dev
Subject: VirtIO html render failure using htlatex
Date: Fri, 03 Oct 2025 18:19:25 +0100	[thread overview]
Message-ID: <87frbzgaxu.fsf@draig.linaro.org> (raw)


Hi,

I was attempting to re-build the VirtIO specifications since upgrading
my main machine to Debian Trixie. The build fails to complete with:

  ! Undefined control sequence.
  \f:HBorder ...border-top:1px solid \#\hline:color 
                                                    ;"></td>
  l.867 R
         ead / Write & Device Specific & \\
  ? 
  ! Emergency stop.
  \f:HBorder ...border-top:1px solid \#\hline:color 

The final result is an empty html file. I verified this was a regression
by running the same build on Bookworm using distrobox. It also works
with the latest Ubuntu. I confirmed it fails on the latest 
texlive image:

  📦[alex@texlive virtio-spec.git]> htlatex --version
  This is pdfTeX, Version 3.141592653-2.6-1.40.28 (TeX Live 2025) (preloaded format=latex)

I've created a minimal test case that triggers the problem:

--8<---------------cut here---------------start------------->8---
\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}
--8<---------------cut here---------------end--------------->8---

save as test.tex and run:

  htlatex test.tex

I'm aware make4ht is an alternative which fails with a slightly
different set of errors:

  📦[alex@texlive virtio-spec.git]> make4ht test.tex "html5"
  [STATUS]  make4ht: Conversion started
  [STATUS]  make4ht: Input file: test.tex
  [ERROR]   htlatex: Compilation errors in the htlatex run
  [ERROR]   htlatex: Filename     Line    Message
  [ERROR]   htlatex: ./test.tex   ?        Undefined control sequence.
  [STATUS]  htlatex:  <- ;"></td> l.8 R ead / Write & Device Specific & \\ The control sequence at the end of the top line
  [ERROR]   htlatex: ./test.tex   ?        Undefined control sequence.
  [STATUS]  htlatex:  <- ;"></td> l.8 R ead / Write & Device Specific & \\ The control sequence at the end of the top line
  [ERROR]   htlatex: ./test.tex   ?        Undefined control sequence.
  [STATUS]  htlatex:  <- ;"></td> l.10 P urpose & Device Specific & \\ The control sequence at the end of the top line
  [ERROR]   htlatex: ./test.tex   ?        Undefined control sequence.
  [STATUS]  htlatex:  <- ;"></td> l.10 P urpose & Device Specific & \\ The control sequence at the end of the top line
  [ERROR]   htlatex: Compilation errors in the htlatex run
  [ERROR]   htlatex: Filename     Line    Message
  [ERROR]   htlatex: ./test.tex   ?        Undefined control sequence.
  [STATUS]  htlatex:  <- ;"></td> l.8 R ead / Write & Device Specific & \\ The control sequence at the end of the top line
  [ERROR]   htlatex: ./test.tex   ?        Undefined control sequence.
  [STATUS]  htlatex:  <- ;"></td> l.8 R ead / Write & Device Specific & \\ The control sequence at the end of the top line
  [ERROR]   htlatex: ./test.tex   ?        Undefined control sequence.
  [STATUS]  htlatex:  <- ;"></td> l.10 P urpose & Device Specific & \\ The control sequence at the end of the top line
  [ERROR]   htlatex: ./test.tex   ?        Undefined control sequence.
  [STATUS]  htlatex:  <- ;"></td> l.10 P urpose & Device Specific & \\ The control sequence at the end of the top line
  [ERROR]   htlatex: Compilation errors in the htlatex run
  [ERROR]   htlatex: Filename     Line    Message
  [ERROR]   htlatex: ./test.tex   ?        Undefined control sequence.
  [STATUS]  htlatex:  <- ;"></td> l.8 R ead / Write & Device Specific & \\ The control sequence at the end of the top line
  [ERROR]   htlatex: ./test.tex   ?        Undefined control sequence.
  [STATUS]  htlatex:  <- ;"></td> l.8 R ead / Write & Device Specific & \\ The control sequence at the end of the top line
  [ERROR]   htlatex: ./test.tex   ?        Undefined control sequence.
  [STATUS]  htlatex:  <- ;"></td> l.10 P urpose & Device Specific & \\ The control sequence at the end of the top line
  [ERROR]   htlatex: ./test.tex   ?        Undefined control sequence.
  [STATUS]  htlatex:  <- ;"></td> l.10 P urpose & Device Specific & \\ The control sequence at the end of the top line
  [STATUS]  make4ht: Conversion finished

Running the same command on Debian Bookworm yields:

  📦[alex@debian-bookworm virtio-spec.git]> make4ht test.tex "html5"
  [STATUS]  make4ht: Conversion started
  [STATUS]  make4ht: Input file: test.tex
  [STATUS]  make4ht: Conversion finished

For references the working versions are:

  📦[alex@debian-bookworm virtio-spec.git]> make4ht --version
  make4ht version v0.3l
  📦[alex@debian-bookworm virtio-spec.git]> htlatex --version
  This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) (preloaded format=latex)

Any suggestions?

Thanks,

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro

             reply	other threads:[~2025-10-03 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 17:19 Alex Bennée [this message]
2025-10-07  8:33 ` VirtIO html render failure using htlatex Manos Pitsidianakis
2025-10-07 13:14   ` Alex Bennée

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=87frbzgaxu.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=tex-live@tug.org \
    --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