Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×

[Help] Translating a sheet : what to do once the html is translated ?

1455040523

Edited 1455040629
Hi guys, I am translating the Call of Cthulhu v5 character sheet to French (I saw that a french v7 sheet is available but I still have a v5 game lying on a shelf); I have a couple of simple questions      How do I test-it? I would rather be sure that it works before making it available, I can visualize the sheet in my browser (it seems I haven’t f… up with the HTML codes for “accents” but I cannot check locally whether it starts the right rolls (as it’s only a translation I am quite confident)      Once tested, how do I make it available, I guess that the question is who shall I ask permission to send the sheet on github.?      Last (but not least question) if we create the characters with an English sheet (I assume my player are able to understand the 50 words needed to read a charater sheet), can we switch to the French sheet without losing the content? (I changed only the visible text of the attributes/skills but not their meaning) I have a free account, and do not need the feature of a pro account (but the custom character sheet), shall I switch to a pro account a couple of month to test my custom sheet and switch back to free or is there a way to do tests otherwise ?  
1455058165
Lithl
Pro
Sheet Author
API Scripter
In order to be absolutely certain of a sheet's appearance and behavior, you need a campaign created by someone with a Pro subscription. It's simplest if you subscribe yourself, but if you've got a friend with a subscription willing to help you with your sheet, that could work, too. I wrote a  Beginner's Guide to GitHub a while back, although the screenshots it uses are from an older version of GitHub for Windows and the interface has changed a little bit. It's also now possible to create a pull request, the last step in the guide, from within the application, although it wasn't at the time the guide was written. If the name  attributes are unchanged between two sheets (and the class  attribute of fieldsets for repeating sections), the content will remain unchanged.