<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{mso-style-priority:99;
mso-style-link:"Body Text Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-name:"Normal \(Web\)\,ZimsEmail";
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BodyTextChar
{mso-style-name:"Body Text Char";
mso-style-priority:99;
mso-style-link:"Body Text";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.BodyTextChar1
{mso-style-name:"Body Text Char1";
mso-style-priority:99;
font-family:"Calibri","sans-serif";}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Courier New";
color:maroon;
font-weight:bold;
font-style:normal;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Courier New";
color:maroon;
font-weight:bold;
font-style:normal;}
span.BalloonTextChar1
{mso-style-name:"Balloon Text Char1";
mso-style-priority:99;
font-family:"Tahoma","sans-serif";}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We’ve had this problem in Frame 10 in docs that have tables with conditional text. The problem occurs when the all the text in the cell (including the end-of-flow
symbol) is conditionalized. FrameMaker can’t hide the end-of-flow symbol since that would technically leave an empty cell.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In our case, users didn’t understand the difference between conditionalizing all the text in a row and conditionalizing the row itself (preferred for our docs).
But if you need to conditionalize text in a cell, don’t conditionalize the end-of-flow symbol.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">After the crash, correcting the problem in FrameMaker doesn’t remove the corruption. The document requires a MIF wash to clear it up.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I hope this helps.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Pat<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>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><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""> framers-bounces@lists.frameusers.com [mailto:framers-bounces@lists.frameusers.com]
<b>On Behalf Of </b>Zimmerman, Gary<br>
<b>Sent:</b> Tuesday, July 01, 2014 3:21 PM<br>
<b>To:</b> rebecca officer; framers@lists.frameusers.com<br>
<b>Subject:</b> RE: Frame 12 conditional text bug<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon">The crashes I've mentioned happen in conditionalized documents - ours are structured, which may figure into this - and when
you change the conditional settings to or from showing all conditions, FM crashes. This has been in FM7, 9, and 10, which is as far as we've gone.<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon">Often the mif wash will fix the problem, but sometimes not. The issue seems to be odd conditioning that FM can't handle in
structured docs, as the kind of conditioning that, when you change the conditions you create an invalid structure that freaks FM out. Things like badly conditioned tables might do this, if you condition one cell structure element of the table accidentally.
We've also noticed it when someone, for example, deletes all text of a particular condition, as by deleting the condition, but there are invisible "remnants" of the condition left in the file. Things like accidentally conditioned (or accidentally not removed)
pilcrows.<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon">Sometimes if we carefully go through the file and find every instance of a condition with all the conditions and text symbols
turned on visible, we find something in the file we had missed before, and when we remove it manually, the file is "fixed".<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon">Hope this can help you and others.<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon">-- garyZ<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon"><o:p> </o:p></span></b></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><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""> rebecca officer [<a href="mailto:rebecca.officer@alliedtelesis.co.nz">mailto:rebecca.officer@alliedtelesis.co.nz</a>]
<br>
<b>Sent:</b> Tuesday, July 01, 2014 4:34 AM<br>
<b>To:</b> <a href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a>; Zimmerman, Gary<br>
<b>Subject:</b> RE: Frame 12 conditional text bug<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Hi Gary<br>
<br>
That's a good idea, thanks. We'll try it. Apart from anything else, it'll be really interesting to see if MIF files show the same bug.<br>
<br>
About those crashes you mentioned, are they on Frame 12? We're seeing a lot of crashes too, but we haven't figured out a pattern to them yet. We're not exactly fans of Frame 12 right now!<br>
<br>
Cheers<br>
Rebecca<br>
<br>
<br>
>>> "Zimmerman, Gary" 06/30/14 5:14 PM >>><br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon"> </span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon">Hi Rebecca,</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon"> </span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon">Have you tried working in .mif files instead of .fm files and only saving to .fm when you're done for the day?
</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon"> </span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon">When we have some conditional text problems that crash FM, a mif wash of the files often helps, and sometimes fixes the problem.
If yours is a bug, then the mif wash won't help, because as soon as you're back in .fm you'll hit the bug again. But maybe if you save the file as a mif, then work in the mif as much as you can, and only save as an .fm doc at the end, it would at least save
you some time during development.</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon"> </span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon">-- garyZ</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Courier New";color:maroon"> </span></b><o:p></o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><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"">
<a href="mailto:framers-bounces@lists.frameusers.com">framers-bounces@lists.frameusers.com</a> [<a href="mailto:framers-bounces@lists.frameusers.com">mailto:framers-bounces@lists.frameusers.com</a>]
<b>On Behalf Of </b>rebecca officer<br>
<b>Sent:</b> Sunday, June 29, 2014 9:58 PM<br>
<b>To:</b> <a href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a><br>
<b>Subject:</b> Frame 12 conditional text bug</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif"">Hi everyone</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif"">I've just posted this on Adobe's bug tracker as
<a href="https://bugbase.adobe.com/index.cfm?event=selectBug&CFGRIDKEY=3783041">https://bugbase.adobe.com/index.cfm?event=selectBug&CFGRIDKEY=3783041</a> but wanted to see if anyone else is seeing it too.
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif"">We have unstructured FM 12 files that use Expressions to choose what conditional text to display. We also use text insets, especially
as TOCs in chapters. When we update the text insets, conditional text displays that should be hidden according to the Expression. This means our documents suddenly display extra text!</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif"">Our text insets are set to update automatically when files open, so opening a file is often enough to trigger this bug.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif"">Fortunately, we found a workaround: The display becomes correct if we turn the Expression off and then on again. For example, if
we set the Show/Hide Conditional Text dialog to Show All and click Apply, then set it to show as per the desired Expression and click Apply, it'll display correctly. Until the next time we do something radical like opening the file.<br>
<br>
The workaround is a lot better than nothing, but it means we have to keep changing the Show/Hide Conditional Text dialog, across books of thousands of pages. It's slowing us down enough to drive us batty.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif"">Cheers</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif"">Rebecca</span><o:p></o:p></p>
</div>
<p><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif""><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.</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Segoe UI","sans-serif""> </span><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p></o:p></span></p>
</div>
<p><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><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.<o:p></o:p></span></p>
<p><span style="font-size:12.0pt;font-family:"Times New Roman","serif""> <o:p></o:p></span></p>
</div>
</div>
</body>
</html>