You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd started using the original version, but then found out that what MySQL thinks is UTF-8 is actually just a subset, specifically, that it doesn't support 4-byte characters, only 3. I've made a variant in a separate branch that defaults to using this charset. There's a good article on it here.
Of course most people won't need that full range - it includes some lesser-used Chinese characters, but more interestingly it includes full-colour Emoji icons that work in OS X and iOS, oh, and GitHub 😸!
Another minor difference is that it's using the 'utf8mb4_unicode_ci' collation, which is more correct than the default 'utf8mb4_general_ci', and results in correct sort orders in German and other languages.
The text was updated successfully, but these errors were encountered:
If you want, it would be nice if the script was updated to prompt the user to choose either utf8 (if they don't have MySQL 5.5.3) or utf8mb4 if they do, then use that setting for the rest of the variables.
I'd started using the original version, but then found out that what MySQL thinks is UTF-8 is actually just a subset, specifically, that it doesn't support 4-byte characters, only 3. I've made a variant in a separate branch that defaults to using this charset. There's a good article on it here.
Of course most people won't need that full range - it includes some lesser-used Chinese characters, but more interestingly it includes full-colour Emoji icons that work in OS X and iOS, oh, and GitHub 😸!
Another minor difference is that it's using the 'utf8mb4_unicode_ci' collation, which is more correct than the default 'utf8mb4_general_ci', and results in correct sort orders in German and other languages.
The text was updated successfully, but these errors were encountered: