As a developer I can annotate objects to be internationalized and let a framework do the rest
(MAGNOLIA-5268)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | i18n |
| Affects Version/s: | None |
| Fix Version/s: | 5.1 |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Sprint: | 5.1 Beta1- Frontend, 5.1 - Final | ||||||||
| Description |
|
There are a lot of places in our code where we use MessagesUtil. While many of those can be replaced by the existing new framework, there are still cases where a well-known key is desirable. We can wrap TranslationService and LocaleProvider into a simple component that translates a given key and is able to format parameters. |