Wording and languages
Your users see the editor in their language, and in your app's own words. Its labels come in English, Spanish, German and Arabic; Arabic mirrors the editor's controls for right-to-left reading.
Choose the language Stable
By default, pass the device's or page's language; the SDK picks the closest one it has
(de-AT → German) and falls back to English. It returns the language it chose.
| Platform | Call |
|---|---|
| iOS | setLocale(tag: Locale.current.identifier) |
| Android | setLocale(Locale.getDefault().toLanguageTag()) |
| React Native | setLocale() (follows the device) |
| Web | setLocale() (follows the browser) |
availableLocales() lists the languages; localeIsRtl() says whether the current one is
right to left.
Use your own wording Stable
Rename any label to match your app, e.g. call effects "Filters":
{ "effects": "Filters", "edit-text": "Change text" }
Pass this to setStrings: a JSON string on iOS and Android, an object in React Native and on
the web.
Each call replaces the previous wording, and an empty object clears it. Use your own
translations here too, for the user's language.
Keys are message ids: the English label in lowercase with dashes (Edit text →
edit-text). A word with several meanings has a prefix, e.g. nav-back for the Back button.
Preview Message ids follow the English labels, so a renamed label in a future release can change its id. Check your wording when you upgrade.
Right to left
In a right-to-left language the transport row, bottom bar and panels are mirrored, and direction icons such as Back point the other way. The timeline keeps time running left to right, as in other video editors.
Fonts for other scripts
On iOS and Android, the system fonts cover every script. On the web there are no system fonts: add one that covers your language's script, for example Noto Sans Arabic for Arabic.