Quote:
Originally Posted by theducks
folk
I prefer to explicitly define my <p> tags only because I don't use only one style for <p>. If I see a raw <p>, I goofed  |
Yabbut, if you have a large group of similar paras, say, a simple first-line indent for a fiction body, wouldn't it be faster/easier just to use the base p for that, and then style your
other paragraphs however you want? Hell, Ducks, my love, if you saw one of our ePUBs, you'd have a cow. We determine the base p style, set it, and then ONLY class the other p classes. I mean, we have dozens of p styles in any given book--say, copyright-page, copyright-page-2em (space above the paragraph), copyright-page-no-space (flush-left, no top/bottom margin), copyright-page-center (just what it says), etc. Hell, that's just one page. (These aren't the actual class names; I'm making them obvious for the purpose of discussion). To me, from a trouble-shooting standpoint, I'm happier if I know that all the plain old, plain old p's are just that: the base. Whatever I decided that would be. Then I know that everything else is, well, something ELSE.
Quote:
And, no, I never intended to infer that one way would work and the other would not.
What I was trying to convey is the Device may ignore some styling in general, No mater how good your code, it ignores your CSS wishes
|
Yes, but...as I was saying, if it will ignore what is in your CSS, it will ignore what's in your CSS, won't it? I mean, if your device ignores, say, copyright-page-2em, it will likely ignore p, as well. It's more likely to ignore the other classes than what you set as P, in my opinion.
HOWEVER: we all know that there are a bajillion ways to make a book. Your way, my way, Wolfie the Curmudgeon's way...within certain reasonable standards, they all work. (Not counting emoties. I'm still recovering from that one.)
;-)
Hitch