Kandralla wrote:GizmoGuy411 wrote:Penn for Pennsylvania was moved from the main list to the State abbreviation list where it belongs, along with other alternate state abbreviations. Yes we definitely want it removed from the TTS!
Am I correct in my assumption that this means that William Penn Highway will now be called "William Penn Highway" as oppoesed to "William Pennsylvania Highway"?
If so thanks, that was annoying.
GizmoGuy411 wrote:LittlestLou wrote:Co Rd is now pronounced as "Coe Road" and not "County Road". Also contrary to naming conventions on the wiki. Again, this is a new issue, not a problem up until this release...
Are you sure, because I could swear that it has been that way for a while. We have a ton of county roads in NW Ohio, and we have slowly been changing them to "CR xxx" as we canvas the rural areas. "CR" does get pronounced correctly as "County Road", and not to be confused with "Country Road".
AlanOfTheBerg wrote:xteejx wrote:Any chance we can have Saint back the way it was, ie St at the start. Annoying work if we have to change them all!
I don't think we should have Waze relying on positional pronunciation. It's just bound to fail. If we make it a standard that "St" is "street" and "St." is "saint" then we know exactly how it will be pronounced regardless of where it is in the street name.
jenncard wrote:Interesting. So the period also converts to a pause? Perhaps this might be an idea for the other post re: ramp naming.... "Exit 123: I-70 W. Grand Junction"
GizmoGuy411 wrote:WeeZer14 just found an issue in New York City with signs that say "NYC". Waze does not pronounce it properly at all.
I'm adding them all the list, however which of the following should we request:
a) NYC = "New York City"
b) NYC = "NYC" (the letters)
c) N.Y.C. = "New York City"
d) N.Y.C. = "NYC" (the letters)
I'm thinking b and c.
(As a side note, Excel says "New York City" for "NYC" and says the letters "N", "Y", "C" for "N.Y.C")
Users browsing this forum: No registered users