Dear Leigh, Thank you so much for taking time to analyze my results and providing your valuable insights. I shall try as per your suggestion.

#bookmap #PDF #DITA-OT

Without seeing the whole plugin, it's difficult to say exactly where to look. You say that you're following the instructions in DITA For Print 1.8 (thank you, by the way) but you seem to be using the

#bookmap #PDF #DITA-OT

Dear All, Thank you so much for your expert suggestions. With your help I found the tag causing the problem, which I have posted below. When I deleted this element from the bookmap, the output is gene

#bookmap #PDF #DITA-OT

You are generating fo:inline as the child of fo:block-container in the following portion of topic.fo. <fo:block-container text-align="center"> <fo:block font-size="22pt" font-weight="bold" line-height

#bookmap #PDF #DITA-OT

We had a similar issue in our DITA-OT 2.3.3 PDF customization plugin. It related to the template for minitoc on chapter pages not having a correct parent in some circumstances. I’d perform a global se

#bookmap #PDF #DITA-OT

Hi, I see that the XSL-FO file contains an fo:inline element inside an fo:block-container element: It's hard to tell what the problem is without seeing your custom plugin but maybe one of your XSLT cu

#bookmap #PDF #DITA-OT

Dear All, I have created a plugin by referring to the book (Dita for Print v1.8). I had installed Dita v2.0 Full and Easy Install Version. I did not face any issues in customizing the plugin and gener

#bookmap #PDF #DITA-OT

Just in case anyone has the same question, I found a simple solution. In root-processing.xsl I replaced the bookmap template with the map template. Now the pages flow like it's a map, without page bre

#DITA-OT #XSLT #PDF

Hi All, I need to prevent page breaks before top level topics in a bookmap. I know it would work like that if we switched to a map, but we need the bookmeta. The custom plugin is based off the PDF2 pl

#DITA-OT #XSLT #PDF

Note to self: custom texts can have parametrized parts, e.g.: <variable id="Body odd footer"><param ref-name="documentnumber"/> <param ref-name="buildlanguage"/> <param ref-name="builddate"/></variabl

#DITA-OT #PDF #HTML

Hi, If you look in the console output the publishing seems to break because one of your XSLT stylesheets is not wellformed: Maybe you can fix that error first and then continue your customization. Reg

#DITA-OT #bookmap #PDF

Hello, Leigh, Thank you so much for responding. Based on your advice, I redirected the path of the Build Files to the build.xml file in the dita-ot folder. (Image is attached for your kind reference)

#DITA-OT #bookmap #PDF

Hi there, Your ANT file is not *quite* a copy of what's in the book. 🙂 You have the line <ant antfile="${dita.dir}/plugins/com.try.custpdf/build.xml"> which calls the build file in your plugin. If you

#DITA-OT #bookmap #PDF

This Ant file is simply deleting your output directory and then calling the build.xml file in plugins/com.try.custpdf. Does build.xml include the code to build the PDF? -Reece

#DITA-OT #bookmap #PDF

Dear All, I am a new Dita learner. Recently, I purchased the Dita for Print Book and I am trying to do the exercises given in the book. I successfully built an ant file. When I generate output, I get

#DITA-OT #bookmap #PDF

Your XPath is selecting every chapter @outputclass value in the document--if you put the value out to a message you should see all the values in the doc. "//*" at the start of an XPath means "all elem

#PDF

Hi all, OT 2.5.4, PDF. I'm trying to set a variable based on the outputclass value of the current <chapter> element in a bookmap. bookmap |_chapter outputclass="foo" |_mapref... |_chapter outputclass=

#PDF

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

Solved the issue!

#PDF #FOP #XSLT

Hi dita experts, as title says, I'm trying to automatically generate title for <screenshots> every time when it comes up in my documentation. It should be same as section titles, but not the titles li

#PDF #FOP #XSLT