You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can use any text editor to edit the `.po` file. But if you prefer, there are also tools like [Poedit](https://poedit.net/) that provide a graphic use interface.
However, as described in [PEP 545 - Python Documentation Translations
Transifex and other similar sites can be handy in some projects, but it did not feel like a fit for PyOpenSci.
Note: for someone not familiar, Transifex is a TMS (Translation Management System), a site that manages your translation files for you and serve as interface for the translators so they don't need to interact with git or GitHub.
One of the goals of PyOpenSci is education, automating the translation contribution felt like missing a great opportunity to provide people new to open source an easy way to learn how to use git and GiHub and go through the open source contribution cycle.
Using Transifex also has the downside of the contributor not getting GitHub credit since Transifex is the one making the PR, which denies a bit the "reward" and the satisfaction of seeing your first contribution.
But as you said, there are many pros and cons and we can always consider the "cost" of maintenance versus the education side, at some point it may make sense to change course.
The translation of this repository assumes that you are using GitHub to edit po files.
python-package-guide/TRANSLATING.md
Lines 142 to 144 in 0786310
However, as described in [PEP 545 - Python Documentation Translations
Note
If the size of the translation project is as small as it is now, we are not in a hurry to solve this problem, as it is sufficient as it is now.
The text was updated successfully, but these errors were encountered: