diff --git a/Manuals/Texinfo/Directories/branches.texinfo b/Manuals/Texinfo/Directories/branches.texinfo
deleted file mode 100755
index e8639d1..0000000
--- a/Manuals/Texinfo/Directories/branches.texinfo
+++ /dev/null
@@ -1,23 +0,0 @@
-@subheading Goals
-
-This directory implements the Subversion's branches concept in a
-trunk, branches, tags repository structure.
-
-@subheading Description
-
-The @file{branches/} directory structure provides the intermediate
-space for creating several instances of @file{trunk/} directory
-structure for parallel development and later merging changes back to
-@file{trunk/} in the same parallel basis.
-
-@subheading Usage
-
-The @file{branches/} directory structure is unused, so far.
-
-@subheading See also
-
-@itemize
-@item @ref{Directories tags}.
-@item @ref{Directories trunk}.
-@item The Subversion book (@url{http://svnbook.red-bean.com/}).
-@end itemize
diff --git a/Manuals/Texinfo/Directories/chapter-intro.texinfo b/Manuals/Texinfo/Directories/chapter-intro.texinfo
deleted file mode 100644
index 52b15fa..0000000
--- a/Manuals/Texinfo/Directories/chapter-intro.texinfo
+++ /dev/null
@@ -1,8 +0,0 @@
-The CentOS Artwork Repository uses directories to organize files and
-describe conceptual idea about corporate identity. Such conceptual
-ideas are explained in each directory related documentation entry.
-
-In this chapter you'll learn what each directory inside The CentOS
-Artwork Repository is for and so, how you can make use of them. For
-that purpose, the following list of directories is available for you
-to explore:
diff --git a/Manuals/Texinfo/Directories/chapter-menu.texinfo b/Manuals/Texinfo/Directories/chapter-menu.texinfo
deleted file mode 100644
index aad68c4..0000000
--- a/Manuals/Texinfo/Directories/chapter-menu.texinfo
+++ /dev/null
@@ -1,49 +0,0 @@
-@menu
-* Directories branches::
-* Directories tags::
-* Directories trunk::
-* Directories trunk Identity::
-* Directories trunk Identity Brushes::
-* Directories trunk Identity Fonts::
-* Directories trunk Identity Images::
-* Directories trunk Identity Images Themes::
-* Directories trunk Identity Images Themes Motifs::
-* Directories trunk Identity Images Themes Motifs Flame::
-* Directories trunk Identity Images Themes Motifs Modern::
-* Directories trunk Identity Images Themes Motifs Pipes::
-* Directories trunk Identity Images Themes Motifs TreeFlower::
-* Directories trunk Identity Models::
-* Directories trunk Identity Models Brands::
-* Directories trunk Identity Models Themes::
-* Directories trunk Identity Models Themes Default::
-* Directories trunk Identity Models Themes Default Concept::
-* Directories trunk Identity Models Themes Default Distro::
-* Directories trunk Identity Models Themes Default Distro 5::
-* Directories trunk Identity Models Themes Default Distro 5.5 Notes Release::
-* Directories trunk Identity Models Themes Default Distro 5 Anaconda::
-* Directories trunk Identity Models Themes Default Distro 5 Firstboot::
-* Directories trunk Identity Models Themes Default Distro 5 Gdm::
-* Directories trunk Identity Models Themes Default Distro 5 Grub::
-* Directories trunk Identity Models Themes Default Distro 5 Gsplash::
-* Directories trunk Identity Models Themes Default Distro 5 Kdm::
-* Directories trunk Identity Models Themes Default Distro 5 Ksplash::
-* Directories trunk Identity Models Themes Default Distro 5 Rhgb::
-* Directories trunk Identity Models Themes Default Distro 5 Syslinux::
-* Directories trunk Identity Models Themes Default Posters::
-* Directories trunk Identity Palettes::
-* Directories trunk Identity Patterns::
-* Directories trunk Identity Webenv::
-* Directories trunk Locales::
-* Directories trunk Manuals::
-* Directories trunk Manuals Directories::
-* Directories trunk Manuals Introduction::
-* Directories trunk Manuals Licenses::
-* Directories trunk Scripts::
-* Directories trunk Scripts Functions::
-* Directories trunk Scripts Functions Help::
-* Directories trunk Scripts Functions Help Backends::
-* Directories trunk Scripts Functions Locale::
-* Directories trunk Scripts Functions Prepare::
-* Directories trunk Scripts Functions Render::
-* Directories trunk Scripts Functions Tuneup::
-@end menu
diff --git a/Manuals/Texinfo/Directories/chapter-nodes.texinfo b/Manuals/Texinfo/Directories/chapter-nodes.texinfo
deleted file mode 100644
index a996a12..0000000
--- a/Manuals/Texinfo/Directories/chapter-nodes.texinfo
+++ /dev/null
@@ -1,235 +0,0 @@
-@node Directories branches
-@section The @file{branches} Directory
-@cindex Directories branches
-@include Directories/branches.texinfo
-
-@node Directories tags
-@section The @file{tags} Directory
-@cindex Directories tags
-@include Directories/tags.texinfo
-
-@node Directories trunk
-@section The @file{trunk} Directory
-@cindex Directories trunk
-@include Directories/trunk.texinfo
-
-@node Directories trunk Identity
-@section The @file{trunk/Identity} Directory
-@cindex Directories trunk Identity
-@include Directories/trunk/Identity.texinfo
-
-@node Directories trunk Identity Brushes
-@section The @file{trunk/Identity/Brushes} Directory
-@cindex Directories trunk Identity Brushes
-@include Directories/trunk/Identity/Brushes.texinfo
-
-@node Directories trunk Identity Fonts
-@section The @file{trunk/Identity/Fonts} Directory
-@cindex Directories trunk Identity Fonts
-@include Directories/trunk/Identity/Fonts.texinfo
-
-@node Directories trunk Identity Images
-@section The @file{trunk/Identity/Images} Directory
-@cindex Directories trunk Identity Images
-@include Directories/trunk/Identity/Images.texinfo
-
-@node Directories trunk Identity Images Themes
-@section The @file{trunk/Identity/Images/Themes} Directory
-@cindex Directories trunk Identity Images Themes
-@include Directories/trunk/Identity/Images/Themes.texinfo
-
-@node Directories trunk Identity Images Themes Motifs
-@section The @file{trunk/Identity/Images/Themes/Motifs} Directory
-@cindex Directories trunk Identity Images Themes Motifs
-@include Directories/trunk/Identity/Images/Themes/Motifs.texinfo
-
-@node Directories trunk Identity Images Themes Motifs Flame
-@section The @file{trunk/Identity/Images/Themes/Motifs/Flame} Directory
-@cindex Directories trunk Identity Images Themes Motifs Flame
-@include Directories/trunk/Identity/Images/Themes/Motifs/Flame.texinfo
-
-@node Directories trunk Identity Images Themes Motifs Modern
-@section The @file{trunk/Identity/Images/Themes/Motifs/Modern} Directory
-@cindex Directories trunk Identity Images Themes Motifs Modern
-@include Directories/trunk/Identity/Images/Themes/Motifs/Modern.texinfo
-
-@node Directories trunk Identity Images Themes Motifs Pipes
-@section The @file{trunk/Identity/Images/Themes/Motifs/Pipes} Directory
-@cindex Directories trunk Identity Images Themes Motifs Pipes
-@include Directories/trunk/Identity/Images/Themes/Motifs/Pipes.texinfo
-
-@node Directories trunk Identity Images Themes Motifs TreeFlower
-@section The @file{trunk/Identity/Images/Themes/Motifs/TreeFlower} Directory
-@cindex Directories trunk Identity Images Themes Motifs TreeFlower
-@include Directories/trunk/Identity/Images/Themes/Motifs/TreeFlower.texinfo
-
-@node Directories trunk Identity Models
-@section The @file{trunk/Identity/Models} Directory
-@cindex Directories trunk Identity Models
-@include Directories/trunk/Identity/Models.texinfo
-
-@node Directories trunk Identity Models Brands
-@section The @file{trunk/Identity/Models/Brands} Directory
-@cindex Directories trunk Identity Models Brands
-@include Directories/trunk/Identity/Models/Brands.texinfo
-
-@node Directories trunk Identity Models Themes
-@section The @file{trunk/Identity/Models/Themes} Directory
-@cindex Directories trunk Identity Models Themes
-@include Directories/trunk/Identity/Models/Themes.texinfo
-
-@node Directories trunk Identity Models Themes Default
-@section The @file{trunk/Identity/Models/Themes/Default} Directory
-@cindex Directories trunk Identity Models Themes Default
-@include Directories/trunk/Identity/Models/Themes/Default.texinfo
-
-@node Directories trunk Identity Models Themes Default Concept
-@section The @file{trunk/Identity/Models/Themes/Default/Concept} Directory
-@cindex Directories trunk Identity Models Themes Default Concept
-@include Directories/trunk/Identity/Models/Themes/Default/Concept.texinfo
-
-@node Directories trunk Identity Models Themes Default Distro
-@section The @file{trunk/Identity/Models/Themes/Default/Distro} Directory
-@cindex Directories trunk Identity Models Themes Default Distro
-@include Directories/trunk/Identity/Models/Themes/Default/Distro.texinfo
-
-@node Directories trunk Identity Models Themes Default Distro 5
-@section The @file{trunk/Identity/Models/Themes/Default/Distro/5} Directory
-@cindex Directories trunk Identity Models Themes Default Distro 5
-@include Directories/trunk/Identity/Models/Themes/Default/Distro/5.texinfo
-
-@node Directories trunk Identity Models Themes Default Distro 5.5 Notes Release
-@section The @file{trunk/Identity/Models/Themes/Default/Distro/5.5/Notes/Release} Directory
-@cindex Directories trunk Identity Models Themes Default Distro 5.5 Notes Release
-@include Directories/trunk/Identity/Models/Themes/Default/Distro/5.5/Notes/Release.texinfo
-
-@node Directories trunk Identity Models Themes Default Distro 5 Anaconda
-@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Anaconda} Directory
-@cindex Directories trunk Identity Models Themes Default Distro 5 Anaconda
-@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Anaconda.texinfo
-
-@node Directories trunk Identity Models Themes Default Distro 5 Firstboot
-@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Firstboot} Directory
-@cindex Directories trunk Identity Models Themes Default Distro 5 Firstboot
-@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Firstboot.texinfo
-
-@node Directories trunk Identity Models Themes Default Distro 5 Gdm
-@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Gdm} Directory
-@cindex Directories trunk Identity Models Themes Default Distro 5 Gdm
-@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gdm.texinfo
-
-@node Directories trunk Identity Models Themes Default Distro 5 Grub
-@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Grub} Directory
-@cindex Directories trunk Identity Models Themes Default Distro 5 Grub
-@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Grub.texinfo
-
-@node Directories trunk Identity Models Themes Default Distro 5 Gsplash
-@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Gsplash} Directory
-@cindex Directories trunk Identity Models Themes Default Distro 5 Gsplash
-@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gsplash.texinfo
-
-@node Directories trunk Identity Models Themes Default Distro 5 Kdm
-@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Kdm} Directory
-@cindex Directories trunk Identity Models Themes Default Distro 5 Kdm
-@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Kdm.texinfo
-
-@node Directories trunk Identity Models Themes Default Distro 5 Ksplash
-@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Ksplash} Directory
-@cindex Directories trunk Identity Models Themes Default Distro 5 Ksplash
-@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Ksplash.texinfo
-
-@node Directories trunk Identity Models Themes Default Distro 5 Rhgb
-@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Rhgb} Directory
-@cindex Directories trunk Identity Models Themes Default Distro 5 Rhgb
-@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Rhgb.texinfo
-
-@node Directories trunk Identity Models Themes Default Distro 5 Syslinux
-@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Syslinux} Directory
-@cindex Directories trunk Identity Models Themes Default Distro 5 Syslinux
-@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Syslinux.texinfo
-
-@node Directories trunk Identity Models Themes Default Posters
-@section The @file{trunk/Identity/Models/Themes/Default/Posters} Directory
-@cindex Directories trunk Identity Models Themes Default Posters
-@include Directories/trunk/Identity/Models/Themes/Default/Posters.texinfo
-
-@node Directories trunk Identity Palettes
-@section The @file{trunk/Identity/Palettes} Directory
-@cindex Directories trunk Identity Palettes
-@include Directories/trunk/Identity/Palettes.texinfo
-
-@node Directories trunk Identity Patterns
-@section The @file{trunk/Identity/Patterns} Directory
-@cindex Directories trunk Identity Patterns
-@include Directories/trunk/Identity/Patterns.texinfo
-
-@node Directories trunk Identity Webenv
-@section The @file{trunk/Identity/Webenv} Directory
-@cindex Directories trunk Identity Webenv
-@include Directories/trunk/Identity/Webenv.texinfo
-
-@node Directories trunk Locales
-@section The @file{trunk/Locales} Directory
-@cindex Directories trunk Locales
-@include Directories/trunk/Locales.texinfo
-
-@node Directories trunk Manuals
-@section The @file{trunk/Manuals} Directory
-@cindex Directories trunk Manuals
-@include Directories/trunk/Manuals.texinfo
-
-@node Directories trunk Manuals Directories
-@section The @file{trunk/Manuals/Directories} Directory
-@cindex Directories trunk Manuals Directories
-@include Directories/trunk/Manuals/Directories.texinfo
-
-@node Directories trunk Manuals Introduction
-@section The @file{trunk/Manuals/Introduction} Directory
-@cindex Directories trunk Manuals Introduction
-@include Directories/trunk/Manuals/Introduction.texinfo
-
-@node Directories trunk Manuals Licenses
-@section The @file{trunk/Manuals/Licenses} Directory
-@cindex Directories trunk Manuals Licenses
-@include Directories/trunk/Manuals/Licenses.texinfo
-
-@node Directories trunk Scripts
-@section The @file{trunk/Scripts} Directory
-@cindex Directories trunk Scripts
-@include Directories/trunk/Scripts.texinfo
-
-@node Directories trunk Scripts Functions
-@section The @file{trunk/Scripts/Functions} Directory
-@cindex Directories trunk Scripts Functions
-@include Directories/trunk/Scripts/Functions.texinfo
-
-@node Directories trunk Scripts Functions Help
-@section The @file{trunk/Scripts/Functions/Help} Directory
-@cindex Directories trunk Scripts Functions Help
-@include Directories/trunk/Scripts/Functions/Help.texinfo
-
-@node Directories trunk Scripts Functions Help Backends
-@section The @file{trunk/Scripts/Functions/Help/Backends} Directory
-@cindex Directories trunk Scripts Functions Help Backends
-@include Directories/trunk/Scripts/Functions/Help/Backends.texinfo
-
-@node Directories trunk Scripts Functions Locale
-@section The @file{trunk/Scripts/Functions/Locale} Directory
-@cindex Directories trunk Scripts Functions Locale
-@include Directories/trunk/Scripts/Functions/Locale.texinfo
-
-@node Directories trunk Scripts Functions Prepare
-@section The @file{trunk/Scripts/Functions/Prepare} Directory
-@cindex Directories trunk Scripts Functions Prepare
-@include Directories/trunk/Scripts/Functions/Prepare.texinfo
-
-@node Directories trunk Scripts Functions Render
-@section The @file{trunk/Scripts/Functions/Render} Directory
-@cindex Directories trunk Scripts Functions Render
-@include Directories/trunk/Scripts/Functions/Render.texinfo
-
-@node Directories trunk Scripts Functions Tuneup
-@section The @file{trunk/Scripts/Functions/Tuneup} Directory
-@cindex Directories trunk Scripts Functions Tuneup
-@include Directories/trunk/Scripts/Functions/Tuneup.texinfo
-
diff --git a/Manuals/Texinfo/Directories/chapter.texinfo b/Manuals/Texinfo/Directories/chapter.texinfo
deleted file mode 100644
index ce2ff93..0000000
--- a/Manuals/Texinfo/Directories/chapter.texinfo
+++ /dev/null
@@ -1,6 +0,0 @@
-@node Directories
-@chapter The Repository Directories
-@cindex Repository directories
-@include Directories/chapter-intro.texinfo
-@include Directories/chapter-menu.texinfo
-@include Directories/chapter-nodes.texinfo
diff --git a/Manuals/Texinfo/Directories/tags.texinfo b/Manuals/Texinfo/Directories/tags.texinfo
deleted file mode 100755
index 609583a..0000000
--- a/Manuals/Texinfo/Directories/tags.texinfo
+++ /dev/null
@@ -1,24 +0,0 @@
-@subheading Goals
-
-This directory implements the Subversion's tags concept in a trunk,
-branches, tags repository structure.
-
-@subheading Description
-
-The @file{tags/} directory structure provides frozen branches.
-Generally, we use frozen branches to make check-points in time for
-development lines under @file{branches/} or @file{trunk/} directory
-structure.
-
-@subheading Usage
-
-The @file{tags/} directory structure is unused, so far.
-
-@subheading See also
-
-@itemize
-@item @ref{Directories branches}.
-@item @ref{Directories trunk}.
-@item The subversion book (@url{http://svnbook.red-bean.com/}).
-@end itemize
-
diff --git a/Manuals/Texinfo/Directories/trunk.texinfo b/Manuals/Texinfo/Directories/trunk.texinfo
deleted file mode 100644
index a7ea8d1..0000000
--- a/Manuals/Texinfo/Directories/trunk.texinfo
+++ /dev/null
@@ -1,26 +0,0 @@
-@subheading Goals
-
-The @file{trunk/} directory structure implements the Subversion's
-trunk concept in a trunk, branches, tags repository structure.
-
-@subheading Description
-
-The @file{trunk/} directory structure provides the main development
-line inside the CentOS Artwork Repository.
-
-@subheading Usage
-
-@itemize
-@item @xref{Directories trunk Identity}.
-@item @xref{Directories trunk Manuals}.
-@item @xref{Directories trunk Locales}.
-@item @xref{Directories trunk Scripts}.
-@end itemize
-
-@subheading See also
-
-@itemize
-@item @ref{Directories branches}.
-@item @ref{Directories tags}.
-@item The Subversion book (@url{http://svnbook.red-bean.com/}).
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity.texinfo b/Manuals/Texinfo/Directories/trunk/Identity.texinfo
deleted file mode 100644
index eca5563..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity.texinfo
+++ /dev/null
@@ -1,279 +0,0 @@
-@subheading Goals
-
-The @file{trunk/Identity} describes what The CentOS Project Corporate
-Identity is and the components it is made of.
-
-@subheading Description
-
-The CentOS Project Corporate Identity is the ``persona'' of the
-organization known as The CentOS Project. The CentOS Project
-Corporate Identity plays a significant role in the way The CentOS
-Project, as organization, presents itself to both internal and
-external stakeholders. In general terms, The CentOS Project Corporate
-Identity expresses the values and ambitions of The CentOS Project
-organization, its business, and its characteristics.
-
-The CentOS Project Corporate Identity provides visibility,
-recognizability, reputation, structure and identification to The
-CentOS Project organization by means of @emph{Corporate Design},
-@emph{Corporate Communication}, and @emph{Corporate Behaviour}.
-
-@image{trunk/Identity/Images/Manual/Corporate/monolithic,450pt,,,jpg}
-
-@subsubheading Corporate Mission
-
-The CentOS Project exists to provide The CentOS Distribution.
-Additionally, The CentOS Project provides The CentOS Web and The
-CentOS Showroom to support and promote the existence of The CentOS
-Distribution, respectively.
-
-@subsubheading Corporate Design
-
-Corporate design is focused on the effective communication of
-corporate visual messages. Corporate visual messages are all the
-information emitted by a corporation that can be perceived by the
-people through their visual sence (i.e., the human eye). In order for
-such visual communication to happen, it is required to put the visual
-message on medium available for people to see. These kind of media
-are know as corporate visual manifestations, since the corporate
-manifests its existence through them using corporate design.
-
-The amount of visual manifestations a corporation uses to communicate
-its existence is very specific to each corporation itself. Inside The
-CentOS Project Corporate Identity, considering @emph{The CentOS
-Project Corporate Structure}, @emph{The CentOS Project Corporate
-Mission} and @emph{The CentOS Project Release Schema}, the following
-visual manifestations were defined:
-
-@table @strong
-@item The CentOS Distribution
-
-The CentOS Distribution visual manifestation exists to cover all
-actions related to artwork production and rebranding required by the
-The CentOS Distribution (--- @strong{Removed}(pxref:Directories trunk Identity Images Themes
-Models Default Distro) ---) in order to comply with its upstream
-redistribution guidelines.
-
-The CentOS Distribution is made of software packages. Inside the
-distribution there are packages that make a remarkable use of images
-and there are packages that don't use images at all. The CentOS
-Distribution visual manifestation gets focused on software packages
-that do use images in a remarkable way (e.g., @file{anaconda},
-@file{grub}, @file{syslinux}, @file{gdm}, @file{kdm}) and that way,
-through images, implements the corporate design in The CentOS
-Distribution (i.e., the operating system).
-
-@item The CentOS Web
-
-The CentOS Web visual manifestation exists to support The CentOS
-Distribution.
-
-The CentOS Web covers web applications which let The CentOS Project to
-manifest its existence on the Internet. Through these web applications
-The CentOS Project provides Corporate Communication. These web
-applications are free software and come from different providers which
-distribute their work with predefined visual styles. Frequently,
-these predefined visual styles have no visual relation among
-themselves and introduce some visual contraditions when they all are
-put together. These visual contraditions need to be removed in order
-to comply with The CentOS Project Corporate Structure guidelines.
-
-@item The CentOS Showroom
-
-The CentOS Showroom visual manifestation exists to promote The CentOS
-Distribution.
-
-The CentOS Showroom covers industrial production of objects branded by
-The CentOS Project (e.g., clothes, stationery and installation media).
-These branded objects are for distribution on social events and/or
-shops. They provide a way of promotion and a route for
-commercialization that may help to aliviate The CentOS Project
-expenses (e.g., electrical power, hosting, servers,
-full-time-developers, etc.), in a similar way as donations may do.
-
-@end table
-
-The visual manifestations above seem to cover all the media required
-by The CentOS Project, as organization, to show its existence.
-However, other visual manifestations could be added in the future, if
-needed, to cover different areas like building, offices, road
-transportation and whaterver visual manifestation The CentOS Project
-thouches to show its existence.
-
-@subsubheading Corporate Communication
-
-The CentOS Project Corporate Communication is based on @emph{Community
-Communication} and takes place through the following avenues:
-
-@itemize
-@item The CentOS Chat (@code{#centos}, @code{#centos-social},
-@code{#centos-devel} on irc.freenode.net)
-@item The CentOS Mailing Lists (@url{http://lists.centos.org/}).
-@item The CentOS Forums (@url{http://forums.centos.org/}).
-@item The CentOS Wiki (@url{http://wiki.centos.org/}).
-@item Social events, interviews, conferences, etc.
-@end itemize
-
-@subsubheading Corporate Behaviour
-
-The CentOS Project Corporate Behaviour is based on @emph{Community
-Behaviour} which take place on @emph{Corporate Communication}.
-
-@subsubheading Corporate Structure
-
-The CentOS Project Corporate Structure is based on a @emph{Monolithic
-Corporate Visual Identity Structure}. In this configuration, one
-unique name and one unique visual style is used in all visual
-manifestation of The CentOS Project.
-
-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: @emph{Hey! we are all part of The CentOS
-Project}.
-
-Other corporate structures for The CentOS Project have been considered
-as well. Such is the case of producing one different visual style for
-each major release of The CentOS Distribution. This structure isn't
-inconvenient at all, but some visual contradictions could be
-introduced if it isn't applied correctly and we need to be aware of
-it. To apply it correctly, we need to know what The CentOS Project is
-made of.
-
-The CentOS Project, as organization, is mainly made of (but not
-limited to) three visual manifestions: Distribution, Web and Showroom.
-Inside the Distribution visual manifestations, The CentOS Project
-maintains near to four different major releases of CentOS
-Distribution, parallely in time. However, inside The CentOS Web
-visual manifestations, the content is produced for no specific release
-information (e.g., there is no a complete web site for each major
-release of The CentOS Distribution individually, but one web site to
-cover them all). Likewise, the content produced in The CentOS Showroom
-is created for no release-specific at all, but for The CentOS Project
-in general.
-
-In order to produce the correct corporate structure for The CentOS
-Project we need to concider all the visual manifestations The CentOS
-Project is made of, not just one of them. If one different visual
-style is used for each major release of The CentOS Distribution, which
-one of those different visual styles would be used to cover the
-remaining visual manifestations The CentOS Project is made of (e.g.,
-The CentOS Web and The CentOS Showroom)?
-
-Probably you are thinking, that's right, but The CentOS Brand connects
-them all already, why would we need to join them up into the same
-visual style too, isn't it more work to do, and harder to maintain?
-
-Harder to maintain, more work to do, probably. Specially when you
-consider that The CentOS Project has proven stability and consistency
-through time and, that, certainly, didn't come through swinging
-magical wands or something but hardly working out to automate tasks
-and providing maintainance through time. Said that, we consider that
-The CentOS Project Corporate Structure must be consequent with such
-stability and consistency tradition. It is true that The CentOS Brand
-does connect all the visual manifestations it is present on, but that
-connection would be stronger if one unique visual style backups it.
-In fact, whatever thing you do to strength the visual connection among
-The CentOS Project visual manifestations would be very good in favor
-of The CentOS Project recognition.
-
-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 The CentOS Distribution, in
-order to refresh The CentOS Distribution visual style; the problem
-itself is in not propagating the brand new visual style created for
-the new release of The CentOS Distribution to all other visual
-manifestations The CentOS Project is made of, in a way The CentOS
-Project could be recognized no matter what 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 the CentOS Artwork Repository.
-
-@subheading Usage
-
-The @file{trunk/Identity} directory structure organizes most files
-used to build and implement The CentOS Project Corporate Identity. In
-that sake, the following work lines are available:
-
-@table @strong
-
-@item Brushes
-
-This work line provides brushes for GIMP. When you prepare the
-repository, brushes in this location are made available immediatly for
-you to use in the ``Brushes'' panel of GIMP.
-
-@xref{Directories trunk Identity Brushes}, for more
-information.
-
-@item Fonts
-
-This work line provides the typography information required by all
-different visual manifestations of The CentOS Project. When you
-prepare the repository, fonts in this location are made available
-immediatly for you to use in GIMP and Inkscape.
-
-@xref{Directories trunk Identity Fonts}, for more information.
-
-@item Images
-
-This work line provides output location for final images that don't
-need to use background images (e.g., brands, icons, illustrations,
-etc.).
-
-@xref{Directories trunk Identity Images}, for more information.
-
-@item Models
-
-This work line provides design models for final images that don't need
-to use background images (e.g., brands, icons, illustrations, etc.).
-
-@xref{Directories trunk Identity Models}, for more information.
-
-@item Palettes
-
-This work line provides palettes of colors for GIMP and Inkscape. When
-you prepare the repository, palettes of colors in this location are
-made available immediatly for you to use in the ``Palettes'' panel of
-GIMP and Inkscape.
-
-@xref{Directories trunk Identity Palettes}, for more information.
-
-@item Patterns
-
-This work line provides patterns for GIMP. When you prepare the
-repository, patterns in this location are made available immediatly
-for you to use in the ``Patterns'' panel of GIMP.
-
-@xref{Directories trunk Identity Patterns}, for more information.
-
-@item Themes
-
-This work line provides theme design models and theme artistic motifs
-for The CentOS Project. If you are interested in creating brand new
-visual styles for The CentOS Project this is the place for you.
-
-@xref{Directories trunk Identity Images Themes}, for more information.
-
-@item Webenv
-
-This work line provides the HTML/XHTML and CSS standard definitions
-used by The CentOS Web visual manifestation. If you are a web
-developer and plan to improve The CentOS Web visual manifestation,
-then the files in this location may result very useful to you.
-
-@xref{Directories trunk Identity Webenv}, for more information.
-@end table
-
-@subheading See also
-
-See @url{http://en.wikipedia.org/Corporate_identity} (and related
-links), for general information on Corporate Identity.
-
-Specially useful has been, and still is, the book @emph{Corporate
-Identity} by Wally Olins (1989). This book provides many of the
-conceptual ideas we've used as base to build The CentOS Artwork
-Repository.
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Brushes.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Brushes.texinfo
deleted file mode 100755
index 0d046e0..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Brushes.texinfo
+++ /dev/null
@@ -1,135 +0,0 @@
-@subheading Goals
-
-This section describes how brushes are organized in the repository and
-how to make them available for you to use in @acronym{GIMP,GNU Image
-Manipulation Program}.
-
-@subheading Description
-
-A brush is a pixmap or set of pixmaps used for painting through an
-image manipulation program like GIMP. Inside the repository, we've
-organized brushes in @emph{common brushes} and @emph{theme-specific
-brushes}. In both cases, 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.
-
-@verbatim
-1. Common brushes 2. Theme-specific brushes
----------------------- -----------------------------------------------------------
-trunk/Identity/Brushes trunk/Identity/Images/Themes/THEMENAME/THEMEVERSION/Brushes
-|-- Xcf |-- Xcf
-| |-- 1.xcf | |-- 1.xcf
-| |-- 2.xcf | |-- 2.xcf
-| `-- 3.xcf | `-- 3.xcf
-|-- 1.gbr |-- 1.gbr
-|-- 2.gih |-- 2.gih
-`-- 3.gbr `-- 3.gbr
-@end verbatim
-
-In order for both common brushes and theme-specific brushes to be
-loaded by GIMP, related @file{.gbr} and @file{.gih} brush files need
-to be stored under @file{~/.gimp-2.2/brushes} directory. This location
-is out of CentOS Artwork Repository and provides no version control by
-itself. This way, brushes aren't exported to this location but into
-the repository directory structure which is versioned. Later, we
-create symbolic links in @file{~/.gimp-2.2/brushes} to connect file
-brushes inside the repository and, this way, provide the configuration
-needed by GIMP to use the brush files produced inside the repository.
-
-@quotation
-@strong{Warning}
-When brushes are added to or removed from the repository, you need to
-update your working copy and all information related to brushes inside
-your workstation (e.g., brush links in @file{~/.gimp-2.2/brushes} and
-the Brushes panel in GIMP). Otherwise, you may end up with broken
-links or brushes in the repository that wouldn't be available for you
-to use in GIMP.
-@end quotation
-
-Inside the repository, common brushes and theme-specific brushes are
-created individually in different locations, but they all are linked
-from one unique location (i.e., @file{~/.gimp-2.2/brushes}). This
-configuration may provoke brush overlapping if a name convenction is
-not implemented correctly. In that sake, file names used for brushes
-inside the repository must be unique, no matter where they be.
-
-As file name convenction inside the repository, brushes are named
-using lowercase letters, numbers, minus characters and dot characters,
-only. Additionally, when links are built, we use one suffix for those
-brushes retrived from @file{trunk/Identity/Brushes} and another suffix
-for those brushes retrivided from theme-specific directories. Using
-both the brush file name and the suffix information, it is possible
-to build unique names for links under @file{~/.gimp-2.2/brushes}
-directory, scalably.
-
-@verbatim
-trunk/Identity/Brushes
-|-- 1.gbr (file) <-- ~/.gimp-2.2/brushes/centos-1.gbr (link)
-|-- 2.gbr (file) <-- ~/.gimp-2.2/brushes/centos-2.gbr (link)
-`-- 3.gbr (file) <-- ~/.gimp-2.2/brushes/centos-3.gbr (link)
-@end verbatim
-
-@verbatim
-trunk/Identity/Images/Themes/THEMENAME/THEMEVERSION/Brushes
-|-- 1.gbr (file) <-- ~/.gimp-2.2/brushes/centos-THEMENAME-THEMEVERSION-1.gbr (link)
-|-- 2.gbr (file) <-- ~/.gimp-2.2/brushes/centos-THEMENAME-THEMEVERSION-2.gbr (link)
-`-- 3.gbr (file) <-- ~/.gimp-2.2/brushes/centos-THEMENAME-THEMEVERSION-3.gbr (link)
-@end verbatim
-
-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, we
-use the same name schema used to name brush links 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}).
-
-@subheading Usage
-
-The way you use brushes is up to your creativeness. However, the way
-brushes are made available needs to be standardized. That's the reason
-of organizing brushes in common brushes and theme-specific brushes.
-
-@subheading Common brushes
-
-Common brushes exist to organize brushes that can be used anywhere
-inside the repository. Inside the repository, common brushes under
-@file{trunk/Identity/Brushes} are mainly used to hold brand
-information related to The CentOS Project (e.g., symbols, logos,
-trademarks, etc.).
-
-Common brushes are always made available under
-@file{~/.gimp-2.2/brushes} directory after preparing the repository
-(@pxref{Directories trunk Scripts Functions Prepare}).
-
-@subheading Theme-specific brushes
-
-Theme-specific brushes exist to organize brushes that can be used
-inside specific artistic motifs only. Inside the repository,
-theme-specific brushes are stored in a directory named @file{Brushes}
-which is stored in the first directory level under the artistic motif
-directory structure. Each artistic motif inside the repository has its
-own @file{Brushes} directory and uses it to store brushes that can be
-considered auxiliars to that artistic motif construction.
-
-Theme-specific brushes aren't made available under
-@file{~/.gimp-2.2/brushes} directory after preparing the repository.
-In order to make theme-specific brushes available under
-@file{~/.gimp-2.2./brushes} it is required to activate/deactivate them
-using the @code{theme} functionality of @command{centos-art.sh}
-script. @c (@pxref{Directories trunk Scripts Functions Theme}).
-
-@subheading See also
-
-@itemize
-@item @url{file:///usr/share/gimp/2.0/help/en/index.html,The Gimp
-Manual}, specifically the section related to
-@url{file:///usr/share/gimp/2.0/help/en/gimp-concepts-brushes.html,
-Brushes}.
-@item @ref{Directories trunk Identity}
-@item @ref{Directories trunk}
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Fonts.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Fonts.texinfo
deleted file mode 100644
index ea4b08b..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Fonts.texinfo
+++ /dev/null
@@ -1,44 +0,0 @@
-@subheading Goals
-
-This section describes how typographies are organized in the
-repository and how to make them available for you to use in
-@acronym{GIMP,GNU Image Manipulation Program} and Inkscape.
-
-@subheading Description
-
-The CentOS Project Corporate Identity is attached to @samp{DejaVu LGC}
-font-family and @samp{Denmark} font-family.
-
-@image{trunk/Identity/Images/Manual/Fonts/dejavu-lgc,430pt,,,jpg}
-
-@image{trunk/Identity/Images/Manual/Fonts/denmark,430pt,,,jpg}
-
-@quotation
-@strong{Caution}
-The copyright and license of @samp{Denmark} typography aren't very
-specific and that issue may represent a threat to The CentOS Project
-Corporate Identity.
-@end quotation
-
-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). If the typography used
-to build The CentOS Logo is compromised somehow, the whole corporate
-visual identity it represents would be compromised, as well. To
-prevent such issues, it would be better for The CentOS Project to move
-on from @samp{Denmark} typography to another typography (free,
-preferably) that retain the same visual style of @samp{Denmark}, but
-intruce a clearer copyright and license notice.
-
-@subheading Usage
-
-@itemize
-@item @xref{Directories trunk Identity Models Brands}.
-@end itemize
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk Identity}.
-@item @ref{Directories trunk}.
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Images.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Images.texinfo
deleted file mode 100755
index cbc5503..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Images.texinfo
+++ /dev/null
@@ -1,24 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk Identity}
-@item @ref{Directories trunk}
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes.texinfo
deleted file mode 100644
index 0bf7e5d..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes.texinfo
+++ /dev/null
@@ -1,89 +0,0 @@
-@subheading Goals
-
-The @file{trunk/Identity/Themes/} directory exists to organize
-production of CentOS themes.
-
-@subheading Description
-
-Initially, we start working themes on their trunk development line
-(e.g., @file{trunk/Identity/Images/Themes/TreeFlower/}), here we
-organize information that cannot be produced automatically (i.e.,
-background images, concepts, color information, screenshots, etc.).
-
-Later, when theme trunk development line is considered ``ready'' for
-implementation (e.g., all required backgrounds have been designed),
-we create a branch for it (e.g.,
-@file{branches/Identity/Images/Themes/TreeFlower/1/}). Once the
-branch has been created, we forget that branch and continue working
-the trunk development line while others (e.g., an artwork quality
-assurance team) test the new branch for tunning it up.
-
-Once the branch has been tunned up, and considered ``ready'' for
-release, it is freezed under @file{tags/} directory (e.g.,
-@file{tags/Identity/Images/Themes/TreeFower/1.0/}) for packagers,
-webmasters, promoters, and anyone who needs images from that CentOS
-theme the tag was created for.
-
-Both branches and tags, inside CentOS Artwork Repository, use
-numerical values to identify themselves under the same location.
-Branches start at one (i.e., @samp{1}) and increment one unit for each
-branch created from the same trunk development line. Tags start at
-zero (i.e., @samp{0}) and increment one unit for each tag created from
-the same branch development line.
-
-@quotation
-@strong{Convenction} Do not freeze trunk development lines using tags
-directly. If you think you need to freeze a trunk development line,
-create a branch for it and then freeze that branch instead.
-@end quotation
-
-The trunk development line may introduce problems we cannot see
-immediatly. Certainly, the high changable nature of trunk development
-line complicates finding and fixing such problems. On the other hand,
-the branched development lines provide a more predictable area where
-only fixes/corrections to current content are commited up to
-repository.
-
-If others find and fix bugs inside the branched development line, we
-could merge such changes/experiences back to trunk development line
-(not visversa) in order for future branches, created from trunk, to
-benefit.
-
-Time intervals used to create branches and tags may vary, just as
-different needs may arrive. For example, consider the release schema
-of CentOS distribution: one major release every 2 years, security
-updates every 6 months, support for 7 years long. Each time a CentOS
-distribution is released, specially if it is a major release, there is
-a theme need in order to cover CentOS distribution artwork
-requirements. At this point, is where CentOS Artwork Repository comes
-up to scene.
-
-Before releasing a new major release of CentOS distribution we create
-a branch for one of several theme development lines available inside
-the CentOS Artwork Repository, perform quality assurance on it, and
-later, freeze that branch using tags. Once a the theme branch has been
-frozen (under @file{tags/} directory), CentOS Packagers (the persons
-whom build CentOS distribution) can use that frozen branch as source
-location to fulfill CentOS distribution artwork needs. The same
-applies to CentOS Webmasters (the persons whom build CentOS websites),
-and any other visual manifestation required by the project.
-
-@subheading Usage
-
-In this location themes are organized in ``Models'' ---to store common
-information--- and ``Motifs''---to store unique information. At
-rendering time, both motifs and models are combined to produce the
-final CentOS themes. CentOS themes can be tagged as ``Default'' or
-``Alternative''. CentOS themes are maintained by CentOS community.
-
-@itemize
-@item @xref{Directories trunk Identity Models Themes}.
-@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Motifs) ---.
-@end itemize
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk Identity}.
-@item @ref{Directories trunk}.
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs.texinfo
deleted file mode 100644
index 85ff9ea..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs.texinfo
+++ /dev/null
@@ -1,165 +0,0 @@
-@subheading Goals
-
-The @file{trunk/Identity/Images/Themes} directory exists to:
-
-@itemize
-@item Organize CentOS themes' artistic motifs.
-@end itemize
-
-@subheading Description
-
-The artistic motif of theme is a graphic design component that
-provides the visual style of themes, it is used as pattern to connect
-all visual manifestations inside one unique theme.
-
-Artistic motifs are based on conceptual ideas. Conceptual ideas bring
-the motivation, they are fuel for the engines of human imagination.
-Good conceptual ideas may produce good motivation to produce almost
-anything, and art works don't escape from it.
-
-@table @samp
-@item TreeFlower
-CentOS like trees, has roots, trunk, branches, leaves and flowers. Day
-by day they work together in freedom, ruled by the laws of nature and
-open standards, to show the beauty of its existence.
-@item Modern
-Modern, squares and circles flowing up.
-@end table
-
-If you have new conceptual ideas for CentOS, then you can say that you
-want to create a new artistic motif for CentOS. To create a new
-artistic motif you need to create a directory under
-@file{Identity/Images/Themes/} using a name coherent with your
-conceptual idea. That name will be the name of your artistic motif. If
-possible, when creating new conceptual ideas for CentOS, think about
-what CentOS means for you, what does it makes you feel, take your
-time, think deep, and share; you can improve the idea as time goes on.
-
-Once you have defined a name for your theme, you need to create the
-motif structure of your theme. The motif structure is the basic
-direcotry structure you'll use to work your ideas. Here is where you
-organize your graphic design projects.
-
-To add a new motif structure to CentOS Artwork Repository, you need to
-use the @command{centos-art} command line in the
-@file{Identity/Images/Themes/} directory as described below:
-
-@example
-centos-art add --motif=ThemeName
-@end example
-
-The previous command will create the basic structure of themes for
-you. The basic structure produced by @command{centos-art} command is
-illustrated in the following figure:
-
-@example
-trunk/Identity/Images/Themes/$ThemeName/
-|-- Backgrounds
-| |-- Img
-| `-- Tpl
-|-- Info
-| |-- Img
-| `-- Tpl
-|-- Palettes
-`-- Screenshots
-@end example
-
-@subheading Usage
-
-When designing artistic motifs for CentOS, consider the following
-recommendations:
-
-@itemize
-@item Give a unique (case-sensitive) name to your Motif. This name is
-used as value wherever theme variable (@b{$THEME}) or translation marker
-(@b{=THEME=}) is. Optionally, you can add a description about
-inspiration and concepts behind your work.
-
-@item Use the location @file{trunk/Identity/Images/Themes/$THEME/} to
-store your work. If it doesn't exist create it. Note that this require
-you to have previous commit access in CentOS Artwork Repository.
-
-@item The CentOS Project is using the blue color (@b{#204c8d}) as base
-color for its corporate visual identity. Use such base corporate color
-information as much as possible in your artistic motif designs.
-
-@item Try to make your design fit one of the theme models.
-
-@item Feel free to make your art enterprise-level and beautiful.
-
-@item Add the following information on your artwork (both in a visible
-design area and document metadata):
-
-@itemize
-
-@item The name (or logo) of your artistic motif.
-
-@item The copyright sentence: @b{Copyright (C) YEAR YOURNAME}
-
-@item The license under which the work is released. All CentOS Art
-works are released under
-@url{http://creativecommons.org/licenses/by-sa/3.0/,Creative Common
-Share-Alike License 3.0}
-(@url{http://creativecommons.org/licenses/by-sa/3.0/}).
-
-@end itemize
-@end itemize
-
-@subheading See also
-
-@menu
-* Directories trunk Identity Images Themes::
-* Directories trunk Identity::
-* Directories trunk::
-@end menu
-
-The @file{Backgrounds/} directory is used to organize artistic motif
-background images and the projects used to build those images.
-
-Background images are linked (using the @b{import} feature of
-Inkscape) inside almost all theme art works. This structure let you
-make centralized changes on the visual identity and propagate them
-quickly to other areas.
-
-In this configuration you design background images for different
-screen resolutions based on the theme artistic motif.
-
-You may create different artistic motifs propositions based
-on the same conceptual idea. The conceptual idea is what defines a
-theme. Artistic motifs are interpretations of that idea.
-
-Inside this directory artistic motifs are organized by name (e.g.,
-TreeFlower, Modern, etc.).
-
-Each artistic motif directory represents just one unique artistic
-motif.
-
-The artistic motif is graphic design used as common pattern to connect
-all visual manifestations inside one unique theme. The artistic motif
-is based on a conceptual idea. Artistic motifs provide visual style
-to themes.
-
-Designing artistic motifs is for anyone interested in creating
-beautiful themes for CentOS. When building a theme for CentOS, the
-first design you need to define is the artistic motif.
-
-Inside CentOS Artwork Repository, theme visual styles (a.k.a.,
-artistic motifs) and theme visual structures (a.k.a., design models)
-are two different working lines. When you design an artistic motif
-for CentOS you concentrate on its visual style, and eventualy, use the
-@command{centos-art} command line interface to render the visual
-style, you are currently producing, against an already-made theme
-model in order to produce the final result. Final images are stored
-under @file{Motifs/} directory using the model name, and the model
-directory structure as reference.
-
-The artistic motif base structure is used by @command{centos-art} to
-produce images automatically. This section describes each directory of
-CentOS artistic motif base structure.
-
-The @file{Backgrounds/} directory is probably the core component,
-inside @file{Motifs/} directory structure. Inside @file{Backgrounds/}
-directory you produce background images used by almost all theme
-models (e.g., Distribution, Websites, Promotion, etc.). The
-@file{Backgrounds/} directory can contain subdirectories to help you
-organize the design process.
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs/Flame.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs/Flame.texinfo
deleted file mode 100644
index 3cfae8b..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs/Flame.texinfo
+++ /dev/null
@@ -1,120 +0,0 @@
-@subheading Goals
-
-This section describes the @emph{Flame} artistic motif. This section
-may be useful for anyone interested in reproducing the @emph{Flame}
-artistic motif, or in creating new artistic motifs for The CentOS
-Project corporate visual identity.
-
-@subheading Description
-
-The @emph{Flame} artistic motif was built using the flame filter of
-Gimp 2.2 in CentOS 5.5.
-
-The flame filter of Gimp can produce stunning, randomly generated
-fractal patterns. The flame filter of Gimp gives us a great oportunity
-to reduce the time used to produce new artistic motifs, because of its
-``randomly generated'' nature. Once the artistic motif be created, it
-is propagated through all visual manifestations of CentOS Project
-corporate visual identity using the @file{centos-art.sh} script
-(@pxref{Directories trunk Scripts}) inside the CentOS Artwork
-Repository.
-
-To set the time intervals between each new visual style production, we
-could reuse the CentOS distribution major release schema. I.e., we
-could produce a new visual style, every two years, based on a new
-``randomly generated'' flame pattern, and publish the whole corporate
-visual identity (i.e., distribution stuff, promotion stuff, websites
-stuff, etc.) with the new major release of CentOS distribution all
-together at once.
-
-Producing a new visual style is not one day's task. Once we have
-defined the artistic motif, we need to propagate it through all visual
-manifestations of The CentOS Project corporate visual identity. When
-we say that we could produce one new visual style every two years we
-really mean: to work two years long in order to propagate a new visual
-style to all visual manifestations of The CentOS Project corporate
-visual identity.
-
-Obviously, in order to propagate one visual style to all different
-visual manifestations of The CentOS Project corporate visual identity,
-we need first to know which the visual manifestations are. To define
-which visual manifestations are inside The CentOS Project corporate
-visual identity is one of the goals the CentOS Artwork Repository and
-this documentation manual are both aimed to satisfy.
-
-Once we define which the visual manifestation are, it is possible to
-define how to produce them, and this way, organize the automation
-process. Such automation process is one of the goals of
-@file{centos-art.sh} script.
-
-With the combination of both CentOS Artwork Repository and
-@file{centos-art.sh} scripts we define work lines where translators,
-programmers, and graphic designers work together to distribute and
-reduce the amount of time employed to produce The CentOS Project
-monolithic corporate identity.
-
-From a monolithic corporate visual identity point of view, notice that
-we are producing a new visual style for the same theme (i.e.,
-@emph{Flame}). It would be another flame design but still a flame
-design. This idea is very important to be aware of, because we are
-somehow ``refreshing'' the theme, not changing it at all.
-
-This way, as we are ``refreshing'' the theme, we still keep oursleves
-inside the monolithic conception we are trying to be attached to
-(i.e., one unique name, and one unique visual style for all visual
-manifestations).
-
-Producing artistic motifs is a creative process that may consume long
-time, specially for people without experienced knowledge on graphic
-design land. Using ``randomly generated'' conception to produce
-artistic motifs could be, practically, a way for anyone to follow in
-order to produce maintainable artistic motifs in few steps.
-
-Due to the ``randomly generated'' nature of Flame filter, we find that
-@emph{Flame} pattern is not always the same when we use @emph{Flame}
-filter interface.
-
-Using the same pattern design for each visual manifestation is
-essential in order to maintain the visual connection among all visual
-manifestations inside the same theme. Occasionally, we may introduce
-pattern variations in opacity, size, or even position but never change
-the pattern design itself, nor the color information used by images
-considered part of the same theme.
-
-@quotation
-@strong{Important}
-When we design background images, which are considered part of the
-same theme, it is essential to use the same design pattern always.
-This is what makes theme images to be visually connected among
-themeselves, and so, the reason we use to define the word ``theme''
-as: a set of images visually connected among themeselves.
-@end quotation
-
-In order for us to reproduce the same flame pattern always,
-@emph{Flame} filter interface provides the @samp{Save} and @samp{Open}
-options. The @samp{Save} option brings up a file save dialog that
-allows you to save the current Flame settings for the plug-in, so that
-you can recreate them later. The @samp{Open} option brings up a file
-selector that allows you to open a previously saved Flame settings
-file.
-
-The Flame settings we used in our example are saved in the file named
-@file{800x600.xcf-flame.def}, inside the @file{Backgrounds/Xcf}
-directory structure.
-
-@ifhtml
-@subheading Screenshots
-
-@image{trunk/Identity/Images/Themes/Flame/1/Concept/motif-thumb-250,,,,jpg}
-@image{trunk/Identity/Images/Themes/Flame/2/Concept/motif-thumb-250,,,,jpg}
-@image{trunk/Identity/Images/Themes/Flame/3/Concept/motif-thumb-250,,,,jpg}
-@end ifhtml
-
-@subheading See also
-
-@itemize
-@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Motifs) ---.
-@item @xref{Directories trunk Identity Images Themes}.
-@item @xref{Directories trunk Identity}.
-@item @xref{Directories trunk}.
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs/Modern.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs/Modern.texinfo
deleted file mode 100644
index df12723..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs/Modern.texinfo
+++ /dev/null
@@ -1,24 +0,0 @@
-@subheading Goals
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@ifhtml
-@subheading Screenshots
-
-@image{trunk/Identity/Images/Themes/Modern/1/Concept/motif-thumb-250,,,,jpg}
-@end ifhtml
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs/Pipes.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs/Pipes.texinfo
deleted file mode 100755
index 80f2bcc..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs/Pipes.texinfo
+++ /dev/null
@@ -1,28 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@ifhtml
-@subheading Screenshots
-
-@image{trunk/Identity/Images/Themes/Pipes/1/Concept/motif-thumb-250,,,,jpg}
-@end ifhtml
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs/TreeFlower.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs/TreeFlower.texinfo
deleted file mode 100644
index 9c31afb..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Images/Themes/Motifs/TreeFlower.texinfo
+++ /dev/null
@@ -1,19 +0,0 @@
-@subheading Goals
-
-@subheading Description
-
-@ifhtml
-@subheading Screenshots
-
-@image{trunk/Identity/Images/Themes/TreeFlower/1/Concept/motif-thumb-250,,,,jpg}
-@image{trunk/Identity/Images/Themes/TreeFlower/2/Concept/motif-thumb-250,,,,jpg}
-@image{trunk/Identity/Images/Themes/TreeFlower/3/Concept/motif-thumb-250,,,,jpg}
-@image{trunk/Identity/Images/Themes/TreeFlower/4/Concept/motif-thumb-250,,,,jpg}
-@end ifhtml
-
-@subheading Usage
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models.texinfo
deleted file mode 100755
index 7e764ff..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models.texinfo
+++ /dev/null
@@ -1,23 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item @dots{}
-@end itemize
-
-@subheading See also
-
-@itemize
-@item ...
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Brands.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Brands.texinfo
deleted file mode 100644
index d9b7c62..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Brands.texinfo
+++ /dev/null
@@ -1,71 +0,0 @@
-@subheading Goals
-
-This section describes The CentOS Brand design models.
-
-@subheading Description
-
-The CentOS Brand provides the one unique name or trademark that
-connects the producer with their products. In this case, the producer
-is The CentOS Project and the products are The CentOS Project visual
-manifestations.
-
-The CentOS Brand is the main visual representation of the CentOS
-project so the typography used in it must be the same always, no
-matter where it be shown. It also has to be clear enough to dismiss
-any confussion between similar typefaces (e.g., the number one (1)
-sometimes is confuesed with the letter @samp{el} (l) or letter
-@samp{ai} (i)).
-
-As convenction, the word @samp{CentOS} uses @samp{Denmark} typography
-as base, both for the word @samp{CentOS} and the phrase
-@samp{Community Enterprise Operating System}. The phrase size of
-CentOS logo is half the size in poits the word @samp{CentOS} has and
-it below @samp{CentOS} word and aligned with it on the left. The
-distance between @samp{CentOS} word and phrase @samp{Community
-Enterprise Operating System} have the size in points the phrase has.
-
-@image{trunk/Identity/Images/Manual/Brands/Logos/a,,,,}
-
-When the CentOS release brand is built, use @samp{Denmark} typography
-for the release number. The release number size is two times larger
-(in height) than default @samp{CentOS} word. The separation between
-release number and @samp{CentOS} word is twice the size in points of
-separation between @samp{CentOS} word and phrase @samp{Community
-Enterprise Operating System}.
-
-Another component inside CentOS logo is the trademark symbol (TM).
-This symbol specifies that the CentOS logo must be consider a product
-brand, even it is not a registered one. The trademark symbol uses
-DejaVu LGC Sans Regular typography. The trademark symbol is aligned
-right-top on the outter side of @samp{CentOS} word. The trademark
-symbol must not exceed haf the distance, in points, between
-@samp{CentOS} word and the release number on its right.
-
-It would be very convenient for the CentOS Project and its community
-to to make a registered trademark (®) of CentOS logo. To make a
-register trademark of CentOS Logo prevents legal complications in the
-market place of brands. It grants the consistency, through time, of
-CentOS project corporate visual identity.
-
-@quotation
-@strong{Note} The information about trademarks and corporate identity
-is my personal interpretation of
-@url{http://en.wikipedia.org/Corporate_identity} and
-@url{http://en.wikipedia.org/Trademark} description. If you have
-practical experiences with these affairs, please serve yourself to
-improve this section with your reasons.
-@end quotation
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk Identity Models}
-@item @ref{Directories trunk Identity}
-@item @ref{Directories trunk}
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes.texinfo
deleted file mode 100644
index 375e1b3..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes.texinfo
+++ /dev/null
@@ -1,46 +0,0 @@
-@subheading Goals
-
-This section describes design models from The CentOS Themes.
-
-@subheading Description
-
-Theme models let you modeling characteristics (e.g., dimensions,
-translation markers, position of each element on the display area,
-etc.) common to all themes. Theme models let you reduce the time
-needed when propagating artistic motifs to different visual
-manifestations.
-
-Theme models serves as a central pool of design templates for themes
-to use. This way you can produce themes with different artistic motifs
-but same characteristics.
-
-@subsubheading Default Design Model
-
-Default Design Models for CentOS Themes provide the common structural
-information (e.g., image dimensions, translation markers, trademark
-position, etc.) the @command{centos-art} script uses to produce images
-when no other design model is specified.
-
-@subsubheading Alternative Design Models
-
-CentOS alternative theme models exist for people how want to use a
-different visual style on their installations of CentOS distribution.
-As the visual style is needed for a system already installed
-components like Anaconda are not required inside alternative themes.
-Inside alternative themes you find post-installation visual style only
-(i.e. Backgrounds, Display Managers, Grub, etc.). CentOS alternative
-themes are maintained by CentOS Community.
-
-@subheading Usage
-
-@itemize
-@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default) ---.
-@end itemize
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk Identity Images Themes}.
-@item @ref{Directories trunk Identity}.
-@item @ref{Directories trunk}.
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default.texinfo
deleted file mode 100644
index 60f0afd..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default.texinfo
+++ /dev/null
@@ -1,79 +0,0 @@
-@subheading Goals
-
-This section describes the default design model of The CentOS Themes.
-
-@subheading Description
-
-The @file{trunk/Identity/Themes/Models/Default} directory implements
-the concept of @emph{Default Design Model} for The CentOS Themes. The
-CentOS Themes Default Design Model provides the common structural
-information (e.g., image dimensions, translation markers, trademark
-position, etc.) the @command{centos-art} script uses to produce images
-when no other design model is specified.
-
-Deisgn models in this directory do use the @emph{CentOS Release
-Brand}. The CentOS Release Brand is a combination of both The CentOS
-Type and The CentOS Release Schema used to illustrate the major
-release of The CentOS Distribution the image produced belongs to. ---
-@strong{Removed}(xref:Directories trunk Identity Models Tpl Brands)
----, for more information.
-
-The CentOS Project maintains near to four different major releases of
-CentOS Distribution. Each major release of CentOS Distribution has
-internal differences that make them unique and, at the same time, each
-CentOS Distribution individually is tagged into the one unique visual
-manifestation (i.e., Distribution). So, how could we implement the
-monolithic visual structure in one visual manifestation that has
-internal difference?
-
-To answer this question we broke the question in two parts and later
-combined the resultant answers to build a possible solution.
-
-@table @strong
-@item How to remark the internal differences visually?
-
-Merge both The CentOS Project Release Schema into The CentOS Project
-Trademark to build The CentOS Project Release Trademark. The CentOS
-Project Release Trademark remarks two things: first, it remarks the
-image is from The CentOS Project and second, it remarks which major
-release of CentOS Distribution does the image belongs to.
---- @strong{Removed}(xref:Directories trunk Identity Models Tpl Brands) ---, for more
-information on how to develop and improve The CentOS Project Brand.
-
-@item How to remark the visual resemblance?
-
-Use a common artistic motifs as background for all CentOS Distribution
-images. --- @strong{Removed}(xref:Directories trunk Identity Images Themes Motifs) ---, for more
-information.
-
-@item So, combining answers above, we could conclude that:
-
-In order to implement the CentOS Monolithic Visual Structure on CentOS
-Distribution visual manifestations, a CentOS Release Trademark and a
-background information based on one unique artistic motif should be
-used in all remarkable images The CentOS Distribution visual
-manifestation is made of.
-@end table
-
-@quotation
-@strong{Important} Remarking the CentOS Release Schema inside each
-major release of CentOS Distribution ---or similar visual
-manifestations--- takes @emph{high attention} inside The CentOS
-Project corporate visual identity. It should be very clear for
-everyone which major release of CentOS Distribution is being used.
-@end quotation
-
-@subheading Usage
-
-@itemize
-@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro) ---.
-@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Concept) ---.
-@end itemize
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk Identity Images Themes}
-@item @ref{Directories trunk Identity Models Themes}
-@item --- @strong{Removed}(ref:Directories trunk Identity Images Themes Motifs) ---
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Concept.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Concept.texinfo
deleted file mode 100755
index e226b31..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Concept.texinfo
+++ /dev/null
@@ -1,22 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro.texinfo
deleted file mode 100644
index 6cee901..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro.texinfo
+++ /dev/null
@@ -1,111 +0,0 @@
-@subheading Goals
-
-This section organizes default design models for different major
-releases of CentOS Distribution.
-
-@subheading Description
-
-In order to better understatand how this visual manifestation is
-organized, it is necessary to consider what The CentOS Distribution is
-and how it is released.
-
-@subsubheading The CentOS Distribution
-
-The CentOS Distribution is an Enterprise-class Linux Distribution
-derived from sources freely provided to the public by a prominent
-North American Enterprise Linux vendor. The CentOS Distribution
-conforms fully with the upstream vendors redistribution policy and
-aims to be 100% binary compatible. (The CentOS Project mainly changes
-packages to remove upstream vendor branding and artwork.)
-
-The CentOS Distribution 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.
-
-@subsubheading The CentOS Distribution Release Schema
-
-The upstream vendor has released 4 versions of their
-@acronym{EL,Enterprise Linux} product that The CentOS Project rebuilds
-the freely available SRPMS for. The upstream vendor releases security
-updates as required by circumstances. The CentOS Project releases
-rebuilds of security updates as soon as possible. Usually within 24
-hours (our stated goal is with 72 hours, but we are usually much
-faster).
-
-The upstream vendor also releases numbered update sets for major
-versions of their EL product from 2 to 4 times per year. There are new
-ISOs from the upstream vendor provided for these update sets. Update
-sets will be completed as soon as possible after the upstream vendor
-releases their version @dots{} generally within 2 weeks. The CentOS
-Project follows these conventions as well, so CentOS-3.9 correlates
-with EL 3 update 9 and CentOS-4.6 correlates with EL 4 update 6,
-CentOS-5.1 correlates to EL 5 update 1, etc.
-
-One thing some people have problems understanding is that if you have
-any CentOS-3 product and update it, you will be updated to the latest
-CentOS-3.x version.
-
-The same is true for CentOS-4 and CentOS-5. If you update any CentOS-4
-product, you will be updated to the latest CentOS-4.x version, or to
-the latest CentOS-5.x version if you are updating a CentOS-5 system.
-This is exactly the same behavior as the upstream product. Let's
-assume that the latest EL4 product is update 6. If you install the
-upstream original EL4 CDs (the ones before any update set) and upgrade
-via @command{yum}, you will have latest update set installed (EL4
-update 6 in our example). Since all updates within a major release
-(CentOS-2, CentOS-3, CentOS-4, CentOS-5) always upgrade to the latest
-version when updates are performed (thus mimicking upstream behavior),
-only the latest version is maintained in each main tree on The CentOS
-Mirrors (@url{http://mirrors.centos.org/}).
-
-There is a CentOS Vault (@url{http://vault.centos.org/}) containing
-old CentOS trees. This vault is a picture of the older tree when it
-was removed from the main tree, and does not receive updates. It
-should only be used for reference.
-
-The CentOS Distribution visual style is controlled by image files.
-These image files are packaged inside The CentOS Distribution and made
-visible once such packages are installed and executed. The way to go
-for changing The CentOS Distribution visual style is changing all
-those image files to add the desired visual style first and later,
-repackage them to make them available inside the final iso files of
-CentOS Distribution.
-
-@subheading Usage
-
-Sometimes, between major releases, image files inside packages can be
-added, removed or just get the name changed. In order to describe such
-variations, the design models directory structure is organized in the
-same way the variations are introduced (i.e., through The CentOS
-Distribution Release Schema). So, each major release of The CentOS
-Distribution has its own design model directory structure.
-
-When a new package/component is added to one or all the major releases
-of The CentOS Distribution, a design model directory structure for
-that component needs to be created. Later, it is filled up with
-related design models. Design models are created for each image file
-inside the component that need to be rebuilt in order to set the
-visual style and brand information correctly.
-
-When a package is removed from one or all major releases of The CentOS
-Distribution, the design model directory structure releated to that
-package/component is no longer used. However, it could be very useful
-for historical reasons. Also, someone could feel motivation enough to
-keep himself documenting it or supporting it for whatever reason.
-
-@itemize
-@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro
-5) ---.
-@end itemize
-
-@subheading See also
-
-@itemize
-@item --- @strong{Removed}(ref:Directories trunk Identity Models Themes Default) ---.
-@item @ref{Directories trunk Identity Models Themes}.
-@item @ref{Directories trunk Identity Images Themes}.
-@item @ref{Directories trunk Identity}.
-@item @ref{Directories trunk}.
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5.5/Notes/Release.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5.5/Notes/Release.texinfo
deleted file mode 100755
index d6bb628..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5.5/Notes/Release.texinfo
+++ /dev/null
@@ -1,23 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@itemize
-@item ...
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5.texinfo
deleted file mode 100755
index c76921e..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5.texinfo
+++ /dev/null
@@ -1,35 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Syslinux) ---.
-@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Anaconda) ---.
-@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Rhgb) ---.
-@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Gdm) ---.
-@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Kdm) ---.
-@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Grub) ---.
-@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Gsplash) ---.
-@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Ksplash) ---.
-@end itemize
-
-@subheading See also
-
-@itemize
-@item --- @strong{Removed}(ref:Directories trunk Identity Models Themes Default Distro) ---.
-@item --- @strong{Removed}(ref:Directories trunk Identity Models Themes Default) ---.
-@item @ref{Directories trunk Identity Models Themes}.
-@item @ref{Directories trunk Identity Images Themes}.
-@item @ref{Directories trunk Identity}.
-@item @ref{Directories trunk}.
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Anaconda.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Anaconda.texinfo
deleted file mode 100644
index c10b6dd..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Anaconda.texinfo
+++ /dev/null
@@ -1,14 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@subheading Usage
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Firstboot.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Firstboot.texinfo
deleted file mode 100755
index e226b31..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Firstboot.texinfo
+++ /dev/null
@@ -1,22 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gdm.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gdm.texinfo
deleted file mode 100755
index 53ef237..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gdm.texinfo
+++ /dev/null
@@ -1,30 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-Another example of using last-rendition flow is that related to GDM
-and KDM @file{tar.gz} file construction. Each @file{tar.gz} file is
-made of several files that need to be put together in order to make
-them installable. In the very specific case of GDM and KDM some of the
-required files are retrived from design models directory structure and
-others from artistic motifs directory structure after had been
-produced through base-rendition. In this case, the action of grouping
-files and packing them is realized through last-rendition action. This
-couldn't be possible through post-rendition because we need to wait to
-have two images first (produced through base-rendition) before we
-could grouping them all into the @file{tar.gz} package.
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Grub.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Grub.texinfo
deleted file mode 100755
index e226b31..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Grub.texinfo
+++ /dev/null
@@ -1,22 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gsplash.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gsplash.texinfo
deleted file mode 100755
index e226b31..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gsplash.texinfo
+++ /dev/null
@@ -1,22 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Kdm.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Kdm.texinfo
deleted file mode 100755
index e226b31..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Kdm.texinfo
+++ /dev/null
@@ -1,22 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Ksplash.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Ksplash.texinfo
deleted file mode 100755
index 02aa8be..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Ksplash.texinfo
+++ /dev/null
@@ -1,25 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-The @file{Preview.png} image of Ksplash which is made of three
-different images. In order to build the @file{Preview.png} image, we
-need to create the three images the @file{Preview.png} image is made
-of first (e.g., through base-rendition) and then, combine them all
-together into one new image, the @file{Preview.png} image in this
-case.
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Rhgb.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Rhgb.texinfo
deleted file mode 100755
index e226b31..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Rhgb.texinfo
+++ /dev/null
@@ -1,22 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Syslinux.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Syslinux.texinfo
deleted file mode 100755
index d6bb628..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Syslinux.texinfo
+++ /dev/null
@@ -1,23 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@itemize
-@item ...
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Posters.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Posters.texinfo
deleted file mode 100644
index e226b31..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Models/Themes/Default/Posters.texinfo
+++ /dev/null
@@ -1,22 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Palettes.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Palettes.texinfo
deleted file mode 100755
index e226b31..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Palettes.texinfo
+++ /dev/null
@@ -1,22 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Patterns.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Patterns.texinfo
deleted file mode 100755
index cbc5503..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Patterns.texinfo
+++ /dev/null
@@ -1,24 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk Identity}
-@item @ref{Directories trunk}
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Identity/Webenv.texinfo b/Manuals/Texinfo/Directories/trunk/Identity/Webenv.texinfo
deleted file mode 100755
index 5736d03..0000000
--- a/Manuals/Texinfo/Directories/trunk/Identity/Webenv.texinfo
+++ /dev/null
@@ -1,327 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-The CentOS web environment is formed by a central web application
----to cover base needs (e.g., per-major release information like
-release notes, lifetime, downloads, documentation, support, security
-advisories, bugs, etc.)--- and many different free web applications
----to cover specific needs (e.g., wiki, mailing lists, etc.)---.
-
-The CentOS web environment is addressed to solve the following issues:
-
-@itemize
-@item One unique name and one unique visual style to all web
-applications used inside the web environment.
-
-@item One-step navigation to web applications inside the environment.
-
-@item High degree of customization to change the visual style of all
-web applications with few changes (e.g, updating just two or three
-images plus common style sheet [CSS] definitions).
-@end itemize
-
-The CentOS project is attached to a monolithic corporate visual
-identity (@pxref{Directories trunk Identity}), where all visual manifestations
-have one unique name and one unique visual style. This way, the CentOS
-web environment has one unique name (the CentOS brand) and one unique
-visual style (the CentOS default theme) for all its visual
-manifestations, the web applications in this case.
-
-Since a maintainance point of view, achiving the one unique visual
-style inside CentOS web environment is not a simple task. The CentOS
-web environment is built upon many different web applications which
-have different visual styles and different internal ways to customize
-their own visual styles. For example: MoinMoin, the web application
-used to support the CentOS wiki (@url{http://wiki.centos.org/}) is
-highly customizable but Mailman (in its 2.x.x serie), the web
-application used to support the CentOS mailing list, doesn't
-support@footnote{The theme support of Mailman may be introduced in
-mailman-3.x.x release.} a customization system that separates
-presentation from logic, similar to that used by MoinMoin.
-
-This visual style diversity complicates our goal of one unique visual
-style for all web applications. So, if we want one unique visual style
-for all web applications used, it is innevitable to modify the web
-applications in order to implement the CentOS one unique visual style
-customization in them. Direct modification of upstream applications is
-not convenient because upstream applications come with their one
-visual style and administrators take the risk of loosing all
-customization changes the next time the application be updated (since
-not all upstream web applications, used in CentOS web environment,
-separate presentation from logic).
-
-To solve the ``one unique visual style'' issue, installation and
-actualization of web applications ---used inside CentOS web
-environment--- need to be independent from upstream web applications
-development line; in a way that CentOS web environment administrators
-can install and update web applications freely without risk of loosing
-the one unique visual style customization changes.
-
-At the surface of this issue we can see the need of one specific yum
-repository to store CentOS web environment customized web applications.
-
-@subsubheading Design model (without ads)
-
-@subsubheading Design model (with ads)
-
-@subsubheading HTML definitions
-
-@subsubheading Controlling visual style
-
-Inside CentOS web environment, the visual style is controlled by the
-following compenents:
-
-@table @strong
-@item Webenv header background
-@verbatim
-trunk/Identity/Images/Themes/$THEME/Backgrounds/Img/1024x250.png
-@end verbatim
-
-@item CSS definitions
-@verbatim
-trunk/Identity/Themes/Models/Default/Promo/Web/CSS/stylesheet.css
-@end verbatim
-@end table
-
-@subsubheading Producing visual style
-
-The visual style of CentOS web environment is defined in the following
-files:
-
-@verbatim
-trunk/Identity/Images/Themes/$THEME/Backgrounds/Xcf/1024x250.xcf
-trunk/Identity/Images/Themes/$THEME/Backgrounds/Img/1024x250.png
-trunk/Identity/Images/Themes/$THEME/Backgrounds/Img/1024x250-bg.png
-trunk/Identity/Images/Themes/$THEME/Backgrounds/Tpl/1024x250.svg
-@end verbatim
-
-As graphic designer you use @file{1024x250.xcf} file to produce
-@file{1024x250-bg.png} file. Later, inside @file{1024x250.svg} file,
-you use the @file{1024x250-bg.png} file as background layer to draw
-your vectorial design. When you consider you artwork ready, use the
-@command{centos-art.sh} script, as described below, to produce the
-visual style controller images of CentOS web environment.
-
-@verbatim
-centos-art render --entry=trunk/Identity/Images/Themes/$THEME/Backgrounds --filter='1024x250'
-@end verbatim
-
-Once you have rendered required image files, changing the visual style
-of CentOS web environment is a matter of replacing old image files
-with new ones, inside webenv repository file system structure. The
-visual style changes will take effect the next time customization line
-of CentOS web applications be packaged, uploded, and installed from
-[webenv] or [webenv-test] repositories.
-
-@subsubheading Navigation
-
-Inside CentOS web environment, the one-step navegation between web
-applications is addressed using the web environment navigation bar.
-The web environment navigation bar contains links to main applications
-and is always visible no matter where you are inside the web
-environment.
-
-@subsubheading Development and release cycle
-
-The CentOS web environment development and relase cycle is described
-below:
-
-@table @strong
-
-@item Download
-
-The first action is download the source code of web applications we
-want to use inside CentOS web environment.
-
-@quotation
-@strong{Important} The source location from which web application are
-downloaded is very important. Use SRPMs from CentOS @strong{[base]}
-and @strong{[updates]} repositories as first choise, and third party
-repositories (e.g. RPMForge, EPEL, etc.) as last resource.
-@end quotation
-
-@item Prepare
-
-Once web application source code has been downloaded, our duty is
-organize its files inside @samp{webenv} version controlled repository.
-
-When preparing the structure keep in mind that different web
-applications have different visual styles, and also different ways to
-implement it. A convenient way to organize the file system structure
-would be create one development line for each web application we use
-inside CentOS web environment. For example, consider the following
-file system structure:
-
-@verbatim
-https://projects.centos.org/svn/webenv/trunk/
-|-- WebApp1/
-| |-- Sources/
-| | `-- webapp1-0.0.1/
-| |-- Rpms/
-| | `-- webapp1-0.0.1.rpm
-| |-- Srpms/
-| | `-- webapp1-0.0.1.srpm
-| `-- Specs/
-| `-- webapp1-0.0.1.spec
-|-- WebApp2/
-`-- WebAppN/
-@end verbatim
-
-@item Customize
-
-Once web applications have been organized inside the version
-controlled repository file system, use subversion to create the CentOS
-customization development line of web applications source code. For
-example, using the above file system structure, you can create the
-customization development line of @file{webapp1-0.0.1/} with the
-following command:
-
-@verbatim
-svn cp trunk/WebApp1/Sources/webapp1-0.0.1 trunk/WebApp1/Sources/webapp1-0.0.1-webenv
-@end verbatim
-
-The command above creates the following structure:
-
-@verbatim
-https://projects.centos.org/svn/webenv/trunk/
-|-- WebApp1/
-| |-- Sources/
-| | |-- webapp1-0.0.1/
-| | `-- webapp1-0.0.1-webenv/
-| |-- Rpms/
-| | `-- webapp1-0.0.1.rpm
-| |-- Srpms/
-| | `-- webapp1-0.0.1.srpm
-| `-- Specs/
-| `-- webapp1-0.0.1.spec
-|-- WebApp2/
-`-- WebAppN/
-@end verbatim
-
-In the above structure, the @file{webapp1-0.0.1-webenv/} directory is
-the place where you customize the visual style of
-@file{webapp1-0.0.1/} web application.
-
-@quotation
-@strong{Tip} Use the @command{diff} command of Subversion between
-CentOS customization and upstream development lines to know what you
-are changing exactly.
-@end quotation
-
-@item Build packages
-
-When web application has been customized, build the web application
-RPM and SRPM using the source location with @samp{-webenv} prefix.
-
-@verbatim
-https://projects.centos.org/svn/webenv/trunk/
-|-- WebApp1/
-| |-- Sources/
-| | |-- webapp1-0.0.1/
-| | `-- webapp1-0.0.1-webenv/
-| |-- Rpms/
-| | |-- webapp1-0.0.1.rpm
-| | `-- webapp1-0.0.1-webenv.rpm
-| |-- Srpms/
-| | |-- webapp1-0.0.1.srpm
-| | `-- webapp1-0.0.1-webenv.srpm
-| `-- Specs/
-| |-- webapp1-0.0.1.spec
-| `-- webapp1-0.0.1-webenv.spec
-|-- WebApp2/
-`-- WebAppN/
-@end verbatim
-
-@item Release for testing
-
-When the customized web application has been packaged, make packages
-available for testing and quality assurance. This can be achives using
-a [webenv-test] yum repository.
-
-@quotation
-@strong{Note} The [webenv-test] repository is not shipped inside
-CentOS distribution default yum configuraiton. In order to use
-[webenv-test] repository you need to configure it first.
-@end quotation
-
-If some problem is found to install/update/use the customized version
-of web application, the problem is notified somewhere (a bugtracker
-maybe) and the customization face is repated in order to fix the
-problem. To release the new package add a number after @samp{-webenv}
-prefix. For example, if some problem is found in
-@file{webapp1-0.0.1-webenv.rpm}, when it be fixed the new package will
-be named @file{webapp1-0.0.1-webenv-1.rpm}. If a problem is found in
-@file{webapp1-0.0.1-webenv-1.rpm}, when it be fixed the new package
-will be named @file{webapp1-0.0.1-webenv-2.rpm}, and so on.
-
-The ``customization --- release for testing'' process is repeated
-until CentOS quality assurance team considers the package is ready for
-production.
-
-@item Release for production
-
-When customized web application packages are considered ready for
-production they are moved from [webenv-test] to [webenv] repository.
-This action is commited by CentOS quality assurance team.
-
-@quotation
-@strong{Note} The [webenv] repository is not shipped inside CentOS
-distribution default yum configuraiton. In order to use [webenv]
-repository you need to configure it first.
-@end quotation
-@end table
-
-@subsubheading The [webenv-test] repository
-
-@verbatim
-/etc/yum.repos.d/CentOS-Webenv-test.repo
-@end verbatim
-
-@verbatim
-[webenv-test]
-name=CentOS-$releasever - Webenv-test
-mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv-test
-#baseurl=http://mirror.centos.org/centos/$releasever/webenv-test/$basearch/
-gpgcheck=1
-gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever
-enabled=1
-priority=10
-@end verbatim
-
-@subsubheading The [webenv] repository
-
-@verbatim
-/etc/yum.repos.d/CentOS-Webenv.repo
-@end verbatim
-
-@verbatim
-[webenv]
-name=CentOS-$releasever - Webenv
-mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv
-#baseurl=http://mirror.centos.org/centos/$releasever/webenv/$basearch/
-gpgcheck=1
-gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever
-enabled=1
-priority=10
-@end verbatim
-
-@subsubheading Priority configuration
-
-Both [webenv] and [webenv-test] repositories update packages inside
-CentOS [base] and CentOS [updates] repositories.
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@menu
-@end menu
diff --git a/Manuals/Texinfo/Directories/trunk/Locales.texinfo b/Manuals/Texinfo/Directories/trunk/Locales.texinfo
deleted file mode 100644
index 823d887..0000000
--- a/Manuals/Texinfo/Directories/trunk/Locales.texinfo
+++ /dev/null
@@ -1,72 +0,0 @@
-@subheading Goals
-
-The @file{trunk/Locales} directory structure provides the localization
-work line and its main goal is provide the translation messages
-required to produce content in different languages.
-
-@subheading Description
-
-Translation messages inside the repository are stored as portable
-objects (e.g., .po, .pot) and machine objects (.mo) under
-@file{trunk/Locales} directory structure.
-
-Translation messages are organized using the directory structure of
-the component being translated. For example, if we want to provide
-translation messages for @file{trunk/Manuals/Repository}, then the
-@file{trunk/Locales/Manuals/Repository} directory needs to be created.
-
-Once the locale directory exists for the component we want to provide
-translation messages for, it is necessary to create the translation
-files where translation messages are. The translation files follows
-the concepts of @command{xml2po} and GNU @command{gettext} tools.
-
-The basic translation process is as follow: first, translatable
-strings are extracted from files and a portable object template (.pot)
-is created or updated with the information. Using the portable object
-template, a portable object (.po) is created or updated for translator
-to locale the messages retrived. Finally, a machine object (.mo) is
-created from portable object to sotore the translated messages.
-
-Inside the repository there are two ways to retrive translatable
-strings from files. The first one is through @command{xml2po} command
-and the second through @command{xgettext} command. The @command{xml2po}
-is used to retrive translatable strings from XML files (e.g., Scalable
-Vector Graphics, DocBook, etc.) and the @command{xgettext} command is
-used to retrive translatable strings from shell scripts files (e.g.,
-the files that make the @command{centos-art.sh} command-line
-interface).
-
-When translatable strings are retrived from XML files, using the
-@command{xml2po} command, there is no need to create the machine
-object as we do when translatable strings ar retrived from shell
-files, using the @command{xgettext} command. The @command{xml2po}
-produces a temporal machine object in order to create a translated XML
-file. Once the translated XML file has been created the machine object
-is no longer needed. On the other hand, the machine object produced by
-the @command{xgettext} command is required by the system in order for
-the show shell script localized messages.
-
-Another difference between @command{xml2po} and @command{xgettext} we
-need to be aware of is the directory structure used to store machine
-objects. In @command{xml2po}, the machine object is created in the
-current working directory as @file{.xml2po.mo} and can be safetly
-removed once the translated XML file has been created. In the case of
-@command{xgettext}, the machine object needs to be stored in the
-@file{$TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo} file in order
-for the system to interpret it and should not be removed since it is
-the file that contain the translation messages themselves.
-
-Automation of localization tasks is achived through the @code{locale}
-functionality of command-line interface.
-
-@subheading Usage
-
-@itemize
-@item @xref{Directories trunk Scripts Functions Locale}.
-@end itemize
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk}
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Manuals.texinfo b/Manuals/Texinfo/Directories/trunk/Manuals.texinfo
deleted file mode 100644
index 4ec2167..0000000
--- a/Manuals/Texinfo/Directories/trunk/Manuals.texinfo
+++ /dev/null
@@ -1,94 +0,0 @@
-@subheading Goals
-
-The @file{trunk/Manual} directory is the place where files related to
-documentation work line are stored in. The main goal of documentation
-work line is to describe what each directory inside the CentOS Artwork
-Repository is for, the conceptual ideas behind them and, if possible,
-how automation scripts make use of them.
-
-@subheading Description
-
-The repository documentation manual is made of the following files:
-
-@table @file
-
-@item repository.css
-
-This file controls the visual style for XHTML output files of
-repository documentation manual.
-
-@item repository-index.texinfo
-
-This file controls the index definition for source files of repository
-documentation manual.
-
-@item repository.info.bz2
-
-This file provides the Info output of repository documentation manual.
-
-@item repository-init.pl
-
-This file provides the initialization script of @command{texi2html},
-the program used by @command{centos-art.sh} script to produce the
-XHTML output of repository documentation manual.
-
-@item repository-menu.texinfo
-
-This file controls the menu definition of chapters for source files of
-repository documentation manual.
-
-@item repository-node.texinfo
-
-This file controls the node definition of chapters for source files of
-repository documentation manual.
-
-@item repository.pdf
-
-This file provides the PDF output of repository documentation manual.
-
-@item repository.sed
-
-This file provides post-transformations for XHTML output files. In
-this file is where XHTML definitions for admonitions are set in.
-
-@item repository.texinfo
-
-This is the source file of repository documentation manual where
-the manual structure initialization is set.
-manual.
-
-@item repository.txt.bz2
-
-This file provides the TXT output of repository documentation manual.
-
-@item repository.xhtml.bz2
-
-This file provides the XHTML output of repository documentation
-manual.
-
-@item repository.xml
-
-This file provides the XML output of repository documentation manual.
-
-@end table
-
-The repository documentation manual is made of the following
-directories:
-
-@itemize
-@item @xref{Directories trunk Manuals Directories}.
-@item @xref{Directories trunk Manuals Introduction}.
-@item @xref{Directories trunk Manuals Licenses}.
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item @xref{Directories trunk Scripts Functions Help}.
-@end itemize
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk}
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Manuals/Directories.texinfo b/Manuals/Texinfo/Directories/trunk/Manuals/Directories.texinfo
deleted file mode 100755
index 0a72b17..0000000
--- a/Manuals/Texinfo/Directories/trunk/Manuals/Directories.texinfo
+++ /dev/null
@@ -1,27 +0,0 @@
-@subheading Goals
-
-The @file{trunk/Manual/Directories} directory stores source
-documentation files related to repository directories. The directory
-structure in this location mirrors the directory structure being
-documented in the repository from top level directories (e.g.,
-@file{trunk}, @file{branches} and @file{tags}) to inner levels,
-including the @file{trunk/Manual} location itself where documentation
-source files are stored in.
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@itemize
-@item ...
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Manuals/Introduction.texinfo b/Manuals/Texinfo/Directories/trunk/Manuals/Introduction.texinfo
deleted file mode 100755
index d6bb628..0000000
--- a/Manuals/Texinfo/Directories/trunk/Manuals/Introduction.texinfo
+++ /dev/null
@@ -1,23 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@itemize
-@item ...
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Manuals/Licenses.texinfo b/Manuals/Texinfo/Directories/trunk/Manuals/Licenses.texinfo
deleted file mode 100755
index d6bb628..0000000
--- a/Manuals/Texinfo/Directories/trunk/Manuals/Licenses.texinfo
+++ /dev/null
@@ -1,23 +0,0 @@
-@subheading Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Description
-
-@itemize
-@item ...
-@end itemize
-
-@subheading Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subheading See also
-
-@itemize
-@item ...
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Scripts.texinfo b/Manuals/Texinfo/Directories/trunk/Scripts.texinfo
deleted file mode 100644
index bdd4fcb..0000000
--- a/Manuals/Texinfo/Directories/trunk/Scripts.texinfo
+++ /dev/null
@@ -1,167 +0,0 @@
-@subheading Goals
-
-This section provides the automation work line. The automation work
-line exists to standardize content production in CentOS Artwork
-Repository. There is no need to type several tasks, time after time,
-if they can be programmed into just one executable script.
-
-In this section you'll find how to organize and extend the
-@command{centos-art.sh} script, a bash scripts specially designed to
-automate most frequent tasks in the repository (e.g., image rendition,
-documenting directory structures, translating content, etc.). If you
-can't resist the idea of automating repeatable tasks, then take a look
-here.
-
-@subheading Description
-
-The best way to understand the @command{centos-art.sh} script is
-studying and improving its source code. However, as start point, you
-may prefer to read an introductory resume before diving into the
-source code details. In this section we identify the different parts
-the @command{centos-art.sh} script is made of and how these parts
-interact one another.
-
-@subsubheading Execution environments
-
-The @command{centos-art.sh} script is basically made of four execution
-environments which are named @emph{script}, @emph{global},
-@emph{specific} and @emph{action}. These execution environments are
-nested one into another and provide different definition levels for
-variables and functions. In this design, variables and functions
-defined in higher execution environments are available on lower
-execution environments, but variables and functions defined in lower
-execution environments are not available for higher execution
-enviroments.
-
-@verbatim
-+----------------------------------------------------------------------+
-| [centos@host]$ centos-art function path/to/dir --option='value' |
-+----------------------------------------------------------------------+
-| ~/bin/centos-art --> ~/artwork/trunk/Scripts/centos-art.sh |
-+---v--------------------------------------------------------------v---+
- | centos-art.sh |
- +---v------------------------------------------------------v---+
- . | cli $@ | .
- . +---v----------------------------------------------v---+ .
- . . | cli_getFunctions | . .
- . . +---v--------------------------------------v---+ . .
- . . . | function | . . .
- . . . +---v------------------------------v---+ . . .
- . . . . | function_getOptions | . . . .
- . . . . | function_doSomething | . . . .
- . . . . +------------------------------+ . . . .
- . . . . . . . .
- . . . . Execution environment (action) . . . .
- . . . ........................................ . . .
- . . . . . .
- . . . Execution environment (specific) . . .
- . . ................................................ . .
- . . . .
- . . Execution environment (global) . .
- . ........................................................ .
- . .
- . Execution environment (script) .
- ................................................................
-@end verbatim
-
-The script execution environment exists to provide script definitions
-that can't be set anywhere else inside the script. Example of such
-definitions include initialization of internationalization through
-@command{gettext} program, script personal information and
-initialization of global functionalities.
-
-The global execution environment exists to provide definitions that
-can't be set anywhere else inside the script. Example of such
-definitions include initialization of functionalities (e.g.,
-@code{cli_printMessage}, @code{cli_getCurrentLocale},
-@code{cli_checkFiles}, etc.) and variables (e.g., @var{FUNCNAM},
-@var{FUNCDIR}, @var{FUNCDIRNAM}, @var{ARGUMENTS}, etc.) that can be
-both used on specific and action execution environments, only.
-
-The specific execution environment exists to provide definitions that
-can't be set anywhere else inside the script. Example of such
-definitions include initialization of specifc functionalities (e.g.,
-@code{render}, @code{help}, @code{locale}, etc.) and specific
-variables (@var{ACTIONNAM}, @var{ACTIONVAL}, etc.) that can be used on
-action execution environment only.
-
-The action execution environment exists to perform the script actions
-themselves. It is here where we perform content rendition, content
-documentation, content localization and whatever action you plan for
-the @command{centos-art.sh} script to perform. For example, if you
-passed the @code{render} value as first argument to
-@command{centos-art.sh} command-line, the script performs the content
-rendition action through the @code{render} function which is defined
-in the @file{render.sh} file under
-@file{trunk/Scripts/Functions/Render} directory. Is there, inside
-@code{render} functionality were the action execution environment
-takes place exactly.
-
-@subsubheading Command-line interface
-
-When the @command{centos-art} command is executed in a bash terminal,
-the bash interpreter uses the @env{PATH} environment variable to find
-where such command is. In order to run the @command{centos-art}, it
-must exist either as a link to an executable file or an executable
-file by its own, in any of the paths provided by @env{PATH}
-environment variable. Otherwise, the bash interpreter will print an
-error message and prompt you back to type a valid command.
-
-By default, after installing The CentOS Distribution, there is no
-@command{centos-art} command available in the @env{PATH} environment
-variable for you to execute. The @command{centos-art} command is made
-available in your workstation as result of executing the
-@code{prepare} functionality of @command{centos-art.sh} script
-(@pxref{Directories trunk Scripts Functions Prepare}) which requires
-you had previously downloaded a working copy of CentOS Artwork
-Repository in your workstation.
-
-When the @command{centos-art} is executed, the first positional
-parameter passed is required and represents the name of the function
-you want to perform (e.g., @code{render} for content rendition,
-@code{locale} for content localization, etc.). Beyond the first
-positional parameter you can provide either option or non-option
-parameters in no specific order. There are also, option parameters
-with arguments and without arguments. Frequently, non-option paramters
-are used to specify the path location inside the repository where the
-function will be performed in (e.g., the directory structure do you
-want to produce content for) and option parameters to specify how such
-functionality is performed (e.g., do you want to go quietly? do you
-want to do filtering? etc.).
-
-@verbatim
- A B C D E
----------- ------- ----------- ---------------- -------
-centos-art funcnam path/to/dir --filter='regex' --quiet
----------- ------- ----------- ---------------- -------
-
- A = The centos-art.sh script command-line.
- B = The centos-art.sh function name.
- C = Non-option parameter.
- D = Option parameter (with argument).
- E = Option parameter (without argument).
-@end verbatim
-
-@subsubheading Parsing command-line options
-
-The action of parsing options is performed through @command{getopt}
-and results particularly interesting. @command{getopt} breaks up
-(parse) options in command lines and checks for legal options using
-the GNU @code{getopt} routines to do this. One important consideration
-on @command{centos-art.sh} script design is that positional parameters
-are retrived in the @code{cli} function but parsed on each specific
-function, individually. There isn't a big parsing definition to cover
-all specific functions, but one parsing definitions for each specific
-functions.
-
-@subheading Usage
-
-@itemize
-@item @xref{Directories trunk Scripts Functions}.
-@end itemize
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk}
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Scripts/Functions.texinfo b/Manuals/Texinfo/Directories/trunk/Scripts/Functions.texinfo
deleted file mode 100755
index 910e891..0000000
--- a/Manuals/Texinfo/Directories/trunk/Scripts/Functions.texinfo
+++ /dev/null
@@ -1,348 +0,0 @@
-@subheading Goals
-
-The @file{trunk/Scripts/Functions} directory exists to organize
-@file{centos-art.sh} specific functionalities.
-
-@subheading Description
-
-The specific functions of @file{centos-art.sh} script are designed
-with the ``Software Toolbox'' philosophy (@inforef{Toolbox
-introduction,,coreutils.info}) in mind: each program ``should do one
-thing well''. Inside @file{centos-art.sh} script, each specific
-functionality is considered a program that should do one thing well.
-Of course, if you find that they still don't do it, feel free to
-improve them in order for them to do so.
-
-The specific functions of @file{centos-art.sh} script are organized
-inside specific directories under @file{trunk/Scripts/Functions}
-location. Each specific function directory should be named as the
-function it represents, with the first letter in uppercase. For
-example, if the function name is @code{render}, the specific function
-directory for it would be @samp{trunk/Scripts/Functions/Render}.
-
-@subsubheading Creating the @code{greet} functionality
-
-To better understand how to design specific functions for
-@file{centos-art.sh} script, let's create the @code{greet}
-functionality which only goal is to print out different kind of
-greetings to your screen. The @code{greet} functionality will be set
-using the follwiing directory structure:
-
-@verbatim
-trunk/Scripts/Functions/Greet <-- The source location of greet function.
-|-- greet_getOptions.sh <-- Defines command-line interface.
-|-- greet_sayGoodbye.sh <-- Defines specific action.
-|-- greet_sayHello.sh <-- Defines specific action.
-`-- greet.sh <-- Defines function initialization.
-@end verbatim
-
-The @file{greet.sh} file contains the initialization script of
-@code{greet} functionality. It is the first file loaded from function
-source location by @command{centos-art.sh} script when it is executed
-using the @code{greet} functionality as first argument.
-
-Inside @file{centos-art.sh} script, as convenction, each function
-script has one top commentary, followed by one blank line, and then
-one function defintion below it only. The top commentary has the
-function description, one-line for copyright notice with your personal
-information, the license under which the function source code is
-released ---the @file{centos-art.sh} script is released as GPL, so do
-all its functions--- and the @code{$Id$} keyword of Subversion which
-is later expanded by @command{svn propset} command. In our example,
-the top comment of @code{greet.sh} function script would look like the
-following:
-
-@verbatim
-#!/bin/bash
-#
-# greet.sh -- This function outputs different kind of greetings to
-# your screen. Use this function to understand how centos-art.sh
-# script specific functionalities work.
-#
-# Copyright (C) YEAR YOURFULLNAME
-#
-# 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.
-# ----------------------------------------------------------------------
-# $Id$
-# ----------------------------------------------------------------------
-
-function greet {
-
- # Define command-line interface.
- greet_getOptions
-
- # Execute action name.
- if [[ $ACTIONNAM =~ "^${FUNCNAM}_[A-Za-z]+$" ]];then
- eval $ACTIONNAM
- else
- cli_printMessage "`gettext "A valid action is required."`" 'AsErrorLine'
- cli_printMessage "${FUNCDIRNAM}" 'AsToKnowMoreLine'
- fi
-
-}
-@end verbatim
-
-The first definition inside @code{greet} function is for variables
-that will be available along the whole execution environment of
-@code{greet} function. This time we didn't define any variable here
-so, we continued with definition of command-line interface, through
-@code{greet_getOptions} function.
-
-The command-line interface of @code{greet} functionality defines how
-to interpret arguments passed from @command{centos-art.sh} script
-command-line. Inside @command{centos-art.sh} script, the
-interpretation of arguments passed through its command-line takes
-place by mean of @command{getopt} command and is written as the
-following code example describes:
-
-@verbatim
-function greet_getOptions {
-
- # Define short options we want to support.
- local ARGSS=""
-
- # Define long options we want to support.
- local ARGSL="hello:,bye:,quiet"
-
- # Redefine ARGUMENTS variable using getopt output.
- cli_doParseArguments
-
- # Redefine positional parameters using ARGUMENTS variable.
- eval set -- "$ARGUMENTS"
-
- # Look for options passed through command-line.
- while true; do
-
- case "$1" in
-
- --hello )
- ACTIONNAM="${FUNCNAM}_sayHello"
- ACTIONVAL="$2"
- shift 2
- ;;
-
- --bye )
- ACTIONNAM="${FUNCNAM}_sayGoodbye"
- ACTIONVAL="$2"
- shift 2
- ;;
-
- --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
- # begining 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_doParseArgumentsReDef "$@"
-
-}
-@end verbatim
-
-The @code{greet_sayHello} and @code{greet_sayGoodbye} function definitions
-are the core of @code{greet} specific functionality. In such function
-definitions we set what our @code{greet} function really does: to
-output different kinds of greetings.
-
-@verbatim
-function greet_sayHello {
-
- cli_printMessage "`gettext "Hello"`, $ACTIONVAL"
-
-}
-@end verbatim
-
-The @code{greet_sayHello} function definition is stored in
-@file{greet_sayHello.sh} function script.
-
-@verbatim
-function greet_sayGoodbye {
-
- cli_printMessage "`gettext "Goodbye"`, $ACTIONVAL"
-
-}
-@end verbatim
-
-The @code{greet_sayGoodbye} function definition is stored in the
-@file{greet_sayGoodbye.sh} function script.
-
-@subsubheading Executing the @code{greet} functionality
-
-To execute the @code{greet} specific functionality we've just created,
-pass the function name (i.e., @code{greet}) as first argument to
-@file{centos-art.sh} script and any of the valid options after it.
-Some examples are illustrated below:
-
-@verbatim
-[centos@projects ~]$ centos-art greet --hello='World'
-Hello, World
-[centos@projects ~]$ centos-art greet --bye='World'
-Goodbye, World
-[centos@projects ~]$ centos-art greet --bye='World' --quiet
-[centos@projects ~]$
-@end verbatim
-
-The word @samp{World} in the examples above can be anything. Likewise,
-if you need to change the way either the hello or goodbye messages are
-printed out, you can modifie the functions @code{greet_sayHello} and
-@code{greet_sayGoodbye}, respectively.
-
-@subsubheading Documenting the @command{greet} functionality
-
-Now that @code{greet} functionality works as we expect, it is time to
-document it. To document functionalities inside
-@command{centos-art.sh} script we use the function directory path as
-argument to the @code{help} functionality (@pxref{Directories trunk
-Scripts Functions Help}) of @file{centos-art.sh} script, just as the
-following command illustrates:
-
-@verbatim
-centos-art help --edit trunk/Scripts/Functions/Greet
-@end verbatim
-
-The function documentation helps to understand how the function really
-works and how it should be used. Also, when @command{centos-art.sh}
-script ends because an error, the documentation entry related to the
-functionality being currently executed is used as vehicle to
-communicate the user what is the correct way of using the
-functionality.
-
-@subsubheading Localizing the @command{greet} functionality
-
-Now that @code{greet} functionality has been documented, it is time to
-localize its output messages. Localizing specific functionalities of
-@command{centos-art.sh} script takes place as part of
-@command{centos-art.sh} script localization itself which is performed
-by applying the path @file{trunk/Scripts} to the @code{locale}
-functionality of @command{centos-art.sh} script.
-
-As the @code{greet} functionality added new translatable strings to
-the @command{centos-art.sh} script, it is required to update the
-translation messages firstly, to add the new translatable strings from
-@code{greet} functionality to @command{centos-art.sh} script
-translation messages and then, edit the translation messages of
-@command{centos-art.sh} script to localize the new translatable
-strings that have been added. To achieve this, execute the following
-two commands:
-
-@verbatim
-centos-art locale --update trunk/Scripts
-@end verbatim
-
-@verbatim
-centos-art locale --edit trunk/Scripts
-@end verbatim
-
-@quotation
-@strong{Warning} To translate output messages in different languages,
-your system locale information ---as in @env{LANG} environment
-variable--- must be set to that locale you want to produce translated
-messages for. For example, if you want to produce translated messages
-for Spanish language, your system locale information must be set to
-@samp{es_ES.UTF-8}, or similar, before executing the @code{locale}
-functionality of @command{centos-art.sh} script.
-@end quotation
-
-Well, it seems that our example is rather complete by now.
-
-@subsubheading Extending the @code{greet} functionality
-
-In the @code{greet} functionality we've described so far, we only use
-@code{cli_printMessage} function in action specific function
-definitions in order to print messages, but more interesting things
-can be achieved inside action specific function definitions. For
-example, if you pass a directory path as argument, you could use it to
-retrive a list of files from therein and process them. If the list of
-files turns too long or you just want to control which files to
-process, so you could add another argument in the form
-@option{--filter='regex'} and reduce the list of files to process
-using a regular expression pattern.
-
-In case you consider to extend the @code{greet} functionality to do
-something different but print out grettings, consider changing the
-function name from @code{greet} to something more appropriate, as
-well. The name change must be coherent with the actions the new
-function is designed to perform.
-
-If you doubt what name is better for your functionality, write to
-@email{centos-devel@@centos.org} mailing list, explain what your
-functionality intends to do and request suggestion about what name
-would be more appropriate for it. That would be also very convenient
-for you, in order to evaluate the purposes of your function and what
-the community thinks about it. It is a way for you to gather ideas
-that help you to write using the community feeling as base.
-
-If your function passes the community evaluation, that is a good sign
-for you to start/keep writing it. However, if it doesn't, it is time
-for you to rethink what you are doing and ask again until it passes
-the community evaluation. You can considered you've passed the
-community evaluation when after proposing your idea, you get a
-considerable amount of possitve responses for what you are doing,
-specially if those responses come from community leaders.
-
-It is very hard to do something useful for a community of people
-without any point of contact with that community you are trying to do
-things for. How could you know you are doing something that is needed
-if you don't know what the needs are? So, explore the community needs
-first, define them, work them out and repeat the process time after
-time, even when you might think the need has been already satisfied.
-At that point, surely, you'll find smaller needs that need to be
-satisfied, as well.
-
-@subsubheading Conclusions
-
-The @code{greet} functionality described in this section may serve as
-introduction for you to understand how specific functionalities are
-created inside @file{centos-art.sh} script. With some of luck this
-introduction will also serve you as motivation to create your own
-specific functionalities for @file{centos-art.sh} script.
-
-By the way, the @code{greet} functionality doesn't exist inside
-@file{centos-art.sh} script yet. Would you like to create it?
-
-@subheading Usage
-
-The following specific functions of @file{centos-art.sh} script, are
-available for you to use:
-
-@itemize
-@item @xref{Directories trunk Scripts Functions Help}.
-@item @xref{Directories trunk Scripts Functions Locale}.
-@item @xref{Directories trunk Scripts Functions Prepare}.
-@item @xref{Directories trunk Scripts Functions Render}.
-@item @xref{Directories trunk Scripts Functions Tuneup}.
-@end itemize
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk Scripts}
-@item @ref{Directories trunk}
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Help.texinfo b/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Help.texinfo
deleted file mode 100644
index 4b39f76..0000000
--- a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Help.texinfo
+++ /dev/null
@@ -1,179 +0,0 @@
-@subheading Name
-
-The @code{help} functionlity is part of @command{centos-art.sh} script
-and standardizes documentation tasks inside the working copy of CentOS
-Artwork Repository.
-
-@subheading Synopsis
-
-@command{centos-art help [OPTIONS] path/to/dir @dots{}}
-
-The @file{path/to/dir} parameter specifies what directory structure
-inside the working copy of CentOS Artwork Repository you want to
-process.
-
-The @code{help} functionality of @command{centos-art.sh} script
-accepts the following options:
-
-@table @option
-@item --quiet
-
-Supress all output messages except error messages. When this option
-is passed, all confirmation requests are supressed as well and a
-possitive answer is assumed for them, just as if the
-@option{--answer-yes} option had been provided.
-
-@item --answer-yes
-
-Assume `yes' to all confirmation requests.
-
-@item --dont-commit-changes
-
-Supress all commit and update actions realized over files, before and
-after the action itself had took place over files in the working copy.
-
-@item --backend="STRING"
-
-Specifies the documentation system used as backend to manage the
-repository documentation manual. When this option is not provided, the
-@samp{texinfo} documentation system is used as default backend.
-
-@item --search="STRING"
-
-Go to node pointed by index entry @samp{STRING}.
-
-@item --edit "path/to/dir"
-
-Edit documentation entry related to path specified by
-@file{path/to/dir}.
-
-The @file{path/to/dir} must point to any directory inside the
-repository. When more than one @file{path/to/dir} are passed as
-non-option arguments to the @command{centos-art.sh} script
-command-line, they are queued for further edition. The edition itself
-takes place through your default text editor (e.g., the one you
-specified in the @env{EDITOR} environment variable) and the text
-editor opens one file at time (i.e., the queue of files to edit is not
-loaded in the text editor.).
-
-@item --read "path/to/dir"
-
-Read documentation entry specified by @file{file/to/dir} path. This
-option is used internally by @command{centos-art.sh} script to print
-out the reference you can follow to know more about an error message.
-
-@item --update
-
-Update output files rexporting them from the specified backend source
-files.
-
-@item --copy "path/to/srcdir" "path/to/dstdir"
-
-Duplicate documentation entries inside the working copy of CentOS
-Artwork Repository.
-
-When documentation entries are copied, only two non-option arguments
-can be passed to @command{centos-art.sh} script. In this case, the
-first non-option argument is considered the source location and the
-second one the target location. Both source location and target
-location must point to a directory under the working copy or files
-under @file{trunk/Manuals/Texinfo/Directories} directory structure.
-
-@item --delete "path/to/dir"
-
-Delete documentation entries inside the working copy of CentOS
-Artwork Repository.
-
-@item --rename "path/to/srcdir" "path/to/dstdir"
-
-Rename documentation entries inside the working copy of CentOS Artwork
-Repository.
-
-When documentation entries are renamed, only two non-option arguments
-can be passed to @command{centos-art.sh} script. In this case, the
-first non-option argument is considered the source location and the
-second one the target location. Both source location and target
-location must point to a directory under the working copy or files
-under @file{trunk/Manuals/Texinfo/Directories} directory structure.
-
-@end table
-
-When documentation entries are removed (e.g., through
-@option{--delete} or @option{--rename} options), the
-@command{centos-art.sh} script takes care of updating nodes, menus and
-cross references related to documentation entries in order to keep the
-manual structure in a correct state.
-
-@subheading Description
-
-Inside the CentOS Artwork Repository, The CentOS Project corporate
-identity is organized through directories. Each directory inside the
-repository responds to one or more conceptual ideas. Conceptual ideas
-are implemented through files.
-
-The @code{help} functionality of @command{centos-art.sh} script uses
-the repository directory layout as reference to document the
-conceptual ideas it is based on. Each directory inside the repository
-can be documented, in order to provide the explanation of what it is
-for and how automation scripts use it.
-
-@quotation
-@strong{Caution} When the repository directory layout changes, the
-documentation layout related must be changed as well in order for both
-locations to be consistent in their paths. Otherwise, you may end up
-having documentation entries that point to unexistent directories in
-the repository.
-@end quotation
-
-Files inside the repository are not documented. The only exception to
-this rule are files under @file{trunk/Manuals} directory, the place
-where documentation source files are stored in. Inside this location
-you can refer files for direct actions using the @code{help}
-functionality of @command{centos-art.sh} script. File actions, in this
-location, are also used to manage specific parts of the manual which
-have no association outside @file{trunk/Manuals} directory (e.g.,
-Preface, Introduction, etc.).
-
-@subsubheading Documentation backends
-
-Documentation backends are organized in @xref{Directories trunk
-Scripts Functions Help Backends}.
-
-@subheading Examples
-
-@table @command
-@item centos-art help --edit trunk/Identity
-
-This command edits the documentation entry related to
-@file{trunk/Identity} directory.
-
-@item centos-art help --read trunk/Identity
-
-This command reads the doumentation entry related to
-@file{trunk/Identity} directory in info format.
-
-@end table
-
-@subheading Author
-
-Written by Alain Reguera Delgado.
-
-@subheading Reporting bugs
-
-Report bugs to @email{centos-artwork@@centos.org} mailing list.
-
-@subheading Copyright
-
-Copyright @copyright{} 2009, 2010, 2011 The CentOS Project.
-
-This is free software. You may redistribute copies of it under the
-terms of the GNU General Public License (@pxref{GNU General Public
-License}). There is NO WARRANTY, to the extent permitted by law.
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk Scripts Functions}
-@item @ref{Directories trunk Scripts}
-@item @ref{Directories trunk}
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Help/Backends.texinfo b/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Help/Backends.texinfo
deleted file mode 100755
index be8b256..0000000
--- a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Help/Backends.texinfo
+++ /dev/null
@@ -1,34 +0,0 @@
-@subheading @code{texinfo}
-
-When @code{texinfo} backend is used (default behaviour), the manual
-structure (@pxref{Directories trunk Manuals}) is supported by GNU
-Texinfo, a documentation system that can produce both online
-information and a printed manual from a single source. The @code{help}
-functionality is an interface you can use to control the source files
-in the manual structure.
-
-The manual output is produced from Texinfo files and stored in
-@file{trunk/Manuals/Texinfo} on different formats including Info, PDF,
-XHTML, XML and TXT.
-
-When the @samp{texinfo} backend is used, you'll always edit
-documentation entries in English language, no matter what your
-prefered language be. This way, the output produced from them will
-always be in English language. To achieve the manual localization in
-your prefered language you need to apply the @code{locale}
-functionality of @command{centos-art.sh} script (@pxref{Directories
-trunk Scripts Functions Locale}) to any of the XML-based English
-outputs supported by @command{centos-art.sh} script (e.g., XHTML) to
-produce portable objects for your prefered language and the
-@code{render} functionality of @command{centos-art.sh} script
-(@pxref{Directories trunk Scripts Functions Render}) to produce the
-translated version of the output XHTML files taken in first place. The
-translated version is produced in the same format of the file taken as
-reference to build the portable objects. XHTML format in this case.
-
-@subheading @code{linuxdoc}
-Not supported yet.
-
-@subheading @code{docbook}
-
-Not supported yet.
diff --git a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Locale.texinfo b/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Locale.texinfo
deleted file mode 100644
index 0eb5ff4..0000000
--- a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Locale.texinfo
+++ /dev/null
@@ -1,255 +0,0 @@
-@subheading Name
-
-The @code{locale} functionlity is part of @command{centos-art.sh}
-script and standardizes localization tasks inside the working copy of
-CentOS Artwork Repository.
-
-@subheading Synopsis
-
-@command{centos-art locale [OPTIONS] path/to/dir}
-
-The @file{path/to/dir} parameter specifies what directory structure
-inside the working copy of CentOS Artwork Repository you want to
-create translation messages for.
-
-The @code{locale} functionality of @command{centos-art.sh} script
-accepts the following options:
-
-@table @option
-@item --quiet
-
-Supress all output messages except error messages. When this option
-is passed, all confirmation requests are supressed as well and a
-possitive answer is assumed for them, just as if the
-@option{--answer-yes} option had been provided.
-
-@item --answer-yes
-
-Assume `yes' to all confirmation requests.
-
-@item --filter="REGEX"
-
-Reduce the list of files to process using @samp{REGEX} as pattern.
-You can use this option in combination with @file{path/to/dir} in
-order to control the amount of files you want to produce as
-base-rendition. The deeper you go into the directory structure the
-more specific you'll be about the component you want to produce. When
-you cannot go deeper into the directory structure, you can use
-@option{--filter} option to reduce the list of files.
-
-@item --dont-commit-changes
-
-Supress all commit and update actions realized over files, before and
-after the action itself had took place over files in the working copy.
-
-@item --update
-
-This option extracts translatable strings from both XML-based files
-(using @command{xml2po}) and shell scripts (using @command{xgettext})
-under @file{path/to/dir}. Translatable strings are initially stored in
-portable objects templates (.pot) which are later merged into portable
-objects (.po) in order to be converted as machine objects (.mo).
-
-Use this option each time you change translatable stirngs inside
-design models and script files.
-
-@item --edit
-
-This option edits the portable object related to @file{path/to/dir}
-location.
-
-Use this option after updating portable objects (through
-@option{--update} option) in order to change the language-specific
-information of translatable strings.
-
-@item --dont-create-mo
-
-This option supresses the creation of machine objects.
-
-@end table
-
-@subheading Description
-
-The CentOS Artwork Repository exists to cover the visual needs of The
-CentOS Project Corporate Identity. The CentOS Project is an
-internationl project and sometimes requires contents in different
-languages. So, in that sake, the CentOS Artwork Repository is designed
-to produce content in as many locales as supported by The CentOS
-Distribution, the platform that supports the whole CentOS Artwork
-Repository, both in workstations and server.
-
-@quotation
-@strong{Tip} To know what locales are supported by The CentOS
-Distribution you are currently using, run the following command:
-
-@verbatim
-locale -a | less
-@end verbatim
-@end quotation
-
-The localization process is very tied to the input files we want to
-provide localized messages for. Inside the CentOS Artwork Repository,
-it is possible to localize XML files (e.g., SVG, XHTML, Docbook) and
-programs written in most popular programming languages (e.g., C, C++,
-C#, Shell Scripts, Python, Java, GNU awk, PHP, etc.).
-
-@subsubheading Design models localization
-
-Design models are used as input to produce most images and some other
-contents as well. Design models are always XML-based files (e.g., SVG,
-XHTML, Docbook), so the @code{locale} functionality uses the
-@command{xml2po} program to create protable objects from them under
-@file{trunk/Locales/Models} directory. Portable objects contain the
-relation between message id and message translation, as translator,
-need to take care of.
-
-Thanks to @command{xml2po}, it is possible for the @code{locale}
-functionality to separate designing tasks from the translating tasks.
-It is possible for graphic designers to concentrate their efforts on
-designing models in English language while translators take care of
-their localization using the @option{--update} and @option{--edit}
-options as much as it be needed.
-
-Once design models have been localized, rendering them in different
-language is a matter using the @code{render} functionality of
-@command{centos-art.sh} script. @xref{Directories trunk Scripts
-Functions Render}, for more information about it.
-
-@subsubheading Shell script localization
-
-The @code{locale} functionality is used to localize the
-@command{centos-art.sh} script itself. The @command{centos-art.sh}
-script is a shell script written in Bash, so the @code{locale}
-functionality uses the @command{gettext} tools to retrive translatable
-strings, create portable objects and machine objects.
-
-Thanks to @command{gettext}, it is possible for the @code{locale}
-functionality to separate programming tasks from the translating
-tasks. It is possible for programmer to concentrate their efforts in
-programming output messages in English language while translators take
-care of their localization using the @option{--update} and
-@option{--edit} options as much as it be needed.
-
-Once @command{centos-art.sh} script has been localized, the translated
-messages should be immediatly visible to you, the next time you
-execute the @command{centos-art.sh} script
-
-@quotation
-@strong{Note}
-In order to localize translatable strings from English language to
-another language you need to be sure the @env{LANG} environment
-variable has been already set to the locale code you want to localize
-message for or see them printed out before running the
-@command{centos-art.sh} script. Localizing English language to itself
-is not supported.
-@end quotation
-
-@subheading Examples
-
-@table @command
-@item centos-art locale --update trunk/Identity/Models/Default/Distro/5/Anaconda
-
-This command updates portable objects related to Anaconda default
-design models of The CentOS Distribution major release 5. The update
-action consists on adding new translatable strings or removing old
-translatable strings from portable objects in order to keep both the
-portable object and the design model consistent.
-
-This command is executed by translators once the graphic designers
-have committed updates to Anaconda default design models (e.g., slide
-text changes).
-
-@item centos-art locale --edit trunk/Identity/Models/Default/Distro/5/Anaconda
-
-This command let translators to edit portable objects related to
-Anaconda default design models of The CentOS Distribution major
-release 5. The edit action is where the translator localize
-translatable strings in English language to another language.
-
-When portable objects for XML-base files are produced, there is no
-need to retain the machine object format, so we the
-@option{--dont-create-mo} is automatically assumed.
-
-@item centos-art locale --update trunk/Scripts
-
-This command updates portable objects related to
-@command{centos-art.sh} script. The update action consists on adding
-new translatable strings or removing old translatable strings from
-portable objects in order to keep both the portable object and the
-@command{centos-art.sh} script to be consistent one another.
-
-This command is executed by translators once the programmers have
-committed updates @command{centos-art.sh} script.
-
-@item centos-art locale --edit trunk/Scripts
-
-This command edits portable objects related to @command{centos-art.sh}
-script in your prefered language.
-
-@item centos-art locale --update trunk/Manual/repository.xhtml
-
-This command updates portable objects for the XHTML output of the
-repository documentation manual. The portable objects are created in
-your prefered language and can be used to produced localized versions
-of the manual in XHTML format.
-
-The update action consists on adding new translatable strings to or
-removing old translatable strings from the portable objects in order
-to keep both the portable object and the manual XHTML output
-consistent one another.
-
-People execute this command after committing changes to the repository
-documentation manual.
-
-@item centos-art locale --edit trunk/Manual/repository.xhtml
-
-This command takes all the repository documentation manual XHTML
-output files, which have not been translated yet inside the
-@file{trunk/Manual/repository.xhtml} directory, as input to produce
-portable objects from them so as for you to localize translatable
-strings to your prefered language (e.g., as specified by the
-@env{LANG} environment variable).
-
-Once the portable objects have been created they are used to produce
-the translated version of the manual in XHTML format under the
-@file{trunk/Manual/repository.xml/LANG} directory, where @samp{LANG}
-refers your prefered language. The translated version of the XHTML
-files is produced using the @code{render} functionality of
-@command{centos-art.sh} script (@pxref{Directories trunk Scripts
-Functions Render}).
-
-When your prefered language is other but English, the
-@command{centos-art.sh} script takes care of updating both the
-portable objects and the translated version of files after you've
-edited a manual documentation entry, using the @code{help}
-functionality of @command{centos-art.sh} script (@pxref{Directories
-trunk Scripts Functions Help}). In other situations, you need to do
-these actions by yourself.
-
-@end table
-
-@subheading Author
-
-Written by Alain Reguera Delgado.
-
-@subheading Reporting bugs
-
-Report bugs to @email{centos-artwork@@centos.org} mailing list.
-
-@subheading Copyright
-
-Copyright @copyright{} 2009, 2010, 2011 The CentOS Project.
-
-This is free software. You may redistribute copies of it under the
-terms of the GNU General Public License (@pxref{GNU General Public
-License}). There is NO WARRANTY, to the extent permitted by law.
-
-@subheading See also
-
-@itemize
-@item The GNU @command{gettext} tools documentation (@command{info gettext})
-@item The @command{xml2po} command documentation (@command{man xml2po})
-@item @ref{Directories trunk Scripts Functions}
-@item @ref{Directories trunk Scripts}
-@item @ref{Directories trunk}
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Prepare.texinfo b/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Prepare.texinfo
deleted file mode 100644
index ea9f743..0000000
--- a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Prepare.texinfo
+++ /dev/null
@@ -1,305 +0,0 @@
-@subheading Name
-
-The @code{prepare} functionality is part of the
-@command{centos-art.sh} script and standardizes configuration of
-preliminar steps you need to follow in order to get your workstation
-ready for using a working copy of CentOS Artwork Repository.
-
-@subheading Synopsis
-
-@command{centos-art prepare [OPTIONS]}
-
-There is no need to specify @file{path/to/dir} information in this
-functionality. Most actions are performed through options.
-
-The @code{prepare} functionality of centos-art.sh script accepts the
-following options:
-
-@table @option
-
-@item --quiet
-
-Supress all output messages except error messages. When this option
-is passed, all confirmation requests are supressed as well and a
-possitive answer is assumed for them, just as if the
-@option{--answer-yes} option had been provided.
-
-@item --answer-yes
-
-Assume @samp{yes} to all confirmation requests.
-
-@item --packages
-
-Install/update software packages required by the working copy of
-CentOS Artwork Repository.
-
-The process of software installation takes place through @command{sudo
-yum} and the repository configuration currently set in your
-workstation.
-
-Most of the software packages required by the working copy of CentOS
-Artwork Repository are available on The CentOS Distribution and can be
-installed using The CentOS Distribution installation media. The only
-exception is Inkscape, the program used to manipulate
-@acronym{SVG,Scalable Vector Graphics} files in the working copy.
-
-The @file{inkscape} package isn't inside The CentOS Distribution or
-any of The CentOS Project repositories neither, so you need to install
-it from a third party repository like @samp{RPMForge} or @samp{EPEL}.
-See page
-@url{http://wiki.centos.org/AdditionalResources/Repositories/,The
-CentOS Repositories}, to know how to configure third party
-repositories in The CentOS Distribution.
-
-@item --link
-
-This option uses symbolic links to install/update the connection
-between components inside the working copy and components outside the
-working copy. Among the components that need to be connected figure
-out the command-line internface of @command{centos-art.sh} script;
-fonts, brushes, palettes and patterns used by programs like GIMP and
-Inkscape; and configuration files of text editors.
-
-The main purpose of such connection is to adapt the working copy to
-the CentOS Distribution filesystem layout (e.g., @file{~/bin}
-directory is for storing personal programs, @file{~/gimp-2.2/brushes}
-is for storing GIMP brushes for personal use, etc.) and, at the same
-time, to provide a way of sharing changes made to connected components
-to other workstations (e.g., if I update a GIMP brush in my
-workstation, you'll receive the change the next you update your
-working copy and then will be immediatly available for you to use in
-GIMP).
-
-@item --environment
-
-Print the name and value of some of the environment variables used by
-@command{centos-art.sh} scripts.
-
-@end table
-
-@subheading Description
-
-The @code{prepare} functionality of @command{centos-art.sh} script is
-part of the CentOS Artwork Repository. So, in order to execute the
-@code{prepare} functionality of @command{centos-art.sh} script you
-need to have access to a working copy of CentOS Artwork Repository,
-first. Working copies of CentOS Artwork Repository are downloaded
-from the source repository and made available to you by mean of
-workstations. A workstation is a computer that you install and
-configure (prepare) to do something. In this case, you pick up a
-computer and prepare it for working on the CentOS Artwork Repository.
-
-@subsubheading Installing the workstation
-
-Installing the workstation is the first step you need to do. In this
-step you make your computer functional through an operating system. In
-this case, The Community Enterprise Operating System; which is also
-know as The CentOS Distribution or just CentOS, for short.
-
-To install The CentOS Distribution you need to have the installation
-media somehow (e.g., CDs, DVDs, Pendrives, etc.). There are several
-different ways to perform the installation process of CentOS
-distribution, but generally, you put the installation media in your
-media reader, boot the computer from it, and follow the installer
-intructions. That simple.
-
-If you don't have the installation media of CentOS distribution, you
-need to download the ISO files related to the media you plan to use
-(e.g., CD or DVD) and then create the installation media by yourself.
-The CentOS Distribution ISO files can be downloaded from
-@url{http://mirrors.centos.org/} and, if you chosen CD or DVD as your
-prefered installation medium, you can burn the ISO files using the
-@command{K3B} application so as to create the installation media
-you'll use. Of course, in order to download the ISO files and create
-the installation media, you need to have an already installed CentOS
-workstation where you can realized all the work.
-
-@subsubheading Configuring the workstation
-
-Once you've installed the workstation and it is up and running, login
-as @samp{root} user, create a username (e.g., @samp{centos}) and set a
-password for it. This is the username you must use for everyday work
-inside your working copy of the CentOS Artwork Repository.
-
-@quotation
-@strong{Caution} Do not use the @samp{root} username for your everyday
-work inside the working copy of CentOS Artwork Repository. It is
-dangerous and might provoke unreversable damages on your workstation.
-@end quotation
-
-Once you've created the username for your everyday work, there are
-some environment variables that you can customize to fit your personal
-needs (e.g., default text editor, default locale information, default
-time zone representation, etc.). To customize these variables you
-need to edit your profile file (i.e., @file{~/.bash_profile}) and set
-the redefinition there. Notice that you may need to logout and then
-do login again in order for the new variable values to take effect.
-
-@table @strong
-@item Default text editor:
-
-The default text editor information is contrlled by the @env{EDITOR}
-environment variable. The @file{centos-art.sh} script uses the default
-text editor to edit subversion pre-commit messages, translation files,
-documentation files, script files, and similar text-based files.
-
-If @env{EDITOR} environment variable is not set, @file{centos-art.sh}
-script uses @file{/usr/bin/vim} as default text editor. Otherwise, the
-following values are recognized by @file{centos-art.sh} script:
-
-@itemize
-@item @file{/usr/bin/vim}
-@item @file{/usr/bin/emacs}
-@item @file{/usr/bin/nano}
-@end itemize
-
-If no one of these values is set in the @env{EDITOR} environment
-variable, the @file{centos-art.sh} script uses @file{/usr/bin/vim}
-text editor, the one installed by default in The CentOS Distribution.
-
-@item Default locale information:
-
-The default locale information is controlled by the @env{LANG}
-environment variable. This variable is initially set in the
-configuration process of CentOS distribution installer, specifically
-in the @samp{Language} step; or once installed using the
-@command{system-config-language} tool.
-
-The @command{centos-art.sh} script uses the @env{LANG} environment
-variable to determine what language to use for printing output
-messages. Another use of @env{LANG} variable inside
-@command{centos-art.sh} script is to determine what translation file
-to update or edit when input files are localized.
-
-@item Default time zone representation:
-
-The time zone representation is a time correction applied to the
-system time (stored in the BIOS clock) based on your country location.
-This correction is specially useful to distributed computers around
-the world that work together and need to be syncronized in time to
-know when things happened.
-
-The CentOS Artwork Repository is made of one server and several
-workstations spread around the world. In order for all these
-workstations to know when changes in the server took place, it is
-required that they all set their system clocks to use the same time
-information (i.e., @acronym{UTC,Coordinated Universal Time}) and set
-the time correction for their specific countries in the operating
-system. Otherwise, it would be difficult to know when something
-exactly happened.
-
-Generally, setting the time information is a straight-forward task and
-configuration tools provided by The CentOS Distribution do cover time
-correction for most of the countries around the world. However, if
-you need a time precision not provided by any of the date and time
-configuration tools provided by The CentOS Distribution then, you need
-to use the @env{TZ} environment variable to correct the time
-information by yourself. The format of @env{TZ} environment variable
-is described in @file{tzset(3)} manual page.
-@end table
-
-@subsubheading Downloading the working copy
-
-Once you've configured the workstation, it is time to download the
-working copy of CentOS Artwork Repository.
-
-To download the working copy of CentOS Artwork Repository you need to
-login as your everyday work username (e.g., @samp{centos}) and use the
-Subversion client to bring all the files you need to work with down
-from the source location of CentOS Artwork Repository
-(@url{https://projects.centos.org/svn/artwork/}) to your workstation,
-just as the following command describes:
-
-@verbatim
-svn co https://projects.centos.org/svn/artwork ~/
-@end verbatim
-
-This command will create the working copy of CentOS Artwork Repository
-in your workstation, specifically in the @file{/home/centos/artwork}
-directory. Note that you only need to execute this command once.
-After that, to keep your working copy up to date, you use the
-Subversion @command{update} command instead.
-
-@quotation
-@strong{Tip} In the condition that you don't have Subversion client
-installed in the workstation, then you can install it using the
-command:
-
-@verbatim
-sudo yum install subversion
-@end verbatim
-@end quotation
-
-@subsubheading Configuring the working copy
-
-Once you have a working copy of CentOS Artwork Repository in your
-workstation, you can go and run the @code{prepare} functionality of
-@command{centos-art.sh} script to realize the remaining configuration
-stuff.
-
-Assuming this is the very first time you run the
-@command{centos-art.sh} script, you'll find that there is no
-@command{centos-art} command-line interface for it in your
-workstation. This is correct. In order to have the
-@command{centos-art} command-line in your workstation, you need to run
-the @command{centos-art.sh} script using its absolute path:
-
-@verbatim
-~/artwork/trunk/Scripts/centos-art.sh prepare [OPTIONS]
-@end verbatim
-
-Assuming you've already run the @code{prepare} functionality
-before, there is no need for you to use the absolute path again.
-Instead, you can use the @command{centos-art} command-line interface
-directly, as the following example describes:
-
-@verbatim
-centos-art.sh prepare [OPTIONS]
-@end verbatim
-
-Notice that you can execute the @code{prepare} functionality more than
-once. This is specially useful to keep the link information
-syncronized. For example, considering you've added new brushes to or
-removed old brushes from your working copy of CentOS Artwork
-Repository, the link information related to those files need to be
-updated in the @file{~/.gimp-2.2/brushes} 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 components.
-
-@subheading Examples
-
-@table @command
-@item centos-art prepare --packages --link
-Preapare both links and packages required to use the working copy of
-CentOS Artwork Repository in the workstation. If required packages are
-already installed this command looks for updates instead.
-
-@item centos-art prepare --link --quiet
-Update connection between the workstation and the working copy of
-CentOS Artwork Repository, using no output.
-@end table
-
-@subheading Author
-
-Written by Alain Reguera Delgado.
-
-@subheading Reporting bugs
-
-Report bugs to @email{centos-artwork@@centos.org} mailing list.
-
-@subheading Copyright
-
-Copyright @copyright{} 2009, 2010, 2011 The CentOS Project.
-
-This is free software. You may redistribute copies of it under the
-terms of the GNU General Public License (@pxref{GNU General Public
-License}). There is NO WARRANTY, to the extent permitted by law.
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk Scripts Functions}
-@item @ref{Directories trunk Scripts}
-@item @ref{Directories trunk}
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Render.texinfo b/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Render.texinfo
deleted file mode 100644
index 36b5c2d..0000000
--- a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Render.texinfo
+++ /dev/null
@@ -1,373 +0,0 @@
-@subheading Name
-
-The @code{render} functionlity is part of @command{centos-art.sh}
-script and standardizes rendition tasks inside the working copy of
-CentOS Artwork Repository.
-
-@subheading Synopsis
-
-@command{centos-art render [OPTIONS] path/to/dir}
-
-The @file{path/to/dir} parameter specifies what directory structure
-inside the working copy of CentOS Artwork Repository you want to
-produce.
-
-The @code{render} functionality of @command{centos-art.sh} script
-accepts the following options:
-
-@table @option
-@item --quiet
-
-Supress all output messages except error messages. When this option
-is passed, all confirmation requests are supressed as well and a
-possitive answer is assumed for them, just as if the
-@option{--answer-yes} option had been provided.
-
-@item --answer-yes
-
-Assume `yes' to all confirmation requests.
-
-@item --filter="REGEX"
-
-Reduce the list of files to process using @samp{REGEX} as pattern.
-You can use this option in combination with @file{path/to/dir} in
-order to control the amount of files you want to produce as
-base-rendition. The deeper you go into the directory structure the
-more specific you'll be about the component you want to produce. When
-you cannot go deeper into the directory structure, you can use
-@option{--filter} option to reduce the list of files.
-
-@item --dont-commit-changes
-
-Supress all commit and update actions realized over files, before and
-after the action itself had took place over files in the working copy.
-
-@item --releasever="STRING"
-
-This option expands release-specific translation makers to
-@samp{STRING}. Use this option when no releasae-specific information
-can be retrived from the path of the directory structure you are
-currently rendering.
-
-@item --basearch="STRING"
-
-This option expands architecture-specific translation makers to
-@samp{STRING}. Use this option when no architecture-specific
-information can be retrived from the path of the directory structure
-you are currently rendering.
-
-@item --theme-model="STRING"
-
-Specify the name of the theme model you want to use to produce theme
-artistic motifs. By default, if this option is not passed, the
-@samp{Default} theme model is used as reference to produce theme
-motifs.
-
-@item --post-rendition="STRING"
-
-This option let you apply a command as post-rendition action. In this
-case, the @samp{STRING} represents the command string you want to
-execute in order to perform in-place modifications to base-rendition
-output.
-
-@item --last-rendition="STRING"
-
-This option let you apply a command as last-rendition action. In this
-case, the @samp{STRING} 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.
-
-@end table
-
-@subheading Description
-
-Inside the working copy of CentOS Artwork Repository, rendition tasks
-take place inside renderable directories. Inside the @code{render}
-functionality of @command{centos-art.sh} script, you can control
-rendition tasks through different flows of rendition named
-base-rendition, post-rendition, last-rendition and directory-specific
-rendition.
-
-@subsubheading Renderable directories
-
-In order for a directory structure to be considered renderable, it
-should have one directory structure for input files and one directory
-structure for output files. Optionally, a third directory structure
-might be available for storing translation files.
-
-Renderable directories are very tied to the way content is produced
-inside the working copy of CentOS Artwork Repository. Presently,
-content is produced through the following organizations:
-
-@table @strong
-@item Direct rendition
-
-In direct rendition, there is one directory structure for input files
-(@file{trunk/Identity/Models}) and one directory structure for output
-files (e.g., @file{trunk/Identity/Images}). Optionally, a third
-directory structure is available to store the input related
-translation files (e.g., @file{trunk/Locales/Identity/Models}).
-
-In direct rendition, when the @code{render} functionality of
-@command{centos-art.sh} script is executed, it uses the input
-directory structure to build a list of files to process, which is used
-as reference to determine the location of the translation file and the
-location of the output file, as well.
-
-@item Theme-specific rendition
-
-In theme-specific rendition, there is one directory structure to store
-input files (@file{trunk/Identity/Themes/Models}), one directory
-structure to store translation files
-(@file{trunk/Locales/Identity/Themes/Models/}), one directory
-structure to store artistic motifs
-(@file{trunk/Identity/Images/Themes}) and one directory structure to
-store output files (@file{trunk/Identity/Images/Themes}).
-
-In theme-specific rendition, when the @code{render} functionality of
-@command{centos-art.sh} script is executed, it uses the input
-directory structure to build a list of files to process, which is used
-as reference to determine the location of the translation file and the
-location of the output file, as well.
-
-In contrast with direct rendition, when we use theme-specific
-rendition, it is possible to combine both design models and artistic
-motifs to produce output in an arbitrary way. This configuration is
-specially interesting because it is possible to create different
-artistic motifs and one unique design model in order to produce one
-unique theme structure with different visual styles. Or the opposite,
-to create different theme structures and apply one unique visual style
-to produce one unique visual styles on different theme structure. Or
-even get a bit farther and experiment with arbitrary combinations
-among them all.
-
-@end table
-
-In both direct and theme-specific rendition, if the location where the
-output file should be stored doesn't exist, the @code{render}
-functionality of @command{centos-art.sh} script will create it for
-you.
-
-In both direct and theme-specific rendition, if the input related
-translation file doesn't exist, the @code{render} functionality of
-@command{centos-art.sh} script will produce the output in the same
-language of its input file.
-
-@subsubheading The base-rendition flow
-
-The base-rendition flow is the first rendition flow of all rendition
-flows available and takes place immediatly after executing the
-@code{render} functionality of @command{centos-art.sh} script.
-
-The base-rendition produces different outputs from one unique input
-format. This is, one input file is used to produce one ore more output
-files. When translation files are available for input files, the
-base-rendition applies the translation file to the input file in order
-to produce a translated instance of it, then this translated instance
-is used as input file to produce one or more output files.
-
-Inside the @code{render} functionality of @command{centos-art.sh}
-script, the input format is always XML (e.g., SVG, XHTML, Docbook),
-the translation files are always portable objects (e.g., PO) and the
-output format depends on the input file provided (e.g., when the
-input format is a SVG file, the base output is a PNG file; when the
-input format is XHTML the base output is an XHTML file; when the input
-format is a Docbook file the base output might be either HTML, RTF, PS
-or PDF).
-
-As application example of base-rendition flow, consider the
-description of the following sections:
-
-@itemize
-@item @ref{Directories trunk Identity Models Themes Default Distro 5
-Anaconda}
-@item @ref{Directories trunk Identity Models Themes Default Distro 5.5
-Notes Release}
-@end itemize
-
-@subsubheading The post-rendition flow
-
-The post-rendition flow is performed immediatly after base-rendition
-flow to extend the base-rendition flow by applying in-place
-modifications to base-rendition output. In-place modifications can be
-performed either through the @option{--post-rendition} command-line
-option of @command{centos-art.sh} script or through directory-specific
-rendition.
-
-Actions commanded through @option{--post-rendition} option are applied
-first and directory-specific actions later. This order is required to
-propagate in-place changes commited to base-rendition output to
-modified copies (i.e., new files) of it created through
-directory-specific rendition. Creation of modified copies is
-something specific to directory-specific rendition only. It is not
-possible for the @option{--post-rendition} option to create modified
-copies of base-rendition flow because commands passed through it are
-applied to the base-rendition output file directly in a disposition
-that don't support creation of new files, but in-place modifications
-only.
-
-The command passed to @option{--post-rendition} option can be changed
-everytime you run the @command{centos-art.sh} script, but actions
-specified in directory-specific rendition cannot be changed in the
-same way. Direcctory-specific rendition is set inside
-@command{centos-art.sh} script to perform specific tasks that cannot
-be achived through @option{--post-rendition} option.
-
-As application example of post-rendition flow, consider the
-description of the following sections:
-
-@itemize
-@item @ref{Directories trunk Identity Models Themes Default Distro 5
-Syslinux}
-@item @ref{Directories trunk Identity Models Themes Default Distro 5
-Grub}
-@end itemize
-
-@subsubheading The last-rendition flow
-
-The last-rendition flow takes place after post-rendition and applies
-in-place modifications to all files produced as result of both
-base-rendition and post-rendition flows in the same directory
-structure, just before passing to process a different directory
-structure. In-place modifications can be performed either through the
-@option{--last-rendition} command-line option of
-@command{centos-art.sh} script or through directory-specific
-rendition.
-
-Actions commanded through @option{--last-rendition} option are applied
-after directory-specific actions. This order is required to prevent
-last-rendition actions commanded from directory-specifc rendition to
-overlap last-rendition actions commanded from
-@option{--last-rendition} option.
-
-The command passed to @option{--last-rendition} option can be changed
-everytime you run the @command{centos-art.sh} script, but actions
-specified in directory-specific rendition cannot be changed in the
-same way. Actions commanded from directory-specific rendition are set
-inside @command{centos-art.sh} script to perform specific tasks that
-cannot be achived through @option{--last-rendition} option.
-
-As application example of last-rendition flow, consider the
-description of the following sections:
-
-@itemize
-@item @ref{Directories trunk Identity Models Themes Default Distro 5
-Ksplash}
-@item @ref{Directories trunk Identity Models Themes Default Distro 5
-Gdm}
-@end itemize
-
-@subsubheading The directory-specific rendition flow
-
-Inside the working copy of CentOS Artwork Repository, some directory
-structure (e.g., @file{Syslinux}, @file{Gurb}, @file{Gdm}, @file{Kdm}
-and @file{KSplash}) required more than base-rendition or even the
-commands you could pass through the @option{--post-rendition} and
-@option{--last-rendition} options, in order for their final files to
-be produced. In these situations, we make use of directory-specific
-rendition flow.
-
-The directory-specific rendition flow applies specific actions to
-specific directory structures when they enter into the rendition flow.
-Using this configuration speeds up production of all those components
-that require intermediate formats or even several independent files,
-in order for the final content to be created.
-
-The directory-specific rendition flow is generally used in combination
-with post-rendition and last-rendition flows inside
-@command{centos-art.sh} script.
-
-@subsubheading Translations
-
-To translate output files, the @code{render} functionality of
-@command{centos-art.sh} script creates a translated instance of the
-input file and uses it then to create the base output file. The
-translated instance is created using the related translation messages
-of the input file. Translation messages are stored under
-@file{trunk/Locales} and are created using the @code{locale}
-functionality of @command{centos-art.sh} script (@pxref{Directories
-trunk Scripts Functions Locale}).
-
-Translation files are optional. When no translation file is available
-for the input file, the base-rendition output is produced using the
-same language of the input file.
-
-@subheading Examples
-
-@table @command
-@item centos-art render trunk/Identity/Images/Brands
-
-This command produces all branding information related to The CentOS
-Project (e.g., symbols, logos and variants of them).
-
-@item centos-art render trunk/Identity/Images/Brands --filter="symbol"
-
-This command produces all branding information, related to The CentOS
-Project, which file names contain the @samp{symbol} string on it.
-
-@item centos-art render trunk/Identity/Images/Themes/Flame/2
-
-This command produces all visual manifestations related to version 2 of
-Flame artistic motif (e.g., Distribution, Posters, etc.) as specified
-by default design models.
-
-@item centos-art render trunk/Identity/Images/Themes/Flame/2/Distro
-
-This command produces the Distribution visual manifestations related
-to version 2 of Flame artistic motif (e.g., Anaconda, Syslinux, Grub,
-Firstboot, Gdm, Kdm, Gsplash, Ksplash, and Rhgb) as specified by
-default design models.
-
-@item centos-art render trunk/Identity/Images/Themes --filter='Distro/5/Anaconda'
-
-This command produces all the images related to Anaconda component
-from Distribution visual manifestations on its major release number
-five, for all the artistic motifs available and as specified by
-default design models.
-
-@item centos-art render trunk/Identity/Images/Themes --filter='Concept' --post-rendition='mogrify -normalize'
-
-This command produces all the images related to Concept component from
-all artistic motifs as specified by default design models. Moreover,
-the @command{mogrify -normalize} command is applied to each PNG image
-produced as result of the base-rendition output.
-
-@quotation
-@strong{Note} The @command{mogrify} command is part of
-ImageMagick@registeredsymbol{} software suite and let you to resize an
-image, blur, crop, despeckle, dither, draw on, flip, join, re-sample,
-and much more. The ImageMagick@registeredsymbol{} software suite is
-copyrighted to
-@url{http://redux.imagemagick.org/MagickStudio/scripts/MagickStudio.cgi,
-ImageMagick Studio LLC}, a non-profit organization dedicated to making
-software imaging solutions freely available.
-
-@end quotation
-
-@end table
-
-@subheading Author
-
-Written by Alain Reguera Delgado.
-
-@subheading Reporting bugs
-
-Report bugs to @email{centos-artwork@@centos.org} mailing list.
-
-@subheading Copyright
-
-Copyright @copyright{} 2009, 2010, 2011 The CentOS Project.
-
-This is free software. You may redistribute copies of it under the
-terms of the GNU General Public License (@pxref{GNU General Public
-License}). There is NO WARRANTY, to the extent permitted by law.
-
-@subheading See also
-
-@itemize
-@item The ImageMagick@registeredsymbol{} software suite documentation
-(@command{rpm -qd ImageMagick | less}).
-@item @ref{Directories trunk Scripts Functions}
-@item @ref{Directories trunk Scripts}
-@item @ref{Directories trunk}
-@end itemize
diff --git a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Tuneup.texinfo b/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Tuneup.texinfo
deleted file mode 100755
index 2b6845d..0000000
--- a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Tuneup.texinfo
+++ /dev/null
@@ -1,190 +0,0 @@
-@subheading Name
-
-The @code{tuneup} functionlity is part of @command{centos-art.sh}
-script and standardizes tasks related to file maintainance inside the
-working copy of CentOS Artwork Repository.
-
-@subheading Synopsis
-
-@command{centos-art tuneup [OPTIONS] path/to/dir}
-
-The @file{path/to/dir} parameter specifies what directory structure
-inside the working copy of CentOS Artwork Repository you want to
-process.
-
-The @code{tuneup} functionality of @command{centos-art.sh} script
-accepts the following options:
-
-@table @option
-@item --quiet
-
-Supress all output messages except error messages. When this option
-is passed, all confirmation requests are supressed as well and a
-possitive answer is assumed for them, just as if the
-@option{--answer-yes} option had been provided.
-
-@item --answer-yes
-
-Assume `yes' to all confirmation requests.
-
-@item --filter="REGEX"
-
-Reduce the list of files to process using @samp{REGEX} as pattern.
-You can use this option in combination with @file{path/to/dir} in
-order to control the amount of files you want to produce as
-base-rendition. The deeper you go into the directory structure the
-more specific you'll be about the component you want to produce. When
-you cannot go deeper into the directory structure, you can use
-@option{--filter} option to reduce the list of files.
-
-@item --dont-commit-changes
-
-Supress all commit and update actions realized over files, before and
-after the action itself had took place over files in the working copy.
-
-@end table
-
-@subheading Description
-
-Tasks related to file maintainance are repetitive. You might find
-yourself doing them time after time inside the working copy of CentOS
-Artwork Repository. 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.
-
-When you execute the @code{tuneup} functionality of
-@command{centos-art.sh} script, it looks for all files that match the
-supported extensions (e.g., @file{.sh}, @file{.svg} and @file{.xhtml})
-in the directory specified, builds a list with them and applies the
-maintainance tasks using file extensions as reference.
-
-@subsubheading Maintaining @file{.sh} files
-
-If shell scripts are found, the @code{tuneup} functionality of
-@command{centos-art.sh} script reads a comment template from
-@file{trunk/Scripts/Functions/Prepare/Config/shell_topcomment.sed} and
-applies it to 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.
-
-In order for the shell script top comment template to be applied
-correctly, the shell scripts you write must have the following
-structure:
-
-@verbatim
- 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| }
-@end verbatim
-
-The @code{tuneup} functionality of @command{centos-art.sh} script
-replaces all lines between the @samp{Copyright} line (e.g., line 5)
-and the first separator line (e.g., line 9), inclusively. Everything
-else in the file will remain immutable.
-
-@subsubheading Maintaining @file{.svg} files
-
-If scalable vector graphics are found, the @code{tuneup} functionality
-reads a metadata template
-(@file{trunk/Scripts/Functions/Tuneup/Config/svg_metadata.sed}) 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 file, too.
-
-The metadata we apply from the metadata template is created dynamicaly
-combining the file absolute path, the workstation time information and
-the @command{centos-art.sh} script copyright holder information as
-reference. Additionally, the @emph{Creative Common
-Distribution-ShareAlike 3.0 License} is also set in the metadata.
-
-The elimination of unused definitions inside SVG files takes place
-through the @option{--vacuum-defs} option of @command{inkscape}
-command-line interface which is described in its man page
-(@command{man inkscape}).
-
-@subsubheading Maintaining @file{.xhtml} files
-
-If web pages are found, the @code{tuneup} functionality of
-@command{centos-art.sh} 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{
} piece
-of code be in the page.
-
-Once the @code{} piece of code has be expanded,
-there is no need to put anything else in the page. You can run the
-@code{tuneup} functionality everytime you update the heading
-information so as to update the table of contents, too.
-
-In order for the @code{tuneup} functionality of
-@command{centos-art.sh} script to transform headings, you need to put
-headings in just one line using one of the following forms:
-
-@verbatim
-
-
-
-@end verbatim
-
-In the example above, h1 can vary from h1 to h6. Closing tag must be
-present and also match the openning tag. The value of @option{name}
-and @option{href} options from the anchor element are set dynamically
-using the md5sum output of combining the page location, the
-@code{head-} string and the heading string. If any of the components
-used to build the heading reference changes, you need to run the the
-@code{tuneup} functionality of @command{centos-art.sh} script in order
-for the anchor elements to use the correct information.
-
-@subheading Examples
-
-@table @command
-@item centos-art tuneup trunk/Scripts
-
-Update the copyright and license notice of all the shell scripts we
-have in @file{trunk/Scripts} directory structure.
-
-@item centos-art tuneup trunk/Identity/Models/Brands --filter="symbol"
-Update metadata and remove unused definitions from all design models
-in @file{trunk/Identity/Models/Brands} which have the word
-@samp{symbol} in the file name.
-
-@item centos-art tuneup trunk/Identity/Webenv/App/Home
-Update headings and the related table of contents to all web pages
-inside @file{trunk/Identity/Webenv/App/Home}, recusively.
-@end table
-
-@subheading Author
-
-Written by Alain Reguera Delgado.
-
-@subheading Reporting bugs
-
-Report bugs to @email{centos-artwork@@centos.org} mailing list.
-
-@subheading Copyright
-
-Copyright @copyright{} 2009, 2010, 2011 The CentOS Project.
-
-This is free software. You may redistribute copies of it under the
-terms of the GNU General Public License (@pxref{GNU General Public
-License}). There is NO WARRANTY, to the extent permitted by law.
-
-@subheading See also
-
-@itemize
-@item @ref{Directories trunk Scripts Functions}
-@item @ref{Directories trunk Scripts}
-@item @ref{Directories trunk}
-@end itemize
diff --git a/Manuals/Texinfo/Introduction/authors.texinfo b/Manuals/Texinfo/Introduction/authors.texinfo
deleted file mode 100755
index f62bdd3..0000000
--- a/Manuals/Texinfo/Introduction/authors.texinfo
+++ /dev/null
@@ -1,41 +0,0 @@
-This section records authoring information of CentOS Artwork
-Repository along the years:
-
-@subheading Graphic Design
-
-@itemize
-@item Guideon de Kok
-@item @email{al@@art.centos.org,Alain Reguera Delgado}
-@item @email{mm@@art.centos.org,Marcus Moeller}
-@end itemize
-
-@subheading Documentation
-
-@itemize
-@item @email{al@@art.centos.org,Alain Reguera Delgado}
-@item @email{ralph@@dev.centos.org,Ralph Angenendt}
-@end itemize
-
-@subheading Localization
-
-@itemize
-@item @email{al@@art.centos.org,Alain Reguera Delgado} (Spanish)
-@end itemize
-
-@subheading Automation
-
-@itemize
-@item @email{al@@art.centos.org,Alain Reguera Delgado}
-@end itemize
-
-@subheading Infrastructure
-@itemize
-@item @email{karan@@dev.centos.org,Karanbirn Singh}
-@item @email{ralph@@dev.centos.org,Ralph Angenendt}
-@end itemize
-
-@subheading Packaging
-@itemize
-@item @email{karan@@dev.centos.org,Karanbirn Singh}
-@item @email{ralph@@dev.centos.org,Ralph Angenendt}
-@end itemize
diff --git a/Manuals/Texinfo/Introduction/chapter-intro.texinfo b/Manuals/Texinfo/Introduction/chapter-intro.texinfo
deleted file mode 100644
index 96fb6b2..0000000
--- a/Manuals/Texinfo/Introduction/chapter-intro.texinfo
+++ /dev/null
@@ -1,21 +0,0 @@
-Welcome to CentOS Artwork Repository Manual.
-
-The CentOS Artwork Repository Manual describes how The CentOS Project
-Corporate Visual Identity is organized and produced inside the CentOS
-Artwork Repository (@url{https://projects.centos.org/svn/artwork/}).
-If you are looking for a comprehensive, task-oriented guide for
-understanding how The CentOS Project Corporate Visual Identity is
-produced, this is the manual for you.
-
-This manual discusses the following intermedite topics:
-
-@itemize
-@item The CentOS Brand
-@item The CentOS Corporate Visual Structure
-@item The CentOS Corporate Visual Style
-@end itemize
-
-This guide assumes you have a basic understanding of your CentOS
-system. If you need help with CentOS, refer to the help page on the
-CentOS Wiki (@url{http://wiki.centos.org/Help}) for a list of
-different places you can find help.
diff --git a/Manuals/Texinfo/Introduction/chapter-menu.texinfo b/Manuals/Texinfo/Introduction/chapter-menu.texinfo
deleted file mode 100644
index 39781c3..0000000
--- a/Manuals/Texinfo/Introduction/chapter-menu.texinfo
+++ /dev/null
@@ -1,8 +0,0 @@
-@menu
-* History::
-* Authors::
-* Copying Conditions::
-* Document Convenctions::
-* Repository Convenctions::
-* Feedback::
-@end menu
diff --git a/Manuals/Texinfo/Introduction/chapter-nodes.texinfo b/Manuals/Texinfo/Introduction/chapter-nodes.texinfo
deleted file mode 100644
index dff1350..0000000
--- a/Manuals/Texinfo/Introduction/chapter-nodes.texinfo
+++ /dev/null
@@ -1,30 +0,0 @@
-@node History
-@section History
-@cindex History
-@include Introduction/history.texinfo
-
-@node Authors
-@section Authors
-@cindex Authors
-@include Introduction/authors.texinfo
-
-@node Copying Conditions
-@section Copying Conditions
-@cindex Copying conditions
-@include Introduction/copying.texinfo
-
-@node Document Convenctions
-@section Document Convenctions
-@cindex Document convenctions
-@include Introduction/doc-convenctions.texinfo
-
-@node Repository Convenctions
-@section Repository Convenctions
-@cindex Repository convenctions
-@include Introduction/repo-convenctions.texinfo
-
-@node Feedback
-@section Send in Your Feedback
-@cindex Feedback
-@include Introduction/feedback.texinfo
-
diff --git a/Manuals/Texinfo/Introduction/chapter.texinfo b/Manuals/Texinfo/Introduction/chapter.texinfo
deleted file mode 100644
index de11d5f..0000000
--- a/Manuals/Texinfo/Introduction/chapter.texinfo
+++ /dev/null
@@ -1,6 +0,0 @@
-@node Introduction
-@chapter Introduction
-@cindex Introduction
-@include Introduction/chapter-intro.texinfo
-@include Introduction/chapter-menu.texinfo
-@include Introduction/chapter-nodes.texinfo
diff --git a/Manuals/Texinfo/Introduction/copying.texinfo b/Manuals/Texinfo/Introduction/copying.texinfo
deleted file mode 100755
index 01bc2af..0000000
--- a/Manuals/Texinfo/Introduction/copying.texinfo
+++ /dev/null
@@ -1,70 +0,0 @@
-Copyright @copyright{} 2009, 2010, 2011 The CentOS Project.
-
-Everyone is permitted to copy and distribute verbatim copies of this
-license document, but changing it is not allowed.
-
-@subheading Preamble
-
-The CentOS Artwork Repository organizes files in a very specific way
-to implement The CentOS Project corporate visual identity. This very
-specific organization of files is part of @command{centos-art.sh}
-script, a bash script that automate most of the frequent tasks inside
-the repository.
-
-The @command{centos-art.sh} script and the organization of files it
-needs to work are not in the public domain; they are copyrighted and
-there are restrictions on their distribution, but these restrictions
-are designed to permit everything that a good cooperating citizen
-would want to do. What is not allowed is to try to prevent others
-from further sharing any version of this program that they might get
-from you.
-
-Specifically, we want to make sure that you have the right to give
-away copies of @command{centos-art.sh} script, that you receive source
-code or else can get it if you want it, that you can change this
-program or use pieces of it in new free programs, and that you know
-you can do these things.
-
-To make sure that everyone has such rights, we have to forbid you to
-deprive anyone else of these rights. For example, if you distribute
-copies of the @command{centos-art.sh} script, you must give the
-recipients all the rights that you have. You must make sure that
-they, too, receive or can get the source code. And you must tell them
-their rights.
-
-Also, for our own protection, we must make certain that everyone finds
-out that there is no warranty for the @command{centos-art.sh} script.
-If this program is modified by someone else and passed on, we want
-their recipients to know that what they have is not what we
-distributed, so that any problems introduced by others will not
-reflect on our reputation.
-
-The centos-art.sh script is released as a GPL work. Individual
-packages used by centos-art.sh script include their own licenses and
-the centos-art.sh script license applies to all packages that it does
-not clash with. If there is a clash between the centos-art.sh script
-license and individual package licenses, the individual package
-license applies instead.
-
-The precise conditions of the license for the @command{centos-art.sh}
-script are found in the General Public Licenses (@pxref{GNU General
-Public License}). This manual specifically is covered by the GNU Free
-Documentation License (@pxref{GNU Free Documentation License}).
-
-@subheading 1. The CentOS Brand
-
-The CentOS Brand (@pxref{Directories trunk Identity Models Brands}) is
-the main visual manifestaion of The CentOS Project. The CentOS Project
-uses The CentOS Brand to connect all its visual manifestions (e.g.,
-GNU/Linux Distributions, Websites, Stationery, etc.) and, this way, it
-provides recognition among other similar projects.
-
-Both The CentOS Brand and all the visual manifestations that derivate
-from it are available for you to study and propose improvement around
-a good citizen's will at The CentOS Community environment, but you are
-not allowed to redistribute them elsewhere, without the given
-permission of The CentOS Project.
-
-If you need to redistribute either The CentOS Brand or any the visual
-manifestatinos that derivate from it, write your intentions to the
-@email{centos-devel@@centos.org} mailing list.
diff --git a/Manuals/Texinfo/Introduction/doc-convenctions.texinfo b/Manuals/Texinfo/Introduction/doc-convenctions.texinfo
deleted file mode 100644
index 9a9cca6..0000000
--- a/Manuals/Texinfo/Introduction/doc-convenctions.texinfo
+++ /dev/null
@@ -1,109 +0,0 @@
-In this manual the personal pronoun @emph{we} is used to repesent
-@emph{The CentOS Artwork SIG}. This is, the group of persons building
-the CentOS Artwork Repository.
-
-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:
-
-@table @command
-@item command
-
-Linux commands (and other operating system commands, when used) are
-represented this way. This style should indicate to you that you can
-type the word or phrase on the command line and press Enter to invoke
-a command. Sometimes a command contains words that would be displayed
-in a different style on their own (such as file names). In these
-cases, they are considered to be part of the command, so the entire
-phrase is displayed as a command. For example:
-
-Use the @command{centos-art identity --render='path/to/dir'} command
-to produce contents inside the @file{trunk/Identity} directory
-structure.
-@end table
-
-@table @file
-@item file name
-
-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:
-
-The @file{init.sh} file in @file{trunk/Scripts/Bash/Cli/} directory is
-the initialization script, written in Bash, used to automate most of
-tasks in the repository.
-
-The @command{centos-art} command uses the @file{ImageMagick} RPM
-package to convert images from PNG format to other formats.
-@end table
-
-@table @key
-@item @key{key}
-
-A key on the keyboard is shown in this style. For example:
-
-To use @key{TAB} completion to list particular files in a directory,
-type @command{ls}, then a character, and finally the Tab key. Your
-terminal displays the list of files in the working directory that
-begin with that character.
-@end table
-
-@table @key
-@item @key{key-combination}
-A combination of keystrokes is represented in this way. For example:
-
-The @key{Ctrl-Alt-Backspace} key combination exits your graphical
-session and returns you to the graphical login screen or the console.
-@end table
-
-@table @code
-@item @code{computer output}
-
-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 displays the contents of a directory. For example:
-
-@verbatim
-Config help_renameEntry.sh
-help_copyEntry.sh help_restoreCrossReferences.sh
-help_deleteCrossReferences.sh help_searchIndex.sh
-@end verbatim
-
-The output returned in response to the command (in this case, the
-contents of the directory) is shown in this style.
-@end table
-
-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:
-
-@quotation
-@strong{Note} Remember that Linux is case sensitive. In other words, a
-rose is not a ROSE is not a rOsE.
-@end quotation
-
-@quotation
-@strong{Tip} The directory @file{/usr/share/doc/} contains additional
-documentation for packages installed on your system.
-@end quotation
-
-@quotation
-@strong{Important} If you modify the DHCP configuration file, the
-changes do not take effect until you restart the DHCP daemon.
-@end quotation
-
-@quotation
-@strong{Caution} Do not perform routine tasks as root --- use a
-regular user account unless you need to use the root account for
-system administration tasks.
-@end quotation
-
-@quotation
-@strong{Warning} Be careful to remove only the necessary partitions.
-Removing other partitions could result in data loss or a corrupted
-system environment.
-@end quotation
diff --git a/Manuals/Texinfo/Introduction/feedback.texinfo b/Manuals/Texinfo/Introduction/feedback.texinfo
deleted file mode 100644
index 1c7f597..0000000
--- a/Manuals/Texinfo/Introduction/feedback.texinfo
+++ /dev/null
@@ -1,9 +0,0 @@
-If you find an error in the @emph{CentOS Artwork Repository}, or if
-you have thought of a way to make this manual better, we would like to
-hear from you! Share your suggestions in the appropriate mailing list
-(@url{http://lists.centos.org/}) and/or bug tracker
-(@url{http://bugs.centos.org/}).
-
-When you make suggestion, try to be as specific as possible. For
-example, if you have found an error in the manual, include the section
-number and some of the surrounding text so we can find it easily.
diff --git a/Manuals/Texinfo/Introduction/history.texinfo b/Manuals/Texinfo/Introduction/history.texinfo
deleted file mode 100755
index 1785ad1..0000000
--- a/Manuals/Texinfo/Introduction/history.texinfo
+++ /dev/null
@@ -1,118 +0,0 @@
-This section records noteworthy changes of CentOS Artwork Repository
-through years.
-
-@subheading 2008
-
-The CentOS Artwork Repository started at CentOS Developers mailing
-list (@email{centos-devel@@centos.org}) during a discussion about how
-to automate the slide images of Anaconda. In such discussion, Ralph
-Angenendt rose up his hand to ask: Do you have something to show?
-
-To answer the question, Alain Reguera Delgado suggested a bash script
-which combined SVG and SED files in order to produce PNG images in
-different languages ---together with the proposition of creating a
-Subversion repository where translations and image production could be
-distributed inside The CentOS Community---.
-
-Karanbirn Sighn considered the idea intresting and provided the
-infrastructure necessary to support the effort. This way the CentOS
-Artwork SIG and the CentOS Artwork Repository were officially created
-and made available in the following urls:
-
-@itemize
-@item @url{https://projects.centos.org/trac/artwork/}
-@item @url{https://projects.centos.org/svn/artwork/}
-@end itemize
-
-Once the CentOS Artwork Repository was available, Alain Reguera
-Delagdo uploaded the bash script for rendering Anaconda slides; Ralph
-Angenendt documented it very well and The CentOS Translators started
-to download working copies of CentOS Artwork Repository to produce
-slide images in their own languages.
-
-@subheading 2009
-
-The rendition script is at a very rustic state where only slide images
-can be produced.
-
-The rendition script was redesigned to extend image production to
-other areas, not just slide images. In this configuration one
-translated SVG instance was created from the SVG file provided as
-input in order to produce one translated PNG image as output. The
-translation of SVG files was made through SED replacement commands and
-the rendition of PNG images was realized through Inkscape command line
-internface.
-
-The rendition script was named @command{render.sh}. The directory
-structures were prepared to receive the rendition script so images
-could be produced inside them. Each directory structure had design
-templates (.svg), translation files (.sed), and translated images
-(.png).
-
-The rendition script was unified in 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.
-
-Concepts about corporate identity began to be considered. As referece,
-it was used the book @emph{Corporate Identity} by Wally Olins (1989)
-and Wikipedia (@url{http://en.wikipedia.org/Corporate_identity}).
-
-The rendition script main's goal becomes to: automate production of a
-monolithic corporate visual identity structure, based on The CentOS
-Mission and The CentOS Release Schema.
-
-The documentation of CentOS Artwork Repository started to take form in
-@LaTeX{} format.
-
-@subheading 2010
-
-The rendition script @command{render.sh} is no longer a rendition
-script, but a collection of functionalities grouped into the
-@command{centos-art.sh} script where rendition is one functionality
-among others. The @command{centos-art.sh} is created to automate most
-frequent tasks inside the repository. There is no need to have links
-all around the repository if a command-line interface can be created
-(through symbolic links, in the @file{~/bin} directory) and be called
-anywhere inside the repository as it would be usually done with
-regular commands.
-
-Inside @command{centos-art.sh}, functionalities started to get
-identified and separated one another. For example, when images were
-rendered, there was no need to load functionalities related to
-documentation manual. This moved us onto common functionalities and
-specific functionalities inside @command{centos-art.sh} script. Common
-functionalities are loaded when the script is initiated and are
-available to specific functionalities.
-
-The @command{centos-art.sh} script was redesigned to handle options
-trough @command{getopt} option parser.
-
-The repository directory structure was updated to improve the
-implementation of concepts related to corporate visual identity.
-Specially in the area related to themes which were divided into design
-models and artistic motifs.
-
-@subheading 2011
-
-The @command{centos-art.sh} script was redesigned to start translating
-SVG and other XML-based files (e.g., XHTML and Docbook files) through
-the @command{xml2po} program and shell scripts files (e.g., Bash
-scripts) through GNU @command{gettext} tools. This configuration
-provided a stronger interface for graphic designers, translators and
-programmers at time of producing localized content. @file{.sed} files
-are no longer used to handle translations.
-
-Improve option parsing through @command{getopt}.
-
-The @command{centos-art.sh} script is updated to organize
-functionalities in two groups: ``the administrative functionalities''
-and ``the productive functionalities''. The administrative
-functionalities cover actions like: copying, deleting and renaming
-directory structures inside the repository. Also, preparing your
-workstation for using @command{centos-art.sh} script, making backups
-of the distribution theme currently installed, installing themes
-created inside repository and restoring themes from backup. On the
-other hand, the productive functionalities cover actions like: content
-rendition, content localization, content documentation and content
-maintainance.
diff --git a/Manuals/Texinfo/Introduction/repo-convenctions.texinfo b/Manuals/Texinfo/Introduction/repo-convenctions.texinfo
deleted file mode 100644
index 48b2fae..0000000
--- a/Manuals/Texinfo/Introduction/repo-convenctions.texinfo
+++ /dev/null
@@ -1,537 +0,0 @@
-The CentOS Artwork Repository is supported by Subversion
-(@url{http://subversion.tigris.org/}), a version control system which
-allows you to keep old versions of files and directories (usually
-source code), keep a log of who, when, and why changes occurred, etc.,
-like CVS, RCS or SCCS.
-
-When using Subversion there is one @emph{source repository} and many
-@emph{working copies} of that source repository. The working copies
-are independent one another, can be distributed all around the world
-and provide a local place for designers, documentors, translators and
-programmers to perform their works in a descentralized way. The
-source repository, on the other hand, provides a central place for all
-independent working copies to interchange data and provides the
-information required to permit extracting previous versions of files
-at any time.
-
-@subsection Repository policy
-@cindex Repository policy
-
-The CentOS Artwork Repository is a collaborative tool that anyone can
-have access to. However, changing that tool in any form is something
-that should be requested in @email{centos-devel@@centos.org} mailing
-list. Generally, people download working copies from CentOS Artwork
-Repository, study the repository organization, make some changes in
-their working copies, make some tests to verify such changes do work
-the way expected and finally request access to commit them up to the
-CentOS Artwork Repository (i.e., the source repository) for others to
-benefit from them.
-
-Once you've received access to commit your changes, there is no need
-for you to request permission again to commit other changes from your
-working copy to CentOS Artwork Repository as long as you behave as a
-@emph{good community citizen}.
-
-As a good community citizen one understand of a person who respects
-the work already done for others and share ideas with authors before
-changing relevant parts of their work, specially in situations when
-the access required to realize the changes has been granted already.
-Of course, there is a time when conversation has taken place, the
-paths has been traced and changing the work is so obvious that there
-is no need for you to talk about it; that's because you already did,
-you already built the trust to keep going. Anyway, the mailing list
-mentioned above is available for sharing ideas in a way that good
-relationship between community citizens could be constantly balanced.
-
-The relationship between community citizens is monitored by repository
-administrators. Repository administrators are responsible of granting
-everything goes the way it needs to go in order for the CentOS Artwork
-Repository to comply its mission which is: to provide a colaborative
-tool for The CentOS Community where The CentOS Project Corporate
-Identity is built and maintained from The CentOS Community itself.
-
-It is also important to remember that all source files inside CentOS
-Artwork Repository should comply the terms of GNU General Public
-License (@pxref{GNU General Public License}) in order for them to
-remain inside the repository.
-
-@subsection Repository organization
-@cindex Repository organization
-
-The CentOS Artwork Repository uses a @file{trunk}, @file{branches},
-and @file{tags} organization.
-
-@table @file
-@item trunk
-
-The @file{trunk} directory organizes the main development line of
-CentOS Artwork Repository. @xref{Directories trunk}, for more
-information.
-
-@item branches
-
-The @file{branches} directory oranizes intermediate development lines
-taken from the main development line. @xref{Directories branches},
-for more information.
-
-@item tags
-
-The @file{tags} directory organizes frozen development lines taken
-either from the main or the intermediate lines of development.
-@xref{Directories tags}, for more information.
-@end table
-
-@subsection Repository file names
-@cindex Repository file names
-
-Inside the CentOS Artwork Repository, file names are all written in
-lowercase (e.g., @samp{01-welcome.png}, @samp{splash.png},
-@samp{anaconda_header.png}, etc.) and directory names are all written
-capitalized (e.g., @samp{Identity}, @samp{Themes}, @samp{Motifs},
-@samp{TreeFlower}, etc.).
-
-@subsection Repository work lines
-
-Inside CentOS Artwork Repository there are four major work lines of
-production which are: @emph{graphic design}, @emph{documentation},
-@emph{localization} and @emph{automation}. These work lines describe
-different areas of content production. Content production inside these
-specific areas may vary as much as persons be working on them.
-Producing content in too many different ways may result innapropriate
-in a collaborative environment like CentOS Artwork Repository where
-content produced in one area depends somehow from content produced in
-another different area. So, a @emph{content production standard} is
-required for each available work line.
-
-@subsubsection Graphic design
-@cindex Graphic design work line
-
-The graphic design work line exists to cover brand design, typography
-design and themes design mainly. Additionally, some auxiliar areas
-like icon design, illustration design, brushes design, patterns
-designs and palettes of colors are also included here for
-completeness.
-
-Inside CentOS Artwork Repository graphic design is performed through
-Inkscape (@url{http://www.inkscape.org/}) and GIMP
-(@url{http://www.gimp.org/}). The Inkscape tool is used to create and
-manipulate scalable vector graphics and export them to PNG format; it
-also provides a command-line interface that we use to perform massive
-exportation from SVG files to PNG files in automation scripts. On the
-other hand, GIMP is used to create and manipulate rastered images,
-create brushes, patterns and palettes of colors.
-
-@quotation
-@strong{Tip} Combine both Inkscape and GIMP specific functionalities
-and possibilities to produce very beautiful images.
-@end quotation
-
-The CentOS Project Corporate Visual Identity is made of different
-visual manifestations (e.g., Distributions, Web sites, Stationery,
-etc.). Visual manifestations implement the corporate identity
-concepts by mean of images. To produce these images, we decompose
-image production in @emph{design models} and @emph{artistic motifs}.
-
-Design models provide the structural information of images (i.e.,
-dimension, position of common elements in the visible area,
-translation markers, etc.) and they are generally produced as scalable
-vector graphics to take advantage of SVG standard, an XML-based
-standard.
-
-Artistic motifs provide the visual style (i.e., the background
-information, the look and feel) some design models need to complete
-the final image produced by automation scripts. Artistic motifs are
-generally produced as rastered images.
-
-The result produced from combining one design model with one artistic
-motif is what we know as a @emph{theme}. Inside themes directory
-structure (@pxref{Directories trunk Identity Images Themes}), you can find
-several design models and several artistic motifs independently one
-another that can be albitrarily combined through @emph{theme
-rendition}, a flexible way to produce images for different visual
-manifestations in very specific visual styles. Inside themes directory
-structure, theme rendition is performed in
-@file{trunk/Identity/Images/Themes} directory structure, the required
-design models are taken from @file{trunk/Identity/Models/Themes}
-directory structure and the action itself is controlled by the
-@code{render} functionality of @command{centos-art.sh} script.
-
-In addition to theme rendition you can find @emph{direct rendition},
-too. Direct rendition is another way of image production where there
-is no artistic motif at all but design models only. Direct rendition
-is very useful to produce simple content that doesn't need specific
-background information. Some of these contents are brands, icons and
-illustrations. Direct rendition is performed in
-@file{trunk/Identity/Images}, the required design models are taken
-from @file{trunk/Identity/Models} directory structure and the action
-itself is controlled by the @code{render} functionality of
-@command{centos-art.sh} script.
-
-@xref{Directories trunk Identity}, for more information about The
-CentOS Corporate Identity and how graphic design fits on it.
-
-@subsubsection Documentation
-@cindex Documentation work line
-
-The documentation work line exists to describe what each directory
-inside the CentOS Artwork Repository is for, the conceptual ideas
-behind them and, if possible, how automation scripts make use of them.
-
-The CentOS Artwork Repository documentation is supported by Texinfo, a
-documentation system that uses a single source file to produce both
-online information and printed output.
-
-The repository documentation is organized under @file{trunk/Manual}
-directory and uses the repository directory structre as reference.
-Each directory in the repository has a documentation entry associated
-in the documentation manual. Documentation entries are stored under
-@file{trunk/Manual/Directories} directory and the action itself is
-controlled by the @code{help} functionality of @command{centos-art.sh}
-script.
-
-The @code{help} functionality let you create, edit and delete
-documentation entries in a way that you don't need to take care of
-updating menus, nodes and cross reference information inside the
-manual structure; the functionality takes care of it for you.
-However, if you need to write repository documentation that have
-nothing to do with repository directories (e.g., Preface, Introduction
-and similar) you need to do it manually, there is no functionality to
-automate such process yet.
-
-@xref{Directories trunk Manuals}, for more information on
-documentation.
-
-@subsubsection Localization
-@cindex Localization work line
-
-The localization work line exists to provide the translation messages
-required to produce content in different languages. Translation
-messages inside the repository are stored as portable objects (e.g.,
-.po, .pot) and machine objects (.mo) under @file{trunk/Locales}
-directory structure.
-
-The procedure used to localize content is taken from @command{gettext}
-standard specification. Basically, translatable strings are retrived
-from source files in order to create portable objects and machine
-objects for them. These portable objects are editable files that
-contain the information used by translators to localize the
-translatable strings retrived from source files. On the other hand,
-machine objects are produced to be machine-redable only, as its name
-implies, and are produced from portable objects.
-
-Since @command{gettext} needs to extract translatable strings form
-source files in order to let translators to localize them, we are
-limitted to use source files supported by @command{gettext} program.
-This is not a limitation at all since @command{gettext} supports most
-popular programming laguages (e.g., C, C++, Java, Bash, Python, Perl,
-PHP and GNU Awk just to mention a few ones). Nevertheless, formats
-like SVG, XHTML and Docbook don't figure as supported formats in the
-list of @command{gettext} supported source files.
-
-To translate XML based source files like SVG, XHTML and Docbook we use
-the @command{xml2po} program instead. The @command{xml2po} comes with
-the @file{gnome-doc-utils} package and retrives translatable strings
-from one XML file to produce portable objects for them.
-
-@quotation
-@strong{Note}
-Portable objects produced by @command{xml2po} have the same format
-that portable objects produced by @command{gettext}. This make the
-localization process quite consistent from translators' point of view.
-No matter what the source file be, the translator will always face the
-same translation file format (i.e., the portable object format).
-@end quotation
-
-With the portable object in place, the @command{xml2po} program is
-used again to create the final translated XML, just with the same
-definition of the source file where translatable strings were taken
-from (e.g., if we extract translatable strings from a SVG file, as
-result we get the same SVG file but with translatable strings already
-localized ---obviously, for this to happen translators need to
-localize translatable strings inside the portable object first,
-localization won't appear as art of magic---). When using
-@command{xml2po}, the machine object is used as temporal file to
-produce the final translated XML file.
-
-@quotation
-@strong{Tip} If you want to have your content localized inside CentOS
-Artwork Repository be sure to use source files supported either by
-@command{gettext} or @command{xml2po} programs.
-@end quotation
-
-@xref{Directories trunk Locales}, for more information.
-
-@subsubsection Automation
-@cindex Automation work line
-
-The automation work line exists to standardize content production in
-CentOS Artwork Repository. There is no need to type several tasks,
-time after time, if they can be programmed into just one executable
-script.
-
-The automation work line takes place under @file{trunk/Scripts}
-directory structure. Here is developed the @command{centos-art.sh}
-script, a bash script specially designed to automate most frequent
-tasks (e.g., rendition, documentation and localization) inside the
-repository. Basically, the @command{centos-art.sh} script is divided
-in several functionalities independent one another that perform
-specific tasks and relay on repository organization to work as
-expected.
-
-@quotation
-@strong{Tip} If you need to improve the way content is produced, look
-inside automation scripts and make your improvement there for everyone
-to benefit.
-@end quotation
-
-@xref{Directories trunk Scripts}, for more information on automation.
-
-@subsection Connection between directories
-@cindex Connection between directories
-@cindex Master paths
-@cindex Auxiliar paths
-
-In order to produce content in CentOS Artwork Repository, it is
-required that all work lines be connected somehow. This is the way
-automation scripts can know where to retrive the information they need
-to work with (e.g., design model, translation messages, output
-location, etc.). We build this kind of connection using two path
-constructions named @emph{master paths} and @emph{auxiliar paths}.
-
-The master path points only to directories that contain the source
-files (e.g., SVG files) required to produce base content (e.g., PNG
-files) through automation scripts. Each master path inside the
-repository may have several auxiliar paths associated, but auxiliar
-paths can only have one master path associated.
-
-The auxiliar paths can point either to directories or files. When an
-auxiliar path points to a directory, that directory contains
-information that modifies somehow the content produced from master
-paths (e.g., translation messages) or provides the output information
-required to know where to store the content produced from master path.
-When an auxiliar path points to a file, that file has no other purpose
-but to document the master path it refers to.
-
-The relation between auxiliar paths and master paths is realized
-combining two path informations which are: the master path itself and
-one second level directory structure from the repository. Generally,
-the master path is considered the path identifier and the second level
-directory structure taken from the repository is considered the common
-part of the path where the identifier is appended.
-
-@float Figure, Path construction
-@verbatim
------+---------------+----------------------------+------+-----------
-Path | Suffix | Identifier |Prefix| Type
------+---------------+----------------------------+------+-----------
- A | |trunk/Identity/Models/Brands| | Directory
------+---------------+----------------------------+------+-----------
- B | trunk/Manual/|trunk/Identity/Models/Brands|.texinfo | File
------+---------------+----------------------------+------+-----------
- C | trunk/Locales/|trunk/Identity/Models/Brands| | Directory
------+---------------+----------------------------+------+-----------
- D | |trunk/Identity/Images/Brands| | Directory
------+---------------+----------------------------+------+-----------
- E | trunk/Locales/|trunk/Identity/Images/Brands|.texinfo | File
------+---------------+----------------------------+------+-----------
-
- A = Master path.
- B = Auxiliar path to documentation entry.
- C = Auxiliar path to translation messages.
- D = Auxiliar path to final content output.
- E = Auxiliar path to documentation entry.
-@end verbatim
-@caption{Path construction.}
-@end float
-
-The path information described above (@pxref{Path construction}) is
-used by direct rendition and can be taken as reference to add other
-components that are equally produced in the repository. To add new
-components that make use of direct rendition inside the repository,
-change just the component name used above (e.g., @file{Brands}) to
-that one you want to add, without changing the path structure around
-it.
-
-The file organization used by theme rendition extends direct rendition
-by separating design models information from backgrounds information.
-To better understand this configuration, you can consider it as two
-independent lists, one of design models and one of artistic motifs,
-which are arbitrary combined between themselves in order to render
-images in specific ways. The possibilities of this configuration are
-endless and let us describe visual manifestations very well. For
-example, consider the organization used to produce @file{Anaconda}
-images; for CentOS distribution major release 5; using @file{Default}
-design models and version @file{3} of @file{Flame} artistic motif:
-
-@float Figure, Path construction extended
-@verbatim
------+---------------+------------------------------------------------------+------+-----------
-Path | Suffix | Identifier |Prefix| Type
------+---------------+------------------------------------------------------+------+-----------
- A | |trunk/Identity/Models/Themes/Default/Distro/5/Anaconda| | Directory
------+---------------+------------------------------------------------------+------+-----------
- B | trunk/Manual/|trunk/Identity/Models/Themes/Default/Distro/5/Anaconda|.texinfo | File
------+---------------+------------------------------------------------------+------+-----------
- C | trunk/Locales/|trunk/Identity/Models/Themes/Default/Distro/5/Anaconda| | Directory
------+---------------+------------------------------------------------------+------+-----------
- D | |trunk/Identity/Images/Themes/Flame/3/Distro/5/Anaconda| | Directory
------+---------------+------------------------------------------------------+------+-----------
- E | trunk/Locales/|trunk/Identity/Images/Themes/Flame/3/Distro/5/Anaconda|.texinfo | File
------+---------------+------------------------------------------------------+------+-----------
-
- A = Master path.
- B = Auxiliar path to documentation entry.
- C = Auxiliar path to translation messages.
- D = Auxiliar path to final content output.
- E = Auxiliar path to documentation entry.
-@end verbatim
-@caption{Path construction extended.}
-@end float
-
-The path information described above (@pxref{Path construction
-extended}) is used by theme rendition and can be taken as reference to
-add other components that are equally produced in the repository.
-
-In this configuration we can change both design model name (e.g.,
-@file{Default}) and artistic motif name (e.g., @file{Flame/3}) to
-something else in order to achieve a different result. The only
-limitations impossed are the storage space provided in the server
-machine and your own creativeness as graphic designer.
-
-@quotation
-@strong{Note}
-A theme ready for implementation may consume from 100 MB to 400 MB of
-storage space. The exact space consumed by a theme depends on the
-amount of screen resolutions the theme supports. The more screen
-resolutions the theme supports, the more storage space demanded for
-it.
-@end quotation
-
-In this configuration we saw how to build the path information for
-@file{Anaconda} component as part of CentOS Distribution visual
-manifestation, but that is not the only component we have inside
-CentOS Distribution visual manifestation. There are other components
-like Syslinux, Grub, Rhgb, Gdm, Kdm, Gsplash and Ksplash that share a
-similar file organization to that described above for @file{Anaconda}
-component.
-
-@subsection Syncronizing path information
-@cindex Syncronizing path information
-
-Syncronizing path information is the action that keeps all path
-information up to date in the repository. This action implies both
-@emph{file movement} and @emph{file content replacement} in this very
-specific order. File movement is related to duplicate, delete and
-rename files and directories in the repository. File content
-replacement is related to replace information, path information in
-this case, inside files in the repository.
-
-The order followed to syncronize path information is relevant because
-the versioned nature of the files we are working with. We don't
-perform file content replacement first because that would imply a
-repository change which will immediatly demmand a commit in order for
-actions like duplicate, delete or rename to take place. However, if we
-perform file movement first, it is possible to commit both file moved
-and file content replacements as if they were just one change. In this
-case the file content replacement takes palce in the target location
-that have been duplicated or renamed, not the one use as source
-location. This configuration is specially useful when files are
-renamed (i.e., one file is copied from a source location to a target
-location and then the source location of it is removed from
-repository).
-
-@quotation
-@strong{Warning} There is no support for URLs actions inside
-@command{centos-art.sh} script. The @command{centos-art.sh} script is
-designed to work with local files inside the working copy only. If you
-need to perform URL actions directly, use Subversion commands instead.
-@end quotation
-
-When one master path is changed it is required that all related
-auxiliar paths be changed, too. This is required in order for master
-paths to retain their relation with auxiliar paths. This way,
-automation scripts are able to know where to retrive translation
-messages from, where to store final output images to and where to look
-for documentation. If relation between master paths and auxiliar paths
-is lost, there is no way for automation scripts to know where to
-retrive the information they need.
-
-The auxiliar paths should never be modified under any reason but to
-satisfy the relationship with the master path. Liberal change of
-auxiliar paths may suppress the conceptual idea they were initially
-created for; and certainly, automation scripts may stop working as
-expected. The update direction to rename path information must be from
-master path to auxiliar path and never the opposite.
-
-The relation between master and auxiliar paths is useful to keep
-repository organized but introduce some complications when we work
-with files that use master path information as reference to build
-structural information. This is the case of repository documentation
-manual source files where inclusions, menus, nodes and cross
-references are built using master path information as reference. Now,
-to see what kind of complication we are talking about, consider what
-would happen to a structural definitions (i.e., inlusions, menus,
-nodes and cross refereces) already set in the manual from one master
-path that is suddenly renamed to something different. If the path
-information is not syncronized, at this point, we lose connection
-between the master path and the auxiliar path created to store the
-related documentation entry, as well as the related structural
-definitions that end up pointing to a master path that no longer
-exist.
-
-The syncronization of path information is aimed to solve these kind of
-issues.
-
-@subsection Extending repository organization
-@cindex Extending repository organization
-
-Occasionly, you may find that new components of The CentOS Project
-Corporate Identity need to be added to the repository in order to work
-them out. If that is the case, the first question we need to ask
-ourselves, before start to create directories blindly all over, is:
-@emph{What is the right place to store it?}
-
-The best place to find answers is in The CentOS Community (see page
-@url{http://wiki.centos.org/GettingHelp}), but going there with hands
-empty is not good idea. It may give the impression you don't really
-care about. Instead, consider the following suggestions to find your
-own comprehension in order to make your own propositions based on it.
-
-When extending respository structure it is very useful to bear in mind
-The CentOS Project Corporate Identity Structure (@pxref{Directories
-trunk Identity}) The CentOS Mission and The CentOS Release Schema. The
-rest is just matter of choosing appropriate names. It is also worth to
-know that each directory in the repository responds to a conceptual
-idea that justifies its existence.
-
-To build a directory structure, you need to define the conceptual idea
-first and later create the directory. There are some locations inside
-the repository that already define some concepts you probably want to
-reuse. For example, @file{trunk/Identity/Images/Themes} to store theme
-artistic motifs, @file{trunk/Identity/Models/Themes} to store theme
-design models, @file{trunk/Manual} to store documentation files,
-@file{trunk/Locales} to store translation messages,
-@file{trunk/Scripts} to store automation scripts and so on.
-
-To illustrate this desition process let's consider the
-@file{trunk/Identity/Images/Themes/TreeFlower/3} directory structure
-as example. This directory can be read as: the theme development line
-of version @file{3} of @file{TreeFlower} artistic motif. Additional,
-we can identify that artistic motifs are part of themes as well as
-themes are part of The CentOS Project Corporate Identity. These
-concepts are better described independently in each documentation
-entry related to the directory structure as it is respectively shown
-in the list of commands bellow.
-
-@verbatim
-centos-art help --read turnk
-centos-art help --read turnk/Identity
-centos-art help --read turnk/Identity/Themes
-centos-art help --read turnk/Identity/Images/Themes
-centos-art help --read turnk/Identity/Images/Themes/TreeFlower
-centos-art help --read turnk/Identity/Images/Themes/TreeFlower/3
-@end verbatim
-
-The concepts behind other location can be found in the same way
-described above, just change the path information used above to the
-one you are trying to know concepts for.
diff --git a/Manuals/Texinfo/Licenses/GFDL.texinfo b/Manuals/Texinfo/Licenses/GFDL.texinfo
deleted file mode 100755
index 922d49a..0000000
--- a/Manuals/Texinfo/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 IDENPENDENT 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 Appendix 1. 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 Appendix 2. 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/Manuals/Texinfo/Licenses/GPL.texinfo b/Manuals/Texinfo/Licenses/GPL.texinfo
deleted file mode 100755
index 01fb28c..0000000
--- a/Manuals/Texinfo/Licenses/GPL.texinfo
+++ /dev/null
@@ -1,352 +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
-
-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.
-
-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.
-
-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.
-
-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.
-
-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.
-
-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.
-
-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.
-
-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.
-
-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.
-
-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.
-
-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.
-
-@strong{NO WARRANTY}
-
-11. 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.
-
-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 Appendix: 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
-
- Copyright (C) 19yy
-
- 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.
-
- , 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/Manuals/Texinfo/Licenses/chapter-intro.texinfo b/Manuals/Texinfo/Licenses/chapter-intro.texinfo
deleted file mode 100755
index e69de29..0000000
--- a/Manuals/Texinfo/Licenses/chapter-intro.texinfo
+++ /dev/null
diff --git a/Manuals/Texinfo/Licenses/chapter-menu.texinfo b/Manuals/Texinfo/Licenses/chapter-menu.texinfo
deleted file mode 100755
index b8240ba..0000000
--- a/Manuals/Texinfo/Licenses/chapter-menu.texinfo
+++ /dev/null
@@ -1,4 +0,0 @@
-@menu
-* GNU General Public License::
-* GNU Free Documentation License::
-@end menu
diff --git a/Manuals/Texinfo/Licenses/chapter-nodes.texinfo b/Manuals/Texinfo/Licenses/chapter-nodes.texinfo
deleted file mode 100755
index da69108..0000000
--- a/Manuals/Texinfo/Licenses/chapter-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/Manuals/Texinfo/Licenses/chapter.texinfo b/Manuals/Texinfo/Licenses/chapter.texinfo
deleted file mode 100755
index a20dbe8..0000000
--- a/Manuals/Texinfo/Licenses/chapter.texinfo
+++ /dev/null
@@ -1,6 +0,0 @@
-@node Licenses
-@chapter Licenses
-@cindex Licenses
-@include Licenses/chapter-intro.texinfo
-@include Licenses/chapter-menu.texinfo
-@include Licenses/chapter-nodes.texinfo
diff --git a/Manuals/Texinfo/en_US/Directories/branches.texinfo b/Manuals/Texinfo/en_US/Directories/branches.texinfo
new file mode 100755
index 0000000..e8639d1
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/branches.texinfo
@@ -0,0 +1,23 @@
+@subheading Goals
+
+This directory implements the Subversion's branches concept in a
+trunk, branches, tags repository structure.
+
+@subheading Description
+
+The @file{branches/} directory structure provides the intermediate
+space for creating several instances of @file{trunk/} directory
+structure for parallel development and later merging changes back to
+@file{trunk/} in the same parallel basis.
+
+@subheading Usage
+
+The @file{branches/} directory structure is unused, so far.
+
+@subheading See also
+
+@itemize
+@item @ref{Directories tags}.
+@item @ref{Directories trunk}.
+@item The Subversion book (@url{http://svnbook.red-bean.com/}).
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/chapter-intro.texinfo b/Manuals/Texinfo/en_US/Directories/chapter-intro.texinfo
new file mode 100644
index 0000000..52b15fa
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/chapter-intro.texinfo
@@ -0,0 +1,8 @@
+The CentOS Artwork Repository uses directories to organize files and
+describe conceptual idea about corporate identity. Such conceptual
+ideas are explained in each directory related documentation entry.
+
+In this chapter you'll learn what each directory inside The CentOS
+Artwork Repository is for and so, how you can make use of them. For
+that purpose, the following list of directories is available for you
+to explore:
diff --git a/Manuals/Texinfo/en_US/Directories/chapter-menu.texinfo b/Manuals/Texinfo/en_US/Directories/chapter-menu.texinfo
new file mode 100644
index 0000000..aad68c4
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/chapter-menu.texinfo
@@ -0,0 +1,49 @@
+@menu
+* Directories branches::
+* Directories tags::
+* Directories trunk::
+* Directories trunk Identity::
+* Directories trunk Identity Brushes::
+* Directories trunk Identity Fonts::
+* Directories trunk Identity Images::
+* Directories trunk Identity Images Themes::
+* Directories trunk Identity Images Themes Motifs::
+* Directories trunk Identity Images Themes Motifs Flame::
+* Directories trunk Identity Images Themes Motifs Modern::
+* Directories trunk Identity Images Themes Motifs Pipes::
+* Directories trunk Identity Images Themes Motifs TreeFlower::
+* Directories trunk Identity Models::
+* Directories trunk Identity Models Brands::
+* Directories trunk Identity Models Themes::
+* Directories trunk Identity Models Themes Default::
+* Directories trunk Identity Models Themes Default Concept::
+* Directories trunk Identity Models Themes Default Distro::
+* Directories trunk Identity Models Themes Default Distro 5::
+* Directories trunk Identity Models Themes Default Distro 5.5 Notes Release::
+* Directories trunk Identity Models Themes Default Distro 5 Anaconda::
+* Directories trunk Identity Models Themes Default Distro 5 Firstboot::
+* Directories trunk Identity Models Themes Default Distro 5 Gdm::
+* Directories trunk Identity Models Themes Default Distro 5 Grub::
+* Directories trunk Identity Models Themes Default Distro 5 Gsplash::
+* Directories trunk Identity Models Themes Default Distro 5 Kdm::
+* Directories trunk Identity Models Themes Default Distro 5 Ksplash::
+* Directories trunk Identity Models Themes Default Distro 5 Rhgb::
+* Directories trunk Identity Models Themes Default Distro 5 Syslinux::
+* Directories trunk Identity Models Themes Default Posters::
+* Directories trunk Identity Palettes::
+* Directories trunk Identity Patterns::
+* Directories trunk Identity Webenv::
+* Directories trunk Locales::
+* Directories trunk Manuals::
+* Directories trunk Manuals Directories::
+* Directories trunk Manuals Introduction::
+* Directories trunk Manuals Licenses::
+* Directories trunk Scripts::
+* Directories trunk Scripts Functions::
+* Directories trunk Scripts Functions Help::
+* Directories trunk Scripts Functions Help Backends::
+* Directories trunk Scripts Functions Locale::
+* Directories trunk Scripts Functions Prepare::
+* Directories trunk Scripts Functions Render::
+* Directories trunk Scripts Functions Tuneup::
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/chapter-nodes.texinfo b/Manuals/Texinfo/en_US/Directories/chapter-nodes.texinfo
new file mode 100644
index 0000000..a996a12
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/chapter-nodes.texinfo
@@ -0,0 +1,235 @@
+@node Directories branches
+@section The @file{branches} Directory
+@cindex Directories branches
+@include Directories/branches.texinfo
+
+@node Directories tags
+@section The @file{tags} Directory
+@cindex Directories tags
+@include Directories/tags.texinfo
+
+@node Directories trunk
+@section The @file{trunk} Directory
+@cindex Directories trunk
+@include Directories/trunk.texinfo
+
+@node Directories trunk Identity
+@section The @file{trunk/Identity} Directory
+@cindex Directories trunk Identity
+@include Directories/trunk/Identity.texinfo
+
+@node Directories trunk Identity Brushes
+@section The @file{trunk/Identity/Brushes} Directory
+@cindex Directories trunk Identity Brushes
+@include Directories/trunk/Identity/Brushes.texinfo
+
+@node Directories trunk Identity Fonts
+@section The @file{trunk/Identity/Fonts} Directory
+@cindex Directories trunk Identity Fonts
+@include Directories/trunk/Identity/Fonts.texinfo
+
+@node Directories trunk Identity Images
+@section The @file{trunk/Identity/Images} Directory
+@cindex Directories trunk Identity Images
+@include Directories/trunk/Identity/Images.texinfo
+
+@node Directories trunk Identity Images Themes
+@section The @file{trunk/Identity/Images/Themes} Directory
+@cindex Directories trunk Identity Images Themes
+@include Directories/trunk/Identity/Images/Themes.texinfo
+
+@node Directories trunk Identity Images Themes Motifs
+@section The @file{trunk/Identity/Images/Themes/Motifs} Directory
+@cindex Directories trunk Identity Images Themes Motifs
+@include Directories/trunk/Identity/Images/Themes/Motifs.texinfo
+
+@node Directories trunk Identity Images Themes Motifs Flame
+@section The @file{trunk/Identity/Images/Themes/Motifs/Flame} Directory
+@cindex Directories trunk Identity Images Themes Motifs Flame
+@include Directories/trunk/Identity/Images/Themes/Motifs/Flame.texinfo
+
+@node Directories trunk Identity Images Themes Motifs Modern
+@section The @file{trunk/Identity/Images/Themes/Motifs/Modern} Directory
+@cindex Directories trunk Identity Images Themes Motifs Modern
+@include Directories/trunk/Identity/Images/Themes/Motifs/Modern.texinfo
+
+@node Directories trunk Identity Images Themes Motifs Pipes
+@section The @file{trunk/Identity/Images/Themes/Motifs/Pipes} Directory
+@cindex Directories trunk Identity Images Themes Motifs Pipes
+@include Directories/trunk/Identity/Images/Themes/Motifs/Pipes.texinfo
+
+@node Directories trunk Identity Images Themes Motifs TreeFlower
+@section The @file{trunk/Identity/Images/Themes/Motifs/TreeFlower} Directory
+@cindex Directories trunk Identity Images Themes Motifs TreeFlower
+@include Directories/trunk/Identity/Images/Themes/Motifs/TreeFlower.texinfo
+
+@node Directories trunk Identity Models
+@section The @file{trunk/Identity/Models} Directory
+@cindex Directories trunk Identity Models
+@include Directories/trunk/Identity/Models.texinfo
+
+@node Directories trunk Identity Models Brands
+@section The @file{trunk/Identity/Models/Brands} Directory
+@cindex Directories trunk Identity Models Brands
+@include Directories/trunk/Identity/Models/Brands.texinfo
+
+@node Directories trunk Identity Models Themes
+@section The @file{trunk/Identity/Models/Themes} Directory
+@cindex Directories trunk Identity Models Themes
+@include Directories/trunk/Identity/Models/Themes.texinfo
+
+@node Directories trunk Identity Models Themes Default
+@section The @file{trunk/Identity/Models/Themes/Default} Directory
+@cindex Directories trunk Identity Models Themes Default
+@include Directories/trunk/Identity/Models/Themes/Default.texinfo
+
+@node Directories trunk Identity Models Themes Default Concept
+@section The @file{trunk/Identity/Models/Themes/Default/Concept} Directory
+@cindex Directories trunk Identity Models Themes Default Concept
+@include Directories/trunk/Identity/Models/Themes/Default/Concept.texinfo
+
+@node Directories trunk Identity Models Themes Default Distro
+@section The @file{trunk/Identity/Models/Themes/Default/Distro} Directory
+@cindex Directories trunk Identity Models Themes Default Distro
+@include Directories/trunk/Identity/Models/Themes/Default/Distro.texinfo
+
+@node Directories trunk Identity Models Themes Default Distro 5
+@section The @file{trunk/Identity/Models/Themes/Default/Distro/5} Directory
+@cindex Directories trunk Identity Models Themes Default Distro 5
+@include Directories/trunk/Identity/Models/Themes/Default/Distro/5.texinfo
+
+@node Directories trunk Identity Models Themes Default Distro 5.5 Notes Release
+@section The @file{trunk/Identity/Models/Themes/Default/Distro/5.5/Notes/Release} Directory
+@cindex Directories trunk Identity Models Themes Default Distro 5.5 Notes Release
+@include Directories/trunk/Identity/Models/Themes/Default/Distro/5.5/Notes/Release.texinfo
+
+@node Directories trunk Identity Models Themes Default Distro 5 Anaconda
+@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Anaconda} Directory
+@cindex Directories trunk Identity Models Themes Default Distro 5 Anaconda
+@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Anaconda.texinfo
+
+@node Directories trunk Identity Models Themes Default Distro 5 Firstboot
+@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Firstboot} Directory
+@cindex Directories trunk Identity Models Themes Default Distro 5 Firstboot
+@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Firstboot.texinfo
+
+@node Directories trunk Identity Models Themes Default Distro 5 Gdm
+@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Gdm} Directory
+@cindex Directories trunk Identity Models Themes Default Distro 5 Gdm
+@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gdm.texinfo
+
+@node Directories trunk Identity Models Themes Default Distro 5 Grub
+@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Grub} Directory
+@cindex Directories trunk Identity Models Themes Default Distro 5 Grub
+@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Grub.texinfo
+
+@node Directories trunk Identity Models Themes Default Distro 5 Gsplash
+@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Gsplash} Directory
+@cindex Directories trunk Identity Models Themes Default Distro 5 Gsplash
+@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gsplash.texinfo
+
+@node Directories trunk Identity Models Themes Default Distro 5 Kdm
+@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Kdm} Directory
+@cindex Directories trunk Identity Models Themes Default Distro 5 Kdm
+@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Kdm.texinfo
+
+@node Directories trunk Identity Models Themes Default Distro 5 Ksplash
+@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Ksplash} Directory
+@cindex Directories trunk Identity Models Themes Default Distro 5 Ksplash
+@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Ksplash.texinfo
+
+@node Directories trunk Identity Models Themes Default Distro 5 Rhgb
+@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Rhgb} Directory
+@cindex Directories trunk Identity Models Themes Default Distro 5 Rhgb
+@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Rhgb.texinfo
+
+@node Directories trunk Identity Models Themes Default Distro 5 Syslinux
+@section The @file{trunk/Identity/Models/Themes/Default/Distro/5/Syslinux} Directory
+@cindex Directories trunk Identity Models Themes Default Distro 5 Syslinux
+@include Directories/trunk/Identity/Models/Themes/Default/Distro/5/Syslinux.texinfo
+
+@node Directories trunk Identity Models Themes Default Posters
+@section The @file{trunk/Identity/Models/Themes/Default/Posters} Directory
+@cindex Directories trunk Identity Models Themes Default Posters
+@include Directories/trunk/Identity/Models/Themes/Default/Posters.texinfo
+
+@node Directories trunk Identity Palettes
+@section The @file{trunk/Identity/Palettes} Directory
+@cindex Directories trunk Identity Palettes
+@include Directories/trunk/Identity/Palettes.texinfo
+
+@node Directories trunk Identity Patterns
+@section The @file{trunk/Identity/Patterns} Directory
+@cindex Directories trunk Identity Patterns
+@include Directories/trunk/Identity/Patterns.texinfo
+
+@node Directories trunk Identity Webenv
+@section The @file{trunk/Identity/Webenv} Directory
+@cindex Directories trunk Identity Webenv
+@include Directories/trunk/Identity/Webenv.texinfo
+
+@node Directories trunk Locales
+@section The @file{trunk/Locales} Directory
+@cindex Directories trunk Locales
+@include Directories/trunk/Locales.texinfo
+
+@node Directories trunk Manuals
+@section The @file{trunk/Manuals} Directory
+@cindex Directories trunk Manuals
+@include Directories/trunk/Manuals.texinfo
+
+@node Directories trunk Manuals Directories
+@section The @file{trunk/Manuals/Directories} Directory
+@cindex Directories trunk Manuals Directories
+@include Directories/trunk/Manuals/Directories.texinfo
+
+@node Directories trunk Manuals Introduction
+@section The @file{trunk/Manuals/Introduction} Directory
+@cindex Directories trunk Manuals Introduction
+@include Directories/trunk/Manuals/Introduction.texinfo
+
+@node Directories trunk Manuals Licenses
+@section The @file{trunk/Manuals/Licenses} Directory
+@cindex Directories trunk Manuals Licenses
+@include Directories/trunk/Manuals/Licenses.texinfo
+
+@node Directories trunk Scripts
+@section The @file{trunk/Scripts} Directory
+@cindex Directories trunk Scripts
+@include Directories/trunk/Scripts.texinfo
+
+@node Directories trunk Scripts Functions
+@section The @file{trunk/Scripts/Functions} Directory
+@cindex Directories trunk Scripts Functions
+@include Directories/trunk/Scripts/Functions.texinfo
+
+@node Directories trunk Scripts Functions Help
+@section The @file{trunk/Scripts/Functions/Help} Directory
+@cindex Directories trunk Scripts Functions Help
+@include Directories/trunk/Scripts/Functions/Help.texinfo
+
+@node Directories trunk Scripts Functions Help Backends
+@section The @file{trunk/Scripts/Functions/Help/Backends} Directory
+@cindex Directories trunk Scripts Functions Help Backends
+@include Directories/trunk/Scripts/Functions/Help/Backends.texinfo
+
+@node Directories trunk Scripts Functions Locale
+@section The @file{trunk/Scripts/Functions/Locale} Directory
+@cindex Directories trunk Scripts Functions Locale
+@include Directories/trunk/Scripts/Functions/Locale.texinfo
+
+@node Directories trunk Scripts Functions Prepare
+@section The @file{trunk/Scripts/Functions/Prepare} Directory
+@cindex Directories trunk Scripts Functions Prepare
+@include Directories/trunk/Scripts/Functions/Prepare.texinfo
+
+@node Directories trunk Scripts Functions Render
+@section The @file{trunk/Scripts/Functions/Render} Directory
+@cindex Directories trunk Scripts Functions Render
+@include Directories/trunk/Scripts/Functions/Render.texinfo
+
+@node Directories trunk Scripts Functions Tuneup
+@section The @file{trunk/Scripts/Functions/Tuneup} Directory
+@cindex Directories trunk Scripts Functions Tuneup
+@include Directories/trunk/Scripts/Functions/Tuneup.texinfo
+
diff --git a/Manuals/Texinfo/en_US/Directories/chapter.texinfo b/Manuals/Texinfo/en_US/Directories/chapter.texinfo
new file mode 100644
index 0000000..ce2ff93
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/chapter.texinfo
@@ -0,0 +1,6 @@
+@node Directories
+@chapter The Repository Directories
+@cindex Repository directories
+@include Directories/chapter-intro.texinfo
+@include Directories/chapter-menu.texinfo
+@include Directories/chapter-nodes.texinfo
diff --git a/Manuals/Texinfo/en_US/Directories/tags.texinfo b/Manuals/Texinfo/en_US/Directories/tags.texinfo
new file mode 100755
index 0000000..609583a
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/tags.texinfo
@@ -0,0 +1,24 @@
+@subheading Goals
+
+This directory implements the Subversion's tags concept in a trunk,
+branches, tags repository structure.
+
+@subheading Description
+
+The @file{tags/} directory structure provides frozen branches.
+Generally, we use frozen branches to make check-points in time for
+development lines under @file{branches/} or @file{trunk/} directory
+structure.
+
+@subheading Usage
+
+The @file{tags/} directory structure is unused, so far.
+
+@subheading See also
+
+@itemize
+@item @ref{Directories branches}.
+@item @ref{Directories trunk}.
+@item The subversion book (@url{http://svnbook.red-bean.com/}).
+@end itemize
+
diff --git a/Manuals/Texinfo/en_US/Directories/trunk.texinfo b/Manuals/Texinfo/en_US/Directories/trunk.texinfo
new file mode 100644
index 0000000..a7ea8d1
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk.texinfo
@@ -0,0 +1,26 @@
+@subheading Goals
+
+The @file{trunk/} directory structure implements the Subversion's
+trunk concept in a trunk, branches, tags repository structure.
+
+@subheading Description
+
+The @file{trunk/} directory structure provides the main development
+line inside the CentOS Artwork Repository.
+
+@subheading Usage
+
+@itemize
+@item @xref{Directories trunk Identity}.
+@item @xref{Directories trunk Manuals}.
+@item @xref{Directories trunk Locales}.
+@item @xref{Directories trunk Scripts}.
+@end itemize
+
+@subheading See also
+
+@itemize
+@item @ref{Directories branches}.
+@item @ref{Directories tags}.
+@item The Subversion book (@url{http://svnbook.red-bean.com/}).
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity.texinfo
new file mode 100644
index 0000000..eca5563
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity.texinfo
@@ -0,0 +1,279 @@
+@subheading Goals
+
+The @file{trunk/Identity} describes what The CentOS Project Corporate
+Identity is and the components it is made of.
+
+@subheading Description
+
+The CentOS Project Corporate Identity is the ``persona'' of the
+organization known as The CentOS Project. The CentOS Project
+Corporate Identity plays a significant role in the way The CentOS
+Project, as organization, presents itself to both internal and
+external stakeholders. In general terms, The CentOS Project Corporate
+Identity expresses the values and ambitions of The CentOS Project
+organization, its business, and its characteristics.
+
+The CentOS Project Corporate Identity provides visibility,
+recognizability, reputation, structure and identification to The
+CentOS Project organization by means of @emph{Corporate Design},
+@emph{Corporate Communication}, and @emph{Corporate Behaviour}.
+
+@image{trunk/Identity/Images/Manual/Corporate/monolithic,450pt,,,jpg}
+
+@subsubheading Corporate Mission
+
+The CentOS Project exists to provide The CentOS Distribution.
+Additionally, The CentOS Project provides The CentOS Web and The
+CentOS Showroom to support and promote the existence of The CentOS
+Distribution, respectively.
+
+@subsubheading Corporate Design
+
+Corporate design is focused on the effective communication of
+corporate visual messages. Corporate visual messages are all the
+information emitted by a corporation that can be perceived by the
+people through their visual sence (i.e., the human eye). In order for
+such visual communication to happen, it is required to put the visual
+message on medium available for people to see. These kind of media
+are know as corporate visual manifestations, since the corporate
+manifests its existence through them using corporate design.
+
+The amount of visual manifestations a corporation uses to communicate
+its existence is very specific to each corporation itself. Inside The
+CentOS Project Corporate Identity, considering @emph{The CentOS
+Project Corporate Structure}, @emph{The CentOS Project Corporate
+Mission} and @emph{The CentOS Project Release Schema}, the following
+visual manifestations were defined:
+
+@table @strong
+@item The CentOS Distribution
+
+The CentOS Distribution visual manifestation exists to cover all
+actions related to artwork production and rebranding required by the
+The CentOS Distribution (--- @strong{Removed}(pxref:Directories trunk Identity Images Themes
+Models Default Distro) ---) in order to comply with its upstream
+redistribution guidelines.
+
+The CentOS Distribution is made of software packages. Inside the
+distribution there are packages that make a remarkable use of images
+and there are packages that don't use images at all. The CentOS
+Distribution visual manifestation gets focused on software packages
+that do use images in a remarkable way (e.g., @file{anaconda},
+@file{grub}, @file{syslinux}, @file{gdm}, @file{kdm}) and that way,
+through images, implements the corporate design in The CentOS
+Distribution (i.e., the operating system).
+
+@item The CentOS Web
+
+The CentOS Web visual manifestation exists to support The CentOS
+Distribution.
+
+The CentOS Web covers web applications which let The CentOS Project to
+manifest its existence on the Internet. Through these web applications
+The CentOS Project provides Corporate Communication. These web
+applications are free software and come from different providers which
+distribute their work with predefined visual styles. Frequently,
+these predefined visual styles have no visual relation among
+themselves and introduce some visual contraditions when they all are
+put together. These visual contraditions need to be removed in order
+to comply with The CentOS Project Corporate Structure guidelines.
+
+@item The CentOS Showroom
+
+The CentOS Showroom visual manifestation exists to promote The CentOS
+Distribution.
+
+The CentOS Showroom covers industrial production of objects branded by
+The CentOS Project (e.g., clothes, stationery and installation media).
+These branded objects are for distribution on social events and/or
+shops. They provide a way of promotion and a route for
+commercialization that may help to aliviate The CentOS Project
+expenses (e.g., electrical power, hosting, servers,
+full-time-developers, etc.), in a similar way as donations may do.
+
+@end table
+
+The visual manifestations above seem to cover all the media required
+by The CentOS Project, as organization, to show its existence.
+However, other visual manifestations could be added in the future, if
+needed, to cover different areas like building, offices, road
+transportation and whaterver visual manifestation The CentOS Project
+thouches to show its existence.
+
+@subsubheading Corporate Communication
+
+The CentOS Project Corporate Communication is based on @emph{Community
+Communication} and takes place through the following avenues:
+
+@itemize
+@item The CentOS Chat (@code{#centos}, @code{#centos-social},
+@code{#centos-devel} on irc.freenode.net)
+@item The CentOS Mailing Lists (@url{http://lists.centos.org/}).
+@item The CentOS Forums (@url{http://forums.centos.org/}).
+@item The CentOS Wiki (@url{http://wiki.centos.org/}).
+@item Social events, interviews, conferences, etc.
+@end itemize
+
+@subsubheading Corporate Behaviour
+
+The CentOS Project Corporate Behaviour is based on @emph{Community
+Behaviour} which take place on @emph{Corporate Communication}.
+
+@subsubheading Corporate Structure
+
+The CentOS Project Corporate Structure is based on a @emph{Monolithic
+Corporate Visual Identity Structure}. In this configuration, one
+unique name and one unique visual style is used in all visual
+manifestation of The CentOS Project.
+
+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: @emph{Hey! we are all part of The CentOS
+Project}.
+
+Other corporate structures for The CentOS Project have been considered
+as well. Such is the case of producing one different visual style for
+each major release of The CentOS Distribution. This structure isn't
+inconvenient at all, but some visual contradictions could be
+introduced if it isn't applied correctly and we need to be aware of
+it. To apply it correctly, we need to know what The CentOS Project is
+made of.
+
+The CentOS Project, as organization, is mainly made of (but not
+limited to) three visual manifestions: Distribution, Web and Showroom.
+Inside the Distribution visual manifestations, The CentOS Project
+maintains near to four different major releases of CentOS
+Distribution, parallely in time. However, inside The CentOS Web
+visual manifestations, the content is produced for no specific release
+information (e.g., there is no a complete web site for each major
+release of The CentOS Distribution individually, but one web site to
+cover them all). Likewise, the content produced in The CentOS Showroom
+is created for no release-specific at all, but for The CentOS Project
+in general.
+
+In order to produce the correct corporate structure for The CentOS
+Project we need to concider all the visual manifestations The CentOS
+Project is made of, not just one of them. If one different visual
+style is used for each major release of The CentOS Distribution, which
+one of those different visual styles would be used to cover the
+remaining visual manifestations The CentOS Project is made of (e.g.,
+The CentOS Web and The CentOS Showroom)?
+
+Probably you are thinking, that's right, but The CentOS Brand connects
+them all already, why would we need to join them up into the same
+visual style too, isn't it more work to do, and harder to maintain?
+
+Harder to maintain, more work to do, probably. Specially when you
+consider that The CentOS Project has proven stability and consistency
+through time and, that, certainly, didn't come through swinging
+magical wands or something but hardly working out to automate tasks
+and providing maintainance through time. Said that, we consider that
+The CentOS Project Corporate Structure must be consequent with such
+stability and consistency tradition. It is true that The CentOS Brand
+does connect all the visual manifestations it is present on, but that
+connection would be stronger if one unique visual style backups it.
+In fact, whatever thing you do to strength the visual connection among
+The CentOS Project visual manifestations would be very good in favor
+of The CentOS Project recognition.
+
+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 The CentOS Distribution, in
+order to refresh The CentOS Distribution visual style; the problem
+itself is in not propagating the brand new visual style created for
+the new release of The CentOS Distribution to all other visual
+manifestations The CentOS Project is made of, in a way The CentOS
+Project could be recognized no matter what 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 the CentOS Artwork Repository.
+
+@subheading Usage
+
+The @file{trunk/Identity} directory structure organizes most files
+used to build and implement The CentOS Project Corporate Identity. In
+that sake, the following work lines are available:
+
+@table @strong
+
+@item Brushes
+
+This work line provides brushes for GIMP. When you prepare the
+repository, brushes in this location are made available immediatly for
+you to use in the ``Brushes'' panel of GIMP.
+
+@xref{Directories trunk Identity Brushes}, for more
+information.
+
+@item Fonts
+
+This work line provides the typography information required by all
+different visual manifestations of The CentOS Project. When you
+prepare the repository, fonts in this location are made available
+immediatly for you to use in GIMP and Inkscape.
+
+@xref{Directories trunk Identity Fonts}, for more information.
+
+@item Images
+
+This work line provides output location for final images that don't
+need to use background images (e.g., brands, icons, illustrations,
+etc.).
+
+@xref{Directories trunk Identity Images}, for more information.
+
+@item Models
+
+This work line provides design models for final images that don't need
+to use background images (e.g., brands, icons, illustrations, etc.).
+
+@xref{Directories trunk Identity Models}, for more information.
+
+@item Palettes
+
+This work line provides palettes of colors for GIMP and Inkscape. When
+you prepare the repository, palettes of colors in this location are
+made available immediatly for you to use in the ``Palettes'' panel of
+GIMP and Inkscape.
+
+@xref{Directories trunk Identity Palettes}, for more information.
+
+@item Patterns
+
+This work line provides patterns for GIMP. When you prepare the
+repository, patterns in this location are made available immediatly
+for you to use in the ``Patterns'' panel of GIMP.
+
+@xref{Directories trunk Identity Patterns}, for more information.
+
+@item Themes
+
+This work line provides theme design models and theme artistic motifs
+for The CentOS Project. If you are interested in creating brand new
+visual styles for The CentOS Project this is the place for you.
+
+@xref{Directories trunk Identity Images Themes}, for more information.
+
+@item Webenv
+
+This work line provides the HTML/XHTML and CSS standard definitions
+used by The CentOS Web visual manifestation. If you are a web
+developer and plan to improve The CentOS Web visual manifestation,
+then the files in this location may result very useful to you.
+
+@xref{Directories trunk Identity Webenv}, for more information.
+@end table
+
+@subheading See also
+
+See @url{http://en.wikipedia.org/Corporate_identity} (and related
+links), for general information on Corporate Identity.
+
+Specially useful has been, and still is, the book @emph{Corporate
+Identity} by Wally Olins (1989). This book provides many of the
+conceptual ideas we've used as base to build The CentOS Artwork
+Repository.
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Brushes.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Brushes.texinfo
new file mode 100755
index 0000000..0d046e0
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Brushes.texinfo
@@ -0,0 +1,135 @@
+@subheading Goals
+
+This section describes how brushes are organized in the repository and
+how to make them available for you to use in @acronym{GIMP,GNU Image
+Manipulation Program}.
+
+@subheading Description
+
+A brush is a pixmap or set of pixmaps used for painting through an
+image manipulation program like GIMP. Inside the repository, we've
+organized brushes in @emph{common brushes} and @emph{theme-specific
+brushes}. In both cases, 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.
+
+@verbatim
+1. Common brushes 2. Theme-specific brushes
+---------------------- -----------------------------------------------------------
+trunk/Identity/Brushes trunk/Identity/Images/Themes/THEMENAME/THEMEVERSION/Brushes
+|-- Xcf |-- Xcf
+| |-- 1.xcf | |-- 1.xcf
+| |-- 2.xcf | |-- 2.xcf
+| `-- 3.xcf | `-- 3.xcf
+|-- 1.gbr |-- 1.gbr
+|-- 2.gih |-- 2.gih
+`-- 3.gbr `-- 3.gbr
+@end verbatim
+
+In order for both common brushes and theme-specific brushes to be
+loaded by GIMP, related @file{.gbr} and @file{.gih} brush files need
+to be stored under @file{~/.gimp-2.2/brushes} directory. This location
+is out of CentOS Artwork Repository and provides no version control by
+itself. This way, brushes aren't exported to this location but into
+the repository directory structure which is versioned. Later, we
+create symbolic links in @file{~/.gimp-2.2/brushes} to connect file
+brushes inside the repository and, this way, provide the configuration
+needed by GIMP to use the brush files produced inside the repository.
+
+@quotation
+@strong{Warning}
+When brushes are added to or removed from the repository, you need to
+update your working copy and all information related to brushes inside
+your workstation (e.g., brush links in @file{~/.gimp-2.2/brushes} and
+the Brushes panel in GIMP). Otherwise, you may end up with broken
+links or brushes in the repository that wouldn't be available for you
+to use in GIMP.
+@end quotation
+
+Inside the repository, common brushes and theme-specific brushes are
+created individually in different locations, but they all are linked
+from one unique location (i.e., @file{~/.gimp-2.2/brushes}). This
+configuration may provoke brush overlapping if a name convenction is
+not implemented correctly. In that sake, file names used for brushes
+inside the repository must be unique, no matter where they be.
+
+As file name convenction inside the repository, brushes are named
+using lowercase letters, numbers, minus characters and dot characters,
+only. Additionally, when links are built, we use one suffix for those
+brushes retrived from @file{trunk/Identity/Brushes} and another suffix
+for those brushes retrivided from theme-specific directories. Using
+both the brush file name and the suffix information, it is possible
+to build unique names for links under @file{~/.gimp-2.2/brushes}
+directory, scalably.
+
+@verbatim
+trunk/Identity/Brushes
+|-- 1.gbr (file) <-- ~/.gimp-2.2/brushes/centos-1.gbr (link)
+|-- 2.gbr (file) <-- ~/.gimp-2.2/brushes/centos-2.gbr (link)
+`-- 3.gbr (file) <-- ~/.gimp-2.2/brushes/centos-3.gbr (link)
+@end verbatim
+
+@verbatim
+trunk/Identity/Images/Themes/THEMENAME/THEMEVERSION/Brushes
+|-- 1.gbr (file) <-- ~/.gimp-2.2/brushes/centos-THEMENAME-THEMEVERSION-1.gbr (link)
+|-- 2.gbr (file) <-- ~/.gimp-2.2/brushes/centos-THEMENAME-THEMEVERSION-2.gbr (link)
+`-- 3.gbr (file) <-- ~/.gimp-2.2/brushes/centos-THEMENAME-THEMEVERSION-3.gbr (link)
+@end verbatim
+
+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, we
+use the same name schema used to name brush links 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}).
+
+@subheading Usage
+
+The way you use brushes is up to your creativeness. However, the way
+brushes are made available needs to be standardized. That's the reason
+of organizing brushes in common brushes and theme-specific brushes.
+
+@subheading Common brushes
+
+Common brushes exist to organize brushes that can be used anywhere
+inside the repository. Inside the repository, common brushes under
+@file{trunk/Identity/Brushes} are mainly used to hold brand
+information related to The CentOS Project (e.g., symbols, logos,
+trademarks, etc.).
+
+Common brushes are always made available under
+@file{~/.gimp-2.2/brushes} directory after preparing the repository
+(@pxref{Directories trunk Scripts Functions Prepare}).
+
+@subheading Theme-specific brushes
+
+Theme-specific brushes exist to organize brushes that can be used
+inside specific artistic motifs only. Inside the repository,
+theme-specific brushes are stored in a directory named @file{Brushes}
+which is stored in the first directory level under the artistic motif
+directory structure. Each artistic motif inside the repository has its
+own @file{Brushes} directory and uses it to store brushes that can be
+considered auxiliars to that artistic motif construction.
+
+Theme-specific brushes aren't made available under
+@file{~/.gimp-2.2/brushes} directory after preparing the repository.
+In order to make theme-specific brushes available under
+@file{~/.gimp-2.2./brushes} it is required to activate/deactivate them
+using the @code{theme} functionality of @command{centos-art.sh}
+script. @c (@pxref{Directories trunk Scripts Functions Theme}).
+
+@subheading See also
+
+@itemize
+@item @url{file:///usr/share/gimp/2.0/help/en/index.html,The Gimp
+Manual}, specifically the section related to
+@url{file:///usr/share/gimp/2.0/help/en/gimp-concepts-brushes.html,
+Brushes}.
+@item @ref{Directories trunk Identity}
+@item @ref{Directories trunk}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Fonts.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Fonts.texinfo
new file mode 100644
index 0000000..ea4b08b
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Fonts.texinfo
@@ -0,0 +1,44 @@
+@subheading Goals
+
+This section describes how typographies are organized in the
+repository and how to make them available for you to use in
+@acronym{GIMP,GNU Image Manipulation Program} and Inkscape.
+
+@subheading Description
+
+The CentOS Project Corporate Identity is attached to @samp{DejaVu LGC}
+font-family and @samp{Denmark} font-family.
+
+@image{trunk/Identity/Images/Manual/Fonts/dejavu-lgc,430pt,,,jpg}
+
+@image{trunk/Identity/Images/Manual/Fonts/denmark,430pt,,,jpg}
+
+@quotation
+@strong{Caution}
+The copyright and license of @samp{Denmark} typography aren't very
+specific and that issue may represent a threat to The CentOS Project
+Corporate Identity.
+@end quotation
+
+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). If the typography used
+to build The CentOS Logo is compromised somehow, the whole corporate
+visual identity it represents would be compromised, as well. To
+prevent such issues, it would be better for The CentOS Project to move
+on from @samp{Denmark} typography to another typography (free,
+preferably) that retain the same visual style of @samp{Denmark}, but
+intruce a clearer copyright and license notice.
+
+@subheading Usage
+
+@itemize
+@item @xref{Directories trunk Identity Models Brands}.
+@end itemize
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk Identity}.
+@item @ref{Directories trunk}.
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images.texinfo
new file mode 100755
index 0000000..cbc5503
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images.texinfo
@@ -0,0 +1,24 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk Identity}
+@item @ref{Directories trunk}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes.texinfo
new file mode 100644
index 0000000..0bf7e5d
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes.texinfo
@@ -0,0 +1,89 @@
+@subheading Goals
+
+The @file{trunk/Identity/Themes/} directory exists to organize
+production of CentOS themes.
+
+@subheading Description
+
+Initially, we start working themes on their trunk development line
+(e.g., @file{trunk/Identity/Images/Themes/TreeFlower/}), here we
+organize information that cannot be produced automatically (i.e.,
+background images, concepts, color information, screenshots, etc.).
+
+Later, when theme trunk development line is considered ``ready'' for
+implementation (e.g., all required backgrounds have been designed),
+we create a branch for it (e.g.,
+@file{branches/Identity/Images/Themes/TreeFlower/1/}). Once the
+branch has been created, we forget that branch and continue working
+the trunk development line while others (e.g., an artwork quality
+assurance team) test the new branch for tunning it up.
+
+Once the branch has been tunned up, and considered ``ready'' for
+release, it is freezed under @file{tags/} directory (e.g.,
+@file{tags/Identity/Images/Themes/TreeFower/1.0/}) for packagers,
+webmasters, promoters, and anyone who needs images from that CentOS
+theme the tag was created for.
+
+Both branches and tags, inside CentOS Artwork Repository, use
+numerical values to identify themselves under the same location.
+Branches start at one (i.e., @samp{1}) and increment one unit for each
+branch created from the same trunk development line. Tags start at
+zero (i.e., @samp{0}) and increment one unit for each tag created from
+the same branch development line.
+
+@quotation
+@strong{Convenction} Do not freeze trunk development lines using tags
+directly. If you think you need to freeze a trunk development line,
+create a branch for it and then freeze that branch instead.
+@end quotation
+
+The trunk development line may introduce problems we cannot see
+immediatly. Certainly, the high changable nature of trunk development
+line complicates finding and fixing such problems. On the other hand,
+the branched development lines provide a more predictable area where
+only fixes/corrections to current content are commited up to
+repository.
+
+If others find and fix bugs inside the branched development line, we
+could merge such changes/experiences back to trunk development line
+(not visversa) in order for future branches, created from trunk, to
+benefit.
+
+Time intervals used to create branches and tags may vary, just as
+different needs may arrive. For example, consider the release schema
+of CentOS distribution: one major release every 2 years, security
+updates every 6 months, support for 7 years long. Each time a CentOS
+distribution is released, specially if it is a major release, there is
+a theme need in order to cover CentOS distribution artwork
+requirements. At this point, is where CentOS Artwork Repository comes
+up to scene.
+
+Before releasing a new major release of CentOS distribution we create
+a branch for one of several theme development lines available inside
+the CentOS Artwork Repository, perform quality assurance on it, and
+later, freeze that branch using tags. Once a the theme branch has been
+frozen (under @file{tags/} directory), CentOS Packagers (the persons
+whom build CentOS distribution) can use that frozen branch as source
+location to fulfill CentOS distribution artwork needs. The same
+applies to CentOS Webmasters (the persons whom build CentOS websites),
+and any other visual manifestation required by the project.
+
+@subheading Usage
+
+In this location themes are organized in ``Models'' ---to store common
+information--- and ``Motifs''---to store unique information. At
+rendering time, both motifs and models are combined to produce the
+final CentOS themes. CentOS themes can be tagged as ``Default'' or
+``Alternative''. CentOS themes are maintained by CentOS community.
+
+@itemize
+@item @xref{Directories trunk Identity Models Themes}.
+@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Motifs) ---.
+@end itemize
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk Identity}.
+@item @ref{Directories trunk}.
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs.texinfo
new file mode 100644
index 0000000..85ff9ea
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs.texinfo
@@ -0,0 +1,165 @@
+@subheading Goals
+
+The @file{trunk/Identity/Images/Themes} directory exists to:
+
+@itemize
+@item Organize CentOS themes' artistic motifs.
+@end itemize
+
+@subheading Description
+
+The artistic motif of theme is a graphic design component that
+provides the visual style of themes, it is used as pattern to connect
+all visual manifestations inside one unique theme.
+
+Artistic motifs are based on conceptual ideas. Conceptual ideas bring
+the motivation, they are fuel for the engines of human imagination.
+Good conceptual ideas may produce good motivation to produce almost
+anything, and art works don't escape from it.
+
+@table @samp
+@item TreeFlower
+CentOS like trees, has roots, trunk, branches, leaves and flowers. Day
+by day they work together in freedom, ruled by the laws of nature and
+open standards, to show the beauty of its existence.
+@item Modern
+Modern, squares and circles flowing up.
+@end table
+
+If you have new conceptual ideas for CentOS, then you can say that you
+want to create a new artistic motif for CentOS. To create a new
+artistic motif you need to create a directory under
+@file{Identity/Images/Themes/} using a name coherent with your
+conceptual idea. That name will be the name of your artistic motif. If
+possible, when creating new conceptual ideas for CentOS, think about
+what CentOS means for you, what does it makes you feel, take your
+time, think deep, and share; you can improve the idea as time goes on.
+
+Once you have defined a name for your theme, you need to create the
+motif structure of your theme. The motif structure is the basic
+direcotry structure you'll use to work your ideas. Here is where you
+organize your graphic design projects.
+
+To add a new motif structure to CentOS Artwork Repository, you need to
+use the @command{centos-art} command line in the
+@file{Identity/Images/Themes/} directory as described below:
+
+@example
+centos-art add --motif=ThemeName
+@end example
+
+The previous command will create the basic structure of themes for
+you. The basic structure produced by @command{centos-art} command is
+illustrated in the following figure:
+
+@example
+trunk/Identity/Images/Themes/$ThemeName/
+|-- Backgrounds
+| |-- Img
+| `-- Tpl
+|-- Info
+| |-- Img
+| `-- Tpl
+|-- Palettes
+`-- Screenshots
+@end example
+
+@subheading Usage
+
+When designing artistic motifs for CentOS, consider the following
+recommendations:
+
+@itemize
+@item Give a unique (case-sensitive) name to your Motif. This name is
+used as value wherever theme variable (@b{$THEME}) or translation marker
+(@b{=THEME=}) is. Optionally, you can add a description about
+inspiration and concepts behind your work.
+
+@item Use the location @file{trunk/Identity/Images/Themes/$THEME/} to
+store your work. If it doesn't exist create it. Note that this require
+you to have previous commit access in CentOS Artwork Repository.
+
+@item The CentOS Project is using the blue color (@b{#204c8d}) as base
+color for its corporate visual identity. Use such base corporate color
+information as much as possible in your artistic motif designs.
+
+@item Try to make your design fit one of the theme models.
+
+@item Feel free to make your art enterprise-level and beautiful.
+
+@item Add the following information on your artwork (both in a visible
+design area and document metadata):
+
+@itemize
+
+@item The name (or logo) of your artistic motif.
+
+@item The copyright sentence: @b{Copyright (C) YEAR YOURNAME}
+
+@item The license under which the work is released. All CentOS Art
+works are released under
+@url{http://creativecommons.org/licenses/by-sa/3.0/,Creative Common
+Share-Alike License 3.0}
+(@url{http://creativecommons.org/licenses/by-sa/3.0/}).
+
+@end itemize
+@end itemize
+
+@subheading See also
+
+@menu
+* Directories trunk Identity Images Themes::
+* Directories trunk Identity::
+* Directories trunk::
+@end menu
+
+The @file{Backgrounds/} directory is used to organize artistic motif
+background images and the projects used to build those images.
+
+Background images are linked (using the @b{import} feature of
+Inkscape) inside almost all theme art works. This structure let you
+make centralized changes on the visual identity and propagate them
+quickly to other areas.
+
+In this configuration you design background images for different
+screen resolutions based on the theme artistic motif.
+
+You may create different artistic motifs propositions based
+on the same conceptual idea. The conceptual idea is what defines a
+theme. Artistic motifs are interpretations of that idea.
+
+Inside this directory artistic motifs are organized by name (e.g.,
+TreeFlower, Modern, etc.).
+
+Each artistic motif directory represents just one unique artistic
+motif.
+
+The artistic motif is graphic design used as common pattern to connect
+all visual manifestations inside one unique theme. The artistic motif
+is based on a conceptual idea. Artistic motifs provide visual style
+to themes.
+
+Designing artistic motifs is for anyone interested in creating
+beautiful themes for CentOS. When building a theme for CentOS, the
+first design you need to define is the artistic motif.
+
+Inside CentOS Artwork Repository, theme visual styles (a.k.a.,
+artistic motifs) and theme visual structures (a.k.a., design models)
+are two different working lines. When you design an artistic motif
+for CentOS you concentrate on its visual style, and eventualy, use the
+@command{centos-art} command line interface to render the visual
+style, you are currently producing, against an already-made theme
+model in order to produce the final result. Final images are stored
+under @file{Motifs/} directory using the model name, and the model
+directory structure as reference.
+
+The artistic motif base structure is used by @command{centos-art} to
+produce images automatically. This section describes each directory of
+CentOS artistic motif base structure.
+
+The @file{Backgrounds/} directory is probably the core component,
+inside @file{Motifs/} directory structure. Inside @file{Backgrounds/}
+directory you produce background images used by almost all theme
+models (e.g., Distribution, Websites, Promotion, etc.). The
+@file{Backgrounds/} directory can contain subdirectories to help you
+organize the design process.
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs/Flame.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs/Flame.texinfo
new file mode 100644
index 0000000..3cfae8b
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs/Flame.texinfo
@@ -0,0 +1,120 @@
+@subheading Goals
+
+This section describes the @emph{Flame} artistic motif. This section
+may be useful for anyone interested in reproducing the @emph{Flame}
+artistic motif, or in creating new artistic motifs for The CentOS
+Project corporate visual identity.
+
+@subheading Description
+
+The @emph{Flame} artistic motif was built using the flame filter of
+Gimp 2.2 in CentOS 5.5.
+
+The flame filter of Gimp can produce stunning, randomly generated
+fractal patterns. The flame filter of Gimp gives us a great oportunity
+to reduce the time used to produce new artistic motifs, because of its
+``randomly generated'' nature. Once the artistic motif be created, it
+is propagated through all visual manifestations of CentOS Project
+corporate visual identity using the @file{centos-art.sh} script
+(@pxref{Directories trunk Scripts}) inside the CentOS Artwork
+Repository.
+
+To set the time intervals between each new visual style production, we
+could reuse the CentOS distribution major release schema. I.e., we
+could produce a new visual style, every two years, based on a new
+``randomly generated'' flame pattern, and publish the whole corporate
+visual identity (i.e., distribution stuff, promotion stuff, websites
+stuff, etc.) with the new major release of CentOS distribution all
+together at once.
+
+Producing a new visual style is not one day's task. Once we have
+defined the artistic motif, we need to propagate it through all visual
+manifestations of The CentOS Project corporate visual identity. When
+we say that we could produce one new visual style every two years we
+really mean: to work two years long in order to propagate a new visual
+style to all visual manifestations of The CentOS Project corporate
+visual identity.
+
+Obviously, in order to propagate one visual style to all different
+visual manifestations of The CentOS Project corporate visual identity,
+we need first to know which the visual manifestations are. To define
+which visual manifestations are inside The CentOS Project corporate
+visual identity is one of the goals the CentOS Artwork Repository and
+this documentation manual are both aimed to satisfy.
+
+Once we define which the visual manifestation are, it is possible to
+define how to produce them, and this way, organize the automation
+process. Such automation process is one of the goals of
+@file{centos-art.sh} script.
+
+With the combination of both CentOS Artwork Repository and
+@file{centos-art.sh} scripts we define work lines where translators,
+programmers, and graphic designers work together to distribute and
+reduce the amount of time employed to produce The CentOS Project
+monolithic corporate identity.
+
+From a monolithic corporate visual identity point of view, notice that
+we are producing a new visual style for the same theme (i.e.,
+@emph{Flame}). It would be another flame design but still a flame
+design. This idea is very important to be aware of, because we are
+somehow ``refreshing'' the theme, not changing it at all.
+
+This way, as we are ``refreshing'' the theme, we still keep oursleves
+inside the monolithic conception we are trying to be attached to
+(i.e., one unique name, and one unique visual style for all visual
+manifestations).
+
+Producing artistic motifs is a creative process that may consume long
+time, specially for people without experienced knowledge on graphic
+design land. Using ``randomly generated'' conception to produce
+artistic motifs could be, practically, a way for anyone to follow in
+order to produce maintainable artistic motifs in few steps.
+
+Due to the ``randomly generated'' nature of Flame filter, we find that
+@emph{Flame} pattern is not always the same when we use @emph{Flame}
+filter interface.
+
+Using the same pattern design for each visual manifestation is
+essential in order to maintain the visual connection among all visual
+manifestations inside the same theme. Occasionally, we may introduce
+pattern variations in opacity, size, or even position but never change
+the pattern design itself, nor the color information used by images
+considered part of the same theme.
+
+@quotation
+@strong{Important}
+When we design background images, which are considered part of the
+same theme, it is essential to use the same design pattern always.
+This is what makes theme images to be visually connected among
+themeselves, and so, the reason we use to define the word ``theme''
+as: a set of images visually connected among themeselves.
+@end quotation
+
+In order for us to reproduce the same flame pattern always,
+@emph{Flame} filter interface provides the @samp{Save} and @samp{Open}
+options. The @samp{Save} option brings up a file save dialog that
+allows you to save the current Flame settings for the plug-in, so that
+you can recreate them later. The @samp{Open} option brings up a file
+selector that allows you to open a previously saved Flame settings
+file.
+
+The Flame settings we used in our example are saved in the file named
+@file{800x600.xcf-flame.def}, inside the @file{Backgrounds/Xcf}
+directory structure.
+
+@ifhtml
+@subheading Screenshots
+
+@image{trunk/Identity/Images/Themes/Flame/1/Concept/motif-thumb-250,,,,jpg}
+@image{trunk/Identity/Images/Themes/Flame/2/Concept/motif-thumb-250,,,,jpg}
+@image{trunk/Identity/Images/Themes/Flame/3/Concept/motif-thumb-250,,,,jpg}
+@end ifhtml
+
+@subheading See also
+
+@itemize
+@item --- @strong{Removed}(xref:Directories trunk Identity Images Themes Motifs) ---.
+@item @xref{Directories trunk Identity Images Themes}.
+@item @xref{Directories trunk Identity}.
+@item @xref{Directories trunk}.
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs/Modern.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs/Modern.texinfo
new file mode 100644
index 0000000..df12723
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs/Modern.texinfo
@@ -0,0 +1,24 @@
+@subheading Goals
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@ifhtml
+@subheading Screenshots
+
+@image{trunk/Identity/Images/Themes/Modern/1/Concept/motif-thumb-250,,,,jpg}
+@end ifhtml
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs/Pipes.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs/Pipes.texinfo
new file mode 100755
index 0000000..80f2bcc
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs/Pipes.texinfo
@@ -0,0 +1,28 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@ifhtml
+@subheading Screenshots
+
+@image{trunk/Identity/Images/Themes/Pipes/1/Concept/motif-thumb-250,,,,jpg}
+@end ifhtml
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs/TreeFlower.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs/TreeFlower.texinfo
new file mode 100644
index 0000000..9c31afb
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Images/Themes/Motifs/TreeFlower.texinfo
@@ -0,0 +1,19 @@
+@subheading Goals
+
+@subheading Description
+
+@ifhtml
+@subheading Screenshots
+
+@image{trunk/Identity/Images/Themes/TreeFlower/1/Concept/motif-thumb-250,,,,jpg}
+@image{trunk/Identity/Images/Themes/TreeFlower/2/Concept/motif-thumb-250,,,,jpg}
+@image{trunk/Identity/Images/Themes/TreeFlower/3/Concept/motif-thumb-250,,,,jpg}
+@image{trunk/Identity/Images/Themes/TreeFlower/4/Concept/motif-thumb-250,,,,jpg}
+@end ifhtml
+
+@subheading Usage
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models.texinfo
new file mode 100755
index 0000000..7e764ff
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models.texinfo
@@ -0,0 +1,23 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item @dots{}
+@end itemize
+
+@subheading See also
+
+@itemize
+@item ...
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Brands.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Brands.texinfo
new file mode 100644
index 0000000..d9b7c62
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Brands.texinfo
@@ -0,0 +1,71 @@
+@subheading Goals
+
+This section describes The CentOS Brand design models.
+
+@subheading Description
+
+The CentOS Brand provides the one unique name or trademark that
+connects the producer with their products. In this case, the producer
+is The CentOS Project and the products are The CentOS Project visual
+manifestations.
+
+The CentOS Brand is the main visual representation of the CentOS
+project so the typography used in it must be the same always, no
+matter where it be shown. It also has to be clear enough to dismiss
+any confussion between similar typefaces (e.g., the number one (1)
+sometimes is confuesed with the letter @samp{el} (l) or letter
+@samp{ai} (i)).
+
+As convenction, the word @samp{CentOS} uses @samp{Denmark} typography
+as base, both for the word @samp{CentOS} and the phrase
+@samp{Community Enterprise Operating System}. The phrase size of
+CentOS logo is half the size in poits the word @samp{CentOS} has and
+it below @samp{CentOS} word and aligned with it on the left. The
+distance between @samp{CentOS} word and phrase @samp{Community
+Enterprise Operating System} have the size in points the phrase has.
+
+@image{trunk/Identity/Images/Manual/Brands/Logos/a,,,,}
+
+When the CentOS release brand is built, use @samp{Denmark} typography
+for the release number. The release number size is two times larger
+(in height) than default @samp{CentOS} word. The separation between
+release number and @samp{CentOS} word is twice the size in points of
+separation between @samp{CentOS} word and phrase @samp{Community
+Enterprise Operating System}.
+
+Another component inside CentOS logo is the trademark symbol (TM).
+This symbol specifies that the CentOS logo must be consider a product
+brand, even it is not a registered one. The trademark symbol uses
+DejaVu LGC Sans Regular typography. The trademark symbol is aligned
+right-top on the outter side of @samp{CentOS} word. The trademark
+symbol must not exceed haf the distance, in points, between
+@samp{CentOS} word and the release number on its right.
+
+It would be very convenient for the CentOS Project and its community
+to to make a registered trademark (®) of CentOS logo. To make a
+register trademark of CentOS Logo prevents legal complications in the
+market place of brands. It grants the consistency, through time, of
+CentOS project corporate visual identity.
+
+@quotation
+@strong{Note} The information about trademarks and corporate identity
+is my personal interpretation of
+@url{http://en.wikipedia.org/Corporate_identity} and
+@url{http://en.wikipedia.org/Trademark} description. If you have
+practical experiences with these affairs, please serve yourself to
+improve this section with your reasons.
+@end quotation
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk Identity Models}
+@item @ref{Directories trunk Identity}
+@item @ref{Directories trunk}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes.texinfo
new file mode 100644
index 0000000..375e1b3
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes.texinfo
@@ -0,0 +1,46 @@
+@subheading Goals
+
+This section describes design models from The CentOS Themes.
+
+@subheading Description
+
+Theme models let you modeling characteristics (e.g., dimensions,
+translation markers, position of each element on the display area,
+etc.) common to all themes. Theme models let you reduce the time
+needed when propagating artistic motifs to different visual
+manifestations.
+
+Theme models serves as a central pool of design templates for themes
+to use. This way you can produce themes with different artistic motifs
+but same characteristics.
+
+@subsubheading Default Design Model
+
+Default Design Models for CentOS Themes provide the common structural
+information (e.g., image dimensions, translation markers, trademark
+position, etc.) the @command{centos-art} script uses to produce images
+when no other design model is specified.
+
+@subsubheading Alternative Design Models
+
+CentOS alternative theme models exist for people how want to use a
+different visual style on their installations of CentOS distribution.
+As the visual style is needed for a system already installed
+components like Anaconda are not required inside alternative themes.
+Inside alternative themes you find post-installation visual style only
+(i.e. Backgrounds, Display Managers, Grub, etc.). CentOS alternative
+themes are maintained by CentOS Community.
+
+@subheading Usage
+
+@itemize
+@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default) ---.
+@end itemize
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk Identity Images Themes}.
+@item @ref{Directories trunk Identity}.
+@item @ref{Directories trunk}.
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default.texinfo
new file mode 100644
index 0000000..60f0afd
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default.texinfo
@@ -0,0 +1,79 @@
+@subheading Goals
+
+This section describes the default design model of The CentOS Themes.
+
+@subheading Description
+
+The @file{trunk/Identity/Themes/Models/Default} directory implements
+the concept of @emph{Default Design Model} for The CentOS Themes. The
+CentOS Themes Default Design Model provides the common structural
+information (e.g., image dimensions, translation markers, trademark
+position, etc.) the @command{centos-art} script uses to produce images
+when no other design model is specified.
+
+Deisgn models in this directory do use the @emph{CentOS Release
+Brand}. The CentOS Release Brand is a combination of both The CentOS
+Type and The CentOS Release Schema used to illustrate the major
+release of The CentOS Distribution the image produced belongs to. ---
+@strong{Removed}(xref:Directories trunk Identity Models Tpl Brands)
+---, for more information.
+
+The CentOS Project maintains near to four different major releases of
+CentOS Distribution. Each major release of CentOS Distribution has
+internal differences that make them unique and, at the same time, each
+CentOS Distribution individually is tagged into the one unique visual
+manifestation (i.e., Distribution). So, how could we implement the
+monolithic visual structure in one visual manifestation that has
+internal difference?
+
+To answer this question we broke the question in two parts and later
+combined the resultant answers to build a possible solution.
+
+@table @strong
+@item How to remark the internal differences visually?
+
+Merge both The CentOS Project Release Schema into The CentOS Project
+Trademark to build The CentOS Project Release Trademark. The CentOS
+Project Release Trademark remarks two things: first, it remarks the
+image is from The CentOS Project and second, it remarks which major
+release of CentOS Distribution does the image belongs to.
+--- @strong{Removed}(xref:Directories trunk Identity Models Tpl Brands) ---, for more
+information on how to develop and improve The CentOS Project Brand.
+
+@item How to remark the visual resemblance?
+
+Use a common artistic motifs as background for all CentOS Distribution
+images. --- @strong{Removed}(xref:Directories trunk Identity Images Themes Motifs) ---, for more
+information.
+
+@item So, combining answers above, we could conclude that:
+
+In order to implement the CentOS Monolithic Visual Structure on CentOS
+Distribution visual manifestations, a CentOS Release Trademark and a
+background information based on one unique artistic motif should be
+used in all remarkable images The CentOS Distribution visual
+manifestation is made of.
+@end table
+
+@quotation
+@strong{Important} Remarking the CentOS Release Schema inside each
+major release of CentOS Distribution ---or similar visual
+manifestations--- takes @emph{high attention} inside The CentOS
+Project corporate visual identity. It should be very clear for
+everyone which major release of CentOS Distribution is being used.
+@end quotation
+
+@subheading Usage
+
+@itemize
+@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro) ---.
+@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Concept) ---.
+@end itemize
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk Identity Images Themes}
+@item @ref{Directories trunk Identity Models Themes}
+@item --- @strong{Removed}(ref:Directories trunk Identity Images Themes Motifs) ---
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Concept.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Concept.texinfo
new file mode 100755
index 0000000..e226b31
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Concept.texinfo
@@ -0,0 +1,22 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro.texinfo
new file mode 100644
index 0000000..6cee901
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro.texinfo
@@ -0,0 +1,111 @@
+@subheading Goals
+
+This section organizes default design models for different major
+releases of CentOS Distribution.
+
+@subheading Description
+
+In order to better understatand how this visual manifestation is
+organized, it is necessary to consider what The CentOS Distribution is
+and how it is released.
+
+@subsubheading The CentOS Distribution
+
+The CentOS Distribution is an Enterprise-class Linux Distribution
+derived from sources freely provided to the public by a prominent
+North American Enterprise Linux vendor. The CentOS Distribution
+conforms fully with the upstream vendors redistribution policy and
+aims to be 100% binary compatible. (The CentOS Project mainly changes
+packages to remove upstream vendor branding and artwork.)
+
+The CentOS Distribution 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.
+
+@subsubheading The CentOS Distribution Release Schema
+
+The upstream vendor has released 4 versions of their
+@acronym{EL,Enterprise Linux} product that The CentOS Project rebuilds
+the freely available SRPMS for. The upstream vendor releases security
+updates as required by circumstances. The CentOS Project releases
+rebuilds of security updates as soon as possible. Usually within 24
+hours (our stated goal is with 72 hours, but we are usually much
+faster).
+
+The upstream vendor also releases numbered update sets for major
+versions of their EL product from 2 to 4 times per year. There are new
+ISOs from the upstream vendor provided for these update sets. Update
+sets will be completed as soon as possible after the upstream vendor
+releases their version @dots{} generally within 2 weeks. The CentOS
+Project follows these conventions as well, so CentOS-3.9 correlates
+with EL 3 update 9 and CentOS-4.6 correlates with EL 4 update 6,
+CentOS-5.1 correlates to EL 5 update 1, etc.
+
+One thing some people have problems understanding is that if you have
+any CentOS-3 product and update it, you will be updated to the latest
+CentOS-3.x version.
+
+The same is true for CentOS-4 and CentOS-5. If you update any CentOS-4
+product, you will be updated to the latest CentOS-4.x version, or to
+the latest CentOS-5.x version if you are updating a CentOS-5 system.
+This is exactly the same behavior as the upstream product. Let's
+assume that the latest EL4 product is update 6. If you install the
+upstream original EL4 CDs (the ones before any update set) and upgrade
+via @command{yum}, you will have latest update set installed (EL4
+update 6 in our example). Since all updates within a major release
+(CentOS-2, CentOS-3, CentOS-4, CentOS-5) always upgrade to the latest
+version when updates are performed (thus mimicking upstream behavior),
+only the latest version is maintained in each main tree on The CentOS
+Mirrors (@url{http://mirrors.centos.org/}).
+
+There is a CentOS Vault (@url{http://vault.centos.org/}) containing
+old CentOS trees. This vault is a picture of the older tree when it
+was removed from the main tree, and does not receive updates. It
+should only be used for reference.
+
+The CentOS Distribution visual style is controlled by image files.
+These image files are packaged inside The CentOS Distribution and made
+visible once such packages are installed and executed. The way to go
+for changing The CentOS Distribution visual style is changing all
+those image files to add the desired visual style first and later,
+repackage them to make them available inside the final iso files of
+CentOS Distribution.
+
+@subheading Usage
+
+Sometimes, between major releases, image files inside packages can be
+added, removed or just get the name changed. In order to describe such
+variations, the design models directory structure is organized in the
+same way the variations are introduced (i.e., through The CentOS
+Distribution Release Schema). So, each major release of The CentOS
+Distribution has its own design model directory structure.
+
+When a new package/component is added to one or all the major releases
+of The CentOS Distribution, a design model directory structure for
+that component needs to be created. Later, it is filled up with
+related design models. Design models are created for each image file
+inside the component that need to be rebuilt in order to set the
+visual style and brand information correctly.
+
+When a package is removed from one or all major releases of The CentOS
+Distribution, the design model directory structure releated to that
+package/component is no longer used. However, it could be very useful
+for historical reasons. Also, someone could feel motivation enough to
+keep himself documenting it or supporting it for whatever reason.
+
+@itemize
+@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro
+5) ---.
+@end itemize
+
+@subheading See also
+
+@itemize
+@item --- @strong{Removed}(ref:Directories trunk Identity Models Themes Default) ---.
+@item @ref{Directories trunk Identity Models Themes}.
+@item @ref{Directories trunk Identity Images Themes}.
+@item @ref{Directories trunk Identity}.
+@item @ref{Directories trunk}.
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5.5/Notes/Release.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5.5/Notes/Release.texinfo
new file mode 100755
index 0000000..d6bb628
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5.5/Notes/Release.texinfo
@@ -0,0 +1,23 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@itemize
+@item ...
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5.texinfo
new file mode 100755
index 0000000..c76921e
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5.texinfo
@@ -0,0 +1,35 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Syslinux) ---.
+@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Anaconda) ---.
+@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Rhgb) ---.
+@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Gdm) ---.
+@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Kdm) ---.
+@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Grub) ---.
+@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Gsplash) ---.
+@item --- @strong{Removed}(xref:Directories trunk Identity Models Themes Default Distro 5 Ksplash) ---.
+@end itemize
+
+@subheading See also
+
+@itemize
+@item --- @strong{Removed}(ref:Directories trunk Identity Models Themes Default Distro) ---.
+@item --- @strong{Removed}(ref:Directories trunk Identity Models Themes Default) ---.
+@item @ref{Directories trunk Identity Models Themes}.
+@item @ref{Directories trunk Identity Images Themes}.
+@item @ref{Directories trunk Identity}.
+@item @ref{Directories trunk}.
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Anaconda.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Anaconda.texinfo
new file mode 100644
index 0000000..c10b6dd
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Anaconda.texinfo
@@ -0,0 +1,14 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@subheading Usage
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Firstboot.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Firstboot.texinfo
new file mode 100755
index 0000000..e226b31
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Firstboot.texinfo
@@ -0,0 +1,22 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gdm.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gdm.texinfo
new file mode 100755
index 0000000..53ef237
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gdm.texinfo
@@ -0,0 +1,30 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+Another example of using last-rendition flow is that related to GDM
+and KDM @file{tar.gz} file construction. Each @file{tar.gz} file is
+made of several files that need to be put together in order to make
+them installable. In the very specific case of GDM and KDM some of the
+required files are retrived from design models directory structure and
+others from artistic motifs directory structure after had been
+produced through base-rendition. In this case, the action of grouping
+files and packing them is realized through last-rendition action. This
+couldn't be possible through post-rendition because we need to wait to
+have two images first (produced through base-rendition) before we
+could grouping them all into the @file{tar.gz} package.
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Grub.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Grub.texinfo
new file mode 100755
index 0000000..e226b31
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Grub.texinfo
@@ -0,0 +1,22 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gsplash.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gsplash.texinfo
new file mode 100755
index 0000000..e226b31
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Gsplash.texinfo
@@ -0,0 +1,22 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Kdm.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Kdm.texinfo
new file mode 100755
index 0000000..e226b31
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Kdm.texinfo
@@ -0,0 +1,22 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Ksplash.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Ksplash.texinfo
new file mode 100755
index 0000000..02aa8be
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Ksplash.texinfo
@@ -0,0 +1,25 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+The @file{Preview.png} image of Ksplash which is made of three
+different images. In order to build the @file{Preview.png} image, we
+need to create the three images the @file{Preview.png} image is made
+of first (e.g., through base-rendition) and then, combine them all
+together into one new image, the @file{Preview.png} image in this
+case.
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Rhgb.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Rhgb.texinfo
new file mode 100755
index 0000000..e226b31
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Rhgb.texinfo
@@ -0,0 +1,22 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Syslinux.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Syslinux.texinfo
new file mode 100755
index 0000000..d6bb628
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Distro/5/Syslinux.texinfo
@@ -0,0 +1,23 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@itemize
+@item ...
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Posters.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Posters.texinfo
new file mode 100644
index 0000000..e226b31
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Models/Themes/Default/Posters.texinfo
@@ -0,0 +1,22 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Palettes.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Palettes.texinfo
new file mode 100755
index 0000000..e226b31
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Palettes.texinfo
@@ -0,0 +1,22 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Patterns.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Patterns.texinfo
new file mode 100755
index 0000000..cbc5503
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Patterns.texinfo
@@ -0,0 +1,24 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk Identity}
+@item @ref{Directories trunk}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Identity/Webenv.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Webenv.texinfo
new file mode 100755
index 0000000..5736d03
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Identity/Webenv.texinfo
@@ -0,0 +1,327 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+The CentOS web environment is formed by a central web application
+---to cover base needs (e.g., per-major release information like
+release notes, lifetime, downloads, documentation, support, security
+advisories, bugs, etc.)--- and many different free web applications
+---to cover specific needs (e.g., wiki, mailing lists, etc.)---.
+
+The CentOS web environment is addressed to solve the following issues:
+
+@itemize
+@item One unique name and one unique visual style to all web
+applications used inside the web environment.
+
+@item One-step navigation to web applications inside the environment.
+
+@item High degree of customization to change the visual style of all
+web applications with few changes (e.g, updating just two or three
+images plus common style sheet [CSS] definitions).
+@end itemize
+
+The CentOS project is attached to a monolithic corporate visual
+identity (@pxref{Directories trunk Identity}), where all visual manifestations
+have one unique name and one unique visual style. This way, the CentOS
+web environment has one unique name (the CentOS brand) and one unique
+visual style (the CentOS default theme) for all its visual
+manifestations, the web applications in this case.
+
+Since a maintainance point of view, achiving the one unique visual
+style inside CentOS web environment is not a simple task. The CentOS
+web environment is built upon many different web applications which
+have different visual styles and different internal ways to customize
+their own visual styles. For example: MoinMoin, the web application
+used to support the CentOS wiki (@url{http://wiki.centos.org/}) is
+highly customizable but Mailman (in its 2.x.x serie), the web
+application used to support the CentOS mailing list, doesn't
+support@footnote{The theme support of Mailman may be introduced in
+mailman-3.x.x release.} a customization system that separates
+presentation from logic, similar to that used by MoinMoin.
+
+This visual style diversity complicates our goal of one unique visual
+style for all web applications. So, if we want one unique visual style
+for all web applications used, it is innevitable to modify the web
+applications in order to implement the CentOS one unique visual style
+customization in them. Direct modification of upstream applications is
+not convenient because upstream applications come with their one
+visual style and administrators take the risk of loosing all
+customization changes the next time the application be updated (since
+not all upstream web applications, used in CentOS web environment,
+separate presentation from logic).
+
+To solve the ``one unique visual style'' issue, installation and
+actualization of web applications ---used inside CentOS web
+environment--- need to be independent from upstream web applications
+development line; in a way that CentOS web environment administrators
+can install and update web applications freely without risk of loosing
+the one unique visual style customization changes.
+
+At the surface of this issue we can see the need of one specific yum
+repository to store CentOS web environment customized web applications.
+
+@subsubheading Design model (without ads)
+
+@subsubheading Design model (with ads)
+
+@subsubheading HTML definitions
+
+@subsubheading Controlling visual style
+
+Inside CentOS web environment, the visual style is controlled by the
+following compenents:
+
+@table @strong
+@item Webenv header background
+@verbatim
+trunk/Identity/Images/Themes/$THEME/Backgrounds/Img/1024x250.png
+@end verbatim
+
+@item CSS definitions
+@verbatim
+trunk/Identity/Themes/Models/Default/Promo/Web/CSS/stylesheet.css
+@end verbatim
+@end table
+
+@subsubheading Producing visual style
+
+The visual style of CentOS web environment is defined in the following
+files:
+
+@verbatim
+trunk/Identity/Images/Themes/$THEME/Backgrounds/Xcf/1024x250.xcf
+trunk/Identity/Images/Themes/$THEME/Backgrounds/Img/1024x250.png
+trunk/Identity/Images/Themes/$THEME/Backgrounds/Img/1024x250-bg.png
+trunk/Identity/Images/Themes/$THEME/Backgrounds/Tpl/1024x250.svg
+@end verbatim
+
+As graphic designer you use @file{1024x250.xcf} file to produce
+@file{1024x250-bg.png} file. Later, inside @file{1024x250.svg} file,
+you use the @file{1024x250-bg.png} file as background layer to draw
+your vectorial design. When you consider you artwork ready, use the
+@command{centos-art.sh} script, as described below, to produce the
+visual style controller images of CentOS web environment.
+
+@verbatim
+centos-art render --entry=trunk/Identity/Images/Themes/$THEME/Backgrounds --filter='1024x250'
+@end verbatim
+
+Once you have rendered required image files, changing the visual style
+of CentOS web environment is a matter of replacing old image files
+with new ones, inside webenv repository file system structure. The
+visual style changes will take effect the next time customization line
+of CentOS web applications be packaged, uploded, and installed from
+[webenv] or [webenv-test] repositories.
+
+@subsubheading Navigation
+
+Inside CentOS web environment, the one-step navegation between web
+applications is addressed using the web environment navigation bar.
+The web environment navigation bar contains links to main applications
+and is always visible no matter where you are inside the web
+environment.
+
+@subsubheading Development and release cycle
+
+The CentOS web environment development and relase cycle is described
+below:
+
+@table @strong
+
+@item Download
+
+The first action is download the source code of web applications we
+want to use inside CentOS web environment.
+
+@quotation
+@strong{Important} The source location from which web application are
+downloaded is very important. Use SRPMs from CentOS @strong{[base]}
+and @strong{[updates]} repositories as first choise, and third party
+repositories (e.g. RPMForge, EPEL, etc.) as last resource.
+@end quotation
+
+@item Prepare
+
+Once web application source code has been downloaded, our duty is
+organize its files inside @samp{webenv} version controlled repository.
+
+When preparing the structure keep in mind that different web
+applications have different visual styles, and also different ways to
+implement it. A convenient way to organize the file system structure
+would be create one development line for each web application we use
+inside CentOS web environment. For example, consider the following
+file system structure:
+
+@verbatim
+https://projects.centos.org/svn/webenv/trunk/
+|-- WebApp1/
+| |-- Sources/
+| | `-- webapp1-0.0.1/
+| |-- Rpms/
+| | `-- webapp1-0.0.1.rpm
+| |-- Srpms/
+| | `-- webapp1-0.0.1.srpm
+| `-- Specs/
+| `-- webapp1-0.0.1.spec
+|-- WebApp2/
+`-- WebAppN/
+@end verbatim
+
+@item Customize
+
+Once web applications have been organized inside the version
+controlled repository file system, use subversion to create the CentOS
+customization development line of web applications source code. For
+example, using the above file system structure, you can create the
+customization development line of @file{webapp1-0.0.1/} with the
+following command:
+
+@verbatim
+svn cp trunk/WebApp1/Sources/webapp1-0.0.1 trunk/WebApp1/Sources/webapp1-0.0.1-webenv
+@end verbatim
+
+The command above creates the following structure:
+
+@verbatim
+https://projects.centos.org/svn/webenv/trunk/
+|-- WebApp1/
+| |-- Sources/
+| | |-- webapp1-0.0.1/
+| | `-- webapp1-0.0.1-webenv/
+| |-- Rpms/
+| | `-- webapp1-0.0.1.rpm
+| |-- Srpms/
+| | `-- webapp1-0.0.1.srpm
+| `-- Specs/
+| `-- webapp1-0.0.1.spec
+|-- WebApp2/
+`-- WebAppN/
+@end verbatim
+
+In the above structure, the @file{webapp1-0.0.1-webenv/} directory is
+the place where you customize the visual style of
+@file{webapp1-0.0.1/} web application.
+
+@quotation
+@strong{Tip} Use the @command{diff} command of Subversion between
+CentOS customization and upstream development lines to know what you
+are changing exactly.
+@end quotation
+
+@item Build packages
+
+When web application has been customized, build the web application
+RPM and SRPM using the source location with @samp{-webenv} prefix.
+
+@verbatim
+https://projects.centos.org/svn/webenv/trunk/
+|-- WebApp1/
+| |-- Sources/
+| | |-- webapp1-0.0.1/
+| | `-- webapp1-0.0.1-webenv/
+| |-- Rpms/
+| | |-- webapp1-0.0.1.rpm
+| | `-- webapp1-0.0.1-webenv.rpm
+| |-- Srpms/
+| | |-- webapp1-0.0.1.srpm
+| | `-- webapp1-0.0.1-webenv.srpm
+| `-- Specs/
+| |-- webapp1-0.0.1.spec
+| `-- webapp1-0.0.1-webenv.spec
+|-- WebApp2/
+`-- WebAppN/
+@end verbatim
+
+@item Release for testing
+
+When the customized web application has been packaged, make packages
+available for testing and quality assurance. This can be achives using
+a [webenv-test] yum repository.
+
+@quotation
+@strong{Note} The [webenv-test] repository is not shipped inside
+CentOS distribution default yum configuraiton. In order to use
+[webenv-test] repository you need to configure it first.
+@end quotation
+
+If some problem is found to install/update/use the customized version
+of web application, the problem is notified somewhere (a bugtracker
+maybe) and the customization face is repated in order to fix the
+problem. To release the new package add a number after @samp{-webenv}
+prefix. For example, if some problem is found in
+@file{webapp1-0.0.1-webenv.rpm}, when it be fixed the new package will
+be named @file{webapp1-0.0.1-webenv-1.rpm}. If a problem is found in
+@file{webapp1-0.0.1-webenv-1.rpm}, when it be fixed the new package
+will be named @file{webapp1-0.0.1-webenv-2.rpm}, and so on.
+
+The ``customization --- release for testing'' process is repeated
+until CentOS quality assurance team considers the package is ready for
+production.
+
+@item Release for production
+
+When customized web application packages are considered ready for
+production they are moved from [webenv-test] to [webenv] repository.
+This action is commited by CentOS quality assurance team.
+
+@quotation
+@strong{Note} The [webenv] repository is not shipped inside CentOS
+distribution default yum configuraiton. In order to use [webenv]
+repository you need to configure it first.
+@end quotation
+@end table
+
+@subsubheading The [webenv-test] repository
+
+@verbatim
+/etc/yum.repos.d/CentOS-Webenv-test.repo
+@end verbatim
+
+@verbatim
+[webenv-test]
+name=CentOS-$releasever - Webenv-test
+mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv-test
+#baseurl=http://mirror.centos.org/centos/$releasever/webenv-test/$basearch/
+gpgcheck=1
+gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever
+enabled=1
+priority=10
+@end verbatim
+
+@subsubheading The [webenv] repository
+
+@verbatim
+/etc/yum.repos.d/CentOS-Webenv.repo
+@end verbatim
+
+@verbatim
+[webenv]
+name=CentOS-$releasever - Webenv
+mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv
+#baseurl=http://mirror.centos.org/centos/$releasever/webenv/$basearch/
+gpgcheck=1
+gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever
+enabled=1
+priority=10
+@end verbatim
+
+@subsubheading Priority configuration
+
+Both [webenv] and [webenv-test] repositories update packages inside
+CentOS [base] and CentOS [updates] repositories.
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@menu
+@end menu
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Locales.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Locales.texinfo
new file mode 100644
index 0000000..823d887
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Locales.texinfo
@@ -0,0 +1,72 @@
+@subheading Goals
+
+The @file{trunk/Locales} directory structure provides the localization
+work line and its main goal is provide the translation messages
+required to produce content in different languages.
+
+@subheading Description
+
+Translation messages inside the repository are stored as portable
+objects (e.g., .po, .pot) and machine objects (.mo) under
+@file{trunk/Locales} directory structure.
+
+Translation messages are organized using the directory structure of
+the component being translated. For example, if we want to provide
+translation messages for @file{trunk/Manuals/Repository}, then the
+@file{trunk/Locales/Manuals/Repository} directory needs to be created.
+
+Once the locale directory exists for the component we want to provide
+translation messages for, it is necessary to create the translation
+files where translation messages are. The translation files follows
+the concepts of @command{xml2po} and GNU @command{gettext} tools.
+
+The basic translation process is as follow: first, translatable
+strings are extracted from files and a portable object template (.pot)
+is created or updated with the information. Using the portable object
+template, a portable object (.po) is created or updated for translator
+to locale the messages retrived. Finally, a machine object (.mo) is
+created from portable object to sotore the translated messages.
+
+Inside the repository there are two ways to retrive translatable
+strings from files. The first one is through @command{xml2po} command
+and the second through @command{xgettext} command. The @command{xml2po}
+is used to retrive translatable strings from XML files (e.g., Scalable
+Vector Graphics, DocBook, etc.) and the @command{xgettext} command is
+used to retrive translatable strings from shell scripts files (e.g.,
+the files that make the @command{centos-art.sh} command-line
+interface).
+
+When translatable strings are retrived from XML files, using the
+@command{xml2po} command, there is no need to create the machine
+object as we do when translatable strings ar retrived from shell
+files, using the @command{xgettext} command. The @command{xml2po}
+produces a temporal machine object in order to create a translated XML
+file. Once the translated XML file has been created the machine object
+is no longer needed. On the other hand, the machine object produced by
+the @command{xgettext} command is required by the system in order for
+the show shell script localized messages.
+
+Another difference between @command{xml2po} and @command{xgettext} we
+need to be aware of is the directory structure used to store machine
+objects. In @command{xml2po}, the machine object is created in the
+current working directory as @file{.xml2po.mo} and can be safetly
+removed once the translated XML file has been created. In the case of
+@command{xgettext}, the machine object needs to be stored in the
+@file{$TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo} file in order
+for the system to interpret it and should not be removed since it is
+the file that contain the translation messages themselves.
+
+Automation of localization tasks is achived through the @code{locale}
+functionality of command-line interface.
+
+@subheading Usage
+
+@itemize
+@item @xref{Directories trunk Scripts Functions Locale}.
+@end itemize
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Manuals.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Manuals.texinfo
new file mode 100644
index 0000000..4ec2167
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Manuals.texinfo
@@ -0,0 +1,94 @@
+@subheading Goals
+
+The @file{trunk/Manual} directory is the place where files related to
+documentation work line are stored in. The main goal of documentation
+work line is to describe what each directory inside the CentOS Artwork
+Repository is for, the conceptual ideas behind them and, if possible,
+how automation scripts make use of them.
+
+@subheading Description
+
+The repository documentation manual is made of the following files:
+
+@table @file
+
+@item repository.css
+
+This file controls the visual style for XHTML output files of
+repository documentation manual.
+
+@item repository-index.texinfo
+
+This file controls the index definition for source files of repository
+documentation manual.
+
+@item repository.info.bz2
+
+This file provides the Info output of repository documentation manual.
+
+@item repository-init.pl
+
+This file provides the initialization script of @command{texi2html},
+the program used by @command{centos-art.sh} script to produce the
+XHTML output of repository documentation manual.
+
+@item repository-menu.texinfo
+
+This file controls the menu definition of chapters for source files of
+repository documentation manual.
+
+@item repository-node.texinfo
+
+This file controls the node definition of chapters for source files of
+repository documentation manual.
+
+@item repository.pdf
+
+This file provides the PDF output of repository documentation manual.
+
+@item repository.sed
+
+This file provides post-transformations for XHTML output files. In
+this file is where XHTML definitions for admonitions are set in.
+
+@item repository.texinfo
+
+This is the source file of repository documentation manual where
+the manual structure initialization is set.
+manual.
+
+@item repository.txt.bz2
+
+This file provides the TXT output of repository documentation manual.
+
+@item repository.xhtml.bz2
+
+This file provides the XHTML output of repository documentation
+manual.
+
+@item repository.xml
+
+This file provides the XML output of repository documentation manual.
+
+@end table
+
+The repository documentation manual is made of the following
+directories:
+
+@itemize
+@item @xref{Directories trunk Manuals Directories}.
+@item @xref{Directories trunk Manuals Introduction}.
+@item @xref{Directories trunk Manuals Licenses}.
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item @xref{Directories trunk Scripts Functions Help}.
+@end itemize
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Manuals/Directories.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Manuals/Directories.texinfo
new file mode 100755
index 0000000..0a72b17
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Manuals/Directories.texinfo
@@ -0,0 +1,27 @@
+@subheading Goals
+
+The @file{trunk/Manual/Directories} directory stores source
+documentation files related to repository directories. The directory
+structure in this location mirrors the directory structure being
+documented in the repository from top level directories (e.g.,
+@file{trunk}, @file{branches} and @file{tags}) to inner levels,
+including the @file{trunk/Manual} location itself where documentation
+source files are stored in.
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@itemize
+@item ...
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Manuals/Introduction.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Manuals/Introduction.texinfo
new file mode 100755
index 0000000..d6bb628
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Manuals/Introduction.texinfo
@@ -0,0 +1,23 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@itemize
+@item ...
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Manuals/Licenses.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Manuals/Licenses.texinfo
new file mode 100755
index 0000000..d6bb628
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Manuals/Licenses.texinfo
@@ -0,0 +1,23 @@
+@subheading Goals
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Description
+
+@itemize
+@item ...
+@end itemize
+
+@subheading Usage
+
+@itemize
+@item ...
+@end itemize
+
+@subheading See also
+
+@itemize
+@item ...
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Scripts.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Scripts.texinfo
new file mode 100644
index 0000000..bdd4fcb
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Scripts.texinfo
@@ -0,0 +1,167 @@
+@subheading Goals
+
+This section provides the automation work line. The automation work
+line exists to standardize content production in CentOS Artwork
+Repository. There is no need to type several tasks, time after time,
+if they can be programmed into just one executable script.
+
+In this section you'll find how to organize and extend the
+@command{centos-art.sh} script, a bash scripts specially designed to
+automate most frequent tasks in the repository (e.g., image rendition,
+documenting directory structures, translating content, etc.). If you
+can't resist the idea of automating repeatable tasks, then take a look
+here.
+
+@subheading Description
+
+The best way to understand the @command{centos-art.sh} script is
+studying and improving its source code. However, as start point, you
+may prefer to read an introductory resume before diving into the
+source code details. In this section we identify the different parts
+the @command{centos-art.sh} script is made of and how these parts
+interact one another.
+
+@subsubheading Execution environments
+
+The @command{centos-art.sh} script is basically made of four execution
+environments which are named @emph{script}, @emph{global},
+@emph{specific} and @emph{action}. These execution environments are
+nested one into another and provide different definition levels for
+variables and functions. In this design, variables and functions
+defined in higher execution environments are available on lower
+execution environments, but variables and functions defined in lower
+execution environments are not available for higher execution
+enviroments.
+
+@verbatim
++----------------------------------------------------------------------+
+| [centos@host]$ centos-art function path/to/dir --option='value' |
++----------------------------------------------------------------------+
+| ~/bin/centos-art --> ~/artwork/trunk/Scripts/centos-art.sh |
++---v--------------------------------------------------------------v---+
+ | centos-art.sh |
+ +---v------------------------------------------------------v---+
+ . | cli $@ | .
+ . +---v----------------------------------------------v---+ .
+ . . | cli_getFunctions | . .
+ . . +---v--------------------------------------v---+ . .
+ . . . | function | . . .
+ . . . +---v------------------------------v---+ . . .
+ . . . . | function_getOptions | . . . .
+ . . . . | function_doSomething | . . . .
+ . . . . +------------------------------+ . . . .
+ . . . . . . . .
+ . . . . Execution environment (action) . . . .
+ . . . ........................................ . . .
+ . . . . . .
+ . . . Execution environment (specific) . . .
+ . . ................................................ . .
+ . . . .
+ . . Execution environment (global) . .
+ . ........................................................ .
+ . .
+ . Execution environment (script) .
+ ................................................................
+@end verbatim
+
+The script execution environment exists to provide script definitions
+that can't be set anywhere else inside the script. Example of such
+definitions include initialization of internationalization through
+@command{gettext} program, script personal information and
+initialization of global functionalities.
+
+The global execution environment exists to provide definitions that
+can't be set anywhere else inside the script. Example of such
+definitions include initialization of functionalities (e.g.,
+@code{cli_printMessage}, @code{cli_getCurrentLocale},
+@code{cli_checkFiles}, etc.) and variables (e.g., @var{FUNCNAM},
+@var{FUNCDIR}, @var{FUNCDIRNAM}, @var{ARGUMENTS}, etc.) that can be
+both used on specific and action execution environments, only.
+
+The specific execution environment exists to provide definitions that
+can't be set anywhere else inside the script. Example of such
+definitions include initialization of specifc functionalities (e.g.,
+@code{render}, @code{help}, @code{locale}, etc.) and specific
+variables (@var{ACTIONNAM}, @var{ACTIONVAL}, etc.) that can be used on
+action execution environment only.
+
+The action execution environment exists to perform the script actions
+themselves. It is here where we perform content rendition, content
+documentation, content localization and whatever action you plan for
+the @command{centos-art.sh} script to perform. For example, if you
+passed the @code{render} value as first argument to
+@command{centos-art.sh} command-line, the script performs the content
+rendition action through the @code{render} function which is defined
+in the @file{render.sh} file under
+@file{trunk/Scripts/Functions/Render} directory. Is there, inside
+@code{render} functionality were the action execution environment
+takes place exactly.
+
+@subsubheading Command-line interface
+
+When the @command{centos-art} command is executed in a bash terminal,
+the bash interpreter uses the @env{PATH} environment variable to find
+where such command is. In order to run the @command{centos-art}, it
+must exist either as a link to an executable file or an executable
+file by its own, in any of the paths provided by @env{PATH}
+environment variable. Otherwise, the bash interpreter will print an
+error message and prompt you back to type a valid command.
+
+By default, after installing The CentOS Distribution, there is no
+@command{centos-art} command available in the @env{PATH} environment
+variable for you to execute. The @command{centos-art} command is made
+available in your workstation as result of executing the
+@code{prepare} functionality of @command{centos-art.sh} script
+(@pxref{Directories trunk Scripts Functions Prepare}) which requires
+you had previously downloaded a working copy of CentOS Artwork
+Repository in your workstation.
+
+When the @command{centos-art} is executed, the first positional
+parameter passed is required and represents the name of the function
+you want to perform (e.g., @code{render} for content rendition,
+@code{locale} for content localization, etc.). Beyond the first
+positional parameter you can provide either option or non-option
+parameters in no specific order. There are also, option parameters
+with arguments and without arguments. Frequently, non-option paramters
+are used to specify the path location inside the repository where the
+function will be performed in (e.g., the directory structure do you
+want to produce content for) and option parameters to specify how such
+functionality is performed (e.g., do you want to go quietly? do you
+want to do filtering? etc.).
+
+@verbatim
+ A B C D E
+---------- ------- ----------- ---------------- -------
+centos-art funcnam path/to/dir --filter='regex' --quiet
+---------- ------- ----------- ---------------- -------
+
+ A = The centos-art.sh script command-line.
+ B = The centos-art.sh function name.
+ C = Non-option parameter.
+ D = Option parameter (with argument).
+ E = Option parameter (without argument).
+@end verbatim
+
+@subsubheading Parsing command-line options
+
+The action of parsing options is performed through @command{getopt}
+and results particularly interesting. @command{getopt} breaks up
+(parse) options in command lines and checks for legal options using
+the GNU @code{getopt} routines to do this. One important consideration
+on @command{centos-art.sh} script design is that positional parameters
+are retrived in the @code{cli} function but parsed on each specific
+function, individually. There isn't a big parsing definition to cover
+all specific functions, but one parsing definitions for each specific
+functions.
+
+@subheading Usage
+
+@itemize
+@item @xref{Directories trunk Scripts Functions}.
+@end itemize
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions.texinfo
new file mode 100755
index 0000000..910e891
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions.texinfo
@@ -0,0 +1,348 @@
+@subheading Goals
+
+The @file{trunk/Scripts/Functions} directory exists to organize
+@file{centos-art.sh} specific functionalities.
+
+@subheading Description
+
+The specific functions of @file{centos-art.sh} script are designed
+with the ``Software Toolbox'' philosophy (@inforef{Toolbox
+introduction,,coreutils.info}) in mind: each program ``should do one
+thing well''. Inside @file{centos-art.sh} script, each specific
+functionality is considered a program that should do one thing well.
+Of course, if you find that they still don't do it, feel free to
+improve them in order for them to do so.
+
+The specific functions of @file{centos-art.sh} script are organized
+inside specific directories under @file{trunk/Scripts/Functions}
+location. Each specific function directory should be named as the
+function it represents, with the first letter in uppercase. For
+example, if the function name is @code{render}, the specific function
+directory for it would be @samp{trunk/Scripts/Functions/Render}.
+
+@subsubheading Creating the @code{greet} functionality
+
+To better understand how to design specific functions for
+@file{centos-art.sh} script, let's create the @code{greet}
+functionality which only goal is to print out different kind of
+greetings to your screen. The @code{greet} functionality will be set
+using the follwiing directory structure:
+
+@verbatim
+trunk/Scripts/Functions/Greet <-- The source location of greet function.
+|-- greet_getOptions.sh <-- Defines command-line interface.
+|-- greet_sayGoodbye.sh <-- Defines specific action.
+|-- greet_sayHello.sh <-- Defines specific action.
+`-- greet.sh <-- Defines function initialization.
+@end verbatim
+
+The @file{greet.sh} file contains the initialization script of
+@code{greet} functionality. It is the first file loaded from function
+source location by @command{centos-art.sh} script when it is executed
+using the @code{greet} functionality as first argument.
+
+Inside @file{centos-art.sh} script, as convenction, each function
+script has one top commentary, followed by one blank line, and then
+one function defintion below it only. The top commentary has the
+function description, one-line for copyright notice with your personal
+information, the license under which the function source code is
+released ---the @file{centos-art.sh} script is released as GPL, so do
+all its functions--- and the @code{$Id$} keyword of Subversion which
+is later expanded by @command{svn propset} command. In our example,
+the top comment of @code{greet.sh} function script would look like the
+following:
+
+@verbatim
+#!/bin/bash
+#
+# greet.sh -- This function outputs different kind of greetings to
+# your screen. Use this function to understand how centos-art.sh
+# script specific functionalities work.
+#
+# Copyright (C) YEAR YOURFULLNAME
+#
+# 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.
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+function greet {
+
+ # Define command-line interface.
+ greet_getOptions
+
+ # Execute action name.
+ if [[ $ACTIONNAM =~ "^${FUNCNAM}_[A-Za-z]+$" ]];then
+ eval $ACTIONNAM
+ else
+ cli_printMessage "`gettext "A valid action is required."`" 'AsErrorLine'
+ cli_printMessage "${FUNCDIRNAM}" 'AsToKnowMoreLine'
+ fi
+
+}
+@end verbatim
+
+The first definition inside @code{greet} function is for variables
+that will be available along the whole execution environment of
+@code{greet} function. This time we didn't define any variable here
+so, we continued with definition of command-line interface, through
+@code{greet_getOptions} function.
+
+The command-line interface of @code{greet} functionality defines how
+to interpret arguments passed from @command{centos-art.sh} script
+command-line. Inside @command{centos-art.sh} script, the
+interpretation of arguments passed through its command-line takes
+place by mean of @command{getopt} command and is written as the
+following code example describes:
+
+@verbatim
+function greet_getOptions {
+
+ # Define short options we want to support.
+ local ARGSS=""
+
+ # Define long options we want to support.
+ local ARGSL="hello:,bye:,quiet"
+
+ # Redefine ARGUMENTS variable using getopt output.
+ cli_doParseArguments
+
+ # Redefine positional parameters using ARGUMENTS variable.
+ eval set -- "$ARGUMENTS"
+
+ # Look for options passed through command-line.
+ while true; do
+
+ case "$1" in
+
+ --hello )
+ ACTIONNAM="${FUNCNAM}_sayHello"
+ ACTIONVAL="$2"
+ shift 2
+ ;;
+
+ --bye )
+ ACTIONNAM="${FUNCNAM}_sayGoodbye"
+ ACTIONVAL="$2"
+ shift 2
+ ;;
+
+ --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
+ # begining 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_doParseArgumentsReDef "$@"
+
+}
+@end verbatim
+
+The @code{greet_sayHello} and @code{greet_sayGoodbye} function definitions
+are the core of @code{greet} specific functionality. In such function
+definitions we set what our @code{greet} function really does: to
+output different kinds of greetings.
+
+@verbatim
+function greet_sayHello {
+
+ cli_printMessage "`gettext "Hello"`, $ACTIONVAL"
+
+}
+@end verbatim
+
+The @code{greet_sayHello} function definition is stored in
+@file{greet_sayHello.sh} function script.
+
+@verbatim
+function greet_sayGoodbye {
+
+ cli_printMessage "`gettext "Goodbye"`, $ACTIONVAL"
+
+}
+@end verbatim
+
+The @code{greet_sayGoodbye} function definition is stored in the
+@file{greet_sayGoodbye.sh} function script.
+
+@subsubheading Executing the @code{greet} functionality
+
+To execute the @code{greet} specific functionality we've just created,
+pass the function name (i.e., @code{greet}) as first argument to
+@file{centos-art.sh} script and any of the valid options after it.
+Some examples are illustrated below:
+
+@verbatim
+[centos@projects ~]$ centos-art greet --hello='World'
+Hello, World
+[centos@projects ~]$ centos-art greet --bye='World'
+Goodbye, World
+[centos@projects ~]$ centos-art greet --bye='World' --quiet
+[centos@projects ~]$
+@end verbatim
+
+The word @samp{World} in the examples above can be anything. Likewise,
+if you need to change the way either the hello or goodbye messages are
+printed out, you can modifie the functions @code{greet_sayHello} and
+@code{greet_sayGoodbye}, respectively.
+
+@subsubheading Documenting the @command{greet} functionality
+
+Now that @code{greet} functionality works as we expect, it is time to
+document it. To document functionalities inside
+@command{centos-art.sh} script we use the function directory path as
+argument to the @code{help} functionality (@pxref{Directories trunk
+Scripts Functions Help}) of @file{centos-art.sh} script, just as the
+following command illustrates:
+
+@verbatim
+centos-art help --edit trunk/Scripts/Functions/Greet
+@end verbatim
+
+The function documentation helps to understand how the function really
+works and how it should be used. Also, when @command{centos-art.sh}
+script ends because an error, the documentation entry related to the
+functionality being currently executed is used as vehicle to
+communicate the user what is the correct way of using the
+functionality.
+
+@subsubheading Localizing the @command{greet} functionality
+
+Now that @code{greet} functionality has been documented, it is time to
+localize its output messages. Localizing specific functionalities of
+@command{centos-art.sh} script takes place as part of
+@command{centos-art.sh} script localization itself which is performed
+by applying the path @file{trunk/Scripts} to the @code{locale}
+functionality of @command{centos-art.sh} script.
+
+As the @code{greet} functionality added new translatable strings to
+the @command{centos-art.sh} script, it is required to update the
+translation messages firstly, to add the new translatable strings from
+@code{greet} functionality to @command{centos-art.sh} script
+translation messages and then, edit the translation messages of
+@command{centos-art.sh} script to localize the new translatable
+strings that have been added. To achieve this, execute the following
+two commands:
+
+@verbatim
+centos-art locale --update trunk/Scripts
+@end verbatim
+
+@verbatim
+centos-art locale --edit trunk/Scripts
+@end verbatim
+
+@quotation
+@strong{Warning} To translate output messages in different languages,
+your system locale information ---as in @env{LANG} environment
+variable--- must be set to that locale you want to produce translated
+messages for. For example, if you want to produce translated messages
+for Spanish language, your system locale information must be set to
+@samp{es_ES.UTF-8}, or similar, before executing the @code{locale}
+functionality of @command{centos-art.sh} script.
+@end quotation
+
+Well, it seems that our example is rather complete by now.
+
+@subsubheading Extending the @code{greet} functionality
+
+In the @code{greet} functionality we've described so far, we only use
+@code{cli_printMessage} function in action specific function
+definitions in order to print messages, but more interesting things
+can be achieved inside action specific function definitions. For
+example, if you pass a directory path as argument, you could use it to
+retrive a list of files from therein and process them. If the list of
+files turns too long or you just want to control which files to
+process, so you could add another argument in the form
+@option{--filter='regex'} and reduce the list of files to process
+using a regular expression pattern.
+
+In case you consider to extend the @code{greet} functionality to do
+something different but print out grettings, consider changing the
+function name from @code{greet} to something more appropriate, as
+well. The name change must be coherent with the actions the new
+function is designed to perform.
+
+If you doubt what name is better for your functionality, write to
+@email{centos-devel@@centos.org} mailing list, explain what your
+functionality intends to do and request suggestion about what name
+would be more appropriate for it. That would be also very convenient
+for you, in order to evaluate the purposes of your function and what
+the community thinks about it. It is a way for you to gather ideas
+that help you to write using the community feeling as base.
+
+If your function passes the community evaluation, that is a good sign
+for you to start/keep writing it. However, if it doesn't, it is time
+for you to rethink what you are doing and ask again until it passes
+the community evaluation. You can considered you've passed the
+community evaluation when after proposing your idea, you get a
+considerable amount of possitve responses for what you are doing,
+specially if those responses come from community leaders.
+
+It is very hard to do something useful for a community of people
+without any point of contact with that community you are trying to do
+things for. How could you know you are doing something that is needed
+if you don't know what the needs are? So, explore the community needs
+first, define them, work them out and repeat the process time after
+time, even when you might think the need has been already satisfied.
+At that point, surely, you'll find smaller needs that need to be
+satisfied, as well.
+
+@subsubheading Conclusions
+
+The @code{greet} functionality described in this section may serve as
+introduction for you to understand how specific functionalities are
+created inside @file{centos-art.sh} script. With some of luck this
+introduction will also serve you as motivation to create your own
+specific functionalities for @file{centos-art.sh} script.
+
+By the way, the @code{greet} functionality doesn't exist inside
+@file{centos-art.sh} script yet. Would you like to create it?
+
+@subheading Usage
+
+The following specific functions of @file{centos-art.sh} script, are
+available for you to use:
+
+@itemize
+@item @xref{Directories trunk Scripts Functions Help}.
+@item @xref{Directories trunk Scripts Functions Locale}.
+@item @xref{Directories trunk Scripts Functions Prepare}.
+@item @xref{Directories trunk Scripts Functions Render}.
+@item @xref{Directories trunk Scripts Functions Tuneup}.
+@end itemize
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk Scripts}
+@item @ref{Directories trunk}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Help.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Help.texinfo
new file mode 100644
index 0000000..4b39f76
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Help.texinfo
@@ -0,0 +1,179 @@
+@subheading Name
+
+The @code{help} functionlity is part of @command{centos-art.sh} script
+and standardizes documentation tasks inside the working copy of CentOS
+Artwork Repository.
+
+@subheading Synopsis
+
+@command{centos-art help [OPTIONS] path/to/dir @dots{}}
+
+The @file{path/to/dir} parameter specifies what directory structure
+inside the working copy of CentOS Artwork Repository you want to
+process.
+
+The @code{help} functionality of @command{centos-art.sh} script
+accepts the following options:
+
+@table @option
+@item --quiet
+
+Supress all output messages except error messages. When this option
+is passed, all confirmation requests are supressed as well and a
+possitive answer is assumed for them, just as if the
+@option{--answer-yes} option had been provided.
+
+@item --answer-yes
+
+Assume `yes' to all confirmation requests.
+
+@item --dont-commit-changes
+
+Supress all commit and update actions realized over files, before and
+after the action itself had took place over files in the working copy.
+
+@item --backend="STRING"
+
+Specifies the documentation system used as backend to manage the
+repository documentation manual. When this option is not provided, the
+@samp{texinfo} documentation system is used as default backend.
+
+@item --search="STRING"
+
+Go to node pointed by index entry @samp{STRING}.
+
+@item --edit "path/to/dir"
+
+Edit documentation entry related to path specified by
+@file{path/to/dir}.
+
+The @file{path/to/dir} must point to any directory inside the
+repository. When more than one @file{path/to/dir} are passed as
+non-option arguments to the @command{centos-art.sh} script
+command-line, they are queued for further edition. The edition itself
+takes place through your default text editor (e.g., the one you
+specified in the @env{EDITOR} environment variable) and the text
+editor opens one file at time (i.e., the queue of files to edit is not
+loaded in the text editor.).
+
+@item --read "path/to/dir"
+
+Read documentation entry specified by @file{file/to/dir} path. This
+option is used internally by @command{centos-art.sh} script to print
+out the reference you can follow to know more about an error message.
+
+@item --update
+
+Update output files rexporting them from the specified backend source
+files.
+
+@item --copy "path/to/srcdir" "path/to/dstdir"
+
+Duplicate documentation entries inside the working copy of CentOS
+Artwork Repository.
+
+When documentation entries are copied, only two non-option arguments
+can be passed to @command{centos-art.sh} script. In this case, the
+first non-option argument is considered the source location and the
+second one the target location. Both source location and target
+location must point to a directory under the working copy or files
+under @file{trunk/Manuals/Texinfo/Directories} directory structure.
+
+@item --delete "path/to/dir"
+
+Delete documentation entries inside the working copy of CentOS
+Artwork Repository.
+
+@item --rename "path/to/srcdir" "path/to/dstdir"
+
+Rename documentation entries inside the working copy of CentOS Artwork
+Repository.
+
+When documentation entries are renamed, only two non-option arguments
+can be passed to @command{centos-art.sh} script. In this case, the
+first non-option argument is considered the source location and the
+second one the target location. Both source location and target
+location must point to a directory under the working copy or files
+under @file{trunk/Manuals/Texinfo/Directories} directory structure.
+
+@end table
+
+When documentation entries are removed (e.g., through
+@option{--delete} or @option{--rename} options), the
+@command{centos-art.sh} script takes care of updating nodes, menus and
+cross references related to documentation entries in order to keep the
+manual structure in a correct state.
+
+@subheading Description
+
+Inside the CentOS Artwork Repository, The CentOS Project corporate
+identity is organized through directories. Each directory inside the
+repository responds to one or more conceptual ideas. Conceptual ideas
+are implemented through files.
+
+The @code{help} functionality of @command{centos-art.sh} script uses
+the repository directory layout as reference to document the
+conceptual ideas it is based on. Each directory inside the repository
+can be documented, in order to provide the explanation of what it is
+for and how automation scripts use it.
+
+@quotation
+@strong{Caution} When the repository directory layout changes, the
+documentation layout related must be changed as well in order for both
+locations to be consistent in their paths. Otherwise, you may end up
+having documentation entries that point to unexistent directories in
+the repository.
+@end quotation
+
+Files inside the repository are not documented. The only exception to
+this rule are files under @file{trunk/Manuals} directory, the place
+where documentation source files are stored in. Inside this location
+you can refer files for direct actions using the @code{help}
+functionality of @command{centos-art.sh} script. File actions, in this
+location, are also used to manage specific parts of the manual which
+have no association outside @file{trunk/Manuals} directory (e.g.,
+Preface, Introduction, etc.).
+
+@subsubheading Documentation backends
+
+Documentation backends are organized in @xref{Directories trunk
+Scripts Functions Help Backends}.
+
+@subheading Examples
+
+@table @command
+@item centos-art help --edit trunk/Identity
+
+This command edits the documentation entry related to
+@file{trunk/Identity} directory.
+
+@item centos-art help --read trunk/Identity
+
+This command reads the doumentation entry related to
+@file{trunk/Identity} directory in info format.
+
+@end table
+
+@subheading Author
+
+Written by Alain Reguera Delgado.
+
+@subheading Reporting bugs
+
+Report bugs to @email{centos-artwork@@centos.org} mailing list.
+
+@subheading Copyright
+
+Copyright @copyright{} 2009, 2010, 2011 The CentOS Project.
+
+This is free software. You may redistribute copies of it under the
+terms of the GNU General Public License (@pxref{GNU General Public
+License}). There is NO WARRANTY, to the extent permitted by law.
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk Scripts Functions}
+@item @ref{Directories trunk Scripts}
+@item @ref{Directories trunk}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Help/Backends.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Help/Backends.texinfo
new file mode 100755
index 0000000..be8b256
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Help/Backends.texinfo
@@ -0,0 +1,34 @@
+@subheading @code{texinfo}
+
+When @code{texinfo} backend is used (default behaviour), the manual
+structure (@pxref{Directories trunk Manuals}) is supported by GNU
+Texinfo, a documentation system that can produce both online
+information and a printed manual from a single source. The @code{help}
+functionality is an interface you can use to control the source files
+in the manual structure.
+
+The manual output is produced from Texinfo files and stored in
+@file{trunk/Manuals/Texinfo} on different formats including Info, PDF,
+XHTML, XML and TXT.
+
+When the @samp{texinfo} backend is used, you'll always edit
+documentation entries in English language, no matter what your
+prefered language be. This way, the output produced from them will
+always be in English language. To achieve the manual localization in
+your prefered language you need to apply the @code{locale}
+functionality of @command{centos-art.sh} script (@pxref{Directories
+trunk Scripts Functions Locale}) to any of the XML-based English
+outputs supported by @command{centos-art.sh} script (e.g., XHTML) to
+produce portable objects for your prefered language and the
+@code{render} functionality of @command{centos-art.sh} script
+(@pxref{Directories trunk Scripts Functions Render}) to produce the
+translated version of the output XHTML files taken in first place. The
+translated version is produced in the same format of the file taken as
+reference to build the portable objects. XHTML format in this case.
+
+@subheading @code{linuxdoc}
+Not supported yet.
+
+@subheading @code{docbook}
+
+Not supported yet.
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Locale.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Locale.texinfo
new file mode 100644
index 0000000..0eb5ff4
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Locale.texinfo
@@ -0,0 +1,255 @@
+@subheading Name
+
+The @code{locale} functionlity is part of @command{centos-art.sh}
+script and standardizes localization tasks inside the working copy of
+CentOS Artwork Repository.
+
+@subheading Synopsis
+
+@command{centos-art locale [OPTIONS] path/to/dir}
+
+The @file{path/to/dir} parameter specifies what directory structure
+inside the working copy of CentOS Artwork Repository you want to
+create translation messages for.
+
+The @code{locale} functionality of @command{centos-art.sh} script
+accepts the following options:
+
+@table @option
+@item --quiet
+
+Supress all output messages except error messages. When this option
+is passed, all confirmation requests are supressed as well and a
+possitive answer is assumed for them, just as if the
+@option{--answer-yes} option had been provided.
+
+@item --answer-yes
+
+Assume `yes' to all confirmation requests.
+
+@item --filter="REGEX"
+
+Reduce the list of files to process using @samp{REGEX} as pattern.
+You can use this option in combination with @file{path/to/dir} in
+order to control the amount of files you want to produce as
+base-rendition. The deeper you go into the directory structure the
+more specific you'll be about the component you want to produce. When
+you cannot go deeper into the directory structure, you can use
+@option{--filter} option to reduce the list of files.
+
+@item --dont-commit-changes
+
+Supress all commit and update actions realized over files, before and
+after the action itself had took place over files in the working copy.
+
+@item --update
+
+This option extracts translatable strings from both XML-based files
+(using @command{xml2po}) and shell scripts (using @command{xgettext})
+under @file{path/to/dir}. Translatable strings are initially stored in
+portable objects templates (.pot) which are later merged into portable
+objects (.po) in order to be converted as machine objects (.mo).
+
+Use this option each time you change translatable stirngs inside
+design models and script files.
+
+@item --edit
+
+This option edits the portable object related to @file{path/to/dir}
+location.
+
+Use this option after updating portable objects (through
+@option{--update} option) in order to change the language-specific
+information of translatable strings.
+
+@item --dont-create-mo
+
+This option supresses the creation of machine objects.
+
+@end table
+
+@subheading Description
+
+The CentOS Artwork Repository exists to cover the visual needs of The
+CentOS Project Corporate Identity. The CentOS Project is an
+internationl project and sometimes requires contents in different
+languages. So, in that sake, the CentOS Artwork Repository is designed
+to produce content in as many locales as supported by The CentOS
+Distribution, the platform that supports the whole CentOS Artwork
+Repository, both in workstations and server.
+
+@quotation
+@strong{Tip} To know what locales are supported by The CentOS
+Distribution you are currently using, run the following command:
+
+@verbatim
+locale -a | less
+@end verbatim
+@end quotation
+
+The localization process is very tied to the input files we want to
+provide localized messages for. Inside the CentOS Artwork Repository,
+it is possible to localize XML files (e.g., SVG, XHTML, Docbook) and
+programs written in most popular programming languages (e.g., C, C++,
+C#, Shell Scripts, Python, Java, GNU awk, PHP, etc.).
+
+@subsubheading Design models localization
+
+Design models are used as input to produce most images and some other
+contents as well. Design models are always XML-based files (e.g., SVG,
+XHTML, Docbook), so the @code{locale} functionality uses the
+@command{xml2po} program to create protable objects from them under
+@file{trunk/Locales/Models} directory. Portable objects contain the
+relation between message id and message translation, as translator,
+need to take care of.
+
+Thanks to @command{xml2po}, it is possible for the @code{locale}
+functionality to separate designing tasks from the translating tasks.
+It is possible for graphic designers to concentrate their efforts on
+designing models in English language while translators take care of
+their localization using the @option{--update} and @option{--edit}
+options as much as it be needed.
+
+Once design models have been localized, rendering them in different
+language is a matter using the @code{render} functionality of
+@command{centos-art.sh} script. @xref{Directories trunk Scripts
+Functions Render}, for more information about it.
+
+@subsubheading Shell script localization
+
+The @code{locale} functionality is used to localize the
+@command{centos-art.sh} script itself. The @command{centos-art.sh}
+script is a shell script written in Bash, so the @code{locale}
+functionality uses the @command{gettext} tools to retrive translatable
+strings, create portable objects and machine objects.
+
+Thanks to @command{gettext}, it is possible for the @code{locale}
+functionality to separate programming tasks from the translating
+tasks. It is possible for programmer to concentrate their efforts in
+programming output messages in English language while translators take
+care of their localization using the @option{--update} and
+@option{--edit} options as much as it be needed.
+
+Once @command{centos-art.sh} script has been localized, the translated
+messages should be immediatly visible to you, the next time you
+execute the @command{centos-art.sh} script
+
+@quotation
+@strong{Note}
+In order to localize translatable strings from English language to
+another language you need to be sure the @env{LANG} environment
+variable has been already set to the locale code you want to localize
+message for or see them printed out before running the
+@command{centos-art.sh} script. Localizing English language to itself
+is not supported.
+@end quotation
+
+@subheading Examples
+
+@table @command
+@item centos-art locale --update trunk/Identity/Models/Default/Distro/5/Anaconda
+
+This command updates portable objects related to Anaconda default
+design models of The CentOS Distribution major release 5. The update
+action consists on adding new translatable strings or removing old
+translatable strings from portable objects in order to keep both the
+portable object and the design model consistent.
+
+This command is executed by translators once the graphic designers
+have committed updates to Anaconda default design models (e.g., slide
+text changes).
+
+@item centos-art locale --edit trunk/Identity/Models/Default/Distro/5/Anaconda
+
+This command let translators to edit portable objects related to
+Anaconda default design models of The CentOS Distribution major
+release 5. The edit action is where the translator localize
+translatable strings in English language to another language.
+
+When portable objects for XML-base files are produced, there is no
+need to retain the machine object format, so we the
+@option{--dont-create-mo} is automatically assumed.
+
+@item centos-art locale --update trunk/Scripts
+
+This command updates portable objects related to
+@command{centos-art.sh} script. The update action consists on adding
+new translatable strings or removing old translatable strings from
+portable objects in order to keep both the portable object and the
+@command{centos-art.sh} script to be consistent one another.
+
+This command is executed by translators once the programmers have
+committed updates @command{centos-art.sh} script.
+
+@item centos-art locale --edit trunk/Scripts
+
+This command edits portable objects related to @command{centos-art.sh}
+script in your prefered language.
+
+@item centos-art locale --update trunk/Manual/repository.xhtml
+
+This command updates portable objects for the XHTML output of the
+repository documentation manual. The portable objects are created in
+your prefered language and can be used to produced localized versions
+of the manual in XHTML format.
+
+The update action consists on adding new translatable strings to or
+removing old translatable strings from the portable objects in order
+to keep both the portable object and the manual XHTML output
+consistent one another.
+
+People execute this command after committing changes to the repository
+documentation manual.
+
+@item centos-art locale --edit trunk/Manual/repository.xhtml
+
+This command takes all the repository documentation manual XHTML
+output files, which have not been translated yet inside the
+@file{trunk/Manual/repository.xhtml} directory, as input to produce
+portable objects from them so as for you to localize translatable
+strings to your prefered language (e.g., as specified by the
+@env{LANG} environment variable).
+
+Once the portable objects have been created they are used to produce
+the translated version of the manual in XHTML format under the
+@file{trunk/Manual/repository.xml/LANG} directory, where @samp{LANG}
+refers your prefered language. The translated version of the XHTML
+files is produced using the @code{render} functionality of
+@command{centos-art.sh} script (@pxref{Directories trunk Scripts
+Functions Render}).
+
+When your prefered language is other but English, the
+@command{centos-art.sh} script takes care of updating both the
+portable objects and the translated version of files after you've
+edited a manual documentation entry, using the @code{help}
+functionality of @command{centos-art.sh} script (@pxref{Directories
+trunk Scripts Functions Help}). In other situations, you need to do
+these actions by yourself.
+
+@end table
+
+@subheading Author
+
+Written by Alain Reguera Delgado.
+
+@subheading Reporting bugs
+
+Report bugs to @email{centos-artwork@@centos.org} mailing list.
+
+@subheading Copyright
+
+Copyright @copyright{} 2009, 2010, 2011 The CentOS Project.
+
+This is free software. You may redistribute copies of it under the
+terms of the GNU General Public License (@pxref{GNU General Public
+License}). There is NO WARRANTY, to the extent permitted by law.
+
+@subheading See also
+
+@itemize
+@item The GNU @command{gettext} tools documentation (@command{info gettext})
+@item The @command{xml2po} command documentation (@command{man xml2po})
+@item @ref{Directories trunk Scripts Functions}
+@item @ref{Directories trunk Scripts}
+@item @ref{Directories trunk}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Prepare.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Prepare.texinfo
new file mode 100644
index 0000000..ea9f743
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Prepare.texinfo
@@ -0,0 +1,305 @@
+@subheading Name
+
+The @code{prepare} functionality is part of the
+@command{centos-art.sh} script and standardizes configuration of
+preliminar steps you need to follow in order to get your workstation
+ready for using a working copy of CentOS Artwork Repository.
+
+@subheading Synopsis
+
+@command{centos-art prepare [OPTIONS]}
+
+There is no need to specify @file{path/to/dir} information in this
+functionality. Most actions are performed through options.
+
+The @code{prepare} functionality of centos-art.sh script accepts the
+following options:
+
+@table @option
+
+@item --quiet
+
+Supress all output messages except error messages. When this option
+is passed, all confirmation requests are supressed as well and a
+possitive answer is assumed for them, just as if the
+@option{--answer-yes} option had been provided.
+
+@item --answer-yes
+
+Assume @samp{yes} to all confirmation requests.
+
+@item --packages
+
+Install/update software packages required by the working copy of
+CentOS Artwork Repository.
+
+The process of software installation takes place through @command{sudo
+yum} and the repository configuration currently set in your
+workstation.
+
+Most of the software packages required by the working copy of CentOS
+Artwork Repository are available on The CentOS Distribution and can be
+installed using The CentOS Distribution installation media. The only
+exception is Inkscape, the program used to manipulate
+@acronym{SVG,Scalable Vector Graphics} files in the working copy.
+
+The @file{inkscape} package isn't inside The CentOS Distribution or
+any of The CentOS Project repositories neither, so you need to install
+it from a third party repository like @samp{RPMForge} or @samp{EPEL}.
+See page
+@url{http://wiki.centos.org/AdditionalResources/Repositories/,The
+CentOS Repositories}, to know how to configure third party
+repositories in The CentOS Distribution.
+
+@item --link
+
+This option uses symbolic links to install/update the connection
+between components inside the working copy and components outside the
+working copy. Among the components that need to be connected figure
+out the command-line internface of @command{centos-art.sh} script;
+fonts, brushes, palettes and patterns used by programs like GIMP and
+Inkscape; and configuration files of text editors.
+
+The main purpose of such connection is to adapt the working copy to
+the CentOS Distribution filesystem layout (e.g., @file{~/bin}
+directory is for storing personal programs, @file{~/gimp-2.2/brushes}
+is for storing GIMP brushes for personal use, etc.) and, at the same
+time, to provide a way of sharing changes made to connected components
+to other workstations (e.g., if I update a GIMP brush in my
+workstation, you'll receive the change the next you update your
+working copy and then will be immediatly available for you to use in
+GIMP).
+
+@item --environment
+
+Print the name and value of some of the environment variables used by
+@command{centos-art.sh} scripts.
+
+@end table
+
+@subheading Description
+
+The @code{prepare} functionality of @command{centos-art.sh} script is
+part of the CentOS Artwork Repository. So, in order to execute the
+@code{prepare} functionality of @command{centos-art.sh} script you
+need to have access to a working copy of CentOS Artwork Repository,
+first. Working copies of CentOS Artwork Repository are downloaded
+from the source repository and made available to you by mean of
+workstations. A workstation is a computer that you install and
+configure (prepare) to do something. In this case, you pick up a
+computer and prepare it for working on the CentOS Artwork Repository.
+
+@subsubheading Installing the workstation
+
+Installing the workstation is the first step you need to do. In this
+step you make your computer functional through an operating system. In
+this case, The Community Enterprise Operating System; which is also
+know as The CentOS Distribution or just CentOS, for short.
+
+To install The CentOS Distribution you need to have the installation
+media somehow (e.g., CDs, DVDs, Pendrives, etc.). There are several
+different ways to perform the installation process of CentOS
+distribution, but generally, you put the installation media in your
+media reader, boot the computer from it, and follow the installer
+intructions. That simple.
+
+If you don't have the installation media of CentOS distribution, you
+need to download the ISO files related to the media you plan to use
+(e.g., CD or DVD) and then create the installation media by yourself.
+The CentOS Distribution ISO files can be downloaded from
+@url{http://mirrors.centos.org/} and, if you chosen CD or DVD as your
+prefered installation medium, you can burn the ISO files using the
+@command{K3B} application so as to create the installation media
+you'll use. Of course, in order to download the ISO files and create
+the installation media, you need to have an already installed CentOS
+workstation where you can realized all the work.
+
+@subsubheading Configuring the workstation
+
+Once you've installed the workstation and it is up and running, login
+as @samp{root} user, create a username (e.g., @samp{centos}) and set a
+password for it. This is the username you must use for everyday work
+inside your working copy of the CentOS Artwork Repository.
+
+@quotation
+@strong{Caution} Do not use the @samp{root} username for your everyday
+work inside the working copy of CentOS Artwork Repository. It is
+dangerous and might provoke unreversable damages on your workstation.
+@end quotation
+
+Once you've created the username for your everyday work, there are
+some environment variables that you can customize to fit your personal
+needs (e.g., default text editor, default locale information, default
+time zone representation, etc.). To customize these variables you
+need to edit your profile file (i.e., @file{~/.bash_profile}) and set
+the redefinition there. Notice that you may need to logout and then
+do login again in order for the new variable values to take effect.
+
+@table @strong
+@item Default text editor:
+
+The default text editor information is contrlled by the @env{EDITOR}
+environment variable. The @file{centos-art.sh} script uses the default
+text editor to edit subversion pre-commit messages, translation files,
+documentation files, script files, and similar text-based files.
+
+If @env{EDITOR} environment variable is not set, @file{centos-art.sh}
+script uses @file{/usr/bin/vim} as default text editor. Otherwise, the
+following values are recognized by @file{centos-art.sh} script:
+
+@itemize
+@item @file{/usr/bin/vim}
+@item @file{/usr/bin/emacs}
+@item @file{/usr/bin/nano}
+@end itemize
+
+If no one of these values is set in the @env{EDITOR} environment
+variable, the @file{centos-art.sh} script uses @file{/usr/bin/vim}
+text editor, the one installed by default in The CentOS Distribution.
+
+@item Default locale information:
+
+The default locale information is controlled by the @env{LANG}
+environment variable. This variable is initially set in the
+configuration process of CentOS distribution installer, specifically
+in the @samp{Language} step; or once installed using the
+@command{system-config-language} tool.
+
+The @command{centos-art.sh} script uses the @env{LANG} environment
+variable to determine what language to use for printing output
+messages. Another use of @env{LANG} variable inside
+@command{centos-art.sh} script is to determine what translation file
+to update or edit when input files are localized.
+
+@item Default time zone representation:
+
+The time zone representation is a time correction applied to the
+system time (stored in the BIOS clock) based on your country location.
+This correction is specially useful to distributed computers around
+the world that work together and need to be syncronized in time to
+know when things happened.
+
+The CentOS Artwork Repository is made of one server and several
+workstations spread around the world. In order for all these
+workstations to know when changes in the server took place, it is
+required that they all set their system clocks to use the same time
+information (i.e., @acronym{UTC,Coordinated Universal Time}) and set
+the time correction for their specific countries in the operating
+system. Otherwise, it would be difficult to know when something
+exactly happened.
+
+Generally, setting the time information is a straight-forward task and
+configuration tools provided by The CentOS Distribution do cover time
+correction for most of the countries around the world. However, if
+you need a time precision not provided by any of the date and time
+configuration tools provided by The CentOS Distribution then, you need
+to use the @env{TZ} environment variable to correct the time
+information by yourself. The format of @env{TZ} environment variable
+is described in @file{tzset(3)} manual page.
+@end table
+
+@subsubheading Downloading the working copy
+
+Once you've configured the workstation, it is time to download the
+working copy of CentOS Artwork Repository.
+
+To download the working copy of CentOS Artwork Repository you need to
+login as your everyday work username (e.g., @samp{centos}) and use the
+Subversion client to bring all the files you need to work with down
+from the source location of CentOS Artwork Repository
+(@url{https://projects.centos.org/svn/artwork/}) to your workstation,
+just as the following command describes:
+
+@verbatim
+svn co https://projects.centos.org/svn/artwork ~/
+@end verbatim
+
+This command will create the working copy of CentOS Artwork Repository
+in your workstation, specifically in the @file{/home/centos/artwork}
+directory. Note that you only need to execute this command once.
+After that, to keep your working copy up to date, you use the
+Subversion @command{update} command instead.
+
+@quotation
+@strong{Tip} In the condition that you don't have Subversion client
+installed in the workstation, then you can install it using the
+command:
+
+@verbatim
+sudo yum install subversion
+@end verbatim
+@end quotation
+
+@subsubheading Configuring the working copy
+
+Once you have a working copy of CentOS Artwork Repository in your
+workstation, you can go and run the @code{prepare} functionality of
+@command{centos-art.sh} script to realize the remaining configuration
+stuff.
+
+Assuming this is the very first time you run the
+@command{centos-art.sh} script, you'll find that there is no
+@command{centos-art} command-line interface for it in your
+workstation. This is correct. In order to have the
+@command{centos-art} command-line in your workstation, you need to run
+the @command{centos-art.sh} script using its absolute path:
+
+@verbatim
+~/artwork/trunk/Scripts/centos-art.sh prepare [OPTIONS]
+@end verbatim
+
+Assuming you've already run the @code{prepare} functionality
+before, there is no need for you to use the absolute path again.
+Instead, you can use the @command{centos-art} command-line interface
+directly, as the following example describes:
+
+@verbatim
+centos-art.sh prepare [OPTIONS]
+@end verbatim
+
+Notice that you can execute the @code{prepare} functionality more than
+once. This is specially useful to keep the link information
+syncronized. For example, considering you've added new brushes to or
+removed old brushes from your working copy of CentOS Artwork
+Repository, the link information related to those files need to be
+updated in the @file{~/.gimp-2.2/brushes} 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 components.
+
+@subheading Examples
+
+@table @command
+@item centos-art prepare --packages --link
+Preapare both links and packages required to use the working copy of
+CentOS Artwork Repository in the workstation. If required packages are
+already installed this command looks for updates instead.
+
+@item centos-art prepare --link --quiet
+Update connection between the workstation and the working copy of
+CentOS Artwork Repository, using no output.
+@end table
+
+@subheading Author
+
+Written by Alain Reguera Delgado.
+
+@subheading Reporting bugs
+
+Report bugs to @email{centos-artwork@@centos.org} mailing list.
+
+@subheading Copyright
+
+Copyright @copyright{} 2009, 2010, 2011 The CentOS Project.
+
+This is free software. You may redistribute copies of it under the
+terms of the GNU General Public License (@pxref{GNU General Public
+License}). There is NO WARRANTY, to the extent permitted by law.
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk Scripts Functions}
+@item @ref{Directories trunk Scripts}
+@item @ref{Directories trunk}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Render.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Render.texinfo
new file mode 100644
index 0000000..36b5c2d
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Render.texinfo
@@ -0,0 +1,373 @@
+@subheading Name
+
+The @code{render} functionlity is part of @command{centos-art.sh}
+script and standardizes rendition tasks inside the working copy of
+CentOS Artwork Repository.
+
+@subheading Synopsis
+
+@command{centos-art render [OPTIONS] path/to/dir}
+
+The @file{path/to/dir} parameter specifies what directory structure
+inside the working copy of CentOS Artwork Repository you want to
+produce.
+
+The @code{render} functionality of @command{centos-art.sh} script
+accepts the following options:
+
+@table @option
+@item --quiet
+
+Supress all output messages except error messages. When this option
+is passed, all confirmation requests are supressed as well and a
+possitive answer is assumed for them, just as if the
+@option{--answer-yes} option had been provided.
+
+@item --answer-yes
+
+Assume `yes' to all confirmation requests.
+
+@item --filter="REGEX"
+
+Reduce the list of files to process using @samp{REGEX} as pattern.
+You can use this option in combination with @file{path/to/dir} in
+order to control the amount of files you want to produce as
+base-rendition. The deeper you go into the directory structure the
+more specific you'll be about the component you want to produce. When
+you cannot go deeper into the directory structure, you can use
+@option{--filter} option to reduce the list of files.
+
+@item --dont-commit-changes
+
+Supress all commit and update actions realized over files, before and
+after the action itself had took place over files in the working copy.
+
+@item --releasever="STRING"
+
+This option expands release-specific translation makers to
+@samp{STRING}. Use this option when no releasae-specific information
+can be retrived from the path of the directory structure you are
+currently rendering.
+
+@item --basearch="STRING"
+
+This option expands architecture-specific translation makers to
+@samp{STRING}. Use this option when no architecture-specific
+information can be retrived from the path of the directory structure
+you are currently rendering.
+
+@item --theme-model="STRING"
+
+Specify the name of the theme model you want to use to produce theme
+artistic motifs. By default, if this option is not passed, the
+@samp{Default} theme model is used as reference to produce theme
+motifs.
+
+@item --post-rendition="STRING"
+
+This option let you apply a command as post-rendition action. In this
+case, the @samp{STRING} represents the command string you want to
+execute in order to perform in-place modifications to base-rendition
+output.
+
+@item --last-rendition="STRING"
+
+This option let you apply a command as last-rendition action. In this
+case, the @samp{STRING} 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.
+
+@end table
+
+@subheading Description
+
+Inside the working copy of CentOS Artwork Repository, rendition tasks
+take place inside renderable directories. Inside the @code{render}
+functionality of @command{centos-art.sh} script, you can control
+rendition tasks through different flows of rendition named
+base-rendition, post-rendition, last-rendition and directory-specific
+rendition.
+
+@subsubheading Renderable directories
+
+In order for a directory structure to be considered renderable, it
+should have one directory structure for input files and one directory
+structure for output files. Optionally, a third directory structure
+might be available for storing translation files.
+
+Renderable directories are very tied to the way content is produced
+inside the working copy of CentOS Artwork Repository. Presently,
+content is produced through the following organizations:
+
+@table @strong
+@item Direct rendition
+
+In direct rendition, there is one directory structure for input files
+(@file{trunk/Identity/Models}) and one directory structure for output
+files (e.g., @file{trunk/Identity/Images}). Optionally, a third
+directory structure is available to store the input related
+translation files (e.g., @file{trunk/Locales/Identity/Models}).
+
+In direct rendition, when the @code{render} functionality of
+@command{centos-art.sh} script is executed, it uses the input
+directory structure to build a list of files to process, which is used
+as reference to determine the location of the translation file and the
+location of the output file, as well.
+
+@item Theme-specific rendition
+
+In theme-specific rendition, there is one directory structure to store
+input files (@file{trunk/Identity/Themes/Models}), one directory
+structure to store translation files
+(@file{trunk/Locales/Identity/Themes/Models/}), one directory
+structure to store artistic motifs
+(@file{trunk/Identity/Images/Themes}) and one directory structure to
+store output files (@file{trunk/Identity/Images/Themes}).
+
+In theme-specific rendition, when the @code{render} functionality of
+@command{centos-art.sh} script is executed, it uses the input
+directory structure to build a list of files to process, which is used
+as reference to determine the location of the translation file and the
+location of the output file, as well.
+
+In contrast with direct rendition, when we use theme-specific
+rendition, it is possible to combine both design models and artistic
+motifs to produce output in an arbitrary way. This configuration is
+specially interesting because it is possible to create different
+artistic motifs and one unique design model in order to produce one
+unique theme structure with different visual styles. Or the opposite,
+to create different theme structures and apply one unique visual style
+to produce one unique visual styles on different theme structure. Or
+even get a bit farther and experiment with arbitrary combinations
+among them all.
+
+@end table
+
+In both direct and theme-specific rendition, if the location where the
+output file should be stored doesn't exist, the @code{render}
+functionality of @command{centos-art.sh} script will create it for
+you.
+
+In both direct and theme-specific rendition, if the input related
+translation file doesn't exist, the @code{render} functionality of
+@command{centos-art.sh} script will produce the output in the same
+language of its input file.
+
+@subsubheading The base-rendition flow
+
+The base-rendition flow is the first rendition flow of all rendition
+flows available and takes place immediatly after executing the
+@code{render} functionality of @command{centos-art.sh} script.
+
+The base-rendition produces different outputs from one unique input
+format. This is, one input file is used to produce one ore more output
+files. When translation files are available for input files, the
+base-rendition applies the translation file to the input file in order
+to produce a translated instance of it, then this translated instance
+is used as input file to produce one or more output files.
+
+Inside the @code{render} functionality of @command{centos-art.sh}
+script, the input format is always XML (e.g., SVG, XHTML, Docbook),
+the translation files are always portable objects (e.g., PO) and the
+output format depends on the input file provided (e.g., when the
+input format is a SVG file, the base output is a PNG file; when the
+input format is XHTML the base output is an XHTML file; when the input
+format is a Docbook file the base output might be either HTML, RTF, PS
+or PDF).
+
+As application example of base-rendition flow, consider the
+description of the following sections:
+
+@itemize
+@item @ref{Directories trunk Identity Models Themes Default Distro 5
+Anaconda}
+@item @ref{Directories trunk Identity Models Themes Default Distro 5.5
+Notes Release}
+@end itemize
+
+@subsubheading The post-rendition flow
+
+The post-rendition flow is performed immediatly after base-rendition
+flow to extend the base-rendition flow by applying in-place
+modifications to base-rendition output. In-place modifications can be
+performed either through the @option{--post-rendition} command-line
+option of @command{centos-art.sh} script or through directory-specific
+rendition.
+
+Actions commanded through @option{--post-rendition} option are applied
+first and directory-specific actions later. This order is required to
+propagate in-place changes commited to base-rendition output to
+modified copies (i.e., new files) of it created through
+directory-specific rendition. Creation of modified copies is
+something specific to directory-specific rendition only. It is not
+possible for the @option{--post-rendition} option to create modified
+copies of base-rendition flow because commands passed through it are
+applied to the base-rendition output file directly in a disposition
+that don't support creation of new files, but in-place modifications
+only.
+
+The command passed to @option{--post-rendition} option can be changed
+everytime you run the @command{centos-art.sh} script, but actions
+specified in directory-specific rendition cannot be changed in the
+same way. Direcctory-specific rendition is set inside
+@command{centos-art.sh} script to perform specific tasks that cannot
+be achived through @option{--post-rendition} option.
+
+As application example of post-rendition flow, consider the
+description of the following sections:
+
+@itemize
+@item @ref{Directories trunk Identity Models Themes Default Distro 5
+Syslinux}
+@item @ref{Directories trunk Identity Models Themes Default Distro 5
+Grub}
+@end itemize
+
+@subsubheading The last-rendition flow
+
+The last-rendition flow takes place after post-rendition and applies
+in-place modifications to all files produced as result of both
+base-rendition and post-rendition flows in the same directory
+structure, just before passing to process a different directory
+structure. In-place modifications can be performed either through the
+@option{--last-rendition} command-line option of
+@command{centos-art.sh} script or through directory-specific
+rendition.
+
+Actions commanded through @option{--last-rendition} option are applied
+after directory-specific actions. This order is required to prevent
+last-rendition actions commanded from directory-specifc rendition to
+overlap last-rendition actions commanded from
+@option{--last-rendition} option.
+
+The command passed to @option{--last-rendition} option can be changed
+everytime you run the @command{centos-art.sh} script, but actions
+specified in directory-specific rendition cannot be changed in the
+same way. Actions commanded from directory-specific rendition are set
+inside @command{centos-art.sh} script to perform specific tasks that
+cannot be achived through @option{--last-rendition} option.
+
+As application example of last-rendition flow, consider the
+description of the following sections:
+
+@itemize
+@item @ref{Directories trunk Identity Models Themes Default Distro 5
+Ksplash}
+@item @ref{Directories trunk Identity Models Themes Default Distro 5
+Gdm}
+@end itemize
+
+@subsubheading The directory-specific rendition flow
+
+Inside the working copy of CentOS Artwork Repository, some directory
+structure (e.g., @file{Syslinux}, @file{Gurb}, @file{Gdm}, @file{Kdm}
+and @file{KSplash}) required more than base-rendition or even the
+commands you could pass through the @option{--post-rendition} and
+@option{--last-rendition} options, in order for their final files to
+be produced. In these situations, we make use of directory-specific
+rendition flow.
+
+The directory-specific rendition flow applies specific actions to
+specific directory structures when they enter into the rendition flow.
+Using this configuration speeds up production of all those components
+that require intermediate formats or even several independent files,
+in order for the final content to be created.
+
+The directory-specific rendition flow is generally used in combination
+with post-rendition and last-rendition flows inside
+@command{centos-art.sh} script.
+
+@subsubheading Translations
+
+To translate output files, the @code{render} functionality of
+@command{centos-art.sh} script creates a translated instance of the
+input file and uses it then to create the base output file. The
+translated instance is created using the related translation messages
+of the input file. Translation messages are stored under
+@file{trunk/Locales} and are created using the @code{locale}
+functionality of @command{centos-art.sh} script (@pxref{Directories
+trunk Scripts Functions Locale}).
+
+Translation files are optional. When no translation file is available
+for the input file, the base-rendition output is produced using the
+same language of the input file.
+
+@subheading Examples
+
+@table @command
+@item centos-art render trunk/Identity/Images/Brands
+
+This command produces all branding information related to The CentOS
+Project (e.g., symbols, logos and variants of them).
+
+@item centos-art render trunk/Identity/Images/Brands --filter="symbol"
+
+This command produces all branding information, related to The CentOS
+Project, which file names contain the @samp{symbol} string on it.
+
+@item centos-art render trunk/Identity/Images/Themes/Flame/2
+
+This command produces all visual manifestations related to version 2 of
+Flame artistic motif (e.g., Distribution, Posters, etc.) as specified
+by default design models.
+
+@item centos-art render trunk/Identity/Images/Themes/Flame/2/Distro
+
+This command produces the Distribution visual manifestations related
+to version 2 of Flame artistic motif (e.g., Anaconda, Syslinux, Grub,
+Firstboot, Gdm, Kdm, Gsplash, Ksplash, and Rhgb) as specified by
+default design models.
+
+@item centos-art render trunk/Identity/Images/Themes --filter='Distro/5/Anaconda'
+
+This command produces all the images related to Anaconda component
+from Distribution visual manifestations on its major release number
+five, for all the artistic motifs available and as specified by
+default design models.
+
+@item centos-art render trunk/Identity/Images/Themes --filter='Concept' --post-rendition='mogrify -normalize'
+
+This command produces all the images related to Concept component from
+all artistic motifs as specified by default design models. Moreover,
+the @command{mogrify -normalize} command is applied to each PNG image
+produced as result of the base-rendition output.
+
+@quotation
+@strong{Note} The @command{mogrify} command is part of
+ImageMagick@registeredsymbol{} software suite and let you to resize an
+image, blur, crop, despeckle, dither, draw on, flip, join, re-sample,
+and much more. The ImageMagick@registeredsymbol{} software suite is
+copyrighted to
+@url{http://redux.imagemagick.org/MagickStudio/scripts/MagickStudio.cgi,
+ImageMagick Studio LLC}, a non-profit organization dedicated to making
+software imaging solutions freely available.
+
+@end quotation
+
+@end table
+
+@subheading Author
+
+Written by Alain Reguera Delgado.
+
+@subheading Reporting bugs
+
+Report bugs to @email{centos-artwork@@centos.org} mailing list.
+
+@subheading Copyright
+
+Copyright @copyright{} 2009, 2010, 2011 The CentOS Project.
+
+This is free software. You may redistribute copies of it under the
+terms of the GNU General Public License (@pxref{GNU General Public
+License}). There is NO WARRANTY, to the extent permitted by law.
+
+@subheading See also
+
+@itemize
+@item The ImageMagick@registeredsymbol{} software suite documentation
+(@command{rpm -qd ImageMagick | less}).
+@item @ref{Directories trunk Scripts Functions}
+@item @ref{Directories trunk Scripts}
+@item @ref{Directories trunk}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Tuneup.texinfo b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Tuneup.texinfo
new file mode 100755
index 0000000..2b6845d
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Directories/trunk/Scripts/Functions/Tuneup.texinfo
@@ -0,0 +1,190 @@
+@subheading Name
+
+The @code{tuneup} functionlity is part of @command{centos-art.sh}
+script and standardizes tasks related to file maintainance inside the
+working copy of CentOS Artwork Repository.
+
+@subheading Synopsis
+
+@command{centos-art tuneup [OPTIONS] path/to/dir}
+
+The @file{path/to/dir} parameter specifies what directory structure
+inside the working copy of CentOS Artwork Repository you want to
+process.
+
+The @code{tuneup} functionality of @command{centos-art.sh} script
+accepts the following options:
+
+@table @option
+@item --quiet
+
+Supress all output messages except error messages. When this option
+is passed, all confirmation requests are supressed as well and a
+possitive answer is assumed for them, just as if the
+@option{--answer-yes} option had been provided.
+
+@item --answer-yes
+
+Assume `yes' to all confirmation requests.
+
+@item --filter="REGEX"
+
+Reduce the list of files to process using @samp{REGEX} as pattern.
+You can use this option in combination with @file{path/to/dir} in
+order to control the amount of files you want to produce as
+base-rendition. The deeper you go into the directory structure the
+more specific you'll be about the component you want to produce. When
+you cannot go deeper into the directory structure, you can use
+@option{--filter} option to reduce the list of files.
+
+@item --dont-commit-changes
+
+Supress all commit and update actions realized over files, before and
+after the action itself had took place over files in the working copy.
+
+@end table
+
+@subheading Description
+
+Tasks related to file maintainance are repetitive. You might find
+yourself doing them time after time inside the working copy of CentOS
+Artwork Repository. 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.
+
+When you execute the @code{tuneup} functionality of
+@command{centos-art.sh} script, it looks for all files that match the
+supported extensions (e.g., @file{.sh}, @file{.svg} and @file{.xhtml})
+in the directory specified, builds a list with them and applies the
+maintainance tasks using file extensions as reference.
+
+@subsubheading Maintaining @file{.sh} files
+
+If shell scripts are found, the @code{tuneup} functionality of
+@command{centos-art.sh} script reads a comment template from
+@file{trunk/Scripts/Functions/Prepare/Config/shell_topcomment.sed} and
+applies it to 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.
+
+In order for the shell script top comment template to be applied
+correctly, the shell scripts you write must have the following
+structure:
+
+@verbatim
+ 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| }
+@end verbatim
+
+The @code{tuneup} functionality of @command{centos-art.sh} script
+replaces all lines between the @samp{Copyright} line (e.g., line 5)
+and the first separator line (e.g., line 9), inclusively. Everything
+else in the file will remain immutable.
+
+@subsubheading Maintaining @file{.svg} files
+
+If scalable vector graphics are found, the @code{tuneup} functionality
+reads a metadata template
+(@file{trunk/Scripts/Functions/Tuneup/Config/svg_metadata.sed}) 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 file, too.
+
+The metadata we apply from the metadata template is created dynamicaly
+combining the file absolute path, the workstation time information and
+the @command{centos-art.sh} script copyright holder information as
+reference. Additionally, the @emph{Creative Common
+Distribution-ShareAlike 3.0 License} is also set in the metadata.
+
+The elimination of unused definitions inside SVG files takes place
+through the @option{--vacuum-defs} option of @command{inkscape}
+command-line interface which is described in its man page
+(@command{man inkscape}).
+
+@subsubheading Maintaining @file{.xhtml} files
+
+If web pages are found, the @code{tuneup} functionality of
+@command{centos-art.sh} 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{} piece
+of code be in the page.
+
+Once the @code{} piece of code has be expanded,
+there is no need to put anything else in the page. You can run the
+@code{tuneup} functionality everytime you update the heading
+information so as to update the table of contents, too.
+
+In order for the @code{tuneup} functionality of
+@command{centos-art.sh} script to transform headings, you need to put
+headings in just one line using one of the following forms:
+
+@verbatim
+
+
+
+@end verbatim
+
+In the example above, h1 can vary from h1 to h6. Closing tag must be
+present and also match the openning tag. The value of @option{name}
+and @option{href} options from the anchor element are set dynamically
+using the md5sum output of combining the page location, the
+@code{head-} string and the heading string. If any of the components
+used to build the heading reference changes, you need to run the the
+@code{tuneup} functionality of @command{centos-art.sh} script in order
+for the anchor elements to use the correct information.
+
+@subheading Examples
+
+@table @command
+@item centos-art tuneup trunk/Scripts
+
+Update the copyright and license notice of all the shell scripts we
+have in @file{trunk/Scripts} directory structure.
+
+@item centos-art tuneup trunk/Identity/Models/Brands --filter="symbol"
+Update metadata and remove unused definitions from all design models
+in @file{trunk/Identity/Models/Brands} which have the word
+@samp{symbol} in the file name.
+
+@item centos-art tuneup trunk/Identity/Webenv/App/Home
+Update headings and the related table of contents to all web pages
+inside @file{trunk/Identity/Webenv/App/Home}, recusively.
+@end table
+
+@subheading Author
+
+Written by Alain Reguera Delgado.
+
+@subheading Reporting bugs
+
+Report bugs to @email{centos-artwork@@centos.org} mailing list.
+
+@subheading Copyright
+
+Copyright @copyright{} 2009, 2010, 2011 The CentOS Project.
+
+This is free software. You may redistribute copies of it under the
+terms of the GNU General Public License (@pxref{GNU General Public
+License}). There is NO WARRANTY, to the extent permitted by law.
+
+@subheading See also
+
+@itemize
+@item @ref{Directories trunk Scripts Functions}
+@item @ref{Directories trunk Scripts}
+@item @ref{Directories trunk}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Introduction/authors.texinfo b/Manuals/Texinfo/en_US/Introduction/authors.texinfo
new file mode 100755
index 0000000..f62bdd3
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Introduction/authors.texinfo
@@ -0,0 +1,41 @@
+This section records authoring information of CentOS Artwork
+Repository along the years:
+
+@subheading Graphic Design
+
+@itemize
+@item Guideon de Kok
+@item @email{al@@art.centos.org,Alain Reguera Delgado}
+@item @email{mm@@art.centos.org,Marcus Moeller}
+@end itemize
+
+@subheading Documentation
+
+@itemize
+@item @email{al@@art.centos.org,Alain Reguera Delgado}
+@item @email{ralph@@dev.centos.org,Ralph Angenendt}
+@end itemize
+
+@subheading Localization
+
+@itemize
+@item @email{al@@art.centos.org,Alain Reguera Delgado} (Spanish)
+@end itemize
+
+@subheading Automation
+
+@itemize
+@item @email{al@@art.centos.org,Alain Reguera Delgado}
+@end itemize
+
+@subheading Infrastructure
+@itemize
+@item @email{karan@@dev.centos.org,Karanbirn Singh}
+@item @email{ralph@@dev.centos.org,Ralph Angenendt}
+@end itemize
+
+@subheading Packaging
+@itemize
+@item @email{karan@@dev.centos.org,Karanbirn Singh}
+@item @email{ralph@@dev.centos.org,Ralph Angenendt}
+@end itemize
diff --git a/Manuals/Texinfo/en_US/Introduction/chapter-intro.texinfo b/Manuals/Texinfo/en_US/Introduction/chapter-intro.texinfo
new file mode 100644
index 0000000..96fb6b2
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Introduction/chapter-intro.texinfo
@@ -0,0 +1,21 @@
+Welcome to CentOS Artwork Repository Manual.
+
+The CentOS Artwork Repository Manual describes how The CentOS Project
+Corporate Visual Identity is organized and produced inside the CentOS
+Artwork Repository (@url{https://projects.centos.org/svn/artwork/}).
+If you are looking for a comprehensive, task-oriented guide for
+understanding how The CentOS Project Corporate Visual Identity is
+produced, this is the manual for you.
+
+This manual discusses the following intermedite topics:
+
+@itemize
+@item The CentOS Brand
+@item The CentOS Corporate Visual Structure
+@item The CentOS Corporate Visual Style
+@end itemize
+
+This guide assumes you have a basic understanding of your CentOS
+system. If you need help with CentOS, refer to the help page on the
+CentOS Wiki (@url{http://wiki.centos.org/Help}) for a list of
+different places you can find help.
diff --git a/Manuals/Texinfo/en_US/Introduction/chapter-menu.texinfo b/Manuals/Texinfo/en_US/Introduction/chapter-menu.texinfo
new file mode 100644
index 0000000..39781c3
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Introduction/chapter-menu.texinfo
@@ -0,0 +1,8 @@
+@menu
+* History::
+* Authors::
+* Copying Conditions::
+* Document Convenctions::
+* Repository Convenctions::
+* Feedback::
+@end menu
diff --git a/Manuals/Texinfo/en_US/Introduction/chapter-nodes.texinfo b/Manuals/Texinfo/en_US/Introduction/chapter-nodes.texinfo
new file mode 100644
index 0000000..dff1350
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Introduction/chapter-nodes.texinfo
@@ -0,0 +1,30 @@
+@node History
+@section History
+@cindex History
+@include Introduction/history.texinfo
+
+@node Authors
+@section Authors
+@cindex Authors
+@include Introduction/authors.texinfo
+
+@node Copying Conditions
+@section Copying Conditions
+@cindex Copying conditions
+@include Introduction/copying.texinfo
+
+@node Document Convenctions
+@section Document Convenctions
+@cindex Document convenctions
+@include Introduction/doc-convenctions.texinfo
+
+@node Repository Convenctions
+@section Repository Convenctions
+@cindex Repository convenctions
+@include Introduction/repo-convenctions.texinfo
+
+@node Feedback
+@section Send in Your Feedback
+@cindex Feedback
+@include Introduction/feedback.texinfo
+
diff --git a/Manuals/Texinfo/en_US/Introduction/chapter.texinfo b/Manuals/Texinfo/en_US/Introduction/chapter.texinfo
new file mode 100644
index 0000000..de11d5f
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Introduction/chapter.texinfo
@@ -0,0 +1,6 @@
+@node Introduction
+@chapter Introduction
+@cindex Introduction
+@include Introduction/chapter-intro.texinfo
+@include Introduction/chapter-menu.texinfo
+@include Introduction/chapter-nodes.texinfo
diff --git a/Manuals/Texinfo/en_US/Introduction/copying.texinfo b/Manuals/Texinfo/en_US/Introduction/copying.texinfo
new file mode 100755
index 0000000..01bc2af
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Introduction/copying.texinfo
@@ -0,0 +1,70 @@
+Copyright @copyright{} 2009, 2010, 2011 The CentOS Project.
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+@subheading Preamble
+
+The CentOS Artwork Repository organizes files in a very specific way
+to implement The CentOS Project corporate visual identity. This very
+specific organization of files is part of @command{centos-art.sh}
+script, a bash script that automate most of the frequent tasks inside
+the repository.
+
+The @command{centos-art.sh} script and the organization of files it
+needs to work are not in the public domain; they are copyrighted and
+there are restrictions on their distribution, but these restrictions
+are designed to permit everything that a good cooperating citizen
+would want to do. What is not allowed is to try to prevent others
+from further sharing any version of this program that they might get
+from you.
+
+Specifically, we want to make sure that you have the right to give
+away copies of @command{centos-art.sh} script, that you receive source
+code or else can get it if you want it, that you can change this
+program or use pieces of it in new free programs, and that you know
+you can do these things.
+
+To make sure that everyone has such rights, we have to forbid you to
+deprive anyone else of these rights. For example, if you distribute
+copies of the @command{centos-art.sh} script, you must give the
+recipients all the rights that you have. You must make sure that
+they, too, receive or can get the source code. And you must tell them
+their rights.
+
+Also, for our own protection, we must make certain that everyone finds
+out that there is no warranty for the @command{centos-art.sh} script.
+If this program is modified by someone else and passed on, we want
+their recipients to know that what they have is not what we
+distributed, so that any problems introduced by others will not
+reflect on our reputation.
+
+The centos-art.sh script is released as a GPL work. Individual
+packages used by centos-art.sh script include their own licenses and
+the centos-art.sh script license applies to all packages that it does
+not clash with. If there is a clash between the centos-art.sh script
+license and individual package licenses, the individual package
+license applies instead.
+
+The precise conditions of the license for the @command{centos-art.sh}
+script are found in the General Public Licenses (@pxref{GNU General
+Public License}). This manual specifically is covered by the GNU Free
+Documentation License (@pxref{GNU Free Documentation License}).
+
+@subheading 1. The CentOS Brand
+
+The CentOS Brand (@pxref{Directories trunk Identity Models Brands}) is
+the main visual manifestaion of The CentOS Project. The CentOS Project
+uses The CentOS Brand to connect all its visual manifestions (e.g.,
+GNU/Linux Distributions, Websites, Stationery, etc.) and, this way, it
+provides recognition among other similar projects.
+
+Both The CentOS Brand and all the visual manifestations that derivate
+from it are available for you to study and propose improvement around
+a good citizen's will at The CentOS Community environment, but you are
+not allowed to redistribute them elsewhere, without the given
+permission of The CentOS Project.
+
+If you need to redistribute either The CentOS Brand or any the visual
+manifestatinos that derivate from it, write your intentions to the
+@email{centos-devel@@centos.org} mailing list.
diff --git a/Manuals/Texinfo/en_US/Introduction/doc-convenctions.texinfo b/Manuals/Texinfo/en_US/Introduction/doc-convenctions.texinfo
new file mode 100644
index 0000000..9a9cca6
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Introduction/doc-convenctions.texinfo
@@ -0,0 +1,109 @@
+In this manual the personal pronoun @emph{we} is used to repesent
+@emph{The CentOS Artwork SIG}. This is, the group of persons building
+the CentOS Artwork Repository.
+
+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:
+
+@table @command
+@item command
+
+Linux commands (and other operating system commands, when used) are
+represented this way. This style should indicate to you that you can
+type the word or phrase on the command line and press Enter to invoke
+a command. Sometimes a command contains words that would be displayed
+in a different style on their own (such as file names). In these
+cases, they are considered to be part of the command, so the entire
+phrase is displayed as a command. For example:
+
+Use the @command{centos-art identity --render='path/to/dir'} command
+to produce contents inside the @file{trunk/Identity} directory
+structure.
+@end table
+
+@table @file
+@item file name
+
+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:
+
+The @file{init.sh} file in @file{trunk/Scripts/Bash/Cli/} directory is
+the initialization script, written in Bash, used to automate most of
+tasks in the repository.
+
+The @command{centos-art} command uses the @file{ImageMagick} RPM
+package to convert images from PNG format to other formats.
+@end table
+
+@table @key
+@item @key{key}
+
+A key on the keyboard is shown in this style. For example:
+
+To use @key{TAB} completion to list particular files in a directory,
+type @command{ls}, then a character, and finally the Tab key. Your
+terminal displays the list of files in the working directory that
+begin with that character.
+@end table
+
+@table @key
+@item @key{key-combination}
+A combination of keystrokes is represented in this way. For example:
+
+The @key{Ctrl-Alt-Backspace} key combination exits your graphical
+session and returns you to the graphical login screen or the console.
+@end table
+
+@table @code
+@item @code{computer output}
+
+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 displays the contents of a directory. For example:
+
+@verbatim
+Config help_renameEntry.sh
+help_copyEntry.sh help_restoreCrossReferences.sh
+help_deleteCrossReferences.sh help_searchIndex.sh
+@end verbatim
+
+The output returned in response to the command (in this case, the
+contents of the directory) is shown in this style.
+@end table
+
+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:
+
+@quotation
+@strong{Note} Remember that Linux is case sensitive. In other words, a
+rose is not a ROSE is not a rOsE.
+@end quotation
+
+@quotation
+@strong{Tip} The directory @file{/usr/share/doc/} contains additional
+documentation for packages installed on your system.
+@end quotation
+
+@quotation
+@strong{Important} If you modify the DHCP configuration file, the
+changes do not take effect until you restart the DHCP daemon.
+@end quotation
+
+@quotation
+@strong{Caution} Do not perform routine tasks as root --- use a
+regular user account unless you need to use the root account for
+system administration tasks.
+@end quotation
+
+@quotation
+@strong{Warning} Be careful to remove only the necessary partitions.
+Removing other partitions could result in data loss or a corrupted
+system environment.
+@end quotation
diff --git a/Manuals/Texinfo/en_US/Introduction/feedback.texinfo b/Manuals/Texinfo/en_US/Introduction/feedback.texinfo
new file mode 100644
index 0000000..1c7f597
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Introduction/feedback.texinfo
@@ -0,0 +1,9 @@
+If you find an error in the @emph{CentOS Artwork Repository}, or if
+you have thought of a way to make this manual better, we would like to
+hear from you! Share your suggestions in the appropriate mailing list
+(@url{http://lists.centos.org/}) and/or bug tracker
+(@url{http://bugs.centos.org/}).
+
+When you make suggestion, try to be as specific as possible. For
+example, if you have found an error in the manual, include the section
+number and some of the surrounding text so we can find it easily.
diff --git a/Manuals/Texinfo/en_US/Introduction/history.texinfo b/Manuals/Texinfo/en_US/Introduction/history.texinfo
new file mode 100755
index 0000000..1785ad1
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Introduction/history.texinfo
@@ -0,0 +1,118 @@
+This section records noteworthy changes of CentOS Artwork Repository
+through years.
+
+@subheading 2008
+
+The CentOS Artwork Repository started at CentOS Developers mailing
+list (@email{centos-devel@@centos.org}) during a discussion about how
+to automate the slide images of Anaconda. In such discussion, Ralph
+Angenendt rose up his hand to ask: Do you have something to show?
+
+To answer the question, Alain Reguera Delgado suggested a bash script
+which combined SVG and SED files in order to produce PNG images in
+different languages ---together with the proposition of creating a
+Subversion repository where translations and image production could be
+distributed inside The CentOS Community---.
+
+Karanbirn Sighn considered the idea intresting and provided the
+infrastructure necessary to support the effort. This way the CentOS
+Artwork SIG and the CentOS Artwork Repository were officially created
+and made available in the following urls:
+
+@itemize
+@item @url{https://projects.centos.org/trac/artwork/}
+@item @url{https://projects.centos.org/svn/artwork/}
+@end itemize
+
+Once the CentOS Artwork Repository was available, Alain Reguera
+Delagdo uploaded the bash script for rendering Anaconda slides; Ralph
+Angenendt documented it very well and The CentOS Translators started
+to download working copies of CentOS Artwork Repository to produce
+slide images in their own languages.
+
+@subheading 2009
+
+The rendition script is at a very rustic state where only slide images
+can be produced.
+
+The rendition script was redesigned to extend image production to
+other areas, not just slide images. In this configuration one
+translated SVG instance was created from the SVG file provided as
+input in order to produce one translated PNG image as output. The
+translation of SVG files was made through SED replacement commands and
+the rendition of PNG images was realized through Inkscape command line
+internface.
+
+The rendition script was named @command{render.sh}. The directory
+structures were prepared to receive the rendition script so images
+could be produced inside them. Each directory structure had design
+templates (.svg), translation files (.sed), and translated images
+(.png).
+
+The rendition script was unified in 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.
+
+Concepts about corporate identity began to be considered. As referece,
+it was used the book @emph{Corporate Identity} by Wally Olins (1989)
+and Wikipedia (@url{http://en.wikipedia.org/Corporate_identity}).
+
+The rendition script main's goal becomes to: automate production of a
+monolithic corporate visual identity structure, based on The CentOS
+Mission and The CentOS Release Schema.
+
+The documentation of CentOS Artwork Repository started to take form in
+@LaTeX{} format.
+
+@subheading 2010
+
+The rendition script @command{render.sh} is no longer a rendition
+script, but a collection of functionalities grouped into the
+@command{centos-art.sh} script where rendition is one functionality
+among others. The @command{centos-art.sh} is created to automate most
+frequent tasks inside the repository. There is no need to have links
+all around the repository if a command-line interface can be created
+(through symbolic links, in the @file{~/bin} directory) and be called
+anywhere inside the repository as it would be usually done with
+regular commands.
+
+Inside @command{centos-art.sh}, functionalities started to get
+identified and separated one another. For example, when images were
+rendered, there was no need to load functionalities related to
+documentation manual. This moved us onto common functionalities and
+specific functionalities inside @command{centos-art.sh} script. Common
+functionalities are loaded when the script is initiated and are
+available to specific functionalities.
+
+The @command{centos-art.sh} script was redesigned to handle options
+trough @command{getopt} option parser.
+
+The repository directory structure was updated to improve the
+implementation of concepts related to corporate visual identity.
+Specially in the area related to themes which were divided into design
+models and artistic motifs.
+
+@subheading 2011
+
+The @command{centos-art.sh} script was redesigned to start translating
+SVG and other XML-based files (e.g., XHTML and Docbook files) through
+the @command{xml2po} program and shell scripts files (e.g., Bash
+scripts) through GNU @command{gettext} tools. This configuration
+provided a stronger interface for graphic designers, translators and
+programmers at time of producing localized content. @file{.sed} files
+are no longer used to handle translations.
+
+Improve option parsing through @command{getopt}.
+
+The @command{centos-art.sh} script is updated to organize
+functionalities in two groups: ``the administrative functionalities''
+and ``the productive functionalities''. The administrative
+functionalities cover actions like: copying, deleting and renaming
+directory structures inside the repository. Also, preparing your
+workstation for using @command{centos-art.sh} script, making backups
+of the distribution theme currently installed, installing themes
+created inside repository and restoring themes from backup. On the
+other hand, the productive functionalities cover actions like: content
+rendition, content localization, content documentation and content
+maintainance.
diff --git a/Manuals/Texinfo/en_US/Introduction/repo-convenctions.texinfo b/Manuals/Texinfo/en_US/Introduction/repo-convenctions.texinfo
new file mode 100644
index 0000000..48b2fae
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Introduction/repo-convenctions.texinfo
@@ -0,0 +1,537 @@
+The CentOS Artwork Repository is supported by Subversion
+(@url{http://subversion.tigris.org/}), a version control system which
+allows you to keep old versions of files and directories (usually
+source code), keep a log of who, when, and why changes occurred, etc.,
+like CVS, RCS or SCCS.
+
+When using Subversion there is one @emph{source repository} and many
+@emph{working copies} of that source repository. The working copies
+are independent one another, can be distributed all around the world
+and provide a local place for designers, documentors, translators and
+programmers to perform their works in a descentralized way. The
+source repository, on the other hand, provides a central place for all
+independent working copies to interchange data and provides the
+information required to permit extracting previous versions of files
+at any time.
+
+@subsection Repository policy
+@cindex Repository policy
+
+The CentOS Artwork Repository is a collaborative tool that anyone can
+have access to. However, changing that tool in any form is something
+that should be requested in @email{centos-devel@@centos.org} mailing
+list. Generally, people download working copies from CentOS Artwork
+Repository, study the repository organization, make some changes in
+their working copies, make some tests to verify such changes do work
+the way expected and finally request access to commit them up to the
+CentOS Artwork Repository (i.e., the source repository) for others to
+benefit from them.
+
+Once you've received access to commit your changes, there is no need
+for you to request permission again to commit other changes from your
+working copy to CentOS Artwork Repository as long as you behave as a
+@emph{good community citizen}.
+
+As a good community citizen one understand of a person who respects
+the work already done for others and share ideas with authors before
+changing relevant parts of their work, specially in situations when
+the access required to realize the changes has been granted already.
+Of course, there is a time when conversation has taken place, the
+paths has been traced and changing the work is so obvious that there
+is no need for you to talk about it; that's because you already did,
+you already built the trust to keep going. Anyway, the mailing list
+mentioned above is available for sharing ideas in a way that good
+relationship between community citizens could be constantly balanced.
+
+The relationship between community citizens is monitored by repository
+administrators. Repository administrators are responsible of granting
+everything goes the way it needs to go in order for the CentOS Artwork
+Repository to comply its mission which is: to provide a colaborative
+tool for The CentOS Community where The CentOS Project Corporate
+Identity is built and maintained from The CentOS Community itself.
+
+It is also important to remember that all source files inside CentOS
+Artwork Repository should comply the terms of GNU General Public
+License (@pxref{GNU General Public License}) in order for them to
+remain inside the repository.
+
+@subsection Repository organization
+@cindex Repository organization
+
+The CentOS Artwork Repository uses a @file{trunk}, @file{branches},
+and @file{tags} organization.
+
+@table @file
+@item trunk
+
+The @file{trunk} directory organizes the main development line of
+CentOS Artwork Repository. @xref{Directories trunk}, for more
+information.
+
+@item branches
+
+The @file{branches} directory oranizes intermediate development lines
+taken from the main development line. @xref{Directories branches},
+for more information.
+
+@item tags
+
+The @file{tags} directory organizes frozen development lines taken
+either from the main or the intermediate lines of development.
+@xref{Directories tags}, for more information.
+@end table
+
+@subsection Repository file names
+@cindex Repository file names
+
+Inside the CentOS Artwork Repository, file names are all written in
+lowercase (e.g., @samp{01-welcome.png}, @samp{splash.png},
+@samp{anaconda_header.png}, etc.) and directory names are all written
+capitalized (e.g., @samp{Identity}, @samp{Themes}, @samp{Motifs},
+@samp{TreeFlower}, etc.).
+
+@subsection Repository work lines
+
+Inside CentOS Artwork Repository there are four major work lines of
+production which are: @emph{graphic design}, @emph{documentation},
+@emph{localization} and @emph{automation}. These work lines describe
+different areas of content production. Content production inside these
+specific areas may vary as much as persons be working on them.
+Producing content in too many different ways may result innapropriate
+in a collaborative environment like CentOS Artwork Repository where
+content produced in one area depends somehow from content produced in
+another different area. So, a @emph{content production standard} is
+required for each available work line.
+
+@subsubsection Graphic design
+@cindex Graphic design work line
+
+The graphic design work line exists to cover brand design, typography
+design and themes design mainly. Additionally, some auxiliar areas
+like icon design, illustration design, brushes design, patterns
+designs and palettes of colors are also included here for
+completeness.
+
+Inside CentOS Artwork Repository graphic design is performed through
+Inkscape (@url{http://www.inkscape.org/}) and GIMP
+(@url{http://www.gimp.org/}). The Inkscape tool is used to create and
+manipulate scalable vector graphics and export them to PNG format; it
+also provides a command-line interface that we use to perform massive
+exportation from SVG files to PNG files in automation scripts. On the
+other hand, GIMP is used to create and manipulate rastered images,
+create brushes, patterns and palettes of colors.
+
+@quotation
+@strong{Tip} Combine both Inkscape and GIMP specific functionalities
+and possibilities to produce very beautiful images.
+@end quotation
+
+The CentOS Project Corporate Visual Identity is made of different
+visual manifestations (e.g., Distributions, Web sites, Stationery,
+etc.). Visual manifestations implement the corporate identity
+concepts by mean of images. To produce these images, we decompose
+image production in @emph{design models} and @emph{artistic motifs}.
+
+Design models provide the structural information of images (i.e.,
+dimension, position of common elements in the visible area,
+translation markers, etc.) and they are generally produced as scalable
+vector graphics to take advantage of SVG standard, an XML-based
+standard.
+
+Artistic motifs provide the visual style (i.e., the background
+information, the look and feel) some design models need to complete
+the final image produced by automation scripts. Artistic motifs are
+generally produced as rastered images.
+
+The result produced from combining one design model with one artistic
+motif is what we know as a @emph{theme}. Inside themes directory
+structure (@pxref{Directories trunk Identity Images Themes}), you can find
+several design models and several artistic motifs independently one
+another that can be albitrarily combined through @emph{theme
+rendition}, a flexible way to produce images for different visual
+manifestations in very specific visual styles. Inside themes directory
+structure, theme rendition is performed in
+@file{trunk/Identity/Images/Themes} directory structure, the required
+design models are taken from @file{trunk/Identity/Models/Themes}
+directory structure and the action itself is controlled by the
+@code{render} functionality of @command{centos-art.sh} script.
+
+In addition to theme rendition you can find @emph{direct rendition},
+too. Direct rendition is another way of image production where there
+is no artistic motif at all but design models only. Direct rendition
+is very useful to produce simple content that doesn't need specific
+background information. Some of these contents are brands, icons and
+illustrations. Direct rendition is performed in
+@file{trunk/Identity/Images}, the required design models are taken
+from @file{trunk/Identity/Models} directory structure and the action
+itself is controlled by the @code{render} functionality of
+@command{centos-art.sh} script.
+
+@xref{Directories trunk Identity}, for more information about The
+CentOS Corporate Identity and how graphic design fits on it.
+
+@subsubsection Documentation
+@cindex Documentation work line
+
+The documentation work line exists to describe what each directory
+inside the CentOS Artwork Repository is for, the conceptual ideas
+behind them and, if possible, how automation scripts make use of them.
+
+The CentOS Artwork Repository documentation is supported by Texinfo, a
+documentation system that uses a single source file to produce both
+online information and printed output.
+
+The repository documentation is organized under @file{trunk/Manual}
+directory and uses the repository directory structre as reference.
+Each directory in the repository has a documentation entry associated
+in the documentation manual. Documentation entries are stored under
+@file{trunk/Manual/Directories} directory and the action itself is
+controlled by the @code{help} functionality of @command{centos-art.sh}
+script.
+
+The @code{help} functionality let you create, edit and delete
+documentation entries in a way that you don't need to take care of
+updating menus, nodes and cross reference information inside the
+manual structure; the functionality takes care of it for you.
+However, if you need to write repository documentation that have
+nothing to do with repository directories (e.g., Preface, Introduction
+and similar) you need to do it manually, there is no functionality to
+automate such process yet.
+
+@xref{Directories trunk Manuals}, for more information on
+documentation.
+
+@subsubsection Localization
+@cindex Localization work line
+
+The localization work line exists to provide the translation messages
+required to produce content in different languages. Translation
+messages inside the repository are stored as portable objects (e.g.,
+.po, .pot) and machine objects (.mo) under @file{trunk/Locales}
+directory structure.
+
+The procedure used to localize content is taken from @command{gettext}
+standard specification. Basically, translatable strings are retrived
+from source files in order to create portable objects and machine
+objects for them. These portable objects are editable files that
+contain the information used by translators to localize the
+translatable strings retrived from source files. On the other hand,
+machine objects are produced to be machine-redable only, as its name
+implies, and are produced from portable objects.
+
+Since @command{gettext} needs to extract translatable strings form
+source files in order to let translators to localize them, we are
+limitted to use source files supported by @command{gettext} program.
+This is not a limitation at all since @command{gettext} supports most
+popular programming laguages (e.g., C, C++, Java, Bash, Python, Perl,
+PHP and GNU Awk just to mention a few ones). Nevertheless, formats
+like SVG, XHTML and Docbook don't figure as supported formats in the
+list of @command{gettext} supported source files.
+
+To translate XML based source files like SVG, XHTML and Docbook we use
+the @command{xml2po} program instead. The @command{xml2po} comes with
+the @file{gnome-doc-utils} package and retrives translatable strings
+from one XML file to produce portable objects for them.
+
+@quotation
+@strong{Note}
+Portable objects produced by @command{xml2po} have the same format
+that portable objects produced by @command{gettext}. This make the
+localization process quite consistent from translators' point of view.
+No matter what the source file be, the translator will always face the
+same translation file format (i.e., the portable object format).
+@end quotation
+
+With the portable object in place, the @command{xml2po} program is
+used again to create the final translated XML, just with the same
+definition of the source file where translatable strings were taken
+from (e.g., if we extract translatable strings from a SVG file, as
+result we get the same SVG file but with translatable strings already
+localized ---obviously, for this to happen translators need to
+localize translatable strings inside the portable object first,
+localization won't appear as art of magic---). When using
+@command{xml2po}, the machine object is used as temporal file to
+produce the final translated XML file.
+
+@quotation
+@strong{Tip} If you want to have your content localized inside CentOS
+Artwork Repository be sure to use source files supported either by
+@command{gettext} or @command{xml2po} programs.
+@end quotation
+
+@xref{Directories trunk Locales}, for more information.
+
+@subsubsection Automation
+@cindex Automation work line
+
+The automation work line exists to standardize content production in
+CentOS Artwork Repository. There is no need to type several tasks,
+time after time, if they can be programmed into just one executable
+script.
+
+The automation work line takes place under @file{trunk/Scripts}
+directory structure. Here is developed the @command{centos-art.sh}
+script, a bash script specially designed to automate most frequent
+tasks (e.g., rendition, documentation and localization) inside the
+repository. Basically, the @command{centos-art.sh} script is divided
+in several functionalities independent one another that perform
+specific tasks and relay on repository organization to work as
+expected.
+
+@quotation
+@strong{Tip} If you need to improve the way content is produced, look
+inside automation scripts and make your improvement there for everyone
+to benefit.
+@end quotation
+
+@xref{Directories trunk Scripts}, for more information on automation.
+
+@subsection Connection between directories
+@cindex Connection between directories
+@cindex Master paths
+@cindex Auxiliar paths
+
+In order to produce content in CentOS Artwork Repository, it is
+required that all work lines be connected somehow. This is the way
+automation scripts can know where to retrive the information they need
+to work with (e.g., design model, translation messages, output
+location, etc.). We build this kind of connection using two path
+constructions named @emph{master paths} and @emph{auxiliar paths}.
+
+The master path points only to directories that contain the source
+files (e.g., SVG files) required to produce base content (e.g., PNG
+files) through automation scripts. Each master path inside the
+repository may have several auxiliar paths associated, but auxiliar
+paths can only have one master path associated.
+
+The auxiliar paths can point either to directories or files. When an
+auxiliar path points to a directory, that directory contains
+information that modifies somehow the content produced from master
+paths (e.g., translation messages) or provides the output information
+required to know where to store the content produced from master path.
+When an auxiliar path points to a file, that file has no other purpose
+but to document the master path it refers to.
+
+The relation between auxiliar paths and master paths is realized
+combining two path informations which are: the master path itself and
+one second level directory structure from the repository. Generally,
+the master path is considered the path identifier and the second level
+directory structure taken from the repository is considered the common
+part of the path where the identifier is appended.
+
+@float Figure, Path construction
+@verbatim
+-----+---------------+----------------------------+------+-----------
+Path | Suffix | Identifier |Prefix| Type
+-----+---------------+----------------------------+------+-----------
+ A | |trunk/Identity/Models/Brands| | Directory
+-----+---------------+----------------------------+------+-----------
+ B | trunk/Manual/|trunk/Identity/Models/Brands|.texinfo | File
+-----+---------------+----------------------------+------+-----------
+ C | trunk/Locales/|trunk/Identity/Models/Brands| | Directory
+-----+---------------+----------------------------+------+-----------
+ D | |trunk/Identity/Images/Brands| | Directory
+-----+---------------+----------------------------+------+-----------
+ E | trunk/Locales/|trunk/Identity/Images/Brands|.texinfo | File
+-----+---------------+----------------------------+------+-----------
+
+ A = Master path.
+ B = Auxiliar path to documentation entry.
+ C = Auxiliar path to translation messages.
+ D = Auxiliar path to final content output.
+ E = Auxiliar path to documentation entry.
+@end verbatim
+@caption{Path construction.}
+@end float
+
+The path information described above (@pxref{Path construction}) is
+used by direct rendition and can be taken as reference to add other
+components that are equally produced in the repository. To add new
+components that make use of direct rendition inside the repository,
+change just the component name used above (e.g., @file{Brands}) to
+that one you want to add, without changing the path structure around
+it.
+
+The file organization used by theme rendition extends direct rendition
+by separating design models information from backgrounds information.
+To better understand this configuration, you can consider it as two
+independent lists, one of design models and one of artistic motifs,
+which are arbitrary combined between themselves in order to render
+images in specific ways. The possibilities of this configuration are
+endless and let us describe visual manifestations very well. For
+example, consider the organization used to produce @file{Anaconda}
+images; for CentOS distribution major release 5; using @file{Default}
+design models and version @file{3} of @file{Flame} artistic motif:
+
+@float Figure, Path construction extended
+@verbatim
+-----+---------------+------------------------------------------------------+------+-----------
+Path | Suffix | Identifier |Prefix| Type
+-----+---------------+------------------------------------------------------+------+-----------
+ A | |trunk/Identity/Models/Themes/Default/Distro/5/Anaconda| | Directory
+-----+---------------+------------------------------------------------------+------+-----------
+ B | trunk/Manual/|trunk/Identity/Models/Themes/Default/Distro/5/Anaconda|.texinfo | File
+-----+---------------+------------------------------------------------------+------+-----------
+ C | trunk/Locales/|trunk/Identity/Models/Themes/Default/Distro/5/Anaconda| | Directory
+-----+---------------+------------------------------------------------------+------+-----------
+ D | |trunk/Identity/Images/Themes/Flame/3/Distro/5/Anaconda| | Directory
+-----+---------------+------------------------------------------------------+------+-----------
+ E | trunk/Locales/|trunk/Identity/Images/Themes/Flame/3/Distro/5/Anaconda|.texinfo | File
+-----+---------------+------------------------------------------------------+------+-----------
+
+ A = Master path.
+ B = Auxiliar path to documentation entry.
+ C = Auxiliar path to translation messages.
+ D = Auxiliar path to final content output.
+ E = Auxiliar path to documentation entry.
+@end verbatim
+@caption{Path construction extended.}
+@end float
+
+The path information described above (@pxref{Path construction
+extended}) is used by theme rendition and can be taken as reference to
+add other components that are equally produced in the repository.
+
+In this configuration we can change both design model name (e.g.,
+@file{Default}) and artistic motif name (e.g., @file{Flame/3}) to
+something else in order to achieve a different result. The only
+limitations impossed are the storage space provided in the server
+machine and your own creativeness as graphic designer.
+
+@quotation
+@strong{Note}
+A theme ready for implementation may consume from 100 MB to 400 MB of
+storage space. The exact space consumed by a theme depends on the
+amount of screen resolutions the theme supports. The more screen
+resolutions the theme supports, the more storage space demanded for
+it.
+@end quotation
+
+In this configuration we saw how to build the path information for
+@file{Anaconda} component as part of CentOS Distribution visual
+manifestation, but that is not the only component we have inside
+CentOS Distribution visual manifestation. There are other components
+like Syslinux, Grub, Rhgb, Gdm, Kdm, Gsplash and Ksplash that share a
+similar file organization to that described above for @file{Anaconda}
+component.
+
+@subsection Syncronizing path information
+@cindex Syncronizing path information
+
+Syncronizing path information is the action that keeps all path
+information up to date in the repository. This action implies both
+@emph{file movement} and @emph{file content replacement} in this very
+specific order. File movement is related to duplicate, delete and
+rename files and directories in the repository. File content
+replacement is related to replace information, path information in
+this case, inside files in the repository.
+
+The order followed to syncronize path information is relevant because
+the versioned nature of the files we are working with. We don't
+perform file content replacement first because that would imply a
+repository change which will immediatly demmand a commit in order for
+actions like duplicate, delete or rename to take place. However, if we
+perform file movement first, it is possible to commit both file moved
+and file content replacements as if they were just one change. In this
+case the file content replacement takes palce in the target location
+that have been duplicated or renamed, not the one use as source
+location. This configuration is specially useful when files are
+renamed (i.e., one file is copied from a source location to a target
+location and then the source location of it is removed from
+repository).
+
+@quotation
+@strong{Warning} There is no support for URLs actions inside
+@command{centos-art.sh} script. The @command{centos-art.sh} script is
+designed to work with local files inside the working copy only. If you
+need to perform URL actions directly, use Subversion commands instead.
+@end quotation
+
+When one master path is changed it is required that all related
+auxiliar paths be changed, too. This is required in order for master
+paths to retain their relation with auxiliar paths. This way,
+automation scripts are able to know where to retrive translation
+messages from, where to store final output images to and where to look
+for documentation. If relation between master paths and auxiliar paths
+is lost, there is no way for automation scripts to know where to
+retrive the information they need.
+
+The auxiliar paths should never be modified under any reason but to
+satisfy the relationship with the master path. Liberal change of
+auxiliar paths may suppress the conceptual idea they were initially
+created for; and certainly, automation scripts may stop working as
+expected. The update direction to rename path information must be from
+master path to auxiliar path and never the opposite.
+
+The relation between master and auxiliar paths is useful to keep
+repository organized but introduce some complications when we work
+with files that use master path information as reference to build
+structural information. This is the case of repository documentation
+manual source files where inclusions, menus, nodes and cross
+references are built using master path information as reference. Now,
+to see what kind of complication we are talking about, consider what
+would happen to a structural definitions (i.e., inlusions, menus,
+nodes and cross refereces) already set in the manual from one master
+path that is suddenly renamed to something different. If the path
+information is not syncronized, at this point, we lose connection
+between the master path and the auxiliar path created to store the
+related documentation entry, as well as the related structural
+definitions that end up pointing to a master path that no longer
+exist.
+
+The syncronization of path information is aimed to solve these kind of
+issues.
+
+@subsection Extending repository organization
+@cindex Extending repository organization
+
+Occasionly, you may find that new components of The CentOS Project
+Corporate Identity need to be added to the repository in order to work
+them out. If that is the case, the first question we need to ask
+ourselves, before start to create directories blindly all over, is:
+@emph{What is the right place to store it?}
+
+The best place to find answers is in The CentOS Community (see page
+@url{http://wiki.centos.org/GettingHelp}), but going there with hands
+empty is not good idea. It may give the impression you don't really
+care about. Instead, consider the following suggestions to find your
+own comprehension in order to make your own propositions based on it.
+
+When extending respository structure it is very useful to bear in mind
+The CentOS Project Corporate Identity Structure (@pxref{Directories
+trunk Identity}) The CentOS Mission and The CentOS Release Schema. The
+rest is just matter of choosing appropriate names. It is also worth to
+know that each directory in the repository responds to a conceptual
+idea that justifies its existence.
+
+To build a directory structure, you need to define the conceptual idea
+first and later create the directory. There are some locations inside
+the repository that already define some concepts you probably want to
+reuse. For example, @file{trunk/Identity/Images/Themes} to store theme
+artistic motifs, @file{trunk/Identity/Models/Themes} to store theme
+design models, @file{trunk/Manual} to store documentation files,
+@file{trunk/Locales} to store translation messages,
+@file{trunk/Scripts} to store automation scripts and so on.
+
+To illustrate this desition process let's consider the
+@file{trunk/Identity/Images/Themes/TreeFlower/3} directory structure
+as example. This directory can be read as: the theme development line
+of version @file{3} of @file{TreeFlower} artistic motif. Additional,
+we can identify that artistic motifs are part of themes as well as
+themes are part of The CentOS Project Corporate Identity. These
+concepts are better described independently in each documentation
+entry related to the directory structure as it is respectively shown
+in the list of commands bellow.
+
+@verbatim
+centos-art help --read turnk
+centos-art help --read turnk/Identity
+centos-art help --read turnk/Identity/Themes
+centos-art help --read turnk/Identity/Images/Themes
+centos-art help --read turnk/Identity/Images/Themes/TreeFlower
+centos-art help --read turnk/Identity/Images/Themes/TreeFlower/3
+@end verbatim
+
+The concepts behind other location can be found in the same way
+described above, just change the path information used above to the
+one you are trying to know concepts for.
diff --git a/Manuals/Texinfo/en_US/Licenses/GFDL.texinfo b/Manuals/Texinfo/en_US/Licenses/GFDL.texinfo
new file mode 100755
index 0000000..922d49a
--- /dev/null
+++ b/Manuals/Texinfo/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 IDENPENDENT 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 Appendix 1. 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 Appendix 2. 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/Manuals/Texinfo/en_US/Licenses/GPL.texinfo b/Manuals/Texinfo/en_US/Licenses/GPL.texinfo
new file mode 100755
index 0000000..01fb28c
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Licenses/GPL.texinfo
@@ -0,0 +1,352 @@
+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
+
+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.
+
+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.
+
+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.
+
+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.
+
+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.
+
+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.
+
+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.
+
+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.
+
+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.
+
+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.
+
+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.
+
+@strong{NO WARRANTY}
+
+11. 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.
+
+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 Appendix: 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
+
+ Copyright (C) 19yy
+
+ 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.
+
+ , 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/Manuals/Texinfo/en_US/Licenses/chapter-intro.texinfo b/Manuals/Texinfo/en_US/Licenses/chapter-intro.texinfo
new file mode 100755
index 0000000..e69de29
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Licenses/chapter-intro.texinfo
diff --git a/Manuals/Texinfo/en_US/Licenses/chapter-menu.texinfo b/Manuals/Texinfo/en_US/Licenses/chapter-menu.texinfo
new file mode 100755
index 0000000..b8240ba
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Licenses/chapter-menu.texinfo
@@ -0,0 +1,4 @@
+@menu
+* GNU General Public License::
+* GNU Free Documentation License::
+@end menu
diff --git a/Manuals/Texinfo/en_US/Licenses/chapter-nodes.texinfo b/Manuals/Texinfo/en_US/Licenses/chapter-nodes.texinfo
new file mode 100755
index 0000000..da69108
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Licenses/chapter-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/Manuals/Texinfo/en_US/Licenses/chapter.texinfo b/Manuals/Texinfo/en_US/Licenses/chapter.texinfo
new file mode 100755
index 0000000..a20dbe8
--- /dev/null
+++ b/Manuals/Texinfo/en_US/Licenses/chapter.texinfo
@@ -0,0 +1,6 @@
+@node Licenses
+@chapter Licenses
+@cindex Licenses
+@include Licenses/chapter-intro.texinfo
+@include Licenses/chapter-menu.texinfo
+@include Licenses/chapter-nodes.texinfo
diff --git a/Manuals/Texinfo/en_US/repository-index.texinfo b/Manuals/Texinfo/en_US/repository-index.texinfo
new file mode 100644
index 0000000..7702d0f
--- /dev/null
+++ b/Manuals/Texinfo/en_US/repository-index.texinfo
@@ -0,0 +1,7 @@
+@node Index
+@unnumbered Index
+@printindex cp
+
+@node List of Figures
+@unnumbered List of Figures
+@listoffloats Figure
diff --git a/Manuals/Texinfo/en_US/repository-menu.texinfo b/Manuals/Texinfo/en_US/repository-menu.texinfo
new file mode 100644
index 0000000..d0b359a
--- /dev/null
+++ b/Manuals/Texinfo/en_US/repository-menu.texinfo
@@ -0,0 +1,7 @@
+@menu
+* Introduction::
+* Directories::
+* Licenses::
+* Index::
+* List of Figures::
+@end menu
diff --git a/Manuals/Texinfo/en_US/repository-nodes.texinfo b/Manuals/Texinfo/en_US/repository-nodes.texinfo
new file mode 100644
index 0000000..722d48f
--- /dev/null
+++ b/Manuals/Texinfo/en_US/repository-nodes.texinfo
@@ -0,0 +1,3 @@
+@include Introduction/chapter.texinfo
+@include Directories/chapter.texinfo
+@include Licenses/chapter.texinfo
diff --git a/Manuals/Texinfo/en_US/repository.texinfo b/Manuals/Texinfo/en_US/repository.texinfo
new file mode 100644
index 0000000..f1f32c4
--- /dev/null
+++ b/Manuals/Texinfo/en_US/repository.texinfo
@@ -0,0 +1,54 @@
+\input texinfo @c -*-texinfo-*-
+@c $Id$
+@setfilename repository.info
+@settitle CentOS Artwork Repository
+@afourpaper
+@finalout
+
+@c -- Summary Description and Copyright -----------------------
+@copying
+This manuals documents relevant information regarding the deployment,
+organization, and administration of CentOS Artwork Repository.
+
+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 GNU Free
+Documentation License.
+@end copying
+
+@c -- Titlepage, Contents, Copyright ---------------------------
+
+@titlepage
+@title CentOS Artwork Repository
+@subtitle Manual
+@author Alain Reguera Delgado
+@page
+@vskip 0pt plus 1filll
+@insertcopying
+@end titlepage
+
+@contents
+
+@c -- `Top' Node and Master Menu -------------------------------
+
+@ifnottex
+@node Top
+@top CentOS Artwork Repository
+@insertcopying
+@end ifnottex
+
+@include repository-menu.texinfo
+
+@c -- The Body of the Document --------------------------------
+
+@include repository-nodes.texinfo
+
+@c -- The End of the Document ---------------------------------
+
+@include repository-index.texinfo
+
+@bye
diff --git a/Manuals/Texinfo/repository-index.texinfo b/Manuals/Texinfo/repository-index.texinfo
deleted file mode 100644
index 7702d0f..0000000
--- a/Manuals/Texinfo/repository-index.texinfo
+++ /dev/null
@@ -1,7 +0,0 @@
-@node Index
-@unnumbered Index
-@printindex cp
-
-@node List of Figures
-@unnumbered List of Figures
-@listoffloats Figure
diff --git a/Manuals/Texinfo/repository-menu.texinfo b/Manuals/Texinfo/repository-menu.texinfo
deleted file mode 100644
index d0b359a..0000000
--- a/Manuals/Texinfo/repository-menu.texinfo
+++ /dev/null
@@ -1,7 +0,0 @@
-@menu
-* Introduction::
-* Directories::
-* Licenses::
-* Index::
-* List of Figures::
-@end menu
diff --git a/Manuals/Texinfo/repository-nodes.texinfo b/Manuals/Texinfo/repository-nodes.texinfo
deleted file mode 100644
index 722d48f..0000000
--- a/Manuals/Texinfo/repository-nodes.texinfo
+++ /dev/null
@@ -1,3 +0,0 @@
-@include Introduction/chapter.texinfo
-@include Directories/chapter.texinfo
-@include Licenses/chapter.texinfo
diff --git a/Manuals/Texinfo/repository.texinfo b/Manuals/Texinfo/repository.texinfo
deleted file mode 100644
index f1f32c4..0000000
--- a/Manuals/Texinfo/repository.texinfo
+++ /dev/null
@@ -1,54 +0,0 @@
-\input texinfo @c -*-texinfo-*-
-@c $Id$
-@setfilename repository.info
-@settitle CentOS Artwork Repository
-@afourpaper
-@finalout
-
-@c -- Summary Description and Copyright -----------------------
-@copying
-This manuals documents relevant information regarding the deployment,
-organization, and administration of CentOS Artwork Repository.
-
-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 GNU Free
-Documentation License.
-@end copying
-
-@c -- Titlepage, Contents, Copyright ---------------------------
-
-@titlepage
-@title CentOS Artwork Repository
-@subtitle Manual
-@author Alain Reguera Delgado
-@page
-@vskip 0pt plus 1filll
-@insertcopying
-@end titlepage
-
-@contents
-
-@c -- `Top' Node and Master Menu -------------------------------
-
-@ifnottex
-@node Top
-@top CentOS Artwork Repository
-@insertcopying
-@end ifnottex
-
-@include repository-menu.texinfo
-
-@c -- The Body of the Document --------------------------------
-
-@include repository-nodes.texinfo
-
-@c -- The End of the Document ---------------------------------
-
-@include repository-index.texinfo
-
-@bye