Skip to content

chore: zh-TW translation grammatical polishing + sort keys same as en.json#1489

Open
dawnFirefly wants to merge 3 commits intoTecharoHQ:mainfrom
dawnFirefly:patch-1
Open

chore: zh-TW translation grammatical polishing + sort keys same as en.json#1489
dawnFirefly wants to merge 3 commits intoTecharoHQ:mainfrom
dawnFirefly:patch-1

Conversation

@dawnFirefly
Copy link

Reworded several strings to sound more natural and fluent in written Chinese, reducing the "machine-translated" impression.
Main examples:

  • js_done_took: "花費" (spend) → "花了" (took, more idiomatic in this context)

  • static_check_endpoint: "這是提供給…" → "這只是提供給…" (Add the missing "just" from original English text)

  • Minor rephrasing in longer explanations for better flow and readability

  • Key order alignment
    Reordered translation keys to exactly match the sequence in en.json.
    This makes side-by-side comparison and future maintenance much easier.

Helps make the zh-TW experience feel more polished and human-written.

Checklist:

  • Added a description of the changes to the [Unreleased] section of docs/docs/CHANGELOG.md
  • Added test cases to the relevant parts of the codebase
  • Ran integration tests npm run test:integration (unsupported on Windows, please use WSL)
  • All of my commits have verified signatures

Signed-off-by: Dawn Firefly <30818360+dawnFirefly@users.noreply.github.com>
@dawnFirefly dawnFirefly changed the title zh-TW translation grammatical polishing + sort keys same as en.json chore: zh-TW translation grammatical polishing + sort keys same as en.json Feb 27, 2026
@Xe
Copy link
Contributor

Xe commented Mar 21, 2026

I'm likely going to have to rename the locales to zh-Hans (what I have as zh-CN) and zh-Hant (what I have as zh-TW). It's causing localization library headaches otherwise.

Xe and others added 2 commits March 21, 2026 20:13
…fix an issue

Signed-off-by: Xe Iaso <me@xeiaso.net>
Signed-off-by: Dawn Firefly <30818360+dawnFirefly@users.noreply.github.com>
@dawnFirefly
Copy link
Author

Sure, I fix the merge conflict too

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants