Skip to content

Offer: Spanish translation of the Orange interface (3.40.0) #7352

Open

Description

@dhinostroza

Hello,

I teach medical informatics in the Hematology specialty program at Universidad Indoamérica (Ecuador), and my students use Orange in class. To make it easier for them, we prepared a Spanish (Latin American) translation of the Orange 3.40.0 interface, and we would like to offer it to the project.

What it covers

  • orange-canvas-core: 467 of 469 strings
  • orange-widget-base: 117 of 117
  • orange3: 3,782 of 4,138 (the rest are intentionally left in English: widget names, algorithm names, search keywords, and strings that are identical in Spanish)

How it was made and checked

  • A machine translation (a local open-weights LLM) with a fixed glossary and style rules (formal "usted", sentence case).
  • An automatic validator for every string: placeholders ({}, %s, %(name)s), HTML tags, keyboard accelerators (&), line breaks, and leading/trailing whitespace are preserved; translated f-strings compile and reference the same variables; pl() forms use "singular|plural" where Spanish needs it.
  • 65 manual corrections, plus a test that instantiates all 105 widgets with the translation, with no errors.
  • It still needs a review by a second native speaker, which we would welcome.

Format
It is ready as Trubar message files, i18n/es/msgs.jaml, for the three repositories at the tags that ship with Orange 3.40.0 (orange3 3.40.0, orange-widget-base 4.27.0, orange-canvas-core 0.2.7), together with the es entry for each trubar-config.yaml.

  • The structure follows i18n/si/msgs.jaml; every entry marked false there is kept false.
  • trubar translate builds all three without errors.
  • The resulting Spanish.json matches, string by string, the translation we tested inside Orange.
  • Only one multi-line entry is still null: the template of the About dialog, in orange-canvas-core.

Questions

  1. Would you accept a Spanish translation?
  2. Should I open pull requests with i18n/es/msgs.jaml against master (after running trubar collect there), or would you prefer the files for 3.40.0 as they are?
  3. Is there anything you require from translation maintainers, for example keeping it updated for new releases?

I am happy to maintain it for future versions.

Thank you for Orange; it works very well for teaching clinicians.

Daniel Hinostroza
Universidad Indoamérica, Ecuador

Activity

  1. dhinostroza commented on Oct 26, 2026

    @dhinostroza
    Author

    For context on maintenance: I was the Spanish translator for phpMyAdmin for about 10 years, so I'm used to keeping a translation in sync with new releases and reviewing it for consistency over time. I'd be glad to do the same for Orange.

  2. janezd commented on Oct 26, 2026

    @janezd
    Contributor
    1. Would you accept a Spanish translation?

    Yes! This would be great!

    1. Should I open pull requests with i18n/es/msgs.jaml against master (after running trubar collect there), or would you prefer the files for 3.40.0 as they are?

    Please open PRs with msgs.jaml and all other necessary files. The release is built using these files, not the translated sources.

    1. Is there anything you require from translation maintainers, for example keeping it updated for new releases?

    This would of course be desirable. :) Orange is released once or twice a year and is not changing a lot lately, so it should not be too much of a burden.

    We are preparing a new release in a few weeks. If you have everything ready and feel confident enough without a second reviewer, we can already include Spanish.

    P. S. 👍 for formal "usted". I did the same for Slovenian. Perhaps I'm old. :)

  3. dhinostroza commented on Oct 26, 2026

    @dhinostroza
    Author

    Thank you! I’ll prepare the PRs against master for the three repositories (orange3, orange-widget-base, orange-canvas-core) and will keep the translation updated for future releases. I’m a native speaker and have reviewed it, so I’m comfortable including it in the upcoming release; corrections from other Spanish speakers will of course be welcome.

  4. dhinostroza commented on Oct 26, 2026

    @dhinostroza
    Author

    The pull requests are ready:

    Each adds i18n/es/msgs.jaml, collected against current master, and registers es in trubar-config.yaml. Details are in the PR descriptions.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions