sillsdev / sillsdev/languageforge-lexbox
Platform.Bible extension strings not in Crowdin
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9
- Forks
- 8
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 49
Description
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 oflocalizedStrings.jsonconsidered for source strings - The translations will be:
- either downloaded one
.jsonfile per language, which need to be merge into their respective sections inlocalizedStrings.json; - or downloaded as a single XLIFF file, which we'll then need to convert into the right
.jsonformat
- either downloaded one
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting platform.bible-extension/contributions/localizedStrings.json and the existing Crowdin source-file configuration for language-depot. Determine how to expose only the en section and whether per-language JSON or XLIFF downloads fit the repository workflow. Done means source strings are available in Crowdin and downloaded translations are merged into the corresponding language sections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- localization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100