Source strings

49,639 Strings
100%
Browse Translate
383,728 Words
100%
2,423,576 Characters
100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
49,639 383,728 2,423,576
All strings Browse Translate Zen
49,420 383,322 2,420,666
Read-only strings Browse Translate Zen
49,639 383,728 2,423,576
Translated strings Browse Translate Zen
219 406 2,910
Strings waiting for review Browse Translate Zen
21,620 182,405 1,170,233
Strings with any failing checks Browse Translate Zen
87 1,359 9,006
Failing check: Unpluralised Browse Translate Zen
246 3,466 23,017
Failing check: Ellipsis Browse Translate Zen
15,098 108,362 705,646
Failing check: Multiple failing checks Browse Translate Zen
7,491 82,514 520,308
Failing check: Long untranslated Browse Translate Zen
414 5,526 31,790
Failing check: Multiple unnamed variables Browse Translate Zen
45 701 4,736
Labeled: auto-merge Browse Translate Zen
6 32 187
Labeled: new in loop Browse Translate Zen
3 79 502
Labeled: non-trivial Browse Translate Zen
9 40 268
Labeled: trivial Browse Translate Zen
49,582 382,908 2,418,070
Strings without a label Browse Translate Zen
Component Approved Translated Unreviewed Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary Checkmk GPL-2.0-or-later 70% 219
dev GPL-2.0-or-later 100% 100% 10,552
stable GPL-2.0-or-later 100% 100% 11,068

Summary

Project website checkmk.com
Instructions for translators

https://forum.checkmk.com/t/about-the-localization-category/21578
Project reviewers24 User avatar MarsellusWallaceUser avatar mhUser avatar Royal_TSUser avatar Elias VoelkerUser avatar athomaidisUser avatar thomas.koslowskiUser avatar gdspd_youUser avatar DanielNunesFerreiraUser avatar spUser avatar hirokoUser avatar sebastian.kirchmeyerUser avatar christian.reiserUser avatar mattias.schlenkerUser avatar thohenstattUser avatar anthony.healeyUser avatar RafaelUser avatar mpasamonteUser avatar ValerioUser avatar Francesco ToscanoUser avatar GianlucaUser avatar pripamontiUser avatar cmklemUser avatar eseyffarthUser avatar roua.chiboub
Language English
Language code en
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 1,728,473,503
08/17/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 49,639 383,728 2,423,576
Approved 0% 0 0% 0 0% 0
Waiting for review 1% 219 1% 406 1% 2,910
Translated 100% 49,639 100% 383,728 100% 2,423,576
Needs editing 0% 0 0% 0 0% 0
Read-only 99% 49,420 99% 383,322 99% 2,420,666
Failing checks 43% 21,620 47% 182,405 48% 1,170,233
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

429 changes 184 changes 199 changes 744 changes 463 changes 594 changes 321 changes 547 changes 358 changes 1,531 changes 226 changes 468 changes 173 changes 666 changes 331 changes 1,549 changes 339 changes 4,363 changes 3,141 changes 742 changes 578 changes 305 changes 214 changes 4,672 changes
AugSepOctNovDecJanFebMarAprMayJunJul

Quick numbers

383 k
Hosted words
49,639
Hosted strings
100%
Translated
9
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated
The “source.pot” file was changed. 08/17/2026
User avatar None

Resource updated
The “source.pot” file was changed. 08/15/2026
User avatar None

String added in the repository
Windows Time service status
Windows Time service status
08/15/2026
User avatar None

String added in the repository
When the value of this attribute changes for a user account, all current authenticated sessions of the user are invalidated and the user must login again. By default, this field uses the fields which hold the time of the last password change of the user.
When the value of this attribute changes for a user account, all current authenticated sessions of the user are invalidated and the user must login again. By default, this field uses the fields which hold the time of the last password change of the user.
08/15/2026
User avatar None

String added in the repository
Using this option, you can define the DN of a group object which is used to filter the users. Only members of this group will then be synchronized. This is a filter which can be used to extend capabilities of the regular "Search Filter". Using the search filter you can only define filters which directly apply to the user objects. To filter by group memberships, you can use the <tt>memberOf</tt> attribute of the user objects in some directories. But some directories do not have such attributes because the memberships are stored in the group objects as e.g. <tt>member</tt> attributes. You should use the regular search filter whenever possible and only use this filter when it is really necessary. So, this option should not be used when using Active Directory. This option is necessary in OpenLDAP directories when you want to filter by group membership.<br><br>If used, enter a plain distinguished name of a group here, e. g. <tt>CN=cmk-users,OU=groups,DC=example,DC=com</tt>
Using this option, you can define the DN of a group object which is used to filter the users. Only members of this group will then be synchronized. This is a filter which can be used to extend capabilities of the regular "Search Filter". Using the search filter you can only define filters which directly apply to the user objects. To filter by group memberships, you can use the <tt>memberOf</tt> attribute of the user objects in some directories. But some directories do not have such attributes because the memberships are stored in the group objects as e.g. <tt>member</tt> attributes. You should use the regular search filter whenever possible and only use this filter when it is really necessary. So, this option should not be used when using Active Directory. This option is necessary in OpenLDAP directories when you want to filter by group membership.<br><br>If used, enter a plain distinguished name of a group here, e. g. <tt>CN=cmk-users,OU=groups,DC=example,DC=com</tt>
08/15/2026
User avatar None

String added in the repository
Using this option, you can define an optional LDAP filter which is used during group related LDAP searches. It can be used to only handle a subset of the groups below the given base DN.<br><br>e.g. <tt>(objectclass=group)</tt>
Using this option, you can define an optional LDAP filter which is used during group related LDAP searches. It can be used to only handle a subset of the groups below the given base DN.<br><br>e.g. <tt>(objectclass=group)</tt>
08/15/2026
User avatar None

String added in the repository
Using this option, you can define an optional LDAP filter which is used during LDAP searches. It can be used to only handle a subset of the users below the given base DN.<br><br>Some common examples:<br><br> All user objects in LDAP:<br> <tt>(&(objectclass=user)(objectcategory=person))</tt><br> Members of a group:<br> <tt>(&(objectclass=user)(objectcategory=person)(memberof=CN=cmk-users,OU=groups,DC=example,DC=com))</tt><br> Members of a nested group:<br> <tt>(&(objectclass=user)(objectcategory=person)(memberof:1.2.840.113556.1.4.1941:=CN=cmk-users,OU=groups,DC=example,DC=com))</tt><br>
Using this option, you can define an optional LDAP filter which is used during LDAP searches. It can be used to only handle a subset of the users below the given base DN.<br><br>Some common examples:<br><br> All user objects in LDAP:<br> <tt>(&(objectclass=user)(objectcategory=person))</tt><br> Members of a group:<br> <tt>(&(objectclass=user)(objectcategory=person)(memberof=CN=cmk-users,OU=groups,DC=example,DC=com))</tt><br> Members of a nested group:<br> <tt>(&(objectclass=user)(objectcategory=person)(memberof:1.2.840.113556.1.4.1941:=CN=cmk-users,OU=groups,DC=example,DC=com))</tt><br>
08/15/2026
User avatar None

String added in the repository
To start updating the agent package, the agent updater must register at a monitoring site.<br><br><i>New with Checkmk 2.5</i>: By default, the agent updater will be registered by the agent controller, after its own successful registration, at the same site and with the same host name.<br><br>Here you can configure the overwriting behavior of subsequent agent controller registrations, or opt to skip the agent controller triggered agent updater registration entirely.<br>Consider the differences between agent controller and agent updater registrations: The agent controller can register at multiple sites, or overwrite existing registrations when registering for the same site again. The agent updater can only hold one registration at a time. Every new registration will overwrite the previous one, regardless of the connection details.<br><br>Available Choices:<ul><li><b>On first agent controller registration</b>: An existing Agent Updater registration will be kept. If you register the agent controller at multiple sites, only the first site will be used for agent updates.</li><li><b>On every agent controller registration</b>: The Agent Updater registration will be overwritten on every agent controller registration. If you register the agent controller at multiple sites, only the last site will be used for agent updates.</li><li><b>Manual</b>: Manually register the agent updater.<br>Either on agent controller registration with explicit flag: <tt>cmk-agent-ctl register [args] --automatic-updates</tt><br>Or separately: <tt>cmk-update-agent register</tt> (Linux)/<tt>check_mk_agent.exe updater register</tt> (Windows).<br>Since the registration is handled manually by the user, any existing agent updater registration will be overwritten.</li></ul><i>Note</i>: Since the agent controller is available for Linux and Windows only, this setting is not relevant for Solaris, where the agent updater will always need to be registered manually.
To start updating the agent package, the agent updater must register at a monitoring site.<br><br><i>New with Checkmk 2.5</i>: By default, the agent updater will be registered by the agent controller, after its own successful registration, at the same site and with the same host name.<br><br>Here you can configure the overwriting behavior of subsequent agent controller registrations, or opt to skip the agent controller triggered agent updater registration entirely.<br>Consider the differences between agent controller and agent updater registrations: The agent controller can register at multiple sites, or overwrite existing registrations when registering for the same site again. The agent updater can only hold one registration at a time. Every new registration will overwrite the previous one, regardless of the connection details.<br><br>Available Choices:<ul><li><b>On first agent controller registration</b>: An existing Agent Updater registration will be kept. If you register the agent controller at multiple sites, only the first site will be used for agent updates.</li><li><b>On every agent controller registration</b>: The Agent Updater registration will be overwritten on every agent controller registration. If you register the agent controller at multiple sites, only the last site will be used for agent updates.</li><li><b>Manual</b>: Manually register the agent updater.<br>Either on agent controller registration with explicit flag: <tt>cmk-agent-ctl register [args] --automatic-updates</tt><br>Or separately: <tt>cmk-update-agent register</tt> (Linux)/<tt>check_mk_agent.exe updater register</tt> (Windows).<br>Since the registration is handled manually by the user, any existing agent updater registration will be overwritten.</li></ul><i>Note</i>: Since the agent controller is available for Linux and Windows only, this setting is not relevant for Solaris, where the agent updater will always need to be registered manually.
08/15/2026
User avatar None

String added in the repository
This rule set allows to deploy an agent plug-in that updates the Checkmk agent for Linux, Solaris and Windows on a regular base. The agent will look for new updates on a regular base and update itself, when a newly baked agent is available, released and signed. <br><b>Note<sup>1</sup>:</b> This update mechanism is baked into the agent itself. So after activating this feature you need at least one more manual update of the agent, of course.<br><b>Note<sup>2</sup>:</b> After deploying this new plug-in it must be registered at your Checkmk server. This can be done either by registering the Agent Controller, or by manual agent updater registration call. Customizable in _Registration_ option below. See there for details.<br><b>Note<sup>3</sup>:</b> In order to deploy this plug-in to Solaris, a Python 3.7 installation (or newer) with installed python packages "cryptography", "requests" and "PySocks" is required on the target hosts.
This rule set allows to deploy an agent plug-in that updates the Checkmk agent for Linux, Solaris and Windows on a regular base. The agent will look for new updates on a regular base and update itself, when a newly baked agent is available, released and signed. <br><b>Note<sup>1</sup>:</b> This update mechanism is baked into the agent itself. So after activating this feature you need at least one more manual update of the agent, of course.<br><b>Note<sup>2</sup>:</b> After deploying this new plug-in it must be registered at your Checkmk server. This can be done either by registering the Agent Controller, or by manual agent updater registration call. Customizable in _Registration_ option below. See there for details.<br><b>Note<sup>3</sup>:</b> In order to deploy this plug-in to Solaris, a Python 3.7 installation (or newer) with installed python packages "cryptography", "requests" and "PySocks" is required on the target hosts.
08/15/2026
User avatar None

String added in the repository
This plug-in synchronizes a field of the users LDAP account to the pager attribute of the Setup user accounts, which is then forwarded to the monitoring core and can be used for notifications. By default, the LDAP attribute <tt>mobile</tt> is used.
This plug-in synchronizes a field of the users LDAP account to the pager attribute of the Setup user accounts, which is then forwarded to the monitoring core and can be used for notifications. By default, the LDAP attribute <tt>mobile</tt> is used.
08/15/2026
Browse all changes for this language