List of Paragraphs not listing all selected tagged content

[bluegiraffe24]

I'm running FrameMaker 11.0.2.384. When I choose Add/List of Paragraphs and include all paragraphs tagged as "RD-RefDocs" the list generates, but it is not complete. I know there is content tagged as RD-RefDocs that doesn't show up in the list. About half of the tagged content shows up. I do have Create Hypertext Links checked when running the LOP.

Any idea how to fix this? Thanks!

[Jeff_Coatsworth]

Anything special about the content that’s tagged & not showing up? In a Text Inset? Show/hide settings applied?

[bluegiraffe24]

No, all of the content tagged as RD-RefDocs has been typed in manually; no text insets that I know of. None of it is conditional.

[Bob_Niland]

Any of it in Tables, or in Text Frames inside Anchored Frames?

[bluegiraffe24]

Yes, all of the content tagged RD-RefDocs is in the cells of tables. The table format is Format A.

[Arnis Gubins]

Was any of the content or tables imported from another application (e.g. Word) or was it all done in FM? You could try a MIF-wash in case there's anythig funky with those RD-RefDoc tags that aren't being listed in your LOP. Otherwise, it shouldn't matter if they are in a table or not, or have overrides, FM should be listing them in the LOP.

[Bob_Niland]

> ... shouldn't matter if they are in a table or not ...

True, but I've seen instances (on 7.1) where the Find tool is unable to find content in Tables or in Text Frames inside Anchored Frames. And it's intermittent, of course.

I rarely generate LOPs, but it struck me as possible that it's using the same gather algorithm as Find, and might be subject to any bugs therein.

[Arnis Gubins]

LOP works extracting paragraphs from tables inside of text frames inside of anchored frames in a flow. It also will extract paragraphs from a graphic frame containing a text frame not in any flow.

[bluegiraffe24]

No, all of the content was created directly in FrameMaker.

[bluegiraffe24]

When I look at the incomplete LOP that is generated, there are a bunch of 1s that show up in addition to the tagged content that it is pulling. Not sure what that means.

[Arnis Gubins]

Those might be emtpy tags. Use the hyperlink from the LOP (ctrl+alt + click) to jump to the paratag to check it out.

[bluegiraffe24]

Yes you are right, they are just empty tags.

[bluegiraffe24]

I've never done an MIF wash before. Could you tell me more about how to do that? Thanks!

[Arnis Gubins]

A MIF wash means that the file is saved in MIF format (this forces the internal database to be written out in a rigid ansi format and any cruft/garbage encountered gets tossed). The "cleaned" MIF file is then read back in and saved as a binary.

In FM11, there is a MIFWash utility for Book files. See the Book Utilities menu:

[bluegiraffe24]

OK. For some reason in FM11 I don't have that menu. If I go to File/Utilities it doesn't show up there either.

[Bob_Niland]

Are you looking in a component file menu or the Book menu?

[bluegiraffe24]

We figured it out. All of the RD-Ref Docs are getting picked up, but the LOP was only showing 1 page of them. If I would delete content at the end of the LOP page, new content would magically appear. We repeated this process to find all of the content. Any idea why FM would only show 1 page of the LOP with no option to look at the other pages?

[Arnis Gubins]

It sounds like the text frame in your LOP isn't set to autoconnect.

[bluegiraffe24]

When I go to Format/Customize Layout/Customize Text Frame, I get the following dialog box, so the autoconnect is already turned on.

[Arnis Gubins]

You might have to manually install it.

*     --------------------------------------------------------- 

* To Register your client with the FrameMaker product.

*     ---------------------------------------------------------

*     The FrameMaker product needs to know about your client to initialize it. To let the FrameMaker product know about this client, you must make some changes to the environment under which the client runs.

*     1.     Copy the attached dll to FrameMaker 10\fminit folder in the Program Files installation directory.

*     2.     Open maker.ini file in the FrameMaker 10 directory. Add the following lines to the [APIClients] section of the maker.ini file:

MIFwash=Standard, MIF Wash, fminit\BookComponentMIFWash.dll, all

The .dll is located at <drive>:\Program Files (x86)\Adobe\AdobeFrameMaker11\Samples\ScriptsAndUtilities\BookMIFWash\BookComponentMIFWash.dll