1 files changed, 82 insertions, 6 deletions
diff --git a/tde-i18n-nb/messages/tdepim/kmail.po b/tde-i18n-nb/messages/tdepim/kmail.po
index 2e4c604b459..a28660679b9 100644
--- a/tde-i18n-nb/messages/tdepim/kmail.po
+++ b/tde-i18n-nb/messages/tdepim/kmail.po
@@ -14,7 +14,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: 2007-03-17 14:43+0100\n"
 "Last-Translator: Bjørn Steensrud <[email protected]>\n"
 "Language-Team: Norwegian Bokmål <[email protected]>\n"
@@ -2390,12 +2390,13 @@ 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. "
+"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 +2406,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 +7649,16 @@ 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"
+"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 "
@@ -15609,3 +15611,77 @@ msgstr ""
 
 #~ msgid "Insert command"
 #~ msgstr "Sett inn kommando"
+
+#~ msgid ""
+#~ "<qt><h3>Message Disposition Notification Policy</h3><p>MDNs are a "
+#~ "generalization of what is commonly called <b>read receipt</b>. The "
+#~ "message author requests a disposition notification to be sent and the "
+#~ "receiver's mail program generates a reply from which the author can learn "
+#~ "what happened to his message. Common disposition types include "
+#~ "<b>displayed</b> (i.e. read), <b>deleted</b> and <b>dispatched</b> (e.g. "
+#~ "forwarded).</p><p>The following options are available to control KMail's "
+#~ "sending of MDNs:</p><ul><li><em>Ignore</em>: Ignores any request for "
+#~ "disposition notifications. No MDN will ever be sent automatically "
+#~ "(recommended).</li><li><em>Ask</em>: Answers requests only after asking "
+#~ "the user for permission. This way, you can send MDNs for selected "
+#~ "messages while denying or ignoring them for others.</li><li><em>Deny</"
+#~ "em>: Always sends a <b>denied</b> notification. This is only "
+#~ "<em>slightly</em> better than always sending MDNs. The author will still "
+#~ "know that the messages has been acted upon, he just cannot tell whether "
+#~ "it was deleted or read etc.</li><li><em>Always send</em>: Always sends "
+#~ "the requested disposition notification. That means that the author of the "
+#~ "message gets to know when the message was acted upon and, in addition, "
+#~ "what happened to it (displayed, deleted, etc.). This option is strongly "
+#~ "discouraged, but since it makes much sense e.g. for customer relationship "
+#~ "management, it has been made available.</li></ul></qt>"
+#~ msgstr ""
+#~ "<qt> <h3>Håndtering av forespørsler om meldingskvittering</h3> "
+#~ "<p>Meldingskvitteringer (engelsk forkortelse MDN) er en utvidelse av det "
+#~ "som ofte kalles <b>lest-melding</b>. Den som sender meldingameldinga få "
+#~ "tilbakemelding fra systemet, og mottakerens e-postprogram lager et svar "
+#~ "som viser avsenderen hva som har hendt med meldinga. Vanlige "
+#~ "tilbakemeldinger er <b>vist</b> (dvs. lest), <b>slettet</b> og "
+#~ "<b>oversendt</b> (f.eks. videresendt). </p> <p>For å styre sending av "
+#~ "meldingskvitteringer i KMail har du disse valgene:</p> <ul> "
+#~ "<li><em>Ignorer</em>: Ignorer alle forespørsler om meldingskvitteringer. "
+#~ "Ingen kvittering blir sendt automatisk (anbefales). </li> <li><em>Spør</"
+#~ "em>: Sender meldingskvittering bare etter at brukeren er blitt spurt om "
+#~ "det. På denne måten kan du sende kvittering for noen meldinger, mens du "
+#~ "avviser eller ignorerer andre.</li> <li><em>Avvis</em>: Sender alltid en "
+#~ "<b>avvist</b>-kvittering. Dette er bare <em>litt</em> bedre enn å alltid "
+#~ "sende kvitteringer. Avsender får fremdeles vite at meldinga er kommet "
+#~ "fram, men får ikke vite om den er lest eller slettet osv.</li> "
+#~ "<li><em>Send alltid</em>: Sender alltid kvitteringen når det spørres "
+#~ "etter det. Det betyr at avsenderen får vite når meldinga kom fram og hva "
+#~ "som har hendt med den (vist, slettet osv.). Dette valget frarådes sterkt, "
+#~ "men siden det er ønskelig for behandling av f.eks. kundeforhold. så er "
+#~ "det gjort tilgjengelig.</li></ul></qt>"
+
+#~ msgid ""
+#~ "This setting defines which users sharing this folder should get \"busy\" "
+#~ "periods in their freebusy lists and should see the alarms for the events "
+#~ "or tasks in this folder. The setting applies to Calendar and Task folders "
+#~ "only (for tasks, this setting is only used for alarms).\n"
+#~ "\n"
+#~ "Example use cases: if the boss shares a folder with his secretary, only "
+#~ "the boss should be marked as busy for his meetings, so he should select "
+#~ "\"Admins\", since the secretary has no admin rights on the folder.\n"
+#~ "On the other hand if a working group shares a Calendar for group "
+#~ "meetings, all readers of the folders should be marked as busy for "
+#~ "meetings.\n"
+#~ "A company-wide folder with optional events in it would use \"Nobody\" "
+#~ "since it is not known who will go to those events."
+#~ msgstr ""
+#~ "Dette valget angir hvilke av brukere som deler denne mappa som får se når "
+#~ "du er opptatt eller ledig. De vil få beskjed om hendelsene eller "
+#~ "oppgavene i denne mappa. Dette valget gjelder kun for Kalender og "
+#~ "oppgavemappene (for oppgaver er dette valget bare brukt for beskjeder).\n"
+#~ "\n"
+#~ "Mulige bruksfelt: Hvis sjefen deler en mappe med sekretæren sin skal bare "
+#~ "sjefen være markert som opptatt for dette møtet, så han burde velge "
+#~ "«Administratorer», siden sekretæren ikke har administrator-rettigheter "
+#~ "til mappa.\n"
+#~ "Men dersom en arbeidsgruppe deler en kalender for gruppemøter, vil alle "
+#~ "som kan lese mappa være markert som opptatt for møtene.\n"
+#~ "En mappe som hele selskapet bruker med valgfrie hendelser vil bruke "
+#~ "«Ingen» siden det ikke er kjent hvem som vil komme på disse hendelsene."