diff --git a/Manuals/Docbook/Entities/Licenses.docbook b/Manuals/Docbook/Entities/Licenses.docbook
new file mode 100644
index 0000000..5a7534e
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses.docbook
@@ -0,0 +1,6 @@
+<?xml version="1.0"?>
+<part>
+ <title>Licenses</title>
+ &license-gpl;
+ &license-gfdl;
+</part>
diff --git a/Manuals/Docbook/Entities/Licenses/Gfdl.docbook b/Manuals/Docbook/Entities/Licenses/Gfdl.docbook
new file mode 100644
index 0000000..e6dd831
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gfdl.docbook
@@ -0,0 +1,27 @@
+<?xml version="1.0"?>
+<appendix id="licenses-gfdl-chapter" xreflabel="GNU Free Documentation License">
+
+ <title>GNU Free Documentation License</title>
+
+ <para>Version 1.2, November 2002</para>
+
+ <para>Copyright © 2000, 2001, 2002 Free Software Foundation,
+ Inc. 675 Mass Ave, Cambridge, MA 02139, USA</para>
+
+ <para>Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.</para>
+
+ &licenses-gfdl-preamble;
+ &licenses-gfdl-applicability-and-definitions;
+ &licenses-gfdl-verbatim-copying;
+ &licenses-gfdl-copying-in-quantity;
+ &licenses-gfdl-modifications;
+ &licenses-gfdl-combining-documents;
+ &licenses-gfdl-collection-of-documents;
+ &licenses-gfdl-aggregation-with-independent-works;
+ &licenses-gfdl-translations;
+ &licenses-gfdl-termination;
+ &licenses-gfdl-future-revisions-of-this-license;
+ &licenses-gfdl-how-to-use-this-license;
+
+</appendix>
diff --git a/Manuals/Docbook/Entities/Licenses/Gfdl/aggregation-with-independent-workds.docbook b/Manuals/Docbook/Entities/Licenses/Gfdl/aggregation-with-independent-workds.docbook
new file mode 100644
index 0000000..2d4d4aa
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gfdl/aggregation-with-independent-workds.docbook
@@ -0,0 +1,25 @@
+<?xml version="1.0"?>
+<section id="licenses-gfdl-section-8" xreflabel="Aggregation with independent works">
+
+ <title>Aggregation with independent works</title>
+
+ <para>A compilation of the Document or its derivatives with other
+ separate and independent documents or works, in or on a volume of
+ a storage or distribution medium, is called an
+ <quote>aggregate</quote> if the copyright resulting from the
+ compilation is not used to limit the legal rights of the
+ compilation's users beyond what the individual works permit. When
+ the Document is included in an aggregate, this License does not
+ apply to the other works in the aggregate which are not themselves
+ derivative works of the Document.</para>
+
+ <para>If the Cover Text requirement of section <xref
+ linkend="licenses-gfdl-section-4" /> is applicable to these copies
+ of the Document, then if the Document is less than one half of the
+ entire aggregate, the Document's Cover Texts may be placed on
+ covers that bracket the Document within the aggregate, or the
+ electronic equivalent of covers if the Document is in electronic
+ form. Otherwise they must appear on printed covers that bracket
+ the whole aggregate.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gfdl/applicability-and-definitions.docbook b/Manuals/Docbook/Entities/Licenses/Gfdl/applicability-and-definitions.docbook
new file mode 100644
index 0000000..9adb858
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gfdl/applicability-and-definitions.docbook
@@ -0,0 +1,102 @@
+<?xml version="1.0"?>
+<section id="licenses-gfdl-section-2" xreflabel="Applicability and definitions">
+
+ <title>Applicability and definitions</title>
+
+ <para>This License applies to any manual or other work, in any
+ medium, that contains a notice placed by the copyright holder
+ saying it can be distributed under the terms of this License.
+ Such a notice grants a world-wide, royalty-free license, unlimited
+ in duration, to use that work under the conditions stated herein.
+ The <quote>Document</quote>, below, refers to any such manual or
+ work. Any member of the public is a licensee, and is addressed as
+ <quote>you</quote>. You accept the license if you copy, modify or
+ distribute the work in a way requiring permission under copyright
+ law.</para>
+
+ <para>A <quote>Modified Version</quote> of the Document means any
+ work containing the Document or a portion of it, either copied
+ verbatim, or with modifications and/or translated into another
+ language.</para>
+
+ <para>A <quote>Secondary Section</quote> is a named appendix or a
+ front-matter section of the Document that deals exclusively with
+ the relationship of the publishers or authors of the Document to
+ the Document's overall subject (or to related matters) and
+ contains nothing that could fall directly within that overall
+ subject. (Thus, if the Document is in part a textbook of
+ mathematics, a Secondary Section may not explain any mathematics.)
+ The relationship could be a matter of historical connection with
+ the subject or with related matters, or of legal, commercial,
+ philosophical, ethical or political position regarding
+ them.</para>
+
+ <para>The <quote>Invariant Sections</quote> are certain Secondary Sections
+ whose titles are designated, as being those of Invariant Sections,
+ in the notice that says that the Document is released under this
+ License. If a section does not fit the above definition of
+ Secondary then it is not allowed to be designated as Invariant.
+ The Document may contain zero Invariant Sections. If the Document
+ does not identify any Invariant Sections then there are
+ none.</para>
+
+ <para>The <quote>Cover Texts</quote> are certain short passages of text that
+ are listed, as Front-Cover Texts or Back-Cover Texts, in the
+ notice that says that the Document is released under this License.
+ A Front-Cover Text may be at most 5 words, and a Back-Cover Text
+ may be at most 25 words.</para>
+
+ <para>A <quote>Transparent</quote> copy of the Document means a
+ machine-readable copy, represented in a format whose specification
+ is available to the general public, that is suitable for revising
+ the document straightforwardly with generic text editors or (for
+ images composed of pixels) generic paint programs or (for
+ drawings) some widely available drawing editor, and that is
+ suitable for input to text formatters or for automatic translation
+ to a variety of formats suitable for input to text formatters. A
+ copy made in an otherwise Transparent file format whose markup, or
+ absence of markup, has been arranged to thwart or discourage
+ subsequent modification by readers is not Transparent. An image
+ format is not Transparent if used for any substantial amount of
+ text. A copy that is not <quote>Transparent</quote> is called
+ <quote>Opaque</quote>.</para>
+
+ <para>Examples of suitable formats for Transparent copies include
+ plain ASCII without markup, Texinfo input format, LaTeX input
+ format, SGML or XML using a publicly available DTD, and
+ standard-conforming simple HTML, PostScript or PDF designed for
+ human modification. Examples of transparent image formats include
+ PNG, XCF and JPG. Opaque formats include proprietary formats that
+ can be read and edited only by proprietary word processors, SGML
+ or XML for which the DTD and/or processing tools are not generally
+ available, and the machine-generated HTML, PostScript or PDF
+ produced by some word processors for output purposes only.</para>
+
+ <para>The <quote>Title Page</quote> means, for a printed book, the
+ title page itself, plus such following pages as are needed to
+ hold, legibly, the material this License requires to appear in the
+ title page. For works in formats which do not have any title page
+ as such, <quote>Title Page</quote> means the text near the most
+ prominent appearance of the work's title, preceding the beginning
+ of the body of the text.</para>
+
+ <para>A section <quote>Entitled XYZ</quote> means a named subunit
+ of the Document whose title either is precisely XYZ or contains
+ XYZ in parentheses following text that translates XYZ in another
+ language. (Here XYZ stands for a specific section name mentioned
+ below, such as <quote>Acknowledgements</quote>,
+ <quote>Dedications</quote>, <quote>Endorsements</quote>, or
+ <quote>History</quote>.) To <quote>Preserve the Title</quote> of
+ such a section when you modify the Document means that it remains
+ a section <quote>Entitled XYZ</quote> according to this
+ definition.</para>
+
+ <para>The Document may include Warranty Disclaimers next to the
+ notice which states that this License applies to the Document.
+ These Warranty Disclaimers are considered to be included by
+ reference in this License, but only as regards disclaiming
+ warranties: any other implication that these Warranty Disclaimers
+ may have is void and has no effect on the meaning of this
+ License.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gfdl/collection-of-documents.docbook b/Manuals/Docbook/Entities/Licenses/Gfdl/collection-of-documents.docbook
new file mode 100644
index 0000000..9396f9b
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gfdl/collection-of-documents.docbook
@@ -0,0 +1,19 @@
+<?xml version="1.0"?>
+<section id="licenses-gfdl-section-7" xreflabel="Collection of documents">
+
+ <title>Collection of documents</title>
+
+ <para>You may make a collection consisting of the Document and
+ other documents released under this License, and replace the
+ individual copies of this License in the various documents with a
+ single copy that is included in the collection, provided that you
+ follow the rules of this License for verbatim copying of each of
+ the documents in all other respects.</para>
+
+ <para>You may extract a single document from such a collection,
+ and distribute it individually under this License, provided you
+ insert a copy of this License into the extracted document, and
+ follow this License in all other respects regarding verbatim
+ copying of that document.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gfdl/combining-documents.docbook b/Manuals/Docbook/Entities/Licenses/Gfdl/combining-documents.docbook
new file mode 100644
index 0000000..71bbcb3
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gfdl/combining-documents.docbook
@@ -0,0 +1,32 @@
+<?xml version="1.0"?>
+<section id="licenses-gfdl-section-6" xreflabel="Combining documents">
+
+ <title>Combining documents</title>
+
+ <para>You may combine the Document with other documents released
+ under this License, under the terms defined in section <xref
+ linkend="licenses-gfdl-section-5" /> above for modified versions,
+ provided that you include in the combination all of the Invariant
+ Sections of all of the original documents, unmodified, and list
+ them all as Invariant Sections of your combined work in its
+ license notice, and that you preserve all their Warranty
+ Disclaimers.</para>
+
+ <para>The combined work need only contain one copy of this
+ License, and multiple identical Invariant Sections may be replaced
+ with a single copy. If there are multiple Invariant Sections with
+ the same name but different contents, make the title of each such
+ section unique by adding at the end of it, in parentheses, the
+ name of the original author or publisher of that section if known,
+ or else a unique number. Make the same adjustment to the section
+ titles in the list of Invariant Sections in the license notice of
+ the combined work.</para>
+
+ <para>In the combination, you must combine any sections Entitled
+ <quote>History</quote> in the various original documents, forming
+ one section Entitled <quote>History</quote>; likewise combine any
+ sections Entitled <quote>Acknowledgements</quote>, and any
+ sections Entitled <quote>Dedications</quote>. You must delete all
+ sections Entitled <quote>Endorsements</quote>.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gfdl/copying-in-quantity.docbook b/Manuals/Docbook/Entities/Licenses/Gfdl/copying-in-quantity.docbook
new file mode 100644
index 0000000..5bb583e
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gfdl/copying-in-quantity.docbook
@@ -0,0 +1,44 @@
+<?xml version="1.0"?>
+<section id="licenses-gfdl-section-4" xreflabel="Copying in quantity">
+
+ <title>Copying in quantity</title>
+
+ <para>If you publish printed copies (or copies in media that
+ commonly have printed covers) of the Document, numbering more than
+ 100, and the Document's license notice requires Cover Texts, you
+ must enclose the copies in covers that carry, clearly and legibly,
+ all these Cover Texts: Front-Cover Texts on the front cover, and
+ Back-Cover Texts on the back cover. Both covers must also clearly
+ and legibly identify you as the publisher of these copies. The
+ front cover must present the full title with all words of the
+ title equally prominent and visible. You may add other material
+ on the covers in addition. Copying with changes limited to the
+ covers, as long as they preserve the title of the Document and
+ satisfy these conditions, can be treated as verbatim copying in
+ other respects.</para>
+
+ <para>If the required texts for either cover are too voluminous to
+ fit legibly, you should put the first ones listed (as many as fit
+ reasonably) on the actual cover, and continue the rest onto
+ adjacent pages.</para>
+
+ <para>If you publish or distribute Opaque copies of the Document
+ numbering more than 100, you must either include a
+ machine-readable Transparent copy along with each Opaque copy, or
+ state in or with each Opaque copy a computer-network location from
+ which the general network-using public has access to download
+ using public-standard network protocols a complete Transparent
+ copy of the Document, free of added material. If you use the
+ latter option, you must take reasonably prudent steps, when you
+ begin distribution of Opaque copies in quantity, to ensure that
+ this Transparent copy will remain thus accessible at the stated
+ location until at least one year after the last time you
+ distribute an Opaque copy (directly or through your agents or
+ retailers) of that edition to the public.</para>
+
+ <para>It is requested, but not required, that you contact the
+ authors of the Document well before redistributing any large
+ number of copies, to give them a chance to provide you with an
+ updated version of the Document.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gfdl/future-revisions-of-this-license.docbook b/Manuals/Docbook/Entities/Licenses/Gfdl/future-revisions-of-this-license.docbook
new file mode 100644
index 0000000..a97aa94
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gfdl/future-revisions-of-this-license.docbook
@@ -0,0 +1,22 @@
+<?xml version="1.0"?>
+<section id="licenses-gfdl-section-11" xreflabel="Future Revisions of this License">
+
+ <title>Future Revisions of this License</title>
+
+ <para>The Free Software Foundation may publish new, revised
+ versions of the GNU Free Documentation License from time to time.
+ Such new versions will be similar in spirit to the present
+ version, but may differ in detail to address new problems or
+ concerns. See <ulink url="http://www.gnu.org/copyleft/" />.</para>
+
+ <para>Each version of the License is given a distinguishing
+ version number. If the Document specifies that a particular
+ numbered version of this License <quote>or any later version</quote> applies
+ to it, you have the option of following the terms and conditions
+ either of that specified version or of any later version that has
+ been published (not as a draft) by the Free Software Foundation.
+ If the Document does not specify a version number of this License,
+ you may choose any version ever published (not as a draft) by the
+ Free Software Foundation.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gfdl/how-to-use-this-license.docbook b/Manuals/Docbook/Entities/Licenses/Gfdl/how-to-use-this-license.docbook
new file mode 100644
index 0000000..5e94411
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gfdl/how-to-use-this-license.docbook
@@ -0,0 +1,40 @@
+<?xmll version="1.0"?>
+<section id="licenses-gfdl-section-12" xreflabel="How to use this License for your documents">
+
+ <title>How to use this License for your documents</title>
+
+ <para>To use this License in a document you have written, include
+ a copy of the License in the document and put the following
+ copyright and license notices just after the title page:</para>
+
+ <programlisting>
+ Copyright (C) YEAR YOUR NAME.
+
+ Permission is granted to copy, distribute and/or modify this
+ document under the terms of the GNU Free Documentation License,
+ Version 1.2 or any later version published by the Free Software
+ Foundation; with no Invariant Sections, no Front-Cover Texts, and
+ no Back-Cover Texts. A copy of the license is included in the
+ section entitled <quote>GNU Free Documentation License</quote>.
+ </programlisting>
+
+ <para>If you have Invariant Sections, Front-Cover Texts and
+ Back-Cover Texts, replace the <quote>with...Texts</quote>. line with
+ this:</para>
+
+ <programlisting>
+ with the Invariant Sections being LIST THEIR TITLES, with the
+ Front-Cover Texts being LIST, and with the Back-Cover Texts being
+ LIST.
+ </programlisting>
+
+ <para>If you have Invariant Sections without Cover Texts, or some
+ other combination of the three, merge those two alternatives to
+ suit the situation.</para>
+
+ <para>If your document contains nontrivial examples of program
+ code, we recommend releasing these examples in parallel under your
+ choice of free software license, such as the GNU General Public
+ License, to permit their use in free software.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gfdl/modifications.docbook b/Manuals/Docbook/Entities/Licenses/Gfdl/modifications.docbook
new file mode 100644
index 0000000..1ff6399
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gfdl/modifications.docbook
@@ -0,0 +1,148 @@
+<?xml version="1.0"?>
+<section id="licenses-gfdl-section-5" xreflabel="Modification">
+
+ <title>Modifications</title>
+
+ <para>You may copy and distribute a Modified Version of the
+ Document under the conditions of sections <xref
+ linkend="licenses-gfdl-section-3" /> and <xref
+ linkend="licenses-gfdl-section-4" /> above, provided that you
+ release the Modified Version under precisely this License, with
+ the Modified Version filling the role of the Document, thus
+ licensing distribution and modification of the Modified Version to
+ whoever possesses a copy of it. In addition, you must do these
+ things in the Modified Version:
+
+ <orderedlist numeration="upperalpha">
+
+ <listitem>
+ <para> Use in the Title Page (and on the covers, if any) a
+ title distinct from that of the Document, and from those
+ of previous versions (which should, if there were any, be
+ listed in the History section of the Document). You may
+ use the same title as a previous version if the original
+ publisher of that version gives permission.</para>
+ </listitem>
+
+ <listitem>
+ <para>List on the Title Page, as authors, one or more
+ persons or entities responsible for authorship of the
+ modifications in the Modified Version, together with at
+ least five of the principal authors of the Document (all
+ of its principal authors, if it has fewer than five),
+ unless they release you from this requirement.</para>
+ </listitem>
+
+ <listitem>
+ <para>State on the Title page the name of the publisher of
+ the Modified Version, as the publisher.</para>
+ </listitem>
+
+ <listitem>
+ <para>Preserve all the copyright notices of the
+ Document.</para>
+ </listitem>
+
+ <listitem>
+ <para>Add an appropriate copyright notice for your
+ modifications adjacent to the other copyright
+ notices.</para>
+ </listitem>
+
+ <listitem>
+ <para>Include, immediately after the copyright notices, a
+ license notice giving the public permission to use the
+ Modified Version under the terms of this License, in the
+ form shown in the Addendum below.</para>
+ </listitem>
+ <listitem>
+ <para>Preserve in that license notice the full lists of
+ Invariant Sections and required Cover Texts given in the
+ Document's license notice.</para>
+ </listitem>
+ <listitem>
+ <para>Include an unaltered copy of this License.</para>
+ </listitem>
+ <listitem>
+ <para>Preserve the section Entitled
+ <quote>History</quote>, Preserve its Title, and add to it
+ an item stating at least the title, year, new authors, and
+ publisher of the Modified Version as given on the Title
+ Page. If there is no section Entitled
+ <quote>History</quote> in the Document, create one stating
+ the title, year, authors, and publisher of the Document as
+ given on its Title Page, then add an item describing the
+ Modified Version as stated in the previous
+ sentence.</para>
+ </listitem>
+ <listitem>
+ <para>Preserve the network location, if any, given in the
+ Document for public access to a Transparent copy of the
+ Document, and likewise the network locations given in the
+ Document for previous versions it was based on. These may
+ be placed in the <quote>History</quote> section. You may
+ omit a network location for a work that was published at
+ least four years before the Document itself, or if the
+ original publisher of the version it refers to gives
+ permission.</para>
+ </listitem>
+ <listitem>
+ <para>For any section Entitled
+ <quote>Acknowledgements</quote> or
+ <quote>Dedications</quote>, Preserve the Title of the
+ section, and preserve in the section all the substance and
+ tone of each of the contributor acknowledgements and/or
+ dedications given therein.</para>
+ </listitem>
+ <listitem>
+ <para>Preserve all the Invariant Sections of the Document,
+ unaltered in their text and in their titles. Section
+ numbers or the equivalent are not considered part of the
+ section titles.</para>
+ </listitem>
+ <listitem>
+ <para>Delete any section Entitled <quote>Endorsements</quote>. Such
+ a section may not be included in the Modified
+ Version.</para>
+ </listitem>
+ <listitem>
+ <para>Do not retitle any existing section to be Entitled
+ <quote>Endorsements</quote> or to conflict in title with
+ any Invariant Section.</para>
+ </listitem>
+ <listitem>
+ <para>Preserve any Warranty Disclaimers.</para>
+ </listitem>
+ </orderedlist>
+ </para>
+
+ <para>If the Modified Version includes new front-matter sections
+ or appendices that qualify as Secondary Sections and contain no
+ material copied from the Document, you may at your option
+ designate some or all of these sections as invariant. To do this,
+ add their titles to the list of Invariant Sections in the Modified
+ Version's license notice. These titles must be distinct from any
+ other section titles.</para>
+
+ <para>You may add a section Entitled <quote>Endorsements</quote>,
+ provided it contains nothing but endorsements of your Modified
+ Version by various parties–for example, statements of peer
+ review or that the text has been approved by an organization as
+ the authoritative definition of a standard.</para>
+
+ <para>You may add a passage of up to five words as a Front-Cover
+ Text, and a passage of up to 25 words as a Back-Cover Text, to the
+ end of the list of Cover Texts in the Modified Version. Only one
+ passage of Front-Cover Text and one of Back-Cover Text may be
+ added by (or through arrangements made by) any one entity. If the
+ Document already includes a cover text for the same cover,
+ previously added by you or by arrangement made by the same entity
+ you are acting on behalf of, you may not add another; but you may
+ replace the old one, on explicit permission from the previous
+ publisher that added the old one.</para>
+
+ <para>The author(s) and publisher(s) of the Document do not by
+ this License give permission to use their names for publicity for
+ or to assert or imply endorsement of any Modified Version.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gfdl/preamble.docbook b/Manuals/Docbook/Entities/Licenses/Gfdl/preamble.docbook
new file mode 100644
index 0000000..a10aba0
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gfdl/preamble.docbook
@@ -0,0 +1,30 @@
+<?xml version="1.0"?>
+<section id="licenses-gfdl-section-1" xreflabel="Preamble">
+
+ <title>Preamble</title>
+
+ <para>The purpose of this License is to make a manual, textbook,
+ or other functional and useful document <quote>free</quote> in the
+ sense of freedom: to assure everyone the effective freedom to copy
+ and redistribute it, with or without modifying it, either
+ commercially or noncommercially. Secondarily, this License
+ preserves for the author and publisher a way to get credit for
+ their work, while not being considered responsible for
+ modifications made by others.</para>
+
+ <para>This License is a kind of <quote>copyleft</quote>, which
+ means that derivative works of the document must themselves be
+ free in the same sense. It complements the <xref
+ linkend="licenses-gfdl-chapter" />, which is a copyleft license
+ designed for free software.</para>
+
+ <para>We have designed this License in order to use it for manuals
+ for free software, because free software needs free documentation:
+ a free program should come with manuals providing the same
+ freedoms that the software does. But this License is not limited
+ to software manuals; it can be used for any textual work,
+ regardless of subject matter or whether it is published as a
+ printed book. We recommend this License principally for works
+ whose purpose is instruction or reference.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gfdl/termination.docbook b/Manuals/Docbook/Entities/Licenses/Gfdl/termination.docbook
new file mode 100644
index 0000000..453d644
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gfdl/termination.docbook
@@ -0,0 +1,15 @@
+<?xml version="1.0"?>
+<section id="licenses-gfdl-section-10" xreflabel="Tremination">
+
+ <title>Termination</title>
+
+ <para>You may not copy, modify, sublicense, or distribute the
+ Document except as expressly provided for under this License. Any
+ other attempt to copy, modify, sublicense or distribute the
+ Document is void, and will automatically terminate your rights
+ under this License. However, parties who have received copies, or
+ rights, from you under this License will not have their licenses
+ terminated so long as such parties remain in full
+ compliance.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gfdl/translations.docbook b/Manuals/Docbook/Entities/Licenses/Gfdl/translations.docbook
new file mode 100644
index 0000000..53eb02a
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gfdl/translations.docbook
@@ -0,0 +1,27 @@
+<?xml version="1.0"?>
+<section id="licenses-gfdl-section-9" xreflabel="Translations">
+
+ <title>Translations</title>
+
+ <para>Translation is considered a kind of modification, so you may
+ distribute translations of the Document under the terms of section
+ <xref linkend="licenses-gfdl-section-5"/>. Replacing Invariant
+ Sections with translations requires special permission from their
+ copyright holders, but you may include translations of some or all
+ Invariant Sections in addition to the original versions of these
+ Invariant Sections. You may include a translation of this
+ License, and all the license notices in the Document, and any
+ Warranty Disclaimers, provided that you also include the original
+ English version of this License and the original versions of those
+ notices and disclaimers. In case of a disagreement between the
+ translation and the original version of this License or a notice
+ or disclaimer, the original version will prevail.</para>
+
+ <para>If a section in the Document is Entitled
+ <quote>Acknowledgements</quote>, <quote>Dedications</quote>, or
+ <quote>History</quote>, the requirement (section <xref
+ linkend="licenses-gfdl-section-5" />) to Preserve its Title
+ (section <xref linkend="licenses-gfdl-section-2" />) will
+ typically require changing the actual title.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gfdl/verbatim-copying.docbook b/Manuals/Docbook/Entities/Licenses/Gfdl/verbatim-copying.docbook
new file mode 100644
index 0000000..5d2647a
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gfdl/verbatim-copying.docbook
@@ -0,0 +1,21 @@
+<?xml version="1.0"?>
+<section id="licenses-gfdl-section-3" xreflabel="Verbatim copying">
+
+ <title>Verbatim copying</title>
+
+ <para>You may copy and distribute the Document in any medium,
+ either commercially or noncommercially, provided that this
+ License, the copyright notices, and the license notice saying this
+ License applies to the Document are reproduced in all copies, and
+ that you add no other conditions whatsoever to those of this
+ License. You may not use technical measures to obstruct or
+ control the reading or further copying of the copies you make or
+ distribute. However, you may accept compensation in exchange for
+ copies. If you distribute a large enough number of copies you
+ must also follow the conditions in section <xref
+ linkend="licenses-gfdl-section-4" />.</para>
+
+ <para>You may also lend copies, under the same conditions stated
+ above, and you may publicly display copies.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl.docbook b/Manuals/Docbook/Entities/Licenses/Gpl.docbook
new file mode 100644
index 0000000..21b56ae
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl.docbook
@@ -0,0 +1,31 @@
+<?xml version="1.0"?>
+<appendix id="licenses-gpl-chapter" xreflabel="GNU General Public License">
+
+ <title>GNU General Public License</title>
+
+ <para>Version 2, June 1991</para>
+
+ <para>Copyright © 1989, 1991 Free Software Foundation, Inc.
+ 675 Mass Ave, Cambridge, MA 02139, USA</para>
+
+ <para>Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.</para>
+
+ &licenses-gpl-preamble;
+ &licenses-gpl-terms-and-conditions;
+ &licenses-gpl-terms-and-conditions-section-0;
+ &licenses-gpl-terms-and-conditions-section-1;
+ &licenses-gpl-terms-and-conditions-section-2;
+ &licenses-gpl-terms-and-conditions-section-3;
+ &licenses-gpl-terms-and-conditions-section-4;
+ &licenses-gpl-terms-and-conditions-section-5;
+ &licenses-gpl-terms-and-conditions-section-6;
+ &licenses-gpl-terms-and-conditions-section-7;
+ &licenses-gpl-terms-and-conditions-section-8;
+ &licenses-gpl-terms-and-conditions-section-9;
+ &licenses-gpl-terms-and-conditions-section-10;
+ &licenses-gpl-terms-and-conditions-section-11;
+ &licenses-gpl-terms-and-conditions-section-12;
+ &licenses-gpl-how-to-apply-this-license;
+
+</appendix>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions.docbook
new file mode 100644
index 0000000..d1a255b
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions.docbook
@@ -0,0 +1,20 @@
+<?xml version="1.0"?>
+<section>
+
+ <title>Terms and Conditions for Copying, Distribution and Modification</title>
+
+ &licenses-gpl-section-2-0;
+ &licenses-gpl-section-2-1;
+ &licenses-gpl-section-2-2;
+ &licenses-gpl-section-2-3;
+ &licenses-gpl-section-2-4;
+ &licenses-gpl-section-2-5;
+ &licenses-gpl-section-2-6;
+ &licenses-gpl-section-2-7;
+ &licenses-gpl-section-2-8;
+ &licenses-gpl-section-2-9;
+ &licenses-gpl-section-2-10;
+ &licenses-gpl-section-2-11;
+ &licenses-gpl-section-2-12;
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-0.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-0.docbook
new file mode 100644
index 0000000..6561990
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-0.docbook
@@ -0,0 +1,26 @@
+<?xml version="1.0"?>
+<section id="licenses-gpl-section-2-0" xreflabel="Section 0">
+
+ <title>Section 0</title>
+
+ <para>This License applies to any program or other work which
+ contains a notice placed by the copyright holder saying it may be
+ distributed under the terms of this General Public License. The
+ <quote>Program</quote>, below, refers to any such program or work,
+ and a <quote>work based on the Program</quote> means either the
+ Program or any derivative work under copyright law: that is to
+ say, a work containing the Program or a portion of it, either
+ verbatim or with modifications and/or translated into another
+ language. (Hereinafter, translation is included without
+ limitation in the term <quote>modification</quote>.) Each
+ licensee is addressed as <quote>you</quote>.</para>
+
+ <para>Activities other than copying, distribution and modification
+ are not covered by this License; they are outside its scope. The
+ act of running the Program is not restricted, and the output from
+ the Program is covered only if its contents constitute a work
+ based on the Program (independent of having been made by running
+ the Program). Whether that is true depends on what the Program
+ does.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-1.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-1.docbook
new file mode 100644
index 0000000..f5d0b88
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-1.docbook
@@ -0,0 +1,18 @@
+<?xml version="1.0"?>
+<section id="licenses-gpl-section-2-1" xreflabel="Section 1">
+
+ <title>Section 1</title>
+
+ <para>You may copy and distribute verbatim copies of the Program's
+ source code as you receive it, in any medium, provided that you
+ conspicuously and appropriately publish on each copy an
+ appropriate copyright notice and disclaimer of warranty; keep
+ intact all the notices that refer to this License and to the
+ absence of any warranty; and give any other recipients of the
+ Program a copy of this License along with the Program.</para>
+
+ <para>You may charge a fee for the physical act of transferring a
+ copy, and you may at your option offer warranty protection in
+ exchange for a fee.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-10.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-10.docbook
new file mode 100644
index 0000000..36839e0
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-10.docbook
@@ -0,0 +1,15 @@
+<?xml version="1.0"?>
+<section id="licenses-gpl-section-2-10" xreflabel="Section 10">
+
+ <title>Section 10</title>
+
+ <para>If you wish to incorporate parts of the Program into other
+ free programs whose distribution conditions are different, write
+ to the author to ask for permission. For software which is
+ copyrighted by the Free Software Foundation, write to the Free
+ Software Foundation; we sometimes make exceptions for this. Our
+ decision will be guided by the two goals of preserving the free
+ status of all derivatives of our free software and of promoting
+ the sharing and reuse of software generally.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-11.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-11.docbook
new file mode 100644
index 0000000..3ddc003
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-11.docbook
@@ -0,0 +1,18 @@
+<?xml version="1.0"?>
+<section id="licenses-gpl-section-11" xreflabel="NO WARRANTY">
+
+ <title>NO WARRANTY</title>
+ <subtitle>Section 11</subtitle>
+
+ <para>BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
+ WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
+ LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+ HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM <quote>AS IS</quote> WITHOUT
+ WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT
+ NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+ FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
+ QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+ PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY
+ SERVICING, REPAIR OR CORRECTION.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-12.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-12.docbook
new file mode 100644
index 0000000..3881698
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-12.docbook
@@ -0,0 +1,19 @@
+<?xml version="1.0"?>
+<section id="licenses-gpl-section-12" xreflabel="Section 12">
+
+ <title>Section 12</title>
+
+ <para>IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO
+ IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY
+ MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE
+ LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+ INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
+ INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+ DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU
+ OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY
+ OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
+ ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.</para>
+
+ <para><emphasis>End of Terms and Conditions.</emphasis></para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-2.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-2.docbook
new file mode 100644
index 0000000..0d8f5c6
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-2.docbook
@@ -0,0 +1,70 @@
+<?xml version="1.0"?>
+<section id="licenses-gpl-section-2-2" xreflabel="Section 2">
+
+ <title>Section 2</title>
+
+ <para>You may modify your copy or copies of the Program or any
+ portion of it, thus forming a work based on the Program, and copy
+ and distribute such modifications or work under the terms of
+ Section 1 above, provided that you also meet all of these
+ conditions:</para>
+
+ <orderedlist numeration="loweralpha">
+ <listitem>
+ <para>You must cause the modified files to carry prominent
+ notices stating that you changed the files and the date of
+ any change.</para>
+ </listitem>
+ <listitem>
+ <para>You must cause any work that you distribute or
+ publish, that in whole or in part contains or is derived
+ from the Program or any part thereof, to be licensed as a
+ whole at no charge to all third parties under the terms of
+ this License.</para>
+ </listitem>
+ <listitem>
+ <para>If the modified program normally reads commands
+ interactively when run, you must cause it, when started
+ running for such interactive use in the most ordinary way,
+ to print or display an announcement including an
+ appropriate copyright notice and a notice that there is no
+ warranty (or else, saying that you provide a warranty) and
+ that users may redistribute the program under these
+ conditions, and telling the user how to view a copy of
+ this License.
+
+ <note>
+ <title>Exception</title>
+ <para>
+ If the Program itself is interactive but does not
+ normally print such an announcement, your work based
+ on the Program is not required to print an
+ announcement.
+ </para>
+ </note>
+ </para>
+ </listitem>
+ </orderedlist>
+
+ <para>These requirements apply to the modified work as a whole.
+ If identifiable sections of that work are not derived from the
+ Program, and can be reasonably considered independent and separate
+ works in themselves, then this License, and its terms, do not
+ apply to those sections when you distribute them as separate
+ works. But when you distribute the same sections as part of a
+ whole which is a work based on the Program, the distribution of
+ the whole must be on the terms of this License, whose permissions
+ for other licensees extend to the entire whole, and thus to each
+ and every part regardless of who wrote it.</para>
+
+ <para>Thus, it is not the intent of this section to claim rights
+ or contest your rights to work written entirely by you; rather,
+ the intent is to exercise the right to control the distribution of
+ derivative or collective works based on the Program.</para>
+
+ <para>In addition, mere aggregation of another work not based on
+ the Program with the Program (or with a work based on the Program)
+ on a volume of a storage or distribution medium does not bring the
+ other work under the scope of this License.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-3.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-3.docbook
new file mode 100644
index 0000000..a78568e
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-3.docbook
@@ -0,0 +1,60 @@
+<?xml version="1.0"?>
+<section id="licenses-gpl-section-2-3" xreflabel="Section 3">
+
+ <title>Section 3</title>
+
+ <para>You may copy and distribute the Program (or a work based on
+ it, under Section 2) in object code or executable form under the
+ terms of Sections 1 and 2 above provided that you also do one of
+ the following:
+
+ <orderedlist numeration="loweralpha">
+ <listitem>
+
+ <para> Accompany it with the complete corresponding
+ machine-readable source code, which must be distributed
+ under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,</para>
+
+ </listitem>
+ <listitem>
+
+ <para>Accompany it with a written offer, valid for at
+ least three years, to give any third party, for a charge
+ no more than your cost of physically performing source
+ distribution, a complete machine-readable copy of the
+ corresponding source code, to be distributed under the
+ terms of Sections 1 and 2 above on a medium customarily
+ used for software interchange; or,</para>
+
+ <para>Accompany it with the information you received as
+ to the offer to distribute corresponding source code.
+ (This alternative is allowed only for noncommercial
+ distribution and only if you received the program in
+ object code or executable form with such an offer, in
+ accord with Subsection b above.)</para>
+
+ </listitem>
+ </orderedlist>
+ </para>
+
+ <para>The source code for a work means the preferred form of the
+ work for making modifications to it. For an executable work,
+ complete source code means all the source code for all modules it
+ contains, plus any associated interface definition files, plus the
+ scripts used to control compilation and installation of the
+ executable. However, as a special exception, the source code
+ distributed need not include anything that is normally distributed
+ (in either source or binary form) with the major components
+ (compiler, kernel, and so on) of the operating system on which the
+ executable runs, unless that component itself accompanies the
+ executable.</para>
+
+ <para>If distribution of executable or object code is made by
+ offering access to copy from a designated place, then offering
+ equivalent access to copy the source code from the same place
+ counts as distribution of the source code, even though third
+ parties are not compelled to copy the source along with the object
+ code.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-4.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-4.docbook
new file mode 100644
index 0000000..0123586
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-4.docbook
@@ -0,0 +1,15 @@
+<?xml version="1.0"?>
+<section id="licenses-gpl-section-2-4" xreflabel="Section 4">
+
+ <title>Section 4</title>
+
+ <para>You may not copy, modify, sublicense, or distribute the
+ Program except as expressly provided under this License. Any
+ attempt otherwise to copy, modify, sublicense or distribute the
+ Program is void, and will automatically terminate your rights
+ under this License. However, parties who have received copies, or
+ rights, from you under this License will not have their licenses
+ terminated so long as such parties remain in full
+ compliance.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-5.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-5.docbook
new file mode 100644
index 0000000..f52db23
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-5.docbook
@@ -0,0 +1,15 @@
+<?xml version="1.0"?>
+<section id="licenses-gpl-section-2-5" xreflabel="Section 5">
+
+ <title>Section 5</title>
+
+ <para>You are not required to accept this License, since you have
+ not signed it. However, nothing else grants you permission to
+ modify or distribute the Program or its derivative works. These
+ actions are prohibited by law if you do not accept this License.
+ Therefore, by modifying or distributing the Program (or any work
+ based on the Program), you indicate your acceptance of this
+ License to do so, and all its terms and conditions for copying,
+ distributing or modifying the Program or works based on it.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-6.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-6.docbook
new file mode 100644
index 0000000..8222570
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-6.docbook
@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<section id="licenses-gpl-section-2-6" xreflabel="Section 6">
+
+ <title>Section 6</title>
+
+ <para>Each time you redistribute the Program (or any work based on
+ the Program), the recipient automatically receives a license from
+ the original licensor to copy, distribute or modify the Program
+ subject to these terms and conditions. You may not impose any
+ further restrictions on the recipients' exercise of the rights
+ granted herein. You are not responsible for enforcing compliance
+ by third parties to this License.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-7.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-7.docbook
new file mode 100644
index 0000000..29a696e
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-7.docbook
@@ -0,0 +1,39 @@
+<?xml version="1.0"?>
+<section id="licenses-gpl-section-2-7" xreflabel="Section 7">
+
+ <title>Section 7</title>
+
+ <para>If, as a consequence of a court judgment or allegation of
+ patent infringement or for any other reason (not limited to patent
+ issues), conditions are imposed on you (whether by court order,
+ agreement or otherwise) that contradict the conditions of this
+ License, they do not excuse you from the conditions of this
+ License. If you cannot distribute so as to satisfy simultaneously
+ your obligations under this License and any other pertinent
+ obligations, then as a consequence you may not distribute the
+ Program at all. For example, if a patent license would not permit
+ royalty-free redistribution of the Program by all those who
+ receive copies directly or indirectly through you, then the only
+ way you could satisfy both it and this License would be to refrain
+ entirely from distribution of the Program.</para>
+
+ <para>If any portion of this section is held invalid or
+ unenforceable under any particular circumstance, the balance of
+ the section is intended to apply and the section as a whole is
+ intended to apply in other circumstances.</para>
+
+ <para>It is not the purpose of this section to induce you to
+ infringe any patents or other property right claims or to contest
+ validity of any such claims; this section has the sole purpose of
+ protecting the integrity of the free software distribution system,
+ which is implemented by public license practices. Many people
+ have made generous contributions to the wide range of software
+ distributed through that system in reliance on consistent
+ application of that system; it is up to the author/donor to decide
+ if he or she is willing to distribute software through any other
+ system and a licensee cannot impose that choice.</para>
+
+ <para>This section is intended to make thoroughly clear what is
+ believed to be a consequence of the rest of this License.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-8.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-8.docbook
new file mode 100644
index 0000000..a3b968d
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-8.docbook
@@ -0,0 +1,15 @@
+<?xml version="1.0"?>
+<section id="licenses-gpl-section-2-8" xreflabel="Section 8">
+
+ <title>Section 8</title>
+
+ <para>If the distribution and/or use of the Program is restricted
+ in certain countries either by patents or by copyrighted
+ interfaces, the original copyright holder who places the Program
+ under this License may add an explicit geographical distribution
+ limitation excluding those countries, so that distribution is
+ permitted only in or among countries not thus excluded. In such
+ case, this License incorporates the limitation as if written in
+ the body of this License.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-9.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-9.docbook
new file mode 100644
index 0000000..0f98bfe
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/Terms-and-conditions/section-9.docbook
@@ -0,0 +1,20 @@
+<?xml version="1.0"?>
+<section id="licenses-gpl-section-2-9" xreflabel="Section 9">
+
+ <title>Section 9</title>
+
+ <para>The Free Software Foundation may publish revised and/or new
+ versions of the General Public License from time to time. Such
+ new versions will be similar in spirit to the present version, but
+ may differ in detail to address new problems or concerns.</para>
+
+ <para>Each version is given a distinguishing version number. If
+ the Program specifies a version number of this License which
+ applies to it and <quote>any later version</quote>, you have the
+ option of following the terms and conditions either of that
+ version or of any later version published by the Free Software
+ Foundation. If the Program does not specify a version number of
+ this License, you may choose any version ever published by the
+ Free Software Foundation.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/how-to-apply-this-license.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/how-to-apply-this-license.docbook
new file mode 100644
index 0000000..32d6c40
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/how-to-apply-this-license.docbook
@@ -0,0 +1,75 @@
+<?xml version="1.0"?>
+<section>
+
+ <title>How to Apply These Terms to Your New Programs</title>
+
+ <para>If you develop a new program, and you want it to be of the
+ greatest possible use to the public, the best way to achieve this
+ is to make it free software which everyone can redistribute and
+ change under these terms.</para>
+
+ <para>To do so, attach the following notices to the program. It
+ is safest to attach them to the start of each source file to most
+ effectively convey the exclusion of warranty; and each file should
+ have at least the <quote>copyright</quote> line and a pointer to
+ where the full notice is found.</para>
+
+ <programlisting>
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) 19yy <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+ </programlisting>
+
+ <para>Also add information on how to contact you by electronic and
+ paper mail.</para>
+
+ <para>If the program is interactive, make it output a short notice
+ like this when it starts in an interactive mode:</para>
+
+ <programlisting>
+ Gnomovision version 69, Copyright (C) 19yy name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+ </programlisting>
+
+ <para>The hypothetical commands `show w' and `show c' should show
+ the appropriate parts of the General Public License. Of course,
+ the commands you use may be called something other than `show w'
+ and `show c'; they could even be mouse-clicks or menu
+ items–whatever suits your program.</para>
+
+ <para>You should also get your employer (if you work as a
+ programmer) or your school, if any, to sign a <quote>copyright
+ disclaimer</quote> for the program, if necessary. Here is a sample;
+ alter the names:</para>
+
+ <programlisting>
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+ </programlisting>
+
+ <para>This General Public License does not permit incorporating
+ your program into proprietary programs. If your program is a
+ subroutine library, you may consider it more useful to permit
+ linking proprietary applications with the library. If this is
+ what you want to do, use the GNU Library General Public License
+ instead of this License.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Licenses/Gpl/preamble.docbook b/Manuals/Docbook/Entities/Licenses/Gpl/preamble.docbook
new file mode 100644
index 0000000..ce9d2cc
--- /dev/null
+++ b/Manuals/Docbook/Entities/Licenses/Gpl/preamble.docbook
@@ -0,0 +1,57 @@
+<?xml version="1.0"?>
+<section>
+
+ <title>Preamble</title>
+
+ <para>The licenses for most software are designed to take away
+ your freedom to share and change it. By contrast, the GNU General
+ Public License is intended to guarantee your freedom to share and
+ change free software–to make sure the software is free for
+ all its users. This General Public License applies to most of the
+ Free Software Foundation's software and to any other program whose
+ authors commit to using it. (Some other Free Software Foundation
+ software is covered by the GNU Library General Public License
+ instead.) You can apply it to your programs, too.</para>
+
+ <para>When we speak of free software, we are referring to freedom,
+ not price. Our General Public Licenses are designed to make sure
+ that you have the freedom to distribute copies of free software
+ (and charge for this service if you wish), that you receive source
+ code or can get it if you want it, that you can change the
+ software or use pieces of it in new free programs; and that you
+ know you can do these things.</para>
+
+ <para>To protect your rights, we need to make restrictions that
+ forbid anyone to deny you these rights or to ask you to surrender
+ the rights. These restrictions translate to certain
+ responsibilities for you if you distribute copies of the software,
+ or if you modify it.</para>
+
+ <para>For example, if you distribute copies of such a program,
+ whether gratis or for a fee, you must give the recipients all the
+ rights that you have. You must make sure that they, too, receive
+ or can get the source code. And you must show them these terms so
+ they know their rights.</para>
+
+ <para>We protect your rights with two steps: (1) copyright the
+ software, and (2) offer you this license which gives you legal
+ permission to copy, distribute and/or modify the software.</para>
+
+ <para>Also, for each author's protection and ours, we want to make
+ certain that everyone understands that there is no warranty for
+ this free software. If the software is modified by someone else
+ and passed on, we want its recipients to know that what they have
+ is not the original, so that any problems introduced by others
+ will not reflect on the original authors' reputations.</para>
+
+ <para>Finally, any free program is threatened constantly by
+ software patents. We wish to avoid the danger that redistributors
+ of a free program will individually obtain patent licenses, in
+ effect making the program proprietary. To prevent this, we have
+ made it clear that any patent must be licensed for everyone's free
+ use or not licensed at all.</para>
+
+ <para>The precise terms and conditions for copying, distribution
+ and modification follow.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Preface.docbook b/Manuals/Docbook/Entities/Preface.docbook
new file mode 100644
index 0000000..3090ff8
--- /dev/null
+++ b/Manuals/Docbook/Entities/Preface.docbook
@@ -0,0 +1,34 @@
+<?xml version="1.0"?>
+<preface>
+
+ <title>Introduction</title>
+
+ <para>Welcome to <emphasis>The CentOS Artwork Repository
+ Manual</emphasis>.</para>
+
+ <para>The CentOS Artwork Repository Manual describes how The
+ CentOS Project Corporate Visual Identity is organized and produced
+ inside the CentOS Artwork Repository (<ulink
+ url="https://projects.centos.org/svn/artwork/" />). If you are
+ looking for a comprehensive, task-oriented guide for understanding
+ how The CentOS Project Corporate Visual Identity is produced, this
+ is the manual for you.</para>
+
+ <para>This manual discusses the following intermedite
+ topics:
+
+ <itemizedlist>
+ <listitem><para>The CentOS Brand</para></listitem>
+ <listitem><para>The CentOS Corporate Visual Structure</para></listitem>
+ <listitem><para>The CentOS Corporate Visual Style</para></listitem>
+ </itemizedlist></para>
+
+ <para>This guide assumes you have a basic understanding of your
+ CentOS system. If you need help with CentOS, refer to the help
+ page on the CentOS Wiki (<ulink url="http://wiki.centos.org/Help"
+ />) for a list of different places you can find help.</para>
+
+ &preface-document-convenctions;
+ &preface-send-in-your-feedback;
+
+</preface>
diff --git a/Manuals/Docbook/Entities/Preface/document-convenctions.docbook b/Manuals/Docbook/Entities/Preface/document-convenctions.docbook
new file mode 100644
index 0000000..c58c66f
--- /dev/null
+++ b/Manuals/Docbook/Entities/Preface/document-convenctions.docbook
@@ -0,0 +1,148 @@
+<?xml version="1.0"?>
+<section>
+
+ <title>Document convenctions</title>
+
+ <para>In this manual the personal pronoun <emphasis>we</emphasis>
+ is used to repesent <emphasis>The CentOS Artwork SIG</emphasis>,
+ the group of persons that build The CentOS Project corporate
+ visual identity through the CentOS Artwork Repository.</para>
+
+ <para>In this manual, certain words are represented in different
+ fonts, typefaces, sizes, and weights. This highlighting is
+ systematic; different words are represented in the same style to
+ indicate their inclusion in a specific category. The types of
+ words that are represented this way include the following:</para>
+
+ <glosslist>
+ <glossentry>
+ <glossterm><command>command</command></glossterm>
+ <glossdef>
+ <para> Linux commands (and other operating system
+ commands, when used) are represented this way. This
+ style should indicate to you that you can type the
+ word or phrase on the command line and press Enter to
+ invoke a command. Sometimes a command contains words
+ that would be displayed in a different style on their
+ own (such as file names). In these cases, they are
+ considered to be part of the command, so the entire
+ phrase is displayed as a command. For example:</para>
+
+ <para>Use the <command>centos-art identity
+ --render='path/to/dir'</command> command to produce
+ contents inside the <filename
+ class="directory">trunk/Identity</filename> directory
+ structure.</para>
+
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm><filename>file name</filename></glossterm>
+ <glossdef>
+ <para>File names, directory names, paths, and RPM
+ package names are represented this way. This style
+ indicates that a particular file or directory exists
+ with that name on your system. Examples:</para>
+
+ <para>The <filename>init.sh</filename> file in
+ <filename
+ class="directory">trunk/Scripts/Bash/Cli/</filename>
+ directory is the initialization script, written in
+ Bash, used to automate most of tasks in the
+ repository.</para>
+
+ <para>The <command>centos-art</command> command uses
+ the <package>ImageMagick</package> RPM package to
+ convert images from PNG format to other
+ formats.</para>
+
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm><keycap>key</keycap></glossterm>
+ <glossdef>
+ <para> A key on the keyboard is shown in this style.
+ For example:</para>
+
+ <para>To use <keycap>TAB</keycap> completion to list
+ particular files in a directory, type @command{ls},
+ then a character, and finally the Tab key. Your
+ terminal displays the list of files in the working
+ directory that begin with that character.</para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry>
+ <glossterm><keycombo action="simul"><keycap>key-combination</keycap></keycombo></glossterm>
+ <glossdef>
+ <para>A combination of keystrokes is represented in
+ this way. For example:</para>
+
+ <para>The <keycombo
+ action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Backspace</keycap></keycombo>
+ key combination exits your graphical session and
+ returns you to the graphical login screen or the
+ console.</para>
+
+ </glossdef>
+
+ </glossentry>
+
+ <glossentry>
+ <glossterm><computeroutput>computer output</computeroutput></glossterm>
+ <glossdef>
+ <para> Text in this style indicates text displayed to a
+ shell prompt such as error messages and responses to
+ commands. For example:</para>
+
+ <para>The <command>ls</command> command displays the
+ contents of a directory. For example:
+
+ <programlisting>
+Config help_renameEntry.sh
+help_copyEntry.sh help_restoreCrossReferences.sh
+help_deleteCrossReferences.sh help_searchIndex.sh
+ </programlisting>
+
+ The output returned in response to the command (in this
+ case, the contents of the directory) is shown in this
+ style.</para>
+ </glossdef>
+ </glossentry>
+ </glosslist>
+
+ <para>Additionally, we use several different strategies to draw
+ your attention to certain pieces of information. In order of
+ urgency, these items are marked as a note, tip, important,
+ caution, or warning. For example:</para>
+
+ <note>
+ <para>Remember that Linux is case sensitive. In other words, a
+ rose is not a ROSE is not a rOsE.</para>
+ </note>
+
+ <tip>
+ <para>The directory @file{/usr/share/doc/} contains additional
+ documentation for packages installed on your system.</para>
+ </tip>
+
+ <important>
+ <para>If you modify the DHCP configuration file, the changes
+ do not take effect until you restart the DHCP daemon.</para>
+ </important>
+
+ <caution>
+ <para>Do not perform routine tasks as root — use a
+ regular user account unless you need to use the root account
+ for system administration tasks.</para>
+ </caution>
+
+ <warning>
+ <para>Be careful to remove only the necessary partitions.
+ Removing other partitions could result in data loss or a
+ corrupted system environment.</para>
+ </warning>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Preface/send-in-your-feedback.docbook b/Manuals/Docbook/Entities/Preface/send-in-your-feedback.docbook
new file mode 100644
index 0000000..b3dc889
--- /dev/null
+++ b/Manuals/Docbook/Entities/Preface/send-in-your-feedback.docbook
@@ -0,0 +1,18 @@
+<?xml version="1.0"?>
+<section>
+
+ <title>Send in your feedback</title>
+
+ <para> If you find an error in the <emphasis>CentOS Artwork
+ Repository</emphasis>, or if you have thought of a way to make
+ this manual better, we would like to hear from you! Share your
+ suggestions in the appropriate mailing list
+ (http://lists.centos.org/) and/or bug tracker
+ (http://bugs.centos.org/).</para>
+
+ <para>When you make suggestion, try to be as specific as possible.
+ For example, if you have found an error in the manual, include the
+ section number and some of the surrounding text so we can find it
+ easily.</para>
+
+</section>
diff --git a/Manuals/Docbook/Entities/Repository.docbook b/Manuals/Docbook/Entities/Repository.docbook
new file mode 100644
index 0000000..e8575d3
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository.docbook
@@ -0,0 +1,10 @@
+<?xml version="1.0"?>
+<part>
+ <title>The Repository</title>
+
+ &repository-history;
+ &repository-copying;
+ &repository-usage;
+ &repository-directories;
+
+</part>
diff --git a/Manuals/Docbook/Entities/Repository/Copying/chapter.docbook b/Manuals/Docbook/Entities/Repository/Copying/chapter.docbook
new file mode 100644
index 0000000..aeffb79
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Copying/chapter.docbook
@@ -0,0 +1,13 @@
+<?xml version="1.0"?>
+<chapter id="repository-copying-chapter" xreflabel="Copying">
+
+ <title>Copying conditions</title>
+
+ <para>Copyright © 2009, 2010, 2011 The CentOS Project</para>
+ <para>Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.</para>
+
+ &repository-copying-section-1;
+ &repository-copying-section-2;
+
+</chapter>
diff --git a/Manuals/Docbook/Entities/Repository/Copying/section-1.docbook b/Manuals/Docbook/Entities/Repository/Copying/section-1.docbook
new file mode 100644
index 0000000..082c06d
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Copying/section-1.docbook
@@ -0,0 +1,57 @@
+<?xml version="1.0"?>
+<sect1 id="repository-copying-section-1" xreflabel="Preamble" label="2.1">
+
+ <title>Preamble</title>
+
+ <para>The CentOS Artwork Repository organizes files in a very
+ specific way to implement The CentOS Project corporate visual
+ identity. This very specific organization of files must be
+ considered part of <command>centos-art.sh</command> script, a bash
+ script that automate most of the frequent tasks inside the
+ repository.</para>
+
+ <para>The <command>centos-art.sh</command> script and the
+ organization of files it needs to work are not in the public
+ domain; they are copyrighted and there are restrictions on their
+ distribution, but these restrictions are designed to permit
+ everything that a good cooperating citizen would want to do. What
+ is not allowed is to try to prevent others from further sharing
+ any version of this program that they might get from you.</para>
+
+ <para>Specifically, we want to make sure that you have the right
+ to give away copies of <command>centos-art.sh</command> script and
+ the organization of files it needs to work, that you receive
+ source code or else can get it if you want it, that you can change
+ this program or use pieces of it in new free programs, and that
+ you know you can do these things.</para>
+
+ <para>To make sure that everyone has such rights, we have to
+ forbid you to deprive anyone else of these rights. For example,
+ if you distribute copies of the <command>centos-art.sh</command>
+ script, you must give the recipients all the rights that you have.
+ You must make sure that they, too, receive or can get the source
+ code. And you must tell them their rights.</para>
+
+ <para>Also, for our own protection, we must make certain that
+ everyone finds out that there is no warranty for the
+ <command>centos-art.sh</command> script. If this program is
+ modified by someone else and passed on, we want their recipients
+ to know that what they have is not what we distributed, so that
+ any problems introduced by others will not reflect on our
+ reputation.</para>
+
+ <para>The <command>centos-art.sh</command> script is released as a
+ GPL work. Individual packages used by
+ <command>centos-art.sh</command> script include their own licenses
+ and the <command>centos-art.sh</command> script license applies to
+ all packages that it does not clash with. If there is a clash
+ between the <command>centos-art.sh</command> script license and
+ individual package licenses, the individual package license
+ applies instead.</para>
+
+ <para>The precise conditions of the license for the
+ <command>centos-art.sh</command> script are found in the <xref
+ linkend="licenses-gpl-chapter" />. This manual specifically is
+ covered by the <xref linkend="licenses-gfdl-chapter" />.</para>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Copying/section-2.docbook b/Manuals/Docbook/Entities/Repository/Copying/section-2.docbook
new file mode 100644
index 0000000..f5081a4
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Copying/section-2.docbook
@@ -0,0 +1,25 @@
+<?xml version="1.0"?>
+<sect1 id="repository-copying-section-2" xreflabel="The CentOS Brand" label="2.2">
+
+ <title>The CentOS Brand</title>
+
+ <para>The CentOS Brand () is the main visual manifestaion of The
+ CentOS Project. The CentOS Project uses The CentOS Brand to
+ connect all its visual manifestions (e.g., GNU/Linux
+ Distributions, Websites, Stationery, etc.) and, this way, it
+ provides recognition among other similar projects available on the
+ Internet.</para>
+
+ <para>Both The CentOS Brand and all the visual manifestations that
+ derivate from it are available for you to study and propose
+ improvement around a good citizen's will at The CentOS Community
+ environment, but you are not allowed to redistribute them
+ elsewhere, without the given permission of The CentOS
+ Project.</para>
+
+ <para>If you need to redistribute either The CentOS Brand or any
+ visual manifestation derived from it, write your intentions to the
+ The CentOS Developers mailing list
+ (centos-devel@centos.org).</para>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Directories/chapter.docbook b/Manuals/Docbook/Entities/Repository/Directories/chapter.docbook
new file mode 100644
index 0000000..eb5bc14
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Directories/chapter.docbook
@@ -0,0 +1,23 @@
+<?xml version="1.0"?>
+<chapter id="repository-directories-chapter" xreflabel="Directories">
+
+ <title>Directories</title>
+
+ <para>The CentOS Artwork Repository uses directories to organize
+ files and describe conceptual idea about corporate identity. Such
+ conceptual ideas are explained in each directory related
+ documentation entry.</para>
+
+ <para>In this chapter you'll learn what each directory inside The
+ CentOS Artwork Repository is for and so, how you can make use of
+ them. For that purpose, the following list of directories is
+ available for you to explore:</para>
+
+ &repository-directories-section-1;
+ &repository-directories-section-2;
+ &repository-directories-section-3;
+ &repository-directories-section-4;
+ &repository-directories-section-5;
+ &repository-directories-section-6;
+
+</chapter>
diff --git a/Manuals/Docbook/Entities/Repository/Directories/trunk.docbook b/Manuals/Docbook/Entities/Repository/Directories/trunk.docbook
new file mode 100644
index 0000000..b209cd2
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Directories/trunk.docbook
@@ -0,0 +1,5 @@
+<?xml version="1.0"?>
+<sect1 id="repository-directories-section-1" xreflabel="trunk" label="4.1">
+ <title><filename class="directory">trunk</filename></title>
+ <para></para>
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Directories/trunk/Identity.docbook b/Manuals/Docbook/Entities/Repository/Directories/trunk/Identity.docbook
new file mode 100644
index 0000000..8414fe4
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Directories/trunk/Identity.docbook
@@ -0,0 +1,260 @@
+<?xml version="1.0"?>
+<sect1 id="repository-directories-section-2" xreflabel="trunk/Identity" label="4.2">
+ <title><filename class="directory">trunk/Identity</filename></title>
+
+ <para>This directory implements The CentOS Project
+ <emphasis>corporate identity</emphasis> based on the The CentOS
+ Project <emphasis>mission</emphasis> and <emphasis>release
+ schema</emphasis>.</para>
+
+ <sect2 id="corporate-mission" xreflabel="The corporate mission" label="4.2.1">
+
+ <title>The corporate mission</title>
+
+ <para>The CentOS Project exists to provide The CentOS
+ Distribution. Additionally, The CentOS Project provides The
+ CentOS Web and The CentOS Showroom to support and promote the
+ existence of The CentOS Distribution, respectively.</para>
+
+ </sect2>
+
+ <sect2 id="corporate-identity" xreflabel="The corporate identity" label="4.2.2">
+ <title>The corporate identity</title>
+
+ <para>The CentOS Project corporate identity is the ``persona''
+ of the organization known as The CentOS Project. The CentOS
+ Project corporate identity plays a significant role in the way
+ The CentOS Project, as organization, presents itself to both
+ internal and external stakeholders. In general terms, The
+ CentOS Project corporate identity expresses the values and
+ ambitions of The CentOS Project organization, its business,
+ and its characteristics.</para>
+
+ <para>The CentOS Project corporate identity provides
+ visibility, recognizability, reputation, structure and
+ identification to The CentOS Project organization by means of
+ <emphasis>corporate design</emphasis>, <emphasis>corporate
+ communication</emphasis>, and <emphasis>corporate
+ behaviour</emphasis>.</para>
+
+ </sect2>
+
+ <sect2 id="corporate-design" xreflabel="The corporate design" label="4.2.3">
+
+ <title>The corporate design</title>
+
+ <para>The corporate design is focused on the effective
+ communication of corporate messages. Corporate messages are
+ all the information emitted from the corporation to a target
+ audience. In order for such communication to happen, it is
+ required to put the messages on a medium available for the
+ target audience to react upon. These media are know as
+ <emphasis>corporate manifestations</emphasis>, because the
+ corporation manifests its existence through them. The specific
+ way used by the corporation to set their messages on different
+ media is what the corporate design is about.</para>
+
+ <para>The amount of manifestations a corporation uses to
+ communicate its existence may very from one corporation to
+ another. In the very specific case of The CentOS Project, the
+ following corporate manifestations come to mind:</para>
+
+ <orderedlist>
+ <listitem>
+
+ <para>The CentOS Distribution — The CentOS
+ Distribution corporate manifestaion is made from SRPM
+ packages. There are packages that make a remarkable
+ use of images (e.g., Anaconda, Grub, Syslinux, Gdm,
+ Kdm, Gsplash, Ksplash, Rhgb, Firstboot, etc.),
+ packages that make a moderated use of images and
+ packages that don't use images at all. Also, there
+ are some packages that make use of text-based
+ information that need to be changed, too (e.g.,
+ release notes, eula, the welcome page of the web
+ browser, etc.), in order for The CentOS Project to
+ comply with upstream's redistribution guidelines. The
+ CentOS Distribution corporate manifestation focuses
+ its attention on SRPM packages that do use images in a
+ remarkable way, specifically those packages that
+ involve upstream branding, and those files with
+ text-based information that need to be changed. This
+ way, through image and text-based files, is
+ implemented the corporate design of The CentOS
+ Distribution corporate manifestations (i.e., all the
+ releases of the operating system).</para>
+
+ </listitem>
+ <listitem>
+
+ <para>The CentOS Web — This corporate
+ manifestation exists to support The CentOS
+ Distribution corporate manifestation. The CentOS Web
+ corporate manifestation covers web applications used
+ by The CentOS Project to manifest its existence on the
+ Internet. These web applications are free software
+ and come from different providers which distribute
+ their work with predefined visual styles. Frequently,
+ these predefined visual styles have no visual relation
+ among themselves and introduce some visual
+ contraditions when they all are put together. These
+ visual contraditions need to be removed in order to
+ comply with The CentOS Project corporate structure
+ guidelines.</para>
+
+ </listitem>
+ <listitem>
+
+ <para>The CentOS Showroom — This corporate
+ manifestation exists to promote The CentOS
+ Distribution. The CentOS Showroom corporate
+ manifestation covers industrial production of objects
+ branded by The CentOS Project (e.g., clothes,
+ stationery and installation media). These branded
+ objects are for distribution on social events and/or
+ shops. They provide a way of promotion and a route
+ for commercialization that may help to aliviate The
+ CentOS Project expenses (e.g., hosting, servers,
+ full-time-developers, etc.), in a similar way as
+ donations may do.</para>
+
+ </listitem>
+ </orderedlist>
+
+ <para>The corporate manifestations above seem to cover all the
+ media required by The CentOS Project, as organization, to show
+ its existence. However, other corporate manifestations could
+ be added in the future, if needed, to cover different areas
+ like building, offices, transportation and whaterver medium
+ The CentOS Project thouches to show its existence.</para>
+
+ </sect2>
+
+ <sect2 id="corporate-communication" xreflabel="The corporate
+ communication" label="4.2.4">
+
+ <title>The corporate communication</title>
+
+ <para> The CentOS Project corporate communication is based on
+ <emphasis>community communication</emphasis> and takes place
+ through the following avenues:
+
+ <itemizedlist>
+ <listitem><para>The CentOS Chat (#centos, #centos-social},
+#centos-devel on irc.freenode.net)</para></listitem>
+ <listitem><para>The CentOS Mailing Lists (<ulink url="http://lists.centos.org/" />).</para></listitem>
+ <listitem><para>The CentOS Forums (<ulink url="http://forums.centos.org/" />).</para></listitem>
+ <listitem><para>The CentOS Wiki (<ulink url="http://wiki.centos.org/" />).</para></listitem>
+ <listitem><para>Social events, interviews, conferences, etc.</para></listitem>
+ </itemizedlist>
+
+ </para>
+
+ </sect2>
+
+ <sect2 id="corporate-behaviour" xreflabel="The corporate behaviour"
+ label="4.2.5">
+
+ <title>The corporate behaviour</title>
+
+ <para>The CentOS Project corporate behaviour is based on
+ <emphasis>community behaviour</emphasis> which take place in
+ <xref linkend="corporate-communication" />.</para>
+
+ </sect2>
+
+ <sect2 id="corporate-structure" xreflabel="The corporate structure"
+ label="4.2.6">
+
+ <title>The corporate structure</title>
+
+ <para> The CentOS Project corporate structure is based on
+ a <emphasis>monolithic corporate visual identity
+ structure</emphasis>. In this configuration, one unique
+ name and one unique visual style is used in all corporate
+ manifestations of The CentOS Project.</para>
+
+ <para>In a monolithic corporate visual identity structure,
+ internal and external stakeholders feel a strong sensation
+ of uniformity, orientation, and identification with the
+ organization. No matter if you are visiting web sites,
+ using the distribution, or acting on social events, the
+ one unique name and one unique visual style connects them
+ all to say: <emphasis>Hey! we are all part of The CentOS
+ Project</emphasis>.</para>
+
+ <para>Other corporate structures for The CentOS Project
+ have been considered as well. Such is the case of
+ producing one different visual style for each major
+ release of The CentOS Distribution. This structure isn't
+ inconvenient at all, but some visual contradictions could
+ be introduced if it isn't applied correctly and we need to
+ be aware of it. To apply it correctly, we need to know
+ what The CentOS Project is made of.</para>
+
+ <para>The CentOS Project, as organization, is mainly made
+ of (but not limited to) three corporate manifestions: The
+ CentOS Distribution, The CentOS Web and The CentOS
+ Showroom. Inside The CentOS Distribution corporate
+ manifestations, The CentOS Project maintains near to four
+ different major releases of The CentOS Distribution (e.g.,
+ the operating system), parallely in time. However, inside
+ The CentOS Web visual manifestations, the content is
+ produced for no specific release information (e.g., there
+ is no a complete web site for each major release of The
+ CentOS Distribution individually, but one web site to
+ cover them all). Likewise, the content produced in The
+ CentOS Showroom is created for no release-specific at all,
+ but for The CentOS Project in general.</para>
+
+ <para>In order to produce the correct corporate structure
+ for The CentOS Project, we need to concider all the
+ corporate manifestations The CentOS Project is made of,
+ not just one of them. If one different visual style is
+ used for each major release of The CentOS Distribution,
+ which one of those different visual styles would be used
+ to cover the remaining visual manifestations The CentOS
+ Project is made of (e.g., The CentOS Web and The CentOS
+ Showroom)?</para>
+
+ <para>Probably you are thinking, that's right, but The
+ CentOS Brand connects them all already, why would we need
+ to join them up into the same visual style too, isn't it
+ more work to do, and harder to maintain?</para>
+
+ <para>Harder to maintain, more work to do, probably.
+ Specially when you consider that The CentOS Project has
+ proven stability and consistency through time and, that,
+ certainly, didn't come through swinging magical wands or
+ something but hardly working out to automate tasks and
+ providing maintainance through time. Said that, we
+ consider that The CentOS Project corporate structure must
+ be consequent with such stability and consistency
+ tradition, beyond the work it might require initially. It
+ is true that The CentOS Brand does connect all the visual
+ manifestations it is present on, but that connection would
+ be stronger if one unique visual style backups it, too.
+ In fact, whatever thing you do to strength the visual
+ connection among The CentOS Project corporate
+ manifestations would be very good in favor of The CentOS
+ Project recognition.</para>
+
+ <para>Obviously, having just one visual style in all
+ corporate manifestations for eternity would be a very
+ boring thing and would give the impression of a visually
+ dead project. So, there is no problem on creating a brand
+ new visual style for each new major release of The CentOS
+ Distribution, in order to refresh The CentOS Distribution
+ visual style; the problem itself is in not propagating the
+ brand new visual style created for the new release of The
+ CentOS Distribution to all other visual manifestations The
+ CentOS Project is made of, in a way The CentOS Project
+ could be recognized no matter what corporate manifestation
+ be in front of us. Such lack of uniformity is what
+ introduces the visual contradition we are precisely trying
+ to solve by mean of themes production in the CentOS
+ Artwork Repository.</para>
+
+ </sect2>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Directories/trunk/Identity/Models.docbook b/Manuals/Docbook/Entities/Repository/Directories/trunk/Identity/Models.docbook
new file mode 100644
index 0000000..9abd711
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Directories/trunk/Identity/Models.docbook
@@ -0,0 +1,5 @@
+<?xml version="1.0"?>
+<sect1 id="repository-directories-section-3" xreflabel="trunk/Identity/Models" label="4.3">
+ <title><filename class="directory">trunk/Identity/Models</filename></title>
+ <para></para>
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Directories/trunk/Identity/Models/Themes.docbook b/Manuals/Docbook/Entities/Repository/Directories/trunk/Identity/Models/Themes.docbook
new file mode 100644
index 0000000..f6fc57f
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Directories/trunk/Identity/Models/Themes.docbook
@@ -0,0 +1,32 @@
+<?xml version="1.0"?>
+<sect1 id="repository-directories-section-4" xreflabel="trunk/Identity/Models/Themes" label="4.4">
+
+ <title><filename class="directory">trunk/Identity/Models/Themes</filename></title>
+
+ <para>This directory implements the concept of <emphasis>themes'
+ design models</emphasis>.</para>
+
+ <para>Themes' design models provide the structural part of images
+ (e.g., dimensions, translation markers, position of each element
+ on the visible area, etc.) required by
+ <command>centos-art.sh</command> to perform theme rendition. The
+ provide the modeling characteristics for all the different visual
+ manifestations a theme is made of. Using themes' design models
+ reduce the time needed for propagating an artistic motif to
+ different visual manifestations.</para>
+
+ <para>In this directory, themes' design models are organized by
+ name. There is one directory for each theme's design model. Each
+ design model directory must be named as specified in <xref
+ linkend="repository-usage-section-3" />. Inside themes' design
+ models directories, there is one directory for each visual
+ manifestions a theme is made of. These directories are named
+ <emphasis>visual manifestation directories</emphasis> and contain
+ one or more SVG files to describe the visual structure of that
+ visual manifestion.</para>
+
+ <para>Themes' design models are <acronym>SVG</acronym> files and
+ can be localized using the <code>locale</code> functionality of
+ <command>centos-art.sh</command> script.</para>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Directories/trunk/Identity/Models/Themes/Default.docbook b/Manuals/Docbook/Entities/Repository/Directories/trunk/Identity/Models/Themes/Default.docbook
new file mode 100644
index 0000000..deb4f77
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Directories/trunk/Identity/Models/Themes/Default.docbook
@@ -0,0 +1,16 @@
+<?xml version="1.0"?>
+<sect1 id="repository-directories-section-5" xreflabel="trunk/Identity/Models/Themes/Default" label="4.5">
+
+ <title><filename class="directory">trunk/Identity/Models/Themes/Default</filename></title>
+
+ <para>This directory implements the concept of <emphasis>themes'
+ default design models</emphasis>.</para>
+
+ <para>Themes' default design models provide the common structural
+ information (e.g., image dimensions, translation markers,
+ trademark position, etc.) the <command>centos-art.sh</command>
+ script uses to produce images when no other design model is
+ specified through the <option>--theme-model</option> option at
+ rendition time.</para>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Directories/trunk/Manuals.docbook b/Manuals/Docbook/Entities/Repository/Directories/trunk/Manuals.docbook
new file mode 100644
index 0000000..f3099b6
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Directories/trunk/Manuals.docbook
@@ -0,0 +1,5 @@
+<?xml version="1.0"?>
+<sect1 id="repository-directories-section-6" xreflabel="trunk/Manuals" label="4.6">
+ <title><filename class="directory">trunk/Manuals</filename></title>
+ <para></para>
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/History/chapter.docbook b/Manuals/Docbook/Entities/Repository/History/chapter.docbook
new file mode 100644
index 0000000..5b5e486
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/History/chapter.docbook
@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<chapter id="repository-history-chapter" xreflabel="History">
+
+ <title>History</title>
+
+ <para>This chapter describes, briefly, where we've been and where
+ we're going to with the CentOS Artwork Repository.</para>
+
+ &repository-history-section-1;
+ &repository-history-section-2;
+ &repository-history-section-3;
+ &repository-history-section-4;
+
+</chapter>
diff --git a/Manuals/Docbook/Entities/Repository/History/section-1.docbook b/Manuals/Docbook/Entities/Repository/History/section-1.docbook
new file mode 100644
index 0000000..59ebc75
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/History/section-1.docbook
@@ -0,0 +1,32 @@
+<?xml version="1.0"?>
+<sect1 id="repository-history-section-1" label="1.1">
+
+ <title>2008</title>
+
+ <para>The CentOS Artwork Repository started at <ulink
+ url="mailto:centos-devel@centos.org">CentOS Developers mailing
+ list</ulink> during a discussion about how to automate the slide
+ images of Anaconda. In such discussion, Ralph Angenendt rose up
+ his hand to ask: Do you have something to show?</para>
+
+ <para>To answer the question, Alain Reguera Delgado suggested a
+ bash script which combined SVG and SED files in order to produce
+ PNG images in different languages —together with the
+ proposition of creating a Subversion repository where translations
+ and image production could be distributed inside The CentOS
+ Community—.</para>
+
+ <para>Karanbirn Sighn considered the idea intresting and provided
+ the infrastructure necessary to support the effort. This way the
+ <ulink url="https://projects.centos.org/trac/artwork/">CentOS
+ Artwork SIG</ulink> and the <ulink
+ url="https://projects.centos.org/svn/artwork/">CentOS Artwork
+ Repository</ulink> were officially created.</para>
+
+ <para>Once the CentOS Artwork Repository was available, Alain
+ Reguera Delagdo uploaded the bash script for rendering Anaconda
+ slides; Ralph Angenendt documented it very well; and people
+ started to download working copies of CentOS Artwork Repository to
+ produce slide images in their own languages.</para>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/History/section-2.docbook b/Manuals/Docbook/Entities/Repository/History/section-2.docbook
new file mode 100644
index 0000000..a7dc742
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/History/section-2.docbook
@@ -0,0 +1,47 @@
+<?xml version="1.0"?>
+<sect1 id="repository-history-section-2" label="1.2">
+
+ <title>2009</title>
+
+ <para>The rendition script was at a very rustic state where only
+ slide images could be produced, so it was redesigned to extend the
+ image production to other areas, not just slide images. In this
+ configuration, one SVG file was used as input to produce a
+ translated instance of it which, in turn, was used to produce one
+ translated PNG image as output. The SVG translated instance was
+ created through SED replacement commands. The translated PNG image
+ was created from the SVG translated instance using Inkscape
+ command-line interface.</para>
+
+ <para>The rendition script was named
+ <quote>render.sh</quote>.</para>
+
+ <para>The repository directory structure was prepared to receive
+ the rendition script using design templates and translation files
+ in the same location. There was one directory structure for each
+ artwork that needed to be produced. In this configuration, if you
+ would want to produce the same artwork with a different visual
+ style or structure, it was needed to create a new directory
+ structure for it because both the image structure and the image
+ visual style were together in the design template.</para>
+
+ <para>The rendition script was moved to a common place and linked
+ from different directory structures. There was no need to have the
+ same code in different directory structures if it could be in just
+ one place and then be linked from different locations.</para>
+
+ <para>The concepts about corporate identity began to be
+ considered. As referece, it was used the book <quote>Corporate
+ Identity</quote> by Wally Olins (1989) and Wikipedia (<ulink
+ url="http://en.wikipedia.org/Corporate_identity" />). This way,
+ the rendition script main's goal becomes to: automate production
+ of a monolithic corporate visual identity structure, based on the
+ mission and the release schema of The CentOS Project.</para>
+
+ <para>The directory structures started to be documented inside the
+ repository using text files without markup. Later, documentation
+ in flat text files was moved to LaTeX format and this way
+ <quote>The CentOS Artwork Repository Manual</quote> started to
+ take form.</para>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/History/section-3.docbook b/Manuals/Docbook/Entities/Repository/History/section-3.docbook
new file mode 100644
index 0000000..43d2181
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/History/section-3.docbook
@@ -0,0 +1,51 @@
+<?xml version="1.0"?>
+<sect1 id="repository-history-section-3" label="1.3">
+
+ <title>2010</title>
+
+ <para>The rendition script changed its name from
+ <command>render.sh</command> to <command>centos-art.sh</command>
+ and became a collection of functionalities where rendition was
+ just one among others (e.g., documenting and localizing).</para>
+
+ <para>The <command>centos-art.sh</command> was created to organize
+ automation of most frequent tasks inside the repository. There
+ was no need to have links all around the repository if a
+ command-line interface could be created (through symbolic links,
+ in the <filename class="directory">~/bin</filename> directory) and
+ be called anywhere inside the repository as it would be a regular
+ command.</para>
+
+ <para>Inside <command>centos-art.sh</command>, functionalities
+ started to get identified and separated one another. For example,
+ when images were rendered, there was no need to load
+ functionalities related to documentation manual. This layout moved
+ us onto common functionalities and specific functionalities inside
+ <command>centos-art.sh</command> script. Common functionalities
+ are loaded when <command>centos-art.sh</command> script is
+ initiated and are available to specific functionalities.</para>
+
+ <para>The <command>centos-art.sh</command> script was redesigned
+ to handle command-line options trough <command>getopt</command>
+ option parser.</para>
+
+ <para>The repository directory structure was updated to improve
+ the implementation of concepts related to corporate visual
+ identity. Specially in the area related to themes which were
+ divided into <emphasis>design models</emphasis> and
+ <emphasis>artistic motifs</emphasis> to eliminate the content
+ duplication produced by having both image structure and image
+ visual style in the same file. Now, themes are produced as result
+ of arbitrary combinations of both design models (structures) and
+ artistic motifs (visual styles).</para>
+
+ <para>In the documentation area, the documentation files in LaTeX
+ format were migrated to Texinfo format. In this configuration,
+ each directory structure in the repository has a documentation
+ entry associated in a Texinfo structure which can be read, edited
+ and administered (e.g., renamed, deleted, copied) interactively
+ throuch <command>centos-art.sh</command>. Additionally, the
+ <command>texi2html</command> program was used to produced XHTML
+ output customized by CSS from The CentOS Webenv.</para>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/History/section-4.docbook b/Manuals/Docbook/Entities/Repository/History/section-4.docbook
new file mode 100644
index 0000000..eeeffdc
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/History/section-4.docbook
@@ -0,0 +1,37 @@
+<?xml version="1.0"?>
+<sect1 id="repository-history-section-4" label="1.4">
+
+ <title>2011</title>
+
+ <para>The <command>centos-art.sh</command> script was redesigned
+ to start translating SVG and other XML-based files (e.g., XHTML
+ and Docbook files) through the <command>xml2po</command> program
+ and shell scripts files (e.g., Bash scripts) through GNU
+ <command>gettext</command> tools. This configuration provided a
+ stronger interface for graphic designers, translators and
+ programmers to produce localized content. The SED files are no
+ longer used to handle translations.</para>
+
+ <para>Improve option parsing through
+ <command>getopt</command>.</para>
+
+ <para>Consolidate the <code>render</code>, <code>help</code> and
+ <code>locale</code> functionalities as the most frequent tasks
+ performed inside the repository. Additionally, the
+ <code>prepare</code> and <code>tuneup</code> functionalities are
+ maintained as useful tasks.</para>
+
+ <para>The <command>centos-art.sh</command> script is updated to
+ organize functionalities in two groups: <quote>the administrative
+ functionalities</quote> and <quote>the productive
+ functionalities</quote>. The administrative functionalities cover
+ actions like: copying, deleting and renaming directory structures
+ inside the repository. Also, preparing your workstation for using
+ <command>centos-art.sh</command> script, making backups of the
+ distribution theme currently installed, installing themes created
+ inside repository and restoring themes from backup. On the other
+ hand, the productive functionalities cover actions like: content
+ rendition, content localization, content documentation and content
+ maintainance.</para>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Usage/chapter.docbook b/Manuals/Docbook/Entities/Repository/Usage/chapter.docbook
new file mode 100644
index 0000000..aaa2edc
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Usage/chapter.docbook
@@ -0,0 +1,30 @@
+<?xml version="1.0"?>
+<chapter id="repository-usage-chapter">
+
+ <title>Usage convenctions</title>
+
+ <para>The CentOS Artwork Repository is supported by <ulink
+ url="http://subversion.tigris.org/">Subversion</ulink>, a version
+ control system which allows you to keep old versions of files and
+ directories (usually source code), keep a log of who, when, and
+ why changes occurred, etc., like CVS, RCS or SCCS.</para>
+
+ <para>When using Subversion there is one "source repository" and
+ many "working copies" of that source repository. The working
+ copies are independent one another, can be distributed all around
+ the world and provide a local place for designers, documentors,
+ translators and programmers to perform their work in a
+ descentralized way. The source repository, on the other hand,
+ provides a central place for all independent working copies to
+ interchange data and provides the information required to permit
+ extracting previous versions of files at any time.</para>
+
+ &repository-usage-section-1;
+ &repository-usage-section-2;
+ &repository-usage-section-3;
+ &repository-usage-section-4;
+ &repository-usage-section-5;
+ &repository-usage-section-6;
+ &repository-usage-section-7;
+
+</chapter>
diff --git a/Manuals/Docbook/Entities/Repository/Usage/section-1.docbook b/Manuals/Docbook/Entities/Repository/Usage/section-1.docbook
new file mode 100644
index 0000000..024c597
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Usage/section-1.docbook
@@ -0,0 +1,49 @@
+<?xml version="1.0"?>
+<sect1 id="repository-usage-section-1" xreflabel="Policy" label="3.1">
+
+ <title>Policy</title>
+
+ <para>The CentOS Artwork Repository is a collaborative tool that
+ anyone can have access to. However, changing that tool in any form
+ is something that should be requested in the <ulink
+ url="mailto:centos-devel@centos.org">CentOS Developers mailing
+ list</ulink>. Generally, people download working copies from
+ CentOS Artwork Repository, study the repository organization, make
+ some changes in their working copies, make some tests to verify
+ such changes do work the way expected and finally request access
+ to commit them up to the CentOS Artwork Repository (i.e., the
+ source repository) for others to benefit from them.</para>
+
+ <para>Once you've received access to commit your changes, there is
+ no need for you to request permission again to commit other
+ changes from your working copy to CentOS Artwork Repository as
+ long as you behave as a <emphasis>good cooperating
+ citizen</emphasis>. Otherwise, your rights to commit changes might
+ be temporarly revoked or completly banished.</para>
+
+ <para>As a good cooperating citizen one understand of a person who
+ respects the work already done by others and share ideas with
+ authors before changing relevant parts of their work, specially in
+ situations when the access required to realize the changes has
+ been granted already. Of course, there is a time when
+ conversation has taken place, the paths has been traced and
+ changing the work is so obvious that there is no need for you to
+ talk about it; that's because you already did, you already built
+ the trust to keep going. Anyway, the mailing list mentioned above
+ is available for sharing ideas in a way that good relationship
+ between community citizens could be constantly balanced.</para>
+
+ <para>The relationship between community citizens is monitored by
+ repository administrators. Repository administrators are
+ responsible of granting everything goes the way it needs to go in
+ order for the CentOS Artwork Repository to accomplish its mission
+ which is: to provide a colaborative tool for The CentOS Community
+ where The CentOS Project Corporate Identity is built and
+ maintained by The CentOS Community itself.</para>
+
+ <para>It is also important to remember that all source files
+ inside CentOS Artwork Repository should comply the terms of <xref
+ linkend="licenses-gpl-chapter" /> in order for them to remain
+ inside the repository.</para>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Usage/section-2.docbook b/Manuals/Docbook/Entities/Repository/Usage/section-2.docbook
new file mode 100644
index 0000000..2b414a3
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Usage/section-2.docbook
@@ -0,0 +1,10 @@
+<?xml verion="1.0"?>
+<sect1 id="repository-usage-section-2" xreflabel="Organization" label="3.2">
+
+ <title>Organization</title>
+
+ <para>The CentOS Artwork Repository organization is described in
+ the chapter <xref linkend="repository-directories-chapter"
+ />.</para>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Usage/section-3.docbook b/Manuals/Docbook/Entities/Repository/Usage/section-3.docbook
new file mode 100644
index 0000000..1d0ded6
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Usage/section-3.docbook
@@ -0,0 +1,17 @@
+<?xml version="1.0"?>
+<sect1 id="repository-usage-section-3" xreflabel="File names" label="3.3">
+
+ <title>File names</title>
+
+ <para>Inside the CentOS Artwork Repository, file names are all
+ written in lowercase (e.g., <filename>01-welcome.png</filename>,
+ <filename>splash.png</filename>,
+ <filename>anaconda_header.png</filename>, etc.) and directory
+ names are all written capitalized (e.g., <filename
+ role="directory">Identity</filename>, <filename
+ role="directory">Themes</filename>, <filename
+ role="directory">Motifs</filename>) and sometimes in cammel case
+ (e.g., <filename role="directory">TreeFlower</filename>, etc.).
+ </para>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Usage/section-4-1.docbook b/Manuals/Docbook/Entities/Repository/Usage/section-4-1.docbook
new file mode 100644
index 0000000..06c4c54
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Usage/section-4-1.docbook
@@ -0,0 +1,15 @@
+<?xml versio="1.0"?>
+<sect2 id="repository-usage-section-4-1" xreflabel="Graphic design" label="3.4.1">
+
+ <title>Graphic design</title>
+
+ <para>The graphic design work line exists to cover brand design,
+ typography design and themes design mainly. Additionally, some
+ auxiliar areas like icon design, illustration design, brushes
+ design, patterns designs and palettes of colors are also included
+ here for completeness.</para>
+
+ <para>The graphic design work line is organized in the <filename
+ class="directory">trunk/Identity</filename> directory.</para>
+
+</sect2>
diff --git a/Manuals/Docbook/Entities/Repository/Usage/section-4-2.docbook b/Manuals/Docbook/Entities/Repository/Usage/section-4-2.docbook
new file mode 100644
index 0000000..c063ad3
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Usage/section-4-2.docbook
@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<sect2 id="repository-usage-section-4-2" xreflabel="Graphic design" label="3.4.2">
+
+ <title>Documentation</title>
+
+ <para>The documentation work line exists to describe what each
+ directory inside the CentOS Artwork Repository is for, the
+ conceptual ideas behind them and, if possible, how automation
+ scripts make use of them.</para>
+
+ <para>The documentation work line is organized in the <filename
+ class="directory">trunk/Manuals</filename> directory.</para>
+
+</sect2>
diff --git a/Manuals/Docbook/Entities/Repository/Usage/section-4-3.docbook b/Manuals/Docbook/Entities/Repository/Usage/section-4-3.docbook
new file mode 100644
index 0000000..86f4f6d
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Usage/section-4-3.docbook
@@ -0,0 +1,14 @@
+<?xml version="1.0"?>
+<sect2 id="repository-usage-section-4-3" xreflabel="Graphic design" label="3.4.3">
+
+ <title>Localization</title>
+
+ <para>The localization work line exists to provide the translation
+ messages required to produce content in different languages.
+ Translation messages inside the repository are stored as portable
+ objects (e.g., .po, .pot) and machine objects (.mo).</para>
+
+ <para>The localization work line is organized in the <filename
+ class="directory">trunk/Locales</filename> directory.</para>
+
+</sect2>
diff --git a/Manuals/Docbook/Entities/Repository/Usage/section-4-4.docbook b/Manuals/Docbook/Entities/Repository/Usage/section-4-4.docbook
new file mode 100644
index 0000000..2675e81
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Usage/section-4-4.docbook
@@ -0,0 +1,18 @@
+<?xml version="1.0"?>
+<sect2 id="repository-usage-section-4-4" xreflabel="Graphic design" label="3.4.4">
+
+ <title>Automation</title>
+
+ <para>The automation work line exists to standardize content
+ production inside the working copies of CentOS Artwork Repository.
+ Here is developed the <command>centos-art.sh</command> script, a
+ bash script specially designed to automate most frequent tasks
+ (e.g., rendition, documentation and localization) inside the
+ repository. There is no need to type several tasks, time after
+ time, if they can be programmed into just one executable
+ script.</para>
+
+ <para>The automation work line is organized in the <filename
+ class="directory">trunk/Scripts</filename> directory.</para>
+
+</sect2>
diff --git a/Manuals/Docbook/Entities/Repository/Usage/section-4.docbook b/Manuals/Docbook/Entities/Repository/Usage/section-4.docbook
new file mode 100644
index 0000000..08f9d15
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Usage/section-4.docbook
@@ -0,0 +1,23 @@
+<?xml version="1.0"?>
+<sect1 id="repository-usage-section-4" xreflabel="Graphic design" label="3.4">
+
+ <title>Work lines</title>
+
+ <para>Inside CentOS Artwork Repository there are four major work
+ lines of production which are: graphic design, documentation,
+ localization and automation. These work lines describe different
+ areas of content production. Content production inside these
+ specific areas may vary as much as persons be working on them.
+ Producing content in too many different ways may result
+ innapropriate in a collaborative environment like CentOS Artwork
+ Repository where content produced in one area depends somehow from
+ content produced in another different area. So, a content
+ production standard is required for each available work
+ line.</para>
+
+ &repository-usage-section-4-1;
+ &repository-usage-section-4-2;
+ &repository-usage-section-4-3;
+ &repository-usage-section-4-4;
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Usage/section-5.docbook b/Manuals/Docbook/Entities/Repository/Usage/section-5.docbook
new file mode 100644
index 0000000..dc9613d
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Usage/section-5.docbook
@@ -0,0 +1,44 @@
+<?xml version="1.0"?>
+<sect1 id="repository-usage-section-5" xreflabel="Connection between directories" label="3.5">
+
+ <title>Connection between directories</title>
+
+ <para>In order for automation scripts to produce content inside
+ working copies of CentOS Artwork Repository, it is required that
+ all work lines be connected somehow. Using this connection,
+ automation scripts can know where to retrive the information they
+ need to work with (e.g., design model, translation messages,
+ output locations, etc.). This connection is built using two path
+ constructions named <emphasis>master paths</emphasis> and
+ <emphasis>auxiliar paths</emphasis>.</para>
+
+ <para>The master path points only to directories that contain
+ source files (e.g., SVG files) required to produce base content
+ (e.g., PNG files) through automation scripts. Each master path
+ inside the repository may have several auxiliar paths associated,
+ but auxiliar paths can only have one master path associated.
+ Master paths are organized under <filename
+ class="directory">trunk/Identity/Models</filename> directory
+ structure and auxiliar paths under <filename
+ class="directory">trunk/Identity/Images</filename>, <filename
+ class="directory">trunk/Locales</filename> and <filename
+ class="directory">trunk/Manuals</filename> directory
+ structures.</para>
+
+ <para>The auxiliar paths can point either to directories or files.
+ When an auxiliar path points to a directory, that directory
+ contains information that modifies somehow the content produced
+ from master paths (e.g., translation messages) or provides the
+ output information required to know where to store the content
+ produced from master path. When an auxiliar path points to a
+ file, that file has no other purpose but to document the master
+ path it refers to.</para>
+
+ <para>The relationship between auxiliar paths and master paths is
+ realized by combining the master path itself and the second level
+ directory structures of the repository. The master path is
+ considered the path identifier and the second level directory
+ structure taken from the repository is considered the common part
+ of the path where the path identifier is appended to.</para>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Usage/section-6.docbook b/Manuals/Docbook/Entities/Repository/Usage/section-6.docbook
new file mode 100644
index 0000000..59684cd
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Usage/section-6.docbook
@@ -0,0 +1,72 @@
+<?xml version="1.0"?>
+<sect1 id="repository-usage-section-6" xreflabel="Syncronizing path information" label="3.6">
+
+ <title>Syncronizing path information</title>
+
+ <para>Syncronizing path information is the action of keeping all
+ path information up to date in the repository. This action implies
+ both file movement and replacement of content inside files already
+ moved, in this very specific order. File movement is related to
+ actions like duplicate, delete and rename files and directories in
+ the repository. Replacement of content inside files is related to
+ replace information, path information in this case, inside files
+ in the repository.</para>
+
+ <para>The order followed to syncronize path information is
+ relevant because the versioned nature of the files we are working
+ with. We don't perform file content replacement first because that
+ would imply a repository change which will immediatly demmand a
+ commit in order for actions like duplicate, delete or rename to
+ take place. However, if we perform file movement first, it is
+ possible to commit both file moved and file content replacements
+ as if they were just one change. In this case the file content
+ replacement takes palce in the target location that have been
+ duplicated or renamed, not the one use as source location. This
+ configuration is specially useful when files are renamed (i.e.,
+ one file is copied from a source location to a target location and
+ then the source location of it is removed from repository).</para>
+
+ <warning><para>There is no support for URLs actions inside
+ <command>centos-art.sh</command> script. The
+ <command>centos-art.sh</command> script is designed to work with
+ local files inside the working copy only. If you need to perform
+ URL actions directly, use Subversion commands
+ instead.</para></warning>
+
+ <para>When one master path is changed it is required that all
+ related auxiliar paths be changed, too. This is required in order
+ for master paths to retain their relation with auxiliar paths.
+ This way, automation scripts are able to know where to retrive
+ translation messages from, where to store final output images to
+ and where to look for documentation. If relation between master
+ paths and auxiliar paths is lost, there is no way for automation
+ scripts to know where to retrive the information they need.</para>
+
+ <para>The auxiliar paths should never be modified under any reason
+ but to satisfy the relationship with the master path. Liberal
+ change of auxiliar paths may suppress the conceptual idea they
+ were initially created for; and certainly, automation scripts may
+ stop working as expected. The update direction to rename path
+ information must be from master path to auxiliar path and never
+ the opposite.</para>
+
+ <para>The relation between master and auxiliar paths is useful to
+ keep repository organized but introduce some complications when we
+ work with files that use master path information as reference to
+ build structural information. This is the case of repository
+ documentation manual source files where inclusions, menus, nodes
+ and cross references are built using master path information as
+ reference. Now, to see what kind of complication we are talking
+ about, consider what would happen to a structural definitions
+ (i.e., inlusions, menus, nodes and cross refereces) already set in
+ the manual from one master path that is suddenly renamed to
+ something different. If the path information is not syncronized,
+ at this point, we lose connection between the master path and the
+ auxiliar path created to store the related documentation entry, as
+ well as the related structural definitions that end up pointing to
+ a master path that no longer exist.</para>
+
+ <para>The syncronization of path information is aimed to solve
+ these kind of issues.</para>
+
+</sect1>
diff --git a/Manuals/Docbook/Entities/Repository/Usage/section-7.docbook b/Manuals/Docbook/Entities/Repository/Usage/section-7.docbook
new file mode 100644
index 0000000..6ab854b
--- /dev/null
+++ b/Manuals/Docbook/Entities/Repository/Usage/section-7.docbook
@@ -0,0 +1,75 @@
+<?xml version="1.0"?>
+<sect1 id="repository-usage-section-7" xreflabel="Syncronizing path information" label="3.7">
+
+ <title>Extending repository organization</title>
+
+ <para>Occasionly, you may find that new components of The CentOS
+ Project Corporate Identity need to be added to the repository in
+ order to work them out. If that is the case, the first question we
+ need to ask ourselves, before start to create directories blindly
+ all over, is: @emph{What is the right place to store it?}</para>
+
+ <para>The best place to find answers is in The CentOS Community
+ (see page @url{http://wiki.centos.org/GettingHelp}), but going
+ there with hands empty is not good idea. It may give the
+ impression you don't really care about. Instead, consider the
+ following suggestions to find your own comprehension in order to
+ make your own propositions based on it.</para>
+
+ <para>When extending respository structure it is very useful to
+ bear in mind The CentOS Project Corporate Identity Structure
+ (@pxref{Directories trunk Identity}) The CentOS Mission and The
+ CentOS Release Schema. The rest is just matter of choosing
+ appropriate names. It is also worth to know that each directory in
+ the repository responds to a conceptual idea that justifies its
+ existence.</para>
+
+ <para>To build a directory structure, you need to define the
+ conceptual idea first and later create the directory. There are
+ some locations inside the repository that already define some
+ concepts you probably want to reuse. For example,
+ @file{trunk/Identity/Images/Themes} to store theme artistic
+ motifs, @file{trunk/Identity/Models/Themes} to store theme design
+ models, @file{trunk/Manual} to store documentation files,
+ @file{trunk/Locales} to store translation messages,
+ @file{trunk/Scripts} to store automation scripts and so on.</para>
+
+ <para>To illustrate this desition process let's consider the
+ @file{trunk/Identity/Images/Themes/TreeFlower/3} directory
+ structure as example. This directory can be read as: the theme
+ development line of version @file{3} of @file{TreeFlower} artistic
+ motif. Additional, we can identify that artistic motifs are part
+ of themes as well as themes are part of The CentOS Project
+ Corporate Identity. These concepts are better described
+ independently in each documentation entry related to the directory
+ structure as it is respectively shown in the list of commands
+ bellow.
+
+ <itemizedlist>
+ <listitem>
+ <para><command>centos-art help --read turnk</command></para>
+ </listitem>
+ <listitem>
+ <para><command>centos-art help --read turnk/Identity</command></para>
+ </listitem>
+ <listitem>
+ <para><command>centos-art help --read turnk/Identity/Images</command></para>
+ </listitem>
+ <listitem>
+ <para><command>centos-art help --read turnk/Identity/Images/Themes</command></para>
+ </listitem>
+ <listitem>
+ <para><command>centos-art help --read turnk/Identity/Images/Themes/TreeFlower</command></para>
+ </listitem>
+ <listitem>
+ <para><command>centos-art help --read turnk/Identity/Images/Themes/TreeFlower/3</command></para>
+ </listitem>
+ </itemizedlist>
+
+ </para>
+
+ <para>The concepts behind other location can be found in the same
+ way described above, just change the path information used above
+ to the one you are trying to know concepts for.</para>
+
+</sect1>
diff --git a/Manuals/Docbook/Parts/Licenses.docbook b/Manuals/Docbook/Parts/Licenses.docbook
deleted file mode 100644
index 5a7534e..0000000
--- a/Manuals/Docbook/Parts/Licenses.docbook
+++ /dev/null
@@ -1,6 +0,0 @@
-<?xml version="1.0"?>
-<part>
- <title>Licenses</title>
- &license-gpl;
- &license-gfdl;
-</part>
diff --git a/Manuals/Docbook/Parts/Licenses/Gfdl.docbook b/Manuals/Docbook/Parts/Licenses/Gfdl.docbook
deleted file mode 100644
index e6dd831..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gfdl.docbook
+++ /dev/null
@@ -1,27 +0,0 @@
-<?xml version="1.0"?>
-<appendix id="licenses-gfdl-chapter" xreflabel="GNU Free Documentation License">
-
- <title>GNU Free Documentation License</title>
-
- <para>Version 1.2, November 2002</para>
-
- <para>Copyright © 2000, 2001, 2002 Free Software Foundation,
- Inc. 675 Mass Ave, Cambridge, MA 02139, USA</para>
-
- <para>Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.</para>
-
- &licenses-gfdl-preamble;
- &licenses-gfdl-applicability-and-definitions;
- &licenses-gfdl-verbatim-copying;
- &licenses-gfdl-copying-in-quantity;
- &licenses-gfdl-modifications;
- &licenses-gfdl-combining-documents;
- &licenses-gfdl-collection-of-documents;
- &licenses-gfdl-aggregation-with-independent-works;
- &licenses-gfdl-translations;
- &licenses-gfdl-termination;
- &licenses-gfdl-future-revisions-of-this-license;
- &licenses-gfdl-how-to-use-this-license;
-
-</appendix>
diff --git a/Manuals/Docbook/Parts/Licenses/Gfdl/aggregation-with-independent-workds.docbook b/Manuals/Docbook/Parts/Licenses/Gfdl/aggregation-with-independent-workds.docbook
deleted file mode 100644
index 2d4d4aa..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gfdl/aggregation-with-independent-workds.docbook
+++ /dev/null
@@ -1,25 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gfdl-section-8" xreflabel="Aggregation with independent works">
-
- <title>Aggregation with independent works</title>
-
- <para>A compilation of the Document or its derivatives with other
- separate and independent documents or works, in or on a volume of
- a storage or distribution medium, is called an
- <quote>aggregate</quote> if the copyright resulting from the
- compilation is not used to limit the legal rights of the
- compilation's users beyond what the individual works permit. When
- the Document is included in an aggregate, this License does not
- apply to the other works in the aggregate which are not themselves
- derivative works of the Document.</para>
-
- <para>If the Cover Text requirement of section <xref
- linkend="licenses-gfdl-section-4" /> is applicable to these copies
- of the Document, then if the Document is less than one half of the
- entire aggregate, the Document's Cover Texts may be placed on
- covers that bracket the Document within the aggregate, or the
- electronic equivalent of covers if the Document is in electronic
- form. Otherwise they must appear on printed covers that bracket
- the whole aggregate.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gfdl/applicability-and-definitions.docbook b/Manuals/Docbook/Parts/Licenses/Gfdl/applicability-and-definitions.docbook
deleted file mode 100644
index 9adb858..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gfdl/applicability-and-definitions.docbook
+++ /dev/null
@@ -1,102 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gfdl-section-2" xreflabel="Applicability and definitions">
-
- <title>Applicability and definitions</title>
-
- <para>This License applies to any manual or other work, in any
- medium, that contains a notice placed by the copyright holder
- saying it can be distributed under the terms of this License.
- Such a notice grants a world-wide, royalty-free license, unlimited
- in duration, to use that work under the conditions stated herein.
- The <quote>Document</quote>, below, refers to any such manual or
- work. Any member of the public is a licensee, and is addressed as
- <quote>you</quote>. You accept the license if you copy, modify or
- distribute the work in a way requiring permission under copyright
- law.</para>
-
- <para>A <quote>Modified Version</quote> of the Document means any
- work containing the Document or a portion of it, either copied
- verbatim, or with modifications and/or translated into another
- language.</para>
-
- <para>A <quote>Secondary Section</quote> is a named appendix or a
- front-matter section of the Document that deals exclusively with
- the relationship of the publishers or authors of the Document to
- the Document's overall subject (or to related matters) and
- contains nothing that could fall directly within that overall
- subject. (Thus, if the Document is in part a textbook of
- mathematics, a Secondary Section may not explain any mathematics.)
- The relationship could be a matter of historical connection with
- the subject or with related matters, or of legal, commercial,
- philosophical, ethical or political position regarding
- them.</para>
-
- <para>The <quote>Invariant Sections</quote> are certain Secondary Sections
- whose titles are designated, as being those of Invariant Sections,
- in the notice that says that the Document is released under this
- License. If a section does not fit the above definition of
- Secondary then it is not allowed to be designated as Invariant.
- The Document may contain zero Invariant Sections. If the Document
- does not identify any Invariant Sections then there are
- none.</para>
-
- <para>The <quote>Cover Texts</quote> are certain short passages of text that
- are listed, as Front-Cover Texts or Back-Cover Texts, in the
- notice that says that the Document is released under this License.
- A Front-Cover Text may be at most 5 words, and a Back-Cover Text
- may be at most 25 words.</para>
-
- <para>A <quote>Transparent</quote> copy of the Document means a
- machine-readable copy, represented in a format whose specification
- is available to the general public, that is suitable for revising
- the document straightforwardly with generic text editors or (for
- images composed of pixels) generic paint programs or (for
- drawings) some widely available drawing editor, and that is
- suitable for input to text formatters or for automatic translation
- to a variety of formats suitable for input to text formatters. A
- copy made in an otherwise Transparent file format whose markup, or
- absence of markup, has been arranged to thwart or discourage
- subsequent modification by readers is not Transparent. An image
- format is not Transparent if used for any substantial amount of
- text. A copy that is not <quote>Transparent</quote> is called
- <quote>Opaque</quote>.</para>
-
- <para>Examples of suitable formats for Transparent copies include
- plain ASCII without markup, Texinfo input format, LaTeX input
- format, SGML or XML using a publicly available DTD, and
- standard-conforming simple HTML, PostScript or PDF designed for
- human modification. Examples of transparent image formats include
- PNG, XCF and JPG. Opaque formats include proprietary formats that
- can be read and edited only by proprietary word processors, SGML
- or XML for which the DTD and/or processing tools are not generally
- available, and the machine-generated HTML, PostScript or PDF
- produced by some word processors for output purposes only.</para>
-
- <para>The <quote>Title Page</quote> means, for a printed book, the
- title page itself, plus such following pages as are needed to
- hold, legibly, the material this License requires to appear in the
- title page. For works in formats which do not have any title page
- as such, <quote>Title Page</quote> means the text near the most
- prominent appearance of the work's title, preceding the beginning
- of the body of the text.</para>
-
- <para>A section <quote>Entitled XYZ</quote> means a named subunit
- of the Document whose title either is precisely XYZ or contains
- XYZ in parentheses following text that translates XYZ in another
- language. (Here XYZ stands for a specific section name mentioned
- below, such as <quote>Acknowledgements</quote>,
- <quote>Dedications</quote>, <quote>Endorsements</quote>, or
- <quote>History</quote>.) To <quote>Preserve the Title</quote> of
- such a section when you modify the Document means that it remains
- a section <quote>Entitled XYZ</quote> according to this
- definition.</para>
-
- <para>The Document may include Warranty Disclaimers next to the
- notice which states that this License applies to the Document.
- These Warranty Disclaimers are considered to be included by
- reference in this License, but only as regards disclaiming
- warranties: any other implication that these Warranty Disclaimers
- may have is void and has no effect on the meaning of this
- License.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gfdl/collection-of-documents.docbook b/Manuals/Docbook/Parts/Licenses/Gfdl/collection-of-documents.docbook
deleted file mode 100644
index 9396f9b..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gfdl/collection-of-documents.docbook
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gfdl-section-7" xreflabel="Collection of documents">
-
- <title>Collection of documents</title>
-
- <para>You may make a collection consisting of the Document and
- other documents released under this License, and replace the
- individual copies of this License in the various documents with a
- single copy that is included in the collection, provided that you
- follow the rules of this License for verbatim copying of each of
- the documents in all other respects.</para>
-
- <para>You may extract a single document from such a collection,
- and distribute it individually under this License, provided you
- insert a copy of this License into the extracted document, and
- follow this License in all other respects regarding verbatim
- copying of that document.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gfdl/combining-documents.docbook b/Manuals/Docbook/Parts/Licenses/Gfdl/combining-documents.docbook
deleted file mode 100644
index 71bbcb3..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gfdl/combining-documents.docbook
+++ /dev/null
@@ -1,32 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gfdl-section-6" xreflabel="Combining documents">
-
- <title>Combining documents</title>
-
- <para>You may combine the Document with other documents released
- under this License, under the terms defined in section <xref
- linkend="licenses-gfdl-section-5" /> above for modified versions,
- provided that you include in the combination all of the Invariant
- Sections of all of the original documents, unmodified, and list
- them all as Invariant Sections of your combined work in its
- license notice, and that you preserve all their Warranty
- Disclaimers.</para>
-
- <para>The combined work need only contain one copy of this
- License, and multiple identical Invariant Sections may be replaced
- with a single copy. If there are multiple Invariant Sections with
- the same name but different contents, make the title of each such
- section unique by adding at the end of it, in parentheses, the
- name of the original author or publisher of that section if known,
- or else a unique number. Make the same adjustment to the section
- titles in the list of Invariant Sections in the license notice of
- the combined work.</para>
-
- <para>In the combination, you must combine any sections Entitled
- <quote>History</quote> in the various original documents, forming
- one section Entitled <quote>History</quote>; likewise combine any
- sections Entitled <quote>Acknowledgements</quote>, and any
- sections Entitled <quote>Dedications</quote>. You must delete all
- sections Entitled <quote>Endorsements</quote>.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gfdl/copying-in-quantity.docbook b/Manuals/Docbook/Parts/Licenses/Gfdl/copying-in-quantity.docbook
deleted file mode 100644
index 5bb583e..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gfdl/copying-in-quantity.docbook
+++ /dev/null
@@ -1,44 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gfdl-section-4" xreflabel="Copying in quantity">
-
- <title>Copying in quantity</title>
-
- <para>If you publish printed copies (or copies in media that
- commonly have printed covers) of the Document, numbering more than
- 100, and the Document's license notice requires Cover Texts, you
- must enclose the copies in covers that carry, clearly and legibly,
- all these Cover Texts: Front-Cover Texts on the front cover, and
- Back-Cover Texts on the back cover. Both covers must also clearly
- and legibly identify you as the publisher of these copies. The
- front cover must present the full title with all words of the
- title equally prominent and visible. You may add other material
- on the covers in addition. Copying with changes limited to the
- covers, as long as they preserve the title of the Document and
- satisfy these conditions, can be treated as verbatim copying in
- other respects.</para>
-
- <para>If the required texts for either cover are too voluminous to
- fit legibly, you should put the first ones listed (as many as fit
- reasonably) on the actual cover, and continue the rest onto
- adjacent pages.</para>
-
- <para>If you publish or distribute Opaque copies of the Document
- numbering more than 100, you must either include a
- machine-readable Transparent copy along with each Opaque copy, or
- state in or with each Opaque copy a computer-network location from
- which the general network-using public has access to download
- using public-standard network protocols a complete Transparent
- copy of the Document, free of added material. If you use the
- latter option, you must take reasonably prudent steps, when you
- begin distribution of Opaque copies in quantity, to ensure that
- this Transparent copy will remain thus accessible at the stated
- location until at least one year after the last time you
- distribute an Opaque copy (directly or through your agents or
- retailers) of that edition to the public.</para>
-
- <para>It is requested, but not required, that you contact the
- authors of the Document well before redistributing any large
- number of copies, to give them a chance to provide you with an
- updated version of the Document.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gfdl/future-revisions-of-this-license.docbook b/Manuals/Docbook/Parts/Licenses/Gfdl/future-revisions-of-this-license.docbook
deleted file mode 100644
index a97aa94..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gfdl/future-revisions-of-this-license.docbook
+++ /dev/null
@@ -1,22 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gfdl-section-11" xreflabel="Future Revisions of this License">
-
- <title>Future Revisions of this License</title>
-
- <para>The Free Software Foundation may publish new, revised
- versions of the GNU Free Documentation License from time to time.
- Such new versions will be similar in spirit to the present
- version, but may differ in detail to address new problems or
- concerns. See <ulink url="http://www.gnu.org/copyleft/" />.</para>
-
- <para>Each version of the License is given a distinguishing
- version number. If the Document specifies that a particular
- numbered version of this License <quote>or any later version</quote> applies
- to it, you have the option of following the terms and conditions
- either of that specified version or of any later version that has
- been published (not as a draft) by the Free Software Foundation.
- If the Document does not specify a version number of this License,
- you may choose any version ever published (not as a draft) by the
- Free Software Foundation.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gfdl/how-to-use-this-license.docbook b/Manuals/Docbook/Parts/Licenses/Gfdl/how-to-use-this-license.docbook
deleted file mode 100644
index 5e94411..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gfdl/how-to-use-this-license.docbook
+++ /dev/null
@@ -1,40 +0,0 @@
-<?xmll version="1.0"?>
-<section id="licenses-gfdl-section-12" xreflabel="How to use this License for your documents">
-
- <title>How to use this License for your documents</title>
-
- <para>To use this License in a document you have written, include
- a copy of the License in the document and put the following
- copyright and license notices just after the title page:</para>
-
- <programlisting>
- Copyright (C) YEAR YOUR NAME.
-
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation License,
- Version 1.2 or any later version published by the Free Software
- Foundation; with no Invariant Sections, no Front-Cover Texts, and
- no Back-Cover Texts. A copy of the license is included in the
- section entitled <quote>GNU Free Documentation License</quote>.
- </programlisting>
-
- <para>If you have Invariant Sections, Front-Cover Texts and
- Back-Cover Texts, replace the <quote>with...Texts</quote>. line with
- this:</para>
-
- <programlisting>
- with the Invariant Sections being LIST THEIR TITLES, with the
- Front-Cover Texts being LIST, and with the Back-Cover Texts being
- LIST.
- </programlisting>
-
- <para>If you have Invariant Sections without Cover Texts, or some
- other combination of the three, merge those two alternatives to
- suit the situation.</para>
-
- <para>If your document contains nontrivial examples of program
- code, we recommend releasing these examples in parallel under your
- choice of free software license, such as the GNU General Public
- License, to permit their use in free software.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gfdl/modifications.docbook b/Manuals/Docbook/Parts/Licenses/Gfdl/modifications.docbook
deleted file mode 100644
index 1ff6399..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gfdl/modifications.docbook
+++ /dev/null
@@ -1,148 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gfdl-section-5" xreflabel="Modification">
-
- <title>Modifications</title>
-
- <para>You may copy and distribute a Modified Version of the
- Document under the conditions of sections <xref
- linkend="licenses-gfdl-section-3" /> and <xref
- linkend="licenses-gfdl-section-4" /> above, provided that you
- release the Modified Version under precisely this License, with
- the Modified Version filling the role of the Document, thus
- licensing distribution and modification of the Modified Version to
- whoever possesses a copy of it. In addition, you must do these
- things in the Modified Version:
-
- <orderedlist numeration="upperalpha">
-
- <listitem>
- <para> Use in the Title Page (and on the covers, if any) a
- title distinct from that of the Document, and from those
- of previous versions (which should, if there were any, be
- listed in the History section of the Document). You may
- use the same title as a previous version if the original
- publisher of that version gives permission.</para>
- </listitem>
-
- <listitem>
- <para>List on the Title Page, as authors, one or more
- persons or entities responsible for authorship of the
- modifications in the Modified Version, together with at
- least five of the principal authors of the Document (all
- of its principal authors, if it has fewer than five),
- unless they release you from this requirement.</para>
- </listitem>
-
- <listitem>
- <para>State on the Title page the name of the publisher of
- the Modified Version, as the publisher.</para>
- </listitem>
-
- <listitem>
- <para>Preserve all the copyright notices of the
- Document.</para>
- </listitem>
-
- <listitem>
- <para>Add an appropriate copyright notice for your
- modifications adjacent to the other copyright
- notices.</para>
- </listitem>
-
- <listitem>
- <para>Include, immediately after the copyright notices, a
- license notice giving the public permission to use the
- Modified Version under the terms of this License, in the
- form shown in the Addendum below.</para>
- </listitem>
- <listitem>
- <para>Preserve in that license notice the full lists of
- Invariant Sections and required Cover Texts given in the
- Document's license notice.</para>
- </listitem>
- <listitem>
- <para>Include an unaltered copy of this License.</para>
- </listitem>
- <listitem>
- <para>Preserve the section Entitled
- <quote>History</quote>, Preserve its Title, and add to it
- an item stating at least the title, year, new authors, and
- publisher of the Modified Version as given on the Title
- Page. If there is no section Entitled
- <quote>History</quote> in the Document, create one stating
- the title, year, authors, and publisher of the Document as
- given on its Title Page, then add an item describing the
- Modified Version as stated in the previous
- sentence.</para>
- </listitem>
- <listitem>
- <para>Preserve the network location, if any, given in the
- Document for public access to a Transparent copy of the
- Document, and likewise the network locations given in the
- Document for previous versions it was based on. These may
- be placed in the <quote>History</quote> section. You may
- omit a network location for a work that was published at
- least four years before the Document itself, or if the
- original publisher of the version it refers to gives
- permission.</para>
- </listitem>
- <listitem>
- <para>For any section Entitled
- <quote>Acknowledgements</quote> or
- <quote>Dedications</quote>, Preserve the Title of the
- section, and preserve in the section all the substance and
- tone of each of the contributor acknowledgements and/or
- dedications given therein.</para>
- </listitem>
- <listitem>
- <para>Preserve all the Invariant Sections of the Document,
- unaltered in their text and in their titles. Section
- numbers or the equivalent are not considered part of the
- section titles.</para>
- </listitem>
- <listitem>
- <para>Delete any section Entitled <quote>Endorsements</quote>. Such
- a section may not be included in the Modified
- Version.</para>
- </listitem>
- <listitem>
- <para>Do not retitle any existing section to be Entitled
- <quote>Endorsements</quote> or to conflict in title with
- any Invariant Section.</para>
- </listitem>
- <listitem>
- <para>Preserve any Warranty Disclaimers.</para>
- </listitem>
- </orderedlist>
- </para>
-
- <para>If the Modified Version includes new front-matter sections
- or appendices that qualify as Secondary Sections and contain no
- material copied from the Document, you may at your option
- designate some or all of these sections as invariant. To do this,
- add their titles to the list of Invariant Sections in the Modified
- Version's license notice. These titles must be distinct from any
- other section titles.</para>
-
- <para>You may add a section Entitled <quote>Endorsements</quote>,
- provided it contains nothing but endorsements of your Modified
- Version by various parties–for example, statements of peer
- review or that the text has been approved by an organization as
- the authoritative definition of a standard.</para>
-
- <para>You may add a passage of up to five words as a Front-Cover
- Text, and a passage of up to 25 words as a Back-Cover Text, to the
- end of the list of Cover Texts in the Modified Version. Only one
- passage of Front-Cover Text and one of Back-Cover Text may be
- added by (or through arrangements made by) any one entity. If the
- Document already includes a cover text for the same cover,
- previously added by you or by arrangement made by the same entity
- you are acting on behalf of, you may not add another; but you may
- replace the old one, on explicit permission from the previous
- publisher that added the old one.</para>
-
- <para>The author(s) and publisher(s) of the Document do not by
- this License give permission to use their names for publicity for
- or to assert or imply endorsement of any Modified Version.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gfdl/preamble.docbook b/Manuals/Docbook/Parts/Licenses/Gfdl/preamble.docbook
deleted file mode 100644
index a10aba0..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gfdl/preamble.docbook
+++ /dev/null
@@ -1,30 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gfdl-section-1" xreflabel="Preamble">
-
- <title>Preamble</title>
-
- <para>The purpose of this License is to make a manual, textbook,
- or other functional and useful document <quote>free</quote> in the
- sense of freedom: to assure everyone the effective freedom to copy
- and redistribute it, with or without modifying it, either
- commercially or noncommercially. Secondarily, this License
- preserves for the author and publisher a way to get credit for
- their work, while not being considered responsible for
- modifications made by others.</para>
-
- <para>This License is a kind of <quote>copyleft</quote>, which
- means that derivative works of the document must themselves be
- free in the same sense. It complements the <xref
- linkend="licenses-gfdl-chapter" />, which is a copyleft license
- designed for free software.</para>
-
- <para>We have designed this License in order to use it for manuals
- for free software, because free software needs free documentation:
- a free program should come with manuals providing the same
- freedoms that the software does. But this License is not limited
- to software manuals; it can be used for any textual work,
- regardless of subject matter or whether it is published as a
- printed book. We recommend this License principally for works
- whose purpose is instruction or reference.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gfdl/termination.docbook b/Manuals/Docbook/Parts/Licenses/Gfdl/termination.docbook
deleted file mode 100644
index 453d644..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gfdl/termination.docbook
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gfdl-section-10" xreflabel="Tremination">
-
- <title>Termination</title>
-
- <para>You may not copy, modify, sublicense, or distribute the
- Document except as expressly provided for under this License. Any
- other attempt to copy, modify, sublicense or distribute the
- Document is void, and will automatically terminate your rights
- under this License. However, parties who have received copies, or
- rights, from you under this License will not have their licenses
- terminated so long as such parties remain in full
- compliance.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gfdl/translations.docbook b/Manuals/Docbook/Parts/Licenses/Gfdl/translations.docbook
deleted file mode 100644
index 53eb02a..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gfdl/translations.docbook
+++ /dev/null
@@ -1,27 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gfdl-section-9" xreflabel="Translations">
-
- <title>Translations</title>
-
- <para>Translation is considered a kind of modification, so you may
- distribute translations of the Document under the terms of section
- <xref linkend="licenses-gfdl-section-5"/>. Replacing Invariant
- Sections with translations requires special permission from their
- copyright holders, but you may include translations of some or all
- Invariant Sections in addition to the original versions of these
- Invariant Sections. You may include a translation of this
- License, and all the license notices in the Document, and any
- Warranty Disclaimers, provided that you also include the original
- English version of this License and the original versions of those
- notices and disclaimers. In case of a disagreement between the
- translation and the original version of this License or a notice
- or disclaimer, the original version will prevail.</para>
-
- <para>If a section in the Document is Entitled
- <quote>Acknowledgements</quote>, <quote>Dedications</quote>, or
- <quote>History</quote>, the requirement (section <xref
- linkend="licenses-gfdl-section-5" />) to Preserve its Title
- (section <xref linkend="licenses-gfdl-section-2" />) will
- typically require changing the actual title.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gfdl/verbatim-copying.docbook b/Manuals/Docbook/Parts/Licenses/Gfdl/verbatim-copying.docbook
deleted file mode 100644
index 5d2647a..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gfdl/verbatim-copying.docbook
+++ /dev/null
@@ -1,21 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gfdl-section-3" xreflabel="Verbatim copying">
-
- <title>Verbatim copying</title>
-
- <para>You may copy and distribute the Document in any medium,
- either commercially or noncommercially, provided that this
- License, the copyright notices, and the license notice saying this
- License applies to the Document are reproduced in all copies, and
- that you add no other conditions whatsoever to those of this
- License. You may not use technical measures to obstruct or
- control the reading or further copying of the copies you make or
- distribute. However, you may accept compensation in exchange for
- copies. If you distribute a large enough number of copies you
- must also follow the conditions in section <xref
- linkend="licenses-gfdl-section-4" />.</para>
-
- <para>You may also lend copies, under the same conditions stated
- above, and you may publicly display copies.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl.docbook b/Manuals/Docbook/Parts/Licenses/Gpl.docbook
deleted file mode 100644
index 21b56ae..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl.docbook
+++ /dev/null
@@ -1,31 +0,0 @@
-<?xml version="1.0"?>
-<appendix id="licenses-gpl-chapter" xreflabel="GNU General Public License">
-
- <title>GNU General Public License</title>
-
- <para>Version 2, June 1991</para>
-
- <para>Copyright © 1989, 1991 Free Software Foundation, Inc.
- 675 Mass Ave, Cambridge, MA 02139, USA</para>
-
- <para>Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.</para>
-
- &licenses-gpl-preamble;
- &licenses-gpl-terms-and-conditions;
- &licenses-gpl-terms-and-conditions-section-0;
- &licenses-gpl-terms-and-conditions-section-1;
- &licenses-gpl-terms-and-conditions-section-2;
- &licenses-gpl-terms-and-conditions-section-3;
- &licenses-gpl-terms-and-conditions-section-4;
- &licenses-gpl-terms-and-conditions-section-5;
- &licenses-gpl-terms-and-conditions-section-6;
- &licenses-gpl-terms-and-conditions-section-7;
- &licenses-gpl-terms-and-conditions-section-8;
- &licenses-gpl-terms-and-conditions-section-9;
- &licenses-gpl-terms-and-conditions-section-10;
- &licenses-gpl-terms-and-conditions-section-11;
- &licenses-gpl-terms-and-conditions-section-12;
- &licenses-gpl-how-to-apply-this-license;
-
-</appendix>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions.docbook
deleted file mode 100644
index d1a255b..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions.docbook
+++ /dev/null
@@ -1,20 +0,0 @@
-<?xml version="1.0"?>
-<section>
-
- <title>Terms and Conditions for Copying, Distribution and Modification</title>
-
- &licenses-gpl-section-2-0;
- &licenses-gpl-section-2-1;
- &licenses-gpl-section-2-2;
- &licenses-gpl-section-2-3;
- &licenses-gpl-section-2-4;
- &licenses-gpl-section-2-5;
- &licenses-gpl-section-2-6;
- &licenses-gpl-section-2-7;
- &licenses-gpl-section-2-8;
- &licenses-gpl-section-2-9;
- &licenses-gpl-section-2-10;
- &licenses-gpl-section-2-11;
- &licenses-gpl-section-2-12;
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-0.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-0.docbook
deleted file mode 100644
index 6561990..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-0.docbook
+++ /dev/null
@@ -1,26 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gpl-section-2-0" xreflabel="Section 0">
-
- <title>Section 0</title>
-
- <para>This License applies to any program or other work which
- contains a notice placed by the copyright holder saying it may be
- distributed under the terms of this General Public License. The
- <quote>Program</quote>, below, refers to any such program or work,
- and a <quote>work based on the Program</quote> means either the
- Program or any derivative work under copyright law: that is to
- say, a work containing the Program or a portion of it, either
- verbatim or with modifications and/or translated into another
- language. (Hereinafter, translation is included without
- limitation in the term <quote>modification</quote>.) Each
- licensee is addressed as <quote>you</quote>.</para>
-
- <para>Activities other than copying, distribution and modification
- are not covered by this License; they are outside its scope. The
- act of running the Program is not restricted, and the output from
- the Program is covered only if its contents constitute a work
- based on the Program (independent of having been made by running
- the Program). Whether that is true depends on what the Program
- does.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-1.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-1.docbook
deleted file mode 100644
index f5d0b88..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-1.docbook
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gpl-section-2-1" xreflabel="Section 1">
-
- <title>Section 1</title>
-
- <para>You may copy and distribute verbatim copies of the Program's
- source code as you receive it, in any medium, provided that you
- conspicuously and appropriately publish on each copy an
- appropriate copyright notice and disclaimer of warranty; keep
- intact all the notices that refer to this License and to the
- absence of any warranty; and give any other recipients of the
- Program a copy of this License along with the Program.</para>
-
- <para>You may charge a fee for the physical act of transferring a
- copy, and you may at your option offer warranty protection in
- exchange for a fee.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-10.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-10.docbook
deleted file mode 100644
index 36839e0..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-10.docbook
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gpl-section-2-10" xreflabel="Section 10">
-
- <title>Section 10</title>
-
- <para>If you wish to incorporate parts of the Program into other
- free programs whose distribution conditions are different, write
- to the author to ask for permission. For software which is
- copyrighted by the Free Software Foundation, write to the Free
- Software Foundation; we sometimes make exceptions for this. Our
- decision will be guided by the two goals of preserving the free
- status of all derivatives of our free software and of promoting
- the sharing and reuse of software generally.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-11.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-11.docbook
deleted file mode 100644
index 3ddc003..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-11.docbook
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gpl-section-11" xreflabel="NO WARRANTY">
-
- <title>NO WARRANTY</title>
- <subtitle>Section 11</subtitle>
-
- <para>BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
- WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
- LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
- HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM <quote>AS IS</quote> WITHOUT
- WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT
- NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
- FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
- QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
- PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY
- SERVICING, REPAIR OR CORRECTION.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-12.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-12.docbook
deleted file mode 100644
index 3881698..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-12.docbook
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gpl-section-12" xreflabel="Section 12">
-
- <title>Section 12</title>
-
- <para>IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO
- IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY
- MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE
- LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
- INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
- INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
- DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU
- OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY
- OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
- ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.</para>
-
- <para><emphasis>End of Terms and Conditions.</emphasis></para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-2.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-2.docbook
deleted file mode 100644
index 0d8f5c6..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-2.docbook
+++ /dev/null
@@ -1,70 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gpl-section-2-2" xreflabel="Section 2">
-
- <title>Section 2</title>
-
- <para>You may modify your copy or copies of the Program or any
- portion of it, thus forming a work based on the Program, and copy
- and distribute such modifications or work under the terms of
- Section 1 above, provided that you also meet all of these
- conditions:</para>
-
- <orderedlist numeration="loweralpha">
- <listitem>
- <para>You must cause the modified files to carry prominent
- notices stating that you changed the files and the date of
- any change.</para>
- </listitem>
- <listitem>
- <para>You must cause any work that you distribute or
- publish, that in whole or in part contains or is derived
- from the Program or any part thereof, to be licensed as a
- whole at no charge to all third parties under the terms of
- this License.</para>
- </listitem>
- <listitem>
- <para>If the modified program normally reads commands
- interactively when run, you must cause it, when started
- running for such interactive use in the most ordinary way,
- to print or display an announcement including an
- appropriate copyright notice and a notice that there is no
- warranty (or else, saying that you provide a warranty) and
- that users may redistribute the program under these
- conditions, and telling the user how to view a copy of
- this License.
-
- <note>
- <title>Exception</title>
- <para>
- If the Program itself is interactive but does not
- normally print such an announcement, your work based
- on the Program is not required to print an
- announcement.
- </para>
- </note>
- </para>
- </listitem>
- </orderedlist>
-
- <para>These requirements apply to the modified work as a whole.
- If identifiable sections of that work are not derived from the
- Program, and can be reasonably considered independent and separate
- works in themselves, then this License, and its terms, do not
- apply to those sections when you distribute them as separate
- works. But when you distribute the same sections as part of a
- whole which is a work based on the Program, the distribution of
- the whole must be on the terms of this License, whose permissions
- for other licensees extend to the entire whole, and thus to each
- and every part regardless of who wrote it.</para>
-
- <para>Thus, it is not the intent of this section to claim rights
- or contest your rights to work written entirely by you; rather,
- the intent is to exercise the right to control the distribution of
- derivative or collective works based on the Program.</para>
-
- <para>In addition, mere aggregation of another work not based on
- the Program with the Program (or with a work based on the Program)
- on a volume of a storage or distribution medium does not bring the
- other work under the scope of this License.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-3.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-3.docbook
deleted file mode 100644
index a78568e..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-3.docbook
+++ /dev/null
@@ -1,60 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gpl-section-2-3" xreflabel="Section 3">
-
- <title>Section 3</title>
-
- <para>You may copy and distribute the Program (or a work based on
- it, under Section 2) in object code or executable form under the
- terms of Sections 1 and 2 above provided that you also do one of
- the following:
-
- <orderedlist numeration="loweralpha">
- <listitem>
-
- <para> Accompany it with the complete corresponding
- machine-readable source code, which must be distributed
- under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,</para>
-
- </listitem>
- <listitem>
-
- <para>Accompany it with a written offer, valid for at
- least three years, to give any third party, for a charge
- no more than your cost of physically performing source
- distribution, a complete machine-readable copy of the
- corresponding source code, to be distributed under the
- terms of Sections 1 and 2 above on a medium customarily
- used for software interchange; or,</para>
-
- <para>Accompany it with the information you received as
- to the offer to distribute corresponding source code.
- (This alternative is allowed only for noncommercial
- distribution and only if you received the program in
- object code or executable form with such an offer, in
- accord with Subsection b above.)</para>
-
- </listitem>
- </orderedlist>
- </para>
-
- <para>The source code for a work means the preferred form of the
- work for making modifications to it. For an executable work,
- complete source code means all the source code for all modules it
- contains, plus any associated interface definition files, plus the
- scripts used to control compilation and installation of the
- executable. However, as a special exception, the source code
- distributed need not include anything that is normally distributed
- (in either source or binary form) with the major components
- (compiler, kernel, and so on) of the operating system on which the
- executable runs, unless that component itself accompanies the
- executable.</para>
-
- <para>If distribution of executable or object code is made by
- offering access to copy from a designated place, then offering
- equivalent access to copy the source code from the same place
- counts as distribution of the source code, even though third
- parties are not compelled to copy the source along with the object
- code.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-4.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-4.docbook
deleted file mode 100644
index 0123586..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-4.docbook
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gpl-section-2-4" xreflabel="Section 4">
-
- <title>Section 4</title>
-
- <para>You may not copy, modify, sublicense, or distribute the
- Program except as expressly provided under this License. Any
- attempt otherwise to copy, modify, sublicense or distribute the
- Program is void, and will automatically terminate your rights
- under this License. However, parties who have received copies, or
- rights, from you under this License will not have their licenses
- terminated so long as such parties remain in full
- compliance.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-5.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-5.docbook
deleted file mode 100644
index f52db23..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-5.docbook
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gpl-section-2-5" xreflabel="Section 5">
-
- <title>Section 5</title>
-
- <para>You are not required to accept this License, since you have
- not signed it. However, nothing else grants you permission to
- modify or distribute the Program or its derivative works. These
- actions are prohibited by law if you do not accept this License.
- Therefore, by modifying or distributing the Program (or any work
- based on the Program), you indicate your acceptance of this
- License to do so, and all its terms and conditions for copying,
- distributing or modifying the Program or works based on it.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-6.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-6.docbook
deleted file mode 100644
index 8222570..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-6.docbook
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gpl-section-2-6" xreflabel="Section 6">
-
- <title>Section 6</title>
-
- <para>Each time you redistribute the Program (or any work based on
- the Program), the recipient automatically receives a license from
- the original licensor to copy, distribute or modify the Program
- subject to these terms and conditions. You may not impose any
- further restrictions on the recipients' exercise of the rights
- granted herein. You are not responsible for enforcing compliance
- by third parties to this License.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-7.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-7.docbook
deleted file mode 100644
index 29a696e..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-7.docbook
+++ /dev/null
@@ -1,39 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gpl-section-2-7" xreflabel="Section 7">
-
- <title>Section 7</title>
-
- <para>If, as a consequence of a court judgment or allegation of
- patent infringement or for any other reason (not limited to patent
- issues), conditions are imposed on you (whether by court order,
- agreement or otherwise) that contradict the conditions of this
- License, they do not excuse you from the conditions of this
- License. If you cannot distribute so as to satisfy simultaneously
- your obligations under this License and any other pertinent
- obligations, then as a consequence you may not distribute the
- Program at all. For example, if a patent license would not permit
- royalty-free redistribution of the Program by all those who
- receive copies directly or indirectly through you, then the only
- way you could satisfy both it and this License would be to refrain
- entirely from distribution of the Program.</para>
-
- <para>If any portion of this section is held invalid or
- unenforceable under any particular circumstance, the balance of
- the section is intended to apply and the section as a whole is
- intended to apply in other circumstances.</para>
-
- <para>It is not the purpose of this section to induce you to
- infringe any patents or other property right claims or to contest
- validity of any such claims; this section has the sole purpose of
- protecting the integrity of the free software distribution system,
- which is implemented by public license practices. Many people
- have made generous contributions to the wide range of software
- distributed through that system in reliance on consistent
- application of that system; it is up to the author/donor to decide
- if he or she is willing to distribute software through any other
- system and a licensee cannot impose that choice.</para>
-
- <para>This section is intended to make thoroughly clear what is
- believed to be a consequence of the rest of this License.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-8.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-8.docbook
deleted file mode 100644
index a3b968d..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-8.docbook
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gpl-section-2-8" xreflabel="Section 8">
-
- <title>Section 8</title>
-
- <para>If the distribution and/or use of the Program is restricted
- in certain countries either by patents or by copyrighted
- interfaces, the original copyright holder who places the Program
- under this License may add an explicit geographical distribution
- limitation excluding those countries, so that distribution is
- permitted only in or among countries not thus excluded. In such
- case, this License incorporates the limitation as if written in
- the body of this License.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-9.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-9.docbook
deleted file mode 100644
index 0f98bfe..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/Terms-and-conditions/section-9.docbook
+++ /dev/null
@@ -1,20 +0,0 @@
-<?xml version="1.0"?>
-<section id="licenses-gpl-section-2-9" xreflabel="Section 9">
-
- <title>Section 9</title>
-
- <para>The Free Software Foundation may publish revised and/or new
- versions of the General Public License from time to time. Such
- new versions will be similar in spirit to the present version, but
- may differ in detail to address new problems or concerns.</para>
-
- <para>Each version is given a distinguishing version number. If
- the Program specifies a version number of this License which
- applies to it and <quote>any later version</quote>, you have the
- option of following the terms and conditions either of that
- version or of any later version published by the Free Software
- Foundation. If the Program does not specify a version number of
- this License, you may choose any version ever published by the
- Free Software Foundation.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/how-to-apply-this-license.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/how-to-apply-this-license.docbook
deleted file mode 100644
index 32d6c40..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/how-to-apply-this-license.docbook
+++ /dev/null
@@ -1,75 +0,0 @@
-<?xml version="1.0"?>
-<section>
-
- <title>How to Apply These Terms to Your New Programs</title>
-
- <para>If you develop a new program, and you want it to be of the
- greatest possible use to the public, the best way to achieve this
- is to make it free software which everyone can redistribute and
- change under these terms.</para>
-
- <para>To do so, attach the following notices to the program. It
- is safest to attach them to the start of each source file to most
- effectively convey the exclusion of warranty; and each file should
- have at least the <quote>copyright</quote> line and a pointer to
- where the full notice is found.</para>
-
- <programlisting>
- <one line to give the program's name and a brief idea of what it does.>
- Copyright (C) 19yy <name of author>
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
- </programlisting>
-
- <para>Also add information on how to contact you by electronic and
- paper mail.</para>
-
- <para>If the program is interactive, make it output a short notice
- like this when it starts in an interactive mode:</para>
-
- <programlisting>
- Gnomovision version 69, Copyright (C) 19yy name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
- </programlisting>
-
- <para>The hypothetical commands `show w' and `show c' should show
- the appropriate parts of the General Public License. Of course,
- the commands you use may be called something other than `show w'
- and `show c'; they could even be mouse-clicks or menu
- items–whatever suits your program.</para>
-
- <para>You should also get your employer (if you work as a
- programmer) or your school, if any, to sign a <quote>copyright
- disclaimer</quote> for the program, if necessary. Here is a sample;
- alter the names:</para>
-
- <programlisting>
- Yoyodyne, Inc., hereby disclaims all copyright interest in the program
- `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
- <signature of Ty Coon>, 1 April 1989
- Ty Coon, President of Vice
- </programlisting>
-
- <para>This General Public License does not permit incorporating
- your program into proprietary programs. If your program is a
- subroutine library, you may consider it more useful to permit
- linking proprietary applications with the library. If this is
- what you want to do, use the GNU Library General Public License
- instead of this License.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Licenses/Gpl/preamble.docbook b/Manuals/Docbook/Parts/Licenses/Gpl/preamble.docbook
deleted file mode 100644
index ce9d2cc..0000000
--- a/Manuals/Docbook/Parts/Licenses/Gpl/preamble.docbook
+++ /dev/null
@@ -1,57 +0,0 @@
-<?xml version="1.0"?>
-<section>
-
- <title>Preamble</title>
-
- <para>The licenses for most software are designed to take away
- your freedom to share and change it. By contrast, the GNU General
- Public License is intended to guarantee your freedom to share and
- change free software–to make sure the software is free for
- all its users. This General Public License applies to most of the
- Free Software Foundation's software and to any other program whose
- authors commit to using it. (Some other Free Software Foundation
- software is covered by the GNU Library General Public License
- instead.) You can apply it to your programs, too.</para>
-
- <para>When we speak of free software, we are referring to freedom,
- not price. Our General Public Licenses are designed to make sure
- that you have the freedom to distribute copies of free software
- (and charge for this service if you wish), that you receive source
- code or can get it if you want it, that you can change the
- software or use pieces of it in new free programs; and that you
- know you can do these things.</para>
-
- <para>To protect your rights, we need to make restrictions that
- forbid anyone to deny you these rights or to ask you to surrender
- the rights. These restrictions translate to certain
- responsibilities for you if you distribute copies of the software,
- or if you modify it.</para>
-
- <para>For example, if you distribute copies of such a program,
- whether gratis or for a fee, you must give the recipients all the
- rights that you have. You must make sure that they, too, receive
- or can get the source code. And you must show them these terms so
- they know their rights.</para>
-
- <para>We protect your rights with two steps: (1) copyright the
- software, and (2) offer you this license which gives you legal
- permission to copy, distribute and/or modify the software.</para>
-
- <para>Also, for each author's protection and ours, we want to make
- certain that everyone understands that there is no warranty for
- this free software. If the software is modified by someone else
- and passed on, we want its recipients to know that what they have
- is not the original, so that any problems introduced by others
- will not reflect on the original authors' reputations.</para>
-
- <para>Finally, any free program is threatened constantly by
- software patents. We wish to avoid the danger that redistributors
- of a free program will individually obtain patent licenses, in
- effect making the program proprietary. To prevent this, we have
- made it clear that any patent must be licensed for everyone's free
- use or not licensed at all.</para>
-
- <para>The precise terms and conditions for copying, distribution
- and modification follow.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Preface.docbook b/Manuals/Docbook/Parts/Preface.docbook
deleted file mode 100644
index 3090ff8..0000000
--- a/Manuals/Docbook/Parts/Preface.docbook
+++ /dev/null
@@ -1,34 +0,0 @@
-<?xml version="1.0"?>
-<preface>
-
- <title>Introduction</title>
-
- <para>Welcome to <emphasis>The CentOS Artwork Repository
- Manual</emphasis>.</para>
-
- <para>The CentOS Artwork Repository Manual describes how The
- CentOS Project Corporate Visual Identity is organized and produced
- inside the CentOS Artwork Repository (<ulink
- url="https://projects.centos.org/svn/artwork/" />). If you are
- looking for a comprehensive, task-oriented guide for understanding
- how The CentOS Project Corporate Visual Identity is produced, this
- is the manual for you.</para>
-
- <para>This manual discusses the following intermedite
- topics:
-
- <itemizedlist>
- <listitem><para>The CentOS Brand</para></listitem>
- <listitem><para>The CentOS Corporate Visual Structure</para></listitem>
- <listitem><para>The CentOS Corporate Visual Style</para></listitem>
- </itemizedlist></para>
-
- <para>This guide assumes you have a basic understanding of your
- CentOS system. If you need help with CentOS, refer to the help
- page on the CentOS Wiki (<ulink url="http://wiki.centos.org/Help"
- />) for a list of different places you can find help.</para>
-
- &preface-document-convenctions;
- &preface-send-in-your-feedback;
-
-</preface>
diff --git a/Manuals/Docbook/Parts/Preface/document-convenctions.docbook b/Manuals/Docbook/Parts/Preface/document-convenctions.docbook
deleted file mode 100644
index c58c66f..0000000
--- a/Manuals/Docbook/Parts/Preface/document-convenctions.docbook
+++ /dev/null
@@ -1,148 +0,0 @@
-<?xml version="1.0"?>
-<section>
-
- <title>Document convenctions</title>
-
- <para>In this manual the personal pronoun <emphasis>we</emphasis>
- is used to repesent <emphasis>The CentOS Artwork SIG</emphasis>,
- the group of persons that build The CentOS Project corporate
- visual identity through the CentOS Artwork Repository.</para>
-
- <para>In this manual, certain words are represented in different
- fonts, typefaces, sizes, and weights. This highlighting is
- systematic; different words are represented in the same style to
- indicate their inclusion in a specific category. The types of
- words that are represented this way include the following:</para>
-
- <glosslist>
- <glossentry>
- <glossterm><command>command</command></glossterm>
- <glossdef>
- <para> Linux commands (and other operating system
- commands, when used) are represented this way. This
- style should indicate to you that you can type the
- word or phrase on the command line and press Enter to
- invoke a command. Sometimes a command contains words
- that would be displayed in a different style on their
- own (such as file names). In these cases, they are
- considered to be part of the command, so the entire
- phrase is displayed as a command. For example:</para>
-
- <para>Use the <command>centos-art identity
- --render='path/to/dir'</command> command to produce
- contents inside the <filename
- class="directory">trunk/Identity</filename> directory
- structure.</para>
-
- </glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm><filename>file name</filename></glossterm>
- <glossdef>
- <para>File names, directory names, paths, and RPM
- package names are represented this way. This style
- indicates that a particular file or directory exists
- with that name on your system. Examples:</para>
-
- <para>The <filename>init.sh</filename> file in
- <filename
- class="directory">trunk/Scripts/Bash/Cli/</filename>
- directory is the initialization script, written in
- Bash, used to automate most of tasks in the
- repository.</para>
-
- <para>The <command>centos-art</command> command uses
- the <package>ImageMagick</package> RPM package to
- convert images from PNG format to other
- formats.</para>
-
- </glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm><keycap>key</keycap></glossterm>
- <glossdef>
- <para> A key on the keyboard is shown in this style.
- For example:</para>
-
- <para>To use <keycap>TAB</keycap> completion to list
- particular files in a directory, type @command{ls},
- then a character, and finally the Tab key. Your
- terminal displays the list of files in the working
- directory that begin with that character.</para>
- </glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm><keycombo action="simul"><keycap>key-combination</keycap></keycombo></glossterm>
- <glossdef>
- <para>A combination of keystrokes is represented in
- this way. For example:</para>
-
- <para>The <keycombo
- action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Backspace</keycap></keycombo>
- key combination exits your graphical session and
- returns you to the graphical login screen or the
- console.</para>
-
- </glossdef>
-
- </glossentry>
-
- <glossentry>
- <glossterm><computeroutput>computer output</computeroutput></glossterm>
- <glossdef>
- <para> Text in this style indicates text displayed to a
- shell prompt such as error messages and responses to
- commands. For example:</para>
-
- <para>The <command>ls</command> command displays the
- contents of a directory. For example:
-
- <programlisting>
-Config help_renameEntry.sh
-help_copyEntry.sh help_restoreCrossReferences.sh
-help_deleteCrossReferences.sh help_searchIndex.sh
- </programlisting>
-
- The output returned in response to the command (in this
- case, the contents of the directory) is shown in this
- style.</para>
- </glossdef>
- </glossentry>
- </glosslist>
-
- <para>Additionally, we use several different strategies to draw
- your attention to certain pieces of information. In order of
- urgency, these items are marked as a note, tip, important,
- caution, or warning. For example:</para>
-
- <note>
- <para>Remember that Linux is case sensitive. In other words, a
- rose is not a ROSE is not a rOsE.</para>
- </note>
-
- <tip>
- <para>The directory @file{/usr/share/doc/} contains additional
- documentation for packages installed on your system.</para>
- </tip>
-
- <important>
- <para>If you modify the DHCP configuration file, the changes
- do not take effect until you restart the DHCP daemon.</para>
- </important>
-
- <caution>
- <para>Do not perform routine tasks as root — use a
- regular user account unless you need to use the root account
- for system administration tasks.</para>
- </caution>
-
- <warning>
- <para>Be careful to remove only the necessary partitions.
- Removing other partitions could result in data loss or a
- corrupted system environment.</para>
- </warning>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Preface/send-in-your-feedback.docbook b/Manuals/Docbook/Parts/Preface/send-in-your-feedback.docbook
deleted file mode 100644
index b3dc889..0000000
--- a/Manuals/Docbook/Parts/Preface/send-in-your-feedback.docbook
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml version="1.0"?>
-<section>
-
- <title>Send in your feedback</title>
-
- <para> If you find an error in the <emphasis>CentOS Artwork
- Repository</emphasis>, or if you have thought of a way to make
- this manual better, we would like to hear from you! Share your
- suggestions in the appropriate mailing list
- (http://lists.centos.org/) and/or bug tracker
- (http://bugs.centos.org/).</para>
-
- <para>When you make suggestion, try to be as specific as possible.
- For example, if you have found an error in the manual, include the
- section number and some of the surrounding text so we can find it
- easily.</para>
-
-</section>
diff --git a/Manuals/Docbook/Parts/Repository.docbook b/Manuals/Docbook/Parts/Repository.docbook
deleted file mode 100644
index e8575d3..0000000
--- a/Manuals/Docbook/Parts/Repository.docbook
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<part>
- <title>The Repository</title>
-
- &repository-history;
- &repository-copying;
- &repository-usage;
- &repository-directories;
-
-</part>
diff --git a/Manuals/Docbook/Parts/Repository/Copying/chapter.docbook b/Manuals/Docbook/Parts/Repository/Copying/chapter.docbook
deleted file mode 100644
index aeffb79..0000000
--- a/Manuals/Docbook/Parts/Repository/Copying/chapter.docbook
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<chapter id="repository-copying-chapter" xreflabel="Copying">
-
- <title>Copying conditions</title>
-
- <para>Copyright © 2009, 2010, 2011 The CentOS Project</para>
- <para>Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.</para>
-
- &repository-copying-section-1;
- &repository-copying-section-2;
-
-</chapter>
diff --git a/Manuals/Docbook/Parts/Repository/Copying/section-1.docbook b/Manuals/Docbook/Parts/Repository/Copying/section-1.docbook
deleted file mode 100644
index 082c06d..0000000
--- a/Manuals/Docbook/Parts/Repository/Copying/section-1.docbook
+++ /dev/null
@@ -1,57 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-copying-section-1" xreflabel="Preamble" label="2.1">
-
- <title>Preamble</title>
-
- <para>The CentOS Artwork Repository organizes files in a very
- specific way to implement The CentOS Project corporate visual
- identity. This very specific organization of files must be
- considered part of <command>centos-art.sh</command> script, a bash
- script that automate most of the frequent tasks inside the
- repository.</para>
-
- <para>The <command>centos-art.sh</command> script and the
- organization of files it needs to work are not in the public
- domain; they are copyrighted and there are restrictions on their
- distribution, but these restrictions are designed to permit
- everything that a good cooperating citizen would want to do. What
- is not allowed is to try to prevent others from further sharing
- any version of this program that they might get from you.</para>
-
- <para>Specifically, we want to make sure that you have the right
- to give away copies of <command>centos-art.sh</command> script and
- the organization of files it needs to work, that you receive
- source code or else can get it if you want it, that you can change
- this program or use pieces of it in new free programs, and that
- you know you can do these things.</para>
-
- <para>To make sure that everyone has such rights, we have to
- forbid you to deprive anyone else of these rights. For example,
- if you distribute copies of the <command>centos-art.sh</command>
- script, you must give the recipients all the rights that you have.
- You must make sure that they, too, receive or can get the source
- code. And you must tell them their rights.</para>
-
- <para>Also, for our own protection, we must make certain that
- everyone finds out that there is no warranty for the
- <command>centos-art.sh</command> script. If this program is
- modified by someone else and passed on, we want their recipients
- to know that what they have is not what we distributed, so that
- any problems introduced by others will not reflect on our
- reputation.</para>
-
- <para>The <command>centos-art.sh</command> script is released as a
- GPL work. Individual packages used by
- <command>centos-art.sh</command> script include their own licenses
- and the <command>centos-art.sh</command> script license applies to
- all packages that it does not clash with. If there is a clash
- between the <command>centos-art.sh</command> script license and
- individual package licenses, the individual package license
- applies instead.</para>
-
- <para>The precise conditions of the license for the
- <command>centos-art.sh</command> script are found in the <xref
- linkend="licenses-gpl-chapter" />. This manual specifically is
- covered by the <xref linkend="licenses-gfdl-chapter" />.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Copying/section-2.docbook b/Manuals/Docbook/Parts/Repository/Copying/section-2.docbook
deleted file mode 100644
index f5081a4..0000000
--- a/Manuals/Docbook/Parts/Repository/Copying/section-2.docbook
+++ /dev/null
@@ -1,25 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-copying-section-2" xreflabel="The CentOS Brand" label="2.2">
-
- <title>The CentOS Brand</title>
-
- <para>The CentOS Brand () is the main visual manifestaion of The
- CentOS Project. The CentOS Project uses The CentOS Brand to
- connect all its visual manifestions (e.g., GNU/Linux
- Distributions, Websites, Stationery, etc.) and, this way, it
- provides recognition among other similar projects available on the
- Internet.</para>
-
- <para>Both The CentOS Brand and all the visual manifestations that
- derivate from it are available for you to study and propose
- improvement around a good citizen's will at The CentOS Community
- environment, but you are not allowed to redistribute them
- elsewhere, without the given permission of The CentOS
- Project.</para>
-
- <para>If you need to redistribute either The CentOS Brand or any
- visual manifestation derived from it, write your intentions to the
- The CentOS Developers mailing list
- (centos-devel@centos.org).</para>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Directories/chapter.docbook b/Manuals/Docbook/Parts/Repository/Directories/chapter.docbook
deleted file mode 100644
index eb5bc14..0000000
--- a/Manuals/Docbook/Parts/Repository/Directories/chapter.docbook
+++ /dev/null
@@ -1,23 +0,0 @@
-<?xml version="1.0"?>
-<chapter id="repository-directories-chapter" xreflabel="Directories">
-
- <title>Directories</title>
-
- <para>The CentOS Artwork Repository uses directories to organize
- files and describe conceptual idea about corporate identity. Such
- conceptual ideas are explained in each directory related
- documentation entry.</para>
-
- <para>In this chapter you'll learn what each directory inside The
- CentOS Artwork Repository is for and so, how you can make use of
- them. For that purpose, the following list of directories is
- available for you to explore:</para>
-
- &repository-directories-section-1;
- &repository-directories-section-2;
- &repository-directories-section-3;
- &repository-directories-section-4;
- &repository-directories-section-5;
- &repository-directories-section-6;
-
-</chapter>
diff --git a/Manuals/Docbook/Parts/Repository/Directories/trunk.docbook b/Manuals/Docbook/Parts/Repository/Directories/trunk.docbook
deleted file mode 100644
index b209cd2..0000000
--- a/Manuals/Docbook/Parts/Repository/Directories/trunk.docbook
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-directories-section-1" xreflabel="trunk" label="4.1">
- <title><filename class="directory">trunk</filename></title>
- <para></para>
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Directories/trunk/Identity.docbook b/Manuals/Docbook/Parts/Repository/Directories/trunk/Identity.docbook
deleted file mode 100644
index 8414fe4..0000000
--- a/Manuals/Docbook/Parts/Repository/Directories/trunk/Identity.docbook
+++ /dev/null
@@ -1,260 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-directories-section-2" xreflabel="trunk/Identity" label="4.2">
- <title><filename class="directory">trunk/Identity</filename></title>
-
- <para>This directory implements The CentOS Project
- <emphasis>corporate identity</emphasis> based on the The CentOS
- Project <emphasis>mission</emphasis> and <emphasis>release
- schema</emphasis>.</para>
-
- <sect2 id="corporate-mission" xreflabel="The corporate mission" label="4.2.1">
-
- <title>The corporate mission</title>
-
- <para>The CentOS Project exists to provide The CentOS
- Distribution. Additionally, The CentOS Project provides The
- CentOS Web and The CentOS Showroom to support and promote the
- existence of The CentOS Distribution, respectively.</para>
-
- </sect2>
-
- <sect2 id="corporate-identity" xreflabel="The corporate identity" label="4.2.2">
- <title>The corporate identity</title>
-
- <para>The CentOS Project corporate identity is the ``persona''
- of the organization known as The CentOS Project. The CentOS
- Project corporate identity plays a significant role in the way
- The CentOS Project, as organization, presents itself to both
- internal and external stakeholders. In general terms, The
- CentOS Project corporate identity expresses the values and
- ambitions of The CentOS Project organization, its business,
- and its characteristics.</para>
-
- <para>The CentOS Project corporate identity provides
- visibility, recognizability, reputation, structure and
- identification to The CentOS Project organization by means of
- <emphasis>corporate design</emphasis>, <emphasis>corporate
- communication</emphasis>, and <emphasis>corporate
- behaviour</emphasis>.</para>
-
- </sect2>
-
- <sect2 id="corporate-design" xreflabel="The corporate design" label="4.2.3">
-
- <title>The corporate design</title>
-
- <para>The corporate design is focused on the effective
- communication of corporate messages. Corporate messages are
- all the information emitted from the corporation to a target
- audience. In order for such communication to happen, it is
- required to put the messages on a medium available for the
- target audience to react upon. These media are know as
- <emphasis>corporate manifestations</emphasis>, because the
- corporation manifests its existence through them. The specific
- way used by the corporation to set their messages on different
- media is what the corporate design is about.</para>
-
- <para>The amount of manifestations a corporation uses to
- communicate its existence may very from one corporation to
- another. In the very specific case of The CentOS Project, the
- following corporate manifestations come to mind:</para>
-
- <orderedlist>
- <listitem>
-
- <para>The CentOS Distribution — The CentOS
- Distribution corporate manifestaion is made from SRPM
- packages. There are packages that make a remarkable
- use of images (e.g., Anaconda, Grub, Syslinux, Gdm,
- Kdm, Gsplash, Ksplash, Rhgb, Firstboot, etc.),
- packages that make a moderated use of images and
- packages that don't use images at all. Also, there
- are some packages that make use of text-based
- information that need to be changed, too (e.g.,
- release notes, eula, the welcome page of the web
- browser, etc.), in order for The CentOS Project to
- comply with upstream's redistribution guidelines. The
- CentOS Distribution corporate manifestation focuses
- its attention on SRPM packages that do use images in a
- remarkable way, specifically those packages that
- involve upstream branding, and those files with
- text-based information that need to be changed. This
- way, through image and text-based files, is
- implemented the corporate design of The CentOS
- Distribution corporate manifestations (i.e., all the
- releases of the operating system).</para>
-
- </listitem>
- <listitem>
-
- <para>The CentOS Web — This corporate
- manifestation exists to support The CentOS
- Distribution corporate manifestation. The CentOS Web
- corporate manifestation covers web applications used
- by The CentOS Project to manifest its existence on the
- Internet. These web applications are free software
- and come from different providers which distribute
- their work with predefined visual styles. Frequently,
- these predefined visual styles have no visual relation
- among themselves and introduce some visual
- contraditions when they all are put together. These
- visual contraditions need to be removed in order to
- comply with The CentOS Project corporate structure
- guidelines.</para>
-
- </listitem>
- <listitem>
-
- <para>The CentOS Showroom — This corporate
- manifestation exists to promote The CentOS
- Distribution. The CentOS Showroom corporate
- manifestation covers industrial production of objects
- branded by The CentOS Project (e.g., clothes,
- stationery and installation media). These branded
- objects are for distribution on social events and/or
- shops. They provide a way of promotion and a route
- for commercialization that may help to aliviate The
- CentOS Project expenses (e.g., hosting, servers,
- full-time-developers, etc.), in a similar way as
- donations may do.</para>
-
- </listitem>
- </orderedlist>
-
- <para>The corporate manifestations above seem to cover all the
- media required by The CentOS Project, as organization, to show
- its existence. However, other corporate manifestations could
- be added in the future, if needed, to cover different areas
- like building, offices, transportation and whaterver medium
- The CentOS Project thouches to show its existence.</para>
-
- </sect2>
-
- <sect2 id="corporate-communication" xreflabel="The corporate
- communication" label="4.2.4">
-
- <title>The corporate communication</title>
-
- <para> The CentOS Project corporate communication is based on
- <emphasis>community communication</emphasis> and takes place
- through the following avenues:
-
- <itemizedlist>
- <listitem><para>The CentOS Chat (#centos, #centos-social},
-#centos-devel on irc.freenode.net)</para></listitem>
- <listitem><para>The CentOS Mailing Lists (<ulink url="http://lists.centos.org/" />).</para></listitem>
- <listitem><para>The CentOS Forums (<ulink url="http://forums.centos.org/" />).</para></listitem>
- <listitem><para>The CentOS Wiki (<ulink url="http://wiki.centos.org/" />).</para></listitem>
- <listitem><para>Social events, interviews, conferences, etc.</para></listitem>
- </itemizedlist>
-
- </para>
-
- </sect2>
-
- <sect2 id="corporate-behaviour" xreflabel="The corporate behaviour"
- label="4.2.5">
-
- <title>The corporate behaviour</title>
-
- <para>The CentOS Project corporate behaviour is based on
- <emphasis>community behaviour</emphasis> which take place in
- <xref linkend="corporate-communication" />.</para>
-
- </sect2>
-
- <sect2 id="corporate-structure" xreflabel="The corporate structure"
- label="4.2.6">
-
- <title>The corporate structure</title>
-
- <para> The CentOS Project corporate structure is based on
- a <emphasis>monolithic corporate visual identity
- structure</emphasis>. In this configuration, one unique
- name and one unique visual style is used in all corporate
- manifestations of The CentOS Project.</para>
-
- <para>In a monolithic corporate visual identity structure,
- internal and external stakeholders feel a strong sensation
- of uniformity, orientation, and identification with the
- organization. No matter if you are visiting web sites,
- using the distribution, or acting on social events, the
- one unique name and one unique visual style connects them
- all to say: <emphasis>Hey! we are all part of The CentOS
- Project</emphasis>.</para>
-
- <para>Other corporate structures for The CentOS Project
- have been considered as well. Such is the case of
- producing one different visual style for each major
- release of The CentOS Distribution. This structure isn't
- inconvenient at all, but some visual contradictions could
- be introduced if it isn't applied correctly and we need to
- be aware of it. To apply it correctly, we need to know
- what The CentOS Project is made of.</para>
-
- <para>The CentOS Project, as organization, is mainly made
- of (but not limited to) three corporate manifestions: The
- CentOS Distribution, The CentOS Web and The CentOS
- Showroom. Inside The CentOS Distribution corporate
- manifestations, The CentOS Project maintains near to four
- different major releases of The CentOS Distribution (e.g.,
- the operating system), parallely in time. However, inside
- The CentOS Web visual manifestations, the content is
- produced for no specific release information (e.g., there
- is no a complete web site for each major release of The
- CentOS Distribution individually, but one web site to
- cover them all). Likewise, the content produced in The
- CentOS Showroom is created for no release-specific at all,
- but for The CentOS Project in general.</para>
-
- <para>In order to produce the correct corporate structure
- for The CentOS Project, we need to concider all the
- corporate manifestations The CentOS Project is made of,
- not just one of them. If one different visual style is
- used for each major release of The CentOS Distribution,
- which one of those different visual styles would be used
- to cover the remaining visual manifestations The CentOS
- Project is made of (e.g., The CentOS Web and The CentOS
- Showroom)?</para>
-
- <para>Probably you are thinking, that's right, but The
- CentOS Brand connects them all already, why would we need
- to join them up into the same visual style too, isn't it
- more work to do, and harder to maintain?</para>
-
- <para>Harder to maintain, more work to do, probably.
- Specially when you consider that The CentOS Project has
- proven stability and consistency through time and, that,
- certainly, didn't come through swinging magical wands or
- something but hardly working out to automate tasks and
- providing maintainance through time. Said that, we
- consider that The CentOS Project corporate structure must
- be consequent with such stability and consistency
- tradition, beyond the work it might require initially. It
- is true that The CentOS Brand does connect all the visual
- manifestations it is present on, but that connection would
- be stronger if one unique visual style backups it, too.
- In fact, whatever thing you do to strength the visual
- connection among The CentOS Project corporate
- manifestations would be very good in favor of The CentOS
- Project recognition.</para>
-
- <para>Obviously, having just one visual style in all
- corporate manifestations for eternity would be a very
- boring thing and would give the impression of a visually
- dead project. So, there is no problem on creating a brand
- new visual style for each new major release of The CentOS
- Distribution, in order to refresh The CentOS Distribution
- visual style; the problem itself is in not propagating the
- brand new visual style created for the new release of The
- CentOS Distribution to all other visual manifestations The
- CentOS Project is made of, in a way The CentOS Project
- could be recognized no matter what corporate manifestation
- be in front of us. Such lack of uniformity is what
- introduces the visual contradition we are precisely trying
- to solve by mean of themes production in the CentOS
- Artwork Repository.</para>
-
- </sect2>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Directories/trunk/Identity/Models.docbook b/Manuals/Docbook/Parts/Repository/Directories/trunk/Identity/Models.docbook
deleted file mode 100644
index 9abd711..0000000
--- a/Manuals/Docbook/Parts/Repository/Directories/trunk/Identity/Models.docbook
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-directories-section-3" xreflabel="trunk/Identity/Models" label="4.3">
- <title><filename class="directory">trunk/Identity/Models</filename></title>
- <para></para>
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Directories/trunk/Identity/Models/Themes.docbook b/Manuals/Docbook/Parts/Repository/Directories/trunk/Identity/Models/Themes.docbook
deleted file mode 100644
index f6fc57f..0000000
--- a/Manuals/Docbook/Parts/Repository/Directories/trunk/Identity/Models/Themes.docbook
+++ /dev/null
@@ -1,32 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-directories-section-4" xreflabel="trunk/Identity/Models/Themes" label="4.4">
-
- <title><filename class="directory">trunk/Identity/Models/Themes</filename></title>
-
- <para>This directory implements the concept of <emphasis>themes'
- design models</emphasis>.</para>
-
- <para>Themes' design models provide the structural part of images
- (e.g., dimensions, translation markers, position of each element
- on the visible area, etc.) required by
- <command>centos-art.sh</command> to perform theme rendition. The
- provide the modeling characteristics for all the different visual
- manifestations a theme is made of. Using themes' design models
- reduce the time needed for propagating an artistic motif to
- different visual manifestations.</para>
-
- <para>In this directory, themes' design models are organized by
- name. There is one directory for each theme's design model. Each
- design model directory must be named as specified in <xref
- linkend="repository-usage-section-3" />. Inside themes' design
- models directories, there is one directory for each visual
- manifestions a theme is made of. These directories are named
- <emphasis>visual manifestation directories</emphasis> and contain
- one or more SVG files to describe the visual structure of that
- visual manifestion.</para>
-
- <para>Themes' design models are <acronym>SVG</acronym> files and
- can be localized using the <code>locale</code> functionality of
- <command>centos-art.sh</command> script.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Directories/trunk/Identity/Models/Themes/Default.docbook b/Manuals/Docbook/Parts/Repository/Directories/trunk/Identity/Models/Themes/Default.docbook
deleted file mode 100644
index deb4f77..0000000
--- a/Manuals/Docbook/Parts/Repository/Directories/trunk/Identity/Models/Themes/Default.docbook
+++ /dev/null
@@ -1,16 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-directories-section-5" xreflabel="trunk/Identity/Models/Themes/Default" label="4.5">
-
- <title><filename class="directory">trunk/Identity/Models/Themes/Default</filename></title>
-
- <para>This directory implements the concept of <emphasis>themes'
- default design models</emphasis>.</para>
-
- <para>Themes' default design models provide the common structural
- information (e.g., image dimensions, translation markers,
- trademark position, etc.) the <command>centos-art.sh</command>
- script uses to produce images when no other design model is
- specified through the <option>--theme-model</option> option at
- rendition time.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Directories/trunk/Manuals.docbook b/Manuals/Docbook/Parts/Repository/Directories/trunk/Manuals.docbook
deleted file mode 100644
index f3099b6..0000000
--- a/Manuals/Docbook/Parts/Repository/Directories/trunk/Manuals.docbook
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-directories-section-6" xreflabel="trunk/Manuals" label="4.6">
- <title><filename class="directory">trunk/Manuals</filename></title>
- <para></para>
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/History/chapter.docbook b/Manuals/Docbook/Parts/Repository/History/chapter.docbook
deleted file mode 100644
index 5b5e486..0000000
--- a/Manuals/Docbook/Parts/Repository/History/chapter.docbook
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<chapter id="repository-history-chapter" xreflabel="History">
-
- <title>History</title>
-
- <para>This chapter describes, briefly, where we've been and where
- we're going to with the CentOS Artwork Repository.</para>
-
- &repository-history-section-1;
- &repository-history-section-2;
- &repository-history-section-3;
- &repository-history-section-4;
-
-</chapter>
diff --git a/Manuals/Docbook/Parts/Repository/History/section-1.docbook b/Manuals/Docbook/Parts/Repository/History/section-1.docbook
deleted file mode 100644
index 59ebc75..0000000
--- a/Manuals/Docbook/Parts/Repository/History/section-1.docbook
+++ /dev/null
@@ -1,32 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-history-section-1" label="1.1">
-
- <title>2008</title>
-
- <para>The CentOS Artwork Repository started at <ulink
- url="mailto:centos-devel@centos.org">CentOS Developers mailing
- list</ulink> during a discussion about how to automate the slide
- images of Anaconda. In such discussion, Ralph Angenendt rose up
- his hand to ask: Do you have something to show?</para>
-
- <para>To answer the question, Alain Reguera Delgado suggested a
- bash script which combined SVG and SED files in order to produce
- PNG images in different languages —together with the
- proposition of creating a Subversion repository where translations
- and image production could be distributed inside The CentOS
- Community—.</para>
-
- <para>Karanbirn Sighn considered the idea intresting and provided
- the infrastructure necessary to support the effort. This way the
- <ulink url="https://projects.centos.org/trac/artwork/">CentOS
- Artwork SIG</ulink> and the <ulink
- url="https://projects.centos.org/svn/artwork/">CentOS Artwork
- Repository</ulink> were officially created.</para>
-
- <para>Once the CentOS Artwork Repository was available, Alain
- Reguera Delagdo uploaded the bash script for rendering Anaconda
- slides; Ralph Angenendt documented it very well; and people
- started to download working copies of CentOS Artwork Repository to
- produce slide images in their own languages.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/History/section-2.docbook b/Manuals/Docbook/Parts/Repository/History/section-2.docbook
deleted file mode 100644
index a7dc742..0000000
--- a/Manuals/Docbook/Parts/Repository/History/section-2.docbook
+++ /dev/null
@@ -1,47 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-history-section-2" label="1.2">
-
- <title>2009</title>
-
- <para>The rendition script was at a very rustic state where only
- slide images could be produced, so it was redesigned to extend the
- image production to other areas, not just slide images. In this
- configuration, one SVG file was used as input to produce a
- translated instance of it which, in turn, was used to produce one
- translated PNG image as output. The SVG translated instance was
- created through SED replacement commands. The translated PNG image
- was created from the SVG translated instance using Inkscape
- command-line interface.</para>
-
- <para>The rendition script was named
- <quote>render.sh</quote>.</para>
-
- <para>The repository directory structure was prepared to receive
- the rendition script using design templates and translation files
- in the same location. There was one directory structure for each
- artwork that needed to be produced. In this configuration, if you
- would want to produce the same artwork with a different visual
- style or structure, it was needed to create a new directory
- structure for it because both the image structure and the image
- visual style were together in the design template.</para>
-
- <para>The rendition script was moved to a common place and linked
- from different directory structures. There was no need to have the
- same code in different directory structures if it could be in just
- one place and then be linked from different locations.</para>
-
- <para>The concepts about corporate identity began to be
- considered. As referece, it was used the book <quote>Corporate
- Identity</quote> by Wally Olins (1989) and Wikipedia (<ulink
- url="http://en.wikipedia.org/Corporate_identity" />). This way,
- the rendition script main's goal becomes to: automate production
- of a monolithic corporate visual identity structure, based on the
- mission and the release schema of The CentOS Project.</para>
-
- <para>The directory structures started to be documented inside the
- repository using text files without markup. Later, documentation
- in flat text files was moved to LaTeX format and this way
- <quote>The CentOS Artwork Repository Manual</quote> started to
- take form.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/History/section-3.docbook b/Manuals/Docbook/Parts/Repository/History/section-3.docbook
deleted file mode 100644
index 43d2181..0000000
--- a/Manuals/Docbook/Parts/Repository/History/section-3.docbook
+++ /dev/null
@@ -1,51 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-history-section-3" label="1.3">
-
- <title>2010</title>
-
- <para>The rendition script changed its name from
- <command>render.sh</command> to <command>centos-art.sh</command>
- and became a collection of functionalities where rendition was
- just one among others (e.g., documenting and localizing).</para>
-
- <para>The <command>centos-art.sh</command> was created to organize
- automation of most frequent tasks inside the repository. There
- was no need to have links all around the repository if a
- command-line interface could be created (through symbolic links,
- in the <filename class="directory">~/bin</filename> directory) and
- be called anywhere inside the repository as it would be a regular
- command.</para>
-
- <para>Inside <command>centos-art.sh</command>, functionalities
- started to get identified and separated one another. For example,
- when images were rendered, there was no need to load
- functionalities related to documentation manual. This layout moved
- us onto common functionalities and specific functionalities inside
- <command>centos-art.sh</command> script. Common functionalities
- are loaded when <command>centos-art.sh</command> script is
- initiated and are available to specific functionalities.</para>
-
- <para>The <command>centos-art.sh</command> script was redesigned
- to handle command-line options trough <command>getopt</command>
- option parser.</para>
-
- <para>The repository directory structure was updated to improve
- the implementation of concepts related to corporate visual
- identity. Specially in the area related to themes which were
- divided into <emphasis>design models</emphasis> and
- <emphasis>artistic motifs</emphasis> to eliminate the content
- duplication produced by having both image structure and image
- visual style in the same file. Now, themes are produced as result
- of arbitrary combinations of both design models (structures) and
- artistic motifs (visual styles).</para>
-
- <para>In the documentation area, the documentation files in LaTeX
- format were migrated to Texinfo format. In this configuration,
- each directory structure in the repository has a documentation
- entry associated in a Texinfo structure which can be read, edited
- and administered (e.g., renamed, deleted, copied) interactively
- throuch <command>centos-art.sh</command>. Additionally, the
- <command>texi2html</command> program was used to produced XHTML
- output customized by CSS from The CentOS Webenv.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/History/section-4.docbook b/Manuals/Docbook/Parts/Repository/History/section-4.docbook
deleted file mode 100644
index eeeffdc..0000000
--- a/Manuals/Docbook/Parts/Repository/History/section-4.docbook
+++ /dev/null
@@ -1,37 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-history-section-4" label="1.4">
-
- <title>2011</title>
-
- <para>The <command>centos-art.sh</command> script was redesigned
- to start translating SVG and other XML-based files (e.g., XHTML
- and Docbook files) through the <command>xml2po</command> program
- and shell scripts files (e.g., Bash scripts) through GNU
- <command>gettext</command> tools. This configuration provided a
- stronger interface for graphic designers, translators and
- programmers to produce localized content. The SED files are no
- longer used to handle translations.</para>
-
- <para>Improve option parsing through
- <command>getopt</command>.</para>
-
- <para>Consolidate the <code>render</code>, <code>help</code> and
- <code>locale</code> functionalities as the most frequent tasks
- performed inside the repository. Additionally, the
- <code>prepare</code> and <code>tuneup</code> functionalities are
- maintained as useful tasks.</para>
-
- <para>The <command>centos-art.sh</command> script is updated to
- organize functionalities in two groups: <quote>the administrative
- functionalities</quote> and <quote>the productive
- functionalities</quote>. The administrative functionalities cover
- actions like: copying, deleting and renaming directory structures
- inside the repository. Also, preparing your workstation for using
- <command>centos-art.sh</command> script, making backups of the
- distribution theme currently installed, installing themes created
- inside repository and restoring themes from backup. On the other
- hand, the productive functionalities cover actions like: content
- rendition, content localization, content documentation and content
- maintainance.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Usage/chapter.docbook b/Manuals/Docbook/Parts/Repository/Usage/chapter.docbook
deleted file mode 100644
index aaa2edc..0000000
--- a/Manuals/Docbook/Parts/Repository/Usage/chapter.docbook
+++ /dev/null
@@ -1,30 +0,0 @@
-<?xml version="1.0"?>
-<chapter id="repository-usage-chapter">
-
- <title>Usage convenctions</title>
-
- <para>The CentOS Artwork Repository is supported by <ulink
- url="http://subversion.tigris.org/">Subversion</ulink>, a version
- control system which allows you to keep old versions of files and
- directories (usually source code), keep a log of who, when, and
- why changes occurred, etc., like CVS, RCS or SCCS.</para>
-
- <para>When using Subversion there is one "source repository" and
- many "working copies" of that source repository. The working
- copies are independent one another, can be distributed all around
- the world and provide a local place for designers, documentors,
- translators and programmers to perform their work in a
- descentralized way. The source repository, on the other hand,
- provides a central place for all independent working copies to
- interchange data and provides the information required to permit
- extracting previous versions of files at any time.</para>
-
- &repository-usage-section-1;
- &repository-usage-section-2;
- &repository-usage-section-3;
- &repository-usage-section-4;
- &repository-usage-section-5;
- &repository-usage-section-6;
- &repository-usage-section-7;
-
-</chapter>
diff --git a/Manuals/Docbook/Parts/Repository/Usage/section-1.docbook b/Manuals/Docbook/Parts/Repository/Usage/section-1.docbook
deleted file mode 100644
index 024c597..0000000
--- a/Manuals/Docbook/Parts/Repository/Usage/section-1.docbook
+++ /dev/null
@@ -1,49 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-usage-section-1" xreflabel="Policy" label="3.1">
-
- <title>Policy</title>
-
- <para>The CentOS Artwork Repository is a collaborative tool that
- anyone can have access to. However, changing that tool in any form
- is something that should be requested in the <ulink
- url="mailto:centos-devel@centos.org">CentOS Developers mailing
- list</ulink>. Generally, people download working copies from
- CentOS Artwork Repository, study the repository organization, make
- some changes in their working copies, make some tests to verify
- such changes do work the way expected and finally request access
- to commit them up to the CentOS Artwork Repository (i.e., the
- source repository) for others to benefit from them.</para>
-
- <para>Once you've received access to commit your changes, there is
- no need for you to request permission again to commit other
- changes from your working copy to CentOS Artwork Repository as
- long as you behave as a <emphasis>good cooperating
- citizen</emphasis>. Otherwise, your rights to commit changes might
- be temporarly revoked or completly banished.</para>
-
- <para>As a good cooperating citizen one understand of a person who
- respects the work already done by others and share ideas with
- authors before changing relevant parts of their work, specially in
- situations when the access required to realize the changes has
- been granted already. Of course, there is a time when
- conversation has taken place, the paths has been traced and
- changing the work is so obvious that there is no need for you to
- talk about it; that's because you already did, you already built
- the trust to keep going. Anyway, the mailing list mentioned above
- is available for sharing ideas in a way that good relationship
- between community citizens could be constantly balanced.</para>
-
- <para>The relationship between community citizens is monitored by
- repository administrators. Repository administrators are
- responsible of granting everything goes the way it needs to go in
- order for the CentOS Artwork Repository to accomplish its mission
- which is: to provide a colaborative tool for The CentOS Community
- where The CentOS Project Corporate Identity is built and
- maintained by The CentOS Community itself.</para>
-
- <para>It is also important to remember that all source files
- inside CentOS Artwork Repository should comply the terms of <xref
- linkend="licenses-gpl-chapter" /> in order for them to remain
- inside the repository.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Usage/section-2.docbook b/Manuals/Docbook/Parts/Repository/Usage/section-2.docbook
deleted file mode 100644
index 2b414a3..0000000
--- a/Manuals/Docbook/Parts/Repository/Usage/section-2.docbook
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml verion="1.0"?>
-<sect1 id="repository-usage-section-2" xreflabel="Organization" label="3.2">
-
- <title>Organization</title>
-
- <para>The CentOS Artwork Repository organization is described in
- the chapter <xref linkend="repository-directories-chapter"
- />.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Usage/section-3.docbook b/Manuals/Docbook/Parts/Repository/Usage/section-3.docbook
deleted file mode 100644
index 1d0ded6..0000000
--- a/Manuals/Docbook/Parts/Repository/Usage/section-3.docbook
+++ /dev/null
@@ -1,17 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-usage-section-3" xreflabel="File names" label="3.3">
-
- <title>File names</title>
-
- <para>Inside the CentOS Artwork Repository, file names are all
- written in lowercase (e.g., <filename>01-welcome.png</filename>,
- <filename>splash.png</filename>,
- <filename>anaconda_header.png</filename>, etc.) and directory
- names are all written capitalized (e.g., <filename
- role="directory">Identity</filename>, <filename
- role="directory">Themes</filename>, <filename
- role="directory">Motifs</filename>) and sometimes in cammel case
- (e.g., <filename role="directory">TreeFlower</filename>, etc.).
- </para>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Usage/section-4-1.docbook b/Manuals/Docbook/Parts/Repository/Usage/section-4-1.docbook
deleted file mode 100644
index 06c4c54..0000000
--- a/Manuals/Docbook/Parts/Repository/Usage/section-4-1.docbook
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml versio="1.0"?>
-<sect2 id="repository-usage-section-4-1" xreflabel="Graphic design" label="3.4.1">
-
- <title>Graphic design</title>
-
- <para>The graphic design work line exists to cover brand design,
- typography design and themes design mainly. Additionally, some
- auxiliar areas like icon design, illustration design, brushes
- design, patterns designs and palettes of colors are also included
- here for completeness.</para>
-
- <para>The graphic design work line is organized in the <filename
- class="directory">trunk/Identity</filename> directory.</para>
-
-</sect2>
diff --git a/Manuals/Docbook/Parts/Repository/Usage/section-4-2.docbook b/Manuals/Docbook/Parts/Repository/Usage/section-4-2.docbook
deleted file mode 100644
index c063ad3..0000000
--- a/Manuals/Docbook/Parts/Repository/Usage/section-4-2.docbook
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<sect2 id="repository-usage-section-4-2" xreflabel="Graphic design" label="3.4.2">
-
- <title>Documentation</title>
-
- <para>The documentation work line exists to describe what each
- directory inside the CentOS Artwork Repository is for, the
- conceptual ideas behind them and, if possible, how automation
- scripts make use of them.</para>
-
- <para>The documentation work line is organized in the <filename
- class="directory">trunk/Manuals</filename> directory.</para>
-
-</sect2>
diff --git a/Manuals/Docbook/Parts/Repository/Usage/section-4-3.docbook b/Manuals/Docbook/Parts/Repository/Usage/section-4-3.docbook
deleted file mode 100644
index 86f4f6d..0000000
--- a/Manuals/Docbook/Parts/Repository/Usage/section-4-3.docbook
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<sect2 id="repository-usage-section-4-3" xreflabel="Graphic design" label="3.4.3">
-
- <title>Localization</title>
-
- <para>The localization work line exists to provide the translation
- messages required to produce content in different languages.
- Translation messages inside the repository are stored as portable
- objects (e.g., .po, .pot) and machine objects (.mo).</para>
-
- <para>The localization work line is organized in the <filename
- class="directory">trunk/Locales</filename> directory.</para>
-
-</sect2>
diff --git a/Manuals/Docbook/Parts/Repository/Usage/section-4-4.docbook b/Manuals/Docbook/Parts/Repository/Usage/section-4-4.docbook
deleted file mode 100644
index 2675e81..0000000
--- a/Manuals/Docbook/Parts/Repository/Usage/section-4-4.docbook
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml version="1.0"?>
-<sect2 id="repository-usage-section-4-4" xreflabel="Graphic design" label="3.4.4">
-
- <title>Automation</title>
-
- <para>The automation work line exists to standardize content
- production inside the working copies of CentOS Artwork Repository.
- Here is developed the <command>centos-art.sh</command> script, a
- bash script specially designed to automate most frequent tasks
- (e.g., rendition, documentation and localization) inside the
- repository. There is no need to type several tasks, time after
- time, if they can be programmed into just one executable
- script.</para>
-
- <para>The automation work line is organized in the <filename
- class="directory">trunk/Scripts</filename> directory.</para>
-
-</sect2>
diff --git a/Manuals/Docbook/Parts/Repository/Usage/section-4.docbook b/Manuals/Docbook/Parts/Repository/Usage/section-4.docbook
deleted file mode 100644
index 08f9d15..0000000
--- a/Manuals/Docbook/Parts/Repository/Usage/section-4.docbook
+++ /dev/null
@@ -1,23 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-usage-section-4" xreflabel="Graphic design" label="3.4">
-
- <title>Work lines</title>
-
- <para>Inside CentOS Artwork Repository there are four major work
- lines of production which are: graphic design, documentation,
- localization and automation. These work lines describe different
- areas of content production. Content production inside these
- specific areas may vary as much as persons be working on them.
- Producing content in too many different ways may result
- innapropriate in a collaborative environment like CentOS Artwork
- Repository where content produced in one area depends somehow from
- content produced in another different area. So, a content
- production standard is required for each available work
- line.</para>
-
- &repository-usage-section-4-1;
- &repository-usage-section-4-2;
- &repository-usage-section-4-3;
- &repository-usage-section-4-4;
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Usage/section-5.docbook b/Manuals/Docbook/Parts/Repository/Usage/section-5.docbook
deleted file mode 100644
index dc9613d..0000000
--- a/Manuals/Docbook/Parts/Repository/Usage/section-5.docbook
+++ /dev/null
@@ -1,44 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-usage-section-5" xreflabel="Connection between directories" label="3.5">
-
- <title>Connection between directories</title>
-
- <para>In order for automation scripts to produce content inside
- working copies of CentOS Artwork Repository, it is required that
- all work lines be connected somehow. Using this connection,
- automation scripts can know where to retrive the information they
- need to work with (e.g., design model, translation messages,
- output locations, etc.). This connection is built using two path
- constructions named <emphasis>master paths</emphasis> and
- <emphasis>auxiliar paths</emphasis>.</para>
-
- <para>The master path points only to directories that contain
- source files (e.g., SVG files) required to produce base content
- (e.g., PNG files) through automation scripts. Each master path
- inside the repository may have several auxiliar paths associated,
- but auxiliar paths can only have one master path associated.
- Master paths are organized under <filename
- class="directory">trunk/Identity/Models</filename> directory
- structure and auxiliar paths under <filename
- class="directory">trunk/Identity/Images</filename>, <filename
- class="directory">trunk/Locales</filename> and <filename
- class="directory">trunk/Manuals</filename> directory
- structures.</para>
-
- <para>The auxiliar paths can point either to directories or files.
- When an auxiliar path points to a directory, that directory
- contains information that modifies somehow the content produced
- from master paths (e.g., translation messages) or provides the
- output information required to know where to store the content
- produced from master path. When an auxiliar path points to a
- file, that file has no other purpose but to document the master
- path it refers to.</para>
-
- <para>The relationship between auxiliar paths and master paths is
- realized by combining the master path itself and the second level
- directory structures of the repository. The master path is
- considered the path identifier and the second level directory
- structure taken from the repository is considered the common part
- of the path where the path identifier is appended to.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Usage/section-6.docbook b/Manuals/Docbook/Parts/Repository/Usage/section-6.docbook
deleted file mode 100644
index 59684cd..0000000
--- a/Manuals/Docbook/Parts/Repository/Usage/section-6.docbook
+++ /dev/null
@@ -1,72 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-usage-section-6" xreflabel="Syncronizing path information" label="3.6">
-
- <title>Syncronizing path information</title>
-
- <para>Syncronizing path information is the action of keeping all
- path information up to date in the repository. This action implies
- both file movement and replacement of content inside files already
- moved, in this very specific order. File movement is related to
- actions like duplicate, delete and rename files and directories in
- the repository. Replacement of content inside files is related to
- replace information, path information in this case, inside files
- in the repository.</para>
-
- <para>The order followed to syncronize path information is
- relevant because the versioned nature of the files we are working
- with. We don't perform file content replacement first because that
- would imply a repository change which will immediatly demmand a
- commit in order for actions like duplicate, delete or rename to
- take place. However, if we perform file movement first, it is
- possible to commit both file moved and file content replacements
- as if they were just one change. In this case the file content
- replacement takes palce in the target location that have been
- duplicated or renamed, not the one use as source location. This
- configuration is specially useful when files are renamed (i.e.,
- one file is copied from a source location to a target location and
- then the source location of it is removed from repository).</para>
-
- <warning><para>There is no support for URLs actions inside
- <command>centos-art.sh</command> script. The
- <command>centos-art.sh</command> script is designed to work with
- local files inside the working copy only. If you need to perform
- URL actions directly, use Subversion commands
- instead.</para></warning>
-
- <para>When one master path is changed it is required that all
- related auxiliar paths be changed, too. This is required in order
- for master paths to retain their relation with auxiliar paths.
- This way, automation scripts are able to know where to retrive
- translation messages from, where to store final output images to
- and where to look for documentation. If relation between master
- paths and auxiliar paths is lost, there is no way for automation
- scripts to know where to retrive the information they need.</para>
-
- <para>The auxiliar paths should never be modified under any reason
- but to satisfy the relationship with the master path. Liberal
- change of auxiliar paths may suppress the conceptual idea they
- were initially created for; and certainly, automation scripts may
- stop working as expected. The update direction to rename path
- information must be from master path to auxiliar path and never
- the opposite.</para>
-
- <para>The relation between master and auxiliar paths is useful to
- keep repository organized but introduce some complications when we
- work with files that use master path information as reference to
- build structural information. This is the case of repository
- documentation manual source files where inclusions, menus, nodes
- and cross references are built using master path information as
- reference. Now, to see what kind of complication we are talking
- about, consider what would happen to a structural definitions
- (i.e., inlusions, menus, nodes and cross refereces) already set in
- the manual from one master path that is suddenly renamed to
- something different. If the path information is not syncronized,
- at this point, we lose connection between the master path and the
- auxiliar path created to store the related documentation entry, as
- well as the related structural definitions that end up pointing to
- a master path that no longer exist.</para>
-
- <para>The syncronization of path information is aimed to solve
- these kind of issues.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/Parts/Repository/Usage/section-7.docbook b/Manuals/Docbook/Parts/Repository/Usage/section-7.docbook
deleted file mode 100644
index 6ab854b..0000000
--- a/Manuals/Docbook/Parts/Repository/Usage/section-7.docbook
+++ /dev/null
@@ -1,75 +0,0 @@
-<?xml version="1.0"?>
-<sect1 id="repository-usage-section-7" xreflabel="Syncronizing path information" label="3.7">
-
- <title>Extending repository organization</title>
-
- <para>Occasionly, you may find that new components of The CentOS
- Project Corporate Identity need to be added to the repository in
- order to work them out. If that is the case, the first question we
- need to ask ourselves, before start to create directories blindly
- all over, is: @emph{What is the right place to store it?}</para>
-
- <para>The best place to find answers is in The CentOS Community
- (see page @url{http://wiki.centos.org/GettingHelp}), but going
- there with hands empty is not good idea. It may give the
- impression you don't really care about. Instead, consider the
- following suggestions to find your own comprehension in order to
- make your own propositions based on it.</para>
-
- <para>When extending respository structure it is very useful to
- bear in mind The CentOS Project Corporate Identity Structure
- (@pxref{Directories trunk Identity}) The CentOS Mission and The
- CentOS Release Schema. The rest is just matter of choosing
- appropriate names. It is also worth to know that each directory in
- the repository responds to a conceptual idea that justifies its
- existence.</para>
-
- <para>To build a directory structure, you need to define the
- conceptual idea first and later create the directory. There are
- some locations inside the repository that already define some
- concepts you probably want to reuse. For example,
- @file{trunk/Identity/Images/Themes} to store theme artistic
- motifs, @file{trunk/Identity/Models/Themes} to store theme design
- models, @file{trunk/Manual} to store documentation files,
- @file{trunk/Locales} to store translation messages,
- @file{trunk/Scripts} to store automation scripts and so on.</para>
-
- <para>To illustrate this desition process let's consider the
- @file{trunk/Identity/Images/Themes/TreeFlower/3} directory
- structure as example. This directory can be read as: the theme
- development line of version @file{3} of @file{TreeFlower} artistic
- motif. Additional, we can identify that artistic motifs are part
- of themes as well as themes are part of The CentOS Project
- Corporate Identity. These concepts are better described
- independently in each documentation entry related to the directory
- structure as it is respectively shown in the list of commands
- bellow.
-
- <itemizedlist>
- <listitem>
- <para><command>centos-art help --read turnk</command></para>
- </listitem>
- <listitem>
- <para><command>centos-art help --read turnk/Identity</command></para>
- </listitem>
- <listitem>
- <para><command>centos-art help --read turnk/Identity/Images</command></para>
- </listitem>
- <listitem>
- <para><command>centos-art help --read turnk/Identity/Images/Themes</command></para>
- </listitem>
- <listitem>
- <para><command>centos-art help --read turnk/Identity/Images/Themes/TreeFlower</command></para>
- </listitem>
- <listitem>
- <para><command>centos-art help --read turnk/Identity/Images/Themes/TreeFlower/3</command></para>
- </listitem>
- </itemizedlist>
-
- </para>
-
- <para>The concepts behind other location can be found in the same
- way described above, just change the path information used above
- to the one you are trying to know concepts for.</para>
-
-</sect1>
diff --git a/Manuals/Docbook/repository.docbook b/Manuals/Docbook/repository.docbook
index 841bc23..9e71a87 100644
--- a/Manuals/Docbook/repository.docbook
+++ b/Manuals/Docbook/repository.docbook
@@ -4,87 +4,87 @@
<!-- Frontmatter -->
- <!ENTITY book-title SYSTEM "Book/title.docbook">
- <!ENTITY book-authors SYSTEM "Book/authors.docbook">
- <!ENTITY book-copyright SYSTEM "Book/copyright.docbook">
- <!ENTITY book-legalnotice SYSTEM "Book/legalnotice.docbook">
- <!ENTITY book-date SYSTEM "Book/date.docbook">
- <!ENTITY book-abstract SYSTEM "Book/abstract.docbook">
- <!ENTITY book-preamble SYSTEM "Book/preamble.docbook">
- <!ENTITY book-preface SYSTEM "Book/preface.docbook">
- <!ENTITY book-parts SYSTEM "Book/parts.docbook">
+ <!ENTITY repository-title SYSTEM "repository-title.docbook">
+ <!ENTITY repository-authors SYSTEM "repository-authors.docbook">
+ <!ENTITY repository-copyright SYSTEM "repository-copyright.docbook">
+ <!ENTITY repository-legalnotice SYSTEM "repository-legalnotice.docbook">
+ <!ENTITY repository-date SYSTEM "repository-date.docbook">
+ <!ENTITY repository-abstract SYSTEM "repository-abstract.docbook">
+ <!ENTITY repository-preamble SYSTEM "repository-preamble.docbook">
+ <!ENTITY repository-preface SYSTEM "repository-preface.docbook">
+ <!ENTITY repository-parts SYSTEM "repository-parts.docbook">
- <!-- Preface -->
- <!ENTITY preface SYSTEM "Preface.docbook">
- <!ENTITY preface-document-convenctions SYSTEM "Preface/document-convenctions.docbook">
- <!ENTITY preface-send-in-your-feedback SYSTEM "Preface/send-in-your-feedback.docbook">
+ <!-- Entities/Preface -->
+ <!ENTITY preface SYSTEM "Entities/Preface.docbook">
+ <!ENTITY preface-document-convenctions SYSTEM "Entities/Preface/document-convenctions.docbook">
+ <!ENTITY preface-send-in-your-feedback SYSTEM "Entities/Preface/send-in-your-feedback.docbook">
<!-- Mainmatter -->
- <!-- Part I: The Repository -->
- <!ENTITY repo-history SYSTEM "Repository/History.docbook">
- <!ENTITY repo-history-2008 SYSTEM "Repository/History/2008.docbook">
- <!ENTITY repo-history-2009 SYSTEM "Repository/History/2009.docbook">
- <!ENTITY repo-history-2010 SYSTEM "Repository/History/2010.docbook">
- <!ENTITY repo-history-2011 SYSTEM "Repository/History/2011.docbook">
+ <!-- Part I: The Entities/Repository -->
+ <!ENTITY repo-history SYSTEM "Entities/Repository/History.docbook">
+ <!ENTITY repo-history-2008 SYSTEM "Entities/Repository/History/2008.docbook">
+ <!ENTITY repo-history-2009 SYSTEM "Entities/Repository/History/2009.docbook">
+ <!ENTITY repo-history-2010 SYSTEM "Entities/Repository/History/2010.docbook">
+ <!ENTITY repo-history-2011 SYSTEM "Entities/Repository/History/2011.docbook">
- <!ENTITY repo-copying SYSTEM "Repository/Copying.docbook">
- <!ENTITY repo-copying-preamble SYSTEM "Repository/Copying/preamble.docbook">
- <!ENTITY repo-copying-the-centos-brand SYSTEM "Repository/Copying/the-centos-brand.docbook">
+ <!ENTITY repo-copying SYSTEM "Entities/Repository/Copying.docbook">
+ <!ENTITY repo-copying-preamble SYSTEM "Entities/Repository/Copying/preamble.docbook">
+ <!ENTITY repo-copying-the-centos-brand SYSTEM "Entities/Repository/Copying/the-centos-brand.docbook">
- <!ENTITY repo-usage SYSTEM "Repository/Usage.docbook">
- <!ENTITY repo-usage-preamble SYSTEM "Repository/Usage/preamble.docbook">
- <!ENTITY repo-usage-organization SYSTEM "Repository/Usage/organization.docbook">
- <!ENTITY repo-usage-filenames SYSTEM "Repository/Usage/filenames.docbook">
- <!ENTITY repo-usage-worklines SYSTEM "Repository/Usage/worklines.docbook">
- <!ENTITY repo-usage-worklines-graphic-design SYSTEM "Repository/Usage/Worklines/graphic-design.docbook">
- <!ENTITY repo-usage-worklines-documentation SYSTEM "Repository/Usage/Worklines/documentation.docbook">
- <!ENTITY repo-usage-worklines-localization SYSTEM "Repository/Usage/Worklines/localization.docbook">
- <!ENTITY repo-usage-worklines-automation SYSTEM "Repository/Usage/Worklines/automation.docbook">
- <!ENTITY repo-usage-connection-between-worklines SYSTEM "Repository/Usage/connection-between-worklines.docbook">
- <!ENTITY repo-usage-syncronizing-paths SYSTEM "Repository/Usage/syncronizing-paths.docbook">
- <!ENTITY repo-usage-extending-repository SYSTEM "Repository/Usage/extending-repository.docbook">
+ <!ENTITY repo-usage SYSTEM "Entities/Repository/Usage.docbook">
+ <!ENTITY repo-usage-preamble SYSTEM "Entities/Repository/Usage/preamble.docbook">
+ <!ENTITY repo-usage-organization SYSTEM "Entities/Repository/Usage/organization.docbook">
+ <!ENTITY repo-usage-filenames SYSTEM "Entities/Repository/Usage/filenames.docbook">
+ <!ENTITY repo-usage-worklines SYSTEM "Entities/Repository/Usage/worklines.docbook">
+ <!ENTITY repo-usage-worklines-graphic-design SYSTEM "Entities/Repository/Usage/Worklines/graphic-design.docbook">
+ <!ENTITY repo-usage-worklines-documentation SYSTEM "Entities/Repository/Usage/Worklines/documentation.docbook">
+ <!ENTITY repo-usage-worklines-localization SYSTEM "Entities/Repository/Usage/Worklines/localization.docbook">
+ <!ENTITY repo-usage-worklines-automation SYSTEM "Entities/Repository/Usage/Worklines/automation.docbook">
+ <!ENTITY repo-usage-connection-between-worklines SYSTEM "Entities/Repository/Usage/connection-between-worklines.docbook">
+ <!ENTITY repo-usage-syncronizing-paths SYSTEM "Entities/Repository/Usage/syncronizing-paths.docbook">
+ <!ENTITY repo-usage-extending-repository SYSTEM "Entities/Repository/Usage/extending-repository.docbook">
- <!ENTITY repo-dir SYSTEM "Repository/Directories.docbook">
- <!ENTITY repo-dir-trunk SYSTEM "Repository/Directories/trunk.docbook">
- <!ENTITY repo-dir-trunk-identity SYSTEM "Repository/Directories/trunk/Identity.docbook">
- <!ENTITY repo-dir-trunk-identity-models SYSTEM "Repository/Directories/trunk/Identity/Models.docbook">
- <!ENTITY repo-dir-trunk-identity-models-themes SYSTEM "Repository/Directories/trunk/Identity/Models/Themes.docbook">
- <!ENTITY repo-dir-trunk-identity-models-themes-default SYSTEM "Repository/Directories/trunk/Identity/Models/Themes/Default.docbook">
- <!ENTITY repo-dir-trunk-manual SYSTEM "Repository/Directories/trunk/Manuals.docbook">
+ <!ENTITY repo-dir SYSTEM "Entities/Repository/Directories.docbook">
+ <!ENTITY repo-dir-trunk SYSTEM "Entities/Repository/Directories/trunk.docbook">
+ <!ENTITY repo-dir-trunk-identity SYSTEM "Entities/Repository/Directories/trunk/Identity.docbook">
+ <!ENTITY repo-dir-trunk-identity-models SYSTEM "Entities/Repository/Directories/trunk/Identity/Models.docbook">
+ <!ENTITY repo-dir-trunk-identity-models-themes SYSTEM "Entities/Repository/Directories/trunk/Identity/Models/Themes.docbook">
+ <!ENTITY repo-dir-trunk-identity-models-themes-default SYSTEM "Entities/Repository/Directories/trunk/Identity/Models/Themes/Default.docbook">
+ <!ENTITY repo-dir-trunk-manual SYSTEM "Entities/Repository/Directories/trunk/Manuals.docbook">
- <!-- Part II: Licenses -->
- <!ENTITY licenses-gpl SYSTEM "Licenses/Gpl.docbook">
- <!ENTITY licenses-gpl-preamble SYSTEM "Licenses/Gpl/preamble.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions SYSTEM "Licenses/Gpl/Terms-and-conditions.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions-section-0 SYSTEM "Licenses/Gpl/Terms-and-conditions/section-0.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions-section-1 SYSTEM "Licenses/Gpl/Terms-and-conditions/section-1.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions-section-2 SYSTEM "Licenses/Gpl/Terms-and-conditions/terms-and-conditions-section.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions-section-3 SYSTEM "Licenses/Gpl/Terms-and-conditions/section-3.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions-section-4 SYSTEM "Licenses/Gpl/Terms-and-conditions/section-4.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions-section-5 SYSTEM "Licenses/Gpl/Terms-and-conditions/section-5.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions-section-6 SYSTEM "Licenses/Gpl/Terms-and-conditions/section-6.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions-section-7 SYSTEM "Licenses/Gpl/Terms-and-conditions/section-7.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions-section-8 SYSTEM "Licenses/Gpl/Terms-and-conditions/section-8.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions-section-9 SYSTEM "Licenses/Gpl/Terms-and-conditions/section-9.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions-section-10 SYSTEM "Licenses/Gpl/Terms-and-conditions/section-10.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions-section-11 SYSTEM "Licenses/Gpl/Terms-and-conditions/section-11.docbook">
- <!ENTITY licenses-gpl-terms-and-conditions-section-12 SYSTEM "Licenses/Gpl/Terms-and-conditions/section-12.docbook">
- <!ENTITY licenses-gpl-how-to-apply-this-license SYSTEM "Licenses/Gpl/how-to-apply-this-license.docbook">
+ <!-- Part II: Entities/Licenses -->
+ <!ENTITY licenses-gpl SYSTEM "Entities/Licenses/Gpl.docbook">
+ <!ENTITY licenses-gpl-preamble SYSTEM "Entities/Licenses/Gpl/preamble.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions-section-0 SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions/section-0.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions-section-1 SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions/section-1.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions-section-2 SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions/terms-and-conditions-section.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions-section-3 SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions/section-3.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions-section-4 SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions/section-4.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions-section-5 SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions/section-5.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions-section-6 SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions/section-6.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions-section-7 SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions/section-7.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions-section-8 SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions/section-8.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions-section-9 SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions/section-9.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions-section-10 SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions/section-10.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions-section-11 SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions/section-11.docbook">
+ <!ENTITY licenses-gpl-terms-and-conditions-section-12 SYSTEM "Entities/Licenses/Gpl/Terms-and-conditions/section-12.docbook">
+ <!ENTITY licenses-gpl-how-to-apply-this-license SYSTEM "Entities/Licenses/Gpl/how-to-apply-this-license.docbook">
- <!ENTITY licenses-gfdl SYSTEM "Licenses/Gfdl.docbook">
- <!ENTITY licenses-gfdl-preamble SYSTEM "Licenses/Gfdl/preamble.docbook">
- <!ENTITY licenses-gfdl-applicability-and-definitions SYSTEM "Licenses/Gfdl/applicability-and-definitions.docbook">
- <!ENTITY licenses-gfdl-verbatim-copying SYSTEM "Licenses/Gfdl/verbatim-copying.docbook">
- <!ENTITY licenses-gfdl-copying-in-quantity SYSTEM "Licenses/Gfdl/copying-in-quantity.docbook">
- <!ENTITY licenses-gfdl-modifications SYSTEM "Licenses/Gfdl/modifications.docbook">
- <!ENTITY licenses-gfdl-combining-documents SYSTEM "Licenses/Gfdl/combining-documents.docbook">
- <!ENTITY licenses-gfdl-collection-of-documents SYSTEM "Licenses/Gfdl/collection-of-documents.docbook">
- <!ENTITY licenses-gfdl-aggregation-with-independent-works SYSTEM "Licenses/Gfdl/aggregation-with-independent-works.docbook">
- <!ENTITY licenses-gfdl-translations SYSTEM "Licenses/Gfdl/translations.docbook">
- <!ENTITY licenses-gfdl-Termination SYSTEM "Licenses/Gfdl/Termination.docbook">
- <!ENTITY licenses-gfdl-future-revisions-of-this-license SYSTEM "Licenses/Gfdl/future-revisions-of-this-license.docbook">
- <!ENTITY licenses-gfdl-how-to-use-this-license SYSTEM "Licenses/Gfdl/how-to-use-this-license.docbook">
+ <!ENTITY licenses-gfdl SYSTEM "Entities/Licenses/Gfdl.docbook">
+ <!ENTITY licenses-gfdl-preamble SYSTEM "Entities/Licenses/Gfdl/preamble.docbook">
+ <!ENTITY licenses-gfdl-applicability-and-definitions SYSTEM "Entities/Licenses/Gfdl/applicability-and-definitions.docbook">
+ <!ENTITY licenses-gfdl-verbatim-copying SYSTEM "Entities/Licenses/Gfdl/verbatim-copying.docbook">
+ <!ENTITY licenses-gfdl-copying-in-quantity SYSTEM "Entities/Licenses/Gfdl/copying-in-quantity.docbook">
+ <!ENTITY licenses-gfdl-modifications SYSTEM "Entities/Licenses/Gfdl/modifications.docbook">
+ <!ENTITY licenses-gfdl-combining-documents SYSTEM "Entities/Licenses/Gfdl/combining-documents.docbook">
+ <!ENTITY licenses-gfdl-collection-of-documents SYSTEM "Entities/Licenses/Gfdl/collection-of-documents.docbook">
+ <!ENTITY licenses-gfdl-aggregation-with-independent-works SYSTEM "Entities/Licenses/Gfdl/aggregation-with-independent-works.docbook">
+ <!ENTITY licenses-gfdl-translations SYSTEM "Entities/Licenses/Gfdl/translations.docbook">
+ <!ENTITY licenses-gfdl-Termination SYSTEM "Entities/Licenses/Gfdl/Termination.docbook">
+ <!ENTITY licenses-gfdl-future-revisions-of-this-license SYSTEM "Entities/Licenses/Gfdl/future-revisions-of-this-license.docbook">
+ <!ENTITY licenses-gfdl-how-to-use-this-license SYSTEM "Entities/Licenses/Gfdl/how-to-use-this-license.docbook">
<!-- Backmatter -->