<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="Verdana">Thanks, Radu.</font></p>
<p><font face="Verdana">Yes, I had seen those github discussions,
and had hoped that maybe something had been implemented. Seems
like a reasonable feature.</font></p>
<p><font face="Verdana">We're trying to use the
com.oxygenxml.pdf.css plugin, which I assume requires special
licensing if used outside of the default install .. ? Will look
into the options.</font></p>
<p><font face="Verdana">Regards,<br>
...scott<br>
</font></p>
<pre class="moz-signature" cols="72">
</pre>
<div class="moz-cite-prefix">On 3/26/24 10:01 PM, Oxygen XML Editor
Support (Radu Coravu) wrote:<br>
</div>
<blockquote type="cite"
cite="mid:ac6b7b5b-a6b2-4bb6-a827-333b80678b0a@oxygenxml.com">Hi
Scott,
<br>
<br>
As you seem to have a custom DITA OT installation inside your
custom framework, why don't you also use it as a default engine
for publishing in the Oxygen Preferences->DITA page?
<br>
<br>
Other than that, the DITA OT needs to have a plugin containing
extra catalogs (or as a hack you need to manually make changes to
the "catalog-dita.xml" inside the DITA OT). There is no
possibility to enforce an extra set of XML catalogs from the
exterior when starting the DITA OT. At some point I wished there
was such a way:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/dita-ot/dita-ot/issues/1515">https://github.com/dita-ot/dita-ot/issues/1515</a>
<br>
<br>
Also Jarno Elovirta experimented at some point with a way to
install plugins in the DITA OT without the need to change any
files in the DITA OT folder itself, this pull request was
abandoned though:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/dita-ot/dita-ot/pull/3152">https://github.com/dita-ot/dita-ot/pull/3152</a>
<br>
<br>
Regards,
<br>
<br>
Radu
<br>
<br>
Radu Coravu
<br>
Oxygen XML Editor
<br>
<br>
On 3/27/24 02:08, Scott Prentice wrote:
<br>
<blockquote type="cite">I've got a custom framework that includes
an OT installation that provides our custom doctype files and
custom plugins. Editing topics that use this custom doctype is
handled without problems, and using transformation scenarios
that are supported by the embedded OT also works fine. But, I'd
like to use an OT target that lives in the default Oxygen OT
installation. My Oxygen DITA settings still point to the
"built-in" OT, so when I set up a transformation scenario for
the Oxygen OT target, it starts to work, but fails when it can't
find the custom DTD.
<br>
<br>
When I add a pointer from
[OXYGEN]/org.dita.base/catalog-dita.xml that references my
custom catalog, the build completes fine. BUT .. I don't want to
modify the default Oxygen installation files.
<br>
<br>
Some thoughts ..
<br>
<br>
- I don't think there's a param that I can add to the
transformation scenario to reference my custom catalog .. is
there?
<br>
<br>
- I've tried adding my catalog in Settings > XML > XML
Catalog .. but that didn't seem to have any affect.
<br>
<br>
Is there any way to add a custom catalog without editing the
default Oxygen files?
<br>
<br>
Currently using Oxygen 25.1.
<br>
<br>
Thanks!
<br>
<br>
...scott
<br>
<br>
<br>
_______________________________________________
<br>
oXygen-user mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:oXygen-user@oxygenxml.com">oXygen-user@oxygenxml.com</a>
<br>
<a class="moz-txt-link-freetext" href="https://www.oxygenxml.com/mailman/listinfo/oxygen-user">https://www.oxygenxml.com/mailman/listinfo/oxygen-user</a>
<br>
<br>
</blockquote>
_______________________________________________
<br>
oXygen-user mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:oXygen-user@oxygenxml.com">oXygen-user@oxygenxml.com</a>
<br>
<a class="moz-txt-link-freetext" href="https://www.oxygenxml.com/mailman/listinfo/oxygen-user">https://www.oxygenxml.com/mailman/listinfo/oxygen-user</a>
<br>
</blockquote>
</body>
</html>