33.7 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, project file, FileID file
D:\MyDoc\Graphics Graphics (before conversion)
D:\MyDoc\Out Mif2Go output and configuration file
And you want the files for
your HTML project assembled as follows:
D:\MyDoc\Out\Wrap HTML files should be copied here
D:\MyDoc\Out\Wrap\images Graphics files should be copied here
D:\MyDoc\Out\Wrap\styles CSS files should be copied here
Your project file (.prj, in D:\MyDoc with
your FrameMaker files) would specify D:\MyDoc\Out
as the path for Mif2Go to use for output.
D:\MyDoc\Out is also where the configuration
file, mif2htm.ini, is located.
To get all the files where
you want them, in the configuration file you would specify the following:
Section
|
Setting
|
[Automation]
|
WrapPath=.\Wrap
A location relative to the
project folder. You could just as well use the absolute path: WrapPath=D:\MyDoc\Out\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 the graphics
for this project. Path separators are backslashes.
|
GraphCopyFiles=*.jpg
*.gif
Files you want out of the
CopyGraphicsFrom folder.
|
[CSS]
|
CssPath=./styles
Where CSS files should be
relative to the HTML files that use them (that is, relative to the WrapPath folder). This path requires a forward slash, because it is used 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 folder). This path
requires a forward slash, because it is
used in the HTML files.
|
> 33 Producing deliverable results > 33.7 Gathering files for an HTML project: an example