View Single Post
Old 03-19-2020, 04:07 PM   #6
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,025
Karma: 147977995
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Another font related thing that bothers me is the base font size set to small and what might be large is set to medium and what would be small is set to x-small. I was editing a book like that earlier today.

Another thing (not font related) that I don't like is the same styles duplicated with different names such as tx1, tx, fmtx1, fmtx, amtx1, and amtx. That's 6 classes that could be done in just 2. Also, these catch all CSS have been known to cause problems in older Readers because of the older software. I've seen recently, 496 extra classes being removes removing unused CSS. This is just ridiculous. I could come up with a nice simple CSS that would handle most use cases and then build the eBook from there using those styles and adding in any styles needed that do not already exist. When done, just remove the extra CSS and it's a nice well coded eBook as most ebooks do not need any sort of complex code. Plus, it would mean that eBooks from that publisher would have a similar/same look. eBooks do not have to look like the pBook.
JSWolf is offline   Reply With Quote