bug-texinfo
[Top][All Lists]
Advanced

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

Re: Makeinfo --html produces broken external refs


From: Eli Zaretskii
Subject: Re: Makeinfo --html produces broken external refs
Date: Fri, 06 Jul 2007 13:41:55 +0300

> From: "Sergey Poznyakoff" <address@hidden>
> Date: Thu, 05 Jul 2007 19:34:21 +0300
> Cc: <address@hidden>
> 
> This is a general outline, some minor differences may occur, e.g.   
> those projects that generate their html docs using texi2html quite
> often have also subdirectories html_mono/ and html_chapter/ for
> monolithic and split by chapter versions. But in general it is pretty
> standard by now, in particular because it is promoted by `gendocs.sh'
> script, which is part of Texinfo.

If gendocs.sh is contradicting the Texinfo manual and the code in
makeinfo, I'd suggest to fix gendocs.sh.

> > I think Texinfo currently doesn't support such a feature.
> 
> Partially, it does. I mean @uref and the like.

@uref is a different feature, since it can reference _any_ document.
We were talking about @xref and its ilk, which are cross-references to
other Texinfo manuals.

> Perhaps so... But we are already hardcoding many similar things in the
> docs. The printed document names and even HTTP references (using @uref),
> to name a few. So I don't see why that differs. 

I think others already explained why this differs.

> With the @setxrefurl commands, the base url for any following @xref
> can be reset any place in the document.

If you want a command whose effect is position-dependent, you could
already use @value, can't you?  It has an advantage that you can
control the value from the command line as well.

> > It would be also nice to figure out a convenient way of specifying
> > different prefix URLs for different manuals referenced from the
> > document that is processed.  For example, a FOO manual could xref to a
> > BAR manual on host1 and to BAZ manual on host2.
> 
> Ah, that's exactly what I described above :^)

Sounds like Karl and Patrice have already figured out a way to solve
this.  Their solution sounds better than yours, since there will be a
single place where such things are defined.




reply via email to

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