Quote:
Originally Posted by JSWolf
...
I want to know why it is most ePub reading software feels it's OK to toss out the CSS?
|
You've seen most of the CSS out there....it's junk...and that's being unfair to junk. The easiest way for an app reader to display a book "well" is to ignore the junk and go with some basic css that it applies to all books.
Unfortunately, not all people like the same viewing options those readers use...so, to some, iBooks or Moon+ are acceptable, while others think they are trash. I clean up the css on all books that I read. That means, like you, I want a reader app that honors the publisher's (me -ish) css. The vast majority of people don't even know what css IS and are happy with the basic functions that you get with Books or Kindle or whatever.
...Then you have the 1, or 2, people out there - the VERY vocal few - who are never happy with anything unless it does exactly what they want, how they want it, when they want it, in the right color...or it's "unprofessional" and "unfinished".
Yes, there are things I would like to have fixed in Marvin but nothing else has come out that can hold a candle to Marvin's functionality
as an ePub reading App.... until there is I'm happy using Marvin to
read books - which is what it was intended to do despite the desires of some - and I don't feel the need to whine about it!
