> Date: Thu, 14 Feb 2002 14:06:54 -0800 > From: Per Bothner <[EMAIL PROTECTED]> > > If you have two unrelated nodes ending up on the same web-page because > they accidentally have similar names, then that is a more fundamental > problem and anchors isn't going to solve the brokenness.
The anchors do solve this, believe me. The only problem with more than one node on a file is to navigate to the right spot when you click on a link. Anchors cause the browser to get to the right place in this case. > You *will* have navigation problems if there are clashes, even with > anchors, because having unrelated nodes on the same web page because > they have similar names is just confusing and wrong, period. I don't see what problems you envision. There are gobs of documents out there with multiple nodes per file, each one referenced by its anchor, and I never had any problems navigating with any of them. Makeinfo 4.0 was producing a single HTML file with all the nodes on it, and I'm not aware of any problems with that, either. > > she could use that option to get rid of the #anchors in the URLs. > > > > Would that be good enough? > > It would be acceptable to me, but I happen to think it should be the > default. And I think that having the #anchor in the URL bar is not something you should bother about. Can we meet halfway? > In fact, I think rather than a switch to turn anchors on > or off, you should have a switch that generates files names using the > same mangling that you currently use for anchors. Sorry, I don't understand this suggestion. Could you please elaborate? _______________________________________________ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
