1 files changed, 84 insertions, 6 deletions
diff --git a/tde-i18n-es/messages/tdepim/kmail.po b/tde-i18n-es/messages/tdepim/kmail.po
index 8e65661f87f..9bb5af433b8 100644
--- a/tde-i18n-es/messages/tdepim/kmail.po
+++ b/tde-i18n-es/messages/tdepim/kmail.po
@@ -15,7 +15,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: kmail\n"
-"POT-Creation-Date: 2022-04-06 20:16+0000\n"
+"POT-Creation-Date: 2022-07-19 20:15+0000\n"
 "PO-Revision-Date: 2008-03-10 13:44+0100\n"
 "Last-Translator: Eloy Cuadra <ecuadra@eloihr.net>\n"
 "Language-Team: Spanish <kde-l10n-es@kde.org>\n"
@@ -2408,12 +2408,13 @@ msgstr ""
 "este posible problema.</p></qt>"
 
 #: configuredialog.cpp:3767
+#, fuzzy
 msgid ""
 "<qt><h3>Message Disposition Notification Policy</h3><p>MDNs are a "
 "generalization of what is commonly called <b>read receipt</b>. The message "
 "author requests a disposition notification to be sent and the receiver's "
 "mail program generates a reply from which the author can learn what happened "
-"to his message. Common disposition types include <b>displayed</b> (i.e. "
+"to their message. Common disposition types include <b>displayed</b> (i.e. "
 "read), <b>deleted</b> and <b>dispatched</b> (e.g. forwarded).</p><p>The "
 "following options are available to control KMail's sending of MDNs:</"
 "p><ul><li><em>Ignore</em>: Ignores any request for disposition "
@@ -2423,7 +2424,7 @@ msgid ""
 "or ignoring them for others.</li><li><em>Deny</em>: Always sends a "
 "<b>denied</b> notification. This is only <em>slightly</em> better than "
 "always sending MDNs. The author will still know that the messages has been "
-"acted upon, he just cannot tell whether it was deleted or read etc.</"
+"acted upon, they just cannot tell whether it was deleted or read etc.</"
 "li><li><em>Always send</em>: Always sends the requested disposition "
 "notification. That means that the author of the message gets to know when "
 "the message was acted upon and, in addition, what happened to it (displayed, "
@@ -7709,15 +7710,16 @@ msgid "Generate free/&busy and activate alarms for:"
 msgstr "Generar libre/ocu&pado y activar las alarmas para:"
 
 #: kmfolderdia.cpp:539
+#, fuzzy
 msgid ""
 "This setting defines which users sharing this folder should get \"busy\" "
 "periods in their freebusy lists and should see the alarms for the events or "
 "tasks in this folder. The setting applies to Calendar and Task folders only "
 "(for tasks, this setting is only used for alarms).\n"
 "\n"
-"Example use cases: if the boss shares a folder with his secretary, only the "
-"boss should be marked as busy for his meetings, so he should select \"Admins"
-"\", since the secretary has no admin rights on the folder.\n"
+"Example use cases: if the boss shares a folder with their secretary, only "
+"the boss should be marked as busy for their meetings, so they should select "
+"\"Admins\", since the secretary has no admin rights on the folder.\n"
 "On the other hand if a working group shares a Calendar for group meetings, "
 "all readers of the folders should be marked as busy for meetings.\n"
 "A company-wide folder with optional events in it would use \"Nobody\" since "
@@ -15013,3 +15015,79 @@ msgstr ""
 
 #~ msgid "Op&en"
 #~ msgstr "A&brir"
+
+#~ msgid ""
+#~ "<qt><h3>Message Disposition Notification Policy</h3><p>MDNs are a "
+#~ "generalization of what is commonly called <b>read receipt</b>. The "
+#~ "message author requests a disposition notification to be sent and the "
+#~ "receiver's mail program generates a reply from which the author can learn "
+#~ "what happened to his message. Common disposition types include "
+#~ "<b>displayed</b> (i.e. read), <b>deleted</b> and <b>dispatched</b> (e.g. "
+#~ "forwarded).</p><p>The following options are available to control KMail's "
+#~ "sending of MDNs:</p><ul><li><em>Ignore</em>: Ignores any request for "
+#~ "disposition notifications. No MDN will ever be sent automatically "
+#~ "(recommended).</li><li><em>Ask</em>: Answers requests only after asking "
+#~ "the user for permission. This way, you can send MDNs for selected "
+#~ "messages while denying or ignoring them for others.</li><li><em>Deny</"
+#~ "em>: Always sends a <b>denied</b> notification. This is only "
+#~ "<em>slightly</em> better than always sending MDNs. The author will still "
+#~ "know that the messages has been acted upon, he just cannot tell whether "
+#~ "it was deleted or read etc.</li><li><em>Always send</em>: Always sends "
+#~ "the requested disposition notification. That means that the author of the "
+#~ "message gets to know when the message was acted upon and, in addition, "
+#~ "what happened to it (displayed, deleted, etc.). This option is strongly "
+#~ "discouraged, but since it makes much sense e.g. for customer relationship "
+#~ "management, it has been made available.</li></ul></qt>"
+#~ msgstr ""
+#~ "<qt><h3>Política sobre los acuses de recibo (MDN)</h3><p>La MDN es una "
+#~ "generalización de lo que comúnmente llamamos «acuse de recibo». El autor "
+#~ "del mensaje solicita una petición de acuse de recibo y el programa "
+#~ "receptor de correo genera una respuesta en la que el autor puede "
+#~ "averiguar qué ocurrió con su mensaje. Los tipos de notificación común "
+#~ "incluyen «mostrado» (por ejemplo, leído), «borrado» y «despachado» (por "
+#~ "ejemplo, reenviado).</p><p>Están disponibles las siguientes opciones para "
+#~ "controlar el envío de MDNs desde KMail:</p><ul><li><em>Ignorar</em>: "
+#~ "Ignora todas las peticiones de acuse de recibo. Ningún MDN se enviará "
+#~ "automáticamente (recomendado).</li><li><em>Preguntar</em>: Responde a las "
+#~ "peticiones después de pedir permiso al usuario. De esta forma, puede "
+#~ "enviar MDNs para los mensajes seleccionados y denegar o ignorar otros.</"
+#~ "li><li><em>Denegar</em>: Siempre envía una notificación <b>denegada</b>. "
+#~ "Esto es <em>algo</em> mejor que enviar siempre MDNs. El autor sabrá que "
+#~ "los mensajes se han recibido, pero no podrá decir si se han borrado o "
+#~ "leído, etc.</li><li><em>Enviar siempre</em>: Siempre envía el acuse de "
+#~ "recibo solicitado. Esto significa que el autor del mensaje sabrá que el "
+#~ "mensaje se ha recibido y qué ocurrió (se mostró, se borró, etc.). Esta "
+#~ "opción no es muy recomendable, pero tiene sentido, por ejemplo en la "
+#~ "gestión de relaciones con los clientes, por lo que está disponible.</li></"
+#~ "ul></qt>"
+
+#~ msgid ""
+#~ "This setting defines which users sharing this folder should get \"busy\" "
+#~ "periods in their freebusy lists and should see the alarms for the events "
+#~ "or tasks in this folder. The setting applies to Calendar and Task folders "
+#~ "only (for tasks, this setting is only used for alarms).\n"
+#~ "\n"
+#~ "Example use cases: if the boss shares a folder with his secretary, only "
+#~ "the boss should be marked as busy for his meetings, so he should select "
+#~ "\"Admins\", since the secretary has no admin rights on the folder.\n"
+#~ "On the other hand if a working group shares a Calendar for group "
+#~ "meetings, all readers of the folders should be marked as busy for "
+#~ "meetings.\n"
+#~ "A company-wide folder with optional events in it would use \"Nobody\" "
+#~ "since it is not known who will go to those events."
+#~ msgstr ""
+#~ "Esta opción define qué usuarios de los que comparten esta carpeta "
+#~ "debieran tener periodos en la lista de ocios y ocupaciones y debieran ver "
+#~ "las alarmas para las tareas de esta carpeta. Esta opción se aplica sólo a "
+#~ "las carpetas «Calendario» y «Tareas» (para las tareas, esta opción sólo "
+#~ "se emplea para las alarmas).\n"
+#~ "\n"
+#~ "Ejemplos de utilización: si el jefe comparte una carpeta con su "
+#~ "secretaria, sólo el jefe debería poder marcar como ocupado el tiempo para "
+#~ "sus reuniones, por lo que debería seleccionar «Admins», mientras que la "
+#~ "secretaria no debería tener permisos de administración sobre la carpeta.\n"
+#~ "Por otra parte, si un grupo de trabajo comparte un calendario de "
+#~ "reuniones, todos los lectores de las carpetas se deberían marcar como "
+#~ "ocupados en las reuniones.\n"
+#~ "Una carpeta de la compañía con eventos opcionales debería usar "
+#~ "«Cualquiera», ya que no se sabe quién irá a esos eventos."