From chinsan.tw@gmail.com  Sun Jul 16 03:27:57 2006
Return-Path: <chinsan.tw@gmail.com>
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 <chinsan.tw@gmail.com>
Reply-To: chinsan <chinsan.tw@gmail.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc: vanilla@FreeBSD.org
Subject: [UPDATE] zh_TW: fdp-primer/translations 100% completed
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         100367
>Category:       docs
>Synopsis:       [UPDATE] zh_TW: fdp-primer/translations 100% completed
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jul 16 03:30:15 GMT 2006
>Closed-Date:    Sun Jul 16 10:20:44 GMT 2006
>Last-Modified:  Sun Jul 16 10:20:44 GMT 2006
>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 @@
 
   <para>O½Ķ FreeBSD (]tGFAQ, Handbook, tutorials, manual pages)`D(FAQ)C</para>
   
-  <para>It is <emphasis>very</emphasis> heavily based on the translation FAQ
-    from the FreeBSD German Documentation Project, originally written by Frank
-    Gr&uuml;nder <email>elwood@mc5sys.in-berlin.de</email> and translated back to
-    English by Bernd Warken <email>bwarken@mayn.de</email>.</para>
+  <para> <emphasis>Dn</emphasis> OH FreeBSD w½Ķp½Ķ FAQ ӨӪA
+    lZ̬ Frank Gr&uuml;nder <email>elwood@mc5sys.in-berlin.de</email> Aå 
+    Bernd Warken <email>bwarken@mayn.de</email> A½Ķ^^媩C</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> OOH</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> O
+	  <phrase>internationalization</phrase> ²gA <phrase>l10n</phrase>
+	  hO <phrase>localization</phrase> ²gCoǳOFѼgKӥΪ²gC</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> NO}Y <quote>i</quote> ᭱ 18 ӦrA̫ᱵ <quote>n</quote>C
+	  PzA
+	  <phrase>l10n</phrase> hO}Y <quote>l</quote> ᭱ 10 ӦrA̫ᱵ <quote>n</quote>C</para>
       </answer>
     </qandaentry>
 
     <qandaentry>
       <question>
-	<para>Is there a mailing list for translators?</para>
+	<para>MĶ̰ѻPQת mailing list ܡH</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>ڡAPyt½Ķ̳Uۦݪ mailing listsCo <ulink 
+	  url="http://www.freebsd.org/docproj/translations.html">½ĶpM</ulink> 
+	  CXU½ĶpԲ mailing lists άC</para>
       </answer>
     </qandaentry>
 
     <qandaentry>
       <question>
-	<para>Are more translators needed?</para>
+	<para>ݭnhH@_ѻP½ĶܡH</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>MoAVhHѻP½ĶANV½AӥB^媩YWBsܡA
+	  U½Ķ]iH֦PBoC</para>
 
-	<para>You do not have to be a professional translator to be able to
-	  help.</para>
+	<para>@woOM~Ķ̡A~ѻP½ĶC</para>
       </answer>
     </qandaentry>
 
     <qandaentry>
       <question>
-	<para>What languages do I need to know?</para>
+	<para>nDǻyOOH</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>zפWAn^D`ZAӥBܩaAQ½ĶynBΦۦpC</para>
 
-	<para>English is not strictly necessary. For example, you could do a
-	  Hungarian translation of the FAQ from the Spanish
-	  translation.</para>
+	<para>^ëD@wn|CpAiHZ(Spanish) FAQ ½ĶIQ(Hungarian)C</para>
       </answer>
     </qandaentry>
     
     <qandaentry>
       <question>
-	<para>What software do I need to know?</para>
+	<para>ӾǷ|ǵ{ϥΩOH</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>jPĳbۤvW]إ FreeBSD CVS repository ƥ(ܤ֤󳡤)AiH
+	  <application>CTM</application> 
+	  <application>CVSup</application> iHCHandbook  "sBɯ FreeBSD" 
+	  @pϥγoǵ{C</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>~Aݭnx <application>CVS</application> ΪkC
+	  p@ӡAAiHd\PtBC</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(|ZAݸɥR) -- gW⻡(tutorial)ӤЦpH CVSup 
+	  o󳡤AHιݤPtC]</para>
       </answer>
     </qandaentry>
 
     <qandaentry>
       <question>
-	<para>How do I find out who else might be translating to the same
-	  language?</para>
+	<para>nX٦֭nڤ@_½ĶOH</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">p½Ķ</ulink> oCFثewU½Ķ̦G
+	    ApGwgLH]bA@˪½Ķu@AФnƮOHOA
+	    лPLpôݬ٦ǦaiHWC</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>YWåCXAy½ĶAάO]Hn½Ķ٥}ťܡANHH &a.doc; aC
 	  </para>
       </answer>
     </qandaentry>
       
     <qandaentry>
       <question>
-	<para>No one else is translating to my language.  What do I do?</para>
+	<para>SH½ĶکҨϥΪyAӫH</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>߰ڡAAnW <quote>FreeBSD
+	  <replaceable>Ay</replaceable> ½Ķp</quote> ҵ{AwWC</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>OAP_O_WɶA]Au@ӤHb½ӤwA
+	  ]A½ĶGBPLi|ӤupôoǤu@OA¾dҦbC</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>gH &a.doc; VjaťAǳƭn½ĶAMp½ĶN|s</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>YAawgH FreeBSD  mirror(M]) AȪܡANLpôA
+	  ø߰ݧAO_bWiHŶөpơA
+	  HάO_iH email b mailing list AȡC</para>
 	
-	<para>Then pick a document and start translating. It is best to start
-	  with something fairly small&mdash;either the FAQ, or one of the
-	  tutorials.</para>
+	<para>MAN}l½oA@}l½ĶɭԡAǽgTu|e 
+	  &mdash; O FAQ աAάOpW⤧峹C</para>
       </answer>
     </qandaentry>
 
     <qandaentry>
       <question>
-	<para>I have translated some documentation, where do I send it?</para>
+	<para>wg½n@ǤFAӱHOH</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>onݱpөwC YAOb½Ķζ(O饻Bw)A
+	  L̷|ۤvy{ӨMw½ĶeAoǤjPy{|bL̺WgC</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>YAOYytߤ@½Ķ(ΧAOtdY½ĶpA÷Q⦨G^X FreeBSD p)
+	  AANӧۤv½ĶGH FreeBSD pC(Ӹ`ЬݤUӰD)</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>ڬOӻytߤ@½Ķ̡Aӫ½ĶGHXhOH</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>ڭ̬O½ĶζAӫڭ̦½ĶGHXhOH</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>AХTwA½ĶG´zAåiTsĶA]NOG
+	  ⥦\{[cOiHTsĶ\C</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>ثeAFreeBSD 󳣬Ob̤Wh <filename>doc/</filename> ؿC
+	  ӸӥؿUh̨ytӰRWA̷ ISO639 wq(<filename>/usr/share/misc/iso639</filename> 
+	  o FreeBSD  1999/01/20 ٷs)C</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>YAoӻyti|PsX覡(OG)
+	  Nӷ|UoˡAӨ̧AҨϥΪsX覡ӤC</para>
 
-	<para>Finally, you should have directories for each document.</para>
+	<para>̫AAӫإߦnU󪺥ؿFC</para>
 
-	<para>For example, a hypothetical Swedish translation might look
-	  like:</para>
+	<para>|ҨӻA](Swedish)½ĶAӷ|G</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> O̷ 
+	  <filename><replaceable>yt(lang)</replaceable>.<replaceable>sX(encoding)</replaceable></filename>
+	  WhӫإߪĶWC
+	  Ъ`NG䤤 <filename>Makefiles</filename> ɡA̬OΨӽsѪC</para>
 
-	<para>Use &man.tar.1; and &man.gzip.1; to compress up your
-	  documentation, and send it to the project.</para>
+	<para>MХ &man.tar.1; P &man.gzip.1; ӧA½ĶY_ӡAñH쥻pӡC</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>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>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 <filename>swedish-docs.tar.gz</filename> ŶWAYASۤvŶ(ISP)
+	  AiHɱH &a.doceng; ӡC</para>
+
+	<para>٦AOo &man.send-pr.1; HqjaFAwgHX½ĶFA
+	  ٦AYHiH˾\BƼf󪺸ܡA½Ķ~nA
+	  ]o]U󴣤½Ķ~誺yZסC</para>
+
+	<para>̫A|H(iOp`ޡAάO &a.doceng; )
+	  |˾\A½ĶAýT{O_i`sĶC~AL̷|SO`NUCXIG</para>
 
 	<orderedlist>
 	  <listitem>
-	    <para>Do all your files use RCS strings (such as "ID")?</para>
+	    <para>Aɮ׬O_ RCS tag (O "ID" )H</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> O_iHQ <command>make all</command> sĶOH</para>
 	  </listitem>
 	  
 	  <listitem>
-	    <para>Does <command>make install</command> work correctly?</para>
+	    <para><command>make install</command> O_GTH</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>YDܡA˾\̷|m{AAo½ĶGiHTϥΡC</para>
 
-	<para>If there are no problems your translation will be committed
-	  as soon as possible.</para>
+	<para>YSDܡAN|ܧ֧A½ĶG commit ihFC</para>
       </answer>
     </qandaentry>
 
     <qandaentry>
       <question>
-	<para>Can I include language or country specific text in my
-	  translation?</para>
+	<para>iH[JYytάYa~F½ĶeܡH</para>
       </question>
 
       <answer>
-	<para>We would prefer that you did not.</para>
+	<para>ڭ̧Ʊ椣no򰵡C</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>|ҨӻA]AǳƧ Handbook ½Ķ媩A
+	  çƱsB][A½Ķ Handbook 媩C</para>
 
-	<para>There is no real reason why that information should not be in the
-	  English (or German, or Spanish, or Japanese, or &hellip;) 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>ڭ̷QXӦԣ]A򤣧oǸTѵ^媩OH(άOwBZB嵥 &hellip;)
+	  ]Ai^yŪ̶]hɡA|QR FreeBSD ~C
+	  ~Ao]iH FreeBSD iסAMAoäOaưڡC</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>YAY~ơA( &man.send-pr.1; )ѵ^媩 Handbook H@׭q
+	  AMA^媩׭qA½An½Ķ Handbook aC</para>
 
-	<para>Thanks.</para>
+	<para>PA¡C</para>
       </answer>
     </qandaentry>
 
     <qandaentry>
       <question>
-	<para>How should language specific characters be included?</para>
+	<para>nӻytSrgih½ĶeOH</para>
       </question>
 
       <answer>
-	<para>Non-ASCII characters in the documentation should be included
-	  using SGML entities.</para>
+	<para>󤺩ҦD ASCII(Non-ASCII) rAnϥ SGML entities ~gihC</para>
 
-	<para>Briefly, these look like an ampersand (&amp;), the name of the
-	  entity, and a semi-colon (;).</para>
+	<para>²ӻAۤ@}Y|O &amp; Ÿ(&amp;)AMO entity W١A̫ᱵW(;)C</para>
 
-	<para>The entity names are defined in ISO8879, which is in the ports
-	  tree as <filename role="package">textproc/iso8879</filename>.</para>
+	<para>o entity WٳO ISO8879 ҨqA port tree hb 
+	  <filename role="package">textproc/iso8879</filename>C</para>
 
-	<para>A few examples include:</para>
+	<para>HU|@ǨҤlG</para>
 
 	<segmentedlist>
-          <segtitle>Entity</segtitle>
+          <segtitle>EntityW</segtitle>
 
-          <segtitle>Appearance</segtitle>
+          <segtitle>ڼˤl</segtitle>
 
-          <segtitle>Description</segtitle>
+          <segtitle></segtitle>
 
 	  <seglistitem>
 	    <seg>&amp;eacute;</seg>
 	    <seg>&eacute;</seg>
-	    <seg>Small <quote>e</quote> with an acute accent</seg>
+	    <seg>p <quote>e</quote>AñayB(acute accent)</seg>
 	  </seglistitem>
 
 	  <seglistitem>
 	    <seg>&amp;Eacute;</seg>
 	    <seg>&Eacute;</seg>
-	    <seg>Large <quote>E</quote> with an acute accent</seg>
+	    <seg>j <quote>E</quote>AñayB(acute accent)</seg>
 	  </seglistitem>
 
 	  <seglistitem>
 	    <seg>&amp;uuml;</seg>
 	    <seg>&uuml;</seg>
-	    <seg>Small <quote>u</quote> with an umlaut</seg>
+	    <seg>p <quote>u</quote>Añaհһytܤ(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>bˤF iso8879 o port ANiHb
+	  <filename>/usr/local/share/sgml/iso8879</filename> oǪԲӦCC</para>
       </answer>
     </qandaentry>
 
     <qandaentry>
       <question>
-	<para>Addressing the reader</para>
+	<para>p٩IŪ̩OH</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>b^󤺡AŪ̳OH <quote>you</quote> Ӻ٩IAӦǻyèS/DϹjC</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>YAҭn½yiHϧOoǮtAХθӻytb@޳NWҨϥΪ٩IaC
+	  pGeyxbܡAЧθʪ٩IӨNC</para>
+
+	<!--
+	  K http://fatpipi.cirx.org/~vanilla/rules.txt
+	  pDnA½Ķ峹ɶq֥Ϊ٩IAڥLΦrC
+	  pGuoΡANĥβĤTH(ΡiLjӫDiAj)A٦NOνƼ(ΡiA̡jӫDiAj)A
+	  Mo٬OotX媺WUyNCpGLOg "I" ½Ķ ""AhLipDC
+	  
+	  O夺jhƪ"You..... you ...etc" 
+	  곣iHiAj²ƩάOקKAo\ŪɭԪZPӦUC
+	-->
       </answer>
     </qandaentry>
 
     <qandaentry>
       <question>
-	<para>Do I need to include any additional information in my
-	  translations?</para>
+	<para>½ĶGnnW@ǨLTOH</para>
       </question>
 
       <answer>
-	<para>Yes.</para>
+	<para>MnC</para>
 
-	<para>The header of the English version of each document will look
-	  something like this:</para>
+	<para>C^媩Z}YAq`|UeG</para>
 
 	<programlisting>&lt;!--
      The FreeBSD Documentation Project
@@ -413,23 +359,19 @@
      &dollar;FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml,v 1.5 2000/07/07 18:38:38 dannyboy Exp &dollar;
 --&gt;</programlisting>
 
-	<para>The exact boilerplate may change, but it will always include a
-	  &dollar;FreeBSD&dollar; line and the phrase <literal>The FreeBSD Documentation
-	    Project</literal>.
-	  Note that the &dollar;FreeBSD part is expanded automatically by
-	  CVS, so it should be empty (just
-	  <literal>&dollar;FreeBSD&dollar;</literal>) for new files.</para>
-
-	<para>Your translated documents should include their own
-	  &dollar;FreeBSD&dollar; line, and change the
-	  <literal>FreeBSD Documentation Project</literal> line to
-	  <literal>The FreeBSD <replaceable>language</replaceable>
-	    Documentation Project</literal>.</para>
+	<para>ڤWeiyPACZ|W &dollar;FreeBSD&dollar; o@H 
+	  <literal>The FreeBSD Documentation Project</literal> ŧiC
+	  Ъ`NG&dollar;FreeBSD }YoO| CVS HۨCʦӦ۰ʧ諸A
+	  ҥHAsɮתܽЫO쪬(]NOung  <literal>&dollar;FreeBSD&dollar;</literal> NnF)C</para>
+
+	<para>½Ķ󤤡An &dollar;FreeBSD&dollar; oAåB
+	  <literal>FreeBSD Documentation Project</literal> oאּ
+	  <literal>The FreeBSD <replaceable>Ayt</replaceable>
+	    Documentation Project</literal>C</para>
 
-	<para>In addition, you should add a third line which indicates which
-	  revision of the English text this is based on.</para>
+	<para>~A٥[WĤTӫXA½ĶA쩳OH^媩Z@Ұ½ĶC</para>
 	
-	<para>So, the Spanish version of this file might start:</para>
+	<para>]OAZ媩(Spanish)ɮ׶}YӬOoˡG</para>
 
 	<programlisting>&lt;!--
      The FreeBSD Spanish Documentation Project
--- zh_TW.Big5.fdp-primer.translations.diff ends here ---


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: vanilla 
State-Changed-When: Sun Jul 16 10:20:42 UTC 2006 
State-Changed-Why:  
Committed, thanks. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=100367 
>Unformatted:
