RE: XRefs mysteriously converted to text (SOLVED)
With the help of some list members, I figured out what must have happened. I deliberately converted a couple of Xrefs to text. In one instance, I probably right-clicked in a location that wasn't precisely on the existing XRef and selected Cross Reference Convert to Text. For example, I may have right-clicked immediately after the last character in the XRef. In that case, the Convert to Text windows opens with the All Cross References option as the default. I failed to notice the option and clicked the Convert button. One way to prevent the behavior, which I will try to adopt, is as follows: * Use the Special Cross Reference command or the right-click Cross Reference command only to create a new XRef. * To edit an existing cross reference, always double-click the XRef itself to ensure that it is selected. Do not right-click or use the menu to edit an existing XRef. * Read the options in the Convert window and think twice before converting any XRef to text! Thanks to all who replied. David Shaked (Wernick) AlmondWeb Ltd. http://www.almondweb.com Technical Documentation * Web Development * Word and WebWorks Consultants -Original Message- From: David Shaked (Wernick) [mailto:[EMAIL PROTECTED] Sent: Monday, August 13, 2007 16:49 To: Framers (framers@lists.frameusers.com) Subject: XRefs mysteriously converted to text I experienced a distressing problem in an FM file that contained dozens of cross references. As I was editing the document, all the XRefs were suddenly and unexpectedly converted to ordinary text. The problem occurred in middle of an editing session. I am certain that when I opened the document, the XRefs were OK. In the past, I have occasionally detected individual cross references that were converted to text. I always assumed that the conversion was my own editing error, but now I am not so sure. I already restored the XRefs, but does someone have an idea what may have caused the problem and how I can prevent it in the future? Is there a known FrameMaker 7.2 bug that converts XRefs to text? Is there a Convert all XRefs to Text command that I inadvertently activated? Possibly relevant information: The FM document was originally created by importing from Word. Many but not all of the XRefs were originally created by a FrameScript program, used in conjunction with the Word import. The document has been heavily edited since then, with no other abnormal phenomena. David Shaked (Wernick) AlmondWeb Ltd. http://www.almondweb.com Technical Documentation * Web Development * Word and WebWorks Consultants ___ 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: XRefs mysteriously converted to text
On 8/14/07, Chris Borokowski [EMAIL PROTECTED] wrote: If you promise not to hold it against me, I'll tell you. I managed to screw this one up this week. In the Xref dialog box, there's an option Convert to Text that brings up another dialog box, and if in that you select Convert All to Text every Xref in your document becomes boring, unclickable text. In a shocking but familiar display of hypocrisy, I had been planning to save a backup, so spent some hours reconstructing Xrefs blown away in a quarter of a second of inattention. If Edit Undo fails to undo this kind of disaster, there's one possible safety net that could save you. If File Preferences General Autosave is enabled, and it hasn't autosaved since the convert-to-text action, the filename.auto.fm file may contain the file's state before the action. Immediately use File Open to open the filename.auto.fm file and save it to a new name, then check the x-refs. The only downside to working with auto-save always on is that saving large files may suspend keyboard action briefly. Small price to pay for insurance. My sympathies... (raises glass of green tea) HTH Regards, Peter ___ Peter Gold KnowHow ProServices ___ 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: XRefs mysteriously converted to text
Thank you, Peter. This is a good tip that I hadn't implemented on this project. --- Peter Gold [EMAIL PROTECTED] wrote: If Edit Undo fails to undo this kind of disaster, there's one possible safety net that could save you. If File Preferences General Autosave is enabled, and it hasn't autosaved since the convert-to-text action, the filename.auto.fm file may contain the file's state before the action. Immediately use File Open to open the filename.auto.fm file and save it to a new name, then check the x-refs. The only downside to working with auto-save always on is that saving large files may suspend keyboard action briefly. Small price to pay for insurance. http://technical-writing.dionysius.com/ technical writing | consulting | development Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. http://autos.yahoo.com/carfinder/ ___ 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.
XRefs mysteriously converted to text (SOLVED)
With the help of some list members, I figured out what must have happened. I deliberately converted a couple of Xrefs to text. In one instance, I probably right-clicked in a location that wasn't precisely on the existing XRef and selected Cross Reference > Convert to Text. For example, I may have right-clicked immediately after the last character in the XRef. In that case, the Convert to Text windows opens with the "All Cross References" option as the default. I failed to notice the option and clicked the Convert button. One way to prevent the behavior, which I will try to adopt, is as follows: * Use the Special > Cross Reference command or the right-click > Cross Reference command only to create a new XRef. * To edit an existing cross reference, always double-click the XRef itself to ensure that it is selected. Do not right-click or use the menu to edit an existing XRef. * Read the options in the Convert window and think twice before converting any XRef to text! Thanks to all who replied. David Shaked (Wernick) AlmondWeb Ltd. http://www.almondweb.com Technical Documentation * Web Development * Word and WebWorks Consultants -Original Message- From: David Shaked (Wernick) [mailto:da...@almondweb.com] Sent: Monday, August 13, 2007 16:49 To: Framers (framers at lists.frameusers.com) Subject: XRefs mysteriously converted to text I experienced a distressing problem in an FM file that contained dozens of cross references. As I was editing the document, all the XRefs were suddenly and unexpectedly converted to ordinary text. The problem occurred in middle of an editing session. I am certain that when I opened the document, the XRefs were OK. In the past, I have occasionally detected individual cross references that were converted to text. I always assumed that the conversion was my own editing error, but now I am not so sure. I already restored the XRefs, but does someone have an idea what may have caused the problem and how I can prevent it in the future? Is there a known FrameMaker 7.2 bug that converts XRefs to text? Is there a "Convert all XRefs to Text" command that I inadvertently activated? Possibly relevant information: The FM document was originally created by importing from Word. Many but not all of the XRefs were originally created by a FrameScript program, used in conjunction with the Word import. The document has been heavily edited since then, with no other abnormal phenomena. David Shaked (Wernick) AlmondWeb Ltd. http://www.almondweb.com Technical Documentation * Web Development * Word and WebWorks Consultants
XRefs mysteriously converted to text
If you promise not to hold it against me, I'll tell you. I managed to screw this one up this week. In the Xref dialog box, there's an option "Convert to Text" that brings up another dialog box, and if in that you select "Convert All to Text" every Xref in your document becomes boring, unclickable text. In a shocking but familiar display of hypocrisy, I "had been planning to" save a backup, so spent some hours reconstructing Xrefs blown away in a quarter of a second of inattention. My sympathies... (raises glass of green tea) --- "David Shaked (Wernick)" wrote: > I already restored the XRefs, but does someone have an idea what may > have > caused the problem and how I can prevent it in the future? Is there a > known > FrameMaker 7.2 bug that converts XRefs to text? Is there a "Convert > all > XRefs to Text" command that I inadvertently activated? http://technical-writing.dionysius.com/ technical writing | consulting | development Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. http://tv.yahoo.com/collections/222
XRefs mysteriously converted to text
On 8/14/07, Chris Borokowski wrote: > If you promise not to hold it against me, I'll tell you. I managed to > screw this one up this week. > > In the Xref dialog box, there's an option "Convert to Text" that brings > up another dialog box, and if in that you select "Convert All to Text" > every Xref in your document becomes boring, unclickable text. > > In a shocking but familiar display of hypocrisy, I "had been planning > to" save a backup, so spent some hours reconstructing Xrefs blown away > in a quarter of a second of inattention. If Edit > Undo fails to undo this kind of disaster, there's one possible safety net that could save you. If File > Preferences > General > Autosave is enabled, and it hasn't autosaved since the convert-to-text action, the filename.auto.fm file may contain the file's state before the action. Immediately use File > Open to open the filename.auto.fm file and save it to a new name, then check the x-refs. The only downside to working with auto-save always on is that saving large files may suspend keyboard action briefly. Small price to pay for insurance. > My sympathies... (raises glass of green tea) HTH Regards, Peter ___ Peter Gold KnowHow ProServices
XRefs mysteriously converted to text
Thank you, Peter. This is a good tip that I hadn't implemented on this project. --- Peter Gold wrote: > If Edit > Undo fails to undo this kind of disaster, there's one > possible safety net that could save you. If File > Preferences > > General > Autosave is enabled, and it hasn't autosaved since the > convert-to-text action, the filename.auto.fm file may contain the > file's state before the action. Immediately use File > Open to open > the filename.auto.fm file and save it to a new name, then check the > x-refs. > > The only downside to working with auto-save always on is that saving > large files may suspend keyboard action briefly. Small price to pay > for insurance. http://technical-writing.dionysius.com/ technical writing | consulting | development Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. http://autos.yahoo.com/carfinder/
XRefs mysteriously converted to text
I experienced a distressing problem in an FM file that contained dozens of cross references. As I was editing the document, all the XRefs were suddenly and unexpectedly converted to ordinary text. The problem occurred in middle of an editing session. I am certain that when I opened the document, the XRefs were OK. In the past, I have occasionally detected individual cross references that were converted to text. I always assumed that the conversion was my own editing error, but now I am not so sure. I already restored the XRefs, but does someone have an idea what may have caused the problem and how I can prevent it in the future? Is there a known FrameMaker 7.2 bug that converts XRefs to text? Is there a Convert all XRefs to Text command that I inadvertently activated? Possibly relevant information: The FM document was originally created by importing from Word. Many but not all of the XRefs were originally created by a FrameScript program, used in conjunction with the Word import. The document has been heavily edited since then, with no other abnormal phenomena. David Shaked (Wernick) AlmondWeb Ltd. http://www.almondweb.com Technical Documentation * Web Development * Word and WebWorks Consultants ___ 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.
XRefs mysteriously converted to text
I experienced a distressing problem in an FM file that contained dozens of cross references. As I was editing the document, all the XRefs were suddenly and unexpectedly converted to ordinary text. The problem occurred in middle of an editing session. I am certain that when I opened the document, the XRefs were OK. In the past, I have occasionally detected individual cross references that were converted to text. I always assumed that the conversion was my own editing error, but now I am not so sure. I already restored the XRefs, but does someone have an idea what may have caused the problem and how I can prevent it in the future? Is there a known FrameMaker 7.2 bug that converts XRefs to text? Is there a "Convert all XRefs to Text" command that I inadvertently activated? Possibly relevant information: The FM document was originally created by importing from Word. Many but not all of the XRefs were originally created by a FrameScript program, used in conjunction with the Word import. The document has been heavily edited since then, with no other abnormal phenomena. David Shaked (Wernick) AlmondWeb Ltd. http://www.almondweb.com Technical Documentation * Web Development * Word and WebWorks Consultants
