groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Weird in-line trivial EQN issue with 1.22.4 - bad font number


From: Damian McGuckin
Subject: Re: Weird in-line trivial EQN issue with 1.22.4 - bad font number
Date: Tue, 8 Aug 2023 08:30:49 +1000 (AEST)

On Mon, 7 Aug 2023, Tadziu Hoffmann wrote:

It's an issue with eqn material inside a macro definition.
To avoid expanding eqn-generated escapes at macro definition
time, bracket the macro definition with ".ec #" (or some other
unused character) and ".ec" (to restore backslash as the escape
character after the macro definition).  This way, backslashes
are retained in the macro and escapes are only evaluated at
macro expansion time.

I need to put that into my revision of the EQN documentation.

If this problem is not only in-line EQN code but also .EQ/.EN code, then it would seem to me that any EQN code inside a groff/troff macro is to be avoided. Anything else seems like a recipe for disaster.

Thoughts?

Thanks - Damian



reply via email to

[Prev in Thread] Current Thread [Next in Thread]