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/27 #34435

Merged
merged 5 commits into from Apr 27, 2020
Merged

I18n sync In & Up 04/27 #34435

merged 5 commits into from Apr 27, 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 27, 2020 08:46
@@ -918,11 +918,11 @@
"lockWhenDone": "Bloquea en cuanto los estudiantes acaben",
"loggedIn": "Iniciado en: {partner}",
"loginCardForPrint1": "1.) Ir a [{directLink}]({directLink}) o a la [{joinLink}]({joinLink}) y el tipo en tu código sección letra-6: **{sectionCode}**",
"loginCardForPrint2": "2.) Elige tu nombre: **{Nombredeestudiante}**",
"loginCardForPrint2": "2.) Elige tu nombre: **{studentName}**",
Copy link
Contributor

Choose a reason for hiding this comment

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

Any idea why these are in this sync?

Copy link
Contributor

Choose a reason for hiding this comment

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

oh, woops! I started a sync out of spanish to catch these last week, but got distracted with sprint work and forgot about it. I left the changed files sitting around on the i18n machine, so they got included in the scoop.

Fortunately, them being here won't cause any problems.

@@ -918,11 +918,11 @@
"lockWhenDone": "Bloquea en cuanto los estudiantes acaben",
"loggedIn": "Iniciado en: {partner}",
"loginCardForPrint1": "1.) Ir a [{directLink}]({directLink}) o a la [{joinLink}]({joinLink}) y el tipo en tu código sección letra-6: **{sectionCode}**",
"loginCardForPrint2": "2.) Elige tu nombre: **{Nombredeestudiante}**",
"loginCardForPrint2": "2.) Elige tu nombre: **{studentName}**",
Copy link
Contributor

Choose a reason for hiding this comment

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

oh, woops! I started a sync out of spanish to catch these last week, but got distracted with sprint work and forgot about it. I left the changed files sitting around on the i18n machine, so they got included in the scoop.

Fortunately, them being here won't cause any problems.

@Hamms Hamms merged commit ba2264f into staging Apr 27, 2020
@Hamms Hamms deleted the i18n-sync-in-up-04-27 branch April 27, 2020 17:48
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