The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not push the repository.

Translation status

103 Strings 100%
Browse Translate
2,035 Words 100%
15,906 Characters 100%

Strings status

Strings Words Characters
103 2,035 15,906
All strings Browse Translate Zen
103 2,035 15,906
Translated strings Browse Translate Zen
6 64 752
Translated strings with dismissed checks Browse Translate Zen

Summary

Project website pagure.io/fedora-docs-l10n/fedora-coreos
Instructions for translators

Mailing list for translators: trans@lists.fedoraproject.org
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository ssh://pagure.io/fedora-docs-l10n/fedora-coreos.git
Repository branch master
Last remote commit automatic update of pot/po files e7be5268e
♪ I'm a bot, bot, bot ♪ authored 6 days ago
Last commit in Weblate Translated using Weblate (Italian) b4f27708f
User avatar iceman authored 2 weeks ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-fedora-coreos/nav/
File mask po/*/master/pages/faq.po
Translation file Download po/es/master/pages/faq.po
Last change May 18, 2025, 10:22 p.m.
Last change made by None
Language Spanish
Language code es
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 507,161,083
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
12 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 103 2,035 15,906
Translated 100% 103 100% 2,035 100% 15,906
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
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

14 changes 0 changes 0 changes 0 changes 0 changes 0 changes 9 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 4 changes 0 changes 0 changes 5 changes 6 changes 2 changes 0 changes 134 changes
JunJulAugSepOctNovDecJanFebMarAprMay

Quick numbers

2,035
Hosted words
103
Hosted strings
100%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed
Changes committed 4 weeks ago
User avatar cyphra

Translation changed
It is worth noting that in Fedora CoreOS we have `docker.service` disabled by default but it is easily started if anything communicates with the `/var/run/docker.sock` because `docker.socket` is enabled by default. This means that if a user runs any `docker` command (via `sudo docker`) then the daemon will be activated.
Cabe destacar que en Fedora CoreOS, `docker.service` está deshabilitado por defecto, pero se inicia fácilmente si cualquiera se comunica con `/var/run/docker.sock`, ya que `docker.socket` está habilitado por defecto. Esto significa que si un usuario ejecuta cualquier comando `docker` (mediante `sudo docker`), el demonio será activado.
4 weeks ago
User avatar cyphra

Translation changed
It is worth noting that in Fedora CoreOS we have `docker.service` disabled by default but it is easily started if anything communicates with the `/var/run/docker.sock` because `docker.socket` is enabled by default. This means that if a user runs any `docker` command (via `sudo docker`) then the daemon will be activated.
Cabe destacar que en Fedora CoreOS, `docker.service` está deshabilitado por defecto, pero se inicia fácilmente si cualquiera se comunica con `/var/run/docker.sock`, ya que `docker.socket` está habilitado por defecto. Esto significa que si un usuario ejecuta cualquier comando docker (mediante `sudo docker`), el demonio será activado.
4 weeks ago
User avatar cyphra

Translation changed
It is worth noting that in Fedora CoreOS we have `docker.service` disabled by default but it is easily started if anything communicates with the `/var/run/docker.sock` because `docker.socket` is enabled by default. This means that if a user runs any `docker` command (via `sudo docker`) then the daemon will be activated.
Cabe destacar que en Fedora CoreOS, `docker.service` está deshabilitado por defecto, pero se inicia fácilmente si se comunica con `/var/run/docker.sock`, ya que `docker.socket` está habilitado por defecto. Esto significa que si un usuario ejecuta cualquier comando docker (mediante `sudo docker`), el demonio será activado.
4 weeks ago
User avatar cyphra

Suggestion removed
Mailing list: https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/[coreos@lists.fedoraproject.org]
*Listados de cCorreo:* https://lists.fedoraproject.org/archives/list/coreosdiversity@lists.fedoraproject.org/[coreosdiversity@lists.fedoraproject.org]
4 weeks ago
User avatar cyphra

Translation completed
Translation completed 4 weeks ago
User avatar cyphra

Translation changed
variant: fcos
version: {butane-latest-stable-spec}
systemd:
units:
- name: dnsmasq.service
mask: false
enabled: true
variant: fcos
version: {butane-latest-stable-spec}
systemd:
units:
- name: dnsmasq.service
mask: false
enabled: true
4 weeks ago
User avatar cyphra

Translation changed
dnsmasq is useful for running a DHCP/DNS/TFTP server for external clients (i.e. not local to the host), too, but that is something we'd prefer users to do in a container. Putting the service in a container insulates the hosted service from breakage as a result of host layer changes. For example, if NetworkManager and podman stopped using dnsmasq, we would remove it from the host and the service you depend on would cease to work.
dnsmasq también es útil para ejecutar un servidor DHCP/DNS/TFTP para clientes externos (es decir, no locales del host), pero es algo que preferiríamos que los usuarios hicieran en un contenedor. Colocar el servicio en un contenedor lo protege de interrupciones causadas por cambios en la capa del host. Por ejemplo, si NetworkManager y podman dejaran de usar dnsmasq, lo eliminaríamos del host y el servicio del que depende dejaría de funcionar.
4 weeks ago
User avatar cyphra

Marked for edit
dnsmasq is useful for running a DHCP/DNS/TFTP server for external clients (i.e. not local to the host), too, but that is something we'd prefer users to do in a container. Putting the service in a container insulates the hosted service from breakage as a result of host layer changes. For example, if NetworkManager and podman stopped using dnsmasq, we would remove it from the host and the service you depend on would cease to work.
dnsmasq también es útil para ejecutar un servidor DHCP/DNS/TFTP para clientes externos (es decir, no locales del host), pero es algo que preferiríamos que los usuarios hicieran en un contenedor.
4 weeks ago
User avatar cyphra

Translation changed
dnsmasq is useful for running a DHCP/DNS/TFTP server for external clients (i.e. not local to the host), too, but that is something we'd prefer users to do in a container. Putting the service in a container insulates the hosted service from breakage as a result of host layer changes. For example, if NetworkManager and podman stopped using dnsmasq, we would remove it from the host and the service you depend on would cease to work.
dnsmasq también es útil para ejecutar un servidor DHCP/DNS/TFTP para clientes externos (es decir, no locales del host), pero es algo que preferiríamos que los usuarios hicieran en un .contenedor.
4 weeks ago
Browse all translation changes