From 5fb0249a795d7b399818f8102774dfa2497f4dc4 Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: Oct 13 2010 03:48:27 +0000 Subject: Update documentation manuals. --- diff --git a/Manuals/en/Html/Repository/repository.html b/Manuals/en/Html/Repository/repository.html index d08c7e3..9661457 100644 --- a/Manuals/en/Html/Repository/repository.html +++ b/Manuals/en/Html/Repository/repository.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + - + - + -CentOS Artwork Repository: 3.7 trunk/Identity/Models/Img/Promo/Web +CentOS Artwork Repository: 3.7 trunk/Identity/Models/Css - - + + @@ -61,28 +61,27 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.7 trunk/Identity/Models/Img/Promo/Web

+

3.7 trunk/Identity/Models/Css

3.7.1 Goals

- - +

This directory exists to provide common style sheets (CSS) definitions +to HTML design models. +

3.7.2 Description

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

3.7.4 See also

- - -
3.8 trunk/Identity/Models/Tpl/Promo/Web   -
@@ -115,11 +110,11 @@ ul.toc {list-style: none} - +
  [ << ] [ Up ][ >> ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_11.html b/Manuals/en/Html/Repository/repository_11.html index 251ebb9..578879d 100644 --- a/Manuals/en/Html/Repository/repository_11.html +++ b/Manuals/en/Html/Repository/repository_11.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.8 trunk/Identity/Models/Tpl/Promo/Web +CentOS Artwork Repository: 3.8 trunk/Identity/Models/Html - - + + @@ -61,366 +61,38 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.8 trunk/Identity/Models/Tpl/Promo/Web

+

3.8 trunk/Identity/Models/Html

3.8.1 Goals

-

Organize scalable vector graphics (svg) to help describe the CentOS -web environment. -

+ + -

3.8.2 The CentOS web environment

+

3.8.2 Description

-

Inside CentOS corporate identity, the CentOS web environment is -considered a promotion component. The CentOS web environment is formed -by a central web application --to cover base needs (e.g., per-major -release information like release notes, lifetime, downloads, -documentation, support, security advisories, bugs, etc.)-- and many -different free web applications --to cover specific needs (e.g., -wiki, mailing lists, etc.)--. -

-

The CentOS web environment is addressed to solve the following issues: -

-

The CentOS project is attached to a monolithic corporate visual -identity (see section trunk/Identity), where all visual manifestations -have one unique name and one unique visual style. This way, the CentOS -web environment has one unique name (the CentOS brand) and one unique -visual style (the CentOS default theme) for all its visual -manifestations, the web applications in this case. -

-

Since a maintainance point of view, achiving the one unique visual -style inside CentOS web environment is not a simple task. The CentOS -web environment is built upon many different web applications which -have different visual styles and different internal ways to customize -their own visual styles. For example: MoinMoin, the web application -used to support the CentOS wiki (http://wiki.centos.org/) is -highly customizable but Mailman (in its 2.x.x serie), the web -application used to support the CentOS mailing list, doesn't -support(1) a customization system that separates -presentation from logic, similar to MoinMoin's one. -

-

This visual style diversity complicates our goal of one unique visual -style for all web applications. So, if we want one unique visual style -for all web applications used, it is innevitable to modify the web -applications in order to implement the CentOS one unique visual style -customization in them. Direct modification of upstream applications is -not convenient because upstream applications come with their one -visual style and administrators take the risk of loosing all -customization changes the next time the application be updated (since -not all upstream web applications, used in CentOS web environment, -separate presentation from logic). -

-

To solve the "one unique visual style" issue, installation and -actualization of web applications --used inside CentOS web -environment-- need to be independent from upstream web applications -development line; in a way that CentOS web environment administrators -can install and update web applications freely without risk of loosing -the one unique visual style customization changes. -

-

At the surface of this issue we can see the need of one specific yum -repository to store CentOS web environment customized web applications. -

-

3.8.2.1 Design model (without ads)

- -
-

The CentOS web customization design model - -

Figure 3.1: The CentOS web customization design model. - -

- - -

3.8.2.2 Design model (with ads)

- -
-

The CentOS web customization design model using promotion - -

Figure 3.2: The CentOS web customization using promotion design model. - -

- - -

3.8.2.3 HTML definitions

- -
-

Web environment html defintions - -

Figure 3.3: Web environment html definitions - -

- - -

3.8.2.4 Controlling visual style

- -

Inside CentOS web environment, the visual style is controlled by the -following compenents: -

-
-
Webenv header background
-
trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Img/1024x250.png
-
-
-
CSS definitions
-
trunk/Identity/Themes/Models/Default/Promo/Web/CSS/stylesheet.css
-
-
- - - -

3.8.2.5 Producing visual style

- -

The visual style of CentOS web environment is defined in the following -files: -

-
trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Xcf/1024x250.xcf
-trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Img/1024x250.png
-trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Img/1024x250-bg.png
-trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Tpl/1024x250.svg
-
-

As graphic designer you use `1024x250.xcf' file to produce -`1024x250-bg.png' file. Later, inside `1024x250.svg' file, -you use the `1024x250-bg.png' file as background layer to draw -your vectorial design. When you consider you artwork ready, use the -centos-art.sh script, as described below, to produce the -visual style controller images of CentOS web environment. -

-
centos-art render --entry=trunk/Identity/Themes/Motifs/$THEME/Backgrounds --filter='1024x250'
-
-

Once you have rendered required image files, changing the visual style -of CentOS web environment is a matter of replacing old image files -with new ones, inside webenv repository file system structure. The -visual style changes will take effect the next time customization line -of CentOS web applications be packaged, uploded, and installed from -[webenv] or [webenv-test] repositories. -

- - -

3.8.2.6 Navigation

- -

Inside CentOS web environment, the one-step navegation between web -applications is addressed using the web environment navigation bar. -The web environment navigation bar contains links to main applications -and is always visible no matter where you are inside the web -environment. -

-
-

The CentOS web navigation design model - -

Figure 3.4: The CentOS web navigation design model. - -

- - -

3.8.2.7 Development and release cycle

- -

The CentOS web environment development and relase cycle is described -below: -

-
-
Download
-
-

The first action is download the source code of web applications we -want to use inside CentOS web environment. -

-
Important

Important

The source location from which web application are -downloaded is very important. Use SRPMs from CentOS [base] -and [updates] repositories as first choise, and third party -repositories (e.g. RPMForge, EPEL, etc.) as last resource. -

- -
-
Prepare
-
-

Once web application source code has been downloaded, our duty is -organize its files inside `webenv' version controlled repository. -

-

When preparing the structure keep in mind that different web -applications have different visual styles, and also different ways to -implement it. A convenient way to organize the file system structure -would be create one development line for each web application we use -inside CentOS web environment. For example, consider the following -file system structure: -

-
https://projects.centos.org/svn/webenv/trunk/
-|-- WebApp1/
-|   |-- Sources/
-|   |   `-- webapp1-0.0.1/
-|   |-- Rpms/
-|   |   `-- webapp1-0.0.1.rpm
-|   |-- Srpms/
-|   |   `-- webapp1-0.0.1.srpm
-|   `-- Specs/
-|       `-- webapp1-0.0.1.spec
-|-- WebApp2/
-`-- WebAppN/
-
-
-
Customize
-
-

Once web applications have been organized inside the version -controlled repository file system, use subversion to create the CentOS -customization development line of web applications source code. For -example, using the above file system structure, you can create the -customization development line of `webapp1-0.0.1/' with the -following command: -

-
svn cp trunk/WebApp1/Sources/webapp1-0.0.1 trunk/WebApp1/Sources/webapp1-0.0.1-webenv
-
-

The command above creates the following structure: -

-
https://projects.centos.org/svn/webenv/trunk/
-|-- WebApp1/
-|   |-- Sources/
-|   |   |-- webapp1-0.0.1/
-|   |   `-- webapp1-0.0.1-webenv/
-|   |-- Rpms/
-|   |   `-- webapp1-0.0.1.rpm
-|   |-- Srpms/
-|   |   `-- webapp1-0.0.1.srpm
-|   `-- Specs/
-|       `-- webapp1-0.0.1.spec
-|-- WebApp2/
-`-- WebAppN/
-
-

In the above structure, the `webapp1-0.0.1-webenv/' directory is -the place where you customize the visual style of -`webapp1-0.0.1/' web application. -

-
Info

Tip

Use Subversion's diff between CentOS -customization and upstream development lines to know what you are -changing exactly. -

- -
-
Build packages
-
-

When web application has been customized, build the web application -RPM and SRPM using the source location with `-webenv' prefix. -

-
https://projects.centos.org/svn/webenv/trunk/
-|-- WebApp1/
-|   |-- Sources/
-|   |   |-- webapp1-0.0.1/
-|   |   `-- webapp1-0.0.1-webenv/
-|   |-- Rpms/
-|   |   |-- webapp1-0.0.1.rpm
-|   |   `-- webapp1-0.0.1-webenv.rpm
-|   |-- Srpms/
-|   |   |-- webapp1-0.0.1.srpm
-|   |   `-- webapp1-0.0.1-webenv.srpm
-|   `-- Specs/
-|       |-- webapp1-0.0.1.spec
-|       `-- webapp1-0.0.1-webenv.spec
-|-- WebApp2/
-`-- WebAppN/
-
-
-
Release for testing
-
-

When the customized web application has been packaged, make packages -available for testing and quality assurance. This can be achives using -a [webenv-test] yum repository. -

-
info

Note

The [webenv-test] repository is not shipped inside -CentOS distribution default yum configuraiton. In order to use -[webenv-test] repository you need to configure it first. -

- -

If some problem is found to install/update/use the customized version -of web application, the problem is notified somewhere (a bugtracker -maybe) and the customization face is repated in order to fix the -problem. To release the new package add a number after `-webenv' -prefix. For example, if some problem is found in -`webapp1-0.0.1-webenv.rpm', when it be fixed the new package will -be named `webapp1-0.0.1-webenv-1.rpm'. If a problem is found in -`webapp1-0.0.1-webenv-1.rpm', when it be fixed the new package -will be named `webapp1-0.0.1-webenv-2.rpm', and so on. -

-

The "customization -- release for testing" process is repeated -until CentOS quality assurance team considers the package is ready for -production. -

-
-
Release for production
-
-

When customized web application packages are considered ready for -production they are moved from [webenv-test] to [webenv] repository. -This action is commited by CentOS quality assurance team. -

-
info

Note

The [webenv] repository is not shipped inside CentOS -distribution default yum configuraiton. In order to use [webenv] -repository you need to configure it first. -

-
-
- - - -

3.8.2.8 The [webenv-test] repository

- -
/etc/yum.repos.d/CentOS-Webenv-test.repo
-
-
[webenv-test]
-name=CentOS-$releasever - Webenv-test
-mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv-test
-#baseurl=http://mirror.centos.org/centos/$releasever/webenv-test/$basearch/
-gpgcheck=1
-gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever
-enabled=1
-priority=10
-
- - -

3.8.2.9 The [webenv] repository

- -
/etc/yum.repos.d/CentOS-Webenv.repo
-
-
[webenv]
-name=CentOS-$releasever - Webenv
-mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv
-#baseurl=http://mirror.centos.org/centos/$releasever/webenv/$basearch/
-gpgcheck=1
-gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever
-enabled=1
-priority=10
-
- - -

3.8.2.10 Priority configuration

- -

Both [webenv] and [webenv-test] repositories update packages inside -CentOS [base] and CentOS [updates] repositories. -

- -

3.8.3 Usage

- +

3.8.4 See also

- - -
3.7 trunk/Identity/Models/Img/Promo/Web   -
- - + + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_12.html b/Manuals/en/Html/Repository/repository_12.html index 9354f98..09c5bba 100644 --- a/Manuals/en/Html/Repository/repository_12.html +++ b/Manuals/en/Html/Repository/repository_12.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.9 trunk/Identity/Release +CentOS Artwork Repository: 3.9 trunk/Identity/Models/Img/Promo/Web - - + + @@ -56,58 +56,70 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.9 trunk/Identity/Release

+ + +

3.9 trunk/Identity/Models/Img/Promo/Web

- +

3.9.1 Goals

- +

3.9.2 Description

+ + - +

3.9.3 Usage

+ + - +

3.9.4 See also

+ + +
3.11 trunk/Identity/Models/Tpl/Promo/Web   +
- - + + - - + +
[ < ][ > ]
[ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_13.html b/Manuals/en/Html/Repository/repository_13.html index 28a8caa..210ea43 100644 --- a/Manuals/en/Html/Repository/repository_13.html +++ b/Manuals/en/Html/Repository/repository_13.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.10 trunk/Identity/Themes +CentOS Artwork Repository: 3.10 trunk/Identity/Models/Tpl - - + + @@ -56,74 +56,66 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.10 trunk/Identity/Themes

+ + +

3.10 trunk/Identity/Models/Tpl

- +

3.10.1 Goals

-

The `trunk/Identity/Themes/' directory exists to: -

- +

3.10.2 Description

+ + - +

3.10.3 Usage

-

In this location themes are organized in "Models" --to store common -information-- and "Motifs"--to store unique information. At -rendering time, both motifs and models are combined to produce the -final CentOS themes. CentOS themes can be tagged as "Default" or -"Alternative". CentOS themes are maintained by CentOS community. -

+ + - +

3.10.4 See also

- - - - -
3.18 trunk/Identity/Themes/Motifs   -
3.11 trunk/Identity/Themes/Models   -
3.55 trunk/Translations/Identity/Themes   -
- - + + - - + +
[ < ][ > ]
[ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_14.html b/Manuals/en/Html/Repository/repository_14.html index 3c868f8..00d00b5 100644 --- a/Manuals/en/Html/Repository/repository_14.html +++ b/Manuals/en/Html/Repository/repository_14.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.11 trunk/Identity/Themes/Models +CentOS Artwork Repository: 3.11 trunk/Identity/Models/Tpl/Promo/Web - - + + @@ -56,59 +56,385 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.11 trunk/Identity/Themes/Models

+ + +

3.11 trunk/Identity/Models/Tpl/Promo/Web

- +

3.11.1 Goals

+

Organize scalable vector graphics (svg) to help describe the CentOS +web environment. +

+ + +

3.11.2 The CentOS web environment

+ +

Inside CentOS corporate identity, the CentOS web environment is +considered a promotion component. The CentOS web environment is formed +by a central web application --to cover base needs (e.g., per-major +release information like release notes, lifetime, downloads, +documentation, support, security advisories, bugs, etc.)-- and many +different free web applications --to cover specific needs (e.g., +wiki, mailing lists, etc.)--. +

+

The CentOS web environment is addressed to solve the following issues: +

+

The CentOS project is attached to a monolithic corporate visual +identity (see section trunk/Identity), where all visual manifestations +have one unique name and one unique visual style. This way, the CentOS +web environment has one unique name (the CentOS brand) and one unique +visual style (the CentOS default theme) for all its visual +manifestations, the web applications in this case. +

+

Since a maintainance point of view, achiving the one unique visual +style inside CentOS web environment is not a simple task. The CentOS +web environment is built upon many different web applications which +have different visual styles and different internal ways to customize +their own visual styles. For example: MoinMoin, the web application +used to support the CentOS wiki (http://wiki.centos.org/) is +highly customizable but Mailman (in its 2.x.x serie), the web +application used to support the CentOS mailing list, doesn't +support(1) a customization system that separates +presentation from logic, similar to MoinMoin's one. +

+

This visual style diversity complicates our goal of one unique visual +style for all web applications. So, if we want one unique visual style +for all web applications used, it is innevitable to modify the web +applications in order to implement the CentOS one unique visual style +customization in them. Direct modification of upstream applications is +not convenient because upstream applications come with their one +visual style and administrators take the risk of loosing all +customization changes the next time the application be updated (since +not all upstream web applications, used in CentOS web environment, +separate presentation from logic). +

+

To solve the "one unique visual style" issue, installation and +actualization of web applications --used inside CentOS web +environment-- need to be independent from upstream web applications +development line; in a way that CentOS web environment administrators +can install and update web applications freely without risk of loosing +the one unique visual style customization changes. +

+

At the surface of this issue we can see the need of one specific yum +repository to store CentOS web environment customized web applications. +

- -

3.11.2 Description

+ +

3.11.2.1 Design model (without ads)

+ +
+

The CentOS web customization design model -

Theme models let you modeling characteristics (e.g., dimensions, -translation markers, position of each element on the display area, -etc.) common to all themes. Theme models let you reduce the time -needed when propagating artistic motifs to different visual -manifestations. +

Figure 3.1: The CentOS web customization design model. +

-

Theme models serves as a central pool of design templates for themes -to use. This way you can produce themes with different artistic motifs -but same characteristics. + + +

3.11.2.2 Design model (with ads)

+ +
+

The CentOS web customization design model using promotion + +

Figure 3.2: The CentOS web customization using promotion design model. + +

+ + +

3.11.2.3 HTML definitions

+ +
+

Web environment html defintions + +

Figure 3.3: Web environment html definitions + +

+ + +

3.11.2.4 Controlling visual style

+ +

Inside CentOS web environment, the visual style is controlled by the +following compenents: +

+
+
Webenv header background
+
trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Img/1024x250.png
+
+
+
CSS definitions
+
trunk/Identity/Themes/Models/Default/Promo/Web/CSS/stylesheet.css
+
+
+ + + +

3.11.2.5 Producing visual style

+ +

The visual style of CentOS web environment is defined in the following +files: +

+
trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Xcf/1024x250.xcf
+trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Img/1024x250.png
+trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Img/1024x250-bg.png
+trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Tpl/1024x250.svg
+
+

As graphic designer you use `1024x250.xcf' file to produce +`1024x250-bg.png' file. Later, inside `1024x250.svg' file, +you use the `1024x250-bg.png' file as background layer to draw +your vectorial design. When you consider you artwork ready, use the +centos-art.sh script, as described below, to produce the +visual style controller images of CentOS web environment. +

+
centos-art render --entry=trunk/Identity/Themes/Motifs/$THEME/Backgrounds --filter='1024x250'
+
+

Once you have rendered required image files, changing the visual style +of CentOS web environment is a matter of replacing old image files +with new ones, inside webenv repository file system structure. The +visual style changes will take effect the next time customization line +of CentOS web applications be packaged, uploded, and installed from +[webenv] or [webenv-test] repositories. +

+ + +

3.11.2.6 Navigation

+ +

Inside CentOS web environment, the one-step navegation between web +applications is addressed using the web environment navigation bar. +The web environment navigation bar contains links to main applications +and is always visible no matter where you are inside the web +environment. +

+
+

The CentOS web navigation design model + +

Figure 3.4: The CentOS web navigation design model. + +

+ + +

3.11.2.7 Development and release cycle

+ +

The CentOS web environment development and relase cycle is described +below: +

+
+
Download
+
+

The first action is download the source code of web applications we +want to use inside CentOS web environment. +

+
Important

Important

The source location from which web application are +downloaded is very important. Use SRPMs from CentOS [base] +and [updates] repositories as first choise, and third party +repositories (e.g. RPMForge, EPEL, etc.) as last resource. +

+ +
+
Prepare
+
+

Once web application source code has been downloaded, our duty is +organize its files inside `webenv' version controlled repository. +

+

When preparing the structure keep in mind that different web +applications have different visual styles, and also different ways to +implement it. A convenient way to organize the file system structure +would be create one development line for each web application we use +inside CentOS web environment. For example, consider the following +file system structure: +

+
https://projects.centos.org/svn/webenv/trunk/
+|-- WebApp1/
+|   |-- Sources/
+|   |   `-- webapp1-0.0.1/
+|   |-- Rpms/
+|   |   `-- webapp1-0.0.1.rpm
+|   |-- Srpms/
+|   |   `-- webapp1-0.0.1.srpm
+|   `-- Specs/
+|       `-- webapp1-0.0.1.spec
+|-- WebApp2/
+`-- WebAppN/
+
+
+
Customize
+
+

Once web applications have been organized inside the version +controlled repository file system, use subversion to create the CentOS +customization development line of web applications source code. For +example, using the above file system structure, you can create the +customization development line of `webapp1-0.0.1/' with the +following command: +

+
svn cp trunk/WebApp1/Sources/webapp1-0.0.1 trunk/WebApp1/Sources/webapp1-0.0.1-webenv
+
+

The command above creates the following structure: +

+
https://projects.centos.org/svn/webenv/trunk/
+|-- WebApp1/
+|   |-- Sources/
+|   |   |-- webapp1-0.0.1/
+|   |   `-- webapp1-0.0.1-webenv/
+|   |-- Rpms/
+|   |   `-- webapp1-0.0.1.rpm
+|   |-- Srpms/
+|   |   `-- webapp1-0.0.1.srpm
+|   `-- Specs/
+|       `-- webapp1-0.0.1.spec
+|-- WebApp2/
+`-- WebAppN/
+
+

In the above structure, the `webapp1-0.0.1-webenv/' directory is +the place where you customize the visual style of +`webapp1-0.0.1/' web application. +

+
Info

Tip

Use Subversion's diff between CentOS +customization and upstream development lines to know what you are +changing exactly. +

+ +
+
Build packages
+
+

When web application has been customized, build the web application +RPM and SRPM using the source location with `-webenv' prefix. +

+
https://projects.centos.org/svn/webenv/trunk/
+|-- WebApp1/
+|   |-- Sources/
+|   |   |-- webapp1-0.0.1/
+|   |   `-- webapp1-0.0.1-webenv/
+|   |-- Rpms/
+|   |   |-- webapp1-0.0.1.rpm
+|   |   `-- webapp1-0.0.1-webenv.rpm
+|   |-- Srpms/
+|   |   |-- webapp1-0.0.1.srpm
+|   |   `-- webapp1-0.0.1-webenv.srpm
+|   `-- Specs/
+|       |-- webapp1-0.0.1.spec
+|       `-- webapp1-0.0.1-webenv.spec
+|-- WebApp2/
+`-- WebAppN/
+
+
+
Release for testing
+
+

When the customized web application has been packaged, make packages +available for testing and quality assurance. This can be achives using +a [webenv-test] yum repository. +

+
info

Note

The [webenv-test] repository is not shipped inside +CentOS distribution default yum configuraiton. In order to use +[webenv-test] repository you need to configure it first. +

+ +

If some problem is found to install/update/use the customized version +of web application, the problem is notified somewhere (a bugtracker +maybe) and the customization face is repated in order to fix the +problem. To release the new package add a number after `-webenv' +prefix. For example, if some problem is found in +`webapp1-0.0.1-webenv.rpm', when it be fixed the new package will +be named `webapp1-0.0.1-webenv-1.rpm'. If a problem is found in +`webapp1-0.0.1-webenv-1.rpm', when it be fixed the new package +will be named `webapp1-0.0.1-webenv-2.rpm', and so on. +

+

The "customization -- release for testing" process is repeated +until CentOS quality assurance team considers the package is ready for +production. +

+
+
Release for production
+
+

When customized web application packages are considered ready for +production they are moved from [webenv-test] to [webenv] repository. +This action is commited by CentOS quality assurance team. +

+
info

Note

The [webenv] repository is not shipped inside CentOS +distribution default yum configuraiton. In order to use [webenv] +repository you need to configure it first. +

+
+
+ + + +

3.11.2.8 The [webenv-test] repository

+ +
/etc/yum.repos.d/CentOS-Webenv-test.repo
+
+
[webenv-test]
+name=CentOS-$releasever - Webenv-test
+mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv-test
+#baseurl=http://mirror.centos.org/centos/$releasever/webenv-test/$basearch/
+gpgcheck=1
+gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever
+enabled=1
+priority=10
+
+ + +

3.11.2.9 The [webenv] repository

+ +
/etc/yum.repos.d/CentOS-Webenv.repo
+
+
[webenv]
+name=CentOS-$releasever - Webenv
+mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv
+#baseurl=http://mirror.centos.org/centos/$releasever/webenv/$basearch/
+gpgcheck=1
+gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever
+enabled=1
+priority=10
+
+ + +

3.11.2.10 Priority configuration

+ +

Both [webenv] and [webenv-test] repositories update packages inside +CentOS [base] and CentOS [updates] repositories.

3.11.3 Usage

-

Inside the framework location above, you find theme models organized -by name. You can add your own theme models to the structure by adding -a directory to the list. By default you have the `See section Default,' and `See section Alternative,' ready-to-use theme models. -

+ +

3.11.4 See also

+ + +
3.9 trunk/Identity/Models/Img/Promo/Web   +
@@ -116,12 +442,12 @@ a directory to the list. By default you have the `See section [ > ] - - + +
  [ << ][ Up ][ >> ][ Up ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_15.html b/Manuals/en/Html/Repository/repository_15.html index 34537ac..f671cef 100644 --- a/Manuals/en/Html/Repository/repository_15.html +++ b/Manuals/en/Html/Repository/repository_15.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.12 trunk/Identity/Themes/Models/Alternative +CentOS Artwork Repository: 3.12 trunk/Identity/Models/Xcf - - + + @@ -61,19 +61,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.12 trunk/Identity/Themes/Models/Alternative

+

3.12 trunk/Identity/Models/Xcf

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

3.12.2 Description

-

CentOS alternative theme models exist for people how want to use a -different visual style on their installations of CentOS distribution. -As the visual style is needed for a system already installed -components like Anaconda are not required inside alternative themes. -Inside alternative themes you find post-installation visual style only -(i.e. Backgrounds, Display Managers, Grub, etc.). CentOS alternative -themes are maintained by CentOS Community. -

+ +

3.12.3 Usage

@@ -115,11 +111,11 @@ themes are maintained by CentOS Community.   [ << ] [ Up ] -[ >> ] +[ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_16.html b/Manuals/en/Html/Repository/repository_16.html index 75f1b9f..306d25d 100644 --- a/Manuals/en/Html/Repository/repository_16.html +++ b/Manuals/en/Html/Repository/repository_16.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.13 trunk/Identity/Themes/Models/Default +CentOS Artwork Repository: 3.13 trunk/Identity/Release - - + + @@ -61,29 +61,28 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.13 trunk/Identity/Themes/Models/Default

+

3.13 trunk/Identity/Release

3.13.1 Goals

-

This location stores CentOS default theme model. The CentOS default -theme model is used in all visual manifestations of CentOS Project's -corporate visual identity (e.g., distributions, web sites, promotion, -etc.). -

+ +

3.13.2 Description

@@ -92,18 +91,6 @@ etc.).

3.13.3 Usage

-

Changing CentOS default theme is not very convenient because that -affects the "recognition" of CentOS Project. Nevertheless, we are -interested on seeing your art work propositions. Specially if your -art work is an improvement to the base idea behind CentOS default -theme (Modern, squares and circles flowing up.). -

-

If you are not happy with CentOS default theme, you can look inside -CentOS alternative themes and download the one you are interested in. -If you are not happy with any of the CentOS alternative themes -available, then go and design your own CentOS alternative theme as -described in See section Theme Motifs. -

3.13.4 See also

@@ -116,11 +103,11 @@ described in See section Theme Motifs.   [ << ] [ Up ] -[ >> ] +[ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_17.html b/Manuals/en/Html/Repository/repository_17.html index 964f706..9e65a5d 100644 --- a/Manuals/en/Html/Repository/repository_17.html +++ b/Manuals/en/Html/Repository/repository_17.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.14 trunk/Identity/Themes/Models/Default/Distro +CentOS Artwork Repository: 3.14 trunk/Identity/Themes - - + + @@ -61,125 +61,69 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.14 trunk/Identity/Themes/Models/Default/Distro

+

3.14 trunk/Identity/Themes

3.14.1 Goals

+

The `trunk/Identity/Themes/' directory exists to: +

3.14.2 Description

-

It applies to all major releases of CentOS distribution. -

-

3.14.2.1 One theme for all major releases

+

3.14.3 Usage

-

Sometimes, specific visual manifestations are formed by common -components which have internal differences. That is the case of CentOS -distribution visual manifestation. -

-

Since a visual style point of view, the CentOS distributions share -common artwork components like Anaconda --to cover the CentOS -distribution installation--, BootUp --to cover the CentOS -distribution start up--, and Backgrounds --to cover the CentOS -distribution desktop--. Now, since a technical point of view, those -common artwork components are made of software improved constantly. -So, we need to find a way to keep one unique name and one unique -visual style in artwork components that have internal difference and -also remark internal difference as well. -

-
Important

Important

Remarking the CentOS release schema inside each -major release of CentOS distribution --or similar visual -manifestation-- takes high attention inside The CentOS Project -corporate visual identity. It should be very clear for people which -major release of CentOS distribution they are using. -

- -

In order to remark the CentOS release schema, the CentOS Artwork SIG -uses a release-specific brand design named "The CentOS Release -Brand". The CentOS release brand is compossed by the CentOS logotype -and the CentOS major release number (as specified in CentOS -release schema definition). In this solution, the CentOS release brand -is set inside all release-specific artworks (e.g., distribution, -installation media, etc.) in remarkable way. The CentOS release -brand is the design component that lets us remark the CentOS release -schema inside the monolithic corporate visual identity structure we -propose to use. +

In this location themes are organized in "Models" --to store common +information-- and "Motifs"--to store unique information. At +rendering time, both motifs and models are combined to produce the +final CentOS themes. CentOS themes can be tagged as "Default" or +"Alternative". CentOS themes are maintained by CentOS community.

-

3.14.2.2 One theme for each major release

- -

Other way we've been using to remark CentOS release schema is -applying one unique theme for each major release of CentOS -distribution. That is, if we have 4 major releases of CentOS -distribution, we need to provide 4 different themes to cover each -CentOS distribution available. -

-

Inside CentOS Artwork Repository, you can create many themes and that -is very convenient. But using one unique theme for each major -release of CentOS distribution would bring visual isolation among -distributions, websites and promotion visual manifestations. If the -CentOS project would maintain just one CentOS distribution (and many -experienced graphic designers ready to create beautiful artworks) this -model would be nice. Indeed, this model looks quite similar to that -one used by Fedora project, doesn't it. But no, the CentOS project -maintains near to 4 major releases of CentOS distribution in parallel, -and that fact makes a huge difference since the corporate visual -identity point of view. -

-

If we use one unique theme for each major release of CentOS -distribution, which one of those themes, does we use to cover other -CentOS visual manifestations, like websites and promotion stuff? -

-

In whatever case you choose some release-specific distribution user -will be visually isolated from other CentOS visual manifestations like -websites and promotion stuff, even if the CentOS brand is present in -all visual manifestations. In such a case, probably, users will end up -asking themselves, why my CentOS distribution has this design and the -CentOS website another one? Isn't them on the same project? With luck -the CentOS brand will exonerate user form visual isolation. -

- - -

3.14.3 Usage

- - -

3.14.4 See also

+ + + + +
3.22 trunk/Identity/Themes/Motifs   +
3.15 trunk/Identity/Themes/Models   +
3.59 trunk/Translations/Identity/Themes   +
- - + + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_18.html b/Manuals/en/Html/Repository/repository_18.html index f53a91c..1947c8d 100644 --- a/Manuals/en/Html/Repository/repository_18.html +++ b/Manuals/en/Html/Repository/repository_18.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.15 trunk/Identity/Themes/Models/Default/Distro/Anaconda +CentOS Artwork Repository: 3.15 trunk/Identity/Themes/Models - - + + @@ -56,58 +56,72 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.15 trunk/Identity/Themes/Models/Default/Distro/Anaconda

+ + +

3.15 trunk/Identity/Themes/Models

- +

3.15.1 Goals

- +

3.15.2 Description

+

Theme models let you modeling characteristics (e.g., dimensions, +translation markers, position of each element on the display area, +etc.) common to all themes. Theme models let you reduce the time +needed when propagating artistic motifs to different visual +manifestations. +

+

Theme models serves as a central pool of design templates for themes +to use. This way you can produce themes with different artistic motifs +but same characteristics. +

- +

3.15.3 Usage

+

Inside the framework location above, you find theme models organized +by name. You can add your own theme models to the structure by adding +a directory to the list. By default you have the `See section Default,' and `See section Alternative,' ready-to-use theme models. +

- +

3.15.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_19.html b/Manuals/en/Html/Repository/repository_19.html index 778bf95..2a48013 100644 --- a/Manuals/en/Html/Repository/repository_19.html +++ b/Manuals/en/Html/Repository/repository_19.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.16 trunk/Identity/Themes/Models/Default/Promo +CentOS Artwork Repository: 3.16 trunk/Identity/Themes/Models/Alternative - - + + @@ -56,27 +56,27 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.16 trunk/Identity/Themes/Models/Default/Promo

+ + +

3.16 trunk/Identity/Themes/Models/Alternative

- +

3.16.1 Goals

- +

3.16.2 Description

-

It applies to all tangible and non tangible items CentOS uses to -promote its existence. Clothes, posters, installation media, -stationery, release countdown images, banners, stickers, are all -examples of promotion designs. +

CentOS alternative theme models exist for people how want to use a +different visual style on their installations of CentOS distribution. +As the visual style is needed for a system already installed +components like Anaconda are not required inside alternative themes. +Inside alternative themes you find post-installation visual style only +(i.e. Backgrounds, Display Managers, Grub, etc.). CentOS alternative +themes are maintained by CentOS Community.

- - - +

3.16.3 Usage

- +

3.16.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_2.html b/Manuals/en/Html/Repository/repository_2.html index 3df2fe9..23b0346 100644 --- a/Manuals/en/Html/Repository/repository_2.html +++ b/Manuals/en/Html/Repository/repository_2.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + - + -CentOS Artwork Repository: 3.17 trunk/Identity/Themes/Models/Default/Web +CentOS Artwork Repository: 3.17 trunk/Identity/Themes/Models/Default - - + + @@ -56,70 +56,71 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.17 trunk/Identity/Themes/Models/Default/Web

+ + +

3.17 trunk/Identity/Themes/Models/Default

- +

3.17.1 Goals

- - +

This location stores CentOS default theme model. The CentOS default +theme model is used in all visual manifestations of CentOS Project's +corporate visual identity (e.g., distributions, web sites, promotion, +etc.). +

- +

3.17.2 Description

-

It applies to all web applications CentOS uses to handle its needs -(Ex. Portals, Wikis, Forums, Blogs, Bug Tracker). Anything involving -HTML standards should be consider here. -

- - - +

3.17.3 Usage

- - +

Changing CentOS default theme is not very convenient because that +affects the "recognition" of CentOS Project. Nevertheless, we are +interested on seeing your art work propositions. Specially if your +art work is an improvement to the base idea behind CentOS default +theme (Modern, squares and circles flowing up.). +

+

If you are not happy with CentOS default theme, you can look inside +CentOS alternative themes and download the one you are interested in. +If you are not happy with any of the CentOS alternative themes +available, then go and design your own CentOS alternative theme as +described in See section Theme Motifs. +

- +

3.17.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_21.html b/Manuals/en/Html/Repository/repository_21.html index cba3bec..9e56df3 100644 --- a/Manuals/en/Html/Repository/repository_21.html +++ b/Manuals/en/Html/Repository/repository_21.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.18 trunk/Identity/Themes/Motifs +CentOS Artwork Repository: 3.18 trunk/Identity/Themes/Models/Default/Distro - - + + @@ -56,137 +56,113 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.18 trunk/Identity/Themes/Motifs

+ + +

3.18 trunk/Identity/Themes/Models/Default/Distro

- +

3.18.1 Goals

-

The `trunk/Identity/Themes/Motifs' directory exists to: -

- - +

3.18.2 Description

-

The artistic motif of theme is a graphic design component that -provides theme's visual style, it is used as pattern to connect all -visual manifestations inside one unique theme. +

It applies to all major releases of CentOS distribution.

-

Artistic motifs are based on conceptual ideas. Conceptual ideas bring -the motivation, they are fuel for the engines of human imagination. -Good conceptual ideas may produce good motivation to produce almost -anything, and art works don't escape from it. + + +

3.18.2.1 One theme for all major releases

+ +

Sometimes, specific visual manifestations are formed by common +components which have internal differences. That is the case of CentOS +distribution visual manifestation.

-
-
`TreeFlower'
-

CentOS like trees, has roots, trunk, branches, leaves and flowers. Day -by day they work together in freedom, ruled by the laws of nature and -open standards, to show the beauty of its existence. -

-
`Modern'
-

Modern, squares and circles flowing up. -

-
- -

If you have new conceptual ideas for CentOS, then you can say that you -want to create a new artistic motif for CentOS. To create a new -artistic motif you need to create a directory under -`Identity/Themes/Motifs/' using a name coherent with your -conceptual idea. That name will be your artistic motif's name. If -possible, when creating new conceptual ideas for CentOS, think about -what CentOS means for you, what does it makes you feel, take your -time, think deep, and share; you can improve the idea as time goes on. +

Since a visual style point of view, the CentOS distributions share +common artwork components like Anaconda --to cover the CentOS +distribution installation--, BootUp --to cover the CentOS +distribution start up--, and Backgrounds --to cover the CentOS +distribution desktop--. Now, since a technical point of view, those +common artwork components are made of software improved constantly. +So, we need to find a way to keep one unique name and one unique +visual style in artwork components that have internal difference and +also remark internal difference as well.

-

Once you have defined a name for your theme, you need to create the -motif structure of your theme. The motif structure is the basic -direcotry structure you'll use to work your ideas. Here is where you -organize your graphic design projects. +

Important

Important

Remarking the CentOS release schema inside each +major release of CentOS distribution --or similar visual +manifestation-- takes high attention inside The CentOS Project +corporate visual identity. It should be very clear for people which +major release of CentOS distribution they are using. +

+ +

In order to remark the CentOS release schema, the CentOS Artwork SIG +uses a release-specific brand design named "The CentOS Release +Brand". The CentOS release brand is compossed by the CentOS logotype +and the CentOS major release number (as specified in CentOS +release schema definition). In this solution, the CentOS release brand +is set inside all release-specific artworks (e.g., distribution, +installation media, etc.) in remarkable way. The CentOS release +brand is the design component that lets us remark the CentOS release +schema inside the monolithic corporate visual identity structure we +propose to use.

-

To add a new motif structure to CentOS Artwork Repository, you need to -use the centos-art command line in the -`Identity/Themes/Motifs/' directory as described below: + + +

3.18.2.2 One theme for each major release

+ +

Other way we've been using to remark CentOS release schema is +applying one unique theme for each major release of CentOS +distribution. That is, if we have 4 major releases of CentOS +distribution, we need to provide 4 different themes to cover each +CentOS distribution available.

-
 
centos-art add --motif=ThemeName
-
-

The previous command will create the motif's basic structure for you. -The basic structure produced by centos-art command is -illustrated in the following figure: +

Inside CentOS Artwork Repository, you can create many themes and that +is very convenient. But using one unique theme for each major +release of CentOS distribution would bring visual isolation among +distributions, websites and promotion visual manifestations. If the +CentOS project would maintain just one CentOS distribution (and many +experienced graphic designers ready to create beautiful artworks) this +model would be nice. Indeed, this model looks quite similar to that +one used by Fedora project, doesn't it. But no, the CentOS project +maintains near to 4 major releases of CentOS distribution in parallel, +and that fact makes a huge difference since the corporate visual +identity point of view. +

+

If we use one unique theme for each major release of CentOS +distribution, which one of those themes, does we use to cover other +CentOS visual manifestations, like websites and promotion stuff? +

+

In whatever case you choose some release-specific distribution user +will be visually isolated from other CentOS visual manifestations like +websites and promotion stuff, even if the CentOS brand is present in +all visual manifestations. In such a case, probably, users will end up +asking themselves, why my CentOS distribution has this design and the +CentOS website another one? Isn't them on the same project? With luck +the CentOS brand will exonerate user form visual isolation.

-
 
trunk/Identity/Themes/Motifs/$ThemeName/
-|-- Backgrounds
-|   |-- Img
-|   `-- Tpl
-|-- Info
-|   |-- Img
-|   `-- Tpl
-|-- Palettes
-`-- Screenshots
-

3.18.3 Usage

-

When designing artistic motifs for CentOS, consider the following -recommendations: -

- -

3.18.4 See also

@@ -198,12 +174,12 @@ works are released under [ > ]   [ << ] -[ Up ] -[ >> ] +[ Up ] +[ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_22.html b/Manuals/en/Html/Repository/repository_22.html index 273f99b..9da2ec8 100644 --- a/Manuals/en/Html/Repository/repository_22.html +++ b/Manuals/en/Html/Repository/repository_22.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.19 trunk/Identity/Themes/Motifs/Modern/Backgrounds +CentOS Artwork Repository: 3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda - - + + @@ -61,156 +61,40 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.19 trunk/Identity/Themes/Motifs/Modern/Backgrounds

+

3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda

3.19.1 Goals

3.19.2 Description

-

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

-

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

-
 
xcf/800x600.xcf
-
-

to produce the background image: -

-
 
img/800x600-bg.png
-
-

which is loaded in: -

-
 
svg/800x600.svg
-
-

to produce the final background image: -

-
 
img/800x600.png         
-
-

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

-

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

-
 
xcf/800x600-anaconda.xcf
-
-

to produce the background image: -

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

which is loaded in: -

-
 
svg/800x600-anaconda.svg
-
-

to produce the file: -

-
 
img/800x600-anaconda.png
-
-

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

-

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

-

Background images are linked (using Inkscape's import feature) -inside almost all theme art works. This structure let you make -centralized changes on the visual identity and propagate them quickly -to other areas. -

-

In this structure you design background images for different screen -resolutions based on theme's artistic motif. -

-

You may create different artistic motifs propositions based -on the same conceptual idea. The conceptual idea is what defines a -theme. Artistic motifs are interpretations of that idea. -

-

Inside this directory artistic motifs are organized by name (e.g., -TreeFlower, Modern, etc.). -

-

Inside each motif directories represent just one unique artistic motif. -

-

The artistic motif is graphic design used as common pattern to connect -all visual manifestations inside one unique theme. The artistic motif -is based on a conceptual idea. Artistic motifs provide visual style -to themes. -

-

Designing artistic motifs is for anyone interested in creating -beautiful themes for CentOS. When building a theme for CentOS, the -first design you need to define is the artistic motif. -

- -

Inside CentOS Artwork Repository, theme visual styles (Motifs) and -theme visual structures (Models) are two different working lines. -When you design an artistic motif for CentOS you concentrate on its -visual style, and eventualy, use the centos-art command line -interface to render the visual style, you are currently producing, -against an already-made theme model in order to produce the final -result. Final images are stored under the motif's name directory -using the model directory structure as reference. -

-

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

3.19.3 Usage

-

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

3.19.4 See also

- - - - - -
3.20 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img   -
3.21 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl   -
3.22 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf   -
3.56 trunk/Translations/Identity/Themes/Backgrounds   -
- @@ -219,11 +103,11 @@ can contain subdirectories to help you organize the design process. - +
  [ << ] [ Up ][ >> ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_23.html b/Manuals/en/Html/Repository/repository_23.html index 9223f12..496f12b 100644 --- a/Manuals/en/Html/Repository/repository_23.html +++ b/Manuals/en/Html/Repository/repository_23.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.20 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img +CentOS Artwork Repository: 3.20 trunk/Identity/Themes/Models/Default/Promo - - + + @@ -61,19 +61,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

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

+

3.20 trunk/Identity/Themes/Models/Default/Promo

@@ -87,32 +87,40 @@ ul.toc {list-style: none}

3.20.2 Description

+

It applies to all tangible and non tangible items CentOS uses to +promote its existence. Clothes, posters, installation media, +stationery, release countdown images, banners, stickers, are all +examples of promotion designs. +

+ +

3.20.3 Usage

-

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

+ +

3.20.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_24.html b/Manuals/en/Html/Repository/repository_24.html index 3f38e54..6e3d23e 100644 --- a/Manuals/en/Html/Repository/repository_24.html +++ b/Manuals/en/Html/Repository/repository_24.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.21 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl +CentOS Artwork Repository: 3.21 trunk/Identity/Themes/Models/Default/Web - - + + @@ -61,19 +61,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

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

+

3.21 trunk/Identity/Themes/Models/Default/Web

@@ -87,14 +87,22 @@ ul.toc {list-style: none}

3.21.2 Description

+

It applies to all web applications CentOS uses to handle its needs +(Ex. Portals, Wikis, Forums, Blogs, Bug Tracker). Anything involving +HTML standards should be consider here. +

+ +

3.21.3 Usage

-

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

+ +

3.21.4 See also

@@ -107,11 +115,11 @@ command line interface.   [ << ] [ Up ] -[ >> ] +[ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_25.html b/Manuals/en/Html/Repository/repository_25.html index 9a32aaa..1c97a6b 100644 --- a/Manuals/en/Html/Repository/repository_25.html +++ b/Manuals/en/Html/Repository/repository_25.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.22 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf +CentOS Artwork Repository: 3.22 trunk/Identity/Themes/Motifs - - + + @@ -61,49 +61,132 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

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

+

3.22 trunk/Identity/Themes/Motifs

3.22.1 Goals

+

The `trunk/Identity/Themes/Motifs' directory exists to: +

+

3.22.2 Description

- - - +

The artistic motif of theme is a graphic design component that +provides theme's visual style, it is used as pattern to connect all +visual manifestations inside one unique theme. +

+

Artistic motifs are based on conceptual ideas. Conceptual ideas bring +the motivation, they are fuel for the engines of human imagination. +Good conceptual ideas may produce good motivation to produce almost +anything, and art works don't escape from it. +

+
+
`TreeFlower'
+

CentOS like trees, has roots, trunk, branches, leaves and flowers. Day +by day they work together in freedom, ruled by the laws of nature and +open standards, to show the beauty of its existence. +

+
`Modern'
+

Modern, squares and circles flowing up. +

+
+ +

If you have new conceptual ideas for CentOS, then you can say that you +want to create a new artistic motif for CentOS. To create a new +artistic motif you need to create a directory under +`Identity/Themes/Motifs/' using a name coherent with your +conceptual idea. That name will be your artistic motif's name. If +possible, when creating new conceptual ideas for CentOS, think about +what CentOS means for you, what does it makes you feel, take your +time, think deep, and share; you can improve the idea as time goes on. +

+

Once you have defined a name for your theme, you need to create the +motif structure of your theme. The motif structure is the basic +direcotry structure you'll use to work your ideas. Here is where you +organize your graphic design projects. +

+

To add a new motif structure to CentOS Artwork Repository, you need to +use the centos-art command line in the +`Identity/Themes/Motifs/' directory as described below: +

+
 
centos-art add --motif=ThemeName
+
+

The previous command will create the motif's basic structure for you. +The basic structure produced by centos-art command is +illustrated in the following figure: +

+
 
trunk/Identity/Themes/Motifs/$ThemeName/
+|-- Backgrounds
+|   |-- Img
+|   `-- Tpl
+|-- Info
+|   |-- Img
+|   `-- Tpl
+|-- Palettes
+`-- Screenshots
+

3.22.3 Usage

-

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

When designing artistic motifs for CentOS, consider the following +recommendations:

+ +

3.22.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_26.html b/Manuals/en/Html/Repository/repository_26.html index c7e8ae0..8c0763a 100644 --- a/Manuals/en/Html/Repository/repository_26.html +++ b/Manuals/en/Html/Repository/repository_26.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.23 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress +CentOS Artwork Repository: 3.23 trunk/Identity/Themes/Motifs/Modern/Backgrounds - - + + @@ -61,80 +61,155 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

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

+

3.23 trunk/Identity/Themes/Motifs/Modern/Backgrounds

3.23.1 Goals

3.23.2 Description

+

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

+

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

+
 
xcf/800x600.xcf
+
+

to produce the background image: +

+
 
img/800x600-bg.png
+
+

which is loaded in: +

+
 
svg/800x600.svg
+
+

to produce the final background image: +

+
 
img/800x600.png         
+
+

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

+

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

+
 
xcf/800x600-anaconda.xcf
+
+

to produce the background image: +

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

which is loaded in: +

+
 
svg/800x600-anaconda.svg
+
+

to produce the file: +

+
 
img/800x600-anaconda.png
+
+

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

+

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

+

Background images are linked (using Inkscape's import feature) +inside almost all theme art works. This structure let you make +centralized changes on the visual identity and propagate them quickly +to other areas. +

+

In this structure you design background images for different screen +resolutions based on theme's artistic motif. +

+

You may create different artistic motifs propositions based +on the same conceptual idea. The conceptual idea is what defines a +theme. Artistic motifs are interpretations of that idea. +

+

Inside this directory artistic motifs are organized by name (e.g., +TreeFlower, Modern, etc.). +

+

Inside each motif directories represent just one unique artistic motif. +

+

The artistic motif is graphic design used as common pattern to connect +all visual manifestations inside one unique theme. The artistic motif +is based on a conceptual idea. Artistic motifs provide visual style +to themes. +

+

Designing artistic motifs is for anyone interested in creating +beautiful themes for CentOS. When building a theme for CentOS, the +first design you need to define is the artistic motif. +

+ +

Inside CentOS Artwork Repository, theme visual styles (Motifs) and +theme visual structures (Models) are two different working lines. +When you design an artistic motif for CentOS you concentrate on its +visual style, and eventualy, use the centos-art command line +interface to render the visual style, you are currently producing, +against an already-made theme model in order to produce the final +result. Final images are stored under the motif's name directory +using the model directory structure as reference. +

+

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

3.23.3 Usage

-

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

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

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

The above command will create the following structure: -

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

3.23.4 See also

+ + + + + +
3.24 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img   +
3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl   +
3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf   +
3.60 trunk/Translations/Identity/Themes/Backgrounds   +
@@ -144,11 +219,11 @@ centos-art render --identity   [ << ] [ Up ] -[ >> ] +[ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_27.html b/Manuals/en/Html/Repository/repository_27.html index f1044fa..becc0e2 100644 --- a/Manuals/en/Html/Repository/repository_27.html +++ b/Manuals/en/Html/Repository/repository_27.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.24 trunk/Identity/Themes/Motifs/Modern/Palettes +CentOS Artwork Repository: 3.24 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img - - + + @@ -61,26 +61,26 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.24 trunk/Identity/Themes/Motifs/Modern/Palettes

+

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

3.24.1 Goals

@@ -91,10 +91,9 @@ ul.toc {list-style: none}

3.24.3 Usage

-

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

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

@@ -102,17 +101,18 @@ limitations. Theme palettes contain theme's unique color information. + - +
[ < ] [ > ]   [ << ] [ Up ][ >> ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_28.html b/Manuals/en/Html/Repository/repository_28.html index a7203ea..4baa3ae 100644 --- a/Manuals/en/Html/Repository/repository_28.html +++ b/Manuals/en/Html/Repository/repository_28.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.25 trunk/Identity/Themes/Motifs/TreeFlower +CentOS Artwork Repository: 3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl - - + + @@ -61,19 +61,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.25 trunk/Identity/Themes/Motifs/TreeFlower

+

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

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

3.25.3 Usage

+

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

3.25.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_29.html b/Manuals/en/Html/Repository/repository_29.html index 558362e..e033bcd 100644 --- a/Manuals/en/Html/Repository/repository_29.html +++ b/Manuals/en/Html/Repository/repository_29.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.26 trunk/Identity/Widgets +CentOS Artwork Repository: 3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf - - + + @@ -61,19 +61,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.26 trunk/Identity/Widgets

+

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

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

3.26.2 Description

+ + +

3.26.3 Usage

+

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

3.26.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_3.html b/Manuals/en/Html/Repository/repository_3.html index c57de2e..605039a 100644 --- a/Manuals/en/Html/Repository/repository_3.html +++ b/Manuals/en/Html/Repository/repository_3.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + - + -CentOS Artwork Repository: 3.27 trunk/Manuals +CentOS Artwork Repository: 3.27 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress - - + + @@ -61,19 +61,19 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.27 trunk/Manuals

+

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

@@ -87,60 +87,49 @@ ul.toc {list-style: none}

3.27.2 Description

- -

3.27.3 Usage

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

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

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

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

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

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

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

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

Use this command to edit file documentation as specified in -`path/to/dir/filename' combination. +
 
cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/
+centos-art render --identity
+
+

The above command will create the following structure:

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

Use this command to update documentation output files. -

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

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

-
Caution

Caution

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

- -
Info

Tip

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

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

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

-
+
 
trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
+|-- 3
+|   |-- en
+|   |   |-- 01-welcome.png
+|   |   |-- 02-donate.png
+|   |   `-- 03-yum.png
+|   `-- es
+|       |-- 01-welcome.png
+|       |-- 02-donate.png
+|       `-- 03-yum.png
+|-- 4
+|   |-- en
+|   |   |-- 01-welcome.png
+|   |   |-- 02-donate.png
+|   |   `-- 03-yum.png
+|   `-- es
+|       |-- 01-welcome.png
+|       |-- 02-donate.png
+|       `-- 03-yum.png
+`-- 5
+    |-- en
+    |   |-- 01-welcome.png
+    |   |-- 02-donate.png
+    |   `-- 03-yum.png
+    `-- es
+        |-- 01-welcome.png
+        |-- 02-donate.png
+        `-- 03-yum.png
+
@@ -148,17 +137,18 @@ repository): + - +
[ < ] [ > ]   [ << ] [ Up ][ >> ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_31.html b/Manuals/en/Html/Repository/repository_31.html index aa4539c..4c90f4f 100644 --- a/Manuals/en/Html/Repository/repository_31.html +++ b/Manuals/en/Html/Repository/repository_31.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.28 trunk/Scripts +CentOS Artwork Repository: 3.28 trunk/Identity/Themes/Motifs/Modern/Palettes - - + + @@ -61,47 +61,41 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.28 trunk/Scripts

+

3.28 trunk/Identity/Themes/Motifs/Modern/Palettes

3.28.1 Goals

-

The `trunk/Scripts' directory exists to: -

3.28.2 Description

- -

3.28.3 Usage

- - +

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

3.28.4 See also

@@ -114,11 +108,11 @@ programming language.   [ << ] [ Up ] -[ >> ] +[ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_32.html b/Manuals/en/Html/Repository/repository_32.html index 6dc5ee8..d1de1c0 100644 --- a/Manuals/en/Html/Repository/repository_32.html +++ b/Manuals/en/Html/Repository/repository_32.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.29 trunk/Scripts/Bash +CentOS Artwork Repository: 3.29 trunk/Identity/Themes/Motifs/TreeFlower - - + + @@ -61,232 +61,53 @@ ul.toc {list-style: none}   [ << ] [ Up ] -[ >> ] +[ >> ]         [Top] [Contents] -[Index] +[Index] [ ? ] - + -

3.29 trunk/Scripts/Bash

+

3.29 trunk/Identity/Themes/Motifs/TreeFlower

3.29.1 Goals

-

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

+ +

3.29.2 Description

-

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

-

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

-

When centos-art.sh script is executed, the first it does is -execute the `trunk/Scripts/Bash/initFunctions.sh' file to -initialize gettext variables and all function scripts inside -`trunk/Scripts/Bash/Functions' directory. -

-

Once gettext variables and all function scripts have been -initialized, the centos-art.sh script initializes its -environment variables using the cli_getVariables function. -At this point the centos-art.sh script calls the -cli_getActions function from cli_getVariables -function's bottom. -

-

The cli_getActions function defines which actions the -centos-art.sh script is able to perform. Inside -cli_getActions function, actions are defined combining -positional arguments and function calls. -

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

Figure 3.5: The centos-art.sh initialization environment. - -

-

3.29.2.1 The identity matching list

- -

The identity matching list is used by identity rendering functions to -define the relation between translation files and identity design -templates. See section trunk/Scripts/Bash/Functions/Config/cli_getIdentityMatchinglist.sh, for more information. -

- - -

3.29.2.2 Adding new features

- -

To add new features inside centos-art.sh script, you need to -set positional arguments and function calls inside -cli_getActions function for the new function or functions -required by the new feature you want to add. -

- -

3.29.3 Usage

- -

3.29.3.1 The centos-art `check' action

- -

This feature is supported through the following command: -

-
-
`centos-art check'
-

This command verifies paths, symbolic links, installed packages and -everything your workstation needs in order to run the -centos-art command correctly. -

-
Warning

Warning

If this is the first time you run -centos-art command, the appropriate way to execute check -action is not using the centos-art command, but the absolute -path to centos-art.sh script instead: -

~/artwork/trunk/Scripts/Bash/centos-art.sh check
-
-
-
- - - -

3.29.3.2 The centos-art `search' action

- -

This feature is not supported yet. -

-
-
`centos-art search 'pattern''
-
-

Use this command to find directories and files that match exactly the -posix-regular expression set in `pattern' as in `^pattern$'. -

-
-
`centos-art search 'pattern1 pattern2 patternN''
-
-

Use this command to search repository entries that match pattern1 -or patter2 or patternN as in -`'^.*(pattern1|pattern2|patternN).*$''. -

-
-
`centos-art search 'path/to/dir1 path/to/dir2 path/to/dirN''
-
-

Use this command to search repository entries that match -`path/to/dir1' or `path/to/dir2', or -`path/to/dirN' as in -`^.*(path/to/dir1|path/to/dir2|path/to/dirN).*$''. -

-
-
- - - -

3.29.3.3 The centos-art `path' action

- -

This feature is not supported yet. -

-
-
`centos-art path 'path/to/dir/' --copy-to='path/to/dir''
-
`centos-art path 'path/to/dir/' --copy-to='path/to/dir/filename''
-
`centos-art path 'path/to/dir/' --move-to='path/to/dir''
-
`centos-art path 'path/to/dir/' --move-to='path/to/dir/filename''
-
`centos-art path 'path/to/dir/' --remove'
-
- - - -

3.29.3.4 The centos-art `locale-art' action

- -

This feature is not supported yet. -

-
-
`centos-art locale-art 'path/to/dir' --edit'
-
`centos-art locale-art 'path/to/dir' --edit='filename''
-
`centos-art locale-art 'path/to/dir' --list'
-
`centos-art locale-art 'path/to/dir' --list='filename''
-
- - - -

3.29.3.5 The centos-art `license' action

- -

This feature is supported through the following command: -

-
-
`centos-art license'
-

Use this command to see a brief description of centos-art -command its copyright and its license notes. -

-
- - - +

3.29.4 See also

- - - - - -
3.30 trunk/Scripts/Bash/Config   -
3.33 trunk/Scripts/Bash/Functions   -
3.45 trunk/Scripts/Bash/Locale   -
3.28 trunk/Scripts   -
- - + + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_33.html b/Manuals/en/Html/Repository/repository_33.html index 565b0da..41f5ec2 100644 --- a/Manuals/en/Html/Repository/repository_33.html +++ b/Manuals/en/Html/Repository/repository_33.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.30 trunk/Scripts/Bash/Config +CentOS Artwork Repository: 3.30 trunk/Identity/Widgets - - + + @@ -56,173 +56,58 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.30 trunk/Scripts/Bash/Config

+ + +

3.30 trunk/Identity/Widgets

- +

3.30.1 Goals

-

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

- - -

3.30.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 loadConfiguration 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.30.2.1 The `render.conf.sh' identity model

+ -

Inside CentOS Artwork Repository, we consider directories under -`trunk/Identity' as identity entries. 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 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. The first entry inside `ACTIONS' array variable (i.e., -`ACTIONS[0]') is reserved to define the primary rendering action -(i.e, `renderImage' or `renderText'). Further entries -inside `ACTIONS' (i.e., `ACTIONS[1]', `ACTIONS[2]', -etc.) are used to define identity post-rendering actions. -

-

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

-
#!/bin/bash
-
-function loadConfiguration {
-
-    # Define post-rendering actions. An empty value means that no
-    # post-rendering action is applied.
-    ACTIONS[0]='renderImage'
-    ACTIONS[1]='renderFormats: tif xpm pdf ppm'
-
-}
-
-

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

-
#!/bin/bash
 
-function loadConfiguration {
-
-    # Define post-rendering actions. An empty value means that no
-    # post-rendering action is applied.
-    ACTIONS[0]='renderText'
-    ACTIONS[1]='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.30.2.2 The `render.conf.sh' translation model

+ +

3.30.2 Description

-

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.30.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.30.4 See also

- - - - -
3.31 trunk/Scripts/Bash/Config/Identity   -
3.32 trunk/Scripts/Bash/Config/Translations   -
3.29 trunk/Scripts/Bash   -
- - + + - - + +
[ < ][ > ]
[ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_34.html b/Manuals/en/Html/Repository/repository_34.html index 517aa0f..0c33eb2 100644 --- a/Manuals/en/Html/Repository/repository_34.html +++ b/Manuals/en/Html/Repository/repository_34.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.31 trunk/Scripts/Bash/Config/Identity +CentOS Artwork Repository: 3.31 trunk/Manuals - - + + @@ -56,27 +56,27 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.31 trunk/Scripts/Bash/Config/Identity

+ + +

3.31 trunk/Manuals

- +

3.31.1 Goals

- +

3.31.2 Description

- +

3.31.3 Usage

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

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

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

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

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

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

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

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

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

Use this command to update documentation output files. +

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

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

+
Caution

Caution

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

+ +
Info

Tip

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

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

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

+
+ + +

3.31.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_35.html b/Manuals/en/Html/Repository/repository_35.html index 0ed6cc1..73c93e3 100644 --- a/Manuals/en/Html/Repository/repository_35.html +++ b/Manuals/en/Html/Repository/repository_35.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.32 trunk/Scripts/Bash/Config/Translations +CentOS Artwork Repository: 3.32 trunk/Scripts - - + + @@ -56,35 +56,38 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.32 trunk/Scripts/Bash/Config/Translations

+ + +

3.32 trunk/Scripts

- +

3.32.1 Goals

+

The `trunk/Scripts' directory exists to: +

- +

3.32.2 Description

- +

3.32.3 Usage

- +

3.32.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_36.html b/Manuals/en/Html/Repository/repository_36.html index 7fee797..b5927d7 100644 --- a/Manuals/en/Html/Repository/repository_36.html +++ b/Manuals/en/Html/Repository/repository_36.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.33 trunk/Scripts/Bash/Functions +CentOS Artwork Repository: 3.33 trunk/Scripts/Bash - - + + @@ -56,66 +56,235 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.33 trunk/Scripts/Bash/Functions

+ + +

3.33 trunk/Scripts/Bash

- +

3.33.1 Goals

- - +

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

- +

3.33.2 Description

- +

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

+

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

+

When centos-art.sh script is executed, the first it does is +execute the `trunk/Scripts/Bash/initFunctions.sh' file to +initialize gettext variables and all function scripts inside +`trunk/Scripts/Bash/Functions' directory. +

+

Once gettext variables and all function scripts have been +initialized, the centos-art.sh script initializes its +environment variables using the cli_getVariables function. +At this point the centos-art.sh script calls the +cli_getActions function from cli_getVariables +function's bottom. +

+

The cli_getActions function defines which actions the +centos-art.sh script is able to perform. Inside +cli_getActions function, actions are defined combining +positional arguments and function calls. +

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

Figure 3.5: The centos-art.sh initialization environment. + +

+ +

3.33.2.1 The identity matching list

- +

The identity matching list is used by identity rendering functions to +define the relation between translation files and identity design +templates. +

+ + +

3.33.2.2 Adding new features

+ +

To add new features inside centos-art.sh script, you need to +set positional arguments and function calls inside +cli_getActions function for the new function or functions +required by the new feature you want to add. +

+ +

3.33.3 Usage

- + +

3.33.3.1 The centos-art `check' action

+ +

This feature is supported through the following command: +

+
+
`centos-art check'
+

This command verifies paths, symbolic links, installed packages and +everything your workstation needs in order to run the +centos-art command correctly. +

+
Warning

Warning

If this is the first time you run +centos-art command, the appropriate way to execute check +action is not using the centos-art command, but the absolute +path to centos-art.sh script instead: +

~/artwork/trunk/Scripts/Bash/centos-art.sh check
+
+
+
+ + + +

3.33.3.2 The centos-art `search' action

- +

This feature is not supported yet. +

+
+
`centos-art search 'pattern''
+
+

Use this command to find directories and files that match exactly the +posix-regular expression set in `pattern' as in `^pattern$'. +

+
+
`centos-art search 'pattern1 pattern2 patternN''
+
+

Use this command to search repository entries that match pattern1 +or patter2 or patternN as in +`'^.*(pattern1|pattern2|patternN).*$''. +

+
+
`centos-art search 'path/to/dir1 path/to/dir2 path/to/dirN''
+
+

Use this command to search repository entries that match +`path/to/dir1' or `path/to/dir2', or +`path/to/dirN' as in +`^.*(path/to/dir1|path/to/dir2|path/to/dirN).*$''. +

+
+
+ + + +

3.33.3.3 The centos-art `path' action

+ +

This feature is not supported yet. +

+
+
`centos-art path 'path/to/dir/' --copy-to='path/to/dir''
+
`centos-art path 'path/to/dir/' --copy-to='path/to/dir/filename''
+
`centos-art path 'path/to/dir/' --move-to='path/to/dir''
+
`centos-art path 'path/to/dir/' --move-to='path/to/dir/filename''
+
`centos-art path 'path/to/dir/' --remove'
+
+ + + +

3.33.3.4 The centos-art `locale-art' action

+ +

This feature is not supported yet. +

+
+
`centos-art locale-art 'path/to/dir' --edit'
+
`centos-art locale-art 'path/to/dir' --edit='filename''
+
`centos-art locale-art 'path/to/dir' --list'
+
`centos-art locale-art 'path/to/dir' --list='filename''
+
+ + + +

3.33.3.5 The centos-art `license' action

+ +

This feature is supported through the following command: +

+
+
`centos-art license'
+

Use this command to see a brief description of centos-art +command its copyright and its license notes. +

+
+ + +

3.33.4 See also

+ + + + +
3.36 trunk/Scripts/Bash/Functions   +
3.49 trunk/Scripts/Bash/Locale   +
3.32 trunk/Scripts   +
- - + + - - + +
[ < ][ > ]
[ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_37.html b/Manuals/en/Html/Repository/repository_37.html index da066fb..de64e47 100644 --- a/Manuals/en/Html/Repository/repository_37.html +++ b/Manuals/en/Html/Repository/repository_37.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.34 trunk/Scripts/Bash/Functions/Config +CentOS Artwork Repository: 3.34 trunk/Scripts/Bash/Config/Identity - - + + @@ -56,42 +56,66 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- + + +

3.34 trunk/Scripts/Bash/Config/Identity

+ + + +

3.34.1 Goals

+ + + + -

3.34 trunk/Scripts/Bash/Functions/Config

+

3.34.2 Description

+ + -
Redirection

Redirection

-The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/Config, instead. -

+ + +

3.34.3 Usage

+ + + + + +

3.34.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_38.html b/Manuals/en/Html/Repository/repository_38.html index 4011508..e4b544f 100644 --- a/Manuals/en/Html/Repository/repository_38.html +++ b/Manuals/en/Html/Repository/repository_38.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.35 trunk/Scripts/Bash/Functions/Config/cli_getActionsIdentity.sh +CentOS Artwork Repository: 3.35 trunk/Scripts/Bash/Config/Translations - - + + @@ -56,41 +56,66 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.35 trunk/Scripts/Bash/Functions/Config/cli_getActionsIdentity.sh

+ + +

3.35 trunk/Scripts/Bash/Config/Translations

+ + + +

3.35.1 Goals

+ + + + + +

3.35.2 Description

+ + + + + +

3.35.3 Usage

+ + + + + +

3.35.4 See also

-
Redirection

Redirection

-The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh, instead. -

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_39.html b/Manuals/en/Html/Repository/repository_39.html index 3c961a3..c3041aa 100644 --- a/Manuals/en/Html/Repository/repository_39.html +++ b/Manuals/en/Html/Repository/repository_39.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.36 trunk/Scripts/Bash/Functions/Config/cli_getActions.sh +CentOS Artwork Repository: 3.36 trunk/Scripts/Bash/Functions - - + + @@ -56,41 +56,70 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.36 trunk/Scripts/Bash/Functions/Config/cli_getActions.sh

+ + +

3.36 trunk/Scripts/Bash/Functions

-
Redirection

Redirection

-The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/render_getActions.sh, instead. -

+ + +

3.36.1 Goals

+ + + + + +

3.36.2 Description

+ + + + + +

3.36.3 Usage

+ + + + + +

3.36.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_4.html b/Manuals/en/Html/Repository/repository_4.html index c8bf6ab..d566aa6 100644 --- a/Manuals/en/Html/Repository/repository_4.html +++ b/Manuals/en/Html/Repository/repository_4.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + - + -CentOS Artwork Repository: 3.37 trunk/Scripts/Bash/Functions/Config/cli_getActionsTranslations.sh +CentOS Artwork Repository: 3.37 trunk/Scripts/Bash/Functions/Config - - + + @@ -56,41 +56,42 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.37 trunk/Scripts/Bash/Functions/Config/cli_getActionsTranslations.sh

+ + +

3.37 trunk/Scripts/Bash/Functions/Config

Redirection

Redirection

-The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh, instead. +The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/Config, instead.

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_41.html b/Manuals/en/Html/Repository/repository_41.html index 93ac366..ba27488 100644 --- a/Manuals/en/Html/Repository/repository_41.html +++ b/Manuals/en/Html/Repository/repository_41.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.38 trunk/Scripts/Bash/Functions/Config/cli_getIdentityMatchinglist.sh +CentOS Artwork Repository: 3.38 trunk/Scripts/Bash/Functions/Config/cli_getActionsIdentity.sh - - + + @@ -56,44 +56,41 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.38 trunk/Scripts/Bash/Functions/Config/cli_getIdentityMatchinglist.sh

+ + +

3.38 trunk/Scripts/Bash/Functions/Config/cli_getActionsIdentity.sh

-
Removed

Removed

-The content of this page was removed. Use the following command to -search what you need: -

-
centos-art help --search --filter='your search pattern'
-
+
Redirection

Redirection

+The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh, instead. +

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_42.html b/Manuals/en/Html/Repository/repository_42.html index f079be9..07dfd9a 100644 --- a/Manuals/en/Html/Repository/repository_42.html +++ b/Manuals/en/Html/Repository/repository_42.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.39 trunk/Scripts/Bash/Functions/Config/repo_renderIdentitySyslinux.sh +CentOS Artwork Repository: 3.39 trunk/Scripts/Bash/Functions/Config/cli_getActions.sh - - + + @@ -56,66 +56,41 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.39 trunk/Scripts/Bash/Functions/Config/repo_renderIdentitySyslinux.sh

- - - -

3.39.1 Goals

- - - - - -

3.39.2 Description

- - - - - -

3.39.3 Usage

- - - - - -

3.39.4 See also

+ + +

3.39 trunk/Scripts/Bash/Functions/Config/cli_getActions.sh

+
Redirection

Redirection

+The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/render_getActions.sh, instead. +

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_43.html b/Manuals/en/Html/Repository/repository_43.html index da6b6fd..82363a4 100644 --- a/Manuals/en/Html/Repository/repository_43.html +++ b/Manuals/en/Html/Repository/repository_43.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.40 trunk/Scripts/Bash/Functions/Prepare/prepare_forUsingPackages.sh +CentOS Artwork Repository: 3.40 trunk/Scripts/Bash/Functions/Config/cli_getActionsTranslations.sh - - + + @@ -56,66 +56,41 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

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

- - - -

3.40.1 Goals

- - - - - -

3.40.2 Description

- - - - - -

3.40.3 Usage

- - - - - -

3.40.4 See also

+ + +

3.40 trunk/Scripts/Bash/Functions/Config/cli_getActionsTranslations.sh

+
Redirection

Redirection

+The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh, instead. +

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_44.html b/Manuals/en/Html/Repository/repository_44.html index 5d3721a..a53a08c 100644 --- a/Manuals/en/Html/Repository/repository_44.html +++ b/Manuals/en/Html/Repository/repository_44.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.41 trunk/Scripts/Bash/Functions/Render/Config +CentOS Artwork Repository: 3.41 trunk/Scripts/Bash/Functions/Config/cli_getIdentityMatchinglist.sh - - + + @@ -56,66 +56,44 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

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

- - - -

3.41.1 Goals

- - - - + -

3.41.2 Description

- - - - - -

3.41.3 Usage

- - - - - -

3.41.4 See also

+

3.41 trunk/Scripts/Bash/Functions/Config/cli_getIdentityMatchinglist.sh

+
Removed

Removed

+The content of this page was removed. Use the following command to +search what you need: +

+
centos-art help --search --filter='your search pattern'
+
- - + + - - + +
[ < ][ > ]
[ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_45.html b/Manuals/en/Html/Repository/repository_45.html index d6983e7..f2aa94c 100644 --- a/Manuals/en/Html/Repository/repository_45.html +++ b/Manuals/en/Html/Repository/repository_45.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.42 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh +CentOS Artwork Repository: 3.42 trunk/Scripts/Bash/Functions/Config/repo_renderIdentitySyslinux.sh - - + + @@ -56,27 +56,27 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

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

+ + +

3.42 trunk/Scripts/Bash/Functions/Config/repo_renderIdentitySyslinux.sh

- +

3.42.1 Goals

- +

3.42.2 Description

- +

3.42.3 Usage

- +

3.42.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_46.html b/Manuals/en/Html/Repository/repository_46.html index 47114cc..e827ece 100644 --- a/Manuals/en/Html/Repository/repository_46.html +++ b/Manuals/en/Html/Repository/repository_46.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.43 trunk/Scripts/Bash/Functions/Render/render_getActions.sh +CentOS Artwork Repository: 3.43 trunk/Scripts/Bash/Functions/Prepare/prepare_forUsingPackages.sh - - + + @@ -56,27 +56,27 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

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

+ + +

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

- +

3.43.1 Goals

- +

3.43.2 Description

- +

3.43.3 Usage

- +

3.43.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_47.html b/Manuals/en/Html/Repository/repository_47.html index b8c5879..0284b95 100644 --- a/Manuals/en/Html/Repository/repository_47.html +++ b/Manuals/en/Html/Repository/repository_47.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.44 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh +CentOS Artwork Repository: 3.44 trunk/Scripts/Bash/Functions/Render - - + + @@ -56,27 +56,27 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

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

+ + +

3.44 trunk/Scripts/Bash/Functions/Render

- +

3.44.1 Goals

- +

3.44.2 Description

- +

3.44.3 Usage

- +

3.44.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_48.html b/Manuals/en/Html/Repository/repository_48.html index ed384c2..58fedfa 100644 --- a/Manuals/en/Html/Repository/repository_48.html +++ b/Manuals/en/Html/Repository/repository_48.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.45 trunk/Scripts/Bash/Locale +CentOS Artwork Repository: 3.45 trunk/Scripts/Bash/Functions/Render/Config - - + + @@ -56,143 +56,237 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- + + +

3.45 trunk/Scripts/Bash/Functions/Render/Config

+ + + +

3.45.1 Goals

+ +

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

+ -

3.45 trunk/Scripts/Bash/Locale

+

3.45.2 Description

+

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

+

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

-

3.45.1 Goals

+

3.45.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.45.2 Description

+

3.45.2.2 The `render.conf.sh' translation model

-

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

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.45.2.1 Configuration files

+

3.45.2.3 The `render.conf.sh' rendering actions

-

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

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

- - -

3.45.3.1 The centos-art `locale-cli' action

- +

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

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

+
`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.45.4 See also

- - -
3.30 trunk/Scripts/Bash/Config   +
3.34 trunk/Scripts/Bash/Config/Identity  
3.33 trunk/Scripts/Bash/Functions   +
3.35 trunk/Scripts/Bash/Config/Translations  
3.28 trunk/Scripts   +
3.33 trunk/Scripts/Bash  
- - + + - - + +
[ < ][ > ]
[ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_49.html b/Manuals/en/Html/Repository/repository_49.html index 87ef2be..b8e0bce 100644 --- a/Manuals/en/Html/Repository/repository_49.html +++ b/Manuals/en/Html/Repository/repository_49.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.46 trunk/Scripts/Perl +CentOS Artwork Repository: 3.46 trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh - - + + @@ -56,27 +56,27 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.46 trunk/Scripts/Perl

+ + +

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

- +

3.46.1 Goals

- +

3.46.2 Description

+ + - +

3.46.3 Usage

+ + - +

3.46.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_5.html b/Manuals/en/Html/Repository/repository_5.html index 3de9fe7..b548b18 100644 --- a/Manuals/en/Html/Repository/repository_5.html +++ b/Manuals/en/Html/Repository/repository_5.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + - + -CentOS Artwork Repository: 3.47 trunk/Scripts/Python +CentOS Artwork Repository: 3.47 trunk/Scripts/Bash/Functions/Render/render_getActions.sh - - + + @@ -56,27 +56,27 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.47 trunk/Scripts/Python

+ + +

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

- +

3.47.1 Goals

- +

3.47.2 Description

- +

3.47.3 Usage

- +

3.47.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_51.html b/Manuals/en/Html/Repository/repository_51.html index e667f8a..640c5ab 100644 --- a/Manuals/en/Html/Repository/repository_51.html +++ b/Manuals/en/Html/Repository/repository_51.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.48 trunk/Translations +CentOS Artwork Repository: 3.48 trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh - - + + @@ -56,678 +56,66 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.48 trunk/Translations

+ + +

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

- +

3.48.1 Goals

-

The `trunk/Translations' directory exists to: -

- +

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

-

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.48.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.48.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.48.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 --translation=/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.48.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: Translations.texi 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: Translations.texi 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: Translations.texi 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: Translations.texi 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.48.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.48.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.48.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.48.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
-#
-# loadConfiguration.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: Translations.texi 94 2010-09-18 10:59:42Z al $
-# ----------------------------------------------------------------------
-
-function loadConfiguration {
-...
-}
-
-

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.48.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.48.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.48.4 See also

- - - - - - - -
3.50 trunk/Translations/Identity/Brands   -
3.52 trunk/Translations/Identity/Fonts   -
3.53 trunk/Translations/Identity/Models   -
3.54 trunk/Translations/Identity/Release   -
3.55 trunk/Translations/Identity/Themes   -
3.1 trunk/Identity   -
- - + + - - + +
[ < ][ > ]
[ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_52.html b/Manuals/en/Html/Repository/repository_52.html index 400705c..7e643ee 100644 --- a/Manuals/en/Html/Repository/repository_52.html +++ b/Manuals/en/Html/Repository/repository_52.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.49 trunk/Translations/Identity +CentOS Artwork Repository: 3.49 trunk/Scripts/Bash/Locale - - + + @@ -56,82 +56,141 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.49 trunk/Translations/Identity

+ + +

3.49 trunk/Scripts/Bash/Locale

- +

3.49.1 Goals

- +

3.49.2 Description

+

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

+

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

+

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

+

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

+

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

+

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

+

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

+

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

+ + +

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

- +

3.49.3 Usage

- + + +

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.4 See also

- - - - - - -
3.50 trunk/Translations/Identity/Brands   -
3.52 trunk/Translations/Identity/Fonts   -
3.53 trunk/Translations/Identity/Models   -
3.54 trunk/Translations/Identity/Release   -
3.55 trunk/Translations/Identity/Themes   -
3.58 trunk/Translations/Identity/Widgets   +
3.36 trunk/Scripts/Bash/Functions  
3.1 trunk/Identity   +
3.32 trunk/Scripts  
- - + + - - + +
[ < ][ > ]
[ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_53.html b/Manuals/en/Html/Repository/repository_53.html index 01f74c9..5902c2f 100644 --- a/Manuals/en/Html/Repository/repository_53.html +++ b/Manuals/en/Html/Repository/repository_53.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.50 trunk/Translations/Identity/Brands +CentOS Artwork Repository: 3.50 trunk/Scripts/Perl - - + + @@ -56,152 +56,58 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.50 trunk/Translations/Identity/Brands

+ + +

3.50 trunk/Scripts/Perl

- +

3.50.1 Goals

- +

3.50.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.50.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.50.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.50.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.50.3 Usage

-

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

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

3.50.4 See also

- - - -
3.51 trunk/Translations/Identity/Brands/Tpl   -
3.2 trunk/Identity/Brands   -
- - + + - - + +
[ < ][ > ]
[ < ][ > ]   [ << ][ Up ][ >> ][ Up ][ >> ]

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_54.html b/Manuals/en/Html/Repository/repository_54.html index 5e2d0bb..f8b9ccf 100644 --- a/Manuals/en/Html/Repository/repository_54.html +++ b/Manuals/en/Html/Repository/repository_54.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.51 trunk/Translations/Identity/Brands/Tpl +CentOS Artwork Repository: 3.51 trunk/Scripts/Python - - + + @@ -56,54 +56,66 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.51 trunk/Translations/Identity/Brands/Tpl

+ + +

3.51 trunk/Scripts/Python

- +

3.51.1 Goals

+ - + +

3.51.2 Description

+ + - +

3.51.3 Usage

+ + - +

3.51.4 See also

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

- This document was generated on October, 3 2010 using texi2html 1.76. + This document was generated on October, 12 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_55.html b/Manuals/en/Html/Repository/repository_55.html index 5ae9db6..450ee99 100644 --- a/Manuals/en/Html/Repository/repository_55.html +++ b/Manuals/en/Html/Repository/repository_55.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + -CentOS Artwork Repository: 3.52 trunk/Translations/Identity/Fonts +CentOS Artwork Repository: 3.52 trunk/Translations - - + + @@ -56,115 +56,678 @@ ul.toc {list-style: none} - - + + - + - +
[ < ][ > ]
[ < ][ > ]   [ << ] [ Up ][ >> ][ >> ]         [Top] [Contents][Index][Index] [ ? ]
- - -

3.52 trunk/Translations/Identity/Fonts

+ + +

3.52 trunk/Translations

- +

3.52.1 Goals

+

The `trunk/Translations' directory exists to: +

- +

3.52.2 Description

-

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

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

+ + +

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

-
# ----------------------------------------------------------------------
-# $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!
+
+
 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
 

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

-
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.
+
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.1 Translation Markers 

+
+
 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
 
-
Inside `trunk/Translations/Identity/Fonts', translation files
-combine the following 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:
 

 

-
 `font-family:Denmark'

-
Specify which font family to use when rendering font preview images.
+
 `=MINOR_RELEASE='

+
Replace with minor release of CentOS distribution. In the schema M.N, the minor
+release is represented by the N letter.
 

-
 `font-weight:normal'

-
Specify which font weight to use when rendering font preview images.
+
 `=MAJOR_RELEASE='

+
Replace with major release of CentOS distribution. In the schema M.N,
+the major release is represented by the M letter.
 

-
 `font-style:normal'

-
Specify which font style to use when rendering font preview images.
+
 `=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 

 
-
-
 3.52.3 Usage 

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

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

-
vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed
+
centos-art render --translation=/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: Translations.texi 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: Translations.texi 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: Translations.texi 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: Translations.texi 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
+#
+# loadConfiguration.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: Translations.texi 94 2010-09-18 10:59:42Z al $
+# ----------------------------------------------------------------------
+
+function loadConfiguration {
+...
+}
+

+
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 

 
 
-
+
+
+
+
+
3.3 trunk/Identity/Fonts  
+
3.54 trunk/Translations/Identity/Brands  
+
3.56 trunk/Translations/Identity/Fonts  
+
3.57 trunk/Translations/Identity/Models  
+
3.58 trunk/Translations/Identity/Release  
+
3.59 trunk/Translations/Identity/Themes  
+
3.1 trunk/Identity  
 

 

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

 

  
-  This document was generated on October, 3 2010 using texi2html 1.76.
+  This document was generated on October, 12 2010 using texi2html 1.76.
  
  

 
diff --git a/Manuals/en/Html/Repository/repository_56.html b/Manuals/en/Html/Repository/repository_56.html
index ab56759..4310c65 100644
--- a/Manuals/en/Html/Repository/repository_56.html
+++ b/Manuals/en/Html/Repository/repository_56.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
 copy of the license is included in the section entitled GNU Free
 Documentation License.  
 -->
-
+
 
 
-CentOS Artwork Repository: 3.53 trunk/Translations/Identity/Models
+CentOS Artwork Repository: 3.53 trunk/Translations/Identity
 
-
-
+
+
 
 
 
@@ -56,54 +56,82 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
[ < ][ > ]
[ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 

-
-
-
 3.53 trunk/Translations/Identity/Models 

+
+
+
 3.53 trunk/Translations/Identity 

 
 
-
+
 
 3.53.1 Goals 

 
+
    
+
  •  ...
+

 
-
+
+
 
 3.53.2 Description 

 
+
    
+
  •  ...
+

+
 
-
+
 
 3.53.3 Usage 

 
+
    
+
  •  ...
+

+
 
-
+
 
 3.53.4 See also 

 
+
+
+
+
+
+
+
+
+
3.54 trunk/Translations/Identity/Brands  
+
3.56 trunk/Translations/Identity/Fonts  
+
3.57 trunk/Translations/Identity/Models  
+
3.58 trunk/Translations/Identity/Release  
+
3.59 trunk/Translations/Identity/Themes  
+
3.62 trunk/Translations/Identity/Widgets  
+
3.1 trunk/Identity  
+

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

 

  
-  This document was generated on October, 3 2010 using texi2html 1.76.
+  This document was generated on October, 12 2010 using texi2html 1.76.
  
  

 
diff --git a/Manuals/en/Html/Repository/repository_57.html b/Manuals/en/Html/Repository/repository_57.html
index 1e6eb4d..6fe2c20 100644
--- a/Manuals/en/Html/Repository/repository_57.html
+++ b/Manuals/en/Html/Repository/repository_57.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
 copy of the license is included in the section entitled GNU Free
 Documentation License.  
 -->
-
+
 
 
-CentOS Artwork Repository: 3.54 trunk/Translations/Identity/Release
+CentOS Artwork Repository: 3.54 trunk/Translations/Identity/Brands
 
-
-
+
+
 
 
 
@@ -56,41 +56,139 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
[ < ][ > ]
[ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 

-
-
-
 3.54 trunk/Translations/Identity/Release 

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

+
+
Convenctional file names look like `blue.sed', `2c-a.sed',
+etc.  Replacement commands inside translation file are applied to
+design templates and translation file names are used as final image
+name.  The image dimensions use the same dimensions that design
+template has.
+

+
+
+
 3.54.2.2 Numeric file names 

+
+
Numeric file names look like `300.sed', `200.sed', etc.
+Replacements commands inside translation files are applied to design
+templates, and translation file names are used as final image name.
+The final image is saved using an specific `width' defined by the
+number part of the translation file name. The image `height' is
+automatically scaled based on the previous `width' definition to
+maintain the design's ratio.  
+

+
For example, if your design template has 400x200 pixels of dimension,
+and you apply a translation file named `300.sed' to it, the final
+image you get as result will have 300x100 pixels of dimension.   The
+same is true if you use higher numbers like `1024.sed', `2048.sed',
+etc. In these cases you have bigger images proportionally.
+

+
As we are using scalable vector graphics to design identity templates,
+the image size you produce is not limitted in size. You can use one
+design template produced in 400x200 pixels to produce larger or
+shorter PNG images using numeric translation files as described
+above.
+

+
+
+
 3.54.2.3 Translation markers 

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

 
+
+
+
+
3.55 trunk/Translations/Identity/Brands/Tpl  
+
3.2 trunk/Identity/Brands  
+

 
 
 
@@ -98,12 +196,12 @@ ul.toc {list-style: none}
 
-
-
+
+
[ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
 

 

  
-  This document was generated on October, 3 2010 using texi2html 1.76.
+  This document was generated on October, 12 2010 using texi2html 1.76.
  
  

 
diff --git a/Manuals/en/Html/Repository/repository_58.html b/Manuals/en/Html/Repository/repository_58.html
index 4eec8f6..dc2c339 100644
--- a/Manuals/en/Html/Repository/repository_58.html
+++ b/Manuals/en/Html/Repository/repository_58.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
 copy of the license is included in the section entitled GNU Free
 Documentation License.  
 -->
-
+
 
 
-CentOS Artwork Repository: 3.55 trunk/Translations/Identity/Themes
+CentOS Artwork Repository: 3.55 trunk/Translations/Identity/Brands/Tpl
 
-
-
+
+
 
 
 
@@ -61,19 +61,19 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
    
    
    
    
 [Top]
 [Contents]
-[Index]
+[Index]
 [ ? ]
 
-
+
 
-
 3.55 trunk/Translations/Identity/Themes 

+
 3.55 trunk/Translations/Identity/Brands/Tpl 

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

  
-  This document was generated on October, 3 2010 using texi2html 1.76.
+  This document was generated on October, 12 2010 using texi2html 1.76.
  
  

 
diff --git a/Manuals/en/Html/Repository/repository_59.html b/Manuals/en/Html/Repository/repository_59.html
index d7265a8..5a2df45 100644
--- a/Manuals/en/Html/Repository/repository_59.html
+++ b/Manuals/en/Html/Repository/repository_59.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
 copy of the license is included in the section entitled GNU Free
 Documentation License.  
 -->
-
+
 
 
-CentOS Artwork Repository: 3.56 trunk/Translations/Identity/Themes/Backgrounds
+CentOS Artwork Repository: 3.56 trunk/Translations/Identity/Fonts
 
-
-
+
+
 
 
 
@@ -61,61 +61,110 @@ ul.toc {list-style: none}
    
 [ << ]
 [ Up ]
-[ >> ]
+[ >> ]
    
    
    
    
 [Top]
 [Contents]
-[Index]
+[Index]
 [ ? ]
 
-
+
 
-
 3.56 trunk/Translations/Identity/Themes/Backgrounds 

+
 3.56 trunk/Translations/Identity/Fonts 

 
 
 
 
 3.56.1 Goals 

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

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

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

+
+
Inside `trunk/Translations/Fonts' you use your favorite text
+editor to create translation files.  Inside
+`trunk/Translations/Fonts' there is not translation template
+directory (`Tpl/'), nor translation rendering using
+centos-art script.  For example, to create the
+`dejavu_lgc_sans-boldoblique.sed' translation file using
+vim editor, type the following command:
+

+
vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed
+

+
+
 
 3.56.4 See also 

 
+
+
+
3.3 trunk/Identity/Fonts  
+

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

 

  
-  This document was generated on October, 3 2010 using texi2html 1.76.
+  This document was generated on October, 12 2010 using texi2html 1.76.
  
  

 
diff --git a/Manuals/en/Html/Repository/repository_6.html b/Manuals/en/Html/Repository/repository_6.html
index e378ec7..59d7ab5 100644
--- a/Manuals/en/Html/Repository/repository_6.html
+++ b/Manuals/en/Html/Repository/repository_6.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
 copy of the license is included in the section entitled GNU Free
 Documentation License.  
 -->
-
+
 
-
+
 
 
-CentOS Artwork Repository: 3.57 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
+CentOS Artwork Repository: 3.57 trunk/Translations/Identity/Models
 
-
-
+
+
 
 
 
@@ -56,134 +56,54 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
[ < ][ > ]
[ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 

-
-
-
 3.57 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress 

+
+
+
 3.57 trunk/Translations/Identity/Models 

 
 
-
+
 
 3.57.1 Goals 

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

 
-
-
+
 
 3.57.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.57.3 Usage 

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

-
 
-
+
 
 3.57.4 See also 

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

 

  
-  This document was generated on October, 3 2010 using texi2html 1.76.
+  This document was generated on October, 12 2010 using texi2html 1.76.
  
  

 
diff --git a/Manuals/en/Html/Repository/repository_61.html b/Manuals/en/Html/Repository/repository_61.html
index c21601e..22907e3 100644
--- a/Manuals/en/Html/Repository/repository_61.html
+++ b/Manuals/en/Html/Repository/repository_61.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
 copy of the license is included in the section entitled GNU Free
 Documentation License.  
 -->
-
+
 
 
-CentOS Artwork Repository: 3.58 trunk/Translations/Identity/Widgets
+CentOS Artwork Repository: 3.58 trunk/Translations/Identity/Release
 
-
-
+
+
 
 
 
@@ -56,73 +56,54 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
+
-
+
[ < ][ > ]
[ < ][ > ]
    
 [ << ]
 [ Up ][ >> ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 

-
-
-
 3.58 trunk/Translations/Identity/Widgets 

-
-
+
 
-
 3.58.1 Goals 

-
-
    
-
  •  ...
-

+
 3.58 trunk/Translations/Identity/Release 

 
 
 
-
 3.58.2 Description 

-
-
    
-
  •  ...
-

+
 3.58.1 Goals 

 
 
 
-
 3.58.3 Usage 

-
-
    
-
  •  ...
-

+
 3.58.2 Description 

 
 
 
-
 3.58.4 See also 

-
-
-
-
3.58 trunk/Translations/Identity/Widgets  
-

+
 3.58.3 Usage 

 
 
+
+
 3.58.4 See also 

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

 

  
-  This document was generated on October, 3 2010 using texi2html 1.76.
+  This document was generated on October, 12 2010 using texi2html 1.76.
  
  

 
diff --git a/Manuals/en/Html/Repository/repository_62.html b/Manuals/en/Html/Repository/repository_62.html
index 5401fb7..054c2d9 100644
--- a/Manuals/en/Html/Repository/repository_62.html
+++ b/Manuals/en/Html/Repository/repository_62.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
 copy of the license is included in the section entitled GNU Free
 Documentation License.  
 -->
-
+
 
 
-CentOS Artwork Repository: Index
+CentOS Artwork Repository: 3.59 trunk/Translations/Identity/Themes
 
-
-
+
+
 
 
 
@@ -56,150 +56,54 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
-
+
+
-
+
[ < ][ > ]
[ < ][ > ]
    
 [ << ][ Up ][ >> ][ Up ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 

-
-
-
 Index 

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

-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Index Entry Section
 
B
branches1. branches
 
C
Common translation files3.48.2.5 Common Translation Files
 
H
How to render brands' translation files3.50.3 Usage
How to render fonts' translation files3.52.3 Usage
How to render translation files3.48.3 Usage
 
S
Specific translation files3.48.2.6 Specific Translation Files
 
T
tags2. tags
Template translation files3.48.2.4 Template Translation Files
Translation brands file names3.50.2.1 Conventional file names
Translation brands file names3.50.2.2 Numeric file names
Translation configuration scripts3.48.2.8 Translation (Pre-)Rendering Configuration Scripts
Translation entries3.48.2.1 Translation Entries
Translation files3.48.2.3 Translation Files
Translation markers3.48.2.2 Translation Markers
Translation paths3.48.2.1 Translation Entries
Translation pre-rendering configuration scripts3.48.2.8 Translation (Pre-)Rendering Configuration Scripts
Translation rendering3.48.2.7 Translation Rendering
Translation rendering default functionality3.48.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 Img Promo Web3.7 trunk/Identity/Models/Img/Promo/Web
trunk Identity Models Tpl Promo Web3.8 trunk/Identity/Models/Tpl/Promo/Web
trunk Identity Release3.9 trunk/Identity/Release
trunk Identity Themes3.10 trunk/Identity/Themes
trunk Identity Themes Models3.11 trunk/Identity/Themes/Models
trunk Identity Themes Models Alternative3.12 trunk/Identity/Themes/Models/Alternative
trunk Identity Themes Models Default3.13 trunk/Identity/Themes/Models/Default
trunk Identity Themes Models Default Distro3.14 trunk/Identity/Themes/Models/Default/Distro
trunk Identity Themes Models Default Distro Anaconda3.15 trunk/Identity/Themes/Models/Default/Distro/Anaconda
trunk Identity Themes Models Default Promo3.16 trunk/Identity/Themes/Models/Default/Promo
trunk Identity Themes Models Default Web3.17 trunk/Identity/Themes/Models/Default/Web
trunk Identity Themes Motifs3.18 trunk/Identity/Themes/Motifs
trunk Identity Themes Motifs Modern Backgrounds3.19 trunk/Identity/Themes/Motifs/Modern/Backgrounds
trunk Identity Themes Motifs Modern Backgrounds Img3.20 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img
trunk Identity Themes Motifs Modern Backgrounds Tpl3.21 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl
trunk Identity Themes Motifs Modern Backgrounds Xcf3.22 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf
trunk Identity Themes Motifs Modern Distro Anaconda Progress3.23 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
trunk Identity Themes Motifs Modern Palettes3.24 trunk/Identity/Themes/Motifs/Modern/Palettes
trunk Identity Themes Motifs TreeFlower3.25 trunk/Identity/Themes/Motifs/TreeFlower
trunk Identity Widgets3.26 trunk/Identity/Widgets
trunk Manuals3.27 trunk/Manuals
trunk Scripts3.28 trunk/Scripts
trunk Scripts Bash3.29 trunk/Scripts/Bash
trunk Scripts Bash Config3.30 trunk/Scripts/Bash/Config
trunk Scripts Bash Config Identity3.31 trunk/Scripts/Bash/Config/Identity
trunk Scripts Bash Config Translations3.32 trunk/Scripts/Bash/Config/Translations
trunk Scripts Bash Functions3.33 trunk/Scripts/Bash/Functions
trunk Scripts Bash Functions Config3.34 trunk/Scripts/Bash/Functions/Config
trunk Scripts Bash Functions Config cli_getActions.sh3.36 trunk/Scripts/Bash/Functions/Config/cli_getActions.sh
trunk Scripts Bash Functions Config cli_getActionsIdentity.sh3.35 trunk/Scripts/Bash/Functions/Config/cli_getActionsIdentity.sh
trunk Scripts Bash Functions Config cli_getActionsTranslations.sh3.37 trunk/Scripts/Bash/Functions/Config/cli_getActionsTranslations.sh
trunk Scripts Bash Functions Config cli_getIdentityMatchinglist.sh3.38 trunk/Scripts/Bash/Functions/Config/cli_getIdentityMatchinglist.sh
trunk Scripts Bash Functions Config repo_renderIdentitySyslinux.sh3.39 trunk/Scripts/Bash/Functions/Config/repo_renderIdentitySyslinux.sh
trunk Scripts Bash Functions Prepare prepare_forUsingPackages.sh3.40 trunk/Scripts/Bash/Functions/Prepare/prepare_forUsingPackages.sh
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 Locale3.45 trunk/Scripts/Bash/Locale
trunk Scripts Perl3.46 trunk/Scripts/Perl
trunk Scripts Python3.47 trunk/Scripts/Python
trunk Translations3.48 trunk/Translations
trunk Translations Identity3.49 trunk/Translations/Identity
trunk Translations Identity Brands3.50 trunk/Translations/Identity/Brands
trunk Translations Identity Brands Tpl3.51 trunk/Translations/Identity/Brands/Tpl
trunk Translations Identity Fonts3.52 trunk/Translations/Identity/Fonts
trunk Translations Identity Models3.53 trunk/Translations/Identity/Models
trunk Translations Identity Release3.54 trunk/Translations/Identity/Release
trunk Translations Identity Themes3.55 trunk/Translations/Identity/Themes
trunk Translations Identity Themes Backgrounds3.56 trunk/Translations/Identity/Themes/Backgrounds
trunk Translations Identity Themes Distro Anaconda Progress3.57 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
trunk Translations Identity Widgets3.58 trunk/Translations/Identity/Widgets
 

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

+
+
+
 3.59 trunk/Translations/Identity/Themes 

+
+
+
+
 3.59.1 Goals 

+
+
+
+
 3.59.2 Description 

+
+
+
+
 3.59.3 Usage 

+
+
+
+
 3.59.4 See also 

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

 

  
-  This document was generated on October, 3 2010 using texi2html 1.76.
+  This document was generated on October, 12 2010 using texi2html 1.76.
  
  

 
diff --git a/Manuals/en/Html/Repository/repository_63.html b/Manuals/en/Html/Repository/repository_63.html
index 89bf31a..c0b4c47 100644
--- a/Manuals/en/Html/Repository/repository_63.html
+++ b/Manuals/en/Html/Repository/repository_63.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
 copy of the license is included in the section entitled GNU Free
 Documentation License.  
 -->
-
+
 
 
-CentOS Artwork Repository: List of Figures
+CentOS Artwork Repository: 3.60 trunk/Translations/Identity/Themes/Backgrounds
 
-
-
+
+
 
 
 
@@ -56,51 +56,66 @@ ul.toc {list-style: none}
 
 
 
-
-
+
+
-
-
-
+
+
+
-
+
[ < ][ > ]
[ < ][ > ]
    [ << ][ Up ][ >> ][ << ][ Up ][ >> ]
    
    
    
    
 [Top]
 [Contents][Index][Index]
 [ ? ]
 

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

-

+
+
+
 3.60 trunk/Translations/Identity/Themes/Backgrounds 

+
+
+
+
 3.60.1 Goals 

+
+
    
+
  •  ...
+

+
+
+
+
 3.60.2 Description 

+
+
    
+
  •  ...
+

+
+
+
+
 3.60.3 Usage 

+
+
    
+
  •  ...
+

+
+
+
+
 3.60.4 See also 

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

 

  
-  This document was generated on October, 3 2010 using texi2html 1.76.
+  This document was generated on October, 12 2010 using texi2html 1.76.
  
  

 
diff --git a/Manuals/en/Html/Repository/repository_64.html b/Manuals/en/Html/Repository/repository_64.html
index 10a7d62..4a67924 100644
--- a/Manuals/en/Html/Repository/repository_64.html
+++ b/Manuals/en/Html/Repository/repository_64.html
@@ -3,7 +3,7 @@
 
-
+
 
 
-CentOS Artwork Repository: 3.15.3 Concepts
+CentOS Artwork Repository: 3.61 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
 
-
-
+
+