public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Cc: tex-live@tug.org,  virtio-comment@lists.linux.dev,  tex4ht@tug.org
Subject: Re: VirtIO html render failure using htlatex
Date: Tue, 07 Oct 2025 14:14:58 +0100	[thread overview]
Message-ID: <875xcqzwdp.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAAjaMXb+_DXG+P+3-bVAOCcSgSO-OVEWFX6-JNNbbyRoFTy0iA@mail.gmail.com> (Manos Pitsidianakis's message of "Tue, 7 Oct 2025 11:33:39 +0300")

Manos Pitsidianakis <manos.pitsidianakis@linaro.org> writes:

> On Fri, Oct 3, 2025 at 8:19 PM Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>>
>> 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 problem are the tabular environment's \cline macros in
> transport-pci.tex, removing them will make compilation work.
>
> Perhaps this tex4ht version does not define it like it defines \hline?
>
> CC'ing tex4ht mailing list.

Karl already forwarded it:

  https://tug.org/pipermail/tex4ht/2025q4/003775.html

and:

  https://svn.gnu.org.ua/viewvc/tex4ht/trunk/lit/tex4ht-html4.tex?r1=1750&r2=1749&pathrev=1750

I'm going to roll the workaround in my virtio spec patches in a bit.

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro

      reply	other threads:[~2025-10-07 13:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 17:19 VirtIO html render failure using htlatex Alex Bennée
2025-10-07  8:33 ` Manos Pitsidianakis
2025-10-07 13:14   ` Alex Bennée [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=875xcqzwdp.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=manos.pitsidianakis@linaro.org \
    --cc=tex-live@tug.org \
    --cc=tex4ht@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