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

Hash autogenerated by build-languages task #703

Merged
merged 7 commits into from
Mar 14, 2017

Conversation

antoniopol06
Copy link
Contributor

No description provided.

@ipeychev
Copy link
Contributor

ipeychev commented Mar 7, 2017

@jbalsas, was that PR reviewed already by you? I don't know PoEditor, so it won't be easy for me to see if it fits its requirements.

@jbalsas
Copy link
Contributor

jbalsas commented Mar 7, 2017 via email

@ipeychev
Copy link
Contributor

ipeychev commented Mar 7, 2017

Ah, okay then. Great, let's manage this PR the next week.

Thanks,

@jbalsas
Copy link
Contributor

jbalsas commented Mar 14, 2017

Just started reviewing :)

:octocat: Sent from GH.

@jbalsas jbalsas merged commit 5f2926a into liferay:master Mar 14, 2017
@jbalsas
Copy link
Contributor

jbalsas commented Mar 14, 2017

Hey @ipeychev, I've reviewed, merged and pushed this to keep exploring the integration. In essence, this can be summarized as:

  • We have a src/ui/react/src/assets/lang/vendor/ckeditor.json file with the strings we want to grab from CKEditor
  • We have src/ui/react/src/assets/lang/{locale}.json files with our custom strings translated to the desired language
  • We have lib/lang/{locale.js} files with all the CKEditor lang strings out of the box

When building we hash those three sets and if it doesn't match the previous one, we proceed to update the generated language files by simply merging the translated keys in ckeditor.json and the corresponding {locale}.json.

We've also identified some edge cases in the build that we'll proceed to fix during the week.

@ipeychev
Copy link
Contributor

ipeychev commented Mar 14, 2017

Het @jbalsas, that's cool! My note and a small concern would be about the hash used there - it is SHA1, isn't it? SHA1 is obsolete and should be avoided. The library used in the code is able to generate hash using other algorithms too. You may think to change the algorithm to SHA256 or even use Node crypto directly.

Thanks,

@antoniopol06 antoniopol06 deleted the ae_702 branch March 16, 2017 07:48
@jbalsas
Copy link
Contributor

jbalsas commented Mar 16, 2017

Thanks for that tip, @ipeychev, we'll take a look to those!

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.

3 participants