Translation & Crowdin Changes

Exciting news! We’re making some changes to the way translations function on our site! Currently, we allow amazing community volunteers to translate various aspects of our site via our translation service, Crowdin . We’re still going to be using Crowdin for all of our translation services, but there are going to be a few changes coming up.  Going forward, the translation of our platform will now be split into 3 different Crowdin projects. Those 3 projects are as follows: Main Site Text on our site that exists outside of our Character Sheets. The text for the Marketplace, Toolbar buttons, My Account page, etc.  Roll20 Official Character Sheets Text for Character Sheets that are created and maintained by Roll20. Roll20 Character Sheets Text for Character Sheets that were created and maintained by the community. With this split, we are also changing the way folks can access and be approved to translate for those projects. Here’s the general gist: Main Site Approval to translate for this project is required . Submit a translation approval request through our Help Center form . Roll20 Official Character Sheets & Roll20 Character Sheets Approval to translate for these projects is no longer required . You’ll either create a new Crowdin account or log in to an existing account, join one of those projects, and you’re good to go. We are looking to move forward with these translation changes by 11/6/2020.  As we make these updates, we will be temporarily cutting off translation requests/changes from 11/5/2020 to 11/6/2020. Translations during that time will not be accepted. Here are a couple of things that are important to note with these changes. Until we make the above changes, translations and translation approvals will function as they did before and the linked Character Sheet projects will be empty. We are no longer accepting Character Sheet translations through GitHub . Crowdin will now automatically overwrite any translations added through GitHub. All translations must be done through Crowdin now.  New translators in the Character Sheet projects will not receive Translator badges on their profiles at this time. Adding this functionality will be a future improvement. Translators in the Main Site project will still receive badges. No one will be losing existing translation badges. Please let us know if you have any further questions, comments, or concerns! Thanks everyone! :)

Evil Hat Productions said: Will this address the tendency with some sheets for the en.json file to *not match* the translation.json file source? Is it safe to assume that translation.json should still travel with the rest of the sheet stuff when posting sheets to the character sheet github?      To confirm, the translation.json will still be required for translation of your sheet and will remain the same as before. As for the mentioned issues, we would need some additional information on the specific instances where the en.json and translation.json files weren't matching. If you could provide me the name of a sheet from our repo that had this issue though, I'll definitely have our team take a look.

ᐰndreas J. said: Here are some of the recent ones, where automatic updates didn't work out, or caused troubles: <a href="https://github.com/Roll20/roll20-character-sheets/issues/7509" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/issues/7509</a> <a href="https://github.com/Roll20/roll20-character-sheets/issues/7459" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/issues/7459</a> <a href="https://github.com/Roll20/roll20-character-sheets/issues/7386" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/issues/7386</a> <a href="https://github.com/Roll20/roll20-character-sheets/pull/7601" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/pull/7601</a> I recall there was some issues with the Forbidden Lands sheet as well, but don't care for digging it up right now. Awesome, thank you Andreas! I'll have the team review as soon as we can.

Lucas X. said: It says something about Translator badge, how do I know if I can get one? I been translating on crowdin for awhile but not sure if I can get the badge Currently, Translator badges are granted when you get approval to translate via our support team . If you are currently approved and don't have one, make sure to contact support and we'll get you squared away. With these changes, you will only get a Translator badge if you contact our support team and are approved to translate for the Main Site project. Translating for the open Character Sheet projects will not provide badges, although that is an improvement we're looking at later down the road.

라브 said: Excited by the new changes!&nbsp; +) So if you are part of the Main Site team, you should be in three different projects (Roll20-Site, Roll20 Official Character Sheets, and Roll20 Character Sheets), correct?&nbsp; Hmmm yes and no.&nbsp; After these changes, if you are approved to join the Main Site project (Roll20-Site), you will still have to manually join the other 2 Character Sheet projects if you want to translate for them; we want to leave the choice of which ones to join up to you. Keep in mind the Character Sheet projects are open projects though, so there is no approval process for them. However, if you are already a translator before these changes have been made, we are looking into adding all current translators to the 3 projects. Current translators have access to everything right now (Character Sheets, Main Site, etc.), so it makes sense to get you added to all 3 projects right off the bat. Does that make sense? Or can I clarify anything there?

Hey folks! Quick update! We're running into some issues with the migration. As such, all 3 projects &nbsp;won't be ready to use until tomorrow. We'll continue to keep you updated as we make progress here. Apologies for the trouble!

Hey everyone, another update here! Unfortunately, we’re running into some issues with Crowdin and have not been able to fully complete the noted updates yet.&nbsp; As we work through these issues, translation submissions will be temporarily closed from now till Monday (11/09/2020). Our sincerest apologies for this inconvenience!&nbsp; If you have any questions or concerns, please feel free to let us know. Otherwise, we’ll continue to keep you updated on the status and situation.

Hello again! Just wanted to update you here that all issues regarding Crowdin have been resolved. As of now, translations are up and running and you can begin to translate in any of the 3 new Crowdin projects. To reiterate, here is the general process and approval changes to each project. Main Site Approval to translate for&nbsp;this project&nbsp; is required . &nbsp;Submit a translation approval request through&nbsp; our Help Center form . Roll20 Official Character Sheets &nbsp;&amp;&nbsp; Roll20 Character Sheets Approval to translate for&nbsp;these projects&nbsp; is no longer required . You’ll either create a new&nbsp; Crowdin &nbsp;account or log in to an existing account, join one of those projects, and you’re good to go. Let us know if you have any other question, comments, or concerns! Thanks for your patience everyone! :)

Hey folks -&nbsp; It actually looks like the&nbsp; Roll20 Character Sheets &nbsp;project is still temporarily unavailable due to the project size - it's still working through the update. Our sincerest apologies for not catching that and notifying you. To confirm though, both the&nbsp; Roll20 Official Character Sheets &nbsp;and Main Site projects are up and good to go. We'll let you know as soon as soon as that final project ( Roll20 Character Sheets )&nbsp;has finished and is up and running. Thank you!

Hello everyone -&nbsp; Final update (hopefully)! The&nbsp; Roll20 Character Sheets &nbsp;project has finished updating and should now be available for translation as well. If you run into any issues or have any questions, please don't hesitate to let us know! Happy rolling! :)

라브 said: D&amp;D 5e official sheet is no longer available on Roll20 Official Character Sheet Project. Is this an error or is it intended? Hey there! You should be able to access the 5th edition sheet at this point. If you are still having trouble accessing it, please let me know.

∇ince said: I recently updated the translation.json for the Forbidden Lands sheet (merged #7683 on Friday), but I'm not seeing any of those changes reflected in the language files on crowdin to allow for translation...&nbsp; I understand that sheets are now being merged more frequently(awesome), but how often will the translation updates happen?&nbsp; Is this an automated process (api) or does someone have to manually merge/update translation changes? Please excuse my ignorance... Thanks Hey&nbsp;∇ince -&nbsp; No worries at all! We might tweak the timing a bit, but right now the Crowdin API checks for and uploads any changes made to the translation.json files in the various repo's roughly every hour. Translations then submitted by translators through Crowdin are manually reviewed/merged and made live at the same time (usually) as the weekly sheet update.&nbsp; Does that make sense? Or can I clarify anything there?

Gan said: Gan said: I have already committed all my changes and they were merged into master. I also got that messege you mentioned. I can see the changes in the github, but nothing in the Roll20 nor in the crowdin. Does it takes some time to see these changes or do I need to contact someone from the Roll20 support? It seems all my changes have been overwritten by the crowdin update. So it seems, that there is no other way then copy-pasting the translation one-by-one? Hey Gan -&nbsp; In general, we are no longer accepting translations outside of Crowdin. However, I've sent you a PM to help get this resolved without copy-pasting. Send me a reply via PM whenever you get a chance. Thanks!

Heya&nbsp;Akefal - Were you still running into troubles here? Or were you able to get this resolved?

This issue is most likely caused by an earlier version of the sheet having a different translation for this key, and then changing the source translation after the initial version. There are two possible solutions here: Add a new translation key for "height". This is recommended if there are other places in the sheet that use the "Page Height" translation. Simply add an English translation as "Height" in that translation box. The latter solution can be done through Crowdin, the former would require modifying the source "translation.json" file in GitHub, as well as the places in the HTML file that use the translation.

Hey folks! Since these changes have been deployed and most questions or concerns have been answered here, we're going to go ahead and close this thread. If you have any other feedback or issues, please reach out to our support team via this form &nbsp;and they'll get you squared away. Thanks all!