Re: [xsl] DTD entities in XSLT

["Willem Van Lishout willemvanlishout@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Depending on the server you use you might be able to gzip it.

On Aug 25, 2020, 22:54, at 22:54, "Martynas JuseviD
ius
martynas@xxxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>What's less great is that the resulting SEF file is 5+ MB :/ That
>pretty much offsets the size of Saxon-CE which we now have removed in
>favor of Saxon-JS 2. I guess we'll need to move more processing to the
>browser in order to avoid page reloads...
>
>On Tue, Aug 25, 2020 at 10:48 PM Martynas JuseviD
ius
>martynas@xxxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
>wrote:
>>
>> I think I managed to integrate the SEF generation into a Maven (web)
>> project. I'll paste it below as it might be useful to others. What it
>> does it basically:
>> - executes shell commands to get a list of .xsl files (recursively)
>> under ${xsl.root.dir}
>> - iterates through the list and inlines DTD entities in each of the
>> files (using net.sf.saxon.Query)
>> - invokes xslt3 on Node.js to compile SEF for the configured
>> ${saxon-js.stylesheet}
>>
>> The default war:war goal has to be disabled and packaging delayed
>> until later so that resources overlaid from dependencies also can be
>> pre-processed and that the SEF file gets packaged into the final war
>> archive. Improvements are welcome.
>>
>> The build now takes quite a bit longer, but no manual intervention or
>> changes to the source files are necessary.
>>
>> The POM can be found here:
>> https://github.com/AtomGraph/LinkedDataHub/blob/rf-saxon-js2/pom.xml
>>
>> On Tue, Aug 25, 2020 at 1:24 PM Martynas JuseviD
ius
>> martynas@xxxxxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
>> wrote:
>> >
>> > It looks to me like that page has an example with a trailing )
>which
>> > shouldn't be there:
>> >
>> > <xsl:variable name="inBrowser"
>> >      select="system-property('xsl:product-name') eq 'Saxon-JS' and
>> >                   system-property('saxon:platform') eq
>'Browser')"/>
>> >
>> > On Mon, Aug 24, 2020 at 2:48 PM Martynas JuseviD
ius
>> > <martynas@xxxxxxxxxxxxx> wrote:
>> > >
>> > > My question is about Saxon-JS 2 however:
>> > >
>http://www.saxonica.com/saxon-js/documentation/index.html#!conformance/xslt3
0
>> > >
>> > > On Mon, Aug 24, 2020 at 2:32 PM Michele R Combs mrrothen@xxxxxxx
>> > > <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>> > > >
>> > > > We use internal text entities with Saxon and have had no
>problem.  We're using Saxon9he
>> > > >
>> > > > Michele
>> > > >
>> > > > -----Original Message-----
>> > > > From: Martynas JuseviD
ius martynas@xxxxxxxxxxxxx
><xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
>> > > > Sent: Monday, August 24, 2020 7:20 AM
>> > > > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> > > > Subject: Re: [xsl] DTD entities in XSLT
>> > > >
>> > > > Thanks. Will this work in Saxon-HE? I'm looking for a solution
>that could be used in open-source code.