Quote:
Originally Posted by Sharkus
Probably us, ie; Kobo.
I think that when books are loaded onto the system there are some automated things that happen to the books, and I believe that adding the kobo css files is one of these things.
There were changes last year to the css, and books were being reprocessed. With the number of books we have, that can take some time.
Another thing to take into consideration is that any css changes do need to be evaluated on the various platforms to ensure they do not have unwanted behaviour. For example, a change that makes things better on eInk devices could cause a problem for an iOS device. I do recall iPhone and iPad css files, so there can be some device specific customizations, but anything generic we have to be very careful with.
|
Lets hope that Kobo drops the Linux Qt platform for coming new ereader devices and starts using Android as OS. I'm not saying that Android is better but as Android and iOS are the OS used on tablets it is the most logical step to reduce the number of platforms and (possible) rendering differences.
A good switch moment would be the release of a full epub 3 complient e-ink reader. Not just firmware wise but also hardware wise.
A full epub 3 complient reader needs at least have audio (speech) capabilities as this is a major part of the new epub 3 standard. I don't think I'll will use it myself very often but as multimedia is part of the new standard it should be capable to handle this.
Motion video will remain problematic as e-ink screens are different from LCD screens. But these hardware limitations don't apply to audio.