Using AsciiDoc for Documentation

Rob Gowin robg at gowin.net
Tue Sep 1 14:44:39 EDT 2015


> On Sep 1, 2015, at 4:56 AM, Mike Evans <mikee at saxicola.co.uk> wrote:
>> [snip]
> 
> Hi Rob
> 
> Looks good to me. Still a few minor bugs with the Asciidoc.  
> 
> Some of the Figure titles are missing
> Second level bullet indents missing
> 
> But these are minor and some tweaking of the XSL should fix that.  Speaking of which, I notice the XSL isn't in github can you make that available somewhere so others can chip in with help? I'd also like to generate the Asciidoc locally so I can ensure both formats are from the same source for comparison purposes.
> 
> Now you (we) have to convince others to use Asciidoc!
> 
> I use Geany for my coding/writing and there is a Markdown plugin for preview, no Asciidoc at the moment though.  I'm looking at the PEG code to see how difficult it would be to produce an Asciidoc previewer plugin.  It may be beyond my learning tolerance though.
> 
> Mike E
> 
> 
> 
> -- 
> PGP key:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x00CDB13500D7AB53  


Hi Mike,

Thanks for taking a look. I have put the XSL file and a python
script to run the conversion process in a repository at 
https://github.com/codesmythe/asciidoc-conversion. See the README
there for details.

As for editors, I just use a command line converter and then
reload the generated HTML into a browser. I need to try some of the
live preview editors mentioned in the link you sent out yesterday.

I'll look at the issues you mentioned in the next couple of days.

Thanks,

Rob






More information about the gnucash-devel mailing list