ES Translations of Companion and Firmware partially performed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- internationalization
Research direction
Start by identifying the untranslated Spanish menus and buttons in the Companion and radio firmware; the issue does not name files or provide the proposed list. Ask the reporter for that list, then check the project’s translation workflow and relevant language files. Done means the agreed main menu and submenu items appear in Spanish in both Companion and firmware.
Written by the indexing model from the issue text.
Description
Is there an existing issue for this feature request?
- I have searched the existing issues
Is your feature request related to a problem?
ES translation of both Companion and the Firmware of any radio is only partially performed. Many menus, sub-menus, and buttons are remaining on English language, which makes very difficult for users non-English speakers to understand the function of the menus and buttons. Almost in every screen of the radio you may see elements untranslated. Same happens with some of the menus on Companion.
Describe the solution you'd like
I kindly request the possibility of translating at least the main options of the menus and submenus. I could produce a list of most of the items that are untranslated, if necessary.
Describe alternatives you've considered
No response
Additional context
No response
- Dominant language
- C
- Stars
- 2.4k
- Forks
- 614
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 67
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- 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 EdgeTX/edgetx
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug 🪲 triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
EdgeTX/edgetx#7412 · 2 comments ·
Maintainers usually reply within 1 day
-
bug 🪲 triage
Difficulty 2/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug 🪲 triage
Difficulty 4/5 3-5 days Newbie friendliness 43/100
Maintainers usually reply within 1 day
-
bug 🪲 triage
Difficulty 3/5 1-2 days Newbie friendliness 52/100
EdgeTX/edgetx#7970 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
containers/bubblewrap#826 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
Revivedx/SavageWindRecomp#488 ·
Maintainers usually reply within 1 day
-
needs-device
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
feature/themes QA/No release-notes/exclude tests tests/missing-coverage tests/test-quality
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
brave/brave-browser#60971 ·
Maintainers usually reply within 1 day