[FOLIO-1968] Replace ui-vendor with ui-organizations in Lokalise configuration Created: 15/Apr/19 Updated: 03/Jun/20 Resolved: 17/Apr/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Peter Murray | Assignee: | Peter Murray |
| Resolution: | Done | Votes: | 0 |
| Labels: | i18n, q2-2019 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: |
| Description |
|
| Comments |
| Comment by Peter Murray [ 16/Apr/19 ] |
|
Now done. One consequence was that the English strings were automatically assigned to keys in all languages that didn't otherwise have a translated string. (This happened because the existing "vendor" translations on GitHub were imported one time to save effort for translators that had already completed their work.) |
| Comment by Peter Murray [ 16/Apr/19 ] |
|
Aliaksei Chumakou pointed out that changes that were made to `en.json` didn't show up in the `en_.json` files during the rename process (such as replacing "Vendor" in a string with "Organization"). This was an artifact of how all of the locale files were loaded as part of the deletion and re-adding of the Git repos. A workaround is to copy all of the `en` values to the `en_` locales, and then to mark the non`en_*` locales to "Unverified" so translators have to review them. For the next time this happens, let's try this: when adding the renamed Git repo into Lokalise, first import the non-`en` locales, then go back into the Lokalise integration configuration, remove the non-`en` locales, add just the `en` locale, and pull the Git repo again. That should have the effect of triggering the language auto_fill for English languages and marking changed keys as "Unverified" for all languages. |