Translation status

522 Strings
90%
Browse Translate
8,948 Words
89%
59,400 Characters
90%

Strings status

Strings Words Characters
522 8,948 59,400
All strings Browse Translate Zen
497 8,416 56,121
Translated strings Browse Translate Zen
25 532 3,279
Unfinished strings Browse Translate Zen
25 532 3,279
Untranslated strings Browse Translate Zen
22 373 2,143
Strings with any failing checks Browse Translate Zen
22 373 2,143
Translated strings with any failing checks Browse Translate Zen
22 373 2,143
Failing check: reStructuredText syntax error Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
doc
doc-code-and-documentation 97% 6 142 1,154 6 10
doc-contributing 100% 3
doc-non-code-contribution
doc-operators 94% 2 62 493 2
doc-organizations 98% 1 12 75 1
doc-users
Browse all components

Summary

Project website docs.openstack.org/contributor-guide
Translation process
  • Translations can be made directly.
  • Translation suggestions are turned off.
  • Any authenticated user can contribute.
  • The translation uses monolingual files.
  • The translation base language can not be edited.
Source code repository local:
Repository branch main
Weblate repository http://weblate.printf.kr/git/contributor-guide/localtest-master/doc-common/
File mask doc-common/*.pot
Monolingual base language file doc-common/en_US.pot
Translation file Download doc-common/en_GB.pot
Last change June 3, 2026, 12:39 p.m.
Last change made by Weblate Admin
Language English (United Kingdom)
Language code en_GB
Text direction Left to right
Case sensitivity Case-sensitive
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
06/03/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 522 8,948 59,400
Translated 95% 497 94% 8,416 94% 56,121
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 4% 22 4% 373 3% 2,143
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 4% 25 5% 532 5% 3,279
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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
JunJulAugSepOctNovDecJanFebMarAprMay

Quick numbers

8,948
Hosted words
522
Hosted strings
95%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+100%
Hosted words
—
+100%
Hosted strings
—
+95%
Translated
—
+100%
Contributors
—
User avatar admin

File uploaded
Processed 522 strings from the uploaded files (skipped: 0, not found: 0, updated: 522).
File upload mode: Replace existing translation file 06/03/2026
User avatar admin

File uploaded
Processed 522 strings from the uploaded files (skipped: 0, not found: 0, updated: 522).
File upload mode: Replace existing translation file 06/03/2026
User avatar admin

Translation replaced file by upload
Translation replaced file by upload 06/03/2026
User avatar admin

String added in the upload
Therefore, having a stable gate pipeline is crucial and the clean check requirement will help with the stable jobs.
Therefore, having a stable gate pipeline is crucial and the clean check requirement will help with the stable jobs.
Therefore, having a stable gate pipeline is crucial and the clean check requirement will help with the stable jobs.
06/03/2026
User avatar admin

String added in the upload
Changes in the gate pipeline are prioritized but also serialized. If a change fails, all tests for changes behind that failing change have to be restarted. If restarts after restarts happen, then resources are never freed up for the check pipeline.
Changes in the gate pipeline are prioritised but also serialised. If a change fails, all tests for changes behind that failing change have to be restarted. If restarts after restarts happen, then resources are never freed up for the check pipeline.
Changes in the gate pipeline are prioritized but also serialized. If a change fails, all tests for changes behind that failing change have to be restarted. If restarts after restarts happen, then resources are never freed up for the check pipeline.
06/03/2026
User avatar admin

String added in the upload
It also helps with approving changes that had been sitting around with a 6-month-old passing check.
It also helps with approving changes that had been sitting around with a 6-month-old passing check.
It also helps with approving changes that had been sitting around with a 6-month-old passing check.
06/03/2026
User avatar admin

String added in the upload
This avoids approving changes that have no hope of ever passing due to pep8 or other trivial errors.
This avoids approving changes that have no hope of ever passing due to pep8 or other trivial errors.
This avoids approving changes that have no hope of ever passing due to pep8 or other trivial errors.
06/03/2026
User avatar admin

String added in the upload
If your change fails in the gate, then there is an increased chance it is introducing non-deterministic failure behavior. Forcing it to go through check again helps make that more apparent.
If your change fails in the gate, then there is an increased chance it is introducing non-deterministic failure behavior. Forcing it to go through check again helps make that more apparent.
If your change fails in the gate, then there is an increased chance it is introducing non-deterministic failure behavior. Forcing it to go through check again helps make that more apparent.
06/03/2026
User avatar admin

String added in the upload
The OpenStack project uses what's called a `clean check` approach. This is designed to keep flaky changes out of the gate. A change always needs to pass the check before it enters the gate. If it fails in the gate, it re-enters the check pipeline.
The OpenStack project uses what's called a `clean check` approach. This is designed to keep flaky changes out of the gate. A change always needs to pass the check before it enters the gate. If it fails in the gate, it re-enters the check pipeline.
The OpenStack project uses what's called a `clean check` approach. This is designed to keep flaky changes out of the gate. A change always needs to pass the check before it enters the gate. If it fails in the gate, it re-enters the check pipeline.
06/03/2026
User avatar admin

String added in the upload
Why do changes go first in the check queue?
Why do changes go first in the check queue?
Why do changes go first in the check queue?
06/03/2026
Browse all translation changes