Joshua Paine wrote: > On Fri, 2009-12-04 at 16:21 -0500, Daniel Clark wrote: >> I'm missing why you wouldn't want to just implement this as code (in C >> or Javascript) that can translate from fossil wiki markup to markdown >> markup (or whatever) and back. > > Doing it in C, if it's not integrated into fossil core, means to use my > repo correctly, you need my custom version of fossil. Bleh.
The entire point is that if done in this manner people wouldn't *need* custom versions of fossil (or non-fossil plugins) - custom versions of fossil (or non-fossil plugins) would just add the ability to edit text in a user's preferred format (and then convert and save that as fossil wiki format). Fossil itself would only ever "see"/store fossil wiki markup, so users without the custom versions of fossil (or non-fossil plugins) could continue to edit text in fossil wiki format. Users of mainline fossil would not need to know or care that custom versions of fossil (or non-fossil plugins) existed. -- Daniel JB Clark | Sys Admin, Free Software Foundation pobox.com/~dclark | http://www.fsf.org/about/staff#danny _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
