Issue #33 - Apprise notification line break

[Emmo213]

Adding a line break for email notifications never worked for me. After some troubleshooting what I discovered was that when the settings form is submitted PHP will urlencode the parameters and when we access those parameters using _GET it does a urldecode, but for some reason certain characters aren't decoded properly. I don't know if it's a PHP bug or something else, but by base64 encoding the values when the form is submitted the setting values remain intact.

For email I've been using <br/> for a line break, but suspect others who are using /r/n or /n are having the same issue.

While personally I only needed this for the notification body I did it for the title too in case that's helpful for somebody else.

This change works with the actual notification but not with the current test notification. Not included in this pull request, it's always bothered me that sending a test notification and sending an actual notification used two different sets of code. That's why, as mentioned in issue #33, the test notification with a line break would succeed but the actual notification would fail, and why this fix works with the actual notification but not with the current test notification. I'm looking at combining those two code bases in a separate pull request.

Edit: the change to use the same code base for both regular and test notifications is PR #174 .

[Emmo213]

It's been a month with no discussion. Should I close this PR as unwanted?

[Nachtzuster]

I'd like to keep the config file human readable, so encoding is a no-go