Alison Craig wrote:

> I received my translated book back from the LSP complete with TOC,
> seemed to be fine.
> After tweaking the formatting in 10 chapters and 7 Appendices, then
> in the correct Variables file I tried to Update the TOC (and all
> Cross-references, Text Insets and OLE links).

Umm... should you really be doing this? I'm no expert on handling
translations (that's someone else's job), so maybe I'm off base. But
when we get translated books back, we generally make no changes to the
translated files (oh, occasionally there's a doc number to correct or
something like that), we just PDF them as is. (For Hebrew, the vendor
even supplies the PDF, since they have to port the RTL languages to

> Instead of 6 pages of proper TOC it generated less than one page of
> seems to be page numbers only. I have consulted the Manual and
> FrameMaker book to no avail.

In the bad TOC file, select View > Reference Pages. Find the TOC
specification -- it's in a text frame with the flow name "TOC," and it
contains paragraphs that have tag names like the headings included in
the TOC, but with a "TOC" suffix (e.g., "Heading1TOC"). It sounds like
each of those pgfs contains only the page number variable (<$pagenum>). 

Now find the TOC spec in the ref pages of a good TOC and compare it to
the bad TOC spec. It may look more like this: 

        <$chapnum>      <$paratext>                      <$pagenum>
(there are tabs in there, including a leader tab in front of <$pagenum>)

If that's the situation, try this: Copy all the text in the good TOC
specification and replace all the text in the bad TOC specification with
it. Then update/regenerate. 

If I'm completely off base regarding the situation or that doesn't solve
the problem, try spending some quality time in the "Tables of Contents"
section of the help/manual. Even if you can't figure it out, a better
understanding of TOCs in FM might help you describe the situation in
more detail. 

Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
rgcombs AT gmailDOTcom

Reply via email to