🚀 go-pugleaf

If it's just a simple replace of "$docid$" with another string in
two files, I would go for converting those 2 files to MIF and
perform a replace directly. If you have other "$docid$" strings
that should not be replaced, you must of course be careful to
only replace the correct ones, and this might be a bit tricky,
depending on how much Perl or other text processing tools you know.

> If the MIF template is better, do I need to include all of the
> Pgf lines or just:

Interesting question. I have actually never used MIF snippets
for import purposes. But, I guess that when FM is told to open
the MIF file (via fmbatch), it must create a complete paragraph
format, and the parts you haven't specified will be "replaced"
by some defaults, which are then imported into your files.
So I think you need to specify the entire paragraph tag.

> Also, regarding converting the MIF template to FM before importing
formats;
> is there a reason it may be better to do so (less potential for errors)?

Not really. However, by converting to a FM file you will see
what FM adds to the MIF file when opening it.

NOTE: there's another way to import MIF files, by using File>Import>File
(not Formats), importing by copy, and specifying a MIF file. In that case,
only the actual MIF statements are imported, nothing else. The MIF file
is never opened by FM and nothing is added to the file. You can do all
sorts of magic this way, BUT you cannot import files via fmbatch...


--
/Thomas Michanek, FrameMaker/UNIX/MIF expert
http://go.to/framers/