Re: [ANN] Saxon 11.1

--===============4624127592465764674==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_MN2PR12MB3821680AC4C44C19BE48AF7DD7279MN2PR12MB3821namp_"

--_000_MN2PR12MB3821680AC4C44C19BE48AF7DD7279MN2PR12MB3821namp_
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

Congratulations! Sounds wonderful, particularly "A otherwise B".

Marcos Sueiro

From: Michael Kay <mike-JkSD5nQpfvpWk0Htik3J/[email protected]>
Sent: Wednesday, February 2, 2022 4:51 AM
To: Mailing list for the SAXON XSLT and XQuery processor <saxon-help@lists.=
sourceforge.net>
Subject: [saxon] [ANN] Saxon 11.1

We are delighted to announce Saxon 11.1, a raft of new products covering th=
ree language platforms (SaxonJ, SaxonCS, and SaxonC), all built from the sa=
me source code. The software can be downloaded from the usual places (see w=
ww.saxonica.com<http://www.saxonica.com>) though a few corners of the websi=
te have yet to be updated.

For SaxonJ (Java), this is the first major release in nearly two years. The=
re's a long list of detailed changes that you can find in the documentation=
, but the main highlights are:

* New functions and syntax extensions, some of them experimental. Some are =
very simple, for example, "A otherwise B" selects A if it exists, otherwise=
 it selects B. Some are more complex and powerful, such as the saxon:update=
 and saxon:deep-update instructions in XSLT. Please try them out and give u=
s feedback.

* A new framework for resolving URIs that refer to external resources, inte=
grating catalog-based resolution where appropriate.

* Most callbacks are now provided via functional interfaces, allowing them =
to be easily written as lambda expressions.

* Timezone handling has moved forward to the modern Java date/time librarie=
s.

* Numerous minor changes to make JSON processing easier

Internally, there's a set of classes for handling Unicode strings. The main=
 motivation for this was to allow common code across Java and C#, but it al=
so improves speed and reduces memory requirements for many string handling =
operations. The effect is not uniform however; for very simple transformati=
ons of documents consisting exclusively of ASCII text, there is generally a=
 memory saving but a small overhead in processing time.

For SaxonCS (.NET 5 and 6 on Windows, Mac, and Linux), this is essentially =
a bug-fixing release for 11.0. The most important issues fixed relate to lo=
calisation (in particular, running on machines whose default Culture settin=
g is not English). For a full list of fixed bugs, please go to https://saxo=
nica.plan.io/projects/saxon/issues<https://saxonica.plan.io/projects/saxon/=
issues> and filter the list of bugs for those labelled as "fixed in mainten=
ance release 11.1". In addition to bug fixes, there are some functional cha=
nges:

* As with SaxonJ, there is a new framework for resolving URIs, based on the=
 C# version of the catalog-based xml resolver. The use of the System.Xml.Xm=
lResolver interface has been largely discontinued, except where needed for =
interoperation with the Microsoft parser, because of its inflexibility in h=
andling different kinds of resources.

* A few new API methods are implemented to plug gaps, in response to user f=
eedback

* XQuery Update is fully supported (in 11.0 the code was present but largel=
y untested).

SaxonCS on Mac is still awaiting notarization from Apple; until that's achi=
eved there may be security warnings when you download it.

For SaxonC (C++, Python, and PHP, on Windows, Mac, and Linux) this is the f=
irst release since 2019.

* The Java code base has moved forward from 9.9 to 11.1, and the build proc=
ess is now integrated with SaxonJ and SaxonCS so that bug fixes can be appl=
ied simultaneously to all three products.

* There are improvements in multi-threading, when multiple transformations =
using the same stylesheet are executed in parallel in a web server

* Memory management of XDM objects is improved

* Localization (using ICU-J) is improved

* Handling of Unicode strings in the various language APIs is improved, red=
ucing the scope for encoding issues.

* There are many API extensions and improvements for all three languages (C=
++, Python, and PHP)

Michael Kay
Saxonica

_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/<http://saxon=
.markmail.org>
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/saxon-help<https://lists.sourc=
eforge.net/lists/listinfo/saxon-help>

--_000_MN2PR12MB3821680AC4C44C19BE48AF7DD7279MN2PR12MB3821namp_
Content-Type: text/html; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
=09{font-family:"Cambria Math";
=09panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
=09{font-family:Calibri;
=09panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
=09{margin:0in;
=09font-size:11.0pt;
=09font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
=09{mso-style-priority:99;
=09color:blue;
=09text-decoration:underline;}
span.EmailStyle19
=09{mso-style-type:personal-reply;
=09font-family:"Calibri",sans-serif;
=09color:windowtext;}
.MsoChpDefault
=09{mso-style-type:export-only;
=09font-size:10.0pt;}
@page WordSection1
=09{size:8.5in 11.0in;
=09margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
=09{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:brea=
k-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Congratulations! Sounds wonderful, particularly &quo=
t;A otherwise B&quot;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Marcos Sueiro<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Michael Kay &lt;mike-JkSD5nQpfvpWk0Htik3J/[email protected]&gt; <=
br>
<b>Sent:</b> Wednesday, February 2, 2022 4:51 AM<br>
<b>To:</b> Mailing list for the SAXON XSLT and XQuery processor &lt;saxon-h=
[email protected]&gt;<br>
<b>Subject:</b> [saxon] [ANN] Saxon 11.1<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We are delighted to announce Saxon 11.1, a raft of n=
ew products covering three language platforms (SaxonJ, SaxonCS, and SaxonC)=
, all built from the same source code. The software can be downloaded from =
the usual places (see
<a href=3D"http://www.saxonica.com">
www.saxonica.com</a>) though a few corners of the website have yet to be up=
dated.<br>
<br>
For SaxonJ (Java), this is the first major release in nearly two years. The=
re's a long list of detailed changes that you can find in the documentation=
, but the main highlights are:<br>
<br>
* New functions and syntax extensions, some of them experimental. Some are =
very simple, for example, &quot;A otherwise B&quot; selects A if it exists,=
 otherwise it selects B. Some are more complex and powerful, such as the sa=
xon:update and saxon:deep-update instructions
 in XSLT. Please try them out and give us feedback.<br>
<br>
* A new framework for resolving URIs that refer to external resources, inte=
grating catalog-based resolution where appropriate.<br>
<br>
* Most callbacks are now provided via functional interfaces, allowing them =
to be easily written as lambda expressions.<br>
<br>
* Timezone handling has moved forward to the modern Java date/time librarie=
s.<br>
<br>
* Numerous minor changes to make JSON processing easier<br>
<br>
Internally, there's a set of classes for handling Unicode strings. The main=
 motivation for this was to allow common code across Java and C#, but it al=
so improves speed and reduces memory requirements for many string handling =
operations. The effect is not uniform
 however; for very simple transformations of documents consisting exclusive=
ly of ASCII text, there is generally a memory saving but a small overhead i=
n processing time.<br>
<br>
For SaxonCS (.NET 5 and 6 on Windows, Mac, and Linux), this is essentially =
a bug-fixing release for 11.0. The most important issues fixed relate to lo=
calisation (in particular, running on machines whose default Culture settin=
g is not English). For a full list
 of fixed bugs, please go to <a href=3D"https://saxonica.plan.io/projects/s=
axon/issues">
https://saxonica.plan.io/projects/saxon/issues</a> and filter the list of b=
ugs for those labelled as &quot;fixed in maintenance release 11.1&quot;. In=
 addition to bug fixes, there are some functional changes:<br>
<br>
* As with SaxonJ, there is a new framework for resolving URIs, based on the=
 C# version of the catalog-based xml resolver. The use of the System.Xml.Xm=
lResolver interface has been largely discontinued, except where needed for =
interoperation with the Microsoft
 parser, because of its inflexibility in handling different kinds of resour=
ces.<br>
<br>
* A few new API methods are implemented to plug gaps, in response to user f=
eedback<br>
<br>
* XQuery Update is fully supported (in 11.0 the code was present but largel=
y untested).<br>
<br>
SaxonCS on Mac is still awaiting notarization from Apple; until that's achi=
eved there may be security warnings when you download it.<br>
<br>
For SaxonC (C++, Python, and PHP, on Windows, Mac, and Linux) this is the f=
irst release since 2019.<br>
<br>
* The Java code base has moved forward from 9.9 to 11.1, and the build proc=
ess is now integrated with SaxonJ and SaxonCS so that bug fixes can be appl=
ied simultaneously to all three products.<br>
<br>
* There are improvements in multi-threading, when multiple transformations =
using the same stylesheet are executed in parallel in a web server<br>
<br>
* Memory management of XDM objects is improved<br>
<br>
* Localization (using ICU-J) is improved<br>
<br>
* Handling of Unicode strings in the various language APIs is improved, red=
ucing the scope for encoding issues.<br>
<br>
* There are many API extensions and improvements for all three languages (C=
++, Python, and PHP)<br>
<br>
Michael Kay<br>
Saxonica<br>
<br>
_______________________________________________<br>
saxon-help mailing list archived at <a href=3D"http://saxon.markmail.org">
http://saxon.markmail.org/</a><br>
<a href=3D"mailto:[email protected]">[email protected]=
forge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/saxon-help">https:/=
/lists.sourceforge.net/lists/listinfo/saxon-help</a>
<o:p></o:p></p>
</div>
</body>
</html>

--_000_MN2PR12MB3821680AC4C44C19BE48AF7DD7279MN2PR12MB3821namp_--



--===============4624127592465764674==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============4624127592465764674==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
[email protected]
https://lists.sourceforge.net/lists/listinfo/saxon-help 
--===============4624127592465764674==--