XSLT capabilities to Userscript and Userstyle execution engines

[sjehuda]

An extension (so called "WebExtension") for XSLT would be beneficial.

[sjehuda]

I think that an XSLT manager would be a greate idea.

I already have XSLT stylesheets that are able to transform Atom, DOAP, OPML, and RSS documents.

https://git.xmpp-it.net/sch/StreamBurner

I think, that incorporating "xslt-processor" of @DesignLiquido or SaxonJS of @Saxonica should be beneficial to Userscript software.

Developers, what do you think of that possibility?

@erosman (FireMonkey) @greasemonkey @Joolee (Userchrome Toggle) @scriptscat @ankit (Stylebot) @openstyles (Stylus) @Tampermonkey @UserStyles @usi-firefox (USI) @violentmonkey

Are there more Usescript or Userstyle management projects which I have neglected to mention?

I want to inform Mr. Melvin Reed also.

[erosman]

What would be the objective of XSLT with regard to userscript/userStyle mangers?

[sjehuda]

@erosman To make XML files, such as Atom, RSS, DOAP, MusicXML, MathXML, usable, and also to transfor HTML documents into better documents. Suppose that you are given an Atom or RSS document. With XSLT, you can design an XSLT stylesheet which would display the title at the bottom at the sides, at the top, or even multiple times. Enclosures can be realized as image gallery, or be instantly played with tags </audio> or </video> et cetera. You can control the document as you deem fit, without any restrictions or some foreign (i.e. of a local site) JS script that you would have to attempt to disable. Download these stylesheets, and add an RSS file. https://git.xmpp-it.net/sch/StreamBurner/src/branch/main/xsl/stylesheet.xsl Execute this command to transform the RSS with the XSLT diectives. $ xsltproc stylesheet.xsl YOUR_RSS_FILE.rss An HTML document be formed. Of course, that is a "traditional" or "common" HTML structure, and yet you might want to change it for RSS podcasts, MathXML, MusicXML etc cetera. There are plenty of possibilities.

[erosman]

User script/style managers inject into a web-page.
Are there examples of web-pages that serve Atom or RSS document to be displayed by the browser?

[sjehuda]

User script/style managers inject into a web-page.

They can also inject into an XML document. It is just data.

Are there examples of web-pages that serve Atom or RSS document to be displayed by the browser?

Yes, Rivista. All its pages are XML documents. https://journal.woodpeckersnest.eu/ Even the search interface is made of XML. https://journal.woodpeckersnest.eu/search/ Additionally, there are many of which are of podcast publishing platforms, yet they do not exploite all the features that XSLT and Atom offer, unlike Rivista, which does more, yet could do even further more. https://justintadlock.com/feed/atom https://blog.system76.com/rss.xml https://igalia.com/feed.xml https://maya.land/blogroll.opml (this one is interesting) https://fundor333.com/index.xml https://sk.ru/rss/ https://feeds.podcastmirror.com/higherside-chats https://classic.noscript.net/feed https://feeds.captivate.fm/aboard/ https://gpl-violations.org/news/index.atom The last one might not work due to recent cors policy, so try it offline.

[erosman]

Yes, Rivista. All its pages are XML documents.

https://journal.woodpeckersnest.eu/

Even the search interface is made of XML.

https://journal.woodpeckersnest.eu/search/

Above pages are standard HTML when viewed in a browser.

[sjehuda]

> Yes, Rivista. All its pages are XML documents. > > https://journal.woodpeckersnest.eu/ > > Even the search interface is made of XML. > > https://journal.woodpeckersnest.eu/search/ Above pages are standard HTML when viewed in a browser.

Thank you foe noticing, yet your statement is wrong. These are, in fact, Atom documents; Please. View the source. These pages appear as HTML, because your software appears to have an XSLT 1.0 interpreter. View the source of every page. Every page of that publication is an XML document. However, it is suggested that, soon, most browsers are expected to remove their XSLT interpreter; yet Even if that XSLT interpreter would not be removed, this idea would still be relevant, especially upon navigating to XML files *without* the directive "xml-stylesheet". Also, it would be relevant when people are not interested to view XML documents with XSLT stylesheets of others; or, when a stylesheet is linked, but is missing. These are the possible scenarios. (1) Invalid stylesheet This document refers to a supposed stylesheet, which is only a plain text file with two lines and two empty lines. https://andregarzia.com/feeds/all.atom.xml https://andregarzia.com/feeds/atom.xsl The stylesheet of DokuWiki appears to be of that of RSS, not of The Atom Syndication Format, and thus the document is not displayed as intended. https://wiki.xmpp-it.net/feed.php https://wiki.xmpp-it.net/lib/exe/css.php?s=feed (2) Missing stylesheet. Stylesheet might be missing, and most supposed "standard" browsers (gecko and webkit) display a blank page. This is deliberately done in order to abuse this scenario and conceal XSLT and syndicated technology from people. For years, the Government News RSS document of the Crown Dependency "Isle of Man" was missing (/xslt/Rss.xslt) which, due to the coordinated malfunction of those supposed standard browsers, resulted in a blank page, as if there was no RSS document. https://web.archive.org/web/20230322203017if_/https://www.gov.im/news/RssNews (3) Undesired stylesheets (CSS or XSLT) People might not want a custom stylesheet, and would prefer their own. This is especially valid to CSS stylesheets, that only decorate a document, not transforming it. http://feeds2.feedburner.com/jasonle/ubfs http://www.blogger.com/styles/atom.css Ignore this *intended* message. It is meant to confuse you.

This is an Atom formatted XML site feed. It is intended to be viewed in a Newsreader or syndicated to another site. Please visit Blogger Help for more info.

Try my Greasemonkey extension with one of the pages which I have sent to you, including that "Government News" page with a missing stylesheet. https://greasyfork.org/en/scripts/465932-newspaper

[erosman]

Above pages are standard HTML when viewed in a browser.

As mentioned, when viewed with a browser, they show as HTML. Userscript managers run in a browser.

Nonetheless, userscript managers only inject the script (or style) and can inject any script/style. The rest is handled by the browser.

[sjehuda]

(4) Misconfigured stylesheet. Interestingly, the stylesheet of gpl-violations.org lacks the namespace "http://www.w3.org/2005/Atom", so it *does not* detect any XML node of "atom". https://gpl-violations.org/news/index.atom https://gpl-violations.org/assets/xml/atom.xsl This is also a relevant scenario.

[sjehuda]

As mentioned, when viewed with a browser, they show as HTML. Userscript managers run in a browser.

They show as HTML, because my stylesheet is set to transform it to HTML, because the purpose of my publication platform is to be also viewed via HTML/HTTP clients. Some stylesheets may transform XML documents to Text or to another XML, and not to HTML.

Nonetheless, userscript managers only inject the script (or style) and can inject any script/style. The rest is handled by the browser.

Yes. I realize that. However, you can utilize SaxonJS or this XSLT Processor, and do what Greasemonkey does to ECMAScript, to XSLT, also. Would that proposal of mine be relevant to you, the developer of FireMonkey, if those supposed standard browsers would not have XSLT interpreters installed?

[erosman]

New features depend on users' demand. If there is a popular demand, it can be looked into.

[sjehuda]

Fine. Do note, that some may not comprehend that idea, because due to the deliberate sabotages and malpractices towards XSLT, in recent years, lesser people are aware of the existence of a standard specification which is meant to transform documents, which is not exclusive to ECMAScript. So, I would be glad to have your consideration to that fact of deliberate sabotage and malpractice. @erosman Thank you for participating in this discussion. Other extension developers are welcome to comment, and even more welcome to agree to that proposed integration, and I would gladly help with testing, and, perhaps, also with development and integration of XSLT.