Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English (United States) 100% 1
Please sign in to see the alerts.

Summary

Project website opendev.org/openstack/keystone
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/keystone/master/doc-admin/
File mask doc-admin/*.pot
Monolingual base language file doc-admin/en_US.pot
10/19/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,807 38,719 253,848
Source 1,807 38,719 253,848
Translated 100% 1,807 100% 38,719 100% 253,848
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 1,807 100% 38,719 100% 253,848
Failing checks 1% 1 1% 6 1% 49
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 1,812 changes
OctNovDecJanFebMarAprMayJunJulAugSep

Quick numbers

38,719
Hosted words
1,807
Hosted strings
100%
Translated
1
Contributors
0
Components
1
Languages
1
Translations
0
Screenshots
and previous 30 days

Trends of last 30 days

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

Alert triggered
No file mask matches. 09/25/2026
User avatar None

Resource updated
File “doc-admin/en_US.pot” was added. 09/25/2026
User avatar None

String added in the repository
It is recommended that installations take the steps necessary to where they can run with both options set to ``strict`` as soon as is practical.
It is recommended that installations take the steps necessary to where they can run with both options set to ``strict`` as soon as is practical.
It is recommended that installations take the steps necessary to where they can run with both options set to ``strict`` as soon as is practical.
09/25/2026
User avatar None

String added in the repository
When set to ``off`` (which is the default), no checking is done on the URL safeness of names. When set to ``new``, an attempt to create a new project or domain with an unsafe name (or update the name of a project or domain to be unsafe) will cause a status code of 400 (Bad Request) to be returned. Setting the configuration option to ``strict`` will, in addition to preventing the creation and updating of entities with unsafe names, cause an authentication attempt which specifies a project or domain name that is unsafe to return a status code of 401 (Unauthorized).
When set to ``off`` (which is the default), no checking is done on the URL safeness of names. When set to ``new``, an attempt to create a new project or domain with an unsafe name (or update the name of a project or domain to be unsafe) will cause a status code of 400 (Bad Request) to be returned. Setting the configuration option to ``strict`` will, in addition to preventing the creation and updating of entities with unsafe names, cause an authentication attempt which specifies a project or domain name that is unsafe to return a status code of 401 (Unauthorized).
When set to ``off`` (which is the default), no checking is done on the URL safeness of names. When set to ``new``, an attempt to create a new project or domain with an unsafe name (or update the name of a project or domain to be unsafe) will cause a status code of 400 (Bad Request) to be returned. Setting the configuration option to ``strict`` will, in addition to preventing the creation and updating of entities with unsafe names, cause an authentication attempt which specifies a project or domain name that is unsafe to return a status code of 401 (Unauthorized).
09/25/2026
User avatar None

String added in the repository
The safety of the names of projects and domains can be controlled via two configuration options:
The safety of the names of projects and domains can be controlled via two configuration options:
The safety of the names of projects and domains can be controlled via two configuration options:
09/25/2026
User avatar None

String added in the repository
In the future, keystone may offer the ability to identify a project in a hierarchy via a URL style of naming from the root of the hierarchy (for example specifying 'projectA/projectB/projectC' as the project name in an authentication request). In order to prepare for this, keystone supports the optional ability to ensure both projects and domains are named without including any of the reserved characters specified in section 2.2 of `rfc3986 <http://tools.ietf.org/html/rfc3986>`_.
In the future, keystone may offer the ability to identify a project in a hierarchy via a URL style of naming from the root of the hierarchy (for example specifying 'projectA/projectB/projectC' as the project name in an authentication request). In order to prepare for this, keystone supports the optional ability to ensure both projects and domains are named without including any of the reserved characters specified in section 2.2 of `rfc3986 <http://tools.ietf.org/html/rfc3986>`_.
In the future, keystone may offer the ability to identify a project in a hierarchy via a URL style of naming from the root of the hierarchy (for example specifying 'projectA/projectB/projectC' as the project name in an authentication request). In order to prepare for this, keystone supports the optional ability to ensure both projects and domains are named without including any of the reserved characters specified in section 2.2 of `rfc3986 <http://tools.ietf.org/html/rfc3986>`_.
09/25/2026
User avatar None

String added in the repository
URL safe naming of projects and domains
URL safe naming of projects and domains
URL safe naming of projects and domains
09/25/2026
User avatar None

String added in the repository
A return code of ``4`` means that the expansion and data migration stages are complete, and the next step is to run ``keystone-manage db_sync --contract``.
A return code of ``4`` means that the expansion and data migration stages are complete, and the next step is to run ``keystone-manage db_sync --contract``.
A return code of ``4`` means that the expansion and data migration stages are complete, and the next step is to run ``keystone-manage db_sync --contract``.
09/25/2026
User avatar None

String added in the repository
A return code of ``2`` means that an upgrade from your current database version is available, your database is not currently under version control, or the database is already under control. Your first step is to run ``keystone-manage db_sync --expand``.
A return code of ``2`` means that an upgrade from your current database version is available, your database is not currently under version control, or the database is already under control. Your first step is to run ``keystone-manage db_sync --expand``.
A return code of ``2`` means that an upgrade from your current database version is available, your database is not currently under version control, or the database is already under control. Your first step is to run ``keystone-manage db_sync --expand``.
09/25/2026
User avatar None

String added in the repository
A return code of ``1`` generally means something serious is wrong with your database and operator intervention will be required.
A return code of ``1`` generally means something serious is wrong with your database and operator intervention will be required.
A return code of ``1`` generally means something serious is wrong with your database and operator intervention will be required.
09/25/2026
Browse all component changes