OpenRCT2 / OpenRCT2/Localisation
Strings 1171, 1172, 1730, 2981, 6308
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 72
- Forks
- 213
- Avg merge
- 10h 33m
- Merged PRs (30d)
- 20
Description
Changed strings from PR OpenRCT2/OpenRCT2#8659:
-STR_1171 :{RED}Closed - -
-STR_1172 :{YELLOW}{STRINGID} - -
+STR_1171 :{RED}Closed
+STR_1172 :{YELLOW}{STRINGID}
-STR_1730 :{RED}Closed - -
+STR_1730 :{RED}Closed
-STR_2981 :{RED}No entry - -
+STR_2981 :{RED}No entry
New strings from PR OpenRCT2/OpenRCT2#8659:
STR_6308 :“{STRINGID}{OUTLINE}{TOPAZ}”{NEWLINE}{STRINGID}
Updated in:
- ar-EG
- ca-ES
- cs-CZ
- da-DK
- de-DE
- en-US
- es-ES
- fr-FR
- hu-HU
- it-IT
- ja-JP
- ko-KR
- nb-NO
- nl-NL
- pt-BR
- sv-SE
- tr-TR
- zh-CN
- zh-TW
Notification when new strings arrive:
@Nubbie @Goddesen @octaroot @telk5093 @Omaranwa @danidoedel @LPSGizmo @BobbyS38 @frenchiveruti @anon569 @JoelTroch
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the locale entries for STR_1171, STR_1172, STR_1730, STR_2981, and STR_6308 and compare them with the changes from PR OpenRCT2/OpenRCT2#8659. Check the three unchecked locales, ar-EG, tr-TR, and zh-CN, and mark the work done when their entries reflect the requested string changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- localization
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100