I had been informed that when using the org.dita.pdf2 plugin, a setting of @xml:lang in a map (mine is set to 'zh-tw') would propagate through the topics in the map and result in the right string values being calling from the right file (in my case zh_TW.xml, which I had translated from the en.xml) ...

I managed, by adding messages at the beginning and end of every template I'd added or modified for the plugin, to isolate the problem. It's being caused by the time it takes to open and get data from SVG files, but I don't know why it's taking so long. The template that is slowing things down is: <x...

So, as usual, Radu found a way to help me debug and fix my problem with fonts not appearing; it turned out to be a basic build problem rather than a font problem. Now, my output is building, but incredibly slowly. A book that takes about 15 seconds to run through the generic PDF2 plugin takes over 2...

Hi Radu,

My transtype is definitely mentioned in the main build.xml file under the 1.8.4 DITA-OT. That's why I can't figure out why the build is saying it's not in the DOST project.

I'll send the output file to support, as you suggest.

Thanks,
Nancy

As far as I can tell, I've followed all the steps from that page (which I had gone to for guidance): 1. The additional plugin(s) should be copied to the plugins directory from the used DITA Open Toolkit installation (by default OXYGEN_INSTALL_DIR\frameworks\dita\DITA-OT\plugins. *** did that, though...

The integration of my plugin simply doesn't seem to be working. The transform is being run from the org.dita.pdf2 folder, but using my {args.xsl} stylesheet as a master stylesheet. So my stylesheets are called, but not the plugin's catalog.xml file (I have one, and it's called just as you suggested,...

I did a test, by replacing the standard dita2pdf2 font-mappings.xml file with my own, and all my fonts were found. So this means that, as you suggested, my font-mappings.xml file isn't being read by the i18n-postprocess.xsl style sheet. I have it specified in my plugins/plugin_name/catalog.xml file ...

Hi Radu, I already have the aliases you suggested (for AvenirLTStdR and AvenirLTStdH as well as AvenirLTStdB and Georgia). I just hadn't included them in the code I sent you. And I'm using a plugin that calls the standard dita2pdf2 plugin. In my 'plugin_name/cfg/catalog.xml file, I have the followin...

Hi Radu, I am getting the same messages that Scott was: [xslt] [PDFX008W][WARN]: Font definition not found for the logical name or alias 'AvenirLTStdR'. [xslt] [PDFX008W][WARN]: Font definition not found for the logical name or alias 'Georgia'. So I did a search to see if anyone had had this problem...

Hi, I'm doing DITA stylesheet work for a client. They're using 1.6.3 and publishing through an Astoria application. I do my work and testing within Oxygen Editor 14.1. I'm seeing that when I build PDF on their system, I'm getting problems in spacing between the end of a table and the following secti...