-
Notifications
You must be signed in to change notification settings - Fork 5k
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
如何写一个好的说明文件 #8665
如何写一个好的说明文件 #8665
Conversation
@lsvih 校对认领 |
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.
@lsvih 校对完毕
|
||
Each TC39 proposal should have a README.md file which explains the purpose of the proposal and its shape at a high level. [This guide](https://github.com/w3ctag/w3ctag.github.io/blob/master/explainers.md) by the W3C TAG has a good introduction for web specifications | ||
每一个 TC39 提案都包括了 README.md 文件来说明该提案目的和高层的发展方向。 | ||
[这一由 W3C TAG 颁布的向导](https://github.com/w3ctag/w3ctag.github.io/blob/master/explainers.md)为网络规范提供了一个良好的入门说明。 |
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.
[这一由 W3C TAG 颁布的向导](https://github.com/w3ctag/w3ctag.github.io/blob/master/explainers.md)为网络规范提供了一个良好的入门说明。 | |
这篇由 W3C TAG 发布的[指南](https://github.com/w3ctag/w3ctag.github.io/blob/master/explainers.md)对网络规范有很好的介绍。 |
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.
好的 这里是我翻译的时候没有注意到同一行的问题 感谢斧正~
@kimberlyohq 感谢校对 |
@lsvih 认领校对 |
@KimYangOfCat 欢迎校对 |
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.
校对了一部分,没有校对完
|
||
Each TC39 proposal should have a README.md file which explains the purpose of the proposal and its shape at a high level. [This guide](https://github.com/w3ctag/w3ctag.github.io/blob/master/explainers.md) by the W3C TAG has a good introduction for web specifications | ||
每一个 TC39 提案都包括了 README.md 文件来说明该提案目的和高层的发展方向。 | ||
[这一由 W3C TAG 颁布的向导](https://github.com/w3ctag/w3ctag.github.io/blob/master/explainers.md)为网络规范提供了一个良好的入门说明。 |
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.
> * 校对者: | ||
|
||
# How to write a good explainer | ||
# 如何写一个好的解释文件 |
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.
# 如何写一个好的解释文件 | |
# 如何写一个好的说明文件 |
关于 explainer 的翻译,我认为意译为 说明文件 ,相比于现在直译为 解释文件 ,阅读体验更好,意思感觉也更准确。
如果你采纳这个校对意见的话,就请全文修改一下,保证所有 explainer 的翻译统一
欢迎另一位校对者参与讨论。
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.
好的 已经修改~
|
||
The rest of this page can be used as a template, to put in your README.md. Not all sections need to be included: This is just a series of optional suggestions. In *italics* is the instructions, and in plain text is the example text. Most of what's here besides the headings should be replaced by your own content. | ||
本页接下来的内容可以作为您的 README.md 文件中的模板 | ||
并不是所有的部分都需要包含在 README.md 文件中, 本文为您提供了一系列可选择的建议。 |
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.
并不是所有的部分都需要包含在 README.md 文件中, 本文为您提供了一系列可选择的建议。 | |
并非模板中的所有章节都需要被引入, 这些只是一系列可选择的建议。 |
和前文有些重复,所以删减一些
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.
@lsvih 校对完毕
@Ashira97 有一说一,本文的翻译质量不是很好,出现了以下问题:
- 全文翻译不统一,前后出现多个翻译版本
- 个别句子理解错误,导致原文与译文所表达的意思天差地别,这是很多刚尝试意译的同学常出现的问题,建议在尝试意译之前,确保直译准确,再尝试使用意译。
- 格式问题,目前你是一句一行的形式进行的翻译,我个人非常不推荐这种方式,虽然不影响最终的 markdown 渲染,但是挺影响源码的阅读体验的。所以最好和原文保持一致,段落分明更好。
希望你接受以上问题并改正,加油嗷~
最后给你个小建议,自己翻译完之后,自己拿着译文阅读一遍,如果你自己能理解译文的内容,那就可以 commit 了,但是如果不能的话,请再多修改一下,这样才能提升自己的翻译水平嗷。
- [JSC]() | ||
- [SpiderMonkey]() | ||
- ... | ||
|
||
## Q&A | ||
## 问题及回答 |
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.
## 问题及回答 | |
## 常见问题 |
感觉似乎不翻译也行,应该没人不知道 Q&A 的意思吧? (哈哈
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.
哈哈 确实
@lsvih 校对完成 |
|
||
This page you're on has some additional advice for how to write an explainer for TC39 proposals, with an outline for content that you might want to include in your proposal's explainer. For some well-written explainers in recent proposals, see [Promise.allSettled](https://github.com/tc39/proposal-promise-allSettled), the [Temporal proposal](https://github.com/tc39/proposal-temporal), or [RegExp Unicode property escapes](https://github.com/tc39/proposal-regexp-unicode-property-escapes). | ||
您浏览指南时会发现其中附加了一些关于如何书写 TC39 提案说明的建议,以及可能想在您的提案说明文件中引用的内容大纲。 |
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 rest of this page can be used as a template, to put in your README.md. Not all sections need to be included: This is just a series of optional suggestions. In *italics* is the instructions, and in plain text is the example text. Most of what's here besides the headings should be replaced by your own content. | ||
本页接下来的内容可以作为您的 README.md 文件中的模板。 |
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.
已修改 谢谢~
|
||
---- | ||
|
||
# Frobnicator | ||
# 制作者 |
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.
Frobnicator 翻译成制作者我觉得有点不太正确?
The word “frobnicate” in IT is a kind of techie slang that describes tweaking or fiddling with physical parts of a technology.
制作者 -> 修改/调整者? 大家怎么看
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.
这个词上下文的语境不是很强,所以确实蛮难翻译的,这里应该指的不是一类人,感觉 调整者
也不是很准确,
原文这个词出现了两次,另一次是在第 97 行,那里将其译作了 装配模块
。
Additionally, web browsers already have a built-in frobnicator which is higher quality.
我查了一下但也没有查到太多实用的信息,如果实在拿不准,我倾向于不翻译。抱歉根据我目前了解到的的信息,我也不知道怎么翻译,
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.
凑个热闹
@kimberlyohq @KimYangOfCat @PassionPenguin 已修改 谢谢三位老师的建议 大家看看还有什么要改的地方吗~ |
译文翻译完成,resolve #8592