mirror of
https://github.com/element-plus/element-plus.git
synced 2024-12-15 02:40:46 +08:00
chore: update guide (#7464)
This commit is contained in:
三咲智子
GitHub
parent
8a52c57d7a
commit
99610f328b
2
.github/CONTRIBUTING.en-US.md
vendored
2
.github/CONTRIBUTING.en-US.md
vendored
@ -18,7 +18,7 @@ We are excited that you are interested in contributing to Element Plus. Before s
|
||||
|
||||
- Fork this repository to your own account. Do not create branches here.
|
||||
|
||||
- Commit info should be formatted as `type(scope): info about commit`. (e.g. `fix(components): [el-scrollbar] fix xxx bug`)
|
||||
- Commit info should be formatted as `type(scope): info about commit`. (e.g. `fix(components): [scrollbar] fix xxx bug`)
|
||||
|
||||
1. type: type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, release, style, test, improvement].
|
||||
|
||||
|
||||
2
.github/CONTRIBUTING.es.md
vendored
2
.github/CONTRIBUTING.es.md
vendored
@ -18,7 +18,7 @@ Estamos orgullosos de que usted esta interesado en contribuir al proyecto `Eleme
|
||||
|
||||
- Crea una bifurcación (“fork”) del repositorio a su propia cuenta en github.com. Por favor no crea ramas nuevas aquí.
|
||||
|
||||
- El formato de la información de envío debe ser `type(scope): info about commit`. (por ejemplo, `fix(components): [el-scrollbar] fix xxx bug`)
|
||||
- El formato de la información de envío debe ser `type(scope): info about commit`. (por ejemplo, `fix(components): [scrollbar] fix xxx bug`)
|
||||
|
||||
1. Tipo: el tipo debe ser uno de [build, chore, ci, docs, feat, fix, perf, refactor, revert, release, style, test, improvement].
|
||||
|
||||
|
||||
2
.github/CONTRIBUTING.fr-FR.md
vendored
2
.github/CONTRIBUTING.fr-FR.md
vendored
@ -18,7 +18,7 @@ Nous sommes ravis que vous souhaitiez contribuer à Element Plus. Avant de soume
|
||||
|
||||
- Faites un fork de ce dépôt vers votre compte. Ne créez pas de branches ici.
|
||||
|
||||
- les informations soumises doivent être présentées sous la forme `type(scope): info about commit`.(par exemple, `fix(components): [el-scrollbar] fix xxx bug`)
|
||||
- les informations soumises doivent être présentées sous la forme `type(scope): info about commit`.(par exemple, `fix(components): [scrollbar] fix xxx bug`)
|
||||
|
||||
1. Type: le type doit être l'un des [build, chore, ci, docs, feat, fix, perf, refactor, revert, release, style, test, improvement].
|
||||
|
||||
|
||||
2
.github/CONTRIBUTING.zh-CN.md
vendored
2
.github/CONTRIBUTING.zh-CN.md
vendored
@ -18,7 +18,7 @@ Element Plus 的成长离不开大家的支持，如果你愿意为 Element Plus
|
||||
|
||||
- 请先 fork 一份到自己的项目下，不要直接在仓库下建分支。
|
||||
|
||||
- commit 信息要以 `type(scope): 描述信息` 的形式填写，例如 `fix(components): [el-scrollbar] fix xxx bug`。
|
||||
- commit 信息要以 `type(scope): 描述信息` 的形式填写，例如 `fix(components): [scrollbar] fix xxx bug`。
|
||||
|
||||
1. type: 必须是 build, chore, ci, docs, feat, fix, perf, refactor, revert, release, style, test, improvement 其中的一个。
|
||||
|
||||
|
||||
@ -6,7 +6,9 @@ In this chapter, we will discuss how to help translating the documentation of El
|
||||
|
||||
## Background
|
||||
|
||||
Before we did the upgrade of the documentation architecture, each documentation update needs 5 languages, which most of the contributors use online translator for their non-native languages, sometimes it would be not only inaccurate but also stressful to them.
|
||||
Before we did the upgrade of the documentation architecture, each documentation update needs 5 languages,
|
||||
which most of the contributors use online translator for their non-native languages,
|
||||
sometimes it would be not only inaccurate but also stressful to them.
|
||||
|
||||
So we decided to give the documentation site an upgrade.
|
||||
|
||||
@ -28,4 +30,5 @@ After you submit your work, it would be online once the translation is approved
|
||||
|
||||
## How can I become a proofreader?
|
||||
|
||||
You can [raise an issue](https://crowdin.com/project/element-plus/discussions) on Crowdin to us for becoming a proofreader of the language you wish to be.
|
||||
You can [raise an issue](https://crowdin.com/project/element-plus/discussions) on Crowdin to us for
|
||||
becoming a proofreader of the language you wish to be.
|
||||
|
||||
@ -6,19 +6,21 @@
|
||||
|
||||
## 大背景
|
||||
|
||||
在给文档站做升级之前，每一次文档改动都需要改五种语言，大部分的贡献者都只会自己的母语和一门外语，大部分的贡献者也会寻求翻译器来翻译其它自己不熟悉的外语，而翻译器翻译的内容对母语者可能造成误解，并且对贡献者来说也是一件麻烦的事情。
|
||||
在给文档站做升级之前，每一次文档改动都需要改五种语言，大部分的贡献者都只会自己的母语和一门外语，
|
||||
大部分的贡献者也会寻求翻译器来翻译其它自己不熟悉的外语，而翻译器翻译的内容对母语者可能造成误解，
|
||||
并且对贡献者来说也是一件麻烦的事情。
|
||||
|
||||
所以我们决定把文档站做升级。
|
||||
|
||||
- 从 Webpack 升级到了 Vite
|
||||
- 从手动维护的到自动化
|
||||
|
||||
我们采用了[Crowdin](https://crowdin.com)作为自动化的第一步来升级文档站。
|
||||
我们采用了 [Crowdin](https://crowdin.com) 作为自动化的第一步来升级文档站。
|
||||
|
||||
## 我怎么才能帮忙贡献翻译的内容？
|
||||
|
||||
1. 首先在 [Crowdin](https://crowdin.com) 上创建一个账号， 这里我们推荐使用 GitHub 的账号做第三方登录，方便快捷。
|
||||
2. 去到 [Element Plus](https://crowdin.com/project/element-plus) 项目.
|
||||
2. 去到 [Element Plus](https://crowdin.com/project/element-plus) 项目。
|
||||
3. 选择你想要贡献翻译的语言。
|
||||
4. 选择你想要贡献翻译的具体文件。
|
||||
5. 翻译。
|
||||
@ -26,6 +28,6 @@
|
||||
以上就是如何参与贡献翻译的全部步骤，Crowdin 的界面和交互设计非常的人性化，在使用过程中应该不会遇到太多难题。
|
||||
当你提交完你的翻译之后，它会在翻译审核通过之后上线。
|
||||
|
||||
## 我怎么样能成为翻译审核？
|
||||
## 我怎么样能帮助翻译审核？
|
||||
|
||||
你可以在 Crowdin 里[提一个 issue](https://crowdin.com/project/element-plus/discussions) 来申请成为一个翻译审核。
|
||||
你可以在 Crowdin 里 [提一个 issue](https://crowdin.com/project/element-plus/discussions) 来申请成为一个翻译审核员。
|
||||
|
||||
Loading…
Reference in New Issue
Block a user