On Mon, Jan 25, 2016, at 02:46 PM, Warren Young wrote: > On Jan 25, 2016, at 11:33 AM, John Gabriele <jgabri...@fastmail.fm> > wrote: > > > > So far I've been unable to get inline images to show up. Does the fossil > > wiki support that? > > Yes, but not in a WYSIWYG fashion. You need to use one of the markup > languages to do that. > > Rather than switch the WYSIWYG editor into raw HTML mode, I recommend > that you learn Markdown, which is simpler than either HTML yet broadly > useful.
Thanks. I'm actually a big fan of Markdown, and have used Pandoc for years. I was considering using the wysiwyg editing interface because the wiki was going to be used by non-technical users, but it may be less work to just show them how to write markdown instead. > Fossil Wiki is roughly as powerful as Markdown, but because it > delegates a lot of its power to HTML, Markdown ends up being simpler in > many cases, including this one. > > Markdown is also more broadly useful on the Internet than Wiki syntax, > being built into so many other tools. (Github, blogging platforms, Stack > Exchange…) > > You can get up to speed on Markdown quickly: > > https://daringfireball.net/projects/markdown/basics Thanks. I've actually written my own little example online that I sometimes refer folks to, <http://www.unexpected-vortices.com/sw/rippledoc/quick-markdown-example.html>, though it includes extras that Pandoc supports. > or from “fossil ui” on a local repo: > > http://localhost:8080/md_rules > > Referencing an image attachment from a Markdown-formatted wiki article > requires jumping through a few hoops, but it’s not too horrible: > > 1. Attach the image > 2. Click attachment > 3a. Right-click “Image,” then copy the URL > 3b. Alternately, left-click “Image,” then copy URL from the browser’s > address bar > 4. Add something like this to the wiki article > >  > > Notice that I’ve trimmed the URL down, removing leading and trailing bits > that aren’t necessary here. You can actually abbreviate it further, > since you only need to give as much of that big long hexadecimal number > as is unique in your repository. Five to eight digits should suffice for > a small repo: > >  > This works! Thanks so much, Warren! -- John _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
