Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I18n sync In & Up 04/13 #34188

Merged
merged 5 commits into from Apr 14, 2020
Merged

I18n sync In & Up 04/13 #34188

merged 5 commits into from Apr 14, 2020

Conversation

deploy-code-org
Copy link
Contributor

I18n Sync In & Up

This PR contains all changes to internationalization source strings made since the last sync (usually a week).

To Review:

  1. Look through the changes in each of the commits and verify that all changes are expected

    • We expect content changes to come in on a regular basis; individual strings will get updated, added, and deleted.

    • We do not usually expect to see "comprehensive" changes - or changes that apply to large numbers of strings or whole categories of strings all at once - unless we have made specific code changes.

  2. Notify the International Partners team about any changes that might appear to manifest as "lost translations"

    • For example: https://github.com/code-dot-org/code-dot-org/pull/31031/files#diff-aa1910a8cf8f9290ae3baf7e39dbae3eL397-R398

      This is a change that added new strings (with both new keys and new content) and simultaneously removed some very similar old ones; we can reasonably infer that the intent here was to swap the new strings out for the old ones. Unfortunately, because the swap also included a content change to the strings the crowdin duplication system won't automatically apply translations to the new strings and so they will need to be manually re-translated.

To Deploy:

Once one or two people have reviewed and approved this change and the tests are passing, ship it!

It's not necessary to wait for everyone on the team to review.

@deploy-code-org deploy-code-org requested a review from a team as a code owner April 13, 2020 08:45
@@ -45,27 +45,27 @@
},
"https://studio.code.org/s/csd5-2019/stage/5/puzzle/2": {
"long_instructions": "# 5-Bit Number\n\nWhen you only had four bits, the highest number that you could make was fifteen. Now you'll have a chance to work with more bits to make higher numbers.\n\nIn this activity, the dots are replaced with numbers, but you still add up everything that's showing to see what number the binary code stands for. The left-most bit doesn't have a number yet, so you'll have to give it one.\n\n# Do This\n\n- Click on the bits to turn them on and off, and see the different numbers you can make.\n- With your partner, discuss the pattern in the numbers. Decide what number you think should go in the left most box.\n- Click \"Edit\" to change the value of the left most bit.\n- Once you've decided on the value, try to make the following numbers: 16, 27, 31",
"teacher_markdown": "Answers for this level can be found in the exemplar linked on [Level 1][0]."
"teacher_markdown": "[][0]\n\nAnswers for this level can be found in the exemplar linked on [Level 1][1].\n\n[/][0]"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Hamms will this break existing translations?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, I can't find any translations for this strings so probably fine

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, good catch! It probably would have, but disaster avoided!

@bethanyaconnor bethanyaconnor merged commit 3e432ae into staging Apr 14, 2020
@bethanyaconnor bethanyaconnor deleted the i18n-sync-in-up-04-13 branch April 14, 2020 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants