[Framers] BookComponentMIFWash.dll - ever any downside/risk ?

[Monique Semp]

Hello, Framers,

I believe that I can ease my template conversion project by “doing a MIF wash” on a book before I begin the template import/revision process.

Now that I know much more than I did when I last rebranded these docs (~6 years ago), and that the FrameMaker (2015) UI exposes much more info than before (such as the Fonts pod), I’m finding remnants of fonts and styles that were incompletely scrubbed during the last rebranding. I can manually take care of them by text-editing the MIF file and then using FrameMaker to convert the edited MIF back to FrameMaker. But my hope is that by MIF washing a book, I can get rid of those ancient artifacts much more easily.

So my question is, is there ever a downside or unintended side-effect from doing a MIF wash? I doubt it, but you never know...

(And, has anyone used the the FrameMaker-provided BookComponentMIFWash utility (as discussed in https://forums.adobe.com/thread/1471039, for FrameMaker 11) with FrameMaker 2015? I presume it’s valid because it’s in the expected \Samples\ScriptsandUtilities folder, and I’ve successfully installed/registered it and see the menu. But I haven’t tried it because I’m not quite sure how to tell if it is running ok.)

Thanks,
-Monique