Translate "This is a required field" and validation errors on 2.3

[verdde]

Summary (*)

Magento 2.3 vanilla with 2 store views

I've installed multiple language packs, currently using this one
https://github.com/EaDesgin/magento2-romanian-language-pack

Everything is translated except the JS validation errors.

Examples (*)

For example :
"This is a required field."

Static deploy is ok generating static files correctly. We can find the translation in mage_translation via cache.

Checked validations.js and entire project and seems string is defined correctly:
$.mage.__('This is a required field.')

Expected results (*)

Translation should display instead of original string "This is a required field."

Behaviour existing on Magento 2.3 vanilla.

Same behaviour found on 2.2.6

Proposed solution (*)

Translation should be loaded normally.

[magento-engcom-team]

Hi @verdde. 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 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@verdde 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 @engcom-backlog-nazar. 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

• Next steps are available in case you are a member of Community Maintainers.

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

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

Hi @verdde thank you for you report, i'm not able to reproduce following steps you described,

[verdde]

@engcom-backlog-nazar

Could you please explain how you did the translation ? Did you tested on multiple store views for a specific language/locale ?

I've tried everything i knew/could and it still doesn't work.

As it should in i18n/test/fr_fr/fr_FR.csv exported the string list translated with no success. Checked theme for bugs or missing strings, found none.

I would greatly appreciate it.

Thank you !

[verdde]

@magento-engcom-team
@engcom-backlog-nazar
@engcom-backlog-tomash
@engcom-backlog-nickolas
Please reopen the ticket this is affecting everyone i am working with and it's using Magento 2.3

Just tested on new M2.3 and the issue is still there.

[kevinvuillemin]

I have same problem, did you find a solution please ?