Functionality for differently-structured glossaries
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39
- Forks
- 7
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 5
Description
There is some code in the translate_glossary branch for translating USFM glossaries with out-of-order verses. The code works in its current state but it is not ready for wide use because it changes (and then changes back) the original glossary file.
This was originally to support one group of translation projects, so it really only needs to be worked on as needed. @davidbaines will have more information about the specific needs of the translation group.
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 the translate_glossary branch and its existing glossary-translation code. Confirm the specific needs of the translation group with @davidbaines, then define completion as supporting differently structured, out-of-order USFM glossaries without changing the original glossary file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- localization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100