Localisation

[SunsetRunner]

Is toLocaleString() supported? I got the current locale from user-settings with locale.language and I tried to localise the date with toLocaleString(), but it didn't work.

How is the date localised in the Fitbit-watchfaces?

[Cmspooner]

I was wondering the same thing. I am able to use toLocaleString() to get commas to appear in my numbers that are greater than 1,000; but date.toLocaleDateString("en-us", { 'weekday': "short" })) and date.toLocaleDateString("en-us", { 'month': "short" }) always returns the date in year-month-day format.

[SunsetRunner]

Any news on this?

We should localise our apps and watchfaces for publication, so, how should this be done, if .toLocaleDateString() is not supported?

My solution is working, but not very elegant...

I haven't found anything about localisation in the documentation, so please help...

[JonFitbit · Accepted solution]

Sorry, the device only support ES 5.1 JavaScript, and toLocaleDateString() doesn't support the formatting options in this version.

[tomcgraves]

Is there a work-around? I want to display the time in HH:MM but not military time. I can slice off the seconds, but I really want 12-hour time.

[Gondwana]

If you've got a Date object, you should be able to use most of the functions listed here.

[SunsetRunner]

I think  

hours %= 12

should do what you want.

[tomcgraves]

Thanks!

Note that if (hours == 12) hours %= 12 returns 0, so

hours = ((hours %= 12) ? 0 : 12);

[SunsetRunner]

Does this work?

I'd have thought

hours = hours === 12 ? hours : hours%12;

[tomcgraves]

It works for me. I'm new to JavaScript, my background is in C++ and C#, so
things like "===" don't spring to mind yet. Thanks for your help!

[Gondwana]

(hours+11)%12+1

[SunsetRunner]

So midnight isn't 0 but 12 in 12h format? I didn't know that! 🙈😅

[tomcgraves]

I see now that Versa 2 has a different OS than Versa 3, so i retract my question. Sorry.