Having a bit of annoyance with this xsl problem.
The crux of it is that I need one section from
Functional Requirements to Design Derived Requirements
and one from Design Derived Requirements to the end of
the doc. Those sections need then certain operations
performed to get the correct xml output (I can handle
that part ok). Hope this is enough info.
text in a data node just means data I can't share with
you guys.
<?xml version="1.0" encoding="ISO-8859-1"?>
<root>
<data>text</data>
<data>text</data>
<data>text</data>
<data>Functional Requirements</data>
<data></data>
<data>text</data>
<data></data>
<data>text</data>
<data></data>
<data>text</data>
<data>text</data>
<data>text</data>
<data>text</data>
<data>text</data>
<data>text</data>
<data>text</data>
<data>text</data>
<data>text</data>
<data>text</data>
<data></data>
<data>text</data>
<data></data>
<data>Design Derived Requirements</data>
<data></data>
<data>text</data>
<data></data>
<data>text</data>
<data></data>
<data>text</data>
<data></data>
<data>text</data>
</root>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--