[FOLIO-2870] Reversion of previously-correct strings in `en_US` locale Created: 10/Nov/20  Updated: 10/Nov/20

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

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

Sprint:
Development Team: None

 Description   

Sergiy Sergiyenko reported that strings in

{en_US.json}

were not being updated after a change was made to an existing key in

{en.json}. The Lokalise service updated their back-end code recently, and as a result there are some unknown number of changes to {en_US} that were missed.

For background: normally when an existing translation string is changed in {en} the value is automatically copied to {en_US} (and {en_GB} and {en_SE}). This issue meant that changes in approximately the last month were missed. I've performed a bulk copy of en to {en_US} (and etc.) and am loading those updates into GitHub now.

Normally, this would have been a non-issue. However, early in the FOLIO project I was using Lokalise to make small editorial changes to strings in {en_US}—capitalization errors, spelling corrections, etc.—rather than reporting them back to developers to fix in en. Unfortunately, Lokalise did not give me a way to select only recently updated source strings, so I had to make a bulk copy for all 10,248 keys in the FOLIO project apps.

Practical impact: you may notice instances where once-correct strings in the {en_US} locale are now incorrect. Please work with the developers to correct the issue in the source {en.json}

files (rather than making these changes directly in Lokalise).


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