Re: [xsl] calling two consecutive xsl files

[António Mota <amsmota@xxxxxxxxx>]

Yes, in portuguese should be "terrmvel", and it too can have both a
"wonderful" or a "horrible" meaning, so i didn't know what the sense
was... And frankly, being about MS i thought of the later...


On Thu, 10 Mar 2005 14:59:31 -0600, JBryant@xxxxxxxxx <JBryant@xxxxxxxxx>
wrote:
> :)
>
> "terrific" = good
>
> Its root is the Latin terrere, to frighten. English (and I suppose other
> languages) has an interesting way of reversing the meanings of some
> adjectives over time. This is one of those adjectives. One informal use of
> "bad" means good, too. And "awful" and "awesome" have traded meanings from
> what they had about 5 centuries ago.
>
> Now that I am WAY off topic....
>
> Jay Bryant
> Bryant Communication Services
> (presently consulting at Synergistic Solution Technologies)
>
> Antsnio Mota <amsmota@xxxxxxxxx>
> 03/10/2005 02:47 PM
> Please respond to
> xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>
> To
> xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> cc
>
> Subject
> Re: [xsl] calling two consecutive xsl files
>
> Hmmm, since i'm not a english native *and* not a MS expert, the
> "terrific" here is a good thing or a bad thing? It's "terrific" in the
> sense of "terror" or in the sense of "uau!".
>
> Or simply putting it it's   :)    or    :(   ?
>
> Now we're using a IIS with asp on it, but i'll prefer a platform
> agnostic thing. The upgrade(?) a "normal" asp to asp.net is
> straithforward?
>
> On Thu, 10 Mar 2005 13:36:04 -0600, Pieter Reint Siegers Kort
> <pieter.siegers@xxxxxxxxxxx> wrote:
> > One way would be to upgrade to ASP.NET with its terrific XML support,
> and
> > use Saxon.NET which supports XSLT 2.0.
> > https://sourceforge.net/projects/saxondotnet/
> >
> > NB1: Saxon.NET is an OS effort to port the great Saxon product to .NET
> and
> > Mono. All functionality offered has its origin in Saxon, therefore all
> > credits go to its creator, Michael Kay.
> >
> > NB2: Saxon.NET is still an early beta product, and is currently about
> 25%
> > slower than using Saxon (on Windows). There is a workaround to this -
> you
> > can spawn processes in ASP.NET which run Saxon transformations in the
> > background and return to you the output, which is the same as running
> Saxon
> > from the command line, and thus has the same performance.
> >
> > Cheers,
> > <prs/>
> > http://www.pietsieg.com