How do I get Frame 12 to recognize a new output type

Report · Mar 20, 2015

I have a DITA-OT plugin that defines a transtype. What I need to know is what are the steps I need to take to implement this transtype so that other Frame users could process DITA using that transtype?

Report · Mar 20, 2015

Just found this topic: Adobe FrameMaker XML Author 12 * Using DITA Open Toolkit to Publish DITA content

So, if my plugin calls the OT integrate, would it make sense to add the plugin into the OT within Frame and then update the ini to list my new transtype?

Report · Mar 20, 2015

Hi Julio...

Thanks for locating that Help topic! I knew it could be done, but didn't know off hand where the docs were.

Well .. I think it's a bit of a toss-up whether you integrate your plugin into FM's instance of the OT, or you point the DItaDir parameter at an external instance. In theory, either should work, but you might want to diff the FM-OT against a fresh install of OT 1.8 to see if there are any modifications.

Personally, if I were distributing this to other FM users I'd probably provide my own OT install and just tell them to update the INI to point at that. That way you're sure that you're working with the same OT. It's possible that someone has already modified the FM-OT, and things might not work as expected.

Either way you have to edit the ditafm.ini file.

Cheers,

...scott

Report · Mar 20, 2015

Hi Scott,

It's been a while. I had a feeling that would be the problem. I'm leaning towards pointing to the OT that I've already tested my plugin against so I don't have to test against the current version FM loads and make fixes. LOL. In any case, I guess I can't avoid the .ini update. The group of users I'm working with is just getting started with DITA and FM so I'm not so sure I can have them update their Frame instances to point to the right directory. Too many things to consider before pushing forward but at least I have an idea of what has to be done regardless of how I implement.

Report · Mar 20, 2015

I think that your plan is the best.

Note that you *should* be able to add the BuildFile section to the ditafm.ini file in the "appdata" area instead of needing to edit the file in the fminit/ditafm folder (I'd hope) ..

%appdata%\Adobe\FrameMaker\12\ditafm.ini

Also, when I take a look at the diatom.ini file I see a bit more than is shown in the online Help (surprise, surprise), which I'd bet also requires some updating ..

[BuildFile]

AntCommand=%FMHOME%\fminit\ditafm\DITA-OT\tools\ant\bin\ant

AntScript=build.xml

ClassPath=%FMHOME%\fminit\ditafm\DITA-OT\lib\xml-apis.jar;..<snip>

DitaExtraParams=

Count=3

DitaDir=%FMHOME%\fminit\ditafm\DITA-OT

1=xhtml

2=htmlhelp

3=pdf2

It's never as easy as you'd hope.

Note that I've never used this process since I use the DITA-FMx connector with the OT (a bit easier, but still somewhat convoluted for custom stuff).

Cheers,

...scott