View Single Post
Old 02-10-2009, 03:46 PM   #80
Amalthia
Wizard
Amalthia does all things with Zen-like beautyAmalthia does all things with Zen-like beautyAmalthia does all things with Zen-like beautyAmalthia does all things with Zen-like beautyAmalthia does all things with Zen-like beautyAmalthia does all things with Zen-like beautyAmalthia does all things with Zen-like beautyAmalthia does all things with Zen-like beautyAmalthia does all things with Zen-like beautyAmalthia does all things with Zen-like beautyAmalthia does all things with Zen-like beauty
 
Amalthia's Avatar
 
Posts: 1,188
Karma: 32196
Join Date: Jan 2007
Location: Anchorage, AK
Device: Sony Reader PRS-505, PRS-650, PRS-T3, Pocketbook HD2
Quote:
Originally Posted by llasram View Post
The tags are just places to hang CSS off of. The <div/> tag creates a block-level element with no extra margins or indent by default, so with no extra CSS it will just make whatever is within the element have line breaks before the start tag and after the end tag.

But what I was suggesting was literally just put the entire document in a single <div/>. Try right after your <body> tag adding a <div> tag and right before your </body> tag adding a </div> tag. That will make sure that none of your <br/> tags are direct children of the <body/> element.
actually, that's kind of brilliant and if it works then it'll make my life so much easier for converting documents. Will try it tonight.

Um, not to beat a dead horse but just to be sure. Will this affect converting to LRF? Or should my previous <p> and <br> work like they have been so far?

Mostly, I just want paragraph indents for <p> and no space between paragraphs. And <br> to just add a line break. I'm kind of shooting to have a uniform standard for mobi, lrf, and epub.

Again thanks for your help! Obviously, I still have much to learn about html and css.
Amalthia is offline   Reply With Quote