OK, sounds good. I really appreciate your work on this. If there's some way I can buy you a coffee, let me know I'm working on putting in a quick filter - just a wrapper for Darcs that sed's out the bad character in question. If I can get that to work, we'll see if the serializer is happy and in turn stops deleting build history on me. If so, it's possible that pushing upstream on the Darcs maintainers could get us a newer version where the character is properly escaped before hitting XML, as it's actually invalid XML to emit like that instead of as an entity.... but there's no entity for it. From one of my colleagues here: "It looks like darcs handling of char 03 is a feature, not a bug. Darcs does not restrict what characters can be used in comments, but can't generate valid XML output if a comment uses an invalid XML character. Apparently, char 03 has no XML representation. is not allowed, because character references must represent valid characters." Not sure I'd call it a feature, but hey. I'll let you know if the wrapper-filter works. |