Improve Smarty Delimiter issue - #522

Consider this test:
<option value="{$id}"<{if $menu_id == $id}> selected='selected'{/if}>{$title}</option>

With that solution, I expect that no tags will be converted resulting in an error. :(

There is always a price to past sins :) Someone thought the non-standard smarty delimiters were a good idea. I think the ability to use examples from the manual, and builtin support in IDEs make ditching the legacy delimiters an even better idea. Hence the change.

The filter code is to make it easier to test modules from 2.5. It isn't a long term feature. It is pretty easy to spot where it will have problem in new development, and a change in whitespace will fix it.

Rather than introduce a more complex solution with inadequate consideration, this just improves the detection in a number cases.

In modern IDE, like the PhpStorm, you can set the delimiters yourself, so this is not a problem anymore, especially since we've switched to .tpl extensions.
But being able to copy and paste examples from tutorials is definitely a good thing.

In modern IDE, like the PhpStorm, you can set the delimiters ...

But that is still a barrier, and there are a lot of IDE's besides PhpStorm. If it works out of the box with the default settings, that is a win IMO.