Asciidoctor :: Discussion

The Holy Grail: AsciiDoc on GitHub to DocBook Chain

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 4 messages Options
KurtStam
Reply | Threaded
Open this post in threaded view
♦
♦
|

The Holy Grail: AsciiDoc on GitHub to DocBook Chain

KurtStam
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 git@github.com: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.

mojavelinux
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Holy Grail: AsciiDoc on GitHub to DocBook Chain

mojavelinux
Administrator
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: book

Again, 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.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
mojavelinux
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Holy Grail: AsciiDoc on GitHub to DocBook Chain

mojavelinux
Administrator
In reply to this post by KurtStam
Ah, I just realized you merged it into pressgang-tools (from your fork). That means I can commit there...so if you don't get a chance to make the changes I mentioned, I'll go ahead and update it.

-Dan


On Fri, Apr 12, 2013 at 3:48 PM, Dan Allen <[hidden email]> wrote:
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: book

Again, 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.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597




--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
mojavelinux
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Holy Grail: AsciiDoc on GitHub to DocBook Chain

mojavelinux
Administrator
In reply to this post by KurtStam
I've updated the project to pressgang-tools 3.0.0 and cleaned up a few things in the build and the examples. I advise anyone interested in using the Asciidoctor Maven Plugin to give it a try!

I expect the instructions on the wiki to work:


NOTE: Some features of AsciiDoc, which include line breaks, page breaks and horizontal rules, won't work yet. AsciiDoc adds it's own processing instructions to the DocBook output for these featues that the normal DocBook XSL doesn't understand. AsciiDoc ships with a custom XSL that handles these tags when you run the a2x command. I've committed support for these processing instructions [1] to PressGang and they should be available in the next release.

Enjoy!

-Dan




On Fri, Apr 12, 2013 at 3:49 PM, Dan Allen <[hidden email]> wrote:
Ah, I just realized you merged it into pressgang-tools (from your fork). That means I can commit there...so if you don't get a chance to make the changes I mentioned, I'll go ahead and update it.

-Dan


On Fri, Apr 12, 2013 at 3:48 PM, Dan Allen <[hidden email]> wrote:
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: book

Again, 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.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597




--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597




--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
Free forum by Nabble Edit this page