Learn About Problem Characters Here...
Note that at least one special character, the apostrophe, will not translate properly - it comes out as backslash-apostrophe (\'), and each time you go back and edit the message, more \ will be added. For a work-around, type the ampersand character (&) and the characters #039; with no spaces and you will see an ' in the output message and you'll be all set (sorry, if I just type out & and #039; here without spaces, all you will see is an apostrophe!). This only works the first time through the message creation process - if you go back to edit, then the apostrophe you created by typing & and #039; will be detected as an apostrophe and marked out with a backslash again. So if you really need to go back and edit, just edit out the apostrophes that have been created from & and #039; in the first pass, and replace with the work-around again. (Duh, sorry, I'll try to work on this explanation when I get a chance, it sounds so circular!) Or, of course, you can avoid the whole thing by avoiding the apostrophe to begin with - "that's" becomes "that is", etc.
Any other special characters will be listed here as we identify them - there surely will be more.
These problems with special characters happen because of all the program processing that it takes to turn your simple input text into HTML and move it to your Web page. The special characters of course have another meaning in various program languages and that is why they get tagged with the backslash (to set them aside in the program as not being part of the internal program command codes. It's the price paid for using a simple shortcut tool like WebMsgNow instead of actually working in the native HTML and other Web languages.