Understanding the Unresolved Cross-References Window in FrameMaker
- Understanding the Unresolved Cross-References Window
- About this Article
If you have never come across the Unresolved Cross-References window, consider yourself lucky. If you have, you know that trying to fix cross-references that have come undone for one reason or another is a challenge.
This article explores the "why"s and investigates the ways to solve unresolved cross-references that occur for the following reasons:
-
The name of the source file has changed.
-
The location (path) of the source file has changed.
This article does not discuss fixing unresolved cross-references that occur for these reasons:
-
A cross-reference marker was deleted from the source information.
-
The source information is part of conditional text that is hidden.
Using the Unresolved Cross-References Window
When you open a file with cross-references or update references some other way, and unresolved cross-references occur, you see the Update Unresolved Cross-References window. This window is not very intuitive, but it does serve a useful purpose: To show you which files contain source information that is no longer recognized by the current document's cross-references (for one reason or another). This window also points out how many total unresolved cross-references are contained in the current document, and how many of those are referenced in each of the individual source files.
You can resolve some unresolved cross-references right from this window. You cannot use this window to solve unresolved cross-references caused by deleted cross-reference markers.
TIP
If a file is closed and has unavailable fonts, open the file before you use the Update Unresolved Cross References window.
Here is an example in which unresolved cross-references in a file were caused in the following manner:
A directory called tech101 contained three files: techa.fm, techb.fm, and techc.fm.
The file techc.fm contained two cross-references: one to techb.fm and one to techa.fm. These cross-references worked fine.
The files were then saved and closed.
The name of techb.fm was changed to techbulb.fm.
The file techc.fm was moved outside the tech101 directory.
Here is how to use the Update Unresolved Cross-References window to fix the cross-reference problems that appear when techc.fm is reopened:
Open a file (techc.fm, in this example) that contains unresolved cross-references (or use Edit > Update References). The Update Unresolved Cross-References window appears, as shown in Figure 1. The top portion of the window provides information about how many total unresolved cross-references are located in the file just opened; in this case, there are two total. Current is selected in the Files Named list. Look below the list to see there are no unresolved cross-references in the Current file. That is, none of the unresolved cross-references has a source within the current file.
-
Click once on the second file in the list, techa.fm. There is one unresolved cross-reference to source file techa.fm, as displayed below the Files Named list (see A in Figure 2a)
-
Click once on the third file in the list, techb.fm. There is one unresolved cross-reference to source file techb.fm, as displayed below the Files Named list (see B in Figure 2b).
Figure 1 The Update Unresolved Cross-References window.
Figure 2 The unresolved cross-reference information, per file.
Now that you determined which files contain the unresolved cross-reference source information, it's time to solve each one:
Click on techa.fm in the Files Named list. This is the first file for which you will resolve cross-references. Why is the cross-reference to this file unresolved? Recall that both the current file (techc.fm) and techa.fm were in the tech101 directory when the cross-references were created. Now techc.fm has been moved outside the tech101 directory whereas techa.fm has not, so the cross-references in techc.fm can no longer find techa.fm.
-
Using the file display in the bottom part (For Cross-References to Selected File, Look In:) of the Update Unresolved Cross-References window, navigate to the correct directory, tech101, and click once on the correct file, techa.fm (see Figure 3).
-
After you finish, click on the Open button. As a result, the Current file will now find its cross-references to this source document using the new path.
-
Click on techb.fm in the Files Named list. This is the next file for which you will resolve cross-references. Recall that not only was the current file, techc.fm, moved outside the directory that contained the source file techb.fm; techb.fm itself was renamed to techbulb.fm. So the current file cannot find its cross-reference source.
-
Navigate to the correct directory, tech101, and click once on the new correct filename, techbulb.fm (see Figure 4). After you finish, click on the Open button. The Current file will now find its cross-references to this source document by using the new path and the new filename.
Figure 3 The cross-references to file techa.fm are resolved.
Figure 4 You can resolve the cross-references to file techb.fm by clicking on the correct filename.
Fixing unresolved cross-references for files that have changed locations, names, or both, is an easy task. After the previous steps for unresolved cross-references are completed, the Update Unresolved Cross-References window will look like the one shown in Figure 5. Notice that there are now no unresolved cross-references in the Current open file.
Figure 5 The result of resolving all the unresolved cross-references.