If it helps: I just tried building ODT output from Oxygen, but this time, forcing the use of "DITA-OT" framework (instead of DITA-OT2.x by default). (In the build config, I set dita.dir=${frameworksDir}/dita/DITA-OT And it works. I now have the images inside the resulting ODT document. Sti...

Hi, Thanks Radu, I usually don't build the output using Oxygen, (this is all automated through CI builds), but I've been unable to get the https://github.com/dita-ot/org.dita.odt to work on a recent DITA-OT framework, and that's the reason I tested through Oxygen. If you have any advice on where I c...

I'm hitting the same issue, using <oXygen/> XML Editor 18.1, build 2017020917 Trying to generate an ODT file from DITA source, through Oxygen, gives me the ODT file, but no images are present inside. I could provide the build log, but no errors/warnings whatsoever. * One thing I noticed in the log, ...

Hi,
I've added the following extension point to my custom plugin, and it seems to do the trick: Is there anything else I need to do, knowing that it works ?

Hi, I'd like to resurrect this topic, as I'm hitting the same use case. In the September thread, you say the next Oxygen release will implement this. Currently, I want to produce a Webhelp with feedback output, but I have a set of custom DITA elements which are defined in a plugin. This plugin provi...

@xephon I ended up designing a custom plugin instead, and this is the portion of code I added to my custom "integrator.xml" file: <condition property="outputFile" value="${dita.map.output.dir}/${outputFile.base}${xsl.formatter.ext}"> <not><isset property="outputFil...

Hi, I'm having exactly the same problem as annetteb, and tried out the fix that was suggested on the yahoo group: You'll find below the diff of what I changed in the build.xml file: diff --git a/demo/fo/build.xml b/demo/fo/build.xml index 08cbcfe..1974b41 100644 --- a/demo/fo/build.xml +++ b/demo/fo...

Yes, I think I found the same Stackoverflow post
http://stackoverflow.com/questions/1355 ... rties-file

Tried it and it seems to work fine.

I finally got around, and this was due to a bad combinations of depends. The only issue I'm having now is that since I had to modify the global demo/fo/build.xml file to make it work, I would have liked to fail gracefully and revert to the original ${outputFile} if the variable I'm passing is empty....

OK, here is what I've come up so far: <target name="app.main" depends="app.pdf"> <echo>Publish the PDF and HTML versions of Application documentation.</echo> <xslt in="${basedir}${file.separator}apps${file.separator}app.ditamap" out="${global.output.dir}${file.sepa...

Actually, I've been able to do exactly what you describe, and got a nice xml file i can use, but how do I use it to customize the PDF output name?

There is an output.dir parameter, but nothing that gives me ways to control the pdf file name...

Thanks, that sounds like a good idea.

I'm not familiar with ant that much though, and I'm using a single build file for many targets, which would all require specific property files.

Do you think that's still doable ?
And how would I call an xslt transformation within each target ?

Thanks

Hi, I've been using DITA-OT for quite a while, and there's something I'm still unable to do. In my app.ditamap file, I have the <prodinfo> properly filled, like : <prodinfo> <prodname>Application Name</prodname> <vrmlist> <vrm modification="Oct 15, 2014" version="3.2"/> </vrmlist...

Alright,

I have some leads then, but still doesn't work.
I'm still getting java classpath errors...

While looking at the shipped build.xml file in the /DITA-OT dir, it seems it contains a bunch of Oxygen hacks...

Is this the place to look ?

I'm trying to use the ant transformations of the built-in DITA-OT framework, which work fine inside Oxygen, outside the editor, using CLI. Like ant -f mybuildfile.xml mytarget . I previously used a manually installed dita-ot environment, and this used to work well, once you set all necessary env var...