But the ability to use the same component files in multiple different book files is one of the foundations of the FrameMaker book paradigm. There are some very good reasons for using structured FrameMaker, but it's really overkill if all you need to do is build several variant books that only have a few components that differ between the various books. That's the kind of situation FrameMaker books were designed to handle.
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:framers-bounces+fred.ridder=intel.com at lists.frameusers.com] On Behalf Of LAnthone at genelogic.com Sent: Thursday, June 08, 2006 4:31 PM To: Combs, Richard Cc: framers at frameusers.com; framers-bounces+lanthone=genelogic.com at lists.frameusers.com Subject: RE: Hiding Pages? I had the same problem with multiple conditions and finally realized that you can't apply a condition at the chapter (file) level. I ended up using Structured FrameMaker with the Sourcerer plug-in. I used attributes at the top level (file or section) to condition entire files. This works very well, but of course, you have to use Structured FrameMaker. I never found a way around that problem and was reluctant to maintain different versions of the book file. However, if you make your conditional content part of the previous chapter, you should be able to hide it when it's printing or conversion time, with page numbering intact. Lauren Anthone, Senior Information Developer Lead, Information Development Department Gene Logic, Inc. 50 West Watkins Gaithersburg, MD 20878 Ph: 240.364.7611 E-mail: lanthone at genelogic.com Corporate Headquarters 610 Professional Drive Gaithersburg, MD 20879
