Change where utf-8 encode is done, refines earlier fix

Refined an earlier fix for a unicode error.  Moved the .encode(...) to a different function (when the string is generated) instead of doing it in the notification, seems having it there causes a problem when non-english language strings are passed through? Not 100% sure, but it does fix both instances now.

Fixes #138