This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
It appears that whitespace has been changed in the serialization-matches assertions for character-map-013 and character-map-017 which affect the meaning of the assertions.
Similarly for normalize-unicode-014 normalize-unicode-015 normalize-unicode-017 normalize-unicode-018
Some problems form an erronious reformatting. charcter-map* and normalize-unicode-01[45] corrected and committed. Not sure that this applies to normalize-unicode-01[78]. Will track
normalize-unicode-01[78] problems are caused by switching to a serialization assertion (as indicated by the TODO) which fails. This is because in the reference tests decimal numeric character entities (e.g. ̈) are used, but (at least in our implementation) the results use hex numerics (e.g. ̈) and hence a character-by-character serialization check fails. How (or whether) this can be controlled needs me to investigate. Temporarily these tests have been reverted to use assert-xml
Thanks.
Was resolved > 30 days ago, closing.