OpenRCT2 / OpenRCT2/Localisation

Review translated technical strings

Open
#3,314 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

There are some strings which we consider to not be "translatable" due to only containing technical code for putting up numbers or colors, etc. However, some language maintainers have felt the need to translate them and as such we keep nagging on the translation report that they are "unneeded" when they are actually (supposedly) translated on purpose.

On #3309 @tygrysek90 introduced a way to suppress the warnings for these strings that were translated on purpose. The action here is to review this file for your language and either:

  1. Add these strings to the suppression file
  2. Remove these translated strings from your language

Once we get good traction, it might even serve a purpose to notice that a given string we thought should be ignored is actually being picked up by everyone.

Reviewed 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 @rmnvgr @ninjum @LucaRed @telk5093 @Gymnasiast @arekdurlik @Tupaschoal @andOlga @mrmagic2020 @daihakken

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 with the attached translated_technical_strings.txt and review the entries for one unchecked language. For each entry, either add it to .github/workflows/suppress_warning.py when the translation is intentional, or remove it from that language; the language's checklist item is done when all entries have been reviewed.

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.