Hi Sebastião ,
This raises a question about how you would prefer these cases to be reported. If a problem is clearly in a
POT/template or ultimately in the application source, should I open an issue against the corresponding TDE component, report it here first, or use some other workflow? I would like to avoid creating unnecessary issues while still separating actual translation problems from problems that need to be fixed upstream.
If the problem is wrong text in the source code, you can fix it and create a PR (rather than an issue) in TGW for inclusion into master branch.
There is one more part of the translation tree about which I am unsure: the documentation.
Slavek will be able to comment more, but I think it is one of the pending things we want to add to TWTW at some point.
My intention is ultimately to leave the Brazilian Portuguese translation in a state where it is not only more complete, but also internally consistent and checked against the applications wherever practical. While doing this, I am keeping track of cases that appear to be translation issues separately from those that may originate in templates or source code.
Translations will keep evolving over time, as TDE does I usually update Italian translations and from time to time review changes on TWTW and make sure they are once again updated. No need to overdo it, if you get what I mean.
Cheers Michele