Platform.Bible extension strings not in Crowdin

[imnasnainaec]

We need to add https://github.com/sillsdev/languageforge-lexbox/blob/develop/platform.bible-extension/contributions/localizedStrings.json to the https://crowdin.com/project/language-depot source files. Crowdin can handle the format and correctly extract the strings for translation, using their keys (the string ids) for context.

There are a couple complications:

• We only want the "en" section of localizedStrings.json considered for source strings
• The translations will be:
  • either downloaded one .json file per language, which need to be merge into their respective sections in localizedStrings.json;
  • or downloaded as a single XLIFF file, which we'll then need to convert into the right .json format

[myieye]

I don't see built in support for multilingual files in crowdin.
So, my understanding is that to use crowdin we'd need to map between localizedStrings.json and one-file-per-locale. We could do that either:

1. With this Crowdin app, for which we'd write a tiny script that lives in crowdin.
   ➕ Probably the simplest
   ➖ localizedStrings.json seems like a fairly weak format. E.g. I don't see anyway to include context for translators. That can be done directly in Crowdin, but it'd be handy if we can generate it locally with AI and push it.
2. With a script in our own repo that maps in the opposite direction.
   ➕ More control (e.g. we could use Lingui and add context locally)
   ➖ More work, but it still wouldn't be hard to whip up a script for this that GHA could also use to automate running it on Crowdin PRs.

[imnasnainaec]

I'd be interested in trying 1. CMFF with the FW Lite Crowdin project, but it would have to be added by the project owner, techops.