3 files changed, 102 insertions, 25 deletions
diff --git a/tde-i18n-lt/messages/tdegames/kgoldrunner.po b/tde-i18n-lt/messages/tdegames/kgoldrunner.po
index a66f7538d69..a215e6b59c9 100644
--- a/tde-i18n-lt/messages/tdegames/kgoldrunner.po
+++ b/tde-i18n-lt/messages/tdegames/kgoldrunner.po
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: kgoldrunner\n"
-"POT-Creation-Date: 2020-05-11 04:09+0200\n"
+"POT-Creation-Date: 2022-07-19 18:18+0000\n"
 "PO-Revision-Date: 2005-09-02 17:29+0300\n"
 "Last-Translator: Donatas Glodenis <dgvirtual@akl.lt>\n"
 "Language-Team: Lithuanian <kde-i18n-lt@kde.org>\n"
@@ -48,8 +48,8 @@ msgid ""
 "next level.  A hidden ladder will appear as you collect the last nugget.\n"
 "\n"
 "The hero (the green figure) is your deputy.  To collect the nuggets, just "
-"point the mouse where you want him to go.  At first gravity takes over and "
-"he falls ..."
+"point the mouse where you want the hero to go.  At first gravity takes over "
+"and the hero falls ..."
 msgstr ""
 
 #: data_messages.cpp:36
@@ -62,7 +62,7 @@ msgid ""
 "This is an exercise in moving around.  Follow the track of gold nuggets "
 "until the ladder pops up at the right.  The hero can only follow the mouse "
 "along simple paths (like _ | L or U), so be careful not to get too far ahead "
-"of him.\n"
+"of them.\n"
 "\n"
 "DANGER: Try not to fall off the ladder or bar into the concrete pit at the "
 "bottom right.  If you do get trapped there, the only way out is to kill the "
@@ -77,8 +77,8 @@ msgstr ""
 msgid ""
 "Now you have to dig to get the gold!  Just use the left and right mouse "
 "buttons to dig left or right of the hero's position.  The hero can then jump "
-"into and through the hole he has dug.  He can also dig several holes in a "
-"row and run sideways through the dug holes.  Be careful though.  After a "
+"into and through the hole they have dug.  They can also dig several holes in "
+"a row and run sideways through the dug holes.  Be careful though.  After a "
 "while the holes close up and you can get trapped and killed.\n"
 "\n"
 "In the third box down, you have to dig two holes, jump in and quickly dig "
@@ -103,14 +103,14 @@ msgid ""
 "You can handle enemies by running away, digging a hole or luring them into "
 "part of the playing area where they get stranded.\n"
 "\n"
-"If an enemy falls into a hole, he gives up any gold he is carrying, then "
-"gets stuck in the hole for a time and climbs out.  If the hole closes while "
-"he is in it, he dies and reappears somewhere else on the screen.  You can "
+"If an enemy falls into a hole, they give up any gold they are carrying, then "
+"get stuck in the hole for a time and climb out.  If the hole closes while "
+"they are in it, they die and reappear somewhere else on the screen.  You can "
 "deliberately kill enemies by digging several holes in a row.\n"
 "\n"
 "More importantly, you can run over an enemy's head.  You must do that right "
-"at the start of this level.  Dig a hole, trap the enemy, wait for him to "
-"fall all the way in, then run over him, with the other enemy in hot "
+"at the start of this level.  Dig a hole, trap the enemy, wait for them to "
+"fall all the way in, then run over them, with the other enemy in hot "
 "pursuit..."
 msgstr ""
 
@@ -160,9 +160,9 @@ msgid ""
 "There's nowhere to dig, so you must dodge the enemies and avoid falling to "
 "the concrete at the wrong time.  Try to keep the enemies together.\n"
 "\n"
-"If an enemy has a gold outline, he is holding a nugget.  He might drop it as "
-"he runs over the concrete or maybe at the top of a ladder ...... patience, "
-"patience !!"
+"If an enemy has a gold outline, they are holding a nugget.  They might drop "
+"it as they run over the concrete or maybe at the top of a ladder ...... "
+"patience, patience !!"
 msgstr ""
 
 #: data_messages.cpp:89
@@ -187,9 +187,9 @@ msgid ""
 "It is best not to kill the enemy.  Try it and you will find out why ... Heh, "
 "heh, heh !! ... ;-)\n"
 "\n"
-"If you do kill him unintentionally, before you have collected the gold at "
+"If you do kill them unintentionally, before you have collected the gold at "
 "the top left, you can still finish the level by digging away the side of the "
-"pit he is in."
+"pit they are in."
 msgstr ""
 
 #: data_messages.cpp:103
diff --git a/tde-i18n-lt/messages/tdemultimedia/audiocd_encoder_vorbis.po b/tde-i18n-lt/messages/tdemultimedia/audiocd_encoder_vorbis.po
index d41493abdd5..c89df6a73fe 100644
--- a/tde-i18n-lt/messages/tdemultimedia/audiocd_encoder_vorbis.po
+++ b/tde-i18n-lt/messages/tdemultimedia/audiocd_encoder_vorbis.po
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: audiocd_encoder_vorbis\n"
-"POT-Creation-Date: 2020-05-11 04:03+0200\n"
+"POT-Creation-Date: 2022-07-19 18:16+0000\n"
 "PO-Revision-Date: 2005-09-02 17:29+0300\n"
 "Last-Translator: Donatas Glodenis <dgvirtual@akl.lt>\n"
 "Language-Team: Lithuanian <kde-i18n-lt@kde.org>\n"
@@ -208,7 +208,7 @@ msgstr ""
 #, no-c-format
 msgid ""
 "Add a description of the song to the file header. This makes it easy for the "
-"user to get advanced song information shown by his media player. You can get "
-"this information automatically via the Internet. Look at the <i>\"CDDB "
+"user to get advanced song information shown by their media player. You can "
+"get this information automatically via the Internet. Look at the <i>\"CDDB "
 "Retrieval\"</i> control module for details."
 msgstr ""
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."