[jira] [Closed] (TAP5-2316) Support for message catalogs for JS modules

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-2316.
--------------------------------------

    Resolution: Invalid

Libraries can contribute to the global message catalog (since at least 5.3).  All pure-text  messages in the global catalog (those that don't appear to be message format strings) are available, localized, on the client.

Documentation forthcoming.

> Support for message catalogs for JS modules
> -------------------------------------------
>
>                 Key: TAP5-2316
>                 URL: https://issues.apache.org/jira/browse/TAP5-2316
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Jochen Kemnade
>              Labels: i18n, javascript
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)