4.1.6 Checking output type and file extension
The project configuration file that DITA2Go
Project Manager copied to your output directory when you set up your
conversion project already contains the correct setting for the output
type (which is indicated by the configuration file name). Do not change
this setting.
Table
4-1 shows the name of the project configuration file for each output
type, and the preset extension for output files. You can change the setting
for the output file extension, for all output types except WinHelp.
For example, to specify a different file extension
for HTML output:
[Setup]
; FileSuffix = suffix used for output file extension and in
; cross references
FileSuffix = .html
The leading dot on the extension is optional.
Table 4-1 Output types, file extensions,
project configuration files
HTML-based Help
|
Eclipse Help
|
.htm
|
_d2eclipse.ini
|
21
|
Microsoft HTML Help
|
.htm
|
_d2htmlhelp.ini
|
18
|
JavaHelp
|
.htm
|
_d2javahelp.ini
|
20
|
OmniHelp
|
.htm
|
_d2omnihelp.ini
|
19
|
Oracle Help for Java
|
.htm
|
_d2oraclehelp.ini
|
20
|
HTML
|
Standard HTML
|
.htm
|
_d2html.ini
|
22
|
XHTML
|
.xhtml
|
_d2xhtml.ini
|
22
|
XML
|
DITA XML
|
.dita (not settable)
|
_d2dita.ini
|
24
|
Docbook XML
|
.ent
|
_d2docbook.ini
|
26
|
Generic XML
|
.xml
|
_d2xml.ini
|
23
|
RTF
|
WinHelp
|
.rtf (not settable)
|
_d2winhelp.ini
|
17
|
Print RTF
|
.rtf
|
_d2rtf.ini
|
15
|
Previous Topic: 4.1.5 Accommodating
paths to network drives
Next Topic: 4.1.7 Producing
print output selectively
Parent Topic: 4.1 Specifying
operating settings
Sibling Topics:
4.1.1 Connecting to
XML catalogs
4.1.2 Accommodating
specializations
4.1.3 Specifying a
DITA XML DTD
4.1.4 Generating
a map from a DITA topic file
4.1.5 Accommodating
paths to network drives
4.1.7 Producing
print output selectively
4.1.8 Including
element tags and paths in output
4.1.9 Reusing
or discarding ASCII DCL files
4.1.10 Specifying
how to treat cases, spaces, and wildcards