At 09:47 PM 5/24/2003, you wrote:
Sorry for the delay in replying.

>>
>> On the Apache (2) side, this is probably being caused by
> AddDefaultCharset
>> in /etc/httpd/conf/httpd.conf.
>>
>> #
>> # Specify a default charset for all pages sent out. This is
>> # always a good idea and opens the door for future
> internationalisation
>> # of your web site, should you ever want it. Specifying it as
>> # a default does little harm; as the standard dictates that a page
>> # is in iso-8859-1 (latin1) unless specified otherwise i.e. you
>> # are merely stating the obvious. There are also some security
>> # reasons in browsers, related to javascript and URL parsing
>> # which encourage you to always set a default char set.
>> #
>> AddDefaultCharset ISO-8859-1
>>
>> This (default) setting is possibly nullifying the page output
>>
>> Content-Type text/html; charset="euc-jp"
>>
>> whereby it is being initially ignored by IE.
>>
>> (You may want to try playing around with the configuration there.)
>
> do you have any specific recommendations?

I am usually one to try a whole set of solutions first and then comment on
which ones which work for me, but since I have not done this here I
hesitated to make any specific recommendations.

I would try first commenting out the default AddDefaultCharset ISO-8859-1.
If that fixes the problem without causing any new ones, then great. If
this changes nothing then for fun I would try replacing ISO-8859-1 with
EUC-JP and seeing if that at least helps on the Japanese side of things
(even though it may upset other areas...). If it does sort out the
Japanese initial charset problem, then it suggests to you that you may be
able to solve the problem by conditionally changing the charsets (e.g.
specifying them depending on the client browser.)

Scott.

Scott - I have the Japanese PC's now loading SM okay, by remarking out the AddDefaultCharset ISO-8859-1 command in httpd.conf. Thanks for that suggestion. Each Japanese user has changed their default language in SM Options to Japanese, as well.


However, additional problems have arisen. When attempting to view a message in the in-box, it gives the following error:

Fatal Error: Call to undefined function mb_detect_encoding() in /var/www/html/squirrelmail-1.4.0/functions/mime.php in line 339

And, when attempting to compose a new message, it gives the following error:

Fatal Error: Call to undefined function mb_detect_encoding() in /var/www/html/squirrelmail-1.4.0/src/compose.php in line 1335


Since these lines follow an if statement checking for iso-2022-jp, I suspect this is related to the previous problem with in changing the default character set, but I'm not sure.


Any suggestions on what the problem/solution might be?

Thanks!

Larry





-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
--
squirrelmail-users mailing list
List Address: [EMAIL PROTECTED]
List Archives:  http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users

Reply via email to