<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi, all.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As part of my project to move all my documents from FrameMaker to Confluence, I had been planning to use Mif2Go to get my FM documents into other formats.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Well, the opportunity to test/start a similar process arose sooner than I expected. One of my specifications needed urgent updates by a SME for me to check later. The SME only has Word and I have not yet moved any documents to Confluence, so I decided to create a Word version for now (which I can _later_ move to Confluence after the updates are done).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So, I bought Mif2Go ... with some trepidation ... fully expecting to spend a <i>_lot_</i> of time understanding how to get the result I wanted, asking a lot of questions of Jeremy, not getting the right output, doing a ton of editing (FrameMaker _<i>and</i>_ Word), writing software to massage/edit the MIF files, tearing my hair out, etc., etc., etc.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><i>In reality, the effort was relatively smooth … without having to send a single e-mail to Omni Systems and Jeremy for support or questions!</i><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In less than a day’s worth of work (includes some hours reading the Mif2Go documentation), with only minor edits to the original FrameMaker files, I was able to create a perfectly structured and clean Word version of a 140 page document – paragraph formats, character formats, and all. It can easily be edited by the SME now and I can move the final doc to Confluence later.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The only real issue I encountered was auto-numbering – the FrameMaker capabilities are much better than Word. But, I had already anticipated that this would cause me some trouble (based on my read of the Mif2Go documentation).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I use quite "standard" chapter and section numbering in my specifications (the usual "1", "1.1", "1.1.1" stuff) but I also use auto-numbering for text in some paragraphs that extend into the side-heads for "Notes" messages, as well as specification numbering paragraphs using variables as part of the auto-number.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thus, I had to make a choice as to how to bring these auto-numbers over - the controls in Mif2Go cannot (not surprisingly) be tweaked to accommodate for all FrameMaker auto-number possibilities in a general way. After some testing (and editing sessions in Word) that showed the trade-offs between multiple approaches, I was able to pick one that minimized the final edits to the Word document (with minor edits to the paragraph designs in FrameMaker).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The results were not perfect, but with some manual editing, in about 5 or 6 hours of effort (spread out over a couple of afternoons), I was done transferring this 130 page document to Word! The drawings in the document will need changes later, but this can wait – they will need to be created/edited using other tools even when using Confluence.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Without Mif2Go, I believe that I would have had to spend <i>many</i> days ... bringing in bare text manually to Word and then adding in all the format fixes (for example, for emphasized text, bolding, etc.). <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So, thanks, Jeremy! Mif2Go is excellent and deserves all the kudos it gets. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Z<o:p></o:p></p></div></body></html>