All user-facing strings emitted by the Bor server and agent should be translatable. This includes log messages intended for operators, error messages returned to clients, and any status or notification text surfaced to end users through the agent.
Scope covers identifying all currently hardcoded strings, extracting them into a translation catalog, and wiring up a standard i18n mechanism (e.g. go-i18n or equivalent) with English as the source locale. Locale selection should be configurable per deployment, with a reasonable fallback to English when a translation is missing.
Strings that are purely internal (debug logs, developer-facing traces) are out of scope for now.
All user-facing strings emitted by the Bor server and agent should be translatable. This includes log messages intended for operators, error messages returned to clients, and any status or notification text surfaced to end users through the agent.
Scope covers identifying all currently hardcoded strings, extracting them into a translation catalog, and wiring up a standard i18n mechanism (e.g. go-i18n or equivalent) with English as the source locale. Locale selection should be configurable per deployment, with a reasonable fallback to English when a translation is missing.
Strings that are purely internal (debug logs, developer-facing traces) are out of scope for now.