Which languages Novus Convert is published in today, the shared plan for the rest of the Novus network, and how to work in another language in the meantime.
Last updated: August 7, 2026
English, and only English. There is no translated version of this site at any URL right now, and no language switcher, because there would be nothing for it to switch to. Saying so plainly is the point of this page: a switcher that offers five languages and serves one is worse than no switcher, and it is a mistake this network has made before.
All ten Novus sites share one locale contract, and it currently names 5 languages: English, Español, Deutsch, Português, 日本語. English is served from unprefixed addresses, exactly where every page already lives, and the others would appear as a path segment — Español at /es/, Deutsch at /de/, Português at /pt/, 日本語 at /ja/. Nothing on this site is published at those addresses yet; they describe the shape a translation would take, not pages you can visit.
The obvious implementation — a switcher that stores a cookie and reloads — has been tried on a sibling site and it failed twice over. Only the component holding the cookie could respond to it, so a visitor who chose another language still got an English page; and because the address never changed, a search engine only ever saw one version of each page, so there was nothing to find in any other language. Whatever ships here will put the locale in the URL, or it will not be worth shipping.
The conversion itself does not care what language you read: the engines run on your device on the bytes of your file, and the output is identical whichever language your browser is set to. A browser's built-in page translation works on every page here, because the text is ordinary server-rendered HTML rather than script-generated content it cannot see. Format names, extensions, and error codes stay in their original form on purpose — those are identifiers, and translating them would make them harder to search for, not easier.
Separate from the site's own language, and worth not confusing with it: 10 translation and message-catalogue formats are supported as conversions, normalised locally through source and target entries like any other route. Plural rules and context are preserved where the target format has somewhere to put them, and reported as a warning where it does not.
A translated page would be listed in sitemap.xml, announced on the changelog, and carry hreflang alternates pointing at its siblings. Until all three of those are true for a language, treat this page as current: it is generated from the shared contract, so the list above updates itself, but the sentence about what is actually published is written by hand and reviewed when it changes.
