- fdp-primer/translations 100% completed
PR: docs/100367 Submitted by: chinsan.tw at gmail.com
This commit is contained in:
Vanilla I. Shu
parent
4439291abe
commit
c40b0a32e1
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=28302
1 changed files with 133 additions and 191 deletions
|
|
@ -36,10 +36,9 @@
|
|||
|
||||
<para>本章是翻譯 FreeBSD 文件(包含：FAQ, Handbook, tutorials, manual pages等)的常見問題(FAQ)。</para>
|
||||
|
||||
<para>It is <emphasis>very</emphasis> heavily based on the translation FAQ
|
||||
from the FreeBSD German Documentation Project, originally written by Frank
|
||||
Gründer <email>elwood@mc5sys.in-berlin.de</email> and translated back to
|
||||
English by Bernd Warken <email>bwarken@mayn.de</email>.</para>
|
||||
<para>本文件 <emphasis>主要</emphasis> 是以 FreeBSD 德文翻譯計劃的翻譯 FAQ 為母本而來的，
|
||||
原始撰稿者為 Frank Gründer <email>elwood@mc5sys.in-berlin.de</email> ，並由
|
||||
Bernd Warken <email>bwarken@mayn.de</email> 再翻譯回英文版。</para>
|
||||
|
||||
<para>The FAQ is maintained by the &a.doceng;.</para>
|
||||
|
||||
|
|
@ -57,190 +56,152 @@
|
|||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>What do <phrase>i18n</phrase> and <phrase>l10n</phrase>
|
||||
mean?</para>
|
||||
<para><phrase>i18n</phrase> 跟 <phrase>l10n</phrase> 是什麼呢？</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para><phrase>i18n</phrase> means
|
||||
<phrase>internationalization</phrase> and <phrase>l10n</phrase>
|
||||
means <phrase>localization</phrase>. They are just a convenient
|
||||
shorthand.</para>
|
||||
<para><phrase>i18n</phrase> 是
|
||||
<phrase>internationalization</phrase> 的簡寫，而 <phrase>l10n</phrase>
|
||||
則是 <phrase>localization</phrase> 的簡寫。這些都是為了書寫方便而用的簡寫。</para>
|
||||
|
||||
<para><phrase>i18n</phrase> can be read as <quote>i</quote> followed by
|
||||
18 letters, followed by <quote>n</quote>. Similarly,
|
||||
<phrase>l10n</phrase> is <quote>l</quote> followed by 10 letters,
|
||||
followed by <quote>n</quote>.</para>
|
||||
<para><phrase>i18n</phrase> 就是開頭為 <quote>i</quote> 後面有 18 個字母，最後接 <quote>n</quote>。
|
||||
同理，
|
||||
<phrase>l10n</phrase> 則是開頭為 <quote>l</quote> 後面有 10 個字母，最後接 <quote>n</quote>。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Is there a mailing list for translators?</para>
|
||||
<para>有專門給譯者參與討論的 mailing list 嗎？</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Yes. Different translation groups have their own mailing
|
||||
lists. The <ulink url="http://www.freebsd.org/docproj/translations.html">list
|
||||
of translation projects</ulink> has more information about the
|
||||
mailing lists and web sites run by each translation project.</para>
|
||||
<para>有啊，不同的語系翻譯者都各自有自屬的 mailing lists。這份 <ulink
|
||||
url="http://www.freebsd.org/docproj/translations.html">翻譯計劃清單</ulink>
|
||||
有列出各翻譯計劃的詳細 mailing lists 及相關網站。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Are more translators needed?</para>
|
||||
<para>需要更多人一起參與翻譯嗎？</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>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.</para>
|
||||
<para>當然囉，越多人參與翻譯，那麼就能夠越快翻完，而且英文版文件若有增減、更新的話，
|
||||
各翻譯版也可以儘快同步囉。</para>
|
||||
|
||||
<para>You do not have to be a professional translator to be able to
|
||||
help.</para>
|
||||
<para>不一定得是專業譯者，才能參與翻譯的。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>What languages do I need to know?</para>
|
||||
<para>有要求哪些語言能力呢？</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>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.</para>
|
||||
<para>理論上，必須要對英文非常熟稔，而且很明顯地，對想翻譯的語言必須要能運用自如。</para>
|
||||
|
||||
<para>English is not strictly necessary. For example, you could do a
|
||||
Hungarian translation of the FAQ from the Spanish
|
||||
translation.</para>
|
||||
<para>英文並非一定要會的。比如說，可以把西班牙文(Spanish)的 FAQ 翻譯為匈牙利文(Hungarian)。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>What software do I need to know?</para>
|
||||
<para>該學會哪些程式的使用呢？</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>It is strongly recommended that you maintain a local copy of the
|
||||
FreeBSD CVS repository (at least the documentation part) either
|
||||
using <application>CTM</application> or
|
||||
<application>CVSup</application>. The "Staying current with FreeBSD"
|
||||
chapter in the Handbook explains how to use these
|
||||
applications.</para>
|
||||
<para>強烈建議在自己機器上也建立 FreeBSD CVS repository 的備份(至少文件部分)，可以用
|
||||
<application>CTM</application> 或
|
||||
<application>CVSup</application> 都可以。Handbook 中的 "更新、升級 FreeBSD"
|
||||
一章內有提到如何使用這些程式。</para>
|
||||
|
||||
<para>You should be comfortable using <application>CVS</application>.
|
||||
This will allow you to see what has changed between different
|
||||
versions of the files that make up the documentation.</para>
|
||||
<para>此外，需要熟悉 <application>CVS</application> 用法。
|
||||
如此一來，你可以查閱不同版本之間的差異處。</para>
|
||||
|
||||
<para>[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]</para>
|
||||
<para>[XXX To Do(尚未撰稿，仍待補充) -- 寫份上手說明(tutorial)來介紹如何以 CVSup
|
||||
取得文件部分，以及察看不同版本之間的差異。]</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>How do I find out who else might be translating to the same
|
||||
language?</para>
|
||||
<para>要怎麼找出來還有誰要跟我一起翻譯的呢？</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>The <ulink
|
||||
url="http://www.FreeBSD.org/docproj/translations.html">Documentation
|
||||
Project translations page</ulink> 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.</para>
|
||||
<para><ulink
|
||||
url="http://www.FreeBSD.org/docproj/translations.html">文件計劃的翻譯</ulink> 這列了目前已知的各翻譯者成果
|
||||
，如果已經有其他人也在做跟你一樣的翻譯工作，那麼請不要重複浪費人力，
|
||||
請與他們聯繫看看還有哪些地方可以幫上忙的。</para>
|
||||
|
||||
<para>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.
|
||||
<para>若上面並未列出你母語的翻譯，或是也有人要翻譯但還未公開宣布的話，那麼就寄信到 &a.doc; 吧。
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>No one else is translating to my language. What do I do?</para>
|
||||
<para>都沒人翻譯為我所使用的語言，該怎麼辦？</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Congratulations, you have just started the <quote>FreeBSD
|
||||
<replaceable>your-language-here</replaceable> Documentation
|
||||
Translation Project</quote>. Welcome aboard.</para>
|
||||
<para>恭喜啊，你剛好踏上 <quote>FreeBSD
|
||||
<replaceable>你的母語</replaceable> 文件翻譯計劃</quote> 的啟程之路，歡迎上船。</para>
|
||||
|
||||
<para>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.</para>
|
||||
<para>首先呢，先判斷是否有妥善規劃時間，因為你只有一個人在翻而已，
|
||||
因此，相關翻譯成果的公布、與其他可能會幫忙的志工們聯繫這些工作都是你的職責所在。</para>
|
||||
|
||||
<para>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.</para>
|
||||
<para>寫信到 &a.doc; 向大家宣布你正準備要翻譯，然後文件計劃的翻譯部分就會更新相關資料</para>
|
||||
|
||||
<para>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.</para>
|
||||
<para>若你的國家已經有人提供 FreeBSD 的 mirror(映設) 服務的話，那麼就先跟他們聯繫，
|
||||
並詢問你是否在上面可以有網頁空間來放相關計劃資料，
|
||||
以及是否可以有提供 email 帳號或 mailing list 服務。</para>
|
||||
|
||||
<para>Then pick a document and start translating. It is best to start
|
||||
with something fairly small—either the FAQ, or one of the
|
||||
tutorials.</para>
|
||||
<para>然後，就開始翻文件囉，一開始翻譯的時候，先找些篇幅較短的文件會比較容易些
|
||||
— 像是 FAQ 啦，或是如何上手之類的說明文章。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>I have translated some documentation, where do I send it?</para>
|
||||
<para>已經翻好一些文件了，該寄到哪呢？</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>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.</para>
|
||||
<para>這要看情況而定。 若你是在翻譯團隊內做的話(像是日本、德國)，
|
||||
他們會有自己內部流程來決定翻譯文件怎麼送，這些大致流程會在他們網頁上面有寫。</para>
|
||||
|
||||
<para>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).</para>
|
||||
<para>若你是某語系的唯一翻譯者(或你是負責某翻譯計劃，並想把成果回饋給 FreeBSD 計劃)
|
||||
，那麼你就應該把自己的翻譯成果寄給 FreeBSD 計劃。(細節請看下個問題)</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>I am the only person working on translating to this language, how
|
||||
do I submit my translation?</para>
|
||||
<para>我是該語系的唯一翻譯者，該怎麼把翻譯成果寄出去呢？</para>
|
||||
|
||||
<para>or</para>
|
||||
<para>或者</para>
|
||||
|
||||
<para>We are a translation team, and want to submit documentation that
|
||||
our members have translated for us?</para>
|
||||
<para>我們是翻譯團隊，該怎麼把我們成員翻譯成果寄出去呢？</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>First, make sure your translation is organized properly. This
|
||||
means that it should drop into the existing documentation tree and
|
||||
build straight away.</para>
|
||||
<para>首先，請先確定你的翻譯成果組織條理分明，並可正確編譯，也就是說：
|
||||
把它擺到現有文件架構內是可以正確編譯成功的。</para>
|
||||
|
||||
<para>Currently, the FreeBSD documentation is stored in a top level
|
||||
directory called <filename>doc/</filename>. Directories below this
|
||||
are named according to the language code they are written in, as
|
||||
defined in ISO639 (<filename>/usr/share/misc/iso639</filename> on a
|
||||
version of FreeBSD newer than 20th January 1999).</para>
|
||||
<para>目前，FreeBSD 文件都是放在最上層的 <filename>doc/</filename> 目錄內。
|
||||
而該目錄下的則依其語系來做分類命名的，依照 ISO639 定義(<filename>/usr/share/misc/iso639</filename>
|
||||
的這個 FreeBSD 版本比 1999/01/20 還新)。</para>
|
||||
|
||||
<para>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.</para>
|
||||
<para>若你這個語系可能會有不同編碼方式(像是：中文)
|
||||
那麼就應該會像下面這樣，來依你所使用的編碼方式細分。</para>
|
||||
|
||||
<para>Finally, you should have directories for each document.</para>
|
||||
<para>最後，你應該建立好各文件的目錄了。</para>
|
||||
|
||||
<para>For example, a hypothetical Swedish translation might look
|
||||
like:</para>
|
||||
<para>舉例來說，假設有瑞典文(Swedish)版的翻譯，那麼應該會長像：</para>
|
||||
|
||||
<programlisting>doc/
|
||||
sv_SE.ISO8859-1/
|
||||
|
|
@ -250,162 +211,147 @@
|
|||
Makefile
|
||||
book.sgml</programlisting>
|
||||
|
||||
<para><literal>sv_SE.ISO8859-1</literal> is the name of the
|
||||
translation, in
|
||||
<filename><replaceable>lang</replaceable>.<replaceable>encoding</replaceable></filename>
|
||||
form. Note the
|
||||
two Makefiles, which will be used to build the documentation.</para>
|
||||
<para><literal>sv_SE.ISO8859-1</literal> 是依照
|
||||
<filename><replaceable>語系(lang)</replaceable>.<replaceable>編碼(encoding)</replaceable></filename>
|
||||
的規則來建立的譯名。
|
||||
請注意：其中有兩個 <filename>Makefiles</filename> 檔，它們是用來編書的。</para>
|
||||
|
||||
<para>Use &man.tar.1; and &man.gzip.1; to compress up your
|
||||
documentation, and send it to the project.</para>
|
||||
<para>然後請用 &man.tar.1; 與 &man.gzip.1; 來把你的翻譯文件壓縮起來，並寄到本計劃來。</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>cd doc</userinput>
|
||||
&prompt.user; <userinput>tar cf swedish-docs.tar sv</userinput>
|
||||
&prompt.user; <userinput>tar cf swedish-docs.tar sv_SE.ISO8859-1</userinput>
|
||||
&prompt.user; <userinput>gzip -9 swedish-docs.tar</userinput></screen>
|
||||
|
||||
<para>Put <filename>swedish-docs.tar.gz</filename> 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.</para>
|
||||
<para>接著，把 <filename>swedish-docs.tar.gz</filename> 放到網頁空間上，若你沒有自己網頁空間的話(ISP不提供)
|
||||
，那麼可以該檔寄到 &a.doceng; 來。</para>
|
||||
|
||||
<para>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.</para>
|
||||
<para>還有，記得用 &man.send-pr.1; 以正式通知大家；你已經寄出翻譯文件了，
|
||||
還有，若有人可以幫忙檢閱、複審文件的話，對翻譯品質較好，
|
||||
因為這也有助於提升翻譯品質的流暢度。</para>
|
||||
|
||||
<para>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:</para>
|
||||
<para>最後，會有人(可能是文件計劃總管，或是 &a.doceng; 成員)
|
||||
會檢閱你的翻譯文件，並確認是否可正常編譯。此外，他們會特別注意下列幾點：</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Do all your files use RCS strings (such as "ID")?</para>
|
||||
<para>你的檔案是否都有用 RCS tag (像是 "ID" 之類的)？</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Does <command>make all</command> in the
|
||||
<filename>sv_SE.ISO8859-1</filename> directory work correctly?</para>
|
||||
<para><filename>sv_SE.ISO8859-1</filename> 是否可以順利 <command>make all</command> 編譯呢？</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Does <command>make install</command> work correctly?</para>
|
||||
<para><command>make install</command> 是否結果有正確？</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<para>If there are any problems then whoever is looking at the
|
||||
submission will get back to you to work them out.</para>
|
||||
<para>若有問題的話，那麼檢閱者會叮嚀你，來讓這些翻譯成果可以正確使用。</para>
|
||||
|
||||
<para>If there are no problems your translation will be committed
|
||||
as soon as possible.</para>
|
||||
<para>若沒問題的話，那麼就會很快把你的翻譯成果 commit 進去了。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Can I include language or country specific text in my
|
||||
translation?</para>
|
||||
<para>可以加入某語系或某國家才有的東西到翻譯內容內嗎？</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>We would prefer that you did not.</para>
|
||||
<para>我們希望不要這麼做。</para>
|
||||
|
||||
<para>For example, suppose that you are translating the Handbook to
|
||||
Korean, and want to include a section about retailers in Korea in
|
||||
your Handbook.</para>
|
||||
<para>舉例來說，假設你正準備把 Handbook 翻譯為韓文版，
|
||||
並希望把韓國零售處也加到你翻譯的 Handbook 韓文版內。</para>
|
||||
|
||||
<para>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.</para>
|
||||
<para>我們想不出來有啥原因，為什麼不把這些資訊提供給英文版呢？(或是德文、西班牙文、日文等 …)
|
||||
因為，有可能英語讀者跑去韓國時，會想買 FreeBSD 相關產品。
|
||||
此外，這也可以提升 FreeBSD 的可見度，很顯然的，這並不是件壞事啊。</para>
|
||||
|
||||
<para>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.</para>
|
||||
<para>若你有某國才有的資料，請(用 &man.send-pr.1; )提供給英文版 Handbook 以作為修訂
|
||||
，然後再把英文版的修訂部分，翻為你要翻譯的 Handbook 吧。</para>
|
||||
|
||||
<para>Thanks.</para>
|
||||
<para>感恩，謝謝。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>How should language specific characters be included?</para>
|
||||
<para>要怎麼把該語系特有的字元寫進去翻譯內容呢？</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Non-ASCII characters in the documentation should be included
|
||||
using SGML entities.</para>
|
||||
<para>文件內所有的非 ASCII(Non-ASCII) 字元，都要使用 SGML entities 才能寫進去。</para>
|
||||
|
||||
<para>Briefly, these look like an ampersand (&), the name of the
|
||||
entity, and a semi-colon (;).</para>
|
||||
<para>簡單來說，長相一開頭會是 & 符號(&)，然後是該 entity 名稱，最後接上分號(;)。</para>
|
||||
|
||||
<para>The entity names are defined in ISO8879, which is in the ports
|
||||
tree as <filename role="package">textproc/iso8879</filename>.</para>
|
||||
<para>這些 entity 名稱都是 ISO8879 所制訂的，而 port tree 內則在
|
||||
<filename role="package">textproc/iso8879</filename>。</para>
|
||||
|
||||
<para>A few examples include:</para>
|
||||
<para>以下舉一些例子：</para>
|
||||
|
||||
<segmentedlist>
|
||||
<segtitle>Entity</segtitle>
|
||||
<segtitle>Entity名稱</segtitle>
|
||||
|
||||
<segtitle>Appearance</segtitle>
|
||||
<segtitle>實際樣子</segtitle>
|
||||
|
||||
<segtitle>Description</segtitle>
|
||||
<segtitle>介紹</segtitle>
|
||||
|
||||
<seglistitem>
|
||||
<seg>&eacute;</seg>
|
||||
<seg>é</seg>
|
||||
<seg>Small <quote>e</quote> with an acute accent</seg>
|
||||
<seg>小 <quote>e</quote>，並帶尖、重音(acute accent)</seg>
|
||||
</seglistitem>
|
||||
|
||||
<seglistitem>
|
||||
<seg>&Eacute;</seg>
|
||||
<seg>É</seg>
|
||||
<seg>Large <quote>E</quote> with an acute accent</seg>
|
||||
<seg>大 <quote>E</quote>，並帶尖、重音(acute accent)</seg>
|
||||
</seglistitem>
|
||||
|
||||
<seglistitem>
|
||||
<seg>&uuml;</seg>
|
||||
<seg>ü</seg>
|
||||
<seg>Small <quote>u</quote> with an umlaut</seg>
|
||||
<seg>小 <quote>u</quote>，並帶日耳曼語系中的母音變化(umlaut)</seg>
|
||||
</seglistitem>
|
||||
</segmentedlist>
|
||||
|
||||
<para>After you have installed the iso8879 port, the files in
|
||||
<filename>/usr/local/share/sgml/iso8879</filename> contain the
|
||||
complete list.</para>
|
||||
<para>在裝了 iso8879 這個 port 之後，就可以在
|
||||
<filename>/usr/local/share/sgml/iso8879</filename> 找到這些的詳細列表。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Addressing the reader</para>
|
||||
<para>如何稱呼讀者呢？</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>In the English documents, the reader is addressed as
|
||||
<quote>you</quote>, there is no formal/informal distinction as there
|
||||
is in some languages.</para>
|
||||
<para>在英文文件內，讀者都是以 <quote>you</quote> 來稱呼，而有些語言並沒有正式/非正式的區隔。</para>
|
||||
|
||||
<para>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.</para>
|
||||
<para>若你所要翻的語言可以區別這些差異，那麼請用該語系在一般技術文件上所使用的稱呼吧。
|
||||
如果容易造成困惑的話，那麼請改用較中性的稱呼來取代。</para>
|
||||
|
||||
<!--
|
||||
摘自 http://fatpipi.cirx.org/~vanilla/rules.txt
|
||||
如非必要，翻譯文章內盡量少用直接稱呼你我他的用字。
|
||||
如果真的得用，就採用第三人稱(用【他】而非【你】)，還有就是用複數(用【你們】而非【你】)，
|
||||
當然這還是得配合原文的上下語意。如果他是寫 "I" 而翻譯成 "我"，則無可厚非。
|
||||
|
||||
但是對於文內絕大多數的"You..... you ...etc"
|
||||
其實都可以把【你】簡化或是避免掉，這對閱讀時候的順暢感應該有幫助。
|
||||
-->
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Do I need to include any additional information in my
|
||||
translations?</para>
|
||||
<para>翻譯成果內要不要附上一些其他訊息呢？</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Yes.</para>
|
||||
<para>當然要。</para>
|
||||
|
||||
<para>The header of the English version of each document will look
|
||||
something like this:</para>
|
||||
<para>每份英文版原稿的開頭，通常會有像下面的內容：</para>
|
||||
|
||||
<programlisting><!--
|
||||
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 $
|
||||
--></programlisting>
|
||||
|
||||
<para>The exact boilerplate may change, but it will always include a
|
||||
$FreeBSD$ line and the phrase <literal>The FreeBSD Documentation
|
||||
Project</literal>.
|
||||
Note that the $FreeBSD part is expanded automatically by
|
||||
CVS, so it should be empty (just
|
||||
<literal>$FreeBSD$</literal>) for new files.</para>
|
||||
<para>實際上的內容可能稍有不同，但每份原稿都會附上 $FreeBSD$ 這一行以及
|
||||
<literal>The FreeBSD Documentation Project</literal> 宣告。
|
||||
請注意：$FreeBSD 開頭的這行是會由 CVS 隨著每次異動而自動更改的，
|
||||
所以，新檔案的話請保持原狀(也就是只要寫 <literal>$FreeBSD$</literal> 就好了)。</para>
|
||||
|
||||
<para>Your translated documents should include their own
|
||||
$FreeBSD$ line, and change the
|
||||
<literal>FreeBSD Documentation Project</literal> line to
|
||||
<literal>The FreeBSD <replaceable>language</replaceable>
|
||||
Documentation Project</literal>.</para>
|
||||
<para>翻譯文件中，必須都要有 $FreeBSD$ 這行，並且把
|
||||
<literal>FreeBSD Documentation Project</literal> 這行改為
|
||||
<literal>The FreeBSD <replaceable>你的語系</replaceable>
|
||||
Documentation Project</literal>。</para>
|
||||
|
||||
<para>In addition, you should add a third line which indicates which
|
||||
revision of the English text this is based on.</para>
|
||||
<para>此外，還必須加上第三行來指出你所翻譯的，到底是以英文版原稿的哪一版本為母本所做的翻譯。</para>
|
||||
|
||||
<para>So, the Spanish version of this file might start:</para>
|
||||
<para>因此呢，西班牙文版(Spanish)的檔案開頭應該是長像這樣：</para>
|
||||
|
||||
<programlisting><!--
|
||||
The FreeBSD Spanish Documentation Project
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue