View Single Post
Old 02-09-2009, 11:29 PM   #78
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
This special interpretation applies only to <br/> tags which are direct children of the <body/> element, so just wrap everything in a <div/> and you should be fine.

The problem with <br/> is that it's a purely formatting element. HTML isn't really a formatting language, especially XHTML 1.x. Instead the markup language supplies semantic constructs -- tags for headers, paragraphs, quotations, etc -- and allows any formatting for those elements the designer wants using CSS. The <br/> tag doesn't really fit this paradigm, and is best avoided (IMHO, as yes -- it isn't yet deprecated).
what would happen if i just applied <div> text here</div> to a line of text? would the create a line break or a paragraph break? or do I need to add extra coding? And how would the html to LRF conversion go using those tags instead? Basically, I've concluded that while I may not go back and re-do the coding for my previous conversions I could try moving ahead with a new code that would work for LRF, Epub, and Mobi.

Thanks for your help.
Amalthia is offline   Reply With Quote