4 May
2015
4 May
'15
1:31 a.m.
I don't think it's fair to blame the digesting process. GIGO applies. There are (mostly ignored) standards for encoding non-ascii content such that at least in principle it can be correctly interpreted. Even if the unusual character codes made it through the program chain intact, the endpoint that displays them would have no clue what to do with them. In fact, I'll give even odds that that is exactly what's happening - the digest contains an unusual ascii code, and the program being used to display the message shows you a ?