Hello,

I have a problem with translation method. Example:

1. "Order" translation in Drupal Core (in Hungarian: "Sorrend")
2. "Order" translation in Drupal Commerce (in Hungarian: "Rendelés")

The problem: Sorrend != Rendelés

Order (Sorrend) translation is correct in Drupal Core context, but incorrect in Drupal Commerce context.

Translation Reference:
https://localize.drupal.org/translate/languages/hu/translate?sid=22144

CommentFileSizeAuthor
incorrect_translation.png11.42 KBecrazor
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ecrazor created an issue. See original summary.

ecrazor’s picture

ecrazor CreditAttribution: ecrazor commented
Issue summary: View changes

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Sutharsan’s picture

Sutharsan CreditAttribution: Sutharsan at LimoenGroen commented

This same problem exists in Dutch.
We should first decide which context should be the default and which the exception. Sort order or purchase order.

In core I find 'Order' (as single string) being used in the context of sort order in:
- template_preprocess_field_multiple_value_form
- \Drupal\views\Plugin\views\sort\SortPluginBase::showSortForm

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

mstrelan’s picture

mstrelan CreditAttribution: mstrelan at PreviousNext commented
Status: Active » Postponed (maintainer needs more info)
Issue tags: +Bug Smash Initiative
Related issues: +#1035716: [policy, no patch] Decide and document guidelines for using string context

I reviewed this as part of the Bug Smash Initiative.

According to the Internationalization documentation there is already a way to provide context to string translations.

In fact there are a number of places in core that provide "Sort order" as the context for the string "Order".

In order to progress this issue we need more information on how to reproduce the issue. Is there a particular usage of the word "Order" that does not have the right context provided? Does commerce need to provide context to differentiate it?

It may also be useful to refer to #1035716: [policy, no patch] Decide and document guidelines for using string context.

mstrelan’s picture

mstrelan CreditAttribution: mstrelan at PreviousNext commented

Further to #15 I see Commerce order entities uses the string context "Commerce". I suspect you may need to just ensure the correct context is used for the translation.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

smustgrave CreditAttribution: smustgrave at Mobomo commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

Since there hasn't been a follow up to #15 going to close this one as outdated.

If still a bug please reopen, maybe updating issue summary.

Thanks all!