OpenRCT2 / OpenRCT2/Localisation

String 6646–6647

Open
#2,868 6 comments 0 reactions 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#20952.

STR_6646    :Author: {STRING}
STR_6647    :Authors: {STRING}

Updated in:

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

Notification when new strings arrive:
@OmarAglan @J0anJosep @LPSGizmo @Wuzzy2 @gr33ndev @tellovishous @dimateos @groenroos @rmnvgr @LucaRed @telk5093 @Mmmmulder @Gymnasiast @marcinkunert @Tupaschoal @CsyeCokTheSolly @LPR-Michael @mrmagic2020 @daihakken

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 finding the locale files for the unchecked languages and inspect how nearby string entries are translated. Add translations for STR_6646 and STR_6647 where needed, then update the corresponding checklist entries when the translations are complete.

Written by the indexing model from the issue text.

Assessment

Domain
localization
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.