Subject: Re: Re: [xsl] Rexsel — A simpler way of writing XSLT From: "Piez, Wendell A. (Fed) wendell.piez@xxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: Mon, 1 Jul 2024 14:29:50 -0000 |
Hello, Or, today, to process HTML into an XSLT pipeline, one might opt for XProc 3.0. What with plain-text, JSON and HTML inputs, and with XSLT streaming and accumulators, maybe XSLT has finally caught up with Omnimark? Regards, Wendell -----Original Message----- From: Martin Honnen martin.honnen@xxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Sent: Sunday, June 30, 2024 4:51 PM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: [xsl] Rexsel A simpler way of writing XSLT On 30/06/2024 19:20, Chris Papademetrious chrispitude@xxxxxxxxx wrote: > Nowadays I mostly process HTML in Python. The funny thing is, I would > kill for a way to natively process HTML5 in XSLT (without resorting to > XHTML) because the content processing I do would fit a template based > approach very well. But alas, there's no easy way in the Python world. If you have a Saxon PE or EE license you can use SaxonCPE or SaxonCEE (https://pypi.org/project/saxoncee/) with Python and use the parse-html extension/XPath 4 function to process HTML5 with XSLT 4/XQuery 4 (and until we see 12.5 with XPath if you use the hack of https://saxonica.plan.io/issues/5967#note-8). parse-html(unparsed-text("https://stackoverflow.com/questions/tagged/saxon")) Your mileage of "easy way" might differ.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] xslide [Was: Rexsel — A , Norm Tovey-Walsh ndw | Thread | Aw: Re: [xsl] Rexsel — A simpler w, Martin Honnen martin |
Re: [xsl] xslide [Was: Rexsel — A , Tony Graham tgraham@ | Date | Aw: Re: [xsl] Rexsel — A simpler w, Martin Honnen martin |
Month |