Chinese UI still shows English error messages in the design system import flow

[shangxinyu1]

Summary

When the system/UI language is Chinese, the error message is still shown in English.

Current behavior

The interface is in Chinese, but the validation/error message under the design system import field appears in English.

Expected behavior

When the app is running in Chinese, user-facing error messages should also be localized to Chinese.

This includes:

• validation errors
• import failures
• inline form error messages
• other user-facing status/error text in the same flow

Steps to reproduce

1. Use the app with Chinese system/UI language.
2. Open the Design System settings/import flow.
3. Trigger an import error.
4. Observe that the error message is displayed in English instead of Chinese.

Notes

• The screenshot shows a Chinese UI with an English inline error message.
• This appears to be an i18n/localization coverage issue.
• Paths or raw technical details may remain untranslated when necessary, but the surrounding user-facing explanation should be localized.

Why this matters

Mixed-language error messages feel inconsistent and reduce clarity for users who are working in a Chinese UI. Localizing user-facing errors would make the product feel more complete and easier to understand.

[lefarcen]

This is open for community help.

If you'd like to work on it, comment /claim below. The first /claim after the latest release gets it. Any comment, linked PR, or progress note keeps the claim active.

[lefarcen]

Hey @shangxinyu1, thanks for the detailed repro and screenshot — the mixed Chinese/English state in the Design Systems import form is a real i18n coverage bug.

I traced the likely path: the Settings → Design Systems import form is already localized for labels/buttons, but when import fails it renders result.error.message directly from the daemon. The daemon currently returns English validation strings for path/import failures, so Chinese UI users can see those raw English messages.

I labeled this bug, help wanted, and good first issue because the fix looks scoped: add localized UI-side handling for design-system import failures, keep raw paths/technical details where useful, and cover both local and GitHub import failure paths. Related context: #426 was a similar i18n coverage gap, and #2205 is broader Simplified Chinese localization work.

[arseniy-gl]

/claim

Taking this. UI-only fix:

• In apps/web/src/components/DesignSystemsSection.tsx:242, destructure code alongside error and map BAD_REQUEST / INTERNAL_ERROR to new localized keys; fall back to raw error.message for unknown codes.
• New keys (settings.designSystemsImportErrorInvalid, settings.designSystemsImportErrorInternal, optional per-message variants) added to types.ts and all 20 locales per the i18n contract.
• Same setXxxError(result.error.message) anti-pattern also exists in apps/web/src/components/SkillsSection.tsx:360,394 — flagging as adjacent.

One quick question before I start: keep the raw error.message text visible after the localized prefix (e.g. "Could not import: "), or replace it entirely with the localized string (raw still available in DevTools / diagnostics)?

Estimated time: a few hours.

[lefarcen]

Hey @arseniy-gl, thanks for picking this up. A few hours noted — we’ll time the check-ins around that.

[arseniy-gl]

PR #6075 is up for this.

The fix maps the daemon error code to a new i18n key and shows a localized summary instead of the raw English message. The raw daemon detail (path / URL) stays under a <details> disclosure so diagnostics still work.

Three new keys added to types.ts and all 19 locale files. Red spec in DesignSystemsSection.test.tsx confirms the Chinese UI no longer shows the raw English error.

Also flagging: the same raw-English pattern exists in SkillsSection.tsx:360,394 — will file a separate follow-up issue for that.

[lefarcen]

PR #6075 is up for this now. It takes the UI-side route discussed here: map the known daemon error codes to localized Settings strings, keep the raw path/URL detail available under a <details> disclosure, and add regression coverage for the Chinese import-error case.

Keeping #2686 open until the PR lands and the fix ships.