Translate Novius OS

Novius OS is ready to be translated into any language (It has already been translated into French, Japanese, Russian, Spanish and Interlingue). Here is the process to translate Novius OS into your language.

Remember we are here to help. Your contribution is very appreciated, thank you.

Quick start guide

The best way to get started with Novius OS translation is to begin with the front-office texts (~220 words only). They shouldn’t take you more than an hour to translate. Here are the steps to follow:

  1. Go to

  2. In the projects’ list (on the right-hand side), click Novius OS latest version (Novius OS versions are released in alphabetical order). If your language is not listed on the next page, let us know, we’ll add it for you.

  3. There are only four files to translate. No account required to suggest translations.

    • Blog application: noviusos_blognews > front.po
    • Forms application: noviusos_forms > front.po
    • Comments application: noviusos_comments > front.po
    • Core: framework > front.po

That’s it, you’re done! Many thanks for your contribution. Now that you’re started, what about translating more? That’d be fantastic. Keep reading, we tell you all you need to know about Novius OS translation.

Copy style guide

We take copywriting and translation very seriously. We have therefore established guidelines common to all applications and languages in order to provide every Novius OS user with consistent and enjoyable copy.

The copy style guide is to be read by every translator. If it’s not available in your language then it is the first document to translate.


We’re happy to have the style guide translated by a professionnal translator. This key document may indeed prove hard to localise. Contact us about this translation.

How to translate

Novius OS translation server is available at It is powered by Pootle. Here is a quick guide to Pootle. (You may also want to have a look at Evernote’s handy tour of Pootle.)

Translate offline

If you prefer to translate offline (or just don’t like Pootle!), you can use OmegaT or any other CAT software which handles PO files.

Go to the version and language you want to translate (see below) and click the ‘Download’ link. Once you’re done translating, contact us and we’ll grant you the rights to upload language files.

Available languages

Available languages

If on home page, your language is not listed under Languages, just contact us. We’ll add it for you.

Translation files

Once your language is available on, click it. Then click the version of Novius OS you want to translate. If you don’t know which one to choose, go for the latest version (Novius OS versions are released in alphabetical order).

You now see a list of directories. The directories starting with noviusos_ are applications. framework contains the strings from the core.

Translation directories

To start translating, don’t click Continue translation but a number in the Need translation column. This allows you to choose a directory. Please follow these priorities:

  • Top priority, the core: framework.
  • Then the native applications: Webpages (noviusos_pages), Media Centre (noviusos_media), Users (noviusos_user) and Applications manager (noviusos_appmanager).
  • And finally the non-native applications.

Suggesting and submitting translations

Everybody can suggest translations. A suggestion will be reviewed by an approved translator before being submitted. Only submitted translations are applied to Novius OS. Unreviewed or rejected suggestions stay in Pootle.


You don’t even need to create an account to suggest translations. Nevertheless creating an account only takes you a minute and allows you to select your languages and avoid the CAPTCHA protection.

Being an approved translators is a great way to make a difference to the Novius OS project. Everyone can apply: Just drop us a few lines about yourself and include your Pootle username. We’ll review your application before granting you extended permissions.

When translating

Placeholders and tags

  • Some strings include variables, e.g. ‘Welcome back, {{user}}’. Obviously, Novius OS end users don’t see these variables which are replaced by the actual value, e.g. ‘Welcome back, Joe’. Variables are to be kept, untranslated, e.g. ‘Re-bonjour {{user}}’.
  • HTML tags are also to be kept and not to be translated. In most cases, you’ll find a start tag and an end tag, e.g. ‘This page has <strong>one sub-page</strong>’. Text between tags must be translated, e.g. ‘Cette page a <strong>une sous-page</strong>’.
  • For non-breaking spaces, please use the HTML entity, i.e. &nbsp;.

Dispelling doubts

Don’t translate in the dark! When you don’t understand a string, need to know the context or have any doubt, please contact us. Our job is to make translation easy. We’re happy to add notes to translator in the translation files for others to benefit from your feedback. We can also provide you with screenshots or indications to find a string in the UI of Novius OS.

When your question or comment regards a specific string, please give us the link to the string. You’ll find it the bottom right corner:

String URL

Translating the documentation

This documentation is powered by Read The Docs which uses Rich Structured Text (RST) files. This format is human-readable and therefore easier to translate.

If on this page, your language is not listed under Translations, contact us. We’ll set up the GitHub repo for you.

Once the repo is ready, clone it. You may also want to clone the English repo so you can copy files from the original version to the translation.

That’s it, you’re all set to start translating. Thank you very much for your contribution!

Read the Docs v: elche
On Read the Docs
Project Home

Free document hosting provided by Read the Docs.