Japanese translation: terms, catalogs and layout

Open
#707 0 comments 0 reactions 0 assignees View on GitHub

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

enhancement

Japanese (ja) as the first language after en-US (decision 101, M4). The maintainer reviews every message.

  1. 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).
  2. Catalogs: locales/ja/ with ui.ftl, common.ftl, cli.ftl and notify.ftl, drafted by an AI in reviewable batches. Each pull request gives every message's English back-translation and flags any uncertain phrasing.
  3. Layout: line-break: strict, word-break: auto-phrase where the browser has it, the system's Japanese fonts; the @ui journeys under ja (CJK widths, wrapping, no clipped text).
  4. 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

  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 nledford/Ladderback

All issues in nledford/Ladderback

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.