<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:12.0pt;
font-family:"Times New Roman","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-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi, Joseph.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>You are not the only one who is abandoning FrameMaker … if you look at my posts in the past months, I have done the same although I have been using it since 1988 off and on. I am still on the list for old times sake, though. </span><span style='font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Please do send me your detailed reasons in an off-list e-mail – would like to know <i>your</i> decision trigger! For me, it was the (a) recent over-pricing for some version upgrades that should have been done as free bug fixes, (b) the Adobe trend (albeit not yet announced for FrameMaker) to SAAS as the only licensing mechanism, and (c) their abandonment of small users (i.e., number of licenses) from their multi-year update licensing system.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Today, <b>all</b> my new documents are no longer in FrameMaker. I am <i>only</i> using it for maintaining and changing old documents, and if the change is large enough, I move it off FrameMaker. That takes a couple of days – even for the large documents – and then I am fine for the future! In time, all my old documents will be moved from FrameMaker.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>However, I have not chosen Flare as my platform, although it looks quite capable. Switching to it is expensive (of course, if they made me a $199 one-time offer to switch from FrameMaker to Flare, I would do it! </span><span style='font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>For now, <i>for my needs (which may not apply to everybody)</i>, a combination of Word 2013 for short documents (less than 10 to 20 pages), and LaTex (for large multi-hundred page specifications) is proving quite workable. Not perfect, and not as flexible as FrameMaker, but the costly “upgrades” of FrameMaker is not acceptable, and the trend to equally costly SAAS is a deal-breaker.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>BTW, LaTeX in particular allows me to achieve *<b>complete</b>* look-and-feel consistency in my specifications – formatting is separate from text entry – and I value that highly. It was my reason for selecting FrameMaker over Word about 12 years ago for my current company.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards, and good luck!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Z<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> framers-bounces@lists.frameusers.com [mailto:framers-bounces@lists.frameusers.com] <b>On Behalf Of </b>Joseph Lorenzini<br><b>Sent:</b> Saturday, October 26, 2013 10:13 AM<br><b>To:</b> FrameMaker Forum; TCS-Users@googlegroups.com<br><b>Subject:</b> So Long and Thanks for the Fish -- Migrating from FrameMaker to Flare<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Hi all,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I have used FrameMaker for over 5 years. I have used it to produce thousands of pages of documentation. And I honestly thought that FM was a great tool...for a time. Plus, the community was super helpful. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>So its with some regret that I am telling you that I am leaving this community and the TCS suite. I am adopting Flare as a replacement. Please note I am no evangelist of Flare nor do I think that there's One Right Tool. FrameMaker can be a great solution for some and if works for you then great. The reasons why I made this choice were driven by a specific business and use case<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>There are many reasons for this but that would cause this post to grow quite large and I didn't want to flood this community with a gigantic post about why I am not using its tool anymore.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>That said, my experience of why and how i migrated may be of interest to others in this forum. If you'd like a detailed explanation and are curious to learn more, I would be happy to share those details with you offline. Feel free to email me.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Sincerely,<o:p></o:p></p></div><div><p class=MsoNormal>Joseph Lorenzini<span style='color:#1F497D'><o:p></o:p></span></p></div></div></div></body></html>