[Tickets #10925] Re: Trying harder to display broken messages

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/10925
------------------------------------------------------------------------------
  Ticket             | 10925
  Updated By         | Jan Schneider <jan at horde.org>
  Summary            | Trying harder to display broken messages
  Queue              | IMP
  Version            | Git master
  Type               | Enhancement
  State              | New
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2012-01-16 14:46) wrote:

Okay, this problem is two-fold and in Horde_String::_convertCharset().  
First of all, $from is empty, which is causing iconv() and  
mb_convert_encoding() to raise errors. I'm going to further track this  
down.
But then there seems to be some problem with my PHP, or at least the  
PHP documentation. Inside the error handler, error_reporting() is  
supposed to return 0 if the command that caused the error is prefixed  
with @, which we do when calling @iconv(). error_reporting() still  
returns the error level for me though, so we don't return false from  
the error handler, thus $php_errormsg is not set in _convertCharset(),  
and we don't try mb_convert_encoding() (which would succeed if we  
tried that).
Do you use iconv at all? If yes, does calling iconv() from that  
message returns an error for you too? If yes, is it because $from is  
empty, and does error_reporting() indeed return 0 in the error handler?