[oXygen-user] Custom DTDs with default Oxygen OT

[Scott Prentice]

It's interesting to see that Chemistry apparently honors the catalog 
defined in the framework, so you can do a PDF build from content using a 
custom doctype with just the framework installed. Not exactly what I 
need, but good to know!

...scott


On 12/20/22 11:46 AM, Scott Prentice wrote:
>
> Thanks, Stefan!
>
> Yeah .. I was hoping to avoid having the users install a plugin .. 
> just install the framework. But I can see that's not going to fly. I'm 
> thinking that the simplest (least effort for the users, and least 
> opportunity for error), is to provide a pre-configured OT installation 
> that they can point to from Preferences. It'll just be ..
>
>     1) Install framework,
>     2) Point to custom OT in Preferences
>
> That way if something goes sideways, they haven't messed with the 
> detail Oxygen installation.
>
> Cheers,
> ...scott
>
>
> On 12/20/22 11:33 AM, Stefan Jung wrote:
>> Hey Scott,
>>
>> You should bundle the grammar files in a toolkit plugin. This is 
>> correct. In your oxygen framework you need to configure the matching 
>> rules to recognize your custom grammar files. You need to install 
>> your plugin to the DITA-OT as well. You need to use 
>> the dita.specialization.catalog.relative extension point in your 
>> plugin.xml.
>>
>> BR
>>
>>
>>
>> Gesendet mit OX Mail
>>
>> Scott Prentice <sp14 at leximation.com <http://sp14@leximation.com>> hat 
>> am December 20, 2022 um 8:25 PM geschrieben:
>>
>>     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
>>
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20221220/cdda4f11/attachment.htm>