Language Management¶
As of v1.7.0, IntroVox automatically supports every language Nextcloud knows about. The wizard's default tour content is translated via Transifex, and end users see it in their Nextcloud language without any admin action.
Admins can optionally provide per-language overrides — custom copy that replaces the default content for a specific language only. Overrides are the exception; for most installs you never need one.
How language coverage works (the short version)¶
- Default content comes from
$l->t('…')calls inlib/Service/DefaultStepsService.php. The English source strings are extracted totranslationfiles/templates/introvox.potand translated on Transifex (nextcloud/introvox). - End users always get the wizard in their Nextcloud language: the full language first (
pt_BR), then its base language (pt), and English when there is no translation for either. No language opt-in by the admin, no per-user gating. - Admin overrides live in the database (
oc_appconfig, keywizard_steps_<lang>). One row per language that has an override; if no row exists, the Transifex-translated default is served.
Adding a language override¶
- Go to Settings → Administration → IntroVox → Tours and click Edit steps on the Welcome tour.
- Click Add language override.
- Type to search the full Nextcloud language list, pick a language, click Add override.
- The step editor switches to that language and shows the current default content as a starting point.
- Edit the steps. The override row is created with the first change you save, not earlier — so picking a language and bailing out costs nothing.
The Language dropdown only lists languages that currently have an override (plus English, always). It will never show the full list of 100+ languages directly.
This page is about the welcome tour. A tour for an app works the same way in its own step editor, but only the built-in tours have auto-translated defaults. Any other app tour only has the steps you write, and users whose language has none get the tour's main language. A built-in tour gives users its translated steps as long as their language, its base language and the tour's main language have no steps of your own. See Tours.
Discarding an override¶
To send a language back to the auto-translated defaults:
- Select the language in the dropdown.
- Click Reset.
- Confirm.
The wizard_steps_<lang> row is deleted. Users in that language now see the Transifex-translated defaults — including any new translations that landed on Transifex since the override was authored.
How language detection works at runtime¶
When a user opens Nextcloud, IntroVox:
- Reads the user's language via
IFactory::findLanguage(null)(e.g.pt_BR): the language they chose, not one IntroVox happens to have a file for. - Makes a short list: the full language, then its base language (
pt_BR, thenpt). - Looks for an override in that order:
wizard_steps_pt_BR, thenwizard_steps_ptinoc_appconfig. - Override exists → serves the first one it finds as-is, after leaving out disabled steps and steps for groups the user is not in.
- No override for either → serves the default steps (
DefaultStepsService::getForLanguage()) in the first of those languages that has a Transifex translation, built via the NextcloudIFactorytranslator. If neither has one, the user gets English, never the server's default language.
So an override for pt also serves pt_BR users, unless pt_BR has an override of its own. Since 2.0.0: before, only the first two letters of the language were used, so an override or a translation for pt_BR or zh_CN was never shown.
See ApiController::getWizardSteps() and DefaultStepsService for the implementation.
Upgrade notes for installs coming from 1.6.x¶
In 1.6.x, opening the Steps tab silently auto-persisted the default tour content into oc_appconfig so that the reorder UX worked. As a result, most 1.6.x installs have six rows in the database (en/nl/de/da/fr/sv) that are byte-identical to the 1.6.x defaults at the time.
After upgrade to 1.7.0:
- Those six rows show up in the language dropdown of the welcome tour's step editor as overrides.
- The wizard keeps working — end users see no difference.
- However, those six languages won't pick up new Transifex translations until the override row is removed. The 1.6.x default copy stays frozen in the DB.
To get back to "everything served from Transifex" for any of those six languages:
- Open Tours and click Edit steps on the Welcome tour.
- Pick the language in the dropdown.
- Click Reset.
This deletes the row; from then on, Transifex updates flow through automatically.
If you'd actually customised one of those six languages in 1.6.x, leave it alone — it's a real override and Reset would discard your work.
The obsolete enabled_languages appconfig key is ignored by 1.7.0 code but left in the database for downgrade safety. You can remove it manually with:
Adding a language that isn't on Transifex yet¶
You don't need to wait for Transifex — the override flow works for any language Nextcloud knows about, even if Transifex hasn't translated the IntroVox strings for it yet. Just add an override, write the copy yourself, save. Users in that language will see your override; users in other languages keep seeing whatever Transifex provides (or English fallback).
If Transifex later adds a translation for that language, your override wins. Reset the override when you no longer need the custom copy.
Example use cases for overrides¶
- Region-specific tips: Dutch users get steps mentioning Dutch Nextcloud cloud providers; international users see generic Transifex-translated content.
- Tenant-specific wording: an institution wants "Welcome to ACME Cloud" instead of "Welcome to Nextcloud" for their users only.
- Translation gaps: a language Transifex hasn't covered yet — the admin writes it themselves as an override until a Transifex translation arrives.
See Also¶
- Multi-Language Support — Transifex integration details
- Transifex Integration — l10n workflow
- Managing Tour Steps — Edit steps per language
- Settings — Available admin settings