- 100% translation completed.

Obtained from: The FreeBSD Traditional Chinese project
svn path=/head/; revision=30702
2007-09-01 07:14:19 +00:00 · 2007-09-01 07:14:19 +00:00 · a23978ba2a · 2020-12-08 03:00:23 +00:00
commit a23978ba2a
parent a07c6ef49d
1 changed files with 48 additions and 63 deletions
--- a/zh_TW.Big5/books/fdp-primer/writing-style/chapter.sgml
+++ b/zh_TW.Big5/books/fdp-primer/writing-style/chapter.sgml
@ -128,7 +128,7 @@
 	</informalexample>
 	
 	<para>以 man(manual)方面舉例，比較妥當的用法是第二句(有用到 SGML
-	  <sgmltag>citerefentry</sgmltag> tag)：</para>
+	  <sgmltag>citerefentry</sgmltag> 標籤)：</para>
 	
 	<informalexample>
 	  <para>請打 <command>man csh</command> 指令以參閱詳情說明。</para>
@ -143,7 +143,7 @@
      <term>每句後面加上兩個空白</term>

      <listitem>
-	<para>為增進文章之易讀，以及讓 <application>Emacs</application>
+	<para>為了使文章更易閱讀，以及讓 <application>Emacs</application>
 	  之類的工具容易運用，請在每一完整句子後面加上兩個空白。</para>

 	<para>不過，句號(.)後面有接大寫字母，
@ -189,7 +189,7 @@
 	通常每本書只會第一次提到時，才會列出完整詞彙，
 	但若您高興也可以在每章第一次提到時又列出完整詞彙。</para>

-      <para>此外，同一縮寫字在前三次使用時，須使用 &lt;acronym&gt; tag，
+      <para>此外，同一縮寫字在前三次使用時，須使用 &lt;acronym&gt; 標籤，
 	並把完整詞彙附在 <literal>role</literal> 屬性內做說明。
 	如此一來就會建立詞彙表，並且當滑鼠移至該縮寫字上方時，
 	就會顯示完整詞彙。</para>
@ -199,16 +199,16 @@
      <title>縮排</title>

      <para><emphasis>無論</emphasis> 檔案縮排設定為何，
-	每個檔案一開始的縮排(indentation)都是從 column 0 開始</para>
+	每個檔案一開始的縮排(indentation)都是從 0 縱列開始</para>

-      <para>未完的 tag 會以多兩個空白來增加縮排，
-	結尾的 tag 則少兩個空白來縮減縮排。  若已達 8 個空白，則以 tab 取代之。
+      <para>未完的標籤會以多兩個空白來增加縮排，
+	結尾的標籤則少兩個空白來縮減縮排。  若已達 8 個空白，則以 tab 取代之。
 	此外，在 tab 前面不要再用空白，也不要在每行後面加上空白。
 	每個 tag 的內文若超過一行的話，則接下來的就多兩個空白以做縮排。</para>

      <para>舉個例子，這節所用的寫法大致是下面這樣：</para>

-      <programlisting><![ CDATA [+--- This is column 0
+      <programlisting><![ CDATA [+--- 這是 0 縱列
 V
 <chapter>
  <title>...</title>
@ -220,7 +220,7 @@ V
      <title>縮排</title>

      <para><emphasis>無論</emphasis> 檔案縮排設定為何，
-        每個檔案一開始的縮排(indentation)都是從 column 0 開始。</para>
+        每個檔案一開始的縮排(indentation)都是從 0 縱列開始。</para>

      ...	
    </sect2>
@ -236,7 +236,7 @@ V

      <programlisting>augroup sgmledit
  autocmd FileType sgml set formatoptions=cq2l " 特殊格式選項
-  autocmd FileType sgml set textwidth=70       " 在 70 column 處即自動換行
+  autocmd FileType sgml set textwidth=70       " 在 70 縱列處即自動換行
  autocmd FileType sgml set shiftwidth=2       " 自動縮排 2 個空白
  autocmd FileType sgml set softtabstop=2      " 按 Tab 會自動轉為兩個空白縮排
  autocmd FileType sgml set tabstop=8          " 把 8 個空白轉為 tab
@ -251,7 +251,7 @@ augroup END</programlisting>
      <sect3>
 	<title>Tag 空行</title>
 	
-	<para>同一縮排等級的 tag 要以空一行來做區隔，而不同縮排等級的則不必。
+	<para>同一縮排等級的標籤要以空一行來做區隔，而不同縮排等級的則不必。
 	  比如：</para>

 	<informalexample>
@ -284,86 +284,73 @@ augroup END</programlisting>
      </sect3>

      <sect3>
-	<title>Separating tags</title>
+	<title>標籤的分行</title>

-	<para>Tags like <sgmltag>itemizedlist</sgmltag> which will
-	  always have further tags inside them, and in fact do not take
-	  character data themselves, are always on a line by
-	  themselves.</para>
+	<para>像是 <sgmltag>itemizedlist</sgmltag>
+	  這類的標籤事實上本身不含任何文字資料，必須得由其他標籤來補充內文。
+	  這類的標籤會獨用一整行。</para>

-	<para>Tags like <sgmltag>para</sgmltag> and
-	  <sgmltag>term</sgmltag> do not need other tags to contain
-	  normal character data, and their contents begin immediately
-	  after the tag, <emphasis>on the same line</emphasis>.</para>
+	<para>另外，像是 <sgmltag>para</sgmltag> 及
+	  <sgmltag>term</sgmltag> 這類的標籤並不需搭配其他標籤，
+	  就可附上文字資料，並且在標籤後面的<emphasis>同一行</emphasis>
+	  內即可立即寫上這些內文。</para>

-	<para>The same applies to when these two types of tags
-	  close.</para>
+	<para>當然，這兩類的標籤結尾時也是跟上面道理相同。</para>

-	<para>This leads to an obvious problem when mixing these
-	  tags.</para>
+	<para>不過，當上述這兩種標籤混用時，會有很明顯的困擾。</para>

-	<para>When a starting tag which cannot contain character data
-	  directly follows a tag of the type that requires other tags
-	  within it to use character data, they are on separate lines.
-	  The second tag should be properly indented.</para>
+	<para>當第一類標籤的後面接上第二類標籤的話，
+	  那麼要把這兩類標籤各自分行來寫。  後者標籤的段落，
+	  也是需要做適當縮排調整。</para>

-	<para>When a tag which can contain character data closes
-	  directly after a tag which cannot contain character data
-	  closes, they co-exist on the same line.</para>
+	<para>而第二類標籤結尾時，可以與第一類標籤的結尾放在同一行。</para>
      </sect3>
    </sect2>

    <sect2>
-      <title>White space changes</title>
+      <title>空白的更改</title>

-      <para>When committing changes, <emphasis>do not commit changes to the
-	  content at the same time as changes to the
-	  formatting</emphasis>.</para>
+      <para>在 commit 修改時，<emphasis>請別在修改內容的同時，
+	也一起更改編排格式</emphasis>。</para>
      
-      <para>This is so that the teams that convert the Handbook to other
-	languages can quickly see what content has actually changed in your
-	commit, without having to decide whether a line has changed because of
-	the content, or just because it has been refilled.</para>
+      <para>如此一來，像是 Handbook 翻譯團隊才能迅速找出你改了哪些內容，
+	而不用費心思去判斷該行的改變，是由於格式重排或者內容異動。</para>

-      <para>For example, if you have added two sentences to a paragraph, such
-	that the line lengths on the paragraph now go over 80 columns, first
-	commit your change with the too-long line lengths.  Then fix the line
-	wrapping, and commit this second change.  In the commit message for
-	the second change, be sure to indicate that this is a whitespace-only
-	change, and that the translation team can ignore it.</para>
+      <para>舉例說明，若要在某段加上兩個句子，如此一來該段落的某行勢必會超出 80
+	縱列，這時請先 commmit 修改。  接著，再修飾過長行落的換行，然後再次
+	commit 之。  而第二次的 commit 紀錄，請明確說明這只是 whitespace-only
+	(修改空白而已) 的更改，如此一來，翻譯團隊就可以忽略第二次 commit 了
+	。</para>
    </sect2>

    <sect2>
      <title>Nonbreaking space</title>

-      <para>Avoid line breaks in places where they look ugly
-	or make it difficult to follow a sentence.  Line breaks depend
-	on the width of the chosen output medium.  In particular, viewing
-	the HTML documentation with a text browser can lead to badly
-	formatted paragraphs like the next one:</para>
+      <para>請避免一些情況下的斷行：造成版面醜醜的、或是須連貫表達的同一句子。
+	斷行的情況會隨所閱讀的工具不同而有所不同。  尤其是透過純文字瀏覽器來看
+	HTML 時會更明顯看到類似下面這樣不好的編排段落：</para>

      <literallayout class="monospaced">Data capacity ranges from 40 MB to 15
 GB.  Hardware compression &hellip;</literallayout>

-      <para>The general entity <literal>&amp;nbsp;</literal> prohibits
-	line breaks between parts belonging together.  Use nonbreaking
-	spaces in the following places:</para>
+      <para>請使用 <literal>&amp;nbsp;</literal> 以避免同句子之間的斷行，
+	以下示範如何使用 nonbreaking spaces：</para>

      <itemizedlist>
 	<listitem>
-	  <para>between numbers and units:</para>
+	  <para>在數字與單位之間：</para>
 	  <programlisting><![ CDATA [57600&nbsp;bps]]></programlisting>
 	</listitem>

 	<listitem>
-	  <para>between program names and version numbers:</para>
+	  <para>在程式名稱與版號之間：</para>
 	  <programlisting><![ CDATA [FreeBSD&nbsp;4.7]]></programlisting>
 	</listitem>

 	<listitem>
-	  <para>between multiword names (use with caution when applying this
-	    to more than 3-4 word names like <quote>The FreeBSD Brazilian
-	      Portuguese Documentation Project</quote>):</para>
+	  <para>multiword 之間 (使用時請小心，像是 <quote>The FreeBSD Brazilian
+	    Portuguese Documentation Project</quote> 這類由三到四個字所組成的，
+	    則不用加。)：</para>
 	  <programlisting><![ CDATA [Sun&nbsp;Microsystems]]></programlisting>  
 	</listitem>
      </itemizedlist>
@ -371,14 +358,12 @@ GB.  Hardware compression &hellip;</literallayout>
  </sect1>

  <sect1 id="writing-style-word-list">
-    <title>Word list</title>
+    <title>詞彙表</title>

-    <para>The following is a small list of words spelled the way they
-      should be used in the FreeBSD Documentation Project.  If the
-      word you are looking for is not in this list, then please
-      consult the <ulink
+    <para>以下為 FreeBSD 文件計劃編排時所採用的小型詞彙表。
+      若找不到要找的詞彙，請參閱 <ulink
      url="http://www.oreilly.com/oreilly/author/stylesheet.html">O'Reilly
-      word list</ulink>.</para>
+      word list</ulink>。</para>

    <itemizedlist>
      <listitem>