docs/100367: [UPDATE] zh_TW: fdp-primer/translations 100% completed
chinsan
chinsan.tw at gmail.com
Sun Jul 16 03:30:17 UTC 2006
>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 at 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 ¤å¥ó(¥]§t¡GFAQ, 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ünder <email>elwood at mc5sys.in-berlin.de</email> and translated back to
- English by Bernd Warken <email>bwarken at mayn.de</email>.</para>
+ <para>¥»¤å¥ó <emphasis>¥Dn</emphasis> ¬O¥H FreeBSD ¼w¤å½Ķp¹ºªºÂ½Ä¶ FAQ ¬°¥À¥»¦Ó¨Óªº¡A
+ ì©l¼¶½ZªÌ¬° Frank Gründer <email>elwood at mc5sys.in-berlin.de</email> ¡A¨Ã¥Ñ
+ Bernd Warken <email>bwarken at 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> ¬O¤°»ò©O¡H</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> ªºÂ²¼g¡A¦Ó <phrase>l10n</phrase>
+ «h¬O <phrase>localization</phrase> ªºÂ²¼g¡C³o¨Ç³£¬O¬°¤F®Ñ¼g¤è«K¦Ó¥ÎªºÂ²¼g¡C</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> ´N¬O¶}ÀY¬° <quote>i</quote> «á±¦³ 18 Ó¦r¥À¡A³Ì«á±µ <quote>n</quote>¡C
+ ¦P²z¡A
+ <phrase>l10n</phrase> «h¬O¶}ÀY¬° <quote>l</quote> «á±¦³ 10 Ó¦r¥À¡A³Ì«á±µ <quote>n</quote>¡C</para>
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>Is there a mailing list for translators?</para>
+ <para>¦³±Mªùµ¹Ä¶ªÌ°Ñ»P°Q½×ªº 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>¦³°Ú¡A¤£¦Pªº»y¨t½ĶªÌ³£¦U¦Û¦³¦ÛÄݪº mailing lists¡C³o¥÷ <ulink
+ url="http://www.freebsd.org/docproj/translations.html">½Ķp¹º²M³æ</ulink>
+ ¦³¦C¥X¦U½Ķp¹ºªº¸Ô²Ó mailing lists ¤Î¬ÛÃöºô¯¸¡C</para>
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>Are more translators needed?</para>
+ <para>»Ýn§ó¦h¤H¤@°_°Ñ»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>·íµMÅo¡A¶V¦h¤H°Ñ»P½Ķ¡A¨º»ò´N¯à°÷¶V§Ö½§¹¡A¦Ó¥B^¤åª©¤å¥óY¦³¼W´î¡B§ó·sªº¸Ü¡A
+ ¦U½Ķª©¤]¥i¥H¾¨§Ö¦P¨BÅo¡C</para>
- <para>You do not have to be a professional translator to be able to
- help.</para>
+ <para>¤£¤@©w±o¬O±M·~ĶªÌ¡A¤~¯à°Ñ»P½Ķªº¡C</para>
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>What languages do I need to know?</para>
+ <para>¦³n¨Dþ¨Ç»y¨¥¯à¤O©O¡H</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½×¤W¡A¥²¶·n¹ï^¤å«D±`¼ô¸Z¡A¦Ó¥B«Ü©úÅã¦a¡A¹ï·Q½Ķªº»y¨¥¥²¶·n¯à¹B¥Î¦Û¦p¡C</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·|ªº¡C¤ñ¦p»¡¡A¥i¥H§â¦è¯Z¤ú¤å(Spanish)ªº FAQ ½Ķ¬°¦I¤ú§Q¤å(Hungarian)¡C</para>
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>What software do I need to know?</para>
+ <para>¸Ó¾Ç·|þ¨Çµ{¦¡ªº¨Ï¥Î©O¡H</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>±j¯P«Øij¦b¦Û¤v¾÷¾¹¤W¤]«Ø¥ß FreeBSD CVS repository ªº³Æ¥÷(¦Ü¤Ö¤å¥ó³¡¤À)¡A¥i¥H¥Î
+ <application>CTM</application> ©Î
+ <application>CVSup</application> ³£¥i¥H¡CHandbook ¤¤ªº "§ó·s¡B¤É¯Å 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»Ýn¼ô±x <application>CVS</application> ¥Îªk¡C
+ ¦p¦¹¤@¨Ó¡A§A¥i¥H¬d¾\¤£¦Pª©¥»¤§¶¡ªº®t²§³B¡C</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(©|¥¼¼¶½Z¡A¤´«Ý¸É¥R) -- ¼g¥÷¤W¤â»¡©ú(tutorial)¨Ó¤¶²Ð¦p¦ó¥H CVSup
+ ¨ú±o¤å¥ó³¡¤À¡A¥H¤Î¹î¬Ý¤£¦Pª©¥»¤§¶¡ªº®t²§¡C]</para>
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>How do I find out who else might be translating to the same
- language?</para>
+ <para>n«ç»ò§ä¥X¨ÓÁÙ¦³½Ön¸ò§Ú¤@°_½Ķªº©O¡H</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> ³o¦C¤F¥Ø«e¤wª¾ªº¦U½ĶªÌ¦¨ªG
+ ¡A¦pªG¤w¸g¦³¨ä¥L¤H¤]¦b°µ¸ò§A¤@¼ËªºÂ½Ä¶¤u§@¡A¨º»ò½Ð¤£n«½Æ®ö¶O¤H¤O¡A
+ ½Ð»P¥LÌÁpô¬Ý¬ÝÁÙ¦³þ¨Ç¦a¤è¥i¥HÀ°¤W¦£ªº¡C</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>Y¤W±¨Ã¥¼¦C¥X§A¥À»yªºÂ½Ä¶¡A©Î¬O¤]¦³¤Hn½Ķ¦ýÁÙ¥¼¤½¶}«Å¥¬ªº¸Ü¡A¨º»ò´N±H«H¨ì &a.doc; §a¡C
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>No one else is translating to my language. What do I do?</para>
+ <para>³£¨S¤H½Ķ¬°§Ú©Ò¨Ï¥Îªº»y¨¥¡A¸Ó«ç»ò¿ì¡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>®¥³ß°Ú¡A§Aè¦n½ñ¤W <quote>FreeBSD
+ <replaceable>§Aªº¥À»y</replaceable> ¤å¥ó½Ķp¹º</quote> ªº±Òµ{¤§¸ô¡AÅwªï¤W²î¡C</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>º¥ý©O¡A¥ý§PÂ_¬O§_¦³§´µ½³W¹º®É¶¡¡A¦]¬°§A¥u¦³¤@Ó¤H¦b½¦Ó¤w¡A
+ ¦]¦¹¡A¬ÛÃö½Ķ¦¨ªGªº¤½¥¬¡B»P¨ä¥L¥i¯à·|À°¦£ªº§Ó¤uÌÁpô³o¨Ç¤u§@³£¬O§AªºÂ¾³d©Ò¦b¡C</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>¼g«H¨ì &a.doc; ¦V¤j®a«Å¥¬§A¥¿·Ç³Æn½Ķ¡AµM«á¤å¥óp¹ºªºÂ½Ä¶³¡¤À´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>Y§Aªº°ê®a¤w¸g¦³¤H´£¨Ñ FreeBSD ªº mirror(¬M³]) ªA°Èªº¸Ü¡A¨º»ò´N¥ý¸ò¥LÌÁpô¡A
+ ¨Ã¸ß°Ý§A¬O§_¦b¤W±¥i¥H¦³ºô¶ªÅ¶¡¨Ó©ñ¬ÛÃöp¹º¸ê®Æ¡A
+ ¥H¤Î¬O§_¥i¥H¦³´£¨Ñ email ±b¸¹©Î mailing list ªA°È¡C</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>µM«á¡A´N¶}©l½¤å¥óÅo¡A¤@¶}©l½Ķªº®ÉÔ¡A¥ý§ä¨Ç½g´T¸ûµuªº¤å¥ó·|¤ñ¸û®e©ö¨Ç
+ — ¹³¬O FAQ °Õ¡A©Î¬O¦p¦ó¤W¤â¤§Ãþªº»¡©ú¤å³¹¡C</para>
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>I have translated some documentation, where do I send it?</para>
+ <para>¤w¸g½¦n¤@¨Ç¤å¥ó¤F¡A¸Ó±H¨ìþ©O¡H</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¦Ó©w¡C Y§A¬O¦b½Ķ¹Î¶¤¤º°µªº¸Ü(¹³¬O¤é¥»¡B¼w°ê)¡A
+ ¥LÌ·|¦³¦Û¤v¤º³¡¬yµ{¨Ó¨M©w½Ķ¤å¥ó«ç»ò°e¡A³o¨Ç¤jP¬yµ{·|¦b¥L̺ô¶¤W±¦³¼g¡C</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>Y§A¬O¬Y»y¨tªº°ß¤@½ĶªÌ(©Î§A¬Ot³d¬Y½Ķp¹º¡A¨Ã·Q§â¦¨ªG¦^õXµ¹ FreeBSD p¹º)
+ ¡A¨º»ò§A´NÀ³¸Ó§â¦Û¤vªºÂ½Ä¶¦¨ªG±Hµ¹ FreeBSD p¹º¡C(²Ó¸`½Ð¬Ý¤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¸Ó»y¨tªº°ß¤@½ĶªÌ¡A¸Ó«ç»ò§â½Ķ¦¨ªG±H¥X¥h©O¡H</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¸Ó«ç»ò§â§Ú̦¨û½Ķ¦¨ªG±H¥X¥h©O¡H</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½Ð¥ý½T©w§AªºÂ½Ä¶¦¨ªG²Õ´±ø²z¤À©ú¡A¨Ã¥i¥¿½T½sĶ¡A¤]´N¬O»¡¡G
+ §â¥¦Â\¨ì²{¦³¤å¥ó¬[ºc¤º¬O¥i¥H¥¿½T½sĶ¦¨¥\ªº¡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>¥Ø«e¡AFreeBSD ¤å¥ó³£¬O©ñ¦b³Ì¤W¼hªº <filename>doc/</filename> ¥Ø¿ý¤º¡C
+ ¦Ó¸Ó¥Ø¿ý¤Uªº«h¨Ì¨ä»y¨t¨Ó°µ¤ÀÃþ©R¦Wªº¡A¨Ì·Ó ISO639 ©w¸q(<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>Y§A³oÓ»y¨t¥i¯à·|¦³¤£¦P½s½X¤è¦¡(¹³¬O¡G¤¤¤å)
+ ¨º»ò´NÀ³¸Ó·|¹³¤U±³o¼Ë¡A¨Ó¨Ì§A©Ò¨Ï¥Îªº½s½X¤è¦¡²Ó¤À¡C</para>
- <para>Finally, you should have directories for each document.</para>
+ <para>³Ì«á¡A§AÀ³¸Ó«Ø¥ß¦n¦U¤å¥óªº¥Ø¿ý¤F¡C</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>»y¨t(lang)</replaceable>.<replaceable>½s½X(encoding)</replaceable></filename>
+ ªº³W«h¨Ó«Ø¥ßªºÄ¶¦W¡C
+ ½Ðª`·N¡G¨ä¤¤¦³¨âÓ <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> ©ñ¨ìºô¶ªÅ¶¡¤W¡AY§A¨S¦³¦Û¤vºô¶ªÅ¶¡ªº¸Ü(ISP¤£´£¨Ñ)
+ ¡A¨º»ò¥i¥H¸ÓÀɱH¨ì &a.doceng; ¨Ó¡C</para>
+
+ <para>ÁÙ¦³¡A°O±o¥Î &man.send-pr.1; ¥H¥¿¦¡³qª¾¤j®a¡F§A¤w¸g±H¥X½Ķ¤å¥ó¤F¡A
+ ÁÙ¦³¡AY¦³¤H¥i¥HÀ°¦£À˾\¡B½Æ¼f¤å¥óªº¸Ü¡A¹ï½Ķ«~½è¸û¦n¡A
+ ¦]¬°³o¤]¦³§U©ó´£¤É½Ķ«~½èªº¬yºZ«×¡C</para>
+
+ <para>³Ì«á¡A·|¦³¤H(¥i¯à¬O¤å¥óp¹ºÁ`ºÞ¡A©Î¬O &a.doceng; ¦¨û)
+ ·|À˾\§AªºÂ½Ä¶¤å¥ó¡A¨Ã½T»{¬O§_¥i¥¿±`½sĶ¡C¦¹¥~¡A¥LÌ·|¯S§Oª`·N¤U¦C´XÂI¡G</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§_¥i¥H¶¶§Q <command>make all</command> ½sĶ©O¡H</para>
</listitem>
<listitem>
- <para>Does <command>make install</command> work correctly?</para>
+ <para><command>make install</command> ¬O§_µ²ªG¦³¥¿½T¡H</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>Y¦³°ÝÃDªº¸Ü¡A¨º»òÀ˾\ªÌ·|¥mÀ{§A¡A¨ÓÅý³o¨Ç½Ķ¦¨ªG¥i¥H¥¿½T¨Ï¥Î¡C</para>
- <para>If there are no problems your translation will be committed
- as soon as possible.</para>
+ <para>Y¨S°ÝÃDªº¸Ü¡A¨º»ò´N·|«Ü§Ö§â§AªºÂ½Ä¶¦¨ªG commit ¶i¥h¤F¡C</para>
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>Can I include language or country specific text in my
- translation?</para>
+ <para>¥i¥H¥[¤J¬Y»y¨t©Î¬Y°ê®a¤~¦³ªºªF¦è¨ì½Ķ¤º®e¤º¶Ü¡H</para>
</question>
<answer>
- <para>We would prefer that you did not.</para>
+ <para>§Ú̧Ʊ椣n³o»ò°µ¡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
+ ¨Ã§Æ±æ§âÁú°ê¹s°â³B¤]¥[¨ì§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 …) 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>§ÚÌ·Q¤£¥X¨Ó¦³Ô£ì¦]¡A¬°¤°»ò¤£§â³o¨Ç¸ê°T´£¨Ñµ¹^¤åª©©O¡H(©Î¬O¼w¤å¡B¦è¯Z¤ú¤å¡B¤é¤åµ¥ …)
+ ¦]¬°¡A¦³¥i¯à^»yŪªÌ¶]¥hÁú°ê®É¡A·|·Q¶R FreeBSD ¬ÛÃö²£«~¡C
+ ¦¹¥~¡A³o¤]¥i¥H´£¤É FreeBSD ªº¥i¨£«×¡A«ÜÅãµMªº¡A³o¨Ã¤£¬O¥óÃa¨Æ°Ú¡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>Y§A¦³¬Y°ê¤~¦³ªº¸ê®Æ¡A½Ð(¥Î &man.send-pr.1; )´£¨Ñµ¹^¤åª© Handbook ¥H§@¬°×q
+ ¡AµM«á¦A§â^¤åª©ªº×q³¡¤À¡A½¬°§An½Ķªº Handbook §a¡C</para>
- <para>Thanks.</para>
+ <para>·P®¦¡AÁÂÁ¡C</para>
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>How should language specific characters be included?</para>
+ <para>n«ç»ò§â¸Ó»y¨t¯S¦³ªº¦r¤¸¼g¶i¥h½Ķ¤º®e©O¡H</para>
</question>
<answer>
- <para>Non-ASCII characters in the documentation should be included
- using SGML entities.</para>
+ <para>¤å¥ó¤º©Ò¦³ªº«D ASCII(Non-ASCII) ¦r¤¸¡A³£n¨Ï¥Î SGML entities ¤~¯à¼g¶i¥h¡C</para>
- <para>Briefly, these look like an ampersand (&), the name of the
- entity, and a semi-colon (;).</para>
+ <para>²³æ¨Ó»¡¡Aªø¬Û¤@¶}ÀY·|¬O & ²Å¸¹(&)¡AµM«á¬O¸Ó 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 ©Ò¨îqªº¡A¦Ó port tree ¤º«h¦b
+ <filename role="package">textproc/iso8879</filename>¡C</para>
- <para>A few examples include:</para>
+ <para>¥H¤UÁ|¤@¨Ç¨Ò¤l¡G</para>
<segmentedlist>
- <segtitle>Entity</segtitle>
+ <segtitle>Entity¦WºÙ</segtitle>
- <segtitle>Appearance</segtitle>
+ <segtitle>¹ê»Ú¼Ë¤l</segtitle>
- <segtitle>Description</segtitle>
+ <segtitle>¤¶²Ð</segtitle>
<seglistitem>
<seg>é</seg>
<seg>é</seg>
- <seg>Small <quote>e</quote> with an acute accent</seg>
+ <seg>¤p <quote>e</quote>¡A¨Ã±a¦y¡B«µ(acute accent)</seg>
</seglistitem>
<seglistitem>
<seg>É</seg>
<seg>É</seg>
- <seg>Large <quote>E</quote> with an acute accent</seg>
+ <seg>¤j <quote>E</quote>¡A¨Ã±a¦y¡B«µ(acute accent)</seg>
</seglistitem>
<seglistitem>
<seg>ü</seg>
<seg>ü</seg>
- <seg>Small <quote>u</quote> with an umlaut</seg>
+ <seg>¤p <quote>u</quote>¡A¨Ã±a¤é¦Õ°Ò»y¨t¤¤ªº¥ÀµÅܤÆ(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 ¤§«á¡A´N¥i¥H¦b
+ <filename>/usr/local/share/sgml/iso8879</filename> §ä¨ì³o¨Çªº¸Ô²Ó¦Cªí¡C</para>
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>Addressing the reader</para>
+ <para>¦p¦óºÙ©IŪªÌ©O¡H</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ŪªÌ³£¬O¥H <quote>you</quote> ¨ÓºÙ©I¡A¦Ó¦³¨Ç»y¨¥¨Ã¨S¦³¥¿¦¡/«D¥¿¦¡ªº°Ï¹j¡C</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>Y§A©Òn½ªº»y¨¥¥i¥H°Ï§O³o¨Ç®t²§¡A¨º»ò½Ð¥Î¸Ó»y¨t¦b¤@¯ë§Þ³N¤å¥ó¤W©Ò¨Ï¥ÎªººÙ©I§a¡C
+ ¦pªG®e©ö³y¦¨§x´bªº¸Ü¡A¨º»ò½Ð§ï¥Î¸û¤¤©ÊªººÙ©I¨Ó¨ú¥N¡C</para>
+
+ <!--
+ ºK¦Û http://fatpipi.cirx.org/~vanilla/rules.txt
+ ¦p«D¥²n¡A½Ķ¤å³¹¤ººÉ¶q¤Ö¥Îª½±µºÙ©I§A§Ú¥Lªº¥Î¦r¡C
+ ¦pªG¯uªº±o¥Î¡A´N±Ä¥Î²Ä¤T¤HºÙ(¥Î¡i¥L¡j¦Ó«D¡i§A¡j)¡AÁÙ¦³´N¬O¥Î½Æ¼Æ(¥Î¡i§AÌ¡j¦Ó«D¡i§A¡j)¡A
+ ·íµM³oÁÙ¬O±o°t¦Xì¤åªº¤W¤U»y·N¡C¦pªG¥L¬O¼g "I" ¦Ó½Ķ¦¨ "§Ú"¡A«hµL¥i«p«D¡C
+
+ ¦ý¬O¹ï©ó¤å¤ºµ´¤j¦h¼Æªº"You..... you ...etc"
+ ¨ä¹ê³£¥i¥H§â¡i§A¡j²¤Æ©Î¬OÁקK±¼¡A³o¹ï¾\Ū®ÉÔªº¶¶ºZ·PÀ³¸Ó¦³À°§U¡C
+ -->
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>Do I need to include any additional information in my
- translations?</para>
+ <para>½Ķ¦¨ªG¤ºn¤£nªþ¤W¤@¨Ç¨ä¥L°T®§©O¡H</para>
</question>
<answer>
- <para>Yes.</para>
+ <para>·íµMn¡C</para>
- <para>The header of the English version of each document will look
- something like this:</para>
+ <para>¨C¥÷^¤åª©ì½Zªº¶}ÀY¡A³q±`·|¦³¹³¤U±ªº¤º®e¡G</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>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>¹ê»Ú¤Wªº¤º®e¥i¯àµy¦³¤£¦P¡A¦ý¨C¥÷ì½Z³£·|ªþ¤W $FreeBSD$ ³o¤@¦æ¥H¤Î
+ <literal>The FreeBSD Documentation Project</literal> «Å§i¡C
+ ½Ðª`·N¡G$FreeBSD ¶}ÀYªº³o¦æ¬O·|¥Ñ CVS ÀHµÛ¨C¦¸²§°Ê¦Ó¦Û°Ê§ó§ïªº¡A
+ ©Ò¥H¡A·sÀɮתº¸Ü½Ð«O«ù쪬(¤]´N¬O¥un¼g <literal>$FreeBSD$</literal> ´N¦n¤F)¡C</para>
+
+ <para>½Ķ¤å¥ó¤¤¡A¥²¶·³£n¦³ $FreeBSD$ ³o¦æ¡A¨Ã¥B§â
+ <literal>FreeBSD Documentation Project</literal> ³o¦æ§ï¬°
+ <literal>The FreeBSD <replaceable>§Aªº»y¨t</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¦æ¨Ó«ü¥X§A©Ò½Ķªº¡A¨ì©³¬O¥H^¤åª©ì½Zªºþ¤@ª©¥»¬°¥À¥»©Ò°µªºÂ½Ä¶¡C</para>
- <para>So, the Spanish version of this file might start:</para>
+ <para>¦]¦¹©O¡A¦è¯Z¤ú¤åª©(Spanish)ªºÀɮ׶}ÀYÀ³¸Ó¬Oªø¹³³o¼Ë¡G</para>
<programlisting><!--
The FreeBSD Spanish Documentation Project
--- zh_TW.Big5.fdp-primer.translations.diff ends here ---
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-doc
mailing list