Skip to content

New Crowdin updates#36

Open
maamokun wants to merge 1 commit intomainfrom
l10n_main2
Open

New Crowdin updates#36
maamokun wants to merge 1 commit intomainfrom
l10n_main2

Conversation

@maamokun
Copy link
Collaborator

No description provided.

@vercel
Copy link

vercel bot commented Jan 22, 2026

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

Project Deployment Review Updated (UTC)
mikn-dev Error Error Jan 22, 2026 3:58am

Request Review

@coderabbitai
Copy link

coderabbitai bot commented Jan 22, 2026

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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 updates the Japanese localization file (src/messages/ja.json) to reflect recent changes in the application's user interface and content. The primary impact is a comprehensive reorganization of the file's structure, introducing new sections for layout and product information, and updating existing content. This ensures the application's Japanese interface remains current and accurate with the latest UI and content changes.

Highlights

  • Localization File Restructuring: The ja.json file has undergone a significant structural overhaul, introducing a new layout section and reorganizing the home section to better align with current application needs.
  • Content Updates for Home Section: The home section has been updated with new content, including a hero section with new blurbs and a circularText entry, and details about ossProducts, while many older, unused keys have been removed.
  • Navigation Keys Relocation: Navigation-related keys previously found under the nav object have been moved and integrated into the new layout section, alongside the introduction of new navigation items such as 'Account Center' and 'Refund Policy'.
  • Crowdin Update: These changes are consistent with an automated update from Crowdin, indicating a refresh of translation strings and potentially the underlying structure of the localization data.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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, titled 'New Crowdin updates', modifies the Japanese localization file src/messages/ja.json. My review found a critical issue: many of the new and updated translation strings are in English instead of Japanese. This appears to be an error from the localization process, possibly with Crowdin, where source English strings were committed instead of their Japanese translations. This will result in a broken experience for Japanese users, as much of the UI will be in English. I've left specific comments pointing out the sections with incorrect translations.

Comment on lines +2 to +16
"layout": {
"resources": "Resources",
"solutions": "Solutions",
"accountCenter": "Account Center",
"support": "Support",
"contact": "Contact Us",
"legal": "Legal",
"terms": "Terms of Service",
"privacy": "Privacy Policy",
"refunds": "Refund Policy",
"jp-payments": "特定商取引法に基づく表記",
"home": "Home",
"vision": "Our Vision",
"opensource": "Open Source"
},

Choose a reason for hiding this comment

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

critical

Most translation values in this layout section are in English. As this is the Japanese localization file (ja.json), these values should be in Japanese. The only correctly translated key in this block is jp-payments. All other values need to be translated.

Comment on lines +18 to +27
"hero": {
"blurb1": "Creators of",
"blurb2": "lots of cool stuff",
"blurb3": "making life easier.",
"circularText": "Open Source ☆ Sugoi ☆ MikanDev ☆ Freedom ☆ ",
"primaryCta": "Take a Look",
"loop": "What makes us cool"
},
"OpenSource": "Everything. Open. Source.",
"OpenSourceBlurb": "We believe in freedom and openness. Every single one of our projects and services are open source and available for anyone to use, modify, and distribute. Check out our GitHub to see what we're working on!",

Choose a reason for hiding this comment

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

critical

The translations in the hero object, as well as for OpenSource and OpenSourceBlurb, are in English. They need to be translated into Japanese for this localization file.

Comment on lines +31 to +40
"ossProducts": {
"karaSnap": {
"title": "KaraSnap",
"description": "The easiest karaoke logging app ever, powered by AI"
},
"nextDiscordAuth": {
"title": "Next Discord Auth",
"description": "Simple, no-nonsense Discord OAuth for your Next.js apps"
}
}

Choose a reason for hiding this comment

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

critical

The translations for ossProducts within the home object are in English. These should be in Japanese. For example, "title": "KaraSnap" and its description need to be translated.

Comment on lines +53 to +56
"ossProducts": {
"viewRepo": "View Repository",
"visitSite": "Visit Website"
}

Choose a reason for hiding this comment

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

critical

These ossProducts translations are in English. They should be translated to Japanese.

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