Lainaus Jan Schneider <[EMAIL PROTECTED]>: > Zitat von Timo Hamina <[EMAIL PROTECTED]>: > >> Jan Schneider kirjoitti: >>> Zitat von Timo Hamina <[EMAIL PROTECTED]>: >>> >>> >>>> Hey, >>>> I have been testing Horde Groupware Webmail Edition 1.1-RC2 and noticed >>>> a character encoding problem when writing html-mail with FCKeditor as >>>> the message composer (it didn't happen with Xinha). >>>> >>>> The problem occurs if I view that html-message as plain text in my >>>> email-client (Thunderbird, Dimp etc.). Characters like öäå gets messed >>>> up as the there is: >>>> >>>> Content-Type: text/plain; >>>> charset=ISO-8859-1 >>>> >>>> in the mime message. However, the message body seems to be encoded in >>>> utf-8 and that is why those characters gets messed up. >>>> >>>> Actually I checked FCkeditor and that page is in utf-8: >>>> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> >>>> >>>> So there seems to be a encoding mismatch between FCKeditor and Dimps >>>> "message builder". >>>> >>>> P.S. I haven't changed any options or settings, except that I use >>>> FCKeditor as the message composer. >>>> >>> >>> Do you see this in IMP too when using the HTML editor? If yes, then it >>> has been fixed since RC2. >>> >>> Jan. >>> >>> >> I tried sending html-message from imp too, and there it didn't happen. >> Happens only in dimp with fckeditor. > > I can't reproduce this. I see a difference though: FCK converts > non-ascii characters to html entities if possible, Xinha doesn't. But > that doesn't matter because html entities are charset-neutral. > Yes those messages are ok if I view them as html-message, but if I choose to view the message as plain text, those encoding problems occurs. This isn't a big problem since html part of the message displays correctly, but obviously it is a little bug as the plain-text part is in wrong charset.
>> P.S. If I input some non iso-8859-1 characters (for example euro sign, >> EUR) to subject field in dimp, it gets shown as guestion mark (?) in >> any email client I view that message. Seems to be ok on imp, if I choose >> utf-8 encoding for the message. > > This is because you can't (yet) select the sending charset in DIMP. It > uses the default charset, like iso-8859-1 for Finish. But this charset > doesn't contain the euro sign for example. > Ah ok, good to know it will have option to select sending charset (as in IMP). > Jan. Regards, Timo -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [EMAIL PROTECTED]
