The XSL (Extensible Stylesheet Language) plug-in enables Typefi workflows to transform an XML document according to instructions specified in an XSL stylesheet. The XSL action uses the Saxon 10 processor. For more information about the XSL plug-in, please get in touch.
* Some custom configuration of this action may be required to match a given XML schema or DTD.
The latest version of the XSL plug-in is 23.0.270, released on 24 September 2024.
We release updates regularly, and it's our goal to make sure that our software works well, constantly—that Typefi continues to deliver, every day. If you have any feedback or run into any issues, please contact us. We're happy to help.
23.0.270 — 24 September 2024
Requires Typefi Server 8.14 or later
- Improved handling of spaces when whitespace mode is set to strict.
22.0.268 — 19 April 2024
Requires Typefi Server 8.14
- Upgraded to Java 21 and Tomcat 10.1 to ensure the security and stability of our services.
21.0.267 — 1 November 2023
Requires Typefi Server 8.10–8.13
Improvements
- When you select Pretty print output, your file will now consistently display formatted content when there is one or more
<tps:s/>
tags between<tps:p>
tags. - Improved the error message for missing style sheets by including a description of the error and the relevant path.
- Updated Apache Log4j to 2.18.0 to be compatible with Java: Open JDK 11.
- Exported CXML now uses Content XML 3.2.
Fixes
-
Import IDML action:
- URLs added to InDesign documents will now transfer to CXML, even if Shared Hyperlink Destination is not selected.
- The CXML for table cell list items now includes
<tps:ul>
and<tps:ol>
. - Table cells with
left
,align toward spine
, oralign away from spine
horizontal alignment overrides no longer export with invalid@Justification
attributes. These overrides now export toalign="left"
oralign="justifyLeft"
. - In the Apply XSL Transform action, entering characters like ( . / + ) in the parameters field no longer triggers an error: COULD NOT ACCESS FILES and opens a new browser tab.
20.0.253 — 30 November 2022
- Updated Apache Log4j to 2.17.1 to resolve known Log4j vulnerabilities.
19.0.252 — 7 January 2022
- Updated Apache Log4j to 2.17.0 to resolve known Log4j vulnerabilities.
18.0.250 — 22 February 2021
Requires Typefi Server 8.2–8.13
- Updated the Saxon-HE XSLT processor from 9.4 to 10.3 (released October 2020).
- Added support for XSLT 3.0.
- Added support for XPath 3.1.
- Improved the error message when an XZIP file does not contain an XSLT entry point. Before, the error was ERRO java.io.IOException : Failed due to [null]. Now, the error is Cannot find an entry XSL stylesheet file in the XZIP archive.
17.0.232 — 8 June 2020
Requires Typefi Server 8.2–8.13
-
Multiple bug fixes and improvements for Apply XSL transform:
- Fixed a bug where selecting the Pretty print output checkbox for an input file that was already pretty printed caused unexpected problems with the output Content XML. It is now safe to select Pretty print output on multiple XSL actions in a workflow.
- Fixed a bug (introduced in v16) where some namespaces were removed from the Content XML.
- Fixed a bug (introduced in v15) where a job would fail if there was a period (.) in the stylesheet filename.
- Fixed an Import IDML bug where character styles applied to a page break created invalid Content XML.
16.0.226 — 7 February 2020
Requires Typefi Server 8.2–8.13
- Added a Pretty print output checkbox for the Apply XSL transform action. For more details, please refer to our article on Applying an XSL transform.
- Removed the Advanced tab and replaced it with the consolidated Pretty print output checkbox for the Import IDML action. For more details, please refer to our article on Importing IDML.
- Renamed XSLT Zip input to Stylesheet for Apply XSL transform.
- Added .xsl as a valid Stylesheet file name extension for Apply XSL transform (we now support XSL files for less complicated transforms and XZIP files for more complex transforms).
- Multiple bug fixes and improvements for Import IDML:
- Fixed an issue where character formatting (for example: underline, strikethrough, superscript, subscript, all caps and small caps) could erroneously be applied as a local style (
tps:style
) when the formatting was applied via a character style. - Fixed multiple issues related to grouped or nested Fixed Elements that could produce invalid, duplicate, or erroneous content (for example,
<tps:p type="[No paragraph style]"><!--Missing float element–>
). - Fixed an issue where hyperlinks within endnotes produced invalid Content XML.
- Fixed an issue where character formatting (for example: underline, strikethrough, superscript, subscript, all caps and small caps) could erroneously be applied as a local style (
15.0.165
Internal release
14.0.140 — 13 September 2019
Requires Typefi Server 8.2–8.13
-
Multiple bug fixes and improvements for Import IDML:
- Fixed an issue where Typefi Section fields may be omitted if the field value contains a comma (for example,
<tps:fieldSet name="Titulo_capitulo" value="Las edades del hombre, adaptadas a la vida del que escribe estas líneas"/>
was omitted). - Fixed an issue where Typefi Sections may be omitted from the output CXML if the first master page of Section did not contain a Main Story Frame.
- Fixed an issue where white space after a character styled string within a footnote may not be handled correctly (for example, the omitted space after the italicized word "missing" in
<tps:footnote><tps:p>This is <tps:c type="italic">missing</tps:c>a white space.</tps:p>
). - Fixed multiple issues related to supporting round trip of Endnote Sections. For more information on Endnotes, please see Content XML 3.1 → Endnotes.
- Fixed an issue where Typefi Section fields may be omitted if the field value contains a comma (for example,
13.0.137
Internal release.
12.0.122 — 13 March 2019
Requires Typefi Server 8.2–8.13
White space processing
Import IDML now has an Advanced tab to specify white space handling when converting from IDML to Content XML. You can choose between Strict (default) or Preserve white space modes, and optionally choose to Format and indent (that is, pretty-print).
To learn more about white space modes like Strict and Preserve in Content XML, please see Content XML 3.1 → White space.
Caution We do not recommend selecting Preserve white space mode and Format and indent at the same time. Doing so may cause undesired results when the Content XML output is used in later actions (for example, Create InDesign document).
- Added acknowledgements for our contributors, whose efforts over many years have made this software what it is (click the workflow plug-in version number to view).
- Fixed an issue in Apply XSL transform where an input XML file containing a BOM character may fail.
- Multiple bug fixes and improvements for Import IDML:
- Fixed an issue where two paragraphs could be merged if a soft style was applied at the end of the first paragraph.
- Fixed an issue where a paragraph separator (
U+2029
) may not be handled correctly, which could cause separate paragraphs to merge. - Fixed an issue where white space in Typefi Fields was double-encoded (that is, it renders as
%20
in later actions). - Fixed a character-encoding issue where some accented characters in Typefi Fields could be replaced by non-accented characters.
- Fixed a character-encoding issue where Import IDML may fail if the input IDML had accented characters in its filename.
- Fixed an issue where footnotes could be omitted from the output Content XML.
11.0.83 — 5 April 2017
- ¿Hablas español? The XSL workflow actions are now localised in Spanish.
- Removed file extension requirements on Apply XSL Stylesheet action.
- Corrected encoding of image paths that contain special characters for Import CXML action (also affects InDesign → Export to CXML action).
- Added support for media (audio and video) elements.
- Updated XSLT processor to Saxon-HE 9.7.0.14 (released 02 December 2016).
10.0.42 — 1 April 2016
Internal release.
9.0 — 9 November 2015
Initial support for localisation.
8.0 — 23 September 2015
First customer release.
Comments
0 comments
Please sign in to leave a comment.