diff options
author | Automated System <gitea@mirror.git.trinitydesktop.org> | 2022-07-19 22:12:26 +0000 |
---|---|---|
committer | TDE Gitea <gitea@mirror.git.trinitydesktop.org> | 2022-07-19 22:12:26 +0000 |
commit | 22c2642990a53e9f6c1e92830cb61a8f4fb9f4cf (patch) | |
tree | 029fe49fbae29bba7976c557f88af479b13e89bc /tde-i18n-pl/messages/tdepim | |
parent | 20b641bea5493abcc245b4617cf5b0bf796e04fe (diff) | |
download | tde-i18n-22c2642990a53e9f6c1e92830cb61a8f4fb9f4cf.tar.gz tde-i18n-22c2642990a53e9f6c1e92830cb61a8f4fb9f4cf.zip |
Merge translation files from master branch.
Diffstat (limited to 'tde-i18n-pl/messages/tdepim')
-rw-r--r-- | tde-i18n-pl/messages/tdepim/kmail.po | 87 |
1 files changed, 81 insertions, 6 deletions
diff --git a/tde-i18n-pl/messages/tdepim/kmail.po b/tde-i18n-pl/messages/tdepim/kmail.po index 522f6976179..2e71792c9cd 100644 --- a/tde-i18n-pl/messages/tdepim/kmail.po +++ b/tde-i18n-pl/messages/tdepim/kmail.po @@ -10,7 +10,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: 2015-01-18 15:21+0100\n" "Last-Translator: mcbx\n" "Language-Team: <pl@li.org>\n" @@ -2447,12 +2447,13 @@ 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. " +"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 +2463,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 +7730,16 @@ 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" +"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 " @@ -14953,3 +14955,76 @@ msgstr "" #, fuzzy #~ msgid "&Options" #~ msgstr "Opcje wspólne" + +#~ 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>Polityka powiadamiania o losie wiadomości</h3> <p>Powiadamianie o " +#~ "losie wiadomości (Message Disposition Notification, MDN) to generalizacja " +#~ "tak zwanego <em>potwierdzenia odbioru</em>. Autor wiadomości żąda od " +#~ "programu pocztowego adresata powiadomienia, z którego autor może " +#~ "dowiedzieć się, co stało się z jego wiadomością. Typowe losy wiadomości " +#~ "to <em>przeczytana</em>, <em>usunięta</em>, <em>przesłana</em> (np. " +#~ "przekazana dalej)</p> <p>KMail oferuje następujące tryby obsługi MDN: " +#~ "<ul><li><em>Ignoruj</em>: wszystkie żądania powiadomienia będą " +#~ "ignorowane. Żadne powiadomienia nie będą wysyłane automatycznie " +#~ "(zalecane).</li><li><em>Pytaj</em>: powiadomienia będą wysyłane dopiero " +#~ "po potwierdzeniu przez użytkownika. Dzięki temu można będzie wysyłać MDN " +#~ "tylko dla wybranych wiadomości.</li><li><em>Odrzuć</em>: zawsze wysyłana " +#~ "będzie odpowiedź <em>Odrzucona</em>. Jest to tylko <em>nieco</em> lepsze " +#~ "od wysyłania zawsze odpowiedniego MDN. Autor będzie wiedział, że " +#~ "wiadomość została odebrana, nie będzie jedynie wiedział, co się z nią " +#~ "dalej stało.</li><li><em>Zawsze wysyłaj</em>: zawsze wysyłana będzie " +#~ "właściwa odpowiedź. Oznacza to, że autor będzie dokładnie wiedział, co " +#~ "stało się z jego wiadomością. Użycie tego trybu nie jest zalecane, ale " +#~ "ponieważ jest on przydatny w pewnych sytuacjach (takich jak system " +#~ "obsługi klientów), został on udostępniony</li></ul></p></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 "" +#~ "Ta opcja określa, którzy użytkownicy korzystający z tego folderu mają być " +#~ "oznaczani jako \"zajęci\" na ich liście zajęć, a także dostawać alarmy o " +#~ "zdarzeniach i zadaniach w tym folderze. Opcja ma zastosowanie jedynie do " +#~ "folderów typu Kalendarz i Zadanie (dla zadań istotne są jedynie alarmy).\n" +#~ "Przykład: jeśli szef dzieli folder z sekretarką, tylko szef powinien być " +#~ "oznaczany jako zajęty podczas swoich spotkań, zatem powinien wybrać opcję " +#~ "\"Administratorzy\", jako że sekretarka nie ma praw administratora.\n" +#~ "Przykład 2: jeśli grupa robocza korzysta z folderu Kalendarza do spotkań " +#~ "roboczych, wszyscy użytkownicy powinni być oznaczani jako zajęci podczas " +#~ "spotkań.\n" +#~ "Przykład 3: folder dostępny dla wszystkich pracowników firmy, informujący " +#~ "o dodatkowych zdarzeniach powinien mieć wybrane \"Nikt\", ponieważ nie " +#~ "wiadomo, kto będzie brał udział w tych zdarzeniach." |