Github user djKooks commented on the issue:
https://github.com/apache/zeppelin/pull/544
@corneadoug Oh okay, I see. Thanks for the guide.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/544
@djKooks Not sure it would make a difference.
In the way it is implemented, each language already have its own .js file.
And inside, the translations are set as an object/json format.
--
Github user djKooks commented on the issue:
https://github.com/apache/zeppelin/pull/544
@corneadoug Good job!
One more suggestion, how about putting multi language resource into json
files to manage easily? Maybe it could be easy to update for who wants to
support translation stri
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/544
Closing this PR, there would be too much to rebase, better make a new one
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
