Hi Sander,
sverhagen wrote:I've made a specialization in DITA-OT (put it in my DITA-OT1.5.4/demo/xxx folder), ran the integrator and added the resulting catalog-dita.xml to my document type in oXygen. I'm getting, though:
Code: Select all
Cannot load the associated CSS file(s).
The error was: 'No CSS file specified.'
Adding the
catalog-dita.xml file of
only one DITA-OT from only one documentation project (
/documentation/architecture,
/documentation/glossary, etc.) should be enough, you don't have to add the
catalog-dita.xml file of the DITA-OT of
every documentation project, because in your case every project has a copy of the same DITA-OT (downloaded/checked out from the same repository). Adding the
catalog-dita.xml file of a DITA-OT that is external to Oxygen is enough for validating and editing the specialized topics in Oxygen Author mode. Editing in Author mode should work on your DITA customization out of the box using the same styles
if you followed the DITA specialization guidelines (for
DITA 1.0 or
DITA 1.2), more specifically if your specialized DTD/schema keeps the
DITAArchVersion attribute on the root element of your specialized topics. If the
DITAArchVersion attribute is detected by the XML parser on the root element (either explicitly in the XML topic file or as default attribute in the specialized DTD/schema associated with it) then the last rule from the
Association rules tab of
the DITA document type will match your specialized topic files. If you look in
the DITA document type you can see that this rule specifies the Java class
DITATopicCustomRuleMatcher which checks only the presence of the attribute (the source code of this class in included in the
Oxygen Author SDK). That means if this attribute is present all the settings of the Oxygen built-in DITA document type will be applied to the specialized topics exactly as for the standard DITA topic files, so they will be edited in Author mode with the same styles.
You can check that by looking in the
Properties view (go to menu
Window -> Show View -> Properties) when the cursor is in a specialized topic which you have opened in Oxygen. Does the table from the
Properties view contain a row
Document type? What is its value? It should be
DITA.
Also validating a specialized topic from your projects in Oxygen should tell us if the specialized DTD/schema was detected correctly using the catalog-dita.xml which you added in the DITA document type. Does the validation action report errors? What are the errors?
sverhagen wrote:The bottleneck is thus that each of our documentation projects has its own DITA-OT instance (downloaded by Maven, and customizations and specializations inserted by Maven also). All of these projects have DITA files, which in oXygen I'd like to treat as the same.
If you only want to edit the topics and maps in Oxygen and you do not need to test in Oxygen the transformation of your DITA maps to PDF, XHTML, etc. then you just need to add only one
catalog-dita.xml file as I said above. That should be enough. So you do not really have a bottleneck for editing in Oxygen. If you need also to test a transformation using Oxygen's DITA-OT you should chain your
catalog-dita.xml file to the
catalog-dita.xml file from Oxygen's DITA-OT using a
<nextCatalog> element.
sverhagen wrote:That all being said... back to the actual CSS files. Isn't there a way that oXygen can reuse the generic styles? After all: my specializations are done by inheritence. That's the only reason why the FO process knows what to do. Why don't oXygen know what to do?
Oxygen should reuse the generic styles out of the box if the specialization keeps the
DITAArchVersion attribute on the root element of the topics. Please check the validation of a specialized topic and the content of the
Properties view for a specialized topic. Does it match Oxygen's built-in DITA document type? If not it seems your specialization was not defined correctly. If yes please
send us some sample files (using our
form for reporting problems) for finding why the standard DITA styles are not applied in Author mode but instead you get the error:
Code: Select all
Cannot load the associated CSS file(s).
The error was: 'No CSS file specified.'
Regards,
Sorin