GNU Mailman/Postorious — Portuguese (Brazil) @ Hosted Weblate

Translation status

652	Strings	98%	Browse Translate
5,356	Words	92%
34,086	Characters	92%

Strings status

Strings Words Characters
652 5,356 34,086	All strings	Browse Translate Zen
646 4,986 31,681	Translated strings	Browse Translate Zen
6 370 2,405	Unfinished strings	Browse Translate Zen
3 64 359	Untranslated strings	Browse Translate Zen
3 306 2,046	Strings marked for edit	Browse Translate Zen
2 21 130	Strings with any failing checks	Browse Translate Zen
2 21 130	Translated strings with any failing checks	Browse Translate Zen
1 35 277	Translated strings with dismissed checks	Browse Translate Zen
2 21 130	Failing check: Multiple capitals	Browse Translate Zen

Other components

Component	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
Django-mailman3 GPL-3.0-or-later		0	0	0	0	0	0	0

HyperKitty GPL-3.0-or-later		0	0	0	0	0	0	0

Mailman Core GPL-3.0-or-later	99%	4	6	41	4	0	0	0

Browse all components

Summary

Project website	list.org
Instructions for translators	Mailing list for translators: <mailman-developers@python.org
Project maintainers2	maxking msapiro
Translation license	GNU General Public License v3.0 or later
Translation process	Translations can be made directly. Translation suggestions can be made. Any authenticated user can contribute. The translation uses bilingual files.
Source code repository	`https://gitlab.com/mailman/postorius.git`
Repository branch	master
Last remote commit	Merge branch 'weblate-gnu-mailman-postorius' into 'master' `f547593a` msapiro authored 02/13/2026
Last commit in Weblate	Merge branch 'weblate-gnu-mailman-postorius' into 'master' `f547593a` msapiro authored 02/13/2026
Weblate repository	`https://hosted.weblate.org/git/gnu-mailman/postorius/`
File mask	`src/postorius/locale/*/LC_MESSAGES/django.po`
Translation file	Download `src/postorius/locale/pt_BR/LC_MESSAGES/django.po`
Last change	June 25, 2025, 12:02 a.m.
Last change made by	None
Language	Portuguese (Brazil)
Language code	pt_BR
Text direction	Left to right
Case sensitivity	Case-sensitive
Number of speakers	200,247,320
Number of plurals	2
Plural type	One/other
Plurals	Singular	0, 1
Plurals	Plural	2, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
Plural formula	`n > 1`

01/25/2026

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		652		5,356		34,086
Translated	99%	646	93%	4,986	92%	31,681
Needs editing	1%	3	5%	306	6%	2,046
Read-only	0%	0	0%	0	0%	0
Failing checks	1%	2	1%	21	1%	130
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	1%	3	1%	64	1%	359

Last 12 months Previous

Activity in last 12 months


Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec	Jan

Quick numbers

5,356

Hosted words

652

Hosted strings

99%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

+100%

—

Hosted strings

+100%

—

Translated

+99%

—

Contributors

—

None

Resource updated

The “src/postorius/locale/pt_BR/LC_MESSAGES/django.po” file was changed. 06/24/2025

None

String added in the repository

English

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.

Portuguese (Brazil) 1943 characters editedCurrent translationState: Needs editing

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, sobrescrevendo, 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 você 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 em uma 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

None

Source string changed

English 185 characters editedNeeds editing

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 stripped~~may 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

None

Resource updated

The “src/postorius/locale/pt_BR/LC_MESSAGES/django.po” file was changed. 06/09/2025

None

String added in the repository

English

Portuguese (Brazil) 209 characters editedCurrent translationState: Needs editing

06/09/2025

None

Source string changed

English 1 character editedNeeds editing

06/09/2025

None

Resource updated

The “src/postorius/locale/pt_BR/LC_MESSAGES/django.po” file was changed. 04/29/2025

None

String added in the repository

English

Portuguese (Brazil) 0 characters editedCurrent translationState: Empty

04/29/2025

None

String added in the repository

English

Portuguese (Brazil) 20 characters editedCurrent translationState: Needs editing

04/29/2025

None

Source string changed

English 10 characters editedNeeds editing

04/29/2025

Browse all translation changes

Quick downloads

652	File in original format as translated in the repository	gettext PO file
652	All strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX
6	Unfinished strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX

Customize download

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>="1 month ago" AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>="1 month ago" AND state:<=needs-editing`	Add
Strings changed in the past two weeks	`changed:>="2 weeks ago"`	Add
Automatically translated strings	`is:automatically-translated`	Add

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the previous translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.