ads

Multilingual Content: Localise the Catalogue, Not Just the Interface

Every title carries its own translated title, synopsis and metadata per language, managed separately from the interface language.

Create Your Free Account See Our Pricing
Multilingual Content: Localise the Catalogue, Not Just the Interface

Interface Language and Catalogue Language Are Separate Choices

Vodlix multilingual content treats language as two separate choices: the language of the interface and the language of the catalogue. Viewers do not want the two tied together. A viewer in Berlin may want German menus with original language titles, or German for both, and the platform should allow either. Vodlix keeps interface language and catalogue translation independent, so each can be set to what the viewer actually wants. For OTT operators, this is what real localisation looks like.


split.svg
Two languages

Interface and catalogue set separately.

rtl.svg
Right to left

Handled as a language property.

attach.svg
On the title

Translations travel with the content.

lang-translations.png

Translations Stored on the Title

In Vodlix, translations live on the title. Each film, series or episode carries its own translated title, synopsis and metadata, one panel per language, alongside the media and artwork. A French synopsis entered once travels into every content row, search result, recommendation and app where that title appears. Because translation is stored with the content, adding a language to the catalogue is a metadata task rather than a rebuild. Title level translation keeps a multilingual catalogue accurate and consistent.


Right to Left Languages Handled Properly

Vodlix handles right to left languages properly. Hebrew, Arabic and Urdu are marked as right to left on the language definition itself, so the entire layout flips because of the language rather than through a special case coded for each screen. Text alignment, navigation and reading order all follow the language setting automatically across web, mobile and TV. Operators serving Middle Eastern or South Asian markets get correct RTL rendering without custom development.


Sensible Language Defaults, Then Viewer Choice

Vodlix applies sensible language defaults and then respects the viewer's choice. On a first visit, the platform can select a catalogue language based on the viewer's location or browser settings, provided that language is installed. After that, the viewer's own selection is remembered rather than guessed again on every visit. Defaults get the first impression right; viewer choice keeps it right. This approach avoids the frustration of a service that repeatedly overrides a viewer's language preference.


Frequently Asked Questions

Have questions about taking advantage of this limited-time offer? Check out the FAQ for answers.

Can I translate titles and synopses on Vodlix, not just menus?
Yes. Vodlix multilingual content lets every title carry its own translated title, synopsis and metadata per language, so the catalogue itself is localised, not only the interface.
Are the interface language and content language linked on Vodlix?
No. Vodlix treats interface language and catalogue language as separate settings, so a viewer can have menus in one language and title descriptions in another.
How does Vodlix handle right to left languages?
Right to left support is a property of the language definition in Vodlix, so layouts, alignment and reading order flip automatically for Arabic, Hebrew and Urdu without a special case per screen.
Where do content translations live in Vodlix?
Translations are stored on the title itself, one panel per language beside the media and artwork, so a translated synopsis travels into every row, search result, recommendation and app.
How does Vodlix choose a viewer's language on first visit?
On a first visit Vodlix can select a language from the viewer's location or browser settings if that language is installed. After that, the viewer's own choice is remembered rather than guessed again.
Can I add a language that is not in the list?
Yes, languages can be added rather than being fixed to a preset list. That matters because the market that turns out to be worth pursuing is often not one you planned for, and it should not require a platform change to serve it.
Do translations apply across web, mobile and TV?
They do, because the translation belongs to the title rather than to a page. Once a synopsis exists in a language it appears wherever that title appears, in every app, without anybody wiring it up per platform.
Is this the same as subtitles?
No. This is the language of your catalogue metadata, the titles and descriptions people read while deciding what to watch. Subtitles are the language of the content itself while it plays, and they are handled separately on each title.