<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<STYLE>
<!--
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
@font-face
{font-family:Consolas}
@font-face
{font-family:Verdana}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-right:0in;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:#336666}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{margin-right:0in;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:#336666}
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:8.0pt;
font-family:"Tahoma","sans-serif";
color:#336666}
pre
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:#336666}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin-right:0in;
margin-left:0in;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:#336666}
span.HTMLPreformattedChar
{font-family:Consolas;
color:#336666}
span.BodyTextChar
{}
span.BalloonTextChar
{font-family:"Tahoma","sans-serif"}
span.BodyTextChar1
{font-family:"Calibri","sans-serif";
color:#336666}
span.EmailStyle24
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.EmailStyle25
{font-family:"Courier New";
color:maroon;
font-weight:bold;
font-style:normal}
span.BalloonTextChar1
{font-family:"Tahoma","sans-serif";
color:#336666}
span.EmailStyle28
{font-family:"Calibri","sans-serif";
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
{}
-->
</STYLE>
<META name=GENERATOR content="MSHTML 9.00.8112.16540"></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Segoe UI" lang=EN-CA bgColor=white vLink=purple link=blue>
<DIV>Hi everyone</DIV>
<DIV> </DIV>
<DIV>First off, thanks to everyone who pointed out the Control+6 keyboard shortcut. 13 years of FM and I didn't know that one. It certainly beats the copy special route.</DIV>
<DIV> </DIV>
<DIV>Second, Kapil Verma, the FM product manager, emailed me off-list to discuss the functionality, and let me know they'll be adding a button in the conditional text pod to make stuff unconditional. He also explained why the checkboxes behave like they do, and suggested an improvement. </DIV>
<DIV> </DIV>
<DIV>I'm very impressed at that level of response to my whinge - thanks, Adobe!</DIV>
<DIV> </DIV>
<DIV>I certainly find the pods an improvement on the old interface, so overall I'm happier with the new UI than the old. </DIV>
<DIV> </DIV>
<DIV>Cheers</DIV>
<DIV>Rebecca<BR><BR>>>> Keith Soltys <keith.soltys@tmx.com> 1/04/14 02:14 >>><BR></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">I’m with Scott on this one. </SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">I do have my gripes about some of the FM interface (I’m still using 10 but will upgrade to 12 as soon as WebWorks supports it), but in general, I’ve found the pods and tearaway catalogs useful. I use two monitors, one in portrait mode for my content, and one in landscape mode for all of the dialogs. Works well and keeps my working area clean. </SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Adobe is paying a lot of attention to its users. I’ve had direct contact with the Adobe development team based on comments made here and in the Adobe forums – they are listening. Bear in mind that FrameMaker is not the only product Adobe sells and some of the changes made were to make FrameMaker more consistent with their other products. You may consider this approach misguided but it’s corporate policy and almost certainly beyond the control of the Adobe team.</SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Regards</SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Keith</SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN> </P>
<DIV>
<DIV style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P style="MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 0.5in; MARGIN-RIGHT: 0in" class=MsoNormal><B><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: windowtext; FONT-SIZE: 10pt" lang=EN-US>From:</SPAN></B><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: windowtext; FONT-SIZE: 10pt" lang=EN-US> framers-bounces@lists.frameusers.com [mailto:framers-bounces@lists.frameusers.com] <B>On Behalf Of </B>Scott Prentice<BR><B>Sent:</B> Sunday, March 30, 2014 12:27 PM<BR><B>To:</B> framers@lists.frameusers.com<BR><B>Subject:</B> Re: making stuff unconditional in FM12</SPAN></P></DIV></DIV>
<P style="MARGIN-LEFT: 0.5in" class=MsoNormal> </P>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'">Aw .. c'mon .. that's a bit harsh, don't you think?</SPAN><BR><BR>I'm not a fan of the "new" (since FM9) UI either, but personally attacking the people behind the current product really isn't fair. The current team developing FrameMaker *is* very interested in customer feedback, and does listen. (And it's certainly not the programmers' faults .. they implement the features they are told to.)<BR><BR>The new UI is a significant change from the old standard, but can be tamed if you're willing to spend the time to learn how to make it do what you want. There are training videos and other info about setting up workspaces and other features, and with FM12, they have fixed most of the missing keyboard shortcuts (I believe). I totally agree that there are some frustrating aspects to it, but that's the new world of UI design. If you don't like it, stick with FM8. No one is forcing you to upgrade (although they do encourage it).<BR><BR>As for XML editors .. I think you'll find that XMetaL is considerably lacking when compared to FM. Especially if you're planning on generating PDFs .. you'll either need to take a step back on your formatting and layout, or you'll still need to use FM for PDF publishing. (But I am biased .. I'll admit that freely.)<BR><BR>Cheers,<BR><BR>...scott<BR><BR></P></DIV>
<P style="MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 0.5in; MARGIN-RIGHT: 0in" class=MsoNormal> </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>
<P><BR>NOTICE: This message contains privileged and confidential<BR>information
intended only for the use of the addressee<BR>named above. If you are not the
intended recipient of<BR>this message you are hereby notified that you must
not<BR>disseminate, copy or take any action in reliance on it.<BR>If you have
received this message in error please<BR>notify Allied Telesis Labs Ltd
immediately.<BR>Any views expressed in this message are those of
the<BR>individual sender, except where the sender has the<BR>authority to issue
and specifically states them to<BR>be the views of Allied Telesis Labs.</P>
<P> </P>
</BODY></HTML>