I'd just check, if the encoding of the mail is set correctly. If the client does not support unicode at all, you're out of luck anyway, because users could include all other sorts of unicode chars (for which no html-entity exists)
you could of course implement a way to convert the chars to their html-entities (XSLT?), but since would only be a partial solution it may not be worth the effort. maybe you could use another editor that can keep the entites. these links might be helpful for you: * http://sourceforge.net/projects/xmlchar/ * http://martin-trummer.blogspot.com/2009/11/wysiwyg-gotchas.html On 12 Jan., 16:13, DCYorke <d...@yorkemail.org> wrote: > We're using RichTextArea to compose emails. The problem seems to be > that some email clients aren't seeing the characters correctly. So © > shows up as a ?, but © shows up correctly. > > On Jan 12, 3:50 am, Martin Trummer <martin.trum...@24act.at> wrote: > > > I just wonder, why you would want to do that? > > what's wrong with the unicode chars? > > > On 11 Jan., 20:03, DCYorke <d...@yorkemail.org> wrote: > > > > When setting HTML to a RichTextArea, some HTML entities are converted > > > to unicode. For instance, « is converted to «, © is > > > converted to © and so forth. The problem seems to originate in the > > > innerHTML property that is used by RichTextArea. Anyone know of a > > > workaround such that when I call getHTML() on the RichTextArea the > > > HTML entities are included instead of the unicode? Thanks in advance. > > > > DCYorke > >
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
