No-break spaces (u+00A0) are not used in drafts
Open
Nobody has claimed this yet.
enhancement
pipeline 3: preprocess
pipeline 6: infer
- Dominant language
- Python
- Stars
- 39
- Forks
- 7
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 5
Description
Some teams use the no-break space (u+00A0) in their translation, but our pipeline treats them (mostly) like regular spaces (u+0020) and does not generate them during inferencing for the test set or creating drafts.
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 tracing how the pipeline handles U+00A0 during inference for the test set and during draft creation. Compare those paths with regular-space handling and identify where no-break spaces are normalized or omitted. Done means translations containing U+00A0 preserve it and generated test-set outputs and drafts can produce it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100