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 | ||
| Template: |
|
| Sprint: | 5.1 Beta1- Frontend, 5.1 - Final |
| Description |
|
I used info.magnolia.i18n for the POC. However, there are a number of other i18n packages and functionality in different places. We'll maybe go for info.magnolia.i18n.system. See so http://wiki.magnolia-cms.com/display/DEV/Consolidate+package+names+for+various+i18n-related+features |
| Comments |
| Comment by Magnolia International [ 16/Sep/13 ] |
|
Went for info.magnolia.i18nsystem; i18n.system would encourage the use of the i18n subpackage independently, whereas there is currently no shared code. |