Greg, Regarding: >Omsys.com's rtf export filter would do the best job if they want to use Word because it mimics the tags pretty well. >As soon as your client actually starts editing, though, they're going to notice lots of discrepancies in appearance. Might not matter to them though, if they aren't going to compare it to the FM version side by side.
More than discrepancies. You should try it first. Mif2Go rtf output is "editable" but it depends on what that consists of. Mif2Go basically strips the automation from the file and puts in manual characters. For example, all bullets and numbers in lists are like keyed entries. You can attach and load your Word template, apply an automated style, but you will still have the hard bullet or number to deal with. For extensive or long term "editing" there will need to be a clever automated method of removing the manual bullets and numbers. Unless someone knows a trick that I don't. Also cross-refs and variables become keyed characters, rather than automated, and I think the non-breaking space or something in Frame cross-refs is turned into a sort of o reverse bullet. Someone will want those removed. There are other matters I don't immediately recall. Someone will also want to resave the rtf output as doc before editing--the rtf becomes unwieldy. There are other limitations I don't recall offhand. But if you just want a Frame format mirrored in Word, for temporary use, Mif2Go does well. Definitely try it first to see if it will work for you and yours. Mike
