qwaletee wrote:How about one LESS space instead? Northern VA/Frederick instead of Northern VA / Frederick

While is does work, as well as any combination so that there is one space in front or of in back of the slash, I agree with sketch that for visual appearance and text wrapping we should not use any of these combinations.

Regardless, we hope to have it fixed, as the problem is more widespread than the examples mentioned in past posts.

qwaletee wrote:Have we ever had a problem with X=10th before? Per the UR below, the X in Malcolm X Blvd was being pronounced "tenth." I don't know if this is an isolated occurrence. I imagine if it is a problem, it could be resolved by changing "X" to "X." (with a period).

https://www.waze.com/editor/?zoom=5&lat ... 35&endshow

"Malcolm X Blvd" is actually being pronounced, "Malcolm the x Boulevard".

The error has been submitted to Waze.

Latest tests:

(REVISED 2014-06-10)
Small round-up of some other test results tonight:

"BUS" says "Business"
"BUSN" says "Business"
"Dr" says "Drive"
"Dr." says "Doctor"
"FM" says "eff emm" and no longer say "Federated States of Micronesia"
"FM 123" says "Farm to Market 123"
"FM-123" says "eff emm 123"
"Int'l" says "International"
"Int'l." says "International" (old abbreviation)
"Intl" says "International"
"Intl." says "International" (not requested)
"Jr." says "Junior" (old abbreviation. Resubmitted for insurance)
"Mt" says "Mount"
"Nat" says "National" (old abbreviation to be removed)
"Nat." says "National" (old abbreviation)
"Nat'l" says "National" (old abbreviation but resubmitted to correct pronunciation)
"Natl" says "National" (old abbreviation)
"Natl." says "National" (old abbreviation)
"N" says "North" (also tested with "I-35E N")
"NE" says "Northeast" instead of "Nebraska"
"NE-123" says "Northeast 123"
"Neb" says "Nebraska" (old abbreviation)
"Penn" says "Pennsylvania" (to be discussed)
"Penn<space>" says "Pennsylvania" (to be discussed)
"Penn x" says "Penn x"
"QEW" says "Queen Elizabeth Way"
"Q.E.W." says "cue eee double-u"
"RM" says the letters "R" and "M"
"RM 123" says "Ranch to Market 123"
"RM-123" says "eff emm 123"
"RM 123" says "Ranch to Market 123"
"SH" says "ess aitch"
"SH 123" says "ess aitch 123"
"SH-123" says "State Highway 123"
"St" says "Street"
"St." says "Saint"
"Ste" says "Sainte" (as used in Canada and possibly elsewhere for Saint".
"Ste." says "Saint"
"Thwy" says "Through-way"
"TR-123" says "Township Road 123"
"Twp" says "Township"
"X-ing" says "Crossing"

sketch wrote:

AlanOfTheBerg wrote:

GizmoGuy411 wrote:"Nat" says "National"

This should be removed. It's not a good abbreviation and there are "Nat" streets in the US.

"Nat'l" should say "National". But yes, "Nat" should not. We really should be more careful with these.

I was not clear in the list. "Nat" was NOT our submitted request. It is an old abbreviation that always said "National". And yes it should be removed.

It was added to the list to show all the abbreviations we current have for an item.

Please recheck the list above, as I have revised it and added a few more and have added some notes.

We may need to reconsider some other additional old abbreviations.

sketch wrote:

GizmoGuy411 wrote: "NE-123" says "Northwest 123"

I hope this is a typo!

I'm sure enough it was a typo that I changed the post.

I had 15 min to get on the forum and read some posts and try to test, and the TTS server is down. So more later.

jdeyoung wrote:I ran across the following UR:
https://www.waze.com/editor/?lon=-88.01 ... 33&env=usa

@report:The street name is correct. It is "SR-7 / 159th St". But it says "State Route Seven Thousand One Hundred Fifty Ninth Street".

For those unable to see that UR.
Have there been any recent changes to fix this? I searched and couldn't find anything related to this particular thing. And if this isn't TTS issue per se, what would be the recommendation to fix?

I've been testing this for a few days, and have more tests to go. So far, here is a progress report with some interesting test results. (For those not aware, a "%20" in the text is a space.)

"Exit to SR-7 / 159th St" Tests in the format; TEXT SUBMITTED = TTS RESULTS

SR-7%20/%20159th%20St = state route seven thousand one hundred and fifty nineth street

SR-7%20/%20159st%20St = state route seven thousand one hundred and fifty nine street street

SR-7%20/%205013st%20St = state route seven <pause> five thousand thirteenth street
(notice that it ignores the first "st" in this example)

SR-7%20/%205013nd%20St = state route seven <pause> five thousand thirteenth street
(notice that it ignores the "nd" in this example)

SR-7%20/%205013rd%20St = state route seven <pause> five thousand thirteenth street
(notice that it ignores the "rd" in this example)

SR-7%20/%205013th%20St = state route seven <pause> five thousand thirteenth street
(notice that it ignores the "th" in this example)

SR-7%20/%205012th%20St = state route seven <pause> five thousand thirteenth street
(notice that it ignores the "th" in this example)

Observations:
- Although I was able to remove the "Exit to " from the tests, I did not yet work to narrow the test further.
- Numbers from 0 to 999 produce the error. Numbers from 1000 to some untested limit do not. Further testing is needed for digit count rather then actual numbers, such as "0999" vs "999".
- "...st, ...nd, ...rd, ...th" as number suffixes are usually ignored, in favor of what the actual number would say. The "...st" is an exception for some cases that I need to test for again.
- At one point in the tests I heard "Saint" for "st" (no period). I will need to test further to discover it again.

On going problems with "N" not being pronounced as "North" STILL!

I'll try to test this issue more to resubmit it AGAIN to Waze.

The two other strange issues mentioned earlier are still not submitted to them, as testing has been tenuous at best lately with the ongoing zero byte TTS file returns as many of you have noticed in the beta clients.

GizmoGuy411 wrote:On going problems with "N" not being pronounced as "North" STILL!

I'll try to test this issue more to resubmit it AGAIN to Waze.

The two other strange issues mentioned earlier are still not submitted to them, as testing has been tenuous at best lately with the ongoing zero byte TTS file returns as many of you have noticed in the beta clients.

Initial tests are not confirming the problem:

http://www.gizmoguy411.com/Waze/TTS/Gar ... wy%20N.mp3

http://www.gizmoguy411.com/Waze/TTS/New%20Jersey%20Tpke N.mp3

Could you provide segment Permalinks so they can also be tested?

qwaletee wrote:Have we ever had a problem with X=10th before? Per the UR below, the X in Malcolm X Blvd was being pronounced "tenth." I don't know if this is an isolated occurrence. I imagine if it is a problem, it could be resolved by changing "X" to "X." (with a period).

https://www.waze.com/editor/?zoom=5&lat ... 35&endshow

Although I had recently submitted the "Malcolm X" issue to Waze, I have since removed the submission as there is a larger issue with Roman Numerals that needs to be addressed. In another thread elsewhere, I posted the following:

GizmoGuy411 wrote:While testing other TTS issues, the "Malcolm X" issue was mentioned again in the TTS test thread.

Here are the very inconsistent results I found testing just a few Roman Numeral examples:

Fred IV = Fred eye vee
Fred X = Fred ex
Fred XIV = Fred fifth
Louis IV = Louis eye vee
Louis X = Louis ex
Louis XIV = Louis fifth
John IV = John the forth
John X = John the tenth
John XIV = John the four-teenth
Malcolm IV = Malcolm the fourth
Malcolm X = Malcolm the tenth
Malcolm XIV = Malcolm the four-teenth
Mark IV = Mark eye vee
Mark X = Mark ex
Mark XIV = Mark fifth

Curiously the results for [Malcolm X] are correct for Roman Numeral usage, but wrong for what we need for that particular name,whereas other names with "X" say "ex" as in the letter x.

We may need to use [Malcolm "X"] to get the results we want, in order to differentiate from Roman Numerals usage. This would be consistent with the use of quotes around N, E, S, and W to get the letters pronounced instead of the cardinal directions.

Also note that for some names "XIV" is pronounced "fifth" and other others "fourteenth".

dbraughlr wrote:Whether Louis XIV is read as lewis ex eye vee or lewis fourteenth, it won't be perfect.

I think we want C, D, I, L, M, V, and X pronounced as letters. It seems that Roman numerals are the exceptions and should require special notation if used at all.

While the logic that the Roman Numerals are the exceptions, and therefore should require special notations seems correct, we have to remember that we have already have set a precedence to use quotes around the letters N, E, S, and W, to get the them pronounced as letters instead of the cardinal directions.

Therefore we may need to follow suite for the letters used for Roman Numerals too.

Of course there are other conflicts to consider as well including: (examples using valid Roman Numerals only, and not every combination of the letters used in Roman Numerals)

CD = cd or 400 ?
CM = centimeter or 900 ?
DC = District of Columbia or 600 ?
MD = Maryland or 1500 ?
MI = Michigan or 1001 ?
MIX = Mix or 1009 ?
MM = millimeter or 2000 ?

So maybe Roman Numerals could use a period after them instead of quotes to differentiate them.