In all of the following test cases my implementation is generating more eol characters than exist in the expected results:

complex-deletes-q1-combined-2
complex-deletes-q2-combined-2
complex-deletes-q4-combined-2
complex-deletes-q4-combined-3
complex-deletes-q5-combined-2
complex-deletes-q5-combined-3
complex-deletes-q6-combined-2
complex-deletes-q8-combined-2
complex-deletes-q9-combined-2
complex-deletes-q10-combined-2
complex-deletes-q10-combined-3
complex-deletes-q11-combined-2
complex-deletes-q12-combined-2
complex-deletes-q13-combined-2
complex-replacevalues-q1-combined-2
complex-replacevalues-q2-combined-2
complex-replacevalues-q4-combined-2
complex-replacevalues-q4-combined-3
complex-replacevalues-q5-combined-2
complex-replacevalues-q6-combined-2
complex-replacevalues-q8-combined-2
complex-replacevalues-q9-combined-2
complex-replacevalues-q10-combined-2
complex-replacevalues-q12-combined-2
complex-replacevalues-q13-combined-2
complex-replacevalues-q14-combined-2
complex-renames-q2-combined-2
complex-renames-q3-combined-2
complex-renames-q4-combined-2
complex-renames-q5-combined-2
complex-renames-q5-combined-3
complex-renames-q6-combined-2
complex-renames-q8-combined-2

It appears that the source file TopMany.xml, used in all of these test cases, contains more eol characters than it does in its XQTS incarnation. When I use the XQTS version of this source file, all of these errors except complex-deletes-q1-combined-2 and complex-deletes-q2-combined-2 disappear.

I'm going to be presumptive and replace TopMany.xml with its XQTS version in CVS. John, if you agree with this change, then please close this bug and I'll follow up on these two remaining test cases.