Rixoffice speaks your language — literally. The entire interface ships in 19 languages, and switching takes one visit to Settings with no restart and no download step. This page lists what is available, how right-to-left scripts are handled and what a language change does and does not affect.
Available languages
The interface is fully translated into:
| Language | Notes |
|---|---|
| English | Default |
| Chinese (Simplified) | For mainland China conventions |
| Chinese (Traditional) | For Taiwan and Hong Kong conventions |
| Japanese | Full UI translation |
| Korean | Full UI translation |
| French | Full UI translation |
| German | Full UI translation |
| Spanish | Full UI translation |
| Portuguese | Full UI translation |
| Italian | Full UI translation |
| Dutch | Full UI translation |
| Polish | Full UI translation |
| Russian | Full UI translation |
| Arabic | Right-to-left interface |
| Hebrew | Right-to-left interface |
| Hindi | Full UI translation |
| Thai | Full UI translation |
| Indonesian | Full UI translation |
| Malay | Full UI translation |
The list spans the world's major script families — Latin, CJK, Cyrillic, Arabic, Devanagari and Thai — so mixed-continent teams can share one office suite without anyone working in a second language. The language is a per-device setting in all cases, so switching back and forth carries no penalty — pick the language that matches the work in front of you and change it whenever that changes.
Changing your language
- Open Settings from the home screen or any tab.
- Find the language section.
- Choose your language from the list.
- The interface switches immediately — no restart required.
That is the entire procedure. There is no language pack to download, no locale to configure at the operating system level and no separate setting for keyboard layout — the interface language is a single decision, applied everywhere at once.
The choice is stored per device, so a shared machine can have one user in German and the next in Japanese without touching each other's documents. On a personal machine, the setting sticks across updates and restarts, exactly as you would expect.
Because the interface is translated as a whole rather than partially, you will not hit a half-localized screen three menus deep. Dialogs, error messages, settings labels and the onboarding flow all follow the same language setting, which is what makes a non-English interface genuinely usable rather than a thin skin over English strings.
Right-to-left done properly
Right-to-left done properly is one of those features you only notice when it is missing. Arabic and Hebrew are not just translated strings over a left-to-right layout. Selecting either flips the workspace to right-to-left: sidebars, ribbons, tab order and dialogs all mirror, and the editors handle bidirectional text in your content. If you write Arabic or Hebrew documents, the interface finally points the same way your text does — ribbons on the right, reading order flowing naturally, and mixed Latin terms inside Arabic sentences rendering correctly.
For anyone who has worked in a word processor that treated RTL as an afterthought — mirrored menus but unmirrored dialogs, or toolbars that jumped when the text direction changed — the difference is immediately visible. Everything mirrors together, and nothing flips mid-sentence.
If your documents mix directions — an English quote inside an Arabic report, a Hebrew heading over Latin body text — the editors resolve the direction per run of text rather than per file, so the mixed content reads correctly without manual direction switches.
What a language change affects
- Changed: menus, ribbon labels, dialogs, settings screens and onboarding text.
- Not changed: your document content, file names, folder structure or cloud data. Language is purely interface.
This separation matters for mixed-language teams: a French interface can edit an English contract, and an Arabic interface can fill in a Japanese deck, all without any conversion step. Nothing about the file on disk depends on the language of the app that edited it.
It also matters for support and training. You can match your interface to a colleague's language while walking them through a problem over a call, then switch back — the menus land in the same places either way, so nothing needs relearning after the call ends.
Interface language versus document translation
Changing the UI language does not translate documents. If you need the content itself in another language, use the AI Translate feature in RixDocs, which converts document text into seven target languages — see AI translate. The two features complement each other: interface language for the person, translation for the document.
A practical example: a Portuguese-speaking editor can run a Portuguese interface, open a German source document and use AI Translate to produce the French edition — three languages in play, zero confusion about which is which.
For teams evaluating Rixoffice against regional requirements, the language list usually settles the interface question in one line: if your people read one of the 19, they work in it. Document translation then handles the content side, and the two together cover most multilingual workflows end to end.
What to explore next
- Interface overview — a tour of the workspace you just translated.
- Dark mode and theming — the other big appearance setting.
- Keyboard shortcuts — work faster in any language.