@jlab-contrib/in-context-translation

jupyterlab_in_context_translation

A Jupyter extension to translate the web interface directly within the application using crowdin in-context. It works for both JupyterLab and Notebook.

Requirements

• A free crowdin account
  • Then join to the JupyterLab project
• JupyterLab >= 4.0.0 or Notebook >= 7.0.0

Install

To install the extension, execute:

pip install jupyterlab_in_context_translation

Usage

[!IMPORTANT] Be sure you have created an account on crowdin and joined the JupyterLab project see Requirements.

1. Pick the pseudo-language in the menu Settings -> Language
2. Acknowledge to save and reload the page
3. On reload, you will be prompted to pick the language you want to translate JupyterLab into and to log in crowdin
4. Start translating the string highlighted by a red border
   1. Hover the string to translate
   2. Click on the edit button that appear in the top left corner
   3. In the dialog, type the translation
   4. Click on Save button
5. To deactivate the feature, pick another language in the menu Settings -> Language

See also the video that illustrates those steps.

https://github.com/user-attachments/assets/bfe0e93b-d55c-4b29-a45e-e82f9aad3757

Uninstall

To remove the extension, execute:

pip uninstall jupyterlab_in_context_translation

Contributing

Development install

Note: You will need NodeJS to build the extension package.

The jlpm command is JupyterLab's pinned version of yarn that is installed with JupyterLab. You may use yarn or npm in lieu of jlpm below.

# Clone the repo to your local environment
# Change directory to the jupyterlab_in_context_translation directory
# Install package in development mode
pip install -e "."
# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite
# Rebuild extension Typescript source after making changes
jlpm build

You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.

# Watch the source directory in one terminal, automatically rebuilding when needed
jlpm watch
# Run JupyterLab in another terminal
jupyter lab

With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).

By default, the jlpm build command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:

jupyter lab build --minimize=False

Development uninstall

pip uninstall jupyterlab_in_context_translation

In development mode, you will also need to remove the symlink created by jupyter labextension develop command. To find its location, you can run jupyter labextension list to figure out where the labextensions folder is located. Then you can remove the symlink named @jlab-contrib/in-context-translation within that folder.

Testing the extension

Frontend tests

This extension is using Jest for JavaScript code testing.

To execute them, execute:

jlpm
jlpm test

Integration tests

This extension uses Playwright for the integration tests (aka user level tests). More precisely, the JupyterLab helper Galata is used to handle testing the extension in JupyterLab.

More information are provided within the ui-tests README.

Packaging the extension

See RELEASE

Changelog

1.0.0

(Full Changelog)

Enhancements made

• Ensure jupyterlab server compatibility #6 (@fcollonval)
• Load the crowdin in-context script #1 (@fcollonval)

Maintenance and upkeep improvements

• Change NPM package scope to jlab-contrib #7 (@fcollonval)

Documentation improvements

• Mention it works for notebook v7 too #5 (@fcollonval)
• embedded the video in README #4 (@fcollonval)

Contributors to this release

(GitHub contributors page for this release)

@fcollonval | @github-actions

<!-- <END NEW CHANGELOG ENTRY> -->