mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-05-31 07:16:47 +00:00
44 lines
2.8 KiB
Markdown
44 lines
2.8 KiB
Markdown
---
|
|
layout: page
|
|
title: "Frontend Translation"
|
|
description: "How to translate the frontend for Home Assistant."
|
|
date: 2017-10-27 13:00
|
|
sidebar: true
|
|
comments: false
|
|
sharing: true
|
|
footer: true
|
|
ha_release: 0.57
|
|
---
|
|
|
|
## {% linkable_title How to start %}
|
|
[Join the translation team](https://lokalise.co/signup/3420425759f6d6d241f598.13594006/all/) 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 <img src='/images/frontend/lokalise-multilanguage-view-button.png' alt="Multilanguage view" style="width: 17px; border: none;"/> button. For more information about the translation workflow, please see the [Lokalise translation workflow documents](https://docs.lokalise.co/category/iOzEuQPS53-for-team-leads-and-translators).
|
|
|
|
<p class='note'>
|
|
The translation of the Home Assistant frontend is still a work in progress. More phrases will be available for translation soon.
|
|
</p>
|
|
|
|
## {% linkable_title Rules %}
|
|
1. Only native speakers should submit translations.
|
|
2. Stick to [Material Design guidelines](https://material.io/guidelines/style/writing.html).
|
|
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.
|
|
|
|
## {% linkable_title Adding a new language %}
|
|
If your language is not listed you can request it at [GitHub](https://github.com/home-assistant/home-assistant-polymer/issues/new). Please provide both the English name and the native name for your language. For example:
|
|
```
|
|
English Name: German
|
|
Native Name: Deutsch
|
|
```
|
|
|
|
<p class='note'>
|
|
Region specific translations (`en-US`, `fr-CA`) will only be included if translations for that region need to differ from the base language translation.
|
|
</p>
|
|
|
|
### {% linkable_title Maintainer steps to add a new language %}
|
|
1. Language tags have to follow [BCP 47](https://tools.ietf.org/html/bcp47). A list of most language tags can be found here: [IANA sutbtag registry](http://www.iana.org/assignments/language-subtag-registry/language-subtag-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).
|