[MAGNOLIA-5268] As a developer I can annotate objects to be internationalized and let a framework do the rest Created: 27/Aug/13 Updated: 15/Sep/15 Resolved: 16/Sep/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | i18n |
| Affects Version/s: | None |
| Fix Version/s: | 5.1 |
| Type: | Story | Priority: | Critical |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | i18n | ||
| Σ Remaining Estimate: | 2d | Remaining Estimate: | 2d |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | 2d | Original Estimate: | 2d |
| Issue Links: |
|
|||||||||||||||||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||||||||||||||||||||||||||||||||
| 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)
|
|||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | language bundles | |||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | 5.1 Beta1- Frontend, 5.1 - Final | |||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 2 | |||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Up until Magnolia 5.0, we were relying on code calling info.magnolia.cms.i18n.MessagesManager in each and every place that needed translation. |
| Comments |
| Comment by Magnolia International [ 25/Sep/13 ] |
|
Reopening - adding convenience method for "known keys". Not convinced this is the way to go, but it'll help getting rid of basenames and calls to MessageUtil. |