[wp-trac] [WordPress Trac] #55603: PHP 8.2: address deprecation of the utf8_encode() and utf8_decode() functions

[WordPress Trac]

#55603: PHP 8.2: address deprecation of the utf8_encode() and utf8_decode()
functions
-------------------------------------------------+-------------------------
 Reporter:  jrf                                  |       Owner:
                                                 |  SergeyBiryukov
     Type:  task (blessed)                       |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.6
Component:  General                              |     Version:  6.0
 Severity:  normal                               |  Resolution:
 Keywords:  2nd-opinion php82 dev-feedback has-  |     Focuses:  coding-
  patch has-unit-tests                           |  standards
-------------------------------------------------+-------------------------

Comment (by dmsnell):

 Just a quick note that multi-byte strings aren't exclusively about non-
 English locales or even absent in English locales.

 Most European language groups have historically had their own single-byte
 encoding in the ISO-8859 family, but they are incompatible with each
 other. Unicode joins all of the recognized character sets into one large
 catalog and UTF-8 is the most universal way to represent that text in
 actual bytes.

 Most modern English-only language online is full of multi-byte characters
 as well, including “smart quotes,” the ellipsis…, em — dash, and a host of
 Emoji 😀.

 I think many in this thread are even //too// familiar with some of these
 complexities. For those who haven't come across the headaches of text
 encoding issues in English, you can be assured that they are there.

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