> {my_var|Trans|html} # Translated and then apply HTML escaping
Yes, trivial example is easily taken care of there. How about this
trivial example:
Hello {name}.
Where the Hello needs translation?
Actually, in some languages who thing needs some translation because
the name may come before Hello. Forcing every translation into the
JSON isn't very nice to the template writer. If you overdo that, you
end up with
{html}
as the whole template! <wink>
> I think if i18n can be done without adding any concepts to the
> language, that would be awesome, and it looks like it can.
I don't think so, but it's just a decision to make on whether json-
template wants to do it or not
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "JSON
Template" 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/json-template?hl=en
-~----------~----~----~----~------~----~------~--~---
