From owner-freebsd-doc@FreeBSD.ORG Sun Jul 16 03:30:16 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8FD416A4DF for ; Sun, 16 Jul 2006 03:30:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20D7A43D49 for ; Sun, 16 Jul 2006 03:30:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k6G3UFfs093754 for ; Sun, 16 Jul 2006 03:30:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k6G3UFBt093753; Sun, 16 Jul 2006 03:30:15 GMT (envelope-from gnats) Resent-Date: Sun, 16 Jul 2006 03:30:15 GMT Resent-Message-Id: <200607160330.k6G3UFBt093753@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, chinsan Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62B3216A4DE; Sun, 16 Jul 2006 03:27:57 +0000 (UTC) (envelope-from chinsan.tw@gmail.com) Received: from smtp2.bc.hgc.com.tw (smtp2.bc.hgc.com.tw [203.133.1.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D64043D46; Sun, 16 Jul 2006 03:27:56 +0000 (GMT) (envelope-from chinsan.tw@gmail.com) Received: from smtp2.bc.hgc.com.tw (u14-109.u203-187.giga.net.tw [203.187.14.109]) by smtp2.bc.hgc.com.tw (Postfix) with SMTP id 1257F2E970; Sun, 16 Jul 2006 11:27:56 +0800 (CST) Received: by smtp2.bc.hgc.com.tw (sSMTP sendmail emulation); Sun, 16 Jul 2006 11:32:10 +0800 Message-Id: <20060716032756.1257F2E970@smtp2.bc.hgc.com.tw> Date: Sun, 16 Jul 2006 11:32:10 +0800 From: chinsan To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: vanilla@FreeBSD.org Subject: docs/100367: [UPDATE] zh_TW: fdp-primer/translations 100% completed X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chinsan List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jul 2006 03:30:17 -0000 >Number: 100367 >Category: docs >Synopsis: [UPDATE] zh_TW: fdp-primer/translations 100% completed >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Sun Jul 16 03:30:15 GMT 2006 >Closed-Date: >Last-Modified: >Originator: chinsan >Release: FreeBSD 6.1-STABLE i386 >Organization: FreeBSD Taiwan >Environment: System: FreeBSD chinsan2.twbbs.org 6.1-STABLE FreeBSD 6.1-STABLE #1: Fri Jun 2 16:44:35 CST 2006 root@chinsan2.twbbs.org:/usr/obj/usr/src/sys/GENERIC i386 >Description: - fdp-primer/translations 100% completed ( http://chinsan2.twbbs.org/chinsan/zh_TW.Big5.fdp-primer.translations.diff ) - Trac Timeline: https://opensvn.csie.org/traccgi/freebsddoc/timeline Thanks. >How-To-Repeat: >Fix: --- zh_TW.Big5.fdp-primer.translations.diff begins here --- diff -ruN zh_TW.Big5/books/fdp-primer.orig/translations/chapter.sgml zh_TW.Big5/books/fdp-primer/translations/chapter.sgml --- zh_TW.Big5/books/fdp-primer.orig/translations/chapter.sgml Sun Jul 16 11:07:30 2006 +++ zh_TW.Big5/books/fdp-primer/translations/chapter.sgml Sun Jul 16 11:07:59 2006 @@ -36,10 +36,9 @@ 本章是翻譯 FreeBSD 文件(包含：FAQ, Handbook, tutorials, manual pages等)的常見問題(FAQ)。 - It is very heavily based on the translation FAQ - from the FreeBSD German Documentation Project, originally written by Frank - Gründer elwood@mc5sys.in-berlin.de and translated back to - English by Bernd Warken bwarken@mayn.de. + 本文件 主要 是以 FreeBSD 德文翻譯計劃的翻譯 FAQ 為母本而來的， + 原始撰稿者為 Frank Gründer elwood@mc5sys.in-berlin.de ，並由 + Bernd Warken bwarken@mayn.de 再翻譯回英文版。 The FAQ is maintained by the &a.doceng;. @@ -57,190 +56,152 @@ - What do i18n and l10n - mean? + i18n 跟 l10n 是什麼呢？ - i18n means - internationalization and l10n - means localization. They are just a convenient - shorthand. + i18n 是 + internationalization 的簡寫，而 l10n + 則是 localization 的簡寫。這些都是為了書寫方便而用的簡寫。 - i18n can be read as i followed by - 18 letters, followed by n. Similarly, - l10n is l followed by 10 letters, - followed by n. + i18n 就是開頭為 i 後面有 18 個字母，最後接 n。 + 同理， + l10n 則是開頭為 l 後面有 10 個字母，最後接 n。 - Is there a mailing list for translators? + 有專門給譯者參與討論的 mailing list 嗎？ - Yes. Different translation groups have their own mailing - lists. The list - of translation projects has more information about the - mailing lists and web sites run by each translation project. + 有啊，不同的語系翻譯者都各自有自屬的 mailing lists。這份 翻譯計劃清單 + 有列出各翻譯計劃的詳細 mailing lists 及相關網站。 - Are more translators needed? + 需要更多人一起參與翻譯嗎？ - Yes. The more people work on translation the faster it gets - done, and the faster changes to the English documentation are - mirrored in the translated documents. + 當然囉，越多人參與翻譯，那麼就能夠越快翻完，而且英文版文件若有增減、更新的話， + 各翻譯版也可以儘快同步囉。 - You do not have to be a professional translator to be able to - help. + 不一定得是專業譯者，才能參與翻譯的。 - What languages do I need to know? + 有要求哪些語言能力呢？ - Ideally, you will have a good knowledge of written English, and - obviously you will need to be fluent in the language you are - translating to. + 理論上，必須要對英文非常熟稔，而且很明顯地，對想翻譯的語言必須要能運用自如。 - English is not strictly necessary. For example, you could do a - Hungarian translation of the FAQ from the Spanish - translation. + 英文並非一定要會的。比如說，可以把西班牙文(Spanish)的 FAQ 翻譯為匈牙利文(Hungarian)。 - What software do I need to know? + 該學會哪些程式的使用呢？ - It is strongly recommended that you maintain a local copy of the - FreeBSD CVS repository (at least the documentation part) either - using CTM or - CVSup. The "Staying current with FreeBSD" - chapter in the Handbook explains how to use these - applications. + 強烈建議在自己機器上也建立 FreeBSD CVS repository 的備份(至少文件部分)，可以用 + CTM 或 + CVSup 都可以。Handbook 中的 "更新、升級 FreeBSD" + 一章內有提到如何使用這些程式。 - You should be comfortable using CVS. - This will allow you to see what has changed between different - versions of the files that make up the documentation. + 此外，需要熟悉 CVS 用法。 + 如此一來，你可以查閱不同版本之間的差異處。 - [XXX To Do -- write a tutorial that shows how to use CVSup to - get just the documentation, check it out, and see what has changed - between two arbitrary revisions] + [XXX To Do(尚未撰稿，仍待補充) -- 寫份上手說明(tutorial)來介紹如何以 CVSup + 取得文件部分，以及察看不同版本之間的差異。] - How do I find out who else might be translating to the same - language? + 要怎麼找出來還有誰要跟我一起翻譯的呢？ - The Documentation - Project translations page lists the translation efforts - that are currently known about. If others are already working - on translating documentation to your language, please do not - duplicate their efforts. Instead, contact them to see how you can - help. + 文件計劃的翻譯 這列了目前已知的各翻譯者成果 + ，如果已經有其他人也在做跟你一樣的翻譯工作，那麼請不要重複浪費人力， + 請與他們聯繫看看還有哪些地方可以幫上忙的。 - If no one is listed on that page as translating for your - language, then send a message to the &a.doc; in case someone else - is thinking of doing a translation, but has not announced it yet. + 若上面並未列出你母語的翻譯，或是也有人要翻譯但還未公開宣布的話，那麼就寄信到 &a.doc; 吧。 - No one else is translating to my language. What do I do? + 都沒人翻譯為我所使用的語言，該怎麼辦？ - Congratulations, you have just started the FreeBSD - your-language-here Documentation - Translation Project. Welcome aboard. + 恭喜啊，你剛好踏上 FreeBSD + 你的母語 文件翻譯計劃 的啟程之路，歡迎上船。 - First, decide whether or not you have got the time to spare. Since - you are the only person working on your language at the moment it is - going to be your responsibility to publicize your work and - coordinate any volunteers that might want to help you. + 首先呢，先判斷是否有妥善規劃時間，因為你只有一個人在翻而已， + 因此，相關翻譯成果的公布、與其他可能會幫忙的志工們聯繫這些工作都是你的職責所在。 - Write an email to the Documentation Project mailing list, - announcing that you are going to translate the documentation, so the - Documentation Project translations page can be maintained. + 寫信到 &a.doc; 向大家宣布你正準備要翻譯，然後文件計劃的翻譯部分就會更新相關資料 - If there is already someone in your country providing FreeBSD - mirroring services you should contact them and ask if you can - have some webspace for your project, and possibly an email - address or mailing list services. + 若你的國家已經有人提供 FreeBSD 的 mirror(映設) 服務的話，那麼就先跟他們聯繫， + 並詢問你是否在上面可以有網頁空間來放相關計劃資料， + 以及是否可以有提供 email 帳號或 mailing list 服務。 - Then pick a document and start translating. It is best to start - with something fairly small—either the FAQ, or one of the - tutorials. + 然後，就開始翻文件囉，一開始翻譯的時候，先找些篇幅較短的文件會比較容易些 + — 像是 FAQ 啦，或是如何上手之類的說明文章。 - I have translated some documentation, where do I send it? + 已經翻好一些文件了，該寄到哪呢？ - That depends. If you are already working with a translation team - (such as the Japanese team, or the German team) then they will have - their own procedures for handling submitted documentation, and these - will be outlined on their web pages. + 這要看情況而定。 若你是在翻譯團隊內做的話(像是日本、德國)， + 他們會有自己內部流程來決定翻譯文件怎麼送，這些大致流程會在他們網頁上面有寫。 - If you are the only person working on a particular language (or - you are responsible for a translation project and want to submit - your changes back to the FreeBSD project) then you should send your - translation to the FreeBSD project (see the next question). + 若你是某語系的唯一翻譯者(或你是負責某翻譯計劃，並想把成果回饋給 FreeBSD 計劃) + ，那麼你就應該把自己的翻譯成果寄給 FreeBSD 計劃。(細節請看下個問題) - I am the only person working on translating to this language, how - do I submit my translation? + 我是該語系的唯一翻譯者，該怎麼把翻譯成果寄出去呢？ - or + 或者 - We are a translation team, and want to submit documentation that - our members have translated for us? + 我們是翻譯團隊，該怎麼把我們成員翻譯成果寄出去呢？ - First, make sure your translation is organized properly. This - means that it should drop into the existing documentation tree and - build straight away. + 首先，請先確定你的翻譯成果組織條理分明，並可正確編譯，也就是說： + 把它擺到現有文件架構內是可以正確編譯成功的。 - Currently, the FreeBSD documentation is stored in a top level - directory called doc/. Directories below this - are named according to the language code they are written in, as - defined in ISO639 (/usr/share/misc/iso639 on a - version of FreeBSD newer than 20th January 1999). + 目前，FreeBSD 文件都是放在最上層的 doc/ 目錄內。 + 而該目錄下的則依其語系來做分類命名的，依照 ISO639 定義(/usr/share/misc/iso639 + 的這個 FreeBSD 版本比 1999/01/20 還新)。 - If your language can be encoded in different ways (for example, - Chinese) then there should be directories below this, one for each - encoding format you have provided. + 若你這個語系可能會有不同編碼方式(像是：中文) + 那麼就應該會像下面這樣，來依你所使用的編碼方式細分。 - Finally, you should have directories for each document. + 最後，你應該建立好各文件的目錄了。 - For example, a hypothetical Swedish translation might look - like: + 舉例來說，假設有瑞典文(Swedish)版的翻譯，那麼應該會長像： doc/ sv_SE.ISO8859-1/ @@ -250,162 +211,147 @@ Makefile book.sgml - sv_SE.ISO8859-1 is the name of the - translation, in - lang.encoding - form. Note the - two Makefiles, which will be used to build the documentation. + sv_SE.ISO8859-1 是依照 + 語系(lang).編碼(encoding) + 的規則來建立的譯名。 + 請注意：其中有兩個 Makefiles 檔，它們是用來編書的。 - Use &man.tar.1; and &man.gzip.1; to compress up your - documentation, and send it to the project. + 然後請用 &man.tar.1; 與 &man.gzip.1; 來把你的翻譯文件壓縮起來，並寄到本計劃來。 &prompt.user; cd doc -&prompt.user; tar cf swedish-docs.tar sv +&prompt.user; tar cf swedish-docs.tar sv_SE.ISO8859-1 &prompt.user; gzip -9 swedish-docs.tar - Put swedish-docs.tar.gz somewhere. If you - do not have access to your own webspace (perhaps your ISP does not - let you have any) then you can email &a.doceng;, and arrange to email - the files when it is convenient. - - Either way, you should use &man.send-pr.1; to submit a report - indicating that you have submitted the documentation. It would be - very helpful if you could get other people to look over your - translation and double check it first, since it is unlikely that the - person committing it will be fluent in the language. - - Someone (probably the Documentation Project Manager, currently - &a.doceng;) will then take your translation and confirm that it builds. - In particular, the following things will be looked at: + 接著，把 swedish-docs.tar.gz 放到網頁空間上，若你沒有自己網頁空間的話(ISP不提供) + ，那麼可以該檔寄到 &a.doceng; 來。 + + 還有，記得用 &man.send-pr.1; 以正式通知大家；你已經寄出翻譯文件了， + 還有，若有人可以幫忙檢閱、複審文件的話，對翻譯品質較好， + 因為這也有助於提升翻譯品質的流暢度。 + + 最後，會有人(可能是文件計劃總管，或是 &a.doceng; 成員) + 會檢閱你的翻譯文件，並確認是否可正常編譯。此外，他們會特別注意下列幾點： - Do all your files use RCS strings (such as "ID")? + 你的檔案是否都有用 RCS tag (像是 "ID" 之類的)？ - Does make all in the - sv_SE.ISO8859-1 directory work correctly? + sv_SE.ISO8859-1 是否可以順利 make all 編譯呢？ - Does make install work correctly? + make install 是否結果有正確？ - If there are any problems then whoever is looking at the - submission will get back to you to work them out. + 若有問題的話，那麼檢閱者會叮嚀你，來讓這些翻譯成果可以正確使用。 - If there are no problems your translation will be committed - as soon as possible. + 若沒問題的話，那麼就會很快把你的翻譯成果 commit 進去了。 - Can I include language or country specific text in my - translation? + 可以加入某語系或某國家才有的東西到翻譯內容內嗎？ - We would prefer that you did not. + 我們希望不要這麼做。 - For example, suppose that you are translating the Handbook to - Korean, and want to include a section about retailers in Korea in - your Handbook. + 舉例來說，假設你正準備把 Handbook 翻譯為韓文版， + 並希望把韓國零售處也加到你翻譯的 Handbook 韓文版內。 - There is no real reason why that information should not be in the - English (or German, or Spanish, or Japanese, or …) versions - as well. It is feasible that an English speaker in Korea might try - to pick up a copy of FreeBSD whilst over there. It also helps - increase FreeBSD's perceived presence around the globe, which is not - a bad thing. + 我們想不出來有啥原因，為什麼不把這些資訊提供給英文版呢？(或是德文、西班牙文、日文等 …) + 因為，有可能英語讀者跑去韓國時，會想買 FreeBSD 相關產品。 + 此外，這也可以提升 FreeBSD 的可見度，很顯然的，這並不是件壞事啊。 - If you have country specific information, please submit it as a - change to the English Handbook (using &man.send-pr.1;) and then - translate the change back to your language in the translated - Handbook. + 若你有某國才有的資料，請(用 &man.send-pr.1; )提供給英文版 Handbook 以作為修訂 + ，然後再把英文版的修訂部分，翻為你要翻譯的 Handbook 吧。 - Thanks. + 感恩，謝謝。 - How should language specific characters be included? + 要怎麼把該語系特有的字元寫進去翻譯內容呢？ - Non-ASCII characters in the documentation should be included - using SGML entities. + 文件內所有的非 ASCII(Non-ASCII) 字元，都要使用 SGML entities 才能寫進去。 - Briefly, these look like an ampersand (&), the name of the - entity, and a semi-colon (;). + 簡單來說，長相一開頭會是 & 符號(&)，然後是該 entity 名稱，最後接上分號(;)。 - The entity names are defined in ISO8879, which is in the ports - tree as textproc/iso8879. + 這些 entity 名稱都是 ISO8879 所制訂的，而 port tree 內則在 + textproc/iso8879。 - A few examples include: + 以下舉一些例子： - Entity + Entity名稱 - Appearance + 實際樣子 - Description + 介紹 &eacute; é - Small e with an acute accent + 小 e，並帶尖、重音(acute accent) &Eacute; É - Large E with an acute accent + 大 E，並帶尖、重音(acute accent) &uuml; ü - Small u with an umlaut + 小 u，並帶日耳曼語系中的母音變化(umlaut) - After you have installed the iso8879 port, the files in - /usr/local/share/sgml/iso8879 contain the - complete list. + 在裝了 iso8879 這個 port 之後，就可以在 + /usr/local/share/sgml/iso8879 找到這些的詳細列表。 - Addressing the reader + 如何稱呼讀者呢？ - In the English documents, the reader is addressed as - you, there is no formal/informal distinction as there - is in some languages. + 在英文文件內，讀者都是以 you 來稱呼，而有些語言並沒有正式/非正式的區隔。 - If you are translating to a language which does distinguish, use - whichever form is typically used in other technical documentation in - your language. If in doubt, use a mildly polite form. + 若你所要翻的語言可以區別這些差異，那麼請用該語系在一般技術文件上所使用的稱呼吧。 + 如果容易造成困惑的話，那麼請改用較中性的稱呼來取代。 + + - Do I need to include any additional information in my - translations? + 翻譯成果內要不要附上一些其他訊息呢？ - Yes. + 當然要。 - The header of the English version of each document will look - something like this: + 每份英文版原稿的開頭，通常會有像下面的內容： <!-- The FreeBSD Documentation Project @@ -413,23 +359,19 @@ $FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml,v 1.5 2000/07/07 18:38:38 dannyboy Exp $ --> - The exact boilerplate may change, but it will always include a - $FreeBSD$ line and the phrase The FreeBSD Documentation - Project. - Note that the $FreeBSD part is expanded automatically by - CVS, so it should be empty (just - $FreeBSD$) for new files. - - Your translated documents should include their own - $FreeBSD$ line, and change the - FreeBSD Documentation Project line to - The FreeBSD language - Documentation Project. + 實際上的內容可能稍有不同，但每份原稿都會附上 $FreeBSD$ 這一行以及 + The FreeBSD Documentation Project 宣告。 + 請注意：$FreeBSD 開頭的這行是會由 CVS 隨著每次異動而自動更改的， + 所以，新檔案的話請保持原狀(也就是只要寫 $FreeBSD$ 就好了)。 + + 翻譯文件中，必須都要有 $FreeBSD$ 這行，並且把 + FreeBSD Documentation Project 這行改為 + The FreeBSD 你的語系 + Documentation Project。 - In addition, you should add a third line which indicates which - revision of the English text this is based on. + 此外，還必須加上第三行來指出你所翻譯的，到底是以英文版原稿的哪一版本為母本所做的翻譯。 - So, the Spanish version of this file might start: + 因此呢，西班牙文版(Spanish)的檔案開頭應該是長像這樣： <!-- The FreeBSD Spanish Documentation Project --- zh_TW.Big5.fdp-primer.translations.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: