Yes, it works.
Operations were carried out on T server on which there is no chroot.
I commented out the operators calling iconv and made these corrections.
GB2312 fulfilled normally.
It seems mb_check_encoding returns false.
I uncommented iconv and was convinced that iconv normally works both
with GB18030, and with ISO-2022-KR.
Whether it is necessary also to add a line:
'GBK' => 'GB18030',
?
---
Best regards,
Vladimir Gorpenko
A.L.E.C писал 2016-09-27 12:40:
On 26.09.2016 22:41, Vladimir Gorpenko wrote:
2. In the second queue RC tries to apply mbstring to conversion of
codings. Mbstring, apparently, doesn't understand GB2312 (GBK), but
understands ISO-2022-KR. Nevertheless, mbstring also doesn't work at W
server. I think, the reason is also somehow connected to chroot.
I'm curious if this patch would fix the GB2312 issue for mbstring path.
-- a/program/lib/Roundcube/rcube_charset.php
+++ b/program/lib/Roundcube/rcube_charset.php
@@ -39,8 +39,8 @@ class rcube_charset
'UNKNOWN' => 'ISO-8859-15',
'USERDEFINED' => 'ISO-8859-15',
'KSC56011987' => 'EUC-KR',
- 'GB2312' => 'GBK',
- 'GB231280' => 'GBK',
+ 'GB2312' => 'GB18030',
+ 'GB231280' => 'GB18030',
'UNICODE' => 'UTF-8',
'UTF7IMAP' => 'UTF7-IMAP',
'TIS620' => 'WINDOWS-874',
@@ -51,7 +51,7 @@ class rcube_charset
'128' => 'SHIFT-JIS',
'129' => 'CP949',
'130' => 'CP1361',
- '134' => 'GBK',
+ '134' => 'GB18030',
'136' => 'BIG5',
'161' => 'WINDOWS-1253',
'162' => 'WINDOWS-1254',
_______________________________________________
Roundcube Development discussion mailing list
[email protected]
http://lists.roundcube.net/mailman/listinfo/dev
