Yasuo Ohgaki wrote:
>
> For instance, you may be reading mail messages from
> database or text file. Encoding can be any encoding with
> this.
The mail message is created by using PHP to retrieve material stored as
Shift_JIS in a MySQL database. PHP then turns the array of retrieved
material into a long string which is then fed to the PHP mailing
routine. Under 4.2.2, mb_send_mail() handled the process perfectly. Now
it doesn't. I have to use mail() instead.
> Which encoding results in mojibake?
> If you have problem ISO-8859-1, set language to 'en' before
> using mb_send_mail.
As I explained before, even when mb_language() reports "Japanese",
mb_send_mail() will not send Japanese, but mail() does.
> Moriyoshi should have overlooked commented out mb_output_handler.
> You need mb_output_handler to convert encoding from EUC-JP to SJIS.
> (If you really want to output SJIS)
Even on 4.2.2, mb_output_handler had to be turned off. I am running an
English language version of RH 6.2 without canna or any other support
for multi-byte characters. Perhaps that is what is causing the
difference.
It's not important to me whether the output is SJIS or EUC-JP. I use PHP
to create databases in English and Japanese to supply content to dynamic
websites, and to send content from the same databases by email. I know
that Windows machines can display EUC-JP websites correctly (if the
correct charset is set in the web page), and that email is sent as JIS.
The reason I use SJIS is because the content is entered into the
databases by means of online forms. The original forms were developed by
someone else in ASP, and nearly two years' worth of material is now in
the database in SJIS. I suppose it would be possible to convert the
content, and switch the EUC-JP, but how would that affect inputting? All
the material is created in Word on Windows machines, and therefore in
SJIS. Would PHP set to EUC-JP convert such input, and would it be more
efficient that way?
> (We may be forgetting to document changes, but I don't
> have time to check it :)
I am extremely grateful that the Open Source community has created
something as powerful and useful as PHP, but if changes are not properly
documented, it will lose its attraction and value. That would be a great
pity.
David Powers
--
PHP Internationalization Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
