BeeWare/Tutorial/Tutorial 3 — English @ Hosted Weblate

Source strings

58	Strings	100%	Browse Translate
1,735	Words	100%
10,953	Characters	100%

This translation is being used as source strings within this component.

Strings status

Strings Words Characters
58 1,735 10,953	All strings	Browse Translate Zen
58 1,735 10,953	Read-only strings	Browse Translate Zen
6 89 613	Strings with any failing checks	Browse Translate Zen
2 63 386	Failing check: Ellipsis	Browse Translate Zen
4 26 227	Failing check: Multiple failing checks	Browse Translate Zen

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	freakboy3742 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 #439 from beeware/dependabot/github_actions/actions/checkout-4.2.2 `b6dc50c` freakboy3742 authored 4 days ago
Last commit in Weblate	Merge pull request #439 from beeware/dependabot/github_actions/actions/checkout-4.2.2 `b6dc50c` freakboy3742 authored 4 days ago
Weblate repository	`https://hosted.weblate.org/git/beeware/tutorial/index/`
File mask	`docs/locales/*/LC_MESSAGES/tutorial/tutorial-3.po`
Translation file	Not available
Last change	May 21, 2024, 10:06 p.m.
Last change made by	None
Language	English
Language code	en
Text direction	Left to right
Number of speakers	1,636,485,517
Number of plurals	2
Plural type	One/other
Plurals	Singular	1
Plurals	Plural	0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula	`n != 1`

3 weeks ago

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		58		1,735		10,953
Translated	100%	58	100%	1,735	100%	10,953
Needs editing	0%	0	0%	0	0%	0
Read-only	100%	58	100%	1,735	100%	10,953
Failing checks	10%	6	5%	89	5%	613
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	0%	0	0%	0	0%	0

Last 12 months Previous

Activity in last 12 months


Nov	Dec	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct

Quick numbers

1,735

Hosted words

Hosted strings

100%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

+100%

—

Hosted strings

+100%

—

Translated

+100%

—

Contributors

—

None Source string added BeeWare Tutorial Tutorial 3 English	English 0 characters edited Read only You will need to recreate your virtual environment using the system ``python3``. Using the system Python is a requirement for packaging your application. 5 months ago
None Source string added BeeWare Tutorial Tutorial 3 English	English 0 characters edited Read only The version of Python being used to run Briefcase (3.12) is not the system python3 (3.10). 5 months ago
None Source string added BeeWare Tutorial Tutorial 3 English	English 0 characters edited Read only If you receive an error that reads something like: 5 months ago
None Source string added BeeWare Tutorial Tutorial 3 English	English 0 characters edited Read only Errors about Python versions 5 months ago
None Source string added BeeWare Tutorial Tutorial 3 English	English 0 characters edited Read only When you're ready to publish a real application, check out the Briefcase How-To guide on `Setting up a macOS code signing identity <https://briefcase.readthedocs.io/en/latest/how-to/code-signing/macOS.html>`__. 5 months ago
None Source string added BeeWare Tutorial Tutorial 3 English	English 0 characters edited Read only This will start to run your native application, using the app bundle created by the ``build`` command. 5 months ago
None Source string added BeeWare Tutorial Tutorial 3 English	English 0 characters edited Read only As noted above, when Briefcase packages an app as a native Linux system package (the default package format for Linux), a support package is not included with the app. Instead, the app will use the Python that is provided by the distribution of Linux being targeted. 5 months ago
None Source string added BeeWare Tutorial Tutorial 3 English	English 0 characters edited Read only It downloaded and installed a support package. The packaging approach taken by Briefcase is best described as "the simplest thing that could possibly work" - it ships a complete, isolated Python interpreter as part of every application it builds (except for Linux native system package builds). This is slightly space inefficient - if you have 5 applications packaged with Briefcase, you'll have 5 copies of the Python interpreter. However, this approach guarantees that every application is completely independent, using a specific version of Python that is known to work with the application. 5 months ago
None Source string added BeeWare Tutorial Tutorial 3 English	English 0 characters edited Read only When you're ready to publish a real application, check out the Briefcase How-To guide on `Setting up a Windows code signing identity <https://briefcase.readthedocs.io/en/latest/how-to/code-signing/windows.html>`__ 6 months ago
None Source string added BeeWare Tutorial Tutorial 3 English	English 0 characters edited Read only In this example, we're not signing our app. As a result, when you use the installer, you'll get a system warning that the application comes from an unknown developer. We've done this to keep the tutorial simple. Setting up code signing identities is a little fiddly, and they're only required if you're intending to distribute your application to others. If we were publishing a real application for others to use, we would need to specify a real signing identity; when that signed app is installed, the system will notify the user that the application is from the known identity associated with the certificate. 6 months ago

Browse all translation changes

Quick downloads

58	File in original format as translated in the repository	gettext PO file
58	All strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX

Customize download

File format*

gettext PO XLIFF 1.1 with gettext extensions XLIFF 1.1 TBX TMX gettext MO CSV XLSX

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>="1 month ago" AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>="1 month ago" AND state:<=needs-editing`	Add
Strings changed in the past two weeks	`changed:>="2 weeks ago"`	Add

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.