id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
1	non-ASCII characters in darcs output cause a crash	warner	somebody	"'ndurner' noticed darcsver crashing, due to a non-ascii character in the
output of 'darcs changes --xml-format'. It looks like the german windows
machine emitted a 'local_date' attribute with a long timezone name, something
like ""Westeuropaische Normalzeit"", except using an a-with-umlaut in the first
word. It looks like the name was encoded with Latin-1.

darcsver has a hack to discard funny-looking characters before it passes the
string to the XML parser, because apparently it's awfully hard to get darcs
to declare a character encoding for its XML output, or for darcs to stick to
that encoding (the local_date string is probably coming from some windows
time/date library, and who knows how to control the encoding *that* uses).
But the hack doesn't discard enough.

My suggestion is to discard everything that isn't ASCII:
{{{
allbadchars = """".join([chr(i) for i in range(0x20) + range(0x7f,0x100)])
tt = string.maketrans(allbadchars, ""?""*len(allbadchars))
}}}

(really, we could probably discard everything that isn't an angle bracket or
the word ""patch"", since all darcsver really cares about is how many
{{{<patch???}}} tokens appear in the file)
"	defect	closed	major		component1		fixed