Tickets :: Comment on [#9532] Ingo Big problem with MIME::encode and accentuated characters

* Your Email Address
* Spam protection	Enter the letters below: .__ . ..__ .___. . \| \\|\ \|[ __[__ \|\ \| \|__/\| \\|[_./[___\| \\|
Comment	> Eventually, after reading RFC 2047 I must recognize that the normal > result of : > $reason = MIME::encode($params['action-value']['reason'], > NLS::getCharset()); is : > "?utf-8?b?w6kg?= =?utf-8?b?w6gg?= =?utf-8?b?w6A=?= " as encoded-words > for "é è ç" characters... > Nevertheless, it seems that MIME::encode is used for encoding the > headers fields but the message himself (here it is "$reason"). Given > I have not this problem with messages I send via IMP (accentuted > characters ares correctly encoded) , I searched into > imp/lib/Compose.php and noticed that messages are not encoded by > MIME:encode. > Am I wrong ? > > Best regards > > Gerard >>> This encoding is perfectly fine. >> >> Hello Jan, >> >> It would be perfectly fine if the message vacation sending by mailbot >> was not : >> "?utf-8?b?w6kg?= =?utf-8?b?w6gg?= =?utf-8?b?w6A=?= " whereas the >> vacation message that has been created via the ingo's interface was : >> "é è ç". >> >> However the encoding is perfectly fine with the below modification... >> // Writing vacation.msg file >> //$reason = >> MIME::encode($params['action-value']['reason'], NLS::getCharset()); >> $reason = $params['action-value']['reason']; >> >> Nevertheless, your answer make me puzzle.... why the encoding would >> be perfectly fine for you and not for me if we have the same version >> ingo 1.2.5 under horde 3.3.10 ? >> >> Best regards >> >> Gérard >> >
Attachment
Watch this ticket

Saved Queries