-
Notifications
You must be signed in to change notification settings - Fork 82
English translation of google drive. #258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
xrgzs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is messed up by auto-formatting.
Line Break Before Closing
:::: Always add a line break before the closing:::, especially when using lists (li), otherwise formatting may be corrupted
jyxjjj
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
大量格式错误
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This pull request provides English translations for the Google Drive driver documentation in the OpenList project. The PR addresses issue #1774 by adding comprehensive English content alongside the existing Chinese documentation using VitePress-style language blocks.
Key Changes
- Added English translations for all sections of the Google Drive setup guide
- Introduced new English screenshot images (e.g.,
google-08-l-en.png) - Implemented bilingual documentation structure using
::: enand::: zh-CNlanguage blocks - Translated Mermaid diagrams and flowcharts to English
Reviewed changes
Copilot reviewed 1 out of 9 changed files in this pull request and generated 8 comments.
| File | Description |
|---|---|
public/img/drivers/google/google-08-l-en.png |
New English screenshot for OAuth client configuration step |
pages/guide/drivers/google_drive.md |
Complete English translation of Google Drive setup guide with bilingual structure |
Note: The review identified several maintainability issues with inconsistent numbering in the Chinese language sections. The Chinese sections continue numbering from where the English sections end (e.g., starting at 3-4 instead of 1-2), which creates confusion. Each language block should restart numbering from 1 to maintain clarity and consistency. Additionally, there are incorrect cross-references within the Chinese text that reference non-existent step numbers.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
pages/guide/drivers/google_drive.md
Outdated
| ::: zh-CN | ||
| 10. 打开 OpenList 的管理界面,点击左侧菜单中的`存储`。 | ||
|
|
||
| 8.2. 在`客户端ID`中填写你的`Oauth 客户端 ID`,在`客户端密钥`中填写你的`Oauth 客户端密钥` | ||
| 11. 在存储列表页面,点击右上角的`添加存储`按钮。 | ||
|
|
||
|  | ||
|  | ||
| 12. 选择驱动为`谷歌云盘(Google Drive)`。 | ||
|
|
||
| 9. 点击`添加`按钮,完成谷歌云盘的添加。 | ||
|  | ||
|  | ||
|
|
||
| ## 4. 关于`Use online api`选项的说明 | ||
| 13. 输入挂载路径,如:`google-drive`。 | ||
|
|
||
| ### 4.1. 自身有密钥的情况下,AccessToken刷新的方式 | ||
| 14. 在`根文件夹 ID`中填写上面获取的根文件夹 ID,如果使用根目录,请填写`root`。 | ||
|
|
||
| 15. 刷新令牌中填写上面获取的刷新令牌(如未获取,请参考[准备接入](#_2-准备接入))。 | ||
|
|
||
| 16. 如果你使用的是 `OpenList (或者公益服务器/自建服务器)`提供的 OAuth 客户端 ID 和密钥,请按照`7.1`和`7.2`进行配置 | ||
|
|
||
| 7.1. 在`Use online api`中勾选,表示使用 OpenList 提供的在线 API。 | ||
|
|
||
| 7.2. Api url address填写为 `https://api.oplist.org/googleui/renewapi`,如果是`公益服务器/自建服务器`,请填写对应的服务器地址。 | ||
|
|
||
|  | ||
|  | ||
|
|
||
| 17. 如果你使用的是自己创建的 OAuth 客户端 ID 和密钥,请按照`8.1`和`8.2`进行配置 | ||
|
|
||
| 8.1. 在`Use online api`中不勾选,表示使用自建的 OAuth 客户端 ID 和密钥。 | ||
|
|
||
| 8.2. 在`客户端ID`中填写你的`Oauth 客户端 ID`,在`客户端密钥`中填写你的`Oauth 客户端密钥` | ||
|
|
||
|  | ||
|  | ||
|
|
||
| 18. 点击`添加`按钮,完成谷歌云盘的添加。 | ||
| ::: |
Copilot
AI
Dec 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The numbering for the Chinese section continues from 10-18 after the English section used 1-9. This creates confusing and inconsistent numbering. The Chinese section should start from 1, matching the structure of the English section.
Should start with:
::: zh-CN
1. 打开 OpenList 的管理界面,点击左侧菜单中的`存储`。
pages/guide/drivers/google_drive.md
Outdated
| 16. 如果你使用的是 `OpenList (或者公益服务器/自建服务器)`提供的 OAuth 客户端 ID 和密钥,请按照`7.1`和`7.2`进行配置 | ||
|
|
||
| 7.1. 在`Use online api`中勾选,表示使用 OpenList 提供的在线 API。 | ||
|
|
||
| 7.2. Api url address填写为 `https://api.oplist.org/googleui/renewapi`,如果是`公益服务器/自建服务器`,请填写对应的服务器地址。 |
Copilot
AI
Dec 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Step 16 references configuration steps "7.1" and "7.2", but these are actually substeps within the current step 16. This reference is confusing because steps 7.x don't exist at the top level.
The reference should either:
- Be changed to "16.1" and "16.2" to match the actual substep numbering
- Or the text should be rephrased to avoid the reference (e.g., "请按照以下两个子步骤进行配置")
| 16. 如果你使用的是 `OpenList (或者公益服务器/自建服务器)`提供的 OAuth 客户端 ID 和密钥,请按照`7.1`和`7.2`进行配置 | |
| 7.1. 在`Use online api`中勾选,表示使用 OpenList 提供的在线 API。 | |
| 7.2. Api url address填写为 `https://api.oplist.org/googleui/renewapi`,如果是`公益服务器/自建服务器`,请填写对应的服务器地址。 | |
| 16. 如果你使用的是 `OpenList (或者公益服务器/自建服务器)`提供的 OAuth 客户端 ID 和密钥,请按照`16.1`和`16.2`进行配置 | |
| 16.1. 在`Use online api`中勾选,表示使用 OpenList 提供的在线 API。 | |
| 16.2. Api url address填写为 `https://api.oplist.org/googleui/renewapi`,如果是`公益服务器/自建服务器`,请填写对应的服务器地址。 |
|
|
||
| ## 3. 在 OpenList 中添加谷歌云盘 { lang="zh-CN" } | ||
|
|
||
| ### 3.1. Configuration { lang="en" } |
Copilot
AI
Dec 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] Inconsistent capitalization in section headings. "Configuration" should be "Configuration Instructions" or "Configuration Details" to better match the Chinese "配置说明" which means "Configuration Instructions/Explanation".
Alternatively, if keeping it simple as "Configuration", then it's acceptable, but there's a mismatch in detail level between the English and Chinese headings.
| ### 3.1. Configuration { lang="en" } | |
| ### 3.1. Configuration Instructions { lang="en" } |
pages/guide/drivers/google_drive.md
Outdated
| 4. 在[指南页面](https://developers.google.com/workspace/drive/api/quickstart/js)中找到`启用API`按钮,点击进入快捷开启界面,点击下一步以及确认后,即可完成开启。 | ||
|
|
||
| ### 2.1. 启用 Google Drive API 的 API | ||
| 5. 也可以访问[谷歌云盘API功能管理界面](https://console.cloud.google.com/apis/library/drive.googleapis.com),在上方找到`启用`按钮,点击后等待启用完成。 | ||
|
|
||
| 1. 在[指南页面](https://developers.google.com/workspace/drive/api/quickstart/js)中找到`启用API`按钮,点击进入快捷开启界面,点击下一步以及确认后,即可完成开启。 | ||
| 6. `配额和系统限制管理`(可选):切换到`配额和系统限制`选项卡,根据你的使用情况和需求,设置合适的配额和限制。 | ||
| ::: |
Copilot
AI
Dec 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The numbering for the Chinese section continues from 4-6 after the English section used 1-3. This creates confusing and inconsistent numbering. The Chinese section should start from 1, matching the structure of the English section.
Should be:
::: zh-CN
1. 在[指南页面](https://developers.google.com/workspace/drive/api/quickstart/js)中找到`启用API`按钮,点击进入快捷开启界面,点击下一步以及确认后,即可完成开启。
2. 也可以访问[谷歌云盘API功能管理界面](https://console.cloud.google.com/apis/library/drive.googleapis.com),在上方找到`启用`按钮,点击后等待启用完成。
3. `配额和系统限制管理`(可选):切换到`配额和系统限制`选项卡,根据你的使用情况和需求,设置合适的配额和限制。There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 1 out of 9 changed files in this pull request and generated 15 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ### 4.2. AccessToken refresh method without own keys { lang="en" } | ||
|
|
||
| ### 4.2.自身没有密钥的情况下,AccessToken刷新的方式 { lang="zh-CN" } |
Copilot
AI
Dec 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove the space before the opening brace. This pattern repeats throughout the file for all language-attributed headings. Apply the fix consistently: {lang="en"} instead of { lang="en" } and {lang="zh-CN"} instead of { lang="zh-CN" }.
| ### 4.2. AccessToken refresh method without own keys { lang="en" } | |
| ### 4.2.自身没有密钥的情况下,AccessToken刷新的方式 { lang="zh-CN" } | |
| ### 4.2. AccessToken refresh method without own keys {lang="en"} | |
| ### 4.2.自身没有密钥的情况下,AccessToken刷新的方式 {lang="zh-CN"} |
|
|
||
| ::: en | ||
|
|
||
| Similar to Aliyun Drive, it is the last string of the official website URL, such as: |
Copilot
AI
Dec 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider using "Alibaba Cloud Drive" instead of "Aliyun Drive" for consistency with official English branding. "Aliyun" is the Chinese brand name, while "Alibaba Cloud" is the official English name.
| Similar to Aliyun Drive, it is the last string of the official website URL, such as: | |
| Similar to Alibaba Cloud Drive, it is the last string of the official website URL, such as: |
|
|
||
| 7. If you use the OAuth Client ID and Secret provided by `OpenList (or Public Server/Self-hosted Server)`, please configure according to `7.1` and `7.2`. | ||
|
|
||
| 7.1. Check `Use online api`, indicating to use the online API provided by OpenList. |
Copilot
AI
Dec 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Inconsistent naming: The checkbox label uses "Use online api" (lowercase) but should be "Use online API" (uppercase) to match proper acronym formatting and the Chinese version "使用在线api".
| ## 4. 关于`Use online api`选项的说明 | ||
| ::: | ||
|
|
||
| ## 4. About `Use online api` option { lang="en" } |
Copilot
AI
Dec 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Inconsistent naming in heading: "Use online api" should be "Use online API" to match proper acronym formatting.
| ## 4. About `Use online api` option { lang="en" } | |
| ## 4. About `Use online API` option { lang="en" } |
|
|
||
| ```mermaid | ||
| --- | ||
| title: How to refresh AccessToken via OnlineAPI? |
Copilot
AI
Dec 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the same mermaid title: "OnlineAPI" should be "Online API" with a space for consistency.
| title: How to refresh AccessToken via OnlineAPI? | |
| title: How to refresh AccessToken via Online API? |
| ### 4.2.自身没有密钥的情况下,AccessToken刷新的方式 | ||
| ::: | ||
|
|
||
| ### 4.2. AccessToken refresh method without own keys { lang="en" } |
Copilot
AI
Dec 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar to line 323, improve the heading grammar: "### 4.2. Access Token refresh method without own keys" → "### 4.2. Refreshing Access Token without Your Own Keys".
| ### 4.2. AccessToken refresh method without own keys { lang="en" } | |
| ### 4.2. Refreshing Access Token without Your Own Keys { lang="en" } |
|
|
||
| ```mermaid | ||
| --- | ||
| title: How to refresh AccessToken via OnlineAPI? |
Copilot
AI
Dec 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mermaid diagram title: "How to refresh AccessToken via OnlineAPI?" should use spaces - "How to refresh Access Token via Online API?".
| title: How to refresh AccessToken via OnlineAPI? | |
| title: How to refresh Access Token via Online API? |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Wangchf <115294077+Wangch29@users.noreply.github.com>
ILoveScratch2
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
很机翻了
|
|
||
| ::: en | ||
|
|
||
| **If you are using OpenList, a public server, or a self-hosted server with built-in keys, you do not need to create this.** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
public server并不能准确说明公益服务器的性质
| ### 2.2. 创建 OAuth 客户端(可选,如果使用OpenList/公益服务器/自建服务器,则不用创建) | ||
| ::: | ||
|
|
||
| ### 2.2. Create OAuth Client (Optional) { lang="en" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
中文大量被省略
|  | ||
|  | ||
|
|
||
| Otherwise, check ☑️ Use the API provided by OpenList. **⚠️ If using a public server/self-hosted server, this uses the built-in Client ID and Client Secret of the public/self-hosted server.** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
不适合用this uses
|
|
||
| ::: en | ||
|
|
||
| 1. Open [OpenList Google Auth Page](https://api.oplist.org/) **⚠️ If using a public server/self-hosted server, please visit the public server/self-hosted server address.** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
缺少定冠词
|
理解并感谢想要贡献的心情,但是这质量我们真的很难办。 |
Description
Provide English translations for parts of the Google Cloud.
提供对google cloud的英文翻译。
Motivation and Context
This change fixes issue #267.
修复了 issue #267.
Checklist / 检查清单
我已阅读 CONTRIBUTING 文档。
我已使用 prettier 或其他适当的格式化工具格式化提交的代码或文档。
我已为所有支持语言(包括中文和英文)更新文档内容。 (若适用)
我已确认编写的文档或代码格式正确, 无语法错误, 拼写错误。
我已相应更新了相关仓库(若适用)。