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-fa/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-fa/messages/tdepim')
-rw-r--r-- | tde-i18n-fa/messages/tdepim/kmail.po | 87 |
1 files changed, 81 insertions, 6 deletions
diff --git a/tde-i18n-fa/messages/tdepim/kmail.po b/tde-i18n-fa/messages/tdepim/kmail.po index a9967d14d07..99859b25675 100644 --- a/tde-i18n-fa/messages/tdepim/kmail.po +++ b/tde-i18n-fa/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: 2007-02-19 11:35+0330\n" "Last-Translator: MaryamSadat Razavi <razavi@itland.ir>\n" "Language-Team: Persian <kde-i18n-fa@kde.org>\n" @@ -2364,12 +2364,13 @@ msgstr "" "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 " @@ -2379,7 +2380,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, " @@ -7540,15 +7541,16 @@ msgid "Generate free/&busy and activate alarms for:" msgstr "تولید هشدارهای آزاد/&اشغال و فعال برای:" #: 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 " @@ -15373,3 +15375,76 @@ msgstr "" #~ msgid "Attaching Image Failed" #~ msgstr "خرابی در پیوست تصویر" + +#~ 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>سیاست اخطار ترتیب پیام</h3><p>MDNs، تعمیم آنچه معمولاً <b>رسید " +#~ "قرمز</b> نامیده میشود، میباشند. نویسندۀ پیام درخواست میکند که اخطار " +#~ "ترتیبی ارسال شود و گیرندۀ برنامۀ نامه پاسخی ایجاد کند که نویسنده از طریق " +#~ "آن بتواند آنچه در مورد پیامش رخ میدهد را بفهمد. انواع متداول ترتیب شامل " +#~ "موارد زیر میباشند<b>نمایش دادهشده</b> (یعنی خواندهشده)، <b>حذفشده</b> و " +#~ "<b>ارسالشده</b> (برای مثال، پیشسوشده).</p><p>گزینههای زیر برای کنترل " +#~ "ارسال MDNs KMail موجود میباشند:</p><ul><li><em>چشمپوشی کردن</em>: از هر " +#~ "درخواستی برای اخطارهای ترتیب چشمپوشی میکند. هیچ MDN به طور خودکار ارسال " +#~ "نمیشود )توصیه میشود(.</li><li><em>پرسیدن</em>: به درخواستها فقط بعد از " +#~ "این که از کاربر در مورد مجوز میپرسد، پاسخ میدهد. با این روش، میتوانید " +#~ "MDNs را هنگام رد کردن یا نادیده گرفتن آنها برای دیگران، جهت پیامهای " +#~ "برگزیده ارسال کنید.</li><li><em>رد کردن</em>: همیشه اخطاری<b>ردشده</b> را " +#~ "ارسال میکند. این کار فقط<em>تا اندازهای</em> بهتر از این است که همیشه " +#~ "MDNs را ارسال کرد. نویسنده هنوز میداند که پیامها مؤثر واقع شدهاند، فقط " +#~ "نمیتواند بگوید که آیا آن حذف شد یا خوانده شد و غیره.</li><li><em>همیشه " +#~ "ارسال کردن</em>: همیشه اخطار ترتیب درخواستشده را ارسال میکند. یعنی " +#~ "نویسندۀ پیام میداند چه زمانی پیام مؤثر واقع شده و به علاوه، میداند چه در " +#~ "مورد آن رخ داده است )نمایش دادهشده، حذفشده و غیره(. این گزینه شدیداً منع " +#~ "میشود، اما از آن جایی که آن برای مثال، برای مدیریت رابطۀ مشتری منطقیتر " +#~ "است، در دسترس قرار گرفته است.</li></ul></qt>t>" + +#~ 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 "" +#~ "این تنظیم، تعریف میکند که کاربرانی که در این پوشه شریکند باید دورههای " +#~ "»اشغال« را در فهرستهای آزاد اشغالشان به دست بیاورند و باید هشدارهای موجود " +#~ "در این پوشه را برای رویدادها یا تکلیفها ببینند. این تنظیم فقط برای " +#~ "پوشههای تقویم و تکلیف اِعمال میشود )در مورد تکلیفها، این تنظیم فقط برای " +#~ "هشدارها استفاده میشود(.\n" +#~ "\n" +#~ "مثال موارد استفاده: اگر رئیس با منشی وی در یک پوشه مشترک هستند، فقط رئیس " +#~ "به خاطر ملاقاتهایش به صورت اشغال نشانگذاری میشود، پس او باید »سرپرستی« را " +#~ "برگزیند، چون منشی حقوق سرپرستی در مورد پوشه را ندارد.\n" +#~ "از طرف دیگر، اگر یک گروه کاری در یک تقویم برای ملاقاتهای گروه مشترک " +#~ "باشند، برای ملاقاتهای تمام خوانندگان پوشهها، اشغال نشانگذاری میشود.\n" +#~ "یک پوشۀ سراسری شرکت که دارای رویدادهای اختیاری است برای »هیچ کس« استفاده " +#~ "نمیشود زیرا مشخص نمیشود که چه کسی به سراغ این رویدادها میرود." |