Thread: Kindle: Text-to-speech disabling has arrived
View Single Post
Old 05-18-2009, 12:49 PM   #56
tompe
Grand Sorcerer
tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.
 
Posts: 7,452
Karma: 7185064
Join Date: Oct 2007
Location: Linköpng, Sweden
Device: Kindle Voyage, Nexus 5, Kindle PW
Quote:
Originally Posted by elmoglick View Post
It may, but then it might only display words without vowels...

The only sure way is to remove the 404 entry.

El
Have you tested? Because the EXTH header can contain entries that a reader program do not know about and they will just be ignored. So changing the type of the EXTH entry should not affect functionality.

If a simple binary editor can trivially fix this then nobody can complain about mobi2mobi (I added a flag --allowtts to mobi2mobi...).
tompe is offline   Reply With Quote