Multilingual Belgian sites: one voice per language, one integration (and where it stops)

A Belgian site is rarely monolingual. A municipality, a news outlet, a professional federation publishes in French and Dutch, sometimes in German, and the audio has to follow that reality: not one voice for everything, but the right voice for each language. The good news is that the setting exists and fits inside a single integration. The honest news is that the catalogue does not yet cover all three national languages. Here are both, without rounding.

One default voice, per language

The principle is simple and already in place: each language has its own default voice, kept independently of the others. You pick the French voice for your French articles, and that voice never becomes, by accident, the voice of your articles in another language. The settings screen offers the enabled languages, and for each one you set its default once. An article published in a given language then goes out with the voice meant for that language, with no per-article intervention. This is exactly what a multilingual site expects: set once, apply everywhere, and change the voice for one language without touching the others. The same choice, male or female voice, timbre, pace, is made language by language, and our piece on choosing a voice by content applies to each.

What the catalogue covers today

The voice catalogue enables five languages: French, English, Spanish, German and Italian. For Belgium, that means something precise. A site publishing in French and German, both national languages of the country, is fully covered: each language gets its default voice, and the integration stays single. The German-speaking Community in the east of the country, often forgotten by tools, is served on the same footing as the French-speaking part. That is a rare case a tool handles cleanly, and it is worth saying.

What it does not cover yet: Dutch

This has to be said just as clearly: Dutch is not in the catalogue today. A bilingual French and Dutch Belgian site can therefore narrate its French pages, but not its Dutch pages, for want of an available Dutch voice. This is not a setting to find or a hidden option: the language is not enabled, full stop. We do not ship a half-solution that would read Dutch with a voice from another language, because the result would be poor and would betray the line we hold everywhere: better not to do it than to do it badly. If Dutch is essential to your project, the tool does not meet that need yet, and that is a decision criterion, not a detail to discover after installation.

One integration, whatever the number of languages

On the setup side, the number of languages does not multiply the work. The audio player is inserted once into the site, and it is the per-language setting that steers the voice, not one installation per language version. For a WordPress site, this goes through the plugin described on the WordPress page: it installs once and respects the declared language of each piece of content. So you do not manage three players for three languages, you manage one player and a table of default voices. That is what makes the promise "two languages, two voices, one integration" true rather than theoretical, with the real caveat of Dutch.

In short, to decide fast

A Belgian site in French and German is fully supported today: one voice per language, set once, one integration. A site in French and Dutch is supported on the French side only, as long as Dutch is not enabled in the catalogue. It is a clean limit, easy to check, and we would rather state it before you test. This way of saying what the tool does and what it does not do yet is the same one defended in what French quality means for a voice tool: honest language coverage beats a ticked box that disappoints on playback.

Read next

• Libraries and media centres: audio in the service of reading accessibility
• Integrating schema.org markup for a narrated article: using AudioObject well
• Audio, ADHD and attention: what the format actually helps with