Sure, Chime. Clever hacks like John's could go into the screen reader, I suppose. I was simply pointing out the correct place for the fix is to give the TTS the ability to say digits and not numbers. The logic is fairly simple: Look at every string of characters, i.e. from white space to the next white space. If there are digits in that string add a space after each char in what you send to the TTS engine. That would get you ham radio call signs in addition to phone numbers, zip codes, and teleconference meeting IDs. It would, of course, read prices as digits, too. You'd hear three nin dot five two and not thirty nine decimal fifty two, or if the engine knows about dollar signs thirty nine dollars and fifty two cents. I could easily live with prices as digits to have more accessible phone numbers, zip codes, and teleconference IDs myself! :) Best, Janina Chime Hart writes: > Thank you Janina-and-John for your analysis. Janina, would you also think an > acception dictionary would also be purely dependant on each TTS? I think > Speakup-and-YASR are an only Linux screen-readers without such a dictionary. > Not sure if Storm reads this list, but I think Fenrir has a way of changing > pronunciations?I asked Storm about single digits-and-he rigged up something, > I think useing John's method, but it only works with Allison, not the > DecTalk software. And Janina, recently in addition to phone > numbers-and-zip-codes, we have Zoom ID numbers. I suppose as I think Kirk > created Speakup, he would be an authority on why these 2 features were never > implemented. > I would think since we can easily ajust caractors, we could also enjoy these > other options. > Chime -- Janina Sajka (she/her/hers) Accessibility Consultant https://linkedin.com/in/jsajka The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa Linux Foundation Fellow https://www.linuxfoundation.org/board-of-directors-2/
