finished intro/ index.md, object/ forinloop.md

Author: howardchi

doc/zh-TW/intro/index.md

@@ -1,37 +1,38 @@
-## Intro
+## 簡介
 
-**JavaScript Garden** is a growing collection of documentation about the most 
-quirky parts of the JavaScript programming language. It gives advice to 
-avoid common mistakes and subtle bugs, as well as performance issues and bad 
-practices, that non-expert JavaScript programmers may encounter on their 
-endeavours into the depths of the language.
+是一個不斷更新的文件，最主要是要去了解一些 Javascript 比較古怪的部份。
+給一些意見來防止遇到一些常見的錯誤和一些難以發現的問題，以及性能問題和不好的習慣。
+初學者也可以借此去了解 Javascript 這項語言的特性。
 
-JavaScript Garden does **not** aim to teach you JavaScript. Former knowledge
-of the language is strongly recommended in order to understand the topics covered
-in this guide. In order to learn the basics of the language, please head over to 
-the excellent [guide][1] on the Mozilla Developer Network.
+JavaScript 庭院 並 **不是** 要教導你 Javascript 的語言。
+如果要能夠理解這篇文章的內容，你需要事先學習 JavaScript 的基礎知識。
+在 Mozilla 開發者網路中有一系列非常棒的學習[guide][1]。
 
-## The Authors
 
-This guide is the work of two lovely [Stack Overflow][2] users, [Ivo Wetzel][3]
-(Writing) and [Zhang Yi Jiang][4] (Design).
+## 作者
 
-## Contributors
+這個使用手冊是來自於 [Stack Overflow][2] 的使用者, [Ivo Wetzel][3]
+(寫作) 和 [Zhang Yi Jiang][4] (設計).
 
- - [Caio Romão][5] (Spelling corrections)
- - [Andreas Blixt][6] (Language corrections)
+## 貢獻者
+
+ - [Caio Romão][5] (拼寫檢查)
+ - [Andreas Blixt][6] (語言修正)
+
+## 繁體中文翻譯
+
+ - [紀力榮][29]
+ - [張仲威][30]
 
 ## Hosting
 
 JavaScript Garden is hosted on GitHub, but [Cramer Development][7] supports us
 with a mirror at [JavaScriptGarden.info][8].
 
-## License
+## 許可
 
-JavaScript Garden is published under the [MIT license][9] and hosted on
-[GitHub][10]. If you find errors or typos please [file an issue][11] or a pull 
-request on the repository. You can also find us in the [JavaScript room][12] on
-Stack Overflow chat.
+JavaScript 庭院是在 [MIT license][9] 許可協議下發佈，並存在於
+[GitHub][10]. 如果你有發現錯誤或是打字上的錯誤 [新增一個任務][11] 或者發一個請求。 你也可以在 StackOverflow 的 [JavaScript room][12] 上面找到我們。
 
 [1]: https://developer.mozilla.org/en/JavaScript/Guide
 [2]: http://stackoverflow.com/
@@ -45,3 +46,5 @@ Stack Overflow chat.
 [10]: https://github.com/BonsaiDen/JavaScript-Garden
 [11]: https://github.com/BonsaiDen/JavaScript-Garden/issues
 [12]: http://chat.stackoverflow.com/rooms/17/javascript
+[29]: http://github.com/chilijung
+[30]: http://github.com/wwwy3y3

doc/zh-TW/object/forinloop.md

@@ -1,51 +1,40 @@
-## The `for in` Loop
+## `for in` 迴圈
 
-Just like the `in` operator, the `for in` loop traverses the prototype
-chain when iterating over the properties of an object.
+就像其他的 `in` 操作符一樣， `for in` 循環也進入所有在物件中的屬性
 
-> **Note:** The `for in` loop will **not** iterate over any properties that 
-> have their `enumerable` attribute set to `false`; for example, the `length` 
-> property of an array.
+> **注意: ** `for in` 迴圈 **不會** 進入那些 `enumerable` 屬性是 `false`，舉例來說， 陣列中 `length` 的屬性
     
-    // Poisoning Object.prototype
+    // 修改 Object.prototype
     Object.prototype.bar = 1;
 
     var foo = {moo: 2};
     for(var i in foo) {
-        console.log(i); // prints both bar and moo
+        console.log(i); // 輸出兩個屬性：bar 和 moo
     }
 
-Since it is not possible to change the behavior of the `for in` loop itself, it
-is necessary to filter out the unwanted properties inside the loop body; 
-this is done using the [`hasOwnProperty`](#object.hasownproperty) method of 
-`Object.prototype`.
+由於不可能改變 `for in` 本身的行為，因為有必要過濾出那些不希望在迴圈出現的屬性，這可以用 `Object.prototype` 原型上的 [`hasOwnProperty`](#object.hasownproperty) 的函數來完成。
 
-> **Note:** Since `for in` always traverses the complete prototype chain, it
-> will get slower with each additional layer of inheritance added to an object.
+> **注意: ** 由於 `for in` 總是要到所有原型鏈裡，因此如果物件的繼承層次太深的話會影響性能。
 
-### Using `hasOwnProperty` for Filtering
 
-    // still the foo from above
+### 用 `hasOwnProperty` 來過濾
+
+    // foo 變數是上面範例中的
     for(var i in foo) {
         if (foo.hasOwnProperty(i)) {
             console.log(i);
         }
     }
 
-This version is the only correct one to use. Due to the use of `hasOwnProperty`, it
-will **only** print out `moo`. When `hasOwnProperty` is left out, the code is 
-prone to errors in cases where the native prototypes - e.g. `Object.prototype` - 
-have been extended.
+這個版本的程式碼是唯一正確的寫法。由於我們使用了 `hasOwnProperty`，這次 **只** 輸出 `moo`。
+如果不只用這個程式碼在原型物件中(比如 `Object.prototype`)被擴展可能會出錯。
 
-One widely used framework that extends `Object.prototype` is [Prototype][1].
-When this framework is included, `for in` loops that do not use
-`hasOwnProperty` are guaranteed to break.
+一個廣泛的模組 [Prototype][1]就礦展了圓型的 JavaScript 物件。
+因此，但這模組包含在頁面中時，不使用 `hasOwnProperty` 過濾的 `for in` 尋難免會出問題。
 
-### In Conclusion
+### 總結
 
-It is recommended to **always** use `hasOwnProperty`. Assumptions should never
-be made about the environment the code is running in, or whether the native
-prototypes have been extended or not.
+推薦 **總是** 使用 `hasOwnProperty`。不要對程式碼的環境做任何假設，不要假設原生的對象是否被擴張
 
 [1]: http://www.prototypejs.org/