Open silopolis opened 1 year ago
I'm trying to understand why there is such a step. Normally, the workflow is: generate POT files, update .tx/config with possible new or removed resources, push source strings to Transifex and, finally, pull translations into the source code repository. In this workflow, there is no need for pushing local translations to Transifex.
There can be scenarios where one might want to push translations to Transifex. For instance, a mass edit of translation files using programmatic ways (grep, sed, etc.) that would require some time and manual work in the Transifex web UI. But I believe this doesn't fit the usual workflow of updating source strings in Transifex.
Describe the bug
Object says it all
How to Reproduce
See In https://github.com/sphinx-doc/sphinx/tree/master/doc/usage/advanced/intl.rst
Environment Information
Platform: win32; (Windows-10-10.0.19044-SP0) Python version: 3.11.0 (main, Oct 24 2022, 18:26:48) [MSC v.1933 64 bit (AMD64)]) Python implementation: CPython Sphinx version: 5.3.0 Docutils version: 0.19 Jinja2 version: 3.1.2
Sphinx extensions
No response
Additional context
No response