DITA-OT projects and spaces in filenames
Posted: Tue Feb 20, 2024 2:04 pm
Hello!
I learned of the DITA-OT project feature last week on the DITA-OT day and hurried to implement it - we have been using a batch file to run the DITA transformation for each PDF separately, so using the DITA-OT project should be a lot more robust.
However, I immediately ran into a problem - our DITA map names often contain spaces, for example "Access Control.ditamap". This has not been a problem before - whether running a PDF transformation on that map via Oxygen or via the command line, the output file name always matched the input: "Access Control.pdf". It still works, when transforming the map directly.
The problem appears when the same map is specified in the DITA-OT project file:
The spaces in file names (and paths) have to be encoded as %20, but this means that the output will also be named Access%20Control.pdf. Again, this is only a problem when transforming the DITA-OT project.
Is there something else I could do besides changing all DITA map names so they wouldn't contain spaces? We are using Oxygen 25.1 and DITA-OT 3.7.4 on Windows, if it's relevant.
I learned of the DITA-OT project feature last week on the DITA-OT day and hurried to implement it - we have been using a batch file to run the DITA transformation for each PDF separately, so using the DITA-OT project should be a lot more robust.
However, I immediately ran into a problem - our DITA map names often contain spaces, for example "Access Control.ditamap". This has not been a problem before - whether running a PDF transformation on that map via Oxygen or via the command line, the output file name always matched the input: "Access Control.pdf". It still works, when transforming the map directly.
The problem appears when the same map is specified in the DITA-OT project file:
Code: Select all
<deliverable>
<context name="Access Control">
<input href="/source/rt_dev/dita/Access%20Control.ditamap"/>
<profile>
<ditaval href="PDF.ditaval"/>
</profile>
</context>
<output href="./Standard%20dev/"/>
<publication idref="pdf-dev"/>
</deliverable>
Is there something else I could do besides changing all DITA map names so they wouldn't contain spaces? We are using Oxygen 25.1 and DITA-OT 3.7.4 on Windows, if it's relevant.