Make WordPress Core

Opened 6 years ago

Last modified 6 years ago

#44548 new enhancement

Email should be encoded with UTF8 and base64

Reported by: miyauchi's profile miyauchi Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: I18N Keywords: has-patch has-unit-tests reporter-feedback
Focuses: Cc:


The plugin WP Multibyte Patch included in the Japanese package is changing the Email charset from UTF-8 to ISO-2022-JP.

Almost all Email clients in Japan can handle UTF-8 now, so I am believing that we don't need to change email charset to ISO-2022-JP.

Also, if we activate WP Multibyte Patch and switch language to another language like FR_fr, the character in the email body will be broken.

But I guess email should be encoded by base64 for non-ascii users. I know 8bit encoding works good, but I guess base64 is reliable for us if we remove the plugin from Japanese package.

Following is an example email header of the Gmail. Gmail is UTF8 + base64.

Subject: =?UTF-8?B?xxxxxxxxxxxxxxxxxx==?=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

Related: #meta3163, #43829, #44296, #44541, #15955, #22363

Following is a list of tickets to improve multibyte enhancement.

Attachments (1)

44548.patch (6.7 KB) - added by miyauchi 6 years ago.

Download all attachments as: .zip

Change History (3)

6 years ago

#1 @miyauchi
6 years ago

  • Keywords has-patch has-unit-tests added

#2 @ocean90
6 years ago

  • Keywords reporter-feedback added

It would be great to see how such a broken email looks like with the raw headers. What's the value of get_bloginfo( 'charset' )?

Note: See TracTickets for help on using tickets.