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/*/books/porters-handbook/upgrading/_index.po
Translation file Download documentation/content/es/books/porters-handbook/upgrading/_index.po
Last change Aug. 23, 2025, 4:31 a.m.
Last author Juan David Jaramillo Ortiz

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 64 1,627 10,330
Translated 100% 64 100% 1,627 100% 10,330
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 1 1% 9 1% 81
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 0 changes 0 changes 0 changes 0 changes 4 changes 0 changes 0 changes 0 changes 3 changes 67 changes 0 changes 0 changes 0 changes 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 5 changes 6 changes 0 changes
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

Quick numbers

1,627
Hosted words
64
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Committed changes

Documentation / books/porters-handbook/upgrading/_index — Spanish

Committed changes a month ago
User avatar juanda097

Translation changed

Documentation / books/porters-handbook/upgrading/_index — Spanish

Upgrading a FreeBSD Port
Actualización dendo un port de FreeBSD
a month ago
User avatar None

Committed changes

Documentation / books/porters-handbook/upgrading/_index — Spanish

Committed changes 2 months ago
User avatar juanda097

Translation changed

Documentation / books/porters-handbook/upgrading/_index — Spanish

If the port is unmaintained, and you are actively using it, please consider volunteering to become its maintainer. FreeBSD has over 4000 ports without maintainers, and this is an area where more volunteers are always needed. (For a detailed description of the responsibilities of maintainers, refer to the section in the extref:{developers-handbook}[Developer's Handbook, POLICIES-MAINTAINER].)
Si el puerto no tiene un encargado y lo está utilizando activamente, considere ofrecerse como voluntario para convertirse en su encargado. FreeBSD tiene más de 4000 puertos sin encargados, y esta es un área donde siempre se necesitan más voluntarios. (Para una descripción detallada de las responsabilidades de los encargados, consulte la sección en el extref:{developers-handbook}[Manual del Desarrollador, POLICIES-MAINTAINER]).)
2 months ago
User avatar juanda097

Translation changed

Documentation / books/porters-handbook/upgrading/_index — Spanish

If the port is unmaintained, and you are actively using it, please consider volunteering to become its maintainer. FreeBSD has over 4000 ports without maintainers, and this is an area where more volunteers are always needed. (For a detailed description of the responsibilities of maintainers, refer to the section in the extref:{developers-handbook}[Developer's Handbook, POLICIES-MAINTAINER].)
Si el pouerto no está mantenido y usted lo usatiene un encargado y lo está utilizando activamente, por favor considere ofrecerse como voluntario para ser su mantenedor. convertirse en su encargado. FreeBSD tiene más de 4000 pouertos sin manteneencargadors, y éesta es un área en la qudonde siempre se necesitan más voluntarios. (Para una descripción detallada de las responsabilidades de los mantenedoreencargados, consulte la sección den el extref:{developers-handbook}[Manual del dDesarrollador, POLÍTICAICIES-MAINTAINER].).
2 months ago
User avatar None

Resource update

Documentation / books/porters-handbook/upgrading/_index — Spanish

The "documentation/content/es/books/porters-handbook/upgrading/_index.po" file was changed. 5 months ago
User avatar None

String updated in the repository

Documentation / books/porters-handbook/upgrading/_index — Spanish

Otherwise, either use the `git diff` method (crossref:upgrading[git-diff, Using Git to Make Patches]) or copy the contents of the port to an entire different directory and use the result of the recursive man:diff[1] output of the new and old ports directories (for example, if the modified port directory is called [.filename]#superedit# and the original is in our tree as [.filename]#superedit.bak#, then save the result of `diff -ruN superedit.bak superedit`). Either unified or context diff is fine, but port committers generally prefer unified diffs. Note the use of the `-N` option-this is the accepted way to force diff to properly deal with the case of new files being added or old files being deleted. Before sending us the diff, please examine the output to make sure all the changes make sense. (In particular, make sure to first clean out the work directories with `make clean`).
De lo contrario, utilice el método `git diff` (crossref:upgrading[git-diff, Usando Git para crear parches]) o copie el contenido del port a un directorio completamente diferente y utilice el resultado de la salida recursiva man:diff[1] de los directorios de ports nuevo y antiguo (por ejemplo, si el directorio del port modificado se llama [.filename]#superedit# y el original está en nuestro árbol como [.filename]#superedit.bak#, entonces guarde el resultado de `diff -ruN superedit.bak superedit`). Cualquier diff unificado o contextual está bien, pero los committers de port generalmente prefieren diffs unificados. Tenga en cuenta el uso de la opción `-N`: es la forma aceptada de forzar a diff a tratar adecuadamente el caso de que se añadan nuevos archivos o se eliminen archivos antiguos. Antes de enviarnos el diff, examine la salida para asegurarse de que todos los cambios tienen sentido. (En particular, asegúrese de limpiar primero los directorios de trabajo con `make clean`).
5 months ago
User avatar None

Committed changes

Documentation / books/porters-handbook/upgrading/_index — Spanish

Committed changes 8 months ago
User avatar juanda097

New translation

Documentation / books/porters-handbook/upgrading/_index — Spanish

https://git.FreeBSD.org/[git.FreeBSD.org] is the FreeBSD public Git server. See extref:{handbook}mirrors[FreeBSD Git Repository URL Table, git-url-table] for more information.
https://git.FreeBSD.org/[git.FreeBSD.org] es el servidor público de Git de FreeBSD. Consulte extref:{handbook}mirrors[Tabla de URLs del repositorio Git de FreeBSD, git-url-table] para más información.
8 months ago
User avatar juanda097

Translation changed

Documentation / books/porters-handbook/upgrading/_index — Spanish

Otherwise, either use the `git diff` method (crossref:upgrading[git-diff, Using Git to Make Patches]) or copy the contents of the port to an entire different directory and use the result of the recursive man:diff[1] output of the new and old ports directories (for example, if the modified port directory is called [.filename]#superedit# and the original is in our tree as [.filename]#superedit.bak#, then save the result of `diff -ruN superedit.bak superedit`). Either unified or context diff is fine, but port committers generally prefer unified diffs. Note the use of the `-N` option-this is the accepted way to force diff to properly deal with the case of new files being added or old files being deleted. Before sending us the diff, please examine the output to make sure all the changes make sense. (In particular, make sure to first clean out the work directories with `make clean`).
De lo contrario, utilice el método `git diff` (<<git-diff>>crossref:upgrading[git-diff, Usando Git para crear parches]) o copie el contenido del port a un directorio completamente diferente y utilice el resultado de la salida recursiva man:diff[1] de los directorios de ports nuevo y antiguo (por ejemplo, si el directorio del port modificado se llama [.filename]#superedit# y el original está en nuestro árbol como [.filename]#superedit.bak#, entonces guarde el resultado de `diff -ruN superedit.bak superedit`). Cualquier diff unificado o contextual está bien, pero los committers de port generalmente prefieren diffs unificados. Tenga en cuenta el uso de la opción `-N`: es la forma aceptada de forzar a diff a tratar adecuadamente el caso de que se añadan nuevos archivos o se eliminen archivos antiguos. Antes de enviarnos el diff, examine la salida para asegurarse de que todos los cambios tienen sentido. (En particular, asegúrese de limpiar primero los directorios de trabajo con `make clean`).
8 months ago
Browse all translation changes