Releases: docbook/xslTNG
DocBook xslTNG Stylesheets version 1.5.0
There's a new search feature in the persistent Table of Contents (ToC) and a bunch of bug fixes and general improvements.
- Added support for a search box in the persistent ToC. It filters the ToC entries based on what’s input.
- Added the persistent ToC link to the home page, where it had previously been suppressed.
- Reduced the size of component titles in articles.
- Added an option to suppress “trivial” Tables of Contents. A top-level ToC that consists of a single entry is suppressed by default.
- Reworked how index entries are generated. Where there used to be one index entry per section, there’s now one index entry per indexterm, numbered sequentially. All the terms in a single section are grouped in a span. You can disable this with $indexed-section-groups.
- Added bibliography, glossary, index, acknowledgments, colophon, and dedication to the ToC for article.
- Reworked a bunch of build infrastructure.
- Fixed #108 by making sure the ‘no-js’ class gets turned into ‘js’ if JavaScript is available.
- Fixed #110 by copying the catalog into org/xmlresolver in the jar file.
- CSS improvement, don’t highlight code elements in ToC entries with borders or background colors.
- Fixed #111 by interpreting ‘unbounded’ correctly in ToC section depth.
- Added support for db:templatename
- Reworked “line” styled verbatim environments with new ‘verblines’ class.
- Tone down the style of literals: lighter border, don’t make them nowrap.
- Fixed #104, change http: to https: in purl.org URLs
- Fixed #91 (with #103) by implementing DocBook Transclusions.
- CSS improvements for revisionhistory tables
- Improved handling of db:coref
1.4.2
DocBook xslTNG Stylesheets version 1.4.1
The JAR file in the 1.4.0 release was incomplete. This release fixes that error. This release also moves some resources around in the JAR file; resources formerly located in {jar}:{path}/
are now located at {jar}:org/docbook/xsltng/{path}
. This means that classpath searches for them are less likely to incorrectly match files in a different JAR.
This release also increments the recommended versions of some dependent libraries. The Saxon XInclude plugin version is raised to 1.1.0 because of a bug. The XML Resolver library version is raised to 2.1.0. The 2.x release of the XML Resolver library supports classpath:
URIs. That means it is now possible to refer to the stylesheets in the JAR file without constructing a temporary catalog on the filesystem. It also fixes a concurrency bug in the way the resource cache is handled.
The build system has been converted to use the Saxon Gradle plugin. It is currently shipping with a custom version of the plugin, but the changes in that version have been sent back to the plugin author, so this is hopefully a temporary situation.
(There are a lot of infrastructure changes here; I'd have been inclined to make this a 1.5.0 release had the previous release not been 1.4.0 and broken.)
This release also fixes the following bugs:
- #97 by supporting
xml:id
attributes on CALS table rows and entries. The IDs will now appear asid
attributes in the corresponding HTML elements. - #98 by rearranging the order of
link
elements in the HTMLhead
so that a CSS override in thedocbook.css
stylesheet can correct the padding. - #100 by handling the case where the HTML chunk fragment is an element, not a document.
- #101 which reported the resources missing from the JAR file.
1.4.0
1.3.1
- Fixed #78, syntax errors in the print CSS, thank you @a-vrma.
- Fixed #67 with #79, thank you @gimsieke. This is an attempt to support the Oxygen change tracking markup. This is incomplete but handles a some simple cases.
- Fixed some rendering issues associated with DocBook
revisionflag
markup. That’s also change markup, but it isn’t related to the Oxygen system. See the$oxy-markup
parameter. - Fixed #76, support
releaseinfo
inbibliomixed
and some cosmetic improvements to the CSS. - Fixed rendering of email addresses; don’t put marginal space around code when it doesn’t have a visible border.
- Fixed #74, improving the CSS for email addresses
- Improved the way ‘reveal’ is handled in the “slides” mode.
- Reworked some of the build system and made editorial improvements here and there.
1.3.0
Added a --resources
option to the Python script. This option will copy the resources (CSS and JavaScript files) from the distribution directory into the output directory where the transformed document is being saved. Added excluded packages to the configuration.
Removed docbook-annotations.css
and its configuration parameter. Annotations are now accessible, so I’ve simply folded the CSS into docbook.css
and docbook-screen.css
.
Changed the xlink-default-style
to javascript
. The markup is accessible when JavaScript isn’t available, so this seems like a reasonable default.
Removed xlink-css
parameter. That CSS is now part of the default DocBook CSS.
Added control-js
and theme-picker
parameters to support user-selectable themes. Added a default-theme
parameter for selecting the default theme (irrespective of whether or not user-selectable themes are enabled). Reworked JS/CSS in an attempt to reduce flicker when switching between pages using a dark theme.
Added support for alternative syntax highlighters: highlight.js and Prism.
Fixed bug where the links in the persistent ToC would be incorrect if the chunks were in different directories.
Bumped the versions of some dependencies (XML Resolver, DocBook).
Fixed issue #69 where using <i>
for <foreignphrase>
was less than ideal. Now using <span>
and getting italics (by default) with CSS.
1.2.0
Reworked CALS table formatting to fix #48. Starting with this release, it should be possible to process arbitrarily long tables. This is accomplished by processing the tables in a single forward pass. Consequently, it is no longer possible for the stylesheets to work out the align-char-width
by inspecting the cells in the column. If an align-char-width
is not specified with a PI, the default $align-char-width
will be used.
Updated the documentation in the reference guide to be explicit about build prerequisites. (Fix #49.)
Changed the default chunking rules so that the first section of a chapter, appendix, or other component is included in the chunk with that component. This will improve the presentation of components that have only a short amount of introductory material before the first section (and greatly improve the presentation when there is no introductory material before the first section). (Fix #45.)
Updated the JavaScript libraries to avoid use of .replaceAll()
which is not yet widely (enough) supported. (Fix #52.)
Updated the CSS for admonitions so that it’s more easily configured with CSS variables. I tweaked the presentation of code
inside admonitions to avoid contrasting background colors that I found aesthetically problematic.
Changed the CSS for literal
so that it will imply white-space: nowrap
. Adding a role="break"
will return white space to normal.
Documented that building on Windows does not work. (Close #44.)
Added trademark marks (™,℠,©,®) for the trademark
element. For the moment, this is done with ::after
in CSS rather than putting the marks explicitly in the HTML output.
Changed package
, markup
, token
, returnvalue
, type
, and errorcode
formatting to use code
instead of span
.
1.1.1
1.1.0
This release fixes issue #41. The fix is not backwards compatible with the previous release. In 1.0.0, using the “javascript” annotation style produced different HTML from the “inline” style. In the absence of JavaScript, the annotations were inaccessible. In this release, the only difference between the two styles is whether or not the script element is inserted which loads the JavaScript to support annotations as modal dialogs. This script updates the classes on annotation-related elements so that they are hidden by default and displayed as dialogs.
- The
f:annotation-style
function has been removed. - The
annotations
parameter has been renamedannotation-style
. - The
annotations-javascript-css
andannotations-inline-css
parameters.
have been replaced with a singleannotations-css
parameter. - The
<?db annotations="style"?>
processing instruction is no longer supported. - The reference guide has been updated accordingly.
This release fixes issue #39. The $debug
flags are now documented.
Related to issue #32, this release includes experimental support for backwards links (reverse jumps or “pmuj”s)
This release fixes issue #38 with a note about performance.