View Single Post
Old 04-10-2023, 03:19 PM   #47
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,796
Karma: 146391129
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by DNSB View Post
Very simple, Jon. If the TTS program saw <em>, it would speak the words until the closing </em> with emphasis however it might be defined in that program much as a human reader would do when reading text though the human is going to base the decision on other criteria. So in your first example, there would likely be no change on the visual italic <i></i> while in the second example, the semantic <em></em> would have a noticeable change and bright would be spoken with emphasis.

Once again, we are not talking about visual appearance (i.e. you reading the text with your mark 1 eyeballs) but rather accessibility where the text may be spoken, displayed in Braille, etc. The audio results will not be up to the results from the use of a full-fledged SSML but it is better than nothing.
But if the program did not read the <i> with emphasis, then there's a problem with the program doing the reading.
JSWolf is offline   Reply With Quote