Skip to content

New Crowdin updates#450

Merged
steveiliop56 merged 5 commits intomainfrom
l10n_main
Nov 21, 2025
Merged

New Crowdin updates#450
steveiliop56 merged 5 commits intomainfrom
l10n_main

Conversation

@steveiliop56
Copy link
Copy Markdown
Member

@steveiliop56 steveiliop56 commented Nov 10, 2025

Summary by CodeRabbit

  • Chores
    • Expanded Traditional Chinese (zh-TW) localization for authentication and security UI: updated translations for login screens, OAuth/redirect messages, manual vs. auto-redirect wording, untrusted/domain warnings, password recovery prompts, and validation messages.
    • Improved Vietnamese (vi-VN) translations for password recovery, provider load errors, and general error messages.
    • Reformatted Brazilian Portuguese (pt-BR) locale file without changing displayed text.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Nov 10, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

Updated three locale JSON files (zh-TW, vi-VN, pt-BR) with translation edits and formatting changes for authentication/OAuth-related UI strings; no code, exports, or control-flow changes. (≈24 words)

Changes

Cohort / File(s) Summary
Traditional Chinese Localization
frontend/src/lib/i18n/locales/zh-TW.json
Replaced and expanded Traditional Chinese translations for OAuth/redirect and authentication UI keys (titles, subtitles, buttons, warnings, validation messages, help text such as untrustedRedirectTitle, untrustedRedirectSubtitle, autoRedirectTitle, autoRedirectSubtitle, manualRedirectTitle, manualRedirectSubtitle, manualRedirectButton, domainWarning, genericError, help, forgotPasswordTitle, requiredInput, invalidInput, domainGo, and related entries).
Vietnamese Localization
frontend/src/lib/i18n/locales/vi-VN.json
Updated Vietnamese translations for authentication UI strings including forgotPasswordTitle, failedToFetchProvidersTitle, and errorSubtitle; remaining keys preserved.
Portuguese (Brazil) Localization (formatting only)
frontend/src/lib/i18n/locales/pt-BR.json
Rewrapped/reformatted JSON (indentation/line-wrapping); no key or value changes detected—purely formatting edits.

Sequence Diagram(s)

(Skipped — changes are localization strings only; no control-flow or feature behavior to diagram.)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

  • Review focus:
    • JSON syntax/encoding and UTF-8 correctness.
    • Confirm no keys were renamed/removed.
    • Spot-check critical user-facing strings for accuracy.

Possibly related PRs

Poem

🐰
I nibble lines of phrases bright,
I polish words for day and night,
OAuth hops and labels sing,
Translations sprout on tiny spring,
A carrot cheer for every right. 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'New Crowdin updates' is vague and generic. While it accurately reflects that localization files were updated via Crowdin, it does not provide meaningful detail about what specific languages or scope of changes were made. Consider a more descriptive title such as 'Update translations for zh-TW, vi-VN, and pt-BR locales' to clearly indicate which languages were updated and the scope of the changes.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 56bab03 and be08534.

📒 Files selected for processing (1)
  • frontend/src/lib/i18n/locales/pt-BR.json (1 hunks)

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov
Copy link
Copy Markdown

codecov Bot commented Nov 10, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 23.67%. Comparing base (9d21d6a) to head (be08534).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #450   +/-   ##
=======================================
  Coverage   23.67%   23.67%           
=======================================
  Files          36       36           
  Lines        2230     2230           
=======================================
  Hits          528      528           
  Misses       1666     1666           
  Partials       36       36           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
frontend/src/lib/i18n/locales/zh-TW.json (2)

25-27: Use consistent formality in similar UI contexts.

Line 25 (existing) uses the formal pronoun "您" for the insecure redirect warning, but the new untrusted redirect message on line 27 uses the informal "你". For consistency in tone and user experience, both should match.

Apply this diff to align the formality:

-    "continueUntrustedRedirectSubtitle": "你嘗試重新導向的域名與設定不符(<code>{{cookieDomain}}</code>)。你確定要繼續嗎?",
+    "continueUntrustedRedirectSubtitle": "您嘗試重新導向的域名與設定不符(<code>{{cookieDomain}}</code>)。您確定要繼續嗎?",

55-55: Align code formatting with rest of file.

The file consistently uses <code> HTML tags for code/variable formatting (e.g., lines 27, 33, 34, 59), but line 55 uses backticks around USERS. For consistency and proper rendering, use the <code> tag format.

Apply this diff:

-    "forgotPasswordMessage": "透過修改 `USERS` 環境變數,你可以重設你的密碼。",
+    "forgotPasswordMessage": "透過修改 <code>USERS</code> 環境變數,你可以重設你的密碼。",
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8453c48 and 54c003c.

📒 Files selected for processing (1)
  • frontend/src/lib/i18n/locales/zh-TW.json (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Analyze (go)
🔇 Additional comments (1)
frontend/src/lib/i18n/locales/zh-TW.json (1)

17-23: JSON structure and translations look solid.

All translations are consistent with existing terminology (e.g., "重新導向" for redirect, "OAuth 供應商" for provider). Template variables ({{variable}}) and HTML tags are preserved correctly. Once the pronoun and code-formatting issues above are addressed, this is ready to merge.

Also applies to: 26-27, 56-61

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 54c003c and 7bdb7be.

📒 Files selected for processing (1)
  • frontend/src/lib/i18n/locales/zh-TW.json (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Analyze (go)
🔇 Additional comments (1)
frontend/src/lib/i18n/locales/zh-TW.json (1)

2-2: JSON structure and translations look good.

The JSON syntax is valid, placeholders (e.g., {{cookieDomain}}, {{username}}) are correctly preserved, HTML code tags are consistently used in most entries, and the Traditional Chinese translations are coherent. Once the pronoun inconsistencies are resolved, this update is ready.

Also applies to: 17-27, 56-61

Comment on lines +26 to +27
"continueUntrustedRedirectTitle": "不受信任的重新導向",
"continueUntrustedRedirectSubtitle": "你嘗試重新導向的域名與設定不符(<code>{{cookieDomain}}</code>)。你確定要繼續嗎?",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Pronoun formality inconsistency: use "您" instead of "你".

Line 27 uses the informal second-person pronoun "你", while the rest of the localization file consistently uses the formal "您". This creates an inconsistent tone in the UI.

-    "continueUntrustedRedirectSubtitle": "你嘗試重新導向的域名與設定不符(<code>{{cookieDomain}}</code>)。你確定要繼續嗎?",
+    "continueUntrustedRedirectSubtitle": "您嘗試重新導向的域名與設定不符(<code>{{cookieDomain}}</code>)。您確定要繼續嗎?",
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"continueUntrustedRedirectTitle": "不受信任的重新導向",
"continueUntrustedRedirectSubtitle": "你嘗試重新導向的域名與設定不符(<code>{{cookieDomain}}</code>)。你確定要繼續嗎",
"continueUntrustedRedirectTitle": "不受信任的重新導向",
"continueUntrustedRedirectSubtitle": "您嘗試重新導向的域名與設定不符(<code>{{cookieDomain}}</code>)。您確定要繼續嗎",
🤖 Prompt for AI Agents
In frontend/src/lib/i18n/locales/zh-TW.json around lines 26 to 27, the subtitle
string uses the informal pronoun "你" while the rest of the file uses the formal
"您"; update the subtitle to use "您" (e.g., replace "你嘗試重新導向的域名與設定不符..." with
"您嘗試重新導向的域名與設定不符...") so the tone is consistent across the localization.

"domainWarningSubtitle": "This instance is configured to be accessed from <code>{{appUrl}}</code>, but <code>{{currentUrl}}</code> is being used. If you proceed, you may encounter issues with authentication.",
"ignoreTitle": "Ignore",
"goToCorrectDomainTitle": "Go to correct domain"
"forgotPasswordMessage": "透過修改 `USERS` 環境變數,你可以重設你的密碼。",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Pronoun formality inconsistency and code tag formatting: use "您" instead of "你", and use <code> tags instead of backticks.

Line 55 uses the informal pronoun "你" (inconsistent with the formal "您" used throughout the file) and backticks around `USERS` instead of <code> tags used elsewhere. For consistency and proper HTML rendering, align this with the rest of the file.

-    "forgotPasswordMessage": "透過修改 `USERS` 環境變數,你可以重設你的密碼。",
+    "forgotPasswordMessage": "透過修改 <code>USERS</code> 環境變數,您可以重設您的密碼。",
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"forgotPasswordMessage": "透過修改 `USERS` 環境變數,你可以重設你的密碼",
"forgotPasswordMessage": "透過修改 <code>USERS</code> 環境變數,您可以重設您的密碼",
🤖 Prompt for AI Agents
frontend/src/lib/i18n/locales/zh-TW.json around line 55: the string uses the
informal pronoun "你" and backticks around `USERS`, which is inconsistent with
the rest of the file; change "你" to the formal "您" and replace the
backticks-wrapped `USERS` with an HTML <code>USERS</code> tag so the message
matches the file’s formality and code formatting conventions.

@steveiliop56 steveiliop56 merged commit e79d1a8 into main Nov 21, 2025
5 of 6 checks passed
@steveiliop56 steveiliop56 deleted the l10n_main branch November 21, 2025 15:48
@coderabbitai coderabbitai Bot mentioned this pull request Dec 14, 2025
@coderabbitai coderabbitai Bot mentioned this pull request Feb 7, 2026
@coderabbitai coderabbitai Bot mentioned this pull request Feb 22, 2026
@coderabbitai coderabbitai Bot mentioned this pull request Mar 1, 2026
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.

1 participant