[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: <etreijs@xxxxxxxxxxxxxxxx>, <Framers@xxxxxxxxx>
Subject: RE: Fixing condition text mess
From: "Debbi Fortney Correia" <debbi.fortney@xxxxxxxxxxx>
Date: Thu, 17 Apr 2003 08:29:45 -0700
Importance: Normal
Reply-To: <debbi.fortney@xxxxxxxxxxx>
Sender: owner-framers@xxxxxxxxx
Hi Ed, Not sure if this will help as it is still a manual procedure, but have you considered creating an LOR using "Condition Tags"? When you initially create this file it shows the condition name and the page number, but you can change it on the LOR reference page to show <$paratext> also. Then you can identify each paragraph that has conditional text assigned and determine which text and/or condition tags can be deleted. Of course if all of the text with a certain condition tag applied can be deleted, deleting the condition tag will present the option of deleting the associated text as well, but this would be on a file-by-file basis. Importing condition tags won't delete tags that aren't present in the file from which you are importing. Debbi Fortney Correia Technical Trainer/Consultant Adobe Certified Expert, FrameMaker & Photoshop Bothell, WA 98011 425-482-2617 debbi.fortney@verizon.net ~~~~~~~~~~~~~ Ed Treijs wrote: We have a number of books that have accumulated a lot of template/format crud over the years. (They are "special" docs, indeed!) The current problem is that the chapters have a semi-random collection of miscellaneous conditional tags, many of which are apparently from years ago and quite obsolete. When regenerating the book, it's easy to get "inconsistent show/hide setting" and "inconsistent conditional indicator" errors. <snip> ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **