anchor.diff:  
   == Prerequisites
   
  -All that's needed to use {project-name} is Ruby 1.9.3 or better and a few RubyGems, which we'll explain how to install in the next section.
  -
  -To check if you have Ruby available, use the `ruby` command to query the version installed:
  +All that's needed to use {project-name} is Ruby (1.9.3 or above; 2.2.x recommended) and a few Ruby gems, which we'll explain how to install in the next section.
  +
  +To check if you have Ruby available, use the `ruby` command to query the installed version:
   
    $ ruby --version
   
  -If you're using {rvm-uri}[RVM], we recommend creating a new gemset to work with {project-name}:
  -
  - $ rvm use @asciidoctor-epub3 --create
  -
  -We like RVM because it keeps the dependencies required by various projects isolated ;)
  -
   == Getting Started
   
  -{project-name} isn't yet published as a RubyGem itself, so you'll need to get the source code.
  -
  -=== Retrieve the project
  -
  -You can retrieve {project-name} in one of two ways:
  -
  -. Clone the git repository
  -. Download a zip archive of the repository
  -
  -==== Option 1: Fetch Using `git clone`
  -
  -If you want to clone the git repository, simply copy the {project-repo-uri}[GitHub repository URL] and pass it to the `git clone` command:
  -
  - $ git clone https://github.com/asciidoctor/asciidoctor-epub3
  -
  -Next, change to the project directory:
  -
  - $ cd asciidoctor-epub3
  -
  -==== Option 2: Download the Archive
  -
  -If you want to download a zip archive, click on the btn:[icon:cloud-download[\] 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.
  -
  -We'll now leverage the project configuration to install the necessary dependencies.
  -
  -=== Install the Dependencies
  -
  -The dependencies needed to use {project-name} are defined in the [file]_Gemfile_ at the root of the project.
  -We can use Bundler to install the dependencies for us.
  -
  -To check if 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 bundle
  -
  -Then use the `bundle` command to install the project dependencies:
  -
  - $ bundle install
  -
  -=== Build and Install the Gem
  -
  -Now that the dependencies are installed, you can build and install the Gem.
  -
  -Use the Rake build tool to build the Gem:
  -
  - $ rake build
  -
  -The build will report that it built the Gem into the [path]_pkg_ directory.
  -
  -Finally, install the Gem.
  -
  - $ gem install pkg/asciidoctor-epub3-1.5.0.dev.gem
  -
  -You're now ready to use {project-name}!
  +You can get {project-name} by <<_install_the_published_gem,installing the published gem>> or <<_development,running the code from source>>.
  +
  +=== Install the Published Gem
  +
  +{project-name} is published as a pre-release on RubyGems.org.
  +You can install the published gem using the following command:
  +
  + $ gem install asciidoctor-epub3 --pre
  + 
  +If you want to syntax highlight source listings, you'll also want to install CodeRay or Pygments.
  +Choose one (or more) of the following:
  +
  +.CodeRay
  + $ gem install coderay
  +
  +.Pygments
  + $ gem install pygments.rb
  + 
  +You then activate syntax highlighting for a given document by adding the `source-highlighter` attribute to the document header (CodeRay shown):
  +
  +[source,asciidoc]
  +----
  +:source-highlighter: coderay 
  +----
  +
  +NOTE: At the moment, Pygments is automatically used if it's available.
  +
  +Assuming all the required gems install properly, verify you can run the `asciidoctor-epub3` script:
  +
  + $ asciidoctor-epub3 -v
  +
  +If you see the version of {project-name} printed, you're ready to use {project-name}.
   Let's get an AsciiDoc document ready to convert to EPUB3.
   
   === Prepare an AsciiDoc Document
  
positive.code: 
  // TODO document command to generate the M+ 1p latin fonts
  
  === The text justification hack
  
  Many of the EPUB3 readers use the http://webkit.org[WebKit browser engine] to render the content and apply the CSS formatting and styles.
  Generally speaking, WebKit is a great engine that brings a lot of consistency and power to the e-book reader landscape.
  It also brings along the same set of bugs.
  
  One of the bugs in WebKit causes rich text to be justified incorrectly.
  In particular, when the value of the `text-align` property is `justify`, WebKit drops the space between formatted text (bold, italic, hyperlink, etc) and non-formatted text, causing the words to be unevenly spaced across the line.
  You can see an example of this problem in the screenshot below.
  
  .WebKit justifying rich text incorrectly
  
negative.code: The theme's CSS files are located in the [path]_data/style_ directory.
  
  IMPORTANT: {project-name} only provides one theme, and, at this time, you can not replace it with a custom theme using the `stylesheet` attribute.
  However, you can use your own [path]_epub3.css_ and [path]_epub3-css3-only.css_ files by specifying the directory where they are located using the `epub3-stylesdir` attribute.
  
  === Fonts
  
  