OpenRCT2 / OpenRCT2/Localisation

Strings 6462-6468

Open
#2,284 0 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#16655.

STR_6462    :Excitement
STR_6463    :Excitement: {COMMA2DP32}
STR_6464    :Intensity
STR_6465    :Intensity: {COMMA2DP32}
STR_6466    :Nausea
STR_6467    :Nausea: {COMMA2DP32}
STR_6468    :Not Yet Known

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

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

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

Review the seven strings listed in issue 2284 and compare the completed locale entries with the untranslated ja-JP, tr-TR, and zh-CN entries. Provide translations for those locales, preserving the placeholders such as {COMMA2DP32}, then mark each completed locale in the issue checklist.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.