By default, most of the template sets use the Smarty strip_tags function on the home page stories; this removes all HTML. You could modify the template to remove the strip_tags function if you like. The reason for this is to use a subset of the text in the page; without stripping the tags, you'd have to do some fancy HTML parsing to ensure that you didn't, for example, truncate the text in the middle of a tag.
I went into the blog_item.tpl file of the template I was using and removed the "strip_tags" from the line "{$page.page_text|strip_tags|truncate:300}". It screwed up the pagination pretty bad. But probably fixable through css.
Will give a cross-browser expanding height container with a min height of 100. This allowed me to play with how I truncated page-excerpts. I can not take credit for the above hack, but can't remember where I found it.
By default, most of the template sets use the Smarty strip_tags function on the home page stories; this removes all HTML. You could modify the template to remove the strip_tags function if you like. The reason for this is to use a subset of the text in the page; without stripping the tags, you'd have to do some fancy HTML parsing to ensure that you didn't, for example, truncate the text in the middle of a tag.
I went into the blog_item.tpl file of the template I was using and removed the "strip_tags" from the line "{$page.page_text|strip_tags|truncate:300}". It screwed up the pagination pretty bad. But probably fixable through css.
I had to use a CSS hack to get the text box height right depending on how the text was truncated.
min-height: 100px;
height:auto !important;
height: 100px;
Will give a cross-browser expanding height container with a min height of 100. This allowed me to play with how I truncated page-excerpts. I can not take credit for the above hack, but can't remember where I found it.