[MAGNOLIA-7391] System i18n: Template definition's 'title' should be i18n-ized comparable to 'labels' & 'description' of form-fields or apps. Created: 10/Oct/18 Updated: 06/Jun/23 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | i18n |
| Affects Version/s: | 5.6.7, 5.7.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Christian Ringele | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | headless-team-support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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: | |
| Epic Link: | AuthorX Support |
| Team: |
| Description |
| Comments |
| Comment by Mareike Schulz [ 15/Oct/18 ] |
|
Hello @Christian Ringele, |
| Comment by Robert Šiška [ 24/Nov/20 ] |
|
The component and pages titles can now be i18nized. The area title i18n keys are not prefixed with module name. See RenderableDefinitionKeyGenerator#keysFor(). Since each page template defines their own areas, consider incorporating page template name into the key too. How it looks: templates.areas.areaName |