About how sheet translations work

Hello. I've recently submitted a new Sheet to roll20. After I did that, many translation files were automatic generated by Roll20 when the sheet went live for the first time. Now I've changed some strings in my translations.json file and I've noticed they weren't updated in the translation files generated by roll20. So, how does this process work? Now I have to update every translation file directly? Can anyone explain Roll20's workflow on this? Thanks

Daniel T. said: Now I've changed some strings in my translations.json file and I've noticed they weren't updated in the translation files generated by roll20. So, how does this process work? Now I have to update every translation file directly? Can anyone explain Roll20's workflow on this? Roll20 is supposed to some script or something that automatically has changes to the translation.json file trickle down to the others, but it seems to fail often. I'd advice to manually add your changes to all the files in the future if you don't feel like gambling on whether it happens or not.

I've noticed that Roll20 automatically adds to the translation files new strings that were added to the translations.json file. But strings that already exists and were changed, it doesn't apply to the translated files, and that actually makes sense. In this case, should I edit the translation file directly on github or is it better to do it on Crowdin?

I've noticed that Roll20 automatically adds to the translation files new strings that were added to the translations.json file. Good, that's what I thought we were talking about. But strings that already exists and were changed, it doesn't apply to the translated files, and that actually makes sense. Right. Guess you need to edit them for all translations then on github. When possible, make changes in CrowdIn rather than github. Roll20 mentions this at times when people add translations(without editing the sheet itself) directly to github.

Thank you very much. I will fix it on Crowdin then.

One last question: if I fix the string on Crowdin, when does it go to production? I've translated the Roll20's Fate Sheet to Portuguese two weeks ago and the translation never went live. I fear the fix on my own sheet won't go live either via Crowdin.

Roll20 should be updating any CrowdIn translations to sheets at the same time as the general sheet changes goes live once a week. From what I've seen on github, Roll20's commit messages impiles it's some script they run that imports the crowdin changes and dumps them in a single commit.

Well, unfortunately  it is not working. My Fate sheet translation was never applied. I will end up updating both on crowdin and on github and pray for one of them to work =/

I've experienced numerous issues where changes to the translation.json do not propagate to the language files.  I often manually update the language files if I've made changes to the translation.json.  As Andreas mention, I also get a warning from the repo manager saying they will accept the changes but translation/language changes should be done using crowdin...  I have made changes using crowdin as well, but if you have just made changes to the translation.json, I don't believe they will be reflected on crowdin until after the pulls have been merged.  Kind of a chicken or egg dilemma.  This means the languages(including english) might be out-of-sync until the next update.

That is the problem. If I update the translation.json today, I have to wait till next week for it to be reflected on Crowdin. Then, after changing it on Crowdin, I'll have to wait a whole other week for them to publish the changes, IF they really do it. As I said, I've translated Fate Sheet by Roll20 and it never went live... They should at least make this process clearer on the docs...