InDesign 2019 (version 14.0.2) - GREP is broken

Is there a fix for Mac yet?

The file CopyPlugin.app is not present in the zipped folder you refer to.

The fix worked for me (macOS 10.13.6). Thank goodness I found this while doing early/preparatory testing. If my Big Script had failed 'on the day' I'd have been freaking out!

As an interim fix, could Adobe push a little warning that pops up if we attempt to use grep on a long document? I was tearing my hair out - grep was working fine on small samples, but not my main document.

I've already sent several books to press this year, confident that grep had found/replaced everything it should have

The fix working fine, follow the link : GREP search fails to find all the matching instances in long InDesign documents

Hi All,

Like i said, GREP is indeed broken in specific cases of long documents.

If possible, do vote for the issue and voice your concerns on the above Uservoice link.

Thanks,

Aman

I think Adobe spoiled something. After the last ID update, GREP can find only 44 of 366.

This is the pattern I am using: \s\(Uk\)

Hi,

Thanks for mentioning. We came to know of a known bug with 14.0.2 version of InDesign wherein the GREP fails to find matches.

Still can you:

1. Mail the sample at amaarora@adobe.com?

2. If you cannot share, then can you confirm if running the GREP query on text ranges of small size say (10K characters), helps InDesign find matches?

In other words, does GREP works for text with fewer characters say 10K?

I also recommend you report the issue at Adobe InDesign Feedback

-Aman

I am trying to do a simple GREP search "National Chung Cheng University$"  (and without the end of paragraph) and it will not find it going forward, but going backward it works.

It does find in the text search.

If this is to find any of these characters followed by a single space, you could make it a bit simpler (and just maybe it will work again! -- although there is nothing really "wrong" with yours).

1. Throw away the outer parentheses. You don't need them.

2. Don't combine […] with the OR bar | unless you literally want to find the bar as well! You don't need OR inside a custom single character class; [abc] matches one of these characters, and [a|b|c] will thus match "a","b", "c", or "|".

3. Try \b instead of \<. They do the same thing, but still. It might be "the" thing that got broken.

4. Try without the lookbehind. If even the basic

\b[aiouwzAIOUWZ]\s

does not work, then we have serious problems. If it does work, you can next try

\b[aiouwAIOW]\K\s

where the \K does what your lookbehind does: it "forgets" the match thus far made before continuing with the space character.