This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29593 - [FO31] search terms
Summary: [FO31] search terms
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL: https://www.w3.org/TR/xpath-functions...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-25 11:14 UTC by Tim Mills
Modified: 2016-07-21 15:09 UTC (History)
1 user (show)

See Also:

Attachments

Description Tim Mills 2016-04-25 11:14:25 UTC 
In the text of 5.3.3 The Unicode Collation Algorithm, I found the use of the phrase "search term" in two of the definitions surprising.  

backwards	yes | no	The value backwards=yes indicates that the last accent in the search term is the most significant.

normalization	yes | no	Indicates whether search terms are converted to normalization form D.
Comment 1 Michael Kay 2016-04-26 13:30:20 UTC 
Reading the current text I note also that the character encoding problem (introduced when the text was migrated from XSLT3.0 to F&O3.1) has not been fixed: for example "Â=â but â!=a." See the XSLT 3.0 spec for the correct reading.

Also the references to Unicode TR35 could more precisely be to part 5

UNICODE LOCALE DATA MARKUP LANGUAGE (LDML) PART 5: COLLATION

I think the descriptions were originally taken from TR35, but they have changed in later versions of TR35, which no longer uses the term "search term". I think the phrase can be replaced by "string(s) to be sorted".
Comment 2 Andrew Coleman 2016-05-06 09:51:21 UTC 
At the meeting on 2016-05-03, the WG agreed to make this editorial change.  Action A-642-03 raised to track this.
Comment 3 Michael Kay 2016-07-21 15:09:07 UTC 
Confirmed that the change was made.