Comment 8 for bug 886466

This is a weird issue, since the byte 0xc2 would be "Â" in utf8 and I don't see where this comes from.

You could try dissecting the string on line 67 and 68 to find exactly the part that causes this issue.