Arbortext Editor (aka Epic) and its DITA Application are quite good
about using Public IDs and catalogs to resolve DTD references. So, if
you get your catalog(s) on to the Catalog path list before the catalogs
that are distributed as part of the product, I would expect everything
A possible exception to this is the rdstyle document type that is used
internally during Arbortext composition or any xxx-rdstyle document
types that you may have created. But this is only a concern if you have
created or added new specializations beyond those provided by OASIS and
even then only if you are doing your composition from within the
Arbortext product. It sounds as if you are using the DITA Open Tool Kit
for composition, and if that is the case, the rdstyle and xxx-rdstyle
doctypes don't matter. And even if they did matter, there is only an
issue if you do not include the new specializations in the ditabase
document type or if you add new topicref specializations. If you do
either of these things, then some customization of the rdstyle or
xxx-rdstyle document types may be needed.
You can look at the catalog files that the Arbortext DITA Application
uses. They are all located in the
.../application/com.arbortext.dita/doctypes folders, mostly in the
ditabase, map, and bookmap sub-folders. Please don't change these files,
but you can override them with your own catalog files.
You can check the Catalog path by looking at the Document tab on the
Session dialog (Help-->About Arbortext Editor-->Session). You can
change your catalog path list from the "File Locations" category on the
Editor's Preferences dialog (Tools-->Preferences). You need to make any
changes to the catalog path list early before any DITA documents have
been opened since open DTDs are cached and won't necessarily be reopened
again during the same Editor session.
You can set an initial value for catalog path using the APTCATPATH
environment variable. Be sure to include the %D symbolic parameter after
your own catalog path entries, so that the Editor will pick up all of
the DITA and non-DITA catalogs it needs. Arbortext catalog processing is
explained in online help, see Arbortext products overview-->Structured
documents-->Working with catalog files or enter help 6563 in the
Arbortext Command window.
Changes to the OASIS DITA DTDs and schemas have been mostly or perhaps
entirely backward compatible and mostly forward compatible as well. So,
I'd be surprised if you are running into version problems with your DITA
DTDs, but I guess it could happen.
What version of Arbortext Editor are you using? The current release
(5.3 M040) includes a very up-to-date version of the final/official
OASIS DITA 1.1 DTDs and schemas including recent errata. I don't think
there is anything newer. Older releases included the most recent OASIS
DITA DTDs and schemas at the time of the release, although the 5.3 M020
and 5.3 M030 releases may not have included the most recent errata.
Arbortext Editor 5.3 F000, M010, M020, and M030 all included the OASIS
DITA 1.1 DTDs and schemas before they had been finally and officially
approved by the OASIS process. Arbortext Editor 5.2 included the DITA
1.0.1 DTDs and schemas. Epic Editor 5.1 included the earlier IBM
versions of the DITA DTDs.
If you run into problems using your own catalogs with the Arbortext DITA
Application, please let us know. If there are problems, we'd like to get
them fixed as soon as we can.
PTC/Arbortext DITA Development Lead