notgne2/tuxpaint-pencil-sharpener
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

testing commit

Browse source
This commit is contained in:
Jacques Chion 2021-09-18 11:18:47 +02:00
parent cbf2b5b2fa
commit 2508f644fa
68 changed files with 6690 additions and 8033 deletions
Download patch file Download diff file Expand all files Collapse all files

30
docs/gl_ES.UTF-8/html/SIGNALS.html
View file

@ -2,7 +2,7 @@
<html>
<head>
<title>
Documentación de sinais de Tux Paint </title>
Tux Paint Signals Documentation </title>
<meta http-equiv="Content-Type"
content="text/html; charset=utf-8">
</head>
@ -17,40 +17,40 @@
width="205"
height="210"
alt="Tux Paint"><br>
versión 0.9.27<br/>
Documentación de sinais </h1>
version 0.9.27<br/>
Signals Documentation </h1>
<p>
Copyright &copy; 2019-2021 por varios colaboradores; vexa AUTHORS (AUTORES).<br>
Copyright &copy; 2019-2021 by various contributors; see AUTHORS.<br>
<a href="http://www.tuxpaint.org/">http://www.tuxpaint.org/</a>
</p>
<p>
9 de Marzo de 2021 </p>
March 9, 2021 </p>
</center>
<hr>
<p>
Tux Paint responde aos seguintes sinais (que poden enviarse ao proceso do programa a través de «<code>kill</code>» ou «<code>killall</code>», por exemplo). </p>
Tux Paint responds to the following signals (which can be sent to the program's process via `<code>kill</code>` or `<code>killall</code>`, for example). </p>
<dl>
<dt>
<code>SIGTERM</code>
(tamén, <b><code>[Ctrl]</code></b> + <b><code>[C]</code></b> dende un terminal executando «<code>tuxpaint</code>») </dt>
(also, <b><code>[Ctrl]</code></b> + <b><code>[C]</code></b> from a terminal running `<code>tuxpaint</code>`) </dt>
<dd>
<p>
Tux Paint responde coma se se premese o botón «Saír» ou se lle dixera ao contorno de escritorio que peche Tux Paint (por exemplo, premendo nun botón de peche da xanela ou premendo <b><code>[Alt]</code></b> + <b><code>[F4]</code></b> na maioría dos sistemas). </p>
Tux Paint responds as if the "Quit" button were pressed, or the desktop environment was told to close Tux Paint (e.g., by clicking a window close button, or pressing <b><code>[Alt]</code></b> + <b><code>[F4]</code></b> on most systems). </p>
<p>
Dende a interface principal, Tux Paint preguntará se quere ou non saír e (a non ser que sexa anulado pol a opción de gardado automático, p. ex.: «<code>--autosave</code>x) se quere gardar o debuxo actual (se non está gardado) , e se é así, e é unha versión modificada dun debuxo existente (a non ser que sexa anulado polas opcións de gardar sobre imaxes antigas ou gardar sempre imaxes novas; por exemplo, «<code>--saveover</code>« e «<code>--saveovernew</code>», respectivamente), se quere ou non sobreescribir o debuxo existente ou gardalo nun novo ficheiro. </p>
From the main interface, Tux Paint will prompt whether or not you wish to quit, and (unless overridden by the auto-save option, e.g. "<code>--autosave</code>") if you'd like to save the current drawing (if unsaved), and if so, and it's a modified version of an existing drawing (unless overridden by the options to save over old images, or always save new images; e.g. "<code>--saveover</code>" and "<code>--saveovernew</code>", respectively), whether or not to overwrite the existing drawing, or save to a new file. </p>
<p>
<b>Nota:</b> Dende outras partes da interface, o sinal interprétase actualmente como unha solicitude de retroceso (por exemplo, dende o diálogo «Novo» de volta á interface principal), coma se se premera un botón «Atrás» en Tux Paint ou se premera a tecla <b><code>[Esc]</code></b>. </p>
<b>Note:</b> From other parts of the interface, the signal is currently interpreted as a request to go back (e.g., from the "New" dialog back to the main interface), as if a "Back" button in Tux Paint were clicked, or the <b><code>[Esc]</code></b> was key pressed. </p>
<p>
Exemplo: <code>killall tuxpaint</code> </p>
Example: <code>killall tuxpaint</code> </p>
</dd>
<dt>
@ -59,16 +59,16 @@
<dd>
<p>
Tux Paint responde axustando a súa opción de gardar automaticamente (coma se fora publicada con «<code>--autosave</code>»), así como a opción de gardar sempre novas imaxes (coma se se publicase con «<code>--saveovernew</code>») no caso de recibir un sinal de <code>SIGUSR1</code> ou de gardar sempre sobre a imaxe existente (coma se se publicase con «<code>--saveover</code>») no caso de recibir <code>SIGUSR2</code>. Entón Tux Paint envíase a sí mesmo un sinal de <code>SIGTERM</code>, nun intento de saír. (Ver arriba.) </p>
Tux Paint responds by setting its auto-save option (as if it had been launched with "<code>--autosave</code>"), as well as either the option to always save new images (as if launched with "<code>--saveovernew</code>") in the case of receiving a <code>SIGUSR1</code> signal, or to always save over the existing image (as if launched with "<code>--saveover</code>") in the case of receiving <code>SIGUSR2</code>. Then Tux Paint sends itself a <code>SIGTERM</code> signal, in an attempt to quit. (See above.) </p>
<p>
Así, dende a interface principal, Tux Paint debería saír case de inmediato, sen facer preguntas. </p>
So, from the main interface, Tux Paint should quit almost immediately, with no questions asked. </p>
<p>
<b>Nota:</b> Dende outras partes da interface, por desgraza, Tux Paint retrocederá un nivel na interface. Polo tanto, neste momento pode que sexa necesario enviar este sinal a Tux Paint unhas cantas veces para que saia completamente. </p>
<b>Note:</b> From other parts of the interface, unfortunately, Tux Paint will go back one level in the interface. Therefore, at this time, it may be necessary to send this signal to Tux Paint a few times, for it to quit completely. </p>
<p>
Exemplo: <code>killall -s SIGUSR1 tuxpaint</code> </p>
Example: <code>killall -s SIGUSR1 tuxpaint</code> </p>
</dd>
</dl>
</body>