Align Chinese and Japanese knowledge translations with English

[lyzno1]

Summary

• update zh-Hans knowledge copy for document counts, wording, and API label to mirror the English source
• refresh ja-JP knowledge strings for counts, API access, deprecation messaging, and availability wording
• sync retrieval test/settings translations by removing obsolete fields and aligning terminology with en-US

Testing

• git commit (pre-commit hook: ESLint) (pass)
• git commit (pre-commit hook: tsgo --noEmit) (pass)
• git commit (pre-commit hook: unit tests check) (pass)

---

Codex Task

[gemini-code-assist]

Summary of Changes

Hello @lyzno1, I'm Gemini Code Assist¹! 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 focuses on enhancing the accuracy and consistency of localized content for Japanese and Simplified Chinese knowledge base interfaces. It involves updating various UI strings, refining terminology related to search and retrieval settings, and ensuring that document count and API access labels are aligned with the English source, ultimately improving the user experience for non-English speakers by providing more precise and consistent translations.

Highlights

• Japanese Translation Refinements: Updated various strings in Japanese for knowledge base hit testing, settings, and general dataset views, including changes to terminology, document count phrasing, and API access labels to improve clarity and consistency.
• Chinese Translation Updates: Aligned Simplified Chinese translations for document counts, word count units, and API access labels to match the English source and enhance user understanding.
• Terminology Alignment: Standardized retrieval-related terminology across Japanese translations, such as changing 'acquisition settings' to 'search settings' and 'model search' to 'search model', and updating placeholder text to reference 'Dify' and 'hit strategy'.
• Deprecation Messaging Enhancement: Enhanced the Japanese deprecation message for N-to-1 Retrieval to not only state its upcoming removal but also recommend using the latest multi-pass search for better results.
• Obsolete Field Removal: Removed the 'text' column from table headers in both Japanese and Simplified Chinese hit testing translations, streamlining the display and removing redundant information.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates the Chinese (zh-Hans) and Japanese (ja-JP) translation files to align them with the English source. The changes include updating terminology (e.g., 'retrieval' to 'search', 'available' to 'enabled'), correcting wording for better accuracy and natural language flow (e.g., 'characters' to 'words', improving sentence structure in Japanese), replacing hardcoded values with dynamic placeholders, and removing obsolete translation keys. The updates are consistent across both languages and significantly improve the quality and accuracy of the localizations. The code changes are correct and well-executed.