Skip to content

Fix multilang wysiwyg #7

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

Merged
merged 2 commits into from
Jun 26, 2013
Merged

Fix multilang wysiwyg #7

merged 2 commits into from
Jun 26, 2013

Conversation

ehsavoie
Copy link
Member

Translated wysiwyg were not stored correctly in database (before JCR time) as translations Thus you could have many wysiwyg for a singe publication each with its own language extension. So now if a wysiwyg has not language defined in database, we use the extension to compute the real language of the content. When we have different wysiwyg attachmentswith the same name (except for the _lang extension) we merge them in a single SimpleDocument, eachbeing a translation.

Emmanuel Hugonnet added 2 commits June 12, 2013 10:01
…time) as translations

Thus you could have many wysiwyg for a singe publication each with its own language extension.
So now if a wysiwyg has not language defined in database, we use the extension to compute the real language of the content.
When we have different wysiwyg attachmentswith the same name (except for the _lang extension) we merge them in a single SimpleDocument, eachbeing a translation.
@ehsavoie ehsavoie merged commit 59386c6 into Silverpeas:master Jun 26, 2013
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

Successfully merging this pull request may close these issues.

1 participant