normalize_extracts: inserting spaces around embedded dashes is not always appropriate
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39
- Forks
- 7
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 5
Description
It's not always appropriate to normalize a word with embedded punctuation by inserting spaces before + after the embedded punctuation character.
A couple of counter examples from some of the target sentences in recent XRI datasets:
Original sentence: Niri poki pule kua-kua dabe edieng wao pihak ruha ihi partai nbe tenama tule hu'a gu mege wai.
Normalized sentence: Niri poki pule kua - kua dabe edieng wao pihak ruha ihi partai nbe tenama tule hu'a gu mege wai.
Original sentence: Ge a bi? nulu-waleng nu tenama dia wai dabe soro hulu mata nbe
Normalized sentence: Ge a bi? nulu - waleng nu tenama dia wai dabe soro hulu mata nbe
Normalizing the word 'kua-kua' to 'kua - kua', or the word 'nulu-waleng' to 'nulu - waleng' is not correct.
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 locating the normalize_extracts entry point and trace how embedded punctuation is normalized. Use the kua-kua and nulu-waleng examples as regression cases; done means those embedded dashes are not separated while the intended normalization behavior remains covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100