Review French navigation file
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- yaml
- Domain
- localization
Research direction
Open the French navigate.yaml in the French folder on the main branch and review the entries after t:, Prefix in say-command, and the Move2D translations in the named rules. Compare the French wording with the English examples and verify that dans, hors de, fin de, and début de are used consistently. Done means the file's listed translations have been checked and any needed corrections are committed.
Written by the indexing model from the issue text.
Description
Hi @olivierthiffault
@NSoiffer noticed that the French translation was missing the file navigate.yaml. The rules in this file control the speech when you are navigating inside expressions.
Neil has made a French navigate.yaml in the French folder in the main branch, but it needs to be checked. Would you have the time to do this, possible before Friday? It would be great to have the file checked before the release, but it's understandable if you don't have the time :)
The following words are translated and need to be checked:
The words after t:
In the rule say-command the words after Prefix.
In the rule into-or-out-of-mtr, the word after the equal sign in the match statement: match: "$Move2D = 'dans'"("dans" is the translation of "in")
There are many instances of the structure:
French: Move2D: "'dans'"
English: Move2D: "'in'"
There are many instances of the structure:
French: Move2D:"'hors de'"
English: Move2D: "'out of'"
There are some instances of the structure:
English: Move2D: "'end of'"
French: Move2D: "'fin de'"
There are some instances of the structure:
French: Move2D: "'début de'"
English: Move2D: "'start of'"
- Dominant language
- Rust
- Stars
- 114
- Forks
- 85
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 42
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.
More from daisy/MathCAT
-
discussion
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
enhancement good first issue rules rust
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
discussion rules
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug needs check rust
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug question
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bitcoindevkit/bdk-ffi#1125 ·