scratchfoundation / scratchfoundation/scratch-blocks

script to copy new strings to translated language files

Open
#2,038 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

developer facing enhancement Low Prevalence Low Severity priority 4
Dominant language
JavaScript
Stars
2.8k
Forks
1.6k
Avg merge
4h 51m
Merged PRs (30d)
12

Description

There should be a script that developers can run after they add or revise strings, which will add their string to all of the translated language files, so scratch-blocks will run safely even before new translations are pulled from transifex.

Related to https://github.com/LLK/scratch-blocks/issues/1820

Contributor guide

Open the contributing guide

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 the translated language files and the related issue #1820 to understand how strings are currently organized and synchronized. The work is done when developers can run a script after adding or revising strings and every translated language file contains the new string as a safe fallback before Transifex updates arrive.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
localization, tooling
Issue type
Feature
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.