35.6.5 Understanding which files are copied from where
If WrapPath has a value other than the project directory when you run a conversion, by default Mif2Go does the following:
• If the directory designated by WrapPath already exists, and EmptyWrapPath=Yes (the default), Mif2Go deletes the prior contents; otherwise Mif2Go creates the directory.
• After converting your document, Mif2Go copies necessary files from the project directory to the WrapPath directory (and to subdirectories, if appropriate). Table 35-2 lists the files that are copied by default.
For example, to have Mif2Go copy to the WrapPath directory only HTML files and just one particular JavaScript file from the project directory, and all other JavaScript files from another directory:
WrapCopyFiles = *.htm justone.js ..\jsfiles\*.js
With these settings, Mif2Go also copies graphics files and CSS files from the project directory, unless you specify otherwise; see §35.7 Placing graphics files for distribution and §35.8 Placing CSS or XSL files for assembly.
Table 35-2 Files copied by default to the wrap directory
* Second group of files is copied to the HTML subdirectory. See §11.3.7 Creating a directory structure for JavaHelp / Oracle Help. ** For OmniHelp, additional files are copied from a viewer directory; see §10.13 Assembling OmniHelp files for viewing. |
|||
For all output types, files specified by GraphCopyFiles (default *.gif, *.jpg, *.png, and *.svg for HTML, or *.bmp and *.wmf for RTF) are copied from the project directory to the GraphPath directory; or to a subdirectory, for JavaHelp and Oracle Help; see §35.7.1 Copying referenced graphics to a distribution directory.
For all HTML output types, files specified by CssCopyFiles (default *.css and *.xsl) are copied from the project directory to the CssPath directory; see §35.8 Placing CSS or XSL files for assembly.
> 35 Producing deliverable results > 35.6 Assembling files for distribution > 35.6.5 Understanding which files are copied from where