Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Django-mailman3 GPL-3.0-or-later 85% 12 208 1,165 10 1
Glossary GNU Mailman GPL-3.0-or-later
HyperKitty GPL-3.0-or-later 98% 3 6 31 1
Mailman Core GPL-3.0-or-later 84% 66 963 6,623 66 32 9
Postorious GPL-3.0-or-later 95% 30 802 5,337 11 10

Summary

Project website list.org
Instructions for translators

Mailing list for translators: <mailman-developers@python.org
Project maintainers2 User avatar maxkingUser avatar msapiro
Language Portuguese
Language code pt
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 249,463,918
04/16/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,413 12,822 82,747
Translated 92% 1,302 84% 10,843 84% 69,591
Needs editing 1% 24 5% 681 5% 4,596
Read-only 0% 0 0% 0 0% 0
Failing checks 3% 44 17% 2,198 17% 14,129
Strings with suggestions 1% 9 1% 49 1% 318
Untranslated strings 6% 87 10% 1,298 10% 8,560
Last 12 months Previous

Activity in last 12 months

0 changes 7 changes 4 changes 0 changes 3 changes 6 changes 0 changes 2 changes 17 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes 13 changes 0 changes 0 changes 0 changes 10 changes 0 changes 0 changes 0 changes
AprMayJunJulAugSepOctNovDecJanFebMar

Quick numbers

12,822
Hosted words
1,413
Hosted strings
92%
Translated
7
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+92%
—
Contributors
—
User avatar None

Resource updated
The “src/mailman/messages/pt/LC_MESSAGES/mailman.po” file was changed. 07/05/2025
User avatar None

String added in the repository
Check whether to Apply DMARC mitigations.
 
07/05/2025
User avatar None

Resource updated
The “src/postorius/locale/pt/LC_MESSAGES/django.po” file was changed. 06/24/2025
User avatar None

String added in the repository
Where are replies to list messages directed? No Munging is strongly recommended for most mailing lists.
This option controls what Mailman does to the Reply-To: header in messages flowing through this mailing list. When set to No Munging, no Reply-To: header is added by Mailman, although if one is present in the original message, it may be stripped depending on First strip Reply-To. Setting this value to Reply to List or either of the Explicit Reply settings causes Mailman to insert a specific Reply-To: header in all messages, either adding to or overriding the header in the original message depending on First Strip Reply-To. Explicit Reply inserts the value of Explicit reply-to_address, Reply goes to list inserts the list posting address. Explicit Reply-to set; no Cc added is useful forannounce-only lists where you want to avoid someone replying to the list address. There are many reasons not to introduce or override the Reply-To: header. One is that some posters depend on their own Reply-To: settings to convey their valid return address. Another is that modifying Reply-To: makes it much more difficult to send private replies. See <a href="http://marc.merlins.org/netrants/reply-to-harmful.html">`Reply-To' Munging Considered Harmful</a> for a general discussion of this issue. See <a href="http://marc.merlins.org/netrants/reply-to-useful.html">`Reply-To' Munging Considered Useful</a> for a dissenting opinion. Some mailing lists have restricted posting privileges, with a parallel list devoted to discussions. Examples are `patches' or `checkin' lists, where software changes are posted by a revision control system, but discussion about the changes occurs on a developers mailing list. To support these types of mailing lists, select Explicit Reply and set the Reply-To: address option to point to the parallel list.
Para onde as respostas para a lista são direcionadas? Não usar o mascaramento é recomendado para maioria das listas.
Esta opção controla o que o Mailman faz com o cabeçalho Reply-To: nas mensagens que fluem pela lista de discussão. Quando se usa o "Não mascare o endereço de e-mail", o cabeçalho Reply-To: não será adicionado pelo Mailman. Contudo, se um estiver presente na mensagem original, ele será mantido. Usando tanto a opção "Responder para a Lista", "Endereço de resposta explícito" ou "Somente Responder", fará o Mailman adicionar um cabeçalho Reply-To: específico em todas as mensagens, a sobrescrever, se necessário, o mesmo campo na mensagem original ("Responder Explicitamente" vai usar o endereço definido em reply_to_address). Na opção "Responder Explicitamente", nenhum Cc será adicionado e é útil para listas exclusivas para anúncios onde quer evitar que as pessoas respondam para a lista. Existem muitas razões para não adicionar ou sobrescrever o cabeçalho Reply-To:. Uma delas é que alguns remetentes dependem deste campo para informar o endereço de resposta válido. Uma outra razão é que ao modificar o "Reply-To:", fica muito mais difícil enviar respostas privadas. Veja <a href="http://marc.merlins.org/netrants/reply-to-harmful.html">`Reply-To' Munging Considered Harmful</a> para uma discussão deste problema. Veja <a href="http://marc.merlins.org/netrants/reply-to-useful.html">`Reply-To' Munging Considered Useful</a> para uma opinião a favor deste recurso. Algumas lista de discussão possuem restrições das postagens, com uma lista em paralelo dedicada para discussões. Alguns exemplos são listas `patches' ou `checkin', onde as mudanças nos códigos são enviadas por um sistema de controle de versão mas a discussão sobre as mudanças ocorre numa lista de desenvolvimento. Para permitir este tipo de lista, selecione "Responder Explicitamente" e ajuste o endereço do campo Reply-To: para a lista em paralelo.
06/24/2025
User avatar None

Source string changed
Where are replies to list messages directed? No Munging is strongly recommended for most mailing lists.
This option controls what Mailman does to the Reply-To: header in messages flowing through this mailing list. When set to No Munging, no Reply-To: header is added by Mailman, although if one is present in the original message, it is not strippedmay be stripped depending on First strip Reply-To. Setting this value to either Reply to List, Explicit Reply, or Reply Only or either of the Explicit Reply settings causes Mailman to insert a specific Reply-To: header in all messages, either adding to or overriding the header in the original message if necessary (depending on First Strip Reply-To. Explicit Reply inserts the value of reply_to_Explicit reply-to_address, Reply goes to list inserts the list posting address). Explicit Reply-to set; no Cc added is useful forannounce-only lists where you want to avoid someone replying to the list address. There are many reasons not to introduce or override the Reply-To: header. One is that some posters depend on their own Reply-To: settings to convey their valid return address. Another is that modifying Reply-To: makes it much more difficult to send private replies. See <a href="http://marc.merlins.org/netrants/reply-to-harmful.html">`Reply-To' Munging Considered Harmful</a> for a general discussion of this issue. See <a href="http://marc.merlins.org/netrants/reply-to-useful.html">`Reply-To' Munging Considered Useful</a> for a dissenting opinion. Some mailing lists have restricted posting privileges, with a parallel list devoted to discussions. Examples are `patches' or `checkin' lists, where software changes are posted by a revision control system, but discussion about the changes occurs on a developers mailing list. To support these types of mailing lists, select Explicit Reply and set the Reply-To: address option to point to the parallel list.
06/24/2025
User avatar None

Resource updated
The “src/postorius/locale/pt/LC_MESSAGES/django.po” file was changed. 06/09/2025
User avatar None

String added in the repository
Should any existing Reply-To: header found in the original message be stripped? If so, this will be done regardless of whether an explicit Reply-To: header is added by Mailman or not.
Deve um cabeçalho "Reply-To:" existente encontrado na mensagem original ser descartado? Se assim for, isso será feito independentemente de um cabeçalho "Reply-To:" explícito ser adicionado pelo Mailman ou não.
06/09/2025
User avatar None

Source string changed
Should any existing Reply-To: header found in the original message be stripped? If so, this will be done regardless of whether an explicit Reply-To: header is added by Mailman or not.
06/09/2025
User avatar None

Resource updated
The “src/postorius/locale/pt/LC_MESSAGES/django.po” file was changed. 04/29/2025
User avatar None

String added in the repository
No. of days after which held messages will be automatically discarded. Set to zero for no automatic discard.
 
04/29/2025
Browse all changes for this language