Broken bookmark cross references in Printed Documentation

Hi,
I'am using RH 10 to generate a printed documentation output. What i notice is that the book marked cross references are broken in the Printed Documentation output. Other cross references are linking fine, but, the bookmarked cross references do not link to their destination.
I generated a chm file for the project and the bookmarked cross references appear fine there. Is there anything that could be tried to rectify this problem.
Please note that i'am using HTML files as the source files to convert to a Word output.
Thanks,
Rupesh

There's no easy way to do this. RH doesn't include any
sequence that will convert to a cross-reference in Word, and
inserting multiple cross-references in Word isn't as easy as
executing a find-and-replace command. The best workaround I've
found so far is this:
1. In your RH doc, include a reference that is easily
distinguished from other text. For example, "For information on
Project Beta, see page BETA."
2. Generate the Word document.
3. Find the first instance of "BETA."
4. Insert a cross-reference to the page number of the Beta
heading.
5. Toggle the field code.
6. Copy the field.
7. Find the next instance of your special text ("BETA" in
this example).
8. Paste the field reference.
9. Repeat this process until you're finished.
Unfortunately, the field code references change each time you
generate the document. Equally unfortunately, Word won't recognize
regular braces and text as a field code reference - you have to use
the Ctrl+F9 sequence to generate them manually. So you can't just
generate the document, insert the first cross-reference, and then
replace "BETA" with {PAGEREF _Ref### \h} across your entire
document - it won't work. Instead, you must visit each reference
and paste the field code sequence manually.
If someone else can improve on this process, I'm sure a lot
of people would be happy. If not, it's the easiest workaround I've
seen here, so you might find it useful.

Similar Messages

XML Bookmarks & Cross References Broken

Problem: Bookmarks and cross-references created in XML output
files generated using RoboHelp X5 do not work. Any suggestions?

Hi Lynnca,
The text of a cross-reference is a property of the FrameMaker xref object that is expected to be autogenerated, so it is not included in the markup. The XML version of an xref is similar to the internal FrameMaker model, where you insert an xref an the text is automatically created and controlled internally. An xref saves as an empty element with information about how to find the source and regenerate the text, but no indication of what text was originally displaying when you exported the markup.
Properly configured, the xref text will autogenerate when you reimport to Frame, so the empty element is OK there. If you are using the XML with some non-Frame post-process, that process will need to accommodate this convention for representing xref links.
Note that the refint tag is actually closed, as indicated by the trailing slash just before the final angle bracket. This is a shortcut for representing elements with no content.
Russ

Cross-references in printed doc

I am thinking about converting a FrameMaker book to RoboHelp,
where I can generate it as CHM or PDF. But I don't want to lose the
page numbers in cross references. RoboHelp seems to convert them to
hyperlinks, which are included in the resulting printed
documentation (DOC). But I would really like to include page number
references as well in the final PDF. Has anyone found a way to do
this?

There's no easy way to do this. RH doesn't include any
sequence that will convert to a cross-reference in Word, and
inserting multiple cross-references in Word isn't as easy as
executing a find-and-replace command. The best workaround I've
found so far is this:
1. In your RH doc, include a reference that is easily
distinguished from other text. For example, "For information on
Project Beta, see page BETA."
2. Generate the Word document.
3. Find the first instance of "BETA."
4. Insert a cross-reference to the page number of the Beta
heading.
5. Toggle the field code.
6. Copy the field.
7. Find the next instance of your special text ("BETA" in
this example).
8. Paste the field reference.
9. Repeat this process until you're finished.
Unfortunately, the field code references change each time you
generate the document. Equally unfortunately, Word won't recognize
regular braces and text as a field code reference - you have to use
the Ctrl+F9 sequence to generate them manually. So you can't just
generate the document, insert the first cross-reference, and then
replace "BETA" with {PAGEREF _Ref### \h} across your entire
document - it won't work. Instead, you must visit each reference
and paste the field code sequence manually.
If someone else can improve on this process, I'm sure a lot
of people would be happy. If not, it's the easiest workaround I've
seen here, so you might find it useful.

Please help! Broken internal cross references.

I'm creating a 20-page PDF from a PowerPoint file. In the source PowerPoint document, I've embedded internal cross references that DO initially carry over when the file is saved out as a PDF. However, whenever I rename the resulting PDF or move it to a new location, all of its internal cross references cease working. I can click on them, and they "flash" once, but they do not take me to a different page. I've been able to replicate the issue on other computers, both inside and outside my organization, and in both Mac and PC environments.
Is this something to do with relative vs. absolute links? Is the issue likely on Adobe's end? Or on PowerPoint's? Is there some setting I need to change somewhere?
Thanks in advance for any thoughts. I've spent hours trying to research and diagnose this problem, to no avail.
For what it's worth, here are some of the tech specs of my system:
- Acrobat v7.0
- PowerPoint 2007
- Windows XP
- To save the PowerPoint as a PDF, I'm selecting the Windows button from the upper-left corner, hovering over "Save as", selecting "PDF or XPS", selecting "PDF" as the file type, selecting my desktop (or other location) as the destination, and clicking "Publish".

Some observations.
Acrobat 7 — PowerPoint 2007
Office 2007 applications are not supported by Acrobat 7's PDFMaker
See: http://helpx.adobe.com/acrobat/kb/compatible-web-browsers-pdfmaker-applications.html
MS "Mac Office" — Acrobat 7
Acrobat 7 supported Office X and Office 2004 only.
Scroll to the bottom of the link above.
You'll see that, with contemporary releases of Mac Office and Acrobat there is no PDFMaker support.
From what you've posted it appears you do not have compatible software combinations on either the Windows or the Mac boxes.
Be well...

Conditional cross references (an easier way?)

Hi gurus,
Forgive me if this is an absurdly simple problem, but our team just isn't figuring out an elegant solution.
What we need is two types of crossreference formats - one for print, one for PDF/the web/any other hyperlinkable medium.
We would like the crossrefs to appear as follows:
Print:
[some arbitrary block of text] (see page xx)
PDF
[some arbitrary block of text]
As far as we can tell, FM's crossreferences always GENERATE text based on the building blocks, whereas FM's hyperlinks allow an arbitrary chunk of selected text to serve as the "active" text. The hyperlink behavior is what we want, in both cases. We're not interested in pulling the name of the target paragraph, or the page number, or anything else - we just want the text we typed to serve as the link, no matter the format.
The only solution we've been able to figure out is to actually create both a hyperlink AND a crossreference, and then conditionalize the crossreference (show in print, hide in PDF.) But this feels unnecesarily complicated.
Is there a cross-ref building block that stands for "just use the selected text?" Or even "don't do anything at all?" It seems both of these solutions would allow us to just build the links using crossreferences, rather than needing to build links via two different formats?
Any help would be greatly appreciated. Until then, we'll just be here, weeping quietly.
Thanks,
Dennis

ddsbleton wrote:
Hi gurus,
Forgive me if this is an absurdly simple problem, but our team just isn't figuring out an elegant solution.
What we need is two types of crossreference formats - one for print, one for PDF/the web/any other hyperlinkable medium.
We would like the crossrefs to appear as follows:
Print:
[some arbitrary block of text] (see page xx)
PDF
[some arbitrary block of text]
As far as we can tell, FM's crossreferences always GENERATE text based on the building blocks, whereas FM's hyperlinks allow an arbitrary chunk of selected text to serve as the "active" text. The hyperlink behavior is what we want, in both cases. We're not interested in pulling the name of the target paragraph, or the page number, or anything else - we just want the text we typed to serve as the link, no matter the format.
The only solution we've been able to figure out is to actually create both a hyperlink AND a crossreference, and then conditionalize the crossreference (show in print, hide in PDF.) But this feels unnecesarily complicated.
Is there a cross-ref building block that stands for "just use the selected text?" Or even "don't do anything at all?" It seems both of these solutions would allow us to just build the links using crossreferences, rather than needing to build links via two different formats?
Any help would be greatly appreciated. Until then, we'll just be here, weeping quietly.
Thank
Dennis
You have two purposes, so you need two kinds of references, and two distributable documents, one for each need. Because a FM cross-reference content can't be broken into pieces, say one piece that displays "some arbitrary block of text," and a piece that displays "(see page xx)," you need two cross-references. Create one cross-reference for print, and point it to the source paragraph; use it with a cross-reference format with the "<$paratext> " building block to capture the text portion of the source, add the text "(see page) " and the <$pagenum> building block. For Web, create another cross-reference to the same source paragraph with only the <$paratext> building block. Create conditions for both cross-references; a print condition, and a Web condition. In the text, apply the appropriate condition to the corresponding cross-reference. Show or hide the condition you need, and create a PDF for one purpose, then reverse the visible/hidden condition settings, and create another PDF for the other purpose.
Because the cross-references in text are different lengths, keep a sharp eye on text reflow in the different conditionalized documents. You can use File > Utilities > Compare Documents in FM, or Acrobat's document comparison features, to check the reflow, but also use your eyes in the real text to confirm what the comparison tools tell you.
Search Google, if necessary, for terms like "importing conditional text settings to framemaker books," without quotes, for more about managing applying conditions to multiple-file books.
HTH
Regards,
Peter Gold
KnowHow ProServices

Cross references in custom XML

Hello!
We have a custom XML schema and a structured application that allows us to edit our XML documents in FM. The schema contains a definition for a cross reference element and a definition for a target element.
=============================================================
Example:
A cross reference element (say, documentA.xml contains this element): <cref target="documentB.xml#sect123"/>.
A target element (say, documentB.xml contains this element): <section id="sect123"/>.
Also I have a book in FM that includes both documentA.xml and documentB.xml.
=============================================================
FM outputs error messages when I try to save documentA.xml.
So, I have few questions concerning this issue.
How should I describe the cref element in EDD?
A manual says, that the @target attribute must be of the IDREF type. Sounds good but the # char is restricted for IDREF values. How can I resolve this contradiction? If I write <cref target="sect123"/> (target id without filename) FM outputs error messages when I open documentA.xml in FM.
Thank you!

Dear Russ,
Thank you very much for the answer. I'm sorry for my replying you with a delay,
To make long story short, now it's OK: we can load a document with cross references to FM as well as we can save it form FM. Thank you once more.
I'd like to make some comments that might be useful for other readers of this forum.
As far as I understand the Structure Developers Guide mostly describes import/export transformations between an XML format and the FM format. But we never convert XML files to FM files and vice versa in our application. We open an XML file in FrameMaker, we edit the XML file in FrameMaker, and finally we save the XML file from FrameMaker. So, while reading the Guide I had a permanent doubt if import/export is the case I deal with.
After several probes and attempts we found out that the following format of cross reference is appropriate for our application:
<xref srcfile="fm-properties.xml#sys_psnt_part_number" format="CrossReference"/>
(We found this type of cross references on page 399 of the Guide).
The xref element must have an attribute of the IDREF type defined in a schema and in an EDD even while we don't use it. This attribute may actually be omitted in an XML file but we had to define it for xref.
The root element of a target XML document must have an attribute of the ID type even while we don't use it.

TOC and Cross reference bookmarks

Hi. I recently finished work on a book that had front matter containing a brief TOC and a detailed TOC. The book also contained individual TOCs at the beginning of each chapter.
I updated all numbering across the book files before generating the TOCs in the front matter, then generated the brief and detailed TOCs using my TOC Styles. However, I assigned cross references for the individual chapter TOCs. May not have been the best choice.
Because there was special styling for some of the front matter TOC entries that wasn't easily specified using just the TOC Styles, I cut and pasted groups of entries from the generated TOC on the pasteboard into a new frame on the page. I checked in Story Editor to ensure that the invisible markers for the TOC entries had been copied into the new frame.
When I exported the files to PDF, the TOC entries no longer pointed to the correct pages. They simply pointed to the first page of the PDF when clicked. Furthermore, no bookmarks showed up the TOC entries in the Bookmarks panel, even though I had "Create PDF Bookmarks" checked in my TOC Styles.
I have three questions, then:
--Is there any way to reclaim the behavior of the TOC bookmarks, and their display in the Bookmarks list of the PDF, if the entries are copied and pasted into a new frame in InDesign, without doing this manually in Acrobat Pro?
--Is there any way to get cross references to display as bookmarks in a PDF, assuming that I needed to make individual PDFs of each chapter, without doing this manually in Acrobat Pro?
--I'm betting that all files should be exported from InDesign as a single PDF in order for all TOC and cross reference links to work properly, without manual intervention in Acrobat Pro? If so, and manual intervention is required, is this accomplished by cataloging/indexing in Acrobat Pro?
I need to be able to pass this information along to a publisher who is now requiring all of their compositors to submit bookmarked PDFs with their printer files. I'm pretty sure I know the answer to this one, but I would like verification from the pros here. Thanks!

Hi. I recently finished work on a book that had front matter containing a brief TOC and a detailed TOC. The book also contained individual TOCs at the beginning of each chapter.
I updated all numbering across the book files before generating the TOCs in the front matter, then generated the brief and detailed TOCs using my TOC Styles. However, I assigned cross references for the individual chapter TOCs. May not have been the best choice.
Because there was special styling for some of the front matter TOC entries that wasn't easily specified using just the TOC Styles, I cut and pasted groups of entries from the generated TOC on the pasteboard into a new frame on the page. I checked in Story Editor to ensure that the invisible markers for the TOC entries had been copied into the new frame.
When I exported the files to PDF, the TOC entries no longer pointed to the correct pages. They simply pointed to the first page of the PDF when clicked. Furthermore, no bookmarks showed up the TOC entries in the Bookmarks panel, even though I had "Create PDF Bookmarks" checked in my TOC Styles.
I have three questions, then:
--Is there any way to reclaim the behavior of the TOC bookmarks, and their display in the Bookmarks list of the PDF, if the entries are copied and pasted into a new frame in InDesign, without doing this manually in Acrobat Pro?
--Is there any way to get cross references to display as bookmarks in a PDF, assuming that I needed to make individual PDFs of each chapter, without doing this manually in Acrobat Pro?
--I'm betting that all files should be exported from InDesign as a single PDF in order for all TOC and cross reference links to work properly, without manual intervention in Acrobat Pro? If so, and manual intervention is required, is this accomplished by cataloging/indexing in Acrobat Pro?
I need to be able to pass this information along to a publisher who is now requiring all of their compositors to submit bookmarked PDFs with their printer files. I'm pretty sure I know the answer to this one, but I would like verification from the pros here. Thanks!

How to find broken links or cross-references in a PDF file?

Hi,
Recently I have been trying to figure out if there is a way to find out any broken link(s) in a PDF file. I'm aware that in FrameMaker we can search for Unresolved Cross-references and fix them, but is there such feature in Acrobat?
Any suggestions on this would be highly appreciated.
Thanks.

There's nothing in Acrobat itself, but there are 3rd-party program plug-ins that do the job. I use 'Autobookmark' (http://www.evermap.com/autobookmark.asp) which does a very good job of finding and marking broken links and allows keyboard-entry editing without having to re-browse the link if you already know the correct path. It also facilitates a lot of other useful functions that Acrobat makes rather tedious (like changing the zoom setting on all links or bookmarks).

Report Generation Toolkit (Word) : How to use correctly bookmark and cross-reference without "Error! Reference source not found"

Hi,
I try to generate a report using a template. In my template I use some cross-reference to refer to one bookmark. For exemple in the first page I created a bookmark for my name and in the header I created a cross-reference refer to my name. The problems is when I run my VI the bookmark actualise perfectly but the cross-reference refer to the bookmark can't actualise with the same value and generates an error : "Error! Reference source not found".
Can somebody help me please!
Nki
Solved!
Go to Solution.
Attachments:
01.jpg ‏72 KB

Hi,
When i create the word template, the bookmaks and the cross-reference referred to the bookmark update correctely. The problem is when I try to change the bookmark using "report generation from template vi" the bookmark change but not the cross-reference and the error generated is "Error! Reference source not found".
I make coople reasherch and i think they have no solution for this because : "if the text in a heading referred to in a cross-reference is revised, the cross-reference to the heading may no longer work" (http://office.microsoft.com/en-us/word-help/troubleshoot-cross-references-HP005189368.aspx).
To "resolved" this problem I create an other bookmark in the template who have the same value white the principle bookmark.
I use Labview 2011 and Micosoft office 2010.

Cross-References Broken In RoboHelp 10 Output

We are using FrameMaker 11 to author our documentation. We have some cross-reference links that do not work when the FrameMaker book is imported into RoboHelp. Upon import, the href information is not included in the link in the HTML code. The text looks like a link, however. When the help is generated, the text is not a link. The following is an example of a non-functioning link:
see <a>Link</a>.</p>
Here is an example of a cross-reference that is functioning correctly:
<a href="#XREF_90399_Heading_Text">Link</a>
There are no errors in FrameMaker. The cross-reference is updating correctly in FrameMaker. In addition, when a PDF is made form the same book, the cross-reference works in the PDF.
Troubleshooting steps I have taken:
I have tried going to MIF and back for both the source and target documents.
I have recreated the cross-reference and marker.
I have tried linking to a heading cross-reference marker, as well as a manually create cross-reference marker.
I have renamed the file.
I have renamed the marker.
I have used different cross-reference formats.
I recreated the file by copying all the text to Notepad and pasting the text back into a fresh FrameMaker file.
None of the steps I have attempted have corrected the issue for the cross-reference I focused my troubleshooting on. I hope that someone can point me in the right direction to correct this issue.

I have been trying everything I can think of to move the files around to resolve the issue. 35 characters is very disappointing. Is this for the file and cross reference or the whole file path? I am not sure how you are going to be able to link from one Framemaker file to another, including a cross-reference name (especially when you can use heading for the cross-reference name) with a limitation like this. We also have a large library with many directories. We utilize single sourcing, so some files are in completely other directories from the file that is cross-referencing to it. From what you are telling me, it sounds like we no longer have the ability to use cross-references from one file to another in our library structure. Are you saying that all cross references basically need to be in the same file to allow cross references to work properly in RoboHelp? We moved from a WebWorks solution and we never had any issues with our links.
What I don't understand is the marker is in the destination file in the converted RoboHelp files, but the link is completely missing the <a href="#XREF_name ofmarker"> code in the cross-reference link. When I go in and manually link the cross-reference in RoboHelp, it works. This seems like a bug. I think having a 35 character limit on a filepath, filename, and cross-reference name is not going to work for anyone that has any sort of complex directory structure with multiple authors, sharing content and since it isn't a limitation of HTML, I don't see why this functions this way. Manually linking isn’t a reasonable option for us. We have a publishing system that publishes all of our output. We have hundreds of files that are generated automatically.

Printed document page number cross-references

Is it possible to export webhelp to Printed Document - MS
Word with page numbers taking the place of hyperlinks? Must the
page numbers be added after the printed document is created?
If so, can the InsertPagRefs macro insert page numbers across
a multifile document?
I anticipate exporting to printed documents consisting of
multiple files with pictures inserted by reference. I need
cross-reference page numbers that look like internal page
references.
If a master document is not recommended for a large manual,
how is a large manual to be handled? I intend not to use Word as a
base for single sourcing and to create RD fields and files for an
*input* document. I intend to use webhelp as the single source so I
can use RH 7 conditional text and mutiple TOCs to produce multiple
documents and document formats!

No but you can easily add them afterwards. There is a macro
on my site that does exactly that.
http://www.grainge.org/pages/authoring/word/word_macros.htm
Your refer to a "large manual". How big is "large"?

Printing cross reference colour highlights InDesign CC

I am using cross references in InDesign CC and a different colour for each. Is it possible to print these from InDesign?

I believe you already have the settings for PDF appearance set in the Cross references dialog.
If you do and are still not seeing the result in the PDF then you need to turn on the setting of Hyperlinks on.
Thanks
Javed

Cross Reference displays wrong Chapter

I have several FrameMaker files that will eventually be combined into one book. In some chapters there are references to outside chapters. At some point another person that was using these files had to switch the Chapter title; for example Chapter 7 became Chapter 6. Now when I open up, lets say Chapter 5, and I set up a cross reference to chapter 6 I got throug the following steps:
I make sure both files are open in FrameMaker, I put my cursor in the spot I want to make a hyperlink > Right click > Cross Reference
When the window Pops up I make the following selections:
Document: Chpater 6
Source Type: Paragraphs
Paragraph type: Heading1
Paragraphs: Page 7
I select the exact paragraph I want referenced
Format: CH XX, #
When I hit replace I am expecting the text on the screen to say something like "CH06, 3-1 Title" but instead it says "CH07, 3-1 Title"
The link goes to the location I want, it goes right to Chapter 6 but the visible text says Chapter 7 which is wrong. I assume this is happening because someone switched those two chapters.
Does anyone know how to edit what the text says or what I need to change in the switched chapters to make it work correctly. Something else I noticed is that the Document option in the cross reference is saying Chapter 6 with the old title, not the latest up to date title.

I think I may be having the same issue. I'm using Technical Communications version 3. I have a huge FM book composed of many books - over 3,000 pages if it were printed. I'm linking to the FM file in RoboHelp (RH). No broken xrefs in FM, but when I go to RH, there are odd xrefs or missing ones. I keep updating both FM and RH without any success. So, I generated a list of cross-reference markers in FM.
This is what I think is causing this. Even though you're supposed to be able to link to the FM file and if all is ok with the FM book (no errors, no broken xrefs), everything should chug along in RH. But, NO, it doesn't. When I put in cross-references in FM, I do them by the paragraph. But then you can also see the actual marker text, which doesn't always agree with the heading text. This is what RH uses. So, if you're having these issues, check the marker text to make sure it matches the paragraph text.
Below is an example where I had updated the heading, but the marker didn't match. FM didn't care and didn't report a broken cross-reference. RH just displayed the xref heading but it wasn't a link. Very frustrating. I'm looking for a way to get the xref markers to match the paragraph headings.
This is the heading: EContent in the PAC Patron Account
and this is the marker text: 28254:Heading 3: 3M eBooks in the PAC Patron Account - Items Out 768
BTW - I saw some snarky answers - just insecure people who want to show how much they know technically. For me, I just want the *******' tool to work! If I wanted to know all the sausage-making, I'd have been a programmer. I actually like to write and fiddling with RH is just tedious! In my experience, programmers are a dime a dozen; good writers are rare.
Make this a snark-free zone and help novices. Lord knows, Adobe's own documentation just doesn't get it. They tell you what something is but not how to do it! Oh, and the UX in RH is so cluttered and confusing! Do you use a pod or a menu item, what is important enough to get a pod? Why are there all these different ways to set up a project? It's like it was designed by hyped-up, overly-caffeinated people with really bad OCD. It's not about the tool, it's about the writers trying to get their jobs done!

Cross-references go to facing page when PDF'd

Is there a workaround for this? Mac, CS5.5. (I also have CS6 but still can't get the file to open!!)
I have a large book file, with facing pages. Cross-references throughout, exporting to PDF via PDF (Print) to get separate pages rather than spreads.
The resulting bookmarks are all correct, but the cross-references go to what would be the right hand page instead of the noted page. So, if the cross-reference is supposed to go to left page 84, it actually goes to right page 85. That works fine if the PDF is viewed in 2-up view, or exported as full spreads, but not in single page view.
Is there a solution? Or is it fixed in CS6?

Yes. There are five in one book. All the page links lead to pages in documents within the book.
The Contents page is in one InDesign document. It has links in it to pages within the other four InDesign documents.
Currently, clicking on the links in the exported PDF of the book takes you to page 1 - except for links to pages within the same InDesign document, and one link on the Contents page which leads to the correct page (that link is set up in the same way as the others).
EDIT: BTW - I will be leaving work in about 30 minutes, so I won't be able to try out any fixes until tomorrow, about 10am (London, UK).
UPDATE: When I checked the broken hyperlinks in Acrobat Professional, all of the page links that led to the cover were set to go to page 0. But in the InDesign document, they're all set to go to the correct page.
Message was edited by: richard_cosgrove

Cross-References coming from Word in FM 7.2

Hi Folks,
I have a problem with the Cross-References. I create an EDD and Read/Write rules, and generate a conversion table. With it I'm converting all the my documentation in MS Word to Structured FM 7,2. It works well, but there two main problems that I can't solve. I spent a lot of time reading the Structure application Developer Guide, but I can't find a solution.
First one is a minor problem that I can solve with a script but, maybe I'm doing something wrong on FM and it is easy to fix on the conversion table. When I apply the conversion table it generate without problems the RootElement, and apply tags for the paragraphs and Character formats, but I can't do that put other tags that are not related with text. I mean, my DTD need this structure:
<book>
<body>
<heading1>xxxxx</heading1>
</body>
</book>
and I obtain it:
<book>
<heading1>xxxxx</heading1>
</book>
I don't know if I can modify Rules, or EDD or Conversion table, to add the intermediate tag when use Structure Current Document
Second one is a blocking one. I generate the XML with the tags and fix any problem on it. It works great and I obtain a XML :
<book><heading1 Id = "i1003066"><bookmark
type = "38548: Heading 1: 1. This is the title"/>This is the title</heading1>
<paragraph>This is the text of the Title <reference Idref = "i1003066" type = "Page"/> and it bla bla bla</paragraph></book>
But when I try to re-open the XML with my structured application I obtain a log error:
"Error at line 17, char 31, Message: ID attribute 'i1003066' was referenced but never declared"
and a warning about cross-references missing (they working before save it as XML). File open and all is fine, except that references are missing and when I try to update the Reference dialog box to find other file is open with this message:
1 Unresolved Cross-References to File: Current
And ask me to find the "Current" file where point the reference. All the references in the document appears missing.
Must I have two set of files, one FM for generate the PDF, and the XML for generate the help with my XLS? It is not possible re-open the XML on Framemaker and don't lost the references?
Thanks for your help.
Regards,

Hi Van,
You wrote:
>> You need to DELETE "Xref" . . . This states that the reference element is a Frame cross-reference element; you should not include another name.
That may or may not be true. If the element names are different in the XML (DTD) than FrameMaker (EDD), this is the mechanism by which you translate names. It may be that in this case, the EDD element name is Xref, but the DTD element name is reference.
You also wrote:
>> Maybe this will help clear things up, but it may be unreasonable to expect that cross-references in Word will translate cleanly to structured FrameMaker.
In this case, I couldn't agree more. Esperanzas, I would recommend that you limit your faith in the conversion process, because there are many variables that will likely get mistranslated. Unless you are willling to do some programming with the FDK to clean up afterwards, I would expect that all cross-references should be recreated manually after import.
Russs

Broken bookmark cross references in Printed Documentation

Similar Messages

Maybe you are looking for