Skip to content

OpenRCT2/Localisation

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Localisation

This repository is for the translation of OpenRCT2 into other languages.
For the main development and codebase of OpenRCT2, visit OpenRCT2/OpenRCT2.

OpenRCT2's base language is English (UK), this is updated and maintained in the main repository.
Other languages are maintained in this repository.
Changes to the master branch are merged into the develop branch of OpenRCT2/OpenRCT2 every day at 4:00 AM UTC.

Chat

Gitter
Gitter
Gitter

Build Status

AppVeyor

To contribute to the translation of OpenRCT2, you will need to fork this repository.
This allows you to edit and push changes of files to your fork so that you can then open a pull request.
For more information, visit GitHub's official forking guide.

Creating a new language

If you want to begin translating OpenRCT2 for a new language, create a new file in the data directory with the correct two letter language and country codes (e.g. cs-CZ), then paste the contents of the en-GB file into it and start translating the strings.

Maintainers & Maintaining languages

In each commit you create regarding a language file change, start the commit description (aka message) with the language and country code you're translating into, discussed in the previous paragraph (cs-CZ, es-ES, etc) (i.e. git commit -m "es-ES: Description of the commit" )

As this project always are moving forward, new strings get added from time to time which means they need to be added to the language files and be translated. All the new strings that are being added can be found in 'issues' on the localisation webpage here on GitHub. To be a maintainer means that you have to add the new strings found on the issues page into the language you're translating in numerical order.

If you want to become a maintainer, tell us what language you will maintain on Gitter

Checking & testing strings in-game

You can always test the translated strings in-game before publishing a pull request which could be good if the string has limited space/has a <newline> formating in it.
One simple way to test the new language is to copy the whole document you've translated and go to your games \OpenRCT2\data\language folder and paste the copied text into the language you want to test.

Language Status

Newest strings can be found in issues
Language Maintainer
Omaranwa
J0anJosep
octaroot
LPSGizmo
danidoedel, Wuzzy2
-Anyone-
Wirlie
JoelTroch
anon569
LucaRed
AaronVanGeffen
telk5093
Goddesen
Gymnasiast
renansimoes, Tupaschoal
Nubbie
BobbyS38
izhangfei
daihakken
Not maintained
en-US only contains strings that differ from en-GB

Note: The status bars can be inaccurate & some maintainers can be more inactive than others.
Anyone can still contribute to the languages.

Questions & Support

If you have any question or issues, please don't hesitate at contacting us at
Gitter