Japanese translation: terms, catalogs and layout
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- css
Research direction
Start with the glossary in §3.1 and PRODUCT.md for tone, then read the existing en-US catalogs under locales/ to mirror their structure in locales/ja/ui.ftl, common.ftl, cli.ftl and notify.ftl; the translation workflow's check script defines what counts as complete. The layout part lives in the styles applying line-break: strict and word-break: auto-phrase, verified through the @ui journeys run under ja. Done means the workflow check passes for ja and a run with LANG=ja_JP.UTF-8 and [agent] locale = "ja" shows unclipped text. This spans many reviewed PRs, so it is not a single sitting.
Written by the indexing model from the issue text.
Description
Japanese (ja) as the first language after en-US (decision 101, M4). The maintainer reviews every message.
- Terms first: the glossary (§3.1) as Fluent terms in
ja(-snapshot,-repository,-plan,-agent,-hub, forget, prune, …), with a short rationale for each choice, reviewed before any message uses them. Polite form (です・ます), calm and exact (PRODUCT.md). - Catalogs:
locales/ja/withui.ftl,common.ftl,cli.ftlandnotify.ftl, drafted by an AI in reviewable batches. Each pull request gives every message's English back-translation and flags any uncertain phrasing. - Layout:
line-break: strict,word-break: auto-phrasewhere the browser has it, the system's Japanese fonts; the@uijourneys underja(CJK widths, wrapping, no clipped text). - CLI and notifications under
ja(LANG=ja_JP.UTF-8;[agent] locale = "ja").
Done when: Japanese is complete and current by the translation workflow's check and the release offers it.
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yantrikos/yantrik-os#1272 ·
Maintainers usually reply within 1 day
-
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 ·