OpenRCT2 / OpenRCT2/Localisation

Strings 6733–6734

Open
#3,056 1 comment 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#23759.

STR_6733    :See-Through
STR_6734    :Map elements that are at or above the cutting height are rendered translucent.

Updated in:

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

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

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 the locale files for the unchecked languages and checking how STR_6733 and STR_6734 are represented in the completed locales. Translate both strings for each remaining locale, then mark the corresponding checklist entries when all requested languages are updated.

Written by the indexing model from the issue text.

Assessment

Domain
localization
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.