Skip to main content
Known Participant
May 26, 2014
Question

DITA Open Toolkit (DITA-OT) nothing happens when building output

  • May 26, 2014
  • 2 replies
  • 1178 views

Hi

I'm trying to generate PDF2/XHTML using the DITA Open Toolkit with FrameMaker 12 but nothing happens when building the output.

I can see the command line start but is then immediately shutdown, and there is nothing generated in the output folder.

I have installed the Java JDK and set the Java_Home variable (before that the output options box didn't open).

Do anyone have a glue what is wrong?

This topic has been closed for replies.

2 replies

NatGi-pXyzoE
Known Participant
March 11, 2018

I have the same problem. Could you provide the answer as Pawan Keshari said he whould do 4 years ago?

Thanks.

Adobe Employee
March 15, 2018

Hello , which version of FM are you using?

thanks,

Amitoj Singh

Adobe Employee
May 27, 2014

Hi,

I am from FrameMaker Engineering Team, Can you Please confirm the Exact Steps for this scenario? And If possible share the Files.

If the files contain any Images, are they present in some other Folder (other than from where the file is located)???

Thanks & Regards,

Pawan Keshari

Known Participant
May 27, 2014

Hi,

I have just tried to use a simple document for testing, incase I would run into trouble.

For example, I have created a DITA concept topic with a title and some paragraphs.

I save the document to: text_topic_en_001, and then try to publish with the DITA-OT.

I suspect I have installed the Java applications wrong, as the DITA-OT plug-in is already installed with FM12

Thanks for you reply Pawan Keshari

Best regards


Known Participant
June 2, 2014

Hello,

I'm still stucking on trying to transform a dita.map in FrameMaker with the DITA-OT plugin.

But now I managed to get the DITA-OT up and running and processed a dita.map to PDF and XHTML.

I downloaded the Toolkit to D: directory that is not under the windows C:program files protection.

Could it be that DITA-OT for FM12 is installed in the C:program files directory which is locked for changed by windows that causes the build to fail?