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

[QUESTION] Support multiple languages for the page content #2380

Closed
varadero opened this issue Nov 6, 2019 · 4 comments
Closed

[QUESTION] Support multiple languages for the page content #2380

varadero opened this issue Nov 6, 2019 · 4 comments

Comments

@varadero
Copy link

varadero commented Nov 6, 2019

What we need is to create a page once but translate the text content in multiple languages. Imagine a very simple sample of a single text block saying "Hello" - we don't want to force the users to create another page with that same text block saying the same in different language. Imagine the page must be translated in 10 languages and the page has 20 text blocks - it would be too hard to do and maintain clones of the page containing the same components with just different texts (adding new text field would require adding it in every clone, which is something that nobody will do). Is there any way to do this with current GrapesJS like a drop-down which switches between different "sets" of text content so the user can choose a language and then go and change the text content for that language of whatever components he wants ?

I was thinking of storing the "data" object on StoreManager's "store" function on language change, but this will not work well if the user switches the language and adds new component - then the current language object and all other language objects will become different (other language objects not having the new component added for the current language).

@pouyamiralayi
Copy link

@varadero i18n module is on the roadmap
cheers!

@varadero
Copy link
Author

varadero commented Nov 6, 2019

@pouyamiralayi But isn't that i18n mentioned there just a module that will allow you to translate GrapesJS itself, not the content that the user created ?

@pouyamiralayi
Copy link

pouyamiralayi commented Nov 6, 2019

@varadero please take a look at this

@varadero
Copy link
Author

varadero commented Nov 6, 2019

Closing s duplicate of #2342

@varadero varadero closed this as completed Nov 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants