If you plan to use a built-in content model as is, you do not need to do anything described in this section.
To prepare a new, modified, or replacement content-model configuration for use with DITA2Go:
If you generated the content model from a DTD and you plan to rerun dtd2ini, also include in configuration file dtd2ini.ini as overrides any [Topic] and [*Table] settings you add. See dtd2ini.txt for instructions.
[Topic] ; ModelName = name of type (usually a built-in) to be replaced ; after this file loads, effective only when this file is ; specified in [DITAContentModels] or ; [DocBookOptions]ContentModel in the project configuration file; ; overrides the default use of the filename (without "DITA"). ModelName = contentmodelname
ModelName specifies either the name of an existing content model to be replaced by the current content model, or a name for the new content model to be added.
If you are replacing a built-in content model, the value for ModelName must be one of the following, depending on the output type:
If you assign any other value to ModelName, DITA2Go adds the new name to the list of models. For example, to add a new DITA topic type widget defined in content-model configuration file DITAwidget.ini, in DITAwidget.ini you would include the following setting:
[Topic] ModelName = widget
To replace the built-in DITA reference content model with a model you have defined in content-model configuration file DITAmyref.ini, in DITAmyref.ini you would include the following setting:
[Topic] ModelName = reference
For DITA, add the base name of each new or modified content-model configuration:
[DITAContentModels] ; Topic type name = any text (not used) DITAtopictype = replaced or new topictype content model
For DocBook, specify the base name of the new or modified content-model configuration:
[DocBookOptions] ; ContentModel = name of content-model .ini, without extension, ; with which to replace the built-in DocBook 4.5 content model. ContentModel = otherdocbookmodel