33.5.1 Copying graphics files to the assembly folder or subfolder
When you specify WrapAndShip=Yes and designate a WrapPath folder, Mif2Go automatically copies graphics files from the project folder to the folder designated by [Graphics]GraphPath. Mif2Go can also automatically copy graphics files from another folder you specify.
To specify which graphics files to copy and from where:
; CopyGraphicsFrom = path to dir containing the graphics files,
CopyGraphicsFrom=path\to\graphics\files
; GraphCopyFiles = list of files to copy from CopyGraphicsFrom
CopyGraphicsFrom and GraphCopyFiles take effect when WrapAndShip=Yes, CompileHelp=Yes, or FTSCommand=path\to\indexer (see §33.8 Gathering and compiling Help-system files).
Say where to get graphics files
When you specify a value for CopyGraphicsFrom, graphics files are copied first from the project folder (unless it is the same as the destination folder), then from the folder designated by CopyGraphicsFrom, to one of the following destinations:
• for JavaHelp and Oracle Help for Java, the folder designated by [JavaHelpOptions]GraphSubdir (see §10.2.7.2 Letting Mif2Go set up the folder structure and copy files)
• for other HTML output types (and DCL output), the folder designated by [Graphics]GraphPath, if any (see §33.5.3 Synchronizing graphics settings for HTML output), otherwise the WrapPath folder
• for RTF output types (and MIF output), the folder designated by WrapPath.
If you specify a relative path for CopyGraphicsFrom, that path is relative to the project folder.
List graphics files to be copied
You can use GraphCopyFiles to list files to be copied. Table 33-3 shows which graphics files are copied by default for each output type. Files assigned to GraphCopyFiles are always copied first from the project folder, then from the CopyGraphicsFrom folder (if any). If GraphCopyFiles is not specified, or is set to nothing, all relevant graphics files are copied from the project folder and then from the CopyGraphicsFrom folder (if any).
Table 33-3 Default graphics files copied for assembly
The file specifications you assign to GraphCopyFiles must be separated by spaces, and no spaces are allowed within a file specification. You can use wildcards in file specifications, and include absolute or relative paths to indicate where graphics files should be copied from. If you do not specify a path, the default is first from the project folder, then from the CopyGraphicsFrom folder (if any). If you specify a relative path, the path is relative to the project folder.
For example, to have Mif2Go copy graphics files for standard HTML output from folder MyGraphics, parallel to the project folder, to folder Images, a subfolder of the WrapPath folder:
; WrapPath is relative to the project folder:
; CopyGraphicsFrom is relative to the project folder:
CopyGraphicsFrom=..\MyGraphics
; GraphPath is relative to the WrapPath folder:
Synchronize with other settings
If you plan to use CopyGraphicsFrom, make sure other graphics settings in the configuration file are consistent with the setting for WrapPath. See:
§33.5.3 Synchronizing graphics settings for HTML output
§33.5.4 Synchronizing graphics settings for RTF output
If you need to copy graphics from more than one folder, use book or file wrap commands; see §32.4.2 Executing system commands before and after conversion. These commands allow you to copy files after conversion (including after graphics generation) but before compilation or other [Automation] operations. Make sure you leave [Automation]EmptyGraphPath=No to avoid deleting the files copied this way. If you want to clear out the destination folder first, do it as part of a book or file wrap command.
> 33 Producing deliverable results > 33.5 Placing graphics files for distribution > 33.5.1 Copying graphics files to the assembly folder or subfolder