skill-weather misinterprets city location Geelong/Jalang about skill-weather

[penrods]

Short term answer: Set you device's location to Geelong at home.mycroft.ai so you don't have to say that explicitly. It defaults to looking at the weather for the device's geo location.

Getting to where you can pronounce Geelong is not a Weather specific issue, is is general STT. Getting domain-specific terminology into all sorts of skills is a real issue, but not something that will be solved specifically here.

[KathyReid]

I was pondering this the other day. This might be a bit of a ramble, but here goes ...

Individual users will each have an individual "context" in which they operate - for Kathy that context is Geelong, on timezone UTC +1000hrs, in Australia, with a preferred language of en-AU, in the state of Victoria, country of Australia.

User 'Jane' might have a very different context. She could live in the town of Alnwick, in the county of Northumberland, in the United Kingdom, on timezone +/- 0000hrs, with a preferred language of en-GB.

Even though Kathy and Jane both speak English natively, their "contexts" are very different. Kathy's hometown of Geelong is pronounced (IPA for English) - dʒɪˈlɒŋ. Jane's hometown of Alnwick is pronounced ænᵻk. The accents in the different towns are very different, especially vowel sounds.

Although Kathy and Jane could set the 'home' location for their Device to their hometown, Mycroft almost needs to be 'primed' that when Kathy says something like JIH-long she means Geelong and when Jane says AN-ik she means Alnwick. Kind of like type hinting, but for STT.

It would also mean that STT would be primed to hear different vowel sounds - Northumbrian vowels are very different to the "flattened" vowels of Australian. Different confidence scores could be given depending on the "primed" STT words.

I have no idea if this is possible, but it got me thinking.