For my program, it has several foreign language strings for international users. I've noticed that at least for certain Cyrillic letters, the FIT output that gets printed to the activity on Garmin Connect (web- and mobile-) ends up getting truncated, by approximately half the quantify of Cyrillic characters present in the string. I think this must be because the FIT file assumes each string length is equivalent to English length, but some UTF-8 characters are multiple bytes long.
So... does FIT output NOT support UTF-8 characters?
If FIT is supposed to support UTF-8 output, please examine the following erroneous behavior. Here are some words used in my app, as they've appeared (with errors) in the FIT output on Garmin Connect webpage.
Your Standing - П <-- should be ПП but for some reason the output is truncated by 1
Your Results - 4.6 km, 0 КП, 21:2 <-- should end with xx:xx digits, meaning we're missing one numerical digit at the end, meaning this string has been shortened by one character, likely because there are two Cyrillic characters in the string
Course Info - 3.7 km, 5 КП, 41:0 <-- same thing here, missing the last numerical digit in the string
Course Format - ЗН, MGR <-- here we're missing the last English character in the string, likely due to the fact that this string contains 2 Cyrillic characters.
Precision - Норма <-- here the word should be Нормальная, which is 10 characters long (but occupies 20 bytes unlike a 10 character long ASCII string which would occupy only 10 bytes), therefore, only 10 bytes are printed, which is five Cyrillic characters
Start Date - Пон, 6 Дек <-- should finish with "Декабрь 2021" again, this string is about 10 characters short, which is because there are about 10 Cyrillic characters present in the string.
Start Time - 6:08:07 (UTC -5) <-- nothing missing here, because no foreign characters
Any tips? Is FIT just not UTF-8 compliant?
Or, it is a problem with the both the web and mobile versions of Garmin Connect, responsible for erroneously printing out the FIT info?
