35.9 Gathering files for
an HTML project: an example
Suppose your file structure
looks like this:
D:\AllDocs\CSS CSS files for all HTML projects
D:\MyDoc FrameMaker files, projects file,
FileID file
D:\MyDoc\Graphics Graphics
D:\MyDoc\HTML Mif2Go
output files and project configuration file
And you want the files for
your HTML project assembled as follows:
D:\MyDoc\HTML\_wrap HTML files should be copied here
D:\MyDoc\HTML\_wrap\images Graphics files should be copied here
D:\MyDoc\HTML\_wrap\styles CSS files should be copied here
Your projects file (.prj, in D:\MyDoc with
your FrameMaker files) would specify D:\MyDoc\HTML as the path for Mif2Go to use for output. D:\MyDoc\HTML is also where your project configuration
file is located.
To get all the files where
you want them, in the configuration file you would specify the following:
![[spacer]](1p.gif)
Section
|
Setting
|
[Automation]
|
WrapPath=.\_wrap
|
A location relative to the
project directory. You could just as well use the absolute path: WrapPath=D:\MyDoc\HTML\_wrap. Notice the
backslashes here, which are required for
Windows.
|
CopyCssFrom=D:\AllDocs\CSS
|
Where to find the CSS files
for this project. Path separators are backslashes.
|
CopyGraphicsFrom=D:\MyDoc\Graphics
|
Where to find graphics for
this project. Path separators are backslashes.
|
GraphCopyFiles=*.jpg *.gif
|
Files you want from the CopyGraphicsFrom directory.
|
[CSS]
|
CssPath=.\styles
|
Where CSS files should be
relative to the HTML files that use them (that is, relative to the WrapPath directory). Mif2Go converts backslashes to forward
slashes before writing these references in the HTML files.
|
[Graphics]
|
GraphPath=.\images
|
Where the graphics should
be relative to the HTML files that reference them (that is, relative
to the WrapPath directory). Mif2Go converts backslashes to forward
slashes before writing these references in the HTML files.
|
> 35 Producing deliverable results > 35.9 Gathering files for an HTML project: an example
