Re: Backslashes in macros and texi2html

[Gavin Smith]

On Sat, Oct 22, 2022 at 06:23:43PM +0200, Jean Abou Samra wrote:
> Do you know of a workaround for this? Werner found something
> where the input is changed,
> https://lists.gnu.org/archive/html/lilypond-devel/2022-10/msg00168.html
> but is there, by any chance, a way to write the @warning macro
> differently so as not to trigger this (apparent) bug?

If texi2html has issues with backslashes in macro arguments then you
are not going to fix it by rewriting the macro.  Werner's workaround
seems sensible.  First substitute the macro arguments, then the resulting
text can have macros that expand to backslashes.

Texinfo has a command @backslashchar{} that produces a backslash,
but I don't know if it works with texi2html.  If it does, you could do
@warning{@backslashchar{}command} instead.