You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2013/07/25 23:29:49 UTC
[jira] [Closed] (TAP5-1140) Extend the support for JS localization
from within the framework to users of the framework.
[ https://issues.apache.org/jira/browse/TAP5-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1140.
--------------------------------------
Resolution: Invalid
Please define more exactly what you need. Also 5.4 goes a long way towards this by exposing the application message catalog to the client side via the t5/core/messages module.
> Extend the support for JS localization from within the framework to users of the framework.
> -------------------------------------------------------------------------------------------
>
> Key: TAP5-1140
> URL: https://issues.apache.org/jira/browse/TAP5-1140
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Shankar Prasad Jha
>
> The support for picking up the appropriate js file for localization exists in the tapestry framework and is being used for localization of tapestry.js. But this feature is not exposed to the applications using tapestry. The methods of RenderSupport interface which provide the ability to add the JavaScripts and CSS do not take locale as the argument. For applications using JS libraries like extJS it would become very simple to localize their applications after addition of this support.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira