[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22778#action_22778
]
Grégory Joseph commented on MAGNOLIA-2748:
------------------------------------------
Another way of seeing this issue is by stating that "paragraph/template
descriptive messages (title, description, ...) are a different concern than
those messages used in templates", or by differentiating "authoring messages"
(paragraph description, template name, buttons suchs as "edit page header") and
"public messages" (those which are used in template scripts, such as "read on"
links, etc)
> i18n: bundles should be chainable in one or the other way (in the
> configuration)
> --------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2748
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2748
> Project: Magnolia
> Issue Type: Improvement
> Reporter: Philipp Bärfuss
> Assignee: Boris Kraft
>
> The issue appears if one wants to create a new paragraph based on a paragraph
> which uses already messages. In that case one would like to chain two bundles.
> After a short discussion we found several potential solutions
> A) use a special syntax in labels, .. bundle:key
> B) support @include tags in the messages files (postprocess file in
> DefaultMessagesImpl.getBundle())
> C) allow comma separated lists in i18nBasename definitions (could be a
> general feature of the MessageManager or part of the FreemarekerHelper)
> D) site wide template messages (register the bundles to use in a central
> place: MAGNOLIA-1519)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
