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

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/9532
------------------------------------------------------------------------------
  Ticket             | 9532
  Updated By         | gerard.breiner at ias.u-psud.fr
  Résumé             | Ingo Big problem with MIME::encode and  accentuated
                     | characters
  Queue              | Ingo
  Version            | 1.2.5
  Type               | Bug
  État               | Not A Bug
  Priorité           | 1. Low
  Milestone          |
  Patch              |
  Propriétaire       |
------------------------------------------------------------------------------


gerard.breiner at ias.u-psud.fr (2011-01-22 13:48) wrote:

> 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