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 2585 - fn-tokenize-6 escaping
Summary: fn-tokenize-6 escaping
Status: CLOSED FIXED
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: 0.8.2
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Carmelo Montanez
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-12 15:13 UTC by Martin Probst
Modified: 2006-06-22 12:58 UTC (History)
0 users

See Also:

Attachments

Description Martin Probst 2005-12-12 15:13:24 UTC 
fn-tokenize-6 result is escaped, should be "Some unparsed HTML <BR> text", is
"Some unparsed HTML &lt;BR&gt; text"
Comment 1 David Carlisle 2005-12-13 11:36:52 UTC 
(In reply to comment #0)
> fn-tokenize-6 result is escaped, should be "Some unparsed HTML <BR> text", is
> "Some unparsed HTML &lt;BR&gt; text"

The "Text" comparison is pretty confusing but finally it was clarified last time
that it means the same as "Fragment" (see bug #2402) so XML serialisation is
still used, so the < needs to be escaped, and I think the supplied result is
correct.
(Note I'm not on the WG, but I went round this loop with the Text comparison
examples last time round:-)

The Catalog would be greatly improved if a global edit changing compare="Text"
to Compare="Fragment" would be made.

David
Comment 2 Carmelo Montanez 2005-12-16 19:46:11 UTC 
David:

Thanks for the observation.  I will leave the test as is and mark it as fixed.
I will also check on your suggestion of globally changing "Text" to "Fragment.
I think we discussed this, but do not recall what the outcome was.

Thanks,
Carmelo
Comment 3 Martin Probst 2005-12-19 07:45:55 UTC 
For me the major difference at the moment is that Text can be compared without
ignoring whitespace, where most of the Fragment tests are pretty printed. That's
maybe something we should keep?