Skip to content

Conversation

@maamokun
Copy link
Collaborator

@maamokun maamokun commented Oct 27, 2025

Summary by CodeRabbit

  • Localization
    • Updated user-facing interface language from Japanese to English across home, navigation, and contact sections. Terminology and phrasing now aligned with English conventions for improved user experience and consistency throughout the application.

@vercel
Copy link

vercel bot commented Oct 27, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
mikn-dev Error Error Oct 27, 2025 2:06pm

@coderabbitai
Copy link

coderabbitai bot commented Oct 27, 2025

Walkthrough

Translation values in the Japanese messages file were updated from Japanese text to English equivalents. All JSON keys remain unchanged; only string values were modified across home, navigation, and contact sections without adding or removing any entries.

Changes

Cohort / File(s) Change Summary
Translation Updates
src/messages/ja.json
Japanese translation values converted to English strings; all keys preserved with no structural modifications or new/removed entries.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Verification needed: Confirm all translation strings are semantically accurate and consistent with the application's messaging conventions
  • Single-file scope: Straightforward value-only changes with no logic or structural modifications reduce complexity

Poem

🐰 Hop, hop—translations take flight,
From nihongo whispers to English bright,
Keys stayed put, values transformed true,
A polyglot file, refreshed anew! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
Title Check ❓ Inconclusive The title "New Crowdin updates" is vague and uses non-descriptive terminology. While it does reference Crowdin, which is related to the localization platform typically used for managing translations, the term "updates" lacks specificity about what is actually being changed. Someone scanning the pull request history would not clearly understand that this PR involves updating translations in the Japanese message file (ja.json) from Japanese to English. The title fails to communicate the primary change in a meaningful way, similar to generic terms like "misc updates". Consider revising the title to be more specific and descriptive of the actual changes, such as "Update Japanese translations in ja.json" or "Sync Japanese localization strings from Crowdin". This would provide clearer context about which language files are being updated and the nature of the changes, making it easier for reviewers to understand the PR's purpose at a glance.
✅ Passed checks (1 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch l10n_main

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.

@gemini-code-assist
Copy link

Summary of Changes

Hello @maamokun, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, titled "New Crowdin updates," modifies the src/messages/ja.json localization file. The primary change involves replacing all existing Japanese translation strings with their English counterparts. This update likely reflects a recent synchronization with Crowdin, potentially indicating a reset of the Japanese translations to the source language or an adjustment in the localization strategy for this specific file.

Highlights

  • Localization File Update: The src/messages/ja.json file has been updated.
  • Language Content Change: All Japanese translation strings within src/messages/ja.json have been replaced with their English equivalents, indicating a significant change in the content of this localization file.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request, likely from an automated translation service (Crowdin), has incorrectly replaced all Japanese translations in src/messages/ja.json with the source English strings. This is a critical issue that will break the localization for Japanese-speaking users, as they will see English text instead of Japanese. These changes should be reverted, and the Crowdin integration should be investigated to fix the root cause of this error.

Comment on lines 1 to 65
{
"home": {
"creating-cool": "生活を豊かにする",
"makeLifeEasier": "を作っています。",
"stuff": "ヤツ",
"apps": "アプリ",
"tools": "ツール",
"bots": "Bot",
"mainBlurb1": "日常生活で出会う問題に対するオープンソースの解決策を作ります。",
"mainBlurb2": "大金持ちでなくても人生を豊かに。",
"takeLook": "見てみよう",
"learnMore": "もっと知る",
"infoTitle": "私達の秘訣",
"infoBlurb": "The MikanDev Difference",
"OSSonOSS": "オープンソース上のオープンソース",
"OSSonOSSBlurb": "私達はオープンソースの力を信じています。私達のプロジェクトは全て自己ホスト、修正、貢献が可能です。使用するサードパーティサービスもオープンソースです。",
"partOfPage": "このページもなんとオープンソースです!",
"viewOnGH": "GitHubで見てみる",
"SimpleNCheap": "シンプルさを追求し生まれた究極ののコストパフォマンス",
"SimpleNCheapBlurb": "私達は複雑なことを好みません。私達のプロジェクトは使いやすさを重視し、高額なサードパーティサービスに依存しません。その節約分はあなたに還元されます!",
"monthlyCost": "平均月額運用費用",
"MAUBilled": "従量課金サービス使用",
"despite": "にもかかわらず...",
"monthlyBandwidth": "平均月間帯域幅使用量",
"mainServices": "主要サービス",
"monthlyUptime": "平均月間稼働率",
"HowSoCheap": "なぜこんなに安いの?",
"SelfFunded": "100%自己資金",
"SelfFundedBlurb": "私達は投資家やVCに責任を負う必要がないため、利益を上げるタイミングを自分たちで決めることができます。私達はお金を稼ぐためではなく、面白いものを作るためにここにいます。",
"WorkWithBest": "最高の人たちと一緒に",
"WorkWithBestBlurb": "私達は他の素敵な組織と提携し、彼らの素晴らしいものを世に出すお手伝いをします。私達はコミュニティに全力を注いでいます!",
"workWithMe": "私たちと一緒にやろう!",
"NoWait": "これ以上言うことはありません。",
"NoWaitBlurb": "私たちのプロジェクトをチェックして、気に入るものがあるかどうかを見てください!"
"creating-cool": "Creating cool",
"makeLifeEasier": "to make life easier.",
"stuff": "stuff",
"apps": "Apps",
"tools": "Tools",
"bots": "Bots",
"mainBlurb1": "We create open-source solutions for those itches in life that need scratching.",
"mainBlurb2": "Enrich your life without breaking the bank.",
"takeLook": "Take a look",
"learnMore": "Learn More",
"infoTitle": "what makes us special",
"infoBlurb": "The MikanDev Difference",
"OSSonOSS": "Open Source with Open Source",
"OSSonOSSBlurb": "We believe in the power of open source. All of our projects are free to self-host, modify and contribute to. Any third-party services we use are also open source.",
"partOfPage": "the very page you're reading is open source!",
"viewOnGH": "View on GitHub",
"SimpleNCheap": "Designed with simplicity for ultimate cost-effectiveness",
"SimpleNCheapBlurb": "We don't believe in overcomplicating things. Our projects are designed to be simple to use, and aren't held up by expensive third-party services. The savings are passed on to you!",
"monthlyCost": "Avg. Monthly running cost",
"MAUBilled": "MAU billed services used",
"despite": "Despite...",
"monthlyBandwidth": "Avg. Monthly bandwidth usage",
"mainServices": "Main services",
"monthlyUptime": "Avg. Monthly uptime",
"HowSoCheap": "How so cheap?",
"SelfFunded": "100% Self-funded",
"SelfFundedBlurb": "We don't have any investors or VC to answer to, so we can decide when we make a profit. We're here to make cool stuff, not money.",
"WorkWithBest": "Working with the best",
"WorkWithBestBlurb": "We partner with other cool organizations and help get their cool stuff out there. We're all about the community :3",
"workWithMe": "Work with us!",
"NoWait": "What's more to say?",
"NoWaitBlurb": "Check out our projects and see if there's something you like!"
},
"nav": {
"support": "サポート",
"docs": "ドキュメント",
"solutions": "ソリューション",
"legal": "法的条約",
"payments": "支払いセンター",
"blog": "ブログ",
"support": "Support",
"docs": "Docs",
"solutions": "Solutions",
"legal": "Legal",
"payments": "Payment Center",
"blog": "Blog",
"discord": "Discord",
"contact": "お問い合わせ",
"terms": "利用規約",
"privacy": "プライバシーポリシー",
"contact": "Contact Us",
"terms": "Terms of Service",
"privacy": "Privacy Policy",
"jp-payments": "特定商取引法に基づく表記",
"gdpr": "GDPRコンプライアンス",
"myAccount": "マイアカウント",
"resources": "リソース",
"cookieConsent": "そこの君!このサイトはCookieを使ってるぞ!!いいよね?",
"accept": "いいね!"
"gdpr": "GDPR Compliance",
"myAccount": "My Account",
"resources": "Resources",
"cookieConsent": "We use cookies for analytics and making stuff work. By clicking 'mmmmmmm cookies 🍪', you agree to our use of cookies.",
"accept": "mmmmmmm cookies 🍪"
},
"contact": {
"title": "お問い合わせ",
"mail": "メール",
"phone": "電話 (日本のみ)*",
"title": "Contact Us",
"mail": "Email",
"phone": "Phone (JP Only)*",
"discord": "Discord",
"join": "Discordに参加",
"general-support": "一般サポート",
"billing-support": "請求に関する問い合わせ",
"abuse-reports": "不正行為の報告",
"phone-disclaimer": "※日本国内の電話番号のみ対応しています。"
"join": "Join our Discord",
"general-support": "General Support",
"billing-support": "Billing Support",
"abuse-reports": "Abuse Reports",
"phone-disclaimer": "*Calling this number from outside of Japan may result in high charges. Please use the email or Discord for support."
}
}

Choose a reason for hiding this comment

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

critical

The contents of this Japanese translation file have been completely replaced with English strings. This will break localization for all Japanese users, as they will be shown English text. This change should be reverted, and the automated process that generated it should be investigated to prevent this from happening in the future.

@cloudflare-workers-and-pages
Copy link

Deploying mikn-dev with  Cloudflare Pages  Cloudflare Pages

Latest commit: 3530b34
Status:🚫  Build failed.

View logs

Copy link

@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: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e30afe8 and 3530b34.

📒 Files selected for processing (1)
  • src/messages/ja.json (1 hunks)

Comment on lines +3 to +34
"creating-cool": "Creating cool",
"makeLifeEasier": "to make life easier.",
"stuff": "stuff",
"apps": "Apps",
"tools": "Tools",
"bots": "Bots",
"mainBlurb1": "We create open-source solutions for those itches in life that need scratching.",
"mainBlurb2": "Enrich your life without breaking the bank.",
"takeLook": "Take a look",
"learnMore": "Learn More",
"infoTitle": "what makes us special",
"infoBlurb": "The MikanDev Difference",
"OSSonOSS": "Open Source with Open Source",
"OSSonOSSBlurb": "We believe in the power of open source. All of our projects are free to self-host, modify and contribute to. Any third-party services we use are also open source.",
"partOfPage": "the very page you're reading is open source!",
"viewOnGH": "View on GitHub",
"SimpleNCheap": "Designed with simplicity for ultimate cost-effectiveness",
"SimpleNCheapBlurb": "We don't believe in overcomplicating things. Our projects are designed to be simple to use, and aren't held up by expensive third-party services. The savings are passed on to you!",
"monthlyCost": "Avg. Monthly running cost",
"MAUBilled": "MAU billed services used",
"despite": "Despite...",
"monthlyBandwidth": "Avg. Monthly bandwidth usage",
"mainServices": "Main services",
"monthlyUptime": "Avg. Monthly uptime",
"HowSoCheap": "How so cheap?",
"SelfFunded": "100% Self-funded",
"SelfFundedBlurb": "We don't have any investors or VC to answer to, so we can decide when we make a profit. We're here to make cool stuff, not money.",
"WorkWithBest": "Working with the best",
"WorkWithBestBlurb": "We partner with other cool organizations and help get their cool stuff out there. We're all about the community :3",
"workWithMe": "Work with us!",
"NoWait": "What's more to say?",
"NoWaitBlurb": "Check out our projects and see if there's something you like!"
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Critical: Japanese translation file contains English text instead of Japanese translations.

This is a Japanese localization file (ja.json), yet all the changed lines now contain English text (e.g., "Creating cool", "Support", "Contact Us"). This will cause Japanese users to see an English interface instead of Japanese.

Line 47 remains unchanged with Japanese text ("特定商取引法に基づく表記"), which strongly suggests that all other changed lines should also contain Japanese translations.

Please clarify:

  • Was this change intentional?
  • Should these values be reverted to Japanese?
  • Is there a misconfiguration in your Crowdin setup that caused English text to replace the Japanese translations?

This PR should not be merged until this is resolved, as it will break the Japanese language experience for your users.

Also applies to: 37-52, 55-63


🏁 Script executed:

#!/bin/bash
# 1. Examine the actual ja.json file content
echo "=== EXAMINING ja.json FILE ==="
cat src/messages/ja.json | head -60

echo -e "\n=== FILE SIZE AND LINE COUNT ==="
wc -l src/messages/ja.json

echo -e "\n=== CHECKING FOR OTHER LANGUAGE FILES ==="
fd -e json src/messages/

echo -e "\n=== EXAMINING en.json FOR COMPARISON ==="
if [ -f src/messages/en.json ]; then
  echo "Found en.json - first 60 lines:"
  cat src/messages/en.json | head -60
fi

echo -e "\n=== CHECKING LOCALE/TRANSLATION DIRECTORY STRUCTURE ==="
ls -la src/messages/ 2>/dev/null || echo "Directory not found at src/messages/"

Length of output: 6107



🏁 Script executed:

#!/bin/bash
# Check git diff for ja.json to see what changed in this PR
echo "=== GIT DIFF FOR ja.json ==="
git diff HEAD~1 src/messages/ja.json 2>/dev/null || git diff src/messages/ja.json 2>/dev/null || echo "Could not retrieve git diff"

echo -e "\n=== GIT LOG FOR ja.json (last 5 commits) ==="
git log --oneline -n 5 -- src/messages/ja.json 2>/dev/null || echo "Could not retrieve git log"

echo -e "\n=== CHECK IF ja.json AND en.json ARE IDENTICAL ==="
if cmp -s src/messages/ja.json src/messages/en.json; then
  echo "ja.json and en.json are IDENTICAL (byte-for-byte)"
else
  echo "ja.json and en.json DIFFER"
  echo "First difference:"
  cmp -l src/messages/ja.json src/messages/en.json | head -5
fi

echo -e "\n=== SEARCHING FOR LOCALIZATION DOCUMENTATION ==="
fd -i readme src/ 2>/dev/null | head -10
fd -i crowdin src/ 2>/dev/null | head -10
fd -i local src/ 2>/dev/null | head -10

echo -e "\n=== CHECKING FOR i18n OR TRANSLATION CONFIG ==="
fd -i 'package.json|tsconfig|vite|webpack|i18n' src/ 2>/dev/null | head -10

Length of output: 5435


Revert ja.json changes—this commit replaced all Japanese translations with English text, breaking the Japanese user experience.

The git diff shows that this PR removed all Japanese translations (生活を豊かにする, アプリ, サポート, etc.) and replaced them with English equivalents. Only the legally required field "jp-payments": "特定商取引法に基づく表記" correctly retained Japanese text.

Before this change, ja.json contained proper Japanese localisation across all sections (home, nav, contact). This commit has broken the entire Japanese language option. This must be reverted or corrected before merging, as Japanese users will now see an English interface instead of Japanese.

Verify your Crowdin configuration or restore the Japanese translations to src/messages/ja.json.

🤖 Prompt for AI Agents
In src/messages/ja.json around lines 3 to 34, the Japanese translations were
replaced with English text breaking the ja locale; revert these lines to the
original Japanese strings (restore all Japanese keys such as
mainBlurb1/mainBlurb2, apps, tools, bots, infoTitle, etc.) or re-import the
proper ja.json from Crowdin/translation source, confirm jp-payments remains
unchanged, and update CI/translation config to prevent automated overwrite (or
add a test) so the ja.json retains Japanese translations going forward.

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