Postal (or zip) codes are not parsed correctly #387
Description
When using the 'navigate' skill it is often useful to use a post code (I am in the UK; US equivalent would be a zip code).
So I might say "Navigate to SW1A 2AA" (or "Navigate to 90210").
Dicio parses the letters correctly but treats each one separately, so it opens Navigation and searches for 's w 1 a 2 a a'. This is not understood (at least by Google maps) so I have manually select the top search result. US zip codes seem even worse - '90210' is parsed as '9 0 2 1 0', which Google treats as lat / lng coordinates and tries to direct me to the middle of Benin (this may be a shock if you were trying to get to Beverly Hills).
I realise this is quite a nuanced issue as sometimes people might want to parse letters and numbers as space separated, and sometimes not. Personally I would have thought that usually if you are spelling something out you would want the letters to be parsed as a single word, but I'm sure there are other use cases.
Great work on the app, I have been wanting to play with a voice assist for a while, but I didn't like the idea of sending the commands off-site for processing.