🚀 go-pugleaf

Ingrid:

I've successfully used a FrameMaker to RTF workflow for purposes of capturing review comments for several years.

Normally, saving a file to RTF will produce a reasonable facsimile of the FrameMaker file, albeit with a few formatting "inaccuracies". I use is a piece of email boilerplate that explains to the addressee that things like clickable cross-references and other niceties are lost during the export process; if an addressee is concerned about document appearance, I send a PDF along with the RTF for their viewing pleasure. The boilerplate also reminds people how to enable Word's Track Changes feature.

Before transmitting an RTF for review, I prefix the filename with "yyyy-mm-dd_hhmm_[iii]", where "iii" identifies the reviewer. This is for my own sanity, enabling me to keep track of iterations and reviewers as various review drafts fly around the organization.

Because RTF files are text-based rather than binary (ala DOC files), that you can use an archive tool like ZIP to compress the files. Since the primary reason for using RTFs is to avoid version incompatibilities, if you're sure a reviewer can open also an RTF in Word, then save it as a binary, and thus smaller, DOC file...

When it comes time to incorporate the RTF-based changes I typically just use copy "CTRL+v RETURN" to paste revised content from the RTF as plain text, then apply whatever formatting is required.

Cheers & hope this helps,
Riley