View Page
Export to Word
Export to PDF
Archive
Presenter mode
Page history
A
t
tachments (0)
Page Information
View Source
Content
…
JEMH Home
2 - Configuring JEMH
Common Problems
Handling UTF-8 multi-byte characters with a MySQL database
Page History
Version
Published
Changed By
Comment
Actions
CURRENT
(v. 3)
Jan 29, 2021 18:47
In November 2003, UTF-8 was restricted by RFC 3629 to match the constraints of the UTF-16 character encoding: explicitly prohibiting code points corresponding to the high and low surrogate characters removed more than 3% of the three-byte sequences, and ending at U+10FFFF removed more than 48% of the four-byte sequences and all five- and six-byte sequences.
v. 2
Jan 29, 2021 13:27
v. 1
Jan 29, 2021 13:26
Return to Page Information
Manage space
Manage content
Integrations
{"serverDuration": 178, "requestCorrelationId": "f4cd68d1a78946c4a207badf7d694223"}