[EAS] Test-To-Speech must be allowed - NOW!

[Tom Spencer]

Not 100% sure I agree...

Just recently, Weather Underground implemented a switch in their 
forecasting - and broke the working TTS I had running.  The most serious 
problems were caused by the change from typed-out words to 
abbreviations.  WSW for west southwest, for example.  The most-humorous 
renderings though are in the wind speeds:  "5 minus 15 MPH" (MPH has 
already been "learned" to be read as "miles per hour", but how does one 
render a dash as "to" without also changing the rendering of temperatures?

" low temperature will be to five F to to fifteen F"?  (low temperature 
-5 - -15)??? (Hopefully, they'd input it as lows tonight will be 5 - 15 
below F; "F": I can teach out...)

<sigh>  All it would take is for someone to input txt msg frm 2 sav bw 2 
ipd & brk tts 4evr1

SVR TS WRN 4 Mt Olmps ar fm 4:45 2dy rn ltng hi wnds pos 

Will your boxes all properly convert that string, as-is, right now?  And 
remember, there's no standard vocabulary for txt msgs beyond a few 
common words.

Richard_Rudman wrote:
> As you all know, the FCC's Part 11 Fifth Report and Order that Text-To-Speech (TTS) EAS messaging will not be allowed at this time saying in so many words that the technology is not ready yet. The Broadcast Warning Working Group disagrees. Here's why. Washington State has already implemented TTS, and it works!

--