Localization workflow share

[goanpeca]

Hello everyone! the localization work in JLab has been carried by a few folks and I would like to make a 30-minute meeting to share the overall view of the full workflow, answer any questions, and comment on work to be done.

Next week I will be working on updating documentation, adding examples, and moving jupyterlab-git to use localization as a POC of how extensions can update their code and share it to be translated with crowdin.

Most of the afternoons are available and I created a doodle to see what time can fit the largest amount of people.

https://doodle.com/poll/2cbk8pt8h6pqvbgx

Tip: Use the calendar view to make it easy to select several time slots.

Timezone is Bogotá/Colombia (I think US Central is currently aligned with this)

Anyone interesting in learning more or/and helping with the missing parts is welcome :-)

Cheers!

[choldgraf]

I almost certainly wont be able to make a meeting due to my new 👶 but would love to see some documentation etc about this. We should also loop in @parente at some point since he has done a lot of great work with transifex in the jupyter docs.

[goanpeca]

Congrats on the new 👶 @choldgraf !

but would love to see some documentation etc about this.

Trying to get all pieces in place soon!

We should also loop in @parente at some point since he has done a lot of great work with transifex in the jupyter docs.

Sure thing, maybe we can set up another meeting to go over how to unify efforts. Would that be ok @parente?

Cheers!

[krassowski]

Any thoughts on whether extensions should require ITranslator, or should it be optional? Is it safe to assume that all lab-components-based apps since 3.0 will provide ITranslator (thinking about at jupyterlab-classic kind of initiatives)?

[krassowski]

Is there a recording or another documentation for how to translate extensions? Also looking towards integrating spellchecker dictionaries, but I feel lost among many repositories, tools and lots of code to digest.

[jtpio]

Is it safe to assume that all lab-components-based apps since 3.0 will provide ITranslator (thinking about at jupyterlab-classic kind of initiatives)?

In a way having the ITranslator a required dependency can be a good way to "force" distribution authors to provide support for translation from the very beginning.

It's also possible to start small on this and provide a temporary simplified plugin, for example in jupyterlab-classic:

https://github.com/jtpio/jupyterlab-classic/blob/027f8f515fc142e76edf8dc3c7701c030aeb776b/packages/application-extension/src/index.ts#L417-L428

Before implementing full support for localization, which might just mean reusing the upstream JupyterLab translation plugin.