[MAGNOLIA-5318] Tool to help with migration of existing objects Created: 16/Sep/13  Updated: 08/Mar/19  Resolved: 08/Mar/19

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

Type: Improvement Priority: Neutral
Reporter: Magnolia International Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: next
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
supersedes MAGNOLIA-5300 Prototype tool to help with migration... 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)
Date of First Response:
Epic Link: language bundles

 Description   

The tool should analyze a given object and ideally

  1. modify/create message bundle files (based on existing translations with non-standard keys, hard-configured texts, ...)
  2. generate a list of jcr properties "to be deleted" - which could be used for update tasks
  3. re-generate the bootstrap file where this object was originally configured

The 1 point can be realized by further instrumenting objects via a subclass of the i18nizer. The last 2 points are unfortunately probably hard to achieve without instrumenting Node2Bean (so we can know where a given Java property comes from in JCR, since it won't necessarily be a 1:1 mapping (references and extends))



 Comments   
Comment by Magnolia International [ 16/Sep/13 ]

A prototype has been committed for MAGNOLIA-5300, which keeps track of "tasks" to do while navigating the UI. It can be used in two ways
Using a script and passing it an object to "inspect". See info.magnolia.i18nsystem.tools.GenerateTranslationFilesImpl
By replacing the system implementation of info.magnolia.i18nsystem.I18nizer by info.magnolia.i18nsystem.tools.ToolingProxytoysI18nizer (can be configured via magnolia.properties for example)

Comment by Daniel Lipp [ 02/Jul/14 ]

Set unassigned and open as nobody will tackle soon.

Comment by Mikaël Geljić [ 08/Mar/19 ]

most old-style dialogs with i18nBasenames have been phased out long ago; unclear which objects left would be worth a migration by now.

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