Events: Set wporg_events charset to latin1 to fix Mojibake
#1050
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iandunn
force-pushed
the
fix-landing-mojibake
branch
from
c6eb9f8 to
a13f3db
Compare
iandunn
force-pushed
the
fix-landing-mojibake
branch
from
a13f3db to
6f4420b
Compare
iandunn
changed the title
wporg_events to latin1 to fix Mojibake
iandunn
changed the title
wporg_events charset to latin1 to fix Mojibake
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1043
The
wporg_eventstable uses thelatin1charset, so we need to set the MySQL connection to use that. Otherwise the results are Mojibake because they're decoded with a different charset than they were encoded with.See these tickets for a similar situation, but in the opposite direction: