This post only applies if ...
1. you are using Ming.le User Settings of Language and Locale (other than using browser default) and
2. your Language and Locale setting actually differ.
If these applies to you, read on...
It's first important to note that to set Landmark's runtime language and localization settings for dates, numeric formatting we use only one of those values today, not both. This is similar to how browsers allow you set this, one setting (like see IE11's Language options) as an example.
So, we've fixed a couple of issues that had Landmark looking at the Ming.le User Setting > Language field rather than the Ming.le User Setting > Locale. In June expect your Locale setting to now be used.
Another issue we shored up was looking to the Landmark Actor IsoLocale value. In June, the Actor's IsoLocale is in play if Ming.le passes en_US (default) into Landmark. There was an issue not allowing that to work. Any other Locale passed into Landmark overrides the Actor setting.
