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.gmi2
1 files changed, 2 insertions, 0 deletions
diff --git a/issues/fix-broken-utf8-chars.gmi b/issues/fix-broken-utf8-chars.gmi
index 0baeef3..7e6b5fe 100644
--- a/issues/fix-broken-utf8-chars.gmi
+++ b/issues/fix-broken-utf8-chars.gmi
@@ -17,3 +17,5 @@ This thread has some really nice ideas
An example of a broken unicode character is: ">". The character ">" appears broken because it is not a valid Unicode character. This can happen for a number of reasons, such as a mistake when typing or pasting the character, corruption during transmission (most likely the case) or storage, or a lack of support for the character in the font or software being used to display the text.
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.
+
+* closed