This project is in a trial period, be cautious while contributing. Setup can still change before being approved as a libre project.

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 10 Tutorial 11 Tutorial 2 Tutorial 3 Tutorial 4 Tutorial 6 Tutorial 7 Tutorial 8 Tutorial 9
5 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 3,777 89,066 547,303
Source 487 11,583 71,401
Approved 0% 0 0% 0 0% 0
Waiting for review 27% 1,048 18% 16,748 18% 103,618
Translated 40% 1,535 31% 28,331 31% 175,019
Needs editing 54% 2,051 61% 54,929 61% 336,145
Read-only 12% 487 13% 11,583 13% 71,401
Failing checks 9% 374 3% 3,326 3% 21,289
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 5% 191 6% 5,806 6% 36,139
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 0 changes 0 changes 3,891 changes 0 changes 1,132 changes 0 changes 56 changes 0 changes 838 changes
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

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

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar None

Resource updated

  1. BeeWare
  2. Tutorial
  3. Tutorial 2
  4. Chinese (Traditional)
The “docs/locales/zh_TW/LC_MESSAGES/tutorial/tutorial-2.po” file was changed. 4 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Tutorial 2
  4. Chinese (Traditional)
The last thing we need to do is define the handler for the button. A handler can be any method, generator, or asynchronous coroutine; it accepts the widget that generated the event as an argument, and will be invoked whenever the button is pressed::
我們需要做的最後一件事是定義按鈕的處理程序。處理程序可以是任何方法、生成器或非同步協程；它接受生成事件的小部件作為參數，並且每當按下按鈕時就會調用::
4 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Tutorial 2
  4. Chinese (Traditional)
This completes our layout; the rest of the startup method is as it was previously - defining a ``MainWindow``, and assigning the main box as the window's content::
這樣就完成了我們的佈局；啟動方法的其餘部分與之前一樣 - 定義一個 MainWindow，並將主框指定為視窗的內容::
4 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Tutorial 2
  4. Chinese (Traditional)
This creates an instance of a ``toga.MainWindow``, which will have a title matching the application's name. A Main Window is a special kind of window in Toga - it's a window that is closely bound to the life cycle of the app. When the Main Window is closed, the application exits. The Main Window is also the window that has the application's menu (if you're on a platform like Windows where menu bars are part of the window).
這將建立一個``toga.MainWindow``實例，它將具有與應用程式名稱相符的標題。主視窗是 Toga 中的一種特殊視窗 - 它是與應用程式的生命週期密切相關的視窗。當主視窗關閉時，應用程式退出。主視窗也是具有應用程式選單的視窗（如果您使用的是 Windows 等平台，其中功能表列是視窗的一部分）
4 days ago
User avatar None

Resource updated

  1. BeeWare
  2. Tutorial
  3. Tutorial 2
  4. Chinese (Simplified)
The “docs/locales/zh_CN/LC_MESSAGES/tutorial/tutorial-2.po” file was changed. 4 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Tutorial 2
  4. Chinese (Simplified)
The last thing we need to do is define the handler for the button. A handler can be any method, generator, or asynchronous coroutine; it accepts the widget that generated the event as an argument, and will be invoked whenever the button is pressed::
我们需要做的最后一件事是定义按钮的处理器。处理器可以是任何方法、生成器或异步协程；它接受生成事件的小部件 (widget ) 作为参数，并且每当按下按钮时就会被调用::
4 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Tutorial 2
  4. Chinese (Simplified)
This completes our layout; the rest of the startup method is as it was previously - defining a ``MainWindow``, and assigning the main box as the window's content::
这完成了我们的布局；其余的 startup 方法与以前一样 - 定义一个 MainWindow，并将主盒子指定为窗口的内容::
4 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Tutorial 2
  4. Chinese (Simplified)
This creates an instance of a ``toga.MainWindow``, which will have a title matching the application's name. A Main Window is a special kind of window in Toga - it's a window that is closely bound to the life cycle of the app. When the Main Window is closed, the application exits. The Main Window is also the window that has the application's menu (if you're on a platform like Windows where menu bars are part of the window).
这将创建一个 toga.MainWindow 的实例，它的标题 (title) 将与应用程序的名称 (self.formal_name) 匹配。主窗口是 Toga 中的一种特殊窗口——它是与应用程序的生命周期 (life cycle) 密切绑定的窗口。当主窗口关闭时，应用程序退出。主窗口也是具有应用程序菜单的窗口（如果你在像 Windows 这样的平台上，菜单栏是窗口的一部分；如果你没有进行任何菜单栏的增删操作，你将看到默认的 file (文件) 和 help (帮助) 这两个菜单栏选项）
4 days ago
User avatar None

Resource updated

  1. BeeWare
  2. Tutorial
  3. Tutorial 2
  4. Portuguese
The “docs/locales/pt/LC_MESSAGES/tutorial/tutorial-2.po” file was changed. 4 days ago
User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Tutorial 2
  4. Portuguese
The last thing we need to do is define the handler for the button. A handler can be any method, generator, or asynchronous coroutine; it accepts the widget that generated the event as an argument, and will be invoked whenever the button is pressed::
A última etapa consiste na definição do gatilho do botão. Um gatilho pode ser qualquer método, gerador ou corrotina assíncrona; ele aceita como argumento o widget que gerou o evento e será invocado sempre que o botão for pressionado::
4 days ago
Browse all project changes