33.4.2 Listing files to copy to the assembly folder

To list files for Mif2Go to copy to the assembly folder:

[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 folder, and relative paths are relative to the project folder. The destination is always the WrapPath folder; see §33.4.1 Specifying an assembly folder. 

Note:

WrapCopyFiles takes effect not only when WrapAndShip=Yes, but also when either of the following is true: CompileHelp=Yes FTSCommand=path/to/indexer See §33.8 Gathering and compiling Help-system files.

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

Table 33-1 Default files copied from output to assembly folder

Output type	WrapCopyFiles copied by default from output to WrapPath folder
HTML, XHTML, XML	*.htm *.html *.xml *.js *.dtd *.mod *.ent *.txt *.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 HTML files; they must remain in the project folder to permit links to work from other files (whenever you convert less than the full book) and from other projects (always).

---

> 33 Producing deliverable results > 33.4 Assembling files for distribution > 33.4.2 Listing files to copy to the assembly folder