On Thu, Aug 14, 2014 at 3:27 AM, Gour <g...@atmarama.net> wrote:
> the topic of the markup in Fossil is quite an old one and in the past
> there was
> a thread about using AsciiDoc markup which can be rendered with
I looked at AsciiDoc. In theory, it's nice, but it appears to have gathered
a huge number of features over the years. It really appears to try to be
"LaTeX Light".
Also, it uses [ and ] for purposes other than "wiki links" (as many wiki
mark-ups use) , so using it as an alternative to either Fossil's native
wiki mark-up or to mark-down would be awkward for many users.
Last I checked (2 years ago?), other than the JASON API, Fossil's web
interface did not provide an easy means for a client side mark-up renderer
to identify the file content.
While the JSON API is very nice, I still think there would be value in
Fossil's generated HTML putting a clearly identifiable <div> around the
content. Maybe like:
<div class="user_content" filename="filename.ext">
Then a client side handler could easily extract both the content and the
filename/extension with which it could dispatch the appropriate renderer.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
