diff options
| author | Munyoki Kilyungi | 2022-11-29 08:29:33 +0300 |
|---|---|---|
| committer | Munyoki Kilyungi | 2022-11-29 08:29:33 +0300 |
| commit | dc8203ff9d1fd1d603af37616c3e5032aaa28997 (patch) | |
| tree | a9723440a0fb957fc1916e972831f25811894103 | |
| parent | 53f42cf145fa986881a07765fd99e651d629f42d (diff) | |
| download | gn-gemtext-dc8203ff9d1fd1d603af37616c3e5032aaa28997.tar.gz | |
Add reference link
| -rw-r--r-- | issues/fix-broken-utf8-chars.gmi | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/issues/fix-broken-utf8-chars.gmi b/issues/fix-broken-utf8-chars.gmi index d6a4a7b..beef2c2 100644 --- a/issues/fix-broken-utf8-chars.gmi +++ b/issues/fix-broken-utf8-chars.gmi @@ -9,3 +9,7 @@ ## Description We have jumbled up text in our database and this has been the case for years. It's impractical for a user to do the fixes using the metadata editing form because there are too many cases. A script that fixes this should be created to fix this issue. + +This thread has some really nice ideas + +=> https://stackoverflow.com/questions/1476356/detecting-utf8-broken-characters-in-mysql Detecting broken characters in mysql |