<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="Verdana">Thanks, Stefan!</font></p>
<p><font face="Verdana">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 ..</font></p>
<p><font face="Verdana"> 1) Install framework, <br>
2) Point to custom OT in Preferences</font></p>
<p><font face="Verdana">That way if something goes sideways, they
haven't messed with the detail Oxygen installation.</font></p>
<p><font face="Verdana">Cheers,<br>
...scott<br>
</font></p>
<p><font face="Verdana"></font><br>
</p>
<div class="moz-cite-prefix">On 12/20/22 11:33 AM, Stefan Jung
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1491869537.31575.1671564822215@office.mailbox.org">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta charset="UTF-8">
<div> Hey Scott, </div>
<div> <br>
</div>
<div> 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. </div>
<div> <br>
</div>
<div> BR </div>
<div> <br class="prevent-remove">
</div>
<div> <br class="prevent-remove">
</div>
<div> <br>
</div>
<div class="ox-mail-signature"> Gesendet mit OX Mail </div>
<div> <br>
</div>
<div class="reply-header"> Scott Prentice <<a
href="http://sp14@leximation.com" rel="noopener noreferrer"
moz-do-not-send="true">sp14@leximation.com</a>> hat am
December 20, 2022 um 8:25 PM geschrieben: </div>
<div class="ox-mail-content-wrapper">
<blockquote class="quoted-mail">
<p><font face="Verdana">I think I know the answer to this
question, but want to confirm that I'm not missing
something.</font></p>
<p><font face="Verdana">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. <br>
</font></p>
<p><font face="Verdana">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.</font></p>
<p><font face="Verdana">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.<br>
</font></p>
<p><font face="Verdana">It seems like my only options are
(after installing the framework) ..</font></p>
<p><font face="Verdana">- install and integrate the "doctypes"
plugin into the default OT in Oxygen</font></p>
<p><font face="Verdana">- OR .. provide another OT that has
the doctypes plugin installed and have the users point to
that as a custom DITA-OT in Oxygen<br>
</font></p>
<p>Thoughts?</p>
<p>Thanks!<br>
...scott</p>
</blockquote>
</div>
</blockquote>
</body>
</html>