I've been working on the source for 3.1.6, and so far found html tags in these files:
Display.cc
defaults.cc
TemplateList.cc
that will need to be changed to be XHTML compliant.
(As well as the default html templates.)
I've got things pretty much working, but still have a bunch of testing to do. Hopefully when I'm done I can provide notes and patches for 3.1.6
Pete
Gilles Detillieux wrote:
Yes, as Boyd reported, the missing closing option tags in template variables like FORMAT, METHOD and SORT, and anything generated by build_select_lists, will not be valid xhtml. The other things I found that won't pass are: 1) <input ...> tags generated by build_select_lists don't currently end with "/>", 2) the <br> tag separating multiple excerpts in Display::buildExcerpts() should be <br/>, and 3) ditto for the <br> tag separating description strings in the DESCRIPTIONS template variable. As long as you don't use any of these, you should be able to get fully xhtml-compliant output just by editing your templates. If you need to use any of these features above, you'll need to edit htsearch/Display.cc to fix the generated tags.Can anyone think of a reason not to do this for all future ht://Dig distributions? Are there some older HTML parsers/browsers that would have problems with a tag like <br/>?
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
