mirror of
https://github.com/multica-ai/multica.git
synced 2026-08-05 09:30:05 +02:00
e3bf9ccd43
* feat(i18n): translate issue as the local word for "task" (MUL-5703) zh-Hans 任务, ja タスク, ko 태스크 across the app locales, the landing dictionaries, and the onboarding issue templates. "issue" has no meaning in any of these languages outside dev jargon; the everyday task word is what users already say for this. The agent execution run is a separate user-visible entity, so it keeps a distinct spelling per locale — zh `task` (unchanged), ja 作業, ko 작업 — and never collapses into the same word as the issue. Untouched: API/DB fields, `multica issue` CLI references, the /issue Slack and Lark slash command, English feature names in the changelog archive, and "issue" in the machine-health sense (异常 / 問題 / 문제). conventions.mdx and conventions.zh.mdx carry the new rule so translation PRs stop reverting to English. Co-authored-by: multica-agent <github@multica.ai> * fix(i18n): finish the run/issue split in the landing copy (MUL-5703) Renaming issue to 任务 / タスク / 태스크 left the agent execution run sharing that word in the landing dictionaries — zh.ts had "任务表格" (issue) and "智能体任务" (run) in one sentence. The run now reads `task` / 作業 / 작업 there too, matching the app locales. Each string was classified against its EN counterpart at the same structural path, so "assign tasks" in the hero (which means issues) stays 任务 while "agent tasks" in the changelog becomes the run word. Strings EN cannot disambiguate were decided by hand. Also: the onboarding starter prompts spelled the concept list `workspace / issue / agent / runtime` while the next prompt in the same file already used the new word, and the ja/ko VCS settings copy was still untranslated English showing "issues" on the settings page. Co-authored-by: multica-agent <github@multica.ai> * fix(i18n): keep Chinese fixed compounds, tidy ja/ko grammar (MUL-5703) 后台任务 and 定时任务 are settled Chinese compounds for "background job" and "cron job" — neither is the agent execution entity, so splitting them into `task` was wrong. Japanese: the landing file spaces katakana-katakana compounds, so replacing タスク with kanji 作業 left "エージェント 作業" and "作業 トークン" reading oddly. Reworded to の / closed compounds. Korean: 작업 ends in a consonant, so the subject marker after the parenthetical becomes 이, not 가. Also drops a __pycache__ artifact that git add -A swept in, and ignores Python bytecode so agent tooling cannot commit it again. Co-authored-by: multica-agent <github@multica.ai> --------- Co-authored-by: Lambda <lambda@multica.ai> Co-authored-by: multica-agent <github@multica.ai>