[Tickets #9567] Re: charset pb replying to message

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/9567
------------------------------------------------------------------------------
  Ticket             | 9567
  Updated By         | rsalmon at mbpgroup.com
  Summary            | charset pb replying to message
  Queue              | IMP
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


rsalmon at mbpgroup.com (2011-03-15 22:12) wrote:

> This isn't correct.  Xss filter needs to return text in whatever  
> charset it was provided in, which is why the convertCharset() call  
> is necessary.  The question is why $dom->encoding is 'ISO-8859-1'  
> for you and 'UTF-8' for *everybody* else.

Hmm wait, weird, the message attached to this ticket looks wrong.  
re-attaching the message.

To the question as why $dom->encoding is 'ISO-8859-1', the answer is  
in the message :
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=

If I change 'charset=3Diso-8859-1"=' to 'charset=3Diso-8859-15"=',  
then $dom->encoding = ISO-8859-15

If I remove the meta tag from the message, everything works fine.

I've checked other messages I'm having issue with, and they all have  
the same charset meta tag

So this behaviour is expected according to  
http://devzone.zend.com/article/8855, Section 4.


I don't understand why this doesn't work here and works for you. What  
version of libxml2 and php are you using just in case this is related  
to the version I'm using. As I'm using the latest (or close enough),  
I'll try to downgrade to whatever version you are using.