Open lewtds opened 10 years ago
I think we can give it a cross-check. For example, i translated felix and herbert, so now another one will check that translation. Make sure to look again at the glossary and fix if its translated another way in the current version.
Did we define a way to cross-check? I think each plan only requires one cross-check and there should be some way to ensure that things don't get repeated unnecessarily
Damn. This is more time-consuming than I thought. Will create a document to teach the volunteers how to help.
@codeclubvietnam/translators - could you define a cross-check schedule, defining who is in charge of which lesson review
@lewtds - I've created a document at https://docs.google.com/document/d/1IWfrhHKO8PV1S0csCch9_DTjgtkXneBspKixVxVK-Zs/edit?usp=sharing to outline how translations are done. Can @codeclubvietnam/translators help to fill this, as I want to start getting people from all over Vietnam (and the world) helping on this task
I've created a spreadsheet at https://docs.google.com/spreadsheets/d/1BgORRBadqQNrGcw6WtWV22YQ7Ty_dqly5Xv4GHWw8dQ/edit?usp=sharing to keep track of who's reviewing and who's translating, so that I can more easily assign translators and reviewers. Please fill in accordingly
Flappy Parrot (final lesson term 1) has 3 translated versions. https://drive.google.com/?tab=co&authuser=0#folders/0B_YafJTpjoSndDNkVFFKQ2U4b0k
Can we verify which is the final
I've just deleted the redundant versions. We're working with the CSV file only.
We need to conduct a thorough review of Scratch Term 1, making sure all terminologies be translated in agreement with the glossary document, all the grammar and spelling mistakes be ironed out. Only after that can we update our version to the latest CodeClub World version (#23) and send them a pull request.