From 63f275205a168773476381b14dc18b8a2f105883 Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: Dec 02 2010 16:08:19 +0000 Subject: Update documentation manual. --- diff --git a/Manuals/en/Html/Repository/repository.html b/Manuals/en/Html/Repository/repository.html index ea19874..bac5fb6 100644 --- a/Manuals/en/Html/Repository/repository.html +++ b/Manuals/en/Html/Repository/repository.html @@ -63,7 +63,7 @@ ul.toc {list-style: none} - +
[Top] [Contents][Index][Index] [ ? ]

CentOS Artwork Repository

@@ -92,9 +92,9 @@ Documentation License. 3. trunk   -Index   +Index   -List of Figures   +List of Figures   @@ -105,7 +105,7 @@ Documentation License. - +
[Top] [Contents][Index][Index] [ ? ]

diff --git a/Manuals/en/Html/Repository/repository_1.html b/Manuals/en/Html/Repository/repository_1.html index fdac3bb..6ee0568 100644 --- a/Manuals/en/Html/Repository/repository_1.html +++ b/Manuals/en/Html/Repository/repository_1.html @@ -71,7 +71,7 @@ ul.toc {list-style: none}   [Top] [Contents] -[Index] +[Index] [ ? ] diff --git a/Manuals/en/Html/Repository/repository_10.html b/Manuals/en/Html/Repository/repository_10.html index 34c8fa1..ecbb55f 100644 --- a/Manuals/en/Html/Repository/repository_10.html +++ b/Manuals/en/Html/Repository/repository_10.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -113,7 +113,7 @@ to HTML design models.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_11.html b/Manuals/en/Html/Repository/repository_11.html index 4b4f4b3..0481a68 100644 --- a/Manuals/en/Html/Repository/repository_11.html +++ b/Manuals/en/Html/Repository/repository_11.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -114,7 +114,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_12.html b/Manuals/en/Html/Repository/repository_12.html index cab5f42..7e20b64 100644 --- a/Manuals/en/Html/Repository/repository_12.html +++ b/Manuals/en/Html/Repository/repository_12.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -118,7 +118,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_13.html b/Manuals/en/Html/Repository/repository_13.html index bfb4134..c9305e4 100644 --- a/Manuals/en/Html/Repository/repository_13.html +++ b/Manuals/en/Html/Repository/repository_13.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -114,7 +114,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_14.html b/Manuals/en/Html/Repository/repository_14.html index 9ec387e..abd3b76 100644 --- a/Manuals/en/Html/Repository/repository_14.html +++ b/Manuals/en/Html/Repository/repository_14.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -446,7 +446,7 @@ CentOS [base] and CentOS [updates] repositories.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_15.html b/Manuals/en/Html/Repository/repository_15.html index 2b31d34..b668706 100644 --- a/Manuals/en/Html/Repository/repository_15.html +++ b/Manuals/en/Html/Repository/repository_15.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -114,7 +114,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_16.html b/Manuals/en/Html/Repository/repository_16.html index d0aea0b..089619c 100644 --- a/Manuals/en/Html/Repository/repository_16.html +++ b/Manuals/en/Html/Repository/repository_16.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -106,7 +106,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_17.html b/Manuals/en/Html/Repository/repository_17.html index 9ff65f6..07f3cf9 100644 --- a/Manuals/en/Html/Repository/repository_17.html +++ b/Manuals/en/Html/Repository/repository_17.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -111,7 +111,7 @@ final CentOS themes. CentOS themes can be tagged as "Default" or 3.15 trunk/Identity/Themes/Models   -3.59 trunk/Translations/Identity/Themes   +3.57 trunk/Translations/Identity/Themes   @@ -122,7 +122,7 @@ final CentOS themes. CentOS themes can be tagged as "Default" or   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_18.html b/Manuals/en/Html/Repository/repository_18.html index a935d5c..3ee915a 100644 --- a/Manuals/en/Html/Repository/repository_18.html +++ b/Manuals/en/Html/Repository/repository_18.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -120,7 +120,7 @@ a directory to the list. By default you have the `See section   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_19.html b/Manuals/en/Html/Repository/repository_19.html index 7c16156..2d272d3 100644 --- a/Manuals/en/Html/Repository/repository_19.html +++ b/Manuals/en/Html/Repository/repository_19.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -118,7 +118,7 @@ themes are maintained by CentOS Community.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_2.html b/Manuals/en/Html/Repository/repository_2.html index 869f71b..37f372d 100644 --- a/Manuals/en/Html/Repository/repository_2.html +++ b/Manuals/en/Html/Repository/repository_2.html @@ -71,7 +71,7 @@ ul.toc {list-style: none}   [Top] [Contents] -[Index] +[Index] [ ? ] diff --git a/Manuals/en/Html/Repository/repository_20.html b/Manuals/en/Html/Repository/repository_20.html index 1b650cb..31940e9 100644 --- a/Manuals/en/Html/Repository/repository_20.html +++ b/Manuals/en/Html/Repository/repository_20.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -119,7 +119,7 @@ described in See section Theme Motifs.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_21.html b/Manuals/en/Html/Repository/repository_21.html index e7f4151..dafc666 100644 --- a/Manuals/en/Html/Repository/repository_21.html +++ b/Manuals/en/Html/Repository/repository_21.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -178,7 +178,7 @@ the CentOS brand will exonerate user form visual isolation.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_22.html b/Manuals/en/Html/Repository/repository_22.html index 27fb59a..9bf110c 100644 --- a/Manuals/en/Html/Repository/repository_22.html +++ b/Manuals/en/Html/Repository/repository_22.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -106,7 +106,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_23.html b/Manuals/en/Html/Repository/repository_23.html index 4bd50ab..d56f006 100644 --- a/Manuals/en/Html/Repository/repository_23.html +++ b/Manuals/en/Html/Repository/repository_23.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -119,7 +119,7 @@ examples of promotion designs.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_24.html b/Manuals/en/Html/Repository/repository_24.html index ed4b7c9..d197bda 100644 --- a/Manuals/en/Html/Repository/repository_24.html +++ b/Manuals/en/Html/Repository/repository_24.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -118,7 +118,7 @@ HTML standards should be consider here.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_25.html b/Manuals/en/Html/Repository/repository_25.html index 8e1fdea..9600844 100644 --- a/Manuals/en/Html/Repository/repository_25.html +++ b/Manuals/en/Html/Repository/repository_25.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -202,7 +202,7 @@ works are released under   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_26.html b/Manuals/en/Html/Repository/repository_26.html index 4ff0df9..6d9462e 100644 --- a/Manuals/en/Html/Repository/repository_26.html +++ b/Manuals/en/Html/Repository/repository_26.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -137,7 +137,7 @@ production of new artistic motifs very quickly 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 `centos-art.sh' script -(see section trunk/Scripts/Bash) inside the CentOS Artwork Repository. +(see section trunk/Scripts/Bash) 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 @@ -289,7 +289,7 @@ visual identity.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_27.html b/Manuals/en/Html/Repository/repository_27.html index 48af9e9..d71270b 100644 --- a/Manuals/en/Html/Repository/repository_27.html +++ b/Manuals/en/Html/Repository/repository_27.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.24 trunk/Identity/Themes/Motifs/Flame/Distro/Anaconda +CentOS Artwork Repository: 3.24 trunk/Identity/Themes/Motifs/Modern - - + + @@ -64,35 +64,27 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.24 trunk/Identity/Themes/Motifs/Flame/Distro/Anaconda

+

3.24 trunk/Identity/Themes/Motifs/Modern

-

3.24.1 Goals

- -
    -
  • ... -
- - +

3.24.1 Presentation

+

trunk/Identity/Themes/Motifs/Modern/Concept/Img/motif +

-

3.24.2 Description

- -
    -
  • ... -
+

3.24.2 Construction

@@ -114,7 +106,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_28.html b/Manuals/en/Html/Repository/repository_28.html index be6a6bf..02bc002 100644 --- a/Manuals/en/Html/Repository/repository_28.html +++ b/Manuals/en/Html/Repository/repository_28.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.25 trunk/Identity/Themes/Motifs/Flame/Distro/BootUp +CentOS Artwork Repository: 3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds - - + + @@ -64,48 +64,156 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.25 trunk/Identity/Themes/Motifs/Flame/Distro/BootUp

+

3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds

3.25.1 Goals

    -
  • ... +
  • Organize background images for Modern theme.

3.25.2 Description

-
    -
  • ... -
+

Inside motif's `Backgrounds/' directory you can create vectorial +designs using Inkscape and background images using Gimp. Later, you +can export background images as `.png' and load them in your +vectorial design project using Inkscape's import feautre. +

+

You may need to repeat this technic for different screen resoluions. +In that case you need to create one file for each screen resolution +and do the appropriate linking inside .svg to .png files. For example +if you need to produce background images in 800x600 you need to create +the following file: +

+
 
xcf/800x600.xcf
+
+

to produce the background image: +

+
 
img/800x600-bg.png
+
+

which is loaded in: +

+
 
svg/800x600.svg
+
+

to produce the final background image: +

+
 
img/800x600.png         
+
+

The `img/800x600.png' background image is produced automatically +by means of rendering scripts. +

+

In other cases, like Anaconda's, it is possible that you need to make +some variations to one background image that don't want to appear on +regular background images of the same resolution. In this case you +need to create a new and specific background image for that art +component. For example, if you need to produce the background image +used by Anconda (800x600) art works you create the file: +

+
 
xcf/800x600-anaconda.xcf
+
+

to produce the background image: +

+
 
img/800x600-anaconda-bg.png
+
+

which is loaded in: +

+
 
svg/800x600-anaconda.svg
+
+

to produce the file: +

+
 
img/800x600-anaconda.png
+
+

The 800x600-anaconda.png file is used by all Anaconda art works +sharing a common 800x600 screen resolution (e.g., Header, Progress, +Splash, Firstboot, etc.). The Anaconda Prompt is indexed to 16 colors +and 640x480 pixels so you need to create a 640x480 background image +for it, and take the color limitation into account when designing it. +

+

Background images without artistic motif are generally used as based +to build the Background images that do contain the theme's artistic +motif. +

+

Background images are linked (using Inkscape's import feature) +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 structure you design background images for different screen +resolutions based on theme's 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.). +

+

Inside each motif directories represent 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 (Motifs) and +theme visual structures (Models) are two different working lines. +When you design an artistic motif for CentOS you concentrate on its +visual style, and eventualy, use the 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 the motif's name directory +using the model directory structure as reference. +

+

The artistic motif base structure is used by centos-art to +produce images automatically. This section describes each directory of +CentOS artistic motif base structure. +

3.25.3 Usage

-
    -
  • ... -
- +

The motif's `Backgrounds/' directory is probably the motif's core +component. Inside motif's `Backgrounds/' directory you produce +background images used by almost all theme models (e.g., Distribution, +Websites, Promotion, etc.). The motif's `Backgrounds/' directory +can contain subdirectories to help you organize the design process. +

3.25.4 See also

+ + + + + +
3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img   +
3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl   +
3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf   +
3.58 trunk/Translations/Identity/Themes/Backgrounds   +
+ @@ -114,7 +222,7 @@ ul.toc {list-style: none} - +
  [ << ] [ Up ][ >> ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_29.html b/Manuals/en/Html/Repository/repository_29.html index 213c5c6..f0d8cfa 100644 --- a/Manuals/en/Html/Repository/repository_29.html +++ b/Manuals/en/Html/Repository/repository_29.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.26 trunk/Identity/Themes/Motifs/Modern +CentOS Artwork Repository: 3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img - - + + @@ -64,49 +64,54 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.26 trunk/Identity/Themes/Motifs/Modern

+

3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img

-

3.26.1 Presentation

-

trunk/Identity/Themes/Motifs/Modern/Concept/Img/motif -

+

3.26.1 Goals

+ +
    +
  • ... +
+ + -

3.26.2 Construction

+

3.26.2 Description

3.26.3 Usage

-
    -
  • ... -
- +

In this directory is where you store all background images (e.g., +.png, .jpg, .xpm, etc.). This directory is required by +`centos-art' command line interface. +

3.26.4 See also

+ - +
[ < ] [ > ]   [ << ] [ Up ][ >> ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_3.html b/Manuals/en/Html/Repository/repository_3.html index ba8191f..45197dd 100644 --- a/Manuals/en/Html/Repository/repository_3.html +++ b/Manuals/en/Html/Repository/repository_3.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -126,83 +126,79 @@ ul.toc {list-style: none} 3.23 trunk/Identity/Themes/Motifs/Flame   -3.24 trunk/Identity/Themes/Motifs/Flame/Distro/Anaconda   +3.24 trunk/Identity/Themes/Motifs/Modern   -3.25 trunk/Identity/Themes/Motifs/Flame/Distro/BootUp   +3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds   -3.26 trunk/Identity/Themes/Motifs/Modern   +3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img   -3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds   +3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl   -3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img   +3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf   -3.29 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl   +3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress   -3.30 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf   +3.30 trunk/Identity/Themes/Motifs/Modern/Palettes   -3.31 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress   +3.31 trunk/Identity/Themes/Motifs/TreeFlower   -3.32 trunk/Identity/Themes/Motifs/Modern/Palettes   +3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds   -3.33 trunk/Identity/Themes/Motifs/TreeFlower   +3.33 trunk/Identity/Widgets   -3.34 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds   +3.34 trunk/Manuals   -3.35 trunk/Identity/Widgets   +3.35 trunk/Scripts   -3.36 trunk/Manuals   +3.36 trunk/Scripts/Bash   -3.37 trunk/Scripts   +3.37 trunk/Scripts/Bash/Functions   -3.38 trunk/Scripts/Bash   +3.38 trunk/Scripts/Bash/Functions/Help   -3.39 trunk/Scripts/Bash/Functions   +3.39 trunk/Scripts/Bash/Functions/Html   -3.40 trunk/Scripts/Bash/Functions/Help   +3.40 trunk/Scripts/Bash/Functions/Locale   -3.41 trunk/Scripts/Bash/Functions/Html   +3.41 trunk/Scripts/Bash/Functions/Path   -3.42 trunk/Scripts/Bash/Functions/Locale   +3.42 trunk/Scripts/Bash/Functions/Render   -3.43 trunk/Scripts/Bash/Functions/Path   +3.43 trunk/Scripts/Bash/Functions/Render/Config   -3.44 trunk/Scripts/Bash/Functions/Render   +3.44 trunk/Scripts/Bash/Functions/Shell   -3.45 trunk/Scripts/Bash/Functions/Render/Config   +3.45 trunk/Scripts/Bash/Functions/Svg   -3.46 trunk/Scripts/Bash/Functions/Shell   +3.46 trunk/Scripts/Bash/Functions/Verify   -3.47 trunk/Scripts/Bash/Functions/Svg   +3.47 trunk/Scripts/Bash/Locale   -3.48 trunk/Scripts/Bash/Functions/Verify   +3.48 trunk/Scripts/Perl   -3.49 trunk/Scripts/Bash/Locale   +3.49 trunk/Scripts/Python   -3.50 trunk/Scripts/Perl   +3.50 trunk/Translations   -3.51 trunk/Scripts/Python   +3.51 trunk/Translations/Identity   -3.52 trunk/Translations   +3.52 trunk/Translations/Identity/Brands   -3.53 trunk/Translations/Identity   +3.53 trunk/Translations/Identity/Brands/Tpl   -3.54 trunk/Translations/Identity/Brands   +3.54 trunk/Translations/Identity/Fonts   -3.55 trunk/Translations/Identity/Brands/Tpl   +3.55 trunk/Translations/Identity/Models   -3.56 trunk/Translations/Identity/Fonts   +3.56 trunk/Translations/Identity/Release   -3.57 trunk/Translations/Identity/Models   +3.57 trunk/Translations/Identity/Themes   -3.58 trunk/Translations/Identity/Release   +3.58 trunk/Translations/Identity/Themes/Backgrounds   -3.59 trunk/Translations/Identity/Themes   +3.59 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress   -3.60 trunk/Translations/Identity/Themes/Backgrounds   - -3.61 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress   - -3.62 trunk/Translations/Identity/Widgets   +3.60 trunk/Translations/Identity/Widgets   @@ -213,7 +209,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_30.html b/Manuals/en/Html/Repository/repository_30.html index 77ac972..91e1c34 100644 --- a/Manuals/en/Html/Repository/repository_30.html +++ b/Manuals/en/Html/Repository/repository_30.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds +CentOS Artwork Repository: 3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl - - + + @@ -64,156 +64,44 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds

+

3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl

3.27.1 Goals

    -
  • Organize background images for Modern theme. +
  • ...

3.27.2 Description

-

Inside motif's `Backgrounds/' directory you can create vectorial -designs using Inkscape and background images using Gimp. Later, you -can export background images as `.png' and load them in your -vectorial design project using Inkscape's import feautre. -

-

You may need to repeat this technic for different screen resoluions. -In that case you need to create one file for each screen resolution -and do the appropriate linking inside .svg to .png files. For example -if you need to produce background images in 800x600 you need to create -the following file: -

-
 
xcf/800x600.xcf
-
-

to produce the background image: -

-
 
img/800x600-bg.png
-
-

which is loaded in: -

-
 
svg/800x600.svg
-
-

to produce the final background image: -

-
 
img/800x600.png         
-
-

The `img/800x600.png' background image is produced automatically -by means of rendering scripts. -

-

In other cases, like Anaconda's, it is possible that you need to make -some variations to one background image that don't want to appear on -regular background images of the same resolution. In this case you -need to create a new and specific background image for that art -component. For example, if you need to produce the background image -used by Anconda (800x600) art works you create the file: -

-
 
xcf/800x600-anaconda.xcf
-
-

to produce the background image: -

-
 
img/800x600-anaconda-bg.png
-
-

which is loaded in: -

-
 
svg/800x600-anaconda.svg
-
-

to produce the file: -

-
 
img/800x600-anaconda.png
-
-

The 800x600-anaconda.png file is used by all Anaconda art works -sharing a common 800x600 screen resolution (e.g., Header, Progress, -Splash, Firstboot, etc.). The Anaconda Prompt is indexed to 16 colors -and 640x480 pixels so you need to create a 640x480 background image -for it, and take the color limitation into account when designing it. -

-

Background images without artistic motif are generally used as based -to build the Background images that do contain the theme's artistic -motif. -

-

Background images are linked (using Inkscape's import feature) -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 structure you design background images for different screen -resolutions based on theme's 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.). -

-

Inside each motif directories represent 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 (Motifs) and -theme visual structures (Models) are two different working lines. -When you design an artistic motif for CentOS you concentrate on its -visual style, and eventualy, use the 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 the motif's name directory -using the model directory structure as reference. -

-

The artistic motif base structure is used by centos-art to -produce images automatically. This section describes each directory of -CentOS artistic motif base structure. -

3.27.3 Usage

-

The motif's `Backgrounds/' directory is probably the motif's core -component. Inside motif's `Backgrounds/' directory you produce -background images used by almost all theme models (e.g., Distribution, -Websites, Promotion, etc.). The motif's `Backgrounds/' directory -can contain subdirectories to help you organize the design process. +

In this directory is where you store all the scalable vector graphics +(e.g., .svg) files. This directory is required by `centos-art' +command line interface.

3.27.4 See also

- - - - - -
3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img   -
3.29 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl   -
3.30 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf   -
3.60 trunk/Translations/Identity/Themes/Backgrounds   -
- @@ -222,7 +110,7 @@ can contain subdirectories to help you organize the design process. - +
  [ << ] [ Up ][ >> ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_31.html b/Manuals/en/Html/Repository/repository_31.html index 28820f2..4660dc1 100644 --- a/Manuals/en/Html/Repository/repository_31.html +++ b/Manuals/en/Html/Repository/repository_31.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img +CentOS Artwork Repository: 3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf - - + + @@ -64,19 +64,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img

+

3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf

@@ -90,13 +90,22 @@ ul.toc {list-style: none}

3.28.2 Description

+
    +
  • ... +
+ +

3.28.3 Usage

-

In this directory is where you store all background images (e.g., -.png, .jpg, .xpm, etc.). This directory is required by -`centos-art' command line interface. +

In this directory is where you store Gimp's project files (e.g, .xcf). +This directory is not required by `centos-art' command line +interface. If you can create a beautiful background images using +scalable vector graphics only, then there is no need to use the +`Xcf/' directory to store Gimp's background projects. Of course, +you can merge Gimp's power with Inkscape's power to produce images +based on them. In this last case you need the `Xcf/' directory.

@@ -104,14 +113,13 @@ ul.toc {list-style: none} - - +
[ < ] [ > ]   [ << ] [ Up ][ >> ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_32.html b/Manuals/en/Html/Repository/repository_32.html index 7283626..0bea18e 100644 --- a/Manuals/en/Html/Repository/repository_32.html +++ b/Manuals/en/Html/Repository/repository_32.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.29 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl +CentOS Artwork Repository: 3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress - - + + @@ -64,19 +64,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.29 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl

+

3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress

@@ -94,23 +94,60 @@ ul.toc {list-style: none}

3.29.3 Usage

-

In this directory is where you store all the scalable vector graphics -(e.g., .svg) files. This directory is required by `centos-art' -command line interface. +

To render Anaconda progress slide images using the Modern's artistic +motif design, the Default theme model, and available translation files +(see section trunk/Translations/Identity/Themes/Distro/Anaconda/Progress); +use the following commands:

+
 
cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/
+centos-art render --identity
+
+

The above command will create the following structure: +

+
 
trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
+|-- 3
+|   |-- en
+|   |   |-- 01-welcome.png
+|   |   |-- 02-donate.png
+|   |   `-- 03-yum.png
+|   `-- es
+|       |-- 01-welcome.png
+|       |-- 02-donate.png
+|       `-- 03-yum.png
+|-- 4
+|   |-- en
+|   |   |-- 01-welcome.png
+|   |   |-- 02-donate.png
+|   |   `-- 03-yum.png
+|   `-- es
+|       |-- 01-welcome.png
+|       |-- 02-donate.png
+|       `-- 03-yum.png
+`-- 5
+    |-- en
+    |   |-- 01-welcome.png
+    |   |-- 02-donate.png
+    |   `-- 03-yum.png
+    `-- es
+        |-- 01-welcome.png
+        |-- 02-donate.png
+        `-- 03-yum.png
+
+

3.29.4 See also

+ - +
[ < ] [ > ]   [ << ] [ Up ][ >> ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_33.html b/Manuals/en/Html/Repository/repository_33.html index 97c0ed8..5d63f2c 100644 --- a/Manuals/en/Html/Repository/repository_33.html +++ b/Manuals/en/Html/Repository/repository_33.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.30 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf +CentOS Artwork Repository: 3.30 trunk/Identity/Themes/Motifs/Modern/Palettes - - + + @@ -64,48 +64,40 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.30 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf

+

3.30 trunk/Identity/Themes/Motifs/Modern/Palettes

3.30.1 Goals

    -
  • ... +
  • Organize palette files for Modern theme.

3.30.2 Description

-
    -
  • ... -
- -

3.30.3 Usage

-

In this directory is where you store Gimp's project files (e.g, .xcf). -This directory is not required by `centos-art' command line -interface. If you can create a beautiful background images using -scalable vector graphics only, then there is no need to use the -`Xcf/' directory to store Gimp's background projects. Of course, -you can merge Gimp's power with Inkscape's power to produce images -based on them. In this last case you need the `Xcf/' directory. +

Here is where graphic designers define theme palettes for +color-limited art works. Theme palettes contain the color information +that rendering functions need, in order to produce images with color +limitations. Theme palettes contain theme's unique color information.

@@ -119,7 +111,7 @@ based on them. In this last case you need the `Xcf/' directory.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_34.html b/Manuals/en/Html/Repository/repository_34.html index 18c4475..80cde19 100644 --- a/Manuals/en/Html/Repository/repository_34.html +++ b/Manuals/en/Html/Repository/repository_34.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.31 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress +CentOS Artwork Repository: 3.31 trunk/Identity/Themes/Motifs/TreeFlower - - + + @@ -64,19 +64,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.31 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress

+

3.31 trunk/Identity/Themes/Motifs/TreeFlower

@@ -90,64 +90,25 @@ ul.toc {list-style: none}

3.31.2 Description

+

TreeFlower theme +

3.31.3 Usage

-

To render Anaconda progress slide images using the Modern's artistic -motif design, the Default theme model, and available translation files -(see section trunk/Translations/Identity/Themes/Distro/Anaconda/Progress); -use the following commands: -

-
 
cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/
-centos-art render --identity
-
-

The above command will create the following structure: -

-
 
trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
-|-- 3
-|   |-- en
-|   |   |-- 01-welcome.png
-|   |   |-- 02-donate.png
-|   |   `-- 03-yum.png
-|   `-- es
-|       |-- 01-welcome.png
-|       |-- 02-donate.png
-|       `-- 03-yum.png
-|-- 4
-|   |-- en
-|   |   |-- 01-welcome.png
-|   |   |-- 02-donate.png
-|   |   `-- 03-yum.png
-|   `-- es
-|       |-- 01-welcome.png
-|       |-- 02-donate.png
-|       `-- 03-yum.png
-`-- 5
-    |-- en
-    |   |-- 01-welcome.png
-    |   |-- 02-donate.png
-    |   `-- 03-yum.png
-    `-- es
-        |-- 01-welcome.png
-        |-- 02-donate.png
-        `-- 03-yum.png
-
-

3.31.4 See also

- - +
[ < ] [ > ]   [ << ] [ Up ][ >> ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_35.html b/Manuals/en/Html/Repository/repository_35.html index 9111405..c770039 100644 --- a/Manuals/en/Html/Repository/repository_35.html +++ b/Manuals/en/Html/Repository/repository_35.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.32 trunk/Identity/Themes/Motifs/Modern/Palettes +CentOS Artwork Repository: 3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds - - + + @@ -64,54 +64,360 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.32 trunk/Identity/Themes/Motifs/Modern/Palettes

+

3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds

3.32.1 Goals

-
    -
  • Organize palette files for Modern theme. -
- +

This section exists to orgnize TreeFlower's backgrounds. +

3.32.2 Description

-

3.32.3 Usage

+

3.32.2.1 Desktop background

-

Here is where graphic designers define theme palettes for -color-limited art works. Theme palettes contain the color information -that rendering functions need, in order to produce images with color -limitations. Theme palettes contain theme's unique color information. +

Once you have defined the vectorial artistic motif design, use the +centos-art.sh script (as described in usage section below) +to produce the png version of it. With the png version of your +vectorial design do the following: +

+

Open the png version with GIMP. +

+

Save the png version as gimp's project inside +`trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Xcf' +directory, using the same name of your vectorial design but with the +`.xcf' extension. +

+

Now use GIMP to improve your design. Here you may add one layer for +pattern, another for colors, and so on until you find yourself +confortable with your artwork. For example, the following layer +distribution (from bottom to top) was used to build revision 285 of +file `1360x768.xcf' using TreeFlower's artistic motif at revision +241. +

+
+
Layer 1: Background
+
+

The first thing we did with GIMP was to create a layer named +`Background' to store the artistic motif (File > Open as layer). +This layer is the lowest layer in the image. Later, we started to +create layers one upon another to change the artistic motif visual +style. +

+
+
Layer 2: Shadow#1
+
+

This layer is above `Background' and contains a linear gradient +from left (000000) to right (transparent) covering the whole image. +This layer masks the artistic motif to avoid the effect of linear +gradient. This layer is 100% of opacity. +

+
+
Layer 3: Shadow#2
+
+

This layer is above `Shadow#1' and contains a linear gradient +from left (000000) to right (transparent) covering just the 70% of the +whole image aproximatly. This layer doesn't mask the artistic motif +which make the left part of it fall into the dark of linear gradient. +This layer is 100% of opacity. +

+
+
Layer 4: Pattern (Paper)
+
+

This layer is above `Shadow#2' an contains the paper pattern +shipped with GIMP 2.2. This layer doesn't mask the artistic motif so +the pattern is applied over the whole image. This layer is set to 15% +of opacity. +

+
+
Layer 5: Pattern (Stripes)
+
+

This layer is above `Pattern (Paper)' and contains the stripes +used over the artistic motif. This layer do masks the artistic motif +so the stripes are only applied to it. This layer is set to 10% of +opacity. +

+
+
Layer 6: Shadow#3
+
+

This layer is above `Pattern (Stripes)' and contains a linear +gradient from right (6600ff) to left (transparent). This layer masks +the artistic motif so the linear gradient doesn't affect it. This +layer is set to 15% of opacity. +

+
+
Layer 7: Shadow#4
+
+

This layer is above `Shadow#3' and contains a +linear gradient from left (000000) to right (transparent). This layer +do masks the artistic motif so the linear gradient doesn't affect it. +This layer is set to 10% of opacity. +

+
+
Layer 8: Color#1
+
+

This layer is above `Shadow#4' and is filled with orange (ffae00) +color over the whole image. This layer is set to 10% of opacity. +

+
+
Layer 9: Color#2
+
+

This layer is above `Color#1' and is filled with +blue (010a88) color over the whole image. This layer is set to 10% of +opacity. +

+
+
+ +
info

Note

There is no definite combination. To get the appropriate +visual design is a matter of constant testing and personal taste. +

+ +

Finally, use the GIMP's `Save as copy ...' option to export the +final design. To export the final design use the same name of your +vectorial design plus `-final.png' extension. +

+

You can repeat these steps to create images for other screen +resolutions.

+

3.32.2.2 Anaconda Prompt (syslinux) background

+ +

When building syslinux backgrounds it is needed to take into account +that the final image is reduced to 16 colors. In desktop background +there is no color limitation but syslinux does have. The goal of this +section is achieving a final syslinux background as close as possible +to desktop backgrounds using 16 colors only. +

+

Another point to consider is the forground and background definition +used by syslinux. The syslinux documentation says that the color set +in position 0 is the background and color set in position 7 is the +forground. The final palette of color used by our background will +match that specification. For great contrast we'll use black as +background and white as forground. At this poing we have black +(000000) and white (ffffff) colors in our syslinux palette, which left +us with 14 colors to play with. +

+

Let's begin with `Xcf/640x300.xcf' layer distribution from bottom +to top: +

+
+
Layer 1: Background
+
+

This layer is the lowest layer in the image composition and contains +the artistic motif image rendered for the same resolution (i.e., +`Img/Png/640x300.png'). This layer is set to 100% of opacity. +

+
+
Layer 2: Pattern (Paper)
+
+

This layer is placed above `Background' layer and contains the +paper pattern shipped with GIMP 2.2. This layer doesn't mask the +artistic motif. This layer is set to 30% of opacity. +

+
+
Layer 3: Pattern (Stripes)
+
+

This layer is placed above `Pattern (Paper)' layer and contains +the stripes pattern shipped with GIMP 2.2. This layer does mask the +artistic motif in order to apply the stripes over it only. The +background is not affected by the stripes pattern just the artistic +motif. This layer is set to 20% of opacity. +

+
+
Layer 4: Shadow#1
+
+

This layer is placed above `Pattern (Stripes)' layer and fills +the entire layer area with violet (6600ff) color. This layer do mask +the artistic motif in order to applied the violet color to the +background area outside the artistic motif only. This layer is set to +15% of opacity. +

+
+
Layer 5: Color#1
+
+

This layer is above `Shadow#1' and is filled with orange (ffae00) +color to cover the whole image. This layer is set to 10% of opacity. +

+
+
Layer 6: Color#2
+
+

This layer is above `Color#1' and is filled with blue (010a88) +color to cover the whole image. This layer is set to 10% of opacity. +

+
+
Layer 7: Shadow#2
+
+

This layer is above `Color#1' and contains a linear gradient from +left (000000) to right (transparent) covering 70% of the image +approximately. +

+
+
+ +

At this point we have the composition and should look like the desktop +backgrounds. Compared with desktop backgrounds there are some +differences in opacity. This is because in our testings the final +color information found with this composition produces an acceptable +16 color image. Of course this is something we haven't seen yet. +

+

To define the color information of our current coposition, save the +syslinux GIMP's background composition we've done using GIMP's +`File > Save as Copy ...' option in the following location: +

+
trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Img/Png/640x300-final.png
+
+

Now, create the final png version of syslinux backgrounds using the +following command: +

+
centos-art render --entry=trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Prompt
+
+

This command will create syslinux-splash final images for all major +releases of CentOS distribution the repository has been configured to. +The important files here are `syslinux-splash.png', other +files may contain the wrong information because we haven't defined yet +the correct color information to use. +

+

Open one `syslinux-splash.png' file with GIMP and use the +`Image > Mode > Indexed' to reduce image colors up to 16 colors, +using GIMP's `Generate optimum palette' feature. If the image +looks aceptable after reducing colors, use GIMP's `Palettes' menu +(Ctrl+P) to import a new palette from file and name it +`CentOS-TreeFlower-Syslinux'. Once you've saved the palette, the +color information is stored at: +

+
~/.gimp-2.2/palettes/CentOS-TreeFlower-Syslinux.gpl
+
+

You need to edit `CentOS-TreeFlower-Syslinux.gpl' file in order +to set the appropriate order of colors. Remember black (000000) in +position 0, and white (ffffff) in position 7. Other positions are +irrelevant. When editing this file you may find that color reduction +did not set black and white colors to their respective values exactly. +Change that manually. For example, consider the following palette: +

+
GIMP Palette
+Name: CentOS-TreeFlower-Syslinux
+Columns: 16
+#
+  0   0   0	Background (black)
+ 23  20  35	Untitled
+ 34  25  48	Untitled
+ 37  35  60	Untitled
+ 47  36  68	Untitled
+ 37  54  86	Untitled
+ 60  48  90	Untitled
+255 255 255	Foreground (white)
+ 66  54  99	Untitled
+ 74  61  98	Untitled
+ 49  78 126	Untitled
+ 43  87 151	Untitled
+ 92  89  95	Untitled
+ 54 104 183	Untitled
+158 153 156	Untitled
+201 196 195	Untitled
+
+

Update the `Palettes' menu to get the new color positions from +the file you just edited and open the palette with double click. +

+

Update the `syslinux.gpl' file copying the following file: +

+
~/.gimp-2.2/palettes/CentOS-TreeFlower-Syslinux.gpl
+
+

to +

+
trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.gpl
+
+

With the `CentOS-TreeFlower-Syslinux' palette opened in the +`Palette Editor', open (Ctrl+O) the following file: +

+
trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.ppm
+
+

and replace its color information with that one in +`CentOS-TreeFlower-Syslinux' palette. When you are replacing +color information inside `syslilnux.ppm', remember to keep the +order of colors just as they are in the +`CentOS-TreeFlower-Palette' palette. +

+

The `syslinux.ppm' file is 16 pixels width and 1 pixel height, so +you probably need to zoom it a bit to set the color information in +their place when using the pen tool with the brush `Circle (01) +(1 x 1)'. +

+

Once you've updated the `syslinux.ppm' file, it is time to update +the following file: +

+
trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.hex
+
+

The `syslinux.hex' file contains the color information in +hexadecimal notation. The color information in hexadecimal notation +is required by ppmtolss16 command. The ppmtolss16 +command produces the final LSS16 image format that is used by syslinux +program inside CentOS distribution. +

+

The color information inside `syslinux.hex' must match the one in +`syslinux.ppm' and `syslinux.gpl'. For example, based on +`CentOS-TreeFlower-Syslinux' palette of colors above, consider +the following `syslinux.hex' file: +

+
#000000=0
+#171423=1
+#221930=2
+#25233c=3
+#2f2444=4
+#253656=5
+#3c305a=6
+#ffffff=7
+#423663=8
+#4a3d62=9
+#314e7e=10
+#2b5797=11
+#5c595f=12
+#3668b7=13
+#9e999c=14
+#c9c4c3=15
+
+ + +

3.32.2.3 Grub background

+ + + +

3.32.3 Usage

+ +
    +
  • ... +
+ + +

3.32.4 See also

- - + + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_36.html b/Manuals/en/Html/Repository/repository_36.html index c530ca3..b96652e 100644 --- a/Manuals/en/Html/Repository/repository_36.html +++ b/Manuals/en/Html/Repository/repository_36.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.33 trunk/Identity/Themes/Motifs/TreeFlower +CentOS Artwork Repository: 3.33 trunk/Identity/Widgets - - + + @@ -59,27 +59,27 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.33 trunk/Identity/Themes/Motifs/TreeFlower

+ + +

3.33 trunk/Identity/Widgets

- +

3.33.1 Goals

    @@ -87,28 +87,26 @@ ul.toc {list-style: none}
- +

3.33.2 Description

-

TreeFlower theme -

- +

3.33.3 Usage

- +

3.33.4 See also

- - + + - - + +
[ < ][ > ]
[ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_37.html b/Manuals/en/Html/Repository/repository_37.html index 77c7750..b0c534e 100644 --- a/Manuals/en/Html/Repository/repository_37.html +++ b/Manuals/en/Html/Repository/repository_37.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.34 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds +CentOS Artwork Repository: 3.34 trunk/Manuals - - + + @@ -59,352 +59,91 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.34 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds

+ + +

3.34 trunk/Manuals

- +

3.34.1 Goals

-

This section exists to orgnize TreeFlower's backgrounds. -

+
    +
  • ... +
+ - +

3.34.2 Description

+
    +
  • ... +
- -

3.34.2.1 Desktop background

-

Once you have defined the vectorial artistic motif design, use the -centos-art.sh script (as described in usage section below) -to produce the png version of it. With the png version of your -vectorial design do the following: -

-

Open the png version with GIMP. -

-

Save the png version as gimp's project inside -`trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Xcf' -directory, using the same name of your vectorial design but with the -`.xcf' extension. -

-

Now use GIMP to improve your design. Here you may add one layer for -pattern, another for colors, and so on until you find yourself -confortable with your artwork. For example, the following layer -distribution (from bottom to top) was used to build revision 285 of -file `1360x768.xcf' using TreeFlower's artistic motif at revision -241. -

+ +

3.34.3 Usage

+
-
Layer 1: Background
-
-

The first thing we did with GIMP was to create a layer named -`Background' to store the artistic motif (File > Open as layer). -This layer is the lowest layer in the image. Later, we started to -create layers one upon another to change the artistic motif visual -style. +

`centos-art help --read='path/to/dir''
+

Use this command to read directory documentation specified in +`path/to/dir'.

-
Layer 2: Shadow#1
-
-

This layer is above `Background' and contains a linear gradient -from left (000000) to right (transparent) covering the whole image. -This layer masks the artistic motif to avoid the effect of linear -gradient. This layer is 100% of opacity. +

`centos-art help --read='path/to/dir' --filter='filename''
+

Use this command to read file documentation as specified by +`path/to/dir/filename' combination.

-
Layer 3: Shadow#2
-
-

This layer is above `Shadow#1' and contains a linear gradient -from left (000000) to right (transparent) covering just the 70% of the -whole image aproximatly. This layer doesn't mask the artistic motif -which make the left part of it fall into the dark of linear gradient. -This layer is 100% of opacity. +

`centos-art help --edit='path/to/dir''
+

Use this command to edit directory documentation as specified in +`path/to/dir'.

-
Layer 4: Pattern (Paper)
-
-

This layer is above `Shadow#2' an contains the paper pattern -shipped with GIMP 2.2. This layer doesn't mask the artistic motif so -the pattern is applied over the whole image. This layer is set to 15% -of opacity. +

`centos-art help --edit='path/to/dir' --filter='filename''
+

Use this command to edit file documentation as specified in +`path/to/dir/filename' combination.

-
Layer 5: Pattern (Stripes)
-
-

This layer is above `Pattern (Paper)' and contains the stripes -used over the artistic motif. This layer do masks the artistic motif -so the stripes are only applied to it. This layer is set to 10% of -opacity. +

`centos-art help --update='path/to/dir''
+

Use this command to update documentation output files.

-
Layer 6: Shadow#3
-
-

This layer is above `Pattern (Stripes)' and contains a linear -gradient from right (6600ff) to left (transparent). This layer masks -the artistic motif so the linear gradient doesn't affect it. This -layer is set to 15% of opacity. +

`centos-art help --remove='path/to/dir''
+

Use this command to remove directory documentation as specified in +`path/to/dir'.

-
-
Layer 7: Shadow#4
-
-

This layer is above `Shadow#3' and contains a -linear gradient from left (000000) to right (transparent). This layer -do masks the artistic motif so the linear gradient doesn't affect it. -This layer is set to 10% of opacity. -

-
-
Layer 8: Color#1
-
-

This layer is above `Shadow#4' and is filled with orange (ffae00) -color over the whole image. This layer is set to 10% of opacity. -

-
-
Layer 9: Color#2
-
-

This layer is above `Color#1' and is filled with -blue (010a88) color over the whole image. This layer is set to 10% of -opacity. -

-
-
- -
info

Note

There is no definite combination. To get the appropriate -visual design is a matter of constant testing and personal taste. +

Caution

Caution

When directory documentation is removed all +documentation under it is also removed.

-

Finally, use the GIMP's `Save as copy ...' option to export the -final design. To export the final design use the same name of your -vectorial design plus `-final.png' extension. -

-

You can repeat these steps to create images for other screen -resolutions. -

- - -

3.34.2.2 Anaconda Prompt (syslinux) background

+
Info

Tip

To recover from directory documentation lost, try the +following command (before commit local changes up to central +repository): +

svn revert path/to/dir --recursive
+
-

When building syslinux backgrounds it is needed to take into account -that the final image is reduced to 16 colors. In desktop background -there is no color limitation but syslinux does have. The goal of this -section is achieving a final syslinux background as close as possible -to desktop backgrounds using 16 colors only. -

-

Another point to consider is the forground and background definition -used by syslinux. The syslinux documentation says that the color set -in position 0 is the background and color set in position 7 is the -forground. The final palette of color used by our background will -match that specification. For great contrast we'll use black as -background and white as forground. At this poing we have black -(000000) and white (ffffff) colors in our syslinux palette, which left -us with 14 colors to play with. -

-

Let's begin with `Xcf/640x300.xcf' layer distribution from bottom -to top: -

-
-
Layer 1: Background
-
-

This layer is the lowest layer in the image composition and contains -the artistic motif image rendered for the same resolution (i.e., -`Img/Png/640x300.png'). This layer is set to 100% of opacity. -

-
-
Layer 2: Pattern (Paper)
-
-

This layer is placed above `Background' layer and contains the -paper pattern shipped with GIMP 2.2. This layer doesn't mask the -artistic motif. This layer is set to 30% of opacity. -

-
-
Layer 3: Pattern (Stripes)
-
-

This layer is placed above `Pattern (Paper)' layer and contains -the stripes pattern shipped with GIMP 2.2. This layer does mask the -artistic motif in order to apply the stripes over it only. The -background is not affected by the stripes pattern just the artistic -motif. This layer is set to 20% of opacity. -

-
-
Layer 4: Shadow#1
-
-

This layer is placed above `Pattern (Stripes)' layer and fills -the entire layer area with violet (6600ff) color. This layer do mask -the artistic motif in order to applied the violet color to the -background area outside the artistic motif only. This layer is set to -15% of opacity. -

-
-
Layer 5: Color#1
-
-

This layer is above `Shadow#1' and is filled with orange (ffae00) -color to cover the whole image. This layer is set to 10% of opacity. -

-
-
Layer 6: Color#2
-
-

This layer is above `Color#1' and is filled with blue (010a88) -color to cover the whole image. This layer is set to 10% of opacity. -

-
-
Layer 7: Shadow#2
-
-

This layer is above `Color#1' and contains a linear gradient from -left (000000) to right (transparent) covering 70% of the image -approximately. -

+
`centos-art help --remove='path/to/dir' --filter='filename''
+

Use this command to remove file documentation as specified in +`path/to/dir/filename' combination. +

-

At this point we have the composition and should look like the desktop -backgrounds. Compared with desktop backgrounds there are some -differences in opacity. This is because in our testings the final -color information found with this composition produces an acceptable -16 color image. Of course this is something we haven't seen yet. -

-

To define the color information of our current coposition, save the -syslinux GIMP's background composition we've done using GIMP's -`File > Save as Copy ...' option in the following location: -

-
trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Img/Png/640x300-final.png
-
-

Now, create the final png version of syslinux backgrounds using the -following command: -

-
centos-art render --entry=trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Prompt
-
-

This command will create syslinux-splash final images for all major -releases of CentOS distribution the repository has been configured to. -The important files here are `syslinux-splash.png', other -files may contain the wrong information because we haven't defined yet -the correct color information to use. -

-

Open one `syslinux-splash.png' file with GIMP and use the -`Image > Mode > Indexed' to reduce image colors up to 16 colors, -using GIMP's `Generate optimum palette' feature. If the image -looks aceptable after reducing colors, use GIMP's `Palettes' menu -(Ctrl+P) to import a new palette from file and name it -`CentOS-TreeFlower-Syslinux'. Once you've saved the palette, the -color information is stored at: -

-
~/.gimp-2.2/palettes/CentOS-TreeFlower-Syslinux.gpl
-
-

You need to edit `CentOS-TreeFlower-Syslinux.gpl' file in order -to set the appropriate order of colors. Remember black (000000) in -position 0, and white (ffffff) in position 7. Other positions are -irrelevant. When editing this file you may find that color reduction -did not set black and white colors to their respective values exactly. -Change that manually. For example, consider the following palette: -

-
GIMP Palette
-Name: CentOS-TreeFlower-Syslinux
-Columns: 16
-#
-  0   0   0	Background (black)
- 23  20  35	Untitled
- 34  25  48	Untitled
- 37  35  60	Untitled
- 47  36  68	Untitled
- 37  54  86	Untitled
- 60  48  90	Untitled
-255 255 255	Foreground (white)
- 66  54  99	Untitled
- 74  61  98	Untitled
- 49  78 126	Untitled
- 43  87 151	Untitled
- 92  89  95	Untitled
- 54 104 183	Untitled
-158 153 156	Untitled
-201 196 195	Untitled
-
-

Update the `Palettes' menu to get the new color positions from -the file you just edited and open the palette with double click. -

-

Update the `syslinux.gpl' file copying the following file: -

-
~/.gimp-2.2/palettes/CentOS-TreeFlower-Syslinux.gpl
-
-

to -

-
trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.gpl
-
-

With the `CentOS-TreeFlower-Syslinux' palette opened in the -`Palette Editor', open (Ctrl+O) the following file: -

-
trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.ppm
-
-

and replace its color information with that one in -`CentOS-TreeFlower-Syslinux' palette. When you are replacing -color information inside `syslilnux.ppm', remember to keep the -order of colors just as they are in the -`CentOS-TreeFlower-Palette' palette. -

-

The `syslinux.ppm' file is 16 pixels width and 1 pixel height, so -you probably need to zoom it a bit to set the color information in -their place when using the pen tool with the brush `Circle (01) -(1 x 1)'. -

-

Once you've updated the `syslinux.ppm' file, it is time to update -the following file: -

-
trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.hex
-
-

The `syslinux.hex' file contains the color information in -hexadecimal notation. The color information in hexadecimal notation -is required by ppmtolss16 command. The ppmtolss16 -command produces the final LSS16 image format that is used by syslinux -program inside CentOS distribution. -

-

The color information inside `syslinux.hex' must match the one in -`syslinux.ppm' and `syslinux.gpl'. For example, based on -`CentOS-TreeFlower-Syslinux' palette of colors above, consider -the following `syslinux.hex' file: -

-
#000000=0
-#171423=1
-#221930=2
-#25233c=3
-#2f2444=4
-#253656=5
-#3c305a=6
-#ffffff=7
-#423663=8
-#4a3d62=9
-#314e7e=10
-#2b5797=11
-#5c595f=12
-#3668b7=13
-#9e999c=14
-#c9c4c3=15
-
- - -

3.34.2.3 Grub background

- - - -

3.34.3 Usage

- -
    -
  • ... -
-

3.34.4 See also

@@ -416,8 +155,8 @@ the following `syslinux.hex' file: [ > ]   [ << ] -[ Up ] -[ >> ] +[ Up ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_38.html b/Manuals/en/Html/Repository/repository_38.html index 75ccbf7..16013a5 100644 --- a/Manuals/en/Html/Repository/repository_38.html +++ b/Manuals/en/Html/Repository/repository_38.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.35 trunk/Identity/Widgets +CentOS Artwork Repository: 3.35 trunk/Scripts - - + + @@ -64,36 +64,47 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.35 trunk/Identity/Widgets

+

3.35 trunk/Scripts

3.35.1 Goals

+

The `trunk/Scripts' directory exists to: +

    -
  • ... +
  • Organize the "trunk" development line of automation scripts by +programming language.

3.35.2 Description

+
    +
  • ... +
+

3.35.3 Usage

+
    +
  • ... +
+

3.35.4 See also

@@ -106,7 +117,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_39.html b/Manuals/en/Html/Repository/repository_39.html index 7addd95..a7c70eb 100644 --- a/Manuals/en/Html/Repository/repository_39.html +++ b/Manuals/en/Html/Repository/repository_39.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.36 trunk/Manuals +CentOS Artwork Repository: 3.36 trunk/Scripts/Bash - - + + @@ -64,90 +64,142 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.36 trunk/Manuals

+

3.36 trunk/Scripts/Bash

3.36.1 Goals

-
    -
  • ... -
- +

The `trunk/Scripts/Bash' directory exists to organize the trunk +development line of `centos-art.sh' automation script. The +`centos-art.sh' script standardizes frequent tasks inside your +working copy of CentOS Artwork Repository. +

3.36.2 Description

-
    -
  • ... -
- - - -

3.36.3 Usage

- -
-
`centos-art help --read='path/to/dir''
-

Use this command to read directory documentation specified in -`path/to/dir'. +

The best way to understand `centos-art.sh' automation script is +studying its source code. The `centos-art.sh' script is splited +in several configuration and function files which are loaded when the +`centos-art.sh' script is executed. This section describes the +order in which `centos-art.sh' loads its configuration and +function files.

-
-
`centos-art help --read='path/to/dir' --filter='filename''
-

Use this command to read file documentation as specified by -`path/to/dir/filename' combination. +

When you type the centos-art command in your terminal, the +operating system trys to execute that command. In order to execute the +command, the operating system needs to know where it is, so the +operating system uses the PATH environment variable to look for +that command's location. If your system was prepared to use CentOS +Artwork Repository correctly (see section trunk/Scripts/Bash/Functions/Verify), you should have a symbolic link inside `~/bin/' +directory that points to the `centos-art.sh' script file. As +`~/bin/' directory is, by default, inside PATH environment +variable, the execution of centos-art command runs the +`centos-art.sh' script.

-
-
`centos-art help --edit='path/to/dir''
-

Use this command to edit directory documentation as specified in -`path/to/dir'. +

When `centos-art.sh' script is executed, the first it does is +executing the `trunk/Scripts/Bash/initFunctions.sh' script to +initialize global variables (e.g., gettext's variables) and +global function scripts. Global function scripts are located inside +`trunk/Scripts/Bash/Functions' directory and their file names +begin with `cli'. Global function scripts provide common +functionalities that can be used anywhere inside `centos-art.sh' +script execution environment.

-
-
`centos-art help --edit='path/to/dir' --filter='filename''
-

Use this command to edit file documentation as specified in -`path/to/dir/filename' combination. +

Once global variables and function scripts have been loaded, +`centos-art.sh' script executes the cli global function +from `cli.sh' function script to retrive command-line arguments +and define some default values that may be used later by specific +function scripts (see section trunk/Scripts/Bash/Functions).

-
-
`centos-art help --update='path/to/dir''
-

Use this command to update documentation output files. +

As convenction, the `centos-art.sh' command-line arguments have +the following format:

-
-
`centos-art help --remove='path/to/dir''
-

Use this command to remove directory documentation as specified in -`path/to/dir'. +

centos-art arg1 --arg2=val2 --arg3=val3
+
+

In the above example, `centos-art' is the command you use to +invoke `centos-art.sh' script. The `arg1' represents the +action you want to do (e.g., `verify', `render', +`locale', `help', etc.). The remaining arguments are +modifiers to `arg1'. The `--arg2' definition is +required. The `--arg3' is optional. For example, if you want +to render all anaconda progress slides, for all major releases of +CentOS distribution, for all languages availabe using TreeFlower motif +as background, you use the following command: +

+
centos-art render --entry=trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Progress
+
+

Now, if you only want to render anaconda progress +`01-welcome.png' slide, for CentOS distribution major release 5, +in English language, you need to add the third argument as follows: +

+
centos-art render --entry=trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Progress --filter=5/en/01-welcome
+
+

Once command-line arguments have been retrived, the +`centos-art.sh' script loads specific functions using the +`cli_getActions.sh' function script. For example, if you run the +command centos-art render --entry, the `centos-art.sh' +script will look for `trunk/Scripts/Bash/Functions/Render' +directory and will load the render function from +`render.sh' function script; this, in order to achive the +rendering task as it defines. +

+
+
+------------------------------------------------------------------+
+| [centos@host]$ centos-art action 'path/to/dir' --option='value'  |
++------------------------------------------------------------------+
+| ~/bin/centos-art --> ~/artwork/trunk/Scripts/Bash/centos-art.sh  |
++---v-----------------------------------------v--------------------+
+    | centos-art.sh                           |
+    +---v---------------------------------v---+
+    .   | initFunctions.sh                |   .
+    .   +---------------------------------+   .
+    .   | cli $@                          |   .
+    .   +---v-------------------------v---+   .
+    .   .   | cli_getActions $@       |   .   .
+    .   .   +---v-----------------v---+   .   .
+    .   .   .   | function call 1 |   .   .   .
+    .   .   .   | function call 2 |   .   .   .
+    .   .   .   | function call n |   .   .   .
+    .   .   .   +-----------------+   .   .   .
+    .   .   ...........................   .   .
+    .   ...................................   .
+    ...........................................
+
+

Figure 3.8: The `centos-art.sh' initialization environment. +

-
Caution

Caution

When directory documentation is removed all -documentation under it is also removed. -

- -
Info

Tip

To recover from directory documentation lost, try the -following command (before commit local changes up to central -repository): -

svn revert path/to/dir --recursive
-
-
-
`centos-art help --remove='path/to/dir' --filter='filename''
-

Use this command to remove file documentation as specified in -`path/to/dir/filename' combination. -

-
+ +

3.36.3 Usage

+

The `centos-art.sh' script usage information is described inside +each specific function documentation (see section trunk/Scripts/Bash/Functions). +

3.36.4 See also

+ + + + +
3.35 trunk/Scripts   +
3.37 trunk/Scripts/Bash/Functions   +
3.47 trunk/Scripts/Bash/Locale   +
@@ -156,7 +208,7 @@ repository): - +
  [ << ] [ Up ][ >> ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_4.html b/Manuals/en/Html/Repository/repository_4.html index 44671d7..8accf12 100644 --- a/Manuals/en/Html/Repository/repository_4.html +++ b/Manuals/en/Html/Repository/repository_4.html @@ -64,14 +64,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -501,7 +501,7 @@ may be created using the renderFormats post-rendering action, inside the image-based related pre-rendering configuration script.

-

See section trunk/Scripts/Bash, for more information. +

See section trunk/Scripts/Bash, for more information.

@@ -509,7 +509,7 @@ script.

3.1.6 See also

-
3.52 trunk/Translations   +
3.50 trunk/Translations  
@@ -530,7 +530,7 @@ links).   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_40.html b/Manuals/en/Html/Repository/repository_40.html index 6517ef4..b9e5c5c 100644 --- a/Manuals/en/Html/Repository/repository_40.html +++ b/Manuals/en/Html/Repository/repository_40.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.37 trunk/Scripts +CentOS Artwork Repository: 3.37 trunk/Scripts/Bash/Functions - - + + @@ -64,60 +64,1026 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.37 trunk/Scripts

+

3.37 trunk/Scripts/Bash/Functions

3.37.1 Goals

-

The `trunk/Scripts' directory exists to: +

The `trunk/Scripts/Bash/Functions' directory exists to organize +`centos-art.sh' specific functionalities.

-
    -
  • Organize the "trunk" development line of automation scripts by -programming language. -
-

3.37.2 Description

-
    -
  • ... -
+

The specific functions of `centos-art.sh' script are designed +with "Software Toolbox" philosophy (see (coreutils.info)Toolbox introduction) in mind: each program "should do one +thing well". Inside `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 `centos-art.sh' script are organized +inside specific directories under `trunk/Scripts/Bash/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 render, the specific function +directory for it would be `trunk/Scripts/Bash/Functions/Render'. +

+

To better understand how specific functions of `centos-art.sh' +script are designed, lets create one function which only goal is to +output different kind of greetings to your screen. +

+

When we create specific functions for `centos-art.sh' script it +is crucial to know what these functions will do exactly and if there +is any function that already does what we intend to do. If there is no +one, it is good time to create them then. Otherwise, if +functionalities already available don't do what you exactly expect, +contact their authors and work together to improve them. +

+
Info

Tip

Join CentOS developers mailing list +centos-art@centos.org to share your ideas. +

+ +

It is also worth to know what global functions and variables do we +have available inside `centos-art.sh' script, so advantage can be +taken from them. Global variables are defined inside global function +scripts. Global functions scripts are stored immediatly under +`trunk/Scripts/Bash/Functions' directory, in files begining with +`cli' prefix. +

+

OK, let's begin with our functionality example. +

+

What function name do we use? Well, lets use greet. Note that +`hello' word is not a verb; but an expression, a kind of +greeting, an interjection specifically. In contrast, `greet' is a +verb and describes what we do when we say `Hello!', `Hi!', +and similar expressions. +

+

So far, we've gathered the following function information: +

+
Name: greet
+Path: trunk/Scripts/Bash/Functions/Greet
+File: trunk/Scripts/Bash/Functions/Greet/greet.sh
+
+

The `greet.sh' function script is the first file +`centos-art.sh' script loads when the `greet' functionality +is called using commands like `centos-art greet --hello='World''. +The `greet.sh' function script contains the greet function +definition. +

+

Inside `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. +

+

Inside `centos-art.sh' script functions, top commentaries have +the following components: the functionality description, one-line for +copyright note with your personal information, the license under +which the function source code is released --the `centos-art.sh' +script is released as GPL, so do all its functions--, subversion's +$Id$ keyword which is later expanded by svn propset +command. +

+

In our greet function example, top commentary for +`greet.sh' function script would look like the following: +

+
#!/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., 59 Temple Place, Suite 330, Boston, MA 02111-1307
+# USA.
+# 
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+

After top commentary, separated by one blank line, the greet +function definition would look like the following: +

+
function greet {
+
+    # Define global variables.
+
+    # Define command-line interface.
+    greet_getActions
+
+}
+
+

The first definition inside greet function, are global +variables that will be available along greet function execution +environment. This time we didn't use global variable definitions for +greet function execution environment, so we left that section +empty. +

+

Later, we call greet_getActions function to define the +command-line interface of greet functionality. The greet +functionality command-line interface defines what and how actions are +performed, based on arguments combination passed to +`centos-art.sh' script. +

+
function greet_getActions {
+
+    case "$ACTIONNAM" in
+
+        --hello )
+            greet_doHello
+            ;;
+
+        --bye )
+            greet_doBye
+            ;;
+
+        * )
+            cli_printMessage "`gettext "The option provided is not valid."`"
+            cli_printMessage "$(caller)" 'AsToKnowMoreLine'
+
+    esac
+
+}
+
+

The ACTIONNAM global variable is defined in `cli.sh' +function script and contains the value passed before the equal sign +(i.e., `=') in the second command-line argument of +`centos-art.sh' script. For example, if the second command-line +argument is `--hello='World'', the value of ACTIONNAM +variable would be `--hello'. Using this configuration let us +deside which action to perform based on the action name passed to +`centos-art.sh' script as second argument. +

+

The greet function definition makes available two valid +greetings through `--hello' and `--bye' options. If no +one of them is provided as second command-line argument, the `*' +case is evaluated instead. +

+

The `*' case and its two further lines should always be present +in `_getActions.sh' function scripts, no matter what specific +functionality you are creating. This convenction helps the user to +find out documentation about current functionality in use. +

+

The greet_doHello and greet_doBye function definitions +are the core of greet specific functionality. In such function +definitions we set what our greet function really does: to +output different kinds of greetings. +

+
function greet_doHello {
+
+    cli_printMessage "`gettext "Hello"` $ACTIONVAL"
+
+}
+
+

The greet_doHello function definition is stored in +`greet_doHello.sh' function script. +

+
function greet_doBye {
+
+    cli_printMessage "`gettext "Goodbye"` $ACTIONVAL"
+
+}
+
+

The greet_doBye function definition is stored in the +`greet_doBye.sh' function script. +

+

Both `greet_doHello.sh' and `greet_doBye.sh' function +scripts are stored inside greet's function directory path (i.e. +`trunk/Scripts/Bash/Functions/Greet'). +

+

The ACTIONVAL global variable is defined in `cli.sh' +function script and contains the value passed after the equal sign +(i.e., `=') in the second command-line argument of +`centos-art.sh' script. For example, if the second command-line +argument is `--hello='World'', the value of ACTIONVAL +variable would be `World' without quotes. +

+

Let's see how greet specific functionality files are organzied +under greet's function directory. To see file organization we +use the tree command: +

+
trunk/Scripts/Bash/Functions/Greet
+|-- greet_doBye.sh
+|-- greet_doHello.sh
+|-- greet_getActions.sh
+`-- greet.sh
+
+

To try the greet specific functionality we've just created, +pass the function name (i.e., `greet') as first argument to +`centos-art.sh' script, and any of the valid options as second +argument. Some examples are illustrated below: +

+
[centos@projects ~]$ centos-art greet --hello='World'
+Hello World
+[centos@projects ~]$ centos-art greet --bye='World'
+Goodbye World
+[centos@projects ~]$ 
+
+

The word `World' in the examples above can be anything. In fact, +change it to have a little fun. +

+

Now that we have a specific function that works as we expect, it is +time to document it. To document greet specific functionality, +we use its directory path and the help functionality +(see section trunk/Scripts/Bash/Functions/Help) of `centos-art.sh' +script, just as the following command illustrates: +

+
centos-art help --edit=trunk/Scripts/Bash/Functions/Greet
+
+

Now that we have documented our function, it is time to translate its +output messages to different languages. To translate specific +functionality output messages to different languages we use the +locale functionality (see section trunk/Scripts/Bash/Functions/Locale) of `centos-art.sh' script, just as the following command +illustrates: +

+
centos-art locale --edit
+
+
Warning

Warning

To translate output messages in different languages, +your system locale information --as in 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 +`es_ES.UTF-8' or similar. +

+

Well, it seems that our example is rather complete by now. +

+

In greet function example we've described so far, we only use +cli_printMessage global function in action specific function +definitions in order to print a message simply, but more interesting +things can be achieved inside action specific function definitions. +For example, if you pass a directory path as second argument option +value, you could 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, you could add the third argument in the form +`--filter='regex'' and reduce the amount of files to process +using a regular expression pattern. +

+

The greet function described in this section may serve you as +an introduction to understand how specific functionalities work inside +`centos-art.sh' script. With some of luck this introduction will +also serve you as motivation to create your own `centos-art.sh' +script specific functionalities. +

+

By the way, the greet functionality doesn't exist inside +`centos-art.sh' script yet. Would you like to create it? +

3.37.3 Usage

+ + +

3.37.3.1 Global variables

+ +

The following global variables of `centos-art.sh' script, are +available for you to use inside specific functions: +

+
+
Variable: TEXTDOMAIN + +
+

Default domain used to retrieve translated messages. This value is set +in `initFunctions.sh' and shouldn't be changed. +

+ +
+
Variable: TEXTDOMAINDIR + +
+

Default directory used to retrieve translated messages. This value is +set in `initFunctions.sh' and shouldn't be changed. +

+ +
+
Variable: FUNCNAM + +
+

Define function name. +

+

Function names associate sets of actions. There is one set of actions +for each unique function name inside `centos-art.sh' script. +

+

Dunction names are passed as first argument in `centos-art.sh' +command-line interface. For example, in the command `centos-art +render --entry=path/to/dir --filter=regex', the ACTION passed to +`centos-art.sh' script is `render'. +

+

When first argument is not provided, the `centos-art.sh' script +immediatly ends its execution. +

+ +
+
Variable: ACTIONNAM + +
+

Define action name. +

+

Each action name identifies an specific action to perform, inside an +specific function. +

+

Action name names aare passed as second argument in +`centos-art.sh' command-line interface. For example, in the +command `centos-art render --entry=path/to/dir --filter=regex', +the ACTIONNAM passed to `centos-art.sh' script is +`--entry'. +

+

When second argument is not provided, the `centos-art.sh' script +immediatly ends its execution. +

+ +
+
Variable: ACTIONVAL + +
+

Define action value. +

+

Action values are associated to just one action name. Action values +contain the repository entry over which its associated action will be +performed in. Repository entries can be directories, files, or URLs +refering the repository structure. +

+

When action value is not specified as repository entry, the +`centos-art.sh' script evaluates the current directory it was +executed from. If such directory is under the repository structure +(i.e., `/home/centos/artwork/'), the `centos-art.sh' script +uses that directory as value to ACTIONVAL variable. Otherwise, +if outside the repository structure, the `centos-art.sh' script +prints the message `The path provided can't be processed.' and, +after it, immediatly ends script execution. +

+

Default action value is passed as second argument in +`centos-art.sh' command-line interface. For example, in the +command `centos-art render --entry=path/to/dir --filter=regex', +the ACTIONVAL passed to `centos-art.sh' script is +`path/to/dir'. +

+ +
+
Variable: REGEX + +
+

Define regular expression used as pattern to build the list of files +to process. +

+

By default, REGEX variable is set to .+ to match all +files. +

+

Functions that need to build a list of files to process use the option +`--filter' to redefine REGEX variable default value, and +so, control the amount of files to process. +

+ +
+
Variable: ARGUMENTS + +
+

Define optional arguments. +

+

Optional arguments, inside `centos-art.sh' script, are considered +as all command-line arguments passed to `centos-art.sh' script, +from third argument position on. For example, in the command +`centos-art render --entry=path/to/dir --filter=regex' , the +optional arguments are from `--filter=regex' argument on. +

+

Optional arguments are parsed using getopt command through +the following base construction: +

+
# Define short options we want to support.
+local ARGSS=""
+
+# Define long options we want to support.
+local ARGSL="filter:,to:"
+
+# Parse arguments using getopt(1) command parser.
+cli_doParseArguments
+
+# Reset positional parameters using output from (getopt) argument
+# parser.
+eval set -- "$ARGUMENTS"
+
+# Define action to take for each option passed.
+while true; do
+    case "$1" in
+        --filter )
+            REGEX="$2" 
+            shift 2
+            ;;
+        --to )
+            TARGET="$2" 
+            shift 2
+            ;;
+        * )
+            break
+    esac
+done
+
+

Optional arguments provide support to command options inside +`centos-art.sh' script. For instance, consider the Subversion +(svn) command, where there are many options (e.g., +`copy', `delete', `move', etc), and inside each +option there are several modifiers (e.g., `--revision', +`--message', `--username', etc.) that can be combined one +another in their short or long variants. +

+

The ARGUMENTS variable is used to store arguments passed from +command-line for later use inside `centos-art.sh' script. Storing +arguments is specially useful when we want to run a command with some +specific options from them. Consider the following command: +

+
centos-art path --copy=SOURCE --to=TARGET --message="The commit message goes here." --username='johndoe'
+
+

In the above command, the `--message', and `--username' +options are specific to svn copy command. In such cases, +options are not interpreted by `centos-art.sh' script itself. +Instead, the `centos-art.sh' script uses getopt to +retrive them and stores them in the ARGUMENT variable for later +use, as described in the following command: +

+
# Build subversion command to duplicate locations inside the
+# workstation.
+eval svn copy $SOURCE $TARGET --quiet $ARGUMENTS
+
+

When getopt parses ARGUMENTS, we may use short options +(e.g., `-m') or long options (e.g., `--message'). When +we use short options, arguments are separated by one space from the +option (e.g., `-m 'This is a commit message.''). When we use +long options arguments are separated by an equal sign (`=') +(e.g., `--message='This is a commit message''). +

+

In order for getopt to parse ARGUMENTS correctly, it +is required to provide the short and long definition of options that +will be passed or at least supported by the command performing the +final action the function script exists for. +

+

As convenction, inside `centos-art.sh' script, short option +definitions are set in the ARGSS variable; and long option +definitions are set in the ARGSL variable. +

+

When you define short and long options, it may be needed to define +which of these option arguments are required and which not. To define +an option argument as required, you need to set one colon `:' +after the option definition (e.g., `-o m: -l message:'). On +the other hand, to define an option argument as not required, you need +to set two colons `::' after the option definition (e.g., +`-o m:: -l message::'). +

+ +
+
Variable: EDITOR + +
+

Default text editor. +

+

The `centos-art.sh' script uses default text EDITOR to edit +pre-commit subversion messages, translation files, configuration +files, script files, and similar text-based files. +

+

If EDITOR environment variable is not set, `centos-art.sh' +script uses `/usr/bin/vim' as default text editor. Otherwise, the +following values are recognized by `centos-art.sh' script: +

    -
  • ... +
  • `/usr/bin/vim' +
  • `/usr/bin/emacs' +
  • `/usr/bin/nano'
+

If no one of these values is set in EDITOR environment variable, +`centos-art.sh' uses `/usr/bin/vim' text editor by default. +

- + + +

3.37.3.2 Global functions

+ +

The following global functions of `centos-art.sh' script are +available for you to use inside specific functions: +

+
+
Function: cli_commitRepoChanges [LOCATION] + +
+

Syncronize changes between repository and working copy. +

+

The cli_commitRepoChanges function uses the value of +LOCATION argument as reference to perform change verification +inside the working copy using subversion commands. If LOCATION +argument is not specified as cli_commitRepoChanges first +argument, the ACTIONVAL variable is used as reference instead. +

+

The cli_commitRepoChanges function brings changes from the +repository to the working copy--using svn update--, checks +the working copy changes--using svn status command--, +prints status report--using both svn update and +svn status commands output, and finally, commits recent +changes from the working copy up to the repository--using +svn commit command--. +

+

Previous to commit the working copy changes up to the repository, the +cli_commitRepoChanges function asks you to verify +changes--using svn diff command--, and later, another +confirmation question is shown to be sure you really want to commit +changes up to central repository. +

+
+
----------------------------------------------------------------------
+--> Bringing changes from the repository into the working copy
+--> Checking changes in the working copy
+----------------------------------------------------------------------
+Added           0 file from the repository.
+Deleted         0 file from the repository.
+Updated         0 file from the repository.
+Conflicted      0 file from the repository.
+Merged          0 file from the repository.
+Modified        4 files from the working copy.
+Unversioned     0 file from the working copy.
+Deleted         0 file from the working copy.
+Added           0 file from the working copy.
+----------------------------------------------------------------------
+
+

Figure 3.9: The cli_commitRepoChanges function output. + +

+

Call the cli_commitRepoChanges function before or/and after +functions that modify files or directories inside the working copy as +you may need to. +

+ +
+
Function: cli_checkFiles FILE [TYPE] + +
+

Verify files existence. +

+

cli_checkFiles receives a FILE absolute path and performs +file verification as specified in TYPE. When TYPE is not +specified, cli_checkFiles verifies FILE existence, no +matter what kind of file it be. If TYPE is specified, use one +of the following values: +

+
+
`d'
+
`directory'
+

Ends script execution if FILE is not a directory. +

+

When you verify directories with cli_checkFiles, if directory doesn't +exist, `centos-art.sh' script asks you for confirmation in order +to create that directory. If you answer positively, +`centos-art.sh' script creates that directory and continues +script flows normally. Otherwise, if you answer negatively, +`centos-art.sh' ends script execution with an error and +documentation message. +

+
+
`f'
+
`regular-file'
+

Ends script execution if FILE is not a regular file. +

+
`h'
+
`symbolic-link'
+

Ends script execution if FILE is not a symbolic link. +

+
`x'
+
`execution'
+

Ends script execution if FILE is not executable. +

+
`fh'
+

Ends script execution if FILE is neither a regular file or a +symbolic link. +

+
+ +

As default behaviour, if FILE passes all verifications, +`centos-art.sh' script continues with its normal flow. +

+ +
+
Function: cli_getCountryCodes [FILTER] + +
+

Output country codes. +

+

The cli_getCountryCodes function outputs a list with country +codes as defined in ISO3166 standard. When FILTER is provided, +cli_getCountryCodes outputs country codes that match +FILTER regular expression pattern. +

+ +
+
Function: cli_getCountryName [FILTER] + +
+

Output country names. +

+

The cli_getCountryName function reads one language locale code +in the format LL_CC and outputs the name of its related country as in +ISO3166. If filter is specified, cli_getCountryName returns the +country name that matches the locale code specified in FILTER, +exactly. +

+

The cli_getCountryName function outputs country name supported +by `centos-art.sh' script. +

+ +
+
Function: cli_getCurrentLocale + +
+

Output current locale used by `centos-art.sh' script. +

+

The cli_getCurrentLocale function uses LANG environment +variable to build a locale pattern that is later applied to +cli_getLocales function output in order to return the current +locale that `centos-art.sh' script works with. +

+

The current locale information, returned by +cli_getCurrentLocale, is output from more specific to less +specific. For example, if `en_GB' locale exists in +cli_getLocales function output, the `en_GB' locale would +take precedence before `en' locale. +

+

Locale precedence selection is quite important in order to define the +locale type we use for message translations. For example, if +`en_GB' is used, we are also saying that no common language +specification is used for English language (i.e., `en'). Instead, +we are using English non-common country-specific language +specifications like `en_AU', `en_BW', `en_GB', +`en_US', etc., for message translations. +

+

Use cli_getCurrentLocale function to know what current locale +information to use inside `centos-art.sh' script. +

+

The cli_getCurrentLocale function outputs current locale used +by `centos-art.sh' script. +

+ +
+
Function: cli_getLangCodes [FILTER] + +
+

Output language codes. +

+

cli_getLangCodes function outputs a list of language codes as +defined in ISO639 standard. When FILTER is provided, +cli_getLangCodes outputs language codes that match FILTER +regular expression pattern. +

+

The cli_getLangCodes function outputs language codes supported +by `centos-art.sh' script. +

+ +
+
Function: cli_getLangName [FILTER] + +
+

Output language names. +

+

cli_getLangName function reads one language locale code in the +format LL_CC and outputs the language related name as in ISO639. If +filter is specified, cli_getLangName returns the language name +that matches the locale code specified in FILTER, exactly. +

+

The cli_getLangName function outputs language names supported +by `centos-art.sh' script. +

+ +
+
Function: cli_getLocales + +
+

Output locale codes supported by `centos-art.sh' script. +

+

Occasionally, you use cli_getLocales function to add locale +information in non-common country-specific language (`LL_CC') +format for those languages (e.g., `bn_IN', `pt_BR', etc.) +which locale differences cannot be solved using common language +specifications (`LL') into one unique common locale specification +(e.g., `bn', `pt', etc.). +

+ +
+
Function: cli_getRepoName NAME TYPE + +
+

Sanitate file names. +

+

Inside `centos-art.sh' script, specific functionalities rely both +in cli_getRepoName and repository file system organization to +achieve their goals. Consider cli_getRepoName function as +central place to manage file name convenctions for other functions +inside `centos-art.sh' script. +

+
Important

Important

cli_getRepoName function doesn't verify file +or directory existence, for that purpose use cli_checkFiles +function instead. +

+ +

The NAME variable contains the file name or directory name you +want to sanitate. +

+

The TYPE variable can be one of the following values: +

+
`d'
+
`directory'
+

Sanitate directory NAMEs. +

+
`f'
+
`regular-file'
+

Sanitate regular file NAMEs. +

+
+ +

Use cli_getRepoName function to sanitate file names and +directory names before their utilization. +

+

Use cli_getRepoName when you need to change file name +convenctions inside `centos-art.sh' script. +

+

When changing file name convenctions inside cli_getRepoName +what you are really changing is the way functions interpret repository +file system organization. In order to a complete file name convenction +change, you also need to change file names and directory names inside +repository file system organization, just as you did in +cli_getRepoName function. +

+
info

Note

See section trunk/Scripts/Bash/Functions/Path, for more +information on how to rename files and directories massively inside +repository file system organization. +

+
+ +
+
Function: cli_getTemporalFile NAME + +
+

Output absolute path to temporal file NAME. +

+

cli_getTemporalFile uses `/tmp' directory as source +location to store temporal files, the `centos-art.sh' script +name, and a random identification string to let you run more than one +`centos-art.sh' script simultaneously on the same user session. +For example, due the following temporal file defintion: +

+
cli_getTemporalFile $FILE
+
+

If FILE name is `instance.svg' and unique random string is +`f16f7b51-ac12-4b7f-9e66-72df847f12de', the final temporal file, +built from previous temporal file definition, would be: +

+
/tmp/centos-art.sh-f16f7b51-ac12-4b7f-9e66-72df847f12de-instance.svg
+
+

When you use cli_getTemporalFile function to create temporal +files, be sure to remove temporal files created once you've ended up +with them. For example, consider the following construction: +

+
for FILE in $FILES;do
+
+    # Initialize temporal instance of file.
+    INSTANCE=$(cli_getTemporalFile $FILE)
+
+    # Do something ... 
+
+    # Remove temporal instance of file.
+    if [[ -f $INSTANCE ]];then
+        rm $INSTANCE
+    fi
+
+done
+
+

Use cli_getTemporalFile function whenever you need to create +temporal files inside `centos-art.sh' script. +

+ +
+
Function: cli_getThemeName + +
+

Output theme name. +

+

In order for cli_getThemeName function to extract theme name +correctly, the ACTIONVAL variable must contain a directory path +under `trunk/Identity/Themes/Motifs/' directory structure. +Otherwise, cli_getThemeName returns an empty string. +

+ +
+
Function: cli_printMessage MESSAGE [FORMAT] + +
+

Give format to output messages. +

+

When FORMAT is not specified, cli_printMessage outputs +information just as it was passed in MESSAGE variable. +Otherwise, FORMAT can take one of the following values: +

+
+
`AsHeadingLine'
+

To print heading messages. +

----------------------------------------------------------------------
+$MESSAGE
+----------------------------------------------------------------------
+
+
+
`AsWarningLine'
+

To print warning messages. +

----------------------------------------------------------------------
+WARNING: $MESSAGE
+----------------------------------------------------------------------
+
+
+
`AsNoteLine'
+

To print note messages. +

----------------------------------------------------------------------
+NOTE: $MESSAGE
+----------------------------------------------------------------------
+
+
+
`AsUpdatingLine'
+

To print `Updating' messages using two-columns format. +

Updating        $MESSAGE
+
+
+
`AsRemovingLine'
+

To print `Removing' messages using two-columns format. +

Removing        $MESSAGE
+
+
+
`AsCheckingLine'
+

To print `Checking' messages using two-columns format. +

Checking        $MESSAGE
+
+
+
`AsCreatingLine'
+

To print `Creating' messages using two-columns format. +

Creating        $MESSAGE
+
+
+
`AsSavedAsLine'
+

To print `Saved as' messages using two-columns format. +

Saved as        $MESSAGE
+
+
+
`AsLinkToLine'
+

To print `Linked to' messages using two-columns format. +

Linked to       $MESSAGE
+
+
+
`AsMovedToLine'
+

To print `Moved to' messages using two-columns format. +

Moved to        $MESSAGE
+
+
+
`AsTranslationLine'
+

To print `Translation' messages using two-columns format. +

Translation     $MESSAGE
+
+
+
`AsConfigurationLine'
+

To print `Configuration' messages using two-columns format. +

Configuration   $MESSAGE
+
+
+
`AsResponseLine'
+

To print response messages using one-column format. +

--> $MESSAGE
+
+
+
`AsRequestLine'
+

To print request messages using one-column format. Request messages +supress the trailing newline character from final output. +

$MESSAGE
+
+
+
`AsYesOrNoRequestLine'
+

To print `yes or no' request messages using one-column format. If +something different from `y' is answered (when using +en_US.UTF-8 locale), script execution ends immediatly. +

+
$MESSAGE [y/N]:
+
+

When you are using `centos-art.sh' script in a locale different +from en_US.UTF-8, confirmation answer may be different from +`y'. For example, if you are using es_ES.UTF-8 locale, the +confirmation question would look like: +

+
$MESSAGE [s/N]:
+
+

and the confirmation answer would be `s', as it is on Spanish +`sí' word. +

+

Definition of which confirmation word to use is set on translation +messages for your specific locale information. See section trunk/Scripts/Bash/Functions/Locale, for more information about locale-specific +translation messages. +

+
+
`AsToKnowMoreLine'
+

To standardize `to know more, run the following command:' +messages. When the `AsToKnowMoreLine' option is used, the +MESSAGE value should be set to "$(caller)". caller +is a Bash builtin that returns the context of the current subroutine +call. `AsToKnowMoreLine' option uses caller builtin +output to build documentation entries dynamically. +

+
----------------------------------------------------------------------
+To know more, run the following command:
+centos-art help --read='path/to/dir'
+----------------------------------------------------------------------
+
+

Use `AsToKnowMoreLine' option after errors and for intentional +script termination. +

+
+
`AsRegularLine'
+

To standardize regular messages using one-column format. +

+

When MESSAGE contains a colon inside (e.g., `description: +message'), the cli_printMessage function outputs MESSAGE +using two-columns format. +

+
+ +
Info

Tip

To improve two-columns format, change the following file: +

trunk/Scripts/Bash/Styles/output_forTwoColumns.awk
+
+ +

Use cli_printMessage function whenever you need to output +information from `centos-art.sh' script. +

+ + + +

3.37.3.3 Specific functions

+ +

The following specific functions of `centos-art.sh' script, are +available for you to use: +

+ + + + + + + + + + +
3.38 trunk/Scripts/Bash/Functions/Help   +
3.39 trunk/Scripts/Bash/Functions/Html   +
3.40 trunk/Scripts/Bash/Functions/Locale   +
3.41 trunk/Scripts/Bash/Functions/Path   +
3.42 trunk/Scripts/Bash/Functions/Render   +
3.43 trunk/Scripts/Bash/Functions/Render/Config   +
3.44 trunk/Scripts/Bash/Functions/Shell   +
3.45 trunk/Scripts/Bash/Functions/Svg   +
3.46 trunk/Scripts/Bash/Functions/Verify   +
+ + +

3.37.4 See also

+ + + +
3.36 trunk/Scripts/Bash   +
3.47 trunk/Scripts/Bash/Locale   +
- - + + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_41.html b/Manuals/en/Html/Repository/repository_41.html index ae33ed0..b397d91 100644 --- a/Manuals/en/Html/Repository/repository_41.html +++ b/Manuals/en/Html/Repository/repository_41.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.38 trunk/Scripts/Bash +CentOS Artwork Repository: 3.38 trunk/Scripts/Bash/Functions/Help - - + + @@ -59,156 +59,96 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.38 trunk/Scripts/Bash

+ + +

3.38 trunk/Scripts/Bash/Functions/Help

- +

3.38.1 Goals

-

The `trunk/Scripts/Bash' directory exists to organize the trunk -development line of `centos-art.sh' automation script. The -`centos-art.sh' script standardizes frequent tasks inside your -working copy of CentOS Artwork Repository. -

+
    +
  • ... +
+ - +

3.38.2 Description

-

The best way to understand `centos-art.sh' automation script is -studying its source code. The `centos-art.sh' script is splited -in several configuration and function files which are loaded when the -`centos-art.sh' script is executed. This section describes the -order in which `centos-art.sh' loads its configuration and -function files. -

-

When you type the centos-art command in your terminal, the -operating system trys to execute that command. In order to execute the -command, the operating system needs to know where it is, so the -operating system uses the PATH environment variable to look for -that command's location. If your system was prepared to use CentOS -Artwork Repository correctly (see section trunk/Scripts/Bash/Functions/Verify), you should have a symbolic link inside `~/bin/' -directory that points to the `centos-art.sh' script file. As -`~/bin/' directory is, by default, inside PATH environment -variable, the execution of centos-art command runs the -`centos-art.sh' script. -

-

When `centos-art.sh' script is executed, the first it does is -executing the `trunk/Scripts/Bash/initFunctions.sh' script to -initialize global variables (e.g., gettext's variables) and -global function scripts. Global function scripts are located inside -`trunk/Scripts/Bash/Functions' directory and their file names -begin with `cli'. Global function scripts provide common -functionalities that can be used anywhere inside `centos-art.sh' -script execution environment. -

-

Once global variables and function scripts have been loaded, -`centos-art.sh' script executes the cli global function -from `cli.sh' function script to retrive command-line arguments -and define some default values that may be used later by specific -function scripts (see section trunk/Scripts/Bash/Functions). -

-

As convenction, the `centos-art.sh' command-line arguments have -the following format: +

    +
  • ... +
+ + + +

3.38.2.1 Output different formats

+ +

Remove -I option from info and plaintext output. Before output info +and plaintext information we moved inside /home/centos/artwork +directory which is the base location for paths inside texinfo +documentation files. There is no need for info and plaintext output +commands to specify the -I options since the command already takes +place in the correct location the path information is correctly built +on.

-
centos-art arg1 --arg2=val2 --arg3=val3
-
-

In the above example, `centos-art' is the command you use to -invoke `centos-art.sh' script. The `arg1' represents the -action you want to do (e.g., `verify', `render', -`locale', `help', etc.). The remaining arguments are -modifiers to `arg1'. The `--arg2' definition is -required. The `--arg3' is optional. For example, if you want -to render all anaconda progress slides, for all major releases of -CentOS distribution, for all languages availabe using TreeFlower motif -as background, you use the following command: +

Nevertheless, the -I option is still required for html output. Once +inside /home/centos/artwork we need to move up to html output +directory in order to run texi2html output command from inthere. This +make texi2html to set relative path to images when html output is +generated.

-
centos-art render --entry=trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Progress
-
-

Now, if you only want to render anaconda progress -`01-welcome.png' slide, for CentOS distribution major release 5, -in English language, you need to add the third argument as follows: +

Relative path to images under html output directory will fail since +there is no image in such location. Instead, a different absolute +location is used. So we need to build that absolute path in order for +images can be shown as we expect.

-
centos-art render --entry=trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Progress --filter=5/en/01-welcome
-
-

Once command-line arguments have been retrived, the -`centos-art.sh' script loads specific functions using the -`cli_getActions.sh' function script. For example, if you run the -command centos-art render --entry, the `centos-art.sh' -script will look for `trunk/Scripts/Bash/Functions/Render' -directory and will load the render function from -`render.sh' function script; this, in order to achive the -rendering task as it defines. +

So this why we still need to use the -I option. We use the -I option +to append the location /home/centos/artwork to texi2html search path; +and because we use @image definition using trunk/ as root +location to define images location ... texi2html is able to find the +correct path to image, no matter where you execute the centos-art.sh +help command.

-
-
+------------------------------------------------------------------+
-| [centos@host]$ centos-art action 'path/to/dir' --option='value'  |
-+------------------------------------------------------------------+
-| ~/bin/centos-art --> ~/artwork/trunk/Scripts/Bash/centos-art.sh  |
-+---v-----------------------------------------v--------------------+
-    | centos-art.sh                           |
-    +---v---------------------------------v---+
-    .   | initFunctions.sh                |   .
-    .   +---------------------------------+   .
-    .   | cli $@                          |   .
-    .   +---v-------------------------v---+   .
-    .   .   | cli_getActions $@       |   .   .
-    .   .   +---v-----------------v---+   .   .
-    .   .   .   | function call 1 |   .   .   .
-    .   .   .   | function call 2 |   .   .   .
-    .   .   .   | function call n |   .   .   .
-    .   .   .   +-----------------+   .   .   .
-    .   .   ...........................   .   .
-    .   ...................................   .
-    ...........................................
-
-

Figure 3.8: The `centos-art.sh' initialization environment. - +

Note that we keep images and documentation output in two different +absolute locations. This is intentional. Such configuration let us +maintain documentation and images independently one another.

- +

3.38.3 Usage

-

The `centos-art.sh' script usage information is described inside -each specific function documentation (see section trunk/Scripts/Bash/Functions). -

+
    +
  • ... +
- + +

3.38.4 See also

- - - - -
3.37 trunk/Scripts   -
3.39 trunk/Scripts/Bash/Functions   -
3.49 trunk/Scripts/Bash/Locale   -
- - + + - - + +
[ < ][ > ]
[ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_42.html b/Manuals/en/Html/Repository/repository_42.html index 0ae537e..86dbd63 100644 --- a/Manuals/en/Html/Repository/repository_42.html +++ b/Manuals/en/Html/Repository/repository_42.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.39 trunk/Scripts/Bash/Functions +CentOS Artwork Repository: 3.39 trunk/Scripts/Bash/Functions/Html - - + + @@ -59,1031 +59,62 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.39 trunk/Scripts/Bash/Functions

+ + +

3.39 trunk/Scripts/Bash/Functions/Html

- +

3.39.1 Goals

-

The `trunk/Scripts/Bash/Functions' directory exists to organize -`centos-art.sh' specific functionalities. -

- - -

3.39.2 Description

- -

The specific functions of `centos-art.sh' script are designed -with "Software Toolbox" philosophy (see (coreutils.info)Toolbox introduction) in mind: each program "should do one -thing well". Inside `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 `centos-art.sh' script are organized -inside specific directories under `trunk/Scripts/Bash/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 render, the specific function -directory for it would be `trunk/Scripts/Bash/Functions/Render'. -

-

To better understand how specific functions of `centos-art.sh' -script are designed, lets create one function which only goal is to -output different kind of greetings to your screen. -

-

When we create specific functions for `centos-art.sh' script it -is crucial to know what these functions will do exactly and if there -is any function that already does what we intend to do. If there is no -one, it is good time to create them then. Otherwise, if -functionalities already available don't do what you exactly expect, -contact their authors and work together to improve them. -

-
Info

Tip

Join CentOS developers mailing list -centos-art@centos.org to share your ideas. -

- -

It is also worth to know what global functions and variables do we -have available inside `centos-art.sh' script, so advantage can be -taken from them. Global variables are defined inside global function -scripts. Global functions scripts are stored immediatly under -`trunk/Scripts/Bash/Functions' directory, in files begining with -`cli' prefix. -

-

OK, let's begin with our functionality example. -

-

What function name do we use? Well, lets use greet. Note that -`hello' word is not a verb; but an expression, a kind of -greeting, an interjection specifically. In contrast, `greet' is a -verb and describes what we do when we say `Hello!', `Hi!', -and similar expressions. -

-

So far, we've gathered the following function information: -

-
Name: greet
-Path: trunk/Scripts/Bash/Functions/Greet
-File: trunk/Scripts/Bash/Functions/Greet/greet.sh
-
-

The `greet.sh' function script is the first file -`centos-art.sh' script loads when the `greet' functionality -is called using commands like `centos-art greet --hello='World''. -The `greet.sh' function script contains the greet function -definition. -

-

Inside `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. -

-

Inside `centos-art.sh' script functions, top commentaries have -the following components: the functionality description, one-line for -copyright note with your personal information, the license under -which the function source code is released --the `centos-art.sh' -script is released as GPL, so do all its functions--, subversion's -$Id$ keyword which is later expanded by svn propset -command. -

-

In our greet function example, top commentary for -`greet.sh' function script would look like the following: -

-
#!/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., 59 Temple Place, Suite 330, Boston, MA 02111-1307
-# USA.
-# 
-# ----------------------------------------------------------------------
-# $Id$
-# ----------------------------------------------------------------------
-
-

After top commentary, separated by one blank line, the greet -function definition would look like the following: -

-
function greet {
-
-    # Define global variables.
-
-    # Define command-line interface.
-    greet_getActions
-
-}
-
-

The first definition inside greet function, are global -variables that will be available along greet function execution -environment. This time we didn't use global variable definitions for -greet function execution environment, so we left that section -empty. -

-

Later, we call greet_getActions function to define the -command-line interface of greet functionality. The greet -functionality command-line interface defines what and how actions are -performed, based on arguments combination passed to -`centos-art.sh' script. -

-
function greet_getActions {
-
-    case "$ACTIONNAM" in
-
-        --hello )
-            greet_doHello
-            ;;
-
-        --bye )
-            greet_doBye
-            ;;
-
-        * )
-            cli_printMessage "`gettext "The option provided is not valid."`"
-            cli_printMessage "$(caller)" 'AsToKnowMoreLine'
-
-    esac
-
-}
-
-

The ACTIONNAM global variable is defined in `cli.sh' -function script and contains the value passed before the equal sign -(i.e., `=') in the second command-line argument of -`centos-art.sh' script. For example, if the second command-line -argument is `--hello='World'', the value of ACTIONNAM -variable would be `--hello'. Using this configuration let us -deside which action to perform based on the action name passed to -`centos-art.sh' script as second argument. -

-

The greet function definition makes available two valid -greetings through `--hello' and `--bye' options. If no -one of them is provided as second command-line argument, the `*' -case is evaluated instead. -

-

The `*' case and its two further lines should always be present -in `_getActions.sh' function scripts, no matter what specific -functionality you are creating. This convenction helps the user to -find out documentation about current functionality in use. -

-

The greet_doHello and greet_doBye function definitions -are the core of greet specific functionality. In such function -definitions we set what our greet function really does: to -output different kinds of greetings. -

-
function greet_doHello {
-
-    cli_printMessage "`gettext "Hello"` $ACTIONVAL"
+
    
+
  •  ...
+

 
-}
-
-

The greet_doHello function definition is stored in -`greet_doHello.sh' function script. -

-
function greet_doBye {
 
-    cli_printMessage "`gettext "Goodbye"` $ACTIONVAL"
+
+
 3.39.2 Description 

 
-}
-
-

The greet_doBye function definition is stored in the -`greet_doBye.sh' function script. -

-

Both `greet_doHello.sh' and `greet_doBye.sh' function -scripts are stored inside greet's function directory path (i.e. -`trunk/Scripts/Bash/Functions/Greet'). -

-

The ACTIONVAL global variable is defined in `cli.sh' -function script and contains the value passed after the equal sign -(i.e., `=') in the second command-line argument of -`centos-art.sh' script. For example, if the second command-line -argument is `--hello='World'', the value of ACTIONVAL -variable would be `World' without quotes. -

-

Let's see how greet specific functionality files are organzied -under greet's function directory. To see file organization we -use the tree command: -

-
trunk/Scripts/Bash/Functions/Greet
-|-- greet_doBye.sh
-|-- greet_doHello.sh
-|-- greet_getActions.sh
-`-- greet.sh
-
-

To try the greet specific functionality we've just created, -pass the function name (i.e., `greet') as first argument to -`centos-art.sh' script, and any of the valid options as second -argument. Some examples are illustrated below: -

-
[centos@projects ~]$ centos-art greet --hello='World'
-Hello World
-[centos@projects ~]$ centos-art greet --bye='World'
-Goodbye World
-[centos@projects ~]$ 
-
-

The word `World' in the examples above can be anything. In fact, -change it to have a little fun. -

-

Now that we have a specific function that works as we expect, it is -time to document it. To document greet specific functionality, -we use its directory path and the help functionality -(see section trunk/Scripts/Bash/Functions/Help) of `centos-art.sh' -script, just as the following command illustrates: -

-
centos-art help --edit=trunk/Scripts/Bash/Functions/Greet
-
-

Now that we have documented our function, it is time to translate its -output messages to different languages. To translate specific -functionality output messages to different languages we use the -locale functionality (see section trunk/Scripts/Bash/Functions/Locale) of `centos-art.sh' script, just as the following command -illustrates: -

-
centos-art locale --edit
-
-
Warning

Warning

To translate output messages in different languages, -your system locale information --as in 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 -`es_ES.UTF-8' or similar. -

+
    +
  • ... +
-

Well, it seems that our example is rather complete by now. -

-

In greet function example we've described so far, we only use -cli_printMessage global function in action specific function -definitions in order to print a message simply, but more interesting -things can be achieved inside action specific function definitions. -For example, if you pass a directory path as second argument option -value, you could 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, you could add the third argument in the form -`--filter='regex'' and reduce the amount of files to process -using a regular expression pattern. -

-

The greet function described in this section may serve you as -an introduction to understand how specific functionalities work inside -`centos-art.sh' script. With some of luck this introduction will -also serve you as motivation to create your own `centos-art.sh' -script specific functionalities. -

-

By the way, the greet functionality doesn't exist inside -`centos-art.sh' script yet. Would you like to create it? -

- +

3.39.3 Usage

- - -

3.39.3.1 Global variables

- -

The following global variables of `centos-art.sh' script, are -available for you to use inside specific functions: -

-
-
Variable: TEXTDOMAIN - -
-

Default domain used to retrieve translated messages. This value is set -in `initFunctions.sh' and shouldn't be changed. -

- -
-
Variable: TEXTDOMAINDIR - -
-

Default directory used to retrieve translated messages. This value is -set in `initFunctions.sh' and shouldn't be changed. -

- -
-
Variable: FUNCNAM - -
-

Define function name. -

-

Function names associate sets of actions. There is one set of actions -for each unique function name inside `centos-art.sh' script. -

-

Dunction names are passed as first argument in `centos-art.sh' -command-line interface. For example, in the command `centos-art -render --entry=path/to/dir --filter=regex', the ACTION passed to -`centos-art.sh' script is `render'. -

-

When first argument is not provided, the `centos-art.sh' script -immediatly ends its execution. -

- -
-
Variable: ACTIONNAM - -
-

Define action name. -

-

Each action name identifies an specific action to perform, inside an -specific function. -

-

Action name names aare passed as second argument in -`centos-art.sh' command-line interface. For example, in the -command `centos-art render --entry=path/to/dir --filter=regex', -the ACTIONNAM passed to `centos-art.sh' script is -`--entry'. -

-

When second argument is not provided, the `centos-art.sh' script -immediatly ends its execution. -

- -
-
Variable: ACTIONVAL - -
-

Define action value. -

-

Action values are associated to just one action name. Action values -contain the repository entry over which its associated action will be -performed in. Repository entries can be directories, files, or URLs -refering the repository structure. -

-

When action value is not specified as repository entry, the -`centos-art.sh' script evaluates the current directory it was -executed from. If such directory is under the repository structure -(i.e., `/home/centos/artwork/'), the `centos-art.sh' script -uses that directory as value to ACTIONVAL variable. Otherwise, -if outside the repository structure, the `centos-art.sh' script -prints the message `The path provided can't be processed.' and, -after it, immediatly ends script execution. -

-

Default action value is passed as second argument in -`centos-art.sh' command-line interface. For example, in the -command `centos-art render --entry=path/to/dir --filter=regex', -the ACTIONVAL passed to `centos-art.sh' script is -`path/to/dir'. -

- -
-
Variable: REGEX - -
-

Define regular expression used as pattern to build the list of files -to process. -

-

By default, REGEX variable is set to .+ to match all -files. -

-

Functions that need to build a list of files to process use the option -`--filter' to redefine REGEX variable default value, and -so, control the amount of files to process. -

- -
-
Variable: ARGUMENTS - -
-

Define optional arguments. -

-

Optional arguments, inside `centos-art.sh' script, are considered -as all command-line arguments passed to `centos-art.sh' script, -from third argument position on. For example, in the command -`centos-art render --entry=path/to/dir --filter=regex' , the -optional arguments are from `--filter=regex' argument on. -

-

Optional arguments are parsed using getopt command through -the following base construction: -

-
# Define short options we want to support.
-local ARGSS=""
-
-# Define long options we want to support.
-local ARGSL="filter:,to:"
-
-# Parse arguments using getopt(1) command parser.
-cli_doParseArguments
-
-# Reset positional parameters using output from (getopt) argument
-# parser.
-eval set -- "$ARGUMENTS"
-
-# Define action to take for each option passed.
-while true; do
-    case "$1" in
-        --filter )
-            REGEX="$2" 
-            shift 2
-            ;;
-        --to )
-            TARGET="$2" 
-            shift 2
-            ;;
-        * )
-            break
-    esac
-done
-
-

Optional arguments provide support to command options inside -`centos-art.sh' script. For instance, consider the Subversion -(svn) command, where there are many options (e.g., -`copy', `delete', `move', etc), and inside each -option there are several modifiers (e.g., `--revision', -`--message', `--username', etc.) that can be combined one -another in their short or long variants. -

-

The ARGUMENTS variable is used to store arguments passed from -command-line for later use inside `centos-art.sh' script. Storing -arguments is specially useful when we want to run a command with some -specific options from them. Consider the following command: -

-
centos-art path --copy=SOURCE --to=TARGET --message="The commit message goes here." --username='johndoe'
-
-

In the above command, the `--message', and `--username' -options are specific to svn copy command. In such cases, -options are not interpreted by `centos-art.sh' script itself. -Instead, the `centos-art.sh' script uses getopt to -retrive them and stores them in the ARGUMENT variable for later -use, as described in the following command: -

-
# Build subversion command to duplicate locations inside the
-# workstation.
-eval svn copy $SOURCE $TARGET --quiet $ARGUMENTS
-
-

When getopt parses ARGUMENTS, we may use short options -(e.g., `-m') or long options (e.g., `--message'). When -we use short options, arguments are separated by one space from the -option (e.g., `-m 'This is a commit message.''). When we use -long options arguments are separated by an equal sign (`=') -(e.g., `--message='This is a commit message''). -

-

In order for getopt to parse ARGUMENTS correctly, it -is required to provide the short and long definition of options that -will be passed or at least supported by the command performing the -final action the function script exists for. -

-

As convenction, inside `centos-art.sh' script, short option -definitions are set in the ARGSS variable; and long option -definitions are set in the ARGSL variable. -

-

When you define short and long options, it may be needed to define -which of these option arguments are required and which not. To define -an option argument as required, you need to set one colon `:' -after the option definition (e.g., `-o m: -l message:'). On -the other hand, to define an option argument as not required, you need -to set two colons `::' after the option definition (e.g., -`-o m:: -l message::'). -

- -
-
Variable: EDITOR - -
-

Default text editor. -

-

The `centos-art.sh' script uses default text EDITOR to edit -pre-commit subversion messages, translation files, configuration -files, script files, and similar text-based files. -

-

If EDITOR environment variable is not set, `centos-art.sh' -script uses `/usr/bin/vim' as default text editor. Otherwise, the -following values are recognized by `centos-art.sh' script: -

    -
  • `/usr/bin/vim' -
  • `/usr/bin/emacs' -
  • `/usr/bin/nano' +
  • ...
-

If no one of these values is set in EDITOR environment variable, -`centos-art.sh' uses `/usr/bin/vim' text editor by default. -

- - - -

3.39.3.2 Global functions

- -

The following global functions of `centos-art.sh' script are -available for you to use inside specific functions: -

-
-
Function: cli_commitRepoChanges [LOCATION] - -
-

Syncronize changes between repository and working copy. -

-

The cli_commitRepoChanges function uses the value of -LOCATION argument as reference to perform change verification -inside the working copy using subversion commands. If LOCATION -argument is not specified as cli_commitRepoChanges first -argument, the ACTIONVAL variable is used as reference instead. -

-

The cli_commitRepoChanges function brings changes from the -repository to the working copy--using svn update--, checks -the working copy changes--using svn status command--, -prints status report--using both svn update and -svn status commands output, and finally, commits recent -changes from the working copy up to the repository--using -svn commit command--. -

-

Previous to commit the working copy changes up to the repository, the -cli_commitRepoChanges function asks you to verify -changes--using svn diff command--, and later, another -confirmation question is shown to be sure you really want to commit -changes up to central repository. -

-
-
----------------------------------------------------------------------
---> Bringing changes from the repository into the working copy
---> Checking changes in the working copy
-----------------------------------------------------------------------
-Added           0 file from the repository.
-Deleted         0 file from the repository.
-Updated         0 file from the repository.
-Conflicted      0 file from the repository.
-Merged          0 file from the repository.
-Modified        4 files from the working copy.
-Unversioned     0 file from the working copy.
-Deleted         0 file from the working copy.
-Added           0 file from the working copy.
-----------------------------------------------------------------------
-
-

Figure 3.9: The cli_commitRepoChanges function output. - -

-

Call the cli_commitRepoChanges function before or/and after -functions that modify files or directories inside the working copy as -you may need to. -

- -
-
Function: cli_checkFiles FILE [TYPE] - -
-

Verify files existence. -

-

cli_checkFiles receives a FILE absolute path and performs -file verification as specified in TYPE. When TYPE is not -specified, cli_checkFiles verifies FILE existence, no -matter what kind of file it be. If TYPE is specified, use one -of the following values: -

-
-
`d'
-
`directory'
-

Ends script execution if FILE is not a directory. -

-

When you verify directories with cli_checkFiles, if directory doesn't -exist, `centos-art.sh' script asks you for confirmation in order -to create that directory. If you answer positively, -`centos-art.sh' script creates that directory and continues -script flows normally. Otherwise, if you answer negatively, -`centos-art.sh' ends script execution with an error and -documentation message. -

-
-
`f'
-
`regular-file'
-

Ends script execution if FILE is not a regular file. -

-
`h'
-
`symbolic-link'
-

Ends script execution if FILE is not a symbolic link. -

-
`x'
-
`execution'
-

Ends script execution if FILE is not executable. -

-
`fh'
-

Ends script execution if FILE is neither a regular file or a -symbolic link. -

-
- -

As default behaviour, if FILE passes all verifications, -`centos-art.sh' script continues with its normal flow. -

- -
-
Function: cli_getCountryCodes [FILTER] - -
-

Output country codes. -

-

The cli_getCountryCodes function outputs a list with country -codes as defined in ISO3166 standard. When FILTER is provided, -cli_getCountryCodes outputs country codes that match -FILTER regular expression pattern. -

- -
-
Function: cli_getCountryName [FILTER] - -
-

Output country names. -

-

The cli_getCountryName function reads one language locale code -in the format LL_CC and outputs the name of its related country as in -ISO3166. If filter is specified, cli_getCountryName returns the -country name that matches the locale code specified in FILTER, -exactly. -

-

The cli_getCountryName function outputs country name supported -by `centos-art.sh' script. -

- -
-
Function: cli_getCurrentLocale - -
-

Output current locale used by `centos-art.sh' script. -

-

The cli_getCurrentLocale function uses LANG environment -variable to build a locale pattern that is later applied to -cli_getLocales function output in order to return the current -locale that `centos-art.sh' script works with. -

-

The current locale information, returned by -cli_getCurrentLocale, is output from more specific to less -specific. For example, if `en_GB' locale exists in -cli_getLocales function output, the `en_GB' locale would -take precedence before `en' locale. -

-

Locale precedence selection is quite important in order to define the -locale type we use for message translations. For example, if -`en_GB' is used, we are also saying that no common language -specification is used for English language (i.e., `en'). Instead, -we are using English non-common country-specific language -specifications like `en_AU', `en_BW', `en_GB', -`en_US', etc., for message translations. -

-

Use cli_getCurrentLocale function to know what current locale -information to use inside `centos-art.sh' script. -

-

The cli_getCurrentLocale function outputs current locale used -by `centos-art.sh' script. -

- -
-
Function: cli_getLangCodes [FILTER] - -
-

Output language codes. -

-

cli_getLangCodes function outputs a list of language codes as -defined in ISO639 standard. When FILTER is provided, -cli_getLangCodes outputs language codes that match FILTER -regular expression pattern. -

-

The cli_getLangCodes function outputs language codes supported -by `centos-art.sh' script. -

- -
-
Function: cli_getLangName [FILTER] - -
-

Output language names. -

-

cli_getLangName function reads one language locale code in the -format LL_CC and outputs the language related name as in ISO639. If -filter is specified, cli_getLangName returns the language name -that matches the locale code specified in FILTER, exactly. -

-

The cli_getLangName function outputs language names supported -by `centos-art.sh' script. -

-
-
Function: cli_getLocales - -
-

Output locale codes supported by `centos-art.sh' script. -

-

Occasionally, you use cli_getLocales function to add locale -information in non-common country-specific language (`LL_CC') -format for those languages (e.g., `bn_IN', `pt_BR', etc.) -which locale differences cannot be solved using common language -specifications (`LL') into one unique common locale specification -(e.g., `bn', `pt', etc.). -

- -
-
Function: cli_getRepoName NAME TYPE - -
-

Sanitate file names. -

-

Inside `centos-art.sh' script, specific functionalities rely both -in cli_getRepoName and repository file system organization to -achieve their goals. Consider cli_getRepoName function as -central place to manage file name convenctions for other functions -inside `centos-art.sh' script. -

-
Important

Important

cli_getRepoName function doesn't verify file -or directory existence, for that purpose use cli_checkFiles -function instead. -

- -

The NAME variable contains the file name or directory name you -want to sanitate. -

-

The TYPE variable can be one of the following values: -

-
`d'
-
`directory'
-

Sanitate directory NAMEs. -

-
`f'
-
`regular-file'
-

Sanitate regular file NAMEs. -

-
- -

Use cli_getRepoName function to sanitate file names and -directory names before their utilization. -

-

Use cli_getRepoName when you need to change file name -convenctions inside `centos-art.sh' script. -

-

When changing file name convenctions inside cli_getRepoName -what you are really changing is the way functions interpret repository -file system organization. In order to a complete file name convenction -change, you also need to change file names and directory names inside -repository file system organization, just as you did in -cli_getRepoName function. -

-
info

Note

See section trunk/Scripts/Bash/Functions/Path, for more -information on how to rename files and directories massively inside -repository file system organization. -

-
- -
-
Function: cli_getTemporalFile NAME - -
-

Output absolute path to temporal file NAME. -

-

cli_getTemporalFile uses `/tmp' directory as source -location to store temporal files, the `centos-art.sh' script -name, and a random identification string to let you run more than one -`centos-art.sh' script simultaneously on the same user session. -For example, due the following temporal file defintion: -

-
cli_getTemporalFile $FILE
-
-

If FILE name is `instance.svg' and unique random string is -`f16f7b51-ac12-4b7f-9e66-72df847f12de', the final temporal file, -built from previous temporal file definition, would be: -

-
/tmp/centos-art.sh-f16f7b51-ac12-4b7f-9e66-72df847f12de-instance.svg
-
-

When you use cli_getTemporalFile function to create temporal -files, be sure to remove temporal files created once you've ended up -with them. For example, consider the following construction: -

-
for FILE in $FILES;do
-
-    # Initialize temporal instance of file.
-    INSTANCE=$(cli_getTemporalFile $FILE)
-
-    # Do something ... 
-
-    # Remove temporal instance of file.
-    if [[ -f $INSTANCE ]];then
-        rm $INSTANCE
-    fi
-
-done
-
-

Use cli_getTemporalFile function whenever you need to create -temporal files inside `centos-art.sh' script. -

- -
-
Function: cli_getThemeName - -
-

Output theme name. -

-

In order for cli_getThemeName function to extract theme name -correctly, the ACTIONVAL variable must contain a directory path -under `trunk/Identity/Themes/Motifs/' directory structure. -Otherwise, cli_getThemeName returns an empty string. -

- -
-
Function: cli_printMessage MESSAGE [FORMAT] - -
-

Give format to output messages. -

-

When FORMAT is not specified, cli_printMessage outputs -information just as it was passed in MESSAGE variable. -Otherwise, FORMAT can take one of the following values: -

-
-
`AsHeadingLine'
-

To print heading messages. -

----------------------------------------------------------------------
-$MESSAGE
-----------------------------------------------------------------------
-
-
-
`AsWarningLine'
-

To print warning messages. -

----------------------------------------------------------------------
-WARNING: $MESSAGE
-----------------------------------------------------------------------
-
-
-
`AsNoteLine'
-

To print note messages. -

----------------------------------------------------------------------
-NOTE: $MESSAGE
-----------------------------------------------------------------------
-
-
-
`AsUpdatingLine'
-

To print `Updating' messages using two-columns format. -

Updating        $MESSAGE
-
-
-
`AsRemovingLine'
-

To print `Removing' messages using two-columns format. -

Removing        $MESSAGE
-
-
-
`AsCheckingLine'
-

To print `Checking' messages using two-columns format. -

Checking        $MESSAGE
-
-
-
`AsCreatingLine'
-

To print `Creating' messages using two-columns format. -

Creating        $MESSAGE
-
-
-
`AsSavedAsLine'
-

To print `Saved as' messages using two-columns format. -

Saved as        $MESSAGE
-
-
-
`AsLinkToLine'
-

To print `Linked to' messages using two-columns format. -

Linked to       $MESSAGE
-
-
-
`AsMovedToLine'
-

To print `Moved to' messages using two-columns format. -

Moved to        $MESSAGE
-
-
-
`AsTranslationLine'
-

To print `Translation' messages using two-columns format. -

Translation     $MESSAGE
-
-
-
`AsConfigurationLine'
-

To print `Configuration' messages using two-columns format. -

Configuration   $MESSAGE
-
-
-
`AsResponseLine'
-

To print response messages using one-column format. -

--> $MESSAGE
-
-
-
`AsRequestLine'
-

To print request messages using one-column format. Request messages -supress the trailing newline character from final output. -

$MESSAGE
-
-
-
`AsYesOrNoRequestLine'
-

To print `yes or no' request messages using one-column format. If -something different from `y' is answered (when using -en_US.UTF-8 locale), script execution ends immediatly. -

-
$MESSAGE [y/N]:
-
-

When you are using `centos-art.sh' script in a locale different -from en_US.UTF-8, confirmation answer may be different from -`y'. For example, if you are using es_ES.UTF-8 locale, the -confirmation question would look like: -

-
$MESSAGE [s/N]:
-
-

and the confirmation answer would be `s', as it is on Spanish -`sí' word. -

-

Definition of which confirmation word to use is set on translation -messages for your specific locale information. See section trunk/Scripts/Bash/Functions/Locale, for more information about locale-specific -translation messages. -

-
-
`AsToKnowMoreLine'
-

To standardize `to know more, run the following command:' -messages. When the `AsToKnowMoreLine' option is used, the -MESSAGE value should be set to "$(caller)". caller -is a Bash builtin that returns the context of the current subroutine -call. `AsToKnowMoreLine' option uses caller builtin -output to build documentation entries dynamically. -

-
----------------------------------------------------------------------
-To know more, run the following command:
-centos-art help --read='path/to/dir'
-----------------------------------------------------------------------
-
-

Use `AsToKnowMoreLine' option after errors and for intentional -script termination. -

-
-
`AsRegularLine'
-

To standardize regular messages using one-column format. -

-

When MESSAGE contains a colon inside (e.g., `description: -message'), the cli_printMessage function outputs MESSAGE -using two-columns format. -

-
- -
Info

Tip

To improve two-columns format, change the following file: -

trunk/Scripts/Bash/Styles/output_forTwoColumns.awk
-
- -

Use cli_printMessage function whenever you need to output -information from `centos-art.sh' script. -

- - - -

3.39.3.3 Specific functions

- -

The following specific functions of `centos-art.sh' script, are -available for you to use: -

- - - - - - - - - - -
3.40 trunk/Scripts/Bash/Functions/Help   -
3.41 trunk/Scripts/Bash/Functions/Html   -
3.42 trunk/Scripts/Bash/Functions/Locale   -
3.43 trunk/Scripts/Bash/Functions/Path   -
3.44 trunk/Scripts/Bash/Functions/Render   -
3.45 trunk/Scripts/Bash/Functions/Render/Config   -
3.46 trunk/Scripts/Bash/Functions/Shell   -
3.47 trunk/Scripts/Bash/Functions/Svg   -
3.48 trunk/Scripts/Bash/Functions/Verify   -
- - - +

3.39.4 See also

- - - -
3.38 trunk/Scripts/Bash   -
3.49 trunk/Scripts/Bash/Locale   -
- - + + - - + +
[ < ][ > ]
[ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_43.html b/Manuals/en/Html/Repository/repository_43.html index 32dd410..b326a39 100644 --- a/Manuals/en/Html/Repository/repository_43.html +++ b/Manuals/en/Html/Repository/repository_43.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.40 trunk/Scripts/Bash/Functions/Help +CentOS Artwork Repository: 3.40 trunk/Scripts/Bash/Functions/Locale - - + + @@ -59,36 +59,28 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.40 trunk/Scripts/Bash/Functions/Help

- - + -

3.40.1 Goals

- -
    -
  • ... -
+

3.40 trunk/Scripts/Bash/Functions/Locale

-

3.40.2 Description

+

3.40.1 Goals

  • ... @@ -96,47 +88,86 @@ ul.toc {list-style: none} -

    3.40.2.1 Output different formats

    - -

    Remove -I option from info and plaintext output. Before output info -and plaintext information we moved inside /home/centos/artwork -directory which is the base location for paths inside texinfo -documentation files. There is no need for info and plaintext output -commands to specify the -I options since the command already takes -place in the correct location the path information is correctly built -on. +

    3.40.2 Description

    + +

    This command looks for `.sh' files inside Bash directory and +extracts translatable strings from files, using xgettext +command, in order to create a portable object template +(`centos-art.sh.pot') file for them.

    -

    Nevertheless, the -I option is still required for html output. Once -inside /home/centos/artwork we need to move up to html output -directory in order to run texi2html output command from inthere. This -make texi2html to set relative path to images when html output is -generated. +

    With the `centos-art.sh.pot' file up to date, the +centos-art command removes the temporal list of files sotred +inside `/tmp' directory and checks the current language of your +user's session to create a portable object file for it, in the +location `$CLI_LANG/$CLI_LANG.po'.

    -

    Relative path to images under html output directory will fail since -there is no image in such location. Instead, a different absolute -location is used. So we need to build that absolute path in order for -images can be shown as we expect. +

    The CLI_LANG variable discribes the locale language used to +output messages inside centos-art command. The locale +language used inside centos-art command is taken from the +LANG environment variable. The CLI_LANG variable has the +`LL_CC' format, where `LL' is a language code from the +ISO-639 standard, and `CC' a country code from the ISO-3166 +standard.

    -

    So this why we still need to use the -I option. We use the -I option -to append the location /home/centos/artwork to texi2html search path; -and because we use @image definition using trunk/ as root -location to define images location ... texi2html is able to find the -correct path to image, no matter where you execute the centos-art.sh -help command. +

    The LANG environment variable is set when you do log in to your +system. If you are using a graphical session, change language to your +native language and do login. That would set and exoprt the LANG +environment variable to the correct value. On the other side, if you +are using a text session edit your `~/.bash_profile' file to set +and export the LANG environment variable to your native locale +as defines the locale -a command output; do logout, and do +login again.

    -

    Note that we keep images and documentation output in two different -absolute locations. This is intentional. Such configuration let us -maintain documentation and images independently one another. +

    At this point, the LANG environment variable has the appropriate +value you need, in order to translate centos-art.sh messages +to your native language (the one set in LANG environment +variable).

    - - -

    3.40.3 Usage

    +

    With the `$CLI_LANG/$CLI_LANG.po' file up to date, the +centos-art opens it for you to update translation strings. +The centos-art command uses the value of EDITOR +environment variable to determine your favorite text editor. If no +value is defined on EDITOR, the `/usr/bin/vim' text editor +is used as default. +

    +

    When you finish PO file's edition and quit text editor, the +centos-art command creates the related machine object in the +location `$CLI_LANG/LC_MESSAGES/$TEXTDOMAIN.mo'. +

    +

    At this point, all translations you made in the PO file should be +available to your language when runing centos-art.sh script. +

    +

    In order to make the centos-art.sh internationalization, the +centos-art.sh script was modified as described in the +gettext info documentation (info gettext). You +can find such modifications in the following files: +

    +
      +
    • `trunk/Scripts/Bash/initFunctions.sh' +
    • `trunk/Scripts/Bash/Functions/Help/cli_localeMessages.sh' +
    • `trunk/Scripts/Bash/Functions/Help/cli_localeMessagesStatus.sh' +
    • ...
    + +

    3.40.3 Usage

    + +
    +
    `centos-art locale --edit'
    +

    Use this command to translate command-line interface output messages +in the current system locale you are using (as specified in LANG +environment variable). +

    +
    `centos-art locale --list'
    +

    Use this command to see the command-line interface locale report. +

    +
    + +

    3.40.4 See also

    @@ -147,8 +178,8 @@ maintain documentation and images independently one another. [ > ]   [ << ] -[ Up ] -[ >> ] +[ Up ] +[ >> ]

    diff --git a/Manuals/en/Html/Repository/repository_44.html b/Manuals/en/Html/Repository/repository_44.html index e532aae..2ffcd53 100644 --- a/Manuals/en/Html/Repository/repository_44.html +++ b/Manuals/en/Html/Repository/repository_44.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.41 trunk/Scripts/Bash/Functions/Html +CentOS Artwork Repository: 3.41 trunk/Scripts/Bash/Functions/Path - - + + @@ -64,57 +64,488 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

    3.41 trunk/Scripts/Bash/Functions/Html

    +

    3.41 trunk/Scripts/Bash/Functions/Path

    3.41.1 Goals

    -
      -
    • ... -
    - +

    This section exists to organize files related to path +functiontionality of `centos-art.sh' script. The path +functionality of `centos-art.sh' script standardizes movement, +syncronization, branching, tagging, and general file maintainance +inside the repository. +

    3.41.2 Description

    -
      -
    • ... -
    - +

    "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." +

    -

    3.41.3 Usage

    +

    3.41.2.1 Repository layout

    -
      -
    • ... -
    +

    The repository layout describes organization of files and directories +inside the repository. The repository layout provides the standard +backend required for automation scripts to work correctly. If such +layout changes unexpectedly, automation scripts may confuse themselves +and stop doing what we expect from them to do. +

    +

    As convenction, inside CentOS Artwork Repository, we organize files +and directories, related to CentOS corporate visual identity, under +three top level directories named `trunk/', `branches/', and +`tags/'. +

    +
    +

    trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-6 +

    Figure 3.10: The CentOS Artwork Repository layout. + +

    +

    The `trunk/' directory (see section trunk) organizes the main +development line of CentOS corporate visual identity. Inside +`trunk/' directory structure, the CentOS corporate visual +identity concepts are implemented using directories. There is one +directory level for each relevant concept inside the repository. The +`trunk/' directory structure is mainly used to develop CentOS +corporate visual identity. +

    +

    The `branches/' directory (see section branches) oranizes parallel +development lines to `trunk/' directory. The `branches/' +directory is used to set points in time where develpment lines are +devided one from another taking separte and idependent lives that +share a common past from the point they were devided on. The +`branches/' directory is mainly used to perform quality assurance +on CentOS corporate visual identity. +

    +

    The `tags/' directory (see section tags) organizes parallel frozen +lines to `branches/' directory. The parallel frozen lines are +immutable, nothing change inside them once they has been created. The +`tags/' directory is mainly used to publish final releases of +CentOS corporate visual identity. +

    +

    The CentOS Artwork Repository layout is firmly grounded on a +Subversion base. Subversion (http://subversion.tigris.org) is 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. Subversion keeps a +single copy of the master sources. This copy is called the source +"repository"; it contains all the information to permit extracting +previous versions of those files at any time. +

    +

    3.41.2.2 Repository name convenctions

    + +

    Repository name convenctions help us to maintain consistency of names +inside the repository. +

    +

    Repository name convenctions are applied to files and directories +inside the repository layout. As convenction, inside the repository +layout, file names are all written in lowercase +(`01-welcome.png', `splash.png', `anaconda_header.png', +etc.) and directory names are all written capitalized (e.g., +`Identity', `Themes', `Motifs', `TreeFlower', +etc.). +

    +

    Repository name convenctions are implemented inside the +cli_getRepoName function of `centos-art.sh' script. With +cli_getRepoName function we reduce the amount of commands and +convenctions you need to remember concentrating them in just one +single place you can look for fixes and improvements. +

    + + +

    3.41.2.3 Repository work flow

    + +

    Repository work flow describes the steps and time intervals used to +produce CentOS corporate visual identity inside CentOS Artwork +Repository. +

    +

    To illustrate repository work flow let's consider themes' development +cycle. +

    +

    Initially, we start working themes on their trunk development line +(e.g., `trunk/Identity/Themes/Motifs/TreeFlower/'), here we +design background images and propagate them to different visual +manifestations using one theme's model as reference. +

    +

    Later, when the theme is considered "ready" for implementation (i.e. +all visual manifestations have been already set), we create a branch +for it (e.g., `branches/Identity/Themes/Motifs/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 `tags/' directory (e.g., +`tags/Identity/Themes/Motifs/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., `1') and increment one unit for each +branch created from the same trunk development line. Tags start at +zero (i.e., `0') and increment one unit for each tag created from +the same branch development line. +

    +
    +

    trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-1 + +

    Figure 3.11: Name convention for tags and branches creation. + +

    +

    As proposition, it would be convenient not to freeze trunk development +lines using tags or anything else. If you think you need to freeze a +trunk development line, create a branch for it and then freeze that +branch instead. +

    +

    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 provides a less changable area where +only small fixes/corrections 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 you can +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 `tags/' directory), CentOS Packagers (the +persons who build CentOS distribution) can use that frozen branch as +source location to fulfill CentOS distribution artwork needs. +

    + + +

    3.41.2.4 Parallel directories

    + +

    Inside CentOS Artwork Repository, parallel directories are simple +directory entries built from a common parent directory and placed in a +location different to that, the common parent directory is placed on. +Parallel directories are useful to create branches, tags, +translations, documentation, pre-rendering configuration script, and +similar directory structures. +

    +

    Parallel directories take their structure from one unique parent +directory. Inside CentOS Artwork Repository, this unique parent +directory is under `trunk/Identity' location. The +`trunk/Identity' location must be considered the reference for +whatever information you plan to create inside the repository. +

    +

    In some circumstances, parallel directories may be created removing +uncommon information from their paths. Uncommon path information +refers to those directory levels in the path which are not common for +other parallel directories. For example, when rendering +`trunk/Identity/Themes/Motifs/TreeFlower/Distro' directory +structure, the `centos-art.sh' script removes the +`Motifs/TreeFlower/' directory levels from path, in order to +build the parallel directory used to retrived translations, and +pre-rendering configuration scripts required by render +functionality. +

    +

    Another example where parallel directory removes the uncommon path +information is when we use the help functionality. This time, +`centos-art.sh' script uses parallel directory information +(without uncommon directory levels) to build the documentation entry +required by Texinfo to store documentation entries inside the +repository. +

    +
    +

    trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-3 + +

    Figure 3.12: Parallel directories removing uncommon information. + +

    +

    Othertimes, parallel directories may add uncommon information to their +paths. This is the case we use to create branches and tags. When we +create branches and tags, a numerical identifier is added to parallel +directory structure path. The place where the numerical identifier is +set on is relevant to corporate visual identity structure and should +be carefully considered where it will be. +

    +
    +

    trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-4 + +

    Figure 3.13: Parallel directories adding uncommon information. + +

    +

    When one parent directory changes, all their related parallel +directories need to be changed too. This is required in order for +parallel directories to match the new parent directory structure. In +the other hand, parallel directories should never be modified by no +reason but to satisfy their parent directory structure. Liberal change +of parallel directories may suppress the conceptual idea they were +initially created for. +

    +
    +

    trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-5 + +

    Figure 3.14: Wrong construction of parallel directories. + +

    + + +

    3.41.2.5 Syncronizing path information

    + +

    Creating parallel directories is very useful to keep repository +organized. But, what would happen to functionalities like help +(see section trunk/Scripts/Bash/Functions/Help) that rely on parent +directory structures to create documentation entries (using parallel +directory structures) if one of those parent directory structures +suddenly changes after the documentation entry has been already +created for it? +

    +

    Well, at this point, functionalities like help may confuse +themselves if path information is not updated. Such functionalities +work with parent directory structure as reference; if a parent +directory changes, the functionalities dont't even note it because +they work with the last parent directory structure available in the +repository, no matter what it is. +

    +

    In the specific case of documentation (the help functionality), +the problem mentioned above provokes that older parent directories, +already documented, remain inside documentation directory structures +as long as you get your hands into the documentation directory +structure (`trunk/Manuals') and remove what must be removed to +match the new parent directory structure. +

    +

    There is no way for help, and similar functionalities that use +parent directories as reference, to know when and how directory +movements take place inside the repository. Such information is +available only when movement actions, like thoses achived by +rm or mv commands, take place inside the +repository. So, is there, at the moment of moving files, when we need +to syncronize parallel directories with their unique parent directory +structure. +

    +

    Syncronizing parallel directories with their respecitive parent +directory implies moving files inside the repository, i.e. we need to, +firstly, rebuild the path information for each parallel directory +inside the repository, using the current path of its parent directory +as reference, and later, use the new path information to move each old +parallel directory from its old location to its new location based on +an updated path information. +

    +

    As CentOS Artwork Repository is built over a version control system, +file movements inside the repository are considered repository +changes. In order for these repository changes to be versioned, we +need to, firstly, add changes related files into version control +system, and later, use commands from the version control system to +move those files already versioned. This configuration makes possible +for everyone to know about changes details inside the repository; and +if needed, revert or update them back to a previous revision. +

    +

    Finally, once all file corrections have been already made, the +syncronization action takes care of updating path references inside +related files. Updating path references inside related files is +specially important for documentation files where documentation nodes +are built using repository path information as reference. +

    + + +

    3.41.2.6 What is the right location to store it?

    + +

    Occasionly, you may find that new corporate visual identity components +need to be added to the repository. If that is your case, the first +question you need to ask yourself, before start to create directories +blindly all over, is: What is the right location to store it? +

    +

    The CentOS Community (http://wiki.centos.org/GettingHelp) is the +best place to find answers to your question, 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 and so, make your propositions based on it. +

    +

    When looking the correct place to store new files, to bear in mind the +corporate visual identity structure used inside the CentOS Artwork +Repository (see section trunk/Identity) would be probaly the best advice +we could offer to you, the rest is just matter of choosing appropriate +names. To illustrate this desition process let's consider the +`trunk/Identity/Themes/Motifs/TreeFlower/Distro/' directory as +example. It is the main development line of CentOS distribution visual +manifestation, using TreeFlower's artistic motif, inside themes of +CentOS corporate visual identity. +

    +

    When building parent directory structures, you may find that reaching +an acceptable location may take some time, and as it happens most of +time, when you find it, that may be not a definite solution. There are +many concepts that you need to play with, in order to find a result +that match the conceptual idea you try to implement in the new +directory location. To know which these concepts are, split the +location in words and read its documentation entry from less specific +to more specific. +

    +

    For example, the +`trunk/Identity/Themes/Motifs/TreeFlower/Distro/' location +evolved through several months of contant work and there is no certain +it won't change in the future, even it fixes quite well the concept we +are trying to implement. The concepts used in +`trunk/Identity/Themes/Distro/Motifs/TreeFlower/Distro/' location +are described in the following commands, respectively: +

    +
    centos-art help --read=turnk/
+centos-art help --read=turnk/Identity/
+centos-art help --read=turnk/Identity/Themes/
+centos-art help --read=turnk/Identity/Themes/Motifs/
+centos-art help --read=turnk/Identity/Themes/Motifs/TreeFlower/
+centos-art help --read=turnk/Identity/Themes/Motifs/TreeFlower/Distro/
+
    +

    Other location concepts can be found similary as we did above, just +change the location we used above by the one you are trying to know +concepts for. +

    + + +

    3.41.3 Usage

    + +
    +
    centos-art path --copy=SRC --to=DST
    +

    Use this command to duplicate `SRC' in working copy, +remembering history. In this command, `SRC' and +`DST' can each be either a working copy (WC) path or +URL: +

    +
    +
    `WC -> WC'
    +

    Copy and schedule for addition (with history). +

    +
    +
    `WC -> URL'
    +

    Immediately commit a copy of WC to URL. +

    +
    +
    `URL -> WC'
    +

    Check out URL into WC, schedule for addition. +

    +
    +
    `URL -> URL'
    +

    Complete server-side copy; used to branch and tag. +

    +
    + +

    This command is an interface for Subversion's copy command. +Options related to Subversion's copy command can be passed +from third argument on. For example to specify a log message use the +`--message' option as follow: +

    +
    centos-art path --copy=URL/SRC --to=URL/DST --message 'Copy url/src to url/dst'
+
    +

    For more information on Subversion's copy functionality, +run the command: svn help copy | less. +

    +
    +
    centos-art path --move=SRC --to=DST
    +

    Move and/or rename something in working copy or repository. In this +command, SRC and DST can both be working copy (WC) paths or URLs: +

    +
    +
    `WC -> WC'
    +

    Move and schedule for addition (with history). +

    +
    `URL -> URL'
    +

    Complete server-side rename. +

    +
    + +

    This command is an interface for Subversion's move command. +Options related to Subversion's move command can be passed +from third argument on. For example to specify a log message use the +`--message' option as follow: +

    +
    centos-art path --move=URL/SRC --to=URL/DST --message 'Move url/src to url/dst'
+
    +

    For more information on Subversion's move functionality, +run the command: svn help move | less. +

    +
    +
    centos-art path --delete='SRC'
    +

    Use this command to remove files and directories from version control. +In this command, `SRC' can be a working copy (WC) path or URL. +

    +
    +
    `WC'
    +

    Each item specified by a PATH is scheduled for deletion upon the next +commit. Files, and directories that have not been committed, are +immediately removed from the working copy. PATHs that are, or +contain, unversioned or modified items will not be removed unless the +`--force' option is given. +

    +
    +
    `URL'
    +

    Each item specified by a URL is deleted from the repository via an +immediate commit. +

    +
    + +

    This command is an interface for Subversion's delete +command. Options related to Subversion's delete can be +passed from third argument on. For example to specify a log message +use the `--message' as follow: +

    +
    centos-art path --delete='URL' --message 'Delete url.'
+
    +

    For more information on Subversion's delete functionality, +run the command: svn help delete | less. +

    +
    +
    centos-art path --sync='SRC'
    +

    Use this command to syncronize path information inside working copy. +This command is automatically used after moving or renaming parent +directories. In this command, `SRC' is a working copy path +inside `trunk/Identity/' location, considered the parent +directory you want to syncronize path information for. +

    +
    + + +

    3.41.4 See also

    + + + +
    3.36 trunk/Scripts/Bash   +
    3.37 trunk/Scripts/Bash/Functions   +
    - - + + - +
    [ < ][ > ]
    [ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]

    diff --git a/Manuals/en/Html/Repository/repository_45.html b/Manuals/en/Html/Repository/repository_45.html index 6fd2426..ed6bad9 100644 --- a/Manuals/en/Html/Repository/repository_45.html +++ b/Manuals/en/Html/Repository/repository_45.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.42 trunk/Scripts/Bash/Functions/Locale +CentOS Artwork Repository: 3.42 trunk/Scripts/Bash/Functions/Render - - + + @@ -59,27 +59,27 @@ ul.toc {list-style: none} - - + + - + - +
    [ < ][ > ]
    [ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
    - - -

    3.42 trunk/Scripts/Bash/Functions/Locale

    + + +

    3.42 trunk/Scripts/Bash/Functions/Render

    - +

    3.42.1 Goals

      @@ -87,99 +87,38 @@ ul.toc {list-style: none}
    - +

    3.42.2 Description

    -

    This command looks for `.sh' files inside Bash directory and -extracts translatable strings from files, using xgettext -command, in order to create a portable object template -(`centos-art.sh.pot') file for them. -

    -

    With the `centos-art.sh.pot' file up to date, the -centos-art command removes the temporal list of files sotred -inside `/tmp' directory and checks the current language of your -user's session to create a portable object file for it, in the -location `$CLI_LANG/$CLI_LANG.po'. -

    -

    The CLI_LANG variable discribes the locale language used to -output messages inside centos-art command. The locale -language used inside centos-art command is taken from the -LANG environment variable. The CLI_LANG variable has the -`LL_CC' format, where `LL' is a language code from the -ISO-639 standard, and `CC' a country code from the ISO-3166 -standard. -

    -

    The LANG environment variable is set when you do log in to your -system. If you are using a graphical session, change language to your -native language and do login. That would set and exoprt the LANG -environment variable to the correct value. On the other side, if you -are using a text session edit your `~/.bash_profile' file to set -and export the LANG environment variable to your native locale -as defines the locale -a command output; do logout, and do -login again. -

    -

    At this point, the LANG environment variable has the appropriate -value you need, in order to translate centos-art.sh messages -to your native language (the one set in LANG environment -variable). -

    -

    With the `$CLI_LANG/$CLI_LANG.po' file up to date, the -centos-art opens it for you to update translation strings. -The centos-art command uses the value of EDITOR -environment variable to determine your favorite text editor. If no -value is defined on EDITOR, the `/usr/bin/vim' text editor -is used as default. -

    -

    When you finish PO file's edition and quit text editor, the -centos-art command creates the related machine object in the -location `$CLI_LANG/LC_MESSAGES/$TEXTDOMAIN.mo'. -

    -

    At this point, all translations you made in the PO file should be -available to your language when runing centos-art.sh script. -

    -

    In order to make the centos-art.sh internationalization, the -centos-art.sh script was modified as described in the -gettext info documentation (info gettext). You -can find such modifications in the following files: -

    -
      -
    • `trunk/Scripts/Bash/initFunctions.sh' -
    • `trunk/Scripts/Bash/Functions/Help/cli_localeMessages.sh' -
    • `trunk/Scripts/Bash/Functions/Help/cli_localeMessagesStatus.sh' -
    -
    • ...
    - +

    3.42.3 Usage

    -
    -
    `centos-art locale --edit'
    -

    Use this command to translate command-line interface output messages -in the current system locale you are using (as specified in LANG -environment variable). -

    -
    `centos-art locale --list'
    -

    Use this command to see the command-line interface locale report. -

    -
    +
      +
    • ... +
    - +

    3.42.4 See also

    + + +
    3.43 trunk/Scripts/Bash/Functions/Render/Config   +
    - - + + - - + +
    [ < ][ > ]
    [ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

    diff --git a/Manuals/en/Html/Repository/repository_46.html b/Manuals/en/Html/Repository/repository_46.html index c53abd2..b3c5fbb 100644 --- a/Manuals/en/Html/Repository/repository_46.html +++ b/Manuals/en/Html/Repository/repository_46.html @@ -27,10 +27,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.43 trunk/Scripts/Bash/Functions/Path +CentOS Artwork Repository: 3.43 trunk/Scripts/Bash/Functions/Render/Config - - + + @@ -59,493 +59,233 @@ ul.toc {list-style: none} - - + + - + - +
    [ < ][ > ]
    [ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
    - - -

    3.43 trunk/Scripts/Bash/Functions/Path

    + + +

    3.43 trunk/Scripts/Bash/Functions/Render/Config

    - +

    3.43.1 Goals

    -

    This section exists to organize files related to path -functiontionality of `centos-art.sh' script. The path -functionality of `centos-art.sh' script standardizes movement, -syncronization, branching, tagging, and general file maintainance -inside the repository. +

    The `trunk/Scripts/Bash/Config' directory exists to oraganize +pre-rendering configuration scripts.

    - +

    3.43.2 Description

    -

    "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." -

    - - -

    3.43.2.1 Repository layout

    - -

    The repository layout describes organization of files and directories -inside the repository. The repository layout provides the standard -backend required for automation scripts to work correctly. If such -layout changes unexpectedly, automation scripts may confuse themselves -and stop doing what we expect from them to do. +

    Pre-rendering configuration scripts let you customize the way +centos-art.sh script renders identity and translation +repository entries. Pre-rendering configuration scripts are +`render.conf.sh' files with render_loadConfig function +definition inside.

    -

    As convenction, inside CentOS Artwork Repository, we organize files -and directories, related to CentOS corporate visual identity, under -three top level directories named `trunk/', `branches/', and -`tags/'. +

    There is one `render.conf.sh' file for each pre-rendering +configuration entry. Pre-rendering configuration entries can be based +both on identity and translation repository entires. Pre-rendering +configuration entries are required for each identity entry, but not +for translation entries.

    -
    -

    trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-6 -

    Figure 3.10: The CentOS Artwork Repository layout. - -

    -

    The `trunk/' directory (see section trunk) organizes the main -development line of CentOS corporate visual identity. Inside -`trunk/' directory structure, the CentOS corporate visual -identity concepts are implemented using directories. There is one -directory level for each relevant concept inside the repository. The -`trunk/' directory structure is mainly used to develop CentOS -corporate visual identity. -

    -

    The `branches/' directory (see section branches) oranizes parallel -development lines to `trunk/' directory. The `branches/' -directory is used to set points in time where develpment lines are -devided one from another taking separte and idependent lives that -share a common past from the point they were devided on. The -`branches/' directory is mainly used to perform quality assurance -on CentOS corporate visual identity. -

    -

    The `tags/' directory (see section tags) organizes parallel frozen -lines to `branches/' directory. The parallel frozen lines are -immutable, nothing change inside them once they has been created. The -`tags/' directory is mainly used to publish final releases of -CentOS corporate visual identity. -

    -

    The CentOS Artwork Repository layout is firmly grounded on a -Subversion base. Subversion (http://subversion.tigris.org) is 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. Subversion keeps a -single copy of the master sources. This copy is called the source -"repository"; it contains all the information to permit extracting -previous versions of those files at any time. -

    - - -

    3.43.2.2 Repository name convenctions

    + +

    3.43.2.1 The `render.conf.sh' identity model

    -

    Repository name convenctions help us to maintain consistency of names -inside the repository. +

    Inside CentOS Artwork Repository, we consider identity entries to all +directories under `trunk/Identity' directory. Identity entries can be +image-based or text-based. When you render image-based identity +entries you need to use image-based pre-rendering configuration +scripts. Likewise, when you render text-based identity entries you +need to use text-based pre-rendering configuration scripts.

    -

    Repository name convenctions are applied to files and directories -inside the repository layout. As convenction, inside the repository -layout, file names are all written in lowercase -(`01-welcome.png', `splash.png', `anaconda_header.png', -etc.) and directory names are all written capitalized (e.g., -`Identity', `Themes', `Motifs', `TreeFlower', -etc.). -

    -

    Repository name convenctions are implemented inside the -cli_getRepoName function of `centos-art.sh' script. With -cli_getRepoName function we reduce the amount of commands and -convenctions you need to remember concentrating them in just one -single place you can look for fixes and improvements. +

    Inside identity pre-rendering configuration scripts, image-based +pre-rendering configuration scripts look like the following:

    +
    #!/bin/bash
 
-
-
     3.43.2.3 Repository work flow 
    
+function render_loadConfig {
 
-
    Repository work flow describes the steps and time intervals used to
-produce CentOS corporate visual identity inside CentOS Artwork
-Repository.  
-
    
-
    To illustrate repository work flow let's consider themes' development
-cycle. 
-
    
-
    Initially, we start working themes on their trunk development line
-(e.g., `trunk/Identity/Themes/Motifs/TreeFlower/'), here we
-design background images and propagate them to different visual
-manifestations using one theme's model as reference.
-
    
-
    Later, when the theme is considered "ready" for implementation (i.e.
-all visual manifestations have been already set), we create a branch
-for it (e.g., `branches/Identity/Themes/Motifs/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 `tags/' directory (e.g.,
-`tags/Identity/Themes/Motifs/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., `1') and increment one unit for each
-branch created from the same trunk development line.  Tags start at
-zero (i.e., `0') and increment one unit for each tag created from
-the same branch development line.
-
    
-
    
-
    trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-1
+    # Define rendering actions.
+    ACTIONS[0]='BASE:renderImage'
+    ACTIONS[1]='POST:renderFormats: tif xpm pdf ppm'
 
-
    Figure 3.11: Name convention for tags and branches creation.
-
-
    
-
    As proposition, it would be convenient not to freeze trunk development
-lines using tags or anything else.  If you think you need to freeze a
-trunk development line, create a branch for it and then freeze that
-branch instead.  
-
    
-
    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 provides a less changable area where
-only small fixes/corrections 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 you can
-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 `tags/' directory), CentOS Packagers (the
-persons who build CentOS distribution) can use that frozen branch as
-source location to fulfill CentOS distribution artwork needs.
+}
+
    +

    Inside identity pre-rendering configuration scripts, text-based +pre-rendering configuration scripts look like the following:

    +
    #!/bin/bash
 
-
-
     3.43.2.4 Parallel directories 
    
-
-
    Inside CentOS Artwork Repository, parallel directories are simple
-directory entries built from a common parent directory and placed in a
-location different to that, the common parent directory is placed on.
-Parallel directories are useful to create branches, tags,
-translations, documentation, pre-rendering configuration script, and
-similar directory structures.
-
    
-
    Parallel directories take their structure from one unique parent
-directory. Inside CentOS Artwork Repository, this unique parent
-directory is under `trunk/Identity' location.  The
-`trunk/Identity' location must be considered the reference for
-whatever information you plan to create inside the repository.
-
    
-
    In some circumstances, parallel directories may be created removing
-uncommon information from their paths. Uncommon path information
-refers to those directory levels in the path which are not common for
-other parallel directories.  For example, when rendering
-`trunk/Identity/Themes/Motifs/TreeFlower/Distro' directory
-structure, the `centos-art.sh' script removes the
-`Motifs/TreeFlower/' directory levels from path, in order to
-build the parallel directory used to retrived translations, and
-pre-rendering configuration scripts required by render
-functionality.
-
    
-
    Another example where parallel directory removes the uncommon path
-information is when we use the help functionality. This time,
-`centos-art.sh' script uses parallel directory information
-(without uncommon directory levels) to build the documentation entry
-required by Texinfo to store documentation entries inside the
-repository.
-
    
-
    
-
    trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-3
+function render_loadConfig {
 
-
    Figure 3.12: Parallel directories removing uncommon information.
-
-
    
-
    Othertimes, parallel directories may add uncommon information to their
-paths. This is the case we use to create branches and tags. When we
-create branches and tags, a numerical identifier is added to parallel
-directory structure path. The place where the numerical identifier is
-set on is relevant to corporate visual identity structure and should
-be carefully considered where it will be.
-
    
-
    
-
    trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-4
+    # Define rendering actions.
+    ACTIONS[0]='BASE:renderText'
+    ACTIONS[1]='POST:formatText: --width=70 --uniform-spacing'
 
-
    Figure 3.13: Parallel directories adding uncommon information.
-
-
    
-
    When one parent directory changes, all their related parallel
-directories need to be changed too. This is required in order for
-parallel directories to match the new parent directory structure.  In
-the other hand, parallel directories should never be modified by no
-reason but to satisfy their parent directory structure. Liberal change
-of parallel directories may suppress the conceptual idea they were
-initially created for.
+}
+
    +

    When using identity pre-rendering configuration scripts, you can +extend both image-based and text-based pre-rendering configuration +scripts using image-based and text-based post-rendering actions, +respectively.

    -
    -

    trunk/Identity/Models/Img/Scripts/Bash/Functions/Path/figure-5 -

    Figure 3.14: Wrong construction of parallel directories. - -

    + +

    3.43.2.2 The `render.conf.sh' translation model

    - -

    3.43.2.5 Syncronizing path information

    - -

    Creating parallel directories is very useful to keep repository -organized. But, what would happen to functionalities like help -(see section trunk/Scripts/Bash/Functions/Help) that rely on parent -directory structures to create documentation entries (using parallel -directory structures) if one of those parent directory structures -suddenly changes after the documentation entry has been already -created for it? -

    -

    Well, at this point, functionalities like help may confuse -themselves if path information is not updated. Such functionalities -work with parent directory structure as reference; if a parent -directory changes, the functionalities dont't even note it because -they work with the last parent directory structure available in the -repository, no matter what it is. -

    -

    In the specific case of documentation (the help functionality), -the problem mentioned above provokes that older parent directories, -already documented, remain inside documentation directory structures -as long as you get your hands into the documentation directory -structure (`trunk/Manuals') and remove what must be removed to -match the new parent directory structure. -

    -

    There is no way for help, and similar functionalities that use -parent directories as reference, to know when and how directory -movements take place inside the repository. Such information is -available only when movement actions, like thoses achived by -rm or mv commands, take place inside the -repository. So, is there, at the moment of moving files, when we need -to syncronize parallel directories with their unique parent directory -structure. -

    -

    Syncronizing parallel directories with their respecitive parent -directory implies moving files inside the repository, i.e. we need to, -firstly, rebuild the path information for each parallel directory -inside the repository, using the current path of its parent directory -as reference, and later, use the new path information to move each old -parallel directory from its old location to its new location based on -an updated path information. -

    -

    As CentOS Artwork Repository is built over a version control system, -file movements inside the repository are considered repository -changes. In order for these repository changes to be versioned, we -need to, firstly, add changes related files into version control -system, and later, use commands from the version control system to -move those files already versioned. This configuration makes possible -for everyone to know about changes details inside the repository; and -if needed, revert or update them back to a previous revision. -

    -

    Finally, once all file corrections have been already made, the -syncronization action takes care of updating path references inside -related files. Updating path references inside related files is -specially important for documentation files where documentation nodes -are built using repository path information as reference. +

    Translation pre-rendering configuration scripts take precedence before +default translation rendering action. Translation pre-rendering +actions are useful when default translation rendering action do not +fit itself to translation entry rendering requirements.

    - -

    3.43.2.6 What is the right location to store it?

    + +

    3.43.2.3 The `render.conf.sh' rendering actions

    -

    Occasionly, you may find that new corporate visual identity components -need to be added to the repository. If that is your case, the first -question you need to ask yourself, before start to create directories -blindly all over, is: What is the right location to store it? -

    -

    The CentOS Community (http://wiki.centos.org/GettingHelp) is the -best place to find answers to your question, 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 and so, make your propositions based on it. +

    Inside both image-based and text-based identity pre-rendering +configuration scripts, we use the `ACTIONS' array variable to +define the way centos-art.sh script performs identity +rendering. Identity rendering is organized by one `BASE' action, +and optional `POST' and `LAST' rendering actions.

    -

    When looking the correct place to store new files, to bear in mind the -corporate visual identity structure used inside the CentOS Artwork -Repository (see section trunk/Identity) would be probaly the best advice -we could offer to you, the rest is just matter of choosing appropriate -names. To illustrate this desition process let's consider the -`trunk/Identity/Themes/Motifs/TreeFlower/Distro/' directory as -example. It is the main development line of CentOS distribution visual -manifestation, using TreeFlower's artistic motif, inside themes of -CentOS corporate visual identity. +

    The `BASE' action specifies what kind of rendering does the +centos-art.sh script will perform with the files related to +the pre-rendering configuration script. The `BASE' action is +required. Possible values to `BASE' action are either +`renderImage' or `renderText' only.

    -

    When building parent directory structures, you may find that reaching -an acceptable location may take some time, and as it happens most of -time, when you find it, that may be not a definite solution. There are -many concepts that you need to play with, in order to find a result -that match the conceptual idea you try to implement in the new -directory location. To know which these concepts are, split the -location in words and read its documentation entry from less specific -to more specific. +

    To specify the `BASE' action you need to set the `BASE:' +string followed by one of the possible values. For example, if you +want to render images, consider the following definition of +`BASE' action:

    -

    For example, the -`trunk/Identity/Themes/Motifs/TreeFlower/Distro/' location -evolved through several months of contant work and there is no certain -it won't change in the future, even it fixes quite well the concept we -are trying to implement. The concepts used in -`trunk/Identity/Themes/Distro/Motifs/TreeFlower/Distro/' location -are described in the following commands, respectively: -

    -
    centos-art help --read=turnk/
-centos-art help --read=turnk/Identity/
-centos-art help --read=turnk/Identity/Themes/
-centos-art help --read=turnk/Identity/Themes/Motifs/
-centos-art help --read=turnk/Identity/Themes/Motifs/TreeFlower/
-centos-art help --read=turnk/Identity/Themes/Motifs/TreeFlower/Distro/
+
    ACTIONS[0]='BASE:renderImage'
+
    
+
    Only one `BASE' action must be specified. If more than one
+`BASE' action is specified, the last one is used. If no
+`BASE' action is specified at all, an error is triggered and the
+centos-art.sh script ends its execution.
+
    
+
    The `POST' action specifies which action to apply for
+each file rendered (at the rendering time). This action is optional.
+You can set many different `POST' actions to apply many different
+actions over the same already rendered file. Possible values to
+`POST' action are `renderFormats', `renderSyslinux',
+`renderGrub', etc. 
+
    
+
    To specify the `POST' action, you need to use set the
+`POST:' followed by the function name of the action you want to
+perform.  The exact form depends on your needs. For example, consider
+the following example to produce `xpm', `jpg', and
+`tif' images, based on already rendered `png' image, and
+also organize the produced files in directories named as their own
+extensions:
+
    
+
    ACTIONS[0]='BASE:renderImage'
+ACTIONS[1]='POST:renderFormats: xpm jpg tif'
+ACTIONS[2]='POST:groupByFormat: png xpm jpg tif'
+
    
+
    In the previous example, file organization takes place at the moment
+of rendering, just after producing the `png' base file and before
+going to the next file in the list of files to render. If you don't
+want to organized the produced files in directories named as their own
+extensions, just remove the `POST:groupByFormat' action line:
+
    
+
    ACTIONS[0]='BASE:renderImage'
+ACTIONS[1]='POST:renderFormats: xpm jpg tif'
+
    
+
    The `LAST' action specifies which actions to apply once the last
+file in the list of files to process has been rendered. The
+`LAST' action is optional. Possible values for `LAST'
+actions may be `groupByFormat', `renderGdmTgz', etc.
+
    
+
    info
    Note
     See section trunk/Scripts/Bash/Functions/Render, to know more
+about possible values for `BASE', `POST' and `LAST'
+action definitions.
+
    
+
+
    To specify the `LAST' action, you need to set the `LAST:'
+string followed by the function name of the action you want to
+perform.  For example, consider the following example if you want to
+render all files first and organize them later:
+
    
+
    ACTIONS[0]='BASE:renderImage'
+ACTIONS[1]='POST:renderFormats: xpm jpg tif'
+ACTIONS[2]='LAST:groupByformat: png xpm jpg tif'
 
    
-
    Other location concepts can be found similary as we did above, just
-change the location we used above by the one you are trying to know
-concepts for.
-
    
 
-
+
 
     3.43.3 Usage 
    
 
-
    
-
     centos-art path --copy=SRC --to=DST
    
-
    Use this command to duplicate `SRC' in working copy,
-remembering history. In this command, `SRC' and
-`DST' can each be either a working copy (WC) path or
-URL:
+
    Use the following commands to administer both identity and translation
+pre-rendering configuration scripts:
 
    
 
    
-
     `WC -> WC'
    
-
    Copy and schedule for addition (with history).
-
    
-
    
-
     `WC -> URL'
    
-
    Immediately commit a copy of WC to URL.
-
    
-
    
-
     `URL -> WC'
    
-
    Check out URL into WC, schedule for addition.
+
     `centos-art config --create='path/to/dir/''
    
+
    
+
    Use this command to create `path/to/dir' related pre-rendering
+configuration script.
 
    
 
    
-
     `URL -> URL'
    
-
    Complete server-side copy;  used to branch and tag.
-
    
-
    
-
-
    This command is an interface for Subversion's copy command.
-Options related to Subversion's copy command can be passed
-from third argument on. For example to specify a log message use the
-`--message' option as follow:
-
    
-
    centos-art path --copy=URL/SRC --to=URL/DST --message 'Copy url/src to url/dst'
-
    
-
    For more information on Subversion's copy functionality,
-run the command: svn help copy | less.
+
     `centos-art config --edit='path/to/dir/''
    
+
    
+
    Use this command to edit `path/to/dir' related pre-rendering
+configuration script.  
 
    
 
    
-
     centos-art path --move=SRC --to=DST
    
-
    Move and/or rename something in working copy or repository. In this
-command, SRC and DST can both be working copy (WC) paths or URLs: 
-
    
-
    
-
     `WC -> WC'
    
-
    Move and schedule for addition (with history).
-
    
-
     `URL -> URL'
    
-
    Complete server-side rename.
-
    
-
    
-
-
    This command is an interface for Subversion's move command.
-Options related to Subversion's move command can be passed
-from third argument on. For example to specify a log message use the
-`--message' option as follow:
-
    
-
    centos-art path --move=URL/SRC --to=URL/DST --message 'Move url/src to url/dst'
-
    
-
    For more information on Subversion's move functionality,
-run the command: svn help move | less.
+
     `centos-art config --read='path/to/dir/''
    
+
    
+
    Use this command to read `path/to/dir' related pre-rendering
+configuration script.  
 
    
 
    
-
     centos-art path --delete='SRC'
    
-
    Use this command to remove files and directories from version control.
-In this command, `SRC' can be a working copy (WC) path or URL. 
-
    
-
    
-
     `WC'
    
-
    Each item specified by a PATH is scheduled for deletion upon the next
-commit.  Files, and directories that have not been committed, are
-immediately removed from the working copy.  PATHs that are, or
-contain, unversioned or modified items will not be removed unless the
-`--force' option is given.
+
     `centos-art config --remove='path/to/dir/''
    
+
    
+
    Use this command to remove `path/to/dir' related pre-rendering
+configuration script.
 
    
 
    
-
     `URL'
    
-
    Each item specified by a URL is deleted from the repository via an
-immediate commit.
-
    
 
    
 
-
    This command is an interface for Subversion's delete
-command. Options related to Subversion's delete can be
-passed from third argument on. For example to specify a log message
-use the `--message' as follow:
+
    In the commands above, `path/to/dir' refers to one renderable
+directory path under `trunk/Identity' or
+`trunk/Translations' structures only. 
 
    
-
    centos-art path --delete='URL' --message 'Delete url.'
-
    
-
    For more information on Subversion's delete functionality,
-run the command: svn help delete | less.
-
    
-
    
-
     centos-art path --sync='SRC'
    
-
    Use this command to syncronize path information inside working copy.
-This command is automatically used after moving or renaming parent
-directories.  In this command, `SRC' is a working copy path
-inside `trunk/Identity/' location, considered the parent
-directory you want to syncronize path information for.
-
    
-
    
-
 
-
+
 
     3.43.4 See also 
    
 
 
-
+
-
    3.38 trunk/Scripts/Bash  
+
    3.36 trunk/Scripts/Bash  
+
    3.37 trunk/Scripts/Bash/Functions  
 
    3.39 trunk/Scripts/Bash/Functions  
+
    3.42 trunk/Scripts/Bash/Functions/Render  
 
    
 
    
 
 
 
-
-
+
+
-
-
+
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_47.html b/Manuals/en/Html/Repository/repository_47.html
index bc2024d..94812e5 100644
--- a/Manuals/en/Html/Repository/repository_47.html
+++ b/Manuals/en/Html/Repository/repository_47.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.44 trunk/Scripts/Bash/Functions/Render
+CentOS Artwork Repository: 3.44 trunk/Scripts/Bash/Functions/Shell
 
-
-
+
+
 
 
 
@@ -59,66 +59,213 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
-
-
     3.44 trunk/Scripts/Bash/Functions/Render 
    
+
+
+
     3.44 trunk/Scripts/Bash/Functions/Shell 
    
 
 
-
+
 
     3.44.1 Goals 
    
 
-
      
-
    •  ...
-
    
-
+
    This section exists to organize files related to shell
+functionality of `centos-art.sh' script.
+
    
 
-
+
 
     3.44.2 Description 
    
 
-
      
-
    •  ...
-
    
+
    The shell functionality of `centos-art.sh' script helps
+you to maintain bash scripts inside repository. For example, suppose
+you've created many functionalities for `centos-art.sh' script,
+and you want to use a common copyright and license note for
+consistency in all your script files. If you have a bunch of files,
+doing this one by one wouldn't be a big deal. In contrast, if the
+amount of files grows, updating the copyright and license note for all
+of them would be a task rather tedious. The shell functionality
+exists to solve maintainance tasks just as the one previously
+mentioned.
+
    
+
    When you use shell functionality to update copyright inside
+script files, it is required that your script files contain (at least)
+the following top commentary structure:
+
    
+
     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| }
+
    
+
    Relevant lines in the above structure are lines from 5 to 9.
+Everything else in the file is left immutable.
+
    
+
    When you are updating copyright through shell
+functionality,  the `centos-art.sh' script replaces everything
+in-between line 5 --the first one matching `^# Copyright .+$'
+string-- and line 9--the first long dash separator matching `^#
+-+$'-- with the content of copyright template instance.
+
    
+
    Caution
    Caution
     Be sure to add the long dash separator that matches
+`^# -+$' regular expression before the function
+definition. Otherwise, if the `Copyright' line is present but no
+long dash separator exists, `centos-art.sh' will remove anything
+in-between the `Copyright' line and the end of file. This way you
+may lost your function definitions entirely.
+
    
+
+
    The copyright template instance is created from one copyright template
+stored in the `Config/tpl_forCopyright.sed' file.  The template
+instance is created once, and later removed when no longer needed. At
+this moment, when template instance is created, the
+`centos-art.sh' script takes advantage of automation in order to
+set copyright full name and date dynamically.
+
    
+
    When you use shell functionality to update copyright, the first
+thing `shell' functionality does is requesting copyright
+information to user, and later, if values were left empty (i.e., no
+value was typed before pressing RET key), the `shell'
+functionality uses its own default values.
+
    
+
    When shell functionality uses its own default values, the final
+copyright note looks like the following:
+
    
+
     1| #!/bin/bash
+ 2| #
+ 3| # doSomthing.sh -- The function description goes here.
+ 4| #
+ 5| # Copyright (C) 2003, 2010 The CentOS Project
+ 6| # 
+ 7| # This program is free software; you can redistribute it and/or modify
+ 8| # it under the terms of the GNU General Public License as published by
+ 9| # the Free Software Foundation; either version 2 of the License, or
+10| # (at your option) any later version.
+11| # 
+12| # This program is distributed in the hope that it will be useful, but
+13| # WITHOUT ANY WARRANTY; without even the implied warranty of
+14| # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+15| # General Public License for more details.
+16| #
+17| # You should have received a copy of the GNU General Public License
+18| # along with this program; if not, write to the Free Software
+19| # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
+20| # USA.
+21| #
+22| # ----------------------------------------------------------------------
+23| # $Id$
+24| # ----------------------------------------------------------------------
+25|
+26| function doSomething {
+27|
+28| }
+
    
+
    Relevant lines in the above structure are lines from 5 to 22.  Pay
+attention how the copyright line was built, and how the license was
+added into the top comment where previously was just three dots.
+Everything else in the file was left immutable. 
+
    
+
    To change copyright information (i.e., full name or year information),
+run the shell functionality over the root directory containing
+the script files you want to update copyright in and enter the
+appropriate information when it be requested. You can run the
+shell functionality as many times as you need to.
+
    
+
    To change copyright license (i.e., the text in-between lines 7 and
+20), you need to edit the `Config/tpl_forCopyright.sed' file, set
+the appropriate information, and run the shell functionality
+once again for changes to take effect over the files you specify.
+
    
+
    Important
    Important
     The `centos-art.sh' script is released as: 
+
    
+
    GNU GENERAL PUBLIC LICENSE
+Version 2, June 1991
+
+Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+
    
+
    Do not change the license information under which `centos-art.sh'
+script is released. Instead, if you think a different license must be
+used, please share your reasons at CentOS Developers mailing list.
+
    
 
 
-
+
 
     3.44.3 Usage 
    
 
-
      
-
    •  ...
-
    
+
    
+
     centos-art sh --update-copyright='path/to/dir'
    
+
     centos-art sh --update-copyright='path/to/dir' --filter='regex'
    
+
    Use these commands to update copyright information in `.sh' files
+under `path/to/dir' directory. 
+
    
+
    
 
+
    When you provide `--filter='regex'' argument, the list of files
+to process is reduced as specified in `regex' regular expression.
+Inside `centos-art.sh' script, the `regex' regular
+expression is used in combination with find command to look
+for files matching the regular expression path pattern.
+
    
+
    Warning
    Warning
     In order for `regex' regular expression to match
+a file, the `regex' regular expresion must match the whole file
+path not just the file name. 
+
    
 
-
+
    For example, if you want to match all `render.conf.sh' files
+inside `path/to/dir', use the .+/render.conf regular
+expression.  Later, `centos-art.sh' script uses this value inside
+^$REGEX\.sh$ expression in order to build the final regular
+expression (i.e., ^.+/render.conf\.sh$) that is evaluated
+against available file paths inside the list of files to process.
+
    
+
    Exceptionally, when you provide `--filter='regex'' in the way
+that `regex', appended to `path/to/dir/' (i.e.
+`path/to/dir/regex'), matches a regular file; the
+`centos-art.sh' script uses the file matching as only file in the
+list of files to process. 
+
    
+
+
 
     3.44.4 See also 
    
 
 
-
+
    3.45 trunk/Scripts/Bash/Functions/Render/Config  
+
    3.36 trunk/Scripts/Bash  
+
    3.37 trunk/Scripts/Bash/Functions  
 
    
 
    
 
 
 
-
-
+
+
-
-
+
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_48.html b/Manuals/en/Html/Repository/repository_48.html
index 336f642..52ccba1 100644
--- a/Manuals/en/Html/Repository/repository_48.html
+++ b/Manuals/en/Html/Repository/repository_48.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.45 trunk/Scripts/Bash/Functions/Render/Config
+CentOS Artwork Repository: 3.45 trunk/Scripts/Bash/Functions/Svg
 
-
-
+
+
 
 
 
@@ -59,233 +59,252 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
-
-
     3.45 trunk/Scripts/Bash/Functions/Render/Config 
    
+
+
+
     3.45 trunk/Scripts/Bash/Functions/Svg 
    
 
 
-
+
 
     3.45.1 Goals 
    
 
-
    The `trunk/Scripts/Bash/Config' directory exists to oraganize
-pre-rendering configuration scripts.
+
    This section exists to organize files related to svg
+functionality of `centos-art.sh' script.
 
    
 
-
+
 
     3.45.2 Description 
    
 
-
    Pre-rendering configuration scripts let you customize the way
-centos-art.sh script renders identity and translation
-repository entries.  Pre-rendering configuration scripts are
-`render.conf.sh' files with render_loadConfig function
-definition inside. 
-
    
-
    There is one `render.conf.sh' file for each pre-rendering
-configuration entry. Pre-rendering configuration entries can be based
-both on identity and translation repository entires.  Pre-rendering
-configuration entries are required for each identity entry, but not
-for translation entries. 
+
    The svg functionality of `centos-art.sh' script helps you
+to maintain scalable vector graphics (SVG) inside repository. For
+example, suppose you've been working in CentOS default design models
+under `trunk/Identity/Themes/Models/', and you want to set common
+metadata to all of them, and later remove all unused SVG defintions
+from `*.svg' files. Doing so file by file may be a tedious task,
+so the `centos-art.sh' script provides the svg
+functionality to aid you maintain such actions.
 
    
+
 
-
-
     3.45.2.1 The `render.conf.sh' identity model 
    
+
+
     3.45.2.1 Metadata maintainance 
    
 
-
    Inside CentOS Artwork Repository, we consider identity entries to all
-directories under `trunk/Identity' directory. Identity entries can be
-image-based or text-based. When you render image-based identity
-entries you need to use image-based pre-rendering configuration
-scripts. Likewise, when you render text-based identity entries you
-need to use text-based pre-rendering configuration scripts.
+
    The metadata used is defined by Inkscape 0.46 using the SVG standard
+markup. The `centos-art.sh' script replaces everything
+in-between <metadata and </metadata> tags with a
+predefined metadata template we've set for this purpose.
 
    
-
    Inside identity pre-rendering configuration scripts, image-based
-pre-rendering configuration scripts look like the following:
+
    The metadata template was created using the metadata information of a
+file which, using Inkscape 0.46, all metadata fields were set. This
+created a complete markup representation of how SVG metadata would
+look like. Later, we replaced every single static value with a
+translation marker in the form `=SOMETEXT=', where
+SOMETEXT is the name of its main opening tag. Later, we
+transform the metadata template into a sed replacement set of commads
+escaping new lines at the end of each line.
 
    
-
    #!/bin/bash
-
-function render_loadConfig {
-
-    # Define rendering actions.
-    ACTIONS[0]='BASE:renderImage'
-    ACTIONS[1]='POST:renderFormats: tif xpm pdf ppm'
-
-}
-
    
-
    Inside identity pre-rendering configuration scripts, text-based
-pre-rendering configuration scripts look like the following:
+
    With metadata template in place, the `centos-art.sh' script uses
+it to create a metadata template instance for the file being processed
+currently.  The metadata template instance contains the metadata
+portion of sed replacement commands with translation markers already
+traduced.  In this action, instance creation, is where we take
+advantage of automation and generate metadata values like title, date,
+keywords, source, identifier, and relation dynamically, based on the
+file path `centos-art.sh' script is currently creating metadata
+information for.
 
    
-
    #!/bin/bash
-
-function render_loadConfig {
-
-    # Define rendering actions.
-    ACTIONS[0]='BASE:renderText'
-    ACTIONS[1]='POST:formatText: --width=70 --uniform-spacing'
-
-}
-
    
-
    When using identity pre-rendering configuration scripts, you can
-extend both image-based and text-based pre-rendering configuration
-scripts using image-based and text-based post-rendering actions,
-respectively. 
+
    With metadata template instance in place, the `centos-art.sh'
+script uses it to replace real values inside all `.svg' files
+under the current location you're running the `centos-art.sh'
+script on.  Default behaviour is to ask user to enter each metadatum
+required, one by one. If user leaves metadatum empty, by pressing
+RET key, `centos-art.sh' uses its default value.
 
    
-
-
-
     3.45.2.2 The `render.conf.sh' translation model 
    
-
-
    Translation pre-rendering configuration scripts take precedence before
-default translation rendering action. Translation pre-rendering
-actions are useful when default translation rendering action do not
-fit itself to translation entry rendering requirements.
+
    The `centos-art.sh' script modifies the following metadata:
 
    
-
-
-
     3.45.2.3 The `render.conf.sh' rendering actions 
    
-
-
    Inside both image-based and text-based identity pre-rendering
-configuration scripts, we use the `ACTIONS' array variable to
-define the way centos-art.sh script performs identity
-rendering.  Identity rendering is organized by one `BASE' action,
-and optional `POST' and `LAST' rendering actions.
-
    
-
    The `BASE' action specifies what kind of rendering does the
-centos-art.sh script will perform with the files related to
-the pre-rendering configuration script. The `BASE' action is
-required. Possible values to `BASE' action are either
-`renderImage' or `renderText' only.
-
    
-
    To specify the `BASE' action you need to set the `BASE:'
-string followed by one of the possible values. For example, if you
-want to render images, consider the following definition of
-`BASE' action:
+
    
+
     `Title'
    
+
    Name by which this document is formally known. If no value is set
+here, `centos-art.sh' script uses the file name as title.
 
    
-
    ACTIONS[0]='BASE:renderImage'
-
    
-
    Only one `BASE' action must be specified. If more than one
-`BASE' action is specified, the last one is used. If no
-`BASE' action is specified at all, an error is triggered and the
-centos-art.sh script ends its execution.
+
    
+
     `Date'
    
+
    Date associated with the creation of this document (YYYY-MM-DD). If no
+value is set here, `centos-art.sh' script uses the current date
+information as in date +%Y-%m-%d.
 
    
-
    The `POST' action specifies which action to apply for
-each file rendered (at the rendering time). This action is optional.
-You can set many different `POST' actions to apply many different
-actions over the same already rendered file. Possible values to
-`POST' action are `renderFormats', `renderSyslinux',
-`renderGrub', etc. 
+
    
+
     `Creator'
    
+
    Name of entity primarily responsible for making the content of this
+document. If no value is set here, `centos-art.sh' script uses
+the string `The CentOS Project'.
 
    
-
    To specify the `POST' action, you need to use set the
-`POST:' followed by the function name of the action you want to
-perform.  The exact form depends on your needs. For example, consider
-the following example to produce `xpm', `jpg', and
-`tif' images, based on already rendered `png' image, and
-also organize the produced files in directories named as their own
-extensions:
+
    
+
     `Rights'
    
+
    Name of entity with rights to the intellectual Property of this
+document. If no value is set here, `centos-art.sh' script uses
+the string `The CentOS Project'.
 
    
-
    ACTIONS[0]='BASE:renderImage'
-ACTIONS[1]='POST:renderFormats: xpm jpg tif'
-ACTIONS[2]='POST:groupByFormat: png xpm jpg tif'
-
    
-
    In the previous example, file organization takes place at the moment
-of rendering, just after producing the `png' base file and before
-going to the next file in the list of files to render. If you don't
-want to organized the produced files in directories named as their own
-extensions, just remove the `POST:groupByFormat' action line:
+
    
+
     `Publisher'
    
+
    Name of entity responsible for making this document available. If no
+value is set here, `centos-art.sh' script uses the string
+`The CentOS Project'.
 
    
-
    ACTIONS[0]='BASE:renderImage'
-ACTIONS[1]='POST:renderFormats: xpm jpg tif'
-
    
-
    The `LAST' action specifies which actions to apply once the last
-file in the list of files to process has been rendered. The
-`LAST' action is optional. Possible values for `LAST'
-actions may be `groupByFormat', `renderGdmTgz', etc.
+
    
+
     `Identifier'
    
+
    Unique URI to reference this document. If no value is set here,
+`centos-art.sh' script uses the current file path to build the
+related url that points to current file location inside repository
+central server.
 
    
-
    info
    Note
     See section trunk/Scripts/Bash/Functions/Render, to know more
-about possible values for `BASE', `POST' and `LAST'
-action definitions.
-
    
-
-
    To specify the `LAST' action, you need to set the `LAST:'
-string followed by the function name of the action you want to
-perform.  For example, consider the following example if you want to
-render all files first and organize them later:
+
    
+
     `Source'
    
+
    Unique URI to reference the source of this document. If no value is
+set here, `centos-art.sh' script uses current file path to build
+the related url that points to current file location inside repository
+central server.
 
    
-
    ACTIONS[0]='BASE:renderImage'
-ACTIONS[1]='POST:renderFormats: xpm jpg tif'
-ACTIONS[2]='LAST:groupByformat: png xpm jpg tif'
-
    
-
-
-
     3.45.3 Usage 
    
-
-
    Use the following commands to administer both identity and translation
-pre-rendering configuration scripts:
+
    
+
     `Relation'
    
+
    Unique URI to a related document. If no value is set here,
+`centos-art.sh' script uses current file path to build the
+related url that points to current file location inside repository
+central server.
 
    
-
    
-
     `centos-art config --create='path/to/dir/''
    
-
    
-
    Use this command to create `path/to/dir' related pre-rendering
-configuration script.
+
    
+
     `Language'
    
+
    Two-letter language tag with optional subtags for the language of this
+document. (e.g. `en-GB'). If no value is set here,
+`centos-art.sh' script uses the current locale information as in
+cli_getCurrentLocale function.
 
    
 
    
-
     `centos-art config --edit='path/to/dir/''
    
-
    
-
    Use this command to edit `path/to/dir' related pre-rendering
-configuration script.  
+
     `Keywords'
    
+
    The topic of this document as comma-separated key words, prhases, or
+classifications. If no value is set here, `centos-art.sh' script
+uses file path to build 
 
    
 
    
-
     `centos-art config --read='path/to/dir/''
    
-
    
-
    Use this command to read `path/to/dir' related pre-rendering
-configuration script.  
+
     `Coverage'
    
+
    Extent or scope of this document. If no value is set here,
+`centos-art.sh' script uses the string `The CentOS Project'.
 
    
 
    
-
     `centos-art config --remove='path/to/dir/''
    
-
    
-
    Use this command to remove `path/to/dir' related pre-rendering
-configuration script.
+
     `Description'
    
+
    Description about the document. If no value is set here,
+`centos-art.sh' script uses uses empty value as default.
 
    
 
    
+
     `Contributors'
    
+
    People that contributes in the creation/maintainance of the document.
+If no value is set here, `centos-art.sh' script uses uses empty
+value as default.
+
    
 
    
 
-
    In the commands above, `path/to/dir' refers to one renderable
-directory path under `trunk/Identity' or
-`trunk/Translations' structures only. 
+
    The `License' metadatum is not set as a choise, by now. It is
+fixed Creative Common Attribution Share-Alike 3.0 License. This is done in order to
+grant license consistency among all SVG files we manage inside CentOS
+Artwork Repository.
 
    
+
 
 
+
     3.45.2.2 Unused definitions 
    
+
+
    As SVG files grow they may end up with unused definitions inside. For
+example, if you stop using a pattern or gradient, tags used to define
+them are considered unused definitions then. Inkscape 0.46 brings the
+`Vaccum Defs' feature to remove those unused definitions from SVG
+files. The `Vaccum Defs' feature is available both at graphical
+interface and command line interface.
+
    
+
    If you have one or two couple of files, removing unused SVG
+definitions using graphical interface may be enough to you.  In
+contrast, if you have houndred of files to maintain it is not a fun
+task to use the gui interface to remove unused SVG definitions editing
+those files one by one.
+
    
+
    To remove unused SVG definitions from several SVG files, the
+`centos-art.sh' script uses Inkscape's command-line interface,
+specifically with the `--vaccum-defs' option.
+
    
+
+
+
     3.45.3 Usage 
    
+
+
    
+
     centos-art svg --update-metadata='path/to/dir'
    
+
     centos-art svg --update-metadata='path/to/dir' --filter='regex'
    
+
    Use these commands to update metadata information to `.svg' files
+under `path/to/dir' directory.
+
    
+
    
+
     centos-art svg --vacuum-defs='path/to/dir'
    
+
     centos-art svg --vacuum-defs='path/to/dir' --filter='regex'
    
+
    Use these commands to remove unused definitions inside `.svg'
+files under `path/to/dir' directory. 
+
    
+
    
+
+
    When you provide `--filter='regex'' argument, the list of files
+to process is reduced as specified in `regex' regular expression.
+Inside `centos-art.sh' script, the `regex' regular
+expression is used in combination with find command to look
+for files matching the regular expression path pattern.
+
    
+
    Warning
    Warning
     In order for `regex' regular expression to match
+a file, the `regex' regular expresion must match the whole file
+path not just the file name. 
+
    
+
+
    For example, if you want to match all `summary.svg' files inside
+`path/to/dir', use the .+/summary regular expression.
+Later, `centos-art.sh' script uses this value inside
+^$REGEX\.svg$ expression in order to build the final regular
+expression (i.e., ^.+/summary\.svg$) that is evaluated against
+available file paths inside the list of files to process.
+
    
+
    Exceptionally, when you provide `--filter='regex'' in the way
+that `regex', appended to `path/to/dir/' (i.e.
+`path/to/dir/regex'), matches a regular file; the
+`centos-art.sh' script uses the file matching as only file in the
+list of files to process. 
+
    
+
+
 
     3.45.4 See also 
    
 
 
-
-
-
    3.38 trunk/Scripts/Bash  
-
    3.39 trunk/Scripts/Bash/Functions  
+
    3.36 trunk/Scripts/Bash  
 
    3.44 trunk/Scripts/Bash/Functions/Render  
+
    3.37 trunk/Scripts/Bash/Functions  
 
    
 
    
 
 
 
-
-
+
+
-
-
+
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_49.html b/Manuals/en/Html/Repository/repository_49.html
index 6e4a047..b6e5fc4 100644
--- a/Manuals/en/Html/Repository/repository_49.html
+++ b/Manuals/en/Html/Repository/repository_49.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.46 trunk/Scripts/Bash/Functions/Shell
+CentOS Artwork Repository: 3.46 trunk/Scripts/Bash/Functions/Verify
 
-
-
+
+
 
 
 
@@ -59,213 +59,281 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
-
-
     3.46 trunk/Scripts/Bash/Functions/Shell 
    
+
+
+
     3.46 trunk/Scripts/Bash/Functions/Verify 
    
 
 
-
+
 
     3.46.1 Goals 
    
 
-
    This section exists to organize files related to shell
-functionality of `centos-art.sh' script.
+
    This section exists to organize files related to `centos-art.sh'
+script `verify' functionality.  The `verify'
+functionality of `centos-art.sh' script helps you to verify the
+workstation configuration you are planning to use as host for your
+working copy of CentOS Artwork Repository.
 
    
 
-
+
 
     3.46.2 Description 
    
 
-
    The shell functionality of `centos-art.sh' script helps
-you to maintain bash scripts inside repository. For example, suppose
-you've created many functionalities for `centos-art.sh' script,
-and you want to use a common copyright and license note for
-consistency in all your script files. If you have a bunch of files,
-doing this one by one wouldn't be a big deal. In contrast, if the
-amount of files grows, updating the copyright and license note for all
-of them would be a task rather tedious. The shell functionality
-exists to solve maintainance tasks just as the one previously
-mentioned.
-
    
-
    When you use shell functionality to update copyright inside
-script files, it is required that your script files contain (at least)
-the following top commentary structure:
+
    The first time you download CentOS Artwork Repository you need to
+configure your workstation in order to use `centos-art.sh'
+script.  These preliminar configurations are based mainly on auxiliar
+RPM packages installation, symbolic links creations, and environment
+variables definitions.  The `verify' functionality of
+`centos-art.sh' script guides you through this preliminar
+configuration process.  
 
    
-
     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| }
-
    
-
    Relevant lines in the above structure are lines from 5 to 9.
-Everything else in the file is left immutable.
+
    If this is the first time you run `centos-art.sh' script, the
+appropriate way to use its `verify' functionality is not using
+the `centos-art.sh' script directly, but the absolute path to
+centos-art.sh script instead (i.e.,
+`~/artwork/trunk/Scripts/Bash/centos-art.sh').  This is necessary
+because `centos-art' symbolic link, under `~/bin/'
+directory, has not been created yet.
 
    
-
    When you are updating copyright through shell
-functionality,  the `centos-art.sh' script replaces everything
-in-between line 5 --the first one matching `^# Copyright .+$'
-string-- and line 9--the first long dash separator matching `^#
--+$'-- with the content of copyright template instance.
+
+
+
     3.46.2.1 Packages 
    
+
+
    Installation of auxiliar RPM packages provides the software required
+to manipulate files inside the repository (e.g., image files,
+documentation files, translation files, script files, etc.). Most of
+RPM packages centos-art.sh script uses are shipped with
+CentOS distribution, and can be installed from CentOS base repository.
+The only exception is `inkscape', the package we use to
+manipulate SVG files.  The `inkscape' package is not inside
+CentOS distribution so it needs to be installed from third party
+repositories.
 
    
-
    Caution
    Caution
     Be sure to add the long dash separator that matches
-`^# -+$' regular expression before the function
-definition. Otherwise, if the `Copyright' line is present but no
-long dash separator exists, `centos-art.sh' will remove anything
-in-between the `Copyright' line and the end of file. This way you
-may lost your function definitions entirely.
+
    info
    Note
     Configuration of third party repositories inside CentOS
+distribution is described in CentOS wiki, specifically in the
+following URL:
+http://wiki.centos.org/AdditionalResources/Repositories
 
    
 
-
    The copyright template instance is created from one copyright template
-stored in the `Config/tpl_forCopyright.sed' file.  The template
-instance is created once, and later removed when no longer needed. At
-this moment, when template instance is created, the
-`centos-art.sh' script takes advantage of automation in order to
-set copyright full name and date dynamically.
+
    Before installing packages, the `centos-art.sh' script uses
+sudo to request root privileges to execute yum's
+installation functionality.  If your user isn't defined as a
+privileged user--at least to run yum commands-- inside
+`/etc/sudoers' configuration file, you will not be able to
+perform package installation tasks as set in `centos-art.sh'
+script `verify' functionality. 
+
    
+
    Setting sudo privileges to users is an administrative task you have to
+do by yourself. If you don't have experience with sudo
+command, please read its man page running the command: man
+sudo. This reading will be very useful, and with some practice, you
+will be able to configure your users to have sudo
+privileges.
+
    
+
+
+
     3.46.2.2 Links 
    
+
+
    Creation of symbolic links helps us to alternate between different
+implementations of `centos-art.sh' script-line (e.g.,
+`centos-art.sh', for Bash implementation; `centos-art.py',
+for Python implementation; `centos-art.pl', for Perl
+implementation; and so on for other implementations). The
+`centos-art.sh' script-line definition takes place inside your
+personal binary (`~/bin/') directory in order to make the script
+implementation --the one that `centos-art' links to-- available
+to PATH environment variable.
 
    
-
    When you use shell functionality to update copyright, the first
-thing `shell' functionality does is requesting copyright
-information to user, and later, if values were left empty (i.e., no
-value was typed before pressing RET key), the `shell'
-functionality uses its own default values.
+
    Creation of symbolic links helps us to reuse components from repository
+working copy. For example, color information files maintained inside
+your working copy must never be duplicated inside program-specific
+configuration directories that uses them in your workstation (e.g.,
+Gimp, Inkscape, etc.).  Instead, a symbolic link must be created for
+each one of them, from program-specific configuration directories to
+files in the working copy.  In this configuration, when someone
+commits changes to color information files up to central repository,
+they--the changes committed-- will be immediatly available to your
+programs the next time you update your working copy --the place
+inside your workstation those color information files are stored--.
 
    
-
    When shell functionality uses its own default values, the final
-copyright note looks like the following:
+
    Creation of symbolic links helps us to make `centos-art.sh'
+script functionalities available outside `trunk/' repository
+directory structure, but at its same level in repository tree. This is
+useful if you need to use the "render" functionality of
+centos-art.sh under `branches/' repository directory
+structure as you usually do inside `trunk/' repository directory
+structure. As consequence of this configuration, automation scripts
+cannot be branched under `branches/Scripts' directory structure.
 
    
-
     1| #!/bin/bash
- 2| #
- 3| # doSomthing.sh -- The function description goes here.
- 4| #
- 5| # Copyright (C) 2003, 2010 The CentOS Project
- 6| # 
- 7| # This program is free software; you can redistribute it and/or modify
- 8| # it under the terms of the GNU General Public License as published by
- 9| # the Free Software Foundation; either version 2 of the License, or
-10| # (at your option) any later version.
-11| # 
-12| # This program is distributed in the hope that it will be useful, but
-13| # WITHOUT ANY WARRANTY; without even the implied warranty of
-14| # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
-15| # General Public License for more details.
-16| #
-17| # You should have received a copy of the GNU General Public License
-18| # along with this program; if not, write to the Free Software
-19| # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
-20| # USA.
-21| #
-22| # ----------------------------------------------------------------------
-23| # $Id$
-24| # ----------------------------------------------------------------------
-25|
-26| function doSomething {
-27|
-28| }
-
    
-
    Relevant lines in the above structure are lines from 5 to 22.  Pay
-attention how the copyright line was built, and how the license was
-added into the top comment where previously was just three dots.
-Everything else in the file was left immutable. 
+
+
+
     3.46.2.3 Environment variables 
    
+
+
    Definition of environemnt variables helps us to set default values to
+our user session life. The user session environment variable defintion
+takes place in the user's `~/.bash_profile' file.  The
+`verify' functionality of `centos-art.sh' script doesn't
+modify your `~/.bash_profile' file.  
 
    
-
    To change copyright information (i.e., full name or year information),
-run the shell functionality over the root directory containing
-the script files you want to update copyright in and enter the
-appropriate information when it be requested. You can run the
-shell functionality as many times as you need to.
+
    The `verify' functionality of `centos-art.sh' script
+evaluates the following environment variables:
 
    
-
    To change copyright license (i.e., the text in-between lines 7 and
-20), you need to edit the `Config/tpl_forCopyright.sed' file, set
-the appropriate information, and run the shell functionality
-once again for changes to take effect over the files you specify.
+
    
+
     EDITOR
    
+
    Default text editor. 
 
    
-
    Important
    Important
     The `centos-art.sh' script is released as: 
+
    The `centos-art.sh' script uses default text EDITOR to edit
+pre-commit subversion messages, translation files, configuration
+files, script files, and similar text-based files.
 
    
-
    GNU GENERAL PUBLIC LICENSE
-Version 2, June 1991
-
-Copyright (C) 1989, 1991 Free Software Foundation, Inc.
-59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
-
    
-
    Do not change the license information under which `centos-art.sh'
-script is released. Instead, if you think a different license must be
-used, please share your reasons at CentOS Developers mailing list.
-
    
+
    If EDITOR environment variable is not set, `centos-art.sh'
+script uses `/usr/bin/vim' as default text editor. Otherwise, the
+following values are recognized by `centos-art.sh' script:
+
    
+
      
+
    •  `/usr/bin/vim'
+
    •  `/usr/bin/emacs'
+
    •  `/usr/bin/nano'
+
    
 
+
    If no one of these values is set in EDITOR environment variable,
+`centos-art.sh' uses `/usr/bin/vim' text editor by default. 
+
    
+
    
+
     TZ
    
+
    
+
    Default time zone representation.
+
    
+
    Time representation inside repository server is set to Coordinated
+Universal Time (UTC).  Time represetation inside repository working
+copies is set as their administrators personally define.  
+
    
+
    When repository working copies time representation be defined, it
+would be a very good convention to follow if working copies
+administrators would set their systems clock to use UTC.  Otherwise it
+would be difficult for working copies users to find out when changes
+were committed up to repository server exactly in time.
+
    
+
    Info
    Tip
     Coordinated Univeral Time (UTC) representation can be
+configured when you install CentOS distribution; or later, runing the
+system-config-date command at a shell prompt from your
+graphical interface.
+
    
 
-
-
     3.46.3 Usage 
    
+
    info
    Note
     If you set your system clock to use UTC representation,
+you also need to set the TZ environment variable inside
+`~/.bash_profile' as follows:
+
    export TZ=UTC
+
    This is required in order for your terminal to display the correct
+time information of your zone, taking UTC representation as reference.
+
    
 
-
    
-
     centos-art sh --update-copyright='path/to/dir'
    
-
     centos-art sh --update-copyright='path/to/dir' --filter='regex'
    
-
    Use these commands to update copyright information in `.sh' files
-under `path/to/dir' directory. 
+
    
+
     TEXTDOMAIN
    
+
    
+
    Default domain used to retrieve translated messages.  This value is
+set in `initFunctions.sh' and shouldn't be changed.
+
    
+
    
+
     TEXTDOMAINDIR
    
+
    
+
    Default directory used to retrieve translated messages. This value is
+set in `initFunctions.sh' and shouldn't be changed.
+
    
+
    
+
     LANG
    
+
    
+
    Default locale information. This value is set when you start your
+session and can be changed using the `locale' functionality of
+`centos-art.sh' script (see section trunk/Scripts/Bash/Functions/Locale, for more information).
 
    
 
    
 
-
    When you provide `--filter='regex'' argument, the list of files
-to process is reduced as specified in `regex' regular expression.
-Inside `centos-art.sh' script, the `regex' regular
-expression is used in combination with find command to look
-for files matching the regular expression path pattern.
-
    
-
    Warning
    Warning
     In order for `regex' regular expression to match
-a file, the `regex' regular expresion must match the whole file
-path not just the file name. 
-
    
 
-
    For example, if you want to match all `render.conf.sh' files
-inside `path/to/dir', use the .+/render.conf regular
-expression.  Later, `centos-art.sh' script uses this value inside
-^$REGEX\.sh$ expression in order to build the final regular
-expression (i.e., ^.+/render.conf\.sh$) that is evaluated
-against available file paths inside the list of files to process.
+
+
     3.46.3 Usage 
    
+
+
    
+
     `centos-art verify --packages'
    
+
    Verify required packages your workstation needs in order to run the
+`centos-art.sh' script correctly.  If there are missing packages,
+the `centos-art.sh' script asks you to confirm their
+installation. When installing packages, the `centos-art.sh'
+script uses the yum application in order to achieve the
+task.
+
    
+
    In case all packages required by `centos-art.sh' script are
+already installed in your workstation, the message `The required
+packages are already installed.' is output for you to know. 
+
    
+
    
+
     `centos-art verify --links'
    
+
    Verify required links your workstation needs in order to run the
+centos-art command correctly.  If any required link is missing, the
+centos-art.sh script asks you to confirm their installation.
+To install required links, the centos-art.sh script uses the
+ln command.
+
    
+
    In case all links required by `centos-art.sh' script are already
+created in your workstation, the message `The required links are
+already installed.' is output for you to know. 
 
    
-
    Exceptionally, when you provide `--filter='regex'' in the way
-that `regex', appended to `path/to/dir/' (i.e.
-`path/to/dir/regex'), matches a regular file; the
-`centos-art.sh' script uses the file matching as only file in the
-list of files to process. 
+
    In case a regular file exists with the same name of a required link,
+the `centos-art.sh' script outputs the `Already exists as
+regular file.' message when listing required links that will be
+installed. Of course, as there is already a regular file where must be
+a link, no link is created. In such cases the `centos-art.sh'
+script will fall into a continue installation request for that missing
+link.  To end this continue request you can answer `No', or
+remove the existent regular file to let `centos-art.sh' script
+install the link on its place.
 
    
+
    
+
     `centos-art verify --environment'
    
+
     `centos-art verify --environment --filter='regex''
    
+
    Output a brief description of environment variables used by
+`centos-art.sh' script. 
+
    
+
    If `--filter' option is provided, output is reduced as defined in
+the `regex' regular expression value. If `--filter' option
+is specified but `regex' value is not, the `centos-art.sh'
+script outputs information as if `--filter' option had not been
+provided at all.
+
    
+
    
 
-
+
+
 
     3.46.4 See also 
    
 
 
-
-
    3.38 trunk/Scripts/Bash  
+
    3.36 trunk/Scripts/Bash  
 
    3.39 trunk/Scripts/Bash/Functions  
+
    3.37 trunk/Scripts/Bash/Functions  
 
    
 
    
 
 
 
-
-
+
+
-
-
+
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_5.html b/Manuals/en/Html/Repository/repository_5.html
index 9ce7bb1..5a43cbd 100644
--- a/Manuals/en/Html/Repository/repository_5.html
+++ b/Manuals/en/Html/Repository/repository_5.html
@@ -64,14 +64,14 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
    
    
    
    
 [Top]
 [Contents]
-[Index]
+[Index]
 [ ? ]
 
 
@@ -106,7 +106,7 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
 
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_50.html b/Manuals/en/Html/Repository/repository_50.html
index 04575a4..4507809 100644
--- a/Manuals/en/Html/Repository/repository_50.html
+++ b/Manuals/en/Html/Repository/repository_50.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.47 trunk/Scripts/Bash/Functions/Svg
+CentOS Artwork Repository: 3.47 trunk/Scripts/Bash/Locale
 
-
-
+
+
 
 
 
@@ -59,252 +59,69 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
-
-
     3.47 trunk/Scripts/Bash/Functions/Svg 
    
+
+
+
     3.47 trunk/Scripts/Bash/Locale 
    
 
 
-
+
 
     3.47.1 Goals 
    
 
-
    This section exists to organize files related to svg
-functionality of `centos-art.sh' script.
+
    This section exists to organize translation messages and templates
+used by `centos-art.sh' script.
 
    
 
-
+
 
     3.47.2 Description 
    
 
-
    The svg functionality of `centos-art.sh' script helps you
-to maintain scalable vector graphics (SVG) inside repository. For
-example, suppose you've been working in CentOS default design models
-under `trunk/Identity/Themes/Models/', and you want to set common
-metadata to all of them, and later remove all unused SVG defintions
-from `*.svg' files. Doing so file by file may be a tedious task,
-so the `centos-art.sh' script provides the svg
-functionality to aid you maintain such actions.
+
    Translated messages of `centos-art.sh' script are managed using
+GNU gettext utilities. Most translation actions have been
+automated through `centos-art.sh' script "locale" functionality
+(see section trunk/Scripts/Bash/Functions/Locale).
 
    
-
-
-
-
     3.47.2.1 Metadata maintainance 
    
 
-
    The metadata used is defined by Inkscape 0.46 using the SVG standard
-markup. The `centos-art.sh' script replaces everything
-in-between <metadata and </metadata> tags with a
-predefined metadata template we've set for this purpose.
-
    
-
    The metadata template was created using the metadata information of a
-file which, using Inkscape 0.46, all metadata fields were set. This
-created a complete markup representation of how SVG metadata would
-look like. Later, we replaced every single static value with a
-translation marker in the form `=SOMETEXT=', where
-SOMETEXT is the name of its main opening tag. Later, we
-transform the metadata template into a sed replacement set of commads
-escaping new lines at the end of each line.
-
    
-
    With metadata template in place, the `centos-art.sh' script uses
-it to create a metadata template instance for the file being processed
-currently.  The metadata template instance contains the metadata
-portion of sed replacement commands with translation markers already
-traduced.  In this action, instance creation, is where we take
-advantage of automation and generate metadata values like title, date,
-keywords, source, identifier, and relation dynamically, based on the
-file path `centos-art.sh' script is currently creating metadata
-information for.
-
    
-
    With metadata template instance in place, the `centos-art.sh'
-script uses it to replace real values inside all `.svg' files
-under the current location you're running the `centos-art.sh'
-script on.  Default behaviour is to ask user to enter each metadatum
-required, one by one. If user leaves metadatum empty, by pressing
-RET key, `centos-art.sh' uses its default value.
-
    
-
    The `centos-art.sh' script modifies the following metadata:
-
    
-
    
-
     `Title'
    
-
    Name by which this document is formally known. If no value is set
-here, `centos-art.sh' script uses the file name as title.
-
    
-
    
-
     `Date'
    
-
    Date associated with the creation of this document (YYYY-MM-DD). If no
-value is set here, `centos-art.sh' script uses the current date
-information as in date +%Y-%m-%d.
-
    
-
    
-
     `Creator'
    
-
    Name of entity primarily responsible for making the content of this
-document. If no value is set here, `centos-art.sh' script uses
-the string `The CentOS Project'.
-
    
-
    
-
     `Rights'
    
-
    Name of entity with rights to the intellectual Property of this
-document. If no value is set here, `centos-art.sh' script uses
-the string `The CentOS Project'.
-
    
-
    
-
     `Publisher'
    
-
    Name of entity responsible for making this document available. If no
-value is set here, `centos-art.sh' script uses the string
-`The CentOS Project'.
-
    
-
    
-
     `Identifier'
    
-
    Unique URI to reference this document. If no value is set here,
-`centos-art.sh' script uses the current file path to build the
-related url that points to current file location inside repository
-central server.
-
    
-
    
-
     `Source'
    
-
    Unique URI to reference the source of this document. If no value is
-set here, `centos-art.sh' script uses current file path to build
-the related url that points to current file location inside repository
-central server.
-
    
-
    
-
     `Relation'
    
-
    Unique URI to a related document. If no value is set here,
-`centos-art.sh' script uses current file path to build the
-related url that points to current file location inside repository
-central server.
-
    
-
    
-
     `Language'
    
-
    Two-letter language tag with optional subtags for the language of this
-document. (e.g. `en-GB'). If no value is set here,
-`centos-art.sh' script uses the current locale information as in
-cli_getCurrentLocale function.
-
    
-
    
-
     `Keywords'
    
-
    The topic of this document as comma-separated key words, prhases, or
-classifications. If no value is set here, `centos-art.sh' script
-uses file path to build 
-
    
-
    
-
     `Coverage'
    
-
    Extent or scope of this document. If no value is set here,
-`centos-art.sh' script uses the string `The CentOS Project'.
-
    
-
    
-
     `Description'
    
-
    Description about the document. If no value is set here,
-`centos-art.sh' script uses uses empty value as default.
-
    
-
    
-
     `Contributors'
    
-
    People that contributes in the creation/maintainance of the document.
-If no value is set here, `centos-art.sh' script uses uses empty
-value as default.
-
    
-
    
-
-
    The `License' metadatum is not set as a choise, by now. It is
-fixed Creative Common Attribution Share-Alike 3.0 License. This is done in order to
-grant license consistency among all SVG files we manage inside CentOS
-Artwork Repository.
-
    
-
-
-
-
     3.47.2.2 Unused definitions 
    
-
-
    As SVG files grow they may end up with unused definitions inside. For
-example, if you stop using a pattern or gradient, tags used to define
-them are considered unused definitions then. Inkscape 0.46 brings the
-`Vaccum Defs' feature to remove those unused definitions from SVG
-files. The `Vaccum Defs' feature is available both at graphical
-interface and command line interface.
-
    
-
    If you have one or two couple of files, removing unused SVG
-definitions using graphical interface may be enough to you.  In
-contrast, if you have houndred of files to maintain it is not a fun
-task to use the gui interface to remove unused SVG definitions editing
-those files one by one.
-
    
-
    To remove unused SVG definitions from several SVG files, the
-`centos-art.sh' script uses Inkscape's command-line interface,
-specifically with the `--vaccum-defs' option.
-
    
-
-
+
 
     3.47.3 Usage 
    
 
-
    
-
     centos-art svg --update-metadata='path/to/dir'
    
-
     centos-art svg --update-metadata='path/to/dir' --filter='regex'
    
-
    Use these commands to update metadata information to `.svg' files
-under `path/to/dir' directory.
-
    
-
    
-
     centos-art svg --vacuum-defs='path/to/dir'
    
-
     centos-art svg --vacuum-defs='path/to/dir' --filter='regex'
    
-
    Use these commands to remove unused definitions inside `.svg'
-files under `path/to/dir' directory. 
-
    
-
    
-
-
    When you provide `--filter='regex'' argument, the list of files
-to process is reduced as specified in `regex' regular expression.
-Inside `centos-art.sh' script, the `regex' regular
-expression is used in combination with find command to look
-for files matching the regular expression path pattern.
+
    The content of `trunk/Scripts/Bash/Locale' directory should not
+be managed manually. Instead, use the "locale" functionality of
+`centos-art.sh' script.  See section trunk/Scripts/Bash/Functions/Locale, for more information on how to use `centos-art.sh'
+"locale" functionality.
 
    
-
    Warning
    Warning
     In order for `regex' regular expression to match
-a file, the `regex' regular expresion must match the whole file
-path not just the file name. 
-
    
 
-
    For example, if you want to match all `summary.svg' files inside
-`path/to/dir', use the .+/summary regular expression.
-Later, `centos-art.sh' script uses this value inside
-^$REGEX\.svg$ expression in order to build the final regular
-expression (i.e., ^.+/summary\.svg$) that is evaluated against
-available file paths inside the list of files to process.
-
    
-
    Exceptionally, when you provide `--filter='regex'' in the way
-that `regex', appended to `path/to/dir/' (i.e.
-`path/to/dir/regex'), matches a regular file; the
-`centos-art.sh' script uses the file matching as only file in the
-list of files to process. 
-
    
-
-
+
 
     3.47.4 See also 
    
 
 
-
-
    3.38 trunk/Scripts/Bash  
+
    3.37 trunk/Scripts/Bash/Functions  
 
    3.39 trunk/Scripts/Bash/Functions  
+
    3.35 trunk/Scripts  
 
    
 
    
 
 
 
-
-
+
+
-
-
+
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_51.html b/Manuals/en/Html/Repository/repository_51.html
index 73b06b9..e18a749 100644
--- a/Manuals/en/Html/Repository/repository_51.html
+++ b/Manuals/en/Html/Repository/repository_51.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.48 trunk/Scripts/Bash/Functions/Verify
+CentOS Artwork Repository: 3.48 trunk/Scripts/Perl
 
-
-
+
+
 
 
 
@@ -59,272 +59,45 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
-
-
     3.48 trunk/Scripts/Bash/Functions/Verify 
    
-
-
-
-
     3.48.1 Goals 
    
-
-
    This section exists to organize files related to `centos-art.sh'
-script `verify' functionality.  The `verify'
-functionality of `centos-art.sh' script helps you to verify the
-workstation configuration you are planning to use as host for your
-working copy of CentOS Artwork Repository.
-
    
-
-
-
     3.48.2 Description 
    
-
-
    The first time you download CentOS Artwork Repository you need to
-configure your workstation in order to use `centos-art.sh'
-script.  These preliminar configurations are based mainly on auxiliar
-RPM packages installation, symbolic links creations, and environment
-variables definitions.  The `verify' functionality of
-`centos-art.sh' script guides you through this preliminar
-configuration process.  
-
    
-
    If this is the first time you run `centos-art.sh' script, the
-appropriate way to use its `verify' functionality is not using
-the `centos-art.sh' script directly, but the absolute path to
-centos-art.sh script instead (i.e.,
-`~/artwork/trunk/Scripts/Bash/centos-art.sh').  This is necessary
-because `centos-art' symbolic link, under `~/bin/'
-directory, has not been created yet.
-
    
-
+
 
-
     3.48.2.1 Packages 
    
+
     3.48 trunk/Scripts/Perl 
    
 
-
    Installation of auxiliar RPM packages provides the software required
-to manipulate files inside the repository (e.g., image files,
-documentation files, translation files, script files, etc.). Most of
-RPM packages centos-art.sh script uses are shipped with
-CentOS distribution, and can be installed from CentOS base repository.
-The only exception is `inkscape', the package we use to
-manipulate SVG files.  The `inkscape' package is not inside
-CentOS distribution so it needs to be installed from third party
-repositories.
-
    
-
    info
    Note
     Configuration of third party repositories inside CentOS
-distribution is described in CentOS wiki, specifically in the
-following URL:
-http://wiki.centos.org/AdditionalResources/Repositories
-
    
-
-
    Before installing packages, the `centos-art.sh' script uses
-sudo to request root privileges to execute yum's
-installation functionality.  If your user isn't defined as a
-privileged user--at least to run yum commands-- inside
-`/etc/sudoers' configuration file, you will not be able to
-perform package installation tasks as set in `centos-art.sh'
-script `verify' functionality. 
-
    
-
    Setting sudo privileges to users is an administrative task you have to
-do by yourself. If you don't have experience with sudo
-command, please read its man page running the command: man
-sudo. This reading will be very useful, and with some practice, you
-will be able to configure your users to have sudo
-privileges.
-
    
 
 
-
     3.48.2.2 Links 
    
-
-
    Creation of symbolic links helps us to alternate between different
-implementations of `centos-art.sh' script-line (e.g.,
-`centos-art.sh', for Bash implementation; `centos-art.py',
-for Python implementation; `centos-art.pl', for Perl
-implementation; and so on for other implementations). The
-`centos-art.sh' script-line definition takes place inside your
-personal binary (`~/bin/') directory in order to make the script
-implementation --the one that `centos-art' links to-- available
-to PATH environment variable.
-
    
-
    Creation of symbolic links helps us to reuse components from repository
-working copy. For example, color information files maintained inside
-your working copy must never be duplicated inside program-specific
-configuration directories that uses them in your workstation (e.g.,
-Gimp, Inkscape, etc.).  Instead, a symbolic link must be created for
-each one of them, from program-specific configuration directories to
-files in the working copy.  In this configuration, when someone
-commits changes to color information files up to central repository,
-they--the changes committed-- will be immediatly available to your
-programs the next time you update your working copy --the place
-inside your workstation those color information files are stored--.
-
    
-
    Creation of symbolic links helps us to make `centos-art.sh'
-script functionalities available outside `trunk/' repository
-directory structure, but at its same level in repository tree. This is
-useful if you need to use the "render" functionality of
-centos-art.sh under `branches/' repository directory
-structure as you usually do inside `trunk/' repository directory
-structure. As consequence of this configuration, automation scripts
-cannot be branched under `branches/Scripts' directory structure.
-
    
-
-
-
     3.48.2.3 Environment variables 
    
+
     3.48.1 Goals 
    
 
-
    Definition of environemnt variables helps us to set default values to
-our user session life. The user session environment variable defintion
-takes place in the user's `~/.bash_profile' file.  The
-`verify' functionality of `centos-art.sh' script doesn't
-modify your `~/.bash_profile' file.  
-
    
-
    The `verify' functionality of `centos-art.sh' script
-evaluates the following environment variables:
-
    
-
    
-
     EDITOR
    
-
    Default text editor. 
-
    
-
    The `centos-art.sh' script uses default text EDITOR to edit
-pre-commit subversion messages, translation files, configuration
-files, script files, and similar text-based files.
-
    
-
    If EDITOR environment variable is not set, `centos-art.sh'
-script uses `/usr/bin/vim' as default text editor. Otherwise, the
-following values are recognized by `centos-art.sh' script:
-
    
 
      
-
    •  `/usr/bin/vim'
-
    •  `/usr/bin/emacs'
-
    •  `/usr/bin/nano'
+
    •  ...
 
    
 
-
    If no one of these values is set in EDITOR environment variable,
-`centos-art.sh' uses `/usr/bin/vim' text editor by default. 
-
    
-
    
-
     TZ
    
-
    
-
    Default time zone representation.
-
    
-
    Time representation inside repository server is set to Coordinated
-Universal Time (UTC).  Time represetation inside repository working
-copies is set as their administrators personally define.  
-
    
-
    When repository working copies time representation be defined, it
-would be a very good convention to follow if working copies
-administrators would set their systems clock to use UTC.  Otherwise it
-would be difficult for working copies users to find out when changes
-were committed up to repository server exactly in time.
-
    
-
    Info
    Tip
     Coordinated Univeral Time (UTC) representation can be
-configured when you install CentOS distribution; or later, runing the
-system-config-date command at a shell prompt from your
-graphical interface.
-
    
 
-
    info
    Note
     If you set your system clock to use UTC representation,
-you also need to set the TZ environment variable inside
-`~/.bash_profile' as follows:
-
    export TZ=UTC
-
    This is required in order for your terminal to display the correct
-time information of your zone, taking UTC representation as reference.
-
    
-
-
    
-
     TEXTDOMAIN
    
-
    
-
    Default domain used to retrieve translated messages.  This value is
-set in `initFunctions.sh' and shouldn't be changed.
-
    
-
    
-
     TEXTDOMAINDIR
    
-
    
-
    Default directory used to retrieve translated messages. This value is
-set in `initFunctions.sh' and shouldn't be changed.
-
    
-
    
-
     LANG
    
-
    
-
    Default locale information. This value is set when you start your
-session and can be changed using the `locale' functionality of
-`centos-art.sh' script (see section trunk/Scripts/Bash/Functions/Locale, for more information).
-
    
-
    
+
+
     3.48.2 Description 
    
 
 
 
 
     3.48.3 Usage 
    
 
-
    
-
     `centos-art verify --packages'
    
-
    Verify required packages your workstation needs in order to run the
-`centos-art.sh' script correctly.  If there are missing packages,
-the `centos-art.sh' script asks you to confirm their
-installation. When installing packages, the `centos-art.sh'
-script uses the yum application in order to achieve the
-task.
-
    
-
    In case all packages required by `centos-art.sh' script are
-already installed in your workstation, the message `The required
-packages are already installed.' is output for you to know. 
-
    
-
    
-
     `centos-art verify --links'
    
-
    Verify required links your workstation needs in order to run the
-centos-art command correctly.  If any required link is missing, the
-centos-art.sh script asks you to confirm their installation.
-To install required links, the centos-art.sh script uses the
-ln command.
-
    
-
    In case all links required by `centos-art.sh' script are already
-created in your workstation, the message `The required links are
-already installed.' is output for you to know. 
-
    
-
    In case a regular file exists with the same name of a required link,
-the `centos-art.sh' script outputs the `Already exists as
-regular file.' message when listing required links that will be
-installed. Of course, as there is already a regular file where must be
-a link, no link is created. In such cases the `centos-art.sh'
-script will fall into a continue installation request for that missing
-link.  To end this continue request you can answer `No', or
-remove the existent regular file to let `centos-art.sh' script
-install the link on its place.
-
    
-
    
-
     `centos-art verify --environment'
    
-
     `centos-art verify --environment --filter='regex''
    
-
    Output a brief description of environment variables used by
-`centos-art.sh' script. 
-
    
-
    If `--filter' option is provided, output is reduced as defined in
-the `regex' regular expression value. If `--filter' option
-is specified but `regex' value is not, the `centos-art.sh'
-script outputs information as if `--filter' option had not been
-provided at all.
-
    
-
    
-
 
 
 
     3.48.4 See also 
    
 
-
-
-
-
    3.38 trunk/Scripts/Bash  
-
    3.39 trunk/Scripts/Bash/Functions  
-
    
 
 
 
@@ -332,8 +105,8 @@ provided at all.
 
-
-
+
+
    [ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_52.html b/Manuals/en/Html/Repository/repository_52.html
index ecb1b69..ab0ebec 100644
--- a/Manuals/en/Html/Repository/repository_52.html
+++ b/Manuals/en/Html/Repository/repository_52.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.49 trunk/Scripts/Bash/Locale
+CentOS Artwork Repository: 3.49 trunk/Scripts/Python
 
-
-
+
+
 
 
 
@@ -64,55 +64,48 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
    
    
    
    
 [Top]
 [Contents]
-[Index]
+[Index]
 [ ? ]
 
-
+
 
-
     3.49 trunk/Scripts/Bash/Locale 
    
+
     3.49 trunk/Scripts/Python 
    
 
 
 
 
     3.49.1 Goals 
    
 
-
    This section exists to organize translation messages and templates
-used by `centos-art.sh' script.
-
    
+
      
+
    •  ...
+
    
+
 
 
 
     3.49.2 Description 
    
 
-
    Translated messages of `centos-art.sh' script are managed using
-GNU gettext utilities. Most translation actions have been
-automated through `centos-art.sh' script "locale" functionality
-(see section trunk/Scripts/Bash/Functions/Locale).
-
    
+
      
+
    •  ...
+
    
+
 
 
 
     3.49.3 Usage 
    
 
-
    The content of `trunk/Scripts/Bash/Locale' directory should not
-be managed manually. Instead, use the "locale" functionality of
-`centos-art.sh' script.  See section trunk/Scripts/Bash/Functions/Locale, for more information on how to use `centos-art.sh'
-"locale" functionality.
-
    
+
      
+
    •  ...
+
    
+
 
 
 
     3.49.4 See also 
    
 
-
-
-
-
    3.39 trunk/Scripts/Bash/Functions  
-
    3.37 trunk/Scripts  
-
    
 
 
 
@@ -121,7 +114,7 @@ be managed manually. Instead, use the "locale" functionality of
 
-
+
       
 [ << ]
 [ Up ][ >> ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_53.html b/Manuals/en/Html/Repository/repository_53.html
index 74cc37a..78b92f4 100644
--- a/Manuals/en/Html/Repository/repository_53.html
+++ b/Manuals/en/Html/Repository/repository_53.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.50 trunk/Scripts/Perl
+CentOS Artwork Repository: 3.50 trunk/Translations
 
-
-
+
+
 
 
 
@@ -64,49 +64,668 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
    
    
    
    
 [Top]
 [Contents]
-[Index]
+[Index]
 [ ? ]
 
-
+
 
-
     3.50 trunk/Scripts/Perl 
    
+
     3.50 trunk/Translations 
    
 
 
 
 
     3.50.1 Goals 
    
 
+
    The `trunk/Translations' directory exists to:
+
    
 
      
-
    •  ...
+
    •  Organize translation files.
+
    •  Organize translation templates used to produce translation files.
 
    
 
 
 
 
     3.50.2 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 they need to be created for
+different locales. To get an approximate idea of how many files we are
+talking about, consider the followig approximate statistic:
+
    
+
      
+
    •  Inside CentOS distribution, there are around 30 images to
+rebrand.(2)
+
+
    •  There are near to four major releases of CentOS distribution to
+rebrand in parallel development.(3) 
+
+
    •  Each CentOS distribution in parallel development supports more
+than two hundreds locales.(4)
+
    
+
+
    In order to aliviate maintainance of artwork production for such
+environment, we divided artwork production in three production lines:
+
    
+
      
+
    1.  See section trunk/Identity/Themes/Models, to define artworks
+characteristics (e.g., dimensions, position on the screen, etc.).
+
    2.  See section trunk/Identity/Themes/Motifs, to define artworks visual
+styles (e.g., the look and feel).
+
    3.  Translations, to define which major releases and locales
+artworks are produced for. 
+
    
+
+
    Inside CentOS Artwork Repository, the artworks' translation production
+line is stored under `trunk/Translations' directory.
+
    
+
    Inside `trunk/Translations' directory, we use "translation
+entries" to organize artworks' "translation files" and artworks'
+"translation templates".
+
    
 
 
-
     3.50.3 Usage 
    
+
     3.50.2.1 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 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 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 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's 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 Modern's artisitic
+motif, the identity entry for Anaconda progress artwork is:
+
    
+
    trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
+
    
+
    and its translation entry is:
+
    
+
    trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
+
    
+
    Note how the `Translations/' directory prefixes `Identity/'
+directory, also how static values (e.g., Identity, Themes, Distro,
+etc.) in the identity's entry path remain in translation's entry path,
+and how variable values like theme names (e.g., Modern) are stript out
+from translation's 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.
+
    
+
    info
    Note
     Translation entries related to identity entries under
+`trunk/Identity/Themes/Motifs' do not use `Motifs/' in the
+path.  We've done this because `trunk/Identity/Themes/Models'
+structure, the other structure under `trunk/Identity/Themes',
+doesn't require translation paths so far. So in the sake of saving
+characters space when building translation entries for
+`trunk/Identity/Themes/Motifs' structure, we organize Motifs
+translation entries under `trunk/Translations/Identity/Themes/'
+directly. 
+
    
+
    If for some reason `trunk/Identity/Themes/Models' structure
+requires translation entries, we need to re-oraganize the current
+directory structure accordingly.
+
    
+
+
    Translation entries, as described above, can be re-used by similar
+identity entries. For example the following identity entries:
+
    
+
    trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/
+trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Progress/
+trunk/Identity/Themes/Motifs/Mettle/Distro/Anaconda/Progress/
+
    
+
    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).
+
    
 
 
+
     3.50.2.2 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
+centos-art script inisde `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
+
+
    Figure 3.15: The image rendering flow.
+
+
    
+
    Translation markers can be whatever text you want, but as convenction
+we use the following to represent releases of CentOS distribution:
+
    
+
    
+
     `=MINOR_RELEASE='
    
+
    Replace with minor release of CentOS distribution. In the schema M.N, the minor
+release is represented by the N letter.
+
    
+
     `=MAJOR_RELEASE='
    
+
    Replace with major release of CentOS distribution. In the schema M.N,
+the major release is represented by the M letter.
+
    
+
     `=RELEASE='
    
+
    Replace the full release of CentOS distribution. It is
+`=MAJOR_RELEASE=.=MINOR_RELEASE=' basically. 
+
    
+
    
+
+
    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.
+
    
+
+
+
     3.50.2.3 Translation Files 
    
+
+
    Translation files are text files with sed's commands inside,
+replacement commands mainly. As convenction, translation file names
+end in `.sed'. Translation files are used by 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 `splash-small.png' and `firstboot-left.png' as based
+to control its visual style. The `splash-small.png' image
+contains, in its graphic design, the release number information of
+CentOS distribution. So the `splash-small.png' is
+release-specific. In the other hand, the `firstboot-left.png'
+doesn't contain release number information. So the
+`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. 
+
    
+
    info
    Note
     The monolithic visual identity is implemented using
+theme models (see section trunk/Identity/Themes/Models) and artistic
+motifs (see section trunk/Identity/Themes/Motifs).
+
    
+
+
    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:
+
    
+
    trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/
+|-- Tpl
+|   `-- splash-small.sed
+`-- firstboot-left.sed
+
    
+
    With the translation entry above, centos-art command is able
+to produce the image `firstboot-left.png' only. To produce
+`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 centos-art script as following:
+
    
+
    centos-art render --entry=/home/centos/artwork/trunk/Translations/Identity/Themes/BootUp/Firstboot --filter='3,4,5,6'
+
    
+
    The above command produces the following translation entiry:
+
    
+
    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
+
    
+
    At this point 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 `--filter='release-number'' argument.
+
    
+
+
+
     3.50.2.4 Template Translation Files 
    
+
+
    Template translation files are translation files stored inside
+translation template directory. Template translation files are used by
+centos-art script to produce specific translation files
+only. Template translation files may be empty or contain
+sed's 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:
+
    
+
    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
+
    
+
    In the above exmaple, the `splash-small.sed' file is a template
+translation file and looks like:
+
    
+
    # -------------------------------------
+# $Id: splash-small.sed 94 2010-09-18 10:59:42Z al $
+# -------------------------------------
+
    
+
    In the above template translation file there are three comments lines,
+but when you render it, the centos-art adds the
+release-specific replacement commands. In our Firstboot example, after
+rendering Firstboot translation entry, the `splash-small.sed'
+translation file specific to CentOS 5, looks like the following:
+
    
+
    # 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
+
    
+
    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:
+
    
+
    trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/
+`-- Tpl
+    `-- en
+        `-- 01-welcome.sed
+
    
+
    and if we render translation files for CentOS 4 and CentOS 5 major
+releases, the translation entry would look like the following:
+
    
+
    trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/
+|-- 4
+|   `-- en
+|       `-- 01-welcome.sed
+|-- 5
+|   `-- en
+|       `-- 01-welcome.sed
+`-- Tpl
+    `-- en
+        `-- 01-welcome.sed
+
    
+
    info
    Note
     Release-specific translation directories preserve
+template translation directory structure and file names.
+
    
+
+
    In the example above, the template translation file looks like the
+following:
+
    
+
    # ------------------------------------------------------------
+# $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/!
+
    
+
    and, after render the translation entry, specific translation files
+look like the following:
+
    
+
    # 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
+
    
+
    In the example above, relevant lines begin with the `s' word
+followed by a separation character (e.g., `/', `!', etc.).
+These lines have the following format:
+
    
+
    s/REGEXP/REPLACEMENT/FLAGS
+
    
+
    The `/' characters may be uniformly replaced by any other single
+character within any given s command.  The `/'
+character (or whatever other character is used in its stead) can
+appear in the REGEXP or REPLACEMENT only if it is preceded by a
+`\' character.
+
    
+
    The s command is probably the most important in
+sed and has a lot of different options.  Its basic concept
+is simple: the 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 `g' command to apply the
+replacements globally.
+
    
+
    Info
    Tip
     More information about how to use sed's
+replacement commands and flags is available in sed's
+documentation manual. To read sed's documentation manual type the
+following command: 
+
    info sed
+
    
+
+
    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 after its definition. For example, see in the
+release-specific translation file above, how the
+`s!=MAJOR_RELASE=!5!g' replacement command is defined
+after `=MAJOR_RELASE=' translation marker definition in
+the REPLACEMENT of `=TITLE=' translation marker replacement
+command.
+
    
+
+
+
     3.50.2.5 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:
+
    
+
    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.
+
    
+
+
+
     3.50.2.6 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 centos-art
+script.
+
    
+
    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
+
    
+
+
+
     3.50.2.7 Translation Rendering 
    
+
+
    When rendering translations, the centos-art script checks
+the translation entry to verify that it has a translation template
+directory inside. The translation template directory (`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 centos-art script outputs a message and quits
+script execution.
+
    
+
+
+
     3.50.2.8 Translation (Pre-)Rendering Configuration Scripts 
    
+
+
    When the 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's default functionality (described below). 
+
    
+
    Translation pre-rendering configuration scripts are stored under
+`trunk/Scripts' directory, specifically under the appropriate
+language implementation. If you are using centos-art Bash's
+implementation, the translation pre-rendering scripts are store in the
+`trunk/Scripts/Bash/Config' location; if you are using
+centos-art Python's implementation, then translation
+pre-rendering scripts are stored in the
+`trunk/Scripts/Python/Config' location, and so on for other
+implementations.
+
    
+
    Bash's translation pre-rendering configuration scripts look like the
+following:
+
    
+
    #!/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 {
+...
+}
+
    
+
    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
+centos-art Bash's implementation, and you are rendering
+translations for CentOS brands, in this situation the translation
+entry would be:
+
    
+
    trunk/Translations/Identity/Brands
+
    
+
    and the entry inside the translation pre-rendering configuration
+structure would be:
+
    
+
    trunk/Scripts/Bash/Config/Identity/Brands
+
    
+
    Once the centos-art script detects that translation
+pre-rendering configuration directory exists, the 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.
+
    
+
    info
    Note
     Translation pre-rendering configuration files have the
+following form:
+
    render.conf.extension
+
    where `extension' refers the programming language implementation
+you are using. For example, `sh' for Bash's, `py' for
+Python's, `pl' for Perl's, and so on for other implementations.
+
    
+
+
    As we are using Bash implementation to describe the translation
+pre-rendering configuration example, the translation pre-rendering
+configuration file that centos-art looks for, inside the
+above translation pre-rendering configuration directory, is
+`render.conf.sh'.
+
    
+
+
+
     3.50.2.9 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
+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 `--filter='release-number'' argument and
+produces release-specific directories. As part of template translation
+duplication process take place, the centos-art script adds
+release-specific replacement commands to each specific translation
+file inside release-specific directories. As result, specific
+translation files, inside release-specific directories, contain
+template translation replacement commands plus,
+release-specific replacement commands.
+
    
+
    info
    Note
     Release-specific replacement commands are standardized
+inside centos-art script using predifined release
+translation markers. Release translation markers are described in the
+translation marker section
+(see Translation Markers).
+
    
+
+
+
+
+
     3.50.3 Usage 
    
+
+
    
+
     `centos-art render --entry='path/to/dir'' 
    
+
    
+
    When `path/to/dir' refers one directory under
+`trunk/Translations', this command orverwrites available
+translation files using translation templates.
+
    
+
    
+
     `centos-art render --entry='path/to/dir' --filter='pattern'' 
    
+
    
+
    When `path/to/dir' refers one directory under
+`trunk/Translations', this command renders release-specific
+translation files as you specify in the `--filter='pattern''
+argument. In this case, `pattern' not a regular expression but an
+number (e.g., `5') or a list of numbers separated by commas
+(e.g., `3,4,5,6') that specify the major release of CentOS
+distribution you want to render translations for.  
+
    
+
    
+
+
+
 
     3.50.4 See also 
    
 
+
+
+
+
+
+
+
+
    3.52 trunk/Translations/Identity/Brands  
+
    3.54 trunk/Translations/Identity/Fonts  
+
    3.55 trunk/Translations/Identity/Models  
+
    3.56 trunk/Translations/Identity/Release  
+
    3.57 trunk/Translations/Identity/Themes  
+
    3.1 trunk/Identity  
+
    
 
 
 
-
-
+
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_54.html b/Manuals/en/Html/Repository/repository_54.html
index 8e496dd..5ab8d1d 100644
--- a/Manuals/en/Html/Repository/repository_54.html
+++ b/Manuals/en/Html/Repository/repository_54.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.51 trunk/Scripts/Python
+CentOS Artwork Repository: 3.51 trunk/Translations/Identity
 
-
-
+
+
 
 
 
@@ -59,27 +59,27 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
-
-
     3.51 trunk/Scripts/Python 
    
+
+
+
     3.51 trunk/Translations/Identity 
    
 
 
-
+
 
     3.51.1 Goals 
    
 
 
      
@@ -87,7 +87,7 @@ ul.toc {list-style: none}
 
    
 
 
-
+
 
     3.51.2 Description 
    
 
 
      
@@ -95,7 +95,7 @@ ul.toc {list-style: none}
 
    
 
 
-
+
 
     3.51.3 Usage 
    
 
 
      
@@ -103,18 +103,34 @@ ul.toc {list-style: none}
 
    
 
 
-
+
 
     3.51.4 See also 
    
 
+
+
+
+
+
+
+
+
+
    3.52 trunk/Translations/Identity/Brands  
+
    3.54 trunk/Translations/Identity/Fonts  
+
    3.55 trunk/Translations/Identity/Models  
+
    3.56 trunk/Translations/Identity/Release  
+
    3.57 trunk/Translations/Identity/Themes  
+
    3.60 trunk/Translations/Identity/Widgets  
+
    3.1 trunk/Identity  
+
    
 
 
 
-
-
+
+
-
-
+
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_55.html b/Manuals/en/Html/Repository/repository_55.html
index 5e94d62..1427f42 100644
--- a/Manuals/en/Html/Repository/repository_55.html
+++ b/Manuals/en/Html/Repository/repository_55.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.52 trunk/Translations
+CentOS Artwork Repository: 3.52 trunk/Translations/Identity/Brands
 
-
-
+
+
 
 
 
@@ -59,673 +59,148 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
-
-
     3.52 trunk/Translations 
    
+
+
+
     3.52 trunk/Translations/Identity/Brands 
    
 
 
-
+
 
     3.52.1 Goals 
    
 
-
    The `trunk/Translations' directory exists to:
-
    
 
      
-
    •  Organize translation files.
-
    •  Organize translation templates used to produce translation files.
+
    •  Organize brands' translation files.
 
    
 
 
-
+
 
     3.52.2 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 they need to be created for
-different locales. To get an approximate idea of how many files we are
-talking about, consider the followig approximate statistic:
-
    
-
      
-
    •  Inside CentOS distribution, there are around 30 images to
-rebrand.(2)
-
-
    •  There are near to four major releases of CentOS distribution to
-rebrand in parallel development.(3) 
-
-
    •  Each CentOS distribution in parallel development supports more
-than two hundreds locales.(4)
-
    
-
-
    In order to aliviate maintainance of artwork production for such
-environment, we divided artwork production in three production lines:
-
    
-
      
-
    1.  See section trunk/Identity/Themes/Models, to define artworks
-characteristics (e.g., dimensions, position on the screen, etc.).
-
    2.  See section trunk/Identity/Themes/Motifs, to define artworks visual
-styles (e.g., the look and feel).
-
    3.  Translations, to define which major releases and locales
-artworks are produced for. 
-
    
-
-
    Inside CentOS Artwork Repository, the artworks' translation production
-line is stored under `trunk/Translations' directory.
-
    
-
    Inside `trunk/Translations' directory, we use "translation
-entries" to organize artworks' "translation files" and artworks'
-"translation templates".
-
    
-
-
-
     3.52.2.1 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 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 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 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's 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 Modern's artisitic
-motif, the identity entry for Anaconda progress artwork is:
-
    
-
    trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
-
    
-
    and its translation entry is:
-
    
-
    trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
-
    
-
    Note how the `Translations/' directory prefixes `Identity/'
-directory, also how static values (e.g., Identity, Themes, Distro,
-etc.) in the identity's entry path remain in translation's entry path,
-and how variable values like theme names (e.g., Modern) are stript out
-from translation's 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.
-
    
-
    info
    Note
     Translation entries related to identity entries under
-`trunk/Identity/Themes/Motifs' do not use `Motifs/' in the
-path.  We've done this because `trunk/Identity/Themes/Models'
-structure, the other structure under `trunk/Identity/Themes',
-doesn't require translation paths so far. So in the sake of saving
-characters space when building translation entries for
-`trunk/Identity/Themes/Motifs' structure, we organize Motifs
-translation entries under `trunk/Translations/Identity/Themes/'
-directly. 
-
    
-
    If for some reason `trunk/Identity/Themes/Models' structure
-requires translation entries, we need to re-oraganize the current
-directory structure accordingly.
-
    
-
-
    Translation entries, as described above, can be re-used by similar
-identity entries. For example the following identity entries:
-
    
-
    trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/
-trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Progress/
-trunk/Identity/Themes/Motifs/Mettle/Distro/Anaconda/Progress/
-
    
-
    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).
-
    
-
-
-
     3.52.2.2 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
-centos-art script inisde `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
-
-
    Figure 3.15: The image rendering flow.
-
-
    
-
    Translation markers can be whatever text you want, but as convenction
-we use the following to represent releases of CentOS distribution:
-
    
-
    
-
     `=MINOR_RELEASE='
    
-
    Replace with minor release of CentOS distribution. In the schema M.N, the minor
-release is represented by the N letter.
-
    
-
     `=MAJOR_RELEASE='
    
-
    Replace with major release of CentOS distribution. In the schema M.N,
-the major release is represented by the M letter.
-
    
-
     `=RELEASE='
    
-
    Replace the full release of CentOS distribution. It is
-`=MAJOR_RELEASE=.=MINOR_RELEASE=' basically. 
-
    
-
    
-
-
    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.
-
    
-
-
-
     3.52.2.3 Translation Files 
    
-
-
    Translation files are text files with sed's commands inside,
-replacement commands mainly. As convenction, translation file names
-end in `.sed'. Translation files are used by 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 `splash-small.png' and `firstboot-left.png' as based
-to control its visual style. The `splash-small.png' image
-contains, in its graphic design, the release number information of
-CentOS distribution. So the `splash-small.png' is
-release-specific. In the other hand, the `firstboot-left.png'
-doesn't contain release number information. So the
-`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. 
-
    
-
    info
    Note
     The monolithic visual identity is implemented using
-theme models (see section trunk/Identity/Themes/Models) and artistic
-motifs (see section trunk/Identity/Themes/Motifs).
-
    
-
-
    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:
-
    
-
    trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/
-|-- Tpl
-|   `-- splash-small.sed
-`-- firstboot-left.sed
-
    
-
    With the translation entry above, centos-art command is able
-to produce the image `firstboot-left.png' only. To produce
-`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 centos-art script as following:
-
    
-
    centos-art render --entry=/home/centos/artwork/trunk/Translations/Identity/Themes/BootUp/Firstboot --filter='3,4,5,6'
-
    
-
    The above command produces the following translation entiry:
-
    
-
    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
-
    
-
    At this point 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 `--filter='release-number'' argument.
-
    
-
-
-
     3.52.2.4 Template Translation Files 
    
-
-
    Template translation files are translation files stored inside
-translation template directory. Template translation files are used by
-centos-art script to produce specific translation files
-only. Template translation files may be empty or contain
-sed's 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:
-
    
-
    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
-
    
-
    In the above exmaple, the `splash-small.sed' file is a template
-translation file and looks like:
-
    
-
    # -------------------------------------
-# $Id: splash-small.sed 94 2010-09-18 10:59:42Z al $
-# -------------------------------------
-
    
-
    In the above template translation file there are three comments lines,
-but when you render it, the centos-art adds the
-release-specific replacement commands. In our Firstboot example, after
-rendering Firstboot translation entry, the `splash-small.sed'
-translation file specific to CentOS 5, looks like the following:
-
    
-
    # 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
-
    
-
    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:
-
    
-
    trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/
-`-- Tpl
-    `-- en
-        `-- 01-welcome.sed
-
    
-
    and if we render translation files for CentOS 4 and CentOS 5 major
-releases, the translation entry would look like the following:
-
    
-
    trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/
-|-- 4
-|   `-- en
-|       `-- 01-welcome.sed
-|-- 5
-|   `-- en
-|       `-- 01-welcome.sed
-`-- Tpl
-    `-- en
-        `-- 01-welcome.sed
-
    
-
    info
    Note
     Release-specific translation directories preserve
-template translation directory structure and file names.
-
    
-
-
    In the example above, the template translation file looks like the
-following:
-
    
-
    # ------------------------------------------------------------
-# $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/!
-
    
-
    and, after render the translation entry, specific translation files
-look like the following:
-
    
-
    # 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
-
    
-
    In the example above, relevant lines begin with the `s' word
-followed by a separation character (e.g., `/', `!', etc.).
-These lines have the following format:
+
    Translation files, inside `trunk/Translations/Identity/Brands'
+translation entry, don't use default rendering translation
+functionality, they use the following translation pre-rendering
+configuration file instead:
 
    
-
    s/REGEXP/REPLACEMENT/FLAGS
+
    /home/centos/artwork/trunk/Translation/Identity/Brands/render.conf.sh
 
    
-
    The `/' characters may be uniformly replaced by any other single
-character within any given s command.  The `/'
-character (or whatever other character is used in its stead) can
-appear in the REGEXP or REPLACEMENT only if it is preceded by a
-`\' character.
-
    
-
    The s command is probably the most important in
-sed and has a lot of different options.  Its basic concept
-is simple: the 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 `g' command to apply the
-replacements globally.
+
    Inside `trunk/Translations/Identity/Brands' translation entry,
+translation files are symbolic links pointing to the common template
+translation structure, inside the translation template (`Tpl/')
+directory.
 
    
-
    Info
    Tip
     More information about how to use sed's
-replacement commands and flags is available in sed's
-documentation manual. To read sed's documentation manual type the
-following command: 
-
    info sed
-
    
-
-
    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 after its definition. For example, see in the
-release-specific translation file above, how the
-`s!=MAJOR_RELASE=!5!g' replacement command is defined
-after `=MAJOR_RELASE=' translation marker definition in
-the REPLACEMENT of `=TITLE=' translation marker replacement
-command.
+
    Inside `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 (`Tpl/') directory
+structure applies to each single design template available.
 
    
-
-
-
     3.52.2.5 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. 
+
    For example, if the brands' translation template (`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
+centos-art script considers translation symbolic links as
+translation files.
 
    
-
    Translation entries, with common translation files inside, look like
-the following:
+
    Translation file names, inside brands' translation template
+(`Tpl') directory have special meaning:
 
    
-
    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.
-
    
 
-
-
     3.52.2.6 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 centos-art
-script.
-
    
-
    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
-
    
-
-
-
     3.52.2.7 Translation Rendering 
    
+
+
     3.52.2.1 Conventional file names 
    
 
-
    When rendering translations, the centos-art script checks
-the translation entry to verify that it has a translation template
-directory inside. The translation template directory (`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 centos-art script outputs a message and quits
-script execution.
+
    Convenctional file names look like `blue.sed', `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.
 
    
 
-
-
     3.52.2.8 Translation (Pre-)Rendering Configuration Scripts 
    
-
-
    When the 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's default functionality (described below). 
-
    
-
    Translation pre-rendering configuration scripts are stored under
-`trunk/Scripts' directory, specifically under the appropriate
-language implementation. If you are using centos-art Bash's
-implementation, the translation pre-rendering scripts are store in the
-`trunk/Scripts/Bash/Config' location; if you are using
-centos-art Python's implementation, then translation
-pre-rendering scripts are stored in the
-`trunk/Scripts/Python/Config' location, and so on for other
-implementations.
-
    
-
    Bash's translation pre-rendering configuration scripts look like the
-following:
-
    
-
    #!/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 $
-# ----------------------------------------------------------------------
+
+
     3.52.2.2 Numeric file names 
    
 
-function render_loadConfig {
-...
-}
-
    
-
    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
-centos-art Bash's implementation, and you are rendering
-translations for CentOS brands, in this situation the translation
-entry would be:
+
    Numeric file names look like `300.sed', `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 `width' defined by the
+number part of the translation file name. The image `height' is
+automatically scaled based on the previous `width' definition to
+maintain the design's ratio.  
 
    
-
    trunk/Translations/Identity/Brands
-
    
-
    and the entry inside the translation pre-rendering configuration
-structure would be:
+
    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.
 
    
-
    trunk/Scripts/Bash/Config/Identity/Brands
-
    
-
    Once the centos-art script detects that translation
-pre-rendering configuration directory exists, the 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.
-
    
-
    info
    Note
     Translation pre-rendering configuration files have the
-following form:
-
    render.conf.extension
-
    where `extension' refers the programming language implementation
-you are using. For example, `sh' for Bash's, `py' for
-Python's, `pl' for Perl's, and so on for other implementations.
-
    
-
-
    As we are using Bash implementation to describe the translation
-pre-rendering configuration example, the translation pre-rendering
-configuration file that centos-art looks for, inside the
-above translation pre-rendering configuration directory, is
-`render.conf.sh'.
+
    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.
 
    
 
-
-
     3.52.2.9 Translation Rendering Default Functionality 
    
+
+
     3.52.2.3 Translation markers 
    
 
-
    In the other hand, if the translation pre-rendering configuration file
-doesn't exist, or it isn't written as function script, the
-centos-art script ignore translation pre-rendering
-configuration functionality and passes to render translation using
-default functionality instead.
+
    Inside `trunk/Translations/Identity/Brands/', translation files
+combine the following translation markers:
 
    
-
    The translation rendering default functionality takes template
-translation directory structure, duplicates it for each release number
-specified in the `--filter='release-number'' argument and
-produces release-specific directories. As part of template translation
-duplication process take place, the centos-art script adds
-release-specific replacement commands to each specific translation
-file inside release-specific directories. As result, specific
-translation files, inside release-specific directories, contain
-template translation replacement commands plus,
-release-specific replacement commands.
+
    
+
     `#000000'
    
+
    
+
    Specify which color to use when rendering brand images.
 
    
-
    info
    Note
     Release-specific replacement commands are standardized
-inside centos-art script using predifined release
-translation markers. Release translation markers are described in the
-translation marker section
-(see Translation Markers).
+
    info
    Note
     As translation files inside
+`trunk/Translations/Identity/Brands' are symbolic links that
+point to template translation files, translation markers are defined
+inside template translation files.
 
    
+
    
+
    
 
 
-
-
+
 
     3.52.3 Usage 
    
 
-
    
-
     `centos-art render --entry='path/to/dir'' 
    
-
    
-
    When `path/to/dir' refers one directory under
-`trunk/Translations', this command orverwrites available
-translation files using translation templates.
+
    To render brands' translation files, use the following command:
 
    
-
    
-
     `centos-art render --entry='path/to/dir' --filter='pattern'' 
    
-
    
-
    When `path/to/dir' refers one directory under
-`trunk/Translations', this command renders release-specific
-translation files as you specify in the `--filter='pattern''
-argument. In this case, `pattern' not a regular expression but an
-number (e.g., `5') or a list of numbers separated by commas
-(e.g., `3,4,5,6') that specify the major release of CentOS
-distribution you want to render translations for.  
-
    
-
    
-
+
    centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands
+
    
 
-
+
 
     3.52.4 See also 
    
 
 
-
-
-
-
-
-
    3.54 trunk/Translations/Identity/Brands  
-
    3.56 trunk/Translations/Identity/Fonts  
-
    3.57 trunk/Translations/Identity/Models  
-
    3.58 trunk/Translations/Identity/Release  
-
    3.59 trunk/Translations/Identity/Themes  
+
    3.53 trunk/Translations/Identity/Brands/Tpl  
 
    3.1 trunk/Identity  
+
    3.2 trunk/Identity/Brands  
 
    
 
    
 
 
 
-
-
+
+
-
-
+
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_56.html b/Manuals/en/Html/Repository/repository_56.html
index 892223c..5c82383 100644
--- a/Manuals/en/Html/Repository/repository_56.html
+++ b/Manuals/en/Html/Repository/repository_56.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.53 trunk/Translations/Identity
+CentOS Artwork Repository: 3.53 trunk/Translations/Identity/Brands/Tpl
 
-
-
+
+
 
 
 
@@ -59,78 +59,50 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
-
-
     3.53 trunk/Translations/Identity 
    
+
+
+
     3.53 trunk/Translations/Identity/Brands/Tpl 
    
 
 
-
+
 
     3.53.1 Goals 
    
 
-
      
-
    •  ...
-
    
 
-
-
+
 
     3.53.2 Description 
    
 
-
      
-
    •  ...
-
    
-
 
-
+
 
     3.53.3 Usage 
    
 
-
      
-
    •  ...
-
    
-
 
-
+
 
     3.53.4 See also 
    
 
-
-
-
-
-
-
-
-
-
    3.54 trunk/Translations/Identity/Brands  
-
    3.56 trunk/Translations/Identity/Fonts  
-
    3.57 trunk/Translations/Identity/Models  
-
    3.58 trunk/Translations/Identity/Release  
-
    3.59 trunk/Translations/Identity/Themes  
-
    3.62 trunk/Translations/Identity/Widgets  
-
    3.1 trunk/Identity  
-
    
 
 
 
-
-
+
+
-
-
+
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_57.html b/Manuals/en/Html/Repository/repository_57.html
index aa4dcb5..fb2a47e 100644
--- a/Manuals/en/Html/Repository/repository_57.html
+++ b/Manuals/en/Html/Repository/repository_57.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.54 trunk/Translations/Identity/Brands
+CentOS Artwork Repository: 3.54 trunk/Translations/Identity/Fonts
 
-
-
+
+
 
 
 
@@ -59,148 +59,104 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
-
-
     3.54 trunk/Translations/Identity/Brands 
    
+
+
+
     3.54 trunk/Translations/Identity/Fonts 
    
 
 
-
+
 
     3.54.1 Goals 
    
 
-
      
-
    •  Organize brands' translation files.
-
    
-
-
-
+
    This section exists to organize fonts translation files.
+
    
+
 
     3.54.2 Description 
    
 
-
    Translation files, inside `trunk/Translations/Identity/Brands'
-translation entry, don't use default rendering translation
-functionality, they use the following translation pre-rendering
-configuration file instead:
+
    Translation files, inside `trunk/Translations/Fonts', have the
+following structure:
 
    
-
    /home/centos/artwork/trunk/Translation/Identity/Brands/render.conf.sh
+
    s!font-family:Denmark!font-family:DejaVu LGC Sans!
+s!font-weight:normal!font-weight:bold!
+s!font-style:normal!font-style:italic!
 
    
-
    Inside `trunk/Translations/Identity/Brands' translation entry,
-translation files are symbolic links pointing to the common template
-translation structure, inside the translation template (`Tpl/')
-directory.
-
    
-
    Inside `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 (`Tpl/') directory
-structure applies to each single design template available.
+
    Inside `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.
 
    
-
    For example, if the brands' translation template (`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
-centos-art script considers translation symbolic links as
-translation files.
-
    
-
    Translation file names, inside brands' translation template
-(`Tpl') directory have special meaning:
-
    
-
-
-
     3.54.2.1 Conventional file names 
    
+
    Important
    Important
     Do not create translation files for font-families
+not used somewhere inside CentOS visual identity. The font's identity
+entry (see section trunk/Identity/Fonts) is used as reference when someone
+needs to know which font-families are allowed to use inside CentOS
+visual identity.
+
    
 
-
    Convenctional file names look like `blue.sed', `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.
-
    
 
-
-
     3.54.2.2 Numeric file names 
    
-
-
    Numeric file names look like `300.sed', `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 `width' defined by the
-number part of the translation file name. The image `height' is
-automatically scaled based on the previous `width' definition to
-maintain the design's 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.
-
    
-
-
-
     3.54.2.3 Translation markers 
    
+
+
     3.54.2.1 Translation Markers 
    
 
-
    Inside `trunk/Translations/Identity/Brands/', translation files
+
    Inside `trunk/Translations/Identity/Fonts', translation files
 combine the following translation markers:
 
    
 
    
-
     `#000000'
    
-
    
-
    Specify which color to use when rendering brand images.
-
    
-
    info
    Note
     As translation files inside
-`trunk/Translations/Identity/Brands' are symbolic links that
-point to template translation files, translation markers are defined
-inside template translation files.
-
    
-
    
+
     `font-family:Denmark'
    
+
    Specify which font family to use when rendering font preview images.
+
    
+
     `font-weight:normal'
    
+
    Specify which font weight to use when rendering font preview images.
+
    
+
     `font-style:normal'
    
+
    Specify which font style to use when rendering font preview images.
+
    
 
    
 
 
-
+
 
     3.54.3 Usage 
    
 
-
    To render brands' translation files, use the following command:
+
    Inside `trunk/Translations/Fonts' you use your favorite text
+editor to create translation files.  Inside
+`trunk/Translations/Fonts' there is not translation template
+directory (`Tpl/'), nor translation rendering using
+centos-art script.  For example, to create the
+`dejavu_lgc_sans-boldoblique.sed' translation file using
+vim editor, type the following command:
 
    
-
    centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands
+
    vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed
 
    
 
-
+
 
     3.54.4 See also 
    
 
 
-
-
    3.55 trunk/Translations/Identity/Brands/Tpl  
-
    3.2 trunk/Identity/Brands  
+
    3.3 trunk/Identity/Fonts  
 
    
 
    
 
 
+
 
-
-
+
+
-
-
+
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_58.html b/Manuals/en/Html/Repository/repository_58.html
index b039214..405c345 100644
--- a/Manuals/en/Html/Repository/repository_58.html
+++ b/Manuals/en/Html/Repository/repository_58.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.55 trunk/Translations/Identity/Brands/Tpl
+CentOS Artwork Repository: 3.55 trunk/Translations/Identity/Models
 
-
-
+
+
 
 
 
@@ -59,50 +59,50 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
-
-
     3.55 trunk/Translations/Identity/Brands/Tpl 
    
+
+
+
     3.55 trunk/Translations/Identity/Models 
    
 
 
-
+
 
     3.55.1 Goals 
    
 
 
-
+
 
     3.55.2 Description 
    
 
 
-
+
 
     3.55.3 Usage 
    
 
 
-
+
 
     3.55.4 See also 
    
 
 
 
 
-
-
+
+
-
-
+
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_59.html b/Manuals/en/Html/Repository/repository_59.html
index c4387c2..9e23aef 100644
--- a/Manuals/en/Html/Repository/repository_59.html
+++ b/Manuals/en/Html/Repository/repository_59.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.56 trunk/Translations/Identity/Fonts
+CentOS Artwork Repository: 3.56 trunk/Translations/Identity/Release
 
-
-
+
+
 
 
 
@@ -59,95 +59,41 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
-
-
     3.56 trunk/Translations/Identity/Fonts 
    
-
-
+
 
-
     3.56.1 Goals 
    
+
     3.56 trunk/Translations/Identity/Release 
    
 
-
    This section exists to organize fonts translation files.
-
    
-
-
     3.56.2 Description 
    
 
-
    Translation files, inside `trunk/Translations/Fonts', have the
-following structure:
-
    
-
    s!font-family:Denmark!font-family:DejaVu LGC Sans!
-s!font-weight:normal!font-weight:bold!
-s!font-style:normal!font-style:italic!
-
    
-
    Inside `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.
-
    
-
    Important
    Important
     Do not create translation files for font-families
-not used somewhere inside CentOS visual identity. The font's identity
-entry (see section trunk/Identity/Fonts) is used as reference when someone
-needs to know which font-families are allowed to use inside CentOS
-visual identity.
-
    
+
+
     3.56.1 Goals 
    
 
 
 
-
     3.56.2.1 Translation Markers 
    
-
-
    Inside `trunk/Translations/Identity/Fonts', translation files
-combine the following translation markers:
-
    
-
    
-
     `font-family:Denmark'
    
-
    Specify which font family to use when rendering font preview images.
-
    
-
     `font-weight:normal'
    
-
    Specify which font weight to use when rendering font preview images.
-
    
-
     `font-style:normal'
    
-
    Specify which font style to use when rendering font preview images.
-
    
-
    
+
     3.56.2 Description 
    
 
 
 
 
     3.56.3 Usage 
    
 
-
    Inside `trunk/Translations/Fonts' you use your favorite text
-editor to create translation files.  Inside
-`trunk/Translations/Fonts' there is not translation template
-directory (`Tpl/'), nor translation rendering using
-centos-art script.  For example, to create the
-`dejavu_lgc_sans-boldoblique.sed' translation file using
-vim editor, type the following command:
-
    
-
    vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed
-
    
 
 
 
     3.56.4 See also 
    
 
-
-
-
    3.3 trunk/Identity/Fonts  
-
    
-
 
 
 
@@ -155,8 +101,8 @@ directory (`Tpl/'), nor translation rendering using
 
-
-
+
+
    [ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_6.html b/Manuals/en/Html/Repository/repository_6.html
index a2eaeee..9d74e32 100644
--- a/Manuals/en/Html/Repository/repository_6.html
+++ b/Manuals/en/Html/Repository/repository_6.html
@@ -64,14 +64,14 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
    
    
    
    
 [Top]
 [Contents]
-[Index]
+[Index]
 [ ? ]
 
 
@@ -190,7 +190,7 @@ improve this section with your reasons.
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
 
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_60.html b/Manuals/en/Html/Repository/repository_60.html
index d852f10..9c0f108 100644
--- a/Manuals/en/Html/Repository/repository_60.html
+++ b/Manuals/en/Html/Repository/repository_60.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.57 trunk/Translations/Identity/Models
+CentOS Artwork Repository: 3.57 trunk/Translations/Identity/Themes
 
-
-
+
+
 
 
 
@@ -64,19 +64,19 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
    
    
    
    
 [Top]
 [Contents]
-[Index]
+[Index]
 [ ? ]
 
-
+
 
-
     3.57 trunk/Translations/Identity/Models 
    
+
     3.57 trunk/Translations/Identity/Themes 
    
 
 
 
@@ -102,7 +102,7 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
 
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_61.html b/Manuals/en/Html/Repository/repository_61.html
index 9fc90d5..550e945 100644
--- a/Manuals/en/Html/Repository/repository_61.html
+++ b/Manuals/en/Html/Repository/repository_61.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.58 trunk/Translations/Identity/Release
+CentOS Artwork Repository: 3.58 trunk/Translations/Identity/Themes/Backgrounds
 
-
-
+
+
 
 
 
@@ -64,32 +64,44 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
    
    
    
    
 [Top]
 [Contents]
-[Index]
+[Index]
 [ ? ]
 
-
+
 
-
     3.58 trunk/Translations/Identity/Release 
    
+
     3.58 trunk/Translations/Identity/Themes/Backgrounds 
    
 
 
 
 
     3.58.1 Goals 
    
 
+
      
+
    •  ...
+
    
+
 
 
 
     3.58.2 Description 
    
 
+
      
+
    •  ...
+
    
+
 
 
 
     3.58.3 Usage 
    
 
+
      
+
    •  ...
+
    
+
 
 
 
     3.58.4 See also 
    
@@ -102,7 +114,7 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
 
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_62.html b/Manuals/en/Html/Repository/repository_62.html
index 153850b..3178ac8 100644
--- a/Manuals/en/Html/Repository/repository_62.html
+++ b/Manuals/en/Html/Repository/repository_62.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.59 trunk/Translations/Identity/Themes
+CentOS Artwork Repository: 3.59 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
 
-
-
+
+
 
 
 
@@ -64,45 +64,125 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
    
    
    
    
 [Top]
 [Contents]
-[Index]
+[Index]
 [ ? ]
 
-
+
 
-
     3.59 trunk/Translations/Identity/Themes 
    
+
     3.59 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress 
    
 
 
 
 
     3.59.1 Goals 
    
 
+
      
+
    •  Organize Anaconda progress translation templates.
+
    •  Organize Anaconda progress translation files in several
+languages and major releases of CentOS distribution.
+
    
+
 
 
 
     3.59.2 Description 
    
 
+
    Use the following command to produce translation files based:
+
    
+
     
    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
+
    
+
    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:
+
    
+
     
    centos-art render --translation --filter='3,4,5'
+
    
+
    The above commands will produce the following translation structure:
+
    
+
     
    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
+
    
+
    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
+`trunk/Identity' structure and render them. 
+
    
+
+
 
 
 
     3.59.3 Usage 
    
 
+
    Translation rendering is described in `trunk/Translations'
+documentation entry (see section trunk/Translations).
+
    
+
 
 
 
     3.59.4 See also 
    
 
 
-
 
-
+
    
 
    [ < ]
 [ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_63.html b/Manuals/en/Html/Repository/repository_63.html
index 6b24547..f74692c 100644
--- a/Manuals/en/Html/Repository/repository_63.html
+++ b/Manuals/en/Html/Repository/repository_63.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.60 trunk/Translations/Identity/Themes/Backgrounds
+CentOS Artwork Repository: 3.60 trunk/Translations/Identity/Widgets
 
-
-
+
+
 
 
 
@@ -64,19 +64,19 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
    
    
    
    
 [Top]
 [Contents]
-[Index]
+[Index]
 [ ? ]
 
-
+
 
-
     3.60 trunk/Translations/Identity/Themes/Backgrounds 
    
+
     3.60 trunk/Translations/Identity/Widgets 
    
 
 
 
@@ -106,6 +106,13 @@ ul.toc {list-style: none}
 
 
     3.60.4 See also 
    
 
+
+
+
    3.60 trunk/Translations/Identity/Widgets  
+
    
+
+
+
 
 
 
@@ -114,7 +121,7 @@ ul.toc {list-style: none}
 
-
+
       
 [ << ]
 [ Up ][ >> ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_64.html b/Manuals/en/Html/Repository/repository_64.html
index d5d46f7..522b465 100644
--- a/Manuals/en/Html/Repository/repository_64.html
+++ b/Manuals/en/Html/Repository/repository_64.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.61 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
+CentOS Artwork Repository: Index
 
-
-
+
+
 
 
 
@@ -60,129 +60,161 @@ ul.toc {list-style: none}
 
 
-
+
-
-
+
+
-
+
    
 
    [ < ][ > ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
+
 
-
     3.61 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress 
    
-
-
-
-
     3.61.1 Goals 
    
-
-
      
-
    •  Organize Anaconda progress translation templates.
-
    •  Organize Anaconda progress translation files in several
-languages and major releases of CentOS distribution.
-
    
-
-
-
-
     3.61.2 Description 
    
-
-
    Use the following command to produce translation files based:
-
    
-
     
    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
-
    
-
    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:
-
    
-
     
    centos-art render --translation --filter='3,4,5'
-
    
-
    The above commands will produce the following translation structure:
-
    
-
     
    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
-
    
-
    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
-`trunk/Identity' structure and render them. 
-
    
-
-
-
-
-
     3.61.3 Usage 
    
-
-
    Translation rendering is described in `trunk/Translations'
-documentation entry (see section trunk/Translations).
-
    
-
-
-
-
     3.61.4 See also 
    
+
     Index 
    
+
    Jump to:   B
+   
+C
+   
+H
+   
+M
+   
+S
+   
+T
+   
+U
+   
+
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    Index Entry Section
     
    B
    branches1. branches
     
    C
    Common translation files3.50.2.5 Common Translation Files
     
    H
    How to render brands' translation files3.52.3 Usage
    How to render fonts' translation files3.54.3 Usage
    How to render translation files3.50.3 Usage
     
    M
    Metadata maintainance3.45.2 Description
     
    S
    Specific translation files3.50.2.6 Specific Translation Files
     
    T
    tags2. tags
    Template translation files3.50.2.4 Template Translation Files
    Translation brands file names3.52.2.1 Conventional file names
    Translation brands file names3.52.2.2 Numeric file names
    Translation configuration scripts3.50.2.8 Translation (Pre-)Rendering Configuration Scripts
    Translation entries3.50.2.1 Translation Entries
    Translation files3.50.2.3 Translation Files
    Translation markers3.50.2.2 Translation Markers
    Translation paths3.50.2.1 Translation Entries
    Translation pre-rendering configuration scripts3.50.2.8 Translation (Pre-)Rendering Configuration Scripts
    Translation rendering3.50.2.7 Translation Rendering
    Translation rendering default functionality3.50.2.9 Translation Rendering Default Functionality
    trunk3. trunk
    trunk Identity3.1 trunk/Identity
    trunk Identity Brands3.2 trunk/Identity/Brands
    trunk Identity Fonts3.3 trunk/Identity/Fonts
    trunk Identity Icons3.4 trunk/Identity/Icons
    trunk Identity Isolinux3.5 trunk/Identity/Isolinux
    trunk Identity Models3.6 trunk/Identity/Models
    trunk Identity Models Css3.7 trunk/Identity/Models/Css
    trunk Identity Models Html3.8 trunk/Identity/Models/Html
    trunk Identity Models Img Promo Web3.9 trunk/Identity/Models/Img/Promo/Web
    trunk Identity Models Tpl3.10 trunk/Identity/Models/Tpl
    trunk Identity Models Tpl Promo Web3.11 trunk/Identity/Models/Tpl/Promo/Web
    trunk Identity Models Xcf3.12 trunk/Identity/Models/Xcf
    trunk Identity Release3.13 trunk/Identity/Release
    trunk Identity Themes3.14 trunk/Identity/Themes
    trunk Identity Themes Models3.15 trunk/Identity/Themes/Models
    trunk Identity Themes Models Alternative3.16 trunk/Identity/Themes/Models/Alternative
    trunk Identity Themes Models Default3.17 trunk/Identity/Themes/Models/Default
    trunk Identity Themes Models Default Distro3.18 trunk/Identity/Themes/Models/Default/Distro
    trunk Identity Themes Models Default Distro Anaconda3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda
    trunk Identity Themes Models Default Promo3.20 trunk/Identity/Themes/Models/Default/Promo
    trunk Identity Themes Models Default Web3.21 trunk/Identity/Themes/Models/Default/Web
    trunk Identity Themes Motifs3.22 trunk/Identity/Themes/Motifs
    trunk Identity Themes Motifs Flame3.23 trunk/Identity/Themes/Motifs/Flame
    trunk Identity Themes Motifs Modern3.24 trunk/Identity/Themes/Motifs/Modern
    trunk Identity Themes Motifs Modern Backgrounds3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds
    trunk Identity Themes Motifs Modern Backgrounds Img3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img
    trunk Identity Themes Motifs Modern Backgrounds Tpl3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl
    trunk Identity Themes Motifs Modern Backgrounds Xcf3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf
    trunk Identity Themes Motifs Modern Distro Anaconda Progress3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
    trunk Identity Themes Motifs Modern Palettes3.30 trunk/Identity/Themes/Motifs/Modern/Palettes
    trunk Identity Themes Motifs TreeFlower3.31 trunk/Identity/Themes/Motifs/TreeFlower
    trunk Identity Themes Motifs TreeFlower Backgrounds3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds
    trunk Identity Widgets3.33 trunk/Identity/Widgets
    trunk Manuals3.34 trunk/Manuals
    trunk Scripts3.35 trunk/Scripts
    trunk Scripts Bash3.36 trunk/Scripts/Bash
    trunk Scripts Bash Functions3.37 trunk/Scripts/Bash/Functions
    trunk Scripts Bash Functions Help3.38 trunk/Scripts/Bash/Functions/Help
    trunk Scripts Bash Functions Html3.39 trunk/Scripts/Bash/Functions/Html
    trunk Scripts Bash Functions Locale3.40 trunk/Scripts/Bash/Functions/Locale
    trunk Scripts Bash Functions Path3.41 trunk/Scripts/Bash/Functions/Path
    trunk Scripts Bash Functions Render3.42 trunk/Scripts/Bash/Functions/Render
    trunk Scripts Bash Functions Render Config3.43 trunk/Scripts/Bash/Functions/Render/Config
    trunk Scripts Bash Functions Shell3.44 trunk/Scripts/Bash/Functions/Shell
    trunk Scripts Bash Functions Svg3.45 trunk/Scripts/Bash/Functions/Svg
    trunk Scripts Bash Functions Verify3.46 trunk/Scripts/Bash/Functions/Verify
    trunk Scripts Bash Locale3.47 trunk/Scripts/Bash/Locale
    trunk Scripts Perl3.48 trunk/Scripts/Perl
    trunk Scripts Python3.49 trunk/Scripts/Python
    trunk Translations3.50 trunk/Translations
    trunk Translations Identity3.51 trunk/Translations/Identity
    trunk Translations Identity Brands3.52 trunk/Translations/Identity/Brands
    trunk Translations Identity Brands Tpl3.53 trunk/Translations/Identity/Brands/Tpl
    trunk Translations Identity Fonts3.54 trunk/Translations/Identity/Fonts
    trunk Translations Identity Models3.55 trunk/Translations/Identity/Models
    trunk Translations Identity Release3.56 trunk/Translations/Identity/Release
    trunk Translations Identity Themes3.57 trunk/Translations/Identity/Themes
    trunk Translations Identity Themes Backgrounds3.58 trunk/Translations/Identity/Themes/Backgrounds
    trunk Translations Identity Themes Distro Anaconda Progress3.59 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
    trunk Translations Identity Widgets3.60 trunk/Translations/Identity/Widgets
     
    U
    Unused definitions3.45.2.1 Metadata maintainance
     
    
+
    Jump to:   B
+   
+C
+   
+H
+   
+M
+   
+S
+   
+T
+   
+U
+   
+
    
 
 
 
-
-
+
+
-
-
+
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_65.html b/Manuals/en/Html/Repository/repository_65.html
index 7698ec1..b4bb2cc 100644
--- a/Manuals/en/Html/Repository/repository_65.html
+++ b/Manuals/en/Html/Repository/repository_65.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: 3.62 trunk/Translations/Identity/Widgets
+CentOS Artwork Repository: List of Figures
 
-
-
+
+
 
 
 
@@ -59,69 +59,65 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
-
-
+
+
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    [ << ][ Up ][ >> ][ << ][ Up ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
-
-
     3.62 trunk/Translations/Identity/Widgets 
    
-
-
-
-
     3.62.1 Goals 
    
-
-
      
-
    •  ...
-
    
-
-
-
-
     3.62.2 Description 
    
-
-
      
-
    •  ...
-
    
-
-
-
-
     3.62.3 Usage 
    
-
-
      
-
    •  ...
-
    
-
-
-
-
     3.62.4 See also 
    
-
-
-
-
    3.62 trunk/Translations/Identity/Widgets  
-
    
-
-
-
+
+
+
     List of Figures 
    
+
    
+
    Figure 3.1
    The CentOS Type.
+
    
+
    Figure 3.2
    The CentOS Type plus release information (i.e., CentOS Release Brand).
+
    
+
    Figure 3.3
    The CentOS Type plus release information plus description (i.e., CentOS Release Brand with description).
+
    
+
    Figure 3.4
    The CentOS web customization design model.
+
    
+
    Figure 3.5
    The CentOS web customization using promotion design model.
+
    
+
    Figure 3.6
    Web environment html definitions
+
    
+
    Figure 3.7
    The CentOS web navigation design model.
+
    
+
    Figure 3.8
    The `centos-art.sh' initialization environment.
+
    
+
    Figure 3.9
    The cli_commitRepoChanges function output.
+
    
+
    Figure 3.10
    The CentOS Artwork Repository layout.
+
    
+
    Figure 3.11
    Name convention for tags and branches creation.
+
    
+
    Figure 3.12
    Parallel directories removing uncommon information.
+
    
+
    Figure 3.13
    Parallel directories adding uncommon information.
+
    
+
    Figure 3.14
    Wrong construction of parallel directories.
+
    
+
    Figure 3.15
    The image rendering flow.
+
    
+
    
 
 
 
-
-
+
+
-
-
-
+
+
+
    [ < ][ > ]
    [ < ][ > ]
    [ << ][ Up ][ >> ][ << ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_66.html b/Manuals/en/Html/Repository/repository_66.html
index a20f0df..cdf1461 100644
--- a/Manuals/en/Html/Repository/repository_66.html
+++ b/Manuals/en/Html/Repository/repository_66.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: Index
+CentOS Artwork Repository: 3.63 trunk/Translations/Identity/Widgets
 
-
-
+
+
 
 
 
@@ -60,163 +60,68 @@ ul.toc {list-style: none}
 
 
-
+
-
-
+
+
-
+
    
 
    [ < ][ > ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
+
 
-
     Index 
    
-
    Jump to:   B
-   
-C
-   
-H
-   
-M
-   
-S
-   
-T
-   
-U
-   
-
    
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
     3.63 trunk/Translations/Identity/Widgets 
    
+
+
+
+
     3.63.1 Goals 
    
+
+
      
+
    •  ...
+
    
+
+
+
+
     3.63.2 Description 
    
+
+
      
+
    •  ...
+
    
+
+
+
+
     3.63.3 Usage 
    
+
+
      
+
    •  ...
+
    
+
+
+
+
     3.63.4 See also 
    
+
+
    Index Entry Section
     
    B
    branches1. branches
     
    C
    Common translation files3.52.2.5 Common Translation Files
     
    H
    How to render brands' translation files3.54.3 Usage
    How to render fonts' translation files3.56.3 Usage
    How to render translation files3.52.3 Usage
     
    M
    Metadata maintainance3.47.2 Description
     
    S
    Specific translation files3.52.2.6 Specific Translation Files
     
    T
    tags2. tags
    Template translation files3.52.2.4 Template Translation Files
    Translation brands file names3.54.2.1 Conventional file names
    Translation brands file names3.54.2.2 Numeric file names
    Translation configuration scripts3.52.2.8 Translation (Pre-)Rendering Configuration Scripts
    Translation entries3.52.2.1 Translation Entries
    Translation files3.52.2.3 Translation Files
    Translation markers3.52.2.2 Translation Markers
    Translation paths3.52.2.1 Translation Entries
    Translation pre-rendering configuration scripts3.52.2.8 Translation (Pre-)Rendering Configuration Scripts
    Translation rendering3.52.2.7 Translation Rendering
    Translation rendering default functionality3.52.2.9 Translation Rendering Default Functionality
    trunk3. trunk
    trunk Identity3.1 trunk/Identity
    trunk Identity Brands3.2 trunk/Identity/Brands
    trunk Identity Fonts3.3 trunk/Identity/Fonts
    trunk Identity Icons3.4 trunk/Identity/Icons
    trunk Identity Isolinux3.5 trunk/Identity/Isolinux
    trunk Identity Models3.6 trunk/Identity/Models
    trunk Identity Models Css3.7 trunk/Identity/Models/Css
    trunk Identity Models Html3.8 trunk/Identity/Models/Html
    trunk Identity Models Img Promo Web3.9 trunk/Identity/Models/Img/Promo/Web
    trunk Identity Models Tpl3.10 trunk/Identity/Models/Tpl
    trunk Identity Models Tpl Promo Web3.11 trunk/Identity/Models/Tpl/Promo/Web
    trunk Identity Models Xcf3.12 trunk/Identity/Models/Xcf
    trunk Identity Release3.13 trunk/Identity/Release
    trunk Identity Themes3.14 trunk/Identity/Themes
    trunk Identity Themes Models3.15 trunk/Identity/Themes/Models
    trunk Identity Themes Models Alternative3.16 trunk/Identity/Themes/Models/Alternative
    trunk Identity Themes Models Default3.17 trunk/Identity/Themes/Models/Default
    trunk Identity Themes Models Default Distro3.18 trunk/Identity/Themes/Models/Default/Distro
    trunk Identity Themes Models Default Distro Anaconda3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda
    trunk Identity Themes Models Default Promo3.20 trunk/Identity/Themes/Models/Default/Promo
    trunk Identity Themes Models Default Web3.21 trunk/Identity/Themes/Models/Default/Web
    trunk Identity Themes Motifs3.22 trunk/Identity/Themes/Motifs
    trunk Identity Themes Motifs Flame3.23 trunk/Identity/Themes/Motifs/Flame
    trunk Identity Themes Motifs Flame Distro Anaconda3.24 trunk/Identity/Themes/Motifs/Flame/Distro/Anaconda
    trunk Identity Themes Motifs Flame Distro BootUp3.25 trunk/Identity/Themes/Motifs/Flame/Distro/BootUp
    trunk Identity Themes Motifs Modern3.26 trunk/Identity/Themes/Motifs/Modern
    trunk Identity Themes Motifs Modern Backgrounds3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds
    trunk Identity Themes Motifs Modern Backgrounds Img3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img
    trunk Identity Themes Motifs Modern Backgrounds Tpl3.29 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl
    trunk Identity Themes Motifs Modern Backgrounds Xcf3.30 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf
    trunk Identity Themes Motifs Modern Distro Anaconda Progress3.31 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
    trunk Identity Themes Motifs Modern Palettes3.32 trunk/Identity/Themes/Motifs/Modern/Palettes
    trunk Identity Themes Motifs TreeFlower3.33 trunk/Identity/Themes/Motifs/TreeFlower
    trunk Identity Themes Motifs TreeFlower Backgrounds3.34 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds
    trunk Identity Widgets3.35 trunk/Identity/Widgets
    trunk Manuals3.36 trunk/Manuals
    trunk Scripts3.37 trunk/Scripts
    trunk Scripts Bash3.38 trunk/Scripts/Bash
    trunk Scripts Bash Functions3.39 trunk/Scripts/Bash/Functions
    trunk Scripts Bash Functions Help3.40 trunk/Scripts/Bash/Functions/Help
    trunk Scripts Bash Functions Html3.41 trunk/Scripts/Bash/Functions/Html
    trunk Scripts Bash Functions Locale3.42 trunk/Scripts/Bash/Functions/Locale
    trunk Scripts Bash Functions Path3.43 trunk/Scripts/Bash/Functions/Path
    trunk Scripts Bash Functions Render3.44 trunk/Scripts/Bash/Functions/Render
    trunk Scripts Bash Functions Render Config3.45 trunk/Scripts/Bash/Functions/Render/Config
    trunk Scripts Bash Functions Shell3.46 trunk/Scripts/Bash/Functions/Shell
    trunk Scripts Bash Functions Svg3.47 trunk/Scripts/Bash/Functions/Svg
    trunk Scripts Bash Functions Verify3.48 trunk/Scripts/Bash/Functions/Verify
    trunk Scripts Bash Locale3.49 trunk/Scripts/Bash/Locale
    trunk Scripts Perl3.50 trunk/Scripts/Perl
    trunk Scripts Python3.51 trunk/Scripts/Python
    trunk Translations3.52 trunk/Translations
    trunk Translations Identity3.53 trunk/Translations/Identity
    trunk Translations Identity Brands3.54 trunk/Translations/Identity/Brands
    trunk Translations Identity Brands Tpl3.55 trunk/Translations/Identity/Brands/Tpl
    trunk Translations Identity Fonts3.56 trunk/Translations/Identity/Fonts
    trunk Translations Identity Models3.57 trunk/Translations/Identity/Models
    trunk Translations Identity Release3.58 trunk/Translations/Identity/Release
    trunk Translations Identity Themes3.59 trunk/Translations/Identity/Themes
    trunk Translations Identity Themes Backgrounds3.60 trunk/Translations/Identity/Themes/Backgrounds
    trunk Translations Identity Themes Distro Anaconda Progress3.61 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
    trunk Translations Identity Widgets3.62 trunk/Translations/Identity/Widgets
     
    U
    Unused definitions3.47.2.1 Metadata maintainance
     
    
+
    3.63 trunk/Translations/Identity/Widgets  
+
    
 
    
-
    Jump to:   B
-   
-C
-   
-H
-   
-M
-   
-S
-   
-T
-   
-U
-   
-
    
+
+
+
 
 
 
-
-
+
+
-
-
+
+
    [ < ][ > ]
    [ < ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_67.html b/Manuals/en/Html/Repository/repository_67.html
index 65123d9..8dcdc0e 100644
--- a/Manuals/en/Html/Repository/repository_67.html
+++ b/Manuals/en/Html/Repository/repository_67.html
@@ -27,10 +27,10 @@ Send bugs and suggestions to 
 
 -->
 
-CentOS Artwork Repository: List of Figures
+CentOS Artwork Repository: Index
 
-
-
+
+
 
 
 
@@ -59,65 +59,165 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    [ << ][ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
-
-
-
     List of Figures 
    
-
    
-
    Figure 3.1
    The CentOS Type.
-
    
-
    Figure 3.2
    The CentOS Type plus release information (i.e., CentOS Release Brand).
-
    
-
    Figure 3.3
    The CentOS Type plus release information plus description (i.e., CentOS Release Brand with description).
-
    
-
    Figure 3.4
    The CentOS web customization design model.
-
    
-
    Figure 3.5
    The CentOS web customization using promotion design model.
-
    
-
    Figure 3.6
    Web environment html definitions
-
    
-
    Figure 3.7
    The CentOS web navigation design model.
-
    
-
    Figure 3.8
    The `centos-art.sh' initialization environment.
-
    
-
    Figure 3.9
    The cli_commitRepoChanges function output.
-
    
-
    Figure 3.10
    The CentOS Artwork Repository layout.
-
    
-
    Figure 3.11
    Name convention for tags and branches creation.
-
    
-
    Figure 3.12
    Parallel directories removing uncommon information.
-
    
-
    Figure 3.13
    Parallel directories adding uncommon information.
-
    
-
    Figure 3.14
    Wrong construction of parallel directories.
-
    
-
    Figure 3.15
    The image rendering flow.
-
    
-
    
+
+
+
     Index 
    
+
    Jump to:   B
+   
+C
+   
+H
+   
+M
+   
+S
+   
+T
+   
+U
+   
+
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    Index Entry Section
     
    B
    branches1. branches
     
    C
    Common translation files3.53.2.5 Common Translation Files
     
    H
    How to render brands' translation files3.55.3 Usage
    How to render fonts' translation files3.57.3 Usage
    How to render translation files3.53.3 Usage
     
    M
    Metadata maintainance3.48.2 Description
     
    S
    Specific translation files3.53.2.6 Specific Translation Files
     
    T
    tags2. tags
    Template translation files3.53.2.4 Template Translation Files
    Translation brands file names3.55.2.1 Conventional file names
    Translation brands file names3.55.2.2 Numeric file names
    Translation configuration scripts3.53.2.8 Translation (Pre-)Rendering Configuration Scripts
    Translation entries3.53.2.1 Translation Entries
    Translation files3.53.2.3 Translation Files
    Translation markers3.53.2.2 Translation Markers
    Translation paths3.53.2.1 Translation Entries
    Translation pre-rendering configuration scripts3.53.2.8 Translation (Pre-)Rendering Configuration Scripts
    Translation rendering3.53.2.7 Translation Rendering
    Translation rendering default functionality3.53.2.9 Translation Rendering Default Functionality
    trunk3. trunk
    trunk Identity3.1 trunk/Identity
    trunk Identity Brands3.2 trunk/Identity/Brands
    trunk Identity Fonts3.3 trunk/Identity/Fonts
    trunk Identity Icons3.4 trunk/Identity/Icons
    trunk Identity Isolinux3.5 trunk/Identity/Isolinux
    trunk Identity Models3.6 trunk/Identity/Models
    trunk Identity Models Css3.7 trunk/Identity/Models/Css
    trunk Identity Models Html3.8 trunk/Identity/Models/Html
    trunk Identity Models Img Promo Web3.9 trunk/Identity/Models/Img/Promo/Web
    trunk Identity Models Tpl3.10 trunk/Identity/Models/Tpl
    trunk Identity Models Tpl Promo Web3.11 trunk/Identity/Models/Tpl/Promo/Web
    trunk Identity Models Xcf3.12 trunk/Identity/Models/Xcf
    trunk Identity Release3.13 trunk/Identity/Release
    trunk Identity Themes3.14 trunk/Identity/Themes
    trunk Identity Themes Models3.15 trunk/Identity/Themes/Models
    trunk Identity Themes Models Alternative3.16 trunk/Identity/Themes/Models/Alternative
    trunk Identity Themes Models Default3.17 trunk/Identity/Themes/Models/Default
    trunk Identity Themes Models Default Distro3.18 trunk/Identity/Themes/Models/Default/Distro
    trunk Identity Themes Models Default Distro Anaconda3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda
    trunk Identity Themes Models Default Promo3.20 trunk/Identity/Themes/Models/Default/Promo
    trunk Identity Themes Models Default Web3.21 trunk/Identity/Themes/Models/Default/Web
    trunk Identity Themes Motifs3.22 trunk/Identity/Themes/Motifs
    trunk Identity Themes Motifs Flame3.23 trunk/Identity/Themes/Motifs/Flame
    trunk Identity Themes Motifs Flame Distro3.24 trunk/Identity/Themes/Motifs/Flame/Distro
    trunk Identity Themes Motifs Flame Distro Anaconda3.25 trunk/Identity/Themes/Motifs/Flame/Distro/Anaconda
    trunk Identity Themes Motifs Flame Distro BootUp3.26 trunk/Identity/Themes/Motifs/Flame/Distro/BootUp
    trunk Identity Themes Motifs Modern3.27 trunk/Identity/Themes/Motifs/Modern
    trunk Identity Themes Motifs Modern Backgrounds3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds
    trunk Identity Themes Motifs Modern Backgrounds Img3.29 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img
    trunk Identity Themes Motifs Modern Backgrounds Tpl3.30 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl
    trunk Identity Themes Motifs Modern Backgrounds Xcf3.31 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf
    trunk Identity Themes Motifs Modern Distro Anaconda Progress3.32 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
    trunk Identity Themes Motifs Modern Palettes3.33 trunk/Identity/Themes/Motifs/Modern/Palettes
    trunk Identity Themes Motifs TreeFlower3.34 trunk/Identity/Themes/Motifs/TreeFlower
    trunk Identity Themes Motifs TreeFlower Backgrounds3.35 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds
    trunk Identity Widgets3.36 trunk/Identity/Widgets
    trunk Manuals3.37 trunk/Manuals
    trunk Scripts3.38 trunk/Scripts
    trunk Scripts Bash3.39 trunk/Scripts/Bash
    trunk Scripts Bash Functions3.40 trunk/Scripts/Bash/Functions
    trunk Scripts Bash Functions Help3.41 trunk/Scripts/Bash/Functions/Help
    trunk Scripts Bash Functions Html3.42 trunk/Scripts/Bash/Functions/Html
    trunk Scripts Bash Functions Locale3.43 trunk/Scripts/Bash/Functions/Locale
    trunk Scripts Bash Functions Path3.44 trunk/Scripts/Bash/Functions/Path
    trunk Scripts Bash Functions Render3.45 trunk/Scripts/Bash/Functions/Render
    trunk Scripts Bash Functions Render Config3.46 trunk/Scripts/Bash/Functions/Render/Config
    trunk Scripts Bash Functions Shell3.47 trunk/Scripts/Bash/Functions/Shell
    trunk Scripts Bash Functions Svg3.48 trunk/Scripts/Bash/Functions/Svg
    trunk Scripts Bash Functions Verify3.49 trunk/Scripts/Bash/Functions/Verify
    trunk Scripts Bash Locale3.50 trunk/Scripts/Bash/Locale
    trunk Scripts Perl3.51 trunk/Scripts/Perl
    trunk Scripts Python3.52 trunk/Scripts/Python
    trunk Translations3.53 trunk/Translations
    trunk Translations Identity3.54 trunk/Translations/Identity
    trunk Translations Identity Brands3.55 trunk/Translations/Identity/Brands
    trunk Translations Identity Brands Tpl3.56 trunk/Translations/Identity/Brands/Tpl
    trunk Translations Identity Fonts3.57 trunk/Translations/Identity/Fonts
    trunk Translations Identity Models3.58 trunk/Translations/Identity/Models
    trunk Translations Identity Release3.59 trunk/Translations/Identity/Release
    trunk Translations Identity Themes3.60 trunk/Translations/Identity/Themes
    trunk Translations Identity Themes Backgrounds3.61 trunk/Translations/Identity/Themes/Backgrounds
    trunk Translations Identity Themes Distro Anaconda Progress3.62 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
    trunk Translations Identity Widgets3.63 trunk/Translations/Identity/Widgets
     
    U
    Unused definitions3.48.2.1 Metadata maintainance
     
    
+
    Jump to:   B
+   
+C
+   
+H
+   
+M
+   
+S
+   
+T
+   
+U
+   
+
    
 
 
 
-
-
+
+
-
+
-
+
    [ < ][ > ]
    [ < ][ > ]
    [ << ][ << ]
 [ Up ][ >> ][ >> ]
 
    
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_7.html b/Manuals/en/Html/Repository/repository_7.html
index e557fd9..64eb09b 100644
--- a/Manuals/en/Html/Repository/repository_7.html
+++ b/Manuals/en/Html/Repository/repository_7.html
@@ -64,14 +64,14 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
    
    
    
    
 [Top]
 [Contents]
-[Index]
+[Index]
 [ ? ]
 
 
@@ -106,7 +106,7 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
 
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_8.html b/Manuals/en/Html/Repository/repository_8.html
index 936557a..4e982b5 100644
--- a/Manuals/en/Html/Repository/repository_8.html
+++ b/Manuals/en/Html/Repository/repository_8.html
@@ -64,14 +64,14 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
    
    
    
    
 [Top]
 [Contents]
-[Index]
+[Index]
 [ ? ]
 
 
@@ -106,7 +106,7 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
 
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_9.html b/Manuals/en/Html/Repository/repository_9.html
index fdda770..07f9da9 100644
--- a/Manuals/en/Html/Repository/repository_9.html
+++ b/Manuals/en/Html/Repository/repository_9.html
@@ -64,14 +64,14 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
    
    
    
    
 [Top]
 [Contents]
-[Index]
+[Index]
 [ ? ]
 
 
@@ -117,7 +117,7 @@ to build artworks.
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
 
 
    
  
diff --git a/Manuals/en/Html/Repository/repository_abt.html b/Manuals/en/Html/Repository/repository_abt.html
index d4115b3..9008214 100644
--- a/Manuals/en/Html/Repository/repository_abt.html
+++ b/Manuals/en/Html/Repository/repository_abt.html
@@ -62,7 +62,7 @@ ul.toc {list-style: none}
 
-
+
    
 
    [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
 
    About This Document
    
@@ -170,7 +170,7 @@ ul.toc {list-style: none}
 
-
+
    
 
    [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
 
    
diff --git a/Manuals/en/Html/Repository/repository_fot.html b/Manuals/en/Html/Repository/repository_fot.html
index 17ec870..f5f927f 100644
--- a/Manuals/en/Html/Repository/repository_fot.html
+++ b/Manuals/en/Html/Repository/repository_fot.html
@@ -62,27 +62,27 @@ ul.toc {list-style: none}
 
-
+
    
 
    [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
 
    Footnotes
    
 
    (1)
    
 
    Mailman's theme support may be introduced in
 mailman-3.x.x release.
-
    (2)
    
+
    (2)
    
 
    This number is an approximate value and may change.
 It is mainly based on CentOS 5 rebranding experience.
-
    (3)
    
+
    (3)
    
 
    This value was taken from
 CentOS release schema.
-
    (4)
    
+
    (4)
    
 
    This value was taken from the
 locale -a command's output.
 
    
 
-
+
    
 
    [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
 
    
diff --git a/Manuals/en/Html/Repository/repository_toc.html b/Manuals/en/Html/Repository/repository_toc.html
index 85d6397..f65adea 100644
--- a/Manuals/en/Html/Repository/repository_toc.html
+++ b/Manuals/en/Html/Repository/repository_toc.html
@@ -62,7 +62,7 @@ ul.toc {list-style: none}
 
-
+
    
 
    [Top]
 [Contents][Index][Index]
 [ ? ]
 
    
 
    Table of Contents
    
@@ -266,344 +266,330 @@ ul.toc {list-style: none}
       
  • 3.23.4 Step 4: Add foreground color
    • 
       
  • 3.23.5 See also
    •
-
  • 3.24 trunk/Identity/Themes/Motifs/Flame/Distro/Anaconda +
  • 3.24 trunk/Identity/Themes/Motifs/Modern
    • -
  • 3.25 trunk/Identity/Themes/Motifs/Flame/Distro/BootUp +
  • 3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds
    • -
  • 3.26 trunk/Identity/Themes/Motifs/Modern +
  • 3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img
    • -
  • 3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds +
  • 3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl
    • -
  • 3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img +
  • 3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf
    • -
  • 3.29 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl +
  • 3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
    • -
  • 3.30 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf +
  • 3.30 trunk/Identity/Themes/Motifs/Modern/Palettes
    • -
  • 3.31 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress +
  • 3.31 trunk/Identity/Themes/Motifs/TreeFlower
    • -
  • 3.32 trunk/Identity/Themes/Motifs/Modern/Palettes +
  • 3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds
    • -
  • 3.33 trunk/Identity/Themes/Motifs/TreeFlower +
  • 3.33 trunk/Identity/Widgets
    • -
  • 3.34 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds +
  • 3.34 trunk/Manuals
    • -
  • 3.35 trunk/Identity/Widgets +
  • 3.35 trunk/Scripts
    • -
  • 3.36 trunk/Manuals +
  • 3.36 trunk/Scripts/Bash
    • -
  • 3.37 trunk/Scripts +
  • 3.37 trunk/Scripts/Bash/Functions
    • -
  • 3.38 trunk/Scripts/Bash -
    • -
  • 3.39 trunk/Scripts/Bash/Functions -
    • -
  • 3.40 trunk/Scripts/Bash/Functions/Help +
  • 3.38 trunk/Scripts/Bash/Functions/Help
    • -
  • 3.41 trunk/Scripts/Bash/Functions/Html +
  • 3.39 trunk/Scripts/Bash/Functions/Html
    • -
  • 3.42 trunk/Scripts/Bash/Functions/Locale +
  • 3.40 trunk/Scripts/Bash/Functions/Locale
    • -
  • 3.43 trunk/Scripts/Bash/Functions/Path +
  • 3.41 trunk/Scripts/Bash/Functions/Path
    • -
  • 3.44 trunk/Scripts/Bash/Functions/Render +
  • 3.42 trunk/Scripts/Bash/Functions/Render
    • -
  • 3.45 trunk/Scripts/Bash/Functions/Render/Config +
  • 3.43 trunk/Scripts/Bash/Functions/Render/Config
    • -
  • 3.46 trunk/Scripts/Bash/Functions/Shell +
  • 3.44 trunk/Scripts/Bash/Functions/Shell
    • -
  • 3.47 trunk/Scripts/Bash/Functions/Svg +
  • 3.45 trunk/Scripts/Bash/Functions/Svg
    • -
  • 3.48 trunk/Scripts/Bash/Functions/Verify +
  • 3.46 trunk/Scripts/Bash/Functions/Verify
    • +
  • 3.47 trunk/Scripts/Bash/Locale +
    • +
  • 3.48 trunk/Scripts/Perl +
    • -
  • 3.49 trunk/Scripts/Bash/Locale +
  • 3.49 trunk/Scripts/Python
    • -
  • 3.50 trunk/Scripts/Perl +
  • 3.50 trunk/Translations
    • -
  • 3.51 trunk/Scripts/Python +
  • 3.51 trunk/Translations/Identity
    • -
  • 3.52 trunk/Translations +
  • 3.52 trunk/Translations/Identity/Brands
    • -
  • 3.53 trunk/Translations/Identity +
  • 3.53 trunk/Translations/Identity/Brands/Tpl
    • -
  • 3.54 trunk/Translations/Identity/Brands +
  • 3.54 trunk/Translations/Identity/Fonts
    • -
  • 3.55 trunk/Translations/Identity/Brands/Tpl +
  • 3.55 trunk/Translations/Identity/Models
    • -
  • 3.56 trunk/Translations/Identity/Fonts +
  • 3.56 trunk/Translations/Identity/Release
    • -
  • 3.57 trunk/Translations/Identity/Models +
  • 3.57 trunk/Translations/Identity/Themes
    • -
  • 3.58 trunk/Translations/Identity/Release +
  • 3.58 trunk/Translations/Identity/Themes/Backgrounds
    • -
  • 3.59 trunk/Translations/Identity/Themes +
  • 3.59 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
    • -
  • 3.60 trunk/Translations/Identity/Themes/Backgrounds +
  • 3.60 trunk/Translations/Identity/Widgets
    • -
  • 3.61 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress -
    • -
  • 3.62 trunk/Translations/Identity/Widgets -
    • -
  • Index
    • -
  • List of Figures
    • +
  • Index
    • +
  • List of Figures
    • - +
    [Top] [Contents][Index][Index] [ ? ]

    diff --git a/Manuals/en/Info/Repository/repository.info.bz2 b/Manuals/en/Info/Repository/repository.info.bz2 index 87575bc..0c2c9a3 100644 Binary files a/Manuals/en/Info/Repository/repository.info.bz2 and b/Manuals/en/Info/Repository/repository.info.bz2 differ diff --git a/Manuals/en/Plaintext/Repository/repository.txt b/Manuals/en/Plaintext/Repository/repository.txt index 76857a8..13e7837 100644 --- a/Manuals/en/Plaintext/Repository/repository.txt +++ b/Manuals/en/Plaintext/Repository/repository.txt @@ -144,235 +144,225 @@ CentOS Artwork Repository 3.23.3 Step 3: Add flame motif 3.23.4 Step 4: Add foreground color 3.23.5 See also - 3.24 trunk/Identity/Themes/Motifs/Flame/Distro/Anaconda - 3.24.1 Goals - 3.24.2 Description + 3.24 trunk/Identity/Themes/Motifs/Modern + 3.24.1 Presentation + 3.24.2 Construction 3.24.3 Usage 3.24.4 See also - 3.25 trunk/Identity/Themes/Motifs/Flame/Distro/BootUp + 3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds 3.25.1 Goals 3.25.2 Description 3.25.3 Usage 3.25.4 See also - 3.26 trunk/Identity/Themes/Motifs/Modern - 3.26.1 Presentation - 3.26.2 Construction + 3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img + 3.26.1 Goals + 3.26.2 Description 3.26.3 Usage 3.26.4 See also - 3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds + 3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl 3.27.1 Goals 3.27.2 Description 3.27.3 Usage 3.27.4 See also - 3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img + 3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf 3.28.1 Goals 3.28.2 Description 3.28.3 Usage 3.28.4 See also - 3.29 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl + 3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress 3.29.1 Goals 3.29.2 Description 3.29.3 Usage 3.29.4 See also - 3.30 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf + 3.30 trunk/Identity/Themes/Motifs/Modern/Palettes 3.30.1 Goals 3.30.2 Description 3.30.3 Usage 3.30.4 See also - 3.31 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress + 3.31 trunk/Identity/Themes/Motifs/TreeFlower 3.31.1 Goals 3.31.2 Description 3.31.3 Usage 3.31.4 See also - 3.32 trunk/Identity/Themes/Motifs/Modern/Palettes + 3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds 3.32.1 Goals 3.32.2 Description + 3.32.2.1 Desktop background + 3.32.2.2 Anaconda Prompt (syslinux) background + 3.32.2.3 Grub background 3.32.3 Usage 3.32.4 See also - 3.33 trunk/Identity/Themes/Motifs/TreeFlower + 3.33 trunk/Identity/Widgets 3.33.1 Goals 3.33.2 Description 3.33.3 Usage 3.33.4 See also - 3.34 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds + 3.34 trunk/Manuals 3.34.1 Goals 3.34.2 Description - 3.34.2.1 Desktop background - 3.34.2.2 Anaconda Prompt (syslinux) background - 3.34.2.3 Grub background 3.34.3 Usage 3.34.4 See also - 3.35 trunk/Identity/Widgets + 3.35 trunk/Scripts 3.35.1 Goals 3.35.2 Description 3.35.3 Usage 3.35.4 See also - 3.36 trunk/Manuals + 3.36 trunk/Scripts/Bash 3.36.1 Goals 3.36.2 Description 3.36.3 Usage 3.36.4 See also - 3.37 trunk/Scripts + 3.37 trunk/Scripts/Bash/Functions 3.37.1 Goals 3.37.2 Description 3.37.3 Usage + 3.37.3.1 Global variables + 3.37.3.2 Global functions + 3.37.3.3 Specific functions 3.37.4 See also - 3.38 trunk/Scripts/Bash + 3.38 trunk/Scripts/Bash/Functions/Help 3.38.1 Goals 3.38.2 Description + 3.38.2.1 Output different formats 3.38.3 Usage 3.38.4 See also - 3.39 trunk/Scripts/Bash/Functions + 3.39 trunk/Scripts/Bash/Functions/Html 3.39.1 Goals 3.39.2 Description 3.39.3 Usage - 3.39.3.1 Global variables - 3.39.3.2 Global functions - 3.39.3.3 Specific functions 3.39.4 See also - 3.40 trunk/Scripts/Bash/Functions/Help + 3.40 trunk/Scripts/Bash/Functions/Locale 3.40.1 Goals 3.40.2 Description - 3.40.2.1 Output different formats 3.40.3 Usage 3.40.4 See also - 3.41 trunk/Scripts/Bash/Functions/Html + 3.41 trunk/Scripts/Bash/Functions/Path 3.41.1 Goals 3.41.2 Description + 3.41.2.1 Repository layout + 3.41.2.2 Repository name convenctions + 3.41.2.3 Repository work flow + 3.41.2.4 Parallel directories + 3.41.2.5 Syncronizing path information + 3.41.2.6 What is the right location to store it? 3.41.3 Usage 3.41.4 See also - 3.42 trunk/Scripts/Bash/Functions/Locale + 3.42 trunk/Scripts/Bash/Functions/Render 3.42.1 Goals 3.42.2 Description 3.42.3 Usage 3.42.4 See also - 3.43 trunk/Scripts/Bash/Functions/Path + 3.43 trunk/Scripts/Bash/Functions/Render/Config 3.43.1 Goals 3.43.2 Description - 3.43.2.1 Repository layout - 3.43.2.2 Repository name convenctions - 3.43.2.3 Repository work flow - 3.43.2.4 Parallel directories - 3.43.2.5 Syncronizing path information - 3.43.2.6 What is the right location to store it? + 3.43.2.1 The `render.conf.sh' identity model + 3.43.2.2 The `render.conf.sh' translation model + 3.43.2.3 The `render.conf.sh' rendering actions 3.43.3 Usage 3.43.4 See also - 3.44 trunk/Scripts/Bash/Functions/Render + 3.44 trunk/Scripts/Bash/Functions/Shell 3.44.1 Goals 3.44.2 Description 3.44.3 Usage 3.44.4 See also - 3.45 trunk/Scripts/Bash/Functions/Render/Config + 3.45 trunk/Scripts/Bash/Functions/Svg 3.45.1 Goals 3.45.2 Description - 3.45.2.1 The `render.conf.sh' identity model - 3.45.2.2 The `render.conf.sh' translation model - 3.45.2.3 The `render.conf.sh' rendering actions + 3.45.2.1 Metadata maintainance + 3.45.2.2 Unused definitions 3.45.3 Usage 3.45.4 See also - 3.46 trunk/Scripts/Bash/Functions/Shell + 3.46 trunk/Scripts/Bash/Functions/Verify 3.46.1 Goals 3.46.2 Description + 3.46.2.1 Packages + 3.46.2.2 Links + 3.46.2.3 Environment variables 3.46.3 Usage 3.46.4 See also - 3.47 trunk/Scripts/Bash/Functions/Svg + 3.47 trunk/Scripts/Bash/Locale 3.47.1 Goals 3.47.2 Description - 3.47.2.1 Metadata maintainance - 3.47.2.2 Unused definitions 3.47.3 Usage 3.47.4 See also - 3.48 trunk/Scripts/Bash/Functions/Verify + 3.48 trunk/Scripts/Perl 3.48.1 Goals 3.48.2 Description - 3.48.2.1 Packages - 3.48.2.2 Links - 3.48.2.3 Environment variables 3.48.3 Usage 3.48.4 See also - 3.49 trunk/Scripts/Bash/Locale + 3.49 trunk/Scripts/Python 3.49.1 Goals 3.49.2 Description 3.49.3 Usage 3.49.4 See also - 3.50 trunk/Scripts/Perl + 3.50 trunk/Translations 3.50.1 Goals 3.50.2 Description + 3.50.2.1 Translation Entries + 3.50.2.2 Translation Markers + 3.50.2.3 Translation Files + 3.50.2.4 Template Translation Files + 3.50.2.5 Common Translation Files + 3.50.2.6 Specific Translation Files + 3.50.2.7 Translation Rendering + 3.50.2.8 Translation (Pre-)Rendering Configuration Scripts + 3.50.2.9 Translation Rendering Default Functionality 3.50.3 Usage 3.50.4 See also - 3.51 trunk/Scripts/Python + 3.51 trunk/Translations/Identity 3.51.1 Goals 3.51.2 Description 3.51.3 Usage 3.51.4 See also - 3.52 trunk/Translations + 3.52 trunk/Translations/Identity/Brands 3.52.1 Goals 3.52.2 Description - 3.52.2.1 Translation Entries - 3.52.2.2 Translation Markers - 3.52.2.3 Translation Files - 3.52.2.4 Template Translation Files - 3.52.2.5 Common Translation Files - 3.52.2.6 Specific Translation Files - 3.52.2.7 Translation Rendering - 3.52.2.8 Translation (Pre-)Rendering Configuration Scripts - 3.52.2.9 Translation Rendering Default Functionality + 3.52.2.1 Conventional file names + 3.52.2.2 Numeric file names + 3.52.2.3 Translation markers 3.52.3 Usage 3.52.4 See also - 3.53 trunk/Translations/Identity + 3.53 trunk/Translations/Identity/Brands/Tpl 3.53.1 Goals 3.53.2 Description 3.53.3 Usage 3.53.4 See also - 3.54 trunk/Translations/Identity/Brands + 3.54 trunk/Translations/Identity/Fonts 3.54.1 Goals 3.54.2 Description - 3.54.2.1 Conventional file names - 3.54.2.2 Numeric file names - 3.54.2.3 Translation markers + 3.54.2.1 Translation Markers 3.54.3 Usage 3.54.4 See also - 3.55 trunk/Translations/Identity/Brands/Tpl + 3.55 trunk/Translations/Identity/Models 3.55.1 Goals 3.55.2 Description 3.55.3 Usage 3.55.4 See also - 3.56 trunk/Translations/Identity/Fonts + 3.56 trunk/Translations/Identity/Release 3.56.1 Goals 3.56.2 Description - 3.56.2.1 Translation Markers 3.56.3 Usage 3.56.4 See also - 3.57 trunk/Translations/Identity/Models + 3.57 trunk/Translations/Identity/Themes 3.57.1 Goals 3.57.2 Description 3.57.3 Usage 3.57.4 See also - 3.58 trunk/Translations/Identity/Release + 3.58 trunk/Translations/Identity/Themes/Backgrounds 3.58.1 Goals 3.58.2 Description 3.58.3 Usage 3.58.4 See also - 3.59 trunk/Translations/Identity/Themes + 3.59 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress 3.59.1 Goals 3.59.2 Description 3.59.3 Usage 3.59.4 See also - 3.60 trunk/Translations/Identity/Themes/Backgrounds + 3.60 trunk/Translations/Identity/Widgets 3.60.1 Goals 3.60.2 Description 3.60.3 Usage 3.60.4 See also - 3.61 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress - 3.61.1 Goals - 3.61.2 Description - 3.61.3 Usage - 3.61.4 See also - 3.62 trunk/Translations/Identity/Widgets - 3.62.1 Goals - 3.62.2 Description - 3.62.3 Usage - 3.62.4 See also Index List of Figures @@ -1968,74 +1958,32 @@ visual identity. 3.23.5 See also --------------- -3.24 trunk/Identity/Themes/Motifs/Flame/Distro/Anaconda -======================================================= - -3.24.1 Goals ------------- - - * ... - -3.24.2 Description ------------------- - - * ... - -3.24.3 Usage ------------- - - * ... - -3.24.4 See also ---------------- - -3.25 trunk/Identity/Themes/Motifs/Flame/Distro/BootUp -===================================================== - -3.25.1 Goals ------------- - - * ... - -3.25.2 Description ------------------- - - * ... - -3.25.3 Usage ------------- - - * ... - -3.25.4 See also ---------------- - -3.26 trunk/Identity/Themes/Motifs/Modern +3.24 trunk/Identity/Themes/Motifs/Modern ======================================== -3.26.1 Presentation +3.24.1 Presentation ------------------- - 3.26.2 Construction + 3.24.2 Construction ------------------- -3.26.3 Usage +3.24.3 Usage ------------ * ... -3.26.4 See also +3.24.4 See also --------------- -3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds +3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds ==================================================== -3.27.1 Goals +3.25.1 Goals ------------ * Organize background images for Modern theme. -3.27.2 Description +3.25.2 Description ------------------ Inside motif's `Backgrounds/' directory you can create vectorial @@ -2137,7 +2085,7 @@ directory structure as reference. images automatically. This section describes each directory of CentOS artistic motif base structure. -3.27.3 Usage +3.25.3 Usage ------------ The motif's `Backgrounds/' directory is probably the motif's core @@ -2146,65 +2094,65 @@ background images used by almost all theme models (e.g., Distribution, Websites, Promotion, etc.). The motif's `Backgrounds/' directory can contain subdirectories to help you organize the design process. -3.27.4 See also +3.25.4 See also --------------- -3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img +3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img ======================================================== -3.28.1 Goals +3.26.1 Goals ------------ * ... -3.28.2 Description +3.26.2 Description ------------------ -3.28.3 Usage +3.26.3 Usage ------------ In this directory is where you store all background images (e.g., .png, .jpg, .xpm, etc.). This directory is required by `centos-art' command line interface. -3.28.4 See also +3.26.4 See also --------------- -3.29 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl +3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl ======================================================== -3.29.1 Goals +3.27.1 Goals ------------ * ... -3.29.2 Description +3.27.2 Description ------------------ -3.29.3 Usage +3.27.3 Usage ------------ In this directory is where you store all the scalable vector graphics (e.g., .svg) files. This directory is required by `centos-art' command line interface. -3.29.4 See also +3.27.4 See also --------------- -3.30 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf +3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf ======================================================== -3.30.1 Goals +3.28.1 Goals ------------ * ... -3.30.2 Description +3.28.2 Description ------------------ * ... -3.30.3 Usage +3.28.3 Usage ------------ In this directory is where you store Gimp's project files (e.g, .xcf). @@ -2215,21 +2163,21 @@ store Gimp's background projects. Of course, you can merge Gimp's power with Inkscape's power to produce images based on them. In this last case you need the `Xcf/' directory. -3.30.4 See also +3.28.4 See also --------------- -3.31 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress +3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress ================================================================= -3.31.1 Goals +3.29.1 Goals ------------ * ... -3.31.2 Description +3.29.2 Description ------------------ -3.31.3 Usage +3.29.3 Usage ------------ To render Anaconda progress slide images using the Modern's artistic @@ -2271,21 +2219,21 @@ use the following commands: |-- 02-donate.png `-- 03-yum.png -3.31.4 See also +3.29.4 See also --------------- -3.32 trunk/Identity/Themes/Motifs/Modern/Palettes +3.30 trunk/Identity/Themes/Motifs/Modern/Palettes ================================================= -3.32.1 Goals +3.30.1 Goals ------------ * Organize palette files for Modern theme. -3.32.2 Description +3.30.2 Description ------------------ -3.32.3 Usage +3.30.3 Usage ------------ Here is where graphic designers define theme palettes for color-limited @@ -2293,38 +2241,38 @@ art works. Theme palettes contain the color information that rendering functions need, in order to produce images with color limitations. Theme palettes contain theme's unique color information. -3.32.4 See also +3.30.4 See also --------------- -3.33 trunk/Identity/Themes/Motifs/TreeFlower +3.31 trunk/Identity/Themes/Motifs/TreeFlower ============================================ -3.33.1 Goals +3.31.1 Goals ------------ * ... -3.33.2 Description +3.31.2 Description ------------------ -3.33.3 Usage +3.31.3 Usage ------------ -3.33.4 See also +3.31.4 See also --------------- -3.34 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds +3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds ======================================================== -3.34.1 Goals +3.32.1 Goals ------------ This section exists to orgnize TreeFlower's backgrounds. -3.34.2 Description +3.32.2 Description ------------------ -3.34.2.1 Desktop background +3.32.2.1 Desktop background ........................... Once you have defined the vectorial artistic motif design, use the @@ -2408,7 +2356,7 @@ vectorial design plus `-final.png' extension. You can repeat these steps to create images for other screen resolutions. -3.34.2.2 Anaconda Prompt (syslinux) background +3.32.2.2 Anaconda Prompt (syslinux) background .............................................. When building syslinux backgrounds it is needed to take into account @@ -2598,48 +2546,48 @@ following `syslinux.hex' file: #9e999c=14 #c9c4c3=15 -3.34.2.3 Grub background +3.32.2.3 Grub background ........................ -3.34.3 Usage +3.32.3 Usage ------------ * ... -3.34.4 See also +3.32.4 See also --------------- -3.35 trunk/Identity/Widgets +3.33 trunk/Identity/Widgets =========================== -3.35.1 Goals +3.33.1 Goals ------------ * ... -3.35.2 Description +3.33.2 Description ------------------ -3.35.3 Usage +3.33.3 Usage ------------ -3.35.4 See also +3.33.4 See also --------------- -3.36 trunk/Manuals +3.34 trunk/Manuals ================== -3.36.1 Goals +3.34.1 Goals ------------ * ... -3.36.2 Description +3.34.2 Description ------------------ * ... -3.36.3 Usage +3.34.3 Usage ------------ `centos-art help --read='path/to/dir'' @@ -2677,13 +2625,13 @@ following `syslinux.hex' file: Use this command to remove file documentation as specified in `path/to/dir/filename' combination. -3.36.4 See also +3.34.4 See also --------------- -3.37 trunk/Scripts +3.35 trunk/Scripts ================== -3.37.1 Goals +3.35.1 Goals ------------ The `trunk/Scripts' directory exists to: @@ -2691,23 +2639,23 @@ The `trunk/Scripts' directory exists to: * Organize the "trunk" development line of automation scripts by programming language. -3.37.2 Description +3.35.2 Description ------------------ * ... -3.37.3 Usage +3.35.3 Usage ------------ * ... -3.37.4 See also +3.35.4 See also --------------- -3.38 trunk/Scripts/Bash +3.36 trunk/Scripts/Bash ======================= -3.38.1 Goals +3.36.1 Goals ------------ The `trunk/Scripts/Bash' directory exists to organize the trunk @@ -2715,7 +2663,7 @@ development line of `centos-art.sh' automation script. The `centos-art.sh' script standardizes frequent tasks inside your working copy of CentOS Artwork Repository. -3.38.2 Description +3.36.2 Description ------------------ The best way to understand `centos-art.sh' automation script is @@ -2807,25 +2755,25 @@ achive the rendering task as it defines. Figure 3.1: The `centos-art.sh' initialization environment. -3.38.3 Usage +3.36.3 Usage ------------ The `centos-art.sh' script usage information is described inside each specific function documentation (*note trunk Scripts Bash Functions::). -3.38.4 See also +3.36.4 See also --------------- -3.39 trunk/Scripts/Bash/Functions +3.37 trunk/Scripts/Bash/Functions ================================= -3.39.1 Goals +3.37.1 Goals ------------ The `trunk/Scripts/Bash/Functions' directory exists to organize `centos-art.sh' specific functionalities. -3.39.2 Description +3.37.2 Description ------------------ The specific functions of `centos-art.sh' script are designed with @@ -3095,10 +3043,10 @@ specific functionalities. By the way, the `greet' functionality doesn't exist inside `centos-art.sh' script yet. Would you like to create it? -3.39.3 Usage +3.37.3 Usage ------------ -3.39.3.1 Global variables +3.37.3.1 Global variables ......................... The following global variables of `centos-art.sh' script, are available @@ -3286,7 +3234,7 @@ for you to use inside specific functions: If no one of these values is set in `EDITOR' environment variable, `centos-art.sh' uses `/usr/bin/vim' text editor by default. -3.39.3.2 Global functions +3.37.3.2 Global functions ......................... The following global functions of `centos-art.sh' script are available @@ -3675,29 +3623,29 @@ for you to use inside specific functions: Use `cli_printMessage' function whenever you need to output information from `centos-art.sh' script. -3.39.3.3 Specific functions +3.37.3.3 Specific functions ........................... The following specific functions of `centos-art.sh' script, are available for you to use: -3.39.4 See also +3.37.4 See also --------------- -3.40 trunk/Scripts/Bash/Functions/Help +3.38 trunk/Scripts/Bash/Functions/Help ====================================== -3.40.1 Goals +3.38.1 Goals ------------ * ... -3.40.2 Description +3.38.2 Description ------------------ * ... -3.40.2.1 Output different formats +3.38.2.1 Output different formats ................................. Remove -I option from info and plaintext output. Before output info and @@ -3727,44 +3675,44 @@ to image, no matter where you execute the centos-art.sh help command. absolute locations. This is intentional. Such configuration let us maintain documentation and images independently one another. -3.40.3 Usage +3.38.3 Usage ------------ * ... -3.40.4 See also +3.38.4 See also --------------- -3.41 trunk/Scripts/Bash/Functions/Html +3.39 trunk/Scripts/Bash/Functions/Html ====================================== -3.41.1 Goals +3.39.1 Goals ------------ * ... -3.41.2 Description +3.39.2 Description ------------------ * ... -3.41.3 Usage +3.39.3 Usage ------------ * ... -3.41.4 See also +3.39.4 See also --------------- -3.42 trunk/Scripts/Bash/Functions/Locale +3.40 trunk/Scripts/Bash/Functions/Locale ======================================== -3.42.1 Goals +3.40.1 Goals ------------ * ... -3.42.2 Description +3.40.2 Description ------------------ This command looks for `.sh' files inside Bash directory and extracts @@ -3822,7 +3770,7 @@ following files: * ... -3.42.3 Usage +3.40.3 Usage ------------ `centos-art locale --edit' @@ -3833,13 +3781,13 @@ following files: `centos-art locale --list' Use this command to see the command-line interface locale report. -3.42.4 See also +3.40.4 See also --------------- -3.43 trunk/Scripts/Bash/Functions/Path +3.41 trunk/Scripts/Bash/Functions/Path ====================================== -3.43.1 Goals +3.41.1 Goals ------------ This section exists to organize files related to `path' @@ -3847,14 +3795,14 @@ functiontionality of `centos-art.sh' script. The `path' functionality of `centos-art.sh' script standardizes movement, syncronization, branching, tagging, and general file maintainance inside the repository. -3.43.2 Description +3.41.2 Description ------------------ _"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."_ -3.43.2.1 Repository layout +3.41.2.1 Repository layout .......................... The repository layout describes organization of files and directories @@ -3899,7 +3847,7 @@ single copy of the master sources. This copy is called the source "repository"; it contains all the information to permit extracting previous versions of those files at any time. -3.43.2.2 Repository name convenctions +3.41.2.2 Repository name convenctions ..................................... Repository name convenctions help us to maintain consistency of names @@ -3918,7 +3866,7 @@ etc.). convenctions you need to remember concentrating them in just one single place you can look for fixes and improvements. -3.43.2.3 Repository work flow +3.41.2.3 Repository work flow ............................. Repository work flow describes the steps and time intervals used to @@ -3988,7 +3936,7 @@ been frozen (under `tags/' directory), CentOS Packagers (the persons who build CentOS distribution) can use that frozen branch as source location to fulfill CentOS distribution artwork needs. -3.43.2.4 Parallel directories +3.41.2.4 Parallel directories ............................. Inside CentOS Artwork Repository, parallel directories are simple @@ -4041,7 +3989,7 @@ initially created for. Figure 3.7: Wrong construction of parallel directories. -3.43.2.5 Syncronizing path information +3.41.2.5 Syncronizing path information ...................................... Creating parallel directories is very useful to keep repository @@ -4096,7 +4044,7 @@ related files. Updating path references inside related files is specially important for documentation files where documentation nodes are built using repository path information as reference. -3.43.2.6 What is the right location to store it? +3.41.2.6 What is the right location to store it? ................................................ Occasionly, you may find that new corporate visual identity components @@ -4148,7 +4096,7 @@ centos-art help --read=turnk/Identity/Themes/Motifs/TreeFlower/Distro/ change the location we used above by the one you are trying to know concepts for. -3.43.3 Usage +3.41.3 Usage ------------ `centos-art path --copy=SRC --to=DST' @@ -4234,40 +4182,40 @@ concepts for. inside `trunk/Identity/' location, considered the parent directory you want to syncronize path information for. -3.43.4 See also +3.41.4 See also --------------- -3.44 trunk/Scripts/Bash/Functions/Render +3.42 trunk/Scripts/Bash/Functions/Render ======================================== -3.44.1 Goals +3.42.1 Goals ------------ * ... -3.44.2 Description +3.42.2 Description ------------------ * ... -3.44.3 Usage +3.42.3 Usage ------------ * ... -3.44.4 See also +3.42.4 See also --------------- -3.45 trunk/Scripts/Bash/Functions/Render/Config +3.43 trunk/Scripts/Bash/Functions/Render/Config =============================================== -3.45.1 Goals +3.43.1 Goals ------------ The `trunk/Scripts/Bash/Config' directory exists to oraganize pre-rendering configuration scripts. -3.45.2 Description +3.43.2 Description ------------------ Pre-rendering configuration scripts let you customize the way @@ -4281,7 +4229,7 @@ both on identity and translation repository entires. Pre-rendering configuration entries are required for each identity entry, but not for translation entries. -3.45.2.1 The `render.conf.sh' identity model +3.43.2.1 The `render.conf.sh' identity model ............................................ Inside CentOS Artwork Repository, we consider identity entries to all @@ -4324,7 +4272,7 @@ extend both image-based and text-based pre-rendering configuration scripts using image-based and text-based post-rendering actions, respectively. -3.45.2.2 The `render.conf.sh' translation model +3.43.2.2 The `render.conf.sh' translation model ............................................... Translation pre-rendering configuration scripts take precedence before @@ -4332,7 +4280,7 @@ default translation rendering action. Translation pre-rendering actions are useful when default translation rendering action do not fit itself to translation entry rendering requirements. -3.45.2.3 The `render.conf.sh' rendering actions +3.43.2.3 The `render.conf.sh' rendering actions ............................................... Inside both image-based and text-based identity pre-rendering @@ -4406,7 +4354,7 @@ ACTIONS[0]='BASE:renderImage' ACTIONS[1]='POST:renderFormats: xpm jpg tif' ACTIONS[2]='LAST:groupByformat: png xpm jpg tif' -3.45.3 Usage +3.43.3 Usage ------------ Use the following commands to administer both identity and translation @@ -4433,19 +4381,19 @@ pre-rendering configuration scripts: directory path under `trunk/Identity' or `trunk/Translations' structures only. -3.45.4 See also +3.43.4 See also --------------- -3.46 trunk/Scripts/Bash/Functions/Shell +3.44 trunk/Scripts/Bash/Functions/Shell ======================================= -3.46.1 Goals +3.44.1 Goals ------------ This section exists to organize files related to `shell' functionality of `centos-art.sh' script. -3.46.2 Description +3.44.2 Description ------------------ The `shell' functionality of `centos-art.sh' script helps you to @@ -4571,7 +4519,7 @@ for changes to take effect over the files you specify. be used, please share your reasons at CentOS Developers mailing list . -3.46.3 Usage +3.44.3 Usage ------------ `centos-art sh --update-copyright='path/to/dir'' @@ -4601,19 +4549,19 @@ inside the list of files to process. matches a regular file; the `centos-art.sh' script uses the file matching as only file in the list of files to process. -3.46.4 See also +3.44.4 See also --------------- -3.47 trunk/Scripts/Bash/Functions/Svg +3.45 trunk/Scripts/Bash/Functions/Svg ===================================== -3.47.1 Goals +3.45.1 Goals ------------ This section exists to organize files related to `svg' functionality of `centos-art.sh' script. -3.47.2 Description +3.45.2 Description ------------------ The `svg' functionality of `centos-art.sh' script helps you to maintain @@ -4625,7 +4573,7 @@ files. Doing so file by file may be a tedious task, so the `centos-art.sh' script provides the `svg' functionality to aid you maintain such actions. -3.47.2.1 Metadata maintainance +3.45.2.1 Metadata maintainance .............................. The metadata used is defined by Inkscape 0.46 using the SVG standard @@ -4732,7 +4680,7 @@ Creative Common Attribution Share-Alike 3.0 License to grant license consistency among all SVG files we manage inside CentOS Artwork Repository. -3.47.2.2 Unused definitions +3.45.2.2 Unused definitions ........................... As SVG files grow they may end up with unused definitions inside. For @@ -4752,7 +4700,7 @@ those files one by one. `centos-art.sh' script uses Inkscape's command-line interface, specifically with the `--vaccum-defs' option. -3.47.3 Usage +3.45.3 Usage ------------ `centos-art svg --update-metadata='path/to/dir'' @@ -4789,13 +4737,13 @@ inside the list of files to process. matches a regular file; the `centos-art.sh' script uses the file matching as only file in the list of files to process. -3.47.4 See also +3.45.4 See also --------------- -3.48 trunk/Scripts/Bash/Functions/Verify +3.46 trunk/Scripts/Bash/Functions/Verify ======================================== -3.48.1 Goals +3.46.1 Goals ------------ This section exists to organize files related to `centos-art.sh' script @@ -4804,7 +4752,7 @@ script helps you to verify the workstation configuration you are planning to use as host for your working copy of CentOS Artwork Repository. -3.48.2 Description +3.46.2 Description ------------------ The first time you download CentOS Artwork Repository you need to @@ -4822,7 +4770,7 @@ appropriate way to use its `verify' functionality is not using the because `centos-art' symbolic link, under `~/bin/' directory, has not been created yet. -3.48.2.1 Packages +3.46.2.1 Packages ................. Installation of auxiliar RPM packages provides the software required to @@ -4852,7 +4800,7 @@ please read its man page running the command: `man sudo'. This reading will be very useful, and with some practice, you will be able to configure your users to have `sudo' privileges. -3.48.2.2 Links +3.46.2.2 Links .............. Creation of symbolic links helps us to alternate between different @@ -4886,7 +4834,7 @@ you need to use the "render" functionality of `centos-art.sh' under configuration, automation scripts cannot be branched under `branches/Scripts' directory structure. -3.48.2.3 Environment variables +3.46.2.3 Environment variables .............................. Definition of environemnt variables helps us to set default values to @@ -4959,7 +4907,7 @@ following environment variables: `centos-art.sh' script (*note trunk Scripts Bash Functions Locale::, for more information). -3.48.3 Usage +3.46.3 Usage ------------ `centos-art verify --packages' @@ -5005,19 +4953,19 @@ following environment variables: outputs information as if `--filter' option had not been provided at all. -3.48.4 See also +3.46.4 See also --------------- -3.49 trunk/Scripts/Bash/Locale +3.47 trunk/Scripts/Bash/Locale ============================== -3.49.1 Goals +3.47.1 Goals ------------ This section exists to organize translation messages and templates used by `centos-art.sh' script. -3.49.2 Description +3.47.2 Description ------------------ Translated messages of `centos-art.sh' script are managed using GNU @@ -5025,7 +4973,7 @@ Translated messages of `centos-art.sh' script are managed using GNU through `centos-art.sh' script "locale" functionality (*note trunk Scripts Bash Functions Locale::). -3.49.3 Usage +3.47.3 Usage ------------ The content of `trunk/Scripts/Bash/Locale' directory should not be @@ -5034,51 +4982,51 @@ managed manually. Instead, use the "locale" functionality of for more information on how to use `centos-art.sh' "locale" functionality. -3.49.4 See also +3.47.4 See also --------------- -3.50 trunk/Scripts/Perl +3.48 trunk/Scripts/Perl ======================= -3.50.1 Goals +3.48.1 Goals ------------ * ... -3.50.2 Description +3.48.2 Description ------------------ -3.50.3 Usage +3.48.3 Usage ------------ -3.50.4 See also +3.48.4 See also --------------- -3.51 trunk/Scripts/Python +3.49 trunk/Scripts/Python ========================= -3.51.1 Goals +3.49.1 Goals ------------ * ... -3.51.2 Description +3.49.2 Description ------------------ * ... -3.51.3 Usage +3.49.3 Usage ------------ * ... -3.51.4 See also +3.49.4 See also --------------- -3.52 trunk/Translations +3.50 trunk/Translations ======================= -3.52.1 Goals +3.50.1 Goals ------------ The `trunk/Translations' directory exists to: @@ -5087,7 +5035,7 @@ The `trunk/Translations' directory exists to: * Organize translation templates used to produce translation files. -3.52.2 Description +3.50.2 Description ------------------ When you create artwork for CentOS distribution you find that some @@ -5124,7 +5072,7 @@ production line is stored under `trunk/Translations' directory. to organize artworks' "translation files" and artworks' "translation templates". -3.52.2.1 Translation Entries +3.50.2.1 Translation Entries ............................ Translation entries exists for each artwork you want to produce. @@ -5205,7 +5153,7 @@ Repository, graphic designers can concentrate their efforts in artworks look and feel (the identity entries), and translators in artworks translations (the translation entries). -3.52.2.2 Translation Markers +3.50.2.2 Translation Markers ............................ Translation markers are used in "Theme Model Designs" and "Translation @@ -5240,7 +5188,7 @@ 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. -3.52.2.3 Translation Files +3.50.2.3 Translation Files .......................... Translation files are text files with `sed''s commands inside, @@ -5308,7 +5256,7 @@ release-specific translation files, run the translation rendering command with the release number you want to produce translation files for in the `--filter='release-number'' argument. -3.52.2.4 Template Translation Files +3.50.2.4 Template Translation Files ................................... Template translation files are translation files stored inside @@ -5478,7 +5426,7 @@ replacement command is defined _after_ `=MAJOR_RELASE=' translation marker definition in the REPLACEMENT of `=TITLE=' translation marker replacement command. -3.52.2.5 Common Translation Files +3.50.2.5 Common Translation Files ................................. Common translation files contain common translations or no translation @@ -5503,7 +5451,7 @@ trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ | `-- splash-small.sed `-- firstboot-left.sed <-- common translation file. -3.52.2.6 Specific Translation Files +3.50.2.6 Specific Translation Files ................................... Specific translation files contain specific translations for their @@ -5526,7 +5474,7 @@ trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ | `-- splash-small.sed `-- firstboot-left.sed -3.52.2.7 Translation Rendering +3.50.2.7 Translation Rendering .............................. When rendering translations, the `centos-art' script checks the @@ -5537,7 +5485,7 @@ files. If the translation template directory doesn't exist inside the translation entry the translation rendering fails. In this case the `centos-art' script outputs a message and quits script execution. -3.52.2.8 Translation (Pre-)Rendering Configuration Scripts +3.50.2.8 Translation (Pre-)Rendering Configuration Scripts .......................................................... When the `centos-art' script finds a translation template directory @@ -5623,7 +5571,7 @@ pre-rendering configuration example, the translation pre-rendering configuration file that `centos-art' looks for, inside the above translation pre-rendering configuration directory, is `render.conf.sh'. -3.52.2.9 Translation Rendering Default Functionality +3.50.2.9 Translation Rendering Default Functionality .................................................... In the other hand, if the translation pre-rendering configuration file @@ -5648,7 +5596,7 @@ commands. translation marker section (*note Translation Markers: trunk:Translations:TranslationMarkers.). -3.52.3 Usage +3.50.3 Usage ------------ `centos-art render --entry='path/to/dir'' @@ -5665,7 +5613,7 @@ commands. `3,4,5,6') that specify the major release of CentOS distribution you want to render translations for. -3.52.4 See also +3.50.4 See also --------------- ---------- Footnotes ---------- @@ -5677,36 +5625,36 @@ mainly based on CentOS 5 rebranding experience. (3) This value was taken from the `locale -a' command's output. -3.53 trunk/Translations/Identity +3.51 trunk/Translations/Identity ================================ -3.53.1 Goals +3.51.1 Goals ------------ * ... -3.53.2 Description +3.51.2 Description ------------------ * ... -3.53.3 Usage +3.51.3 Usage ------------ * ... -3.53.4 See also +3.51.4 See also --------------- -3.54 trunk/Translations/Identity/Brands +3.52 trunk/Translations/Identity/Brands ======================================= -3.54.1 Goals +3.52.1 Goals ------------ * Organize brands' translation files. -3.54.2 Description +3.52.2 Description ------------------ Translation files, inside `trunk/Translations/Identity/Brands' @@ -5739,7 +5687,7 @@ script considers translation symbolic links as translation files. Translation file names, inside brands' translation template (`Tpl') directory have special meaning: -3.54.2.1 Conventional file names +3.52.2.1 Conventional file names ................................ Convenctional file names look like `blue.sed', `2c-a.sed', etc. @@ -5747,7 +5695,7 @@ 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. -3.54.2.2 Numeric file names +3.52.2.2 Numeric file names ........................... Numeric file names look like `300.sed', `200.sed', etc. Replacements @@ -5768,7 +5716,7 @@ 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. -3.54.2.3 Translation markers +3.52.2.3 Translation markers ............................ Inside `trunk/Translations/Identity/Brands/', translation files combine @@ -5782,7 +5730,7 @@ the following translation markers: point to template translation files, translation markers are defined inside template translation files. -3.54.3 Usage +3.52.3 Usage ------------ To render brands' translation files, use the following command: @@ -5790,33 +5738,33 @@ To render brands' translation files, use the following command: centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands -3.54.4 See also +3.52.4 See also --------------- -3.55 trunk/Translations/Identity/Brands/Tpl +3.53 trunk/Translations/Identity/Brands/Tpl =========================================== -3.55.1 Goals +3.53.1 Goals ------------ -3.55.2 Description +3.53.2 Description ------------------ -3.55.3 Usage +3.53.3 Usage ------------ -3.55.4 See also +3.53.4 See also --------------- -3.56 trunk/Translations/Identity/Fonts +3.54 trunk/Translations/Identity/Fonts ====================================== -3.56.1 Goals +3.54.1 Goals ------------ This section exists to organize fonts translation files. -3.56.2 Description +3.54.2 Description ------------------ Translation files, inside `trunk/Translations/Fonts', have the @@ -5838,7 +5786,7 @@ visual identity. someone needs to know which font-families are allowed to use inside CentOS visual identity. -3.56.2.1 Translation Markers +3.54.2.1 Translation Markers ............................ Inside `trunk/Translations/Identity/Fonts', translation files combine @@ -5855,7 +5803,7 @@ the following translation markers: `font-style:normal' Specify which font style to use when rendering font preview images. -3.56.3 Usage +3.54.3 Usage ------------ Inside `trunk/Translations/Fonts' you use your favorite text editor to @@ -5868,79 +5816,79 @@ type the following command: vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed -3.56.4 See also +3.54.4 See also --------------- -3.57 trunk/Translations/Identity/Models +3.55 trunk/Translations/Identity/Models ======================================= -3.57.1 Goals +3.55.1 Goals ------------ -3.57.2 Description +3.55.2 Description ------------------ -3.57.3 Usage +3.55.3 Usage ------------ -3.57.4 See also +3.55.4 See also --------------- -3.58 trunk/Translations/Identity/Release +3.56 trunk/Translations/Identity/Release ======================================== -3.58.1 Goals +3.56.1 Goals ------------ -3.58.2 Description +3.56.2 Description ------------------ -3.58.3 Usage +3.56.3 Usage ------------ -3.58.4 See also +3.56.4 See also --------------- -3.59 trunk/Translations/Identity/Themes +3.57 trunk/Translations/Identity/Themes ======================================= -3.59.1 Goals +3.57.1 Goals ------------ -3.59.2 Description +3.57.2 Description ------------------ -3.59.3 Usage +3.57.3 Usage ------------ -3.59.4 See also +3.57.4 See also --------------- -3.60 trunk/Translations/Identity/Themes/Backgrounds +3.58 trunk/Translations/Identity/Themes/Backgrounds =================================================== -3.60.1 Goals +3.58.1 Goals ------------ * ... -3.60.2 Description +3.58.2 Description ------------------ * ... -3.60.3 Usage +3.58.3 Usage ------------ * ... -3.60.4 See also +3.58.4 See also --------------- -3.61 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress +3.59 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress ================================================================ -3.61.1 Goals +3.59.1 Goals ------------ * Organize Anaconda progress translation templates. @@ -5948,7 +5896,7 @@ vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.se * Organize Anaconda progress translation files in several languages and major releases of CentOS distribution. -3.61.2 Description +3.59.2 Description ------------------ Use the following command to produce translation files based: @@ -6021,129 +5969,127 @@ structure and render them. * *Note trunk Identity Themes Motifs Modern Distro Anaconda Progress::. -3.61.3 Usage +3.59.3 Usage ------------ Translation rendering is described in `trunk/Translations' documentation entry (*note trunk Translations::). -3.61.4 See also +3.59.4 See also --------------- -3.62 trunk/Translations/Identity/Widgets +3.60 trunk/Translations/Identity/Widgets ======================================== -3.62.1 Goals +3.60.1 Goals ------------ * ... -3.62.2 Description +3.60.2 Description ------------------ * ... -3.62.3 Usage +3.60.3 Usage ------------ * ... -3.62.4 See also +3.60.4 See also --------------- Index ***** -branches: See 1. (line 401) -Common translation files: See 3.52.2.5. (line 5484) -How to render brands' translation files: See 3.54.3. (line 5788) -How to render fonts' translation files: See 3.56.3. (line 5861) -How to render translation files: See 3.52.3. (line 5654) -Metadata maintainance: See 3.47.2. (line 4628) -Specific translation files: See 3.52.2.6. (line 5509) -tags: See 2. (line 404) -Template translation files: See 3.52.2.4. (line 5314) -Translation brands file names: See 3.54.2.1. (line 5745) -Translation configuration scripts: See 3.52.2.8. (line 5543) -Translation entries: See 3.52.2.1. (line 5130) -Translation files: See 3.52.2.3. (line 5246) -Translation markers: See 3.52.2.2. (line 5211) -Translation paths: See 3.52.2.1. (line 5130) -Translation pre-rendering configuration scripts:See 3.52.2.8. - (line 5543) -Translation rendering: See 3.52.2.7. (line 5532) -Translation rendering default functionality: See 3.52.2.9. (line 5629) -trunk: See 3. (line 407) -trunk Identity: See 3.1. (line 410) -trunk Identity Brands: See 3.2. (line 830) -trunk Identity Fonts: See 3.3. (line 847) -trunk Identity Icons: See 3.4. (line 924) -trunk Identity Isolinux: See 3.5. (line 941) -trunk Identity Models: See 3.6. (line 958) -trunk Identity Models Css: See 3.7. (line 978) -trunk Identity Models Html: See 3.8. (line 1000) -trunk Identity Models Img Promo Web: See 3.9. (line 1021) -trunk Identity Models Tpl: See 3.10. (line 1042) -trunk Identity Models Tpl Promo Web: See 3.11. (line 1063) -trunk Identity Models Xcf: See 3.12. (line 1377) -trunk Identity Release: See 3.13. (line 1398) -trunk Identity Themes: See 3.14. (line 1415) -trunk Identity Themes Models: See 3.15. (line 1440) -trunk Identity Themes Models Alternative: See 3.16. (line 1473) -trunk Identity Themes Models Default: See 3.17. (line 1500) -trunk Identity Themes Models Default Distro: See 3.18. (line 1532) +branches: See 1. (line 391) +Common translation files: See 3.50.2.5. (line 5432) +How to render brands' translation files: See 3.52.3. (line 5736) +How to render fonts' translation files: See 3.54.3. (line 5809) +How to render translation files: See 3.50.3. (line 5602) +Metadata maintainance: See 3.45.2. (line 4576) +Specific translation files: See 3.50.2.6. (line 5457) +tags: See 2. (line 394) +Template translation files: See 3.50.2.4. (line 5262) +Translation brands file names: See 3.52.2.1. (line 5693) +Translation configuration scripts: See 3.50.2.8. (line 5491) +Translation entries: See 3.50.2.1. (line 5078) +Translation files: See 3.50.2.3. (line 5194) +Translation markers: See 3.50.2.2. (line 5159) +Translation paths: See 3.50.2.1. (line 5078) +Translation pre-rendering configuration scripts:See 3.50.2.8. + (line 5491) +Translation rendering: See 3.50.2.7. (line 5480) +Translation rendering default functionality: See 3.50.2.9. (line 5577) +trunk: See 3. (line 397) +trunk Identity: See 3.1. (line 400) +trunk Identity Brands: See 3.2. (line 820) +trunk Identity Fonts: See 3.3. (line 837) +trunk Identity Icons: See 3.4. (line 914) +trunk Identity Isolinux: See 3.5. (line 931) +trunk Identity Models: See 3.6. (line 948) +trunk Identity Models Css: See 3.7. (line 968) +trunk Identity Models Html: See 3.8. (line 990) +trunk Identity Models Img Promo Web: See 3.9. (line 1011) +trunk Identity Models Tpl: See 3.10. (line 1032) +trunk Identity Models Tpl Promo Web: See 3.11. (line 1053) +trunk Identity Models Xcf: See 3.12. (line 1367) +trunk Identity Release: See 3.13. (line 1388) +trunk Identity Themes: See 3.14. (line 1405) +trunk Identity Themes Models: See 3.15. (line 1430) +trunk Identity Themes Models Alternative: See 3.16. (line 1463) +trunk Identity Themes Models Default: See 3.17. (line 1490) +trunk Identity Themes Models Default Distro: See 3.18. (line 1522) trunk Identity Themes Models Default Distro Anaconda:See 3.19. - (line 1616) -trunk Identity Themes Models Default Promo: See 3.20. (line 1633) -trunk Identity Themes Models Default Web: See 3.21. (line 1659) -trunk Identity Themes Motifs: See 3.22. (line 1684) -trunk Identity Themes Motifs Flame: See 3.23. (line 1788) -trunk Identity Themes Motifs Flame Distro Anaconda:See 3.24. (line 1974) -trunk Identity Themes Motifs Flame Distro BootUp:See 3.25. (line 1995) -trunk Identity Themes Motifs Modern: See 3.26. (line 2016) -trunk Identity Themes Motifs Modern Backgrounds:See 3.27. (line 2033) -trunk Identity Themes Motifs Modern Backgrounds Img:See 3.28. - (line 2155) -trunk Identity Themes Motifs Modern Backgrounds Tpl:See 3.29. - (line 2176) -trunk Identity Themes Motifs Modern Backgrounds Xcf:See 3.30. - (line 2197) -trunk Identity Themes Motifs Modern Distro Anaconda Progress:See 3.31. - (line 2224) -trunk Identity Themes Motifs Modern Palettes: See 3.32. (line 2280) -trunk Identity Themes Motifs TreeFlower: See 3.33. (line 2302) -trunk Identity Themes Motifs TreeFlower Backgrounds:See 3.34. - (line 2319) -trunk Identity Widgets: See 3.35. (line 2615) -trunk Manuals: See 3.36. (line 2632) -trunk Scripts: See 3.37. (line 2686) -trunk Scripts Bash: See 3.38. (line 2710) -trunk Scripts Bash Functions: See 3.39. (line 2822) -trunk Scripts Bash Functions Help: See 3.40. (line 3690) -trunk Scripts Bash Functions Html: See 3.41. (line 3741) -trunk Scripts Bash Functions Locale: See 3.42. (line 3762) -trunk Scripts Bash Functions Path: See 3.43. (line 3842) -trunk Scripts Bash Functions Render: See 3.44. (line 4243) -trunk Scripts Bash Functions Render Config: See 3.45. (line 4264) -trunk Scripts Bash Functions Shell: See 3.46. (line 4442) -trunk Scripts Bash Functions Svg: See 3.47. (line 4610) -trunk Scripts Bash Functions Verify: See 3.48. (line 4798) -trunk Scripts Bash Locale: See 3.49. (line 5014) -trunk Scripts Perl: See 3.50. (line 5043) -trunk Scripts Python: See 3.51. (line 5060) -trunk Translations: See 3.52. (line 5081) -trunk Translations Identity: See 3.53. (line 5683) -trunk Translations Identity Brands: See 3.54. (line 5704) -trunk Translations Identity Brands Tpl: See 3.55. (line 5799) -trunk Translations Identity Fonts: See 3.56. (line 5814) -trunk Translations Identity Models: See 3.57. (line 5877) -trunk Translations Identity Release: See 3.58. (line 5892) -trunk Translations Identity Themes: See 3.59. (line 5907) -trunk Translations Identity Themes Backgrounds:See 3.60. (line 5922) -trunk Translations Identity Themes Distro Anaconda Progress:See 3.61. - (line 5943) -trunk Translations Identity Widgets: See 3.62. (line 6036) -Unused definitions: See 3.47.2.1. (line 4735) + (line 1606) +trunk Identity Themes Models Default Promo: See 3.20. (line 1623) +trunk Identity Themes Models Default Web: See 3.21. (line 1649) +trunk Identity Themes Motifs: See 3.22. (line 1674) +trunk Identity Themes Motifs Flame: See 3.23. (line 1778) +trunk Identity Themes Motifs Modern: See 3.24. (line 1964) +trunk Identity Themes Motifs Modern Backgrounds:See 3.25. (line 1981) +trunk Identity Themes Motifs Modern Backgrounds Img:See 3.26. + (line 2103) +trunk Identity Themes Motifs Modern Backgrounds Tpl:See 3.27. + (line 2124) +trunk Identity Themes Motifs Modern Backgrounds Xcf:See 3.28. + (line 2145) +trunk Identity Themes Motifs Modern Distro Anaconda Progress:See 3.29. + (line 2172) +trunk Identity Themes Motifs Modern Palettes: See 3.30. (line 2228) +trunk Identity Themes Motifs TreeFlower: See 3.31. (line 2250) +trunk Identity Themes Motifs TreeFlower Backgrounds:See 3.32. + (line 2267) +trunk Identity Widgets: See 3.33. (line 2563) +trunk Manuals: See 3.34. (line 2580) +trunk Scripts: See 3.35. (line 2634) +trunk Scripts Bash: See 3.36. (line 2658) +trunk Scripts Bash Functions: See 3.37. (line 2770) +trunk Scripts Bash Functions Help: See 3.38. (line 3638) +trunk Scripts Bash Functions Html: See 3.39. (line 3689) +trunk Scripts Bash Functions Locale: See 3.40. (line 3710) +trunk Scripts Bash Functions Path: See 3.41. (line 3790) +trunk Scripts Bash Functions Render: See 3.42. (line 4191) +trunk Scripts Bash Functions Render Config: See 3.43. (line 4212) +trunk Scripts Bash Functions Shell: See 3.44. (line 4390) +trunk Scripts Bash Functions Svg: See 3.45. (line 4558) +trunk Scripts Bash Functions Verify: See 3.46. (line 4746) +trunk Scripts Bash Locale: See 3.47. (line 4962) +trunk Scripts Perl: See 3.48. (line 4991) +trunk Scripts Python: See 3.49. (line 5008) +trunk Translations: See 3.50. (line 5029) +trunk Translations Identity: See 3.51. (line 5631) +trunk Translations Identity Brands: See 3.52. (line 5652) +trunk Translations Identity Brands Tpl: See 3.53. (line 5747) +trunk Translations Identity Fonts: See 3.54. (line 5762) +trunk Translations Identity Models: See 3.55. (line 5825) +trunk Translations Identity Release: See 3.56. (line 5840) +trunk Translations Identity Themes: See 3.57. (line 5855) +trunk Translations Identity Themes Backgrounds:See 3.58. (line 5870) +trunk Translations Identity Themes Distro Anaconda Progress:See 3.59. + (line 5891) +trunk Translations Identity Widgets: See 3.60. (line 5984) +Unused definitions: See 3.45.2.1. (line 4683) List of Figures *************** diff --git a/Manuals/en/Texinfo/Repository/trunk/chapter-menu.texi b/Manuals/en/Texinfo/Repository/trunk/chapter-menu.texi index fa19e94..183ee3e 100644 --- a/Manuals/en/Texinfo/Repository/trunk/chapter-menu.texi +++ b/Manuals/en/Texinfo/Repository/trunk/chapter-menu.texi @@ -22,8 +22,6 @@ * trunk Identity Themes Models Default Web:: * trunk Identity Themes Motifs:: * trunk Identity Themes Motifs Flame:: -* trunk Identity Themes Motifs Flame Distro Anaconda:: -* trunk Identity Themes Motifs Flame Distro BootUp:: * trunk Identity Themes Motifs Modern:: * trunk Identity Themes Motifs Modern Backgrounds:: * trunk Identity Themes Motifs Modern Backgrounds Img:: diff --git a/Manuals/en/Texinfo/Repository/trunk/chapter-nodes.texi b/Manuals/en/Texinfo/Repository/trunk/chapter-nodes.texi index 49a0583..b921520 100644 --- a/Manuals/en/Texinfo/Repository/trunk/chapter-nodes.texi +++ b/Manuals/en/Texinfo/Repository/trunk/chapter-nodes.texi @@ -113,16 +113,6 @@ @cindex trunk Identity Themes Motifs Flame @include trunk/Identity/Themes/Motifs/Flame.texi -@node trunk Identity Themes Motifs Flame Distro Anaconda -@section trunk/Identity/Themes/Motifs/Flame/Distro/Anaconda -@cindex trunk Identity Themes Motifs Flame Distro Anaconda -@include trunk/Identity/Themes/Motifs/Flame/Distro/Anaconda.texi - -@node trunk Identity Themes Motifs Flame Distro BootUp -@section trunk/Identity/Themes/Motifs/Flame/Distro/BootUp -@cindex trunk Identity Themes Motifs Flame Distro BootUp -@include trunk/Identity/Themes/Motifs/Flame/Distro/BootUp.texi - @node trunk Identity Themes Motifs Modern @section trunk/Identity/Themes/Motifs/Modern @cindex trunk Identity Themes Motifs Modern