pokerogue/docs/localization.md

Localization 101

PokéRogue's localization team puts immense effort into making the game accessible around the world, supporting over 10 different languages at the time of writing this document. As a developer, it's important to help maintain global accessibility by effectively coordinating with the Translation Team on any new features or enhancements.

This document aims to cover everything you need to know to help keep the integration process for localization smooth and simple.

Stupid Assumptions

Before you continue, this document assumes:

• You have already forked the repository and set up a development environment according to the respository README.

• You have a basic level of familiarity with Git commands and GitHub repositories.
• You have joined the community Discord and have access to #dev-corner and related channels via #select-roles. This is the easiest way to keep in touch with both the Translation Team and other like-minded contributors!

About the pokerogue-locales submodule

PokéRogue's translations are managed under a separate dedicated repository, pokerogue-locales. This repository is integrated into the main one as a git submodule within the public/locales folder.

What Is a Submodule?

In essence, a submodule is a way for one repository (i.e. pokerogue) to use another repository internally (pokerogue-locales). From the perspective of the main project, the locales submodule is fairly simple to work with, but there are some important commands to keep in mind.

Fetching Changes from Submodules

Once you have set up your fork or whenever it gets out of date, run the following command to integrate the latest locales changes into your branch:

git submodule update --init --recursive

¹

This is run automatically after merge or switching branches, so you usually won't have to run it manually in most cases.

How Are Translations Integrated?

This project uses the i18next library to integrate translations from public/locales into the source code based on the user's settings or location. The basic process for fetching translated text goes as follows:

1. The source code fetches text by a given key, e.g.

   i18next.t("fileName:keyName", { arg1: "Hello", arg2: "an example", ... })
   

2. The game looks up the key in the corresponding JSON file in the user's language, e.g.

   // from "en/file-name.json"...
   "keyName": "{{arg1}}! This is {{arg2}} of translated text!"
   

   If the key doesn't exist for the user's language, the game will default to the corresponding English key.
3. The game shows the text to the user:

   "Hello! This is an example of translated text!"
   

Submitting locales changes.

If you have a feature or enhancement that requires additions or changes to in-game text, you will need to make a fork of the pokerogue-locales repo and submit your text changes as a pull request to that repo in addition to your pull request to the main project. Since these two PRs aren't technically linked, it's important to coordinate with the Translation Team to ensure that both PRs are integrated safely into the project.

Requirements for Adding Translated Text

When your new feature or enhancement requires adding a new locales key without changing text in existing keys, we require the following workflow with regards to localization:

1. You (the developer) make a pull request to the main repository for your new feature. If this feature requires new text, the text should be integrated into the code with a new i18next key pointing to where you plan to add it into the locales repository. DO NOT HARDCODE PLAYER-FACING TEXT INTO THE CODE!
2. You then make another pull request -- this time to the pokerogue-locales repository -- adding a new entry with text for each key you added to your main PR.

• You only need to change English keys when making the PR; the Translation Team will take care of the rest.
• For any feature pulled from the mainline Pokémon games (e.g. a Move or Ability implementation), it's best practice to include a source link for any added text. Poké Corpus is a great resource for finding text from the mainline games; otherwise, a video/picture showing the text in mainline should suffice.
• You should also [notify the current Head of Translation](#Notifying Translation) to ensure a fast response.

3. At this point, you may begin [testing locales integration in your main PR](#Filming Locales Changes).
4. The Translation Team will approve the locale PR (after corrections, if necessary), then merge it into pokerogue-locales.
5. The Dev Team will approve your main PR for your feature, then merge it into PokéRogue's beta environment.

Requirements for Modifying Translated Text

PRs that modify existing text have different risks with respect to coordination between development and translation, so their requirements are slightly different:

• As above, you set up 2 PRs: one for the feature itself in the main repo, and another for the associated locales changes in the locale repo.
• Now, however, you need to have your main PR be approved by the Dev Team before your corresponding locale changes are merged in.
• After your main PR is approved, the Translation Team will merge your locale PR, and you may update the submodule and post video evidence of locale integration into the locales PR.

Filming Locales Changes

After making a PR involving any outwards-facing behavior (but especially locales-related ones), it's generally considered good practice to attach a video of those changes working in-game.

Basic procedure:

1. Update your locales submodule to use the latest locales from the remote. Many code editors with git integration allow for checking out submodules directly from the UI, or you can run git submodule update --remote --recursive.

• If the locales PR hasn't been

2. Set some of the in-game overrides inside overrides.ts to those corresponding to the Moves and Abilities being tested.
3. Start a local dev server (npm run start:dev).
4. Film the locales change being displayed in the recording software of your choice².

Here are a few guidelines to bear in mind when recording:

• 1 change = 1 video. GitHub has a hard 10mB limit on video uploads, so prefer splitting individual interactions into individual recordings.
• Keep videos short. Nobody wants to watch a 5-minute film for 10 seconds of content. Around 1 turn of content is good enough.

Notifying Translation

Put simply, stating that a PR exists makes it much easier to review and merge.

The easiest way to do this is by pinging the current Head of Translation in the Discord (ideally in #dev-corner or similar).

The current Head of Translation is:

** @lugiadrien **

Closing Remarks

If you have any questions about the developer process for localization, don't hesitate to ask! Feel free to contact us on Discord - the Dev Team and Translation Team will be happy to answer any questions.

---

1. If you run into issues with your development environment afterwards, try deleting the .git/modules/public and public/locales folders before re-running the command. ↩︎

2. For those lacking a screen capture device, OBS Studio is a popular open-source option. ↩︎