-
Notifications
You must be signed in to change notification settings - Fork 59
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
doc: translate /about pages #238
Conversation
✅ Deploy Preview for cue ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
@myitcv
|
Will do! Just back from holiday so catching up on things. |
content/zh/docs/about/_index.md
Outdated
|
||
> 译者注:原文中使用的 `Schema`,虽然直译应为 `模式`,但是个人认为此翻译并不是特别好理解。 | ||
> 于是与 CUE 的维护者之一 [@myitcv](https://github.com/myitcv) 进行了 [讨论](https://cuelang.slack.com/archives/C032M6T7WAG/p1645762537397239) , | ||
> 他认为 `specification` 或 `struct` 会更接近,因此下文将 `Schema` 翻译为 `规范`。 |
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.
这块修改一下,将后面的改为 Schema
?
content/zh/docs/about/_index.md
Outdated
相反的,采用了基于继承的覆盖的模型。 | ||
但是它的复杂性使得早期的工具难以实现,也从未实现,复制其模型的 GCL 后代也是如此。 | ||
|
||
CUE 回归最初使用基于约束的的想法,也努力吸收 15 年使用 GCL 的经验教训, |
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.
CUE 回到了使用基于约束的最初想法,并努力从使用 GCL 15 年的经验中吸取教训。同时,也从后代中吸取了经验教训以及完全不同的配置方法。
* add chinese translation of /about Signed-off-by: hezhaoyang <gmzhaoyang@gmail.com>
Co-authored-by: Tianxin Dong <wuwuglu19@gmail.com> Signed-off-by: hezhaoyang <gmzhaoyang@gmail.com>
Co-authored-by: Tianxin Dong <wuwuglu19@gmail.com> Signed-off-by: hezhaoyang <gmzhaoyang@gmail.com>
* do not translate `Schema` any more * make some sentences more smooth and fluent Signed-off-by: hezhaoyang <gmzhaoyang@gmail.com>
### 工具 | ||
|
||
自动化是关键。 | ||
o |
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.
What's this?
这些实际上是像人类语言这样不规则和复杂的非常大的配置,这些系统一个特点就是定义的 类型 或 约束条件 可以验证数据,并减少重复使用的代码块。 | ||
总的来说,这种方法非常适合云上的配置。 | ||
|
||
然而,GCL 的早期设计追求的是更简单的东西,巧合的是它与图归一化的概念不相容。 |
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.
然而,GCL 的早期设计追求的是更简单的东西,巧合的是它与图归一化的概念不相容。 | |
然而,GCL 的早期设计追求的是更简单的东西,巧的是这种设计与图归一化的概念不相容。这种简单的设计后来也被证明是远远不够的,但此时想要转向之前的设计已经太晚了。与图归一化相反的,GCL 采用了基于继承的覆盖模型。这种模型的复杂性使得早期的工具难以实现,也从未实现。复制其模型的 GCL 后代也是如此。 |
|
||
### 类型 和 值 | ||
|
||
CUE 没有区分 值 和 类型,这是一个超强的概念,能让 CUE 定义非常详细的约束条件,同时也极大地简化了很多事情: |
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.
我建议只在中英文之间加空格,其他特殊意义的值可以用代码框,
如: CUE 没有区分值
和类型
。
|
||
这样的方法比全面继承的方法更有局限性: | ||
它不太可能复用已存在的配置。但另一方面,它在移除引用时更强大。 | ||
比如,假设一组工作中的每个工作都需要使用特定的模板, |
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.
BTW,为什么每个断句都要换行?
只要想要减少重复代码块,`cue` 工具就可以帮助来自动重写配置。 | ||
请到 [Kubernetes tutorial](/docs/tutorials/kubernetes) 的 Quick and Dirty | ||
这一节查看关于使用 `import` 和 `trim` 工具的例子。 | ||
使用这个方法,可以清理成千上万行。 |
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.
使用这个方法,可以清理成千上万行。 | |
使用这个方法,可以清理成千上万行代码。 |
Hi all - it has been some time since we looked at translating some of the content for cuelang.org. Since then we have upgrade to a new improved version: https://cuelang.org (same address). Thank you for the contributions here, and apologies we never really got to a point where we could consider the work "done". I have opened cue-lang/cue#3107 as a tracking issue for supporting translations in the new site and suggest we pick up the conversation there. |
Add Chinese translation of /about