Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Tutorial 39% 306 8,492 51,904 78 40 0 0
Android BSD-3-Clause 11% 38 857 5,306 0 3 0 0
Glossary BeeWare BSD-3-Clause 0 0 0 0 0 0 0
camera-access BSD-3-Clause 0% 27 783 4,671 27 2 0 0
custom-icons BSD-3-Clause 0% 23 725 4,407 21 6 0 0
index BSD-3-Clause 95% 1 28 399 0 0 0 0
index BSD-3-Clause 0 0 0 0 2 0 0
index BSD-3-Clause 0% 8 96 598 8 0 0 0
iOS BSD-3-Clause 14% 12 332 1,977 0 0 0 0
testing BSD-3-Clause 12% 21 611 3,550 0 3 0 0
Tutorial 0 BSD-3-Clause 84% 7 171 1,167 3 3 0 0
Tutorial 1 BSD-3-Clause 0 0 0 0 3 0 0
Tutorial 2 BSD-3-Clause 86% 7 300 1,672 1 5 0 0
Tutorial 3 BSD-3-Clause 50% 29 994 6,340 5 4 0 0
Tutorial 4 BSD-3-Clause 16% 25 714 4,264 0 3 0 0
Tutorial 6 BSD-3-Clause 33% 12 438 2,496 0 3 0 0
Tutorial 7 BSD-3-Clause 8% 54 1,304 8,162 0 3 0 0
Tutorial 8 BSD-3-Clause 4% 42 1,139 6,895 13 0 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
Translation license BSD-3-Clause index Tutorial 0 Tutorial 1 Tutorial 2 Tutorial 3 Tutorial 4 Tutorial 6 Tutorial 7 Tutorial 8 Android index iOS camera-access custom-icons index testing BeeWare
2 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 505 11,973 73,478
Translated 39% 199 29% 3,481 29% 21,574
Needs editing 45% 228 54% 6,574 54% 40,111
Read-only 0% 0 0% 0 0% 0
Failing checks 7% 40 2% 257 2% 1,497
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 15% 78 16% 1,918 16% 11,793
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 0 changes 0 changes 653 changes 0 changes 383 changes 0 changes 16 changes 0 changes 9 changes 0 changes 175 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

11,973
Hosted words
505
Hosted strings
39%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+15%
Hosted words
+100%
+11%
Hosted strings
+100%
−9%
Translated
+48%
−100%
Contributors
+100%
User avatar None

Resource updated

  1. BeeWare
  2. Tutorial
  3. Topics
  4. camera-access
  5. Portuguese
File “docs/locales/pt/LC_MESSAGES/tutorial/topics/camera-access.po” was added. 2 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Topics
  4. camera-access
  5. Portuguese
Permissions are declared in the files that are generated during the original call to ``briefcase create``. Unfortunately, Briefcase can't update these files once they've been initially generated; so if you want to add a new permission to your app, or modify existing permissions, you'll need to re-create the app. You can do this by re-running ``briefcase create``; this will warn you that the existing app will be overwritten, and then regenerate the application with the new permissions.
 
2 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Topics
  4. camera-access
  5. Portuguese
Adding more permissions
 
2 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Topics
  4. camera-access
  5. Portuguese
When the app runs, you'll be presented with a button. Press the button, and the platform's default camera dialog will be displayed. Take a photo; the camera dialog will disappear, and the photo will be displayed on in the app, just above the button. You could then take another photo; this will replace the first photo.
 
2 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Topics
  4. camera-access
  5. Portuguese
Android
 
2 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Topics
  4. camera-access
  5. Portuguese
macOS
 
2 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Topics
  4. camera-access
  5. Portuguese
We can now generate and run the app:
 
2 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Topics
  4. camera-access
  5. Portuguese
This declares that your app needs to access the camera, and provides a short description why the camera is required. This description is needed on some platforms (most notably macOS and iOS) and will be displayed to the user as a additional information when the permission dialog is presented.
 
2 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Topics
  4. camera-access
  5. Portuguese
The permissions required by each platform are slightly different, but Briefcase has a cross-platform representation for many common hardware permissions. In the ``[tool.briefcase.app.helloworld]`` configuration section of your app's ``pyproject.toml`` file, add the following (just above the ``sources`` declaration):
 
2 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Topics
  4. camera-access
  5. Portuguese
However, this request comes in two parts. The first is in the code we've just seen; but before the app can ask for permissions, it needs to declare the permissions it is going to ask for.
 
2 days ago
Browse all changes for this language