ci: create terms.md for ai translation #21251
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ti-chi-bot
bot
added
missing-translation-status
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary of Changes
Hello @shhdgit, 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 introduces a new markdown file intended to function as a centralized glossary for technical terms. Its primary purpose is to standardize terminology, particularly to facilitate and improve the accuracy of AI-driven translation processes for documentation.
Highlights
- New Glossary File Creation: I've added a new file,
resources/terms.md, which serves as a comprehensive glossary of technical terms. - AI Translation Support: This new
terms.mdfile is specifically designed to aid AI translation efforts by providing standardized English terms and their corresponding Chinese translations, along with contextual comments. - Standardized Terminology: The file contains 474 entries, covering a wide range of technical concepts from database internals (e.g., '2-phase commit', 'MVCC', 'Raft') to general computing terms (e.g., 'concurrency', 'latency', 'thread pool'), ensuring consistent terminology across documentation.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| 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 issue 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 is currently in preview and 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 to provide feedback.
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
-
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. ↩
| | effective range | 生效范围 | | | ||
| | earlier version | 以下版本 | | | ||
| | edit | 修改/编辑（如：修改 ini 文件） | | | ||
| | effective range | 生效范围 | | |
There was a problem hiding this comment.
Duplicate entry for "effective range" (defined on line 120). Remove this line.
| | trie | 字典树 | | | ||
| | trie | 单词查找树 | | |
| | listening address | 监听地址 | | | ||
| | load | 负载 | | | ||
| | load | 加载 | | | ||
| | Local Persist Volume(s)/LPV(s) | 本地持久化卷 | | |
There was a problem hiding this comment.
| | mutex | 互斥锁 | Mutual exclusion | | ||
| | MySQL syntax | MySQL 语法 | | | ||
| | namespace | 命名空间 | | | ||
| | nest loop | 嵌套循环 | | |
| | rough set | 粗糙集 | | | ||
| | routine | 例程 | | | ||
| | row store | 行存 | | | ||
| | rule based optimization (RBO) | 基于规则的优化 | | |
There was a problem hiding this comment.
| | sign bit | 符号位 | | | ||
| | simulate | 模拟 | | | ||
| | single-instance | 单机 | | | ||
| | single point of failure (SPOF) | 单点故障 | || |
There was a problem hiding this comment.
Remove the extra pipe character.
| | single point of failure (SPOF) | 单点故障 | || | |
| | single point of failure (SPOF) | 单点故障 | |
| | target machine | （部署）目标机器 | | | ||
| | technology stack | 技术栈 | | | ||
| | test | 测试 | | | ||
| | the configuration file | 配置文件 | | |
There was a problem hiding this comment.
| | Cartesian product | 笛卡尓积 | | | ||
| | case-sensitive | 大小写敏感 | | | ||
| | certificate signing request (CSR) | 证书签名请求 | | | ||
| | cost based optimization (CBO) | 基于代价的优化 | | |
| | trie | 单词查找树 | | | ||
| | tutorial | 教程 | | | ||
| | type | 类型 | | | ||
| | type infer | 类型推导 | | |
| | verification | 验证 | | | ||
| | verify | 验证 | | | ||
| | Vertical Pod Autoscaling (VPA) | Pod 自动垂直扩容 | TiDB on Kubernetes | | ||
| | wild card | 通配符 | | |
|
@shhdgit: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
ti-chi-bot
bot
removed
the
missing-translation-status
First-time contributors' checklist
What is changed, added or deleted? (Required)
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.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?