From 2cf25ad9c298c4720fe709568bff0c61d78adc9d Mon Sep 17 00:00:00 2001 From: pan93412 Date: Thu, 21 Nov 2019 21:24:55 +0800 Subject: [PATCH 1/5] l10n(zh_TW): update base Signed-off-by: pan93412 --- locale/zh-tw/about/index.md | 69 ++++++++++++ locale/zh-tw/about/releases.md | 25 +++++ locale/zh-tw/docs/meta/topics/dependencies.md | 102 ++++++++++++++++++ 3 files changed, 196 insertions(+) create mode 100644 locale/zh-tw/about/index.md create mode 100644 locale/zh-tw/about/releases.md create mode 100644 locale/zh-tw/docs/meta/topics/dependencies.md diff --git a/locale/zh-tw/about/index.md b/locale/zh-tw/about/index.md new file mode 100644 index 0000000000000..188a160f95cde --- /dev/null +++ b/locale/zh-tw/about/index.md @@ -0,0 +1,69 @@ +--- +layout: about.hbs +title: About +trademark: Trademark +--- + +# About Node.js® + +As an asynchronous event-driven JavaScript runtime, Node.js is designed to build +scalable network applications. In the following "hello world" example, many +connections can be handled concurrently. Upon each connection, the callback is +fired, but if there is no work to be done, Node.js will sleep. + +```javascript +const http = require('http'); + +const hostname = '127.0.0.1'; +const port = 3000; + +const server = http.createServer((req, res) => { + res.statusCode = 200; + res.setHeader('Content-Type', 'text/plain'); + res.end('Hello World\n'); +}); + +server.listen(port, hostname, () => { + console.log(`Server running at http://${hostname}:${port}/`); +}); +``` + +This is in contrast to today's more common concurrency model, in which OS threads +are employed. Thread-based networking is relatively inefficient and very +difficult to use. Furthermore, users of Node.js are free from worries of +dead-locking the process, since there are no locks. Almost no function in +Node.js directly performs I/O, so the process never blocks. Because nothing blocks, scalable systems are very reasonable to develop in Node.js. + +If some of this language is unfamiliar, there is a full article on +[Blocking vs. Non-Blocking][]. + +--- + +Node.js is similar in design to, and influenced by, systems like Ruby's +[Event Machine][] and Python's [Twisted][]. Node.js takes the event model a bit +further. It presents an [event loop][] as a runtime construct instead of as a library. In other systems, there is always a blocking call to start the +event-loop. +Typically, behavior is defined through callbacks at the beginning of a script, and +at the end a server is started through a blocking call like +`EventMachine::run()`. In Node.js, there is no such start-the-event-loop call. +Node.js simply enters the event loop after executing the input script. Node.js +exits the event loop when there are no more callbacks to perform. This behavior +is like browser JavaScript — the event loop is hidden from the user. + +HTTP is a first-class citizen in Node.js, designed with streaming and low +latency in mind. This makes Node.js well suited for the foundation of a web +library or framework. + +Node.js being designed without threads doesn't mean you can't take +advantage of multiple cores in your environment. Child processes can be spawned +by using our [`child_process.fork()`][] API, and are designed to be easy to +communicate with. Built upon that same interface is the [`cluster`][] module, +which allows you to share sockets between processes to enable load balancing +over your cores. + +[Blocking vs. Non-Blocking]: /en/docs/guides/blocking-vs-non-blocking/ +[`child_process.fork()`]: https://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options +[`cluster`]: https://nodejs.org/api/cluster.html +[event loop]: /en/docs/guides/event-loop-timers-and-nexttick/ +[Event Machine]: https://github.com/eventmachine/eventmachine +[Twisted]: https://twistedmatrix.com/trac/ diff --git a/locale/zh-tw/about/releases.md b/locale/zh-tw/about/releases.md new file mode 100644 index 0000000000000..549d7ffede0e2 --- /dev/null +++ b/locale/zh-tw/about/releases.md @@ -0,0 +1,25 @@ +--- +layout: about-release-schedule.hbs +title: Releases +statuses: + maintenance: 'Maintenance LTS' + active: 'Active LTS' + current: 'Current' + pending: 'Pending' +columns: + - 'Release' + - 'Status' + - 'Codename' + - 'Initial Release' + - 'Active LTS Start' + - 'Maintenance LTS Start' + - 'End-of-life' +schedule-footer: Dates are subject to change. +--- + +# Releases + +Major Node.js versions enter _Current_ release status for six months, which gives library authors time to add support for them. +After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to _Active LTS_ status and are ready for general use. +_LTS_ release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. +Production applications should only use _Active LTS_ or _Maintenance LTS_ releases. diff --git a/locale/zh-tw/docs/meta/topics/dependencies.md b/locale/zh-tw/docs/meta/topics/dependencies.md new file mode 100644 index 0000000000000..d34e0ba34dce6 --- /dev/null +++ b/locale/zh-tw/docs/meta/topics/dependencies.md @@ -0,0 +1,102 @@ +--- +title: Dependencies +layout: docs.hbs +--- + +# Dependencies + +There are several dependencies that Node.js relies on to work the way it does. + +* [Libraries](#libraries) + * [V8](#v8) + * [libuv](#libuv) + * [http-parser](#http-parser) + * [c-ares](#c-ares) + * [OpenSSL](#openssl) + * [zlib](#zlib) +* [Tools](#tools) + * [npm](#npm) + * [gyp](#gyp) + * [gtest](#gtest) + +## Libraries + +### V8 + +The V8 library provides Node.js with a JavaScript engine, which Node.js +controls via the V8 C++ API. V8 is maintained by Google, for use in Chrome. + +* [Documentation](https://v8docs.nodesource.com/) + +### libuv + +Another important dependency is libuv, a C library that is used to abstract +non-blocking I/O operations to a consistent interface across all supported +platforms. It provides mechanisms to handle file system, DNS, network, child +processes, pipes, signal handling, polling and streaming. It also includes a +thread pool for offloading work for some things that can't be done +asynchronously at the operating system level. + +* [Documentation](http://docs.libuv.org/) + +### llhttp + +HTTP parsing is handled by a lightweight TypeScript and C library called llhttp. +It is designed to not make any syscalls or allocations, so it has a very small +per-request memory footprint. + +* [Documentation](https://github.com/joyent/http-parser/) + +### c-ares + +For some asynchronous DNS requests, Node.js uses a C library called c-ares. +It is exposed through the DNS module in JavaScript as the `resolve()` family of +functions. The `lookup()` function, which is what the rest of core uses, makes +use of threaded `getaddrinfo(3)` calls in libuv. The reason for this is that +c-ares supports /etc/hosts, /etc/resolv.conf and /etc/svc.conf, but not things +like mDNS. + +* [Documentation](https://c-ares.haxx.se/docs.html) + +### OpenSSL + +OpenSSL is used extensively in both the `tls` and `crypto` modules. It provides +battle-tested implementations of many cryptographic functions that the modern +web relies on for security. + +* [Documentation](https://www.openssl.org/docs/) + +### zlib + +For fast compression and decompression, Node.js relies on the industry-standard +zlib library, also known for its use in gzip and libpng. Node.js uses zlib to +create sync, async and streaming compression and decompression interfaces. + +* [Documentation](https://www.zlib.net/manual.html) + +## Tools + +### npm + +Node.js is all about modularity, and with that comes the need for a quality +package manager; for this purpose, npm was made. With npm comes the largest +selection of community-created packages of any programming ecosystem, +which makes building Node.js apps quick and easy. + +* [Documentation](https://docs.npmjs.com/) + +### gyp + +The build system is handled by gyp, a python-based project generator copied +from V8. It can generate project files for use with build systems across many +platforms. Node.js requires a build system because large parts of it — and its +dependencies — are written in languages that require compilation. + +* [Documentation](https://gyp.gsrc.io/docs/UserDocumentation.md) + +### gtest + +Native code can be tested using gtest, which is taken from Chromium. It allows +testing C/C++ without needing an existing node executable to bootstrap from. + +* [Documentation](https://code.google.com/p/googletest/wiki/V1_7_Documentation) From c335121ea51574c14dee8c7d0e1df249021713b9 Mon Sep 17 00:00:00 2001 From: pan93412 Date: Thu, 21 Nov 2019 20:44:34 +0800 Subject: [PATCH 2/5] l10n(zh_TW): update & improve translations Signed-off-by: pan93412 --- locale/zh-tw/404.md | 4 +- locale/zh-tw/about/index.md | 22 +++----- locale/zh-tw/about/releases.md | 36 ++++++------ locale/zh-tw/docs/meta/topics/dependencies.md | 55 +++++++++++++------ locale/zh-tw/download/current.md | 22 ++++---- locale/zh-tw/download/index.md | 24 ++++---- locale/zh-tw/download/package-manager.md | 22 ++++---- locale/zh-tw/download/releases.md | 4 +- locale/zh-tw/index.md | 8 +-- locale/zh-tw/security.md | 4 +- locale/zh-tw/site.json | 34 ++++++------ 11 files changed, 125 insertions(+), 110 deletions(-) diff --git a/locale/zh-tw/404.md b/locale/zh-tw/404.md index 792a18a0f39bc..407bf446808bd 100644 --- a/locale/zh-tw/404.md +++ b/locale/zh-tw/404.md @@ -4,6 +4,6 @@ permalink: false title: 404 --- -## 404: 找不到網頁 +## 404：找不到網頁 -### ENOENT: 找不到文件或目錄 +### ENOENT：無此檔案或目錄 diff --git a/locale/zh-tw/about/index.md b/locale/zh-tw/about/index.md index 188a160f95cde..27b1e8160bc27 100644 --- a/locale/zh-tw/about/index.md +++ b/locale/zh-tw/about/index.md @@ -1,15 +1,12 @@ --- layout: about.hbs -title: About -trademark: Trademark +title: 關於 +trademark: 商標 --- -# About Node.js® +# 關於 Node.js® -As an asynchronous event-driven JavaScript runtime, Node.js is designed to build -scalable network applications. In the following "hello world" example, many -connections can be handled concurrently. Upon each connection, the callback is -fired, but if there is no work to be done, Node.js will sleep. +作為一個異步事件驅動的 JavaScript 執行階段，Node.js 設計來建構可擴充的網路應用程式。下方的「Hello World」範例中，多個連線皆能並行處理。一當每個連線建立後，會先執行回呼函式，但如果沒有需要作的事情，Node.js 則會休眠。 ```javascript const http = require('http'); @@ -24,7 +21,7 @@ const server = http.createServer((req, res) => { }); server.listen(port, hostname, () => { - console.log(`Server running at http://${hostname}:${port}/`); + console.log(`伺服器正在 http://${hostname}:${port}/ 運作`); }); ``` @@ -34,14 +31,13 @@ difficult to use. Furthermore, users of Node.js are free from worries of dead-locking the process, since there are no locks. Almost no function in Node.js directly performs I/O, so the process never blocks. Because nothing blocks, scalable systems are very reasonable to develop in Node.js. -If some of this language is unfamiliar, there is a full article on -[Blocking vs. Non-Blocking][]. +如果不熟悉這門語言的一些地方，在 [阻塞式與非阻塞式的比較][] 這篇文章有完整的解釋。 --- Node.js is similar in design to, and influenced by, systems like Ruby's [Event Machine][] and Python's [Twisted][]. Node.js takes the event model a bit -further. It presents an [event loop][] as a runtime construct instead of as a library. In other systems, there is always a blocking call to start the +further. It presents an [事件循環][] as a runtime construct instead of as a library. In other systems, there is always a blocking call to start the event-loop. Typically, behavior is defined through callbacks at the beginning of a script, and at the end a server is started through a blocking call like @@ -61,9 +57,9 @@ communicate with. Built upon that same interface is the [`cluster`][] module, which allows you to share sockets between processes to enable load balancing over your cores. -[Blocking vs. Non-Blocking]: /en/docs/guides/blocking-vs-non-blocking/ +[阻塞式與非阻塞式的比較]: /en/docs/guides/blocking-vs-non-blocking/ [`child_process.fork()`]: https://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options [`cluster`]: https://nodejs.org/api/cluster.html -[event loop]: /en/docs/guides/event-loop-timers-and-nexttick/ +[事件循環]: /en/docs/guides/event-loop-timers-and-nexttick/ [Event Machine]: https://github.com/eventmachine/eventmachine [Twisted]: https://twistedmatrix.com/trac/ diff --git a/locale/zh-tw/about/releases.md b/locale/zh-tw/about/releases.md index 549d7ffede0e2..bf2e0aed6f659 100644 --- a/locale/zh-tw/about/releases.md +++ b/locale/zh-tw/about/releases.md @@ -1,25 +1,25 @@ --- layout: about-release-schedule.hbs -title: Releases +title: 發布版 statuses: - maintenance: 'Maintenance LTS' - active: 'Active LTS' - current: 'Current' - pending: 'Pending' + maintenance: '維護 LTS' + active: '活躍 LTS' + current: '最新版' + pending: '待發布版' columns: - - 'Release' - - 'Status' - - 'Codename' - - 'Initial Release' - - 'Active LTS Start' - - 'Maintenance LTS Start' - - 'End-of-life' -schedule-footer: Dates are subject to change. + - '發布版' + - '狀態' + - '內部代號' + - '初發布版' + - '活躍 LTS 週期開始' + - '維護 LTS 週期開始' + - '結束生命週期' +schedule-footer: 日期會隨時變更。 --- -# Releases +# 發布版 -Major Node.js versions enter _Current_ release status for six months, which gives library authors time to add support for them. -After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to _Active LTS_ status and are ready for general use. -_LTS_ release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. -Production applications should only use _Active LTS_ or _Maintenance LTS_ releases. +主要 Node.js 版本會進入為時 6 個月的 _最新版_ 發布狀態，以讓函式庫作者有時間支援。 +6 個月後，奇數版號（9、11 等等）會不再受支援，而偶數版號（10、12 等等）會移至 _活躍 LTS_ 狀態並準備日常使用。 +_LTS_ 發布版狀態指「長期維護」，通常會保證嚴重臭蟲會在 30 個月內修正。 +生產環境的應用程式應只使用 _活躍 LTS_ 或 _維護 LTS_ 版本。 diff --git a/locale/zh-tw/docs/meta/topics/dependencies.md b/locale/zh-tw/docs/meta/topics/dependencies.md index d34e0ba34dce6..a3fcf27f10392 100644 --- a/locale/zh-tw/docs/meta/topics/dependencies.md +++ b/locale/zh-tw/docs/meta/topics/dependencies.md @@ -1,32 +1,51 @@ --- -title: Dependencies +title: 依賴項目 layout: docs.hbs --- -# Dependencies +# 依賴項目 -There are several dependencies that Node.js relies on to work the way it does. +這裡列出了多個 Node.js 所仰賴的依賴項目，以讓 Node.js 能如預期般運作。 -* [Libraries](#libraries) +* [函式庫](#libraries) * [V8](#v8) * [libuv](#libuv) * [http-parser](#http-parser) * [c-ares](#c-ares) * [OpenSSL](#openssl) * [zlib](#zlib) -* [Tools](#tools) +* [工具](#tools) * [npm](#npm) * [gyp](#gyp) * [gtest](#gtest) -## Libraries + + +## 函式庫 ### V8 -The V8 library provides Node.js with a JavaScript engine, which Node.js -controls via the V8 C++ API. V8 is maintained by Google, for use in Chrome. +V8 函式庫為 Node.js 提供了 JavaScript 引擎（Node.js 使用 V8 C++ API 控制）。 +V8 是 Google 維護用來在 Chrome 使用的。 -* [Documentation](https://v8docs.nodesource.com/) +* [文件](https://v8docs.nodesource.com/) ### libuv @@ -37,7 +56,7 @@ processes, pipes, signal handling, polling and streaming. It also includes a thread pool for offloading work for some things that can't be done asynchronously at the operating system level. -* [Documentation](http://docs.libuv.org/) +* [文件](http://docs.libuv.org/) ### llhttp @@ -45,7 +64,7 @@ HTTP parsing is handled by a lightweight TypeScript and C library called llhttp. It is designed to not make any syscalls or allocations, so it has a very small per-request memory footprint. -* [Documentation](https://github.com/joyent/http-parser/) +* [文件](https://github.com/joyent/http-parser/) ### c-ares @@ -56,7 +75,7 @@ use of threaded `getaddrinfo(3)` calls in libuv. The reason for this is that c-ares supports /etc/hosts, /etc/resolv.conf and /etc/svc.conf, but not things like mDNS. -* [Documentation](https://c-ares.haxx.se/docs.html) +* [文件](https://c-ares.haxx.se/docs.html) ### OpenSSL @@ -64,7 +83,7 @@ OpenSSL is used extensively in both the `tls` and `crypto` modules. It provides battle-tested implementations of many cryptographic functions that the modern web relies on for security. -* [Documentation](https://www.openssl.org/docs/) +* [文件](https://www.openssl.org/docs/) ### zlib @@ -72,9 +91,9 @@ For fast compression and decompression, Node.js relies on the industry-standard zlib library, also known for its use in gzip and libpng. Node.js uses zlib to create sync, async and streaming compression and decompression interfaces. -* [Documentation](https://www.zlib.net/manual.html) +* [文件](https://www.zlib.net/manual.html) -## Tools +## 工具 ### npm @@ -83,7 +102,7 @@ package manager; for this purpose, npm was made. With npm comes the largest selection of community-created packages of any programming ecosystem, which makes building Node.js apps quick and easy. -* [Documentation](https://docs.npmjs.com/) +* [文件](https://docs.npmjs.com/) ### gyp @@ -92,11 +111,11 @@ from V8. It can generate project files for use with build systems across many platforms. Node.js requires a build system because large parts of it — and its dependencies — are written in languages that require compilation. -* [Documentation](https://gyp.gsrc.io/docs/UserDocumentation.md) +* [文件](https://gyp.gsrc.io/docs/UserDocumentation.md) ### gtest Native code can be tested using gtest, which is taken from Chromium. It allows testing C/C++ without needing an existing node executable to bootstrap from. -* [Documentation](https://code.google.com/p/googletest/wiki/V1_7_Documentation) +* [文件](https://code.google.com/p/googletest/wiki/V1_7_Documentation) diff --git a/locale/zh-tw/download/current.md b/locale/zh-tw/download/current.md index 06ec29d2a8c3d..105660449a389 100644 --- a/locale/zh-tw/download/current.md +++ b/locale/zh-tw/download/current.md @@ -7,29 +7,29 @@ downloads: lts: LTS current: 目前版本 tagline-current: 最新功能 - tagline-lts: 推薦大多數使用者使用 + tagline-lts: 建議大部分使用者使用 display-hint: 顯示 intro: > - 下載適合你的平台的 Node.js 原始碼或安裝套件，立刻開始使用 Node.js。 - currentVersion: 目前版本 + 下載適合您平台的 Node.js 原始碼或安裝套件。立刻開始使用 Node.js。 + currentVersion: 最新版 includes: 包含 buildInstructions: 在支援的平台上，使用原始碼建構 Node.js WindowsInstaller: Windows 安裝包 - WindowsBinary: Windows 二進制檔案 + WindowsBinary: Windows 二進位檔案 MacOSInstaller: macOS 安裝包 - MacOSBinary: macOS 二進制檔案 - LinuxBinaries: Linux 二進制檔案 + MacOSBinary: macOS 二進位檔案 + LinuxBinaries: Linux 二進位檔案 SourceCode: 原始碼 additional: headline: 其它平台 intro: > - Node.js 社群為其它平台維護的非官方建構。請注意 Node.js 團隊並不為這些建構提供技術支援且其可能與現行 Node.js 版本不一致。 + Node.js 社群為其它平台維護的非官方建構。請注意 Node.js 團隊並不為這些建置版本提供技術支援且其可能與現行 Node.js 版本不一致。 platform: 平台 provider: 提供者 - SmartOSBinaries: SmartOS 二進制檔案 + SmartOSBinaries: SmartOS 二進位檔案 DockerImage: Docker 映像檔 officialDockerImage: Node.js 官方 Docker 映像檔 - LinuxPowerSystems: Linux on Power Systems - LinuxSystemZ: Linux on System z - AIXPowerSystems: AIX on Power Systems + LinuxPowerSystems: 建置在 Power 系統上的 Linux + LinuxSystemZ: 建置在 System Z 上的 Linux + AIXPowerSystems: 建置在 Power 系統的 AIX --- diff --git a/locale/zh-tw/download/index.md b/locale/zh-tw/download/index.md index 70103c990ac15..df467c01cc4f8 100644 --- a/locale/zh-tw/download/index.md +++ b/locale/zh-tw/download/index.md @@ -7,29 +7,29 @@ downloads: lts: LTS current: 目前版本 tagline-current: 最新功能 - tagline-lts: 推薦大多數使用者使用 + tagline-lts: 建議大部分使用者使用 display-hint: 顯示 intro: > - 在你的平台上下載 Node.js 原始碼或者安裝套件，立刻開始使用 Node.js。 - currentVersion: 目前版本 + 下載適合您平台的 Node.js 原始碼或安裝套件。立刻開始使用 Node.js。 + currentVersion: 最新版 includes: 包含 - buildInstructions: 使用原始碼在支援的平台上建構 Node.js + buildInstructions: 在支援的平台上，使用原始碼建構 Node.js WindowsInstaller: Windows 安裝包 - WindowsBinary: Windows 二進制檔案 + WindowsBinary: Windows 二進位檔案 MacOSInstaller: macOS 安裝包 - MacOSBinary: macOS 二進制檔案 - LinuxBinaries: Linux 二進制檔案 + MacOSBinary: macOS 二進位檔案 + LinuxBinaries: Linux 二進位檔案 SourceCode: 原始碼 additional: headline: 其它平台 intro: > - Node.js 社群為其它平臺維護非官方的建構。請注意這些構建並不受 Node.js 核心團隊技術支援且可能尚未跟 Node.js 的目前發布版本保持一致。 + Node.js 社群為其它平台維護的非官方建構。請注意 Node.js 團隊並不為這些建置版本提供技術支援且其可能與現行 Node.js 版本不一致。 platform: 平台 provider: 提供者 - SmartOSBinaries: SmartOS 二進制檔案 + SmartOSBinaries: SmartOS 二進位檔案 DockerImage: Docker 映像檔 officialDockerImage: Node.js 官方 Docker 映像檔 - LinuxPowerSystems: Power Systems 上的 Linux - LinuxSystemZ: System z 上的 Linux - AIXPowerSystems: Power Systems 上的 AIX + LinuxPowerSystems: 建置在 Power 系統上的 Linux + LinuxSystemZ: 建置在 System Z 上的 Linux + AIXPowerSystems: 建置在 Power 系統的 AIX --- diff --git a/locale/zh-tw/download/package-manager.md b/locale/zh-tw/download/package-manager.md index 630d794416499..b4c53a05599b5 100644 --- a/locale/zh-tw/download/package-manager.md +++ b/locale/zh-tw/download/package-manager.md @@ -1,11 +1,11 @@ --- layout: page.hbs -title: 透過套件管理安裝 Node.js +title: 使用套件管理器安裝 Node.js --- -# 透過套件管理安裝 Node.js +# 使用套件管理器安裝 Node.js -***請注意：*** 下列的套件維護及支援 **並非由** Node.js 核心團隊提供，任何套件使用上的問題，應直接聯繫各套件的維護者，若發現問題出於 Node.js 本身，則應由套件維護者聯繫上層。 +***請注意：*** 下列的套件維護及支援 **並非由** Node.js 核心團隊提供，任何套件使用上的問題，應直接聯絡各套件的維護者，若發現問題出於 Node.js 本身，則應由套件維護者聯絡上游。 --- @@ -29,7 +29,7 @@ title: 透過套件管理安裝 Node.js ## Android -Android 的 Node.js 支援仍是試驗版，因此 Node.js 開發者尚未提供預先編譯的二進制檔。 +Android 的 Node.js 支援仍是試驗版，因此 Node.js 開發者尚未提供預先編譯的二進位檔。 但社群提供了第三方的解決方式，舉例來說，[Termux](https://termux.com/) 社群提供了終端機模擬器及 Android 的 Linux 環境，也有自己的套件管理器及許多預先編譯的[程式清單](https://github.com/termux/termux-packages)。 @@ -52,13 +52,13 @@ pacman -S nodejs npm ## Debian 及 Ubuntu 系列發行版，企業版 Linux/Fedora 和 Snap packages -[官方 Node.js 二進制發行版](https://github.com/nodesource/distributions/blob/master/README.md) 透過 NodeSource 提供. +[官方 Node.js 二進位發行版](https://github.com/nodesource/distributions/blob/master/README.md) 透過 NodeSource 提供. ## FreeBSD 近期的版本已可透過 [www/node](https://www.freshports.org/www/node) port 取得 Node.js。 -透過 [pkg](https://www.freebsd.org/cgi/man.cgi?pkg) 安裝二進制套件： +透過 [pkg](https://www.freebsd.org/cgi/man.cgi?pkg) 安裝二進位套件： ```bash pkg install node @@ -98,15 +98,15 @@ Node.js 可透過 pkgsrc 樹取得： cd /usr/pkgsrc/lang/nodejs && make install ``` -或使用 pkgin 安裝二進制套件（若適用於你的平台的話）： +或使用 pkgin 安裝二進位套件（若適用於你的平台的話）： ```bash pkgin -y install nodejs ``` ## nvm -Node 版本管理器（Node Version Manager, nvm）是款用來管理 Node.js 多重版本的 bash 腳本，它可讓你執行安裝、移除及切換版本等操作。 -若要安裝 NVM 可以使用此[安裝腳本](https://github.com/creationix/nvm#install-script)。 +Node 版本管理器（Node Version Manager, nvm）是款用來管理 Node.js 多重版本的 bash 文稿，它可讓你執行安裝、移除及切換版本等操作。 +若要安裝 NVM 可以使用此[安裝文稿](https://github.com/creationix/nvm#install-script)。 在 Unix / OS X 系統上從源碼編譯的 Node.js 可以透過 [nvm](https://github.com/creationix/nvm) 安裝至其指定位置： @@ -184,7 +184,7 @@ port install nodejs7 使用 **[pkgsrc](https://pkgsrc.joyent.com/install-on-osx/)**： -安裝二進制套件： +安裝二進位套件： ```bash pkgin -y install nodejs @@ -198,7 +198,7 @@ cd pkgsrc/lang/nodejs && bmake install ## SmartOS 及 illumos -SmartOS 映像檔已經預載了 pkgsrc，其他的 illumos 發行版則需要先**[安裝pkgsrc](https://pkgsrc.joyent.com/install-on-illumos/)**，接著你就可以依照平常的方式安裝二進制套件： +SmartOS 映像檔已經預載了 pkgsrc，其他的 illumos 發行版則需要先**[安裝pkgsrc](https://pkgsrc.joyent.com/install-on-illumos/)**，接著你就可以依照平常的方式安裝二進位套件： ```bash pkgin -y install nodejs diff --git a/locale/zh-tw/download/releases.md b/locale/zh-tw/download/releases.md index e1a5f980c90cb..4e96df807c154 100644 --- a/locale/zh-tw/download/releases.md +++ b/locale/zh-tw/download/releases.md @@ -1,11 +1,11 @@ --- layout: download-releases.hbs title: 先前釋出的版本 -modules: "NODE_MODULE_VERSION 是 Node.js ABI (application binary interface) 的版本號，其代表編譯 Node.js 的 C++ 函式庫版本，用來確定是否不需經過重新編譯就能直接使用。早期版本號是個十六進位數值，現在則為一個整數。" +modules: "NODE_MODULE_VERSION 是 Node.js ABI (application binary interface) 的版本號碼，其代表編譯 Node.js 的 C++ 函式庫版本，用來確定是否不需經過重新編譯就能直接使用。早期版本號碼是個十六進位數值，現在則為一個整數。" --- ### io.js 與 Node.js -1.x 到 3.x 的版本被稱為 “io.js”，因為它們屬於 io.js 的分支。從 Node.js 4.0.0 開始，io.js 與 Node.js 合併到 Node.js 的發行版本中。 +1.x 到 3.x 的版本被稱為「io.js」，因為它們屬於 io.js 的分支。從 Node.js 4.0.0 開始，io.js 與 Node.js 合併到 Node.js 的發行版本中。
diff --git a/locale/zh-tw/index.md b/locale/zh-tw/index.md index b2064133d221c..46044f555cd4c 100644 --- a/locale/zh-tw/index.md +++ b/locale/zh-tw/index.md @@ -5,12 +5,12 @@ labels: download: 下載 download-for: 目前版本： other-downloads: 其它版本 - other-lts-downloads: 其它 LTS 版下載 - other-current-downloads: 其它最新版下載 - current: 目前版本 + other-lts-downloads: 其它長期維護版下載 + other-current-downloads: 其它最新版本下載 + current: 最新版本 lts: 長期維護版 tagline-current: 包含最新功能 - tagline-lts: 推薦給大多數用戶 + tagline-lts: 適合給大部分使用者 changelog: 更新紀錄 api: API 文件 version-schedule-prompt: 或參考 diff --git a/locale/zh-tw/security.md b/locale/zh-tw/security.md index 63ee2853c23be..caf82901f9ad6 100644 --- a/locale/zh-tw/security.md +++ b/locale/zh-tw/security.md @@ -5,7 +5,7 @@ title: 安全 # 安全 -## 回報 Node.js 的臭蟲 +## 回報 Node.js 臭蟲 Node.js 非常嚴肅地看待安全性臭蟲，所有的臭蟲都應回報至 [HackerOne](https://hackerone.com/nodejs)，其後將由專責安全問題的部門處理。 @@ -46,4 +46,4 @@ Node.js 官方為了安全研究員們及負責的公開揭露而展開了一個 ## 對本政策的建言 -若你對改善本流程有任何建議的話，請開啟一個 [pull request](https://github.com/nodejs/nodejs.org) 或是 [一個 issue](https://github.com/nodejs/security-wg/issues/new) 來與我們一同討論。 +若你對改善本流程有任何建議的話，請開一個 [pull request](https://github.com/nodejs/nodejs.org) 或是 [issue](https://github.com/nodejs/security-wg/issues/new) 來與我們一同討論。 diff --git a/locale/zh-tw/site.json b/locale/zh-tw/site.json index 1f46e6928a86a..ef0a343a03e00 100644 --- a/locale/zh-tw/site.json +++ b/locale/zh-tw/site.json @@ -1,21 +1,21 @@ { "title": "Node.js", - "editOnGithub":"在 GitHub 上編輯", + "editOnGithub": "在 GitHub 上編輯", "author": "Node.js 基金會", "url": "https://nodejs.org/zh-tw/", "locale": "zh-tw", - "language": "中文(繁體)", - "languageEnglishVersion": "Chinese Traditional", + "language": "中文 (繁體)", + "languageEnglishVersion": "Traditional Chinese", "scrollToTop": "回到頁首", - "reportNodeIssue": "回報 Node.js 問題 ", + "reportNodeIssue": "回報 Node.js 問題", "reportWebsiteIssue": "回報 Node.js 網站問題", "getHelpIssue": "取得協助", - "by": "by", + "by": "依", "all-downloads": "所有下載選項", - "nightly": "每日構建", - "chakracore-nightly": "Node-ChakraCore 每日構建", - "unofficial-builds": "非官方構建版", - "previous": "前一個", + "nightly": "每日建置版本", + "chakracore-nightly": "Node-ChakraCore 每日建置版本", + "unofficial-builds": "非官方建置版本", + "previous": "上一個", "next": "下一個", "feeds": [ { @@ -24,11 +24,11 @@ }, { "link": "feed/releases.xml", - "text": "Node.js 部落格: 發佈" + "text": "Node.js 部落格：發佈版" }, { "link": "feed/vulnerability.xml", - "text": "Node.js 部落格: 安全報告" + "text": "Node.js 部落格：安全報告" } ], "home": { @@ -43,11 +43,11 @@ }, "workinggroups": { "link": "about/working-groups", - "text": "工作組" + "text": "工作群組" }, "releases": { "link": "about/releases", - "text": "發佈" + "text": "發佈版" }, "resources": { "link": "about/resources", @@ -67,7 +67,7 @@ "text": "下載", "releases": { "link": "download/releases", - "text": "以往的版本" + "text": "舊版" }, "package-manager": { "link": "download/package-manager", @@ -75,10 +75,10 @@ }, "shasums": { "link": "SHASUMS256.txt.asc", - "text": "發佈文件的 SHASUM 簽名" + "text": "發佈檔案的 SHASUM 簽名" }, "install-on-linux": { - "text": "在 Linux 上，通過二進位檔案安裝 Node.js" + "text": "在 Linux 上使用二進位檔案安裝 Node.js" } }, "docs": { @@ -139,7 +139,7 @@ "text": "基金會" }, "releases": { - "title": "發佈歷史", + "title": "發佈版歷史", "downloads": "下載" }, "links": { From 4990f6af88be7bd5f29cfaf2252c6aadef8f0323 Mon Sep 17 00:00:00 2001 From: pan93412 Date: Sun, 24 Nov 2019 17:59:59 +0800 Subject: [PATCH 3/5] fix(zh_TW): remove untranslated contents --- locale/zh-tw/about/index.md | 65 ---------- locale/zh-tw/docs/meta/topics/dependencies.md | 121 ------------------ 2 files changed, 186 deletions(-) delete mode 100644 locale/zh-tw/about/index.md delete mode 100644 locale/zh-tw/docs/meta/topics/dependencies.md diff --git a/locale/zh-tw/about/index.md b/locale/zh-tw/about/index.md deleted file mode 100644 index 27b1e8160bc27..0000000000000 --- a/locale/zh-tw/about/index.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -layout: about.hbs -title: 關於 -trademark: 商標 ---- - -# 關於 Node.js® - -作為一個異步事件驅動的 JavaScript 執行階段，Node.js 設計來建構可擴充的網路應用程式。下方的「Hello World」範例中，多個連線皆能並行處理。一當每個連線建立後，會先執行回呼函式，但如果沒有需要作的事情，Node.js 則會休眠。 - -```javascript -const http = require('http'); - -const hostname = '127.0.0.1'; -const port = 3000; - -const server = http.createServer((req, res) => { - res.statusCode = 200; - res.setHeader('Content-Type', 'text/plain'); - res.end('Hello World\n'); -}); - -server.listen(port, hostname, () => { - console.log(`伺服器正在 http://${hostname}:${port}/ 運作`); -}); -``` - -This is in contrast to today's more common concurrency model, in which OS threads -are employed. Thread-based networking is relatively inefficient and very -difficult to use. Furthermore, users of Node.js are free from worries of -dead-locking the process, since there are no locks. Almost no function in -Node.js directly performs I/O, so the process never blocks. Because nothing blocks, scalable systems are very reasonable to develop in Node.js. - -如果不熟悉這門語言的一些地方，在 [阻塞式與非阻塞式的比較][] 這篇文章有完整的解釋。 - ---- - -Node.js is similar in design to, and influenced by, systems like Ruby's -[Event Machine][] and Python's [Twisted][]. Node.js takes the event model a bit -further. It presents an [事件循環][] as a runtime construct instead of as a library. In other systems, there is always a blocking call to start the -event-loop. -Typically, behavior is defined through callbacks at the beginning of a script, and -at the end a server is started through a blocking call like -`EventMachine::run()`. In Node.js, there is no such start-the-event-loop call. -Node.js simply enters the event loop after executing the input script. Node.js -exits the event loop when there are no more callbacks to perform. This behavior -is like browser JavaScript — the event loop is hidden from the user. - -HTTP is a first-class citizen in Node.js, designed with streaming and low -latency in mind. This makes Node.js well suited for the foundation of a web -library or framework. - -Node.js being designed without threads doesn't mean you can't take -advantage of multiple cores in your environment. Child processes can be spawned -by using our [`child_process.fork()`][] API, and are designed to be easy to -communicate with. Built upon that same interface is the [`cluster`][] module, -which allows you to share sockets between processes to enable load balancing -over your cores. - -[阻塞式與非阻塞式的比較]: /en/docs/guides/blocking-vs-non-blocking/ -[`child_process.fork()`]: https://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options -[`cluster`]: https://nodejs.org/api/cluster.html -[事件循環]: /en/docs/guides/event-loop-timers-and-nexttick/ -[Event Machine]: https://github.com/eventmachine/eventmachine -[Twisted]: https://twistedmatrix.com/trac/ diff --git a/locale/zh-tw/docs/meta/topics/dependencies.md b/locale/zh-tw/docs/meta/topics/dependencies.md deleted file mode 100644 index a3fcf27f10392..0000000000000 --- a/locale/zh-tw/docs/meta/topics/dependencies.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -title: 依賴項目 -layout: docs.hbs ---- - -# 依賴項目 - -這裡列出了多個 Node.js 所仰賴的依賴項目，以讓 Node.js 能如預期般運作。 - -* [函式庫](#libraries) - * [V8](#v8) - * [libuv](#libuv) - * [http-parser](#http-parser) - * [c-ares](#c-ares) - * [OpenSSL](#openssl) - * [zlib](#zlib) -* [工具](#tools) - * [npm](#npm) - * [gyp](#gyp) - * [gtest](#gtest) - - - -## 函式庫 - -### V8 - -V8 函式庫為 Node.js 提供了 JavaScript 引擎（Node.js 使用 V8 C++ API 控制）。 -V8 是 Google 維護用來在 Chrome 使用的。 - -* [文件](https://v8docs.nodesource.com/) - -### libuv - -Another important dependency is libuv, a C library that is used to abstract -non-blocking I/O operations to a consistent interface across all supported -platforms. It provides mechanisms to handle file system, DNS, network, child -processes, pipes, signal handling, polling and streaming. It also includes a -thread pool for offloading work for some things that can't be done -asynchronously at the operating system level. - -* [文件](http://docs.libuv.org/) - -### llhttp - -HTTP parsing is handled by a lightweight TypeScript and C library called llhttp. -It is designed to not make any syscalls or allocations, so it has a very small -per-request memory footprint. - -* [文件](https://github.com/joyent/http-parser/) - -### c-ares - -For some asynchronous DNS requests, Node.js uses a C library called c-ares. -It is exposed through the DNS module in JavaScript as the `resolve()` family of -functions. The `lookup()` function, which is what the rest of core uses, makes -use of threaded `getaddrinfo(3)` calls in libuv. The reason for this is that -c-ares supports /etc/hosts, /etc/resolv.conf and /etc/svc.conf, but not things -like mDNS. - -* [文件](https://c-ares.haxx.se/docs.html) - -### OpenSSL - -OpenSSL is used extensively in both the `tls` and `crypto` modules. It provides -battle-tested implementations of many cryptographic functions that the modern -web relies on for security. - -* [文件](https://www.openssl.org/docs/) - -### zlib - -For fast compression and decompression, Node.js relies on the industry-standard -zlib library, also known for its use in gzip and libpng. Node.js uses zlib to -create sync, async and streaming compression and decompression interfaces. - -* [文件](https://www.zlib.net/manual.html) - -## 工具 - -### npm - -Node.js is all about modularity, and with that comes the need for a quality -package manager; for this purpose, npm was made. With npm comes the largest -selection of community-created packages of any programming ecosystem, -which makes building Node.js apps quick and easy. - -* [文件](https://docs.npmjs.com/) - -### gyp - -The build system is handled by gyp, a python-based project generator copied -from V8. It can generate project files for use with build systems across many -platforms. Node.js requires a build system because large parts of it — and its -dependencies — are written in languages that require compilation. - -* [文件](https://gyp.gsrc.io/docs/UserDocumentation.md) - -### gtest - -Native code can be tested using gtest, which is taken from Chromium. It allows -testing C/C++ without needing an existing node executable to bootstrap from. - -* [文件](https://code.google.com/p/googletest/wiki/V1_7_Documentation) From 0cde8b55d704e2008e5e7b0c9a3acebeb62bd9e3 Mon Sep 17 00:00:00 2001 From: pan93412 <28441561+pan93412@users.noreply.github.com> Date: Mon, 25 Nov 2019 22:59:04 +0800 Subject: [PATCH 4/5] fix(zh_TW): fix the mistakes mentioned by reviewers --- locale/zh-tw/about/releases.md | 4 ++-- locale/zh-tw/download/current.md | 4 ++-- locale/zh-tw/download/package-manager.md | 4 ++-- locale/zh-tw/security.md | 4 ++-- locale/zh-tw/site.json | 2 +- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/locale/zh-tw/about/releases.md b/locale/zh-tw/about/releases.md index bf2e0aed6f659..551e8f728fc34 100644 --- a/locale/zh-tw/about/releases.md +++ b/locale/zh-tw/about/releases.md @@ -10,7 +10,7 @@ columns: - '發布版' - '狀態' - '內部代號' - - '初發布版' + - '初始發布版' - '活躍 LTS 週期開始' - '維護 LTS 週期開始' - '結束生命週期' @@ -21,5 +21,5 @@ schedule-footer: 日期會隨時變更。 主要 Node.js 版本會進入為時 6 個月的 _最新版_ 發布狀態，以讓函式庫作者有時間支援。 6 個月後，奇數版號（9、11 等等）會不再受支援，而偶數版號（10、12 等等）會移至 _活躍 LTS_ 狀態並準備日常使用。 -_LTS_ 發布版狀態指「長期維護」，通常會保證嚴重臭蟲會在 30 個月內修正。 +_LTS_ 發布版狀態指「長期維護」，通常會保證會在這總共 30 個月修正嚴重臭蟲。 生產環境的應用程式應只使用 _活躍 LTS_ 或 _維護 LTS_ 版本。 diff --git a/locale/zh-tw/download/current.md b/locale/zh-tw/download/current.md index 105660449a389..b8088ad00a304 100644 --- a/locale/zh-tw/download/current.md +++ b/locale/zh-tw/download/current.md @@ -29,7 +29,7 @@ additional: SmartOSBinaries: SmartOS 二進位檔案 DockerImage: Docker 映像檔 officialDockerImage: Node.js 官方 Docker 映像檔 - LinuxPowerSystems: 建置在 Power 系統上的 Linux + LinuxPowerSystems: 建置在 Power Systems 上的 Linux LinuxSystemZ: 建置在 System Z 上的 Linux - AIXPowerSystems: 建置在 Power 系統的 AIX + AIXPowerSystems: 建置在 Power Systems 上的 AIX --- diff --git a/locale/zh-tw/download/package-manager.md b/locale/zh-tw/download/package-manager.md index b4c53a05599b5..ae4afc088e593 100644 --- a/locale/zh-tw/download/package-manager.md +++ b/locale/zh-tw/download/package-manager.md @@ -105,8 +105,8 @@ pkgin -y install nodejs ``` ## nvm -Node 版本管理器（Node Version Manager, nvm）是款用來管理 Node.js 多重版本的 bash 文稿，它可讓你執行安裝、移除及切換版本等操作。 -若要安裝 NVM 可以使用此[安裝文稿](https://github.com/creationix/nvm#install-script)。 +Node 版本管理器（Node Version Manager, nvm）是款用來管理 Node.js 多重版本的 bash 指令稿，它可讓你執行安裝、移除及切換版本等操作。 +若要安裝 NVM 可以使用此[安裝指令稿](https://github.com/creationix/nvm#install-script)。 在 Unix / OS X 系統上從源碼編譯的 Node.js 可以透過 [nvm](https://github.com/creationix/nvm) 安裝至其指定位置： diff --git a/locale/zh-tw/security.md b/locale/zh-tw/security.md index caf82901f9ad6..60e0c29b871ff 100644 --- a/locale/zh-tw/security.md +++ b/locale/zh-tw/security.md @@ -5,7 +5,7 @@ title: 安全 # 安全 -## 回報 Node.js 臭蟲 +## 回報 Node.js 的臭蟲 Node.js 非常嚴肅地看待安全性臭蟲，所有的臭蟲都應回報至 [HackerOne](https://hackerone.com/nodejs)，其後將由專責安全問題的部門處理。 @@ -19,7 +19,7 @@ Node.js 官方為了安全研究員們及負責的公開揭露而展開了一個 ## 回報第三方模組中的臭蟲 -第三方模組中的安全性臭蟲應向其維護者回報，且應透過 [HackerOne](https://hackerone.com/nodejs-ecosystem) 來協調。關於此流程的細節可參考安全性工作小組的 [repository](https://github.com/nodejs/security-wg/blob/master/processes/third_party_vuln_process.md)。 +第三方模組中的安全性臭蟲應向其維護者回報，且應透過 [HackerOne](https://hackerone.com/nodejs-ecosystem) 來協調。關於此流程的細節可參考安全性工作小組的[檔案庫](https://github.com/nodejs/security-wg/blob/master/processes/third_party_vuln_process.md)。 感謝你對於 Node.js 及其生態系安全性的改善，我們相當感謝並認可你的付出及負責任地揭露問題。 diff --git a/locale/zh-tw/site.json b/locale/zh-tw/site.json index ef0a343a03e00..79442852cf5f7 100644 --- a/locale/zh-tw/site.json +++ b/locale/zh-tw/site.json @@ -10,7 +10,7 @@ "reportNodeIssue": "回報 Node.js 問題", "reportWebsiteIssue": "回報 Node.js 網站問題", "getHelpIssue": "取得協助", - "by": "依", + "by": "by", "all-downloads": "所有下載選項", "nightly": "每日建置版本", "chakracore-nightly": "Node-ChakraCore 每日建置版本", From fa5aebbadd77ce92337ce2b9f699d783e6beb9d0 Mon Sep 17 00:00:00 2001 From: pan93412 Date: Tue, 26 Nov 2019 18:50:39 +0800 Subject: [PATCH 5/5] fix(zh_TW): fix the mistakes mentioned by reviewers --- locale/zh-tw/about/releases.md | 2 +- locale/zh-tw/download/current.md | 2 +- locale/zh-tw/download/index.md | 6 +++--- locale/zh-tw/security.md | 4 ++-- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/locale/zh-tw/about/releases.md b/locale/zh-tw/about/releases.md index 551e8f728fc34..5876ead7871fb 100644 --- a/locale/zh-tw/about/releases.md +++ b/locale/zh-tw/about/releases.md @@ -21,5 +21,5 @@ schedule-footer: 日期會隨時變更。 主要 Node.js 版本會進入為時 6 個月的 _最新版_ 發布狀態，以讓函式庫作者有時間支援。 6 個月後，奇數版號（9、11 等等）會不再受支援，而偶數版號（10、12 等等）會移至 _活躍 LTS_ 狀態並準備日常使用。 -_LTS_ 發布版狀態指「長期維護」，通常會保證會在這總共 30 個月修正嚴重臭蟲。 +_LTS_ 發布版狀態指「長期維護」，通常保證會在 30 個月的維護期間內修復發現的嚴重臭蟲。 生產環境的應用程式應只使用 _活躍 LTS_ 或 _維護 LTS_ 版本。 diff --git a/locale/zh-tw/download/current.md b/locale/zh-tw/download/current.md index b8088ad00a304..edac407f5b5fb 100644 --- a/locale/zh-tw/download/current.md +++ b/locale/zh-tw/download/current.md @@ -30,6 +30,6 @@ additional: DockerImage: Docker 映像檔 officialDockerImage: Node.js 官方 Docker 映像檔 LinuxPowerSystems: 建置在 Power Systems 上的 Linux - LinuxSystemZ: 建置在 System Z 上的 Linux + LinuxSystemZ: 建置在 System z 上的 Linux AIXPowerSystems: 建置在 Power Systems 上的 AIX --- diff --git a/locale/zh-tw/download/index.md b/locale/zh-tw/download/index.md index df467c01cc4f8..3dbb20aaf3dee 100644 --- a/locale/zh-tw/download/index.md +++ b/locale/zh-tw/download/index.md @@ -29,7 +29,7 @@ additional: SmartOSBinaries: SmartOS 二進位檔案 DockerImage: Docker 映像檔 officialDockerImage: Node.js 官方 Docker 映像檔 - LinuxPowerSystems: 建置在 Power 系統上的 Linux - LinuxSystemZ: 建置在 System Z 上的 Linux - AIXPowerSystems: 建置在 Power 系統的 AIX + LinuxPowerSystems: 建置在 Power Systems 上的 Linux + LinuxSystemZ: 建置在 System z 上的 Linux + AIXPowerSystems: 建置在 Power Systems 上的 AIX --- diff --git a/locale/zh-tw/security.md b/locale/zh-tw/security.md index 60e0c29b871ff..555eeb799de1f 100644 --- a/locale/zh-tw/security.md +++ b/locale/zh-tw/security.md @@ -19,13 +19,13 @@ Node.js 官方為了安全研究員們及負責的公開揭露而展開了一個 ## 回報第三方模組中的臭蟲 -第三方模組中的安全性臭蟲應向其維護者回報，且應透過 [HackerOne](https://hackerone.com/nodejs-ecosystem) 來協調。關於此流程的細節可參考安全性工作小組的[檔案庫](https://github.com/nodejs/security-wg/blob/master/processes/third_party_vuln_process.md)。 +第三方模組中的安全性臭蟲應向其維護者回報，且應透過 [HackerOne](https://hackerone.com/nodejs-ecosystem) 來協調。關於此流程的細節可參考安全性工作小組的 [Repository](https://github.com/nodejs/security-wg/blob/master/processes/third_party_vuln_process.md)。 感謝你對於 Node.js 及其生態系安全性的改善，我們相當感謝並認可你的付出及負責任地揭露問題。 ## 揭露政策 -下列為 Node.js 之安全性揭露政策 +下列為 Node.js 之安全性揭露政策： * 收到安全性的回報後我們會指派一個主要負責人，此人會負責確認問題，並協調修補、釋出的流程及確認受影響版本，審核程式碼以確保沒有其他類似問題，為所有維護中的版本提供修補程式，並確保這些修補程式不會在發布前被公開。