Hi, 

If the abstract appears only on the titlepage of the article, you can customize 
the titlepage stylesheet to omit the abstract. 
Otherwise, you can do it with profiling, and assign a condition to the abstract 
that does not get fulfilled, but for this you have to modify your build 
environment somewhat.
Bob's book describes both methods in detail: 
http://www.sagehill.net/docbookxsl/index.html

There may be other solutions well, but these come to my mind first.

Regards, 

Robert


On Saturday, May 01, 2010 19:19 CEST, Grant Taylor <[email protected]> 
wrote: 
 
> Hi.  I'm relatively new to DocBook, so this may be completely off track.
> 
> In short I want to know what the best way is to suppress an element in 
> the processed output.
> 
> I have multiple articles that include one <abstract> element per article 
> that is used as a summary of the article.  (If I should be using 
> something other than <abstract> please let me know what I should use.) 
> I am then XIncluding the <title> and <abstract> of the articles using 
> XInclude lines with an XPointer referencing the ID of the element to 
> include.  This is working just fine.
> 
> What I want to know how to do is suppress the output of the <abstract> 
> in the original article when I'm processing it by its self.
> 
> I added the <abstract> to the articles for the purpose of being 
> XIncluded elsewhere and I want it to not show up unless it's explicitly 
> referenced.  I guess you could look at the <abstract> as meta data for 
> the article that I want there to be used by other DocBooks, not to be 
> used the the article its self.
> 
> How would I go about suppressing an element in the individual article(s)?
> 
> Thanks in advance.
> 
> 
> 
> Grant. . . .
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to