Cross-Reference creation

Hello to all!
I am new to this amazing world of Extendscript but I have been using Framemaker since version 5.5.
I am working on a kind of cross-reference manager and it works really nice. I can list all cross-references at book or document level, select the cross-reference to be shown in the current document and so on. I am using non-structured FM.
The problem I am facing is the creation of cross-reference itself.I know how to create a Cross-Ref Marker for the Xref, but I don´t know how to insert the Xref into the content. I tried with NewAnchoredFormattedObject function with objType, format and textLoc parameters. Also there´s the XRefSrcText property (string containg unique ID:pgf_tag:text).
The question is: Should I use the same string (the content of XRefSrcText) as text for the Cross-Ref type Marker? Or just the pgf text that contains the Cross-Ref?
I have found several examples using Framescript but I am unable to replicate the code using ES.
Thanks for reading me. I will appreciate any help on this.
Regards

Hi again Jang:
I have been trying to create the XREF following your suggestions:
First I created a XREF using the FM procedure. Then I created a code to get the info from Data Browser in the ESTK.
Then I created a XREF using my own code: FM recognizes the XREF (as you can see on the right image) but I cannot get any cross-ref on the content.
Here is the code for the Cross-ref marker target creation:
var doc = app.ActiveDoc;
var flow = doc.MainFlowInDoc;
var pgf = doc.TextSelection.beg.obj
var tLoc, marker, markerType;
tLoc = new TextLoc(pgf, 0);
marker = doc.NewAnchoredObject(Constants.FO_Marker, tLoc);
markerType = doc.GetNamedObject(Constants.FO_MarkerType, "Cross-Ref");
marker.MarkerTypeId = markerType;
marker.MarkerText = "10978: Heading1: PREAMBLE";
Here is the code I am using to create the XREF:
var doc = app.ActiveDoc;
var flow = doc.MainFlowInDoc;
var pgf = doc.TextSelection.beg.obj;
var oTLoc1=new TextLoc (pgf, 0);
var format="Page";
var newcrossref=doc.NewAnchoredFormattedXRef(format, oTLoc1);
newcrossref.XRefFmt.Name=format;
newcrossref.XRefSrcText= "10978: Heading1: PREAMBLE";
I have tried with tons of modifications but without success.
I hope you can help me!
Regards

Similar Messages

Error in cross reference creation urgent

Hi,
I am trying to create cross reference in SOA11g. I created xref tables(DEMO_CONTACT) first. when i try to populate data into that table using xref:populateXRefRow1M() function, it is showing following error:
XPath expression failed to execute. An error occurs while processing the XPath expression; the expression is xref:populateXRefRow1M("DEMO_CONTACT.xref","SBL8_ID","bpws:getVariableData('ContactVarTMP1')","SBL6_ID","bpws:getVariableData('ContactVarTMP2')","bpws:getVariableData('xrefAction')"). The XPath expression failed to execute; the reason was: internal xpath error. Check the detailed root cause described in the exception message text and verify that the XPath query is correct.
can anyone help me to solve this issue.
Thanks

Make sure the URL is accessible. Can you provide below information -
1. Which version of OSB and SOA are you working with?
2. Which type of service have you defined on OSB?
Regards,
Anuj

Cross-reference tag errors in Trados preventing MIF creation

Our Spanish translator provides files from translation memory with unresolved cross-reference text in English; when we update the book the cross-references are translated to Spanish and the page numbers are also updated within the cross-reference text. After our DTP process, when we return the files to the translator to update the translation memory, he gets a misalignment in the tags and Trados prevents him from creating a MIF file. Trados won't let him ignore the cross-references. We're using unstructured FrameMaker 2009 and he has Trados 2007. We're in the midst of a deadline for a project due next week and he wants to charge us an enormous fee to fix the tags manually. Can anyone suggest a solution the translator can use? I'm a newbie forum user, but I checked the FAQ and did not see anything. Thanks! Sue

As far as I know, FM cross-references (which came into Trados via MIF and S-Tagger) are handled as placeables. I suppose the mismatches stem from a "placeables differences penalty", which by default is 2%, even for otherwise exact matches.
A possible solution could be to impose no penalties for placeables in Trados, i.e. set the placeables differences penalty to 0%. But be careful, this may overshoot the mark, as there might be relevant differences in placeables that must be reviewed. I'm not aware of a setting in Trados where you could specify this more selectively.
Johannes

How can I get XML cross-references to translate to Structured FrameMaker?

I've been using Structured FrameMaker from the beginning, and have designed many EDDs, and about 10 years ago I did some translation of SGML into Structured FrameMaker (7.2) which worked well.
Now, (with FrameMaker 10), I've had to design an EDD to translate XML documents into Structured FrameMaker.
In my EDD I've a CrossReference element called XRef; this has an attribute of ID, which in turn has a value of IDReference and has Special AttributeConrols of ReadOnly.
My target elements in the EDD all have an ID attribute with a value of UniqueID.
My XML document's target xref element has an attribute of linkend, and in XML this works as I'd expect.
When I pass the XML file through the EDD/Template, everything works except that I get an ID = no value, which, of course, results in no display of the cross-reference data in the document.
Oddly, in structured FrameMaker, my element of link, with an attribute of linkend, works as it should, and displays the data. It may not be important, but the value for linkend is IDReference not UniqueID, and this displays correctly (I changed this attribute's value to Unique ID in my EDD and it made no difference to the XRef value in my document).
After making all these EDD changes, I've been careful to save the changes, import them to all files in my book and finally update the book.   Everything hangs together - except, of course, that the cross-reference doesn't work.
I'd sincerely appreciate any help or advice other users might have because I'm quite frankly stumped.

Russ,
Sorry about the delay in replying; got sidetracked trying to fix some FrameMaker 10 problems; on occasion, it laughs and crashes if we copy an element in a document and paste it to somewhere illegal. This doesn't happen all the time, but it might be something someone might do, so it was interesting to know.
Anyway, back to cross-references.
In our r/w rules we have:
"linkend" is fm attribute "ID";
Can we also have a similar line under the cross-reference element as:
element "xref"
     is fm cross-reference element "XRef";
     attribute "linkend" is fm property cross-reference id;
     attribute "role" is fm property cross-reference format;
At the moment the second line is:
.....attribute ID is fm property cross-reference id;
I tried adding the attribute "linkend" is fm property cross-reference id; (so that I had both linkend and ID) bit but this made no difference.
In general use cross-references work, in that it picks up data in one place in the document, e.g. WorldWideWeb, and repeats it elsewhere.   So in our xml file we have a link element with an attribute linkend which, when it's processed (ignoring the handshake code used to link the two - which could be something vague like 12345vvdog), repeats whatever is the target.
Conversely, for a cross-reference, in xml they use an xref element which also has a linkend attribute (similar mysterious secret handshake behind the scenes) which is deemed to point to a list of references.   This looks like it might be the stumbling block in that it links to an area in the xml document which is used as an internally generated list of references. Apparently this is only built when the xml book equivelent is finalised, so is not, like the link and linkend coupling described above.
I've passed this back to the xml people, and they are investigating a different way of preparing their cross-reference to a list of references (I'm now thoroughly confused with all these references - good thing the weekend's just around the corner).
I appreciate all you help and advice, I'll admit that this is a lot more difficult to understand than straight-forward EDD element creation along with their respective attributes.   Life used to be so much more simple back then!
In sum, what I thought I was doing was allowing an ID attribute with a value of IDReference in my elements, this was deemed to allow for FrameMaker cross-referencing.   In Structured FrameMaker, on its own, this works just fine; it all fell flat on its face when trying to import xml.   I tried to see whether the xref element's ID attribute could also be a UniqueID, but as just about everyone has said, this is a silly idea.   I was just trying stuff to see whether it might make a difference - you'll not be surprised to see that it didn't!
For the moment, I have attributes called ID with a value of IDReference, and I understand you're all suggesting to leave it at that.
If I understand correctly, I could eventually use an IDRef attribute if I wanted a UniqueID value to be used, though I'm not sure what a UniqueID is used or useful for, so will file that for future use.
Again, thanks for the advice and help.
Chris

How to fix crashing when PDF and procedure for cross reference?

I'm using Frame 8. When I try to PDF my book, Frame crashes. I have tried PDFing the individual chapters, but that didn't work.
Also, I'm trying to create either a cross reference or hyperlink. I have a paragraph that says "For more information, see the Setup section in Chapter 1" The Setup section in chapter 1 is a heading 4. I've tried using the instructions in the Frame help, but I don't understand them, and I don't know whether I need a hyperlink or a cross reference. Can I get simpler explanation and how-to?
Thanks!

Several things could be causing the crashing during the PDF creation process.
1. Have you applied the MS hotfix mentioned here?
http://blogs.adobe.com/techcomm/2009/07/repost_hotfix_for_framemaker.html
2. In your PDF Setup, make sure that you have Tagged PDF turned off and in the Links panel enable "Create Named Destinations for All Paragraphs".
Try it again and also make sure that you have applied all of the FM8 patches in sequence.
You can use either cross-references or hypertext links to create the jumps, though cross-refs are easier to do and maintain.
1. To insert a cross-ref to the Chapter 1 Setup section, you first would need to have Chapter 1 open along with the document that you are currently working on.
2. At the location where you want to insert the cross-reference, select the Special > Cross-Reference menu option.
3. For the first time that you use a cross-reference, you have create a format for it. In your case the "For more information, see the" and "section in" are constant strings and the section name "Setup" and "Chapter 1" are the variables.
    a) Click on the "Edit Format" button in the Reference section towards the bottom of the window. This will open a new dialogue window allowing you to create a format for use.
     b) In this window, give the format a name so that you can easily identify it, such as "More info in Chapter section".
     c) Then you have to enter in the "Defintion" line what you want the cross-ref to say, which could be (without quotes) "For more information, see the <$paratext> section in <$paranum[Chapter]>." The items in the angled brackets are building blocks used by FM to pick up content from the specified destination when you make the cross-ref. The first one <$paratext> specifies to grab the content of the paragragh that you point to (in this case it should be "Setup" section heading. The <$paranum[Chapter}> item will grab the autonumber value from the Chapter tag (or use whichever one that you have for chapter numbering at the start of each chapter).
     d) Once you're satisfied with your format, click on the Add and then Done buttons. This will save thgis format in the cross-ref catalog.
4. To actually insert the cross-ref, select the target document (e.g. Chapter 1) from the drop down list for "Dcoument:".
5. Then under the Source Type (the down arrow below the Document), make sure that you have Paragraphs selected.
6. In the left column you will see the paratags available in the Chapter 1 document.
7. Pick the paratag type that contains the Setup section title (heading 4 ?).
8. In the right-hand column you should then see all of the heading 4 tags in Chapter 1.
9. Select the Setup in this column.
10. Check that the Format line shows the one that you created earlier ("More Info in Chapter Section") and then click on the Insert button.
You're done.
If you don't like the formatting or it's picking up the wrong content, then open the cross-ref dialogue again and edit the format to get what you want.

Cross Reference Source text options

Creating a Cross Reference linking to a Paragraph. In the paragraph where the cross-reference source is inserted, may the cross-reference link be applied to existing text in that paragraph so that the cross-reference destination text does not appear? Text anchors can be created to accomplish this, but that is an extra step (I can create a cross reference linking to a paragraph all in one dialog box). Thanks in advance for any suggestions.

Hi, Seir:
I agree that it's confusing. Here's how I do it:
To create a text anchor at the insertion point location:
* Open the Hyperlinks/Cross-References panel's menu (also called "flyout menu." It's the small icon at the upper-right of the panel, below the double-arrow (>>) icon that collapses the panel.
* Choose New Hyperlink Destination. THIS SHOULD BE NAMED NEW TEXT ANCHOR!!!
* Choose Type: Text Anchor
* Name the anchor as you like Click OK.
To create a cross-reference to a text anchor:
* Place the insertion point where you want it.
* Click the Create new Cross-Reference button on the bottom of the Hyperlinks/Cross-Reference panel.
* Choose Link To: Text Anchor
* Choose the target document
* Choose the text anchor
* Choose the Cross-Reference format
* Choose Appearance properties
* Click OK
I'm not sure what could cause the straight/curly quotes problem other than perhaps the font doesn't have curly quotes. Have you tried other fonts?
HTH
Regards,
Peter Gold
KnowHow ProServices

Error while creating Cross-reference table using Xreftool (PIP Ins)

Error while running xref.sh script unable to create cross reference table.
**Error: Exception in thread "main" java.lang.NoClassDefFoundError: oracle/tip/xref/tool/AdminTool**
Could not find xref directory within tip folder (/OracleAS_1/bpel/docs/workflow/oracle/tip)
searched for similar issue in OTN it says issue fixed by upgrading Oracle AS, we are using 10.1.3.4 MLR#8
http://kr.forums.oracle.com/forums/thread.jspa?threadID=835446
steps followed.
Creating Cross-Reference Tables
Complete the following procedure to create cross-reference tables.
To create cross-reference tables
1 Navigate to the following directory:
%SOAHOME%/SiebelODOPPIP/scripts/
2 Open the following file for editing:
xref.sh
3 Set the userid and passwd for logging into BPEL console on the appropriate lines.
4 Set the correct SOA_HOME location on the appropriate line.
5 Save and close the file.
6 Make the file executeable:
chmod +x xref.sh
dos2unix xref.sh
7 Change directory (cd) to integration/esb/bin under %SOAHOME%.
8 Execute ../../../SiebelODOPPIP/scripts/xref.sh.
I am using SOA suite 10.1.3.3 and getting same error
Error: Exception in thread "main" java.lang.NoClassDefFoundError: oracle/tip/xref/tool/AdminTool

Hi Abhijeet,
please check in transaction FI01, about your data consistencies. You can use this wiki help in terms of Address, it it found any useful facts for you
Address Checks - Business Address Services (BC-SRV-ADR) - SAP Library

Display cross-references' linked documents filename in the xref panel

Our company creates technical manuals consisting of five chapters, all named the same, except with a different prefix. For example the "ABC Widget" manual has an introduction chapter named "ABC 1 - Introduction", a safety chapter named "ABC 2 - Safety", etc. Many times I re-use documents for creating subsequent manuals using the "Save As" command. So the "ABC 1 - Introduction" chapter would be saved as "EFG 1 - Introduction" for the "EFG Widget" book. For all the internal xrefs it saves a whole lot of time since all of the xrefs are preserved. But for cross-document references it creates a problem. For example, if the "ABC 1 - Introduction" chapter has a xref to "ABC 2 - Safety", when I save the Introduction chapter as "EFG 1 - Introduction" it will still retain the xref to "ABC 2 - Safety".
Right now, the only way to see if there are xrefs pointing to latent docs, is to check each one manually. If the xref panel displayed a column indicating the filename of the linked documents, I would be able to tell at a glance if that xref was pointing to the wrong document.
Thank you.
ID CS5, MAC

Hi Van,
I fear, I expressed myself not very clear. I try again.
We have DITA structured documents. However, lastest status often was saved in the FM document. The xml documents often are not representing the final status.
When I open the FM8 document in FM9 everything looks pretty good.
But: When I want to save the document as xml with FM9, I'm getting errors regarding the cross references.
The cross references which were created in FM8 - doesn't matter, if a valid xml document or a FM document - always look the same.
(BTW: I don't think that in structured documents cross references always refer to elemts with a unique ID.)
example from xml which was created with FM8:
<xref href = "#id08B4A0R30E9" type = "fm:Chapter">"..."</xref>
the only difference in the FM document is that the element is called fm-xref there, as it's not an external url.
in FM9 those cross references are totally different.
example from xml which was created in FM9:
<xref href = "#id08B4A0R30E9" class = "- topic/xref">"..."</xref>
When saving the FM documents with the cross references from the first example as xml in FM9 (we don't have FM8 anymore), I get an error that the attribute type is not defined.
When having a xml document that was last changed with FM8 and opening/ saving this with FM9, there is no error.
At the moment I do not know how to solve this issue.
And also I'm not sure weather the same problem might accour again with change from FM9 to FM10 or else.
It is a great effort to make new cross references just because we upgraded from FM8 to FM9. (And of course always at most inconvienent time.)
As we are thinking of upgrading to FM10, it would be good to know before, if there are any similar issues to expect.
Or if there is an fix for FM9 or FM10 to avoid this at all.
Regards,
Anna

Cross reference not working properly in epub exported from IDCC

Hi,
I'm not sure whether this is a known issue within ID so forgive me for bringing it up if it is. I couldn't find any satisfying answer on this forum, hence my question.
It seems that cross references between the xhtml-docs created from split ID document during the epub export don't work properly. They link to the text anchors specified as relative links. My editor uses software compliant to many e-reader platforms that removes all the relative links between the xhtml files within any epub and replaces them by absolute hyperlinks (http://). The result is... broken links all over. Their specification asks for the the anchor entires in the content.opf file instead of the relative links. Is there a way to work it out in InDesign and have the content.opf file contain the navigation to the anchors in xhtml files within the epub?
I'm working with IDCC 9.1 btw. Would appreciate any help...
Kind regards, Kasia

Hi,
   Not sure exactly where you gone wrong.
   If you want the running sum to start from beginning for each YEAR and each LINES. Use this
           =RunningSum([Sales revenue]; ([Year];[Lines]))   => Need Square brackets around Year and Lines. This forum site doesn't display square bracket correctly
   If you want the running sum to start from beginning only for each LINES (regardless of YEARS). Use this
            =RunningSum([Sales revenue]; ([Lines]))
   Not sure why you added ROW in your functions. Hope this help. Works for me, just tested using my efashion with the same structure are yours.
Regards,
Ken
Edited by: Ken Low on May 9, 2011 8:15 AM
Edited by: Ken Low on May 9, 2011 8:17 AM

Look up ESB Cross-Reference within ODI

We have a need to look up ESB cross reference table that is populated by AIA PIPs. I saw ESB Cross-Reference KM mentioned in "Oracle Data Integrator Knowledge Modules Reference Guides 10.1.3". My question is that can this KM be used to do ESB cross reference table look up. We don't need to populate xref table, just need to look up.

Hi Ace2-
Thanks for your quick response!
I can able to reterive unmatched records by using “Left outer join” but it will multiple the record counts for “matching condition”.
PRODUCT_ID,PRODUCT_NAME,SALES_QTY,SALES_AMT
101,SEGATE-HD,10,100
101,SEGATE-HD,10,100
102,TOSHIBA-HD,20,5000
103,TRANSCEND-PENDRIVE,10,2000
104,SONY ERICSSON,10,100000
105,NOKIA-7710,20,20000
106,TOSHIBA-HD,10,9000
107,NULL,NULL,NULL
The above records will be the output of outer join. If you see the 2nd record it is getting duplicated as 1st record. I have to exclude the 2nd record as it increases the record count of “PRODUCT_SALES.csv” file.
Thanks, Prabhu

InDesign Tagged Text for Cross-reference Entries

I'm transforming XML to InDesign Tagged Text. The XML has index codes. For regular page entry type entries I'm having no problem outputting to the appropriate InDesign Tagged Text markup. However, I cannot figure out how to code cross-reference type entries. The document "Using Adobe InDesign Tagged Text CS5 Tagged Text" is extremely limited in its usefulness as it does not list all possible values for tag type tags, etc. I've tried dozens of tag combos and guesses at values. None have worked. Also, for some reason, even though I can create a "See x" type reference in the InDesign document, when I export to InDesign Tagged Text to look at the code, those tags are not included in the export.
Does anyone have a more definitive list of possible IDTT index tag values?

I have been exporting various things to IDTT to see what the result would be, with nothing really helpful as a result. I'll try hyperlinks, but reading of the Adobe guide to InDesign Tagged Text and also just looking at the InDesign scripting object model leads me to believe that there must be specific tags to create index-specific cross-reference tags.

How do I preserve cross reference text when exporting to XML?

I am exporting my Framemaker documents to XML. However, when I open the raw XML, the reference formatting is obviously gone. So instead of seeing, say, see Figure 6. I now see, see .
Is there some way to preserve this on export?
Help would be much appreceated!

Josh,
The normal behavior is to have an empty element with the ID/IDRef markup that allows the xref element to be resolved again afterwards, by whatever post-processing step you put the XML through. The text of a cross-reference is a FrameMaker formatting artifact (not unlike a paragraph format, etc.) and is intentionally discarded during export. If you reimport the XML with the empty element, FM will re-resolve the xref, and then will restore the text using whatever format it originally had (the format name is also stored as markup).
If you want to preserve the element tag of the xref, I don't think there is any way to preserve the text, unless you write an import/export API client. You could possibly use an XSLT stylesheet to repopulate the text in some cases, but this seems like a process fraught with many complications.
If you do not care about the element tag, the manual says that you can just unwrap it, then you'll get the xref text. Here is a (rough) snip from the Structure Developers Guide:
Translating FrameMaker cross-reference elements to text in markup
You may not want your FrameMaker cross-reference elements to remain elements in the
markup representation—you can choose to translate them to text instead. To do so, use
this rule:
fm element "fmtag" unwrap;
where fmtag is the FrameMaker element tag for a cross-reference element.
All of this does beg the following question, though... why do you want to do this, especially if the text is referencing figure numbers, page numbers, etc. that have no relevance in the markup? Normally, it is expected that preservation of the markup is the essential thing, allowing the text to be regenerated later by whatever process uses the XML (perhaps including FM). If you drop the element tag, the actual link will be permanently lost.
Russ

Why is a single Cross Reference text turning red after doing an Update?

After updating a large book in FrameMaker10, the same cross-reference made in a couple of chapters is turning to red text. It is set as Heading 2. I tried to deleted the heading and re-typing it. I tried to change the style to Body and back to Heading 2 but all references to it are turning to red text after I update the book. Any idea what is wrong and how do I fix it? I am using unstructured version. See image.

Apply a Character Format of Default ¶ Font. Then re-apply the desired Paragraph Format. If the red goes away, it was either a Character Format that had been applied or a local color override. If the red is still there ...
Look at the Special > Cross-Reference > Format > Definition itself. Look for any <character-format-name> and see if any of those have a red Color defined in their Format > Character > Designer. If so, remove that building block from the definition [Change] [Done] [Replace].

Cross references not picking up character styles in source text

I'm getting some annoying odd behaviour with cross references in Frame 12.
I have some tables, where the paragraph style in the cell is called "Cell Body" (nothing odd there).
Quite a few of the cells only have one word in them, and that word is set to courier font with a character style (called "Code").
Then, elsewhere in the document, I am referring to this text using cross references. I am referencing the paragraph style Cell Body, and the cross reference format applied is like this "<hyperlink><$paratext><Default ¶ Font>"
"hyperlink" is another character style that makes the text go green.
So, the cross reference out to take the text from the cell (in Courier) and reproduce it, coloured green.
However for about half of these cross references, it isn't picking up the Code character style in the source text, so the cross ref is just green, no green courier.
Things are further bamboozled when I output to HTML Help.
In the CHM file, the cross refs which appear to work OK (green courier) are now just courier.
The ones which failed to pick up the courier look the same as they do in Frame (just green).
Any ideas as to what's going on?
I've tried troubleshooting by clearing the cells, reapplying the para style and default character style, then reapplying the code character style, then replacing the cross reference - which sometimes seemed to fix it but didn't always.

Arnis Gubins wrote:
Using two character tags in-line together (a la <hyperlink><Code>) is asking for trouble. IIRC, FM doesn't re-apply these in order on an update and depending upon how they are defined (and what is set to AsIs), the outer one usually wins. .
So why does the blimmin' dialog invite me to do precisely that, by providing me with a list of all the character styles I have, and allowing me to select as many of them as I like??? /sulks/ Indeed, if Frame still shipped with a printed user guide instead of stupid "optimised for viewing on iPhones" online webhelp nonsense, I suspect I might very well be able to find an example in the manual of using multiple character styles in that dialog! If it doesn't want you to use more than one, why doesn't it grey out after you add the first one? /sighs/ The concept is called "cascading styles", it's a fundamental web paradigm! And it works in the main body text - why not in Xrefs!
Also, I have been very scrupulous to keep my character styles orthogonal so none of their AsIs's mash each other up.
But, rant over, I shall follow your splendid suggestion for a "Code Hyperlink" style.
Arnis Gubins wrote:
Also, x-ref formatting may behave differently in the new Publishing modules depending upon ....
...Depending on how badly designed and buggy this new Frame12 feature is, I should say! The Publish module should not randomly stop behaving in a WYSIWIG manner in completely undocumented fashion just because Adobe couldn't be bothered to code it properly. /sighs/
Frankly, for my current project, I've given up trying to jump through hoops for Publish - I'm concentrating on getting the Frame source right and assuming these quirks will be fixed in Frame 13 (or 14, depending on how superstitious they are). Because if I put in ad hoc workarounds for them in Frame 12, I (or a colleague) will only have to undo them later when they're fixed, and by then we'll all have forgotten what the original problem was.

Cross-reference failure when converted to PDF

One of my clients uses FrameMaker 7.1 to author their product documents, and convert everything to PDF before releasing it. I often see problems where cross-references within the document work in FrameMaker, but do not work as links in PDF, even though they show as links and the cursor in Acrobat changes correctly as it should when pointing to a link. I have now encountered a FrameMaker file where the cross-references worked as links in the first revision of a PDF, but a random selection of them didn't in the next revision, even though no changes were made to any cross-references in the original FM file. It's not an issue with my PC or that of the person who generated the files - we have tried the conversion on multiple installations and they all produce the same result. To fix it we've had to locate each failed link in the PDF and put it right manually in the FM source file. Has anyone else encountered this? Any thoughts on the cause?

DxCooper (not your real name, I guess),
The rigid approach is to check in the PDF Setup dialog, last tab "Links", whether the option "Create Named Destinations for All Elements and Paragraphs" is selected. This helps but the size of the PDF may increase considerably.
Another thing which may help, especially (but not limited to) if the documents originally were authored in previous versions of FrameMaker, is the use of what is described in the prose of the above mentioned dialog: Optimize the PDF size by running the described routines once for every file. As far as I remember you can select a book file for that feature.
HTH,
- Michael (who feels better, if he can write to people with a name)

Cross-Reference creation

Similar Messages

Maybe you are looking for