Translation status

122 Strings 71%
Browse Translate
4,531 Words 65%

Strings status

122
All strings — 4,531 words Browse Translate Zen
87
Translated strings — 2,952 words Browse Translate Zen
35
Unfinished strings — 1,579 words Browse Translate Zen
9
Untranslated strings — 138 words Browse Translate Zen
26
Strings marked for edit — 1,441 words Browse Translate Zen
35
Unfinished strings without suggestions — 1,579 words Browse Translate Zen
1
Strings with any failing checks — 23 words Browse Translate Zen
1
Translated strings with dismissed checks — 1 word Browse Translate Zen
1
Failing check: Consecutive duplicated words — 23 words Browse Translate Zen
122
Strings without a label — 4,531 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% 208 5,060 33,426 208 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,161 7,790 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% 548 19,875 137,408 548 1 0 0
books/developers-handbook/ipv6/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 293 6,085 41,416 293 0 0 0
books/developers-handbook/x86/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 927 21,323 120,708 927 1 0 0
books/porters-handbook/pkg-files/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 94 1,311 9,480 94 0 0 0
books/developers-handbook/sockets/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 269 6,806 40,777 268 1 0 0
books/handbook/firewalls/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 703 18,745 116,342 703 0 0 0
books/handbook/disks/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 644 14,166 89,878 642 3 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/problem-reports/_index.po
Translation file Download documentation/content/es/articles/problem-reports/_index.po
Last change Feb. 22, 2026, 4:31 p.m.
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 122 4,531 28,164
Translated 71% 87 65% 2,952 65% 18,524
Needs editing 21% 26 31% 1,441 31% 8,741
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 1 1% 23 1% 196
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 7% 9 3% 138 3% 899
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 12 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 0 changes 0 changes 0 changes 0 changes 71 changes
Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb

Quick numbers

4,531
Hosted words
122
Hosted strings
71%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+3%
Hosted words
+100%
+6%
Hosted strings
+100%
−28%
Translated
+100%
+100%
Contributors
—
User avatar None

New strings to translate

Documentation / articles/problem-reports/_index — Spanish

35 new strings to translate appeared to the translation. 6 days ago
User avatar None

Resource update

Documentation / articles/problem-reports/_index — Spanish

The "documentation/content/es/articles/problem-reports/_index.po" file was changed. 6 days ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Spanish

extref:{pr-guidelines}[Problem Report Handling Guidelines]: Valuable insight into how problem reports are handled by the FreeBSD developers.
extref:{pr-guidelines}[Problem Report Handling Guidelines]: Conocimiento valioso sobre cómo los desarrolladores de FreeBSD se encargan de los informes de problemas.
6 days ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Spanish

https://github.com/smileytechguy/reporting-bugs-effectively/blob/master/ENGLISH.md[How to Report Bugs Effectively]: An excellent essay by Simon G. Tatham on composing useful (non-FreeBSD-specific) problem reports.
https://github.com/smileytechguy/reporting-bugs-effectively/blob/master/ENGLISH.md[How to Report Bugs Effectively]: Un ensayo excelente de Simon G. Tatham sobre cómo componer informes de error útiles (no específico de FreeBSD).
6 days ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Spanish

Join the relevant IRC channels. A partial listing is here: https://wiki.freebsd.org/IRC/Channels[]. Inform the people in that channel about the problem report and ask for assistance. Be patient and stay in the channel after posting, so that the people from different time zones around the world have a chance to catch up.
Únete a los canales de IRC relevantes. Se puede encontrar un listado parcial aquí: https://wiki.freebsd.org/IRC/Channels[]. Informa a la gente en el canal acerca del informe del problema y pide ayuda. Sé paciente y mantente en el canal después de preguntar, de forma que la gente de diferentes zonas horarias alrededor del mundo tenga una oportunidad para ponerse al día.
6 days ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Spanish

If someone requests additional information from you, or you remember or discover something you did not mention in the initial report, please submit a follow up. The number one reason for a bug not getting fixed is lack of communication with the originator. The easiest way is to use the comment option on the individual Bugzilla PR's web page, which you can reach from the https://bugs.freebsd.org/bugzilla/query.cgi[Bugzilla PR search page].
Si alguien te solicita información adicional, o si recuerdas o descubres algo que no mencionaste en el informe inicial, por favor, envía un follow-up. La razón número uno para que un error no se arregle es la falta de comunicación con el usuario que creó el error. La forma más fácil es usar la opción de comentarios en la página web de cada PR, a la que puedes acceder desde la https://bugs.freebsd.org/bugzilla/query.cgi[página de búsqueda de PRs].
6 days ago
User avatar None

Source string changed

Documentation / articles/problem-reports/_index — Spanish

If someone requests additional information from you, or you remember or discover something you did not mention in the initial report, please submit a follow up. The number one reason for a bug not getting fixed is lack of communication with the originator. The easiest way is to use the comment option on the individual Bugzilla PR's web page, which you can reach from the https://bugs.freebsd.org/bugzilla/query.cgi[Bugzilla PR search page].
6 days ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Spanish

_Description:_ A complete and accurate description of the problem you are experiencing. Try to avoid speculating about the causes of the problem unless you are certain that you are on the right track, as it may mislead a developer into making incorrect assumptions about the problem. It should include the actions you need to take to reproduce the problem. If you know any workaround, include it. It not only helps other people with the same problem work around it, but may also help a developer understand the cause for the problem.
_Description:_ Una descripción completa y precisa del problema que estás experimentando. Intenta evitar especular sobre las posibles causas del problema a menos que se tenga la seguridad de que el camino descrito es el correcto, ya que puede inducir a un desarrollador a hacer suposiciones incorrectas sobre el problema. Debería incluir las acciones que hay que realizar para reproducir el problema. Si conoces alguna solución, inclúyela. No solo ayuda a otras personas con el mismo problema a solucionarlo, sino que también puede ayudar a un desarrollador a entender la causa del problema.
6 days ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Spanish

_Environment:_ This should describe, as accurately as possible, the environment in which the problem has been observed. This includes the operating system version, the version of the specific program or file that contains the problem, and any other relevant items such as system configuration, other installed software that influences the problem, etc.—quite simply everything a developer needs to know to reconstruct the environment in which the problem occurs.
_Environment:_ Esto debería describir, con la mayor precisión posible, el entorno en el que se ha observado el problema. Esto incluye la versión del sistema operativo, la versión del programa o archivo específico que contiene el problema y cualquier otro elemento relevante como la configuración del sistema, otro software instalado que influya en el problema, etc. —simplemente todo lo que un desarrollador necesita saber para reconstruir el entorno en el que se produce el problema.
6 days ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Spanish

If you really do not know where the problem lies (or the explanation does not seem to fit into the ones above), use the `misc` category. Before you do so, you may wish to ask for help first. You may be advised that one of the existing categories really is a better choice.
Si realmente no sabes dónde está el problema (o la explicación no parece adecuarse a ninguna de las de arriba), utiliza la categoría `misc`. Antes de hacerlo, podrías querer pedir ayuda primero en la {freebsd-questions}. Te podrían aconsejar que una de las categorías existentes es realmente una mejor opción.
6 days ago
Browse all translation changes