Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Plugin not called for all pre-process extension points for PDF transform

See original GitHub issue

Desired Goal

I’m attempting to update an old job we have - we have a custom Python script which converts textual instances of @@VAR:SomeTextHere into <keyword keyref="SomeTextHere_first"> the first time the keyword is seen and <keyword keyref="SomeTextHere_other"> for subsequent uses. These keywords are defined in the ditamap.

I don’t want to modify the real source files, and ideally I don’t want to have a 2-stage process of:

  • Parse ditamap, copy all referred ditas to a temporary location and modify those files
  • Run dita over the new files.

So I thought I could hook into the dependency points once the dita files have been copied across to the temporary directory, and modify them there.

Expected Behavior

Using DITA-OT I expect my plugin to be called for the extension points defined in the docs ( when performing PDF transform.

Actual Behavior

It’s only called for depend.preprocess.pre and

Possible Solution

Possible solution is to add in the old preprocessing targets.

I’m also open to any other solutions to my problem!


  • DITA-OT version: 3.2
  • Operating system and version: Linux
  • How did you run DITA-OT? dita command
  • Transformation type: PDF

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

Herbert-SDLcommented, Dec 11, 2018

@robander No problem! In the meantime, I’ve implemented the custom preprocessing pipeline and it works very well.

Herbert-SDLcommented, Dec 7, 2018

@robander Thank you for clarifying. As said, I consider my current solution a hack, as I changed one of the standard files of the toolkit. Never considered having a custom preprocessing pipeline, but I’ll try that instead.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Extension points for plug-ins to the DITA Open Toolkit
Any extension that is not recognized by the DITA-OT is ignored; all elements other than <plugin> are optional. Since version 1.5.3 multiple extension...
Read more >
Extension point add an intermediate processing step for PDF?
Hi,. You can look in the equivalent build file "plugins/org.dita.pdf2/build_template.xml" at the template "transform.topic2fo". It ...
Read more >
Pre-processing extension points - DITA Open Toolkit
The following extension points are available in the original preprocess pipeline that was used by default for all transformations prior to DITA-OT 3.0....
Read more >
DITA-OT HTML5 processing in PDF Chemistry
In fact the PDF Chemistry transformation is based on the PDF XSL-FO transformation but uses stylesheets from the HTML5 DITA-OT plugin during ...
Read more >
ant parameter -
demo/fo/build.xml in the template called transform.topic2fo. Find the ... The fo plugin doesn't include plugin extension points like the other transforms do ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found