diff options
Diffstat (limited to 'docs/_locale/es/contributing.pot')
| -rw-r--r-- | docs/_locale/es/contributing.pot | 44 |
1 files changed, 44 insertions, 0 deletions
diff --git a/docs/_locale/es/contributing.pot b/docs/_locale/es/contributing.pot index 07b516ff..cbea3424 100644 --- a/docs/_locale/es/contributing.pot +++ b/docs/_locale/es/contributing.pot @@ -207,6 +207,10 @@ msgstr "Malo: radio (a menos que se trate de la distancia entre el centro de un msgid "Beeing brave and running the latest rolling releases will sometimes trigger bugs due to corner cases we missed in our design. Those bugs should be filed via Phabricator_ but you can help us to narrow doen the issue. Login to your VyOS system and change into configuration mode by typing ``configure``. Now re-load your boot configuration by simply typing ``load`` followed by return." msgstr "Ser valiente y ejecutar los últimos lanzamientos continuos a veces desencadenará errores debido a los casos de esquina que pasamos por alto en nuestro diseño. Esos errores deben archivarse a través de Phabricator_ pero puede ayudarnos a reducir el problema. Inicie sesión en su sistema VyOS y cambie al modo de configuración escribiendo ``configure``. Ahora vuelva a cargar su configuración de arranque simplemente escribiendo ``cargar`` seguido de retorno." +#: ../../contributing/debugging.rst:160 +msgid "Being brave and running the latest rolling releases will sometimes trigger bugs due to corner cases we missed in our design. Those bugs should be filed via Phabricator_ but you can help us to narrow down the issue. Login to your VyOS system and change into configuration mode by typing ``configure``. Now re-load your boot configuration by simply typing ``load`` followed by return." +msgstr "Being brave and running the latest rolling releases will sometimes trigger bugs due to corner cases we missed in our design. Those bugs should be filed via Phabricator_ but you can help us to narrow down the issue. Login to your VyOS system and change into configuration mode by typing ``configure``. Now re-load your boot configuration by simply typing ``load`` followed by return." + #: ../../contributing/debugging.rst:170 msgid "Boot Timing" msgstr "Temporización de arranque" @@ -884,6 +888,10 @@ msgid "Our StrongSWAN build differs from the upstream:" msgstr "Nuestra construcción StrongSWAN difiere de la anterior:" #: ../../contributing/testing.rst:20 +msgid "Our `VyOS CI`_ system is based on Jenkins and builds all our required packages for VyOS 1.2 to 1.4. In addition to the package build, there is the vyos-build Job which builds and tests the VyOS ISO image which is published after a successful test drive." +msgstr "Our `VyOS CI`_ system is based on Jenkins and builds all our required packages for VyOS 1.2 to 1.4. In addition to the package build, there is the vyos-build Job which builds and tests the VyOS ISO image which is published after a successful test drive." + +#: ../../contributing/testing.rst:20 msgid "Our `VyOS CI`_ system is based on Jenkins and builds all our required packages for VyOS 1.2 to 1.4. In addition to the package build, there is the vyos-build Job which builds and tests the VyOS ISO image which is published after a successfull test drive." msgstr "Nuestro sistema `VyOS CI`_ se basa en Jenkins y crea todos nuestros paquetes necesarios para VyOS 1.2 a 1.4. Además de la compilación del paquete, existe el trabajo vyos-build que compila y prueba la imagen ISO de VyOS que se publica después de una prueba de manejo exitosa." @@ -924,6 +932,10 @@ msgstr "Envíe sus parches utilizando la conocida solicitud de extracción de Gi msgid "Please use the following template as good starting point when developing new modules or even rewrite a whole bunch of code in the new style XML/Pyhon interface." msgstr "Utilice la siguiente plantilla como un buen punto de partida cuando desarrolle nuevos módulos o incluso reescriba un montón de código en el nuevo estilo de interfaz XML/Pyhon." +#: ../../contributing/development.rst:254 +msgid "Please use the following template as good starting point when developing new modules or even rewrite a whole bunch of code in the new style XML/Python interface." +msgstr "Please use the following template as good starting point when developing new modules or even rewrite a whole bunch of code in the new style XML/Python interface." + #: ../../contributing/testing.rst:104 msgid "Port description" msgstr "Descripción del puerto" @@ -1017,6 +1029,10 @@ msgstr "Smoketests ejecuta comandos predefinidos de la CLI de VyOS y verifica si msgid "So if you plan to build your own custom ISO image and wan't to make use of our smoketests, ensure that you have the `vyos-1x-smoketest` package installed." msgstr "Entonces, si planea crear su propia imagen ISO personalizada y no quiere utilizar nuestras pruebas de humo, asegúrese de tener instalado el paquete `vyos-1x-smoketest`." +#: ../../contributing/testing.rst:45 +msgid "So if you plan to build your own custom ISO image and want to make use of our smoketests, ensure that you have the `vyos-1x-smoketest` package installed." +msgstr "So if you plan to build your own custom ISO image and want to make use of our smoketests, ensure that you have the `vyos-1x-smoketest` package installed." + #: ../../contributing/build-vyos.rst:202 msgid "Some VyOS packages (namely vyos-1x) come with build-time tests which verify some of the internal library calls that they work as expected. Those tests are carried out through the Python Unittest module. If you want to build the ``vyos-1x`` package (which is our main development package) you need to start your Docker container using the following argument: ``--sysctl net.ipv6.conf.lo.disable_ipv6=0``, otherwise those tests will fail." msgstr "Algunos paquetes de VyOS (a saber, vyos-1x) vienen con pruebas de tiempo de compilación que verifican que algunas de las llamadas de la biblioteca interna funcionan como se esperaba. Estas pruebas se realizan a través del módulo Unittest de Python. Si desea compilar el paquete ``vyos-1x`` (que es nuestro paquete de desarrollo principal), debe iniciar su contenedor Docker con el siguiente argumento: ``--sysctl net.ipv6.conf.lo.disable_ipv6=0 ``, de lo contrario esas pruebas fallarán." @@ -1198,6 +1214,10 @@ msgid "The package ends up in deb_dist dir." msgstr "El paquete termina en el directorio deb_dist." #: ../../contributing/debugging.rst:148 +msgid "The reason is that the configuration migration backend is rewritten and uses a new form of \"magic string\" which is applied on demand when real config migration is run on boot. When running individual migrators for testing, you need to convert the \"magic string\" on your own by:" +msgstr "The reason is that the configuration migration backend is rewritten and uses a new form of \"magic string\" which is applied on demand when real config migration is run on boot. When running individual migrators for testing, you need to convert the \"magic string\" on your own by:" + +#: ../../contributing/debugging.rst:148 msgid "The reason is that the configuration migration backend is rewritten and uses a new form of \"magic string\" which is applied on demand when real config migration is run on boot. When runnint individual migrators for testing, you need to convert the \"magic string\" on your own by:" msgstr "La razón es que el backend de migración de configuración se reescribe y usa una nueva forma de "cadena mágica" que se aplica a pedido cuando se ejecuta la migración de configuración real en el arranque. Cuando no ejecuta migradores individuales para realizar pruebas, debe convertir la "cadena mágica" por su cuenta:" @@ -1314,10 +1334,18 @@ msgid "To debug issues in priorities or to see what's going on in the background msgstr "Para depurar problemas en las prioridades o para ver lo que sucede en segundo plano, puede usar el script ``/opt/vyatta/sbin/priority.pl`` que enumera el orden de ejecución de los scripts." #: ../../contributing/build-vyos.rst:373 +msgid "To debug the build process and gain additional information of what could be the root cause, you need to use `chroot` to change into the build directory. This is explained in the following step by step procedure:" +msgstr "To debug the build process and gain additional information of what could be the root cause, you need to use `chroot` to change into the build directory. This is explained in the following step by step procedure:" + +#: ../../contributing/build-vyos.rst:373 msgid "To debug the build process and gain additional information of what could be the root cause, you need to use `chroot` to change into the build directry. This is explained in the following step by step procedure:" msgstr "Para depurar el proceso de compilación y obtener información adicional sobre cuál podría ser la causa principal, debe usar `chroot` para cambiar al directorio de compilación. Esto se explica en el siguiente procedimiento paso a paso:" #: ../../contributing/debugging.rst:182 +msgid "To enable boot time graphing change the Kernel commandline and add the following string: ``init=/usr/lib/systemd/systemd-bootchart``" +msgstr "To enable boot time graphing change the Kernel commandline and add the following string: ``init=/usr/lib/systemd/systemd-bootchart``" + +#: ../../contributing/debugging.rst:182 msgid "To enable boot time graphing change the Kernel commandline and add the folowing string: ``init=/usr/lib/systemd/systemd-bootchart``" msgstr "Para habilitar la representación gráfica del tiempo de arranque, cambie la línea de comandos del Kernel y agregue la siguiente cadena: ``init=/usr/lib/systemd/systemd-bootchart``" @@ -1409,6 +1437,10 @@ msgstr "Plataformas de virtualización" msgid "VyOS CLI is all about priorities. Every CLI node has a corresponding ``node.def`` file and possibly an attached script that is executed when the node is present. Nodes can have a priority, and on system bootup - or any other ``commit`` to the config all scripts are executed from lowest to higest priority. This is good as this gives a deterministic behavior." msgstr "VyOS CLI tiene que ver con las prioridades. Cada nodo CLI tiene un archivo ``node.def`` correspondiente y posiblemente un script adjunto que se ejecuta cuando el nodo está presente. Los nodos pueden tener una prioridad, y en el arranque del sistema, o cualquier otro "commit" a la configuración, todos los scripts se ejecutan de menor a mayor prioridad. Esto es bueno ya que da un comportamiento determinista." +#: ../../contributing/debugging.rst:190 +msgid "VyOS CLI is all about priorities. Every CLI node has a corresponding ``node.def`` file and possibly an attached script that is executed when the node is present. Nodes can have a priority, and on system bootup - or any other ``commit`` to the config all scripts are executed from lowest to highest priority. This is good as this gives a deterministic behavior." +msgstr "VyOS CLI is all about priorities. Every CLI node has a corresponding ``node.def`` file and possibly an attached script that is executed when the node is present. Nodes can have a priority, and on system bootup - or any other ``commit`` to the config all scripts are executed from lowest to highest priority. This is good as this gives a deterministic behavior." + #: ../../contributing/build-vyos.rst:168 msgid "VyOS has switched to Debian (12) Bookworm in its ``current`` branch, Due to software version updates, it is recommended to use the official Docker Hub image to build VyOS ISO." msgstr "VyOS has switched to Debian (12) Bookworm in its ``current`` branch, Due to software version updates, it is recommended to use the official Docker Hub image to build VyOS ISO." @@ -1485,6 +1517,10 @@ msgstr "Cuando pueda verificar que en realidad se trata de un error, dedique alg msgid "When you are working on interface configuration and you also wan't to test if the Smoketests pass you would normally loose the remote SSH connection to your :abbr:`DUT (Device Under Test)`. To handle this issue, some of the interface based tests can be called with an environment variable beforehand to limit the number of interfaces used in the test. By default all interface e.g. all Ethernet interfaces are used." msgstr "Cuando está trabajando en la configuración de la interfaz y tampoco quiere probar si las pruebas de humo pasan, normalmente perdería la conexión SSH remota a su :abbr:`DUT (Dispositivo bajo prueba)`. Para manejar este problema, algunas de las pruebas basadas en interfaz se pueden llamar con una variable de entorno de antemano para limitar la cantidad de interfaces utilizadas en la prueba. De forma predeterminada, se utilizan todas las interfaces, por ejemplo, todas las interfaces Ethernet." +#: ../../contributing/testing.rst:109 +msgid "When you are working on interface configuration and you also want to test if the Smoketests pass you would normally loose the remote SSH connection to your :abbr:`DUT (Device Under Test)`. To handle this issue, some of the interface based tests can be called with an environment variable beforehand to limit the number of interfaces used in the test. By default all interface e.g. all Ethernet interfaces are used." +msgstr "When you are working on interface configuration and you also want to test if the Smoketests pass you would normally loose the remote SSH connection to your :abbr:`DUT (Device Under Test)`. To handle this issue, some of the interface based tests can be called with an environment variable beforehand to limit the number of interfaces used in the test. By default all interface e.g. all Ethernet interfaces are used." + #: ../../contributing/issues-features.rst:21 msgid "When you believe you have found a bug, it is always a good idea to verify the issue prior to opening a bug request." msgstr "Cuando crea que ha encontrado un error, siempre es una buena idea verificar el problema antes de abrir una solicitud de error." @@ -1550,6 +1586,10 @@ msgstr "Tiene sus propios paquetes `*.deb` de kernel personalizados en la carpet msgid "You shoudl now see a Python backtrace which will help us to handle the issue, please attach it to the Phabricator_ task." msgstr "Ahora debería ver un seguimiento de Python que nos ayudará a manejar el problema, adjúntelo a la tarea Phabricator_." +#: ../../contributing/debugging.rst:166 +msgid "You should now see a Python backtrace which will help us to handle the issue, please attach it to the Phabricator_ task." +msgstr "You should now see a Python backtrace which will help us to handle the issue, please attach it to the Phabricator_ task." + #: ../../contributing/development.rst:146 msgid "You then can proceed with cloning your fork or add a new remote to your local repository:" msgstr "Luego puede continuar con la clonación de su bifurcación o agregar un nuevo control remoto a su repositorio local:" @@ -1666,6 +1706,10 @@ msgstr "cometer:expresión:" msgid "contine execution using ``cont``" msgstr "contiene ejecución usando ``cont''" +#: ../../contributing/debugging.rst:128 +msgid "continue execution using ``cont``" +msgstr "continue execution using ``cont``" + #: ../../contributing/development.rst:675 msgid "default:" msgstr "por defecto:" |