Skip to content

Commit da3a441

Browse files
authored
feat: finished The Handbook.md
1 parent cc2cf80 commit da3a441

File tree

1 file changed

+25
-25
lines changed

1 file changed

+25
-25
lines changed

docs/documentation/zh/handbook-v2/The Handbook.md

Lines changed: 25 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -8,52 +8,52 @@ handbook: "true"
88

99
## 关于本手册
1010

11-
Over 20 years after its introduction to the programming community, JavaScript is now one of the most widespread cross-platform languages ever created. Starting as a small scripting language for adding trivial interactivity to webpages, JavaScript has grown to be a language of choice for both frontend and backend applications of every size. While the size, scope, and complexity of programs written in JavaScript has grown exponentially, the ability of the JavaScript language to express the relationships between different units of code has not. Combined with JavaScript's rather peculiar runtime semantics, this mismatch between language and program complexity has made JavaScript development a difficult task to manage at scale.
11+
在被引入编程社区 20 多年后,JavaScript 现在是有史以来最广泛使用的跨平台语言之一。JavaScript 最初是一种用于向网页添加微不足道的交互性的小型脚本语言,现已发展成为各种规模的前端和后端应用程序的首选语言。虽然用 JavaScript 编写的程序的大小、范围和复杂性呈指数级增长,但 JavaScript 语言表达不同代码单元之间关系的能力却没有。结合 JavaScript 相当特殊的运行时语义,语言和程序复杂性之间的这种不匹配使得 JavaScript 开发成为一项难以大规模管理的任务。
1212

13-
The most common kinds of errors that programmers write can be described as type errors: a certain kind of value was used where a different kind of value was expected. This could be due to simple typos, a failure to understand the API surface of a library, incorrect assumptions about runtime behavior, or other errors. The goal of TypeScript is to be a static typechecker for JavaScript programs - in other words, a tool that runs before your code runs (static) and ensures that the types of the program are correct (typechecked).
13+
程序员编写的最常见的错误类型可以描述为类型错误:在预期不同类型的值的地方使用了某种类型的值。这可能是由于简单的拼写错误、未能理解库的 API 表面、对运行时行为的错误假设或其他错误。TypeScript 的目标是成为 JavaScript 程序的静态类型检查器 - 换句话说,一个在代码运行之前运行的工具(静态)并确保程序的类型正确(类型检查)。
1414

15-
If you are coming to TypeScript without a JavaScript background, with the intention of TypeScript being your first language, we recommend you first start reading the documentation on either the [Microsoft Learn JavaScript tutorial](https://docs.microsoft.com/javascript/) or read [JavaScript at the Mozilla Web Docs](https://developer.mozilla.org/docs/Web/JavaScript/Guide).
16-
If you have experience in other languages, you should be able to pick up JavaScript syntax quite quickly by reading the handbook.
15+
如果您在没有 JavaScript 背景的情况下使用 TypeScript,并且打算将 TypeScript 作为您的第一语言,我们建议您首先开始阅读 [Microsoft 学习 JavaScript 教程](https://docs.microsoft.com/javascript/) 上的文档或阅读 [Mozilla 网络文档中的 JavaScript](https://developer.mozilla.org/docs/Web/JavaScript/Guide)
16+
如果您有其他语言的经验,您应该能够通过阅读手册很快掌握 JavaScript 语法。
1717

1818
## 本手册的结构是怎样的
1919

20-
The handbook is split into two sections:
20+
手册分为两部分:
2121

22-
- **The Handbook**
22+
- **手册**
2323

24-
The TypeScript Handbook is intended to be a comprehensive document that explains TypeScript to everyday programmers. You can read the handbook by going from top to bottom in the left-hand navigation.
24+
TypeScript 手册旨在成为向日常程序员解释 TypeScript 的综合文档。您可以在左侧导航中从上到下阅读手册。
2525

26-
You should expect each chapter or page to provide you with a strong understanding of the given concepts. The TypeScript Handbook is not a complete language specification, but it is intended to be a comprehensive guide to all of the language's features and behaviors.
26+
您应该期望每一章或每一页都能为您提供对给定概念的深刻理解。TypeScript 手册不是一个完整的语言规范,但它旨在成为该语言所有特性和行为的一个综合指南。
2727

28-
A reader who completes the walkthrough should be able to:
28+
完成演练的读者应该能够:
2929

30-
- Read and understand commonly-used TypeScript syntax and patterns
31-
- Explain the effects of important compiler options
32-
- Correctly predict type system behavior in most cases
30+
- 阅读并理解常用的 TypeScript 语法和模式
31+
- 解释重要编译器选项的影响
32+
- 在大多数情况下正确预测类型系统行为
3333

34-
In the interests of clarity and brevity, the main content of the Handbook will not explore every edge case or minutiae of the features being covered. You can find more details on particular concepts in the reference articles.
34+
为清晰和简洁起见,本手册的主要内容不会探讨所涵盖功能的所有边缘情况或细节。您可以在参考文章中找到有关特定概念的更多详细信息。
3535

36-
- **Reference Files**
36+
- **参考文件**
3737

38-
The reference section below the handbook in the navigation is built to provide a richer understanding of how a particular part of TypeScript works. You can read it top-to-bottom, but each section aims to provide a deeper explanation of a single concept - meaning there is no aim for continuity.
38+
导航中手册下方的参考部分旨在提供对 TypeScript 特定部分如何工作的更丰富的理解。您可以从上到下阅读它,但每个部分都旨在为单个概念提供更深入的解释 - 这意味着没有连续性的目标。
3939

4040
### 非目标
4141

42-
The Handbook is also intended to be a concise document that can be comfortably read in a few hours. Certain topics won't be covered in order to keep things short.
42+
该手册还旨在成为一份简洁的文档,可以在几个小时内轻松阅读。为了简短起见,某些主题不会被涵盖。
4343

44-
Specifically, the Handbook does not fully introduce core JavaScript basics like functions, classes, and closures. Where appropriate, we'll include links to background reading that you can use to read up on those concepts.
44+
具体来说,该手册没有完全介绍核心 JavaScript 基础知识,如函数、类和闭包。在适当的情况下,我们将包含指向背景阅读的链接,您可以使用这些链接来阅读这些概念。
4545

46-
The Handbook also isn't intended to be a replacement for a language specification. In some cases, edge cases or formal descriptions of behavior will be skipped in favor of high-level, easier-to-understand explanations. Instead, there are separate reference pages that more precisely and formally describe many aspects of TypeScript's behavior. The reference pages are not intended for readers unfamiliar with TypeScript, so they may use advanced terminology or reference topics you haven't read about yet.
46+
该手册也不打算替代语言规范。在某些情况下,将跳过边缘情况或对行为的正式描述,转而采用更易于理解的高级解释。相反,有单独的参考页面更准确、更正式地描述了 TypeScript 行为的许多方面。参考页面不适用于不熟悉 TypeScript 的读者,因此他们可能会使用您尚未阅读的高级术语或参考主题。
4747

48-
Finally, the Handbook won't cover how TypeScript interacts with other tools, except where necessary. Topics like how to configure TypeScript with webpack, rollup, parcel, react, babel, closure, lerna, rush, bazel, preact, vue, angular, svelte, jquery, yarn, or npm are out of scope - you can find these resources elsewhere on the web.
48+
最后,除非必要,否则手册不会涵盖 TypeScript 如何与其他工具交互。诸如如何使用 webpackrollupparcelreactbabelclosurelernarushbazelpreactvueangularsveltejqueryyarn npm 配置 TypeScript 等主题超出了范围 - 您可以在其他地方找到这些资源在网上。
4949

5050
## 立即开始
5151

52-
Before getting started with [The Basics](/zh/docs/handbook/2/basic-types.html), we recommend reading one of the following introductory pages. These introductions are intended to highlight key similarities and differences between TypeScript and your favored programming language, and clear up common misconceptions specific to those languages.
52+
在开始使用[基础知识](/zh/docs/handbook/2/basic-types.html)之前,我们建议您阅读以下介绍性页面之一。这些介绍旨在突出 TypeScript 与您喜欢的编程语言之间的主要相似之处和不同之处,并澄清针对这些语言的常见误解。
5353

54-
- [TypeScript for New Programmers](/zh/docs/handbook/typescript-from-scratch.html)
55-
- [TypeScript for JavaScript Programmers](/zh/docs/handbook/typescript-in-5-minutes.html)
56-
- [TypeScript for OOP Programmers](/zh/docs/handbook/typescript-in-5-minutes-oop.html)
57-
- [TypeScript for Functional Programmers](/zh/docs/handbook/typescript-in-5-minutes-func.html)
54+
- [适用于新手程序员的 TypeScript](/zh/docs/handbook/typescript-from-scratch.html)
55+
- [适用于 JavaScript 程序员的 TypeScript](/zh/docs/handbook/typescript-in-5-minutes.html)
56+
- [适用于 OOP 程序员的 TypeScript](/zh/docs/handbook/typescript-in-5-minutes-oop.html)
57+
- [适用于函数式程序员的 TypeScript](/zh/docs/handbook/typescript-in-5-minutes-func.html)
5858

59-
Otherwise, jump to [The Basics](/zh/docs/handbook/2/basic-types.html) or grab a copy in [Epub](/assets/typescript-handbook.epub) or [PDF](/assets/typescript-handbook.pdf) form.
59+
否则,请跳转到[基础知识](/zh/docs/handbook/2/basic-types.html) 或获取一份 [Epub](/assets/typescript-handbook.epub) [PDF](/assets/typescript-handbook.pdf) 格式的副本。

0 commit comments

Comments
 (0)