How are you doing the profiling, Cheri? You need to set the condition to what you want to show up -- any other setting for that condition (including no setting at all) makes it disappear during the profiling phase.
For example, if you have the following code: <sect1 condition="internal"> <title>Awesome title goes here</title> ... </sect1> Then setting condition to "internal" will keep it in the document; setting it to "external", "fred", or anything else will exclude it from the document. Don't forget to process the profiled version using either Single-pass or Two-pass processing. Ken On 5/23/07, Dennison, Cheri <[EMAIL PROTECTED]> wrote:
Hi, I'm using: * Saxon 6.5.5 * Xerces 2.8.0 * Apache FOP 0.20.5 Context: I just want to confirm that my experience of profiling is correct, because it contradicts the description of profiling in the chapter in Bob Stayton's book. My task is to try to control what goes in the PDF. My Results: -- Any element with attribute condition="anyvalue" gets hidden and doesn't show up in the PDF. So, the attribute is removing the element from the output instead of putting the element into the output. That seems to be the opposite of how profiling is described in the book. -- It doesn't matter what I set profile.condition to when I process the guide. Any value causes any element with a condition attribute to be hidden from the PDF. Does this sound right? It seems to work consistently, but it just doesn't work like I thought it would. Thanks so much for any thoughts you have!! cheri -- Cheri Dennison / Technical Writer AWS Platform Group [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
