[MGNLUI-6942] Relocate UI compatibility i18n keys still being used in new apps Created: 09/Nov/21  Updated: 07/Dec/21  Resolved: 02/Dec/21

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

Type: Bug Priority: Neutral
Reporter: Maxime Michel Assignee: Jaromir Sarf
Resolution: Fixed Votes: 0
Labels: VN-Testing, maintenance, tech-debt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLUI-6945 Translate compatibility keys using Lo... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Sprint: UI Maintenance 2
Story Points: 5

 Description   

Although both UI & DAM have been translated to German, French, Italian and Spanish, there are many keys in the compatibility module that are still appearing in the app. They should be relocated to the non-compatibility module so they can be translated.

This is easily verifiable by using DAM in one of those languages on the nightly.

Example: move these keys to this location.

 


Generated at Mon Feb 12 09:41:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.