[FOLIO-1436] Reuse of translation key names not supported by Lokalise Created: 23/Aug/18 Updated: 12/Nov/18 Resolved: 23/Aug/18 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P3 |
| Reporter: | Peter Murray | Assignee: | Peter Murray |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: |
| Description |
|
There are several examples of where translation key names are reused across `ui-*` modules. For example, `meta.title`:
Lokalise imposes these conditions on translation key names (emphasis added):
In case you were wondering if Lokalise's notion of a "platform" would help us, it doesn't.
(Both quotes are taken from Localization workflow: best practices - Lokalise Blog.) When loading the translation files from GitHub to Lokalise, the impact is that Lokalise only remembers the last imported file as the location of a particular translation key. On export, that translation key is only exported to that file. For example, in the recent merge of translation keys from Lokalise into ui-users resulted in the removal of the `meta.title` key in the German translation file. |
| Comments |
| Comment by Peter Murray [ 23/Aug/18 ] |
|
Hang on – I may have an answer... |
| Comment by Peter Murray [ 23/Aug/18 ] |
|
Yes, flipping the "Differentiate keys by file" as István Bender suggested fixed this problem. |