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 Sept. 9, 2023, 9:39 p.m.
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 114 4,385 27,115
Translated 91% 104 83% 3,674 83% 22,604
Needs editing 8% 10 16% 711 16% 4,511
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

2 changes 0 changes 0 changes 0 changes 0 changes 22 changes 116 changes 0 changes 3 changes 0 changes 0 changes 0 changes 2 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

4,385
Hosted words
114
Hosted strings
91%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

New strings to translate

Documentation / articles/problem-reports/_index — Spanish

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

Resource update

Documentation / articles/problem-reports/_index — Spanish

The "documentation/content/es/articles/problem-reports/_index.po" file was changed. 10 months 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.
10 months ago
User avatar None

Source string changed

Documentation / articles/problem-reports/_index — Spanish

extref:{pr-guidelines}[Problem Report Handling Guidelines]-v: Valuable insight into how problem reports are handled by the FreeBSD developers.
10 months 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).
10 months ago
User avatar None

Source string changed

Documentation / articles/problem-reports/_index — Spanish

https://github.com/smileytechguy/reporting-bugs-effectively/blob/master/ENGLISH.md[How to Report Bugs Effectively]-a: An excellent essay by Simon G. Tatham on composing useful (non-FreeBSD-specific) problem reports.
10 months 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/IrcChannels[]. 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.
10 months ago
User avatar None

Source string changed

Documentation / articles/problem-reports/_index — Spanish

Join the relevant IRC channels. A partial listing is here: https://wiki.freebsd.org/IrcRC/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.
10 months 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.
10 months ago
User avatar None

Source string changed

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.
10 months ago
Browse all translation changes