>Yep look like the patch file is not UTF8 encoded? Yeh, its not actually encoded at all. If it were, I would expect to see:
utf32 - 0x000000F3 utf16 - 0x00F3 utf8 - 0xC3 0xB3 So, is it coming out of github's character patch generation code that way directly? If so, we could write a bit of code with some regex to fix. Mike
