Frontend Translation


How to start

Join the translation team and choose your language. Even if your language is completely translated, extra proofreading is a big help! Please feel free to review the existing translations, and vote for alternatives that might be more appropriate.

First time users may find it helpful to switch between multilanguage and single language view using the Multilanguage view button. For more information about the translation workflow, please see the Lokalise translation workflow documents.

The translation of the Home Assistant frontend is still a work in progress. More phrases will be available for translation soon.

Rules

  1. Only native speakers should submit translations.
  2. Stick to Material Design guidelines.
  3. Don’t translate or change proper nouns like Home Assistant, Hass.io or Hue.
  4. For a region specific translation, keys that will be the same as the base translation should be filled with [VOID]. These will be replaced during our translation build process.
  5. Translations under the state_badge keys will be used for the notification badge display. These translations should be short enough to fit in the badge label without overflowing. This can be tested in the Home Assistant UI either by editing the label text with your browsers development tools, or by using the States developer tool in the Home Assistant UI. In the UI, enter a new entity ID (device_tracker.test), and enter the text you want to test in state.
  6. If text will be duplicated across different translation keys, make use of the Lokalise key reference feature where possible. The base translation provides examples of this underneath the states translations. Please see the Lokalise key referencing documentation for more details.

Adding a new language

If your language is not listed you can request it at GitHub. Please provide both the English name and the native name for your language. For example:

English Name: German
Native Name: Deutsch

Region specific translations (en-US, fr-CA) will only be included if translations for that region need to differ from the base language translation.

Maintainer steps to add a new language

  1. Language tags have to follow BCP 47. A list of most language tags can be found here: IANA sutbtag registry. Examples: fr, fr-CA, zh-Hans. Only include the country code if country specific overrides are being included, and the base language is already translated.
  2. Add the language tag and native name in src/translations/translationMetadata.json. Examples: “Français”, “Français (CA)”
  3. Add the new language in Lokalize. Note: Sometimes you have to change the tag in Lokalise (Language -> Language settings -> custom ISO code).