Ticket #3574 (closed defect (bug): fixed)
Character set not specified in TinyMCE files
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | 2.0.9 |
| Component: | Administration | Version: | 2.0.7 |
| Severity: | major | Keywords: | has-patch |
| Cc: | nbachiyski, ruckus |
Description
Using 8-bit characters in TinyMCE translation does not work, because the output from tiny_mce_gzip.php and wp-mce-help.php does not specify any charset in Content-Type. This leaves it up to PHP and the web server to complete the Content-Type charset information, possibly incorrectly.
The charset should not be hard-coded in these scripts, so that plugins such as Character Set Conversions[1] can use the gettext hook to transcode the messages to the character set specified in the blog settings.
[1]: http:/kimmo.suominen.com/sw/charsets/
Attachments
-
tinymce-charset.diff
(1.2 KB) -
added by ruckus 5 years ago.
- Patch against 2.0.7-RC1
Change History
-
attachment
tinymce-charset.diff
added
comment:1
markjaquith — 5 years ago
- Milestone changed from 2.0.8 to 2.2
Does this apply to 2.1 or 2.2? If so, we should fix it there first.
comment:2
foolswisdom — 5 years ago
- Cc nbachiyski added
- Keywords has-patch added; bg|has-patch removed
- Status changed from new to closed
- Resolution set to fixed
- Milestone changed from 2.2 to 2.0.9
Committed for 2.2 and 2.1.1. Let's milestone for 2.0.9.
Looks like the change was applied to 2.1 and 2.2, so it applied. I'm not running the trunk (yet), so my patches tend to be against 2.0.x.
Patch against 2.0.7-RC1