bug-texinfo
[Top][All Lists]
Advanced

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

Re: problem with groff.texi: @ref{} in PDF and HTML fomats


From: G. Branden Robinson
Subject: Re: problem with groff.texi: @ref{} in PDF and HTML fomats
Date: Wed, 27 May 2020 23:37:29 +1000
User-agent: NeoMutt/20180716

Hi Gavin,

Please accept my apologies for the delay.  I kept wanting to produce a
reduced version of the groff Texinfo manual but kept stubbing my toe
against tedium; I use Vim, not Emacs, and if there's a Vim plugin to fix
up all the node links when doing massive chunks of deletion, I don't
know about it.

At 2020-04-27T13:57:58+0100, Gavin Smith wrote:
> I don't know why this happens.  There is no reason that the word "see"
> there should be in HTML output.

In a bit of mixed blessing, the error HTML rendering has gone away since
I reported this.  Did I have a stale version of texinfo.tex, as Werner
Leberg suggested might be the case?  Possibly.

On the other hand, the PDF output still has a problem.  I went back and
checked out the revision that was current as of the time of my problem
report--it's still there, and remains on HEAD.

> I thought maybe that @ref had been redefined as a macro but looking at
> http://git.savannah.gnu.org/cgit/groff.git/tree/doc it doesn't look
> like it.  Could you send me the complete sources you used to get this
> error (including any included files)?  Optionally you could also try
> to reduce the size of the failing input.

I'm not sure what you mean by "included files", but you should be able
to repro this from groff Git HEAD straight from Savannah.

I'm attaching the script I use to build groff; it should work fine
without arguments.

$ git clone git://git.savannah.gnu.org/groff.git
$ cd groff
$ make-groff

Then open build/doc/groff.pdf with your favorite PDF viewer.  In the
first paragraph of section 5.6.5 (Built-in Registers), you should find
the sentence:

        A complete listing of all built-in registers can be found in tie
        E [Register Index], page 235.

> Yes, it looks like it.  This is mysterious but we might be able to see 
> the reason once we solve the other problem.  Again I wonder if @ref 
> has a wrong definition.

Thank you for your work on Texinfo!

Regards,
Branden

Attachment: make-groff
Description: Text document

Attachment: signature.asc
Description: PGP signature


reply via email to

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