Use case:
You want to localize your app but you have many settings and also some texts on the watch face. If you translate all resource strings (settings and watch facing strings) then the size of the prg file becomes way too large if you localize towards many languages. (The size of the prg becoming too large is especially a problem on older watches, but also on newer watches this is not ideal as it takes longer to load the app if the size is larger).
Ideally I would only translate resource strings used on the watch face itself as this would give a good balance. I would not translate the resource strings of the settings (I'd just leave this to the default english) but if I follow this path then you bump into the issue that Garmin Express has not (properly) implemented the resource fallback mechanism. (The resource fallback system works properly in the other Garmin apps (Garmin Connect Mobile and in Garmin Connect Iq Mobile))
However the fact that Garmin Express does not implement the resource fallback to default language is a blocker for me to implement localized apps:
- I don't want settings pages without text
- I don't want to monopolize the storage of the device with my app
Could you please ask the team to PLEASE look into this issue?
To minimize the work for the Garmin Express team I have done a bit of legwork:
* I've uploaded a sample app to the store: https://apps.garmin.com/en-US/apps/79a4c6db-388c-4e6b-8556-b6e542eea960 (app is pending approval)
* (this app has partial localization in dutch
* to test the bug switch your windows language to dutch; launch garmin express and visit the settings of the app
(The issue is only present for those languages you have indicated you are going to support in the manifest)
