Skip to content
BranchesTags

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

LanguageNon DeveloperDeveloperLocalisation
EnglishDiscordDiscordDiscord
NederlandsDiscord

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 be maintaining on Discord.

Checking & testing strings in-game

You can always test the translated strings in-game before publishing a pull request. This can be especially handy to see if the strings fits the window.
To do this, go to the directory where OpenRCT2 resides (not to be confused with the directory where it saves your parks and config!), then go to data/language and replace the existing file with your updated version.

Language Status

Newest strings can be found in issues
LanguageMaintainer
Omaranwa
J0anJosep
LPSGizmo
Wuzzy2
-Anyone-
tellovishous
dimateos
groenroos
rmnvgr
LucaRed
telk5093
Goddesen
Gymnasiast
marcinkunert
Tupaschoal
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, you can always ask us on Discord.

Checking Translation Integrity

We have an action that automatically runs on every Pull Request and reports, for every supported language:

  • If there are any strings left to translate
  • If there are any strings that do not need translation
  • If there are any strings that might not have been translated, as they are the same

The script is on the repository and can be run locally if one wants to anticipate the results, by doing:

python .github\workflows\translation_check.py -r <path to en-GB.txt> -m <path to data/language folder on master branch> -b <path to data/language folder on your branch>

Note that -b and -m can use the same argument if you don't want differential analysis.

You can use the --help switch to read more about what each switch does.

About

Repository for translation and discussion for OpenRCT2.

Resources

Readme
Activity

Stars

0 stars

Watchers

1 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - J0anJosep/Localisation: Repository for translation and discussion for OpenRCT2. · GitHub
Skip to content
BranchesTags
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
LanguageNon DeveloperDeveloperLocalisation
EnglishDiscordDiscordDiscord
NederlandsDiscord
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 be maintaining on Discord.
Checking & testing strings in-game
You can always test the translated strings in-game before publishing a pull request. This can be especially handy to see if the strings fits the window.

To do this, go to the directory where OpenRCT2 resides (not to be confused with the directory where it saves your parks and config!), then go to data/language and replace the existing file with your updated version.
Language Status
Newest strings can be found in issues
LanguageMaintainer
Omaranwa
J0anJosep
LPSGizmo
Wuzzy2
-Anyone-
tellovishous
dimateos
groenroos
rmnvgr
LucaRed
telk5093
Goddesen
Gymnasiast
marcinkunert
Tupaschoal
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, you can always ask us on Discord.
Checking Translation Integrity
We have an action that automatically runs on every Pull Request and reports, for every supported language:
  • If there are any strings left to translate
  • If there are any strings that do not need translation
  • If there are any strings that might not have been translated, as they are the same
The script is on the repository and can be run locally if one wants to anticipate the results, by doing:
python .github\workflows\translation_check.py -r <path to en-GB.txt> -m <path to data/language folder on master branch> -b <path to data/language folder on your branch>

Note that -b and -m can use the same argument if you don't want differential analysis.
You can use the --help switch to read more about what each switch does.
About
Repository for translation and discussion for OpenRCT2.
Resources
Readme
Activity
Stars
0 stars
Watchers
1 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - J0anJosep/Localisation: Repository for translation and discussion for OpenRCT2. · GitHub
Skip to content
BranchesTags
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
LanguageNon DeveloperDeveloperLocalisation
EnglishDiscordDiscordDiscord
NederlandsDiscord
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 be maintaining on Discord.
Checking & testing strings in-game
You can always test the translated strings in-game before publishing a pull request. This can be especially handy to see if the strings fits the window.

To do this, go to the directory where OpenRCT2 resides (not to be confused with the directory where it saves your parks and config!), then go to data/language and replace the existing file with your updated version.
Language Status
Newest strings can be found in issues
LanguageMaintainer
Omaranwa
J0anJosep
LPSGizmo
Wuzzy2
-Anyone-
tellovishous
dimateos
groenroos
rmnvgr
LucaRed
telk5093
Goddesen
Gymnasiast
marcinkunert
Tupaschoal
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, you can always ask us on Discord.
Checking Translation Integrity
We have an action that automatically runs on every Pull Request and reports, for every supported language:
  • If there are any strings left to translate
  • If there are any strings that do not need translation
  • If there are any strings that might not have been translated, as they are the same
The script is on the repository and can be run locally if one wants to anticipate the results, by doing:
python .github\workflows\translation_check.py -r <path to en-GB.txt> -m <path to data/language folder on master branch> -b <path to data/language folder on your branch>

Note that -b and -m can use the same argument if you don't want differential analysis.
You can use the --help switch to read more about what each switch does.
About
Repository for translation and discussion for OpenRCT2.
Resources
Readme
Activity
Stars
0 stars
Watchers
1 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - J0anJosep/Localisation: Repository for translation and discussion for OpenRCT2. · GitHub
Skip to content
BranchesTags
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
LanguageNon DeveloperDeveloperLocalisation
EnglishDiscordDiscordDiscord
NederlandsDiscord
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 be maintaining on Discord.
Checking & testing strings in-game
You can always test the translated strings in-game before publishing a pull request. This can be especially handy to see if the strings fits the window.

To do this, go to the directory where OpenRCT2 resides (not to be confused with the directory where it saves your parks and config!), then go to data/language and replace the existing file with your updated version.
Language Status
Newest strings can be found in issues
LanguageMaintainer
Omaranwa
J0anJosep
LPSGizmo
Wuzzy2
-Anyone-
tellovishous
dimateos
groenroos
rmnvgr
LucaRed
telk5093
Goddesen
Gymnasiast
marcinkunert
Tupaschoal
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, you can always ask us on Discord.
Checking Translation Integrity
We have an action that automatically runs on every Pull Request and reports, for every supported language:
  • If there are any strings left to translate
  • If there are any strings that do not need translation
  • If there are any strings that might not have been translated, as they are the same
The script is on the repository and can be run locally if one wants to anticipate the results, by doing:
python .github\workflows\translation_check.py -r <path to en-GB.txt> -m <path to data/language folder on master branch> -b <path to data/language folder on your branch>

Note that -b and -m can use the same argument if you don't want differential analysis.
You can use the --help switch to read more about what each switch does.
About
Repository for translation and discussion for OpenRCT2.
Resources
Readme
Activity
Stars
0 stars
Watchers
1 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
GitHub - J0anJosep/Localisation: Repository for translation and discussion for OpenRCT2. · GitHub
Skip to content
BranchesTags
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
LanguageNon DeveloperDeveloperLocalisation
EnglishDiscordDiscordDiscord
NederlandsDiscord
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 be maintaining on Discord.
Checking & testing strings in-game
You can always test the translated strings in-game before publishing a pull request. This can be especially handy to see if the strings fits the window.

To do this, go to the directory where OpenRCT2 resides (not to be confused with the directory where it saves your parks and config!), then go to data/language and replace the existing file with your updated version.
Language Status
Newest strings can be found in issues
LanguageMaintainer
Omaranwa
J0anJosep
LPSGizmo
Wuzzy2
-Anyone-
tellovishous
dimateos
groenroos
rmnvgr
LucaRed
telk5093
Goddesen
Gymnasiast
marcinkunert
Tupaschoal
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, you can always ask us on Discord.
Checking Translation Integrity
We have an action that automatically runs on every Pull Request and reports, for every supported language:
  • If there are any strings left to translate
  • If there are any strings that do not need translation
  • If there are any strings that might not have been translated, as they are the same
The script is on the repository and can be run locally if one wants to anticipate the results, by doing:
python .github\workflows\translation_check.py -r <path to en-GB.txt> -m <path to data/language folder on master branch> -b <path to data/language folder on your branch>

Note that -b and -m can use the same argument if you don't want differential analysis.
You can use the --help switch to read more about what each switch does.
About
Repository for translation and discussion for OpenRCT2.
Resources
Readme
Activity
Stars
0 stars
Watchers
1 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - J0anJosep/Localisation: Repository for translation and discussion for OpenRCT2. · GitHub
Skip to content
BranchesTags
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
LanguageNon DeveloperDeveloperLocalisation
EnglishDiscordDiscordDiscord
NederlandsDiscord
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 be maintaining on Discord.
Checking & testing strings in-game
You can always test the translated strings in-game before publishing a pull request. This can be especially handy to see if the strings fits the window.

To do this, go to the directory where OpenRCT2 resides (not to be confused with the directory where it saves your parks and config!), then go to data/language and replace the existing file with your updated version.
Language Status
Newest strings can be found in issues
LanguageMaintainer
Omaranwa
J0anJosep
LPSGizmo
Wuzzy2
-Anyone-
tellovishous
dimateos
groenroos
rmnvgr
LucaRed
telk5093
Goddesen
Gymnasiast
marcinkunert
Tupaschoal
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, you can always ask us on Discord.
Checking Translation Integrity
We have an action that automatically runs on every Pull Request and reports, for every supported language:
  • If there are any strings left to translate
  • If there are any strings that do not need translation
  • If there are any strings that might not have been translated, as they are the same
The script is on the repository and can be run locally if one wants to anticipate the results, by doing:
python .github\workflows\translation_check.py -r <path to en-GB.txt> -m <path to data/language folder on master branch> -b <path to data/language folder on your branch>

Note that -b and -m can use the same argument if you don't want differential analysis.
You can use the --help switch to read more about what each switch does.
About
Repository for translation and discussion for OpenRCT2.
Resources
Readme
Activity
Stars
0 stars
Watchers
1 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
})();
GitHub - J0anJosep/Localisation: Repository for translation and discussion for OpenRCT2. · GitHub
Skip to content
BranchesTags
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
LanguageNon DeveloperDeveloperLocalisation
EnglishDiscordDiscordDiscord
NederlandsDiscord
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 be maintaining on Discord.
Checking & testing strings in-game
You can always test the translated strings in-game before publishing a pull request. This can be especially handy to see if the strings fits the window.

To do this, go to the directory where OpenRCT2 resides (not to be confused with the directory where it saves your parks and config!), then go to data/language and replace the existing file with your updated version.
Language Status
Newest strings can be found in issues
LanguageMaintainer
Omaranwa
J0anJosep
LPSGizmo
Wuzzy2
-Anyone-
tellovishous
dimateos
groenroos
rmnvgr
LucaRed
telk5093
Goddesen
Gymnasiast
marcinkunert
Tupaschoal
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, you can always ask us on Discord.
Checking Translation Integrity
We have an action that automatically runs on every Pull Request and reports, for every supported language:
  • If there are any strings left to translate
  • If there are any strings that do not need translation
  • If there are any strings that might not have been translated, as they are the same
The script is on the repository and can be run locally if one wants to anticipate the results, by doing:
python .github\workflows\translation_check.py -r <path to en-GB.txt> -m <path to data/language folder on master branch> -b <path to data/language folder on your branch>

Note that -b and -m can use the same argument if you don't want differential analysis.
You can use the --help switch to read more about what each switch does.
About
Repository for translation and discussion for OpenRCT2.
Resources
Readme
Activity
Stars
0 stars
Watchers
1 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages