From 22c2642990a53e9f6c1e92830cb61a8f4fb9f4cf Mon Sep 17 00:00:00 2001
From: Automated System
Date: Tue, 19 Jul 2022 22:12:26 +0000
Subject: Merge translation files from master branch.
---
tde-i18n-da/messages/tdepim/kmail.po | 90 +++++++++++++++++++++++++++++++++---
1 file changed, 84 insertions(+), 6 deletions(-)
(limited to 'tde-i18n-da/messages/tdepim')
diff --git a/tde-i18n-da/messages/tdepim/kmail.po b/tde-i18n-da/messages/tdepim/kmail.po
index 55f99fad8df..14d36aa5eae 100644
--- a/tde-i18n-da/messages/tdepim/kmail.po
+++ b/tde-i18n-da/messages/tdepim/kmail.po
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kmail\n"
-"POT-Creation-Date: 2022-04-06 20:16+0000\n"
+"POT-Creation-Date: 2022-07-19 20:15+0000\n"
"PO-Revision-Date: 2008-08-14 11:28+0200\n"
"Last-Translator: Martin Schlander \n"
"Language-Team: Danish \n"
@@ -2374,12 +2374,13 @@ msgstr ""
"over det mulige problem.
"
#: configuredialog.cpp:3767
+#, fuzzy
msgid ""
"Message Disposition Notification Policy
MDNs are a "
"generalization of what is commonly called read receipt. 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 displayed (i.e. "
+"to their message. Common disposition types include displayed (i.e. "
"read), deleted and dispatched (e.g. forwarded).
The "
"following options are available to control KMail's sending of MDNs:"
"p>
- Ignore: Ignores any request for disposition "
@@ -2389,7 +2390,7 @@ msgid ""
"or ignoring them for others.
- Deny: Always sends a "
"denied notification. This is only slightly 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>
- Always send: 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 +7645,16 @@ 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"
+"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 "
@@ -14892,3 +14894,79 @@ msgstr ""
#~ msgid "Op&en"
#~ msgstr "Å&bn"
+
+#~ msgid ""
+#~ "
Message Disposition Notification Policy
MDNs are a "
+#~ "generalization of what is commonly called read receipt. 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 "
+#~ "displayed (i.e. read), deleted and dispatched (e.g. "
+#~ "forwarded).
The following options are available to control KMail's "
+#~ "sending of MDNs:
- Ignore: Ignores any request for "
+#~ "disposition notifications. No MDN will ever be sent automatically "
+#~ "(recommended).
- Ask: 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.
- Deny"
+#~ "em>: Always sends a denied notification. This is only "
+#~ "slightly 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.
- Always send: 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.
"
+#~ msgstr ""
+#~ "'Message Dispositon Notification'-politik
MDN'er er en "
+#~ "generalisering af det der almindeligvis kaldes læse-kvittering. "
+#~ "Brevets forfatter beder om besked at få at vide hvad der sker med brevet "
+#~ "og modtagerens e-mail-program genererer et svar ud fra hvilket "
+#~ "forfatteren kan lære hvad der skete med brevet. Almindelige typer svar "
+#~ "inkluderer vist (altså læst), slettet og behandlet "
+#~ "(altså f.eks. videresendt).
Følgende valgmuligheder er til stede "
+#~ "for at kontrollere KMail's udsending af MDN'er:
- Ignorér"
+#~ "em>: Ignorerer alle forespørgsler. Ingen MDN vil nogensinde blive sendt "
+#~ "automatisk (anbefalet).
- Spørg: Svarer kun på "
+#~ "forespørgsler efter at have bedt brugeren om tilladelse. På denne måde "
+#~ "kan du sende MDN'er til udvalgte breve mens du nægter eller ignorerer dem "
+#~ "for andre.
- Nægt: Sender altid en nægtet "
+#~ "meddelelse. Dette er kun lidt bedre end altid at sende MDN'er. "
+#~ "Forfatteren vil stadig vide at der er blevet reageret på brevet, han kan "
+#~ "blot ikke vide om det blev slettet eller læst.
- Send altid"
+#~ "em>: Sender altid den forespurgte meddelelse. Det betyder at forfatteren "
+#~ "af brevet får at vide hvornår der blev reageret på brevet, og derudover "
+#~ "hvad der skete med det (vist, slettet osv.). Vi advarer stærkt mod denne "
+#~ "mulighed, men da det sommetider giver mening f.eks. i forbindelse med "
+#~ "kundeforhold, er det blevet gjort muligt.
"
+
+#~ msgid ""
+#~ "This setting defines which users sharing this folder should get \"busy\" "
+#~ "periods in their freebusy lists and should see the alarms for the events "
+#~ "or tasks in this folder. The setting applies to Calendar and Task folders "
+#~ "only (for tasks, this setting is only used for alarms).\n"
+#~ "\n"
+#~ "Example use cases: if the boss shares a folder with his secretary, only "
+#~ "the boss should be marked as busy for his meetings, so he should select "
+#~ "\"Admins\", since the secretary has no admin rights on the folder.\n"
+#~ "On the other hand if a working group shares a Calendar for group "
+#~ "meetings, all readers of the folders should be marked as busy for "
+#~ "meetings.\n"
+#~ "A company-wide folder with optional events in it would use \"Nobody\" "
+#~ "since it is not known who will go to those events."
+#~ msgstr ""
+#~ "Denne indstilling angiver hvilke brugere som deler mappen skal få "
+#~ "\"optagne\" perioder i deres ledig-optagne lister og skal se alarmen for "
+#~ "begivenhederne eller opgaverne i mappen. Indstillingen gælder kun "
+#~ "kalender- og opgavemapper (for opgaver bruges indstillingen kun til "
+#~ "alarmer).\n"
+#~ "\n"
+#~ "Eksempel på brugertilfælde: Hvis chefen deler en mappe med sin sekretær, "
+#~ "skal kun chefen markeres som optaget for sine møder, så han skal vælge "
+#~ "\"Administrator\", eftersom sekretæren ikke har administratorsrettigheder "
+#~ "til mappen.\n"
+#~ "Hvis en arbejdsgruppe på den anden side deler en kalender for "
+#~ "gruppemøder, skal alle læsere af mappen markeres som optaget ved mødet.\n"
+#~ "En mappe for et helt foretagende som indeholder valgfrie aktiviteter "
+#~ "ville bruge \"Ingen\", eftersom det ikke er kendt hvem der vil deltage i "
+#~ "aktiviteterne."
--
cgit v1.2.1