MobileRead Forums - View Single Post

JSWolf · 09-01-2019, 01:13 PM

Actually, I find it easier to just define p as what most p is going to be and use classes for when I need/want to change p. I don't like any CSS where you cannot change the order of the classes or it fails for work correctly. That makes things more complex and the idea is to keep the CSS as simple as possible. No need to make things more complex. body > p does make thing more complex as you should be using a header for the chapter titles.

Also, sections are ePub 3. Keep it simple and keep it ePub 2 compatible unless you can't. But the way it sounds, you might be making it more complicated. A lot of reading software doesn't do ePub 3 and if you make it be specifically ePub 3, it won't display properly. So the question is, do you really need to make this eBook ePub 3 specific?

09-01-2019, 01:13 PM	#29
JSWolf Resident Curmudgeon Posts: 80,043 Karma: 147977995 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	Actually, I find it easier to just define p as what most p is going to be and use classes for when I need/want to change p. I don't like any CSS where you cannot change the order of the classes or it fails for work correctly. That makes things more complex and the idea is to keep the CSS as simple as possible. No need to make things more complex. body > p does make thing more complex as you should be using a header for the chapter titles. Also, sections are ePub 3. Keep it simple and keep it ePub 2 compatible unless you can't. But the way it sounds, you might be making it more complicated. A lot of reading software doesn't do ePub 3 and if you make it be specifically ePub 3, it won't display properly. So the question is, do you really need to make this eBook ePub 3 specific? Last edited by JSWolf; 09-01-2019 at 01:15 PM.