Rebuild the pseudo-translation .mo on every --pseudo-translation run

Open Beginner friendly
#3,607 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
localization

Research direction

Start with devsupport/pseudo-translation/generate_pseudo_translation.py and trace the --pseudo-translation and --pseudo-translation-bidi entry points to see where the pre-generated .mo is loaded. Run the relevant pseudo-translation command against current source strings and verify that each invocation rebuilds the catalog and includes newly added translatable strings.

Written by the indexing model from the issue text.

Description

--pseudo-translation/--pseudo-translation-bidi rely on a pre-generated .mo (devsupport/pseudo-translation/generate_pseudo_translation.py), which goes stale as new translatable strings are added - e.g. translate/virtaal#1492's own new "Language:" string was missing from it during testing.

Rebuilding is cheap - worth just regenerating it on every --pseudo-translation run instead of relying on a stale pre-built one, so it's always in sync with the current source without a separate manual regen step.

🤖 Generated with Claude Code

Dominant language
Python
Stars
304
Forks
61
Avg merge
6h 30m
Merged PRs (30d)
240

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.

More from translate/virtaal

All issues in translate/virtaal

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.