Skip to content

Update translations#2862

Open
bc-svc-local wants to merge 1 commit intomasterfrom
LOCAL-1444-deliver-translations-2026-03-02-09-32-06
Open

Update translations#2862
bc-svc-local wants to merge 1 commit intomasterfrom
LOCAL-1444-deliver-translations-2026-03-02-09-32-06

Conversation

@bc-svc-local
Copy link
Collaborator

@bc-svc-local bc-svc-local commented Mar 2, 2026

This pull request was created automatically. Please check new translations, approve and deliver them.


Note

Low Risk
Low risk: changes are limited to locale JSON string updates/additions, with no code logic changes. Primary risk is user-facing wording/consistency issues (some new strings remain English in certain locales).

Overview
Refreshes packages/locale translations across multiple languages by replacing leftover English strings (e.g., numeric validation and Adyen multibanco mandate fields) with localized text.

Adds new localized strings used by the cart stock/backorder UX (e.g., cart.backorder_quantities_changed_heading, cart.cart_stock_modal_destination, cart.qty_label, backorder show/hide labels) and introduces payment.payment_methods_unavailable_error plus shipping.multishipping_backordered_quantity in affected locales.

Written by Cursor Bugbot for commit 56ae752. This will update automatically on new commits. Configure here.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 4 potential issues.

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

"custom_min_number_error": "{label} must be greater than or equal to {min}",
"custom_max_number_error": "{label} must be less than or equal to {max}",
"custom_range_error": "{label} must be between {min} and {max}",
"custom_min_number_error": "{label}は 0 以上である必要があります{min}",
Copy link

Choose a reason for hiding this comment

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

Japanese min-number translation hardcodes "0" instead of placeholder

High Severity

The Japanese custom_min_number_error translation hardcodes a literal 0 where the {min} placeholder belongs, and then appends {min} at the end of the string where it makes no grammatical sense. Users will always see "0" as the minimum regardless of the actual value, with the real minimum tacked on at the end. Similarly, custom_max_number_error places {max} at the end of the string instead of before 以下, producing a broken sentence like "{label}は 以下である必要があります{max}" instead of the correct "{label}は{min}以上である必要があります" / "{label}は{max}以下である必要があります".

Additional Locations (1)

Fix in Cursor Fix in Web

"item_count_text": "{count, plural, one{1 vare} other{# varer} }",
"backorder_count_text": "{count} vil være i restordre",
"backorder_quantities_changed_heading": "The backorder quantities have changed for below items:",
"cart_stock_modal_destination": "Destination #{consignmentNumber} ({address})",
Copy link

Choose a reason for hiding this comment

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

Multiple new strings left untranslated in all locales

Medium Severity

The newly added keys backorder_quantities_changed_heading, cart_stock_modal_destination, and qty_label are left in English across every non-English locale file (da, de, es-*, fr, it, ja, nl, no, pl, pt-BR, pt, sv). While some other new keys in this PR were properly translated, these three were not translated in any language, meaning non-English users will see English text in an otherwise localized UI.

Additional Locations (2)

Fix in Cursor Fix in Web

"backorder_quantities_changed_heading": "The backorder quantities have changed for below items:",
"cart_stock_modal_destination": "Destination #{consignmentNumber} ({address})",
"ready_to_ship_count_text": "{count} listo para enviar",
"show_backorder_details": "Detalles de la lista pendiente de los programas",
Copy link

Choose a reason for hiding this comment

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

LATAM Spanish "show backorder details" is a nonsensical mistranslation

Medium Severity

The show_backorder_details translation in all LATAM Spanish locales (es-419, es-AR, es-CL, es-CO, es-LA, es-MX, es-PE) reads "Detalles de la lista pendiente de los programas" — meaning "Details of the pending list of programs." This is nonsensical in context. The action verb "Show"/"Mostrar" is also missing. Compare with the correct Spain Spanish (es.json) translation: "Mostrar detalles de pedidos pendientes" ("Show pending order details"). The same locales also have a semantically drifted hide_backorder_details using "reservación pendiente" (pending reservation) instead of "pedidos pendientes" (backorders).

Additional Locations (2)

Fix in Cursor Fix in Web

"payment_method_invalid_error": "Det har oppstått et problem med å behandle betalingen din. Kontakt oss for å få hjelp, eller velg en annen betalingsmåte.",
"payment_method_unavailable_error": "Denne betalingsleverandøren er midlertidig utilgjengelig. Prøv igjen senere.",
"payment_not_required_text": "Betaling kreves ikke for denne bestillingen.",
"payment_methods_unavailable_error": "Vi kan ikke belaste betalingsmetodene for øyeblikket. Prøv igjen senere, eller kontakt butikken for å få hjelp.",
Copy link

Choose a reason for hiding this comment

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

Norwegian mistranslates "load" as "charge" for payment methods

Medium Severity

The Norwegian payment_methods_unavailable_error uses "belaste" (to charge/debit) instead of "laste inn" (to load). The translated message reads "We cannot charge the payment methods at the moment" instead of the intended "We cannot load the payment methods at the moment." Compare with the correct Swedish equivalent using "ladda" (load) and Danish using "indlæse" (load). This could mislead Norwegian users into thinking a charge was attempted.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant