diff options
Diffstat (limited to 'tde-i18n-lt/messages/tdepim/kmail.po')
| -rw-r--r-- | tde-i18n-lt/messages/tdepim/kmail.po | 89 |
1 files changed, 83 insertions, 6 deletions
diff --git a/tde-i18n-lt/messages/tdepim/kmail.po b/tde-i18n-lt/messages/tdepim/kmail.po index 949598a002c..067366aea50 100644 --- a/tde-i18n-lt/messages/tdepim/kmail.po +++ b/tde-i18n-lt/messages/tdepim/kmail.po @@ -7,7 +7,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-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,13 @@ 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. " +"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 +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, " @@ -7746,15 +7747,16 @@ 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" +"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 " @@ -15732,3 +15734,78 @@ msgstr "" #~ "</p><p>Jei to neužtenka, galite bandyti atnaujinti IMAP talpyklę. Jei tai " #~ "darysite, prarasite visus vietoje atliktus pakeitimus šiam aplankui ir " #~ "visiems paaplankiams.</p>" + +#~ 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>Pranešimo apie laiško pristatymą taisyklė</h3><p>PLP (pranešimai " +#~ "apie laiško pristatymą) yra tai, kas paprastai vadinama<b>perskaitymo " +#~ "pranešimu</b>. Laiško autorius prašo pranešimo apie laiško pristatymą, ir " +#~ "gavėjo e. pašto programa sukuria atsakymą, iš kurio autorius gali " +#~ "sužinoti, kas nutiko jo laiškui. Paprastai laiško pristatymo pranešimai " +#~ "įvardinami tipais <b>parodytas</b> (t.y., perskaitytas), <b>ištrintas</b> " +#~ "ir <b>apdorotas</b> (pvz., persiųstas).</p><p>Tai, kaip KMail siunčia " +#~ "PLP, yra nustatoma tokiomis parinktimis:</p><ul><li><em>Ignoruoti</em>: " +#~ "ignoruoti visus PLP prašymus. Jokie PLP nebus siunčiami automatiškai " +#~ "(rekomenduojama).</li><li><em>Klausiti</em>: atsakyti į PLP prašymus " +#~ "prieš tai paklausus naudotojo leidimo. Tokiu būdu, galite siųsti PLP dėl " +#~ "pasirinktų laiškų, o kitus prašymus ignoruoti arba atmesti.</" +#~ "li><li><em>Atmesti</em>: visuomet siųsti pranešimą <b>atmesta</b>. Tai - " +#~ "tik <em>šiek - tiek</em> geriau nei visuomet siųsti PLP. Autorius vis " +#~ "tiek žinos, kad Jūs kažką su laišku darėte, jis tik nebus tikras, ar " +#~ "laiškas ištrintas, ar perskaitytas, ir pan.</li><li><em>Visuomet siųsti</" +#~ "em>: visuomet siųsti prašomą pranešimą apie laiško pristatymą. Tai " +#~ "reiškia, kad autorius visada žinos, ar Jūs kažką darėte su laišku, ir " +#~ "taip pat - ką darėte (perskaitėte, ištrynėte, ir t.t.). Šia parinktimi " +#~ "naudotis nerekomenduojama, tačiau, kadangi ji gali būti reikalinga, pvz., " +#~ "ryšių su klientais tikslais, ji yra palikta kaip galimybė.</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 "" +#~ "Šis nustatymas apibrėžia, kurie naudotojai, bendrai naudojantys šį " +#~ "aplanką, turėtų matyti „užimtus“ periodus užimtumo sąrašuose, bei gauti " +#~ "perspėjimus dėl įvykių ar darbų šiame aplanke. Nustatymas veikia tik " +#~ "Kalendoriaus ir Darbų aplankus (dėl darbų, šis nustatymas naudojamas tik " +#~ "perspėjimams).\n" +#~ "Pavyzdiniai naudojimo atvejai: jei viršininkas bendrai naudoja aplanką su " +#~ "savo sekretore, tik viršininkas turi būti nurodytas kaip „užimtas“ savo " +#~ "susitikimų metu, todėl jis turėtų pasirinkti „Administratoriai“, kadangi " +#~ "sekretorė neturi administravimo teisės konkrečiam aplankui.\n" +#~ "Iš kitos pusės, jei darbo grupė bendrai naudojasi Kalendoriumi grupės " +#~ "susitikimams, visi aplanko skaitytojai turi būti pažymėti užsiėmusiais " +#~ "susitikimų metu.\n" +#~ "Visos įmonės naudojamame aplanke su pasirenkamais įvykiais turi būti " +#~ "nustatyta „Niekas“, kadangi nėra žinoma, kas eis į konkrečius įvykius." |