Merge translation files from master branch.

1 files changed, 85 insertions, 6 deletions

diff --git a/tde-i18n-ms/messages/tdepim/kmail.po b/tde-i18n-ms/messages/tdepim/kmail.po
index 2315572b110..1581a3d6353 100644
--- a/tde-i18n-ms/messages/tdepim/kmail.po
+++ b/tde-i18n-ms/messages/tdepim/kmail.po
@@ -4,7 +4,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: Mimos\n"
-"POT-Creation-Date: 2022-04-06 20:16+0000\n"
+"POT-Creation-Date: 2022-07-19 20:15+0000\n"
 "PO-Revision-Date: 2005-11-23 18:09+0800\n"
 "Last-Translator: MIMOS <opensource@mimos.my>\n"
 "Language-Team: Malay <kedidiemas@yahoogroups.com>\n"
@@ -2375,12 +2375,13 @@ msgstr ""
 "mungkin berlaku.</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 "
@@ -2390,7 +2391,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, "
@@ -7659,15 +7660,16 @@ msgid "Generate free/&busy and activate alarms for:"
 msgstr "Janakan bebas/&sibuk dan aktifkan penggera untuk:"
 
 #: 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 "
@@ -16109,3 +16111,80 @@ msgstr ""
 
 #~ msgid "Extension"
 #~ msgstr "Sambungan"
+
+#~ 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>Dasar Pemberitahuan Penyusunan Mesej</h3><p>Secara umum MDN "
+#~ "dinamai <b>resit baca</b>. Penulis mesej meminta pemberitahuan "
+#~ "penyusunan  dihantar dan penerima program mel menjana jawapan supaya "
+#~ "penulis tahu apa yang telah berlaku kepada mesej tersebut. Jenis "
+#~ "penyusunan yang biasa termasuk <b>dipaparkan</b> (iaitu, dibaca), "
+#~ "<b>dihapuskan</b> dan <b>dikirim</b> (contoh, diperpanjangkan).</"
+#~ "p><p>Opsyen berikut disediakan untuk mengawal penghantaran MDN:</"
+#~ "p><ul><li><em>Abaikan</em>: Mengabaikan sebarang permintaan pemberitahuan "
+#~ "penyusunan . Secara automatik MDN tidak akan dihantar. (disyorkan).</"
+#~ "li><li><em>Tanya</em>: Jawapan kepada permintaan hanya diberikan selepas "
+#~ "mendapat izin daripada pengguna. Dengan cara ini, anda boleh menghantar "
+#~ "MDN untuk mesej yang dipilih, dalam masa yang sama menolak atau "
+#~ "mengabaikannya untuk pihak lain.</li><li><em>Tolak</em>: Sentiasa "
+#~ "menghantar pemberitahuan <b>tertolak</b>. Ini <em>sedikit</em> lebih baik "
+#~ "berbanding terlalu kerap menghantar MDN. Penulis masih tahu bahawa "
+#~ "mesejnya telah diambil tindakan, hanya tidak tahu sama ada mesej itu "
+#~ "dihapus, dibaca dll.</li><li><em>Hantar selalu</em>: Selalu menghantar "
+#~ "pemberitahuan penyusunan yang diminta. Ini bermakna, penulis mesej tahu "
+#~ "bila dan apa tindakan yang diambil ke atas mesejnya (dipaparkan, "
+#~ "dihapuskan, dll.). Anda sangat tidak digalakkan memilih opsyen ini, "
+#~ "tetapi oleh sebab ia berguna contohnya untuk pengurusan perhubungan "
+#~ "pelanggan, ia telah diwujudkan.</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 ""
+#~ "Seting ini mentakrif mana satu pengguna kongsi yang sepatutnya mendapat "
+#~ "tempoh \"sibuk\" dalam senarai sibuk bebas dan sepatutnya nampak penggera "
+#~ "untuk peristiwa atau tugasan dalam folder ini. Seting ini digunakan hanya "
+#~ "kepada folder Kalendar dan Tugasan  (untuk tugasan, seting ini hanya "
+#~ "digunakan untuk penggera).\n"
+#~ "\n"
+#~ "Contoh kes: jika bos berkongsi folder dengan setiausahanya, hanya bos "
+#~ "ditanda sebagai sibuk kerana mesyuaratnya, jadi bos sepatutnya memilih "
+#~ "\"Pentadbir\", kerana setiausaha tidak ada hak mentadbir ke atas folder.\n"
+#~ "Sebaliknya, jika satu pasukan kerja berkongsi satu Kalendar untuk "
+#~ "mesyuarat kumpulan, semua pembaca folder ditandakan sibuk kerana "
+#~ "mesyuarat.\n"
+#~ "Folder tahap syarikat yang mempunyai opsyen peristiwa menggunakan\"Tiada "
+#~ "sesiapa\" kerana tidak diketahui siapa yang akan pergi ke peristiwa "
+#~ "tersebut."