Skip to content
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

captions(cn): translate what-s-new-in-react-18 #11

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

QC-L
Copy link
Member

@QC-L QC-L commented Jun 15, 2021


38
00:02:34,170 --> 00:02:35,527
time due to a slow network.
由于网速慢
但网速缺很慢

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
但网速缺很慢
但网速却很慢


45
00:03:04,552 --> 00:03:09,583
The way it works is by rendering all the
components on the server first, then sending
它的工作方式是先渲染服务器上的所有组件,然后发送
其工作原理是先在服务器上的渲染所有组件,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
其工作原理是先在服务器上的渲染所有组件
其工作原理是先在服务器上渲染所有组件


57
00:03:52,800 --> 00:03:57,080
This works by using Suspense, where you’d
say which parts of your application will take
这通过使用 Suspense 起作用,你可以在其中说明应用程序的哪些部分
这方式通过 Suspense 实现,你可以在应用程序中声明哪些部分

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
这方式通过 Suspense 实现,你可以在应用程序中声明哪些部分
这种方式通过 Suspense 实现,你可以在应用程序中声明哪些部分


75
00:05:09,719 --> 00:05:15,210
This ensures that the most critical interactions
are to be repeated as soon as we can hydrate
这确保了最关键的相互作用在我们可以水合后立即重复
这确保了交互可以在我们可以水合完成后,再次被执行

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
这确保了交互可以在我们可以水合完成后,再次被执行
这确保了最关键的交互可以在我们水合完成后,再次被执行

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants