Re^2: Template::Toolkit, look-and-feel and internationalization

[lachoy]

in reply to Re: Template::Toolkit, look-and-feel and internationalization
in thread Template::Toolkit, look-and-feel and internationalization

How does the FILTER usage work when you've got to pass parameters?

I've implemented something similar to this in OpenInteract2 -- you just call:

[% MSG( 'somekey', param1, param2, ... ) %]

...and that call gets replaced by the relevant lookup and replacement. Behind the scenes it's using Locale::Maketext, but that detail is irrelevant to the template creator.

[davidrw]

It's built to handle things like [% FILTER repeat(3) %]blah [% END %] -- Two starting points (with some good examples) are the FILTER directive and the Template::Filters docs.

[lachoy]

Nice! Learn something new every day...

[ruoso]

Just a little question... I saw that the | can be used for an alias to FILTER, but I didn't understood if this only applies to non-block directive... And if it's valid to remove the whitespaces... would the following be valid?
• [%|i18n%]Text to be translated[%END%]
• [%|i18n(10)%]You gained %d experience points[%END%]

P.S.: Is there an alias for [%END%]?

[deliria]

<EDIT>
Yes, that's valid
</EDIT>

Changing that to:
[% "Text to be translated" | i18n %]
and
[% "You gained %d experience points" | i18n(10) %]

respectively, would eliminate the need for the [%END%] tag. I also find this more readable.