Hi, Actually, now that you mention it, I think I ran into something like that when I was playing around with Myghty. I think I just changed the tag to have a separate end tag and kept going, but you're right, that is an IE issue.
I guess it it boils down to whether you want pristine templates and let Kid deal with browser issues, or whether you are willing to compensate for IE's special personality :-) in your templates so that you can have xhtml output.. I think I could go either way. I also think my only reason for wanting xhtml 1.1 strict output is so I can use the "valid xhtml" graphic from W3C. :-) This is probably not worth the hassle, but letting the developer choose their poison is a good idea, so it's good that we will be able to in 0.6. Thanks for the reminder! Krys Bob Ippolito wrote: > All versions of IE that I've used can't handle a <script src="foo"/> > tag, which is semantically equivalent (in XML-based markup) to > <script src="foo"></script>. For example, the markup in the wiki > tutorial uses this syntax, and would not work correctly in IE if not > using the HTML4 serialization. > > -bob > > On Oct 2, 2005, at 9:29 AM, Krys Wilken wrote: > >> >> This will be lovely! :-) >> >> (We are IE 6 only at work and I have not seen any compatibility >> problems >> with IE6 and XHTML, so I am unsure why I would want to stay with HTML 4 >> for that environment. I guess the HTML 4 setting for for compatibility >> with older browsers.) >> >> Thanks Fabian! :-) >> >> Krys >> >> Kevin Dangoor wrote: >> >> >>> On 10/1/05, Krys Wilken <[EMAIL PROTECTED]> wrote: >>> >>> >>> >>>> I ran into something similar where I wanted my pages to by xhtml 1.1 >>>> strict, but Kid's FAQ explained the 4.01 Transitional for the HTML >>>> serializer. I can accept that reasoning, but I was thinking that it >>>> would be nice if there was some way in TG to be able to choose the >>>> serializer. (i.e. HTML or XML) since Kid has both. >>>> >>>> >>>> >>> >>> You're in luck... TurboGears 0.6 has a new config setting: >>> # kid.outputformat=html >>> thanks to a patch from Fabian Neumann. >>> >>> >>> >>> >>>> Not sure if there are API differences between the two serializers >>>> and if >>>> that would cause trouble for TG. I guess some investigating is in >>>> order. >>>> >>>> >>>> >>> >>> Nope. It'll work just fine. I author all of my templates in xhtml. (I >>> render them in HTML 4 because much as I dislike IE, there are some >>> users of IE that I like :) >>> >>> Kevin >>> >>> >>> >>> >> >> > >
