OVOS Localize Tutorial

This guide is for first-time contributors who want to translate OVOS skills.

Goal

By the end of this tutorial, you will know how to:

  1. Set your languages
  2. Change languages later from the top-right menu
  3. Choose a skill that needs help
  4. Open the translation editor
  5. Submit your contribution

Before You Start

  • Open the live platform in your browser
  • You do not need coding experience
  • You should have a GitHub account (needed when submitting your translation)

Scenario 1: First Setup (Choose Your Languages)

Click the top-right Set languages button to choose your language before starting.

  1. Open OVOS Localize.
  2. Click the Set languages button in the top-right corner of the header.
  3. Select one or more languages you can translate.
  4. Click save/continue.
  1. Header showing the top-right Set languages button
  2. Language selection modal with checkboxes

Choose the language(s) you know.

Scenario 2: Change Languages Later (Top Right)

  1. In the header, click the top-right button labeled Set languages.
  2. Search for a language in the search box.
  3. Check or uncheck languages.
  4. Save changes.

Scenario 3: Choose a Skill

  1. Go to the Dashboard page.
  2. Use Search skills... to find a specific skill, or browse cards.
  3. Pick a skill card.
  4. Click a language badge on that card (for example pt-PT).
  1. Dashboard with skill cards visible

Tip: Red badges usually indicate the language needs more translation work.

Scenario 4: Open the Editor and Translate

  1. After choosing a skill and language, the editor opens.
  2. Read the English source text on the left.
  3. Write your translation in the center editor.
  4. Use the context panel on the right to understand usage.
  1. 3-panel editor (source, translation editor, context panel)
  2. Edited translation text before submission

Scenario 5: Submit Your Translation

  1. Click the submit button in the editor.
  2. A GitHub issue page opens with pre-filled data.
  3. Click Submit new issue on GitHub.
  4. Automation creates a pull request for maintainers to review.
  1. Submit action from editor
  2. GitHub new issue page with pre-filled translation data

Quality Checklist

  • Keep placeholders like {name} exactly unchanged.
  • Preserve line meaning from source.
  • Keep punctuation and formatting where required.
  • For .voc files, keep terms concise.
  • For .dialog files, write natural spoken language.

Common Problems

I cannot find my language

  • In the language modal, click Can't find your language? Request it.
  • Submit the request form.

I selected the wrong language

  • Click Set languages in the top-right header and update your selection.

I am not sure what a line means

  • Use the right-side context panel in the editor.
  • Open the skill README when available.

Quick Path (30 Seconds)

  1. Click Set languages
  2. Choose your language
  3. Open Dashboard
  4. Choose a skill card and language badge
  5. Translate lines
  6. Submit on GitHub