Article View: adobe.framemaker
Article #1308Re: FDK create CrossReference
From: Russ Ward
Date: Wed, 17 Dec 2008 21:01
Date: Wed, 17 Dec 2008 21:01
16 lines
1332 bytes
1332 bytes
Hanzel, I'm not sure, but I don't think so. I believe that the text displayed by an xref is off limits... only FrameMaker itself can get in there through an update. I could be wrong. Since you know the ID and text of the target, you could do a workaround like this: - Programmtically open up some "dummy" or "scratchpad" file - Create an identical target in that file - In the same file, create an xref to that target - Update the dummy file - Copy the xref into your original document - Reset the file pointer on the newly-copied xref (FP_XRefFile) It's a bit more coding but it should work, if no one else suggests a better way. Russ
Technical Details
Message-ID:
<59b74ac9.0@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news.glorb.com!news2!newsfeed.sovam.com!goblin1!goblin.stu.neva.ru!eweka.nl!hq-usenetpeers.eweka.nl!news4us.nl!webcrossingReferences:
<59b74ac9.-1@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: fd315,3736651f31906d9 X-Google-Attributes: gidfd315,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: "Russ Ward" <russ@weststreetconsulting.com> Newsgroups: adobe.framemaker Subject: Re: FDK create CrossReference Message-ID: <59b74ac9.0@webcrossing.la2eafNXanI> Date: Wed, 17 Dec 2008 13:01:03 -0800 References: <59b74ac9.-1@webcrossing.la2eafNXanI> Lines: 20 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news.glorb.com!news2!newsfeed.sovam.com!goblin1!goblin.stu.neva.ru!eweka.nl!hq-usenetpeers.eweka.nl!news4us.nl!webcrossing