A safer alternative is to "unlock" all of the text insets before creating 
the PDF. There is a TiLocked property of text insets that is not available 
in the FrameMaker interface. When you set this property to "False" it allows 
the text inset to act like native text. The beauty is that you can restore 
the text inset by resetting the TiLocked property to True.

Note that if you have cross-references from one text inset to another, this 
method won't work. Your link will appear in the PDF, but it will be looking 
for the source inset file instead of the container file.

I have FrameScript scripts to deal with cross-references in text insets, 
including those from one inset to another. If you are interested in a 
FrameScript solution, please contact me offlist.

Rick Quatro
Carmen Publishing Inc

> Gyanesh Talwar wrote:
>> I have a text inset with cross references in it (the destination of
> cross
>> refs also is in the same text inset.). When I generate a PDF, the
> cross
>> references do not work, the hypertext in the inset works though. After
>> converting the text inset into text and then writing the PDF, the
> cross
>> references start working in the PDF.
>> Am I supposed to convert the text inset to text or am I missing
> something
>> here? Is there another way to make the cross references work?
> Yep, that's the workaround for this particular bug:
> 1. Save all files in the book.
> 2. Convert all text insets to text.
> 3. Create PDF.
> 4. Close all files *without saving*.
> Step 4 is, of course, critical. If you have FrameScript, the whole
> process can be automated. If you have to do it manually, be careful and
> consider working on copies of your files.
> Richard
> Richard G. Combs
> Senior Technical Writer
> Polycom, Inc.
> richardDOTcombs AT polycomDOTcom
> 303-223-5111
> ------
> rgcombs AT gmailDOTcom
> 303-777-0436
> ------

Reply via email to