<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style>
<!--
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
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
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p
{margin-right:0in;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif"}
span.EmailStyle19
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.BalloonTextChar
{font-family:"Tahoma","sans-serif"}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
{}
-->
</style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">It seems odd, considering that Word is pretty much the standard corporate word processor.
</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">As it is, I will probably keep using WebWorks ePublisher in place of Frame’s native output because I can use it to seamlessly integrate Word and FrameMaker
docs in a WebWorks project. </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Regards</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Keith</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> Matt Sullivan [mailto:sullivanmattr@gmail.com]
<br>
<b>Sent:</b> Thursday, January 16, 2014 1:54 PM<br>
<b>To:</b> Keith Soltys<br>
<b>Cc:</b> framers@lists.frameusers.com<br>
<b>Subject:</b> Re: FrameMaker 12 released</span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"> </p>
<p class="MsoNormal" style="margin-left:.5in">@Keith, I am not aware of additional Word import functionality, although in the past, filters have been updated to the latest Word versions at time of release. Improved Word import is not one of the “themes” of
the release.</p>
<div>
<div>
<div>
<p style="margin-left:.5in"><span style="font-family:"Arial","sans-serif"; color:black"><br>
-Matt</span></p>
<div id="sig">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-family:"Arial","sans-serif"; color:#003399">Matt R. Sullivan</span></b><span style="font-family:"Arial","sans-serif"; color:#003399"> </span><span style="font-size:7.5pt; font-family:"Arial","sans-serif"; color:#003399"><br>
<strong><span style="font-family:"Arial","sans-serif"">co-author <a href="http://framemaker11book.com/">Publishing Fundamentals: Unstructured FrameMaker 11</a></span></strong> <br>
<strong><span style="font-family:"Arial","sans-serif"">P:</span></strong> 714.798.7596 | <strong><span style="font-family:"Arial","sans-serif"">C:</span></strong> 714.585.2335 | <a href="mailto:matt@mattrsullivan.com">matt@mattrsullivan.com</a> <br>
<br>
<a href="http://twitter.com/mattrsullivan">@mattrsullivan</a> <a href="http://www.linkedin.com/in/mattrsullivan">linkedIn</a> <a href="http://www.facebook.com/mattrsullivan">facebook</a> <a href="http://mattrsullivan.com/">mattrsullivan.com</a> </span><span style="font-family:"Arial","sans-serif"; color:#003399"></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> </span></p>
</div>
</div>
<p class="MsoNormal" style="margin-right:0in; margin-bottom:12.0pt; margin-left:.5in">
</p>
</div>
<p class="MsoNormal" style="margin-left:.5in"> </p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">On Jan 15, 2014, at 6:35 AM, Keith Soltys <<a href="mailto:keith.soltys@tmx.com">keith.soltys@tmx.com</a>> wrote:</p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br>
</p>
<p class="MsoNormal" style="margin-left:.5in">From a scan of their product pages and the few reviews out now, this looks like a compelling upgrade. I passed on FM 11 because most of the new features seemed oriented to structured authoring. This release has
the number one item on my list of requested feature enhancements - regular expressions in search. That alone would be worth the upgrade to me.<br>
<br>
The improved conditional text pod, smart catalogs, and other GUI enhancements are also good.<br>
<br>
I would like to know if they've improved the MS Word import. I didn't see any mention of that anywhere.<br>
<br>
Regards</p>
</div>
<p class="MsoNormal" style="margin-left:.5in"> </p>
</div>
<font size="2" face="arial"><br>
NOTICE OF CONFIDENTIALITY This e-mail, including all materials contained in or attached to this e-mail, contains proprietary and confidential information solely for the internal use of the intended recipient. If you have received this email in error, please
notify us immediately by return e-mail or otherwise and ensure that it is permanently deleted from your systems, and do not print, copy, distribute or read its contents.
<br>
<br>
AVIS DE CONFIDENTIALITÉ Le présent courriel, y compris tous les documents qu'il contient ou qui y sont joints, renferme des renseignements exclusifs et confidentiels destinés uniquement à l'usage interne du destinataire prévu. Si vous avez reçu le présent courriel
par erreur, veuillez nous aviser immédiatement, notamment par retour de courriel, et vous assurer qu'il est supprimé de façon permanente de vos systèmes; veuillez également vous abstenir d'imprimer, de copier, de distribuer ou de lire son contenu.
</font>
</body>
</html>