[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: |
|
||||||||||||
| 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 |
| Comments |
| Comment by Philipp Bärfuss [ 26/May/09 ] |
|
two good examples is the copy past of the messages bundles in:
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
or by
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 |
| 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. |