diff --git a/Manuals/Repository/trunk/Identity.texi b/Manuals/Repository/trunk/Identity.texi
index b8e8a5c..65f22ca 100644
--- a/Manuals/Repository/trunk/Identity.texi
+++ b/Manuals/Repository/trunk/Identity.texi
@@ -114,7 +114,7 @@ script.
@subsection See also
@menu
-* trunk Translations::
+@comment --- Removed(* trunk Translations::) ---
@end menu
@subsection References
diff --git a/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi
index 87c608c..adda528 100644
--- a/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi
+++ b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi
@@ -138,6 +138,6 @@ organize the design process.
* trunk Identity Themes Motifs Modern Backgrounds Img::
* trunk Identity Themes Motifs Modern Backgrounds Tpl::
* trunk Identity Themes Motifs Modern Backgrounds Xcf::
-* trunk Translations Identity Themes Backgrounds::
+@comment --- Removed(* trunk Translations Identity Themes Backgrounds::) ---
@end menu
diff --git a/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi
index a0f9856..8735b28 100644
--- a/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi
+++ b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi
@@ -10,8 +10,8 @@
To render Anaconda progress slide images using the @emph{Modern}
artistic motif design, the Default theme model, and available
-translation files (@pxref{trunk Translations Identity Themes Distro
-Anaconda Progress}); use the following commands:
+translation files (--- @strong{Removed}(pxref:trunk Translations Identity Themes Distro
+Anaconda Progress) ---); use the following commands:
@example
cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/
diff --git a/Manuals/Repository/trunk/Locales.texi b/Manuals/Repository/trunk/Locales.texi
index 691dda6..dd1f94f 100644
--- a/Manuals/Repository/trunk/Locales.texi
+++ b/Manuals/Repository/trunk/Locales.texi
@@ -650,10 +650,10 @@ distribution you want to render translations for.
@subsection See also
@menu
-* trunk Translations Identity Brands::
-* trunk Translations Identity Fonts::
-* trunk Translations Identity Models::
-* trunk Translations Identity Release::
-* trunk Translations Identity Themes::
+@comment --- Removed(* trunk Translations Identity Brands::) ---
+@comment --- Removed(* trunk Translations Identity Fonts::) ---
+@comment --- Removed(* trunk Translations Identity Models::) ---
+@comment --- Removed(* trunk Translations Identity Release::) ---
+@comment --- Removed(* trunk Translations Identity Themes::) ---
* trunk Identity::
@end menu
diff --git a/Manuals/Repository/trunk/Locales/Identity.texi b/Manuals/Repository/trunk/Locales/Identity.texi
index 3949170..5bf1b70 100644
--- a/Manuals/Repository/trunk/Locales/Identity.texi
+++ b/Manuals/Repository/trunk/Locales/Identity.texi
@@ -19,11 +19,11 @@
@subsection See also
@menu
-* trunk Translations Identity Brands::
-* trunk Translations Identity Fonts::
-* trunk Translations Identity Models::
-* trunk Translations Identity Release::
-* trunk Translations Identity Themes::
-* trunk Translations Identity Widgets::
+@comment --- Removed(* trunk Translations Identity Brands::) ---
+@comment --- Removed(* trunk Translations Identity Fonts::) ---
+@comment --- Removed(* trunk Translations Identity Models::) ---
+@comment --- Removed(* trunk Translations Identity Release::) ---
+@comment --- Removed(* trunk Translations Identity Themes::) ---
+@comment --- Removed(* trunk Translations Identity Widgets::) ---
* trunk Identity::
@end menu
diff --git a/Manuals/Repository/trunk/Locales/Identity/Brands.texi b/Manuals/Repository/trunk/Locales/Identity/Brands.texi
index c20a12a..6f771ef 100644
--- a/Manuals/Repository/trunk/Locales/Identity/Brands.texi
+++ b/Manuals/Repository/trunk/Locales/Identity/Brands.texi
@@ -100,6 +100,6 @@ centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity
@subsection See also
@menu
-* trunk Translations Identity Brands Tpl::
+@comment --- Removed(* trunk Translations Identity Brands Tpl::) ---
* trunk Identity Brands::
@end menu
diff --git a/Manuals/Repository/trunk/Locales/Identity/Themes/Distro/Anaconda/Progress.texi b/Manuals/Repository/trunk/Locales/Identity/Themes/Distro/Anaconda/Progress.texi
index 812b34d..f2d99e2 100644
--- a/Manuals/Repository/trunk/Locales/Identity/Themes/Distro/Anaconda/Progress.texi
+++ b/Manuals/Repository/trunk/Locales/Identity/Themes/Distro/Anaconda/Progress.texi
@@ -88,7 +88,7 @@ Now, with translation files in place, let's move to
@subsection Usage
Translation rendering is described in @samp{trunk/Translations}
-documentation entry (@pxref{trunk Translations}).
+documentation entry (--- @strong{Removed}(pxref:trunk Translations) ---).
@subsection See also
diff --git a/Manuals/Repository/trunk/Locales/Identity/Widgets.texi b/Manuals/Repository/trunk/Locales/Identity/Widgets.texi
index ded7872..fda4863 100644
--- a/Manuals/Repository/trunk/Locales/Identity/Widgets.texi
+++ b/Manuals/Repository/trunk/Locales/Identity/Widgets.texi
@@ -19,5 +19,5 @@
@subsection See also
@menu
-* trunk Translations Identity Widgets::
+@comment --- Removed(* trunk Translations Identity Widgets::) ---
@end menu
diff --git a/Manuals/Repository/trunk/Scripts/Bash/Functions/Render.texi b/Manuals/Repository/trunk/Scripts/Bash/Functions/Render.texi
index 2853557..71dcbc5 100644
--- a/Manuals/Repository/trunk/Scripts/Bash/Functions/Render.texi
+++ b/Manuals/Repository/trunk/Scripts/Bash/Functions/Render.texi
@@ -155,7 +155,7 @@ configuration, design templates and translation files don't need to
have the same names since such name relationship between them is
specified in the matching list properly.
-@xref{trunk Translations}, for more information.
+--- @strong{Removed}(xref:trunk Translations) ---, for more information.
@item One pre-rendition configuration script:
diff --git a/Manuals/Repository/trunk/Translations.texi b/Manuals/Repository/trunk/Translations.texi
deleted file mode 100644
index 691dda6..0000000
--- a/Manuals/Repository/trunk/Translations.texi
+++ /dev/null
@@ -1,659 +0,0 @@
-@subsection Goals
-
-The @file{trunk/Translations} directory exists to:
-
-@itemize
-@item Organize translation files.
-@item Organize translation templates used to produce translation files.
-@end itemize
-
-@subsection Description
-
-When you create artwork for CentOS distribution you find that some
-artworks need to be created for different major releases of CentOS
-distribution and inside each major release that needs to be created for
-different locales. To get an approximate idea of how many files we are
-talking about, consider the followig approximate statistic:
-
-@itemize
-@item Inside CentOS distribution, there are around 30 images to
-rebrand.@footnote{This number is an approximate value and may change.
-It is mainly based on CentOS 5 rebranding experience.}
-
-@item There are near to four major releases of CentOS distribution to
-rebrand in parallel development.@footnote{This value was taken from
-CentOS release schema.}
-
-@item Each CentOS distribution in parallel development supports more
-than two hundreds locales.@footnote{This value was taken from the
-output of @command{locale -a} command.}
-@end itemize
-
-In order to aliviate maintainance of artwork production for such
-environment, we divided artwork production in three production lines:
-
-@enumerate
-@item @xref{trunk Identity Themes Models}, to define artworks
-characteristics (e.g., dimensions, position on the screen, etc.).
-@item @xref{trunk Identity Themes Motifs}, to define artworks visual
-styles (e.g., the look and feel).
-@item Translations, to define which major releases and locales
-artworks are produced for.
-@end enumerate
-
-Inside CentOS Artwork Repository, the artworks' translation production
-line is stored under @file{trunk/Translations} directory.
-
-Inside @file{trunk/Translations} directory, we use ``translation
-entries'' to organize artworks' ``translation files'' and artworks'
-``translation templates''.
-
-@subsubsection Translation Entries
-@cindex Translation paths
-@cindex Translation entries
-
-Translation entries exists for each artwork you want to produce.
-Translation entries can be empty directories, or directories
-containing translation files and translation templates.
-
-When translation entries are empty directories, the identity entry is
-used as reference to create file names and directories layout for
-rendered files. In this case, the @command{centos-art} script takes
-one design template and outputs one non-translated file for each
-design template available. This configuration is mainly used to
-produce non-translatable artworks like themes' backgrounds.
-
-When translation entries contain translation files, the translation
-entry implements the CentOS release schema and is used as reference to
-create file names and directories layout for translated artworks. In
-this case, the @command{centos-art} script applies one translation
-file to one design template to create one translated instance which is
-used to output one translated file. When the translated file is
-rendered, the @command{centos-art} script remove the previous instance
-and takes the next file in the list of translation files to repate the
-whole process once again, and so on for all files in the list. This
-configuration is mainly used to produce translatable artworks like
-Anaconda progress slide images.
-
-To find out correspondence between translation entries and identity
-entries, you need to look the path of both translation entries and
-identity entries. For example, if you are using the @emph{Modern}
-artisitic motif, the identity entry for Anaconda progress artwork is:
-
-@verbatim
-trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
-@end verbatim
-
-and its translation entry is:
-
-@verbatim
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
-@end verbatim
-
-Note how the @file{Translations/} directory prefixes @file{Identity/}
-directory, also how static values (e.g., Identity, Themes, Distro,
-etc.) in the identity entry path remain in translation entry path, and
-how variable values like theme names (e.g., @emph{Modern}) are stript
-out from translation entry path. The same convenction can be applied
-to other identity entries in order to determine their translation
-entries, or to other translation entries to determine their identity
-entries.
-
-@quotation
-@strong{Note} Translation entries related to identity entries under
-@file{trunk/Identity/Themes/Motifs} do not use @file{Motifs/} in the
-path. We've done this because @file{trunk/Identity/Themes/Models}
-structure, the other structure under @file{trunk/Identity/Themes},
-doesn't require translation paths so far. So in the sake of saving
-characters space when building translation entries for
-@file{trunk/Identity/Themes/Motifs} structure, we organize Motifs
-translation entries under @file{trunk/Translations/Identity/Themes/}
-directly.
-
-If for some reason @file{trunk/Identity/Themes/Models} structure
-requires translation entries, we need to re-oraganize the current
-directory structure accordingly.
-@end quotation
-
-Translation entries, as described above, can be re-used by similar
-identity entries. For example the following identity entries:
-
-@verbatim
-trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/
-trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Progress/
-trunk/Identity/Themes/Motifs/Mettle/Distro/Anaconda/Progress/
-@end verbatim
-
-are all valid identity entries able to re-use translation files inside
-Anaconda progress translation entry (the one shown in our example
-above). This way, you can create several identity entries and maintain
-just one translation entry for all of them. Once you change the
-translation files inside the common translation entry, changes inside
-identity entries will take effect inside the next you render them.
-
-Trying to make things plain and simple: inside CentOS Artwork
-Repository, graphic designers can concentrate their efforts in
-artworks look and feel (the identity entries), and translators in
-artworks translations (the translation entries).
-
-@subsubsection Translation Markers
-@anchor{trunk:Translations:TranslationMarkers}
-@cindex Translation markers
-
-Translation markers are used in ``Theme Model Designs'' and
-``Translation Files'' as replacement patterns to commit content
-translation. When you are rendering content using
-@command{centos-art} script inisde @file{trunk/Identity} structure,
-artistic motifs and translation files are applied to model designs to
-produce translated content as result. In order to have the appropriate
-translation in content rendered, markers defintion in translation
-files should match markers in model designs exactly.
-
-Translation markers can be whatever text you want, but as convenction
-we use the following to represent releases of CentOS distribution:
-
-@table @samp
-@item =MINOR_RELEASE=
-Replace with minor release of CentOS distribution. In the schema M.N, the minor
-release is represented by the N letter.
-@item =MAJOR_RELEASE=
-Replace with major release of CentOS distribution. In the schema M.N,
-the major release is represented by the M letter.
-@item =RELEASE=
-Replace the full release of CentOS distribution. It is
-@samp{=MAJOR_RELEASE=.=MINOR_RELEASE=} basically.
-@end table
-
-Specific translation markers convenctions are described inside
-specific translation entries. Read translation entries documentation
-to know more about supported translation markers.
-
-Translation markers standardization creates a common point of
-reference for translators and graphic designers. To have translation
-markers well defined makes possible that translators and graphic
-designers can work together but independently one another.
-
-@subsubsection Translation Files
-@cindex Translation files
-
-Translation files are text files with @command{sed} commands inside,
-replacement commands mainly. As convenction, translation file names
-end in @samp{.sed}. Translation files are used by @command{centos-art}
-script to produce translated artworks for specific major releases of
-CentOS Distribution. There are common translation files, specific
-translation, and template translation files.
-
-For example, the Firstboot artwork of CentOS distribution uses the
-images @file{splash-small.png} and @file{firstboot-left.png} as based
-to control its visual style. The @file{splash-small.png} image
-contains, in its graphic design, the release number information of
-CentOS distribution. So the @file{splash-small.png} is
-release-specific. In the other hand, the @file{firstboot-left.png}
-doesn't contain release number information. So the
-@file{firstboot-left.png} is not release-specific.
-
-If we want to produce Firstboot artwork for different major releases
-of CentOS distribution, using a monolithic visual identity, all
-Firstboot images should have the same visual style and, at the same
-time, the release-specific information in the release-specific images.
-
-@quotation
-@strong{Note} The monolithic visual identity is implemented using
-theme models (@pxref{trunk Identity Themes Models}) and artistic
-motifs (@pxref{trunk Identity Themes Motifs}).
-@end quotation
-
-Assuming that both theme models and theme motifs are ready for using,
-the initial translation entry to produce Firstboot artworks would look
-like the following:
-
-@verbatim
-trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/
-|-- Tpl
-| `-- splash-small.sed
-`-- firstboot-left.sed
-@end verbatim
-
-With the translation entry above, @command{centos-art} command is able
-to produce the image @file{firstboot-left.png} only. To produce
-@file{splash-small.png} images for major releases (e.g., 3, 4, 5, and
-6) of CentOS distribution we need to produce the release-specific
-translation files using the @command{centos-art} script as following:
-
-@verbatim
-centos-art render --entry=/home/centos/artwork/trunk/Translations/Identity/Themes/BootUp/Firstboot --filter='3,4,5,6'
-@end verbatim
-
-The above command produces the following translation entiry:
-
-@verbatim
-trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/
-|-- 3
-| `-- splash-small.sed
-|-- 4
-| `-- splash-small.sed
-|-- 5
-| `-- splash-small.sed
-|-- 6
-| `-- splash-small.sed
-|-- Tpl
-| `-- splash-small.sed
-`-- firstboot-left.sed
-@end verbatim
-
-At this point @command{centos-art} is able to produce the Firstboot
-artwork images for major releases of CentOS distribution. To add new
-release-specific translation files, run the translation rendering
-command with the release number you want to produce translation files
-for in the @samp{--filter='release-number'} argument.
-
-@subsubsection Template Translation Files
-@cindex Template translation files
-
-Template translation files are translation files stored inside
-translation template directory. Template translation files are used by
-@command{centos-art} script to produce specific translation files
-only. Template translation files may be empty or contain @command{sed}
-replacement commands. If template translation files are empty files,
-the final specifc translation file built from it contains
-release-specific replacement commands only. For example, see the
-following translation entry:
-
-@verbatim
-trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/
-|-- 3
-| `-- splash-small.sed
-|-- 4
-| `-- splash-small.sed
-|-- 5
-| `-- splash-small.sed
-|-- 6
-| `-- splash-small.sed
-|-- Tpl
-| `-- splash-small.sed <-- template translation file.
-`-- firstboot-left.sed
-@end verbatim
-
-In the above exmaple, the @file{splash-small.sed} file is a template
-translation file and looks like:
-
-@verbatim
-# -------------------------------------
-# $Id: splash-small.sed 94 2010-09-18 10:59:42Z al $
-# -------------------------------------
-@end verbatim
-
-In the above template translation file there are three comments lines,
-but when you render it, the @command{centos-art} adds the
-release-specific replacement commands. In our Firstboot example, after
-rendering Firstboot translation entry, the @file{splash-small.sed}
-translation file specific to CentOS 5, looks like the following:
-
-@verbatim
-# Warning: Do not modify this file directly. This file is created
-# automatically using 'centos-art' command line interface. Any change
-# you do in this file will be lost the next time you update
-# translation files using 'centos-art' command line interface. If you
-# want to improve the content of this translation file, improve its
-# template file instead and run the 'centos-art' command line
-# interface later to propagate your changes.
-# -------------------------------------
-# $Id: splash-small.sed 94 2010-09-18 10:59:42Z al $
-# -------------------------------------
-
-# Release number information.
-s!=RELEASE=!=MAJOR_RELEASE=.=MINOR_RELEASE=!g
-s!=MINOR_RELEASE=!0!g
-s!=MAJOR_RELEASE=!5!g
-@end verbatim
-
-If template translation files are not empty, replacement commands
-inside template translation files are preserved inside
-release-specific translation files. For example, consider the English
-template translation file of Anaconda progress welcome slide. The
-translation template directory structure looks like the following:
-
-@verbatim
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/
-`-- Tpl
- `-- en
- `-- 01-welcome.sed
-@end verbatim
-
-and if we render translation files for CentOS 4 and CentOS 5 major
-releases, the translation entry would look like the following:
-
-@verbatim
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/
-|-- 4
-| `-- en
-| `-- 01-welcome.sed
-|-- 5
-| `-- en
-| `-- 01-welcome.sed
-`-- Tpl
- `-- en
- `-- 01-welcome.sed
-@end verbatim
-
-@quotation
-@strong{Note} Release-specific translation directories preserve
-template translation directory structure and file names.
-@end quotation
-
-In the example above, the template translation file looks like the
-following:
-
-@verbatim
-# ------------------------------------------------------------
-# $Id: 01-welcome.sed 94 2010-09-18 10:59:42Z al $
-# ------------------------------------------------------------
-s/=TITLE=/Welcome to CentOS =MAJOR_RELEASE= !/
-s/=TEXT1=/Thank you for installing CentOS =MAJOR_RELEASE=./
-s/=TEXT2=/CentOS is an enterprise-class Linux Distribution derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor./
-s/=TEXT3=/CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. CentOS mainly changes packages to remove upstream vendor branding and artwork./
-s/=TEXT4=//
-s/=TEXT5=//
-s/=TEXT6=//
-s!=URL=!http://www.centos.org/!
-@end verbatim
-
-and, after render the translation entry, specific translation files
-look like the following:
-
-@verbatim
-# Warning: Do not modify this file directly. This file is created
-# automatically using 'centos-art' command line interface. Any change
-# you do in this file will be lost the next time you update
-# translation files using 'centos-art' command line interface. If you
-# want to improve the content of this translation file, improve its
-# template file instead and run the 'centos-art' command line
-# interface later to propagate your changes.
-# ------------------------------------------------------------
-# $Id: 01-welcome.sed 94 2010-09-18 10:59:42Z al $
-# ------------------------------------------------------------
-
-s/=TITLE=/Welcome to CentOS =MAJOR_RELEASE= !/
-s/=TEXT1=/Thank you for installing CentOS =MAJOR_RELEASE=./
-s/=TEXT2=/CentOS is an enterprise-class Linux Distribution derived from sources freely provided to the public by a prominen t North American Enterprise Linux vendor./
-s/=TEXT3=/CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. Cent OS mainly changes packages to remove upstream vendor branding and artwork./
-s/=TEXT4=//
-s/=TEXT5=//
-s/=TEXT6=//
-s!=URL=!http://www.centos.org/!
-
-# Release number information.
-s!=RELEASE=!=MAJOR_RELEASE=.=MINOR_RELEASE=!g
-s!=MINOR_RELEASE=!0!g
-s!=MAJOR_RELEASE=!5!g
-@end verbatim
-
-In the example above, relevant lines begin with the @samp{s} word
-followed by a separation character (e.g., @samp{/}, @samp{!}, etc.).
-These lines have the following format:
-
-@verbatim
-s/REGEXP/REPLACEMENT/FLAGS
-@end verbatim
-
-The @samp{/} characters may be uniformly replaced by any other single
-character within any given @command{s} command. The @samp{/}
-character (or whatever other character is used in its stead) can
-appear in the REGEXP or REPLACEMENT only if it is preceded by a
-@samp{\} character.
-
-The @command{s} command is probably the most important in
-@command{sed} and has a lot of different options. Its basic concept
-is simple: the @command{s} command attempts to match the pattern space
-against the supplied REGEXP; if the match is successful, then that
-portion of the pattern space which was matched is replaced with
-REPLACEMENT.
-
-In the context of our translation files, the REGEXP is where you
-define translation markers and REPLACEMENT where you define the
-translation text you want to have after artworks rendering. Sometimes
-we use the FLAG component with the @samp{g} command to apply the
-replacements globally.
-
-@quotation
-@strong{Tip} More information about how to use @command{sed}
-replacement commands and flags is available in @command{sed}
-documentation manual. To read @command{sed} documentation manual type
-the following command:
-@verbatim
-info sed
-@end verbatim
-@end quotation
-
-Inside translation files, you can use translation markers not only
-inside the REGEXP but in the REPLACEMENT too. In order for this
-configuration to work, the REPLACEMENT of translation markers needs to
-be define @emph{after} its definition. For example, see in the
-release-specific translation file above, how the
-@samp{s!=MAJOR_RELASE=!5!g} replacement command is defined
-@emph{after} @samp{=MAJOR_RELASE=} translation marker definition in
-the REPLACEMENT of @samp{=TITLE=} translation marker replacement
-command.
-
-@subsubsection Common Translation Files
-@cindex Common translation files
-
-Common translation files contain common translations or no
-translation at all for their related artworks. They are in the root
-directory of the translation entry. Common translation files create
-common artworks for all major releases of CentOS Distribution.
-
-Translation entries, with common translation files inside, look like
-the following:
-
-@verbatim
-trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/
-|-- 3
-| `-- splash-small.sed
-|-- 4
-| `-- splash-small.sed
-|-- 5
-| `-- splash-small.sed
-|-- 6
-| `-- splash-small.sed
-|-- Tpl
-| `-- splash-small.sed
-`-- firstboot-left.sed <-- common translation file.
-@end verbatim
-
-@subsubsection Specific Translation Files
-@cindex Specific translation files
-
-Specific translation files contain specific translations for their
-related artworks. Specific translation files are not in the root
-directory of the translation entry, but inside directories which
-describe the type of translation they are doing. Specific translation
-files are produced automatically using the @command{centos-art}
-script.
-
-@verbatim
-trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/
-|-- 3
-| `-- splash-small.sed <-- CentOS 3 specific translation file.
-|-- 4
-| `-- splash-small.sed <-- CentOS 4 specific translation file.
-|-- 5
-| `-- splash-small.sed <-- CentOS 5 specific translation file.
-|-- 6
-| `-- splash-small.sed <-- CentOS 6 specific translation file.
-|-- Tpl
-| `-- splash-small.sed
-`-- firstboot-left.sed
-@end verbatim
-
-@subsubsection Translation Rendering
-@cindex Translation rendering
-
-When rendering translations, the @command{centos-art} script checks
-the translation entry to verify that it has a translation template
-directory inside. The translation template directory (@file{Tpl/})
-contains common translation files used to build release-specific
-translation files. If the translation template directory doesn't exist
-inside the translation entry the translation rendering fails. In this
-case the @command{centos-art} script outputs a message and quits
-script execution.
-
-@subsubsection Translation (Pre-)Rendering Configuration Scripts
-@cindex Translation configuration scripts
-@cindex Translation pre-rendering configuration scripts
-
-When the @command{centos-art} script finds a translation template
-directory inside translation entry, it looks for translations
-pre-rendering configuration scripts for that translation entry.
-Translation pre-rendering configuration scripts let you extend
-translation default functionality (described below).
-
-Translation pre-rendering configuration scripts are stored under
-@file{trunk/Scripts} directory, specifically under the appropriate
-language implementation. If you are using @command{centos-art} Bash
-implementation, the translation pre-rendering scripts are store in the
-@file{trunk/Scripts/Bash/Config} location; if you are using
-@command{centos-art} Python implementation, then translation
-pre-rendering scripts are stored in the
-@file{trunk/Scripts/Python/Config} location, and so on for other
-implementations.
-
-Bash translation pre-rendering configuration scripts look like the
-following:
-
-@verbatim
-#!/bin/bash
-#
-# render_loadConfig.sh -- brief description here.
-#
-# Copyright (C) YEAR YOURNAME
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
-# (at your option) any later version.
-#
-# This program is distributed in the hope that it will be useful, but
-# WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-# General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
-# USA.
-#
-# ----------------------------------------------------------------------
-# $Id: render_loadConfig.sh 94 2010-09-18 10:59:42Z al $
-# ----------------------------------------------------------------------
-
-function render_loadConfig {
-...
-}
-@end verbatim
-
-Translation pre-rendering scripts are function scripts loaded and
-executed when rendering a translation entry. Translation pre-rendering
-scripts are loaded using the translation entry being rendered as
-reference. For example, suppose you are using the
-@command{centos-art} Bash implementation, and you are rendering
-translations for CentOS brands, in this situation the translation
-entry would be:
-
-@verbatim
-trunk/Translations/Identity/Brands
-@end verbatim
-
-and the entry inside the translation pre-rendering configuration
-structure would be:
-
-@verbatim
-trunk/Scripts/Bash/Config/Identity/Brands
-@end verbatim
-
-Once the @command{centos-art} script detects that translation
-pre-rendering configuration directory exists, the @command{centos-art}
-script looks for the translation pre-rendering configuration file. If
-the translation pre-rendering configuration file exists, it is loaded
-and executed. Once the translation pre-rendering configuration file
-has been executed the translation rendering process is over, and so
-the script execution.
-
-@quotation
-@strong{Note} Translation pre-rendering configuration files have the
-following form:
-@verbatim
-render.conf.extension
-@end verbatim
-where @samp{extension} refers the programming language implementation
-you are using. For example, @samp{sh} for Bash, @samp{py} for Python,
-@samp{pl} for Perl, and so on for other implementations.
-@end quotation
-
-As we are using Bash implementation to describe the translation
-pre-rendering configuration example, the translation pre-rendering
-configuration file that @command{centos-art} looks for, inside the
-above translation pre-rendering configuration directory, is
-@file{render.conf.sh}.
-
-@subsubsection Translation Rendering Default Functionality
-@cindex Translation rendering default functionality
-
-In the other hand, if the translation pre-rendering configuration file
-doesn't exist, or it isn't written as function script, the
-@command{centos-art} script ignore translation pre-rendering
-configuration functionality and passes to render translation using
-default functionality instead.
-
-The translation rendering default functionality takes template
-translation directory structure, duplicates it for each release number
-specified in the @samp{--filter='release-number'} argument and
-produces release-specific directories. As part of template translation
-duplication process take place, the @command{centos-art} script adds
-release-specific replacement commands for each specific translation
-file inside release-specific directories. As result, specific
-translation files, inside release-specific directories, contain
-template translation replacement commands @emph{plus},
-release-specific replacement commands.
-
-@quotation
-@strong{Note} Release-specific replacement commands are standardized
-inside @command{centos-art} script using predifined release
-translation markers. Release translation markers are described in the
-translation marker section
-(@pxref{trunk:Translations:TranslationMarkers, Translation Markers}).
-@end quotation
-
-@c --- figure required to illustrate this section.
-
-@subsection Usage
-@cindex How to render translation files
-
-@table @samp
-@item centos-art render --entry='path/to/dir'
-
-When @samp{path/to/dir} refers one directory under
-@samp{trunk/Translations}, this command orverwrites available
-translation files using translation templates.
-
-@item centos-art render --entry='path/to/dir' --filter='pattern'
-
-When @samp{path/to/dir} refers one directory under
-@file{trunk/Translations}, this command renders release-specific
-translation files as you specify in the @samp{--filter='pattern'}
-argument. In this case, @samp{pattern} not a regular expression but an
-number (e.g., @samp{5}) or a list of numbers separated by commas
-(e.g., @samp{3,4,5,6}) that specify the major release of CentOS
-distribution you want to render translations for.
-@end table
-
-@subsection See also
-
-@menu
-* trunk Translations Identity Brands::
-* trunk Translations Identity Fonts::
-* trunk Translations Identity Models::
-* trunk Translations Identity Release::
-* trunk Translations Identity Themes::
-* trunk Identity::
-@end menu
diff --git a/Manuals/Repository/trunk/Translations/Identity.texi b/Manuals/Repository/trunk/Translations/Identity.texi
deleted file mode 100644
index 3949170..0000000
--- a/Manuals/Repository/trunk/Translations/Identity.texi
+++ /dev/null
@@ -1,29 +0,0 @@
-@subsection Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subsection Description
-
-@itemize
-@item ...
-@end itemize
-
-@subsection Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subsection See also
-
-@menu
-* trunk Translations Identity Brands::
-* trunk Translations Identity Fonts::
-* trunk Translations Identity Models::
-* trunk Translations Identity Release::
-* trunk Translations Identity Themes::
-* trunk Translations Identity Widgets::
-* trunk Identity::
-@end menu
diff --git a/Manuals/Repository/trunk/Translations/Identity/Brands.texi b/Manuals/Repository/trunk/Translations/Identity/Brands.texi
deleted file mode 100644
index c20a12a..0000000
--- a/Manuals/Repository/trunk/Translations/Identity/Brands.texi
+++ /dev/null
@@ -1,105 +0,0 @@
-@subsection Goals
-
-@itemize
-@item Organize brands' translation files.
-@end itemize
-
-@subsection Description
-
-Translation files, inside @file{trunk/Translations/Identity/Brands}
-translation entry, don't use default rendering translation
-functionality, they use the following translation pre-rendering
-configuration file instead:
-
-@verbatim
-/home/centos/artwork/trunk/Translation/Identity/Brands/render.conf.sh
-@end verbatim
-
-Inside @file{trunk/Translations/Identity/Brands} translation entry,
-translation files are symbolic links pointing to the common template
-translation structure, inside the translation template (@samp{Tpl/})
-directory.
-
-Inside @file{trunk/Translations/Identity/Brands} translation entry,
-translation files are created using identity design templates as
-reference. The translation pre-rendering script creates a translation
-structure where the translation template (@samp{Tpl/}) directory
-structure applies to each single design template available.
-
-For example, if the brands' translation template (@samp{Tpl/})
-directory has 30 translation files, and there are 20 design templates;
-the brands' translation pre-rendering script creates a translation
-structure of symbolic links where the 30 translation files apply the
-20 design templates one by one, producing 600 translation symbolic
-links as result. At this point, when rendering identity, the
-@command{centos-art} script considers translation symbolic links as
-translation files.
-
-Translation file names, inside brands' translation template
-(@samp{Tpl}) directory have special meaning:
-
-@subsubsection Conventional file names
-@cindex Translation brands file names
-
-Convenctional file names look like @file{blue.sed}, @file{2c-a.sed},
-etc. Replacement commands inside translation file are applied to
-design templates and translation file names are used as final image
-name. The image dimensions use the same dimensions that design
-template has.
-
-@subsubsection Numeric file names
-@cindex Translation brands file names
-
-Numeric file names look like @file{300.sed}, @file{200.sed}, etc.
-Replacements commands inside translation files are applied to design
-templates, and translation file names are used as final image name.
-The final image is saved using an specific @samp{width} defined by the
-number part of the translation file name. The image @samp{height} is
-automatically scaled based on the previous @samp{width} definition to
-maintain the designing ratio.
-
-For example, if your design template has 400x200 pixels of dimension,
-and you apply a translation file named `300.sed' to it, the final
-image you get as result will have 300x100 pixels of dimension. The
-same is true if you use higher numbers like `1024.sed', `2048.sed',
-etc. In these cases you have bigger images proportionally.
-
-As we are using scalable vector graphics to design identity templates,
-the image size you produce is not limitted in size. You can use one
-design template produced in 400x200 pixels to produce larger or
-shorter PNG images using numeric translation files as described
-above.
-
-@subsubsection Translation markers
-
-Inside @file{trunk/Translations/Identity/Brands/}, translation files
-combine the following translation markers:
-
-@table @samp
-@item #000000
-
-Specify which color to use when rendering brand images.
-
-@quotation
-@strong{Note} As translation files inside
-@file{trunk/Translations/Identity/Brands} are symbolic links that
-point to template translation files, translation markers are defined
-inside template translation files.
-@end quotation
-@end table
-
-@subsection Usage
-@cindex How to render brands' translation files
-
-To render brands' translation files, use the following command:
-
-@verbatim
-centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands
-@end verbatim
-
-@subsection See also
-
-@menu
-* trunk Translations Identity Brands Tpl::
-* trunk Identity Brands::
-@end menu
diff --git a/Manuals/Repository/trunk/Translations/Identity/Brands/Tpl.texi b/Manuals/Repository/trunk/Translations/Identity/Brands/Tpl.texi
deleted file mode 100644
index b53171e..0000000
--- a/Manuals/Repository/trunk/Translations/Identity/Brands/Tpl.texi
+++ /dev/null
@@ -1,10 +0,0 @@
-@subsection Goals
-
-@subsection Description
-
-@subsection Usage
-
-@subsection See also
-
-@menu
-@end menu
diff --git a/Manuals/Repository/trunk/Translations/Identity/Fonts.texi b/Manuals/Repository/trunk/Translations/Identity/Fonts.texi
deleted file mode 100644
index 2699334..0000000
--- a/Manuals/Repository/trunk/Translations/Identity/Fonts.texi
+++ /dev/null
@@ -1,62 +0,0 @@
-@subsection Goals
-
-This section exists to organize fonts translation files.
-@subsection Description
-
-Translation files, inside @file{trunk/Translations/Fonts}, have the
-following structure:
-
-@verbatim
-s!font-family:Denmark!font-family:DejaVu LGC Sans!
-s!font-weight:normal!font-weight:bold!
-s!font-style:normal!font-style:italic!
-@end verbatim
-
-Inside @file{trunk/Translations/Fonts}, there is one translation file
-for each font preview image you want to produce. This way, we create
-one translation file for each font-family we use somewhere inside
-CentOS visual identity.
-
-@quotation
-@strong{Important} Do not create translation files for
-font-families not used somewhere inside CentOS visual identity. The
-identity of font entry (@pxref{trunk Identity Fonts}) is used as
-reference when someone needs to know which font-families are allowed
-to use inside CentOS visual identity.
-@end quotation
-
-@subsubsection Translation Markers
-
-Inside @file{trunk/Translations/Identity/Fonts}, translation files
-combine the following translation markers:
-
-@table @samp
-@item font-family:Denmark
-Specify which font family to use when rendering font preview images.
-@item font-weight:normal
-Specify which font weight to use when rendering font preview images.
-@item font-style:normal
-Specify which font style to use when rendering font preview images.
-@end table
-
-@subsection Usage
-@cindex How to render fonts' translation files
-
-Inside @file{trunk/Translations/Fonts} you use your favorite text
-editor to create translation files. Inside
-@file{trunk/Translations/Fonts} there is not translation template
-directory (@file{Tpl/}), nor translation rendering using
-@command{centos-art} script. For example, to create the
-@file{dejavu_lgc_sans-boldoblique.sed} translation file using
-@command{vim} editor, type the following command:
-
-@verbatim
-vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed
-@end verbatim
-
-@subsection See also
-
-@menu
-* trunk Identity Fonts::
-@end menu
-
diff --git a/Manuals/Repository/trunk/Translations/Identity/Models.texi b/Manuals/Repository/trunk/Translations/Identity/Models.texi
deleted file mode 100644
index b53171e..0000000
--- a/Manuals/Repository/trunk/Translations/Identity/Models.texi
+++ /dev/null
@@ -1,10 +0,0 @@
-@subsection Goals
-
-@subsection Description
-
-@subsection Usage
-
-@subsection See also
-
-@menu
-@end menu
diff --git a/Manuals/Repository/trunk/Translations/Identity/Release.texi b/Manuals/Repository/trunk/Translations/Identity/Release.texi
deleted file mode 100644
index b53171e..0000000
--- a/Manuals/Repository/trunk/Translations/Identity/Release.texi
+++ /dev/null
@@ -1,10 +0,0 @@
-@subsection Goals
-
-@subsection Description
-
-@subsection Usage
-
-@subsection See also
-
-@menu
-@end menu
diff --git a/Manuals/Repository/trunk/Translations/Identity/Themes.texi b/Manuals/Repository/trunk/Translations/Identity/Themes.texi
deleted file mode 100644
index b53171e..0000000
--- a/Manuals/Repository/trunk/Translations/Identity/Themes.texi
+++ /dev/null
@@ -1,10 +0,0 @@
-@subsection Goals
-
-@subsection Description
-
-@subsection Usage
-
-@subsection See also
-
-@menu
-@end menu
diff --git a/Manuals/Repository/trunk/Translations/Identity/Themes/Backgrounds.texi b/Manuals/Repository/trunk/Translations/Identity/Themes/Backgrounds.texi
deleted file mode 100644
index fb39647..0000000
--- a/Manuals/Repository/trunk/Translations/Identity/Themes/Backgrounds.texi
+++ /dev/null
@@ -1,22 +0,0 @@
-@subsection Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subsection Description
-
-@itemize
-@item ...
-@end itemize
-
-@subsection Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subsection See also
-
-@menu
-@end menu
diff --git a/Manuals/Repository/trunk/Translations/Identity/Themes/Distro/Anaconda/Progress.texi b/Manuals/Repository/trunk/Translations/Identity/Themes/Distro/Anaconda/Progress.texi
deleted file mode 100644
index 812b34d..0000000
--- a/Manuals/Repository/trunk/Translations/Identity/Themes/Distro/Anaconda/Progress.texi
+++ /dev/null
@@ -1,94 +0,0 @@
-@subsection Goals
-
-@itemize
-@item Organize Anaconda progress translation templates.
-@item Organize Anaconda progress translation files in several
-languages and major releases of CentOS distribution.
-@end itemize
-
-@subsection Description
-
-Use the following command to produce translation files based:
-
-@example
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
-`-- Tpl
- |-- en
- | |-- 01-welcome.sed
- | |-- 02-donate.sed
- | `-- 03-yum.sed
- `-- es
- |-- 01-welcome.sed
- |-- 02-donate.sed
- `-- 03-yum.sed
-@end example
-
-In order to produce the slide images in PNG format we need to have the
-translation files first. So we use the following commands to create
-translation files for CentOS 3, 4, and 5 major releases:
-
-@example
-centos-art render --translation --filter='3,4,5'
-@end example
-
-The above commands will produce the following translation structure:
-
-@example
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
-|-- 3
-| |-- en
-| | |-- 01-welcome.sed
-| | |-- 02-donate.sed
-| | `-- 03-yum.sed
-| `-- es
-| |-- 01-welcome.sed
-| |-- 02-donate.sed
-| `-- 03-yum.sed
-|-- 4
-| |-- en
-| | |-- 01-welcome.sed
-| | |-- 02-donate.sed
-| | `-- 03-yum.sed
-| `-- es
-| |-- 01-welcome.sed
-| |-- 02-donate.sed
-| `-- 03-yum.sed
-|-- 5
-| |-- en
-| | |-- 01-welcome.sed
-| | |-- 02-donate.sed
-| | `-- 03-yum.sed
-| `-- es
-| |-- 01-welcome.sed
-| |-- 02-donate.sed
-| `-- 03-yum.sed
-`-- Tpl
- |-- en
- | |-- 01-welcome.sed
- | |-- 02-donate.sed
- | `-- 03-yum.sed
- `-- es
- |-- 01-welcome.sed
- |-- 02-donate.sed
- `-- 03-yum.sed
-@end example
-
-At this point we have all the translation files we need to produce
-Anaconda progress welcome, donate and yum slides images; in English
-and Spanish languages; for CentOS 3, CentOS 4, and CentOS 5. That is,
-a sum of 18 images around.
-
-Now, with translation files in place, let's move to
-@file{trunk/Identity} structure and render them.
-
-@itemize
-@item @xref{trunk Identity Themes Motifs Modern Distro Anaconda Progress}.
-@end itemize
-
-@subsection Usage
-
-Translation rendering is described in @samp{trunk/Translations}
-documentation entry (@pxref{trunk Translations}).
-
-
-@subsection See also
diff --git a/Manuals/Repository/trunk/Translations/Identity/Widgets.texi b/Manuals/Repository/trunk/Translations/Identity/Widgets.texi
deleted file mode 100644
index ded7872..0000000
--- a/Manuals/Repository/trunk/Translations/Identity/Widgets.texi
+++ /dev/null
@@ -1,23 +0,0 @@
-@subsection Goals
-
-@itemize
-@item ...
-@end itemize
-
-@subsection Description
-
-@itemize
-@item ...
-@end itemize
-
-@subsection Usage
-
-@itemize
-@item ...
-@end itemize
-
-@subsection See also
-
-@menu
-* trunk Translations Identity Widgets::
-@end menu
diff --git a/Manuals/Repository/trunk/chapter-menu.texi b/Manuals/Repository/trunk/chapter-menu.texi
index 08db957..662cda9 100644
--- a/Manuals/Repository/trunk/chapter-menu.texi
+++ b/Manuals/Repository/trunk/chapter-menu.texi
@@ -59,15 +59,4 @@
* trunk Scripts Bash Locale::
* trunk Scripts Perl::
* trunk Scripts Python::
-* trunk Translations::
-* trunk Translations Identity::
-* trunk Translations Identity Brands::
-* trunk Translations Identity Brands Tpl::
-* trunk Translations Identity Fonts::
-* trunk Translations Identity Models::
-* trunk Translations Identity Release::
-* trunk Translations Identity Themes::
-* trunk Translations Identity Themes Backgrounds::
-* trunk Translations Identity Themes Distro Anaconda Progress::
-* trunk Translations Identity Widgets::
@end menu
diff --git a/Manuals/Repository/trunk/chapter-nodes.texi b/Manuals/Repository/trunk/chapter-nodes.texi
index 14808cd..65278a8 100644
--- a/Manuals/Repository/trunk/chapter-nodes.texi
+++ b/Manuals/Repository/trunk/chapter-nodes.texi
@@ -298,58 +298,3 @@
@cindex trunk Scripts Python
@include trunk/Scripts/Python.texi
-@node trunk Translations
-@section trunk/Translations
-@cindex trunk Translations
-@include trunk/Translations.texi
-
-@node trunk Translations Identity
-@section trunk/Translations/Identity
-@cindex trunk Translations Identity
-@include trunk/Translations/Identity.texi
-
-@node trunk Translations Identity Brands
-@section trunk/Translations/Identity/Brands
-@cindex trunk Translations Identity Brands
-@include trunk/Translations/Identity/Brands.texi
-
-@node trunk Translations Identity Brands Tpl
-@section trunk/Translations/Identity/Brands/Tpl
-@cindex trunk Translations Identity Brands Tpl
-@include trunk/Translations/Identity/Brands/Tpl.texi
-
-@node trunk Translations Identity Fonts
-@section trunk/Translations/Identity/Fonts
-@cindex trunk Translations Identity Fonts
-@include trunk/Translations/Identity/Fonts.texi
-
-@node trunk Translations Identity Models
-@section trunk/Translations/Identity/Models
-@cindex trunk Translations Identity Models
-@include trunk/Translations/Identity/Models.texi
-
-@node trunk Translations Identity Release
-@section trunk/Translations/Identity/Release
-@cindex trunk Translations Identity Release
-@include trunk/Translations/Identity/Release.texi
-
-@node trunk Translations Identity Themes
-@section trunk/Translations/Identity/Themes
-@cindex trunk Translations Identity Themes
-@include trunk/Translations/Identity/Themes.texi
-
-@node trunk Translations Identity Themes Backgrounds
-@section trunk/Translations/Identity/Themes/Backgrounds
-@cindex trunk Translations Identity Themes Backgrounds
-@include trunk/Translations/Identity/Themes/Backgrounds.texi
-
-@node trunk Translations Identity Themes Distro Anaconda Progress
-@section trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
-@cindex trunk Translations Identity Themes Distro Anaconda Progress
-@include trunk/Translations/Identity/Themes/Distro/Anaconda/Progress.texi
-
-@node trunk Translations Identity Widgets
-@section trunk/Translations/Identity/Widgets
-@cindex trunk Translations Identity Widgets
-@include trunk/Translations/Identity/Widgets.texi
-