On Mon, 9 Mar 2026 11:26:09 -0000
"David Carlisle d.p.carlisle@xxxxxxxxx"
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

>  On 09/03/2026 11:12, Schimon Jehudah sch@xxxxxxxxxxxx wrote:
> 
> David. Which MIME-Type should servers send so that this document
> would be realized properly? Schimon
> 
> I just used the filesystem so saved it as foo.xml but on a server it
> can have any name as long as you send it with a suitable mime type
> such as text/xml or application/xml see for example xml+
> https://www.w3.org/TR/xhtml-media-types/
> 
> 
> If you use the filesystem and save the file as foo.html then
> naturally the browser will use the html parser, in which xhtml:p is
> just an unknown element.
> 

Yes. I am aware of the realization of XHTML document from the local
file system by setting the file extension to "xhtml".

However, it does not work with the produced document.

https://invent.kde.org/shibe/pubsub/-/blob/adee0e06ee0fa94d3efb78cec8cc8b27a3d8cb2d/pubsub.cgi

For record. The MIME-Type sent is "application/pubsub+xml".

MIME-Type "application/xml" works the same as application/pubsub+xml",
and application/xhtml+xml will display the whole text at a single and
wrapped line.

Since XSLT 3.0 does the required task, I am not concerned, any more, as
the Python version of the CGI script of Chawan could be utilized with
realization of XML prefixes (i.e. "pubsub:pubsub" and "atom:entry"),
for both productive and learning purposes.

I thank you, all, for your participation, observations, and advisory.

Schimon