Hi Mica, That's it: page imposition. We're using Antenna House. How might you approach this instead?

Hello, We're trying to create a two-page layout where each printed page has two pages on it. Although creating a two-column layout is simple enough, we're having difficult with the static content sinc

hello~ We're migrating to the official DITA-OT 3.5 docker image but it looks like it's missing tools.jar: Unable to locate tools.jar. Expected to find it in /opt/java/openjdk/lib/tools.jar java.lang.I

that did it. thanks, Radu!

Hi, We're exploring project files. They seem to work fine in DITA-OT 3.4 but throw this error in DITA-OT 3.5: java.lang.NullPointerException at org.dita.dost.invoker.Main.lambda$handleProject$3(Main.j

That did it, thanks! We were also importing each XSL file one-by-one, but simply importing the base topic2fo.xsl file once at the beginning of the shell and then overriding them proves more efficient.

That’s a good idea. Thanks, Kris. I’ll give it a try. Take care,- Nick Sent from mobile

Hi, We're upgrading from OT 2.3.3 and are starting to work on OT 3.5. Our plugin runs in OT 3.0.4 but not in OT 3.4 or OT 3.5... Is there something we need to do in the newer versions of OT? We use a

Hi, We notice that ditamaps with a ditavalref element at the root of their map and chunks at some chapter maps end up with broken links in normalized output for those chapter maps. It looks like the c

#branch-filtering #chunk

We convert dita to json so that a ditamap structure can feed a python app. It’s a lot like creating a text output. What’s your json data structure? Take care, - Nick Sent from mobile

#JSON

Hi Mark, Radu, It’s unsuccessful. Adding this to the custom markdown plugin.xml file throws an integration error about dita.xsl.markdown being an undefined extension point... <feature extension=“dita.

#LwDITA

Thanks, Radu. I’ll give this markdown extension point shot. Take care,- Nick Sent from mobile

#LwDITA

Hello! We’d like to customize the structure of some output elements and also add the original file path and a few other details to the bottom of every page in the vanilla Markdown output. I’m not find

#LwDITA

Hi folks, In OT 3.4 we’d like to create a Markdown output with this structure: | out | images | index.md | topics The default output mimics the input file structure, which can be all over the place. O

#markdown

Hi! Our topic.fo file for a custom pdf2 output renders fine in FOP for note label images in bullets. However, for some reason Antenna House adds something like 6pts of padding above the note label ima

#PDF

Hi Aaron, I probably do this incorrectly but it works. I have a preprocess plugin with a bunch of targets in there. Then I just call the main ant target from other plugins to run a few proprocessing s

#DITA-OT

Hi jdaniel, Is this using the same PDF plugin with different ditamaps or the same ditamap with different PDF plugins? Take care,- Nick Sent from mobile

#PDF

Hi Bernard, On a personal note, I started in dita as a tech writer and wanted “pure” block elements, so no embedded p tags. Over time, and as I moved into an information architecture role, I find p el

#mixed-content

Hi! We use custom note types without specialization. It’s an update to the XSL template for notes and then an updated localization variable. For example, we have a special warning symbol used for elec

#specialization

In DITA-OT 2.3.3 if you reuse a topic multiple times in the same map structure and produce XHTML, the output does not have multiple topics--it only has the first one it finds. This creates sad breadcr

#DITA-OT