Re: short_open_tag

KK>> Most browsers have no problem dealing with XHTML compliant HTML, that KK>> is, they handle <br/> and friends properly. Other XML requirements in KK>> XHTML are only additional constraints on case, on attribute quotes KK>> and the like. There's a little difference between "make any use of it" and "discard it as trash because they don't understand what it is". I asked about first (the only viable reason to do <br/> today and next 2-3 years on the Web), you are talking about the second. KK>> XHTML compliant code has the advantage of being parseable with KK>> XML parsers (of course) and thus being easier to handle with tools. KK>> You can parse XML without knowing a DTD, you cannot do this with KK>> SGML. I seriously doubt most of PHP users really parse their PHP pages with SGML or XML tools. YMMV, of course, but my experience hints me they don't. KK>> <? still is a violation of XML, and probably of SGML, too. There KK>> was and still is a reason for recommending the use of <?php. Again, there's a difference between "recommending because it sits well with SGML" and "forcing into people's throats by instantly breaking all their code". Again, most people don't care too much if their code is SGML-compliant, as they have no use of SGML-compliance as is (except that warm fuzzy feeling, of course). -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/ +972-3-6139665 ext.106