Chinese support — product surface and compatibility matrix¶

Status: Proposed scope contract
Purpose: Prevent “Chinese support” from being treated as one boolean. Each YazSes surface has its own implementation dependency, validation method, and release state.

Legend:

• P1 — intended first-class Mandarin scope.
• Conditional — can be P1 only if its named blocker is cleared.
• Existing primitive — low-level support exists already but still needs end-to-end validation.
• Deferred — deliberately outside P1.

Product surfaces¶

Injection matrix¶

A recognizer passing CER does not certify text delivery.

Use this exact fixture family, preserving mixed Han/Latin/digits/punctuation:

Simplified: 你好，世界。简体中文测试 123，YazSes。
Traditional: 你好，世界。繁體中文測試 123，YazSes。
Mixed: 今天 review PR #378，然后保存文件。

Each report records OS/session, backend selected, target app, expected string, actual string, and whether fallback was used. No usernames, home paths, hostnames, clipboard contents unrelated to the fixture, or private dictated text are committed.

Language-profile matrix¶

Postprocessor audit matrix template¶

CHN-30 must fill this from code, not assumptions:

A row cannot be marked safe solely because it did not throw an exception.

Support wording rule¶

Documentation should name the actual green cells rather than say only “Chinese supported.”

Example after a partial successful gate:

Mandarin hold-to-talk and file transcription are validated for Simplified and Traditional output on Windows, macOS and Linux X11. Wayland uses clipboard fallback. Chinese Meeting Mode remains experimental while its transcript-quality metrics are being validated.

That wording is more useful and more durable than a single support badge.