Quote:
Originally Posted by acabal
Unfortunately we're not going to be able to offer a whole lot of support for ADE 2.0.1, which looks like it's from 2012. Our compatible epubs should hopefully look somewhat acceptable on them, since in the "compatible" epubs we replace advanced CSS selectors with class selectors. But don't expect to be able to use our "advanced" epubs (which don't look good on today's software, let alone software from 2012) on any version of ADE this century.
|
That's untrue that you cannot get your compatible ePub to work with ADE. The reason your compatible ePub doesn't work is because of error(s) in the CSS. ADE ignores the CSS entirely if it finds an error and ADE has found an error. Your CSS is way much of a mess and too complex for the formatting of the eBooks. Why not just use simple CSS unless the formatting calls for something more complex. You "house" CSS needs to go as it doesn't work. And you
Quote:
|
I sympathize with people who bought into platforms that no longer offer updates. The ereader device space is one with little competition and even less technical enthusiasm, so options are limited and it can be frustrating to spend a lot of money on a device that just a few years later is stuck with obsolete software. But our project aims at modern standards, produced at a volunteer-time pace, so the amount of effort we can put in to supporting 8-year-old software that was bad even in 2012 is limited.
|
I have to say that these "modern" standards are not actually all that well supported. This is why your eBooks do not look good in most ePub reading software INCLUDING KePub on Kobo.
Your advanced ePub could work much better if you just got rid of all the "advanced" stuff that you do not need. The rule in making eBooks is to keep the code as simple as possible and you keep it as complicated as possible. Any professional eBook maker on Mobileread will tell you that your code is lousy.
As for people buying old platforms, a lot of people did not buy old platforms. They bough current platforms that are now not being supported and not everyone has the money to upgrade to a new Reader.
So please stop saying that you have to support the latest standard that are very poorly supported. You code is over-the-top and if you made your code properly your eBooks would work. They do not have to be made to only work with Books on iOS. So please stop say you cannot support ADE 2.0.1. You can if you wanted to. I cannot see most public domain books needing such code as you use. Your code is rubbish and needs to be scrapped and started over from the ground up.
Would you like me to take one of your eBooks and show you what compatible really means as you obviously have no idea what the word compatible means. It's not compatible. So please fix your listing and replace the word Compatible with Incompatible.