Vista general

Sitio web del proyecto docs.freebsd.org/en
Licencia de la traducción BSD 2-Clause "Simplified" License
Proceso de traducción
  • Las traducciones pueden hacerse directamente.
  • Es posible sugerir traducciones.
  • Solo determinados usuarios pueden contribuir.
  • La traducción utiliza archivos bilingües.
Máscara de archivos documentation/content/*/articles/problem-reports/_index.po
Archivo de traducción Descargar documentation/content/id/articles/problem-reports/_index.po
Último cambio 10 de marzo de 2022 a las 07:51
Último autor Azrael JD

Estadísticas sobre las cadenas de texto

Porcentaje de cadenas Cadenas alojadas Porcentaje de palabras Palabras alojadas Porcentaje de caracteres Caracteres alojados
Total 114 4 385 27 115
Traducido 2% 3 1% 3 1% 23
Necesita edición 0% 0 0% 0 0% 0
De solo lectura 0% 0 0% 0 0% 0
Comprobaciones fallidas 0% 0 0% 0 0% 0
Cadenas con sugerencias 0% 0 0% 0 0% 0
Cadenas no traducidas 97% 111 99% 4 382 99% 27 092
Últimos 12 meses Anteriores

Actividad en los últimos 12 meses

0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios 0 cambios
Oct nov dic Ene Feb Mar Abr May Jun Jul Ago Sep

Números rápidos

4 385
Palabras alojadas
114
Cadenas alojadas
2%
Traducido
0
Contribuidores
y los 30 días previos

Tendencias en los últimos 30 días

—
Palabras alojadas
+100%
—
Cadenas alojadas
+100%
—
Traducido
+2%
—
Contribuidores
—
Avatar de usuario Ninguno

Cadenas nuevas por traducir

Documentation / articles/problem-reports/_index — Indonesio

Aparecieron en la traducción 10 cadenas nuevas para traducir. hace 2 años
Avatar de usuario Ninguno

Actualización de recurso

Documentation / articles/problem-reports/_index — Indonesio

Se modificó el archivo «documentation/content/id/articles/problem-reports/_index.po». hace 2 años
Avatar de usuario Ninguno

Cadena actualizada en el repositorio

Documentation / articles/problem-reports/_index — Indonesio

extref:{pr-guidelines}[Problem Report Handling Guidelines]: Valuable insight into how problem reports are handled by the FreeBSD developers.
 
hace 2 años
Avatar de usuario Ninguno

Cadena actualizada en el repositorio

Documentation / articles/problem-reports/_index — Indonesio

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.
 
hace 2 años
Avatar de usuario Ninguno

Cadena actualizada en el repositorio

Documentation / articles/problem-reports/_index — Indonesio

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.
 
hace 2 años
Avatar de usuario Ninguno

Cadena actualizada en el repositorio

Documentation / articles/problem-reports/_index — Indonesio

_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.
 
hace 2 años
Avatar de usuario Ninguno

Cadena actualizada en el repositorio

Documentation / articles/problem-reports/_index — Indonesio

_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.
 
hace 2 años
Avatar de usuario Ninguno

Cadena actualizada en el repositorio

Documentation / articles/problem-reports/_index — Indonesio

Also note that while including small patches in a PR is generally all right—particularly when they fix the problem described in the PR-large patches and especially new code which may require substantial review before committing should be placed on a web or ftp server, and the URL should be included in the PR instead of the patch. Patches in email tend to get mangled, and the larger the patch, the harder it will be for interested parties to unmangle it. Also, posting a patch on the web allows you to modify it without having to resubmit the entire patch in a followup to the original PR. Finally, large patches simply increase the size of the database, since closed PRs are not actually deleted but instead kept and simply marked as complete.
 
hace 2 años
Avatar de usuario Ninguno

Cadena actualizada en el repositorio

Documentation / articles/problem-reports/_index — Indonesio

For the base FreeBSD code, you should carefully study the contents of [.filename]#/usr/src/UPDATING# on your system or the latest version at https://cgit.freebsd.org/src/tree/UPDATING[https://cgit.freebsd.org/src/tree/UPDATING]. (This is vital information if you are upgrading from one version to another, especially if you are upgrading to the FreeBSD-CURRENT branch).
 
hace 2 años
Avatar de usuario Ninguno

Cadena actualizada en el repositorio

Documentation / articles/problem-reports/_index — Indonesio

The extref:{handbook}eresources/[mailing lists, eresources-mail]. If you are not subscribed, use https://www.FreeBSD.org/search/#mailinglists[the searchable archives] on the FreeBSD web site. If the problem has not been discussed on the lists, you might try posting a message about it and waiting a few days to see if someone can spot something that has been overlooked.
 
hace 2 años
Explorar todos los cambios de traducción