RigPlane
Languages

Supported languages.

What is actually translated today — the app interface, the support channel, and the documentation. Three different surfaces, three different states. No marketing translations of anything we have not shipped.

Three axes, three states

Localization is not one thing. Below is the honest current state of each surface separately: the app interface (RigPlane Core and RigPlane Pro), the support channel, and the developer/operator documentation on rigplane.dev.

App UI

What the app shows.

Strings inside RigPlane Core (web UI) and RigPlane Pro (desktop shell).

English en-US
Source
Russian ru-RU
Complete
Japanese ja-JP
Pilot

Pro shares its preferred language with the embedded Core web UI, so the whole desktop app follows one selection. Change it in Pro under Preferences → Advanced.

Support

How we answer email.

Diagnostic reports, support email, GitHub Issues, Discord.

English
Complete
Russian
Not offered
Japanese
Not offered

Support is English-only. We do not promise localized response times in any other language. If you write to [email protected] in another language, we may still try, but it is not a service commitment.

Documentation

What rigplane.dev contains.

Operator and developer documentation, install guides, vendor notes.

English
Complete
Russian
Not offered
Japanese
Not offered

Community translations of documentation pages are welcome via PR to rigplane-core, but none are shipped yet for any locale.

What the labels mean

Source
The locale the developers write code in. English is en-US and is the reference text every other locale translates from.
Complete
Every translatable string has a translation. Glossary tokens (radio abbreviations, mode codes, units, brand names) are preserved. A native speaker has reviewed the result.
Pilot
Every translatable string has a translation, produced by an automated translator following community-standard ham radio conventions. Native-speaker validation is pending. The translation is useful as a foundation; rough edges are expected until a native operator reviews.
Not offered
This surface is not available in this language. We are not committing to a date.

What is intentionally not translated

Some terms stay in their original form in every locale, because that is how operators recognise them. Radio abbreviations and Q-codes (CW, SSB, FT8, QRZ, QSO, RTTY), mode codes, signal-report formats, frequency and SI units (MHz, kHz, dB, W), and brand and model names (Icom IC-7610, Yaesu FTX-1, Xiegu X6100, Lab599 TX-500, RC-28) are not localized. The full glossary is documented in the translator guide on rigplane.dev.

Helping with a translation

RigPlane Core is MIT-licensed and accepts community translation pull requests. The translator guide on rigplane.dev covers the file layout (frontend/src/lib/i18n/locales/<bcp47>.json), the glossary of preserved terms, and what review looks like for a new locale.

RigPlane Pro translations are produced internally by the team for now and are not open to community PRs.

This page

This page itself is English. Translating the public marketing site is a separate, larger commitment, and we have not made it. If that changes we will say so here, not before.