OpenRCT2 / OpenRCT2/Localisation

String 6435

Open
#2,158 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

new field
Dominant language
No language data
Stars
72
Forks
213
Avg merge
10h 33m
Merged PRs (30d)
20

Description

New strings from PR OpenRCT2/OpenRCT2#14071

STR_6435    :{WINDOW_COLOUR_2}Vandals stopped: {BLACK}{COMMA16}

Updated in:

  • ar-EG
  • ca-ES
  • cs-CZ
  • da-DK
  • de-DE
  • en-US
  • eo-OO
  • es-ES
  • fr-FR
  • hu-HU
  • it-IT
  • ja-JP
  • ko-KR
  • nb-NO
  • nl-NL
  • pl-PL
  • pt-BR
  • sv-SE
  • tr-TR
  • zh-CN
  • zh-TW

Notification when new strings arrive:
@Omaranwa @J0anJosep @octaroot @LPSGizmo @danidoedel @Wuzzy2 @tellovishous @rzhao271 @Wirlie @JoelTroch @anon569 @LucaRed @AaronVanGeffen @telk5093 @Goddesen @Gymnasiast @renansimoes @Tupaschoal @izhangfei @daihakken @marcinkunert

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating STR_6435 in the localisation files and review the existing translations and formatting tokens. Translate the string for one or more unchecked locales in the issue checklist, preserving the placeholders; done means the selected locale entries are updated consistently.

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
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.