terms.md: add several terms for doc translation

[qiancai]

First-time contributors' checklist

• I've signed the Contributor License Agreement, which is required for the repository owners to accept my contribution.

What is changed, added or deleted? (Required)

As in the title

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s):

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lilin90 for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gemini-code-assist]

Summary of Changes

Hello @qiancai, 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 enhances the documentation's translation resources by incorporating several new technical terms into the terms.md glossary. These additions aim to standardize terminology and provide clear translation guidelines for future documentation efforts, ensuring consistency across different language versions.

Highlights

• New Terminology Added: Several new technical terms have been added to the terms.md glossary, expanding the vocabulary available for documentation translation.
• Translation Guidance Included: Specific translation notes and Chinese equivalents have been provided for each new term, ensuring consistency and clarity in translated documentation.

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

Changelog

• resources/terms.md
  • Added "auto embedding" with specific translation notes.
  • Included "Bring Your Own Key (BYOK)" with its Chinese translation.
  • Added "CRUD" with its Chinese translation.
  • Introduced "full-text search" with its Chinese translation.
  • Added "see also" with its Chinese translation.
  • Included "TiDB Cloud Premium" and "TiDB Self-Managed" with translation guidance.
  • Added "vector search" with its Chinese translation.

Activity

• No review comments or activity have been recorded on this pull request yet.

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 adds several new terms to the glossary for documentation translation. The additions are relevant and helpful. I have a couple of minor suggestions to improve grammar and maintain style consistency within the file.

[gemini-code-assist]

There's a minor grammatical error in the comment. It should be 'as a verb' instead of 'as verb'.

Suggested change

	| auto embedding | auto embedding | Keep it in English as a feature name. If it is used as a verb, translate it to "自动生成向量" in Chinese. |
	| auto embedding | auto embedding | Keep it in English as a feature name. If it is used as a verb, translate it to "自动生成向量" in Chinese. |

References

1. The style guide requires correcting English grammar, spelling, and punctuation mistakes. (Line 20) ^(link)

[gemini-code-assist]

To maintain consistency with other entries in this file, please use half-width parentheses and comma. Most other entries with acronyms or explanations use half-width punctuation.

Suggested change

	| Bring Your Own Key (BYOK) | Bring Your Own Key（BYOK，由用户自行提供 API 密钥） | |
	| Bring Your Own Key (BYOK) | Bring Your Own Key (BYOK, 由用户自行提供 API 密钥) | |

References

1. The style guide emphasizes consistency in terminology and formatting. (Lines 16, 25, 47) ^(link)