ensure that all strings being passed as arguments to the email template ...

...are unicode, and remove encode operations in formcontext
Just wondering - any reason to mask the original error message? (i.e. which char was the problem) Why not just let the exception rise? (maybe we catch ValueError-s somewhere?)

I will merge regardless, we'll see whether it works on test.