Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #12

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md #12

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
View file
Open in desktop
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