TDE
/
tde-i18n
mirror of https://mirror.git.trinitydesktop.org/gitea/TDE/tde-i18n
0
0
Fork 0
Code Issues Releases Wiki Activity

Update translation files

Browse Source 
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: tdepim/kmail
Translate-URL: https://mirror.git.trinitydesktop.org/weblate/projects/tdepim/kmail/
pull/38/head
TDE Weblate 2 years ago
parent 0f1d9746c0
commit 6f966b3645
67 changed files with 2091 additions and 402 deletions
Show Stats Download Patch File Download Diff File

12
tde-i18n-af/messages/tdepim/kmail.po
Unescape View File

@ -2,7 +2,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail 3_3_branch\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2004-11-10 16:33+0200\n"
"Last-Translator: Frikkie Thirion <frix@expertron.co.za>\n"
"Language-Team: AFRIKAANS <AF@lia.org.za>\n"
@ -2207,7 +2207,7 @@ msgid ""
"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 "
@ -2217,7 +2217,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, "
@ -6892,9 +6892,9 @@ msgid ""
"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 "

35
tde-i18n-ar/messages/tdepim/kmail.po
Unescape View File

@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2006-12-23 17:52+0100\n"
"Last-Translator: محمد سعد Mohamed SAAD <metehyi@free.fr>\n"
"Language-Team: Arabic <doc@arabeyes.org>\n"
@ -2353,12 +2353,35 @@ msgstr ""
"للمشاكل المستعصية.</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. 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>"
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 "
@ -2368,7 +2391,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, "
@ -7689,9 +7712,9 @@ msgid ""
"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 "

12
tde-i18n-az/messages/tdepim/kmail.po
Unescape View File

@ -3,7 +3,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2004-03-18 00:20+0200\n"
"Last-Translator: Mətin Əmirov <metin@karegen.com>\n"
"Language-Team: Azerbaijani <translation-team-az@lists.sourceforge.net>\n"
@ -2310,7 +2310,7 @@ msgid ""
"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 "
@ -2320,7 +2320,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, "
@ -7191,9 +7191,9 @@ msgid ""
"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 "

12
tde-i18n-be/messages/tdepim/kmail.po
Unescape View File

@ -11,7 +11,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-02-03 01:09+0100\n"
"Last-Translator: Siarhei Liantsevich <serzh.by@gmail.com>\n"
"Language-Team: Belarusian\n"
@ -2212,7 +2212,7 @@ msgid ""
"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 "
@ -2222,7 +2222,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, "
@ -6923,9 +6923,9 @@ msgid ""
"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 "

50
tde-i18n-bg/messages/tdepim/kmail.po
Unescape View File

@ -11,7 +11,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2019-12-22 13:51+0000\n"
"Last-Translator: Emanoil Kotsev <deloptes@gmail.com>\n"
"Language-Team: Bulgarian <https://mirror.git.trinitydesktop.org/weblate/"
@ -2399,12 +2399,35 @@ msgstr ""
"да сте наясно с този проблем.</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. 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>"
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 "
@ -2414,7 +2437,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, "
@ -7646,15 +7669,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Генериране на \"свободен/&зает\" и активиране на аларма за:"
#: 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"
#| "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."
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 "

12
tde-i18n-bn/messages/tdepim/kmail.po
Unescape View File

@ -3,7 +3,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2006-02-06 01:01-0600\n"
"Last-Translator: Deepayan Sarkar <deepayan@bengalinux.org>\n"
"Language-Team: Bengali <kde-translation@bengalinux.org>\n"
@ -2207,7 +2207,7 @@ msgid ""
"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 "
@ -2217,7 +2217,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, "
@ -6895,9 +6895,9 @@ msgid ""
"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 "

12
tde-i18n-br/messages/tdepim/kmail.po
Unescape View File

@ -5,7 +5,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail-1.1\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2005-01-23 05:51+0100\n"
"Last-Translator: Jañ-Mai Drapier <jan-mai.drapier@mail.dotcom.fr>\n"
"Language-Team: Brezhoneg <Suav.Icb@wanadoo.fr>\n"
@ -2253,7 +2253,7 @@ msgid ""
"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 "
@ -2263,7 +2263,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, "
@ -7056,9 +7056,9 @@ msgid ""
"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 "

35
tde-i18n-bs/messages/tdepim/kmail.po
Unescape View File

@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2004-12-12 16:40-0800\n"
"Last-Translator: Vedran Ljubovic <vljubovic@smartnet.ba>\n"
"Language-Team: Bosanski <lokal@linux.org.ba>\n"
@ -2419,12 +2419,35 @@ msgstr ""
"opciju, ali trebate biti svjesni mogućeg 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. 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>"
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 "
@ -2434,7 +2457,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, "
@ -7785,9 +7808,9 @@ msgid ""
"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 "

50
tde-i18n-ca/messages/tdepim/kmail.po
Unescape View File

@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-07-29 20:36+0200\n"
"Last-Translator: Josep Ma. Ferrer <txemaq@gmail.com>\n"
"Language-Team: Catalan <kde-i18n-ca@kde.org>\n"
@ -2405,12 +2405,35 @@ msgstr ""
"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. 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>"
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 "
@ -2420,7 +2443,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, "
@ -7722,15 +7745,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Genera lliure/&ocupat i activa les alarmes per a:"
#: 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"
#| "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."
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 "

50
tde-i18n-cs/messages/tdepim/kmail.po
Unescape View File

@ -15,7 +15,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2021-12-19 18:17+0000\n"
"Last-Translator: Slávek Banko <slavek.banko@axis.cz>\n"
"Language-Team: Czech <https://mirror.git.trinitydesktop.org/weblate/projects/"
@ -2386,12 +2386,35 @@ msgstr ""
"je třeba počítat s možnými problémy.</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. 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>"
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 "
@ -2401,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, "
@ -7661,15 +7684,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Zajistit &zaneprázdnění a nastavit alarm pro:"
#: 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"
#| "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."
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 "

35
tde-i18n-cy/messages/tdepim/kmail.po
Unescape View File

@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2004-02-25 13:47+0000\n"
"Last-Translator: KD at KGyfieithu <kyfieithu@dotmon.com>\n"
"Language-Team: Cymraeg <cy@li.org>\n"
@ -2388,12 +2388,35 @@ msgstr ""
"dewisiad yma, ond dylech chi fod yn ymwybodol o'r problem posibl.</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. 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>"
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 "
@ -2403,7 +2426,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, "
@ -7502,9 +7525,9 @@ msgid ""
"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 "

50
tde-i18n-da/messages/tdepim/kmail.po
Unescape View File

@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-08-14 11:28+0200\n"
"Last-Translator: Martin Schlander <mschlander@opensuse.org>\n"
"Language-Team: Danish <kde-i18n-doc@kde.org>\n"
@ -2374,12 +2374,35 @@ msgstr ""
"over det mulige problem.</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. 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>"
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 "
@ -2389,7 +2412,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, "
@ -7644,15 +7667,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Opret ledig-&optaget og aktivér alarm for:"
#: 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"
#| "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."
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 "

50
tde-i18n-de/messages/tdepim/kmail.po
Unescape View File

@ -17,7 +17,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2020-03-25 21:58+0000\n"
"Last-Translator: Chris <xchrisx@uber.space>\n"
"Language-Team: German <https://mirror.git.trinitydesktop.org/weblate/"
@ -2438,12 +2438,35 @@ msgstr ""
"sollten sich allerdings der möglichen Probleme bewusst sein.</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. 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>"
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 "
@ -2453,7 +2476,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, "
@ -7809,15 +7832,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Frei/&Beschäftigt erstellen und Erinnerungen aktivieren für:"
#: 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"
#| "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."
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 "

50
tde-i18n-el/messages/tdepim/kmail.po
Unescape View File

@ -13,7 +13,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-05-26 12:38+0300\n"
"Last-Translator: Spiros Georgaras <sng@hellug.gr>\n"
"Language-Team: Greek <i18ngr@lists.hellug.gr>\n"
@ -2412,12 +2412,35 @@ msgstr ""
"έχετε υπ` όψιν το πιθανό πρόβλημα.</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. 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>"
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 "
@ -2427,7 +2450,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, "
@ -7766,15 +7789,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Δημιουργία free/&busy και ενεργοποίηση ειδοποιήσεων για:"
#: 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"
#| "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."
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 "

50
tde-i18n-en_GB/messages/tdepim/kmail.po
Unescape View File

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2006-03-12 17:42+0000\n"
"Last-Translator: Malcolm Hunter <malcolm.hunter@gmx.co.uk>\n"
"Language-Team: British English <kde-en-gb@kde.me.uk>\n"
@ -2377,12 +2377,35 @@ msgstr ""
"should be aware of the possible problem.</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. 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>"
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 "
@ -2392,7 +2415,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, "
@ -7659,15 +7682,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Generate free/&busy and activate alarms for:"
#: 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"
#| "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."
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 "

35
tde-i18n-eo/messages/tdepim/kmail.po
Unescape View File

@ -10,7 +10,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2020-11-01 17:48+0000\n"
"Last-Translator: Thomas CORDONNIER <t_cordonnier@yahoo.fr>\n"
"Language-Team: Esperanto <https://mirror.git.trinitydesktop.org/weblate/"
@ -2346,12 +2346,35 @@ msgstr ""
"implikaĵoj.</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. 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>"
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 "
@ -2361,7 +2384,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, "
@ -7491,9 +7514,9 @@ msgid ""
"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 "

50
tde-i18n-es/messages/tdepim/kmail.po
Unescape View File

@ -15,7 +15,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18: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,35 @@ 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. 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>"
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 +2446,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 +7732,30 @@ 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"
#| "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."
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 "

50
tde-i18n-et/messages/tdepim/kmail.po
Unescape View File

@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-07-28 13:25+0300\n"
"Last-Translator: Marek Laane <bald@starman.ee>\n"
"Language-Team: Estonian <kde-et@linux.ee>\n"
@ -2359,12 +2359,35 @@ msgstr ""
"lülitada, kuid sa peaksid probleemist teadlik olema.</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. 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>"
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 "
@ -2374,7 +2397,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, "
@ -7611,15 +7634,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Va&ba/hõivatud info saadetakse ja häired aktiveeritakse kasutajatele:"
#: 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"
#| "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."
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 "

50
tde-i18n-eu/messages/tdepim/kmail.po
Unescape View File

@ -10,7 +10,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-01-23 00:46+0100\n"
"Last-Translator: Iñaki Larrañaga Murgoitio <dooteo@euskalgnu.org>\n"
"Language-Team: Basque <itzulpena@euskalgnu.org>\n"
@ -2376,12 +2376,35 @@ msgstr ""
"hau, baina kontuz ibili aipatutako arazoekin.</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. 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>"
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 "
@ -2391,7 +2414,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, "
@ -7641,15 +7664,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Sortu libre/&lanpetuta eta aktibatu alarmak honentzat:"
#: 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"
#| "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."
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 "

50
tde-i18n-fa/messages/tdepim/kmail.po
Unescape View File

@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-02-19 11:35+0330\n"
"Last-Translator: MaryamSadat Razavi <razavi@itland.ir>\n"
"Language-Team: Persian <kde-i18n-fa@kde.org>\n"
@ -2364,12 +2364,35 @@ msgstr ""
"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. 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>"
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 "
@ -2379,7 +2402,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, "
@ -7540,15 +7563,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "تولید هشدارهای آزاد/&اشغال و فعال برای:‌"
#: 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"
#| "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."
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 "

35
tde-i18n-fi/messages/tdepim/kmail.po
Unescape View File

@ -12,7 +12,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-10-30 21:58+0200\n"
"Last-Translator: Mikko Piippo <piippo@cc.helsinki.fi>\n"
"Language-Team: <fi@li.org>\n"
@ -2390,12 +2390,35 @@ msgstr ""
"käyttöön liittyvät ongelmat.</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. 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>"
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 "
@ -2405,7 +2428,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, "
@ -7660,9 +7683,9 @@ msgid ""
"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 "

50
tde-i18n-fr/messages/tdepim/kmail.po
Unescape View File

@ -19,7 +19,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-08-15 23:16+0200\n"
"Last-Translator: Pierre Buard <pierre.buard@gmail.com>\n"
"Language-Team: Français <kde-francophone@kde.org>\n"
@ -2434,12 +2434,35 @@ msgstr ""
"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. 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>"
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 "
@ -2449,7 +2472,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, "
@ -7811,15 +7834,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Générer des alarmes activées et libres / &occupées pour :"
#: 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"
#| "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."
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 "

50
tde-i18n-fy/messages/tdepim/kmail.po
Unescape View File

@ -12,7 +12,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-04-27 11:01+0100\n"
"Last-Translator: Berend Ytsma <berendy@gmail.com>\n"
"Language-Team: Frysk <kde-i18n-fry@kde.org>\n"
@ -2397,12 +2397,35 @@ msgstr ""
"dizze mooglike swierrichheid.</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. 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>"
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 "
@ -2412,7 +2435,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, "
@ -7678,15 +7701,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Frij/&beset-ynformaasje oanmeitsje en oantinken oansette foar:"
#: 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"
#| "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."
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 "

12
tde-i18n-ga/messages/tdepim/kmail.po
Unescape View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: tdepim/kmail.po\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2004-12-03 14:52-0500\n"
"Last-Translator: Kevin Patrick Scannell <scannell@SLU.EDU>\n"
"Language-Team: ga <LL@li.org>\n"
@ -2195,7 +2195,7 @@ msgid ""
"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 "
@ -2205,7 +2205,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, "
@ -6857,9 +6857,9 @@ msgid ""
"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 "

50
tde-i18n-gl/messages/tdepim/kmail.po
Unescape View File

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-01-14 18:36+0100\n"
"Last-Translator: Xabi G. Feal <xabigf@gmx.net>\n"
"Language-Team: Galician <trasno@ceu.fi.udc.es>\n"
@ -2389,12 +2389,35 @@ msgstr ""
"ser consciente dos posibeis problemas.</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. 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>"
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 "
@ -2404,7 +2427,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, "
@ -7688,15 +7711,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Xerar e activar alarmas de ocupado/cei&be 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"
#| "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."
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 "

12
tde-i18n-he/messages/tdepim/kmail.po
Unescape View File

@ -16,7 +16,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-01-24 20:05+0200\n"
"Last-Translator: Diego Iastrubni <elcuco@kde.org>\n"
"Language-Team: <he@li.org>\n"
@ -2289,7 +2289,7 @@ msgid ""
"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 "
@ -2299,7 +2299,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, "
@ -7089,9 +7089,9 @@ msgid ""
"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 "

12
tde-i18n-hi/messages/tdepim/kmail.po
Unescape View File

@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2004-08-24 13:36+0530\n"
"Last-Translator: Ravishankar Shrivastava <raviratlami@gmail.com>\n"
"Language-Team: Hindi <indlinux-hindi@lists.sourceforge.net>\n"
@ -2319,7 +2319,7 @@ msgid ""
"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 "
@ -2329,7 +2329,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, "
@ -7222,9 +7222,9 @@ msgid ""
"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 "

12
tde-i18n-hr/messages/tdepim/kmail.po
Unescape View File

@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail 0\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2004-04-20 13:25+CEST\n"
"Last-Translator: auto\n"
"Language-Team: Croatian <lokalizacija@linux.hr>\n"
@ -2393,7 +2393,7 @@ msgid ""
"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 "
@ -2403,7 +2403,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, "
@ -7390,9 +7390,9 @@ msgid ""
"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 "

50
tde-i18n-hu/messages/tdepim/kmail.po
Unescape View File

@ -3,7 +3,7 @@
msgid ""
msgstr ""
"Project-Id-Version: TDE 3.5\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-01-13 11:11+0100\n"
"Last-Translator: Tamas Szanto <tszanto@interware.hu>\n"
"Language-Team: Hungarian <kde-lista@sophia.jpte.hu>\n"
@ -2375,12 +2375,35 @@ msgstr ""
"el, hogy a lehetőség az említett módon kihasználható.</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. 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>"
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 "
@ -2390,7 +2413,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, "
@ -7596,15 +7619,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Foglaltsági a&datok és emlékeztetők generálása a következőknek:"
#: 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"
#| "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."
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 "

50
tde-i18n-is/messages/tdepim/kmail.po
Unescape View File

@ -14,7 +14,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-04-22 11:55+0000\n"
"Last-Translator: Sveinn í Felli <sveinki@nett.is>\n"
"Language-Team: icelandic <kde-isl@molar.is>\n"
@ -2386,12 +2386,35 @@ msgstr ""
"vakandi fyrir þessu hugsanlega vandamáli.</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. 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>"
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 "
@ -2401,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, "
@ -7629,15 +7652,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "&Búa til laus/upptekinn og virkja áminningar fyrir:"
#: 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"
#| "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."
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 "

50
tde-i18n-it/messages/tdepim/kmail.po
Unescape View File

@ -11,7 +11,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-08-14 11:27+0200\n"
"Last-Translator: Luigi Toscano <luigi.toscano@tiscali.it>\n"
"Language-Team: Italian <kde-i18n-it@kde.org>\n"
@ -2402,12 +2402,35 @@ msgstr ""
"dovresti fare molta attenzione.</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. 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>"
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 "
@ -2417,7 +2440,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, "
@ -7739,15 +7762,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Genera libero/occu&pato e attiva gli avvertimenti per:"
#: 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"
#| "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."
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 "

50
tde-i18n-ja/messages/tdepim/kmail.po
Unescape View File

@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-02-08 21:00+0900\n"
"Last-Translator: Yukiko Bando <ybando@k6.dion.ne.jp>\n"
"Language-Team: Japanese <Kdeveloper@kde.gr.jp>\n"
@ -2377,12 +2377,35 @@ msgstr ""
"意してください。</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. 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>"
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 "
@ -2392,7 +2415,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, "
@ -7550,15 +7573,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "動静 (予定の有無) を生成し、アラームを有効にする(&B):"
#: 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"
#| "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."
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 "

50
tde-i18n-kk/messages/tdepim/kmail.po
Unescape View File

@ -5,7 +5,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-04-27 10:35+0600\n"
"Last-Translator: Sairan Kikkarin <sairan@computer.org>\n"
"Language-Team: Kazakh\n"
@ -2348,12 +2348,35 @@ msgstr ""
"салдары есіңізде болсын.</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. 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>"
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 "
@ -2363,7 +2386,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, "
@ -7504,15 +7527,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "&Бос/бос емес деп белгілеп ескерту белсендіру:"
#: 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"
#| "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."
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 "

50
tde-i18n-km/messages/tdepim/kmail.po
Unescape View File

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-08-04 09:36+0700\n"
"Last-Translator: Khoem Sokhem <khoemsokhem@khmeros.info>\n"
"Language-Team: Khmer <en@li.org>\n"
@ -2330,12 +2330,35 @@ msgstr ""
"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. 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>"
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 "
@ -2345,7 +2368,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, "
@ -7407,15 +7430,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "បង្កើត​​ ទំនេ/រវល់ និង​ធ្វើ​ឲ្យការជូនដំណឹងសកម្មសម្រាប់ ៖"
#: 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"
#| "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."
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 "

50
tde-i18n-ko/messages/tdepim/kmail.po
Unescape View File

@ -17,7 +17,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-01-30 21:04+0900\n"
"Last-Translator: Youngbin Park <shrike@nate.com>\n"
"Language-Team: Korean <ko@li.org>\n"
@ -2370,12 +2370,35 @@ msgstr ""
"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. 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>"
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 "
@ -2385,7 +2408,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, "
@ -7574,15 +7597,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "free/busy 활성알람 생성 :"
#: 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"
#| "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."
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 "

50
tde-i18n-lt/messages/tdepim/kmail.po
Unescape View File

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-08-29 14:49+0300\n"
"Last-Translator: Donatas Glodenis <dgvirtual@akl.lt>\n"
"Language-Team: Lithuanian <kde-i18n-lt@kde.org>\n"
@ -2398,12 +2398,35 @@ msgstr ""
"laiško, tačiau turėtumėte žinoti apie potencialią problemą.</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. 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>"
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 "
@ -2413,7 +2436,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, "
@ -7746,15 +7769,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Kurti laisvas/&užsiėmęs veiklos perspėjimus:"
#: 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"
#| "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."
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 "

12
tde-i18n-lv/messages/tdepim/kmail.po
Unescape View File

@ -5,7 +5,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2002-03-23 20:42EEST\n"
"Last-Translator: Andris Maziks <andzha@latnet.lv>\n"
"Language-Team: Latvian\n"
@ -2329,7 +2329,7 @@ msgid ""
"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 "
@ -2339,7 +2339,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, "
@ -7270,9 +7270,9 @@ msgid ""
"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 "

35
tde-i18n-mk/messages/tdepim/kmail.po
Unescape View File

@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-04-19 00:53+0200\n"
"Last-Translator: Bozidar Proevski <bobibobi@freemail.com.mk>\n"
"Language-Team: Macedonian <mkde-l10n@lists.sourceforge.net>\n"
@ -2371,12 +2371,35 @@ msgstr ""
"но треба да сте свесни за можните проблеми.</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. 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>"
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 "
@ -2386,7 +2409,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, "
@ -7587,9 +7610,9 @@ msgid ""
"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 "

50
tde-i18n-ms/messages/tdepim/kmail.po
Unescape View File

@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: Mimos\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2005-11-23 18:09+0800\n"
"Last-Translator: MIMOS <opensource@mimos.my>\n"
"Language-Team: Malay <kedidiemas@yahoogroups.com>\n"
@ -2375,12 +2375,35 @@ msgstr ""
"mungkin berlaku.</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. 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>"
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 "
@ -2390,7 +2413,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, "
@ -7659,15 +7682,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Janakan bebas/&sibuk dan aktifkan penggera untuk:"
#: 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"
#| "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."
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 "

50
tde-i18n-nb/messages/tdepim/kmail.po
Unescape View File

@ -14,7 +14,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-03-17 14:43+0100\n"
"Last-Translator: Bjørn Steensrud <bjornst@powertech.no>\n"
"Language-Team: Norwegian Bokmål <i18n-nb@lister.ping.uio.no>\n"
@ -2390,12 +2390,35 @@ msgstr ""
"til.</p>"
#: 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. 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>"
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 "
@ -2405,7 +2428,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, "
@ -7648,15 +7671,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Lag ledig/&opptatt og skru på alarmer for:"
#: 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"
#| "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."
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 "

50
tde-i18n-nds/messages/tdepim/kmail.po
Unescape View File

@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-08-12 20:13+0200\n"
"Last-Translator: Sönke Dibbern <s_dibbern@web.de>\n"
"Language-Team: Low Saxon <kde-i18n-nds@kde.org>\n"
@ -2367,12 +2367,35 @@ msgstr ""
"Problem.</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. 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>"
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 "
@ -2382,7 +2405,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, "
@ -7674,15 +7697,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Free-/&Bunnen-Marken opstellen un Alarms anmaken för:"
#: 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"
#| "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."
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 "

50
tde-i18n-nl/messages/tdepim/kmail.po
Unescape View File

@ -13,7 +13,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-03-01 20:20+0100\n"
"Last-Translator: Bram Schoenmakers <bramschoenmakers@kde.nl>\n"
"Language-Team: Nederlands <kde-i18n-nl@kde.org>\n"
@ -2413,12 +2413,35 @@ msgstr ""
"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. 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>"
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 "
@ -2428,7 +2451,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, "
@ -7738,15 +7761,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Vrij/&bezet-informatie aanmaken en herinneringen aanzetten voor:"
#: 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"
#| "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."
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 "

50
tde-i18n-nn/messages/tdepim/kmail.po
Unescape View File

@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2006-07-23 19:03+0200\n"
"Last-Translator: Gaute Hvoslef Kvalnes <gaute@verdsveven.com>\n"
"Language-Team: Norwegian Nynorsk <i18n-nn@lister.ping.uio.no>\n"
@ -2380,12 +2380,35 @@ msgstr ""
"for problem det kan føra til.</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. 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>"
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 "
@ -2395,7 +2418,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, "
@ -7633,15 +7656,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Generer &ledig/oppteken og slå på alarmar for:"
#: 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"
#| "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."
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 "

12
tde-i18n-pa/messages/tdepim/kmail.po
Unescape View File

@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-05-07 12:45+0530\n"
"Last-Translator: A S Alam <aalam@users.sf.net>\n"
"Language-Team: Punjabi <punjabi-l10n@lists.sf.net>\n"
@ -2223,7 +2223,7 @@ msgid ""
"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 "
@ -2233,7 +2233,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, "
@ -6941,9 +6941,9 @@ msgid ""
"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 "

50
tde-i18n-pl/messages/tdepim/kmail.po
Unescape View File

@ -10,7 +10,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2015-01-18 15:21+0100\n"
"Last-Translator: mcbx\n"
"Language-Team: <pl@li.org>\n"
@ -2447,12 +2447,35 @@ msgstr ""
"</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. 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>"
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 "
@ -2462,7 +2485,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, "
@ -7729,15 +7752,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Generuj alarmy wolny/&zajęty dla:"
#: 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"
#| "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."
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 "

50
tde-i18n-pt/messages/tdepim/kmail.po
Unescape View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-07-10 22:33+0100\n"
"Last-Translator: Pedro Morais <morais@kde.org>\n"
"Language-Team: pt <kde-i18n-pt@kde.org>\n"
@ -2428,12 +2428,35 @@ msgstr ""
"mas deverá ficar a saber do possível 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. 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>"
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 "
@ -2443,7 +2466,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, "
@ -7756,15 +7779,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Gerar alarmes de livre/ocupado e a&ctivá-los 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"
#| "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."
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 "

50
tde-i18n-pt_BR/messages/tdepim/kmail.po
Unescape View File

@ -10,7 +10,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-11-27 17:21-0200\n"
"Last-Translator: Felipe Arruda <felipemiguel@gmail.com>\n"
"Language-Team: Brazilian Portuguese <kde-i18n-pt_br@mail.kde.org>\n"
@ -2412,12 +2412,35 @@ msgstr ""
"possíveis.</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. 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>"
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 "
@ -2427,7 +2450,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, "
@ -7741,15 +7764,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Gerar informações Livre/&Ocupado e ativar alarmes 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"
#| "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."
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 "

50
tde-i18n-ro/messages/tdepim/kmail.po
Unescape View File

@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2005-06-25 01:38+0300\n"
"Last-Translator: Claudiu Costin <claudiuc@kde.org>\n"
"Language-Team: Romanian <kde-i18n-ro@kde.org>\n"
@ -2406,12 +2406,35 @@ msgstr ""
"puteţi activa, dar trebuie să aveţi grijă la consecinţele posibile.</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. 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>"
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 "
@ -2421,7 +2444,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, "
@ -7711,15 +7734,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Generează liber/&ocupat şi activează alarmele pentru:"
#: 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"
#| "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."
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 "

50
tde-i18n-ru/messages/tdepim/kmail.po
Unescape View File

@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2022-02-12 17:01+0000\n"
"Last-Translator: Alexander Golubev <fatzer2@gmail.com>\n"
"Language-Team: Russian <https://mirror.git.trinitydesktop.org/weblate/"
@ -2376,12 +2376,35 @@ msgstr ""
"включите эту опцию, но помните о возможных проблемах.</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. 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>"
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 "
@ -2391,7 +2414,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, "
@ -7660,15 +7683,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Отметить время как &занятое и включить напоминания:"
#: 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"
#| "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."
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 "

12
tde-i18n-rw/messages/tdepim/kmail.po
Unescape View File

@ -15,7 +15,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail 3.4\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2005-05-25 18:51-0600\n"
"Last-Translator: Steve Murphy <murf@e-tools.com>\n"
"Language-Team: Kinyarwanda <translation-team-rw@lists.sourceforge.net>\n"
@ -2651,7 +2651,7 @@ msgid ""
"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 "
@ -2661,7 +2661,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, "
@ -8428,9 +8428,9 @@ msgid ""
"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 "

12
tde-i18n-se/messages/tdepim/kmail.po
Unescape View File

@ -10,7 +10,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-03-06 22:56+0100\n"
"Last-Translator: Børre Gaup <boerre@skolelinux.no>\n"
"Language-Team: Northern Sami <i18n-sme@lister.ping.uio.no>\n"
@ -2260,7 +2260,7 @@ msgid ""
"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 "
@ -2270,7 +2270,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, "
@ -7189,9 +7189,9 @@ msgid ""
"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 "

50
tde-i18n-sk/messages/tdepim/kmail.po
Unescape View File

@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-08-05 22:30+0200\n"
"Last-Translator: Richard Fric <Richard.Fric@kdemail.net>\n"
"Language-Team: Slovak <sk@li.org>\n"
@ -2374,12 +2374,35 @@ msgstr ""
"môžete ju povoliť, ale uvedomte si prípadné problémy.</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. 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>"
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 "
@ -2389,7 +2412,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, "
@ -7682,15 +7705,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Generovať voľný/o&bsadený a aktivačný alarm pre:"
#: 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"
#| "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."
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 "

35
tde-i18n-sl/messages/tdepim/kmail.po
Unescape View File

@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2007-09-15 02:43+0200\n"
"Last-Translator: Jure Repinc <jlp@holodeck1.com>\n"
"Language-Team: Slovenščina <lugos-slo@lugos.si>\n"
@ -2391,12 +2391,35 @@ msgstr ""
"se morate zavedati morebitnih težav povezanih s tem.</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. 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>"
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 "
@ -2406,7 +2429,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, "
@ -7793,9 +7816,9 @@ msgid ""
"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 "

50
tde-i18n-sr/messages/tdepim/kmail.po
Unescape View File

@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-08-16 13:31+0200\n"
"Last-Translator: Chusslove Illich <caslav.ilic@gmx.net>\n"
"Language-Team: Serbian <kde-i18n-sr@kde.org>\n"
@ -2376,12 +2376,35 @@ msgstr ""
"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. 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>"
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 "
@ -2391,7 +2414,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, "
@ -7694,15 +7717,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Направи слободно/&заузето и активирај аларме за:"
#: 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"
#| "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."
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 "

50
tde-i18n-sr@Latn/messages/tdepim/kmail.po
Unescape View File

@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-08-16 13:31+0200\n"
"Last-Translator: Chusslove Illich <caslav.ilic@gmx.net>\n"
"Language-Team: Serbian <kde-i18n-sr@kde.org>\n"
@ -2377,12 +2377,35 @@ msgstr ""
"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. 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>"
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 "
@ -2392,7 +2415,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, "
@ -7701,15 +7724,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Napravi slobodno/&zauzeto i aktiviraj alarme za:"
#: 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"
#| "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."
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 "

12
tde-i18n-ss/messages/tdepim/kmail.po
Unescape View File

@ -5,7 +5,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2002-11-10 00:41+0200\n"
"Last-Translator: Adam Mathebula <adam@translate.org.za>\n"
"Language-Team: Siswati <siswati@translate.org.za>\n"
@ -2166,7 +2166,7 @@ msgid ""
"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 "
@ -2176,7 +2176,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, "
@ -6743,9 +6743,9 @@ msgid ""
"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 "

50
tde-i18n-sv/messages/tdepim/kmail.po
Unescape View File

@ -11,7 +11,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-07-25 09:34+0200\n"
"Last-Translator: Stefan Asserhäll <stefan.asserhall@comhem.se>\n"
"Language-Team: Swedish <sv@li.org>\n"
@ -2378,12 +2378,35 @@ msgstr ""
"vara medveten om det möjliga problemet.</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. 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>"
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 "
@ -2393,7 +2416,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, "
@ -7646,15 +7669,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Skapa ledig-&upptagen och aktivera alarm för:"
#: 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"
#| "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."
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 "

35
tde-i18n-ta/messages/tdepim/kmail.po
Unescape View File

@ -21,7 +21,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2005-03-24 00:56-0800\n"
"Last-Translator: Tamil PC <tamilpc@ambalam.com>\n"
"Language-Team: <ta@li.org>\n"
@ -2360,12 +2360,35 @@ msgstr ""
"உயிரூட்டலாம். ஆனால், விளைவுகளை நன்குப் புரிந்து கொள்ளுங்கள்.</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. 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>"
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 "
@ -2375,7 +2398,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, "
@ -7551,9 +7574,9 @@ msgid ""
"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 "

35
tde-i18n-tg/messages/tdepim/kmail.po
Unescape View File

@ -13,7 +13,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2005-09-17 13:29+0500\n"
"Last-Translator: Victor Ibragimov <youth_opportunities@tajikngo.org>\n"
"Language-Team: Tajik\n"
@ -2442,12 +2442,35 @@ msgstr ""
"</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. 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>"
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 "
@ -2457,7 +2480,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, "
@ -7757,9 +7780,9 @@ msgid ""
"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 "

12
tde-i18n-th/messages/tdepim/kmail.po
Unescape View File

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2006-10-17 12:43+1000\n"
"Last-Translator: Sahachart Anukulkitch <drrider@gmail.com>\n"
"Language-Team: Thai <l10n@opentle.org>\n"
@ -2259,7 +2259,7 @@ msgid ""
"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 "
@ -2269,7 +2269,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, "
@ -7130,9 +7130,9 @@ msgid ""
"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 "

12
tde-i18n-tr/messages/tdepim/kmail.po
Unescape View File

@ -11,7 +11,7 @@ msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-02-29 16:01+0200\n"
"Last-Translator: Serdar Soytetir <tulliana@gmail.com>\n"
"Language-Team: Turkish <kde-i18n-doc@lists.kde.org>\n"
@ -2351,7 +2351,7 @@ msgid ""
"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 "
@ -2361,7 +2361,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, "
@ -7254,9 +7254,9 @@ msgid ""
"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 "

50
tde-i18n-uk/messages/tdepim/kmail.po
Unescape View File

@ -12,7 +12,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2022-04-08 06:23+0000\n"
"Last-Translator: Roman Savochenko <roman@oscada.org>\n"
"Language-Team: Ukrainian <https://mirror.git.trinitydesktop.org/weblate/"
@ -2397,12 +2397,35 @@ msgstr ""
"цей параметр, але не забувайте про можливі проблеми.</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. 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>"
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 "
@ -2412,7 +2435,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, "
@ -7743,15 +7766,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "Генерувати нагадування про події та вільний/за&йнятий час для:"
#: 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"
#| "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."
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 "

12
tde-i18n-uz/messages/tdepim/kmail.po
Unescape View File

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-04-14 22:22+0200\n"
"Last-Translator: Mashrab Kuvatov <kmashrab@uni-bremen.de>\n"
"Language-Team: Uzbek <floss-uz-l10n@googlegroups.com>\n"
@ -2232,7 +2232,7 @@ msgid ""
"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 "
@ -2242,7 +2242,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, "
@ -6928,9 +6928,9 @@ msgid ""
"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 "

12
tde-i18n-uz@cyrillic/messages/tdepim/kmail.po
Unescape View File

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-04-14 22:22+0200\n"
"Last-Translator: Mashrab Kuvatov <kmashrab@uni-bremen.de>\n"
"Language-Team: Uzbek <floss-uz-l10n@googlegroups.com>\n"
@ -2228,7 +2228,7 @@ msgid ""
"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 "
@ -2238,7 +2238,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, "
@ -6921,9 +6921,9 @@ msgid ""
"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 "

12
tde-i18n-wa/messages/tdepim/kmail.po
Unescape View File

@ -14,7 +14,7 @@ msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"Report-Msgid-Bugs-To: http://bugs.trinitydesktop.org\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2003-09-10 00:08+0200\n"
"Last-Translator: Lorint Hendschel <lorint.hendschel@skynet.be>\n"
"Language-Team: Walon <linux-wa@chanae.alphanet.ch>\n"
@ -2389,7 +2389,7 @@ msgid ""
"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 "
@ -2399,7 +2399,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, "
@ -7441,9 +7441,9 @@ msgid ""
"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 "

50
tde-i18n-zh_CN/messages/tdepim/kmail.po
Unescape View File

@ -11,7 +11,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail 3.5\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-01-29 14:12+0800\n"
"Last-Translator: Lie_Ex <lilith.ex@gmail.com>\n"
"Language-Team: zh_CN <kde-china@kde.org>\n"
@ -2291,12 +2291,35 @@ msgstr ""
"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. 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>"
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 "
@ -2306,7 +2329,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, "
@ -7259,15 +7282,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "生成忙/闲及激活提醒的用户(&B)："
#: 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"
#| "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."
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 "

50
tde-i18n-zh_TW/messages/tdepim/kmail.po
Unescape View File

@ -14,7 +14,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
"POT-Creation-Date: 2022-04-06 18:16+0000\n"
"POT-Creation-Date: 2022-07-19 18:15+0000\n"
"PO-Revision-Date: 2008-08-01 15:33+0800\n"
"Last-Translator: Frank Weng (a.k.a. Franklin) <franklin at goodhorse dot idv "
"dot tw>\n"
@ -2293,12 +2293,35 @@ msgstr ""
"您還是可以選擇將這個功能打開。</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. 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>"
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 "
@ -2308,7 +2331,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, "
@ -7207,15 +7230,30 @@ msgid "Generate free/&busy and activate alarms for:"
msgstr "設定忙碌或空閒標記並提醒(&B)："
#: 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"
#| "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."
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 "

Write Preview
Loading…
Cancel
Save