Email Express WYSIWYG styling to body content adds garbage characters

Mike Infranco

When bolding, italicizing or underlining body text within email express extra garbage characters are added on both sides of the selected content. According to convio this is a known bug with no work arounds and no current solution. Is that accurate?

Cheryl Muschallik

I'm experiencing an issue where "?" marks are seemingly randomly being inserted into my code, though I am not using the WYSIWYG. Support has not associated my issue with a bug but maybe this is the same problem?

Jesse Kelsey

A couple of things to consider:



1) Never use a WYSIWYG editor if you can avoid it. If you can't avoid it, hopefully there is a 'source' or 'html' option so that you can edit HTML entities directly. Some WYSIWYG editors still manage to add characters, which is what might be happening in these cases.



2) I've encountered hidden characters or 'gremlims' when attempting to copy/paste from Word, Photoshop or other applications. You might want to try to 'zap the gremlins' first in a plain text editor. TextWrangler has a feature for this. I'm sure there are other text editors that can remove hidden characters. Photoshop, especially, adds question marks if copy/pasting from Photoshop to a WYSIWYG or HTML editor.



-Jesse

Brian Mucha

Totally! You can disable WYSIYG for yourself in your Luminate Administrator Prefs, which you get to by clicking your name in the masthead.



I also agree Word is a big one for adding special characters. It automatically converts primes (') for quotes (’), n-dashes for hyphens and stuff like that.

 

Mike Infranco

Actually, the whole point of using the WYSIWYG is so that non-technical users can effectively use the Email Express tool to send their own emails. The special characters are showing up when you click on the formatting buttons (bold, etc); I am not referring to pasting from Word.



This bug (which Support has acknowledged as one) makes me question Email Express' use as a tool. It's distressing that BB has no workaround, and no ETA on fixing the bug.