OpenRCT2 / OpenRCT2/Localisation
Strings 6499, 6500
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 72
- Forks
- 213
- Avg merge
- 10h 33m
- Merged PRs (30d)
- 20
Description
New strings from PR OpenRCT2/OpenRCT2#17499.
STR_6499 :Vehicle type not supported by track design format
STR_6500 :Track elements not supported by track design format
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
- 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 by locating the ja-JP and tr-TR translation entries corresponding to STR_6499 and STR_6500, using the listed English strings as the reference. Add translations for both locales and update the checklist when both entries are complete.
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
- 45/100