Translation status

1,091 Strings 98%
Browse Translate
28,196 Words 97%

Strings status

1,091
All strings — 28,196 words Browse Translate Zen
1,071
Translated strings — 27,569 words Browse Translate Zen
20
Unfinished strings — 627 words Browse Translate Zen
6
Untranslated strings — 99 words Browse Translate Zen
14
Strings marked for edit — 528 words Browse Translate Zen
20
Unfinished strings without suggestions — 627 words Browse Translate Zen
181
Translated strings with dismissed checks — 3,757 words Browse Translate Zen
5
Strings with comments — 306 words Browse Translate Zen
1,091
Strings without a label — 28,196 words Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
books/developers-handbook/kerneldebug/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 210 5,085 33,598 210 0 0 0
books/fdp-primer/rosetta/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 62 417 4,051 62 0 0 0
books/handbook/wayland/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 135 4,029 26,851 135 0 0 0
books/developers-handbook/policies/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 51 1,159 7,777 51 0 0 0
books/arch-handbook/scsi/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 356 8,562 62,236 356 0 0 0
books/handbook/zfs/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 547 19,873 136,360 547 1 0 0
books/fdp-primer/weblate/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 157 1,843 13,659 157 0 0 0
books/developers-handbook/ipv6/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 293 6,065 41,182 293 0 0 0
books/developers-handbook/x86/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 924 21,343 120,765 924 1 0 0
books/handbook/disks/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 660 14,329 90,448 659 2 0 0
Browse all components

Overview

Project website docs.freebsd.org/en
Translation license BSD 2-Clause "Simplified" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
File mask documentation/content/*/articles/committers-guide/_index.po
Translation file Download documentation/content/es/articles/committers-guide/_index.po
Last change Jan. 17, 2024, 11:50 p.m.
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,091 28,196 178,860
Translated 98% 1,071 97% 27,569 97% 174,473
Needs editing 1% 14 1% 528 1% 3,521
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 1% 6 1% 99 1% 866
Last 12 months Previous

Activity in last 12 months

0 changes 499 changes 1 change 102 changes 0 changes 4 changes 4 changes 373 changes 2 changes 0 changes 1,136 changes 263 changes 70 changes 0 changes 0 changes 0 changes 0 changes 0 changes 63 changes 10 changes 0 changes 0 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

28,196
Hosted words
1,091
Hosted strings
98%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

New strings to translate

Documentation / articles/committers-guide/_index — Spanish

4 new strings to translate appeared to the translation. 3 months ago
User avatar None

Resource update

Documentation / articles/committers-guide/_index — Spanish

The "documentation/content/es/articles/committers-guide/_index.po" file was changed. 3 months ago
User avatar None

String updated in the repository

Documentation / articles/committers-guide/_index — Spanish

FreeBSD builds with both Clang and GCC. The project does this in a careful and controlled way to maximize benefits from this extra work, while keeping the extra work to a minimum. Supporting both Clang and GCC improves the flexibility our users have. These compilers have different strengths and weaknesses, and supporting both allows users to pick the best one for their needs. Clang and GCC support similar dialects of C and C++, necessitating a relatively small amount of conditional code. The project gains increased code coverage and improves the code quality by using features from both compilers. The project is able to build in more user environments and leverage more CI environments by supporting this range, increasing convenience for users and giving them more tools to test with. By carefully constraining the range of versions supported to modern versions of these compilers, the project avoids unduly increasing the testing matrix. Older and obscure compilers, as well as older dialects of the languages, have extremely limited support that allow user programs to build with them, but without constraining the base system to being built with them. The exact balance continues to evolve to ensure the benefits of extra work remain greater than the burdens it imposes. The project used to support really old Intel compilers or old GCC versions, but we traded supporting those obsolete compilers for a carefully selected range of modern compilers. This section documents where we use different compilers, and the expectations around that.
FreeBSD compila tanto con Clang como con GCC. El proyecto hace esto de forma cuidadosa y controlada para maximizar los beneficios de este trabajo extra, a la vez que mantiene el trabajo extra en mínimos. Suportar tanto Clang como GCC mejora la flexibilidad que tienen nuestros usuarios. Estos compiladores tienen distintas fortalezas y debilidades, y soportar ambos permite a los usuarios escoger el que mejor se adapta a sus necesidades. Clang y GCC soportan dialectos similares de C y C++, necesitándose una cantidad relativamente pequeña de código condicional. El proyecto gana más cobertura de código y mejora la calidad del código usando características de ambos compiladores. El proyecto es capaz de compilar en más entornos de usuario y aprovechar más entornos de CI al soportar este rango, incrementando las ventajas para los usuarios y dándoles más herramientas con las que probar. Mediante la restricción cuidadosa de las versiones modernas soportadas en estos compiladores, el proyecto evita incrementar la matriz de pruebas sin necesidad. Los compiladores más viejos y oscuros, así como dialectos más antiguos de los lenguajes, tienen un soporte extremadamente limitado que permite a los programas de usuarios compilar con ellos, pero sin limitar a que el sistema base se compile con ellos. El equilibro exacto está en constante evolución para asegurar que los beneficios del trabajo extra son mayores que la carga que imponen. El proyecto solía soportar compiladores de Intel realmente antiguos o versiones antiguas de GCC, pero cambiamos soportar esos compiladores obsoletos por una selección cuidadosas de compiladores modernos. Esta sección documenta dónde usamos los diferentes compiladores, y las expectativas al respecto.
3 months ago
User avatar None

Source string changed

Documentation / articles/committers-guide/_index — Spanish

FreeBSD builds with both Clang and GCC. The project does this in a careful and controlled way to maximize benefits from this extra work, while keeping the extra work to a minimum. Supporting both Clang and GCC improves the flexibility our users have. These compilers have different strengths and weaknesses, and supporting both allows users to pick the best one for their needs. Clang and GCC support similar dialects of C and C++, necessitating a relatively small amount of conditional code. The project gains increased code coverage and improves the code quality by using features from both compilers. The project is able to build in more user environments and leverage more CI environments by supporting this range, increasing convenience for users and giving them more tools to test with. By carefully constraining the range of versions supported to modern versions of these compilers, the project avoids unduely increasing the testing matrix. Older and obscure compilers, as well as older dialects of the langauages, have extremely limited support that allow user programs to build with them, but without constraining the base system to being built with them. The exact balance continues to evolve to ensure the benefits of extra work remain greater than the burdens it imposes. The project used to support really old Intel compilers or old GCC versions, but we traded supporting those obsolete compilers for a carefully selected range of modern compilers. This section documents where we use different compilers, and the expectations around that.
3 months ago
User avatar None

String updated in the repository

Documentation / articles/committers-guide/_index — Spanish

Sometimes there are merge conflicts. That is OK. Do not panic. Instead, handle them the same as any other merge conflicts. To keep it simple, I will just describe a common issue that may arise. A pointer to a complete treatment can be found at the end of this section.
A veces hay conflictos al fusionar. Está bien. No te asustes. En lugar de eso, trátalos como cualquier otro conflicto de merge. Para hacerlo sencillo, simplemente describiré un problema común que puede aparecer. Se puede encontrar un enlace a un tratamiento más completo al final de esta sección.
3 months ago
User avatar None

Source string changed

Documentation / articles/committers-guide/_index — Spanish

Sometimes there are merge conflicts. That is OK. Do not panic. Instead, handle them the same as any other merge conflicts. To keep it simple, I will just describe a common issue that may arise. A pointer to a more complete treatment can be found at the end of this section.
3 months ago
User avatar None

String updated in the repository

Documentation / articles/committers-guide/_index — Spanish

Tag signatures can be verified with `git verify-tag <tag name>`, or `git tag -v <tag name>`.
Las firmas de los tags se pueden verificar con `git verity-tag <tag name>`, o `git tag -v <tag name>`.
3 months ago
User avatar None

Source string changed

Documentation / articles/committers-guide/_index — Spanish

Tag signatures can be verified with `git veritfy-tag <tag name>`, or `git tag -v <tag name>`.
3 months ago
User avatar None

String updated in the repository

Documentation / articles/committers-guide/_index — Spanish

shows me moving the working tree to the `main` branch (a816...) and then updating from upstream (to 5ef0...). In this case, bad would be HEAD (or 5ef0bd68b515) and good would be a8163e165c5b. As you can see from the output, HEAD@{1} also often works, but isn't foolproof if you have done other things to your Git tree after updating, but before you discover the need to bisect.
me muestra moviendo el directorio de trabajo a la rama `main` (a816...) y después actualizando desde el origen (a 5ef0...). En esta caso, malo sería HEAD (o 5rf0bd68) y bueno sería a8163e165. Como puedes ver en la salida, HEAD@{1} también funciona, pero no es a prueba de fallos si has hecho otras cosas en tu árbol después de actualizar, pero antes de que descubrieras que tenías que hacer bisección.
3 months ago
User avatar None

Source string changed

Documentation / articles/committers-guide/_index — Spanish

shows me moving the working tree to the `main` branch (a816...) and then updating from upstream (to 5ef0...). In this case, bad would be HEAD (or 5ref0bd68b515) and good would be a8163e165c5b. As you can see from the output, HEAD@{1} also often works, but isn't foolproof if you have done other things to your Git tree after updating, but before you discover the need to bisect.
3 months ago
Browse all translation changes