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>.
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.

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

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.

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).

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...

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 reference or hyperlinking not working for InDesign CS5 Book to ePub

I cannot get hyperlinks or cross reference links to work when generating an ePub from InDesign CS5. (7.0.0.355, Mac OS 10.6.2)
Here's how to recreate a simple test demonstrating the issue.
1. Create a new InDesign Book (File -> New -> Book)
2. Create document one (File -> New -> Document)
3. Create a text box and type "Table of Contents"
4. Create document two (File -> New -> Document)
5. Create a text box in it and type "Story One"
6. Create a new paragraph style and assign it to the Story One text
7. Save document 2. I just kept the name Untitled-2.xhtml
8. Back in document 1, add a cross-reference and select document 2, the style you created, and then "Story One". "Story One" should now appear under the previously typed Table of Contents text, and when highlighed, should show it is an active cross reference in the Hyperlinks panel.
9. Save document 1. I just kept the name Untitled-1.xhtml
10. Add both documents to the Book and save the book.
11. From the Book panel, select Export Book to EPUB...
12. Save the epub file and open it in Adobe Digital Editions.
Note that the text "Story One" appears as a hyperlink but when clicked does not switch to the document 2. It does nothing apparent when clicked.
Looking at the XHTML source for the first document, it is immediately evident why. The filename for document 2.thml is missing. It looks like this: <a href="#anchor-anchor">
When it should be : <a href="Untitled-2.xhtml#anchor-anchor">
The same thing works if you create a hyperlink instead of a cross reference.
I note then when I use the option to go to the destinate reference in the Cross Link (hyperlink) panel, it does switch to the second InDesign docuemtn. So the cross reference is functioning (in InDesign). But the link is broken in the ePub for the above mentioned reason.
Bug? Something I'm overlooking?
Entire source of Untitled-1.xhtml:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Untitled-1.xhtml</title>
<link href="template.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="untitled-1">
<div class="generated-style">
Table of Contents
<a href="#anchor-anchor">‚Äústory one‚Äù</a>
</div>
</div>
</body>
</html>

As far as I can tell, it has NOT yet been fixed in CS5.5. I'm having the same problem. I have about 90 hyperlinks to fix.
And the explanation that Teus Dejong gives indicates it's not going to be that helpful: "we have found that only the links in documents split by the CS5 exporter will be fixed. For books the script does only work for references to earlier documents in the book, not for forward references. This means in practice that for most books the script will not repair the links and should be seen as a means to add the year only. At the moment I see no way to repair this, because the book epub output of InDesign does not contain sufficient information to repair links referencing forward to others documents in a book."
It's pretty discouraging.

TCS2 - Cross References between linked Frame files not working

Hi,
All the cross-references in my linked in FrameMaker 9 files work when output in PDF, however, when outputting WebHelp from RoboHelp 8, FrameMaker cross references that reference another FrameMaker file (i.e. not Current) do not work. The format is correct, they appear blue and underlined like every other link/cross-reference, but when moused over in the browser, there's no link to click. The HTML created by RoboHelp does not point to a file. For example, here's the HTML for one link not working as shown from within RoboHelp:
   •   <a>Create Supported App from
Install</a>.
RoboHelp appears to partially convert the link as appears in the HTML but I think there should be more information in the <a> definition, such as in the HTML created for a link that references a topic created from the same FrameMaker file.
   •   <a
 href="#XREF_17096_Creating_an">Creating an App</a>
I've ensured all the cross-references in each framemaker file in the book have the same format and are mapped to <$paratext> in the project settings. I've also tried importing the FrameMaker book instead of linking it and the same problem persists.
Any ideas on how to make RoboHelp create the link correctly? Any help you can offer would be greatly appreciated.
Thank you,
Jacquie Finney

Most of the major cross reference issues have been resolved in TCS 2 with further improvements in TCS 3.
Please ensure that you have all the patches of TCS 2 installed on your system.
If the issue is still there, there could be an altogether different reason for cross reference not working or the issue might have been fixed in TCS 3.
The reason or workaround can be analysed once the sample files with the issues are provided.
It will be great if you could share a small sample FM document containing the cross reference and target having the issue. If the cross reference is across documents, then a FrameMaker book along with its FM files can be shared in a zip format.
You can mail the documents to me at magrawalATadobeDOTcom
Mayank

Word cross references not converting to hyperlinks

The cross references (i.e. {REF Welcome \h}) to bookmarks in
my Word document are not converting to hyperlinks in the HTML when
I have "Convert references into hyperlinks" checked when importing
the Word document (either in doc or docx format). This did work
with the older version Robohelp 5. Is there a setting I'm missing?
Thank you!
Pat

You said you've tried mapping styles.
I solved a similar situation. This involved a FrameMaker book imported by reference to RoboHelp. A cross reference to the paragraph style "Figure Title" was not getting converted.
I realized that in RoboHelp, I had mapped "Figure Title" to "None" or no output. (I do not want figure titles appearing in the online output, only in print).
Therefore, since the style was not mapped, the content was excluded and the cross reference did not get converted.
A different situation, but perhaps it can point you in the right direction.
Try changing the cross reference in FrameMaker to the next nearest heading, table title, or figure title. See if that makes a difference.
Make sure all the styles from each of your FrameMaker files is mapped to a RoboHelp style.

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.

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 stream

Hello!
I'm in real trouble, and I think that the answer is very close to me, but I can't get it by myself...
Here is my problem:
I'm currently improving the PDF parser that I've made, adding support for cross reference streams. After a careful reading of the ISO 32000 specification (with PDF 1.7 in background), I've wrote a piece of code that decode the stream and build the corresponding objects (I use Java).
But the decoded values are meaningless, and I don't understand why!
The data are like that:
filter predictor: 12
encoding : Flate
fields length : 1 2 1 (this is the W entry values)
column size : 4
I assume that there is one color per pixel formed by one byte.
First, I 'deflate' the data, then 'unfilter' them. Both operations look ok as I've made test for the Flate encoding (ok), and the for the filter I've use it with PDFBox source (and my work unfiltered well what PDFBox filtered...).
Note that I compared my outputs with those produced by PDFBox, and they are the same... Something may be wrong in the parameters I use, but I no idea now...
I think I missed out something as I read incorrect data as entry type 18...
I don't know where to go now, after a whole week of work!
If any have an idea, I'd be grateful to hear it!

This is ready algorithm to read PNG predictor styled Cross Reference Stream:
1. You need to read from PDF three variables: /Columns 5/Predictor 12 and /W[1 3 1] and of course stream
2. Deflate (encode) stream via zlib (without passing anything more than stream)
3. Divide encoded stream to rows, but length of each rows must be one bigger than columns variable (in this case is 6) because first value is type xref row
6. rows without first row go to UNprediction with this algorithm:
def self.do_png_post_prediction(data, bpp, bpr)
 result = ""
 uprow = thisrow = "\0" * bpr # just zero fill (byte zero - not char zero)
 ncols = data.size / bpr
 ncols.times do |col| # just for each rows
 line = data[col * bpr, bpr]
 predictor = 10 + line[0]
 for i in (bpp..bpr-1) # just for each values of row without first value
 up = uprow[i]
 left = thisrow[i-bpp]
 upleft = uprow[i-bpp]
 case predictor
 when PNG_NONE
 thisrow = line
 when PNG_SUB
 thisrow[i] = ((line[i] + left) & 0xFF).chr
 when PNG_UP
 thisrow[i] = ((line[i] + up) & 0xFF).chr
 when PNG_AVERAGE
 thisrow[i] = ((line[i] + ((left + up) / 2)) & 0xFF).chr
 when PNG_PAETH
 p = left + up - upleft
 pa, pb, pc = (p - left).abs, (p - up).abs, (p - upleft).abs
 thisrow[i] = ((line[i] +
 case [ pa, pb, pc ].min
 when pa then left
 when pb then up
 when pc then upleft
 end
 ) & 0xFF).chr # AND 0xFF is very important, without this values growing extremely fast
 else
 puts "Unknown PNG predictor : #{predictor}"
 thisrow = line
 end
 end
 result << thisrow[bpp..-1]
 uprow = thisrow
 end
 result
 end
 7. Take bytes from UNpredicted rows, and in this case
 1st byte first byte is type
 2nd byte
 3rd-5th - is this what You want - offset in decoded PDF to objects (Xref table): offset = 2^9*5th + 2^8*4th + 3rd

Cross Reference Sources appearing in Story Editor view but not appearing in the Cross Ref pane

I have imported a Word document containing working cross references into an InDesign document. The vast majority of these cross references import correctly and link to their destinations within the document, however there are some that are not working. If I view the text frame in the story editor view, I can see these "broken" cross reference sources that came in from the Word doc but on selecting them I can see that there isnt a corresponding entry for it in the cross reference pane. As said, there are only a few that are behaving like this.
What could be causing these not to appear in the cross reference pane?
Obviously as they are not appearing in the list of cross references I can't update them, and also, as they are technically broken cross references, because a source exists for them but there is no corresponding entry in the pane, then on export to epub, InDesign crashes (If there is one broken cross reference in a document, export to Epub will crash indesign).
Also, to clarify, in the Word doc if I navigate to a cross reference that is failing once in InDesign, I can update it properly, and also navigate to its destination in the Word doc, so it's not as though these cross references are broken before coming into InDesign. Also I believe the destinations for these "broken" cross references are coming across properly to indesign too as I can see them in the story editor view.
Supposed Cross Reference source selected in Story Editor view on left, but no corresponding cross reference highlighted in pane on right:
Technical Details:
InDesign CS5.5 - Version 7.5.3
Microsoft Word 2010, File type .docx

I have found the possible cause of this problem!
If a table is used within the Word document somewhere between where the cross reference source is and its destination then that particular cross reference will be broken as described above in my initial post.
So the "fix" is to remove any occurances of a table in the Word document and the cross references come into InDesign perfectly. This is actually not a fix at all. I need to use tables in the Word document for layout purposes so if they break cross references if they stand between them and their destinations then I have to compromise, i.e. use tables but with no cross references in the document or vice versa.
I found a similar issue recently with index markers in Word causing a shift on the cross reference tags when bought into InDesign. The "fix" again for that was to remove all index markers from the Word document. See post about this here: http://forums.adobe.com/thread/1043981
InDesign really needs to sort out the issues with importing of Word documents with cross references in them. If I can't use index markers and tables in a Word document without breaking its cross references then they can't claim to have the ability to import a Word document while maintaining its cross references into an InDesign document. It just doesnt work as ive painstakingly proven.

Cross-References Broken In RoboHelp 10 Output

Similar Messages

Maybe you are looking for