Project Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Checkmk 53% 23,038 221,986 1,423,799 3,538 11,180

Summary

Language code es
Aliased language codes es_es, es_la, esp, spa
English name of the language Spanish
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 507,599,381
Plural: Default plural 2 translations
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
Plural: CLDR v38+ plural 1 translation
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)
Plural: Qt Linguist plural 0 translations
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)
08/17/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 49,526 383,528 2,422,089
Approved 0% 0 0% 0 0% 0
Waiting for review 53% 26,467 42% 161,459 41% 997,725
Translated 53% 26,488 42% 161,542 41% 998,290
Needs editing 39% 19,500 42% 162,417 42% 1,035,922
Read-only 1% 21 1% 83 1% 565
Failing checks 22% 11,180 21% 83,240 22% 537,679
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 7% 3,538 15% 59,569 16% 387,877
Last 12 months Previous

Activity in last 12 months

459 changes 185 changes 216 changes 743 changes 489 changes 594 changes 340 changes 537 changes 370 changes 1,531 changes 245 changes 526 changes 194 changes 557 changes 368 changes 1,553 changes 366 changes 4,360 changes 3,179 changes 939 changes 1,134 changes 319 changes 212 changes 5,237 changes
AugSepOctNovDecJanFebMarAprMayJunJul

Quick numbers

383 k
Hosted words
49,526
Hosted strings
53%
Translated
7
Contributors
and previous 30 days

Trends of last 30 days

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

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

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

String added in the repository
Windows Time service status
Mostrar el estado del servicio
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.
Cuando el valor de este atributo cambia para una cuenta de usuario, todas las sesiones autenticadas actuales del usuario se invalidan y el usuario debe iniciar sesión de nuevo. Por defecto, este campo utiliza los campos que contienen la hora del último cambio de contraseña del usuario.
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>
Con esta opción puede definir el DN de un objeto de grupo que se utiliza para filtrar los usuarios. Sólo se sincronizarán los miembros de este grupo. Se trata de un filtro que puede utilizarse para ampliar las capacidades del "Filtro de búsqueda" normal. Con el filtro de búsqueda sólo puede definir filtros que se apliquen directamente a los objetos de usuario. Para filtrar por pertenencia a grupos, puede utilizar el atributo <tt>memberOf</tt> de los objetos de usuario en algunos directorios. Pero algunos directorios no tienen tales atributos porque las pertenencias se almacenan en los objetos de grupo como, por ejemplo, atributos <tt>member</tt>. Debería utilizar el filtro de búsqueda normal siempre que sea posible y sólo utilizar este filtro cuando sea realmente necesario. Finalmente se puede decir, que no se debe utilizar esta opción cuando se utiliza Active Directory. Esta opción es necesaria en los directorios OpenLDAP cuando se desea filtrar por pertenencia a un grupo.<br><br>Si la utiliza, indique aquí el nombre distinguido de un grupo, por ejemplo <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>
Con esta opción se puede definir un filtro LDAP opcional que se utiliza durante las búsquedas LDAP relacionadas con los grupos. Se puede utilizar para manejar sólo un subconjunto de los grupos por debajo del DN base dado.<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>
Con esta opción se puede definir un filtro LDAP opcional que se utiliza durante las búsquedas LDAP. Se puede utilizar para manejar sólo un subconjunto de los usuarios por debajo del DN base dado.<br><br>Algunos ejemplos comunes:<br><br> Todos los objetos de usuario en LDAP:<br> <tt>(&(objectclass=user)(objectcategory=persona))</tt><br> Miembros de un grupo:<br> <tt>(&(objectclass=user)(objectcategory=person)(memberof=CN=cmk-users,OU=groups,DC=example,DC=com))</tt><br> Miembros de un grupo anidado:<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.
 
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.
Este conjunto de reglas permite desplegar un plugin de agente que actualiza el agente Checkmk para Linux, Solaris y Windows de forma regular. El agente buscará nuevas actualizaciones de forma regular y se actualizará a sí mismo, cuando un nuevo agente bakeado esté disponible, liberado y firmado. <br><b>Nota</sup>1</sup>:</b> Este mecanismo de actualización está integrado en el propio agente. Así que después de activar esta característica se necesita al menos una actualización manual más del agente, por supuesto.<br><b>Nota<sup>2</sup>:</b> Después de desplegar este nuevo plugin es necesario llamarlo una vez manualmente para registrar el agente en su servidor de actualizaciones. Llame a <tt>cmk-update-agent -H <i>HOST</i></tt>, donde <i>HOST</i> debe ser el nombre de ese host en su monitorización. Encontrará el plugin en <tt>/usr/lib/check_mk_agent/plugins</tt> (UNIX) y en el subdirectorio <tt>plugins</tt> de su directorio de instalación del agente (Windows).
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.
Este plugin sincroniza un campo de la cuenta LDAP de los usuarios con el atributo pager de las cuentas de usuario de Setup, que es reenviado al núcleo de monitorización y puede ser usado para notificaciones. Por defecto se utiliza el atributo LDAP <tt>mobile</tt>.
08/15/2026
Browse all changes for this language