Public docs

Guide: Global Language Selection

How locale is resolved, persisted, and rendered across SerenQuant web routes as localization expands beyond English and Korean.

URL policy: no locale path prefixes. Routes remain stable.
Resolution order: user profile locale > sq_locale cookie > Accept-Language > default en-US.
Supported locales: en-US, en-GB, zh-CN, zh-TW, zh-HK, ja-JP, ko-KR, de-DE, pt-BR, fr-FR, es-ES, es-419, hi-IN with alias normalization for common regional variants.
Persistence: unauthenticated users store locale in cookie; authenticated users persist to profile and cookie.
Formatting: display-only number/date formatting follows active locale; backend timestamps remain UTC.
Fallback: unsupported locale values are canonicalized to default locale without request failure, and untranslated locales use the English message catalog until dedicated translations land.
Quality gates: key parity, hardcoded-literal guard, and runtime smoke are required in release CI.

Last updated

Mar 24, 2026

Feedback

Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.

Last updated

Mar 24, 2026

Feedback

Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.

Public docs

How locale is resolved, persisted, and rendered across SerenQuant web routes as localization expands beyond English and Korean.

URL policy: no locale path prefixes. Routes remain stable.
Resolution order: user profile locale > sq_locale cookie > Accept-Language > default en-US.
Supported locales: en-US, en-GB, zh-CN, zh-TW, zh-HK, ja-JP, ko-KR, de-DE, pt-BR, fr-FR, es-ES, es-419, hi-IN with alias normalization for common regional variants.
Persistence: unauthenticated users store locale in cookie; authenticated users persist to profile and cookie.
Formatting: display-only number/date formatting follows active locale; backend timestamps remain UTC.
Fallback: unsupported locale values are canonicalized to default locale without request failure, and untranslated locales use the English message catalog until dedicated translations land.
Quality gates: key parity, hardcoded-literal guard, and runtime smoke are required in release CI.

Last updated

Mar 24, 2026

Feedback

Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.

Last updated

Mar 24, 2026

Feedback

Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.