[wp-trac] [WordPress Trac] #63974: .mo file loaded as UTF-8 by default - non-standard and ignoring Content-Type headers

[WordPress Trac]

#63974: .mo file loaded as UTF-8 by default - non-standard and ignoring Content-
Type headers
-------------------------+------------------------------
 Reporter:  kkmuffme     |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  I18N         |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------
Changes (by swissspidy):

 * type:  defect (bug) => enhancement


Comment:

 > > are any of them saving files not as UTF-8?

 > What do you mean? A file does not have an inherent encoding, which is
 why the "Content-Type" header should be used.

 > This change won't affect most sites at all and for those plugins that
 are affected (= they provide .mo files with the Content-Type header
 missing) it's a minimal, simple fix in their release pipeline which
 ensures that their .mo files adhere to the standard more exactly and
 prevent encoding issues.

 You keep mentioning plugins that are doing it wrong by not including this
 header. Can you name some of these affected plugins? It would be great to
 have some examples to gauge impact and use for testing and outreach.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/63974#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform