a part of the fixes targets invalid XML where parenthesis are used as xml:id values. that makes it impossible for strict XML processors to load the affected document.
some Windows OS-based editors seem to been used as one URL ended with a LF entitity which is unexpected and depending on the client code / used URL parser might lead to problems.
there are also several occurances of 
 (CR) in change records without any semantical significance, certainly stemming from the Windows editor world, and possibly an annoyance for users. let me know if i should amend an removal of these as well.
a part of the fixes targets invalid XML where parenthesis are used as xml:id values. that makes it impossible for strict XML processors to load the affected document.
some Windows OS-based editors seem to been used as one URL ended with a LF entitity which is unexpected and depending on the client code / used URL parser might lead to problems.
there are also several occurances of

(CR) in change records without any semantical significance, certainly stemming from the Windows editor world, and possibly an annoyance for users. let me know if i should amend an removal of these as well.