[Top][All Lists]

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

Re: Different base URL for @xref?

From: Alfred M. Szmidt
Subject: Re: Different base URL for @xref?
Date: Wed, 13 May 2009 02:18:31 -0400

   > @ifhtml
   > See @url{http://www.gnu.org/s/libc/manual/html_node/Argp.html,Parsing 
Program Options with Argp}, for details. 
   > @end ifhtml
   > @ifnothtml
   > @xref{argp, , Parsing Program Options with Argp, libc, The GNU C Library 
Reference Manual}, for details.
   > @end ifnothtml
   > And would like to make it a bit nicer.

   You will have to come up with a complete workable scheme, and AFAIK
   it ain't easy.  Keep in mind that the produced output can be moved
   to another directory or even another machine.  The current scheme
   assumes that all the HTML files produced from the manuals live in
   the same parent directory.  If you want something more complex, you
   will have to explain how it will work in general.

I do not think that this should be that hard, we have two types of
manuals, split and non-split.  One could implement the following
variables (a list of three items, with a expansion part),

                  URL                                 SPLIT      NON-SPLIT
  @set baseurldir http://www.gnu.org/s/@page@/manual/ html_node/ html_mono/

makeinfo (or texi2html) could then read this variables, and do the
right thing when expanding sub-sequent cross references.  In the case
of a non-split manual, we would get the url:


and for the split case,


I do not think that for HTML manuals it is common to move things back
and forth, and have the relevant manuals in the parent directory for
info this is always the case.  But people browsing HTML will almost
always have a network connection, or a web server running locally.  In
those cases the URL part of BASEURLDIR could point to
http://localhost/@page@/manual/ or a external webserver.

makeinfo/texi2html would have to expand @page@ appropriatly though.
Switching between different base URLs, if one has many @xrefs might
get cumbersome, but I do not think that this is very common to do.

reply via email to

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