But that's not what I meant. What I meant is like in the file system:
absolute paths start at the root. So e.g. (imaginary)
[[Documentation/UserGuide/GettingStarted/chapter1]]
is an absolute path, while relative paths start with the present
document's path, so to link to the above Page from another chapter,
let's say from
[[Documentation/UserGuide/GettingStarted/chapter2]]
you can simply write [[../chapter1]]
Relative links are not used because hardly anyone knows about them.
I still find that people are using the full http path for links within
the Wiki... so a link to the next page shows as an external link instead
of an internal link. :-(
The only discrepancy is that path names starting with a slash are
interpreted as childs from the present document. So from the page
[[Documentation/UserGuide/GettingStarted]]
the link
[[/chapter1]] and [[/chapter2]] lead to the above subpages (and do not
represent absolute pathnames like in dos or unix filesystem naming
conventions).
Mmmm within the Wiki structure, this makes sense though. The base page
should never be slash something (have a leading slash). Some people,
myself included, have created base pages with a leading slash, and it
creates all sorts of interesting problems.
I can see how using relative links would help with translations. Are
there any "gotchas" that anyone can think of with using relative links?
What about with transcluded content? The User Guides use a lot of
transluded pages....
Changing existing pages over... ouch. Not sure the WikiBot can handle
this. Doing it manually would be a painful process. Ideas?
C.
--
Clayton Cornell [email protected]
OpenOffice.org Documentation Project co-lead
StarOffice - Sun Microsystems, Inc. - Hamburg, Germany
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
