Translations Help

Why 'adopt' a language?

R6Maps.com is designed to support multiple languages for nearly every feature (ironically though this page is English only :).  If you use the site and speak another language (or have enough patience), please consider helping create translations.

Translations are needed for general terms like the side menu and stats functionality. However, map room labels take most time: about 9-12 hours currently for all maps & about one hour per season after.  Of course you will be thanked on the about page, and your work will benefit many other users!

NOTE: You do not need to be a coder to provide translations!  You can enter translations in a spreadsheet or enter them directly in code, depending on your comfort level.

Step 1: Pick a Language

The about page contains a list of languages that need to be translated. Some languages only need ongoing help, such as for new maps or new site features while others would be new for the site.

Please email r6maps@gmail.com to indicate if you can help with a language.

You will then be added as a contributor to the shared spreadsheet, or a placeholder column will be added if you are entering translations directly in code.  Although it is possible for multiple people to work on a language together, this will help reduce the chances of wasted duplicate effort.

Google Doc Link

Step 2 - Option A: Enter terms in a spreadsheet

If you are not familiar with modifying website code:

You can enter translations directly in a Google spreadsheet.  After emailing r6maps@gmail.com (see "step 1" above), you will be added as a contributor to the Google spreadsheet.  Please review the notes in the spreadsheet and email any questions you may have.

NOTE: For both Step 2 options, some care should be taken to try to match translations to what appears in-game.

Step 2 - Option B: Enter terms in code

If you are comfortable with modifying website code and Github pull requests:

You can enter translations directly in code, previewing changes in real-time while running the site locally.  The code is available here on Github.  Please review the README for some instructions on running the site locally (you will need to install npm and build some javascript files).

Additionally, there is an example PR here that you can use as a reference for files that need to be updated. It may become out of date but can hopefully still be used as a helpful example.

Step 3: Spread the word :)

Once the new language is available on the live site, please consider posting about it - especially on sites where users speak the new language.  This will help more users benefit from your hard work!

Also, you will be asked to provide a name (or handle if you prefer) and link, so that you can be credited for your effort.  You can refer to existing thank you notes on the about page for examples.

Thank you for considering helping out!