Skip to content
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

Closed
jaimestuardo opened this issue Mar 14, 2016 · 10 comments
Closed

js-translation.json is not generated #3771

jaimestuardo opened this issue Mar 14, 2016 · 10 comments
Assignees
Labels
Area: Frontend bug report Fixed in 2.2.x The issue has been fixed in 2.2 release line Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@jaimestuardo
Copy link

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

@jaimestuardo jaimestuardo changed the title js-translatin.json is not generated js-translation.json is not generated Mar 14, 2016
@thomvanderboon
Copy link

Known problem: #2056

@antboiko antboiko added the PS label Mar 15, 2016
@hshar7
Copy link
Contributor

hshar7 commented Apr 6, 2016

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 :)

@piotrekkaminski
Copy link
Contributor

@antboiko please review and create ticket if needed

@antboiko
Copy link

Hi @jaimestuardo , I've created internal ticket MAGETWO-54632 to investigate this.

Thanks,
Anton.

@antboiko antboiko added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development and removed Progress: needs update labels Jun 22, 2016
@vkorotun vkorotun removed the PS label Aug 4, 2016
@avra911
Copy link

avra911 commented Jan 16, 2017

Hi, @antboiko!

I can confirm this issue still persist in 2.1.3 version. However in developer mode seems fine, while in production mode the generated file js-translation.json contains only []. Maybe this can help.

@ekupelian
Copy link

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.

@veloraven
Copy link
Contributor

We have internal ticket MAGETWO-61923 for ver. 2.1

@magento-engcom-team magento-engcom-team added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development bug report Area: Frontend Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed labels Sep 11, 2017
@magento-engcom-team
Copy link
Contributor

@jaimestuardo thank you for the report. The issued fixed in MAGETWO-59042 and available in 2.2.0

@magento-engcom-team magento-engcom-team added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Sep 20, 2017
@pitangaweb
Copy link

It still does not work on Magento 2.2. My js-translation.json contains only "[]"

@Eddcapone
Copy link

Does still not work in Magento 2.4.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend bug report Fixed in 2.2.x The issue has been fixed in 2.2 release line Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Development

No branches or pull requests