summaryrefslogtreecommitdiff
path: root/issues/fix-broken-utf8-chars.gmi
diff options
context:
space:
mode:
Diffstat (limited to 'issues/fix-broken-utf8-chars.gmi')
-rw-r--r--issues/fix-broken-utf8-chars.gmi5
1 files changed, 5 insertions, 0 deletions
diff --git a/issues/fix-broken-utf8-chars.gmi b/issues/fix-broken-utf8-chars.gmi
index 7e6b5fe..161c3b0 100644
--- a/issues/fix-broken-utf8-chars.gmi
+++ b/issues/fix-broken-utf8-chars.gmi
@@ -18,4 +18,9 @@ An example of a broken unicode character is: ">". The character ">" a
To find the correct replacement for the character ">", or any other character for the matter, you can look up its Unicode code point. In this case, the code point for ">" is "U+2273", which corresponds to the character "≥". You can then use this code point to search for and replace the broken character with the correct character in the text.
+Tables I've had to convert:
+
+* Investigators
+* InfoFiles
+
* closed