fix(i18n): refine zh-TW localization

[nrps9909]

Summary

Fixes #8938.

This updates 54 Traditional Chinese (Taiwan) UI values after reviewing them one by one against the en-US source and their UI context. The patch only changes the canonical frontend/resources/translations/zh-TW.json file.

Highlights:

• correct a semantic mistranslation where the local-AI description duplicated its title instead of describing PDF chat, writing help, and table autofill
• fix the malformed <email/>> placeholder rendering and the Simplified Chinese character in 不确定
• improve authentication and password-reset messages while preserving the intended line breaks
• replace non-Taiwan terms such as 用戶, 網絡, 圖標, 鏈接, 代碼, and 優先級 with established Taiwan usage
• keep interpolation placeholders, message references, tags, keys, and data types unchanged

Existing open PRs #8815, #8907, and #8915 touch other zh-TW keys; their changes are intentionally excluded. The older broad sync in #8670 was also checked at key level and does not contain these targeted corrections.

Validation

• python3 -m json.tool frontend/resources/translations/zh-TW.json
• 2,776 leaf keys: exact en-US/zh-TW key and data-type parity
• all 54 changed values: placeholder, message-reference, HTML-like tag, and newline parity
• npx --yes @inlang/cli@3.3.0 validate --project ./project.inlang
• git diff --check

Assistance disclosure

This localization review and PR description were prepared with OpenAI Codex assistance. Each changed value was checked against the English source and surrounding UI context; no machine-translation command or external translation platform was used to generate the patch.

Contributor agreement

I reviewed and accept the repository CLA, including its broad transferable and sublicensable grant and its permission for third-party licensing on any terms.

Feature Preview

Not applicable: this is a locale-only semantic correction.

PR Checklist

• My code adheres to AppFlowy conventions
• I listed the issue fixed by this PR above
• This PR only contains semantic locale changes
• Relevant JSON, structure, placeholder, newline, and Inlang validation checks pass; the full application test suite was not run because no application code changed

Summary by Sourcery

Refine the zh-TW localization strings to correct mistranslations and ensure consistency with the en-US source and Taiwanese usage.

Bug Fixes:

• Correct inaccurate or misleading zh-TW translations, including AI-related descriptions and authentication messages.
• Fix malformed placeholders and incorrect characters in zh-TW messages to render properly in the UI.

Enhancements:

• Align zh-TW terminology with standard Taiwan usage across multiple UI strings while preserving placeholders, structure, and formatting.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Refines 54 Traditional Chinese (Taiwan) UI strings in the canonical zh-TW.json localization file to better match en-US semantics, fix placeholders and tags, and align terminology with Taiwan usage while preserving keys, structure, and interpolation behavior.

File-Level Changes

Change	Details	Files
Improve semantic accuracy and Taiwan-specific wording for selected zh-TW UI strings while keeping JSON structure and interpolation intact.	Reviewed 54 zh-TW values against en-US source and UI context and updated mistranslations or vague wording to accurately describe features (e.g., local-AI capabilities). Corrected malformed placeholder and tag renderings (e.g., fixing <email/>> and ensuring newline formatting matches en-US). Replaced non-Taiwan or Mainland-preferred terms with established Taiwan usage across authentication, password-reset, and general UI messages. Verified parity of keys, data types, placeholders, message references, HTML-like tags, and newlines between en-US and zh-TW for all modified entries.	frontend/resources/translations/zh-TW.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[CLAassistant]

All committers have signed the CLA.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}