OpenRCT2 / OpenRCT2/Localisation

[Idea] Automatically mark translations as done

Open
#2,000 1 comment 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

Currently adding new translations involves creating a checklist with all the supported languages and marking it as done after a PR has been merged. This has a few drawbacks:

  • the PR reviewer has to manually go to given issue and the language as done
  • the PR creator has to make sure he/she points to an issue
  • some issues are already translated but they are not marked as done

I'm wondering if this could be automatized. After a translation would be added to given language on master branch a script should go through all issues and mark them as done. If all translations are done it should be closed.

This involves probably some changes in the issue formatting and/or creating one issue per translation but maybe(?) it could be done and would be a nice quality of life improvement.

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 by reviewing how translation issues are formatted and how translation changes reach the master branch. Define how added languages would be detected, how existing checklist items would be updated, and when an issue should close. Done means the process handles already translated languages and removes the need for manual checklist updates.

Written by the indexing model from the issue text.

Assessment

Domain
localization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.