-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Polly pronounces “S” in ref as “South” #286
Comments
Do you have a screenshot of the problem? Abbreviations.plist is used for abbreviating, not for expanding abbreviations, and only on the road name (after any On the other hand, there is a geographical issue with Shields.plist, where |
I'm pretty sure the voice instruction said "South 94" |
That application uses Amazon Polly. It’s likely that Polly interprets “S” as “South” in this context. We can avoid that and similar issues by surrounding the ref in a |
We’re already marking up the ref to be interpreted as an address. I wonder if there’s a more appropriate interpretation here. /cc @bsudekum |
→ #334 |
@bhousel pointed out that, because of how many county roads in New Jersey are currently tagged |
The “S” as “South” case was fixed in #509. Not sure whether “A1(M)” still gets pronounced as “a one open-parenthesis em close-parenthesis”. |
#552 should’ve fixed the parenthesis case as well. |
In Saxony, Germany there are roads like
S 81
. Wikipedia has a list and here are some on the map.Right now these are extended to
South 81
instead of stayingS 81
(via this code).This is definitely a fringe problem (only 5000 km of roads in Germany have this abbreviation) but highlights issues with using abbreviation expansion of one place in another.
/cc @1ec5 @bsudekum
The text was updated successfully, but these errors were encountered: