[TAP5-2316] Support for message catalogs for JS modules

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 5.4
• Component/s: tapestry-core
• Labels: i18n javascript
• Assignee: Unassigned
• Reporter: Jochen Kemnade
• Created: 09/Apr/14 09:33
• Updated: 16/Apr/14 06:59
• Resolved: 15/Apr/14 22:25

Description

Content that is rendered in the client from JavaScript modules is quite hard to internationalize.
Either you can manually create a messages JSON object and pass it to the client via data attributes or the init function or you can add all the strings to the core message catalog and require that.
The latter is not possible for component libraries though as they do not have a message catalog.
The former is not possible for "utility" modules that do not have an associated Java class.
This could be solved by creating a virtual message module for every JavaScript module that has a corresponding .properties file next to it.

Issue Links

• relates to: TAP5-1140 Extend the support for JS localization from within the framework to users of the framework.