Re: [ANN] Saxon 11.1

--===============5844371309887979708==
Content-Type: multipart/alternative; boundary="000000000000b1d20105d71e1b06"

--000000000000b1d20105d71e1b06
Content-Type: text/plain; charset="UTF-8"

Congratulations to the Complete Team for this Great work!

On Wed, 2 Feb 2022 at 15:41, Michael Kay <mike-JkSD5nQpfvpWk0Htik3J/[email protected]> wrote:

> We are delighted to announce Saxon 11.1, a raft of new 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
> www.saxonica.com) though a few corners of the website have yet to be
> updated.
>
> For SaxonJ (Java), this is the first major release in nearly two years.
> There'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 us
> feedback.
>
> * A new framework for resolving URIs that refer to external resources,
> integrating 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
> libraries.
>
> * 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 also improves speed and reduces memory requirements for many string
> handling operations. The effect is not uniform however; for very simple
> transformations 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
> localisation (in particular, running on machines whose default Culture
> setting is not English). For a full list of fixed bugs, please go to
> https://saxonica.plan.io/projects/saxon/issues and filter the list of
> bugs for those labelled as "fixed in maintenance release 11.1". In addition
> to bug fixes, there are some functional changes:
>
>   * 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.XmlResolver interface has been largely discontinued, except
> where needed for interoperation with the Microsoft parser, because of its
> inflexibility in handling different kinds of resources.
>
>   * A few new API methods are implemented to plug gaps, in response to
> user feedback
>
>   * XQuery Update is fully supported (in 11.0 the code was present but
> largely untested).
>
> SaxonCS on Mac is still awaiting notarization from Apple; until that's
> achieved there may be security warnings when you download it.
>
> For SaxonC (C++, Python, and PHP, on Windows, Mac, and Linux) this is the
> first release since 2019.
>
> * The Java code base has moved forward from 9.9 to 11.1, and the build
> process is now integrated with SaxonJ and SaxonCS so that bug fixes can be
> applied 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,
> reducing 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/
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/saxon-help
>


-- 
Vishnu Singh | http://marklogicgd.blogspot.com/
<http://marklogicgd.blogspot.in/>

--000000000000b1d20105d71e1b06
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Congratulations to the Complete Team for this Great work!<=
/div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">O=
n Wed, 2 Feb 2022 at 15:41, Michael Kay &lt;<a href=3D"mailto:mike@saxonica=
.com">mike-JkSD5nQpfvpWk0Htik3J/[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">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" rel=3D"noreferrer=
" target=3D"_blank">www.saxonica.com</a>) though a few corners of the websi=
te have yet to be updated.<br>
<br>
For SaxonJ (Java), this is the first major release in nearly two years. The=
re&#39;s a long list of detailed changes that you can find in the documenta=
tion, 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&#39;s a set of classes for handling Unicode strings. The =
main motivation for this was to allow common code across Java and C#, but i=
t also improves speed and reduces memory requirements for many string handl=
ing operations. The effect is not uniform however; for very simple transfor=
mations of documents consisting exclusively of ASCII text, there is general=
ly a memory saving but a small overhead in 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"h=
ttps://saxonica.plan.io/projects/saxon/issues" rel=3D"noreferrer" target=3D=
"_blank">https://saxonica.plan.io/projects/saxon/issues</a> and filter the =
list of bugs for those labelled as &quot;fixed in maintenance release 11.1&=
quot;. In addition to bug fixes, there are some functional changes:<br>
<br>
=C2=A0 * 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.XmlResolver interface has been largely discontinued, except where need=
ed for interoperation with the Microsoft parser, because of its inflexibili=
ty in handling different kinds of resources.<br>
<br>
=C2=A0 * A few new API methods are implemented to plug gaps, in response to=
 user feedback<br>
<br>
=C2=A0 * XQuery Update is fully supported (in 11.0 the code was present but=
 largely untested).<br>
<br>
SaxonCS on Mac is still awaiting notarization from Apple; until that&#39;s =
achieved 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/" =
rel=3D"noreferrer" target=3D"_blank">http://saxon.markmail.org/</a><br>
<a href=3D"mailto:[email protected]" target=3D"_blank">saxon=
[email protected]</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/saxon-help" rel=3D"=
noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/=
saxon-help</a> <br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><div dir=3D"ltr"><div>Vishnu Singh |=C2=A0<a hre=
f=3D"http://marklogicgd.blogspot.in/" target=3D"_blank">http://marklogicgd.=
blogspot.com/</a></div><div><br></div></div></div>

--000000000000b1d20105d71e1b06--


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


--===============5844371309887979708==
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 
--===============5844371309887979708==--