|
| 1 | +# :wrench: 正體中文的翻譯工作正在進行中..... :wrench: |
| 2 | + |
| 3 | +## GitHub Page |
| 4 | + |
| 5 | +https://felixshai.github.io/open-source-guide/ |
| 6 | + |
| 7 | +## :memo: 翻譯工程進度檢查表 :memo: |
| 8 | +- [X] 首頁及各文章的標題翻譯 |
| 9 | +- [X] 使用 opencc 對簡體中文版本做初步的轉換 |
| 10 | +- [ ] opencc 翻譯檢查 |
| 11 | + |
| 12 | + - [X] 如何為開源做貢獻？(how-to-contribute) |
| 13 | + - [ ] 發起一個開源專案 (starting-a-project) |
| 14 | + - [ ] 尋找專案的使用者 (finding-users) |
| 15 | + - [X] 打造友善、溫暖的社群 (building-community) |
| 16 | + - [ ] 維護者最佳實踐 (best-practices) |
| 17 | + - [ ] 領導與治理 (leadership-and-governance) |
| 18 | + - [ ] 透過為開源專案工作而獲得報酬 (getting-paid) |
| 19 | + - [ ] 建立一套行為準則 (code-of-conduct) |
| 20 | + - [ ] 開源衡量準則 (metrics) |
| 21 | + - [ ] 開源的法律保障 (legal) |
| 22 | + |
| 23 | +- [ ] 檢查文章內的超連結是否正確 |
| 24 | + |
| 25 | + - [ ] 如何為開源做貢獻？(how-to-contribute) |
| 26 | + - [ ] 發起一個開源專案 (starting-a-project) |
| 27 | + - [ ] 尋找專案的使用者 (finding-users) |
| 28 | + - [ ] 打造友善、溫暖的社群 (building-community) |
| 29 | + - [ ] 維護者最佳實踐 (best-practices) |
| 30 | + - [ ] 領導與治理 (leadership-and-governance) |
| 31 | + - [ ] 透過為開源專案工作而獲得報酬 (getting-paid) |
| 32 | + - [ ] 建立一套行為準則 (code-of-conduct) |
| 33 | + - [ ] 開源衡量準則 (metrics) |
| 34 | + - [ ] 開源的法律保障 (legal) |
| 35 | + |
| 36 | +## 如何翻譯 |
| 37 | +1. 文章(article)的位置在 `_articles\zh-TW\` 目錄下，檔名是用檢查表中的英文命名。 |
| 38 | + |
| 39 | +2. 推薦使用 `Issue` 來先說明你要領哪一塊文章檢查翻譯，或是只領文章中的幾個段落檢查，避免有兩人以上對同篇文章的同個段落工作。 |
| 40 | + |
| 41 | +3. 每篇文章的 .md 檔最上頭的 toc 欄位底下， key 跟 value 都要翻成跟每個段落的標題一樣， |
| 42 | + 不然點選目錄的選項，頁面不能正確的對準到該段落。 |
| 43 | + |
| 44 | +4. 建議大標小標的前後用`**`包起來，讓大小標變粗體，不然標題跟內文看起來蠻相似的。 |
| 45 | + |
| 46 | +## 翻譯規則 |
| 47 | + |
| 48 | +|規則名稱|翻譯方式| |
| 49 | +|:-|:-| |
| 50 | +|引號轉換 quotation change|原作中引句使用雙引號`""`部分改為`「」`| |
| 51 | +|小括號轉全形 fullwidth parentheses|原作中`()` 換成 `（）`，使用新注音可透過按 \` 後 `shift`+`(` 輸入全形小括號| |
| 52 | +|大小標轉粗體 Bold the title|因為字的格式相同，導致標題與內文視覺上分不出來，所以需要將大小標轉為粗體| |
| 53 | +|中英文之間加空格 whitespace between languages|為使排版易讀，中英文字之間需用半形空格格開| |
| 54 | +|引文省略時表達方式|簡中使用（。。。）但應該保留(...)| |
| 55 | + |
| 56 | +## 銘謝 |
| 57 | + |
| 58 | +[opencc](https://github.com/BYVoid/OpenCC) |
| 59 | + |
| 60 | + |
| 61 | +# Open Source Guides |
| 62 | + |
| 63 | +[](https://travis-ci.org/github/opensource.guide) |
| 64 | + |
| 65 | +Open Source Guides (https://opensource.guide/) are a collection of resources for individuals, communities, and companies who want to learn how to run and contribute to an open source project. |
| 66 | + |
| 67 | +## Background |
| 68 | +The first set of Open Source Guides were created and curated by GitHub, along with input from outside community reviewers, but they are not exclusive to GitHub products. |
| 69 | + |
| 70 | +Our goal is to aggregate community best practices, *not* what GitHub (or any other individual or entity) thinks is best. Therefore, we try to use examples and quotations from others to illustrate our points. |
| 71 | + |
| 72 | +**Open Source Guides are a resource and a discussion forum.** One reason we started this project is because we felt that there weren't enough resources for people creating open source projects. We made these guides open source in hopes that you'll use this space to talk about best practices, then document them when you've found consensus. We'd like this to be a safe space to talk about what's hard, what's scary, and what's simply confusing about running open source projects. |
| 73 | + |
| 74 | +## Roadmap |
| 75 | + |
| 76 | +We've shared our vision and priorities for this project in our [roadmap](docs/roadmap.md). |
| 77 | + |
| 78 | +## Contributing |
| 79 | + |
| 80 | +This site is powered by [Jekyll](https://jekyllrb.com/). Our goal is for this project to reflect community best practices, so we'd love your input! Got a question or an idea? Check out our [contributing guidelines](/CONTRIBUTING.md) for ways to offer feedback and contribute. |
| 81 | + |
| 82 | +## Licenses |
| 83 | + |
| 84 | +Content is released under [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/). See [notices](notices.md) for complete details, including attribution guidelines, contribution terms, and software and third-party licenses and permissions. |
| 85 | + |
| 86 | +## Acknowledgments |
| 87 | + |
| 88 | +The initial release of these guides were authored by **@nayafia, @bkeepers, @stephbwills,** and **@mlinksva**. |
| 89 | + |
| 90 | +Thanks to **@aitchabee, @benbalter, @brettcannon, @caabernathy, @coralineada, @dmleong, @ericholscher, @gr2m, @janl, @jessfraz, @joshsimmons, @kfogel, @kytrinyx, @lee-dohm, @mikeal, @mikemcquaid, @nathansobo, @nruff, @nsqe, @orta, @parkr, @shazow, @steveklabnik,** and **@wooorm** for lending their valuable input and expertise leading up to the initial release, and to **@sophshep** and **@jeejkang** for designing and illustrating the guides. |
| 91 | + |
| 92 | +## Disclaimer |
| 93 | +While we've got advice about running an open source project, we're not lawyers. Be sure to read our [disclaimer](notices.md#legal-disclaimer) before diving in. |
0 commit comments