Going nutso' with a "phantom" cross-reference

[hedley.fin...@myob.com]

Fred, Tammy:

> Checking for unresolved x-refs with all conditions showing
> establishes that all the x-refs are good, and you should then be
> able to document that the "bad" ones that are reported in the Book
> Errors windows when you publish any given conditionalized version
> are due only to hidden x-refs.

I would recommend adding an unresolved cross-references index to the end 
of your book.  This reliably reports cross-references that point to hidden 
or non-existent targets and does not consider cross-references that are 
themselves hidden by a condition.  Then you would not have to change your 
SQA (whatever that is -- I came in late).

Regards,
Hedley

--
Hedley Finger
Technical Communications Tools & Processes Specialist
MYOB Australia 
P.O. box 371   Blackburn VIC 3130   Australia
12 Wesley Court   Tally Ho Business Park   East Burwood VIC 3151 Australia

Tel. +61 3 9222 9992 x 7421,   Mob. (cell) +61 412 461 558

? MYOB Technology Pty Ltd 2006

RE: Going nutso' with a phantom cross-reference

[hedley . finger]

Fred, Tammy:

 Checking for unresolved x-refs with all conditions showing
 establishes that all the x-refs are good, and you should then be
 able to document that the bad ones that are reported in the Book
 Errors windows when you publish any given conditionalized version
 are due only to hidden x-refs.

I would recommend adding an unresolved cross-references index to the end 
of your book.  This reliably reports cross-references that point to hidden 
or non-existent targets and does not consider cross-references that are 
themselves hidden by a condition.  Then you would not have to change your 
SQA (whatever that is -- I came in late).

Regards,
Hedley

--
Hedley Finger
Technical Communications Tools  Processes Specialist
MYOB Australia http://myob.com/au
P.O. box 371   Blackburn VIC 3130   Australia
12 Wesley Court   Tally Ho Business Park   East Burwood VIC 3151 Australia
mailto:hedleyDOTfingerATmyobDOTcom
Tel. +61 3 9222 9992 x 7421,   Mob. (cell) +61 412 461 558

© MYOB Technology Pty Ltd 2006
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Going nutso' with a phantom cross-reference

[Tammy . VanBoening]

Framemaker 7.1, all patches, Windows XP.

I have a 12 file book that whenever generated gives the same single error 
message - unresolved cross-reference in a particular file in the book. 
When I click on the error message in the Book Error Log, however, I don't 
jump to the same location all of the time - sometimes it's page 1, 
sometimes page 10, etc. and sometimes, I get that unable to find the error 
in the file message. I have spent 4 hours trouble-shooting this guide to 
no avail! Since this is a container file for text insets and I use 
conditional text, I have done the following:

I have manually checked each and every crosss-reference in the container 
file itself with all conditions turned on and no unresolved x-refs are 
found.
I have manually checked each and every text inset in the container file 
with all conditions turned on and have found no unresolved x-refs.
I have generated a PDF of the file and checked each and every x-ref for 
the 'dead link' syndrome and all links work as expected.
I have used search and find on the container file with all conditions 
turned on and I get the message that no unresolved x-refs are found.
I have used search and find on the text inset book and have even opned the 
text insets themselves in the container file and used search and find and 
I get the message that no unresolved x-refs are found.
In frustration and desparation, I even searched for all x-ref markers in 
the file and found no errant markers.


At this point, I am stumped and at a complete loss. The only reason that I 
am being so anal about this is that SQA rules dictate that the final 
version of any document checked in must be error-free and right now, I 
can't say that because I keep getting this single blasted error message.

Any and all advice, thoughts, suggestions (virtual sledgehammers) are 
appreciated.

Thanks,

TVB

Tammy Van Boening
Senior Technical Writer
Jeppesen Sanderson, Inc.
303-328-4420
[EMAIL PROTECTED]
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

RE: Going nutso' with a phantom cross-reference

[Ridder, Fred]

If you conditionalize any cross-references, it is virtually inevitable 
that you will get unresolved errors when you do an update book
operation with some condition(s) set to be hidden, regardless of
the dictates of your company's SQA rules. 

When FrameMaker does a book update, it check's *all* cross-
references, even if they are hidden. The hitch is that if the target
(source) of the x-ref is also hidden, FrameMaker reports the link
as unresolved. The only way to avoid this is to never conditionalize
cross-references. If that's not possible, your SQA rules will just 
have to be modified to accept a list of exceptions for 
cross-references that are reported as unresolved for a particular
set of show/hide condition settings. Checking for unresolved
x-refs with all conditions showing establishes that all the x-refs
are good, and you should then be able to document that the 
bad ones that are reported in the Book Errors windows when 
you publish any given conditionalized version are due only to
hidden x-refs

My opinions only; I don't speak for Intel.
Fred Ridder (fred dot ridder at intel dot com)
Intel
Parsippany, NJ



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
Sent: Friday, July 14, 2006 10:35 AM
To: framers@frameusers.com
Cc: [EMAIL PROTECTED]
Subject: Going nutso' with a phantom cross-reference

Framemaker 7.1, all patches, Windows XP.

I have a 12 file book that whenever generated gives the same single
error 
message - unresolved cross-reference in a particular file in the book. 
When I click on the error message in the Book Error Log, however, I
don't 
jump to the same location all of the time - sometimes it's page 1, 
sometimes page 10, etc. and sometimes, I get that unable to find the
error 
in the file message. I have spent 4 hours trouble-shooting this guide to

no avail! Since this is a container file for text insets and I use 
conditional text, I have done the following:

I have manually checked each and every crosss-reference in the container

file itself with all conditions turned on and no unresolved x-refs are 
found.
I have manually checked each and every text inset in the container file 
with all conditions turned on and have found no unresolved x-refs.
I have generated a PDF of the file and checked each and every x-ref for 
the 'dead link' syndrome and all links work as expected.
I have used search and find on the container file with all conditions 
turned on and I get the message that no unresolved x-refs are found.
I have used search and find on the text inset book and have even opned
the 
text insets themselves in the container file and used search and find
and 
I get the message that no unresolved x-refs are found.
In frustration and desparation, I even searched for all x-ref markers in

the file and found no errant markers.


At this point, I am stumped and at a complete loss. The only reason that
I 
am being so anal about this is that SQA rules dictate that the final 
version of any document checked in must be error-free and right now, I 
can't say that because I keep getting this single blasted error message.

Any and all advice, thoughts, suggestions (virtual sledgehammers) are 
appreciated.

Thanks,

TVB

Tammy Van Boening
Senior Technical Writer
Jeppesen Sanderson, Inc.
303-328-4420
[EMAIL PROTECTED]
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit
http://lists.frameusers.com/mailman/options/framers/fred.ridder%40intel.
com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

RE: Going nutso' with a phantom cross-reference

[Tammy . VanBoening]

Thank you Fred.  Your very articulate statement at the end about 

If that's not possible, your SQA rules will just 
have to be modified to accept a list of exceptions for 
cross-references that are reported as unresolved for a particular
set of show/hide condition settings. Checking for unresolved
x-refs with all conditions showing establishes that all the x-refs
are good, and you should then be able to document that the 
bad ones that are reported in the Book Errors windows when 
you publish any given conditionalized version are due only to
hidden x-refs

is just what I need to put into writing for my SQA folks.  Solutions 
always come so fast on this list.

Thanks again,

TVB

Tammy Van Boening
Senior Technical Writer
Jeppesen Sanderson, Inc.
303-328-4420
[EMAIL PROTECTED]
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Going nutso' with a "phantom" cross-reference

[tammy.vanboen...@jeppesen.com]

Framemaker 7.1, all patches, Windows XP.

I have a 12 file book that whenever generated gives the same single error 
message - unresolved cross-reference in a particular file in the book. 
When I click on the error message in the Book Error Log, however, I don't 
"jump" to the same location all of the time - sometimes it's page 1, 
sometimes page 10, etc. and sometimes, I get that unable to find the error 
in the file message. I have spent 4 hours trouble-shooting this guide to 
no avail! Since this is a container file for text insets and I use 
conditional text, I have done the following:

I have manually checked each and every crosss-reference in the container 
file itself with all conditions turned on and no unresolved x-refs are 
found.
I have manually checked each and every text inset in the container file 
with all conditions turned on and have found no unresolved x-refs.
I have generated a PDF of the file and checked each and every x-ref for 
the 'dead link' syndrome and all links work as expected.
I have used search and find on the container file with all conditions 
turned on and I get the message that no unresolved x-refs are found.
I have used search and find on the text inset book and have even opned the 
text insets themselves in the container file and used search and find and 
I get the message that no unresolved x-refs are found.
In frustration and desparation, I even searched for all x-ref markers in 
the file and found no errant markers.


At this point, I am stumped and at a complete loss. The only reason that I 
am being so anal about this is that SQA rules dictate that the final 
version of any document checked in must be error-free and right now, I 
can't say that because I keep getting this single blasted error message.

Any and all advice, thoughts, suggestions (virtual sledgehammers) are 
appreciated.

Thanks,

TVB

Tammy Van Boening
Senior Technical Writer
Jeppesen Sanderson, Inc.
303-328-4420
tammy.vanboening at jeppesen.com

Going nutso' with a "phantom" cross-reference

[Ridder, Fred]

If you conditionalize any cross-references, it is virtually inevitable 
that you will get "unresolved" errors when you do an update book
operation with some condition(s) set to be hidden, regardless of
the dictates of your company's SQA rules. 

When FrameMaker does a book update, it check's *all* cross-
references, even if they are hidden. The hitch is that if the target
(source) of the x-ref is also hidden, FrameMaker reports the link
as unresolved. The only way to avoid this is to never conditionalize
cross-references. If that's not possible, your SQA rules will just 
have to be modified to accept a list of exceptions for 
cross-references that are reported as unresolved for a particular
set of show/hide condition settings. Checking for unresolved
x-refs with all conditions showing establishes that all the x-refs
are good, and you should then be able to document that the 
"bad" ones that are reported in the Book Errors windows when 
you publish any given conditionalized version are due only to
hidden x-refs

My opinions only; I don't speak for Intel.
Fred Ridder (fred dot ridder at intel dot com)
Intel
Parsippany, NJ



-Original Message-
From: framers-bounces+fred.ridder=intel@lists.frameusers.com
[mailto:framers-bounces+fred.ridder=intel.com at lists.frameusers.com] On
Behalf Of Tammy.VanBoening at jeppesen.com
Sent: Friday, July 14, 2006 10:35 AM
To: framers at frameusers.com
Cc: larry_prado at jeppesen.com
Subject: Going nutso' with a "phantom" cross-reference

Framemaker 7.1, all patches, Windows XP.

I have a 12 file book that whenever generated gives the same single
error 
message - unresolved cross-reference in a particular file in the book. 
When I click on the error message in the Book Error Log, however, I
don't 
"jump" to the same location all of the time - sometimes it's page 1, 
sometimes page 10, etc. and sometimes, I get that unable to find the
error 
in the file message. I have spent 4 hours trouble-shooting this guide to

no avail! Since this is a container file for text insets and I use 
conditional text, I have done the following:

I have manually checked each and every crosss-reference in the container

file itself with all conditions turned on and no unresolved x-refs are 
found.
I have manually checked each and every text inset in the container file 
with all conditions turned on and have found no unresolved x-refs.
I have generated a PDF of the file and checked each and every x-ref for 
the 'dead link' syndrome and all links work as expected.
I have used search and find on the container file with all conditions 
turned on and I get the message that no unresolved x-refs are found.
I have used search and find on the text inset book and have even opned
the 
text insets themselves in the container file and used search and find
and 
I get the message that no unresolved x-refs are found.
In frustration and desparation, I even searched for all x-ref markers in

the file and found no errant markers.


At this point, I am stumped and at a complete loss. The only reason that
I 
am being so anal about this is that SQA rules dictate that the final 
version of any document checked in must be error-free and right now, I 
can't say that because I keep getting this single blasted error message.

Any and all advice, thoughts, suggestions (virtual sledgehammers) are 
appreciated.

Thanks,

TVB

Tammy Van Boening
Senior Technical Writer
Jeppesen Sanderson, Inc.
303-328-4420
tammy.vanboening at jeppesen.com
___


You are currently subscribed to Framers as fred.ridder at intel.com.

Send list messages to framers at lists.frameusers.com.

To unsubscribe send a blank email to 
framers-unsubscribe at lists.frameusers.com
or visit
http://lists.frameusers.com/mailman/options/framers/fred.ridder%40intel.
com

Send administrative questions to lisa at frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

Going nutso' with a "phantom" cross-reference

[tammy.vanboen...@jeppesen.com]

Thank you Fred.  Your very articulate statement at the end about 

If that's not possible, your SQA rules will just 
have to be modified to accept a list of exceptions for 
cross-references that are reported as unresolved for a particular
set of show/hide condition settings. Checking for unresolved
x-refs with all conditions showing establishes that all the x-refs
are good, and you should then be able to document that the 
"bad" ones that are reported in the Book Errors windows when 
you publish any given conditionalized version are due only to
hidden x-refs

is just what I need to put into writing for my SQA folks.  Solutions 
always come so fast on this list.

Thanks again,

TVB

Tammy Van Boening
Senior Technical Writer
Jeppesen Sanderson, Inc.
303-328-4420
tammy.vanboening at jeppesen.com