Index: zh_TW.UTF-8/books/fdp-primer/zh_TW.po =================================================================== --- zh_TW.UTF-8/books/fdp-primer/zh_TW.po +++ zh_TW.UTF-8/books/fdp-primer/zh_TW.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: \n" "POT-Creation-Date: 2016-06-06 18:36+0800\n" -"PO-Revision-Date: 2016-06-17 00:44+0800\n" +"PO-Revision-Date: 2016-06-30 06:13+0800\n" "Last-Translator: raycherng <>\n" "Language-Team: Chinese \n" "Language: zh_TW\n" @@ -68,8 +68,8 @@ #. (itstool) path: important/para #: book.translate.xml:119 msgid "" -"THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD DOCUMENTATION PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT " -"LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE." +"THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD DOCUMENTATION PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE " +"GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE." msgstr "" #. (itstool) path: abstract/para @@ -414,8 +414,8 @@ #. (itstool) path: sect1/para #: book.translate.xml:451 msgid "" -"Some preparatory steps must be taken before editing the FreeBSD documentation. First, subscribe to the FreeBSD documentation project mailing list. Some team members also interact on the #bsddocs IRC channel on EFnet. These people can help " -"with questions or problems involving the documentation." +"Some preparatory steps must be taken before editing the FreeBSD documentation. First, subscribe to the FreeBSD documentation project mailing list. Some team members also interact on the #bsddocs IRC channel on EFnet. These people can help with questions or problems involving the " +"documentation." msgstr "在編輯 FreeBSD 文件之前，有一些準備工作要做。 首先，請訂閱 FreeBSD 文件計劃郵件論壇。 有些團隊成員也會出現在EFnet的#bsddocs IRC 頻道。這些人可以幫忙解決文件相關的問題。" #. (itstool) path: step/para @@ -525,8 +525,8 @@ #. (itstool) path: step/para #: book.translate.xml:550 msgid "" -"Submit the diff file using the web-based Problem Report system. If using the web form, enter a synopsis of [patch] short description of problem. Select the category docs and the class doc-bug. In the body of the message, enter a short description of the changes " -"and any important details about them. Use the [ Browse... ] button to attach the diff file." +"Submit the diff file using the web-based Problem Report system. If using the web form, enter a synopsis of [patch] short description of problem. Select the category docs and the class doc-bug. In the body of the message, enter a short description of the changes and any important details about " +"them. Use the [ Browse... ] button to attach the diff file." msgstr "使用網頁版 Problem Report 系統提交 diff 檔。 如果使用網頁版，請輸入[修正檔] 問題簡短描述的概要 。選擇 docs 分類和 doc-bug類別。在訊息的主體中，輸入修正的簡短描述和其他相關的重要的細節。使用[ Browse... ] 按鈕來附加 diff 檔。" #. (itstool) path: chapter/title @@ -652,8 +652,7 @@ #. (itstool) path: sect1/para #: book.translate.xml:760 msgid "" -"FreeBSD documentation is not just books and articles. Manual pages for all the commands and configuration files are also part of the documentation, and part of the FDP's territory. Two repositories are involved: doc for the books and articles, and base for the operating system and manual pages. To edit manual pages, the base " -"repository must be checked out separately." +"FreeBSD documentation is not just books and articles. Manual pages for all the commands and configuration files are also part of the documentation, and part of the FDP's territory. Two repositories are involved: doc for the books and articles, and base for the operating system and manual pages. To edit manual pages, the base repository must be checked out separately." msgstr "" #. (itstool) path: sect1/para @@ -669,8 +668,8 @@ #. (itstool) path: sect1/para #: book.translate.xml:777 msgid "" -"FreeBSD documentation is traditionally stored in /usr/doc/, and system source code with manual pages in /usr/src/. These directory trees are relocatable, and users may want to put the working copies in other locations to avoid interfering with existing information in the main directories. The examples that follow use ~/doc and ~/src, both subdirectories of the user's home directory." +"FreeBSD documentation is traditionally stored in /usr/doc/, and system source code with manual pages in /usr/src/. These directory trees are relocatable, and users may want to put the working copies in other locations to avoid interfering with existing information in the main directories. The examples that follow use ~/doc and ~/src, both subdirectories of the " +"user's home directory." msgstr "" #. (itstool) path: sect1/title @@ -701,9 +700,7 @@ #. (itstool) path: sect1/para #: book.translate.xml:809 -msgid "" -"The documents and files in the FreeBSD repository change daily. People modify files and commit changes frequently. Even a short time after an initial checkout, there will already be differences between the local working copy and the main FreeBSD repository. To update the local version with the changes that have been made to the main repository, use svn update on the directory containing the " -"local working copy:" +msgid "The documents and files in the FreeBSD repository change daily. People modify files and commit changes frequently. Even a short time after an initial checkout, there will already be differences between the local working copy and the main FreeBSD repository. To update the local version with the changes that have been made to the main repository, use svn update on the directory containing the local working copy:" msgstr "" #. (itstool) path: sect1/screen @@ -842,8 +839,8 @@ #. (itstool) path: row/entry #: book.translate.xml:971 msgid "" -"Contains files that are not specific to the various translations and encodings of the documentation. Contains subdirectories to further categorize the information. For example, the files that comprise the make1 infrastructure are in share/mk, while the additional XML support files (such " -"as the FreeBSD extended DocBook DTD) are in share/xml." +"Contains files that are not specific to the various translations and encodings of the documentation. Contains subdirectories to further categorize the information. For example, the files that comprise the make1 infrastructure are in share/mk, while the additional XML support files (such as the FreeBSD extended DocBook " +"DTD) are in share/xml." msgstr "" #. (itstool) path: row/entry @@ -854,8 +851,8 @@ #. (itstool) path: row/entry #: book.translate.xml:986 msgid "" -"One directory exists for each available translation and encoding of the documentation, for example en_US.ISO8859-1/ and zh_TW.UTF-8/. The names are long, but by fully specifying the language and encoding we prevent any future headaches when a translation team wants to provide documentation in the same language but in more than one encoding. This also avoids problems " -"that might be caused by a future switch to Unicode." +"One directory exists for each available translation and encoding of the documentation, for example en_US.ISO8859-1/ and zh_TW.UTF-8/. The names are long, but by fully specifying the language and encoding we prevent any future headaches when a translation team wants to provide documentation in the same language but in more than one encoding. This also avoids problems that might be caused by a future " +"switch to Unicode." msgstr "" #. (itstool) path: sect1/title @@ -1010,8 +1007,8 @@ #. (itstool) path: sect4/para #: book.translate.xml:1154 msgid "" -"In earlier versions of the Handbook, the files were stored in the same directory as book.xml, and named after the value of the id attribute on the file's chapter element. Now, it is possible to include images in each chapter. Images for each Handbook chapter are stored within share/images/books/handbook. The localized version of these " -"images should be placed in the same directory as the XML sources for each chapter. Namespace collisions are inevitable, and it is easier to work with several directories with a few files in them than it is to work with one directory that has many files in it." +"In earlier versions of the Handbook, the files were stored in the same directory as book.xml, and named after the value of the id attribute on the file's chapter element. Now, it is possible to include images in each chapter. Images for each Handbook chapter are stored within share/images/books/handbook. The localized version of these images should be placed in the same " +"directory as the XML sources for each chapter. Namespace collisions are inevitable, and it is easier to work with several directories with a few files in them than it is to work with one directory that has many files in it." msgstr "" #. (itstool) path: sect4/para @@ -1637,9 +1634,7 @@ #. (itstool) path: listitem/para #: book.translate.xml:1788 -msgid "" -"This variable is best set with env1 or the user shell's method of setting environment variables, setenv for csh1 or export for sh1." +msgid "This variable is best set with env1 or the user shell's method of setting environment variables, setenv for csh1 or export for sh1." msgstr "" #. (itstool) path: varlistentry/term @@ -1848,9 +1843,7 @@ #. (itstool) path: example/para #: book.translate.xml:1967 -msgid "" -"The web site can be viewed at . Be aware that many links refer to the real FreeBSD site by name, and those links will still go to the external site instead of the local test version. Fully testing the local site will require temporarily setting DNS so www.FreeBSD.org resolves to localhost or the local IP address." +msgid "The web site can be viewed at . Be aware that many links refer to the real FreeBSD site by name, and those links will still go to the external site instead of the local test version. Fully testing the local site will require temporarily setting DNS so www.FreeBSD.org resolves to localhost or the local IP address." msgstr "" #. (itstool) path: example/title @@ -1909,8 +1902,8 @@ #. (itstool) path: sect1/para #: book.translate.xml:2060 msgid "" -"Inevitably, this was not enough. When text is in a machine-usable format, machines are expected to be able to use and manipulate it intelligently. Authors want to indicate that certain phrases should be emphasized, or added to a glossary, or made into hyperlinks. Filenames could be shown in a typewriter style font for viewing on screen, but as italics when printed, or any of a " -"myriad of other options for presentation." +"Inevitably, this was not enough. When text is in a machine-usable format, machines are expected to be able to use and manipulate it intelligently. Authors want to indicate that certain phrases should be emphasized, or added to a glossary, or made into hyperlinks. Filenames could be shown in a typewriter style font for viewing on screen, but as italics when printed, or any of a myriad of other options for " +"presentation." msgstr "" #. (itstool) path: sect1/para @@ -1942,8 +1935,8 @@ #. (itstool) path: sect1/para #: book.translate.xml:2092 msgid "" -"Markup is commonly used to describe adding value or increasing cost. The term takes on both these meanings when applied to text. Markup is additional text included in the document, distinguished from the document's content in some way, so that programs that process the document can read the markup and use it when making decisions about the document. Editors can " -"hide the markup from the user, so the user is not distracted by it." +"Markup is commonly used to describe adding value or increasing cost. The term takes on both these meanings when applied to text. Markup is additional text included in the document, distinguished from the document's content in some way, so that programs that process the document can read the markup and use it when making decisions about the document. Editors can hide the markup from the user, so the " +"user is not distracted by it." msgstr "" #. (itstool) path: sect1/para @@ -1977,8 +1970,7 @@ #. (itstool) path: sect1/para #: book.translate.xml:2123 -msgid "" -"Of course, one markup language might not be enough. A markup language for technical documentation has very different requirements than a markup language that is intended for cookery recipes. This, in turn, would be very different from a markup language used to describe poetry. What is really needed is a first language used to write these other markup languages. A meta markup language." +msgid "Of course, one markup language might not be enough. A markup language for technical documentation has very different requirements than a markup language that is intended for cookery recipes. This, in turn, would be very different from a markup language used to describe poetry. What is really needed is a first language used to write these other markup languages. A meta markup language." msgstr "" #. (itstool) path: sect1/para @@ -1995,15 +1987,15 @@ #. (itstool) id: book.translate.xml#xml-primer-validating #: book.translate.xml:2143 msgid "" -"A schema is a complete specification of all the elements that are allowed to appear, the order in which they should appear, which elements are mandatory, which are optional, and so forth. This makes it possible to write an XML parser which reads in both the schema and a document which claims to conform to the schema. The parser can then confirm " -"whether or not all the elements required by the vocabulary are in the document in the right order, and whether there are any errors in the markup. This is normally referred to as validating the document." +"A schema is a complete specification of all the elements that are allowed to appear, the order in which they should appear, which elements are mandatory, which are optional, and so forth. This makes it possible to write an XML parser which reads in both the schema and a document which claims to conform to the schema. The parser can then confirm whether or not all the elements required " +"by the vocabulary are in the document in the right order, and whether there are any errors in the markup. This is normally referred to as validating the document." msgstr "" #. (itstool) path: note/para #: book.translate.xml:2157 msgid "" -"Validation confirms that the choice of elements, their ordering, and so on, conforms to that listed in the grammar. It does not check whether appropriate markup has been used for the content. If all the filenames in a document were marked up as function names, the parser would not flag this as an error (assuming, of course, that the schema defines elements for " -"filenames and functions, and that they are allowed to appear in the same place)." +"Validation confirms that the choice of elements, their ordering, and so on, conforms to that listed in the grammar. It does not check whether appropriate markup has been used for the content. If all the filenames in a document were marked up as function names, the parser would not flag this as an error (assuming, of course, that the schema defines elements for filenames and functions, and that they are " +"allowed to appear in the same place)." msgstr "" #. (itstool) path: sect1/para @@ -2028,9 +2020,7 @@ #. (itstool) path: sect1/para #: book.translate.xml:2191 -msgid "" -"For example, consider a typical book. At the very top level, the book is itself an element. This book element obviously contains chapters, which can be considered to be elements in their own right. Each chapter will contain more elements, such as paragraphs, quotations, and footnotes. Each paragraph might contain further elements, identifying content that was direct speech, or the name of a " -"character in the story." +msgid "For example, consider a typical book. At the very top level, the book is itself an element. This book element obviously contains chapters, which can be considered to be elements in their own right. Each chapter will contain more elements, such as paragraphs, quotations, and footnotes. Each paragraph might contain further elements, identifying content that was direct speech, or the name of a character in the story." msgstr "" #. (itstool) path: sect1/para @@ -2233,8 +2223,8 @@ #. (itstool) path: sect2/para #: book.translate.xml:2368 msgid "" -"Before running the examples in this document, install textproc/docproj from the FreeBSD Ports Collection. This is a meta-port that downloads and installs the standard programs and supporting files needed by the Documentation Project. csh1 users must use rehash for the " -"shell to recognize new programs after they have been installed, or log out and then log back in again." +"Before running the examples in this document, install textproc/docproj from the FreeBSD Ports Collection. This is a meta-port that downloads and installs the standard programs and supporting files needed by the Documentation Project. csh1 users must use rehash for the shell to recognize new programs after " +"they have been installed, or log out and then log back in again." msgstr "" #. (itstool) path: step/para @@ -2443,8 +2433,8 @@ #. (itstool) path: listitem/para #: book.translate.xml:2564 msgid "" -"The beginning of the string identifies the owner of the FPI. For example, the FPI \"ISO 8879:1986//ENTITIES Greek Symbols//EN\" lists ISO 8879:1986 as being the owner for the set of entities for Greek symbols. ISO 8879:1986 is the International Organization for Standardization (ISO) number for the " -"SGML standard, the predecessor (and a superset) of XML." +"The beginning of the string identifies the owner of the FPI. For example, the FPI \"ISO 8879:1986//ENTITIES Greek Symbols//EN\" lists ISO 8879:1986 as being the owner for the set of entities for Greek symbols. ISO 8879:1986 is the International Organization for Standardization (ISO) number for the SGML standard, " +"the predecessor (and a superset) of XML." msgstr "" #. (itstool) path: listitem/para @@ -2460,8 +2450,8 @@ #. (itstool) path: listitem/para #: book.translate.xml:2589 msgid "" -"ISO 9070:1991 defines how registered names are generated. It might be derived from the number of an ISO publication, an ISBN code, or an organization code assigned according to ISO 6523. Additionally, a registration authority could be created in order to assign registered names. The ISO council delegated this to the " -"American National Standards Institute (ANSI)." +"ISO 9070:1991 defines how registered names are generated. It might be derived from the number of an ISO publication, an ISBN code, or an organization code assigned according to ISO 6523. Additionally, a registration authority could be created in order to assign registered names. The ISO council delegated this to the American National Standards " +"Institute (ANSI)." msgstr "" #. (itstool) path: listitem/para @@ -2477,8 +2467,8 @@ #. (itstool) path: listitem/para #: book.translate.xml:2611 msgid "" -"There are several keywords that indicate the type of information in the file. Some of the most common keywords are DTD, ELEMENT, ENTITIES, and TEXT. DTD is used only for DTD files, ELEMENT is usually used for DTD fragments that contain only entity or element " -"declarations. TEXT is used for XML content (text and tags)." +"There are several keywords that indicate the type of information in the file. Some of the most common keywords are DTD, ELEMENT, ENTITIES, and TEXT. DTD is used only for DTD files, ELEMENT is usually used for DTD fragments that contain only entity or element declarations. TEXT " +"is used for XML content (text and tags)." msgstr "" #. (itstool) path: varlistentry/term @@ -2570,9 +2560,7 @@ #. (itstool) path: sect1/para #: book.translate.xml:2711 -msgid "" -"XML sections begin with a <! tag and end with a >. These sections contain instructions for the parser rather than elements of the document. Everything between these tags is XML syntax. The DOCTYPE declaration shown earlier is an example of XML syntax " -"included in the document." +msgid "XML sections begin with a <! tag and end with a >. These sections contain instructions for the parser rather than elements of the document. Everything between these tags is XML syntax. The DOCTYPE declaration shown earlier is an example of XML syntax included in the document." msgstr "" #. (itstool) path: sect1/title @@ -2713,8 +2701,8 @@ #. (itstool) path: sect2/para #: book.translate.xml:2837 msgid "" -"General entities can also be used to enter characters that could not otherwise be included in an XML document. For example, < and & cannot normally appear in an XML document. The XML parser sees the < symbol as the start of a tag. Likewise, when the & symbol is " -"seen, the next text is expected to be an entity name." +"General entities can also be used to enter characters that could not otherwise be included in an XML document. For example, < and & cannot normally appear in an XML document. The XML parser sees the < symbol as the start of a tag. Likewise, when the & symbol is seen, the next text is expected to be an " +"entity name." msgstr "" #. (itstool) path: sect2/para @@ -3261,9 +3249,8 @@ #. (itstool) path: sect3/para #: book.translate.xml:3355 msgid "" -"Create an entity file that defines general entities to include each chapter and guard these definitions with a parameter entity that can be set to either INCLUDE or IGNORE to control whether the entity is defined. After these conditional general entity definitions, place one more definition for each general entity to set them to an empty value. This technique makes use of " -"the fact that entity definitions cannot be overridden but the first definition always takes effect. So the inclusion of the chapter is controlled with the corresponding parameter entity. Set to INCLUDE, the first general entity definition will be read and the second one will be ignored. Set to IGNORE, the first definition will be ignored and the second one will take " -"effect." +"Create an entity file that defines general entities to include each chapter and guard these definitions with a parameter entity that can be set to either INCLUDE or IGNORE to control whether the entity is defined. After these conditional general entity definitions, place one more definition for each general entity to set them to an empty value. This technique makes use of the fact that entity definitions " +"cannot be overridden but the first definition always takes effect. So the inclusion of the chapter is controlled with the corresponding parameter entity. Set to INCLUDE, the first general entity definition will be read and the second one will be ignored. Set to IGNORE, the first definition will be ignored and the second one will take effect." msgstr "" #. (itstool) path: example/title @@ -3466,9 +3453,9 @@ msgstr "" #. (itstool) path: example/para -#: book.translate.xml:3590 book.translate.xml:3625 book.translate.xml:3641 book.translate.xml:3686 book.translate.xml:3718 book.translate.xml:3795 book.translate.xml:3823 book.translate.xml:3845 book.translate.xml:3867 book.translate.xml:3923 book.translate.xml:3940 book.translate.xml:3970 book.translate.xml:3995 book.translate.xml:4736 book.translate.xml:4762 book.translate.xml:4843 book.translate.xml:4877 -#: book.translate.xml:4924 book.translate.xml:4984 book.translate.xml:5046 book.translate.xml:5126 book.translate.xml:5260 book.translate.xml:5421 book.translate.xml:5480 book.translate.xml:5507 book.translate.xml:5537 book.translate.xml:5576 book.translate.xml:5684 book.translate.xml:5741 book.translate.xml:5792 book.translate.xml:5911 book.translate.xml:5979 book.translate.xml:6008 book.translate.xml:6029 -#: book.translate.xml:6071 book.translate.xml:6126 book.translate.xml:6159 book.translate.xml:6176 book.translate.xml:6210 book.translate.xml:6234 book.translate.xml:6714 book.translate.xml:6730 +#: book.translate.xml:3590 book.translate.xml:3625 book.translate.xml:3641 book.translate.xml:3686 book.translate.xml:3718 book.translate.xml:3795 book.translate.xml:3823 book.translate.xml:3845 book.translate.xml:3867 book.translate.xml:3923 book.translate.xml:3940 book.translate.xml:3970 book.translate.xml:3995 book.translate.xml:4736 book.translate.xml:4762 book.translate.xml:4843 book.translate.xml:4877 book.translate.xml:4924 +#: book.translate.xml:4984 book.translate.xml:5046 book.translate.xml:5126 book.translate.xml:5260 book.translate.xml:5421 book.translate.xml:5480 book.translate.xml:5507 book.translate.xml:5537 book.translate.xml:5576 book.translate.xml:5684 book.translate.xml:5741 book.translate.xml:5792 book.translate.xml:5911 book.translate.xml:5979 book.translate.xml:6008 book.translate.xml:6029 book.translate.xml:6071 book.translate.xml:6126 +#: book.translate.xml:6159 book.translate.xml:6176 book.translate.xml:6210 book.translate.xml:6234 book.translate.xml:6714 book.translate.xml:6730 msgid "Usage:" msgstr "" @@ -3688,8 +3675,8 @@ #. (itstool) path: example/para #: book.translate.xml:3768 msgid "" -"Keep in mind that < and & still are recognized as special characters in pre-formatted text. This is why the example shown had to use &lt; instead of <. For consistency, &gt; was used in place of >, too. Watch out for the special characters that may appear in text copied from a " -"plain-text source, like an email message or program code." +"Keep in mind that < and & still are recognized as special characters in pre-formatted text. This is why the example shown had to use &lt; instead of <. For consistency, &gt; was used in place of >, too. Watch out for the special characters that may appear in text copied from a plain-text source, like an email " +"message or program code." msgstr "" #. (itstool) path: sect2/title @@ -3699,9 +3686,7 @@ #. (itstool) path: sect2/para #: book.translate.xml:3783 -msgid "" -"Mark up tabular information using the table element. A table consists of one or more table rows (tr), each containing one or more cells of table data (td). Each cell can contain other block elements, such as paragraphs or lists. It can also contain another table (this nesting can repeat indefinitely). If the cell only contains one paragraph then the pelement is not " -"needed." +msgid "Mark up tabular information using the table element. A table consists of one or more table rows (tr), each containing one or more cells of table data (td). Each cell can contain other block elements, such as paragraphs or lists. It can also contain another table (this nesting can repeat indefinitely). If the cell only contains one paragraph then the pelement is not needed." msgstr "" #. (itstool) path: example/title @@ -3996,8 +3981,8 @@ #. (itstool) path: sect1/para #: book.translate.xml:4080 msgid "" -"This chapter is an introduction to DocBook as it is used for FreeBSD documentation. DocBook is a large and complex markup system, but the subset described here covers the parts that are most widely used for FreeBSD documentation. While a moderate subset is covered, it is impossible to anticipate every situation. Please post questions that this document does not answer to the FreeBSD documentation project mailing list." +"This chapter is an introduction to DocBook as it is used for FreeBSD documentation. DocBook is a large and complex markup system, but the subset described here covers the parts that are most widely used for FreeBSD documentation. While a moderate subset is covered, it is impossible to anticipate every situation. Please post questions that this document does not answer to the FreeBSD documentation project mailing list." msgstr "" #. (itstool) path: footnote/para @@ -4008,8 +3993,8 @@ #. (itstool) path: sect1/para #: book.translate.xml:4088 msgid "" -"DocBook was originally developed by HaL Computer Systems and O'Reilly & Associates to be a Document Type Definition (DTD) for writing technical documentation <_:footnote-1/>. Since 1998 it is maintained by the DocBook Technical Committee. As such, and unlike LinuxDoc and XHTML, DocBook is very heavily oriented towards markup that describes what something is, rather than describing how it should be presented." +"DocBook was originally developed by HaL Computer Systems and O'Reilly & Associates to be a Document Type Definition (DTD) for writing technical documentation <_:footnote-1/>. Since 1998 it is maintained by the DocBook Technical Committee. As such, and unlike LinuxDoc and XHTML, DocBook is very heavily oriented " +"towards markup that describes what something is, rather than describing how it should be presented." msgstr "" #. (itstool) path: sect1/para @@ -4440,9 +4425,7 @@ #. (itstool) path: sect1/para #: book.translate.xml:4439 -msgid "" -"The nature of the document being written should be used to determine whether it is best marked up as a book or an article. Articles are well suited to information that does not need to be broken down into several chapters, and that is, relatively speaking, quite short, at up to 20-25 pages of content. Books are best suited to information that can be broken up into several chapters, possibly with appendices " -"and similar content as well." +msgid "The nature of the document being written should be used to determine whether it is best marked up as a book or an article. Articles are well suited to information that does not need to be broken down into several chapters, and that is, relatively speaking, quite short, at up to 20-25 pages of content. Books are best suited to information that can be broken up into several chapters, possibly with appendices and similar content as well." msgstr "" #. (itstool) path: sect1/para @@ -4757,8 +4740,8 @@ #. (itstool) path: example/para #. (itstool) path: sect2/para -#: book.translate.xml:4741 book.translate.xml:4779 book.translate.xml:4856 book.translate.xml:4887 book.translate.xml:4946 book.translate.xml:5008 book.translate.xml:5076 book.translate.xml:5143 book.translate.xml:5201 book.translate.xml:5285 book.translate.xml:5325 book.translate.xml:5434 book.translate.xml:5486 book.translate.xml:5515 book.translate.xml:5543 book.translate.xml:5591 book.translate.xml:5703 -#: book.translate.xml:5753 book.translate.xml:5800 book.translate.xml:5937 book.translate.xml:5985 book.translate.xml:6014 book.translate.xml:6035 book.translate.xml:6087 book.translate.xml:6133 book.translate.xml:6163 book.translate.xml:6186 book.translate.xml:6216 book.translate.xml:6238 book.translate.xml:6690 book.translate.xml:6704 book.translate.xml:6719 book.translate.xml:6737 +#: book.translate.xml:4741 book.translate.xml:4779 book.translate.xml:4856 book.translate.xml:4887 book.translate.xml:4946 book.translate.xml:5008 book.translate.xml:5076 book.translate.xml:5143 book.translate.xml:5201 book.translate.xml:5285 book.translate.xml:5325 book.translate.xml:5434 book.translate.xml:5486 book.translate.xml:5515 book.translate.xml:5543 book.translate.xml:5591 book.translate.xml:5703 book.translate.xml:5753 +#: book.translate.xml:5800 book.translate.xml:5937 book.translate.xml:5985 book.translate.xml:6014 book.translate.xml:6035 book.translate.xml:6087 book.translate.xml:6133 book.translate.xml:6163 book.translate.xml:6186 book.translate.xml:6216 book.translate.xml:6238 book.translate.xml:6690 book.translate.xml:6704 book.translate.xml:6719 book.translate.xml:6737 msgid "Appearance:" msgstr "" @@ -4941,8 +4924,7 @@ #. (itstool) path: sect2/para #: book.translate.xml:4910 -msgid "" -"itemizedlist and orderedlist are similar to their counterparts in HTML, ul and ol. Each one consists of one or more listitem elements, and each listitem contains one or more block elements. The listitem elements are analogous to HTML's li tags. However, unlike HTML, they are required." +msgid "itemizedlist and orderedlist are similar to their counterparts in HTML, ul and ol. Each one consists of one or more listitem elements, and each listitem contains one or more block elements. The listitem elements are analogous to HTML's li tags. However, unlike HTML, they are required." msgstr "" #. (itstool) path: example/title @@ -5283,8 +5265,8 @@ #. (itstool) path: sect2/para #: book.translate.xml:5240 msgid "" -"In general terms (and see the DocBook documentation for more detail) a table (which can be either formal or informal) consists of a table element. This contains at least one tgroup element, which specifies (as an attribute) the number of columns in this table group. Within the tablegroup there is one thead element, which contains elements for the table headings (column " -"headings), and one tbody which contains the body of the table." +"In general terms (and see the DocBook documentation for more detail) a table (which can be either formal or informal) consists of a table element. This contains at least one tgroup element, which specifies (as an attribute) the number of columns in this table group. Within the tablegroup there is one thead element, which contains elements for the table headings (column headings), and one tbody which " +"contains the body of the table." msgstr "" #. (itstool) path: sect2/para @@ -6533,9 +6515,7 @@ #. (itstool) path: sect2/para #: book.translate.xml:6506 -msgid "" -"Suppose there is a book with three chapters, and the chapters are stored in their own directories, called chapter1/chapter.xml, chapter2/chapter.xml, and chapter3/chapter.xml. If each chapter has images associated with it, place those images in each chapter's subdirectory (chapter1/, chapter2/, and " -"chapter3/)." +msgid "Suppose there is a book with three chapters, and the chapters are stored in their own directories, called chapter1/chapter.xml, chapter2/chapter.xml, and chapter3/chapter.xml. If each chapter has images associated with it, place those images in each chapter's subdirectory (chapter1/, chapter2/, and chapter3/)." msgstr "" #. (itstool) path: sect2/para @@ -6627,8 +6607,8 @@ #. (itstool) path: sect2/para #: book.translate.xml:6594 msgid "" -"Use descriptive values for xml:id names. The values must be unique within the entire document, not just in a single file. In the example, the subsection xml:id is constructed by appending text to the chapter xml:id. This ensures that the xml:ids are unique. It also helps both reader and anyone editing the document to see where the " -"link is located within the document, similar to a directory path to a file." +"Use descriptive values for xml:id names. The values must be unique within the entire document, not just in a single file. In the example, the subsection xml:id is constructed by appending text to the chapter xml:id. This ensures that the xml:ids are unique. It also helps both reader and anyone editing the document to see where the link is located within the document, " +"similar to a directory path to a file." msgstr "" #. (itstool) path: sect2/title @@ -6685,8 +6665,8 @@ #. (itstool) path: sect2/para #: book.translate.xml:6650 msgid "" -"The link element described here allows the writer to define the link text. When link text is used, it is very important to be descriptive to give the reader an idea of where the link goes. Remember that DocBook can be rendered to multiple types of media. The reader might be looking at a printed book or other form of media where there are no links. If the link text is not descriptive enough, the reader might " -"not be able to locate the linked section." +"The link element described here allows the writer to define the link text. When link text is used, it is very important to be descriptive to give the reader an idea of where the link goes. Remember that DocBook can be rendered to multiple types of media. The reader might be looking at a printed book or other form of media where there are no links. If the link text is not descriptive enough, the reader might not be able to locate the linked " +"section." msgstr "" #. (itstool) path: sect2/para @@ -6835,8 +6815,8 @@ #. (itstool) path: chapter/para #: book.translate.xml:6800 msgid "" -"XML is concerned with content, and says nothing about how that content should be presented to the reader or rendered on paper. Multiple style sheet languages have been developed to describe visual layout, including Extensible Stylesheet Language Transformation (XSLT), Document Style Semantics and Specification Language (DSSSL), and " -"Cascading Style Sheets (CSS)." +"XML is concerned with content, and says nothing about how that content should be presented to the reader or rendered on paper. Multiple style sheet languages have been developed to describe visual layout, including Extensible Stylesheet Language Transformation (XSLT), Document Style Semantics and Specification Language (DSSSL), and Cascading Style Sheets (CSS)." msgstr "" #. (itstool) path: chapter/para @@ -6861,8 +6841,7 @@ #. (itstool) path: sect2/para #: book.translate.xml:6829 -msgid "" -"The FreeBSD XSLT and DSSSL stylesheets refer to docbook.css, which is expected to be present in the same directory as the XHTML files. The project-wide CSS file is copied from doc/share/misc/docbook.css when documents are converted to XHTML, and is installed automatically." +msgid "The FreeBSD XSLT and DSSSL stylesheets refer to docbook.css, which is expected to be present in the same directory as the XHTML files. The project-wide CSS file is copied from doc/share/misc/docbook.css when documents are converted to XHTML, and is installed automatically." msgstr "" #. (itstool) path: chapter/title @@ -7370,13 +7349,12 @@ #. (itstool) path: sect1/para #: book.translate.xml:7327 msgid "" -"The GNU gettext system offers translators an easy way to create and maintain translations of documents. Translatable strings are extracted from the original document into a PO (Portable Object) file. Translated versions of the strings are entered with a separate editor. The strings " -"can be used directly or built into a complete translated version of the original document." +"The GNU gettext system offers translators an easy way to create and maintain translations of documents. Translatable strings are extracted from the original document into a PO (Portable Object) file. Translated versions of the strings are entered with a separate editor. The strings can be used directly or built into a " +"complete translated version of the original document." msgstr "GNU gettext 系統提供翻譯者一個簡單的方法來建立和維護文件的翻譯。翻譯的字串從原始文件題取出來到PO (Portable Object) 檔。字串的翻譯用另外的編輯器輸入。翻譯的字串可以直接使用，或是編譯成原始文件的完整翻譯版本。" #. (itstool) path: sect1/para #: book.translate.xml:7340 -#, fuzzy msgid "The procedure shown in is assumed to have already been performed, but the TRANSLATOR option must be enabled in the textproc/docproj port. If that option was not enabled, display the options menu and enable it, then reinstall the port:" msgstr "在 的步驟還必須打開 textproc/docproj port TRANSLATOR 選項。如果沒有打開這個選項，請打開選項後，重新安裝 port。" @@ -7394,13 +7372,11 @@ #. (itstool) path: sect1/para #: book.translate.xml:7352 -#, fuzzy msgid "This example shows the creation of a Spanish translation of the short Leap Seconds article." msgstr "這個範例示範如何建立Leap Seconds 短文的西班牙文翻譯" #. (itstool) path: procedure/title #: book.translate.xml:7357 -#, fuzzy msgid "Install a PO Editor" msgstr "安裝 PO 編輯器" @@ -7421,13 +7397,11 @@ #. (itstool) path: procedure/title #: book.translate.xml:7370 -#, fuzzy msgid "Initial Setup" msgstr "初始設定" #. (itstool) path: procedure/para #: book.translate.xml:7372 -#, fuzzy msgid "When a new translation is first created, the directory structure and Makefile must be created or copied from the English original:" msgstr "第一次建立新的翻譯時，目錄結構和 Makefile 必須建立或是從英文版複製過來。" @@ -7464,7 +7438,6 @@ #. (itstool) path: procedure/para #: book.translate.xml:7400 -#, fuzzy msgid "Translating a document consists of two steps: extracting translatable strings from the original document, and entering translations for those strings. These steps are repeated until the translator feels that enough of the document has been translated to produce a usable translated document." msgstr "翻譯文件公有兩個步驟：將可翻譯的字串從原始文件提去出來，然後翻譯這些字串。重複這些步驟，直到翻譯者認為文件的翻譯部份已經足夠用來產生可讀的翻譯文件。" @@ -7501,7 +7474,6 @@ #. (itstool) path: procedure/title #: book.translate.xml:7432 -#, fuzzy msgid "Generating a Translated Document" msgstr "產生翻譯文件" @@ -7547,10 +7519,9 @@ #. (itstool) path: sect1/para #: book.translate.xml:7460 -#, fuzzy msgid "" -"The first step to creating a new translated document is locating or creating a directory to hold it. FreeBSD puts translated documents in a subdirectory named for their language and region in the format lang_REGION. lang is a two-character lowercase code. It is followed by an underscore character and then the " -"two-character uppercase REGION code." +"The first step to creating a new translated document is locating or creating a directory to hold it. FreeBSD puts translated documents in a subdirectory named for their language and region in the format lang_REGION. lang is a two-character lowercase code. It is followed by an underscore character and then the two-character uppercase " +"REGION code." msgstr "建立新翻譯文件的第一步是找到或建立一個目錄來放它。FreeBSD 將翻譯文件放在子目錄，用語系和區域以語系_區域來命名。語系 是小寫的兩個字元碼。接著是底線和兩個字元的大寫 REGION 碼。" #. (itstool) path: table/title @@ -8061,13 +8032,12 @@ #. (itstool) path: sect1/para #: book.translate.xml:7683 msgid "" -"FreeBSD documentation builds are controlled by a Makefile in the same directory. With simple articles, the Makefile can often just be copied verbatim from the original English directory. The translation process combines multiple separate book.xml and chapter.xml files in books into a single file, so the Makefile for book translations must be copied and modified." +"FreeBSD documentation builds are controlled by a Makefile in the same directory. With simple articles, the Makefile can often just be copied verbatim from the original English directory. The translation process combines multiple separate book.xml and chapter.xml files in books into a single file, so the Makefile for book translations must be " +"copied and modified." msgstr "FreeBSD 文件的編譯是由同一個目錄的 Makefile 控制。簡單的文章可以從原始的英語目錄直接複製 Makefile 過來。書籍的翻譯流程結合多個獨立的 book.xml 和 chapter.xml 成為一個檔案， 所以書籍翻譯的 Makefile 必須複製並修改。" #. (itstool) path: example/title #: book.translate.xml:7694 -#, fuzzy msgid "Creating a Spanish Translation of the Porter's Handbook" msgstr "建立 Porter 手冊的西班牙語翻譯" @@ -8213,7 +8183,6 @@ #. (itstool) path: step/para #: book.translate.xml:7771 -#, fuzzy msgid "Now the document structure is ready for the translator to begin translating with make po." msgstr "現在文件結構已經準備好讓翻譯者執行 make po 開始翻譯。" @@ -8321,7 +8290,6 @@ #. (itstool) path: sect1/title #: book.translate.xml:7844 -#, fuzzy msgid "Translating" msgstr "翻譯" @@ -8377,7 +8345,6 @@ #. (itstool) path: sect1/title #: book.translate.xml:7898 -#, fuzzy msgid "Tips for Translators" msgstr "給翻譯者的提示" @@ -8537,14 +8504,11 @@ #. (itstool) path: sect1/para #: book.translate.xml:8062 -msgid "" -"A translated version of the original document can be created at any time. Any untranslated portions of the original will be included in English in the resulting document. Most PO editors have an indicator that shows how much of the translation has been completed. This makes it easy for the translator to see when enough strings have been translated to make building the final document " -"worthwhile." +msgid "A translated version of the original document can be created at any time. Any untranslated portions of the original will be included in English in the resulting document. Most PO editors have an indicator that shows how much of the translation has been completed. This makes it easy for the translator to see when enough strings have been translated to make building the final document worthwhile." msgstr "原文的翻譯版本可以在任何時候被建立。未翻譯的部份會以英文呈獻。大部份 PO 編輯器有指標可以顯示翻譯完成度。這讓翻譯者更容易看翻譯好的字串是否足夠來編譯最終的文件。" #. (itstool) path: example/title #: book.translate.xml:8072 -#, fuzzy msgid "Building the Spanish Porter's Handbook" msgstr "編譯西班牙文 Porter 手冊" @@ -8816,8 +8780,8 @@ #. (itstool) path: sect2/para #: book.translate.xml:8324 msgid "" -"Give clear, correct, tested examples. A trivial example is better than no example. A good example is better yet. Do not give bad examples, identifiable by apologies or sentences like but really it should never be done that way. Bad examples are worse than no examples. Give good examples, because even when warned not to use the example as shown, the " -"reader will usually just use the example as shown." +"Give clear, correct, tested examples. A trivial example is better than no example. A good example is better yet. Do not give bad examples, identifiable by apologies or sentences like but really it should never be done that way. Bad examples are worse than no examples. Give good examples, because even when warned not to use the example as shown, the reader will usually just use the example " +"as shown." msgstr "" #. (itstool) path: sect2/para @@ -9012,7 +8976,6 @@ #. (itstool) path: sect2/title #: book.translate.xml:8515 -#, fuzzy msgid "Letter Case" msgstr "大小寫" @@ -9098,7 +9061,6 @@ #. (itstool) path: sect2/para #: book.translate.xml:8579 -#, fuzzy msgid "Tags containing long attributes follow the same rules. Following the indentation rules in this case helps editors and writers see which content is inside the tags:" msgstr "有長屬性的標籤也是遵循一樣的原則。遵守縮排規則可以幫助編輯和作者了解哪些內容在標籤內：" @@ -9483,7 +9445,6 @@ #. (itstool) path: row/entry #: book.translate.xml:8839 -#, fuzzy msgid "things that apply to user space, not the kernel" msgstr "指user space，不是核心。" @@ -9687,7 +9648,6 @@ #. (itstool) path: chapter/title #: book.translate.xml:9054 -#, fuzzy msgid "See Also" msgstr "他山之石" @@ -9759,8 +9719,8 @@ #. (itstool) path: appendix/para #: book.translate.xml:9167 msgid "" -"These examples are not exhaustive—they do not contain all the elements that might be desirable to use, particularly in a document's front matter. For more examples of DocBook markup, examine the XML source for this and other documents available in the Subversion doc repository, or available online starting at http://svnweb.FreeBSD.org/doc/." +"These examples are not exhaustive—they do not contain all the elements that might be desirable to use, particularly in a document's front matter. For more examples of DocBook markup, examine the XML source for this and other documents available in the Subversion doc repository, or available online starting at http://svnweb.FreeBSD." +"org/doc/." msgstr "" #. (itstool) path: sect1/title