-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
js-translation.json is not generated #3771
Comments
Known problem: #2056 |
Hi @jaimestuardo I have tried translations with latest develop branch and I can say almost all phrases are translated. Could you please use develop branch and let us know if this issue persists? Otherwise we can close :) |
@antboiko please review and create ticket if needed |
Hi @jaimestuardo , I've created internal ticket MAGETWO-54632 to investigate this. Thanks, |
Hi, @antboiko! I can confirm this issue still persist in 2.1.3 version. However in |
As a workaround it seems that deleting js-translation.json from pub/static/frontend/Magento/[theme]/[lang_code]/ allows "setup:static-content:deploy [lang_code]" to correctly generate the file. |
We have internal ticket MAGETWO-61923 for ver. 2.1 |
@jaimestuardo thank you for the report. The issued fixed in MAGETWO-59042 and available in 2.2.0 |
It still does not work on Magento 2.2. My js-translation.json contains only "[]" |
… [GITHUB PR#4814] #3771
[TSG-CSL3] For 2.2 (pr21)
Does still not work in Magento 2.4.4 |
I have Magento2 localized to es_ES. Translations work partially.
First of all, I have generated the CSV using Magento2 way but some translations were not included in CSV file.
Well.. for those non-translated sentences, I have being adding to the file manually.
The problem I always have is that js-translation.json file were not generated automatically. So I have created it manually and copied inside i18n/[company]/es_es/ folder, in the same location as CSV file.
With that action, that json file were copied automatically to pub/static folder, but today, I did that again, but it is impossible the json file to be copied.
I think this a bug in translation system.
Any workaround on this?
By the way. I am in development mode, with full cache disabled.
Regards
Jaime
The text was updated successfully, but these errors were encountered: