Translation workflow: list missing and stale messages, and offer only complete languages
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 40/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- ci-cd, localization, tooling
Research direction
Start in crates/l10n/locales/ to see how per-language message files and recorded source hashes are stored, then find the existing just recipes and the language-negotiation code that decides which locales are offered. Add a recipe that compares recorded hashes against current en-US text and reports missing and stale messages, then gate offering a language on completeness and currency in release builds. Done when editing an en-US message makes the recipe list its translations as stale and a release check rejects an offered incomplete language.
Written by the indexing model from the issue text.
Description
Decision 101's tooling, so a translation can be kept current (Japanese first, #704 later).
- Source hashes:
crates/l10n/locales/<tag>/keeps, for each message, a hash of theen-UStext it was translated from (value and attributes together). Writing a translation records the hash; nothing else edits the file by hand. - A
justrecipe lists, per language, the messages that are missing and the ones whoseen-UStext changed since (stale), with the old and new English for each stale one. - Offered languages: a language is built but not offered (negotiation skips it) until it is complete and current; development builds offer it for review, as they do the pseudolocales.
- CI listing (its own PR, a CI change): every pull request prints the list without failing; not a required check.
- Release check (its own PR, a CI change): the release pull request's checks refuse a release that offers a language with a missing or stale message (§12.1).
Done when: changing an en-US message marks its translations stale in the recipe's output, and a release can't offer an incomplete language.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 56m
- Merged PRs (30d)
- 349
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from nledford/Ladderback
-
bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
nledford/Ladderback#809 ·
Maintainers usually reply within 1 day
-
bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nledford/Ladderback#759 ·
Maintainers usually reply within 1 day
-
enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nledford/Ladderback#746 ·
Maintainers usually reply within 1 day
-
enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nledford/Ladderback#745 ·
Maintainers usually reply within 1 day
-
bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nledford/Ladderback#647 ·
Maintainers usually reply within 1 day
All issues in nledford/Ladderback
Similar issues
-
crate: spate-kafka priority: low tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
macOS 菜单栏托盘图标保留橙色,与系统单色图标风格不一致Possibly taken @xhugoliu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YizhengWw/HachimoDock#56 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area:ui bug effort:low P2 source:agent
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day