<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;}
/* 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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">I have the solution. Here’s the story:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Converting a whole book to HTML is very processor-intensive. When it consumes all resources, FM crashes.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Remember that FM copies the file-specific HTML settings from the first file in the book, and then adds new book-specific reference pages and HTML settings tables
to the first file. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">My problem was because FM crashed before creating and applying the proper book-specific settings to the first file. Thus it used the default settings, which
caused the rogue word See in my X-refs. It was also failing to convert my images and a few other issues.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I ran the conversion while watching task manager on my Win7 32-bit P4 machine, and watched processor load skyrocket up to 95% and then FM crash.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">When I repeated the process on a Win7 64-bit I7 machine, it ran to completion without ever breaking 20% processor load.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I then repeated it with a much larger file (595 images vs 76) and it sailed right through, again never exceeding 20% load.<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">So the moral of the story is don’t try to save a book as HTML unless you have the hardware to handle the job. If FM crashes, then your machine may not be up
to the task. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Sachin from Adobe Support will post the same info to the forums. I asked him to see if he could come up with some more precise guidelines so we would know what
sort of computer to ask for. The best he could do was to say a 64-bit machine makes a big difference, and he would try to get more precise information to share with us.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">john<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"><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"><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""> John Sgammato
<br>
<b>Sent:</b> Tuesday, June 05, 2012 7:19 AM<br>
<b>To:</b> 'Chris Despopoulos'; framers@lists.frameusers.com<br>
<b>Subject:</b> RE: FM10 crashes saving book as HTML, inserts rogue word<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chris was definitely onto something, and I learned a lot. Now I get good HTML output, but FM still crashes; that puzzle is in India now.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Here’s what I discovered:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">To save an entire book as HTML, you first set HTML mappings in one file in the book using File > Utilities> HTML Setup. The settings are stored in an HTML reference
page (actually a couple of pages) in that file. Then you copy the settings to other files in the book. Now every file has an HTML reference page with your new settings. These settings include whether to break the file at Heading 1, Heading 2, etc – I had to
uncheck those to get the monolithic file that I needed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">When FrameMaker converts the entire book to HTML, it reads the HTML mappings from the first chapter HTML reference pages, and then makes a new BookHTML reference
page that it puts into the first file in the book.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">None of my three books were generating the BookHTML ref page. As a result, FM was using some default values (I don’t know where they live), so the output was
wrong – hence the rogue word See inserted into X-Refs. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I added a new Reference page called BookHTML and copied the existing HTML mapping table onto that new ref page. The table was longer than the page, but I let
it overflow the frame rather than add a new page. I imported the ref page across all files, updated and saved the book, and tried again.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Now the book generates good HTML, but FM still crashes at the end.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The good output is enough for me to move on to the next phase of my overdue project, but the crash and the failure to autogenerate the reference pages are real
issues to be resolved. Those are in Adobe’s hands now. I will follow up as needed.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks for everyone’s help!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">john<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">ps In my researches, I also saw references to a BookHeadings table or page. I did nothing about that. I may follow up on it if I can.<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"><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:[mailto:framers-bounces@lists.frameusers.com]">[mailto:framers-bounces@lists.frameusers.com]</a>
<b>On Behalf Of </b>Chris Despopoulos<br>
<b>Sent:</b> Monday, June 04, 2012 4:41 AM<br>
<b>To:</b> <a href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a><br>
<b>Subject:</b> RE: FM10 crashes saving book as HTML, inserts rogue word<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Courier New";color:black">I can't say anything about the crash. But I can say that the inconsistencies when saving as HTML may have to do with your book-wide HTML setup.
The first document in the book should have two sets of HTML setup flows, one for the document and one for the book. Look at your ref pages in that first file -- you should see two versions of each HTML setup table. Make sure both are in sync. My guess is
they are not. <br>
<br>
About the crash, I would try making a special book using your files, but with only the first file in the book, then try that. See if it crashes. If it does, then zip it up and send it to the team in India. You would be doing us all a favor. If it doesn't
crash, add files one-by-one until you get the crash. Then delete files EXCEPT that culprit until it's the only one. Still crashes? You might have something odd in that file -- try mif-washing it. Othersies, zip it up and send it to India!<br>
<br>
Cheers cud<o:p></o:p></span></p>
</div>
</div>
</body>
</html>