<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<style type="text/css">.mceResizeHandle {position: absolute;border: 1px solid black;background: #FFF;width: 5px;height: 5px;z-index: 10000}.mceResizeHandle:hover {background: #000}img[data-mce-selected] {outline: 1px solid black}img.mceClonedResizable, table.mceClonedResizable {position: absolute;outline: 1px dashed black;opacity: .5;z-index: 10000}
</style>
</head><body style="">
<div>
If you are using FM's native RTF, it's always been a bit dodgy.
</div>
<div>
(Though the PDF-to-Word exporter is even more so!)
</div>
<div>
</div>
<div>
I would *highly* recommend that you invest in a copy of MIF2Go (http://mif2go.com/). It provides a MUCH better output.
</div>
<div>
</div>
<div>
Grant
</div>
<div>
<br />> On February 21, 2014 at 7:20 AM "Harding, Dan" <dharding@illinois.edu> wrote:
<br />>
<br />>
<br />> Good morning,
<br />>
<br />> We have used the same authoring process for eons: Authors/editors work in MS Word, as well as preliminary indexing work. I then take the MS Word file, import into FM (unstructured) and do the final print-ready formatting, making things adhere to our publishing standards and tightening up consistency.
<br />>
<br />> As a process it work well... until it's time to revise the book for the next edition.
<br />>
<br />> Our authors and editors will ONLY work in MS Word. PDF comments/revisions will not work, as there frequently are extensive revisions including insertion of new sections (multiple pages) of content, as well as shuffling of content.
<br />>
<br />> When I export the final FM version back to MS Word for them to work on, the conversion is VERY crude and frequently requires extensive work on the post-conversion Word files for the editors to be able to work within the files.
<br />>
<br />> Then of course there's the reformatting from scratch in FM when the revisions are done (which actually is faster and more reliable than trying to reconcile changes in the MS Word version with the existing FM version).
<br />>
<br />> Is there a better way to perform the round-trip process given the MS Word requirement, and barring that, are there better ways/tools to get cleaner MS Word files from FM than exporting to RTF?
<br />>
<br />> Would making the change from unstructured to structured FM on my part help in this regard?
<br />>
<br />> Environment:
<br />>
<br />> Windows 7 64-bit Enterprise
<br />> Framemaker 10 (unstructured) [NOTE: TCS 5 is on order but I have not received it yet.]
<br />> Microsoft Office 2010
<br />>
<br />> Thank you in advance.
<br />>
<br />> Dan Harding
<br />> University of Illinois Tax School
<br />>
<br />> _______________________________________________
<br />>
<br />>
<br />> You are currently subscribed to framers as grant@hedgewizard.net.
<br />>
<br />> Send list messages to framers@lists.frameusers.com.
<br />>
<br />> To unsubscribe send a blank email to
<br />> framers-unsubscribe@lists.frameusers.com
<br />> or visit http://lists.frameusers.com/mailman/options/framers/grant%40hedgewizard.net
<br />>
<br />> Send administrative questions to listadmin@frameusers.com. Visit
<br />> http://www.frameusers.com/ for more resources and info.
</div>
</body></html>