[MGNLCTS-69] As an editor I want i18n support with no trade-offs, to create multisite & multilanguage websites. Created: 19/Jun/15 Updated: 23/Aug/22 |
|
| Status: | Open |
| Project: | Content Translation Support |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Michael Büchele | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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: | |
| Team: |
| Description |
|
Essential i18n features are missing today, which makes a lot of customization necessary in projects: Examples:
|
| Comments |
| Comment by Antti Hietala [ 20/Mar/17 ] |
Supported. Each locale has language and country properties. They allow regional variations such as zh_TW for traditional Chinese or pt_BR for Brazilian Portuguese. https://documentation.magnolia-cms.com/display/DOCS/Language+configuration#Languageconfiguration-3.Definelocalesinsite |