[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: "Framers List" <framers@xxxxxxxxxxxxxx>
Subject: Cross-ref inconsistencies in FM6 and PDF
From: "Michael Lewis" <mlewis@xxxxxxxxxxxxxx>
Date: Sun, 22 Sep 2002 15:56:35 +1000
Cc: <framers@xxxxxxxxx>, <Frame2Acrobat@xxxxxxxxxxx>
Importance: Normal
In-Reply-To: <LISTMANAGER-31989-16337-2002.09.20-15.20.48--mlewis#brandle.com.au@lists.FrameUsers.com>
Reply-To: <mlewis@xxxxxxxxxxxxxx>
Sender: owner-framers@xxxxxxxxx
Framers all, This is for info. I've just had an interesting experience that I haven't seen reported previously. (Apologies if I've missed it.) Client has a junior tech writer, fairly new to FM. She was given the task of restructuring an existing multi-file FM doc (essentially 1 file per chapter, plus front matter and ToC). This involved changing some headings, either in wording or in pgf tag (Heading 3 changing to Heading 2, etc). I was asked to investigate the fact that some crossref links in the generated PDF didn't work. Acrobat knew they were links (cursor changed to pointing finger, whole xref flashed when clicked) but they didn't go anywhere. It turned out that all such xrefs linked to a changed heading. It's not altogether surprising that, if you change the text at the source of a crossref, something might happen to the generated link. What I was really puzzled by was that the xrefs were fine in the FM files ("Go to source" worked), FM didn't complain when the book was updated, and the PDF generation process didn't raise any warnings or errors. We just finished up with non-functional links. Of course, creating fresh xrefs in FM and regenerating the PDF fixed the problem. Michael Lewis Brandle Pty Limited, Sydney, Australia http://www.brandle.com.au ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **