Please help with my LoF

[sssuuusssaaannn]

Hi,

I posted the following problem as a continuation of a discussion in a different thread.  However, for some reason the callout next to the title in the topics list in green and says 'answered' so maybe I should just have asked the question in a fresh topic.  Here's the post, please help:

I am having similar problems with my List of Figures. . Upon generation, my LoF lists all the graphics in order with a page number afterwards but there is no leader and no figure title (e.g., 'Figure 1–1 before the name of the graphic). I realize there's no reason for the LoF to add the figure title as it's part of the style, but maybe there's a provision in the ref pages that allows for this.

I realize the solution is probably in the reference pages, as I was also having a problem with the ToC and was told to fix those pages, and this solved the problem. However, this was a simple fix that I was able to do myself. I've been looking at the ref pages for the List of Figures in the ref page I want to emulate, and I can't figure out how to change the ref pages in my current LoF. I even tried deleting the ref pages and replacing them with theref pages from the 'good' LoF, but when I regenerated, I got blank body pages.

Could someone please run me through the required changes? Perhaps a good hearted expert can let me send them attachments, if that will help?

Thank you so much!

PS I tried importing formats from a 'good' LoF in another book, no go, and I also tried to rename the file as suggested above, no go.

[peter minneapolis]

All generated files get their instructions from a reference page whose name corresponds to the kind of generated file. IIRC, for example "TOC" for a TOC, "LOF" for an LOF. [EDIT] Examine the reference page of the "good" example TOC you have to see how this information corresponds. [/EDIT] When you set up the generated file, you choose the source paragraph formats to extract; generating the file creates the reference page, on which are paragraphs whose formats have the same name as the specified source paragraphs, suffixed with TOC or LOF, etc., appended to the name. For example Heading1TOC, or FigureLOF. Unless things have changed in recent releases, you then need to refine the font, and other properties of the suffixed paragraph formats with the paragraph designer, to suit your needs; you also need to set one or more tab stops with or without leaders and alignments. You also need to insert actual tab characters before or after the appropriate building blocks in the example paragraphs on the reference page.

IMPORTANT NOTES ABOUT TABS IN GENERATED FILES:

* The generated results of setting up these reference page instructions won't appear on the generated file's body page until you generate or update from within the source file or book. The most confusing part of this process is how tabs work. While typing a tab into the example paragraph moves building blocks, the corresponding body page extracted text doesn't get the needed tab character until the file is regenerated. The body page tab characters are inserted when FM reads the reference page example paragraphs and creates the tab character in the body page output. That's why I describe the reference pages as containing "instructions."

* There's a pesky potential gotcha when you set the rightmost tab stop in the example suffixed paragraph formats on the reference page. The reference page text frame's width usually is a default, usually using the standard margins. If the body page text frame is narrower than the reference page text frame, a right-aligned tab stop will be to the right of the text frame's right border, so the tab won't recognize and obey it. It's a good practice to set the tab stops in generated paragraphs on the body page, to avoid the problem of a too-narrow text frame.

As to how to set up generated files, Search Google for terms like "FrameMaker creating modifying formatting generated files lists tutorial" without quotes.

HTH

Regards,

Peter

_______________________

Peter Gold

KnowHow ProServices

Message was edited by: peter at knowhowpro