From 6dd80b077cc2aeb84d9ecd4ae48186bf5a88f276 Mon Sep 17 00:00:00 2001 From: Munyoki Kilyungi Date: Tue, 29 Aug 2023 13:25:55 +0300 Subject: Mention tables that were converted in clased utf-8 issue Signed-off-by: Munyoki Kilyungi --- issues/fix-broken-utf8-chars.gmi | 5 +++++ 1 file changed, 5 insertions(+) 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 -- cgit v1.2.3