- Features
- Multilingual Content
Translating the Buttons Is the Easy Half
Every title can carry its own title, synopsis and metadata in each language you run, separately from the language your interface is drawn in. Right to left scripts are handled as a property of the language rather than as a special case.
Two Languages, Not One
Most platforms treat language as a single setting, and it is actually two. There is the language your service is drawn in, the menus and buttons and error messages, and there is the language your catalogue is described in, the titles and the synopses. Those are not the same choice and viewers do not want them tied together. Somebody in Berlin may want the interface in German and the film titles left as they were released. Somebody else wants both in German. A platform that offers one switch forces a compromise on one of them. Vodlix keeps the two apart, with a separate toggle per language for the site and for the content, so you can enable a language for the interface without pretending you have translated a catalogue you have not.
Each language has its own switch for the interface and another for content, so you can add a language to the site now and translate the catalogue into it later without either state looking broken.
Hebrew, Arabic and Urdu are marked as right to left on the language itself, so the layout flips because of what the language is rather than because somebody wrote a special case for it.
A first visit can pick a language from the visitor location or their browser, provided you have that language installed and active. After that it is their choice, not a guess repeated forever.
The Translation Lives on the Title
Each piece of content carries its own translations, one panel per language, held next to the media and the artwork rather than in a separate system that has to be kept in step. That placement is the whole point. A synopsis translated into French belongs to the film, so it travels with it into every row, every search result and every app without anybody wiring it up. It also means the person editing a title can see which languages are filled in and which are not, at the moment they are working on it, which is the only time anybody reliably notices. Adding a language later does not invalidate anything already written, and a title with no translation for a given language falls back rather than appearing empty. The interface side of the same job is described under multilingual.
One Language Is Always Load Bearing
There is a default content language that stays enabled whatever else you do, and it exists because metadata cannot be allowed to disappear. It is the primary locale everything falls back to, so a title that has been translated into three of your seven languages still has a name in the other four rather than a gap where a name should be. Treating one language as structural and the rest as additions is what keeps a partially translated catalogue usable instead of embarrassing, which matters because every catalogue is partially translated. Nobody finishes. The default is also what your SEO metadata falls back to, so a search engine indexing a page in a language you have not fully covered still finds something to read.
Language Is a Market Decision
Adding a language is rarely about translation for its own sake. It is about a market, which usually arrives with a currency, a set of payment methods people actually use, and rights that apply to some countries and not others. Those are separate settings and they tend to move together, so it is worth planning them together. The territories a title may be watched in are covered under conditional access, the ways people can pay under payment gateways, and what any of it returned under reports and analytics. The language list itself is open ended, so a market you had not planned for is an addition rather than a rebuild.
Frequently Asked Questions
Have questions about taking advantage of this limited-time offer? Check out the FAQ for answers.