Omni Systems, Inc. Mif2Go User's Guide, Version 55
> 32 Working with content models > 32.7 Specializing or modifying DITA topic types > 32.7.5 Listing DITA topic type configuration files
When you provide a DITA
topictype
.ini
configuration file, you must list the name of the topic type in your
project configuration file, so Mif2Go knows you are specializing, and knows to look
for the name of the specialized configuration file.
To list specialized topic types, in your project configuration file specify the following:
DITAopictype = any text here (ignored)
Give each new type any alphanumeric name, except
the name of a built-in type; that is, you may not name a new
type topic
, concept
,
task
, reference
,
map
, or (for DITA version 1.1) glossary
.
List the name of a built-in topic type only
if you are overriding a feature of that topic type.
You can put whatever you want to the right of the equals sign; Mif2Go reads only the topic type name to the left of the equals sign.
Provide a DITA
topictype
.ini
configuration file named for each topic type you list; see §32.2.2 Generating a content model from a DTD.
or §32.7.2 Overriding settings in a DITA content model.
Mif2Go loads each listed DITA
topictype
.ini
configuration file at start-up, after initializing internal values for
the built-in base topic types.
You do not have to list a topic type if the type
is explicitly requested through an assignment to [DITAOptions]DefTopic
(see §15.9.2.2 Specifying a default DITA topic type),
or in a DITATopic marker, in which case the corresponding DITA
topictype
.ini
configuration file loads on demand. If the topic type information replaces
one or more of the built-in types, this is the best way to load it.
If you create a new topic type that is derived from another new type, you can optionally list only the last topic type in the chain to get the whole batch loaded. Listing all types in the chain is harmless, but unnecessary.