Translating JSLab

Languages

JSLab’s interface ships in English, Spanish, Japanese, Chinese and Portuguese. Choose one with Language in Settings → General; System follows your Mac. JSLab has to restart to apply a change, and tells you so.

Only English is complete. The Spanish, Japanese, Chinese and Portuguese files hold a small seed of draft strings, a few dozen keys each out of more than 900, limited to short, unambiguous labels such as menu titles, settings tab names and the core verbs. No native speaker has reviewed them yet. Everything else falls back to English on purpose.

Terms of art such as Auto Log, magic comment, logpoint and loop protection are deliberately left untranslated in those seeds. A confidently wrong translation of one is worse than English, because a reader can’t tell which strings to distrust.

Suggest a correction

If a translated label reads wrong, or you’d like to help with a language, write to [email protected] with the text you see, where it appears and your suggested wording. Anything not yet translated falls back to English on purpose.

What JSLab doesn’t translate

• Theme and font names, such as Graphite, Dracula and JetBrains Mono. They’re proper nouns.
• Values in the output panel, such as undefined, null and Invalid Date. They’re JavaScript’s own notation, and translating them would make the output disagree with the runtime.
• Key names such as Space, Home and PgUp, which label physical keys.