Merge translation files from master branch.

1 files changed, 87 insertions, 6 deletions

diff --git a/tde-i18n-pt_BR/messages/tdepim/kmail.po b/tde-i18n-pt_BR/messages/tdepim/kmail.po
index 75385f9932f..d1e659ff888 100644
--- a/tde-i18n-pt_BR/messages/tdepim/kmail.po
+++ b/tde-i18n-pt_BR/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: 2007-11-27 17:21-0200\n"
 "Last-Translator: Felipe Arruda <felipemiguel@gmail.com>\n"
 "Language-Team: Brazilian Portuguese <kde-i18n-pt_br@mail.kde.org>\n"
@@ -2412,12 +2412,13 @@ msgstr ""
 "possíveis.</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 "
@@ -2427,7 +2428,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, "
@@ -7741,15 +7742,16 @@ msgid "Generate free/&busy and activate alarms for:"
 msgstr "Gerar informações Livre/&Ocupado e ativar alarmes para:"
 
 #: 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 "
@@ -15763,3 +15765,82 @@ msgstr ""
 #~ "<p>\n"
 #~ "É recomendado deixar esta opção ligada para uma maior integridade.\n"
 #~ "</qt>"
+
+#~ 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>Política de Notificação de Recebimento de Mensagem (MDN)</"
+#~ "h3><p>Notificações de Recebimento de Mensagens (<em>Message Disposition "
+#~ "Notifications</em> ou MDNs) são generalizações do que é comumente chamado "
+#~ "<b>recibo de leitura</b>. O autor da mensagem requisita uma notificação "
+#~ "de recebimento a ser enviada e o programa de e-mail do receptor gera uma "
+#~ "resposta a partir da qual o autor pode saber o que aconteceu com a sua "
+#~ "mensagem. Tipos comuns de recebimento incluem <b>exibida</b> (isto é, "
+#~ "lida), <b>removida</b> e <b>despachada</b> (isto é, reenviada).</p><p>As "
+#~ "seguintes opções estão disponíveis para controlar o envio de MDNs no "
+#~ "KMail:</p><ul><li><em>Ignorar</em>: Ignora qualquer requisição de "
+#~ "notificação de recebimento. Nenhum MDN será enviando automaticamente "
+#~ "(recomendado).</li><li><em>Perguntar</em>: Responde requisições somente "
+#~ "depois de solicitar permissão ao usuário. Deste modo, você pode enviar "
+#~ "MDNs para as mensagens selecionadas enquanto bloqueia ou ignora para "
+#~ "outras.</li><li><em>Negar</em>: Envia sempre uma notificação de "
+#~ "<b>negado</b>. Isto é apenas <em>um pouco</em> melhor do que sempre "
+#~ "enviar MDNs. O autor ainda saberá que as mensagens sofreram alguma ação, "
+#~ "ele apenas não pode dizer se elas foram removidas ou lidas, etc.</"
+#~ "li><li><em>Sempre enviar</em>: Sempre envia a notificação de recebimento "
+#~ "requisitada. Isto significa que o autor da mensagem saberá quando a "
+#~ "mensagem sofreu alguma ação e, além disso, o que aconteceu com ela "
+#~ "(exibida, removida, etc.). Esta opção é fortemente desencorajada, mas já "
+#~ "que ela faz muito sentido, por exemplo, para o gerenciamento de "
+#~ "relacionamento com o cliente, ela foi mantida disponível.</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 ""
+#~ "Esta configuração define quais usuários compartilhando esta pasta devem "
+#~ "ter períodos  \"ocupados\" nas suas listas de Livre/Ocupado e devem ver "
+#~ "os alarmes para os eventos e tarefas nesta pasta. As configurações se "
+#~ "aplicam a pastas de Calendário e Tarefas, apenas (para tarefas, esta "
+#~ "configuração é utilizada apenas para alarmes).\n"
+#~ "\n"
+#~ "Casos de uso de exemplo: se o chefe compartilha uma pasta com sua "
+#~ "secretária,apenas o chefe deve ser marcado como ocupado para suas "
+#~ "reuniões, então ele deve selecionar \"Administradores\", já que a "
+#~ "secretária não possui permissões de administração na pasta.\n"
+#~ "Por outro lado, se uma equipe compartilha um calendário para reuniões, "
+#~ "todos os leitores das pastas deverão ser marcados como ocupados para as "
+#~ "reuniões.\n"
+#~ "Uma pasta geral para a companhia com eventos opcionais utilizaria "
+#~ "\"Ninguém\", já que não se sabe quem irá para os eventos."