Contributor Guide
  • Contributor Guide
  • Localization
    • Translations
      • Spanish Style Guide
        • Glosario de términos
        • Prácticas recomendadas
        • Errores comunes de traducción
  • Development
    • Proposing Code Changes
    • Reviewing Code
    • Developer Tools
  • Feedback
    • Reporting Issues
      • Inspecting Crashes
      • Retrieving Logs
    • Creating Feature Requests
    • Starting Discussions
Powered by GitBook
On this page
  • Using Weblate
  • Style Guides
  • Specific Language Style Guides
  • Using a Desktop Translation App
  • Excluded Projects

Was this helpful?

Edit on GitHub
Export as PDF
  1. Localization

Translations

PreviousContributor GuideNextSpanish Style Guide

Last updated 10 months ago

Was this helpful?

Localizing our website and apps is an important part of making elementary OS available to as many people as possible. Instead of relying solely on an internal translation team, we use crowdsourcing so that anyone can submit translations with little to no technical knowledge. In order to keep our voice consistent across the entire platform, and to help new translators get started, we’ve put together this translation guide.

Using Weblate

Our apps and website are translated through Weblate: A libre web-based translation management system. In order to submit translations, you should:

  1. Have a

  2. Set your

  3. Browse our

Once you’ve selected a project, you can provide suggestions for strings that have not yet been translated, or suggest changes to strings that have already been translated. These suggestions will be evaluated by a translation team member and they will choose the most appropriate one. For more information about Weblate, you can refer to its .

By default, you will only be able to suggest translations. If you would like permission to save translations directly, and message an admin your Weblate username and the language you want to translate.

Style Guides

When translating you may encounter a situation where you have to decide between several ways of saying the same thing. In these situations we refer to the Ubuntu , and for language specific issues, we follow Ubuntu's . Following these guidelines ensures uniform translations, while also allowing anyone to contribute.

Specific Language Style Guides

Some language teams have created guides specific to their language to support their own translation efforts. You can check a list of the current available guides here:

Each style guide will use their own language to explain their details. Expect these pages to not be available in English.

Using a Desktop Translation App

If you don't want to translate using Weblate, or want to make a lot a changes at once, you can also translate offline. To do so:

  1. Go to a project you want to translate

  2. Choose your language

  3. Click on "Files" and then select "Download translation as gettext PO"

  4. Start translating

  5. Once you've finished, use the "Upload translation" option in the "Files" menu on the same page you downloaded the po files from

Excluded Projects

Some projects have been excluded from translations for technical or logistic reasons.

  • Developer and contributor facing documentation is excluded since developers and contributors will need to be able to read and write in English to do their work.

  • The elementary store is excluded since product information is only stored in English on the Printful platform, so it cannot be translated.

Choose your favorite text-, code- or PO-editor (e.g. )

Weblate account
language preferences
translatable projects
documentation
join us on Matrix
general translator guide
team translation guidelines
Spanish Style Guide
Poedit