I suspect the answer to this is going to be a negative (for reasons I'll explain below), but let me explain the issue first:
I've just refactored rather a large chunk of documentation to improve it's structure: it was all cut and paste, moving stuff around, very easy really. Except for one thing: none of my hyperlinks work anymore because now the structure has changed the names of all the section targets have changed too! So now I face a long and tedious task of fixing up all the links, and that's not going to be much fun :-( As an aside: Last time I built the full Boost docs (cvs HEAD) I noticed rather a lot of broken link messages, so I suspect I'm not alone here. So now the "what if": what if I wrote: [section:some_id title] and some_id was a *stable* name for that section, no matter where it got moved too? It sure would save a lot of work, and I suspect a lot of future breakages too. We could do this by just using "library_name.some_id" as the linkend, but I guess we're not doing that because of the risk of conflicts? Note that we can't use an explicit anchor inside a section block, so that doesn't work either, and: [#name] [section ..] links to the preceding page, while: [section ...] [#name] scrolls the title off the top of the page when you click through to it :-( Grrrrr. But what I'd really like is for a sort of quickbook preprocessing phase: go through and gather up all the section names, make each one a template that links to that section (wherever it is) using the title of that section (whatever it is) as the link text. So now I can just write: See [sf_gamma] and I'll get a link to the docs for tgamma which reads "Gamma". But of course this really messes up quickbook's internals I guess? Anyone have any better ideas? Cheers, John. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
