Thanks for your comments Fr�d�ric
Wish you lots of success,
Valerie
Fr�d�ric Glorieux wrote:
>
> >
> >>This is critic for me, because real life sxw files have usually
> >>"automatic-styles" (really bad idea from OOo dev). Also, i need
> >>customizable styles in different languages, and for different exports.
> >>
> >
> >
> > Automatic styles are mostly linked to predefined styles ....
>
> :o( look up needed.
>
> > Now,
> > imagine parsing and processing all that information into variables
>
> Hey, maybe with a good xpath, something better could be done. I have no
> time these days to explore this, but perhaps better could be done than 2
> passes
>
> > and
> > making these available to XSLT ? Wouldn't that be wonderful ? But it
> > seams impossible to handle all of that in XSLT - especially if you want
> > to have a fast execution time.
> >
> > I am wondering .... did you ever happen to investigate strong
> > possibilities of XSLT + programming (Groovy or something similar) ? Or
> > is, in your opinion, Java + XSLT the best solution ever to be ?
>
> To my opinion, value of XSLT is to be a very cross paltform language.
> Using XSL extensions (like MS javascript, even JAVA) make your XSL dev
> loosing this power. Better is to think in pipe process. If you need some
> strong procedural calculation, provide by a language like JAVA or
> Python, think it as a generator (generate the clean XML you need), and
> let your XSL to be pure 1.0.
>
> --
> Fr�d�ric Glorieux ("AJLSM", <http://ajlsm.com>)
> "Transfolio" <http://transfolio.org>
>
> ---------------------------------------------------------------------
> 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]
