#10862 closed defect (bug) (worksforme)
Incorrect encoding for non-ascii symbols in emails
| Reported by: | bobrik | Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Version: | 2.8.4 | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
WordPress uses iso-8859-1 as email codepage. It's better to use UTF-8 instead. No changes for ascii users but so many profit for other world :)
There's no any good way to hack around incorrect encoding now, so very annoying problem. Must be fixed in the next release.
Patch included. You may use it or make PHPMailer $CharSet var static to make it possible to change it by plugin or any other way.
Attachments (1)
Change History (12)
#1
@
17 years ago
- Summary Incorrect incoding for non-ascii symbols in emails → Incorrect encoding for non-ascii symbols in emails
#3
@
17 years ago
- Component Charset → Mail
- Keywords needs-patch reporter-feedback added; has-patch codepage phpmailer mail removed
- Owner removed
- Version 2.9 → 2.8.4
Just asking: bobrik how can you say for shure WordPress uses iso-8859-1 as email codepage? Did you find a definition / documnetation of that somewhere? I would love to know more, because I remember a similar ticket.
Your patch modifies the phpmailer classes which is bad practise. Please find the location in the code where it's instances need to be configured. Next to this, there isn't any chance to update the PHP4 version of the phpmailer class any longer because the current project leader closed that branch.
So -1 for the current patch from my side.
#5
@
17 years ago
- Cc added
Any plugin can use that class so default codepage must be ok for most cases.
How long changing class defaults to correct values became a bad practise? Or it's better to set that value for every object?
I don't see any troubles with that.
#7
@
17 years ago
- Cc added
Can you show how this manifests itself?
Can you provide an example of what you want to happen and what happens instead?
i.e.
when new users register, an email is sent from wordpress with the contents "XYZ hasło 슰°"
what is being received is garbled text,... etc
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
fix patch