"Not yet calculated" for the tax in the summary section in the checkout is not translatable

[rajeev-k-tomy]

Preconditions (*)

1. 2.2.3 (still present in 2.3-beta)
2. Those sites which uses more than 1 stores (languages).

Steps to reproduce (*)

1. Setup a two-store site where the default store uses "en_Us" as the language and the second store uses "es_ES" (Spanish ).

2. Add Spanish translation for the text: "Not yet calculated" through the design section. i.e, in the file: app/design/frontend/<Package>/<theme>/i18n/es_ES.csv.

    "Not yet calculated","Aún no calculado"
   

3. Now on the frontend, switch to Spanish store. Then add a product to the cart and go for checkout.

4. In the payment step, under the summary section, you will see "Not yet calculated" is not translated for the Tax eventhough the same text corresponding to Shipping is translated.

Expected result (*)

1. In the summary section in the checkout, we should see Aún no calculado for the Tax total.

Actual result (*)

1. But what we see there is Not yet calculated

Why this is happened

The issue occured because of there is no translation applied for the text: "Not yet calculated" in the UiComponent Magento_Tax/js/view/checkout/summary/tax.

This is how the text is called on the template. File: vendor/magento/module-tax/view/frontend/web/template/checkout/summary/tax.html

       <!-- ko ifnot: isCalculated() -->
            <span class="not-calculated" data-bind="text: getValue()"></span>
        <!-- /ko -->

So getValue() is providing the text here. So if we check in the component js file: vendor/magento/module-tax/view/frontend/web/js/view/checkout/summary/tax.js

return Component.extend({
    defaults: {
        ...
        notCalculatedMessage: 'Not yet calculated',
       ...
    },
    ...
    /**
     * @return {*}
     */
    getValue: function () {
        var amount;

        if (!this.isCalculated()) {
            return this.notCalculatedMessage;
        }
        amount = totals.getSegment('tax').value;

        return this.getFormattedPrice(amount);
    },
   ....

As you can see the text does not have any translations applied.

How can fix this?

Apparently adding translation in the component will fix the issue. Example is shown:

File: vendor/magento/module-tax/view/frontend/web/js/view/checkout/summary/tax.js

define([
    'ko',
    'mage/translate',
    'Magento_Checkout/js/view/summary/abstract-total',
    'Magento_Checkout/js/model/quote',
    'Magento_Checkout/js/model/totals'
], function (ko, $t, Component, quote, totals) {
    
    return Component.extend({
        defaults: {
            notCalculatedMessage: $t('Not yet calculated'),
        },
        ...
    });
});

Awaiting the response. Thank you. :)

[magento-engcom-team]

Hi @progammer-rkt. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

@progammer-rkt do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[magento-engcom-team]

Hi @anujwebkul. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

Hi @torhoehn. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

@torhoehn Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-96019, MAGETWO-96020 were created