Rafael Fontenelle

Just to mention that the broken theme issue is addressed in #363

As translator, I love to find translation files with up-to-date source strings, not having to run commands to check whether there are new ones. So, I'm in favor of having...

@Ayush-singla27 If your PR should close this issue, consider next time use a keyword to [link your PR to the issue](https://docs.github.com/pt/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword). Using keywords like close, resolves, fixes, etc. will automatically...

@Ayush-singla27 That linking works only in the original post, but we're past that point. @stabbystabstab can still close, or just wait an admin spot this conversation and close it.

@ieahleen It seems so, yes. Reading the source file, the intention is to create a "`text.innerText` Your [weapon] breaks." string. This step adds "Your", making sure there is a space...

@m-aciek Thanks for the suggestion.

@m-aciek Currently .tx/config is recreated when scripts/update.sh runs the sed command outputting to .tx/config. Still, some changes are necessary to fit the new tx client, so thanks for bringing this...

I would like to highlight the frc-docs-translations workflow brought up in https://github.com/readthedocs/readthedocs.org/issues/4463#issuecomment-950789132 and next comments, a job nicely done by @Daltz333 and others, which could be used as inspiration for...

@mendax1234 Do you want an explanation or a PR we can start working on?

> In addition, if you only modify a specific file and don't change its location , it seems that when you push it to transifex again , the translation of...