I don’t know how much work is being done on the pt-BR team right now.
The last time that i wrote some translation string they got stale for review for a while.
Maybe someone from the i18n team can help on this. Last time @claudep accepted my request.
Sorry, looks like 6 coordinators, 20 reviewers and 481 translators!! is not enough for the pt_BR team to finish the remaining strings Please @edufelipe, I trust in you
While we are at it, @leandrodesouzadev, do you think you would be able to finish Portuguese translations for the 5.1 release?
@claudep It looks like you have fixed that translation bug already
I have added all other fixes, such as keeping the required non-breaking space, to the humanize package as suggestions.
I’ve also added a translation for all strings that were untranslated. Now the strings are unreviewed, but as of now there are no untranslated string in pt_BR.
maybe we can nudge a few of those reviewers instead? There are quite a few unreviewed strings in pt_BR and like @leandrodesouzadev mentioned, they seem to have been waiting review for a while.
I also believe that you were referring to the humanize section, that has no more strings to translate.
But on the other end, we still have a lot of work remaining on the django-docs section.
@claudep I wasn’t able to change the strings in the humanize package directly because they were marked as reviewed. All I could do is send my changes as suggestions.
There is a typo in the %d months translation that would be really neat to have accepted for 5.1.
@claudep Perfect. I fixed the string and I also took some time to review all unreviewed strings as well as tweak some of the translations for uniformity.
The verb “to delete” has several possible translations in Portuguese. In Django admin it was sometimes translated as “apagar”, other times translated as “excluir” and the most common: “remover”.
I changed all translation to “remover” so that the buttons and labels and messages say the same thing.
@claudep Just saw the announcement for Django 5.1 release candidate 1 and I have verified that all strings are translated and reviewed in the pt_BR translation.
@leandrodesouzadev, for your information, Transifex allows to show another language than English as source (from top right menu), so you could for example translate from pt_BR and then only change what is specific to pt vs pt_BR, this should speed up your work.
I noticed that the translation of Django itself to pt_BR is already complete, which is great. However, I understand that translating Django’s documentation is a massive task and ideally should not be done independently. That said, I would like to know if there is any initiative or ongoing project to address this issue.
I’ve come across several mistakes in the existing documentation translation. For example:
Please 
maybe we can nudge a few of those reviewers instead? There are quite a few unreviewed strings in pt_BR and like 
