Translation Not working in change password in frontend

[KishorkumarKar]

Hi

Preconditions

I have Magento 2.1.7 with two store English Spanish After login in front end in Spanish Store. I Tried to change password the From validation text not translated correctly. I have tried to translate Inline it is not working.

Steps to reproduce

1. Login to front end .
2. Go to account information
3. Change the store (language in spanish)
4. Change Password
5. type 123 in ** Current Password , New Password**
6. Look into the error message

Expected result

Error mesage tranlated to spanish

Actual result

Go to account information type 123 in ** Current Password , New Password**

Its is not translated in Spanish. It is not working for other combination also

[dmanners]

I had this problem when dealing with multiple stores. When building that static content I needed to run the command once for each language. As I understand this is/will be fixed in 2.2.0 or maybe even 2.1.9 but for older versions running the command once for each locale should sort this.

php bin/magento setup:static-content:deploy --theme=Your/theme --theme=Magento/backend en_US
php bin/magento setup:static-content:deploy --theme=Your/theme --theme=Magento/backend de_DE

I think it is related to #7862

[KishorkumarKar]

Hi,
I have done that but not working

[dmanners]

Hmm, ok I assume that that string is actually in the translation pack. Also it might be a good idea on your local machine to remove all the static files and re-run the setup:static-content:deploy command just to make sure there are no left over translations.

[orlangur]

Does it happen for any JS translation or just this one? #10913 fix may be worth trying also.

[KishorkumarKar]

It works in another place But not working here.
I have done as @dmanners said ut not working.

[hostep]

Sound more like a duplicate of #5509, which should get fixed by #10747 which is probably going to be included in Magento 2.1.10. The fix is also already included in version 2.2.0-rc3.0 (by f67e598).

[magento-engcom-team]

Hi @KishorkumarKar
Thank you for your report.
This bug is duplicate #5509.