Re: Limit to number of GREP replacement text?

Article View: adobe.scripting.indesign

Article #80

Back to adobe.scripting.indesign Previous Next

#80

From: Shane_Stanley
Date: Fri, 27 Mar 2009 21:37

11 lines
1648 bytes

On 28/3/09 7:13 AM, "Dave Saunders" <member@adobeforums.com> wrote:

> I believe that GREP by definition cannot go beyond $9.

Not really -- quite a few implementations can handle up to 99
backreferences. In fact, these days I suspect more do than don't. But it's
hardly a great limitation in something like InDesign.

-- 
Shane Stanley <sstanley@myriad-com.com.au>
AppleScript Pro Sessions <http://scriptingmatters.com/aspro>

Technical Details

Message-ID: <C5F3925C.4FB76%sstanley@myriad-com.com.au>

Path: arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!newshub.sdsu.edu!webcrossing

References: <59b86e14.-1@webcrossing.la2eafNXanI>

Show Full Headers

Complete Article Headers

X-Google-Thread: f939a,8d5304158d58b65a
X-Google-Attributes: gidf939a,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
From: Shane_Stanley@adobeforums.com
Path: arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!newshub.sdsu.edu!webcrossing
Newsgroups: adobe.scripting.indesign
Subject: Re: Limit to number of GREP replacement text?
Message-ID: <C5F3925C.4FB76%sstanley@myriad-com.com.au>
Date: Fri, 27 Mar 2009 14:37:48 -0700
References: <59b86e14.-1@webcrossing.la2eafNXanI>
Lines: 14
Received: from outbound.icp-qv1-irony-out3.iinet.net.au [203.59.1.148] by adobeforums.com; Fri, 27 Mar 2009 14:38:25 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtMBAGPjzEl8qAC8/2dsb2JhbAAI0W6DdwY
X-IronPort-AV: E=Sophos;i="4.38,434,1233500400"; 
   d="scan'208";a="409068724"
Received: from unknown (HELO [192.168.1.7]) ([124.168.0.188])
  by outbound.icp-qv1-irony-out3.iinet.net.au with ESMTP; 28 Mar 2009 06:37:51 +0900
User-Agent: Microsoft-Entourage/12.15.0.081119
Thread-Topic: Limit to number of GREP replacement text?
Thread-Index: AcmvJEW1QymjrauCUEi6JzeCMe/ghA==
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit

Reply to Parent Message