[MGNLUI-2045] create new message-bundles each for every app / module (with texts) and define naming-convention for theses files Created: 06/Sep/13  Updated: 28/Sep/13  Resolved: 17/Sep/13

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

Type: Bug Priority: Neutral
Reporter: Christoph Meier Assignee: Christoph Meier
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon CNTCTSAPP-50 create new message-bundles each for c... Closed
depends upon MGNLCAT-93 create new message-bundles each for c... Closed
depends upon MGNLDAM-305 create new message-bundles each for D... Closed
depends upon MGNLUI-2080 Fix MessagesUtil.getKey usage for tho... Closed
is depended upon by MGNLUI-1826 i18n keys: As a developer I don’t hav... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: 5.1 Beta1- Frontend

 Description   

create new message-bundles each for every module (with texts) and define naming-convention for theses files



 Comments   
Comment by Christoph Meier [ 09/Sep/13 ]

for the naming-convention see http://wiki.magnolia-cms.com/display/DEV/i18n+in+Magnolia+5#i18ninMagnolia5-Message-bundles-naming-convention

Comment by Christoph Meier [ 09/Sep/13 ]

created a new branch (and pushed to remote-repo) for the modules

  • contacts-app
  • dam
  • ... (to be continued)
Comment by Christoph Meier [ 16/Sep/13 ]

to be relase-ready, this ticket will get the status "fixed", although STK hasn't its proper bundle, yet.
STK should rely on "old-stuff"-fallback-mechanisme meanwhile, hopefully

Comment by Christoph Meier [ 16/Sep/13 ]

to be relase-ready, this ticket will get the status "fixed", although STK hasn't its proper bundle, yet. (will be done later on with MGNLSTK-1240 )
STK should rely on "old-stuff"-fallback-mechanisme meanwhile, hopefully

Comment by Christopher Zimmermann [ 16/Sep/13 ]

REVIEW:
Please create a ticket in all affected projects. ie DAM, Contacts, Categorization. And link to this ticket as "is depended upon by".
Commits in those projects should not be made with a MGNLUI ticket in the commit message. Those commits should have gone against tickets in their own project.
Since commits are already made on this ticket - in the new tickets description, mention that commits are made against this ticket.

Comment by Christoph Meier [ 27/Sep/13 ]

app-security-messages hast some unneccessary-keys (duplicates) and some keys with again keys as avlues; and ui-generic-messages has generated keys - maybe form older version of key.generators - which seem obsolete.
=> i create a sub-ticket for that to clean up

Generated at Mon Feb 12 08:52:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.