I've been working rather extensively trying to get all languages to work=20
properly on my system with squirrelmail.
I am using Gentoo, PHP 5.1.1, and Squirrelmail 1.4.6-release. For testing=
simplicity, it is simply a stock release from the Squirrelmail website, wit=
I have rebuilt PHP about 14 different ways trying to get things to work to =
avail - here's what I've determined:
Gentoo has an "nls" USE flag, which if used, makes the PHP package dependan=
upon gettext, and enables building of both gettext and mbstring as shared=20
extensions for PHP.
If the "nls" USE flag is disabled, selecting another language in=20
Squirrelmail's Display Options works. However, if Japanese is selected,=20
warnings are shown about needing mbstring (although Japanese text *is*=20
shown), and mail cannot be viewed because of the errors, though a folder li=
and mail index is shown, and one can browse the options pages, etc. all in=
Japanese but with the warning at the top.
If the "nls" USE flag is enabled, selecting another language does absolutel=
nothing, although the output encoding is changed to whatever is appropriate=
for that language. Furthermore, if Japanese is selected, the subject lines=
in the message index are all truncated shorter than normal, with characters=
such as # and & shown before the '...'.
I have written a small test script (UTF-8 encoded) that verifies mbstring i=
ini_set ('mbstring.internal_encoding', 'UTF-8');
print 'This is a PHP file.';
I can successfully view this file in a web browser and verify that the=20
encoding is actually ISO-2022-JP.
I normally use the Hardened-PHP patch and a number of other USE flags, howe=
for the purposes of trying to get to the bottom of this, I built a PHP=20
instance with no USE flags whatsoever, and then enabled only what=20
Squirrelmail complained about needing - namely session and pcre support. =20
This made no difference.
I also have a hacked-up version of squirrelmail that's been made to use UTF=
internally and as the output charset for all languages - it breaks in the=20
exact same way. While it does seem to work just fine, even for Japanese,=20
without the mbstring PHP extension, I've been told by somebody on the=20
squirrelmail-devel list that I need to use mbstring or there will be proble=
=2D i.e. the line length on outbound messages will be wrong.
Please let me know any suggestions you may have, as I'd like to get this=20
Casey Allen Shobe | cshobe@... | 206-381-2800
SeattleServer.com, Inc. | http://www.seattleserver.com