Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Android BSD-3-Clause 43% 194 4,313 26,682 0 20 0 0
index BSD-3-Clause 70% 14 170 1,024 0 11 0 0
iOS BSD-3-Clause 43% 63 1,646 9,783 0 1 0 0

Overview

Project website docs.beeware.org
Instructions for translators

Navigate to a component that is showing an incomplete translation; click on Translate, and update strings as required. Any string marked as "Needs editing" needs to be reviewed. Anything marked with green sidebar has been translated previously - but any string can be modified if you think a translation can be improved.

Pay close attention to markup. We use Restructured Text and Sphinx markup; at present, Weblate won't identify or correct markup errors.

Try to keep the tone consistent. The BeeWare tutorial is deliberately written in a casual, friendly tone; try to preserve that tone in translations.

We also avoid phrasing that the could leave the reader feeling "stupid". We avoid saying that things are "simple", or that you "just" need to do X; if a user has a problem doing a "simple" thing, or can't "just" do the thing you ask, they might conclude that the problem is with them. Avoid comparable phrasing in translations.

Once you've modified a translation, click on "Save and continue" to move to the next string. There's nothing else you need to do to make translations go live. Weblate will wait a few hours to make sure changes are combined together, and then commit changes to the upstream repository. When the commit happens, you’ll see a new commit in the Github repository that you're translating; a few minutes after that, a build should start on ReadTheDocs. Each language project has its own ReadTheDocs project, formed by adding the language suffix to the end of the base BeeWare ReadTheDocs URL.

For example, the BeeWare tutorial will show additional commits in the Github repository, and each language has it's own ReadTheDocs page (e.g., French, Chinese etc)

As soon as the ReadTheDocs build completes, the changes will be made live. If the ReadTheDocs build fails (usually due to a markup error) no changes will be published until the error is corrected. The build log will show the line in the source document that is causing a problem (e.g., "tutorial-1:16" is line 16 of the Tutorial 1 translation). The translations are sorted by line number in the Weblate interface; the right hand side bar shows the source string location for each translated string.

Project maintainers User avatar freakboy3742 User avatar glasnt
9 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 504 10,144 61,920
Source 63 1,268 7,740
Approved 0% 0 0% 0 0% 0
Waiting for review 33% 170 27% 2,747 26% 16,691
Translated 46% 233 39% 4,015 39% 24,431
Needs editing 53% 271 60% 6,129 60% 37,489
Read-only 12% 63 12% 1,268 12% 7,740
Failing checks 6% 32 1% 82 1% 464
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0

Quick numbers

0
Hosted words
0
Hosted strings
0%
Translated
and previous 30 days

Trends of last 30 days

Hosted words
Hosted strings
Translated
Contributors
User avatar None

Changes committed

Changes committed 9 days ago
User avatar gmkeebiy

Marked for edit

9 days ago
User avatar gmkeebiy

Marked for edit

9 days ago
User avatar gmkeebiy

Contributor joined

Contributor joined 9 days ago
User avatar None

Alert triggered

Broken project website URL 2 months ago
User avatar None

Alert triggered

Broken project website URL 2 months ago
User avatar None

Changes committed

Changes committed 2 months ago
User avatar gallegonovato

Translation completed

Translation completed 2 months ago
User avatar gallegonovato

Translation changed

2 months ago
User avatar gallegonovato

Contributor joined

Contributor joined 2 months ago
Browse all project changes