Saxon » SaxonJS

The Saxon-JS code for handling collations has had a lot of work since the 1.0.0 release. This includes addressing the problems raised in this bug:

1. The "comparer" objects (which have compare and equals methods) used for value comparisons and general comparisons now check for a specified collation, using the codepoint collation as default.

2. The codepointCollation.equals() method has been updated as suggested.

Also, "collation" objects now have a standard format, and can be supplied to the SaxonJS.transform() call using the "collations" option. This takes a map (JS object) from collation URIs to collations. A collation is an object with certain methods (where the arguments are JS strings): equals (mandatory), compare, collationKey, contains, startsWith, endsWith, and indexOf.

The following collations are now implemented in Saxon-JS: unicode codepoint collation (http://www.w3.org/2005/xpath-functions/collation/codepoint), and the HTML ASCII case-insensitive collation (http://www.w3.org/2005/xpath-functions/collation/html-ascii-case-insensitive).

The use of Unicode Collation Algorithm collations (those beginning http://www.w3.org/2013/collation/UCA) is not yet implemented. Currently if one of these collations is specified, then Saxon-JS always just uses the default codepoint collation.

The documentation needs to be updated with the above information for the next release.

Committed changes on the 2.0 trunk branch to implement support for UCA collations as suggested above (including when lang="XX" is specified in xsl:sort, see change in Compare.sortKeyProps ).

When the only query parameter used in a UCA collation URI is "strength=secondary" (or "strength=2"), then a full caseblind collation is used (Compare.caseblind), to support contains, startsWith, etc. as well as equals and compare.

Otherwise, the collation object uses Intl.Collator, and so only supports equals and compare (so has restricted use as described above).

Details for handling strength parameter:

• primary|1 => sensitivity: "base"
• secondary|2 => sensitivity: "accent"
• tertiary|3 => sensitivity: "variant"
• quaternary|4|identical|5 => sensitivity: "variant", ignorePunctuation: "false"

The following query parameters are ignored: version, maxVariable, backwards, normalization, caseLevel, reorder; and alternate is only supported if alternate=blanked.

I think we can now close this as done.