Translation status

64 Strings 98%
Browse Translate
1,627 Words 96%

Strings status

64
All strings — 1,627 words Browse Translate Zen
63
Translated strings — 1,573 words Browse Translate Zen
1
Unfinished strings — 54 words Browse Translate Zen
1
Strings marked for edit — 54 words Browse Translate Zen
1
Unfinished strings without suggestions — 54 words Browse Translate Zen
2
Strings with any failing checks — 63 words Browse Translate Zen
1
Translated strings with any failing checks — 9 words Browse Translate Zen
10
Translated strings with dismissed checks — 85 words Browse Translate Zen
1
Failing check: Unchanged translation — 9 words Browse Translate Zen
1
Failing check: Has been translated — 54 words Browse Translate Zen
64
Strings without a label — 1,627 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. Fix this component to clear its alerts. BSD-2-Clause 0% 210 5,085 33,598 210 0 0 0
books/developers-handbook/policies/_index This component is linked to the Documentation/articles/bsdl-gpl repository. Fix this component to clear its alerts. 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. Fix this component to clear its alerts. 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,415 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,065 41,292 293 0 0 0
books/handbook/wayland/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 146 4,179 27,954 146 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/handbook/virtualization/_index This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 1% 705 12,688 90,017 705 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. Fix this component to clear its alerts. BSD-2-Clause 1% 269 6,803 40,769 268 1 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/*/books/porters-handbook/upgrading/_index.po
Translation file Download documentation/content/es/books/porters-handbook/upgrading/_index.po
Last change Feb. 13, 2025, 7:53 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 98% 63 96% 1,573 96% 9,934
Needs editing 1% 1 3% 54 3% 396
Read-only 0% 0 0% 0 0% 0
Failing checks 3% 2 3% 63 4% 477
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 0 changes 3 changes 0 changes 0 changes 0 changes 3 changes 6 changes 0 changes 0 changes 0 changes 0 changes 0 changes 4 changes 0 changes 0 changes 0 changes 3 changes 67 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

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

Trends of last 30 days

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

Committed changes

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

Committed changes 2 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.
2 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`).
2 months ago
User avatar None

New string to translate

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

1 new string to translate appeared in the translation. 4 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. 4 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` (<<git-diff>>) 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`).
4 months ago
User avatar None

Source string changed

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

Otherwise, either use the `git diff` method (<<git-diff>>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`).
4 months ago
User avatar None

New string to translate

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

1 new string to translate appeared in the translation. 7 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. 7 months ago
User avatar None

String updated in the repository

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

If upgrading the port requires special steps like changing configuration files or running a specific program, it must be documented in this file. The format of an entry in this file is:
Si la actualización del puerto requiere pasos especiales, como cambiar los archivos de configuración o ejecutar un programa específico, debe documentarse en este archivo. El formato de una entrada en este archivo es:
7 months ago
Browse all translation changes