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-nds/messages/tdepim/kmail.po | 88 ++++++++++++++++++++++++++++++++--- 1 file changed, 82 insertions(+), 6 deletions(-) (limited to 'tde-i18n-nds/messages/tdepim/kmail.po') diff --git a/tde-i18n-nds/messages/tdepim/kmail.po b/tde-i18n-nds/messages/tdepim/kmail.po index aa46494f82a..68c740905d4 100644 --- a/tde-i18n-nds/messages/tdepim/kmail.po +++ b/tde-i18n-nds/messages/tdepim/kmail.po @@ -6,7 +6,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-12 20:13+0200\n" "Last-Translator: Sönke Dibbern \n" "Language-Team: Low Saxon \n" @@ -2367,12 +2367,13 @@ msgstr "" "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:

  • Ignore: Ignores any request for disposition " @@ -2382,7 +2383,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.
  • 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, " @@ -7674,15 +7675,16 @@ 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" +"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 " @@ -15666,3 +15668,77 @@ msgstr "" #~ msgid "Attaching Image Failed" #~ msgstr "Bileggen vun en Bild fehlslaan" + +#~ 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: 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 "" +#~ "

    Behanneln vun Narichttostand-Bescheden (NTBen)

    De " +#~ "Schriever vun en Naricht kann Bescheden dor över anföddern, wat mit sien " +#~ "Naricht vör sik geiht; dat Nettpostprogramm vun den Adressaat stellt " +#~ "disse automaatsch op. Normaal Narichttostänn sünd wiest (d.h. " +#~ "leest), wegdaan un verarbeidt (t.B. wiederleddt).

    Du " +#~ "hest disse Optschonen för dat Behanneln vun NTB-Anföddern:

    • Övergahn: Övergeiht all Anfragen na all Bescheden. " +#~ "Bescheden warrt nienich automaatsch sendt (anraadt).
    • Fragen: Fraagt Di, wat op de Anföddern antert warrn schall. So kannst Du " +#~ "Bescheden för utsöchte Narichten sennen, wielt Du Anföddern bi anner " +#~ "Narichten övergahn oder afwiesen kannst.
    • Afwiesen: Sendt " +#~ "jümmers en &qout;Afwiest"-Bescheed. Dat is bloots en lütt beten beter as jümmers den födderten Bescheed to sennen. De Senner kann so " +#~ "sehn, dat Du mit de Naricht wat doon hest, he kann bloots nich seggen, " +#~ "wat Du ehr ankeken, wegdaan oder dor wat anners mit maakt hest.
    • Jümmers sennen: Sendt jümmers den anfödderten Bescheed. " +#~ "De Senner kriggt to weten, dat Du wat mit de Naricht daan hest, " +#~ "un ok, wat Du dormit daan hest (ankeken, wegdaan, usw.). Vun " +#~ "disse Optschoon warrt redig afraadt. Liekers hett se ehr Sinn in wiss " +#~ "Ümgeven, t.B. in Kunnenpleeg-Systemen, un is dorför hier verföögbor.
    " + +#~ 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 "" +#~ "Disse Optschoon leggt fast, för welk Brukers vun den deelten Orner " +#~ "\"Bunnen\"-Tieden un Begeefnis-/Opgaven-Alarms opstellt warrt. De " +#~ "Optschoon gellt bloots för Kalenner- un Opgaven-Ornern (bi Opgaven-Ornern " +#~ "gellt dat bloots för Alarms).\n" +#~ "\n" +#~ "Bispelen: Wenn de Baas vun en Bedrief en Orner mit sien Topleger/sche " +#~ "deelt, schull bloots de Baas wielt sien Möten bunnen wesen, he schull " +#~ "also \"Plegers\" utsöken, wiel sien Topleger/sche keen Plegerrechten för " +#~ "den Orner hett.\n" +#~ "Wenn aver en Arbeitkoppel en Kalenner för Koppelmöten deelt, schullen all " +#~ "Koppelmaten (\"Lesers\" vun de Ornern) wielt de Möten bunnen wesen.\n" +#~ "En bedriefwiet Orner mit Begeefnissen ahn Mitmaakplicht dor binnen schull " +#~ "\"Keeneen\" bruken, denn dat is nich kloor, woneem dorhen geiht." -- cgit v1.2.1