View Single Post
Old 04-15-2012, 07:46 PM   #17
Keroberos
Zealot
Keroberos ought to be getting tired of karma fortunes by now.Keroberos ought to be getting tired of karma fortunes by now.Keroberos ought to be getting tired of karma fortunes by now.Keroberos ought to be getting tired of karma fortunes by now.Keroberos ought to be getting tired of karma fortunes by now.Keroberos ought to be getting tired of karma fortunes by now.Keroberos ought to be getting tired of karma fortunes by now.Keroberos ought to be getting tired of karma fortunes by now.Keroberos ought to be getting tired of karma fortunes by now.Keroberos ought to be getting tired of karma fortunes by now.Keroberos ought to be getting tired of karma fortunes by now.
 
Keroberos's Avatar
 
Posts: 128
Karma: 238654
Join Date: Aug 2009
Device: Kobo Mini (4GB), Nook Classic wi-fi, iPod Touch (Bluefire Reader)
Quote:
Originally Posted by ProDigit View Post
And I hope some programmers might read this thread and decide it indeed benefits to not make everything mandatory, but just imply a code within reader software/firmware, that if some specific line of code is not present, a standard pattern will be followed.
I think they should have done that from the start; Like why does every epub needs to have a mimetype file and a container.xml, if for most books these files are identical?
This makes no sense, you are wanting to remove xhtml from the epub in an attempt to make it use less resources, but you want the e-reader programmers to add more code to their readers to correct for the missing bits you think aren't necessary, that kind of code uses resources--probably more than you could save by removing the xhtml restrictions. Web browsers allow for incorrect html because they have a lot of code in them to help correct broken/buggy html.

The epub spec is more strict so they can be opened with the most minimal hardware/software requirements.

Last edited by Keroberos; 04-15-2012 at 07:52 PM. Reason: clarity
Keroberos is offline   Reply With Quote