Hi Mike, In general, you can link to the top level of a book (part number) and that will always work. For example, http://docs.sun.com/doc/819-2244
We do have a solution to stable 'deep' links to man pages, based on the ID for the element. I wrote a procedure for creating persistent links to man pages here: http://opensolaris.org/os/community/documentation/reviews/persist_links I believe this concept also applies to element IDs in books, such that you could craft a link to a particular ID that would always be true, until you change or remove that element. -Michelle Mike Pogue wrote: > Hey, everybody! > > There is a bug open on DTrace (6558281 P2 bad url in dtrace script(s?)) that > boils down to making a URL reference in code to documentation that has moved. > So, the permalink turned out to be "not so perma". :-) > > Now, we'll fix this particular case (one way or another), but it does bring > up the larger issue of permalinks, and not just doc->doc, but also code->doc. > Links going from docs -> code seem like a pretty safe thing to do in > practice, but given that docs can and do change (or move around) more > frequently than code does, how much should we encourage/discourage links the > other direction, from code -> docs? Or, alternately, is there a need for > more stable links into the docs? How do other projects solve this? > > Mike > > > This message posted from opensolaris.org > _______________________________________________ > docs-discuss mailing list > docs-discuss at opensolaris.org >
