diff --git a/Artworks/Docs/Asciidoc/Distro/eula.asciidoc b/Artworks/Docs/Asciidoc/Distro/eula.asciidoc
deleted file mode 100644
index cc006fc..0000000
--- a/Artworks/Docs/Asciidoc/Distro/eula.asciidoc
+++ /dev/null
@@ -1,7 +0,0 @@
-= CentOS =RELEASE= EULA
-The CentOS Project
-
-CentOS =RELEASE= comes with no guarantees or warranties of any sorts, either
-written or implied. The Distribution is released as
-file:///usr/share/doc/centos-release-5/GPL[GPL] work. Individual packages in
-the distribution come with their own licences.
diff --git a/Artworks/Docs/Asciidoc/Distro/eula.conf b/Artworks/Docs/Asciidoc/Distro/eula.conf
deleted file mode 100644
index 27a5361..0000000
--- a/Artworks/Docs/Asciidoc/Distro/eula.conf
+++ /dev/null
@@ -1,33 +0,0 @@
-[eula-final/eula.docbook]
-source = "eula.asciidoc"
-command = "asciidoc --backend=docbook"
-
-[eula-final/eula.xhtml]
-source = "eula-final/eula.docbook"
-command = "centos-art render --backend=xhtml"
-
-[eula-final/eula.pdf]
-source = "eula-final/eula.docbook"
-command = "centos-art render --backend=pdf"
-
-#
-# Add rendition support for different languages too. The following
-# lines are valid when LANG environment variable doesn't begin with
-# `en' characters.
-#
-
-[eula-final-${LANG}/eula.docbook]
-source = "eula-final/eula.docbook"
-localization = "eula-l10n/${LANG}.po"
-command = "centos-art render --backend=docbook"
-
-[eula-final-${LANG}/eula.xhtml]
-source = "eula-final-${LANG}/eula.docbook"
-localization = "eula-l10n/${LANG}.po"
-command = "centos-art render --backend=xhtml"
-
-[eula-final-${LANG}/eula.pdf]
-source = "eula-final-${LANG}/eula.docbook"
-localization = "eula-l10n/${LANG}.po"
-command = "centos-art render --backend=pdf"
-
diff --git a/Artworks/Docs/Asciidoc/Distro/firefox_service_agreement.asciidoc b/Artworks/Docs/Asciidoc/Distro/firefox_service_agreement.asciidoc
deleted file mode 100644
index cda14d5..0000000
--- a/Artworks/Docs/Asciidoc/Distro/firefox_service_agreement.asciidoc
+++ /dev/null
@@ -1,153 +0,0 @@
-Mozilla Firefox - Website Services Agreement
-============================================
-
-The accompanying version of Mozilla Firefox utilizes website information
-services (``Services''), such as safe-browsing features, which are provided by
-the Mozilla Corporation and made available to you under additional terms. By
-using the Services, you consent to the terms of the referenced Mozilla Firefox
-Website Services Agreement.
-
-If you do not agree to these terms, do not use the Services and disable the
-Services in Edit -> Preferences -> Security and uncheck the options for both:
-``Tell me if the site I'm visiting is a suspected attack site'' and ``Tell me
-if the site I'm visiting is a suspected forgery.''
-
-Version 3.0, June 2008
-----------------------
-
-During the Mozilla Firefox installation process, and at later times, you may be
-given the option of installing additional components from third-party software
-providers. The installation and use of those third-party components may be
-governed by additional license agreements.
-
-In this Mozilla Firefox Website Services Agreement (``Agreement''), the
-accompanying executable version of Mozilla Firefox shall be referred to as
-``the Product''.
-
-The Product utilizes website information services (``Services''), such as
-safe-browsing features, which are provided by the Mozilla Corporation
-(``Mozilla'') and made available to you subject to the terms below. By using
-the Services, you consent to the terms of this Agreement. If you do not agree
-to the terms of this Agreement, do not use the Services and disable the
-Services in the preferences/security menu.
-
-Use Of Service
-~~~~~~~~~~~~~~
-
-Mozilla permits you to use the Services via the Product. This Agreement will
-also govern the use of Services made available to you as a result of your
-installing any executable software upgrades to the Product provided to you by
-CentOS, where those Services replace and/or supplement the Services provided
-through use of the Product. In such a case, ``the Product'' shall
-also refer to such installed upgrades. However, if such upgrades are
-accompanied by a separate agreement from Mozilla, the terms of that agreement
-will govern.
-
-Termination
-~~~~~~~~~~~
-
-If you breach this Agreement your right to use the Services will terminate
-immediately and without notice, but all provisions of this Agreement except the
-Use of Services (Paragraph 1) will survive termination and continue in effect.
-
-Proprietary Rights
-~~~~~~~~~~~~~~~~~~
-
-Subject to this Agreement and to all applicable licensing terms governing your
-use of the Product, Mozilla, for itself and on behalf of its licensors, hereby
-reserves all intellectual property rights in the Services, except for the
-rights expressly granted in this Agreement. You may not remove or alter any
-trademark, logo, copyright or other proprietary notice in or on the Product.
-This agreement does not grant you any right to use the trademarks, service
-marks or logos of Mozilla or its licensors. Nothing in this Agreement shall be
-construed to limit any rights granted under open source licenses applicable to
-the Product and to corresponding source code versions of the Product.
-
-Privacy Policy
-~~~~~~~~~~~~~~
-
-The Mozilla Firefox Privacy Policy is made available online at
-http://www.mozilla.com/legal/privacy/, as that policy may be updated from time
-to time.
-
-Website Information Services
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Mozilla and its contributors, licensors and partners work to provide the most
-accurate and up-to-date phishing and malware information. However, they cannot
-guarantee that this information is comprehensive and error-free: some risky
-sites may not be identified, and some safe sites may be identified in error.
-
-Disclaimer Of Warranty
-~~~~~~~~~~~~~~~~~~~~~~
-
-The product and services are provided ``as is'' with all faults. to the extent
-permitted by law, mozilla and mozilla's distributors, and licensors hereby
-disclaim all warranties, whether express or implied, including without
-limitation warranties that the product and services are free of defects,
-merchantable, fit for a particular purpose and non-infringing. you bear the
-entire risk as to selecting the product and services for your purposes and as
-to the quality and performance of the product and services. this limitation
-will apply notwithstanding the failure of essential purpose of any remedy.
-some jurisdictions do not allow the exclusion or limitation of implied
-warranties, so this disclaimer may not apply to you.
-
-Limitation Of Liability
-~~~~~~~~~~~~~~~~~~~~~~~
-
-Except as required by law, mozilla and its distributors, directors, licensors,
-contributors and agents (collectively, the ``mozilla group'') will
-not be liable for any indirect, special, incidental, consequential or exemplary
-damages arising out of or in any way relating to this agreement or the use of
-or inability to use the product and the services, including without limitation
-damages for loss of goodwill, work stoppage, lost profits, loss of data, and
-computer failure or malfunction, even if advised of the possibility of such
-damages and regardless of the theory (contract, tort or otherwise) upon which
-such claim is based. the mozilla group's collective liability under this
-agreement will not exceed the greater of $500 (five hundred dollars) and the
-fees paid by you under the license (if any). Some jurisdictions do not allow
-the exclusion or limitation of incidental, consequential or special damages, so
-this exclusion and limitation may not apply to you.
-
-U.S. Goverment End-Users
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-This Product is a ``commercial item,'' as that term is defined in 48
-C.F.R. 2.101, consisting of ``commercial computer software'' and
-``commercial computer software documentation,'' as such terms are
-used in 48 C.F.R. 12.212 (Sept. 1995) and 48 C.F.R. 227.7202 (June 1995).
-Consistent with 48 C.F.R. 12.212, 48 C.F.R. 27.405(b)(2) (June 1998) and 48
-C.F.R. 227.7202, all U.S. Government End Users acquire the Product with only
-those rights as set forth therein.
-
-Miscellaneous
-~~~~~~~~~~~~~
-
-a. This Agreement constitutes the entire agreement between Mozilla and you
-concerning the subject matter hereof, and it may only be modified by a written
-amendment signed by an authorized executive of Mozilla.
-
-b. Except to the extent applicable law, if any, provides otherwise, this
-Agreement will be governed by the laws of the state of California, U.S.A.,
-excluding its conflict of law provisions.
-
-c. This Agreement will not be governed by the United Nations Convention on
-Contracts for the International Sale of Goods.
-
-d. If any part of this Agreement is held invalid or unenforceable, that part
-will be construed to reflect the parties' original intent, and the remaining
-portions will remain in full force and effect
-
-e. A waiver by either party of any term or condition of this Agreement or any
-breach thereof, in any one instance, will not waive such term or condition or
-any subsequent breach thereof.
-
-f. Except as required by law, the controlling language of this Agreement is
-English.
-
-g. You may assign your rights under this Agreement to any party that consents
-to, and agrees to be bound by, its terms; the Mozilla Corporation may assign
-its rights under this Agreement without condition.
-
-h. This Agreement will be binding upon and inure to the benefit of the parties,
-their successors and permitted assigns.
diff --git a/Artworks/Docs/Asciidoc/Distro/firefox_service_agreement.conf b/Artworks/Docs/Asciidoc/Distro/firefox_service_agreement.conf
deleted file mode 100644
index e69de29..0000000
--- a/Artworks/Docs/Asciidoc/Distro/firefox_service_agreement.conf
+++ /dev/null
diff --git a/Artworks/Docs/Asciidoc/Distro/firefox_startpage.asciidoc b/Artworks/Docs/Asciidoc/Distro/firefox_startpage.asciidoc
deleted file mode 100644
index a512a38..0000000
--- a/Artworks/Docs/Asciidoc/Distro/firefox_startpage.asciidoc
+++ /dev/null
@@ -1,44 +0,0 @@
-Welcome to CentOS 5.8
-=====================
-The CentOS Project
-
-Abstract
---------
-
-CentOS 5.8 comes with no guarantees or warranties of any sorts, either written
-or implied. The Distribution is released as
-file:///usr/share/doc/centos-release-5/GPL[GPL] work. Individual packages in
-the distribution come with their own licences.
-
-What is CentOS?
----------------
-
-http://www.centos.org/[CentOS] is an Enterprise-class Linux Distribution
-derived from sources freely provided to the public by a prominent North
-American Enterprise Linux vendor. CentOS conforms fully with the upstream
-vendors redistribution policy and aims to be 100% binary compatible. (CentOS
-mainly changes packages to remove upstream vendor branding and artwork.)
-
-CentOS is developed by a small but growing team of core developers. In turn the
-core developers are supported by an active user community including system
-administrators, network administrators, enterprise users, managers, core Linux
-contributors and Linux enthusiasts from around the world.
-
-Advantages
-----------
-
-CentOS has numerous advantages including: an active and growing user community,
-quickly rebuilt, tested, and QA'ed errata packages, an extensive
-http://www.centos.org/modules/tinycontent/index.php?id=15[mirror network],
-developers who are contactable and responsive reliable Enterprise Linux class
-distribution, multiple free support avenues.
-
-Support
--------
-The following free support avenues are available:
-
-- http://www.centos.org/[The CentOS Website]
-- http://wiki.centos.org/[The CentOS Wiki] (includes a dynaic http://wiki.centos.org/FAQs[FAQ])
-- http://www.centos.org/modules/tinycontent/index.php?id=8[The CentOS IRC Chat]
-- http://lists.centos.org/[The CentOS Mailing lists]
-- http://forums.centos.org/[The CentOS Forums]
diff --git a/Artworks/Docs/Asciidoc/Distro/firefox_startpage.conf b/Artworks/Docs/Asciidoc/Distro/firefox_startpage.conf
deleted file mode 100644
index e69de29..0000000
--- a/Artworks/Docs/Asciidoc/Distro/firefox_startpage.conf
+++ /dev/null
diff --git a/Artworks/Docs/Asciidoc/Distro/rnotes.asciidoc b/Artworks/Docs/Asciidoc/Distro/rnotes.asciidoc
deleted file mode 100644
index 2ae9e49..0000000
--- a/Artworks/Docs/Asciidoc/Distro/rnotes.asciidoc
+++ /dev/null
@@ -1,26 +0,0 @@
-= CentOS =RELEASE= Release Notes
-The CentOS Project
-
-The CentOS =RELEASE= Release Notes are licensed under a
-http://creativecommons.org/licenses/by-sa/3.0/[Creative Common
-Attribution-ShareAlike 3.0 License].
-
-The CentOS Project welcomes you to CentOS =RELEASE=.
-
-The complete release notes for CentOS =RELEASE= can be found online at:
-http://wiki.centos.org/Manuals/ReleaseNotes/=RELEASE=/[http://wiki.centos.org/Manuals/ReleaseNotes/=RELEASE=/]
-
-A list of frequently asked questions and answers about CentOS =RELEASE= can be found
-online at: http://wiki.centos.org/FAQs/5/[http://wiki.centos.org/FAQs/5/]
-
-If you are looking for help with CentOS, we recommend you start at the
-http://wiki.centos.org/GettingHelp/[http://wiki.centos.org/GettingHelp/] for
-pointers to the different sources where
-you can get help.
-
-If you would like to contribute to The CentOS Project, see
-http://wiki.centos.org/HowToContribute/[http://wiki.centos.org/HowToContribute/]
-for areas where you could help.
-
-For more information about The CentOS Project in general please visit our
-homepage at: http://www.centos.org/[http://www.centos.org/]
diff --git a/Artworks/Docs/Asciidoc/Distro/rnotes.conf b/Artworks/Docs/Asciidoc/Distro/rnotes.conf
deleted file mode 100644
index b1bd285..0000000
--- a/Artworks/Docs/Asciidoc/Distro/rnotes.conf
+++ /dev/null
@@ -1,32 +0,0 @@
-[release-notes-final/release-notes.docbook]
-source = "release-notes.asciidoc"
-command = "asciidoc --backend=docbook"
-
-[release-notes-final/release-notes.xhtml]
-source = "release-notes-final/release-notes.docbook"
-command = "centos-art render --backend=xhtml"
-
-[release-notes-final/release-notes.pdf]
-source = "release-notes-final/release-notes.docbook"
-command = "centos-art render --backend=pdf"
-
-#
-# Add rendition support for different languages too. The following
-# lines are valid when LANG environment variable doesn't begin with
-# `en' characters.
-#
-
-[release-notes-final-${LANG}/release-notes.docbook]
-source = "release-notes-final/release-notes.docbook"
-localization = "release-notes-l10n/${LANG}.po"
-command = "centos-art render --backend=docbook"
-
-[release-notes-final-${LANG}/release-notes.xhtml]
-source = "release-notes-final-${LANG}/release-notes.docbook"
-localization = "release-notes-l10n/${LANG}.po"
-command = "centos-art render --backend=xhtml"
-
-[release-notes-final-${LANG}/release-notes.pdf]
-source = "release-notes-final-${LANG}/release-notes.docbook"
-localization = "release-notes-l10n/${LANG}.po"
-command = "centos-art render --backend=pdf"
diff --git a/Artworks/Docs/Asciidoc/Repository/centos-artwork.asciidoc b/Artworks/Docs/Asciidoc/Repository/centos-artwork.asciidoc
deleted file mode 100644
index e69de29..0000000
--- a/Artworks/Docs/Asciidoc/Repository/centos-artwork.asciidoc
+++ /dev/null
diff --git a/Artworks/Docs/Asciidoc/Repository/centos-artwork.conf b/Artworks/Docs/Asciidoc/Repository/centos-artwork.conf
deleted file mode 100644
index e69de29..0000000
--- a/Artworks/Docs/Asciidoc/Repository/centos-artwork.conf
+++ /dev/null
diff --git a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-author.docbook b/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-author.docbook
deleted file mode 100644
index 3d8d6a9..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-author.docbook
+++ /dev/null
@@ -1,6 +0,0 @@
-<author>
-
- <!-- centos-art(docbook): book.bookinfo.author.firtname -->
- <!-- centos-art(docbook): book.bookinfo.author.surname -->
-
-</author>
diff --git a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-copyright-holder.docbook b/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-copyright-holder.docbook
deleted file mode 100644
index ac998b8..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-copyright-holder.docbook
+++ /dev/null
@@ -1 +0,0 @@
-<holder>&TCP;. All rights reserved.</holder>
diff --git a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-copyright-year.docbook b/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-copyright-year.docbook
deleted file mode 100644
index df9b499..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-copyright-year.docbook
+++ /dev/null
@@ -1 +0,0 @@
-<year>YEAR</year>
diff --git a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-copyright.docbook b/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-copyright.docbook
deleted file mode 100644
index 78f0186..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-copyright.docbook
+++ /dev/null
@@ -1,4 +0,0 @@
-<copyright>
- <!-- centos-art(docbook): book.bookinfo.copyright.year -->
- <!-- centos-art(docbook): book.bookinfo.copyright.holder -->
-</copyright>
diff --git a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-legalnotice.docbook b/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-legalnotice.docbook
deleted file mode 100644
index 5cb78bc..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-legalnotice.docbook
+++ /dev/null
@@ -1,10 +0,0 @@
-<legalnotice>
- <para>
- 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 <xref linkend="licenses-gfdl" />.
- </para>
-</legalnotice>
diff --git a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-revhistory-revision.docbook b/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-revhistory-revision.docbook
deleted file mode 100644
index 7b09a2c..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-revhistory-revision.docbook
+++ /dev/null
@@ -1,8 +0,0 @@
-<revision>
-
- <!-- centos-art(docbook): book.bookinfo.revhistory.revision.revnumber
- <!-- centos-art(docbook): book.bookinfo.revhistory.revision.date
- <!-- centos-art(docbook): book.bookinfo.revhistory.revision.author
- <!-- centos-art(docbook): book.bookinfo.revhistory.revision.revdescription
-
-</revision>
diff --git a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-revhistory.docbook b/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-revhistory.docbook
deleted file mode 100644
index cd07a1c..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo-revhistory.docbook
+++ /dev/null
@@ -1,5 +0,0 @@
-<revhistory>
-
- <!-- centos-art(docbook): book.bookinfo.revhistory.revision -->
-
-</revhistory>
diff --git a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo.docbook b/Artworks/Docs/Docbook/Default/Book/Book-bookinfo.docbook
deleted file mode 100644
index 2cb60f9..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Book-bookinfo.docbook
+++ /dev/null
@@ -1,8 +0,0 @@
-<bookinfo>
-
- <!-- centos-art(docbook): book.bookinfo.author -->
- <!-- centos-art(docbook): book.bookinfo.copyright -->
- <!-- centos-art(docbook): book.bookinfo.legalnotice -->
- <!-- centos-art(docbook): book.bookinfo.revhistory -->
-
-</bookinfo>
diff --git a/Artworks/Docs/Docbook/Default/Book/Book-subtitle.docbook b/Artworks/Docs/Docbook/Default/Book/Book-subtitle.docbook
deleted file mode 100644
index b60a07e..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Book-subtitle.docbook
+++ /dev/null
@@ -1 +0,0 @@
-<subtitle>BOOKSUBTITLE</subtitle>
diff --git a/Artworks/Docs/Docbook/Default/Book/Book-title.docbook b/Artworks/Docs/Docbook/Default/Book/Book-title.docbook
deleted file mode 100644
index b54b481..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Book-title.docbook
+++ /dev/null
@@ -1,2 +0,0 @@
-<title>BOOKTITLE</title>
-<!-- centos-art(docbook): book.subtitle -->
diff --git a/Artworks/Docs/Docbook/Default/Book/Book.docbook b/Artworks/Docs/Docbook/Default/Book/Book.docbook
deleted file mode 100644
index b447fc9..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Book.docbook
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" []>
-
-<book lang="en_US">
-
- <!-- centos-art(docbook): book.title -->
- <!-- centos-art(docbook): book.bookinfo -->
- <!-- centos-art(docbook): book.preface -->
- <!-- centos-art(docbook): book.part -->
-
-</book>
diff --git a/Artworks/Docs/Docbook/Default/Book/Book.ent b/Artworks/Docs/Docbook/Default/Book/Book.ent
deleted file mode 100644
index af62731..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Book.ent
+++ /dev/null
@@ -1,58 +0,0 @@
-<!--
- $Id$
- This file defines entities for words and phrases frequently used
- inside The CentOS Artwork Repository User's Guide. It is a way of
- normalizing the use of concepts inside the documentation and make
- their maintainance easier to realize.
--->
-
-<!-- About Corporate Identity -->
-
-<!ENTITY CI "Corporate Identity">
-<!ENTITY CVI "Corporate Visual Identity">
-<!ENTITY CVIS "Corporate Visual Identity Structure">
-<!ENTITY MCVIS "Monolithic Corporate Visual Identity Structure">
-<!ENTITY VS "Visual Style">
-
-<!-- About The CentOS Project -->
-
-<!ENTITY C "CentOS">
-<!ENTITY TC "The &C;">
-<!ENTITY TCL "&TC; Logo">
-<!ENTITY TCS "&TC; Symbol">
-<!ENTITY TCT "&TC; Type">
-<!ENTITY TCB "&TC; Brand">
-<!ENTITY TCP "<ulink type='http' url='http://www.centos.org'>&TC; Project</ulink>">
-<!ENTITY TCC "&TC; Community">
-<!ENTITY TCD "&TC; Distribution">
-<!ENTITY TCA "&TC; Artwork">
-<!ENTITY TCM "<ulink url='http://mirrors.centos.org/'>&TC; Mirrors</ulink>">
-
-<!ENTITY TCPCI "&TCP; &CI;">
-<!ENTITY TCPCVI "&TCP; &CVI;">
-<!ENTITY TCPCVI "&TCP; &CVI;">
-<!ENTITY TCPCVIS "&TCP; &CVIS;">
-<!ENTITY TCPMCVIS "&TCP; &MCVIS;">
-
-<!ENTITY TCAR "<ulink type='https' url='https://projects.centos.org/svn/artwork'>&TCA; Repository</ulink>">
-<!ENTITY TCAS "<ulink type='https' url='https://projects.centos.org/trac/artwork'>&TCA; SIG</ulink>">
-
-<!ENTITY TCARUG "<citetitle>The CentOS Artwork Repository User's Guide</citetitle>">
-<!ENTITY TCDRS "&TCD; Release Schema">
-<!ENTITY TCAML "<email>centos-artwork@centos.org</email> mailing list">
-<!ENTITY TCDML "<email>centos-devel@centos.org</email> mailing list">
-<!ENTITY TCML "<email>centos-info@centos.org</email> mailing list">
-<!ENTITY TCW "&TC; Web">
-<!ENTITY TCWE "&TCW; Environment">
-<!ENTITY TCWIKI "<ulink type='http' url='http://wiki.centos.org/'>&TC; Wiki</ulink>">
-<!ENTITY TCML "<ulink type='http' url='http://lists.centos.org/'>&TC; Mailing Lists</ulink>">
-
-<!ENTITY TCS "&TC; Showroom">
-<!ENTITY TCBRAND "&TC; Brand">
-<!ENTITY TCLOGO "<xref linkend='identity-brand-logo' />">
-<!ENTITY TCTYPE "<xref linkend='identity-brand-type' />">
-<!ENTITY TCSYMBOL "<xref linkend='identity-brand-symbol' />">
-<!ENTITY TCMOTIF "<xref linkend='identity-brand-motif' />">
-<!ENTITY TCM "&TC; Mission">
-<!ENTITY TCDOCS "<ulink type='http' url='http://www.centos.org/docs/'>&TC; Documentation</ulink>">
-
diff --git a/Artworks/Docs/Docbook/Default/Book/Part-partintro.docbook b/Artworks/Docs/Docbook/Default/Book/Part-partintro.docbook
deleted file mode 100644
index c8467b4..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Part-partintro.docbook
+++ /dev/null
@@ -1,3 +0,0 @@
-<partintro>
- <!-- centos-art(dobook): book.part.partintro.para -->
-</partintro>
diff --git a/Artworks/Docs/Docbook/Default/Book/Part.docbook b/Artworks/Docs/Docbook/Default/Book/Part.docbook
deleted file mode 100644
index 7f13f50..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Part.docbook
+++ /dev/null
@@ -1,8 +0,0 @@
-<part id="PART_NAME">
-
- <title>PART_TITLE</title>
-
- <!-- centos-art(docbook): book.part.partintro -->
- <!-- centos-art(docbook): book.part.chapter -->
-
-</part>
diff --git a/Artworks/Docs/Docbook/Default/Book/Part/Chapter.docbook b/Artworks/Docs/Docbook/Default/Book/Part/Chapter.docbook
deleted file mode 100644
index 19f5bf7..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Part/Chapter.docbook
+++ /dev/null
@@ -1,7 +0,0 @@
-<chapter id="CHAPTER_ID">
-
- <title>CHAPTER_TITLE</title>
-
- <!-- centos-art.sh(docbook): book.part.chapters.sections -->
-
-</chapter>
diff --git a/Artworks/Docs/Docbook/Default/Book/Part/Chapter/section.docbook b/Artworks/Docs/Docbook/Default/Book/Part/Chapter/section.docbook
deleted file mode 100644
index 1ca0bd5..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Part/Chapter/section.docbook
+++ /dev/null
@@ -1,13 +0,0 @@
-<SECTION_TAG id="SECTION_ID">
-
- <title>SECTION_TITLE</title>
-
- <para>
- Write the section content here.
- </para>
-
- <para>
- ...
- </para>
-
-</SECTION_TAG>
diff --git a/Artworks/Docs/Docbook/Default/Book/Preface.docbook b/Artworks/Docs/Docbook/Default/Book/Preface.docbook
deleted file mode 100644
index 42c8578..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Preface.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<preface id="preface">
-
- <title>Preface</title>
-
- &preface-overview;
- &preface-docconvs;
- &preface-feedback;
-
-</preface>
diff --git a/Artworks/Docs/Docbook/Default/Book/Preface/docconvs.docbook b/Artworks/Docs/Docbook/Default/Book/Preface/docconvs.docbook
deleted file mode 100644
index 17509ca..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Preface/docconvs.docbook
+++ /dev/null
@@ -1,225 +0,0 @@
-<section id="preface-docconvs">
-
- <title>Document Convenctions</title>
-
- <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>
-
- <variablelist>
- <varlistentry>
- <term><command>command</command></term>
- <listitem>
- <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 <keycap>Enter</keycap> 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 render
- Identity/Images/Themes/TreeFlower/4/Distro/5/Anaconda
- --filter="01-welcome"</command> command to produce the first
- slide image used by Anaconda in the branch 5 of &TCD;
- using the version 4 of TreeFlower artistic motif.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>file name</filename></term>
- <listitem>
- <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">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
- <filename>ImageMagick</filename> RPM package to convert
- images from PNG format to other formats.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><keycap>key</keycap></term>
- <listitem>
- <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</command>, then a
- character, and finally the <keycap>Tab</keycap> key. Your
- terminal displays the list of files in the working
- directory that begin with that character.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><keycombo action="simul"><keycap>key</keycap><keycap>combination</keycap></keycombo></term>
- <listitem>
- <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>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><computeroutput>computer output</computeroutput></term>
- <listitem>
- <para>
- Text in this style indicates text displayed to a shell
- prompt such as error messages and responses to commands.
- For example, the <command>ls</command> command displays
- the contents of a directory using this style:
- </para>
-
-<screen>
-render_doTranslation.sh render_getDirTemplate.sh render_doBaseActions.sh
-render_getConfigOption.sh render_getOptions.sh render_doThemeActions.sh
-render_getDirOutput.sh render.sh
-</screen>
-
- <para>
- The output returned in response to the command (in this
- case, the contents of the directory) is shown in this
- style.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><prompt>prompt</prompt></term>
- <listitem>
- <para>
- A prompt, which is a computer's way of signifying that it
- is ready for you to input something, is shown in this
- style. Examples:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <prompt>$</prompt>
- </para>
- </listitem>
- <listitem>
- <para>
- <prompt>#</prompt>
- </para>
- </listitem>
- <listitem>
- <para>
- <prompt>[centos@projects centos]$</prompt>
- </para>
- </listitem>
- <listitem>
- <para>
- <prompt>projects login:</prompt>
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><userinput>user input</userinput></term>
- <listitem>
- <para>
- Text that the user types, either on the command line or
- into a text box on a GUI screen, is displayed in this
- style. In the following example,
- <userinput>text</userinput> is displayed in this style: To
- boot your system into the text based installation program,
- you must type in the <userinput>text</userinput> command
- at the <prompt>boot:</prompt> prompt.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><replaceable>replaceable</replaceable></term>
- <listitem>
- <para>
- Text used in examples that is meant to be replaced with
- data provided by the user is displayed in this style. In
- the following example,
- <replaceable>version-number</replaceable> is displayed in
- this style: The directory for the kernel source is
- <filename
- class="directory">/usr/src/kernels/<replaceable>version-number</replaceable>/</filename>,
- where <replaceable>version-number</replaceable> is the
- version and type of kernel installed on this system.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <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 <filename
- class="directory">/usr/share/doc/</filename> 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/Artworks/Docs/Docbook/Default/Book/Preface/feedback.docbook b/Artworks/Docs/Docbook/Default/Book/Preface/feedback.docbook
deleted file mode 100644
index 14cc875..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Preface/feedback.docbook
+++ /dev/null
@@ -1,43 +0,0 @@
-<section id="preface-feedback">
-
- <title>Send In Your Feedback</title>
-
- <para>
- &TCAR; is an ongoing work which might contain errors and
- require new features. If you find errors inside &TCAR; or have
- any suggestion, we want to know about it.
- </para>
-
- <para>
- To report errors and suggestions about &TCAR; you need to do
- the following:
- </para>
-
- <orderedlist>
- <listitem>
- <para>
- <ulink url="https://projects.centos.org/trac/artwork/register">Register yourself in the bug tracker</ulink>.</ulink>
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://projects.centos.org/trac/artwork/login">Log in the bug tracker using your account.</ulink>
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="https://projects.centos.org/trac/artwork/newticket">Write a new ticket in the bug tracker using your account.</ulink>
- </para>
- </listitem>
-
- <para>
- While you are writing your feedback report, please keep in
- mind that it is very useful that you be specific about the
- issue you are reporting in order for others be able of
- reproducing it and, this way, find a solution for it. For
- example, consider to include all the error messages you see in
- your screen and the exact order of commands you used to
- perform actions when using the centos-art.sh script.
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Default/Book/Preface/overview.docbook b/Artworks/Docs/Docbook/Default/Book/Preface/overview.docbook
deleted file mode 100644
index 34d81db..0000000
--- a/Artworks/Docs/Docbook/Default/Book/Preface/overview.docbook
+++ /dev/null
@@ -1,13 +0,0 @@
-<section id="preface-overview">
-
- <title>Overview</title>
-
- <para>
- Summarize, in a few paragraphs, what this book is all about.
- </para>
-
- <para>
- ...
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Default/Licenses/Gfdl/gfdl.docbook b/Artworks/Docs/Docbook/Default/Licenses/Gfdl/gfdl.docbook
deleted file mode 100644
index 89b468a..0000000
--- a/Artworks/Docs/Docbook/Default/Licenses/Gfdl/gfdl.docbook
+++ /dev/null
@@ -1,608 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" []>
-
-<appendix id="licenses-gfdl">
-
- <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>
-
- <sect1 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" />, 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>
-
- </sect1>
-
- <sect1 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 id="modified-version" xreflabel="Modified Version">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 id="secondary-section" xreflabel="Secondary Section">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 <xref linkend="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 id="invariant-sections" xreflabel="Invariant
- Sections">The <quote>Invariant Sections</quote> are certain
- <xref linkend="secondary-section" /> 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 Section then
- there are none.</para>
-
- <para id="cover-texts" xreflabel="Cover Texts">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 id="transparent" xreflabel="Transparent">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 <xref linkend="transparent" /> file format whose
- markup, or absence of markup, has been arranged to thwart or
- discourage subsequent modification by readers is not <xref
- linkend="transparent" />. An image format is not <xref
- linkend="transparent" /> if used for any substantial amount of
- text. A copy that is not <quote><xref linkend="transparent"
- /></quote> is called <quote>Opaque</quote>.</para>
-
- <para>Examples of suitable formats for <xref linkend="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 id="title-page" xreflabel="Title Page">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>
-
- </sect1>
-
- <sect1 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>
-
- </sect1>
-
- <sect1 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 <xref linkend="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 <xref linkend="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 <xref linkend="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 <xref linkend="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>
-
- </sect1>
-
- <sect1 id="licenses-gfdl-section-5" xreflabel="Modification">
-
- <title>Modifications</title>
-
- <para>
- You may copy and distribute a <xref
- linkend="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 <xref linkend="modified-version" /> under
- precisely this License, with the <xref
- linkend="modified-version" /> filling the role of the
- Document, thus licensing distribution and modification of
- the <xref linkend="modified-version" /> to whoever
- possesses a copy of it. In addition, you must do these
- things in the <xref linkend="modified-version" />:
- </para>
-
- <orderedlist numeration="upperalpha">
-
- <listitem>
- <para>Use in the <xref linkend="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 <xref linkend="title-page" />, as
- authors, one or more persons or entities responsible
- for authorship of the modifications in the <xref
- linkend="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 <xref linkend="title-page" /> the
- name of the publisher of the <xref
- linkend="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 <xref linkend="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 <xref linkend="invariant-sections" /> and required
- <xref linkend="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 <xref
- linkend="modified-version" /> as given on the <xref
- linkend="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 <xref linkend="title-page"
- />, then add an item describing the <xref
- linkend="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 <xref
- linkend="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 <xref
- linkend="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 <xref linkend="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 <xref linkend="invariant-sections"
- />.</para> </listitem>
-
- <listitem>
- <para>Preserve any Warranty Disclaimers.</para>
- </listitem>
- </orderedlist>
-
- <para>
- If the <xref linkend="modified-version" /> includes new
- front-matter sections or appendices that qualify as <xref
- linkend="secondary-section" /> 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 <xref
- linkend="invariant-sections"/> in the <xref
- linkend="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 <xref linkend="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 <xref
- linkend="cover-texts"/> in the <xref
- linkend="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
- <xref linkend="modified-version" />.
- </para>
-
- </sect1>
-
- <sect1 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 <xref linkend="invariant-sections"/> of
- all of the original documents, unmodified, and list them all
- as <xref linkend="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 <xref
- linkend="invariant-sections"/> may be replaced with a single
- copy. If there are multiple <xref
- linkend="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 <xref linkend="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>
-
- </sect1>
-
- <sect1 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>
-
- </sect1>
-
- <sect1 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 <xref
- linkend="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>
-
- </sect1>
-
- <sect1 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
- <xref linkend="invariant-sections" />with translations
- requires special permission from their copyright holders, but
- you may include translations of some or all <xref
- linkend="invariant-sections" /> in addition to the original
- versions of these <xref linkend="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>
-
- </sect1>
-
- <sect1 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>
-
- </sect1>
-
- <sect1 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>
-
- </sect1>
-
- <sect1 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>
-
-<screen>
-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>.
-</screen>
-
- <para>If you have <xref linkend="invariant-sections" />,
- Front-Cover Texts and Back-Cover Texts, replace the
- <quote>with...Texts</quote>. line with this:</para>
-
-<screen>
-with the Invariant Sections being LIST THEIR TITLES, with the
-Front-Cover Texts being LIST, and with the Back-Cover Texts being
-LIST.
-</screen>
-
- <para>If you have <xref linkend="invariant-sections" />
- without <xref linkend="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>
-
- </sect1>
-
-</appendix>
diff --git a/Artworks/Docs/Docbook/Default/Licenses/Gpl/gpl.docbook b/Artworks/Docs/Docbook/Default/Licenses/Gpl/gpl.docbook
deleted file mode 100644
index 7394198..0000000
--- a/Artworks/Docs/Docbook/Default/Licenses/Gpl/gpl.docbook
+++ /dev/null
@@ -1,539 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" []>
-<appendix id="licenses-gpl">
-
- <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>
-
- <sect1 id="licenses-gpl-0" xreflabel="Preamble">
-
- <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:
- </para>
-
- <orderedlist numeration="arabic">
- <listitem>
- <para>copyright the software, and</para>
- </listitem>
- <listitem>
- <para>offer you this license which gives you legal
- permission to copy, distribute and/or modify the
- software.</para>
- </listitem>
- </orderedlist>
-
- <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>
-
- </sect1>
-
- <sect1 id="licenses-gpl-1">
-
- <title>Terms and Conditions for Copying, Distribution and Modification</title>
-
- <sect2 id="licenses-gpl-1-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>
-
- </sect2>
-
- <sect2 id="licenses-gpl-1-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 <xref linkend="licenses-gpl-1-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.
- </para>
- </listitem>
- </orderedlist>
-
- <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>
- 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>
-
- </sect2>
-
- <sect2 id="licenses-gpl-1-3" xreflabel="Section 3">
-
- <title>Section 3</title>
-
- <para>
- You may copy and distribute the Program (or a work based on
- it, under <xref linkend="licenses-gpl-1-2" />) in object code
- or executable form under the terms of <xref
- linkend="licenses-gpl-1-1" /> and <xref
- linkend="licenses-gpl-1-2" /> above provided that you also do
- one of the following:
- </para>
-
- <orderedlist numeration="loweralpha">
- <listitem>
- <para>
- Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of
- <xref linkend="licenses-gpl-1-1" /> and <xref
- linkend="licenses-gpl-1-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 <xref
- linkend="licenses-gpl-1-1" /> and <xref
- linkend="licenses-gpl-1-2" /> above on a medium customarily
- used for software interchange; or,
- </para>
- </listitem>
-
- <listitem>
- <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>
- 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>
-
- </sect2>
-
- <sect2 id="licenses-gpl-1-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>
-
- </sect2>
-
- <sect2 id="licenses-gpl-1-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>
-
- </sect2>
-
- <sect2 id="licenses-gpl-1-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>
-
- </sect2>
-
- <sect2 id="licenses-gpl-1-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>
-
- </sect2>
-
- <sect2 id="licenses-gpl-1-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>
-
- </sect2>
-
- <sect2 id="licenses-gpl-1-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>
-
- </sect2>
-
- <sect2 id="licenses-gpl-1-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>
-
- </sect2>
-
- <sect2 id="licenses-gpl-1-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>
-
- </sect2>
-
- <sect2 id="licenses-gpl-1-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>
-
- </sect2>
-
- </sect1>
-
- <sect1 id="licenses-gpl-2" xreflabel="How to Apply These Terms to Your New Programs">
-
- <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>
-
-<screen>
-<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.
-</screen>
-
- <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>
-
-<screen>
-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.
-</screen>
-
- <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>
-
-<screen>
-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
-</screen>
-
- <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>
-
- </sect1>
-
-</appendix>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity.docbook
deleted file mode 100644
index d36b086..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity.docbook
+++ /dev/null
@@ -1,17 +0,0 @@
-<part id="identity">
-
- <title>Corporate Visual Identity</title>
-
- <partintro>
- <para>
- ...
- </para>
- </partintro>
-
- &identity-project;
- &identity-brand;
- &identity-distro;
- &identity-web;
- &identity-showroom;
-
-</part>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity.ent b/Artworks/Docs/Docbook/Tcar-ug/Identity.ent
deleted file mode 100644
index 144c375..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity.ent
+++ /dev/null
@@ -1,19 +0,0 @@
-<!ENTITY identity SYSTEM "Identity.docbook">
-<!ENTITY identity-project SYSTEM "Identity/Project.docbook">
-<!ENTITY identity-project-mission SYSTEM "Identity/Project/mission.docbook">
-<!ENTITY identity-project-behaviour SYSTEM "Identity/Project/behaviour.docbook">
-<!ENTITY identity-project-communication SYSTEM "Identity/Project/communication.docbook">
-<!ENTITY identity-project-design SYSTEM "Identity/Project/design.docbook">
-<!ENTITY identity-project-structure SYSTEM "Identity/Project/structure.docbook">
-
-<!ENTITY identity-brand SYSTEM "Identity/Brand.docbook">
-<!ENTITY identity-brand-intro SYSTEM "Identity/Brand/intro.docbook">
-<!ENTITY identity-brand-symbol SYSTEM "Identity/Brand/symbol.docbook">
-<!ENTITY identity-brand-type SYSTEM "Identity/Brand/type.docbook">
-<!ENTITY identity-brand-logo SYSTEM "Identity/Brand/logo.docbook">
-<!ENTITY identity-brand-motif SYSTEM "Identity/Brand/motif.docbook">
-<!ENTITY identity-distro SYSTEM "Identity/Distribution.docbook">
-<!ENTITY identity-showroom SYSTEM "Identity/Showroom.docbook">
-
-<!ENTITY identity-web SYSTEM "Identity/Web.docbook">
-<!ENTITY identity-web-intro SYSTEM "Identity/Web/intro.docbook">
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand.docbook
deleted file mode 100644
index 0c0ba19..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand.docbook
+++ /dev/null
@@ -1,11 +0,0 @@
-<chapter id="identity-brand">
-
- <title>The CentOS Brand</title>
-
- &identity-brand-intro;
- &identity-brand-symbol;
- &identity-brand-type;
- &identity-brand-logo;
- &identity-brand-motif;
-
-</chapter>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/intro.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/intro.docbook
deleted file mode 100644
index 84a602a..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/intro.docbook
+++ /dev/null
@@ -1,49 +0,0 @@
-<sect1 id="identity-brand-intro">
-
- <title>Introduction</title>
-
- <para>
- &TCBRAND; is the main visual manifestaion of &TCP;. &TCP;
- uses &TCBRAND; to connect all the visual manifestions it is
- made of (e.g., GNU/Linux Distributions, Web sites, Stationery,
- etc.) and, this way, provides recognition
- <footnote>
- <para>
- ... just as a GPG signature might do for RPM packages.
- </para>
- </footnote>
- among similar projects available on the Internet. The CentOS
- Brand is made of a graphical component (&TCSYMBOL;) and a
- typographical component (&TCTYPE;) that, when put together,
- make &TCLOGO;. The components that make &TCBRAND; can be used
- together or separately, considering that, in hierarchy order,
- &TCLOGO; is rather prefered than &TCSYMBOL;, as well as
- &TCSYMBOL; is rather prefered than &TCTYPE;.
- </para>
-
- <para>
- In addition to those components mentioned above, &TCBRAND;
- includes another component named &TCMOTIF;. &TCMOTIF; is
- mainly used as background on images and is directly related to
- the look and feel of all visual manifestations &TCP; shows its
- existence on. In contrast with &TCLOGO;, &TCSYMBOL; and
- &TCTYPE;; &TCMOTIF; might change from time to time providing a
- vehicle to <quote>refresh</quote> how &TCP; looks and feels.
- </para>
-
- <para>
- &TCBRAND; and all the visual manifestations derivated from it
- are available for you to study and propose improvement around
- a good citizen's will inside &TCC;, but you are not allowed to
- redistribute them elsewhere, without the given permission of
- &TCP;.
- </para>
-
- <para>
- If you need to redistribute either &TCLOGO; or any visual
- manifestation derived from it, write your intentions to the
- The CentOS Developers mailing list (<ulink
- url="mailto:centos-devel@centos.org">centos-devel@centos.org</ulink>).
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/logo.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/logo.docbook
deleted file mode 100644
index ee01fda..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/logo.docbook
+++ /dev/null
@@ -1,17 +0,0 @@
-<sect1 id="identity-brand-logo" xreflabel="&TCL;">
-
- <title>&TCL;</title>
-
- <para>
- &TCL; is a construction made of &TCS; and &TCT;. &TCS; and
- &TCL; are the main visual manifestations of the organization
- known as &TCP;. As &TCS;, &TCL; is used to
- <quote>brand</quote> images produced by &TCP; and provide a
- visual connection between images so they can be monolithically
- recognized as part of &TCP;. &TCL; must be exactly the same
- every time it is printed out and a route to reproduce it in
- such a way must be available so as to avoid reproduction
- mistakes when images are branded with it.
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/motif.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/motif.docbook
deleted file mode 100644
index 7341757..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/motif.docbook
+++ /dev/null
@@ -1,5 +0,0 @@
-<sect1 id="identity-brand-motif" xreflabel="The CentOS Motif">
- <title>The CentOS Motif</title>
- <para>...</para>
-</sect1>
-
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/symbol.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/symbol.docbook
deleted file mode 100644
index 7ddeb03..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/symbol.docbook
+++ /dev/null
@@ -1,15 +0,0 @@
-<sect1 id="identity-brand-symbol" xreflabel="&TCS;">
-
- <title>&TCS;</title>
-
- <para>
- &TCS; is the graphical part of &TCL;. As &TCL;, &TCS; is used
- to <quote>brand</quote> images produced by &TCP; and provide a
- visual connection between images so they can be monolithically
- recognized as part of &TCP;. &TCS; must be exactly the same
- every time it is printed out and a route to reproduce it in
- such a way must be available so as to avoid reproduction
- mistakes when images are branded with it.
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/type.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/type.docbook
deleted file mode 100644
index d76106b..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Brand/type.docbook
+++ /dev/null
@@ -1,17 +0,0 @@
-<sect1 id="identity-brand-type" xreflabel="&TCT;">
-
- <title>&TCT;</title>
-
- <para>
- &TCT; is the typographical part of &TCL;. Comparing with both
- &TCL; and &TCS;, &TCT; by its own, provides poor visual
- connection between images that intend to be recognized as a
- monolithic part of &TCP; and shouldn't be used alone.
- Instead, &TCL; or &TCS; are preferred. &TCS; must be exactly
- the same every time it is printed out and a route to reproduce
- it in such a way must be available so as to avoid reproduction
- mistakes when images are branded with it.
- </para>
-
-</sect1>
-
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Distribution.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Distribution.docbook
deleted file mode 100644
index 0236910..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Distribution.docbook
+++ /dev/null
@@ -1,16 +0,0 @@
-<chapter id="identity-distro">
-
- <title>The CentOS Distribution</title>
- <para>...</para>
-
- <sect1>
- <title>Release Schema</title>
- <para>...</para>
- </sect1>
-
- <sect1>
- <title>...</title>
- <para>...</para>
- </sect1>
-
-</chapter>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Project.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Project.docbook
deleted file mode 100644
index 3634415..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Project.docbook
+++ /dev/null
@@ -1,41 +0,0 @@
-<chapter id="identity-project">
-
- <title>The CentOS Project</title>
-
- <para>
- The CentOS Project Corporate Identity is the
- <quote>persona</quote> 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 Corporate Design,
- Corporate Communication, and Corporate Behaviour.
- </para>
-
- <figure id="identity-project-structure-fig1">
- <title>The CentOS Project Corporate Identity.</title>
- <screenshot>
- <screeninfo>The CentOS Project Corporate Identity.</screeninfo>
- <mediaobject>
- <imageobject>
- <imagedata fileref="=TCAR_WORKDIR=/Documentation/Manuals/Svg/Corporate/monolithic.png" format="PNG" />
- </imageobject>
- </mediaobject>
- </screenshot>
- </figure>
-
- &identity-project-mission;
- &identity-project-design;
- &identity-project-communication;
- &identity-project-behaviour;
- &identity-project-structure;
-
-</chapter>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/behaviour.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/behaviour.docbook
deleted file mode 100755
index bd22f04..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/behaviour.docbook
+++ /dev/null
@@ -1,21 +0,0 @@
-<sect1 id="identity-project-behaviour">
-
- <title>Corporate Behaviour</title>
-
- <para>
- &TCP; corporate behaviour is focused on the effective
- interaction of each member involved in the organization (e.g.,
- core developers, community members, etc.). It is related to
- ethics and politics used to do the things inside the
- organization. It is related to the sense of direction chosen
- by the organization and they way the organization projects
- itself to achieve it.
- </para>
-
- <para>
- &TCP; corporate behaviour takes place through &TCP; corporate
- communication, as described in <xref
- linkend="identity-project-communication" />.
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/communication.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/communication.docbook
deleted file mode 100755
index c46dd12..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/communication.docbook
+++ /dev/null
@@ -1,141 +0,0 @@
-<sect1 id="identity-project-communication">
-
- <title>Corporate Communication</title>
-
- <para>
- &TCP; corporate communication is focused on the effective
- propagation of corporate messages. Propagation of corporate
- messages is closely related to the media the organization uses
- as vehicle to distribute its corporate messages.
- </para>
-
- <para>
- &TCP; corporate communication takes place through the
- following visual manifestations:
- </para>
-
- <variablelist>
-
- <varlistentry>
- <term>&TCD;</term>
- <listitem>
- <para>
- This visual manifestation communicates its existence
- through software packages. There are packages that make a
- remarkable use of images, packages that make a moderate
- use of images, and packages that don't use images at all.
- This visual manifestation is focused on providing &TCP;
- images required by software packages that do use images in
- a remarkable way, specially those holding the upstream
- brand (e.g., <package>anaconda</package>,
- <package>grub</package>, <package>syslinux</package>,
- <package>gdm</package>, <package>kdebase</package>).
- </para>
- <itemizedlist>
- <listitem>
- <para>
- The Community Enterprise Operating System itself
- (communicates the essense of &TCP; existence.).
- </para>
- </listitem>
- <listitem>
- <para>
- Release Schema (Lifetime) and all the stuff related (e.g.,
- Release Notes, Documentation, Erratas, etc.).
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&TCW;</term>
- <listitem>
- <para>
- This visual manifestation communicates its existence
- through web applications. 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. Removing
- these visual contraditions is object of work for this
- visual manifestation.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- The CentOS Chat.
- </para>
- </listitem>
- <listitem>
- <para>
- The CentOS Mailing Lists.
- </para>
- </listitem>
- <listitem>
- <para>
- The CentOS Forums.
- </para>
- </listitem>
- <listitem>
- <para>
- The CentOS Wiki.
- </para>
- </listitem>
- <listitem>
- <para>
- Special Interest Groups (SIGs).
- </para>
- </listitem>
- <listitem>
- <para>
- Social Events, Interviews, Conferences, etc.
- </para>
- </listitem>
- <listitem>
- <para>
- The extensive network of mirrors available for downloading
- ISO files as well as RPMs and SRPMs used to build them up
- in different architectures.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&TCS;</term>
- <listitem>
- <para>
- This visual manifestation communicates its existence
- through production of industrial objects carrying &TCBRAND;.
- These branded objects are directed to be distributed on
- social events and/or shops. They provide a way of
- promotion and commercialization that may help to reduce
- &TCP; expenses (e.g., electrical power, hosting, servers,
- full-time-developers, etc.), in a similar way as donations
- may do.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Stationery (e.g., Posters, Stickers, CD Lables and Sleeves).
- </para>
- </listitem>
- <listitem>
- <para>
- Clothes (e.g., Shirts, T-shirts, Pullovers, Caps).
- </para>
- </listitem>
- <listitem>
- <para>
- Installation media (e.g., CDs, DVD, Pendrives).
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </varlistentry>
- </variablelist>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/design.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/design.docbook
deleted file mode 100755
index 7429c7f..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/design.docbook
+++ /dev/null
@@ -1,96 +0,0 @@
-<sect1 id="identity-project-design">
-
- <title>Corporate Graphic Design</title>
-
- <para>
- The corporate design is focused on the effective presentation
- of corporate messages. As corporate messages we understand all
- the information emitted from the organization; and when we say
- <emphasis>all</emphasis> we mean everything that can be
- perceived through the human senses. The corporate design takes
- care of defining what this information is and controlling the
- way it goes out the organization producing it.
- </para>
-
- <para>
- When the organization doesn't take control over the corporate
- messages it produces, the organization is letting that area of
- its identity to the unknown and the results might be good or
- not so good, it is hard to know. The issue to see here is
- that even the organization doesn't take control over its
- corporate messages, they are always talking about the
- organization. Taking control of corporate messages is a
- decition the organization needs to take by itself, based on
- its need of better describe what it is.
- </para>
-
- <para>
- In the very specific case of &TCP;, we'll concentrate our
- attention on corporate messages that reach us through the
- visual sense. This is, all the visual manifestations &TCP; is
- made of. As visual manifestaions we understand all the visible
- media &TCP; uses to manifest its existence on. At this point
- it is necessary to consider what &TCP; is, what its mission is
- and what it is producing. This, in order to identify which
- visual manifestations the organization is demanding attention
- of corporate design for.
- </para>
-
- <para>
- Inside &TCP; we identify and apply corporate design to the
- following visual manifestations:
- </para>
-
- <orderedlist numeration="arabic">
-
- <listitem>
- <para>
- &TCD; — This visual manifestation exists to cover all
- actions related to artwork production and rebranding, required
- by &TCD; in order to comply with upstream's redistribution
- guidelines. This visual manifestation is described in <xref
- linkend="identity-distro" />.
- </para>
- </listitem>
-
- <listitem>
- <para>
- &TCW; — This visual manifestation exists to cover all
- actions related to artwork production required by &TCP; to
- manifest its existence in the World Wide Web medium. This
- visual manifestation is described in <xref
- linkend="identity-web" />.
- </para>
- </listitem>
-
- <listitem>
- <para>
- &TCS; — This visual manifestation exists to cover all
- actions related to artwork production required by &TCP; to
- manifest its existence through media produced industrially
- (e.g., stationery, clothes, CDs, DVDs, etc.). This visual
- manifestation is described in <xref
- linkend="identity-showroom" />.
- </para>
- </listitem>
- </orderedlist>
-
- <para>
- The visual manifestations identified above seem to cover most
- media required by &TCP;, as organization, to show its
- existence. However, other visual manifestations could be
- added in the future, as long as they be needed, to cover
- different areas like stands, buildings, offices, road
- transportation or whaterver visual manifestation &TCP;
- thouches to show its existence.
- </para>
-
- <para>
- Once all visual manifestations have been identified and
- defined through design models, it is time to visually remark
- their connection with &TCP;. This kind of connection is
- realized by applying &TCBRAND; to design models inside visual
- manifestations supported through corporate design.
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/mission.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/mission.docbook
deleted file mode 100644
index 507873d..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/mission.docbook
+++ /dev/null
@@ -1,40 +0,0 @@
-<sect1 id="identity-project-mission">
-
- <title>Corporate Mission</title>
-
- <para>
- &TCP; exists to produce &TCD;, an Enterprise-class Linux
- Distribution derived from sources freely provided to the
- public by a prominent North American Enterprise Linux vendor.
- &TCD; conforms fully with the upstream vendors redistribution
- policy and aims to be 100% binary compatible. (&TCD; mainly
- changes packages to remove upstream vendor branding and
- artwork.).
- </para>
-
- <para>
- &TCD; is developed by a small but growing team of core
- developers. In turn the core developers are supported by an
- active user community including system administrators, network
- administrators, enterprise users, managers, core Linux
- contributors and Linux enthusiasts from around the world.
- </para>
-
- <para>
- &TCD; has numerous advantages including: an active and growing
- user community, quickly rebuilt, tested, and QA'ed errata
- packages, an extensive mirror network, developers who are
- contactable and responsive of a reliable Enterprise-class
- Linux Distribution, multiple free support avenues including a
- <ulink type="http" url="http://wiki.centos.org/">Wiki</ulink>,
- <ulink type="http"
- url="http://www.centos.org/modules/tinycontent/index.php?id=8">IRC
- Chat</ulink>, <ulink type="http"
- url="http://lists.centos.org/">Email Lists</ulink>, <ulink
- type="http"
- url="http://www.centos.org/modules/newbb/">Forums</ulink>, and
- a dynamic <ulink type="http"
- url="http://www.centos.org/modules/smartfaq/">FAQ</ulink>.
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/structure.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/structure.docbook
deleted file mode 100755
index a0d20f9..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Project/structure.docbook
+++ /dev/null
@@ -1,91 +0,0 @@
-<sect1 id="identity-project-structure">
-
- <title>Corporate Structure</title>
-
- <para>
- &TCP; corporate structure is based on a &MCVIS;. In this
- configuration, one unique name and one unique visual style is
- used in all visual manifestation &TCP; is made of.
- </para>
-
- <para>
- In a monolithic corporate visual identity structure, internal
- and external stakeholders use to 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:
- Hey! we are all part of &TCP;.
- </para>
-
- <para>
- Other corporate structures for &TCP; have been considered as
- well. Such is the case of producing one different visual style
- for each major release of &TCD;. 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 &TCP;
- is made of.
- </para>
-
- <para>
- &TCP;, as organization, is mainly made of (but not limited to)
- three visual manifestions: &TCD;, &TCW; and &TCS;. Inside
- &TCD; visual manifestations, &TCP; maintains near to four
- different major releases of &TCD;, parallely in time.
- However, inside &TCW; 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 &TCD;
- individually, but one web site to cover them all). Likewise,
- the content produced in &TCS; is industrially created for no
- specific release, but &TCP; in general.
- </para>
-
- <para>
- In order to produce the &TCPMCVIS; correctly, we need to
- concider all the visual manifestations &TCP; is made of, not
- just one of them. If one different visual style is
- implemented for each major release of &TCD;, which one of
- those different visual styles would be used to cover the
- remaining visual manifestations &TCP; is made of (e.g., &TCW;
- and &TCS;)?
- </para>
-
- <para>
- Probably you are thinking: yes, I see your point, but &TCBRAND;
- 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 &TCP; 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. With
- that in mind, we consider &TCPCVIS; must be consequent with
- such stability and consistency tradition. It is true that
- &TCBRAND; does connect all the visual manifestations it is present
- on, but that connection is strengthened if one unique visual
- style backups it. In fact, whatever thing you do to strength
- the visual connection among &TCP; visual manifestations would
- be very good in favor of &TCP; recognition.
- </para>
-
- <para>
- Obviously, having just one visual style in all visual
- manifestations for eternity would be a very boring thing and
- would give the idea of a visually dead project. So, there is
- no problem on creating a brand new visual style for each new
- major release of &TCD;, in order to refresh &TCD; visual
- style; the problem itself is in not propagating the brand new
- visual style created for the new release of &TCD; to all other
- visual manifestations &TCP; is made of, in a way &TCP; could
- be recognized no matter what visual 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 &TCAR;.
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Showroom.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Showroom.docbook
deleted file mode 100644
index db87232..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Showroom.docbook
+++ /dev/null
@@ -1,11 +0,0 @@
-<chapter id="identity-showroom">
-
- <title>The CentOS Showroom</title>
- <para>...</para>
-
- <sect1>
- <title>...</title>
- <para>...</para>
- </sect1>
-
-</chapter>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Web.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Web.docbook
deleted file mode 100644
index 5a5ba5d..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Web.docbook
+++ /dev/null
@@ -1,7 +0,0 @@
-<chapter id="identity-web">
-
- <title>The CentOS Web</title>
-
- &identity-web-intro;
-
-</chapter>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Identity/Web/intro.docbook b/Artworks/Docs/Docbook/Tcar-ug/Identity/Web/intro.docbook
deleted file mode 100644
index 956fa35..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Identity/Web/intro.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="identity-web-intro">
-
- <title>Introduction</title>
-
- <para>
- ...
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Locales.docbook b/Artworks/Docs/Docbook/Tcar-ug/Locales.docbook
deleted file mode 100644
index 656b9d8..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Locales.docbook
+++ /dev/null
@@ -1,21 +0,0 @@
-<part id="locale">
-
- <title>Localization</title>
-
- <partintro>
- <para>...</para>
- </partintro>
-
- <chapter>
- <title>...</title>
- <para>...</para>
-
- <sect1>
- <title>...</title>
- <para>...</para>
- </sect1>
-
- </chapter>
-
-</part>
-
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Locales.ent b/Artworks/Docs/Docbook/Tcar-ug/Locales.ent
deleted file mode 100644
index 48245e8..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Locales.ent
+++ /dev/null
@@ -1,2 +0,0 @@
-<!ENTITY locales SYSTEM "Locales.docbook">
-
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals.docbook b/Artworks/Docs/Docbook/Tcar-ug/Manuals.docbook
deleted file mode 100644
index 44bacd4..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals.docbook
+++ /dev/null
@@ -1,30 +0,0 @@
-<part id="manuals">
-
- <title>Documentation</title>
-
- <partintro>
- <para>
- &TCAR; documentation work line is implemented through
- documentation manuals. Documentation manuals are
- implemented through different documentation formats
- provided inside &TCD; (e.g.,
- <application>Docbook</application>,
- <application>Texinfo</application>,
- <application>LaTeX</application>, etc.). Structuring
- tasks related to documentation systems (e.g., creating,
- editing, deleting, copying, renaming, etc.) are
- standardized through the <code>help</code> functionality
- of <command>centos-art.sh</command> script, as described
- in <xref linkend="scripts-bash-help" />. This way, people
- writting documentation don't need to deal with underlaying
- tasks like creating files, updating menus, nodes, cross
- references and wondering where to put everything in
- &TCAR;.
- </para>
-
- </partintro>
-
- &manuals-production;
- &manuals-formats;
-
-</part>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals.ent b/Artworks/Docs/Docbook/Tcar-ug/Manuals.ent
deleted file mode 100644
index c68bc34..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals.ent
+++ /dev/null
@@ -1,13 +0,0 @@
-<!ENTITY manuals SYSTEM "Manuals.docbook">
-<!ENTITY manuals-production SYSTEM "Manuals/Production.docbook">
-<!ENTITY manuals-production-intro SYSTEM "Manuals/Production/intro.docbook">
-<!ENTITY manuals-production-identifying-goals SYSTEM "Manuals/Production/identifying-goals.docbook">
-<!ENTITY manuals-production-identifying-title SYSTEM "Manuals/Production/identifying-title.docbook">
-<!ENTITY manuals-production-identifying-structure SYSTEM "Manuals/Production/identifying-structure.docbook">
-<!ENTITY manuals-production-implementing-structure SYSTEM "Manuals/Production/implementing-structure.docbook">
-<!ENTITY manuals-production-maintaining-structure SYSTEM "Manuals/Production/maintaining-structure.docbook">
-<!ENTITY manuals-formats SYSTEM "Manuals/Formats.docbook">
-<!ENTITY manuals-formats-intro SYSTEM "Manuals/Formats/intro.docbook">
-<!ENTITY manuals-formats-texinfo SYSTEM "Manuals/Formats/texinfo.docbook">
-<!ENTITY manuals-formats-docbook SYSTEM "Manuals/Formats/docbook.docbook">
-<!ENTITY manuals-formats-latex SYSTEM "Manuals/Formats/latex.docbook">
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats.docbook b/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats.docbook
deleted file mode 100644
index 9fac62b..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats.docbook
+++ /dev/null
@@ -1,10 +0,0 @@
-<chapter id="manuals-formats">
-
- <title>Documentation Formats</title>
-
- &manuals-formats-intro;
- &manuals-formats-texinfo;
- &manuals-formats-docbook;
- &manuals-formats-latex;
-
-</chapter>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats/docbook.docbook b/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats/docbook.docbook
deleted file mode 100644
index 1b7c5da..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats/docbook.docbook
+++ /dev/null
@@ -1,51 +0,0 @@
-<sect1 id="manuals-formats-docbook">
-
- <title>DocBook</title>
-
- <para>
- This section describes the implementation of DocBook
- documentation format inside the <xref
- linkend="scripts-bash-help"/> functionality of
- <command>centos-art.sh</command> script. In this section we
- assume you have a basic understanding of DocBook documentation
- format. Otherwise, if you don't know what DocBook
- documentation format is, take a look at <ulink
- url="http://docbook.org/">DocBook website</ulink> and then,
- come back here.
- </para>
-
- <sect2>
- <title>Document Structure</title>
- <para>
- ...
- </para>
- </sect2>
-
- <sect2>
- <title>Document Templates</title>
- <para>
- ...
- </para>
- </sect2>
-
- <sect2>
- <title>Document Expansions</title>
- <para>
- ...
- </para>
- </sect2>
-
- <sect2>
- <title>Document Configuration</title>
- <para>
- ...
- </para>
- </sect2>
-
- <sect2>
- <title>Document Localization</title>
- <para>
- ...
- </para>
- </sect2>
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats/intro.docbook b/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats/intro.docbook
deleted file mode 100644
index f3d96f4..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats/intro.docbook
+++ /dev/null
@@ -1,24 +0,0 @@
-<sect1 id="manuals-formats-intro">
-
- <title>Introduction</title>
-
- <para>
- &TCD; provides support for different documentation formats,
- including Texinfo, LaTeX, DocBook and LinuxDoc. These formats
- have their own specifications and requirements to create and
- maintain documentation manuals written through them. Inside
- &TCAR;, the <xref linkend="scripts-bash-help" /> functionality
- provides the interface you use to create and maintain
- documentation manuals without needing to take care the
- underlaying structuring tasks.
- </para>
-
- <para>
- This chapter describes how the <xref
- linkend="scripts-bash-help" /> functionality implements the
- different documentation source formats available inside &TCD;,
- and the internationalization issues related to documentation
- manuals produced through them.
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats/latex.docbook b/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats/latex.docbook
deleted file mode 100644
index b777161..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats/latex.docbook
+++ /dev/null
@@ -1,47 +0,0 @@
-<sect1 id="manuals-formats-latex">
-
- <title>LaTeX</title>
-
- <para>
- This section describes the implementation of LaTeX
- documentation format inside the <function>help</function>
- functionality of centos-art.sh script described in <xref
- linkend="scripts-bash-help" />. In this section we assume you
- have a basic understanding of LaTeX language.
- </para>
-
- <sect2>
- <title>Document Structure</title>
- <para>
- ...
- </para>
- </sect2>
-
- <sect2>
- <title>Document Templates</title>
- <para>
- ...
- </para>
- </sect2>
-
- <sect2>
- <title>Document Expansions</title>
- <para>
- ...
- </para>
- </sect2>
-
- <sect2>
- <title>Document Configuration</title>
- <para>
- ...
- </para>
- </sect2>
-
- <sect2>
- <title>Document Localization</title>
- <para>
- ...
- </para>
- </sect2>
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats/texinfo.docbook b/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats/texinfo.docbook
deleted file mode 100644
index 801ec4b..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Formats/texinfo.docbook
+++ /dev/null
@@ -1,871 +0,0 @@
-<sect1 id="manuals-formats-texinfo">
-
- <title>Texinfo</title>
-
- <para>
- This section describes the implementation of Texinfo
- documentation format inside the <xref
- linkend="scripts-bash-help"/> functionality of
- <command>centos-art.sh</command> script. In this section we
- assume you have a basic understanding of Texinfo documentation
- system. Otherwise, if you don't know what Texinfo
- documentation system is, read the Texinfo manual first (e.g.,
- by running the <command>info texinfo</command> command) and
- then, come back here.
- </para>
-
- <sect2 id="manuals-formats-texinfo-structure">
- <title>Document Structure</title>
- <para>
- The <xref linkend="scripts-bash-help"/> functionality of
- <command>centos-art.sh</command> provides a document structure
- that makes documentation manuals created through it to be
- scalable and maintainable through time. This document
- structure follows the idea of an upside-down tree to organize
- chapters, sections, subsections and the like, as described in
- <xref linkend="manuals-production-identifying-structure" />.
- </para>
-
- <para>
- The <xref linkend="scripts-bash-help"/>
- functionality creates documentation manuals source files in
- the <filename
- class="directory">Documentation/Models/Texinfo/</filename>
- directory and saves output produced from them in the <filename
- class="directory">Documentation/Manuals/Texinfo/</filename>
- directory. To produce documentation manuals initial source
- files, the <xref linkend="scripts-bash-help"/> functionality
- uses Texinfo documentation templates, as described in <xref
- linkend="manuals-formats-texinfo-templates" />.
- </para>
-
- <para>
- Inside the documentation models directory, source files are
- stored inside language-specific directories. The
- language-specific directories are necessary to implement
- internationalization of Texinfo source files, as described in
- <xref linkend="manuals-formats-texinfo-l10n" />.
- </para>
-
- <para>
- Inside the language-specific directory, the following files
- exist to store the manual's main definitions (e.g., title,
- subtitle, author, copyright notice, chapters, appendixes,
- indexes and all similar stuff a documentation manual usually
- has). In addition to these files, there is one directory for
- each chapter created inside the manual. Inside each chapter
- directory, you'll find the files controlling the section
- definitions related each chapter they belong to. The section
- files (a.k.a. <quote>documentation entries</quote>) are
- suffixed with a <filename class="extension">texinfo</filename>
- extension and named arbitrarily, as it is illustrated in <xref
- linkend="manuals-formats-texinfo-structure-example1" />.
- Inside section files it is where you write the manual's
- content itself.
- </para>
-
- <example id="manuals-formats-texinfo-structure-example1">
- <title>Texinfo document structure</title>
- <screenshot>
- <screeninfo>Texinfo document structure</screeninfo>
- <mediaobject>
- <textobject>
- <programlisting>Documentation/Models/Texinfo/${MANUAL_NAME}
-`-- ${LANG}
- |-- ${CHAPTER_NAME}/
- | `-- ${SECTION_NAME}.texinfo
- |-- ${CHAPTER_NAME}-menu.texinfo
- |-- ${CHAPTER_NAME}-nodes.texinfo
- |-- ${CHAPTER_NAME}.texinfo
- |-- Licenses -> Documentation/Models/Texinfo/Default/${LANG}/Licenses
- |-- Licenses-menu.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses-menu.texinfo
- |-- Licenses-nodes.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses-nodes.texinfo
- |-- Licenses.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses.texinfo
- |-- ${MANUAL_NAME}.conf
- |-- ${MANUAL_NAME}-index.texinfo
- |-- ${MANUAL_NAME}-menu.texinfo
- |-- ${MANUAL_NAME}-nodes.texinfo
- `-- ${MANUAL_NAME}.texinfo</programlisting>
- </textobject>
- </mediaobject>
- </screenshot>
- </example>
-
- <para>
- Texinfo (as in <package>texinfo-4.8-14.el5</package>) doesn't
- support part sectioning inside documentation manuals, so
- neither the <xref linkend="scripts-bash-help"/> functionality
- does. Nevertheless, you can create several documentation
- manuals and consider them as part of a bigger documentation
- manual to workaround this issue.
- </para>
-
- <para>
- In this document structure, the creation of documentation
- manuals, chapters and sections is not limitted. You can create
- as many documenation manuals, chapters and sections as you
- need. The only limitation would be the amount of free space
- required to store the Texinfo source files and the output
- files produced from them in your workstation.
- </para>
-
- </sect2>
-
- <sect2 id="manuals-formats-texinfo-templates">
- <title>Document Templates</title>
- <para>
- Texinfo document templates provide the initial document
- structure the <xref linkend="scripts-bash-help"/>
- functionality needs in order to create and maintain document
- structures, as described in <xref
- linkend="manuals-formats-texinfo-structure" />.
- </para>
-
- <para>
- Texinfo document templates are language-specific. This means
- that there is (or, at least, must be) one Texinfo document
- template for each language you plan to support documentation
- manuals for. By default, &TCAR; provides a default Texinfo
- document template under <filename class="directory">en_US</filename>
- directory. This template structure is used when your current
- locale is English language or when you are creating/editing a
- documentation manual in a language other than English, but no
- language-specific document template for that language exists
- in the <filename
- class="directory">Scripts/Documentation/Models/Texinfo/Default/</filename>
- directory.
- </para>
-
- <para>
- The <filename
- class="directory">Scripts/Documentation/Models/Texinfo/Default/</filename>
- directory organizes all Texinfo document templates using the
- format LL_CC, where LL is the language code (as in ISO-639)
- and CC the country code (as in ISO-3166). The directory
- structure of Texinfo document templates is illustrated in the
- <xref linkend="manuals-formats-texinfo-templates-example1" />
- and implemented through the following files:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><filename>manual.texinfo</filename></term>
- <listitem>
- <para>
- This file can be found inside the language-specific directory
- and contains the manual's main definitions (e.g., document
- title, document language, document authors, copyright notice,
- etc.).
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>manual-menu.texinfo</filename></term>
- <listitem>
- <para>
- This file can be found inside the language-specific directory
- and contains the menu definitions of chapters inside the
- manual. When <xref linkend="scripts-bash-help" />
- functionality creates instances of this file, menu definitions
- inside it are automatically updated when a new chapter is
- created or deleted through the <xref
- linkend="scripts-bash-help"/> functionality. Generally, you
- don't need to edit instances of this file once the
- documentation manual has been created.
- </para>
- <para>
- When a documentation manual is created for first time, this
- file is copied from Texinfo document template directory
- structure to the documentation manual being currently created.
- At this specific moment, the instance created contains the
- following Texinfo menu definition:
- </para>
-
-<programlisting>
-@menu
-* Licenses::
-* Index::
-@end menu
-</programlisting>
-
- <para>
- Later, when chapters are added to or deleted from the
- documentation manual, the content of this file varies adding
- or deleting menu entries accordingly. Nevertheless, the two
- entries shown above are ignored when new chapters are added to
- or removed from the list, so they will always be present in
- instances of this file. To preserve the manual consistency,
- the <xref linkend="scripts-bash-help"/> functionality prevents
- you from deleting any of these chapters once the documentation
- manual has been created.
- </para>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>manual-nodes.texinfo</filename></term>
- <listitem>
- <para>
- This file can be found inside the language-specific directory
- and contains the node definitions of all chapters inside the
- manual. When <xref linkend="scripts-bash-help"/>
- functionality creates instances of this file, node definitions
- inside it are automatically created based on menu definitions
- (see <filename>manual-menu.texinfo</filename> file above) and
- they don't include any content here. Instead, as part of the
- node definition, the <code>@include</code> command is used to
- connect each node with its content. Generally, you don't need
- to edit instances of this file once the documentation manual
- has been created.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>manual-index.texinfo</filename></term>
- <listitem>
- <para>
- This file can be found inside the language-specific directory
- and contains the Texinfo commands used to generated an
- organized view of all indexes you defined inside documentation
- entries so they can be quickly accessed. Generally, you don't
- need to edit instnaces of this file once the documentation
- manual has been created.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>manual.conf</filename></term>
- <listitem>
- <para>
- This file contains the initial configuration of documentation
- manuals written in Texinfo format. When a documentation manual
- is created for first time, this file is copied into its target
- directory so you be able to customize specific information
- like menu order, title styles and template assignments
- therein. The content of this file is described in <xref
- linkend="manuals-formats-texinfo-configuration" />.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>Chapters.texinfo</filename></term>
- <listitem>
- <para>
- This file contains Texinfo's main chapter definition used
- by <xref linkend="scripts-bash-help"/> functionality when new
- chapters are created inside documentation manuals. When
- chapters are created for first time, they come without any
- introduction or documentation entry inside.
- </para>
- <para>
- In case you need to add/update the chapters definition files,
- edit the related chapter definition file inside the
- documentation manual you are working on, not the template file
- used to create it. To edit the chapter definition file, don't
- provide any section information in the documentation entry.
- For example, if you want to update the chapter introduction
- related to <quote>trunk</quote> chapter inside
- <quote>tcar-fs</quote> documentation manual, use the
- <quote>tcar-fs::trunk:</quote> documentation entry.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>Chapters-menu.texinfo</filename></term>
- <listitem>
- <para>
- This file is part of Texinfo's main chapter definition and
- should be initially empty. Later, when chapters are created
- for first time, this file is copied as it is (i.e., empty)
- into the documentation manual to store the Texinfo menu
- entries related to all documentation entries created inside
- the chapter. The Texinfo menu entries related to documentation
- entries are automatically created using Texinfo source files
- as reference.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>Chapters-nodes.texinfo</filename></term>
- <listitem>
- <para>
- This file is part of Texinfo's main chapter definition and
- contains the node definition the <xref linkend="scripts-bash-help"/>
- functionality uses as reference to create the list of Texinfo
- nodes related to all documentation entries created inside the
- chapter. The node definition of documentation entries is
- automatically created from the menu definition of
- documentation entries (see
- <filename>Chapters-menu.texinfo</filename> file above), once it
- has been updated from Texinfo source files.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>section.texinfo</filename></term>
- <listitem>
- <para>
- This file contains the Texinfo section definition used by
- <xref linkend="scripts-bash-help"/> functionality when new
- documentation entries are created inside chapters of
- documentation manuals. When documentation entries are created
- for first time, they are created as empty documentation
- entries that you need to fill up with content. Again, if you
- want to update the content of sections inside the
- documentation manual, update the related documentation entry
- inside the documentation manual, not the template file used to
- create it.
- </para>
-
- <para>
- The creation of documentation entries inside the documentation
- manual is represented by the
- <filename>${SECTION_NAME}.texinfo</filename> file, as
- described in <xref
- linkend="manuals-formats-texinfo-structure-example1" />. In
- this example, <code>${SECTION_NAME}</code> is a variable
- string referring the file name of documentation entries. The
- file names of documentation entries are made of letters,
- numbers and the minus sign (which is generally used as word
- separator).
- </para>
-
- <para>
- Documentation entries are not limited inside chapters of
- documentation manuals. You can create as many documentation
- entries as you need to describe the content of your manual.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- There are other files which aren't related to manual's source
- files, but to manual's output files. Such files are described
- below and can be found either inside or outside the
- language-specific directories so you can control common and
- specific output settings through them. These files aren't
- copied into the directory structure of new documentation
- manuals created through the <xref linkend="scripts-bash-help"/>
- functionality. Instead, they remain inside the template
- directory structure so as to be reused each time the output of
- documentation manuals is rendered.
- </para>
-
- <variablelist>
- <varlistentry>
- <term><filename>manual-init.pl</filename></term>
- <listitem>
- <para>
- This file can be found inside and outside language-specific
- directories and contains the Texi2html initialization script.
- When this file is outside the language-specific directory, it
- contains common customizations to all language-specific
- outputs (e.g., changing the output DTD). When this file is
- inside the language-specific directory, it contains
- translations for that language-specific output (e.g., special
- words like See, Index, Contents, Top, etc., are localized
- here).
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>manual.sed</filename></term>
- <listitem>
- <para>
- This file can be found inside and outside language-specific
- directories and contains special transformations for Texi2html
- output. Again, when this file is inside language-specific
- directories the transformation are applied to that
- language-specific XHTML output and when it is outside
- language-specific directories the transformations are applied
- to all language-specific XHTML outputs. Most transformations
- achieved through this file are to produce admonitions since
- Texinfo documentation format (as in
- <package>texinfo-4.8-14.el5</package>) doesn't have an
- internal command to build them.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <example id="manuals-formats-texinfo-templates-example1">
- <title>Template for texinfo document structures</title>
- <screenshot>
- <screeninfo>Template for texinfo document structures</screeninfo>
- <mediaobject>
- <textobject>
- <programlisting>
-Documentation/Models/Texinfo/Default/
-|-- ${LANG}/
-| |-- Chapters/
-| | |-- section.texinfo
-| | `-- section-functions.texinfo
-| |-- Chapters-menu.texinfo
-| |-- Chapters-nodes.texinfo
-| |-- Chapters.texinfo
-| |-- Licenses/
-| | |-- GFDL.texinfo
-| | `-- GPL.texinfo
-| |-- Licenses-menu.texinfo
-| |-- Licenses-nodes.texinfo
-| |-- Licenses.texinfo
-| |-- manual-index.texinfo
-| |-- manual-init.pl
-| |-- manual-menu.texinfo
-| |-- manual-nodes.texinfo
-| |-- manual.conf
-| |-- manual.sed
-| `-- manual.texinfo
-|-- manual-init.pl
-`-- manual.sed
-</programlisting>
- </textobject>
- </mediaobject>
- </screenshot>
- </example>
-
- <para>
- Inside the directory structure of Texinfo document templates,
- the <filename class="directory">Chapters</filename> directory
- stores section specific models used to create and maintain
- section files inside manuals. File names beginning with
- <quote>Chapters</quote>, at the same level of <filename
- class="directory">Chapters</filename> directory, are used to
- create chapter specific files inside manuals.
- </para>
-
- <para>
- The <filename class="directory">Licenses</filename> directory
- organizes the license information linked from all manuals.
- Notice the license information is not copied into
- documentation manuals when they are created, but referred from
- models location where they are maintained. This configuration
- permits all documentation manuals written in Texinfo format
- inside &TCAR; to use the same license information. This way,
- if a change is committed to license files, it will be
- immediately propagated to all documentation manuals the next
- time their output files be updated.
- </para>
- </sect2>
-
- <sect2 id="manuals-formats-texinfo-macros">
- <title>Document Expansions</title>
- <para>
- The document expansions are special constructions the <xref
- linkend="scripts-bash-help" /> functionality provides to
- generate content dynamically inside Texinfo source files.
- </para>
-
- <sect3>
- <title>The <code>SeeAlso</code> Expansion</title>
-
- <para>
- This expansion creates a list of links with section entries
- one level ahead from the section entry being currently
- processed. In this construction, the TYPE variable can be
- either <quote>itemize</quote>, <quote>enumerate</quote> or
- <quote>menu</quote>. When no TYPE variable is provided, the
- <quote>itemize</quote> value is considered as default.
- </para>
-
- <screen>@c -- <[centos-art(SeeAlso,TYPE)
-@c -- ]></screen>
-
- <para>
- This expansion might result useful when you are documenting
- the repository file system. For example, if you are currently
- editing the documentation entry related to <filename
- class="directory">Identity</filename> directory and want
- to create a linkable list of all documentation entries in the
- first level under it, the code you'll have once the
- construction be expanded would look like the following:
- </para>
-
-<screen>
-@c -- <[centos-art(SeeAlso)
-@itemize
-@item @ref{Trunk Identity Brushes}
-@item @ref{Trunk Identity Fonts}
-@item @ref{Trunk Identity Images}
-@item @ref{Trunk Identity Models}
-@item @ref{Trunk Identity Palettes}
-@item @ref{Trunk Identity Patterns}
-@item @ref{Trunk Identity Webenv}
-@end itemize
-@c -- ]>
-</screen>
-
- <para>
- An interesting thing to notice here is that document
- expansions are executed each time the related documentation
- entry is edited or updated. Following with the example above,
- if the documentation entries related to directories under
- <filename class="directory">Identity</filename> changes
- for some reason (e.g., they are removed from documentation
- manual), the list generated as result of document expansion
- will be updated automatically after editing the documentation
- entry or updating the documentation manual structure.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2 id="manuals-formats-texinfo-configuration">
- <title>Document Configuration</title>
- <para>
- The document configuration is stored in the
- <filename>${MANUAL_NAME}.conf</filename> file, inside the
- documentation manual directory structure. This file is
- originally copied from <filename>manual.conf</filename>
- template file when the documentation manual is created for
- first time. The content of
- <filename>${MANUAL_NAME}.conf</filename> file is organized in
- sections. Each section here is written in one line of its own
- and have the form <code>[section_name]</code>. Under sections,
- the configuration settings take place through
- <code>name="value"</code> pairs set in one line each. Notice
- that quotation marks around the option_value are required.
- Comments are also possible using the <code>#</code> character
- at the begining of lines. Comments and empty lines (including
- tabs and white spaces) are ignored. In case more than one
- section or option appear with the same name inside the
- configuration file, the first one found will be used. Nested
- section definitions are not supported.
- </para>
-
- <screen>[section_name]
-# This is a comment.
-option_name = "option_value"</screen>
-
- <para>
- The <filename>${MANUAL_NAME}.conf</filename> file is specific
- to document templates. If you are using Texinfo document
- template to create documentation manuals, then the default
- configuration file for that documentation manual is taken from
- Texinfo document template directory structure. However, if you
- are using a document template different to Texinfo document
- template, the default configuration file will be taken from
- the related document template directory structure you are
- creating the documentation manual from.
- </para>
-
- <sect3>
- <title>The <code>[main]</code> Section</title>
- <para>
- The <code>[main]</code> section organizes settings that let
- you customize the way sections and menu definitions are
- created inside the documentation manual. The following options
- are available in this section:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><code>manual_format</code></term>
- <listitem>
- <para>
- This option specifies the documentation format used by manual.
- To write documentation manuals in Texinfo format, the value
- of this option must always be:
- </para>
- <screen>manual_format = "texinfo"</screen>
- <caution>
- <para>
- Once the documentation manual has been created, you must not
- change the value of <option>manual_format</option> option.
- This will produce an error because there is not a migration
- feature available yet. In the future, when you change this
- value, it must be possible to transform documentation manuals
- from one format to another.
- </para>
- </caution>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><code>manual_section_style</code></term>
- <listitem>
- <para>
- This option specifies the title style used by sections inside
- the manual. Possible values to this option are
- `cap-each-word' to capitalize each word in the section title,
- `cap-first-word' to capitalize the first word in the section
- title only and `directory' to transform each word in the
- section title into a directory path. From all these options,
- `cap-each-word' is the one used as default.
- </para>
- <screen>manual_section_style = "cap-each-word"</screen>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><code>manual_section_order</code></term>
- <listitem>
- <para>
- This option specifies the order used by sections inside the
- manual. By default new sections added to the manual are put on
- the end to follow the section order in which they were
- `created'. Other possible values to this option are `ordered'
- and `reversed' to sort the list of sections alphabetically
- from A-Z and Z-A, respectively.
- </para>
- <screen>manual_section_order = "created"</screen>
- </listitem>
- </varlistentry>
- </variablelist>
- </sect3>
-
- <sect3>
- <title>The <code>[templates]</code> Section</title>
- <para>
- The <code>[templates]</code> section provides the assignment
- relation between template files and documentation entry files
- inside the manual. The template definition is set on the left
- side using relative path and the documentation entry files are
- described on the right side using a regular expression. The
- first match wins.
- </para>
- <screen>Chapters/section.texinfo = "^.+\.texinfo$"</screen>
- </sect3>
-
- </sect2>
-
- <sect2 id="manuals-formats-texinfo-l10n">
- <title>Document Localization</title>
- <para>
- To produce localized documentation manuals through Texinfo
- documentation format it is necessary to create one
- documentation manual for each language it is desired to
- support documentation for. Documentation manuals created in
- this configuration don't have a direct relation among
- themselves except that one adopted by people writting them to
- keep their content syncronized. In this configuration
- translators take one documentation manual as reference (a.k.a.
- the source manual) and produce several translated manuals
- based on its content. To keep track of changes inside the
- source manual, the underlaying version control system must be
- used considering that there is no direct way to apply
- <command>gettext</command><footnote>
- <para>
- The <command>gettext</command> program translates
- a natural language message into the user's language, by
- looking up the translation in a message catalog. For more
- information about the <command>gettext</command>
- program, run <command>info gettext</command>.
- </para>
- </footnote> procedures to Texinfo source files.
- </para>
-
- <para>
- In order to maintain localization of Texinfo source files
- through <command>gettext</command> procedures, it is necessary
- to convert the Texinfo source files into XML format first.
- This way it would be possible to make use of <xref
- linkend="scripts-bash-locale"/> and <xref
- linkend="scripts-bash-render"/> functionalities to maintain
- translation messages in different languages through portable
- objects and producing localized XML files based on such
- portable objects, respectively. Once the localized XML file
- is available, it would be a matter of using an XSLT processor
- (see the <command>xsltproc</command> command) to realize the
- convertion from XML to a localize Texinfo (or possible other)
- format. Nevertheless, this workaround fails because the
- Document Type Definition (DTD) required to validate the XML
- file produced from <command>makeinfo</command> (as in
- <package>texinfo-4.8-14.el5</package>) is not availabe inside
- &TCD; (release 5.5), nor it is the XSLT files required to
- realize the transformation itself for such DTD.
- </para>
-
- <para>
- Another similar approach to maintain localization of Texinfo
- source files through <command>gettext</command> procedures
- would be to convert Texinfo source file to DocBook format; for
- who the required DTD and XSLT files are available inside
- &TCD;. This way, following a procedure similar to that one
- describe for XML files above, it would be possible to end up
- having localized DocBook files that can be used as source to
- produce localized output for both online and printing media.
- However, the DocBook output produced from
- <command>makeinfo</command> command (as in
- <package>texinfo-4.8-14.el5</package>) isn't a valid DocBook
- document according to DocBook DTDs available inside &TCD;
- (release 5.5) thus provoking the validation and transformation
- of such a malformed document to fail.
- </para>
-
- <sect3 id="manuals-texinfo-l10n-language">
- <title>Document Language</title>
- <para>
- The language information of those documentation manuals
- produced through Texinfo documentation format is declared by
- Texinfo's <code>@documentlanguage</code> command. This
- command receives one argument refering the language code (as
- in ISO-639 standard) and must be set inside the manual's main
- definition file. Generally, there is no need to change the
- document language declaration once it has been created by the
- <xref linkend="scripts-bash-help"/> functionality; unless you
- mistakently create the manual for a locale code different to
- that one you previously pretended to do in first place, of
- course.
- </para>
-
- <para>
- The language information used in both Texinfo source files and
- XHTML output produced by the <xref linkend="scripts-bash-help"/>
- functionality is determined by the user's session
- <envar>LANG</envar> environment variable. This variable can
- be customized in the graphical login screen before login, or
- once you've login by explicitly setting the value of
- <envar>LANG</envar> environment variable inside the
- <filename>~/.bash_profile</filename> file.
- </para>
-
- <tip>
- <para>
- To create documentation manuals in English language the
- <envar>LANG</envar> environment variable must be set to
- <code>en_US.UTF-8</code> or something similar. Likewise, if
- you want to create documentation manuals in a language other
- than English, be sure the <envar>LANG</envar> environment
- variable is set to the appropriate locale code.<footnote>
- <para>
- The appropriate locale code to set here can be found in
- the output produced by the <command>locale -a |
- less</command> command.
- </para></footnote>
- </para>
- </tip>
-
- <para>
- When producing output from Texinfo source files using the
- <command>makeinfo</command> command (as in the
- <package>texinfo-4.8-14.el5</package> package), the language
- information set by <code>@documentlanguage</code> is ignored
- in Info and HTML output, but cosidered by Tex program to
- redefine various English words used in the PDF output (e.g.,
- <quote>Chapters</quote>, <quote>Index</quote>,
- <quote>See</quote>, and so on) based on the current language
- set in.
- </para>
-
- </sect3>
-
- <sect3 id="manuals-texinfo-l10n-encoding">
- <title>Document Encoding</title>
- <para>
- The encoding information of documentation manuals produced
- through Texinfo documentation format is declared by Texinfo's
- <code>@documentencoding</code> command and can take either
- <code>US-ASCII</code>, <code>ISO-8859-1</code>,
- <code>ISO-8859-15</code> or <code>ISO-8859-2</code> as
- argument. Nevertheless, you should be aware that the
- <xref linkend="scripts-bash-help" /> functionality doesn't
- declare the <code>@documentencoding</code> inside Texinfo
- source files. Let's see why.
- </para>
-
- <para>
- When the <code>@documentencoding</code> command is set in
- Texinfo source files, the terminal encoding you use to read
- the Info output produced from such files must be set to that
- encoding information you provided as argument to
- <code>@documentencoding</code> command; this, before using an
- Info reader to open the Info output file in the terminal.
- Otherwise, when the terminal and the Texinfo source files
- encoding definition differ one another, characters defined
- through Texinfo's special way of producing floating accents
- won't be displayed as expected (even when the
- <option>--enable-encoding</option> is provided to
- <command>makeinfo</command> command). On the other hand, when
- the <code>@documentencoding</code> command is not set in
- Texinfo source files, it is possible to write and read
- documentation manuals using the UTF-8 encoding without needing
- to use Texinfo's special way of producing floating accents
- because the terminal encoding would be able to interpret the
- characters entered when the Texinfo source files were written
- in first place.
- </para>
-
- <para>
- When Texinfo's special way of producing floating accents isn't
- used, HTML entities are not produced in XHTML output produced
- by <command>texi2html</command>, nor in the HTML output
- produced by <command>makeinfo</command>, nor in PDF output.
- In this last case, when producing PDF output, you can realize
- what the floating accents are by trying to produce an
- accentuated Spanish <code>i</code> letter (e.g.,
- <code>í</code>). When you do so, you'll note that that
- construction puts the accentuation mark
- <emphasis>over</emphasis> the <code>i</code> letter's dot,
- instead of removing the <code>i</code> letter's dot and
- put the accentuation mark on its place. In the case of XHTML
- output, however, it is possible to produce well localized
- XHTML output by setting
- </para>
-
- <screen><meta http-equiv="content-type" content="text/html; charset=UTF-8" /></screen>
-
- <para>
- on the head section of each XHTML output to instruct the web
- browsers what encoding to use to display the document content.
- Of course, in order to display the document content correctly,
- the web browser should provide support for UTF-8 encoding.
- </para>
-
- <para>
- These contradictions provide the reasons over which it was
- decided not to set the <code>@documentencoding</code> in those
- Texinfo source files produced by the <xref
- linkend="scripts-bash-help" /> functionality.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2 id="manuals-texinfo-l10n-conclusions">
- <title>Conclusions</title>
-
- <para>
- Texinfo documentation format is very good producing online
- documentation for reading text terminals. It provides feautres
- to export source files to different output formats both for
- reading online and paper. However, localized documents becomes
- hard to maintain because it is required one document structure
- for each language you want to produce documentation for.
- </para>
- <para>
- Intermediate formats like XML and Docbook provide an
- alternative to centralize localization of Texinfo document
- source files, but there is no supported way inside &TCD; to
- transformed a localized XML file back into texinfo format, nor
- a way of producing well formed Docbook documents from Texinfo
- source files. Thus, one Texinfo source structure for each
- language to support is the solution adopted by <xref
- linkend="scripts-bash-help" /> functionality.
- </para>
-
- <para>
- When using Texinfo documentation format it is difficult to
- produce well localized PDF outputs, but it is possible to
- produce well localized Info, Text, and XHTML outputs as long
- as no document encoding be explicitly set inside Texinfo
- source files and UTF-8 be used as default terminal character
- encoding.
- </para>
-
- </sect2>
-
-</sect1>
-
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production.docbook b/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production.docbook
deleted file mode 100644
index 58451f0..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production.docbook
+++ /dev/null
@@ -1,12 +0,0 @@
-<chapter id="manuals-production">
-
- <title>Documentation Production Cycle</title>
-
- &manuals-production-intro;
- &manuals-production-identifying-goals;
- &manuals-production-identifying-title;
- &manuals-production-identifying-structure;
- &manuals-production-implementing-structure;
- &manuals-production-maintaining-structure;
-
-</chapter>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/identifying-goals.docbook b/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/identifying-goals.docbook
deleted file mode 100644
index c47888c..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/identifying-goals.docbook
+++ /dev/null
@@ -1,50 +0,0 @@
-<sect1 id="manuals-production-identifying-goals">
-
- <title>Identifying Document Goals</title>
-
- <para>
- The first step in producing a documentation manual is to
- clearly understand what you exactly need to document and why
- you need to do so. The obvious answer to this question would
- be to describe the basic ideas behind an implementation so it
- can be useful once published. It is important that you find
- out the reasons you need to do what you are doing and, also,
- those helping you to retain the motivation to keep doing it in
- the future. Otherwise, without such foundations, you'll surely
- end up leaving the effort soon enough to make a lost cause
- from your initial work.
- </para>
-
- <para>
- Before <citetitle>The CentOS Artwork Repository File
- System</citetitle> documentation manual would exist, there was
- an emerging need to understand what each directory inside the
- growing directory layout was for, how it could be used and
- each directory could be connected one another. At that moment,
- the directory layout was very unstable and explaining the
- whole idea behind it was not possible, there were too many
- changing concepts floating around which needed to be
- considered in the same changing way. So, to understand what
- was happening, the <citetitle>The CentOS Artwork Repository
- File System</citetitle> documentation manual was created.
- </para>
-
- <para>
- The <citetitle>The CentOS Artwork Repository File
- System</citetitle> manual was conceived based on the idea of
- documenting each directory inside the repository individually
- and, later, by considering all directory documentations
- altogether, it would be (hypothetically) possible to correct
- the whole idea through an improvement cycle that would
- consolidate the final idea we were trying to implement.
- </para>
-
- <para>
- Other documentation manuals can be based on reasons different
- from those described above, however, no matter what those
- reasons are, it will be helpful to make yourself a clean idea
- about what you are going to document exactly before putting
- your hands on it.
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/identifying-structure.docbook b/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/identifying-structure.docbook
deleted file mode 100644
index 8178a2e..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/identifying-structure.docbook
+++ /dev/null
@@ -1,145 +0,0 @@
-<sect1 id="manuals-production-identifying-structure">
- <title>Identifying Document Structure</title>
- <para>
- Once both the manual's title and the manual's directory name
- have been defined, it is time for you to plan the document
- structure through which the manual's content will be
- organized.
- </para>
-
- <para>
- The specific document structure you choose for a documentation
- manuals is affected by the documentation format you use to
- write documentation source files. Nevertheless, no matter
- what the documentation format be, the document structure
- produced from the <xref linkend="scripts-bash-help" />
- functionality will always follow and upside-down tree
- configuration for document structures. In this configuration,
- documentation manuals can be organized through different
- structural levels (e.g., parts, chapters, sections,
- subsection, etc.) based on the support provided by the
- documentation format you chose.
- </para>
-
- <para>
- The <citetitle>The CentOS Artwork Repository File
- System</citetitle> documentation manual was conceived to
- document each directory structure &TCAR; is made of, using
- Texinfo as main documentation format.
- </para>
-
- <para>
- At this point we find that &TCAR; had more levels deep than
- sectioning commands available inside documentation format.
- This way it is not possible to use one sectioning command for
- each directory level inside the repository directory structure
- we need to document. Based on these issues, it is
- imperative to re-accommodate the document structure in order
- to be able of documenting every directory &TCAR; is made of,
- using the sectioning levels supported by that documentation
- format we chose, no matter how many levels deep the repository
- directory structure had.
- </para>
-
- <para>
- As consequence, <citetitle>The CentOS Artwork Repository File
- System</citetitle> ended up being organized through the
- following documentation structure:
- </para>
-
- <variablelist>
- <varlistentry>
- <term>Chapter 1. The <filename class="directory">trunk</filename>
- Directory</term>
- <listitem>
- <para>
- This chapter describes the <filename
- class="directory">trunk</filename> directory inside the
- repository and all subdirectories inside it. The first level
- of directories (i.e., the <filename
- class="directory">trunk</filename> directory itself) is
- described inside the chapter entry. Deeper directory levels
- are all documented through sections and have a file for their
- own. It is also possible to write subsections and
- subsubsections, however, they don't have a file for their own
- as sections do. Subsections and Subsubsections should be
- written as part of section files (i.e., when writting
- sections).
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 2. The <filename class="directory">branches</filename>
- Directory</term>
- <listitem>
- <para>
- This chapter describes the <filename
- class="directory">branches</filename> directory and all
- directories inside it following the same structure described
- for <filename class="directory">trunk</filename> directory
- above.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 3. The <filename class="directory">tags</filename>
- Directory</term>
- <listitem>
- <para>
- This chapter describes the <filename
- class="directory">tags</filename> directory and all
- directories inside it following the same structure described
- for <filename class="directory">trunk</filename> directory
- above.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Appendix A. Licenses</term>
- <listitem>
- <para>
- This appendix is confined to organize licenses mentioned
- in the manual. The content of this appendix is out of
- documenatation manual scope itself and is shared among all
- documentation manuals written through the <xref
- linkend="scripts-bash-help" /> functionality.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Index</term>
- <listitem>
- <para>
- This chapter organizes links to those index definitions you
- defined inside the documentation manual. The index information
- displayed by this chapter is auto-generated each time the
- manual's output files are created so this chapter is not
- editable.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- The document structure illustrated above is also considered
- the default document structure used by the <xref
- linkend="scripts-bash-help" /> functionality of
- <command>centos-art.sh</command> script when you produce new
- documentation manuals inside &TCAR;. In contrast with document
- structure illustrated above, the default document structure
- used by <xref linkend="scripts-bash-help" /> functionality
- doesn't include sectioning constructions like parts, chapters,
- sections, subsections and the like in the document structure
- created. Such structuring constructions should be specified by
- you when building the documentation manual. The only
- exceptions to this restriction are sectioning structures used
- to organize contents like <quote>Index</quote> and
- <quote>Licenses</quote>, which are considered inseparable
- components of documentation manuals stored inside &TCAR;.
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/identifying-title.docbook b/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/identifying-title.docbook
deleted file mode 100644
index 2c8a8bd..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/identifying-title.docbook
+++ /dev/null
@@ -1,26 +0,0 @@
-<sect1>
- <title>Identifying Document Title</title>
- <para>
- Once you've make yourself an clean idea of what the
- documentation manual is for and the needs behind it, it is
- time for you to define the manual's title and the manual's
- directory name. Both manuals' title and manual's directory
- name describe what the documentation manual is about. The
- manual's title is used inside the documentation while the
- manual's directory name is used to store the related source
- files inside &TCAR; directory structure. Generally, the
- manual's title is a phrase of few words and the manual's
- directory name is the abbreviation of that phrase set as
- manual's title.
- </para>
-
- <para>
- Following with our example, the manual's title chosen was
- <citetitle>The CentOS Artwork Repository File
- System</citetitle> and its directory name was set to
- <quote><filename>Tcar-fs</filename></quote> to comply with the
- file name convenctions described at <xref
- linkend="repo-convs-filenames" />.
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/implementing-structure.docbook b/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/implementing-structure.docbook
deleted file mode 100644
index 1feb428..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/implementing-structure.docbook
+++ /dev/null
@@ -1,12 +0,0 @@
-<sect1 id="manuals-production-implementing-structure">
-
- <title>Implementing Document Structure</title>
-
- <para>
- The document structure implementation is automated by the
- <xref linkend="scripts-bash-help" /> functionality, as
- described in <xref
- linkend="manuals-production-identifying-structure" />.
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/intro.docbook b/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/intro.docbook
deleted file mode 100644
index 5b3f328..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/intro.docbook
+++ /dev/null
@@ -1,21 +0,0 @@
-<sect1>
-
- <title>Introduction</title>
-
- <para>
- This chapter describes the procedure you should follow to
- create and maintain documentation manuals inside &TCAR;.
- </para>
-
- <para>
- This chapter describes general concepts that can be applied
- through the documentation formats supported inside the
- <function>help</function> functionality of
- <command>centos-art.sh</command> script. To illustrate the
- production process related to documentation manuals inside
- &TCAR;, this chapter uses the <citetitle>The CentOS Artwork
- Repository File System</citetitle> (TCAR-FS) documentation
- manual as example.
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/maintaining-structure.docbook b/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/maintaining-structure.docbook
deleted file mode 100644
index f503380..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Manuals/Production/maintaining-structure.docbook
+++ /dev/null
@@ -1,12 +0,0 @@
-<sect1 id="manuals-production-maintaining-structure">
-
- <title>Maintaining Document Structure</title>
-
- <para>
- The document structure maintenance is implemented by the <xref
- linkend="scripts-bash-help" /> functionality, as described in
- <xref linkend="manuals-production-identifying-structure"
- />.
- </para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Preface.docbook b/Artworks/Docs/Docbook/Tcar-ug/Preface.docbook
deleted file mode 100644
index 42c8578..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Preface.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<preface id="preface">
-
- <title>Preface</title>
-
- &preface-overview;
- &preface-docconvs;
- &preface-feedback;
-
-</preface>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Preface.ent b/Artworks/Docs/Docbook/Tcar-ug/Preface.ent
deleted file mode 100644
index ce36070..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Preface.ent
+++ /dev/null
@@ -1,4 +0,0 @@
-<!ENTITY preface SYSTEM "Preface.docbook">
-<!ENTITY preface-overview SYSTEM "Preface/overview.docbook">
-<!ENTITY preface-docconvs SYSTEM "Preface/docconvs.docbook">
-<!ENTITY preface-feedback SYSTEM "Preface/feedback.docbook">
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Preface/docconvs.docbook b/Artworks/Docs/Docbook/Tcar-ug/Preface/docconvs.docbook
deleted file mode 100644
index 17509ca..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Preface/docconvs.docbook
+++ /dev/null
@@ -1,225 +0,0 @@
-<section id="preface-docconvs">
-
- <title>Document Convenctions</title>
-
- <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>
-
- <variablelist>
- <varlistentry>
- <term><command>command</command></term>
- <listitem>
- <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 <keycap>Enter</keycap> 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 render
- Identity/Images/Themes/TreeFlower/4/Distro/5/Anaconda
- --filter="01-welcome"</command> command to produce the first
- slide image used by Anaconda in the branch 5 of &TCD;
- using the version 4 of TreeFlower artistic motif.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename>file name</filename></term>
- <listitem>
- <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">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
- <filename>ImageMagick</filename> RPM package to convert
- images from PNG format to other formats.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><keycap>key</keycap></term>
- <listitem>
- <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</command>, then a
- character, and finally the <keycap>Tab</keycap> key. Your
- terminal displays the list of files in the working
- directory that begin with that character.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><keycombo action="simul"><keycap>key</keycap><keycap>combination</keycap></keycombo></term>
- <listitem>
- <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>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><computeroutput>computer output</computeroutput></term>
- <listitem>
- <para>
- Text in this style indicates text displayed to a shell
- prompt such as error messages and responses to commands.
- For example, the <command>ls</command> command displays
- the contents of a directory using this style:
- </para>
-
-<screen>
-render_doTranslation.sh render_getDirTemplate.sh render_doBaseActions.sh
-render_getConfigOption.sh render_getOptions.sh render_doThemeActions.sh
-render_getDirOutput.sh render.sh
-</screen>
-
- <para>
- The output returned in response to the command (in this
- case, the contents of the directory) is shown in this
- style.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><prompt>prompt</prompt></term>
- <listitem>
- <para>
- A prompt, which is a computer's way of signifying that it
- is ready for you to input something, is shown in this
- style. Examples:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <prompt>$</prompt>
- </para>
- </listitem>
- <listitem>
- <para>
- <prompt>#</prompt>
- </para>
- </listitem>
- <listitem>
- <para>
- <prompt>[centos@projects centos]$</prompt>
- </para>
- </listitem>
- <listitem>
- <para>
- <prompt>projects login:</prompt>
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><userinput>user input</userinput></term>
- <listitem>
- <para>
- Text that the user types, either on the command line or
- into a text box on a GUI screen, is displayed in this
- style. In the following example,
- <userinput>text</userinput> is displayed in this style: To
- boot your system into the text based installation program,
- you must type in the <userinput>text</userinput> command
- at the <prompt>boot:</prompt> prompt.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><replaceable>replaceable</replaceable></term>
- <listitem>
- <para>
- Text used in examples that is meant to be replaced with
- data provided by the user is displayed in this style. In
- the following example,
- <replaceable>version-number</replaceable> is displayed in
- this style: The directory for the kernel source is
- <filename
- class="directory">/usr/src/kernels/<replaceable>version-number</replaceable>/</filename>,
- where <replaceable>version-number</replaceable> is the
- version and type of kernel installed on this system.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <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 <filename
- class="directory">/usr/share/doc/</filename> 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/Artworks/Docs/Docbook/Tcar-ug/Preface/feedback.docbook b/Artworks/Docs/Docbook/Tcar-ug/Preface/feedback.docbook
deleted file mode 100644
index b6f8334..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Preface/feedback.docbook
+++ /dev/null
@@ -1,14 +0,0 @@
-<section id="preface-feedback">
-
- <title>Send In Your Feedback</title>
-
- <para>
- If you find a bug in &TCAR; or this manual, we would like to
- hear about it. To report bugs related to this manual, send an
- e-mail to the <email>centos-devel@centos.org</email> mailing
- list. When you write the bug report, take care of being
- specific about the problem you are reporting on (e.g., where
- it is, the section number, etc.) so we can found it easily.
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Preface/overview.docbook b/Artworks/Docs/Docbook/Tcar-ug/Preface/overview.docbook
deleted file mode 100644
index b12e354..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Preface/overview.docbook
+++ /dev/null
@@ -1,84 +0,0 @@
-<section id="preface-overview">
-
- <title>Overview</title>
-
- <para>
- Welcome to &TCARUG;, the official documentation of &TCAR;.
- </para>
-
- <para>
- This book describes the corporate visual identity of &TCP; and
- the way it is produced. If you are interested in making &TCP;
- a more beautiful project, this book is definitly for you.
- </para>
-
- <para>
- To make the information in this book managable, it has been
- organized in the following parts:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <xref linkend="repo" /> describes the convenctions you should
- follow to keep everything organized and consistent inside the
- repository directory structure, how to to install and
- configure a working copy inside your workstation. At the end
- of this part you will find a history of most relevant changes
- committed to the repository along the years.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <xref linkend="identity" /> describes the corporate visual
- identity of the organization known as &TCP; and the production
- tasks related to image rendition inside &TCAR;. If you are a
- graphic designer, this part of the book might result
- interesting to you.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <xref linkend="locale" /> describes production tasks related to
- content internationalization and localization inside &TCAR;.
- If you are a translator, this part of the book might result
- interesting to you.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <xref linkend="manuals" /> describes production tasks related
- to content documentation inside &TCAR;. If you are a
- documentor, this part of the book might result interesting to
- you.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <xref linkend="scripts" /> describes automation of production
- tasks inside &TCAR;. If you are a programmer, this part of the
- book might result interesting to you.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <xref linkend="licenses" /> organizes the licenses mentioned
- in this book.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- This book assumes you have a basic understanding of &TCD;. If
- you need help with it, go to the <ulink
- url="http://wiki.centos.org/Help">Help</ulink> page inside
- &TCWIKI; for or a list of different places you can find help.
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository.docbook
deleted file mode 100644
index ea8dd86..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<part id="repo">
-
- <title>Repository</title>
-
- &repo-convs;
- &repo-ws;
- &repo-history;
-
-</part>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository.ent b/Artworks/Docs/Docbook/Tcar-ug/Repository.ent
deleted file mode 100644
index f0a40a4..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository.ent
+++ /dev/null
@@ -1,26 +0,0 @@
-<!ENTITY repo SYSTEM "Repository.docbook">
-<!ENTITY repo-convs SYSTEM "Repository/Conventions.docbook">
-<!ENTITY repo-convs-mission SYSTEM "Repository/Conventions/mission.docbook">
-<!ENTITY repo-convs-infra SYSTEM "Repository/Conventions/infra.docbook">
-<!ENTITY repo-convs-worklines SYSTEM "Repository/Conventions/worklines.docbook">
-<!ENTITY repo-convs-directories SYSTEM "Repository/Conventions/directories.docbook">
-<!ENTITY repo-convs-relbdirs SYSTEM "Repository/Conventions/relbdirs.docbook">
-<!ENTITY repo-convs-syncpaths SYSTEM "Repository/Conventions/syncpaths.docbook">
-<!ENTITY repo-convs-extending SYSTEM "Repository/Conventions/extending.docbook">
-<!ENTITY repo-convs-filenames SYSTEM "Repository/Conventions/filenames.docbook">
-<!ENTITY repo-convs-publishing SYSTEM "Repository/Conventions/publishing.docbook">
-<!ENTITY repo-convs-authoring SYSTEM "Repository/Conventions/authoring.docbook">
-<!ENTITY repo-convs-copying SYSTEM "Repository/Conventions/copying.docbook">
-
-<!ENTITY repo-ws SYSTEM "Repository/Workstation.docbook">
-<!ENTITY repo-ws-intro SYSTEM "Repository/Workstation/intro.docbook">
-<!ENTITY repo-ws-install SYSTEM "Repository/Workstation/install.docbook">
-<!ENTITY repo-ws-config SYSTEM "Repository/Workstation/config.docbook">
-
-<!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">
-<!ENTITY repo-history-2012 SYSTEM "Repository/History/2012.docbook">
-<!ENTITY repo-history-2013 SYSTEM "Repository/History/2013.docbook">
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions.docbook
deleted file mode 100644
index 792bcd5..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions.docbook
+++ /dev/null
@@ -1,17 +0,0 @@
-<chapter id="repo-convs">
-
- <title>Repository Conventions</title>
-
- &repo-convs-mission;
- &repo-convs-infra;
- &repo-convs-worklines;
- &repo-convs-directories;
- &repo-convs-filenames;
- &repo-convs-relbdirs;
- &repo-convs-syncpaths;
- &repo-convs-extending;
- &repo-convs-publishing;
- &repo-convs-authoring;
- &repo-convs-copying;
-
-</chapter>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/authoring.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/authoring.docbook
deleted file mode 100755
index 06a4394..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/authoring.docbook
+++ /dev/null
@@ -1,30 +0,0 @@
-<section id="repo-convs-authoring">
-
- <title>Repository Authoring</title>
-
- <para>
- The content produced inside &TCAR; is copyright of &TCP;.
- This is something you, as author, should be aware of because
- you are contributing your creation's rights to someone else;
- &TCP; in this case. This way, your work is distributed using
- <quote>&TCP;</quote> as copyright holder, not your name (even
- you remain as natural author of the work). Because &TCP; is
- the copyright holder, is the license chosen by &TCP; the one
- applied to your work, so it is the one you need to agree with
- before making a creation inside &TCAR;.
- </para>
-
- <para>
- &TCP; is a community project controlled by its own community
- of users. Inside the community, The CentOS Administrators
- group is the higher authority and the only one able to set
- core desition like the kind of license used inside the project
- and subprojects like &TCAR;.
- </para>
-
- <para>
- The redistribution conditions of &TCAR; are described in <xref
- linkend="repo-convs-copying" />.
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/copying.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/copying.docbook
deleted file mode 100755
index 6ecabc2..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/copying.docbook
+++ /dev/null
@@ -1,60 +0,0 @@
-<section id="repo-convs-copying">
-
- <title>Repository Copying Conditions</title>
-
- <para>
- &TCP; uses &TCAR; to produce &TCP; corporate visual identity.
- </para>
-
- <para>
- The &TCAR; is not in the public domain; it is 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 work that they might get from you.
- </para>
-
- <para>
- Specifically, we want to make sure that you have the right to
- give away copies of &TCAR;, that you receive source code or
- else can get it if you want it, that you can change this work
- or use pieces of it in new free works, 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 &TCAR;, 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 &TCAR;.
- If this work 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 &TCAR; is released as a GPL work. Individual packages
- used by &TCAR; include their own licenses and the &TCAR;
- license applies to all packages that it does not clash with.
- If there is a clash between the &TCAR; license and individual
- package licenses, the individual package license applies
- instead.
- </para>
-
- <para>
- The precise conditions of the license for the &TCAR; are found
- in <xref linkend="licenses-gpl" />. This manual specifically
- is covered by the conditions found in <xref
- linkend="licenses-gfdl" />.
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/directories.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/directories.docbook
deleted file mode 100755
index c980bb2..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/directories.docbook
+++ /dev/null
@@ -1,794 +0,0 @@
-<section id="repo-convs-directories">
-
- <title>Repository Directory Structure</title>
-
- <para>
- This section describes the directory structure of &TCAR;. You
- can use this section as reference to know where the files you
- are looking at are stored in and where you can store new
- files, as well. This section organizes directories'
- description using the same hierarchy the repository has. This
- section begins describing the first level of directories in
- the repository and continues with each relevant sub-directory
- in the hierarchy, one by one.
- </para>
-
- <para>
- The directory structure this section describes is based on the
- document <quote><emphasis>&TCAR; Directory
- Structure</emphasis>,</quote> available at:
- <filename>Documentation/Models/Svg/Repository/directory-structure.svgz</filename>
- </para>
-
- <section id="repo-convs-directories-artworks">
- <title>The <filename class="directory">Artworks</filename> Directory</title>
- <para>
- This directory contains the files used to produce the
- corporate visual identity of &TCP;. The information in this
- directory is organized in Brushes, Gradients, Fonts, Images,
- Models, Palettes, Patterns and Webenv directories.
- </para>
-
- <variablelist>
- <varlistentry>
- <term><filename class="directory">Artworks/Brushes/</filename></term>
- <listitem>
- <para>
- This directory contains GIMP brushes. Brushes stored in this
- directory will be available inside GIMP's brushes dialog. This
- directory organizes brushes files inside <filename
- class="directory">Images</filename> and <filename
- class="directory">Models</filename> directories. Inside
- <filename class="directory">Models</filename> directory we
- find the GIMP projects used to build the brush images.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Patterns/</filename></term>
- <listitem>
- <para>
- This directory contains GIMP patterns. Patterns stored in this
- directory will be available inside GIMP's patterns dialog. This
- directory organizes patterns files inside <filename
- class="directory">Images</filename> and <filename
- class="directory">Models</filename> directories. Inside
- <filename class="directory">Models</filename> directory we
- find the GIMP projects used to build the pattern images.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Gradients/</filename></term>
- <listitem>
- <para>
- This directory contains GIMP gradients. Gradients stored in
- this directory will be available inside GIMP's gradients
- dialog. This directory organizes gradient files inside
- <filename class="directory">Images</filename> and <filename
- class="directory">Models</filename> directories. Inside
- <filename class="directory">Models</filename> directory we
- find the GIMP projects used to build the gradient images.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Fonts/</filename></term>
- <listitem>
- <para>
- This directory contains font files. Font files stored in this
- directory will be available to be used from applications like
- GIMP and Inkscape. This directory organizes font files inside
- <filename class="directory">Images</filename> and <filename
- class="directory">Models</filename> directories. Inside
- <filename class="directory">Models</filename> directory we
- find the Fontforge projects used to build the font files,
- which are stored in the <filename
- class="directory">Images</filename> directory.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Images/</filename></term>
- <listitem>
- <para>
- This directory contains final images. The directory structure
- used to organize files here is rather similar to that used in
- <filename class="directory">Artworks/Models/</filename>
- directory structure.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Images/Themes/</filename></term>
- <listitem>
- <para>
- This directory contains image files rendered from design
- models that use theme background images. In this location you
- can also find design models used to create the background
- images, too.
- </para>
- <caution>
- <para>
- Design models used to build themes' background images must not
- be moved to <filename
- class="directory">Artworks/Models/Themes/</filename> directory
- structure. Design models used to build themes' background
- images are theme-specific, so they must be inside <filename
- class="directory">Artworks/Images/Themes/</filename> directory
- structure.
- </para>
- </caution>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/</filename></term>
- <listitem>
- <para>
- This directory contains theme directory structure
- organized in version number. Here, ${THEME_NAME} is a
- string of letters representing the name of the theme. In
- this string, all letters are written in lowercase except
- the first one which must be written in uppercase.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/</filename></term>
- <listitem>
- <para>
- This directory contains the theme directory structure
- organized in theme components. Here, ${THEME_VERSION} is a
- string with the form M.N, where M and N are integer
- numbers from 0 to 9. M is required and .N is optional.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Backgrounds/</filename></term>
- <listitem>
- <para>
- This directory contains theme-specific background images
- and design models used to build them. This directory is a
- key component of theme concept. It provides background
- images to different sizes which are use on different theme
- components, as defined by theme design models stored at
- <filename
- class="directory">Artworks/Models/Themes</filename>
- directory.
- </para>
-
- <table id="repo-convs-directories-tb1">
- <title>Theme-specific background files</title>
- <tgroup cols='2' align='left' colsep='1' rowsep='1'>
- <thead>
- <row>
- <entry>Images/</entry>
- <entry>Models/</entry>
- <entry>Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><filename>160x600-final.png</filename>, <filename>160x600-final.jpg</filename></entry>
- <entry><filename>160x600-final.svgz</filename>,
- <filename>160x600-final.xcf</filename></entry>
- <entry>Graphic design at 160x600 pixels, used to
- produce the left-side bar of <quote>Firstboot</quote>
- theme component.</entry>
- </row>
- <row>
- <entry><filename>200x150-final.png</filename>, <filename>200x150-final.jpg</filename></entry>
- <entry><filename>200x150-final.svgz</filename>, <filename>200x150-final.xcf</filename></entry>
- <entry>Graphic design at 200x150 pixels, used to produce
- the screenshot of both
- <quote>Gdm</quote> and <quote>Kdm</quote> theme
- components.
- </entry>
- </row>
- <row>
- <entry><filename>400x300-final.png</filename>, <filename>400x300-final.jpg</filename></entry>
- <entry><filename>400x300-final.svgz</filename>, <filename>400x300-final.xcf</filename></entry>
- <entry>Graphic design at 400x300 pixels, used to
- produce the splash component of both
- <quote>Gnome</quote> and <quote>Kde</quote> theme
- components.</entry>
- </row>
- <row>
- <entry><filename>490x200-final.png</filename>, <filename>490x200-final.jpg</filename></entry>
- <entry><filename>490x200-final.svgz</filename>, <filename>490x200-final.xcf</filename></entry>
- <entry>Graphic design at 490x200 pixels, used to
- produce the splash image of <quote>Anaconda</quote>
- theme component.</entry>
- </row>
- <row>
- <entry><filename>510x300-final.png</filename>, <filename>510x300-final.jpg</filename></entry>
- <entry><filename>510x300-final.svgz</filename>, <filename>510x300-final.xcf</filename></entry>
- <entry>Graphic design at 510x300 pixels, used to
- produce the slide images of <quote>Anaconda</quote> theme component.</entry>
- </row>
- <row>
- <entry><filename>640x300-final.png</filename>, <filename>640x300-final.jpg</filename></entry>
- <entry><filename>640x300-final.svgz</filename>, <filename>640x300-final.xcf</filename></entry>
- <entry>Graphic design at 640x300 pixels, used to
- produce the splash image of <quote>Syslinux</quote>
- theme component.</entry>
- </row>
- <row>
- <entry><filename>640x480-final.png</filename>, <filename>640x480-final.jpg</filename></entry>
- <entry><filename>640x480-final.svgz</filename>, <filename>640x480-final.xcf</filename></entry>
- <entry>Graphic design at 640x480 pixels, used to
- produce the splash image of <quote>Grub</quote> theme
- component.</entry>
- </row>
- <row>
- <entry><filename>744x1052-final.png</filename>, <filename>744x1052-final.jpg</filename></entry>
- <entry><filename>744x1052-final.svgz</filename>, <filename>744x1052-final.xcf</filename></entry>
- <entry>Graphic design at 744x1052 pixels, used to
- produce the <quote>Posters</quote> theme components.</entry>
- </row>
- <row>
- <entry><filename>800x600-final.png</filename>, <filename>800x600-final.jpg</filename></entry>
- <entry><filename>800x600-final.svgz</filename>, <filename>800x600-final.xcf</filename></entry>
- <entry>Graphic design at 800x600 pixels, used to
- produce the <quote>Concept</quote> theme component.</entry>
- </row>
- <row>
- <entry><filename>800x88-final.png</filename>, <filename>800x88-final.jpg</filename></entry>
- <entry><filename>800x88-final.svgz</filename>, <filename>800x88-final.xcf</filename></entry>
- <entry>Graphic design at 800x88 pixels, used to
- produce the heading image of <quote>Anaconda</quote>
- theme component.</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <para>
- Besides background files described in <xref
- linkend="repo-convs-directories-tb1" />, you'll also find
- background files for specific screen resolutions. The
- number of files you find here may vary depending the
- screen resolutions demanded by &TCD; at <filename
- class="directory">/usr/share/backgrounds/</filename>.
- Resolution-specific background files follow the same name
- convention described in the table above but change the
- resolution numbers to show the screen resolution they
- represent (e.g., <filename>1360x768-final.png</filename>
- for 1360x768 screen resolutions.).
- </para>
- <para>
- The word <quote>-final</quote> is used on background files
- to mark them as ready for applying. When you design
- background images, you might need to create intermediate
- images so as to reach desired effects by combining them
- into a final one. Such intermediate images do not use the
- word <quote>-final</quote>. Only the result of all your
- combinations and tests must have the word
- <quote>-final</quote> on its name.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Backgrounds/Images/</filename></term>
- <listitem>
- <para>
- This directory contains theme-specific background images,
- mostly in PNG and JPG formats. The files in this
- directory are used by <command>centos-art.sh</command>
- script to produce theme components. The relation between
- image files and theme component is described in <xref
- linkend="repo-convs-directories-tb1" />.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Backgrounds/Models/</filename></term>
- <listitem>
- <para>
- This directory contains theme-specific background design
- models, mostly in SVGZ and XCF formats. The files in this
- directory are used to produce theme-specific background
- images, only.
- </para>
- <para>
- Design models in this directory must not be confused with
- design models stored in <filename
- class="directory">Artworks/Models/Theme/</filename>
- directory. Design models stored in this directory are
- theme-specific while design models stored in <filename
- class="directory">Artworks/Models/Theme/</filename> are
- common to all themes.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Concept/</filename></term>
- <listitem>
- <para>
- This directory contains theme-specific conceptual ideas.
- The images in this directory can be used to present the
- theme's artistic motif in the community. These images
- include can include theme name, theme version, theme
- author, theme license, theme copyright and similar
- information.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Distro/</filename></term>
- <listitem>
- <para>
- This directory contains theme-specific images for each
- component of &TCD;. In this location, images are organized
- in distribution major release, distribution component and
- language, if the current locale is different from English
- language.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Gradients/</filename></term>
- <listitem>
- <para>
- This directory contains theme-specific GIMP gradients.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Palettes/</filename></term>
- <listitem>
- <para>
- This directory contains theme-specific GIMP palettes.
- The centos-art.sh script uses theme-specific palettes to produce indexed
- images with reduced number of colors used by specific
- theme components, like <quote>Syslinux</quote> and
- <quote>Grub</quote>. These components have specific color
- requirements which we must comply with.
- </para>
-
- <para>
- <xref linkend="repo-convs-directories-tb2" />, describes
- the palettes files used inside themes and the number of
- colors they require.
- </para>
-
- <table id="repo-convs-directories-tb2">
- <title>Theme-specific palette files</title>
- <tgroup cols='2' align='left' colsep='1' rowsep='1'>
- <thead>
- <row>
- <entry>File</entry>
- <entry>Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><filename>syslinux.gpl</filename></entry>
- <entry>
- This palette is used to produce Syslinux final image.
- This palette must be created to hold 16 colors using GIMP's
- palette format. Inside the palette file, the color
- information is organized in an index that begins at 0
- and ends at 15. In this index, the color information
- set at position 0 must be the background color used in
- the image (e.g., the darkest color in the list) and
- the color information set at position 7 must be the
- foreground color used in the image (e.g., the lightest
- color in the list).
- </entry>
- </row>
- <row>
- <entry><filename>grub.gpl</filename></entry>
- <entry>This palette is used to produce Grub final image.
- This palette must be created to hold 14 colors using
- GIMP's palette format. Inside the palette file, color
- information can be set in any order.</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <tip>
- <para>
- To produce optimum palettes of colors, open with GIMP the
- full-colored PNG image you need to reduce colors to and
- reduce colors using GIMP's indexing tool at
- <guimenuitem>Mode</guimenuitem> →
- <guimenuitem>Indexed...</guimenuitem> from
- <guimenu>Image</guimenu> menu. Later, you import the set
- of colors into a new palette using the GIMP palettes
- editor and save it here. This way, you can grantee
- <command>centos-art.sh</command> script will use the
- correct color information when it produces images with
- reduced colors for theme-specific components.
- </para>
- </tip>
-
- <caution>
- <para>
- When you create theme-specific palettes, it is necessary
- that you fill the comment field of palette file using the
- related color information in hexadecimal format.
- Otherwise, centos-art.sh script won't be able to realize
- image conversion from PNG to LSS format.
- </para>
- </caution>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Patterns/</filename></term>
- <listitem>
- <para>
- This directory contains theme-specific GIMP patterns.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Screenshots/</filename></term>
- <listitem>
- <para>
- This directory contains theme-specific screenshots. It is
- a series of images illustrating the theme already in
- place. Here you'll find one screenshot for each relevant
- component inside &TCD;.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Models/</filename></term>
- <listitem>
- <para>
- This directory contains design models (e.g., scalable vector
- graphics using the <filename
- class="extension">.svgz</filename> extension) and image
- configuration files (e.g., plain text using the <filename
- class="extension">.conf</filename> extension) used by
- <command>centos-art.sh</command> script to produce images
- inside <filename
- class="directory">Artworks/Images/</filename>. Relevant
- components inside this directory include Brands, Icons, Themes
- and Webenv.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Models/Brands/</filename></term>
- <listitem>
- <para>
- This directory organizes branding information for &TCP;.
- Relevant components inside this directory include Logos/,
- Symbols/, and Types/ directories. If you need to tune up &TCP;
- branding information, this is the directory you need to go to.
- To know more about &TCB;, see <xref linkend="identity-brand" />.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Models/Icons/</filename></term>
- <listitem>
- <para>
- This directory organizes icon design models for &TCP;. By
- default, &TCD; uses the same icons set packaged inside the
- SRPMs the upstream provider makes available. Only icons related
- to branding information are changed in order to identify
- &TCP; and comply with upstream redistribution guidelines. This
- directory is not very used by now, it presently contains
- design models for Tango's icons set.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Models/Themes/</filename></term>
- <listitem>
- <para>
- This directory contains design models organized by categories.
- When you are producing theme-specific images, you can use the
- option <option>--theme-model</option> to instruct the
- <command>centos-art.sh</command> script what of these
- categories you want to use as reference to produce
- theme-specific images.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Models/Themes/Default/</filename></term>
- <listitem>
- <para>
- This directory contains default design models used to produce
- theme-specific images, when the
- <option>--theme-option</option> is not provided to
- <command>centos-art.sh</command> script at theme-specific
- images rendition time. This directory is also used as
- reference by <command>centos-art.sh</command> script to build
- the theme-specific directory structures inside <filename
- class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/</filename>
- directory, when the <xref linkend="scripts-bash-prepare" />
- functionality is executed. So, if you find that some
- directories in this location are empty, don't remove them.
- They should be present in order for
- <command>centos-art.sh</command> script to prepare
- theme-specific directory structures correctly.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Models/Themes/Default/Concept/</filename></term>
- <listitem>
- <para>
- This directory contains design models used to produce the
- conceptual presentation of each theme. This is a 800x600px
- image that illustrate the background artistic motif along the
- license and copyright information. All images produced from
- this design model use the CC-SA license and &TCP; as copyright
- holder.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Models/Themes/Default/Distro/</filename></term>
- <listitem>
- <para>
- This directory contains design models used to produce the
- visual style of each component inside &TCD; for all its major
- releases. The first sub-directory level under this directory
- will contain the major release which components will be
- produced for. Inside the release-specific directory you will
- find one directory for each related distribution component,
- including <application>Grub</application>,
- <application>Anaconda</application>,
- <application>Gdm</application>,
- <application>Syslinux</application>,
- <application>Firstboot</application> and others.
- </para>
-
- <para>
- The components you find inside &TCD; may vary from one major
- release to another. They might be added or removed as required
- in each new major release. Thus, it is very important to keep
- the relation between components and major releases accurate
- inside this directory.
- </para>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Models/Themes/Default/Media/</filename></term>
- <listitem>
- <para>
- This directory contains design models used to produce visual
- style for installation media, including CDs, DVDs, LiveCDs and
- LiveDVDs. We don't use release-specific directories in this
- location because it is determined automatically from the
- <filename>/etc/redhat-release</filename> file or the
- <option>--releasever</option> option through the command-line
- of <command>centos-art.sh</command> script.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Models/Themes/Default/Palettes/</filename></term>
- <listitem>
- <para>
- This directory contains the palettes of colors used by
- <command>centos-art.sh</command> script when no one is found
- inside <filename
- class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Palettes/</filename>
- directory.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Models/Themes/Default/Gradients/</filename></term>
- <listitem>
- <para>
- This directory is empty. It is used to build theme-specific
- directory structures. Don't remove it.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Models/Themes/Default/Patterns/</filename></term>
- <listitem>
- <para>
- This directory is empty. It is used to build theme-specific
- directory structures. Don't remove it.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Models/Themes/Default/Posters/</filename></term>
- <listitem>
- <para>
- This directory contains design models used by
- <command>centos-art.sh</command> script to produce posters.
- Posters are promotional stuff, generally printed in different
- media and sizes to be shown on events.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Models/Webenv/</filename></term>
- <listitem>
- <para>
- This directory contains common design models used by &TCWE;.
- These images include, admonition icons, heading backgrounds,
- html backgrounds, admonition backgrounds and whatever
- graphical information &TCWE; could need.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Palettes/</filename></term>
- <listitem>
- <para>
- This directory contains GIMP palettes that you always want to
- have available in GIMP sessions.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Patterns/</filename></term>
- <listitem>
- <para>
- This directory contains GIMP patterns that you always want to
- have available in GIMP sessions.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Artworks/Webenv/</filename></term>
- <listitem>
- <para>
- This directory contains customizations for specific web
- applications. The kind of files you find here vary from one
- web application to another. Generally, you find <filename
- class="extension">.css</filename> and <filename
- class="extension">.html</filename> files here. Relevant
- components inside this directory include Docbook, Httpd,
- Mantis, Moin, PhpBB, Punbb, Puntal, Style-guide, Texi2html and
- Trac.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- </section>
-
- <section id="repo-convs-directories-documentation">
- <title>The <filename class="directory">Documentation</filename> Directory</title>
- <para>
- This directory contains documentation related to &TCAR;
- written in different formats. This directory is organized in
- Models and Manuals. Models contain the documentation source
- files and Manuals the final documentation ready to be read
- through different media (e.g., online and paper). Here, the
- language used to write documentation manuals is English.
- </para>
-
- <variablelist>
- <varlistentry>
- <term><filename class="directory">Documentation/Models/</filename></term>
- <listitem>
- <para>
- This directory contains documentation source formats used
- inside &TCAR;.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Documentation/Models/${MANUAL_FORMAT}/</filename></term>
- <listitem>
- <para>
- This directory contains documentation manuals' name for
- specific documentation formats.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Documentation/Models/${MANUAL_FORMAT}/${MANUAL_NAME}/</filename></term>
- <listitem>
- <para>
- This directory contains the documentation manual directory
- structure. Here is where source files are stored in. If you
- want to modify content from a documentation manual, this is
- the directory level you need to go to.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><filename class="directory">Documentation/Manuals/</filename></term>
- <listitem>
- <para>
- This directory organizes documentation final files, organized
- by documentation format, documentation manual name and
- documentation language, if documentation files were produced
- to a language different from English.
- </para>
- </listitem>
- </varlistentry>
-
- </variablelist>
-
- <para>
- Several documentation formats have been used to write &TCAR;
- documentation manuals through time, including
- <application>Texinfo</application>,
- <application>LaTeX</application> and finally
- <application>DocBook</application>. From these documentation
- formats, DocBook is addressed to be the one adopted in the
- near future as default documentation format inside &TCAR;.
- Support for other documentation formats will remain inside
- <command>centos-art.sh</command> script without further
- improvements. This in order to dedicate more attention to
- DocBook documentation format.
- </para>
-
- <para>
- The directory structure used by each documentation format is
- not described in this section. To know more about
- documentation formats and the directory structure used by
- documentation manuals, read <xref linkend="manuals-formats"
- />.
- </para>
-
- </section>
-
- <section id="repo-convs-directories-localization">
- <title>The <filename class="directory">Localization</filename> Directory</title>
- <para>
- ...
- </para>
- </section>
-
- <section id="repo-convs-directories-automation">
- <title>The <filename class="directory">Automation</filename> Directory</title>
- <para>
- ...
- </para>
- </section>
-
- <section id="repo-convs-directories-packages">
- <title>The <filename class="directory">Packages</filename> Directory</title>
- <para>
- ...
- </para>
- </section>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/extending.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/extending.docbook
deleted file mode 100755
index a270e5a..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/extending.docbook
+++ /dev/null
@@ -1,44 +0,0 @@
-<section id="repo-convs-extending">
-
- <title>Extending Repository Layout</title>
-
- <para>
- Occasionly, you may find that new components of &TCPCVI; 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 starting to create directories blindly all over, is:
- <emphasis>What is the right place to store it?</emphasis>
- </para>
-
- <para>
- To build a directory structure inside the repository you need
- to define the concept behind it first. Later you need to
- create a new directory inside the repository, remembering that
- there are locations inside the repository that already define
- concepts you probably would prefer to reuse. For example, the
- <filename
- class="directory">Identity/Images/Themes</filename>
- directory stores artistic motifs of different themes, the
- <filename
- class="directory">Identity/Models/Themes</filename>
- directory stores design models for themes, the <filename
- class="directory">Manuals</filename> directory stores
- documentation, the <filename
- class="directory">Locales</filename> stores translation
- messages, and the <filename
- class="directory">Scripts</filename> stores automation
- scripts.
- </para>
-
- <para>
- The best suggestion we can probably give you would be to send
- a mail with your questions to the <ulink
- url="mailto:centos-devel@centos.org">CentOS developers mailing
- list</ulink> (<ulink
- url="mailto:centos-devel@centos.org">centos-devel@centos.org</ulink>).
- This is the place where development of &TCAR; takes place and
- surely, in community, it will be possible to find a place for
- your new component inside the repository.
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/filenames.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/filenames.docbook
deleted file mode 100755
index c43fada..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/filenames.docbook
+++ /dev/null
@@ -1,185 +0,0 @@
-<section id="repo-convs-filenames">
-
- <title>Repository File Names</title>
-
- <section id="repo-convs-filenames-rfiles">
- <title>Regular Files</title>
-
- <para>
- Inside &TCAR;, file names are always written in lowercase.
- Digits (e.g., 0, 1, 2), hyphen (<code>-</code>), dot
- (<code>.</code>) and low line (<code>_</code>)
- characters are also accepted. In case you use hyphen and dot
- characters, don't use them as first character in the file
- name.
- </para>
-
- <section id="repo-convs-filenames-rfiles-ok">
- <title>Files Written Correctly</title>
- <para>
- The following file names are written correctly:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <filename>01-welcome.png</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>splash.png</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>anaconda_header.png</filename>
- </para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section id="repo-convs-filenames-rfiles-wrong">
- <title>Files Written Incorrectly</title>
- <para>
- The following file names are written incorrectly:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <filename>01-Welcome.png</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>-welcome.png</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>Splash.png</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename>AnacondaHeader.png</filename>
- </para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section id="repo-convs-filenames-rfiles-exceptions">
- <title>Exceptions</title>
- <para>
- When you name files, consider the following exceptions:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- In the very specific case of repository documentation entries
- written in Texinfo format, file names follow the directory
- structure naming convenction. This is because they are
- documenting directories and that is something
- we want to remark. So, to better describe what we are
- documenting, files related to documentation entries follow the
- name convenction used by the item they document.
- </para>
- </listitem>
- </itemizedlist>
-
- </section>
-
- </section>
-
- <section id="repo-convs-filenames-hfiles">
- <title>Symbolic Links</title>
- <para>
- Inside &TCAR;, symbolic link names follow the same
- convenctions described in <xref
- linkend="repo-convs-filenames-rfiles"/>.
- </para>
- </section>
-
- <section id="repo-convs-filenames-dfiles">
- <title>Directories</title>
- <para>
- Inside &TCAR;, directory names are all written capitalized and
- sometimes in cammel case. Digits (e.g., 0, 1, 2), hyphen
- (<code>-</code>), dot (<code>.</code>) and low line
- (<code>_</code>) characters are also accepted. In case you
- use hyphen and dot characters, don't use them as first
- character in the directory name.
- </para>
-
- <section id="repo-convs-filenames-dfiles-ok">
- <title>Directories Written Correctly</title>
- <para>
- The following directory names are written correctly:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <filename class="directory">Identity</filename>,
- <filename class="directory">Themes</filename>,
- <filename class="directory">Motifs</filename>,
- <filename class="directory">TreeFlower</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename class="directory">Tcar-ug</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename class="directory">0.0.1</filename>, <filename
- class="directory">0.0.1-35</filename>
- </para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section id="repo-convs-filenames-dfiles-wrong">
- <title>Directories Written Incorrectly</title>
- <para>
- The following directory names are written incorrectly:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <filename class="directory">identitY</filename>,
- <filename class="directory">theMes</filename>,
- <filename class="directory">MOTIFS</filename>,
- <filename class="directory">treeFlower</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename class="directory">tcar-ug</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename class="directory">.0.1</filename>, <filename
- class="directory">.0.1-35</filename>
- </para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section id="repo-convs-filenames-dfiles-exceptions">
- <title>Exceptions</title>
- <para>
- When you name directories, consider the following exceptions:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- No one so far.
- </para>
- </listitem>
- </itemizedlist>
- </section>
-
- </section>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/infra.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/infra.docbook
deleted file mode 100755
index 69f49ba..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/infra.docbook
+++ /dev/null
@@ -1,142 +0,0 @@
-<section id="repo-convs-infra">
-
- <title>Repository Infrastructure</title>
-
- <para>
- &TCAR; is made of one <quote>central repository</quote> and
- many <quote>working copies</quote> of that central repository.
- The working copies are independent one another, can be
- distributed all around the world and provide a local place for
- designers, documenters, translators and programmers to perform
- their work in a decentralized way. The central repository, on
- the other hand, provides a common place for all independent
- working copies to exchange data in the community.
- </para>
-
- <figure id="repo-convs-infra-1">
- <title>Repository infrastructure</title>
- <screenshot>
- <screeninfo>Repository infrastructure</screeninfo>
- <mediaobject>
- <imageobject>
- <imagedata fileref="=TCAR_WORKDIR=/Documentation/Manuals/Svg/Repository/infrastructure.png" format="PNG" />
- </imageobject>
- </mediaobject>
- </screenshot>
- </figure>
-
- <section id="repo-convs-infra-subversion">
- <title>Subversion</title>
-
- <para>
- The current infrastructure that holds &TCAR;, on the Internet,
- is made of the following components:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <application><ulink
- url="http://subversion.tigris.org/">Subversion</ulink></application>
- — Modern Version Control System designed to replace CVS.
- </para>
- </listitem>
- <listitem>
- <para>
- <application><ulink
- url="http://trac.edgewall.org/">Trac</ulink></application>
- — Enhanced wiki and issue tracking system.
- </para>
- </listitem>
- <listitem>
- <para>
- <application>Httpd+WebDav</application> as data exchanging route between the workstations
- and the central repository, through the Internet. Httpd was
- configured to provide service through SSL, so all traffic
- between the workstations and the server be protected while it
- travels across the Internet. </para>
- </listitem>
- <listitem>
- <para>
- The access rights are controlled by using a combination of both
- Subversion's authorization files and Httpd's password files.
- These files can be managed consistently through Trac's WebAdmin
- plug-in.
- </para>
- </listitem>
- </itemizedlist>
-
- <para>
- In this infrastructure, the first level of directories in the
- repository provides the Subversion's standard
- trunk-branches-tags layout. The second level of directories
- provides organization for different work lines, as described
- in <xref linkend="repo-convs-worklines" />. All other
- subsequent directory levels from second level on exist to
- organize specific concepts related to the work line they
- belong to.
- </para>
-
- </section>
-
- <section id="repo-convs-infra-git">
- <title>Git</title>
-
- <para>
- In addition to current Subversion infrastructure, we are
- working on a Git infrastructure with the intention of
- migrating the current Subversion infrastructure up to it,
- progressively. The Git infrastructure we are working on is
- made of the following components:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- Git — Fast version control system.
- </para>
- </listitem>
- <listitem>
- <para>
- <application>Gitolite</application> — Highly flexible
- server for git directory version tracker.
- </para>
- </listitem>
- <listitem>
- <para>
- <application>Gitweb</application> — Simple web interface
- to git repositories.
- </para>
- </listitem>
- <listitem>
- <para>
- <application>MantisBT</application> — Web-based issue
- tracking system.
- </para>
- </listitem>
- <listitem>
- <para>
- The data exchanging route between the working copies and the
- central repository takes place through SSH.
- </para>
- </listitem>
- <listitem>
- <para>
- The access rights are controlled by using a combination of SSH
- public keys and Gitolite's repository configuration file.
- </para>
- </listitem>
- </itemizedlist>
-
- <para>
- In this infrastructure, the first level of directories in the
- repository provides organization for different work lines, as
- described in <xref linkend="repo-convs-worklines" />. All
- other subsequent directory levels from second level on exist
- to organize specific concepts related to the work line they
- belong to.
- </para>
-
- </section>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/mission.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/mission.docbook
deleted file mode 100755
index 32c6a9d..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/mission.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<section id="repo-convs-mission">
-
- <title>Repository Mission</title>
-
- <para>
- &TCAR; exists to produce &TCP; corporate visual identity.
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/publishing.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/publishing.docbook
deleted file mode 100755
index 71bcd14..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/publishing.docbook
+++ /dev/null
@@ -1,59 +0,0 @@
-<section id="repo-convs-publishing">
-
- <title>Repository Publishing</title>
-
- <para>
- When you perform changes inside your working copy, those
- changes are local to your working copy only. In order for you
- to share your changes with others, you need to commit them up
- to the central repository the working copy you are using was
- initially downloaded from. To commit your changes up to the
- central repository you use the <command>commit</command>
- command from the Subversion's client you've installed in your
- workstation.
- </para>
-
- <para>
- Initially, when you get registered inside &TCAR;, you won't be
- able to publish your changes to &TCAR; immediatly. It is
- necessary that you prove your interest in contributing first
- sending a mail to the <ulink
- url="http://lists.centos.org/mailman/listinfo/centos-devel">CentOS
- Developers mailing list</ulink> (<ulink
- url="mailto:centos-devel@centos.org">centos-devel@centos.org</ulink>),
- preferably in conjunction with a description of the changes
- you pretend to commit. This restriction is necessary in order
- to protect the source repository from spammers.
- </para>
-
- <para>
- Once you've received access to publish your changes, they will
- remain valid to you and there is no need for you to request
- permission to publish new changes as long as you behave as a
- good cooperating citizen.
- </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. As complement, 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 that everything goes the way it needs
- to go in order for &TCAR; to accomplish its mission (see <xref
- linkend="repo-convs-mission" />).
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/relbdirs.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/relbdirs.docbook
deleted file mode 100755
index 835f241..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/relbdirs.docbook
+++ /dev/null
@@ -1,157 +0,0 @@
-<section id="repo-convs-relbdirs">
-
- <title>Repository Path Relations</title>
-
- <para>
- In order for automation scripts to produce content inside a
- working copy of &TCAR;, it is required that all work lines be
- related somehow. The automation scripts take the relation
- between work lines as reference to determine the place the
- information they will work with will be retrieve from (e.g.,
- scalable vector graphics, documentation, translations, etc.),
- as well as the place where it will store the final files
- produced as result of automation process (e.g., portable
- network graphics, documentation ready for printing and reading
- online, etc.).
- </para>
- <para>
- In order to implement the relation between work lines it is
- required to establish a path name convenction, so we can
- conceptually organize different components and relate them one
- another using predictable path constructions in a scalable
- way. Based on this need, we identify three different path
- types inside &TCAR;. These path types are: <emphasis>Output
- Paths</emphasis>, <emphasis>Input Paths</emphasis>, and
- <emphasis>Auxiliary Paths</emphasis>.
- </para>
-
- <section id="repo-convs-relbdirs-renderable">
- <title>Output Paths</title>
-
- <para>
- The output paths point to directories inside the working copy
- which contain files produced from files inside the input
- paths. For example, the following paths are consider as output
- paths:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <filename class="directory">Identity/Images/Brands/</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename class="directory">Documentation/Manuals/Tcar-ug/</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename class="directory">Identity/Images/Themes/Modern/2/Distro/5/Anaconda/</filename>
- </para>
- </listitem>
- </itemizedlist>
-
- <para>
- Output paths are also known as <emphasis><quote>Render-able
- Directories</quote></emphasis> because they are the type of
- path you should provide as argument to <xref
- linkend="scripts-bash-render" /> functionality so as to
- produce content through it.
- </para>
-
- </section>
-
- <section id="repo-convs-relbdirs-designmodels">
- <title>Input Paths</title>
- <para>
- The input paths point to a directories inside the working copy
- which contain files used to produce files inside output paths.
- For example, the following paths are considered as input
- paths:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <filename class="directory">Identity/Models/Brands/</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename class="directory">Documentation/Models/Tcar-ug/</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename class="directory">Identity/Models/Themes/Default/Distro/5/Anaconda/</filename>
- </para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section id="repo-convs-relbdirs-auxiliar">
- <title>Auxiliary Paths</title>
-
- <para>
- The auxiliary paths point to directories inside the working
- copy which contain files used to create modified instances of
- inside input paths which are use in turn to produce files
- inside output paths. For example, the following paths are
- considered as auxiliary paths:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <filename class="directory">Identity/Images/Brands/</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename class="directory">Locales/Documentation/Models/Docbook/Tcar-ug/es_ES/</filename>
- </para>
- </listitem>
- <listitem>
- <para>
- <filename class="directory">Locales/Identity/Models/Themes/Default/Distro/5/Anaconda/es_ES/</filename>
- </para>
- </listitem>
- </itemizedlist>
-
- <para>
- The relationship between input, output and auxiliary paths is
- created by combining the first directory level of input paths
- with the first directory level in the repository directory
- layout. In the repository directory layout, the first level
- includes the <filename class="directory">Identity</filename>,
- <filename class="directory">Documentation</filename> and
- <filename class="directory">Scripts</filename> directories.
- These directories are always used to create input and output
- paths. The <filename class="directory">Locales</filename>
- directory, on the other hand, is always used to create
- auxiliary paths only for input paths available under <filename
- class="directory">Identity</filename>, <filename
- class="directory">Documentation</filename> and <filename
- class="directory">Scripts</filename> directories.
- </para>
-
- <para>
- For example, if the <varname>LANG</varname> environment
- variable is set to <quote>es_ES.UTF-8</quote> and you execute
- the <xref linkend="scripts-bash-render"/> functionality of
- <command>centos-art.sh</command> script with the <filename
- class="directory">Documentation/Manuals/Docbook/Tcar-ug/</filename>
- input path as argument, it will produce &TCARUG; in Spanish
- language using translation messages from
- <filename>Locales/Documentation/Models/Docbook/Tcar-ug/es_ES/</filename>
- auxiliary path and would save final documentation files under
- <filename
- class="directory">Documentation/Manuals/Docbook/Tcar-ug/es_ES/</filename>
- output path.
- </para>
-
- </section>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/syncpaths.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/syncpaths.docbook
deleted file mode 100755
index d8e353d..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/syncpaths.docbook
+++ /dev/null
@@ -1,99 +0,0 @@
-<section id="repo-convs-syncpaths">
-
- <title>Syncronizing Repository Paths</title>
-
- <para>
- Once both master and auxiliar paths have been related in the
- repository, they shouldn't be changed except you absolutly
- need to do so. In this cases, when you need to change master
- or auxiliar paths, it is required that you also change the
- relation between them so as to retain their bond. This
- process of keeping master and auxiliar paths
- <quote>connected</quote> between themselves is known as
- <emphasis>path syncronization</emphasis>.
- </para>
-
- <para>
- Path syncronization is required for automation scripts to know
- where to store final output, where to retrive translation
- messages from, and whatever information you might need to
- count with. If the 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 to work with or
- where to store the output information produced from it.
- Through path syncronization we organize and extend the content
- production inside the repository.
- </para>
-
- <para>
- Path syncronization affects both movement of files and
- replacement of content inside files. Movement of files is
- related to actions like renaming files and directories inside
- the repository. Replacement of content inside files is
- related to actions like replacing information (e.g., paths
- information) inside files in order to keep file contents and
- file locations consistent one another after a file has been
- moved.
- </para>
-
- <para>
- The order followed to syncronize path information is very
- important because the versioned nature of the files we are
- working with. When a renaming action needs to be performed
- inside the repository, we avoid making replacements inside
- files first and file movements later. This would demand two
- commit actions: one for the files' internal changes and
- another for the file movement itself. Instead, we prefer to
- perform file movements first and files' internal replacements
- later. This way it is possible to commit both changes as if
- they were just one.
- </para>
-
- <note>
- <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's commands
- instead.
- </para>
- </note>
-
- <para>
- At this moment there isn't full implementation of path
- syncronization inside <command>centos-art.sh</command> script
- and that is somthing we need to do oursleves. However, the
- <quote>texinfo</quote> backend inside the
- <function>help</function> functionality does provide a restricted
- implementation of path syncronization to documentation area
- through the <option>--copy</option>, <option>--delete</option>
- and <option>--rename</option> options. You can read this
- implementation and use it as reference to implement path
- syncronization in other areas.
- </para>
-
- <para>
- The plan for a full implementation of path syncronization
- inside <command>centos-art.sh</command> script would be to
- create individual restricted implementations like the one in
- <quote>texinfo</quote> backend for other areas that demand it
- and then, create a higher implmentation that combines them all
- as needed. This way, if we try to rename a repository
- directory, the higher action can know which are all the
- restricted actions that should be performed in order
- to make the full path syncronization.
- </para>
-
- <para>
- For example, if the directory we are renaming is a master
- path, it is required to syncronize the related output and
- localization auxiliar paths. On the other hand, if the
- directory we are renaming through full path syncronization is
- an auxiliar path, it is required to determine first what is
- the related master path and later, perform the syncronization
- from master path to auxiliar paths as if the path provided
- would be the master path not the auxiliar path.
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/worklines.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/worklines.docbook
deleted file mode 100755
index f31dd87..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Conventions/worklines.docbook
+++ /dev/null
@@ -1,186 +0,0 @@
-<section id="repo-convs-worklines">
-
- <title>Repository Work Lines</title>
-
- <para>
- The content production inside &TCAR; has been divided into
- individual work lines that relate one another based on the
- idea of doing one thing well. In this model, the content
- produced individually by each work line is combined one
- another later to achieve higher purposes (e.g., corporate
- identity for &TCP;). The repository work lines, as conceived
- here, provide a reliable environment for people to work
- synchronized and decentralized.
- </para>
-
- <para>
- The action of combining work lines inside &TCAR; is also known
- as the <quote>Production Cycle</quote> of CentOS corporate
- visual identity. The rest of this section describes the work
- lines available in the repository and how they integrate one
- another.
- </para>
-
- <section id="repo-convs-worklines-artworks">
-
- <title>Artworks</title>
-
- <para>
- <emphasis>Artworks</emphasis> is the first component we work
- out in order to produce new corporate visual identities.
- Through this work line, graphic designers create
- <quote>models</quote> and <quote>motifs</quote> for all the
- visual manifestation &TCP; is made of. Once design models and
- artistic motifs are set in place, graphic designers use the
- <xref linkend="scripts-bash-render" /> functionality to
- combine them into final images.
- </para>
-
- <para>
- The mission of <emphasis>Artworks</emphasis> work line is
- define all the visual manifestations the &TCP; is made of and
- provide design models and artistic motifs for them in order to
- produce the image files required to transmit the visual style
- that identifies &TCP; as unique organization.
- </para>
-
- <para>
- To know more about &TCPCVI;, read <xref linkend="identity" />.
- </para>
-
- </section>
-
- <section id="repo-convs-worklines-l10n">
-
- <title>Localization</title>
-
- <para>
- <emphasis>Localization</emphasis> is the second component that
- must be worked out in the production cycle of CentOS corporate
- visual identity. Through this work line translators localize
- source files (e.g., SVG, DocBook, Shell scripts) which are
- later used to produce localized images, localized
- documentation and localized automation scripts. To localize
- source files, translators use the <xref
- linkend="scripts-bash-locale" /> functionality which takes
- care of retrieving translatable strings from source files and
- provide a consistent localization interface based on GNU
- <application>gettext</application> multi-lingual message
- production tool set and <command>xml2po</command> command.
- </para>
-
- <para>
- The localization process takes place inside the
- <quote><filename
- class="directory">Localization/</filename></quote> directory
- in the first level of each repository directory structure.
- This directory mirrors the renderable directory structures
- outside it and stores <filename
- class="extension">.po</filename> and <filename
- class="extension">.pot</filename> files mainly.
- </para>
-
- <para>
- The mission of <emphasis>Localization</emphasis> work line is
- extend the visual identity (produced in English language) to
- as many native languages as possible, in order for people
- which doesn't understand English language to feel more
- comfortable with &TCP; in their own native languages.
- </para>
-
- <para>
- To know more about the specific localization process read
- <xref linkend="locale" />.
- </para>
-
- </section>
-
- <section id="repo-convs-worklines-manuals">
-
- <title>Documentation</title>
-
- <para>
- The documentation work line is the third component that must
- be worked out in the corporate identity production cycle.
- Through this work line documentors settle down the conceptual
- and practical used to edificate &TCAR;. To write
- documentation, documentors use the <function>help</function>
- functionality described in <xref linkend="scripts-bash-help"
- /> which provides a consistent interface for building
- documentation through different documentation backends (e.g.,
- Texinfo, DocBook, LaTeX, etc.).
- </para>
-
- <para>
- The main purpose of this work line is describe the standard
- procedures &TCAR; realies on, as well as conceive a place to
- help you understand what &TCAR; is and what can you do with
- it.
- </para>
-
- <para>
- The documentation work line takes palce in the <ulink
- url="https://projects.centos.org/~al/artwork.git/Manuals"><filename
- class="directory">Manuals</filename></ulink> directory.
- </para>
-
- </section>
-
- <section id="repo-convs-worklines-packages">
- <title>Packages</title>
-
- <para>
- The packages work line is the fourth component that must be
- worked out in the corporate identity production cycle. Through
- this work line packager gather final images, final
- translations and final documentation related to art works and
- put all together inside RPM packages. For this purpose,
- packagers use the <function>pack</function> describe in
- <xref linkend="scripts-bash-pack" /> which provides a
- consistent interface for building packages inside the
- repository.
- </para>
-
- <para>
- The main purpose of this work line is pack all the information
- &TCP; requires to rebrand &TCD; according Red Hat
- redistribution guidelines.
- </para>
-
- <para>
- The packages work line takes palce in the <ulink
- url="https://projects.centos.org/~al/artwork.git/Packages"><filename
- class="directory">Packages</filename></ulink> directory.
- </para>
-
- </section>
-
- <section id="repo-convs-worklines-scripts">
-
- <title>Automation</title>
-
- <para>
- The automation work line is the fifth and last component that
- must be worked out in the corporate identity production cycle.
- This work line closes the production cycle and provides the
- production standards graphic designers, documentors,
- translators and packagers need to make their work consistent
- and reusable. For this purpose, programmers develop the
- <command>centos-art.sh</command> script described in <xref
- linkend="scripts" />.
- </para>
-
- <para>
- The main purpose of this work line is standardize the
- interaction of work lines in a reliable way.
- </para>
-
- <para>
- The automation work line takes palce in the <ulink
- url="https://projects.centos.org/~al/artwork.git/Scripts"><filename
- class="directory">Scripts</filename></ulink> directory.
- </para>
-
- </section>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/History.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/History.docbook
deleted file mode 100644
index ca54c8a..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/History.docbook
+++ /dev/null
@@ -1,17 +0,0 @@
-<chapter id="repo-history">
-
- <title>Repository History</title>
-
- <para>
- This chapter summarizes relevant changes committed to &TCAR;
- along the years.
- </para>
-
- &repo-history-2008;
- &repo-history-2009;
- &repo-history-2010;
- &repo-history-2011;
- &repo-history-2012;
- &repo-history-2013;
-
-</chapter>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2008.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2008.docbook
deleted file mode 100644
index aff53c8..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2008.docbook
+++ /dev/null
@@ -1,67 +0,0 @@
-<section id="repo-history-2008">
-
- <title>2008's</title>
-
- <para>
- &TCAR; started at <ulink
- url="mailto:centos-devel@centos.org">The CentOS Developers
- Mailing List</ulink> around 2008, on a discussion about how to
- automate slide images used by Anaconda (&TCD; installer). In
- such discussion, <ulink
- url="http://wiki.centos.org/RalphAngenendt">Ralph
- Angenendt</ulink> rose up his hand to ask —Do you have
- something to show?—.
- </para>
-
- <para>
- To answer the question, <ulink
- url="http://wiki.centos.org/AlainRegueraDelgado">Alain Reguera
- Delgado</ulink> suggested a bash script which combined SVG and
- SED files in order to produce PNG images in different
- languages —in conjunction with the proposition of
- creating a Subversion repository where translations and image
- production could be distributed inside &TCC;—.
- </para>
-
- <para>
- <ulink url="http://wiki.centos.org/KaranbirSingh">Karanbir
- Singh</ulink> considered the idea intresting and provided the
- infrastructure necessary to support the effort. This way,
- &TCAS; and &TCAR; were officially created and made world wide
- available. In this configuration, users were able to register
- themselves and administrators were able to assign access
- rights to registered users inside &TCAR;, both using a web
- interface.
- </para>
-
- <para>
- Once &TCAR; was available, Alain Reguera Delgado uploaded the
- bash script used to produce the Anaconda
- slides;<footnote><para>See <ulink
- url="https://projects.centos.org/trac/artwork/browser/Main/render.sh?rev=15"
- /></para></footnote> Ralph Angenendt documented it very
- well;<footnote><para>See <ulink type="http"
- url="https://projects.centos.org/trac/artwork/wiki/HowToTranslateSlides"
- /></para></footnote> and people started to download working
- copies of &TCAR; to produce slide images in their own
- languages.<footnote><para>See the following <ulink
- url="http://www.google.com/search?q=anaconda+slides+site%3Alists.centos.org">Google
- search</ulink>.</para></footnote>
- </para>
-
- <para>
- From this time on &TCAR; has been evolving into an automated
- production environment where &TCC; can conceive &TCP;
- corporate visual identity.
- </para>
-
- <para>
- The exact changes commited to &TCAR; through history can be
- found in the <ulink
- url="https://projects.centos.org/trac/artwork/timeline">repository
- logs</ulink> so you can know the real history about it. For
- those of you who just want to get a glance of changes
- committed, see <xref linkend="repo-history" />.
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2009.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2009.docbook
deleted file mode 100644
index 725ca9c..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2009.docbook
+++ /dev/null
@@ -1,55 +0,0 @@
-<section>
-
- <title>2009's</title>
-
- <para>
- Around 2009, 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,
- different from 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 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 art work that needed to be produced. In this
- configuration, if you would want to produce the same art work
- 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>
- Corporate identity concepts began to be considered. As
- referece, it was used the book "Corporate Identity" by Wally
- Olins (1989) and <ulink
- url="http://en.wikipedia.org/Corporate_identity">Wikipedia
- related links</ulink>. This way, the rendition script main's
- goal becomes to: <emphasis>automate the production process of
- a monolithic corporate visual identity structure, based on the
- mission and the release schema of The CentOS
- Project</emphasis>.
- </para>
-
- <para>
- The repository directory structures began to be documented by
- mean of flat text files. Later, documentation in flat text
- files was moved onto LaTeX format and this way &TCARUG; was
- initiated.
- </para>
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2010.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2010.docbook
deleted file mode 100644
index 4faacb0..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2010.docbook
+++ /dev/null
@@ -1,78 +0,0 @@
-<section>
-
- <title>2010's</title>
-
- <para>
- Around 2010, 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., documentation and localization).
- </para>
-
- <para>
- The <command>centos-art.sh</command> was initially conceived
- to automate frequent tasks inside the repository based in the
- idea of Unix toolbox: to create small and specialized tools
- that do one thing well. This way, functionalities inside
- <command>centos-art.sh</command> began to be 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 <quote>common
- functionalities</quote> and <quote>specific
- functionalities</quote> 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>
- Suddenly, no need was found to keep all the links spreaded
- around the repository in order to execute the
- <command>centos-art.sh</command> script from different
- locations. The <command>centos-art</command> command-line
- interface was used instead. The <command>centos-art</command>
- command-line interface is a symbolic link stored inside the
- <filename class="directory">~/bin</filename> directory
- pointing to <command>centos-art.sh</command> script. As
- default configuration, inside The CentOS Distribution, the
- path to <filename class="directory">~/bin</filename> is
- included in the search path for commands (see
- <envar>PATH</envar> environment variable). This way, using
- the <command>centos-art</command> command-line interface, it
- is possible to execute the <command>centos-art.sh</command>
- script from virtually anywhere inside the workstation, just as
- we frequently do with regular commands.
- </para>
-
- <para>
- Start using GNU getopt as default option parser inside the
- <command>centos-art.sh</command> script.
- </para>
-
- <para>
- The repository directory structure was updated to improve the
- implementation of corporate visual identity concepts.
- Specially in the area related to themes. Having both structure
- and style in the same file introduced content duplication when
- producing art works. Because of this reason, they were
- separated into two different directory structures: the design
- models and the artistic motifs directory structures. From
- this point on, the <command>centos-art.sh</command> was able
- to produce themes as result of arbitrary combinations between
- design models (structure) and artistic motifs (visual styles).
- </para>
-
- <para>
- In the documentation area, the documents 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 and copied)
- interactively through <command>centos-art.sh</command> script.
- Additionally, the texi2html program was used to produced
- customized XHTML output in conjunction with CSS from &TCW;.
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2011.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2011.docbook
deleted file mode 100644
index 69f840d..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2011.docbook
+++ /dev/null
@@ -1,51 +0,0 @@
-<section>
-
- <title>2011's</title>
-
- <para>
- Around 2011, the <command>centos-art.sh</command> script was
- redesigned to start translating XML-based files (e.g., SVG and
- Docbook files) through <command>xml2po</command> program and
- shell scripts (e.g., Bash scripts) through GNU gettext tools.
- This configuration provided a stronger localization interface
- for graphic designers, translators and programmers. The SED
- replacement files are no longer used to handle localization.
- </para>
-
- <para>
- The <function>render</function>, <function>help</function> and
- <function>locale</function> functionalities consolidated
- themselves as the most frequent tasks performed in &TCAR;
- working copy. Additionally, the <function>prepare</function>
- and <function>tuneup</function> functionalities were also
- maintained as useful tasks.
- </para>
-
- <para>
- In the documentation area, it was introduced the
- transformation of localized DocBook XML DTD instances through
- the <function>render</function> and
- <function>locale</function> functionalities. In this
- configuration, you use <function>locale</function>
- functionality to localize DocBook source files to your
- prefered language and later, using the
- <function>render</function> functionality, you can produce the
- localized XTHML and PDF output as specified in a XSLT layer.
- Unfortunly, the transformation DocBook XML -> FO -> PDF
- (through PassiveTex) seems to be buggy inside CentOS 5.5, so
- it was commented inside the <command>centos-art.sh</command>
- script. Most documentation is now organized in DocBook format,
- even Texinfo format remains as the only format with automated
- production tasks.
- </para>
-
- <para>
- In the automation area, the <command>centos-art.sh</command>
- script introduced the capability of reading configuration
- files. The main goal here was moving some command-line options
- from functionalities onto a more persistent medium. Most
- configuration files were set to define the position of brands
- inside images and documentation manual specific options.
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2012.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2012.docbook
deleted file mode 100644
index cf81287..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2012.docbook
+++ /dev/null
@@ -1,431 +0,0 @@
-<section id="repository-history-2012">
-
- <title>2012's</title>
-
- <para>
- &TCAR; development was eventually stopped at November 2011
- until July 2012 when we needed to make the
- <command>centos-art.sh</command> script a bit more
- customizable than it presently was. For example, it was
- considered as a need that functionalities inside the
- <command>centos-art.sh</command> script must be not just
- conceived independent one another but reusable in different
- contexts as well.
- </para>
-
- <simplesect id="repository-history-2012-UpdateLocales">
- <title>Make Localization Of <command>centos-art.sh</command>
- Script Specific To Different Contexts</title>
-
- <para>
- The procedure used to locale messages inside the
- <command>centos-art.sh</command> script has to be re-designed
- in order to accept such pluggable behavior into the script. We
- couldn't publish unique <filename>centos-art.sh.po</filename>
- and <filename>centos-art.sh.mo</filename> files because they
- may contain different information in different contexts. For
- example, if you are using the <function>render</function> and
- <function>help</function> functionalities you only need
- translation messages for them and not those from other
- functionalities that may exist in the central repository but
- you didn't download nor use into your working copy.
- </para>
-
- <para>
- One solution for this could be to have independent PO files
- for each functionality of <command>centos-art.sh</command>
- script which are combined to create the final PO and MO files
- that <application>gettext</application> uses to retrive
- translated strings when <command>centos-art.sh</command>
- script is running. For this solution to be effective, you must
- be selective about the functionalities and locales directories
- you download into your working copy. For example, if you want
- to use the render functionality and its locale messages only,
- you must download the required directories and exclude others.
- </para>
-
- <note>
- <para>
- In case you don't want to be selective and download the whole
- repository, the creation of the
- <filename>centos-art.sh.po</filename>,
- <filename>centos-art.sh.pot</filename> and
- <filename>centos-art.sh.mo</filename> files will occur
- automatically the first time you run the
- <function>prepare</function> functionality (which require the
- <function>locale</function> functionality to be available), or
- later, by running the following command:
- <screen>centos-art locale Scripts/Bash --update</screen>
- </para>
-
- <para>
- For more information about the <function>prepare</function>
- and <function>locale</function> functionalities, see <xref
- linkend="scripts-bash-locale" /> and <xref
- linkend="scripts-bash-prepare" /> respectively.
- </para>
-
- </note>
-
- <para>
- As shown in <xref linkend="repository-history-2012-2" />, both
- <function>Commons</function> and <function>Locales</function>
- functionalities will always be required directories. The
- <function>Commons</function> directory contains the common
- functionalities and the <function>Locales</function> directory
- contains the standard procedures you need to run in order to
- build the final <filename>centos-art.sh.mo</filename> file
- used by <application>gettext</application> to retrive
- translation strings when the <command>centos-art.sh</command>
- script is running. Remember that
- <filename>centos-art.sh.pot</filename>,
- <filename>centos-art.sh.po</filename> files aren't under
- version control and they are built by combining each
- funtionality message.po file into a PO and later a MO file.
- </para>
-
- <example id="repository-history-2012-2">
- <title>Directory structure of a rendering-only context</title>
- <screenshot>
- <screeninfo>Directory structure of a rendering-only context</screeninfo>
- <mediaobject>
- <textobject>
-<programlisting>
-/home/centos/Projects/artwork/
-|-- Locales/
-| `-- Scripts/
-| `-- Bash/
-| `-- es_ES/
-| |-- Functions/
-| | |-- Commons/
-| | | |-- messages.po
-| | | `-- messages.pot
-| | |-- Locales/
-| | | |-- messages.po
-| | | `-- messages.pot
-| | `-- Render/
-| | |-- messages.po
-| | `-- messages.pot
-| |-- LC_MESSAGES/
-| | `-- centos-art.sh.mo
-| |-- centos-art.sh.po
-| `-- centos-art.sh.pot
-`-- Scripts/
- `-- Bash/
- |-- Functions/
- | |-- Commons/
- | |-- Locales/
- | `-- Render/
- `-- centos-art.sh
-</programlisting>
- </textobject>
- </mediaobject>
- </screenshot>
- </example>
-
- <para>
- A practical example of using the solution described above may
- be found when you are working on the corporate identity of
- &TCP; and then need to start a new corporate identity project
- for another organization. You want to keep the directory
- structure of &TCAR; and its automation tool, the
- <command>centos-art.sh</command> script. Your new project
- requires you to introduce new functionalities to
- <command>centos-art.sh</command> which don't fit the needs of
- &TCP; (e.g., you want to introduce a
- <function>report</function> functionality to mesure how much
- connect time do you consume through your PPP internface.) or
- you just want to keep the directory structure of your new
- project as simple as possible.
- </para>
-
- <para>
- To go through this it is possible to mix specific parts of
- different central repositories into one single working copy.
- This is the working copy you'll use to manage your new
- project. In <xref linkend="repository-history-2012-1" />, we
- see how the <filename class="directory">Render</filename>,
- <filename class="directory">Locales</filename> and <filename
- class="directory">Commons</filename> directories which come
- from the &TCAR; has been integrated into the working copy of
- your new project.
- </para>
-
- <example id="repository-history-2012-1">
- <title>Mixing automation functionalities.</title>
- <screenshot>
- <screeninfo>Mixing automation functionalities.</screeninfo>
- <mediaobject>
- <textobject>
-<programlisting>
-/home/al/Projects/Myapp/
-|-- Locales/
-| `-- Scripts/
-| `-- Bash/
-| `-- es_ES/
-| |-- Functions/
-| | |-- Commons/ <--| from https://projects.centos.org/svn/artwork/
-| | | |-- messages.po
-| | | `-- messages.pot
-| | |-- Locales/ <--| from https://projects.centos.org/svn/artwork/
-| | | |-- messages.po
-| | | `-- messages.pot
-| | |-- Render/ <--| from https://projects.centos.org/svn/artwork/
-| | | |-- messages.po
-| | | `-- messages.pot
-| | `-- Report/
-| | |-- messages.po
-| | `-- messages.pot
-| |-- LC_MESSAGES/
-| | `-- myapp.sh.mo
-| |-- myapp.sh.po
-| `-- myapp.sh.pot
-`-- Scripts/
- `-- Bash/
- |-- Functions/
- | |-- Commons/ <--| from https://projects.centos.org/svn/artwork/
- | |-- Locales/ <--| from https://projects.centos.org/svn/artwork/
- | |-- Render/ <--| from https://projects.centos.org/svn/artwork/
- | `-- Report/
- `-- myapp.sh
-</programlisting>
- </textobject>
- </mediaobject>
- </screenshot>
- </example>
-
- <para>
- At this point, your working copy contains files from two
- different central repositories. One repository provides the
- files of your new organization project and the other one
- provides the files related to the <function>render</function>
- functionality from &TCAR;. In this environment, all updates
- commited to the <filename class="directory">Render</filename>,
- <filename class="directory">Locales</filename> and <filename
- class="directory">Commons</filename> directories at &TCAR;
- will be available to you too, the next time you update your
- working copy. Likewise, if you change something in any of
- these directories and commit your changes, your changes will
- be available to poeple working in &TCAR; the next time they
- update their working copies.
- </para>
-
- <para>
- Understanding the need of mixing different central
- repositories into a single working copy is an important step
- for reusing the functionalities that come with centos-art.sh
- script, but it is not enough if you want to customize the
- information produced by it. By default, the centos-art.sh
- script uses information related to &TCP;. You probably need to
- change this if you are producing images to a different
- organization than &TCP;. For example, some of the information
- you might need to change would be the copyright holder,
- brands, domain names, mailing lists, and so forth. To change
- this information you need to duplicate the file
- <filename>centos-art.sh</filename> and rename it to something
- else. Later, you need to edit the renamed version and change
- variables inside according your needs. In <xref
- linkend="repository-history-2012-1" />, we used the name
- <command>myapp.sh</command> instead of
- <command>centos-art.sh</command> so the information we set
- inside it could reflect the specific needs that motivated the
- creation of a new project without affecting those from &TCP;.
- </para>
-
- <para>
- Most of the information you need to change in your duplicated
- version of <filename>centos-art.sh</filename> file is
- controlled by a set of read-only variables. You modify these
- variables here and they will be available all along the script
- execution time. For example, you can change the value of
- <varname>CLI_WRKCOPY</varname> variable inside your duplicated
- version of <filename>centos-art.sh</filename> to change the
- absolute path you use to store your working copy.
- </para>
-
- </simplesect>
-
- <simplesect>
- <title>Enhance The CentOS Logo Construction</title>
-
- <para>
- The CentOS Logo is made of two different components known as
- The CentOS Symbol and The CentOS Type. Presently (at the end
- of September), to produce these components, we create one
- <acronym>SVG</acronym> image for each PNG image we want to
- produce, store it in <filename
- class="directory">Identity/Models/Brands/Logos</filename>
- directory structure and run the command:
- </para>
-
- <cmdsynopsis>
- <command>centos-art render Identity/Images/Brands/Logos</command>
- </cmdsynopsis>
-
- <para>
- This model works and scales well in situations when there
- isn't a need to reuse final images among themselves. However,
- when you need to reuse images among themselves, a better
- solution is required. The goal here would be: don't create
- <acronym>SVG</acronym> images for PNG images you can build
- based on other PNG images.
- </para>
-
- <para>
- This might be achieved through one of the following ways:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- Create a new specific functionality to achieved the goal.
- Needed because the <xref linkend="scripts-bash-render" />
- specific functionality uses <acronym>SVG</acronym> files as
- reference to build images (i.e., one <acronym>SVG</acronym>
- image produces one PNG image).
- </para>
- </listitem>
-
- <listitem>
- <para>
- Modify <xref linkend="scripts-bash-render" /> functionality to
- work in different modes based on file type or file extension.
- The first mode would use <acronym>SVG</acronym> files as
- reference to build PNG images (just as it was doing so far).
- The second mode would use a configuration file named
- <filename>render.conf</filename> as reference inside the
- design models directory you want to produce images for so as
- to build the related PNG images. In this second case, the
- configuration file specifies how final PNG images will be
- produced (e.g., by appending or overlapping them one another).
- </para>
- </listitem>
- </itemizedlist>
-
- <para>
- For example, consider the following command-line:
- </para>
-
- <cmdsynopsis>
- <command>centos-art render Identity/Images/Brands/Logos</command>
- </cmdsynopsis>
-
- <para>
- This command should evaluate which type of rendition will be
- done, based on whether the source file is a scalable vector
- graphic (<acronym>SVG</acronym>) or a configuration file. To
- make this decision, the <command>centos-art.sh</command>
- script looks for <acronym>SVG</acronym> files first, and
- configuration files later. When <acronym>SVG</acronym> files
- are found, the <command>centos-art.sh</command> script uses a
- list of <acronym>SVG</acronym> files and process them one by
- one excluding any related configuration file that could exist.
- On the other hand, if no <acronym>SVG</acronym> file is found
- inside the related design model directory structure, the
- <command>centos-art.sh</command> script will use the
- configuration file with the name
- <filename>render.conf</filename> to create images as specified
- inside it. When neither a <acronym>SVG</acronym> or a
- configuration file is found inside the design model directory
- structure, the <command>centos-art.sh</command> script
- finishes its execution without any error message. For
- example, if no <acronym>SVG</acronym> file is found inside
- <filename
- class="directory">Identity/Models/Brands/Logos/</filename>
- directory and the
- <filename>Identity/Models/Brands/Logos/images.conf</filename>
- configuration file exists therein with the following content:
- </para>
-
-<programlisting>
-[centos.png]
-models = "Identity/Models/Brands/Symbols/centos-symbol-forlogos.svgz Identity/Models/Brands/Types/centos.svgz"
-formats = "xpm jpg"
-heights = "48 78"
-fgcolor = "000000 ffffff"
-bgcolor = "ffffff-0"
-command = "/usr/bin/convert +append"
-
-[centos-artwork.png]
-models = "Identity/Models/Brands/Symbols/centos-symbol-forlogos.svgz Identity/Models/Brands/Types/centos.svgz Identity/Models/Brands/Types/artwork.svgz"
-formats = "xpm jpg"
-heights = "48 78"
-fgcolor = "000000 ffffff"
-bgcolor = "ffffff-0"
-command = "/usr/bin/convert +append"
-</programlisting>
-
- <para>
- The <command>centos-art.sh</command> script should produce the
- following image files:
- </para>
-
-<programlisting>
-Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.jpg
-Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.png
-Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.xpm
-Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.png
-Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.jpg
-Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.xmp
-Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.jpg
-Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.png
-Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.xpm
-Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.png
-Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.jpg
-Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.xmp
-Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.jpg
-Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.png
-Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.xpm
-Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.png
-Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.jpg
-Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.xmp
-Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.jpg
-Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.png
-Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.xpm
-Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.png
-Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.jpg
-Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.xmp
-</programlisting>
-
- <para>
- The final location for storing images output inside the
- repository is determined by using the design model directory
- provided as argument. Basically, the
- <command>centos-art.sh</command> script changes the path
- components from Models to Images and adds foreground color,
- background color, height value and image name to it to
- differentiate rendered images.
- </para>
-
- <para>
- In case you need to restrict the amount of files you want to
- produce including their formats, heights, colors and commands,
- you need to modify the content of the related
- <filename>render.conf</filename> configuration file. There is
- not any command-line option available for such tasks. The most
- <xref linkend="scripts-bash-render" xreflabel="render"/>
- command-line options can do for you is when there are more
- than one configuration file inside the same design model
- directory and you need to specify which one of them will be
- used as reference. In such case you can use the
- <option>--filter="REGEX"</option> option.
- </para>
-
- <para>
- When images are produced through configuration files, the
- <command>centos-art.sh</command> script takes the order
- provided in the list of design models to build the list of
- images you will work with through the command specified. For
- example, the order in which images will be appended or
- overlapped.
- </para>
-
- <para>
- Localization of logo images will not be and must not be
- supported in any way. That would bring disastrous confusion in
- the area of visual recognition.
- </para>
-
- </simplesect>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2013.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2013.docbook
deleted file mode 100644
index 290647a..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/History/2013.docbook
+++ /dev/null
@@ -1,141 +0,0 @@
-<section id="repository-history-2013">
-
- <title>2013's</title>
-
- <para>
- &TCAR; development was eventually stopped at November, 2012,
- when I moved myself from Cienfuegos to Havana city for working
- The first months were very difficult, specially at the moment
- of finding a stable place to set my personal desktop (I was
- moving myself from one apartment to another, frequently).
- </para>
-
- <para>
- On May 14th, the work in Havana ends for me and I have to
- return to Cienfuegos city. I tried to take advantage of the
- situation dedicating more work and study hours to &TCAR; and
- the related automation scripts once again. At this point I
- consider a Git+Gitolite+Gitweb+MantisBT infrastructure for
- &TCAR; and start working on it in my workstation. This, in
- order to implement a distributed work flow for &TCAR; based on
- Git version control system.
- </para>
-
- <simplesect id="repository-history-2013-VersionControl">
- <title>Update Version Control Environment</title>
- <para>
- The function environment related to version control tasks was
- renamed from <function>svn</function> to <xref
- linkend="scripts-bash-vcs" /> in order to handle both
- <application>Subversion</application> and
- <application>Git</application> working copies of &TCAR;. This
- change prepares the <command>centos-art.sh</command> script to
- follow the suggestion of a complete migration from
- <application>Subversion</application> to
- <application>Git</application>, at some point.
- </para>
-
- <para>
- Because the <application>Subversion</application>
- infrastructure is the one in place right now and it is the one
- with most artwork history, it will be
- <application>Subversion</application> the version control
- system we are using as default in
- <filename>centos-art.sh</filename>. However this will surely
- change as soon as a <application>Git</application>
- infrastructure be approved for &TCAR; and everything could be
- moved there.
- </para>
- </simplesect>
-
- <simplesect id="repository-history-2013-ConfigurationFile">
- <title>Start Using The <filename>centos-art.conf</filename> File</title>
- <para>
- Based on the need of supporting more than one application to
- handle version control tasks, it was added the
- <filename>centos-art.conf</filename> file into the <filename
- class="directory">Scripts/Bash</filename> directory. This file
- exists to customize specific behaviours of
- <command>centos-art.sh</command> script once it has been
- executed (e.g., what kind of application will be used as
- default for doing version control, or even if the actions
- related to version control will be performed or not).
- </para>
- </simplesect>
-
-
- <simplesect id="repository-history-2013-UpdateRepositoryLayout">
- <title>Update Repository Directories Structure</title>
- <para>
- I face the following situation: I am working on a
- documentation project named <quote>solinfo-network</quote>.
- While I was organizing it, I found that the directory
- structure of &TCAR; fits quite well the needs of
- <quote>solinfo-network</quote> documentation project. However,
- I don't want to duplicate automation scripts in two separate
- projects, but share them between themselves (i.e., changes
- committed to automation scripts are pushed to one single
- place, not two.).
- </para>
- <para>
- When we use Subversion repositories, it is possible to
- checkout specific parts of different repositories into a new
- repository. This is very useful if we need to create several
- projects that share the same component and we don't want to
- duplicate the common component in two or more different
- projects but <quote>share</quote> it between them. See
- <xref linkend="repository-history-2012-UpdateLocales" />.
- </para>
-
- <para>
- When we use Git repository, it is not possible to checkout
- specific parts of a repository but the complete tree. So, in
- order to share common components of a repository we need to
- create one repository for each common component we want to
- share and then use Git submodules<citation>see progit-book,
- page 152.</citation> This requires that brand new
- repositories be created for each component we want to share.
- </para>
-
- <para>
- In both situations, including Git and Subversion repositories,
- it is necessary that we define very well the structure of each
- component we want to share, so it can be
- <quote>plugged</quote> nicely into other projects. Likewise,
- other projects must have the same directory structure the
- pluggable component was design to fit in. If these two
- conditions can be reached, it would be possible to reuse
- repositories components and concentrate efforts. The current
- directory structure &TCAR; is set in allows components inside
- Subversion repositories to be reused by related working
- copies. However, we cannot do the same if it is stored in a
- Git repository. In order for Git repositories to be able to
- share components with other Git repositories, &TCAR; directory
- structure needs to be reorganized to better delineate each
- component the repository is made of.
- </para>
-
- <para>
- For more information see <xref linkend="repo-convs" />.
- </para>
-
- </simplesect>
-
- <!--
-
- <simplesect id="repository-history-2013-UpdateDocbookStructure">
- <title>Update DocBook Physical Divisions</title>
- <para>
- The main purpose of this update is changing the main physical
- division of DocBook documents from entities to XInclude. This
- change affects both <xref linkend="scripts-bash-render"/> and
- <xref linkend="scripts-bash-locale" /> functionalities.
- </para>
-
- <para>
- ...
- </para>
- </simplesect>
- -->
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Workstation.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Workstation.docbook
deleted file mode 100644
index cf55d5e..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Workstation.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<chapter id="repo-ws">
-
- <title>Preparing Your Workstation</title>
-
- &repo-ws-intro;
- &repo-ws-install;
- &repo-ws-config;
-
-</chapter>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Workstation/config.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Workstation/config.docbook
deleted file mode 100644
index 8ad40d0..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Workstation/config.docbook
+++ /dev/null
@@ -1,351 +0,0 @@
-<section id="repo-ws-config">
-
- <title>Configuring Your Workstation</title>
-
- <para>
- Once your workstation has been installed, it is time for you
- to configure it. The configuration of your workstation
- consists on defining your workplace, download a working copy
- from &TCAR; and finally, run the <function>prepare</function>
- functionality of <command>centos-art.sh</command> script to
- install/update the software needed, render images, create
- links, and anything else needed.
- </para>
-
- <section id="repo-ws-config-wp">
- <title>Define Your Workplace</title>
- <para>
- Once you've installed the workstation and it is up and
- running, you need to register the user name you'll use for
- working. In this task you need to use the commands
- <command>useradd</command> and <command>passwd</command> to
- create the user name and set a password for it, respectively.
- These commands require administrative privileges to be
- executed, so you need to login as <quote>root</quote>
- superuser for doing so.
- </para>
-
- <caution>
- <para>
- Do not use the <quote>root</quote> username for regular
- tasks inside your working copy of &TCAR;. This is dangerous
- and might provoke unreversable damages to your workstation.
- </para>
- </caution>
-
- <para>
- When you've registered your user name in the workstation, it
- provides an identifier for you to open a user's session in the
- workstation and a place to store the information you produce,
- as well. This place is known as your home directory and is
- unique for each user registered in the workstation. For
- example, if you register the user name john in your
- workstation, your home directory would be located at <filename
- class="directory">/home/john/</filename>.
- </para>
-
- <para>
- At this point it is important to define where to download the
- working copy of &TCAR; inside your home directory. This
- desition deserves special attention and should be implemented
- carefully in order to grant a standard environment that could
- be distributed. Let's see some alternatives.
- </para>
-
- <section>
- <title>Different absolute paths</title>
- <para>
- Consider that you store your working copy under <filename
- class="directory">/home/john/Projects/artwork/</filename> and
- I store mine under <filename
- class="directory">/home/al/Projects/artwork/</filename>, we'll
- end up refering the same files inside our working copies
- through different absolute paths. This alternative generates
- a contradiction when files which hold path information inside
- are committed up to the central repository from different
- working copies. The contradiction comes from the question:
- which is the correct absolute path to use inside such files,
- yours or mine? (None of them is, of course.)
- </para>
-
- </section>
-
- <section id="repo-ws-config-wp-OneUniqueAbsolutePath">
- <title>One unique absolute path</title>
- <para>
- Another case would be that where you and I ourselves use one
- unique home directory (e.g., <filename
- class="directory">/home/centos/Projects/artwork/</filename>)
- to store the working copy of &TCAR; in our own workstations,
- but configure the subversion client to use different user
- names to commit changes up from the working copy to the
- central repository. This alternative might be not so good in
- situations where you and I have to share the same workstation.
- In such cases, it would be required that we both share the
- password information of the same system user (the
- <quote>centos</quote> user in our example) which, in
- addition, gives access to that user's subversion client
- configuration and this way provokes the whole sense of using
- different subversion credentials for committing changes to be
- lost.
- </para>
- </section>
-
- <section>
- <title>Different absolute paths through dynamic expansion</title>
- <para>
- Most of the absolute paths we use inside the working copy are
- made of two parts, one dynamic and one relative fixed. The
- dynamic part is the home directory of the current user and its
- value can be retrived from the <envar>$HOME</envar>
- environment variable. The fixed part of the path is the one
- we set inside the repositroy structure itself as a matter of
- organization. What we need here is to find a way to expand
- variables inside files that don't support variable expansion.
- This alternative had worked rather fine when we produce
- produce PNG files from SVG files and XTHML from DocBook files,
- but the same is not true for absolute paths inside files that
- are used as in their permanent state inside the repository
- (e.g., CSS files and other files similar in purpose).
- </para>
- </section>
-
- <section>
- <title>Different absolute paths, dynamic expansion, symbolic
- links, relative links, and environment variables</title>
-
- <para>
- With this solution it is possible to store working copies of
- &TCAR; on different locations inside the same workstation
- without lose relation between files. Here we use the
- TCAR_WORKDIR environment variable to set the location of the
- working copy inside the workstation. Later the centos-art.sh
- scripts uses this value as reference to determine where the
- working copy is. This value is also the one used for dynamic
- expansion inside design models and other similar files. In the
- case of web projects where different components are required
- to produce the final content, we create symbolic links between
- them and use relative paths so it is possible to reuse them
- and retain the relation between them in different contexts.
- </para>
-
- <para>
- For example, lets consider the organization of XHTML manuals
- rendered from DocBook source files. When you render a DocBook
- manual inside &TCAR; it creates XHTML files. This XHTML files
- use images and common style sheets for better presentation.
- Both of these images and styles components live outside the
- XHTML structure so, in order to make them available
- relatively to the XHTML structure, we created symbolic links
- from the XHTML structure to the outside location where they
- are in. The creation of symbolic links takes place
- automatically when each DockBook manual is rendered through
- <command>centos-art.sh</command>, which uses the value of
- TCAR_WORKDIR environment variable as reference to determine
- the absolute path of the working copy.
- </para>
-
- <para>
- Bacause absolute paths are no longer stored inside permanent
- files and <command>centos-art.sh</command> script uses the
- TCAR_WORKDIR environment variable to determine where the
- working copy is stored in the workstation, it should be safe
- to download working copies of &TCAR; anywhere in the
- workstation. One just have to be sure that the value of
- TCAR_WORKDIR environment variable does match the location of
- the working copy you are using.
- </para>
-
- </section>
-
- </section>
-
- <section id="repo-ws-config-wc">
- <title>Download Your Working Copy</title>
-
- <para>
- In order to use &TCAR; you need to download a working copy
- from the central repository into your workstation. To
- download such working copy use the following command:
- </para>
-
- <screen>git clone https://projects.centos.org/~al/artwork.git</screen>
-
- <para>
- This command will create your working copy inside your home
- directory, specifically in a directory named <filename
- class="directory">artwork.git</filename>. Inside this directory
- you will find all the files you need to work with inside
- &TCAR;. If you want to have your working copy in a location
- different to that one shown above, see <xref
- linkend="repo-ws-config-ChangeWorkingCopy" />.
- </para>
-
- <para>
- The first time you download the working copy it contains no
- image files, nor documentation, or localized content inside
- it. This is because all the files provided in the working copy
- are source files (e.g., the files needed to produce other
- files) and it is up to you to render them in order to produce
- the final files (e.g., images and documentation) used to
- implement &TCPCVI;.
- </para>
-
- </section>
-
- <section id="repo-ws-config-sudoers">
- <title>Configure Administrative Tasks</title>
-
- <para>
- Most of the administrative tasks you need to perform in your
- working copy of &TCAR; are standardized inside the
- <function>prepare</function> functionality of
- <command>centos-art.sh</command> script. Inside
- <command>centos-art.sh</command>
- script, all administrative task are invoked through the
- <command>sudo</command> command. Thus, in order for the
- <command>centos-art.sh</command> script to perform
- administrative tasks, you need to update the
- <command>sudo</command>'s configuration in a way that such
- administrative actions be allowed.
- </para>
-
- <para>
- At time of this writing the <command>centos-art.sh</command>
- script implements just one administrative task, that is
- package management. Nevertheless, in the future, other
- administrative tasks might be included as well (e.g.,
- installing themes locally from the working copy for testing
- purposes.).
- </para>
-
- <para>
- To update the <command>sudo</command>'s configuration, execute
- the <command>visudo</command> command as <quote>root</quote>.
- Later, uncoment the <varname>Cmnd_Alias</varname> related to
- <quote>SOFTWARE</quote> and add a line for your username
- allowing software commands. This configuration is illustrated
- in <xref linkend="repo-ws-config-sudoers-example" />.
- </para>
-
- <example id="repo-ws-config-sudoers-example">
- <title>The <filename>/etc/sudoers</filename> configuration file</title>
- <screenshot>
- <screeninfo><filename>/etc/sudoers</filename> configuration file</screeninfo>
- <mediaobject>
- <textobject>
-<programlisting>
-## Installation and management of software
-Cmnd_Alias SOFTWARE = /bin/rpm, /usr/bin/up2date, /usr/bin/yum
-
-## Next comes the main part: which users can run what software on
-## which machines (the sudoers file can be shared between multiple
-## systems).
-## Syntax:
-##
-## user MACHINE=COMMANDS
-##
-## The COMMANDS section may have other options added to it.
-##
-## Allow root to run any commands anywhere
-root ALL=(ALL) ALL
-
-## Allow the centos user to run installation and management of
-## software anywhere.
-al ALL=(ALL) SOFTWARE
-</programlisting>
- </textobject>
- </mediaobject>
- </screenshot>
- </example>
-
- </section>
-
- <section id="repo-ws-config-runout">
- <title>Run Preparation Tool</title>
- <para>
- Once you've both downloaded a working copy from &TCAR;
- and configured the <command>sudo</command>'s configuration
- file successfully, run the <function>prepare</function>
- functionality of <command>centos-art.sh</command> script to
- complete the configuration process using the following
- command:
- </para>
-
- <screen>~/artwork/Scripts/Bash/centos-art.sh prepare</screen>
-
- <para>
- To know more about the <function>prepare</function>
- functionality of <command>centos-art.sh</command> script, see
- <xref linkend="scripts-bash-prepare" />.
- </para>
- </section>
-
- <section id="repo-ws-config-ChangeWorkingCopy">
- <title>Changing Your Working Copy Default Path</title>
- <para>
- By default your working copy should be store in your home
- directory, specifically in the location <filename
- class="directory">~/artwork</filename>. This location may not
- be the final location where you want to have your working copy
- in situations where you are working on several projects at the
- same time or you already have a define location to organize
- your projects inside your home directory. Thus, you may need
- to change the default location of your working copy to a more
- appropriate location.
- </para>
-
- <para>
- The default path to your working copy is controlled by the
- <envar>TCAR_WORKDIR</envar> environment variable. This
- variable is firstly defined in your personal profile after
- running the prepare functionality of
- <command>centos-art.sh</command> script. So, to change the
- path of your working copy correctly, do the following:
- </para>
-
- <orderedlist>
- <listitem>
- <para>
- Create the parent directory you will use to store your working
- copy. For example:
- <screen>mkdir -p ~/Projects/CentOS</screen>
- </para>
- </listitem>
- <listitem>
- <para>
- Move the currently downloaded working copy from ~/artwork to
- your new location. For example:
- <screen>mv ~/artwork ~/Projects/CentOS/</screen>
- </para>
- </listitem>
- <listitem>
- <para>
- Update the environment variables set in
- <filename>~/.bash_profile</filename> by running the
- <command>centos-art.sh</command> script from the new location.
- For example:
- <screen>~/Projects/CentOS/artwork/Scripts/Bash/centos-art.sh prepare --set-environment</screen>
- </para>
- </listitem>
- <listitem>
- <para>
- Do log out from your active user's seesion and do log in again
- so the environment changes take effect. Or just update the
- current environment information by running the following
- command:
- <screen>. ~/.bash_profile</screen>
- </para>
- </listitem>
- <listitem>
- <para>
- Update internal links by running the
- <command>centos-art.sh</command> script. For example:
- <screen>${TCAR_WORKDIR}/Scripts/Bash/centos-art.sh prepare --links</screen>
- </para>
- </listitem>
- </orderedlist>
-
- </section>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Workstation/install.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Workstation/install.docbook
deleted file mode 100644
index 46d30a9..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Workstation/install.docbook
+++ /dev/null
@@ -1,41 +0,0 @@
-<section id="repo-ws-install">
-
- <title>Installing Your Workstation</title>
-
- <para>
- To install your workstation use &TCD; default configuration as
- proposed by &TCD; installer. This includes default
- partitioning and packages. &TCAR; is been completly develop
- upon &TCD; and realies on such environment to achieve most
- automation tasks. In order to get a reproducable environment,
- it is convenient that you, too, use the same operating system
- that we do.
- </para>
-
- <section id="repo-ws-install-support">
- <title>Supported Platforms</title>
-
- <para>
- &TCAR; has been tested in the following platforms:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- The CentOS Distribution major release 5 update 5, for i386 and
- i686 architectures.
- </para>
- </listitem>
- </itemizedlist>
-
- <para>
- In case you be using a working copy of &TCAR; in a different
- platform from those listed here, please send a mail to <ulink
- url="mailto:centos-devel@centos.org">centos-devel@centos.org</ulink>
- notifying it. It is our intention to make &TCAR; as portable
- as possible through different major releases of &TCD;.
- </para>
-
- </section>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/Workstation/intro.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/Workstation/intro.docbook
deleted file mode 100644
index d6677cc..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/Workstation/intro.docbook
+++ /dev/null
@@ -1,27 +0,0 @@
-<section id="repo-ws-intro">
-
- <title>Introduction</title>
-
- <para>
- The workstation is the machine you use to store your working
- copy of &TCAR;. The working copy is an ordinary directory
- tree on your workstation, containing a collection of files
- that you can edit however you wish. The working copy is your
- own private work area related to &TCAR; where you perform
- changes and receive changes from others.
- </para>
-
- <para>
- In order to make your workstation completely functional, it is
- necessary that you install it and configure it to satisfy the
- needs demanded by the working copy of &TCAR; you later
- download in it.
- </para>
-
- <para>
- This chapter describes the steps you need to follow in order
- to install and configure a workstation for using a working
- copy of &TCAR; in all its extention.
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Repository/introduction.docbook b/Artworks/Docs/Docbook/Tcar-ug/Repository/introduction.docbook
deleted file mode 100644
index a059dc5..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Repository/introduction.docbook
+++ /dev/null
@@ -1,120 +0,0 @@
-<section id="preface-overview">
-
- <title>Overview</title>
-
- <para>
- The corporations always have a corporate identity, even when
- they don't take an intentional control over it. It is a choise
- from the corporation to define how much control to take over
- its identity. This kind of control is expensive and not all
- corporations are able to maintain it. However, it is
- necessary that, based on pragmatic facts, the corporation
- assume an acceptable degree of compromise with its identity in
- order to create a consistent idea of itself in a way that can
- be progresively improved through time.
- </para>
-
- <para>
- During the years (2003-2009), we've seen a growing interest
- inside &TCC; for helping on &TCP; development. Some people
- seem to be very clear about what the project needs are and how
- to maintain it being a very stable project, but others however
- don't to get what &TCP; is (even it is explained time after
- time) and sometimes decide to put their efforts in the wrong
- direction making everything to be a waste of time and source
- of distraction from what is really needed.
- </para>
-
- <para>
- &TCAR; phases the question <quote>What can I do for
- &TCP;?</quote> by identifying different work lines you can
- join in and providing automated production mechanisms that
- complement one another according to each work line needs so
- consistent results can be achieved inside a distributed
- environment under version control. For example, consider an
- environment where there are graphic designers to produce
- images, documentors to produce documentation manuals (whose
- can use images produced by graphic designers), programmers to
- produce automation scripts (needed to standardize production
- tasks) and translators to localize source files created by
- graphic designers, documetors and programmers. Once such
- environment has been implemented, it would be possible for
- packagers to take localized images and localized documentation
- from &TCAR; (through an automation script probably) to
- rebrand/update the content of those packages inside &TCD; that
- must include information specific to &TCP; itself (e.g., boot
- loader, distribution installer, release notes, display
- managers, release notes, web browsers default page, etc.).
- </para>
-
- <para>
- Most production tasks inside &TCAR; are focused on the files
- needed to implement &TCP; corporate visual identity.<footnote>
- <para>
- Notice that, here, visual identity means everything
- perceived through the human's visual sences (i.e., the
- human eyes), but the corporate identity is a wider concept
- that extends to all human senses (i.e., visibilty (eyes),
- audition (ears), scent (nose), touch (fingers), and savour
- (tongue)), not just that one related to visual aspects.
- Nevertheless, we need to be consequent with the media
- where &TCP; manifests its existence on, as described in
- <xref linkend="identity" />.
- </para></footnote> This includes everything from file edition
- (e.g., text width, text indentation, line numbering, text
- tabulation, etc.) up to how the web sites, distribution, and
- industrial stuff (e.g., pullovers, caps, installation media,
- etc.) look and feel. Notice that, more specific details like
- typography, window design, icons, menu items, etc., inside
- &TCD; are already covered by &TCP; upstream provider. In our
- effort to be 100% binary compatible with the upstream provider
- and also keeping maintainance low, we stand over those
- specific details as much as possible assuming them as default.
- However, if you feel brave enough (and prove your ability to
- keep yourself being that way) it would be possible to open a
- work line for you to maintain variants of such very specific
- details inside &TCAR;.
- </para>
-
- <para>
- In addition to visual manifestations, there are also emotional
- feelings and ethical behaviours that must be considered as
- part of &TCP; corporate identity. A pleasant experience in
- this area includes &TCWIKI;, specifically the way it was
- conceived and administered. When the &TCWIKI; was published,
- &TCP; published a list of needs with it so anyone could
- contribute based on them. Not much time after that, the list
- of tasks triggered some souls' motivations ruled by the good
- will of initiating the translation of that content published
- inside the wiki, redesigning its visual style, proposing the
- TreeFlower theme for &TCD;, and reducing to zero the
- contraditions of precoceived minds with respect, reason and
- passion. As result of this experience, we found that &TCC;
- posseses an incredible strong creative force, however, a long
- path must be traveled before it can be focalized into the
- right direction because: it isn't enough just telling what the
- right direction is, it is also necessary to provide the
- vehicles for &TCC; be able of moving through it.
- </para>
-
- <para>
- &TCAR; extends the feelings and ethicals behaviours from
- &TCWIKI; to itself by identifying the visual manifestations
- &TCP; is made of (i.e., tracing a direction) and allowing
- people to develop them through standardized procedures inside
- a colaborative environment (i.e., providing the vehicles).
- </para>
-
- <para>
- Finally, if you find yourself needing to do something for
- &TCP; and &TCAR; isn't the place for it, be sure to define
- what that something exactly is and also make it a community
- effort so it can be validated as something useful to the
- community itself. Otherwise, the effort would loose its
- initial sense soon enough so as to be considered seriously.
- Notice that the way these needs are described may take
- different forms: they can be written and organized inside a
- book, an article, or even a well documented program ;-).
- </para>
-
-</section>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts.docbook
deleted file mode 100644
index 088ba46..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts.docbook
+++ /dev/null
@@ -1,24 +0,0 @@
-<part id="scripts">
-
- <title>Automation</title>
-
- <partintro>
- <para>
- This part of the book describes &TCAR; automation work
- line. Through this work line programmers provide the
- production standards that graphic designers,
- documentalists, translators and packagers need to make
- their work consistent and reusable. For this purpose,
- programmers develop the <command>centos-art.sh</command>
- script and its functionalities. The main purpose of this
- work line is standardize the interaction of work lines in
- a reliable way. The automation work line takes place in
- the <ulink
- url="https://projects.centos.org/~al/artwork.git/Scripts">Scripts</ulink>
- directory.
- </para>
- </partintro>
-
- &scripts-bash;
-
-</part>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts.ent b/Artworks/Docs/Docbook/Tcar-ug/Scripts.ent
deleted file mode 100644
index 3a8db4c..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts.ent
+++ /dev/null
@@ -1,16 +0,0 @@
-<!ENTITY scripts SYSTEM "Scripts.docbook">
-<!ENTITY scripts-bash SYSTEM "Scripts/Bash.docbook">
-<!ENTITY scripts-bash-intro SYSTEM "Scripts/Bash/intro.docbook">
-<!ENTITY scripts-bash-mission SYSTEM "Scripts/Bash/mission.docbook">
-<!ENTITY scripts-bash-nameconvs SYSTEM "Scripts/Bash/nameconvs.docbook">
-<!ENTITY scripts-bash-environment SYSTEM "Scripts/Bash/environment.docbook">
-<!ENTITY scripts-bash-cliref SYSTEM "Scripts/Bash/cliref.docbook">
-<!ENTITY scripts-bash-render SYSTEM "Scripts/Bash/render.docbook">
-<!ENTITY scripts-bash-locale SYSTEM "Scripts/Bash/locale.docbook">
-<!ENTITY scripts-bash-help SYSTEM "Scripts/Bash/help.docbook">
-<!ENTITY scripts-bash-prepare SYSTEM "Scripts/Bash/prepare.docbook">
-<!ENTITY scripts-bash-pack SYSTEM "Scripts/Bash/pack.docbook">
-<!ENTITY scripts-bash-tuneup SYSTEM "Scripts/Bash/tuneup.docbook">
-<!ENTITY scripts-bash-vcs SYSTEM "Scripts/Bash/vcs.docbook">
-
-<!ENTITY scripts-bash-cli_checkFiles SYSTEM "Scripts/Bash/cli_checkFiles.docbook">
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash.docbook
deleted file mode 100644
index 33a1e2f..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash.docbook
+++ /dev/null
@@ -1,23 +0,0 @@
-<reference id="scripts-bash">
-
- <title>The <command>centos-art.sh</command> Reference</title>
- <subtitle>Version 0.4</subtitle>
-
- <partintro>
- &scripts-bash-intro;
- &scripts-bash-mission;
- &scripts-bash-nameconvs;
- &scripts-bash-cliref;
- &scripts-bash-environment;
- </partintro>
-
- &scripts-bash-prepare;
- &scripts-bash-help;
- &scripts-bash-render;
- &scripts-bash-locale;
- &scripts-bash-pack;
- &scripts-bash-tuneup;
- &scripts-bash-vcs;
- &scripts-bash-cli_checkFiles;
-
-</reference>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/cli_checkFiles.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/cli_checkFiles.docbook
deleted file mode 100644
index 74f40a4..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/cli_checkFiles.docbook
+++ /dev/null
@@ -1,245 +0,0 @@
-<refentry id="scripts-bash-cli_checkFiles">
-
- <refmeta>
- <refentrytitle>cli_checkFiles</refentrytitle>
- <manvolnum>1</manvolnum>
- <indexterm type="common-function">
- <primary>Standardize constructions for file verifications</primary>
- </indexterm>
- </refmeta>
-
- <refnamediv>
- <refname>cli_checkFiles</refname>
- <refpurpose>Standardize constructions for file verifications.</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
- <cmdsynopsis>
- <command>cli_checkFiles</command>
- <arg choice="req">
- <arg>-d</arg>
- <arg>-e</arg>
- <arg>-f</arg>
- <arg>-h</arg>
- <arg>-x</arg>
- </arg>
- <arg choice="req" rep="repeat"><replaceable>LOCATION</replaceable></arg>
- </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsection id="scripts-bash-cli_checkFiles-description">
- <title>Description</title>
- <para>
- The <function>cli_checkFiles</function> exists to answer basic
- questions like <quote>Is <replaceable>LOCATION</replaceable>
- is a regular file?</quote> and <quote>Is
- <replaceable>LOCATION</replaceable> a directory?</quote>. The
- answer to such questions affects the script execution flow in
- the following way: when the answer positive (e.g.,
- <replaceable>LOCATION</replaceable> is a regular file), the
- script passes the test silently and continues its execution.
- When the answer is negative(e.g.,
- <replaceable>LOCATION</replaceable> is not a regular file),
- the script finishes its execution immediately with an error
- message.
- </para>
-
- <para>
- The <function>cli_checkFiles</function> function is exported
- to <command>centos-art.sh</command> script environment in the
- very beginning of its execution and will be available all
- along its execution lifetime. You can use this function inside
- common and specific functions whenever you need to verify
- files inside the &TCAR;.
- </para>
-
- <para>
- The <function>cli_checkFiles</function> function is available
- inside the <command>centos-art.sh</command> script only as
- part of its execution environment. This function is exported
- to <command>centos-art.sh</command> script just after
- executing the script from the command-line and will be
- available all along the script lifetime. So, you can use this
- function both in common and specific functionalities of
- centos-art.sh script.
- </para>
-
- <para>
- The <function>cli_checkFiles</function> function doesn't
- create subsequent execution environments.
- </para>
- </refsection>
-
- <refsection id="scripts-bash-cli_checkFiles-usage">
- <title>Usage</title>
- <para>
- Use the <function>cli_checkFiles</function> function inside
- <command>centos-art.sh</command> script whenever you need to
- control the script execution flow based on file type (e.g.,
- regular files, directories, links, etc.) verifications.
- </para>
- </refsection>
-
- <refsection id="scripts-bash-cli_checkFiles-options">
- <title>Options</title>
- <para>
- The <function>cli_checkFiles</function> function accepts the
- following options:
- </para>
- <variablelist>
- <varlistentry>
- <term><option>-d</option></term>
- <listitem>
- <para>
- Verifies whether <replaceable>LOCATION</replaceable> exists
- and is a directory. If it doesn't exists or isn't a directory,
- an error message is printed and the script finishes its
- execution. Otherwise, if it exists and is a directory, the
- script continues its execution normally.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>-e</option></term>
- <listitem>
- <para>
- Verifies whether <replaceable>LOCATION</replaceable> exists or
- not. If it doesn't exist, an error message is printed and the
- script finishes its execution. Otherwise, if it does exists,
- the script continues its execution normally.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>-f</option></term>
- <listitem>
- <para>
- Verifies whether <replaceable>LOCATION</replaceable> exists
- and is a regular file. If it doesn't exists or isn't a regular
- file, an error message is printed and the script finishes its
- execution. Otherwise, if it exists and is a regular file, the
- script continues its execution normally.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>-h</option></term>
- <listitem>
- <para>
- Verifies whether <replaceable>LOCATION</replaceable> exists
- and is a symbolic link. If it doesn't exists or isn't a
- symbolic link, an error message is printed and the script
- finishes its execution immediately. Otherwise, if it does
- exist and is a symbolic link, the script continue its
- execution normally.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>-x</option></term>
- <listitem>
- <para>
- Verifies whether <replaceable>LOCATION</replaceable> exists
- and execution permission is granted. If it doesn't exist or
- hasn't execution permission, the script finishes its execution
- immediately. Otherwise, if it exists and has execution
- permissions, the script continues its execution normally.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- The value of the <replaceable>LOCATION</replaceable> argument
- must be an absolute path to the file you want to verify. If
- such file doesn't exists in any supported form, the script
- finishes its execution with an error message.
- </para>
- </refsection>
-
- <refsection id="scripts-bash-cli_checkFiles-example">
- <title>Examples</title>
- <para>
- The following example was taken from
- <command>centos-art.sh</command> script initialization phase.
- Notice the position of <function>cli_checkFiles</function>
- function inside the loop. If some of the function files we
- need to export doesn't have execution rights,
- <function>cli_checkFiles</function> will
- finish the script execution immediately with an error message.
- </para>
-<programlisting language="bash">
-# Process the list of files.
-for FUNCFILE in $FUNCFILES;do
-
- # Verify the execution rights for function file.
- cli_checkFiles -x ${FUNCFILE}
-
- # Initialize the function file.
- . ${FUNCFILE}
-
- # Export the function names inside the file to current shell
- # script environment.
- export -f $(egrep "${PATTERN}" ${FUNCFILE} | gawk '{ print $2 }')
-
-done
-</programlisting>
- </refsection>
-
- <refsection>
- <title>Bugs</title>
- <para>
- To report bugs related to this function, please create a new
- ticket at <ulink
- url="https://projects.centos.org/trac/artwork" /> refering the
- name of this function clearly and the specific problems you
- found in it.
- </para>
- </refsection>
-
- <refsection id="scripts-bash-cli_checkFiles-authors">
- <title>Authors</title>
- <itemizedlist>
- <listitem>
- <para>
- Alain Reguera Delgado <email>alain.reguera@gmail.com</email>, =COPYRIGHT_YEAR_LIST=
- </para>
- </listitem>
- </itemizedlist>
- </refsection>
-
- <refsection id="scripts-bash-cli_checkFiles-licence">
- <title>License</title>
-
- <para>
- Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
- </refsection>
-
-</refentry>
-
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/cliref.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/cliref.docbook
deleted file mode 100644
index a8ff53e..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/cliref.docbook
+++ /dev/null
@@ -1,569 +0,0 @@
-<sect1 id="scripts-bash-cliref">
-
- <title>Command-line Interface</title>
-
- <para>
- The <command>centos-art.sh</command> script follows a
- conventional GNU/Linux command-line interface where there
- might be options and non-option arguments in it. As convention
- to <command>centos-art.sh</command>, the first non-option
- argument passed through the command-line will be the name of
- the specific function you want to execute (e.g., <xref
- linkend="scripts-bash-render" />, <xref
- linkend="scripts-bash-locale" />, <xref
- linkend="scripts-bash-help" />, etc.). This first argument
- will be immediately removed from the list of arguments passed
- to <command>centos-art.sh</command> script leaving just the
- remaining options and non-option arguments passed to it. From
- this point on, the <command>centos-art.sh</command> script
- uses the <command>getopt</command> command to retrieve option
- arguments and remove them from the list of arguments passed to
- <command>centos-art.sh</command> script.
- </para>
-
- <para>
- To better understand the <command>centos-art.sh</command>
- command-line interface, consider the command shown in <xref
- linkend="scripts-bash-cliref-example1" />. This example
- shows the entire command as a list of space-separated
- arguments. Each argument passed in the command-line can be
- reached using positional variables as described in <xref
- linkend="scripts-bash-cliref-implementation-example1" />.
- </para>
-
- <example id="scripts-bash-cliref-example1">
- <title>The command-line interface</title>
- <screenshot>
- <screeninfo>The command-line interface</screeninfo>
- <mediaobject>
- <textobject>
-<programlisting>
-centos-art render Identity/Images/Themes --with-brands
-</programlisting>
- </textobject>
- </mediaobject>
- </screenshot>
- </example>
-
- <sect2 id="scripts-bash-cliref-options">
- <title>Option Arguments</title>
-
- <para>
- As convention inside the <command>centos-art.sh</command>, all
- specific function environments should provide support for the
- following option arguments:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><option>-h</option> | <option>--help</option></term>
- <listitem>
- <para>
- This option makes <command>centos-art.sh</command> to shows
- information about the specific function environment (e.g., how
- to execute it, available options, etc.) set as first
- non-option argument. For example, if you provide the
- <command>centos-art render --help</command>, the
- <command>centos-art.sh</command> script will display to you
- the information related to <xref linkend="scripts-bash-render"
- /> functionality.
- </para>
- <para>
- This information is retrieved from <quote>The CentOS Artwork
- Repository File System (tcar-fs)</quote> documentation manual.
- This manual is written in Texinfo format and provides a quick
- way for you to read and browse documentation related to each
- directory inside &TCAR; as you work with it from a text
- terminal.
- </para>
-
- <!--
- Enhancement
- ===========
- At some point, documentation written in Texinfo format will be
- replaced by Docbook format and profiling will be used to reach
- documentation model files which will be also transformed
- automatically based on the output required. In the case of
- centos-art.sh help functionality, man pages will be used as
- default output format.
- -->
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>-q</option> | <option>--quiet</option></term>
- <listitem>
- <para>
- This option makes the <command>centos-art.sh</command> script
- to suppress messages sent to standard output. This option
- doesn't suppress error messages, nor questions related to
- script execution.
- </para>
- </listitem>
- </varlistentry>
-
- </variablelist>
-
- <para>
- The specific option arguments used by function environments
- are described individually, as part of each function
- environment documentation. To know more about the specific
- options used by function environments, see <xref
- linkend="scripts-bash-cliref-specificfuncs" /> and <xref
- linkend="scripts-bash-cliref-commonfuncs" />.
- </para>
-
- <table id="scripts-bash-cliref-specificfuncs">
- <title>Specific functions environment</title>
- <tgroup cols="2" align="left">
- <thead>
- <row>
- <entry>Name</entry>
- <entry>Description</entry>
- </row>
- </thead>
-
- <tbody>
- <row>
- <entry><xref linkend="scripts-bash-prepare" /></entry>
- <entry>Standardize configuration tasks inside &TCAR;</entry>
- </row>
- <row>
- <entry><xref linkend="scripts-bash-render" /></entry>
- <entry>Standardize rendition tasks inside &TCAR;</entry>
- </row>
- <row>
- <entry><xref linkend="scripts-bash-locale" /></entry>
- <entry>Standardize localization tasks inside &TCAR;</entry>
- </row>
- <row>
- <entry><xref linkend="scripts-bash-help" /></entry>
- <entry>Standardize documentation tasks inside &TCAR;</entry>
- </row>
- <row>
- <entry><xref linkend="scripts-bash-pack" /></entry>
- <entry>Standardize packing tasks inside &TCAR;</entry>
- </row>
- <row>
- <entry><xref linkend="scripts-bash-tuneup" /></entry>
- <entry>Standardize maintainance tasks inside &TCAR;</entry>
- </row>
- <row>
- <entry><xref linkend="scripts-bash-vcs" /></entry>
- <entry>Standardize version control tasks inside &TCAR;</entry>
- </row>
- </tbody>
-
- </tgroup>
- </table>
-
- <table id="scripts-bash-cliref-commonfuncs">
- <title>Common functions environment</title>
- <tgroup cols="2" align="left">
- <thead>
- <row>
- <entry>Name</entry>
- <entry>Description</entry>
- </row>
- </thead>
-
- <tbody>
- <row>
- <entry>
- <literal>cli_checkFiles</literal>
- </entry>
- <entry>
- Standardize conditional expressions applied to files
- (including links and directories) inside the
- <command>centos-art.sh</command> script.
- </entry>
- </row>
- <row>
- <entry>cli_checkRepoDirSource</entry>
- <entry>
- Standardize directories' path construction inside the
- working copy, using absolute paths.
- </entry>
- </row>
- <row>
- <entry>cli_expandTMarkers</entry>
- <entry>
- Standardize translation markers construction and their
- related expansion.
- </entry>
- </row>
- <row>
- <entry>cli_exportFunctions</entry>
- <entry>
- Standardize the way specific functionalities are
- exported to <command>centos-art.sh</command> script
- environment.
- </entry>
- </row>
- <row>
- <entry>cli_getConfigLines</entry>
- <entry>
- Standardize the way configuration lines are retrieved
- form configuration files.
- </entry>
- </row>
- <row>
- <entry>cli_getConfigSectionNames</entry>
- <entry>
- Standardize the way section names are retrieved from
- configuration files.
- </entry>
- </row>
- <row>
- <entry>cli_getConfigValue</entry>
- <entry>
- Standardize the way configuration values are retrieved
- from configuration files.
- </entry>
- </row>
- <row>
- <entry>cli_getFilesList</entry>
- <entry>
- Standardize the way list of files are built inside
- <command>centos-art.sh</command> script.
- </entry>
- </row>
- <row>
- <entry>cli_getPathComponent</entry>
- <entry>
- Standardize the way directory structures are organized
- inside the working copy of &TCAR;.
- </entry>
- </row>
- <row>
- <entry>cli_getRepoName</entry>
- <entry>
- Standardize files and directories name convection
- inside the working copy of &TCAR;.
- </entry>
- </row>
- <row>
- <entry>cli_getTemporalFile</entry>
- <entry>
- Standardize temporal files creation.
- </entry>
- </row>
- <row>
- <entry>cli_parseArgumentsReDef</entry>
- <entry>
- Initiate/reset and sanitize positional parameters
- passed to this function and creates the list of
- arguments that <command>getopt</command> will process.
- </entry>
- </row>
- <row>
- <entry>cli_parseArguments</entry>
- <entry>
- Redefine the <varname>ARGUMENTS</varname> global
- variable using <command>getopt</command> output.
- </entry>
- </row>
- <row>
- <entry>cli_printCopyrightInfo</entry>
- <entry>
- Standardize the copyright information printed on
- content produced by <command>centos-art.sh</command>
- script.
- </entry>
- </row>
- <row>
- <entry>cli_printMailingList</entry>
- <entry>
- Standardize the way mailing list addresses are printed
- on content produced by
- <command>centos-art.sh</command> script.
- </entry>
- </row>
- <row>
- <entry>cli_printMessage</entry>
- <entry>
- Standardize the way messages are printed by
- <command>centos-art.sh</command> script.
- </entry>
- </row>
- <row>
- <entry>cli_printUrl</entry>
- <entry>
- Standardize the way URLs are printed by
- <command>centos-art.sh</command> script.
- </entry>
- </row>
- <row>
- <entry>cli_runFnEnvironment</entry>
- <entry>
- Standardize the way <command>centos-art.sh</command>
- script is called to itself.
- </entry>
- </row>
- <row>
- <entry>cli</entry>
- <entry>
- Initiates the <command>centos-art.sh</command> script
- command-line interface.
- </entry>
- </row>
- <row>
- <entry>cli_synchronizeRepoChanges</entry>
- <entry>
- Standardize the way changes are synchronized between
- the working copy and the central repository.
- </entry>
- </row>
- <row>
- <entry>cli_terminateScriptExecution</entry>
- <entry>
- Standardize the actions that must be realized just
- before leaving the script execution (e.g., cleaning
- temporal files).
- </entry>
- </row>
- <row>
- <entry>cli_unsetFunctions</entry>
- <entry>
- Unset functionalities from
- <command>centos-art.sh</command> script execution
- environment.
- </entry>
- </row>
-
- </tbody>
-
- </tgroup>
- </table>
-
- </sect2>
-
- <sect2>
- <title>Non-Option Arguments</title>
-
- <para>
- Once option arguments have been removed from the list of
- arguments passed to <command>centos-art.sh</command>
- command-line, non-option arguments are processed then.
- Non-option arguments will always be paths pointing to
- directories inside your working copy of &TCAR; or
- documentation entries pointing to specific sections in a
- documentation manual. Paths provided in the command-line can
- be absolute or relative considering the root directory of the
- working copy as start point. For example, both the absolute
- path <quote><filename
- class="directory">${HOME}/Projects/CentOS/artwork/Identity/Themes/</filename></quote>
- and the relative path <quote><filename
- class="directory">Identity/Themes</filename></quote> point to
- the same location. Documentation entries, on the other hand,
- exist to specify the files inside the <quote><filename
- class="directory">Documentation/Models/</filename></quote>
- directory structure you want to work with, based on specific
- documentation manual components (e.g., manual name, part,
- chapter or section). To know more about documentation entries,
- see the <xref linkend="scripts-bash-help"/> functionality
- reference.
- </para>
-
- </sect2>
-
- <sect2 id="scripts-bash-cliref-implementation">
-
- <title>Implementation</title>
-
- <para>
- The command-line interface of
- <command>centos-art.sh</command> script is implemented
- individually for each specific function environments it is
- made of. Each specific function environment inside the
- <command>centos-art.sh</command> has its own command-line
- definition and can differ in options when they are
- compared one another. The command-line differences between
- specific function environments exist as consequence of the
- purpose they were designed for (e.g., different purposes,
- different options and arguments). Nevertheless, all
- specific function environments use the same base
- construction to implement their unique command-line
- interfaces (see <xref
- linkend="scripts-bash-cliref-implementation-example1" />).
- </para>
-
- <para>
- The specific function environments the
- <command>centos-art.sh</command> script is made of use the
- <quote><filename>Scripts/Bash/Functions/<replaceable>Fname</replaceable>/<replaceable>fname</replaceable>_getOptions.sh</filename></quote>
- file to store the
- <function><replaceable>fname</replaceable>_getOptions</function>
- function definition. This function definition is where you
- set the relation between actions to be executed and
- arguments passed to <command>centos-art.sh</command>
- script.
- </para>
-
- <para>
- Basically, when you decide to create new function
- environments for the <command>centos-art.sh</command>
- script, you need to consider whether they will use
- arguments from the command-line or not. When the function
- environment doesn't need arguments (e.g., it exists to
- redefine values related to variables only) there is not
- need to consider a parsing feature for it. However, when
- you need to interact with a specific function through the
- command-line, you should use the
- <function><replaceable>fname</replaceable>_getOptions</function>
- function related to your
- <function><replaceable>fname</replaceable></function>
- function environment to define the way such interaction
- will take place. This way you can control the possible
- arguments your function environment will be able to
- interpret from the command-line.
- </para>
-
- <example id="scripts-bash-cliref-implementation-example1">
- <title>The command-line implementation</title>
- <screenshot>
- <screeninfo>The command-line implementation</screeninfo>
- <mediaobject>
- <textobject>
-<programlisting>
-function <replaceable>fname</replaceable>_getOptions {
-
- # Define short options we want to support.
- local ARGSS="h,q"
-
- # Define long options we want to support.
- local ARGSL="help,quiet"
-
- # Redefine ARGUMENTS using getopt(1) command parser.
- cli_parseArguments
-
- # Redefine positional parameters using ARGUMENTS variable.
- eval set -- "$ARGUMENTS"
-
- # Look for options passed through command-line.
- while true; do
-
- case "$1" in
-
- -h | --help )
- cli_runFnEnvironment help --read --format="texinfo" "tcar-fs::scripts:bash-functions-<replaceable>fname</replaceable>"
- shift 1
- exit
- ;;
-
- -q | --quiet )
- FLAG_QUIET="true"
- shift 1
- ;;
-
- -- )
- # Remove the `--' argument from the list of arguments
- # in order for processing non-option arguments
- # correctly. At this point all option arguments have
- # been processed already but the `--' argument still
- # remains to mark ending of option arguments and
- # beginning of non-option arguments. The `--' argument
- # needs to be removed here in order to avoid
- # centos-art.sh script to process it as a path inside
- # the repository, which obviously is not.
- shift 1
- break
- ;;
- esac
- done
-
- # Redefine ARGUMENTS variable using current positional parameters.
- cli_parseArgumentsReDef "$@"
-
-}
-</programlisting>
-</textobject>
-</mediaobject>
-</screenshot>
-</example>
-
- <para>
- Using the base structure described in <xref
- linkend="scripts-bash-cliref-implementation-example1"/>, you can
- create new options so your specific function environment
- can express its usefulness. For example, if you want your
- specific function environment to print a greeting on the
- screen when the <option>--hello</option> option is passed
- through its command-line, you can modify the base
- structure shown above with the following:
- </para>
-
-<programlisting>
-...
-
- # Define long options we want to support.
- local ARGSL="help,quiet,hello"
-
-...
-
- --hello )
- cli_printMessage "`gettext "Hello World!"`"
- shift 1
- ;;
-...
-</programlisting>
-
- <para>
- In case you want to provide an option value in the form
- <option>--hello="World"</option>, you can do it as described
- below:
- </para>
-
-<programlisting>
-...
-
- # Define long options we want to support.
- local ARGSL="help,quiet,hello:"
-
-...
-
- --hello )
- cli_printMessage "`gettext "Hello"` ${2}"
- shift 2
- ;;
-...
-</programlisting>
-
- <para>
- In this last case, the option value is required. So, if you
- provide the <option>--hello</option> option but do not provide
- a value for it, an error will be triggered and the script will
- finish its execution. To make an option value not-required,
- you need to use two colons instead of one when you define the
- options, see the following lines:
- </para>
-
-<programlisting>
-...
-
- # Define long options we want to support.
- local ARGSL="help,quiet,hello::"
-
-...
-
- --hello )
- cli_printMessage "`gettext "Hello"` ${2}"
- shift 2
- ;;
-...
-</programlisting>
-
- <para>
- To know more about the features provided by
- <command>getopt</command> command, read its man page (e.g.,
- typing the <command>man getopt</command> command in your
- terminal). This information will also help you to understand
- how to improve the command-line interfaces you create for
- the function environments of <command>centos-art.sh</command>
- script.
- </para>
-
- </sect2>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/environment.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/environment.docbook
deleted file mode 100644
index fbbcfd9..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/environment.docbook
+++ /dev/null
@@ -1,475 +0,0 @@
-<sect1 id="scripts-bash-environment">
-
- <title>The Execution Environment</title>
-
- <para>
- The execution environment of <command>centos-art.sh</command>
- script is organized in four levels. The first level is the
- <quote>shell environment</quote>, the second level is the
- <quote>command environment</quote>, the third level is the
- <quote>common functions environment</quote> and, finally, the
- fourth level which contains the <quote>specific function
- environment</quote>, as described in <xref
- linkend="scripts-bash-environment-example1" />. In this
- context, child environments inherit definitions (e.g.,
- variables and functions) from their parent environments making
- possible to logically organize the script in a way that needs
- can be isolated one another to follow the paradigm proposed by
- Unix developers at Bell Labs when felt that programs
- <quote>should do one thing well.</quote>
- </para>
-
- <example id="scripts-bash-environment-example1">
- <title>The execution environment</title>
- <screenshot>
- <screeninfo>The execution environment</screeninfo>
- <mediaobject>
- <textobject>
-<programlisting>
-+-----------------------------------------------------+
-| Shell environment |
-+---|-------------------|-----------------|-----------+
-. |-- TCAR_WORKDIR |-- TCAR_BRAND |-- EDITOR .
-. |-- LANG |-- HOME |-- PATH .
-. `-- centos-art.sh `-- TMPDIR `-- ... .
-. +---|-----------------------------------------+ .
-. | Command environment | .
-. +---|---------------|----------------|--------+ .
-. . |-- CLI_NAME |-- CLI_VERSION `-- ... . .
-. . |-- CLI_FUNCDIR `-- CLI_BASEDIR . .
-. . `-- cli() . .
-. . +---|-----------------------------------+ . .
-. . | Common functions environment | . .
-. . +---|------------------------|----------+ . .
-. . . |-- cli_printMessage() |-- ... . . .
-. . . |-- cli_getFilesList() |-- ... . . .
-. . . `-- render() `-- ... . . .
-. . . +---|---------------------------+ . . .
-. . . | Specific function environment | . . .
-. . . +-------------------------------+ . . .
-. . ......................................... . .
-. ............................................... .
-.......................................................
-</programlisting>
- </textobject>
- </mediaobject>
- </screenshot>
- </example>
-
- <sect2>
- <title>The Shell Environment</title>
-
- <para>
- The <command>centos-art.sh</command> script uses the following
- shell environment variables:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><envar>PATH</envar></term>
- <listitem>
- <para>
- The <envar>PATH</envar> environment variable is specific to
- the operating system and provides search paths for command
- execution. By default, the <command>centos-art.sh</command>
- script links executable scripts from the <filename
- class="directory">~/bin</filename> directory which is one of
- the locations used as search path in this variable. This is
- how we create the <command>centos-art</command> command from
- the <command>centos-art.sh</command> script inside your
- working copy.
- </para>
-
- <para>
- This variable is not initialized inside the
- <command>centos-art.sh</command> script. Instead, the value
- set in <filename>~/.bash_profile</filename> file is used.
- </para>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><envar>EDITOR</envar></term>
- <listitem>
- <para>
- The <envar>EDITOR</envar> environment variable is specific to
- the operating system and provides the path to your default
- text editor. The <command>centos-art.sh</command> script uses
- the default text editor to edit subversion pre-commit
- messages, translation files, documentation files, script
- files, and similar text-based files.
- </para>
-
- <para>
- Possible values for this variable are:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <filename class="directory">/usr/bin/vim</filename>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <filename class="directory">/usr/bin/emacs</filename>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <filename class="directory">/usr/bin/nano</filename>
- </para>
- </listitem>
- </itemizedlist>
-
- <para>
- In case none of these values is set for the
- <envar>EDITOR</envar> environment variable inside
- <filename>~/.bash_profile</filename>, the
- <command>centos-art.sh</command> script uses <filename
- class="directory">/usr/bin/vim</filename> as default text
- editor. This is the text editor installed by default in &TCD;.
- </para>
-
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><varname>TEXTDOMAIN</varname></term>
- <listitem>
- <para>
- The <envar>TEXTDOMAIN</envar> environment variable is specific
- to the operating system and provides the domain name of that
- application we are producing translation messages for. This
- variable, in combination with <envar>TEXTDOMAINDIR</envar>, is
- used by <application>gettext</application> to find out the
- location of translation messages. In the very specific case
- of <command>centos-art.sh</command> script we use the
- <literal>centos-art.sh</literal> name as domain name.
- </para>
-
- <para>
- This variable is initialized inside the
- <command>centos-art.sh</command> script, so if you set it
- outside it (e.g., in <filename>~/.bash_profile</filename>) the
- value you set there will be overwritten by that one set inside
- <command>centos-art.sh</command> script, once it is executed.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><varname>TEXTDOMAINDIR</varname></term>
- <listitem>
- <para>
- The <envar>TEXTDOMAINDIR</envar> environment variable is
- specific to the operating system and provides the absolute
- path to the directory containing the translation messages
- related to that application specified by
- <envar>TEXTDOMAIN</envar> environment variable. In the very
- specific case of <command>centos-art.sh</command> script we
- use the <filename
- class="directory">Locales/Scripts/Bash</filename>
- path as default value.
- </para>
- <para>
- This variable is initialized inside the
- <command>centos-art.sh</command> script, so if you set it
- outside it (e.g., in <filename>~/.bash_profile</filename>) the
- value you set there will be overwritten by that one set inside
- <command>centos-art.sh</command> script, once it is executed.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><envar>TMPDIR</envar></term>
- <listitem>
- <para>
- The <envar>TMPDIR</envar> environment variable is specific to
- the operating system and provides the absolute path to the
- temporal directory the centos-art.sh script will use along its
- execution. This variable is defined inside the
- <command>centos-art.sh</command> script itself using the
- <command>mktemp</command> command and will be unique on each
- script execution. Thus, you should be able to run several
- instances of <command>centos-art.sh</command> script
- simultaneously without any problem.
- </para>
-
- <para>
- When you contribute code to <command>centos-art.sh</command>
- script and need to create temporal files, do it inside the
- absolute path specified by this variable.
- </para>
-
- <para>
- This variable is redefined inside the
- <command>centos-art.sh</command> script, so if you set it
- outside it (e.g., in <filename>~/.bash_profile</filename>) the
- value you set there will be overwritten by that one set inside
- <command>centos-art.sh</command> script, once it is executed.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><envar>LANG</envar></term>
- <listitem>
- <para>
- The <envar>LANG</envar> environment variable is specific to
- the operating system and controls the default locale
- information of it. The <command>centos-art.sh</command>
- script use the <envar>LANG</envar> environment variable to
- determine what language to use for printing output messages
- from the script itself, as well as the portable objects
- locations that need to be updated or edited when you localize
- directory structures inside the working copy of &TCAR;.
- </para>
-
- <para>
- The <envar>LANG</envar> environment variable is initially set
- in the installation process of &TCD;, specifically in the
- <emphasis>Language</emphasis> step. Generally, there is no
- need to customize this variable in your personal profile. If
- you need to change the value of this environment variable do
- it through the login screen of GNOME Desktop Environment or
- the <command>system-config-language</command> command, or even
- resetting the variable before executing the
- <command>centos-art.sh</command> script.
- </para>
- </listitem>
- </varlistentry>
-
- </variablelist>
-
- <para>
- In addition to shell environment variables described above,
- the <command>centos-art.sh</command> script adds the following
- variables inside the <filename>~/.bash_profile</filename> file
- to control the script behaviour in a per-user level:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><varname>TCAR_WORKDIR</varname></term>
- <listitem>
- <para>
- The <envar>TCAR_WORKDIR</envar> environment variable is
- specific to <command>centos-art.sh</command> script and
- controls the working copy default location of &TCAR;. This is
- the place in your workstation where &TCAR; file system is
- stored for you to work with it.
- </para>
-
- <para>
- By default, just after installing your workstation, this
- variable will not be found in it and the
- <command>centos-art.sh</command> script will finish its
- execution with an error message if you try to execute it
- without any argument. This behaviour is OK because the
- <command>centos-art.sh</command> script doesn't know where you
- stored the working copy of &TCAR; in your workstation. In
- order for this variable to exist in your workstation you need
- to configure your workstation first, as described in <xref
- linkend="repo-ws-config" />.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><varname>TCAR_BRAND</varname></term>
- <listitem>
- <para>
- The <envar>TCAR_BRAND</envar> environment variable is specific
- to <command>centos-art.sh</command> script and controls the
- brand information that identifies the content produced inside
- &TCAR;. The brand information is used to give name to some
- files inside the repository (e.g., see files under <filename
- class="directory">Identity/Models/Brands</filename>
- directory).
- </para>
- <para>
- By default, this variable takes <quote>centos</quote> as
- value. In case you want to change it to something else, you
- should consider the following implications:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- The <command>centos-art.sh</command> script will no longer be
- referred as such. Instead, the
- <filename>${TCAR_BRAND}-art.sh</filename> name will be used.
- This implies that you no longer are using the
- <command>centos-art.sh</command> file we provide as part of
- &TCAR; and won't be able to commit changes to it. However, if
- you retain the same logic from
- <command>centos-art.sh</command> script in
- <filename>${TCAR_WORKDIR}-art.sh</filename>, you can use
- common and specific functionalities provided by
- <command>centos-art.sh</command> script and commit changes to
- them.
- </para>
- </listitem>
- <listitem>
- <para>
- The files stored under <filename
- class="directory">Identity/Models/Brands</filename>
- should be named using the value of
- <literal>${TCAR_BRAND}</literal> as section. If you change
- the value of this variable, you need to be sure the new value
- set does coincide with the file names you use to store brand
- information.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </varlistentry>
- </variablelist>
-
- </sect2>
-
- <sect2>
- <title>The Command Environment</title>
-
- <para>
- The first file the <command>centos-art.sh</command> script
- calls is the
- <filename>Scripts/Bash/Functions/Commons/cli.sh</filename>
- file. This file initializes all variables and functions you
- will be able to use along the script execution environment
- lifetime. Such environment variables are for internal use
- inside the <command>centos-art.sh</command> script only and
- users shouldn't modify them to customize the script in a
- per-user level. Instead, to customize the script behaviour in
- a per-user level, you need to make use of your personal
- environment variables set in the
- <filename>~/.bash_profile</filename> file.
- </para>
-
- <para>
- Once environment variables are initialized, the
- <command>centos-art.sh</command> script initializes common and
- specific environment functions, in that order.
- </para>
-
- <sect3>
- <title>Common Function Environment</title>
-
- <para>
- Common function environments are stored under <filename
- class="directory">Scripts/Bash/Functions/Commons</filename>
- directory and will be available always, both for common
- environment functions themselves and specific environment
- functions.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Specific Function Environments</title>
-
- <para>
- Specific function environments, on the other hand, are stored
- in the <filename
- class="directory">Scripts/Bash/Functions/${CLI_FUNCDIRNAM}/${CLI_FUNCNAME}.sh</filename>
- file, where:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><varname>CLI_FUNCDIRNAME</varname></term>
- <listitem>
- <para>
- Is the first argument passed to
- <command>centos-art.sh</command> script with the first letter
- in uppercase but the rest in lowercase. For example,
- <literal>Render</literal>, <literal>Locale</literal> and
- <literal>Help</literal> are all possible values to this
- variable.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><varname>CLI_FUNCNAME</varname></term>
- <listitem>
- <para>
- Is the first argument passed to
- <command>centos-art.sh</command> script with all letters in
- lowercase. For example, <literal>render</literal>,
- <literal>locale</literal> and <literal>help</literal> are all
- possible values to this variable.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- Specific functions environment can be written in just one file
- or in several files inside the same directory. Using one file
- to write specific functions environment is rarely seen inside
- the <command>centos-art.sh</command> script but it could
- happen in situations where the need you want to solve can be
- written in a few lines inside just one file. On the other
- hand, if you find yourself writing a too long file, it is
- convenient to logically divide it into several files. This
- logical division takes place using functions, which indeed
- create other environments where you can create and express
- your solutions.
- </para>
-
- <para>
- The order in which individual files are exported and executed
- inside the specific functions environments depends in the way
- each developer write the <filename
- class="directory">Scripts/Bash/Functions/${CLI_FUNCDIRNAM}/${CLI_FUNCNAME}.sh</filename>
- file. This is the main file inside the specific function
- environment and controls the kind of logical division you
- implement to organize the solution you need. As file name
- convention, the following structure for new specific functions
- environment is proposed:
- </para>
-
-<programlisting>
-Scripts/Bash/Functions/${CLI_FUNCDIRNAM}/
-|-- ${CLI_FUNCNAME}.sh
-`-- ${CLI_FUNCNAME}_verbSubject.sh
-</programlisting>
-
- <para>
- Specific functions environment is exported after common
- functions environment does, so it is not possible for specific
- functions environment to be available inside the common
- functions environment, nor inside other specific functions
- environment, different to the one been passed as first
- argument to the <command>centos-art.sh</command> script
- command-line.<footnote>
- <para>
- Although, it is possible for you to call the
- <command>centos-art.sh</command> script to itself
- through the <function>cli_runFnEnvironment</function>
- common function environment.
- </para>
- </footnote> In <xref
- linkend="scripts-bash-environment-example1" />,
- <function>render</function> is a specific function environment
- while <function>cli_printMessage</function> and
- <function>cli_getFilesList</function> are common function
- environments.
- </para>
-
- <para>
- Both specific and common function environments exist to
- standardize frequent tasks inside &TCAR;. The following
- sections will describe which these frequent tasks are and the
- way they are standardized using specific and common function
- environments.
- </para>
- </sect3>
-
- </sect2>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/funref.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/funref.docbook
deleted file mode 100644
index c67c159..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/funref.docbook
+++ /dev/null
@@ -1,1294 +0,0 @@
-<sect1 id="scripts-bash-funref">
-
- <title>Environment Functions Reference</title>
-
- <para>
- In addition to environment variables described above, the
- centos-art.sh script makes available the following common
- environment functions once it is executed:
- </para>
-
- <variablelist>
-
- <varlistentry>
- <term>
- <cmdsynopsis>
- <command id="cli_checkRepoDirSource" xreflabel="cli_checkRepoDirSource">cli_checkRepoDirSource
- <indexterm type="common-function" zone="cli_checkRepoDirSource">
- <primary>cli_checkRepoDirSource</primary>
- </indexterm>
- </command>
- </cmdsynopsis>
- </term>
- <listitem>
-
- <para>
- The <function>cli_checkRepoDirSource</function> function
- standardizes the path construction to directories inside it
- the working copy, using absolute paths. This function
- transforms relative paths passed as non-option arguments to
- <command>centos-art.sh</command> script command-line into
- absolute paths inside the working copy and verifies whether
- they really exist as directories inside the working copy or
- not. If the path provided doesn't exist as directory inside
- the working copy, the script will finish its execution
- immediately with an error message. Otherwise, if the directory
- exists, the variable <varname>ACTIONVAL</varname> is redefined
- with the related absolute path for further use.
- </para>
-
- <para>
- Use the <function>cli_checkRepoDirSource</function> function
- whenever you need to be sure that non-option arguments passed
- to <command>centos-art.sh</command> script command-line will
- always point to directories inside the working copy.
- </para>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
- <cmdsynopsis>
- <command id="cli_expandTMarkers" xreflabel="cli_expandTMarkers">cli_expandTMarkers
- <indexterm type="common-function" zone="cli_expandTMarkers">
- <primary>cli_expandTMarkers</primary>
- </indexterm>
- </command>
- <arg choice="req"><replaceable>LOCATION</replaceable></arg>
- </cmdsynopsis>
- </term>
- <listitem>
- <para>
- The <function>cli_expandTMarkers</function> standardizes
- construction of translation markers and their related
- expansion. As convention, translation markers are set inside
- source files (e.g., DocBook, SVG) and expanded inside temporal
- instances used to produce final contents. The
- <replaceable>LOCATION</replaceable> argument should point to
- the temporal file where translation markers expansion takes
- place in.
- </para>
- <para>
- Translation markers written in source files must comply the
- <literal>=[A-Z_]+=</literal> regular expression pattern. For
- example, <literal>=UNKNOWN_MARKER=</literal> is a valid
- translation marker without any replacement. To prevent
- <command>centos-art.sh</command> script from expanding
- translation markers, add a backslash (<literal>\</literal>)
- between the first equal sign and the following letter. For
- example, <literal>=\...=</literal> won't be expanded.
- </para>
- <para>
- The <function>cli_expandTMarkers</function> supports the
- following translation markers:
- </para>
- <variablelist>
- <varlistentry>
- <term><literal>=\COPYRIGHT_YEAR_LAST=</literal></term>
- <term><literal>=\COPYRIGHT_YEAR=</literal></term>
- <listitem>
- <para>
- These translation markers expand to the last year used in
- copyright notes. For example,
- <literal>=COPYRIGHT_YEAR_LAST=</literal>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\COPYRIGHT_YEAR_LIST=</literal></term>
- <term><literal>=\COPYRIGHT_YEARS_LIST=</literal></term>
- <listitem>
- <para>
- This translation markers expand to the list of years used in
- copyright notes. For example,
- <literal>=COPYRIGHT_YEARS_LIST=</literal>. The first year
- represents the time we began to work on &TCAR;.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\COPYRIGHT_HOLDER=</literal></term>
- <listitem>
- <para>
- This translation marker expands to the holder used in
- copyright notes. For example,
- <literal>=COPYRIGHT_HOLDER=</literal>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\COPYRIGHT_HOLDER_PREDICATE=</literal></term>
- <listitem>
- <para>
- This translation marker expands both the holder and the
- predicate used in copyright notes. For example,
- <literal>=COPYRIGHT_HOLDER_PREDICATE=</literal>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\BRAND=</literal></term>
- <listitem>
- <para>
- This translation marker expands to the brand name used on
- files names and URLs inside &TCAR;. For example,
- <literal>=BRAND=</literal>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\LICENSE=</literal></term>
- <listitem>
- <para>
- This translation marker expands to the license information
- used in files created by <command>centos-art.sh</command>
- script. For example, <literal>=LICENSE=</literal>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\LICENSE_URL=</literal></term>
- <listitem>
- <para>
- This translation marker expands to the license URL used in
- files created by <command>centos-art.sh</command> script. For
- example, <literal>=LICENSE_URL=</literal>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\THEME=</literal></term>
- <listitem>
- <para>
- This translation marker expands to the theme portion of path
- you are producing through centos-art.sh script. As
- consequence, this translation marker should be used in
- situations where you are producing theme components only.
- This translation marker expands its value by retrieving the
- theme part of the path you provide as non-option argument to
- <command>centos-art.sh</command> script. For example, if you
- provide the path
- <filename>Identity/Images/Themes/Modern/2/Distro/5</filename>,
- this translation will expand to the
- <literal>Modern/2/</literal> value.
- </para>
- <para>
- In case you need to retrieve the theme name or version
- separately one another, then you can use the
- <literal>=\THEMENAME=</literal> and
- <literal>=\THEMERELEASE=</literal> translation markers,
- respectively. When you use these translation markers, forward
- slashes are removed from result. So, if you provide the path
- <filename>Identity/Images/Themes/Modern/2/Distro/5</filename>,
- <literal>=\THEMENAME=</literal> will expand to
- <literal>Modern</literal> and
- <literal>=THEMERELEASE=</literal> will expand to
- <literal>2</literal>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\RELEASE=</literal></term>
- <listitem>
- <para>
- This translation marker expands to the current release
- information of your CentOS distribution. By default this
- information is retrieved from
- <filename>/etc/redhat-release</filename>. In case the option
- <option>--release</option> be passed, the value specified with
- it will overwrite the default value and will be this the one
- used as section for this translation marker to retrieve the
- release information. So, for example, if you are running a
- CentOS-5.8 distribution and no <option>--release</option>
- option is passed to <command>centos-art.sh</command> script,
- this translation marker expands to <literal>5.8</literal>. On
- the other hand, if you are still running a CentOS-5.8
- distribution but provide the <option>--release=6.3</option>
- option to <command>centos-art.sh</command> script, this
- translation marker expands to <literal>6.3</literal> instead.
- </para>
- <para>
- In case you need to retrieve minor and major release numbers
- separately one another, then you can use the
- <literal>=\MINOR_RELEASE=</literal> and
- <literal>=\MAJOR_RELEASE=</literal> translation makers,
- respectively.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\ARCH=</literal></term>
- <listitem>
- <para>
- This translation marker expands to the current architecture of
- your CentOS Distribution. By default this information is
- retrieved from <command>uname -i</command>. In case the option
- <option>--arch</option> be passed, the value specified with it
- will overwrite the default value and will be the one used as
- section. For example, if the <command>uname -i</command>
- outputs the line <computeroutput>i386</computeroutput>, this
- translation marker will expand to <literal>i386</literal>. On
- the other hand, if you pass the <option>--arch=x86_64</option>
- option to <command>centos-art.sh</command> script, this
- translation marker will expand to <literal>x86_64</literal>
- instead.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\URL=</literal></term>
- <listitem>
- <para>
- This translation marker expands to the URL which points to
- &TCP; home page. For example, <literal>=URL=</literal>. In
- case you are using the centos-art.sh script in a different
- locale but English (<literal>en_US.UTF-8</literal>), this
- translation marker expands as usual but with the language
- information appended to the end of the string. For example, if
- you are executing the centos-art.shscript for Spanish locale
- (e.g., <literal>es_ES.UTF-8</literal>), this translation
- marker expands to <literal>=URL=es/</literal>.
- </para>
-
- <para>
- In case you need to expand other URL related to &TCP; domain,
- use translation markers described in <xref
- linkend="scripts-bash-funref-expandTMarkers-Url" />. Likewise
- =\URL=, translation markers described in <xref
- linkend="scripts-bash-funref-expandTMarkers-Url" /> does
- append the current language information to the end of the URL
- string based on the locale information you are currently
- executing the <command>centos-art.sh</command> script.
- </para>
-
- <table id="scripts-bash-funref-expandTMarkers-Url">
- <title>URL-related translation markers</title>
- <tgroup cols="2" align="left">
- <thead>
- <row>
- <entry>Translation Marker</entry>
- <entry>Expands To</entry>
- </row>
- </thead>
-
- <tbody>
- <row>
- <entry><literal>=\URL_WIKI=</literal></entry>
- <entry><literal>=URL_WIKI=</literal></entry>
- </row>
- <row>
- <entry><literal>=\URL_LISTS=</literal></entry>
- <entry><literal>=URL_LISTS=</literal></entry>
- </row>
- <row>
- <entry><literal>=\URL_FORUMS=</literal></entry>
- <entry><literal>=URL_FORUMS=</literal></entry>
- </row>
- <row>
- <entry><literal>=\URL_MIRRORS=</literal></entry>
- <entry><literal>=URL_MIRRORS=</literal></entry>
- </row>
- <row>
- <entry><literal>=\URL_DOCS=</literal></entry>
- <entry><literal>=URL_DOCS=</literal></entry>
- </row>
- <row>
- <entry><literal>=\URL_PROJECTS=</literal></entry>
- <entry><literal>=URL_PROJECTS=</literal></entry>
- </row>
- <row>
- <entry><literal>=\URL_SVN=</literal></entry>
- <entry><literal>=URL_SVN=</literal></entry>
- </row>
- <row>
- <entry><literal>=\URL_TRAC=</literal></entry>
- <entry><literal>=URL_TRAC=</literal></entry>
- </row>
- <row>
- <entry><literal>=\URL_PLANET=</literal></entry>
- <entry><literal>=URL_PLANET=</literal></entry>
- </row>
- </tbody>
-
- </tgroup>
- </table>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\MAIL_DOCS=</literal></term>
- <listitem>
- <para>
- This translation marker expands to CentOS documentation
- mailing list address. For example,
- <literal>=MAIL_DOCS=</literal>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\LOCALE=</literal></term>
- <listitem>
- <para>
- This translation marker expands to the current locale
- information used by <command>centos-art.sh</command> script.
- This value is retrieved from the <envar>LANG</envar>
- environment variable and should look like
- <literal>=LOCALE=</literal>. In case you need to retrieve the
- language and country part separately one another, you can use
- the <literal>=\LOCALE_LL=</literal> and
- <literal>=\LOCALE_CC=</literal>, respectively.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\REPO_TLDIR=</literal></term>
- <listitem>
- <para>
- This translation marker expands to the absolute path to
- <filename class="directory"></filename> directory inside
- your workstation. For example,
- <literal>/home/al/Projects/CentOS/artwork/trunk</literal>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>=\REPO_HOME=</literal></term>
- <term><literal>=\TCAR_WORKDIR=</literal></term>
- <listitem>
- <para>
- This translation marker expands to the absolute path of your
- working copy. For example,
- <literal>/home/al/Projects/CentOS/artwork</literal>.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- See also: <xref linkend="cli_getTemporalFile" />
- </para>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
- <cmdsynopsis>
- <command id="cli_exportFunctions" xreflabel="cli_exportFuncations">cli_exportFunctions
- <indexterm type="common-function" zone="cli_exportFunctions">
- <primary>cli_exportFunctions</primary>
- </indexterm>
- </command>
- <arg choice="req"><replaceable>EXPORTID</replaceable></arg>
- </cmdsynopsis>
- </term>
- <listitem>
- <para>
- The <function>cli_exportFunctions</function> function
- standardizes the way specific functionalities are exported to
- <command>centos-art.sh</command> script execution environment.
- The <replaceable>EXPORTID</replaceable> argument points the
- specific function initialization file relatively from
- <filename>Scripts/Bash/Functions</filename> directory
- on. For example, if we want to export the
- <function>render</function> specific functionality, we use the
- following construction:
- </para>
-<programlisting>
-cli_exportFunctions "Render/render"
-</programlisting>
- <para>
- In this construction, <literal>Render</literal> with the first
- letter in upper case is the name of the directory under
- <filename
- class="directory">Scripts/Bash/Functions</filename>
- where the specific functionality is stored in, and
- <literal>render</literal> with all letters in lower case is
- the name of the specific functionality we want to export,
- without its extension. This name is also used as suffix to
- identify all files related to the specific functionality we
- are exporting to <command>centos-art.sh</command> script
- execution environment.
- </para>
-
- <para>
- See also: <xref linkend="cli_unsetFunctions" />
- </para>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
- <cmdsynopsis>
- <command id="cli_getConfigLines" xreflabel="cli_getConfigLines">cli_getConfigLines
- <indexterm type="cli_getConfigLines" zone="cli_getConfigLines">
- <primary>cli_getConfigLines</primary>
- </indexterm>
- </command>
- <arg choice="req"><replaceable>FILE</replaceable></arg>
- <arg choice="req"><replaceable>SECTION</replaceable></arg>
- <arg choice="req"><replaceable>OPTION</replaceable></arg>
- </cmdsynopsis>
- </term>
- <listitem>
- <para>
- The <function>cli_getConfigLines</function> function
- standardizes the way configuration lines are retrieved from
- configuration files.
- </para>
-
- <para>
- The <function>cli_getConfigLines</function> function accepts
- the following arguments:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><replaceable>FILE</replaceable></term>
- <listitem>
- <para>
- This argument specifies the absolute path to the configuration
- file you want to retrieve configuration lines from. For
- example,
- <quote><filename>${TCAR_WORKDIR}/Identity/Models/Themes/Default/Distro/5/Anaconda/branding.conf</filename></quote>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><replaceable>SECTION</replaceable></term>
- <listitem>
- <para>
- This argument specifies the name of the section you want to
- retrieve configuration lines from. For example,
- <quote>symbols</quote> without brackets.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><replaceable>OPTION</replaceable></term>
- <listitem>
- <para>
- This argument specifies the name of the option related to the
- configuration line you want to retrieve. For example,
- <quote>anaconda_header.svgz</quote>.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- In order for <function>cli_getConfigLines</function> to work
- properly, the configuration files must have a section line
- with the form <literal>[sectionname]</literal> which groups
- several <literal>option = "value"</literal> lines.
- Lines beginning with <literal>#</literal> are ignored and can
- be used for comments.
- </para>
-
- <example id="cli_getConfigLines-conffile">
- <title>Configuration file used to produce Tcar-fs documentation manual</title>
- <screenshot>
- <screeninfo>Configuration used to produce Tcar-fs documentation manual</screeninfo>
- <mediaobject>
- <textobject>
-<programlisting>
-[main]
-
-# Specify documentation backend used by documentation manual.
-manual_format = "texinfo"
-
-# Specify title style used by sections inside the manual.
-manual_section_style = "directory"
-
-# Specify the order used by sections inside the manual.
-manual_section_order = "ordered"
-
-[templates]
-
-# Specify relation between template files and section definition files
-# inside the manual.
-Chapters/section-functions.texinfo = "^.+-functions-[[:alnum:]]+\.texinfo$"
-Chapters/section.texinfo = "^.+\.texinfo$"
-</programlisting>
-</textobject>
-</mediaobject>
-</screenshot>
- </example>
-
- <para>
- The section names and option names used inside configuration
- files can be anything. It depends on the use and
- interpretation programmed inside
- <command>centos-art.sh</command> script for specific purposes
- which defines what kind of section and options must exist
- inside a configuration file. For example, consider the
- configuration files used by <function>render</function>
- functionality. They follow the same structure used in
- documentation configuration files but the meaning of their
- sections and options change to fit the specific needs of
- <function>render</function> functionality.
- </para>
-
- <example id="cli_getConfigLines-conffile-2">
- <title>Configuration file used to produced Anaconda images</title>
- <screenshot>
- <screeninfo>Configuration used to produced Anaconda images</screeninfo>
- <mediaobject>
- <textobject>
-<programlisting>
-[types]
-
-anaconda_header.svgz = "Types/White/48/=\BRAND=-5.png:x48+20+20"
-first.svgz = "Types/White/32/=\BRAND=-5.png:x32+30+219"
-splash.svgz = "Types/White/48/=\BRAND=-5-msg.png:x48+30+138"
-
-[symbols]
-
-anaconda_header.svgz = "Symbols/48/=\BRAND=.png:x48+732+20"
-first.svgz = "Symbols/48/=\BRAND=.png:x48+30+20"
-splash.svgz = "Symbols/48/=\BRAND=.png:x48+30+20"
-</programlisting>
-</textobject>
-</mediaobject>
-</screenshot>
- </example>
-
- <para>
- Use the <function>cli_getConfigLines</function> function when
- you need to retrieve <literal>option = "value"</literal> lines
- from configuration files in a controlled way.
- </para>
-
- <para>
- See also: <xref linkend="cli_getConfigValue" />
- </para>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
- <cmdsynopsis>
- <command id="cli_getConfigValue" xreflabel="cli_getConfigValue">cli_getConfigValue
- <indexterm type="common-function" zone="cli_getConfigValue">
- <primary>cli_getConfigValue</primary>
- </indexterm>
- </command>
- <arg choice="req"><replaceable>FILE</replaceable></arg>
- <arg choice="req"><replaceable>SECTION</replaceable></arg>
- <arg choice="req"><replaceable>OPTION</replaceable></arg>
- </cmdsynopsis>
- </term>
- <listitem>
- <para>
- The <function>cli_getConfigValue</function> function
- standardizes the way option values are retrieved from
- configuration files. As convention,
- <function>cli_getConfigValue</function> uses the output
- produced by <function>cli_getConfigLines</function> as input
- to retrieve the option values. As convention, in
- <literal>option = "value"</literal> lines, the values
- retrieved are always on the right side. The values retrieved
- are also output without quotation and translation markers
- already expanded.
- </para>
-
- <para>
- The <function>cli_getConfigValue</function> function accepts
- the following arguments:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><replaceable>FILE</replaceable></term>
- <listitem>
- <para>
- This argument specifies the absolute path to the configuration
- file you want to retrieve the value from. For example,
- <quote><filename>${TCAR_WORKDIR}/Identity/Models/Themes/Default/Distro/5/Anaconda/branding.conf</filename></quote>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><replaceable>SECTION</replaceable></term>
- <listitem>
- <para>
- This argument specifies the name of the section related to the
- configuration line you want to retrieve the value from. For
- example, <quote>symbols</quote> without brackets.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><replaceable>OPTION</replaceable></term>
- <listitem>
- <para>
- This argument specifies the name of the option you want to
- retrieve the value from. For example, in <xref
- linkend="cli_getConfigLines-conffile-2" />, the
- <quote><literal>anaconda_header.svgz</literal></quote> option will output the
- <quote><literal>Symbols/48/=\BRAND=.png:x48+732+20</literal></quote> value
- without quotation and translation markers expanded. So if the
- value of <envar>TCAR_BRAND</envar> environment variable is
- <quote><literal>centos</literal></quote>, the real value you
- get will be
- <quote><literal>Symbols/48/centos.png:x48+732+20</literal></quote>.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- Use the <function>cli_getConfigValue</function> function
- whenever you want to retrieve values from configuration files
- in a controlled way.
- </para>
-
- <para>
- See also: <xref linkend="cli_getConfigLines" />
- </para>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
- <cmdsynopsis>
- <command id="cli_getFilesList" xreflabel="cli_getFilesList">cli_getFilesList
- <indexterm type="common-function" zone="cli_getFilesList">
- <primary>cli_getFilesList</primary>
- </indexterm>
- </command>
- <arg choice="opt">--pattern</arg>
- <arg choice="opt">--mindepth</arg>
- <arg choice="opt">--maxdepth</arg>
- <arg choice="opt">--type</arg>
- <arg choice="opt">--uid</arg>
- <arg choice="req" rep="repeat"><replaceable>LOCATION</replaceable></arg>
- </cmdsynopsis>
- </term>
- <listitem>
- <para>
- The <function>cli_getFilesList</function> standardizes the way
- list of files are built inside the
- <command>centos-art.sh</command> script. This function outputs
- a sorted and unique list of files based on the options and
- location provided as argument. This function is an interface
- to the <command>find</command> command. Don't use
- <command>find</command> command directly inside the
- centos-art.sh script. Instead, use the
- <function>cli_getFilesList</function> function.
- </para>
- <para>
- The <function>cli_getFilesList</function> accepts the
- following arguments:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><replaceable>LOCATION</replaceable></term>
- <listitem>
- <para>
- This arguments must be the absolute path to a directory and
- specifies where the search of files in any form (e.g.,
- directories, links, etc.) will take place in. If
- <replaceable>LOCATION</replaceable> isn't a directory, the
- script finishes its execution with an error message.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- The <function>cli_getFilesList</function> accepts the
- following options:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><option>--pattern="<replaceable>REGEX</replaceable>"</option></term>
- <listitem>
- <para>
- This option specifies a posix-egrep type regular expression as
- value. This regular expression is applied to path specified in
- <replaceable>LOCATION</replaceable> argument. Only file paths
- that match this regular expression inside
- <replaceable>LOCATION</replaceable> directory will be included
- in the final list of files. By default, if this option is not
- provided, the
- <quote><literal>^/.*[[:alnum:]_/-]+$</literal></quote> regular
- expression is used.
- </para>
- <para>
- When you use the <function>cli_getFilesList</function> you
- don't need to specified the absolute path of files you want to
- look for. This is something
- <function>cli_getFilesList</function> already does for you.
- When you use this function, the value you pass as regular
- expression isn't the final regular expression used. Instead,
- the regular expression you pass is used to build the final
- regular expression passed to <command>find</command> command.
- The final regular expression passed to find is
- <quote><literal>^/.*${PATTERN}$</literal></quote>, where
- <literal>${PATTERN}</literal> is the value you passed to
- <option>--pattern</option> option as
- <replaceable>REGEX</replaceable>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--mindepth="<replaceable>NUMBER</replaceable>"</option></term>
- <listitem>
- <para>
- This option specifies the minimal
- <replaceable>NUMBER</replaceable> of levels deep the search
- should go under the directory
- <replaceable>LOCATION</replaceable> specified. For example, if
- you specify <option>--mindepth="2"</option> the search will
- start two levels deep considering the path provided as
- section.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--maxdepth="<replaceable>NUMBER</replaceable>"</option></term>
- <listitem>
- <para>
- This option specifies the maximum
- <replaceable>NUMBER</replaceable> of levels deep the search
- should go under the directory
- <replaceable>LOCATION</replaceable> specified. For example, if
- you specify <option>--maxdepth="2"</option> the search will
- begin in the very same directory path you provided as
- <replaceable>LOCATION</replaceable> and stop two levels deep
- using it as section.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--type="<replaceable>STRING</replaceable>"</option></term>
- <listitem>
- <para>
- This option specifies the type of files being searched. This
- option accepts the same values the <command>find</command>
- <option>-type</option> option does. However, the following
- <replaceable>STRING</replaceable> values are the most used
- inside the script so far:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- d — directory.
- </para>
- </listitem>
- <listitem>
- <para>
- f — regular file.
- </para>
- </listitem>
- </itemizedlist>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--uid="<replaceable>NUMBER</replaceable>"</option></term>
- <listitem>
- <para>
- This option specifies the numeric user id of the files you
- want to search. Only files that match this numeric user id
- will be added to the final list of files.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- Use the <function>cli_getFilesList</function> whenever you
- need to build list of files for further processing.
- </para>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
- <cmdsynopsis>
- <command id="cli_getPathComponent" xreflabel="cli_getPathComponent">cli_getPathComponent
- <indexterm type="common-function" zone="cli_getPathComponent">
- <primary>cli_getPathComponent</primary>
- </indexterm>
- </command>
- <arg>--release</arg>
- <arg>--release-major</arg>
- <arg>--release-minor</arg>
- <arg>--release-pattern</arg>
- <arg>--architecture</arg>
- <arg>--architecture-pattern</arg>
- <arg>--motif</arg>
- <arg>--motif-name</arg>
- <arg>--motif-release</arg>
- <arg>--motif-pattern</arg>
- <arg choice="req"><replaceable>PATH</replaceable></arg>
- </cmdsynopsis>
- </term>
- <listitem>
- <para>
- ...
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
- <cmdsynopsis>
- <command id="cli_synchronizeRepoChanges" xreflabel="cli_synchronizeRepoChanges">cli_synchronizeRepoChanges
- <indexterm type="common-function" zone="cli_synchronizeRepoChanges">
- <primary>cli_syncronizeRepoChanges</primary>
- </indexterm>
- </command>
- <arg choice="req"><replaceable>LOCATION</replaceable></arg>
- </cmdsynopsis>
- </term>
- <listitem>
- <para>
- The <function>cli_synchronizeRepoChanges</function>
- standardizes the way changes are synchronized between the
- working copy and the central repository using
- <replaceable>LOCATION</replaceable> as section. This
- function is the interface we use inside the
- <command>centos-art.sh</command> script to execute the
- <function>Svn</function> functionality described in <xref
- linkend="scripts-bash-vcs" />.
- </para>
- <para>
- Use <function>cli_synchronizeRepoChanges</function> function
- inside the <command>centos-art.sh</command> script whenever
- you need to synchronize one or more changes at any
- <replaceable>LOCATION</replaceable> inside the working copy.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
- <cmdsynopsis>
- <command id="cli_printMessage" xreflabel="cli_printMessage">cli_printMessage
- <indexterm type="common-function" zone="cli_printMessage">
- <primary>cli_printMessage</primary>
- </indexterm>
- </command>
- <arg choice="req"><replaceable>MESSAGE</replaceable></arg>
- <group choice="opt">
- <arg>--as-separator-line</arg>
- <arg>--as-banner-line</arg>
- <arg>--as-cropping-line</arg>
- <arg>--as-tuningup-line</arg>
- <arg>--as-checking-line</arg>
- <arg>--as-combining-line</arg>
- <arg>--as-creating-line</arg>
- <arg>--as-reading-line</arg>
- <arg>--as-savedas-line</arg>
- <arg>--as-linkto-line</arg>
- <arg>--as-movedto-line</arg>
- <arg>--as-validating-line</arg>
- <arg>--as-template-line</arg>
- <arg>--as-configuration-line</arg>
- <arg>--as-palette-line</arg>
- <arg>--as-reponse-line</arg>
- <arg>--as-request-line</arg>
- <arg>--as-selection-line</arg>
- <arg>--as-error-line</arg>
- <arg>--as-toknowmore-line</arg>
- <arg>--as-yesornorequest-line</arg>
- <arg>--as-notrailingnew-line</arg>
- <arg>--as-stdout-line</arg>
- <arg>--as-stderr-line</arg>
- </group>
- </cmdsynopsis>
- </term>
- <listitem>
- <para>
- The <function>cli_printMessage</function> function
- standardizes the way centos-ar.sh scirpt prints messages. By
- default, centos-art.sh script prints all messages to the
- standard output with the exception of those messages printed
- with the <option>--as-stderr-line</option> option, which are
- printed to standard error output instead.
- </para>
-
- <para>
- The <function>cli_printMessage</function> function requires
- two arguments. The first argument specifies the
- <replaceable>MESSAGE</replaceable> you want to print and the
- second argument specifies the FORMAT you'll use to print that
- message. Because this function is so used inside the
- centos-art.sh script, it is convenient to provide localization
- to strings passed as <replaceable>MESSAGE</replaceable> using
- <command>gettext</command> contructions when they aren't
- paths.
- </para>
-
- <para>
- The <function>cli_printMessage</function> function accepts the
- following formats as second argument:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><option>--as-separator-line</option></term>
- <listitem>
- <para>
- This format takes the first character passed as
- <replaceable>MESSAGE</replaceable> and repeats it horizontally
- to build a separator line. Use this format whenever you need
- to create a logical separation between different actions.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--as-banner-line</option></term>
- <listitem>
- <para>
- This format takes the string passed as
- <replaceable>MESSAGE</replaceable> and puts it inside two
- horizontal separator lines. Use this format whenever you need
- to print header information for following lines.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--as-cropping-line</option></term>
- <listitem>
- <para>
- This format is for two columns messages where
- <replaceable>MESSAGE</replaceable> generally refers to a file
- inside the repository. Use this format whenever you need to
- imply the fact that certain file has been cropped.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--as-tuningup-line</option></term>
- <listitem>
- <para>
- This format is for two columns messages where
- <replaceable>MESSAGE</replaceable>
- generally refers to a file inside the repository. Use this
- format whenever you need to imply the fact that certain file
- has been tuned-up.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-checking-line</option></term>
- <listitem>
- <para>
- This format is for two columns messages where
- <replaceable>MESSAGE</replaceable> generally refers to a file
- inside the repository. Use this format whenever you need to
- imply the fact that certain file has been checked or verified
- (e.g., through <function>cli_checkFiles</function>
- functionality).
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-combining-line</option></term>
- <listitem>
- <para>
- This format is for two columns messages where
- <replaceable>MESSAGE</replaceable> generally refers to a file
- inside the repository. Use this format whenever you need to
- imply the fact that certain file has been combined.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-creating-line</option></term>
- <listitem>
- <para>
- This format is for two columns messages where
- <replaceable>MESSAGE</replaceable> generally refers to a file
- inside the repository. Use this format whenever you need to
- imply the fact that certain file has been created.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-reading-line</option></term>
- <listitem>
- <para>
- This format is for two columns messages where
- <replaceable>MESSAGE</replaceable> generally refers to a file
- inside the repository. Use this format whenever you need to
- imply the fact that certain file has been read.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-savedas-line</option></term>
- <listitem>
- <para>
- This format is for two columns messages where
- <replaceable>MESSAGE</replaceable> generally refers to a file
- inside the repository. Use this format whenever you need to
- imply the fact that certain file has been saved.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-linkto-line</option></term>
- <listitem>
- <para>
- This format is for two columns messages where
- <replaceable>MESSAGE</replaceable> generally refers to a file
- inside the repository. Use this format whenever you need to
- imply the fact that certain file has been linked.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-movedto-line</option></term>
- <listitem>
- <para>
- This format is for two columns messages where
- <replaceable>MESSAGE</replaceable> generally refers to a file
- inside the repository. Use this format whenever you need to
- imply the fact that certain file has been moved.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-validating-line</option></term>
- <listitem>
- <para>
- This format is for two columns messages where
- <replaceable>MESSAGE</replaceable> generally refers to a file
- inside the repository. Use this format whenever you need to
- imply the fact that certain file has been validated.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-template-line</option></term>
- <listitem>
- <para>
- This format is for two columns messages where
- <replaceable>MESSAGE</replaceable> generally refers to a file
- inside the repository. Use this format whenever you need to
- imply the fact that certain file is a template or design
- model.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-configuration-line</option></term>
- <listitem>
- <para>
- This format is for two columns messages where
- <replaceable>MESSAGE</replaceable> generally refers to a file
- inside the repository. Use this format whenever you need to
- imply the fact that certain file is a configuration file.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-palette-line</option></term>
- <listitem>
- <para>
- This format is for two columns messages where
- <replaceable>MESSAGE</replaceable> generally refers to a file
- inside the repository. Use this format whenever you need to
- imply the fact that certain file is a palette of colors.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-response-line</option></term>
- <listitem>
- <para>
- This format adds <literal>--></literal> at the begining of the
- string passed as <replaceable>MESSAGE</replaceable>. Use this
- format whenever you need to imply the fact that certain file
- is considered part of a response. For example, when you need
- to express that a group of files will take ceratin action, you
- can use this option to doing so.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-request-line</option></term>
- <listitem>
- <para>
- This format prints <replaceable>MESSAGE</replaceable> without
- trailing new line. Use this format whenever you need to imply
- a question or yes or no request.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-selection-line</option></term>
- <listitem>
- <para>
- This format uses each word in
- <replaceable>MESSAGE</replaceable> as item of a selection
- list. Use this format whenever you need to select one of the
- items provided as <replaceable>MESSAGE</replaceable>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-error-line</option></term>
- <listitem>
- <para>
- This format prints error messages produced by centos-art.sh
- script. It uses the <command>caller</command> built-in command
- to display the line number and the filename where such error
- was triggered. Later, it prints where to find more information
- by using the <option>--as-toknowmore-line</option> option.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><option>--as-toknowmore-line</option></term>
- <listitem>
- <para>
- This format takes a function name as
- <replaceable>MESSAGE</replaceable> and prints the command you
- can use to find more information about it. When this option is
- passed the script finishes its execution immediately. This
- option is used in combination with
- <option>--as-error-line</option> to finish the script
- execution after an error.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--as-yesornorequest-line</option></term>
- <listitem>
- <para>
- This format takes a question as
- <replaceable>MESSAGE</replaceable> and reads a yes or no
- answer. When answer is negative, the script finishes its
- execution immediately. When answer is affirmative, the script
- continues its execution normally.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--as-notrailingnew-line</option></term>
- <listitem>
- <para>
- Print <replaceable>MESSAGE</replaceable> without any trailing
- newline.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--as-stdout-line</option></term>
- <listitem>
- <para>
- Print <replaceable>MESSAGE</replaceable> to standard output.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--as-stderr-line</option></term>
- <listitem>
- <para>
- Print <replaceable>MESSAGE</replaceable> to standard error
- output.
- </para>
- </listitem>
- </varlistentry>
-
- </variablelist>
- <para>
- Use <function>cli_printMessage</function> function whenever
- you need to print information inside the
- <command>centos-art.sh</command> script.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
- <cmdsynopsis>
- <command id="cli_unsetFunctions" xreflabel="cli_unsetFunctions">cli_unsetFunctions
- <indexterm type="common-function" zone="cli_unsetFunctions">
- <primary>cli_unsetFunctions</primary>
- </indexterm>
- </command>
- <arg choice="req"><replaceable>EXPORTID</replaceable></arg>
- </cmdsynopsis>
- </term>
- <listitem>
- <para>
- ...
- </para>
- <para>
- See also: <xref linkend="cli_exportFunctions" />
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
- <cmdsynopsis>
- <command id="cli_getTemporalFile" xreflabel="cli_getTemporalFile">cli_getTemporalFile
- <indexterm type="common-function" zone="cli_unsetFunctions">
- <primary>cli_unsetFunctions</primary>
- </indexterm>
- </command>
- <arg choice="req"><replaceable>FILENAME</replaceable></arg>
- </cmdsynopsis>
- </term>
- <listitem>
- <para>
- ...
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>...</term>
- <listitem>
- <para>
- ...
- </para>
- </listitem>
- </varlistentry>
-
- </variablelist>
-
-</sect1>
-
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/help.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/help.docbook
deleted file mode 100644
index 8855021..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/help.docbook
+++ /dev/null
@@ -1,754 +0,0 @@
-<refentry id="scripts-bash-help">
-
- <refmeta>
- <refentrytitle>help</refentrytitle>
- <indexterm type="common-function">
- <primary>Standardize constructions tasks inside &TCAR;</primary>
- </indexterm>
- </refmeta>
-
- <refnamediv>
- <refname>help</refname>
- <refpurpose>Standardize documentation tasks inside &TCAR;.</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
- <cmdsynopsis>
- <command>centos-art help</command>
- <arg choice="opt">
- <arg>-h|--help</arg>
- <arg>-q|--quiet</arg>
- <arg>--answer-yes</arg>
- <arg>--synchronize</arg>
- <arg>--format="<replaceable>KEYWORD</replaceable>"</arg>
- <arg>--search="<replaceable>KEYWORD</replaceable>"</arg>
- <arg>--edit</arg>
- <arg>--read</arg>
- <arg>--update-output</arg>
- <arg>--update-structure</arg>
- <arg>--copy</arg>
- <arg>--delete</arg>
- <arg>--rename</arg>
- </arg>
- <group choice="req">
- <arg rep="repeat"><replaceable>MANUAL</replaceable>:<replaceable>PART</replaceable>:<replaceable>CHAPTER</replaceable>:<replaceable>SECTION</replaceable></arg>
- <arg rep="repeat"><replaceable>LOCATION</replaceable></arg>
- </group>
- </cmdsynopsis>
-
- </refsynopsisdiv>
-
- <refsection id="scripts-bash-help-description">
- <title>Description</title>
-
- <para>
- The <function>help</function> functionality exists to create
- and maintain documentation manuals inside &TCAR;.
- </para>
-
- <refsection id="scripts-bash-help-description-docentry">
- <title>Documentation Entries</title>
- <para>
- The documentation entry identifies the specific file you want
- to work with inside a documentation manual. The help
- functionality recognizes documentation entries in the
- following formats:
- </para>
- <variablelist>
- <varlistentry>
- <term>Path style</term>
- <listitem>
- <para>
- This format uses paths to represent the documentation entries
- you want to work with. This format assumes you are using the
- first path component as chapter and the rest of the path as
- section identifier both inside <quote>tcar-fs</quote>
- documentation manual as parent documentation structure. The
- field related to the part sectioning structure in the
- documentation entry (the second field) is assumed empty, as
- well. For example, if you want to document the directory
- <quote><filename
- class="directory">Scripts/Bash/Functions/Help</filename></quote>,
- then you can do it with the following command:
- </para>
-
- <cmdsynopsis>
- <command>centos-art help --edit Scripts/Bash/Functions/Help</command>
- </cmdsynopsis>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Colon style</term>
- <listitem>
- <para>
- This format uses colons to represent the documentation entries
- you want to work with. In this format, the whole documentation
- entry is divided in fields using colon as separator character.
- Documentation entries written this way use each field to
- specify manual, part, chapter and section identifiers (in this
- order). The section identifier can use a path style or hyphen
- style to separate
- components. For example, if you want to document the directory
- <quote><filename
- class="directory">Scripts/Bash/Functions/Help</filename></quote>,
- then you can do it with any of the following commands:
- </para>
-
- <cmdsynopsis>
- <command>centos-art help --edit tcar-fs::trunk:Scripts/Bash/Functions/Help</command>
- <command>centos-art help --edit tcar-fs::trunk:scripts-bash-functions-help</command>
- </cmdsynopsis>
-
- <para>
- The documentation manual name specified in the first field of
- a colon style documentation entry, must match the name the
- name of the directory where the documentation manual is stored
- in. By default documentation manuals are written in
- Documentation/Models/Texinfo or
- Documentation/Models/Docbook directories, based on
- whether they are written in Texinfo or Docbook documentation
- format.
- </para>
- <para>
- The match relation between the manual name you provide in the
- documentation entry and the related directory name inside
- &TCAR; is case insensitive. The same is true for all other
- documentation entry fields.
- </para>
-
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- From these documentation entry formats, the colon style
- provides more flexibility than path style does. You can use
- documentation entries written in colon style to create and
- maintain different documentation manuals, including the
- <quote>tcar-fs</quote> documentation manual. This is something
- you cannot do with documentation entries written in path style
- because they confine all documentation actions to
- <quote>tcar-fs</quote> documentation manual.
- </para>
- </refsection>
-
- </refsection>
-
- <refsection id="scripts-bash-help-options">
- <title>Options</title>
- <para>
- The <command>centos-art help</command> command accepts common
- options described in <xref
- linkend="scripts-bash-cliref-options" /> and the following
- specific options:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><option>--answer-yes</option></term>
- <listitem>
- <para>
- Assume <emphasis>yes</emphasis> to all confirmation requests.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--synchronize</option></term>
- <listitem>
- <para>
- Synchronizes available changes between the working copy and
- the central repository.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--format="<replaceable>KEYWORD</replaceable>"</option></term>
- <listitem>
- <para>
- Specifies the format of documentation entry source file. This
- information is used as reference to build the absolute path of
- documentation entry, so you always have to provide it in order
- to reach the documentation entry you want to work with.
- Possible values for this option are shown in <xref
- linkend="scripts-bash-help-supportedformats" />. When none of
- these values is passed as format, Texinfo is used as default
- format.
- </para>
-
- <table id="scripts-bash-help-supportedformats">
- <title>Documentation formats</title>
- <tgroup cols="3" align="left">
- <thead>
- <row>
- <entry>Keyword</entry>
- <entry>Description</entry>
- <entry>Supported</entry>
- </row>
- </thead>
-
- <tbody>
- <row>
- <entry><literal>texinfo</literal></entry>
- <entry><xref linkend="manuals-formats-texinfo"/></entry>
- <entry>Yes</entry>
- </row>
- <row>
- <entry><literal>docbook</literal></entry>
- <entry><xref linkend="manuals-formats-docbook"/></entry>
- <entry>No</entry>
- </row>
- <row>
- <entry><literal>latex</literal></entry>
- <entry><xref linkend="manuals-formats-latex"/></entry>
- <entry>No</entry>
- </row>
- <row>
- <entry><literal>linuxdoc</literal></entry>
- <entry>...</entry>
- <entry>No</entry>
- </row>
- </tbody>
-
- </tgroup>
- </table>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--search="<replaceable>KEYWORD</replaceable>"</option></term>
- <listitem>
- <para>
- Looks for documentation entries that match the
- <replaceable>KEYWORD</replaceable> specified as value and
- display them one by one in the order they were found. The way
- each documentation entry is presented to you depends on the
- documentation format the related documentation manual was
- written on.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--edit</option></term>
- <listitem>
- <para>
- Edit the documentation entry provided as argument. The
- edition itself takes place through your default text editor
- (e.g., the one you specified in the <envar>EDITOR</envar>
- environment variable) one file at a time (i.e., the queue of
- files to edit is not loaded in the text editor.).
- </para>
- <para>
- When parent components inside documentation entries doesn't
- exist (e.g., you try to create a section for a documentation
- manual that doesn't exist), the <function>help</function>
- functionality will create all documentation parent structures
- considering the documentation format constraints and the
- following document structure hierarchy order: documentation
- <quote>manual</quote> first, <quote>parts</quote> second,
- <quote>chapters</quote> third and <quote>sections</quote>
- lastly.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--read</option></term>
- <listitem>
- <para>
- Read the documentation entry provided as argument. This
- option is used internally by <command>centos-art.sh</command>
- script to refer documentation based on errors, so you can know
- more about them and the causes that could have provoked them.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--update-output</option></term>
- <listitem>
- <para>
- Update output files rexporting them from the specified backend
- source files.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--update-structure</option></term>
- <listitem>
- <para>
- Update document structure (e.g., cross references, menus,
- nodes, etc.) and should be passed with a section as
- documentation entry.
- </para>
- <para>
- This option should be used whenever a document structure
- changes (e.g., documentation entries are added, copied,
- renamed, deleted, etc.). This option grantees the document
- integrity and should be run before updating documentation
- manual final output files.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--copy</option></term>
- <listitem>
- <para>
- Duplicate documentation entries inside the working copy using
- version control.
- </para>
- <para>
- When you duplicate documentation entries through this option,
- you should pass only two documentation entries in the command
- line. The first one is considered the source location and
- should point to a file under version control inside the
- working copy. The second one is considered the target location
- and should point either to the same structural level the
- source points to or a direct parent level based on source
- location, as described below.
- </para>
-
- <variablelist>
- <varlistentry>
- <term>
- "<replaceable>manual:part:chapter:section1</replaceable>" "<replaceable>manual:part:chapter:section2</replaceable>"</term>
- <listitem>
- <para>
- Duplicates <replaceable>section1</replaceable> as
- <replaceable>section2</replaceable> inside the same
- <replaceable>chapter</replaceable>,
- <replaceable>part</replaceable> and
- <replaceable>manual</replaceable>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
- "<replaceable>manual:part:chapter1:</replaceable>" "<replaceable>manual:part:chapter2:</replaceable>"</term>
- <listitem>
- <para>
- Duplicates <replaceable>chapter1</replaceable> as
- <replaceable>chapter2</replaceable> inside the same
- <replaceable>part</replaceable> and
- <replaceable>manual</replaceable>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
- "<replaceable>manual:part1::</replaceable>" "<replaceable>manual:part2::</replaceable>"</term>
- <listitem>
- <para>
- Duplicates <replaceable>part1</replaceable> as
- <replaceable>part2</replaceable> inside the same
- <replaceable>manual</replaceable>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>
- "<replaceable>manual1:::</replaceable>" "<replaceable>manual2:::</replaceable>"</term>
- <listitem>
- <para>
- Duplicates <replaceable>manual1</replaceable> as
- <replaceable>manual2</replaceable> inside <filename
- class="directory">Documentation/Models/${FLAG_FORMAT}/</filename>
- directory, where ${FLAG_FORMAT} is the name of the format
- passed as option with the first letter in uppercase and the
- rest in lowercase.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- When you copy documentation entries through this option, all
- structuring sections inside the one copied will be also
- copied. For example, if you copy a documentation manual that
- is made of parts, chapters and sections, the duplicated manual
- will contain all those parts, chapters and sections, as well.
- The same is true for lower sectioning structures. Thus, you
- can be more specific in the documentation entry by reducing
- the amount of content to duplicate.
- </para>
-
- <para>
- When you copy documentation entries through this option, you
- do it using documentation entries in the same structural level
- only. This option doesn't support copying documentation
- entries from differnet structural levels. For example, you
- cannot copy one section to a chapter different from that the
- source section you specified belongs to. The same applies to
- chapters, and parts.
- </para>
-
- <para>
- When you copy documentation entries through this option, the
- source documentation entry you specify must not contain
- pending changes. Otherwise, the target section won't be
- created and the script will immediatly stop its execution with
- a <quote>The source location has pending changes.</quote>
- error message.
- </para>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--delete</option></term>
- <listitem>
- <para>
- Delete documentation entries. It is possible to delete more
- than one documentation entry by specifying several
- documentation entries in the command line.
- </para>
- <para>
- When you delete documentation entries, you can pass any number
- of documentation entries as argument. The documentation
- entries you provide will be processed one by one.
- </para>
- <para>
- When you delete a documentation entry from a documentation
- manual, all cross references pointing to the deleted
- documentation entry will be transformed into something
- different to point out the fact that the related documentation
- entry has been removed from the documentation manual and
- restored back if you create the deleted section again. The
- purpose of this is to keep the documentation manual structure
- in a consistent state.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--rename</option></term>
- <listitem>
- <para>
- Rename documentation entries inside the working copy. This
- option copies the source documentation entry to its target
- location, removes the source documentation entry, and restores
- removed cross references renaming them to point the specified
- target documentation entry.
- </para>
- <para>
- When you rename documentation entries, it is required to pass
- only two non-option parameters to the command-line. The first
- non-option parameter is considered the source location and the
- second one the target location. Both source location and
- target location must point to a directory under version
- control inside the working copy.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- </refsection>
-
- <refsection id="scripts-bash-help-examples">
- <title>Examples</title>
-
- <para>
- This section describes, using examples, the procedure you
- should follow to manage documentation manuals through
- <function>help</function> functionality inside &TCAR;. To
- better understand the procedure to follow, it describes a
- hypothetical documentation scenario and the related commands
- and outputs you may go through in order to complete specific
- documentation tasks successfully.
- </para>
-
- <refsection id="scripts-bash-help-description-create">
- <title>Creating Document Structures</title>
- <para>
- To create new documentation manuals inside &TCAR; you need to
- provide both <option>--edit</option> and
- <option>--format</option> options as well as a documentation
- entry in the form <quote><literal>manual:::</literal></quote>
- to the <function>help</function> functionality.
- </para>
-
- <para>
- For example, consider a scenario where you need to create a
- documentation manual in texinfo format to describe different
- maintenance tasks you need to realized in order to keep your
- pets happy. We'll name such manual <quote>My Zoo</quote>. It
- will use chapters to organize each different kind of pets you
- have. Inside chapters, sections will have the pet's name as
- their own name to describe each pet's requirements, schedules,
- and so on. To create such documentation manual, run the
- following command:
- </para>
-
- <cmdsynopsis>
- <command>centos-art help --edit --format="texinfo" "myzoo:::"</command>
- </cmdsynopsis>
-
- <para>
- In case such documentation manual doesn't exist in the
- <filename
- class="directory">Docuementation/Models/Texinfo/</filename>
- directory, this command will produce the following output:
- </para>
-
-<programlisting>
-The following documentation manual doesn't exist:
---> Documentation/Models/Texinfo/Myzoo/en_US/myzoo.texinfo
-Do you want to create it now? [yes/no]: yes
-Enter manual's title: My Zoo
-Enter manual's subtitle: Reference
-Enter manual's abstract: This manual describes my zoo maintenance tasks.
-Creating Documentation/Models/Texinfo/Myzoo
-Creating Documentation/Models/Texinfo/Myzoo/en_US
-Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo.conf
-Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-index.texinfo
-Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-menu.texinfo
-Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-nodes.texinfo
-Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo.texinfo
-Creating Documentation/Models/Texinfo/Myzoo/en_US/Licenses/chapter-menu.texinfo
-Creating Documentation/Models/Texinfo/Myzoo/en_US/Licenses/chapter-nodes.texinfo
-Creating Documentation/Models/Texinfo/Myzoo/en_US/Licenses/chapter.texinfo
-Updating Documentation/Models/Texinfo/Myzoo/en_US/myzoo.texinfo
-Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2
-Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2
-Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml
-Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook
-Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf
-Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2
-</programlisting>
-
- <para>
- Once the documentation structure has been created this way,
- the recently created documentation manual is ready to receive
- new sectioning levels (e.g., parts, chapters, sections, etc.).
- For example, to create a new chapter named
- <quote>Turtles</quote> inside <quote>My Zoo</quote>
- documentation manual, run the following command:
- </para>
-
- <cmdsynopsis>
- <command>centos-art help --edit --format="texinfo" "myzoo::turtles:"</command>
- </cmdsynopsis>
-
-<programlisting>
-The following documentation chapter doesn't exist:
---> Documentation/Models/Texinfo/Myzoo/en_US/Turtles
-Do you want to create it now? [yes/no]: yes
-Enter chapter's title: Turtles
-Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles
-Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter-menu.texinfo
-Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter-nodes.texinfo
-Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter.texinfo
-Updating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-menu.texinfo
-Updating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-nodes.texinfo
-Updating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter.texinfo
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2
-</programlisting>
-
- <para>
- Once chapters have been created it is possible to create
- sections inside them. For example, if you want to create a
- section for describing the life of a turtle named Longneck,
- run the following command:
- </para>
-
- <cmdsynopsis>
- <command>centos-art help --edit --format="texinfo" "myzoo::turtles:longneck"</command>
- </cmdsynopsis>
-
-<programlisting>
-The following documentation section doesn't exist:
---> Documentation/Models/Texinfo/Myzoo/en_US/Turtles/longneck.texinfo
-Do you want to create it now? [yes/no]: yes
-Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/longneck.texinfo
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2
-</programlisting>
-
- </refsection>
-
- <refsection id="scripts-bash-help-description-edit">
- <title>Editing Document Structures</title>
- <para>
- To edit documentation entries you can follow the same
- procedure described above. Just keep in mind the following
- rules:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- When the entry you want to edit already exist it will be
- edited.
- </para>
- </listitem>
-
- <listitem>
- <para>
- When the entry you want to edit doesn't exist it will be created
- first and edited later.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </refsection>
-
- <refsection id="scripts-bash-help-description-copy">
- <title>Copying Document Structures</title>
- <para>
- Consider a new turtle named Slowfeet has arrived to your home
- and you want to duplicate Longneck's section for it (they both
- are turtles and have similar requirements, squedules, etc.).
- To copy documentation entries you use the
- <option>--copy</option> option with two documentation entries,
- where the first one is the source location and the second one
- the target location. To do this, run the following command:
- </para>
-
- <cmdsynopsis>
- <command>centos-art help --copy --format="texinfo" "myzoo::turtles:longneck" "myzoo::turtles:slowfeet"</command>
- </cmdsynopsis>
-
-<programlisting>
-Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/slowfeet.texinfo
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf
-Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2
-</programlisting>
-
- </refsection>
-
- <refsection id="scripts-bash-help-description-rename">
- <title>Renaming Document Structures</title>
- <para>
- Consider you've created the section of Longneck turtle using
- the following documentation entry format
- <quote>myzoo::turtles:longnek</quote>, but you didn't notice
- the typo in it. You've made cross references to the misspelled
- section in a few pages inside the <quote>My Zoo</quote>
- documentation manual and some time later you realize the
- section name has a spelling problem. To fix such a problem
- you can rename the misspelled section with the correct one
- running the following command:
- </para>
-
- <cmdsynopsis>
- <command>centos-art help --rename --format="texinfo" "myzoo::turtles:longnek" "myzoo::turtles:longneck"</command>
- </cmdsynopsis>
-
-<programlisting>
-Creating Documentation/Models/Texinfo/MyZoo/en_US/Turtles/longneck.texinfo
-Deleting Documentation/Models/Texinfo/MyZoo/en_US/Turtles/longnek.texinfo
-Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.info.bz2
-Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xhtml.tar.bz2
-Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xml
-Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.docbook
-Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.pdf
-Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.txt.bz2
-</programlisting>
-
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-help-description-delete">
- <title>Deleting Document Structures</title>
- <para>
- Consider you gift the turtle named Longneck to a friend and
- you want to delete its section from the <quote>My Zoo</quote>
- documentation manual. To do so, run the following command:
- </para>
- <cmdsynopsis>
- <command>centos-art help --delete --format="texinfo" "myzoo::turtles:longneck"</command>
- </cmdsynopsis>
-<programlisting>
-Deleting Documentation/Models/Texinfo/Myzoo/en_US/Turtles/longneck.texinfo
-Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.info.bz2
-Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xhtml.tar.bz2
-Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xml
-Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.docbook
-Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.pdf
-Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.txt.bz2
-</programlisting>
-
- </refsection>
-
- </refsection>
-
- <refsection id="scripts-bash-help-bugs">
- <title>Bugs</title>
- <para>
- To report bugs related to this function, please create a new
- ticket <ulink
- url="https://projects.centos.org/trac/artwork/newticket?summary=Error%20Standardizing%20Documentation%20Tasks&component=Scripts">here</ulink>
- refering the specific problems you found in it. For example,
- it would be useful if you copy and paste any error output from
- <command>centos-art.sh</command> script.
- </para>
- </refsection>
-
- <refsection id="scripts-bash-help-authors">
- <title>Authors</title>
- <para>
- The following people have worked in this functionality:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Alain Reguera Delgado <<ulink url="mailto:alain.reguera@gmail.com">alain.reguera@gmail.com</ulink>>, =COPYRIGHT_YEAR_LIST=
- </para>
- </listitem>
- </itemizedlist>
- </refsection>
-
- <refsection id="scripts-bash-help-licence">
- <title>License</title>
-
- <para>
- Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
- </refsection>
-
-</refentry>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/intro.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/intro.docbook
deleted file mode 100644
index bf64c16..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/intro.docbook
+++ /dev/null
@@ -1,6 +0,0 @@
-<para>
- This reference covers the <command>centos-art.sh</command> script
- mission, name convenctions, command-line interface and execution
- environments. You can use this reference to understand how the
- <command>centos-art.sh</command> script works.
-</para>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/locale.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/locale.docbook
deleted file mode 100644
index 21a37d9..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/locale.docbook
+++ /dev/null
@@ -1,292 +0,0 @@
-<refentry id="scripts-bash-locale">
-
- <refmeta>
- <refentrytitle>locale</refentrytitle>
- <indexterm type="specific-function">
- <primary>Standardize translation tasks inside &TCAR;</primary>
- </indexterm>
- </refmeta>
-
- <refnamediv>
- <refname>locale</refname>
- <refpurpose>Standardize translation tasks inside &TCAR;</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
- <para>
- The <varname>DIRECTORY</varname> parameter specifies the
- directory path, inside the working copy of &TCAR;, where the
- files you want to process are stored in. This paramter can be
- provided more than once in order to process more than one
- directory path in a single command execution. When this
- parameter is not provided, the current directory path where
- the command was called from is used instead.
- </para>
- </refsynopsisdiv>
-
- <refsection id="scripts-bash-locale-options">
- <title>Options</title>
- <para>
- The <function>locale</function> functionality accepts the
- following options:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><option>--quiet</option></term>
- <listitem>
- <para>
- Supress all output messages except error messages. When this
- option is passed, all confirmation requests are supressed and
- a possitive answer is assumed for them, just as if the
- <option>--answer-yes</option> option would have been provided.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--answer-yes</option></term>
- <listitem>
- <para>
- Assume <emphasis>yes</emphasis> to all confirmation requests.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--filter="REGEX"</option></term>
- <listitem>
- <para>
- Reduce the list of files to process inside
- <varname>DIRECTORY</varname> using <varname>REGEX</varname> as
- pattern. You can use this option to control the amount of
- files you want to locale. The deeper you go into the
- directory structure the more specific you'll be about the
- files you want to locale. When you cannot go deeper into the
- directory structure through <varname>DIRECTORY</varname>
- specification, use this option to reduce the list of files
- therein.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--synchronize</option></term>
- <listitem>
- <para>
- Synchronizes available changes between the working copy and
- the central repository.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--update</option></term>
- <listitem>
- <para>
- This option updates both POT and PO files related to source
- files. Use this option everytime you change translatable
- strings inside the source files.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--edit</option></term>
- <listitem>
- <para>
- This option edits the portable object related to source files.
- When you provide this option, your default text editor is used
- to open the portable object you, as translator, need to change
- in order to keep source file messages consistent with their
- localized versions. In the very specific case of shell
- scripts localization, this option takes care of updating the
- machine object (MO) file the shell script requires to
- displayed translation messages correctly when it is executed.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--delete</option></term>
- <listitem>
- <para>
- This option unlocalizes source files. When you provide this
- option, the localization directory related to source files is
- removed from the working copy in conjunction with all portable
- objects and machine objects inside it.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--dont-create-mo</option></term>
- <listitem>
- <para>
- This option suppresses machine objects creation when shell
- scripts are localized.
- </para>
- </listitem>
- </varlistentry>
-
- </variablelist>
- </refsection>
-
- <refsection id="scripts-bash-locale-description">
- <title>Description</title>
-
- <para>
- The localization process is very tied to the source files we
- want to provide localized messages for. Inside the working
- copy of &TCAR; it is possible to localize XML-based files
- (e.g., SVG and Docbook) and programs written in most popular
- programming languages (e.g., C, C++, C#, Shell Scripts,
- Python, Java, GNU awk, PHP, etc.).
- </para>
-
- <para>
- The localization process initiates by retriving translatable
- strings from source files. When source files are XML-based
- files, the only requisite to retrive translatable strings
- correctly is that they be well-formed. Beyond that, the
- <command>xml2po</command> command takes care of everything
- else. When source files are Shell script files, it is
- necessary that you previously define what strings inside the
- script are considered as translatable strings in order for
- <command>xgettext</command> command to retrive them correctly.
- To define translatable strings inside shell scripts, you need
- to use either <command>gettext</command>,
- <command>ngettext</command>, <command>eval_gettext</command>
- or <command>eval_ngettext</command> command as it is following
- described:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- Use the <command>gettext</command> command to display the
- native language translation of a textual message.
- </para>
- <screen>MESSAGE="`gettext "There is no entry to create."`"</screen>
- </listitem>
-
- <listitem>
- <para>
- Use the <command>ngettext</command> command to display the
- native language translation of a textual message whose
- grammatical form depends on a number.
- </para>
- <screen>MESSAGE="`ngettext "The following entry will be created" \
- "The following entries will be created" \
- $COUNT`:"</screen>
- </listitem>
-
- <listitem>
- <para>
- Use the <command>eval_gettext</command> command to display the
- native language translation of a textual message, performing
- dollar-substitution on the result. Note that only shell
- variables mentioned in the message will be dollar-substituted
- in the result.
- </para>
- <screen>MESSAGE="`eval_gettext "The location \\\"\\\$LOCATION\\\" is not valid."`"</screen>
- </listitem>
-
- <listitem>
- <para>
- Use the <command>eval_ngettext</command> command to display
- the native language translation of a textual message whose
- grammatical form depends on a number, performing
- dollar-substitution on the result. Note that only shell
- variables mentioned in messages will be dollar-substituted in
- the result.
- </para>
- <screen>MESSAGE="`eval_ngettext "The following entry will be created in \\\$LOCATION" \
- "The following entries will be created in \\\$LOCATION" \
- $COUNT`:"</screen>
- </listitem>
- </itemizedlist>
-
- <para>
- Once translatable strings are retrived, a portable object
- template (POT) file is created for storing them. Later, the
- POT file is used to create a portable object (PO). The
- portable object is the place where localization itself takes
- place, it is the file translators edit to localize messages.
- When translatable strings change inside source files, it is
- necessary that you update these POT and PO files in order to
- keep consistency between source file messages and their
- localized versions.
- </para>
-
- <para>
- Inside source files, translatable strings are always written
- in English language. In order to localize translatable strings
- from English language to another language, you need to be sure
- the <envar>LANG</envar> environment variable has been already
- set to the locale code you want to localize message for or see
- them printed out before running the
- <function>locale</function> functionality of
- <command>centos-art.sh</command> script. Localizing English
- language to itself is not supported.
- </para>
-
- <para>
- To have a list of all locale codes you can have localized
- messages for, run the following command: <command>locale -a |
- less</command>.
- </para>
- </refsection>
-
- <refsection id="scripts-bash-locale-environment">
- <title>Function Specific Environment</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-locale-authors">
- <title>Authors</title>
- <para>
- The following people have worked in the
- <function>locale</function> functionality:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Alain Reguera Delgado <<ulink url="mailto:alain.reguera@gmail.com">alain.reguera@gmail.com</ulink>>, =COPYRIGHT_YEAR_LIST=
- </para>
- </listitem>
- </itemizedlist>
- </refsection>
-
- <refsection id="scripts-bash-locale-licence">
- <title>License</title>
-
- <para>
- Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
- </refsection>
-
-</refentry>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/mission.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/mission.docbook
deleted file mode 100644
index 283781e..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/mission.docbook
+++ /dev/null
@@ -1,9 +0,0 @@
-<sect1 id="scripts-bash-mission">
-<title>Mission</title>
-
-<para>
- The <command>centos-art.sh</command> script exists to automate
- frequent tasks inside &TCAR;.
-</para>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/nameconvs.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/nameconvs.docbook
deleted file mode 100644
index a041b3a..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/nameconvs.docbook
+++ /dev/null
@@ -1,54 +0,0 @@
-<sect1 id="scripts-bash-nameconvs">
-
- <title>Convenctions</title>
-
- <para>
- ...
- </para>
-
- <sect2 id="scripts-bash-nameconvs-vars">
- <title>Variable Names</title>
- <para>
- ...
- </para>
- </sect2>
-
- <sect2 id="scripts-bash-nameconvs-funcs">
- <title>Function Names</title>
- <para>
- ...
- </para>
- </sect2>
-
- <sect2 id="scripts-bash-nameconvs-exitstatus">
- <title>Exit Status</title>
- <para>
- The <command>centos-art.sh</command> script has the following
- exit status:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <code>0</code> — The script completed successfully
- without error.
- </para>
- </listitem>
-
- <listitem>
- <para>
- <code>1</code> — The script didn't complete successfully
- because something went wrong. This error status is generally
- produced by <function>cli_printMessage</function>
- functionality, when you use it with the
- <option>--as-error-line</option> option as second argument.
- </para>
- </listitem>
- </itemizedlist>
-
- <para>
- ...
- </para>
- </sect2>
-
-</sect1>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/pack.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/pack.docbook
deleted file mode 100755
index 01c5937..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/pack.docbook
+++ /dev/null
@@ -1,82 +0,0 @@
-<refentry id="scripts-bash-pack">
-
- <refmeta>
- <refentrytitle>pack</refentrytitle>
- <indexterm type="specific-function">
- <primary>Standardize packing tasks inside &TCAR;</primary>
- </indexterm>
- </refmeta>
-
- <refnamediv>
- <refname>pack</refname>
- <refpurpose>Standardize packing tasks inside &TCAR;</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
- <para>
- ...
- </para>
- </refsynopsisdiv>
-
- <refsection id="scripts-bash-pack-description">
- <title>Description</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-pack-usage">
- <title>Usage</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-pack-environment">
- <title>Function Specific Environment</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-pack-authors">
- <title>Authors</title>
- <itemizedlist>
- <listitem>
- <para>
- ...
- </para>
- </listitem>
- </itemizedlist>
- </refsection>
-
- <refsection id="scripts-bash-pack-licence">
- <title>License</title>
-
- <para>
- Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
- </refsection>
-
-</refentry>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/prepare.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/prepare.docbook
deleted file mode 100644
index 4fb9cf9..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/prepare.docbook
+++ /dev/null
@@ -1,314 +0,0 @@
-<refentry id="scripts-bash-prepare">
-
- <refmeta>
- <refentrytitle>prepare</refentrytitle>
- <indexterm type="specific-function">
- <primary>Standardize configuration tasks inside &TCAR;</primary>
- </indexterm>
- </refmeta>
-
- <refnamediv>
- <refname>prepare</refname>
- <refpurpose>Standardize configuration tasks inside &TCAR;</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
- <para>
- Assuming this is the very first time you run the
- <command>centos-art</command> command, you'll find that there
- isn't such a command in your workstation. This is correct
- because you haven't created the symbolic link that makes it
- available in your execution path, yet. In order to make the
- <command>centos-art</command> command available in the
- execution path of your workstation, you need to run the
- <command>centos-art.sh</command> script using its absolute
- path first:
- </para>
-
- <cmdsynopsis>
- <command>~/artwork/Scripts/Bash/centos-art.sh</command>
- <arg choice="req">prepare</arg>
- <arg>-h|--help</arg>
- <arg>-q|--quiet</arg>
- <arg>--answer-yes</arg>
- <arg>--set-environment</arg>
- <arg>--see-environment</arg>
- <arg>--packages</arg>
- <arg>--locales</arg>
- <arg>--links</arg>
- <arg>--images</arg>
- <arg>--manuals</arg>
- <arg>--synchronize</arg>
- </cmdsynopsis>
-
- <para>
- Later, once the <command>centos-art</command> command is
- available in your execution path, there is no need for you to
- use any absolute path again. From this time on, you can use
- the <command>centos-art</command> command-line interface
- directly, as the following example describes:
- </para>
-
- <cmdsynopsis>
- <command>centos-art</command>
- <arg choice="req">prepare</arg>
- <arg>-h|--help</arg>
- <arg>-q|--quiet</arg>
- <arg>--answer-yes</arg>
- <arg>--set-environment</arg>
- <arg>--see-environment</arg>
- <arg>--packages</arg>
- <arg>--locales</arg>
- <arg>--links</arg>
- <arg>--images</arg>
- <arg>--manuals</arg>
- <arg>--synchronize</arg>
- </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsection>
- <title>Description</title>
- <para>
- The <function>prepare</function> function exists to set
- environment variables, install/update required packages,
- create symbolic links for content reusing, render images based
- on available design models and artistic motifs, render
- documentation manuals, build language-specific files required
- for content localization and anything else needed in order to
- make the working copy of &TCAR; ready to be used.
- </para>
-
- <para>
- When no option is provided to <function>prepare</function>
- functionality, the <command>centos-art.sh</command> script
- uses the <option>--set-environment</option>,
- <option>--packages</option>, <option>--locales</option>
- <option>--links</option>, <option>--images</option> and
- <option>--manuals</option> options, in that order, as default
- behaviour. Otherwise, if you provide any option, the
- <command>centos-art.sh</command> script avoids its default
- behaviour and executes the <function>prepare</function>
- functionality as specified by the options you provided.
- </para>
-
- <para>
- Notice that it is possible for you to execute the
- <function>prepare</function> functionality as many times as
- you need to. This is specially useful when you need to keep
- syncronized the relation between content produced inside your
- working copy and the applications you use outside it. For
- example, considering you've added new brushes to or removed
- old brushes from your working copy of &TCAR;, the link
- information related to those files need to be updated in the
- <filename class="directory">~/.gimp-2.2/brushes</filename>
- directory too, in a way the addition/deletion change that took
- place in your working copy can be reflected there, as well.
- The same is true for other similar components like fonts,
- patterns and palettes.
- </para>
-
- </refsection>
-
- <refsection>
- <title>Usage</title>
- <para>
- Use the <function>prepare</function> functionality the first
- time you download a working copy of &TCAR; or later, to be
- sure your workstation has all the components it needs so you
- can use the working copy of &TCAR; in all its extension.
- </para>
- </refsection>
-
- <refsection id="scripts-bash-prepare-options">
- <title>Options</title>
-
- <para>
- The <command>centos-art prepare</command> command accepts
- common options described in <xref
- linkend="scripts-bash-cliref-options" /> and the following
- specific options:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><option>--answer-yes</option></term>
- <listitem>
- <para>
- Assume <emphasis>yes</emphasis> to all confirmation requests.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--packages</option></term>
- <listitem>
- <para>
- This option verifies packeges required by automation scripts
- and installs or updates them as required. When required
- packages aren't installed or need to be updated, the
- <command>centos-art</command> uses the <command>sudo</command>
- and <command>yum</command> to perform either installations or
- actualizations tasks. In both cases, it is required that you
- configure the <filename>/etc/sudoers</filename> configuration
- file first, as discribed in <xref
- linkend="repo-ws-config-sudoers" />.
- </para>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--locales</option></term>
- <listitem>
- <para>
- This option creates or updates the portable objects (PO) and
- machine object (MO) used by <application>gettext</application>
- to retrive translated strings related to
- <command>centos-art.sh</command> script. This option calls
- the <function>locale</function> functionality of centos-art.sh
- with the <option>--update</option> option, as described in
- <xref linkend="scripts-bash-locale" />.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--links</option></term>
- <listitem>
- <para>
- This option maintains the file relation between your working
- copy and configuration files inside your workstation through
- symbolic links. When you provide this option, the
- <command>centos-art.sh</command> script puts itself into your
- system's execution path through its command line interface
- <command>centos-art</command> and makes common brushes,
- patterns, palettes and fonts inside the working copy,
- available to applications like GIMP in order for you to make
- use of them without loosing version control over them.
- </para>
- <caution>
- <para>
- This option removes all common fonts, brushes, patterns, and
- palettes currently installed in your home directory, in order
- to create a fresh installation of them all again, using the
- working copy as section.
- </para>
- </caution>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--images</option></term>
- <listitem>
- <para>
- This option initializes image files inside the working copy.
- When you provide this option, the
- <command>centos-art.sh</command> calls the
- <function>render</function> functionality to create images
- related to each design model available in your working copy,
- as described in <xref linkend="scripts-bash-render" />.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--manuals</option></term>
- <listitem>
- <para>
- This option initializes documentation files inside the working
- copy. When you provide this option, the
- <command>centos-art.sh</command> script calls both the
- <function>render</function> and <function>help</function>
- functionality to produce DocBook and Texinfo manuals,
- respectively.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--see-environment</option></term>
- <listitem>
- <para>
- Print the name and value of some of the environment variables
- used by <command>centos-art.sh</command> script as described
- in <xref linkend="scripts-bash-environment" />.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--set-environment</option></term>
- <listitem>
- <para>
- Set default environment values to your personal profile
- (<filename>~/.bash_profile</filename>).
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- </refsection>
-
- <refsection id="scripts-bash-prepare-example">
- <title>Examples</title>
- <para>
- None.
- </para>
- </refsection>
-
- <refsection id="scripts-bash-prepare-bugs">
- <title>Bugs</title>
- <para>
- To report bugs related to this function, please create a new
- ticket <ulink
- url="https://projects.centos.org/trac/artwork/newticket?summary=Error%20Standardizing%20Configuration%20Tasks&component=Scripts">here</ulink>
- refering the specific problems you found in it. For example,
- it would be useful if you copy and paste any error output from
- <command>centos-art.sh</command> script.
- </para>
- </refsection>
-
- <refsection id="scripts-bash-prepare-authors">
- <title>Authors</title>
- <para>
- The following people have worked in this functionality:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Alain Reguera Delgado <<ulink url="mailto:alain.reguera@gmail.com">alain.reguera@gmail.com</ulink>>, =COPYRIGHT_YEAR_LIST=
- </para>
- </listitem>
- </itemizedlist>
- </refsection>
-
- <refsection id="scripts-bash-prepare-licence">
- <title>License</title>
-
- <para>
- Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
- </refsection>
-
-</refentry>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/render.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/render.docbook
deleted file mode 100644
index 84826ba..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/render.docbook
+++ /dev/null
@@ -1,435 +0,0 @@
-<refentry id="scripts-bash-render">
-
- <refmeta>
- <refentrytitle>render</refentrytitle>
- <indexterm type="specific-function">
- <primary>Standardize rendition tasks inside &TCAR;.</primary>
- </indexterm>
- </refmeta>
-
- <refnamediv>
- <refname>render</refname>
- <refpurpose>Standardize rendition tasks inside &TCAR;.</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
- <cmdsynopsis>
- <command>centos-art</command>
- <arg choice="req">render</arg>
- <arg>-h|--help</arg>
- <arg>-q|--quiet</arg>
- <arg>--filter="<replaceable>REGEX</replaceable>"</arg>
- <arg>--answer-yes</arg>
- <arg>--dont-dirspecific</arg>
- <arg>--releasever="<replaceable>RELEASEVER</replaceable>"</arg>
- <arg>--basearch="<replaceable>BASEARCH</replaceable>"</arg>
- <arg>--post-rendition="<replaceable>COMMAND</replaceable>"</arg>
- <arg>--last-rendition="<replaceable>COMMAND</replaceable>"</arg>
- <arg>--theme-model="<replaceable>MODELNAME</replaceable>"</arg>
- <arg>--with-brands</arg>
- <arg>--synchronize</arg>
- <arg choice="req" rep="repeat"><replaceable>LOCATION</replaceable></arg>
- </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsection id="scripts-bash-render-description">
- <title>Description</title>
-
- <para>
- The <function>render</function> functionality exists to
- automate content rendition inside &TCAR;. The content
- rendition process itself takes place through the following
- rendition modes:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <literal>svg</literal> — This modes works with both
- gzip-compressed (<filename class="extension">.svgz</filename>)
- or uncompressed (<filename class="extension">.svg</filename>)
- scalable vector graphics as source files and produces portable
- network graphics as main output.
- </para>
- </listitem>
- <listitem>
- <para>
- <literal>docbook</literal> — This mode works with
- DocBook source files and produces XHTML as main output. It is
- also possible to produce PDF output from DocBook source files,
- however PDF output is commented because its production fails
- trying to create indexes.
- </para>
- </listitem>
- <listitem>
- <para>
- <literal>conf</literal> — This mode works with one or
- more configuration files as source and produces portable
- network graphics as main output. The format used in these
- configuration files is described in <xref
- linkend="scripts-bash-render-description-conffiles"/>.
- </para>
- </listitem>
- </itemizedlist>
-
- <para>
- To determine the rendition mode, the
- <function>render</function> functionality uses the path
- provided as <replaceable>LOCATION</replaceable> argument and
- the path name convention described in <xref
- linkend="repo-convs-relbdirs" />.
- </para>
-
- <refsection id="scripts-bash-render-description-renderabledirs">
- <title>Render-able Directories</title>
-
- <para>
- The render-able directories are conventional locations inside
- the working copy where you can find final output files. The
- final output files are produced from source files and
- auxiliary files. Auxiliary files are frequently used to
- create localized instances of source files which are, in turn,
- used to create final output files in different forms (e.g., in
- a different language).
- </para>
-
- <para>
- Inside the working copy of &TCAR;, the following directory
- structures are considered render-able directories:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <filename class="directory">Identity/Images/</filename>
- — This directory structure organizes final image files
- in different formats. It also includes source files for
- producing the backgrounds of themes. Related design models for
- all these files are under <filename
- class="directory">Identity/Models/</filename> directory
- structure.
- </para>
- <important>
- <para>
- Don't move any source file related to theme backgrounds from
- render-able directories to theme design models directory
- structure. The source files related to theme backgrounds are
- specific to each theme and cannot be shared among different
- themes. The directory structure related to theme design models
- is reserved for files shared by all themes.
- </para>
- </important>
- </listitem>
- <listitem>
- <para>
- <filename
- class="directory">Documentation/Manuals/</filename>
- — This directory structure organizes final documentation
- files. Design models for all these files are organized under
- <filename
- class="directory">Documentation/Models/</filename>
- directory structure.
- </para>
- </listitem>
- </itemizedlist>
-
- <para>
- Inside render-able directories the rendition process is
- performed through different rendition flows known as
- theme-rendition, base-rendition, post-rendition and
- last-rendition.
- </para>
- </refsection>
-
- <refsection id="scripts-bash-render-description-themeflow">
- <title>Theme-Rendition Flow</title>
- <para>
- The theme-rendition flow exists to produce content inside
- <filename>Identity/Images/Themes/</filename> directory
- structure. This rendition flow identifies which directories
- are render-able and uses the base-rendition on them, one by
- one.
- </para>
- <para>
- The theme-rendition flow exists to support massive rendition
- of themes through the following command:
- </para>
-
- <cmdsynopsis>
- <command>centos-art render Identity/Images/Themes</command>
- </cmdsynopsis>
-
- <para>
- In case you need to limit the amount of themes or components
- inside themes you want to render, you can be more
- specific about the <replaceable>LOCATION</replaceable> you
- passed as argument and use the
- <option>--filter="<replaceable>REGEX</replaceable>"</option>
- to specify the file you want to render. For example, if you
- only want to render the <filename>01-welcome.png</filename>
- Anaconda file for CentOS-5 distribution based on version 2 of
- Modern artistic motif, then you can run the following command:
- </para>
-
- <cmdsynopsis>
- <command>centos-art render Identity/Images/Themes/Modern/2/Distro/5/Anaconda --filter="01-welcome"</command>
- </cmdsynopsis>
-
- <para>
- Notice that you can reach the same result in different ways
- here by creating combinations between the path you provide as
- <replaceable>LOCATION</replaceable> and the
- <option>--filter</option> option. For example, the following
- commands produce the same result:
- </para>
-
- <cmdsynopsis>
- <command>centos-art render Identity/Images/Themes/Modern/2/Distro/5/Anaconda</command>
- </cmdsynopsis>
-
- <cmdsynopsis>
- <command>centos-art render Identity/Images/Themes/Modern --filter="2/Distro/5/Anaconda"</command>
- </cmdsynopsis>
-
- <para>
- You can use whatever combination you like whenever it matches
- a valid render-able directory inside the working copy. But it
- seems to be an acceptable practice to use the
- <replaceable>LOCATION</replaceable> argument to specify the
- render-able directory path inside the <filename
- class="directory">Identity/Images/Themes</filename>
- directory which images need to be rendered for and the
- <option>--filter</option> option only when it is needed to
- restrict rendition to a specific file inside the directory
- provided as <replaceable>LOCATION</replaceable>.
- </para>
-
- </refsection>
-
- <refsection id="scripts-bash-render-description-baseflow">
- <title>Base-Rendition Flow</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-render-description-postflow">
- <title>Post-Rendition Flow </title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-render-description-lastflow">
- <title>Last-Rendition Flow </title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-render-description-conffiles">
- <title>Configuration Files (<filename>render.conf</filename>)</title>
- <para>
- ...
- </para>
- </refsection>
- </refsection>
-
- <refsection id="scripts-bash-render-usage">
- <title>Usage</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-render-option">
- <title>Options</title>
-
- <para>
- The <command>centos-art prepare</command> command accepts
- common options described in <xref
- linkend="scripts-bash-cliref-options" /> and the following
- specific options:
- </para>
-
- <variablelist>
-
- <varlistentry>
- <term><option>--answer-yes</option></term>
- <listitem>
- <para>
- Assume <emphasis>yes</emphasis> to all confirmation requests.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--filter="<replaceable>REGEX</replaceable>"</option></term>
- <listitem>
- <para>
- This option reduces the list of files to process inside
- <replaceable>LOCATION</replaceable> using
- <replaceable>REGEX</replaceable> as <replaceable>REGUEX</replaceable>
- using <replaceable>REGEX</replaceable> as files you want to render.
- The deeper you go into the directory structure the more
- specific you'll be about the files you want to render. When
- you cannot go deeper into the directory structure through
- <replaceable>LOCATION</replaceable> specification, use this
- option to reduce the list of files therein.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--synchronize</option></term>
- <listitem>
- <para>
- Synchronizes available changes between the working copy and
- the central repository.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--releasever="<replaceable>RELEASE</replaceable>"</option></term>
- <listitem>
- <para>
- This option expands the <code>=\RELEASE=</code>,
- <code>=\MAJOR_RELEASE=</code>, and
- <code>=\MINOR_RELEASE=</code> translation makers based on
- <replaceable>NUMBER</replaceable> value. Notice that
- translation markers here were escaped using a backslash
- (<code>\</code>) in order to prevent their expansion. Use this
- option when you need to produce release-specific contents, but
- no release information can be retrived from the directory path
- you are currently rendering.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--basearch="<replaceable>BASEARCH</replaceable>"</option></term>
- <listitem>
- <para>
- This option expands the <code>=\ARCHITECTURE=</code>,
- translation makers based on <replaceable>ARHC</replaceable> value.
- Notice that translation markers here were escaped using a
- backslash (<code>\</code>) in order to prevent their
- expansion. Use this option when you need to produce
- architecture-sepecific contents but no architecture
- information can be retrived from the directory path you are
- currently rendering.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--theme-model="<replaceable>MODELNAME</replaceable>"</option></term>
- <listitem>
- <para>
- This option specifies the name of theme model you want to use
- when producing theme artistic motifs. By default, if this
- option is not provided, the <literal>Default</literal> theme
- model is used as reference to produce theme artistic motifs.
- To know what values can be passed as
- <replaceable>MODELNAME</replaceable>, run the following
- command:
- </para>
-
- <cmdsynopsis>
- <command>ls ${TCAR_WORKDIR}/Identity/Models/Themes</command>
- </cmdsynopsis>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--post-rendition="<replaceable>COMMAND</replaceable>"</option></term>
- <listitem>
- <para>
- This option lets you apply a command as post-rendition action.
- In this case, the <replaceable>COMMAND</replaceable>
- represents the command-line you want to execute in order to
- perform in-place modifications to base-rendition output.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--last-rendition="<replaceable>COMMAND</replaceable>"</option></term>
- <listitem>
- <para>
- This option lets you apply a command as last-rendition action.
- In this case, the <replaceable>COMMAND</replaceable> argument
- represents the command string you want to execute in order to
- perform in-place modifications to base-rendition,
- post-rendition and directory-specific rendition outputs.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </refsection>
-
- <refsection id="scripts-bash-render-examples">
- <title>Examples</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-render-bugs">
- <title>Bugs</title>
- <para>
- To report bugs related to this function, please create a new
- ticket <ulink
- url="https://projects.centos.org/trac/artwork/newticket?summary=Error%20Standardizing%20Rendition%20Tasks&component=Scripts">here</ulink>
- refering the specific problems you found in it. For example,
- it would be useful if you copy and paste any error output from
- <command>centos-art.sh</command> script.
- </para>
- </refsection>
-
- <refsection id="scripts-bash-render-authors">
- <title>Authors</title>
- <para>
- The following people have worked in this functionality:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Alain Reguera Delgado <<ulink url="mailto:alain.reguera@gmail.com">alain.reguera@gmail.com</ulink>>, =COPYRIGHT_YEAR_LIST=
- </para>
- </listitem>
- </itemizedlist>
- </refsection>
-
- <refsection id="scripts-bash-render-licence">
- <title>License</title>
-
- <para>
- Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
- </refsection>
-
-</refentry>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/svn.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/svn.docbook
deleted file mode 100644
index 179cf3d..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/svn.docbook
+++ /dev/null
@@ -1,83 +0,0 @@
-<refentry id="scripts-bash-svn">
-
- <refmeta>
- <refentrytitle>svn</refentrytitle>
- <indexterm type="specific-function">
- <primary>Standardize version control tasks inside &TCAR;</primary>
- </indexterm>
- </refmeta>
-
- <refnamediv>
- <refname>svn</refname>
- <refpurpose>Standardize version control tasks inside &TCAR;</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
- <para>
- ...
- </para>
- </refsynopsisdiv>
-
- <refsection id="scripts-bash-svn-description">
- <title>Description</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-svn-usage">
- <title>Usage</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-svn-environment">
- <title>Function Specific Environment</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-svn-authors">
- <title>Authors</title>
- <itemizedlist>
- <listitem>
- <para>
- ...
- </para>
- </listitem>
- </itemizedlist>
- </refsection>
-
- <refsection id="scripts-bash-svn-licence">
- <title>License</title>
-
- <para>
- Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
- </refsection>
-
-</refentry>
-
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/tuneup.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/tuneup.docbook
deleted file mode 100644
index c40f697..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/tuneup.docbook
+++ /dev/null
@@ -1,301 +0,0 @@
-<refentry id="scripts-bash-tuneup">
-
- <refmeta>
- <refentrytitle>tuneup</refentrytitle>
- <indexterm type="specific-function">
- <primary>Standardize maintainance tasks inside &TCAR;</primary>
- </indexterm>
- </refmeta>
-
- <refnamediv>
- <refname>tuneup</refname>
- <refpurpose>Standardize maintainance tasks inside &TCAR;</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
- <para>
- The <varname>DIRECTORY</varname> parameter specifies the
- directory path, inside the working copy of &TCAR;, where the
- files you want to process are stored in. This paramter can be
- provided more than once in order to process more than one
- directory path in a single command execution. When this
- parameter is not provided, the current directory path where
- the command was called from is used instead.
- </para>
- </refsynopsisdiv>
-
- <refsection id="scripts-bash-tuneup-description">
- <title>Description</title>
-
- <para>
- Tasks related to file maintainance are repetitive. You might
- find yourself doing them time after time inside the working
- copy of &TCAR;. Some of these maintainance tasks do update top
- comments on shell scripts, create table of contents for web
- pages, update metadata related to design models and remove
- unused definitions from design models.
- </para>
-
- <para>
- When you execute the tuneup functionality of centos-art.sh
- script, it looks for all files that match the supported
- extensions (e.g., <filename class="extension">.sh</filename>,
- <filename class="extension">.svg</filename> and <filename
- class="extension">.xhtml</filename>) in the directory
- specified, builds a list with them and applies the
- maintainance tasks using file extensions as refentry.
- </para>
-
- <para>
- When shell scripts are found, the <function>tuneup</function>
- functionality of centos-art.sh script reads a comment template
- from
- <filename>Scripts/Functions/Tuneup/Shell/Config/topcomment.sed</filename>
- and applies it to all shell scripts found, one by one. As
- result, all shell scripts will end up having the same
- copyright and license information the comment template does.
- </para>
- <para>
- In order for the shell script top comment template to be
- applied correctly, the shell scripts you write must have the
- structure described in <xref linkend="scripts-bash-tuneup-fig1" />.
- </para>
-
- <example id="scripts-bash-tuneup-fig1">
- <title>Shell script top-comment template.</title>
- <screenshot>
- <screeninfo>Shell script top-comment template.</screeninfo>
- <mediaobject>
- <textobject>
-<programlisting>
- 1| #!/bin/bash
- 2| #
- 3| # doSomething.sh -- The function description goes here.
- 4| #
- 5| # Copyright
- 6| #
- 7| # ...
- 8| #
- 9| # ----------------------------------------------------------------------
-10| # $Id$
-11| # ----------------------------------------------------------------------
-12|
-13| function doSomething {
-14|
-15| }
-</programlisting>
- </textobject>
- </mediaobject>
- </screenshot>
- </example>
-
- <para>
- The <function>tuneup</function> functionality of
- <command>centos-art.sh</command> script replaces all lines
- between the <literal>Copyright</literal> line (e.g., line 5)
- and the first separator line (e.g., line 9), inclusively.
- Everything else will remain immutable in the file.
- </para>
-
- <para>
- When scalable vector graphics are found, the tuneup
- functionality reads a SVG metadata template from
- <filename>Scripts/Functions/Tuneup/Svg/Config/metadata.sed</filename>
- and applies it to all files found, one by one. Immediatly
- after the metadata template has been applied and, before
- passing to next file, all unused definition are removed from
- the file, too.
- </para>
- <para>
- The metadata applied by the SVG metadata template is created
- dynamicaly combining the absolute path of the file being
- currently modified, the workstation's date information, the
- <command>centos-art.sh</command> script copyright holder
- (e.g., =COPYRIGHT_HOLDER=) as refentry and the Creative
- Common Distribution-ShareAlike 3.0 License as default license
- to release SVG files.
- </para>
- <para>
- The elimination of unused definitions inside SVG files takes
- place through Inkscape's <option>--vacuum-defs</option>
- option, as described in its man page (e.g., <command>man
- inkscape</command>).
- </para>
-
- <para>
- When HTML files are found, the <function>tuneup</function>
- functionality of <command>centos-art.sh</command> script
- transforms web page headings to make them accessible through a
- table of contents. The table of contents is expanded in
- place, wherever the <code><div
- class="toc"></div></code> piece of code be in the
- file. Once the table of contents has been expanded, there is
- no need to put anything else in the page. You can run the
- <function>tuneup</function> functionality everytime you update
- the heading information so as to update the table of contents,
- too.
- </para>
- <para>
- In order for this functionality to build the table of contents
- from headings, you need to put headings in just one line. The
- headin level can vary from <code>h1</code> to <code>h6</code>
- with attribute definitions accepted. Closing tag must be
- present and also match the openning tag. Inside the heading
- definition an anchor definition must be present with attribute
- definitions accepted. The value of <property>name</property>
- and <property>href</property> attributes from the anchor
- element are set dynamically using the md5sum output of
- combining the page location, the <literal>head-</literal>
- string and the heading content itself. If any of the
- components used to build the heading refentry changes, you
- need to run the the tuneup functionality of
- <command>centos-art.sh</command> script in order for the
- anchor elements to use the correct information.
- </para>
- <para>
- For example, the headings shown in <xref
- linkend="scripts-bash-tuneup-fig2" /> produces the table of
- contents shown in <xref linkend="scripts-bash-tuneup-fig3" />.
- </para>
-
- <example id="scripts-bash-tuneup-fig2">
- <title>HTML heading definition.</title>
- <screenshot>
- <screeninfo>HTML heading definition.</screeninfo>
- <mediaobject>
- <textobject>
-<programlisting>
-<h1 class="title"><a name="head-8a23b56a28dfa7277d176576f217054a">Forms</a></h1>
-<h2 class="title"><a name="head-629f38bc607f2a270177106b450aeae3">Elements</a></h2>
-<h2 class="title"><a name="head-f49cae1d73592c984bbb0bffb1d5699a">Recommendations</a></h2>
-</programlisting>
- </textobject>
- </mediaobject>
- </screenshot>
- </example>
-
- <example id="scripts-bash-tuneup-fig3">
- <title>HTML table of contents definition.</title>
- <screenshot>
- <screeninfo>HTML table of contents definition.</screeninfo>
- <mediaobject>
- <textobject>
-<programlisting>
-<div class="toc"> <p>Table of contents</p> <dl><dt><a href="#head-8a23b56a28dfa7277d176576f217054a">Forms</a> <dl><dt><a href="#head-629f38bc607f2a270177106b450aeae3">Elements</a> </dt><dt><a href="#head-f49cae1d73592c984bbb0bffb1d5699a">Recommendations</a> </dt></dl> </dt></dl> </div>
-</programlisting>
- </textobject>
- </mediaobject>
- </screenshot>
- </example>
- </refsection>
-
- <refsection id="scripts-bash-tuneup-options">
- <title>Options</title>
- <para>
- The <function>tuneup</function> functionality accepts the
- following options:
- </para>
-
- <variablelist>
- <varlistentry>
- <term><option>--quiet</option></term>
- <listitem>
- <para>
- Supress all output messages except error messages. When this
- option is passed, all confirmation requests are supressed and
- a possitive answer is assumed for them, just as if the
- <option>--answer-yes</option> option would have been provided.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--answer-yes</option></term>
- <listitem>
- <para>
- Assume <emphasis>yes</emphasis> to all confirmation requests.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--filter="REGEX"</option></term>
- <listitem>
- <para>
- Reduce the list of files to process inside
- <replaceable>path/to/dir</replaceable> using
- <replaceable>REGEX</replaceable> as pattern. You can use this
- option to control the amount of files you want to tuneup. The
- deeper you go into the directory structure the more specific
- you'll be about the files you want to tuneup. When you cannot
- go deeper into the directory structure through
- <replaceable>path/to/dir</replaceable> specification, use this
- option to reduce the list of files therein.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--synchronize</option></term>
- <listitem>
- <para>
- Synchronizes available changes between the working copy and
- the central repository.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </refsection>
-
- <refsection id="scripts-bash-tuneup-environment">
- <title>Function Specific Environment</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-tuneup-authors">
- <title>Authors</title>
- <para>
- The following people have worked in the
- <function>tuneup</function> functionality:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Alain Reguera Delgado <<ulink url="mailto:alain.reguera@gmail.com">alain.reguera@gmail.com</ulink>>, =COPYRIGHT_YEAR_LIST=
- </para>
- </listitem>
- </itemizedlist>
- </refsection>
-
- <refsection id="scripts-bash-tuneup-licence">
- <title>License</title>
-
- <para>
- Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
- </refsection>
-
-</refentry>
diff --git a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/vcs.docbook b/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/vcs.docbook
deleted file mode 100644
index fbf8a4c..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/Scripts/Bash/vcs.docbook
+++ /dev/null
@@ -1,83 +0,0 @@
-<refentry id="scripts-bash-vcs">
-
- <refmeta>
- <refentrytitle>vcs</refentrytitle>
- <indexterm type="specific-function">
- <primary>Standardize version control tasks inside &TCAR;</primary>
- </indexterm>
- </refmeta>
-
- <refnamediv>
- <refname>vcs</refname>
- <refpurpose>Standardize version control tasks inside &TCAR;</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
- <para>
- ...
- </para>
- </refsynopsisdiv>
-
- <refsection id="scripts-bash-vcs-description">
- <title>Description</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-vcs-usage">
- <title>Usage</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-vcs-environment">
- <title>Function Specific Environment</title>
- <para>
- ...
- </para>
- </refsection>
-
- <refsection id="scripts-bash-vcs-authors">
- <title>Authors</title>
- <itemizedlist>
- <listitem>
- <para>
- ...
- </para>
- </listitem>
- </itemizedlist>
- </refsection>
-
- <refsection id="scripts-bash-vcs-licence">
- <title>License</title>
-
- <para>
- Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
-
- <para>
- 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.
- </para>
- </refsection>
-
-</refentry>
-
diff --git a/Artworks/Docs/Docbook/Tcar-ug/tcar-ug.docbook b/Artworks/Docs/Docbook/Tcar-ug/tcar-ug.docbook
deleted file mode 100644
index b0a19c9..0000000
--- a/Artworks/Docs/Docbook/Tcar-ug/tcar-ug.docbook
+++ /dev/null
@@ -1,84 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" []>
-<!--
- WARNING: Keep the preable definition as it is (in two lines). The
- centos-art.sh script uses this information as pattern to rebuild
- the preamble definition later and introduce system entities
- definitions in it. If centos-art.sh script cannot rebuild the
- preamble definition of this document its validation will fail and
- consequently, no final rendition will be possible.
--->
-<book lang="en_US">
-
- <!-- Front matter -->
-
- <title>The CentOS Artwork Repository</title>
- <subtitle>User's Guide</subtitle>
-
- <bookinfo>
- <author>
- <firstname>Alain</firstname>
- <surname>Reguera Delgado</surname>
- </author>
-
- <!-- Copyright: The copyright page is verso and contains the
- copyright notice, the publishing/printing history, the country
- where printed, ISBN and/or CIP information. The page is
- usually typeset in a smaller font than the normal text. -->
- <copyright>
- <year>2009</year>
- <year>2010</year>
- <year>2011</year>
- <year>2012</year>
- <year>2013</year>
- <holder>&TCP;. All rights reserved.</holder>
- </copyright>
-
- <legalnotice>
- <para>
- 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
- <xref linkend="licenses-gfdl" />.
- </para>
- </legalnotice>
-
- <revhistory>
- <revision>
- <revnumber>1.0</revnumber>
- <date>Today</date>
- <author>
- <firstname>Alain</firstname>
- <surname>Reguera Delgado</surname>
- </author>
- <revdescription>
- <para>
- Under development.
- </para>
- </revdescription>
- </revision>
- </revhistory>
-
- </bookinfo>
-
- <!-- Preface -->
- &preface;
- <!-- Main matter -->
- &repo;
- &identity;
- &locales;
- &manuals;
- &scripts;
- <!-- Licenses -->
- <!--
- WARNING: Licenses are included by centos-art.sh script at
- execution time, so don't remove the comments this message is in
- between, nor this message so you can remember it.
- -->
- <!-- Back matter -->
- <index><title>Index</title></index>
-
-</book>
diff --git a/Artworks/Docs/Svg/Brands/Logos/centos.svgz b/Artworks/Docs/Svg/Brands/Logos/centos.svgz
deleted file mode 100644
index c94a127..0000000
Binary files a/Artworks/Docs/Svg/Brands/Logos/centos.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Symbols/centos-howto-1of4.svgz b/Artworks/Docs/Svg/Brands/Symbols/centos-howto-1of4.svgz
deleted file mode 100644
index 2b74847..0000000
Binary files a/Artworks/Docs/Svg/Brands/Symbols/centos-howto-1of4.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Symbols/centos-howto-2of4.svgz b/Artworks/Docs/Svg/Brands/Symbols/centos-howto-2of4.svgz
deleted file mode 100644
index d2b583e..0000000
Binary files a/Artworks/Docs/Svg/Brands/Symbols/centos-howto-2of4.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Symbols/centos-howto-3of4.svgz b/Artworks/Docs/Svg/Brands/Symbols/centos-howto-3of4.svgz
deleted file mode 100644
index 0d1dba5..0000000
Binary files a/Artworks/Docs/Svg/Brands/Symbols/centos-howto-3of4.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Symbols/centos-howto-4of4.svgz b/Artworks/Docs/Svg/Brands/Symbols/centos-howto-4of4.svgz
deleted file mode 100644
index 842a1d9..0000000
Binary files a/Artworks/Docs/Svg/Brands/Symbols/centos-howto-4of4.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-10-p.svgz b/Artworks/Docs/Svg/Brands/Types/centos-10-p.svgz
deleted file mode 100644
index e514a7a..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-10-p.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-10.svgz b/Artworks/Docs/Svg/Brands/Types/centos-10.svgz
deleted file mode 100644
index 6258646..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-10.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-3-p.svgz b/Artworks/Docs/Svg/Brands/Types/centos-3-p.svgz
deleted file mode 100644
index 2f23c5f..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-3-p.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-3.svgz b/Artworks/Docs/Svg/Brands/Types/centos-3.svgz
deleted file mode 100644
index 9b421ff..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-3.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-4-p.svgz b/Artworks/Docs/Svg/Brands/Types/centos-4-p.svgz
deleted file mode 100644
index 639a685..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-4-p.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-4.svgz b/Artworks/Docs/Svg/Brands/Types/centos-4.svgz
deleted file mode 100644
index bfb97c2..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-4.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-5-p.svgz b/Artworks/Docs/Svg/Brands/Types/centos-5-p.svgz
deleted file mode 100644
index c1c73e6..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-5-p.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-5.svgz b/Artworks/Docs/Svg/Brands/Types/centos-5.svgz
deleted file mode 100644
index e9ad7e8..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-5.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-6-p.svgz b/Artworks/Docs/Svg/Brands/Types/centos-6-p.svgz
deleted file mode 100644
index 687ec69..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-6-p.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-6.svgz b/Artworks/Docs/Svg/Brands/Types/centos-6.svgz
deleted file mode 100644
index 8585c3b..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-6.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-7-p.svgz b/Artworks/Docs/Svg/Brands/Types/centos-7-p.svgz
deleted file mode 100644
index e5d85a6..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-7-p.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-7.svgz b/Artworks/Docs/Svg/Brands/Types/centos-7.svgz
deleted file mode 100644
index aadc35d..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-7.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-8-p.svgz b/Artworks/Docs/Svg/Brands/Types/centos-8-p.svgz
deleted file mode 100644
index ab102bc..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-8-p.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-8.svgz b/Artworks/Docs/Svg/Brands/Types/centos-8.svgz
deleted file mode 100644
index c1e9da5..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-8.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-9-p.svgz b/Artworks/Docs/Svg/Brands/Types/centos-9-p.svgz
deleted file mode 100644
index aeb2b56..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-9-p.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-9.svgz b/Artworks/Docs/Svg/Brands/Types/centos-9.svgz
deleted file mode 100644
index 13907a1..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-9.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-art-p.svgz b/Artworks/Docs/Svg/Brands/Types/centos-art-p.svgz
deleted file mode 100644
index d57e89a..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-art-p.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-art.svgz b/Artworks/Docs/Svg/Brands/Types/centos-art.svgz
deleted file mode 100644
index d8e36fd..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-art.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-p.svgz b/Artworks/Docs/Svg/Brands/Types/centos-p.svgz
deleted file mode 100644
index 9d0692c..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-p.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-r.svgz b/Artworks/Docs/Svg/Brands/Types/centos-r.svgz
deleted file mode 100644
index c975082..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-r.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos-tm.svgz b/Artworks/Docs/Svg/Brands/Types/centos-tm.svgz
deleted file mode 100644
index e19bb94..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos-tm.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Brands/Types/centos.svgz b/Artworks/Docs/Svg/Brands/Types/centos.svgz
deleted file mode 100644
index 26811b3..0000000
Binary files a/Artworks/Docs/Svg/Brands/Types/centos.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Corporate/common-design-model-fig1.svgz b/Artworks/Docs/Svg/Corporate/common-design-model-fig1.svgz
deleted file mode 100644
index 91b88e1..0000000
Binary files a/Artworks/Docs/Svg/Corporate/common-design-model-fig1.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Corporate/common-design-model-fig2.svgz b/Artworks/Docs/Svg/Corporate/common-design-model-fig2.svgz
deleted file mode 100644
index 38d267f..0000000
Binary files a/Artworks/Docs/Svg/Corporate/common-design-model-fig2.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Corporate/monolithic.svgz b/Artworks/Docs/Svg/Corporate/monolithic.svgz
deleted file mode 100644
index ca572fb..0000000
Binary files a/Artworks/Docs/Svg/Corporate/monolithic.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/header-fig-1.svgz b/Artworks/Docs/Svg/Distro/Anaconda/header-fig-1.svgz
deleted file mode 100755
index 7a8d5c1..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/header-fig-1.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/header-fig-2.svgz b/Artworks/Docs/Svg/Distro/Anaconda/header-fig-2.svgz
deleted file mode 100755
index b183a40..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/header-fig-2.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/header-fig-summary.svgz b/Artworks/Docs/Svg/Distro/Anaconda/header-fig-summary.svgz
deleted file mode 100755
index 2c6a56c..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/header-fig-summary.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-1.svgz b/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-1.svgz
deleted file mode 100755
index 9ca9a2b..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-1.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-2.svgz b/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-2.svgz
deleted file mode 100755
index ceb0db1..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-2.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-3.svgz b/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-3.svgz
deleted file mode 100755
index 5fdcd8b..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-3.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-4.svgz b/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-4.svgz
deleted file mode 100755
index a14ac0d..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-4.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-5.svgz b/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-5.svgz
deleted file mode 100755
index 27ccbee..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-5.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-summary.svgz b/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-summary.svgz
deleted file mode 100755
index f849e75..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/progress-fig-summary.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/splash-fig-1.svgz b/Artworks/Docs/Svg/Distro/Anaconda/splash-fig-1.svgz
deleted file mode 100755
index 6015230..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/splash-fig-1.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/splash-fig-2.svgz b/Artworks/Docs/Svg/Distro/Anaconda/splash-fig-2.svgz
deleted file mode 100755
index 2322cfc..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/splash-fig-2.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/splash-fig-summary.svgz b/Artworks/Docs/Svg/Distro/Anaconda/splash-fig-summary.svgz
deleted file mode 100644
index 3d76b4a..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/splash-fig-summary.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/summary.svgz b/Artworks/Docs/Svg/Distro/Anaconda/summary.svgz
deleted file mode 100755
index b23b620..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/summary.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/syslinux-fig-1.svgz b/Artworks/Docs/Svg/Distro/Anaconda/syslinux-fig-1.svgz
deleted file mode 100755
index 3f6b27c..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/syslinux-fig-1.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/syslinux-fig-2.svgz b/Artworks/Docs/Svg/Distro/Anaconda/syslinux-fig-2.svgz
deleted file mode 100755
index 9b11d80..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/syslinux-fig-2.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/syslinux-fig-3.svgz b/Artworks/Docs/Svg/Distro/Anaconda/syslinux-fig-3.svgz
deleted file mode 100755
index bbed5ba..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/syslinux-fig-3.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/Anaconda/syslinux-fig-summary.svgz b/Artworks/Docs/Svg/Distro/Anaconda/syslinux-fig-summary.svgz
deleted file mode 100755
index 5120530..0000000
Binary files a/Artworks/Docs/Svg/Distro/Anaconda/syslinux-fig-summary.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/BootUp/firstboot-fig-1.svgz b/Artworks/Docs/Svg/Distro/BootUp/firstboot-fig-1.svgz
deleted file mode 100644
index 4aee16f..0000000
Binary files a/Artworks/Docs/Svg/Distro/BootUp/firstboot-fig-1.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Distro/BootUp/firstboot-fig-summary.svgz b/Artworks/Docs/Svg/Distro/BootUp/firstboot-fig-summary.svgz
deleted file mode 100644
index 8b46337..0000000
Binary files a/Artworks/Docs/Svg/Distro/BootUp/firstboot-fig-summary.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Fonts/dejavu-lgc.svgz b/Artworks/Docs/Svg/Fonts/dejavu-lgc.svgz
deleted file mode 100644
index 55fb02d..0000000
Binary files a/Artworks/Docs/Svg/Fonts/dejavu-lgc.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Fonts/denmark.svgz b/Artworks/Docs/Svg/Fonts/denmark.svgz
deleted file mode 100644
index 2acea0f..0000000
Binary files a/Artworks/Docs/Svg/Fonts/denmark.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Repository/directory-structure.svgz b/Artworks/Docs/Svg/Repository/directory-structure.svgz
deleted file mode 100644
index 9975856..0000000
Binary files a/Artworks/Docs/Svg/Repository/directory-structure.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Repository/infrastructure.svgz b/Artworks/Docs/Svg/Repository/infrastructure.svgz
deleted file mode 100644
index 308a021..0000000
Binary files a/Artworks/Docs/Svg/Repository/infrastructure.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-1.svgz b/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-1.svgz
deleted file mode 100644
index 1e53a09..0000000
Binary files a/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-1.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-2.svgz b/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-2.svgz
deleted file mode 100644
index 0f3bfcf..0000000
Binary files a/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-2.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-3.svgz b/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-3.svgz
deleted file mode 100644
index 1296f1e..0000000
Binary files a/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-3.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-4.svgz b/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-4.svgz
deleted file mode 100644
index ceea222..0000000
Binary files a/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-4.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-5.svgz b/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-5.svgz
deleted file mode 100644
index 89c165a..0000000
Binary files a/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-5.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-6.svgz b/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-6.svgz
deleted file mode 100644
index c04de8a..0000000
Binary files a/Artworks/Docs/Svg/Scripts/Bash/Functions/Path/figure-6.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Scripts/initFunctions.svgz b/Artworks/Docs/Svg/Scripts/initFunctions.svgz
deleted file mode 100644
index f9014d4..0000000
Binary files a/Artworks/Docs/Svg/Scripts/initFunctions.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Scripts/renderImage.svgz b/Artworks/Docs/Svg/Scripts/renderImage.svgz
deleted file mode 100644
index b187c16..0000000
Binary files a/Artworks/Docs/Svg/Scripts/renderImage.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Showroom/Clothes/cap-back.svgz b/Artworks/Docs/Svg/Showroom/Clothes/cap-back.svgz
deleted file mode 100644
index 72e4995..0000000
Binary files a/Artworks/Docs/Svg/Showroom/Clothes/cap-back.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Showroom/Clothes/cap-front.svgz b/Artworks/Docs/Svg/Showroom/Clothes/cap-front.svgz
deleted file mode 100644
index a3f8291..0000000
Binary files a/Artworks/Docs/Svg/Showroom/Clothes/cap-front.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Showroom/Clothes/cap-left.svgz b/Artworks/Docs/Svg/Showroom/Clothes/cap-left.svgz
deleted file mode 100644
index d2ef431..0000000
Binary files a/Artworks/Docs/Svg/Showroom/Clothes/cap-left.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Showroom/Clothes/cap-right.svgz b/Artworks/Docs/Svg/Showroom/Clothes/cap-right.svgz
deleted file mode 100644
index bbd5996..0000000
Binary files a/Artworks/Docs/Svg/Showroom/Clothes/cap-right.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Showroom/Clothes/shirt-back.svgz b/Artworks/Docs/Svg/Showroom/Clothes/shirt-back.svgz
deleted file mode 100644
index 2f4d897..0000000
Binary files a/Artworks/Docs/Svg/Showroom/Clothes/shirt-back.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Showroom/Clothes/shirt-front.svgz b/Artworks/Docs/Svg/Showroom/Clothes/shirt-front.svgz
deleted file mode 100644
index a1403ab..0000000
Binary files a/Artworks/Docs/Svg/Showroom/Clothes/shirt-front.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Showroom/Clothes/summary.svgz b/Artworks/Docs/Svg/Showroom/Clothes/summary.svgz
deleted file mode 100644
index 26f462f..0000000
Binary files a/Artworks/Docs/Svg/Showroom/Clothes/summary.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Showroom/Clothes/tshirt-back.svgz b/Artworks/Docs/Svg/Showroom/Clothes/tshirt-back.svgz
deleted file mode 100644
index cd0d8c5..0000000
Binary files a/Artworks/Docs/Svg/Showroom/Clothes/tshirt-back.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Showroom/Clothes/tshirt-front.svgz b/Artworks/Docs/Svg/Showroom/Clothes/tshirt-front.svgz
deleted file mode 100644
index 343ed4f..0000000
Binary files a/Artworks/Docs/Svg/Showroom/Clothes/tshirt-front.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Webenv/customization-with-ads.svgz b/Artworks/Docs/Svg/Webenv/customization-with-ads.svgz
deleted file mode 100644
index 7f0ae99..0000000
Binary files a/Artworks/Docs/Svg/Webenv/customization-with-ads.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Webenv/customization.svgz b/Artworks/Docs/Svg/Webenv/customization.svgz
deleted file mode 100644
index 482a531..0000000
Binary files a/Artworks/Docs/Svg/Webenv/customization.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Webenv/homepage.svgz b/Artworks/Docs/Svg/Webenv/homepage.svgz
deleted file mode 100644
index 41b449c..0000000
Binary files a/Artworks/Docs/Svg/Webenv/homepage.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Webenv/navigation.svgz b/Artworks/Docs/Svg/Webenv/navigation.svgz
deleted file mode 100644
index 69419c5..0000000
Binary files a/Artworks/Docs/Svg/Webenv/navigation.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Webenv/webenv-html-defs.svgz b/Artworks/Docs/Svg/Webenv/webenv-html-defs.svgz
deleted file mode 100644
index e1483b4..0000000
Binary files a/Artworks/Docs/Svg/Webenv/webenv-html-defs.svgz and /dev/null differ
diff --git a/Artworks/Docs/Svg/Webenv/wiki-moin.svgz b/Artworks/Docs/Svg/Webenv/wiki-moin.svgz
deleted file mode 100644
index 3a09750..0000000
Binary files a/Artworks/Docs/Svg/Webenv/wiki-moin.svgz and /dev/null differ
diff --git a/Artworks/Docs/Texinfo/Default/en_US/Chapters-menu.texinfo b/Artworks/Docs/Texinfo/Default/en_US/Chapters-menu.texinfo
deleted file mode 100644
index e69de29..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/Chapters-menu.texinfo
+++ /dev/null
diff --git a/Artworks/Docs/Texinfo/Default/en_US/Chapters-nodes.texinfo b/Artworks/Docs/Texinfo/Default/en_US/Chapters-nodes.texinfo
deleted file mode 100644
index 3e2dc0b..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/Chapters-nodes.texinfo
+++ /dev/null
@@ -1 +0,0 @@
-@include =INCL=
diff --git a/Artworks/Docs/Texinfo/Default/en_US/Chapters.texinfo b/Artworks/Docs/Texinfo/Default/en_US/Chapters.texinfo
deleted file mode 100644
index 249e5cc..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/Chapters.texinfo
+++ /dev/null
@@ -1,12 +0,0 @@
-@node =CHAPTER_NODE=
-@chapter =CHAPTER_TITLE=
-@cindex =CHAPTER_CIND=
-
-@c -- Chapter Introduction
-...
-
-@c -- Chapter Menu
-@include =CHAPTER_NAME=-menu.texinfo
-
-@c -- Chapter Nodes
-@include =CHAPTER_NAME=-nodes.texinfo
diff --git a/Artworks/Docs/Texinfo/Default/en_US/Chapters/section-functions.texinfo b/Artworks/Docs/Texinfo/Default/en_US/Chapters/section-functions.texinfo
deleted file mode 100644
index 88cd2cc..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/Chapters/section-functions.texinfo
+++ /dev/null
@@ -1,35 +0,0 @@
-@node =SECT=
-@section =SECT=
-@cindex =CIND=
-
-@subheading Name
-
-The =SECT= directory organizes @dots{}
-
-@subheading Synopsis
-
-@dots{}
-
-@subheading Description
-
-@dots{}
-
-@subheading Examples
-
-@dots{}
-
-@subheading Author
-
-Written by @dots{}
-
-@subheading Reporting bugs
-
-Report bugs to @email{centos-artwork@@centos.org} mailing list.
-
-@subheading Copyright
-
-Copyright @copyright{} =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
-
-This is free software. You may redistribute copies of it under the
-terms of the @ref{GNU General Public License}. There is NO WARRANTY,
-to the extent permitted by law.
diff --git a/Artworks/Docs/Texinfo/Default/en_US/Chapters/section.texinfo b/Artworks/Docs/Texinfo/Default/en_US/Chapters/section.texinfo
deleted file mode 100644
index 9461faa..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/Chapters/section.texinfo
+++ /dev/null
@@ -1,8 +0,0 @@
-@node =NODE=
-@section =SECT=
-@cindex =CIND=
-
-...
-
-@c -- <[centos-art(SeeAlso)
-@c -- ]>
diff --git a/Artworks/Docs/Texinfo/Default/en_US/Licenses-menu.texinfo b/Artworks/Docs/Texinfo/Default/en_US/Licenses-menu.texinfo
deleted file mode 100755
index b8240ba..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/Licenses-menu.texinfo
+++ /dev/null
@@ -1,4 +0,0 @@
-@menu
-* GNU General Public License::
-* GNU Free Documentation License::
-@end menu
diff --git a/Artworks/Docs/Texinfo/Default/en_US/Licenses-nodes.texinfo b/Artworks/Docs/Texinfo/Default/en_US/Licenses-nodes.texinfo
deleted file mode 100755
index da69108..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/Licenses-nodes.texinfo
+++ /dev/null
@@ -1,9 +0,0 @@
-@node GNU General Public License
-@section GNU General Public License
-@cindex GNU General Public License
-@include Licenses/GPL.texinfo
-
-@node GNU Free Documentation License
-@section GNU Free Documentation License
-@cindex GNU Free Documentation License
-@include Licenses/GFDL.texinfo
diff --git a/Artworks/Docs/Texinfo/Default/en_US/Licenses.texinfo b/Artworks/Docs/Texinfo/Default/en_US/Licenses.texinfo
deleted file mode 100755
index 8b2fda9..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/Licenses.texinfo
+++ /dev/null
@@ -1,5 +0,0 @@
-@node Licenses
-@appendix Licenses
-@cindex Licenses
-@include Licenses-menu.texinfo
-@include Licenses-nodes.texinfo
diff --git a/Artworks/Docs/Texinfo/Default/en_US/Licenses/GFDL.texinfo b/Artworks/Docs/Texinfo/Default/en_US/Licenses/GFDL.texinfo
deleted file mode 100755
index c40cf38..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/Licenses/GFDL.texinfo
+++ /dev/null
@@ -1,414 +0,0 @@
-Version 1.2, November 2002
-
-@verbatim
-Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc.
- 675 Mass Ave, Cambridge, MA 02139, USA
-@end verbatim
-
-Everyone is permitted to copy and distribute verbatim copies of this
-license document, but changing it is not allowed.
-
-@subheading Preamble
-
-The purpose of this License is to make a manual, textbook, or other
-functional and useful document ``free'' 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.
-
-This License is a kind of ``copyleft'', which means that derivative
-works of the document must themselves be free in the same sense. It
-complements the GNU General Public License, which is a copyleft
-license designed for free software.
-
-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.
-
-@subheading 1. Applicability and definitions
-
-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 ``Document'', below,
-refers to any such manual or work. Any member of the public is a
-licensee, and is addressed as ``you''. You accept the license if you
-copy, modify or distribute the work in a way requiring permission
-under copyright law.
-
-A ``Modified Version'' 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.
-
-A ``Secondary Section'' 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.
-
-The ``Invariant Sections'' 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.
-
-The ``Cover Texts'' 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.
-
-A ``Transparent'' 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 ``Transparent'' is called ``Opaque''.
-
-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.
-
-The ``Title Page'' 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, ``Title Page'' means
-the text near the most prominent appearance of the work's title,
-preceding the beginning of the body of the text.
-
-A section ``Entitled XYZ'' 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 ``Acknowledgements'',
-``Dedications'', ``Endorsements'', or ``History''.) To ``Preserve the
-Title'' of such a section when you modify the Document means that it
-remains a section ``Entitled XYZ'' according to this definition.
-
-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.
-
-@subheading 2. Verbatim copying
-
-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 @emph{3.
-Copying in quantity}.
-
-You may also lend copies, under the same conditions stated above, and
-you may publicly display copies.
-
-@subheading 3. Copying in quantity
-
-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.
-
-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.
-
-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.
-
-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.
-
-@subheading 4. Modifications
-
-You may copy and distribute a Modified Version of the Document under
-the conditions of sections @emph{2. Verbatim copying} and @emph{3.
-Copying in quantity} 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:
-
-A. 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.
-
-B. 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.
-
-C. State on the Title page the name of the publisher of the Modified
-Version, as the publisher.
-
-D. Preserve all the copyright notices of the Document.
-
-E. Add an appropriate copyright notice for your modifications adjacent
-to the other copyright notices.
-
-F. 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.
-
-G. Preserve in that license notice the full lists of Invariant
-Sections and required Cover Texts given in the Document's license
-notice.
-
-H. Include an unaltered copy of this License.
-
-I. Preserve the section Entitled ``History'', 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 ``History'' 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.
-
-J. 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 ``History'' 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.
-
-K. For any section Entitled ``Acknowledgements'' or ``Dedications'',
-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.
-
-L. 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.
-
-M. Delete any section Entitled ``Endorsements''. Such a section may
-not be included in the Modified Version.
-
-N. Do not retitle any existing section to be Entitled ``Endorsements''
-or to conflict in title with any Invariant Section.
-
-O. Preserve any Warranty Disclaimers.
-
-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.
-
-You may add a section Entitled ``Endorsements'', 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.
-
-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.
-
-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.
-
-@subheading 5. Combining documents
-
-You may combine the Document with other documents released under this
-License, under the terms defined in section @emph{4. Modifications}
-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.
-
-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.
-
-In the combination, you must combine any sections Entitled ``History''
-in the various original documents, forming one section Entitled
-``History''; likewise combine any sections Entitled
-``Acknowledgements'',
-and any sections Entitled ``Dedications''. You must delete all sections
-Entitled ``Endorsements''.
-
-@subheading 6. Collections of documents
-
-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.
-
-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.
-
-@subheading 7. Aggregation with independent works
-
-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 ``aggregate'' 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.
-
-If the Cover Text requirement of section @emph{3. Copying in quantity}
-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.
-
-@subheading 8. Translations
-
-Translation is considered a kind of modification, so you may
-distribute translations of the Document under the terms of section
-@emph{4. Modifications}. 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.
-
-If a section in the Document is Entitled ``Acknowledgements'',
-``Dedications'', or ``History'', the requirement (section @emph{4.
-Modifications}) to Preserve its Title (section @emph{1. Applicability
-and definitions}) will typically require changing the actual title.
-
-@subheading 9. Termination
-
-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.
-
-@subheading Future Revisions of this License
-
-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
-@url{http://www.gnu.org/copyleft/}.
-
-Each version of the License is given a distinguishing version number.
-If the Document specifies that a particular numbered version of this
-License ``or any later version'' 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.
-
-@subheading How to use this License for your documents
-
-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:
-
-@verbatim
- 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 ``GNU Free Documentation License''.
-@end verbatim
-
-If you have Invariant Sections, Front-Cover Texts and Back-Cover
-Texts, replace the ``with...Texts''. line with this:
-
-@verbatim
- with the Invariant Sections being LIST THEIR TITLES, with the
- Front-Cover Texts being LIST, and with the Back-Cover Texts
- being LIST.
-@end verbatim
-
-If you have Invariant Sections without Cover Texts, or some other
-combination of the three, merge those two alternatives to suit the
-situation.
-
-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.
diff --git a/Artworks/Docs/Texinfo/Default/en_US/Licenses/GPL.texinfo b/Artworks/Docs/Texinfo/Default/en_US/Licenses/GPL.texinfo
deleted file mode 100755
index 3349125..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/Licenses/GPL.texinfo
+++ /dev/null
@@ -1,376 +0,0 @@
-Version 2, June 1991
-
-@verbatim
-Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 675 Mass Ave, Cambridge, MA 02139, USA
-@end verbatim
-
-Everyone is permitted to copy and distribute verbatim copies of this
-license document, but changing it is not allowed.
-
-@subheading Preamble
-
-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.
-
-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.
-
-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.
-
-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.
-
-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.
-
-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.
-
-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.
-
-The precise terms and conditions for copying, distribution and
-modification follow.
-
-@subheading TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-@subsubheading Section 0
-
-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 ``Program'',
-below, refers to any such program or work, and a ``work based on the
-Program'' 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 ``modification''.) Each licensee is addressed
-as ``you''.
-
-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.
-
-@subsubheading Section 1
-
-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.
-
-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.
-
-@subsubheading Section 2
-
-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:
-
-a) You must cause the modified files to carry prominent notices
-stating that you changed the files and the date of any change.
-
-b) 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.
-
-c) 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. (Exception: 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.)
-
-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.
-
-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.
-
-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.
-
-@subsubheading Section 3
-
-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:
-
-a) 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,
-
-b) 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,
-
-c) 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.)
-
-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.
-
-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.
-
-@subsubheading Section 4
-
-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.
-
-@subsubheading Section 5
-
-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.
-
-@subsubheading Section 6
-
-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.
-
-@subsubheading Section 7
-
-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.
-
-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.
-
-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.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
-@subsubheading Section 8
-
-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.
-
-@subsubheading Section 9
-
-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.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and ``any
-later version'', 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.
-
-@subsubheading Section 10
-
-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.
-
-@subsubheading NO WARRANTY
-
-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 ``AS IS'' 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.
-
-@subsubheading Section 12
-
-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.
-
-@strong{END OF TERMS AND CONDITIONS}
-
-@subheading How to Apply These Terms to Your New Programs
-
-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.
-
-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 ``copyright'' line and a pointer to where the full notice is
-found.
-
-@verbatim
- <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.
-@end verbatim
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
-@verbatim
- 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.
-@end verbatim
-
-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.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a ``copyright disclaimer'' for the program, if
-necessary. Here is a sample; alter the names:
-
-@verbatim
- 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
-@end verbatim
-
-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.
diff --git a/Artworks/Docs/Texinfo/Default/en_US/manual-index.texinfo b/Artworks/Docs/Texinfo/Default/en_US/manual-index.texinfo
deleted file mode 100755
index b197b13..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/manual-index.texinfo
+++ /dev/null
@@ -1,8 +0,0 @@
-@node Index
-@unnumbered Index
-@syncodeindex fn cp
-@syncodeindex vr cp
-@syncodeindex ky cp
-@syncodeindex pg cp
-@syncodeindex tp cp
-@printindex cp
diff --git a/Artworks/Docs/Texinfo/Default/en_US/manual-init.pl b/Artworks/Docs/Texinfo/Default/en_US/manual-init.pl
deleted file mode 100755
index c6eff54..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/manual-init.pl
+++ /dev/null
@@ -1,7 +0,0 @@
-# This file extends the `../manual-init.pl' initialization file to
-# provide English specific initializations for `texi2html-1.76-4.fc6'.
-# ----------------------------------------------------------------------
-# $Id$
-# ----------------------------------------------------------------------
-
-return 1;
diff --git a/Artworks/Docs/Texinfo/Default/en_US/manual-menu.texinfo b/Artworks/Docs/Texinfo/Default/en_US/manual-menu.texinfo
deleted file mode 100644
index 0afc9ff..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/manual-menu.texinfo
+++ /dev/null
@@ -1,4 +0,0 @@
-@menu
-* Licenses::
-* Index::
-@end menu
diff --git a/Artworks/Docs/Texinfo/Default/en_US/manual-nodes.texinfo b/Artworks/Docs/Texinfo/Default/en_US/manual-nodes.texinfo
deleted file mode 100644
index e69de29..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/manual-nodes.texinfo
+++ /dev/null
diff --git a/Artworks/Docs/Texinfo/Default/en_US/manual.conf b/Artworks/Docs/Texinfo/Default/en_US/manual.conf
deleted file mode 100755
index 72b65de..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/manual.conf
+++ /dev/null
@@ -1,36 +0,0 @@
-# This file controls the manual configuration. This file is divided
-# in configuration sections (e.g., `main' and `templates') which, in
-# turn, are organized in the form `variable = value'.
-# ----------------------------------------------------------------------
-# $Id$
-# ----------------------------------------------------------------------
-
-[main]
-
-# Specify documentation backend used by documentation manual. This is
-# the format used to write documentation manual source files.
-manual_format = "texinfo"
-
-# Specify title style used by sections inside the manual. Possible
-# values to this option are `cap-each-word' to capitalize each word in
-# the section title, `cap-first-word' to capitalize the first word in
-# the section title only and `directory' to transform each word in the
-# section title into a directory path. From all these options,
-# `cap-each-word' is the one used as default.
-manual_section_style = "cap-each-word"
-
-# Specify the order used by sections inside the manual. By default new
-# sections added to the manual are put on the end to follow the
-# section `created' order. Other possible values to this option are
-# `ordered' and `reversed' to sort the list of sections alphabetically
-# from A-Z and Z-A, respectively.
-manual_section_order = "created"
-
-[templates]
-
-# Specify relation between template files and section definition files
-# inside the manual. Template definition is set on the left side using
-# relative path. The section main definition file is described on the
-# right using a regular expression. The first match wins.
-Chapters/section-functions.texinfo = "^.+-functions-[[:alnum:]]+\.texinfo$"
-Chapters/section.texinfo = "^.+\.texinfo$"
diff --git a/Artworks/Docs/Texinfo/Default/en_US/manual.sed b/Artworks/Docs/Texinfo/Default/en_US/manual.sed
deleted file mode 100755
index 274b0f5..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/manual.sed
+++ /dev/null
@@ -1,40 +0,0 @@
-#!/bin/sed
-#
-# repository.sed -- This file provide English transformations for
-# texi2html outupt, based on The CentOS Project CSS definitions.
-#
-# Copyright (C) 2009-2012 The CentOS Project
-#
-# 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., 59 Temple Place, Suite 330, Boston, MA 02111-1307
-# USA.
-#
-# ----------------------------------------------------------------------
-# $Id$
-# ----------------------------------------------------------------------
-
-# Quotations.
-s!<blockquote><p><strong>Note</strong>!<blockquote class="blue icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/note.png" alt="Info" /><h2>Note</h2><p>!g
-
-s!<blockquote><p><strong>Warning</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/warning.png" alt="Warning" /><h2>Warning</h2><p>!g
-
-s!<blockquote><p><strong>Important</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/important.png" alt="Important" /><h2>Important</h2><p>!g
-
-s!<blockquote><p><strong>Tip</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/tip.png" alt="Tip" /><h2>Tip</h2><p>!g
-
-s!<blockquote><p><strong>Caution</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/caution.png" alt="Caution" /><h2>Caution</h2><p>!g
-
-s!<blockquote><p><strong>Convention</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/ruler.png" alt="Convention" /><h2>Convention</h2><p>!g
-
-s!<blockquote><p><strong>Redirection</strong>!<blockquote class="blue icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/redirect.png" alt="Redirection" /><h2>Redirection</h2><p>!g
diff --git a/Artworks/Docs/Texinfo/Default/en_US/manual.texinfo b/Artworks/Docs/Texinfo/Default/en_US/manual.texinfo
deleted file mode 100644
index 0a7f838..0000000
--- a/Artworks/Docs/Texinfo/Default/en_US/manual.texinfo
+++ /dev/null
@@ -1,74 +0,0 @@
-\input texinfo @c -*-texinfo-*-
-@c -- Header --------------------------------------------------
-
-@setfilename =MANUAL_NAME=.info
-@settitle =MANUAL_TITLE=
-@documentlanguage =LOCALE_LL=
-@afourpaper
-@finalout
-
-@c -- Variables -----------------------------------------------
-
-@set TCENTOS The Community Enterprise Operating System
-@set TCPROJ @url{http://www.centos.org/, The CentOS Project}
-@set TCWIKI @url{http://wiki.centos.org/, The CentOS Wiki}
-@set TCMLISTS @url{http://lists.centos.org/, The CentOS Mailing Lists}
-@set TCBUGS @url{http://bugs.centos.org/, The CentOS Bugs}
-@set TCMIRRORS @url{http://mirrors.centos.org/, The CentOS Mirrors}
-@set TCPLANET @url{http://planet.centos.org/, The CentOS Planet}
-@set TCFORUMS @url{http://forums.centos.org/, The CentOS Forums}
-@set TCINFOML @email{centos-info@@centos.org, The CentOS Information Mailing List}
-@set TCDEVSML @email{centos-devel@@centos.org, The CentOS Developers Mailing List}
-@set TCDOCSML @email{centos-docs@@centos.org, The CentOS Documentation Mailing List}
-@set TCARTWML @email{centos-artwork@@centos.org, The CentOS Artwork Mailing List}
-@set TCL10NML @email{centos-l10n@@centos.org, The CentOS Localization Mailing List}
-@set TCAR @url{https://projects.centos.org/svn/artwork/, The CentOS Artwork Repository}
-@set TCAS @url{https://projects.centos.org/trac/artwork/, The CentOS Artwork SIG}
-
-@c -- Summary description and copyright -----------------------
-
-@copying
-=MANUAL_ABSTRACT=
-
-Copyright @copyright{} =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
-
-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 @ref{GNU Free
-Documentation License}.
-@end copying
-
-@c -- Titlepage, contents, copyright ---------------------------
-
-@titlepage
-@title =MANUAL_TITLE=
-@subtitle =MANUAL_SUBTITLE=
-@author =COPYRIGHT_HOLDER=
-@page
-@vskip 0pt plus 1filll
-@insertcopying
-@end titlepage
-@contents
-
-@c -- `Top' node and master menu -------------------------------
-
-@ifnottex
-@node Top
-@top =MANUAL_TITLE=
-@insertcopying
-@end ifnottex
-
-@include =MANUAL_NAME=-menu.texinfo
-
-@c -- The body of the document --------------------------------
-
-@include =MANUAL_NAME=-nodes.texinfo
-
-@c -- The end of the document ---------------------------------
-
-@include Licenses.texinfo
-@include =MANUAL_NAME=-index.texinfo
-
-@bye
diff --git a/Artworks/Docs/Texinfo/Default/es_ES/Licenses-menu.texinfo b/Artworks/Docs/Texinfo/Default/es_ES/Licenses-menu.texinfo
deleted file mode 100755
index b8240ba..0000000
--- a/Artworks/Docs/Texinfo/Default/es_ES/Licenses-menu.texinfo
+++ /dev/null
@@ -1,4 +0,0 @@
-@menu
-* GNU General Public License::
-* GNU Free Documentation License::
-@end menu
diff --git a/Artworks/Docs/Texinfo/Default/es_ES/Licenses-nodes.texinfo b/Artworks/Docs/Texinfo/Default/es_ES/Licenses-nodes.texinfo
deleted file mode 100755
index e7eded9..0000000
--- a/Artworks/Docs/Texinfo/Default/es_ES/Licenses-nodes.texinfo
+++ /dev/null
@@ -1,9 +0,0 @@
-@node GNU General Public License
-@section Licencia Pública General de GNU
-@cindex Licencia pública general GNU
-@include Licenses/GPL.texinfo
-
-@node GNU Free Documentation License
-@section Licencia de Documentación Libre de GNU
-@cindex Licencia documentación libre GNU
-@include Licenses/GFDL.texinfo
diff --git a/Artworks/Docs/Texinfo/Default/es_ES/Licenses.texinfo b/Artworks/Docs/Texinfo/Default/es_ES/Licenses.texinfo
deleted file mode 100755
index be90966..0000000
--- a/Artworks/Docs/Texinfo/Default/es_ES/Licenses.texinfo
+++ /dev/null
@@ -1,5 +0,0 @@
-@node Licenses
-@appendix Licencias
-@cindex Licencias
-@include Licenses-menu.texinfo
-@include Licenses-nodes.texinfo
diff --git a/Artworks/Docs/Texinfo/Default/es_ES/Licenses/GFDL.texinfo b/Artworks/Docs/Texinfo/Default/es_ES/Licenses/GFDL.texinfo
deleted file mode 100755
index 8f789ec..0000000
--- a/Artworks/Docs/Texinfo/Default/es_ES/Licenses/GFDL.texinfo
+++ /dev/null
@@ -1,372 +0,0 @@
-@subheading Preámbulo
-
-El propósito de esta Licencia es permitir que un manual, libro de
-texto, u otro documento escrito sea «libre» en el sentido de libertad:
-asegurar a todo el mundo la libertad efectiva de copiarlo y
-redistribuirlo, con o sin modificaciones, de manera comercial o no. En
-segundo término, esta Licencia proporciona al autor y al editor una
-manera de obtener reconocimiento por su trabajo, sin que se le
-considere responsable de las modificaciones realizadas por otros.
-
-Esta Licencia es de tipo «copyleft», lo que significa que los trabajos
-derivados del documento deben a su vez ser libres en el mismo sentido.
-Complementa la Licencia Pública General de GNU, que es una licencia
-tipo copyleft diseñada para el software libre.
-
-Hemos diseñado esta Licencia para usarla en manuales de software
-libre, ya que el software libre necesita documentación libre: Un
-programa libre debe venir con los manuales que ofrezcan la mismas
-libertades que da el software. Pero esta licencia no se limita a
-manuales de software; puede ser usada para cualquier trabajo textual,
-sin tener en cuenta su temática o si se publica como libro impreso.
-Recomendamos esta licencia principalmente para trabajos cuyo fin sea
-instructivo o de referencia.
-
-@subheading 1. Aplicación y definiciones
-
-Esta Licencia se aplica a cualquier manual u otro trabajo que contenga
-un aviso colocado por el poseedor del copyright diciendo que puede
-distribuirse bajo los términos de esta Licencia. El «Documento»,
-abajo, se refiere a cualquier manual o trabajo. Cualquier miembro del
-público es un licenciatario,y será referido como «Usted».
-
-Una «Versión Modificada» del Documento significa cualquier trabajo que
-contenga el Documento o una porción del mismo, ya sea una copia
-literal o con modificaciones y/o traducciones a otro idioma.
-
-Una «Sección Secundaria» es un apéndice con título o una sección
-preliminar del Documento que trata exclusivamente de la relación entre
-los autores o editores y el tema general delDocumento que trata
-exclusivamente con la relación entre los editores o autores del
-Documento con el asunto general del Documento (o asuntos relacionados)
-y no contiene nada que pueda considerarse dentro del tema principal.
-(Por ejemplo, si el Documento es en parte un libro de texto de
-matemáticas, una Sección Secundaria no explicará nada de matemáticas.)
-La relación puede ser una conexión histórica con el asunto o temas
-relacionados, o una opinión legal, comercial, filosófica, ética o
-política acerca de ellos.
-
-Las «Secciones Invariantes» son ciertas Secciones Secundarias cuyos
-títulos son designados como Secciones Invariantes en la nota que
-indica que el Documento se publica bajo esta Licencia.
-
-Los «Textos de Cubierta» son ciertos pasajes cortos de texto que se
-listan como Textos de Cubierta Delantera o Textos de Cubierta Trasera
-en la nota que indica que el Documento se publica bajo esta Licencia.
-
-Una copia «Transparente» del Documento, significa una copia para
-lectura en máquina, representada en un formato cuya especificación
-está disponible al público en general, cuyo contenido puede ser visto
-y editados directamente con editores de texto genéricos o (para
-imágenes compuestas por píxeles) con programas genéricos de
-manipulación de imágenes o (para dibujos) con algún editor de dibujos
-ampliamente disponible, y que sea adecuado como entrada para
-formateadores de texto o para su traducción automática a formatos
-adecuados para formateadores de texto. Una copia hecha en un formato
-definido como Transparente, pero cuyo marcaje o ausencia de él haya
-sido diseñado para impedir o dificultar modificaciones posteriores por
-parte de los lectores no es Transparente. Una copia que no es
-«Transparente» se denomina «Opaca».
-
-Como ejemplos de formatos adecuados para copias Transparentes están
-ASCII puro sin marcaje, formato de entrada de Texinfo, formato de
-entrada de LaTeX, SGML o XML usando una DTD disponible públicamente, y
-HTML, PostScript o PDF simples, que sigan los estándares y diseños
-para que los modifiquen personas.Los formatos Opacos incluyen formatos
-propietarios que pueden ser leídos y editados únicamente en
-procesadores de textos propietarios, SGML o XML para los cuáles las
-DTD y/o herramientas de procesamiento no estén ampliamente
-disponibles, y HTML, PostScript o PDF generados por algunos
-procesadores de textos sólo como salida.
-
-La «Portada» significa, en un libro impreso, la página de título, más
-las páginas siguientes que sean necesarias para mantener legiblemente
-el material que esta Licencia requiere en la portada. Para trabajos en
-formatos que no tienen página de portada como tal, «Portada»significa
-el texto cercano a la aparición más prominente del título del
-trabajo,precediendo el comienzo del cuerpo del texto.
-
-@subheading 2. Copia literal
-
-Usted puede copiar y distribuir el Documento en cualquier medio, sea
-en forma comercial o no, siempre y cuando proporcione esta Licencia,
-las notas de copyright y la nota que indica que esta Licencia se
-aplica al Documento reproduciéndola en todas las copias y que usted no
-añada ninguna otra condición a las expuestas en esta Licencia. Usted
-no puede usar medidas técnicas para obstruir o controlar la lectura o
-copia posterior de las copias que usted haga o distribuya. Sin
-embargo, usted puede aceptar compensación a cambio de las copias. Si
-distribuye un número suficientemente grande de copias también deberá
-seguir las condiciones de la sección 3.
-
-Usted también puede prestar copias, bajo las mismas condiciones
-establecidas anteriormente, y puede exhibir copias públicamente.
-
-@subheading 3. Copiando en cantidad
-
-Si publica copias impresas del Documento que sobrepasen las 100, y la
-nota de licencia del Documento exige Textos de Cubierta, debe
-incluirlas copias con cubiertas que lleven en forma clara y legible
-todos esos Textos de Cubierta: Textos de Cubierta Delantera en la
-cubierta delantera y Textos de Cubierta Trasera en la cubierta
-trasera. Ambas cubiertas deben identificarlo a Usted clara y
-legiblemente como editor de tales copias. La cubierta debe mostrar el
-título completo con todas las palabras igualmente prominentes y
-visibles. Además puede añadir otro material en las cubiertas. Las
-copias con cambios limitados a las cubiertas, siempre que conserven el
-título del Documento y satisfagan estas condiciones, pueden
-considerarse como copias literales en todos los aspectos.
-
-Si los textos requeridos para la cubierta son muy voluminosos para que
-ajusten legiblemente, debe colocar los primeros (tantos como sea
-razonable colocar) en la verdadera cubierta y situar el resto en
-páginas adyacentes.
-
-Si Usted publica o distribuye copias Opacas del Documento cuya
-cantidad exceda las 100, debe incluir una copia Transparente, que
-pueda ser leída por una máquina, con cada copia Opaca, o bien mostrar,
-en cada copia Opaca, una dirección de red donde cualquier usuario de
-la misma tenga acceso por medio de protocolos públicos y
-estandarizados a una copia Transparente del Documento completa, sin
-material adicional. Si usted hace uso de la última opción, deberá
-tomar las medidas necesarias, cuando comience la distribución de las
-copias Opacas en cantidad, para asegurar que esta copia Transparente
-permanecerá accesible en el sitio establecido por lo menos un año
-después de la última vez que distribuya una copia Opaca de esa edición
-al público (directamente o a través de sus agentes o distribuidores).
-
-Se solicita, aunque no es requisito, que se ponga en contacto con los
-autores del Documento antes de redistribuir gran número de copias,
-para darles la oportunidad de que le proporcionen una versión
-actualizada del Documento.
-
-@subheading 4. Modificaciones
-
-Puede copiar y distribuir una Versión Modificada del Documento bajo
-las condiciones de las secciones 2 y 3 anteriores, siempre que Usted
-libere la Versión Modificada bajo esta misma Licencia, con la Versión
-Modificada haciendo el rol del Documento, por lo tanto dando Licencia
-de distribución y modificación de la Versión Modificada a quienquiera
-posea una copia de la misma. Además, debe hacer lo siguiente en la
-Versión Modificada:
-
-A. Usar en la Portada (y en las cubiertas, si hay alguna) un título
-distinto al del Documento y de sus versiones anteriores (que deberían,
-si hay alguna, estar listadas en la sección de Historia del
-Documento). Puede usar el mismo título de versiones anteriores al
-original siempre y cuando quien las publicó originalmente otorgue
-permiso.
-
-B. Listar en la Portada, como autores, una o más personas o entidades
-responsables de la autoría de las modificaciones de la Versión
-Modificada, junto con por lo menos cinco de los autores principales
-del Documento (todos sus autores principales, si hay menos de cinco),
-a menos que le eximan de tal requisito.
-
-C. Mostrar en la Portada como editor el nombre del editor de la
-Versión Modificada
-
-D. Conservar todas las notas de copyright del Documento.
-
-E. Añadir una nota de copyright apropiada a sus modificaciones,
-adyacente a las otras notas de copyright.
-
-F. Incluir, inmediatamente después de los avisos de copyright, una
-nota de licencia dando el permiso público para usar la Versión
-Modificada bajo los términos de esta Licencia, de la forma mostrada en
-el Adenda de más abajo.
-
-G. Incluir, inmediatamente después de ese aviso de licencia, la lista
-completa de Secciones invariantes y de los Textos de Cubierta que sean
-requeridos en el aviso de Licencia del Documento original.
-
-H. Incluir una copia sin modificación de esta Licencia.
-
-I. Conservar la sección titulada «Historia», conservar su Título y
-añadirle un elemento que declare al menos el título, el año, los
-nuevos autores y el editor de la Versión Modificada, tal como figuran
-en la Portada. Si no hay una sección titulada «Historia» en el
-Documento, crear una estableciendo el título, el año, los autores y el
-editor del Documento, tal como figuran en su Portada, añadiendo además
-un elemento describiendo la Versión Modificada, como se estableció en
-la sentencia anterior.
-
-J. Conservar la dirección en red, si la hay, dada en el Documento para
-el acceso público a una copia Transparente del mismo, así como las
-otras direcciones de red dadas en el Documento para versiones
-anteriores en las que estuviese basado. Pueden ubicarse en la sección
-«Historia». Se puede omitir la ubicación en red de un trabajo que haya
-sido publicado por lo menos cuatro años antes que el Documento mismo,
-o si el editor original de dicha versión da permiso.
-
-K. En cualquier sección titulada «Agradecimientos» o «Dedicatorias»,
-conservar el título de la sección y conservar en ella toda la
-sustancia y el tono de los agradecimientos y/o dedicatorias incluidas
-por cada contribuyente.
-
-L. Conservar todas las Secciones Invariantes del Documento, sin
-alterar su texto ni sus títulos. Los números de sección o equivalentes
-no se consideran parte de los títulos de la sección.
-
-M. Borrar cualquier sección titulada «Aprobaciones». Tales secciones
-no pueden estar incluidas en las Versiones Modificadas.
-
-N. No cambiar el título de ninguna sección existente a «Aprobaciones»
-ni a uno que entre en conflicto con el de alguna Sección Invariante.
-
-Si la Versión Modificada incluye secciones o apéndices nuevos que
-cualifiquen como Secciones Secundarias y no contienen ningún material
-copiado del Documento, puede opcionalmente designar algunas o todas
-esas secciones como invariantes. Para hacerlo, añada sus títulos a la
-lista de Secciones Invariantes en el aviso de licencia de la Versión
-Modificada. Tales títulos deben ser distintos de cualquier otro título
-de sección.
-
-Puede añadir una sección titulada «Aprobaciones», siempre que contenga
-únicamente aprobaciones de su Versión Modificada por otras fuentes
---por ejemplo, observaciones de compañeros o que el texto ha sido
-aprobado por una organización como definición oficial de un estándar.
-
-Puede añadir un pasaje de hasta cinco palabras como Texto de Cubierta
-Delantera y un pasaje de hasta 25 palabras como Texto de Cubierta
-Trasera al final de la lista de Texto de Cubierta en la Versión
-Modificada. Una entidad sólo puede añadir (o hacer que se añada) un
-pasaje al Texto de Cubierta Delantera y uno al de Cubierta Trasera. Si
-el Documento ya incluye un textos de cubiertas añadidos previamente
-por usted o por acuerdo previo con la entidad que usted representa,
-usted no puede añadir otro; pero puede reemplazar el anterior, con
-permiso explícito del editor anterior que agregó el texto anterior.
-
-Con esta Licencia ni los autores ni los editores del Documento dan
-permiso para usar sus nombres para publicidad ni para asegurar o
-implicar aprobación de cualquier Versión Modificada.
-
-@subheading 5. Combinación de documentos
-
-Usted puede combinar el Documento con otros documentos liberados bajo
-esta Licencia, bajo los términos definidos en la sección section 4 más
-arriba para versiones modificadas, siempre que incluya en la
-combinación todas las Secciones Invariantes de todos los documentos
-originales, sin modificaciones, y las liste todas como Secciones
-Invariantes de su trabajo combinado en su aviso de licencia.
-
-El trabajo combinado necesita contener solamente una copia de esta
-Licencia, y múltiples Secciones Invariantes idénticas pueden
-reemplazarse por una sola copia. Si hay múltiples Secciones
-Invariantes con el mismo nombre pero con contenidos diferentes, haga
-el título de cada una de estas secciones único añadiéndolo al final de
-este, entre paréntesis, el nombre del autor o de quien editó
-originalmente esa sección, si es conocido, o si no, un número único.
-Haga el mismo ajuste a los títulos de sección en la lista de Secciones
-Invariantes en la nota de licencia del trabajo combinado.
-
-En la combinación, debe combinar cualquier sección titulada «Historia»
-de los distintos documentos originales, formando una sección titulada
-«Historia»; de la misma forma, combine cualquier sección titulada
-«Reconocimientos» y cualquier sección titulada «Dedicatorias». Debe
-borrar todas las secciones tituladas «Aprobaciones».
-
-@subheading 6. Colecciones de documentos
-
-Puede hacer una colección que conste del Documento y de otros
-documentos publicados bajo esta Licencia, y reemplazar las copias
-individuales de esta Licencia en todos los documentos por una sola
-copia que esté incluida en la colección, siempre que siga las reglas
-de esta Licencia para cada copia literal de cada uno de los documentos
-en cualquiera de los demás aspectos.
-
-Puede extraer un solo documento de una de tales colecciones y
-distribuirlo individualmente bajo esta Licencia, siempre que inserte
-una copia de esta Licencia en el documento extraído, y siga esta
-Licencia en todos los demás aspectos relativos a la copia literal de
-dicho documento.
-
-@subheading 7. Agregación con trabajos independientes
-
-Una recopilación que conste del Documento o sus derivados y de otros
-documentos o trabajos separados e independientes, en cualquier soporte
-de almacenamiento o distribución, no cuenta como un todo como una
-Versión Modificada del Documento, siempre que no se reclame ningún
-derecho de copyright por la compilación. Dicha compilación se denomina
-un «agregado», y esta Licencia no se aplica a otros trabajos
-autocontenidos incluidos con el Documento. teniendo en cuenta que son
-compilados, si no son los mismos trabajos derivados del Documento. Si
-el requisito de Texto de Cubierta de la sección 3 es aplicable a estas
-copias del Documento, entonces si el Documento es menor que un cuarto
-del agregado completo, los Textos de Cubierta del Documento pueden
-colocarse en cubiertas que enmarquen solamente el Documento dentro del
-agregado. En caso contrario deben aparecer en cubiertas impresas
-enmarcando todo el agregado.
-
-@subheading 8. Traducción
-
-La Traducción se considera como un tipo de modificación, por lo que
-usted puede distribuir traducciones del Documento bajo los términos de
-la sección 4. El reemplazo las Secciones Invariantes por traducciones
-requiere permiso especial de los poseedores del copyright, pero usted
-puede incluir traducciones de algunas o todas las Secciones
-Invariantes junto con las versiones originales de las mismas. Puede
-incluir una traducción de esta Licencia, siempre que incluya también
-la versión original en inglés de esta Licencia. En caso de desacuerdo
-entre la traducción y la versión original en inglés de esta Licencia,
-la versión original en Inglés prevalecerá.
-
-@subheading 9. Terminación
-
-Usted no puede copiar, modificar, sublicenciar o distribuir el
-Documento salvo por lo permitido expresamente por esta Licencia.
-Cualquier otro intento de copia, modificación, sublicenciamiento o
-distribución del Documento es nulo, y dará por terminados
-automáticamente sus derechos bajo esa Licencia. Sin embargo, los
-terceros que hayan recibido copias, o derechos, de usted bajo esta
-Licencia no verán terminadas sus licencias, siempre que permanezcan en
-total conformidad con ella.
-
-@subheading Revisiones futuras de esta licencia
-
-La Free Software Foundation puede publicar versiones nuevas y
-revisadas de la Licencia de Documentación Libre GNU de vez en cuando.
-Dichas versiones nuevas serán similares en espíritu a la presente
-versión, pero pueden diferir en detalles para solucionar nuevos
-problemas o preocupaciones. Vea @url{http://www.gnu.org/copyleft/}.
-
-Cada versión de la Licencia tiene un número de versión que la
-distingue. Si el Documento especifica que se aplica una versión
-numerada en particular de esta licencia o «cualquier versión
-posterior», usted tiene la opción de seguir los términos y condiciones
-de la versión especificada o cualquiera posterior que haya sido
-publicada (no como borrador) por la Free Software Foundation. Si el
-Documento no especifica un número de versión de esta Licencia, puede
-escoger cualquier versión que haya sido publicada (no como borrador)
-por la Free Software Foundation.
-
-@subheading Adenda
-
-Para usar esta licencia en un documento que usted haya escrito,
-incluya una copia de la Licencia en el documento y ponga el siguiente
-copyright y notificación de licencia justo después de la página de
-título:
-
-@example
-Copyright © AÑO SU NOMBRE.
-
-Se otorga permiso para copiar, distribuir y/o modificar este documento
-bajo los términos de la Licencia de Documentación Libre de GNU,
-Versión 1.1 o cualquier otra versión posterior publicada por la
-Free Software Foundation; con las Secciones Invariantes siendo su
-LISTE SUS TÍTULOS, con Textos de Cubierta Delantera siendo LISTA, y
-con los Textos de Cubierta Trasera siendo LISTA. Una copia de la
-licencia está incluida en la sección titulada «GNU Free
-Documentation License».
-@end example
-
-Si no tiene Secciones Invariantes, escriba «sin Secciones Invariantes»
-en vez de decir cuáles son invariantes. Si no tiene Textos de Cubierta
-Frontal, escriba «sin Textos de Cubierta Frontal»; de la misma manera
-para Textos de Cubierta Trasera.
-
-Si su documento contiene ejemplos de código de programa no triviales,
-recomendamos liberar estos ejemplos en paralelo bajo la licencia de
-software libre que usted elija, como la Licencia Pública General de
-GNU (@pxref{GNU General Public License}), para permitir su uso en
-software libre.
diff --git a/Artworks/Docs/Texinfo/Default/es_ES/Licenses/GPL.texinfo b/Artworks/Docs/Texinfo/Default/es_ES/Licenses/GPL.texinfo
deleted file mode 100755
index 79680fe..0000000
--- a/Artworks/Docs/Texinfo/Default/es_ES/Licenses/GPL.texinfo
+++ /dev/null
@@ -1,329 +0,0 @@
-@subheading Preámbulo
-
-Las licencias que cubren la mayor parte del software están diseñadas
-para quitarle a usted la libertad de compartirlo y modificarlo. Por el
-contrario, la Licencia Pública General de GNU pretende garantizarle la
-libertad de compartir y modificar software libre, para asegurar que el
-software es libre para todos sus usuarios. Esta Licencia Pública
-General se aplica a la mayor parte del software del la Free Software
-Foundation y a cualquier otro programa si sus autores se comprometen a
-utilizarla. (Existe otro software de la Free Software Foundation que
-está cubierto por la Licencia Pública General de GNU para
-Bibliotecas). Si quiere, también puede aplicarla a sus propios
-programas.
-
-Cuando hablamos de software libre, estamos refiriéndonos a libertad,
-no a precio. Nuestras Licencias Públicas Generales están diseñadas
-para asegurarnos de que tenga la libertad de distribuir copias de
-software libre (y cobrar por ese servicio si quiere), de que reciba el
-código fuente o que pueda conseguirlo si lo quiere, de que pueda
-modificar el software o usar fragmentos de él en programas nuevos
-libres, y de que sepa que puede hacer todas estas cosas.
-
-Para proteger sus derechos necesitamos algunas restricciones que
-prohíban a cualquiera negarle a usted estos derechos o pedirle que
-renuncie a ellos. Estas restricciones se traducen en ciertas
-obligaciones que le afectan si distribuye copias del software, o si lo
-modifica.
-
-Por ejemplo, si distribuye copias de uno de estos programas, sea
-gratuitamente, o a cambio de una contraprestación, debe dar a los
-receptores todos los derechos que tiene. Debe asegurarse de que ellos
-también reciben, o pueden conseguir, el código fuente. Y debe
-mostrarles estas condiciones de forma que conozcan sus derechos.
-
-Protegemos sus derechos con la combinación de dos medidas:
-
-@itemize
-@item Derechos de copia del software (copyright), y
-@item Le ofrecemos esta licencia, que le da permiso legal para copiar,
-distribuir y/o modificar el software.
-@end itemize
-
-También, para la protección de cada autor y la nuestra propia,
-queremos asegurarnos de que todo el mundo comprende que no se
-proporciona ninguna garantía para este software libre. Si el software
-se modifica por cualquiera y éste a su vez lo distribuye, queremos que
-sus receptores sepan que lo que tienen no es el original, de forma que
-cualquier problema introducido por otros no afecte a la reputación de
-los autores originales.
-
-Finalmente, cualquier programa libre está constantemente amenazado por
-patentes sobre el software. Queremos evitar el peligro de que los
-redistribuidores de un programa libre obtengan patentes por su cuenta,
-convirtiendo de facto el programa en propietario. Para evitar esto,
-hemos dejado claro que cualquier patente debe ser pedida para el uso
-libre de cualquiera, o no ser pedida.
-
-Los términos precisos y las condiciones para la copia, distribución y
-modificación se exponen a continuación.
-
-@subheading TÉRMINOS Y CONDICIONES PARA LA COPIA, DISTRIBUCIÓN Y MODIFICACIÓN
-
-@subsubheading Sección 0
-
-Esta Licencia se aplica a cualquier programa u otro tipo de obra que
-contenga una notificación colocada por el propietario del copyright
-diciendo que puede distribuirse bajo los términos de esta Licencia
-Pública General. El «Programa», en adelante, se referirá a cualquier
-programa u obra, y «obra basada en el Programa» se referirá bien al
-Programa o a cualquier trabajo derivado de él según la ley de derechos
-de autor (copyright): Esto es, una obra o trabajo que contenga el
-programa o una porción de él, bien en forma literal o con
-modificaciones y/o traducido en otro lenguaje. Aquí y después, la
-traducción está incluida sin limitación en el término «modificación».
-Cada concesionario (licenciatario) será denominado «usted».
-
-Cualquier otra actividad que no sea la copia, distribución o
-modificación no está cubierta por esta Licencia, está fuera de su
-ámbito. El acto de ejecutar el Programa no está restringido, y los
-resultados del Programa están cubiertos únicamente si sus contenidos
-constituyen un trabajo basado en el Programa, independientemente de
-haberlo producido mediante la ejecución del programa. El que esto se
-cumpla, depende de lo que haga el programa.
-
-@subsubheading Sección 1
-
-Usted puede copiar y distribuir copias literales del código fuente del
-Programa, según lo has recibido, en cualquier medio, supuesto que de
-forma adecuada y bien visible publique en cada copia un anuncio de
-copyright adecuado y un repudio de garantía, mantenga intactos todos
-los anuncios que se refieran a esta Licencia y a la ausencia de
-garantía, y proporcione a cualquier otro receptor del programa una
-copia de esta Licencia junto con el Programa.
-
-Puede cobrar un precio por el acto físico de transferir una copia, y
-puede, según su libre albedrío, ofrecer garantía a cambio de unos
-honorarios.
-
-@subsubheading Sección 2
-
-Puede modificar su copia o copias del Programa o de cualquier porción
-de él, formando de esta manera un trabajo basado en el Programa, y
-copiar y distribuir esa modificación o trabajo bajo los términos de la
-Sección 1 anterior, probado que además usted cumpla con todas las
-siguientes condiciones:
-
-@enumerate
-@item Debe hacer que los ficheros modificados lleven anuncios
-prominentes indicando que los ha cambiado y la fecha de cualquier
-cambio.
-
-@item Debe hacer que cualquier trabajo que distribuya o publique y que
-en todo o en parte contenga o sea derivado del Programa o de cualquier
-parte de él sea licenciada como un todo, sin carga alguna, a todas las
-terceras partes y bajo los términos de esta Licencia.
-
-@item 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.
-
-Excepción: Si el propio Programa es interactivo pero normalmente no
-muestra ese anuncio, no se requiere que su trabajo basado en el
-Programa muestre ningún anuncio.
-
-@end enumerate
-
-Estos requisitos se aplican al trabajo modificado como un todo. Si
-partes identificables de ese trabajo no son derivadas del Programa, y
-pueden, razonablemente, ser consideradas trabajos independientes y
-separados por ellos mismos, entonces esta Licencia y sus términos no
-se aplican a esas partes cuando sean distribuidas como trabajos
-separados. Pero cuando distribuya esas mismas secciones como partes de
-un todo que es un trabajo basado en el Programa, la distribución del
-todo debe ser según los términos de esta licencia, cuyos permisos para
-otros licenciatarios se extienden al todo completo, y por lo tanto a
-todas y cada una de sus partes, con independencia de quién la
-escribió.
-
-Por lo tanto, no es la intención de este apartado reclamar derechos o
-desafiar sus derechos sobre trabajos escritos totalmente por usted
-mismo. El intento es ejercer el derecho a controlar la distribución de
-trabajos derivados o colectivos basados en el Programa.
-
-Además, el simple hecho de reunir un trabajo no basado en el Programa
-con el Programa (o con un trabajo basado en el Programa) en un volumen
-de almacenamiento o en un medio de distribución no hace que dicho
-trabajo entre dentro del ámbito cubierto por esta Licencia.
-
-@subsubheading Sección 3
-
-Puede copiar y distribuir el Programa (o un trabajo basado en él,
-según se especifica en la Sección 2, como código objeto o en formato
-ejecutable según los términos de las Secciones 1 y 2 anteriores,
-supuesto que además cumpla una de las siguientes condiciones:
-
-@enumerate
-
-@item Acompañarlo con el código fuente leíble completo
-correspondiente, leíble por máquinas, que debe ser distribuido según
-los términos las Secciones 1 y 2 mencionadas antes en un medio
-habitualmente utilizado para el intercambio de software, o,
-
-@item Acompañarlo con una oferta por escrito, válida durante al menos
-tres años, de proporcionar a cualquier tercera parte una copia
-completa en formato electrónico del código fuente correspondiente, a
-un coste no mayor que el de realizar físicamente la distribución del
-fuente, que será distribuido bajo las condiciones descritas en los
-apartados 1 y 2 anteriores, en un medio habitualmente utilizado para
-el intercambio de programas, o
-
-@item Acompañarlo con la información que recibiste ofreciendo
-distribuir el código fuente correspondiente. (Esta opción se permite
-sólo para distribución no comercial y sólo si usted recibió el
-programa como código objeto o en formato ejecutable con tal oferta, de
-acuerdo con la Subsección b anterior).
-@end enumerate
-
-Por código fuente de un trabajo se entiende la forma preferida del
-trabajo cuando se le hacen modificaciones. Para un trabajo ejecutable,
-se entiende por código fuente completo todo el código fuente para
-todos los módulos que contiene, más cualquier fichero asociado de
-definición de interfaces, más los guiones utilizados para controlar la
-compilación e instalación del ejecutable. Como excepción especial el
-código fuente distribuido no necesita incluir nada que sea distribuido
-normalmente (bien como fuente, bien en forma binaria) con los
-componentes principales (compilador, núcleo y similares) del sistema
-operativo en el cual funciona el ejecutable, a no ser que el propio
-componente acompañe al ejecutable.
-
-Si la distribución del ejecutable o del código objeto se hace mediante
-la oferta acceso para copiarlo de un cierto lugar, entonces se
-considera la oferta de acceso para copiar el código fuente del mismo
-lugar como distribución del código fuente, incluso aunque terceras
-partes no estén forzadas a copiar el fuente junto con el código
-objeto.
-
-@subsubheading Sección 4
-
-No puede copiar, modificar, sublicenciar o distribuir el Programa
-excepto como prevé expresamente esta Licencia. Cualquier intento de
-copiar, modificar sublicenciar o distribuir el Programa de otra forma
-es inválida, y hará que cesen automáticamente los derechos que te
-proporciona esta Licencia. En cualquier caso, las partes que hayan
-recibido copias o derechos de usted bajo esta Licencia no cesarán en
-sus derechos mientras esas partes continúen cumpliéndola. 5Sección 5
-
-No está obligado a aceptar esta licencia, ya que no la ha firmado. Sin
-embargo, no hay hada más que le proporcione permiso para modificar o
-distribuir el Programa o sus trabajos derivados. Estas acciones están
-prohibidas por la ley si no acepta esta Licencia. Por lo tanto, si
-modifica o distribuye el Programa (o cualquier trabajo basado en el
-Programa), está indicando que acepta esta Licencia para poder hacerlo,
-y todos sus términos y condiciones para copiar, distribuir o modificar
-el Programa o trabajos basados en él. 6Sección 6
-
-Cada vez que redistribuya el Programa (o cualquier trabajo basado en
-el Programa), el receptor recibe automáticamente una licencia del
-licenciatario original para copiar, distribuir o modificar el
-Programa, de forma sujeta a estos términos y condiciones. No puede
-imponer al receptor ninguna restricción más sobre el ejercicio de los
-derechos aquí garantizados. No es usted responsable de hacer cumplir
-esta licencia por terceras partes. 7Sección 7
-
-Si como consecuencia de una resolución judicial o de una alegación de
-infracción de patente o por cualquier otra razón (no limitada a
-asuntos relacionados con patentes) se le imponen condiciones (ya sea
-por mandato judicial, por acuerdo o por cualquier otra causa) que
-contradigan las condiciones de esta Licencia, ello no le exime de
-cumplir las condiciones de esta Licencia. Si no puede realizar
-distribuciones de forma que se satisfagan simultáneamente sus
-obligaciones bajo esta licencia y cualquier otra obligación pertinente
-entonces, como consecuencia, no puede distribuir el Programa de
-ninguna forma. Por ejemplo, si una patente no permite la
-redistribución libre de derechos de autor del Programa por parte de
-todos aquellos que reciban copias directa o indirectamente a través de
-usted, entonces la única forma en que podría satisfacer tanto esa
-condición como esta Licencia sería evitar completamente la
-distribución del Programa.
-
-Si cualquier porción de este apartado se considera inválida o
-imposible de cumplir bajo cualquier circunstancia particular ha de
-cumplirse el resto y la sección por entero ha de cumplirse en
-cualquier otra circunstancia.
-
-No es el propósito de este apartado inducirle a infringir ninguna
-reivindicación de patente ni de ningún otro derecho de propiedad o
-impugnar la validez de ninguna de dichas reivindicaciones. Este
-apartado tiene el único propósito de proteger la integridad del
-sistema de distribución de software libre, que se realiza mediante
-prácticas de licencia pública. Mucha gente ha hecho contribuciones
-generosas a la gran variedad de software distribuido mediante ese
-sistema con la confianza de que el sistema se aplicará
-consistentemente. Será el autor/donante quien decida si quiere
-distribuir software mediante cualquier otro sistema y una licencia no
-puede imponer esa elección.
-
-Este apartado pretende dejar completamente claro lo que se cree que es
-una consecuencia del resto de esta Licencia.
-
-@subsubheading Sección 8
-
-Si la distribución y/o uso de el Programa está restringida en ciertos
-países, bien por patentes o por interfaces bajo copyright, el tenedor
-del copyright que coloca este Programa bajo esta Licencia puede añadir
-una limitación explícita de distribución geográfica excluyendo esos
-países, de forma que la distribución se permita sólo en o entre los
-países no excluidos de esta manera. En ese caso, esta Licencia
-incorporará la limitación como si estuviese escrita en el cuerpo de
-esta Licencia. 9Sección 9
-
-La Free Software Foundation puede publicar versiones revisadas y/o
-nuevas de la Licencia Pública General de tiempo en tiempo. Dichas
-nuevas versiones serán similares en espíritu a la presente versión,
-pero pueden ser diferentes en detalles para considerar nuevos
-problemas o situaciones.
-
-Cada versión recibe un número de versión que la distingue de otras. Si
-el Programa especifica un número de versión de esta Licencia que se
-aplica aplica a éste y a «cualquier versión posterior», usted tiene la
-opción de seguir los términos y condiciones, bien de esa versión, bien
-de cualquier versión posterior publicada por la Free Software
-Foundation. Si el Programa no especifica un número de versión de esta
-Licencia, usted puede escoger cualquier versión publicada por la Free
-Software Foundation.
-
-@subsubheading Sección 10
-
-Si quiere incorporar partes del Programa en otros programas libres
-cuyas condiciones de distribución son diferentes, escribe al autor
-para pedirle permiso. Si el software tiene copyright de la Free
-Software Foundation, escribe a la Free Software Foundation: algunas
-veces hacemos excepciones en estos casos. Nuestra decisión estará
-guiada por el doble objetivo de de preservar la libertad de todos los
-derivados de nuestro software libre y promover el que se comparta y
-reutilice el software en general.
-
-@subsubheading AUSENCIA DE GARANTÍA
-
-Sección 11
-
-DEBIDO A QUE EL PROGRAMA SE LICENCIA LIBRE DE CARGAS, NO SE OFRECE
-NINGUNA GARANTÍA SOBRE EL PROGRAMA, EN TODA LA EXTENSIÓN PERMITIDA POR
-LA LEGISLACIÓN APLICABLE. EXCEPTO CUANDO SE INDIQUE DE OTRA FORMA POR
-ESCRITO, LOS PROPIETARIOS DEL COPYRIGHT Y/U OTRAS PARTES PROPORCIONAN
-EL PROGRAMA «TAL CUAL», SIN GARANTÍA DE NINGUNA CLASE, BIEN EXPRESA O
-IMPLÍCITA, CON INCLUSIÓN, PERO SIN LIMITACIÓN A LAS GARANTÍAS
-MERCANTILES IMPLÍCITAS O A LA CONVENIENCIA PARA UN PROPÓSITO
-PARTICULAR. CUALQUIER RIESGO REFERENTE A LA CALIDAD Y PRESTACIONES DEL
-PROGRAMA ES ASUMIDO POR USTED. SI SE PROBASE QUE EL PROGRAMA ES
-DEFECTUOSO, USTED ASUME EL COSTE DE CUALQUIER SERVICIO, REPARACIÓN O
-CORRECCIÓN NECESARIO.
-
-@subsubheading Sección 12
-
-EN NINGÚN CASO, SALVO QUE LO REQUIERA LA LEGISLACIÓN APLICABLE O HAYA
-SIDO ACORDADO POR ESCRITO, NINGÚN TENEDOR DEL COPYRIGHT NI NINGUNA
-OTRA PARTE QUE MODIFIQUE Y/O REDISTRIBUYA EL PROGRAMA SEGÚN SE PERMITE
-EN ESTA LICENCIA SERÁ RESPONSABLE ANTE USTED POR DAÑOS, INCLUYENDO
-CUALQUIER DAÑO GENERAL, ESPECIAL, INCIDENTAL O RESULTANTE PRODUCIDO
-POR EL USO O LA IMPOSIBILIDAD DE USO DEL PROGRAMA (CON INCLUSIÓN, PERO
-SIN LIMITACIÓN A LA PÉRDIDA DE DATOS O A LA GENERACIÓN INCORRECTA DE
-DATOS O A PÉRDIDAS SUFRIDAS POR USTED O POR TERCERAS PARTES O A UN
-FALLO DEL PROGRAMA AL FUNCIONAR EN COMBINACIÓN CON CUALQUIER OTRO
-PROGRAMA), INCLUSO SI DICHO TENEDOR U OTRA PARTE HA SIDO ADVERTIDO DE
-LA POSIBILIDAD DE DICHOS DAÑOS.
diff --git a/Artworks/Docs/Texinfo/Default/es_ES/manual-index.texinfo b/Artworks/Docs/Texinfo/Default/es_ES/manual-index.texinfo
deleted file mode 100755
index bed8139..0000000
--- a/Artworks/Docs/Texinfo/Default/es_ES/manual-index.texinfo
+++ /dev/null
@@ -1,8 +0,0 @@
-@node Index
-@unnumbered Índice
-@syncodeindex fn cp
-@syncodeindex vr cp
-@syncodeindex ky cp
-@syncodeindex pg cp
-@syncodeindex tp cp
-@printindex cp
diff --git a/Artworks/Docs/Texinfo/Default/es_ES/manual-init.pl b/Artworks/Docs/Texinfo/Default/es_ES/manual-init.pl
deleted file mode 100755
index d8e2045..0000000
--- a/Artworks/Docs/Texinfo/Default/es_ES/manual-init.pl
+++ /dev/null
@@ -1,119 +0,0 @@
-# This file extends the '../manual-init.pl' initialization file to # provide Spanish translation messages for `texi2html-1.76-4.fc6'.
-# ----------------------------------------------------------------------
-# $Id$
-# ----------------------------------------------------------------------
-
-$LANGUAGES->{'es'} = {
- ' The buttons in the navigation panels have the following meaning:' => 'Los botones en el panel de navegación tienen el significado siguiente:',
- ' where the @strong{ Example } assumes that the current position is at @strong{ Subsubsection One-Two-Three } of a document of the following structure:' => 'donde el @strong{Ejemplo} asume que la posición actual es en @strong{Subsubsección Uno-Dos-Tres}',
- ' Up ' => 'Arriba',
- '%{acronym_like} (%{explanation})' => '',
- '%{month}, %{day} %{year}' => '',
- '%{name} of %{class}' => '%{name} de %{class}',
- '%{name} on %{class}' => '%{name} en %{class}',
- '%{node_file_href}' => '',
- '%{node_file_href} @cite{%{book}}' => '',
- '%{node_file_href} section `%{section}\' in @cite{%{book}}' => 'sección %{node_file_href} `%{section}\' en @cite{%{book}}',
- '%{reference_name}' => '',
- '%{style} %{number}' => '',
- '%{style}: %{caption_first_line}' => '',
- '%{style}: %{shortcaption_first_line}' => '',
- '@b{%{quotation_arg}:} ' => '',
- '@cite{%{book}}' => '',
- 'About This Document' => 'Acerca de este documento',
- 'April' => 'abril',
- 'August' => 'agosto',
- 'Button' => 'Botón',
- 'Contents' => 'Contenidos',
- 'Current Position' => 'Posición actual',
- 'December' => 'diciembre',
- 'February' => 'febrero',
- 'Footnotes' => 'Pie de página',
- 'From 1.2.3 go to' => 'Desde 1.2.3 va a',
- 'Go to' => 'Ir a',
- 'Index' => 'Índice',
- 'Index Entry' => 'Entrada índice',
- 'January' => 'enero',
- 'July' => 'julio',
- 'Jump to' => 'Saltar a',
- 'June' => 'junio',
- 'March' => 'marzo',
- 'May' => 'mayo',
- 'Menu:' => 'Menú:',
- 'Name' => 'Nombre',
- 'Next' => 'Siguiente',
- 'November' => 'noviembre',
- 'October' => 'octubre',
- 'Overview' => 'Introducción',
- 'Overview:' => 'Introducción:',
- 'Prev' => 'Anterior',
- 'Section' => 'Sección',
- 'Section One' => 'Sección Uno',
- 'See %{node_file_href}' => 'Véase %{node_file_href}',
- 'See %{node_file_href} @cite{%{book}}' => 'Véase %{node_file_href} @cite{%{book}}',
- 'See %{node_file_href} section `%{section}\' in @cite{%{book}}' => 'Véase la sección %{node_file_href} `%{section}\' en @cite{%{book}}',
- 'See %{reference_name}' => 'Véase %{reference_name}',
- 'See @cite{%{book}}' => 'Véase @cite{%{book}}',
- 'See section %{reference_name}' => 'Véase la sección %{reference_name}',
- 'See section `%{section}\' in @cite{%{book}}' => 'Véase la sección `%{section}\' en @cite{%{book}}',
- 'September' => 'septiembre',
- 'Short Table of Contents' => 'Resumen del Contenido',
- 'Subsection One-Four' => 'Subsección Uno-Cuatro',
- 'Subsection One-One' => 'Subsección Uno-Uno',
- 'Subsection One-Three' => 'Subsección Uno-Tres',
- 'Subsection One-Two' => 'Subsección Uno-Dos',
- 'Subsubsection One-Two-Four' => 'Subsubsección Uno-Dos-Cuatro',
- 'Subsubsection One-Two-One' => 'Subsubsección Uno-Dos-Uno',
- 'Subsubsection One-Two-Three' => 'Subsubsección Uno-Dos-Tress',
- 'Subsubsection One-Two-Two' => 'Subsubsección Uno-Dos-Dos',
- 'T2H_today' => '',
- 'Table of Contents' => 'Tabla de contenidos',
- 'This document was generated by @emph{%{user}} on @emph{%{date}} using @uref{%{program_homepage}, @emph{%{program}}}.' => 'Este documento fue generado pr @emph{%{user}} en @emph{%{date}} usando @uref{%{program_homepage}, @emph{%{program}}}.',
- 'This document was generated by @emph{%{user}} using @uref{%{program_homepage}, @emph{%{program}}}.' => 'Este documento fue generado por @emph{%{user}} usando @uref{%{program_homepage}, @emph{%{program}}}.',
- 'This document was generated on @i{%{date}} using @uref{%{program_homepage}, @i{%{program}}}.' => 'Este documento fue generado en @i{%{date}} usando @uref{%{program_homepage}, @i{%{program}}}.',
- 'This document was generated using @uref{%{program_homepage}, @emph{%{program}}}.' => 'Este documento fue generado usando @uref{%{program_homepage}, @emph{%{program}}}.',
- 'Top' => 'Inicio',
- 'Untitled Document' => 'Documento sintítulo',
- 'about (help)' => 'Acerca de (ayuda)',
- 'beginning of this chapter or previous chapter' => 'Inicio del capítulo o capítulo anterior',
- 'by @emph{%{user}}' => 'por @emph{%{user}}',
- 'by @emph{%{user}} on @emph{%{date}}' => 'por @emph{%{user}} el @emph{%{date}}',
- 'cover (top) of document' => 'Cubierta (inicio) del documento',
- 'current' => 'actual',
- 'current section' => 'Sección actual',
- 'first section in reading order' => 'Primera sección en orden de lectura',
- 'following node' => 'Nodo siguiente',
- 'index' => 'Índice',
- 'last section in reading order' => 'Última sección en orden de lectura',
- 'next chapter' => 'Capítulo siguiente',
- 'next node' => 'Nodo siguiente',
- 'next section in reading order' => 'Sección siguiente en order de lectura',
- 'next section on same level' => 'Sección siguiente en el mismo nivel',
- 'node following in node reading order' => 'siguiente nodo en orden de lectura',
- 'node up' => 'nodo arriba',
- 'on @emph{%{date}}' => 'el @emph{%{date}}',
- 'previous node' => 'nodo anterior',
- 'previous section in reading order' => 'Sección anterior en orden de lectura',
- 'previous section on same level' => 'Sección anterior en el mismo nivel',
- 'section `%{section}\' in @cite{%{book}}' => 'sección `%{section}\' en @cite{%{book}}',
- 'see %{node_file_href}' => 'Véase %{node_file_href}',
- 'see %{node_file_href} @cite{%{book}}' => 'Véase %{node_file_href} @cite{%{book}}',
- 'see %{node_file_href} section `%{section}\' in @cite{%{book}}' => 'Véase %{node_file_href} sección `%{section}\' en @cite{%{book}}',
- 'see %{reference_name}' => 'Véase %{reference_name}',
- 'see @cite{%{book}}' => 'Véase @cite{%{book}}',
- 'see section %{reference_name}' => 'véase sección %{reference_name}',
- 'see section `%{section}\' in @cite{%{book}}' => 'véase sección `%{section}\' en @cite{%{book}}',
- 'short table of contents' => 'resumen del contenido',
- 'table of contents' => 'Tabla de contenidos',
- 'unknown' => 'desconocido',
- 'up node' => 'nodo superior',
- 'up section' => 'Sección superior'
- };
-
-$T2H_OBSOLETE_STRINGS->{'es'} = {
- 'See' => 'Véase',
- 'section' => 'sección',
- 'see' => 'véase'
- };
-
-return 1;
diff --git a/Artworks/Docs/Texinfo/Default/es_ES/manual-menu.texinfo b/Artworks/Docs/Texinfo/Default/es_ES/manual-menu.texinfo
deleted file mode 100644
index 0afc9ff..0000000
--- a/Artworks/Docs/Texinfo/Default/es_ES/manual-menu.texinfo
+++ /dev/null
@@ -1,4 +0,0 @@
-@menu
-* Licenses::
-* Index::
-@end menu
diff --git a/Artworks/Docs/Texinfo/Default/es_ES/manual-nodes.texinfo b/Artworks/Docs/Texinfo/Default/es_ES/manual-nodes.texinfo
deleted file mode 100644
index e69de29..0000000
--- a/Artworks/Docs/Texinfo/Default/es_ES/manual-nodes.texinfo
+++ /dev/null
diff --git a/Artworks/Docs/Texinfo/Default/es_ES/manual.conf b/Artworks/Docs/Texinfo/Default/es_ES/manual.conf
deleted file mode 100755
index b4f9ae4..0000000
--- a/Artworks/Docs/Texinfo/Default/es_ES/manual.conf
+++ /dev/null
@@ -1,43 +0,0 @@
-# Este fichero controla la configuración del manual. Este fichero
-# está dividido en diferentes secciones de configuración (e.g., `main'
-# para organizar la configuración principal y `templates' para
-# organizar la relación de asiganación plantillas-sección). Cada
-# sección de configuración está organizada en pares de valores
-# `variable = valor' usados para describir las preferencias de
-# configuración.
-# ----------------------------------------------------------------------
-# $Id$
-# ----------------------------------------------------------------------
-
-[main]
-
-# Especifica el trasfondo de documentación usado por el manual. Este
-# es el formato utilizado para redactar los ficheros fuentes del
-# manual de documentación.
-manual_format = "texinfo"
-
-# Especifica el estilo de títulos utilizados por las secciones del
-# manual. Los valores posibles para esta opción son `cap-each-word'
-# para escribir la primera letra de cada palabra en el título con
-# mayúscula y el resto en minúscula, `cap-first-word' para escribir
-# solo la primera letra del título en mayúscula y el resto en
-# minúscula; y `directory' para transformar el título en un camino de
-# directorio.
-manual_section_style = "cap-each-word"
-
-# Especifica el order con que se muestran las secciones en el manual.
-# Los valores posibles para esta opción son `created' para ubicar las
-# nuevas secciones creadas en orden de creación, `ordered' para
-# ordenar las secciones alfabéticamente sin importar el orden con el
-# cual fueron creadas; y `reversed' lo contrario the `ordered'.
-manual_section_order = "created"
-
-[templates]
-
-# Especifica la relación entre los ficheros de plantilla y los
-# ficheros de definición de secciones en el manual. La definición de
-# las plantillas se escriben en forma de camino relativo en el
-# izquierdo y la definición de secciones en forma de expresión regular
-# en el lado derecho.
-Chapters/section-functions.texinfo = "^.+-functions-[[:alnum:]]+\.texinfo$"
-Chapters/section.texinfo = "^.+\.texinfo$"
diff --git a/Artworks/Docs/Texinfo/Default/es_ES/manual.sed b/Artworks/Docs/Texinfo/Default/es_ES/manual.sed
deleted file mode 100644
index baa4b5b..0000000
--- a/Artworks/Docs/Texinfo/Default/es_ES/manual.sed
+++ /dev/null
@@ -1,40 +0,0 @@
-#!/bin/sed
-#
-# repository.sed -- This file provide Spanish transformations for
-# texi2html outupt, based on The CentOS Project CSS definitions.
-#
-# Copyright (C) 2009-2012 The CentOS Project
-#
-# 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., 59 Temple Place, Suite 330, Boston, MA 02111-1307
-# USA.
-#
-# ----------------------------------------------------------------------
-# $Id$
-# ----------------------------------------------------------------------
-
-# Quotations.
-s!<blockquote><p><strong>Nota</strong>!<blockquote class="blue icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/note.png" alt="Info" /><h2>Nota</h2><p>!g
-
-s!<blockquote><p><strong>Advertencia</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/warning.png" alt="Advertencia" /><h2>Advertencia</h2><p>!g
-
-s!<blockquote><p><strong>Importante</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/star.png" alt="Importante" /><h2>Importante</h2><p>!g
-
-s!<blockquote><p><strong>Idea</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/tip.png" alt="Idea" /><h2>Idea</h2><p>!g
-
-s!<blockquote><p><strong>Precaución</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/caution.png" alt="Precaución" /><h2>Precaución</h2><p>!g
-
-s!<blockquote><p><strong>Convensión</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/ruler.png" alt="Convensión" /><h2>Convensión</h2><p>!g
-
-s!<blockquote><p><strong>Redirección</strong>!<blockquote class="blue icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/redirect.png" alt="Redirección" /><h2>Redirección</h2><p>!g
diff --git a/Artworks/Docs/Texinfo/Default/es_ES/manual.texinfo b/Artworks/Docs/Texinfo/Default/es_ES/manual.texinfo
deleted file mode 100644
index c21f607..0000000
--- a/Artworks/Docs/Texinfo/Default/es_ES/manual.texinfo
+++ /dev/null
@@ -1,75 +0,0 @@
-\input texinfo @c -*-texinfo-*-
-@c -- Header --------------------------------------------------
-
-@setfilename =MANUAL_NAME=.info
-@settitle =MANUAL_TITLE=
-@documentlanguage es
-@afourpaper
-@finalout
-
-@c -- Variables -----------------------------------------------
-
-@set TCENTOS The Community Enterprise Operating System
-@set TCPROJ @url{http://www.centos.org/, The CentOS Project}
-@set TCWIKI @url{http://wiki.centos.org/, The CentOS Wiki}
-@set TCMLISTS @url{http://lists.centos.org/, The CentOS Mailing Lists}
-@set TCBUGS @url{http://bugs.centos.org/, The CentOS Bugs}
-@set TCMIRRORS @url{http://mirrors.centos.org/, The CentOS Mirrors}
-@set TCPLANET @url{http://planet.centos.org/, The CentOS Planet}
-@set TCFORUMS @url{http://forums.centos.org/, The CentOS Forums}
-@set TCINFOML @email{centos-info@@centos.org, The CentOS Information Mailing List}
-@set TCDEVSML @email{centos-devel@@centos.org, The CentOS Developers Mailing List}
-@set TCDOCSML @email{centos-docs@@centos.org, The CentOS Documentation Mailing List}
-@set TCARTWML @email{centos-artwork@@centos.org, The CentOS Artwork Mailing List}
-@set TCL10NML @email{centos-l10n@@centos.org, The CentOS Localization Mailing List}
-@set TCAR @url{https://projects.centos.org/svn/artwork/, The CentOS Artwork Repository}
-@set TCAS @url{https://projects.centos.org/trac/artwork/, The CentOS Artwork SIG}
-
-@c -- Summary description and copyright -----------------------
-
-@copying
-=MANUAL_ABSTRACT=
-
-Copyright @copyright{} =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
-
-Se otorga permiso para copiar, distribuir y/o modificar este documento
-bajo los términos de la Licencia de Documentación Libre de GNU,
-Versión 1.1 o cualquier otra versión posterior publicada por la Free
-Software Foundation; con las Secciones Invariantes, con Textos de
-Cubierta Delantera, y con los Textos de Cubierta Trasera. Una copia de
-la licencia está incluida en la sección titulada @ref{GNU Free
-Documentation License}.
-@end copying
-
-@c -- Titlepage, contents, copyright ---------------------------
-
-@titlepage
-@title =MANUAL_TITLE=
-@subtitle =MANUAL_SUBTITLE=
-@author =COPYRIGHT_HOLDER=
-@page
-@vskip 0pt plus 1filll
-@insertcopying
-@end titlepage
-@contents
-
-@c -- `Top' node and master menu -------------------------------
-
-@ifnottex
-@node Top
-@top =MANUAL_TITLE=
-@insertcopying
-@end ifnottex
-
-@include =MANUAL_NAME=-menu.texinfo
-
-@c -- The body of the document --------------------------------
-
-@include =MANUAL_NAME=-nodes.texinfo
-
-@c -- The end of the document ---------------------------------
-
-@include Licenses.texinfo
-@include =MANUAL_NAME=-index.texinfo
-
-@bye
diff --git a/Artworks/Docs/Texinfo/Default/manual-init.pl b/Artworks/Docs/Texinfo/Default/manual-init.pl
deleted file mode 100755
index 8f68ea7..0000000
--- a/Artworks/Docs/Texinfo/Default/manual-init.pl
+++ /dev/null
@@ -1,389 +0,0 @@
-#!/usr/bin/perl
-#
-# repository.init -- This file initializes Texi2HTML program to
-# produce the repository documentation manual using the CentOS Web
-# Environment XHTML and CSS standard definition.
-#
-# Copyright (C) 2009, 2010, 2011 The CentOS Project
-#
-# 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., 59 Temple Place, Suite 330, Boston, MA 02111-1307
-# USA.
-# ----------------------------------------------------------------------
-# $Id$
-# ----------------------------------------------------------------------
-
-# -iso
-# if set, ISO8859 characters are used for special symbols (like
-# copyright, etc)
-$USE_ISO = 1;
-
-# -I
-# add a directory to the list of directories where @include files are
-# searched for (besides the directory of the file). additional '-I'
-# args are appended to this list. (APA: Don't implicitely search .,
-# to conform with the docs!) my @INCLUDE_DIRS = (".");
-#@INCLUDE_DIRS = ("/home/al/Projects/CentOS/artwork");
-
-# Extension used on output files.
-$EXTENSION = "xhtml";
-
-# Horizontal rules.
-$DEFAULT_RULE = '<div class="page-line white"><hr style="display:none;" /></div>';
-$SMALL_RULE = $DEFAULT_RULE;
-$MIDDLE_RULE = $DEFAULT_RULE;
-$BIG_RULE = $DEFAULT_RULE;
-
-# -split section|chapter|node|none
-# if $SPLIT is set to 'section' (resp. 'chapter') one html file per
-# section (resp. chapter) is generated. If $SPLIT is set to 'node' one
-# html file per node or sectionning element is generated. In all these
-# cases separate pages for Top, Table of content (Toc), Overview and
-# About are generated. Otherwise a monolithic html file that contains
-# the whole document is created.
-$SPLIT = 'section';
-
-# -sec-nav|-nosec-nav
-# if this is set then navigation panels are printed at the beginning
-# of each section. If the document is split at nodes then navigation
-# panels are printed at the end if there were more than $WORDS_IN_PAGE
-# words on page.
-#
-# If the document is split at sections this is ignored.
-#
-# This is most useful if you do not want to have section navigation
-# with -split chapter. There will be chapter navigation panel at the
-# beginning and at the end of chapters anyway.
-$SECTION_NAVIGATION = 1;
-
-# Layout control
-$print_page_head = \&T2H_XHTML_print_page_head;
-$print_page_foot = \&T2H_XHTML_print_page_foot;
-$print_frame = \&T2H_XHTML_print_frame;
-$button_icon_img = \&T2H_XHTML_button_icon_img;
-$print_navigation = \&T2H_XHTML_print_navigation;
-
-#FIXME update once it is more stabilized in texi2html.init
-sub T2H_XHTML_print_page_head
-{
- my $fh = shift;
- my $longtitle = "$Texi2HTML::THISDOC{'title_unformatted'}";
- $longtitle .= ": $Texi2HTML::UNFORMATTED{'This'}" if exists $Texi2HTML::UNFORMATTED{'This'};
- print $fh <<EOT;
-<?xml version="1.0"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="$LANG" lang="$LANG">
-<head>
-
- <title>$longtitle</title>
-
- <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
- <meta name="description" content="$longtitle" />
- <meta name="keywords" content="$longtitle" />
- <meta name="resource-type" content="document" />
- <meta name="distribution" content="global" />
- <meta name="generator" content="$Texi2HTML::THISDOC{program}" />
- <meta name="copyright" content="2009-2012 The CentOS Project" />
-
- <link href="Css/stylesheet.css" rel="stylesheet" type="text/css" media="screen projection" />
-
-</head>
-
-<body>
-
-<a name="top" />
-
-<div id="wrap">
-
- <div id="page-body">
-
- <div id="content">
-
-<!-- Created on $Texi2HTML::THISDOC{today} by $Texi2HTML::THISDOC{program} -->
-EOT
-}
-
-sub T2H_XHTML_print_page_foot
-{
- my $fh = shift;
- my @date=localtime(time);
- my $year=$date[5] += 1900;
- my $program_string = program_string();
- print $fh <<EOT;
-
- <p class="credits">$program_string</p>
-
- </div>
-
- </div>
-
-
-</div>
-
-</body>
-
-</html>
-EOT
-}
-
-# / in <img>
-sub T2H_XHTML_button_icon_img
-{
- my $button = shift;
- my $icon = shift;
- my $name = shift;
- return '' if (!defined($icon));
- if (defined($name) && $name)
- {
- $name = ": $name";
- }
- else
- {
- $name = '';
- }
- $button = "" if (!defined ($button));
- return qq{<img src="$icon" border="0" alt="$button$name" align="middle" />};
-}
-
-$simple_map{'*'} = '<br />';
-
-# formatting functions
-
-$def_line = \&t2h_xhtml_def_line;
-$index_summary = \&t2h_xhtml_index_summary;
-$image = \&t2h_xhtml_image;
-
-# need / in <img>
-sub t2h_xhtml_image($$$)
-{
- my $file = shift;
- my $base = shift;
- my $preformatted = shift;
- return "[ $base ]" if ($preformatted);
- return "<img src=\"$file\" alt=\"$base\" />";
-}
-
-# process definition commands line @deffn for example
-# <u> replaced by <span>
-sub t2h_xhtml_def_line($$$$$)
-{
- my $category = shift;
- my $name = shift;
- my $type = shift;
- my $arguments = shift;
- my $index_label = shift;
- $index_label = '' if (!defined($index_label));
- $name = '' if (!defined($name) or ($name =~ /^\s*$/));
- $type = '' if (!defined($type) or $type =~ /^\s*$/);
- if (!defined($arguments) or $arguments =~ /^\s*$/)
- {
- $arguments = '';
- }
- else
- {
- $arguments = '<i>' . $arguments . '</i>';
- }
- my $type_name = '';
- $type_name = " $type" if ($type ne '');
- $type_name .= ' <b>' . $name . '</b>' if ($name ne '');
- $type_name .= $arguments . "\n";
- if (! $DEF_TABLE)
- {
- return '<dt>'. '<span style="text-decoration: underline">' . $category . ':</span>' . $type_name . $index_label . "</dt>\n";
- }
- else
- {
-
- return "<tr>\n<td align=\"left\">" . $type_name .
- "</td>\n<td align=\"right\">" . $category . $index_label . "</td>\n" . "</tr>\n";
- }
-}
-
-# There is a br which needs /
-sub t2h_xhtml_index_summary($$)
-{
- my $alpha = shift;
- my $nonalpha = shift;
- my $join = '';
- my $nonalpha_text = '';
- my $alpha_text = '';
- $join = " \n<br />\n" if (@$nonalpha and @$alpha);
- if (@$nonalpha)
- {
- $nonalpha_text = join("\n \n", @$nonalpha) . "\n";
- }
- if (@$alpha)
- {
- $alpha_text = join("\n \n", @$alpha) . "\n \n";
- }
- #I18n
- return "<table><tr><th valign=\"top\">" . &$I('Jump to') . ": </th><td>" .
- $nonalpha_text . $join . $alpha_text . '</td></tr></table>';
-}
-
-# Layout of navigation panel
-sub T2H_XHTML_print_navigation
-{
- my $fh = shift;
- my $buttons = shift;
- my $vertical = shift;
- print $fh '<table class="navibar">' . "\n";
-
- print $fh "<tr>" unless $vertical;
- for my $button (@$buttons)
- {
- print $fh qq{<tr>\n} if $vertical;
- print $fh qq{<td>};
-
- if (ref($button) eq 'CODE')
- {
- &$button($fh, $vertical);
- }
- elsif (ref($button) eq 'SCALAR')
- {
- print $fh "$$button" if defined($$button);
- }
- elsif (ref($button) eq 'ARRAY')
- {
- my $text = $button->[1];
- my $button_href = $button->[0];
- if (defined($button_href) and !ref($button_href)
- and defined($text) and (ref($text) eq 'SCALAR') and defined($$text))
- { # use given text
- if ($Texi2HTML::HREF{$button_href})
- {
- print $fh "" .
- &$anchor('',
- $Texi2HTML::HREF{$button_href},
- $$text
- )
- ;
- }
- else
- {
- print $fh $$text;
- }
- }
- }
- elsif ($button eq ' ')
- { # handle space button
- print $fh
- $ICONS && $ACTIVE_ICONS{' '} ?
- &$button_icon_img($button, $ACTIVE_ICONS{' '}) :
- $NAVIGATION_TEXT{' '};
- #next;
- }
- elsif ($Texi2HTML::HREF{$button})
- { # button is active
- my $btitle = $BUTTONS_GOTO{$button} ?
- 'title="' . ucfirst($BUTTONS_GOTO{$button}) . '"' : '';
- if ($ICONS && $ACTIVE_ICONS{$button})
- { # use icon
- print $fh '' .
- &$anchor('',
- $Texi2HTML::HREF{$button},
- &$button_icon_img($button,
- $ACTIVE_ICONS{$button},
- #$Texi2HTML::NAME{$button}),
- $Texi2HTML::NO_TEXI{$button}),
- $btitle
- );
- }
- else
- { # use text
- print $fh
- '[' .
- &$anchor('',
- $Texi2HTML::HREF{$button},
- $NAVIGATION_TEXT{$button},
- $btitle
- ) .
- ']';
- }
- }
- else
- { # button is passive
- print $fh
- $ICONS && $PASSIVE_ICONS{$button} ?
- &$button_icon_img($button,
- $PASSIVE_ICONS{$button},
- #$Texi2HTML::NAME{$button}) :
- $Texi2HTML::NO_TEXI{$button}) :
-
- "[" . $NAVIGATION_TEXT{$button} . "]";
- }
- print $fh "</td>\n";
- print $fh "</tr>\n" if $vertical;
- }
- print $fh "</tr>" unless $vertical;
- print $fh "</table>\n";
-}
-
-# Use icons for navigation.
-$ICONS = 0;
-
-# insert here name of icon images for buttons
-# Icons are used, if $ICONS and resp. value are set
-%ACTIVE_ICONS =
- (
- 'Top', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-top.png',
- 'Contents', 'file:///usr/share/icons/Bluecurve/24x24/stock/help-contents.png',
- 'Overview', '',
- 'Index', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-find.png',
- 'This', '',
- 'Back', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png',
- 'FastBack', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-first.png',
- 'Prev', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png',
- 'Up', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-up.png',
- 'Next', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
- 'NodeUp', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-up.png',
- 'NodeNext', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
- 'NodePrev', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png',
- 'Following', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
- 'Forward', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
- 'FastForward', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-last.png',
- 'About' , 'file:///usr/share/icons/Bluecurve/24x24/stock/gtk-about.png',
- 'First', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-first.png',
- 'Last', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-last.png',
- ' ', ''
- );
-
-# Insert here name of icon images for these, if button is inactive
-%PASSIVE_ICONS =
- (
- 'Top', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-top.png',
- 'Contents', 'file:///usr/share/icons/Bluecurve/24x24/stock/help-contents.png',
- 'Overview', '',
- 'Index', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-find.png',
- 'This', '',
- 'Back', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png',
- 'FastBack', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-first.png',
- 'Prev', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png',
- 'Up', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-up.png',
- 'Next', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
- 'NodeUp', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-up.png',
- 'NodeNext', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
- 'NodePrev', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png',
- 'Following', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
- 'Forward', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
- 'FastForward', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-last.png',
- 'About' , 'file:///usr/share/icons/Bluecurve/24x24/stock/gtk-about.png',
- 'First', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-first.png',
- 'Last', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-last.png',
- ' ', ''
- );
-
-return 1;
diff --git a/Artworks/Docs/Texinfo/Default/manual.sed b/Artworks/Docs/Texinfo/Default/manual.sed
deleted file mode 100644
index 2b89341..0000000
--- a/Artworks/Docs/Texinfo/Default/manual.sed
+++ /dev/null
@@ -1,29 +0,0 @@
-#!/bin/sed
-#
-# repository.sed -- This file provides common transformations for
-# texi2html output, based on The CentOS Project CSS definitions.
-#
-# Copyright (C) 2009, 2010, 2011 The CentOS Project
-#
-# 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., 59 Temple Place, Suite 330, Boston, MA 02111-1307
-# USA.
-#
-# ----------------------------------------------------------------------
-# $Id$
-# ----------------------------------------------------------------------
-
-# Links
-#s!<a href="(https|http|ftps|ftp)://!<a class="www" href="\1://!g
-#s!<a href="mailto:!<a class="mailto" href="mailto:!g
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity-menu.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity-menu.texinfo
deleted file mode 100644
index 898140e..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity-menu.texinfo
+++ /dev/null
@@ -1,19 +0,0 @@
-@menu
-* Identity Brushes::
-* Identity Brushes Corporate::
-* Identity Fonts::
-* Identity Images::
-* Identity Images Brands::
-* Identity Images Brands Logos::
-* Identity Images Brands Symbols::
-* Identity Images Brands Types::
-* Identity Images Icons::
-* Identity Images Themes::
-* Identity Models::
-* Identity Models Brands::
-* Identity Models Brands Logos::
-* Identity Models Themes::
-* Identity Palettes::
-* Identity Patterns::
-* Identity Webenv::
-@end menu
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity-nodes.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity-nodes.texinfo
deleted file mode 100644
index 2902a4f..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity-nodes.texinfo
+++ /dev/null
@@ -1,17 +0,0 @@
-@include Identity/brushes.texinfo
-@include Identity/brushes-corporate.texinfo
-@include Identity/fonts.texinfo
-@include Identity/images.texinfo
-@include Identity/images-brands.texinfo
-@include Identity/images-brands-logos.texinfo
-@include Identity/images-brands-symbols.texinfo
-@include Identity/images-brands-types.texinfo
-@include Identity/images-icons.texinfo
-@include Identity/images-themes.texinfo
-@include Identity/models.texinfo
-@include Identity/models-brands.texinfo
-@include Identity/models-brands-logos.texinfo
-@include Identity/models-themes.texinfo
-@include Identity/palettes.texinfo
-@include Identity/patterns.texinfo
-@include Identity/webenv.texinfo
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity.texinfo
deleted file mode 100644
index 9383c82..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity.texinfo
+++ /dev/null
@@ -1,28 +0,0 @@
-@node Identity
-@chapter The @file{Scripts} Directory
-@cindex Identity
-
-@c -- Chapter Introduction
-The @file{Identity} directory describes @value{TCPCI}, what it
-is and the components it is made of.
-
-@value{TCPCI} 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. @value{TCPCI} provides visibility, recognizability,
-reputation, structure and identification to The CentOS Project by
-means of Corporate Design, Corporate Communication, and Corporate
-Behaviour.
-
-From Corporate Design, Corporate Communication and Corporate
-Behaviour, it is the Corporate Design the one organized inside
-@file{Identity} directory through the following components:
-
-@c -- Chapter Menu
-@include Identity-menu.texinfo
-
-@c -- Chapter Nodes
-@include Identity-nodes.texinfo
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/brushes-corporate.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/brushes-corporate.texinfo
deleted file mode 100644
index 6a8d0c9..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/brushes-corporate.texinfo
+++ /dev/null
@@ -1,10 +0,0 @@
-@node Identity Brushes Corporate
-@section @file{Identity/Brushes/Corporate}
-@cindex Identity brushes corporate
-
-...
-
-@c -- <[centos-art(SeeAlso)
-@itemize
-@end itemize
-@c -- ]>
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/brushes.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/brushes.texinfo
deleted file mode 100644
index 216cf0d..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/brushes.texinfo
+++ /dev/null
@@ -1,79 +0,0 @@
-@node Identity Brushes
-@section @file{Identity/Brushes}
-@cindex Identity brushes
-
-The @file{Identity/Brushes} directory exists to organize GIMP
-brushes used inside @value{TCPCVI}.
-
-A brush is a pixmap or set of pixmaps used for painting through an
-image manipulation program like GIMP. Inside the repository, brushes
-are initially created in @file{.xcf} format and later exported to any
-of the brush formats recognized by GIMP (e.g., @file{.gbr} or
-@file{.gih}) using the same name of its source file.
-
-The @file{Identity/Brushes} directory is under version control.
-
-The @file{Identity/Brushes} directory contains no file, but the
-following organizational directories:
-
-@c -- <[centos-art(SeeAlso)
-@itemize
-@end itemize
-@c -- ]>
-
-Content rendition inside @file{Identity/Brushes} directory is
-not supported.
-
-In order for brushes to be loaded by GIMP, they should be stored in
-the @file{~/.gimp-2.2/brushes} directory. This location is out of
-@value{TCAR} and doesn't provide version control by itself. To be able
-of using version controlled brushes inside GIMP, we store brush
-related files inside @file{Identity/Brushes} directory and
-create links to them from @file{~/.gimp-2.2/brushes} directory.
-
-@float Example,identity-brushes-1
-@verbatim
-Identity/Brushes
-|-- Corporate
-| |-- symbol.xcf
-| `-- symbol.gbr (file) <-- ~/.gimp-2.2/brushes/corporate-symbol.gbr (link)
-|-- TreeFlower
-| |-- flower.gbr (file) <-- ~/.gimp-2.2/brushes/treeflower-flower.gbr (link)
-| |-- flower.xcf
-| |-- branch.gbr (file) <-- ~/.gimp-2.2/brushes/treeflower-branch.gbr (link)
-| |-- branch.xcf
-| |-- trunk.gbr (file) <-- ~/.gimp-2.2/brushes/treeflower-trunk.gbr (link)
-| `-- trunk.xcf
-`-- Others
- `-- ...
-@end verbatim
-@caption{Relation between brushes inside the workstation.}
-@end float
-
-The entire link preparation and maintenance of brushes inside the
-working copy is automated by @code{prepare} functionality of
-@command{centos-art.sh} script.
-
-Inside the working copy, brushes might be created individually in
-different locations, but they all need to be linked from one unique
-location (i.e., @file{~/.gimp-2.2/brushes}). This configuration may
-provoke brushes to overlap one another if a consistent name convention
-is not implemented correctly. In that sake, the brushes file names
-are build using their directory and file names as reference in order
-to build unique names that can be used as identifiers.
-
-Brushes produced with GIMP has a description field associated that is
-shown in the Brushes panel of GIMP. This description is set when the
-brush is created as @file{.xcf} file and can be updated when it is
-exported either to @file{.gbr} or @file{.gih} format. It wouldn't be
-too useful to have two or more brushes using the same description so,
-we also make description of brush files unique, too. In that sake, use
-the file name as description but without including the file extension
-(e.g., if we have the @file{centos-flame-3.gbr} brush, its description
-would be @code{centos-flame-3}).
-
-More information about GIMP brushes can be found in
-@url{file:///usr/share/gimp/2.0/help/en/index.html,The Gimp Manual},
-specifically in the section related to
-@url{file:///usr/share/gimp/2.0/help/en/gimp-concepts-brushes.html,
-Brushes}.
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/fonts.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/fonts.texinfo
deleted file mode 100644
index 7eaeee9..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/fonts.texinfo
+++ /dev/null
@@ -1,54 +0,0 @@
-@node Identity Fonts
-@section @file{Identity/Fonts}
-@cindex Identity fonts
-
-The @file{Identity/Fonts} directory exists to organize
-typographies used inside @value{TCPCVI} that aren't packaged inside
-@value{TCD}.
-
-The @file{Identity/Fonts} directory is under version control.
-
-Content rendition inside @file{Identity/Fonts} directory is not
-supported.
-
-@c -- describe, in one paragraph, what a font is.
-
-In order for fonts to be available inside programs like GIMP and
-Inkscape, font files should be stored either in
-@file{/usr/share/fonts} or @file{~/.fonts} directory. These locations
-are out of @value{TCAR} and doesn't provide version control by
-themselves. In order for version controlled typographies to be
-available inside programs like GIMP and Inkscape, we store them under
-@file{Identity/Fonts} directory and create links to them from
-@file{~/.fonts} directory.
-
-@float Example, identity-fonts-1
-@verbatim
-Identity/Fonts
-`-- denmark.ttf (file) <-- ~/.fonts/denmark.ttf (link)
-@end verbatim
-@caption{Relation between fonts inside the workstation.}
-@end float
-
-The creation and maintenance of links related to fonts inside the
-working copy are automated by @code{prepare} functionality of
-@command{centos-art.sh} script.
-
-Inside @value{TCPCVI}, the @samp{DejaVu LGC} typography is used as
-default typography in all visual manifestations. The @samp{DejaVu LGC}
-typography comes with @value{TCD} so there is no need to store it in
-@file{Identity/Fonts} for you to use.
-
-Inside @value{TCPCVI}, the @samp{Denmark} typography is used as base
-to build The CentOS Logo (i.e., the main graphic design that
-connects/identifies all visual manifestations related to The CentOS
-Project). The @samp{Denmark} typography doesn't come with @value{TCD}
-so it is store in @file{Identity/Fonts} for you to use.
-
-The license information of @samp{Denmark} typography isn't very clear,
-at least not as clear as the one in @samp{DejaVu LGC} typography is.
-Using a typography with a doubtful license might put in risk the
-content produced from it. To prevent such issues, it would be better
-to move on from @samp{Denmark} typography to another typography (free,
-preferably) that retain the same visual style of @samp{Denmark}, but
-with a clearer copyright and license notice.
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-brands-logos.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-brands-logos.texinfo
deleted file mode 100644
index aafccb9..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-brands-logos.texinfo
+++ /dev/null
@@ -1,42 +0,0 @@
-@node Identity Images Brands Logos
-@section @file{Identity/Images/Brands/Logos}
-@cindex Identity images brands logos
-
-The @file{Identity/Images/Brands/Logos} exists to organize
-images related to The CentOS Logos, in different formats (e.g., PNG,
-JPG, PDF, TIF, XBM, XPM) and dimensions.
-
-The CentOS Logo is a construction made of The CentOS Symbol and The
-CentOS Type. The CentOS Symbol and The CentOS Logo are the main visual
-manifestations of the organization known as @value{TCPROJ}. As The
-CentOS Symbol, The CentOS Logo is used to ``brand'' images produced by
-@value{TCPROJ} and provide a visual connection between images so they
-can be monolithically recognized as part of @value{TCPROJ}. The CentOS
-Logo must be exactly the same every time it is printed out and a route
-to reproduce it in such a way must be available so as to avoid
-reproduction mistakes when images are branded with it.
-
-The @file{Identity/Images/Brands/Logos} directory and the files
-inside it aren't under version control.
-
-The @file{Identity/Images/Brands/Logos} directory contains files
-used by the @file{redhat-logos} package, specifically the files inside
-the @file{/usr/share/pixmaps/redhat} directory.
-
-The @file{Identity/Images/Brands/Logos} directory organizes
-files under directories numerically named (e.g., @file{48}, @file{64},
-@file{128}, etc.). Inside these directories, image files are stored
-in specific heights and named as
-@file{centos-<something>.<extension>}, where @code{<somthing>}
-describes the file content and @code{<extension>} sets the file
-extension. In all cases, the directory name can be used as reference
-to determine the image height of files stored inside. For example,
-the directory @file{48} stores image files of 48 pixels height in
-different formats.
-
-Content rendition inside @file{Identity/Images/Brands/Logos}
-directory takes place through the following command:
-
-@verbatim
-centos-art render Identity/Images/Brands/Logos --dont-commit-changes
-@end verbatim
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-brands-symbols.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-brands-symbols.texinfo
deleted file mode 100644
index 6e78e1f..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-brands-symbols.texinfo
+++ /dev/null
@@ -1,40 +0,0 @@
-@node Identity Images Brands Symbols
-@section @file{Identity/Images/Brands/Symbols}
-@cindex Identity images brands symbols
-
-The @file{Identity/Images/Brands/Symbols} exists to organize
-images related to The CentOS Symbol, in different formats (e.g., PNG,
-JPG, PDF, TIF, XBM, XPM) and dimensions.
-
-The CentOS Symbol is the graphical part of The CentOS Logo. As The
-CentOS Logo, The CentOS Symbol is used to ``brand'' images produced by
-@value{TCPROJ} and provide a visual connection between images so they
-can be monolithically recognized as part of @value{TCPROJ}. The CentOS
-Symbol must be exactly the same every time it is printed out and a
-route to reproduce it in such a way must be available so as to avoid
-reproduction mistakes when images are branded with it.
-
-The @file{Identity/Images/Brands/Symbols} directory and the files
-inside it aren't under version control.
-
-The @file{Identity/Images/Brands/Symbols} directory contains
-files used by the @file{redhat-logos} package, specifically the files
-inside the @file{/usr/share/pixmaps/redhat} directory.
-
-The @file{Identity/Images/Brands/Symbols} directory organizes
-files under directories numerically named (e.g., @file{48}, @file{64},
-@file{128}, etc.). Inside these directories, image files are stored
-in specific heights and named as
-@file{centos-<something>.<extension>}, where @code{<somthing>}
-describes the file content and @code{<extension>} sets the file
-extension. In all cases, the directory name can be used as reference
-to determine the image height of files stored inside. For example,
-the directory @file{48} stores image files of 48 pixels height in
-different formats.
-
-Content rendition inside @file{Identity/Images/Brands/Symbols}
-directory takes place through the following command:
-
-@verbatim
-centos-art render Identity/Images/Brands/Symbols --dont-commit-changes
-@end verbatim
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-brands-types.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-brands-types.texinfo
deleted file mode 100644
index e196966..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-brands-types.texinfo
+++ /dev/null
@@ -1,44 +0,0 @@
-@node Identity Images Brands Types
-@section @file{Identity/Images/Brands/Types}
-@cindex Identity images brands types
-
-The @file{Identity/Images/Brands/Types} exists to organize
-images related to The CentOS Symbol, in different formats (e.g., PNG,
-JPG, PDF, TIF, XBM, XPM) and dimensions.
-
-The CentOS Type is the typographical part of The CentOS Logo.
-Comparing with both The CentOS Logo and The CentOS Symbol, The CentOS
-Type by its own, provides poor visual connection between images that
-intend to be recognized as a monolithic part of @value{TCPROJ} and
-shouldn't be used alone. Instead, The CentOS Logo or The CentOS Symbol
-are preferred. The CentOS Symbol must be exactly the same every time
-it is printed out and a route to reproduce it in such a way must be
-available so as to avoid reproduction mistakes when images are branded
-with it.
-
-The @file{Identity/Images/Brands/Types} directory and the files
-inside it aren't under version control. Files in this location are
-mainly used to build The CentOS Logo from combining both The CentOS
-Type and The CentOS Symbol in specific situations that might be needed
-doing so.
-
-The @file{Identity/Images/Brands/Types} directory contains files
-used by no package, as far as we've found out.
-
-The @file{Identity/Images/Brands/Types} directory organizes
-files under directories numerically named (e.g., @file{48}, @file{64},
-@file{128}, etc.). Inside these directories, image files are stored
-in specific heights and named as
-@file{centos-<something>.<extension>}, where @code{<somthing>}
-describes the file content and @code{<extension>} sets the file
-extension. In all cases, the directory name can be used as reference
-to determine the image height of files stored inside. For example,
-the directory @file{48} stores image files of 48 pixels height in
-different formats.
-
-Content rendition inside @file{Identity/Images/Brands/Types}
-directory takes place through the following command:
-
-@verbatim
-centos-art render Identity/Images/Brands/Types --dont-commit-changes
-@end verbatim
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-brands.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-brands.texinfo
deleted file mode 100644
index f871dcc..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-brands.texinfo
+++ /dev/null
@@ -1,24 +0,0 @@
-@node Identity Images Brands
-@section @file{Identity/Images/Brands}
-@cindex Identity images brands
-
-The @file{Identity/Images/Brands} directory exists to organize
-brand information related to @value{TCPROJ}.
-
-The @file{Identity/Images/Brands} directory isn't under version
-control.
-
-The @file{Identity/Images/Brands} contains no file, but the
-following organizational directories:
-
-@c -- <[centos-art(SeeAlso)
-@itemize
-@end itemize
-@c -- ]>
-
-Content rendition inside @file{Identity/Images/Brands} directory
-takes place through the following command:
-
-@verbatim
-centos-art render Identity/Images/Brands --dont-commit-changes
-@end verbatim
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-icons.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-icons.texinfo
deleted file mode 100644
index c8b46b6..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-icons.texinfo
+++ /dev/null
@@ -1,10 +0,0 @@
-@node Identity Images Icons
-@section @file{Identity/Images/Icons}
-@cindex Identity images icons
-
-...
-
-@c -- <[centos-art(SeeAlso)
-@itemize
-@end itemize
-@c -- ]>
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-themes.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-themes.texinfo
deleted file mode 100644
index cf3a6d9..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images-themes.texinfo
+++ /dev/null
@@ -1,7 +0,0 @@
-@node Identity Images Themes
-@section @file{Identity/Images/Themes}
-@cindex Identity images themes
-...
-
-@menu
-@end menu
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images.texinfo
deleted file mode 100644
index 964b2f9..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/images.texinfo
+++ /dev/null
@@ -1,26 +0,0 @@
-@node Identity Images
-@section @file{Identity/Images}
-@cindex Identity images
-
-The @file{Identity/Images} directory exists to store all image
-files (e.g., PNG, JPG, PPM, etc.) related to @value{TCPCVI}.
-
-The @file{Identity/Images} directory is under version control.
-
-The @file{Identity/Images} directory contains no file, but the
-following organizational directories:
-
-@c -- <[centos-art(SeeAlso)
-@itemize
-@item @ref{Identity Images Brands}
-@item @ref{Identity Images Icons}
-@item @ref{Identity Images Themes}
-@end itemize
-@c -- ]>
-
-Content rendition inside @file{Identity/Images} directory takes
-place through the following command:
-
-@verbatim
-centos-art render Identity/Images --dont-commit-changes
-@end verbatim
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/models-brands-logos.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/models-brands-logos.texinfo
deleted file mode 100644
index d7d98d9..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/models-brands-logos.texinfo
+++ /dev/null
@@ -1,8 +0,0 @@
-@node Identity Models Brands Logos
-@section @file{Identity/Models/Brands/Logos}
-@cindex Identity models brands logos
-
-...
-
-@menu
-@end menu
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/models-brands.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/models-brands.texinfo
deleted file mode 100644
index 39946bc..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/models-brands.texinfo
+++ /dev/null
@@ -1,9 +0,0 @@
-@node Identity Models Brands
-@section @file{Identity/Models/Brands}
-@cindex Identity models brands
-
-...
-
-@menu
-* Identity Models Brands Logos::
-@end menu
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/models-themes.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/models-themes.texinfo
deleted file mode 100644
index 70a31c4..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/models-themes.texinfo
+++ /dev/null
@@ -1,10 +0,0 @@
-@node Identity Models Themes
-@section @file{Identity/Models/Themes}
-@cindex Identity models themes
-
-...
-
-@c -- <[centos-art(SeeAlso)
-@itemize
-@end itemize
-@c -- ]>
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/models.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/models.texinfo
deleted file mode 100644
index 1b2f26e..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/models.texinfo
+++ /dev/null
@@ -1,10 +0,0 @@
-@node Identity Models
-@section @file{Identity/Models}
-@cindex Identity models
-
-...
-
-@c -- <[centos-art(SeeAlso)
-@itemize
-@end itemize
-@c -- ]>
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/palettes.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/palettes.texinfo
deleted file mode 100644
index 7ae9984..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/palettes.texinfo
+++ /dev/null
@@ -1,7 +0,0 @@
-@node Identity Palettes
-@section @file{Identity/Palettes}
-@cindex Identity palettes
-...
-
-@menu
-@end menu
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/patterns.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/patterns.texinfo
deleted file mode 100644
index 1157522..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/patterns.texinfo
+++ /dev/null
@@ -1,8 +0,0 @@
-@node Identity Patterns
-@section @file{Identity/Patterns}
-@cindex Identity patterns
-
-...
-
-@menu
-@end menu
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/webenv.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/webenv.texinfo
deleted file mode 100644
index 1571757..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Identity/webenv.texinfo
+++ /dev/null
@@ -1,7 +0,0 @@
-@node Identity Webenv
-@section @file{Identity/Webenv}
-@cindex Identity webenv
-...
-
-@menu
-@end menu
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts-menu.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts-menu.texinfo
deleted file mode 100644
index d5de2d3..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts-menu.texinfo
+++ /dev/null
@@ -1,4 +0,0 @@
-@menu
-* Scripts Functions::
-* Scripts Functions Prepare::
-@end menu
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts-nodes.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts-nodes.texinfo
deleted file mode 100644
index 89f5123..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts-nodes.texinfo
+++ /dev/null
@@ -1,2 +0,0 @@
-@include Scripts/functions.texinfo
-@include Scripts/functions-prepare.texinfo
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts.texinfo
deleted file mode 100644
index 1d17b2e..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts.texinfo
+++ /dev/null
@@ -1,75 +0,0 @@
-@node Scripts
-@chapter The @file{Scripts} Directory
-@cindex Scripts
-
-@c -- Chapter Introduction
-
-The @file{Scripts} directory exists to organize automation
-scripts related to @value{TCPCVI}. Such automation scripts are
-implemented through @command{centos-art.sh} script, a bash scripts
-designed to automate most frequent tasks performed inside the working
-copy of @value{TCAR} (e.g., image rendition, content documentation,
-content translation, etc.).
-
-The @file{Scripts} directory and all files inside it are under
-version control.
-
-The @file{Scripts} directory contains just one file, the
-@file{centos-art.sh} file. This file is the invocation script the
-@command{centos-art} command calls to. In addition to
-@file{centos-art.sh} file, the following directories are available:
-
-Content rendition inside @file{Scripts} is not supported.
-
-Once the @command{centos-art.sh} script is executed, the following
-variables are available all along the script execution:
-
-@defvar CLI_PROGRAM
-The @var{CLI_PROGRAM} variable is read-only and contains the name of
-the script, which is @samp{centos-art}, without extension.
-@end defvar
-
-@defvar CLI_PROGRAM_ID
-The @var{CLI_PROGRAM_ID} variable is read-only and contains the
-process identification assigned to @command{centos-art.sh} script,
-once executed.
-@end defvar
-
-@defvar CLI_VERSION
-The @var{CLI_VERSION} variable is read-only and contains the version
-number of @command{centos-art.sh} script.
-@end defvar
-
-@defvar CLI_BASEDIR
-The @var{CLI_BASEDIR} variable is read-only and contains the absolute
-path of directory where @command{centos-art.sh} script is stored in.
-@end defvar
-
-@defvar CLI_TEMPDIR
-The @var{CLI_TEMPDIR} variable is read-only and contains the absolute
-path of directory where temporal files created by
-@command{centos-art.sh} script are stored in.
-@end defvar
-
-@defvar TEXTDOMAIN
-The @var{TEXDOMAIN} variable is read-only and contains the name of the
-program we are providing localization for (i.e., @samp{centos-art.sh}).
-@end defvar
-
-@defvar TEXTDOMAINDIR
-The @var{TEXTDOMAINDIR} variable is read-only and contains the
-absolute path of directory holding localization messages for
-@command{centos-art.sh}. In order for this variable to take effect,
-its value must be set using the
-@file{$@{BASEDIR@}/$@{LANG@}/LC_MESSAGES/$@{TEXDOMAIN@}} construction;
-where @var{BASEDIR} is an absolute path inside your workstation,
-@var{LANG} a language code based on the standards @samp{ISO-639} and
-@samp{ISO-3166} (e.g., @samp{es_ES} for Spanish from Spain,
-@samp{fr_FR} for French from France, etc.).
-@end defvar
-
-@c -- Chapter Menu
-@include Scripts-menu.texinfo
-
-@c -- Chapter Nodes
-@include Scripts-nodes.texinfo
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts/functions-prepare.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts/functions-prepare.texinfo
deleted file mode 100644
index 43d0fc3..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts/functions-prepare.texinfo
+++ /dev/null
@@ -1,86 +0,0 @@
-@node Scripts Functions Prepare
-@section @file{Scripts/Functions/Prepare}
-@cindex Scripts functions prepare
-
-The @file{Scripts/Functions/Prepare} directory exists to
-organize the @code{prepare} functionality of @command{centos-art.sh}
-script. The @code{prepare} functionality is written in Bash and its
-main goal is to standardize the final configuration stuff your
-workstation needs, once the working copy of @value{TCAR} has been
-downloaded inside it.
-
-The @file{Scripts/Functions/Prepare} directory and all files
-inside it are under version control.
-
-Content rendition inside @file{Scripts/Functions/Prepare} is not
-supported.
-
-Inside @file{Scripts/Functions/Prepare} directory, file names
-and function names share the same name convenction with the exception
-that file names end with a @samp{.sh} suffix while function names
-doesn't. Both, file names and function names, begin with
-@samp{prepare_} prefix followed by a description of what the function
-does.
-
-Inside @file{Scripts/Functions/Prepare} directory, you can find
-the following functions:
-
-@defun prepare
-The @code{prepare} (initialization) function creates the base
-execution environment required to standardize final configuration
-stuff needed by your workstation, once the working copy of
-@value{TCAR} has been downloaded in it.
-@end defun
-
-@defun prepare_getOptions
-The @code{prepare_getOptions} function parses command options provided
-to @command{centos-art.sh} script when the first argument in the
-command-line is the @samp{prepare} word. This function decides what
-action to perform based on options provided. To parse options, this
-function makes use of @command{getopt} program.
-@end defun
-
-@defun prepare_updateLinks
-The @code{prepare_updateLinks} function updates the symbolic
-link relation that connects your workstation with the files inside the
-working copy of @value{TCAR}. This function makes brushes, palettes,
-patterns and fonts inside the working copy available to programs like
-GIMP and Inkscape installed in your workstation.
-@end defun
-
-@defun prepare_updateImages
-The @code{prepare_updateImages} function initializes image files
-inside the working copy. This function makes a list of all design
-models inside the working copy and renders them one by one to produces
-the related output images.
-@end defun
-
-@defun prepare_updateManuals
-The @code{prepare_updateManuals} function initializes
-documentation files inside the working copy. This function makes a
-list of all documentation manuals source files inside the working copy
-and produces related output for them.
-@end defun
-
-@defun prepare_updatePackages
-The @code{prepare_updatePackages} function verifies the required
-packages your workstation needs to have installed in order for
-@command{centos-art.sh} script to run correctly. If one or
-more packages are uninstalled or out of date, the
-@command{centos-art.sh} script asks you to confirm their
-installation or actualization through the @command{sudo yum} command.
-@end defun
-
-@defun prepare_getEnvars
-The @code{prepare_getEnvars} function outputs a brief description of
-relevant environment variables the @command{centos-art.sh} script
-makes use of.
-@end defun
-
-@defun prepare_getLinkName DIRECTORY, FILE
-The @code{prepare_getLinkName} function takes a @var{DIRECTORY} path
-as first argument and a @var{FILE} path as second argument to output a
-file name with the path information that remains from substracting the
-@var{DIRECTORY} path from the @var{FILE} path provided as argument.
-@end defun
-
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts/functions.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts/functions.texinfo
deleted file mode 100644
index 9c4c148..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/Scripts/functions.texinfo
+++ /dev/null
@@ -1,68 +0,0 @@
-@node Scripts Functions
-@section @file{Scripts/Functions}
-@cindex Scripts functions
-
-The @file{Scripts/Functions} directory exists to organize common and
-specific functionalities related to the @command{centos-art.sh}
-script. Common functionalities are loaded once the
-@command{centos-art.sh} script is executed and made available for
-specific functionalities to reuse.
-
-The @file{Scripts/Functions} directory and all files inside it
-are under version control.
-
-Content rendition inside `Scripts/Functions' directory is not
-supported.
-
-Inside @file{Scripts/Functions} directory, specific
-functionalities are organized in the following directories:
-
-@c -- <[centos-art(SeeAlso)
-@itemize
-@end itemize
-@c -- ]>
-
-Inside @file{Scripts/Functions} directory, common
-functionalities are stored in files prefixed with the @samp{cli}
-string as described below:
-
-@defun cli "$@@"
-The @code{cli} functionality initializes the command-line interface
-(cli) of @command{centos-art.sh} script. This function evaluates the
-first argument provided to @command{centos-art.sh} script and call the
-specific functionality that responds to it. The @code{cli} function
-is directly called from @file{centos-art.sh} itself once global
-variables are defined, working copy verification performed, common
-functionalities exported into the execution environment, and signals
-trapped. The @code{cli} function receives all positional parameters
-passed to @command{centos-art.sh} as argument.
-
-The @code{cli} function creates the a new environment inside that one
-created by @command{centos-art.sh} script execution. Variables defined
-herein will be avaialble to all specific functionalities and common
-functionalities used inside specific functionalities.
-
-@defvar FUNCNAM
-The @var{FUNCNAM} variable stores the function name passed as first
-argument to @command{centos-art.sh} script using the file convenction
-specified by @code{cli_getRepoName} function.
-@end defvar
-
-@defvar FUNCDIR
-The @var{FUNCDIR} variable stores the absolute path of directory
-holding @command{centos-art.sh} script functions, both common and
-specific.
-@end defvar
-
-@defvar FUNCDIRNAM
-...
-@end defvar
-
-@defvar FUNCSCRIPT
-...
-@end defvar
-
-@defvar ARGUMENTS
-...
-@end defvar
-@end defun
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs-index.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs-index.texinfo
deleted file mode 100755
index b197b13..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs-index.texinfo
+++ /dev/null
@@ -1,8 +0,0 @@
-@node Index
-@unnumbered Index
-@syncodeindex fn cp
-@syncodeindex vr cp
-@syncodeindex ky cp
-@syncodeindex pg cp
-@syncodeindex tp cp
-@printindex cp
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs-menu.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs-menu.texinfo
deleted file mode 100644
index 3f09b90..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs-menu.texinfo
+++ /dev/null
@@ -1,6 +0,0 @@
-@menu
-* Identity::
-* Scripts::
-* Licenses::
-* Index::
-@end menu
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs-nodes.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs-nodes.texinfo
deleted file mode 100644
index 57ce834..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs-nodes.texinfo
+++ /dev/null
@@ -1,2 +0,0 @@
-@include Identity.texinfo
-@include Scripts.texinfo
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs.conf b/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs.conf
deleted file mode 100755
index 789f831..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs.conf
+++ /dev/null
@@ -1,36 +0,0 @@
-# This file controls the manual configuration. This file is divided
-# in configuration sections (e.g., `main' and `templates') which, in
-# turn, are organized in the form `variable = value'.
-# ----------------------------------------------------------------------
-# $Id$
-# ----------------------------------------------------------------------
-
-[main]
-
-# Specify documentation backend used by documentation manual. This is
-# the format used to write documentation manual source files.
-manual_format = "texinfo"
-
-# Specify title style used by sections inside the manual. Possible
-# values to this option are `cap-each-word' to capitalize each word in
-# the section title, `cap-first-word' to capitalize the first word in
-# the section title only and `directory' to transform each word in the
-# section title into a directory path. From all these options,
-# `cap-each-word' is the one used as default.
-manual_section_style = "directory"
-
-# Specify the order used by sections inside the manual. By default new
-# sections added to the manual are put on the end to follow the
-# section `created' order. Other possible values to this option are
-# `ordered' and `reversed' to sort the list of sections alphabetically
-# from A-Z and Z-A, respectively.
-manual_section_order = "ordered"
-
-[templates]
-
-# Specify relation between template files and section definition files
-# inside the manual. Template definition is set on the left side using
-# relative path. The section main definition file is described on the
-# right using a regular expression. The first match wins.
-Chapters/section-functions.texinfo = "^.+-functions-[[:alnum:]]+\.texinfo$"
-Chapters/section.texinfo = "^.+\.texinfo$"
diff --git a/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs.texinfo b/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs.texinfo
deleted file mode 100644
index db713aa..0000000
--- a/Artworks/Docs/Texinfo/Tcar-fs/en_US/tcar-fs.texinfo
+++ /dev/null
@@ -1,83 +0,0 @@
-\input texinfo @c -*-texinfo-*-
-@c -- Header --------------------------------------------------
-
-@setfilename tcar-fs.info
-@settitle The CentOS Artwork Repository File System
-@documentlanguage en
-@afourpaper
-@finalout
-
-@c -- Variables -----------------------------------------------
-
-@set TCENTOS The Community Enterprise Operating System
-@set TCPROJ @url{http://www.centos.org/, The CentOS Project}
-@set TCWIKI @url{http://wiki.centos.org/, The CentOS Wiki}
-@set TCMLISTS @url{http://lists.centos.org/, The CentOS Mailing Lists}
-@set TCBUGS @url{http://bugs.centos.org/, The CentOS Bugs}
-@set TCMIRRORS @url{http://mirrors.centos.org/, The CentOS Mirrors}
-@set TCPLANET @url{http://planet.centos.org/, The CentOS Planet}
-@set TCFORUMS @url{http://forums.centos.org/, The CentOS Forums}
-@set TCINFOML @email{centos-info@@centos.org, The CentOS Information Mailing List}
-@set TCDEVSML @email{centos-devel@@centos.org, The CentOS Developers Mailing List}
-@set TCDOCSML @email{centos-docs@@centos.org, The CentOS Documentation Mailing List}
-@set TCARTWML @email{centos-artwork@@centos.org, The CentOS Artwork Mailing List}
-@set TCL10NML @email{centos-l10n@@centos.org, The CentOS Localization Mailing List}
-@set TCAR @url{https://projects.centos.org/svn/artwork/, The CentOS Artwork Repository}
-@set TCAS @url{https://projects.centos.org/trac/artwork/, The CentOS Artwork SIG}
-
-@set TCPCVI The CentOS Project Corporate Visual Identity
-@set TCPCI The CentOS Project Corporate Identity
-@set TCPCVIS The CentOS Project Corporate Visual Identity Structure
-@set TCPCMVIS The CentOS Project Monolithic Corporate Visual Identity Structure
-
-@set TCD The CentOS Distribution
-
-@c -- Summary description and copyright -----------------------
-
-@copying
-This manual describes the directories inside @value{TCAR}. You can use
-this manual as reference to know where to store or look for
-information inside your working copy of @value{TCAR}.
-
-Copyright @copyright{} 2009, 2010, 2011 The CentOS Project
-
-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 @ref{GNU Free
-Documentation License}.
-@end copying
-
-@c -- Titlepage, contents, copyright ---------------------------
-
-@titlepage
-@title The CentOS Artwork Repository
-@subtitle File System
-@author Alain Reguera Delgado
-@page
-@vskip 0pt plus 1filll
-@insertcopying
-@end titlepage
-@contents
-
-@c -- `Top' node and master menu -------------------------------
-
-@ifnottex
-@node Top
-@top The CentOS Artwork Repository File System
-@insertcopying
-@end ifnottex
-
-@include tcar-fs-menu.texinfo
-
-@c -- The body of the document --------------------------------
-
-@include tcar-fs-nodes.texinfo
-
-@c -- The end of the document ---------------------------------
-
-@include Licenses.texinfo
-@include tcar-fs-index.texinfo
-
-@bye
diff --git a/Artworks/Documentation/Automation/Bash/Functions/Path/figure-1.svgz b/Artworks/Documentation/Automation/Bash/Functions/Path/figure-1.svgz
new file mode 100644
index 0000000..1e53a09
Binary files /dev/null and b/Artworks/Documentation/Automation/Bash/Functions/Path/figure-1.svgz differ
diff --git a/Artworks/Documentation/Automation/Bash/Functions/Path/figure-2.svgz b/Artworks/Documentation/Automation/Bash/Functions/Path/figure-2.svgz
new file mode 100644
index 0000000..0f3bfcf
Binary files /dev/null and b/Artworks/Documentation/Automation/Bash/Functions/Path/figure-2.svgz differ
diff --git a/Artworks/Documentation/Automation/Bash/Functions/Path/figure-3.svgz b/Artworks/Documentation/Automation/Bash/Functions/Path/figure-3.svgz
new file mode 100644
index 0000000..1296f1e
Binary files /dev/null and b/Artworks/Documentation/Automation/Bash/Functions/Path/figure-3.svgz differ
diff --git a/Artworks/Documentation/Automation/Bash/Functions/Path/figure-4.svgz b/Artworks/Documentation/Automation/Bash/Functions/Path/figure-4.svgz
new file mode 100644
index 0000000..ceea222
Binary files /dev/null and b/Artworks/Documentation/Automation/Bash/Functions/Path/figure-4.svgz differ
diff --git a/Artworks/Documentation/Automation/Bash/Functions/Path/figure-5.svgz b/Artworks/Documentation/Automation/Bash/Functions/Path/figure-5.svgz
new file mode 100644
index 0000000..89c165a
Binary files /dev/null and b/Artworks/Documentation/Automation/Bash/Functions/Path/figure-5.svgz differ
diff --git a/Artworks/Documentation/Automation/Bash/Functions/Path/figure-6.svgz b/Artworks/Documentation/Automation/Bash/Functions/Path/figure-6.svgz
new file mode 100644
index 0000000..c04de8a
Binary files /dev/null and b/Artworks/Documentation/Automation/Bash/Functions/Path/figure-6.svgz differ
diff --git a/Artworks/Documentation/Automation/initFunctions.svgz b/Artworks/Documentation/Automation/initFunctions.svgz
new file mode 100644
index 0000000..f9014d4
Binary files /dev/null and b/Artworks/Documentation/Automation/initFunctions.svgz differ
diff --git a/Artworks/Documentation/Automation/renderImage.svgz b/Artworks/Documentation/Automation/renderImage.svgz
new file mode 100644
index 0000000..b187c16
Binary files /dev/null and b/Artworks/Documentation/Automation/renderImage.svgz differ
diff --git a/Artworks/Documentation/Brands/Logos/centos.svgz b/Artworks/Documentation/Brands/Logos/centos.svgz
new file mode 100644
index 0000000..c94a127
Binary files /dev/null and b/Artworks/Documentation/Brands/Logos/centos.svgz differ
diff --git a/Artworks/Documentation/Brands/Symbols/centos-howto-1of4.svgz b/Artworks/Documentation/Brands/Symbols/centos-howto-1of4.svgz
new file mode 100644
index 0000000..2b74847
Binary files /dev/null and b/Artworks/Documentation/Brands/Symbols/centos-howto-1of4.svgz differ
diff --git a/Artworks/Documentation/Brands/Symbols/centos-howto-2of4.svgz b/Artworks/Documentation/Brands/Symbols/centos-howto-2of4.svgz
new file mode 100644
index 0000000..d2b583e
Binary files /dev/null and b/Artworks/Documentation/Brands/Symbols/centos-howto-2of4.svgz differ
diff --git a/Artworks/Documentation/Brands/Symbols/centos-howto-3of4.svgz b/Artworks/Documentation/Brands/Symbols/centos-howto-3of4.svgz
new file mode 100644
index 0000000..0d1dba5
Binary files /dev/null and b/Artworks/Documentation/Brands/Symbols/centos-howto-3of4.svgz differ
diff --git a/Artworks/Documentation/Brands/Symbols/centos-howto-4of4.svgz b/Artworks/Documentation/Brands/Symbols/centos-howto-4of4.svgz
new file mode 100644
index 0000000..842a1d9
Binary files /dev/null and b/Artworks/Documentation/Brands/Symbols/centos-howto-4of4.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-10-p.svgz b/Artworks/Documentation/Brands/Types/centos-10-p.svgz
new file mode 100644
index 0000000..e514a7a
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-10-p.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-10.svgz b/Artworks/Documentation/Brands/Types/centos-10.svgz
new file mode 100644
index 0000000..6258646
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-10.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-3-p.svgz b/Artworks/Documentation/Brands/Types/centos-3-p.svgz
new file mode 100644
index 0000000..2f23c5f
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-3-p.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-3.svgz b/Artworks/Documentation/Brands/Types/centos-3.svgz
new file mode 100644
index 0000000..9b421ff
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-3.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-4-p.svgz b/Artworks/Documentation/Brands/Types/centos-4-p.svgz
new file mode 100644
index 0000000..639a685
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-4-p.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-4.svgz b/Artworks/Documentation/Brands/Types/centos-4.svgz
new file mode 100644
index 0000000..bfb97c2
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-4.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-5-p.svgz b/Artworks/Documentation/Brands/Types/centos-5-p.svgz
new file mode 100644
index 0000000..c1c73e6
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-5-p.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-5.svgz b/Artworks/Documentation/Brands/Types/centos-5.svgz
new file mode 100644
index 0000000..e9ad7e8
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-5.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-6-p.svgz b/Artworks/Documentation/Brands/Types/centos-6-p.svgz
new file mode 100644
index 0000000..687ec69
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-6-p.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-6.svgz b/Artworks/Documentation/Brands/Types/centos-6.svgz
new file mode 100644
index 0000000..8585c3b
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-6.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-7-p.svgz b/Artworks/Documentation/Brands/Types/centos-7-p.svgz
new file mode 100644
index 0000000..e5d85a6
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-7-p.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-7.svgz b/Artworks/Documentation/Brands/Types/centos-7.svgz
new file mode 100644
index 0000000..aadc35d
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-7.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-8-p.svgz b/Artworks/Documentation/Brands/Types/centos-8-p.svgz
new file mode 100644
index 0000000..ab102bc
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-8-p.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-8.svgz b/Artworks/Documentation/Brands/Types/centos-8.svgz
new file mode 100644
index 0000000..c1e9da5
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-8.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-9-p.svgz b/Artworks/Documentation/Brands/Types/centos-9-p.svgz
new file mode 100644
index 0000000..aeb2b56
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-9-p.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-9.svgz b/Artworks/Documentation/Brands/Types/centos-9.svgz
new file mode 100644
index 0000000..13907a1
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-9.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-art-p.svgz b/Artworks/Documentation/Brands/Types/centos-art-p.svgz
new file mode 100644
index 0000000..d57e89a
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-art-p.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-art.svgz b/Artworks/Documentation/Brands/Types/centos-art.svgz
new file mode 100644
index 0000000..d8e36fd
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-art.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-p.svgz b/Artworks/Documentation/Brands/Types/centos-p.svgz
new file mode 100644
index 0000000..9d0692c
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-p.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-r.svgz b/Artworks/Documentation/Brands/Types/centos-r.svgz
new file mode 100644
index 0000000..c975082
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-r.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos-tm.svgz b/Artworks/Documentation/Brands/Types/centos-tm.svgz
new file mode 100644
index 0000000..e19bb94
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos-tm.svgz differ
diff --git a/Artworks/Documentation/Brands/Types/centos.svgz b/Artworks/Documentation/Brands/Types/centos.svgz
new file mode 100644
index 0000000..26811b3
Binary files /dev/null and b/Artworks/Documentation/Brands/Types/centos.svgz differ
diff --git a/Artworks/Documentation/Corporate/common-design-model-fig1.svgz b/Artworks/Documentation/Corporate/common-design-model-fig1.svgz
new file mode 100644
index 0000000..91b88e1
Binary files /dev/null and b/Artworks/Documentation/Corporate/common-design-model-fig1.svgz differ
diff --git a/Artworks/Documentation/Corporate/common-design-model-fig2.svgz b/Artworks/Documentation/Corporate/common-design-model-fig2.svgz
new file mode 100644
index 0000000..38d267f
Binary files /dev/null and b/Artworks/Documentation/Corporate/common-design-model-fig2.svgz differ
diff --git a/Artworks/Documentation/Corporate/monolithic.svgz b/Artworks/Documentation/Corporate/monolithic.svgz
new file mode 100644
index 0000000..ca572fb
Binary files /dev/null and b/Artworks/Documentation/Corporate/monolithic.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/header-fig-1.svgz b/Artworks/Documentation/Distro/Anaconda/header-fig-1.svgz
new file mode 100755
index 0000000..7a8d5c1
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/header-fig-1.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/header-fig-2.svgz b/Artworks/Documentation/Distro/Anaconda/header-fig-2.svgz
new file mode 100755
index 0000000..b183a40
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/header-fig-2.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/header-fig-summary.svgz b/Artworks/Documentation/Distro/Anaconda/header-fig-summary.svgz
new file mode 100755
index 0000000..2c6a56c
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/header-fig-summary.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/progress-fig-1.svgz b/Artworks/Documentation/Distro/Anaconda/progress-fig-1.svgz
new file mode 100755
index 0000000..9ca9a2b
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/progress-fig-1.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/progress-fig-2.svgz b/Artworks/Documentation/Distro/Anaconda/progress-fig-2.svgz
new file mode 100755
index 0000000..ceb0db1
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/progress-fig-2.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/progress-fig-3.svgz b/Artworks/Documentation/Distro/Anaconda/progress-fig-3.svgz
new file mode 100755
index 0000000..5fdcd8b
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/progress-fig-3.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/progress-fig-4.svgz b/Artworks/Documentation/Distro/Anaconda/progress-fig-4.svgz
new file mode 100755
index 0000000..a14ac0d
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/progress-fig-4.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/progress-fig-5.svgz b/Artworks/Documentation/Distro/Anaconda/progress-fig-5.svgz
new file mode 100755
index 0000000..27ccbee
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/progress-fig-5.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/progress-fig-summary.svgz b/Artworks/Documentation/Distro/Anaconda/progress-fig-summary.svgz
new file mode 100755
index 0000000..f849e75
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/progress-fig-summary.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/splash-fig-1.svgz b/Artworks/Documentation/Distro/Anaconda/splash-fig-1.svgz
new file mode 100755
index 0000000..6015230
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/splash-fig-1.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/splash-fig-2.svgz b/Artworks/Documentation/Distro/Anaconda/splash-fig-2.svgz
new file mode 100755
index 0000000..2322cfc
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/splash-fig-2.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/splash-fig-summary.svgz b/Artworks/Documentation/Distro/Anaconda/splash-fig-summary.svgz
new file mode 100644
index 0000000..3d76b4a
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/splash-fig-summary.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/summary.svgz b/Artworks/Documentation/Distro/Anaconda/summary.svgz
new file mode 100755
index 0000000..b23b620
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/summary.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/syslinux-fig-1.svgz b/Artworks/Documentation/Distro/Anaconda/syslinux-fig-1.svgz
new file mode 100755
index 0000000..3f6b27c
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/syslinux-fig-1.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/syslinux-fig-2.svgz b/Artworks/Documentation/Distro/Anaconda/syslinux-fig-2.svgz
new file mode 100755
index 0000000..9b11d80
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/syslinux-fig-2.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/syslinux-fig-3.svgz b/Artworks/Documentation/Distro/Anaconda/syslinux-fig-3.svgz
new file mode 100755
index 0000000..bbed5ba
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/syslinux-fig-3.svgz differ
diff --git a/Artworks/Documentation/Distro/Anaconda/syslinux-fig-summary.svgz b/Artworks/Documentation/Distro/Anaconda/syslinux-fig-summary.svgz
new file mode 100755
index 0000000..5120530
Binary files /dev/null and b/Artworks/Documentation/Distro/Anaconda/syslinux-fig-summary.svgz differ
diff --git a/Artworks/Documentation/Distro/BootUp/firstboot-fig-1.svgz b/Artworks/Documentation/Distro/BootUp/firstboot-fig-1.svgz
new file mode 100644
index 0000000..4aee16f
Binary files /dev/null and b/Artworks/Documentation/Distro/BootUp/firstboot-fig-1.svgz differ
diff --git a/Artworks/Documentation/Distro/BootUp/firstboot-fig-summary.svgz b/Artworks/Documentation/Distro/BootUp/firstboot-fig-summary.svgz
new file mode 100644
index 0000000..8b46337
Binary files /dev/null and b/Artworks/Documentation/Distro/BootUp/firstboot-fig-summary.svgz differ
diff --git a/Artworks/Documentation/Fonts/dejavu-lgc.svgz b/Artworks/Documentation/Fonts/dejavu-lgc.svgz
new file mode 100644
index 0000000..55fb02d
Binary files /dev/null and b/Artworks/Documentation/Fonts/dejavu-lgc.svgz differ
diff --git a/Artworks/Documentation/Fonts/denmark.svgz b/Artworks/Documentation/Fonts/denmark.svgz
new file mode 100644
index 0000000..2acea0f
Binary files /dev/null and b/Artworks/Documentation/Fonts/denmark.svgz differ
diff --git a/Artworks/Documentation/Repository/Asciidoc/Distro/eula.asciidoc b/Artworks/Documentation/Repository/Asciidoc/Distro/eula.asciidoc
new file mode 100644
index 0000000..cc006fc
--- /dev/null
+++ b/Artworks/Documentation/Repository/Asciidoc/Distro/eula.asciidoc
@@ -0,0 +1,7 @@
+= CentOS =RELEASE= EULA
+The CentOS Project
+
+CentOS =RELEASE= comes with no guarantees or warranties of any sorts, either
+written or implied. The Distribution is released as
+file:///usr/share/doc/centos-release-5/GPL[GPL] work. Individual packages in
+the distribution come with their own licences.
diff --git a/Artworks/Documentation/Repository/Asciidoc/Distro/eula.conf b/Artworks/Documentation/Repository/Asciidoc/Distro/eula.conf
new file mode 100644
index 0000000..27a5361
--- /dev/null
+++ b/Artworks/Documentation/Repository/Asciidoc/Distro/eula.conf
@@ -0,0 +1,33 @@
+[eula-final/eula.docbook]
+source = "eula.asciidoc"
+command = "asciidoc --backend=docbook"
+
+[eula-final/eula.xhtml]
+source = "eula-final/eula.docbook"
+command = "centos-art render --backend=xhtml"
+
+[eula-final/eula.pdf]
+source = "eula-final/eula.docbook"
+command = "centos-art render --backend=pdf"
+
+#
+# Add rendition support for different languages too. The following
+# lines are valid when LANG environment variable doesn't begin with
+# `en' characters.
+#
+
+[eula-final-${LANG}/eula.docbook]
+source = "eula-final/eula.docbook"
+localization = "eula-l10n/${LANG}.po"
+command = "centos-art render --backend=docbook"
+
+[eula-final-${LANG}/eula.xhtml]
+source = "eula-final-${LANG}/eula.docbook"
+localization = "eula-l10n/${LANG}.po"
+command = "centos-art render --backend=xhtml"
+
+[eula-final-${LANG}/eula.pdf]
+source = "eula-final-${LANG}/eula.docbook"
+localization = "eula-l10n/${LANG}.po"
+command = "centos-art render --backend=pdf"
+
diff --git a/Artworks/Documentation/Repository/Asciidoc/Distro/firefox_service_agreement.asciidoc b/Artworks/Documentation/Repository/Asciidoc/Distro/firefox_service_agreement.asciidoc
new file mode 100644
index 0000000..cda14d5
--- /dev/null
+++ b/Artworks/Documentation/Repository/Asciidoc/Distro/firefox_service_agreement.asciidoc
@@ -0,0 +1,153 @@
+Mozilla Firefox - Website Services Agreement
+============================================
+
+The accompanying version of Mozilla Firefox utilizes website information
+services (``Services''), such as safe-browsing features, which are provided by
+the Mozilla Corporation and made available to you under additional terms. By
+using the Services, you consent to the terms of the referenced Mozilla Firefox
+Website Services Agreement.
+
+If you do not agree to these terms, do not use the Services and disable the
+Services in Edit -> Preferences -> Security and uncheck the options for both:
+``Tell me if the site I'm visiting is a suspected attack site'' and ``Tell me
+if the site I'm visiting is a suspected forgery.''
+
+Version 3.0, June 2008
+----------------------
+
+During the Mozilla Firefox installation process, and at later times, you may be
+given the option of installing additional components from third-party software
+providers. The installation and use of those third-party components may be
+governed by additional license agreements.
+
+In this Mozilla Firefox Website Services Agreement (``Agreement''), the
+accompanying executable version of Mozilla Firefox shall be referred to as
+``the Product''.
+
+The Product utilizes website information services (``Services''), such as
+safe-browsing features, which are provided by the Mozilla Corporation
+(``Mozilla'') and made available to you subject to the terms below. By using
+the Services, you consent to the terms of this Agreement. If you do not agree
+to the terms of this Agreement, do not use the Services and disable the
+Services in the preferences/security menu.
+
+Use Of Service
+~~~~~~~~~~~~~~
+
+Mozilla permits you to use the Services via the Product. This Agreement will
+also govern the use of Services made available to you as a result of your
+installing any executable software upgrades to the Product provided to you by
+CentOS, where those Services replace and/or supplement the Services provided
+through use of the Product. In such a case, ``the Product'' shall
+also refer to such installed upgrades. However, if such upgrades are
+accompanied by a separate agreement from Mozilla, the terms of that agreement
+will govern.
+
+Termination
+~~~~~~~~~~~
+
+If you breach this Agreement your right to use the Services will terminate
+immediately and without notice, but all provisions of this Agreement except the
+Use of Services (Paragraph 1) will survive termination and continue in effect.
+
+Proprietary Rights
+~~~~~~~~~~~~~~~~~~
+
+Subject to this Agreement and to all applicable licensing terms governing your
+use of the Product, Mozilla, for itself and on behalf of its licensors, hereby
+reserves all intellectual property rights in the Services, except for the
+rights expressly granted in this Agreement. You may not remove or alter any
+trademark, logo, copyright or other proprietary notice in or on the Product.
+This agreement does not grant you any right to use the trademarks, service
+marks or logos of Mozilla or its licensors. Nothing in this Agreement shall be
+construed to limit any rights granted under open source licenses applicable to
+the Product and to corresponding source code versions of the Product.
+
+Privacy Policy
+~~~~~~~~~~~~~~
+
+The Mozilla Firefox Privacy Policy is made available online at
+http://www.mozilla.com/legal/privacy/, as that policy may be updated from time
+to time.
+
+Website Information Services
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Mozilla and its contributors, licensors and partners work to provide the most
+accurate and up-to-date phishing and malware information. However, they cannot
+guarantee that this information is comprehensive and error-free: some risky
+sites may not be identified, and some safe sites may be identified in error.
+
+Disclaimer Of Warranty
+~~~~~~~~~~~~~~~~~~~~~~
+
+The product and services are provided ``as is'' with all faults. to the extent
+permitted by law, mozilla and mozilla's distributors, and licensors hereby
+disclaim all warranties, whether express or implied, including without
+limitation warranties that the product and services are free of defects,
+merchantable, fit for a particular purpose and non-infringing. you bear the
+entire risk as to selecting the product and services for your purposes and as
+to the quality and performance of the product and services. this limitation
+will apply notwithstanding the failure of essential purpose of any remedy.
+some jurisdictions do not allow the exclusion or limitation of implied
+warranties, so this disclaimer may not apply to you.
+
+Limitation Of Liability
+~~~~~~~~~~~~~~~~~~~~~~~
+
+Except as required by law, mozilla and its distributors, directors, licensors,
+contributors and agents (collectively, the ``mozilla group'') will
+not be liable for any indirect, special, incidental, consequential or exemplary
+damages arising out of or in any way relating to this agreement or the use of
+or inability to use the product and the services, including without limitation
+damages for loss of goodwill, work stoppage, lost profits, loss of data, and
+computer failure or malfunction, even if advised of the possibility of such
+damages and regardless of the theory (contract, tort or otherwise) upon which
+such claim is based. the mozilla group's collective liability under this
+agreement will not exceed the greater of $500 (five hundred dollars) and the
+fees paid by you under the license (if any). Some jurisdictions do not allow
+the exclusion or limitation of incidental, consequential or special damages, so
+this exclusion and limitation may not apply to you.
+
+U.S. Goverment End-Users
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+This Product is a ``commercial item,'' as that term is defined in 48
+C.F.R. 2.101, consisting of ``commercial computer software'' and
+``commercial computer software documentation,'' as such terms are
+used in 48 C.F.R. 12.212 (Sept. 1995) and 48 C.F.R. 227.7202 (June 1995).
+Consistent with 48 C.F.R. 12.212, 48 C.F.R. 27.405(b)(2) (June 1998) and 48
+C.F.R. 227.7202, all U.S. Government End Users acquire the Product with only
+those rights as set forth therein.
+
+Miscellaneous
+~~~~~~~~~~~~~
+
+a. This Agreement constitutes the entire agreement between Mozilla and you
+concerning the subject matter hereof, and it may only be modified by a written
+amendment signed by an authorized executive of Mozilla.
+
+b. Except to the extent applicable law, if any, provides otherwise, this
+Agreement will be governed by the laws of the state of California, U.S.A.,
+excluding its conflict of law provisions.
+
+c. This Agreement will not be governed by the United Nations Convention on
+Contracts for the International Sale of Goods.
+
+d. If any part of this Agreement is held invalid or unenforceable, that part
+will be construed to reflect the parties' original intent, and the remaining
+portions will remain in full force and effect
+
+e. A waiver by either party of any term or condition of this Agreement or any
+breach thereof, in any one instance, will not waive such term or condition or
+any subsequent breach thereof.
+
+f. Except as required by law, the controlling language of this Agreement is
+English.
+
+g. You may assign your rights under this Agreement to any party that consents
+to, and agrees to be bound by, its terms; the Mozilla Corporation may assign
+its rights under this Agreement without condition.
+
+h. This Agreement will be binding upon and inure to the benefit of the parties,
+their successors and permitted assigns.
diff --git a/Artworks/Documentation/Repository/Asciidoc/Distro/firefox_service_agreement.conf b/Artworks/Documentation/Repository/Asciidoc/Distro/firefox_service_agreement.conf
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/Artworks/Documentation/Repository/Asciidoc/Distro/firefox_service_agreement.conf
diff --git a/Artworks/Documentation/Repository/Asciidoc/Distro/firefox_startpage.asciidoc b/Artworks/Documentation/Repository/Asciidoc/Distro/firefox_startpage.asciidoc
new file mode 100644
index 0000000..a512a38
--- /dev/null
+++ b/Artworks/Documentation/Repository/Asciidoc/Distro/firefox_startpage.asciidoc
@@ -0,0 +1,44 @@
+Welcome to CentOS 5.8
+=====================
+The CentOS Project
+
+Abstract
+--------
+
+CentOS 5.8 comes with no guarantees or warranties of any sorts, either written
+or implied. The Distribution is released as
+file:///usr/share/doc/centos-release-5/GPL[GPL] work. Individual packages in
+the distribution come with their own licences.
+
+What is CentOS?
+---------------
+
+http://www.centos.org/[CentOS] is an Enterprise-class Linux Distribution
+derived from sources freely provided to the public by a prominent North
+American Enterprise Linux vendor. CentOS conforms fully with the upstream
+vendors redistribution policy and aims to be 100% binary compatible. (CentOS
+mainly changes packages to remove upstream vendor branding and artwork.)
+
+CentOS is developed by a small but growing team of core developers. In turn the
+core developers are supported by an active user community including system
+administrators, network administrators, enterprise users, managers, core Linux
+contributors and Linux enthusiasts from around the world.
+
+Advantages
+----------
+
+CentOS has numerous advantages including: an active and growing user community,
+quickly rebuilt, tested, and QA'ed errata packages, an extensive
+http://www.centos.org/modules/tinycontent/index.php?id=15[mirror network],
+developers who are contactable and responsive reliable Enterprise Linux class
+distribution, multiple free support avenues.
+
+Support
+-------
+The following free support avenues are available:
+
+- http://www.centos.org/[The CentOS Website]
+- http://wiki.centos.org/[The CentOS Wiki] (includes a dynaic http://wiki.centos.org/FAQs[FAQ])
+- http://www.centos.org/modules/tinycontent/index.php?id=8[The CentOS IRC Chat]
+- http://lists.centos.org/[The CentOS Mailing lists]
+- http://forums.centos.org/[The CentOS Forums]
diff --git a/Artworks/Documentation/Repository/Asciidoc/Distro/firefox_startpage.conf b/Artworks/Documentation/Repository/Asciidoc/Distro/firefox_startpage.conf
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/Artworks/Documentation/Repository/Asciidoc/Distro/firefox_startpage.conf
diff --git a/Artworks/Documentation/Repository/Asciidoc/Distro/rnotes.asciidoc b/Artworks/Documentation/Repository/Asciidoc/Distro/rnotes.asciidoc
new file mode 100644
index 0000000..2ae9e49
--- /dev/null
+++ b/Artworks/Documentation/Repository/Asciidoc/Distro/rnotes.asciidoc
@@ -0,0 +1,26 @@
+= CentOS =RELEASE= Release Notes
+The CentOS Project
+
+The CentOS =RELEASE= Release Notes are licensed under a
+http://creativecommons.org/licenses/by-sa/3.0/[Creative Common
+Attribution-ShareAlike 3.0 License].
+
+The CentOS Project welcomes you to CentOS =RELEASE=.
+
+The complete release notes for CentOS =RELEASE= can be found online at:
+http://wiki.centos.org/Manuals/ReleaseNotes/=RELEASE=/[http://wiki.centos.org/Manuals/ReleaseNotes/=RELEASE=/]
+
+A list of frequently asked questions and answers about CentOS =RELEASE= can be found
+online at: http://wiki.centos.org/FAQs/5/[http://wiki.centos.org/FAQs/5/]
+
+If you are looking for help with CentOS, we recommend you start at the
+http://wiki.centos.org/GettingHelp/[http://wiki.centos.org/GettingHelp/] for
+pointers to the different sources where
+you can get help.
+
+If you would like to contribute to The CentOS Project, see
+http://wiki.centos.org/HowToContribute/[http://wiki.centos.org/HowToContribute/]
+for areas where you could help.
+
+For more information about The CentOS Project in general please visit our
+homepage at: http://www.centos.org/[http://www.centos.org/]
diff --git a/Artworks/Documentation/Repository/Asciidoc/Distro/rnotes.conf b/Artworks/Documentation/Repository/Asciidoc/Distro/rnotes.conf
new file mode 100644
index 0000000..b1bd285
--- /dev/null
+++ b/Artworks/Documentation/Repository/Asciidoc/Distro/rnotes.conf
@@ -0,0 +1,32 @@
+[release-notes-final/release-notes.docbook]
+source = "release-notes.asciidoc"
+command = "asciidoc --backend=docbook"
+
+[release-notes-final/release-notes.xhtml]
+source = "release-notes-final/release-notes.docbook"
+command = "centos-art render --backend=xhtml"
+
+[release-notes-final/release-notes.pdf]
+source = "release-notes-final/release-notes.docbook"
+command = "centos-art render --backend=pdf"
+
+#
+# Add rendition support for different languages too. The following
+# lines are valid when LANG environment variable doesn't begin with
+# `en' characters.
+#
+
+[release-notes-final-${LANG}/release-notes.docbook]
+source = "release-notes-final/release-notes.docbook"
+localization = "release-notes-l10n/${LANG}.po"
+command = "centos-art render --backend=docbook"
+
+[release-notes-final-${LANG}/release-notes.xhtml]
+source = "release-notes-final-${LANG}/release-notes.docbook"
+localization = "release-notes-l10n/${LANG}.po"
+command = "centos-art render --backend=xhtml"
+
+[release-notes-final-${LANG}/release-notes.pdf]
+source = "release-notes-final-${LANG}/release-notes.docbook"
+localization = "release-notes-l10n/${LANG}.po"
+command = "centos-art render --backend=pdf"
diff --git a/Artworks/Documentation/Repository/Asciidoc/Repository/centos-artwork.asciidoc b/Artworks/Documentation/Repository/Asciidoc/Repository/centos-artwork.asciidoc
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/Artworks/Documentation/Repository/Asciidoc/Repository/centos-artwork.asciidoc
diff --git a/Artworks/Documentation/Repository/Asciidoc/Repository/centos-artwork.conf b/Artworks/Documentation/Repository/Asciidoc/Repository/centos-artwork.conf
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/Artworks/Documentation/Repository/Asciidoc/Repository/centos-artwork.conf
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-author.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-author.docbook
new file mode 100644
index 0000000..3d8d6a9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-author.docbook
@@ -0,0 +1,6 @@
+<author>
+
+ <!-- centos-art(docbook): book.bookinfo.author.firtname -->
+ <!-- centos-art(docbook): book.bookinfo.author.surname -->
+
+</author>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-copyright-holder.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-copyright-holder.docbook
new file mode 100644
index 0000000..ac998b8
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-copyright-holder.docbook
@@ -0,0 +1 @@
+<holder>&TCP;. All rights reserved.</holder>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-copyright-year.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-copyright-year.docbook
new file mode 100644
index 0000000..df9b499
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-copyright-year.docbook
@@ -0,0 +1 @@
+<year>YEAR</year>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-copyright.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-copyright.docbook
new file mode 100644
index 0000000..78f0186
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-copyright.docbook
@@ -0,0 +1,4 @@
+<copyright>
+ <!-- centos-art(docbook): book.bookinfo.copyright.year -->
+ <!-- centos-art(docbook): book.bookinfo.copyright.holder -->
+</copyright>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-legalnotice.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-legalnotice.docbook
new file mode 100644
index 0000000..5cb78bc
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-legalnotice.docbook
@@ -0,0 +1,10 @@
+<legalnotice>
+ <para>
+ 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 <xref linkend="licenses-gfdl" />.
+ </para>
+</legalnotice>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-revhistory-revision.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-revhistory-revision.docbook
new file mode 100644
index 0000000..7b09a2c
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-revhistory-revision.docbook
@@ -0,0 +1,8 @@
+<revision>
+
+ <!-- centos-art(docbook): book.bookinfo.revhistory.revision.revnumber
+ <!-- centos-art(docbook): book.bookinfo.revhistory.revision.date
+ <!-- centos-art(docbook): book.bookinfo.revhistory.revision.author
+ <!-- centos-art(docbook): book.bookinfo.revhistory.revision.revdescription
+
+</revision>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-revhistory.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-revhistory.docbook
new file mode 100644
index 0000000..cd07a1c
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo-revhistory.docbook
@@ -0,0 +1,5 @@
+<revhistory>
+
+ <!-- centos-art(docbook): book.bookinfo.revhistory.revision -->
+
+</revhistory>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo.docbook
new file mode 100644
index 0000000..2cb60f9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-bookinfo.docbook
@@ -0,0 +1,8 @@
+<bookinfo>
+
+ <!-- centos-art(docbook): book.bookinfo.author -->
+ <!-- centos-art(docbook): book.bookinfo.copyright -->
+ <!-- centos-art(docbook): book.bookinfo.legalnotice -->
+ <!-- centos-art(docbook): book.bookinfo.revhistory -->
+
+</bookinfo>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Book-subtitle.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-subtitle.docbook
new file mode 100644
index 0000000..b60a07e
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-subtitle.docbook
@@ -0,0 +1 @@
+<subtitle>BOOKSUBTITLE</subtitle>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Book-title.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-title.docbook
new file mode 100644
index 0000000..b54b481
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Book-title.docbook
@@ -0,0 +1,2 @@
+<title>BOOKTITLE</title>
+<!-- centos-art(docbook): book.subtitle -->
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Book.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Book.docbook
new file mode 100644
index 0000000..b447fc9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Book.docbook
@@ -0,0 +1,11 @@
+<?xml version="1.0"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" []>
+
+<book lang="en_US">
+
+ <!-- centos-art(docbook): book.title -->
+ <!-- centos-art(docbook): book.bookinfo -->
+ <!-- centos-art(docbook): book.preface -->
+ <!-- centos-art(docbook): book.part -->
+
+</book>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Book.ent b/Artworks/Documentation/Repository/Docbook/Default/Book/Book.ent
new file mode 100644
index 0000000..af62731
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Book.ent
@@ -0,0 +1,58 @@
+<!--
+ $Id$
+ This file defines entities for words and phrases frequently used
+ inside The CentOS Artwork Repository User's Guide. It is a way of
+ normalizing the use of concepts inside the documentation and make
+ their maintainance easier to realize.
+-->
+
+<!-- About Corporate Identity -->
+
+<!ENTITY CI "Corporate Identity">
+<!ENTITY CVI "Corporate Visual Identity">
+<!ENTITY CVIS "Corporate Visual Identity Structure">
+<!ENTITY MCVIS "Monolithic Corporate Visual Identity Structure">
+<!ENTITY VS "Visual Style">
+
+<!-- About The CentOS Project -->
+
+<!ENTITY C "CentOS">
+<!ENTITY TC "The &C;">
+<!ENTITY TCL "&TC; Logo">
+<!ENTITY TCS "&TC; Symbol">
+<!ENTITY TCT "&TC; Type">
+<!ENTITY TCB "&TC; Brand">
+<!ENTITY TCP "<ulink type='http' url='http://www.centos.org'>&TC; Project</ulink>">
+<!ENTITY TCC "&TC; Community">
+<!ENTITY TCD "&TC; Distribution">
+<!ENTITY TCA "&TC; Artwork">
+<!ENTITY TCM "<ulink url='http://mirrors.centos.org/'>&TC; Mirrors</ulink>">
+
+<!ENTITY TCPCI "&TCP; &CI;">
+<!ENTITY TCPCVI "&TCP; &CVI;">
+<!ENTITY TCPCVI "&TCP; &CVI;">
+<!ENTITY TCPCVIS "&TCP; &CVIS;">
+<!ENTITY TCPMCVIS "&TCP; &MCVIS;">
+
+<!ENTITY TCAR "<ulink type='https' url='https://projects.centos.org/svn/artwork'>&TCA; Repository</ulink>">
+<!ENTITY TCAS "<ulink type='https' url='https://projects.centos.org/trac/artwork'>&TCA; SIG</ulink>">
+
+<!ENTITY TCARUG "<citetitle>The CentOS Artwork Repository User's Guide</citetitle>">
+<!ENTITY TCDRS "&TCD; Release Schema">
+<!ENTITY TCAML "<email>centos-artwork@centos.org</email> mailing list">
+<!ENTITY TCDML "<email>centos-devel@centos.org</email> mailing list">
+<!ENTITY TCML "<email>centos-info@centos.org</email> mailing list">
+<!ENTITY TCW "&TC; Web">
+<!ENTITY TCWE "&TCW; Environment">
+<!ENTITY TCWIKI "<ulink type='http' url='http://wiki.centos.org/'>&TC; Wiki</ulink>">
+<!ENTITY TCML "<ulink type='http' url='http://lists.centos.org/'>&TC; Mailing Lists</ulink>">
+
+<!ENTITY TCS "&TC; Showroom">
+<!ENTITY TCBRAND "&TC; Brand">
+<!ENTITY TCLOGO "<xref linkend='identity-brand-logo' />">
+<!ENTITY TCTYPE "<xref linkend='identity-brand-type' />">
+<!ENTITY TCSYMBOL "<xref linkend='identity-brand-symbol' />">
+<!ENTITY TCMOTIF "<xref linkend='identity-brand-motif' />">
+<!ENTITY TCM "&TC; Mission">
+<!ENTITY TCDOCS "<ulink type='http' url='http://www.centos.org/docs/'>&TC; Documentation</ulink>">
+
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Part-partintro.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Part-partintro.docbook
new file mode 100644
index 0000000..c8467b4
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Part-partintro.docbook
@@ -0,0 +1,3 @@
+<partintro>
+ <!-- centos-art(dobook): book.part.partintro.para -->
+</partintro>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Part.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Part.docbook
new file mode 100644
index 0000000..7f13f50
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Part.docbook
@@ -0,0 +1,8 @@
+<part id="PART_NAME">
+
+ <title>PART_TITLE</title>
+
+ <!-- centos-art(docbook): book.part.partintro -->
+ <!-- centos-art(docbook): book.part.chapter -->
+
+</part>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Part/Chapter.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Part/Chapter.docbook
new file mode 100644
index 0000000..19f5bf7
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Part/Chapter.docbook
@@ -0,0 +1,7 @@
+<chapter id="CHAPTER_ID">
+
+ <title>CHAPTER_TITLE</title>
+
+ <!-- centos-art.sh(docbook): book.part.chapters.sections -->
+
+</chapter>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Part/Chapter/section.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Part/Chapter/section.docbook
new file mode 100644
index 0000000..1ca0bd5
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Part/Chapter/section.docbook
@@ -0,0 +1,13 @@
+<SECTION_TAG id="SECTION_ID">
+
+ <title>SECTION_TITLE</title>
+
+ <para>
+ Write the section content here.
+ </para>
+
+ <para>
+ ...
+ </para>
+
+</SECTION_TAG>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Preface.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Preface.docbook
new file mode 100644
index 0000000..42c8578
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Preface.docbook
@@ -0,0 +1,9 @@
+<preface id="preface">
+
+ <title>Preface</title>
+
+ &preface-overview;
+ &preface-docconvs;
+ &preface-feedback;
+
+</preface>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Preface/docconvs.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Preface/docconvs.docbook
new file mode 100644
index 0000000..17509ca
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Preface/docconvs.docbook
@@ -0,0 +1,225 @@
+<section id="preface-docconvs">
+
+ <title>Document Convenctions</title>
+
+ <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>
+
+ <variablelist>
+ <varlistentry>
+ <term><command>command</command></term>
+ <listitem>
+ <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 <keycap>Enter</keycap> 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 render
+ Identity/Images/Themes/TreeFlower/4/Distro/5/Anaconda
+ --filter="01-welcome"</command> command to produce the first
+ slide image used by Anaconda in the branch 5 of &TCD;
+ using the version 4 of TreeFlower artistic motif.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename>file name</filename></term>
+ <listitem>
+ <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">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
+ <filename>ImageMagick</filename> RPM package to convert
+ images from PNG format to other formats.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><keycap>key</keycap></term>
+ <listitem>
+ <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</command>, then a
+ character, and finally the <keycap>Tab</keycap> key. Your
+ terminal displays the list of files in the working
+ directory that begin with that character.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><keycombo action="simul"><keycap>key</keycap><keycap>combination</keycap></keycombo></term>
+ <listitem>
+ <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>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><computeroutput>computer output</computeroutput></term>
+ <listitem>
+ <para>
+ Text in this style indicates text displayed to a shell
+ prompt such as error messages and responses to commands.
+ For example, the <command>ls</command> command displays
+ the contents of a directory using this style:
+ </para>
+
+<screen>
+render_doTranslation.sh render_getDirTemplate.sh render_doBaseActions.sh
+render_getConfigOption.sh render_getOptions.sh render_doThemeActions.sh
+render_getDirOutput.sh render.sh
+</screen>
+
+ <para>
+ The output returned in response to the command (in this
+ case, the contents of the directory) is shown in this
+ style.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><prompt>prompt</prompt></term>
+ <listitem>
+ <para>
+ A prompt, which is a computer's way of signifying that it
+ is ready for you to input something, is shown in this
+ style. Examples:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <prompt>$</prompt>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <prompt>#</prompt>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <prompt>[centos@projects centos]$</prompt>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <prompt>projects login:</prompt>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><userinput>user input</userinput></term>
+ <listitem>
+ <para>
+ Text that the user types, either on the command line or
+ into a text box on a GUI screen, is displayed in this
+ style. In the following example,
+ <userinput>text</userinput> is displayed in this style: To
+ boot your system into the text based installation program,
+ you must type in the <userinput>text</userinput> command
+ at the <prompt>boot:</prompt> prompt.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><replaceable>replaceable</replaceable></term>
+ <listitem>
+ <para>
+ Text used in examples that is meant to be replaced with
+ data provided by the user is displayed in this style. In
+ the following example,
+ <replaceable>version-number</replaceable> is displayed in
+ this style: The directory for the kernel source is
+ <filename
+ class="directory">/usr/src/kernels/<replaceable>version-number</replaceable>/</filename>,
+ where <replaceable>version-number</replaceable> is the
+ version and type of kernel installed on this system.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <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 <filename
+ class="directory">/usr/share/doc/</filename> 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/Artworks/Documentation/Repository/Docbook/Default/Book/Preface/feedback.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Preface/feedback.docbook
new file mode 100644
index 0000000..14cc875
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Preface/feedback.docbook
@@ -0,0 +1,43 @@
+<section id="preface-feedback">
+
+ <title>Send In Your Feedback</title>
+
+ <para>
+ &TCAR; is an ongoing work which might contain errors and
+ require new features. If you find errors inside &TCAR; or have
+ any suggestion, we want to know about it.
+ </para>
+
+ <para>
+ To report errors and suggestions about &TCAR; you need to do
+ the following:
+ </para>
+
+ <orderedlist>
+ <listitem>
+ <para>
+ <ulink url="https://projects.centos.org/trac/artwork/register">Register yourself in the bug tracker</ulink>.</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://projects.centos.org/trac/artwork/login">Log in the bug tracker using your account.</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://projects.centos.org/trac/artwork/newticket">Write a new ticket in the bug tracker using your account.</ulink>
+ </para>
+ </listitem>
+
+ <para>
+ While you are writing your feedback report, please keep in
+ mind that it is very useful that you be specific about the
+ issue you are reporting in order for others be able of
+ reproducing it and, this way, find a solution for it. For
+ example, consider to include all the error messages you see in
+ your screen and the exact order of commands you used to
+ perform actions when using the centos-art.sh script.
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Book/Preface/overview.docbook b/Artworks/Documentation/Repository/Docbook/Default/Book/Preface/overview.docbook
new file mode 100644
index 0000000..34d81db
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Book/Preface/overview.docbook
@@ -0,0 +1,13 @@
+<section id="preface-overview">
+
+ <title>Overview</title>
+
+ <para>
+ Summarize, in a few paragraphs, what this book is all about.
+ </para>
+
+ <para>
+ ...
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Licenses/Gfdl/gfdl.docbook b/Artworks/Documentation/Repository/Docbook/Default/Licenses/Gfdl/gfdl.docbook
new file mode 100644
index 0000000..89b468a
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Licenses/Gfdl/gfdl.docbook
@@ -0,0 +1,608 @@
+<?xml version="1.0"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" []>
+
+<appendix id="licenses-gfdl">
+
+ <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>
+
+ <sect1 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" />, 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>
+
+ </sect1>
+
+ <sect1 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 id="modified-version" xreflabel="Modified Version">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 id="secondary-section" xreflabel="Secondary Section">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 <xref linkend="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 id="invariant-sections" xreflabel="Invariant
+ Sections">The <quote>Invariant Sections</quote> are certain
+ <xref linkend="secondary-section" /> 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 Section then
+ there are none.</para>
+
+ <para id="cover-texts" xreflabel="Cover Texts">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 id="transparent" xreflabel="Transparent">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 <xref linkend="transparent" /> file format whose
+ markup, or absence of markup, has been arranged to thwart or
+ discourage subsequent modification by readers is not <xref
+ linkend="transparent" />. An image format is not <xref
+ linkend="transparent" /> if used for any substantial amount of
+ text. A copy that is not <quote><xref linkend="transparent"
+ /></quote> is called <quote>Opaque</quote>.</para>
+
+ <para>Examples of suitable formats for <xref linkend="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 id="title-page" xreflabel="Title Page">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>
+
+ </sect1>
+
+ <sect1 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>
+
+ </sect1>
+
+ <sect1 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 <xref linkend="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 <xref linkend="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 <xref linkend="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 <xref linkend="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>
+
+ </sect1>
+
+ <sect1 id="licenses-gfdl-section-5" xreflabel="Modification">
+
+ <title>Modifications</title>
+
+ <para>
+ You may copy and distribute a <xref
+ linkend="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 <xref linkend="modified-version" /> under
+ precisely this License, with the <xref
+ linkend="modified-version" /> filling the role of the
+ Document, thus licensing distribution and modification of
+ the <xref linkend="modified-version" /> to whoever
+ possesses a copy of it. In addition, you must do these
+ things in the <xref linkend="modified-version" />:
+ </para>
+
+ <orderedlist numeration="upperalpha">
+
+ <listitem>
+ <para>Use in the <xref linkend="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 <xref linkend="title-page" />, as
+ authors, one or more persons or entities responsible
+ for authorship of the modifications in the <xref
+ linkend="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 <xref linkend="title-page" /> the
+ name of the publisher of the <xref
+ linkend="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 <xref linkend="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 <xref linkend="invariant-sections" /> and required
+ <xref linkend="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 <xref
+ linkend="modified-version" /> as given on the <xref
+ linkend="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 <xref linkend="title-page"
+ />, then add an item describing the <xref
+ linkend="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 <xref
+ linkend="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 <xref
+ linkend="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 <xref linkend="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 <xref linkend="invariant-sections"
+ />.</para> </listitem>
+
+ <listitem>
+ <para>Preserve any Warranty Disclaimers.</para>
+ </listitem>
+ </orderedlist>
+
+ <para>
+ If the <xref linkend="modified-version" /> includes new
+ front-matter sections or appendices that qualify as <xref
+ linkend="secondary-section" /> 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 <xref
+ linkend="invariant-sections"/> in the <xref
+ linkend="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 <xref linkend="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 <xref
+ linkend="cover-texts"/> in the <xref
+ linkend="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
+ <xref linkend="modified-version" />.
+ </para>
+
+ </sect1>
+
+ <sect1 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 <xref linkend="invariant-sections"/> of
+ all of the original documents, unmodified, and list them all
+ as <xref linkend="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 <xref
+ linkend="invariant-sections"/> may be replaced with a single
+ copy. If there are multiple <xref
+ linkend="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 <xref linkend="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>
+
+ </sect1>
+
+ <sect1 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>
+
+ </sect1>
+
+ <sect1 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 <xref
+ linkend="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>
+
+ </sect1>
+
+ <sect1 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
+ <xref linkend="invariant-sections" />with translations
+ requires special permission from their copyright holders, but
+ you may include translations of some or all <xref
+ linkend="invariant-sections" /> in addition to the original
+ versions of these <xref linkend="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>
+
+ </sect1>
+
+ <sect1 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>
+
+ </sect1>
+
+ <sect1 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>
+
+ </sect1>
+
+ <sect1 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>
+
+<screen>
+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>.
+</screen>
+
+ <para>If you have <xref linkend="invariant-sections" />,
+ Front-Cover Texts and Back-Cover Texts, replace the
+ <quote>with...Texts</quote>. line with this:</para>
+
+<screen>
+with the Invariant Sections being LIST THEIR TITLES, with the
+Front-Cover Texts being LIST, and with the Back-Cover Texts being
+LIST.
+</screen>
+
+ <para>If you have <xref linkend="invariant-sections" />
+ without <xref linkend="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>
+
+ </sect1>
+
+</appendix>
diff --git a/Artworks/Documentation/Repository/Docbook/Default/Licenses/Gpl/gpl.docbook b/Artworks/Documentation/Repository/Docbook/Default/Licenses/Gpl/gpl.docbook
new file mode 100644
index 0000000..7394198
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Default/Licenses/Gpl/gpl.docbook
@@ -0,0 +1,539 @@
+<?xml version="1.0"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" []>
+<appendix id="licenses-gpl">
+
+ <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>
+
+ <sect1 id="licenses-gpl-0" xreflabel="Preamble">
+
+ <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:
+ </para>
+
+ <orderedlist numeration="arabic">
+ <listitem>
+ <para>copyright the software, and</para>
+ </listitem>
+ <listitem>
+ <para>offer you this license which gives you legal
+ permission to copy, distribute and/or modify the
+ software.</para>
+ </listitem>
+ </orderedlist>
+
+ <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>
+
+ </sect1>
+
+ <sect1 id="licenses-gpl-1">
+
+ <title>Terms and Conditions for Copying, Distribution and Modification</title>
+
+ <sect2 id="licenses-gpl-1-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>
+
+ </sect2>
+
+ <sect2 id="licenses-gpl-1-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 <xref linkend="licenses-gpl-1-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.
+ </para>
+ </listitem>
+ </orderedlist>
+
+ <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>
+ 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>
+
+ </sect2>
+
+ <sect2 id="licenses-gpl-1-3" xreflabel="Section 3">
+
+ <title>Section 3</title>
+
+ <para>
+ You may copy and distribute the Program (or a work based on
+ it, under <xref linkend="licenses-gpl-1-2" />) in object code
+ or executable form under the terms of <xref
+ linkend="licenses-gpl-1-1" /> and <xref
+ linkend="licenses-gpl-1-2" /> above provided that you also do
+ one of the following:
+ </para>
+
+ <orderedlist numeration="loweralpha">
+ <listitem>
+ <para>
+ Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of
+ <xref linkend="licenses-gpl-1-1" /> and <xref
+ linkend="licenses-gpl-1-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 <xref
+ linkend="licenses-gpl-1-1" /> and <xref
+ linkend="licenses-gpl-1-2" /> above on a medium customarily
+ used for software interchange; or,
+ </para>
+ </listitem>
+
+ <listitem>
+ <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>
+ 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>
+
+ </sect2>
+
+ <sect2 id="licenses-gpl-1-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>
+
+ </sect2>
+
+ <sect2 id="licenses-gpl-1-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>
+
+ </sect2>
+
+ <sect2 id="licenses-gpl-1-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>
+
+ </sect2>
+
+ <sect2 id="licenses-gpl-1-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>
+
+ </sect2>
+
+ <sect2 id="licenses-gpl-1-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>
+
+ </sect2>
+
+ <sect2 id="licenses-gpl-1-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>
+
+ </sect2>
+
+ <sect2 id="licenses-gpl-1-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>
+
+ </sect2>
+
+ <sect2 id="licenses-gpl-1-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>
+
+ </sect2>
+
+ <sect2 id="licenses-gpl-1-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>
+
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="licenses-gpl-2" xreflabel="How to Apply These Terms to Your New Programs">
+
+ <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>
+
+<screen>
+<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.
+</screen>
+
+ <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>
+
+<screen>
+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.
+</screen>
+
+ <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>
+
+<screen>
+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
+</screen>
+
+ <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>
+
+ </sect1>
+
+</appendix>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity.docbook
new file mode 100644
index 0000000..d36b086
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity.docbook
@@ -0,0 +1,17 @@
+<part id="identity">
+
+ <title>Corporate Visual Identity</title>
+
+ <partintro>
+ <para>
+ ...
+ </para>
+ </partintro>
+
+ &identity-project;
+ &identity-brand;
+ &identity-distro;
+ &identity-web;
+ &identity-showroom;
+
+</part>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity.ent b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity.ent
new file mode 100644
index 0000000..144c375
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity.ent
@@ -0,0 +1,19 @@
+<!ENTITY identity SYSTEM "Identity.docbook">
+<!ENTITY identity-project SYSTEM "Identity/Project.docbook">
+<!ENTITY identity-project-mission SYSTEM "Identity/Project/mission.docbook">
+<!ENTITY identity-project-behaviour SYSTEM "Identity/Project/behaviour.docbook">
+<!ENTITY identity-project-communication SYSTEM "Identity/Project/communication.docbook">
+<!ENTITY identity-project-design SYSTEM "Identity/Project/design.docbook">
+<!ENTITY identity-project-structure SYSTEM "Identity/Project/structure.docbook">
+
+<!ENTITY identity-brand SYSTEM "Identity/Brand.docbook">
+<!ENTITY identity-brand-intro SYSTEM "Identity/Brand/intro.docbook">
+<!ENTITY identity-brand-symbol SYSTEM "Identity/Brand/symbol.docbook">
+<!ENTITY identity-brand-type SYSTEM "Identity/Brand/type.docbook">
+<!ENTITY identity-brand-logo SYSTEM "Identity/Brand/logo.docbook">
+<!ENTITY identity-brand-motif SYSTEM "Identity/Brand/motif.docbook">
+<!ENTITY identity-distro SYSTEM "Identity/Distribution.docbook">
+<!ENTITY identity-showroom SYSTEM "Identity/Showroom.docbook">
+
+<!ENTITY identity-web SYSTEM "Identity/Web.docbook">
+<!ENTITY identity-web-intro SYSTEM "Identity/Web/intro.docbook">
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand.docbook
new file mode 100644
index 0000000..0c0ba19
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand.docbook
@@ -0,0 +1,11 @@
+<chapter id="identity-brand">
+
+ <title>The CentOS Brand</title>
+
+ &identity-brand-intro;
+ &identity-brand-symbol;
+ &identity-brand-type;
+ &identity-brand-logo;
+ &identity-brand-motif;
+
+</chapter>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/intro.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/intro.docbook
new file mode 100644
index 0000000..84a602a
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/intro.docbook
@@ -0,0 +1,49 @@
+<sect1 id="identity-brand-intro">
+
+ <title>Introduction</title>
+
+ <para>
+ &TCBRAND; is the main visual manifestaion of &TCP;. &TCP;
+ uses &TCBRAND; to connect all the visual manifestions it is
+ made of (e.g., GNU/Linux Distributions, Web sites, Stationery,
+ etc.) and, this way, provides recognition
+ <footnote>
+ <para>
+ ... just as a GPG signature might do for RPM packages.
+ </para>
+ </footnote>
+ among similar projects available on the Internet. The CentOS
+ Brand is made of a graphical component (&TCSYMBOL;) and a
+ typographical component (&TCTYPE;) that, when put together,
+ make &TCLOGO;. The components that make &TCBRAND; can be used
+ together or separately, considering that, in hierarchy order,
+ &TCLOGO; is rather prefered than &TCSYMBOL;, as well as
+ &TCSYMBOL; is rather prefered than &TCTYPE;.
+ </para>
+
+ <para>
+ In addition to those components mentioned above, &TCBRAND;
+ includes another component named &TCMOTIF;. &TCMOTIF; is
+ mainly used as background on images and is directly related to
+ the look and feel of all visual manifestations &TCP; shows its
+ existence on. In contrast with &TCLOGO;, &TCSYMBOL; and
+ &TCTYPE;; &TCMOTIF; might change from time to time providing a
+ vehicle to <quote>refresh</quote> how &TCP; looks and feels.
+ </para>
+
+ <para>
+ &TCBRAND; and all the visual manifestations derivated from it
+ are available for you to study and propose improvement around
+ a good citizen's will inside &TCC;, but you are not allowed to
+ redistribute them elsewhere, without the given permission of
+ &TCP;.
+ </para>
+
+ <para>
+ If you need to redistribute either &TCLOGO; or any visual
+ manifestation derived from it, write your intentions to the
+ The CentOS Developers mailing list (<ulink
+ url="mailto:centos-devel@centos.org">centos-devel@centos.org</ulink>).
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/logo.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/logo.docbook
new file mode 100644
index 0000000..ee01fda
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/logo.docbook
@@ -0,0 +1,17 @@
+<sect1 id="identity-brand-logo" xreflabel="&TCL;">
+
+ <title>&TCL;</title>
+
+ <para>
+ &TCL; is a construction made of &TCS; and &TCT;. &TCS; and
+ &TCL; are the main visual manifestations of the organization
+ known as &TCP;. As &TCS;, &TCL; is used to
+ <quote>brand</quote> images produced by &TCP; and provide a
+ visual connection between images so they can be monolithically
+ recognized as part of &TCP;. &TCL; must be exactly the same
+ every time it is printed out and a route to reproduce it in
+ such a way must be available so as to avoid reproduction
+ mistakes when images are branded with it.
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/motif.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/motif.docbook
new file mode 100644
index 0000000..7341757
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/motif.docbook
@@ -0,0 +1,5 @@
+<sect1 id="identity-brand-motif" xreflabel="The CentOS Motif">
+ <title>The CentOS Motif</title>
+ <para>...</para>
+</sect1>
+
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/symbol.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/symbol.docbook
new file mode 100644
index 0000000..7ddeb03
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/symbol.docbook
@@ -0,0 +1,15 @@
+<sect1 id="identity-brand-symbol" xreflabel="&TCS;">
+
+ <title>&TCS;</title>
+
+ <para>
+ &TCS; is the graphical part of &TCL;. As &TCL;, &TCS; is used
+ to <quote>brand</quote> images produced by &TCP; and provide a
+ visual connection between images so they can be monolithically
+ recognized as part of &TCP;. &TCS; must be exactly the same
+ every time it is printed out and a route to reproduce it in
+ such a way must be available so as to avoid reproduction
+ mistakes when images are branded with it.
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/type.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/type.docbook
new file mode 100644
index 0000000..d76106b
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Brand/type.docbook
@@ -0,0 +1,17 @@
+<sect1 id="identity-brand-type" xreflabel="&TCT;">
+
+ <title>&TCT;</title>
+
+ <para>
+ &TCT; is the typographical part of &TCL;. Comparing with both
+ &TCL; and &TCS;, &TCT; by its own, provides poor visual
+ connection between images that intend to be recognized as a
+ monolithic part of &TCP; and shouldn't be used alone.
+ Instead, &TCL; or &TCS; are preferred. &TCS; must be exactly
+ the same every time it is printed out and a route to reproduce
+ it in such a way must be available so as to avoid reproduction
+ mistakes when images are branded with it.
+ </para>
+
+</sect1>
+
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Distribution.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Distribution.docbook
new file mode 100644
index 0000000..0236910
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Distribution.docbook
@@ -0,0 +1,16 @@
+<chapter id="identity-distro">
+
+ <title>The CentOS Distribution</title>
+ <para>...</para>
+
+ <sect1>
+ <title>Release Schema</title>
+ <para>...</para>
+ </sect1>
+
+ <sect1>
+ <title>...</title>
+ <para>...</para>
+ </sect1>
+
+</chapter>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project.docbook
new file mode 100644
index 0000000..3634415
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project.docbook
@@ -0,0 +1,41 @@
+<chapter id="identity-project">
+
+ <title>The CentOS Project</title>
+
+ <para>
+ The CentOS Project Corporate Identity is the
+ <quote>persona</quote> 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 Corporate Design,
+ Corporate Communication, and Corporate Behaviour.
+ </para>
+
+ <figure id="identity-project-structure-fig1">
+ <title>The CentOS Project Corporate Identity.</title>
+ <screenshot>
+ <screeninfo>The CentOS Project Corporate Identity.</screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="=TCAR_WORKDIR=/Documentation/Manuals/Svg/Corporate/monolithic.png" format="PNG" />
+ </imageobject>
+ </mediaobject>
+ </screenshot>
+ </figure>
+
+ &identity-project-mission;
+ &identity-project-design;
+ &identity-project-communication;
+ &identity-project-behaviour;
+ &identity-project-structure;
+
+</chapter>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/behaviour.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/behaviour.docbook
new file mode 100755
index 0000000..bd22f04
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/behaviour.docbook
@@ -0,0 +1,21 @@
+<sect1 id="identity-project-behaviour">
+
+ <title>Corporate Behaviour</title>
+
+ <para>
+ &TCP; corporate behaviour is focused on the effective
+ interaction of each member involved in the organization (e.g.,
+ core developers, community members, etc.). It is related to
+ ethics and politics used to do the things inside the
+ organization. It is related to the sense of direction chosen
+ by the organization and they way the organization projects
+ itself to achieve it.
+ </para>
+
+ <para>
+ &TCP; corporate behaviour takes place through &TCP; corporate
+ communication, as described in <xref
+ linkend="identity-project-communication" />.
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/communication.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/communication.docbook
new file mode 100755
index 0000000..c46dd12
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/communication.docbook
@@ -0,0 +1,141 @@
+<sect1 id="identity-project-communication">
+
+ <title>Corporate Communication</title>
+
+ <para>
+ &TCP; corporate communication is focused on the effective
+ propagation of corporate messages. Propagation of corporate
+ messages is closely related to the media the organization uses
+ as vehicle to distribute its corporate messages.
+ </para>
+
+ <para>
+ &TCP; corporate communication takes place through the
+ following visual manifestations:
+ </para>
+
+ <variablelist>
+
+ <varlistentry>
+ <term>&TCD;</term>
+ <listitem>
+ <para>
+ This visual manifestation communicates its existence
+ through software packages. There are packages that make a
+ remarkable use of images, packages that make a moderate
+ use of images, and packages that don't use images at all.
+ This visual manifestation is focused on providing &TCP;
+ images required by software packages that do use images in
+ a remarkable way, specially those holding the upstream
+ brand (e.g., <package>anaconda</package>,
+ <package>grub</package>, <package>syslinux</package>,
+ <package>gdm</package>, <package>kdebase</package>).
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The Community Enterprise Operating System itself
+ (communicates the essense of &TCP; existence.).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Release Schema (Lifetime) and all the stuff related (e.g.,
+ Release Notes, Documentation, Erratas, etc.).
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>&TCW;</term>
+ <listitem>
+ <para>
+ This visual manifestation communicates its existence
+ through web applications. 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. Removing
+ these visual contraditions is object of work for this
+ visual manifestation.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The CentOS Chat.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The CentOS Mailing Lists.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The CentOS Forums.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The CentOS Wiki.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Special Interest Groups (SIGs).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Social Events, Interviews, Conferences, etc.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The extensive network of mirrors available for downloading
+ ISO files as well as RPMs and SRPMs used to build them up
+ in different architectures.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>&TCS;</term>
+ <listitem>
+ <para>
+ This visual manifestation communicates its existence
+ through production of industrial objects carrying &TCBRAND;.
+ These branded objects are directed to be distributed on
+ social events and/or shops. They provide a way of
+ promotion and commercialization that may help to reduce
+ &TCP; expenses (e.g., electrical power, hosting, servers,
+ full-time-developers, etc.), in a similar way as donations
+ may do.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Stationery (e.g., Posters, Stickers, CD Lables and Sleeves).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Clothes (e.g., Shirts, T-shirts, Pullovers, Caps).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Installation media (e.g., CDs, DVD, Pendrives).
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/design.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/design.docbook
new file mode 100755
index 0000000..7429c7f
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/design.docbook
@@ -0,0 +1,96 @@
+<sect1 id="identity-project-design">
+
+ <title>Corporate Graphic Design</title>
+
+ <para>
+ The corporate design is focused on the effective presentation
+ of corporate messages. As corporate messages we understand all
+ the information emitted from the organization; and when we say
+ <emphasis>all</emphasis> we mean everything that can be
+ perceived through the human senses. The corporate design takes
+ care of defining what this information is and controlling the
+ way it goes out the organization producing it.
+ </para>
+
+ <para>
+ When the organization doesn't take control over the corporate
+ messages it produces, the organization is letting that area of
+ its identity to the unknown and the results might be good or
+ not so good, it is hard to know. The issue to see here is
+ that even the organization doesn't take control over its
+ corporate messages, they are always talking about the
+ organization. Taking control of corporate messages is a
+ decition the organization needs to take by itself, based on
+ its need of better describe what it is.
+ </para>
+
+ <para>
+ In the very specific case of &TCP;, we'll concentrate our
+ attention on corporate messages that reach us through the
+ visual sense. This is, all the visual manifestations &TCP; is
+ made of. As visual manifestaions we understand all the visible
+ media &TCP; uses to manifest its existence on. At this point
+ it is necessary to consider what &TCP; is, what its mission is
+ and what it is producing. This, in order to identify which
+ visual manifestations the organization is demanding attention
+ of corporate design for.
+ </para>
+
+ <para>
+ Inside &TCP; we identify and apply corporate design to the
+ following visual manifestations:
+ </para>
+
+ <orderedlist numeration="arabic">
+
+ <listitem>
+ <para>
+ &TCD; — This visual manifestation exists to cover all
+ actions related to artwork production and rebranding, required
+ by &TCD; in order to comply with upstream's redistribution
+ guidelines. This visual manifestation is described in <xref
+ linkend="identity-distro" />.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ &TCW; — This visual manifestation exists to cover all
+ actions related to artwork production required by &TCP; to
+ manifest its existence in the World Wide Web medium. This
+ visual manifestation is described in <xref
+ linkend="identity-web" />.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ &TCS; — This visual manifestation exists to cover all
+ actions related to artwork production required by &TCP; to
+ manifest its existence through media produced industrially
+ (e.g., stationery, clothes, CDs, DVDs, etc.). This visual
+ manifestation is described in <xref
+ linkend="identity-showroom" />.
+ </para>
+ </listitem>
+ </orderedlist>
+
+ <para>
+ The visual manifestations identified above seem to cover most
+ media required by &TCP;, as organization, to show its
+ existence. However, other visual manifestations could be
+ added in the future, as long as they be needed, to cover
+ different areas like stands, buildings, offices, road
+ transportation or whaterver visual manifestation &TCP;
+ thouches to show its existence.
+ </para>
+
+ <para>
+ Once all visual manifestations have been identified and
+ defined through design models, it is time to visually remark
+ their connection with &TCP;. This kind of connection is
+ realized by applying &TCBRAND; to design models inside visual
+ manifestations supported through corporate design.
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/mission.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/mission.docbook
new file mode 100644
index 0000000..507873d
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/mission.docbook
@@ -0,0 +1,40 @@
+<sect1 id="identity-project-mission">
+
+ <title>Corporate Mission</title>
+
+ <para>
+ &TCP; exists to produce &TCD;, an Enterprise-class Linux
+ Distribution derived from sources freely provided to the
+ public by a prominent North American Enterprise Linux vendor.
+ &TCD; conforms fully with the upstream vendors redistribution
+ policy and aims to be 100% binary compatible. (&TCD; mainly
+ changes packages to remove upstream vendor branding and
+ artwork.).
+ </para>
+
+ <para>
+ &TCD; is developed by a small but growing team of core
+ developers. In turn the core developers are supported by an
+ active user community including system administrators, network
+ administrators, enterprise users, managers, core Linux
+ contributors and Linux enthusiasts from around the world.
+ </para>
+
+ <para>
+ &TCD; has numerous advantages including: an active and growing
+ user community, quickly rebuilt, tested, and QA'ed errata
+ packages, an extensive mirror network, developers who are
+ contactable and responsive of a reliable Enterprise-class
+ Linux Distribution, multiple free support avenues including a
+ <ulink type="http" url="http://wiki.centos.org/">Wiki</ulink>,
+ <ulink type="http"
+ url="http://www.centos.org/modules/tinycontent/index.php?id=8">IRC
+ Chat</ulink>, <ulink type="http"
+ url="http://lists.centos.org/">Email Lists</ulink>, <ulink
+ type="http"
+ url="http://www.centos.org/modules/newbb/">Forums</ulink>, and
+ a dynamic <ulink type="http"
+ url="http://www.centos.org/modules/smartfaq/">FAQ</ulink>.
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/structure.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/structure.docbook
new file mode 100755
index 0000000..a0d20f9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Project/structure.docbook
@@ -0,0 +1,91 @@
+<sect1 id="identity-project-structure">
+
+ <title>Corporate Structure</title>
+
+ <para>
+ &TCP; corporate structure is based on a &MCVIS;. In this
+ configuration, one unique name and one unique visual style is
+ used in all visual manifestation &TCP; is made of.
+ </para>
+
+ <para>
+ In a monolithic corporate visual identity structure, internal
+ and external stakeholders use to 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:
+ Hey! we are all part of &TCP;.
+ </para>
+
+ <para>
+ Other corporate structures for &TCP; have been considered as
+ well. Such is the case of producing one different visual style
+ for each major release of &TCD;. 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 &TCP;
+ is made of.
+ </para>
+
+ <para>
+ &TCP;, as organization, is mainly made of (but not limited to)
+ three visual manifestions: &TCD;, &TCW; and &TCS;. Inside
+ &TCD; visual manifestations, &TCP; maintains near to four
+ different major releases of &TCD;, parallely in time.
+ However, inside &TCW; 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 &TCD;
+ individually, but one web site to cover them all). Likewise,
+ the content produced in &TCS; is industrially created for no
+ specific release, but &TCP; in general.
+ </para>
+
+ <para>
+ In order to produce the &TCPMCVIS; correctly, we need to
+ concider all the visual manifestations &TCP; is made of, not
+ just one of them. If one different visual style is
+ implemented for each major release of &TCD;, which one of
+ those different visual styles would be used to cover the
+ remaining visual manifestations &TCP; is made of (e.g., &TCW;
+ and &TCS;)?
+ </para>
+
+ <para>
+ Probably you are thinking: yes, I see your point, but &TCBRAND;
+ 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 &TCP; 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. With
+ that in mind, we consider &TCPCVIS; must be consequent with
+ such stability and consistency tradition. It is true that
+ &TCBRAND; does connect all the visual manifestations it is present
+ on, but that connection is strengthened if one unique visual
+ style backups it. In fact, whatever thing you do to strength
+ the visual connection among &TCP; visual manifestations would
+ be very good in favor of &TCP; recognition.
+ </para>
+
+ <para>
+ Obviously, having just one visual style in all visual
+ manifestations for eternity would be a very boring thing and
+ would give the idea of a visually dead project. So, there is
+ no problem on creating a brand new visual style for each new
+ major release of &TCD;, in order to refresh &TCD; visual
+ style; the problem itself is in not propagating the brand new
+ visual style created for the new release of &TCD; to all other
+ visual manifestations &TCP; is made of, in a way &TCP; could
+ be recognized no matter what visual 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 &TCAR;.
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Showroom.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Showroom.docbook
new file mode 100644
index 0000000..db87232
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Showroom.docbook
@@ -0,0 +1,11 @@
+<chapter id="identity-showroom">
+
+ <title>The CentOS Showroom</title>
+ <para>...</para>
+
+ <sect1>
+ <title>...</title>
+ <para>...</para>
+ </sect1>
+
+</chapter>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Web.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Web.docbook
new file mode 100644
index 0000000..5a5ba5d
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Web.docbook
@@ -0,0 +1,7 @@
+<chapter id="identity-web">
+
+ <title>The CentOS Web</title>
+
+ &identity-web-intro;
+
+</chapter>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Web/intro.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Web/intro.docbook
new file mode 100644
index 0000000..956fa35
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Identity/Web/intro.docbook
@@ -0,0 +1,9 @@
+<sect1 id="identity-web-intro">
+
+ <title>Introduction</title>
+
+ <para>
+ ...
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Locales.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Locales.docbook
new file mode 100644
index 0000000..656b9d8
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Locales.docbook
@@ -0,0 +1,21 @@
+<part id="locale">
+
+ <title>Localization</title>
+
+ <partintro>
+ <para>...</para>
+ </partintro>
+
+ <chapter>
+ <title>...</title>
+ <para>...</para>
+
+ <sect1>
+ <title>...</title>
+ <para>...</para>
+ </sect1>
+
+ </chapter>
+
+</part>
+
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Locales.ent b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Locales.ent
new file mode 100644
index 0000000..48245e8
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Locales.ent
@@ -0,0 +1,2 @@
+<!ENTITY locales SYSTEM "Locales.docbook">
+
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals.docbook
new file mode 100644
index 0000000..44bacd4
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals.docbook
@@ -0,0 +1,30 @@
+<part id="manuals">
+
+ <title>Documentation</title>
+
+ <partintro>
+ <para>
+ &TCAR; documentation work line is implemented through
+ documentation manuals. Documentation manuals are
+ implemented through different documentation formats
+ provided inside &TCD; (e.g.,
+ <application>Docbook</application>,
+ <application>Texinfo</application>,
+ <application>LaTeX</application>, etc.). Structuring
+ tasks related to documentation systems (e.g., creating,
+ editing, deleting, copying, renaming, etc.) are
+ standardized through the <code>help</code> functionality
+ of <command>centos-art.sh</command> script, as described
+ in <xref linkend="scripts-bash-help" />. This way, people
+ writting documentation don't need to deal with underlaying
+ tasks like creating files, updating menus, nodes, cross
+ references and wondering where to put everything in
+ &TCAR;.
+ </para>
+
+ </partintro>
+
+ &manuals-production;
+ &manuals-formats;
+
+</part>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals.ent b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals.ent
new file mode 100644
index 0000000..c68bc34
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals.ent
@@ -0,0 +1,13 @@
+<!ENTITY manuals SYSTEM "Manuals.docbook">
+<!ENTITY manuals-production SYSTEM "Manuals/Production.docbook">
+<!ENTITY manuals-production-intro SYSTEM "Manuals/Production/intro.docbook">
+<!ENTITY manuals-production-identifying-goals SYSTEM "Manuals/Production/identifying-goals.docbook">
+<!ENTITY manuals-production-identifying-title SYSTEM "Manuals/Production/identifying-title.docbook">
+<!ENTITY manuals-production-identifying-structure SYSTEM "Manuals/Production/identifying-structure.docbook">
+<!ENTITY manuals-production-implementing-structure SYSTEM "Manuals/Production/implementing-structure.docbook">
+<!ENTITY manuals-production-maintaining-structure SYSTEM "Manuals/Production/maintaining-structure.docbook">
+<!ENTITY manuals-formats SYSTEM "Manuals/Formats.docbook">
+<!ENTITY manuals-formats-intro SYSTEM "Manuals/Formats/intro.docbook">
+<!ENTITY manuals-formats-texinfo SYSTEM "Manuals/Formats/texinfo.docbook">
+<!ENTITY manuals-formats-docbook SYSTEM "Manuals/Formats/docbook.docbook">
+<!ENTITY manuals-formats-latex SYSTEM "Manuals/Formats/latex.docbook">
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats.docbook
new file mode 100644
index 0000000..9fac62b
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats.docbook
@@ -0,0 +1,10 @@
+<chapter id="manuals-formats">
+
+ <title>Documentation Formats</title>
+
+ &manuals-formats-intro;
+ &manuals-formats-texinfo;
+ &manuals-formats-docbook;
+ &manuals-formats-latex;
+
+</chapter>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats/docbook.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats/docbook.docbook
new file mode 100644
index 0000000..1b7c5da
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats/docbook.docbook
@@ -0,0 +1,51 @@
+<sect1 id="manuals-formats-docbook">
+
+ <title>DocBook</title>
+
+ <para>
+ This section describes the implementation of DocBook
+ documentation format inside the <xref
+ linkend="scripts-bash-help"/> functionality of
+ <command>centos-art.sh</command> script. In this section we
+ assume you have a basic understanding of DocBook documentation
+ format. Otherwise, if you don't know what DocBook
+ documentation format is, take a look at <ulink
+ url="http://docbook.org/">DocBook website</ulink> and then,
+ come back here.
+ </para>
+
+ <sect2>
+ <title>Document Structure</title>
+ <para>
+ ...
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Document Templates</title>
+ <para>
+ ...
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Document Expansions</title>
+ <para>
+ ...
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Document Configuration</title>
+ <para>
+ ...
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Document Localization</title>
+ <para>
+ ...
+ </para>
+ </sect2>
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats/intro.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats/intro.docbook
new file mode 100644
index 0000000..f3d96f4
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats/intro.docbook
@@ -0,0 +1,24 @@
+<sect1 id="manuals-formats-intro">
+
+ <title>Introduction</title>
+
+ <para>
+ &TCD; provides support for different documentation formats,
+ including Texinfo, LaTeX, DocBook and LinuxDoc. These formats
+ have their own specifications and requirements to create and
+ maintain documentation manuals written through them. Inside
+ &TCAR;, the <xref linkend="scripts-bash-help" /> functionality
+ provides the interface you use to create and maintain
+ documentation manuals without needing to take care the
+ underlaying structuring tasks.
+ </para>
+
+ <para>
+ This chapter describes how the <xref
+ linkend="scripts-bash-help" /> functionality implements the
+ different documentation source formats available inside &TCD;,
+ and the internationalization issues related to documentation
+ manuals produced through them.
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats/latex.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats/latex.docbook
new file mode 100644
index 0000000..b777161
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats/latex.docbook
@@ -0,0 +1,47 @@
+<sect1 id="manuals-formats-latex">
+
+ <title>LaTeX</title>
+
+ <para>
+ This section describes the implementation of LaTeX
+ documentation format inside the <function>help</function>
+ functionality of centos-art.sh script described in <xref
+ linkend="scripts-bash-help" />. In this section we assume you
+ have a basic understanding of LaTeX language.
+ </para>
+
+ <sect2>
+ <title>Document Structure</title>
+ <para>
+ ...
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Document Templates</title>
+ <para>
+ ...
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Document Expansions</title>
+ <para>
+ ...
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Document Configuration</title>
+ <para>
+ ...
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Document Localization</title>
+ <para>
+ ...
+ </para>
+ </sect2>
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats/texinfo.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats/texinfo.docbook
new file mode 100644
index 0000000..801ec4b
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Formats/texinfo.docbook
@@ -0,0 +1,871 @@
+<sect1 id="manuals-formats-texinfo">
+
+ <title>Texinfo</title>
+
+ <para>
+ This section describes the implementation of Texinfo
+ documentation format inside the <xref
+ linkend="scripts-bash-help"/> functionality of
+ <command>centos-art.sh</command> script. In this section we
+ assume you have a basic understanding of Texinfo documentation
+ system. Otherwise, if you don't know what Texinfo
+ documentation system is, read the Texinfo manual first (e.g.,
+ by running the <command>info texinfo</command> command) and
+ then, come back here.
+ </para>
+
+ <sect2 id="manuals-formats-texinfo-structure">
+ <title>Document Structure</title>
+ <para>
+ The <xref linkend="scripts-bash-help"/> functionality of
+ <command>centos-art.sh</command> provides a document structure
+ that makes documentation manuals created through it to be
+ scalable and maintainable through time. This document
+ structure follows the idea of an upside-down tree to organize
+ chapters, sections, subsections and the like, as described in
+ <xref linkend="manuals-production-identifying-structure" />.
+ </para>
+
+ <para>
+ The <xref linkend="scripts-bash-help"/>
+ functionality creates documentation manuals source files in
+ the <filename
+ class="directory">Documentation/Models/Texinfo/</filename>
+ directory and saves output produced from them in the <filename
+ class="directory">Documentation/Manuals/Texinfo/</filename>
+ directory. To produce documentation manuals initial source
+ files, the <xref linkend="scripts-bash-help"/> functionality
+ uses Texinfo documentation templates, as described in <xref
+ linkend="manuals-formats-texinfo-templates" />.
+ </para>
+
+ <para>
+ Inside the documentation models directory, source files are
+ stored inside language-specific directories. The
+ language-specific directories are necessary to implement
+ internationalization of Texinfo source files, as described in
+ <xref linkend="manuals-formats-texinfo-l10n" />.
+ </para>
+
+ <para>
+ Inside the language-specific directory, the following files
+ exist to store the manual's main definitions (e.g., title,
+ subtitle, author, copyright notice, chapters, appendixes,
+ indexes and all similar stuff a documentation manual usually
+ has). In addition to these files, there is one directory for
+ each chapter created inside the manual. Inside each chapter
+ directory, you'll find the files controlling the section
+ definitions related each chapter they belong to. The section
+ files (a.k.a. <quote>documentation entries</quote>) are
+ suffixed with a <filename class="extension">texinfo</filename>
+ extension and named arbitrarily, as it is illustrated in <xref
+ linkend="manuals-formats-texinfo-structure-example1" />.
+ Inside section files it is where you write the manual's
+ content itself.
+ </para>
+
+ <example id="manuals-formats-texinfo-structure-example1">
+ <title>Texinfo document structure</title>
+ <screenshot>
+ <screeninfo>Texinfo document structure</screeninfo>
+ <mediaobject>
+ <textobject>
+ <programlisting>Documentation/Models/Texinfo/${MANUAL_NAME}
+`-- ${LANG}
+ |-- ${CHAPTER_NAME}/
+ | `-- ${SECTION_NAME}.texinfo
+ |-- ${CHAPTER_NAME}-menu.texinfo
+ |-- ${CHAPTER_NAME}-nodes.texinfo
+ |-- ${CHAPTER_NAME}.texinfo
+ |-- Licenses -> Documentation/Models/Texinfo/Default/${LANG}/Licenses
+ |-- Licenses-menu.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses-menu.texinfo
+ |-- Licenses-nodes.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses-nodes.texinfo
+ |-- Licenses.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses.texinfo
+ |-- ${MANUAL_NAME}.conf
+ |-- ${MANUAL_NAME}-index.texinfo
+ |-- ${MANUAL_NAME}-menu.texinfo
+ |-- ${MANUAL_NAME}-nodes.texinfo
+ `-- ${MANUAL_NAME}.texinfo</programlisting>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </example>
+
+ <para>
+ Texinfo (as in <package>texinfo-4.8-14.el5</package>) doesn't
+ support part sectioning inside documentation manuals, so
+ neither the <xref linkend="scripts-bash-help"/> functionality
+ does. Nevertheless, you can create several documentation
+ manuals and consider them as part of a bigger documentation
+ manual to workaround this issue.
+ </para>
+
+ <para>
+ In this document structure, the creation of documentation
+ manuals, chapters and sections is not limitted. You can create
+ as many documenation manuals, chapters and sections as you
+ need. The only limitation would be the amount of free space
+ required to store the Texinfo source files and the output
+ files produced from them in your workstation.
+ </para>
+
+ </sect2>
+
+ <sect2 id="manuals-formats-texinfo-templates">
+ <title>Document Templates</title>
+ <para>
+ Texinfo document templates provide the initial document
+ structure the <xref linkend="scripts-bash-help"/>
+ functionality needs in order to create and maintain document
+ structures, as described in <xref
+ linkend="manuals-formats-texinfo-structure" />.
+ </para>
+
+ <para>
+ Texinfo document templates are language-specific. This means
+ that there is (or, at least, must be) one Texinfo document
+ template for each language you plan to support documentation
+ manuals for. By default, &TCAR; provides a default Texinfo
+ document template under <filename class="directory">en_US</filename>
+ directory. This template structure is used when your current
+ locale is English language or when you are creating/editing a
+ documentation manual in a language other than English, but no
+ language-specific document template for that language exists
+ in the <filename
+ class="directory">Scripts/Documentation/Models/Texinfo/Default/</filename>
+ directory.
+ </para>
+
+ <para>
+ The <filename
+ class="directory">Scripts/Documentation/Models/Texinfo/Default/</filename>
+ directory organizes all Texinfo document templates using the
+ format LL_CC, where LL is the language code (as in ISO-639)
+ and CC the country code (as in ISO-3166). The directory
+ structure of Texinfo document templates is illustrated in the
+ <xref linkend="manuals-formats-texinfo-templates-example1" />
+ and implemented through the following files:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><filename>manual.texinfo</filename></term>
+ <listitem>
+ <para>
+ This file can be found inside the language-specific directory
+ and contains the manual's main definitions (e.g., document
+ title, document language, document authors, copyright notice,
+ etc.).
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename>manual-menu.texinfo</filename></term>
+ <listitem>
+ <para>
+ This file can be found inside the language-specific directory
+ and contains the menu definitions of chapters inside the
+ manual. When <xref linkend="scripts-bash-help" />
+ functionality creates instances of this file, menu definitions
+ inside it are automatically updated when a new chapter is
+ created or deleted through the <xref
+ linkend="scripts-bash-help"/> functionality. Generally, you
+ don't need to edit instances of this file once the
+ documentation manual has been created.
+ </para>
+ <para>
+ When a documentation manual is created for first time, this
+ file is copied from Texinfo document template directory
+ structure to the documentation manual being currently created.
+ At this specific moment, the instance created contains the
+ following Texinfo menu definition:
+ </para>
+
+<programlisting>
+@menu
+* Licenses::
+* Index::
+@end menu
+</programlisting>
+
+ <para>
+ Later, when chapters are added to or deleted from the
+ documentation manual, the content of this file varies adding
+ or deleting menu entries accordingly. Nevertheless, the two
+ entries shown above are ignored when new chapters are added to
+ or removed from the list, so they will always be present in
+ instances of this file. To preserve the manual consistency,
+ the <xref linkend="scripts-bash-help"/> functionality prevents
+ you from deleting any of these chapters once the documentation
+ manual has been created.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename>manual-nodes.texinfo</filename></term>
+ <listitem>
+ <para>
+ This file can be found inside the language-specific directory
+ and contains the node definitions of all chapters inside the
+ manual. When <xref linkend="scripts-bash-help"/>
+ functionality creates instances of this file, node definitions
+ inside it are automatically created based on menu definitions
+ (see <filename>manual-menu.texinfo</filename> file above) and
+ they don't include any content here. Instead, as part of the
+ node definition, the <code>@include</code> command is used to
+ connect each node with its content. Generally, you don't need
+ to edit instances of this file once the documentation manual
+ has been created.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename>manual-index.texinfo</filename></term>
+ <listitem>
+ <para>
+ This file can be found inside the language-specific directory
+ and contains the Texinfo commands used to generated an
+ organized view of all indexes you defined inside documentation
+ entries so they can be quickly accessed. Generally, you don't
+ need to edit instnaces of this file once the documentation
+ manual has been created.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename>manual.conf</filename></term>
+ <listitem>
+ <para>
+ This file contains the initial configuration of documentation
+ manuals written in Texinfo format. When a documentation manual
+ is created for first time, this file is copied into its target
+ directory so you be able to customize specific information
+ like menu order, title styles and template assignments
+ therein. The content of this file is described in <xref
+ linkend="manuals-formats-texinfo-configuration" />.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename>Chapters.texinfo</filename></term>
+ <listitem>
+ <para>
+ This file contains Texinfo's main chapter definition used
+ by <xref linkend="scripts-bash-help"/> functionality when new
+ chapters are created inside documentation manuals. When
+ chapters are created for first time, they come without any
+ introduction or documentation entry inside.
+ </para>
+ <para>
+ In case you need to add/update the chapters definition files,
+ edit the related chapter definition file inside the
+ documentation manual you are working on, not the template file
+ used to create it. To edit the chapter definition file, don't
+ provide any section information in the documentation entry.
+ For example, if you want to update the chapter introduction
+ related to <quote>trunk</quote> chapter inside
+ <quote>tcar-fs</quote> documentation manual, use the
+ <quote>tcar-fs::trunk:</quote> documentation entry.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename>Chapters-menu.texinfo</filename></term>
+ <listitem>
+ <para>
+ This file is part of Texinfo's main chapter definition and
+ should be initially empty. Later, when chapters are created
+ for first time, this file is copied as it is (i.e., empty)
+ into the documentation manual to store the Texinfo menu
+ entries related to all documentation entries created inside
+ the chapter. The Texinfo menu entries related to documentation
+ entries are automatically created using Texinfo source files
+ as reference.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename>Chapters-nodes.texinfo</filename></term>
+ <listitem>
+ <para>
+ This file is part of Texinfo's main chapter definition and
+ contains the node definition the <xref linkend="scripts-bash-help"/>
+ functionality uses as reference to create the list of Texinfo
+ nodes related to all documentation entries created inside the
+ chapter. The node definition of documentation entries is
+ automatically created from the menu definition of
+ documentation entries (see
+ <filename>Chapters-menu.texinfo</filename> file above), once it
+ has been updated from Texinfo source files.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename>section.texinfo</filename></term>
+ <listitem>
+ <para>
+ This file contains the Texinfo section definition used by
+ <xref linkend="scripts-bash-help"/> functionality when new
+ documentation entries are created inside chapters of
+ documentation manuals. When documentation entries are created
+ for first time, they are created as empty documentation
+ entries that you need to fill up with content. Again, if you
+ want to update the content of sections inside the
+ documentation manual, update the related documentation entry
+ inside the documentation manual, not the template file used to
+ create it.
+ </para>
+
+ <para>
+ The creation of documentation entries inside the documentation
+ manual is represented by the
+ <filename>${SECTION_NAME}.texinfo</filename> file, as
+ described in <xref
+ linkend="manuals-formats-texinfo-structure-example1" />. In
+ this example, <code>${SECTION_NAME}</code> is a variable
+ string referring the file name of documentation entries. The
+ file names of documentation entries are made of letters,
+ numbers and the minus sign (which is generally used as word
+ separator).
+ </para>
+
+ <para>
+ Documentation entries are not limited inside chapters of
+ documentation manuals. You can create as many documentation
+ entries as you need to describe the content of your manual.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>
+ There are other files which aren't related to manual's source
+ files, but to manual's output files. Such files are described
+ below and can be found either inside or outside the
+ language-specific directories so you can control common and
+ specific output settings through them. These files aren't
+ copied into the directory structure of new documentation
+ manuals created through the <xref linkend="scripts-bash-help"/>
+ functionality. Instead, they remain inside the template
+ directory structure so as to be reused each time the output of
+ documentation manuals is rendered.
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><filename>manual-init.pl</filename></term>
+ <listitem>
+ <para>
+ This file can be found inside and outside language-specific
+ directories and contains the Texi2html initialization script.
+ When this file is outside the language-specific directory, it
+ contains common customizations to all language-specific
+ outputs (e.g., changing the output DTD). When this file is
+ inside the language-specific directory, it contains
+ translations for that language-specific output (e.g., special
+ words like See, Index, Contents, Top, etc., are localized
+ here).
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename>manual.sed</filename></term>
+ <listitem>
+ <para>
+ This file can be found inside and outside language-specific
+ directories and contains special transformations for Texi2html
+ output. Again, when this file is inside language-specific
+ directories the transformation are applied to that
+ language-specific XHTML output and when it is outside
+ language-specific directories the transformations are applied
+ to all language-specific XHTML outputs. Most transformations
+ achieved through this file are to produce admonitions since
+ Texinfo documentation format (as in
+ <package>texinfo-4.8-14.el5</package>) doesn't have an
+ internal command to build them.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <example id="manuals-formats-texinfo-templates-example1">
+ <title>Template for texinfo document structures</title>
+ <screenshot>
+ <screeninfo>Template for texinfo document structures</screeninfo>
+ <mediaobject>
+ <textobject>
+ <programlisting>
+Documentation/Models/Texinfo/Default/
+|-- ${LANG}/
+| |-- Chapters/
+| | |-- section.texinfo
+| | `-- section-functions.texinfo
+| |-- Chapters-menu.texinfo
+| |-- Chapters-nodes.texinfo
+| |-- Chapters.texinfo
+| |-- Licenses/
+| | |-- GFDL.texinfo
+| | `-- GPL.texinfo
+| |-- Licenses-menu.texinfo
+| |-- Licenses-nodes.texinfo
+| |-- Licenses.texinfo
+| |-- manual-index.texinfo
+| |-- manual-init.pl
+| |-- manual-menu.texinfo
+| |-- manual-nodes.texinfo
+| |-- manual.conf
+| |-- manual.sed
+| `-- manual.texinfo
+|-- manual-init.pl
+`-- manual.sed
+</programlisting>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </example>
+
+ <para>
+ Inside the directory structure of Texinfo document templates,
+ the <filename class="directory">Chapters</filename> directory
+ stores section specific models used to create and maintain
+ section files inside manuals. File names beginning with
+ <quote>Chapters</quote>, at the same level of <filename
+ class="directory">Chapters</filename> directory, are used to
+ create chapter specific files inside manuals.
+ </para>
+
+ <para>
+ The <filename class="directory">Licenses</filename> directory
+ organizes the license information linked from all manuals.
+ Notice the license information is not copied into
+ documentation manuals when they are created, but referred from
+ models location where they are maintained. This configuration
+ permits all documentation manuals written in Texinfo format
+ inside &TCAR; to use the same license information. This way,
+ if a change is committed to license files, it will be
+ immediately propagated to all documentation manuals the next
+ time their output files be updated.
+ </para>
+ </sect2>
+
+ <sect2 id="manuals-formats-texinfo-macros">
+ <title>Document Expansions</title>
+ <para>
+ The document expansions are special constructions the <xref
+ linkend="scripts-bash-help" /> functionality provides to
+ generate content dynamically inside Texinfo source files.
+ </para>
+
+ <sect3>
+ <title>The <code>SeeAlso</code> Expansion</title>
+
+ <para>
+ This expansion creates a list of links with section entries
+ one level ahead from the section entry being currently
+ processed. In this construction, the TYPE variable can be
+ either <quote>itemize</quote>, <quote>enumerate</quote> or
+ <quote>menu</quote>. When no TYPE variable is provided, the
+ <quote>itemize</quote> value is considered as default.
+ </para>
+
+ <screen>@c -- <[centos-art(SeeAlso,TYPE)
+@c -- ]></screen>
+
+ <para>
+ This expansion might result useful when you are documenting
+ the repository file system. For example, if you are currently
+ editing the documentation entry related to <filename
+ class="directory">Identity</filename> directory and want
+ to create a linkable list of all documentation entries in the
+ first level under it, the code you'll have once the
+ construction be expanded would look like the following:
+ </para>
+
+<screen>
+@c -- <[centos-art(SeeAlso)
+@itemize
+@item @ref{Trunk Identity Brushes}
+@item @ref{Trunk Identity Fonts}
+@item @ref{Trunk Identity Images}
+@item @ref{Trunk Identity Models}
+@item @ref{Trunk Identity Palettes}
+@item @ref{Trunk Identity Patterns}
+@item @ref{Trunk Identity Webenv}
+@end itemize
+@c -- ]>
+</screen>
+
+ <para>
+ An interesting thing to notice here is that document
+ expansions are executed each time the related documentation
+ entry is edited or updated. Following with the example above,
+ if the documentation entries related to directories under
+ <filename class="directory">Identity</filename> changes
+ for some reason (e.g., they are removed from documentation
+ manual), the list generated as result of document expansion
+ will be updated automatically after editing the documentation
+ entry or updating the documentation manual structure.
+ </para>
+
+ </sect3>
+
+ </sect2>
+
+ <sect2 id="manuals-formats-texinfo-configuration">
+ <title>Document Configuration</title>
+ <para>
+ The document configuration is stored in the
+ <filename>${MANUAL_NAME}.conf</filename> file, inside the
+ documentation manual directory structure. This file is
+ originally copied from <filename>manual.conf</filename>
+ template file when the documentation manual is created for
+ first time. The content of
+ <filename>${MANUAL_NAME}.conf</filename> file is organized in
+ sections. Each section here is written in one line of its own
+ and have the form <code>[section_name]</code>. Under sections,
+ the configuration settings take place through
+ <code>name="value"</code> pairs set in one line each. Notice
+ that quotation marks around the option_value are required.
+ Comments are also possible using the <code>#</code> character
+ at the begining of lines. Comments and empty lines (including
+ tabs and white spaces) are ignored. In case more than one
+ section or option appear with the same name inside the
+ configuration file, the first one found will be used. Nested
+ section definitions are not supported.
+ </para>
+
+ <screen>[section_name]
+# This is a comment.
+option_name = "option_value"</screen>
+
+ <para>
+ The <filename>${MANUAL_NAME}.conf</filename> file is specific
+ to document templates. If you are using Texinfo document
+ template to create documentation manuals, then the default
+ configuration file for that documentation manual is taken from
+ Texinfo document template directory structure. However, if you
+ are using a document template different to Texinfo document
+ template, the default configuration file will be taken from
+ the related document template directory structure you are
+ creating the documentation manual from.
+ </para>
+
+ <sect3>
+ <title>The <code>[main]</code> Section</title>
+ <para>
+ The <code>[main]</code> section organizes settings that let
+ you customize the way sections and menu definitions are
+ created inside the documentation manual. The following options
+ are available in this section:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><code>manual_format</code></term>
+ <listitem>
+ <para>
+ This option specifies the documentation format used by manual.
+ To write documentation manuals in Texinfo format, the value
+ of this option must always be:
+ </para>
+ <screen>manual_format = "texinfo"</screen>
+ <caution>
+ <para>
+ Once the documentation manual has been created, you must not
+ change the value of <option>manual_format</option> option.
+ This will produce an error because there is not a migration
+ feature available yet. In the future, when you change this
+ value, it must be possible to transform documentation manuals
+ from one format to another.
+ </para>
+ </caution>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><code>manual_section_style</code></term>
+ <listitem>
+ <para>
+ This option specifies the title style used by sections inside
+ the manual. Possible values to this option are
+ `cap-each-word' to capitalize each word in the section title,
+ `cap-first-word' to capitalize the first word in the section
+ title only and `directory' to transform each word in the
+ section title into a directory path. From all these options,
+ `cap-each-word' is the one used as default.
+ </para>
+ <screen>manual_section_style = "cap-each-word"</screen>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><code>manual_section_order</code></term>
+ <listitem>
+ <para>
+ This option specifies the order used by sections inside the
+ manual. By default new sections added to the manual are put on
+ the end to follow the section order in which they were
+ `created'. Other possible values to this option are `ordered'
+ and `reversed' to sort the list of sections alphabetically
+ from A-Z and Z-A, respectively.
+ </para>
+ <screen>manual_section_order = "created"</screen>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </sect3>
+
+ <sect3>
+ <title>The <code>[templates]</code> Section</title>
+ <para>
+ The <code>[templates]</code> section provides the assignment
+ relation between template files and documentation entry files
+ inside the manual. The template definition is set on the left
+ side using relative path and the documentation entry files are
+ described on the right side using a regular expression. The
+ first match wins.
+ </para>
+ <screen>Chapters/section.texinfo = "^.+\.texinfo$"</screen>
+ </sect3>
+
+ </sect2>
+
+ <sect2 id="manuals-formats-texinfo-l10n">
+ <title>Document Localization</title>
+ <para>
+ To produce localized documentation manuals through Texinfo
+ documentation format it is necessary to create one
+ documentation manual for each language it is desired to
+ support documentation for. Documentation manuals created in
+ this configuration don't have a direct relation among
+ themselves except that one adopted by people writting them to
+ keep their content syncronized. In this configuration
+ translators take one documentation manual as reference (a.k.a.
+ the source manual) and produce several translated manuals
+ based on its content. To keep track of changes inside the
+ source manual, the underlaying version control system must be
+ used considering that there is no direct way to apply
+ <command>gettext</command><footnote>
+ <para>
+ The <command>gettext</command> program translates
+ a natural language message into the user's language, by
+ looking up the translation in a message catalog. For more
+ information about the <command>gettext</command>
+ program, run <command>info gettext</command>.
+ </para>
+ </footnote> procedures to Texinfo source files.
+ </para>
+
+ <para>
+ In order to maintain localization of Texinfo source files
+ through <command>gettext</command> procedures, it is necessary
+ to convert the Texinfo source files into XML format first.
+ This way it would be possible to make use of <xref
+ linkend="scripts-bash-locale"/> and <xref
+ linkend="scripts-bash-render"/> functionalities to maintain
+ translation messages in different languages through portable
+ objects and producing localized XML files based on such
+ portable objects, respectively. Once the localized XML file
+ is available, it would be a matter of using an XSLT processor
+ (see the <command>xsltproc</command> command) to realize the
+ convertion from XML to a localize Texinfo (or possible other)
+ format. Nevertheless, this workaround fails because the
+ Document Type Definition (DTD) required to validate the XML
+ file produced from <command>makeinfo</command> (as in
+ <package>texinfo-4.8-14.el5</package>) is not availabe inside
+ &TCD; (release 5.5), nor it is the XSLT files required to
+ realize the transformation itself for such DTD.
+ </para>
+
+ <para>
+ Another similar approach to maintain localization of Texinfo
+ source files through <command>gettext</command> procedures
+ would be to convert Texinfo source file to DocBook format; for
+ who the required DTD and XSLT files are available inside
+ &TCD;. This way, following a procedure similar to that one
+ describe for XML files above, it would be possible to end up
+ having localized DocBook files that can be used as source to
+ produce localized output for both online and printing media.
+ However, the DocBook output produced from
+ <command>makeinfo</command> command (as in
+ <package>texinfo-4.8-14.el5</package>) isn't a valid DocBook
+ document according to DocBook DTDs available inside &TCD;
+ (release 5.5) thus provoking the validation and transformation
+ of such a malformed document to fail.
+ </para>
+
+ <sect3 id="manuals-texinfo-l10n-language">
+ <title>Document Language</title>
+ <para>
+ The language information of those documentation manuals
+ produced through Texinfo documentation format is declared by
+ Texinfo's <code>@documentlanguage</code> command. This
+ command receives one argument refering the language code (as
+ in ISO-639 standard) and must be set inside the manual's main
+ definition file. Generally, there is no need to change the
+ document language declaration once it has been created by the
+ <xref linkend="scripts-bash-help"/> functionality; unless you
+ mistakently create the manual for a locale code different to
+ that one you previously pretended to do in first place, of
+ course.
+ </para>
+
+ <para>
+ The language information used in both Texinfo source files and
+ XHTML output produced by the <xref linkend="scripts-bash-help"/>
+ functionality is determined by the user's session
+ <envar>LANG</envar> environment variable. This variable can
+ be customized in the graphical login screen before login, or
+ once you've login by explicitly setting the value of
+ <envar>LANG</envar> environment variable inside the
+ <filename>~/.bash_profile</filename> file.
+ </para>
+
+ <tip>
+ <para>
+ To create documentation manuals in English language the
+ <envar>LANG</envar> environment variable must be set to
+ <code>en_US.UTF-8</code> or something similar. Likewise, if
+ you want to create documentation manuals in a language other
+ than English, be sure the <envar>LANG</envar> environment
+ variable is set to the appropriate locale code.<footnote>
+ <para>
+ The appropriate locale code to set here can be found in
+ the output produced by the <command>locale -a |
+ less</command> command.
+ </para></footnote>
+ </para>
+ </tip>
+
+ <para>
+ When producing output from Texinfo source files using the
+ <command>makeinfo</command> command (as in the
+ <package>texinfo-4.8-14.el5</package> package), the language
+ information set by <code>@documentlanguage</code> is ignored
+ in Info and HTML output, but cosidered by Tex program to
+ redefine various English words used in the PDF output (e.g.,
+ <quote>Chapters</quote>, <quote>Index</quote>,
+ <quote>See</quote>, and so on) based on the current language
+ set in.
+ </para>
+
+ </sect3>
+
+ <sect3 id="manuals-texinfo-l10n-encoding">
+ <title>Document Encoding</title>
+ <para>
+ The encoding information of documentation manuals produced
+ through Texinfo documentation format is declared by Texinfo's
+ <code>@documentencoding</code> command and can take either
+ <code>US-ASCII</code>, <code>ISO-8859-1</code>,
+ <code>ISO-8859-15</code> or <code>ISO-8859-2</code> as
+ argument. Nevertheless, you should be aware that the
+ <xref linkend="scripts-bash-help" /> functionality doesn't
+ declare the <code>@documentencoding</code> inside Texinfo
+ source files. Let's see why.
+ </para>
+
+ <para>
+ When the <code>@documentencoding</code> command is set in
+ Texinfo source files, the terminal encoding you use to read
+ the Info output produced from such files must be set to that
+ encoding information you provided as argument to
+ <code>@documentencoding</code> command; this, before using an
+ Info reader to open the Info output file in the terminal.
+ Otherwise, when the terminal and the Texinfo source files
+ encoding definition differ one another, characters defined
+ through Texinfo's special way of producing floating accents
+ won't be displayed as expected (even when the
+ <option>--enable-encoding</option> is provided to
+ <command>makeinfo</command> command). On the other hand, when
+ the <code>@documentencoding</code> command is not set in
+ Texinfo source files, it is possible to write and read
+ documentation manuals using the UTF-8 encoding without needing
+ to use Texinfo's special way of producing floating accents
+ because the terminal encoding would be able to interpret the
+ characters entered when the Texinfo source files were written
+ in first place.
+ </para>
+
+ <para>
+ When Texinfo's special way of producing floating accents isn't
+ used, HTML entities are not produced in XHTML output produced
+ by <command>texi2html</command>, nor in the HTML output
+ produced by <command>makeinfo</command>, nor in PDF output.
+ In this last case, when producing PDF output, you can realize
+ what the floating accents are by trying to produce an
+ accentuated Spanish <code>i</code> letter (e.g.,
+ <code>í</code>). When you do so, you'll note that that
+ construction puts the accentuation mark
+ <emphasis>over</emphasis> the <code>i</code> letter's dot,
+ instead of removing the <code>i</code> letter's dot and
+ put the accentuation mark on its place. In the case of XHTML
+ output, however, it is possible to produce well localized
+ XHTML output by setting
+ </para>
+
+ <screen><meta http-equiv="content-type" content="text/html; charset=UTF-8" /></screen>
+
+ <para>
+ on the head section of each XHTML output to instruct the web
+ browsers what encoding to use to display the document content.
+ Of course, in order to display the document content correctly,
+ the web browser should provide support for UTF-8 encoding.
+ </para>
+
+ <para>
+ These contradictions provide the reasons over which it was
+ decided not to set the <code>@documentencoding</code> in those
+ Texinfo source files produced by the <xref
+ linkend="scripts-bash-help" /> functionality.
+ </para>
+
+ </sect3>
+
+ </sect2>
+
+ <sect2 id="manuals-texinfo-l10n-conclusions">
+ <title>Conclusions</title>
+
+ <para>
+ Texinfo documentation format is very good producing online
+ documentation for reading text terminals. It provides feautres
+ to export source files to different output formats both for
+ reading online and paper. However, localized documents becomes
+ hard to maintain because it is required one document structure
+ for each language you want to produce documentation for.
+ </para>
+ <para>
+ Intermediate formats like XML and Docbook provide an
+ alternative to centralize localization of Texinfo document
+ source files, but there is no supported way inside &TCD; to
+ transformed a localized XML file back into texinfo format, nor
+ a way of producing well formed Docbook documents from Texinfo
+ source files. Thus, one Texinfo source structure for each
+ language to support is the solution adopted by <xref
+ linkend="scripts-bash-help" /> functionality.
+ </para>
+
+ <para>
+ When using Texinfo documentation format it is difficult to
+ produce well localized PDF outputs, but it is possible to
+ produce well localized Info, Text, and XHTML outputs as long
+ as no document encoding be explicitly set inside Texinfo
+ source files and UTF-8 be used as default terminal character
+ encoding.
+ </para>
+
+ </sect2>
+
+</sect1>
+
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production.docbook
new file mode 100644
index 0000000..58451f0
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production.docbook
@@ -0,0 +1,12 @@
+<chapter id="manuals-production">
+
+ <title>Documentation Production Cycle</title>
+
+ &manuals-production-intro;
+ &manuals-production-identifying-goals;
+ &manuals-production-identifying-title;
+ &manuals-production-identifying-structure;
+ &manuals-production-implementing-structure;
+ &manuals-production-maintaining-structure;
+
+</chapter>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/identifying-goals.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/identifying-goals.docbook
new file mode 100644
index 0000000..c47888c
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/identifying-goals.docbook
@@ -0,0 +1,50 @@
+<sect1 id="manuals-production-identifying-goals">
+
+ <title>Identifying Document Goals</title>
+
+ <para>
+ The first step in producing a documentation manual is to
+ clearly understand what you exactly need to document and why
+ you need to do so. The obvious answer to this question would
+ be to describe the basic ideas behind an implementation so it
+ can be useful once published. It is important that you find
+ out the reasons you need to do what you are doing and, also,
+ those helping you to retain the motivation to keep doing it in
+ the future. Otherwise, without such foundations, you'll surely
+ end up leaving the effort soon enough to make a lost cause
+ from your initial work.
+ </para>
+
+ <para>
+ Before <citetitle>The CentOS Artwork Repository File
+ System</citetitle> documentation manual would exist, there was
+ an emerging need to understand what each directory inside the
+ growing directory layout was for, how it could be used and
+ each directory could be connected one another. At that moment,
+ the directory layout was very unstable and explaining the
+ whole idea behind it was not possible, there were too many
+ changing concepts floating around which needed to be
+ considered in the same changing way. So, to understand what
+ was happening, the <citetitle>The CentOS Artwork Repository
+ File System</citetitle> documentation manual was created.
+ </para>
+
+ <para>
+ The <citetitle>The CentOS Artwork Repository File
+ System</citetitle> manual was conceived based on the idea of
+ documenting each directory inside the repository individually
+ and, later, by considering all directory documentations
+ altogether, it would be (hypothetically) possible to correct
+ the whole idea through an improvement cycle that would
+ consolidate the final idea we were trying to implement.
+ </para>
+
+ <para>
+ Other documentation manuals can be based on reasons different
+ from those described above, however, no matter what those
+ reasons are, it will be helpful to make yourself a clean idea
+ about what you are going to document exactly before putting
+ your hands on it.
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/identifying-structure.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/identifying-structure.docbook
new file mode 100644
index 0000000..8178a2e
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/identifying-structure.docbook
@@ -0,0 +1,145 @@
+<sect1 id="manuals-production-identifying-structure">
+ <title>Identifying Document Structure</title>
+ <para>
+ Once both the manual's title and the manual's directory name
+ have been defined, it is time for you to plan the document
+ structure through which the manual's content will be
+ organized.
+ </para>
+
+ <para>
+ The specific document structure you choose for a documentation
+ manuals is affected by the documentation format you use to
+ write documentation source files. Nevertheless, no matter
+ what the documentation format be, the document structure
+ produced from the <xref linkend="scripts-bash-help" />
+ functionality will always follow and upside-down tree
+ configuration for document structures. In this configuration,
+ documentation manuals can be organized through different
+ structural levels (e.g., parts, chapters, sections,
+ subsection, etc.) based on the support provided by the
+ documentation format you chose.
+ </para>
+
+ <para>
+ The <citetitle>The CentOS Artwork Repository File
+ System</citetitle> documentation manual was conceived to
+ document each directory structure &TCAR; is made of, using
+ Texinfo as main documentation format.
+ </para>
+
+ <para>
+ At this point we find that &TCAR; had more levels deep than
+ sectioning commands available inside documentation format.
+ This way it is not possible to use one sectioning command for
+ each directory level inside the repository directory structure
+ we need to document. Based on these issues, it is
+ imperative to re-accommodate the document structure in order
+ to be able of documenting every directory &TCAR; is made of,
+ using the sectioning levels supported by that documentation
+ format we chose, no matter how many levels deep the repository
+ directory structure had.
+ </para>
+
+ <para>
+ As consequence, <citetitle>The CentOS Artwork Repository File
+ System</citetitle> ended up being organized through the
+ following documentation structure:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term>Chapter 1. The <filename class="directory">trunk</filename>
+ Directory</term>
+ <listitem>
+ <para>
+ This chapter describes the <filename
+ class="directory">trunk</filename> directory inside the
+ repository and all subdirectories inside it. The first level
+ of directories (i.e., the <filename
+ class="directory">trunk</filename> directory itself) is
+ described inside the chapter entry. Deeper directory levels
+ are all documented through sections and have a file for their
+ own. It is also possible to write subsections and
+ subsubsections, however, they don't have a file for their own
+ as sections do. Subsections and Subsubsections should be
+ written as part of section files (i.e., when writting
+ sections).
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Chapter 2. The <filename class="directory">branches</filename>
+ Directory</term>
+ <listitem>
+ <para>
+ This chapter describes the <filename
+ class="directory">branches</filename> directory and all
+ directories inside it following the same structure described
+ for <filename class="directory">trunk</filename> directory
+ above.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Chapter 3. The <filename class="directory">tags</filename>
+ Directory</term>
+ <listitem>
+ <para>
+ This chapter describes the <filename
+ class="directory">tags</filename> directory and all
+ directories inside it following the same structure described
+ for <filename class="directory">trunk</filename> directory
+ above.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Appendix A. Licenses</term>
+ <listitem>
+ <para>
+ This appendix is confined to organize licenses mentioned
+ in the manual. The content of this appendix is out of
+ documenatation manual scope itself and is shared among all
+ documentation manuals written through the <xref
+ linkend="scripts-bash-help" /> functionality.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Index</term>
+ <listitem>
+ <para>
+ This chapter organizes links to those index definitions you
+ defined inside the documentation manual. The index information
+ displayed by this chapter is auto-generated each time the
+ manual's output files are created so this chapter is not
+ editable.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>
+ The document structure illustrated above is also considered
+ the default document structure used by the <xref
+ linkend="scripts-bash-help" /> functionality of
+ <command>centos-art.sh</command> script when you produce new
+ documentation manuals inside &TCAR;. In contrast with document
+ structure illustrated above, the default document structure
+ used by <xref linkend="scripts-bash-help" /> functionality
+ doesn't include sectioning constructions like parts, chapters,
+ sections, subsections and the like in the document structure
+ created. Such structuring constructions should be specified by
+ you when building the documentation manual. The only
+ exceptions to this restriction are sectioning structures used
+ to organize contents like <quote>Index</quote> and
+ <quote>Licenses</quote>, which are considered inseparable
+ components of documentation manuals stored inside &TCAR;.
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/identifying-title.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/identifying-title.docbook
new file mode 100644
index 0000000..2c8a8bd
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/identifying-title.docbook
@@ -0,0 +1,26 @@
+<sect1>
+ <title>Identifying Document Title</title>
+ <para>
+ Once you've make yourself an clean idea of what the
+ documentation manual is for and the needs behind it, it is
+ time for you to define the manual's title and the manual's
+ directory name. Both manuals' title and manual's directory
+ name describe what the documentation manual is about. The
+ manual's title is used inside the documentation while the
+ manual's directory name is used to store the related source
+ files inside &TCAR; directory structure. Generally, the
+ manual's title is a phrase of few words and the manual's
+ directory name is the abbreviation of that phrase set as
+ manual's title.
+ </para>
+
+ <para>
+ Following with our example, the manual's title chosen was
+ <citetitle>The CentOS Artwork Repository File
+ System</citetitle> and its directory name was set to
+ <quote><filename>Tcar-fs</filename></quote> to comply with the
+ file name convenctions described at <xref
+ linkend="repo-convs-filenames" />.
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/implementing-structure.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/implementing-structure.docbook
new file mode 100644
index 0000000..1feb428
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/implementing-structure.docbook
@@ -0,0 +1,12 @@
+<sect1 id="manuals-production-implementing-structure">
+
+ <title>Implementing Document Structure</title>
+
+ <para>
+ The document structure implementation is automated by the
+ <xref linkend="scripts-bash-help" /> functionality, as
+ described in <xref
+ linkend="manuals-production-identifying-structure" />.
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/intro.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/intro.docbook
new file mode 100644
index 0000000..5b3f328
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/intro.docbook
@@ -0,0 +1,21 @@
+<sect1>
+
+ <title>Introduction</title>
+
+ <para>
+ This chapter describes the procedure you should follow to
+ create and maintain documentation manuals inside &TCAR;.
+ </para>
+
+ <para>
+ This chapter describes general concepts that can be applied
+ through the documentation formats supported inside the
+ <function>help</function> functionality of
+ <command>centos-art.sh</command> script. To illustrate the
+ production process related to documentation manuals inside
+ &TCAR;, this chapter uses the <citetitle>The CentOS Artwork
+ Repository File System</citetitle> (TCAR-FS) documentation
+ manual as example.
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/maintaining-structure.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/maintaining-structure.docbook
new file mode 100644
index 0000000..f503380
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Manuals/Production/maintaining-structure.docbook
@@ -0,0 +1,12 @@
+<sect1 id="manuals-production-maintaining-structure">
+
+ <title>Maintaining Document Structure</title>
+
+ <para>
+ The document structure maintenance is implemented by the <xref
+ linkend="scripts-bash-help" /> functionality, as described in
+ <xref linkend="manuals-production-identifying-structure"
+ />.
+ </para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface.docbook
new file mode 100644
index 0000000..42c8578
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface.docbook
@@ -0,0 +1,9 @@
+<preface id="preface">
+
+ <title>Preface</title>
+
+ &preface-overview;
+ &preface-docconvs;
+ &preface-feedback;
+
+</preface>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface.ent b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface.ent
new file mode 100644
index 0000000..ce36070
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface.ent
@@ -0,0 +1,4 @@
+<!ENTITY preface SYSTEM "Preface.docbook">
+<!ENTITY preface-overview SYSTEM "Preface/overview.docbook">
+<!ENTITY preface-docconvs SYSTEM "Preface/docconvs.docbook">
+<!ENTITY preface-feedback SYSTEM "Preface/feedback.docbook">
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface/docconvs.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface/docconvs.docbook
new file mode 100644
index 0000000..17509ca
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface/docconvs.docbook
@@ -0,0 +1,225 @@
+<section id="preface-docconvs">
+
+ <title>Document Convenctions</title>
+
+ <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>
+
+ <variablelist>
+ <varlistentry>
+ <term><command>command</command></term>
+ <listitem>
+ <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 <keycap>Enter</keycap> 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 render
+ Identity/Images/Themes/TreeFlower/4/Distro/5/Anaconda
+ --filter="01-welcome"</command> command to produce the first
+ slide image used by Anaconda in the branch 5 of &TCD;
+ using the version 4 of TreeFlower artistic motif.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename>file name</filename></term>
+ <listitem>
+ <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">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
+ <filename>ImageMagick</filename> RPM package to convert
+ images from PNG format to other formats.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><keycap>key</keycap></term>
+ <listitem>
+ <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</command>, then a
+ character, and finally the <keycap>Tab</keycap> key. Your
+ terminal displays the list of files in the working
+ directory that begin with that character.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><keycombo action="simul"><keycap>key</keycap><keycap>combination</keycap></keycombo></term>
+ <listitem>
+ <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>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><computeroutput>computer output</computeroutput></term>
+ <listitem>
+ <para>
+ Text in this style indicates text displayed to a shell
+ prompt such as error messages and responses to commands.
+ For example, the <command>ls</command> command displays
+ the contents of a directory using this style:
+ </para>
+
+<screen>
+render_doTranslation.sh render_getDirTemplate.sh render_doBaseActions.sh
+render_getConfigOption.sh render_getOptions.sh render_doThemeActions.sh
+render_getDirOutput.sh render.sh
+</screen>
+
+ <para>
+ The output returned in response to the command (in this
+ case, the contents of the directory) is shown in this
+ style.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><prompt>prompt</prompt></term>
+ <listitem>
+ <para>
+ A prompt, which is a computer's way of signifying that it
+ is ready for you to input something, is shown in this
+ style. Examples:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <prompt>$</prompt>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <prompt>#</prompt>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <prompt>[centos@projects centos]$</prompt>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <prompt>projects login:</prompt>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><userinput>user input</userinput></term>
+ <listitem>
+ <para>
+ Text that the user types, either on the command line or
+ into a text box on a GUI screen, is displayed in this
+ style. In the following example,
+ <userinput>text</userinput> is displayed in this style: To
+ boot your system into the text based installation program,
+ you must type in the <userinput>text</userinput> command
+ at the <prompt>boot:</prompt> prompt.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><replaceable>replaceable</replaceable></term>
+ <listitem>
+ <para>
+ Text used in examples that is meant to be replaced with
+ data provided by the user is displayed in this style. In
+ the following example,
+ <replaceable>version-number</replaceable> is displayed in
+ this style: The directory for the kernel source is
+ <filename
+ class="directory">/usr/src/kernels/<replaceable>version-number</replaceable>/</filename>,
+ where <replaceable>version-number</replaceable> is the
+ version and type of kernel installed on this system.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <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 <filename
+ class="directory">/usr/share/doc/</filename> 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/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface/feedback.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface/feedback.docbook
new file mode 100644
index 0000000..b6f8334
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface/feedback.docbook
@@ -0,0 +1,14 @@
+<section id="preface-feedback">
+
+ <title>Send In Your Feedback</title>
+
+ <para>
+ If you find a bug in &TCAR; or this manual, we would like to
+ hear about it. To report bugs related to this manual, send an
+ e-mail to the <email>centos-devel@centos.org</email> mailing
+ list. When you write the bug report, take care of being
+ specific about the problem you are reporting on (e.g., where
+ it is, the section number, etc.) so we can found it easily.
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface/overview.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface/overview.docbook
new file mode 100644
index 0000000..b12e354
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Preface/overview.docbook
@@ -0,0 +1,84 @@
+<section id="preface-overview">
+
+ <title>Overview</title>
+
+ <para>
+ Welcome to &TCARUG;, the official documentation of &TCAR;.
+ </para>
+
+ <para>
+ This book describes the corporate visual identity of &TCP; and
+ the way it is produced. If you are interested in making &TCP;
+ a more beautiful project, this book is definitly for you.
+ </para>
+
+ <para>
+ To make the information in this book managable, it has been
+ organized in the following parts:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <xref linkend="repo" /> describes the convenctions you should
+ follow to keep everything organized and consistent inside the
+ repository directory structure, how to to install and
+ configure a working copy inside your workstation. At the end
+ of this part you will find a history of most relevant changes
+ committed to the repository along the years.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <xref linkend="identity" /> describes the corporate visual
+ identity of the organization known as &TCP; and the production
+ tasks related to image rendition inside &TCAR;. If you are a
+ graphic designer, this part of the book might result
+ interesting to you.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <xref linkend="locale" /> describes production tasks related to
+ content internationalization and localization inside &TCAR;.
+ If you are a translator, this part of the book might result
+ interesting to you.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <xref linkend="manuals" /> describes production tasks related
+ to content documentation inside &TCAR;. If you are a
+ documentor, this part of the book might result interesting to
+ you.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <xref linkend="scripts" /> describes automation of production
+ tasks inside &TCAR;. If you are a programmer, this part of the
+ book might result interesting to you.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <xref linkend="licenses" /> organizes the licenses mentioned
+ in this book.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ This book assumes you have a basic understanding of &TCD;. If
+ you need help with it, go to the <ulink
+ url="http://wiki.centos.org/Help">Help</ulink> page inside
+ &TCWIKI; for or a list of different places you can find help.
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository.docbook
new file mode 100644
index 0000000..ea8dd86
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository.docbook
@@ -0,0 +1,9 @@
+<part id="repo">
+
+ <title>Repository</title>
+
+ &repo-convs;
+ &repo-ws;
+ &repo-history;
+
+</part>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository.ent b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository.ent
new file mode 100644
index 0000000..f0a40a4
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository.ent
@@ -0,0 +1,26 @@
+<!ENTITY repo SYSTEM "Repository.docbook">
+<!ENTITY repo-convs SYSTEM "Repository/Conventions.docbook">
+<!ENTITY repo-convs-mission SYSTEM "Repository/Conventions/mission.docbook">
+<!ENTITY repo-convs-infra SYSTEM "Repository/Conventions/infra.docbook">
+<!ENTITY repo-convs-worklines SYSTEM "Repository/Conventions/worklines.docbook">
+<!ENTITY repo-convs-directories SYSTEM "Repository/Conventions/directories.docbook">
+<!ENTITY repo-convs-relbdirs SYSTEM "Repository/Conventions/relbdirs.docbook">
+<!ENTITY repo-convs-syncpaths SYSTEM "Repository/Conventions/syncpaths.docbook">
+<!ENTITY repo-convs-extending SYSTEM "Repository/Conventions/extending.docbook">
+<!ENTITY repo-convs-filenames SYSTEM "Repository/Conventions/filenames.docbook">
+<!ENTITY repo-convs-publishing SYSTEM "Repository/Conventions/publishing.docbook">
+<!ENTITY repo-convs-authoring SYSTEM "Repository/Conventions/authoring.docbook">
+<!ENTITY repo-convs-copying SYSTEM "Repository/Conventions/copying.docbook">
+
+<!ENTITY repo-ws SYSTEM "Repository/Workstation.docbook">
+<!ENTITY repo-ws-intro SYSTEM "Repository/Workstation/intro.docbook">
+<!ENTITY repo-ws-install SYSTEM "Repository/Workstation/install.docbook">
+<!ENTITY repo-ws-config SYSTEM "Repository/Workstation/config.docbook">
+
+<!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">
+<!ENTITY repo-history-2012 SYSTEM "Repository/History/2012.docbook">
+<!ENTITY repo-history-2013 SYSTEM "Repository/History/2013.docbook">
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions.docbook
new file mode 100644
index 0000000..792bcd5
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions.docbook
@@ -0,0 +1,17 @@
+<chapter id="repo-convs">
+
+ <title>Repository Conventions</title>
+
+ &repo-convs-mission;
+ &repo-convs-infra;
+ &repo-convs-worklines;
+ &repo-convs-directories;
+ &repo-convs-filenames;
+ &repo-convs-relbdirs;
+ &repo-convs-syncpaths;
+ &repo-convs-extending;
+ &repo-convs-publishing;
+ &repo-convs-authoring;
+ &repo-convs-copying;
+
+</chapter>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/authoring.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/authoring.docbook
new file mode 100755
index 0000000..06a4394
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/authoring.docbook
@@ -0,0 +1,30 @@
+<section id="repo-convs-authoring">
+
+ <title>Repository Authoring</title>
+
+ <para>
+ The content produced inside &TCAR; is copyright of &TCP;.
+ This is something you, as author, should be aware of because
+ you are contributing your creation's rights to someone else;
+ &TCP; in this case. This way, your work is distributed using
+ <quote>&TCP;</quote> as copyright holder, not your name (even
+ you remain as natural author of the work). Because &TCP; is
+ the copyright holder, is the license chosen by &TCP; the one
+ applied to your work, so it is the one you need to agree with
+ before making a creation inside &TCAR;.
+ </para>
+
+ <para>
+ &TCP; is a community project controlled by its own community
+ of users. Inside the community, The CentOS Administrators
+ group is the higher authority and the only one able to set
+ core desition like the kind of license used inside the project
+ and subprojects like &TCAR;.
+ </para>
+
+ <para>
+ The redistribution conditions of &TCAR; are described in <xref
+ linkend="repo-convs-copying" />.
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/copying.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/copying.docbook
new file mode 100755
index 0000000..6ecabc2
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/copying.docbook
@@ -0,0 +1,60 @@
+<section id="repo-convs-copying">
+
+ <title>Repository Copying Conditions</title>
+
+ <para>
+ &TCP; uses &TCAR; to produce &TCP; corporate visual identity.
+ </para>
+
+ <para>
+ The &TCAR; is not in the public domain; it is 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 work that they might get from you.
+ </para>
+
+ <para>
+ Specifically, we want to make sure that you have the right to
+ give away copies of &TCAR;, that you receive source code or
+ else can get it if you want it, that you can change this work
+ or use pieces of it in new free works, 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 &TCAR;, 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 &TCAR;.
+ If this work 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 &TCAR; is released as a GPL work. Individual packages
+ used by &TCAR; include their own licenses and the &TCAR;
+ license applies to all packages that it does not clash with.
+ If there is a clash between the &TCAR; license and individual
+ package licenses, the individual package license applies
+ instead.
+ </para>
+
+ <para>
+ The precise conditions of the license for the &TCAR; are found
+ in <xref linkend="licenses-gpl" />. This manual specifically
+ is covered by the conditions found in <xref
+ linkend="licenses-gfdl" />.
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/directories.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/directories.docbook
new file mode 100755
index 0000000..c980bb2
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/directories.docbook
@@ -0,0 +1,794 @@
+<section id="repo-convs-directories">
+
+ <title>Repository Directory Structure</title>
+
+ <para>
+ This section describes the directory structure of &TCAR;. You
+ can use this section as reference to know where the files you
+ are looking at are stored in and where you can store new
+ files, as well. This section organizes directories'
+ description using the same hierarchy the repository has. This
+ section begins describing the first level of directories in
+ the repository and continues with each relevant sub-directory
+ in the hierarchy, one by one.
+ </para>
+
+ <para>
+ The directory structure this section describes is based on the
+ document <quote><emphasis>&TCAR; Directory
+ Structure</emphasis>,</quote> available at:
+ <filename>Documentation/Models/Svg/Repository/directory-structure.svgz</filename>
+ </para>
+
+ <section id="repo-convs-directories-artworks">
+ <title>The <filename class="directory">Artworks</filename> Directory</title>
+ <para>
+ This directory contains the files used to produce the
+ corporate visual identity of &TCP;. The information in this
+ directory is organized in Brushes, Gradients, Fonts, Images,
+ Models, Palettes, Patterns and Webenv directories.
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><filename class="directory">Artworks/Brushes/</filename></term>
+ <listitem>
+ <para>
+ This directory contains GIMP brushes. Brushes stored in this
+ directory will be available inside GIMP's brushes dialog. This
+ directory organizes brushes files inside <filename
+ class="directory">Images</filename> and <filename
+ class="directory">Models</filename> directories. Inside
+ <filename class="directory">Models</filename> directory we
+ find the GIMP projects used to build the brush images.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Patterns/</filename></term>
+ <listitem>
+ <para>
+ This directory contains GIMP patterns. Patterns stored in this
+ directory will be available inside GIMP's patterns dialog. This
+ directory organizes patterns files inside <filename
+ class="directory">Images</filename> and <filename
+ class="directory">Models</filename> directories. Inside
+ <filename class="directory">Models</filename> directory we
+ find the GIMP projects used to build the pattern images.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Gradients/</filename></term>
+ <listitem>
+ <para>
+ This directory contains GIMP gradients. Gradients stored in
+ this directory will be available inside GIMP's gradients
+ dialog. This directory organizes gradient files inside
+ <filename class="directory">Images</filename> and <filename
+ class="directory">Models</filename> directories. Inside
+ <filename class="directory">Models</filename> directory we
+ find the GIMP projects used to build the gradient images.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Fonts/</filename></term>
+ <listitem>
+ <para>
+ This directory contains font files. Font files stored in this
+ directory will be available to be used from applications like
+ GIMP and Inkscape. This directory organizes font files inside
+ <filename class="directory">Images</filename> and <filename
+ class="directory">Models</filename> directories. Inside
+ <filename class="directory">Models</filename> directory we
+ find the Fontforge projects used to build the font files,
+ which are stored in the <filename
+ class="directory">Images</filename> directory.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Images/</filename></term>
+ <listitem>
+ <para>
+ This directory contains final images. The directory structure
+ used to organize files here is rather similar to that used in
+ <filename class="directory">Artworks/Models/</filename>
+ directory structure.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Images/Themes/</filename></term>
+ <listitem>
+ <para>
+ This directory contains image files rendered from design
+ models that use theme background images. In this location you
+ can also find design models used to create the background
+ images, too.
+ </para>
+ <caution>
+ <para>
+ Design models used to build themes' background images must not
+ be moved to <filename
+ class="directory">Artworks/Models/Themes/</filename> directory
+ structure. Design models used to build themes' background
+ images are theme-specific, so they must be inside <filename
+ class="directory">Artworks/Images/Themes/</filename> directory
+ structure.
+ </para>
+ </caution>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/</filename></term>
+ <listitem>
+ <para>
+ This directory contains theme directory structure
+ organized in version number. Here, ${THEME_NAME} is a
+ string of letters representing the name of the theme. In
+ this string, all letters are written in lowercase except
+ the first one which must be written in uppercase.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/</filename></term>
+ <listitem>
+ <para>
+ This directory contains the theme directory structure
+ organized in theme components. Here, ${THEME_VERSION} is a
+ string with the form M.N, where M and N are integer
+ numbers from 0 to 9. M is required and .N is optional.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Backgrounds/</filename></term>
+ <listitem>
+ <para>
+ This directory contains theme-specific background images
+ and design models used to build them. This directory is a
+ key component of theme concept. It provides background
+ images to different sizes which are use on different theme
+ components, as defined by theme design models stored at
+ <filename
+ class="directory">Artworks/Models/Themes</filename>
+ directory.
+ </para>
+
+ <table id="repo-convs-directories-tb1">
+ <title>Theme-specific background files</title>
+ <tgroup cols='2' align='left' colsep='1' rowsep='1'>
+ <thead>
+ <row>
+ <entry>Images/</entry>
+ <entry>Models/</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><filename>160x600-final.png</filename>, <filename>160x600-final.jpg</filename></entry>
+ <entry><filename>160x600-final.svgz</filename>,
+ <filename>160x600-final.xcf</filename></entry>
+ <entry>Graphic design at 160x600 pixels, used to
+ produce the left-side bar of <quote>Firstboot</quote>
+ theme component.</entry>
+ </row>
+ <row>
+ <entry><filename>200x150-final.png</filename>, <filename>200x150-final.jpg</filename></entry>
+ <entry><filename>200x150-final.svgz</filename>, <filename>200x150-final.xcf</filename></entry>
+ <entry>Graphic design at 200x150 pixels, used to produce
+ the screenshot of both
+ <quote>Gdm</quote> and <quote>Kdm</quote> theme
+ components.
+ </entry>
+ </row>
+ <row>
+ <entry><filename>400x300-final.png</filename>, <filename>400x300-final.jpg</filename></entry>
+ <entry><filename>400x300-final.svgz</filename>, <filename>400x300-final.xcf</filename></entry>
+ <entry>Graphic design at 400x300 pixels, used to
+ produce the splash component of both
+ <quote>Gnome</quote> and <quote>Kde</quote> theme
+ components.</entry>
+ </row>
+ <row>
+ <entry><filename>490x200-final.png</filename>, <filename>490x200-final.jpg</filename></entry>
+ <entry><filename>490x200-final.svgz</filename>, <filename>490x200-final.xcf</filename></entry>
+ <entry>Graphic design at 490x200 pixels, used to
+ produce the splash image of <quote>Anaconda</quote>
+ theme component.</entry>
+ </row>
+ <row>
+ <entry><filename>510x300-final.png</filename>, <filename>510x300-final.jpg</filename></entry>
+ <entry><filename>510x300-final.svgz</filename>, <filename>510x300-final.xcf</filename></entry>
+ <entry>Graphic design at 510x300 pixels, used to
+ produce the slide images of <quote>Anaconda</quote> theme component.</entry>
+ </row>
+ <row>
+ <entry><filename>640x300-final.png</filename>, <filename>640x300-final.jpg</filename></entry>
+ <entry><filename>640x300-final.svgz</filename>, <filename>640x300-final.xcf</filename></entry>
+ <entry>Graphic design at 640x300 pixels, used to
+ produce the splash image of <quote>Syslinux</quote>
+ theme component.</entry>
+ </row>
+ <row>
+ <entry><filename>640x480-final.png</filename>, <filename>640x480-final.jpg</filename></entry>
+ <entry><filename>640x480-final.svgz</filename>, <filename>640x480-final.xcf</filename></entry>
+ <entry>Graphic design at 640x480 pixels, used to
+ produce the splash image of <quote>Grub</quote> theme
+ component.</entry>
+ </row>
+ <row>
+ <entry><filename>744x1052-final.png</filename>, <filename>744x1052-final.jpg</filename></entry>
+ <entry><filename>744x1052-final.svgz</filename>, <filename>744x1052-final.xcf</filename></entry>
+ <entry>Graphic design at 744x1052 pixels, used to
+ produce the <quote>Posters</quote> theme components.</entry>
+ </row>
+ <row>
+ <entry><filename>800x600-final.png</filename>, <filename>800x600-final.jpg</filename></entry>
+ <entry><filename>800x600-final.svgz</filename>, <filename>800x600-final.xcf</filename></entry>
+ <entry>Graphic design at 800x600 pixels, used to
+ produce the <quote>Concept</quote> theme component.</entry>
+ </row>
+ <row>
+ <entry><filename>800x88-final.png</filename>, <filename>800x88-final.jpg</filename></entry>
+ <entry><filename>800x88-final.svgz</filename>, <filename>800x88-final.xcf</filename></entry>
+ <entry>Graphic design at 800x88 pixels, used to
+ produce the heading image of <quote>Anaconda</quote>
+ theme component.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <para>
+ Besides background files described in <xref
+ linkend="repo-convs-directories-tb1" />, you'll also find
+ background files for specific screen resolutions. The
+ number of files you find here may vary depending the
+ screen resolutions demanded by &TCD; at <filename
+ class="directory">/usr/share/backgrounds/</filename>.
+ Resolution-specific background files follow the same name
+ convention described in the table above but change the
+ resolution numbers to show the screen resolution they
+ represent (e.g., <filename>1360x768-final.png</filename>
+ for 1360x768 screen resolutions.).
+ </para>
+ <para>
+ The word <quote>-final</quote> is used on background files
+ to mark them as ready for applying. When you design
+ background images, you might need to create intermediate
+ images so as to reach desired effects by combining them
+ into a final one. Such intermediate images do not use the
+ word <quote>-final</quote>. Only the result of all your
+ combinations and tests must have the word
+ <quote>-final</quote> on its name.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Backgrounds/Images/</filename></term>
+ <listitem>
+ <para>
+ This directory contains theme-specific background images,
+ mostly in PNG and JPG formats. The files in this
+ directory are used by <command>centos-art.sh</command>
+ script to produce theme components. The relation between
+ image files and theme component is described in <xref
+ linkend="repo-convs-directories-tb1" />.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Backgrounds/Models/</filename></term>
+ <listitem>
+ <para>
+ This directory contains theme-specific background design
+ models, mostly in SVGZ and XCF formats. The files in this
+ directory are used to produce theme-specific background
+ images, only.
+ </para>
+ <para>
+ Design models in this directory must not be confused with
+ design models stored in <filename
+ class="directory">Artworks/Models/Theme/</filename>
+ directory. Design models stored in this directory are
+ theme-specific while design models stored in <filename
+ class="directory">Artworks/Models/Theme/</filename> are
+ common to all themes.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Concept/</filename></term>
+ <listitem>
+ <para>
+ This directory contains theme-specific conceptual ideas.
+ The images in this directory can be used to present the
+ theme's artistic motif in the community. These images
+ include can include theme name, theme version, theme
+ author, theme license, theme copyright and similar
+ information.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Distro/</filename></term>
+ <listitem>
+ <para>
+ This directory contains theme-specific images for each
+ component of &TCD;. In this location, images are organized
+ in distribution major release, distribution component and
+ language, if the current locale is different from English
+ language.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Gradients/</filename></term>
+ <listitem>
+ <para>
+ This directory contains theme-specific GIMP gradients.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Palettes/</filename></term>
+ <listitem>
+ <para>
+ This directory contains theme-specific GIMP palettes.
+ The centos-art.sh script uses theme-specific palettes to produce indexed
+ images with reduced number of colors used by specific
+ theme components, like <quote>Syslinux</quote> and
+ <quote>Grub</quote>. These components have specific color
+ requirements which we must comply with.
+ </para>
+
+ <para>
+ <xref linkend="repo-convs-directories-tb2" />, describes
+ the palettes files used inside themes and the number of
+ colors they require.
+ </para>
+
+ <table id="repo-convs-directories-tb2">
+ <title>Theme-specific palette files</title>
+ <tgroup cols='2' align='left' colsep='1' rowsep='1'>
+ <thead>
+ <row>
+ <entry>File</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry><filename>syslinux.gpl</filename></entry>
+ <entry>
+ This palette is used to produce Syslinux final image.
+ This palette must be created to hold 16 colors using GIMP's
+ palette format. Inside the palette file, the color
+ information is organized in an index that begins at 0
+ and ends at 15. In this index, the color information
+ set at position 0 must be the background color used in
+ the image (e.g., the darkest color in the list) and
+ the color information set at position 7 must be the
+ foreground color used in the image (e.g., the lightest
+ color in the list).
+ </entry>
+ </row>
+ <row>
+ <entry><filename>grub.gpl</filename></entry>
+ <entry>This palette is used to produce Grub final image.
+ This palette must be created to hold 14 colors using
+ GIMP's palette format. Inside the palette file, color
+ information can be set in any order.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <tip>
+ <para>
+ To produce optimum palettes of colors, open with GIMP the
+ full-colored PNG image you need to reduce colors to and
+ reduce colors using GIMP's indexing tool at
+ <guimenuitem>Mode</guimenuitem> →
+ <guimenuitem>Indexed...</guimenuitem> from
+ <guimenu>Image</guimenu> menu. Later, you import the set
+ of colors into a new palette using the GIMP palettes
+ editor and save it here. This way, you can grantee
+ <command>centos-art.sh</command> script will use the
+ correct color information when it produces images with
+ reduced colors for theme-specific components.
+ </para>
+ </tip>
+
+ <caution>
+ <para>
+ When you create theme-specific palettes, it is necessary
+ that you fill the comment field of palette file using the
+ related color information in hexadecimal format.
+ Otherwise, centos-art.sh script won't be able to realize
+ image conversion from PNG to LSS format.
+ </para>
+ </caution>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Patterns/</filename></term>
+ <listitem>
+ <para>
+ This directory contains theme-specific GIMP patterns.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Screenshots/</filename></term>
+ <listitem>
+ <para>
+ This directory contains theme-specific screenshots. It is
+ a series of images illustrating the theme already in
+ place. Here you'll find one screenshot for each relevant
+ component inside &TCD;.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Models/</filename></term>
+ <listitem>
+ <para>
+ This directory contains design models (e.g., scalable vector
+ graphics using the <filename
+ class="extension">.svgz</filename> extension) and image
+ configuration files (e.g., plain text using the <filename
+ class="extension">.conf</filename> extension) used by
+ <command>centos-art.sh</command> script to produce images
+ inside <filename
+ class="directory">Artworks/Images/</filename>. Relevant
+ components inside this directory include Brands, Icons, Themes
+ and Webenv.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Models/Brands/</filename></term>
+ <listitem>
+ <para>
+ This directory organizes branding information for &TCP;.
+ Relevant components inside this directory include Logos/,
+ Symbols/, and Types/ directories. If you need to tune up &TCP;
+ branding information, this is the directory you need to go to.
+ To know more about &TCB;, see <xref linkend="identity-brand" />.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Models/Icons/</filename></term>
+ <listitem>
+ <para>
+ This directory organizes icon design models for &TCP;. By
+ default, &TCD; uses the same icons set packaged inside the
+ SRPMs the upstream provider makes available. Only icons related
+ to branding information are changed in order to identify
+ &TCP; and comply with upstream redistribution guidelines. This
+ directory is not very used by now, it presently contains
+ design models for Tango's icons set.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Models/Themes/</filename></term>
+ <listitem>
+ <para>
+ This directory contains design models organized by categories.
+ When you are producing theme-specific images, you can use the
+ option <option>--theme-model</option> to instruct the
+ <command>centos-art.sh</command> script what of these
+ categories you want to use as reference to produce
+ theme-specific images.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Models/Themes/Default/</filename></term>
+ <listitem>
+ <para>
+ This directory contains default design models used to produce
+ theme-specific images, when the
+ <option>--theme-option</option> is not provided to
+ <command>centos-art.sh</command> script at theme-specific
+ images rendition time. This directory is also used as
+ reference by <command>centos-art.sh</command> script to build
+ the theme-specific directory structures inside <filename
+ class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/</filename>
+ directory, when the <xref linkend="scripts-bash-prepare" />
+ functionality is executed. So, if you find that some
+ directories in this location are empty, don't remove them.
+ They should be present in order for
+ <command>centos-art.sh</command> script to prepare
+ theme-specific directory structures correctly.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Models/Themes/Default/Concept/</filename></term>
+ <listitem>
+ <para>
+ This directory contains design models used to produce the
+ conceptual presentation of each theme. This is a 800x600px
+ image that illustrate the background artistic motif along the
+ license and copyright information. All images produced from
+ this design model use the CC-SA license and &TCP; as copyright
+ holder.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Models/Themes/Default/Distro/</filename></term>
+ <listitem>
+ <para>
+ This directory contains design models used to produce the
+ visual style of each component inside &TCD; for all its major
+ releases. The first sub-directory level under this directory
+ will contain the major release which components will be
+ produced for. Inside the release-specific directory you will
+ find one directory for each related distribution component,
+ including <application>Grub</application>,
+ <application>Anaconda</application>,
+ <application>Gdm</application>,
+ <application>Syslinux</application>,
+ <application>Firstboot</application> and others.
+ </para>
+
+ <para>
+ The components you find inside &TCD; may vary from one major
+ release to another. They might be added or removed as required
+ in each new major release. Thus, it is very important to keep
+ the relation between components and major releases accurate
+ inside this directory.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Models/Themes/Default/Media/</filename></term>
+ <listitem>
+ <para>
+ This directory contains design models used to produce visual
+ style for installation media, including CDs, DVDs, LiveCDs and
+ LiveDVDs. We don't use release-specific directories in this
+ location because it is determined automatically from the
+ <filename>/etc/redhat-release</filename> file or the
+ <option>--releasever</option> option through the command-line
+ of <command>centos-art.sh</command> script.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Models/Themes/Default/Palettes/</filename></term>
+ <listitem>
+ <para>
+ This directory contains the palettes of colors used by
+ <command>centos-art.sh</command> script when no one is found
+ inside <filename
+ class="directory">Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Palettes/</filename>
+ directory.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Models/Themes/Default/Gradients/</filename></term>
+ <listitem>
+ <para>
+ This directory is empty. It is used to build theme-specific
+ directory structures. Don't remove it.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Models/Themes/Default/Patterns/</filename></term>
+ <listitem>
+ <para>
+ This directory is empty. It is used to build theme-specific
+ directory structures. Don't remove it.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Models/Themes/Default/Posters/</filename></term>
+ <listitem>
+ <para>
+ This directory contains design models used by
+ <command>centos-art.sh</command> script to produce posters.
+ Posters are promotional stuff, generally printed in different
+ media and sizes to be shown on events.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Models/Webenv/</filename></term>
+ <listitem>
+ <para>
+ This directory contains common design models used by &TCWE;.
+ These images include, admonition icons, heading backgrounds,
+ html backgrounds, admonition backgrounds and whatever
+ graphical information &TCWE; could need.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Palettes/</filename></term>
+ <listitem>
+ <para>
+ This directory contains GIMP palettes that you always want to
+ have available in GIMP sessions.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Patterns/</filename></term>
+ <listitem>
+ <para>
+ This directory contains GIMP patterns that you always want to
+ have available in GIMP sessions.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Artworks/Webenv/</filename></term>
+ <listitem>
+ <para>
+ This directory contains customizations for specific web
+ applications. The kind of files you find here vary from one
+ web application to another. Generally, you find <filename
+ class="extension">.css</filename> and <filename
+ class="extension">.html</filename> files here. Relevant
+ components inside this directory include Docbook, Httpd,
+ Mantis, Moin, PhpBB, Punbb, Puntal, Style-guide, Texi2html and
+ Trac.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </section>
+
+ <section id="repo-convs-directories-documentation">
+ <title>The <filename class="directory">Documentation</filename> Directory</title>
+ <para>
+ This directory contains documentation related to &TCAR;
+ written in different formats. This directory is organized in
+ Models and Manuals. Models contain the documentation source
+ files and Manuals the final documentation ready to be read
+ through different media (e.g., online and paper). Here, the
+ language used to write documentation manuals is English.
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><filename class="directory">Documentation/Models/</filename></term>
+ <listitem>
+ <para>
+ This directory contains documentation source formats used
+ inside &TCAR;.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Documentation/Models/${MANUAL_FORMAT}/</filename></term>
+ <listitem>
+ <para>
+ This directory contains documentation manuals' name for
+ specific documentation formats.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Documentation/Models/${MANUAL_FORMAT}/${MANUAL_NAME}/</filename></term>
+ <listitem>
+ <para>
+ This directory contains the documentation manual directory
+ structure. Here is where source files are stored in. If you
+ want to modify content from a documentation manual, this is
+ the directory level you need to go to.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename class="directory">Documentation/Manuals/</filename></term>
+ <listitem>
+ <para>
+ This directory organizes documentation final files, organized
+ by documentation format, documentation manual name and
+ documentation language, if documentation files were produced
+ to a language different from English.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+
+ <para>
+ Several documentation formats have been used to write &TCAR;
+ documentation manuals through time, including
+ <application>Texinfo</application>,
+ <application>LaTeX</application> and finally
+ <application>DocBook</application>. From these documentation
+ formats, DocBook is addressed to be the one adopted in the
+ near future as default documentation format inside &TCAR;.
+ Support for other documentation formats will remain inside
+ <command>centos-art.sh</command> script without further
+ improvements. This in order to dedicate more attention to
+ DocBook documentation format.
+ </para>
+
+ <para>
+ The directory structure used by each documentation format is
+ not described in this section. To know more about
+ documentation formats and the directory structure used by
+ documentation manuals, read <xref linkend="manuals-formats"
+ />.
+ </para>
+
+ </section>
+
+ <section id="repo-convs-directories-localization">
+ <title>The <filename class="directory">Localization</filename> Directory</title>
+ <para>
+ ...
+ </para>
+ </section>
+
+ <section id="repo-convs-directories-automation">
+ <title>The <filename class="directory">Automation</filename> Directory</title>
+ <para>
+ ...
+ </para>
+ </section>
+
+ <section id="repo-convs-directories-packages">
+ <title>The <filename class="directory">Packages</filename> Directory</title>
+ <para>
+ ...
+ </para>
+ </section>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/extending.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/extending.docbook
new file mode 100755
index 0000000..a270e5a
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/extending.docbook
@@ -0,0 +1,44 @@
+<section id="repo-convs-extending">
+
+ <title>Extending Repository Layout</title>
+
+ <para>
+ Occasionly, you may find that new components of &TCPCVI; 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 starting to create directories blindly all over, is:
+ <emphasis>What is the right place to store it?</emphasis>
+ </para>
+
+ <para>
+ To build a directory structure inside the repository you need
+ to define the concept behind it first. Later you need to
+ create a new directory inside the repository, remembering that
+ there are locations inside the repository that already define
+ concepts you probably would prefer to reuse. For example, the
+ <filename
+ class="directory">Identity/Images/Themes</filename>
+ directory stores artistic motifs of different themes, the
+ <filename
+ class="directory">Identity/Models/Themes</filename>
+ directory stores design models for themes, the <filename
+ class="directory">Manuals</filename> directory stores
+ documentation, the <filename
+ class="directory">Locales</filename> stores translation
+ messages, and the <filename
+ class="directory">Scripts</filename> stores automation
+ scripts.
+ </para>
+
+ <para>
+ The best suggestion we can probably give you would be to send
+ a mail with your questions to the <ulink
+ url="mailto:centos-devel@centos.org">CentOS developers mailing
+ list</ulink> (<ulink
+ url="mailto:centos-devel@centos.org">centos-devel@centos.org</ulink>).
+ This is the place where development of &TCAR; takes place and
+ surely, in community, it will be possible to find a place for
+ your new component inside the repository.
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/filenames.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/filenames.docbook
new file mode 100755
index 0000000..c43fada
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/filenames.docbook
@@ -0,0 +1,185 @@
+<section id="repo-convs-filenames">
+
+ <title>Repository File Names</title>
+
+ <section id="repo-convs-filenames-rfiles">
+ <title>Regular Files</title>
+
+ <para>
+ Inside &TCAR;, file names are always written in lowercase.
+ Digits (e.g., 0, 1, 2), hyphen (<code>-</code>), dot
+ (<code>.</code>) and low line (<code>_</code>)
+ characters are also accepted. In case you use hyphen and dot
+ characters, don't use them as first character in the file
+ name.
+ </para>
+
+ <section id="repo-convs-filenames-rfiles-ok">
+ <title>Files Written Correctly</title>
+ <para>
+ The following file names are written correctly:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>01-welcome.png</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>splash.png</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>anaconda_header.png</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="repo-convs-filenames-rfiles-wrong">
+ <title>Files Written Incorrectly</title>
+ <para>
+ The following file names are written incorrectly:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>01-Welcome.png</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>-welcome.png</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>Splash.png</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>AnacondaHeader.png</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="repo-convs-filenames-rfiles-exceptions">
+ <title>Exceptions</title>
+ <para>
+ When you name files, consider the following exceptions:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ In the very specific case of repository documentation entries
+ written in Texinfo format, file names follow the directory
+ structure naming convenction. This is because they are
+ documenting directories and that is something
+ we want to remark. So, to better describe what we are
+ documenting, files related to documentation entries follow the
+ name convenction used by the item they document.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+
+ </section>
+
+ <section id="repo-convs-filenames-hfiles">
+ <title>Symbolic Links</title>
+ <para>
+ Inside &TCAR;, symbolic link names follow the same
+ convenctions described in <xref
+ linkend="repo-convs-filenames-rfiles"/>.
+ </para>
+ </section>
+
+ <section id="repo-convs-filenames-dfiles">
+ <title>Directories</title>
+ <para>
+ Inside &TCAR;, directory names are all written capitalized and
+ sometimes in cammel case. Digits (e.g., 0, 1, 2), hyphen
+ (<code>-</code>), dot (<code>.</code>) and low line
+ (<code>_</code>) characters are also accepted. In case you
+ use hyphen and dot characters, don't use them as first
+ character in the directory name.
+ </para>
+
+ <section id="repo-convs-filenames-dfiles-ok">
+ <title>Directories Written Correctly</title>
+ <para>
+ The following directory names are written correctly:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename class="directory">Identity</filename>,
+ <filename class="directory">Themes</filename>,
+ <filename class="directory">Motifs</filename>,
+ <filename class="directory">TreeFlower</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename class="directory">Tcar-ug</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename class="directory">0.0.1</filename>, <filename
+ class="directory">0.0.1-35</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="repo-convs-filenames-dfiles-wrong">
+ <title>Directories Written Incorrectly</title>
+ <para>
+ The following directory names are written incorrectly:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename class="directory">identitY</filename>,
+ <filename class="directory">theMes</filename>,
+ <filename class="directory">MOTIFS</filename>,
+ <filename class="directory">treeFlower</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename class="directory">tcar-ug</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename class="directory">.0.1</filename>, <filename
+ class="directory">.0.1-35</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="repo-convs-filenames-dfiles-exceptions">
+ <title>Exceptions</title>
+ <para>
+ When you name directories, consider the following exceptions:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ No one so far.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ </section>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/infra.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/infra.docbook
new file mode 100755
index 0000000..69f49ba
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/infra.docbook
@@ -0,0 +1,142 @@
+<section id="repo-convs-infra">
+
+ <title>Repository Infrastructure</title>
+
+ <para>
+ &TCAR; is made of one <quote>central repository</quote> and
+ many <quote>working copies</quote> of that central repository.
+ The working copies are independent one another, can be
+ distributed all around the world and provide a local place for
+ designers, documenters, translators and programmers to perform
+ their work in a decentralized way. The central repository, on
+ the other hand, provides a common place for all independent
+ working copies to exchange data in the community.
+ </para>
+
+ <figure id="repo-convs-infra-1">
+ <title>Repository infrastructure</title>
+ <screenshot>
+ <screeninfo>Repository infrastructure</screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="=TCAR_WORKDIR=/Documentation/Manuals/Svg/Repository/infrastructure.png" format="PNG" />
+ </imageobject>
+ </mediaobject>
+ </screenshot>
+ </figure>
+
+ <section id="repo-convs-infra-subversion">
+ <title>Subversion</title>
+
+ <para>
+ The current infrastructure that holds &TCAR;, on the Internet,
+ is made of the following components:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <application><ulink
+ url="http://subversion.tigris.org/">Subversion</ulink></application>
+ — Modern Version Control System designed to replace CVS.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <application><ulink
+ url="http://trac.edgewall.org/">Trac</ulink></application>
+ — Enhanced wiki and issue tracking system.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <application>Httpd+WebDav</application> as data exchanging route between the workstations
+ and the central repository, through the Internet. Httpd was
+ configured to provide service through SSL, so all traffic
+ between the workstations and the server be protected while it
+ travels across the Internet. </para>
+ </listitem>
+ <listitem>
+ <para>
+ The access rights are controlled by using a combination of both
+ Subversion's authorization files and Httpd's password files.
+ These files can be managed consistently through Trac's WebAdmin
+ plug-in.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ In this infrastructure, the first level of directories in the
+ repository provides the Subversion's standard
+ trunk-branches-tags layout. The second level of directories
+ provides organization for different work lines, as described
+ in <xref linkend="repo-convs-worklines" />. All other
+ subsequent directory levels from second level on exist to
+ organize specific concepts related to the work line they
+ belong to.
+ </para>
+
+ </section>
+
+ <section id="repo-convs-infra-git">
+ <title>Git</title>
+
+ <para>
+ In addition to current Subversion infrastructure, we are
+ working on a Git infrastructure with the intention of
+ migrating the current Subversion infrastructure up to it,
+ progressively. The Git infrastructure we are working on is
+ made of the following components:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Git — Fast version control system.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <application>Gitolite</application> — Highly flexible
+ server for git directory version tracker.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <application>Gitweb</application> — Simple web interface
+ to git repositories.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <application>MantisBT</application> — Web-based issue
+ tracking system.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The data exchanging route between the working copies and the
+ central repository takes place through SSH.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The access rights are controlled by using a combination of SSH
+ public keys and Gitolite's repository configuration file.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ In this infrastructure, the first level of directories in the
+ repository provides organization for different work lines, as
+ described in <xref linkend="repo-convs-worklines" />. All
+ other subsequent directory levels from second level on exist
+ to organize specific concepts related to the work line they
+ belong to.
+ </para>
+
+ </section>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/mission.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/mission.docbook
new file mode 100755
index 0000000..32c6a9d
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/mission.docbook
@@ -0,0 +1,9 @@
+<section id="repo-convs-mission">
+
+ <title>Repository Mission</title>
+
+ <para>
+ &TCAR; exists to produce &TCP; corporate visual identity.
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/publishing.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/publishing.docbook
new file mode 100755
index 0000000..71bcd14
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/publishing.docbook
@@ -0,0 +1,59 @@
+<section id="repo-convs-publishing">
+
+ <title>Repository Publishing</title>
+
+ <para>
+ When you perform changes inside your working copy, those
+ changes are local to your working copy only. In order for you
+ to share your changes with others, you need to commit them up
+ to the central repository the working copy you are using was
+ initially downloaded from. To commit your changes up to the
+ central repository you use the <command>commit</command>
+ command from the Subversion's client you've installed in your
+ workstation.
+ </para>
+
+ <para>
+ Initially, when you get registered inside &TCAR;, you won't be
+ able to publish your changes to &TCAR; immediatly. It is
+ necessary that you prove your interest in contributing first
+ sending a mail to the <ulink
+ url="http://lists.centos.org/mailman/listinfo/centos-devel">CentOS
+ Developers mailing list</ulink> (<ulink
+ url="mailto:centos-devel@centos.org">centos-devel@centos.org</ulink>),
+ preferably in conjunction with a description of the changes
+ you pretend to commit. This restriction is necessary in order
+ to protect the source repository from spammers.
+ </para>
+
+ <para>
+ Once you've received access to publish your changes, they will
+ remain valid to you and there is no need for you to request
+ permission to publish new changes as long as you behave as a
+ good cooperating citizen.
+ </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. As complement, 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 that everything goes the way it needs
+ to go in order for &TCAR; to accomplish its mission (see <xref
+ linkend="repo-convs-mission" />).
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/relbdirs.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/relbdirs.docbook
new file mode 100755
index 0000000..835f241
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/relbdirs.docbook
@@ -0,0 +1,157 @@
+<section id="repo-convs-relbdirs">
+
+ <title>Repository Path Relations</title>
+
+ <para>
+ In order for automation scripts to produce content inside a
+ working copy of &TCAR;, it is required that all work lines be
+ related somehow. The automation scripts take the relation
+ between work lines as reference to determine the place the
+ information they will work with will be retrieve from (e.g.,
+ scalable vector graphics, documentation, translations, etc.),
+ as well as the place where it will store the final files
+ produced as result of automation process (e.g., portable
+ network graphics, documentation ready for printing and reading
+ online, etc.).
+ </para>
+ <para>
+ In order to implement the relation between work lines it is
+ required to establish a path name convenction, so we can
+ conceptually organize different components and relate them one
+ another using predictable path constructions in a scalable
+ way. Based on this need, we identify three different path
+ types inside &TCAR;. These path types are: <emphasis>Output
+ Paths</emphasis>, <emphasis>Input Paths</emphasis>, and
+ <emphasis>Auxiliary Paths</emphasis>.
+ </para>
+
+ <section id="repo-convs-relbdirs-renderable">
+ <title>Output Paths</title>
+
+ <para>
+ The output paths point to directories inside the working copy
+ which contain files produced from files inside the input
+ paths. For example, the following paths are consider as output
+ paths:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename class="directory">Identity/Images/Brands/</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename class="directory">Documentation/Manuals/Tcar-ug/</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename class="directory">Identity/Images/Themes/Modern/2/Distro/5/Anaconda/</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ Output paths are also known as <emphasis><quote>Render-able
+ Directories</quote></emphasis> because they are the type of
+ path you should provide as argument to <xref
+ linkend="scripts-bash-render" /> functionality so as to
+ produce content through it.
+ </para>
+
+ </section>
+
+ <section id="repo-convs-relbdirs-designmodels">
+ <title>Input Paths</title>
+ <para>
+ The input paths point to a directories inside the working copy
+ which contain files used to produce files inside output paths.
+ For example, the following paths are considered as input
+ paths:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename class="directory">Identity/Models/Brands/</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename class="directory">Documentation/Models/Tcar-ug/</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename class="directory">Identity/Models/Themes/Default/Distro/5/Anaconda/</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="repo-convs-relbdirs-auxiliar">
+ <title>Auxiliary Paths</title>
+
+ <para>
+ The auxiliary paths point to directories inside the working
+ copy which contain files used to create modified instances of
+ inside input paths which are use in turn to produce files
+ inside output paths. For example, the following paths are
+ considered as auxiliary paths:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename class="directory">Identity/Images/Brands/</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename class="directory">Locales/Documentation/Models/Docbook/Tcar-ug/es_ES/</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename class="directory">Locales/Identity/Models/Themes/Default/Distro/5/Anaconda/es_ES/</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The relationship between input, output and auxiliary paths is
+ created by combining the first directory level of input paths
+ with the first directory level in the repository directory
+ layout. In the repository directory layout, the first level
+ includes the <filename class="directory">Identity</filename>,
+ <filename class="directory">Documentation</filename> and
+ <filename class="directory">Scripts</filename> directories.
+ These directories are always used to create input and output
+ paths. The <filename class="directory">Locales</filename>
+ directory, on the other hand, is always used to create
+ auxiliary paths only for input paths available under <filename
+ class="directory">Identity</filename>, <filename
+ class="directory">Documentation</filename> and <filename
+ class="directory">Scripts</filename> directories.
+ </para>
+
+ <para>
+ For example, if the <varname>LANG</varname> environment
+ variable is set to <quote>es_ES.UTF-8</quote> and you execute
+ the <xref linkend="scripts-bash-render"/> functionality of
+ <command>centos-art.sh</command> script with the <filename
+ class="directory">Documentation/Manuals/Docbook/Tcar-ug/</filename>
+ input path as argument, it will produce &TCARUG; in Spanish
+ language using translation messages from
+ <filename>Locales/Documentation/Models/Docbook/Tcar-ug/es_ES/</filename>
+ auxiliary path and would save final documentation files under
+ <filename
+ class="directory">Documentation/Manuals/Docbook/Tcar-ug/es_ES/</filename>
+ output path.
+ </para>
+
+ </section>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/syncpaths.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/syncpaths.docbook
new file mode 100755
index 0000000..d8e353d
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/syncpaths.docbook
@@ -0,0 +1,99 @@
+<section id="repo-convs-syncpaths">
+
+ <title>Syncronizing Repository Paths</title>
+
+ <para>
+ Once both master and auxiliar paths have been related in the
+ repository, they shouldn't be changed except you absolutly
+ need to do so. In this cases, when you need to change master
+ or auxiliar paths, it is required that you also change the
+ relation between them so as to retain their bond. This
+ process of keeping master and auxiliar paths
+ <quote>connected</quote> between themselves is known as
+ <emphasis>path syncronization</emphasis>.
+ </para>
+
+ <para>
+ Path syncronization is required for automation scripts to know
+ where to store final output, where to retrive translation
+ messages from, and whatever information you might need to
+ count with. If the 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 to work with or
+ where to store the output information produced from it.
+ Through path syncronization we organize and extend the content
+ production inside the repository.
+ </para>
+
+ <para>
+ Path syncronization affects both movement of files and
+ replacement of content inside files. Movement of files is
+ related to actions like renaming files and directories inside
+ the repository. Replacement of content inside files is
+ related to actions like replacing information (e.g., paths
+ information) inside files in order to keep file contents and
+ file locations consistent one another after a file has been
+ moved.
+ </para>
+
+ <para>
+ The order followed to syncronize path information is very
+ important because the versioned nature of the files we are
+ working with. When a renaming action needs to be performed
+ inside the repository, we avoid making replacements inside
+ files first and file movements later. This would demand two
+ commit actions: one for the files' internal changes and
+ another for the file movement itself. Instead, we prefer to
+ perform file movements first and files' internal replacements
+ later. This way it is possible to commit both changes as if
+ they were just one.
+ </para>
+
+ <note>
+ <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's commands
+ instead.
+ </para>
+ </note>
+
+ <para>
+ At this moment there isn't full implementation of path
+ syncronization inside <command>centos-art.sh</command> script
+ and that is somthing we need to do oursleves. However, the
+ <quote>texinfo</quote> backend inside the
+ <function>help</function> functionality does provide a restricted
+ implementation of path syncronization to documentation area
+ through the <option>--copy</option>, <option>--delete</option>
+ and <option>--rename</option> options. You can read this
+ implementation and use it as reference to implement path
+ syncronization in other areas.
+ </para>
+
+ <para>
+ The plan for a full implementation of path syncronization
+ inside <command>centos-art.sh</command> script would be to
+ create individual restricted implementations like the one in
+ <quote>texinfo</quote> backend for other areas that demand it
+ and then, create a higher implmentation that combines them all
+ as needed. This way, if we try to rename a repository
+ directory, the higher action can know which are all the
+ restricted actions that should be performed in order
+ to make the full path syncronization.
+ </para>
+
+ <para>
+ For example, if the directory we are renaming is a master
+ path, it is required to syncronize the related output and
+ localization auxiliar paths. On the other hand, if the
+ directory we are renaming through full path syncronization is
+ an auxiliar path, it is required to determine first what is
+ the related master path and later, perform the syncronization
+ from master path to auxiliar paths as if the path provided
+ would be the master path not the auxiliar path.
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/worklines.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/worklines.docbook
new file mode 100755
index 0000000..f31dd87
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Conventions/worklines.docbook
@@ -0,0 +1,186 @@
+<section id="repo-convs-worklines">
+
+ <title>Repository Work Lines</title>
+
+ <para>
+ The content production inside &TCAR; has been divided into
+ individual work lines that relate one another based on the
+ idea of doing one thing well. In this model, the content
+ produced individually by each work line is combined one
+ another later to achieve higher purposes (e.g., corporate
+ identity for &TCP;). The repository work lines, as conceived
+ here, provide a reliable environment for people to work
+ synchronized and decentralized.
+ </para>
+
+ <para>
+ The action of combining work lines inside &TCAR; is also known
+ as the <quote>Production Cycle</quote> of CentOS corporate
+ visual identity. The rest of this section describes the work
+ lines available in the repository and how they integrate one
+ another.
+ </para>
+
+ <section id="repo-convs-worklines-artworks">
+
+ <title>Artworks</title>
+
+ <para>
+ <emphasis>Artworks</emphasis> is the first component we work
+ out in order to produce new corporate visual identities.
+ Through this work line, graphic designers create
+ <quote>models</quote> and <quote>motifs</quote> for all the
+ visual manifestation &TCP; is made of. Once design models and
+ artistic motifs are set in place, graphic designers use the
+ <xref linkend="scripts-bash-render" /> functionality to
+ combine them into final images.
+ </para>
+
+ <para>
+ The mission of <emphasis>Artworks</emphasis> work line is
+ define all the visual manifestations the &TCP; is made of and
+ provide design models and artistic motifs for them in order to
+ produce the image files required to transmit the visual style
+ that identifies &TCP; as unique organization.
+ </para>
+
+ <para>
+ To know more about &TCPCVI;, read <xref linkend="identity" />.
+ </para>
+
+ </section>
+
+ <section id="repo-convs-worklines-l10n">
+
+ <title>Localization</title>
+
+ <para>
+ <emphasis>Localization</emphasis> is the second component that
+ must be worked out in the production cycle of CentOS corporate
+ visual identity. Through this work line translators localize
+ source files (e.g., SVG, DocBook, Shell scripts) which are
+ later used to produce localized images, localized
+ documentation and localized automation scripts. To localize
+ source files, translators use the <xref
+ linkend="scripts-bash-locale" /> functionality which takes
+ care of retrieving translatable strings from source files and
+ provide a consistent localization interface based on GNU
+ <application>gettext</application> multi-lingual message
+ production tool set and <command>xml2po</command> command.
+ </para>
+
+ <para>
+ The localization process takes place inside the
+ <quote><filename
+ class="directory">Localization/</filename></quote> directory
+ in the first level of each repository directory structure.
+ This directory mirrors the renderable directory structures
+ outside it and stores <filename
+ class="extension">.po</filename> and <filename
+ class="extension">.pot</filename> files mainly.
+ </para>
+
+ <para>
+ The mission of <emphasis>Localization</emphasis> work line is
+ extend the visual identity (produced in English language) to
+ as many native languages as possible, in order for people
+ which doesn't understand English language to feel more
+ comfortable with &TCP; in their own native languages.
+ </para>
+
+ <para>
+ To know more about the specific localization process read
+ <xref linkend="locale" />.
+ </para>
+
+ </section>
+
+ <section id="repo-convs-worklines-manuals">
+
+ <title>Documentation</title>
+
+ <para>
+ The documentation work line is the third component that must
+ be worked out in the corporate identity production cycle.
+ Through this work line documentors settle down the conceptual
+ and practical used to edificate &TCAR;. To write
+ documentation, documentors use the <function>help</function>
+ functionality described in <xref linkend="scripts-bash-help"
+ /> which provides a consistent interface for building
+ documentation through different documentation backends (e.g.,
+ Texinfo, DocBook, LaTeX, etc.).
+ </para>
+
+ <para>
+ The main purpose of this work line is describe the standard
+ procedures &TCAR; realies on, as well as conceive a place to
+ help you understand what &TCAR; is and what can you do with
+ it.
+ </para>
+
+ <para>
+ The documentation work line takes palce in the <ulink
+ url="https://projects.centos.org/~al/artwork.git/Manuals"><filename
+ class="directory">Manuals</filename></ulink> directory.
+ </para>
+
+ </section>
+
+ <section id="repo-convs-worklines-packages">
+ <title>Packages</title>
+
+ <para>
+ The packages work line is the fourth component that must be
+ worked out in the corporate identity production cycle. Through
+ this work line packager gather final images, final
+ translations and final documentation related to art works and
+ put all together inside RPM packages. For this purpose,
+ packagers use the <function>pack</function> describe in
+ <xref linkend="scripts-bash-pack" /> which provides a
+ consistent interface for building packages inside the
+ repository.
+ </para>
+
+ <para>
+ The main purpose of this work line is pack all the information
+ &TCP; requires to rebrand &TCD; according Red Hat
+ redistribution guidelines.
+ </para>
+
+ <para>
+ The packages work line takes palce in the <ulink
+ url="https://projects.centos.org/~al/artwork.git/Packages"><filename
+ class="directory">Packages</filename></ulink> directory.
+ </para>
+
+ </section>
+
+ <section id="repo-convs-worklines-scripts">
+
+ <title>Automation</title>
+
+ <para>
+ The automation work line is the fifth and last component that
+ must be worked out in the corporate identity production cycle.
+ This work line closes the production cycle and provides the
+ production standards graphic designers, documentors,
+ translators and packagers need to make their work consistent
+ and reusable. For this purpose, programmers develop the
+ <command>centos-art.sh</command> script described in <xref
+ linkend="scripts" />.
+ </para>
+
+ <para>
+ The main purpose of this work line is standardize the
+ interaction of work lines in a reliable way.
+ </para>
+
+ <para>
+ The automation work line takes palce in the <ulink
+ url="https://projects.centos.org/~al/artwork.git/Scripts"><filename
+ class="directory">Scripts</filename></ulink> directory.
+ </para>
+
+ </section>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History.docbook
new file mode 100644
index 0000000..ca54c8a
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History.docbook
@@ -0,0 +1,17 @@
+<chapter id="repo-history">
+
+ <title>Repository History</title>
+
+ <para>
+ This chapter summarizes relevant changes committed to &TCAR;
+ along the years.
+ </para>
+
+ &repo-history-2008;
+ &repo-history-2009;
+ &repo-history-2010;
+ &repo-history-2011;
+ &repo-history-2012;
+ &repo-history-2013;
+
+</chapter>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2008.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2008.docbook
new file mode 100644
index 0000000..aff53c8
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2008.docbook
@@ -0,0 +1,67 @@
+<section id="repo-history-2008">
+
+ <title>2008's</title>
+
+ <para>
+ &TCAR; started at <ulink
+ url="mailto:centos-devel@centos.org">The CentOS Developers
+ Mailing List</ulink> around 2008, on a discussion about how to
+ automate slide images used by Anaconda (&TCD; installer). In
+ such discussion, <ulink
+ url="http://wiki.centos.org/RalphAngenendt">Ralph
+ Angenendt</ulink> rose up his hand to ask —Do you have
+ something to show?—.
+ </para>
+
+ <para>
+ To answer the question, <ulink
+ url="http://wiki.centos.org/AlainRegueraDelgado">Alain Reguera
+ Delgado</ulink> suggested a bash script which combined SVG and
+ SED files in order to produce PNG images in different
+ languages —in conjunction with the proposition of
+ creating a Subversion repository where translations and image
+ production could be distributed inside &TCC;—.
+ </para>
+
+ <para>
+ <ulink url="http://wiki.centos.org/KaranbirSingh">Karanbir
+ Singh</ulink> considered the idea intresting and provided the
+ infrastructure necessary to support the effort. This way,
+ &TCAS; and &TCAR; were officially created and made world wide
+ available. In this configuration, users were able to register
+ themselves and administrators were able to assign access
+ rights to registered users inside &TCAR;, both using a web
+ interface.
+ </para>
+
+ <para>
+ Once &TCAR; was available, Alain Reguera Delgado uploaded the
+ bash script used to produce the Anaconda
+ slides;<footnote><para>See <ulink
+ url="https://projects.centos.org/trac/artwork/browser/Main/render.sh?rev=15"
+ /></para></footnote> Ralph Angenendt documented it very
+ well;<footnote><para>See <ulink type="http"
+ url="https://projects.centos.org/trac/artwork/wiki/HowToTranslateSlides"
+ /></para></footnote> and people started to download working
+ copies of &TCAR; to produce slide images in their own
+ languages.<footnote><para>See the following <ulink
+ url="http://www.google.com/search?q=anaconda+slides+site%3Alists.centos.org">Google
+ search</ulink>.</para></footnote>
+ </para>
+
+ <para>
+ From this time on &TCAR; has been evolving into an automated
+ production environment where &TCC; can conceive &TCP;
+ corporate visual identity.
+ </para>
+
+ <para>
+ The exact changes commited to &TCAR; through history can be
+ found in the <ulink
+ url="https://projects.centos.org/trac/artwork/timeline">repository
+ logs</ulink> so you can know the real history about it. For
+ those of you who just want to get a glance of changes
+ committed, see <xref linkend="repo-history" />.
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2009.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2009.docbook
new file mode 100644
index 0000000..725ca9c
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2009.docbook
@@ -0,0 +1,55 @@
+<section>
+
+ <title>2009's</title>
+
+ <para>
+ Around 2009, 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,
+ different from 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 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 art work that needed to be produced. In this
+ configuration, if you would want to produce the same art work
+ 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>
+ Corporate identity concepts began to be considered. As
+ referece, it was used the book "Corporate Identity" by Wally
+ Olins (1989) and <ulink
+ url="http://en.wikipedia.org/Corporate_identity">Wikipedia
+ related links</ulink>. This way, the rendition script main's
+ goal becomes to: <emphasis>automate the production process of
+ a monolithic corporate visual identity structure, based on the
+ mission and the release schema of The CentOS
+ Project</emphasis>.
+ </para>
+
+ <para>
+ The repository directory structures began to be documented by
+ mean of flat text files. Later, documentation in flat text
+ files was moved onto LaTeX format and this way &TCARUG; was
+ initiated.
+ </para>
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2010.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2010.docbook
new file mode 100644
index 0000000..4faacb0
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2010.docbook
@@ -0,0 +1,78 @@
+<section>
+
+ <title>2010's</title>
+
+ <para>
+ Around 2010, 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., documentation and localization).
+ </para>
+
+ <para>
+ The <command>centos-art.sh</command> was initially conceived
+ to automate frequent tasks inside the repository based in the
+ idea of Unix toolbox: to create small and specialized tools
+ that do one thing well. This way, functionalities inside
+ <command>centos-art.sh</command> began to be 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 <quote>common
+ functionalities</quote> and <quote>specific
+ functionalities</quote> 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>
+ Suddenly, no need was found to keep all the links spreaded
+ around the repository in order to execute the
+ <command>centos-art.sh</command> script from different
+ locations. The <command>centos-art</command> command-line
+ interface was used instead. The <command>centos-art</command>
+ command-line interface is a symbolic link stored inside the
+ <filename class="directory">~/bin</filename> directory
+ pointing to <command>centos-art.sh</command> script. As
+ default configuration, inside The CentOS Distribution, the
+ path to <filename class="directory">~/bin</filename> is
+ included in the search path for commands (see
+ <envar>PATH</envar> environment variable). This way, using
+ the <command>centos-art</command> command-line interface, it
+ is possible to execute the <command>centos-art.sh</command>
+ script from virtually anywhere inside the workstation, just as
+ we frequently do with regular commands.
+ </para>
+
+ <para>
+ Start using GNU getopt as default option parser inside the
+ <command>centos-art.sh</command> script.
+ </para>
+
+ <para>
+ The repository directory structure was updated to improve the
+ implementation of corporate visual identity concepts.
+ Specially in the area related to themes. Having both structure
+ and style in the same file introduced content duplication when
+ producing art works. Because of this reason, they were
+ separated into two different directory structures: the design
+ models and the artistic motifs directory structures. From
+ this point on, the <command>centos-art.sh</command> was able
+ to produce themes as result of arbitrary combinations between
+ design models (structure) and artistic motifs (visual styles).
+ </para>
+
+ <para>
+ In the documentation area, the documents 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 and copied)
+ interactively through <command>centos-art.sh</command> script.
+ Additionally, the texi2html program was used to produced
+ customized XHTML output in conjunction with CSS from &TCW;.
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2011.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2011.docbook
new file mode 100644
index 0000000..69f840d
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2011.docbook
@@ -0,0 +1,51 @@
+<section>
+
+ <title>2011's</title>
+
+ <para>
+ Around 2011, the <command>centos-art.sh</command> script was
+ redesigned to start translating XML-based files (e.g., SVG and
+ Docbook files) through <command>xml2po</command> program and
+ shell scripts (e.g., Bash scripts) through GNU gettext tools.
+ This configuration provided a stronger localization interface
+ for graphic designers, translators and programmers. The SED
+ replacement files are no longer used to handle localization.
+ </para>
+
+ <para>
+ The <function>render</function>, <function>help</function> and
+ <function>locale</function> functionalities consolidated
+ themselves as the most frequent tasks performed in &TCAR;
+ working copy. Additionally, the <function>prepare</function>
+ and <function>tuneup</function> functionalities were also
+ maintained as useful tasks.
+ </para>
+
+ <para>
+ In the documentation area, it was introduced the
+ transformation of localized DocBook XML DTD instances through
+ the <function>render</function> and
+ <function>locale</function> functionalities. In this
+ configuration, you use <function>locale</function>
+ functionality to localize DocBook source files to your
+ prefered language and later, using the
+ <function>render</function> functionality, you can produce the
+ localized XTHML and PDF output as specified in a XSLT layer.
+ Unfortunly, the transformation DocBook XML -> FO -> PDF
+ (through PassiveTex) seems to be buggy inside CentOS 5.5, so
+ it was commented inside the <command>centos-art.sh</command>
+ script. Most documentation is now organized in DocBook format,
+ even Texinfo format remains as the only format with automated
+ production tasks.
+ </para>
+
+ <para>
+ In the automation area, the <command>centos-art.sh</command>
+ script introduced the capability of reading configuration
+ files. The main goal here was moving some command-line options
+ from functionalities onto a more persistent medium. Most
+ configuration files were set to define the position of brands
+ inside images and documentation manual specific options.
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2012.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2012.docbook
new file mode 100644
index 0000000..cf81287
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2012.docbook
@@ -0,0 +1,431 @@
+<section id="repository-history-2012">
+
+ <title>2012's</title>
+
+ <para>
+ &TCAR; development was eventually stopped at November 2011
+ until July 2012 when we needed to make the
+ <command>centos-art.sh</command> script a bit more
+ customizable than it presently was. For example, it was
+ considered as a need that functionalities inside the
+ <command>centos-art.sh</command> script must be not just
+ conceived independent one another but reusable in different
+ contexts as well.
+ </para>
+
+ <simplesect id="repository-history-2012-UpdateLocales">
+ <title>Make Localization Of <command>centos-art.sh</command>
+ Script Specific To Different Contexts</title>
+
+ <para>
+ The procedure used to locale messages inside the
+ <command>centos-art.sh</command> script has to be re-designed
+ in order to accept such pluggable behavior into the script. We
+ couldn't publish unique <filename>centos-art.sh.po</filename>
+ and <filename>centos-art.sh.mo</filename> files because they
+ may contain different information in different contexts. For
+ example, if you are using the <function>render</function> and
+ <function>help</function> functionalities you only need
+ translation messages for them and not those from other
+ functionalities that may exist in the central repository but
+ you didn't download nor use into your working copy.
+ </para>
+
+ <para>
+ One solution for this could be to have independent PO files
+ for each functionality of <command>centos-art.sh</command>
+ script which are combined to create the final PO and MO files
+ that <application>gettext</application> uses to retrive
+ translated strings when <command>centos-art.sh</command>
+ script is running. For this solution to be effective, you must
+ be selective about the functionalities and locales directories
+ you download into your working copy. For example, if you want
+ to use the render functionality and its locale messages only,
+ you must download the required directories and exclude others.
+ </para>
+
+ <note>
+ <para>
+ In case you don't want to be selective and download the whole
+ repository, the creation of the
+ <filename>centos-art.sh.po</filename>,
+ <filename>centos-art.sh.pot</filename> and
+ <filename>centos-art.sh.mo</filename> files will occur
+ automatically the first time you run the
+ <function>prepare</function> functionality (which require the
+ <function>locale</function> functionality to be available), or
+ later, by running the following command:
+ <screen>centos-art locale Scripts/Bash --update</screen>
+ </para>
+
+ <para>
+ For more information about the <function>prepare</function>
+ and <function>locale</function> functionalities, see <xref
+ linkend="scripts-bash-locale" /> and <xref
+ linkend="scripts-bash-prepare" /> respectively.
+ </para>
+
+ </note>
+
+ <para>
+ As shown in <xref linkend="repository-history-2012-2" />, both
+ <function>Commons</function> and <function>Locales</function>
+ functionalities will always be required directories. The
+ <function>Commons</function> directory contains the common
+ functionalities and the <function>Locales</function> directory
+ contains the standard procedures you need to run in order to
+ build the final <filename>centos-art.sh.mo</filename> file
+ used by <application>gettext</application> to retrive
+ translation strings when the <command>centos-art.sh</command>
+ script is running. Remember that
+ <filename>centos-art.sh.pot</filename>,
+ <filename>centos-art.sh.po</filename> files aren't under
+ version control and they are built by combining each
+ funtionality message.po file into a PO and later a MO file.
+ </para>
+
+ <example id="repository-history-2012-2">
+ <title>Directory structure of a rendering-only context</title>
+ <screenshot>
+ <screeninfo>Directory structure of a rendering-only context</screeninfo>
+ <mediaobject>
+ <textobject>
+<programlisting>
+/home/centos/Projects/artwork/
+|-- Locales/
+| `-- Scripts/
+| `-- Bash/
+| `-- es_ES/
+| |-- Functions/
+| | |-- Commons/
+| | | |-- messages.po
+| | | `-- messages.pot
+| | |-- Locales/
+| | | |-- messages.po
+| | | `-- messages.pot
+| | `-- Render/
+| | |-- messages.po
+| | `-- messages.pot
+| |-- LC_MESSAGES/
+| | `-- centos-art.sh.mo
+| |-- centos-art.sh.po
+| `-- centos-art.sh.pot
+`-- Scripts/
+ `-- Bash/
+ |-- Functions/
+ | |-- Commons/
+ | |-- Locales/
+ | `-- Render/
+ `-- centos-art.sh
+</programlisting>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </example>
+
+ <para>
+ A practical example of using the solution described above may
+ be found when you are working on the corporate identity of
+ &TCP; and then need to start a new corporate identity project
+ for another organization. You want to keep the directory
+ structure of &TCAR; and its automation tool, the
+ <command>centos-art.sh</command> script. Your new project
+ requires you to introduce new functionalities to
+ <command>centos-art.sh</command> which don't fit the needs of
+ &TCP; (e.g., you want to introduce a
+ <function>report</function> functionality to mesure how much
+ connect time do you consume through your PPP internface.) or
+ you just want to keep the directory structure of your new
+ project as simple as possible.
+ </para>
+
+ <para>
+ To go through this it is possible to mix specific parts of
+ different central repositories into one single working copy.
+ This is the working copy you'll use to manage your new
+ project. In <xref linkend="repository-history-2012-1" />, we
+ see how the <filename class="directory">Render</filename>,
+ <filename class="directory">Locales</filename> and <filename
+ class="directory">Commons</filename> directories which come
+ from the &TCAR; has been integrated into the working copy of
+ your new project.
+ </para>
+
+ <example id="repository-history-2012-1">
+ <title>Mixing automation functionalities.</title>
+ <screenshot>
+ <screeninfo>Mixing automation functionalities.</screeninfo>
+ <mediaobject>
+ <textobject>
+<programlisting>
+/home/al/Projects/Myapp/
+|-- Locales/
+| `-- Scripts/
+| `-- Bash/
+| `-- es_ES/
+| |-- Functions/
+| | |-- Commons/ <--| from https://projects.centos.org/svn/artwork/
+| | | |-- messages.po
+| | | `-- messages.pot
+| | |-- Locales/ <--| from https://projects.centos.org/svn/artwork/
+| | | |-- messages.po
+| | | `-- messages.pot
+| | |-- Render/ <--| from https://projects.centos.org/svn/artwork/
+| | | |-- messages.po
+| | | `-- messages.pot
+| | `-- Report/
+| | |-- messages.po
+| | `-- messages.pot
+| |-- LC_MESSAGES/
+| | `-- myapp.sh.mo
+| |-- myapp.sh.po
+| `-- myapp.sh.pot
+`-- Scripts/
+ `-- Bash/
+ |-- Functions/
+ | |-- Commons/ <--| from https://projects.centos.org/svn/artwork/
+ | |-- Locales/ <--| from https://projects.centos.org/svn/artwork/
+ | |-- Render/ <--| from https://projects.centos.org/svn/artwork/
+ | `-- Report/
+ `-- myapp.sh
+</programlisting>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </example>
+
+ <para>
+ At this point, your working copy contains files from two
+ different central repositories. One repository provides the
+ files of your new organization project and the other one
+ provides the files related to the <function>render</function>
+ functionality from &TCAR;. In this environment, all updates
+ commited to the <filename class="directory">Render</filename>,
+ <filename class="directory">Locales</filename> and <filename
+ class="directory">Commons</filename> directories at &TCAR;
+ will be available to you too, the next time you update your
+ working copy. Likewise, if you change something in any of
+ these directories and commit your changes, your changes will
+ be available to poeple working in &TCAR; the next time they
+ update their working copies.
+ </para>
+
+ <para>
+ Understanding the need of mixing different central
+ repositories into a single working copy is an important step
+ for reusing the functionalities that come with centos-art.sh
+ script, but it is not enough if you want to customize the
+ information produced by it. By default, the centos-art.sh
+ script uses information related to &TCP;. You probably need to
+ change this if you are producing images to a different
+ organization than &TCP;. For example, some of the information
+ you might need to change would be the copyright holder,
+ brands, domain names, mailing lists, and so forth. To change
+ this information you need to duplicate the file
+ <filename>centos-art.sh</filename> and rename it to something
+ else. Later, you need to edit the renamed version and change
+ variables inside according your needs. In <xref
+ linkend="repository-history-2012-1" />, we used the name
+ <command>myapp.sh</command> instead of
+ <command>centos-art.sh</command> so the information we set
+ inside it could reflect the specific needs that motivated the
+ creation of a new project without affecting those from &TCP;.
+ </para>
+
+ <para>
+ Most of the information you need to change in your duplicated
+ version of <filename>centos-art.sh</filename> file is
+ controlled by a set of read-only variables. You modify these
+ variables here and they will be available all along the script
+ execution time. For example, you can change the value of
+ <varname>CLI_WRKCOPY</varname> variable inside your duplicated
+ version of <filename>centos-art.sh</filename> to change the
+ absolute path you use to store your working copy.
+ </para>
+
+ </simplesect>
+
+ <simplesect>
+ <title>Enhance The CentOS Logo Construction</title>
+
+ <para>
+ The CentOS Logo is made of two different components known as
+ The CentOS Symbol and The CentOS Type. Presently (at the end
+ of September), to produce these components, we create one
+ <acronym>SVG</acronym> image for each PNG image we want to
+ produce, store it in <filename
+ class="directory">Identity/Models/Brands/Logos</filename>
+ directory structure and run the command:
+ </para>
+
+ <cmdsynopsis>
+ <command>centos-art render Identity/Images/Brands/Logos</command>
+ </cmdsynopsis>
+
+ <para>
+ This model works and scales well in situations when there
+ isn't a need to reuse final images among themselves. However,
+ when you need to reuse images among themselves, a better
+ solution is required. The goal here would be: don't create
+ <acronym>SVG</acronym> images for PNG images you can build
+ based on other PNG images.
+ </para>
+
+ <para>
+ This might be achieved through one of the following ways:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Create a new specific functionality to achieved the goal.
+ Needed because the <xref linkend="scripts-bash-render" />
+ specific functionality uses <acronym>SVG</acronym> files as
+ reference to build images (i.e., one <acronym>SVG</acronym>
+ image produces one PNG image).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Modify <xref linkend="scripts-bash-render" /> functionality to
+ work in different modes based on file type or file extension.
+ The first mode would use <acronym>SVG</acronym> files as
+ reference to build PNG images (just as it was doing so far).
+ The second mode would use a configuration file named
+ <filename>render.conf</filename> as reference inside the
+ design models directory you want to produce images for so as
+ to build the related PNG images. In this second case, the
+ configuration file specifies how final PNG images will be
+ produced (e.g., by appending or overlapping them one another).
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ For example, consider the following command-line:
+ </para>
+
+ <cmdsynopsis>
+ <command>centos-art render Identity/Images/Brands/Logos</command>
+ </cmdsynopsis>
+
+ <para>
+ This command should evaluate which type of rendition will be
+ done, based on whether the source file is a scalable vector
+ graphic (<acronym>SVG</acronym>) or a configuration file. To
+ make this decision, the <command>centos-art.sh</command>
+ script looks for <acronym>SVG</acronym> files first, and
+ configuration files later. When <acronym>SVG</acronym> files
+ are found, the <command>centos-art.sh</command> script uses a
+ list of <acronym>SVG</acronym> files and process them one by
+ one excluding any related configuration file that could exist.
+ On the other hand, if no <acronym>SVG</acronym> file is found
+ inside the related design model directory structure, the
+ <command>centos-art.sh</command> script will use the
+ configuration file with the name
+ <filename>render.conf</filename> to create images as specified
+ inside it. When neither a <acronym>SVG</acronym> or a
+ configuration file is found inside the design model directory
+ structure, the <command>centos-art.sh</command> script
+ finishes its execution without any error message. For
+ example, if no <acronym>SVG</acronym> file is found inside
+ <filename
+ class="directory">Identity/Models/Brands/Logos/</filename>
+ directory and the
+ <filename>Identity/Models/Brands/Logos/images.conf</filename>
+ configuration file exists therein with the following content:
+ </para>
+
+<programlisting>
+[centos.png]
+models = "Identity/Models/Brands/Symbols/centos-symbol-forlogos.svgz Identity/Models/Brands/Types/centos.svgz"
+formats = "xpm jpg"
+heights = "48 78"
+fgcolor = "000000 ffffff"
+bgcolor = "ffffff-0"
+command = "/usr/bin/convert +append"
+
+[centos-artwork.png]
+models = "Identity/Models/Brands/Symbols/centos-symbol-forlogos.svgz Identity/Models/Brands/Types/centos.svgz Identity/Models/Brands/Types/artwork.svgz"
+formats = "xpm jpg"
+heights = "48 78"
+fgcolor = "000000 ffffff"
+bgcolor = "ffffff-0"
+command = "/usr/bin/convert +append"
+</programlisting>
+
+ <para>
+ The <command>centos-art.sh</command> script should produce the
+ following image files:
+ </para>
+
+<programlisting>
+Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.jpg
+Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.png
+Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.xpm
+Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.png
+Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.jpg
+Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.xmp
+Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.jpg
+Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.png
+Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.xpm
+Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.png
+Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.jpg
+Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.xmp
+Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.jpg
+Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.png
+Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.xpm
+Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.png
+Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.jpg
+Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.xmp
+Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.jpg
+Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.png
+Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.xpm
+Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.png
+Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.jpg
+Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.xmp
+</programlisting>
+
+ <para>
+ The final location for storing images output inside the
+ repository is determined by using the design model directory
+ provided as argument. Basically, the
+ <command>centos-art.sh</command> script changes the path
+ components from Models to Images and adds foreground color,
+ background color, height value and image name to it to
+ differentiate rendered images.
+ </para>
+
+ <para>
+ In case you need to restrict the amount of files you want to
+ produce including their formats, heights, colors and commands,
+ you need to modify the content of the related
+ <filename>render.conf</filename> configuration file. There is
+ not any command-line option available for such tasks. The most
+ <xref linkend="scripts-bash-render" xreflabel="render"/>
+ command-line options can do for you is when there are more
+ than one configuration file inside the same design model
+ directory and you need to specify which one of them will be
+ used as reference. In such case you can use the
+ <option>--filter="REGEX"</option> option.
+ </para>
+
+ <para>
+ When images are produced through configuration files, the
+ <command>centos-art.sh</command> script takes the order
+ provided in the list of design models to build the list of
+ images you will work with through the command specified. For
+ example, the order in which images will be appended or
+ overlapped.
+ </para>
+
+ <para>
+ Localization of logo images will not be and must not be
+ supported in any way. That would bring disastrous confusion in
+ the area of visual recognition.
+ </para>
+
+ </simplesect>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2013.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2013.docbook
new file mode 100644
index 0000000..290647a
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/History/2013.docbook
@@ -0,0 +1,141 @@
+<section id="repository-history-2013">
+
+ <title>2013's</title>
+
+ <para>
+ &TCAR; development was eventually stopped at November, 2012,
+ when I moved myself from Cienfuegos to Havana city for working
+ The first months were very difficult, specially at the moment
+ of finding a stable place to set my personal desktop (I was
+ moving myself from one apartment to another, frequently).
+ </para>
+
+ <para>
+ On May 14th, the work in Havana ends for me and I have to
+ return to Cienfuegos city. I tried to take advantage of the
+ situation dedicating more work and study hours to &TCAR; and
+ the related automation scripts once again. At this point I
+ consider a Git+Gitolite+Gitweb+MantisBT infrastructure for
+ &TCAR; and start working on it in my workstation. This, in
+ order to implement a distributed work flow for &TCAR; based on
+ Git version control system.
+ </para>
+
+ <simplesect id="repository-history-2013-VersionControl">
+ <title>Update Version Control Environment</title>
+ <para>
+ The function environment related to version control tasks was
+ renamed from <function>svn</function> to <xref
+ linkend="scripts-bash-vcs" /> in order to handle both
+ <application>Subversion</application> and
+ <application>Git</application> working copies of &TCAR;. This
+ change prepares the <command>centos-art.sh</command> script to
+ follow the suggestion of a complete migration from
+ <application>Subversion</application> to
+ <application>Git</application>, at some point.
+ </para>
+
+ <para>
+ Because the <application>Subversion</application>
+ infrastructure is the one in place right now and it is the one
+ with most artwork history, it will be
+ <application>Subversion</application> the version control
+ system we are using as default in
+ <filename>centos-art.sh</filename>. However this will surely
+ change as soon as a <application>Git</application>
+ infrastructure be approved for &TCAR; and everything could be
+ moved there.
+ </para>
+ </simplesect>
+
+ <simplesect id="repository-history-2013-ConfigurationFile">
+ <title>Start Using The <filename>centos-art.conf</filename> File</title>
+ <para>
+ Based on the need of supporting more than one application to
+ handle version control tasks, it was added the
+ <filename>centos-art.conf</filename> file into the <filename
+ class="directory">Scripts/Bash</filename> directory. This file
+ exists to customize specific behaviours of
+ <command>centos-art.sh</command> script once it has been
+ executed (e.g., what kind of application will be used as
+ default for doing version control, or even if the actions
+ related to version control will be performed or not).
+ </para>
+ </simplesect>
+
+
+ <simplesect id="repository-history-2013-UpdateRepositoryLayout">
+ <title>Update Repository Directories Structure</title>
+ <para>
+ I face the following situation: I am working on a
+ documentation project named <quote>solinfo-network</quote>.
+ While I was organizing it, I found that the directory
+ structure of &TCAR; fits quite well the needs of
+ <quote>solinfo-network</quote> documentation project. However,
+ I don't want to duplicate automation scripts in two separate
+ projects, but share them between themselves (i.e., changes
+ committed to automation scripts are pushed to one single
+ place, not two.).
+ </para>
+ <para>
+ When we use Subversion repositories, it is possible to
+ checkout specific parts of different repositories into a new
+ repository. This is very useful if we need to create several
+ projects that share the same component and we don't want to
+ duplicate the common component in two or more different
+ projects but <quote>share</quote> it between them. See
+ <xref linkend="repository-history-2012-UpdateLocales" />.
+ </para>
+
+ <para>
+ When we use Git repository, it is not possible to checkout
+ specific parts of a repository but the complete tree. So, in
+ order to share common components of a repository we need to
+ create one repository for each common component we want to
+ share and then use Git submodules<citation>see progit-book,
+ page 152.</citation> This requires that brand new
+ repositories be created for each component we want to share.
+ </para>
+
+ <para>
+ In both situations, including Git and Subversion repositories,
+ it is necessary that we define very well the structure of each
+ component we want to share, so it can be
+ <quote>plugged</quote> nicely into other projects. Likewise,
+ other projects must have the same directory structure the
+ pluggable component was design to fit in. If these two
+ conditions can be reached, it would be possible to reuse
+ repositories components and concentrate efforts. The current
+ directory structure &TCAR; is set in allows components inside
+ Subversion repositories to be reused by related working
+ copies. However, we cannot do the same if it is stored in a
+ Git repository. In order for Git repositories to be able to
+ share components with other Git repositories, &TCAR; directory
+ structure needs to be reorganized to better delineate each
+ component the repository is made of.
+ </para>
+
+ <para>
+ For more information see <xref linkend="repo-convs" />.
+ </para>
+
+ </simplesect>
+
+ <!--
+
+ <simplesect id="repository-history-2013-UpdateDocbookStructure">
+ <title>Update DocBook Physical Divisions</title>
+ <para>
+ The main purpose of this update is changing the main physical
+ division of DocBook documents from entities to XInclude. This
+ change affects both <xref linkend="scripts-bash-render"/> and
+ <xref linkend="scripts-bash-locale" /> functionalities.
+ </para>
+
+ <para>
+ ...
+ </para>
+ </simplesect>
+ -->
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Workstation.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Workstation.docbook
new file mode 100644
index 0000000..cf55d5e
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Workstation.docbook
@@ -0,0 +1,9 @@
+<chapter id="repo-ws">
+
+ <title>Preparing Your Workstation</title>
+
+ &repo-ws-intro;
+ &repo-ws-install;
+ &repo-ws-config;
+
+</chapter>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Workstation/config.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Workstation/config.docbook
new file mode 100644
index 0000000..8ad40d0
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Workstation/config.docbook
@@ -0,0 +1,351 @@
+<section id="repo-ws-config">
+
+ <title>Configuring Your Workstation</title>
+
+ <para>
+ Once your workstation has been installed, it is time for you
+ to configure it. The configuration of your workstation
+ consists on defining your workplace, download a working copy
+ from &TCAR; and finally, run the <function>prepare</function>
+ functionality of <command>centos-art.sh</command> script to
+ install/update the software needed, render images, create
+ links, and anything else needed.
+ </para>
+
+ <section id="repo-ws-config-wp">
+ <title>Define Your Workplace</title>
+ <para>
+ Once you've installed the workstation and it is up and
+ running, you need to register the user name you'll use for
+ working. In this task you need to use the commands
+ <command>useradd</command> and <command>passwd</command> to
+ create the user name and set a password for it, respectively.
+ These commands require administrative privileges to be
+ executed, so you need to login as <quote>root</quote>
+ superuser for doing so.
+ </para>
+
+ <caution>
+ <para>
+ Do not use the <quote>root</quote> username for regular
+ tasks inside your working copy of &TCAR;. This is dangerous
+ and might provoke unreversable damages to your workstation.
+ </para>
+ </caution>
+
+ <para>
+ When you've registered your user name in the workstation, it
+ provides an identifier for you to open a user's session in the
+ workstation and a place to store the information you produce,
+ as well. This place is known as your home directory and is
+ unique for each user registered in the workstation. For
+ example, if you register the user name john in your
+ workstation, your home directory would be located at <filename
+ class="directory">/home/john/</filename>.
+ </para>
+
+ <para>
+ At this point it is important to define where to download the
+ working copy of &TCAR; inside your home directory. This
+ desition deserves special attention and should be implemented
+ carefully in order to grant a standard environment that could
+ be distributed. Let's see some alternatives.
+ </para>
+
+ <section>
+ <title>Different absolute paths</title>
+ <para>
+ Consider that you store your working copy under <filename
+ class="directory">/home/john/Projects/artwork/</filename> and
+ I store mine under <filename
+ class="directory">/home/al/Projects/artwork/</filename>, we'll
+ end up refering the same files inside our working copies
+ through different absolute paths. This alternative generates
+ a contradiction when files which hold path information inside
+ are committed up to the central repository from different
+ working copies. The contradiction comes from the question:
+ which is the correct absolute path to use inside such files,
+ yours or mine? (None of them is, of course.)
+ </para>
+
+ </section>
+
+ <section id="repo-ws-config-wp-OneUniqueAbsolutePath">
+ <title>One unique absolute path</title>
+ <para>
+ Another case would be that where you and I ourselves use one
+ unique home directory (e.g., <filename
+ class="directory">/home/centos/Projects/artwork/</filename>)
+ to store the working copy of &TCAR; in our own workstations,
+ but configure the subversion client to use different user
+ names to commit changes up from the working copy to the
+ central repository. This alternative might be not so good in
+ situations where you and I have to share the same workstation.
+ In such cases, it would be required that we both share the
+ password information of the same system user (the
+ <quote>centos</quote> user in our example) which, in
+ addition, gives access to that user's subversion client
+ configuration and this way provokes the whole sense of using
+ different subversion credentials for committing changes to be
+ lost.
+ </para>
+ </section>
+
+ <section>
+ <title>Different absolute paths through dynamic expansion</title>
+ <para>
+ Most of the absolute paths we use inside the working copy are
+ made of two parts, one dynamic and one relative fixed. The
+ dynamic part is the home directory of the current user and its
+ value can be retrived from the <envar>$HOME</envar>
+ environment variable. The fixed part of the path is the one
+ we set inside the repositroy structure itself as a matter of
+ organization. What we need here is to find a way to expand
+ variables inside files that don't support variable expansion.
+ This alternative had worked rather fine when we produce
+ produce PNG files from SVG files and XTHML from DocBook files,
+ but the same is not true for absolute paths inside files that
+ are used as in their permanent state inside the repository
+ (e.g., CSS files and other files similar in purpose).
+ </para>
+ </section>
+
+ <section>
+ <title>Different absolute paths, dynamic expansion, symbolic
+ links, relative links, and environment variables</title>
+
+ <para>
+ With this solution it is possible to store working copies of
+ &TCAR; on different locations inside the same workstation
+ without lose relation between files. Here we use the
+ TCAR_WORKDIR environment variable to set the location of the
+ working copy inside the workstation. Later the centos-art.sh
+ scripts uses this value as reference to determine where the
+ working copy is. This value is also the one used for dynamic
+ expansion inside design models and other similar files. In the
+ case of web projects where different components are required
+ to produce the final content, we create symbolic links between
+ them and use relative paths so it is possible to reuse them
+ and retain the relation between them in different contexts.
+ </para>
+
+ <para>
+ For example, lets consider the organization of XHTML manuals
+ rendered from DocBook source files. When you render a DocBook
+ manual inside &TCAR; it creates XHTML files. This XHTML files
+ use images and common style sheets for better presentation.
+ Both of these images and styles components live outside the
+ XHTML structure so, in order to make them available
+ relatively to the XHTML structure, we created symbolic links
+ from the XHTML structure to the outside location where they
+ are in. The creation of symbolic links takes place
+ automatically when each DockBook manual is rendered through
+ <command>centos-art.sh</command>, which uses the value of
+ TCAR_WORKDIR environment variable as reference to determine
+ the absolute path of the working copy.
+ </para>
+
+ <para>
+ Bacause absolute paths are no longer stored inside permanent
+ files and <command>centos-art.sh</command> script uses the
+ TCAR_WORKDIR environment variable to determine where the
+ working copy is stored in the workstation, it should be safe
+ to download working copies of &TCAR; anywhere in the
+ workstation. One just have to be sure that the value of
+ TCAR_WORKDIR environment variable does match the location of
+ the working copy you are using.
+ </para>
+
+ </section>
+
+ </section>
+
+ <section id="repo-ws-config-wc">
+ <title>Download Your Working Copy</title>
+
+ <para>
+ In order to use &TCAR; you need to download a working copy
+ from the central repository into your workstation. To
+ download such working copy use the following command:
+ </para>
+
+ <screen>git clone https://projects.centos.org/~al/artwork.git</screen>
+
+ <para>
+ This command will create your working copy inside your home
+ directory, specifically in a directory named <filename
+ class="directory">artwork.git</filename>. Inside this directory
+ you will find all the files you need to work with inside
+ &TCAR;. If you want to have your working copy in a location
+ different to that one shown above, see <xref
+ linkend="repo-ws-config-ChangeWorkingCopy" />.
+ </para>
+
+ <para>
+ The first time you download the working copy it contains no
+ image files, nor documentation, or localized content inside
+ it. This is because all the files provided in the working copy
+ are source files (e.g., the files needed to produce other
+ files) and it is up to you to render them in order to produce
+ the final files (e.g., images and documentation) used to
+ implement &TCPCVI;.
+ </para>
+
+ </section>
+
+ <section id="repo-ws-config-sudoers">
+ <title>Configure Administrative Tasks</title>
+
+ <para>
+ Most of the administrative tasks you need to perform in your
+ working copy of &TCAR; are standardized inside the
+ <function>prepare</function> functionality of
+ <command>centos-art.sh</command> script. Inside
+ <command>centos-art.sh</command>
+ script, all administrative task are invoked through the
+ <command>sudo</command> command. Thus, in order for the
+ <command>centos-art.sh</command> script to perform
+ administrative tasks, you need to update the
+ <command>sudo</command>'s configuration in a way that such
+ administrative actions be allowed.
+ </para>
+
+ <para>
+ At time of this writing the <command>centos-art.sh</command>
+ script implements just one administrative task, that is
+ package management. Nevertheless, in the future, other
+ administrative tasks might be included as well (e.g.,
+ installing themes locally from the working copy for testing
+ purposes.).
+ </para>
+
+ <para>
+ To update the <command>sudo</command>'s configuration, execute
+ the <command>visudo</command> command as <quote>root</quote>.
+ Later, uncoment the <varname>Cmnd_Alias</varname> related to
+ <quote>SOFTWARE</quote> and add a line for your username
+ allowing software commands. This configuration is illustrated
+ in <xref linkend="repo-ws-config-sudoers-example" />.
+ </para>
+
+ <example id="repo-ws-config-sudoers-example">
+ <title>The <filename>/etc/sudoers</filename> configuration file</title>
+ <screenshot>
+ <screeninfo><filename>/etc/sudoers</filename> configuration file</screeninfo>
+ <mediaobject>
+ <textobject>
+<programlisting>
+## Installation and management of software
+Cmnd_Alias SOFTWARE = /bin/rpm, /usr/bin/up2date, /usr/bin/yum
+
+## Next comes the main part: which users can run what software on
+## which machines (the sudoers file can be shared between multiple
+## systems).
+## Syntax:
+##
+## user MACHINE=COMMANDS
+##
+## The COMMANDS section may have other options added to it.
+##
+## Allow root to run any commands anywhere
+root ALL=(ALL) ALL
+
+## Allow the centos user to run installation and management of
+## software anywhere.
+al ALL=(ALL) SOFTWARE
+</programlisting>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </example>
+
+ </section>
+
+ <section id="repo-ws-config-runout">
+ <title>Run Preparation Tool</title>
+ <para>
+ Once you've both downloaded a working copy from &TCAR;
+ and configured the <command>sudo</command>'s configuration
+ file successfully, run the <function>prepare</function>
+ functionality of <command>centos-art.sh</command> script to
+ complete the configuration process using the following
+ command:
+ </para>
+
+ <screen>~/artwork/Scripts/Bash/centos-art.sh prepare</screen>
+
+ <para>
+ To know more about the <function>prepare</function>
+ functionality of <command>centos-art.sh</command> script, see
+ <xref linkend="scripts-bash-prepare" />.
+ </para>
+ </section>
+
+ <section id="repo-ws-config-ChangeWorkingCopy">
+ <title>Changing Your Working Copy Default Path</title>
+ <para>
+ By default your working copy should be store in your home
+ directory, specifically in the location <filename
+ class="directory">~/artwork</filename>. This location may not
+ be the final location where you want to have your working copy
+ in situations where you are working on several projects at the
+ same time or you already have a define location to organize
+ your projects inside your home directory. Thus, you may need
+ to change the default location of your working copy to a more
+ appropriate location.
+ </para>
+
+ <para>
+ The default path to your working copy is controlled by the
+ <envar>TCAR_WORKDIR</envar> environment variable. This
+ variable is firstly defined in your personal profile after
+ running the prepare functionality of
+ <command>centos-art.sh</command> script. So, to change the
+ path of your working copy correctly, do the following:
+ </para>
+
+ <orderedlist>
+ <listitem>
+ <para>
+ Create the parent directory you will use to store your working
+ copy. For example:
+ <screen>mkdir -p ~/Projects/CentOS</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Move the currently downloaded working copy from ~/artwork to
+ your new location. For example:
+ <screen>mv ~/artwork ~/Projects/CentOS/</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Update the environment variables set in
+ <filename>~/.bash_profile</filename> by running the
+ <command>centos-art.sh</command> script from the new location.
+ For example:
+ <screen>~/Projects/CentOS/artwork/Scripts/Bash/centos-art.sh prepare --set-environment</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do log out from your active user's seesion and do log in again
+ so the environment changes take effect. Or just update the
+ current environment information by running the following
+ command:
+ <screen>. ~/.bash_profile</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Update internal links by running the
+ <command>centos-art.sh</command> script. For example:
+ <screen>${TCAR_WORKDIR}/Scripts/Bash/centos-art.sh prepare --links</screen>
+ </para>
+ </listitem>
+ </orderedlist>
+
+ </section>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Workstation/install.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Workstation/install.docbook
new file mode 100644
index 0000000..46d30a9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Workstation/install.docbook
@@ -0,0 +1,41 @@
+<section id="repo-ws-install">
+
+ <title>Installing Your Workstation</title>
+
+ <para>
+ To install your workstation use &TCD; default configuration as
+ proposed by &TCD; installer. This includes default
+ partitioning and packages. &TCAR; is been completly develop
+ upon &TCD; and realies on such environment to achieve most
+ automation tasks. In order to get a reproducable environment,
+ it is convenient that you, too, use the same operating system
+ that we do.
+ </para>
+
+ <section id="repo-ws-install-support">
+ <title>Supported Platforms</title>
+
+ <para>
+ &TCAR; has been tested in the following platforms:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ The CentOS Distribution major release 5 update 5, for i386 and
+ i686 architectures.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ In case you be using a working copy of &TCAR; in a different
+ platform from those listed here, please send a mail to <ulink
+ url="mailto:centos-devel@centos.org">centos-devel@centos.org</ulink>
+ notifying it. It is our intention to make &TCAR; as portable
+ as possible through different major releases of &TCD;.
+ </para>
+
+ </section>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Workstation/intro.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Workstation/intro.docbook
new file mode 100644
index 0000000..d6677cc
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/Workstation/intro.docbook
@@ -0,0 +1,27 @@
+<section id="repo-ws-intro">
+
+ <title>Introduction</title>
+
+ <para>
+ The workstation is the machine you use to store your working
+ copy of &TCAR;. The working copy is an ordinary directory
+ tree on your workstation, containing a collection of files
+ that you can edit however you wish. The working copy is your
+ own private work area related to &TCAR; where you perform
+ changes and receive changes from others.
+ </para>
+
+ <para>
+ In order to make your workstation completely functional, it is
+ necessary that you install it and configure it to satisfy the
+ needs demanded by the working copy of &TCAR; you later
+ download in it.
+ </para>
+
+ <para>
+ This chapter describes the steps you need to follow in order
+ to install and configure a workstation for using a working
+ copy of &TCAR; in all its extention.
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/introduction.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/introduction.docbook
new file mode 100644
index 0000000..a059dc5
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Repository/introduction.docbook
@@ -0,0 +1,120 @@
+<section id="preface-overview">
+
+ <title>Overview</title>
+
+ <para>
+ The corporations always have a corporate identity, even when
+ they don't take an intentional control over it. It is a choise
+ from the corporation to define how much control to take over
+ its identity. This kind of control is expensive and not all
+ corporations are able to maintain it. However, it is
+ necessary that, based on pragmatic facts, the corporation
+ assume an acceptable degree of compromise with its identity in
+ order to create a consistent idea of itself in a way that can
+ be progresively improved through time.
+ </para>
+
+ <para>
+ During the years (2003-2009), we've seen a growing interest
+ inside &TCC; for helping on &TCP; development. Some people
+ seem to be very clear about what the project needs are and how
+ to maintain it being a very stable project, but others however
+ don't to get what &TCP; is (even it is explained time after
+ time) and sometimes decide to put their efforts in the wrong
+ direction making everything to be a waste of time and source
+ of distraction from what is really needed.
+ </para>
+
+ <para>
+ &TCAR; phases the question <quote>What can I do for
+ &TCP;?</quote> by identifying different work lines you can
+ join in and providing automated production mechanisms that
+ complement one another according to each work line needs so
+ consistent results can be achieved inside a distributed
+ environment under version control. For example, consider an
+ environment where there are graphic designers to produce
+ images, documentors to produce documentation manuals (whose
+ can use images produced by graphic designers), programmers to
+ produce automation scripts (needed to standardize production
+ tasks) and translators to localize source files created by
+ graphic designers, documetors and programmers. Once such
+ environment has been implemented, it would be possible for
+ packagers to take localized images and localized documentation
+ from &TCAR; (through an automation script probably) to
+ rebrand/update the content of those packages inside &TCD; that
+ must include information specific to &TCP; itself (e.g., boot
+ loader, distribution installer, release notes, display
+ managers, release notes, web browsers default page, etc.).
+ </para>
+
+ <para>
+ Most production tasks inside &TCAR; are focused on the files
+ needed to implement &TCP; corporate visual identity.<footnote>
+ <para>
+ Notice that, here, visual identity means everything
+ perceived through the human's visual sences (i.e., the
+ human eyes), but the corporate identity is a wider concept
+ that extends to all human senses (i.e., visibilty (eyes),
+ audition (ears), scent (nose), touch (fingers), and savour
+ (tongue)), not just that one related to visual aspects.
+ Nevertheless, we need to be consequent with the media
+ where &TCP; manifests its existence on, as described in
+ <xref linkend="identity" />.
+ </para></footnote> This includes everything from file edition
+ (e.g., text width, text indentation, line numbering, text
+ tabulation, etc.) up to how the web sites, distribution, and
+ industrial stuff (e.g., pullovers, caps, installation media,
+ etc.) look and feel. Notice that, more specific details like
+ typography, window design, icons, menu items, etc., inside
+ &TCD; are already covered by &TCP; upstream provider. In our
+ effort to be 100% binary compatible with the upstream provider
+ and also keeping maintainance low, we stand over those
+ specific details as much as possible assuming them as default.
+ However, if you feel brave enough (and prove your ability to
+ keep yourself being that way) it would be possible to open a
+ work line for you to maintain variants of such very specific
+ details inside &TCAR;.
+ </para>
+
+ <para>
+ In addition to visual manifestations, there are also emotional
+ feelings and ethical behaviours that must be considered as
+ part of &TCP; corporate identity. A pleasant experience in
+ this area includes &TCWIKI;, specifically the way it was
+ conceived and administered. When the &TCWIKI; was published,
+ &TCP; published a list of needs with it so anyone could
+ contribute based on them. Not much time after that, the list
+ of tasks triggered some souls' motivations ruled by the good
+ will of initiating the translation of that content published
+ inside the wiki, redesigning its visual style, proposing the
+ TreeFlower theme for &TCD;, and reducing to zero the
+ contraditions of precoceived minds with respect, reason and
+ passion. As result of this experience, we found that &TCC;
+ posseses an incredible strong creative force, however, a long
+ path must be traveled before it can be focalized into the
+ right direction because: it isn't enough just telling what the
+ right direction is, it is also necessary to provide the
+ vehicles for &TCC; be able of moving through it.
+ </para>
+
+ <para>
+ &TCAR; extends the feelings and ethicals behaviours from
+ &TCWIKI; to itself by identifying the visual manifestations
+ &TCP; is made of (i.e., tracing a direction) and allowing
+ people to develop them through standardized procedures inside
+ a colaborative environment (i.e., providing the vehicles).
+ </para>
+
+ <para>
+ Finally, if you find yourself needing to do something for
+ &TCP; and &TCAR; isn't the place for it, be sure to define
+ what that something exactly is and also make it a community
+ effort so it can be validated as something useful to the
+ community itself. Otherwise, the effort would loose its
+ initial sense soon enough so as to be considered seriously.
+ Notice that the way these needs are described may take
+ different forms: they can be written and organized inside a
+ book, an article, or even a well documented program ;-).
+ </para>
+
+</section>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts.docbook
new file mode 100644
index 0000000..088ba46
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts.docbook
@@ -0,0 +1,24 @@
+<part id="scripts">
+
+ <title>Automation</title>
+
+ <partintro>
+ <para>
+ This part of the book describes &TCAR; automation work
+ line. Through this work line programmers provide the
+ production standards that graphic designers,
+ documentalists, translators and packagers need to make
+ their work consistent and reusable. For this purpose,
+ programmers develop the <command>centos-art.sh</command>
+ script and its functionalities. The main purpose of this
+ work line is standardize the interaction of work lines in
+ a reliable way. The automation work line takes place in
+ the <ulink
+ url="https://projects.centos.org/~al/artwork.git/Scripts">Scripts</ulink>
+ directory.
+ </para>
+ </partintro>
+
+ &scripts-bash;
+
+</part>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts.ent b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts.ent
new file mode 100644
index 0000000..3a8db4c
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts.ent
@@ -0,0 +1,16 @@
+<!ENTITY scripts SYSTEM "Scripts.docbook">
+<!ENTITY scripts-bash SYSTEM "Scripts/Bash.docbook">
+<!ENTITY scripts-bash-intro SYSTEM "Scripts/Bash/intro.docbook">
+<!ENTITY scripts-bash-mission SYSTEM "Scripts/Bash/mission.docbook">
+<!ENTITY scripts-bash-nameconvs SYSTEM "Scripts/Bash/nameconvs.docbook">
+<!ENTITY scripts-bash-environment SYSTEM "Scripts/Bash/environment.docbook">
+<!ENTITY scripts-bash-cliref SYSTEM "Scripts/Bash/cliref.docbook">
+<!ENTITY scripts-bash-render SYSTEM "Scripts/Bash/render.docbook">
+<!ENTITY scripts-bash-locale SYSTEM "Scripts/Bash/locale.docbook">
+<!ENTITY scripts-bash-help SYSTEM "Scripts/Bash/help.docbook">
+<!ENTITY scripts-bash-prepare SYSTEM "Scripts/Bash/prepare.docbook">
+<!ENTITY scripts-bash-pack SYSTEM "Scripts/Bash/pack.docbook">
+<!ENTITY scripts-bash-tuneup SYSTEM "Scripts/Bash/tuneup.docbook">
+<!ENTITY scripts-bash-vcs SYSTEM "Scripts/Bash/vcs.docbook">
+
+<!ENTITY scripts-bash-cli_checkFiles SYSTEM "Scripts/Bash/cli_checkFiles.docbook">
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash.docbook
new file mode 100644
index 0000000..33a1e2f
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash.docbook
@@ -0,0 +1,23 @@
+<reference id="scripts-bash">
+
+ <title>The <command>centos-art.sh</command> Reference</title>
+ <subtitle>Version 0.4</subtitle>
+
+ <partintro>
+ &scripts-bash-intro;
+ &scripts-bash-mission;
+ &scripts-bash-nameconvs;
+ &scripts-bash-cliref;
+ &scripts-bash-environment;
+ </partintro>
+
+ &scripts-bash-prepare;
+ &scripts-bash-help;
+ &scripts-bash-render;
+ &scripts-bash-locale;
+ &scripts-bash-pack;
+ &scripts-bash-tuneup;
+ &scripts-bash-vcs;
+ &scripts-bash-cli_checkFiles;
+
+</reference>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/cli_checkFiles.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/cli_checkFiles.docbook
new file mode 100644
index 0000000..74f40a4
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/cli_checkFiles.docbook
@@ -0,0 +1,245 @@
+<refentry id="scripts-bash-cli_checkFiles">
+
+ <refmeta>
+ <refentrytitle>cli_checkFiles</refentrytitle>
+ <manvolnum>1</manvolnum>
+ <indexterm type="common-function">
+ <primary>Standardize constructions for file verifications</primary>
+ </indexterm>
+ </refmeta>
+
+ <refnamediv>
+ <refname>cli_checkFiles</refname>
+ <refpurpose>Standardize constructions for file verifications.</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <cmdsynopsis>
+ <command>cli_checkFiles</command>
+ <arg choice="req">
+ <arg>-d</arg>
+ <arg>-e</arg>
+ <arg>-f</arg>
+ <arg>-h</arg>
+ <arg>-x</arg>
+ </arg>
+ <arg choice="req" rep="repeat"><replaceable>LOCATION</replaceable></arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsection id="scripts-bash-cli_checkFiles-description">
+ <title>Description</title>
+ <para>
+ The <function>cli_checkFiles</function> exists to answer basic
+ questions like <quote>Is <replaceable>LOCATION</replaceable>
+ is a regular file?</quote> and <quote>Is
+ <replaceable>LOCATION</replaceable> a directory?</quote>. The
+ answer to such questions affects the script execution flow in
+ the following way: when the answer positive (e.g.,
+ <replaceable>LOCATION</replaceable> is a regular file), the
+ script passes the test silently and continues its execution.
+ When the answer is negative(e.g.,
+ <replaceable>LOCATION</replaceable> is not a regular file),
+ the script finishes its execution immediately with an error
+ message.
+ </para>
+
+ <para>
+ The <function>cli_checkFiles</function> function is exported
+ to <command>centos-art.sh</command> script environment in the
+ very beginning of its execution and will be available all
+ along its execution lifetime. You can use this function inside
+ common and specific functions whenever you need to verify
+ files inside the &TCAR;.
+ </para>
+
+ <para>
+ The <function>cli_checkFiles</function> function is available
+ inside the <command>centos-art.sh</command> script only as
+ part of its execution environment. This function is exported
+ to <command>centos-art.sh</command> script just after
+ executing the script from the command-line and will be
+ available all along the script lifetime. So, you can use this
+ function both in common and specific functionalities of
+ centos-art.sh script.
+ </para>
+
+ <para>
+ The <function>cli_checkFiles</function> function doesn't
+ create subsequent execution environments.
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-cli_checkFiles-usage">
+ <title>Usage</title>
+ <para>
+ Use the <function>cli_checkFiles</function> function inside
+ <command>centos-art.sh</command> script whenever you need to
+ control the script execution flow based on file type (e.g.,
+ regular files, directories, links, etc.) verifications.
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-cli_checkFiles-options">
+ <title>Options</title>
+ <para>
+ The <function>cli_checkFiles</function> function accepts the
+ following options:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><option>-d</option></term>
+ <listitem>
+ <para>
+ Verifies whether <replaceable>LOCATION</replaceable> exists
+ and is a directory. If it doesn't exists or isn't a directory,
+ an error message is printed and the script finishes its
+ execution. Otherwise, if it exists and is a directory, the
+ script continues its execution normally.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-e</option></term>
+ <listitem>
+ <para>
+ Verifies whether <replaceable>LOCATION</replaceable> exists or
+ not. If it doesn't exist, an error message is printed and the
+ script finishes its execution. Otherwise, if it does exists,
+ the script continues its execution normally.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-f</option></term>
+ <listitem>
+ <para>
+ Verifies whether <replaceable>LOCATION</replaceable> exists
+ and is a regular file. If it doesn't exists or isn't a regular
+ file, an error message is printed and the script finishes its
+ execution. Otherwise, if it exists and is a regular file, the
+ script continues its execution normally.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-h</option></term>
+ <listitem>
+ <para>
+ Verifies whether <replaceable>LOCATION</replaceable> exists
+ and is a symbolic link. If it doesn't exists or isn't a
+ symbolic link, an error message is printed and the script
+ finishes its execution immediately. Otherwise, if it does
+ exist and is a symbolic link, the script continue its
+ execution normally.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-x</option></term>
+ <listitem>
+ <para>
+ Verifies whether <replaceable>LOCATION</replaceable> exists
+ and execution permission is granted. If it doesn't exist or
+ hasn't execution permission, the script finishes its execution
+ immediately. Otherwise, if it exists and has execution
+ permissions, the script continues its execution normally.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>
+ The value of the <replaceable>LOCATION</replaceable> argument
+ must be an absolute path to the file you want to verify. If
+ such file doesn't exists in any supported form, the script
+ finishes its execution with an error message.
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-cli_checkFiles-example">
+ <title>Examples</title>
+ <para>
+ The following example was taken from
+ <command>centos-art.sh</command> script initialization phase.
+ Notice the position of <function>cli_checkFiles</function>
+ function inside the loop. If some of the function files we
+ need to export doesn't have execution rights,
+ <function>cli_checkFiles</function> will
+ finish the script execution immediately with an error message.
+ </para>
+<programlisting language="bash">
+# Process the list of files.
+for FUNCFILE in $FUNCFILES;do
+
+ # Verify the execution rights for function file.
+ cli_checkFiles -x ${FUNCFILE}
+
+ # Initialize the function file.
+ . ${FUNCFILE}
+
+ # Export the function names inside the file to current shell
+ # script environment.
+ export -f $(egrep "${PATTERN}" ${FUNCFILE} | gawk '{ print $2 }')
+
+done
+</programlisting>
+ </refsection>
+
+ <refsection>
+ <title>Bugs</title>
+ <para>
+ To report bugs related to this function, please create a new
+ ticket at <ulink
+ url="https://projects.centos.org/trac/artwork" /> refering the
+ name of this function clearly and the specific problems you
+ found in it.
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-cli_checkFiles-authors">
+ <title>Authors</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Alain Reguera Delgado <email>alain.reguera@gmail.com</email>, =COPYRIGHT_YEAR_LIST=
+ </para>
+ </listitem>
+ </itemizedlist>
+ </refsection>
+
+ <refsection id="scripts-bash-cli_checkFiles-licence">
+ <title>License</title>
+
+ <para>
+ Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ </refsection>
+
+</refentry>
+
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/cliref.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/cliref.docbook
new file mode 100644
index 0000000..a8ff53e
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/cliref.docbook
@@ -0,0 +1,569 @@
+<sect1 id="scripts-bash-cliref">
+
+ <title>Command-line Interface</title>
+
+ <para>
+ The <command>centos-art.sh</command> script follows a
+ conventional GNU/Linux command-line interface where there
+ might be options and non-option arguments in it. As convention
+ to <command>centos-art.sh</command>, the first non-option
+ argument passed through the command-line will be the name of
+ the specific function you want to execute (e.g., <xref
+ linkend="scripts-bash-render" />, <xref
+ linkend="scripts-bash-locale" />, <xref
+ linkend="scripts-bash-help" />, etc.). This first argument
+ will be immediately removed from the list of arguments passed
+ to <command>centos-art.sh</command> script leaving just the
+ remaining options and non-option arguments passed to it. From
+ this point on, the <command>centos-art.sh</command> script
+ uses the <command>getopt</command> command to retrieve option
+ arguments and remove them from the list of arguments passed to
+ <command>centos-art.sh</command> script.
+ </para>
+
+ <para>
+ To better understand the <command>centos-art.sh</command>
+ command-line interface, consider the command shown in <xref
+ linkend="scripts-bash-cliref-example1" />. This example
+ shows the entire command as a list of space-separated
+ arguments. Each argument passed in the command-line can be
+ reached using positional variables as described in <xref
+ linkend="scripts-bash-cliref-implementation-example1" />.
+ </para>
+
+ <example id="scripts-bash-cliref-example1">
+ <title>The command-line interface</title>
+ <screenshot>
+ <screeninfo>The command-line interface</screeninfo>
+ <mediaobject>
+ <textobject>
+<programlisting>
+centos-art render Identity/Images/Themes --with-brands
+</programlisting>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </example>
+
+ <sect2 id="scripts-bash-cliref-options">
+ <title>Option Arguments</title>
+
+ <para>
+ As convention inside the <command>centos-art.sh</command>, all
+ specific function environments should provide support for the
+ following option arguments:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><option>-h</option> | <option>--help</option></term>
+ <listitem>
+ <para>
+ This option makes <command>centos-art.sh</command> to shows
+ information about the specific function environment (e.g., how
+ to execute it, available options, etc.) set as first
+ non-option argument. For example, if you provide the
+ <command>centos-art render --help</command>, the
+ <command>centos-art.sh</command> script will display to you
+ the information related to <xref linkend="scripts-bash-render"
+ /> functionality.
+ </para>
+ <para>
+ This information is retrieved from <quote>The CentOS Artwork
+ Repository File System (tcar-fs)</quote> documentation manual.
+ This manual is written in Texinfo format and provides a quick
+ way for you to read and browse documentation related to each
+ directory inside &TCAR; as you work with it from a text
+ terminal.
+ </para>
+
+ <!--
+ Enhancement
+ ===========
+ At some point, documentation written in Texinfo format will be
+ replaced by Docbook format and profiling will be used to reach
+ documentation model files which will be also transformed
+ automatically based on the output required. In the case of
+ centos-art.sh help functionality, man pages will be used as
+ default output format.
+ -->
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-q</option> | <option>--quiet</option></term>
+ <listitem>
+ <para>
+ This option makes the <command>centos-art.sh</command> script
+ to suppress messages sent to standard output. This option
+ doesn't suppress error messages, nor questions related to
+ script execution.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+
+ <para>
+ The specific option arguments used by function environments
+ are described individually, as part of each function
+ environment documentation. To know more about the specific
+ options used by function environments, see <xref
+ linkend="scripts-bash-cliref-specificfuncs" /> and <xref
+ linkend="scripts-bash-cliref-commonfuncs" />.
+ </para>
+
+ <table id="scripts-bash-cliref-specificfuncs">
+ <title>Specific functions environment</title>
+ <tgroup cols="2" align="left">
+ <thead>
+ <row>
+ <entry>Name</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+
+ <tbody>
+ <row>
+ <entry><xref linkend="scripts-bash-prepare" /></entry>
+ <entry>Standardize configuration tasks inside &TCAR;</entry>
+ </row>
+ <row>
+ <entry><xref linkend="scripts-bash-render" /></entry>
+ <entry>Standardize rendition tasks inside &TCAR;</entry>
+ </row>
+ <row>
+ <entry><xref linkend="scripts-bash-locale" /></entry>
+ <entry>Standardize localization tasks inside &TCAR;</entry>
+ </row>
+ <row>
+ <entry><xref linkend="scripts-bash-help" /></entry>
+ <entry>Standardize documentation tasks inside &TCAR;</entry>
+ </row>
+ <row>
+ <entry><xref linkend="scripts-bash-pack" /></entry>
+ <entry>Standardize packing tasks inside &TCAR;</entry>
+ </row>
+ <row>
+ <entry><xref linkend="scripts-bash-tuneup" /></entry>
+ <entry>Standardize maintainance tasks inside &TCAR;</entry>
+ </row>
+ <row>
+ <entry><xref linkend="scripts-bash-vcs" /></entry>
+ <entry>Standardize version control tasks inside &TCAR;</entry>
+ </row>
+ </tbody>
+
+ </tgroup>
+ </table>
+
+ <table id="scripts-bash-cliref-commonfuncs">
+ <title>Common functions environment</title>
+ <tgroup cols="2" align="left">
+ <thead>
+ <row>
+ <entry>Name</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+
+ <tbody>
+ <row>
+ <entry>
+ <literal>cli_checkFiles</literal>
+ </entry>
+ <entry>
+ Standardize conditional expressions applied to files
+ (including links and directories) inside the
+ <command>centos-art.sh</command> script.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_checkRepoDirSource</entry>
+ <entry>
+ Standardize directories' path construction inside the
+ working copy, using absolute paths.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_expandTMarkers</entry>
+ <entry>
+ Standardize translation markers construction and their
+ related expansion.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_exportFunctions</entry>
+ <entry>
+ Standardize the way specific functionalities are
+ exported to <command>centos-art.sh</command> script
+ environment.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_getConfigLines</entry>
+ <entry>
+ Standardize the way configuration lines are retrieved
+ form configuration files.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_getConfigSectionNames</entry>
+ <entry>
+ Standardize the way section names are retrieved from
+ configuration files.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_getConfigValue</entry>
+ <entry>
+ Standardize the way configuration values are retrieved
+ from configuration files.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_getFilesList</entry>
+ <entry>
+ Standardize the way list of files are built inside
+ <command>centos-art.sh</command> script.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_getPathComponent</entry>
+ <entry>
+ Standardize the way directory structures are organized
+ inside the working copy of &TCAR;.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_getRepoName</entry>
+ <entry>
+ Standardize files and directories name convection
+ inside the working copy of &TCAR;.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_getTemporalFile</entry>
+ <entry>
+ Standardize temporal files creation.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_parseArgumentsReDef</entry>
+ <entry>
+ Initiate/reset and sanitize positional parameters
+ passed to this function and creates the list of
+ arguments that <command>getopt</command> will process.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_parseArguments</entry>
+ <entry>
+ Redefine the <varname>ARGUMENTS</varname> global
+ variable using <command>getopt</command> output.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_printCopyrightInfo</entry>
+ <entry>
+ Standardize the copyright information printed on
+ content produced by <command>centos-art.sh</command>
+ script.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_printMailingList</entry>
+ <entry>
+ Standardize the way mailing list addresses are printed
+ on content produced by
+ <command>centos-art.sh</command> script.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_printMessage</entry>
+ <entry>
+ Standardize the way messages are printed by
+ <command>centos-art.sh</command> script.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_printUrl</entry>
+ <entry>
+ Standardize the way URLs are printed by
+ <command>centos-art.sh</command> script.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_runFnEnvironment</entry>
+ <entry>
+ Standardize the way <command>centos-art.sh</command>
+ script is called to itself.
+ </entry>
+ </row>
+ <row>
+ <entry>cli</entry>
+ <entry>
+ Initiates the <command>centos-art.sh</command> script
+ command-line interface.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_synchronizeRepoChanges</entry>
+ <entry>
+ Standardize the way changes are synchronized between
+ the working copy and the central repository.
+ </entry>
+ </row>
+ <row>
+ <entry>cli_terminateScriptExecution</entry>
+ <entry>
+ Standardize the actions that must be realized just
+ before leaving the script execution (e.g., cleaning
+ temporal files).
+ </entry>
+ </row>
+ <row>
+ <entry>cli_unsetFunctions</entry>
+ <entry>
+ Unset functionalities from
+ <command>centos-art.sh</command> script execution
+ environment.
+ </entry>
+ </row>
+
+ </tbody>
+
+ </tgroup>
+ </table>
+
+ </sect2>
+
+ <sect2>
+ <title>Non-Option Arguments</title>
+
+ <para>
+ Once option arguments have been removed from the list of
+ arguments passed to <command>centos-art.sh</command>
+ command-line, non-option arguments are processed then.
+ Non-option arguments will always be paths pointing to
+ directories inside your working copy of &TCAR; or
+ documentation entries pointing to specific sections in a
+ documentation manual. Paths provided in the command-line can
+ be absolute or relative considering the root directory of the
+ working copy as start point. For example, both the absolute
+ path <quote><filename
+ class="directory">${HOME}/Projects/CentOS/artwork/Identity/Themes/</filename></quote>
+ and the relative path <quote><filename
+ class="directory">Identity/Themes</filename></quote> point to
+ the same location. Documentation entries, on the other hand,
+ exist to specify the files inside the <quote><filename
+ class="directory">Documentation/Models/</filename></quote>
+ directory structure you want to work with, based on specific
+ documentation manual components (e.g., manual name, part,
+ chapter or section). To know more about documentation entries,
+ see the <xref linkend="scripts-bash-help"/> functionality
+ reference.
+ </para>
+
+ </sect2>
+
+ <sect2 id="scripts-bash-cliref-implementation">
+
+ <title>Implementation</title>
+
+ <para>
+ The command-line interface of
+ <command>centos-art.sh</command> script is implemented
+ individually for each specific function environments it is
+ made of. Each specific function environment inside the
+ <command>centos-art.sh</command> has its own command-line
+ definition and can differ in options when they are
+ compared one another. The command-line differences between
+ specific function environments exist as consequence of the
+ purpose they were designed for (e.g., different purposes,
+ different options and arguments). Nevertheless, all
+ specific function environments use the same base
+ construction to implement their unique command-line
+ interfaces (see <xref
+ linkend="scripts-bash-cliref-implementation-example1" />).
+ </para>
+
+ <para>
+ The specific function environments the
+ <command>centos-art.sh</command> script is made of use the
+ <quote><filename>Scripts/Bash/Functions/<replaceable>Fname</replaceable>/<replaceable>fname</replaceable>_getOptions.sh</filename></quote>
+ file to store the
+ <function><replaceable>fname</replaceable>_getOptions</function>
+ function definition. This function definition is where you
+ set the relation between actions to be executed and
+ arguments passed to <command>centos-art.sh</command>
+ script.
+ </para>
+
+ <para>
+ Basically, when you decide to create new function
+ environments for the <command>centos-art.sh</command>
+ script, you need to consider whether they will use
+ arguments from the command-line or not. When the function
+ environment doesn't need arguments (e.g., it exists to
+ redefine values related to variables only) there is not
+ need to consider a parsing feature for it. However, when
+ you need to interact with a specific function through the
+ command-line, you should use the
+ <function><replaceable>fname</replaceable>_getOptions</function>
+ function related to your
+ <function><replaceable>fname</replaceable></function>
+ function environment to define the way such interaction
+ will take place. This way you can control the possible
+ arguments your function environment will be able to
+ interpret from the command-line.
+ </para>
+
+ <example id="scripts-bash-cliref-implementation-example1">
+ <title>The command-line implementation</title>
+ <screenshot>
+ <screeninfo>The command-line implementation</screeninfo>
+ <mediaobject>
+ <textobject>
+<programlisting>
+function <replaceable>fname</replaceable>_getOptions {
+
+ # Define short options we want to support.
+ local ARGSS="h,q"
+
+ # Define long options we want to support.
+ local ARGSL="help,quiet"
+
+ # Redefine ARGUMENTS using getopt(1) command parser.
+ cli_parseArguments
+
+ # Redefine positional parameters using ARGUMENTS variable.
+ eval set -- "$ARGUMENTS"
+
+ # Look for options passed through command-line.
+ while true; do
+
+ case "$1" in
+
+ -h | --help )
+ cli_runFnEnvironment help --read --format="texinfo" "tcar-fs::scripts:bash-functions-<replaceable>fname</replaceable>"
+ shift 1
+ exit
+ ;;
+
+ -q | --quiet )
+ FLAG_QUIET="true"
+ shift 1
+ ;;
+
+ -- )
+ # Remove the `--' argument from the list of arguments
+ # in order for processing non-option arguments
+ # correctly. At this point all option arguments have
+ # been processed already but the `--' argument still
+ # remains to mark ending of option arguments and
+ # beginning of non-option arguments. The `--' argument
+ # needs to be removed here in order to avoid
+ # centos-art.sh script to process it as a path inside
+ # the repository, which obviously is not.
+ shift 1
+ break
+ ;;
+ esac
+ done
+
+ # Redefine ARGUMENTS variable using current positional parameters.
+ cli_parseArgumentsReDef "$@"
+
+}
+</programlisting>
+</textobject>
+</mediaobject>
+</screenshot>
+</example>
+
+ <para>
+ Using the base structure described in <xref
+ linkend="scripts-bash-cliref-implementation-example1"/>, you can
+ create new options so your specific function environment
+ can express its usefulness. For example, if you want your
+ specific function environment to print a greeting on the
+ screen when the <option>--hello</option> option is passed
+ through its command-line, you can modify the base
+ structure shown above with the following:
+ </para>
+
+<programlisting>
+...
+
+ # Define long options we want to support.
+ local ARGSL="help,quiet,hello"
+
+...
+
+ --hello )
+ cli_printMessage "`gettext "Hello World!"`"
+ shift 1
+ ;;
+...
+</programlisting>
+
+ <para>
+ In case you want to provide an option value in the form
+ <option>--hello="World"</option>, you can do it as described
+ below:
+ </para>
+
+<programlisting>
+...
+
+ # Define long options we want to support.
+ local ARGSL="help,quiet,hello:"
+
+...
+
+ --hello )
+ cli_printMessage "`gettext "Hello"` ${2}"
+ shift 2
+ ;;
+...
+</programlisting>
+
+ <para>
+ In this last case, the option value is required. So, if you
+ provide the <option>--hello</option> option but do not provide
+ a value for it, an error will be triggered and the script will
+ finish its execution. To make an option value not-required,
+ you need to use two colons instead of one when you define the
+ options, see the following lines:
+ </para>
+
+<programlisting>
+...
+
+ # Define long options we want to support.
+ local ARGSL="help,quiet,hello::"
+
+...
+
+ --hello )
+ cli_printMessage "`gettext "Hello"` ${2}"
+ shift 2
+ ;;
+...
+</programlisting>
+
+ <para>
+ To know more about the features provided by
+ <command>getopt</command> command, read its man page (e.g.,
+ typing the <command>man getopt</command> command in your
+ terminal). This information will also help you to understand
+ how to improve the command-line interfaces you create for
+ the function environments of <command>centos-art.sh</command>
+ script.
+ </para>
+
+ </sect2>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/environment.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/environment.docbook
new file mode 100644
index 0000000..fbbcfd9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/environment.docbook
@@ -0,0 +1,475 @@
+<sect1 id="scripts-bash-environment">
+
+ <title>The Execution Environment</title>
+
+ <para>
+ The execution environment of <command>centos-art.sh</command>
+ script is organized in four levels. The first level is the
+ <quote>shell environment</quote>, the second level is the
+ <quote>command environment</quote>, the third level is the
+ <quote>common functions environment</quote> and, finally, the
+ fourth level which contains the <quote>specific function
+ environment</quote>, as described in <xref
+ linkend="scripts-bash-environment-example1" />. In this
+ context, child environments inherit definitions (e.g.,
+ variables and functions) from their parent environments making
+ possible to logically organize the script in a way that needs
+ can be isolated one another to follow the paradigm proposed by
+ Unix developers at Bell Labs when felt that programs
+ <quote>should do one thing well.</quote>
+ </para>
+
+ <example id="scripts-bash-environment-example1">
+ <title>The execution environment</title>
+ <screenshot>
+ <screeninfo>The execution environment</screeninfo>
+ <mediaobject>
+ <textobject>
+<programlisting>
++-----------------------------------------------------+
+| Shell environment |
++---|-------------------|-----------------|-----------+
+. |-- TCAR_WORKDIR |-- TCAR_BRAND |-- EDITOR .
+. |-- LANG |-- HOME |-- PATH .
+. `-- centos-art.sh `-- TMPDIR `-- ... .
+. +---|-----------------------------------------+ .
+. | Command environment | .
+. +---|---------------|----------------|--------+ .
+. . |-- CLI_NAME |-- CLI_VERSION `-- ... . .
+. . |-- CLI_FUNCDIR `-- CLI_BASEDIR . .
+. . `-- cli() . .
+. . +---|-----------------------------------+ . .
+. . | Common functions environment | . .
+. . +---|------------------------|----------+ . .
+. . . |-- cli_printMessage() |-- ... . . .
+. . . |-- cli_getFilesList() |-- ... . . .
+. . . `-- render() `-- ... . . .
+. . . +---|---------------------------+ . . .
+. . . | Specific function environment | . . .
+. . . +-------------------------------+ . . .
+. . ......................................... . .
+. ............................................... .
+.......................................................
+</programlisting>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </example>
+
+ <sect2>
+ <title>The Shell Environment</title>
+
+ <para>
+ The <command>centos-art.sh</command> script uses the following
+ shell environment variables:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><envar>PATH</envar></term>
+ <listitem>
+ <para>
+ The <envar>PATH</envar> environment variable is specific to
+ the operating system and provides search paths for command
+ execution. By default, the <command>centos-art.sh</command>
+ script links executable scripts from the <filename
+ class="directory">~/bin</filename> directory which is one of
+ the locations used as search path in this variable. This is
+ how we create the <command>centos-art</command> command from
+ the <command>centos-art.sh</command> script inside your
+ working copy.
+ </para>
+
+ <para>
+ This variable is not initialized inside the
+ <command>centos-art.sh</command> script. Instead, the value
+ set in <filename>~/.bash_profile</filename> file is used.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><envar>EDITOR</envar></term>
+ <listitem>
+ <para>
+ The <envar>EDITOR</envar> environment variable is specific to
+ the operating system and provides the path to your default
+ text editor. The <command>centos-art.sh</command> script uses
+ the default text editor to edit subversion pre-commit
+ messages, translation files, documentation files, script
+ files, and similar text-based files.
+ </para>
+
+ <para>
+ Possible values for this variable are:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename class="directory">/usr/bin/vim</filename>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename class="directory">/usr/bin/emacs</filename>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename class="directory">/usr/bin/nano</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ In case none of these values is set for the
+ <envar>EDITOR</envar> environment variable inside
+ <filename>~/.bash_profile</filename>, the
+ <command>centos-art.sh</command> script uses <filename
+ class="directory">/usr/bin/vim</filename> as default text
+ editor. This is the text editor installed by default in &TCD;.
+ </para>
+
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><varname>TEXTDOMAIN</varname></term>
+ <listitem>
+ <para>
+ The <envar>TEXTDOMAIN</envar> environment variable is specific
+ to the operating system and provides the domain name of that
+ application we are producing translation messages for. This
+ variable, in combination with <envar>TEXTDOMAINDIR</envar>, is
+ used by <application>gettext</application> to find out the
+ location of translation messages. In the very specific case
+ of <command>centos-art.sh</command> script we use the
+ <literal>centos-art.sh</literal> name as domain name.
+ </para>
+
+ <para>
+ This variable is initialized inside the
+ <command>centos-art.sh</command> script, so if you set it
+ outside it (e.g., in <filename>~/.bash_profile</filename>) the
+ value you set there will be overwritten by that one set inside
+ <command>centos-art.sh</command> script, once it is executed.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>TEXTDOMAINDIR</varname></term>
+ <listitem>
+ <para>
+ The <envar>TEXTDOMAINDIR</envar> environment variable is
+ specific to the operating system and provides the absolute
+ path to the directory containing the translation messages
+ related to that application specified by
+ <envar>TEXTDOMAIN</envar> environment variable. In the very
+ specific case of <command>centos-art.sh</command> script we
+ use the <filename
+ class="directory">Locales/Scripts/Bash</filename>
+ path as default value.
+ </para>
+ <para>
+ This variable is initialized inside the
+ <command>centos-art.sh</command> script, so if you set it
+ outside it (e.g., in <filename>~/.bash_profile</filename>) the
+ value you set there will be overwritten by that one set inside
+ <command>centos-art.sh</command> script, once it is executed.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><envar>TMPDIR</envar></term>
+ <listitem>
+ <para>
+ The <envar>TMPDIR</envar> environment variable is specific to
+ the operating system and provides the absolute path to the
+ temporal directory the centos-art.sh script will use along its
+ execution. This variable is defined inside the
+ <command>centos-art.sh</command> script itself using the
+ <command>mktemp</command> command and will be unique on each
+ script execution. Thus, you should be able to run several
+ instances of <command>centos-art.sh</command> script
+ simultaneously without any problem.
+ </para>
+
+ <para>
+ When you contribute code to <command>centos-art.sh</command>
+ script and need to create temporal files, do it inside the
+ absolute path specified by this variable.
+ </para>
+
+ <para>
+ This variable is redefined inside the
+ <command>centos-art.sh</command> script, so if you set it
+ outside it (e.g., in <filename>~/.bash_profile</filename>) the
+ value you set there will be overwritten by that one set inside
+ <command>centos-art.sh</command> script, once it is executed.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><envar>LANG</envar></term>
+ <listitem>
+ <para>
+ The <envar>LANG</envar> environment variable is specific to
+ the operating system and controls the default locale
+ information of it. The <command>centos-art.sh</command>
+ script use the <envar>LANG</envar> environment variable to
+ determine what language to use for printing output messages
+ from the script itself, as well as the portable objects
+ locations that need to be updated or edited when you localize
+ directory structures inside the working copy of &TCAR;.
+ </para>
+
+ <para>
+ The <envar>LANG</envar> environment variable is initially set
+ in the installation process of &TCD;, specifically in the
+ <emphasis>Language</emphasis> step. Generally, there is no
+ need to customize this variable in your personal profile. If
+ you need to change the value of this environment variable do
+ it through the login screen of GNOME Desktop Environment or
+ the <command>system-config-language</command> command, or even
+ resetting the variable before executing the
+ <command>centos-art.sh</command> script.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+
+ <para>
+ In addition to shell environment variables described above,
+ the <command>centos-art.sh</command> script adds the following
+ variables inside the <filename>~/.bash_profile</filename> file
+ to control the script behaviour in a per-user level:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><varname>TCAR_WORKDIR</varname></term>
+ <listitem>
+ <para>
+ The <envar>TCAR_WORKDIR</envar> environment variable is
+ specific to <command>centos-art.sh</command> script and
+ controls the working copy default location of &TCAR;. This is
+ the place in your workstation where &TCAR; file system is
+ stored for you to work with it.
+ </para>
+
+ <para>
+ By default, just after installing your workstation, this
+ variable will not be found in it and the
+ <command>centos-art.sh</command> script will finish its
+ execution with an error message if you try to execute it
+ without any argument. This behaviour is OK because the
+ <command>centos-art.sh</command> script doesn't know where you
+ stored the working copy of &TCAR; in your workstation. In
+ order for this variable to exist in your workstation you need
+ to configure your workstation first, as described in <xref
+ linkend="repo-ws-config" />.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>TCAR_BRAND</varname></term>
+ <listitem>
+ <para>
+ The <envar>TCAR_BRAND</envar> environment variable is specific
+ to <command>centos-art.sh</command> script and controls the
+ brand information that identifies the content produced inside
+ &TCAR;. The brand information is used to give name to some
+ files inside the repository (e.g., see files under <filename
+ class="directory">Identity/Models/Brands</filename>
+ directory).
+ </para>
+ <para>
+ By default, this variable takes <quote>centos</quote> as
+ value. In case you want to change it to something else, you
+ should consider the following implications:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The <command>centos-art.sh</command> script will no longer be
+ referred as such. Instead, the
+ <filename>${TCAR_BRAND}-art.sh</filename> name will be used.
+ This implies that you no longer are using the
+ <command>centos-art.sh</command> file we provide as part of
+ &TCAR; and won't be able to commit changes to it. However, if
+ you retain the same logic from
+ <command>centos-art.sh</command> script in
+ <filename>${TCAR_WORKDIR}-art.sh</filename>, you can use
+ common and specific functionalities provided by
+ <command>centos-art.sh</command> script and commit changes to
+ them.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The files stored under <filename
+ class="directory">Identity/Models/Brands</filename>
+ should be named using the value of
+ <literal>${TCAR_BRAND}</literal> as section. If you change
+ the value of this variable, you need to be sure the new value
+ set does coincide with the file names you use to store brand
+ information.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </sect2>
+
+ <sect2>
+ <title>The Command Environment</title>
+
+ <para>
+ The first file the <command>centos-art.sh</command> script
+ calls is the
+ <filename>Scripts/Bash/Functions/Commons/cli.sh</filename>
+ file. This file initializes all variables and functions you
+ will be able to use along the script execution environment
+ lifetime. Such environment variables are for internal use
+ inside the <command>centos-art.sh</command> script only and
+ users shouldn't modify them to customize the script in a
+ per-user level. Instead, to customize the script behaviour in
+ a per-user level, you need to make use of your personal
+ environment variables set in the
+ <filename>~/.bash_profile</filename> file.
+ </para>
+
+ <para>
+ Once environment variables are initialized, the
+ <command>centos-art.sh</command> script initializes common and
+ specific environment functions, in that order.
+ </para>
+
+ <sect3>
+ <title>Common Function Environment</title>
+
+ <para>
+ Common function environments are stored under <filename
+ class="directory">Scripts/Bash/Functions/Commons</filename>
+ directory and will be available always, both for common
+ environment functions themselves and specific environment
+ functions.
+ </para>
+
+ </sect3>
+
+ <sect3>
+ <title>Specific Function Environments</title>
+
+ <para>
+ Specific function environments, on the other hand, are stored
+ in the <filename
+ class="directory">Scripts/Bash/Functions/${CLI_FUNCDIRNAM}/${CLI_FUNCNAME}.sh</filename>
+ file, where:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><varname>CLI_FUNCDIRNAME</varname></term>
+ <listitem>
+ <para>
+ Is the first argument passed to
+ <command>centos-art.sh</command> script with the first letter
+ in uppercase but the rest in lowercase. For example,
+ <literal>Render</literal>, <literal>Locale</literal> and
+ <literal>Help</literal> are all possible values to this
+ variable.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>CLI_FUNCNAME</varname></term>
+ <listitem>
+ <para>
+ Is the first argument passed to
+ <command>centos-art.sh</command> script with all letters in
+ lowercase. For example, <literal>render</literal>,
+ <literal>locale</literal> and <literal>help</literal> are all
+ possible values to this variable.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>
+ Specific functions environment can be written in just one file
+ or in several files inside the same directory. Using one file
+ to write specific functions environment is rarely seen inside
+ the <command>centos-art.sh</command> script but it could
+ happen in situations where the need you want to solve can be
+ written in a few lines inside just one file. On the other
+ hand, if you find yourself writing a too long file, it is
+ convenient to logically divide it into several files. This
+ logical division takes place using functions, which indeed
+ create other environments where you can create and express
+ your solutions.
+ </para>
+
+ <para>
+ The order in which individual files are exported and executed
+ inside the specific functions environments depends in the way
+ each developer write the <filename
+ class="directory">Scripts/Bash/Functions/${CLI_FUNCDIRNAM}/${CLI_FUNCNAME}.sh</filename>
+ file. This is the main file inside the specific function
+ environment and controls the kind of logical division you
+ implement to organize the solution you need. As file name
+ convention, the following structure for new specific functions
+ environment is proposed:
+ </para>
+
+<programlisting>
+Scripts/Bash/Functions/${CLI_FUNCDIRNAM}/
+|-- ${CLI_FUNCNAME}.sh
+`-- ${CLI_FUNCNAME}_verbSubject.sh
+</programlisting>
+
+ <para>
+ Specific functions environment is exported after common
+ functions environment does, so it is not possible for specific
+ functions environment to be available inside the common
+ functions environment, nor inside other specific functions
+ environment, different to the one been passed as first
+ argument to the <command>centos-art.sh</command> script
+ command-line.<footnote>
+ <para>
+ Although, it is possible for you to call the
+ <command>centos-art.sh</command> script to itself
+ through the <function>cli_runFnEnvironment</function>
+ common function environment.
+ </para>
+ </footnote> In <xref
+ linkend="scripts-bash-environment-example1" />,
+ <function>render</function> is a specific function environment
+ while <function>cli_printMessage</function> and
+ <function>cli_getFilesList</function> are common function
+ environments.
+ </para>
+
+ <para>
+ Both specific and common function environments exist to
+ standardize frequent tasks inside &TCAR;. The following
+ sections will describe which these frequent tasks are and the
+ way they are standardized using specific and common function
+ environments.
+ </para>
+ </sect3>
+
+ </sect2>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/funref.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/funref.docbook
new file mode 100644
index 0000000..c67c159
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/funref.docbook
@@ -0,0 +1,1294 @@
+<sect1 id="scripts-bash-funref">
+
+ <title>Environment Functions Reference</title>
+
+ <para>
+ In addition to environment variables described above, the
+ centos-art.sh script makes available the following common
+ environment functions once it is executed:
+ </para>
+
+ <variablelist>
+
+ <varlistentry>
+ <term>
+ <cmdsynopsis>
+ <command id="cli_checkRepoDirSource" xreflabel="cli_checkRepoDirSource">cli_checkRepoDirSource
+ <indexterm type="common-function" zone="cli_checkRepoDirSource">
+ <primary>cli_checkRepoDirSource</primary>
+ </indexterm>
+ </command>
+ </cmdsynopsis>
+ </term>
+ <listitem>
+
+ <para>
+ The <function>cli_checkRepoDirSource</function> function
+ standardizes the path construction to directories inside it
+ the working copy, using absolute paths. This function
+ transforms relative paths passed as non-option arguments to
+ <command>centos-art.sh</command> script command-line into
+ absolute paths inside the working copy and verifies whether
+ they really exist as directories inside the working copy or
+ not. If the path provided doesn't exist as directory inside
+ the working copy, the script will finish its execution
+ immediately with an error message. Otherwise, if the directory
+ exists, the variable <varname>ACTIONVAL</varname> is redefined
+ with the related absolute path for further use.
+ </para>
+
+ <para>
+ Use the <function>cli_checkRepoDirSource</function> function
+ whenever you need to be sure that non-option arguments passed
+ to <command>centos-art.sh</command> script command-line will
+ always point to directories inside the working copy.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ <cmdsynopsis>
+ <command id="cli_expandTMarkers" xreflabel="cli_expandTMarkers">cli_expandTMarkers
+ <indexterm type="common-function" zone="cli_expandTMarkers">
+ <primary>cli_expandTMarkers</primary>
+ </indexterm>
+ </command>
+ <arg choice="req"><replaceable>LOCATION</replaceable></arg>
+ </cmdsynopsis>
+ </term>
+ <listitem>
+ <para>
+ The <function>cli_expandTMarkers</function> standardizes
+ construction of translation markers and their related
+ expansion. As convention, translation markers are set inside
+ source files (e.g., DocBook, SVG) and expanded inside temporal
+ instances used to produce final contents. The
+ <replaceable>LOCATION</replaceable> argument should point to
+ the temporal file where translation markers expansion takes
+ place in.
+ </para>
+ <para>
+ Translation markers written in source files must comply the
+ <literal>=[A-Z_]+=</literal> regular expression pattern. For
+ example, <literal>=UNKNOWN_MARKER=</literal> is a valid
+ translation marker without any replacement. To prevent
+ <command>centos-art.sh</command> script from expanding
+ translation markers, add a backslash (<literal>\</literal>)
+ between the first equal sign and the following letter. For
+ example, <literal>=\...=</literal> won't be expanded.
+ </para>
+ <para>
+ The <function>cli_expandTMarkers</function> supports the
+ following translation markers:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><literal>=\COPYRIGHT_YEAR_LAST=</literal></term>
+ <term><literal>=\COPYRIGHT_YEAR=</literal></term>
+ <listitem>
+ <para>
+ These translation markers expand to the last year used in
+ copyright notes. For example,
+ <literal>=COPYRIGHT_YEAR_LAST=</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\COPYRIGHT_YEAR_LIST=</literal></term>
+ <term><literal>=\COPYRIGHT_YEARS_LIST=</literal></term>
+ <listitem>
+ <para>
+ This translation markers expand to the list of years used in
+ copyright notes. For example,
+ <literal>=COPYRIGHT_YEARS_LIST=</literal>. The first year
+ represents the time we began to work on &TCAR;.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\COPYRIGHT_HOLDER=</literal></term>
+ <listitem>
+ <para>
+ This translation marker expands to the holder used in
+ copyright notes. For example,
+ <literal>=COPYRIGHT_HOLDER=</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\COPYRIGHT_HOLDER_PREDICATE=</literal></term>
+ <listitem>
+ <para>
+ This translation marker expands both the holder and the
+ predicate used in copyright notes. For example,
+ <literal>=COPYRIGHT_HOLDER_PREDICATE=</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\BRAND=</literal></term>
+ <listitem>
+ <para>
+ This translation marker expands to the brand name used on
+ files names and URLs inside &TCAR;. For example,
+ <literal>=BRAND=</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\LICENSE=</literal></term>
+ <listitem>
+ <para>
+ This translation marker expands to the license information
+ used in files created by <command>centos-art.sh</command>
+ script. For example, <literal>=LICENSE=</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\LICENSE_URL=</literal></term>
+ <listitem>
+ <para>
+ This translation marker expands to the license URL used in
+ files created by <command>centos-art.sh</command> script. For
+ example, <literal>=LICENSE_URL=</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\THEME=</literal></term>
+ <listitem>
+ <para>
+ This translation marker expands to the theme portion of path
+ you are producing through centos-art.sh script. As
+ consequence, this translation marker should be used in
+ situations where you are producing theme components only.
+ This translation marker expands its value by retrieving the
+ theme part of the path you provide as non-option argument to
+ <command>centos-art.sh</command> script. For example, if you
+ provide the path
+ <filename>Identity/Images/Themes/Modern/2/Distro/5</filename>,
+ this translation will expand to the
+ <literal>Modern/2/</literal> value.
+ </para>
+ <para>
+ In case you need to retrieve the theme name or version
+ separately one another, then you can use the
+ <literal>=\THEMENAME=</literal> and
+ <literal>=\THEMERELEASE=</literal> translation markers,
+ respectively. When you use these translation markers, forward
+ slashes are removed from result. So, if you provide the path
+ <filename>Identity/Images/Themes/Modern/2/Distro/5</filename>,
+ <literal>=\THEMENAME=</literal> will expand to
+ <literal>Modern</literal> and
+ <literal>=THEMERELEASE=</literal> will expand to
+ <literal>2</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\RELEASE=</literal></term>
+ <listitem>
+ <para>
+ This translation marker expands to the current release
+ information of your CentOS distribution. By default this
+ information is retrieved from
+ <filename>/etc/redhat-release</filename>. In case the option
+ <option>--release</option> be passed, the value specified with
+ it will overwrite the default value and will be this the one
+ used as section for this translation marker to retrieve the
+ release information. So, for example, if you are running a
+ CentOS-5.8 distribution and no <option>--release</option>
+ option is passed to <command>centos-art.sh</command> script,
+ this translation marker expands to <literal>5.8</literal>. On
+ the other hand, if you are still running a CentOS-5.8
+ distribution but provide the <option>--release=6.3</option>
+ option to <command>centos-art.sh</command> script, this
+ translation marker expands to <literal>6.3</literal> instead.
+ </para>
+ <para>
+ In case you need to retrieve minor and major release numbers
+ separately one another, then you can use the
+ <literal>=\MINOR_RELEASE=</literal> and
+ <literal>=\MAJOR_RELEASE=</literal> translation makers,
+ respectively.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\ARCH=</literal></term>
+ <listitem>
+ <para>
+ This translation marker expands to the current architecture of
+ your CentOS Distribution. By default this information is
+ retrieved from <command>uname -i</command>. In case the option
+ <option>--arch</option> be passed, the value specified with it
+ will overwrite the default value and will be the one used as
+ section. For example, if the <command>uname -i</command>
+ outputs the line <computeroutput>i386</computeroutput>, this
+ translation marker will expand to <literal>i386</literal>. On
+ the other hand, if you pass the <option>--arch=x86_64</option>
+ option to <command>centos-art.sh</command> script, this
+ translation marker will expand to <literal>x86_64</literal>
+ instead.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\URL=</literal></term>
+ <listitem>
+ <para>
+ This translation marker expands to the URL which points to
+ &TCP; home page. For example, <literal>=URL=</literal>. In
+ case you are using the centos-art.sh script in a different
+ locale but English (<literal>en_US.UTF-8</literal>), this
+ translation marker expands as usual but with the language
+ information appended to the end of the string. For example, if
+ you are executing the centos-art.shscript for Spanish locale
+ (e.g., <literal>es_ES.UTF-8</literal>), this translation
+ marker expands to <literal>=URL=es/</literal>.
+ </para>
+
+ <para>
+ In case you need to expand other URL related to &TCP; domain,
+ use translation markers described in <xref
+ linkend="scripts-bash-funref-expandTMarkers-Url" />. Likewise
+ =\URL=, translation markers described in <xref
+ linkend="scripts-bash-funref-expandTMarkers-Url" /> does
+ append the current language information to the end of the URL
+ string based on the locale information you are currently
+ executing the <command>centos-art.sh</command> script.
+ </para>
+
+ <table id="scripts-bash-funref-expandTMarkers-Url">
+ <title>URL-related translation markers</title>
+ <tgroup cols="2" align="left">
+ <thead>
+ <row>
+ <entry>Translation Marker</entry>
+ <entry>Expands To</entry>
+ </row>
+ </thead>
+
+ <tbody>
+ <row>
+ <entry><literal>=\URL_WIKI=</literal></entry>
+ <entry><literal>=URL_WIKI=</literal></entry>
+ </row>
+ <row>
+ <entry><literal>=\URL_LISTS=</literal></entry>
+ <entry><literal>=URL_LISTS=</literal></entry>
+ </row>
+ <row>
+ <entry><literal>=\URL_FORUMS=</literal></entry>
+ <entry><literal>=URL_FORUMS=</literal></entry>
+ </row>
+ <row>
+ <entry><literal>=\URL_MIRRORS=</literal></entry>
+ <entry><literal>=URL_MIRRORS=</literal></entry>
+ </row>
+ <row>
+ <entry><literal>=\URL_DOCS=</literal></entry>
+ <entry><literal>=URL_DOCS=</literal></entry>
+ </row>
+ <row>
+ <entry><literal>=\URL_PROJECTS=</literal></entry>
+ <entry><literal>=URL_PROJECTS=</literal></entry>
+ </row>
+ <row>
+ <entry><literal>=\URL_SVN=</literal></entry>
+ <entry><literal>=URL_SVN=</literal></entry>
+ </row>
+ <row>
+ <entry><literal>=\URL_TRAC=</literal></entry>
+ <entry><literal>=URL_TRAC=</literal></entry>
+ </row>
+ <row>
+ <entry><literal>=\URL_PLANET=</literal></entry>
+ <entry><literal>=URL_PLANET=</literal></entry>
+ </row>
+ </tbody>
+
+ </tgroup>
+ </table>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\MAIL_DOCS=</literal></term>
+ <listitem>
+ <para>
+ This translation marker expands to CentOS documentation
+ mailing list address. For example,
+ <literal>=MAIL_DOCS=</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\LOCALE=</literal></term>
+ <listitem>
+ <para>
+ This translation marker expands to the current locale
+ information used by <command>centos-art.sh</command> script.
+ This value is retrieved from the <envar>LANG</envar>
+ environment variable and should look like
+ <literal>=LOCALE=</literal>. In case you need to retrieve the
+ language and country part separately one another, you can use
+ the <literal>=\LOCALE_LL=</literal> and
+ <literal>=\LOCALE_CC=</literal>, respectively.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\REPO_TLDIR=</literal></term>
+ <listitem>
+ <para>
+ This translation marker expands to the absolute path to
+ <filename class="directory"></filename> directory inside
+ your workstation. For example,
+ <literal>/home/al/Projects/CentOS/artwork/trunk</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>=\REPO_HOME=</literal></term>
+ <term><literal>=\TCAR_WORKDIR=</literal></term>
+ <listitem>
+ <para>
+ This translation marker expands to the absolute path of your
+ working copy. For example,
+ <literal>/home/al/Projects/CentOS/artwork</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>
+ See also: <xref linkend="cli_getTemporalFile" />
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ <cmdsynopsis>
+ <command id="cli_exportFunctions" xreflabel="cli_exportFuncations">cli_exportFunctions
+ <indexterm type="common-function" zone="cli_exportFunctions">
+ <primary>cli_exportFunctions</primary>
+ </indexterm>
+ </command>
+ <arg choice="req"><replaceable>EXPORTID</replaceable></arg>
+ </cmdsynopsis>
+ </term>
+ <listitem>
+ <para>
+ The <function>cli_exportFunctions</function> function
+ standardizes the way specific functionalities are exported to
+ <command>centos-art.sh</command> script execution environment.
+ The <replaceable>EXPORTID</replaceable> argument points the
+ specific function initialization file relatively from
+ <filename>Scripts/Bash/Functions</filename> directory
+ on. For example, if we want to export the
+ <function>render</function> specific functionality, we use the
+ following construction:
+ </para>
+<programlisting>
+cli_exportFunctions "Render/render"
+</programlisting>
+ <para>
+ In this construction, <literal>Render</literal> with the first
+ letter in upper case is the name of the directory under
+ <filename
+ class="directory">Scripts/Bash/Functions</filename>
+ where the specific functionality is stored in, and
+ <literal>render</literal> with all letters in lower case is
+ the name of the specific functionality we want to export,
+ without its extension. This name is also used as suffix to
+ identify all files related to the specific functionality we
+ are exporting to <command>centos-art.sh</command> script
+ execution environment.
+ </para>
+
+ <para>
+ See also: <xref linkend="cli_unsetFunctions" />
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ <cmdsynopsis>
+ <command id="cli_getConfigLines" xreflabel="cli_getConfigLines">cli_getConfigLines
+ <indexterm type="cli_getConfigLines" zone="cli_getConfigLines">
+ <primary>cli_getConfigLines</primary>
+ </indexterm>
+ </command>
+ <arg choice="req"><replaceable>FILE</replaceable></arg>
+ <arg choice="req"><replaceable>SECTION</replaceable></arg>
+ <arg choice="req"><replaceable>OPTION</replaceable></arg>
+ </cmdsynopsis>
+ </term>
+ <listitem>
+ <para>
+ The <function>cli_getConfigLines</function> function
+ standardizes the way configuration lines are retrieved from
+ configuration files.
+ </para>
+
+ <para>
+ The <function>cli_getConfigLines</function> function accepts
+ the following arguments:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><replaceable>FILE</replaceable></term>
+ <listitem>
+ <para>
+ This argument specifies the absolute path to the configuration
+ file you want to retrieve configuration lines from. For
+ example,
+ <quote><filename>${TCAR_WORKDIR}/Identity/Models/Themes/Default/Distro/5/Anaconda/branding.conf</filename></quote>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><replaceable>SECTION</replaceable></term>
+ <listitem>
+ <para>
+ This argument specifies the name of the section you want to
+ retrieve configuration lines from. For example,
+ <quote>symbols</quote> without brackets.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><replaceable>OPTION</replaceable></term>
+ <listitem>
+ <para>
+ This argument specifies the name of the option related to the
+ configuration line you want to retrieve. For example,
+ <quote>anaconda_header.svgz</quote>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>
+ In order for <function>cli_getConfigLines</function> to work
+ properly, the configuration files must have a section line
+ with the form <literal>[sectionname]</literal> which groups
+ several <literal>option = "value"</literal> lines.
+ Lines beginning with <literal>#</literal> are ignored and can
+ be used for comments.
+ </para>
+
+ <example id="cli_getConfigLines-conffile">
+ <title>Configuration file used to produce Tcar-fs documentation manual</title>
+ <screenshot>
+ <screeninfo>Configuration used to produce Tcar-fs documentation manual</screeninfo>
+ <mediaobject>
+ <textobject>
+<programlisting>
+[main]
+
+# Specify documentation backend used by documentation manual.
+manual_format = "texinfo"
+
+# Specify title style used by sections inside the manual.
+manual_section_style = "directory"
+
+# Specify the order used by sections inside the manual.
+manual_section_order = "ordered"
+
+[templates]
+
+# Specify relation between template files and section definition files
+# inside the manual.
+Chapters/section-functions.texinfo = "^.+-functions-[[:alnum:]]+\.texinfo$"
+Chapters/section.texinfo = "^.+\.texinfo$"
+</programlisting>
+</textobject>
+</mediaobject>
+</screenshot>
+ </example>
+
+ <para>
+ The section names and option names used inside configuration
+ files can be anything. It depends on the use and
+ interpretation programmed inside
+ <command>centos-art.sh</command> script for specific purposes
+ which defines what kind of section and options must exist
+ inside a configuration file. For example, consider the
+ configuration files used by <function>render</function>
+ functionality. They follow the same structure used in
+ documentation configuration files but the meaning of their
+ sections and options change to fit the specific needs of
+ <function>render</function> functionality.
+ </para>
+
+ <example id="cli_getConfigLines-conffile-2">
+ <title>Configuration file used to produced Anaconda images</title>
+ <screenshot>
+ <screeninfo>Configuration used to produced Anaconda images</screeninfo>
+ <mediaobject>
+ <textobject>
+<programlisting>
+[types]
+
+anaconda_header.svgz = "Types/White/48/=\BRAND=-5.png:x48+20+20"
+first.svgz = "Types/White/32/=\BRAND=-5.png:x32+30+219"
+splash.svgz = "Types/White/48/=\BRAND=-5-msg.png:x48+30+138"
+
+[symbols]
+
+anaconda_header.svgz = "Symbols/48/=\BRAND=.png:x48+732+20"
+first.svgz = "Symbols/48/=\BRAND=.png:x48+30+20"
+splash.svgz = "Symbols/48/=\BRAND=.png:x48+30+20"
+</programlisting>
+</textobject>
+</mediaobject>
+</screenshot>
+ </example>
+
+ <para>
+ Use the <function>cli_getConfigLines</function> function when
+ you need to retrieve <literal>option = "value"</literal> lines
+ from configuration files in a controlled way.
+ </para>
+
+ <para>
+ See also: <xref linkend="cli_getConfigValue" />
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ <cmdsynopsis>
+ <command id="cli_getConfigValue" xreflabel="cli_getConfigValue">cli_getConfigValue
+ <indexterm type="common-function" zone="cli_getConfigValue">
+ <primary>cli_getConfigValue</primary>
+ </indexterm>
+ </command>
+ <arg choice="req"><replaceable>FILE</replaceable></arg>
+ <arg choice="req"><replaceable>SECTION</replaceable></arg>
+ <arg choice="req"><replaceable>OPTION</replaceable></arg>
+ </cmdsynopsis>
+ </term>
+ <listitem>
+ <para>
+ The <function>cli_getConfigValue</function> function
+ standardizes the way option values are retrieved from
+ configuration files. As convention,
+ <function>cli_getConfigValue</function> uses the output
+ produced by <function>cli_getConfigLines</function> as input
+ to retrieve the option values. As convention, in
+ <literal>option = "value"</literal> lines, the values
+ retrieved are always on the right side. The values retrieved
+ are also output without quotation and translation markers
+ already expanded.
+ </para>
+
+ <para>
+ The <function>cli_getConfigValue</function> function accepts
+ the following arguments:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><replaceable>FILE</replaceable></term>
+ <listitem>
+ <para>
+ This argument specifies the absolute path to the configuration
+ file you want to retrieve the value from. For example,
+ <quote><filename>${TCAR_WORKDIR}/Identity/Models/Themes/Default/Distro/5/Anaconda/branding.conf</filename></quote>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><replaceable>SECTION</replaceable></term>
+ <listitem>
+ <para>
+ This argument specifies the name of the section related to the
+ configuration line you want to retrieve the value from. For
+ example, <quote>symbols</quote> without brackets.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><replaceable>OPTION</replaceable></term>
+ <listitem>
+ <para>
+ This argument specifies the name of the option you want to
+ retrieve the value from. For example, in <xref
+ linkend="cli_getConfigLines-conffile-2" />, the
+ <quote><literal>anaconda_header.svgz</literal></quote> option will output the
+ <quote><literal>Symbols/48/=\BRAND=.png:x48+732+20</literal></quote> value
+ without quotation and translation markers expanded. So if the
+ value of <envar>TCAR_BRAND</envar> environment variable is
+ <quote><literal>centos</literal></quote>, the real value you
+ get will be
+ <quote><literal>Symbols/48/centos.png:x48+732+20</literal></quote>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>
+ Use the <function>cli_getConfigValue</function> function
+ whenever you want to retrieve values from configuration files
+ in a controlled way.
+ </para>
+
+ <para>
+ See also: <xref linkend="cli_getConfigLines" />
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ <cmdsynopsis>
+ <command id="cli_getFilesList" xreflabel="cli_getFilesList">cli_getFilesList
+ <indexterm type="common-function" zone="cli_getFilesList">
+ <primary>cli_getFilesList</primary>
+ </indexterm>
+ </command>
+ <arg choice="opt">--pattern</arg>
+ <arg choice="opt">--mindepth</arg>
+ <arg choice="opt">--maxdepth</arg>
+ <arg choice="opt">--type</arg>
+ <arg choice="opt">--uid</arg>
+ <arg choice="req" rep="repeat"><replaceable>LOCATION</replaceable></arg>
+ </cmdsynopsis>
+ </term>
+ <listitem>
+ <para>
+ The <function>cli_getFilesList</function> standardizes the way
+ list of files are built inside the
+ <command>centos-art.sh</command> script. This function outputs
+ a sorted and unique list of files based on the options and
+ location provided as argument. This function is an interface
+ to the <command>find</command> command. Don't use
+ <command>find</command> command directly inside the
+ centos-art.sh script. Instead, use the
+ <function>cli_getFilesList</function> function.
+ </para>
+ <para>
+ The <function>cli_getFilesList</function> accepts the
+ following arguments:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><replaceable>LOCATION</replaceable></term>
+ <listitem>
+ <para>
+ This arguments must be the absolute path to a directory and
+ specifies where the search of files in any form (e.g.,
+ directories, links, etc.) will take place in. If
+ <replaceable>LOCATION</replaceable> isn't a directory, the
+ script finishes its execution with an error message.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>
+ The <function>cli_getFilesList</function> accepts the
+ following options:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><option>--pattern="<replaceable>REGEX</replaceable>"</option></term>
+ <listitem>
+ <para>
+ This option specifies a posix-egrep type regular expression as
+ value. This regular expression is applied to path specified in
+ <replaceable>LOCATION</replaceable> argument. Only file paths
+ that match this regular expression inside
+ <replaceable>LOCATION</replaceable> directory will be included
+ in the final list of files. By default, if this option is not
+ provided, the
+ <quote><literal>^/.*[[:alnum:]_/-]+$</literal></quote> regular
+ expression is used.
+ </para>
+ <para>
+ When you use the <function>cli_getFilesList</function> you
+ don't need to specified the absolute path of files you want to
+ look for. This is something
+ <function>cli_getFilesList</function> already does for you.
+ When you use this function, the value you pass as regular
+ expression isn't the final regular expression used. Instead,
+ the regular expression you pass is used to build the final
+ regular expression passed to <command>find</command> command.
+ The final regular expression passed to find is
+ <quote><literal>^/.*${PATTERN}$</literal></quote>, where
+ <literal>${PATTERN}</literal> is the value you passed to
+ <option>--pattern</option> option as
+ <replaceable>REGEX</replaceable>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--mindepth="<replaceable>NUMBER</replaceable>"</option></term>
+ <listitem>
+ <para>
+ This option specifies the minimal
+ <replaceable>NUMBER</replaceable> of levels deep the search
+ should go under the directory
+ <replaceable>LOCATION</replaceable> specified. For example, if
+ you specify <option>--mindepth="2"</option> the search will
+ start two levels deep considering the path provided as
+ section.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--maxdepth="<replaceable>NUMBER</replaceable>"</option></term>
+ <listitem>
+ <para>
+ This option specifies the maximum
+ <replaceable>NUMBER</replaceable> of levels deep the search
+ should go under the directory
+ <replaceable>LOCATION</replaceable> specified. For example, if
+ you specify <option>--maxdepth="2"</option> the search will
+ begin in the very same directory path you provided as
+ <replaceable>LOCATION</replaceable> and stop two levels deep
+ using it as section.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--type="<replaceable>STRING</replaceable>"</option></term>
+ <listitem>
+ <para>
+ This option specifies the type of files being searched. This
+ option accepts the same values the <command>find</command>
+ <option>-type</option> option does. However, the following
+ <replaceable>STRING</replaceable> values are the most used
+ inside the script so far:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ d — directory.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ f — regular file.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--uid="<replaceable>NUMBER</replaceable>"</option></term>
+ <listitem>
+ <para>
+ This option specifies the numeric user id of the files you
+ want to search. Only files that match this numeric user id
+ will be added to the final list of files.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>
+ Use the <function>cli_getFilesList</function> whenever you
+ need to build list of files for further processing.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ <cmdsynopsis>
+ <command id="cli_getPathComponent" xreflabel="cli_getPathComponent">cli_getPathComponent
+ <indexterm type="common-function" zone="cli_getPathComponent">
+ <primary>cli_getPathComponent</primary>
+ </indexterm>
+ </command>
+ <arg>--release</arg>
+ <arg>--release-major</arg>
+ <arg>--release-minor</arg>
+ <arg>--release-pattern</arg>
+ <arg>--architecture</arg>
+ <arg>--architecture-pattern</arg>
+ <arg>--motif</arg>
+ <arg>--motif-name</arg>
+ <arg>--motif-release</arg>
+ <arg>--motif-pattern</arg>
+ <arg choice="req"><replaceable>PATH</replaceable></arg>
+ </cmdsynopsis>
+ </term>
+ <listitem>
+ <para>
+ ...
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ <cmdsynopsis>
+ <command id="cli_synchronizeRepoChanges" xreflabel="cli_synchronizeRepoChanges">cli_synchronizeRepoChanges
+ <indexterm type="common-function" zone="cli_synchronizeRepoChanges">
+ <primary>cli_syncronizeRepoChanges</primary>
+ </indexterm>
+ </command>
+ <arg choice="req"><replaceable>LOCATION</replaceable></arg>
+ </cmdsynopsis>
+ </term>
+ <listitem>
+ <para>
+ The <function>cli_synchronizeRepoChanges</function>
+ standardizes the way changes are synchronized between the
+ working copy and the central repository using
+ <replaceable>LOCATION</replaceable> as section. This
+ function is the interface we use inside the
+ <command>centos-art.sh</command> script to execute the
+ <function>Svn</function> functionality described in <xref
+ linkend="scripts-bash-vcs" />.
+ </para>
+ <para>
+ Use <function>cli_synchronizeRepoChanges</function> function
+ inside the <command>centos-art.sh</command> script whenever
+ you need to synchronize one or more changes at any
+ <replaceable>LOCATION</replaceable> inside the working copy.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ <cmdsynopsis>
+ <command id="cli_printMessage" xreflabel="cli_printMessage">cli_printMessage
+ <indexterm type="common-function" zone="cli_printMessage">
+ <primary>cli_printMessage</primary>
+ </indexterm>
+ </command>
+ <arg choice="req"><replaceable>MESSAGE</replaceable></arg>
+ <group choice="opt">
+ <arg>--as-separator-line</arg>
+ <arg>--as-banner-line</arg>
+ <arg>--as-cropping-line</arg>
+ <arg>--as-tuningup-line</arg>
+ <arg>--as-checking-line</arg>
+ <arg>--as-combining-line</arg>
+ <arg>--as-creating-line</arg>
+ <arg>--as-reading-line</arg>
+ <arg>--as-savedas-line</arg>
+ <arg>--as-linkto-line</arg>
+ <arg>--as-movedto-line</arg>
+ <arg>--as-validating-line</arg>
+ <arg>--as-template-line</arg>
+ <arg>--as-configuration-line</arg>
+ <arg>--as-palette-line</arg>
+ <arg>--as-reponse-line</arg>
+ <arg>--as-request-line</arg>
+ <arg>--as-selection-line</arg>
+ <arg>--as-error-line</arg>
+ <arg>--as-toknowmore-line</arg>
+ <arg>--as-yesornorequest-line</arg>
+ <arg>--as-notrailingnew-line</arg>
+ <arg>--as-stdout-line</arg>
+ <arg>--as-stderr-line</arg>
+ </group>
+ </cmdsynopsis>
+ </term>
+ <listitem>
+ <para>
+ The <function>cli_printMessage</function> function
+ standardizes the way centos-ar.sh scirpt prints messages. By
+ default, centos-art.sh script prints all messages to the
+ standard output with the exception of those messages printed
+ with the <option>--as-stderr-line</option> option, which are
+ printed to standard error output instead.
+ </para>
+
+ <para>
+ The <function>cli_printMessage</function> function requires
+ two arguments. The first argument specifies the
+ <replaceable>MESSAGE</replaceable> you want to print and the
+ second argument specifies the FORMAT you'll use to print that
+ message. Because this function is so used inside the
+ centos-art.sh script, it is convenient to provide localization
+ to strings passed as <replaceable>MESSAGE</replaceable> using
+ <command>gettext</command> contructions when they aren't
+ paths.
+ </para>
+
+ <para>
+ The <function>cli_printMessage</function> function accepts the
+ following formats as second argument:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><option>--as-separator-line</option></term>
+ <listitem>
+ <para>
+ This format takes the first character passed as
+ <replaceable>MESSAGE</replaceable> and repeats it horizontally
+ to build a separator line. Use this format whenever you need
+ to create a logical separation between different actions.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--as-banner-line</option></term>
+ <listitem>
+ <para>
+ This format takes the string passed as
+ <replaceable>MESSAGE</replaceable> and puts it inside two
+ horizontal separator lines. Use this format whenever you need
+ to print header information for following lines.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--as-cropping-line</option></term>
+ <listitem>
+ <para>
+ This format is for two columns messages where
+ <replaceable>MESSAGE</replaceable> generally refers to a file
+ inside the repository. Use this format whenever you need to
+ imply the fact that certain file has been cropped.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--as-tuningup-line</option></term>
+ <listitem>
+ <para>
+ This format is for two columns messages where
+ <replaceable>MESSAGE</replaceable>
+ generally refers to a file inside the repository. Use this
+ format whenever you need to imply the fact that certain file
+ has been tuned-up.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-checking-line</option></term>
+ <listitem>
+ <para>
+ This format is for two columns messages where
+ <replaceable>MESSAGE</replaceable> generally refers to a file
+ inside the repository. Use this format whenever you need to
+ imply the fact that certain file has been checked or verified
+ (e.g., through <function>cli_checkFiles</function>
+ functionality).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-combining-line</option></term>
+ <listitem>
+ <para>
+ This format is for two columns messages where
+ <replaceable>MESSAGE</replaceable> generally refers to a file
+ inside the repository. Use this format whenever you need to
+ imply the fact that certain file has been combined.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-creating-line</option></term>
+ <listitem>
+ <para>
+ This format is for two columns messages where
+ <replaceable>MESSAGE</replaceable> generally refers to a file
+ inside the repository. Use this format whenever you need to
+ imply the fact that certain file has been created.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-reading-line</option></term>
+ <listitem>
+ <para>
+ This format is for two columns messages where
+ <replaceable>MESSAGE</replaceable> generally refers to a file
+ inside the repository. Use this format whenever you need to
+ imply the fact that certain file has been read.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-savedas-line</option></term>
+ <listitem>
+ <para>
+ This format is for two columns messages where
+ <replaceable>MESSAGE</replaceable> generally refers to a file
+ inside the repository. Use this format whenever you need to
+ imply the fact that certain file has been saved.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-linkto-line</option></term>
+ <listitem>
+ <para>
+ This format is for two columns messages where
+ <replaceable>MESSAGE</replaceable> generally refers to a file
+ inside the repository. Use this format whenever you need to
+ imply the fact that certain file has been linked.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-movedto-line</option></term>
+ <listitem>
+ <para>
+ This format is for two columns messages where
+ <replaceable>MESSAGE</replaceable> generally refers to a file
+ inside the repository. Use this format whenever you need to
+ imply the fact that certain file has been moved.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-validating-line</option></term>
+ <listitem>
+ <para>
+ This format is for two columns messages where
+ <replaceable>MESSAGE</replaceable> generally refers to a file
+ inside the repository. Use this format whenever you need to
+ imply the fact that certain file has been validated.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-template-line</option></term>
+ <listitem>
+ <para>
+ This format is for two columns messages where
+ <replaceable>MESSAGE</replaceable> generally refers to a file
+ inside the repository. Use this format whenever you need to
+ imply the fact that certain file is a template or design
+ model.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-configuration-line</option></term>
+ <listitem>
+ <para>
+ This format is for two columns messages where
+ <replaceable>MESSAGE</replaceable> generally refers to a file
+ inside the repository. Use this format whenever you need to
+ imply the fact that certain file is a configuration file.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-palette-line</option></term>
+ <listitem>
+ <para>
+ This format is for two columns messages where
+ <replaceable>MESSAGE</replaceable> generally refers to a file
+ inside the repository. Use this format whenever you need to
+ imply the fact that certain file is a palette of colors.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-response-line</option></term>
+ <listitem>
+ <para>
+ This format adds <literal>--></literal> at the begining of the
+ string passed as <replaceable>MESSAGE</replaceable>. Use this
+ format whenever you need to imply the fact that certain file
+ is considered part of a response. For example, when you need
+ to express that a group of files will take ceratin action, you
+ can use this option to doing so.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-request-line</option></term>
+ <listitem>
+ <para>
+ This format prints <replaceable>MESSAGE</replaceable> without
+ trailing new line. Use this format whenever you need to imply
+ a question or yes or no request.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-selection-line</option></term>
+ <listitem>
+ <para>
+ This format uses each word in
+ <replaceable>MESSAGE</replaceable> as item of a selection
+ list. Use this format whenever you need to select one of the
+ items provided as <replaceable>MESSAGE</replaceable>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-error-line</option></term>
+ <listitem>
+ <para>
+ This format prints error messages produced by centos-art.sh
+ script. It uses the <command>caller</command> built-in command
+ to display the line number and the filename where such error
+ was triggered. Later, it prints where to find more information
+ by using the <option>--as-toknowmore-line</option> option.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>--as-toknowmore-line</option></term>
+ <listitem>
+ <para>
+ This format takes a function name as
+ <replaceable>MESSAGE</replaceable> and prints the command you
+ can use to find more information about it. When this option is
+ passed the script finishes its execution immediately. This
+ option is used in combination with
+ <option>--as-error-line</option> to finish the script
+ execution after an error.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--as-yesornorequest-line</option></term>
+ <listitem>
+ <para>
+ This format takes a question as
+ <replaceable>MESSAGE</replaceable> and reads a yes or no
+ answer. When answer is negative, the script finishes its
+ execution immediately. When answer is affirmative, the script
+ continues its execution normally.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--as-notrailingnew-line</option></term>
+ <listitem>
+ <para>
+ Print <replaceable>MESSAGE</replaceable> without any trailing
+ newline.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--as-stdout-line</option></term>
+ <listitem>
+ <para>
+ Print <replaceable>MESSAGE</replaceable> to standard output.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--as-stderr-line</option></term>
+ <listitem>
+ <para>
+ Print <replaceable>MESSAGE</replaceable> to standard error
+ output.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+ <para>
+ Use <function>cli_printMessage</function> function whenever
+ you need to print information inside the
+ <command>centos-art.sh</command> script.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ <cmdsynopsis>
+ <command id="cli_unsetFunctions" xreflabel="cli_unsetFunctions">cli_unsetFunctions
+ <indexterm type="common-function" zone="cli_unsetFunctions">
+ <primary>cli_unsetFunctions</primary>
+ </indexterm>
+ </command>
+ <arg choice="req"><replaceable>EXPORTID</replaceable></arg>
+ </cmdsynopsis>
+ </term>
+ <listitem>
+ <para>
+ ...
+ </para>
+ <para>
+ See also: <xref linkend="cli_exportFunctions" />
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ <cmdsynopsis>
+ <command id="cli_getTemporalFile" xreflabel="cli_getTemporalFile">cli_getTemporalFile
+ <indexterm type="common-function" zone="cli_unsetFunctions">
+ <primary>cli_unsetFunctions</primary>
+ </indexterm>
+ </command>
+ <arg choice="req"><replaceable>FILENAME</replaceable></arg>
+ </cmdsynopsis>
+ </term>
+ <listitem>
+ <para>
+ ...
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>...</term>
+ <listitem>
+ <para>
+ ...
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+
+</sect1>
+
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/help.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/help.docbook
new file mode 100644
index 0000000..8855021
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/help.docbook
@@ -0,0 +1,754 @@
+<refentry id="scripts-bash-help">
+
+ <refmeta>
+ <refentrytitle>help</refentrytitle>
+ <indexterm type="common-function">
+ <primary>Standardize constructions tasks inside &TCAR;</primary>
+ </indexterm>
+ </refmeta>
+
+ <refnamediv>
+ <refname>help</refname>
+ <refpurpose>Standardize documentation tasks inside &TCAR;.</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <cmdsynopsis>
+ <command>centos-art help</command>
+ <arg choice="opt">
+ <arg>-h|--help</arg>
+ <arg>-q|--quiet</arg>
+ <arg>--answer-yes</arg>
+ <arg>--synchronize</arg>
+ <arg>--format="<replaceable>KEYWORD</replaceable>"</arg>
+ <arg>--search="<replaceable>KEYWORD</replaceable>"</arg>
+ <arg>--edit</arg>
+ <arg>--read</arg>
+ <arg>--update-output</arg>
+ <arg>--update-structure</arg>
+ <arg>--copy</arg>
+ <arg>--delete</arg>
+ <arg>--rename</arg>
+ </arg>
+ <group choice="req">
+ <arg rep="repeat"><replaceable>MANUAL</replaceable>:<replaceable>PART</replaceable>:<replaceable>CHAPTER</replaceable>:<replaceable>SECTION</replaceable></arg>
+ <arg rep="repeat"><replaceable>LOCATION</replaceable></arg>
+ </group>
+ </cmdsynopsis>
+
+ </refsynopsisdiv>
+
+ <refsection id="scripts-bash-help-description">
+ <title>Description</title>
+
+ <para>
+ The <function>help</function> functionality exists to create
+ and maintain documentation manuals inside &TCAR;.
+ </para>
+
+ <refsection id="scripts-bash-help-description-docentry">
+ <title>Documentation Entries</title>
+ <para>
+ The documentation entry identifies the specific file you want
+ to work with inside a documentation manual. The help
+ functionality recognizes documentation entries in the
+ following formats:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Path style</term>
+ <listitem>
+ <para>
+ This format uses paths to represent the documentation entries
+ you want to work with. This format assumes you are using the
+ first path component as chapter and the rest of the path as
+ section identifier both inside <quote>tcar-fs</quote>
+ documentation manual as parent documentation structure. The
+ field related to the part sectioning structure in the
+ documentation entry (the second field) is assumed empty, as
+ well. For example, if you want to document the directory
+ <quote><filename
+ class="directory">Scripts/Bash/Functions/Help</filename></quote>,
+ then you can do it with the following command:
+ </para>
+
+ <cmdsynopsis>
+ <command>centos-art help --edit Scripts/Bash/Functions/Help</command>
+ </cmdsynopsis>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Colon style</term>
+ <listitem>
+ <para>
+ This format uses colons to represent the documentation entries
+ you want to work with. In this format, the whole documentation
+ entry is divided in fields using colon as separator character.
+ Documentation entries written this way use each field to
+ specify manual, part, chapter and section identifiers (in this
+ order). The section identifier can use a path style or hyphen
+ style to separate
+ components. For example, if you want to document the directory
+ <quote><filename
+ class="directory">Scripts/Bash/Functions/Help</filename></quote>,
+ then you can do it with any of the following commands:
+ </para>
+
+ <cmdsynopsis>
+ <command>centos-art help --edit tcar-fs::trunk:Scripts/Bash/Functions/Help</command>
+ <command>centos-art help --edit tcar-fs::trunk:scripts-bash-functions-help</command>
+ </cmdsynopsis>
+
+ <para>
+ The documentation manual name specified in the first field of
+ a colon style documentation entry, must match the name the
+ name of the directory where the documentation manual is stored
+ in. By default documentation manuals are written in
+ Documentation/Models/Texinfo or
+ Documentation/Models/Docbook directories, based on
+ whether they are written in Texinfo or Docbook documentation
+ format.
+ </para>
+ <para>
+ The match relation between the manual name you provide in the
+ documentation entry and the related directory name inside
+ &TCAR; is case insensitive. The same is true for all other
+ documentation entry fields.
+ </para>
+
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>
+ From these documentation entry formats, the colon style
+ provides more flexibility than path style does. You can use
+ documentation entries written in colon style to create and
+ maintain different documentation manuals, including the
+ <quote>tcar-fs</quote> documentation manual. This is something
+ you cannot do with documentation entries written in path style
+ because they confine all documentation actions to
+ <quote>tcar-fs</quote> documentation manual.
+ </para>
+ </refsection>
+
+ </refsection>
+
+ <refsection id="scripts-bash-help-options">
+ <title>Options</title>
+ <para>
+ The <command>centos-art help</command> command accepts common
+ options described in <xref
+ linkend="scripts-bash-cliref-options" /> and the following
+ specific options:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><option>--answer-yes</option></term>
+ <listitem>
+ <para>
+ Assume <emphasis>yes</emphasis> to all confirmation requests.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--synchronize</option></term>
+ <listitem>
+ <para>
+ Synchronizes available changes between the working copy and
+ the central repository.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--format="<replaceable>KEYWORD</replaceable>"</option></term>
+ <listitem>
+ <para>
+ Specifies the format of documentation entry source file. This
+ information is used as reference to build the absolute path of
+ documentation entry, so you always have to provide it in order
+ to reach the documentation entry you want to work with.
+ Possible values for this option are shown in <xref
+ linkend="scripts-bash-help-supportedformats" />. When none of
+ these values is passed as format, Texinfo is used as default
+ format.
+ </para>
+
+ <table id="scripts-bash-help-supportedformats">
+ <title>Documentation formats</title>
+ <tgroup cols="3" align="left">
+ <thead>
+ <row>
+ <entry>Keyword</entry>
+ <entry>Description</entry>
+ <entry>Supported</entry>
+ </row>
+ </thead>
+
+ <tbody>
+ <row>
+ <entry><literal>texinfo</literal></entry>
+ <entry><xref linkend="manuals-formats-texinfo"/></entry>
+ <entry>Yes</entry>
+ </row>
+ <row>
+ <entry><literal>docbook</literal></entry>
+ <entry><xref linkend="manuals-formats-docbook"/></entry>
+ <entry>No</entry>
+ </row>
+ <row>
+ <entry><literal>latex</literal></entry>
+ <entry><xref linkend="manuals-formats-latex"/></entry>
+ <entry>No</entry>
+ </row>
+ <row>
+ <entry><literal>linuxdoc</literal></entry>
+ <entry>...</entry>
+ <entry>No</entry>
+ </row>
+ </tbody>
+
+ </tgroup>
+ </table>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--search="<replaceable>KEYWORD</replaceable>"</option></term>
+ <listitem>
+ <para>
+ Looks for documentation entries that match the
+ <replaceable>KEYWORD</replaceable> specified as value and
+ display them one by one in the order they were found. The way
+ each documentation entry is presented to you depends on the
+ documentation format the related documentation manual was
+ written on.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--edit</option></term>
+ <listitem>
+ <para>
+ Edit the documentation entry provided as argument. The
+ edition itself takes place through your default text editor
+ (e.g., the one you specified in the <envar>EDITOR</envar>
+ environment variable) one file at a time (i.e., the queue of
+ files to edit is not loaded in the text editor.).
+ </para>
+ <para>
+ When parent components inside documentation entries doesn't
+ exist (e.g., you try to create a section for a documentation
+ manual that doesn't exist), the <function>help</function>
+ functionality will create all documentation parent structures
+ considering the documentation format constraints and the
+ following document structure hierarchy order: documentation
+ <quote>manual</quote> first, <quote>parts</quote> second,
+ <quote>chapters</quote> third and <quote>sections</quote>
+ lastly.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--read</option></term>
+ <listitem>
+ <para>
+ Read the documentation entry provided as argument. This
+ option is used internally by <command>centos-art.sh</command>
+ script to refer documentation based on errors, so you can know
+ more about them and the causes that could have provoked them.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--update-output</option></term>
+ <listitem>
+ <para>
+ Update output files rexporting them from the specified backend
+ source files.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--update-structure</option></term>
+ <listitem>
+ <para>
+ Update document structure (e.g., cross references, menus,
+ nodes, etc.) and should be passed with a section as
+ documentation entry.
+ </para>
+ <para>
+ This option should be used whenever a document structure
+ changes (e.g., documentation entries are added, copied,
+ renamed, deleted, etc.). This option grantees the document
+ integrity and should be run before updating documentation
+ manual final output files.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--copy</option></term>
+ <listitem>
+ <para>
+ Duplicate documentation entries inside the working copy using
+ version control.
+ </para>
+ <para>
+ When you duplicate documentation entries through this option,
+ you should pass only two documentation entries in the command
+ line. The first one is considered the source location and
+ should point to a file under version control inside the
+ working copy. The second one is considered the target location
+ and should point either to the same structural level the
+ source points to or a direct parent level based on source
+ location, as described below.
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term>
+ "<replaceable>manual:part:chapter:section1</replaceable>" "<replaceable>manual:part:chapter:section2</replaceable>"</term>
+ <listitem>
+ <para>
+ Duplicates <replaceable>section1</replaceable> as
+ <replaceable>section2</replaceable> inside the same
+ <replaceable>chapter</replaceable>,
+ <replaceable>part</replaceable> and
+ <replaceable>manual</replaceable>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ "<replaceable>manual:part:chapter1:</replaceable>" "<replaceable>manual:part:chapter2:</replaceable>"</term>
+ <listitem>
+ <para>
+ Duplicates <replaceable>chapter1</replaceable> as
+ <replaceable>chapter2</replaceable> inside the same
+ <replaceable>part</replaceable> and
+ <replaceable>manual</replaceable>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ "<replaceable>manual:part1::</replaceable>" "<replaceable>manual:part2::</replaceable>"</term>
+ <listitem>
+ <para>
+ Duplicates <replaceable>part1</replaceable> as
+ <replaceable>part2</replaceable> inside the same
+ <replaceable>manual</replaceable>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ "<replaceable>manual1:::</replaceable>" "<replaceable>manual2:::</replaceable>"</term>
+ <listitem>
+ <para>
+ Duplicates <replaceable>manual1</replaceable> as
+ <replaceable>manual2</replaceable> inside <filename
+ class="directory">Documentation/Models/${FLAG_FORMAT}/</filename>
+ directory, where ${FLAG_FORMAT} is the name of the format
+ passed as option with the first letter in uppercase and the
+ rest in lowercase.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>
+ When you copy documentation entries through this option, all
+ structuring sections inside the one copied will be also
+ copied. For example, if you copy a documentation manual that
+ is made of parts, chapters and sections, the duplicated manual
+ will contain all those parts, chapters and sections, as well.
+ The same is true for lower sectioning structures. Thus, you
+ can be more specific in the documentation entry by reducing
+ the amount of content to duplicate.
+ </para>
+
+ <para>
+ When you copy documentation entries through this option, you
+ do it using documentation entries in the same structural level
+ only. This option doesn't support copying documentation
+ entries from differnet structural levels. For example, you
+ cannot copy one section to a chapter different from that the
+ source section you specified belongs to. The same applies to
+ chapters, and parts.
+ </para>
+
+ <para>
+ When you copy documentation entries through this option, the
+ source documentation entry you specify must not contain
+ pending changes. Otherwise, the target section won't be
+ created and the script will immediatly stop its execution with
+ a <quote>The source location has pending changes.</quote>
+ error message.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--delete</option></term>
+ <listitem>
+ <para>
+ Delete documentation entries. It is possible to delete more
+ than one documentation entry by specifying several
+ documentation entries in the command line.
+ </para>
+ <para>
+ When you delete documentation entries, you can pass any number
+ of documentation entries as argument. The documentation
+ entries you provide will be processed one by one.
+ </para>
+ <para>
+ When you delete a documentation entry from a documentation
+ manual, all cross references pointing to the deleted
+ documentation entry will be transformed into something
+ different to point out the fact that the related documentation
+ entry has been removed from the documentation manual and
+ restored back if you create the deleted section again. The
+ purpose of this is to keep the documentation manual structure
+ in a consistent state.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--rename</option></term>
+ <listitem>
+ <para>
+ Rename documentation entries inside the working copy. This
+ option copies the source documentation entry to its target
+ location, removes the source documentation entry, and restores
+ removed cross references renaming them to point the specified
+ target documentation entry.
+ </para>
+ <para>
+ When you rename documentation entries, it is required to pass
+ only two non-option parameters to the command-line. The first
+ non-option parameter is considered the source location and the
+ second one the target location. Both source location and
+ target location must point to a directory under version
+ control inside the working copy.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </refsection>
+
+ <refsection id="scripts-bash-help-examples">
+ <title>Examples</title>
+
+ <para>
+ This section describes, using examples, the procedure you
+ should follow to manage documentation manuals through
+ <function>help</function> functionality inside &TCAR;. To
+ better understand the procedure to follow, it describes a
+ hypothetical documentation scenario and the related commands
+ and outputs you may go through in order to complete specific
+ documentation tasks successfully.
+ </para>
+
+ <refsection id="scripts-bash-help-description-create">
+ <title>Creating Document Structures</title>
+ <para>
+ To create new documentation manuals inside &TCAR; you need to
+ provide both <option>--edit</option> and
+ <option>--format</option> options as well as a documentation
+ entry in the form <quote><literal>manual:::</literal></quote>
+ to the <function>help</function> functionality.
+ </para>
+
+ <para>
+ For example, consider a scenario where you need to create a
+ documentation manual in texinfo format to describe different
+ maintenance tasks you need to realized in order to keep your
+ pets happy. We'll name such manual <quote>My Zoo</quote>. It
+ will use chapters to organize each different kind of pets you
+ have. Inside chapters, sections will have the pet's name as
+ their own name to describe each pet's requirements, schedules,
+ and so on. To create such documentation manual, run the
+ following command:
+ </para>
+
+ <cmdsynopsis>
+ <command>centos-art help --edit --format="texinfo" "myzoo:::"</command>
+ </cmdsynopsis>
+
+ <para>
+ In case such documentation manual doesn't exist in the
+ <filename
+ class="directory">Docuementation/Models/Texinfo/</filename>
+ directory, this command will produce the following output:
+ </para>
+
+<programlisting>
+The following documentation manual doesn't exist:
+--> Documentation/Models/Texinfo/Myzoo/en_US/myzoo.texinfo
+Do you want to create it now? [yes/no]: yes
+Enter manual's title: My Zoo
+Enter manual's subtitle: Reference
+Enter manual's abstract: This manual describes my zoo maintenance tasks.
+Creating Documentation/Models/Texinfo/Myzoo
+Creating Documentation/Models/Texinfo/Myzoo/en_US
+Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo.conf
+Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-index.texinfo
+Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-menu.texinfo
+Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-nodes.texinfo
+Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo.texinfo
+Creating Documentation/Models/Texinfo/Myzoo/en_US/Licenses/chapter-menu.texinfo
+Creating Documentation/Models/Texinfo/Myzoo/en_US/Licenses/chapter-nodes.texinfo
+Creating Documentation/Models/Texinfo/Myzoo/en_US/Licenses/chapter.texinfo
+Updating Documentation/Models/Texinfo/Myzoo/en_US/myzoo.texinfo
+Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2
+Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2
+Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml
+Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook
+Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf
+Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2
+</programlisting>
+
+ <para>
+ Once the documentation structure has been created this way,
+ the recently created documentation manual is ready to receive
+ new sectioning levels (e.g., parts, chapters, sections, etc.).
+ For example, to create a new chapter named
+ <quote>Turtles</quote> inside <quote>My Zoo</quote>
+ documentation manual, run the following command:
+ </para>
+
+ <cmdsynopsis>
+ <command>centos-art help --edit --format="texinfo" "myzoo::turtles:"</command>
+ </cmdsynopsis>
+
+<programlisting>
+The following documentation chapter doesn't exist:
+--> Documentation/Models/Texinfo/Myzoo/en_US/Turtles
+Do you want to create it now? [yes/no]: yes
+Enter chapter's title: Turtles
+Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles
+Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter-menu.texinfo
+Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter-nodes.texinfo
+Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter.texinfo
+Updating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-menu.texinfo
+Updating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-nodes.texinfo
+Updating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter.texinfo
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2
+</programlisting>
+
+ <para>
+ Once chapters have been created it is possible to create
+ sections inside them. For example, if you want to create a
+ section for describing the life of a turtle named Longneck,
+ run the following command:
+ </para>
+
+ <cmdsynopsis>
+ <command>centos-art help --edit --format="texinfo" "myzoo::turtles:longneck"</command>
+ </cmdsynopsis>
+
+<programlisting>
+The following documentation section doesn't exist:
+--> Documentation/Models/Texinfo/Myzoo/en_US/Turtles/longneck.texinfo
+Do you want to create it now? [yes/no]: yes
+Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/longneck.texinfo
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2
+</programlisting>
+
+ </refsection>
+
+ <refsection id="scripts-bash-help-description-edit">
+ <title>Editing Document Structures</title>
+ <para>
+ To edit documentation entries you can follow the same
+ procedure described above. Just keep in mind the following
+ rules:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ When the entry you want to edit already exist it will be
+ edited.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When the entry you want to edit doesn't exist it will be created
+ first and edited later.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </refsection>
+
+ <refsection id="scripts-bash-help-description-copy">
+ <title>Copying Document Structures</title>
+ <para>
+ Consider a new turtle named Slowfeet has arrived to your home
+ and you want to duplicate Longneck's section for it (they both
+ are turtles and have similar requirements, squedules, etc.).
+ To copy documentation entries you use the
+ <option>--copy</option> option with two documentation entries,
+ where the first one is the source location and the second one
+ the target location. To do this, run the following command:
+ </para>
+
+ <cmdsynopsis>
+ <command>centos-art help --copy --format="texinfo" "myzoo::turtles:longneck" "myzoo::turtles:slowfeet"</command>
+ </cmdsynopsis>
+
+<programlisting>
+Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/slowfeet.texinfo
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf
+Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2
+</programlisting>
+
+ </refsection>
+
+ <refsection id="scripts-bash-help-description-rename">
+ <title>Renaming Document Structures</title>
+ <para>
+ Consider you've created the section of Longneck turtle using
+ the following documentation entry format
+ <quote>myzoo::turtles:longnek</quote>, but you didn't notice
+ the typo in it. You've made cross references to the misspelled
+ section in a few pages inside the <quote>My Zoo</quote>
+ documentation manual and some time later you realize the
+ section name has a spelling problem. To fix such a problem
+ you can rename the misspelled section with the correct one
+ running the following command:
+ </para>
+
+ <cmdsynopsis>
+ <command>centos-art help --rename --format="texinfo" "myzoo::turtles:longnek" "myzoo::turtles:longneck"</command>
+ </cmdsynopsis>
+
+<programlisting>
+Creating Documentation/Models/Texinfo/MyZoo/en_US/Turtles/longneck.texinfo
+Deleting Documentation/Models/Texinfo/MyZoo/en_US/Turtles/longnek.texinfo
+Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.info.bz2
+Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xhtml.tar.bz2
+Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xml
+Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.docbook
+Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.pdf
+Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.txt.bz2
+</programlisting>
+
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-help-description-delete">
+ <title>Deleting Document Structures</title>
+ <para>
+ Consider you gift the turtle named Longneck to a friend and
+ you want to delete its section from the <quote>My Zoo</quote>
+ documentation manual. To do so, run the following command:
+ </para>
+ <cmdsynopsis>
+ <command>centos-art help --delete --format="texinfo" "myzoo::turtles:longneck"</command>
+ </cmdsynopsis>
+<programlisting>
+Deleting Documentation/Models/Texinfo/Myzoo/en_US/Turtles/longneck.texinfo
+Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.info.bz2
+Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xhtml.tar.bz2
+Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xml
+Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.docbook
+Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.pdf
+Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.txt.bz2
+</programlisting>
+
+ </refsection>
+
+ </refsection>
+
+ <refsection id="scripts-bash-help-bugs">
+ <title>Bugs</title>
+ <para>
+ To report bugs related to this function, please create a new
+ ticket <ulink
+ url="https://projects.centos.org/trac/artwork/newticket?summary=Error%20Standardizing%20Documentation%20Tasks&component=Scripts">here</ulink>
+ refering the specific problems you found in it. For example,
+ it would be useful if you copy and paste any error output from
+ <command>centos-art.sh</command> script.
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-help-authors">
+ <title>Authors</title>
+ <para>
+ The following people have worked in this functionality:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Alain Reguera Delgado <<ulink url="mailto:alain.reguera@gmail.com">alain.reguera@gmail.com</ulink>>, =COPYRIGHT_YEAR_LIST=
+ </para>
+ </listitem>
+ </itemizedlist>
+ </refsection>
+
+ <refsection id="scripts-bash-help-licence">
+ <title>License</title>
+
+ <para>
+ Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ </refsection>
+
+</refentry>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/intro.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/intro.docbook
new file mode 100644
index 0000000..bf64c16
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/intro.docbook
@@ -0,0 +1,6 @@
+<para>
+ This reference covers the <command>centos-art.sh</command> script
+ mission, name convenctions, command-line interface and execution
+ environments. You can use this reference to understand how the
+ <command>centos-art.sh</command> script works.
+</para>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/locale.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/locale.docbook
new file mode 100644
index 0000000..21a37d9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/locale.docbook
@@ -0,0 +1,292 @@
+<refentry id="scripts-bash-locale">
+
+ <refmeta>
+ <refentrytitle>locale</refentrytitle>
+ <indexterm type="specific-function">
+ <primary>Standardize translation tasks inside &TCAR;</primary>
+ </indexterm>
+ </refmeta>
+
+ <refnamediv>
+ <refname>locale</refname>
+ <refpurpose>Standardize translation tasks inside &TCAR;</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <para>
+ The <varname>DIRECTORY</varname> parameter specifies the
+ directory path, inside the working copy of &TCAR;, where the
+ files you want to process are stored in. This paramter can be
+ provided more than once in order to process more than one
+ directory path in a single command execution. When this
+ parameter is not provided, the current directory path where
+ the command was called from is used instead.
+ </para>
+ </refsynopsisdiv>
+
+ <refsection id="scripts-bash-locale-options">
+ <title>Options</title>
+ <para>
+ The <function>locale</function> functionality accepts the
+ following options:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><option>--quiet</option></term>
+ <listitem>
+ <para>
+ Supress all output messages except error messages. When this
+ option is passed, all confirmation requests are supressed and
+ a possitive answer is assumed for them, just as if the
+ <option>--answer-yes</option> option would have been provided.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--answer-yes</option></term>
+ <listitem>
+ <para>
+ Assume <emphasis>yes</emphasis> to all confirmation requests.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--filter="REGEX"</option></term>
+ <listitem>
+ <para>
+ Reduce the list of files to process inside
+ <varname>DIRECTORY</varname> using <varname>REGEX</varname> as
+ pattern. You can use this option to control the amount of
+ files you want to locale. The deeper you go into the
+ directory structure the more specific you'll be about the
+ files you want to locale. When you cannot go deeper into the
+ directory structure through <varname>DIRECTORY</varname>
+ specification, use this option to reduce the list of files
+ therein.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--synchronize</option></term>
+ <listitem>
+ <para>
+ Synchronizes available changes between the working copy and
+ the central repository.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--update</option></term>
+ <listitem>
+ <para>
+ This option updates both POT and PO files related to source
+ files. Use this option everytime you change translatable
+ strings inside the source files.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--edit</option></term>
+ <listitem>
+ <para>
+ This option edits the portable object related to source files.
+ When you provide this option, your default text editor is used
+ to open the portable object you, as translator, need to change
+ in order to keep source file messages consistent with their
+ localized versions. In the very specific case of shell
+ scripts localization, this option takes care of updating the
+ machine object (MO) file the shell script requires to
+ displayed translation messages correctly when it is executed.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--delete</option></term>
+ <listitem>
+ <para>
+ This option unlocalizes source files. When you provide this
+ option, the localization directory related to source files is
+ removed from the working copy in conjunction with all portable
+ objects and machine objects inside it.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--dont-create-mo</option></term>
+ <listitem>
+ <para>
+ This option suppresses machine objects creation when shell
+ scripts are localized.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+ </refsection>
+
+ <refsection id="scripts-bash-locale-description">
+ <title>Description</title>
+
+ <para>
+ The localization process is very tied to the source files we
+ want to provide localized messages for. Inside the working
+ copy of &TCAR; it is possible to localize XML-based files
+ (e.g., SVG and Docbook) and programs written in most popular
+ programming languages (e.g., C, C++, C#, Shell Scripts,
+ Python, Java, GNU awk, PHP, etc.).
+ </para>
+
+ <para>
+ The localization process initiates by retriving translatable
+ strings from source files. When source files are XML-based
+ files, the only requisite to retrive translatable strings
+ correctly is that they be well-formed. Beyond that, the
+ <command>xml2po</command> command takes care of everything
+ else. When source files are Shell script files, it is
+ necessary that you previously define what strings inside the
+ script are considered as translatable strings in order for
+ <command>xgettext</command> command to retrive them correctly.
+ To define translatable strings inside shell scripts, you need
+ to use either <command>gettext</command>,
+ <command>ngettext</command>, <command>eval_gettext</command>
+ or <command>eval_ngettext</command> command as it is following
+ described:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use the <command>gettext</command> command to display the
+ native language translation of a textual message.
+ </para>
+ <screen>MESSAGE="`gettext "There is no entry to create."`"</screen>
+ </listitem>
+
+ <listitem>
+ <para>
+ Use the <command>ngettext</command> command to display the
+ native language translation of a textual message whose
+ grammatical form depends on a number.
+ </para>
+ <screen>MESSAGE="`ngettext "The following entry will be created" \
+ "The following entries will be created" \
+ $COUNT`:"</screen>
+ </listitem>
+
+ <listitem>
+ <para>
+ Use the <command>eval_gettext</command> command to display the
+ native language translation of a textual message, performing
+ dollar-substitution on the result. Note that only shell
+ variables mentioned in the message will be dollar-substituted
+ in the result.
+ </para>
+ <screen>MESSAGE="`eval_gettext "The location \\\"\\\$LOCATION\\\" is not valid."`"</screen>
+ </listitem>
+
+ <listitem>
+ <para>
+ Use the <command>eval_ngettext</command> command to display
+ the native language translation of a textual message whose
+ grammatical form depends on a number, performing
+ dollar-substitution on the result. Note that only shell
+ variables mentioned in messages will be dollar-substituted in
+ the result.
+ </para>
+ <screen>MESSAGE="`eval_ngettext "The following entry will be created in \\\$LOCATION" \
+ "The following entries will be created in \\\$LOCATION" \
+ $COUNT`:"</screen>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ Once translatable strings are retrived, a portable object
+ template (POT) file is created for storing them. Later, the
+ POT file is used to create a portable object (PO). The
+ portable object is the place where localization itself takes
+ place, it is the file translators edit to localize messages.
+ When translatable strings change inside source files, it is
+ necessary that you update these POT and PO files in order to
+ keep consistency between source file messages and their
+ localized versions.
+ </para>
+
+ <para>
+ Inside source files, translatable strings are always written
+ in English language. In order to localize translatable strings
+ from English language to another language, you need to be sure
+ the <envar>LANG</envar> environment variable has been already
+ set to the locale code you want to localize message for or see
+ them printed out before running the
+ <function>locale</function> functionality of
+ <command>centos-art.sh</command> script. Localizing English
+ language to itself is not supported.
+ </para>
+
+ <para>
+ To have a list of all locale codes you can have localized
+ messages for, run the following command: <command>locale -a |
+ less</command>.
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-locale-environment">
+ <title>Function Specific Environment</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-locale-authors">
+ <title>Authors</title>
+ <para>
+ The following people have worked in the
+ <function>locale</function> functionality:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Alain Reguera Delgado <<ulink url="mailto:alain.reguera@gmail.com">alain.reguera@gmail.com</ulink>>, =COPYRIGHT_YEAR_LIST=
+ </para>
+ </listitem>
+ </itemizedlist>
+ </refsection>
+
+ <refsection id="scripts-bash-locale-licence">
+ <title>License</title>
+
+ <para>
+ Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ </refsection>
+
+</refentry>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/mission.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/mission.docbook
new file mode 100644
index 0000000..283781e
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/mission.docbook
@@ -0,0 +1,9 @@
+<sect1 id="scripts-bash-mission">
+<title>Mission</title>
+
+<para>
+ The <command>centos-art.sh</command> script exists to automate
+ frequent tasks inside &TCAR;.
+</para>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/nameconvs.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/nameconvs.docbook
new file mode 100644
index 0000000..a041b3a
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/nameconvs.docbook
@@ -0,0 +1,54 @@
+<sect1 id="scripts-bash-nameconvs">
+
+ <title>Convenctions</title>
+
+ <para>
+ ...
+ </para>
+
+ <sect2 id="scripts-bash-nameconvs-vars">
+ <title>Variable Names</title>
+ <para>
+ ...
+ </para>
+ </sect2>
+
+ <sect2 id="scripts-bash-nameconvs-funcs">
+ <title>Function Names</title>
+ <para>
+ ...
+ </para>
+ </sect2>
+
+ <sect2 id="scripts-bash-nameconvs-exitstatus">
+ <title>Exit Status</title>
+ <para>
+ The <command>centos-art.sh</command> script has the following
+ exit status:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <code>0</code> — The script completed successfully
+ without error.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <code>1</code> — The script didn't complete successfully
+ because something went wrong. This error status is generally
+ produced by <function>cli_printMessage</function>
+ functionality, when you use it with the
+ <option>--as-error-line</option> option as second argument.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ ...
+ </para>
+ </sect2>
+
+</sect1>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/pack.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/pack.docbook
new file mode 100755
index 0000000..01c5937
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/pack.docbook
@@ -0,0 +1,82 @@
+<refentry id="scripts-bash-pack">
+
+ <refmeta>
+ <refentrytitle>pack</refentrytitle>
+ <indexterm type="specific-function">
+ <primary>Standardize packing tasks inside &TCAR;</primary>
+ </indexterm>
+ </refmeta>
+
+ <refnamediv>
+ <refname>pack</refname>
+ <refpurpose>Standardize packing tasks inside &TCAR;</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <para>
+ ...
+ </para>
+ </refsynopsisdiv>
+
+ <refsection id="scripts-bash-pack-description">
+ <title>Description</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-pack-usage">
+ <title>Usage</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-pack-environment">
+ <title>Function Specific Environment</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-pack-authors">
+ <title>Authors</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ ...
+ </para>
+ </listitem>
+ </itemizedlist>
+ </refsection>
+
+ <refsection id="scripts-bash-pack-licence">
+ <title>License</title>
+
+ <para>
+ Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ </refsection>
+
+</refentry>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/prepare.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/prepare.docbook
new file mode 100644
index 0000000..4fb9cf9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/prepare.docbook
@@ -0,0 +1,314 @@
+<refentry id="scripts-bash-prepare">
+
+ <refmeta>
+ <refentrytitle>prepare</refentrytitle>
+ <indexterm type="specific-function">
+ <primary>Standardize configuration tasks inside &TCAR;</primary>
+ </indexterm>
+ </refmeta>
+
+ <refnamediv>
+ <refname>prepare</refname>
+ <refpurpose>Standardize configuration tasks inside &TCAR;</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <para>
+ Assuming this is the very first time you run the
+ <command>centos-art</command> command, you'll find that there
+ isn't such a command in your workstation. This is correct
+ because you haven't created the symbolic link that makes it
+ available in your execution path, yet. In order to make the
+ <command>centos-art</command> command available in the
+ execution path of your workstation, you need to run the
+ <command>centos-art.sh</command> script using its absolute
+ path first:
+ </para>
+
+ <cmdsynopsis>
+ <command>~/artwork/Scripts/Bash/centos-art.sh</command>
+ <arg choice="req">prepare</arg>
+ <arg>-h|--help</arg>
+ <arg>-q|--quiet</arg>
+ <arg>--answer-yes</arg>
+ <arg>--set-environment</arg>
+ <arg>--see-environment</arg>
+ <arg>--packages</arg>
+ <arg>--locales</arg>
+ <arg>--links</arg>
+ <arg>--images</arg>
+ <arg>--manuals</arg>
+ <arg>--synchronize</arg>
+ </cmdsynopsis>
+
+ <para>
+ Later, once the <command>centos-art</command> command is
+ available in your execution path, there is no need for you to
+ use any absolute path again. From this time on, you can use
+ the <command>centos-art</command> command-line interface
+ directly, as the following example describes:
+ </para>
+
+ <cmdsynopsis>
+ <command>centos-art</command>
+ <arg choice="req">prepare</arg>
+ <arg>-h|--help</arg>
+ <arg>-q|--quiet</arg>
+ <arg>--answer-yes</arg>
+ <arg>--set-environment</arg>
+ <arg>--see-environment</arg>
+ <arg>--packages</arg>
+ <arg>--locales</arg>
+ <arg>--links</arg>
+ <arg>--images</arg>
+ <arg>--manuals</arg>
+ <arg>--synchronize</arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsection>
+ <title>Description</title>
+ <para>
+ The <function>prepare</function> function exists to set
+ environment variables, install/update required packages,
+ create symbolic links for content reusing, render images based
+ on available design models and artistic motifs, render
+ documentation manuals, build language-specific files required
+ for content localization and anything else needed in order to
+ make the working copy of &TCAR; ready to be used.
+ </para>
+
+ <para>
+ When no option is provided to <function>prepare</function>
+ functionality, the <command>centos-art.sh</command> script
+ uses the <option>--set-environment</option>,
+ <option>--packages</option>, <option>--locales</option>
+ <option>--links</option>, <option>--images</option> and
+ <option>--manuals</option> options, in that order, as default
+ behaviour. Otherwise, if you provide any option, the
+ <command>centos-art.sh</command> script avoids its default
+ behaviour and executes the <function>prepare</function>
+ functionality as specified by the options you provided.
+ </para>
+
+ <para>
+ Notice that it is possible for you to execute the
+ <function>prepare</function> functionality as many times as
+ you need to. This is specially useful when you need to keep
+ syncronized the relation between content produced inside your
+ working copy and the applications you use outside it. For
+ example, considering you've added new brushes to or removed
+ old brushes from your working copy of &TCAR;, the link
+ information related to those files need to be updated in the
+ <filename class="directory">~/.gimp-2.2/brushes</filename>
+ directory too, in a way the addition/deletion change that took
+ place in your working copy can be reflected there, as well.
+ The same is true for other similar components like fonts,
+ patterns and palettes.
+ </para>
+
+ </refsection>
+
+ <refsection>
+ <title>Usage</title>
+ <para>
+ Use the <function>prepare</function> functionality the first
+ time you download a working copy of &TCAR; or later, to be
+ sure your workstation has all the components it needs so you
+ can use the working copy of &TCAR; in all its extension.
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-prepare-options">
+ <title>Options</title>
+
+ <para>
+ The <command>centos-art prepare</command> command accepts
+ common options described in <xref
+ linkend="scripts-bash-cliref-options" /> and the following
+ specific options:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><option>--answer-yes</option></term>
+ <listitem>
+ <para>
+ Assume <emphasis>yes</emphasis> to all confirmation requests.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--packages</option></term>
+ <listitem>
+ <para>
+ This option verifies packeges required by automation scripts
+ and installs or updates them as required. When required
+ packages aren't installed or need to be updated, the
+ <command>centos-art</command> uses the <command>sudo</command>
+ and <command>yum</command> to perform either installations or
+ actualizations tasks. In both cases, it is required that you
+ configure the <filename>/etc/sudoers</filename> configuration
+ file first, as discribed in <xref
+ linkend="repo-ws-config-sudoers" />.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--locales</option></term>
+ <listitem>
+ <para>
+ This option creates or updates the portable objects (PO) and
+ machine object (MO) used by <application>gettext</application>
+ to retrive translated strings related to
+ <command>centos-art.sh</command> script. This option calls
+ the <function>locale</function> functionality of centos-art.sh
+ with the <option>--update</option> option, as described in
+ <xref linkend="scripts-bash-locale" />.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--links</option></term>
+ <listitem>
+ <para>
+ This option maintains the file relation between your working
+ copy and configuration files inside your workstation through
+ symbolic links. When you provide this option, the
+ <command>centos-art.sh</command> script puts itself into your
+ system's execution path through its command line interface
+ <command>centos-art</command> and makes common brushes,
+ patterns, palettes and fonts inside the working copy,
+ available to applications like GIMP in order for you to make
+ use of them without loosing version control over them.
+ </para>
+ <caution>
+ <para>
+ This option removes all common fonts, brushes, patterns, and
+ palettes currently installed in your home directory, in order
+ to create a fresh installation of them all again, using the
+ working copy as section.
+ </para>
+ </caution>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--images</option></term>
+ <listitem>
+ <para>
+ This option initializes image files inside the working copy.
+ When you provide this option, the
+ <command>centos-art.sh</command> calls the
+ <function>render</function> functionality to create images
+ related to each design model available in your working copy,
+ as described in <xref linkend="scripts-bash-render" />.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--manuals</option></term>
+ <listitem>
+ <para>
+ This option initializes documentation files inside the working
+ copy. When you provide this option, the
+ <command>centos-art.sh</command> script calls both the
+ <function>render</function> and <function>help</function>
+ functionality to produce DocBook and Texinfo manuals,
+ respectively.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--see-environment</option></term>
+ <listitem>
+ <para>
+ Print the name and value of some of the environment variables
+ used by <command>centos-art.sh</command> script as described
+ in <xref linkend="scripts-bash-environment" />.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--set-environment</option></term>
+ <listitem>
+ <para>
+ Set default environment values to your personal profile
+ (<filename>~/.bash_profile</filename>).
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ </refsection>
+
+ <refsection id="scripts-bash-prepare-example">
+ <title>Examples</title>
+ <para>
+ None.
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-prepare-bugs">
+ <title>Bugs</title>
+ <para>
+ To report bugs related to this function, please create a new
+ ticket <ulink
+ url="https://projects.centos.org/trac/artwork/newticket?summary=Error%20Standardizing%20Configuration%20Tasks&component=Scripts">here</ulink>
+ refering the specific problems you found in it. For example,
+ it would be useful if you copy and paste any error output from
+ <command>centos-art.sh</command> script.
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-prepare-authors">
+ <title>Authors</title>
+ <para>
+ The following people have worked in this functionality:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Alain Reguera Delgado <<ulink url="mailto:alain.reguera@gmail.com">alain.reguera@gmail.com</ulink>>, =COPYRIGHT_YEAR_LIST=
+ </para>
+ </listitem>
+ </itemizedlist>
+ </refsection>
+
+ <refsection id="scripts-bash-prepare-licence">
+ <title>License</title>
+
+ <para>
+ Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ </refsection>
+
+</refentry>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/render.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/render.docbook
new file mode 100644
index 0000000..84826ba
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/render.docbook
@@ -0,0 +1,435 @@
+<refentry id="scripts-bash-render">
+
+ <refmeta>
+ <refentrytitle>render</refentrytitle>
+ <indexterm type="specific-function">
+ <primary>Standardize rendition tasks inside &TCAR;.</primary>
+ </indexterm>
+ </refmeta>
+
+ <refnamediv>
+ <refname>render</refname>
+ <refpurpose>Standardize rendition tasks inside &TCAR;.</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <cmdsynopsis>
+ <command>centos-art</command>
+ <arg choice="req">render</arg>
+ <arg>-h|--help</arg>
+ <arg>-q|--quiet</arg>
+ <arg>--filter="<replaceable>REGEX</replaceable>"</arg>
+ <arg>--answer-yes</arg>
+ <arg>--dont-dirspecific</arg>
+ <arg>--releasever="<replaceable>RELEASEVER</replaceable>"</arg>
+ <arg>--basearch="<replaceable>BASEARCH</replaceable>"</arg>
+ <arg>--post-rendition="<replaceable>COMMAND</replaceable>"</arg>
+ <arg>--last-rendition="<replaceable>COMMAND</replaceable>"</arg>
+ <arg>--theme-model="<replaceable>MODELNAME</replaceable>"</arg>
+ <arg>--with-brands</arg>
+ <arg>--synchronize</arg>
+ <arg choice="req" rep="repeat"><replaceable>LOCATION</replaceable></arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsection id="scripts-bash-render-description">
+ <title>Description</title>
+
+ <para>
+ The <function>render</function> functionality exists to
+ automate content rendition inside &TCAR;. The content
+ rendition process itself takes place through the following
+ rendition modes:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <literal>svg</literal> — This modes works with both
+ gzip-compressed (<filename class="extension">.svgz</filename>)
+ or uncompressed (<filename class="extension">.svg</filename>)
+ scalable vector graphics as source files and produces portable
+ network graphics as main output.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>docbook</literal> — This mode works with
+ DocBook source files and produces XHTML as main output. It is
+ also possible to produce PDF output from DocBook source files,
+ however PDF output is commented because its production fails
+ trying to create indexes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>conf</literal> — This mode works with one or
+ more configuration files as source and produces portable
+ network graphics as main output. The format used in these
+ configuration files is described in <xref
+ linkend="scripts-bash-render-description-conffiles"/>.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ To determine the rendition mode, the
+ <function>render</function> functionality uses the path
+ provided as <replaceable>LOCATION</replaceable> argument and
+ the path name convention described in <xref
+ linkend="repo-convs-relbdirs" />.
+ </para>
+
+ <refsection id="scripts-bash-render-description-renderabledirs">
+ <title>Render-able Directories</title>
+
+ <para>
+ The render-able directories are conventional locations inside
+ the working copy where you can find final output files. The
+ final output files are produced from source files and
+ auxiliary files. Auxiliary files are frequently used to
+ create localized instances of source files which are, in turn,
+ used to create final output files in different forms (e.g., in
+ a different language).
+ </para>
+
+ <para>
+ Inside the working copy of &TCAR;, the following directory
+ structures are considered render-able directories:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename class="directory">Identity/Images/</filename>
+ — This directory structure organizes final image files
+ in different formats. It also includes source files for
+ producing the backgrounds of themes. Related design models for
+ all these files are under <filename
+ class="directory">Identity/Models/</filename> directory
+ structure.
+ </para>
+ <important>
+ <para>
+ Don't move any source file related to theme backgrounds from
+ render-able directories to theme design models directory
+ structure. The source files related to theme backgrounds are
+ specific to each theme and cannot be shared among different
+ themes. The directory structure related to theme design models
+ is reserved for files shared by all themes.
+ </para>
+ </important>
+ </listitem>
+ <listitem>
+ <para>
+ <filename
+ class="directory">Documentation/Manuals/</filename>
+ — This directory structure organizes final documentation
+ files. Design models for all these files are organized under
+ <filename
+ class="directory">Documentation/Models/</filename>
+ directory structure.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ Inside render-able directories the rendition process is
+ performed through different rendition flows known as
+ theme-rendition, base-rendition, post-rendition and
+ last-rendition.
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-render-description-themeflow">
+ <title>Theme-Rendition Flow</title>
+ <para>
+ The theme-rendition flow exists to produce content inside
+ <filename>Identity/Images/Themes/</filename> directory
+ structure. This rendition flow identifies which directories
+ are render-able and uses the base-rendition on them, one by
+ one.
+ </para>
+ <para>
+ The theme-rendition flow exists to support massive rendition
+ of themes through the following command:
+ </para>
+
+ <cmdsynopsis>
+ <command>centos-art render Identity/Images/Themes</command>
+ </cmdsynopsis>
+
+ <para>
+ In case you need to limit the amount of themes or components
+ inside themes you want to render, you can be more
+ specific about the <replaceable>LOCATION</replaceable> you
+ passed as argument and use the
+ <option>--filter="<replaceable>REGEX</replaceable>"</option>
+ to specify the file you want to render. For example, if you
+ only want to render the <filename>01-welcome.png</filename>
+ Anaconda file for CentOS-5 distribution based on version 2 of
+ Modern artistic motif, then you can run the following command:
+ </para>
+
+ <cmdsynopsis>
+ <command>centos-art render Identity/Images/Themes/Modern/2/Distro/5/Anaconda --filter="01-welcome"</command>
+ </cmdsynopsis>
+
+ <para>
+ Notice that you can reach the same result in different ways
+ here by creating combinations between the path you provide as
+ <replaceable>LOCATION</replaceable> and the
+ <option>--filter</option> option. For example, the following
+ commands produce the same result:
+ </para>
+
+ <cmdsynopsis>
+ <command>centos-art render Identity/Images/Themes/Modern/2/Distro/5/Anaconda</command>
+ </cmdsynopsis>
+
+ <cmdsynopsis>
+ <command>centos-art render Identity/Images/Themes/Modern --filter="2/Distro/5/Anaconda"</command>
+ </cmdsynopsis>
+
+ <para>
+ You can use whatever combination you like whenever it matches
+ a valid render-able directory inside the working copy. But it
+ seems to be an acceptable practice to use the
+ <replaceable>LOCATION</replaceable> argument to specify the
+ render-able directory path inside the <filename
+ class="directory">Identity/Images/Themes</filename>
+ directory which images need to be rendered for and the
+ <option>--filter</option> option only when it is needed to
+ restrict rendition to a specific file inside the directory
+ provided as <replaceable>LOCATION</replaceable>.
+ </para>
+
+ </refsection>
+
+ <refsection id="scripts-bash-render-description-baseflow">
+ <title>Base-Rendition Flow</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-render-description-postflow">
+ <title>Post-Rendition Flow </title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-render-description-lastflow">
+ <title>Last-Rendition Flow </title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-render-description-conffiles">
+ <title>Configuration Files (<filename>render.conf</filename>)</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+ </refsection>
+
+ <refsection id="scripts-bash-render-usage">
+ <title>Usage</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-render-option">
+ <title>Options</title>
+
+ <para>
+ The <command>centos-art prepare</command> command accepts
+ common options described in <xref
+ linkend="scripts-bash-cliref-options" /> and the following
+ specific options:
+ </para>
+
+ <variablelist>
+
+ <varlistentry>
+ <term><option>--answer-yes</option></term>
+ <listitem>
+ <para>
+ Assume <emphasis>yes</emphasis> to all confirmation requests.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--filter="<replaceable>REGEX</replaceable>"</option></term>
+ <listitem>
+ <para>
+ This option reduces the list of files to process inside
+ <replaceable>LOCATION</replaceable> using
+ <replaceable>REGEX</replaceable> as <replaceable>REGUEX</replaceable>
+ using <replaceable>REGEX</replaceable> as files you want to render.
+ The deeper you go into the directory structure the more
+ specific you'll be about the files you want to render. When
+ you cannot go deeper into the directory structure through
+ <replaceable>LOCATION</replaceable> specification, use this
+ option to reduce the list of files therein.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--synchronize</option></term>
+ <listitem>
+ <para>
+ Synchronizes available changes between the working copy and
+ the central repository.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--releasever="<replaceable>RELEASE</replaceable>"</option></term>
+ <listitem>
+ <para>
+ This option expands the <code>=\RELEASE=</code>,
+ <code>=\MAJOR_RELEASE=</code>, and
+ <code>=\MINOR_RELEASE=</code> translation makers based on
+ <replaceable>NUMBER</replaceable> value. Notice that
+ translation markers here were escaped using a backslash
+ (<code>\</code>) in order to prevent their expansion. Use this
+ option when you need to produce release-specific contents, but
+ no release information can be retrived from the directory path
+ you are currently rendering.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--basearch="<replaceable>BASEARCH</replaceable>"</option></term>
+ <listitem>
+ <para>
+ This option expands the <code>=\ARCHITECTURE=</code>,
+ translation makers based on <replaceable>ARHC</replaceable> value.
+ Notice that translation markers here were escaped using a
+ backslash (<code>\</code>) in order to prevent their
+ expansion. Use this option when you need to produce
+ architecture-sepecific contents but no architecture
+ information can be retrived from the directory path you are
+ currently rendering.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--theme-model="<replaceable>MODELNAME</replaceable>"</option></term>
+ <listitem>
+ <para>
+ This option specifies the name of theme model you want to use
+ when producing theme artistic motifs. By default, if this
+ option is not provided, the <literal>Default</literal> theme
+ model is used as reference to produce theme artistic motifs.
+ To know what values can be passed as
+ <replaceable>MODELNAME</replaceable>, run the following
+ command:
+ </para>
+
+ <cmdsynopsis>
+ <command>ls ${TCAR_WORKDIR}/Identity/Models/Themes</command>
+ </cmdsynopsis>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--post-rendition="<replaceable>COMMAND</replaceable>"</option></term>
+ <listitem>
+ <para>
+ This option lets you apply a command as post-rendition action.
+ In this case, the <replaceable>COMMAND</replaceable>
+ represents the command-line you want to execute in order to
+ perform in-place modifications to base-rendition output.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--last-rendition="<replaceable>COMMAND</replaceable>"</option></term>
+ <listitem>
+ <para>
+ This option lets you apply a command as last-rendition action.
+ In this case, the <replaceable>COMMAND</replaceable> argument
+ represents the command string you want to execute in order to
+ perform in-place modifications to base-rendition,
+ post-rendition and directory-specific rendition outputs.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsection>
+
+ <refsection id="scripts-bash-render-examples">
+ <title>Examples</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-render-bugs">
+ <title>Bugs</title>
+ <para>
+ To report bugs related to this function, please create a new
+ ticket <ulink
+ url="https://projects.centos.org/trac/artwork/newticket?summary=Error%20Standardizing%20Rendition%20Tasks&component=Scripts">here</ulink>
+ refering the specific problems you found in it. For example,
+ it would be useful if you copy and paste any error output from
+ <command>centos-art.sh</command> script.
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-render-authors">
+ <title>Authors</title>
+ <para>
+ The following people have worked in this functionality:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Alain Reguera Delgado <<ulink url="mailto:alain.reguera@gmail.com">alain.reguera@gmail.com</ulink>>, =COPYRIGHT_YEAR_LIST=
+ </para>
+ </listitem>
+ </itemizedlist>
+ </refsection>
+
+ <refsection id="scripts-bash-render-licence">
+ <title>License</title>
+
+ <para>
+ Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ </refsection>
+
+</refentry>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/svn.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/svn.docbook
new file mode 100644
index 0000000..179cf3d
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/svn.docbook
@@ -0,0 +1,83 @@
+<refentry id="scripts-bash-svn">
+
+ <refmeta>
+ <refentrytitle>svn</refentrytitle>
+ <indexterm type="specific-function">
+ <primary>Standardize version control tasks inside &TCAR;</primary>
+ </indexterm>
+ </refmeta>
+
+ <refnamediv>
+ <refname>svn</refname>
+ <refpurpose>Standardize version control tasks inside &TCAR;</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <para>
+ ...
+ </para>
+ </refsynopsisdiv>
+
+ <refsection id="scripts-bash-svn-description">
+ <title>Description</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-svn-usage">
+ <title>Usage</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-svn-environment">
+ <title>Function Specific Environment</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-svn-authors">
+ <title>Authors</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ ...
+ </para>
+ </listitem>
+ </itemizedlist>
+ </refsection>
+
+ <refsection id="scripts-bash-svn-licence">
+ <title>License</title>
+
+ <para>
+ Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ </refsection>
+
+</refentry>
+
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/tuneup.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/tuneup.docbook
new file mode 100644
index 0000000..c40f697
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/tuneup.docbook
@@ -0,0 +1,301 @@
+<refentry id="scripts-bash-tuneup">
+
+ <refmeta>
+ <refentrytitle>tuneup</refentrytitle>
+ <indexterm type="specific-function">
+ <primary>Standardize maintainance tasks inside &TCAR;</primary>
+ </indexterm>
+ </refmeta>
+
+ <refnamediv>
+ <refname>tuneup</refname>
+ <refpurpose>Standardize maintainance tasks inside &TCAR;</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <para>
+ The <varname>DIRECTORY</varname> parameter specifies the
+ directory path, inside the working copy of &TCAR;, where the
+ files you want to process are stored in. This paramter can be
+ provided more than once in order to process more than one
+ directory path in a single command execution. When this
+ parameter is not provided, the current directory path where
+ the command was called from is used instead.
+ </para>
+ </refsynopsisdiv>
+
+ <refsection id="scripts-bash-tuneup-description">
+ <title>Description</title>
+
+ <para>
+ Tasks related to file maintainance are repetitive. You might
+ find yourself doing them time after time inside the working
+ copy of &TCAR;. Some of these maintainance tasks do update top
+ comments on shell scripts, create table of contents for web
+ pages, update metadata related to design models and remove
+ unused definitions from design models.
+ </para>
+
+ <para>
+ When you execute the tuneup functionality of centos-art.sh
+ script, it looks for all files that match the supported
+ extensions (e.g., <filename class="extension">.sh</filename>,
+ <filename class="extension">.svg</filename> and <filename
+ class="extension">.xhtml</filename>) in the directory
+ specified, builds a list with them and applies the
+ maintainance tasks using file extensions as refentry.
+ </para>
+
+ <para>
+ When shell scripts are found, the <function>tuneup</function>
+ functionality of centos-art.sh script reads a comment template
+ from
+ <filename>Scripts/Functions/Tuneup/Shell/Config/topcomment.sed</filename>
+ and applies it to all shell scripts found, one by one. As
+ result, all shell scripts will end up having the same
+ copyright and license information the comment template does.
+ </para>
+ <para>
+ In order for the shell script top comment template to be
+ applied correctly, the shell scripts you write must have the
+ structure described in <xref linkend="scripts-bash-tuneup-fig1" />.
+ </para>
+
+ <example id="scripts-bash-tuneup-fig1">
+ <title>Shell script top-comment template.</title>
+ <screenshot>
+ <screeninfo>Shell script top-comment template.</screeninfo>
+ <mediaobject>
+ <textobject>
+<programlisting>
+ 1| #!/bin/bash
+ 2| #
+ 3| # doSomething.sh -- The function description goes here.
+ 4| #
+ 5| # Copyright
+ 6| #
+ 7| # ...
+ 8| #
+ 9| # ----------------------------------------------------------------------
+10| # $Id$
+11| # ----------------------------------------------------------------------
+12|
+13| function doSomething {
+14|
+15| }
+</programlisting>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </example>
+
+ <para>
+ The <function>tuneup</function> functionality of
+ <command>centos-art.sh</command> script replaces all lines
+ between the <literal>Copyright</literal> line (e.g., line 5)
+ and the first separator line (e.g., line 9), inclusively.
+ Everything else will remain immutable in the file.
+ </para>
+
+ <para>
+ When scalable vector graphics are found, the tuneup
+ functionality reads a SVG metadata template from
+ <filename>Scripts/Functions/Tuneup/Svg/Config/metadata.sed</filename>
+ and applies it to all files found, one by one. Immediatly
+ after the metadata template has been applied and, before
+ passing to next file, all unused definition are removed from
+ the file, too.
+ </para>
+ <para>
+ The metadata applied by the SVG metadata template is created
+ dynamicaly combining the absolute path of the file being
+ currently modified, the workstation's date information, the
+ <command>centos-art.sh</command> script copyright holder
+ (e.g., =COPYRIGHT_HOLDER=) as refentry and the Creative
+ Common Distribution-ShareAlike 3.0 License as default license
+ to release SVG files.
+ </para>
+ <para>
+ The elimination of unused definitions inside SVG files takes
+ place through Inkscape's <option>--vacuum-defs</option>
+ option, as described in its man page (e.g., <command>man
+ inkscape</command>).
+ </para>
+
+ <para>
+ When HTML files are found, the <function>tuneup</function>
+ functionality of <command>centos-art.sh</command> script
+ transforms web page headings to make them accessible through a
+ table of contents. The table of contents is expanded in
+ place, wherever the <code><div
+ class="toc"></div></code> piece of code be in the
+ file. Once the table of contents has been expanded, there is
+ no need to put anything else in the page. You can run the
+ <function>tuneup</function> functionality everytime you update
+ the heading information so as to update the table of contents,
+ too.
+ </para>
+ <para>
+ In order for this functionality to build the table of contents
+ from headings, you need to put headings in just one line. The
+ headin level can vary from <code>h1</code> to <code>h6</code>
+ with attribute definitions accepted. Closing tag must be
+ present and also match the openning tag. Inside the heading
+ definition an anchor definition must be present with attribute
+ definitions accepted. The value of <property>name</property>
+ and <property>href</property> attributes from the anchor
+ element are set dynamically using the md5sum output of
+ combining the page location, the <literal>head-</literal>
+ string and the heading content itself. If any of the
+ components used to build the heading refentry changes, you
+ need to run the the tuneup functionality of
+ <command>centos-art.sh</command> script in order for the
+ anchor elements to use the correct information.
+ </para>
+ <para>
+ For example, the headings shown in <xref
+ linkend="scripts-bash-tuneup-fig2" /> produces the table of
+ contents shown in <xref linkend="scripts-bash-tuneup-fig3" />.
+ </para>
+
+ <example id="scripts-bash-tuneup-fig2">
+ <title>HTML heading definition.</title>
+ <screenshot>
+ <screeninfo>HTML heading definition.</screeninfo>
+ <mediaobject>
+ <textobject>
+<programlisting>
+<h1 class="title"><a name="head-8a23b56a28dfa7277d176576f217054a">Forms</a></h1>
+<h2 class="title"><a name="head-629f38bc607f2a270177106b450aeae3">Elements</a></h2>
+<h2 class="title"><a name="head-f49cae1d73592c984bbb0bffb1d5699a">Recommendations</a></h2>
+</programlisting>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </example>
+
+ <example id="scripts-bash-tuneup-fig3">
+ <title>HTML table of contents definition.</title>
+ <screenshot>
+ <screeninfo>HTML table of contents definition.</screeninfo>
+ <mediaobject>
+ <textobject>
+<programlisting>
+<div class="toc"> <p>Table of contents</p> <dl><dt><a href="#head-8a23b56a28dfa7277d176576f217054a">Forms</a> <dl><dt><a href="#head-629f38bc607f2a270177106b450aeae3">Elements</a> </dt><dt><a href="#head-f49cae1d73592c984bbb0bffb1d5699a">Recommendations</a> </dt></dl> </dt></dl> </div>
+</programlisting>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </example>
+ </refsection>
+
+ <refsection id="scripts-bash-tuneup-options">
+ <title>Options</title>
+ <para>
+ The <function>tuneup</function> functionality accepts the
+ following options:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><option>--quiet</option></term>
+ <listitem>
+ <para>
+ Supress all output messages except error messages. When this
+ option is passed, all confirmation requests are supressed and
+ a possitive answer is assumed for them, just as if the
+ <option>--answer-yes</option> option would have been provided.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--answer-yes</option></term>
+ <listitem>
+ <para>
+ Assume <emphasis>yes</emphasis> to all confirmation requests.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--filter="REGEX"</option></term>
+ <listitem>
+ <para>
+ Reduce the list of files to process inside
+ <replaceable>path/to/dir</replaceable> using
+ <replaceable>REGEX</replaceable> as pattern. You can use this
+ option to control the amount of files you want to tuneup. The
+ deeper you go into the directory structure the more specific
+ you'll be about the files you want to tuneup. When you cannot
+ go deeper into the directory structure through
+ <replaceable>path/to/dir</replaceable> specification, use this
+ option to reduce the list of files therein.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--synchronize</option></term>
+ <listitem>
+ <para>
+ Synchronizes available changes between the working copy and
+ the central repository.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsection>
+
+ <refsection id="scripts-bash-tuneup-environment">
+ <title>Function Specific Environment</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-tuneup-authors">
+ <title>Authors</title>
+ <para>
+ The following people have worked in the
+ <function>tuneup</function> functionality:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Alain Reguera Delgado <<ulink url="mailto:alain.reguera@gmail.com">alain.reguera@gmail.com</ulink>>, =COPYRIGHT_YEAR_LIST=
+ </para>
+ </listitem>
+ </itemizedlist>
+ </refsection>
+
+ <refsection id="scripts-bash-tuneup-licence">
+ <title>License</title>
+
+ <para>
+ Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ </refsection>
+
+</refentry>
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/vcs.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/vcs.docbook
new file mode 100644
index 0000000..fbf8a4c
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/Scripts/Bash/vcs.docbook
@@ -0,0 +1,83 @@
+<refentry id="scripts-bash-vcs">
+
+ <refmeta>
+ <refentrytitle>vcs</refentrytitle>
+ <indexterm type="specific-function">
+ <primary>Standardize version control tasks inside &TCAR;</primary>
+ </indexterm>
+ </refmeta>
+
+ <refnamediv>
+ <refname>vcs</refname>
+ <refpurpose>Standardize version control tasks inside &TCAR;</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <para>
+ ...
+ </para>
+ </refsynopsisdiv>
+
+ <refsection id="scripts-bash-vcs-description">
+ <title>Description</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-vcs-usage">
+ <title>Usage</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-vcs-environment">
+ <title>Function Specific Environment</title>
+ <para>
+ ...
+ </para>
+ </refsection>
+
+ <refsection id="scripts-bash-vcs-authors">
+ <title>Authors</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ ...
+ </para>
+ </listitem>
+ </itemizedlist>
+ </refsection>
+
+ <refsection id="scripts-bash-vcs-licence">
+ <title>License</title>
+
+ <para>
+ Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ </refsection>
+
+</refentry>
+
diff --git a/Artworks/Documentation/Repository/Docbook/Tcar-ug/tcar-ug.docbook b/Artworks/Documentation/Repository/Docbook/Tcar-ug/tcar-ug.docbook
new file mode 100644
index 0000000..b0a19c9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Docbook/Tcar-ug/tcar-ug.docbook
@@ -0,0 +1,84 @@
+<?xml version="1.0"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" []>
+<!--
+ WARNING: Keep the preable definition as it is (in two lines). The
+ centos-art.sh script uses this information as pattern to rebuild
+ the preamble definition later and introduce system entities
+ definitions in it. If centos-art.sh script cannot rebuild the
+ preamble definition of this document its validation will fail and
+ consequently, no final rendition will be possible.
+-->
+<book lang="en_US">
+
+ <!-- Front matter -->
+
+ <title>The CentOS Artwork Repository</title>
+ <subtitle>User's Guide</subtitle>
+
+ <bookinfo>
+ <author>
+ <firstname>Alain</firstname>
+ <surname>Reguera Delgado</surname>
+ </author>
+
+ <!-- Copyright: The copyright page is verso and contains the
+ copyright notice, the publishing/printing history, the country
+ where printed, ISBN and/or CIP information. The page is
+ usually typeset in a smaller font than the normal text. -->
+ <copyright>
+ <year>2009</year>
+ <year>2010</year>
+ <year>2011</year>
+ <year>2012</year>
+ <year>2013</year>
+ <holder>&TCP;. All rights reserved.</holder>
+ </copyright>
+
+ <legalnotice>
+ <para>
+ 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
+ <xref linkend="licenses-gfdl" />.
+ </para>
+ </legalnotice>
+
+ <revhistory>
+ <revision>
+ <revnumber>1.0</revnumber>
+ <date>Today</date>
+ <author>
+ <firstname>Alain</firstname>
+ <surname>Reguera Delgado</surname>
+ </author>
+ <revdescription>
+ <para>
+ Under development.
+ </para>
+ </revdescription>
+ </revision>
+ </revhistory>
+
+ </bookinfo>
+
+ <!-- Preface -->
+ &preface;
+ <!-- Main matter -->
+ &repo;
+ &identity;
+ &locales;
+ &manuals;
+ &scripts;
+ <!-- Licenses -->
+ <!--
+ WARNING: Licenses are included by centos-art.sh script at
+ execution time, so don't remove the comments this message is in
+ between, nor this message so you can remember it.
+ -->
+ <!-- Back matter -->
+ <index><title>Index</title></index>
+
+</book>
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters-menu.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters-menu.texinfo
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters-menu.texinfo
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters-nodes.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters-nodes.texinfo
new file mode 100644
index 0000000..3e2dc0b
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters-nodes.texinfo
@@ -0,0 +1 @@
+@include =INCL=
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters.texinfo
new file mode 100644
index 0000000..249e5cc
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters.texinfo
@@ -0,0 +1,12 @@
+@node =CHAPTER_NODE=
+@chapter =CHAPTER_TITLE=
+@cindex =CHAPTER_CIND=
+
+@c -- Chapter Introduction
+...
+
+@c -- Chapter Menu
+@include =CHAPTER_NAME=-menu.texinfo
+
+@c -- Chapter Nodes
+@include =CHAPTER_NAME=-nodes.texinfo
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters/section-functions.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters/section-functions.texinfo
new file mode 100644
index 0000000..88cd2cc
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters/section-functions.texinfo
@@ -0,0 +1,35 @@
+@node =SECT=
+@section =SECT=
+@cindex =CIND=
+
+@subheading Name
+
+The =SECT= directory organizes @dots{}
+
+@subheading Synopsis
+
+@dots{}
+
+@subheading Description
+
+@dots{}
+
+@subheading Examples
+
+@dots{}
+
+@subheading Author
+
+Written by @dots{}
+
+@subheading Reporting bugs
+
+Report bugs to @email{centos-artwork@@centos.org} mailing list.
+
+@subheading Copyright
+
+Copyright @copyright{} =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
+
+This is free software. You may redistribute copies of it under the
+terms of the @ref{GNU General Public License}. There is NO WARRANTY,
+to the extent permitted by law.
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters/section.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters/section.texinfo
new file mode 100644
index 0000000..9461faa
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Chapters/section.texinfo
@@ -0,0 +1,8 @@
+@node =NODE=
+@section =SECT=
+@cindex =CIND=
+
+...
+
+@c -- <[centos-art(SeeAlso)
+@c -- ]>
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses-menu.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses-menu.texinfo
new file mode 100755
index 0000000..b8240ba
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses-menu.texinfo
@@ -0,0 +1,4 @@
+@menu
+* GNU General Public License::
+* GNU Free Documentation License::
+@end menu
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses-nodes.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses-nodes.texinfo
new file mode 100755
index 0000000..da69108
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses-nodes.texinfo
@@ -0,0 +1,9 @@
+@node GNU General Public License
+@section GNU General Public License
+@cindex GNU General Public License
+@include Licenses/GPL.texinfo
+
+@node GNU Free Documentation License
+@section GNU Free Documentation License
+@cindex GNU Free Documentation License
+@include Licenses/GFDL.texinfo
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses.texinfo
new file mode 100755
index 0000000..8b2fda9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses.texinfo
@@ -0,0 +1,5 @@
+@node Licenses
+@appendix Licenses
+@cindex Licenses
+@include Licenses-menu.texinfo
+@include Licenses-nodes.texinfo
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses/GFDL.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses/GFDL.texinfo
new file mode 100755
index 0000000..c40cf38
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses/GFDL.texinfo
@@ -0,0 +1,414 @@
+Version 1.2, November 2002
+
+@verbatim
+Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc.
+ 675 Mass Ave, Cambridge, MA 02139, USA
+@end verbatim
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+@subheading Preamble
+
+The purpose of this License is to make a manual, textbook, or other
+functional and useful document ``free'' 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.
+
+This License is a kind of ``copyleft'', which means that derivative
+works of the document must themselves be free in the same sense. It
+complements the GNU General Public License, which is a copyleft
+license designed for free software.
+
+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.
+
+@subheading 1. Applicability and definitions
+
+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 ``Document'', below,
+refers to any such manual or work. Any member of the public is a
+licensee, and is addressed as ``you''. You accept the license if you
+copy, modify or distribute the work in a way requiring permission
+under copyright law.
+
+A ``Modified Version'' 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.
+
+A ``Secondary Section'' 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.
+
+The ``Invariant Sections'' 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.
+
+The ``Cover Texts'' 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.
+
+A ``Transparent'' 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 ``Transparent'' is called ``Opaque''.
+
+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.
+
+The ``Title Page'' 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, ``Title Page'' means
+the text near the most prominent appearance of the work's title,
+preceding the beginning of the body of the text.
+
+A section ``Entitled XYZ'' 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 ``Acknowledgements'',
+``Dedications'', ``Endorsements'', or ``History''.) To ``Preserve the
+Title'' of such a section when you modify the Document means that it
+remains a section ``Entitled XYZ'' according to this definition.
+
+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.
+
+@subheading 2. Verbatim copying
+
+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 @emph{3.
+Copying in quantity}.
+
+You may also lend copies, under the same conditions stated above, and
+you may publicly display copies.
+
+@subheading 3. Copying in quantity
+
+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.
+
+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.
+
+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.
+
+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.
+
+@subheading 4. Modifications
+
+You may copy and distribute a Modified Version of the Document under
+the conditions of sections @emph{2. Verbatim copying} and @emph{3.
+Copying in quantity} 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:
+
+A. 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.
+
+B. 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.
+
+C. State on the Title page the name of the publisher of the Modified
+Version, as the publisher.
+
+D. Preserve all the copyright notices of the Document.
+
+E. Add an appropriate copyright notice for your modifications adjacent
+to the other copyright notices.
+
+F. 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.
+
+G. Preserve in that license notice the full lists of Invariant
+Sections and required Cover Texts given in the Document's license
+notice.
+
+H. Include an unaltered copy of this License.
+
+I. Preserve the section Entitled ``History'', 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 ``History'' 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.
+
+J. 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 ``History'' 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.
+
+K. For any section Entitled ``Acknowledgements'' or ``Dedications'',
+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.
+
+L. 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.
+
+M. Delete any section Entitled ``Endorsements''. Such a section may
+not be included in the Modified Version.
+
+N. Do not retitle any existing section to be Entitled ``Endorsements''
+or to conflict in title with any Invariant Section.
+
+O. Preserve any Warranty Disclaimers.
+
+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.
+
+You may add a section Entitled ``Endorsements'', 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.
+
+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.
+
+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.
+
+@subheading 5. Combining documents
+
+You may combine the Document with other documents released under this
+License, under the terms defined in section @emph{4. Modifications}
+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.
+
+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.
+
+In the combination, you must combine any sections Entitled ``History''
+in the various original documents, forming one section Entitled
+``History''; likewise combine any sections Entitled
+``Acknowledgements'',
+and any sections Entitled ``Dedications''. You must delete all sections
+Entitled ``Endorsements''.
+
+@subheading 6. Collections of documents
+
+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.
+
+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.
+
+@subheading 7. Aggregation with independent works
+
+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 ``aggregate'' 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.
+
+If the Cover Text requirement of section @emph{3. Copying in quantity}
+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.
+
+@subheading 8. Translations
+
+Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section
+@emph{4. Modifications}. 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.
+
+If a section in the Document is Entitled ``Acknowledgements'',
+``Dedications'', or ``History'', the requirement (section @emph{4.
+Modifications}) to Preserve its Title (section @emph{1. Applicability
+and definitions}) will typically require changing the actual title.
+
+@subheading 9. Termination
+
+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.
+
+@subheading Future Revisions of this License
+
+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
+@url{http://www.gnu.org/copyleft/}.
+
+Each version of the License is given a distinguishing version number.
+If the Document specifies that a particular numbered version of this
+License ``or any later version'' 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.
+
+@subheading How to use this License for your documents
+
+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:
+
+@verbatim
+ 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 ``GNU Free Documentation License''.
+@end verbatim
+
+If you have Invariant Sections, Front-Cover Texts and Back-Cover
+Texts, replace the ``with...Texts''. line with this:
+
+@verbatim
+ with the Invariant Sections being LIST THEIR TITLES, with the
+ Front-Cover Texts being LIST, and with the Back-Cover Texts
+ being LIST.
+@end verbatim
+
+If you have Invariant Sections without Cover Texts, or some other
+combination of the three, merge those two alternatives to suit the
+situation.
+
+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.
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses/GPL.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses/GPL.texinfo
new file mode 100755
index 0000000..3349125
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/Licenses/GPL.texinfo
@@ -0,0 +1,376 @@
+Version 2, June 1991
+
+@verbatim
+Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 675 Mass Ave, Cambridge, MA 02139, USA
+@end verbatim
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+@subheading Preamble
+
+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.
+
+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.
+
+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.
+
+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.
+
+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.
+
+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.
+
+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.
+
+The precise terms and conditions for copying, distribution and
+modification follow.
+
+@subheading TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+@subsubheading Section 0
+
+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 ``Program'',
+below, refers to any such program or work, and a ``work based on the
+Program'' 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 ``modification''.) Each licensee is addressed
+as ``you''.
+
+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.
+
+@subsubheading Section 1
+
+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.
+
+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.
+
+@subsubheading Section 2
+
+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:
+
+a) You must cause the modified files to carry prominent notices
+stating that you changed the files and the date of any change.
+
+b) 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.
+
+c) 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. (Exception: 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.)
+
+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.
+
+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.
+
+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.
+
+@subsubheading Section 3
+
+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:
+
+a) 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,
+
+b) 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,
+
+c) 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.)
+
+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.
+
+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.
+
+@subsubheading Section 4
+
+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.
+
+@subsubheading Section 5
+
+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.
+
+@subsubheading Section 6
+
+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.
+
+@subsubheading Section 7
+
+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.
+
+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.
+
+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.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+@subsubheading Section 8
+
+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.
+
+@subsubheading Section 9
+
+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.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and ``any
+later version'', 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.
+
+@subsubheading Section 10
+
+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.
+
+@subsubheading NO WARRANTY
+
+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 ``AS IS'' 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.
+
+@subsubheading Section 12
+
+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.
+
+@strong{END OF TERMS AND CONDITIONS}
+
+@subheading How to Apply These Terms to Your New Programs
+
+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.
+
+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 ``copyright'' line and a pointer to where the full notice is
+found.
+
+@verbatim
+ <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.
+@end verbatim
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+@verbatim
+ 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.
+@end verbatim
+
+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.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a ``copyright disclaimer'' for the program, if
+necessary. Here is a sample; alter the names:
+
+@verbatim
+ 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
+@end verbatim
+
+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.
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual-index.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual-index.texinfo
new file mode 100755
index 0000000..b197b13
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual-index.texinfo
@@ -0,0 +1,8 @@
+@node Index
+@unnumbered Index
+@syncodeindex fn cp
+@syncodeindex vr cp
+@syncodeindex ky cp
+@syncodeindex pg cp
+@syncodeindex tp cp
+@printindex cp
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual-init.pl b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual-init.pl
new file mode 100755
index 0000000..c6eff54
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual-init.pl
@@ -0,0 +1,7 @@
+# This file extends the `../manual-init.pl' initialization file to
+# provide English specific initializations for `texi2html-1.76-4.fc6'.
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+return 1;
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual-menu.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual-menu.texinfo
new file mode 100644
index 0000000..0afc9ff
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual-menu.texinfo
@@ -0,0 +1,4 @@
+@menu
+* Licenses::
+* Index::
+@end menu
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual-nodes.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual-nodes.texinfo
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual-nodes.texinfo
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual.conf b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual.conf
new file mode 100755
index 0000000..72b65de
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual.conf
@@ -0,0 +1,36 @@
+# This file controls the manual configuration. This file is divided
+# in configuration sections (e.g., `main' and `templates') which, in
+# turn, are organized in the form `variable = value'.
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+[main]
+
+# Specify documentation backend used by documentation manual. This is
+# the format used to write documentation manual source files.
+manual_format = "texinfo"
+
+# Specify title style used by sections inside the manual. Possible
+# values to this option are `cap-each-word' to capitalize each word in
+# the section title, `cap-first-word' to capitalize the first word in
+# the section title only and `directory' to transform each word in the
+# section title into a directory path. From all these options,
+# `cap-each-word' is the one used as default.
+manual_section_style = "cap-each-word"
+
+# Specify the order used by sections inside the manual. By default new
+# sections added to the manual are put on the end to follow the
+# section `created' order. Other possible values to this option are
+# `ordered' and `reversed' to sort the list of sections alphabetically
+# from A-Z and Z-A, respectively.
+manual_section_order = "created"
+
+[templates]
+
+# Specify relation between template files and section definition files
+# inside the manual. Template definition is set on the left side using
+# relative path. The section main definition file is described on the
+# right using a regular expression. The first match wins.
+Chapters/section-functions.texinfo = "^.+-functions-[[:alnum:]]+\.texinfo$"
+Chapters/section.texinfo = "^.+\.texinfo$"
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual.sed b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual.sed
new file mode 100755
index 0000000..274b0f5
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual.sed
@@ -0,0 +1,40 @@
+#!/bin/sed
+#
+# repository.sed -- This file provide English transformations for
+# texi2html outupt, based on The CentOS Project CSS definitions.
+#
+# Copyright (C) 2009-2012 The CentOS Project
+#
+# 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., 59 Temple Place, Suite 330, Boston, MA 02111-1307
+# USA.
+#
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+# Quotations.
+s!<blockquote><p><strong>Note</strong>!<blockquote class="blue icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/note.png" alt="Info" /><h2>Note</h2><p>!g
+
+s!<blockquote><p><strong>Warning</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/warning.png" alt="Warning" /><h2>Warning</h2><p>!g
+
+s!<blockquote><p><strong>Important</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/important.png" alt="Important" /><h2>Important</h2><p>!g
+
+s!<blockquote><p><strong>Tip</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/tip.png" alt="Tip" /><h2>Tip</h2><p>!g
+
+s!<blockquote><p><strong>Caution</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/caution.png" alt="Caution" /><h2>Caution</h2><p>!g
+
+s!<blockquote><p><strong>Convention</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/ruler.png" alt="Convention" /><h2>Convention</h2><p>!g
+
+s!<blockquote><p><strong>Redirection</strong>!<blockquote class="blue icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/redirect.png" alt="Redirection" /><h2>Redirection</h2><p>!g
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual.texinfo
new file mode 100644
index 0000000..0a7f838
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/en_US/manual.texinfo
@@ -0,0 +1,74 @@
+\input texinfo @c -*-texinfo-*-
+@c -- Header --------------------------------------------------
+
+@setfilename =MANUAL_NAME=.info
+@settitle =MANUAL_TITLE=
+@documentlanguage =LOCALE_LL=
+@afourpaper
+@finalout
+
+@c -- Variables -----------------------------------------------
+
+@set TCENTOS The Community Enterprise Operating System
+@set TCPROJ @url{http://www.centos.org/, The CentOS Project}
+@set TCWIKI @url{http://wiki.centos.org/, The CentOS Wiki}
+@set TCMLISTS @url{http://lists.centos.org/, The CentOS Mailing Lists}
+@set TCBUGS @url{http://bugs.centos.org/, The CentOS Bugs}
+@set TCMIRRORS @url{http://mirrors.centos.org/, The CentOS Mirrors}
+@set TCPLANET @url{http://planet.centos.org/, The CentOS Planet}
+@set TCFORUMS @url{http://forums.centos.org/, The CentOS Forums}
+@set TCINFOML @email{centos-info@@centos.org, The CentOS Information Mailing List}
+@set TCDEVSML @email{centos-devel@@centos.org, The CentOS Developers Mailing List}
+@set TCDOCSML @email{centos-docs@@centos.org, The CentOS Documentation Mailing List}
+@set TCARTWML @email{centos-artwork@@centos.org, The CentOS Artwork Mailing List}
+@set TCL10NML @email{centos-l10n@@centos.org, The CentOS Localization Mailing List}
+@set TCAR @url{https://projects.centos.org/svn/artwork/, The CentOS Artwork Repository}
+@set TCAS @url{https://projects.centos.org/trac/artwork/, The CentOS Artwork SIG}
+
+@c -- Summary description and copyright -----------------------
+
+@copying
+=MANUAL_ABSTRACT=
+
+Copyright @copyright{} =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
+
+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 @ref{GNU Free
+Documentation License}.
+@end copying
+
+@c -- Titlepage, contents, copyright ---------------------------
+
+@titlepage
+@title =MANUAL_TITLE=
+@subtitle =MANUAL_SUBTITLE=
+@author =COPYRIGHT_HOLDER=
+@page
+@vskip 0pt plus 1filll
+@insertcopying
+@end titlepage
+@contents
+
+@c -- `Top' node and master menu -------------------------------
+
+@ifnottex
+@node Top
+@top =MANUAL_TITLE=
+@insertcopying
+@end ifnottex
+
+@include =MANUAL_NAME=-menu.texinfo
+
+@c -- The body of the document --------------------------------
+
+@include =MANUAL_NAME=-nodes.texinfo
+
+@c -- The end of the document ---------------------------------
+
+@include Licenses.texinfo
+@include =MANUAL_NAME=-index.texinfo
+
+@bye
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses-menu.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses-menu.texinfo
new file mode 100755
index 0000000..b8240ba
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses-menu.texinfo
@@ -0,0 +1,4 @@
+@menu
+* GNU General Public License::
+* GNU Free Documentation License::
+@end menu
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses-nodes.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses-nodes.texinfo
new file mode 100755
index 0000000..e7eded9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses-nodes.texinfo
@@ -0,0 +1,9 @@
+@node GNU General Public License
+@section Licencia Pública General de GNU
+@cindex Licencia pública general GNU
+@include Licenses/GPL.texinfo
+
+@node GNU Free Documentation License
+@section Licencia de Documentación Libre de GNU
+@cindex Licencia documentación libre GNU
+@include Licenses/GFDL.texinfo
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses.texinfo
new file mode 100755
index 0000000..be90966
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses.texinfo
@@ -0,0 +1,5 @@
+@node Licenses
+@appendix Licencias
+@cindex Licencias
+@include Licenses-menu.texinfo
+@include Licenses-nodes.texinfo
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses/GFDL.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses/GFDL.texinfo
new file mode 100755
index 0000000..8f789ec
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses/GFDL.texinfo
@@ -0,0 +1,372 @@
+@subheading Preámbulo
+
+El propósito de esta Licencia es permitir que un manual, libro de
+texto, u otro documento escrito sea «libre» en el sentido de libertad:
+asegurar a todo el mundo la libertad efectiva de copiarlo y
+redistribuirlo, con o sin modificaciones, de manera comercial o no. En
+segundo término, esta Licencia proporciona al autor y al editor una
+manera de obtener reconocimiento por su trabajo, sin que se le
+considere responsable de las modificaciones realizadas por otros.
+
+Esta Licencia es de tipo «copyleft», lo que significa que los trabajos
+derivados del documento deben a su vez ser libres en el mismo sentido.
+Complementa la Licencia Pública General de GNU, que es una licencia
+tipo copyleft diseñada para el software libre.
+
+Hemos diseñado esta Licencia para usarla en manuales de software
+libre, ya que el software libre necesita documentación libre: Un
+programa libre debe venir con los manuales que ofrezcan la mismas
+libertades que da el software. Pero esta licencia no se limita a
+manuales de software; puede ser usada para cualquier trabajo textual,
+sin tener en cuenta su temática o si se publica como libro impreso.
+Recomendamos esta licencia principalmente para trabajos cuyo fin sea
+instructivo o de referencia.
+
+@subheading 1. Aplicación y definiciones
+
+Esta Licencia se aplica a cualquier manual u otro trabajo que contenga
+un aviso colocado por el poseedor del copyright diciendo que puede
+distribuirse bajo los términos de esta Licencia. El «Documento»,
+abajo, se refiere a cualquier manual o trabajo. Cualquier miembro del
+público es un licenciatario,y será referido como «Usted».
+
+Una «Versión Modificada» del Documento significa cualquier trabajo que
+contenga el Documento o una porción del mismo, ya sea una copia
+literal o con modificaciones y/o traducciones a otro idioma.
+
+Una «Sección Secundaria» es un apéndice con título o una sección
+preliminar del Documento que trata exclusivamente de la relación entre
+los autores o editores y el tema general delDocumento que trata
+exclusivamente con la relación entre los editores o autores del
+Documento con el asunto general del Documento (o asuntos relacionados)
+y no contiene nada que pueda considerarse dentro del tema principal.
+(Por ejemplo, si el Documento es en parte un libro de texto de
+matemáticas, una Sección Secundaria no explicará nada de matemáticas.)
+La relación puede ser una conexión histórica con el asunto o temas
+relacionados, o una opinión legal, comercial, filosófica, ética o
+política acerca de ellos.
+
+Las «Secciones Invariantes» son ciertas Secciones Secundarias cuyos
+títulos son designados como Secciones Invariantes en la nota que
+indica que el Documento se publica bajo esta Licencia.
+
+Los «Textos de Cubierta» son ciertos pasajes cortos de texto que se
+listan como Textos de Cubierta Delantera o Textos de Cubierta Trasera
+en la nota que indica que el Documento se publica bajo esta Licencia.
+
+Una copia «Transparente» del Documento, significa una copia para
+lectura en máquina, representada en un formato cuya especificación
+está disponible al público en general, cuyo contenido puede ser visto
+y editados directamente con editores de texto genéricos o (para
+imágenes compuestas por píxeles) con programas genéricos de
+manipulación de imágenes o (para dibujos) con algún editor de dibujos
+ampliamente disponible, y que sea adecuado como entrada para
+formateadores de texto o para su traducción automática a formatos
+adecuados para formateadores de texto. Una copia hecha en un formato
+definido como Transparente, pero cuyo marcaje o ausencia de él haya
+sido diseñado para impedir o dificultar modificaciones posteriores por
+parte de los lectores no es Transparente. Una copia que no es
+«Transparente» se denomina «Opaca».
+
+Como ejemplos de formatos adecuados para copias Transparentes están
+ASCII puro sin marcaje, formato de entrada de Texinfo, formato de
+entrada de LaTeX, SGML o XML usando una DTD disponible públicamente, y
+HTML, PostScript o PDF simples, que sigan los estándares y diseños
+para que los modifiquen personas.Los formatos Opacos incluyen formatos
+propietarios que pueden ser leídos y editados únicamente en
+procesadores de textos propietarios, SGML o XML para los cuáles las
+DTD y/o herramientas de procesamiento no estén ampliamente
+disponibles, y HTML, PostScript o PDF generados por algunos
+procesadores de textos sólo como salida.
+
+La «Portada» significa, en un libro impreso, la página de título, más
+las páginas siguientes que sean necesarias para mantener legiblemente
+el material que esta Licencia requiere en la portada. Para trabajos en
+formatos que no tienen página de portada como tal, «Portada»significa
+el texto cercano a la aparición más prominente del título del
+trabajo,precediendo el comienzo del cuerpo del texto.
+
+@subheading 2. Copia literal
+
+Usted puede copiar y distribuir el Documento en cualquier medio, sea
+en forma comercial o no, siempre y cuando proporcione esta Licencia,
+las notas de copyright y la nota que indica que esta Licencia se
+aplica al Documento reproduciéndola en todas las copias y que usted no
+añada ninguna otra condición a las expuestas en esta Licencia. Usted
+no puede usar medidas técnicas para obstruir o controlar la lectura o
+copia posterior de las copias que usted haga o distribuya. Sin
+embargo, usted puede aceptar compensación a cambio de las copias. Si
+distribuye un número suficientemente grande de copias también deberá
+seguir las condiciones de la sección 3.
+
+Usted también puede prestar copias, bajo las mismas condiciones
+establecidas anteriormente, y puede exhibir copias públicamente.
+
+@subheading 3. Copiando en cantidad
+
+Si publica copias impresas del Documento que sobrepasen las 100, y la
+nota de licencia del Documento exige Textos de Cubierta, debe
+incluirlas copias con cubiertas que lleven en forma clara y legible
+todos esos Textos de Cubierta: Textos de Cubierta Delantera en la
+cubierta delantera y Textos de Cubierta Trasera en la cubierta
+trasera. Ambas cubiertas deben identificarlo a Usted clara y
+legiblemente como editor de tales copias. La cubierta debe mostrar el
+título completo con todas las palabras igualmente prominentes y
+visibles. Además puede añadir otro material en las cubiertas. Las
+copias con cambios limitados a las cubiertas, siempre que conserven el
+título del Documento y satisfagan estas condiciones, pueden
+considerarse como copias literales en todos los aspectos.
+
+Si los textos requeridos para la cubierta son muy voluminosos para que
+ajusten legiblemente, debe colocar los primeros (tantos como sea
+razonable colocar) en la verdadera cubierta y situar el resto en
+páginas adyacentes.
+
+Si Usted publica o distribuye copias Opacas del Documento cuya
+cantidad exceda las 100, debe incluir una copia Transparente, que
+pueda ser leída por una máquina, con cada copia Opaca, o bien mostrar,
+en cada copia Opaca, una dirección de red donde cualquier usuario de
+la misma tenga acceso por medio de protocolos públicos y
+estandarizados a una copia Transparente del Documento completa, sin
+material adicional. Si usted hace uso de la última opción, deberá
+tomar las medidas necesarias, cuando comience la distribución de las
+copias Opacas en cantidad, para asegurar que esta copia Transparente
+permanecerá accesible en el sitio establecido por lo menos un año
+después de la última vez que distribuya una copia Opaca de esa edición
+al público (directamente o a través de sus agentes o distribuidores).
+
+Se solicita, aunque no es requisito, que se ponga en contacto con los
+autores del Documento antes de redistribuir gran número de copias,
+para darles la oportunidad de que le proporcionen una versión
+actualizada del Documento.
+
+@subheading 4. Modificaciones
+
+Puede copiar y distribuir una Versión Modificada del Documento bajo
+las condiciones de las secciones 2 y 3 anteriores, siempre que Usted
+libere la Versión Modificada bajo esta misma Licencia, con la Versión
+Modificada haciendo el rol del Documento, por lo tanto dando Licencia
+de distribución y modificación de la Versión Modificada a quienquiera
+posea una copia de la misma. Además, debe hacer lo siguiente en la
+Versión Modificada:
+
+A. Usar en la Portada (y en las cubiertas, si hay alguna) un título
+distinto al del Documento y de sus versiones anteriores (que deberían,
+si hay alguna, estar listadas en la sección de Historia del
+Documento). Puede usar el mismo título de versiones anteriores al
+original siempre y cuando quien las publicó originalmente otorgue
+permiso.
+
+B. Listar en la Portada, como autores, una o más personas o entidades
+responsables de la autoría de las modificaciones de la Versión
+Modificada, junto con por lo menos cinco de los autores principales
+del Documento (todos sus autores principales, si hay menos de cinco),
+a menos que le eximan de tal requisito.
+
+C. Mostrar en la Portada como editor el nombre del editor de la
+Versión Modificada
+
+D. Conservar todas las notas de copyright del Documento.
+
+E. Añadir una nota de copyright apropiada a sus modificaciones,
+adyacente a las otras notas de copyright.
+
+F. Incluir, inmediatamente después de los avisos de copyright, una
+nota de licencia dando el permiso público para usar la Versión
+Modificada bajo los términos de esta Licencia, de la forma mostrada en
+el Adenda de más abajo.
+
+G. Incluir, inmediatamente después de ese aviso de licencia, la lista
+completa de Secciones invariantes y de los Textos de Cubierta que sean
+requeridos en el aviso de Licencia del Documento original.
+
+H. Incluir una copia sin modificación de esta Licencia.
+
+I. Conservar la sección titulada «Historia», conservar su Título y
+añadirle un elemento que declare al menos el título, el año, los
+nuevos autores y el editor de la Versión Modificada, tal como figuran
+en la Portada. Si no hay una sección titulada «Historia» en el
+Documento, crear una estableciendo el título, el año, los autores y el
+editor del Documento, tal como figuran en su Portada, añadiendo además
+un elemento describiendo la Versión Modificada, como se estableció en
+la sentencia anterior.
+
+J. Conservar la dirección en red, si la hay, dada en el Documento para
+el acceso público a una copia Transparente del mismo, así como las
+otras direcciones de red dadas en el Documento para versiones
+anteriores en las que estuviese basado. Pueden ubicarse en la sección
+«Historia». Se puede omitir la ubicación en red de un trabajo que haya
+sido publicado por lo menos cuatro años antes que el Documento mismo,
+o si el editor original de dicha versión da permiso.
+
+K. En cualquier sección titulada «Agradecimientos» o «Dedicatorias»,
+conservar el título de la sección y conservar en ella toda la
+sustancia y el tono de los agradecimientos y/o dedicatorias incluidas
+por cada contribuyente.
+
+L. Conservar todas las Secciones Invariantes del Documento, sin
+alterar su texto ni sus títulos. Los números de sección o equivalentes
+no se consideran parte de los títulos de la sección.
+
+M. Borrar cualquier sección titulada «Aprobaciones». Tales secciones
+no pueden estar incluidas en las Versiones Modificadas.
+
+N. No cambiar el título de ninguna sección existente a «Aprobaciones»
+ni a uno que entre en conflicto con el de alguna Sección Invariante.
+
+Si la Versión Modificada incluye secciones o apéndices nuevos que
+cualifiquen como Secciones Secundarias y no contienen ningún material
+copiado del Documento, puede opcionalmente designar algunas o todas
+esas secciones como invariantes. Para hacerlo, añada sus títulos a la
+lista de Secciones Invariantes en el aviso de licencia de la Versión
+Modificada. Tales títulos deben ser distintos de cualquier otro título
+de sección.
+
+Puede añadir una sección titulada «Aprobaciones», siempre que contenga
+únicamente aprobaciones de su Versión Modificada por otras fuentes
+--por ejemplo, observaciones de compañeros o que el texto ha sido
+aprobado por una organización como definición oficial de un estándar.
+
+Puede añadir un pasaje de hasta cinco palabras como Texto de Cubierta
+Delantera y un pasaje de hasta 25 palabras como Texto de Cubierta
+Trasera al final de la lista de Texto de Cubierta en la Versión
+Modificada. Una entidad sólo puede añadir (o hacer que se añada) un
+pasaje al Texto de Cubierta Delantera y uno al de Cubierta Trasera. Si
+el Documento ya incluye un textos de cubiertas añadidos previamente
+por usted o por acuerdo previo con la entidad que usted representa,
+usted no puede añadir otro; pero puede reemplazar el anterior, con
+permiso explícito del editor anterior que agregó el texto anterior.
+
+Con esta Licencia ni los autores ni los editores del Documento dan
+permiso para usar sus nombres para publicidad ni para asegurar o
+implicar aprobación de cualquier Versión Modificada.
+
+@subheading 5. Combinación de documentos
+
+Usted puede combinar el Documento con otros documentos liberados bajo
+esta Licencia, bajo los términos definidos en la sección section 4 más
+arriba para versiones modificadas, siempre que incluya en la
+combinación todas las Secciones Invariantes de todos los documentos
+originales, sin modificaciones, y las liste todas como Secciones
+Invariantes de su trabajo combinado en su aviso de licencia.
+
+El trabajo combinado necesita contener solamente una copia de esta
+Licencia, y múltiples Secciones Invariantes idénticas pueden
+reemplazarse por una sola copia. Si hay múltiples Secciones
+Invariantes con el mismo nombre pero con contenidos diferentes, haga
+el título de cada una de estas secciones único añadiéndolo al final de
+este, entre paréntesis, el nombre del autor o de quien editó
+originalmente esa sección, si es conocido, o si no, un número único.
+Haga el mismo ajuste a los títulos de sección en la lista de Secciones
+Invariantes en la nota de licencia del trabajo combinado.
+
+En la combinación, debe combinar cualquier sección titulada «Historia»
+de los distintos documentos originales, formando una sección titulada
+«Historia»; de la misma forma, combine cualquier sección titulada
+«Reconocimientos» y cualquier sección titulada «Dedicatorias». Debe
+borrar todas las secciones tituladas «Aprobaciones».
+
+@subheading 6. Colecciones de documentos
+
+Puede hacer una colección que conste del Documento y de otros
+documentos publicados bajo esta Licencia, y reemplazar las copias
+individuales de esta Licencia en todos los documentos por una sola
+copia que esté incluida en la colección, siempre que siga las reglas
+de esta Licencia para cada copia literal de cada uno de los documentos
+en cualquiera de los demás aspectos.
+
+Puede extraer un solo documento de una de tales colecciones y
+distribuirlo individualmente bajo esta Licencia, siempre que inserte
+una copia de esta Licencia en el documento extraído, y siga esta
+Licencia en todos los demás aspectos relativos a la copia literal de
+dicho documento.
+
+@subheading 7. Agregación con trabajos independientes
+
+Una recopilación que conste del Documento o sus derivados y de otros
+documentos o trabajos separados e independientes, en cualquier soporte
+de almacenamiento o distribución, no cuenta como un todo como una
+Versión Modificada del Documento, siempre que no se reclame ningún
+derecho de copyright por la compilación. Dicha compilación se denomina
+un «agregado», y esta Licencia no se aplica a otros trabajos
+autocontenidos incluidos con el Documento. teniendo en cuenta que son
+compilados, si no son los mismos trabajos derivados del Documento. Si
+el requisito de Texto de Cubierta de la sección 3 es aplicable a estas
+copias del Documento, entonces si el Documento es menor que un cuarto
+del agregado completo, los Textos de Cubierta del Documento pueden
+colocarse en cubiertas que enmarquen solamente el Documento dentro del
+agregado. En caso contrario deben aparecer en cubiertas impresas
+enmarcando todo el agregado.
+
+@subheading 8. Traducción
+
+La Traducción se considera como un tipo de modificación, por lo que
+usted puede distribuir traducciones del Documento bajo los términos de
+la sección 4. El reemplazo las Secciones Invariantes por traducciones
+requiere permiso especial de los poseedores del copyright, pero usted
+puede incluir traducciones de algunas o todas las Secciones
+Invariantes junto con las versiones originales de las mismas. Puede
+incluir una traducción de esta Licencia, siempre que incluya también
+la versión original en inglés de esta Licencia. En caso de desacuerdo
+entre la traducción y la versión original en inglés de esta Licencia,
+la versión original en Inglés prevalecerá.
+
+@subheading 9. Terminación
+
+Usted no puede copiar, modificar, sublicenciar o distribuir el
+Documento salvo por lo permitido expresamente por esta Licencia.
+Cualquier otro intento de copia, modificación, sublicenciamiento o
+distribución del Documento es nulo, y dará por terminados
+automáticamente sus derechos bajo esa Licencia. Sin embargo, los
+terceros que hayan recibido copias, o derechos, de usted bajo esta
+Licencia no verán terminadas sus licencias, siempre que permanezcan en
+total conformidad con ella.
+
+@subheading Revisiones futuras de esta licencia
+
+La Free Software Foundation puede publicar versiones nuevas y
+revisadas de la Licencia de Documentación Libre GNU de vez en cuando.
+Dichas versiones nuevas serán similares en espíritu a la presente
+versión, pero pueden diferir en detalles para solucionar nuevos
+problemas o preocupaciones. Vea @url{http://www.gnu.org/copyleft/}.
+
+Cada versión de la Licencia tiene un número de versión que la
+distingue. Si el Documento especifica que se aplica una versión
+numerada en particular de esta licencia o «cualquier versión
+posterior», usted tiene la opción de seguir los términos y condiciones
+de la versión especificada o cualquiera posterior que haya sido
+publicada (no como borrador) por la Free Software Foundation. Si el
+Documento no especifica un número de versión de esta Licencia, puede
+escoger cualquier versión que haya sido publicada (no como borrador)
+por la Free Software Foundation.
+
+@subheading Adenda
+
+Para usar esta licencia en un documento que usted haya escrito,
+incluya una copia de la Licencia en el documento y ponga el siguiente
+copyright y notificación de licencia justo después de la página de
+título:
+
+@example
+Copyright © AÑO SU NOMBRE.
+
+Se otorga permiso para copiar, distribuir y/o modificar este documento
+bajo los términos de la Licencia de Documentación Libre de GNU,
+Versión 1.1 o cualquier otra versión posterior publicada por la
+Free Software Foundation; con las Secciones Invariantes siendo su
+LISTE SUS TÍTULOS, con Textos de Cubierta Delantera siendo LISTA, y
+con los Textos de Cubierta Trasera siendo LISTA. Una copia de la
+licencia está incluida en la sección titulada «GNU Free
+Documentation License».
+@end example
+
+Si no tiene Secciones Invariantes, escriba «sin Secciones Invariantes»
+en vez de decir cuáles son invariantes. Si no tiene Textos de Cubierta
+Frontal, escriba «sin Textos de Cubierta Frontal»; de la misma manera
+para Textos de Cubierta Trasera.
+
+Si su documento contiene ejemplos de código de programa no triviales,
+recomendamos liberar estos ejemplos en paralelo bajo la licencia de
+software libre que usted elija, como la Licencia Pública General de
+GNU (@pxref{GNU General Public License}), para permitir su uso en
+software libre.
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses/GPL.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses/GPL.texinfo
new file mode 100755
index 0000000..79680fe
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/Licenses/GPL.texinfo
@@ -0,0 +1,329 @@
+@subheading Preámbulo
+
+Las licencias que cubren la mayor parte del software están diseñadas
+para quitarle a usted la libertad de compartirlo y modificarlo. Por el
+contrario, la Licencia Pública General de GNU pretende garantizarle la
+libertad de compartir y modificar software libre, para asegurar que el
+software es libre para todos sus usuarios. Esta Licencia Pública
+General se aplica a la mayor parte del software del la Free Software
+Foundation y a cualquier otro programa si sus autores se comprometen a
+utilizarla. (Existe otro software de la Free Software Foundation que
+está cubierto por la Licencia Pública General de GNU para
+Bibliotecas). Si quiere, también puede aplicarla a sus propios
+programas.
+
+Cuando hablamos de software libre, estamos refiriéndonos a libertad,
+no a precio. Nuestras Licencias Públicas Generales están diseñadas
+para asegurarnos de que tenga la libertad de distribuir copias de
+software libre (y cobrar por ese servicio si quiere), de que reciba el
+código fuente o que pueda conseguirlo si lo quiere, de que pueda
+modificar el software o usar fragmentos de él en programas nuevos
+libres, y de que sepa que puede hacer todas estas cosas.
+
+Para proteger sus derechos necesitamos algunas restricciones que
+prohíban a cualquiera negarle a usted estos derechos o pedirle que
+renuncie a ellos. Estas restricciones se traducen en ciertas
+obligaciones que le afectan si distribuye copias del software, o si lo
+modifica.
+
+Por ejemplo, si distribuye copias de uno de estos programas, sea
+gratuitamente, o a cambio de una contraprestación, debe dar a los
+receptores todos los derechos que tiene. Debe asegurarse de que ellos
+también reciben, o pueden conseguir, el código fuente. Y debe
+mostrarles estas condiciones de forma que conozcan sus derechos.
+
+Protegemos sus derechos con la combinación de dos medidas:
+
+@itemize
+@item Derechos de copia del software (copyright), y
+@item Le ofrecemos esta licencia, que le da permiso legal para copiar,
+distribuir y/o modificar el software.
+@end itemize
+
+También, para la protección de cada autor y la nuestra propia,
+queremos asegurarnos de que todo el mundo comprende que no se
+proporciona ninguna garantía para este software libre. Si el software
+se modifica por cualquiera y éste a su vez lo distribuye, queremos que
+sus receptores sepan que lo que tienen no es el original, de forma que
+cualquier problema introducido por otros no afecte a la reputación de
+los autores originales.
+
+Finalmente, cualquier programa libre está constantemente amenazado por
+patentes sobre el software. Queremos evitar el peligro de que los
+redistribuidores de un programa libre obtengan patentes por su cuenta,
+convirtiendo de facto el programa en propietario. Para evitar esto,
+hemos dejado claro que cualquier patente debe ser pedida para el uso
+libre de cualquiera, o no ser pedida.
+
+Los términos precisos y las condiciones para la copia, distribución y
+modificación se exponen a continuación.
+
+@subheading TÉRMINOS Y CONDICIONES PARA LA COPIA, DISTRIBUCIÓN Y MODIFICACIÓN
+
+@subsubheading Sección 0
+
+Esta Licencia se aplica a cualquier programa u otro tipo de obra que
+contenga una notificación colocada por el propietario del copyright
+diciendo que puede distribuirse bajo los términos de esta Licencia
+Pública General. El «Programa», en adelante, se referirá a cualquier
+programa u obra, y «obra basada en el Programa» se referirá bien al
+Programa o a cualquier trabajo derivado de él según la ley de derechos
+de autor (copyright): Esto es, una obra o trabajo que contenga el
+programa o una porción de él, bien en forma literal o con
+modificaciones y/o traducido en otro lenguaje. Aquí y después, la
+traducción está incluida sin limitación en el término «modificación».
+Cada concesionario (licenciatario) será denominado «usted».
+
+Cualquier otra actividad que no sea la copia, distribución o
+modificación no está cubierta por esta Licencia, está fuera de su
+ámbito. El acto de ejecutar el Programa no está restringido, y los
+resultados del Programa están cubiertos únicamente si sus contenidos
+constituyen un trabajo basado en el Programa, independientemente de
+haberlo producido mediante la ejecución del programa. El que esto se
+cumpla, depende de lo que haga el programa.
+
+@subsubheading Sección 1
+
+Usted puede copiar y distribuir copias literales del código fuente del
+Programa, según lo has recibido, en cualquier medio, supuesto que de
+forma adecuada y bien visible publique en cada copia un anuncio de
+copyright adecuado y un repudio de garantía, mantenga intactos todos
+los anuncios que se refieran a esta Licencia y a la ausencia de
+garantía, y proporcione a cualquier otro receptor del programa una
+copia de esta Licencia junto con el Programa.
+
+Puede cobrar un precio por el acto físico de transferir una copia, y
+puede, según su libre albedrío, ofrecer garantía a cambio de unos
+honorarios.
+
+@subsubheading Sección 2
+
+Puede modificar su copia o copias del Programa o de cualquier porción
+de él, formando de esta manera un trabajo basado en el Programa, y
+copiar y distribuir esa modificación o trabajo bajo los términos de la
+Sección 1 anterior, probado que además usted cumpla con todas las
+siguientes condiciones:
+
+@enumerate
+@item Debe hacer que los ficheros modificados lleven anuncios
+prominentes indicando que los ha cambiado y la fecha de cualquier
+cambio.
+
+@item Debe hacer que cualquier trabajo que distribuya o publique y que
+en todo o en parte contenga o sea derivado del Programa o de cualquier
+parte de él sea licenciada como un todo, sin carga alguna, a todas las
+terceras partes y bajo los términos de esta Licencia.
+
+@item 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.
+
+Excepción: Si el propio Programa es interactivo pero normalmente no
+muestra ese anuncio, no se requiere que su trabajo basado en el
+Programa muestre ningún anuncio.
+
+@end enumerate
+
+Estos requisitos se aplican al trabajo modificado como un todo. Si
+partes identificables de ese trabajo no son derivadas del Programa, y
+pueden, razonablemente, ser consideradas trabajos independientes y
+separados por ellos mismos, entonces esta Licencia y sus términos no
+se aplican a esas partes cuando sean distribuidas como trabajos
+separados. Pero cuando distribuya esas mismas secciones como partes de
+un todo que es un trabajo basado en el Programa, la distribución del
+todo debe ser según los términos de esta licencia, cuyos permisos para
+otros licenciatarios se extienden al todo completo, y por lo tanto a
+todas y cada una de sus partes, con independencia de quién la
+escribió.
+
+Por lo tanto, no es la intención de este apartado reclamar derechos o
+desafiar sus derechos sobre trabajos escritos totalmente por usted
+mismo. El intento es ejercer el derecho a controlar la distribución de
+trabajos derivados o colectivos basados en el Programa.
+
+Además, el simple hecho de reunir un trabajo no basado en el Programa
+con el Programa (o con un trabajo basado en el Programa) en un volumen
+de almacenamiento o en un medio de distribución no hace que dicho
+trabajo entre dentro del ámbito cubierto por esta Licencia.
+
+@subsubheading Sección 3
+
+Puede copiar y distribuir el Programa (o un trabajo basado en él,
+según se especifica en la Sección 2, como código objeto o en formato
+ejecutable según los términos de las Secciones 1 y 2 anteriores,
+supuesto que además cumpla una de las siguientes condiciones:
+
+@enumerate
+
+@item Acompañarlo con el código fuente leíble completo
+correspondiente, leíble por máquinas, que debe ser distribuido según
+los términos las Secciones 1 y 2 mencionadas antes en un medio
+habitualmente utilizado para el intercambio de software, o,
+
+@item Acompañarlo con una oferta por escrito, válida durante al menos
+tres años, de proporcionar a cualquier tercera parte una copia
+completa en formato electrónico del código fuente correspondiente, a
+un coste no mayor que el de realizar físicamente la distribución del
+fuente, que será distribuido bajo las condiciones descritas en los
+apartados 1 y 2 anteriores, en un medio habitualmente utilizado para
+el intercambio de programas, o
+
+@item Acompañarlo con la información que recibiste ofreciendo
+distribuir el código fuente correspondiente. (Esta opción se permite
+sólo para distribución no comercial y sólo si usted recibió el
+programa como código objeto o en formato ejecutable con tal oferta, de
+acuerdo con la Subsección b anterior).
+@end enumerate
+
+Por código fuente de un trabajo se entiende la forma preferida del
+trabajo cuando se le hacen modificaciones. Para un trabajo ejecutable,
+se entiende por código fuente completo todo el código fuente para
+todos los módulos que contiene, más cualquier fichero asociado de
+definición de interfaces, más los guiones utilizados para controlar la
+compilación e instalación del ejecutable. Como excepción especial el
+código fuente distribuido no necesita incluir nada que sea distribuido
+normalmente (bien como fuente, bien en forma binaria) con los
+componentes principales (compilador, núcleo y similares) del sistema
+operativo en el cual funciona el ejecutable, a no ser que el propio
+componente acompañe al ejecutable.
+
+Si la distribución del ejecutable o del código objeto se hace mediante
+la oferta acceso para copiarlo de un cierto lugar, entonces se
+considera la oferta de acceso para copiar el código fuente del mismo
+lugar como distribución del código fuente, incluso aunque terceras
+partes no estén forzadas a copiar el fuente junto con el código
+objeto.
+
+@subsubheading Sección 4
+
+No puede copiar, modificar, sublicenciar o distribuir el Programa
+excepto como prevé expresamente esta Licencia. Cualquier intento de
+copiar, modificar sublicenciar o distribuir el Programa de otra forma
+es inválida, y hará que cesen automáticamente los derechos que te
+proporciona esta Licencia. En cualquier caso, las partes que hayan
+recibido copias o derechos de usted bajo esta Licencia no cesarán en
+sus derechos mientras esas partes continúen cumpliéndola. 5Sección 5
+
+No está obligado a aceptar esta licencia, ya que no la ha firmado. Sin
+embargo, no hay hada más que le proporcione permiso para modificar o
+distribuir el Programa o sus trabajos derivados. Estas acciones están
+prohibidas por la ley si no acepta esta Licencia. Por lo tanto, si
+modifica o distribuye el Programa (o cualquier trabajo basado en el
+Programa), está indicando que acepta esta Licencia para poder hacerlo,
+y todos sus términos y condiciones para copiar, distribuir o modificar
+el Programa o trabajos basados en él. 6Sección 6
+
+Cada vez que redistribuya el Programa (o cualquier trabajo basado en
+el Programa), el receptor recibe automáticamente una licencia del
+licenciatario original para copiar, distribuir o modificar el
+Programa, de forma sujeta a estos términos y condiciones. No puede
+imponer al receptor ninguna restricción más sobre el ejercicio de los
+derechos aquí garantizados. No es usted responsable de hacer cumplir
+esta licencia por terceras partes. 7Sección 7
+
+Si como consecuencia de una resolución judicial o de una alegación de
+infracción de patente o por cualquier otra razón (no limitada a
+asuntos relacionados con patentes) se le imponen condiciones (ya sea
+por mandato judicial, por acuerdo o por cualquier otra causa) que
+contradigan las condiciones de esta Licencia, ello no le exime de
+cumplir las condiciones de esta Licencia. Si no puede realizar
+distribuciones de forma que se satisfagan simultáneamente sus
+obligaciones bajo esta licencia y cualquier otra obligación pertinente
+entonces, como consecuencia, no puede distribuir el Programa de
+ninguna forma. Por ejemplo, si una patente no permite la
+redistribución libre de derechos de autor del Programa por parte de
+todos aquellos que reciban copias directa o indirectamente a través de
+usted, entonces la única forma en que podría satisfacer tanto esa
+condición como esta Licencia sería evitar completamente la
+distribución del Programa.
+
+Si cualquier porción de este apartado se considera inválida o
+imposible de cumplir bajo cualquier circunstancia particular ha de
+cumplirse el resto y la sección por entero ha de cumplirse en
+cualquier otra circunstancia.
+
+No es el propósito de este apartado inducirle a infringir ninguna
+reivindicación de patente ni de ningún otro derecho de propiedad o
+impugnar la validez de ninguna de dichas reivindicaciones. Este
+apartado tiene el único propósito de proteger la integridad del
+sistema de distribución de software libre, que se realiza mediante
+prácticas de licencia pública. Mucha gente ha hecho contribuciones
+generosas a la gran variedad de software distribuido mediante ese
+sistema con la confianza de que el sistema se aplicará
+consistentemente. Será el autor/donante quien decida si quiere
+distribuir software mediante cualquier otro sistema y una licencia no
+puede imponer esa elección.
+
+Este apartado pretende dejar completamente claro lo que se cree que es
+una consecuencia del resto de esta Licencia.
+
+@subsubheading Sección 8
+
+Si la distribución y/o uso de el Programa está restringida en ciertos
+países, bien por patentes o por interfaces bajo copyright, el tenedor
+del copyright que coloca este Programa bajo esta Licencia puede añadir
+una limitación explícita de distribución geográfica excluyendo esos
+países, de forma que la distribución se permita sólo en o entre los
+países no excluidos de esta manera. En ese caso, esta Licencia
+incorporará la limitación como si estuviese escrita en el cuerpo de
+esta Licencia. 9Sección 9
+
+La Free Software Foundation puede publicar versiones revisadas y/o
+nuevas de la Licencia Pública General de tiempo en tiempo. Dichas
+nuevas versiones serán similares en espíritu a la presente versión,
+pero pueden ser diferentes en detalles para considerar nuevos
+problemas o situaciones.
+
+Cada versión recibe un número de versión que la distingue de otras. Si
+el Programa especifica un número de versión de esta Licencia que se
+aplica aplica a éste y a «cualquier versión posterior», usted tiene la
+opción de seguir los términos y condiciones, bien de esa versión, bien
+de cualquier versión posterior publicada por la Free Software
+Foundation. Si el Programa no especifica un número de versión de esta
+Licencia, usted puede escoger cualquier versión publicada por la Free
+Software Foundation.
+
+@subsubheading Sección 10
+
+Si quiere incorporar partes del Programa en otros programas libres
+cuyas condiciones de distribución son diferentes, escribe al autor
+para pedirle permiso. Si el software tiene copyright de la Free
+Software Foundation, escribe a la Free Software Foundation: algunas
+veces hacemos excepciones en estos casos. Nuestra decisión estará
+guiada por el doble objetivo de de preservar la libertad de todos los
+derivados de nuestro software libre y promover el que se comparta y
+reutilice el software en general.
+
+@subsubheading AUSENCIA DE GARANTÍA
+
+Sección 11
+
+DEBIDO A QUE EL PROGRAMA SE LICENCIA LIBRE DE CARGAS, NO SE OFRECE
+NINGUNA GARANTÍA SOBRE EL PROGRAMA, EN TODA LA EXTENSIÓN PERMITIDA POR
+LA LEGISLACIÓN APLICABLE. EXCEPTO CUANDO SE INDIQUE DE OTRA FORMA POR
+ESCRITO, LOS PROPIETARIOS DEL COPYRIGHT Y/U OTRAS PARTES PROPORCIONAN
+EL PROGRAMA «TAL CUAL», SIN GARANTÍA DE NINGUNA CLASE, BIEN EXPRESA O
+IMPLÍCITA, CON INCLUSIÓN, PERO SIN LIMITACIÓN A LAS GARANTÍAS
+MERCANTILES IMPLÍCITAS O A LA CONVENIENCIA PARA UN PROPÓSITO
+PARTICULAR. CUALQUIER RIESGO REFERENTE A LA CALIDAD Y PRESTACIONES DEL
+PROGRAMA ES ASUMIDO POR USTED. SI SE PROBASE QUE EL PROGRAMA ES
+DEFECTUOSO, USTED ASUME EL COSTE DE CUALQUIER SERVICIO, REPARACIÓN O
+CORRECCIÓN NECESARIO.
+
+@subsubheading Sección 12
+
+EN NINGÚN CASO, SALVO QUE LO REQUIERA LA LEGISLACIÓN APLICABLE O HAYA
+SIDO ACORDADO POR ESCRITO, NINGÚN TENEDOR DEL COPYRIGHT NI NINGUNA
+OTRA PARTE QUE MODIFIQUE Y/O REDISTRIBUYA EL PROGRAMA SEGÚN SE PERMITE
+EN ESTA LICENCIA SERÁ RESPONSABLE ANTE USTED POR DAÑOS, INCLUYENDO
+CUALQUIER DAÑO GENERAL, ESPECIAL, INCIDENTAL O RESULTANTE PRODUCIDO
+POR EL USO O LA IMPOSIBILIDAD DE USO DEL PROGRAMA (CON INCLUSIÓN, PERO
+SIN LIMITACIÓN A LA PÉRDIDA DE DATOS O A LA GENERACIÓN INCORRECTA DE
+DATOS O A PÉRDIDAS SUFRIDAS POR USTED O POR TERCERAS PARTES O A UN
+FALLO DEL PROGRAMA AL FUNCIONAR EN COMBINACIÓN CON CUALQUIER OTRO
+PROGRAMA), INCLUSO SI DICHO TENEDOR U OTRA PARTE HA SIDO ADVERTIDO DE
+LA POSIBILIDAD DE DICHOS DAÑOS.
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual-index.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual-index.texinfo
new file mode 100755
index 0000000..bed8139
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual-index.texinfo
@@ -0,0 +1,8 @@
+@node Index
+@unnumbered Índice
+@syncodeindex fn cp
+@syncodeindex vr cp
+@syncodeindex ky cp
+@syncodeindex pg cp
+@syncodeindex tp cp
+@printindex cp
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual-init.pl b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual-init.pl
new file mode 100755
index 0000000..d8e2045
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual-init.pl
@@ -0,0 +1,119 @@
+# This file extends the '../manual-init.pl' initialization file to # provide Spanish translation messages for `texi2html-1.76-4.fc6'.
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+$LANGUAGES->{'es'} = {
+ ' The buttons in the navigation panels have the following meaning:' => 'Los botones en el panel de navegación tienen el significado siguiente:',
+ ' where the @strong{ Example } assumes that the current position is at @strong{ Subsubsection One-Two-Three } of a document of the following structure:' => 'donde el @strong{Ejemplo} asume que la posición actual es en @strong{Subsubsección Uno-Dos-Tres}',
+ ' Up ' => 'Arriba',
+ '%{acronym_like} (%{explanation})' => '',
+ '%{month}, %{day} %{year}' => '',
+ '%{name} of %{class}' => '%{name} de %{class}',
+ '%{name} on %{class}' => '%{name} en %{class}',
+ '%{node_file_href}' => '',
+ '%{node_file_href} @cite{%{book}}' => '',
+ '%{node_file_href} section `%{section}\' in @cite{%{book}}' => 'sección %{node_file_href} `%{section}\' en @cite{%{book}}',
+ '%{reference_name}' => '',
+ '%{style} %{number}' => '',
+ '%{style}: %{caption_first_line}' => '',
+ '%{style}: %{shortcaption_first_line}' => '',
+ '@b{%{quotation_arg}:} ' => '',
+ '@cite{%{book}}' => '',
+ 'About This Document' => 'Acerca de este documento',
+ 'April' => 'abril',
+ 'August' => 'agosto',
+ 'Button' => 'Botón',
+ 'Contents' => 'Contenidos',
+ 'Current Position' => 'Posición actual',
+ 'December' => 'diciembre',
+ 'February' => 'febrero',
+ 'Footnotes' => 'Pie de página',
+ 'From 1.2.3 go to' => 'Desde 1.2.3 va a',
+ 'Go to' => 'Ir a',
+ 'Index' => 'Índice',
+ 'Index Entry' => 'Entrada índice',
+ 'January' => 'enero',
+ 'July' => 'julio',
+ 'Jump to' => 'Saltar a',
+ 'June' => 'junio',
+ 'March' => 'marzo',
+ 'May' => 'mayo',
+ 'Menu:' => 'Menú:',
+ 'Name' => 'Nombre',
+ 'Next' => 'Siguiente',
+ 'November' => 'noviembre',
+ 'October' => 'octubre',
+ 'Overview' => 'Introducción',
+ 'Overview:' => 'Introducción:',
+ 'Prev' => 'Anterior',
+ 'Section' => 'Sección',
+ 'Section One' => 'Sección Uno',
+ 'See %{node_file_href}' => 'Véase %{node_file_href}',
+ 'See %{node_file_href} @cite{%{book}}' => 'Véase %{node_file_href} @cite{%{book}}',
+ 'See %{node_file_href} section `%{section}\' in @cite{%{book}}' => 'Véase la sección %{node_file_href} `%{section}\' en @cite{%{book}}',
+ 'See %{reference_name}' => 'Véase %{reference_name}',
+ 'See @cite{%{book}}' => 'Véase @cite{%{book}}',
+ 'See section %{reference_name}' => 'Véase la sección %{reference_name}',
+ 'See section `%{section}\' in @cite{%{book}}' => 'Véase la sección `%{section}\' en @cite{%{book}}',
+ 'September' => 'septiembre',
+ 'Short Table of Contents' => 'Resumen del Contenido',
+ 'Subsection One-Four' => 'Subsección Uno-Cuatro',
+ 'Subsection One-One' => 'Subsección Uno-Uno',
+ 'Subsection One-Three' => 'Subsección Uno-Tres',
+ 'Subsection One-Two' => 'Subsección Uno-Dos',
+ 'Subsubsection One-Two-Four' => 'Subsubsección Uno-Dos-Cuatro',
+ 'Subsubsection One-Two-One' => 'Subsubsección Uno-Dos-Uno',
+ 'Subsubsection One-Two-Three' => 'Subsubsección Uno-Dos-Tress',
+ 'Subsubsection One-Two-Two' => 'Subsubsección Uno-Dos-Dos',
+ 'T2H_today' => '',
+ 'Table of Contents' => 'Tabla de contenidos',
+ 'This document was generated by @emph{%{user}} on @emph{%{date}} using @uref{%{program_homepage}, @emph{%{program}}}.' => 'Este documento fue generado pr @emph{%{user}} en @emph{%{date}} usando @uref{%{program_homepage}, @emph{%{program}}}.',
+ 'This document was generated by @emph{%{user}} using @uref{%{program_homepage}, @emph{%{program}}}.' => 'Este documento fue generado por @emph{%{user}} usando @uref{%{program_homepage}, @emph{%{program}}}.',
+ 'This document was generated on @i{%{date}} using @uref{%{program_homepage}, @i{%{program}}}.' => 'Este documento fue generado en @i{%{date}} usando @uref{%{program_homepage}, @i{%{program}}}.',
+ 'This document was generated using @uref{%{program_homepage}, @emph{%{program}}}.' => 'Este documento fue generado usando @uref{%{program_homepage}, @emph{%{program}}}.',
+ 'Top' => 'Inicio',
+ 'Untitled Document' => 'Documento sintítulo',
+ 'about (help)' => 'Acerca de (ayuda)',
+ 'beginning of this chapter or previous chapter' => 'Inicio del capítulo o capítulo anterior',
+ 'by @emph{%{user}}' => 'por @emph{%{user}}',
+ 'by @emph{%{user}} on @emph{%{date}}' => 'por @emph{%{user}} el @emph{%{date}}',
+ 'cover (top) of document' => 'Cubierta (inicio) del documento',
+ 'current' => 'actual',
+ 'current section' => 'Sección actual',
+ 'first section in reading order' => 'Primera sección en orden de lectura',
+ 'following node' => 'Nodo siguiente',
+ 'index' => 'Índice',
+ 'last section in reading order' => 'Última sección en orden de lectura',
+ 'next chapter' => 'Capítulo siguiente',
+ 'next node' => 'Nodo siguiente',
+ 'next section in reading order' => 'Sección siguiente en order de lectura',
+ 'next section on same level' => 'Sección siguiente en el mismo nivel',
+ 'node following in node reading order' => 'siguiente nodo en orden de lectura',
+ 'node up' => 'nodo arriba',
+ 'on @emph{%{date}}' => 'el @emph{%{date}}',
+ 'previous node' => 'nodo anterior',
+ 'previous section in reading order' => 'Sección anterior en orden de lectura',
+ 'previous section on same level' => 'Sección anterior en el mismo nivel',
+ 'section `%{section}\' in @cite{%{book}}' => 'sección `%{section}\' en @cite{%{book}}',
+ 'see %{node_file_href}' => 'Véase %{node_file_href}',
+ 'see %{node_file_href} @cite{%{book}}' => 'Véase %{node_file_href} @cite{%{book}}',
+ 'see %{node_file_href} section `%{section}\' in @cite{%{book}}' => 'Véase %{node_file_href} sección `%{section}\' en @cite{%{book}}',
+ 'see %{reference_name}' => 'Véase %{reference_name}',
+ 'see @cite{%{book}}' => 'Véase @cite{%{book}}',
+ 'see section %{reference_name}' => 'véase sección %{reference_name}',
+ 'see section `%{section}\' in @cite{%{book}}' => 'véase sección `%{section}\' en @cite{%{book}}',
+ 'short table of contents' => 'resumen del contenido',
+ 'table of contents' => 'Tabla de contenidos',
+ 'unknown' => 'desconocido',
+ 'up node' => 'nodo superior',
+ 'up section' => 'Sección superior'
+ };
+
+$T2H_OBSOLETE_STRINGS->{'es'} = {
+ 'See' => 'Véase',
+ 'section' => 'sección',
+ 'see' => 'véase'
+ };
+
+return 1;
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual-menu.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual-menu.texinfo
new file mode 100644
index 0000000..0afc9ff
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual-menu.texinfo
@@ -0,0 +1,4 @@
+@menu
+* Licenses::
+* Index::
+@end menu
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual-nodes.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual-nodes.texinfo
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual-nodes.texinfo
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual.conf b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual.conf
new file mode 100755
index 0000000..b4f9ae4
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual.conf
@@ -0,0 +1,43 @@
+# Este fichero controla la configuración del manual. Este fichero
+# está dividido en diferentes secciones de configuración (e.g., `main'
+# para organizar la configuración principal y `templates' para
+# organizar la relación de asiganación plantillas-sección). Cada
+# sección de configuración está organizada en pares de valores
+# `variable = valor' usados para describir las preferencias de
+# configuración.
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+[main]
+
+# Especifica el trasfondo de documentación usado por el manual. Este
+# es el formato utilizado para redactar los ficheros fuentes del
+# manual de documentación.
+manual_format = "texinfo"
+
+# Especifica el estilo de títulos utilizados por las secciones del
+# manual. Los valores posibles para esta opción son `cap-each-word'
+# para escribir la primera letra de cada palabra en el título con
+# mayúscula y el resto en minúscula, `cap-first-word' para escribir
+# solo la primera letra del título en mayúscula y el resto en
+# minúscula; y `directory' para transformar el título en un camino de
+# directorio.
+manual_section_style = "cap-each-word"
+
+# Especifica el order con que se muestran las secciones en el manual.
+# Los valores posibles para esta opción son `created' para ubicar las
+# nuevas secciones creadas en orden de creación, `ordered' para
+# ordenar las secciones alfabéticamente sin importar el orden con el
+# cual fueron creadas; y `reversed' lo contrario the `ordered'.
+manual_section_order = "created"
+
+[templates]
+
+# Especifica la relación entre los ficheros de plantilla y los
+# ficheros de definición de secciones en el manual. La definición de
+# las plantillas se escriben en forma de camino relativo en el
+# izquierdo y la definición de secciones en forma de expresión regular
+# en el lado derecho.
+Chapters/section-functions.texinfo = "^.+-functions-[[:alnum:]]+\.texinfo$"
+Chapters/section.texinfo = "^.+\.texinfo$"
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual.sed b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual.sed
new file mode 100644
index 0000000..baa4b5b
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual.sed
@@ -0,0 +1,40 @@
+#!/bin/sed
+#
+# repository.sed -- This file provide Spanish transformations for
+# texi2html outupt, based on The CentOS Project CSS definitions.
+#
+# Copyright (C) 2009-2012 The CentOS Project
+#
+# 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., 59 Temple Place, Suite 330, Boston, MA 02111-1307
+# USA.
+#
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+# Quotations.
+s!<blockquote><p><strong>Nota</strong>!<blockquote class="blue icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/note.png" alt="Info" /><h2>Nota</h2><p>!g
+
+s!<blockquote><p><strong>Advertencia</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/warning.png" alt="Advertencia" /><h2>Advertencia</h2><p>!g
+
+s!<blockquote><p><strong>Importante</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/star.png" alt="Importante" /><h2>Importante</h2><p>!g
+
+s!<blockquote><p><strong>Idea</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/tip.png" alt="Idea" /><h2>Idea</h2><p>!g
+
+s!<blockquote><p><strong>Precaución</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/caution.png" alt="Precaución" /><h2>Precaución</h2><p>!g
+
+s!<blockquote><p><strong>Convensión</strong>!<blockquote class="orange icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/ruler.png" alt="Convensión" /><h2>Convensión</h2><p>!g
+
+s!<blockquote><p><strong>Redirección</strong>!<blockquote class="blue icon"><img src="/home/centos/Projects/artwork/trunk/Identity/Images/Webenv/redirect.png" alt="Redirección" /><h2>Redirección</h2><p>!g
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual.texinfo b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual.texinfo
new file mode 100644
index 0000000..c21f607
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/es_ES/manual.texinfo
@@ -0,0 +1,75 @@
+\input texinfo @c -*-texinfo-*-
+@c -- Header --------------------------------------------------
+
+@setfilename =MANUAL_NAME=.info
+@settitle =MANUAL_TITLE=
+@documentlanguage es
+@afourpaper
+@finalout
+
+@c -- Variables -----------------------------------------------
+
+@set TCENTOS The Community Enterprise Operating System
+@set TCPROJ @url{http://www.centos.org/, The CentOS Project}
+@set TCWIKI @url{http://wiki.centos.org/, The CentOS Wiki}
+@set TCMLISTS @url{http://lists.centos.org/, The CentOS Mailing Lists}
+@set TCBUGS @url{http://bugs.centos.org/, The CentOS Bugs}
+@set TCMIRRORS @url{http://mirrors.centos.org/, The CentOS Mirrors}
+@set TCPLANET @url{http://planet.centos.org/, The CentOS Planet}
+@set TCFORUMS @url{http://forums.centos.org/, The CentOS Forums}
+@set TCINFOML @email{centos-info@@centos.org, The CentOS Information Mailing List}
+@set TCDEVSML @email{centos-devel@@centos.org, The CentOS Developers Mailing List}
+@set TCDOCSML @email{centos-docs@@centos.org, The CentOS Documentation Mailing List}
+@set TCARTWML @email{centos-artwork@@centos.org, The CentOS Artwork Mailing List}
+@set TCL10NML @email{centos-l10n@@centos.org, The CentOS Localization Mailing List}
+@set TCAR @url{https://projects.centos.org/svn/artwork/, The CentOS Artwork Repository}
+@set TCAS @url{https://projects.centos.org/trac/artwork/, The CentOS Artwork SIG}
+
+@c -- Summary description and copyright -----------------------
+
+@copying
+=MANUAL_ABSTRACT=
+
+Copyright @copyright{} =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=
+
+Se otorga permiso para copiar, distribuir y/o modificar este documento
+bajo los términos de la Licencia de Documentación Libre de GNU,
+Versión 1.1 o cualquier otra versión posterior publicada por la Free
+Software Foundation; con las Secciones Invariantes, con Textos de
+Cubierta Delantera, y con los Textos de Cubierta Trasera. Una copia de
+la licencia está incluida en la sección titulada @ref{GNU Free
+Documentation License}.
+@end copying
+
+@c -- Titlepage, contents, copyright ---------------------------
+
+@titlepage
+@title =MANUAL_TITLE=
+@subtitle =MANUAL_SUBTITLE=
+@author =COPYRIGHT_HOLDER=
+@page
+@vskip 0pt plus 1filll
+@insertcopying
+@end titlepage
+@contents
+
+@c -- `Top' node and master menu -------------------------------
+
+@ifnottex
+@node Top
+@top =MANUAL_TITLE=
+@insertcopying
+@end ifnottex
+
+@include =MANUAL_NAME=-menu.texinfo
+
+@c -- The body of the document --------------------------------
+
+@include =MANUAL_NAME=-nodes.texinfo
+
+@c -- The end of the document ---------------------------------
+
+@include Licenses.texinfo
+@include =MANUAL_NAME=-index.texinfo
+
+@bye
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/manual-init.pl b/Artworks/Documentation/Repository/Texinfo/Default/manual-init.pl
new file mode 100755
index 0000000..8f68ea7
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/manual-init.pl
@@ -0,0 +1,389 @@
+#!/usr/bin/perl
+#
+# repository.init -- This file initializes Texi2HTML program to
+# produce the repository documentation manual using the CentOS Web
+# Environment XHTML and CSS standard definition.
+#
+# Copyright (C) 2009, 2010, 2011 The CentOS Project
+#
+# 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., 59 Temple Place, Suite 330, Boston, MA 02111-1307
+# USA.
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+# -iso
+# if set, ISO8859 characters are used for special symbols (like
+# copyright, etc)
+$USE_ISO = 1;
+
+# -I
+# add a directory to the list of directories where @include files are
+# searched for (besides the directory of the file). additional '-I'
+# args are appended to this list. (APA: Don't implicitely search .,
+# to conform with the docs!) my @INCLUDE_DIRS = (".");
+#@INCLUDE_DIRS = ("/home/al/Projects/CentOS/artwork");
+
+# Extension used on output files.
+$EXTENSION = "xhtml";
+
+# Horizontal rules.
+$DEFAULT_RULE = '<div class="page-line white"><hr style="display:none;" /></div>';
+$SMALL_RULE = $DEFAULT_RULE;
+$MIDDLE_RULE = $DEFAULT_RULE;
+$BIG_RULE = $DEFAULT_RULE;
+
+# -split section|chapter|node|none
+# if $SPLIT is set to 'section' (resp. 'chapter') one html file per
+# section (resp. chapter) is generated. If $SPLIT is set to 'node' one
+# html file per node or sectionning element is generated. In all these
+# cases separate pages for Top, Table of content (Toc), Overview and
+# About are generated. Otherwise a monolithic html file that contains
+# the whole document is created.
+$SPLIT = 'section';
+
+# -sec-nav|-nosec-nav
+# if this is set then navigation panels are printed at the beginning
+# of each section. If the document is split at nodes then navigation
+# panels are printed at the end if there were more than $WORDS_IN_PAGE
+# words on page.
+#
+# If the document is split at sections this is ignored.
+#
+# This is most useful if you do not want to have section navigation
+# with -split chapter. There will be chapter navigation panel at the
+# beginning and at the end of chapters anyway.
+$SECTION_NAVIGATION = 1;
+
+# Layout control
+$print_page_head = \&T2H_XHTML_print_page_head;
+$print_page_foot = \&T2H_XHTML_print_page_foot;
+$print_frame = \&T2H_XHTML_print_frame;
+$button_icon_img = \&T2H_XHTML_button_icon_img;
+$print_navigation = \&T2H_XHTML_print_navigation;
+
+#FIXME update once it is more stabilized in texi2html.init
+sub T2H_XHTML_print_page_head
+{
+ my $fh = shift;
+ my $longtitle = "$Texi2HTML::THISDOC{'title_unformatted'}";
+ $longtitle .= ": $Texi2HTML::UNFORMATTED{'This'}" if exists $Texi2HTML::UNFORMATTED{'This'};
+ print $fh <<EOT;
+<?xml version="1.0"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="$LANG" lang="$LANG">
+<head>
+
+ <title>$longtitle</title>
+
+ <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+ <meta name="description" content="$longtitle" />
+ <meta name="keywords" content="$longtitle" />
+ <meta name="resource-type" content="document" />
+ <meta name="distribution" content="global" />
+ <meta name="generator" content="$Texi2HTML::THISDOC{program}" />
+ <meta name="copyright" content="2009-2012 The CentOS Project" />
+
+ <link href="Css/stylesheet.css" rel="stylesheet" type="text/css" media="screen projection" />
+
+</head>
+
+<body>
+
+<a name="top" />
+
+<div id="wrap">
+
+ <div id="page-body">
+
+ <div id="content">
+
+<!-- Created on $Texi2HTML::THISDOC{today} by $Texi2HTML::THISDOC{program} -->
+EOT
+}
+
+sub T2H_XHTML_print_page_foot
+{
+ my $fh = shift;
+ my @date=localtime(time);
+ my $year=$date[5] += 1900;
+ my $program_string = program_string();
+ print $fh <<EOT;
+
+ <p class="credits">$program_string</p>
+
+ </div>
+
+ </div>
+
+
+</div>
+
+</body>
+
+</html>
+EOT
+}
+
+# / in <img>
+sub T2H_XHTML_button_icon_img
+{
+ my $button = shift;
+ my $icon = shift;
+ my $name = shift;
+ return '' if (!defined($icon));
+ if (defined($name) && $name)
+ {
+ $name = ": $name";
+ }
+ else
+ {
+ $name = '';
+ }
+ $button = "" if (!defined ($button));
+ return qq{<img src="$icon" border="0" alt="$button$name" align="middle" />};
+}
+
+$simple_map{'*'} = '<br />';
+
+# formatting functions
+
+$def_line = \&t2h_xhtml_def_line;
+$index_summary = \&t2h_xhtml_index_summary;
+$image = \&t2h_xhtml_image;
+
+# need / in <img>
+sub t2h_xhtml_image($$$)
+{
+ my $file = shift;
+ my $base = shift;
+ my $preformatted = shift;
+ return "[ $base ]" if ($preformatted);
+ return "<img src=\"$file\" alt=\"$base\" />";
+}
+
+# process definition commands line @deffn for example
+# <u> replaced by <span>
+sub t2h_xhtml_def_line($$$$$)
+{
+ my $category = shift;
+ my $name = shift;
+ my $type = shift;
+ my $arguments = shift;
+ my $index_label = shift;
+ $index_label = '' if (!defined($index_label));
+ $name = '' if (!defined($name) or ($name =~ /^\s*$/));
+ $type = '' if (!defined($type) or $type =~ /^\s*$/);
+ if (!defined($arguments) or $arguments =~ /^\s*$/)
+ {
+ $arguments = '';
+ }
+ else
+ {
+ $arguments = '<i>' . $arguments . '</i>';
+ }
+ my $type_name = '';
+ $type_name = " $type" if ($type ne '');
+ $type_name .= ' <b>' . $name . '</b>' if ($name ne '');
+ $type_name .= $arguments . "\n";
+ if (! $DEF_TABLE)
+ {
+ return '<dt>'. '<span style="text-decoration: underline">' . $category . ':</span>' . $type_name . $index_label . "</dt>\n";
+ }
+ else
+ {
+
+ return "<tr>\n<td align=\"left\">" . $type_name .
+ "</td>\n<td align=\"right\">" . $category . $index_label . "</td>\n" . "</tr>\n";
+ }
+}
+
+# There is a br which needs /
+sub t2h_xhtml_index_summary($$)
+{
+ my $alpha = shift;
+ my $nonalpha = shift;
+ my $join = '';
+ my $nonalpha_text = '';
+ my $alpha_text = '';
+ $join = " \n<br />\n" if (@$nonalpha and @$alpha);
+ if (@$nonalpha)
+ {
+ $nonalpha_text = join("\n \n", @$nonalpha) . "\n";
+ }
+ if (@$alpha)
+ {
+ $alpha_text = join("\n \n", @$alpha) . "\n \n";
+ }
+ #I18n
+ return "<table><tr><th valign=\"top\">" . &$I('Jump to') . ": </th><td>" .
+ $nonalpha_text . $join . $alpha_text . '</td></tr></table>';
+}
+
+# Layout of navigation panel
+sub T2H_XHTML_print_navigation
+{
+ my $fh = shift;
+ my $buttons = shift;
+ my $vertical = shift;
+ print $fh '<table class="navibar">' . "\n";
+
+ print $fh "<tr>" unless $vertical;
+ for my $button (@$buttons)
+ {
+ print $fh qq{<tr>\n} if $vertical;
+ print $fh qq{<td>};
+
+ if (ref($button) eq 'CODE')
+ {
+ &$button($fh, $vertical);
+ }
+ elsif (ref($button) eq 'SCALAR')
+ {
+ print $fh "$$button" if defined($$button);
+ }
+ elsif (ref($button) eq 'ARRAY')
+ {
+ my $text = $button->[1];
+ my $button_href = $button->[0];
+ if (defined($button_href) and !ref($button_href)
+ and defined($text) and (ref($text) eq 'SCALAR') and defined($$text))
+ { # use given text
+ if ($Texi2HTML::HREF{$button_href})
+ {
+ print $fh "" .
+ &$anchor('',
+ $Texi2HTML::HREF{$button_href},
+ $$text
+ )
+ ;
+ }
+ else
+ {
+ print $fh $$text;
+ }
+ }
+ }
+ elsif ($button eq ' ')
+ { # handle space button
+ print $fh
+ $ICONS && $ACTIVE_ICONS{' '} ?
+ &$button_icon_img($button, $ACTIVE_ICONS{' '}) :
+ $NAVIGATION_TEXT{' '};
+ #next;
+ }
+ elsif ($Texi2HTML::HREF{$button})
+ { # button is active
+ my $btitle = $BUTTONS_GOTO{$button} ?
+ 'title="' . ucfirst($BUTTONS_GOTO{$button}) . '"' : '';
+ if ($ICONS && $ACTIVE_ICONS{$button})
+ { # use icon
+ print $fh '' .
+ &$anchor('',
+ $Texi2HTML::HREF{$button},
+ &$button_icon_img($button,
+ $ACTIVE_ICONS{$button},
+ #$Texi2HTML::NAME{$button}),
+ $Texi2HTML::NO_TEXI{$button}),
+ $btitle
+ );
+ }
+ else
+ { # use text
+ print $fh
+ '[' .
+ &$anchor('',
+ $Texi2HTML::HREF{$button},
+ $NAVIGATION_TEXT{$button},
+ $btitle
+ ) .
+ ']';
+ }
+ }
+ else
+ { # button is passive
+ print $fh
+ $ICONS && $PASSIVE_ICONS{$button} ?
+ &$button_icon_img($button,
+ $PASSIVE_ICONS{$button},
+ #$Texi2HTML::NAME{$button}) :
+ $Texi2HTML::NO_TEXI{$button}) :
+
+ "[" . $NAVIGATION_TEXT{$button} . "]";
+ }
+ print $fh "</td>\n";
+ print $fh "</tr>\n" if $vertical;
+ }
+ print $fh "</tr>" unless $vertical;
+ print $fh "</table>\n";
+}
+
+# Use icons for navigation.
+$ICONS = 0;
+
+# insert here name of icon images for buttons
+# Icons are used, if $ICONS and resp. value are set
+%ACTIVE_ICONS =
+ (
+ 'Top', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-top.png',
+ 'Contents', 'file:///usr/share/icons/Bluecurve/24x24/stock/help-contents.png',
+ 'Overview', '',
+ 'Index', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-find.png',
+ 'This', '',
+ 'Back', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png',
+ 'FastBack', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-first.png',
+ 'Prev', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png',
+ 'Up', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-up.png',
+ 'Next', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
+ 'NodeUp', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-up.png',
+ 'NodeNext', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
+ 'NodePrev', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png',
+ 'Following', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
+ 'Forward', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
+ 'FastForward', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-last.png',
+ 'About' , 'file:///usr/share/icons/Bluecurve/24x24/stock/gtk-about.png',
+ 'First', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-first.png',
+ 'Last', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-last.png',
+ ' ', ''
+ );
+
+# Insert here name of icon images for these, if button is inactive
+%PASSIVE_ICONS =
+ (
+ 'Top', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-top.png',
+ 'Contents', 'file:///usr/share/icons/Bluecurve/24x24/stock/help-contents.png',
+ 'Overview', '',
+ 'Index', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-find.png',
+ 'This', '',
+ 'Back', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png',
+ 'FastBack', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-first.png',
+ 'Prev', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png',
+ 'Up', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-up.png',
+ 'Next', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
+ 'NodeUp', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-up.png',
+ 'NodeNext', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
+ 'NodePrev', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png',
+ 'Following', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
+ 'Forward', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png',
+ 'FastForward', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-last.png',
+ 'About' , 'file:///usr/share/icons/Bluecurve/24x24/stock/gtk-about.png',
+ 'First', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-first.png',
+ 'Last', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-last.png',
+ ' ', ''
+ );
+
+return 1;
diff --git a/Artworks/Documentation/Repository/Texinfo/Default/manual.sed b/Artworks/Documentation/Repository/Texinfo/Default/manual.sed
new file mode 100644
index 0000000..2b89341
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Default/manual.sed
@@ -0,0 +1,29 @@
+#!/bin/sed
+#
+# repository.sed -- This file provides common transformations for
+# texi2html output, based on The CentOS Project CSS definitions.
+#
+# Copyright (C) 2009, 2010, 2011 The CentOS Project
+#
+# 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., 59 Temple Place, Suite 330, Boston, MA 02111-1307
+# USA.
+#
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+# Links
+#s!<a href="(https|http|ftps|ftp)://!<a class="www" href="\1://!g
+#s!<a href="mailto:!<a class="mailto" href="mailto:!g
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity-menu.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity-menu.texinfo
new file mode 100644
index 0000000..898140e
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity-menu.texinfo
@@ -0,0 +1,19 @@
+@menu
+* Identity Brushes::
+* Identity Brushes Corporate::
+* Identity Fonts::
+* Identity Images::
+* Identity Images Brands::
+* Identity Images Brands Logos::
+* Identity Images Brands Symbols::
+* Identity Images Brands Types::
+* Identity Images Icons::
+* Identity Images Themes::
+* Identity Models::
+* Identity Models Brands::
+* Identity Models Brands Logos::
+* Identity Models Themes::
+* Identity Palettes::
+* Identity Patterns::
+* Identity Webenv::
+@end menu
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity-nodes.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity-nodes.texinfo
new file mode 100644
index 0000000..2902a4f
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity-nodes.texinfo
@@ -0,0 +1,17 @@
+@include Identity/brushes.texinfo
+@include Identity/brushes-corporate.texinfo
+@include Identity/fonts.texinfo
+@include Identity/images.texinfo
+@include Identity/images-brands.texinfo
+@include Identity/images-brands-logos.texinfo
+@include Identity/images-brands-symbols.texinfo
+@include Identity/images-brands-types.texinfo
+@include Identity/images-icons.texinfo
+@include Identity/images-themes.texinfo
+@include Identity/models.texinfo
+@include Identity/models-brands.texinfo
+@include Identity/models-brands-logos.texinfo
+@include Identity/models-themes.texinfo
+@include Identity/palettes.texinfo
+@include Identity/patterns.texinfo
+@include Identity/webenv.texinfo
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity.texinfo
new file mode 100644
index 0000000..9383c82
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity.texinfo
@@ -0,0 +1,28 @@
+@node Identity
+@chapter The @file{Scripts} Directory
+@cindex Identity
+
+@c -- Chapter Introduction
+The @file{Identity} directory describes @value{TCPCI}, what it
+is and the components it is made of.
+
+@value{TCPCI} 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. @value{TCPCI} provides visibility, recognizability,
+reputation, structure and identification to The CentOS Project by
+means of Corporate Design, Corporate Communication, and Corporate
+Behaviour.
+
+From Corporate Design, Corporate Communication and Corporate
+Behaviour, it is the Corporate Design the one organized inside
+@file{Identity} directory through the following components:
+
+@c -- Chapter Menu
+@include Identity-menu.texinfo
+
+@c -- Chapter Nodes
+@include Identity-nodes.texinfo
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/brushes-corporate.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/brushes-corporate.texinfo
new file mode 100644
index 0000000..6a8d0c9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/brushes-corporate.texinfo
@@ -0,0 +1,10 @@
+@node Identity Brushes Corporate
+@section @file{Identity/Brushes/Corporate}
+@cindex Identity brushes corporate
+
+...
+
+@c -- <[centos-art(SeeAlso)
+@itemize
+@end itemize
+@c -- ]>
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/brushes.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/brushes.texinfo
new file mode 100644
index 0000000..216cf0d
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/brushes.texinfo
@@ -0,0 +1,79 @@
+@node Identity Brushes
+@section @file{Identity/Brushes}
+@cindex Identity brushes
+
+The @file{Identity/Brushes} directory exists to organize GIMP
+brushes used inside @value{TCPCVI}.
+
+A brush is a pixmap or set of pixmaps used for painting through an
+image manipulation program like GIMP. Inside the repository, brushes
+are initially created in @file{.xcf} format and later exported to any
+of the brush formats recognized by GIMP (e.g., @file{.gbr} or
+@file{.gih}) using the same name of its source file.
+
+The @file{Identity/Brushes} directory is under version control.
+
+The @file{Identity/Brushes} directory contains no file, but the
+following organizational directories:
+
+@c -- <[centos-art(SeeAlso)
+@itemize
+@end itemize
+@c -- ]>
+
+Content rendition inside @file{Identity/Brushes} directory is
+not supported.
+
+In order for brushes to be loaded by GIMP, they should be stored in
+the @file{~/.gimp-2.2/brushes} directory. This location is out of
+@value{TCAR} and doesn't provide version control by itself. To be able
+of using version controlled brushes inside GIMP, we store brush
+related files inside @file{Identity/Brushes} directory and
+create links to them from @file{~/.gimp-2.2/brushes} directory.
+
+@float Example,identity-brushes-1
+@verbatim
+Identity/Brushes
+|-- Corporate
+| |-- symbol.xcf
+| `-- symbol.gbr (file) <-- ~/.gimp-2.2/brushes/corporate-symbol.gbr (link)
+|-- TreeFlower
+| |-- flower.gbr (file) <-- ~/.gimp-2.2/brushes/treeflower-flower.gbr (link)
+| |-- flower.xcf
+| |-- branch.gbr (file) <-- ~/.gimp-2.2/brushes/treeflower-branch.gbr (link)
+| |-- branch.xcf
+| |-- trunk.gbr (file) <-- ~/.gimp-2.2/brushes/treeflower-trunk.gbr (link)
+| `-- trunk.xcf
+`-- Others
+ `-- ...
+@end verbatim
+@caption{Relation between brushes inside the workstation.}
+@end float
+
+The entire link preparation and maintenance of brushes inside the
+working copy is automated by @code{prepare} functionality of
+@command{centos-art.sh} script.
+
+Inside the working copy, brushes might be created individually in
+different locations, but they all need to be linked from one unique
+location (i.e., @file{~/.gimp-2.2/brushes}). This configuration may
+provoke brushes to overlap one another if a consistent name convention
+is not implemented correctly. In that sake, the brushes file names
+are build using their directory and file names as reference in order
+to build unique names that can be used as identifiers.
+
+Brushes produced with GIMP has a description field associated that is
+shown in the Brushes panel of GIMP. This description is set when the
+brush is created as @file{.xcf} file and can be updated when it is
+exported either to @file{.gbr} or @file{.gih} format. It wouldn't be
+too useful to have two or more brushes using the same description so,
+we also make description of brush files unique, too. In that sake, use
+the file name as description but without including the file extension
+(e.g., if we have the @file{centos-flame-3.gbr} brush, its description
+would be @code{centos-flame-3}).
+
+More information about GIMP brushes can be found in
+@url{file:///usr/share/gimp/2.0/help/en/index.html,The Gimp Manual},
+specifically in the section related to
+@url{file:///usr/share/gimp/2.0/help/en/gimp-concepts-brushes.html,
+Brushes}.
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/fonts.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/fonts.texinfo
new file mode 100644
index 0000000..7eaeee9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/fonts.texinfo
@@ -0,0 +1,54 @@
+@node Identity Fonts
+@section @file{Identity/Fonts}
+@cindex Identity fonts
+
+The @file{Identity/Fonts} directory exists to organize
+typographies used inside @value{TCPCVI} that aren't packaged inside
+@value{TCD}.
+
+The @file{Identity/Fonts} directory is under version control.
+
+Content rendition inside @file{Identity/Fonts} directory is not
+supported.
+
+@c -- describe, in one paragraph, what a font is.
+
+In order for fonts to be available inside programs like GIMP and
+Inkscape, font files should be stored either in
+@file{/usr/share/fonts} or @file{~/.fonts} directory. These locations
+are out of @value{TCAR} and doesn't provide version control by
+themselves. In order for version controlled typographies to be
+available inside programs like GIMP and Inkscape, we store them under
+@file{Identity/Fonts} directory and create links to them from
+@file{~/.fonts} directory.
+
+@float Example, identity-fonts-1
+@verbatim
+Identity/Fonts
+`-- denmark.ttf (file) <-- ~/.fonts/denmark.ttf (link)
+@end verbatim
+@caption{Relation between fonts inside the workstation.}
+@end float
+
+The creation and maintenance of links related to fonts inside the
+working copy are automated by @code{prepare} functionality of
+@command{centos-art.sh} script.
+
+Inside @value{TCPCVI}, the @samp{DejaVu LGC} typography is used as
+default typography in all visual manifestations. The @samp{DejaVu LGC}
+typography comes with @value{TCD} so there is no need to store it in
+@file{Identity/Fonts} for you to use.
+
+Inside @value{TCPCVI}, the @samp{Denmark} typography is used as base
+to build The CentOS Logo (i.e., the main graphic design that
+connects/identifies all visual manifestations related to The CentOS
+Project). The @samp{Denmark} typography doesn't come with @value{TCD}
+so it is store in @file{Identity/Fonts} for you to use.
+
+The license information of @samp{Denmark} typography isn't very clear,
+at least not as clear as the one in @samp{DejaVu LGC} typography is.
+Using a typography with a doubtful license might put in risk the
+content produced from it. To prevent such issues, it would be better
+to move on from @samp{Denmark} typography to another typography (free,
+preferably) that retain the same visual style of @samp{Denmark}, but
+with a clearer copyright and license notice.
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-brands-logos.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-brands-logos.texinfo
new file mode 100644
index 0000000..aafccb9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-brands-logos.texinfo
@@ -0,0 +1,42 @@
+@node Identity Images Brands Logos
+@section @file{Identity/Images/Brands/Logos}
+@cindex Identity images brands logos
+
+The @file{Identity/Images/Brands/Logos} exists to organize
+images related to The CentOS Logos, in different formats (e.g., PNG,
+JPG, PDF, TIF, XBM, XPM) and dimensions.
+
+The CentOS Logo is a construction made of The CentOS Symbol and The
+CentOS Type. The CentOS Symbol and The CentOS Logo are the main visual
+manifestations of the organization known as @value{TCPROJ}. As The
+CentOS Symbol, The CentOS Logo is used to ``brand'' images produced by
+@value{TCPROJ} and provide a visual connection between images so they
+can be monolithically recognized as part of @value{TCPROJ}. The CentOS
+Logo must be exactly the same every time it is printed out and a route
+to reproduce it in such a way must be available so as to avoid
+reproduction mistakes when images are branded with it.
+
+The @file{Identity/Images/Brands/Logos} directory and the files
+inside it aren't under version control.
+
+The @file{Identity/Images/Brands/Logos} directory contains files
+used by the @file{redhat-logos} package, specifically the files inside
+the @file{/usr/share/pixmaps/redhat} directory.
+
+The @file{Identity/Images/Brands/Logos} directory organizes
+files under directories numerically named (e.g., @file{48}, @file{64},
+@file{128}, etc.). Inside these directories, image files are stored
+in specific heights and named as
+@file{centos-<something>.<extension>}, where @code{<somthing>}
+describes the file content and @code{<extension>} sets the file
+extension. In all cases, the directory name can be used as reference
+to determine the image height of files stored inside. For example,
+the directory @file{48} stores image files of 48 pixels height in
+different formats.
+
+Content rendition inside @file{Identity/Images/Brands/Logos}
+directory takes place through the following command:
+
+@verbatim
+centos-art render Identity/Images/Brands/Logos --dont-commit-changes
+@end verbatim
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-brands-symbols.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-brands-symbols.texinfo
new file mode 100644
index 0000000..6e78e1f
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-brands-symbols.texinfo
@@ -0,0 +1,40 @@
+@node Identity Images Brands Symbols
+@section @file{Identity/Images/Brands/Symbols}
+@cindex Identity images brands symbols
+
+The @file{Identity/Images/Brands/Symbols} exists to organize
+images related to The CentOS Symbol, in different formats (e.g., PNG,
+JPG, PDF, TIF, XBM, XPM) and dimensions.
+
+The CentOS Symbol is the graphical part of The CentOS Logo. As The
+CentOS Logo, The CentOS Symbol is used to ``brand'' images produced by
+@value{TCPROJ} and provide a visual connection between images so they
+can be monolithically recognized as part of @value{TCPROJ}. The CentOS
+Symbol must be exactly the same every time it is printed out and a
+route to reproduce it in such a way must be available so as to avoid
+reproduction mistakes when images are branded with it.
+
+The @file{Identity/Images/Brands/Symbols} directory and the files
+inside it aren't under version control.
+
+The @file{Identity/Images/Brands/Symbols} directory contains
+files used by the @file{redhat-logos} package, specifically the files
+inside the @file{/usr/share/pixmaps/redhat} directory.
+
+The @file{Identity/Images/Brands/Symbols} directory organizes
+files under directories numerically named (e.g., @file{48}, @file{64},
+@file{128}, etc.). Inside these directories, image files are stored
+in specific heights and named as
+@file{centos-<something>.<extension>}, where @code{<somthing>}
+describes the file content and @code{<extension>} sets the file
+extension. In all cases, the directory name can be used as reference
+to determine the image height of files stored inside. For example,
+the directory @file{48} stores image files of 48 pixels height in
+different formats.
+
+Content rendition inside @file{Identity/Images/Brands/Symbols}
+directory takes place through the following command:
+
+@verbatim
+centos-art render Identity/Images/Brands/Symbols --dont-commit-changes
+@end verbatim
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-brands-types.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-brands-types.texinfo
new file mode 100644
index 0000000..e196966
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-brands-types.texinfo
@@ -0,0 +1,44 @@
+@node Identity Images Brands Types
+@section @file{Identity/Images/Brands/Types}
+@cindex Identity images brands types
+
+The @file{Identity/Images/Brands/Types} exists to organize
+images related to The CentOS Symbol, in different formats (e.g., PNG,
+JPG, PDF, TIF, XBM, XPM) and dimensions.
+
+The CentOS Type is the typographical part of The CentOS Logo.
+Comparing with both The CentOS Logo and The CentOS Symbol, The CentOS
+Type by its own, provides poor visual connection between images that
+intend to be recognized as a monolithic part of @value{TCPROJ} and
+shouldn't be used alone. Instead, The CentOS Logo or The CentOS Symbol
+are preferred. The CentOS Symbol must be exactly the same every time
+it is printed out and a route to reproduce it in such a way must be
+available so as to avoid reproduction mistakes when images are branded
+with it.
+
+The @file{Identity/Images/Brands/Types} directory and the files
+inside it aren't under version control. Files in this location are
+mainly used to build The CentOS Logo from combining both The CentOS
+Type and The CentOS Symbol in specific situations that might be needed
+doing so.
+
+The @file{Identity/Images/Brands/Types} directory contains files
+used by no package, as far as we've found out.
+
+The @file{Identity/Images/Brands/Types} directory organizes
+files under directories numerically named (e.g., @file{48}, @file{64},
+@file{128}, etc.). Inside these directories, image files are stored
+in specific heights and named as
+@file{centos-<something>.<extension>}, where @code{<somthing>}
+describes the file content and @code{<extension>} sets the file
+extension. In all cases, the directory name can be used as reference
+to determine the image height of files stored inside. For example,
+the directory @file{48} stores image files of 48 pixels height in
+different formats.
+
+Content rendition inside @file{Identity/Images/Brands/Types}
+directory takes place through the following command:
+
+@verbatim
+centos-art render Identity/Images/Brands/Types --dont-commit-changes
+@end verbatim
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-brands.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-brands.texinfo
new file mode 100644
index 0000000..f871dcc
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-brands.texinfo
@@ -0,0 +1,24 @@
+@node Identity Images Brands
+@section @file{Identity/Images/Brands}
+@cindex Identity images brands
+
+The @file{Identity/Images/Brands} directory exists to organize
+brand information related to @value{TCPROJ}.
+
+The @file{Identity/Images/Brands} directory isn't under version
+control.
+
+The @file{Identity/Images/Brands} contains no file, but the
+following organizational directories:
+
+@c -- <[centos-art(SeeAlso)
+@itemize
+@end itemize
+@c -- ]>
+
+Content rendition inside @file{Identity/Images/Brands} directory
+takes place through the following command:
+
+@verbatim
+centos-art render Identity/Images/Brands --dont-commit-changes
+@end verbatim
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-icons.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-icons.texinfo
new file mode 100644
index 0000000..c8b46b6
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-icons.texinfo
@@ -0,0 +1,10 @@
+@node Identity Images Icons
+@section @file{Identity/Images/Icons}
+@cindex Identity images icons
+
+...
+
+@c -- <[centos-art(SeeAlso)
+@itemize
+@end itemize
+@c -- ]>
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-themes.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-themes.texinfo
new file mode 100644
index 0000000..cf3a6d9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images-themes.texinfo
@@ -0,0 +1,7 @@
+@node Identity Images Themes
+@section @file{Identity/Images/Themes}
+@cindex Identity images themes
+...
+
+@menu
+@end menu
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images.texinfo
new file mode 100644
index 0000000..964b2f9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/images.texinfo
@@ -0,0 +1,26 @@
+@node Identity Images
+@section @file{Identity/Images}
+@cindex Identity images
+
+The @file{Identity/Images} directory exists to store all image
+files (e.g., PNG, JPG, PPM, etc.) related to @value{TCPCVI}.
+
+The @file{Identity/Images} directory is under version control.
+
+The @file{Identity/Images} directory contains no file, but the
+following organizational directories:
+
+@c -- <[centos-art(SeeAlso)
+@itemize
+@item @ref{Identity Images Brands}
+@item @ref{Identity Images Icons}
+@item @ref{Identity Images Themes}
+@end itemize
+@c -- ]>
+
+Content rendition inside @file{Identity/Images} directory takes
+place through the following command:
+
+@verbatim
+centos-art render Identity/Images --dont-commit-changes
+@end verbatim
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/models-brands-logos.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/models-brands-logos.texinfo
new file mode 100644
index 0000000..d7d98d9
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/models-brands-logos.texinfo
@@ -0,0 +1,8 @@
+@node Identity Models Brands Logos
+@section @file{Identity/Models/Brands/Logos}
+@cindex Identity models brands logos
+
+...
+
+@menu
+@end menu
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/models-brands.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/models-brands.texinfo
new file mode 100644
index 0000000..39946bc
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/models-brands.texinfo
@@ -0,0 +1,9 @@
+@node Identity Models Brands
+@section @file{Identity/Models/Brands}
+@cindex Identity models brands
+
+...
+
+@menu
+* Identity Models Brands Logos::
+@end menu
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/models-themes.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/models-themes.texinfo
new file mode 100644
index 0000000..70a31c4
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/models-themes.texinfo
@@ -0,0 +1,10 @@
+@node Identity Models Themes
+@section @file{Identity/Models/Themes}
+@cindex Identity models themes
+
+...
+
+@c -- <[centos-art(SeeAlso)
+@itemize
+@end itemize
+@c -- ]>
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/models.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/models.texinfo
new file mode 100644
index 0000000..1b2f26e
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/models.texinfo
@@ -0,0 +1,10 @@
+@node Identity Models
+@section @file{Identity/Models}
+@cindex Identity models
+
+...
+
+@c -- <[centos-art(SeeAlso)
+@itemize
+@end itemize
+@c -- ]>
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/palettes.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/palettes.texinfo
new file mode 100644
index 0000000..7ae9984
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/palettes.texinfo
@@ -0,0 +1,7 @@
+@node Identity Palettes
+@section @file{Identity/Palettes}
+@cindex Identity palettes
+...
+
+@menu
+@end menu
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/patterns.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/patterns.texinfo
new file mode 100644
index 0000000..1157522
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/patterns.texinfo
@@ -0,0 +1,8 @@
+@node Identity Patterns
+@section @file{Identity/Patterns}
+@cindex Identity patterns
+
+...
+
+@menu
+@end menu
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/webenv.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/webenv.texinfo
new file mode 100644
index 0000000..1571757
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Identity/webenv.texinfo
@@ -0,0 +1,7 @@
+@node Identity Webenv
+@section @file{Identity/Webenv}
+@cindex Identity webenv
+...
+
+@menu
+@end menu
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts-menu.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts-menu.texinfo
new file mode 100644
index 0000000..d5de2d3
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts-menu.texinfo
@@ -0,0 +1,4 @@
+@menu
+* Scripts Functions::
+* Scripts Functions Prepare::
+@end menu
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts-nodes.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts-nodes.texinfo
new file mode 100644
index 0000000..89f5123
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts-nodes.texinfo
@@ -0,0 +1,2 @@
+@include Scripts/functions.texinfo
+@include Scripts/functions-prepare.texinfo
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts.texinfo
new file mode 100644
index 0000000..1d17b2e
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts.texinfo
@@ -0,0 +1,75 @@
+@node Scripts
+@chapter The @file{Scripts} Directory
+@cindex Scripts
+
+@c -- Chapter Introduction
+
+The @file{Scripts} directory exists to organize automation
+scripts related to @value{TCPCVI}. Such automation scripts are
+implemented through @command{centos-art.sh} script, a bash scripts
+designed to automate most frequent tasks performed inside the working
+copy of @value{TCAR} (e.g., image rendition, content documentation,
+content translation, etc.).
+
+The @file{Scripts} directory and all files inside it are under
+version control.
+
+The @file{Scripts} directory contains just one file, the
+@file{centos-art.sh} file. This file is the invocation script the
+@command{centos-art} command calls to. In addition to
+@file{centos-art.sh} file, the following directories are available:
+
+Content rendition inside @file{Scripts} is not supported.
+
+Once the @command{centos-art.sh} script is executed, the following
+variables are available all along the script execution:
+
+@defvar CLI_PROGRAM
+The @var{CLI_PROGRAM} variable is read-only and contains the name of
+the script, which is @samp{centos-art}, without extension.
+@end defvar
+
+@defvar CLI_PROGRAM_ID
+The @var{CLI_PROGRAM_ID} variable is read-only and contains the
+process identification assigned to @command{centos-art.sh} script,
+once executed.
+@end defvar
+
+@defvar CLI_VERSION
+The @var{CLI_VERSION} variable is read-only and contains the version
+number of @command{centos-art.sh} script.
+@end defvar
+
+@defvar CLI_BASEDIR
+The @var{CLI_BASEDIR} variable is read-only and contains the absolute
+path of directory where @command{centos-art.sh} script is stored in.
+@end defvar
+
+@defvar CLI_TEMPDIR
+The @var{CLI_TEMPDIR} variable is read-only and contains the absolute
+path of directory where temporal files created by
+@command{centos-art.sh} script are stored in.
+@end defvar
+
+@defvar TEXTDOMAIN
+The @var{TEXDOMAIN} variable is read-only and contains the name of the
+program we are providing localization for (i.e., @samp{centos-art.sh}).
+@end defvar
+
+@defvar TEXTDOMAINDIR
+The @var{TEXTDOMAINDIR} variable is read-only and contains the
+absolute path of directory holding localization messages for
+@command{centos-art.sh}. In order for this variable to take effect,
+its value must be set using the
+@file{$@{BASEDIR@}/$@{LANG@}/LC_MESSAGES/$@{TEXDOMAIN@}} construction;
+where @var{BASEDIR} is an absolute path inside your workstation,
+@var{LANG} a language code based on the standards @samp{ISO-639} and
+@samp{ISO-3166} (e.g., @samp{es_ES} for Spanish from Spain,
+@samp{fr_FR} for French from France, etc.).
+@end defvar
+
+@c -- Chapter Menu
+@include Scripts-menu.texinfo
+
+@c -- Chapter Nodes
+@include Scripts-nodes.texinfo
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts/functions-prepare.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts/functions-prepare.texinfo
new file mode 100644
index 0000000..43d0fc3
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts/functions-prepare.texinfo
@@ -0,0 +1,86 @@
+@node Scripts Functions Prepare
+@section @file{Scripts/Functions/Prepare}
+@cindex Scripts functions prepare
+
+The @file{Scripts/Functions/Prepare} directory exists to
+organize the @code{prepare} functionality of @command{centos-art.sh}
+script. The @code{prepare} functionality is written in Bash and its
+main goal is to standardize the final configuration stuff your
+workstation needs, once the working copy of @value{TCAR} has been
+downloaded inside it.
+
+The @file{Scripts/Functions/Prepare} directory and all files
+inside it are under version control.
+
+Content rendition inside @file{Scripts/Functions/Prepare} is not
+supported.
+
+Inside @file{Scripts/Functions/Prepare} directory, file names
+and function names share the same name convenction with the exception
+that file names end with a @samp{.sh} suffix while function names
+doesn't. Both, file names and function names, begin with
+@samp{prepare_} prefix followed by a description of what the function
+does.
+
+Inside @file{Scripts/Functions/Prepare} directory, you can find
+the following functions:
+
+@defun prepare
+The @code{prepare} (initialization) function creates the base
+execution environment required to standardize final configuration
+stuff needed by your workstation, once the working copy of
+@value{TCAR} has been downloaded in it.
+@end defun
+
+@defun prepare_getOptions
+The @code{prepare_getOptions} function parses command options provided
+to @command{centos-art.sh} script when the first argument in the
+command-line is the @samp{prepare} word. This function decides what
+action to perform based on options provided. To parse options, this
+function makes use of @command{getopt} program.
+@end defun
+
+@defun prepare_updateLinks
+The @code{prepare_updateLinks} function updates the symbolic
+link relation that connects your workstation with the files inside the
+working copy of @value{TCAR}. This function makes brushes, palettes,
+patterns and fonts inside the working copy available to programs like
+GIMP and Inkscape installed in your workstation.
+@end defun
+
+@defun prepare_updateImages
+The @code{prepare_updateImages} function initializes image files
+inside the working copy. This function makes a list of all design
+models inside the working copy and renders them one by one to produces
+the related output images.
+@end defun
+
+@defun prepare_updateManuals
+The @code{prepare_updateManuals} function initializes
+documentation files inside the working copy. This function makes a
+list of all documentation manuals source files inside the working copy
+and produces related output for them.
+@end defun
+
+@defun prepare_updatePackages
+The @code{prepare_updatePackages} function verifies the required
+packages your workstation needs to have installed in order for
+@command{centos-art.sh} script to run correctly. If one or
+more packages are uninstalled or out of date, the
+@command{centos-art.sh} script asks you to confirm their
+installation or actualization through the @command{sudo yum} command.
+@end defun
+
+@defun prepare_getEnvars
+The @code{prepare_getEnvars} function outputs a brief description of
+relevant environment variables the @command{centos-art.sh} script
+makes use of.
+@end defun
+
+@defun prepare_getLinkName DIRECTORY, FILE
+The @code{prepare_getLinkName} function takes a @var{DIRECTORY} path
+as first argument and a @var{FILE} path as second argument to output a
+file name with the path information that remains from substracting the
+@var{DIRECTORY} path from the @var{FILE} path provided as argument.
+@end defun
+
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts/functions.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts/functions.texinfo
new file mode 100644
index 0000000..9c4c148
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/Scripts/functions.texinfo
@@ -0,0 +1,68 @@
+@node Scripts Functions
+@section @file{Scripts/Functions}
+@cindex Scripts functions
+
+The @file{Scripts/Functions} directory exists to organize common and
+specific functionalities related to the @command{centos-art.sh}
+script. Common functionalities are loaded once the
+@command{centos-art.sh} script is executed and made available for
+specific functionalities to reuse.
+
+The @file{Scripts/Functions} directory and all files inside it
+are under version control.
+
+Content rendition inside `Scripts/Functions' directory is not
+supported.
+
+Inside @file{Scripts/Functions} directory, specific
+functionalities are organized in the following directories:
+
+@c -- <[centos-art(SeeAlso)
+@itemize
+@end itemize
+@c -- ]>
+
+Inside @file{Scripts/Functions} directory, common
+functionalities are stored in files prefixed with the @samp{cli}
+string as described below:
+
+@defun cli "$@@"
+The @code{cli} functionality initializes the command-line interface
+(cli) of @command{centos-art.sh} script. This function evaluates the
+first argument provided to @command{centos-art.sh} script and call the
+specific functionality that responds to it. The @code{cli} function
+is directly called from @file{centos-art.sh} itself once global
+variables are defined, working copy verification performed, common
+functionalities exported into the execution environment, and signals
+trapped. The @code{cli} function receives all positional parameters
+passed to @command{centos-art.sh} as argument.
+
+The @code{cli} function creates the a new environment inside that one
+created by @command{centos-art.sh} script execution. Variables defined
+herein will be avaialble to all specific functionalities and common
+functionalities used inside specific functionalities.
+
+@defvar FUNCNAM
+The @var{FUNCNAM} variable stores the function name passed as first
+argument to @command{centos-art.sh} script using the file convenction
+specified by @code{cli_getRepoName} function.
+@end defvar
+
+@defvar FUNCDIR
+The @var{FUNCDIR} variable stores the absolute path of directory
+holding @command{centos-art.sh} script functions, both common and
+specific.
+@end defvar
+
+@defvar FUNCDIRNAM
+...
+@end defvar
+
+@defvar FUNCSCRIPT
+...
+@end defvar
+
+@defvar ARGUMENTS
+...
+@end defvar
+@end defun
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs-index.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs-index.texinfo
new file mode 100755
index 0000000..b197b13
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs-index.texinfo
@@ -0,0 +1,8 @@
+@node Index
+@unnumbered Index
+@syncodeindex fn cp
+@syncodeindex vr cp
+@syncodeindex ky cp
+@syncodeindex pg cp
+@syncodeindex tp cp
+@printindex cp
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs-menu.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs-menu.texinfo
new file mode 100644
index 0000000..3f09b90
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs-menu.texinfo
@@ -0,0 +1,6 @@
+@menu
+* Identity::
+* Scripts::
+* Licenses::
+* Index::
+@end menu
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs-nodes.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs-nodes.texinfo
new file mode 100644
index 0000000..57ce834
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs-nodes.texinfo
@@ -0,0 +1,2 @@
+@include Identity.texinfo
+@include Scripts.texinfo
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs.conf b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs.conf
new file mode 100755
index 0000000..789f831
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs.conf
@@ -0,0 +1,36 @@
+# This file controls the manual configuration. This file is divided
+# in configuration sections (e.g., `main' and `templates') which, in
+# turn, are organized in the form `variable = value'.
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+[main]
+
+# Specify documentation backend used by documentation manual. This is
+# the format used to write documentation manual source files.
+manual_format = "texinfo"
+
+# Specify title style used by sections inside the manual. Possible
+# values to this option are `cap-each-word' to capitalize each word in
+# the section title, `cap-first-word' to capitalize the first word in
+# the section title only and `directory' to transform each word in the
+# section title into a directory path. From all these options,
+# `cap-each-word' is the one used as default.
+manual_section_style = "directory"
+
+# Specify the order used by sections inside the manual. By default new
+# sections added to the manual are put on the end to follow the
+# section `created' order. Other possible values to this option are
+# `ordered' and `reversed' to sort the list of sections alphabetically
+# from A-Z and Z-A, respectively.
+manual_section_order = "ordered"
+
+[templates]
+
+# Specify relation between template files and section definition files
+# inside the manual. Template definition is set on the left side using
+# relative path. The section main definition file is described on the
+# right using a regular expression. The first match wins.
+Chapters/section-functions.texinfo = "^.+-functions-[[:alnum:]]+\.texinfo$"
+Chapters/section.texinfo = "^.+\.texinfo$"
diff --git a/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs.texinfo b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs.texinfo
new file mode 100644
index 0000000..db713aa
--- /dev/null
+++ b/Artworks/Documentation/Repository/Texinfo/Tcar-fs/en_US/tcar-fs.texinfo
@@ -0,0 +1,83 @@
+\input texinfo @c -*-texinfo-*-
+@c -- Header --------------------------------------------------
+
+@setfilename tcar-fs.info
+@settitle The CentOS Artwork Repository File System
+@documentlanguage en
+@afourpaper
+@finalout
+
+@c -- Variables -----------------------------------------------
+
+@set TCENTOS The Community Enterprise Operating System
+@set TCPROJ @url{http://www.centos.org/, The CentOS Project}
+@set TCWIKI @url{http://wiki.centos.org/, The CentOS Wiki}
+@set TCMLISTS @url{http://lists.centos.org/, The CentOS Mailing Lists}
+@set TCBUGS @url{http://bugs.centos.org/, The CentOS Bugs}
+@set TCMIRRORS @url{http://mirrors.centos.org/, The CentOS Mirrors}
+@set TCPLANET @url{http://planet.centos.org/, The CentOS Planet}
+@set TCFORUMS @url{http://forums.centos.org/, The CentOS Forums}
+@set TCINFOML @email{centos-info@@centos.org, The CentOS Information Mailing List}
+@set TCDEVSML @email{centos-devel@@centos.org, The CentOS Developers Mailing List}
+@set TCDOCSML @email{centos-docs@@centos.org, The CentOS Documentation Mailing List}
+@set TCARTWML @email{centos-artwork@@centos.org, The CentOS Artwork Mailing List}
+@set TCL10NML @email{centos-l10n@@centos.org, The CentOS Localization Mailing List}
+@set TCAR @url{https://projects.centos.org/svn/artwork/, The CentOS Artwork Repository}
+@set TCAS @url{https://projects.centos.org/trac/artwork/, The CentOS Artwork SIG}
+
+@set TCPCVI The CentOS Project Corporate Visual Identity
+@set TCPCI The CentOS Project Corporate Identity
+@set TCPCVIS The CentOS Project Corporate Visual Identity Structure
+@set TCPCMVIS The CentOS Project Monolithic Corporate Visual Identity Structure
+
+@set TCD The CentOS Distribution
+
+@c -- Summary description and copyright -----------------------
+
+@copying
+This manual describes the directories inside @value{TCAR}. You can use
+this manual as reference to know where to store or look for
+information inside your working copy of @value{TCAR}.
+
+Copyright @copyright{} 2009, 2010, 2011 The CentOS Project
+
+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 @ref{GNU Free
+Documentation License}.
+@end copying
+
+@c -- Titlepage, contents, copyright ---------------------------
+
+@titlepage
+@title The CentOS Artwork Repository
+@subtitle File System
+@author Alain Reguera Delgado
+@page
+@vskip 0pt plus 1filll
+@insertcopying
+@end titlepage
+@contents
+
+@c -- `Top' node and master menu -------------------------------
+
+@ifnottex
+@node Top
+@top The CentOS Artwork Repository File System
+@insertcopying
+@end ifnottex
+
+@include tcar-fs-menu.texinfo
+
+@c -- The body of the document --------------------------------
+
+@include tcar-fs-nodes.texinfo
+
+@c -- The end of the document ---------------------------------
+
+@include Licenses.texinfo
+@include tcar-fs-index.texinfo
+
+@bye
diff --git a/Artworks/Documentation/Repository/directory-structure.svgz b/Artworks/Documentation/Repository/directory-structure.svgz
new file mode 100644
index 0000000..3a1adc6
Binary files /dev/null and b/Artworks/Documentation/Repository/directory-structure.svgz differ
diff --git a/Artworks/Documentation/Repository/infrastructure.svgz b/Artworks/Documentation/Repository/infrastructure.svgz
new file mode 100644
index 0000000..308a021
Binary files /dev/null and b/Artworks/Documentation/Repository/infrastructure.svgz differ
diff --git a/Artworks/Documentation/Showroom/Clothes/cap-back.svgz b/Artworks/Documentation/Showroom/Clothes/cap-back.svgz
new file mode 100644
index 0000000..72e4995
Binary files /dev/null and b/Artworks/Documentation/Showroom/Clothes/cap-back.svgz differ
diff --git a/Artworks/Documentation/Showroom/Clothes/cap-front.svgz b/Artworks/Documentation/Showroom/Clothes/cap-front.svgz
new file mode 100644
index 0000000..a3f8291
Binary files /dev/null and b/Artworks/Documentation/Showroom/Clothes/cap-front.svgz differ
diff --git a/Artworks/Documentation/Showroom/Clothes/cap-left.svgz b/Artworks/Documentation/Showroom/Clothes/cap-left.svgz
new file mode 100644
index 0000000..d2ef431
Binary files /dev/null and b/Artworks/Documentation/Showroom/Clothes/cap-left.svgz differ
diff --git a/Artworks/Documentation/Showroom/Clothes/cap-right.svgz b/Artworks/Documentation/Showroom/Clothes/cap-right.svgz
new file mode 100644
index 0000000..bbd5996
Binary files /dev/null and b/Artworks/Documentation/Showroom/Clothes/cap-right.svgz differ
diff --git a/Artworks/Documentation/Showroom/Clothes/shirt-back.svgz b/Artworks/Documentation/Showroom/Clothes/shirt-back.svgz
new file mode 100644
index 0000000..2f4d897
Binary files /dev/null and b/Artworks/Documentation/Showroom/Clothes/shirt-back.svgz differ
diff --git a/Artworks/Documentation/Showroom/Clothes/shirt-front.svgz b/Artworks/Documentation/Showroom/Clothes/shirt-front.svgz
new file mode 100644
index 0000000..a1403ab
Binary files /dev/null and b/Artworks/Documentation/Showroom/Clothes/shirt-front.svgz differ
diff --git a/Artworks/Documentation/Showroom/Clothes/summary.svgz b/Artworks/Documentation/Showroom/Clothes/summary.svgz
new file mode 100644
index 0000000..26f462f
Binary files /dev/null and b/Artworks/Documentation/Showroom/Clothes/summary.svgz differ
diff --git a/Artworks/Documentation/Showroom/Clothes/tshirt-back.svgz b/Artworks/Documentation/Showroom/Clothes/tshirt-back.svgz
new file mode 100644
index 0000000..cd0d8c5
Binary files /dev/null and b/Artworks/Documentation/Showroom/Clothes/tshirt-back.svgz differ
diff --git a/Artworks/Documentation/Showroom/Clothes/tshirt-front.svgz b/Artworks/Documentation/Showroom/Clothes/tshirt-front.svgz
new file mode 100644
index 0000000..343ed4f
Binary files /dev/null and b/Artworks/Documentation/Showroom/Clothes/tshirt-front.svgz differ
diff --git a/Artworks/Documentation/Webenv/customization-with-ads.svgz b/Artworks/Documentation/Webenv/customization-with-ads.svgz
new file mode 100644
index 0000000..7f0ae99
Binary files /dev/null and b/Artworks/Documentation/Webenv/customization-with-ads.svgz differ
diff --git a/Artworks/Documentation/Webenv/customization.svgz b/Artworks/Documentation/Webenv/customization.svgz
new file mode 100644
index 0000000..482a531
Binary files /dev/null and b/Artworks/Documentation/Webenv/customization.svgz differ
diff --git a/Artworks/Documentation/Webenv/homepage.svgz b/Artworks/Documentation/Webenv/homepage.svgz
new file mode 100644
index 0000000..41b449c
Binary files /dev/null and b/Artworks/Documentation/Webenv/homepage.svgz differ
diff --git a/Artworks/Documentation/Webenv/navigation.svgz b/Artworks/Documentation/Webenv/navigation.svgz
new file mode 100644
index 0000000..69419c5
Binary files /dev/null and b/Artworks/Documentation/Webenv/navigation.svgz differ
diff --git a/Artworks/Documentation/Webenv/webenv-html-defs.svgz b/Artworks/Documentation/Webenv/webenv-html-defs.svgz
new file mode 100644
index 0000000..e1483b4
Binary files /dev/null and b/Artworks/Documentation/Webenv/webenv-html-defs.svgz differ
diff --git a/Artworks/Documentation/Webenv/wiki-moin.svgz b/Artworks/Documentation/Webenv/wiki-moin.svgz
new file mode 100644
index 0000000..3a09750
Binary files /dev/null and b/Artworks/Documentation/Webenv/wiki-moin.svgz differ