Copy drift: "elegido" vs "seleccionado", and unexplained "hold" jargon
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #750 by @grunch — merged
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- dart
- Domain
- localization
Research direction
Start with the six ARB files mentioned in the issue and compare the payment-method selection strings and the invoice-hold wording. Read .specify/DESIGN_SYSTEM.md §9 for the existing terminology guidance. Done means the selection term is consistent across the files and the hold wording is understandable without unexplained jargon.
Written by the indexing model from the issue text.
Description
Problem
Wording drifts between screens:
- "chosen" vs "selected" for the same concept.
paymentMethodsChosenLabel"Elegidos" andpaymentMethodsChosenCount"1 elegido" on one side,paymentMethodsSelectedCount"1 método seleccionado" on the other, one screen apart. invoiceHoldNote/bondWhyHoldhighlight the English word "hold" as if it were a term the user should know.
Proposal
- Use one verb for payment-method selection in all six ARB files.
- Explain the hold invoice in plain words ("los sats quedan retenidos…") without the jargon. If the term stays, it should at least be explained where it first appears.
Consider adding a short glossary of the trade vocabulary to .specify/DESIGN_SYSTEM.md §9, so new strings reuse the same words.
- Dominant language
- Dart
- Stars
- 11
- Forks
- 9
- Avg merge
- 13h 4m
- Merged PRs (30d)
- 259
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 MostroP2P/app
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Add-invoice screen stays on "Sent, waiting for the node" after a late acceptance on a sell orderOpenbug priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area: ui
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MostroP2P/app#341 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
cat: puzzle
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
lichess-org/mobile#3826 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
saber-notes/saber#1844 ·
-
area-clientside-dartpad
Difficulty 1/5 Under an hour Newbie friendliness 64/100
Maintainers usually reply within 2 days
-
🚀 [firebase_core] Bump Firebase iOS SDK (12.19.0 → 13.0.0)Possibly taken @SelaseKay claimed this today. OpenNeeds Attention type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
firebase/flutterfire#18769 · 1 comment ·
Maintainers usually reply within 1 day