asciidoctor-pdf 1.5.0.beta.7 → 1.5.0.beta.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4d563652f77af3a20dcc19c756b55981f7a0efaea638a4678087ca95f12a3048
-  data.tar.gz: e335e4b4ad2487ced3f7ab927bbdb8711aa64405987365b41fc7f6695a19a5ac
+  metadata.gz: 4971b7ad193cc6b81346ac764010d20b46bbfdd66986e601938fcca2cd3929ba
+  data.tar.gz: 86076a5fcb2bc9f6fbb54b8479f04be26a576b207be08ea5b504013dec48ef72
 SHA512:
-  metadata.gz: c0129884c47560e43eb28149451c618160bfcafe68112fb3d247ec67bae13a3f47130cd65dac9b140c2f20e3eaef8d96661b749afea7a1bed2054cdf7c16b8a4
-  data.tar.gz: 7ece71b33af340fac13ffa6e78187e86c25c38f7f0d472a02aaaea8c8cffda5bf5ccd560f4a5a2e914eaaa1dd9730bf4cfef0d9e931b4b60305b6fc065eff429
+  metadata.gz: 940b1a41aa08c0950fb9e609f1ab5cf5c960bee9535cbd5710306b5c7a20d30794ec41fa2ea4b0a78a9c11f5d53262e6bac25417777f6a96e2fded72dd5d121c
+  data.tar.gz: 3017ce6726c7cae78b59394fe12be84587e691375c9e11f196384d42b8a254d2f10201e110503af1447eb456c0e070d90e7d1c0f7099e4e87057d2a4c69606ff

data/CHANGELOG.adoc

@@ -5,6 +5,38 @@
 This document provides a high-level view of the changes to the {project-name} by release.
 For a detailed view of what has changed, refer to the {uri-repo}/commits/master[commit history] on GitHub.
 
+== 1.5.0.beta.8 (2019-11-23) - @mojavelinux
+
+* automatically hyphenate prose using the text-hyphen gem if the `hyphens` document attribute is set (#20)
+* set hyphenation language using the `hyphens` attribute value, falling back to the `lang` attribute (#20)
+* add support for capitalize text transform (#1382)
+* fix AsciiDoc table cell from overflowing bounds of table and creating extra page (#1369)
+* don't double escape XML special characters in literal table cell (#1370)
+* allow theme to customize the width and color of text decoration (underline and line-through) (#812)
+* use same line height throughout abstract
+* don't mangle XML attribute values when applying lowercase text transform (#1391)
+* place toc at same position in outline as it is in the document (#1361)
+* log warning with error message if remote image cannot be retrieved
+* allow initial page mode to be set to fullscreen using pdf-page-mode=fullscreen attribute or page_mode=fullscreen theme key (#1357)
+* allow theme to configure content of entries in authors line on title page (#800)
+* allow theme to override styles of caption on admonition blocks (#561)
+* allow theme to configure hanging indent for titles in toc (#1153)
+* apply hanging indent to wrapped entries in index (#645)
+* allow theme to configure text decoration of headings (#811)
+* define line-through and underline roles as built-in custom roles so they can be customized (#1393)
+* allow top value of logo and title on title page to be specified in any measurement unit
+* don't set a top value for the logo on the title page if not set in theme
+* if value of scripts attribute is cjk, break lines between any two CJK characters except punctuation in table cells (#1359) (*gasol*)
+* ignore invalid cellbgcolor value (#1396)
+* recommend installing prawn-gmagick gem if image format is unsupported
+* set cache_images option on SVG interface if cache-uri attribute is set on document (#223)
+* upgrade prawn-svg to fix display of links in plantuml diagrams (#1105)
+* allow icon set to be specified as prefix on target of icon macro (#1365)
+* write Unix epoch dates to pdfmark file in UTC when reproducible is set
+* don't include software versions in PDF info if reproducible attribute is set
+* fix optimizer so it applies pdfmark after reading input file
+* allow converter instance to be reused
+
 == 1.5.0.beta.7 (2019-10-29) - @mojavelinux
 
 * fix value of implicit page-count attribute when page numbering and running content don't start on same page (#1334)

data/README.adoc

@@ -1,6 +1,6 @@
 = Asciidoctor PDF: A native PDF converter for AsciiDoc
 Dan Allen <https://github.com/mojavelinux[@mojavelinux]>; Sarah White <https://github.com/graphitefriction[@graphitefriction]>
-v1.5.0.beta.7, 2019-10-29
+v1.5.0.beta.8, 2019-11-23
 // Settings:
 :experimental:
 :idprefix:
@@ -12,7 +12,6 @@ ifdef::env-github,env-browser[]
 endif::[]
 ifdef::env-github[]
 :status:
-:outfilesuffix: .adoc
 :!toc-title:
 :caution-caption: :fire:
 :important-caption: :exclamation:
@@ -24,7 +23,7 @@ endif::[]
 :project-name: Asciidoctor PDF
 :project-handle: asciidoctor-pdf
 // Variables:
-:release-version: 1.5.0.beta.7
+:release-version: 1.5.0.beta.8
 // URIs:
 :url-asciidoctor: http://asciidoctor.org
 :url-gem: http://rubygems.org/gems/asciidoctor-pdf
@@ -95,7 +94,7 @@ endif::[]
 == Highlights
 
 * Direct AsciiDoc to PDF conversion
-* <<docs/theming-guide#,Configuration-driven theme (style and layout)>>
+* <<docs/theming-guide.adoc#,Configuration-driven theme (style and layout)>>
 * SVG support
 * PDF document outline (i.e., bookmarks)
 * Table of contents page(s)
@@ -162,7 +161,7 @@ ERROR:  While executing gem ... (Gem::FilePermissionError)
     You don't have write permissions for the /Library/Ruby/Gems/2.x.x directory.
 ....
 
-A better practice (and one that will ensure your sanity) is to ignore any version of Ruby installed on your system and use https://rvm.io[RVM] to manage the Ruby installation instead.
+A better practice (and one that will ensure your sanity) is to ignore any version of Ruby installed on your system and use {url-rvm}[RVM] to manage the Ruby installation instead.
 The benefit of this approach is that a) Ruby is guaranteed to be set up correctly, b) installing gems will in no way interfere with the operation of your system, and c) any bin scripts provided by the installed gems will be available on your PATH.
 All files are managed in user space (aka your home or user directory).
 If something gets messed up, you can simply remove the [.path]_$HOME/.rvm_ folder and start over.
@@ -247,10 +246,10 @@ Let's grab an AsciiDoc document to distill and start putting {project-name} to u
 
 === An Example AsciiDoc Document
 
-If you don't already have an AsciiDoc document, you can use the <<examples/basic-example#,basic-example.adoc>> file found in the examples directory of this project.
+If you don't already have an AsciiDoc document, you can use the <<examples/basic-example.adoc#,basic-example.adoc>> file found in the examples directory of this project.
 
 ifeval::[{safe-mode-level} >= 20]
-See <<examples/basic-example#,basic-example.adoc>>.
+See <<examples/basic-example.adoc#,basic-example.adoc>>.
 endif::[]
 ifeval::[{safe-mode-level} < 20]
 .basic-example.adoc
@@ -284,7 +283,7 @@ Open the [.path]_basic-example.pdf_ file with a PDF viewer to see the result.
 image::examples/example-pdf-screenshot.png[Screenshot of PDF document,width=850,467,scaledwidth=100%]
 
 ifndef::env-site[]
-You're also encouraged to try converting this <<README#,README>> as well as the documents in the examples directory to see more of what {project-name} can do.
+You're also encouraged to try converting this <<README.adoc#,README>> as well as the documents in the examples directory to see more of what {project-name} can do.
 endif::[]
 
 The pain of the DocBook toolchain should be melting away about now.
@@ -292,7 +291,7 @@ The pain of the DocBook toolchain should be melting away about now.
 == Themes
 
 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 <<docs/theming-guide#,Asciidoctor PDF Theme Guide>>.
+To learn how the theming system works and how to create and apply custom themes, refer to the <<docs/theming-guide.adoc#,Asciidoctor PDF Theme Guide>>.
 You can use the built-in theme files, which you can find in the [.path]_data/themes_ directory, as examples.
 
 If you've enabled a source highlighter, you can control the style (aka theme) it applies to source blocks using the `coderay-style`, `pygments-style`, and `rouge-style` attributes, respectively.
@@ -301,7 +300,7 @@ For example, to configure Rouge to use the built-in monokai theme, run Asciidoct
  $ asciidoctor-pdf -a rouge-style=monokai basic-example.adoc
 
 It's possible to develop your own theme for Rouge.
-Refer to the <<docs/theming-guide#,Asciidoctor PDF Theme Guide>> for details.
+Refer to the <<docs/theming-guide.adoc#,Asciidoctor PDF Theme Guide>> for details.
 
 === Support for Non-Latin Languages
 
@@ -590,7 +589,7 @@ The result becomes indistinguishable from other PDF objects.
 What that means for text is that any font family used for text in the SVG _must_ be registered in the Asciidoctor PDF theme file (and thus with Prawn).
 Otherwise, Prawn will fallback to using the closest matching built-in (afm) font from PDF (e.g., sans-serif becomes Helvetica).
 Recall that afm fonts only support basic Latin.
-As we like to say, PDF is <<docs/theming-guide#built-in-afm-fonts,bring your own font>>.
+As we like to say, PDF is <<docs/theming-guide.adoc#built-in-afm-fonts,bring your own font>>.
 
 If you're using Asciidoctor Diagram to generate SVGs to embed in the PDF, you likely need to specify the default font the diagramming tool uses.
 Let's assume you are making a plantuml diagram.
@@ -992,218 +991,8 @@ hexapdf also allows you to add password protection to your PDF, if that's someth
 ifndef::env-site[]
 == Contributing
 
-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.
-*All pull requests must include a) tests that verify the code change and b) an entry in the CHANGELOG.adoc file to document what changed.*
-If a pull request is missing tests or a CHANGELOG entry, *it will not be merged*.
-
-Feel free to use the {url-project-issues}[issue tracker] or {url-project-list}[Asciidoctor mailing list] to provide feedback or suggestions in other ways.
-
-== Development
-
-To help develop {project-name}, 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.
-
-=== Retrieve the Source Code
-
-You can retrieve the source of {project-name} in one of two ways:
-
-. Clone the git repository
-. Download a zip archive of the repository
-
-==== Option 1: Fetch Using Git
-
-If you want to clone the git repository, simply copy the {url-project-repo}[GitHub repository URL] and pass it to the `git clone` command:
-
- $ git clone https://github.com/asciidoctor/asciidoctor-pdf
-
-Next, change to the project directory:
-
- $ cd asciidoctor-pdf
-
-==== Option 2: Download the Archive
-
-If you want to download a zip archive, click the btn:[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 {project-handle} directory, you can simply add the absolute path of the [path]_bin_ directory to your `PATH` environment variable.
-
-We'll leverage the project configuration to install the necessary dependencies.
-
-=== Install Dependencies
-
-We recommend using {url-rvm}[RVM] to manage the installation of Ruby you'll use to build and develop the project.
-
- $ rvm use 2.6
-
-The dependencies needed to use {project-name} are defined in the [.path]_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 installed version:
-
- $ bundle --version
-
-If it's not installed, use the `gem` command to install it.
-
- $ gem install bundler
-
-Then use the `bundle` command with the `--path` option to install the project dependencies into the project:
-
- $ bundle --path=.bundle/gems
-
-NOTE: You must call `bundle` from the project directory so that it can find the [.path]_Gemfile_.
-
-=== Run the Tests
-
-Tests are written using RSpec.
-To run the tests, simply invoke rspec via bundler.
-
- $ bundle exec rspec
-
-To disable the visual integration tests, pass the `` option:
-
- $ bundle exec rspec -t ~visual
-
-If a visual integration test fails, you can instruct the test suite to keep the files in the [.path]_spec/output_ directory by setting the `DEBUG` environment variable:
-
- $ DEBUG=true bundle exec rspec -t visual
-
-If you want to see the name of each test as it is run, add the `-fd` option:
-
- $ bundle exec rspec -fd
-
-You can also use the provided Rake task (note the name difference):
-
- $ bundle exec rake spec
-
-Running tests using `rspec` directly gives you the advantage of being able to specify additional options.
-
-To run a single test, you can filter by the name of the test.
-For example, to run all tests that pertain to failures, use:
-
- $ bundle exec rspec -e fail
-
-To run all tests that have `wip` in the name, use:
-
- $ bundle exec rspec -e wip
-
-You can also run all tests in a given file by passing the file's path to rspec:
-
- $ bundle exec rspec spec/toc_spec.rb
-
-For a full list of options that rspec provides, run `rspec -h`.
-
-=== Run the Application (optional)
-
-Like with Bundler, you have to run the application from the project directory.
-Assuming all the required gems install properly, verify you can run the `asciidoctor-pdf` script using Ruby:
-
- $ bundle exec asciidoctor-pdf -v
-
-If you see the version of {project-name} printed, you're ready to use {project-name}!
-
-You can use the application to convert a document as follows:
-
- $ bundle exec asciidoctor-pdf /path/to/sample.adoc
-
-=== Install the Application (optional)
-
-If you want to install the application globally so you can run it anywhere, use the following `rake` task:
-
- $ bundle exec rake install
-
-This task will package the gem and install it into your system gems.
-
-If you want to install the gem using a separate command, first use the following `rake` task to build it:
-
- $ rm -rf pkg
-   bundle exec rake build
-
-This task packages the application as a gem and writes it to the [.path]_pkg_ directory.
-A message will be printed to the console telling you the exact filename.
-You can now use the `gem install` command to install it.
-
- $ gem install pkg/*.gem
-
-You'll want to pay attention to which Ruby installation you are installing the gem into.
-If successful, the `asciidoctor-pdf` executable will be available on your PATH.
-
-endif::[]
-
-=== Test a Pull Request
-
-To test a pull request (PR), you first need to fetch the branch that contains the change and switch to it.
-The steps below are covered in detail in the https://help.github.com/articles/checking-out-pull-requests-locally[GitHub help].
-
-Let's assume you want to test PR 955.
-Here's how you fetch and switch to it:
-
- $ git fetch origin pull/955/head:pr-955-review
-   git checkout pr-955-review
-
-IMPORTANT: Make sure you replace the number with the number of the PR you want to test.
-
-In case any dependencies have changed, you should run the `bundle` command again:
-
- $ bundle
-
-Now you can run the application as modified by the PR:
-
- $ bundle exec asciidoctor-pdf /path/to/sample.adoc
-
-To switch back to master, just type:
-
- $ git checkout master
-
-=== Generate Code Coverage Report
-
-To generate a code coverage report when running tests using simplecov, set the `COVERAGE` environment variable as follows when running the tests:
-
- $ COVERAGE=true bundle exec rake spec
-
-You'll see a total coverage score as well as a link to the HTML report in the output.
-The HTML report helps you understand which lines and branches were missed, if any.
-
-Despite being fast, the downside of using simplecov is that it misses code branches.
-You can use deep-cover instead of simplecov to generate a more thorough report.
-To do so, set the `COVERAGE` environment variable to `deep` when running the tests:
-
- $ COVERAGE=deep bundle exec rake spec
-
-You'll see a total coverage score, a detailed coverage report, and a link to HTML report in the output.
-The HTML report helps you understand which lines and branches were missed, if any.
-
-////
-As an alternative to deep cover's native HTML reporter, you can also use istanbul / nyc.
-First, you'll need to have the `nyc` command available on your system:
-
- $ npm install -g nyc
-
-Next, in addition to the `COVERAGE` environment variable, also set the `DEEP_COVER_REPORTER` environment variable as follows when running the tests:
-
- $ COVERAGE=deep DEEP_COVER_REPORTER=istanbul bundle exec rake spec
-
-You'll see a total coverage score, a detailed coverage report, and a link to HTML report in the output.
-The HTML report helps you understand which lines and branches were missed, if any.
-////
-
-=== Rebuild the Formatter Text Parser
-
-The formatted text is first converted to a pseudo-HTML language, then converted from there into Prawn text fragments using a https://github.com/cjheath/treetop[treetop] parser.
-treetop is a Ruby-based parsing DSL based on parsing expression grammars.
-This strategy allows the converter to manipulate the formatted text without needing the know the internal details of how Prawn arranges text fragments.
-It also allows Asciidoctor to behave in a consistent manner, since some of the inline parsing in Asciidoctor assumes that the converter is generating an SGML-based language like HTML or DocBook.
-
-The parsing expression grammar is defined in the source file [.path]_lib/asciidoctor/pdf/formatted_text/parser.treetop_.
-If you make a change to this file, you must regenerate the parser, which is defined in the source file _lib/asciidoctor/pdf/formatted_text/parser.rb_.
-(Don't modify the generated parser directly).
-
-Use the following command to regenerate the parser:
-
- bundle exec tt lib/asciidoctor/pdf/formatted_text/parser.treetop
-
-You then need to commit both files.
+See the <<CONTRIBUTING.adoc#,contributing guide>>.
+To help develop {project-name}, or to simply use the development version, refer to the <<CONTRIBUTING-CODE.adoc#,developing and contributing code guide>>.
 
 [[resources,Links]]
 == Resources
@@ -1219,5 +1008,5 @@ You then need to commit both files.
 Copyright (C) 2014-2019 OpenDevise Inc. and the Asciidoctor Project.
 Free use of this software is granted under the terms of the MIT License.
 
-For the full text of the license, see the <<LICENSE#,LICENSE>> file.
-Refer to the <<NOTICE#,NOTICE>> file for information about third-party Open Source software in use.
+For the full text of the license, see the <<LICENSE.adoc#,LICENSE>> file.
+Refer to the <<NOTICE.adoc#,NOTICE>> file for information about third-party Open Source software in use.

data/asciidoctor-pdf.gemspec

@@ -37,7 +37,7 @@ Gem::Specification.new do |s|
   s.add_runtime_dependency 'prawn', '~> 2.2.0'
   s.add_runtime_dependency 'prawn-table', '~> 0.2.0'
   s.add_runtime_dependency 'prawn-templates', '~> 0.1.0'
-  s.add_runtime_dependency 'prawn-svg', '~> 0.29.0'
+  s.add_runtime_dependency 'prawn-svg', '~> 0.30.0'
   s.add_runtime_dependency 'prawn-icon', '~> 2.5.0'
   s.add_runtime_dependency 'safe_yaml', '~> 1.0.0'
   s.add_runtime_dependency 'thread_safe', '~> 0.3.0'

data/bin/asciidoctor-pdf

@@ -13,12 +13,7 @@ options = Asciidoctor::Cli::Options.new backend: 'pdf', header_footer: true
 # FIXME provide an API in Asciidoctor for sub-components to print version information
 unless ARGV != ['-v'] && (ARGV & ['-V', '--version']).empty?
   $stdout.write %(Asciidoctor PDF #{Asciidoctor::PDF::VERSION} using )
-  # NOTE the print_version method was added in Asciidoctor 1.5.2
-  if options.respond_to? :print_version
-    options.print_version
-  else
-    puts %(Asciidoctor #{::Asciidoctor::VERSION} [http://asciidoctor.org])
-  end
+  options.print_version
   exit 0
 end
 

data/data/themes/base-theme.yml

@@ -21,6 +21,8 @@ base_font_style: normal
 base_line_height: 1.15
 base_border_color: 'EEEEEE'
 base_border_width: 0.5
+role_line-through_text_decoration: line-through
+role_underline_text_decoration: underline
 role_big_font_size: 14
 role_small_font_size: 10
 button_content: '[%s]'

data/data/themes/default-theme.yml

@@ -53,6 +53,10 @@ base:
   border_radius: 4
   border_width: 0.5
 role:
+  line-through:
+    text_decoration: line-through
+  underline:
+    text_decoration: underline
   big:
     font_size: $base_font_size_large
   small:

data/docs/theming-guide.adoc

@@ -438,6 +438,14 @@ Text can be aligned as follows:
 * right
 * justify (stretched to each edge)
 
+==== Text Decorations
+
+The following decorations can be applied to text:
+
+* none (no decoration)
+* underline
+* line-through
+
 ==== Image Alignments
 
 Images can be aligned as follows:
@@ -465,6 +473,7 @@ The following transforms are recognized:
 
 * uppercase
 * lowercase
+* capitalize (each word, like CSS)
 * none (clears an inherited value)
 
 [CAUTION#transform-unicode-letters]
@@ -480,8 +489,6 @@ or
  $ gem install unicode
 ====
 
-// Additional transforms, such as capitalize, may be added in the future.
-
 === Colors
 
 The theme language supports color values in three formats:
@@ -986,8 +993,10 @@ Each time a theme is loaded, the keys are overlaid onto the keys from the previo
 
 The keys in the `role` category define custom roles for formatting.
 The name of the role is the first subkey level.
-The role name may not contain an underscore.
-The keys under the role are the concrete theming properties.
+The role name may contain a hyphen, but *a role name cannot contain an underscore*.
+The keys under the role are the theming properties.
+
+IMPORTANT: Custom roles only apply to inline phrases.
 
 Here's an example of a role for making text red:
 
@@ -1005,7 +1014,21 @@ This role can be used as follows:
 Error text is shown in [.red]#red#.
 ----
 
-Currently, custom roles only apply to inline phrases and only support changing the font properties.
+You can also use a role to unset a font color (to make it inherit):
+
+[source,yaml]
+----
+role:
+  heading-code:
+    font-color: ~
+----
+
+This role can be used as follows:
+
+[source,asciidoc]
+----
+== [.heading-code]`SELECT` clause
+----
 
 The converter provides several predefined roles.
 The `big` and `small` roles map the font size to the $base-font-size-large and $base-font-size-small values, respectively.
@@ -1083,6 +1106,27 @@ You'll need to define these in your theme if you'd like to make use of them when
 |role:
   heavy:
     font-style: bold
+
+|text-decoration
+|<<text-decorations,Text decoration>> +
+(default: none)
+|role:
+  deleted:
+    text-decoration: line-through
+
+|text-decoration-color
+|<<colors,Color>> +
+(default: $role-<name>-font-color)
+|role:
+  deleted:
+    text-decoration-color: #ff0000
+
+|text-decoration-width
+|<<values,Number>> +
+(default: 1)
+|role:
+  underline:
+    text-decoration-width: 0.5
 |===
 
 [#keys-page]
@@ -1156,6 +1200,12 @@ See <<Title Page>> for details.
 |page:
   margin-outer: 0.59in
 
+|mode
+|fullscreen
+(default: _not set_)
+|page:
+  mode: fullscreen
+
 |size
 |https://github.com/prawnpdf/pdf-core/blob/0.6.0/lib/pdf/core/page_geometry.rb#L16-L68[Named size^] {vbar} <<measurement-units,Measurement[width,height]>> +
 (default: A4)
@@ -1349,10 +1399,22 @@ The keys in this category are used to style hyperlink text.
   font-style: italic
 
 |text-decoration
-|none {vbar} underline {vbar} line-through +
+|<<text-decorations,Text decoration>> +
 (default: none)
 |link:
   text-decoration: underline
+
+|text-decoration-color
+|<<colors,Color>> +
+(default: $link-font-color)
+|link:
+  text-decoration-color: #0000ff
+
+|text-decoration-width
+|<<values,Number>> +
+(default: 1)
+|link:
+  text-decoration-width: 0.5
 |===
 
 [#keys-literal]
@@ -1469,11 +1531,29 @@ The keys in this category control the style of most headings, including part tit
 |heading:
   font-style: bold
 
+|text-decoration
+|<<text-decorations,Text decoration>> +
+(default: none)
+|heading:
+  text-decoration: underline
+
+|text-decoration-color
+|<<colors,Color>> +
+(default: $heading-font-color)
+|heading:
+  text-decoration-color: #cccccc
+
+|text-decoration-width
+|<<values,Number>> +
+(default: 1)
+|heading:
+  text-decoration-width: 0.5
+
 |text-transform
 |<<text-transforms,Text transform>> +
 (default: _inherit_)
 |heading:
-  text-transform: uppercase
+  text-transform: capitalize
 
 |line-height
 |<<values,Number>> +
@@ -1562,7 +1642,7 @@ The keys in this category control the style of most headings, including part tit
 |<<text-transforms,Text transform>> +
 (default: $heading-text-transform)
 |heading:
-  h3-text-transform: lowercase
+  h3-text-transform: uppercase
 
 |margin-top
 |<<measurement-units,Measurement>> +
@@ -1697,7 +1777,7 @@ TIP: The title page can be disabled for the book doctype by setting the `notitle
     image: image:logo.png[pdfwidth=25%]
 
 |top
-|Percentage^[4]^ +
+|<<measurement-units,Measurement>>^[4]^ +
 (default: 10%)
 |title-page:
   logo:
@@ -1755,7 +1835,7 @@ TIP: The title page can be disabled for the book doctype by setting the `notitle
     line-height: 0.9
 
 |top
-|Percentage^[3]^ +
+|<<measurement-units,Measurement>>^[4]^ +
 (default: 40%)
 |title-page:
   title:
@@ -1842,6 +1922,17 @@ TIP: The title page can be disabled for the book doctype by setting the `notitle
 
 3+|[#key-prefix-authors]*Key Prefix:* <<key-prefix-authors,title-page-authors>>
 
+|content
+|<<quoted-string,Quoted AsciiDoc string>> +
+(optional subkeys: name_only, with_email, with_url) +
+(default: "\{author}")
+|title-page:
+  authors:
+    content:
+      name_only: "{author}"
+      with_email: "{author} <{email}>"
+      with_url: "{url}[{author}]"
+
 |display
 |none +
 (default: _not set_)
@@ -1977,7 +2068,7 @@ The color keyword `transparent` is not recognized in this context.
 The size of the background image can be controlled using any of the sizing attributes on the image macro (i.e., fit, pdfwidth, scaledwidth, or width) when `fit=none`.
 The position of the background image can be controlled using the `position` attribute.
 . Target may be an absolute path or a path relative to the value of the `pdf-themesdir` attribute.
-. Percentage unit can be % (relative to content height) or vh (relative to page height).
+. % unit is relative to content height; vh unit is relative to page height.
 
 [#keys-prose]
 === Prose
@@ -3864,11 +3955,23 @@ The keys in this category control the arrangement and style of the table of cont
   font-style: bold
 
 |text-decoration
-|none {vbar} underline +
+|<<text-decorations,Text decoration>> +
 (default: none)
 |toc:
   text-decoration: underline
 
+|text-decoration-color
+|<<colors,Color>> +
+(default: $toc-font-color)
+|toc
+  text-decoration-color: #cccccc
+
+|text-decoration-width
+|<<values,Number>> +
+(default: 1)
+|toc:
+  text-decoration-width: 0.5
+
 |text-transform
 |<<text-transforms,Text transform>> +
 (default: _inherit_)
@@ -3887,6 +3990,12 @@ The keys in this category control the arrangement and style of the table of cont
 |toc:
   indent: 20
 
+|hanging-indent
+|<<measurement-units,Measurement>> +
+(default: _not set_)
+|toc:
+  hanging-indent: 0.5in
+
 |margin-top
 |<<measurement-units,Measurement>> +
 (default: 0)
@@ -3919,12 +4028,6 @@ The keys in this category control the arrangement and style of the table of cont
 |toc:
   font-style: italic
 
-|text-decoration
-|none {vbar} underline +
-(default: _inherit_)
-|toc:
-  text-decoration: none
-
 |text-transform
 |<<text-transforms,Text transform>> +
 (default: _inherit_)
@@ -4276,6 +4379,8 @@ IMPORTANT: If you don't specify a height for either the header or footer key, it
 TIP: Although not listed in the table above, you can control the font settings (font-family, font-size, font-color, font-style, text-transform) that get applied to the running content in each column position for each page side (e.g., `footer-<side>-<position>-font-color`).
 For example, you can set the font color used for the right-hand column on recto pages by setting `footer-recto-right-font-color: 6CC644`.
 
+==== Disabling
+
 If you define running header and footer content in your theme (including the height), you can still disable this content per document by setting the `noheader` and `nofooter` attributes in the AsciiDoc document header, respectively.
 
 If you extend either the base or default theme, and don't specify content for the footer, the current page number will be added to the right side on recto pages and the left side on verso pages.
@@ -4295,6 +4400,8 @@ footer:
 
 Instead of erasing the content (which is what the `~` does), you can specify content of your choosing.
 
+==== Replacing
+
 If you want to replace the alternating page numbers with a centered page number, then you can restrict the footer to a single column and specify the content for the center position.
 
 [source,yaml]
@@ -4490,7 +4597,13 @@ The only thing you need to add to an existing build is the attributes mentioned
 * https://github.com/asciidoctor/asciidoctor-maven-examples/tree/master/asciidoctor-pdf-with-theme-example[Maven Example]
 * https://github.com/asciidoctor/asciidoctor-gradle-examples/tree/master/asciidoc-to-pdf-with-theme-example[Gradle Example]
 
-TIP: To reference a theme file or directory of fonts inside a JAR file on the classpath, prefix the path with `uri:classloader:`.
+Speaking of Java, you can bundle and distribute your theme and fonts in a jar file.
+To reference the theme file and/or directory of fonts from inside the jar, refer to their location on the classpath using the `uri:classloader:` prefix.
+Here's how you'd load both the theme and fonts from the classpath:
+
+ $ asciidoctorj -b pdf -a pdf-theme="uri:classloader:/path/to/themes/my-theme.yml" -a pdf-fontsdir="uri:classloader:/path/to/fonts" document.adoc
+
+This only works when running Asciidoctor PDF on the JVM.
 
 == Theme-Related Document Attributes
 
@@ -4514,6 +4627,10 @@ These settings override equivalent keys defined in the theme file, where applica
 (format can be image or PDF)
 |:front-cover-image: image:front-cover.pdf[]
 
+|hyphens^[7]^
+|language code {vbar} _blank_ to default to en_us (default: _not set_)
+|:hyphens: de
+
 |media
 |screen {vbar} print {vbar} prepress
 |:media: prepress