[MAGNOLIA-6417] Add support for new I18N mechanism Created: 15/Oct/15  Updated: 27/Nov/15  Resolved: 27/Nov/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Espen Jervidalo Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MAGNOLIA-6181 Expose i18n functionality via context... Closed
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)
Epic Link: deprecate old i18n

 Description   

Use the same context name to ensure seamless migration if possible. Otherwise use new context e.x. i18nfn.

Concept for keys is needed.


Generated at Mon Feb 12 04:14:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.