From: Casey A. S. <li...@se...> - 2006-02-25 17:56:19
|
On Saturday 25 February 2006 14:11, Tomas Kuliavas wrote: > Please stop blaming mbstring. It has only one dangerous feature. function > overloading. This feature is not enabled by default and not enabled in > your setup. It /is/ enabled in our setup. configtest.php shows: mbstring - Mbstring functions are available. I'm not trying to place blame on anything, I'm simply giving you the info I have been able to determine. I did not even mention mbstring in the E-mail you're replying to, but in my previous E-mail where I did discuss problems with the mbstring extension affecting translations, all I did was describe what I'm seeing and asked for suggestions. > SquirrelMail translations don't stay in English because you have mbstring. > System locale issue is specific to gettext extension and not to mbstring. Well, I don't claim to know the intricate details of how PHP works, however with the mbstring extension disabled, gettext does translate things correctly (except that I see the warning about not having mbstring enabled when I try to use Japenese) on a box with no locales but en_US and en_US.utf8. On the same box, enabling mbstring causes nothing to be translated and everything is shown in English regardless of language choice. However, now that we have all the locales built, translations work whether or not mbstring is enabled. How do you explain the phenomenon described in the first paragraph above? According to your logic, I should have never had any translations working when in fact they were. > Main Japanese translation code was written before changes in SquirrelMail > header decoding. If decoding changes broke Japanese translation, we must > fix decoding code and Japanese extra code functions. Japanese translation doesn't appear to be broken - with all of the glibc locales built on the box now, the Squirrelmail interface displays in Japanese properly for a stock squirrelmail 1.4.6 install. The only problem is that subject lines (in english, which is what all my mail is) are shorter than they should be, because spaces become   making them 5 characters instead of 1 by the time they hit whatever function does the subject truncation for the index display (and other characters too I'm sure, but spaces are the most obvious example). Cheers, -- Casey Allen Shobe | cs...@se... | 206-381-2800 SeattleServer.com, Inc. | http://www.seattleserver.com |