Hi Scott, > File file:/C:/my_image.eps not found .eps images are not usually used as image format. Are you outputting PDF from DITA instances? Then what PDF plug-in and PDF Formatter are you using? Re

Hi List, If you are publishing DITA documents that contains <indexterm>, you may make index pages by specifying backmatter/booklists/indexlist. Also if your publication contains Simplified Chinese loc

#DITA-OT #PDF

Hi Nick, Unfortunately AH Formatter does not support static contents per column. What content do you want to put into static contents? If it is only footnote, specifying axf:footnote-position="column"

Hi Chiris, Sorry for the late reply. As PDF2 plug-in has extension point named "org.dita.pdf2.xsl.topicmerge", you can override default topicmerge stylesheet processing by making plug-in. Here is my e

Hi Chiris, > Do you have an idea where this specific template of yours has to be placed in the pdf2 section? What DITA-OT version are you using? I will take a look at PDF2 plug-in tomorrow. Regards,

Hi Chiris, As <topicgroup> is specialization of topicref, it affects numbering wrongly. To avoid this problem, I always skip <topicgroup> in the merged middle file processing in PDF output. See https:

Hi Chiris, > I have a special DITA PDF-layout (FOP) with no cover page but just first and odd pages. The first page has a simple footer with the page number, and the odd pages show an extended footer

If you want add some prefix for page-number: cover-1 safety-3 You can specify fo:folio-prefix as the children of fo:page-sequence such like following: <fo:page-sequence master-reference="a4-master" re

#PDF

Hi Erik, I'm not sure what the concrete problem is. If your question is about PDF, I believe that the PDF page count is stored in PDF file as the static data. But page count does not belong to metadat

#PDF

Hi Vadim, I'm very interested with ODT transform and investigating it now. In my understanding the style is defined in following XSLT module: https://github.com/dita-ot/org.dita.odt/blob/master/xsl/xs

#DITA-OT #ODT

Hi Nicholas, > The xsl-fo syntax in the topic.fo is the same for both and we cannot find where Antenna House (or maybe FOP is ignoring) the additional padding. Could your send me your XSL-FO file frag

#PDF

Hi Corinna, > but it seems that the @outputclass value does not appear in the merged output so there's nothing to work with in the XSLT. I have the same problem in one of our project. The user authors

#DITA-OT

Hi Kris, Sorry for the late reply. > <kje> > Do you think authors become confused because they are building <hazardstatement> elements that contain > multiple <messagepanel> elements AND associating m

Hi Kris, > Are you using the hazard statement domain? Yes, I recommend Japanese users to adopt it. Some DITA users are using hazard statement domain now. > Are there things that you want to do with ha

I attached sample Word(.docx) snapshot that this plug-in generates.

Hi Wim, I'm very glad if you use (or test) our DITA to Word(.docx) plug-in and send your impression to us. https://github.com/AntennaHouse/ah-wml The features are This plug-in directly generates .docx

Hi I have very similar experience with your customer. In my case, the user publishes their contents with PDF (using XSL-FO) and HTML via DITA-OT. But they do want Word output when they extend DITA sol

From developer's perspective, I think using POI is the declaration of the XSLT's virtual defeat. In my DITA to Word(.docx) plug-in it uses only XSLT 3.0 stylesheet without one exception which calculat

I have the similar problem if chapter/@href refers submap. In this case @outputclass is not retained in the merged middle file. This is the same as DITA-OT 3.1 (the version i'm using). To prevent this

I am also developing DITA to .docx DITA-OT plug-in at this moment (still work in progress): Antenna House DITA to Word(.docx) DITA-OT plug-in https://github.com/AntennaHouse/ah-wml > a simple XML form