Last modified: 2009-01-14 21:23:57 UTC
See url. The file contains a bare 0x0F character on the title field which is passed untranslated through the API to the user as XML. It would be bad if this were an invalid unicode char, but being < 32, per http://www.w3.org/TR/REC-xml/#charsets its presence makes the full api result not well-formed, choking XML parsers on it. Related to bug 15261, bug 16105.
Should be fixed in r45749: 0x0F is invalid UTF-8 and converted to the UTF-8 replacement character (U+FFFD).