German (de) translation

[b14ckyy]

German (de) translation

Adds full German localization and makes it selectable in the language dropdown.

Changes

• locale/de/messages.json – complete German translation (2263 keys, structure identical to en).
  • 1912 keys translated; technical terms intentionally kept in English where the FPV/INAV community uses them (e.g. Flight Controller, ESC, VTX, Gyro, Throttle, Failsafe, RTH, LOITER, MSP, CLI, UART, Blackbox, TPA, RSSI, flight-mode and CLI variable names).
  • Replaces a stale partial translation that was ~94 % untranslated English placeholders (fell through to the en fallback in the app).
• js/localization.js – register 'de' in availableLanguages so it appears in the language selector (language_de = "Deutsch" already existed).

Known follow-up (out of scope, separate PR)

The redesigned LED Strip tab has hardcoded English UI text (tabs/led_strip.html) with no i18n keys: "Quick Presets", the ①–④ step headers and their instructions, the X-Frame/Cross-Frame/Wing preset buttons, "/ 128 placed", and "Edit palette colors". Localizing these requires adding new keys across all locales, so they are deliberately left for a follow-up.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[github-actions]

Branch Targeting Suggestion

You've targeted the master branch with this PR. Please consider if a version branch might be more appropriate:

• maintenance-9.x - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.

• maintenance-10.x - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x

If master is the correct target for this change because it should never be included in any release, no action is needed.

---

This is an automated suggestion to help route contributions to the appropriate branch.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Configurator test build ready — commit 06e7d59

Download build artifacts for PR #2657

Available platforms (scroll to the Artifacts section at the bottom of the run page):

• Windows x64 (ZIP, MSI) and x32 (ZIP, MSI)
• macOS arm64 (ZIP, DMG) and x64 (ZIP, DMG)
• Linux x64 (DEB, RPM, ZIP) and aarch64 (DEB, RPM, ZIP)

A GitHub login is required to download artifacts. Build is for testing only.

[sensei-hacker]

Just an FYI for contributors: The tentative schedule for INAV 10 is to have a full release in mid December. That means RC2 needs to be in early to mid November, which places INAV 10.0RC1 at September 1. Please plan to have any new features for INAV 10.0 ready for RC1 no later than September 1. After that, 10.1 will follow about six to seven months later.