Some of the functions provided here should be filters to respect the Twig semantic

[stof]

tourl, toHtml and t at least should be filters rather than functions.

Note that it is possible to keep the function but deprecate it, to avoid breaking BC.

[moufmouf]

I understand for toUrl but I'm not sure about t and toHtml.

t can take several parameters (the translation key + substitution parameters), so I think I need it as a function, as filters do not take parameters (unless I'm wrong).
toHtml takes an object that has a toHtml method has a parameter. It feels weird to make it a filter as the input is not really some text.

However, I was not aware of the possibility to deprecate filters. That's really good news as at least half the functions here have been added a bit carelessly... :s I'm gonna deprecate a bunch of them right now!

[stof]

@moufmouf the translation key would be the filtered value, and substitution parameters would be filter parameters. Twig filters are taking parameters.

[moufmouf]

Ok, I was not aware that filters could accept parameters (it might be obvious, but there is no sample in the Twig doc: http://twig.sensiolabs.org/doc/advanced.html#filters

I'll change the t implementation then!

[stof]

One of the examples in the doc is using them:

{{ now|date('d/m/Y') }}