especially since 'make html' is optional
according to GNU Coding standards
html/ps/pdf were added as standard targets not too long ago. Of course
that doesn't mean you have to support them instantly -- there isn't even
a released release of Autoconf that has them yet, though CVS Autoconf
does.
> I concur that a relative link to a user's local html installation would
In theory, sure, but I don't see how we can automatically deduce what an
installation's web site looks like :).
As far as Texinfo's future goes, my only idea is to have a config file
for handling cross-manual references, and the default will be to use the
online manuals on http://www.gnu.org. System packagers could hopefully
change/override that to use local copies if they try to build a
systematic HTML tree of Texinfo files (I'm not sure anyone does). I
doubt individual admins would bother, unless they were bored and
underworked :).
When and whether I'll ever actually implement it, time will tell.
best,
karl
_______________________________________________
M4-patches mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/m4-patches
