OpenRCT2 / OpenRCT2/Localisation
String 6628
Open
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#21980.
STR_6628 :Can only be placed on path edges!
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:
@Omaranwa @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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the STR_6628 entry and the repository's existing translation conventions. Complete the unchecked locale translations listed in the issue, then verify that STR_6628 is present and correctly formatted for each updated language.
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
- 55/100