Skip to content

i18n: disambiguate Computer Use Type and Key labels - #2530

Open
YspritanHyzygy wants to merge 1 commit into
osaurus-ai:mainfrom
YspritanHyzygy:i18n/split-computer-use-type-key
Open

i18n: disambiguate Computer Use Type and Key labels#2530
YspritanHyzygy wants to merge 1 commit into
osaurus-ai:mainfrom
YspritanHyzygy:i18n/split-computer-use-type-key

Conversation

@YspritanHyzygy

@YspritanHyzygy YspritanHyzygy commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Summary

The Computer Use diagnostics panel reused the generic Type and Key localization keys. In Simplified Chinese, those generic terms correctly refer to a category and a credential elsewhere, but they produced 类型 and 密钥 in this action inspector.

This change gives the typing action and keyboard-key field dedicated localization keys, so each label can be translated for its actual context without changing unrelated uses. It also clarifies the Simplified Chinese Press key action as 按下按键.

New German, Korean, and Russian entries remain marked needs_review for native review.

Changes

  • Adds dedicated localization keys for the Computer Use typing action and keyboard-key field
  • Preserves the existing generic Type and Key translations in unrelated contexts
  • Clarifies the Simplified Chinese Press key action as 按下按键

Test Plan

Tested source: f3b3b8b8

  • bash scripts/i18n/check.sh
  • Compiled Localizable.xcstrings for en, de, zh-Hans, zh-Hant, ko, and ru with xcstringstool
  • Built the Release app on macOS with Xcode 27 beta; the vMLX pin remained b52ddf1
  • Opened Settings > Computer Use > Advanced > Diagnostics in an isolated Simplified Chinese Release app and verified:
    • the Type action displays 输入
    • the keyboard-key field displays 按键
    • the Press key action displays 按下按键

Model bundle, generation defaults, and eval scores are not applicable to this localization-only change.

Screenshots

Not attached; the labels were verified in an isolated local Release build.

Checklist

  • I have read CONTRIBUTING.md
  • No unit test was added; String Catalog validation and direct UI verification cover the changed behavior
  • No documentation update is needed for these label corrections
  • I verified the build on macOS with Xcode 16.4+

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant