It's bad tactics to suggest that you're 80% of the way to a solution, and
not show us the 80%. No-one wants to redo the work you've already done on
the off-chance that they'll be able to help you with the final 20%.
That's especially true as it's a difficult problem and one has to do a lot
of guesswork about the requirements. What output would you expect if the
two
source documents are:
<snip>
Sorry, but suggesting improvements to code I haven't seen is beyond my
abilities.
I debated posting any XSL I had, and didn't because it was voluminous--never
mind the data. As it was I was I was looking for an algorithm, not for a
correction in syntax or semantics.
As for the optimization, now I have the transform running in under 6
seconds, and that's "good enough" for the moment. But thank you for your
input above.
Regards,
--A
_________________________________________________________________
Don?t just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
--~------------------------------------------------------------------
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>
--~--