Acknowledged
5 months ago

utf-8 and string resources

i have a problem with german umlauts (öäü) in string resources:

whenever i get the app from the ciq store (iq file) i only get "?" instead of umlauts while it works fine when i sideload the app or test in the simulator.

this happened before (see https://forums.garmin.com/developer/connect-iq/i/bug-reports/connect-mobile-and-utf-8-for-app-settings) and seemed to be fixed with SDK 3.2.3 but now using SDK 4.1.7 it re- appeared...

Tobi
  • over 2 years ago

    I have Ä in strings (March) and nobody noticed me about problem but I use custom font. I can't test it on device but on sim it looks good

  • over 2 years ago in reply to _psx_

    1. yes - all my mc and xml files are UTF-8 (i also dont see how a wrongly encoded file would work OK in the .prg build but not in the iq build...)

    2. not really - im more a vi kind of guy (but all the ciq stuff happens in vscode...)

    i checked with SDK 4.1.4 today and it shows the same problem :-(

  • over 2 years ago

    1.ALL files should be marked as utf-8

    2. Have you ever used ctrl+h in eclipse and replace something in many files?

  • over 2 years ago

    the first ticket concentrates on the properties as this is where i notices first ...

  • over 2 years ago in reply to flocsy🤠

    of course i cant say for sure but it looks the same for me - umlauts do not show anywhere (so internal fonts but also the property choices in garmin connect mobile) when they come from a string resource and i installed the app via the store (this way i still get correct umlauts shown when they have been received as http json response for example).

    when i build the prg and sideload the app it works as epxpected. same for the simulator.

    this leads me to think the iq build somehow treats strings.xml different the the prg build ...

    (still wondering why this only seems to be happening to me)