🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: adobe.framemaker
Article #26611

Re: TOC hyperlinks don't work in PDF

#26611
From: Zelly M.
Date: Thu, 23 May 2002 18:35
7 lines
1475 bytes
I thought I added another message to this thread saying thank you and how I solved or worked around my problem, but it's not appearing. 

So, again, thank you for the responses. Yes, the TOC was an automatically generated file. I deleted it from the book and also from Windows Explorer, and started anew. This time the TOC links work in both FM and PDF. 

For me, having all the individual files open in the book doesn't seem to matter as far as the TOC links working properly. Though, I have a hard time remembering to keep them open when generating files or updating the book (I am always opening and closing files in a book), I am going to try to remember to keep them open. 

Thanks again.
Technical Details
Message-ID: <ef8b4b7.6@WebX.aaQKaf7vad4>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!supernews.com!news.tele.dk!small.news.tele.dk!194.213.69.151!news.algonet.se!algonet!news000.worldonline.se!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!t-online.de!WebX
References: <ef8b4b7.-1@WebX.aaQKaf7vad4>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fd315,895e4f14cc88aad8
X-Google-Attributes: gidfd315,public
X-Google-ArrivalTime: 2002-05-23 11:37:52 PST
From: "Zelly M." <zooid@bitstream.net>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!supernews.com!news.tele.dk!small.news.tele.dk!194.213.69.151!news.algonet.se!algonet!news000.worldonline.se!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!t-online.de!WebX
Newsgroups: adobe.framemaker
Subject: Re: TOC hyperlinks don't work in PDF
Message-ID: <ef8b4b7.6@WebX.aaQKaf7vad4>
Date: Thu, 23 May 2002 11:35:41 -0700
References: <ef8b4b7.-1@WebX.aaQKaf7vad4>
Lines: 14
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit