dedup unicode and unicode-full
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- rust, yaml
- Domain
- accessibility
Research direction
Compare the unicode and unicode-full YAML files first, then trace the program that swaps their contents to understand how it handles duplication. Confirm the intended placement of duplicate entries and how the speech engine represents “lambda”; done means the duplicate data is removed from unicode-full.yaml and the pronunciation is correct.
Written by the indexing model from the issue text.
Description
It looks like there is duplication in the unicode-full and unicode files. But that's for another day (feel free to get AI to find the duplication and remove it -- typically it should go away in unicode-full.yaml. There is another issue to swap around what goes where. I'm not sure if the program that does that handles duplication well.
AI says that it is written as "lambda" but it sounds more like "lam-da" (as in English). Hopefully the speech engine does this correctly.
Originally posted by @NSoiffer in https://github.com/daisy/MathCAT/issues/789#issuecomment-5772143469
- Dominant language
- Rust
- Stars
- 114
- Forks
- 85
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 77
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from daisy/MathCAT
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug rules
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
discussion
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
discussion translation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
daisy/MathCAT#675 · 1 comment ·
Maintainers usually reply within 1 day
-
feature request for vector from O to APossibly taken @moritz-gross claimed this 9 days ago. Openenhancement good first issue rules rust
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
daisy/MathCAT#621 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
`categorize_command` has no `uv` arm, so every `rtk uv …` row counts as `other` in the ecosystem mixOpenarea:api bug good first issue priority:low
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
area/cli kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
good first issue open-endedness: low type: new feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100