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

Make this extension localizable and test translation infrastructure for extensions #727

Closed
goanpeca opened this issue Aug 13, 2020 · 5 comments · Fixed by #888
Closed

Make this extension localizable and test translation infrastructure for extensions #727

goanpeca opened this issue Aug 13, 2020 · 5 comments · Fixed by #888

Comments

@goanpeca
Copy link
Member

No description provided.

@fcollonval
Copy link
Member

@goanpeca could you please provide more information on :

  • how to make the extension localized
  • where to define the various translation (is it in this project, in a separated one, in the jupyterlab one)?
  • how to distribute the translations

@goanpeca
Copy link
Member Author

Hi @fcollonval sure thing.

So there are two parts, frontend and backend. I will explain in more detail what is needed. I can open a small PR to illustrate what needs to be done :)

@fcollonval
Copy link
Member

So there are two parts, frontend and backend. I will explain in more detail what is needed. I can open a small PR to illustrate what needs to be done :)

That would be awesome - thanks!

@JessicaBarh
Copy link
Contributor

Hi @goanpeca and @fcollonval,

I'm working on a PR for this and so far I've followed a similar concept as the changes made to the jupyterlab packages on this commit. What I can't figure out is the po file (how would that be generated) and if there are any other backend or frontend stuff that need to be done.
If you can open such PR that would be super helpful, thank you!

@fcollonval fcollonval linked a pull request Mar 17, 2021 that will close this issue
@fcollonval
Copy link
Member

Closing this one as the work was mainly done in #888. Remaining translation holes are tracked in #1023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants