WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Wrong-o.
Apparently `utf8` in MySQL (and some other applications) is limited to [3 Byte
Unicode characters](https://en.wikipedia.org/wiki/UTF-8#Description).
Unfortunately the bulk of the
[Emoji characters](https://unicode-table.com/en/#emoticons) is found in 4 Byte
[Emoji characters](https://symbl.cc/en/unicode-table/#emoticons) is found in 4 Byte
Unicode space.

Trying to store those Emoji (and other 4 Byte characters) in a MySQL `utf8`
Expand All @@ -38,7 +38,7 @@ don't want to convert just a few columns to the new charset but all of them
(because consistency and because you will have to change your connection's
charset as well) and you really only care about Emoji and not about
characters for
[Ancient Greek Musical Notation](https://unicode-table.com/en/#ancient-greek-musical-notation)
[Ancient Greek Musical Notation](https://symbl.cc/en/unicode-table/#ancient-greek-musical-notation)
aaand you just did all that converting a couple of years ago for `utf8` and
don't really have the time and nerve to do it again ...

Expand Down