View Single Post
Old 06-08-2023, 06:05 AM   #131
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,073
Karma: 147983159
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by Faterson View Post
Not at all – it's the no. 1 feature I'm looking for in a quality e-reader app: the ability to override the original CSS easily, because I'm not interested in the original CSS in the least.

Both Moon+ Reader and Marvin are great in allowing the easy override of original CSS, which is what makes them such excellent e-reader apps.

This is the biggest, most delightful difference between printed books (duh...) and e-books: e-books allow all readers to be their own typographers. How? By supporting easy override of the original CSS.

Yes, I know, Jon, that you're obsessed with original CSS and "publisher's style", but you should realize that you're in a tiny minority of users with that preference. Most readers of e-books including myself don't give a damn about original CSS and "publisher's style". In all my years of using Marvin and Moon+ Reader, I have never switched on the "Publisher's Settings" button in either of them. Not once. I'm simply not interested in seeing the "publisher's layout" in the least. I wish to read e-books just how I wish to see them displayed – not how the publisher would like to display them for me.

That said, I have nothing against e-book readers supporting "Publisher's Style" and original CSS just like you want it. But it should be clear that this is a minority concern and that most users wouldn't even notice that such a feature was available in the app, and they likely wouldn't properly appreciate it.
Quote:
Originally Posted by DNSB View Post
For me, Moon+ Reader is atrocious excuse for an epub renderer. To even get Moon+ to make some use of the epub's CSS, you end up digging down multiple menus. And yet, there is a rather vocal crowd proclaiming that it is the greatest thing since sliced bread and insisting any issues with Moon+ should be fixed by the epub publishers and not Moon+'s developers.
I agree 100%. It's not an opinion. It's fact.

ePub formatting is not about overriding the CSS. It's about following the CSS. I feel sorry for you because you don't get this.
JSWolf is online now   Reply With Quote