W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2013

[Bug 20674] [XT3TS] result-document-0202 and others

From: <bugzilla@jessica.w3.org>
Date: Tue, 15 Jan 2013 22:05:11 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-20674-523-ITA4Vigxk9@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20674

--- Comment #2 from Tim Mills <tim@cbcl.co.uk> ---
We do byte-by-byte comparison of the serialised result against the expected
result.  To get around the problem, we serialise the result both with \n and
\r\n and try the comparison with each.

Is it safe to replace a 13 10 byte sequence with 10 without reference to the
text encoding, or would we have to use the output encoding to decode the byte
stream, do the character replacement, then re-encode to a byte stream?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 15 January 2013 22:05:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 January 2013 22:05:12 GMT