Custom DTDs with default Oxygen OT

I think I know the answer to this question, but want to confirm that I'm not missing something. I've got a set of custom DITA DTDs wrapped up in an OT plugin. If I install this plugin in the OT, I'm able to successfully generate output from content that uses the public IDs defined by those DTDs. However, what I'd like is to include this plugin in an Oxygen framework, and have the custom doctypes honored for OT builds without "installing" the plugin. As it stands, users can install the framework and edit topics and maps using the custom doctypes. It validates fine and all is well, but when they go to do an OT build, it fails to recognize the location for the custom DTDs. I thought there was an OT parameter that let you specify the location of an alternate catalog file, but I'm not seeing that. Was hoping that I could get this to work by just having the users install the framework. It seems like my only options are (after installing the framework) .. - install and integrate the "doctypes" plugin into the default OT in Oxygen - OR .. provide another OT that has the doctypes plugin installed and have the users point to that as a custom DITA-OT in Oxygen Thoughts? Thanks! ...scott
participants (1)
-
Scott Prentice