String 7050-7063

Open
#3,540 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
content, internationalization, localization

Research direction

No file or test is named. Locate the translation files for the unchecked locales, compare their entries for STR_7050 through STR_7063 with the provided English strings, and follow the repository’s existing translation conventions. Done means the applicable locale translations are added and the checklist is updated.

Written by the indexing model from the issue text.

Description

new field

New strings from PR OpenRCT2/OpenRCT2#27061.

These strings are used in the Guest List window.

STR_7050    :Guests walking
STR_7051    :Guests heading for {STRINGID}
STR_7052    :Guests queuing for {STRINGID}
STR_7053    :Guests drowning
STR_7054    :Guests on {STRINGID}
STR_7055    :Guests in {STRINGID}
STR_7056    :Guests at {STRINGID}
STR_7057    :Guests sitting
STR_7058    :Guests picked up
STR_7059    :Guests watching {STRINGID}
STR_7060    :Guests watching construction of {STRINGID}
STR_7061    :Guests looking at scenery
STR_7062    :Guests leaving the park
STR_7063    :Guests watching new ride being constructed

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
  • vi-VN
  • zh-CN
  • zh-TW

Notification when new strings arrive:
@OmarAglan @J0anJosep @tygrysek90 @LPSGizmo @Wuzzy2 @tellovishous @dimateos @Davis-3450 @rmnvgr @ninjum @LucaRed @telk5093 @Gymnasiast @arekdurlik @Tupaschoal @andOlga @mrmagic2020 @daihakken

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

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.

More from OpenRCT2/Localisation

All issues in OpenRCT2/Localisation

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.