<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello Kapil<br>
<br>
Although your workaround and fix will no doubt be highly appreciated
by unstructured users, they don't address the issue that we have
seen with FM 11 <i>structured </i>- that is, that printing a file
to the Adobe PDF printer (whether using Save As, Save as PDF, or
Print) takes 10 times as long as it used to. I am not exaggerating.
We have a 550-page structured book that we used to convert to PDF in
FM9 in about 10 minutes or less. Now with FM11 it takes 90 minutes
or more.<br>
<br>
I originally posted this issue on the Adobe forums - see
<a class="moz-txt-link-freetext" href="http://forums.adobe.com/message/4661181#4661181">http://forums.adobe.com/message/4661181#4661181</a>. But there was no
resolution. I guess if a FM developer says, "i have not seen that
happening a lot, except few cases ," that means have to live with
it?<br>
<br>
In the meantime, my recommendation to structured FM users is: If you
want to convert your docs to PDF, don't upgrade until Adobe do
something about these problems.<br>
<br>
Roger Shuttleworth<br>
London, Canada<br>
<br>
<div class="moz-cite-prefix">On 27/09/2012 1:18 AM, Kapil Verma
wrote:<br>
</div>
<blockquote
cite="mid:FF15B4B2822C6345ADAAE9A8041C39E2012119CFDC20@indiambx02.corp.adobe.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Cambria;
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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
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;}
/* List Definitions */
@list l0
{mso-list-id:137500987;
mso-list-type:hybrid;
mso-list-template-ids:-1934093524 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1159618136;
mso-list-template-ids:675076036;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal">Hello everyone,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am from Adobe and wanted to give you some
information about the “Print to .PS” issue that has been
reported in the forums recently. We have looked into this
issue and found the cause. Today, we wanted to share it with
you all along with a workaround solution in the interim.
Furthermore, <b>we are working on fixing this issue and
expect to come out with a fix soon</b>. <o:p></o:p></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>What causes the issue<o:p></o:p></b></p>
<p class="MsoNormal">This issue occurs when a user who is
running FrameMaker11 in <u>unstructured mode</u> and tries to
print a <u>book</u>, which was also created in the
unstructured mode. This issue is not present when printing a
Framemaker document, or when FrameMaker is running in
structured mode. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Workaround<o:p></o:p></b></p>
<p class="MsoNormal">The workaround is to switch to structured
mode (you can do so by going to Edit > Preferences >
General and use the Product Interface dropdown to select
“Structured FrameMaker”) and restart FrameMaker. This would be
a one-time action and afterwards, FrameMaker will launch in
Structured mode and you won’t face this issue. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This being said, we do however realize that
many of you are working in the unstructured mode and wouldn’t
like to see the additional structured menus and toolbars. To
address this, we are providing a set of workspace, menu and
toolbar files (attached with this message). With these files,
a new workspace will be created in your FrameMaker structured
mode and this workspace will only have the unstructured menus
and toolbars. So, you can continue to work in a familiar
environment with only the unstructured features that you are
used to seeing. Please download the attached files and follow
the steps below to copy these files in the relevant folders.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><u>Steps to create the new “Unstructured”
workspace when running in the Structured mode<o:p></o:p></u></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo3">Copy
Unstructured.fws in
%appdata%\Adobe\FrameMaker\11\WorkSpaces\Structured’ folder<o:p></o:p></li>
<li class="MsoNormal" style="mso-list:l0 level1 lfo3">Copy
menus-unstr.cfg in
%appdata%\Adobe\FrameMaker\11\WorkSpaces\Structured\menus’
folder<o:p></o:p></li>
<li class="MsoNormal" style="mso-list:l0 level1 lfo3">Copy
fmtoolbar-unstr.xml in
%appdata%\Adobe\FrameMaker\11\WorkSpaces\Structured\toolbars’
folder<o:p></o:p></li>
<li class="MsoNormal" style="mso-list:l0 level1 lfo3">Launch
FM in structured mode and switch to the ‘unstructured’
workspace.<o:p></o:p></li>
</ol>
<p class="MsoNormal"><i>* Note: this would not remove DITA and
S1000D menus. If you want to remove those menus as well,
please write to me separately and I will be happy to send
you those instructions.<o:p></o:p></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hope that this workaround works as a
solution in the short term, while we work hard on fixing this
issue for you. We hope to come out with a fix soon to this
problem.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-family:"Cambria","serif";mso-fareast-language:EN-IN">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Cambria","serif";mso-fareast-language:EN-IN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Cambria","serif";mso-fareast-language:EN-IN">Kapil
Verma<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Cambria","serif";color:#943634;mso-fareast-language:EN-IN">Sr.
Product Manager - FrameMaker | FrameMaker Publishing Server<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Cambria","serif";color:#943634;mso-fareast-language:EN-IN">O:
+91-120-2444711 x 34505<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Cambria","serif";color:#943634;mso-fareast-language:EN-IN"><o:p> </o:p></span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
href="http://blogs.adobe.com/techcomm/category/framemaker"><span
style="color:blue;mso-fareast-language:EN-IN">http://blogs.adobe.com/techcomm/category/framemaker</span></a><span
style="mso-fareast-language:EN-IN"><o:p></o:p></span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
href="http://twitter.com/#%21/KapilVermaAdobe"><span
style="color:blue;mso-fareast-language:EN-IN">http://twitter.com/KapilVermaAdobe</span></a><span
style="mso-fareast-language:EN-IN"><o:p></o:p></span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
href="http://www.adobe.com/products/framemaker/"><span
style="color:blue;mso-fareast-language:EN-IN">http://www.adobe.com/products/framemaker/</span></a><span
style="mso-fareast-language:EN-IN"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
You are currently subscribed to framers as <a class="moz-txt-link-abbreviated" href="mailto:shuttie27@gmail.com">shuttie27@gmail.com</a>.
Send list messages to <a class="moz-txt-link-abbreviated" href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a>.
To unsubscribe send a blank email to
<a class="moz-txt-link-abbreviated" href="mailto:framers-unsubscribe@lists.frameusers.com">framers-unsubscribe@lists.frameusers.com</a>
or visit <a class="moz-txt-link-freetext" href="http://lists.frameusers.com/mailman/options/framers/shuttie27%40gmail.com">http://lists.frameusers.com/mailman/options/framers/shuttie27%40gmail.com</a>
Send administrative questions to <a class="moz-txt-link-abbreviated" href="mailto:listadmin@frameusers.com">listadmin@frameusers.com</a>. Visit
<a class="moz-txt-link-freetext" href="http://www.frameusers.com/">http://www.frameusers.com/</a> for more resources and info.
</pre>
</blockquote>
<br>
</body>
</html>