Update translations: default

[translation-platform]

This PR modifies translations in the project. It will append multiple commits and may add, modify, or delete translations. Feel free to merge any time.

Before you deploy

• Check translations for malicious HTML.

Merge conflicts?

Details

If this PR has been open long enough that it has drifted out of sync from the base branch and it has developed merge conflicts as a result, follow these steps, in order:

1. Close this PR.
2. Run the following Spy command in Slack, inserting the PR number in the second argument:

@spy translation-platform force-pull Shopify/polaris pull_request_number=<this PR>.

Translation Platform will recreate the translation commits based on the latest commit on the base branch and open a new PR.

Translation quality issues?

Details

If there are any translation issues, please kindly include them in our translation feedback form.

Our language specialists will review and make any necessary corrections. Updates (if necessary) will arrive asynchronously, so if the error is non-blocking, proceed with shipping your pull request.

If your issue is a blocker or high severity, please ping @locpms in #help-localization so it can be prioritized.

Questions?

Visit #help-localization for questions about this pull request or to report a translation quality issue.

Translation component owners: @Shopify/polaris-eng

[translation-platform]

🕐 This PR has been open for 2 days now 🕐

It is best to merge it as soon as possible in order to avoid having to deal with merge conflicts.

More importantly, the content here really wants to reach production so everyone can benefit from it.

It is your responsibility to merge this PR once you've reviewed it. 🙏

💚

[translation-platform]

🕐 This PR has been open for 6 days now 🕐

It is best to merge it as soon as possible in order to avoid having to deal with merge conflicts.

More importantly, the content here really wants to reach production so everyone can benefit from it.

It is your responsibility to merge this PR once you've reviewed it. 🙏

💚

[translation-platform]

🕐 This PR has been open for 8 days now 🕐

It is best to merge it as soon as possible in order to avoid having to deal with merge conflicts.

More importantly, the content here really wants to reach production so everyone can benefit from it.

It is your responsibility to merge this PR once you've reviewed it. 🙏

💚

[translation-platform]

🕐 This PR has been open for 10 days now 🕐

It is best to merge it as soon as possible in order to avoid having to deal with merge conflicts.

More importantly, the content here really wants to reach production so everyone can benefit from it.

It is your responsibility to merge this PR once you've reviewed it. 🙏

💚

[translation-platform]

🕐 This PR has been open for 13 days now 🕐

It is best to merge it as soon as possible in order to avoid having to deal with merge conflicts.

More importantly, the content here really wants to reach production so everyone can benefit from it.

It is your responsibility to merge this PR once you've reviewed it. 🙏

💚

[translation-platform]

🕐 This PR has been open for 16 days now 🕐

It is best to merge it as soon as possible in order to avoid having to deal with merge conflicts.

More importantly, the content here really wants to reach production so everyone can benefit from it.

It is your responsibility to merge this PR once you've reviewed it. 🙏

💚

[translation-platform]

🕐 This PR has been open for 20 days now 🕐

It is best to merge it as soon as possible in order to avoid having to deal with merge conflicts.

More importantly, the content here really wants to reach production so everyone can benefit from it.

It is your responsibility to merge this PR once you've reviewed it. 🙏

💚

[translation-platform]

🕐 This PR has been open for 23 days now 🕐

It is best to merge it as soon as possible in order to avoid having to deal with merge conflicts.

More importantly, the content here really wants to reach production so everyone can benefit from it.

It is your responsibility to merge this PR once you've reviewed it. 🙏

💚

[translation-platform]

🕐 This PR has been open for 27 days now 🕐

It is best to merge it as soon as possible in order to avoid having to deal with merge conflicts.

More importantly, the content here really wants to reach production so everyone can benefit from it.

It is your responsibility to merge this PR once you've reviewed it. 🙏

💚

[translation-platform]

🕐 This PR has been open for about 1 month now 🕐

It is best to merge it as soon as possible in order to avoid having to deal with merge conflicts.

More importantly, the content here really wants to reach production so everyone can benefit from it.

It is your responsibility to merge this PR once you've reviewed it. 🙏

💚

[translation-platform]

🕐 This PR has been open for about 1 month now 🕐

It is best to merge it as soon as possible in order to avoid having to deal with merge conflicts.

More importantly, the content here really wants to reach production so everyone can benefit from it.

It is your responsibility to merge this PR once you've reviewed it. 🙏

💚

[translation-platform]

🕐 This PR has been open for about 1 month now 🕐

It is best to merge it as soon as possible in order to avoid having to deal with merge conflicts.

More importantly, the content here really wants to reach production so everyone can benefit from it.

It is your responsibility to merge this PR once you've reviewed it. 🙏

💚

[github-actions]

Hi! We noticed there hasn’t been activity on this PR in a while. After 30 days, it will close automatically.

If it’s still relevant, or you have updates, comment and let us know. And don’t worry, you can always re-open later if needed.

[shopify-shipitnext]

🔎 View this PR in Shipit Next.

ℹ️ Expand to learn how to deploy and handle emergencies using Shipit Next

Overview

Shipit Next will merge your code on your behalf because this repository uses Shipit Next and its merge queue.

To ship this PR, you can either:

• Comment /shipit to enqueue this PR for merging.
• Go to this PR in Shipit Next and click on the "Ship It" button in the top-right corner.

Comment Commands

• /shipit: Enqueue this PR into the merge queue where it will eventually be merged and deployed.
• /cancel: Eject this PR from the merge queue and rebuild PRs that were enqueued after this PR.
• /shipit --jump-queue: Enqueue this PR at the top of the merge queue where it will be included in the next deploy. Use this for non-emergency situations.
  - Emergency handling procedure for this command can be found here.
• /shipit --emergency: Merge this PR directly into main and deploy to all environments once all require_for_emergency CI checks pass. Please be aware that changes deployed with this command will not be automatically rolled back.
  • Emergency handling procedure for this command can be found here.

Commands exclusive to Deploy Before Merge

• /cancel --emergency: Eject this PR from the merge and rollback any deployments containing this PR.

---

Documentation

• ℹ️ You can read how the merge queue works in Vault here.
• ⚠️ Emergency handling documentation in the Vault describes how to handle emergencies, e.g. failed canaries, broken code in production, etc.

Questions or feedback?

• Non-urgent questions can be submitted in our Discourse.
• Feedback can be submitted in our frustrations Google form.
• If you have feature requests, you may add them or vote for them in our GitHub repository.