Snaps at Book Building. Renaming the 14 dir. doesn't help, neither mif roundtrip. Please help!
You all patched up? Does it happen to all books or just one in particular? Have you submitted the error log to the FM engineers?
1. I don't know. Installed in Sept.'17 -- where do I get the patches?
2. Only one, and not always.
3. No -- last time I submitted, the response was to not expect a response.
Go to the Help menu for info on your current version, and for a link to updates.
Please confirm via Help > About FrameMaker that you are using version 188.8.131.520
If not, please use Help > Updates to download and install that version.
If you're up to date with your Fm version, I suggest creating a new book, adding chapters and then building a new TOC/IX from scratch.
Other than that, you may be beyond what we can help with in a user forum, and you'll need to get in touch with Adobe Tech Support directly.
Thank you Jeff, Matt,
The patch installed, but that was not enough, neither the forum suggestions.
I still don’t know what was wrong prior to the patching. Afterwards, when I started debugging in earnest, pinpointed to some 4-layer index markers (unsupported in my templates but not snapping before). Indeed, the patch was supposed to fix some indexing bugs, so it might need another patch.
Are you saying that the 4th level index entries are causing the issue?
Yes, when I deleted the 4-tier index markers, I could successfully rebuild the book.
Let me clarify. In my template, the 4th level marker creates a glaringly bad entry with the font larger that the para default, thus overlapping neighboring lines. Could the overlap cause the snaps?
reformat the 4th level entry using the paragraph designer. Update all, and you should be ready to go.
If not, check the IX reference page and follow form with the other 3 levels of marker to produce the 4th level entry.
Are you saying I am no longer allowed to create overlapping lines?
It was intentional, to prevent 4-level entries.
My initial reaction was "Why in the world do you need a 4th level entry?!
I don't believe that the tight leading would cause the error, but perhaps you can go with red & bold and a smaller font to see if it cleans up the problem.