Thread: Accessibility question: TTS and ligatures
View Single Post
Old 05-03-2018, 07:57 AM   #17
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: 80,197
Karma: 148951761
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 doubleshuffle View Post
I've decided to try and make my next upload to the MR library conform to accessibility standards. The text contains some ae- and oe-ligatures (which I am very fond of and would like to keep). Does anyone know if TTS programs are able to deal with them properly, or will I have to sacrifice them in the name of accessibility?
Versions of ADE/RMSDK 2.0.1 and later all support ligatures. So if you have fl in the text, you will be shown the fl ligature if the font supports it. So you don't need ligatures specifically in the text. Just let ADE/RMSDK do the ligatures.
JSWolf is offline   Reply With Quote