Kurt,This is *fantastic*. I played around with it yesterday and, after some hacking on the XSL stylesheet, I ended up with this PDF of the AsciiDoc Quick Reference:I've got a patch coming that will add support for processing instructions that AsciiDoc (or Asciidoctor) inserts into the DocBook output that require mapping to FO elements.One request. Could you upgrade to pressgang-tools 3.0.0 and DocBook 1.76.1? I made that change in my local copy and it works great. Also, if you could change the final name of the PDF to pressgang-tools-example.pdf instead of S-RAMP*?Please note that the current version of the Maven plugin doesn't support changing the doctype, so it needs to be set in the AsciiDoc document for now.:doctype: bookAgain, great work!-Dan--On Thu, Apr 11, 2013 at 2:04 PM, KurtStam [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Hi guys,
I added a template project to the PressGang wiki, see
https://github.com/pressgang/pressgang-tools/wiki/GuideReadme
The directory layout looks like:
├── Guide
│ └── en-US
│ ├── Guide-docinfo.xml
│ ├── Guide.asciidoc
│ ├── GuideExampleChapter.asciidoc
│ ├── GuideReadme.asciidoc
│ ├── GuideSecondExampleChapter.asciidoc
│ └── _Sidebar.asciidoc
├── Home.asciidoc
├── images
│ └── jenkins.png
└── pom.xml
You can simply clone and then copy it to your GitHub wiki to get started.
git clone [hidden email]:pressgang/pressgang-tools.wiki.git
If you have suggestions for improvement, please let me know.
Cheers,
--Kurt
p.s. https://github.com/asciidoctor/asciidoctor/issues/116 (to include the docinfo.xml) is still being worked on.
If you reply to this email, your message will be added to the discussion below:http://discuss.asciidoctor.org/The-Holy-Grail-AsciiDoc-on-GitHub-to-DocBook-Chain-tp111.htmlTo start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAMLDan AllenPrincipal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
Free forum by Nabble | Edit this page |