RE: Flakey cross references
Hi, When you have activated Track Text Edits and cut text and paste it elsewhere in the same file, FrameMaker also does not paste the marker. The marker is still in its previous location, just with the condition FM8_TRACK_CHANGES_DELETED. When you later accept your changes, the cross-reference to that text will become unresolved. It would have pointed to the wrong location anyway. Best regards Winfried -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Combs, Richard Sent: Thursday, July 22, 2010 4:03 AM To: Combs, Richard; dr_go...@pobox.com; Dr Rick Smith Cc: framers@lists.frameusers.com Subject: RE: Flakey cross references My apologies to Steve if this came across as rude. I usually remember to review for snippiness before sending, but my microwave was beeping at me. :-) Nonetheless, I stand by my points. And I remembered another reason xrefs can unexpectedly break. If you cut and paste text containing an xref marker, FM retains the marker, so the xrefs to it will find the text's new location. But if you _copy_ and paste, FM is clever enough to eliminate the marker so that you don't have duplicate unique markers. So, if you're the belt-and-suspenders type who first copies and pastes, and then goes back and cuts the original -- oops, broken xrefs. Richard -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers- boun...@lists.frameusers.com] On Behalf Of Combs, Richard Sent: Wednesday, July 21, 2010 7:32 PM To: dr_go...@pobox.com; Dr Rick Smith Cc: framers@lists.frameusers.com Subject: RE: Flakey cross references Steve Johnson wrote: I've had it both ways but as a best practice you need to save the document you're referring to after you place the cross-reference. Every tag that is the target of a cross-reference gets a marker. For reasons unknown to me, sometimes these markers become stale and have to be deleted and reinserted. This might also cause your references to break. Do a search for All Markers or for Markers of Type cross-reference and check them out. Make sure the marker matches the tag with which it's associated. Sorry, but this is just bad advice. Cross-reference markers don't become stale. When you point a cross-reference to a paragraph, FM generates a unique string for the marker text. (If you point xrefs to markers you manually inserted -- which is necessary when creating xrefs to destinations in text insets -- it's up to you to ensure that the marker text is unique and identifiable by you.) This unique marker text string identifies the destination of the cross- reference so the cross-reference knows where to take you. The string looks something like this: 38790: Head1: Conference Templates The second element of the string is the name of the paragraph tag in which the marker is created. But it's just a unique string; using the pgf tag name is just a convention some FM programmers chose to use. If you change that paragraph to a Head2, the marker string isn't updated to 38790: Head2: Conference Templates -- it remains unchanged. It _has_ to, otherwise the cross-references to that marker won't be able to find it anymore and will be broken. If you delete and reinsert xref markers (unless you exactly re-create their marker text), or if you (m)ake sure the marker matches the tag, you'll _definitely_ break the cross-references to it. Some of the reasons cross-references break are: (1) The destination file isn't open, and FM can't open it in the background to resolve the xref (because, e.g., there are missing fonts). (2) The destination is in hidden conditional text (this is operator error; the xref should have the same condition applied and also be hidden). (3) Someone accidentally deleted the marker (most often happens when editing without View Text Symbols turned on). (4) Someone who doesn't understand markers thinks editing the marker text or re-creating them to overcome staleness is a good idea. Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-903-6372 -- ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Flakey cross references
Hi, When you have activated "Track Text Edits" and cut text and paste it elsewhere in the same file, FrameMaker also does not paste the marker. The marker is still in its previous location, just with the condition FM8_TRACK_CHANGES_DELETED. When you later accept your changes, the cross-reference to that text will become unresolved. It would have pointed to the wrong location anyway. Best regards Winfried > -Original Message- > From: framers-bounces at lists.frameusers.com > [mailto:framers-bounces at lists.frameusers.com] On Behalf Of > Combs, Richard > Sent: Thursday, July 22, 2010 4:03 AM > To: Combs, Richard; dr_gonzo at pobox.com; Dr Rick Smith > Cc: framers at lists.frameusers.com > Subject: RE: Flakey cross references > > My apologies to Steve if this came across as rude. I usually > remember to review for snippiness before sending, but my > microwave was beeping at me. :-) > > Nonetheless, I stand by my points. And I remembered another > reason xrefs can unexpectedly break. If you cut and paste > text containing an xref marker, FM retains the marker, so the > xrefs to it will find the text's new location. But if you > _copy_ and paste, FM is clever enough to eliminate the marker > so that you don't have duplicate "unique" markers. So, if > you're the belt-and-suspenders type who first copies and > pastes, and then goes back and cuts the original -- oops, > broken xrefs. > > Richard > > > -Original Message- > > From: framers-bounces at lists.frameusers.com [mailto:framers- > > bounces at lists.frameusers.com] On Behalf Of Combs, Richard > > Sent: Wednesday, July 21, 2010 7:32 PM > > To: dr_gonzo at pobox.com; Dr Rick Smith > > Cc: framers at lists.frameusers.com > > Subject: RE: Flakey cross references > > > > Steve Johnson wrote: > > > > > I've had it both ways but as a best practice you need to save the > > > document you're referring to after you place the cross-reference. > > > > > > Every tag that is the target of a cross-reference gets a > marker. For > > > reasons unknown to me, sometimes these markers become > stale and have > > > to be deleted and reinserted. This might also cause your > references to > > > break. > > > > > > Do a search for All Markers or for Markers of Type > cross-reference and > > > check them out. Make sure the marker matches the tag with > which it's > > > associated. > > > > Sorry, but this is just bad advice. Cross-reference markers > don't become > > "stale." > > > > When you point a cross-reference to a paragraph, FM > generates a unique > > string for the marker text. (If you point xrefs to markers > you manually > > inserted -- which is necessary when creating xrefs to > destinations in text > > insets -- it's up to you to ensure that the marker text is > unique and > > identifiable by you.) > > > > This unique marker text string identifies the destination > of the cross- > > reference so the cross-reference "knows" where to take you. > The string > > looks something like this: > > > > 38790: Head1: Conference Templates > > > > The second element of the string is the name of the > paragraph tag in which > > the marker is created. But it's just a unique string; using > the pgf tag > > name is just a convention some FM programmers chose to use. > If you change > > that paragraph to a Head2, the marker string isn't updated > to "38790: > > Head2: Conference Templates" -- it remains unchanged. It _has_ to, > > otherwise the cross-references to that marker won't be able > to find it > > anymore and will be broken. > > > > If you delete and reinsert xref markers (unless you exactly > re-create their > > marker text), or if you "(m)ake sure the marker matches the > tag," you'll > > _definitely_ break the cross-references to it. > > > > Some of the reasons cross-references break are: > > > > (1) The destination file isn't open, and FM can't open it > in the background > > to resolve the xref (because, e.g., there are missing fonts). > > > > (2) The destination is in hidden conditional text (this is > operator error; > > the xref should have the same condition applied and also be hidden). > > > > (3) Someone accidentally deleted the marker (most often happens when > > editing without View > Text Symbols turned on). > > > > (4) Someone who doesn't understand markers thinks editing > the marker text > > or re-creating them to overcome "staleness" is a good idea. > > > > > > Richard G. Combs > > Senior Technical Writer > > Polycom, Inc. > > richardDOTcombs AT polycomDOTcom > > 303-223-5111 > > -- > > rgcombs AT gmailDOTcom > > 303-903-6372 > > --
Re: Flakey cross references
Keep in mind that there are two parts to every cross reference: the text that refers, and the text referred to. You need both files open to create a cross reference and you must save BOTH files to preserve the cross reference. As far a I know, you can't create a cross reference to a read-only file. But honestly, I've never seriously tried. On Jul 20, 2010, at 1:00 PM, framers-requ...@lists.frameusers.com wrote: From: Layton, Debbie debbie.lay...@xerox.com To: framers@lists.frameusers.com Subject: Flakey cross references Message-ID: 78ef4e337f3131469c3bb1f11a42d8970d83b...@usa7061ms04.na.xerox.net Content-Type: text/plain;charset=us-ascii I'm using FrameMaker 7.0 on XP Professional. I've got a book with about 11 chapters in it. I continue to get unresolved cross reference messages. I have gone in and re-done all of them, since the original files were copied from another manual, but when I open the documents again, I get the messages again. None of the files have been moved. I have been printing .ps files in order to create PDFs of the book. (Somehow that seems to have something to do with the problem.) The links in the PDF files are fine, and the page numbers are correct. ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: Flakey cross references
I've had it both ways but as a best practice you need to save the document you're referring to after you place the cross-reference. Every tag that is the target of a cross-reference gets a marker. For reasons unknown to me, sometimes these markers become stale and have to be deleted and reinserted. This might also cause your references to break. Do a search for All Markers or for Markers of Type cross-reference and check them out. Make sure the marker matches the tag with which it's associated. On Wed, Jul 21, 2010 at 8:09 AM, Dr Rick Smith r...@cryptosmith.com wrote: Keep in mind that there are two parts to every cross reference: the text that refers, and the text referred to. You need both files open to create a cross reference and you must save BOTH files to preserve the cross reference. As far a I know, you can't create a cross reference to a read-only file. But honestly, I've never seriously tried. On Jul 20, 2010, at 1:00 PM, framers-requ...@lists.frameusers.com wrote: From: Layton, Debbie debbie.lay...@xerox.com To: framers@lists.frameusers.com Subject: Flakey cross references Message-ID: 78ef4e337f3131469c3bb1f11a42d8970d83b...@usa7061ms04.na.xerox.net Content-Type: text/plain; charset=us-ascii I'm using FrameMaker 7.0 on XP Professional. I've got a book with about 11 chapters in it. I continue to get unresolved cross reference messages. I have gone in and re-done all of them, since the original files were copied from another manual, but when I open the documents again, I get the messages again. None of the files have been moved. I have been printing .ps files in order to create PDFs of the book. (Somehow that seems to have something to do with the problem.) The links in the PDF files are fine, and the page numbers are correct. ___ You are currently subscribed to framers as dr_go...@pobox.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/dr_gonzo%40pobox.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info. -- Steve Johnson, dr_go...@pobox.com ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: Flakey cross references
Steve Johnson wrote: I've had it both ways but as a best practice you need to save the document you're referring to after you place the cross-reference. Every tag that is the target of a cross-reference gets a marker. For reasons unknown to me, sometimes these markers become stale and have to be deleted and reinserted. This might also cause your references to break. Do a search for All Markers or for Markers of Type cross-reference and check them out. Make sure the marker matches the tag with which it's associated. Sorry, but this is just bad advice. Cross-reference markers don't become stale. When you point a cross-reference to a paragraph, FM generates a unique string for the marker text. (If you point xrefs to markers you manually inserted -- which is necessary when creating xrefs to destinations in text insets -- it's up to you to ensure that the marker text is unique and identifiable by you.) This unique marker text string identifies the destination of the cross-reference so the cross-reference knows where to take you. The string looks something like this: 38790: Head1: Conference Templates The second element of the string is the name of the paragraph tag in which the marker is created. But it's just a unique string; using the pgf tag name is just a convention some FM programmers chose to use. If you change that paragraph to a Head2, the marker string isn't updated to 38790: Head2: Conference Templates -- it remains unchanged. It _has_ to, otherwise the cross-references to that marker won't be able to find it anymore and will be broken. If you delete and reinsert xref markers (unless you exactly re-create their marker text), or if you (m)ake sure the marker matches the tag, you'll _definitely_ break the cross-references to it. Some of the reasons cross-references break are: (1) The destination file isn't open, and FM can't open it in the background to resolve the xref (because, e.g., there are missing fonts). (2) The destination is in hidden conditional text (this is operator error; the xref should have the same condition applied and also be hidden). (3) Someone accidentally deleted the marker (most often happens when editing without View Text Symbols turned on). (4) Someone who doesn't understand markers thinks editing the marker text or re-creating them to overcome staleness is a good idea. Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-903-6372 -- ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: Flakey cross references
My apologies to Steve if this came across as rude. I usually remember to review for snippiness before sending, but my microwave was beeping at me. :-) Nonetheless, I stand by my points. And I remembered another reason xrefs can unexpectedly break. If you cut and paste text containing an xref marker, FM retains the marker, so the xrefs to it will find the text's new location. But if you _copy_ and paste, FM is clever enough to eliminate the marker so that you don't have duplicate unique markers. So, if you're the belt-and-suspenders type who first copies and pastes, and then goes back and cuts the original -- oops, broken xrefs. Richard -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers- boun...@lists.frameusers.com] On Behalf Of Combs, Richard Sent: Wednesday, July 21, 2010 7:32 PM To: dr_go...@pobox.com; Dr Rick Smith Cc: framers@lists.frameusers.com Subject: RE: Flakey cross references Steve Johnson wrote: I've had it both ways but as a best practice you need to save the document you're referring to after you place the cross-reference. Every tag that is the target of a cross-reference gets a marker. For reasons unknown to me, sometimes these markers become stale and have to be deleted and reinserted. This might also cause your references to break. Do a search for All Markers or for Markers of Type cross-reference and check them out. Make sure the marker matches the tag with which it's associated. Sorry, but this is just bad advice. Cross-reference markers don't become stale. When you point a cross-reference to a paragraph, FM generates a unique string for the marker text. (If you point xrefs to markers you manually inserted -- which is necessary when creating xrefs to destinations in text insets -- it's up to you to ensure that the marker text is unique and identifiable by you.) This unique marker text string identifies the destination of the cross- reference so the cross-reference knows where to take you. The string looks something like this: 38790: Head1: Conference Templates The second element of the string is the name of the paragraph tag in which the marker is created. But it's just a unique string; using the pgf tag name is just a convention some FM programmers chose to use. If you change that paragraph to a Head2, the marker string isn't updated to 38790: Head2: Conference Templates -- it remains unchanged. It _has_ to, otherwise the cross-references to that marker won't be able to find it anymore and will be broken. If you delete and reinsert xref markers (unless you exactly re-create their marker text), or if you (m)ake sure the marker matches the tag, you'll _definitely_ break the cross-references to it. Some of the reasons cross-references break are: (1) The destination file isn't open, and FM can't open it in the background to resolve the xref (because, e.g., there are missing fonts). (2) The destination is in hidden conditional text (this is operator error; the xref should have the same condition applied and also be hidden). (3) Someone accidentally deleted the marker (most often happens when editing without View Text Symbols turned on). (4) Someone who doesn't understand markers thinks editing the marker text or re-creating them to overcome staleness is a good idea. Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-903-6372 -- ___ You are currently subscribed to framers as richard.co...@polycom.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/richard.combs%40polycom .com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info. ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Flakey cross references
Keep in mind that there are two parts to every cross reference: the text that refers, and the text referred to. You need both files open to create a cross reference and you must save BOTH files to preserve the cross reference. As far a I know, you can't create a cross reference to a read-only file. But honestly, I've never seriously tried. > On Jul 20, 2010, at 1:00 PM, framers-request at lists.frameusers.com wrote: > >> From: "Layton, Debbie" >> To: >> Subject: Flakey cross references >> Message-ID: >> <78EF4E337F3131469C3BB1F11A42D8970D83B1CF at USA7061MS04.na.xerox.net> >> Content-Type: text/plain;charset="us-ascii" >> >> I'm using FrameMaker 7.0 on XP Professional. I've got a book with about >> 11 chapters in it. >> >> >> >> I continue to get unresolved cross reference messages. I have gone in >> and re-done all of them, since the original files were copied from >> another manual, but when I open the documents again, I get the messages >> again. None of the files have been moved. I have been printing .ps files >> in order to create PDFs of the book. (Somehow that seems to have >> something to do with the problem.) The links in the PDF files are fine, >> and the page numbers are correct. >>
Flakey cross references
I've had it both ways but as a best practice you need to save the document you're referring to after you place the cross-reference. Every tag that is the target of a cross-reference gets a marker. For reasons unknown to me, sometimes these markers become stale and have to be deleted and reinserted. This might also cause your references to break. Do a search for All Markers or for Markers of Type cross-reference and check them out. Make sure the marker matches the tag with which it's associated. On Wed, Jul 21, 2010 at 8:09 AM, Dr Rick Smith wrote: > Keep in mind that there are two parts to every cross reference: the text that > refers, and the text referred to. You need both files open to create a cross > reference and you must save BOTH files to preserve the cross reference. > > As far a I know, you can't create a cross reference to a read-only file. But > honestly, I've never seriously tried. > > >> On Jul 20, 2010, at 1:00 PM, framers-request at lists.frameusers.com wrote: >> >>> From: "Layton, Debbie" >>> To: >>> Subject: Flakey cross references >>> Message-ID: >>> ? ? ?<78EF4E337F3131469C3BB1F11A42D8970D83B1CF at USA7061MS04.na.xerox.net> >>> Content-Type: text/plain; ? ?charset="us-ascii" >>> >>> I'm using FrameMaker 7.0 on XP Professional. I've got a book with about >>> 11 chapters in it. >>> >>> >>> >>> I continue to get unresolved cross reference messages. I have gone in >>> and re-done all of them, since the original files were copied from >>> another manual, but when I open the documents again, I get the messages >>> again. None of the files have been moved. I have been printing .ps files >>> in order to create PDFs of the book. (Somehow that seems to have >>> something to do with the problem.) The links in the PDF files are fine, >>> and the page numbers are correct. >>> > > ___ > > > You are currently subscribed to framers as dr_gonzo at pobox.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/dr_gonzo%40pobox.com > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info. > -- Steve Johnson, dr_gonzo at pobox.com
Flakey cross references
Steve Johnson wrote: > I've had it both ways but as a best practice you need to save the > document you're referring to after you place the cross-reference. > > Every tag that is the target of a cross-reference gets a marker. For > reasons unknown to me, sometimes these markers become stale and have > to be deleted and reinserted. This might also cause your references to > break. > > Do a search for All Markers or for Markers of Type cross-reference and > check them out. Make sure the marker matches the tag with which it's > associated. Sorry, but this is just bad advice. Cross-reference markers don't become "stale." When you point a cross-reference to a paragraph, FM generates a unique string for the marker text. (If you point xrefs to markers you manually inserted -- which is necessary when creating xrefs to destinations in text insets -- it's up to you to ensure that the marker text is unique and identifiable by you.) This unique marker text string identifies the destination of the cross-reference so the cross-reference "knows" where to take you. The string looks something like this: 38790: Head1: Conference Templates The second element of the string is the name of the paragraph tag in which the marker is created. But it's just a unique string; using the pgf tag name is just a convention some FM programmers chose to use. If you change that paragraph to a Head2, the marker string isn't updated to "38790: Head2: Conference Templates" -- it remains unchanged. It _has_ to, otherwise the cross-references to that marker won't be able to find it anymore and will be broken. If you delete and reinsert xref markers (unless you exactly re-create their marker text), or if you "(m)ake sure the marker matches the tag," you'll _definitely_ break the cross-references to it. Some of the reasons cross-references break are: (1) The destination file isn't open, and FM can't open it in the background to resolve the xref (because, e.g., there are missing fonts). (2) The destination is in hidden conditional text (this is operator error; the xref should have the same condition applied and also be hidden). (3) Someone accidentally deleted the marker (most often happens when editing without View > Text Symbols turned on). (4) Someone who doesn't understand markers thinks editing the marker text or re-creating them to overcome "staleness" is a good idea. Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-903-6372 --
Flakey cross references
My apologies to Steve if this came across as rude. I usually remember to review for snippiness before sending, but my microwave was beeping at me. :-) Nonetheless, I stand by my points. And I remembered another reason xrefs can unexpectedly break. If you cut and paste text containing an xref marker, FM retains the marker, so the xrefs to it will find the text's new location. But if you _copy_ and paste, FM is clever enough to eliminate the marker so that you don't have duplicate "unique" markers. So, if you're the belt-and-suspenders type who first copies and pastes, and then goes back and cuts the original -- oops, broken xrefs. Richard > -Original Message- > From: framers-bounces at lists.frameusers.com [mailto:framers- > bounces at lists.frameusers.com] On Behalf Of Combs, Richard > Sent: Wednesday, July 21, 2010 7:32 PM > To: dr_gonzo at pobox.com; Dr Rick Smith > Cc: framers at lists.frameusers.com > Subject: RE: Flakey cross references > > Steve Johnson wrote: > > > I've had it both ways but as a best practice you need to save the > > document you're referring to after you place the cross-reference. > > > > Every tag that is the target of a cross-reference gets a marker. For > > reasons unknown to me, sometimes these markers become stale and have > > to be deleted and reinserted. This might also cause your references to > > break. > > > > Do a search for All Markers or for Markers of Type cross-reference and > > check them out. Make sure the marker matches the tag with which it's > > associated. > > Sorry, but this is just bad advice. Cross-reference markers don't become > "stale." > > When you point a cross-reference to a paragraph, FM generates a unique > string for the marker text. (If you point xrefs to markers you manually > inserted -- which is necessary when creating xrefs to destinations in text > insets -- it's up to you to ensure that the marker text is unique and > identifiable by you.) > > This unique marker text string identifies the destination of the cross- > reference so the cross-reference "knows" where to take you. The string > looks something like this: > > 38790: Head1: Conference Templates > > The second element of the string is the name of the paragraph tag in which > the marker is created. But it's just a unique string; using the pgf tag > name is just a convention some FM programmers chose to use. If you change > that paragraph to a Head2, the marker string isn't updated to "38790: > Head2: Conference Templates" -- it remains unchanged. It _has_ to, > otherwise the cross-references to that marker won't be able to find it > anymore and will be broken. > > If you delete and reinsert xref markers (unless you exactly re-create their > marker text), or if you "(m)ake sure the marker matches the tag," you'll > _definitely_ break the cross-references to it. > > Some of the reasons cross-references break are: > > (1) The destination file isn't open, and FM can't open it in the background > to resolve the xref (because, e.g., there are missing fonts). > > (2) The destination is in hidden conditional text (this is operator error; > the xref should have the same condition applied and also be hidden). > > (3) Someone accidentally deleted the marker (most often happens when > editing without View > Text Symbols turned on). > > (4) Someone who doesn't understand markers thinks editing the marker text > or re-creating them to overcome "staleness" is a good idea. > > > Richard G. Combs > Senior Technical Writer > Polycom, Inc. > richardDOTcombs AT polycomDOTcom > 303-223-5111 > -- > rgcombs AT gmailDOTcom > 303-903-6372 > -- > > > > > > > ___ > > > You are currently subscribed to framers as richard.combs at polycom.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/richard.combs%40polycom > .com > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info.
Flakey cross references
I'm using FrameMaker 7.0 on XP Professional. I've got a book with about 11 chapters in it. I continue to get unresolved cross reference messages. I have gone in and re-done all of them, since the original files were copied from another manual, but when I open the documents again, I get the messages again. None of the files have been moved. I have been printing .ps files in order to create PDFs of the book. (Somehow that seems to have something to do with the problem.) The links in the PDF files are fine, and the page numbers are correct. Any idea what's happening here? Thanks! Debbie Layton Technical Writer Customer Publications 503.582.6822 debbie.lay...@xerox.com ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: Flakey cross references
Is there any hidden conditionalized text? That could cause the message. Did you do a search on unresolved cross-ref? Nadine On 19/07/2010 7:47 PM, Layton, Debbie wrote: I'm using FrameMaker 7.0 on XP Professional. I've got a book with about 11 chapters in it. I continue to get unresolved cross reference messages. I have gone in and re-done all of them, since the original files were copied from another manual, but when I open the documents again, I get the messages again. None of the files have been moved. I have been printing .ps files in order to create PDFs of the book. (Somehow that seems to have something to do with the problem.) The links in the PDF files are fine, and the page numbers are correct. Any idea what's happening here? Thanks! Debbie Layton Technical Writer Customer Publications 503.582.6822 debbie.lay...@xerox.com ___ You are currently subscribed to framers as generic...@yahoo.ca. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/generic668%40yahoo.ca Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info. ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: Flakey cross references
If you're only seeing the unresolved cross-reference messages when you open the file (in the book, I presume), it's probably because the files that the cross-references point to haven't opened yet. If most cross-references point to one or two files, open those first, then open all the other files, and you should be all set. If you're not getting unresolved cross-references reported in an error log when you update the book, the cross-references are fine. Hope that helps! Susan McDonald On Jul 20, 2010, at 1:00 PM, framers-requ...@lists.frameusers.com wrote: From: Layton, Debbie debbie.lay...@xerox.com To: framers@lists.frameusers.com Subject: Flakey cross references Message-ID: 78ef4e337f3131469c3bb1f11a42d8970d83b...@usa7061ms04.na.xerox.net Content-Type: text/plain; charset=us-ascii I'm using FrameMaker 7.0 on XP Professional. I've got a book with about 11 chapters in it. I continue to get unresolved cross reference messages. I have gone in and re-done all of them, since the original files were copied from another manual, but when I open the documents again, I get the messages again. None of the files have been moved. I have been printing .ps files in order to create PDFs of the book. (Somehow that seems to have something to do with the problem.) The links in the PDF files are fine, and the page numbers are correct. Any idea what's happening here? Thanks! Debbie Layton Technical Writer Customer Publications 503.582.6822 debbie.lay...@xerox.com Freedom is not to be rummaged for, among old parchments or musty records. It is written, as with a sun-beam, on the whole of human nature, by the hand of the Divinity itself. Alexander Hamilton ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Flakey cross references
Is there any hidden conditionalized text? That could cause the message. Did you do a search on unresolved cross-ref? Nadine On 19/07/2010 7:47 PM, Layton, Debbie wrote: > I'm using FrameMaker 7.0 on XP Professional. I've got a book with about > 11 chapters in it. > > > > I continue to get unresolved cross reference messages. I have gone in > and re-done all of them, since the original files were copied from > another manual, but when I open the documents again, I get the messages > again. None of the files have been moved. I have been printing .ps files > in order to create PDFs of the book. (Somehow that seems to have > something to do with the problem.) The links in the PDF files are fine, > and the page numbers are correct. > > > > Any idea what's happening here? > > > > Thanks! > > > > Debbie Layton > > Technical Writer > Customer Publications > 503.582.6822 > debbie.layton at xerox.com > > > > ___ > > > You are currently subscribed to framers as generic668 at yahoo.ca. > > 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/generic668%40yahoo.ca > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info. > >
Flakey cross references
If you're only seeing the unresolved cross-reference messages when you open the file (in the book, I presume), it's probably because the files that the cross-references point to haven't opened yet. If most cross-references point to one or two files, open those first, then open all the other files, and you should be all set. If you're not getting unresolved cross-references reported in an error log when you update the book, the cross-references are fine. Hope that helps! Susan McDonald On Jul 20, 2010, at 1:00 PM, framers-request at lists.frameusers.com wrote: > From: "Layton, Debbie" > To: > Subject: Flakey cross references > Message-ID: > <78EF4E337F3131469C3BB1F11A42D8970D83B1CF at USA7061MS04.na.xerox.net> > Content-Type: text/plain; charset="us-ascii" > > I'm using FrameMaker 7.0 on XP Professional. I've got a book with about > 11 chapters in it. > > > > I continue to get unresolved cross reference messages. I have gone in > and re-done all of them, since the original files were copied from > another manual, but when I open the documents again, I get the messages > again. None of the files have been moved. I have been printing .ps files > in order to create PDFs of the book. (Somehow that seems to have > something to do with the problem.) The links in the PDF files are fine, > and the page numbers are correct. > > > > Any idea what's happening here? > > > > Thanks! > > > > Debbie Layton > > Technical Writer > Customer Publications > 503.582.6822 > debbie.layton at xerox.com > "Freedom is not to be rummaged for, among old parchments or musty records. It is written, as with a sun-beam, on the whole of human nature, by the hand of the Divinity itself." Alexander Hamilton
Flakey cross references
I'm using FrameMaker 7.0 on XP Professional. I've got a book with about 11 chapters in it. I continue to get unresolved cross reference messages. I have gone in and re-done all of them, since the original files were copied from another manual, but when I open the documents again, I get the messages again. None of the files have been moved. I have been printing .ps files in order to create PDFs of the book. (Somehow that seems to have something to do with the problem.) The links in the PDF files are fine, and the page numbers are correct. Any idea what's happening here? Thanks! Debbie Layton Technical Writer Customer Publications 503.582.6822 debbie.layton at xerox.com
