bmitch3020 wrote:Any automated solution is going to result in a lot of one-off or edge cases that don't work correctly. I think the best solution is to provide a TTS input under the Label input. Use the default TTS rules if no values are provided, and show the expanded value. And if "customize TTS" or some other checkbox is selected, allow the map editor to put in plain English (or their language of choice) into the TTS box. E.g.:
Label: Dr. Martin Luther King Jr. St N
TTS: Doctor Martin Luther King Junior Street North
Label: N St.
TTS: N Street
Label: Geo Wash Pkwy
TTS: George Washington Parkway
This way the label can match the sign, but the editor can fix the TTS if we see the default isn't correct.
In another life, I dealt with TTS quite a bit. The idea of a 'TTS override' field is very common.
The first field should match the street signs as closely as possible, and be visible in the UI. the TTS field should default to empty, and only be filled in if the spoken TTS is wrong or pronounces something oddly. For instance, barberton OH is pronounced like barber-ton (think haircuts) but many TTS engines will pronouns it bar-burton (with the 'Berton' part emphasized for some reason.)
Anyway, +1 for the TTS override field.
Sent from my Kindle Fire using Tapatalk