Normalize language codes to ISO-639-3 when creating extract files
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39
- Forks
- 7
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 5
Description
When extracting verse text from a Paratext project into an extract file, the file name is uses the ISO language code read from the project's Settings.xml file. These values vary between ISO-639-2 and ISO-639-3 language codes, making it more difficult to easily identify extract files in the same language. Normalizing the ISO language code from the settings file (to ISO-639-3) when assigning the file name would make the extract files easier to use.
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 at the extraction entry point that reads the project's Settings.xml and trace how its language code is used to name the extract file. Locate existing extraction tests, or add coverage alongside them, for both ISO-639-2 and ISO-639-3 settings values. Done means generated extract filenames consistently use the ISO-639-3 code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100