Limit interpret-as=address to numbers in road names

[bsudekum]

Came across a case where polly speaks N Street NW as North Street NW. The if-first-word-in-ref code we had in place for refs should also be applied to .wayName, .destination, .rotaryName.

/cc @ericrwolfe @frederoni @1ec5

[1ec5]

What if the street is named North S Street, East W Avenue or Northwest N Street?

This is symptomatic of a broader issue we have with Polly, which is that it keeps trying to expand abbreviations even though abbreviations are already expanded in OpenStreetMap. Can you look into whether there’s a way to specify in SSML that abbreviation expansion should be disabled?

[1ec5]

We can probably roll back #418, since it was address that was causing parentheses to be read aloud.

/ref #286 (comment)

[1ec5]

I think this will miss route numbers like NY 120A, in which 120A should be wrapped in interpret-as="address" in order to say “one-twenty a” instead of “one hundred twenty a”. How about wrapping a word in address if it contains a digit?

[1ec5]

FYI, this will miss any codes like A-35. OSM tagging conventions call for a space, as in I 35, but I do see some other regions using hyphens. We could harden this code by enumerating the string with String.enumerateSubstrings(in:options:_:) and byWord, or with String.replacingOccurrences(of:with:options:range:) and regularExpression.

[bsudekum]

@1ec5 current code produces something like given the names above:

<speak>
  <prosody volume='x-loud' rate='1.08'>
    Head east on NY <say-as interpret-as="address">120A</say-as> <say-as interpret-as="address">A-35</say-as>, then in 3 quarters of a mile , Turn right onto NY <say-as interpret-as="address">120A</say-as> <say-as interpret-as="address">A-35</say-as>
  </prosody>
</speak>

[bsudekum]

link to mp3: https://cloudup.com/c_X5YsKdCFh

[1ec5]

Nit: containsDecimalDigit would be more accurate.