Multi language support on Vivoactive 3 (FW 3.30)

FSeifert,

Thank you for the report. I was able to reproduce this issue exactly as you described. It looks like it's in the device software as you suspect. I've created a ticket and pushed it to the vivoactive 3 team. I'll try and keep you up to date!

Thanks,
- Coleman

Thanks Coleman for fast tests. I thought I'm doing something wrong.
best regards
2aCD

unfortunately the problem still exists after new update 3.40 on VA3

I have encountered the same issue while developing the Crystal watch face for Vivoactive 3, which uses a custom font throughout:
https://apps.garmin.com/en-GB/apps/9...7-17cfa0f0081b

I have just completed a significant amount of internationalisation work, including for Chinese, as this has been requested by multiple users. As the localisation overrides work in the simulator, as FSeifert has mentioned, I was lucky to catch this issue on hardware before public release (why the hardware behaves so differently from the simulator is a separate topic...). The current public version uses Time.FORMAT_MEDIUM strings, which are known to be inconsistent (e.g. "Thur" instead of "Thu", even in English).

As this issue prevents me from releasing any updates for Vivo 3 (because all users will be forced to English), Coleman.ConnectIQ I'd be grateful if you could provide an ETA for the fix. Please let me know if you can think of any workarounds in the meantime.

Does this issue affect any other watches?

Thanks,

Vince.

As this issue prevents me from releasing any updates for Vivo 3 (because all users will be forced to English), Coleman.ConnectIQ I'd be grateful if you could provide an ETA for the fix. Please let me know if you can think of any workarounds in the meantime.

Does this issue affect any other watches?

Vince,

I have some experience regarding the va3 and this localisation issue in 3.30-3.40

Here is what I have found:

The language isn't forced to English. It actually forces the language that was set on the device before the upgrade to 3.30 / 3.40.

In your case your language on your actual va3 was set as English before you upgraded to 3.30 / 3.40, and for that it always loads English resources regardless of the language you try after the upgrade.

I discovered this on a va3 that had Danish language set, and after the upgrade to 3.30 / 3.40, it always forces the Danish resources to be loaded.

Most users will already have the watch in their preferred language before upgrading, so for probably 95% of your users, the correct resources will be loaded.

I'd say it is safe to release. ;)

jim_m_58, HermoT,

Wow! I couldn't have hoped for two more helpful replies, so thank you both very much (would have tagged you properly, but I get an error on posting...).

That's some pretty creative problem solving in the linked article, and will no doubt save others, including myself, an awful lot of pain.

HermoT, the insight into the specific nature of the 3.30-3.40 upgrade problem is also very valuable, as I'd never have been able to work that out on my own, despite owning the hardware. Whilst I'm sure we'd all prefer that the language setting work properly(!), the information you've provided at least means that my project's no longer blocked.

Thanks again!

There's a bunch of stuff in the general developer forum that can help you with questions, and folks that can help when you can't find the answer.

Ditto!

Looking forward to seeing your apps warmsound

Cheers!

HermoT, it's taken me this long to realise that you were actually the first reviewer on my first watch face, so double-thanks for setting me off on the right foot!

Cheers!

HermoT, it's taken me this long to realise that you were actually the first reviewer on my first watch face, so double-thanks for setting me off on the right foot!

You're welcome! Glad to have you in our midst!