Is built-in Find/Change by list script Unicode compliant?

Question

I'm using the built-in find/change by list script for a scholarly text. It works fine, but some search and replace queries that involve some more unusual characters are turned into gibberish.

So I'm wondering if anybody knows whether the script is actually fully Unicode compliant, or if there is something that I'm doing wrong.

The query I've been using is below (the academic author uses a hacked pi font to get special ornaments instead of the correctly encoded unicode characters, hence the substitution):

grep {findWhat:"(?<=\\s)r(?=\\s)"} {changeTo:"ﷺ"} {includeFootnotes:true, includeMasterPages:true, includeHiddenLayers:true, wholeWord:false} Find r between any whitespaces and replace with ﷺ.

grep {findWhat:"(?<=\\s)u(?=\\s)"} {changeTo:"ﷷ"} {includeFootnotes:true, includeMasterPages:true, includeHiddenLayers:true, wholeWord:false} Find u between any whitespaces and replace with ﷷ.

But when I run it, the outcome in InDesign is Ô∑∑ instead of ﷷ and Ô∑∫ instead of ﷺ . Any clues?

tntype · Accepted Answer

Manan, Peter,thank you for taking the time to look at this.Peter, to your questions:it worked manually and when I did a manual search, copy-pasting the very same characters into the search dialogueI tried the Unicode values using the <XXXX> as I would in the search dialogue, which of course didn't work. I wasn't aware of the syntax that you've given me, thank you! Where else could I find this?Manan, seeing that it worked for you, I tried it to with a new, clean document. This did not work. But then I moved the two queries that I've shared here to the top of the query list, and all of a sudden it worked. I've double checked by putting it below again, and then I had the same garbled text again.This made me check the preceding GREP queries again, and I realised that I had not double escaped a number of queries, which in combination must have caused the replacements to go weird. I've checked and corrected everything and now it all works, no matter the order of queries.Thank you both again!

Peter Kahrel · Answer

InDesign is Unicode-compliant, the script should be, too. What you see is strange behaviour.

Do you get the correct result when you insert the character and apply the font manually?

What happens when you do the find/change manually?

If the above don't work, maybe use the character's Unicode value instead of the character literal. To get a character'sUnicode value, enter it in a text frame, select it, and open the Info panel. It's displayed as e.g. 0xFDFA. In the GREP replacement, use the format \x{FDFA}

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded