MobileRead Forums - View Single Post - Telling a text-to-speech reader how to pronounce things?

Simons Mith · 11-08-2021, 06:17 AM

I have found some references to VTML online [https://static.carahsoft.com/concret..._Language.pdf] but it smells rather proprietary to me.

While that would let me do something like

Code:

<vtml_partofsp part="verb">record</vtml_partofsp>

to get 'record' pronounced as a verb, I have no idea how well it will
work in general.

Fixing these mispronunciations certainly counts as nice-to-have rather than vital, and anyway they're commendably rare considering it's a sci-fi book, but is there
a better way than vtml tags, which I only found out about yesterday? I'm thinking again about the typography tweaks for the units. I find conventional spaces to be too wide for my tastes, but IME the various narrow spaces are less well supported. I don't want to get a little bit fancy and then have those annoying boxes appear because some lame reader doesn't know what a figure space   is. OTOH my experience on rendering of custom spaces might be out of date now. Maybe they're reliably supported for the most part?

11-08-2021, 06:17 AM	#3
Simons Mith Member Posts: 23 Karma: 10 Join Date: Oct 2020 Device: none	I have found some references to VTML online [https://static.carahsoft.com/concret..._Language.pdf] but it smells rather proprietary to me. While that would let me do something like Code: <vtml_partofsp part="verb">record</vtml_partofsp> to get 'record' pronounced as a verb, I have no idea how well it will work in general. Fixing these mispronunciations certainly counts as nice-to-have rather than vital, and anyway they're commendably rare considering it's a sci-fi book, but is there a better way than vtml tags, which I only found out about yesterday? I'm thinking again about the typography tweaks for the units. I find conventional spaces to be too wide for my tastes, but IME the various narrow spaces are less well supported. I don't want to get a little bit fancy and then have those annoying boxes appear because some lame reader doesn't know what a figure space   is. OTOH my experience on rendering of custom spaces might be out of date now. Maybe they're reliably supported for the most part?