XML Module - Revision history

John: /* LPA domain moved from lpa.co.uk to lpai.uk*/

2025-04-27T19:17:06Z

LPA domain moved from lpa.co.uk to lpai.uk

← Older revision		Revision as of 19:17, 27 April 2025
Line 57:		Line 57:
	; The -c option		; The -c option
	: causes prefixes to be removed from attribute names if the explicitly denoted namespace is the same as that of the containing tag (XML input only);		: causes prefixes to be removed from attribute names if the explicitly denoted namespace is the same as that of the containing tag (XML input only);
	Plxml's Prolog output is compatible with [https://www.lpai~~.co~~.uk/ LPA Prolog]. Specifically, strings containing ~ (tilde) characters are output as lists of character codes.		Plxml's Prolog output is compatible with [https://www.lpai.uk/ LPA Prolog]. Specifically, strings containing ~ (tilde) characters are output as lists of character codes.
	=== Using plxml as a development tool ===		=== Using plxml as a development tool ===
	A common use of xml.pl is to populate template XML documents with answers from a Prolog application. A nice approach is to design a prototype document and then translate this into an xml/2 term with plxml.		A common use of xml.pl is to populate template XML documents with answers from a Prolog application. A nice approach is to design a prototype document and then translate this into an xml/2 term with plxml.

John: /* Using plxml.exe */

2025-04-27T19:15:14Z

Using plxml.exe

← Older revision		Revision as of 19:15, 27 April 2025
Line 57:		Line 57:
	; The -c option		; The -c option
	: causes prefixes to be removed from attribute names if the explicitly denoted namespace is the same as that of the containing tag (XML input only);		: causes prefixes to be removed from attribute names if the explicitly denoted namespace is the same as that of the containing tag (XML input only);
	Plxml's Prolog output is compatible with [https://www.~~lpa~~.co.uk/ LPA Prolog]. Specifically, strings containing ~ (tilde) characters are output as lists of character codes.		Plxml's Prolog output is compatible with [https://www.lpai.co.uk/ LPA Prolog]. Specifically, strings containing ~ (tilde) characters are output as lists of character codes.
	=== Using plxml as a development tool ===		=== Using plxml as a development tool ===
	A common use of xml.pl is to populate template XML documents with answers from a Prolog application. A nice approach is to design a prototype document and then translate this into an xml/2 term with plxml.		A common use of xml.pl is to populate template XML documents with answers from a Prolog application. A nice approach is to design a prototype document and then translate this into an xml/2 term with plxml.

John: /* Updating link to HTTPS */

2022-08-02T20:05:50Z

Updating link to HTTPS

← Older revision		Revision as of 20:05, 2 August 2022
Line 62:		Line 62:

	For example, a prototype HTML page could be produced with a WYSIWYG XHTML editor.		For example, a prototype HTML page could be produced with a WYSIWYG XHTML editor.
	Alternatively, if your editor produces plain HTML, you can use plxml in combination with [~~http~~://www.html-tidy.org/ HTML Tidy] e.g.		Alternatively, if your editor produces plain HTML, you can use plxml in combination with [https://www.html-tidy.org/ HTML Tidy] e.g.
	tidy -asxhtml -ascii [HTMLFile] \| plxml - [PLFile]		tidy -asxhtml -ascii [HTMLFile] \| plxml - [PLFile]
	Similarly, during prototyping/early development it may be convenient to use plxml as the interface, rather than integrating xml.pl.		Similarly, during prototyping/early development it may be convenient to use plxml as the interface, rather than integrating xml.pl.

John: /* Link to html-tidy.org */

2022-03-23T22:34:17Z

Link to html-tidy.org

← Older revision		Revision as of 22:34, 23 March 2022
Line 62:		Line 62:

	For example, a prototype HTML page could be produced with a WYSIWYG XHTML editor.		For example, a prototype HTML page could be produced with a WYSIWYG XHTML editor.
	Alternatively, if your editor produces plain HTML, you can use plxml in combination with [http://www.~~htacg~~.org/ HTML Tidy] e.g.		Alternatively, if your editor produces plain HTML, you can use plxml in combination with [http://www.html-tidy.org/ HTML Tidy] e.g.
	tidy -asxhtml -ascii [HTMLFile] \| plxml - [PLFile]		tidy -asxhtml -ascii [HTMLFile] \| plxml - [PLFile]
	Similarly, during prototyping/early development it may be convenient to use plxml as the interface, rather than integrating xml.pl.		Similarly, during prototyping/early development it may be convenient to use plxml as the interface, rather than integrating xml.pl.

John: /* Using plxml.exe */

2020-05-11T22:39:20Z

Using plxml.exe

← Older revision		Revision as of 22:39, 11 May 2020
Line 57:		Line 57:
	; The -c option		; The -c option
	: causes prefixes to be removed from attribute names if the explicitly denoted namespace is the same as that of the containing tag (XML input only);		: causes prefixes to be removed from attribute names if the explicitly denoted namespace is the same as that of the containing tag (XML input only);
	Plxml's Prolog output is compatible with [~~http~~://www.lpa.co.uk/ LPA Prolog]. Specifically, strings containing ~ (tilde) characters are output as lists of character codes.		Plxml's Prolog output is compatible with [https://www.lpa.co.uk/ LPA Prolog]. Specifically, strings containing ~ (tilde) characters are output as lists of character codes.
	=== Using plxml as a development tool ===		=== Using plxml as a development tool ===
	A common use of xml.pl is to populate template XML documents with answers from a Prolog application. A nice approach is to design a prototype document and then translate this into an xml/2 term with plxml.		A common use of xml.pl is to populate template XML documents with answers from a Prolog application. A nice approach is to design a prototype document and then translate this into an xml/2 term with plxml.

John at 23:22, 26 March 2020

2020-03-26T23:22:11Z

← Older revision		Revision as of 23:22, 26 March 2020
Line 73:		Line 73:
	The iso-8859-1, iso-8859-2, iso-8859-15 and windows-1252 8-bit encodings are supported, but they must be identified correctly in the signature of the XML document.		The iso-8859-1, iso-8859-2, iso-8859-15 and windows-1252 8-bit encodings are supported, but they must be identified correctly in the signature of the XML document.

	With the exception of comments and CDATA sections, xml.pl and ~~therefore~~ plxml, output a plain ASCII encoding with the following properties:		With the exception of comments and CDATA sections, xml.pl and plxml output a plain ASCII encoding with the following properties:
	* In all character data, the characters & < and > are encoded as &amp; &lt; and &gt; respectively.		* In all character data, the characters & < and > are encoded as &amp; &lt; and &gt; respectively.
	* In non-parsed character data, such as ''Attribute Values'', the characters " and ' are encoded as &quot; and &apos; respectively.		* In non-parsed character data, such as ''Attribute Values'', the characters " and ' are encoded as &quot; and &apos; respectively.

John: plxml v5.0

2020-03-26T23:19:40Z

plxml v5.0

← Older revision		Revision as of 23:19, 26 March 2020
Line 8:		Line 8:
	<pre>Current Version:		<pre>Current Version:
	XML Module 3.7 released 2014/07/09		XML Module 3.7 released 2014/07/09
	Windows application plxml 4.0 released ~~2016~~/12/27		Windows application plxml 5.0 released 2020/03/27
	</pre>		</pre>
	[https://binding-time.co.uk/download/xmlpl.tar.gz Download the source code] in tar.gz format (21KB)		[https://binding-time.co.uk/download/xmlpl.tar.gz Download the source code] in tar.gz format (21KB)

	[https://binding-time.co.uk/download/xmlpl.zip Download the source code and Windows application] as a ZIP file (~~431KB~~). ''~~Substantial~~ XML ~~input performance improvement~~ in ~~version 4~~.0''.		[https://binding-time.co.uk/download/xmlpl.zip Download the source code and Windows application] as a ZIP file (436KB). ''UTF-8 XML output – supporting non-ASCII Unicode characters in comments and CDATA sections.''

	== Extracting the files ==		== Extracting the files ==
Line 72:		Line 72:
	By default, plxml can accept input encoded as UTF-8 or UTF-16, which encompasses plain 7-bit ASCII.		By default, plxml can accept input encoded as UTF-8 or UTF-16, which encompasses plain 7-bit ASCII.
	The iso-8859-1, iso-8859-2, iso-8859-15 and windows-1252 8-bit encodings are supported, but they must be identified correctly in the signature of the XML document.		The iso-8859-1, iso-8859-2, iso-8859-15 and windows-1252 8-bit encodings are supported, but they must be identified correctly in the signature of the XML document.
	xml.pl~~, (~~and therefore plxml), output a plain ASCII encoding with the following properties:
			With the exception of comments and CDATA sections, xml.pl and therefore plxml, output a plain ASCII encoding with the following properties:
	* In all character data, the characters & < and > are encoded as &amp; &lt; and &gt; respectively.		* In all character data, the characters & < and > are encoded as &amp; &lt; and &gt; respectively.
	* In non-parsed character data, such as ''Attribute Values'', the characters " and ' are encoded as &quot; and &apos; respectively.		* In non-parsed character data, such as ''Attribute Values'', the characters " and ' are encoded as &quot; and &apos; respectively.
	* Any character codes > 127 are output as decimal character entities e.g. 160 as &#160;.		* Any character codes > 127 are output as decimal character entities e.g. 160 as &#160;.
	* Only [https://www.w3.org/TR/xml/#NT-Char character codes allowed by the XML specification] are encoded by xml_parse/[2,3].
			Only [https://www.w3.org/TR/xml/#NT-Char character codes allowed by the XML specification] are encoded by xml_parse/[2,3].

			From version 5.0, plxml XML output is encoded as UTF-8.

John: Updated link to XML specification.

2018-06-20T10:52:38Z

Updated link to XML specification.

← Older revision		Revision as of 10:52, 20 June 2018
Line 76:		Line 76:
	* In non-parsed character data, such as ''Attribute Values'', the characters " and ' are encoded as &quot; and &apos; respectively.		* In non-parsed character data, such as ''Attribute Values'', the characters " and ' are encoded as &quot; and &apos; respectively.
	* Any character codes > 127 are output as decimal character entities e.g. 160 as &#160;.		* Any character codes > 127 are output as decimal character entities e.g. 160 as &#160;.
	* Only [~~http~~://www.w3.org/TR/~~2000~~/~~REC-xml-20001006~~#NT-Char character codes allowed by the XML specification] are encoded by xml_parse/[2,3].		* Only [https://www.w3.org/TR/xml/#NT-Char character codes allowed by the XML specification] are encoded by xml_parse/[2,3].

John: /* Download */

2018-01-13T20:31:58Z

Download

← Older revision	Revision as of 20:31, 13 January 2018
(No difference)

John: /* Using plxml as a development tool */

2017-02-20T13:52:56Z

Using plxml as a development tool

← Older revision		Revision as of 13:52, 20 February 2017
Line 60:		Line 60:
	=== Using plxml as a development tool ===		=== Using plxml as a development tool ===
	A common use of xml.pl is to populate template XML documents with answers from a Prolog application. A nice approach is to design a prototype document and then translate this into an xml/2 term with plxml.		A common use of xml.pl is to populate template XML documents with answers from a Prolog application. A nice approach is to design a prototype document and then translate this into an xml/2 term with plxml.

	For example, a prototype HTML page could be produced with a WYSIWYG XHTML editor.		For example, a prototype HTML page could be produced with a WYSIWYG XHTML editor.
	Alternatively, if your editor produces plain HTML, you can use plxml in combination with [http://www.htacg.org/ HTML Tidy] e.g.		Alternatively, if your editor produces plain HTML, you can use plxml in combination with [http://www.htacg.org/ HTML Tidy] e.g.
	tidy -asxhtml -ascii [HTMLFile] \| plxml - [PLFile]		tidy -asxhtml -ascii [HTMLFile] \| plxml - [PLFile]
	Similarly, during prototyping/early development it may be convenient to use plxml as the interface, rather than integrating xml.pl ~~itself~~.		Similarly, during prototyping/early development it may be convenient to use plxml as the interface, rather than integrating xml.pl.

	=== Using plxml to repair XML ===		=== Using plxml to repair XML ===