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
Translation license BSD 3-Clause "New" or "Revised" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://github.com/beeware/beeware
Repository branch main
Last remote commit Merge pull request #444 from beeware/autoupdates/config-files 0d814ca
User avatar freakboy3742 authored yesterday
Last commit in Weblate Merge pull request #444 from beeware/autoupdates/config-files 0d814ca
User avatar freakboy3742 authored yesterday
Weblate repository https://hosted.weblate.org/git/beeware/tutorial/index/
File mask docs/locales/*/LC_MESSAGES/tutorial/topics/custom-icons.po
Translation file Download docs/locales/fr/LC_MESSAGES/tutorial/topics/custom-icons.po
Last change June 19, 2024, 2:15 a.m.
Last change made by None
Language French
Language code fr
Text direction Left to right
Number of speakers 295,510,923
Number of plurals 2
Plural type One/other
Plurals Singular 0, 1
Plural 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
Plural formula n > 1
4 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 23 725 4,407
Translated 0% 0 0% 0 0% 0
Needs editing 8% 2 4% 33 4% 181
Read-only 0% 0 0% 0 0% 0
Failing checks 26% 6 4% 35 4% 194
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 91% 21 95% 692 95% 4,226
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 24 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

725
Hosted words
23
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
—
—
Contributors
—
User avatar None

Resource updated
The “docs/locales/fr/LC_MESSAGES/tutorial/topics/custom-icons.po” file was changed. 5 months ago
User avatar None

Resource updated
File “docs/locales/fr/LC_MESSAGES/tutorial/topics/custom-icons.po” was added. 5 months ago
User avatar None

String added in the repository
You'll need to re-create the app like this whenever you make a change to your ``pyproject.toml`` that doesn't relate to source code or dependencies. Any change to descriptions, version numbers, colors, or permissions will require a re-create step. Because of this, while you are developing your project, you shouldn't make any manual changes to the contents of the ``build`` folder, and you shouldn't add the ``build`` folder to your version control system. The ``build`` folder should be considered entirely ephemeral - an output of the build system that can be recreated as needed to reflect the current configuration of your project.
 
5 months ago
User avatar None

String added in the repository
You can then re-build and re-run the app using ``briefcase run``. You won't notice any changes to the desktop app; but the Android or iOS apps should now have a light blue splash screen background.
 
5 months ago
User avatar None

String added in the repository
Unfortunately, Briefcase isn't able to apply this change to an already generated project, as it requires making modifications to one of the files that was generated during the original call to ``briefcase create``. To apply this change, we have to re-create the app by re-running ``briefcase create``. When we do this, we'll be prompted to confirm that we want to overwrite the existing project:
 
5 months ago
User avatar None

String added in the repository
When you run the app on iOS or Android, in addition to the icon change, you should also notice that the splash screen incorporates the new icon. However, the light blue background of the icon looks a little out of place against the white background of the splash screen. We can fix this by customizing the background color of the splash screen. Add the following definition to your ``pyproject.toml``, just after the ``icon`` definition::
 
5 months ago
User avatar None

String added in the repository
If you're using a recent version of Android, you may notice that the app icon has been changed to a green snake, but the background of the icon is *white*, rather than light blue. We'll fix this in the next step.
 
5 months ago
User avatar None

String added in the repository
Now that we have icons, we can update the application again. However, ``briefcase update`` will only copy the updated resources into the build directory; we also want to rebuild the app to make sure the new icon is included, then start the app. We can shortcut this process by passing ``--update-resources`` to our call to ``run`` - this will update the app, update the app's resources, and then start the app:
 
5 months ago
User avatar None

String added in the repository
The only exception will be the icons with ``-adaptive-`` in their name; these will have a transparent background. This represents all the different icon sizes and shapes you need to support an app on every platform that Briefcase supports.
 
5 months ago
User avatar None

String added in the repository
Icon of green snake with a light blue background
 
5 months ago
Browse all translation changes