diff options
| author | Munyoki Kilyungi | 2023-08-11 15:55:36 +0300 |
|---|---|---|
| committer | Munyoki Kilyungi | 2023-08-11 15:55:36 +0300 |
| commit | 5012c9857ee11fb2ce43b2b60b69367eedf3a596 (patch) | |
| tree | 64d15cb585ca6d8d213bc59b2d3579cee35bb760 | |
| parent | e06b245b7e5f4c979949bafa76e7e585439a3fc0 (diff) | |
| download | gn-gemtext-5012c9857ee11fb2ce43b2b60b69367eedf3a596.tar.gz | |
Close utf8 char issues
Signed-off-by: Munyoki Kilyungi <me@bonfacemunyoki.com>
| -rw-r--r-- | issues/fix-broken-utf8-chars.gmi | 2 |
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 |