> <t:p>Paloose is a simplified (much simplified) version of ... </t:p> > > There is nothing here that indicates the final look (obviously). The > relevant template > > <xsl:template match="t:p" mode="inline-text"> > <xsl:element name="div"> > <xsl:attribute name="class">normalPara</xsl:attribute> > <xsl:apply-templates mode="inline-text"/> > </xsl:element> > </xsl:template> > > translates this into a simple HTML div > > <div class="normalPara">Paloose is a simplified (much simplified) > version of ... </div>
Argh! This is a particular pet peeve of mine. HTML provides the <p> element specifically for marking up paragraphs. By using a <div> you've removed any semantic meaning from the markup! It might as well not be HTML at all. You can apply the same CSS styles to any HTML element, so why not use something that carries a well-known semantic meaning that can be interpreted equally well by non-visual means, and that has a useful default styling for when your CSS isn't applied? Same goes for headings: <h1>, <h2>, etc. are much more appropriate than divs with special classes. I always find it a good exercise when building a site to view it without any CSS applied (in Firefox: View->Page Style->No Style), and if I can still clearly see the structure of the page's content (heading hierarchy, paragraphs, lists, etc.) then it's good. If on the other hand all the paragraphs and headings run together without any visual clues to their meaning (as happens with the Paloose site!) then I've probably got some work to do. Sorry to get off-topic, just hate to see <div> and <span> over-used in place of perfectly good semantic HTML. Nice software though! I look forward to giving it a try. :-) --Jason --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
