On Wed, 14 Aug 2013 11:11:13 +0200, Natacha Porté <[email protected]> wrote:

Hello,

on Wednesday 14 August 2013 at 10:57, j. van den hoff wrote:
problem: on the server the repo is located at

http://fossil.0branch.com/sd

and the cross-links don't work any more since the `sd/' is missing
(specifically, the `quickstart guide' link at the top of the landing page
is not working as you can see). dump question: how can I make the
cross-links work both locally as well as when accessing the server repo?

The fastest solution is to use relative links, since those don't depend
on a particular path prefix.

The cleanest solution is probably to align markdown absolute links to
the not-so-absolute logic used in absolute-looking links in fossil wiki.

which I don't quite understand anyway. I just proceeded by the `fossil' documentation when introducing the `/doc/trunk' bit in the links. so if you don't mind, what exactly do you mean by "use relative links". in my specific case what would I have to use in the markdown file in order to link, e.g., to the file

www/quick.md

so that it works both in the local clone as well as on the given server?

This task is still somewhere in my huge todo list, but I would first
need to come up to speed with all the baseurl wierdness that happened
since I looked at it, and come up with a good idea to deal with the
compatibility breakage it introduces.

since this is my first try at the embedded documentation issue: does this mean that my present problem is specific to the current markdown implementation and not there with the `fossil' wiki
language?

j.



Hoping this helps,
Natacha (who is to blame for markdown-in-fossil)

which is nice since in this way one keeps the option to translate the help pages to other formats and use them outside of the fossil gui.


--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to