- From: <bugzilla@jessica.w3.org>
- Date: Fri, 23 Sep 2016 08:59:02 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29865 Bug ID: 29865 Summary: [FO31] UCA collation in substring matching Product: XPath / XQuery / XSLT Version: Candidate Recommendation Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Functions and Operators 3.1 Assignee: mike@saxonica.com Reporter: mike@saxonica.com QA Contact: public-qt-comments@w3.org Target Milestone: --- We say on the one hand: All implementations must recognize URIs in this family [UCA collations] in the collation argument of functions that take a collation argument. and on the other It is possible to define collations that do not have the ability to decompose a string into units suitable for substring matching. An argument to a function defined in this section may be a URI that identifies a collation that is able to compare two strings, but that does not have the capability to split the string into collation units. Such a collation may cause the function to fail, or to give unexpected results or it may be rejected as an unsuitable argument. The ability to decompose strings into collation units is an ·implementation-defined· property of the collation. I think we should be explicit (unless there is a technical reason to the contrary) that the UCA family of collations can be used for substring matching. I have added some tests to contains(), starts-with(), and ends-with() to use UCA collations. Saxon fails on these tests, but I think that's an implementation shortcoming. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 23 September 2016 08:59:52 UTC