View Single Post
Old 06-27-2016, 06:40 PM   #17
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,680
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by JustinThought View Post
What I'm advocating is a standard for the way the programming is presented, so that when the developer comes up with a cool presentation technique, it shows the same on Aldiko, Cool Reader, Moon+, and any other app you use; and the same on the dedicated e-readers.
I've understood this all along. I just fail to see:

1) why device/app manufacturers/developers would honor any such standard. They already disregard current format standards when they see fit; why would they honor a presentation--or ebook-coding--standard?

2) If such a standard were adopted, how would existing devices/apps handle newer layouts they're not equipped to display as per the standard? Would they have to decline to open a book if they determine they couldn't display it the way the standard requires?

My point is that it simply can't work. The same ebook will ALWAYS render differently on other devices/apps. Sometimes drastically so. Just like internet browsers.

It is what it is.
DiapDealer is online now   Reply With Quote