Translation status

56 Strings 96%
Browse Translate
2,293 Words 96%
17,325 Characters 95%

Strings status

Strings Words Characters
56 2,293 17,325
All strings Browse Translate Zen
54 2,205 16,541
Translated strings Browse Translate Zen
2 88 784
Unfinished strings Browse Translate Zen
2 88 784
Strings marked for edit Browse Translate Zen

Overview

Project website pagure.io/fedora-docs-l10n/quick-docs
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/quick-docs.git
Repository branch master
Last remote commit automatic update of pot/po files 9e7cac8ada
♪ I'm a bot, bot, bot ♪ authored 3 days ago
Last commit in Weblate Translated using Weblate (Spanish) 057d79c034
Weblate Translation Memory authored 2 hours ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-quick-docs/nav/
File mask po/*/master/pages/fedora-repositories.po
Translation file Download po/es/master/pages/fedora-repositories.po
Last change June 15, 2024, 10:50 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
11 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 56 2,293 17,325
Translated 96% 54 96% 2,205 95% 16,541
Needs editing 3% 2 3% 88 4% 784
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

0 changes 62 changes 0 changes 1 change 0 changes 5 changes 0 changes 0 changes 60 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
AprMayJunJulAugSepOctNovDecJanFebMar

Quick numbers

2,293
Hosted words
56
Hosted strings
96%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated
The “po/es/master/pages/fedora-repositories.po” file was changed. 10 months ago
User avatar None

String added in the repository
In Branched releases - the state a release is in between branching from Rawhide and stable release, see https://fedoraproject.org/wiki/Releases/Branched[Branched] for more details - the fedora repository alone represents the release's stable state. The _updates_ repository for Branched releases is not used until they become stable. Before the https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updates-testing-activation[updates-testing activation], package builds for the Branched release are sent directly to this repository. After the _Bodhi enabling point_, package builds that pass the https://fedoraproject.org/wiki/Updates_Policy[Updates Policy] move from _updates-testing_ repository to this repository.
En las versiones Branched – el estado en el que se encuentra una versión entre la ramificación de Rawhide y la versión estable, vea más detalles en https://fedoraproject.org/wiki/Releases/Branched[Branched] – el repositorio fedora por si solo representa el estado estable de la versión. El repositorio _updates_ (actualizaciones) para las versiones Branched no se usa hasta que llegan a ser estable. Antes del https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling[punto de habilitación Bodhi], los paquetes construidos para la versión Branched son enviados directamente a este repositorio. Después del _punto de habilitación Bodhi_, los paquetes construidos que pasen la https://fedoraproject.org/wiki/Updates_Policy[Política de Actualizaciones] se mueven del repositorio _updates-testing_ a este repositorio.
10 months ago
User avatar None

Source string changed
In Branched releases - the state a release is in between branching from Rawhide and stable release, see https://fedoraproject.org/wiki/Releases/Branched[Branched] for more details - the fedora repository alone represents the release's stable state. The _updates_ repository for Branched releases is not used until they become stable. Before the https://docs.fedoraproject.org/wikien-US/fesco/Updates_Policy#Bodhi_enabling[Bodhi enabling point/#updates-testing-activation[updates-testing activation], package builds for the Branched release are sent directly to this repository. After the _Bodhi enabling point_, package builds that pass the https://fedoraproject.org/wiki/Updates_Policy[Updates Policy] move from _updates-testing_ repository to this repository.
10 months ago
User avatar None

String added in the repository
yohaan vakil; Otto Urpelainen; Chetan Giradkar; Adam Williamson
Yohaan vakil, Otto Urpelainen, Ooyama Yosiyuki
10 months ago
User avatar None

Source string changed
yohaan vakil; Otto Urpelainen; Ooyama YosiyukiChetan Giradkar; Adam Williamson
10 months ago
User avatar None

Changes committed
Changes committed 11 months ago
User avatar vareli

Translation completed
Translation completed 11 months ago
User avatar vareli

Translation added
For this and other less important functions, we need as much feedback as possible, so it makes sense to have all pre-release testers have _updates-testing_ enabled by default, and encourage them to provide feedback through Bodhi.
Para esta y otras funciones menos importantes, necesitamos tantos comentarios como sea posible, por lo que tiene sentido que todos los evaluadores previos al lanzamiento tengan habilitado _updates-testing_ de modo predeterminado y les alentamos a proporcionar comentarios a través de Bodhi.
11 months ago
User avatar vareli

Translation added
The main purpose is to insulate _image builds_ from potentially problematic changes. Branched images - nightly images, and the Alpha, Beta and GA (Final) _milestone_ builds and their https://fedoraproject.org/wiki/Go_No_Go_Meeting[test compose and release candidate builds] - are built from the _stable_ packages, that is, only those in the _fedora_ repository, not those in _updates-testing_. In this sense, _updates-testing_ protects not a set of users, but a set of _builds_, from potentially destabilizing changes. Especially when we are building an Alpha, Beta or GA release, we need to be able to reduce the amount of change in the package set between composes in order to produce an image of high quality. The _updates-testing_ mechanism allows for that: during https://fedoraproject.org/wiki/Milestone_freezes[Milestone freezes], new builds can be sent to _updates-testing_, but cannot move from there to _stable_ (_fedora_) without special circumstances. In this way, we can work on release images while not preventing packagers from sending out builds.
El objetivo principal es aislar la_ creación de imágenes_ de cambios potencialmente problemáticos. Las imágenes – imágenes nocturnas y las compilaciones de _hitos_ Alpha, Beta y GA (Final) y sus https://fedoraproject.org/wiki/Go_No_Go_Meeting[composiciones candidatas de prueba y lanzamiento] – se construyen desde paquetes estables, esto es, solo aquellos del repositorio _fedora_, no los que están en _updates-testing_. En este sentido, _updates-testing_ protege no a un conjunto de usuarios, sino a un conjunto de _compilaciones_ de cambios potencialmente desestabilizadores. Especialmente cuando estamos compilando una versión Alpha, Beta o GA, necesitamos reducir la cantidad de cambios en el conjunto de paquetes entre composiciones con el objetivo de producir una imagen de alta calidad. El mecanismo de _updates-testing_ permite por esto: durante los https://fedoraproject.org/wiki/Milestone_freezes[Hitos congelados], se pueden enviar nuevas compilaciones a _updates-testing_, pero no se pueden mover de allí a _stable_ (_fedora_) sin circunstancias especiales. De este modo, podemos trabajar en las imágenes de la versión sin evitar que los empaquetadores puedan mandar compilaciones.
11 months ago
User avatar vareli

Translation added
When it comes to a Branched pre-release, the expectation is that anyone who installs it wants to help test it: we effectively consider anyone running a Branched release to be a tester. The function of _updates-testing_ is different in this case. There is not a 'general user population' of Branched users who run with _updates-testing_ disabled, and are protected from problematic updates by the group of update testers. Instead, _updates-testing_ in Branched serves other important functions.
Cuando se trata de una versión preliminar Branched, la expectativa es que cualquiera que la instale pueda llegar a probarla: nosotros, efectivamente, consideramos que cualquiera que ejecute una versión Branched es un evaluador. La función de _updates-testing_ en este caso es diferente. No existe una 'población general de usuarios' de Branched que lo ejecuten con _updates-testing_ deshabilitado y estén protegidos de actualizaciones problemáticas por el grupo de evaluadores de actualización. En su lugar, _updates-testing_ en Branched cumple otras funciones importantes.
11 months ago
Browse all translation changes