What this site is published in, and what it is not

Where each language lives

A language belongs in the address, never in a cookie. A cookie that changes the page while the URL 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.

• 🇬🇧Englishen

  / -- served now, from every address without a language prefix.

• 🇪🇸Españoles

  /es is reserved by the shared list and is not published here. Nothing is rendered under it yet.

• 🇩🇪Deutschde

  /de is reserved by the shared list and is not published here. Nothing is rendered under it yet.

• 🇧🇷Portuguêspt-BR

  /pt is reserved by the shared list and is not published here. Nothing is rendered under it yet.

• 🇯🇵日本語ja

  /ja is reserved by the shared list and is not published here. Nothing is rendered under it yet.

What is not translated yet

Being plain about this is the point of the page. 4 of the 5 languages on the shared list, namely Español, Deutsch, Português and 日本語, 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. If you are reading this in a language it was not written in, that is your browser’s own translation feature, and nobody at Novus has checked what it says. That matters more than usual on the pages describing what a tool does and does not do.
• The tools themselves depend far less on reading the interface than the writing around them does. Merging, splitting, rotating, compressing and exporting are visual operations on a document you can already see. The gap is in the guides, tutorials, answers and articles, which is exactly where a translation would take the most work to be worth publishing.

The language of your document

This is a different question from the one above, and it is probably the one you came for. The language of this interface and the language inside your PDF have nothing to do with each other. Every tool here except one treats a document as pages and bytes: a merge, a split, a rotation, a compression, a password or a signature does not read the words, so the file’s language and script are irrelevant and nothing is re-encoded.

The exception is the OCR tool, which has to recognise letters. It exposes trained data for 3 languages, English, French and Spanish, and those files are served from this origin rather than fetched from a CDN. Those are the only choices: a scan in another language can still be run through it, but you would be asking data trained on one language to read another, and the invisible text layer it writes would be worth less than no text layer at all. The tool page states that limit rather than leaving you to find it afterwards.

Ask for a language

If you would use Novus PDF Studio in one of the languages above, or in one that is not on the list at all, say so at pdf@novusstreamsolutions.com, or through the contact page. Knowing which languages people actually want is what would decide the order they are done in. There is no date on this page because there is not one to give.

Related: Accessibility · AI access policy · PDF tools