Thanks Radu. Your assistance is much appreciated. Regards, Paul

#DITA-OT

Hi Paul, I reproduced the problem on my side and added extra details on this issue: https://github.com/dita-ot/dita-ot/issues/3671 so for now "--store-type=memory" does not work with DITA OT 3.6 but m

#DITA-OT

Hi Radu, Here is the information you requested. When I run the following command from the command line: ./dita --input /usr/local/temp/dita_content/test.ditamap --output=/usr/local/temp/dita_content -

#DITA-OT

Hi Paul, Just to make sure maybe you can post more details about the error, attach a part of the DITA OT console output for example which might show in what ANT build file or XSLT stylesheet the error

#DITA-OT

Hi Chris, I did see that issue but the error is different so I presumed it might not be related. Thanks for the prompt response. Paul

#DITA-OT

Hi Paul, I suspect you've run into the following recently filed issue: https://github.com/dita-ot/dita-ot/issues/3671 - Chris

#DITA-OT

I'm wondering if it is possible to generate PDF output using the default PDF plugin in DITA-OT 3.6 if setting "store-type" to "memory". I'm getting the following error if I run it using that option: E

#DITA-OT

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

Hi Chris, Thanks for sharing your obtained publishing times. Using DITA OT 3.6 with "store-type=memory" I did not find any significant improvement running on Mac OS but I did find a big improvement wh

#DITA-OT

Wow, this is quite an impressive release! I compared this release against the 3.5.4 release by running an html5 transformation on 89 books in our deliverable set. With default options, this release is

#DITA-OT

I'm happy to announce that DITA-OT version 3.6 is now available for download at https://www.dita-ot.org! Highlights of the new release include: * Performance enhancements including new options for par

#DITA-OT

If your topics don’t contain conrefs, you don’t need to disable conref processing. OT will not process conrefs if there are none. But you can use those *.skip properties to disable some preprocessing

#DITA-OT

Hi Toshihiko Makita, Yes, #1. I updated classpath in dita.bat. Not success, not able to find/load the license file. #2. I'm able to succeed when I add <factory> method in <xslt> and remove <pipeline>

#DITA-OT

Hi Balaji, One of our client is currently using Saxon-PE 9-9-1-7J with DITA-OT 3.4.1 on their publishing server without no problem. Do you have any problem using Saxon-PE on your environment? Regards,

#DITA-OT