groff
[Top][All Lists]
Advanced

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

Re: [Groff] Re: a node is illegal within \X


From: Werner LEMBERG
Subject: Re: [Groff] Re: a node is illegal within \X
Date: Tue, 06 Feb 2001 13:12:20 +0100 (CET)

> >     .de HZ
> >     .ds hhh \\*[hd*mark] \\$3
> >     \X'ps: exec [ /View [/XYZ 44 730 1.0] /Title (\\*[hhh]) /OUT pdfmark'
> >     ..
> > 
> > This works great and I get the marks I want, except that I get
> > a slew of warning messages from groff, one warning message per
> > invocation of .HZ.
> > 
> >     sample.mm:86: a node is illegal within \X
> >     sample.mm:88: a node is illegal within \X
> > 
> > How can I convince groff that everything is copasetic with what
> > I've written?  Or is there a better way to write this?
> 
> Well, i"ll answer my own question.  It turns out that MM will set
> \*[hd*mark] to have a value like "1.2.3\ \ ", and that groff doesn't
> like those escaped spaces.
> 
> I fixed it with a hack to get rid of the two escaped spaces, and
> while I was at it grabbed a few lessons from the recently posted
> pdfmark macros.
> 
>       .de HZ
>       .       ds hhh \\*[hd*mark]
>       .       chop hhh
>       .       chop hhh
>       .       pdfbookmark "\\*[hhh] \\$3"
>       ..

It's difficult to find (good) default values for all nodes in \X.  I
would favor a change in the mm macros which allows finer control over
\*[hd*mark].  J├Ârgen?

On my side, I can change the error messages into warning messages
which can then be suppressed (using the .warn request).

Comments?


    Werner

reply via email to

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