Yes, mbstring is installed. But one configuration setting raises doubts:

Multibyte Support       enabled
Multibyte string engine         libmbfl
HTTP input encoding translation         disabled
libmbfl version         1.3.2

I do not know, is "HTTP input encoding translation" significant for my situation or now.

Now I have a letter with GB2312 charset.

This encoding is specified in:

- headers, where it is used: Subject: =?gb2312?B?STo...

- Content-type header:
Content-Type: text/plain;
Content-Type: text/html;

- The coding is mentioned in HTML headers quite strange. I don't know, what does it mean.

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:m=3D""; =
xmlns=3D"";><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312">

I am sure the letter is encoded properly because eM client opens it correctly.
But in RC I see something like the Arab characters.

Best regards,
   Vladimir Gorpenko

A.L.E.C писал 2016-09-22 10:48:
On 22.09.2016 09:45, Vladimir Gorpenko wrote:
As far as I can judge, RC 1.1.4 doesn't support these codings.

Roundcube supports all encodings supported by iconv/mbstring.

Do these letters specify encoding in mail headers and/or HTML head?

Do you have php-mbstring installed?

Are you sure they are properly encoded? E.g. if conversion to utf-8
fails (using mbstring or iconv) then the content will be displayed as is
(with removed non-unicode characters).
Roundcube Development discussion mailing list

Reply via email to