[FOLIO-2657] Move translation keys in Lokalise from one git repo to another Created: 25/Jun/20  Updated: 14/Jul/21  Resolved: 14/Jul/21

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Peter Murray Assignee: Peter Murray
Resolution: Done Votes: 0
Labels: i18n, lokalise
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:

 Description   

As brought up by Jason Skomorowski, when a UI module is refactored to move the functionality into, say, a plugin or component library, it would be less work for the translators to have a script that moves translation values to the new location rather than deleting existing and adding new keys.



 Comments   
Comment by Peter Murray [ 14/Jul/21 ]

I faced this earlier today, I think there is a reasonable process for handling this that doesn't involve creating a script that calls the APIs. If this happens, follow these steps:

  1. make a copy of the translations from the old location
  2. rename the enclosing directory to be the name of the new module
  3. in Lokalise, use the "Filter" by filename function to select and delete the keys from the old location
  4. in Lokalise, remove the old location GitHub integration and add the new (with just the en.json file defined, as normal)
  5. in Lokalise, make a pull request to copy in the `en` labels and values
  6. in Lokalise, upload the directory of other translations (ensuring the enclosing directory has the new name)

With this method in place, I'm closing this issue until this happens so often that a script is more advisable than this manual process.

Generated at Thu Feb 08 23:22:17 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.