SOLVED: Cross Refs - why do they change type?

["Jo Watkiss" <JoWatkiss@xxxxxxxxxxx>]

Thank you Fred for the explanation of Paragraph Tags vs. CrossRef
Markers - my misunderstanding of this made me assume that something was
going very wrong.

In the event, Thomas had the solution - that some files in the book
couldn't open silently for various reasons.  Once I opened all files in
the book, Hey Presto all my unresolved Cross Refs disappeared.

Many thanks,
Jo Watkiss

-----Original Message-----
From: Thomas Michanek [mailto:thomas.michanek@xxxxxxxxx] 
Sent: 08 March 2004 15:12
To: Steve Rickaby; Ridder, Fred; Jo Watkiss
Cc: Free Framers
Subject: SPAM: Re: Cross Refs - why do they change type?

[ The original message appeared on the FrameUsers mailing list.
  This reply is sent only to the "Free Framers" mailing list.
  If this reply is useful, consider copying it to FrameUsers. ]

At 1:00 pm +0000 8/3/04, Jo Watkiss wrote:
> All cross refs are inserted using 'Paragraph Tags' as the source type.
> Every now and then I find that I have unresolved cross refs.  For some

> reason these are now looking for cross ref markers rather than the 
> Para Tags as originally inserted.

From: "Ridder, Fred" <fred.ridder@xxxxxxxxx>
> Paragraph Tags vs. Cross-Reference Markers is *not* a property of the 
> cross-references. It is strictly a display option in the Cross- 
> Reference dialog.
> In any event, unresolved cross-references have nothing whatever to do 
> with the display options in the Cross References dialog. The only 
> thing that causes FrameMaker to report an unresolved cross-reference 
> is when FrameMaker cannot find a marker with the appropriate ID number

> in the target file. Assuming that the correct target file is indeed 
> available, the two most common causes of unresolved cross- references 
> are unintentional deletion of the marker, or applying a text condition

> to a marker and then hiding that condition.

Just one more thing to note: FM may report unresolved cross-refs when
you open a file, but a subsequent search doesn't find any!
This is most often due to the problem that FM needs to (silently) open
the cross-ref'd file(s) to resolve (check) them. If a file that isn't
already open cannot be opened in the background without error messages
(such as unavailable fonts), the cross-ref will be reported as
unresolved. When the cross-ref'd file later is opened and any error
messages are confirmed, the previously unresolved cross-refs become
resolved (since the cross-ref destination now is available).
This typically happens if you Open All Files in Book.

This isn't Jo's original problem, but is worth noting. A special case of
the causes Fred mentions, is that copying and pasting text containing
cross-ref markers (such as headings) may lose the marker or replace it
with a similar marker that isn't "up to the job"
of the original marker.

I hope this came through as lucid as it is in my mind :-)

_____________________________________________
Thomas Michanek, FrameMaker/UNIX/MIF expert Technical Communicator,
Uppsala, Sweden mailto:Thomas.Michanek@xxxxxxxxx http://go.to/framers/
_____________________________________________

Join the "Free Framers" mailing list: send an email to
majordomo@xxxxxxxxx with "subscribe framers" in the body





** To unsubscribe, send a message to majordomo@xxxxxxxxx **
** with "unsubscribe framers" (no quotes) in the body.   **