![]() The only difference I've been able to find is that the oxygen run's tempįiles have mention of the image in stage2.fo and stage3.fo. ![]() No obvious difference between the in-oxygen and command-line DITA runs. Oddly, if I use the default DITA PDF transformation scenario in Oxygen, ![]() * Doesn't matter if I run on a ditamap, or a single dita topic dita files are not appearing in my PDF output using the XML Editor, Schema Editor and XSLT Editor/Debugger You can also make a small DITA Map Project which exhibits the issue, send it to and I'll try to find some time to look into it. So the difference might be caused by the fact that you are comparing the published output obtained with two distinct versions of the DITA OT.Ĭould you post the complete ANT console output received when running using DITA OT 2.1? Oxygen XML Editor 17.0 comes with a DITA OT 1.8.5 installation. while the command-line run doesn't.ĭita -verbose -format pdf -i test/test_image_topic.ditaĭoc_content (location of top-level ditamaps, and path for running DITA)ĭoc_content/test (location of. The only difference I've been able to find is that the oxygen run's temp files have mention of the image in stage2.fo and stage3.fo. The log output from both DITA runs show no obvious difference between the in-oxygen and command-line DITA runs. We cant display the raw photo in the browser, but looking at the. Oddly, if I use the default DITA PDF transformation scenario in Oxygen, the image is included perfectly. And while thats great for photo editing, its not so great for, which is why image. Doesn't matter if I run on a ditamap, or a single dita topic.dita files are not appearing in my PDF output using the stock DITA command-line installation.
0 Comments
Leave a Reply. |