Comment 1 for bug 1605473

This is a known issue - believe there is another report open as well.

Problem is that I don't know upfront how the browser will handle UTF8, so we assume an encoding standard, but can still be wrong.

Probably needs patch that is different per browser used.