35.6.3 Listing files to copy to the wrap directory

To list files for Mif2Go to copy to the wrap directory (for example):

[Automation]

WrapAndShip=Yes

; WrapCopyFiles = list of files to copy, separated by spaces

WrapCopyFiles = *.htm *.js

The file specifications you assign to WrapCopyFiles must be separated by spaces, but no spaces are allowed within a file specification. You can use wildcards in file specifications. File specifications can include absolute or relative paths to indicate where files should be copied from; the default is from the project directory, and relative paths are relative to the project directory. The destination is always the WrapPath directory; see §35.6.1 Specifying a wrap directory. 

Note:  WrapCopyFiles takes effect not only when WrapAndShip=Yes, but also when one of the following is true for the output type specified:

HTML Help: [Automation]CompileHelp=Yes

WinHelp: [Automation]CompileHelp=Yes

JavaHelp: [JavaHelpOptions]FTSCommand=path/to/indexer

Oracle Help: [OracleHelpOptions]FTSCommand=path/to/indexer

See §35.10 Gathering and processing Help-system files.

If no setting for WrapCopyFiles is present, certain files are copied by default from the project directory to the wrap directory. Table 35-1 lists the files that are copied by default for each output type.

Table 35-1 Default files copied from project directory to wrap directory

Output type	Files copied by default from project to WrapPath directory
HTML, XHTML, XML	*.htm *.html *.xhtm *.xhtml *.xml *.js *.dtd *.mod *.ent *.xsd
DITA	*.dita *.ditamap *.bookmap *.dtd *.mod *.ent *.xsd
Eclipse Help	*.htm *.js *.xml
HTML Help	*.htm *.js *.hh? *.h
OmniHelp	*.htm *.js
WinHelp	*.rtf *.hpj *.cnt *.h
Word	*.rtf

Note:  Never move output files; the originals must remain in the project directory to permit links to work from other files (whenever you convert less than a full document) and from other projects (always).

---