[MAGNOLIA-1519] i18n should be definable at module level Created: 09/May/07 Updated: 15/Sep/15 Resolved: 15/Sep/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface, core, gui |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Obsolete | 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)
|
||||||||||||||||||||||||
| Description |
|
It would be very nice if a module could define its i18nbasename property, that would be valid/used for the whole module, i.e all dialogs, paragraphs etc. |
| Comments |
| Comment by Magnolia International [ 15/Sep/15 ] |
|
This is now irrelevant, since we obsoleted the use of basenames with the i18n mechanism introduced in 5.2 (see |