<para>It is <emphasis>very</emphasis> heavily based on the translation FAQ

  <para>¥»¤å¥ó <emphasis>¥D­n</emphasis> ¬O¥H FreeBSD ¼w¤å½Ķ­p¹ºªºÂ½Ä¶ FAQ ¬°¥À¥»¦Ó¨Óªº¡A

    from the FreeBSD German Documentation Project, originally written by Frank

    ­ì©l¼¶½ZªÌ¬° Frank Gr&uuml;nder <email>elwood@mc5sys.in-berlin.de</email> ¡A¨Ã¥Ñ 

    Gr&uuml;nder <email>elwood@mc5sys.in-berlin.de</email> and translated back to

    Bernd Warken <email>bwarken@mayn.de</email> ¦A½Ķ¦^­^¤åª©¡C</para>

    English by Bernd Warken <email>bwarken@mayn.de</email>.</para>

	<para>What do <phrase>i18n</phrase> and <phrase>l10n</phrase>

	<para><phrase>i18n</phrase> ¸ò <phrase>l10n</phrase> ¬O¤°»ò©O¡H</para>

	  mean?</para>

	<para><phrase>i18n</phrase> means

	<para><phrase>i18n</phrase> ¬O

	  <phrase>internationalization</phrase> and <phrase>l10n</phrase>

	  <phrase>internationalization</phrase> ªºÂ²¼g¡A¦Ó <phrase>l10n</phrase>

	  means <phrase>localization</phrase>. They are just a convenient

	  «h¬O <phrase>localization</phrase> ªºÂ²¼g¡C³o¨Ç³£¬O¬°¤F®Ñ¼g¤è«K¦Ó¥ÎªºÂ²¼g¡C</para>

	  shorthand.</para>

	<para><phrase>i18n</phrase> can be read as <quote>i</quote> followed by

	<para><phrase>i18n</phrase> ´N¬O¶}ÀY¬° <quote>i</quote> «á­±¦³ 18 ­Ó¦r¥À¡A³Ì«á±µ <quote>n</quote>¡C

	  18 letters, followed by <quote>n</quote>. Similarly,

	  ¦P²z¡A

	  <phrase>l10n</phrase> is <quote>l</quote> followed by 10 letters,

	  <phrase>l10n</phrase> «h¬O¶}ÀY¬° <quote>l</quote> «á­±¦³ 10 ­Ó¦r¥À¡A³Ì«á±µ <quote>n</quote>¡C</para>

	  followed by <quote>n</quote>.</para>

	<para>Is there a mailing list for translators?</para>

	<para>¦³±Mªùµ¹Ä¶ªÌ°Ñ»P°Q½×ªº mailing list ¶Ü¡H</para>

	<para>Yes.  Different translation groups have their own mailing

	<para>¦³°Ú¡A¤£¦Pªº»y¨t½ĶªÌ³£¦U¦Û¦³¦ÛÄݪº mailing lists¡C³o¥÷ <ulink 

          lists.  The <ulink url="http://www.freebsd.org/docproj/translations.html">list

	  url="http://www.freebsd.org/docproj/translations.html">½Ķ­p¹º²M³æ</ulink> 

            of translation projects</ulink> has more information about the

	  ¦³¦C¥X¦U½Ķ­p¹ºªº¸Ô²Ó mailing lists ¤Î¬ÛÃöºô¯¸¡C</para>

          mailing lists and web sites run by each translation project.</para>

	<para>Are more translators needed?</para>

	<para>»Ý­n§ó¦h¤H¤@°_°Ñ»P½Ķ¶Ü¡H</para>

	<para>Yes. The more people work on translation the faster it gets

	<para>·íµMÅo¡A¶V¦h¤H°Ñ»P½Ķ¡A¨º»ò´N¯à°÷¶V§Ö½§¹¡A¦Ó¥B­^¤åª©¤å¥ó­Y¦³¼W´î¡B§ó·sªº¸Ü¡A

	  done, and the faster changes to the English documentation are

	  ¦U½Ķª©¤]¥i¥H¾¨§Ö¦P¨BÅo¡C</para>

	  mirrored in the translated documents.</para>

	<para>You do not have to be a professional translator to be able to

	<para>¤£¤@©w±o¬O±M·~ĶªÌ¡A¤~¯à°Ñ»P½Ķªº¡C</para>

	  help.</para>

	<para>What languages do I need to know?</para>

	<para>¦³­n¨D­þ¨Ç»y¨¥¯à¤O©O¡H</para>

	<para>Ideally, you will have a good knowledge of written English, and

	<para>²z½×¤W¡A¥²¶·­n¹ï­^¤å«D±`¼ô¸Z¡A¦Ó¥B«Ü©úÅã¦a¡A¹ï·Q½Ķªº»y¨¥¥²¶·­n¯à¹B¥Î¦Û¦p¡C</para>

	  obviously you will need to be fluent in the language you are

	  translating to.</para>

	<para>English is not strictly necessary. For example, you could do a

	<para>­^¤å¨Ã«D¤@©w­n·|ªº¡C¤ñ¦p»¡¡A¥i¥H§â¦è¯Z¤ú¤å(Spanish)ªº FAQ ½Ķ¬°¦I¤ú§Q¤å(Hungarian)¡C</para>

	  Hungarian translation of the FAQ from the Spanish

	  translation.</para>

	<para>What software do I need to know?</para>

	<para>¸Ó¾Ç·|­þ¨Çµ{¦¡ªº¨Ï¥Î©O¡H</para>

	<para>It is strongly recommended that you maintain a local copy of the

	<para>±j¯P«Øij¦b¦Û¤v¾÷¾¹¤W¤]«Ø¥ß FreeBSD CVS repository ªº³Æ¥÷(¦Ü¤Ö¤å¥ó³¡¤À)¡A¥i¥H¥Î

	  FreeBSD CVS repository (at least the documentation part) either

	  <application>CTM</application> ©Î

	  using <application>CTM</application> or

	  <application>CVSup</application> ³£¥i¥H¡CHandbook ¤¤ªº "§ó·s¡B¤É¯Å FreeBSD" 

	  <application>CVSup</application>. The "Staying current with FreeBSD"

	  ¤@³¹¤º¦³´£¨ì¦p¦ó¨Ï¥Î³o¨Çµ{¦¡¡C</para>

	  chapter in the Handbook explains how to use these

	  applications.</para>

	<para>You should be comfortable using <application>CVS</application>.

	<para>¦¹¥~¡A»Ý­n¼ô±x <application>CVS</application> ¥Îªk¡C

	  This will allow you to see what has changed between different

	  ¦p¦¹¤@¨Ó¡A§A¥i¥H¬d¾\¤£¦Pª©¥»¤§¶¡ªº®t²§³B¡C</para>

	  versions of the files that make up the documentation.</para>

	<para>[XXX To Do -- write a tutorial that shows how to use CVSup to

	<para>[XXX To Do(©|¥¼¼¶½Z¡A¤´«Ý¸É¥R) -- ¼g¥÷¤W¤â»¡©ú(tutorial)¨Ó¤¶²Ð¦p¦ó¥H CVSup 

	  get just the documentation, check it out, and see what has changed

	  ¨ú±o¤å¥ó³¡¤À¡A¥H¤Î¹î¬Ý¤£¦Pª©¥»¤§¶¡ªº®t²§¡C]</para>

	  between two arbitrary revisions]</para>

	<para>How do I find out who else might be translating to the same

	<para>­n«ç»ò§ä¥X¨ÓÁÙ¦³½Ö­n¸ò§Ú¤@°_½Ķªº©O¡H</para>

	  language?</para>

	<para>The <ulink

	<para><ulink

	    url="http://www.FreeBSD.org/docproj/translations.html">Documentation

	    url="http://www.FreeBSD.org/docproj/translations.html">¤å¥ó­p¹ºªºÂ½Ä¶</ulink> ³o¦C¤F¥Ø«e¤wª¾ªº¦U½ĶªÌ¦¨ªG

	    Project translations page</ulink> lists the translation efforts

	    ¡A¦pªG¤w¸g¦³¨ä¥L¤H¤]¦b°µ¸ò§A¤@¼ËªºÂ½Ä¶¤u§@¡A¨º»ò½Ð¤£­n­«½Æ®ö¶O¤H¤O¡A

	  that are currently known about. If others are already working

	    ½Ð»P¥L­ÌÁpô¬Ý¬ÝÁÙ¦³­þ¨Ç¦a¤è¥i¥HÀ°¤W¦£ªº¡C</para>

	  on translating documentation to your language, please do not

	  duplicate their efforts. Instead, contact them to see how you can

	  help.</para>

	<para>If no one is listed on that page as translating for your

	<para>­Y¤W­±¨Ã¥¼¦C¥X§A¥À»yªºÂ½Ä¶¡A©Î¬O¤]¦³¤H­n½Ķ¦ýÁÙ¥¼¤½¶}«Å¥¬ªº¸Ü¡A¨º»ò´N±H«H¨ì &a.doc; §a¡C

	  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>No one else is translating to my language.  What do I do?</para>

	<para>³£¨S¤H½Ķ¬°§Ú©Ò¨Ï¥Îªº»y¨¥¡A¸Ó«ç»ò¿ì¡H</para>

	<para>Congratulations, you have just started the <quote>FreeBSD

	<para>®¥³ß°Ú¡A§A­è¦n½ñ¤W <quote>FreeBSD

	  <replaceable>your-language-here</replaceable> Documentation

	  <replaceable>§Aªº¥À»y</replaceable> ¤å¥ó½Ķ­p¹º</quote> ªº±Òµ{¤§¸ô¡AÅwªï¤W²î¡C</para>

          Translation Project</quote>. Welcome aboard.</para>

	<para>First, decide whether or not you have got the time to spare. Since

	<para>­º¥ý©O¡A¥ý§PÂ_¬O§_¦³§´µ½³W¹º®É¶¡¡A¦]¬°§A¥u¦³¤@­Ó¤H¦b½¦Ó¤w¡A

	  you are the only person working on your language at the moment it is

	  ¦]¦¹¡A¬ÛÃö½Ķ¦¨ªGªº¤½¥¬¡B»P¨ä¥L¥i¯à·|À°¦£ªº§Ó¤u­ÌÁpô³o¨Ç¤u§@³£¬O§AªºÂ¾³d©Ò¦b¡C</para>

	  going to be your responsibility to publicize your work and

	  coordinate any volunteers that might want to help you.</para>

	<para>Write an email to the Documentation Project mailing list,

	<para>¼g«H¨ì &a.doc; ¦V¤j®a«Å¥¬§A¥¿·Ç³Æ­n½Ķ¡AµM«á¤å¥ó­p¹ºªºÂ½Ä¶³¡¤À´N·|§ó·s¬ÛÃö¸ê®Æ</para>

	  announcing that you are going to translate the documentation, so the

	  Documentation Project translations page can be maintained.</para>

	<para>If there is already someone in your country providing FreeBSD

	<para>­Y§Aªº°ê®a¤w¸g¦³¤H´£¨Ñ FreeBSD ªº mirror(¬M³]) ªA°Èªº¸Ü¡A¨º»ò´N¥ý¸ò¥L­ÌÁpô¡A

	  mirroring services you should contact them and ask if you can

	  ¨Ã¸ß°Ý§A¬O§_¦b¤W­±¥i¥H¦³ºô­¶ªÅ¶¡¨Ó©ñ¬ÛÃö­p¹º¸ê®Æ¡A

	  have some webspace for your project, and possibly an email

	  ¥H¤Î¬O§_¥i¥H¦³´£¨Ñ email ±b¸¹©Î mailing list ªA°È¡C</para>

	  address or mailing list services.</para>

	<para>Then pick a document and start translating. It is best to start

	<para>µM«á¡A´N¶}©l½¤å¥óÅo¡A¤@¶}©l½Ķªº®É­Ô¡A¥ý§ä¨Ç½g´T¸ûµuªº¤å¥ó·|¤ñ¸û®e©ö¨Ç 

	  with something fairly small—either the FAQ, or one of the

	  &mdash; ¹³¬O FAQ °Õ¡A©Î¬O¦p¦ó¤W¤â¤§Ãþªº»¡©ú¤å³¹¡C</para>

	  tutorials.</para>

	<para>I have translated some documentation, where do I send it?</para>

	<para>¤w¸g½¦n¤@¨Ç¤å¥ó¤F¡A¸Ó±H¨ì­þ©O¡H</para>

	<para>That depends. If you are already working with a translation team

	<para>³o­n¬Ý±¡ªp¦Ó©w¡C ­Y§A¬O¦b½Ķ¹Î¶¤¤º°µªº¸Ü(¹³¬O¤é¥»¡B¼w°ê)¡A

	  (such as the Japanese team, or the German team) then they will have

	  ¥L­Ì·|¦³¦Û¤v¤º³¡¬yµ{¨Ó¨M©w½Ķ¤å¥ó«ç»ò°e¡A³o¨Ç¤j­P¬yµ{·|¦b¥L­Ìºô­¶¤W­±¦³¼g¡C</para>

	  their own procedures for handling submitted documentation, and these

	  will be outlined on their web pages.</para>

	<para>If you are the only person working on a particular language (or

	<para>­Y§A¬O¬Y»y¨tªº°ß¤@½ĶªÌ(©Î§A¬O­t³d¬Y½Ķ­p¹º¡A¨Ã·Q§â¦¨ªG¦^õXµ¹ FreeBSD ­p¹º)

	  you are responsible for a translation project and want to submit

	  ¡A¨º»ò§A´NÀ³¸Ó§â¦Û¤vªºÂ½Ä¶¦¨ªG±Hµ¹ FreeBSD ­p¹º¡C(²Ó¸`½Ð¬Ý¤U­Ó°ÝÃD)</para>

	  your changes back to the FreeBSD project) then you should send your

	  translation to the FreeBSD project (see the next question).</para>

	<para>I am the only person working on translating to this language, how

	<para>§Ú¬O¸Ó»y¨tªº°ß¤@½ĶªÌ¡A¸Ó«ç»ò§â½Ķ¦¨ªG±H¥X¥h©O¡H</para>

	  do I submit my translation?</para>

	<para>or</para>

	<para>©ÎªÌ</para>

	<para>We are a translation team, and want to submit documentation that

	<para>§Ú­Ì¬O½Ķ¹Î¶¤¡A¸Ó«ç»ò§â§Ú­Ì¦¨­û½Ķ¦¨ªG±H¥X¥h©O¡H</para>

	  our members have translated for us?</para>

	<para>First, make sure your translation is organized properly. This

	<para>­º¥ý¡A½Ð¥ý½T©w§AªºÂ½Ä¶¦¨ªG²Õ´±ø²z¤À©ú¡A¨Ã¥i¥¿½T½sĶ¡A¤]´N¬O»¡¡G

	  means that it should drop into the existing documentation tree and

	  §â¥¦Â\¨ì²{¦³¤å¥ó¬[ºc¤º¬O¥i¥H¥¿½T½sĶ¦¨¥\ªº¡C</para>

	  build straight away.</para>

	<para>Currently, the FreeBSD documentation is stored in a top level

	<para>¥Ø«e¡AFreeBSD ¤å¥ó³£¬O©ñ¦b³Ì¤W¼hªº <filename>doc/</filename> ¥Ø¿ý¤º¡C

	  directory called <filename>doc/</filename>. Directories below this

	  ¦Ó¸Ó¥Ø¿ý¤Uªº«h¨Ì¨ä»y¨t¨Ó°µ¤ÀÃþ©R¦Wªº¡A¨Ì·Ó ISO639 ©w¸q(<filename>/usr/share/misc/iso639</filename> 

	  are named according to the language code they are written in, as

	  ªº³o­Ó FreeBSD ª©¥»¤ñ 1999/01/20 ÁÙ·s)¡C</para>

	  defined in ISO639 (<filename>/usr/share/misc/iso639</filename> on a

	  version of FreeBSD newer than 20th January 1999).</para>

	<para>If your language can be encoded in different ways (for example,

	<para>­Y§A³o­Ó»y¨t¥i¯à·|¦³¤£¦P½s½X¤è¦¡(¹³¬O¡G¤¤¤å)

	  Chinese) then there should be directories below this, one for each

	  ¨º»ò´NÀ³¸Ó·|¹³¤U­±³o¼Ë¡A¨Ó¨Ì§A©Ò¨Ï¥Îªº½s½X¤è¦¡²Ó¤À¡C</para>

	  encoding format you have provided.</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

	<para>Á|¨Ò¨Ó»¡¡A°²³]¦³·ç¨å¤å(Swedish)ª©ªºÂ½Ä¶¡A¨º»òÀ³¸Ó·|ªø¹³¡G</para>

	  like:</para>

	<para><literal>sv_SE.ISO8859-1</literal> is the name of the

	<para><literal>sv_SE.ISO8859-1</literal> ¬O¨Ì·Ó 

	  translation, in

	  <filename><replaceable>»y¨t(lang)</replaceable>.<replaceable>½s½X(encoding)</replaceable></filename>

	  <filename><replaceable>lang</replaceable>.<replaceable>encoding</replaceable></filename>

	  ªº³W«h¨Ó«Ø¥ßªºÄ¶¦W¡C

	  form.  Note the

	  ½Ðª`·N¡G¨ä¤¤¦³¨â­Ó <filename>Makefiles</filename> ÀÉ¡A¥¦­Ì¬O¥Î¨Ó½s®Ñªº¡C</para>

	  two Makefiles, which will be used to build the documentation.</para>

	<para>Use &man.tar.1; and &man.gzip.1; to compress up your

	<para>µM«á½Ð¥Î &man.tar.1; »P &man.gzip.1; ¨Ó§â§AªºÂ½Ä¶¤å¥óÀ£ÁY°_¨Ó¡A¨Ã±H¨ì¥»­p¹º¨Ó¡C</para>

	  documentation, and send it to the project.</para>

&prompt.user; <userinput>tar cf swedish-docs.tar sv</userinput>

&prompt.user; <userinput>tar cf swedish-docs.tar sv_SE.ISO8859-1</userinput>

	<para>Put <filename>swedish-docs.tar.gz</filename> somewhere.  If you

	<para>±µµÛ¡A§â <filename>swedish-docs.tar.gz</filename> ©ñ¨ìºô­¶ªÅ¶¡¤W¡A­Y§A¨S¦³¦Û¤vºô­¶ªÅ¶¡ªº¸Ü(ISP¤£´£¨Ñ)

	  do not have access to your own webspace (perhaps your ISP does not

	  ¡A¨º»ò¥i¥H¸ÓÀɱH¨ì &a.doceng; ¨Ó¡C</para>

	  let you have any) then you can email &a.doceng;, and arrange to email

	  the files when it is convenient.</para>

	<para>ÁÙ¦³¡A°O±o¥Î &man.send-pr.1; ¥H¥¿¦¡³qª¾¤j®a¡F§A¤w¸g±H¥X½Ķ¤å¥ó¤F¡A

	  ÁÙ¦³¡A­Y¦³¤H¥i¥HÀ°¦£À˾\¡B½Æ¼f¤å¥óªº¸Ü¡A¹ï½Ķ«~½è¸û¦n¡A

	<para>Either way, you should use &man.send-pr.1; to submit a report

	  ¦]¬°³o¤]¦³§U©ó´£¤É½Ķ«~½èªº¬yºZ«×¡C</para>

	  indicating that you have submitted the documentation. It would be

	  very helpful if you could get other people to look over your

	<para>³Ì«á¡A·|¦³¤H(¥i¯à¬O¤å¥ó­p¹ºÁ`ºÞ¡A©Î¬O &a.doceng; ¦¨­û)

	  translation and double check it first, since it is unlikely that the

	  ·|À˾\§AªºÂ½Ä¶¤å¥ó¡A¨Ã½T»{¬O§_¥i¥¿±`½sĶ¡C¦¹¥~¡A¥L­Ì·|¯S§Oª`·N¤U¦C´XÂI¡G</para>

	  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>Do all your files use RCS strings (such as "ID")?</para>

	    <para>§AªºÀɮ׬O§_³£¦³¥Î RCS tag (¹³¬O "ID" ¤§Ãþªº)¡H</para>

	    <para>Does <command>make all</command> in the

	    <para><filename>sv_SE.ISO8859-1</filename> ¬O§_¥i¥H¶¶§Q <command>make all</command> ½sĶ©O¡H</para>

	      <filename>sv_SE.ISO8859-1</filename> directory work correctly?</para>

	    <para>Does <command>make install</command> work correctly?</para>

	    <para><command>make install</command> ¬O§_µ²ªG¦³¥¿½T¡H</para>

	<para>If there are any problems then whoever is looking at the

	<para>­Y¦³°ÝÃDªº¸Ü¡A¨º»òÀ˾\ªÌ·|¥mÀ{§A¡A¨ÓÅý³o¨Ç½Ķ¦¨ªG¥i¥H¥¿½T¨Ï¥Î¡C</para>

	  submission will get back to you to work them out.</para>

	<para>If there are no problems your translation will be committed

	<para>­Y¨S°ÝÃDªº¸Ü¡A¨º»ò´N·|«Ü§Ö§â§AªºÂ½Ä¶¦¨ªG commit ¶i¥h¤F¡C</para>

	  as soon as possible.</para>

	<para>Can I include language or country specific text in my

	<para>¥i¥H¥[¤J¬Y»y¨t©Î¬Y°ê®a¤~¦³ªºªF¦è¨ì½Ķ¤º®e¤º¶Ü¡H</para>

	  translation?</para>

	<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

	<para>Á|¨Ò¨Ó»¡¡A°²³]§A¥¿·Ç³Æ§â Handbook ½Ķ¬°Áú¤åª©¡A

	  Korean, and want to include a section about retailers in Korea in

	  ¨Ã§Æ±æ§âÁú°ê¹s°â³B¤]¥[¨ì§A½Ķªº Handbook Áú¤åª©¤º¡C</para>

	  your Handbook.</para>

	<para>There is no real reason why that information should not be in the

	<para>§Ú­Ì·Q¤£¥X¨Ó¦³Ô£­ì¦]¡A¬°¤°»ò¤£§â³o¨Ç¸ê°T´£¨Ñµ¹­^¤åª©©O¡H(©Î¬O¼w¤å¡B¦è¯Z¤ú¤å¡B¤é¤åµ¥ &hellip;)

	  English (or German, or Spanish, or Japanese, or …) versions

	  ¦]¬°¡A¦³¥i¯à­^»yŪªÌ¶]¥hÁú°ê®É¡A·|·Q¶R FreeBSD ¬ÛÃö²£«~¡C

	  as well. It is feasible that an English speaker in Korea might try

	  ¦¹¥~¡A³o¤]¥i¥H´£¤É FreeBSD ªº¥i¨£«×¡A«ÜÅãµMªº¡A³o¨Ã¤£¬O¥óÃa¨Æ°Ú¡C</para>

	  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>If you have country specific information, please submit it as a

	<para>­Y§A¦³¬Y°ê¤~¦³ªº¸ê®Æ¡A½Ð(¥Î &man.send-pr.1; )´£¨Ñµ¹­^¤åª© Handbook ¥H§@¬°­×­q

	  change to the English Handbook (using &man.send-pr.1;) and then

	  ¡AµM«á¦A§â­^¤åª©ªº­×­q³¡¤À¡A½¬°§A­n½Ķªº Handbook §a¡C</para>

	  translate the change back to your language in the translated

	  Handbook.</para>

	<para>Thanks.</para>

	<para>·P®¦¡AÁÂÁ¡C</para>

	<para>How should language specific characters be included?</para>

	<para>­n«ç»ò§â¸Ó»y¨t¯S¦³ªº¦r¤¸¼g¶i¥h½Ķ¤º®e©O¡H</para>

	<para>Non-ASCII characters in the documentation should be included

	<para>¤å¥ó¤º©Ò¦³ªº«D ASCII(Non-ASCII) ¦r¤¸¡A³£­n¨Ï¥Î SGML entities ¤~¯à¼g¶i¥h¡C</para>

	  using SGML entities.</para>

	<para>Briefly, these look like an ampersand (&amp;), the name of the

	<para>²³æ¨Ó»¡¡Aªø¬Û¤@¶}ÀY·|¬O &amp; ²Å¸¹(&amp;)¡AµM«á¬O¸Ó entity ¦WºÙ¡A³Ì«á±µ¤W¤À¸¹(;)¡C</para>

	  entity, and a semi-colon (;).</para>

	<para>The entity names are defined in ISO8879, which is in the ports

	<para>³o¨Ç entity ¦WºÙ³£¬O ISO8879 ©Ò¨î­qªº¡A¦Ó port tree ¤º«h¦b 

	  tree as <filename role="package">textproc/iso8879</filename>.</para>

	  <filename role="package">textproc/iso8879</filename>¡C</para>

	<para>A few examples include:</para>

	<para>¥H¤UÁ|¤@¨Ç¨Ò¤l¡G</para>

          <segtitle>Entity</segtitle>

          <segtitle>Entity¦WºÙ</segtitle>

          <segtitle>Appearance</segtitle>

          <segtitle>¹ê»Ú¼Ë¤l</segtitle>

          <segtitle>Description</segtitle>

          <segtitle>¤¶²Ð</segtitle>

	    <seg>Small <quote>e</quote> with an acute accent</seg>

	    <seg>¤p <quote>e</quote>¡A¨Ã±a¦y¡B­«­µ(acute accent)</seg>

	    <seg>Large <quote>E</quote> with an acute accent</seg>

	    <seg>¤j <quote>E</quote>¡A¨Ã±a¦y¡B­«­µ(acute accent)</seg>

	    <seg>Small <quote>u</quote> with an umlaut</seg>

	    <seg>¤p <quote>u</quote>¡A¨Ã±a¤é¦Õ°Ò»y¨t¤¤ªº¥À­µÅܤÆ(umlaut)</seg>

	<para>After you have installed the iso8879 port, the files in

	<para>¦b¸Ë¤F iso8879 ³o­Ó port ¤§«á¡A´N¥i¥H¦b

	  <filename>/usr/local/share/sgml/iso8879</filename> contain the

	  <filename>/usr/local/share/sgml/iso8879</filename> §ä¨ì³o¨Çªº¸Ô²Ó¦Cªí¡C</para>

	  complete list.</para>

	<para>Addressing the reader</para>

	<para>¦p¦óºÙ©IŪªÌ©O¡H</para>

	<para>In the English documents, the reader is addressed as

	<para>¦b­^¤å¤å¥ó¤º¡AŪªÌ³£¬O¥H <quote>you</quote> ¨ÓºÙ©I¡A¦Ó¦³¨Ç»y¨¥¨Ã¨S¦³¥¿¦¡/«D¥¿¦¡ªº°Ï¹j¡C</para>

	  <quote>you</quote>, there is no formal/informal distinction as there

	  is in some languages.</para>

	<para>If you are translating to a language which does distinguish, use

	<para>­Y§A©Ò­n½ªº»y¨¥¥i¥H°Ï§O³o¨Ç®t²§¡A¨º»ò½Ð¥Î¸Ó»y¨t¦b¤@¯ë§Þ³N¤å¥ó¤W©Ò¨Ï¥ÎªººÙ©I§a¡C

	  whichever form is typically used in other technical documentation in

	  ¦pªG®e©ö³y¦¨§x´bªº¸Ü¡A¨º»ò½Ð§ï¥Î¸û¤¤©ÊªººÙ©I¨Ó¨ú¥N¡C</para>

	  your language. If in doubt, use a mildly polite form.</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

	-->

	<para>Do I need to include any additional information in my

	<para>½Ķ¦¨ªG¤º­n¤£­nªþ¤W¤@¨Ç¨ä¥L°T®§©O¡H</para>

	  translations?</para>

	<para>Yes.</para>

	<para>·íµM­n¡C</para>

	<para>The header of the English version of each document will look

	<para>¨C¥÷­^¤åª©­ì½Zªº¶}ÀY¡A³q±`·|¦³¹³¤U­±ªº¤º®e¡G</para>

	  something like this:</para>

	<para>The exact boilerplate may change, but it will always include a

	<para>¹ê»Ú¤Wªº¤º®e¥i¯àµy¦³¤£¦P¡A¦ý¨C¥÷­ì½Z³£·|ªþ¤W &dollar;FreeBSD&dollar; ³o¤@¦æ¥H¤Î 

	  &dollar;FreeBSD&dollar; line and the phrase <literal>The FreeBSD Documentation

	  <literal>The FreeBSD Documentation Project</literal> «Å§i¡C

	    Project</literal>.

	  ½Ðª`·N¡G$FreeBSD ¶}ÀYªº³o¦æ¬O·|¥Ñ CVS ÀHµÛ¨C¦¸²§°Ê¦Ó¦Û°Ê§ó§ïªº¡A

	  Note that the $FreeBSD part is expanded automatically by

	  ©Ò¥H¡A·sÀɮתº¸Ü½Ð«O«ù­ìª¬(¤]´N¬O¥u­n¼g  <literal>&dollar;FreeBSD&dollar;</literal> ´N¦n¤F)¡C</para>

	  CVS, so it should be empty (just

	  <literal>&dollar;FreeBSD&dollar;</literal>) for new files.</para>

	<para>½Ķ¤å¥ó¤¤¡A¥²¶·³£­n¦³ &dollar;FreeBSD&dollar; ³o¦æ¡A¨Ã¥B§â

	  <literal>FreeBSD Documentation Project</literal> ³o¦æ§ï¬°

	<para>Your translated documents should include their own

	  <literal>The FreeBSD <replaceable>§Aªº»y¨t</replaceable>

	  $FreeBSD$ line, and change the

	    Documentation Project</literal>¡C</para>

	  <literal>FreeBSD Documentation Project</literal> line to

	  <literal>The FreeBSD <replaceable>language</replaceable>

	    Documentation Project</literal>.</para>

	<para>In addition, you should add a third line which indicates which

	<para>¦¹¥~¡AÁÙ¥²¶·¥[¤W²Ä¤T¦æ¨Ó«ü¥X§A©Ò½Ķªº¡A¨ì©³¬O¥H­^¤åª©­ì½Zªº­þ¤@ª©¥»¬°¥À¥»©Ò°µªºÂ½Ä¶¡C</para>

	  revision of the English text this is based on.</para>

	<para>So, the Spanish version of this file might start:</para>

	<para>¦]¦¹©O¡A¦è¯Z¤ú¤åª©(Spanish)ªºÀɮ׶}ÀYÀ³¸Ó¬Oªø¹³³o¼Ë¡G</para>