Hi Stuart, > I tried it on the DocBook generated by asciidoc from book.txt in the asciidoc > distribution (http://code.google.com/p/asciidoc/source/browse/doc/book.txt) > then > round-tripped it to HTML with asciidoc and PDF with a2x -- both compiled > without > errors!
Thanks for testing it out. That's great! > I've attached the input book.xml and output book.txt. As you've pointed out > some > elements are yet to be translated, but it's great leg-up when you're faced > with > a translation like this (we've had questions in the past asking for exactly > this > functionality). > > I've added a link to your project to the list of 'External Resources and > Applications' in the AsciiDoc homepage > (http://www.methods.co.nz/asciidoc/#X2). Cool, thanks. Maybe others will contribute to it. > PS: I've got more ebooks from O'Reilly than from any other publisher, it's > gratifying to think that some may have been processed by AsciiDoc. Many authors respond enthusiastically to writing in AsciiDoc. :-) The XSLT was developed specifically for a new edition of Learning Android. I believe the author likes AsciiDoc so much that he started using it for all of his internal documentation at his company. -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
