Description of problem:
This might be a regression - I thought this was fixed at some point - but I'm seeing it rear its ugly head (again).

Some notifications are rendering garbage when trying to display multibyte characters.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create a new org called 你好.
2. Refresh orgs page (to assure it's actually there)
3. Attempt to delete
  
Actual results:
404 Resource Not Found: {"displayMessage":"owner with key: ä½ å¥½ was not found."}

Expected results:

404 Resource Not Found: {"displayMessage":"owner with key: 你好 was not found."}
Generally speaking, notifications should be unicode-friendly.

Additional info:

I am going to make this block bug #709813 because I don't currently know of another way to test such a scenario. But we should try to get this fixed once and for all, across the notifications code.

if I find this to actually be a dupe (i.e., the other was never fixed) i will close it.