WordPress.org
Get WordPress

Make WordPress Core

Changes between Initial Version and Version 2 of Ticket #62172


Ignore:
Timestamp:
10/05/2024 07:18:14 PM (2 months ago)
Author:
dmsnell
Comment:

Updated to fix the inverted deprecation (let's go back to US-ASCII-only 🙃), and thanks @mdawaffe!

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #62172 – Description

    initial v2  
    1818 - HTML is sent to the browser and a `<meta charset="">` tag is produced to instruct the browser how to interpret the bytes it receives. This may or may not match the HTML which WordPress is generating, as most block code and most filters are hard-coded PHP strings in UTF-8 or are at least isomorphic to it up to US-ASCII.
    1919
    20 So as is the case with deprecating XHTML and HTML4 support, deprecating UTF-8 is mostly about being honest with ourselves and making space officially to remove complex and risky parts of the codebase that often do more harm and help. There's a good chance today that WordPress is already extremely fragile when working with non-UTF-8 systems, and deprecating it would make it possible to fix those existing issues.
     20So as is the case with deprecating XHTML and HTML4 support, deprecating non-UTF-8 support is mostly about being honest with ourselves and making space officially to remove complex and risky parts of the codebase that often do more harm and help. There's a good chance today that WordPress is already extremely fragile when working with non-UTF-8 systems, and deprecating it would make it possible to fix those existing issues.
    2121
    22 Deprecating UTF-8 means WordPress can stop attempting to support an N-to-M text-encoding architecture and replace it with an N-to-1 architecture, where strings that need to be converted are converted at the boundary of the system while everything inside the system is UTF-8, harmonizing all of the different levels of encoding and code.
     22Deprecating non-UTF-8 support means WordPress can stop attempting to support an N-to-M text-encoding architecture and replace it with an N-to-1 architecture, where strings that need to be converted are converted at the boundary of the system while everything inside the system is UTF-8, harmonizing all of the different levels of encoding and code.