batch conversion to rtf

[FieryPantone]

Not my idea, I hasten to add <g> but a colleague is wondering whether there's an easy batch-approach to saving a slew of .fm files in rtf. My first thought was DZBatcher, but that particular option does not seem to be supported. FrameScript would be fine, except that a) no-one here yet knows how to use it; b) we're waiting for licences.<br /><br />All suggestions welcome.

[J_D_W]

There is a $10 plugin that does this for all files in a book, called RtfSave.

Jon

[AxialInfo]

Mif2Go does it http://www.omsys.com and is extremely programmable.

[FieryPantone]

Thanks for both tips; I already have my suspicions about which product the company bean-counters will prefer ;-} but shall take a good look at Mif2Go after seeing it mentioned here so often.

[AxialInfo]

Bruce's plugin is an enhancement to FM's built-in RTF export capabilities, which means it's a pretty much "one-way, my-way" export, no capabilities to finesse the transition.

MIF2Go is highly configurable.

They're opposite ends of the spectrum in getting to functional RTF or DOC files, if the goal is to create RTF/DOC that will "live on" after their FM incarnation.

[Art Campbell]

To amplify Sheila's explanation.... if all you need is to be able to pop open an RTF in Word or another application, the plugin may work, but it depends upon the robustness of the FM export filter.

If you want to hold on to the FM look and feel, you want MIF2Go.

Art

[FieryPantone]

Well, to give a bit of background information ... I feel the colleague in question is making a fundamental mistake by even considering converting his Frame files to .rtf, and that however thoughtful the conversion route might be he's more than likely to end up with inward-bound garbage and a lot of unforeseen problems when he tries to re-use the .rtf as a source for easy updates.<br /><br />I'll have another try at convincing him that for updates to a whole library of existing files he's better off distributing comment-enabled .pdf and accepting small changes as comments, larger changes as stand-alone .doc files. Works for me, with a pretty similar documentation set. [sideswipe - pity Adobe product A doesn't export comments direct to Adobe product B, but if ever there was a well-flogged dead horse it's integration between FM and Adobe <g>]<br /><br />I'll pass on your observations on Mif2Go, as well. Thanks for your input, which gives me a better understanding of (unflogged) horses for courses here.