|Dependency Graph||View Issue Relation Graph Vertical|
View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005017||phpList 3 application||General||public||08-12-05 03:30||18-02-08 14:06|
|Target Version||2.10.7||Fixed in Version||2.10.4|
|Summary||0005017: Special character "o acute" is displayed as "ó" in text version of a message.|
|Description||I assume, PHPList does the following:|
-> you write an HTML-message in the FCKeditor
-> FCKeditor stores this message in ASCII-style in field "message" in table "_message" in the database
-> the send process takes the content of the message field and stores it in the mail's body
-> because the send process fails to convert the HTML-ASCII back to the special chars or another plain text compatible encoding, all special chars are scrambled in plain text messages
-> HTML messages look fine, because modern E-Mail-clients are able to decode the ASCII-part of special characters in HTML-messages
Seems like this is a major bug in the program's send routine. There is a second field in the table "_message" called "textmessage" but this one's empty. Bug or feature?
What do you think?
|Additional Information||solution submitted: http://www.phplist.com/forums/viewtopic.php?p=14259|
reported to work for German characters.
|Tags||No tags attached.|
|possible solution: http://www.phplist.com/forums/viewtopic.php?p=14875#14875|
||The submitted solution does not seem to work with the current version (2.10.2), we still get the special chars..|
||see also http://forums.phplist.com/viewtopic.php?p=19824|
In the German forum JenGermany reports that special characters like ä, ö, ü, are displayed as ä ö ü in the text version of an HTML message (see http://forums.phplist.com/viewtopic.php?t=6884 )
The following fix apparently solved the problem:
In class.phplistmailer.php on line 61 (function add_text($text)) ,
$this->Body = $text;
$this->Body = html_entity_decode($text ,ENT_QUOTES, 'UTF-8' );
Charset for HTML messages: UTF-8
Charset for Text messages: UTF-8
I couldn't reproduce the problem on my installation, but I had USE_MANUAL_TEXT_PART enabled, which might perhaps account for that.
||yes, I can confirm that. Annoying, I thought it had been fixed, but obviously not|