[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:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  I18N          |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by dmsnell):

 Mind sharing a link to the spec where the content content header is
 discussed?

 Are you talking about finishing user generated files? Because many are
 read from the file system which contain no headers.

 That class doesn’t read in UTF-8 so much as it reads in //bytes// without
 performing any kind of character decoding. What are you suggesting the
 input bytes should be if not UTF-8? How should one represent an inherently
 multibyte character such as one of the thousands of CJK characters?

 Also, I’m not sure if you were meaning to write non-UTF-8 in your
 examples, but it could help if you specify the byte values you are writing
 instead of the text, which here will be UTF-8 by nature of the browser you
 used to write it.

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