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
It's hard to keep track of the changes made to the tutorial and update the translations in consequence. If I'm not ready to update the translation for every merged PR, I'll loose track of the changes, and the translation will be out of date quickly.
The only tool for translators I've ever used is Mozilla's Pontoon, but I'm sure there is plenty others. All we have to do is export the tutorial in a file format that can be read by a chosen software, and work on the translation. Then a CI job should be able to handle the translations and generate the static files for the translated tutorial.
I'm not sure I understand the problem. Wouldn't it be simple enough to check what has been committed to the main branch since the last commit to the respective language's directory?
It's hard to keep track of the changes made to the tutorial and update the translations in consequence. If I'm not ready to update the translation for every merged PR, I'll loose track of the changes, and the translation will be out of date quickly.
The only tool for translators I've ever used is Mozilla's Pontoon, but I'm sure there is plenty others. All we have to do is export the tutorial in a file format that can be read by a chosen software, and work on the translation. Then a CI job should be able to handle the translations and generate the static files for the translated tutorial.
What are your thoughts on this @Overv ?
The text was updated successfully, but these errors were encountered: