[MAGNOLIA-2748] i18n: bundles should be chainable in one or the other way (in the configuration) Created: 26/May/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1519 i18n should be definable at module level Closed
is related to MGNLSTK-221 A module-wide i18nBasename would be nice Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

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)



 Comments   
Comment by Philipp Bärfuss [ 26/May/09 ]

two good examples is the copy past of the messages bundles in:

  • newsletter
  • categorization

which define there own messages but would need the messages from STK too

Comment by Magnolia International [ 26/May/09 ]

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)

We might also want to take into account the fact that the latter is much more likely to have to be editable/configurable.

Comment by Philipp Bärfuss [ 10/Jun/10 ]

commons configuration has actually a very similar approach for including other properties files

http://commons.apache.org/configuration/howto_properties.html

Comment by Magnolia International [ 15/Sep/15 ]

This is somewhat obsoleted by the introduction of the new i18n mechanism in 5.2 (see MAGNOLIA-5268) – but the issue still exists, for components that extend others across modules. (cc czimmermann)

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:39:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.