Component Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary Breezy Weather LGPL-3.0-only 20% 0 0 0 0 0 0 1
Breezy Weather Android LGPL-3.0-only 30% 0 0 0 0 0 1 4

Overview

Project website github.com/breezy-weather/breezy-weather
Instructions for translators

IMPORTANT

  • Using automatic translators without reviewing, bots, ignoring project instructions, ignoring project notes for a string or ignoring Weblate warnings (if not justified), is not allowed and if repeated, it will be considered as sabotage, whether it was intentional or not, and can get you blocked (we usually send one or more warnings first).
  • Strings ending with _voice are used by accessibility tools, you need to think what the user needs to hear, not what he needs to read (it will never be written in the app)
  • For meteorological terms, you can find translations for some languages here: https://unterm.un.org/unterm2/en
  • For scales, please search on Wikipedia official terms (Beaufort wind scale, UV index, etc) or AccuWeather (air quality)
  • You can guess the context from the ID of the translated line
  • Please give priority to translating the lines in the order they are listed in the original English file
  • Do NOT use " and ', use appropriate typographic quotes for your language (in English: “ and ”, ‘ and ’), so that we avoid using escaped characters in the source code

Specific cases

  • If you need to create a new language, please ensure that you can dedicate time to make significant progress before next release of Breezy Weather (short term, usually 1-2 times a month). Indeed, Weblate is a continuous integration tool and there is no way for us to withhold translations on Weblate, and it will be pushed to app repo, and due to the way Android projects work, it will be pushed to end-users. We don't want to push a translation to end-users where 90 % of the translation is missing, so please keep that in mind. 18% are non-translatable strings so try to strive for at least 40% coverage, prioritizing the most important strings (the ones from the beginning).
  • English (and regional variants) and French translations are maintained by repo maintainers, but they are open to proofreading/improvements. You will need to make a pull request on GitHub, as we didn’t find a way to make these languages in suggestion-only mode in Weblate (let us know if you find anything).
  • If there is a line used at multiple places in the code, but with different gender/plural in your language, please open an issue on our GitHub to let us know
Project maintainers User avatar papjul
Language German
Language code de
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 141,444,441
an hour ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,084 3,583 26,300
Approved 0% 0 0% 0 0% 0
Waiting for review 69% 757 82% 2,940 69% 18,163
Translated 100% 1,084 100% 3,583 100% 26,300
Needs editing 0% 0 0% 0 0% 0
Read-only 30% 327 17% 643 30% 8,137
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 1% 1 1% 2 1% 15
Untranslated strings 0% 0 0% 0 0% 0

Quick numbers

3,583
Hosted words
1,084
Hosted strings
98%
Translated
and previous 30 days

Trends of last 30 days

+1%
Hosted words
+100%
+1%
Hosted strings
+100%
−1%
Translated
+100%
+20%
Contributors
+100%
User avatar None

Changes committed

Changes committed an hour ago
User avatar min7-i

Suggestion removed

an hour ago
User avatar min7-i

Comment added

@Kachelkaiser I think there has been a mix-up here. According to the following sources (Met Office https://www.metoffice.gov.uk/weather/guides/coast-and-sea/beaufort-scale and DWD https://www.wettergefahren.de/warnungen/windwarnskala.html) wind strength 2 (light breeze) should be "leichte Brise" while wind strength 3 (gentle breeze) should be "schwache Brise" or "schwacher Wind".

Do you have other sources where the terms are translated differently?

2 hours ago
User avatar min7-i

Comment resolved

Comment resolved 2 hours ago
User avatar min7-i

Comment resolved

Comment resolved 2 hours ago
User avatar min7-i

Comment added

@ColorfulRhino I agree that "Karten" can be misunderstood as maps here, so I think using "Kacheln" instead is a good idea. Initially, I wanted to keep the differentiation between cards and tiles (as discussed here for instance https://ux.stackexchange.com/a/78822), but I can understand that most users probably won't know the difference.

2 hours ago
User avatar min7-i

Translation completed

Translation completed 4 hours ago
User avatar min7-i

Translation added

4 hours ago
User avatar min7-i

Translation added

4 hours ago
User avatar min7-i

Translation added

4 hours ago
Browse all changes for this language