Lo and behold, a native PDF converter for AsciiDoc built with Asciidoctor and Prawn!
No more middleman.
No more DocBook toolchain.
It’s AsciiDoc straight to PDF!
|
Status
|
Asciidoctor PDF is currently alpha software. While the converter handles most AsciiDoc content, there’s still work needed to fill in gaps where conversion is incomplete, incorrect or not implemented. See the milestone v1.5.0 in the issue tracker for details. |
Asciidoctor PDF is made possible by an amazing Ruby Gem named Prawn. And what a gem it is!
Prawn is a nimble PDF writer for Ruby. More important, it’s a hackable platform that offers both high level APIs for the most common needs and low level APIs for bending the document model to accomodate special circumstances.
With Prawn, you can write text, draw lines and shapes and place images anywhere on the page and add as much color as you like. In addition, it brings a fluent API and aggressive code re-use to the printable document space.
Here’s an example that demonstrates how to use Prawn to create a basic PDF document.
require 'prawn'
Prawn::Document.generate 'example.pdf' do
text 'Hello, PDF creation!'
endIt’s that easy. And that’s just the beginning. Skip ahead to Getting started to start putting it use.
Prawn is the killer library for PDF generation we’ve needed to close this critical gap in Asciidoctor. It absolutely takes the pain out of creating printable documents. Picking up from there, Asciidoctor PDF takes the pain out of creating PDF documents from AsciiDoc.
-
Direct AsciiDoc to PDF conversion
-
PDF document outline (i.e., bookmarks)
-
Table of contents page(s)
-
Document metadata (title, authors, subject, keywords, etc)
-
Internal cross reference links
-
Syntax highlighting with CodeRay or Pygments
-
Page numbering
-
Customizable running content (header and footer)
-
“Keep together” blocks (i.e., page breaks avoided in certain block content)
-
Orphan section titles avoided
-
Table border settings honored
-
Font-based icons (currently admonition blocks only)
-
Custom fonts
See WORKLOG.
All that’s needed is Ruby (1.9.3 or better; 2.2.x recommended) and a few Ruby Gems, which we explain how to install in the next section.
To check you have Ruby available, use the ruby command to query the version installed:
$ ruby --version
You can get Asciidoctor PDF by installing the published gem or running the code from source.
Asciidoctor PDF is published in pre-release on RubyGems.org. You can install the published gem using the following command:
$ gem install --pre asciidoctor-pdf
If you want to syntax highlight source listings, you’ll also want to install CodeRay or Pygments. To be safe, go ahead and install both gems:
$ gem install coderay pygments.rb
Assuming all the required gems install properly, verify you can run the asciidoctor-pdf script:
$ asciidoctor-pdf -v
If you see the version of Asciidoctor PDF printed, you’re ready to use Asciidoctor PDF.
Let’s grab an AsciiDoc document to distill and start putting Asciidoctor PDF to use!
If you don’t already have an AsciiDoc document, you can use the example.adoc file found in the examples directory of this project.
See example.adoc.
It’s time to convert the AsciiDoc document directly to PDF.
|
Important
|
You’ll need to the coderay gem installed to run this example since it uses the source-highlighter attribute with the value of coderay.
|
Converting to PDF is a simple as running the asciidoctor-pdf script using Ruby and passing our AsciiDoc document as the first argument.
$ asciidoctor-pdf example.adoc
This command is just a shorthand way of running:
$ asciidoctor -r asciidoctor-pdf -b pdf example.adoc
When the script completes, you should see the file example.pdf in the same directory. Open the example.pdf file with a PDF viewer to see the result.
You’re also encouraged to try converting this README as well as the documents in the examples directory to see more of what Asciidoctor PDF can do.
The pain of the DocBook toolchain should be melting away about now.
The layout and styling of the PDF is driven by a YAML configuration file. To learn how the theming system works and how to create and apply custom themes, refer to the Asciidoctor PDF Theme Guide. You can use the built-in theme files, which you can find in the data/themes directory, as examples.
Asciidoctor PDF also provides a shell script that invokes GhostScript (gs) to optimize and compress the generated PDF with minimal impact on quality.
You must have Ghostscript installed to use it.
Here’s an example usage:
$ ./bin/optimize-pdf example.pdf
The command will generate the file example-optimized.pdf in the current directory.
|
Warning
|
The optimize-pdf script currently requires a Bash shell (Linux, OSX, etc).
We plan to rewrite the script in Ruby so it works across platforms (see issue #1)
|
|
Important
|
The optimize-pdf script relies on Ghostscript >= 9.10.
Otherwise, it may actually make the PDF larger.
Also, you should only consider using it if the file size of the original PDF is > 5MB.
|
If a file is found with the extension .pdfmarks and the same rootname as the input file, it is used to add metadata to the generated PDF document.
This file is necessary to preserve the document metadata since Ghostscript will otherwise drop it.
That’s why Asciidoctor PDF always creates this file in addition to the PDF.
In the spirit of free software, everyone is encouraged to help improve this project.
To contribute code, simply fork the project on GitHub, hack away and send a pull request with your proposed changes.
Feel free to use the issue tracker or Asciidoctor mailing list to provide feedback or suggestions in other ways.
To help develop Asciidoctor PDF, or to simply use the development version, you need to get the source from GitHub. Follow the instructions below to learn how to clone the source and run it from your local copy.
You can retrieve the source of Asciidoctor PDF in one of two ways:
-
Clone the git repository
-
Download a zip archive of the repository
If you want to clone the git repository, simply copy the GitHub repository URL and pass it to git clone command:
$ git clone https://github.com/asciidoctor/asciidoctor-pdf
Next, change to the project directory:
$ cd asciidoctor-pdf
If you want to download a zip archive, click the Download Zip button on the right-hand side of the repository page on GitHub. Once the download finishes, extract the archive, open a console and change to that directory.
|
Tip
|
Instead of working out of the asciidoctor-pdf directory, you can simply add the absolute path of the bin directory to your PATH environment variable.
|
We’ll leverage the project configuration to install the necessary dependencies.
If you’re using RVM, we recommend creating a new gemset to work with Asciidoctor PDF:
$ rvm use 2.2@asciidoctor-pdf --create
We like RVM because it keeps the dependencies required by various projects isolated.
The dependencies needed to use Asciidoctor PDF are defined in the Gemfile at the root of the project. We can use Bundler to install the dependencies for us.
To check you have Bundler available, use the bundle command to query the version installed:
$ bundle --version
If it’s not installed, use the gem command to install it.
$ gem install bundler
Then use the bundle command to install the project dependencies:
$ bundle
|
Note
|
You need to call bundle from the project directory so that it can find the Gemfile.
|
Assuming all the required gems install properly, verify you can run the asciidoctor-pdf script using Ruby:
$ ruby ./bin/asciidoctor-pdf -v
or
$ bundle exec ./bin/asciidoctor-pdf -v
If you see the version of Asciidoctor PDF printed, you’re ready to use Asciidoctor PDF!
|
Caution
|
If you get an error message—and you’re not using a Ruby manager like RVM—you may need to invoke the script through bundle exec:
For best results, be sure to always use bundle exec whenever invoking the ./bin/asciidoctor-pdf script in development mode.
|
Asciidoctor PDF was written by Dan Allen and Sarah White of OpenDevise Inc. on behalf of the Asciidoctor Project.