From b8013f49344f77cfd31a5849dfc93796d8e33958 Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: Oct 29 2010 11:48:22 +0000 Subject: Update documentation manuals. --- diff --git a/Manuals/en/Html/Repository/repository.html b/Manuals/en/Html/Repository/repository.html index 16f3098..ef567da 100644 --- a/Manuals/en/Html/Repository/repository.html +++ b/Manuals/en/Html/Repository/repository.html @@ -60,7 +60,7 @@ ul.toc {list-style: none} - +
[Top] [Contents][Index][Index] [ ? ]

CentOS Artwork Repository

@@ -86,9 +86,9 @@ Documentation License. 3. trunk   -Index   +Index   -List of Figures   +List of Figures   @@ -99,7 +99,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 6533333..6b486cc 100644 --- a/Manuals/en/Html/Repository/repository_1.html +++ b/Manuals/en/Html/Repository/repository_1.html @@ -68,7 +68,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 bda24dd..5de304c 100644 --- a/Manuals/en/Html/Repository/repository_10.html +++ b/Manuals/en/Html/Repository/repository_10.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -110,7 +110,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 c120816..409d57f 100644 --- a/Manuals/en/Html/Repository/repository_11.html +++ b/Manuals/en/Html/Repository/repository_11.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -111,7 +111,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 1c471bf..64f12e2 100644 --- a/Manuals/en/Html/Repository/repository_12.html +++ b/Manuals/en/Html/Repository/repository_12.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -115,7 +115,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 241e65a..23f9d4b 100644 --- a/Manuals/en/Html/Repository/repository_13.html +++ b/Manuals/en/Html/Repository/repository_13.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -111,7 +111,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 f2a978a..39b09d6 100644 --- a/Manuals/en/Html/Repository/repository_14.html +++ b/Manuals/en/Html/Repository/repository_14.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -443,7 +443,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 e077698..1b93c8f 100644 --- a/Manuals/en/Html/Repository/repository_15.html +++ b/Manuals/en/Html/Repository/repository_15.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -111,7 +111,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 ddc5717..e768177 100644 --- a/Manuals/en/Html/Repository/repository_16.html +++ b/Manuals/en/Html/Repository/repository_16.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -103,7 +103,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 42dc308..1fbd7e5 100644 --- a/Manuals/en/Html/Repository/repository_17.html +++ b/Manuals/en/Html/Repository/repository_17.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -108,7 +108,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.58 trunk/Translations/Identity/Themes   @@ -119,7 +119,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 93c7d61..b99c886 100644 --- a/Manuals/en/Html/Repository/repository_18.html +++ b/Manuals/en/Html/Repository/repository_18.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -117,7 +117,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 8ca75cd..c386627 100644 --- a/Manuals/en/Html/Repository/repository_19.html +++ b/Manuals/en/Html/Repository/repository_19.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -115,7 +115,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 5937fdc..a03888c 100644 --- a/Manuals/en/Html/Repository/repository_2.html +++ b/Manuals/en/Html/Repository/repository_2.html @@ -68,7 +68,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 c04e81d..1ae0ac2 100644 --- a/Manuals/en/Html/Repository/repository_20.html +++ b/Manuals/en/Html/Repository/repository_20.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -116,7 +116,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 cfc2540..08c3ac7 100644 --- a/Manuals/en/Html/Repository/repository_21.html +++ b/Manuals/en/Html/Repository/repository_21.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -175,7 +175,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 84c6495..8410337 100644 --- a/Manuals/en/Html/Repository/repository_22.html +++ b/Manuals/en/Html/Repository/repository_22.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -103,7 +103,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 51982a4..41a57fd 100644 --- a/Manuals/en/Html/Repository/repository_23.html +++ b/Manuals/en/Html/Repository/repository_23.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -116,7 +116,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 ebce722..0e60a9b 100644 --- a/Manuals/en/Html/Repository/repository_24.html +++ b/Manuals/en/Html/Repository/repository_24.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -115,7 +115,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 3747841..3578c35 100644 --- a/Manuals/en/Html/Repository/repository_25.html +++ b/Manuals/en/Html/Repository/repository_25.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -199,7 +199,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 7d46f3c..79c030b 100644 --- a/Manuals/en/Html/Repository/repository_26.html +++ b/Manuals/en/Html/Repository/repository_26.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -207,7 +207,7 @@ can contain subdirectories to help you organize the design process. 3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf   -3.60 trunk/Translations/Identity/Themes/Backgrounds   +3.59 trunk/Translations/Identity/Themes/Backgrounds   @@ -219,7 +219,7 @@ can contain subdirectories to help you organize the design process.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_27.html b/Manuals/en/Html/Repository/repository_27.html index e3d0f45..131d567 100644 --- a/Manuals/en/Html/Repository/repository_27.html +++ b/Manuals/en/Html/Repository/repository_27.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -108,7 +108,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 1b7392f..2a15308 100644 --- a/Manuals/en/Html/Repository/repository_28.html +++ b/Manuals/en/Html/Repository/repository_28.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -107,7 +107,7 @@ command line interface.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_29.html b/Manuals/en/Html/Repository/repository_29.html index 829c18f..8ec7737 100644 --- a/Manuals/en/Html/Repository/repository_29.html +++ b/Manuals/en/Html/Repository/repository_29.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -116,7 +116,7 @@ based on them. In this last case you need the `Xcf/' directory.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_3.html b/Manuals/en/Html/Repository/repository_3.html index df7af0d..6508ae3 100644 --- a/Manuals/en/Html/Repository/repository_3.html +++ b/Manuals/en/Html/Repository/repository_3.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -155,51 +155,49 @@ ul.toc {list-style: none} 3.39 trunk/Scripts/Bash/Functions/Path   -3.40 trunk/Scripts/Bash/Functions/Prepare/prepare_forUsingPackages.sh   +3.40 trunk/Scripts/Bash/Functions/Render   -3.41 trunk/Scripts/Bash/Functions/Render   +3.41 trunk/Scripts/Bash/Functions/Render/Config   -3.42 trunk/Scripts/Bash/Functions/Render/Config   +3.42 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh   -3.43 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh   +3.43 trunk/Scripts/Bash/Functions/Render/render_getActions.sh   -3.44 trunk/Scripts/Bash/Functions/Render/render_getActions.sh   +3.44 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh   -3.45 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh   +3.45 trunk/Scripts/Bash/Functions/Shell   -3.46 trunk/Scripts/Bash/Functions/Shell   +3.46 trunk/Scripts/Bash/Functions/Svg   -3.47 trunk/Scripts/Bash/Functions/Svg   +3.47 trunk/Scripts/Bash/Functions/Verify   -3.48 trunk/Scripts/Bash/Functions/Verify   +3.48 trunk/Scripts/Bash/Locale   -3.49 trunk/Scripts/Bash/Locale   +3.49 trunk/Scripts/Perl   -3.50 trunk/Scripts/Perl   +3.50 trunk/Scripts/Python   -3.51 trunk/Scripts/Python   +3.51 trunk/Translations   -3.52 trunk/Translations   +3.52 trunk/Translations/Identity   -3.53 trunk/Translations/Identity   +3.53 trunk/Translations/Identity/Brands   -3.54 trunk/Translations/Identity/Brands   +3.54 trunk/Translations/Identity/Brands/Tpl   -3.55 trunk/Translations/Identity/Brands/Tpl   +3.55 trunk/Translations/Identity/Fonts   -3.56 trunk/Translations/Identity/Fonts   +3.56 trunk/Translations/Identity/Models   -3.57 trunk/Translations/Identity/Models   +3.57 trunk/Translations/Identity/Release   -3.58 trunk/Translations/Identity/Release   +3.58 trunk/Translations/Identity/Themes   -3.59 trunk/Translations/Identity/Themes   +3.59 trunk/Translations/Identity/Themes/Backgrounds   -3.60 trunk/Translations/Identity/Themes/Backgrounds   +3.60 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress   -3.61 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress   - -3.62 trunk/Translations/Identity/Widgets   +3.61 trunk/Translations/Identity/Widgets   @@ -210,7 +208,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 f0c92de..c15941b 100644 --- a/Manuals/en/Html/Repository/repository_30.html +++ b/Manuals/en/Html/Repository/repository_30.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -93,7 +93,7 @@ ul.toc {list-style: none}

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); +(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/
@@ -144,7 +144,7 @@ centos-art render --identity
 
  [ << ] [ Up ][ >> ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_31.html b/Manuals/en/Html/Repository/repository_31.html index dfa814f..9015808 100644 --- a/Manuals/en/Html/Repository/repository_31.html +++ b/Manuals/en/Html/Repository/repository_31.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -108,7 +108,7 @@ limitations. Theme palettes contain theme's unique color information.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_32.html b/Manuals/en/Html/Repository/repository_32.html index b3b9f7e..c6dfc16 100644 --- a/Manuals/en/Html/Repository/repository_32.html +++ b/Manuals/en/Html/Repository/repository_32.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -103,7 +103,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_33.html b/Manuals/en/Html/Repository/repository_33.html index 0e59bbc..31c914e 100644 --- a/Manuals/en/Html/Repository/repository_33.html +++ b/Manuals/en/Html/Repository/repository_33.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -414,7 +414,7 @@ the following `syslinux.hex' file:   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_34.html b/Manuals/en/Html/Repository/repository_34.html index d23454c..5761b14 100644 --- a/Manuals/en/Html/Repository/repository_34.html +++ b/Manuals/en/Html/Repository/repository_34.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -103,7 +103,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_35.html b/Manuals/en/Html/Repository/repository_35.html index f593cd3..c781e9b 100644 --- a/Manuals/en/Html/Repository/repository_35.html +++ b/Manuals/en/Html/Repository/repository_35.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -154,7 +154,7 @@ repository):   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_36.html b/Manuals/en/Html/Repository/repository_36.html index 7c39c55..9e1e366 100644 --- a/Manuals/en/Html/Repository/repository_36.html +++ b/Manuals/en/Html/Repository/repository_36.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -114,7 +114,7 @@ programming language.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_37.html b/Manuals/en/Html/Repository/repository_37.html index 39b65fd..0f5d120 100644 --- a/Manuals/en/Html/Repository/repository_37.html +++ b/Manuals/en/Html/Repository/repository_37.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -231,7 +231,7 @@ command its copyright and its license notes. - @@ -244,7 +244,7 @@ command its copyright and its license notes. - +

diff --git a/Manuals/en/Html/Repository/repository_38.html b/Manuals/en/Html/Repository/repository_38.html index 88f4795..0a1ae51 100644 --- a/Manuals/en/Html/Repository/repository_38.html +++ b/Manuals/en/Html/Repository/repository_38.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -105,13 +105,13 @@ ul.toc {list-style: none} 3.39 trunk/Scripts/Bash/Functions/Path   -3.41 trunk/Scripts/Bash/Functions/Render   +3.40 trunk/Scripts/Bash/Functions/Render   -3.46 trunk/Scripts/Bash/Functions/Shell   +3.45 trunk/Scripts/Bash/Functions/Shell   -3.47 trunk/Scripts/Bash/Functions/Svg   +3.46 trunk/Scripts/Bash/Functions/Svg   -3.48 trunk/Scripts/Bash/Functions/Verify   +3.47 trunk/Scripts/Bash/Functions/Verify   @@ -131,7 +131,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 476d620..578250a 100644 --- a/Manuals/en/Html/Repository/repository_39.html +++ b/Manuals/en/Html/Repository/repository_39.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -111,7 +111,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_4.html b/Manuals/en/Html/Repository/repository_4.html index e4eb487..e3ecfba 100644 --- a/Manuals/en/Html/Repository/repository_4.html +++ b/Manuals/en/Html/Repository/repository_4.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -506,7 +506,7 @@ script.

3.1.6 See also

- @@ -527,7 +527,7 @@ links).   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_40.html b/Manuals/en/Html/Repository/repository_40.html index 4ea6ff5..34fab4b 100644 --- a/Manuals/en/Html/Repository/repository_40.html +++ b/Manuals/en/Html/Repository/repository_40.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -111,7 +111,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_41.html b/Manuals/en/Html/Repository/repository_41.html index 0c14906..947e3ca 100644 --- a/Manuals/en/Html/Repository/repository_41.html +++ b/Manuals/en/Html/Repository/repository_41.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -111,7 +111,7 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_42.html b/Manuals/en/Html/Repository/repository_42.html index 106990c..5b06ada 100644 --- a/Manuals/en/Html/Repository/repository_42.html +++ b/Manuals/en/Html/Repository/repository_42.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -118,7 +118,7 @@ repository file system syncronized with documentation file system.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_43.html b/Manuals/en/Html/Repository/repository_43.html index bdc3e24..3252ef4 100644 --- a/Manuals/en/Html/Repository/repository_43.html +++ b/Manuals/en/Html/Repository/repository_43.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.40 trunk/Scripts/Bash/Functions/Prepare/prepare_forUsingPackages.sh +CentOS Artwork Repository: 3.40 trunk/Scripts/Bash/Functions/Render - - + + @@ -61,19 +61,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.40 trunk/Scripts/Bash/Functions/Prepare/prepare_forUsingPackages.sh

+

3.40 trunk/Scripts/Bash/Functions/Render

@@ -103,6 +103,10 @@ ul.toc {list-style: none}

3.40.4 See also

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

diff --git a/Manuals/en/Html/Repository/repository_44.html b/Manuals/en/Html/Repository/repository_44.html index 51a116f..8628c58 100644 --- a/Manuals/en/Html/Repository/repository_44.html +++ b/Manuals/en/Html/Repository/repository_44.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.41 trunk/Scripts/Bash/Functions/Render +CentOS Artwork Repository: 3.41 trunk/Scripts/Bash/Functions/Render/Config - - + + @@ -61,61 +61,224 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.41 trunk/Scripts/Bash/Functions/Render

+

3.41 trunk/Scripts/Bash/Functions/Render/Config

3.41.1 Goals

-
    -
  • ... -
- +

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

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

-

3.41.3 Usage

+

3.41.2.1 The `render.conf.sh' identity model

+ +

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

+

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

+
#!/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: +

+
#!/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. +

+

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

+ + +

3.41.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: +

+
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'
+
+ + +

3.41.3 Usage

+ +

Use the following commands to administer both identity and translation +pre-rendering configuration scripts: +

+
+
`centos-art config 'path/to/dir/' --create'
+
+

Use this command to create `path/to/dir' related pre-rendering +configuration script. +

+
+
`centos-art config 'path/to/dir/' --edit'
+
+

Use this command to edit `path/to/dir' related pre-rendering +configuration script. +

+
+
`centos-art config 'path/to/dir/' --read'
+
+

Use this command to read `path/to/dir' related pre-rendering +configuration script. +

+
+
`centos-art config 'path/to/dir/' --remove'
+
+

Use this command to remove `path/to/dir' related pre-rendering +configuration script. +

+
+
+ +

In the commands above, `path/to/dir' refers to one renderable +directory path under `trunk/Identity' or +`trunk/Translations' structures only. +

+ +

3.41.4 See also

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

diff --git a/Manuals/en/Html/Repository/repository_45.html b/Manuals/en/Html/Repository/repository_45.html index c311801..2cfe5cb 100644 --- a/Manuals/en/Html/Repository/repository_45.html +++ b/Manuals/en/Html/Repository/repository_45.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.42 trunk/Scripts/Bash/Functions/Render/Config +CentOS Artwork Repository: 3.42 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh - - + + @@ -56,220 +56,53 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.42 trunk/Scripts/Bash/Functions/Render/Config

- - - -

3.42.1 Goals

- -

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

- - -

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

- + -

3.42.2.1 The `render.conf.sh' identity model

- -

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

-

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

-
#!/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: -

-
#!/bin/bash
-
-function render_loadConfig {
-
-    # Define rendering actions.
-    ACTIONS[0]='BASE:renderText'
-    ACTIONS[1]='POST:formatText: --width=70 --uniform-spacing'
+

3.42 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh

-} -
-

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

-

3.42.2.2 The `render.conf.sh' translation model

+

3.42.1 Goals

+ +
    +
  • ... +
-

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.42.2.3 The `render.conf.sh' rendering actions

+

3.42.2 Description

-

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: -

-
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'
-

3.42.3 Usage

-

Use the following commands to administer both identity and translation -pre-rendering configuration scripts: -

-
-
`centos-art config 'path/to/dir/' --create'
-
-

Use this command to create `path/to/dir' related pre-rendering -configuration script. -

-
-
`centos-art config 'path/to/dir/' --edit'
-
-

Use this command to edit `path/to/dir' related pre-rendering -configuration script. -

-
-
`centos-art config 'path/to/dir/' --read'
-
-

Use this command to read `path/to/dir' related pre-rendering -configuration script. -

-
-
`centos-art config 'path/to/dir/' --remove'
-
-

Use this command to remove `path/to/dir' related pre-rendering -configuration script. -

-
-
+
    +
  • ... +
-

In the commands above, `path/to/dir' refers to one renderable -directory path under `trunk/Identity' or -`trunk/Translations' structures only. -

3.42.4 See also

- - - @@ -277,8 +110,8 @@ directory path under `trunk/Identity' or - - + +
[ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_46.html b/Manuals/en/Html/Repository/repository_46.html index e44c280..5df30fc 100644 --- a/Manuals/en/Html/Repository/repository_46.html +++ b/Manuals/en/Html/Repository/repository_46.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.43 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh +CentOS Artwork Repository: 3.43 trunk/Scripts/Bash/Functions/Render/render_getActions.sh - - + + @@ -61,19 +61,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.43 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh

+

3.43 trunk/Scripts/Bash/Functions/Render/render_getActions.sh

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

diff --git a/Manuals/en/Html/Repository/repository_47.html b/Manuals/en/Html/Repository/repository_47.html index 3b51ff5..1be86b6 100644 --- a/Manuals/en/Html/Repository/repository_47.html +++ b/Manuals/en/Html/Repository/repository_47.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.44 trunk/Scripts/Bash/Functions/Render/render_getActions.sh +CentOS Artwork Repository: 3.44 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh - - + + @@ -61,19 +61,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.44 trunk/Scripts/Bash/Functions/Render/render_getActions.sh

+

3.44 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh

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

diff --git a/Manuals/en/Html/Repository/repository_48.html b/Manuals/en/Html/Repository/repository_48.html index 36cc303..e31a2d3 100644 --- a/Manuals/en/Html/Repository/repository_48.html +++ b/Manuals/en/Html/Repository/repository_48.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.45 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh +CentOS Artwork Repository: 3.45 trunk/Scripts/Bash/Functions/Shell - - + + @@ -61,19 +61,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.45 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh

+

3.45 trunk/Scripts/Bash/Functions/Shell

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

diff --git a/Manuals/en/Html/Repository/repository_49.html b/Manuals/en/Html/Repository/repository_49.html index 456e62b..e450b1e 100644 --- a/Manuals/en/Html/Repository/repository_49.html +++ b/Manuals/en/Html/Repository/repository_49.html @@ -24,10 +24,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/Svg - - + + @@ -61,43 +61,66 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.46 trunk/Scripts/Bash/Functions/Shell

+

3.46 trunk/Scripts/Bash/Functions/Svg

3.46.1 Goals

-
    -
  • ... -
- +

This section exists to organize the "svg" functionality of +centos-art.sh script. +

3.46.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 a set of (let's say 30) SVG +files, and you want to set common metadata to all of them. Doing so +file by file is a tedious task, so the centos-art.sh script provides +the "svg" functionality to aid you maintain such actions. +

+

Most "svg" actions take one opening tag (e.g., `<metadata'), +and one closing tag (e.g., `</metadata') and replace everything +in-between with the information you define. The information you need +to define is inside template files as sed's replacement commands. +Template files are stored under +`trunk/Scripts/Bash/Functions/Svg/Tpl/' directory and can contain +translation markers. +

+

Translation markers have the form `=SOMETEXT='. Translation +markers are used by "svg" functionalities to introduce dynamic +information (e.g., dates, keywords based on path, etc.) +

3.46.3 Usage

-
    -
  • ... -
+
+
centos-art svg --update-metadata='path/to/dir'
+

Use this command to update metadata information to all `.svg' +files under `path/to/dir' as defined in the metadata template +file. +

+
+
centos-art svg --update-metadata='path/to/dir' --filter='filename'
+

Use this command to update metadata information to +`path/to/dir/filename', as defined in the metadata template file. +

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

diff --git a/Manuals/en/Html/Repository/repository_5.html b/Manuals/en/Html/Repository/repository_5.html index 39b831f..67c27b9 100644 --- a/Manuals/en/Html/Repository/repository_5.html +++ b/Manuals/en/Html/Repository/repository_5.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -103,7 +103,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 4cd968e..c0c695c 100644 --- a/Manuals/en/Html/Repository/repository_50.html +++ b/Manuals/en/Html/Repository/repository_50.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.47 trunk/Scripts/Bash/Functions/Svg +CentOS Artwork Repository: 3.47 trunk/Scripts/Bash/Functions/Verify - - + + @@ -61,67 +61,109 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.47 trunk/Scripts/Bash/Functions/Svg

+

3.47 trunk/Scripts/Bash/Functions/Verify

3.47.1 Goals

-

This section exists to organize the "svg" functionality of -centos-art.sh script. +

This section exists to organize files related to "verify" +functionality of centos-art.sh script. The "verify" functionality +of centos-art.sh script helps you to prepare the workstation you are +planning to use 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 a set of (let's say 30) SVG -files, and you want to set common metadata to all of them. Doing so -file by file is a tedious task, so the centos-art.sh script provides -the "svg" functionality to aid you maintain such actions. +

The first time you download CentOS Artwork Repository you need to +configure your workstation in order to use automation scripts. These +preliminar configurations are based mainly on auxiliar RPM packages +installation, and some symbolic links creations.

-

Most "svg" actions take one opening tag (e.g., `<metadata'), -and one closing tag (e.g., `</metadata') and replace everything -in-between with the information you define. The information you need -to define is inside template files as sed's replacement commands. -Template files are stored under -`trunk/Scripts/Bash/Functions/Svg/Tpl/' directory and can contain -translation markers. +

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 manipulate SVG files. +The inkscape package is not inside CentOS distribution so it needs to +be installed from third party repositories.

-

Translation markers have the form `=SOMETEXT='. Translation -markers are used by "svg" functionalities to introduce dynamic -information (e.g., dates, keywords based on path, etc.) +

Creation of symbolic links help to reuse components inside your +repository working copy. For example, palettes of colors maintained +inside CentOS artwork repository are not duplicated inside programs' +configuration directories on your workstation. Instead, palettes of +colors maintain inside CentOS artwork repository are linked from +program configuration directories. In this configuration, when someone +commits palette of colors changes up to central repository you can +immediatly start using these changes the next time you update palette +of colors in your repository working copy. +

+

Creation of symbolic links help to make automation scripts available +to repository structures different to `trunk/'. This is useful if +you need to render artworks under `branches/' repository +structure using the same automation scripts you use inside +`trunk/'. As this configuration consecuence, automation scripts +cannot be branched under `branches/Scripts' repository structure. +

+

Creation of symbolic links help to create the centos-art +command line to whatever script invokation you are using (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 command line +definition takes place inside your personal binary (`~/bin/') +directory. +

+

Definition of environment variables help to set default values you use +along your user session. Environment variables definition takes place +inside your personal `~/.bash_profile' file. You can use this +file to define which is your default text editor (EDITOR), time +zone (TZ) and any value you consider useful for your day-by-day +working. +

+

Another convenction to consider is the system date/time representation +we use. It would be very convenient if your workstation is configured +to use Coordinated Universal Time (UTC), just as CentOS Artwork +Repository server is configured. This way, both your repository +working copy and the central repository will coordinate time +information correctly. Otherwise it would be difficult to find out +when changes were committed exactly.

3.47.3 Usage

-
centos-art svg --update-metadata='path/to/dir'
-

Use this command to update metadata information to all `.svg' -files under `path/to/dir' as defined in the metadata template -file. +

`centos-art verify --packages'
+

This command verifies installed packages your workstation needs in +order to run the centos-art command correctly.

-
centos-art svg --update-metadata='path/to/dir' --filter='filename'
-

Use this command to update metadata information to -`path/to/dir/filename', as defined in the metadata template file. +

`centos-art verify --paths'
+

This command verifies required repository files your workstation needs +in order to run the centos-art command correctly.

+

If this is the first time you run centos-art command, the +appropriate way to execute "verify" action is not using the +centos-art command, but the absolute path to +centos-art.sh script instead (i.e., +`~/artwork/trunk/Scripts/Bash/centos-art.sh'). +

3.47.4 See also

@@ -134,7 +176,7 @@ file.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_51.html b/Manuals/en/Html/Repository/repository_51.html index cd1dba6..ae3ac36 100644 --- a/Manuals/en/Html/Repository/repository_51.html +++ b/Manuals/en/Html/Repository/repository_51.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.48 trunk/Scripts/Bash/Functions/Verify +CentOS Artwork Repository: 3.48 trunk/Scripts/Bash/Locale - - + + @@ -61,122 +61,132 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.48 trunk/Scripts/Bash/Functions/Verify

+

3.48 trunk/Scripts/Bash/Locale

3.48.1 Goals

-

This section exists to organize files related to "verify" -functionality of centos-art.sh script. The "verify" functionality -of centos-art.sh script helps you to prepare the workstation you are -planning to use centos-art.sh script. -

+
    +
  • Organize `centos-art.sh' locale files. +
+

3.48.2 Description

-

The first time you download CentOS Artwork Repository you need to -configure your workstation in order to use automation scripts. These -preliminar configurations are based mainly on auxiliar RPM packages -installation, and some symbolic links creations. +

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.

-

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 manipulate SVG files. -The inkscape package is not inside CentOS distribution so it needs to -be installed from third party repositories. +

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

-

Creation of symbolic links help to reuse components inside your -repository working copy. For example, palettes of colors maintained -inside CentOS artwork repository are not duplicated inside programs' -configuration directories on your workstation. Instead, palettes of -colors maintain inside CentOS artwork repository are linked from -program configuration directories. In this configuration, when someone -commits palette of colors changes up to central repository you can -immediatly start using these changes the next time you update palette -of colors in your repository working copy. +

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.

-

Creation of symbolic links help to make automation scripts available -to repository structures different to `trunk/'. This is useful if -you need to render artworks under `branches/' repository -structure using the same automation scripts you use inside -`trunk/'. As this configuration consecuence, automation scripts -cannot be branched under `branches/Scripts' repository structure. +

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.

-

Creation of symbolic links help to create the centos-art -command line to whatever script invokation you are using (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 command line -definition takes place inside your personal binary (`~/bin/') -directory. +

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

-

Definition of environment variables help to set default values you use -along your user session. Environment variables definition takes place -inside your personal `~/.bash_profile' file. You can use this -file to define which is your default text editor (EDITOR), time -zone (TZ) and any value you consider useful for your day-by-day -working. +

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.

-

Another convenction to consider is the system date/time representation -we use. It would be very convenient if your workstation is configured -to use Coordinated Universal Time (UTC), just as CentOS Artwork -Repository server is configured. This way, both your repository -working copy and the central repository will coordinate time -information correctly. Otherwise it would be difficult to find out -when changes were committed exactly. +

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.

+

3.48.2.1 Configuration files

+ +

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.48.3 Usage

+ + +

3.48.3.1 The centos-art `locale-cli' action

+
-
`centos-art verify --packages'
-

This command verifies installed packages your workstation needs in -order to run the centos-art command correctly. -

-
-
`centos-art verify --paths'
-

This command verifies required repository files your workstation needs -in order to run the centos-art command correctly. +

`centos-art locale-cli --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-cli --list'
+

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

-

If this is the first time you run centos-art command, the -appropriate way to execute "verify" action is not using the -centos-art command, but the absolute path to -centos-art.sh script instead (i.e., -`~/artwork/trunk/Scripts/Bash/centos-art.sh'). -

- +

3.48.4 See also

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

diff --git a/Manuals/en/Html/Repository/repository_52.html b/Manuals/en/Html/Repository/repository_52.html index 7ee1faf..7f5a4b8 100644 --- a/Manuals/en/Html/Repository/repository_52.html +++ b/Manuals/en/Html/Repository/repository_52.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.49 trunk/Scripts/Bash/Locale +CentOS Artwork Repository: 3.49 trunk/Scripts/Perl - - + + @@ -56,128 +56,45 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.49 trunk/Scripts/Bash/Locale

- - - -

3.49.1 Goals

- -
    -
  • Organize `centos-art.sh' locale files. -
- - + -

3.49.2 Description

+

3.49 trunk/Scripts/Perl

-

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

-

3.49.2.1 Configuration files

+

3.49.1 Goals

-

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.49.3 Usage

+

3.49.2 Description

-

3.49.3.1 The centos-art `locale-cli' action

- -
-
`centos-art locale-cli --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-cli --list'
-

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

-
+

3.49.3 Usage

3.49.4 See also

- - - - @@ -185,8 +102,8 @@ environment variable). - - + +
[ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_53.html b/Manuals/en/Html/Repository/repository_53.html index 71ebe72..44e5ea5 100644 --- a/Manuals/en/Html/Repository/repository_53.html +++ b/Manuals/en/Html/Repository/repository_53.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.50 trunk/Scripts/Perl +CentOS Artwork Repository: 3.50 trunk/Scripts/Python - - + + @@ -61,19 +61,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.50 trunk/Scripts/Perl

+

3.50 trunk/Scripts/Python

@@ -87,10 +87,18 @@ ul.toc {list-style: none}

3.50.2 Description

+
    +
  • ... +
+

3.50.3 Usage

+
    +
  • ... +
+

3.50.4 See also

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

diff --git a/Manuals/en/Html/Repository/repository_54.html b/Manuals/en/Html/Repository/repository_54.html index 480b2ab..016ecd9 100644 --- a/Manuals/en/Html/Repository/repository_54.html +++ b/Manuals/en/Html/Repository/repository_54.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.51 trunk/Scripts/Python +CentOS Artwork Repository: 3.51 trunk/Translations - - + + @@ -61,57 +61,669 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.51 trunk/Scripts/Python

+

3.51 trunk/Translations

3.51.1 Goals

+

The `trunk/Translations' directory exists to: +

    -
  • ... +
  • Organize translation files. +
  • Organize translation templates used to produce translation files.

3.51.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.51.3 Usage

+

3.51.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.51.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.6: 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.51.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.51.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.51.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.51.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.51.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.51.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: splash-small.sed 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.51.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.51.3 Usage

+ +
+
`centos-art render '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 '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.51.4 See also

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

diff --git a/Manuals/en/Html/Repository/repository_55.html b/Manuals/en/Html/Repository/repository_55.html index 440133f..d4d83af 100644 --- a/Manuals/en/Html/Repository/repository_55.html +++ b/Manuals/en/Html/Repository/repository_55.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.52 trunk/Translations +CentOS Artwork Repository: 3.52 trunk/Translations/Identity - - + + @@ -56,661 +56,65 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.52 trunk/Translations

+ + +

3.52 trunk/Translations/Identity

- +

3.52.1 Goals

-

The `trunk/Translations' directory exists to: -

    -
  • Organize translation files. -
  • Organize translation templates used to produce 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.6: 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: -

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

-

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

- -

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.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: splash-small.sed 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.52.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.52.3 Usage

-
-
`centos-art render '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 '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.52.4 See also

- + - - - - @@ -722,8 +126,8 @@ distribution you want to render translations for. - - + +

diff --git a/Manuals/en/Html/Repository/repository_56.html b/Manuals/en/Html/Repository/repository_56.html index eb386b5..0f3a209 100644 --- a/Manuals/en/Html/Repository/repository_56.html +++ b/Manuals/en/Html/Repository/repository_56.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.53 trunk/Translations/Identity +CentOS Artwork Repository: 3.53 trunk/Translations/Identity/Brands - - + + @@ -61,73 +61,143 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.53 trunk/Translations/Identity

+

3.53 trunk/Translations/Identity/Brands

3.53.1 Goals

    -
  • ... +
  • Organize brands' translation files.

3.53.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: +

+
/home/centos/artwork/trunk/Translation/Identity/Brands/render.conf.sh
+
+

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

+

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.53.3 Usage

- -
    -
  • ... -
+

3.53.2.1 Conventional file names

+

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.53.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.53.2.3 Translation markers

+ +

Inside `trunk/Translations/Identity/Brands/', 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. +

+
+
+ + + +

3.53.3 Usage

+ +

To render brands' translation files, use the following command: +

+
centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands
+
+ +

3.53.4 See also

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

diff --git a/Manuals/en/Html/Repository/repository_57.html b/Manuals/en/Html/Repository/repository_57.html index cc40add..545b530 100644 --- a/Manuals/en/Html/Repository/repository_57.html +++ b/Manuals/en/Html/Repository/repository_57.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.54 trunk/Translations/Identity/Brands +CentOS Artwork Repository: 3.54 trunk/Translations/Identity/Brands/Tpl - - + + @@ -56,139 +56,41 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.54 trunk/Translations/Identity/Brands

- - - -

3.54.1 Goals

- -
    -
  • Organize brands' 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: -

-
/home/centos/artwork/trunk/Translation/Identity/Brands/render.conf.sh
-
-

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

-

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

+

3.54 trunk/Translations/Identity/Brands/Tpl

-

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.1 Goals

- -

3.54.2.3 Translation markers

-

Inside `trunk/Translations/Identity/Brands/', 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. -

-
-
+ +

3.54.2 Description

3.54.3 Usage

-

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

- - - - @@ -196,8 +98,8 @@ inside template translation files. - - + +
[ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_58.html b/Manuals/en/Html/Repository/repository_58.html index c7998f0..58962cf 100644 --- a/Manuals/en/Html/Repository/repository_58.html +++ b/Manuals/en/Html/Repository/repository_58.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.55 trunk/Translations/Identity/Brands/Tpl +CentOS Artwork Repository: 3.55 trunk/Translations/Identity/Fonts - - + + @@ -61,45 +61,106 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.55 trunk/Translations/Identity/Brands/Tpl

+

3.55 trunk/Translations/Identity/Fonts

3.55.1 Goals

+
    +
  • Organize fonts' translation files. +
+

3.55.2 Description

+

Translation files, inside `trunk/Translations/Fonts', have the +following structure: +

+
# ----------------------------------------------------------------------
+# $Id: Fonts.texi 29 2010-09-12 05:32:26Z al $
+# ----------------------------------------------------------------------
+
+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.55.3 Usage

+

3.55.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.55.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.55.4 See also

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

diff --git a/Manuals/en/Html/Repository/repository_59.html b/Manuals/en/Html/Repository/repository_59.html index 31cc303..6401ef5 100644 --- a/Manuals/en/Html/Repository/repository_59.html +++ b/Manuals/en/Html/Repository/repository_59.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.56 trunk/Translations/Identity/Fonts +CentOS Artwork Repository: 3.56 trunk/Translations/Identity/Models - - + + @@ -56,102 +56,41 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.56 trunk/Translations/Identity/Fonts

- - + -

3.56.1 Goals

- -
    -
  • Organize fonts' translation files. -
+

3.56 trunk/Translations/Identity/Models

-

3.56.2 Description

- -

Translation files, inside `trunk/Translations/Fonts', have the -following structure: -

-
# ----------------------------------------------------------------------
-# $Id: Fonts.texi 29 2010-09-12 05:32:26Z al $
-# ----------------------------------------------------------------------
-
-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

- - - - @@ -159,8 +98,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 b1c540f..d20ee03 100644 --- a/Manuals/en/Html/Repository/repository_6.html +++ b/Manuals/en/Html/Repository/repository_6.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -169,7 +169,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 f0a5400..be96c86 100644 --- a/Manuals/en/Html/Repository/repository_60.html +++ b/Manuals/en/Html/Repository/repository_60.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.57 trunk/Translations/Identity/Models +CentOS Artwork Repository: 3.57 trunk/Translations/Identity/Release - - + + @@ -61,19 +61,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.57 trunk/Translations/Identity/Models

+

3.57 trunk/Translations/Identity/Release

@@ -99,7 +99,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 6579883..4fe640f 100644 --- a/Manuals/en/Html/Repository/repository_61.html +++ b/Manuals/en/Html/Repository/repository_61.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.58 trunk/Translations/Identity/Release +CentOS Artwork Repository: 3.58 trunk/Translations/Identity/Themes - - + + @@ -61,19 +61,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.58 trunk/Translations/Identity/Release

+

3.58 trunk/Translations/Identity/Themes

@@ -99,7 +99,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 d2ca241..c995f71 100644 --- a/Manuals/en/Html/Repository/repository_62.html +++ b/Manuals/en/Html/Repository/repository_62.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.59 trunk/Translations/Identity/Themes +CentOS Artwork Repository: 3.59 trunk/Translations/Identity/Themes/Backgrounds - - + + @@ -61,32 +61,44 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.59 trunk/Translations/Identity/Themes

+

3.59 trunk/Translations/Identity/Themes/Backgrounds

3.59.1 Goals

+
    +
  • ... +
+

3.59.2 Description

+
    +
  • ... +
+

3.59.3 Usage

+
    +
  • ... +
+

3.59.4 See also

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

diff --git a/Manuals/en/Html/Repository/repository_63.html b/Manuals/en/Html/Repository/repository_63.html index 708a088..19bb034 100644 --- a/Manuals/en/Html/Repository/repository_63.html +++ b/Manuals/en/Html/Repository/repository_63.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.60 trunk/Translations/Identity/Themes/Backgrounds +CentOS Artwork Repository: 3.60 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress - - + + @@ -61,57 +61,125 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.60 trunk/Translations/Identity/Themes/Backgrounds

+

3.60 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress

3.60.1 Goals

    -
  • ... +
  • Organize Anaconda progress translation templates. +
  • Organize Anaconda progress translation files in several +languages and major releases of CentOS distribution.

3.60.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.60.3 Usage

-
    -
  • ... -
+

Translation rendering is described in `trunk/Translations' +documentation entry (see section trunk/Translations). +

3.60.4 See also

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

diff --git a/Manuals/en/Html/Repository/repository_64.html b/Manuals/en/Html/Repository/repository_64.html index 1db24ed..58ee684 100644 --- a/Manuals/en/Html/Repository/repository_64.html +++ b/Manuals/en/Html/Repository/repository_64.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.61 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress +CentOS Artwork Repository: 3.61 trunk/Translations/Identity/Widgets - - + + @@ -61,117 +61,56 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.61 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress

+

3.61 trunk/Translations/Identity/Widgets

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

+ + + + + + + @@ -179,7 +118,7 @@ documentation entry (see section trunk/Trans - +
[ < ]   [ << ] [ Up ][ >> ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_65.html b/Manuals/en/Html/Repository/repository_65.html index d99d01e..4cbaf5f 100644 --- a/Manuals/en/Html/Repository/repository_65.html +++ b/Manuals/en/Html/Repository/repository_65.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: 3.62 trunk/Translations/Identity/Widgets +CentOS Artwork Repository: Index - - + + @@ -57,68 +57,148 @@ 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

- - - +

Index

+
Jump to:   B +   +C +   +H +   +S +   +T +   +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Index Entry Section

B
branches1. branches

C
Common translation files3.51.2.5 Common Translation Files

H
How to render brands' translation files3.53.3 Usage
How to render fonts' translation files3.55.3 Usage
How to render translation files3.51.3 Usage

S
Specific translation files3.51.2.6 Specific Translation Files

T
tags2. tags
Template translation files3.51.2.4 Template Translation Files
Translation brands file names3.53.2.1 Conventional file names
Translation brands file names3.53.2.2 Numeric file names
Translation configuration scripts3.51.2.8 Translation (Pre-)Rendering Configuration Scripts
Translation entries3.51.2.1 Translation Entries
Translation files3.51.2.3 Translation Files
Translation markers3.51.2.2 Translation Markers
Translation paths3.51.2.1 Translation Entries
Translation pre-rendering configuration scripts3.51.2.8 Translation (Pre-)Rendering Configuration Scripts
Translation rendering3.51.2.7 Translation Rendering
Translation rendering default functionality3.51.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 Modern Backgrounds3.23 trunk/Identity/Themes/Motifs/Modern/Backgrounds
trunk Identity Themes Motifs Modern Backgrounds Img3.24 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img
trunk Identity Themes Motifs Modern Backgrounds Tpl3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl
trunk Identity Themes Motifs Modern Backgrounds Xcf3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf
trunk Identity Themes Motifs Modern Distro Anaconda Progress3.27 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
trunk Identity Themes Motifs Modern Palettes3.28 trunk/Identity/Themes/Motifs/Modern/Palettes
trunk Identity Themes Motifs TreeFlower3.29 trunk/Identity/Themes/Motifs/TreeFlower
trunk Identity Themes Motifs TreeFlower Backgrounds3.30 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds
trunk Identity Widgets3.31 trunk/Identity/Widgets
trunk Manuals3.32 trunk/Manuals
trunk Scripts3.33 trunk/Scripts
trunk Scripts Bash3.34 trunk/Scripts/Bash
trunk Scripts Bash Functions3.35 trunk/Scripts/Bash/Functions
trunk Scripts Bash Functions Help3.36 trunk/Scripts/Bash/Functions/Help
trunk Scripts Bash Functions Html3.37 trunk/Scripts/Bash/Functions/Html
trunk Scripts Bash Functions Locale3.38 trunk/Scripts/Bash/Functions/Locale
trunk Scripts Bash Functions Path3.39 trunk/Scripts/Bash/Functions/Path
trunk Scripts Bash Functions Render3.40 trunk/Scripts/Bash/Functions/Render
trunk Scripts Bash Functions Render Config3.41 trunk/Scripts/Bash/Functions/Render/Config
trunk Scripts Bash Functions Render render_getActions.sh3.43 trunk/Scripts/Bash/Functions/Render/render_getActions.sh
trunk Scripts Bash Functions Render render_getActionsIdentity.sh3.42 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh
trunk Scripts Bash Functions Render render_getActionsTranslations.sh3.44 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh
trunk Scripts Bash Functions Shell3.45 trunk/Scripts/Bash/Functions/Shell
trunk Scripts Bash Functions Svg3.46 trunk/Scripts/Bash/Functions/Svg
trunk Scripts Bash Functions Verify3.47 trunk/Scripts/Bash/Functions/Verify
trunk Scripts Bash Locale3.48 trunk/Scripts/Bash/Locale
trunk Scripts Perl3.49 trunk/Scripts/Perl
trunk Scripts Python3.50 trunk/Scripts/Python
trunk Translations3.51 trunk/Translations
trunk Translations Identity3.52 trunk/Translations/Identity
trunk Translations Identity Brands3.53 trunk/Translations/Identity/Brands
trunk Translations Identity Brands Tpl3.54 trunk/Translations/Identity/Brands/Tpl
trunk Translations Identity Fonts3.55 trunk/Translations/Identity/Fonts
trunk Translations Identity Models3.56 trunk/Translations/Identity/Models
trunk Translations Identity Release3.57 trunk/Translations/Identity/Release
trunk Translations Identity Themes3.58 trunk/Translations/Identity/Themes
trunk Translations Identity Themes Backgrounds3.59 trunk/Translations/Identity/Themes/Backgrounds
trunk Translations Identity Themes Distro Anaconda Progress3.60 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
trunk Translations Identity Widgets3.61 trunk/Translations/Identity/Widgets

- - - +
Jump to:   B +   +C +   +H +   +S +   +T +   +
- - + + - - + +
[ < ][ > ]
[ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

diff --git a/Manuals/en/Html/Repository/repository_66.html b/Manuals/en/Html/Repository/repository_66.html index dbeb352..ee9b731 100644 --- a/Manuals/en/Html/Repository/repository_66.html +++ b/Manuals/en/Html/Repository/repository_66.html @@ -24,10 +24,10 @@ Send bugs and suggestions to --> -CentOS Artwork Repository: Index +CentOS Artwork Repository: List of Figures - - + + @@ -56,150 +56,47 @@ ul.toc {list-style: none} - - + + - + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ][ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

Index

-
Jump to:   B -   -C -   -H -   -S -   -T -   -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
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

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 Modern Backgrounds3.23 trunk/Identity/Themes/Motifs/Modern/Backgrounds
trunk Identity Themes Motifs Modern Backgrounds Img3.24 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img
trunk Identity Themes Motifs Modern Backgrounds Tpl3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl
trunk Identity Themes Motifs Modern Backgrounds Xcf3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf
trunk Identity Themes Motifs Modern Distro Anaconda Progress3.27 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
trunk Identity Themes Motifs Modern Palettes3.28 trunk/Identity/Themes/Motifs/Modern/Palettes
trunk Identity Themes Motifs TreeFlower3.29 trunk/Identity/Themes/Motifs/TreeFlower
trunk Identity Themes Motifs TreeFlower Backgrounds3.30 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds
trunk Identity Widgets3.31 trunk/Identity/Widgets
trunk Manuals3.32 trunk/Manuals
trunk Scripts3.33 trunk/Scripts
trunk Scripts Bash3.34 trunk/Scripts/Bash
trunk Scripts Bash Functions3.35 trunk/Scripts/Bash/Functions
trunk Scripts Bash Functions Help3.36 trunk/Scripts/Bash/Functions/Help
trunk Scripts Bash Functions Html3.37 trunk/Scripts/Bash/Functions/Html
trunk Scripts Bash Functions Locale3.38 trunk/Scripts/Bash/Functions/Locale
trunk Scripts Bash Functions Path3.39 trunk/Scripts/Bash/Functions/Path
trunk Scripts Bash Functions Prepare prepare_forUsingPackages.sh3.40 trunk/Scripts/Bash/Functions/Prepare/prepare_forUsingPackages.sh
trunk Scripts Bash Functions Render3.41 trunk/Scripts/Bash/Functions/Render
trunk Scripts Bash Functions Render Config3.42 trunk/Scripts/Bash/Functions/Render/Config
trunk Scripts Bash Functions Render render_getActions.sh3.44 trunk/Scripts/Bash/Functions/Render/render_getActions.sh
trunk Scripts Bash Functions Render render_getActionsIdentity.sh3.43 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh
trunk Scripts Bash Functions Render render_getActionsTranslations.sh3.45 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh
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

-
Jump to:   B -   -C -   -H -   -S -   -T -   -
+ + +

List of Figures

+
+
Figure 3.1

The CentOS web customization design model. +

+
Figure 3.2

The CentOS web customization using promotion design model. +

+
Figure 3.3

Web environment html definitions +

+
Figure 3.4

The CentOS web navigation design model. +

+
Figure 3.5

The centos-art.sh initialization environment. +

+
Figure 3.6

The image rendering flow. +

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

diff --git a/Manuals/en/Html/Repository/repository_7.html b/Manuals/en/Html/Repository/repository_7.html index 00cd66b..ef9c0d0 100644 --- a/Manuals/en/Html/Repository/repository_7.html +++ b/Manuals/en/Html/Repository/repository_7.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -103,7 +103,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 17a6f30..bd0c27f 100644 --- a/Manuals/en/Html/Repository/repository_8.html +++ b/Manuals/en/Html/Repository/repository_8.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -103,7 +103,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 0221910..eea2eae 100644 --- a/Manuals/en/Html/Repository/repository_9.html +++ b/Manuals/en/Html/Repository/repository_9.html @@ -61,14 +61,14 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] @@ -114,7 +114,7 @@ to build artworks.   [ << ] [ Up ] -[ >> ] +[ >> ]

diff --git a/Manuals/en/Html/Repository/repository_abt.html b/Manuals/en/Html/Repository/repository_abt.html index 67c5452..5f7f5d7 100644 --- a/Manuals/en/Html/Repository/repository_abt.html +++ b/Manuals/en/Html/Repository/repository_abt.html @@ -59,7 +59,7 @@ ul.toc {list-style: none} - +
[Top] [Contents][Index][Index] [ ? ]

About This Document

@@ -167,7 +167,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 4a1b94a..fc12f12 100644 --- a/Manuals/en/Html/Repository/repository_fot.html +++ b/Manuals/en/Html/Repository/repository_fot.html @@ -59,27 +59,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 df3d81a..490359e 100644 --- a/Manuals/en/Html/Repository/repository_toc.html +++ b/Manuals/en/Html/Repository/repository_toc.html @@ -59,7 +59,7 @@ ul.toc {list-style: none} - +
[Top] [Contents][Index][Index] [ ? ]

Table of Contents

@@ -388,208 +388,201 @@ ul.toc {list-style: none}
  • 3.39.3 Usage
  • 3.39.4 See also
  • -
  • 3.40 trunk/Scripts/Bash/Functions/Prepare/prepare_forUsingPackages.sh +
  • 3.40 trunk/Scripts/Bash/Functions/Render
  • -
  • 3.41 trunk/Scripts/Bash/Functions/Render +
  • 3.41 trunk/Scripts/Bash/Functions/Render/Config
  • -
  • 3.42 trunk/Scripts/Bash/Functions/Render/Config -
  • +
  • 3.42 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh +
  • -
  • 3.43 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh +
  • 3.43 trunk/Scripts/Bash/Functions/Render/render_getActions.sh
  • -
  • 3.44 trunk/Scripts/Bash/Functions/Render/render_getActions.sh +
  • 3.44 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh
  • -
  • 3.45 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh +
  • 3.45 trunk/Scripts/Bash/Functions/Shell
  • -
  • 3.46 trunk/Scripts/Bash/Functions/Shell +
  • 3.46 trunk/Scripts/Bash/Functions/Svg
  • -
  • 3.47 trunk/Scripts/Bash/Functions/Svg +
  • 3.47 trunk/Scripts/Bash/Functions/Verify
  • -
  • 3.48 trunk/Scripts/Bash/Functions/Verify +
  • 3.48 trunk/Scripts/Bash/Locale
  • -
  • 3.49 trunk/Scripts/Bash/Locale -
  • +
  • 3.49 trunk/Scripts/Perl +
  • -
  • 3.50 trunk/Scripts/Perl +
  • 3.50 trunk/Scripts/Python
  • -
  • 3.51 trunk/Scripts/Python +
  • 3.51 trunk/Translations
  • -
  • 3.52 trunk/Translations -
  • +
  • 3.52 trunk/Translations/Identity +
  • -
  • 3.53 trunk/Translations/Identity +
  • 3.53 trunk/Translations/Identity/Brands
  • -
  • 3.54 trunk/Translations/Identity/Brands -
  • +
  • 3.54 trunk/Translations/Identity/Brands/Tpl +
  • -
  • 3.55 trunk/Translations/Identity/Brands/Tpl +
  • 3.55 trunk/Translations/Identity/Fonts
  • -
  • 3.56 trunk/Translations/Identity/Fonts -
  • +
  • 3.56 trunk/Translations/Identity/Models +
  • -
  • 3.57 trunk/Translations/Identity/Models +
  • 3.57 trunk/Translations/Identity/Release
  • -
  • 3.58 trunk/Translations/Identity/Release +
  • 3.58 trunk/Translations/Identity/Themes
  • -
  • 3.59 trunk/Translations/Identity/Themes +
  • 3.59 trunk/Translations/Identity/Themes/Backgrounds
  • -
  • 3.60 trunk/Translations/Identity/Themes/Backgrounds +
  • 3.60 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
  • -
  • 3.61 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress +
  • 3.61 trunk/Translations/Identity/Widgets
  • -
  • 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 c0a5250..ae10207 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 ee6277a..8bdf4f1 100644 --- a/Manuals/en/Plaintext/Repository/repository.txt +++ b/Manuals/en/Plaintext/Repository/repository.txt @@ -231,139 +231,134 @@ CentOS Artwork Repository 3.39.2 Description 3.39.3 Usage 3.39.4 See also - 3.40 trunk/Scripts/Bash/Functions/Prepare/prepare_forUsingPackages.sh + 3.40 trunk/Scripts/Bash/Functions/Render 3.40.1 Goals 3.40.2 Description 3.40.3 Usage 3.40.4 See also - 3.41 trunk/Scripts/Bash/Functions/Render + 3.41 trunk/Scripts/Bash/Functions/Render/Config 3.41.1 Goals 3.41.2 Description + 3.41.2.1 The `render.conf.sh' identity model + 3.41.2.2 The `render.conf.sh' translation model + 3.41.2.3 The `render.conf.sh' rendering actions 3.41.3 Usage 3.41.4 See also - 3.42 trunk/Scripts/Bash/Functions/Render/Config + 3.42 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh 3.42.1 Goals 3.42.2 Description - 3.42.2.1 The `render.conf.sh' identity model - 3.42.2.2 The `render.conf.sh' translation model - 3.42.2.3 The `render.conf.sh' rendering actions 3.42.3 Usage 3.42.4 See also - 3.43 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh + 3.43 trunk/Scripts/Bash/Functions/Render/render_getActions.sh 3.43.1 Goals 3.43.2 Description 3.43.3 Usage 3.43.4 See also - 3.44 trunk/Scripts/Bash/Functions/Render/render_getActions.sh + 3.44 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh 3.44.1 Goals 3.44.2 Description 3.44.3 Usage 3.44.4 See also - 3.45 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh + 3.45 trunk/Scripts/Bash/Functions/Shell 3.45.1 Goals 3.45.2 Description 3.45.3 Usage 3.45.4 See also - 3.46 trunk/Scripts/Bash/Functions/Shell + 3.46 trunk/Scripts/Bash/Functions/Svg 3.46.1 Goals 3.46.2 Description 3.46.3 Usage 3.46.4 See also - 3.47 trunk/Scripts/Bash/Functions/Svg + 3.47 trunk/Scripts/Bash/Functions/Verify 3.47.1 Goals 3.47.2 Description 3.47.3 Usage 3.47.4 See also - 3.48 trunk/Scripts/Bash/Functions/Verify + 3.48 trunk/Scripts/Bash/Locale 3.48.1 Goals 3.48.2 Description + 3.48.2.1 Configuration files 3.48.3 Usage + 3.48.3.1 The `centos-art' `locale-cli' action 3.48.4 See also - 3.49 trunk/Scripts/Bash/Locale + 3.49 trunk/Scripts/Perl 3.49.1 Goals 3.49.2 Description - 3.49.2.1 Configuration files 3.49.3 Usage - 3.49.3.1 The `centos-art' `locale-cli' action 3.49.4 See also - 3.50 trunk/Scripts/Perl + 3.50 trunk/Scripts/Python 3.50.1 Goals 3.50.2 Description 3.50.3 Usage 3.50.4 See also - 3.51 trunk/Scripts/Python + 3.51 trunk/Translations 3.51.1 Goals 3.51.2 Description + 3.51.2.1 Translation Entries + 3.51.2.2 Translation Markers + 3.51.2.3 Translation Files + 3.51.2.4 Template Translation Files + 3.51.2.5 Common Translation Files + 3.51.2.6 Specific Translation Files + 3.51.2.7 Translation Rendering + 3.51.2.8 Translation (Pre-)Rendering Configuration Scripts + 3.51.2.9 Translation Rendering Default Functionality 3.51.3 Usage 3.51.4 See also - 3.52 trunk/Translations + 3.52 trunk/Translations/Identity 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.3 Usage 3.52.4 See also - 3.53 trunk/Translations/Identity + 3.53 trunk/Translations/Identity/Brands 3.53.1 Goals 3.53.2 Description + 3.53.2.1 Conventional file names + 3.53.2.2 Numeric file names + 3.53.2.3 Translation markers 3.53.3 Usage 3.53.4 See also - 3.54 trunk/Translations/Identity/Brands + 3.54 trunk/Translations/Identity/Brands/Tpl 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.3 Usage 3.54.4 See also - 3.55 trunk/Translations/Identity/Brands/Tpl + 3.55 trunk/Translations/Identity/Fonts 3.55.1 Goals 3.55.2 Description + 3.55.2.1 Translation Markers 3.55.3 Usage 3.55.4 See also - 3.56 trunk/Translations/Identity/Fonts + 3.56 trunk/Translations/Identity/Models 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/Release 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 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/Backgrounds 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/Themes/Distro/Anaconda/Progress 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 trunk/Translations/Identity/Widgets 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 @@ -2697,8 +2692,8 @@ This feature is not supported yet. 3.39.4 See also --------------- -3.40 trunk/Scripts/Bash/Functions/Prepare/prepare_forUsingPackages.sh -===================================================================== +3.40 trunk/Scripts/Bash/Functions/Render +======================================== 3.40.1 Goals ------------ @@ -2718,37 +2713,16 @@ This feature is not supported yet. 3.40.4 See also --------------- -3.41 trunk/Scripts/Bash/Functions/Render -======================================== - -3.41.1 Goals ------------- - - * ... - -3.41.2 Description ------------------- - - * ... - -3.41.3 Usage ------------- - - * ... - -3.41.4 See also ---------------- - -3.42 trunk/Scripts/Bash/Functions/Render/Config +3.41 trunk/Scripts/Bash/Functions/Render/Config =============================================== -3.42.1 Goals +3.41.1 Goals ------------ The `trunk/Scripts/Bash/Config' directory exists to oraganize pre-rendering configuration scripts. -3.42.2 Description +3.41.2 Description ------------------ Pre-rendering configuration scripts let you customize the way @@ -2762,7 +2736,7 @@ both on identity and translation repository entires. Pre-rendering configuration entries are required for each identity entry, but not for translation entries. -3.42.2.1 The `render.conf.sh' identity model +3.41.2.1 The `render.conf.sh' identity model ............................................ Inside CentOS Artwork Repository, we consider identity entries to all @@ -2805,7 +2779,7 @@ extend both image-based and text-based pre-rendering configuration scripts using image-based and text-based post-rendering actions, respectively. -3.42.2.2 The `render.conf.sh' translation model +3.41.2.2 The `render.conf.sh' translation model ............................................... Translation pre-rendering configuration scripts take precedence before @@ -2813,7 +2787,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.42.2.3 The `render.conf.sh' rendering actions +3.41.2.3 The `render.conf.sh' rendering actions ............................................... Inside both image-based and text-based identity pre-rendering @@ -2887,7 +2861,7 @@ ACTIONS[0]='BASE:renderImage' ACTIONS[1]='POST:renderFormats: xpm jpg tif' ACTIONS[2]='LAST:groupByformat: png xpm jpg tif' -3.42.3 Usage +3.41.3 Usage ------------ Use the following commands to administer both identity and translation @@ -2914,103 +2888,103 @@ pre-rendering configuration scripts: directory path under `trunk/Identity' or `trunk/Translations' structures only. -3.42.4 See also +3.41.4 See also --------------- -3.43 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh +3.42 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh ===================================================================== -3.43.1 Goals +3.42.1 Goals ------------ * ... -3.43.2 Description +3.42.2 Description ------------------ * ... -3.43.3 Usage +3.42.3 Usage ------------ * ... -3.43.4 See also +3.42.4 See also --------------- -3.44 trunk/Scripts/Bash/Functions/Render/render_getActions.sh +3.43 trunk/Scripts/Bash/Functions/Render/render_getActions.sh ============================================================= -3.44.1 Goals +3.43.1 Goals ------------ * ... -3.44.2 Description +3.43.2 Description ------------------ * ... -3.44.3 Usage +3.43.3 Usage ------------ * ... -3.44.4 See also +3.43.4 See also --------------- -3.45 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh +3.44 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh ========================================================================= -3.45.1 Goals +3.44.1 Goals ------------ * ... -3.45.2 Description +3.44.2 Description ------------------ * ... -3.45.3 Usage +3.44.3 Usage ------------ * ... -3.45.4 See also +3.44.4 See also --------------- -3.46 trunk/Scripts/Bash/Functions/Shell +3.45 trunk/Scripts/Bash/Functions/Shell ======================================= -3.46.1 Goals +3.45.1 Goals ------------ * ... -3.46.2 Description +3.45.2 Description ------------------ * ... -3.46.3 Usage +3.45.3 Usage ------------ * ... -3.46.4 See also +3.45.4 See also --------------- -3.47 trunk/Scripts/Bash/Functions/Svg +3.46 trunk/Scripts/Bash/Functions/Svg ===================================== -3.47.1 Goals +3.46.1 Goals ------------ This section exists to organize the "svg" functionality of centos-art.sh script. -3.47.2 Description +3.46.2 Description ------------------ The "svg" functionality of centos-art.sh script helps you to maintain @@ -3031,7 +3005,7 @@ can contain translation markers. are used by "svg" functionalities to introduce dynamic information (e.g., dates, keywords based on path, etc.) -3.47.3 Usage +3.46.3 Usage ------------ `centos-art svg --update-metadata='path/to/dir'' @@ -3042,13 +3016,13 @@ are used by "svg" functionalities to introduce dynamic information Use this command to update metadata information to `path/to/dir/filename', as defined in the metadata template file. -3.47.4 See also +3.46.4 See also --------------- -3.48 trunk/Scripts/Bash/Functions/Verify +3.47 trunk/Scripts/Bash/Functions/Verify ======================================== -3.48.1 Goals +3.47.1 Goals ------------ This section exists to organize files related to "verify" functionality @@ -3056,7 +3030,7 @@ of centos-art.sh script. The "verify" functionality of centos-art.sh script helps you to prepare the workstation you are planning to use centos-art.sh script. -3.48.2 Description +3.47.2 Description ------------------ The first time you download CentOS Artwork Repository you need to @@ -3111,7 +3085,7 @@ working copy and the central repository will coordinate time information correctly. Otherwise it would be difficult to find out when changes were committed exactly. -3.48.3 Usage +3.47.3 Usage ------------ `centos-art verify --packages' @@ -3127,18 +3101,18 @@ appropriate way to execute "verify" action is not using the `centos-art' command, but the absolute path to `centos-art.sh' script instead (i.e., `~/artwork/trunk/Scripts/Bash/centos-art.sh'). -3.48.4 See also +3.47.4 See also --------------- -3.49 trunk/Scripts/Bash/Locale +3.48 trunk/Scripts/Bash/Locale ============================== -3.49.1 Goals +3.48.1 Goals ------------ * Organize `centos-art.sh' locale files. -3.49.2 Description +3.48.2 Description ------------------ This command looks for `.sh' files inside Bash directory and extracts @@ -3183,7 +3157,7 @@ favorite text editor. If no value is defined on EDITOR, the At this point, all translations you made in the PO file should be available to your language when runing `centos-art.sh' script. -3.49.2.1 Configuration files +3.48.2.1 Configuration files ............................ In order to make the `centos-art.sh' internationalization, the @@ -3197,10 +3171,10 @@ following files: * `trunk/Scripts/Bash/Functions/Help/cli_localeMessagesStatus.sh' -3.49.3 Usage +3.48.3 Usage ------------ -3.49.3.1 The `centos-art' `locale-cli' action +3.48.3.1 The `centos-art' `locale-cli' action ............................................. `centos-art locale-cli --edit' @@ -3211,51 +3185,51 @@ following files: `centos-art locale-cli --list' Use this command to see the command-line interface locale report. -3.49.4 See also +3.48.4 See also --------------- -3.50 trunk/Scripts/Perl +3.49 trunk/Scripts/Perl ======================= -3.50.1 Goals +3.49.1 Goals ------------ * ... -3.50.2 Description +3.49.2 Description ------------------ -3.50.3 Usage +3.49.3 Usage ------------ -3.50.4 See also +3.49.4 See also --------------- -3.51 trunk/Scripts/Python +3.50 trunk/Scripts/Python ========================= -3.51.1 Goals +3.50.1 Goals ------------ * ... -3.51.2 Description +3.50.2 Description ------------------ * ... -3.51.3 Usage +3.50.3 Usage ------------ * ... -3.51.4 See also +3.50.4 See also --------------- -3.52 trunk/Translations +3.51 trunk/Translations ======================= -3.52.1 Goals +3.51.1 Goals ------------ The `trunk/Translations' directory exists to: @@ -3264,7 +3238,7 @@ The `trunk/Translations' directory exists to: * Organize translation templates used to produce translation files. -3.52.2 Description +3.51.2 Description ------------------ When you create artwork for CentOS distribution you find that some @@ -3301,7 +3275,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.51.2.1 Translation Entries ............................ Translation entries exists for each artwork you want to produce. @@ -3382,7 +3356,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.51.2.2 Translation Markers ............................ Translation markers are used in "Theme Model Designs" and "Translation @@ -3417,7 +3391,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.51.2.3 Translation Files .......................... Translation files are text files with `sed''s commands inside, @@ -3485,7 +3459,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.51.2.4 Template Translation Files ................................... Template translation files are translation files stored inside @@ -3655,7 +3629,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.51.2.5 Common Translation Files ................................. Common translation files contain common translations or no translation @@ -3680,7 +3654,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.51.2.6 Specific Translation Files ................................... Specific translation files contain specific translations for their @@ -3703,7 +3677,7 @@ trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ | `-- splash-small.sed `-- firstboot-left.sed -3.52.2.7 Translation Rendering +3.51.2.7 Translation Rendering .............................. When rendering translations, the `centos-art' script checks the @@ -3714,7 +3688,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.51.2.8 Translation (Pre-)Rendering Configuration Scripts .......................................................... When the `centos-art' script finds a translation template directory @@ -3800,7 +3774,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.51.2.9 Translation Rendering Default Functionality .................................................... In the other hand, if the translation pre-rendering configuration file @@ -3825,7 +3799,7 @@ commands. translation marker section (*note Translation Markers: trunk:Translations:TranslationMarkers.). -3.52.3 Usage +3.51.3 Usage ------------ `centos-art render 'path/to/dir'' @@ -3843,7 +3817,7 @@ commands. you want to render translations for. -3.52.4 See also +3.51.4 See also --------------- ---------- Footnotes ---------- @@ -3855,36 +3829,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.52 trunk/Translations/Identity ================================ -3.53.1 Goals +3.52.1 Goals ------------ * ... -3.53.2 Description +3.52.2 Description ------------------ * ... -3.53.3 Usage +3.52.3 Usage ------------ * ... -3.53.4 See also +3.52.4 See also --------------- -3.54 trunk/Translations/Identity/Brands +3.53 trunk/Translations/Identity/Brands ======================================= -3.54.1 Goals +3.53.1 Goals ------------ * Organize brands' translation files. -3.54.2 Description +3.53.2 Description ------------------ Translation files, inside `trunk/Translations/Identity/Brands' @@ -3917,7 +3891,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.53.2.1 Conventional file names ................................ Convenctional file names look like `blue.sed', `2c-a.sed', etc. @@ -3925,7 +3899,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.53.2.2 Numeric file names ........................... Numeric file names look like `300.sed', `200.sed', etc. Replacements @@ -3946,7 +3920,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.53.2.3 Translation markers ............................ Inside `trunk/Translations/Identity/Brands/', translation files combine @@ -3960,7 +3934,7 @@ the following translation markers: point to template translation files, translation markers are defined inside template translation files. -3.54.3 Usage +3.53.3 Usage ------------ To render brands' translation files, use the following command: @@ -3968,33 +3942,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.53.4 See also --------------- -3.55 trunk/Translations/Identity/Brands/Tpl +3.54 trunk/Translations/Identity/Brands/Tpl =========================================== -3.55.1 Goals +3.54.1 Goals ------------ -3.55.2 Description +3.54.2 Description ------------------ -3.55.3 Usage +3.54.3 Usage ------------ -3.55.4 See also +3.54.4 See also --------------- -3.56 trunk/Translations/Identity/Fonts +3.55 trunk/Translations/Identity/Fonts ====================================== -3.56.1 Goals +3.55.1 Goals ------------ * Organize fonts' translation files. -3.56.2 Description +3.55.2 Description ------------------ Translation files, inside `trunk/Translations/Fonts', have the @@ -4020,7 +3994,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.55.2.1 Translation Markers ............................ Inside `trunk/Translations/Identity/Fonts', translation files combine @@ -4037,7 +4011,7 @@ the following translation markers: `font-style:normal' Specify which font style to use when rendering font preview images. -3.56.3 Usage +3.55.3 Usage ------------ Inside `trunk/Translations/Fonts' you use your favorite text editor to @@ -4050,79 +4024,79 @@ type the following command: vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed -3.56.4 See also +3.55.4 See also --------------- -3.57 trunk/Translations/Identity/Models +3.56 trunk/Translations/Identity/Models ======================================= -3.57.1 Goals +3.56.1 Goals ------------ -3.57.2 Description +3.56.2 Description ------------------ -3.57.3 Usage +3.56.3 Usage ------------ -3.57.4 See also +3.56.4 See also --------------- -3.58 trunk/Translations/Identity/Release +3.57 trunk/Translations/Identity/Release ======================================== -3.58.1 Goals +3.57.1 Goals ------------ -3.58.2 Description +3.57.2 Description ------------------ -3.58.3 Usage +3.57.3 Usage ------------ -3.58.4 See also +3.57.4 See also --------------- -3.59 trunk/Translations/Identity/Themes +3.58 trunk/Translations/Identity/Themes ======================================= -3.59.1 Goals +3.58.1 Goals ------------ -3.59.2 Description +3.58.2 Description ------------------ -3.59.3 Usage +3.58.3 Usage ------------ -3.59.4 See also +3.58.4 See also --------------- -3.60 trunk/Translations/Identity/Themes/Backgrounds +3.59 trunk/Translations/Identity/Themes/Backgrounds =================================================== -3.60.1 Goals +3.59.1 Goals ------------ * ... -3.60.2 Description +3.59.2 Description ------------------ * ... -3.60.3 Usage +3.59.3 Usage ------------ * ... -3.60.4 See also +3.59.4 See also --------------- -3.61 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress +3.60 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress ================================================================ -3.61.1 Goals +3.60.1 Goals ------------ * Organize Anaconda progress translation templates. @@ -4130,7 +4104,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.60.2 Description ------------------ Use the following command to produce translation files based: @@ -4203,131 +4177,129 @@ structure and render them. * *Note trunk Identity Themes Motifs Modern Distro Anaconda Progress::. -3.61.3 Usage +3.60.3 Usage ------------ Translation rendering is described in `trunk/Translations' documentation entry (*note trunk Translations::). -3.61.4 See also +3.60.4 See also --------------- -3.62 trunk/Translations/Identity/Widgets +3.61 trunk/Translations/Identity/Widgets ======================================== -3.62.1 Goals +3.61.1 Goals ------------ * ... -3.62.2 Description +3.61.2 Description ------------------ * ... -3.62.3 Usage +3.61.3 Usage ------------ * ... -3.62.4 See also +3.61.4 See also --------------- Index ***** -branches: See 1. (line 389) -Common translation files: See 3.52.2.5. (line 3661) -How to render brands' translation files: See 3.54.3. (line 3966) -How to render fonts' translation files: See 3.56.3. (line 4043) -How to render translation files: See 3.52.3. (line 3831) -Specific translation files: See 3.52.2.6. (line 3686) -tags: See 2. (line 392) -Template translation files: See 3.52.2.4. (line 3491) -Translation brands file names: See 3.54.2.1. (line 3923) -Translation configuration scripts: See 3.52.2.8. (line 3720) -Translation entries: See 3.52.2.1. (line 3307) -Translation files: See 3.52.2.3. (line 3423) -Translation markers: See 3.52.2.2. (line 3388) -Translation paths: See 3.52.2.1. (line 3307) -Translation pre-rendering configuration scripts:See 3.52.2.8. - (line 3720) -Translation rendering: See 3.52.2.7. (line 3709) -Translation rendering default functionality: See 3.52.2.9. (line 3806) -trunk: See 3. (line 395) -trunk Identity: See 3.1. (line 398) -trunk Identity Brands: See 3.2. (line 818) -trunk Identity Fonts: See 3.3. (line 835) -trunk Identity Icons: See 3.4. (line 911) -trunk Identity Isolinux: See 3.5. (line 928) -trunk Identity Models: See 3.6. (line 945) -trunk Identity Models Css: See 3.7. (line 965) -trunk Identity Models Html: See 3.8. (line 987) -trunk Identity Models Img Promo Web: See 3.9. (line 1008) -trunk Identity Models Tpl: See 3.10. (line 1029) -trunk Identity Models Tpl Promo Web: See 3.11. (line 1050) -trunk Identity Models Xcf: See 3.12. (line 1364) -trunk Identity Release: See 3.13. (line 1385) -trunk Identity Themes: See 3.14. (line 1402) -trunk Identity Themes Models: See 3.15. (line 1427) -trunk Identity Themes Models Alternative: See 3.16. (line 1460) -trunk Identity Themes Models Default: See 3.17. (line 1487) -trunk Identity Themes Models Default Distro: See 3.18. (line 1519) +branches: See 1. (line 384) +Common translation files: See 3.51.2.5. (line 3635) +How to render brands' translation files: See 3.53.3. (line 3940) +How to render fonts' translation files: See 3.55.3. (line 4017) +How to render translation files: See 3.51.3. (line 3805) +Specific translation files: See 3.51.2.6. (line 3660) +tags: See 2. (line 387) +Template translation files: See 3.51.2.4. (line 3465) +Translation brands file names: See 3.53.2.1. (line 3897) +Translation configuration scripts: See 3.51.2.8. (line 3694) +Translation entries: See 3.51.2.1. (line 3281) +Translation files: See 3.51.2.3. (line 3397) +Translation markers: See 3.51.2.2. (line 3362) +Translation paths: See 3.51.2.1. (line 3281) +Translation pre-rendering configuration scripts:See 3.51.2.8. + (line 3694) +Translation rendering: See 3.51.2.7. (line 3683) +Translation rendering default functionality: See 3.51.2.9. (line 3780) +trunk: See 3. (line 390) +trunk Identity: See 3.1. (line 393) +trunk Identity Brands: See 3.2. (line 813) +trunk Identity Fonts: See 3.3. (line 830) +trunk Identity Icons: See 3.4. (line 906) +trunk Identity Isolinux: See 3.5. (line 923) +trunk Identity Models: See 3.6. (line 940) +trunk Identity Models Css: See 3.7. (line 960) +trunk Identity Models Html: See 3.8. (line 982) +trunk Identity Models Img Promo Web: See 3.9. (line 1003) +trunk Identity Models Tpl: See 3.10. (line 1024) +trunk Identity Models Tpl Promo Web: See 3.11. (line 1045) +trunk Identity Models Xcf: See 3.12. (line 1359) +trunk Identity Release: See 3.13. (line 1380) +trunk Identity Themes: See 3.14. (line 1397) +trunk Identity Themes Models: See 3.15. (line 1422) +trunk Identity Themes Models Alternative: See 3.16. (line 1455) +trunk Identity Themes Models Default: See 3.17. (line 1482) +trunk Identity Themes Models Default Distro: See 3.18. (line 1514) trunk Identity Themes Models Default Distro Anaconda:See 3.19. - (line 1603) -trunk Identity Themes Models Default Promo: See 3.20. (line 1620) -trunk Identity Themes Models Default Web: See 3.21. (line 1646) -trunk Identity Themes Motifs: See 3.22. (line 1671) -trunk Identity Themes Motifs Modern Backgrounds:See 3.23. (line 1775) + (line 1598) +trunk Identity Themes Models Default Promo: See 3.20. (line 1615) +trunk Identity Themes Models Default Web: See 3.21. (line 1641) +trunk Identity Themes Motifs: See 3.22. (line 1666) +trunk Identity Themes Motifs Modern Backgrounds:See 3.23. (line 1770) trunk Identity Themes Motifs Modern Backgrounds Img:See 3.24. - (line 1897) + (line 1892) trunk Identity Themes Motifs Modern Backgrounds Tpl:See 3.25. - (line 1918) + (line 1913) trunk Identity Themes Motifs Modern Backgrounds Xcf:See 3.26. - (line 1939) + (line 1934) trunk Identity Themes Motifs Modern Distro Anaconda Progress:See 3.27. - (line 1966) -trunk Identity Themes Motifs Modern Palettes: See 3.28. (line 2022) -trunk Identity Themes Motifs TreeFlower: See 3.29. (line 2044) + (line 1961) +trunk Identity Themes Motifs Modern Palettes: See 3.28. (line 2017) +trunk Identity Themes Motifs TreeFlower: See 3.29. (line 2039) trunk Identity Themes Motifs TreeFlower Backgrounds:See 3.30. - (line 2061) -trunk Identity Widgets: See 3.31. (line 2357) -trunk Manuals: See 3.32. (line 2374) -trunk Scripts: See 3.33. (line 2428) -trunk Scripts Bash: See 3.34. (line 2452) -trunk Scripts Bash Functions: See 3.35. (line 2585) -trunk Scripts Bash Functions Help: See 3.36. (line 2606) -trunk Scripts Bash Functions Html: See 3.37. (line 2627) -trunk Scripts Bash Functions Locale: See 3.38. (line 2648) -trunk Scripts Bash Functions Path: See 3.39. (line 2669) -trunk Scripts Bash Functions Prepare prepare_forUsingPackages.sh:See 3.40. - (line 2703) -trunk Scripts Bash Functions Render: See 3.41. (line 2724) -trunk Scripts Bash Functions Render Config: See 3.42. (line 2745) -trunk Scripts Bash Functions Render render_getActions.sh:See 3.44. - (line 2944) -trunk Scripts Bash Functions Render render_getActionsIdentity.sh:See 3.43. - (line 2923) -trunk Scripts Bash Functions Render render_getActionsTranslations.sh:See 3.45. - (line 2965) -trunk Scripts Bash Functions Shell: See 3.46. (line 2986) -trunk Scripts Bash Functions Svg: See 3.47. (line 3007) -trunk Scripts Bash Functions Verify: See 3.48. (line 3051) -trunk Scripts Bash Locale: See 3.49. (line 3136) -trunk Scripts Perl: See 3.50. (line 3220) -trunk Scripts Python: See 3.51. (line 3237) -trunk Translations: See 3.52. (line 3258) -trunk Translations Identity: See 3.53. (line 3861) -trunk Translations Identity Brands: See 3.54. (line 3882) -trunk Translations Identity Brands Tpl: See 3.55. (line 3977) -trunk Translations Identity Fonts: See 3.56. (line 3992) -trunk Translations Identity Models: See 3.57. (line 4059) -trunk Translations Identity Release: See 3.58. (line 4074) -trunk Translations Identity Themes: See 3.59. (line 4089) -trunk Translations Identity Themes Backgrounds:See 3.60. (line 4104) -trunk Translations Identity Themes Distro Anaconda Progress:See 3.61. - (line 4125) -trunk Translations Identity Widgets: See 3.62. (line 4218) + (line 2056) +trunk Identity Widgets: See 3.31. (line 2352) +trunk Manuals: See 3.32. (line 2369) +trunk Scripts: See 3.33. (line 2423) +trunk Scripts Bash: See 3.34. (line 2447) +trunk Scripts Bash Functions: See 3.35. (line 2580) +trunk Scripts Bash Functions Help: See 3.36. (line 2601) +trunk Scripts Bash Functions Html: See 3.37. (line 2622) +trunk Scripts Bash Functions Locale: See 3.38. (line 2643) +trunk Scripts Bash Functions Path: See 3.39. (line 2664) +trunk Scripts Bash Functions Render: See 3.40. (line 2698) +trunk Scripts Bash Functions Render Config: See 3.41. (line 2719) +trunk Scripts Bash Functions Render render_getActions.sh:See 3.43. + (line 2918) +trunk Scripts Bash Functions Render render_getActionsIdentity.sh:See 3.42. + (line 2897) +trunk Scripts Bash Functions Render render_getActionsTranslations.sh:See 3.44. + (line 2939) +trunk Scripts Bash Functions Shell: See 3.45. (line 2960) +trunk Scripts Bash Functions Svg: See 3.46. (line 2981) +trunk Scripts Bash Functions Verify: See 3.47. (line 3025) +trunk Scripts Bash Locale: See 3.48. (line 3110) +trunk Scripts Perl: See 3.49. (line 3194) +trunk Scripts Python: See 3.50. (line 3211) +trunk Translations: See 3.51. (line 3232) +trunk Translations Identity: See 3.52. (line 3835) +trunk Translations Identity Brands: See 3.53. (line 3856) +trunk Translations Identity Brands Tpl: See 3.54. (line 3951) +trunk Translations Identity Fonts: See 3.55. (line 3966) +trunk Translations Identity Models: See 3.56. (line 4033) +trunk Translations Identity Release: See 3.57. (line 4048) +trunk Translations Identity Themes: See 3.58. (line 4063) +trunk Translations Identity Themes Backgrounds:See 3.59. (line 4078) +trunk Translations Identity Themes Distro Anaconda Progress:See 3.60. + (line 4099) +trunk Translations Identity Widgets: See 3.61. (line 4192) List of Figures *************** diff --git a/Manuals/en/Texinfo/Repository/trunk/chapter-menu.texi b/Manuals/en/Texinfo/Repository/trunk/chapter-menu.texi index af89244..2763876 100644 --- a/Manuals/en/Texinfo/Repository/trunk/chapter-menu.texi +++ b/Manuals/en/Texinfo/Repository/trunk/chapter-menu.texi @@ -38,7 +38,6 @@ * trunk Scripts Bash Functions Html:: * trunk Scripts Bash Functions Locale:: * trunk Scripts Bash Functions Path:: -* trunk Scripts Bash Functions Prepare prepare_forUsingPackages.sh:: * trunk Scripts Bash Functions Render:: * trunk Scripts Bash Functions Render Config:: * trunk Scripts Bash Functions Render render_getActionsIdentity.sh:: diff --git a/Manuals/en/Texinfo/Repository/trunk/chapter-nodes.texi b/Manuals/en/Texinfo/Repository/trunk/chapter-nodes.texi index d07602d..cc1ddd0 100644 --- a/Manuals/en/Texinfo/Repository/trunk/chapter-nodes.texi +++ b/Manuals/en/Texinfo/Repository/trunk/chapter-nodes.texi @@ -193,11 +193,6 @@ @cindex trunk Scripts Bash Functions Path @include trunk/Scripts/Bash/Functions/Path.texi -@node trunk Scripts Bash Functions Prepare prepare_forUsingPackages.sh -@section trunk/Scripts/Bash/Functions/Prepare/prepare_forUsingPackages.sh -@cindex trunk Scripts Bash Functions Prepare prepare_forUsingPackages.sh -@include trunk/Scripts/Bash/Functions/Prepare/prepare_forUsingPackages.sh.texi - @node trunk Scripts Bash Functions Render @section trunk/Scripts/Bash/Functions/Render @cindex trunk Scripts Bash Functions Render