<Research>: Transliteration support for non-NLLB scripts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39
- Forks
- 7
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 5
Description
When a source/target language is written in a script that is not known to NLLB, drafting accuracy to/from that language seems to improve if the text is "transliterated" to Latin script using the uroman utility. However, the uroman utility is not bi-directional, so there's no way to generate predictions / translations in the original script.
Further research into the options for a bidirectional solution are needed, such as TecKit maps from WSTech. Research would also be useful to identify what scenarios can benefit from bidirectional transliteration (new languages in new scripts; new languages in existing scripts (which scripts?); etc).
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
No files or tests are named; begin by comparing the issue's uroman approach with bidirectional options such as TecKit maps from WSTech. Document which language and script scenarios benefit from bidirectional transliteration and what is needed to support predictions in the original script.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- internationalization, machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100