Follow-up: Problem converting book to HTML

Combs, Richard richard.combs at Polycom.com
Wed Jun 30 15:37:14 PDT 2010


Karen Robbins wrote: 
 
> Problem may lie buried in the layouts/master pages. Tested with a
> 30-page file that was skipped during conversion. When all text from
> this file was copied to a new file that contained only default
> body/master/reference pages, and that file was added to the book, it
> converted correctly.
> 
> All files in the book share the same master and reference pages,
> paragraph styles, and character styles. All files begin with an
> "AHead" element. All other files (except the 600-pager) converted,
> including two that are larger than the 30-page file.
> 
> Any more thoughts on what in the template materials might be the culprit?

Well, the tried and true troubleshooting technique is to add back one removed element at a time until you find the one that breaks things. Or add a group (like ref pages), and if that breaks things, start removing members of the group one at a time until it works again. The idea is to pinpoint the source of the problem. 

But before you do that -- I don't recall if you've already tried a "MIF wash" -- save the problem file as MIF, open that in FM, and then resave as FM. That's kind of a general cure-all for file corruption or weirdness. 


Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
------
rgcombs AT gmailDOTcom
303-903-6372
------










More information about the framers mailing list