Just to chime in, I tried to look at the way Django and Jinja templates (which are very similar to twig) are implemented and supported on editors.
In the case of Django and Jinja, they are supported on an .html file directly (there is no special extension, as there was with .twig files) http://jinja.pocoo.org/templates/#synopsis http://jinja.pocoo.org/integration/#textmate <http://jinja.pocoo.org/templates/#synopsis>So twig templates would be fine right now, if we were keep going on that route: foo.twig.html, foo.twig.xml, foo.twig.bar And the same goes for php templates. For all of them, we at least get syntax highlighting by default on any format used. The only rub I have is with html+php templates (which will be quite common) for: foo.php.html my first thought was to name them foo.php.php, to get all the benefits that come with the .php extension when it comes to pretty much any editor by default, and to comply with the <name>.<renderer>.<format> naming. This is only a personal opinion and I'm not suggesting it, just mentioning it for discussion, as this obviously looks even more weird and confusing, and likely a no-go for best practice. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
