> Hello > > I considered to use fossil for my project but the curernt release is > unusable for me. > > I could not find any way for fossil to store non-text files and serve > them over http with the correct content-type, either inferred by some > magic or specified manually. > > As I would like to use illustrations/diagrams/pictures in the > documentation which I hoped to store in the included wiki there is no > way to do that with fossil. > > A somewhat different issue is easy linking to wiki attachments and/or > SCM objects in the docs. Since the artifacts are technically immutable > just linking to the artifact directly should suffice in most cases as > the link should not change over time but it would be nicer if there > was a way to generate links relative to the repository location so > that the links work also when the repository is moved to another > location. > > Another question is how to reliably link to a particular version vs > latest version of a file which is managed by fossil. > > As the wiki formatting page does not answer these question I suspect > fossil only relies on direct links so far. > > Is there something I am missing here? > > Thanks
basically you need to follow the embedded documentation link on the home page to get some information about this http://www.fossil-scm.org/doc/tip/www/embeddeddoc.wiki Also if you look at http://www.fossil-scm.org/doc/tip/www/branching.wiki you will see that it contains pictures. They are GIFs in the same directory and are linked with a relative link such as <img src="branch01.gif" width=280 height=68> The fossil code that handles this is in src/doc.c if you are interested and can read C (or even if you can't) HTH Eric _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
