[wp-trac] [WordPress Trac] #63974: .mo file loaded as UTF-8 by default - non-standard and ignoring Content-Type headers
WordPress Trac
noreply at wordpress.org
Mon Sep 15 14:30:09 UTC 2025
#63974: .mo file loaded as UTF-8 by default - non-standard and ignoring Content-
Type headers
--------------------------+------------------------------
Reporter: kkmuffme | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: I18N | Version:
Severity: normal | Resolution:
Keywords: | Focuses:
--------------------------+------------------------------
Comment (by siliconforks):
Replying to [comment:2 kkmuffme]:
> If no Content-Encoding header is specified, it should be treated as
ANSI. Since ANSI does not support multibyte characters, this means those
should be removed.
This seems like a bad idea to me, since silently deleting (non-)characters
often leads to security vulnerabilities:
https://www.unicode.org/reports/tr36/tr36-15.html#Deletion_of_Noncharacters
--
Ticket URL: <https://core.trac.wordpress.org/ticket/63974#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list