mastodon - Link to source

One of the benefits of eSpeak-NG is that it doesn't make assumptions like reading "CUP" is Cuban Pesos (hello US OneCore voices) - but the flip side is that eSpeak will read the year 1987 as "nineteen hundred eighty seven". If you'd like it to read that as "nineteen eighty seven" & learn a little #regex on the way, then @fastfinge has you covered with the "Correcting Years With NVDA and Espeak" blog post: stuff.interfree.ca/2025/08/28/…

#NVDA #NVDAsr #Tips #Accessibility

Sam's Stuff - Correcting Years With NVDA and Espeak

stuff.interfree.ca
#Accessibility #nvdasr #nvda #tips #RegEx @🇨🇦Samuel Proulx🇨🇦

reshared this

in reply to NV Access

mastodon - Link to source

Brandon Tyson

I can't resist the temptation to discuss more OneCore oddities, we also can't forget the OneCore bug with reading ernesto, or have you been using applications where unchecking check boxes was necessary? Also fun fact. Microsoft David always uses its OneCore data even in SAPI5. Zira uses OneCore data in OneCore, but its older data in SAPI5. What this means, is that David will always exhibit these problems, but Zira will only if using OneCore and not SAPI.
⇧