I think the method described here ( for Nook) also works for T3
http://www.pigsgourdsandwikis.com/20...ook-color.html
it seems you need to add
adobe-text-layout: optimizeSpeed;
to the css for main body style- which will usually be called "calibre" if you've run a calibre epub to epub conversion
so it will not work for DRM'd books but from my initial tests it does seem to be working for books that calibre can process.
I added it to a test book which I then eyeballed in ADE v2 on PC & all the hyphenation seems to have gone away.
& adding that line should be backwards compatible for other readers, it's a "harmless" line if the epub reader engine does not understand it, then it should just be ignored ( that will also need testing but I did 1 quick test - see enxt sentence)
I put same book on t2 & t3, same font etc , after adding the CSS to the book, & compared same page on each - hyphenation has gone, no obvious untoward effects.
(I did note that in a couple of places the T3 put s one word less on a line, so the T3 full page is 1 sentence shorter than the t2 full page. - I guess that is because the justification calculations code has changed - both readers had everything set to defaults )
I would appreciate feedback/help with testing; if it works it will fix my only real issue with T3 & it's not too much hassle to do, as I can probably automate it via Calibre extra CSS
I cant see any way to teach the t3 to add this extra css line - it will have to be done for each book, before sideloading.
http://www.pigsgourdsandwikis.com/20...ook-color.html
it seems you need to add
adobe-text-layout: optimizeSpeed;
to the css for main body style- which will usually be called "calibre" if you've run a calibre epub to epub conversion
so it will not work for DRM'd books but from my initial tests it does seem to be working for books that calibre can process.
I added it to a test book which I then eyeballed in ADE v2 on PC & all the hyphenation seems to have gone away.
& adding that line should be backwards compatible for other readers, it's a "harmless" line if the epub reader engine does not understand it, then it should just be ignored ( that will also need testing but I did 1 quick test - see enxt sentence)
I put same book on t2 & t3, same font etc , after adding the CSS to the book, & compared same page on each - hyphenation has gone, no obvious untoward effects.
(I did note that in a couple of places the T3 put s one word less on a line, so the T3 full page is 1 sentence shorter than the t2 full page. - I guess that is because the justification calculations code has changed - both readers had everything set to defaults )
I would appreciate feedback/help with testing; if it works it will fix my only real issue with T3 & it's not too much hassle to do, as I can probably automate it via Calibre extra CSS
I cant see any way to teach the t3 to add this extra css line - it will have to be done for each book, before sideloading.