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
Currently when contributors add a new documentation translation, project owners need to manually create a translation project and configure it in RTD.
For lonely owners of multiple projects, this can quickly become a boring thing to do.
It would be more convenient if RTD had a way to detect new languages in the repository, and automatically create and configure the translation project, without manual intervention.
At the other end of the translation pipeline, Weblate allows some automations of this kind (catalog files can be automatically updated, translations can be automatically pushed).
With RTD translation project automatic creation, this would allow the translation community to be almost independent for producing and publishing translations.
What do you think?
The text was updated successfully, but these errors were encountered:
I understand this could be a little boring to do, but making it automatically would need to deal with permissions which will make this feature become pretty complex immediately.
Currently when contributors add a new documentation translation, project owners need to manually create a translation project and configure it in RTD.
For lonely owners of multiple projects, this can quickly become a boring thing to do.
It would be more convenient if RTD had a way to detect new languages in the repository, and automatically create and configure the translation project, without manual intervention.
At the other end of the translation pipeline, Weblate allows some automations of this kind (catalog files can be automatically updated, translations can be automatically pushed).
With RTD translation project automatic creation, this would allow the translation community to be almost independent for producing and publishing translations.
What do you think?
The text was updated successfully, but these errors were encountered: