Strings Words Characters | |||
---|---|---|---|
0 0 0 |
|
All strings | 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 |
|
|
Source code repository |
local:
|
|
Repository branch | main | |
Weblate repository |
https://hosted.weblate.org/git/beeware/glossary/
|
|
File mask | *.tbx |
|
Translation file |
Download
es.tbx
|
|
Last change | Jan. 10, 2024, 1:38 a.m. | |
Last change made by | None | |
Language | Spanish | |
Language code | es | |
Text direction | Left to right | |
Number of speakers | 493,528,078 | |
Number of plurals | 3 | |
Plural type | One/many/other | |
Plurals | One | 1 | Many | 1000000, 2000000 |
Other | 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, … | |
Plural formula | (n == 1) ? 0 : ((n != 0 && n % 1000000 == 0) ? 1 : 2) |
String statistics
Strings percent | Hosted strings | Words percent | Hosted words | Characters percent | Hosted characters | |
---|---|---|---|---|---|---|
Total | 0 | 0 | 0 | |||
Translated | 100% | 0 | 100% | 0 | 100% | 0 |
Needs editing | 0% | 0 | 0% | 0 | 0% | 0 |
Read-only | 0% | 0 | 0% | 0 | 0% | 0 |
Failing checks | 0% | 0 | 0% | 0 | 0% | 0 |
Strings with suggestions | 0% | 0 | 0% | 0 | 0% | 0 |
Untranslated strings | 0% | 0 | 0% | 0 | 0% | 0 |
Quick numbers
Trends of last 30 days
None
Resource updated |
|
None
Changes committed |
Changes committed
9 months ago
|
0 | File in original format as translated in the repository | TermBase eXchange file | ||||||
---|---|---|---|---|---|---|---|---|
0 | All strings, converted files enriched with comments; suitable for offline translation | CSV | gettext PO | TBX | TMX | XLIFF 1.1 with gettext extensions | XLIFF 1.1 | XLSX |
es.tbx
” was added. 9 months ago