summaryrefslogtreecommitdiff
path: root/issues/fix-broken-utf8-chars.gmi
diff options
context:
space:
mode:
authorMunyoki Kilyungi2022-11-29 08:23:36 +0300
committerMunyoki Kilyungi2022-11-29 08:23:36 +0300
commit53f42cf145fa986881a07765fd99e651d629f42d (patch)
tree42885347dc221917827c6eb53c0543c8e07582b7 /issues/fix-broken-utf8-chars.gmi
parent73744507a04dd5a6ee6031b54d42758d409d5aa8 (diff)
downloadgn-gemtext-53f42cf145fa986881a07765fd99e651d629f42d.tar.gz
Create new issue that addresses broken utf-8 characters in our db
Diffstat (limited to 'issues/fix-broken-utf8-chars.gmi')
-rw-r--r--issues/fix-broken-utf8-chars.gmi11
1 files changed, 11 insertions, 0 deletions
diff --git a/issues/fix-broken-utf8-chars.gmi b/issues/fix-broken-utf8-chars.gmi
new file mode 100644
index 0000000..d6a4a7b
--- /dev/null
+++ b/issues/fix-broken-utf8-chars.gmi
@@ -0,0 +1,11 @@
+# Fix Broken UTF-8 characters in our Database
+
+## Tags
+
+* assigned: bonfacem, arthur
+* type: database
+* priority: high
+
+## 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.