-
Notifications
You must be signed in to change notification settings - Fork 83
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -11,29 +11,101 @@ categories: | |||||||||||||
| - drivers | ||||||||||||||
| --- | ||||||||||||||
|
|
||||||||||||||
| ::: en | ||||||||||||||
|
|
||||||||||||||
| Official website: https://drive.google.com/ | ||||||||||||||
|
|
||||||||||||||
| - Supports Team Drive (Fill in the Team Drive directory ID for the Root Folder ID) | ||||||||||||||
|
|
||||||||||||||
| ::: | ||||||||||||||
| ::: zh-CN | ||||||||||||||
|
|
||||||||||||||
| 官网:https://drive.google.com/ | ||||||||||||||
|
|
||||||||||||||
| - 支持团队盘(根目录ID填写团队盘的目录ID) | ||||||||||||||
|
|
||||||||||||||
| ## 1. 必要条件 | ||||||||||||||
| ::: | ||||||||||||||
|
|
||||||||||||||
| ## 1. Prerequisites { lang="en" } | ||||||||||||||
|
|
||||||||||||||
| ## 1. 必要条件 { lang="zh-CN" } | ||||||||||||||
ILoveScratch2 marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||||||||||
|
|
||||||||||||||
| ::: en | ||||||||||||||
|
|
||||||||||||||
| 1. The machine hosting OpenList must be able to connect to Google Drive. | ||||||||||||||
|
|
||||||||||||||
| 2. You must enable the Google Drive API service. For details, please refer to [Enable Google Drive API](#21-enable-google-drive-api). | ||||||||||||||
|
|
||||||||||||||
| > Detailed steps can be found in [Google Workspace > Google Drive > Quickstart](https://developers.google.com/workspace/drive/api/quickstart/js) | ||||||||||||||
|
|
||||||||||||||
| ::: | ||||||||||||||
| ::: zh-CN | ||||||||||||||
|
|
||||||||||||||
| 1. 搭建 OpenList 服务的机器必须能够连接到 Google 网盘。 | ||||||||||||||
|
|
||||||||||||||
| 2. 必须启用 Google 云盘 API 服务,具体启用方式请参考 [启用 Google Drive API](#21-启用-google-drive-api-的-api)。 | ||||||||||||||
|
|
||||||||||||||
| > 详细步骤可参考 [Google Workspace > Google Drive > 快速入门指南](https://developers.google.com/workspace/drive/api/quickstart/js) | ||||||||||||||
|
|
||||||||||||||
| ## 2. 准备接入 | ||||||||||||||
| ::: | ||||||||||||||
|
|
||||||||||||||
| ## 2. Preparation { lang="en" } | ||||||||||||||
|
|
||||||||||||||
| ## 2. 准备接入 { lang="zh-CN" } | ||||||||||||||
|
|
||||||||||||||
| ### 2.1. Enable Google Drive API { lang="en" } | ||||||||||||||
|
|
||||||||||||||
| ### 2.1. 启用 Google Drive API 的 API { lang="zh-CN" } | ||||||||||||||
|
|
||||||||||||||
| ::: en | ||||||||||||||
|
|
||||||||||||||
| 1. Find the `Enable the API` button on the [Guide Page](https://developers.google.com/workspace/drive/api/quickstart/js), click to enter the quick enable interface, click Next and Confirm to complete the activation. | ||||||||||||||
|
|
||||||||||||||
| ### 2.1. 启用 Google Drive API 的 API | ||||||||||||||
| 2. You can also visit the [Google Drive API Management Interface](https://console.cloud.google.com/apis/library/drive.googleapis.com), find the `Enable` button at the top, and click it to wait for the enablement to complete. | ||||||||||||||
|
|
||||||||||||||
| 3. `Quotas and System Limits Management` (Optional): Switch to the `Quotas` tab and set appropriate quotas and limits according to your usage and needs. | ||||||||||||||
|
|
||||||||||||||
| ::: | ||||||||||||||
| ::: 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. `配额和系统限制管理`(可选):切换到`配额和系统限制`选项卡,根据你的使用情况和需求,设置合适的配额和限制。 | ||||||||||||||
|
|
||||||||||||||
| ### 2.2. 创建 OAuth 客户端(可选,如果使用OpenList/公益服务器/自建服务器,则不用创建) | ||||||||||||||
| ::: | ||||||||||||||
|
|
||||||||||||||
| ### 2.2. Create OAuth Client (Optional) { lang="en" } | ||||||||||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 中文大量被省略 |
||||||||||||||
|
|
||||||||||||||
| ### 2.2. 创建 OAuth 客户端(可选,如果使用OpenList/公益服务器/自建服务器,则不用创建) { lang="zh-CN" } | ||||||||||||||
|
|
||||||||||||||
| ::: 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.** | ||||||||||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||||||||||||||
|
|
||||||||||||||
| 1. In the [Credentials Interface](https://console.cloud.google.com/apis/credentials?hl=en), click the `Create Credentials` drop-down menu, select and click `OAuth client ID`. | ||||||||||||||
|
|
||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| 2. In the pop-up window, select `Web application` and fill in the application name. | ||||||||||||||
|
|
||||||||||||||
| 3. In `Authorized redirect URIs`, fill in `https://api.oplist.org/googleui/callback`. If it is a self-built or public service, please fill in the corresponding domain name, such as `https://your-domain.com/googleui/callback`. | ||||||||||||||
|
|
||||||||||||||
| 4. Click the `Create` button to complete the creation of the OAuth client. Note: Please copy and save the `Client ID` and `Client Secret`, which will be needed later. | ||||||||||||||
|
|
||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| 5. Add yourself to the test users. Find the `OAuth consent screen` menu on the left, enter it, find the `+ Add Users` button under `Test users`, click it, enter your Google account email address, and click Add. | ||||||||||||||
|
|
||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| 6. After testing, you can publish the application. Find the `OAuth consent screen` menu on the left, enter it, find the `Publish App` button under `Publishing status`, click it, and confirm the publication to complete the application publication. | ||||||||||||||
|
|
||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| ::: | ||||||||||||||
| ::: zh-CN | ||||||||||||||
|
|
||||||||||||||
| 1. 在[凭据界面](https://console.cloud.google.com/apis/credentials?hl=zh-cn)中,点击`创建凭据`下拉菜单,选择和点击`OAuth 客户端 ID` | ||||||||||||||
|
|
||||||||||||||
|
|
@@ -55,7 +127,50 @@ categories: | |||||||||||||
|
|
||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| ### 2.3. 获取`访问密钥`和`刷新密钥` | ||||||||||||||
| ::: | ||||||||||||||
|
|
||||||||||||||
| ### 2.3. Get `Access Token` and `Refresh Token` { lang="en" } | ||||||||||||||
|
|
||||||||||||||
| ### 2.3. 获取`访问密钥`和`刷新密钥` { lang="zh-CN" } | ||||||||||||||
|
|
||||||||||||||
| ::: 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.** | ||||||||||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 缺少定冠词 |
||||||||||||||
|
|
||||||||||||||
| 2. Select `GoogleDrive Login` in the drop-down box on the page. | ||||||||||||||
|
|
||||||||||||||
|  | ||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| 3. If you created an OAuth Client ID in the previous steps, please enter the `Client ID` and `Client Secret` you just created in the input box below. | ||||||||||||||
|
|
||||||||||||||
|  | ||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| 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.** | ||||||||||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 不适合用 |
||||||||||||||
|
|
||||||||||||||
|  | ||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| 4. Click the `Get Authorization` button. The system will jump to the Google authorization page. Log in to your Google account and authorize OpenList to access your Google Drive. | ||||||||||||||
|
|
||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| 5. If the prompt `This app is not verified by Google` appears, please click `Advanced` and then click `Go to oplist.org (unsafe)` to continue. (If it is a public server/self-hosted server, the domain name here is subject to the actual public service domain name, please identify it carefully). | ||||||||||||||
|
|
||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| 6. Please pay attention to the permission information on the authorization page (in the red box below), and ensure that it **only** accesses your **Google Drive files**. If you find that the permission is not just to access **Google Drive** in the public service, please raise an issue at [openlistteam/docs/issues](https://github.com/openlistteam/docs/issues). | ||||||||||||||
|
|
||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| 7. After successful authorization, the system will return a `Refresh Token` and `Access Token`. Please copy and save the token for use in subsequent configurations. | ||||||||||||||
|
|
||||||||||||||
|  | ||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| ::: | ||||||||||||||
| ::: zh-CN | ||||||||||||||
|
|
||||||||||||||
| 1. 打开[OpenList Google 授权页面](https://api.oplist.org/) **⚠️如果使用公益服务器/自建服务器,请访问公益服务器/自建服务器** | ||||||||||||||
|
|
||||||||||||||
|
|
@@ -91,17 +206,78 @@ categories: | |||||||||||||
|  | ||||||||||||||
|  | ||||||||||||||
|
|
||||||||||||||
| ## 3. 在 OpenList 中添加谷歌云盘 | ||||||||||||||
| ::: | ||||||||||||||
|
|
||||||||||||||
| ## 3. Add Google Drive in OpenList { lang="en" } | ||||||||||||||
|
|
||||||||||||||
| ## 3. 在 OpenList 中添加谷歌云盘 { lang="zh-CN" } | ||||||||||||||
|
|
||||||||||||||
| ### 3.1. Configuration { lang="en" } | ||||||||||||||
|
||||||||||||||
| ### 3.1. Configuration { lang="en" } | |
| ### 3.1. Configuration Instructions { 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.
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: |
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".
ILoveScratch2 marked this conversation as resolved.
Show resolved
Hide resolved
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" } |
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 English heading should be updated for clarity and grammatical correctness. Consider: "### 4.1. Access Token refresh method with own keys" → "### 4.1. Refreshing Access Token with Your Own Keys" for better readability and grammar.
| ### 4.1. AccessToken refresh method with own keys { lang="en" } | |
| ### 4.1. Refreshing Access Token with Your 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.
Inconsistent capitalization: "AccessToken" should have a space - "Access Token" - for readability. This also applies to lines 351, 359, and throughout the document where the term appears.
| ### 4.1. AccessToken refresh method with own keys { lang="en" } | |
| ### 4.1. 自身有密钥的情况下,AccessToken刷新的方式 { lang="zh-CN" } | |
| ### 4.1. Access Token refresh method with own keys { lang="en" } | |
| ### 4.1. 自身有密钥的情况下,Access Token刷新的方式 { 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.
Same issue: "AccessToken" should be "Access Token" with a space.
| ### 4.2. AccessToken refresh method without own keys { lang="en" } | |
| ### 4.2. Access Token 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" } |
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"} |
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? |
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? |
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 mermaid diagram participant label, "OnlineAPI" should be "Online API" with a space for consistency with the rest of the documentation.
Uh oh!
There was an error while loading. Please reload this page.