Source strings

276 Strings
100%
Browse Translate
5,835 Words
100%
36,506 Characters
100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
276 5,835 36,506
All strings Browse Translate Zen
276 5,835 36,506
Read-only strings Browse Translate Zen
31 437 3,000
Strings with any failing checks Browse Translate Zen
2 10 71
Failing check: Ellipsis Browse Translate Zen
31 437 3,000
Failing check: Multiple failing checks Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
doc
doc-common 100% 74
doc-contributing 100% 7
doc-non-code-contribution
doc-operators 100% 7
doc-organizations 100% 8
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-code-and-documentation/
File mask doc-code-and-documentation/*.pot
Monolingual base language file doc-code-and-documentation/en_US.pot
Translation file Download doc-code-and-documentation/en_US.pot
Last change June 3, 2026, 12:03 p.m.
Last change made by None
Language English (United States)
Language code en_US
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 276 5,835 36,506
Translated 100% 276 100% 5,835 100% 36,506
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 276 100% 5,835 100% 36,506
Failing checks 11% 31 7% 437 8% 3,000
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

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

5,835
Hosted words
276
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

+100%
Hosted words
—
+100%
Hosted strings
—
+100%
Translated
—
—
Contributors
—
User avatar None

Resource updated
File “doc-code-and-documentation/en_US.pot” was added. 06/03/2026
User avatar None

String added in the repository
See `Stable Branches <https://docs.openstack.org/project-team-guide/stable-branches.html>`__ for more information.
See `Stable Branches <https://docs.openstack.org/project-team-guide/stable-branches.html>`__ for more information.
See `Stable Branches <https://docs.openstack.org/project-team-guide/stable-branches.html>`__ for more information.
06/03/2026
User avatar None

String added in the repository
The `final change <https://review.opendev.org/c/openstack/nova/+/950217>`__ should have several `(cherry picked from <sha>)` at the bottom of the commit message.
The `final change <https://review.opendev.org/c/openstack/nova/+/950217>`__ should have several `(cherry picked from <sha>)` at the bottom of the commit message.
The `final change <https://review.opendev.org/c/openstack/nova/+/950217>`__ should have several `(cherry picked from <sha>)` at the bottom of the commit message.
06/03/2026
User avatar None

String added in the repository
In order to backport a commit that has been merged to master, the commit must be backported to all :ref:`open branches <stable-branches>` between master and the target branch (even if some of those branches are Unmaintained). If a commit must be backported to multiple branches, each backport should be cherry-picked from the next-newest backport. For example, to cherry-pick change `I06b19044 <https://review.opendev.org/q/I06b19044876aab9b4585384352f8dccc39984526>`__ with change number `946581 <https://review.opendev.org/c/openstack/nova/+/946581>`__ from `master` (2025.2) to `stable/2024.1`:
In order to backport a commit that has been merged to master, the commit must be backported to all :ref:`open branches <stable-branches>` between master and the target branch (even if some of those branches are Unmaintained). If a commit must be backported to multiple branches, each backport should be cherry-picked from the next-newest backport. For example, to cherry-pick change `I06b19044 <https://review.opendev.org/q/I06b19044876aab9b4585384352f8dccc39984526>`__ with change number `946581 <https://review.opendev.org/c/openstack/nova/+/946581>`__ from `master` (2025.2) to `stable/2024.1`:
In order to backport a commit that has been merged to master, the commit must be backported to all :ref:`open branches <stable-branches>` between master and the target branch (even if some of those branches are Unmaintained). If a commit must be backported to multiple branches, each backport should be cherry-picked from the next-newest backport. For example, to cherry-pick change `I06b19044 <https://review.opendev.org/q/I06b19044876aab9b4585384352f8dccc39984526>`__ with change number `946581 <https://review.opendev.org/c/openstack/nova/+/946581>`__ from `master` (2025.2) to `stable/2024.1`:
06/03/2026
User avatar None

String added in the repository
Backports
Backports
Backports
06/03/2026
User avatar None

String added in the repository
The change ID is the same as in the previous case.
The change ID is the same as in the previous case.
The change ID is the same as in the previous case.
06/03/2026
User avatar None

String added in the repository
If your commit depends on a change which has been updated since you started your work, and you need to get the latest patchset from that change, you can cherry-pick your own changes on top of it:
If your commit depends on a change which has been updated since you started your work, and you need to get the latest patchset from that change, you can cherry-pick your own changes on top of it:
If your commit depends on a change which has been updated since you started your work, and you need to get the latest patchset from that change, you can cherry-pick your own changes on top of it:
06/03/2026
User avatar None

String added in the repository
Cherry-picking
Cherry-picking
Cherry-picking
06/03/2026
User avatar None

String added in the repository
After checking out the patch, you will be switched to a new branch automatically, on which you can make your changes.
After checking out the patch, you will be switched to a new branch automatically, on which you can make your changes.
After checking out the patch, you will be switched to a new branch automatically, on which you can make your changes.
06/03/2026
User avatar None

String added in the repository
The change ID can be found on the web UI of Gerrit:
The change ID can be found on the web UI of Gerrit:
The change ID can be found on the web UI of Gerrit:
06/03/2026
Browse all translation changes