Timeline for Fixing broken UTF-8 encoding
Current License: CC BY-SA 4.0
Post Revisions
30 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2024 at 7:07 | answer | added | bhu1st | timeline score: 0 | |
| Apr 26, 2021 at 5:14 | answer | added | Marek Tichy | timeline score: 4 | |
| Jun 13, 2020 at 23:47 | comment | added | Rick James | See "Mojibake" in stackoverflow.com/questions/38363566/… | |
| Jan 9, 2020 at 0:10 | answer | added | Jordan Daigle | timeline score: 1 | |
| Jul 7, 2019 at 22:25 | history | edited | Peter Mortensen | CC BY-SA 4.0 |
Active reading [<http://en.wikipedia.org/wiki/UTF-8>].
|
| Aug 15, 2017 at 9:05 | history | edited | Cœur | CC BY-SA 3.0 |
removing "help"
|
| Nov 16, 2016 at 14:23 | answer | added | Erik Aronesty | timeline score: 0 | |
| Oct 19, 2016 at 16:58 | comment | added | Wiktor Stribiżew |
Acc. to this answer, mysqli_set_charset($dbc, "utf8"); might help.
|
|
| Sep 9, 2016 at 21:05 | comment | added | jar |
one of the problems afaik is utf8_general_ci which apparently will not guarantee good UTF8 stackoverflow.com/a/1036459/183677. Also those characters you mention are valid UTF8 hexutf8.com/… (but I realize its probably just what you're seeing in console or whatever). pays to post the actual bytes
|
|
| Mar 8, 2015 at 17:43 | answer | added | Luke Madhanga | timeline score: 1 | |
| Jul 14, 2014 at 8:11 | answer | added | Celleb | timeline score: 19 | |
| Feb 26, 2013 at 12:24 | answer | added | David 天宇 Wong | timeline score: 0 | |
| Dec 28, 2011 at 15:06 | history | edited | Jayrox | CC BY-SA 3.0 |
edited body
|
| Dec 25, 2011 at 20:17 | comment | added | Sebastián Grignoli | Yes, Jayrox, check out my answer below. | |
| Apr 20, 2011 at 14:21 | answer | added | Jose De Gouveia | timeline score: 0 | |
| Dec 16, 2010 at 16:05 | answer | added | jsdalton | timeline score: 98 | |
| Aug 19, 2010 at 11:38 | answer | added | Sebastián Grignoli | timeline score: 93 | |
| Mar 4, 2010 at 12:59 | answer | added | blueyed | timeline score: 11 | |
| Dec 31, 2009 at 20:20 | vote | accept | Jayrox | ||
| Nov 24, 2009 at 19:09 | answer | added | Dan | timeline score: 1 | |
| Aug 29, 2009 at 18:39 | answer | added | Jayrox | timeline score: 3 | |
| Aug 28, 2009 at 17:59 | answer | added | Eli | timeline score: 66 | |
| Aug 28, 2009 at 12:56 | history | edited | Jayrox | CC BY-SA 2.5 |
added 49 characters in body
|
| Aug 28, 2009 at 12:56 | history | edited | Welbog |
edited tags
|
|
| Aug 28, 2009 at 3:15 | history | edited | Jayrox | CC BY-SA 2.5 |
added phpMyAdmin info
|
| Aug 28, 2009 at 3:10 | comment | added | Jayrox | It is possible that it was double encoded. Is there a safe way to programatically check this, and if so what is the best way to safely decode the double encoding? | |
| Aug 28, 2009 at 2:58 | answer | added | teambob | timeline score: 0 | |
| Aug 28, 2009 at 2:46 | comment | added | Managu | A quick look seems to suggest that your strings might have been "double" utf-8 encoded. I.e. encoded in utf-8, those bytes taken as unicode characters, and the result encoded in utf-8. Going backwards: "î"="\xC3\x83\xC2\xAE" <-(utf-8)- "\xC3\xAE" <-(utf-8)- "\xEE" = "î". Or perhaps not -- not much data to diagnose here. | |
| Aug 28, 2009 at 2:35 | comment | added | Managu | Perhaps you could list the characters those are supposed to represent? And maybe a hex dump? | |
| Aug 28, 2009 at 2:14 | history | asked | Jayrox | CC BY-SA 2.5 |