Localization API for views
bouncepaw opened this issue · comments
The current API is as such: there is a special module l18n (why L and 18? It's either I and 18 or L and 10, right?) and everyone calls it when needed.
While it's cool, it's hard to refactor and update (with new localizations, for example).
I want to try out a different l10n approach for views, along with #117.
I kinda figured this out. I am using std templates. Closing.