“It doesn't work for me” is a bit concise. What does(n't) it do that you would(n't)?

I'm not sure if it's mentioned in that thread but there are good reasons not to blindly apply your rule to any word at the end of a paragraph. What. if it's quite a long word, coincidentally?

Jesse, I think it would! But better put the ^ “Start of Paragraph” at the beginning, just to make sure it will only remove the right text.

(Sure, there is little chance that particular text may occur inside a sentence, but better make it double-safe!)

The copying-and-pasting bits are scriptable, but unfortunately the scripting interface doesn't allow access to your 'selected range of pages' in the Pages panel. (If this happens to get added in CS6, it'd be a welcome addition … I could think of a few useful things to do with it!)

Oh sure you can use Master pages (in fact, do you have reasons not to?), but I've had some fun writing this quick Javascript. It uses logical page numbers, unencumbered by stuff like roman numeral preambles and separe sections, so take care to enter the right ones.

(Edit: next time watch out for possible post enhancements..)

(Edit II: 3rd time lucky?)

InDesign really doesn't like objects that spill over to the adjacent page. Just this month, we fell into this trap when we removed two pages from an otherwise ready-for-press document, and when it was printed we noticed ID had put all of the pages-spanning on top of everything else. That needed reprinting … and it was a full colour job …

So now I always take care to cut off images at the binding page side. It's a bother, but better safe than (again) sorry.

But your outer glow problem is something else. In your case you could try this: draw an empty rectangle on top of the page (taking care to align it exactly on the binding edge); cut your glowing image; select the empty rectangle and use “Paste Into”. If I'm correct, this will neatly clip off the glowing border.

Here is a script that will relentlessly remove all except in the list “keepThese”. Your example script replaces it with another, this one does not (so you might want to make sure this is what you meant).

Note that it solely tests the name of each character style, not if and where it is inside any style group. If you have two styles named “test” in two different groups, both will remain.

It was easy – – surprisingly so! Kasyan's script did all the work, but he checks explicitly for a placed InDesign page. It took only a little check to find out under what name a placed Photoshop image is stored (see the commented-out “alert” line in my version below). It turned out to be a type of “Image” with a link type of “Photoshop” …

… (After about half an hour of head scratching..)

In fact it was so easy I decided to take it to the next level :) I added a little dialog that shows a selection of checkboxes, and you can turn each one on or off as you wish. The “layer names” list does not come from your placed images — although it is possible to read all of them, you'd get a load of extra names as well. You can adjust the list of names near the top of the function “Main”.

An oddity I ran into: it seems changing layer visibility invalidates the image and re-creates the link! That lead to the aforementioned bout of head-scratching, as suddenly “in the middle of the script”, it would report that the referenced image had disappeared! So I took a shortcut here: “refresh” the link on line 43, rather than re-using the loaded variable “placedFile”. Oh well, that's the sort of thing I do for fun.

So here is the script; it seems wrapping it up inside {pre} and {code} tags defeat WordPress post-beautifications (curly quotes, en-dashed) but if not, at least now you know what to look for.

There is no way a PageMaker script can work with InDesign.

Sorry, but that's the way it is. It's not just that the scripting language is different — PageMaker has its own unique built-in language, InDesign exports its scripting model to any programming language that supports importing external definitions — or that items have different names than in InDesign (“style” vs. “ParagraphStyle”, etc.). The entire document model, objects, commands, and properties is entirely different.

To “use” the same script in InDesign, it has to be rewritten from scratch — you cannot “change just the right bits” to make it work.

Umm, that is not a good fix.

What it does, in essence, is finding any of the individual characters inside the set. The entire part between the square brackets means “any single one of the characters inside” (the OR | does not work inside a [character set] as such, it merely adds the | character to the allowed ones). You can see it indeed doesn't work if you check your example

Afghanistan War 1919–1922, 169, 171

— all it does is it finds all digit strings that are preceded by a space — or by a comma, quote, colon, or pipe, as you can see if you insert a pipe anywhere inside a string of digits.

By the way, the reason your first try failed:

(?<=,” |, |: )d+

is because Lookbehind does not work with strings of different length, they all have to be of the same length. For the same reason you cannot use repeating codes (+, *, and ?) inside a Lookbehind — I guess it would make poor old InDesign work too hard, going over all possible combinations.

But you can work around this by making them two Lookbehinds:

((?<=,” )|(?<=, |: ))d+

The first one checks for “comma-quote-space”, the second one for “comma-space” or “colon-space”. They are grouped inside parentheses with an OR bar, so if one doesn't work, the other takes over.