Hi Martin,
for more context what I need is "full" localization support for js
templates, similar to the support provided for components:
1- by allowing to have localized js template files per page. E.g.: my.js,
my_es.js, my_fr.js
2- by automatically solving messages in the template (without passing a
variables model with all the messages). E.g.: var x =
'${message:someResourceKey}';I already solved the 2nd one by overriding PackagedTextTemplate#asString() and overriding MapVariableInterpolator#getValue(). but now I need to localize the template file names themselves as mentioned in point 1. Thanx! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/support-for-L10N-in-templates-tp4479741p4485558.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
