• Resolved pengin324

    (@pengin324)


    I realized that UTF-8 strings are destroyed during the processing by Postie.

    Then I figured out that htmlentities is the origin of this problem.
    cf: http://stackoverflow.com/questions/5679715/htmlentities-destroys-utf-8-strings

    For my case, it was easy to fix this by changing the source as below. But I’m not sure this solution is universal for others. For example, I’m not sure the third argument of htmlspecialchars should be UTF-8 or not depending on the settings.

    
        DebugEcho("GetContent: html not allowed (htmlentities)");
        //$meta_return .= htmlentities($part->body);
        $meta_return .= htmlspecialchars($part->body, ENT_QUOTES, "UTF-8");
    

    But anyway, I would like to report this and hope to see this is fiexed.

    • This topic was modified 9 years, 8 months ago by pengin324.
Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘UTF-8 Strings are destroyed (with solution)’ is closed to new replies.