Editing Unicode guide
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 123: | Line 123: | ||
The second edition of Unicode increased the codespace to 21-bit and introduced UTF-32 as its fixed-width encoding. UCS-2 was succeeded by the variable-width UTF-16 encoding we have today. A portion of the codespace was reserved as 'surrogate' code points to preserve compatibility between UCS-2 and UTF-16: These code points are seen as valid code points by UCS-2 systems but decoded as 21-bit code points by UTF-16. | The second edition of Unicode increased the codespace to 21-bit and introduced UTF-32 as its fixed-width encoding. UCS-2 was succeeded by the variable-width UTF-16 encoding we have today. A portion of the codespace was reserved as 'surrogate' code points to preserve compatibility between UCS-2 and UTF-16: These code points are seen as valid code points by UCS-2 systems but decoded as 21-bit code points by UTF-16. | ||
Lots of time is spent discussing which encoding is the better variable-width encoding | Lots of time is spent discussing which encoding is the better variable-width encoding. But in practice the encoding you use is likely decided by the tools you use and APIs you interact with. This choice is increasingly irrelevant as Unicode becomes a first class feature of programming languages and encoding becomes an implementation detail. | ||
== Algorithms == | == Algorithms == |