2012/2/22 Christopher Schultz <ch...@christopherschultz.net>: > On 2/21/12 3:43 PM, Konstantin Kolinko wrote: >> 2012/2/22 André Warnier <a...@ice-sa.com>: >>> Pid wrote: >>>> >>>> On 21/02/2012 13:59, Jim Showalter wrote: >>>>> >>>>> Hi. Thanks for the timely response. I wasn't certain if I >>>>> should post this to the group or not. I can repost for the >>>>> archive if you want. >>>> >>>> >>>> Yes. Always to the list. >>>> >>>>> Here are some examples. >>>>> >>>>> The worst offender (in my opinion) is >>>>> http://tomcat.apache.org/tomcat-7.0-doc/config/context.html. >>>>> The tables don't word wrap at all and I can't begin to get >>>>> the section on my screen without the need for horizontal >>>>> scrolling. Other sections in the configuration >>>>> documentation word wrap to different degrees. I like to >>>>> increase the font size slightly and read the documentation by >>>>> just scrolling down. If I have to go back and forth too much >>>>> it is very distracting. >>>> >>>> >>>> Ugh. That is definitely wrong. I will take a look later on as >>>> to the cause. >>>> >>> >>> By the way, for the page in question, my HTML-checker lists 147 >>> errors (not warnings), the few first of which being : >>> >>> line 59 column 5 - Error: end tag for element "P" which is not >>> open line 78 column 11 - Error: end tag for element "P" which is >>> not open line 111 column 10 - Error: end tag for element "P" >>> which is not open line 137 column 5 - Error: end tag for element >>> "P" which is not open line 154 column 5 - Error: end tag for >>> element "P" which is not open >> >> That is usually caused by nesting <ul> or <ol> inside a <p>. A >> list should not be nested in a paragraph, or the validator will >> complain. > > Many (all?) XSLT processors will emit <p /> (for example) if there is > no content in a <p></p> pair. I know that definitely doesn't work in > many (all?) web browsers, even in XHTML mode. In our XSLTs, we have > <xsl:text> </xsl:text> nodes in places like these where otherwise the > results are ... unacceptable (like in a <script></script> pair where > there is no body at all but we must have an end-tag).
XSLT does not know how tags can be nested and it does not know that end tag for <p> is optional. It happily prints <p>See items in my list: <ul><li>item</li></ul></p>. It is exactly what is written in the source XML. A strict HTML validator will say that <p> ends when <ul> starts. A correct HTML will be <p>See items in my list:</p><ul><li>item</li></ul> Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
