I've found the jumping-text-frame problem often is caused by a text frame or graphic being close to the edge of the page. That can include slug area text frames, page number text frames, page outline graphics, and background images or tints that touch the spine or page edge.

Here are some things that helped me at various times:

* Adjust all text frames so they are farther away from the page edges.

* Resize my (temporary) page outlines so they are a 1/2-point away from the outside page edge, or delete them.

* Change the top/bottom/left/right bleeds to zero—of course this doesn't help for final output, just for preliminary proofs.

* Set the pdf to “Use Document Bleeds Settings: On” rather than defining the bleed using the pdf output window's left/right/top/bottom options.

I had one book where I could output all pages with no problem, but if I select a range of pages like: “83, 86, 112-114, 256, 389,” the running feet were all over the place. Some were properly positioned, some were in the middle of the page, some were falling off the left or right side of the page, and some are so far off they were missing entirely.

I have CS6 now but haven't used it long enough to know whether this problem persists.

Thanks, Jeldrik. Good point about putting the cursor “after” the last word—I must not have had enough coffee the day I was working this out!

Interesting alternate process cutting-and-pasting the anchor. When you do this, the pasted text frame moves up and down the page, depending on the length of the text on the page, because it's position is relative to the anchor. Also, you have to add a text frame to blank pages so you have somewhere to anchor the page number frame. It is easier, though, to repeatedly paste the anchor than to repeatedly click and drag anchor handles.

I have an InDesign CS5.5 file (and IDML copy) set up for this, including some long-winded instructions. The styles, layers, and frames are created but the process has not been “run.”

If anyone to take a look, the DropBox link is:

https://dl.dropbox.com/u/481433…..Folder.zip

I have had a character unexpectedly deleted in an S&R when using the “FindChangebyList” script I've been using for years. Our editors hard code quotation marks to indicate which are opening (<”) and which are closing (“). In a recent book of 8 chapters, all the chapters S&R'd fine using that script except chapter 3. In the middle of chapter 3 that S&R began inserting an ornament instead of an opening quotation mark and deleting the first character of the following word. This is not an InDesign issue or an issue with the script—it must be a Word artifact that was accidentally replicated when the copyeditor did their own S&R to code the quotation marks in that chapter.

My current Word clean-up procedure is to open all the files in Word, save them as Word .htm files, and then resave them as Word .rtf files. Saving to .htm is what cleans up the random “stuff,” re-saving as .rtf is just my preference, I could probably re-save as .doc or .dox at that point but I haven't tested that. The trip through .htm seems to solve many mysterious formatting errors such as the S&R error above and the inexplicable proliferation of superscript from some point in a file all the way to the end.

If your original text came from a Word file, I would suggest that you save that file as Word .htm and then .rtf and then reimport it into InDesign (or at least the list portion) to see if the S&R error came from the underlying text.

Also,

(?<=d.)[a single space]+

will find a number followed by a period and space anywhere, not just at the beginning of a list so don't do a “Replace All” with it.

Does InDesign CS4 let you edit table cell text in the Story Editor window, or is that CS5? Try Edit/Edit in Story Editor (or the CS4 equivalent) to see if making text changes there is faster.

Be warned . . . I've seen InDesign's automated footnotes reflow without warning, which bumped text, which cascaded through the entire book, which screwed up the index. Be sure to check double-double check your final pages to make sure all footnotes are as they should be.

Rebecca