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 3168 - fn-codepoint-equal-17 and fn-codepoint-equal-14 have invalid baselines
Summary: fn-codepoint-equal-17 and fn-codepoint-equal-14 have invalid baselines
Status: CLOSED DUPLICATE of bug 3132
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: 0.9.0
Hardware: Other Linux
: P2 normal
Target Milestone: ---
Assignee: Carmelo Montanez
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-30 22:52 UTC by Frans Englich
Modified: 2006-07-05 19:50 UTC (History)
0 users

See Also:

Attachments

Description Frans Englich 2006-04-30 22:52:56 UTC 
I'm really trying to understand these tests:

* fn-codepoint-equal-14's query is fn:codepoint-equal("aa",fn:upper-case("aa")), and has a baseline containing 'true. I don't see how "aa" and "AA" is considered equal on a codepoint basis. Contrast to fn-codepoint-equal-12, for example.

*fn-codepoint-equal-14's query is 'fn:codepoint-equal("aa","aa") and fn:false()', and has a baseline containing "true". Since one of the operands always is false, I think this should always evaluate to false.


Regards,
Frans
Comment 1 Carmelo Montanez 2006-05-01 14:00:09 UTC 
Hey Frans:

Thanks for the comment.  This was also commented on two otehr bugs,
3154 and 3132.  The corerct results wew submitted.

Thanks,
Carmelo

*** This bug has been marked as a duplicate of 3132 ***