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 ret
David Powers wrote:
> Yasuo Ohgaki wrote:
>
>>Then you may be feeding messages with encoding other
>>than internal encoding to mb_send_mail?
>
>
> If that's the case, the question is how?
For instance, you may be reading mail messages from
database or text file. En
Yasuo Ohgaki wrote:
>
> Then you may be feeding messages with encoding other
> than internal encoding to mb_send_mail?
If that's the case, the question is how?
Nothing has changed in my code, except for the need to substitute mail()
for mb_send_mail(). Under 4.2.2, mb_send
Yasuo Ohgaki wrote:
>
> I don't have problem with mb_send_mail()/mail()/over_load.
>
> It sounds like you haven't set mb_language() to Japanese.
> You have to set appropriate language to encode mail messages
> correctly. Refer to mb_language() manual page.
mb_language() is
David Powers wrote:
> Following the problems I reported earlier with the changes to mbstring
> in 4.3.0, I have now experienced unexpected behaviour with mb_send_mail.
> When serving a string of Japanese and English to mb_send_mail() in a
> script that had worked faultlessly under 4.2.2