Skip to content

workHubHelp copy disagrees across en, zh-CN, and zh-TW #5289

Open
Lxr-max/maka
#1

Description

@heeoneie

What happened

workHubHelp in apps/desktop/src/renderer/locales/settings-preferences-copy.ts says three different things across the three locales, and the two versions describe opposite situations — one says the feature is unusable, the other describes what it does.

locale line value
zh-CN 336 WorkHub 目前仍不可用。此开关仅供开发测试,开启后也不能保证正常使用。
zh-TW 435 在一個入口檢視已有工作,並將新輸入保守地送往普通任務。
en 491 WorkHub is not available yet. This toggle is for development testing and does not enable a usable feature.

I do not know which one is right, and that is the question here. Either WorkHub is still unavailable and the zh-TW string needs replacing, or it has since become usable and it is en/zh-CN that are stale. Someone who knows the current state of the feature has to say which.

How to reproduce

grep -o "workHubHelp: '[^']*'" apps/desktop/src/renderer/locales/settings-preferences-copy.ts

Then open Settings → Chat defaults with the interface language set to each of the three locales and compare the help text under the WorkHub toggle.

Environment

Not runtime-specific. Present on main and on stack/i18n-ko-core; the strings above are read from a193ad8d1.

Logs, screenshots, or additional context

How the three came apart

Nobody did anything wrong here — it is ordinary merge-order drift between two pull requests:

So #3853 branched before #3935 landed, translated the copy that was current at the time, and merged a week later. Git does not flag that as a conflict, because the two pull requests touched different lines of the same object.

The chronology is worth stating plainly, because it cuts the other way from what a reader might assume: zh-TW is the most recently committed of the three, so “the newest one is right” does not settle it either.

Scope

workHubHelp is the only key affected. #3935 changed exactly two lines in this file, and comparing every key on those lines before and after shows workHubHelp as the only entry whose value differs — 14 keys on the zh-CN line and 44 on the en line are otherwise identical.

Why this is being filed separately

Found while building the Korean glossary for #3977 (desktop slice 1), which covers this file. It is out of that issue's scope — slice 1 adds a ko catalog and does not change existing locales — and resolving it needs a product answer about WorkHub rather than a translation decision, so it should not be folded into a translation pull request.

Once the intended wording is settled I am happy to fix it, including the ko string, so slice 1 does not add a fourth variant.

cc @AcerYue0, who wrote the zh-TW catalog in #3853 and will know what the source text looked like at that point.


Claude Opus 5 assisted with the investigation and this write-up. Every line number, commit, and string above was read from a local checkout.

Activity

  1. AcerYue0 commented on Sep 14, 2026

    @AcerYue0
    Contributor

    Suggested revision:

    • Clarify that the Traditional Chinese copy was outdated rather than merely “stale.”
    • Use wording consistent with the English and Simplified Chinese versions.
    • Consider revising the Traditional Chinese text to:

      WorkHub 目前仍停用。此開關僅供開發測試,啟用後也不保證能正常運作。

    • Retain the note that the locale hygiene check passes.
  2. SummerC0zyR0ck commented on Sep 14, 2026

    @SummerC0zyR0ck
    Contributor

    I dug into this and I think the tree plus the history already answer it — recording the evidence here, with the caveat that the intended wording is a product statement, so I'd like @ARE404 and @likun666661 to confirm.

    Reading current main:

    So the intended text today looks like the en/zh-CN "not available yet" copy, and the zh-TW string added by #3853 (2026-09-04) translated the pre-#3935 source — which is why it reads as a description of a usable feature.

    Proposed resolution: replace zh-TW's workHubHelp with a Traditional Chinese rendering of the current en/zh-CN text, and make any upcoming ko string follow the same source, so all locales stay in step.

  3. hbw00111 commented on Sep 14, 2026

    @hbw00111
    Contributor

    take

  4. Lxr-max commented on Sep 15, 2026

    @Lxr-max

    take

  5. github-actions commented on Sep 15, 2026

    @github-actions

    Issue #5289 is already assigned to hbw00111, so it was not reassigned.

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

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions