Associating default DITA CSS with new DTD shells

[juliovaz]

Hi,
I've probably missed this in the help but I can't seem to figure out how to get my new DTD shells to display correctly in Author mode. I don't want to associate the default CSS with each new document, I want this to stay with the rest of my global options. How can I make this work? Thanks.

[Radu]

Hi Julio,

I will assume you are using Oxygen 15.2.
Basically you create (you probably already have) a folder on your disk in which the custom CSSs are located. Let's say the main CSS is called custom.css.
Then in the same folder you create an XML catalog file catalog.xml which has a single URI mapping like:

Code: Select all

<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">

  <uri name="http://www.oxygenxml.com/extensions/author/css/userCustom.css" uri="custom.css"/>

</catalog>

Then in the Oxygen Preferences->XML / XML Catalog page you add a reference to your XML catalog and reopen the topics, your CSS should be used as an additional layer in addition to all CSSs which come with the base DITA configuration in Oxygen.

http://www.oxygenxml.com/doc/ug-oxygen/ ... ports.html

Regards,
Radu

[juliovaz]

Hi Radu,

Unfortunately, the team I'm working with doesn't have oXygen 15.2 (don't ask, long story). However, what I want to do is associate the base CSS files supplied by oXygen with my new DTD shells (as they only incorporate a single element based on ph). I need this to work for 13 and 14. Thanks.

[Radu]

Hi Julio,

Did you integrate your DTD specialization in the DITA OT which comes with Oxygen?

http://www.oxygenxml.com/doc/ug-oxygen/ ... ation.html

If so, when opening a specialization topic Oxygen should auto-detect it to be DITA and apply the DITA CSSs to it (+ DITA toolbar, actions, validation, etc).

If this is not the case, maybe your specialization DTDs are not properly constructed.
In the Oxygen Preferences->Document Type Association page there is a DITA document type configuration. If you edit that, it has a set of association rules.
The last of the rules in that list is a custom rule which checks if the DITAArchVersion attribute is defined on the root element of the opened topic (the DTDs should add it as a default attribute to the root topic element).
You can add a new rule in the list specific for your public ID but as I said, that last rule we have in the DITA document type configuration should match any valid DITA specialization.
If you consider your specialization DTDs to be correct and Oxygen is still not recognizing your topics out of the box to be DITA, maybe you can email us some resources (DTDs, sample topics) and we'll take a look at them.

Regards,
Radu

[juliovaz]

Hi Julio,

Did you integrate your DTD specialization in the DITA OT which comes with Oxygen?

I think this is probably the issue. I've integrated the specialization with an external OT so it's not connected to the OT you supply. Later today, I'll see if adding a new rule for the publidID will help. Busy, busy, busy.

[juliovaz]

Adding in the rule worked. Thanks.