- From: Leif Halvard Silli <lhs@malform.no>
- Date: Wed, 22 Jul 2009 15:40:16 +0200
- CC: Anne van Kesteren <annevk@opera.com>, Thomas Broyer <t.broyer@ltgt.net>, HTML WG <public-html@w3.org>
Anne van Kesteren On 09-07-22 14.49: > On Wed, 22 Jul 2009 13:48:41 +0200, Leif Halvard Silli: >> What does 'this does not work for Python' mean? That Python >> uses another embedding syntax? But the syntax is up to Python >> to decide and not an argument against those languages that >> consciously have chosen the PI syntax. > > It is indicative that "solving" this for PHP does not solve the > wider problem. However, I'm not at all convinced it solves the > problem for PHP. Only for very basic cases. I don't see that Python, having chosen another syntax, indicates anything other than another preference and coding style. And, w.r.t. to what it solves for PHP, that too depend on the coding style. We've already heard from Daniel that it solves a problem in WYSIWYG editors. >>> and also does not work in common PHP scenarios such as >>> <div<?php if($foo) { echo " class='bar'"; }?>> >> But since we are talking HTML and not XHTML, you could use >> >> <div class=' <?php if($foo) { echo " bar"; }?>' > >> >> and be valid. > > But that's not the same. Often it should be the same. >>> et cetera. >> As the HTML 5 draft says: What is possible to do in the DOM >> vs in text/HTML vs XHTML etc, may differ. > > I don't think the syntax of certain templating languages should > be of concern to the syntax of HTML or XHTML. Actually, it is PHP and Biferno that have chosen to use the PI syntax of HTML/XHTML. And not the other way around. Hence it should absolutely be a concern of HTML/XHTML to continue to support this syntax. I am counting 2 independent supporters of adding back support for the PI extension mechanism - so far. -- leif halvard silli
Received on Wednesday, 22 July 2009 13:40:58 UTC