Skip to content
Novus Examples

Languages

Novus Examples is published in English. The wider Novus Stream Solutions estate works to a shared list of 5 languages, and this page shows both: what this site renders today, and what the shared list contains. It is generated from that list rather than typed out, so it cannot fall behind it.

Where each language lives

A language belongs in the URL, never in a cookie. A cookie that changes the page while the address stays the same means a search engine only ever sees one version, so there is nothing to find in any other language — and a shared link opens in whatever language the recipient last chose rather than the one it was written in. English is deliberately unprefixed: / and /en serving the same page would duplicate every URL on the site.

The 5 languages in the shared Novus locale contract, and whether Novus Examples renders each one today.
LanguageTagAddressStatus here
Englishen/Served now, from every URL with no language prefix.
Españoles/esNot rendered here. The address above is reserved by the shared contract, not published.
Deutschde/deNot rendered here. The address above is reserved by the shared contract, not published.
Portuguêspt-BR/ptNot rendered here. The address above is reserved by the shared contract, not published.
日本語ja/jaNot rendered here. The address above is reserved by the shared contract, not published.

What is not translated yet

Being plain about this is the point of the page. 4 of the 5 languages on the shared list — Español, Deutsch, Português, 日本語 — have no pages on this host. There is no language switcher in the navigation, and no partly translated page anywhere, because a switcher that changes nothing is worse than no switcher: it tells you the site speaks your language and then does not.

Nothing here is machine-translated on the fly either. If you reach a page in a language you did not ask for, that is your browser’s own translation feature rather than this site, and nobody at Novus Stream Solutions has checked what it says.

The language of the site is not the language of the files

These are separate questions and this page only answers the first. The library itself is deliberately multilingual: the Localization category ships gettext catalogs, XLIFF, Android and .NET resources, Apple strings, Flutter ARB and i18next JSON, including right-to-left Arabic and CJK fixtures, precisely so you can test translation tooling against files with known content. Fixtures elsewhere in the catalogue carry non-Latin scripts, mixed encodings and bidirectional text on purpose.

What is English is the wrapper around them: the file titles, spec sheets, category pages, glossary and guides. So the tools themselves stay usable without reading English — a download is a download, and every studio is visual — while the written material is where the gap is real.

Ask for a language

If you would use Novus Examples in one of the languages above, or in one that is not on the list, say so at examples@novusstreamsolutions.com. Knowing which languages people actually want is what decides the order they are done in, and there is no date on this page because there is not one to promise.

Related: Accessibility · AI and crawler access · Localization fixtures · Contact