From 9c6e0de798ba2b07c80e2edff90ecaefdf572a39 Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: Mar 01 2011 17:07:30 +0000 Subject: Rename trunk/Manuals/Filesystem to trunk/Manuals/Repository. --- diff --git a/Manuals/Filesystem/branches/chapter-intro.texi b/Manuals/Filesystem/branches/chapter-intro.texi deleted file mode 100644 index e69de29..0000000 --- a/Manuals/Filesystem/branches/chapter-intro.texi +++ /dev/null diff --git a/Manuals/Filesystem/branches/chapter-menu.texi b/Manuals/Filesystem/branches/chapter-menu.texi deleted file mode 100644 index 8b13789..0000000 --- a/Manuals/Filesystem/branches/chapter-menu.texi +++ /dev/null @@ -1 +0,0 @@ - diff --git a/Manuals/Filesystem/branches/chapter-nodes.texi b/Manuals/Filesystem/branches/chapter-nodes.texi deleted file mode 100644 index 8b13789..0000000 --- a/Manuals/Filesystem/branches/chapter-nodes.texi +++ /dev/null @@ -1 +0,0 @@ - diff --git a/Manuals/Filesystem/branches/chapter.texi b/Manuals/Filesystem/branches/chapter.texi deleted file mode 100644 index e053279..0000000 --- a/Manuals/Filesystem/branches/chapter.texi +++ /dev/null @@ -1,6 +0,0 @@ -@node branches -@chapter branches -@cindex branches -@include branches/chapter-intro.texi -@include branches/chapter-menu.texi -@include branches/chapter-nodes.texi diff --git a/Manuals/Filesystem/filesystem-html/filesystem.html b/Manuals/Filesystem/filesystem-html/filesystem.html deleted file mode 100644 index 0a61430..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem.html +++ /dev/null @@ -1,105 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: CentOS Artwork Repository - File System - - - - - - - - - - - - - - - - - - - - - -
[Top][Contents][Index][ ? ]
-

CentOS Artwork Repository - File System

- -

Copyright © 2009-2011 Alain Reguera Delgado -

-

Permission is granted to copy, distribute and/or modify this document -under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no -Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A -copy of the license is included in the section entitled GNU Free -Documentation License. -

- - - - - - - -
1. branches   -
2. tags   -
3. trunk   -
Index   -
List of Figures   -
- - - - - - - - - - -
[Top][Contents][Index][ ? ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_1.html b/Manuals/Filesystem/filesystem-html/filesystem_1.html deleted file mode 100644 index dabf03b..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_1.html +++ /dev/null @@ -1,96 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 1. branches - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

1. branches

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_10.html b/Manuals/Filesystem/filesystem-html/filesystem_10.html deleted file mode 100644 index 7f1e92f..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_10.html +++ /dev/null @@ -1,119 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.7 trunk/Identity/Models/Css - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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

- - - - - -

3.7.3 Usage

- - - - - -

3.7.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_11.html b/Manuals/Filesystem/filesystem-html/filesystem_11.html deleted file mode 100644 index 5a1c1e9..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_11.html +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.8 trunk/Identity/Models/Html - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.8 trunk/Identity/Models/Html

- - - -

3.8.1 Goals

- - - - - -

3.8.2 Description

- - - - - -

3.8.3 Usage

- - - - - -

3.8.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_12.html b/Manuals/Filesystem/filesystem-html/filesystem_12.html deleted file mode 100644 index 8601e56..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_12.html +++ /dev/null @@ -1,124 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.9 trunk/Identity/Models/Img/Promo/Web - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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 ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_13.html b/Manuals/Filesystem/filesystem-html/filesystem_13.html deleted file mode 100644 index dccc572..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_13.html +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.10 trunk/Identity/Models/Tpl - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.10 trunk/Identity/Models/Tpl

- - - -

3.10.1 Goals

- - - - - -

3.10.2 Description

- - - - - -

3.10.3 Usage

- - - - - -

3.10.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_14.html b/Manuals/Filesystem/filesystem-html/filesystem_14.html deleted file mode 100644 index 224e014..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_14.html +++ /dev/null @@ -1,428 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.11 trunk/Identity/Models/Tpl/Promo/Web - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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 that used by MoinMoin. -

-

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

-

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

-

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

- - -

3.11.2.1 Design model (without ads)

- - - -

3.11.2.2 Design model (with ads)

- - - -

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

- - -

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 the diff command of Subversion 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

- - - - - -

3.11.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_15.html b/Manuals/Filesystem/filesystem-html/filesystem_15.html deleted file mode 100644 index 23e7f95..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_15.html +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.12 trunk/Identity/Models/Xcf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.12 trunk/Identity/Models/Xcf

- - - -

3.12.1 Goals

- - - - - -

3.12.2 Description

- - - - - -

3.12.3 Usage

- - - - - -

3.12.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_16.html b/Manuals/Filesystem/filesystem-html/filesystem_16.html deleted file mode 100644 index 1f74aac..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_16.html +++ /dev/null @@ -1,112 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.13 trunk/Identity/Release - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.13 trunk/Identity/Release

- - - -

3.13.1 Goals

- - - - - -

3.13.2 Description

- - - -

3.13.3 Usage

- - - -

3.13.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_17.html b/Manuals/Filesystem/filesystem-html/filesystem_17.html deleted file mode 100644 index 8dc944c..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_17.html +++ /dev/null @@ -1,130 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.14 trunk/Identity/Themes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.14 trunk/Identity/Themes

- - - -

3.14.1 Goals

- -

The `trunk/Identity/Themes/' directory exists to organize -production of CentOS themes. -

- - -

3.14.2 Description

- - - -

3.14.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.15 trunk/Identity/Themes/Models   -
3.22 trunk/Identity/Themes/Motifs   -
- - - -

3.14.4 See also

- - - - -
3.1 trunk/Identity   -
3. trunk   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_18.html b/Manuals/Filesystem/filesystem-html/filesystem_18.html deleted file mode 100644 index c7ac743..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_18.html +++ /dev/null @@ -1,126 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.15 trunk/Identity/Themes/Models - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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 ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_19.html b/Manuals/Filesystem/filesystem-html/filesystem_19.html deleted file mode 100644 index 456cc70..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_19.html +++ /dev/null @@ -1,124 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.16 trunk/Identity/Themes/Models/Alternative - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.16 trunk/Identity/Themes/Models/Alternative

- - - -

3.16.1 Goals

- - - - - -

3.16.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.16.3 Usage

- - - - - -

3.16.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_2.html b/Manuals/Filesystem/filesystem-html/filesystem_2.html deleted file mode 100644 index d24ef20..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_2.html +++ /dev/null @@ -1,96 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 2. tags - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

2. tags

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_20.html b/Manuals/Filesystem/filesystem-html/filesystem_20.html deleted file mode 100644 index fcb397b..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_20.html +++ /dev/null @@ -1,125 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.17 trunk/Identity/Themes/Models/Default - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.17 trunk/Identity/Themes/Models/Default

- - - -

3.17.1 Goals

- -

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

- - -

3.17.2 Description

- - - -

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 ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_21.html b/Manuals/Filesystem/filesystem-html/filesystem_21.html deleted file mode 100644 index 04deb2c..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_21.html +++ /dev/null @@ -1,184 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.18 trunk/Identity/Themes/Models/Default/Distro - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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

- - - -

3.18.1 Goals

- - - - - -

3.18.2 Description

- -

It applies to all major releases of CentOS distribution. -

- - -

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

-

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

- - -

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

-

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

- - - -

3.18.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_22.html b/Manuals/Filesystem/filesystem-html/filesystem_22.html deleted file mode 100644 index a3752c0..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_22.html +++ /dev/null @@ -1,112 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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

- - - -

3.19.1 Goals

- - - - - -

3.19.2 Description

- - - -

3.19.3 Usage

- - - -

3.19.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_23.html b/Manuals/Filesystem/filesystem-html/filesystem_23.html deleted file mode 100644 index 4ace555..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_23.html +++ /dev/null @@ -1,125 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.20 trunk/Identity/Themes/Models/Default/Promo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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

- - - -

3.20.1 Goals

- - - - - -

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

- - - - - -

3.20.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_24.html b/Manuals/Filesystem/filesystem-html/filesystem_24.html deleted file mode 100644 index 7fd1cf6..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_24.html +++ /dev/null @@ -1,124 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.21 trunk/Identity/Themes/Models/Default/Web - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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

- - - -

3.21.1 Goals

- - - - - -

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

- - - - - -

3.21.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_25.html b/Manuals/Filesystem/filesystem-html/filesystem_25.html deleted file mode 100644 index 92bb64d..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_25.html +++ /dev/null @@ -1,214 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.22 trunk/Identity/Themes/Motifs - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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 the visual style of themes, it is used as pattern to connect -all visual manifestations inside one unique theme. -

-

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

-
-
`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 the name of your artistic motif. If -possible, when creating new conceptual ideas for CentOS, think about -what CentOS means for you, what does it makes you feel, take your -time, think deep, and share; you can improve the idea as time goes on. -

-

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

-

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

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

The previous command will create the basic structure of themes 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

- -

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

- - - - -

3.22.4 See also

- - - - - -
3.14 trunk/Identity/Themes   -
3.1 trunk/Identity   -
3. trunk   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_26.html b/Manuals/Filesystem/filesystem-html/filesystem_26.html deleted file mode 100644 index fed8f16..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_26.html +++ /dev/null @@ -1,315 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.23 trunk/Identity/Themes/Motifs/Flame - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.23 trunk/Identity/Themes/Motifs/Flame

- - - -

3.23.1 Goals

- -

This section describes the steps we followed to construct the -Flame artistic motif. This section may be useful for anyone -interested in reproducing the Flame artistic motif, or in -creating new artistic motifs for The CentOS Project corporate visual -identity (see section trunk/Identity). -

- - -

3.23.2 Description

- -

The Flame artistic motif was built using the flame filter of -Gimp 2.2 in CentOS 5.5. -

-

The flame filter of Gimp can produce stunning, randomly generated -fractal patterns. The flame filter of Gimp gives us a great oportunity -to reduce the time used to produce new artistic motifs, because of its -"randomly generated" nature. Once the artistic motif be created, it -is propagated through all visual manifestations of CentOS Project -corporate visual identity using the `centos-art.sh' script -(see section trunk/Scripts/Bash) inside the CentOS Artwork Repository. -

-

To set the time intervals between each new visual style production, we -could reuse the CentOS distribution major release schema. I.e., we -could produce a new visual style, every two years, based on a new -"randomly generated" flame pattern, and publish the whole corporate -visual identity (i.e., distribution stuff, promotion stuff, websites -stuff, etc.) with the new major release of CentOS distribution all -together at once. -

-

Producing a new visual style is not one day's task. Once we have -defined the artistic motif, we need to propagate it through all visual -manifestations of The CentOS Project corporate visual identity. When -we say that we could produce one new visual style every two years we -really mean: to work two years long in order to propagate a new visual -style to all visual manifestations of The CentOS Project corporate -visual identity. -

-

Obviously, in order to propagate one visual style to all different -visual manifestations of The CentOS Project corporate visual identity, -we need first to know which the visual manifestations are. To define -which visual manifestations are inside The CentOS Project corporate -visual identity is one of the goals the CentOS Artwork Repository and -this documentation manual are both aimed to satisfy. -

-

Once we define which the visual manifestation are, it is possible to -define how to produce them, and this way, organize the automation -process. Such automation process is one of the goals of -`centos-art.sh' script. -

-

With the combination of both CentOS Artwork Repository and -`centos-art.sh' scripts we define work lines where translators, -programmers, and graphic designers work together to distribute and -reduce the amount of time employed to produce The CentOS Project -monolithic corporate identity. -

-

From a monolithic corporate visual identity point of view, notice that -we are producing a new visual style for the same theme (i.e., -Flame). It would be another flame design but still a flame -design. This idea is very important to be aware of, because we are -somehow "refreshing" the theme, not changing it at all. -

-

This way, as we are "refreshing" the theme, we still keep oursleves -inside the monolithic conception we are trying to be attached to -(i.e., one unique name, and one unique visual style for all visual -manifestations). -

-

Producing artistic motifs is a creative process that may consume long -time, specially for people without experienced knowledge on graphic -design land. Using "randomly generated" conception to produce -artistic motifs could be, practically, a way for anyone to follow in -order to produce maintainable artistic motifs in few steps. -

-

Due to the "randomly generated" nature of Flame filter, we find that -Flame pattern is not always the same when we use Flame -filter interface. -

-

Using the same pattern design for each visual manifestation is -essential in order to maintain the visual connection among all visual -manifestations inside the same theme. Occasionally, we may introduce -pattern variations in opacity, size, or even position but never change -the pattern design itself, nor the color information used by images -considered part of the same theme. -

-
Important

Important

-When we design background images, which are considered part of the -same theme, it is essential to use the same design pattern always. -This is what makes theme images to be visually connected among -themeselves, and so, the reason we use to define the word "theme" -as: a set of images visually connected among themeselves. -

- -

In order for us to reproduce the same flame pattern always, -Flame filter interface provides the `Save' and `Open' -options. The `Save' option brings up a file save dialog that -allows you to save the current Flame settings for the plug-in, so that -you can recreate them later. The `Open' option brings up a file -selector that allows you to open a previously saved Flame settings -file. -

-

The Flame settings we used in our example are saved in the file: -

-
trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def
-
- - -

3.23.3 Construction

- - - -

3.23.3.1 Step 1: Set image size

- -

Create an empty image and fill the `Background' layer with black -(000000) color. Image dimensions depend on the final -destination you plan to use the image for. For the sake of our -construction example we used an image of 640x480 pixels and 300 pixels -per inch (ppi). -

- - -

3.23.3.2 Step 2: Add base color and pattern information

- -

Create a new layer named `Base', place it over `Background' -layer and fill it with the base color (7800ff) you want to have -your background image set in. Add a mask to `Base' layer using -radial gradient and blur it. You may need to repeat this step more -than once in order to achieve a confortable black radial degradation -on the right side of your design. -

-

Duplicate `Base' layer and name it `Paper'. Place -`Paper' layer over `Base' layer. Remove content of -`Paper' layer and fill it with `Paper (100x100)' pattern. -Once you've done with black radial degradation, reduce the -`Paper' layer opacity to 20%. -

-

Notice that when we duplicate one layer, the mask information related -to layer is preserved from previous to next layer. This saves us some -of the time required to produce different layers with the same mask -information on them. -

-

Duplicate `Paper' layer and rename it `Stripes'. Remove -paper pattern from `Stripes' layer. Fill `Stripes' layer -with `Stripes (48x48)' pattern and reduce the `Stripes' -layer opacity to 15%. -

- - -

3.23.3.3 Step 3: Add flame motif

- -

Create a new layer named `Flame'. Set the foreground -(003cff) and background (0084ff) colors to the gradient -you want to build the flame motif. -

-

To build flame motif, use the flame filter (`Filters > Render > -Nature > Flame...') on `Flame' layer. We used a layer mask, with -a radial gradient on it to control the boundaries of flame motif on -`Flame' layer. -

-

Duplicate `Flame' layer and rename it `Flame Blur'. Place `Flame -Blur' below `Flame' layer. Apply Gussian blur filter -(`Filters > Blur > Gussian Blur...') until reaching the desiered -effect. -

-

The opacity value, in `Flame' layers, may vary from one image to -another based on the place the image will be finally placed on. For -example, images used as desktop background have the `Flame' layer -opacity set at 100% but `Flame Blur' is set to 70%. However, you -may find that background images used in anaconda progress slides have -opacity reduced differently, in order to reduce brightness in a way -that texts could look clean and readable over it. -

- - -

3.23.3.4 Step 4: Add foreground color

- -

Create a new layer named `Color', place it on top of all visible -layers and fill it with plain color (4c005a). Reduce -`Color' layer opacity to 20%. You can use the `Color' layer -to control the right side color information you want to produce the -image for. -

-

Duplicate `Flame' layer and create a new layer named -`Color#1'. Place `Color#1' layer on top of layer named -`Color'. Remove the mask information from `Color#1' layer -and recreate a new one using an inverted alpha channel as reference. -Remove `Color#1' layer content and fill it back with plain black -(000000) color. Reduce `Color#1' opacity to 20%. In this -step we created a mask to protect the flame artistic motif from black -color, so when we decrement or increment the opacity of layer, the -flame artistic motif wouldn't be affected, just the environment -suround it. -

-

When you set color information, remember that the same artistic motif -needs to be indexed to 14 and 16 colors, in order to produce Grub and -Syslinux visual manifestations respectively. Using many different -colors in the artistic motif may reduce the possibility of your design -to fix all different situations in. Likewise, using more colors in -one design, and less colors in another design will reduce the -connectivity among your designs, since color information is relevant -to visual identity. -

-

When you propagate your artistic motif visual style to different -visual manifestations of CentOS Project corporate visual identity, it -is up to you to find out justice and compromise among all possible -variables you may face. -

- - -

3.23.4 See also

- - - - - - -
3.22 trunk/Identity/Themes/Motifs   -
3.14 trunk/Identity/Themes   -
3.1 trunk/Identity   -
3. trunk   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_27.html b/Manuals/Filesystem/filesystem-html/filesystem_27.html deleted file mode 100644 index 73182d3..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_27.html +++ /dev/null @@ -1,112 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.24 trunk/Identity/Themes/Motifs/Modern - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.24 trunk/Identity/Themes/Motifs/Modern

- - - -

3.24.1 Presentation

- - - -

3.24.2 Construction

- - - -

3.24.3 Usage

- - - - - -

3.24.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_28.html b/Manuals/Filesystem/filesystem-html/filesystem_28.html deleted file mode 100644 index e143fa0..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_28.html +++ /dev/null @@ -1,229 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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

- - - -

3.25.1 Goals

- - - - - -

3.25.2 Description

- -

Inside `Motifs' directory, the `Backgrounds/' directory is -used to 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 the import feautre of -Inkscape. -

-

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 (e.g. Anaconda), 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 artistic -motif. -

-

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

-

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

-

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

-

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

-

Each artistic motif directory represents just one unique artistic -motif. -

-

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

-

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

- -

Inside CentOS Artwork Repository, theme visual styles (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 `Motifs/' directory using -the model name, and the model directory structure as reference. -

-

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

- - -

3.25.3 Usage

- -

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

- - -

3.25.4 See also

- - - - - -
3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img   -
3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl   -
3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf   -
- - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_29.html b/Manuals/Filesystem/filesystem-html/filesystem_29.html deleted file mode 100644 index 8aa6f9c..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_29.html +++ /dev/null @@ -1,117 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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

- - - -

3.26.1 Goals

- - - - - -

3.26.2 Description

- - - -

3.26.3 Usage

- -

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

- - -

3.26.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_3.html b/Manuals/Filesystem/filesystem-html/filesystem_3.html deleted file mode 100644 index d8922c3..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_3.html +++ /dev/null @@ -1,215 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3. trunk - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3. trunk

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
3.1 trunk/Identity   -
3.2 trunk/Identity/Brands   -
3.3 trunk/Identity/Fonts   -
3.4 trunk/Identity/Icons   -
3.5 trunk/Identity/Isolinux   -
3.6 trunk/Identity/Models   -
3.7 trunk/Identity/Models/Css   -
3.8 trunk/Identity/Models/Html   -
3.9 trunk/Identity/Models/Img/Promo/Web   -
3.10 trunk/Identity/Models/Tpl   -
3.11 trunk/Identity/Models/Tpl/Promo/Web   -
3.12 trunk/Identity/Models/Xcf   -
3.13 trunk/Identity/Release   -
3.14 trunk/Identity/Themes   -
3.15 trunk/Identity/Themes/Models   -
3.16 trunk/Identity/Themes/Models/Alternative   -
3.17 trunk/Identity/Themes/Models/Default   -
3.18 trunk/Identity/Themes/Models/Default/Distro   -
3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda   -
3.20 trunk/Identity/Themes/Models/Default/Promo   -
3.21 trunk/Identity/Themes/Models/Default/Web   -
3.22 trunk/Identity/Themes/Motifs   -
3.23 trunk/Identity/Themes/Motifs/Flame   -
3.24 trunk/Identity/Themes/Motifs/Modern   -
3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds   -
3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img   -
3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl   -
3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf   -
3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress   -
3.30 trunk/Identity/Themes/Motifs/Modern/Palettes   -
3.31 trunk/Identity/Themes/Motifs/TreeFlower   -
3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds   -
3.33 trunk/Identity/Widgets   -
3.34 trunk/Locales   -
3.35 trunk/Locales/Identity   -
3.36 trunk/Locales/Identity/Brands   -
3.37 trunk/Locales/Identity/Brands/Tpl   -
3.38 trunk/Locales/Identity/Fonts   -
3.39 trunk/Locales/Identity/Models   -
3.40 trunk/Locales/Identity/Release   -
3.41 trunk/Locales/Identity/Themes   -
3.42 trunk/Locales/Identity/Themes/Backgrounds   -
3.43 trunk/Locales/Identity/Themes/Distro/Anaconda/Progress   -
3.44 trunk/Locales/Identity/Widgets   -
3.45 trunk/Manuals   -
3.46 trunk/Scripts   -
3.47 trunk/Scripts/Bash   -
3.48 trunk/Scripts/Bash/Cli   -
3.49 trunk/Scripts/Bash/Cli/Functions   -
3.50 trunk/Scripts/Bash/Cli/Functions/Help   -
3.51 trunk/Scripts/Bash/Cli/Functions/Html   -
3.52 trunk/Scripts/Bash/Cli/Functions/Locale   -
3.53 trunk/Scripts/Bash/Cli/Functions/Manual   -
3.54 trunk/Scripts/Bash/Cli/Functions/Path   -
3.55 trunk/Scripts/Bash/Cli/Functions/Render   -
3.56 trunk/Scripts/Bash/Cli/Functions/Render/Config   -
3.57 trunk/Scripts/Bash/Cli/Functions/Shell   -
3.58 trunk/Scripts/Bash/Cli/Functions/Svg   -
3.59 trunk/Scripts/Bash/Cli/Functions/Verify   -
3.60 trunk/Scripts/Python   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_30.html b/Manuals/Filesystem/filesystem-html/filesystem_30.html deleted file mode 100644 index 7a62563..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_30.html +++ /dev/null @@ -1,116 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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

- - - -

3.27.1 Goals

- - - - - -

3.27.2 Description

- - - -

3.27.3 Usage

- -

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

- - -

3.27.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_31.html b/Manuals/Filesystem/filesystem-html/filesystem_31.html deleted file mode 100644 index 9635974..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_31.html +++ /dev/null @@ -1,125 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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

- - - -

3.28.1 Goals

- - - - - -

3.28.2 Description

- - - - - - -

3.28.3 Usage

- -

In this directory is where you store the project files (e.g, .xcf) of -Gimp. 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 background projects. Of course, you can -merge both Gimp and Inkscape power to produce images based on them. -In this last case you need the `Xcf/' directory. -

- - -

3.28.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_32.html b/Manuals/Filesystem/filesystem-html/filesystem_32.html deleted file mode 100644 index 87ff40b..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_32.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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

- - - -

3.29.1 Goals

- - - - - -

3.29.2 Description

- - - -

3.29.3 Usage

- -

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

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

The above command will create the following structure: -

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

3.29.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_33.html b/Manuals/Filesystem/filesystem-html/filesystem_33.html deleted file mode 100644 index 17e301e..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_33.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.30 trunk/Identity/Themes/Motifs/Modern/Palettes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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

- - - -

3.30.1 Goals

- - - - - -

3.30.2 Description

- - - -

3.30.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 the unique color information -required by theme. -

- - -

3.30.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_34.html b/Manuals/Filesystem/filesystem-html/filesystem_34.html deleted file mode 100644 index c0995a1..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_34.html +++ /dev/null @@ -1,112 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.31 trunk/Identity/Themes/Motifs/TreeFlower - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.31 trunk/Identity/Themes/Motifs/TreeFlower

- - - -

3.31.1 Goals

- - - - - -

3.31.2 Description

- - - -

3.31.3 Usage

- - - -

3.31.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_35.html b/Manuals/Filesystem/filesystem-html/filesystem_35.html deleted file mode 100644 index 84faa76..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_35.html +++ /dev/null @@ -1,424 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

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

- - - -

3.32.1 Goals

- -

This section exists to orgnize backgrounds of TreeFlower -artistic motif. -

- - -

3.32.2 Description

- - - -

3.32.2.1 Desktop background

- -

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

-

Open the png version with GIMP. -

-

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

-

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

-
-
Layer 1: Background
-
-

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

-
-
Layer 2: Shadow#1
-
-

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

-
-
Layer 3: Shadow#2
-
-

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

-
-
Layer 4: Pattern (Paper)
-
-

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

-
-
Layer 5: Pattern (Stripes)
-
-

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

-
-
Layer 6: Shadow#3
-
-

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

-
-
Layer 7: Shadow#4
-
-

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

-
-
Layer 8: Color#1
-
-

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

-
-
Layer 9: Color#2
-
-

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

-
-
- -
info

Note

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

- -

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

-

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

- - -

3.32.2.2 Anaconda Prompt (syslinux) background

- -

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

-

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

-

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

-
-
Layer 1: Background
-
-

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

-
-
Layer 2: Pattern (Paper)
-
-

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

-
-
Layer 3: Pattern (Stripes)
-
-

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

-
-
Layer 4: Shadow#1
-
-

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

-
-
Layer 5: Color#1
-
-

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

-
-
Layer 6: Color#2
-
-

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

-
-
Layer 7: Shadow#2
-
-

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

-
-
- -

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

-

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

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

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

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

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

-

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

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

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

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

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

-

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

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

to -

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

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

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

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

-

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

-

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

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

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

-

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

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

3.32.2.3 Grub background

- - - -

3.32.3 Usage

- - - - - -

3.32.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_36.html b/Manuals/Filesystem/filesystem-html/filesystem_36.html deleted file mode 100644 index 0f90440..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_36.html +++ /dev/null @@ -1,112 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.33 trunk/Identity/Widgets - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.33 trunk/Identity/Widgets

- - - -

3.33.1 Goals

- - - - - -

3.33.2 Description

- - - -

3.33.3 Usage

- - - -

3.33.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_37.html b/Manuals/Filesystem/filesystem-html/filesystem_37.html deleted file mode 100644 index 3297d47..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_37.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.34 trunk/Locales - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.34 trunk/Locales

- -

The `trunk/Locales' directory exists to store the translation -messages used to produce content in different languages. -

-

Translation messages are organized using the directory structure of -the component being translated. For example, if we want to provide -translation messages for `trunk/Manuals/Filesystem', then the -`trunk/Locales/Manuals/Filesystem' directory needs to be created. -

-

Once the locale directory exists for the component we want to provide -translation messages for, it is necessary to create the translation -files where translation messages are. The translation files follows -the concepts of xml2po and GNU gettext tools. -

-

The basic translation process is as follow: first, translatable -strings are extracted from files and a portable object template (.pot) -is created or updated with the information. Using the portable object -template, a portable object (.po) is created or updated for translator -to locale the messages retrived. Finally, a machine object (.mo) is -created from portable object to sotore the translated messages. -

-

Inside the repository there are two ways to retrive translatable -strings from files. The first one is through xml2po command -and the second through xgettext command. The xml2po -is used to retrive translatable strings from XML files (e.g., Scalable -Vector Graphics, DocBook, etc.) and the xgettext command is -used to retrive translatable strings from shell scripts files (e.g., -the files that make the centos-art.sh command-line -interface). -

-

When translatable strings are retrived from XML files, using the -xml2po command, there is no need to create the machine -object as we do when translatable strings ar retrived from shell -files, using the xgettext command. The xml2po -produces a temporal machine object in order to create a translated XML -file. Once the translated XML file has been created the machine object -is no longer needed. On the other hand, the machine object produced by -the xgettext command is required by the system in order for -the show shell script localized messages. -

-

Another difference between xml2po and xgettext we -need to be aware of is the directory structure used to store machine -objects. In xml2po, the machine object is created in the -current working directory as `.xml2po.mo' and can be safetly -removed once the translated XML file has been created. In the case of -xgettext, the machine object needs to be stored in the -`$TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo' file in order -for the system to interpret it and should not be removed since it is -the file that contain the translation messages themselves. -

-

Automation of localization tasks is achived through the locale -functionality of command-line interface. -

- - -
3.52 trunk/Scripts/Bash/Cli/Functions/Locale   -
- - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_38.html b/Manuals/Filesystem/filesystem-html/filesystem_38.html deleted file mode 100644 index 0113c6b..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_38.html +++ /dev/null @@ -1,124 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.35 trunk/Locales/Identity - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.35 trunk/Locales/Identity

- - - -

3.35.1 Goals

- - - - - -

3.35.2 Description

- - - - - -

3.35.3 Usage

- - - - - -

3.35.4 See also

- - - -
3.1 trunk/Identity   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_39.html b/Manuals/Filesystem/filesystem-html/filesystem_39.html deleted file mode 100644 index 310233c..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_39.html +++ /dev/null @@ -1,204 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.36 trunk/Locales/Identity/Brands - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.36 trunk/Locales/Identity/Brands

- - - -

3.36.1 Goals

- - - - - -

3.36.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.36.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.36.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 designing ratio. -

-

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

-

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

- - -

3.36.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.36.3 Usage

- -

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

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

3.36.4 See also

- - - -
3.2 trunk/Identity/Brands   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_4.html b/Manuals/Filesystem/filesystem-html/filesystem_4.html deleted file mode 100644 index 83184c6..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_4.html +++ /dev/null @@ -1,233 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.1 trunk/Identity - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.1 trunk/Identity

- - - -

3.1.1 Goals

- -

The `trunk/Identity' directory exists to organize CentOS -corporate identity artworks. -

- - -

3.1.2 Description

- -

The CentOS Project corporate identity is the "persona" of the -organization known as The CentOS Project. The CentOS Project -corporate identity plays a significant role in the way the CentOS -Project, as organization, presents itself to both internal and -external stakeholders. In general terms, the CentOS Project corporate -visual identity expresses the values and ambitions of the CentOS -Project organization, its business, and its characteristics. -

-

The CentOS Project corporate identity provides visibility, -recognizability, reputation, structure and identification to the -CentOS Project organization by means of corporate design, corporate -communication, and corporate behaviour. -

-

The CentOS Project settles down its corporate visual identity on a -"monolithic corporate visual identity structure". In this structure -The CentOS Project uses one unique name (The CentOS Brand) and one -unique visual style (The CentOS Default Theme) in all its -manifestations. -

-
-
The CentOS Brands
-

The CentOS brand is the name or trademark that conncects the producer -with their products. In this case, the producer is The CentOS Project -and the products are the CentOS distributions, the CentOS web sites, -the CentOS promotion stuff, etc. -

-

See section trunk/Identity/Brands, for more information. -

-
-
The CentOS Themes
-
-

The CentOS themes are a set of image files connected all together by -one unique visual style. Each theme is organized in different visual -manifestations, in order to cover each visual manifestation of The -CentOS Project (i.e., distributions, websites, promotion stuff, etc.). -See section trunk/Identity/Themes, for more information. -

-
- -

Inside a monolithic corporate visual identity structure, internal and -external stakeholders use to feel a strong sensation of uniformity, -orientation, and identification with the organization. No matter if -you are visiting websites, using the distribution, or acting on social -events, the one unique name and one unique visual style conect them -all to say: Hey! we are all parts of the CentOS project. And, -probably, some vister will say: Can I join the party? Yes you can, it -is free. :) -

- - -

3.1.3 Usage

- -

To produce identity artworks, use the following commands: -

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

When `path/to/dir' refers to one renderable directory under -`trunk/Identity', this command renders identity artworks using -both related design models and related translation files. -

-
-
`centos-art render 'path/to/dir' --filter='pattern''
-
-

When `path/to/dir' refers to one renderable directory under -`trunk/Identity', this command renders identity artworks using -both related design models and related translation files that match -the regular expression passed in `--filter='pattern'' argument. -

-

To control the number of files produced by centos-art -command, you need to look into the translation path and provide a -regular expression pattern that matches the translation path, or -paths, related to the file, or files, you want to produce. -

-

The regular expression pattern you provide to centos-art -command is applied to the translation path from its very beginning. -It is not the same to say `5/en/01-welcome' that -`01-welcome', the frist expression matches but the last one does -not. -

-

When using `--filter='pattern'' you don't need to specify the -file extension. It is removed from translation path before applying -the pattern, so it doesn't count here. -

-
- - - -

3.1.4 File name convenctions

- -

As file name convenction, inside CentOS Artwork Repository, both -text-based and image-based file name produced by centos-art.sh -script has the same name of their translation files without -the `.sed' extension. The file extension is set as follow: -

- - -

3.1.4.1 When text-based files are rendered

- -

Text-based files end up having the same extension of their design -template file. -

- - -

3.1.4.2 When image-based files are rendered

- -

Image-based files always end up having the `.png' extension. -

-
Info

Tip

Once `.png' images are created, other image formats -may be created using the renderFormats post-rendering -action, inside the image-based related pre-rendering configuration -script. -

-

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

- - - -

3.1.5 See also

- - - - -

3.1.6 References

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_40.html b/Manuals/Filesystem/filesystem-html/filesystem_40.html deleted file mode 100644 index 1f791dd..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_40.html +++ /dev/null @@ -1,108 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.37 trunk/Locales/Identity/Brands/Tpl - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.37 trunk/Locales/Identity/Brands/Tpl

- - - -

3.37.1 Goals

- - - -

3.37.2 Description

- - - -

3.37.3 Usage

- - - -

3.37.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_41.html b/Manuals/Filesystem/filesystem-html/filesystem_41.html deleted file mode 100644 index e47ea70..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_41.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.38 trunk/Locales/Identity/Fonts - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.38 trunk/Locales/Identity/Fonts

- - - -

3.38.1 Goals

- -

This section exists to organize fonts translation files. -

- -

3.38.2 Description

- -

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

-
s!font-family:Denmark!font-family:DejaVu LGC Sans!
-s!font-weight:normal!font-weight:bold!
-s!font-style:normal!font-style:italic!
-
-

Inside `trunk/Translations/Fonts', there is one translation file -for each font preview image you want to produce. This way, we create -one translation file for each font-family we use somewhere inside -CentOS visual identity. -

-
Important

Important

Do not create translation files for -font-families not used somewhere inside CentOS visual identity. The -identity of font 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.38.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.38.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.38.4 See also

- - - -
3.3 trunk/Identity/Fonts   -
- - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_42.html b/Manuals/Filesystem/filesystem-html/filesystem_42.html deleted file mode 100644 index 20f2397..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_42.html +++ /dev/null @@ -1,108 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.39 trunk/Locales/Identity/Models - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.39 trunk/Locales/Identity/Models

- - - -

3.39.1 Goals

- - - -

3.39.2 Description

- - - -

3.39.3 Usage

- - - -

3.39.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_43.html b/Manuals/Filesystem/filesystem-html/filesystem_43.html deleted file mode 100644 index 6622bd2..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_43.html +++ /dev/null @@ -1,108 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.40 trunk/Locales/Identity/Release - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.40 trunk/Locales/Identity/Release

- - - -

3.40.1 Goals

- - - -

3.40.2 Description

- - - -

3.40.3 Usage

- - - -

3.40.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_44.html b/Manuals/Filesystem/filesystem-html/filesystem_44.html deleted file mode 100644 index c2113bc..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_44.html +++ /dev/null @@ -1,108 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.41 trunk/Locales/Identity/Themes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.41 trunk/Locales/Identity/Themes

- - - -

3.41.1 Goals

- - - -

3.41.2 Description

- - - -

3.41.3 Usage

- - - -

3.41.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_45.html b/Manuals/Filesystem/filesystem-html/filesystem_45.html deleted file mode 100644 index 5ad2c4b..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_45.html +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.42 trunk/Locales/Identity/Themes/Backgrounds - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.42 trunk/Locales/Identity/Themes/Backgrounds

- - - -

3.42.1 Goals

- - - - - -

3.42.2 Description

- - - - - -

3.42.3 Usage

- - - - - -

3.42.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_46.html b/Manuals/Filesystem/filesystem-html/filesystem_46.html deleted file mode 100644 index bbf0368..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_46.html +++ /dev/null @@ -1,188 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.43 trunk/Locales/Identity/Themes/Distro/Anaconda/Progress - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.43 trunk/Locales/Identity/Themes/Distro/Anaconda/Progress

- - - -

3.43.1 Goals

- - - - - -

3.43.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.43.3 Usage

- -

Translation rendering is described in `trunk/Translations' -documentation entry (-- Removed(pxref:trunk Translations) --). -

- - - -

3.43.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_47.html b/Manuals/Filesystem/filesystem-html/filesystem_47.html deleted file mode 100644 index b309d57..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_47.html +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.44 trunk/Locales/Identity/Widgets - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.44 trunk/Locales/Identity/Widgets

- - - -

3.44.1 Goals

- - - - - -

3.44.2 Description

- - - - - -

3.44.3 Usage

- - - - - -

3.44.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_48.html b/Manuals/Filesystem/filesystem-html/filesystem_48.html deleted file mode 100644 index 14a65d2..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_48.html +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.45 trunk/Manuals - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.45 trunk/Manuals

- - - -

3.45.1 Goals

- - - - - -

3.45.2 Description

- - - - - -

3.45.3 Usage

- - - - - -

3.45.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_49.html b/Manuals/Filesystem/filesystem-html/filesystem_49.html deleted file mode 100644 index 16c9320..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_49.html +++ /dev/null @@ -1,123 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.46 trunk/Scripts - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.46 trunk/Scripts

- - - -

3.46.1 Goals

- -

The `trunk/Scripts' directory exists to: -

- - - - -

3.46.2 Description

- - - - - -

3.46.3 Usage

- - - - - -

3.46.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_5.html b/Manuals/Filesystem/filesystem-html/filesystem_5.html deleted file mode 100644 index 829b8ee..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_5.html +++ /dev/null @@ -1,112 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.2 trunk/Identity/Brands - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.2 trunk/Identity/Brands

- - - -

3.2.1 Goals

- - - - - -

3.2.2 Description

- - - -

3.2.3 Usage

- - - -

3.2.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_50.html b/Manuals/Filesystem/filesystem-html/filesystem_50.html deleted file mode 100644 index 09be060..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_50.html +++ /dev/null @@ -1,251 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.47 trunk/Scripts/Bash - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.47 trunk/Scripts/Bash

- - - -

3.47.1 Goals

- -

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

- - -

3.47.2 Description

- -

The best way to understand `centos-art.sh' automation script is -studying its source code. However, as start point, you may prefer to -read an introductory resume before diving into the source code -details. -

-

The `centos-art.sh' script is written in Bash. Most tasks, inside -`centos-art.sh' script, have been organized in many specific -functionalities that you can invoke from the centos-art -command-line interface. -

-

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 location. If your system was prepared to use CentOS -Artwork Repository correctly (-- Removed(pxref:trunk Scripts Bash Functions -Verify) --), you should have a symbolic link inside `~/bin/' -directory that points to the `centos-art.sh' script file. As -`~/bin/' directory is, by default, inside PATH environment -variable, the execution of centos-art command runs the -`centos-art.sh' script. -

-

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

-

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

-

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

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

In the above example, `centos-art' is the command you use to -invoke `centos-art.sh' script. The `arg1' is required and -represents the functionality you want to perform (e.g., -`verify', `render', `locale', `manual', -etc.). The remaining arguments are modifiers to `arg1'. The -`--arg2' definition is required and represets, specifically, -the action inside the functionality you want to perform. The -`--arg3' and on, are optional. -

-

Once command-line arguments have been retrived, the -`centos-art.sh' script loads specific functionalities using the -`cli_getFunctions.sh' function script. Only one specific -functionality can be loaded at one script execution I.e., you run -centos-art.sh script to run just one functionality. -

-
-
+----------------------------------------------------------------------+
-| [centos@host]$ centos-art function --action='value' --option='value' |
-+----------------------------------------------------------------------+
-| ~/bin/centos-art --> ~/artwork/trunk/Scripts/Bash/centos-art.sh      |
-+---v-----------------------------------------v------------------------+
-    | centos-art.sh                           |
-    +---v---------------------------------v---+
-    .   | initEnvironment.sh              |   .
-    .   +---------------------------------+   .
-    .   | cli $@                          |   .
-    .   +---v-------------------------v---+   .
-    .   .   | cli_getFunctions        |   .   .
-    .   .   +---v-----------------v---+   .   .
-    .   .   .   | function1       |   .   .   .
-    .   .   .   | function2       |   .   .   .
-    .   .   .   | function3       |   .   .   .
-    .   .   .   +-----------------+   .   .   .
-    .   .   ...........................   .   .
-    .   ...................................   .
-    ...........................................
-
-

Figure 3.1: The functionalities initialization environment. - -

-

Functionalities are implemented by means of actions. Once the -functionality has been initiazalized, actions initialization take -place for that functionality. Actions initialization model is very -similar to functions initialization model. But with the difference, -that actions are loaded inside function environment, and so, share -variables and functions defined inside function environment. -

-
-
+--------------------------------------+
-| cli_getFunctions                     |
-+---v------------------------------v---+
-.   | function1                    |   .
-.   +---v----------------------v---+   .
-.   .   | function1_getActions |   .   .
-.   .   +---v--------------v---+   .   .
-.   .   .   | action 1     |   .   .   .
-.   .   .   | action 2     |   .   .   .
-.   .   .   | action n     |   .   .   .
-.   .   .   +--------------+   .   .   .
-.   .   ........................   .   .
-.   ................................   .
-.   +------------------------------+   .
-.   | function2                    |   .
-.   +---v----------------------v---+   .
-.   .   | function2_getActions |   .   .
-.   .   +---v--------------v---+   .   .
-.   .   .   | action 1     |   .   .   .
-.   .   .   | action 2     |   .   .   .
-.   .   .   | action n     |   .   .   .
-.   .   .   +--------------+   .   .   .
-.   .   ........................   .   .
-.   ................................   .
-.   +------------------------------+   .
-.   | function3                    |   .
-.   +---v----------------------v---+   .
-.   .   | function3_getActions |   .   .
-.   .   +---v--------------v---+   .   .
-.   .   .   | action 1     |   .   .   .
-.   .   .   | action 2     |   .   .   .
-.   .   .   | action n     |   .   .   .
-.   .   .   +--------------+   .   .   .
-.   .   ........................   .   .
-.   ................................   .
-........................................
-
-

Figure 3.2: The actions initialization environment. - -

- - -

3.47.3 Usage

- -

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

- - -

3.47.4 See also

- - - -
3.46 trunk/Scripts   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_51.html b/Manuals/Filesystem/filesystem-html/filesystem_51.html deleted file mode 100644 index 372472e..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_51.html +++ /dev/null @@ -1,92 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.48 trunk/Scripts/Bash/Cli - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.48 trunk/Scripts/Bash/Cli

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_52.html b/Manuals/Filesystem/filesystem-html/filesystem_52.html deleted file mode 100644 index c39421c..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_52.html +++ /dev/null @@ -1,1354 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.49 trunk/Scripts/Bash/Cli/Functions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.49 trunk/Scripts/Bash/Cli/Functions

- - - -

3.49.1 Goals

- -

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

- - -

3.49.2 Description

- -

The specific functions of `centos-art.sh' script are designed -with "Software Toolbox" philosophy (see (coreutils.info)Toolbox introduction) in mind: each program "should do one -thing well". Inside `centos-art.sh' script, each specific -functionality is considered a program that should do one thing well. -Of course, if you find that they still don't do it, feel free to -improve them in order for them to do so. -

-

The specific functions of `centos-art.sh' script are organized -inside specific directories under `trunk/Scripts/Bash/Functions' -location. Each specific function directory should be named as the -function it represents, with the first letter in uppercase. For -example, if the function name is render, the specific function -directory for it would be `trunk/Scripts/Bash/Functions/Render'. -

-

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

-

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

-
Info

Tip

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

- -

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

-

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

-

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

-

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

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

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

-

Inside `centos-art.sh' script, as convenction, each function -script has one top commentary, followed by one blank line, and then -one function defintion below it only. -

-

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

-

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

-
#!/bin/bash
-#
-# greet.sh -- This function outputs different kind of greetings to
-# your screen. Use this function to understand how centos-art.sh
-# script specific functionalities work.
-#
-# Copyright (C) YEAR YOURFULLNAME
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
-# (at your option) any later version.
-# 
-# This program is distributed in the hope that it will be useful, but
-# WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
-# General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
-# USA.
-# 
-# ----------------------------------------------------------------------
-# $Id$
-# ----------------------------------------------------------------------
-
-

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

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

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

-

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

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

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

-

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

-

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

-

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

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

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

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

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

-

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

-

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

-

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

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

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

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

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

-

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

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

To have a well documented function helps user to understand how your -function really works, and how it should be used. When no valid -action is passed to a function, the `centos-art.sh' script uses -the function documentation entry as vehicle to communicate which the -valid functions are. When no documentation entry exists for a -function, the `centos-art.sh' script informs that no -documentation entry exists for such function and requests user to -create it right at that time. -

-

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

-
centos-art locale --edit
-
-
Warning

Warning

To translate output messages in different languages, -your system locale information --as in LANG environment -variable-- must be set to that locale you want to produce translated -messages for. For example, if you want to produce translated messages -for Spanish language, your system locale information must be set to -`es_ES.UTF-8', or similar, first. -

- -

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

-

In greet function example we've described so far, we only use -cli_printMessage global function in action specific function -definitions in order to print messages, but more interesting things -can be achieved inside action specific function definitions. For -example, if you pass a directory path as action value in second -argument, you could retrive a list of files from therein, and process -them. If the list of files turns too long or you just want to control -which files to process, you could add the third argument in the form -`--filter='regex'' and reduce the amount of files to process -using a regular expression pattern. -

-

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

-

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

- - -

3.49.3 Usage

- - - -

3.49.3.1 Global variables

- -

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

-
-
Variable: TEXTDOMAIN - -
-

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

- -
-
Variable: TEXTDOMAINDIR - -
-

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

- -
-
Variable: FUNCNAM - -
-

Define function name. -

-

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

-

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

-

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

- -
-
Variable: FUNCDIR - -
-
- -
-
Variable: FUNCDIRNAME - -
-
- -
-
Variable: FUNCSCRIPT - -
-
- -
-
Variable: FUNCCONFIG - -
-
- -
-
Variable: ACTIONNAM - -
-

Define action name. -

-

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

-

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

-

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

- -
-
Variable: ACTIONVAL - -
-

Define action value. -

-

Action values are associated to just one action name. Action values -contain the working copy entry over which its associated action will be -performed in. Working copy entries can be files or directories inside -the working copy. -

- -
-
Variable: REGEX - -
-

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

-

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

-

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

- -
-
Variable: ARGUMENTS - -
-

Define optional arguments. -

-

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

-

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

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

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

-

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

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

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

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

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

-

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

-

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

-

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

- -
-
Variable: EDITOR - -
-

Default text editor. -

-

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

-

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

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

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

- - - -

3.49.3.2 Global functions

- -

Function scripts stored directly under -`trunk/Scripts/Bash/Functions/' directory are used to define -global functions. Global functions can be used inside action specific -functionalities and or even be reused inside themselves. This section -provides introductory information to global functions you can use -inside `centos-art.sh' script. -

-
-
Function: cli_checkActionArguments - -
-

Validate action value (ACTIONVAL) variable. -

-

The action value variable can take one of the following values: -

-
    -
  1. Path to one directory inside the local working copy, -
  2. Path to one file inside the local working copy, -
- -

If another value different from that specified above is passed to -action value variable, the `centos-art.sh' script prints an error -message and ends script execution. -

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

Verify file existence. -

-

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

-
-
`d'
-
`directory'
-

Ends script execution if FILE is not a directory. -

-

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

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

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

-
`h'
-
`symbolic-link'
-

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

-
`x'
-
`execution'
-

Ends script execution if FILE is not executable. -

-
`fh'
-

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

-
`fd'
-

Ends script execution if FILE is neither a regular file nor a -directory. -

-
`isInWorkingCopy'
-

Ends script execution if FILE is not inside the working copy. -

-
- -

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

- -
-
Function: cli_commitRepoChanges [LOCATION] - -
-

Syncronize changes between repository and working copy. -

-

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

-

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

-

If LOCATION argument is not specified, the value of -ACTIONVAL variable is used as reference instead. -

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

Figure 3.3: The cli_commitRepoChanges function output. - -

-

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

- -
-
Function: cli_doParseArguments - -
-

Redefine arguments (ARGUMENTS) global variable using -getopt command output. For more information about how to use -cli_doParseArguments function, see ARGUMENTS variable -description above. -

- -
-
Function: cli_doParseArgumentsReDef $@ - -
-

Initialize/reset arguments (ARGUMENTS) global variable using -positional parameters variable ($@) as reference. -

-

When we work inside function definitions, positional parameters are -reset to the last function definition positional parameters. If you -need to redefine positional parameters from one specific function, you -need to call cli_doParseArgumentsReDef with the positional -parameters variable ($@), set as first argument, to that -specific function you want to redefine positional parameters at. -

- -
-
Function: cli_getArguments - -
-

Initialize function name (FUNCNAM), action name -(ACTIONNAM), and action value (ACTIONVAL) global -variables, using positional parameters passed in $@ variable. -

-

The cli_getArguments function is called from cli.sh -function script, using cli function positional parameters -(i.e., the positional parameters passed as arguments in the -command-line) as first function argument. -

-

Once command-line positional parameters are accesible to -`centos-art.sh' script execution evironment, -cli_getArguments uses regular expression to retrive -action variables from first and second argument. The first argument -defines the value used as function name (FUNCNAM), and the -second argument defines both values used as action name -(ACTIONNAM) and action value (ACTIONVAL), respectively. -

-

The first argument is a word in lower case. This word specifies the -name of the functionality you want to use (e.g., `render' to -render images, `manual' to work on documentation, and so on.) -

-

The second argument has a long option style (e.g., -`--option=value'). The `--option' represents the action name -(ACTIONNAM), and the characters inbetween the equal sign -(`=') and the first space character, are considered as the action -value (ACTIONVAL). In order to provide action values with space -characters inbetween you need to enclose action value with quotes like -in `--option='This is long value with spaces inbetween''. -Generally, action values are used to specify paths over which the -action name acts on. -

-

Once action related variables (i.e., FUNCNAM, ACTIONNAM, -and ACTIONVAL) are defined and validated, -cli_getArguments shifts the positional arguments to remove the -first two arguments passed (i.e., those used to retrive action related -variables) and redefine the arguments (ARGUMENTS) global -variable with the new positional parameters information. -

- -
-
Function: cli_getFunctions - -
-

Initialize funtionalities supported by `centos-art.sh' script. -

-

Functionalities supported by `centos-art.sh' script are organized -in functionality directories under -`trunk/Scripts/Bash/Functions/' directory. Each functionality -directory stores function scripts to the functionality such directory -was created for. Function scripts contain function definitions. -Function definitions contain several commands focused on achieving one -specific task only (i.e., the one such functionality was created for). -

-

In order for `centos-art.sh' script to recognize a functionality, -such functionality needs to be stored under -`trunk/Scripts/Bash/Functions/' in a directory written -capitalized (i.e., the whole name is written in lowercase except the -first character which is in uppercase). The directory where one -specific functionality is stored is known as the `functionality -directory'. -

-

Inside each functionality directory, the functionalty itself is -implemented through function scripts. Function scripts are organized -in files independently one another and written in `camelCase' -format with the function name as prefix. Separation between prefix -and description is done using underscore (`_') character. -

-

In order for `centos-art.sh' script to load functionalities -correctly, function definition inside function scripts should be set -using the `function' reserved word, just as in the following -example: -

-
function prefix_doSomething {
-
-    # Do something here...
-
-}
-
-

The above function definition is just a convenction we use, in order -to make identification of function names easier read and automate by -`centos-art.sh' script initialization commands, once -`centos-art.sh' script determines which functionality directory -to use. Specifically, in order to initialize and export functions, -`centos-art.sh' script executes all function scripts inside the -functionality directory, and later grep on them using a -regular expression pattern, where the `function' reserved word is -used as reference to retrive the function names and export them to -`centos-art.sh' script execution environment, and so, make -function definitions --from function scripts inside the functionality -directory-- available for further calls. -

-

If the functionality specified in the command-line first argument -doesn't have a functionality directory, `centos-art.sh' script -considers the functionality provided in the command-line as invalid -functionality and immediatly stops script execution with an error -message. -

-

In order to keep visual consistency among function scripts, please -consider using the following function script design model as template -for your own function scripts: -

-
#!/bin/bash
-#
-# prefix_doSomething.sh -- This function illustrates function scripts
-# design model you can use to create your own function scripts inside
-# centos-art.sh script.
-#
-# Copyright (C) YEAR YOURFULLNAME
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
-# (at your option) any later version.
-# 
-# This program is distributed in the hope that it will be useful, but
-# WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
-# General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
-# USA.
-# 
-# ----------------------------------------------------------------------
-# $Id$
-# ----------------------------------------------------------------------
-
-function prefix_doSomething {
-
-    # Do something here...
-
-}
-
- -
-
Function: cli_getCountryCodes [FILTER] - -
-

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

-

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

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

Outputs country name supported by `centos-art.sh' script. -

-

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

- -
-
Function: cli_getCurrentLocale - -
-

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

-

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

-

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

-

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

-

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

- -
-
Function: cli_getFilesList [LOCATION] - -
-

Output list of files to process. -

-

The cli_getFilesList function uses LOCATION variable as -source location to build a list of files just as specified by regular -expression (REGEX) global variable. Essentially, what the -cli_getFilesList function does is using find command -to look for files in the location (LOCATION) just as posix-egrep -regular expression (REGEX) specifies. -

-

If LOCATION is not specified when cli_getFilesList -function is called, the action value (ACTIONVAL) global variable -is used as location value instead. -

-

By default, if the regular expression (REGEX) global variable is -not redefined after its first definition in the cli function, -all files that match default regular expression value (i.e., -`.+') will be added to the list of files to process. Otherwise, -if you redefine the regular expression global variable after its first -definition in the cli function and before calling -cli_getFilesList function, the last value you specifed is used -instead. -

-

When you need to customize the regular expression (REGEX) global -variable value inside a function, do not redefine the global variable -(at least you be absolutly convinced you need to). Instead, set the -regular expression global variable as `local' to the function you -need a customized regular expression value for. If we don't redefine -the regular expression global variable as local to the function, or -use another name for the regular expression variable (which is not -very convenient in order to keep the amount of names to remember low), -you may experiment undesired concantenation issues that make your -regular expression to be something different from that you expect them -to be, specially if the function where you are doing the variable -redefinition is called several times during the same script execution. -

-

As result, the cli_getFilesList re-defines the value of -FILES variable with the list of files the find command -returned. As example, consider the following construction: -

-
function prefix_doSomething {
-
-    # Initialize the list of files to process.
-    local FILES=''
-
-    # Initialize location.
-    local LOCATION=/home/centos/artwork/trunk/Identity/Themes/Models/Default
-
-    # Re-define regular expression to match scalable vector graphic
-    # files only. Note how we use the global value of REGEX to build a
-    # new local REGEX value here.
-    local REGEX="${REGEX}.*\.(svgz|svg)"
-
-    # Redefine list of files to process.
-    cli_getFilesList $LOCATION
-
-    # Process list of files.
-    for FILE in $FILES;do
-        cli_printMessages "$FILE" 'AsResponseLine'
-        # Do something else here on...
-    done
-
-}
-
-
- -
-
Function: cli_getLangCodes [FILTER] - -
-

Outputs language codes supported by `centos-art.sh' script. -

-

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

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

Outputs language names supported by `centos-art.sh' script. -

-

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

- -
-
Function: cli_getLocales - -
-

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

-

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

- -
-
Function: cli_getRepoName NAME TYPE - -
-

Sanitate file names. -

-

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

-
Important

Important

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

- -

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

-

The TYPE variable specifies what type of sanitation you want to -perform on NAME. The TYPE can be one of the following -values: -

-
-
`d'
-
`directory'
-

Sanitate directory NAMEs. -

-
`f'
-
`regular-file'
-

Sanitate regular file NAMEs. -

-
- -

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

-

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

-

When we change file name convenctions inside cli_getRepoName -what we are really changing is the way functions interpret repository -file system organization. Notice that when we change a file name -(e.g., a function name), it is necessary to update all files where -such file name is placed on. This may require a massive substitution -inside the repository, each time we change name convenctions in the -repository (-- Removed(pxref:trunk Scripts Bash Functions Path) --, for more -information). -

- -
-
Function: cli_getRepoStatus [LOCATION] - -
-

Request repository status. -

-

This function requests the status of a LOCATION inside the -working copy using the svn status command and returns the -first character in the output line, just as described in svn -help status. If LOCATION is not a regular file or a directory, -inside the working copy, the `centos-art.sh' script prints a -message and ends its execution. -

-

Use this function to perform verifications based a repository -LOCATION status. -

- -
-
Function: cli_getTemporalFile NAME - -
-

Output absolute path to temporal file NAME. -

-

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

-
cli_getTemporalFile $FILE
-
-

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

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

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

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

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

- -
-
Function: cli_getThemeName - -
-

Output theme name. -

-

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

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

Define standard output message definition supported by -`centos-art.sh' script. -

-

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

-
-
`AsHeadingLine'
-

To print heading messages. -

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

To print warning messages. -

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

To print note messages. -

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

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

Updating        $MESSAGE
-
-
-
`AsRemovingLine'
-

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

Removing        $MESSAGE
-
-
-
`AsCheckingLine'
-

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

Checking        $MESSAGE
-
-
-
`AsCreatingLine'
-

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

Creating        $MESSAGE
-
-
-
`AsSavedAsLine'
-

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

Saved as        $MESSAGE
-
-
-
`AsLinkToLine'
-

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

Linked to       $MESSAGE
-
-
-
`AsMovedToLine'
-

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

Moved to        $MESSAGE
-
-
-
`AsTranslationLine'
-

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

Translation     $MESSAGE
-
-
-
`AsConfigurationLine'
-

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

Configuration   $MESSAGE
-
-
-
`AsResponseLine'
-

To print response messages on one-column format. -

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

To print request messages on one-column format. Request messages -output messages with one colon (`:') and without trailing newline -(`\n') at message end. -

$MESSAGE:
-
-
-
`AsYesOrNoRequestLine'
-

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

-
$MESSAGE [y/N]:
-
-

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

-
$MESSAGE [s/N]:
-
-

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

-

Definition of which confirmation word to use is set on translation -messages for your specific locale information. -- Removed(xref:trunk Scripts -Bash Functions Locale) --, for more information about locale-specific -translation messages. -

-
-
`AsToKnowMoreLine'
-

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

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

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

-
-
`AsRegularLine'
-

To standardize regular messages on one-column format. -

-

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

-
- -

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

-
Info

Tip

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

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

3.49.3.3 Specific functions

- -

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

- - - -

3.49.4 See also

- - - -
3.47 trunk/Scripts/Bash   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_53.html b/Manuals/Filesystem/filesystem-html/filesystem_53.html deleted file mode 100644 index b0455ba..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_53.html +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.50 trunk/Scripts/Bash/Cli/Functions/Help - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.50 trunk/Scripts/Bash/Cli/Functions/Help

- - - -

3.50.1 Goals

- - - - - -

3.50.2 Description

- - - - - -

3.50.3 Usage

- - - - - -

3.50.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_54.html b/Manuals/Filesystem/filesystem-html/filesystem_54.html deleted file mode 100644 index da714b6..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_54.html +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.51 trunk/Scripts/Bash/Cli/Functions/Html - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.51 trunk/Scripts/Bash/Cli/Functions/Html

- - - -

3.51.1 Goals

- - - - - -

3.51.2 Description

- - - - - -

3.51.3 Usage

- - - - - -

3.51.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_55.html b/Manuals/Filesystem/filesystem-html/filesystem_55.html deleted file mode 100644 index dd32a24..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_55.html +++ /dev/null @@ -1,185 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.52 trunk/Scripts/Bash/Cli/Functions/Locale - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.52 trunk/Scripts/Bash/Cli/Functions/Locale

- - - -

3.52.1 Goals

- - - - - -

3.52.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 finishd PO file edition and quit text editor, the -centos-art command creates the related machine object in the -location `$CLI_LANG/LC_MESSAGES/$TEXTDOMAIN.mo'. -

-

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

-

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

- - - - - - -

3.52.3 Usage

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

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

-
`centos-art locale --list'
-

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

-
- - - -

3.52.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_56.html b/Manuals/Filesystem/filesystem-html/filesystem_56.html deleted file mode 100644 index fa1b0ba..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_56.html +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.53 trunk/Scripts/Bash/Cli/Functions/Manual - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.53 trunk/Scripts/Bash/Cli/Functions/Manual

- - - -

3.53.1 Goals

- - - - - -

3.53.2 Description

- - - - - -

3.53.3 Usage

- - - - - -

3.53.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_57.html b/Manuals/Filesystem/filesystem-html/filesystem_57.html deleted file mode 100644 index cb1f243..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_57.html +++ /dev/null @@ -1,437 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.54 trunk/Scripts/Bash/Cli/Functions/Path - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.54 trunk/Scripts/Bash/Cli/Functions/Path

- - - -

3.54.1 Goals

- -

This section exists to organize files related to path -functiontionality. The path functionality standardizes -movement, syncronization, branching, tagging, and general file -maintainance inside the repository. -

- - -

3.54.2 Description

- -

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

- - -

3.54.2.1 Repository layout

- -

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

-

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

-

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

-

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

-

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

-

The CentOS Artwork Repository layout is firmly grounded on a -Subversion base. Subversion (http://subversion.tigris.org) is a -version control system, which allows you to keep old versions of files -and directories (usually source code), keep a log of who, when, and -why changes occurred, etc., like CVS, RCS or SCCS. Subversion keeps a -single copy of the master sources. This copy is called the source -"repository"; it contains all the information to permit extracting -previous versions of those files at any time. -

- - -

3.54.2.2 Repository name convenctions

- -

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

-

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

-

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

- - -

3.54.2.3 Repository work flow

- -

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

-

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

-

Initially, we start working themes on their trunk development line -(e.g., `trunk/Identity/Themes/Motifs/TreeFlower/'), here we -organize information that cannot be produced automatically (i.e., -background images, concepts, color information, screenshots, etc.). -

-

Later, when theme trunk development line is considered "ready" for -implementation (e.g., all required backgrounds have been designed), -we create a branch for it (e.g., -`branches/Identity/Themes/Motifs/TreeFlower/1/'). Once the -branch has been created, we forget that branch and continue working -the trunk development line while others (e.g., an artwork quality -assurance team) test the new branch for tunning it up. -

-

Once the branch has been tunned up, and considered "ready" for -release, it is freezed under `tags/' directory (e.g., -`tags/Identity/Themes/Motifs/TreeFower/1.0/') for packagers, -webmasters, promoters, and anyone who needs images from that CentOS -theme the tag was created for. -

-

Both branches and tags, inside CentOS Artwork Repository, use -numerical values to identify themselves under the same location. -Branches start at one (i.e., `1') and increment one unit for each -branch created from the same trunk development line. Tags start at -zero (i.e., `0') and increment one unit for each tag created from -the same branch development line. -

-
Convenction

Convenction

Do not freeze trunk development lines using tags -directly. If you think you need to freeze a trunk development line, -create a branch for it and then freeze that branch instead. -

- -

The trunk development line may introduce problems we cannot see -immediatly. Certainly, the high changable nature of trunk development -line complicates finding and fixing such problems. On the other hand, -the branched development lines provide a more predictable area where -only fixes/corrections to current content are commited up to -repository. -

-

If others find and fix bugs inside the branched development line, we -could merge such changes/experiences back to trunk development line -(not visversa) in order for future branches, created from trunk, to -benefit. -

-

Time intervals used to create branches and tags may vary, just as -different needs may arrive. For example, consider the release schema -of CentOS distribution: one major release every 2 years, security -updates every 6 months, support for 7 years long. Each time a CentOS -distribution is released, specially if it is a major release, there is -a theme need in order to cover CentOS distribution artwork -requirements. At this point, is where CentOS Artwork Repository comes -up to scene. -

-

Before releasing a new major release of CentOS distribution we create -a branch for one of several theme development lines available inside -the CentOS Artwork Repository, perform quality assurance on it, and -later, freeze that branch using tags. Once a the theme branch has been -frozen (under `tags/' directory), CentOS Packagers (the persons -whom build CentOS distribution) can use that frozen branch as source -location to fulfill CentOS distribution artwork needs. The same -applies to CentOS Webmasters (the persons whom build CentOS websites), -and any other visual manifestation required by the project. -

- - -

3.54.2.4 Parallel directories

- -

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

-

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

-

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

-

Another example of parallel directory is the documentation structure -created by manual functionality. This time, -`centos-art.sh' script uses parallel directory information with -uncommon directory levels to build the documentation entry required by -Texinfo documentation system, inside the repository. -

-

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

-

When one parent directory changes, all their related parallel -directories need to be changed too. This is required in order for -parallel directories to retain their relation with the parent -directory structure. In the other hand, parallel directories should -never be modified under no reason but to satisfy the relation to their -parent directory structure. Liberal change of parallel directories -may suppresses the conceptual idea they were initially created for; -and certainly, things may stop working the way they should do. -

- - -

3.54.2.5 Syncronizing path information

- -

Parallel directories are very useful to keep repository organized but -introduce some complications. For instance, consider what would -happen to functionalities like manual (`trunk Scripts Bash -Functions Manual') that rely on parent directory structures to create -documentation entries (using parallel directory structures) if one of -those parent directory structures suddenly changes after the -documentation entry has been already created for it? -

-

In such cases, functionalities like manual may confuse -themselves if path information is not updated to reflect the relation -with its parent directory. Such functionalities work with parent -directory structure as reference; if a parent directory changes, the -functionalities dont't even note it because they work with the last -parent directory structure available in the repository, no matter what -it is. -

-

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

-

There is no immediate way for manual, and similar -functionalities that use parent directories as reference, to know when -and how directory movements take place inside the repository. Such -information is available only when the file movement itself takes -place inside the repository. So, is there, at the moment of moving -files, when we need to syncronize parallel directories with their -unique parent directory structure. -

-
Warning

Warning

There is not support for URL reference inside -`centos-art.sh' script. The `centos-art.sh' script is -designed to work with local files inside the working copy only. -

- -

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

-

Finally, once all path information has been corrected, it is time to -take care of information inside the files. For instance, considere -what would happen if you make a reference to a documentation node, and -later the documentation node you refere to is deleted. That would make -Texinfo to produce error messages at export time. So, the -`centos-art.sh' script needs to know when such changes happen, in -a way they could be noted and handled without producing errors. -

- - -

3.54.2.6 What is the right place to store it?

- -

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

-

The CentOS Community different free support vains (see: -http://wiki.centos.org/GettingHelp) are the best place to find -answers to your question, but going there with hands empty is not good -idea. It may give the impression you don't really care about. Instead, -consider the following suggestions to find your own comprehension and -so, make your propositions based on it. -

-

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

-

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

-

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

-
centos-art manual --read=turnk/
-centos-art manual --read=turnk/Identity/
-centos-art manual --read=turnk/Identity/Themes/
-centos-art manual --read=turnk/Identity/Themes/Motifs/
-centos-art manual --read=turnk/Identity/Themes/Motifs/TreeFlower/
-
-

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

- - -

3.54.3 Usage

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

Copy `SRC' to `DST' and schedule `DST' for -addition (with history). In this command, `SRC' and `DST' -are both working copy (WC) entries. -

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

Delete `DST'. In order for this command to work the file or -directory you intend to delete should be under version control first. -In this command, `SRC' is a working copy (WC) entry. -

-
-
- - - -

3.54.4 See also

- - - -
3.47 trunk/Scripts/Bash   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_58.html b/Manuals/Filesystem/filesystem-html/filesystem_58.html deleted file mode 100644 index 6380525..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_58.html +++ /dev/null @@ -1,821 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.55 trunk/Scripts/Bash/Cli/Functions/Render - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.55 trunk/Scripts/Bash/Cli/Functions/Render

- -

The render functionality exists to produce both identity and -translation files on different levels of information (i.e., different -languages, release numbers, architectures, etc.). -

-

The render functionality relies on "renderable directory -structures" to produce files. Renderable directory structures can be -either "identity directory structures" or "translation directory -structures" with special directories inside. -

- - -

3.55.1 Renderable identity directory structures

- -

Renderable identity directory structures are the starting point of -identity rendition. Whenever we want to render a component of CentOS -corporate visual identity, we need to point `centos-art.sh' to a -renderable identity directory structure. If such renderable identity -directory structure doesn't exist, then it is good time to create it. -

-

Inside the working copy, one renderable identity directory structures -represents one visual manifestation of CentOS corporate visual -identity, or said differently, each visual manifestation of CentOS -corporate visual identity should have one renderable identity -directory structure. -

-

Inside renderable identity directory structures, `centos-art.sh' -can render both image-based and text-based files. Specification of -whether a renderable identity directory structure produces image-based -or text-based content is a configuration action that takes place in -the pre-rendition configuration script of that renderable identity -directory structure. -

-

Inside renderable identity directory structures, content production is -organized in different configurations. A content production -configuration is a unique combination of the components that make an -identity directory structure renderable. One content production -configuration does one thing only (e.g., to produce untranslated -images), but it can be extended (e.g., adding translation files) to -achieve different needs (e.g., to produce translated images). -

- - -

3.55.1.1 Design template without translation

- -

The design template without translation configuration is based on a -renderable identity directory structure with an empty translation -directory structure. In this configuration, one design template -produces one untranslated file. Both design templates and final -untranslated files share the same file name, but they differ one -another in file-type and file-extension. -

-

For example, to produce images without translations (there is no much -use in producing text-based files without translations), consider the -following configuration: -

-
-
One renderable identity directory structure:
-
-

In this example we used `Identity/Path/To/Dir' as the identity -component we want to produce untranslated images for. Identity -components can be either under `trunk/' or `branches/' -directory structure. -

-

The identity component (i.e., `Identity/Path/To/Dir', in this -case) is also the bond component we use to connect the identity -directory structures with their respective auxiliar directories (i.e., -translation directory structres and pre-rendition configuration -structures). The bond component is the path convenction that -`centos-art.sh' uses to know where to look for related -translations, configuration scripts and whatever auxiliar thing a -renderable directory structure may need to have. -

-
      | The bond component
-      |----------------->|
-trunk/Identity/Path/To/Dir  <-- Renderable identity directory structure.
-|-- Tpl                     <-- Design template directory.
-|   `-- file.svg            <-- Design template file.
-`-- Img                     <-- Directory used to store final files.
-    `-- file.png            <-- Final image-based file produced from
-                                design template file.
-
-

Inside design template directory, design template files are based on -SVG (Scalable Vector Graphics) and use the extension -.svg. Design template files can be organized using several -directory levels to create a simple but extensible configuration, -specially if translated images are not required. -

-

In order for SVG (Scalable Vector Graphics) files to be -considered "design template" files, they should be placed under the -design template directory and to have set a CENTOSARTWORK -object id inside. -

-

The CENTOSARTWORK word itself is a convenction name we use to -define which object/design area, inside a design template, the -`centos-art.sh' script will use to export as -PNG (Portable Network Graphic) image at rendition time. -Whithout such object id specification, the `centos-art.sh' script -cannot know what object/design area you (as designer) want to export -as PNG (Portable Network Graphic) image file. -

-
info

Note

At rendition time, the content of `Img/' directory -structure is produced by `centos-art.sh' automatically. -

- -

When a renderable identity directory structure is configured to -produce image-based content, `centos-art.sh' produces -PNG (Portable Network Graphics) files with the .png -extension. Once the base image format has been produced, it is -possible for `centos-art.sh' to use it in order to automatically -create other image formats that may be needed (-- Removed(pxref:trunk Scripts -Bash Functions Render Config) --). -

-

Inside the working copy, you can find an example of "design template -without translation" configuration at `trunk/Identity/Models/'. -

-

See section trunk/Identity, for more information. -

-
-
One translation directory structure:
-
-

In order for an identity entry to be considered an identity renderable -directory structure, it should have a translation entry. The content -of the translation entry is relevant to determine how to process the -identity renderable directory entry. -

-

If the translation entry is empty (i.e., there is no file inside it), -`centos-art.sh' interprets the identity renderable directory -structure as a "design templates without translation" configuration. -

-
                   | The bond component
-                   |----------------->|
-trunk/Translations/Identity/Path/To/Dir
-`-- (empty)
-
-

If the translation entry is not empty, `centos-art.sh' can -interpret the identity renderable directory structure as one of the -following configurations: "design template with translation -(one-to-one)" or "design template with translation (optimized)". -Which one of these configurations is used depends on the value -assigned to the matching list (MATCHINGLIST) variable in the -pre-rendition configuration script of the renderable identity -directory structure we are producing images for. -

-

If the matching list variable is empty (as it is by default), then -"design template with translation (one-to-one)" configuration is -used. In this configuration it is required that both design templates -and translation files have the same file names. This way, one -translation files is applied to one design template, to produce -one translated image. -

-

If the matching list variable is not empty (because you redefine it in -the pre-rendition configuration script), then "design template with -translation (optimized)" configuration is used instead. In this -configuration, design templates and translation files don't need to -have the same names since such name relationship between them is -specified in the matching list properly. -

-

-- Removed(xref:trunk Translations) --, for more information. -

-
-
One pre-rendition configuration script:
-
-

In order to make an identity directory structure renderable, a -pre-rendition configuration script should exist for it. The -pre-rendition configuration script specifies what type of rendition -does `centos-art.sh' will perform over the identity directory -structure and how does it do that. -

-
                                           | The bond component
-                                           |----------------->|
-trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir
-`-- render.conf.sh
-
-

In this configuration the pre-rendition configuration script -(`render.conf.sh') would look like the following: -

-
function render_loadConfig {
-
-    # Define rendition actions.
-    ACTIONS[0]='BASE:renderImage'
-
-}
-
-

Since translation directory structure is empty, `centos-art.sh' -assumes a "design template without translation" configuration to -produce untranslated images. -

-

To produce untranslated images, `centos-art.sh' takes one design -template and creates one temporal instance from it. Later, -`centos-art.sh' uses the temporal design template instance as -source file to export the final untranslated image. The action of -exporting images from SVG (Scalable Vector Graphics) to -PNG (Portable Network Graphics) is possible thanks to -Inkscape's command-line interface and the CENTOSARTWORK object -id we previously set inside design templates. -

-
centos-art.sh render --identity=trunk/Identity/Path/To/Dir
--------------------------------------------------
-0 | Execute centos-art.sh on renderable identity directory structure.
---v----------------------------------------------
-trunk/Identity/Path/To/Dir/Tpl/file.svg
--------------------------------------------------
-1 | Create instance from design template.
---v----------------------------------------------
-/tmp/centos-art.sh-a07e824a-5953-4c21-90ae-f5e8e9781f5f-file.svg
--------------------------------------------------
-2 | Render untranslated image from design template instance.
---v----------------------------------------------
-trunk/Identity/NewDir/Img/file.png
--------------------------------------------------
-3 | Remove design template instance.
-
-

Finally, when the untranslated image has been created, the temporal -design template instance is removed. At this point, -`centos-art.sh' takes the next design template and repeats the -whole production flow once again (design template by design template), -until all design templates be processed. -

-

-- Removed(xref:trunk Scripts Bash Functions Render Config) --, for more -information. -

-
- - - -

3.55.1.2 Design template with translation (one-to-one)

- -

Producing untranslated images is fine in many cases, but not always. -Sometimes it is required to produce images in different languages and -that is something that untrasnlated image production cannot achieve. -However, if we fill its empty translation entry with translation files -(one for each design template) we extend the production flow from -untranslated image production to translated image production. -

-

In order for `centos-art.sh' to produce images correctly, each -design template should have one translation file and each translation -file should have one design template. Otherwise, if there is a -missing design template or a missing translation file, -`centos-art.sh' will not produce the final image related to the -missing component. -

-

In order for `centos-art.sh' to know which is the relation -between translation files and design templates the translation -directory structure is taken as reference. For example, the -`trunk/Translations/Identity/Path/To/Dir/file.sed' translation -file does match `trunk/Identity/Path/To/Dir/Tpl/file.svg' design -template, but it doesn't match -`trunk/Identity/Path/To/Dir/File.svg' or -`trunk/Identity/Path/To/Dir/Tpl/File.svg' or -`trunk/Identity/Path/To/Dir/Tpl/SubDir/file.svg' design -templates. -

-

The pre-rendition configuration script used to produce untranslated -images is the same we use to produce translated images. There is no -need to modify it. So, as we are using the same pre-rendition -configuration script, we can say that translated image production is -somehow an extended/improved version of untranslated image production. -

-
info

Note

If we use no translation file in the translation entry -(i.e., an empty directory), `centos-art.sh' assumes the -untranslated image production. If we fill the translation entry with -translation files, `centos-art.sh' assumes the translated image -production. -

- -

To produce final images, `centos-art.sh' applies one translation -file to one design template and produce a translated design template -instance. Later, `centos-art.sh' uses the translated template -instance to produce the translated image. Finally, when the translated -image has been produced, `centos-art.sh' removes the translated -design template instance. This production flow is repeated for each -translation file available in the translatio entry. -

-
centos-art.sh render --identity=trunk/Identity/Path/To/Dir
--------------------------------------------------
-0 | Execute centos-art.sh on directory structure.
---v----------------------------------------------
-trunk/Translations/Identity/Path/To/Dir/file.sed
--------------------------------------------------
-1 | Apply translation to design template.
---v----------------------------------------------
-trunk/Identity/Path/To/Dir/Tpl/file.svg
--------------------------------------------------
-2 | Create design template instance.
---v----------------------------------------------
-/tmp/centos-art.sh-a07e824a-5953-4c21-90ae-f5e8e9781f5f-file.svg
--------------------------------------------------
-3 | Render PNG image from template instance.
---v----------------------------------------------
-trunk/Identity/NewDir/Img/file.png
--------------------------------------------------
-4 | Remove design template instance.
-
- - -

3.55.1.3 Design template with translation (optimized)

- -

Producing translated images satisfies almost all our production images -needs, but there is still a pitfall in them. In order to produce -translated images as in the "one-to-one" configuration describes -previously, it is required that one translation file has one design -template. That's useful in many cases, but what would happen if we -need to apply many different translation files to the same design -template? Should we have to duplicate the same design template file -for each translation file, in order to satisfy the "one-to-one" -relation? What if we need to assign translation files to design -templates arbitrarily? -

-

Certenly, that's something the "one-to-one" configuration cannot -handle. So, that's why we had to "optimize" it. The optimized -configuration consists on using a matching list (MATCHINGLIST) -variable that specifies the relationship between translation files and -design templates in an arbitrary way. Using such matching list between -translation files and design templates let us use as many assignment -combinations as translation files and design templates we are working -with. -

-

The MATCHINGLIST variable is set in the pre-rendition -configuration script of the component we want to produce images for. -By default, the MATCHINGLIST variable is empty which means no -matching list is used. Otherwise, if MATCHINGLIST variable has a -value different to empty value then, `centos-art.sh' interprets -the matching list in order to know how translation files are applied -to design templates. -

-

For example, consider the following configuration: -

-
-
One entry under `trunk/Identity/':
-
-

In this configuration we want to produce three images using a -paragraph-based style, controlled by `paragraph.svg' design -template; and one image using a list-based style, controlled by -`list.svg' design template. -

-
trunk/Identity/Path/To/Dir
-|-- Tpl
-|   |-- paragraph.svg
-|   `-- list.svg
-`-- Img
-    |-- 01-welcome.png
-    |-- 02-donate.png
-    |-- 03-docs.png
-    `-- 04-support.png
-
-
-
One entry under `trunk/Translations/':
-
-

In order to produce translated images we need to have one translation -file for each translated image we want to produce. Notice how -translation names do match final image file names, but how translation -names do not match design template names. When we use matching list -there is no need for translation files to match the names of design -templates, such name relation is set inside the matching list itself. -

-
trunk/Translations/Identity/Path/To/Dir
-|-- 01-welcome.sed
-|-- 02-donate.sed
-|-- 03-docs.sed
-`-- 04-support.sed
-
-
-
One entry under `trunk/trunk/Scripts/Bash/Functions/Render/Config/':
-
-

In order to produce different translated images using specific design -templates, we need to specify the relation between translation files -and design templates in a way that `centos-art.sh' could know -exactly what translation file to apply to what design template. This -relation between translation files and design templates is set using -the matching list MATCHINGLIST variable inside the pre-rendition -configuration script of the component we want to produce images for. -

-
trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir
-`-- render.conf.sh
-
-

In this configuration the pre-rendition configuration script -(`render.conf.sh') would look like the following: -

-
function render_loadConfig {
-
-    # Define rendition actions.
-    ACTIONS[0]='BASE:renderImage'
-
-    # Define matching list.
-    MATCHINGLIST="\
-    paragraph.svg:\
-        01-welcome.sed\
-        02-donate.sed\
-        04-support.sed
-    list.svg:\
-        03-docs.sed
-    "
-
-}
-
-

As result, `centos-art.sh' will produce `01-welcome.png', -`02-donate.png' and `04-support.png' using the -paragraph-based design template, but `03-docs.png' using the -list-based design template. -

-
- - - -

3.55.1.4 Design template with translation (optimized+flexibility)

- -

In the production models we've seen so far, there are design templates -to produce untranslated images and translation files which combiend -with design templates produce translated images. That may seems like -all our needs are covered, doesn't it? Well, it almost does. -

-

Generally, we use design templates to define how final images will -look like. Generally, each renderable directory structure has one -`Tpl/' directory where we organize design templates for that -identity component. So, we can say that there is only one unique -design template definition for each identity component; or what is the -same, said differently, identity components can be produced in one way -only, the way its own design template directory specifies. This is -not enough for theme production. It is a limitation, indeed. -

-

Initially, to create one theme, we created one renderable directory -structure for each theme component. When we found ourselves with many -themes, and components inside them, it was obvious that the same -design model was duplicated inside each theme. As design models were -independently one another, if we changed one theme's design model, -that change was useless to other themes. So, in order to reuse design -model changes, we unified design models into one common directory -structure. -

-

With design models unified in a common structure, another problem rose -up. As design models also had the visual style of theme components, -there was no difference between themes, so there was no apparent need -to have an independent theme directory structure for each different -theme. So, it was also needed to separate visual styles from design -models. -

-

At this point there are two independent worklines: one directory -structure to store design models (the final image characteristics -[i.e., dimensions, translation markers, etc.]) and one directory -structure to store visual styles (the final image visual style [i.e., -the image look and feel]). So, it is possible to handle both -different design models and different visual styles independtly one -another and later create combinations among them using -`centos-art.sh'. -

-

For example, consider the following configuration: -

-
-
One entry under `trunk/Identity/Themes/Models/':
-
-

The design model entry exists to organize design model files (similar -to design templates). Both design models and design templates are very -similar; they both should have the CENTOSARTWORK export id -present to identify the exportation area, translation marks, etc. -However, design models do use dynamic backgrounds inclusion while -design templates don't. -

-
                        THEMEMODEL | | The bond component
-                             |<----| |--------------------->|
-trunk/Identity/Themes/Models/Default/Distro/Anaconda/Progress/
-|-- paragraph.svg
-`-- list.svg
-
-

Inisde design models, dynamic backgrounds are required in order for -different artistic motifs to reuse common design models. Firstly, in -order to create dynamic backgrounds inside design models, we import a -bitmap to cover design model's background and later, update design -model's path information to replace fixed values to dynamic values. -

-
-
One entry under `trunk/Identity/Themes/Motifs/':
-
-

The artistic motif entry defines the visual style we want to produce -images for, only. Final images (i.e., those built from combining both -design models and artistic motif backrounds) are not stored here, but -under branches directory structure. In the artistic motif entry, we -only define those images that cannot be produced automatically by -`centos-art.sh' (e.g., Backgrounds, Color information, -Screenshots, etc.). -

-
                  Artistic motif name | | Artistic motif backgrounds
-                             |<-------| |-------->|
-trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/
-|-- Img
-|   |-- Png
-|   |   |-- 510x300.png
-|   |   `-- 510x300-final.png
-|   `-- Jpg
-|       |-- 510x300.jpg
-|       `-- 510x300-final.jpg
-|-- Tpl
-|   `-- 510x300.svg
-`-- Xcf
-    `-- 510x300.xcf
-
-
-
One entry under `trunk/Translations/':
-
-

The translation entry specifies, by means of translation files, the -language-specific information we want to produce image for. When we -create the translation entry we don't use the name of neither design -model nor artistic motif, just the design model component we want to -produce images for. -

-
                                   | The bond component
-                                   |--------------------->|
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/
-`-- 5
-    |-- en
-    |   |-- 01-welcome.sed
-    |   |-- 02-donate.sed
-    |   `-- 03-docs.sed
-    `-- es
-        |-- 01-welcome.sed
-        |-- 02-donate.sed
-        `-- 03-docs.sed
-
-
-
One entry under `trunk/Scripts/Bash/Functions/Render/Config/':
-
-

There is one pre-rendition configuration script for each theme -component. So, each time a theme component is rendered, its -pre-rendition configuration script is evaluated to teach -`centos-art.sh' how to render the component. -

-
trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Distro/Anaconda/Progress/
-`-- render.conf.sh
-
-

In this configuration the pre-rendition configuration script -(`render.conf.sh') would look like the following: -

-
function render_loadConfig {
-
-    # Define rendition actions.
-    ACTIONS[0]='BASE:renderImage'
-
-    # Define matching list.
-    MATCHINGLIST="\
-    paragraph.svg:\
-        01-welcome.sed\
-        02-donate.sed
-    list.svg:\
-        03-docs.sed
-        "
-
-    # Deifne theme model.
-    THEMEMODEL='Default'
-
-}
-
-
- -

The production flow of "optimize+flexibility" configuration… -

- -

3.55.2 Renderable translation directory structures

- -

Translation directory structures are auxiliar structures of renderable -identity directory structures. There is one translation directory -structure for each renderable identity directory structure. Inside -translation directory structures we organize translation files used by -renderable identity directory structures that produce translated -images. Renderable identity directory structures that produce -untranslated images don't use translation files, but they do use a -translation directory structure, an empty translation directory -structure, to be precise. -

-

In order to aliviate production of translation file, we made -translation directory structures renderable adding a template -(`Tpl/') directory structure to handle common content inside -translation files. This way, we work on translation templates and -later use `centos-art.sh' to produce specific translation files -(based on translation templates) for different information (e.g., -languages, release numbers, architectures, etc.). -

-

If for some reason, translation files get far from translation -templates and translation templates become incovenient to produce such -translation files then, care should be taken to avoid replacing the -content of translation files with the content of translation templates -when `centos-art.sh' is executed to produce translation files -from translation templates. -

-

Inside renderable translation directory structures, -`centos-art.sh' can produce text-based files only. -

- - -

3.55.3 Copying renderable directory structures

- -

A renderable layout is formed by design models, design images, -pre-rendition configuration scripts and translations files. This way, -when we say to duplicate rendition stuff we are saying to duplicate -these four directory structures (i.e., design models, design images, -pre-rendition configuration scripts, and related translations files). -

-

When we duplicate directories, inside `trunk/Identity' directory -structure, we need to be aware of renderable layout described above -and the source location used to perform the duplication action. The -source location is relevant to centos-art.sh script in order to -determine the required auxiliar information inside directory -structures that need to be copied too (otherwise we may end up with -orphan directory structures unable to be rendered, due the absence of -required information). -

-

In order for a renderable directory structure to be valid, the new -directory structure copied should match the following conditions: -

-
    -
  1. To have a unique directory structure under -`trunk/Identity', organized by any one of the above -organizational designs above. - -
  2. To have a unique directory structure under -`trunk/Translations' to store translation files. - -
  3. To have a unique directory structure under -`trunk/Scripts/Bash/Functions/Render/Config' to set pre-rendition -configuration script. -
- -

As convenction, the render_doCopy function uses -`trunk/Identity' directory structure as source location. Once -the `trunk/Identity' directory structure has been specified and -verified, the related path information is built from it and copied -automatically to the new location specified by FLAG_TO variable. -

-

Design templates + No translation: -

-

Command: -- centos-art render -copy=trunk/Identity/Path/To/Dir -to=trunk/Identity/NewPath/To/Dir -

-

Sources: -- trunk/Identity/Path/To/Dir -- trunk/Translations/Identity/Path/To/Dir -- trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir -

-

Targets: -- trunk/Identity/NewPath/To/Dir -- trunk/Translations/Identity/NewPath/To/Dir -- trunk/Scripts/Bash/Functions/Render/Config/Identity/NewPath/To/Dir -

-

Renderable layout 2: -

-

Command: -- centos-art render -copy=trunk/Identity/Themes/Motifs/TreeFlower \ - -to=trunk/Identity/Themes/Motifs/NewPath/To/Dir -

-

Sources: -- trunk/Identity/Themes/Motifs/TreeFlower -- trunk/Translations/Identity/Themes -- trunk/Translations/Identity/Themes/Motifs/TreeFlower -- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes -- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/TreeFlower -

-

Targets: -- trunk/Identity/Themes/Motifs/NewPath/To/Dir -- trunk/Translations/Identity/Themes -- trunk/Translations/Identity/Themes/Motifs/NewPath/To/Dir -- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes -- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewPath/To/Dir -

-

Notice that design models are not included in source or target -locations. This is intentional. In "Renderable layout 2", design -models live by their own, they just exist, they are there, available -for any artistic motif to use. By default `Themes/Models/Default' -design model directory structure is used, but other design models -directory structures (under Themes/Models/) can be created and used -changing the value of THEMEMODEL variable inside the pre-rendition -configuration script of the artistic motif source location you want to -produce. -

-

Notice how translations and pre-rendition configuration scripts may -both be equal in source and target. This is because such structures -are common to all artistic motifs (the default values to use when no -specific values are provided). -

-

- The common directory structures are not copied or deleted. We cannot - copy a directory structure to itself. -

-

- The common directory structures represent the default value to use - when no specific translations and/or pre-rendition configuration - script are provided inside source location. -

-

- The specific directory structures, if present, are both copiable and - removable. This is, when you perform a copy or delete action from - source, that source specific auxiliar directories are transfered in - the copy action to a new location (that specified by FLAG_TO - variable). -

-

- When translations and/or pre-rendition configuration scripts are - found inside the source directory structure, the centos-art.sh - script loads common auxiliar directories first and later specific - auxiliar directories. This way, identity rendition of source - locations can be customized idividually over the base of common - default values. -

-

- The specific auxiliar directories are optional. -

-

- The common auxiliar directories should be present always. This is, - in order to provide the information required by render functionality - (i.e., to make it functional in the more basic level of its - existence). -

-

Notice how the duplication process is done from `trunk/Identity' on, -not the oposite. If you try to duplicate a translation structure (or -similar auxiliar directory structures like pre-rendition configuration -scripts), the `trunk/Identity' for that translation is not created. -This limitation is impossed by the fact that many `trunk/Identity' -directory structures may reuse/share the same translation directory -structure. We cannot delete one translation (or similar) directory -structures while a related `trunk/Identity/' directory structure is -still in need of it. -

-

The `render_doCopy' functionality does duplicate directory structures -directly involved in rendition process only. Once such directories -have been duplicated, the functionality stops thereat. -

- - -

3.55.4 Usage

- - - - - -

3.55.5 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_59.html b/Manuals/Filesystem/filesystem-html/filesystem_59.html deleted file mode 100644 index 21185a0..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_59.html +++ /dev/null @@ -1,287 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.56 trunk/Scripts/Bash/Cli/Functions/Render/Config - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.56 trunk/Scripts/Bash/Cli/Functions/Render/Config

- - - -

3.56.1 Goals

- -

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

- - -

3.56.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.56.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.56.2.2 The `render.conf.sh' translation model

- -

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

- - -

3.56.2.3 The `render.conf.sh' rendering actions

- -

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

-

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

-

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

-
ACTIONS[0]='BASE:renderImage'
-
-

Only one `BASE' action must be specified. If more than one -`BASE' action is specified, the last one is used. If no -`BASE' action is specified at all, an error is triggered and the -centos-art.sh script ends its execution. -

-

The `POST' action specifies which action to apply for -each file rendered (at the rendering time). This action is optional. -You can set many different `POST' actions to apply many different -actions over the same already rendered file. Possible values to -`POST' action are `renderFormats', `renderSyslinux', -`renderGrub', etc. -

-

To specify the `POST' action, you need to use set the -`POST:' followed by the function name of the action you want to -perform. The exact form depends on your needs. For example, consider -the following example to produce `xpm', `jpg', and -`tif' images, based on already rendered `png' image, and -also organize the produced files in directories named as their own -extensions: -

-
ACTIONS[0]='BASE:renderImage'
-ACTIONS[1]='POST:renderFormats: xpm jpg tif'
-ACTIONS[2]='POST:groupByFormat: png xpm jpg tif'
-
-

In the previous example, file organization takes place at the moment -of rendering, just after producing the `png' base file and before -going to the next file in the list of files to render. If you don't -want to organized the produced files in directories named as their own -extensions, just remove the `POST:groupByFormat' action line: -

-
ACTIONS[0]='BASE:renderImage'
-ACTIONS[1]='POST:renderFormats: xpm jpg tif'
-
-

The `LAST' action specifies which actions to apply once the last -file in the list of files to process has been rendered. The -`LAST' action is optional. Possible values for `LAST' -actions may be `groupByFormat', `renderGdmTgz', etc. -

-
info

Note

-- Removed(xref: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.56.3 Usage

- -

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

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

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

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

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

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

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

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

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

- - - -
3.47 trunk/Scripts/Bash   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_6.html b/Manuals/Filesystem/filesystem-html/filesystem_6.html deleted file mode 100644 index 9c940b7..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_6.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.3 trunk/Identity/Fonts - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.3 trunk/Identity/Fonts

- - - -

3.3.1 Goals

- -

This section exists to organize digital typographies used by the -CentOS project. -

- - -

3.3.2 Description

- - - -

3.3.3 Usage

- -

The CentOS corporate identity is attached to `DejaVu LGC' -font-family. Whatever artwork you design for CentOS project, that -requires typography usage, must be done using `DejaVu LGC' -font-family. -

-
-
Recommendation-1:
-
-

For screen desings (e.g., anything that final destination will never -be printed on paper or any medium outside computer screens) use -`DejaVu LGC Sans' font-family. -

-
-
Recommendation-2:
-
-

For non-screen designs (e.g., anything that final desition will be -printed on paper or any other medium outside computer screens) use -`DejaVu LGC Serif' font-family. As convenction files described in -this rule are stored under `Stationery' directories. -

-
- -

The only execption for the two recommendations above is the typography -used inside CentOS logo. The CentOS logo is the main visual -representation of the CentOS project so the typography used in it must -be the same always, no matter where it be shown. It also has to be -clear enough to dismiss any confussion between similar typefaces -(e.g., the number one (1) sometimes is confuesed with the letter -`el' (l) or letter `ai' (i)). -

-

As CentOS logo typography convenction, the word `CentOS' uses -`Denmark' typography as base, both for the word `CentOS' and -the phrase `Community Enterprise Operating System'. The phrase -size of CentOS logo is half the size in poits the word `CentOS' -has and it below `CentOS' word and aligned with it on the left. -The distance between `CentOS' word and phrase `Community -Enterprise Operating System' have the size in points the phrase has. -

-

When the CentOS release brand is built, use `Denmark' typography -for the release number. The release number size is two times larger -(in height) than default `CentOS' word. The separation between -release number and `CentOS' word is twice the size in points of -separation between `CentOS' word and phrase `Community -Enterprise Operating System'. -

-

Another component inside CentOS logo is the trademark symbol (TM). -This symbol specifies that the CentOS logo must be consider a product -brand, even it is not a registered one. The trademark symbol uses -DejaVu LGC Sans Regular typography. The trademark symbol is aligned -right-top on the outter side of `CentOS' word. The trademark -symbol must not exceed haf the distance, in points, between -`CentOS' word and the release number on its right. -

-

It would be very convenient for the CentOS Project and its community -to to make a registered trademark (®) of CentOS logo. To make a -register trademark of CentOS Logo prevents legal complications in the -market place of brands. It grants the consistency, through time, of -CentOS project corporate visual identity. -

-
info

Note

The information about trademarks and corporate identity -is my personal interpretation of -http://en.wikipedia.org/Corporate_identity and -http://en.wikipedia.org/Trademark description. If you have -practical experiences with these affairs, please serve yourself to -improve this section with your reasons. -

- - - -

3.3.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_60.html b/Manuals/Filesystem/filesystem-html/filesystem_60.html deleted file mode 100644 index e3425ad..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_60.html +++ /dev/null @@ -1,277 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.57 trunk/Scripts/Bash/Cli/Functions/Shell - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.57 trunk/Scripts/Bash/Cli/Functions/Shell

- - - -

3.57.1 Goals

- -

This section exists to organize files related to shell -functionality of `centos-art.sh' script. -

- - -

3.57.2 Description

- -

The shell functionality of `centos-art.sh' script helps -you to maintain bash scripts inside repository. For example, suppose -you've created many functionalities for `centos-art.sh' script, -and you want to use a common copyright and license note for -consistency in all your script files. If you have a bunch of files, -doing this one by one wouldn't be a big deal. In contrast, if the -amount of files grows, updating the copyright and license note for all -of them would be a task rather tedious. The shell functionality -exists to solve maintainance tasks just as the one previously -mentioned. -

-

When you use shell functionality to update copyright inside -script files, it is required that your script files contain (at least) -the following top commentary structure: -

-
-
 1| #!/bin/bash
- 2| #
- 3| # doSomething.sh -- The function description goes here.
- 4| # 
- 5| # Copyright
- 6| #
- 7| # ...
- 8| #
- 9| # ----------------------------------------------------------------------
-10| # $Id$
-11| # ----------------------------------------------------------------------
-12|
-13| function doSomething {
-14|     
-15| }
-
-

Figure 3.4: The functions script base comment structure - -

-

Relevant lines in the above structure are lines from 5 to 9. -Everything else in the file is left immutable. -

-

When you are updating copyright through shell -functionality, the `centos-art.sh' script replaces everything -in-between line 5 --the first one matching `^# Copyright .+$' -string-- and line 9--the first long dash separator matching `^# --+$'-- with the content of copyright template instance. -

-
Caution

Caution

Be sure to add the long dash separator that matches -`^# -+$' regular expression before the function -definition. Otherwise, if the `Copyright' line is present but no -long dash separator exists, `centos-art.sh' will remove anything -in-between the `Copyright' line and the end of file. This way you -may lost your function definitions entirely. -

- -

The copyright template instance is created from one copyright template -stored in the `Config/tpl_forCopyright.sed' file. The template -instance is created once, and later removed when no longer needed. At -this moment, when template instance is created, the -`centos-art.sh' script takes advantage of automation in order to -set copyright full name and date dynamically. -

-

When you use shell functionality to update copyright, the first -thing `shell' functionality does is requesting copyright -information to user, and later, if values were left empty (i.e., no -value was typed before pressing RET key), the `shell' -functionality uses its own default values. -

-

When shell functionality uses its own default values, the final -copyright note looks like the following: -

-
-
 1| #!/bin/bash
- 2| #
- 3| # doSomthing.sh -- The function description goes here.
- 4| #
- 5| # Copyright (C) 2003, 2010 The CentOS Project
- 6| # 
- 7| # This program is free software; you can redistribute it and/or modify
- 8| # it under the terms of the GNU General Public License as published by
- 9| # the Free Software Foundation; either version 2 of the License, or
-10| # (at your option) any later version.
-11| # 
-12| # This program is distributed in the hope that it will be useful, but
-13| # WITHOUT ANY WARRANTY; without even the implied warranty of
-14| # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
-15| # General Public License for more details.
-16| #
-17| # You should have received a copy of the GNU General Public License
-18| # along with this program; if not, write to the Free Software
-19| # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
-20| # USA.
-21| #
-22| # ----------------------------------------------------------------------
-23| # $Id$
-24| # ----------------------------------------------------------------------
-25|
-26| function doSomething {
-27|
-28| }
-
-

Figure 3.5: The function script comment example - -

-

Relevant lines in the above structure are lines from 5 to 22. Pay -attention how the copyright line was built, and how the license was -added into the top comment where previously was just three dots. -Everything else in the file was left immutable. -

-

To change copyright information (i.e., full name or year information), -run the shell functionality over the root directory containing -the script files you want to update copyright in and enter the -appropriate information when it be requested. You can run the -shell functionality as many times as you need to. -

-

To change copyright license (i.e., the text in-between lines 7 and -20), you need to edit the `Config/tpl_forCopyright.sed' file, set -the appropriate information, and run the shell functionality -once again for changes to take effect over the files you specify. -

-
Important

Important

The `centos-art.sh' script is released as: -

-
GNU GENERAL PUBLIC LICENSE
-Version 2, June 1991
-
-Copyright (C) 1989, 1991 Free Software Foundation, Inc.
-59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
-
-

Do not change the license information under which `centos-art.sh' -script is released. Instead, if you think a different license must be -used, please share your reasons at CentOS Developers mailing list. -

- - - -

3.57.3 Usage

- -
-
centos-art sh --update-copyright='path/to/dir'
-
centos-art sh --update-copyright='path/to/dir' --filter='regex'
-

Use these commands to update copyright information in `.sh' files -under `path/to/dir' directory. -

-
- -

When you provide `--filter='regex'' argument, the list of files -to process is reduced as specified in `regex' regular expression. -Inside `centos-art.sh' script, the `regex' regular -expression is used in combination with find command to look -for files matching the regular expression path pattern. -

-
Warning

Warning

In order for `regex' regular expression to match -a file, the `regex' regular expresion must match the whole file -path not just the file name. -

- -

For example, if you want to match all `render.conf.sh' files -inside `path/to/dir', use the .+/render.conf regular -expression. Later, `centos-art.sh' script uses this value inside -^$REGEX\.sh$ expression in order to build the final regular -expression (i.e., ^.+/render.conf\.sh$) that is evaluated -against available file paths inside the list of files to process. -

-

Exceptionally, when you provide `--filter='regex'' in the way -that `regex', appended to `path/to/dir/' (i.e. -`path/to/dir/regex'), matches a regular file; the -`centos-art.sh' script uses the file matching as only file in the -list of files to process. -

- - -

3.57.4 See also

- - - -
3.47 trunk/Scripts/Bash   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_61.html b/Manuals/Filesystem/filesystem-html/filesystem_61.html deleted file mode 100644 index 10c9a6d..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_61.html +++ /dev/null @@ -1,309 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.58 trunk/Scripts/Bash/Cli/Functions/Svg - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.58 trunk/Scripts/Bash/Cli/Functions/Svg

- - - -

3.58.1 Goals

- -

This section exists to organize files related to svg -functionality of `centos-art.sh' script. -

- - -

3.58.2 Description

- -

The svg functionality of `centos-art.sh' script helps you -to maintain scalable vector graphics (SVG) inside repository. For -example, suppose you've been working in CentOS default design models -under `trunk/Identity/Themes/Models/', and you want to set common -metadata to all of them, and later remove all unused SVG defintions -from `*.svg' files. Doing so file by file may be a tedious task, -so the `centos-art.sh' script provides the svg -functionality to aid you maintain such actions. -

- - - -

3.58.2.1 Metadata maintainance

- -

The metadata used is defined by Inkscape 0.46 using the SVG standard -markup. The `centos-art.sh' script replaces everything -in-between <metadata and </metadata> tags with a -predefined metadata template we've set for this purpose. -

-

The metadata template was created using the metadata information of a -file which, using Inkscape 0.46, all metadata fields were set. This -created a complete markup representation of how SVG metadata would -look like. Later, we replaced every single static value with a -translation marker in the form `=SOMETEXT=', where -SOMETEXT is the name of its main opening tag. Later, we -transform the metadata template into a sed replacement set of commads -escaping new lines at the end of each line. -

-

With metadata template in place, the `centos-art.sh' script uses -it to create a metadata template instance for the file being processed -currently. The metadata template instance contains the metadata -portion of sed replacement commands with translation markers already -traduced. In this action, instance creation, is where we take -advantage of automation and generate metadata values like title, date, -keywords, source, identifier, and relation dynamically, based on the -file path `centos-art.sh' script is currently creating metadata -information for. -

-

With metadata template instance in place, the `centos-art.sh' -script uses it to replace real values inside all `.svg' files -under the current location you're running the `centos-art.sh' -script on. Default behaviour is to ask user to enter each metadatum -required, one by one. If user leaves metadatum empty, by pressing -RET key, `centos-art.sh' uses its default value. -

-

The `centos-art.sh' script modifies the following metadata: -

-
-
`Title'
-

Name by which this document is formally known. If no value is set -here, `centos-art.sh' script uses the file name as title. -

-
-
`Date'
-

Date associated with the creation of this document (YYYY-MM-DD). If no -value is set here, `centos-art.sh' script uses the current date -information as in date +%Y-%m-%d. -

-
-
`Creator'
-

Name of entity primarily responsible for making the content of this -document. If no value is set here, `centos-art.sh' script uses -the string `The CentOS Project'. -

-
-
`Rights'
-

Name of entity with rights to the intellectual Property of this -document. If no value is set here, `centos-art.sh' script uses -the string `The CentOS Project'. -

-
-
`Publisher'
-

Name of entity responsible for making this document available. If no -value is set here, `centos-art.sh' script uses the string -`The CentOS Project'. -

-
-
`Identifier'
-

Unique URI to reference this document. If no value is set here, -`centos-art.sh' script uses the current file path to build the -related url that points to current file location inside repository -central server. -

-
-
`Source'
-

Unique URI to reference the source of this document. If no value is -set here, `centos-art.sh' script uses current file path to build -the related url that points to current file location inside repository -central server. -

-
-
`Relation'
-

Unique URI to a related document. If no value is set here, -`centos-art.sh' script uses current file path to build the -related url that points to current file location inside repository -central server. -

-
-
`Language'
-

Two-letter language tag with optional subtags for the language of this -document. (e.g. `en-GB'). If no value is set here, -`centos-art.sh' script uses the current locale information as in -cli_getCurrentLocale function. -

-
-
`Keywords'
-

The topic of this document as comma-separated key words, prhases, or -classifications. If no value is set here, `centos-art.sh' script -uses file path to build -

-
-
`Coverage'
-

Extent or scope of this document. If no value is set here, -`centos-art.sh' script uses the string `The CentOS Project'. -

-
-
`Description'
-

Description about the document. If no value is set here, -`centos-art.sh' script uses uses empty value as default. -

-
-
`Contributors'
-

People that contributes in the creation/maintainance of the document. -If no value is set here, `centos-art.sh' script uses uses empty -value as default. -

-
- -

The `License' metadatum is not set as a choise, by now. It is -fixed Creative Common Attribution Share-Alike 3.0 License. This is done in order to -grant license consistency among all SVG files we manage inside CentOS -Artwork Repository. -

- - - -

3.58.2.2 Unused definitions

- -

Many of the no-longer-used gradients, patterns, and markers (more -precisely, those which you edited manually) remain in the -corresponding palettes and can be reused for new objects. However if -you want to optimize your document, use the `Vacuum Defs' command -in `File' menu. It will remove any gradients, patterns, or -markers which are not used by anything in the document, making the -file smaller. -

-

If you have one or two couple of files, removing unused definitions -using the graphical interface may be enough to you. In contrast, if -you have dozens or even houndreds of scalable vector graphics files to -maintain it is not a fun task to use the graphical interface to remove -unused definitions editing those files one by one. -

-

To remove unused definitions from several scalable vector graphics -files, the `centos-art.sh' script uses Inkscape command-line -interface, specifically with the `--vaccum-defs' option. -

- - -

3.58.3 Usage

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

Use these commands to update metadata information to `.svg' files -under `path/to/dir' directory. -

-
-
centos-art svg --vacuum-defs='path/to/dir'
-
centos-art svg --vacuum-defs='path/to/dir' --filter='regex'
-

Use these commands to remove unused definitions inside `.svg' -files under `path/to/dir' directory. -

-
- -

When you provide `--filter='regex'' argument, the list of files -to process is reduced as specified in `regex' regular expression. -Inside `centos-art.sh' script, the `regex' regular -expression is used in combination with find command to look -for files matching the regular expression path pattern. -

-
Warning

Warning

In order for `regex' regular expression to match -a file, the `regex' regular expresion must match the whole file -path not just the file name. -

- -

For example, if you want to match all `summary.svg' files inside -`path/to/dir', use the .+/summary regular expression. -Later, `centos-art.sh' script uses this value inside -^$REGEX\.svg$ expression in order to build the final regular -expression (i.e., ^.+/summary\.svg$) that is evaluated against -available file paths inside the list of files to process. -

-

Exceptionally, when you provide `--filter='regex'' in the way -that `regex', appended to `path/to/dir/' (i.e. -`path/to/dir/regex'), matches a regular file; the -`centos-art.sh' script uses the file matching as only file in the -list of files to process. -

- - -

3.58.4 See also

- - - -
3.47 trunk/Scripts/Bash   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_62.html b/Manuals/Filesystem/filesystem-html/filesystem_62.html deleted file mode 100644 index 7f832b4..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_62.html +++ /dev/null @@ -1,356 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.59 trunk/Scripts/Bash/Cli/Functions/Verify - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.59 trunk/Scripts/Bash/Cli/Functions/Verify

- - - -

3.59.1 Goals

- -

This section exists to organize files related to `centos-art.sh' -script `verify' functionality. The `verify' -functionality of `centos-art.sh' script helps you to verify the -workstation configuration you are planning to use as host for your -working copy of CentOS Artwork Repository. -

- - -

3.59.2 Description

- -

The first time you download CentOS Artwork Repository you need to -configure your workstation in order to use `centos-art.sh' -script. These preliminar configurations are based mainly on auxiliar -RPM packages installation, symbolic links creations, and environment -variables definitions. The `verify' functionality of -`centos-art.sh' script guides you through this preliminar -configuration process. -

-

If this is the first time you run `centos-art.sh' script, the -appropriate way to use its `verify' functionality is not using -the `centos-art.sh' script directly, but the absolute path to -centos-art.sh script instead (i.e., -`~/artwork/trunk/Scripts/Bash/centos-art.sh'). This is necessary -because `centos-art' symbolic link, under `~/bin/' -directory, has not been created yet. -

- - -

3.59.2.1 Packages

- -

Installation of auxiliar RPM packages provides the software required -to manipulate files inside the repository (e.g., image files, -documentation files, translation files, script files, etc.). Most of -RPM packages centos-art.sh script uses are shipped with -CentOS distribution, and can be installed from CentOS base repository. -The only exception is `inkscape', the package we use to -manipulate SVG files. The `inkscape' package is not inside -CentOS distribution so it needs to be installed from third party -repositories. -

-
info

Note

Configuration of third party repositories inside CentOS -distribution is described in CentOS wiki, specifically in the -following URL: -http://wiki.centos.org/AdditionalResources/Repositories -

- -

Before installing packages, the `centos-art.sh' script uses -sudo to request root privileges to execute yum -installation functionality. If your user isn't defined as a -privileged user--at least to run yum commands-- inside -`/etc/sudoers' configuration file, you will not be able to -perform package installation tasks as set in `centos-art.sh' -script `verify' functionality. -

-

Setting sudo privileges to users is an administrative task you have to -do by yourself. If you don't have experience with sudo -command, please read its man page running the command: man -sudo. This reading will be very useful, and with some practice, you -will be able to configure your users to have sudo -privileges. -

- - -

3.59.2.2 Links

- -

Creation of symbolic links helps us to alternate between different -implementations of `centos-art.sh' script-line (e.g., -`centos-art.sh', for Bash implementation; `centos-art.py', -for Python implementation; `centos-art.pl', for Perl -implementation; and so on for other implementations). The -`centos-art.sh' script-line definition takes place inside your -personal binary (`~/bin/') directory in order to make the script -implementation --the one that `centos-art' links to-- available -to PATH environment variable. -

-

Creation of symbolic links helps us to reuse components from repository -working copy. For example, color information files maintained inside -your working copy must never be duplicated inside program-specific -configuration directories that uses them in your workstation (e.g., -Gimp, Inkscape, etc.). Instead, a symbolic link must be created for -each one of them, from program-specific configuration directories to -files in the working copy. In this configuration, when someone -commits changes to color information files up to central repository, -they--the changes committed-- will be immediatly available to your -programs the next time you update your working copy --the place -inside your workstation those color information files are stored--. -

-

Creation of symbolic links helps us to make `centos-art.sh' -script functionalities available outside `trunk/' repository -directory structure, but at its same level in repository tree. This is -useful if you need to use the "render" functionality of -centos-art.sh under `branches/' repository directory -structure as you usually do inside `trunk/' repository directory -structure. As consequence of this configuration, automation scripts -cannot be branched under `branches/Scripts' directory structure. -

- - -

3.59.2.3 Environment variables

- -

Definition of environemnt variables helps us to set default values to -our user session life. The user session environment variable defintion -takes place in the user's `~/.bash_profile' file. The -`verify' functionality of `centos-art.sh' script doesn't -modify your `~/.bash_profile' file. -

-

The `verify' functionality of `centos-art.sh' script -evaluates the following environment variables: -

-
-
EDITOR
-

Default text editor. -

-

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

-

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

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

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

-
-
TEXTDOMAIN
-
-

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

-
-
TEXTDOMAINDIR
-
-

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

-
-
LANG
-
-

Default locale information. -

-

This variable is initially set in the configuration process of CentOS -distribution installer (i.e., Anaconda), specifically in the -`Language' step; or once installed using the -system-config-language tool. -

-

The `centos-art.sh' script uses the LANG environment -variable to know in which language the script messages are printed -out. -

-
-
TZ
-
-

Default time zone representation. -

-

This variable is initially set in the configuration process of CentOS -distribution installer (i.e., Anaconda), specifically in the -`Date and time' step; or once installed using the -system-config-date tool. -

-

The `centos-art.sh' script doesn't use the TZ environment -variable information at all. Instead, this variable is used by the -system shell to show the time information according to your phisical -location on planet Earth. -

-

Inside your computer, the time information is firstly set in the BIOS -clock (which may need correction), and later in the configuration -process of CentOS distribution installer (or later, by any of the -related configuration tools inside CentOS distribution). Generally, -setting time information is a straight-forward task and configuration -tools available do cover most relevant location. However, if you need -a time precision not provided by the configuration tools available -inside CentOS distribution then, using TZ variable may be -necessary. -

-
Convenction

Convenction

In order to keep changes syncronized between -central repository and its working copies: configure both repository -server and workstations (i.e., the place where each working copy is -set on) to use Coordinated Universal Time (UTC) as base time -representation. Later, correct the time information for your specific -location using time zone correction. -

- -

The format of TZ environment variable is described in -`tzset(3)' manual page. -

-
-
- - - -

3.59.3 Usage

- -
-
centos-art verify --packages
-
-

Verify required packages your workstation needs in order to run the -`centos-art.sh' script correctly. If there are missing packages, -the `centos-art.sh' script asks you to confirm their -installation. When installing packages, the `centos-art.sh' -script uses the yum application in order to achieve the -task. -

-

In case all packages required by `centos-art.sh' script are -already installed in your workstation, the message `The required -packages are already installed.' is output for you to know. -

-
-
centos-art verify --links
-
-

Verify required links your workstation needs in order to run the -centos-art command correctly. If any required link is missing, the -centos-art.sh script asks you to confirm their installation. -To install required links, the centos-art.sh script uses the -ln command. -

-

In case all links required by `centos-art.sh' script are already -created in your workstation, the message `The required links are -already installed.' is output for you to know. -

-

In case a regular file exists with the same name of a required link, -the `centos-art.sh' script outputs the `Already exists as -regular file.' message when listing required links that will be -installed. Of course, as there is already a regular file where must be -a link, no link is created. In such cases the `centos-art.sh' -script will fall into a continue installation request for that missing -link. To end this continue request you can answer `No', or -remove the existent regular file to let `centos-art.sh' script -install the link on its place. -

-
-
centos-art verify --environment
-
centos-art verify --environment --filter='regex'
-
-

Output a brief description of environment variables used by -`centos-art.sh' script. -

-

If `--filter' option is provided, output is reduced as defined in -the `regex' regular expression value. If `--filter' option -is specified but `regex' value is not, the `centos-art.sh' -script outputs information as if `--filter' option had not been -provided at all. -

-
-
- - - -

3.59.4 See also

- - - -
3.47 trunk/Scripts/Bash   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_63.html b/Manuals/Filesystem/filesystem-html/filesystem_63.html deleted file mode 100644 index ed7e391..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_63.html +++ /dev/null @@ -1,123 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.60 trunk/Scripts/Python - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.60 trunk/Scripts/Python

- - - -

3.60.1 Goals

- - - - - -

3.60.2 Description

- - - - - -

3.60.3 Usage

- - - - - -

3.60.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_64.html b/Manuals/Filesystem/filesystem-html/filesystem_64.html deleted file mode 100644 index 96bed8d..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_64.html +++ /dev/null @@ -1,196 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: Index - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

Index

-
Jump to:   B -   -H -   -M -   -T -   -U -   -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Index Entry Section
B
branches1. branches
H
How to render brands' translation files3.36.3 Usage
How to render fonts' translation files3.38.3 Usage
M
Metadata maintainance3.58.2 Description
T
tags2. tags
Translation brands file names3.36.2.1 Conventional file names
Translation brands file names3.36.2.2 Numeric file names
trunk3. trunk
trunk Identity3.1 trunk/Identity
trunk Identity Brands3.2 trunk/Identity/Brands
trunk Identity Fonts3.3 trunk/Identity/Fonts
trunk Identity Icons3.4 trunk/Identity/Icons
trunk Identity Isolinux3.5 trunk/Identity/Isolinux
trunk Identity Models3.6 trunk/Identity/Models
trunk Identity Models Css3.7 trunk/Identity/Models/Css
trunk Identity Models Html3.8 trunk/Identity/Models/Html
trunk Identity Models Img Promo Web3.9 trunk/Identity/Models/Img/Promo/Web
trunk Identity Models Tpl3.10 trunk/Identity/Models/Tpl
trunk Identity Models Tpl Promo Web3.11 trunk/Identity/Models/Tpl/Promo/Web
trunk Identity Models Xcf3.12 trunk/Identity/Models/Xcf
trunk Identity Release3.13 trunk/Identity/Release
trunk Identity Themes3.14 trunk/Identity/Themes
trunk Identity Themes Models3.15 trunk/Identity/Themes/Models
trunk Identity Themes Models Alternative3.16 trunk/Identity/Themes/Models/Alternative
trunk Identity Themes Models Default3.17 trunk/Identity/Themes/Models/Default
trunk Identity Themes Models Default Distro3.18 trunk/Identity/Themes/Models/Default/Distro
trunk Identity Themes Models Default Distro Anaconda3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda
trunk Identity Themes Models Default Promo3.20 trunk/Identity/Themes/Models/Default/Promo
trunk Identity Themes Models Default Web3.21 trunk/Identity/Themes/Models/Default/Web
trunk Identity Themes Motifs3.22 trunk/Identity/Themes/Motifs
trunk Identity Themes Motifs Flame3.23 trunk/Identity/Themes/Motifs/Flame
trunk Identity Themes Motifs Modern3.24 trunk/Identity/Themes/Motifs/Modern
trunk Identity Themes Motifs Modern Backgrounds3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds
trunk Identity Themes Motifs Modern Backgrounds Img3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img
trunk Identity Themes Motifs Modern Backgrounds Tpl3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl
trunk Identity Themes Motifs Modern Backgrounds Xcf3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf
trunk Identity Themes Motifs Modern Distro Anaconda Progress3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
trunk Identity Themes Motifs Modern Palettes3.30 trunk/Identity/Themes/Motifs/Modern/Palettes
trunk Identity Themes Motifs TreeFlower3.31 trunk/Identity/Themes/Motifs/TreeFlower
trunk Identity Themes Motifs TreeFlower Backgrounds3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds
trunk Identity Widgets3.33 trunk/Identity/Widgets
trunk Locales3.34 trunk/Locales
trunk Locales Identity3.35 trunk/Locales/Identity
trunk Locales Identity Brands3.36 trunk/Locales/Identity/Brands
trunk Locales Identity Brands Tpl3.37 trunk/Locales/Identity/Brands/Tpl
trunk Locales Identity Fonts3.38 trunk/Locales/Identity/Fonts
trunk Locales Identity Models3.39 trunk/Locales/Identity/Models
trunk Locales Identity Release3.40 trunk/Locales/Identity/Release
trunk Locales Identity Themes3.41 trunk/Locales/Identity/Themes
trunk Locales Identity Themes Backgrounds3.42 trunk/Locales/Identity/Themes/Backgrounds
trunk Locales Identity Themes Distro Anaconda Progress3.43 trunk/Locales/Identity/Themes/Distro/Anaconda/Progress
trunk Locales Identity Widgets3.44 trunk/Locales/Identity/Widgets
trunk Manuals3.45 trunk/Manuals
trunk Scripts3.46 trunk/Scripts
trunk Scripts Bash3.47 trunk/Scripts/Bash
trunk Scripts Bash Cli3.48 trunk/Scripts/Bash/Cli
trunk Scripts Bash Cli Functions3.49 trunk/Scripts/Bash/Cli/Functions
trunk Scripts Bash Cli Functions Help3.50 trunk/Scripts/Bash/Cli/Functions/Help
trunk Scripts Bash Cli Functions Html3.51 trunk/Scripts/Bash/Cli/Functions/Html
trunk Scripts Bash Cli Functions Locale3.52 trunk/Scripts/Bash/Cli/Functions/Locale
trunk Scripts Bash Cli Functions Manual3.53 trunk/Scripts/Bash/Cli/Functions/Manual
trunk Scripts Bash Cli Functions Path3.54 trunk/Scripts/Bash/Cli/Functions/Path
trunk Scripts Bash Cli Functions Render3.55 trunk/Scripts/Bash/Cli/Functions/Render
trunk Scripts Bash Cli Functions Render Config3.56 trunk/Scripts/Bash/Cli/Functions/Render/Config
trunk Scripts Bash Cli Functions Shell3.57 trunk/Scripts/Bash/Cli/Functions/Shell
trunk Scripts Bash Cli Functions Svg3.58 trunk/Scripts/Bash/Cli/Functions/Svg
trunk Scripts Bash Cli Functions Verify3.59 trunk/Scripts/Bash/Cli/Functions/Verify
trunk Scripts Python3.60 trunk/Scripts/Python
U
Unused definitions3.58.2.1 Metadata maintainance
-
Jump to:   B -   -H -   -M -   -T -   -U -   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_65.html b/Manuals/Filesystem/filesystem-html/filesystem_65.html deleted file mode 100644 index 06499ed..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_65.html +++ /dev/null @@ -1,103 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: List of Figures - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

List of Figures

-
-
Figure 3.1

The functionalities initialization environment. -

-
Figure 3.2

The actions initialization environment. -

-
Figure 3.3

The cli_commitRepoChanges function output. -

-
Figure 3.4

The functions script base comment structure -

-
Figure 3.5

The function script comment example -

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_66.html b/Manuals/Filesystem/filesystem-html/filesystem_66.html deleted file mode 100644 index 8f7f279..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_66.html +++ /dev/null @@ -1,103 +0,0 @@ - - - - - - -CentOS Artwork Repository - Filesystem: List of Figures - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

List of Figures

-
-
Figure 3.1

The functionalities initialization environment. -

-
Figure 3.2

The actions initialization environment. -

-
Figure 3.3

The cli_commitRepoChanges function output. -

-
Figure 3.4

The functions script base comment structure -

-
Figure 3.5

The function script comment example -

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

- - This document was generated on February, 28 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_67.html b/Manuals/Filesystem/filesystem-html/filesystem_67.html deleted file mode 100644 index 35705dd..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_67.html +++ /dev/null @@ -1,103 +0,0 @@ - - - - - - -CentOS Artwork Repository - Filesystem: List of Figures - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

List of Figures

-
-
Figure 3.1

The functionalities initialization environment. -

-
Figure 3.2

The actions initialization environment. -

-
Figure 3.3

The cli_commitRepoChanges function output. -

-
Figure 3.4

The functions script base comment structure -

-
Figure 3.5

The function script comment example -

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

- - This document was generated on February, 28 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_7.html b/Manuals/Filesystem/filesystem-html/filesystem_7.html deleted file mode 100644 index 50e776a..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_7.html +++ /dev/null @@ -1,112 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.4 trunk/Identity/Icons - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.4 trunk/Identity/Icons

- - - -

3.4.1 Goals

- - - - - -

3.4.2 Description

- - - -

3.4.3 Usage

- - - -

3.4.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_8.html b/Manuals/Filesystem/filesystem-html/filesystem_8.html deleted file mode 100644 index ec115b2..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_8.html +++ /dev/null @@ -1,112 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.5 trunk/Identity/Isolinux - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.5 trunk/Identity/Isolinux

- - - -

3.5.1 Goals

- - - - - -

3.5.2 Description

- - - -

3.5.3 Usage

- - - -

3.5.4 See also

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

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_9.html b/Manuals/Filesystem/filesystem-html/filesystem_9.html deleted file mode 100644 index 2d21314..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_9.html +++ /dev/null @@ -1,123 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: 3.6 trunk/Identity/Models - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
- - -

3.6 trunk/Identity/Models

- - - -

3.6.1 Goals

- -

This section exists to organize design models. -

- - -

3.6.2 Description

- -

Design models are representative designs useful to understand how -to build artworks. -

- - -

3.6.3 Usage

- - - -

3.6.4 See also

- - - - - - -
3.8 trunk/Identity/Models/Html   -
3.7 trunk/Identity/Models/Css   -
3.10 trunk/Identity/Models/Tpl   -
3.12 trunk/Identity/Models/Xcf   -
- - - - - - - - - -
[ < ][ > ]   [ << ][ Up ][ >> ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_abt.html b/Manuals/Filesystem/filesystem-html/filesystem_abt.html deleted file mode 100644 index a6c2ab8..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_abt.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: About This Document - - - - - - - - - - - - - - - - - - - - -
[Top][Contents][Index][ ? ]
-

About This Document

-

- This document was generated on March, 1 2011 using texi2html 1.76. -

-

- The buttons in the navigation panels have the following meaning: -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Button Name Go to From 1.2.3 go to
[ < ] Backprevious section in reading order1.2.2
[ > ] Forwardnext section in reading order1.2.4
[ << ] FastBackbeginning of this chapter or previous chapter1
[ Up ] Upup section1.2
[ >> ] FastForwardnext chapter2
[Top] Topcover (top) of document  
[Contents] Contentstable of contents  
[Index] Indexindex  
[ ? ] Aboutabout (help)  
- -

- where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure: -

- - - - - - - - - -
[Top][Contents][Index][ ? ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_fot.html b/Manuals/Filesystem/filesystem-html/filesystem_fot.html deleted file mode 100644 index d2d8b3e..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_fot.html +++ /dev/null @@ -1,80 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: Footnotes - - - - - - - - - - - - - - - - - - - - -
[Top][Contents][Index][ ? ]
-

Footnotes

-

(1)

-

The theme support of Mailman may be introduced in -mailman-3.x.x release. -

- - - - - -
[Top][Contents][Index][ ? ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-html/filesystem_toc.html b/Manuals/Filesystem/filesystem-html/filesystem_toc.html deleted file mode 100644 index f3cebbf..0000000 --- a/Manuals/Filesystem/filesystem-html/filesystem_toc.html +++ /dev/null @@ -1,573 +0,0 @@ - - - - - - -CentOS Artwork Repository - File System: Table of Contents - - - - - - - - - - - - - - - - - - - - -
[Top][Contents][Index][ ? ]
-

Table of Contents

-
- - -
- - - - - - -
[Top][Contents][Index][ ? ]
-

- - This document was generated on March, 1 2011 using texi2html 1.76. - -
- -

- - diff --git a/Manuals/Filesystem/filesystem-index.texi b/Manuals/Filesystem/filesystem-index.texi deleted file mode 100644 index a6413a5..0000000 --- a/Manuals/Filesystem/filesystem-index.texi +++ /dev/null @@ -1,9 +0,0 @@ -@node Index -@unnumbered Index -@printindex cp - -@node List of Figures -@unnumbered List of Figures -@ifnotinfo -@listoffloats Figure -@end ifnotinfo diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/community.tex b/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/community.tex deleted file mode 100644 index 34d8eff..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/community.tex +++ /dev/null @@ -1,23 +0,0 @@ -% ------------------------------------------------------------ -% $Id: community.tex 6024 2010-06-28 04:28:27Z al $ -% ------------------------------------------------------------ - \section{The CentOS Community} -\hypertarget{sec:Concepts:CentOS:Community}{} - \label{sec:Concepts:CentOS:Community} - -The CentOS Project is designed for people who need an enterprise class -operating system without the cost or support of the prominent North -American Enterprise Linux vendor. - -\begin{description} - -\item[CentOS Administrators:] People building CentOS Distribution and -its infrastructure are considered CentOS Administrators. Each CentOS -Distribution has an Administrator Leader. - -\item[CentOS Community Members:] People using CentOS Distribution are -concidered CentOS Community Members. Inside CentOS Community, Members -affiliate Special Interest Groups (SIGs). Special Interest Groups help -to organize and distribute work inside The CentOS Project. - -\end{description} diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/distribution.tex b/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/distribution.tex deleted file mode 100644 index bdf41ed..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/distribution.tex +++ /dev/null @@ -1,30 +0,0 @@ -% ------------------------------------------------------------ -% $Id: distribution.tex 6024 2010-06-28 04:28:27Z al $ -% ------------------------------------------------------------ - \section{The CentOS Distribution} -\hypertarget{sec:Concepts:CentOS:Distribution}{} - \label{sec:Concepts:CentOS:Distribution} - -The CentOS Distribution is a free enterprise class computing platform -to anyone who wishes to use it. The CentOS Distribution is built from -publicly available open source SRPMS provided by a prominent North -American Enterprise Linux vendor. The CentOS Distribution conforms -fully with the upstream vendors redistribution policies and aims to be -100\% binary compatible (The CentOS Project mainly changes packages to -remove upstream vendor branding and artwork.). - -The CentOS Project releases its CentOS Distribution as a GPL work. The -GPL applies to the software collection known as the CentOS -Distribution. Individual packages included in the distribution -include their own licenses and the GPL applies to all packages that it -does not clash with. If there is a clash between the GPL and -individual package licenses, the individual package license applies -instead. - -Neither the CentOS Project (we who build CentOS Distribution) nor any -version of CentOS Distribution is affiliated with, produced by, or -supported by the prominent North American Enterprise Linux vendor. -Neither does our software contain the upstream vendor's product \dots -although it is built from the same open source SRPMS as the upstream -enterprise products. - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/incorporation.tex b/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/incorporation.tex deleted file mode 100644 index 3cf5003..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/incorporation.tex +++ /dev/null @@ -1,6 +0,0 @@ - -\section{The CentOS Incorporation} - -The CentOS Project is a legal entity separate from the persons who own -it or the persons who manage or operate it. - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/introduction.tex b/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/introduction.tex deleted file mode 100644 index 0bbe3ef..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/introduction.tex +++ /dev/null @@ -1,8 +0,0 @@ - -This chapter describes the CentOS Project as legal entity. It -describes how the incorporation would survive longer than the lives of -any particular member, existing in perpetuity. Information in this -chapter provides the emotional tools that CentOS Community needs, in -order to create a strong feeling of identification with the CentOS -Project and its mission. - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/mission.tex b/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/mission.tex deleted file mode 100644 index c3dd2bf..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/mission.tex +++ /dev/null @@ -1,9 +0,0 @@ -% ------------------------------------------------------------ -% $Id: mission.tex 6024 2010-06-28 04:28:27Z al $ -% ------------------------------------------------------------ - \section{The CentOS Mission} -\hypertarget{sec:Concepts:CentOS:Mission}{} - \label{sec:Concepts:CentOS:Mission} - -The CentOS Project exists to provide the CentOS Distribution. - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/organization.tex b/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/organization.tex deleted file mode 100644 index 08c9ec6..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/organization.tex +++ /dev/null @@ -1,12 +0,0 @@ - -\section{The CentOS Organization} - -The CentOS Project is organized and managed on Internet by a group of -Administrators which provide their knowledge and personal resources to -build the different major releases of CentOS Distribution and maintain -the required infrastructure. - -The CentOS Project exists by its own, it is not affilieted with any -other organization. The only source of hardware or funding to -distribute the CentOS Distribution is by donations. - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/philosophy.tex b/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/philosophy.tex deleted file mode 100644 index 0110ad4..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/philosophy.tex +++ /dev/null @@ -1,5 +0,0 @@ - -\section{The CentOS Philosophy} - -The CentOS Project is higly based on meritocracy. - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/release.tex b/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/release.tex deleted file mode 100644 index 2ce9409..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/CentOS/release.tex +++ /dev/null @@ -1,46 +0,0 @@ -% ------------------------------------------------------------ -% $Id: release.tex 6024 2010-06-28 04:28:27Z al $ -% ------------------------------------------------------------ - \section{The CentOS Release Schema} -\hypertarget{sec:Concepts:CentOS:Release}{} - \label{sec:Concepts:CentOS:Release} - -The upstream vendor has released 4 versions of enterprise Linux that -CentOS rebuilds the freely available SRPMS for. So, the major CentOS -releases are CentOS 2, CentOS 3, CentOS 4 and CentOS 5. The upstream -vendor releases security updates as required by circumstances. CentOS -releases rebuilds of security updates as soon as possible. Usually -within 24 hours (our stated goal is with 72 hours, but we are usually -much faster). - -The upstream vendor also releases numbered update sets for Version 3, -Version 4 and Version 5 of their product (Currently EL 3 update 9, EL -4 update 6 and EL 5 update 1) 2 to 4 times per year. There are new -ISOs from the upstream vendor provided for these update sets. Update -sets will be completed as soon as possible after the vendor releases -their version ... generally within 2 weeks. CentOS follows these -conventions as well, so CentOS 3.9 correlates with EL 3 update 9 and -CentOS 4.6 correlates with EL 4 update 6, CentOS 5.1 correlates to EL -5 update 1, etc. - -One thing some people have problems understanding is that if you have -any CentOS-3 product and update it, you will be updated to the latest -CentOS-3.x version. - -The same is true for CentOS-4 and CentOS 5. If you update any CentOS-4 -product, you will be updated to the latest CentOS-4.x version, or to -the latest CentOS 5.x version if you are updating a CentOS 5 system. -This is exactly the same behavior as the upstream product. Let's -assume that the latest EL4 product is update 6. If you install the -upstream original EL4 CDs (the ones before any update set) and upgrade -via their up2date, you will have latest update set installed (EL4 -update 6 in our example). Since all updates within a major release -(CentOS 2, CentOS 3, CentOS 4, CentOS 5) always upgrade to the latest -version when updates are performed (thus mimicking upstream behavior), -only the latest version is maintained in each main tree on the CentOS -mirrors. - -There is a CentOS Vault containing old CentOS trees. This vault is a -picture of the older tree when it was removed from the main tree, and -does not receive updates. It should only be used for reference. - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/Frameworks/files.tex b/Manuals/Filesystem/filesystem-latex/Concepts/Frameworks/files.tex deleted file mode 100644 index e78a961..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/Frameworks/files.tex +++ /dev/null @@ -1,53 +0,0 @@ -% Part : Concepts -% Chapter: Frameworks -% ------------------------------------------------------------ -% $Id: files.tex 6044 2010-07-11 07:49:09Z al $ -% ------------------------------------------------------------ - -\section{File Types} - -Inside CentOS Artwork Repository, there are ``image files'' and ``text -files''. - -\subsection{Image Files} -\hypertarget{sec:Concepts:Frameworks:Image}{} - -Image files are used to implement the CentOS visual style on all -CentOS visual manifestations where image files are involved (i.e. -CentOS distribution, CentOS web sites, CentOS promotion, etc.). Image -files are inside identity frameworks. - -Image files may be available in different formats. Image files in -different formats are produced taking the PNG format as base. The PNG -format is the Inkscape's export format used by \texttt{render.sh} -indentity script to produce a image copy of the SVG design templates. -The \texttt{render.sh} identity script uses command line image -manipulation tools, like ImageMagick and Netpbm, to do image format -convertions from PNG to the formats you specify. You can produce as -many image formats as supported by the previously mentioned command -line image maipulation tools. - -Image files production in different formats is specified inside -configuration scripts, specifically in the variable -\hyperlink{sec:Concepts:Scripts:Configuration:ACTIONS}{\texttt{ACTIONS}} -(\autoref{sec:Concepts:Scripts:Configuration:ACTIONS}). - -Inside frameworks, image files are stored in a directory named `img'. -This name is a convenction that scripts use to store framework's -produced images. If you want to change the image directory's name to -something different from `img', you need to set the same name in all -images' directories along the CentOS Artwork Repository, and update -scripts to recognize the new name you set. This is something you -problably don't need to do, but if you still want to, please share -your reasons in -\href{mailto:centos-devel@centos.org}{centos-devel@centos.org} before -commit your changes. Changing the image directory's name is a big -chanage that needs to be discussed in the community. - -\subsection{Text Files} -\hypertarget{sec:Concepts:Frameworks:Files:Text}{} - -Text files are used to implement the CentOS visual style on all CentOS -visual manifestations where text files are involved (i.e. eula files -and release notes used by Anaconda, etc.). Text files are inside -identity frameworks. diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/Frameworks/introduction.tex b/Manuals/Filesystem/filesystem-latex/Concepts/Frameworks/introduction.tex deleted file mode 100755 index 82c884d..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/Frameworks/introduction.tex +++ /dev/null @@ -1,26 +0,0 @@ -% Part : Concepts -% Chapter: Frameworks -% ------------------------------------------------------------ -% $Id: introduction.tex 6023 2010-06-27 10:09:48Z al $ -% ------------------------------------------------------------ - -Inside CentOS Artwork Repository, CentOS visual identity has been -organized in ``frameworks'', which have been divided in two major -groups: ``translations'', and ``identity''. These two groups of -frameworks are very similar in organization, they both have ``design -templates'' ---to define how things look like---, ``rendering script'' ----to automate the way things are produced---, and ``translated -files'' ---to store the final result of things being produced---. But -their files differ in content and type. - -The identity frameworks are focused on image conception (i.e. image -designing, image rendering, etc.). The translation frameworks are -focused on translation files conception (i.e. translation path -definition, file name definitions, translation markers definition, -etc.). - -Generally, one identity framework has one translation framework -associeted to it. When you render images inside identity frameworks, -the related translation framework is used as translation source and -file name definition. - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/Frameworks/rendering.tex b/Manuals/Filesystem/filesystem-latex/Concepts/Frameworks/rendering.tex deleted file mode 100644 index c7baa89..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/Frameworks/rendering.tex +++ /dev/null @@ -1,45 +0,0 @@ -% Part : Concepts -% Chapter: Frameworks -% ------------------------------------------------------------ -% $Id: rendering.tex 6023 2010-06-27 10:09:48Z al $ -% ------------------------------------------------------------ - -\section{Rendering} -\hypertarget{sec:Concepts:Frameworks:Rendering}{} - -Rendering is the process by which you produce translated content based -on design templates and translation files. Inside CentOS Artwork -Repository you can render images and texts. - -\subsection{Image Rendering} -\hypertarget{sec:Concepts:Frameworks:Rendering:Image}{} - -Image files are rendered using the \texttt{render.sh} identity script. -The \texttt{render.sh} identity script is available in the framework -containing the image files you want to produce. To execute the -\texttt{render.sh} identity script, you need to be inside framework's -directory and use the following syntax: - -\begin{quote} -\texttt{./render.sh 'REGEX'} -\end{quote} - -The REGEX argument is optional. It is used to reduce the amount of -files you want to render. It is a posix-egrep regular expression -pattern, applied against the translation path. - -\subsection{Text Rendering} - -Text files are rendered using the \texttt{render.sh} identity script. -The \texttt{render.sh} identity script is available in the framework -containing the text files you want to produce. To execute the -\texttt{render.sh} identity script, you need to be inside framework's -directory and use the following syntax: - -\begin{quote} -\texttt{./render.sh 'REGEX'} -\end{quote} - -The REGEX argument is optional. It is used to reduce the amount of -files you want to render. It is a posix-egrep regular expression -pattern, applied against the translation path. diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/Frameworks/templates.tex b/Manuals/Filesystem/filesystem-latex/Concepts/Frameworks/templates.tex deleted file mode 100644 index 13a7ca4..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/Frameworks/templates.tex +++ /dev/null @@ -1,113 +0,0 @@ -% Part : Concepts -% Chapter: Frameworks -% ------------------------------------------------------------ -% $Id: templates.tex 6207 2010-08-05 13:11:13Z al $ -% ------------------------------------------------------------ - -\section{Design Templates} -\hypertarget{sec:Concepts:Frameworks:Templates}{} -\label{sec:Concepts:Frameworks:Templates} - -Design templates are plain text files. Design templates may or may not -contain translation markers inside. Design templates are used to -define the CentOS visual style (the look and feel) of CentOS corporate -identity in all its manifestations. Design templates are the -documents you need to create or edit in order to implement or maintain -the monolithic CentOS corporate visual structure. Design templates -are normative documents that need to be conceived carefully. - -Design templates may be based on specific markups (i.e. XHTML, SVG, -CSS, etc.). If that is the case, translation markers may be combined -inside the specific markup design template to create a translatable -markup-specific design template. In contrast, if design templates do -not have specific markup inside, they are considered the simpliest -design templates because they only have translation markers inside. - -Design templates can be read, edited, and studied using your favorite -text editor. - -Design templates are specific to frameworks using design patterns to -define the visual style of content produced inside them. This is the -case of frameworks inside ``trunk/Identity/'', where design templates -are used to define images' visual style; and ``trunk/Translations/'', -where design tempates are used to define translations' common files. - -Inside frameworks, design templates are stored in a directory named -`tpl'. This name is a convenction that scripts use to find framework's -design tempate files. If you want to change the design template -directory's name to something different from `tpl', you need to set -the same name in all design templates' directories along the CentOS -Artwork Repository, and update scripts to recognize the new name you -set. This is something you problably don't need to do, but if you -still want to, please share your reasons in -\href{mailto:centos-devel@centos.org}{centos-devel@centos.org} before -commit your changes. Changing the design template directory's name is -a big chanage that needs to be discussed in the community. - -\subsection{Simpliest Design Templates} - -The simpliest design templates are inside identity frameworks. The -simpliest design tempaltes are plain text files with translation -markers only. These kind of design templates are used to define -information like ``eula files'' (i.e trunk/Identity/Release/Tpl/eula) -used by Anaconda and similar files. The simpliest design template -files do not use extension. - -\subsection{Translation Design Templates} - -The translation design templates are inside translation frameworks. -The translation design templats are plain text documents whithout any -kind of markup. Instead, they contain sed's replacements commands. -As convenction, translation file names end with the extension `.sed'. -Translation files are created and edited using your favorite text -editor. - -\subsection{SVG Design Templates} - -The scalar vector graphics (SVG) design templates are inside identity -frameworks. The SVG design templates are plain text files with -markup, based on SVG standard. The SVG standard is described at -\href{http://www.w3.org/2000/svg}{http://www.w3.org/2000/svg}. - -Even SVG design templates can be read and edited with your favorite -text editor, it is better to use a SVG editor like -\href{http://www.inkscape.org/}{Inkscape} (see -http://www.inkscape.org/) to create and edit them. The SVG design -template files are used to define the visual style of images -controlling the visual style of CentOS distribution, CentOS web sites, -CentOS promotion, etc. - -Inside SVG design templates, each object has an ``Id'' property. By -default the object's Id is a combination of letters and numbers -granting its uniqueness inside the entire document. - -Inside CentOS Artwork Repository, SVG design templates are rendered -automatically using the \texttt{render.sh} identity script. The -\texttt{render.sh} identity script looks for the object's Id property -containing the CENTOSARTWORK uppercase word and exports its area as -bitmap, automatically. - -If you are designing SVG templates for CentOS Artwork Repository, and -you are using the \texttt{render.sh} identity script to render them, -you need to set the CENTOSARTWORK uppercase word as object's Id on the -design object you want to export as bitmap during the rendering -process. The CENTOSARTWORK uppercase word is a convenction used by -scripts to find the export area on your SVG design templates. - -In CentOS Artwork Repository, SVG design templates are released under -the \href{http://creativecommons.org/licenses/by-sa/3.0/}{Creative -Common Share-Alike License 3.0}.\footnote{See -http://creativecommons.org/licenses/by-sa/3.0/} In Inkscape, you say -so in the ``Document Metadata'' panel, available in the ``File'' menu. - -\subsection{XHTML Design Templates} - -The XHTML design templates are inside identity frameworks. They are -plain text with markup, based on the -\href{http://www.w3.org/TR/xhtml1}{XHTML standard} described at -\href{http://www.w3.org/TR/xhtml1}{http://www.w3.org/TR/xhtml1}. These -files are created and edited using your favorite text editor. XHTML -design templates are used to define the visual style of files like the -``Release Notes'' (trunk/Identity/Release/Tpl/release-notes.html) used -by Anaconda. - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/brands.tex b/Manuals/Filesystem/filesystem-latex/Concepts/Identity/brands.tex deleted file mode 100644 index 67a8543..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/brands.tex +++ /dev/null @@ -1,249 +0,0 @@ -% Part : Concepts -% Chapter: Corporate Identity -% ------------------------------------------------------------ -% $Id: brands.tex 6207 2010-08-05 13:11:13Z al $ -% ------------------------------------------------------------ - -\section{The CentOS Brand} -\hypertarget{sec:Concepts:Identity:Brands}{} -\label{sec:Concepts:Identity:Brands} - -\begin{description} -\item[framework:] trunk/Identity/Brands/ -\end{description} - -\noindent The CentOS brand is the name or trademark that conncects the -producer with their products. In this case, the producer is The CentOS -Project and the products are the CentOS distributions, the CentOS web -sites, the CentOS promotion, etc. - -The CentOS Project uses the CentOS brand inside its GNU/Linux -enterprise distributions, web sites, and promotions to connect them -all visually and this way committing the monolithic visual structure -where one unique name and one unique visual style is used in all -visual manifestations. - -% ------------------------------------------------------------ -\section{The CentOS Logotype} -\hypertarget{sec:Concepts:Identity:Brands:Logotype}{} -\label{sec:Concepts:Identity:Brands:Logotype} - -\begin{description} -\item[framework:] trunk/Identity/Brands/Type -\end{description} - -\noindent The CentOS Logotype is represented by the word ``CentOS'' -using \texttt{denmark.ttf} typography. See -\autoref{fig:Concepts:Identity:Brands:Logotype}. - -\begin{figure} -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Brands/Img/CentOS/Type/Build/a/801.pdf}} -\end{center} -\caption{The CentOS Logotype.% - \label{fig:Concepts:Identity:Brands:Logotype}} -\end{figure} - -% ------------------------------------------------------------ -\section{The CentOS Symbol} -\hypertarget{sec:Concepts:Identity:Brands:Symbol}{} -\label{sec:Concepts:Identity:Brands:Symbol} - -\begin{description} -\item[framework:] trunk/Identity/Brands/Symbol -\end{description} - -\noindent The CentOS Symbol is the main visual representation of The -CentOS Project, and probably the most importat visual component inside -CentOS corporate identity. See -\autoref{fig:Concepts:Identity:Brands:Symbol}. Due the CentOS symbol -is graphical element, without any kind of embedded typography, it -provides an efficient way of identification in a multi-language -environments. - -\begin{figure} -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Brands/Img/CentOS/Symbol/Build/5c-a/801.pdf}} -\end{center} -\caption{The CentOS Symbol.% - \label{fig:Concepts:Identity:Brands:Symbol}} -\end{figure} - -% ------------------------------------------------------------ -\section{The Concept Behind CentOS Symbol} -\hypertarget{sec:Concepts:Identity:Brands:SymbolConcept}{} -\label{sec:Concepts:Identity:Brands:SymbolConcept} - -At the moment of writting these lines, I haven't found any reference -about the author who worked out the CentOS symbol and the concept -behind its design. That information would be useful as motivation -source. The CentOS symbol is the visual representation of that the -CentOS community is working for, it would be very nice to have that -information available somewhere. Until then, all we can do is giving -interpretations about it. - -I will take the adventure of describing my personal interpretation -about the CentOS symbol design and the concept behind it. This -interpretation is not definite, nor a final concept. Certainly, this -interpretation may have nothing in common with the one used by the -author of CentOS symbol. The ideas written in this section may change -in the future in the sake of reaching a better CentOS symbol -interpretation for the CentOS community to stand on.\footnote{This is -probably an interesting topic to debate at -``\href{mailto:centos-devel@centos.org}{centos-devel@centos.org}'' -mailing list.} - -The first thing, in order to interpret the CentOS symbol, is to know -which is ``\hyperlink{sec:Concepts:CentOS:Mission}{The CentOS Project -Mission}'' (\autoref{sec:Concepts:CentOS:Mission}) and feel a deep -compromise with it. Later on, take a look to the CentOS symbol and -try to identify each component its design is based on. If you take a -careful look at \autoref{fig:Concepts:Identity:Brands:Symbol} you find -that the CentOS symbol is based on squares, arrows and different -colors. - -The square is a geometrical figure that has four parallel sides of -equal dimensions. The equal dimensions brings the idea of justice -among all parts involved. That is, each part is in harmony one -another. This kind of harmony could be verified at simple sight, or -you can take a rule and messure each side to see that they have the -same dimensions. As long as we can verify this harmony is true, it -starts to be a fact of reason that we can rely on. - -In a second state, the CentOS symbol is built of four identical -$90^{\circ}$ squares filled with unique colors. The squares provide -reason based pragmatic facts. The colors provide emotions. So, in this -design state we could say that different emotions are controlled by -the same pragmatic reasons. - -In a third state, the $90^{\circ}$ set of squares is duplicated to -create a new set of squares. In this new set of squares fill colors -were removed and the whole squares set was rotated $45^{\circ}$. At -this point eight arrows, pointing the outside, are immediatly visible. -Emotions are so strong that they found a way to expand themselves out -of $90^{\circ}$ pragmatic reasons. But reason evolves with changes -and takes new forms ---the $45^{\circ}$ squares set--- to let flow off -the emotions' nature, and thus, uses that enormous expansion force to -create an infinite loop of common benefits, still controlled by the -reason of pragmatic facts. - -At this point the CentOS symbol has been completed. - -% ------------------------------------------------------------ -\section{The CentOS Trademark} -\hypertarget{sec:Concepts:Identity:Brands:Trademark}{} -\label{sec:Concepts:Identity:Brands:Trademark} - -\begin{description} -\item[framework:] trunk/Identity/Brands/Type/Tpl/2c-tm.svg -\end{description} - -\noindent The CentOS Trademark is a distinctive sign or indicator used -by The CentOS Project (as legal entity) to identify that its product -(The CentOS Distribution) or services to consumers with which the -trademark appears originate from a unique source, and to distinguish -its products or services from those of other entities. - -\begin{figure} -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Brands/Img/CentOS/Type/Build/tm/801.pdf}} -\end{center} -\caption{The CentOS Trademark.% - \label{fig:Concepts:Identity:Brands:Trademark}} -\end{figure} - -A trademark is designated by the following symbols: - -\begin{itemize} - -\item $^{\textup{\textsc{tm}}}$ (for an unregistered trademark, that -is, a mark used to promote or brand goods); - -\item $^{\textup{\textsc{sm}}}$ (for an unregistered service mark, -that is, a mark used to promote or brand services); and - -\item \textregistered\ (for a registered trademark). - -\end{itemize} - -% ------------------------------------------------------------ -\section{The CentOS Release Trademark} -\hypertarget{sec:Concepts:Identity:Brands:Release}{} -\label{sec:Concepts:Identity:Brands:Release} - -\begin{description} -\item[framework:] trunk/Identity/Brands/Type/Tpl/2c-tmr.svg -\end{description} - -\noindent The CentOS Release Trademark combines the CentOS trademark -and one decimal number. Based on -``\hyperlink{sec:Concepts:CentOS:Release}{The CentOS Release Schema}'' -(\autoref{sec:Concepts:CentOS:Release}), the CentOS project uses the -CentOS release trademak to identify CentOS visual manifestations that -share common visual structures with internal differences (i.e., The -CentOS Distributions and their installation media). - -Construction of CentOS release trademark, for major releases 4 and 5, -are illustrated on \autoref{fig:Concepts:Identity:Brands:Release:4} -and \autoref{fig:Concepts:Identity:Brands:Release:5}, respectively. - -\begin{figure} -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Brands/Img/CentOS/Type/Build/tmr4/801.pdf}} -\end{center} -\caption{The CentOS trademark for major release number four.% - \label{fig:Concepts:Identity:Brands:Release:4}} -\end{figure} - -\begin{figure} -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Brands/Img/CentOS/Type/Build/tmr5/801.pdf}} -\end{center} -\caption{The CentOS trademark for major release number five.% - \label{fig:Concepts:Identity:Brands:Release:5}} -\end{figure} - -Another way is to copy the release trademark SVG artwork and paste it -on the SVG design template you want it to appear in. Done that, -replace the decimal number with the string \texttt{=MAJOR\_RELEASE=}, -exactly. - -When you render the artwork component, that where you pasted the -release trademark SVG artwork in, you are producing the same artwork -component design for as many major releases as you have specified in -the translation structure of that artwork component being rendered. -Note that, in order for this translation mechanism to work correctly, -the translation structure should be prepared to support the major -release schema first, as described in -``\hyperlink{cha:Concepts:Translations}{Translation}'' -(\autoref{cha:Concepts:Translations}) and -``\hyperlink{sec:Concepts:CentOS:Release}{The CentOS Release Schema}'' -(\autoref{sec:Concepts:CentOS:Release}). - -% ------------------------------------------------------------ -\section{The CentOS Logo} -\hypertarget{sec:Concepts:Identity:Brands:Logos}{} -\label{sec:Concepts:Identity:Brands:Logos} - -\begin{description} -\item[framework:] trunk/Identity/Brands/Logos -\end{description} - -\noindent The CentOS Logo is a graphical element (ideogram, symbol, -emblem, icon, sign) that, together with its logotype (a uniquely set -and arranged typeface) form The CentOS Trademark or commercial brand. -See \autoref{fig:Concepts:Identity:Brands:Logos:Horizontal}. - -\begin{figure} -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Brands/Img/CentOS/Logo/Horizontal/Build/5c-tm/801.pdf}} -\end{center} -\caption{The CentOS Logo (horizontal) with trademark (TM) included.% - \label{fig:Concepts:Identity:Brands:Logos:Horizontal}} -\end{figure} diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/icons.tex b/Manuals/Filesystem/filesystem-latex/Concepts/Identity/icons.tex deleted file mode 100644 index b87e77e..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/icons.tex +++ /dev/null @@ -1,14 +0,0 @@ -% Part : Concepts -% Chapter: Corporate Identity -% ------------------------------------------------------------ -% $Id: icons.tex 6023 2010-06-27 10:09:48Z al $ -% ------------------------------------------------------------ - -\section{Icons} -\hypertarget{sec:Concepts:Identity:Icons}{} -\label{sec:Concepts:Identity:Icons} - -\begin{description} -\item[framework:] trunk/Identity/Icons/ -\end{description} - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/introduction.tex b/Manuals/Filesystem/filesystem-latex/Concepts/Identity/introduction.tex deleted file mode 100644 index 111f6f4..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/introduction.tex +++ /dev/null @@ -1,24 +0,0 @@ -% Part : Concepts -% Chapter: The CentOS Visual Identity -% ------------------------------------------------------------ -% $Id: introduction.tex 6019 2010-06-26 06:42:08Z al $ -% ------------------------------------------------------------ - -\begin{description} -\item[framework:] trunk/Identity/ -\end{description} - -\noindent This chapter describes the CentOS Project corporate -identity. The CentOS Project corporate identity is the ``persona'' of -the organization known as The CentOS Project. The CentOS Project -corporate identity plays a significant role in the way the CentOS -Project, as organization, presents itself to both internal and -external stakeholders. In general terms, the CentOS Project corporate -visual identity expresses the values and ambitions of the CentOS -Project organization, its business, and its characteristics. - -The CentOS Project corporate identity provides visibility, -recognizability, reputation, structure and identification to the -CentOS Project organization by means of corporate design, corporate -communication, and corporate behaviour. - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/models.tex b/Manuals/Filesystem/filesystem-latex/Concepts/Identity/models.tex deleted file mode 100644 index a7f7c53..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/models.tex +++ /dev/null @@ -1,24 +0,0 @@ -% Part : Concepts -% Chapter: Corporate Identity -% ------------------------------------------------------------ -% $Id: models.tex 6023 2010-06-27 10:09:48Z al $ -% ------------------------------------------------------------ - -\section{Models} -\hypertarget{sec:Concepts:Identity:Models}{} -\label{sec:Concepts:Identity:Models} - -\begin{description} -\item[framework:] trunk/Identity/Models/ -\end{description} - -\noindent Here is where you find design models. Design models are -representative images used to illustrate key components inside a -specific design. Design models are frequently used to make -documentation clearer. - -When designing models, try to make them language independent so they -can be reused in differet language documents. For example, you can use -letters or numbers to identify areas in the model and later use the -figure's caption to describe the meaning of those letters and numbers, -respectively. diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/release.tex b/Manuals/Filesystem/filesystem-latex/Concepts/Identity/release.tex deleted file mode 100644 index 8aa299c..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/release.tex +++ /dev/null @@ -1,19 +0,0 @@ -% Part : Concepts -% Chapter: Corporate Identity -% ------------------------------------------------------------ -% $Id: release.tex 6023 2010-06-27 10:09:48Z al $ -% ------------------------------------------------------------ - -\section{Release} -\hypertarget{sec:Concepts:Identity:Release}{} -\label{sec:Concepts:Identity:Release} - -\begin{description} -\item[framework:] trunk/Identity/Release/ -\end{description} - -\noindent Here is where CentOS Distribution release-specific files are -produced. This framework contains textual templates that produce -textual files, like ``release notes'' and ``eula files'' used by -Anaconda. - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/structure.tex b/Manuals/Filesystem/filesystem-latex/Concepts/Identity/structure.tex deleted file mode 100644 index 2542eba..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/structure.tex +++ /dev/null @@ -1,87 +0,0 @@ -% ------------------------------------------------------------ -% $Id: structure.tex 6024 2010-06-28 04:28:27Z al $ -% ------------------------------------------------------------ - \section{Visual Structure} -\hypertarget{sec:Concepts:Identity:Structure}{} - \label{sec:Concepts:Identity:Structure} - -The CentOS Project settles down its corporate visual identity on a -``monolithic corporate visual identity structure''. In this structure -The CentOS Project uses one unique name -(``\hyperlink{sec:Concepts:Identity:Brands}{The CentOS Brand}'') and -one unique visual style -(``\hyperlink{sec:Concepts:Identity:Themes:Default}{The CentOS Default -Theme}'') in all its manifestations. - -The CentOS Project organizes its visual manifestation in four top -level structures: The CentOS Distribution, The CentOS Web, The CentOS -Promotion, and The CentOS Behaiviour. The CentOS Distribution , The -CentOS Web, and The CentOS Promotion use one unique name and one -unique visual style in all its manifestations. - -% ------------------------------------------------------------ - \subsection{Distribution Visual Structure} -\hypertarget{sec:Concepts:Identity:Structure:Distribution}{} - \label{sec:Concepts:Identity:Structure:Distribution} - -It applies to all major releases of CentOS distribution. - -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, 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 components are made -of software improved constantly. - -The software constant improvement is reflected on a numbered release -schema, described in ``\hyperlink{sec:Concepts:CentOS:Release}{The -CentOS Release Schema}'' (\autoref{sec:Concepts:CentOS:Release}). The CentOS release schema is a tool to -provide exact information, specific to one release at any given time. - -People can use this release schema to know the software details that -they are using on their computers, report bugs, fixes, suggestions, or -simply any kind of usefull information; in the same exact basis. - -Remarking the CentOS release schema inside each major release of -CentOS Distribution ---or similar visual manifestation--- takes high -attention in the sake of The CentOS Project corporate visual identity. -For archiving that purpose, graphic designers use ``The CentOS Release -Brand'' in all artwork components controlling the visual style of -CentOS Distribution ---or similar--- visual manifestation. - -Artwork components controlling the visual style of CentOS Distribution -visual manifestation are described in -``\hyperlink{par:Distribution}{Distribution}'' -(\autoref{par:Distribution}). - -% ------------------------------------------------------------ - \subsection{Web Visual Structure} -\hypertarget{sec:Concepts:Identity:Structure:Web}{} - \label{sec:Concepts:Identity:Structure:Web} - -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. - -% ------------------------------------------------------------ - \subsection{Promotion Visual Structure} -\hypertarget{sec:Concepts:Identity:Structure:Promotion}{} - \label{sec:Concepts:Identity:Structure:Promotion} - -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. - -% ------------------------------------------------------------ - \subsection{Behaviour Visual Structure} -\hypertarget{sec:Concepts:Identity:Structure:Behaviour}{} - \label{sec:Concepts:Identity:Structure:Behaviour} - -It applies to CentOS community's social behavior. To what we do and -how we do it. - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/themes.tex b/Manuals/Filesystem/filesystem-latex/Concepts/Identity/themes.tex deleted file mode 100644 index f7a34e9..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/themes.tex +++ /dev/null @@ -1,544 +0,0 @@ -% Part : Concepts -% Chapter: Corporate Identity -% ------------------------------------------------------------ -% $Id: themes.tex 6207 2010-08-05 13:11:13Z al $ -% ------------------------------------------------------------ -\section{Themes} -\hypertarget{sec:Concepts:Identity:Themes}{} -\label{sec:Concepts:Identity:Themes} - -\begin{description} -\item[framework:] trunk/Identity/Themes/ -\end{description} - -\noindent Here is where themes are produced. In the above framework -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. - -% ------------------------------------------------------------ -\section{CentOS Default Theme} -\hypertarget{sec:Concepts:Identity:Themes:Default}{} -\label{sec:Concepts:Identity:Themes:Default} - -The CentOS default theme is used in all visual manifestations of -CentOS Project's corporate visual identity (e.g., distributions, web -sites, promotion, etc.). - -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 -(\textbf{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 ``\hyperlink{sec:Concepts:Identity:Themes:Motifs}{Theme -Motifs}'' (\autoref{sec:Concepts:Identity:Themes:Motifs}). - -% ------------------------------------------------------------ -\section{CentOS Alternative Themes} -\hypertarget{sec:Concepts:Identity:Themes:Alternative}{} -\label{sec:Concepts:Identity:Themes:Alternative} - -CentOS alternative themes 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. - -% ------------------------------------------------------------ -\section{Theme Transition} -\hypertarget{sec:Concepts:Identity:Themes:Transition}{} -\label{sec:Concepts:Identity:Themes:Transition} - -Theme transition is the action of moving a theme from alternative to -default. This transition begins when an alternative theme gets -popular enough inside CentOS Comminity, and both CentOS Administrators -and CentOS Comunity Members want to extend it to all CentOS Visual -Manifestations. - -Once the popular alternative theme has been extended through all -CentOS visual manifestations, the alternative theme implementation -phase starts. The alternative theme implementation phase is where -default theme art work is replaced with alternative theme ones. After -the implementation phase, the previous default theme is tagged as -alternative and the implemented alternative as default. - -Theme Transition has a huge impact in CentOS Corporate Visual -Identity, it should be done only if absolutly necessary. Generally, it -is better to improve the current default theme, based on its concept, -than create a completly new one. - -% ------------------------------------------------------------ -\section{Theme Models} -\hypertarget{sec:Concepts:Identity:Themes:Models}{} -\label{sec:Concepts:Identity:Themes:Models} - -\begin{description} -\item[framework:] trunk/Identity/Themes/Models/ -\end{description} - -\noindent Here is where theme models are stored. 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. - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -trunk/Identity/Themes/ -|-- Models -| |-- Default <-- theme's model name. -| | |-- Distro -| | | |-- Anaconda -| | | | |-- Header -| | | | |-- Progress -| | | | |-- Prompt -| | | | `-- Splash -| | | `-- BootUp -| | | |-- Firstboot -| | | |-- GDM -| | | |-- GRUB -| | | |-- GSplash -| | | |-- KDM -| | | |-- KSplash -| | | |-- RHGB -| | | `-- Plymouth -| | |-- Promo -| | |-- Web -| |-- Alternative <-- theme's model name. -| | |-- Distro -| | | `-- BootUp -| | | |-- Firstboot -| | | |-- GDM -| | | |-- GRUB -| | | |-- GSplash -| | | |-- KDM -| | | |-- KSplash -| | | |-- RHGB -| | | `-- Plymouth -| |-- ... more theme models. -\end{verbatim} -\hrulefill -\caption{Theme models structure.% - \label{fig:Concepts:Identity:Themes:Models}} -\end{figure} - -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. - -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 following -ready-to-use theme models: - -\begin{itemize} - -\item \textbf{Default:} Stores the theme model used to produce -``\hyperlink{sec:Concepts:Identity:Themes:Default}{CentOS -Default Theme}'' -(\autoref{sec:Concepts:Identity:Themes:Default}). - -\item \textbf{Alternative:} Stores the theme model used to produce -``\hyperlink{sec:Concepts:Identity:Themes:Alternative}{CentOS -Alternative Themes}'' -(\autoref{sec:Concepts:Identity:Themes:Alternative}). - -\end{itemize} - -\begin{figure} -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Models/Img/en/Corporate/common-design-model-fig1.pdf}} -\end{center} -\caption{Anaconda theme model producing three different visual -styles.} -\end{figure} - -\begin{figure} -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Models/Img/en/Corporate/common-design-model-fig2.pdf}} -\end{center} -\caption{Firstboot theme model producing three different visual -styles.} -\end{figure} - -% ------------------------------------------------------------ -\section{Theme Motifs} -\hypertarget{sec:Concepts:Identity:Themes:Motifs}{} -\label{sec:Concepts:Identity:Themes:Motifs} - -\begin{description} -\item[framework:] trunk/Identity/Themes/Motifs/ -\end{description} - -\noindent Here is where the themes' artistic motifs are produced. The -artistic motif is a graphic design used as common pattern to connect -all CentOS Project's visual manifestations inside the same theme. - -Inside the framework location above, artistic motifs are organized by -names inside the standard file structure illustrated in -\autoref{fig:Concepts:Identity:Themes:Motifs:Default} and -\autoref{fig:Concepts:Identity:Themes:Motifs:Alternative}. - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -trunk/Identity/Themes/ -|-- Motifs -| |-- Modern <-- theme name. -| | |-- Backgrounds -| | |-- Distro -| | | |-- Anaconda -| | | | |-- Header -| | | | |-- Progress -| | | | |-- Prompt -| | | | `-- Splash -| | | |-- BootUp -| | | | |-- Firstboot -| | | | |-- GDM -| | | | |-- GRUB -| | | | |-- GSplash -| | | | |-- KDM -| | | | |-- KSplash -| | | | |-- RHGB -| | | | `-- Plymouth -| | | `-- Desktop -| | |-- Info -| | |-- Palettes -| | |-- Promo -| | |-- Screenshots -| | `-- Web -| |-- ... more theme names. -\end{verbatim} -\hrulefill -\caption{Theme motifs default structure.% - \label{fig:Concepts:Identity:Themes:Motifs:Default}} -\end{figure} - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -trunk/Identity/Themes/ -|-- Motifs -| |-- TreeFlower <-- theme name. -| | |-- Backgrounds -| | |-- Distro -| | | |-- BootUp -| | | | |-- Firstboot -| | | | |-- GDM -| | | | |-- GRUB -| | | | |-- GSplash -| | | | |-- KDM -| | | | |-- KSplash -| | | | |-- RHGB -| | | | `-- Plymouth -| | | `-- Desktop -| | |-- Info -| | |-- Palettes -| | |-- Screenshots -| |-- ... more theme names. -\end{verbatim} -\hrulefill -\caption{Theme motifs alternative structure.% - \label{fig:Concepts:Identity:Themes:Motifs:Alternative}} -\end{figure} - -When designing artistic motifs for CentOS, consider the following -recommendations: - -\begin{itemize} - -\item Give a unique (case-sensitive) name to your Motif. This name is -used as value wherever theme variable (\$THEME) or translation marker -(\texttt{=THEME=}) is. Optionally, you can add a description about -inspiration and concepts behind your work. - -\item Use the location trunk/Identity/Themes/Motifs/\$THEME/ to store -your work. If it doesn't exist create it. Note that this require you -to have previous commit access in CentOS Artwork Repository. - -\item The CentOS Project is using the blue color (\texttt{\#204c8d}) -as base for its corporate visual identity. Use the CentOS Project's -base corporate color as much as possible in your artistic motif -designs. - -\item Try to make your design fit one of the -``\hyperlink{sec:Concepts:Identity:Themes:Models}{Theme Models}'' -(\autoref{sec:Concepts:Identity:Themes:Models}). - -\item Feel free to make your art enterprise-level and beautiful. - -\item Add the following information on your art work (both in a visible -design area, and inside Inkscape's document metadata section wherever -it be possible): - -\begin{itemize} - -\item The name (or logo) of your artistic motif. - -\item The copyright sentence: \texttt{Copyright (C) YEAR YOURNAME} - -\item The license under which the work is released. All CentOS Art -works are released under -\href{http://creativecommons.org/licenses/by-sa/3.0/}{Creative Common -Share-Alike License 3.0} -(\href{http://creativecommons.org/licenses/by-sa/3.0/}{http://creativecommons.org/licenses/by-sa/3.0/}). - -\end{itemize} - -\end{itemize} -% ------------------------------------------------------------ -\section{Theme Palettes} -\hypertarget{sec:Concepts:Identity:Themes:Palettes}{} -\label{sec:Concepts:Identity:Themes:Palettes} - -\begin{description} -\item[framework:] turnk/Identity/Themes/Motifs/\$THEME/Palettes/\\ -\end{description} - -\noindent 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. -\autoref{tab:Concepts:Identity:Themes:Palettes:Files}. - -% ------------------------------------------------------------ -\section{Theme Palettes Creation} -\hypertarget{sec:Concepts:Identity:Themes:Palettes:Creation}{} -\label{sec:Concepts:Identity:Themes:Palettes:Creation} - -Theme palettes are based on art works' specific color information you -are creating palettes for. As we write this section, there are two art -works that require color limitations. They are Grub and Syslinux art -works. - -This section describes a generic procedure you can use to create theme -palettes for art works which need to be produced with color -limitations. - -\begin{enumerate} - -\item As first step, you need to produce a PNG file with the final -design of that art work you are creating palettes for. You can do -this by using the \texttt{render.sh} script available in the art -work's identity framework. - -\item Secondly, you need to generate the limited color information for -that PNG file the three different file formats (See -\autoref{tab:Concepts:Identity:Themes:Palettes:Files}). You can do -this by using the Gimp as described below: - -\begin{table}[!hbp] -\center -\begin{tabular}{ll} -\hline -\textbf{File} & \textbf{Description}\\ -\hline -\texttt{.gpl} & Gimp palette files.\\ -\texttt{.ppm} & Portable Pixel Map palette files.\\ -\texttt{.hex} & Hexadecimal auxiliar palette files.\\ -\hline -\end{tabular} -\caption{Palette file types.% - \label{tab:Concepts:Identity:Themes:Palettes:Files}} -\end{table} - -\end{enumerate} - -To create the \texttt{.gpl} file: - -\begin{enumerate} - -\item Open the Gimp (\textit{Applications / Graphics / The Gimp}). - -\item Open the PNG format file you want to generate the limited color -information for (\textit{File / Open ...}). - -\item Index the image (\textit{Image / Mode / Indexed...}). This will -open the window ``Indexed Color Conversion''. Use this window to -``Generate optimum palette'' by setting the maximum number of colors -you want to have in the final indexed image. In this window, by the -default, Gimp has set 255 as the maximum number of colors, you should -change this value to fit the art work color limitation requirements -(i.e. 14 colors for Grub's splash, and 16 colors for Syslinux splash, -etc.). Another option you can play with is ``Color dithering'' at the -window's bottom, particularly the ``Floyd-Steinberg (reduced color -dithering)'' option which seems to archive the best results. - -\item At this point you have reduced color information and indexed the -image. This let you save the color information as a Gimp palette file -(.gpl) for further using. - -To export the color information as Gimp palette you need to open the -palette window (\textit{Ctrl+P}) and go to the action ``Import -Palette...'' inside ``Palettes Menu''. This will open the window -``Import Palette''. In this window you need to specify the source from -where you will retrive color information and the name of the palette -file. Use ``Image'' as source to create your palette and the -appropriate name (e.g., \texttt{centos-\$themename-grub}).\footnote{in -\texttt{centos-\$themename-grub} file name, the \texttt{\$themename} -part is the theme's name you are working on (e.g., Modern, TreeFlower, -etc.) for Grub's palette, \texttt{centos-\$themename-syslinux} for -Syslinux palette, etc.} - -\end{enumerate} - -To create the \texttt{.ppm} file: - -\begin{enumerate} - -\item Use the Gimp to create a new image (\textit{Ctrl+N}) of 16 x 1 -pixels of dimension. That is 16 pixels width and 1 pixel height. - -\item That is a rather small image so you problably want to zoom it in -to better see what you are doing. In a 1024x768 screen resolution, -zoom the 16 x 1 pixel image to 4500\% makes things clear enough. If -you are using a different screen resolution you probably need to zoom -in to a different value. - -\item Now it's time to fill up the empty image with the color -information we created previously. You do this using the pen tool -(\textit{N}) with a 1x1 brush (\textit{Shit+Ctrl+B}). At this point it -is a good time to open the ``Palette Editor'' window and use the Gimp -palette file with the color information we created (\textit{Ctrl+P / -doble click on the palette file}). - -\begin{quote} - -\textbf{Caution!:} If you are creating \texttt{.ppm} palettes for -Anaconda prompt (syslinux), the order used to set the color -information is relevant. Relevant values in the image are positions: 0 -and 7. Position 0 is used as background color, which is black -(\texttt{\#000000}) generally and position 7 is used as forground -color, which is white (\texttt{\#ffffff}) generally. This, in order to -grant the highest contrast. See -\autoref{fig:Concepts:Identity:Themes:Palettes:Syslinux}. - -\end{quote} - -\end{enumerate} - -To create the (\texttt{.hex}) file: - -\begin{enumerate} - -\item Create a plain text file and put the hexadecimal color -information and its index position defined in \texttt{.ppm} palette -inside the file, one definition by line. The format used to create -the \texttt{.hex} file is \texttt{\#rrbbgg=i \dots}. Where -\texttt{\#rrggbb=i} indicates that the color \texttt{\#rrggbb} (hex) -should be assigned index i (decimal). - -\begin{quote} -\textbf{Caution!:} In order to produce Anaconda prompt (syslinux) -images correctly, both \texttt{.hex} and \texttt{.ppm} color and index -information should match. -\end{quote} - -\end{enumerate} - -\begin{figure}[!hbp] -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Models/Img/en/Distro/Anaconda/Prompt/syslinux-palette.pdf}} -\end{center} -\caption{Palette's background (A) and forground (B) color position.% - \label{fig:Concepts:Identity:Themes:Palettes:Syslinux}} -\end{figure} - -% ------------------------------------------------------------ -\section{Theme File Structure} -\hypertarget{sec:Concepts:Identity:Themes:Files}{} -\label{sec:Concepts:Identity:Themes:Files} - -Inside CentOS Artwork Repository, each theme has a name and a -directory for it. Inside each theme directory, the CentOS Project -visual style is organized in the directories: Distro, Info, Palettes, -Promo, Screenshots, and Web. - -% ------------------------------------------------------------ -\subsection{The \texttt{Distro} Directory} -\hypertarget{sec:Concepts:Identity:Themes:Files:Distro}{} -\label{sec:Concepts:Identity:Themes:Files:Distro} - -Here is where image files controlling CentOS Distribution visual style -are produced. - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -turnk/Identity/Themes/Motifs/$THEME/Distro/ -|-- Anaconda -| |-- Header -| |-- Progress -| |-- Prompt -| `-- Splash -|-- BootUp -| |-- Firstboot -| |-- GDM -| |-- GRUB -| |-- GSplash -| |-- KDM -| |-- KSplash -| `-- RHGB -`-- Desktop -\end{verbatim} -\hrulefill -\caption{The CentOS distribution theme structure.} -\end{figure} - -% ------------------------------------------------------------ -\subsection{The \texttt{Palettes} Directory} -\hypertarget{sec:Concepts:Identity:Themes:Files:Palettes}{} -\label{sec:Concepts:Identity:Themes:Files:Palettes} - -Here is where theme's palettes are sotred. Palettes are used to -automate image rendering in cases where a limited amount of color need -to be specified. Before you could render color-limited art works (e.g. -Grub, and Syslinux), you need to create their color-limited palettes -first. See -``\hyperlink{sec:Concepts:Identity:Themes:Palettes:Creation}{Theme -Palette Creation}'' -(\autoref{sec:Concepts:Identity:Themes:Palettes:Creation}). - -% ------------------------------------------------------------ -\subsection{The \texttt{Promo} Directory} -\hypertarget{sec:Concepts:Identity:Themes:Files:Promo}{} -\label{sec:Concepts:Identity:Themes:Files:Promo} - -Here is where image files controlling CentOS promotion visual style -are produced. - -% ------------------------------------------------------------ -\subsection{The \texttt{Screenshots} Directory} -\hypertarget{sec:Concepts:Identity:Themes:Files:Screenshots}{} -\label{sec:Concepts:Identity:Themes:Files:Screenshots} - -Here is where theme's screenshots are stored. The purpose of this -directory is to collect theme's implementation graphical history -through time. Inside this directory you can have distribution -screenshots, web sites screenshtos, and promotion screenshots. If -theme has been implemented out of computers like would be the case of -events, stands, etc. those photos can be added here too, in the -promotion screenshot section. - -% ------------------------------------------------------------ -\subsection{The \texttt{Web} Directory} -\hypertarget{sec:Concepts:Identity:Themes:Files:Web}{} -\label{sec:Concepts:Identity:Themes:Files:Web} - -Here is where image files controlling CentOS Web sites visual style -are produced. diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/widgets.tex b/Manuals/Filesystem/filesystem-latex/Concepts/Identity/widgets.tex deleted file mode 100644 index 5cd8db2..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/Identity/widgets.tex +++ /dev/null @@ -1,13 +0,0 @@ -% Part : Concepts -% Chapter: Corporate Identity -% ------------------------------------------------------------ -% $Id: widgets.tex 6023 2010-06-27 10:09:48Z al $ -% ------------------------------------------------------------ - -\section{Widgets} -\hypertarget{sec:Concepts:Identity:Widgets}{} -\label{sec:Concepts:Identity:Widgets} - -\begin{description} -\item[framework:] trunk/Identity/Widgets/ -\end{description} diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/logo.tex b/Manuals/Filesystem/filesystem-latex/Concepts/logo.tex deleted file mode 100644 index b9fa0a1..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/logo.tex +++ /dev/null @@ -1,17 +0,0 @@ -% Part : Concepts -% Chapter: The CentOS Logo -% ------------------------------------------------------------ -% $Id: logo.tex 6191 2010-08-02 02:36:14Z al $ -% ------------------------------------------------------------ - -\section{Horizontal} -\hypertarget{sec:Concepts:Logo:Horizontal}{} -\label{sec:Concepts:Logo:Horizontal} - -\section{Pyramidal} -\section{Circular} -\section{Construction} -\section{Usage} -\section{Colors} -\section{Reductions} -\section{Prohibitions} diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/manuals.tex b/Manuals/Filesystem/filesystem-latex/Concepts/manuals.tex deleted file mode 100644 index 2d783d6..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/manuals.tex +++ /dev/null @@ -1,288 +0,0 @@ -% Part : Concepts -% Chapter: Manuals -% ------------------------------------------------------------ -% $Id: manuals.tex 6191 2010-08-02 02:36:14Z al $ -% ------------------------------------------------------------ - -\begin{description} -\item[framework:] trunk/Manuals/ -\end{description} - -\noindent This chapter describes the CentOS Artwork Repository User -Guide. The CentOS Artwork Repository User Guide is the book you are -reading right now. The main goals of this book is helping you to -understand how CentOS Artwork Repository works, and what you can do to -get the best of it. It is also an excuse for you to join us and help -improving it. - -\section{Structure} - -Inside CentOS Artwork Repository, documentation is conceived using -\LaTeX's book class. Instead of having the entire document in a single -file, information has been spread in separated files under Manuals -framework structure. The Manuals framework structure is illustrated in -\autoref{fig:Concepts:Manuals:Structure} and described in -``\hyperlink{sec:Concepts:Manuals:Files}{Relevant Files}'' (see -\autoref{sec:Concepts:Manuals:Files}) and -``\hyperlink{sec:Concepts:Manuals:Directories}{Relevant Directories}'' -(see \autoref{sec:Concepts:Manuals:Directories}). - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -trunk/Manuals/ -|-- Concepts -| |-- CentOS -| |-- Frameworks -| |-- Identity -| `-- ... -|-- Distribution -| |-- Anaconda -| | |-- Firstboot -| | |-- Header -| | |-- Progress -| | `-- ... -| |-- Backgrounds -| |-- BootUp -| | |-- GDM -| | |-- GRUB -| | `-- ... -| `-- Release -|-- Licenses -|-- Translations -|-- Workstation -|-- convenctions.tex -|-- repository.aux -|-- repository.lof -|-- repository.log -|-- repository.lot -|-- repository.out -|-- repository.pdf -|-- repository.tex -`-- repository.toc -\end{verbatim} -\hrulefill -\caption{Manuals framework structure.% - \label{fig:Concepts:Manuals:Structure}} -\end{figure} - -\section{Writing Style} - -When writing for CentOS Artwork Repository User Guide, keep in mind -the following quote taken from the online ``BBC News Styleguide'': ----The key to good writing is \textbf{simple thoughts simply -expressed}. Use short sentences and short words. Anything which is -confused, complicated, poorly written or capable of being -misunderstood risks losing the listener or viewer, and once you have -done that, you might just as well not have come to work---. - -If you need to express complicated ideas, try to split them out in -smaller and simpler ideas as much as possible. If you consider it -appropriate, try to use -``\hyperlink{sec:Concepts:Identity:Models}{Design Models}'' (see -\autoref{sec:Concepts:Identity:Models}) to illustrate your thoughts. - -\subsection{Cross References} - -When you create \LaTeX's cross references, you need to define targets -and links. Targets are the specific locations in the document that -links point to. In \LaTeX, these cross reference targets and links -can be defined in many ways, so we need to standardize the way we use -inside CentOS Artwork Repository User Guide to make it look uniform -and easy to read. - -Inside CentOS Artwork Repository User Guide, cross references look -like illustrated in -\autoref{fig:Concepts:Manuals:CrossRef:Presentation}. Cross reference -targets are defined as illustrated in -\autoref{fig:Concepts:Manuals:CrossRef:Targets}, and links to those -targets are defined as illustrated in -\autoref{fig:Concepts:Manuals:CrossRef:Links}. - -Note that we use both \texttt{hypertarget} and \texttt{label} commands -to define targets, and \texttt{hyperlink} and \texttt{autoref} to -define links. With \texttt{hyperlink} we create long text links ----usefull when reading in the coputer---, and with \texttt{autoref} -we create numbered links ---usefull when reading in a printed copy---. - -\begin{figure}[!hbp] -\hrulefill -\begin{flushleft} -\dots you can find more information in -``\hyperlink{sec:Concepts:Identity:Brands}{Logos}'' (see -\autoref{sec:Concepts:Identity:Brands}), specifically in -\hyperlink{sec:Concepts:Identity:Brands:Logos}{the horizontal version} (see -\autoref{sec:Concepts:Identity:Brands:Logos}). -\end{flushleft} -\hrulefill -\caption{Cross reference link presentation.% - \label{fig:Concepts:Manuals:CrossRef:Presentation}} -\end{figure} - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -\part{Concepts} -... -\chapter{The CentOS Logo} -\hypertarget{sec:Concepts:Logo}{} -\label{sec:Concepts:Logo} -... -\section{Horizontal} -\hypertarget{sec:Concepts:Identity:Brands}{} -\label{sec:Concepts:Identity:Brands} -... -\end{verbatim} -\hrulefill -\caption{\LaTeX's definition for cross reference targets.% - \label{fig:Concepts:Manuals:CrossRef:Targets}} -\end{figure} - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -\dots you can find more information in -``\hyperlink{sec:Concepts:Identity:Brands}{The CentOS Logo}'' -(see \autoref{sec:Concepts:Identity:Brands}), specifically in -\hyperlink{sec:Concepts:Identity:Brands:Logos}{the horizontal version} -(see \autoref{sec:Concepts:Identity:Brands:Logos}). -\end{verbatim} -\hrulefill -\caption{\LaTeX's definition for cross reference links.% - \label{fig:Concepts:Manuals:CrossRef:Links}} -\end{figure} - -\subsection{Figures} - -Inside CentOS Artwork Repository User Guide, illustrations (i.e. -images, framework structures, source code, commands, etc.) are shown -using \LaTeX's \texttt{figure} environment. An example of -\texttt{figure} environment definition is illustrated in -\autoref{fig:Concepts:Manuals:Figures}. More information about -\LaTeX's \texttt{figure} environment can be found in \LaTeX's info -manual. To read the \LaTeX's info manual, execute in your terminal the -command: \texttt{info latex}. - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -\begin{figure}[!hbp] -\hrulefill -... -\hrulefill -\caption{... .% - \label{fig:...}} -\end{figure} -\end{verbatim} -\hrulefill -\caption{\LaTeX's definition for \texttt{figure} environment.% - \label{fig:Concepts:Manuals:Figures}} -\end{figure} - -\subsection{Tables} - -Inside CentOS Artwork Repository User Guide, tabular information (i.e. -translation markers, etc.) is shown using \LaTeX's \texttt{table} -environment. An example of \texttt{table} environment definition is -illustrated in \autoref{fig:Concepts:Manuals:Tables}. More -information about \LaTeX's \texttt{table} environment can be found in -\LaTeX's info manual. To read the \LaTeX's info manual, execute in -your terminal the command: \texttt{info latex}. - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -\begin{table}[!hbp] -\centering -\begin{tabular}[pos]{cols} -\hline -... -\hline -\end{tabular} -\caption{... .% - \label{tab:...}} -\end{table} -\end{verbatim} -\hrulefill -\caption{\LaTeX's definition for \texttt{table} environment.% - \label{fig:Concepts:Manuals:Tables}} -\end{figure} - -\section{Relevant Files} -\hypertarget{sec:Concepts:Manuals:Files}{} -\label{sec:Concepts:Manuals:Files} - -\subsection{repository.tex} - -The \texttt{repository.tex} file is the main book's file. Here is -where you define specific book information like class, title, authors, -etc. Inside \texttt{repository.tex} you organize chapters and load -their sections. - -\subsection{introduction.tex} - -The \texttt{Introduction.tex} file introduces a specific artwork -component: what it does, where and when it appears in, etc. - -\subsection{framework.tex} - -The \texttt{rramework.tex} file describes how to interact with a -specific artwork component: where to find the artwork component inside -CentOS Artwork Repository, how to render their images, how to render -their translations, their specific translation markers, etc. - -\subsection{rebranding.tex} - -The \texttt{rebranding.tex} file describes how to rebrand a specific -artwork component: where to find the arwork component inside CentOS -Distribution, related packages you need to modify, etc. - -\section{Relevant Directories} -\hypertarget{sec:Concepts:Manuals:Directories}{} -\label{sec:Concepts:Manuals:Directories} - -\subsection{Concepts} - -The \texttt{Concepts} directory organizes chapters related to -``Concepts'' part. Files in this directory describe concepts used -inside CentOS Artwork Repository. - -\subsection{Workstation} - -The \texttt{Workstation} directory organizes chapters related to -``Preparing Your Workstation'' part. Files in this directory describe -actions (i.e. installation and configuration) you need to do before -using CentOS Artwork Repository. - -\subsection{Distribution} - -The \texttt{Distribution} directory organizes chapters releated to -``Distribution'' part. This part gets its attention into the different -artwork components of CentOS Distribution, using a subdirectory -structure to organize them and the files \texttt{introduction.tex}, -\texttt{framework.tex}, and \texttt{rebranding.tex} to describe them. - -\subsection{Licenses} - -The \texttt{Licenses} directory organizes licenses used in this book. - -\section{Revisions} -\hypertarget{sec:Concepts:Manuals:Revisions}{} -\label{sec:Concepts:Manuals:Revisions} - -Revisions are a way of organizing changes committed to CentOS Artwork -Repository User Guide. Revisions have the format ``Revision M.N'', -where M is the major revision number, and N is the update revision -number. Revision update number (N) may increase by one every month to -release that month's changes. Once the six month cycle is reached, -major revision number (M) is increased by one and update revision -number (N) is reset to 0. - -\section{Export to PDF} - -To produce the file \texttt{repository.pdf}, you need to get inside -the Manual's framework and execute the command: - -\begin{quote} -\texttt{pdflatex repository.tex} -\end{quote} diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/motif.tex b/Manuals/Filesystem/filesystem-latex/Concepts/motif.tex deleted file mode 100644 index 0ddcd27..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/motif.tex +++ /dev/null @@ -1,9 +0,0 @@ -% Part : Concepts -% Chapter: The CentOS Artistic Motif -% ------------------------------------------------------------ -% $Id: motif.tex 6191 2010-08-02 02:36:14Z al $ -% ------------------------------------------------------------ - -\section{CentOS Default Artistic Motif} -\section{CentOS Alternative Artistic Motif} -\section{CentOS Artistic Motif License} diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/rebranding.tex b/Manuals/Filesystem/filesystem-latex/Concepts/rebranding.tex deleted file mode 100644 index 780477b..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/rebranding.tex +++ /dev/null @@ -1,28 +0,0 @@ -% Part : Concepts -% Chapter: Rebranding -% ------------------------------------------------------------ -% $Id: rebranding.tex 6191 2010-08-02 02:36:14Z al $ -% ------------------------------------------------------------ - -To comply with upstream redistribution policy, the CentOS Project -removes all upstream brands and artworks from CentOS Distribution. The -CentOS Project has its own brand and its own artwork. The CentOS Brand -and CentOS Artwork are what the CentOS Project uses in CentOS -Distribution. - -The action of removing upstream brands and artworks and add CentOS -brands and artworks is what we call rebranding. - -CentOS Brands and artworks are organized inside CentOS Artwork -Repository. The CentOS Artwork Repository is maintain by CentOS -Artwork SIG which is formed by CentOS Community People. - -\section{General Suggestions} - -\begin{itemize} - -\item Use original names as much as possible. Do not rename original -file names if you don't need to. - -\end{itemize} - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/release.tex b/Manuals/Filesystem/filesystem-latex/Concepts/release.tex deleted file mode 100644 index 3f0ca92..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/release.tex +++ /dev/null @@ -1,11 +0,0 @@ -% Part : Concepts -% Chapter: The CentOS Release Brand -% ------------------------------------------------------------ -% $Id: release.tex 6191 2010-08-02 02:36:14Z al $ -% ------------------------------------------------------------ - -\section{Construction} -\section{Usage} -\section{Colors} -\section{Reductions} -\section{Prohibitions} diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/scripts.tex b/Manuals/Filesystem/filesystem-latex/Concepts/scripts.tex deleted file mode 100644 index 660bcba..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/scripts.tex +++ /dev/null @@ -1,395 +0,0 @@ -% Part : Concepts -% Chapter: Scripts -% ------------------------------------------------------------ -% $Id: scripts.tex 6207 2010-08-05 13:11:13Z al $ -% ------------------------------------------------------------ - -\begin{description} -\item[framework:] trunk/Scripts/ -\end{description} - -\noindent Inside CentOS Artwork Repository, scripts are organized in -three groups: ``invocation scripts'', ``configuration scripts'' and -``function scripts''. Scripts are mainly used to help you automate and -standardize tasks. A graphical representation of how scripts are -organized inside CentOS Artwork Repository is illustrated in -\autoref{fig:Concepts:Scripts}. - -\begin{figure}[!hbp] -\centering -\includegraphics[width=0.8\textwidth]{% - ../Identity/Models/Img/en/Scripts/initFunctions.pdf} -\caption{The scripts organization model.% - \label{fig:Concepts:Scripts}} -\end{figure} - -\section{Invocation Scripts} -\hypertarget{sec:Concepts:Scripts:Invocation}{} -\label{sec:Concepts:Scripts:Invocation} - -Invocation scripts are identified by the name \texttt{render.sh}. You -may find invocation scripts inside \texttt{trunk/Translations/} and -\texttt{trunk/Identity/} structures. Invocation scripts' main purpose -is calling the appropriate configuration script. - -\section{Configuration Scripts} -\hypertarget{sec:Concepts:Scripts:Configuration}{} -\label{sec:Concepts:Scripts:Configuration} - -\begin{description} -\item[framework:] trunk/Scripts/Config/ -\end{description} - -\noindent Configuration scripts are identified by the name -\texttt{render.conf.sh}. In the script organization model -(\autoref{fig:Concepts:Scripts}), configuration scripts are the first -scripts executed by you after running the invocation script -(\texttt{render.sh}). Generally, configuration scripts are short -files that initialize functions, set variable definitions, and call -the appropriate function to start rendering. - -\subsection{Initialize Functions} - -Function initialization is the first action you do inside -configuration scripts. By default, functions are initialized using -the \texttt{initFunctions.sh} script, as illustrated in -\autoref{fig:Concepts:Scripts:Configuration:initFunctions}. The -\texttt{initFunctions.sh} script looks for functions definitions in -files that match the expansion \texttt{*.sh} inside the -\texttt{trunk/Scripts/Functions/} path, and exports them to the -current shell environment, that created when you ran the invocation -script. - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -# Initialize functions. -. /home/centos/artwork/trunk/Scripts/initFunctions.sh -\end{verbatim} -\hrulefill -\caption{Function initialization inside configuration scripts.% - \label{fig:Concepts:Scripts:Configuration:initFunctions}} -\end{figure} - -Once functions are initialized, they are ready to be used by you, in -any point after its initialization. This initialization arms you with -a customizable set of functionalities that can be used on -configuration scripts and reused inside functions themselves. - -\subsection{Define Artwork Component} - -The \texttt{ARTCOMP} variable defines the artwork component you want -to render. The \texttt{ARTCOMP}'s value defines the specific artwork -component's matching list and Themes' translation path. The -\texttt{ARTCOMP}'s value is built using the translation path structure -as reference. For example, if you want to render Anaconda progress -files, you need to know that artwork component's translation path -which is:\\ -\\ -\fbox{trunk/Translations/Identity/Themes/Distro/Anaconda/Progress}\\ -\\ -and then, go to its \texttt{render.conf.sh} file to define -\texttt{ARTCOMP} as the following:\\ -\\ -\fbox{ARTCOMP='Distro/Anaconda/Progress'}\\ -\\ -The \texttt{ARTCOMP}'s value is processed by \texttt{getMatchingList} -function to determine the specific artwork component's -translation-design matching list. The matching list function is -described in \autoref{sec:Concepts:Scripts:Function:getMatchingList}. - -\subsection{Define Filtering Pattern} - -The \texttt{REGEX} variable defines a regular expression as filtering -pattern. If the filtering pattern is specified, the rendering process -is limited to the amount of files matching the filtering pattern. By -default, this value is set to receive the shell's first argument -(\texttt{\$1}). This let you pass the filtering pattern on the -command line, at rendering time. If you need a fixed value for the -filtering pattern, you can change the \texttt{REGEX}'s value on your -working copy to whatever you need, but please do no commit that. - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -# Define filtering pattern. This is a regular expression -# matching the translation path. -REGEX="$1" -\end{verbatim} -\hrulefill -\caption{Define filtering pattern inside configuration scripts.% - \label{fig:Concepts:Scripts:Configuration:REGEX}} -\end{figure} - -\subsection{Define Post-rendering Actions} -\hypertarget{sec:Concepts:Scripts:Configuration:ACTIONS}{} -\label{sec:Concepts:Scripts:Configuration:ACTIONS} - -Post-rendering actions are specific functionalities applied to the -final files produced by base rendering functions like -\texttt{renderImage} and \texttt{renderText}. Post-rendering actions -are defined by the \texttt{ACTIONS} array variable. By default, the -\texttt{ACTIONS}'s value is set to empty (\texttt{ACTIONS[0]=''}) -which provokes no post-rendering action to be applied. A different -configuration is illustrated on -\autoref{fig:Concepts:Scripts:Configuration:ACTIONS}. - -When rendering images, using \texttt{renderImage}, the only result you -get is in PNG format. This is enough most of the time. But in some -other situations, you need to produce the same image in many different -formats (i.e. xpm, pdf, tiff, xbm, etc.). These tasks are very -specific and are not included inside \texttt{renderImage} function. -Instead, the \texttt{renderFormats} function was created and used as -post-rendering action in these situations. - -When rendering texts, using \texttt{renderText}, the only result you -get is in plain text format. Again, this is enough most of the time. -But in some other situations, you need to modify the final result to -provide some standardizations like: maximum line width, indentation of -first line different from second, one space between words, two after -sentences, etc. These tasks are very specific and are not included -inside \texttt{renderText} function. Instead, the \texttt{formatText} -function was created and used as post-rendering action in these -situations. - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -# Define post-rendering actions. An empty value means that no -# post-rendering action is applied. -ACTIONS[0]='renderFormats: tif xpm pdf ppm' -ACTIONS[1]='groupByFormat: png tif xpm pdf ppm' -\end{verbatim} -\hrulefill -\caption[Define post-rendering actions.]{Define post-rendering\ -actions. In this figure, post-rendering actions are used to produce\ -tif, xpm, pdf, ppm, image formats (from the base PNG image format)\ -and group them (PNG format included) inside directories. This is, all\ -png files are stored inside a png directory, all xpm files are\ -stored inside a xpm directory, and so on.% - \label{fig:Concepts:Scripts:Configuration:ACTIONS}} -\end{figure} - -\subsection{Start Rendering} - -The start rendering section defines the base action to do when the -current configuration script is called. In this section what you do is -calling one of the following functions: \texttt{renderImage} -(\autoref{sec:Concepts:Scripts:Function:renderImage}), or -\texttt{renderText} -(\autoref{sec:Concepts:Scripts:Function:renderText}). - -\section{Function Scripts} -\hypertarget{sec:Concepts:Scripts:Function}{} -\label{sec:Concepts:Scripts:Function} - -\begin{description} -\item[framework:] trunk/Scripts/Functions/ -\end{description} - -\noindent Function scripts are, in fact, shell functions. A shell -function stores a series of commands for later execution. When the -name of a shell function is used as a simple command name, the list of -commands associated with that function name is executed. Functions -are executed in the context of the current shell; no new process is -created to interpret them (contrast this with the execution of a -shell script). - -\subsection{renderImage} -\hypertarget{sec:Concepts:Scripts:Function:renderImage}{} -\label{sec:Concepts:Scripts:Function:renderImage} - -Inside CentOS Artwork Repository, the \texttt{renderImage} function is -the heart of image production. The \texttt{renderImage} function takes -translation files and apply them to design templates, as specified in -the artwork componet's matching list that is been rendered. The final -result are PNG images based on design templates and translation files. - -Additionally, the \texttt{renderImage} function accepts the following -post-rendering actions: - -\begin{description} - -\item[renderFormats:] The \texttt{renderFormats} function let you -produce different image formats from the base PNG image format. The -amount of image formats you can produce with \texttt{renderFormats} is -limited to the amount of image formats that ImageMagick command line -image manipulation tool can support. - -\item[groupByFormat:] The \texttt{renderByFormat} function let you -group similar image formats inside common directories. - -\item[renderGrub:] The \texttt{renderGrub} function let you produce 14 -colors images from the base PNG image format. The \texttt{renderGrub} -function is used to automate GRUB artwork component image production. -For this function to work, it is required to define the -\texttt{grub.ppm} palette first. - -\item[renderSyslinux:] The \texttt{renderSyslinux} function let you -produce LSS16 images from the base PNG image format. The -\texttt{renderSyslinux} function is used to automate Anaconda prompt -artwork component image production. For this function to work, it is -required to define the \texttt{syslinux.ppm} and \texttt{syslinux.hex} -palettes first. - -\item[renderBrands:] The \texttt{renderBrands} function let you -produce different image formats from the base PNG image format. -Basically, it is does the same of \texttt{renderFormats}, plus two -colors grayscale, and emboss effect convertions that are not included -inside \texttt{renderFormats}. - -\end{description} - -\subsection{renderText} -\hypertarget{sec:Concepts:Scripts:Function:renderText}{} -\label{sec:Concepts:Scripts:Function:renderText} - -The \texttt{renderText} function produce plain text files from text -plain design tempaltes and translation files. The \texttt{renderText} -standardize the text rendering process inside CentOS Artwork -Repository. Additionally, the \texttt{renderText} function accepts the -following post-rendering actions: - -\begin{description} - -\item[formatText:] The \texttt{formatText} function, let you format -plain text files. This function uses the GNU's \texttt{fmt} tool as -base to do all modifications. - -\end{description} - -\subsection{getMatchingList} -\hypertarget{sec:Concepts:Scripts:Function:getMatchingList}{} -\label{sec:Concepts:Scripts:Function:getMatchingList} - -The matching list specifies the relation between design templates and -translation files that artwork components have. The -\texttt{renderImage} and \texttt{renderText} functions require this -information in order to work properly. - -Initially, the matching list was defined explicitly and independently -inside each artwork component's configuration script. Later, as many -of these components had just the same configuration stuff, the code -was reduced and unified inside \texttt{getMatchingList} function. -Inside \texttt{getMatchingList}, there is a case selection statement -where specific matching lists cases are defined, and one default -behaivour that match in thoses cases where none else does. - -The matching list code reduction changed the way you customize artwork -component's matching list. From now on, you look inside configuration -files to be sure that \texttt{ARTCOMP} variable refers to the -appropriate artwork component, and inside \texttt{getMatchingList} -function to define its matching list. For example, when rendering -Anaconda progress, its matching list specifies which translation files -apply which design templates. So, to change the matching list of this -artwork component, you need to edit the function -\texttt{getMatchingList} and set the appropriate relation there, in -the Anaconda progress matching list specification. - -When setting artwork components' matching list, you can use any of the -following configuration available: - -\begin{description} - -\item[Configuration 1:] Specific translation files are applied to -specific design templates. In this configuration you have detailed -control over which translation files are applied to which design -template. - -\begin{verbatim} -MATCHINGLIST="\ -design-template-A.svg: translation-file-1.sed translation-file-2.sed -design-template-B.svg: translation-file-3.sed translation-file-4.sed -" -\end{verbatim} - -Another way to write the previous example is: - -\begin{verbatim} -MATCHINGLIST="\ -design-template-A.svg:\ - translation-file-1.sed\ - translation-file-2.sed -design-template-B.svg:\ - translation-file-3.sed\ - translation-file-4.sed -" -\end{verbatim} - -In the above examples translation files 1 and 2 apply -design-template-A.svg. Likewise, translation files 3 and 4 apply -design-template-B.svg. That was a simple case, but what about if you -have hundreds of translation files to apply to specific design -templates? Lets say, translation files from 1 to 49 apply -design-template-A.svg and translation files from 50 to 99 apply -design-template-B.svg. It would be tiresome to write down the name of -every single file in the above configuration. In these situations you -can ``generate'' the translation files as shown below: - -\begin{verbatim} -MATCHINGLIST="\ -design-template-A.svg:\ - $(for NUMBER in $(sed 1 49);do - echo -n translation-file-${NUMBER}.sed ' ' - done) -design-template-B.svg:\ - $(for NUMBER in $(sed 50 99);do - echo -n translation-file-${NUMBER}.sed ' ' - done) -" -\end{verbatim} - -Another interesting case is when you need to apply hundreds of -translation files to hundreds of design templates, in a file structure -where they both share a common bond path. That is the -\texttt{Identity/Brands} artwork component case. Writing down such a -matching list consumes lot of time. So you can ``generate'' the -entire matching list like the following: - -\begin{verbatim} -MATCHINGLIST="\ -$(for TEMPLATE in $(find $(getPath 'trunk/Identity/Brands')/tpl \ - -name '*.svg' | sed -r 's!.*/Brands/Tpl/(.*)$!\1!' | sort );do - - TRANSLATION=$(find $(getPath \ - 'trunk/Translations/Identity/Brands')/$(echo $TEMPLATE \ - | sed 's!\.svg!!') -name '*.sed' \ - | sed -r 's!^.*/Brands/(.*)$!\1!' \ - | sort | tr '\n' ' ') - - echo $TEMPLATE: $TRANSLATION - done) -" -\end{verbatim} - -\item[Configuration 2:] All translation files are applied to a single -design template. In this configuration all artwork component's -translation files are applied to one design template -(design-template-A.svg for the matter of this case). - -\begin{verbatim} -MATCHINGLIST="design-template-A.svg" -\end{verbatim} - -\item[Configuration 3:] Translation files are applied to design -templates that share a common name. In this configuration translation -files are applied to design templates taking the name part, without -extension, as reference. This means that, if you have a translation -file named \texttt{File-1.sed} you need to have a \texttt{File-1.svg} -inside design templates. This way, \texttt{File-1.sed} can be applied -to \texttt{File-1.svg} and, as result, produce the \texttt{File-1.png} -file. This is the default matching list behaivour. - -\begin{verbatim} -MATCHINGLIST="" -\end{verbatim} - -\end{description} - -\subsection{getPath} - -The \texttt{getPath} function creates the artwork component's absolute -path. Before output the absolute path, \texttt{getPath} removes any -``strange'' character from the final path. For \texttt{getPath} to -work, the relative path to the artwork component should be provided -from \texttt{trunk/}'s directory level on. diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/structure.tex b/Manuals/Filesystem/filesystem-latex/Concepts/structure.tex deleted file mode 100644 index f9faf32..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/structure.tex +++ /dev/null @@ -1,8 +0,0 @@ -% Part : Concepts -% Chapter: The CentOS Visual Structure -% ------------------------------------------------------------ -% $Id: structure.tex 6191 2010-08-02 02:36:14Z al $ -% ------------------------------------------------------------ - -\section{Monolithic Structure} - diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/symbol.tex b/Manuals/Filesystem/filesystem-latex/Concepts/symbol.tex deleted file mode 100644 index c6b26bf..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/symbol.tex +++ /dev/null @@ -1,11 +0,0 @@ -% Part : Concepts -% Chapter: The CentOS Symbol -% ------------------------------------------------------------ -% $Id: symbol.tex 6191 2010-08-02 02:36:14Z al $ -% ------------------------------------------------------------ - -\section{Construction} -\section{Usage} -\section{Colors} -\section{Reductions} -\section{Prohibitions} diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/translations.tex b/Manuals/Filesystem/filesystem-latex/Concepts/translations.tex deleted file mode 100644 index c892f28..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/translations.tex +++ /dev/null @@ -1,147 +0,0 @@ -% Part : Concepts -% Chapter: Translations -% ------------------------------------------------------------ -% $Id: translations.tex 6191 2010-08-02 02:36:14Z al $ -% ------------------------------------------------------------ - -\begin{description} -\item[framework:] trunk/Translations/ -\end{description} - -\noindent Here is where translators locale images. Image localization -is defined inside \texttt{.sed} files, also known as translation -files. Translation files can be common or specific. The given -organization of translation files defines the translation path. - -\section{Common Translations} -\hypertarget{sec:Concepts:Translations:Common}{} - -Common translation files contain common localization or no -localization at all for their related images. They are in the root -directory of the translation path. Common translation files create -common images for all major releases of CentOS Distribution. - -\section{Specific Translations} -\hypertarget{sec:Concepts:Translations:Specific}{} - -Specific translation files contain specific localization for their -related images. Specific translation files are not in the root -directory of the translation path. Specific translation files are -inside directories which describe the type of translation they are -doing. - -\section{Translation Path} -\hypertarget{sec:Concepts:Translations:Path}{} - -Translation path is where we organize common and specific translation -files. Translation path is also used as reference to build the path of -rendered images inside image directory (see -\hyperlink{sec:Concepts:Frameworks:Image}{Image Files}). - -When rendering images, if no REGEX argument is provided to -\texttt{render.sh} identity script, all translation files in the -translation path are read and applied one by one to its related design -template ---as defined in \texttt{getMatchingList} function--- to -produce a translated image. Images produced using the -\texttt{render.sh} identity script have the same name of its -translation file, but with the \texttt{.png} extension instead. - -To control the number of images produced by \texttt{render.sh} -identity script, you need to look into the translation path and -provide a regular expression pattern that matches the translation -path, or paths, related to the image, or images, you want to produce. - -The regular expression pattern you provide to \texttt{render.sh} -identity script is applied to the translation path from its very -beginning. It is not the same to say \texttt{5/es/01-welcome} that -\texttt{01-welcome}, the frist expression matches but the last one -does not. - -When using REGEX you don't need to specify the file extension. It is -removed from translation path before applying the REGEX pattern, so it -doesn't count here. - -\section{Translation Markers} -\hypertarget{sec:Concepts:Translations:Markers}{} - -Translation markers are used in design templates and translation files -as replacement pattern to commit image translation. When -\texttt{render.sh} identity script renders images, translation files -are applied to design templates to get a PNG translated image as -result. In order to have the appropriate translation on the PNG -image, marker defintion in translation files should match markers in -design templates. - -Translation markers can be whatever text you want, but as convenction -we've defined those we use inside CentOS Artwork Repository. This -definition creates a common point of reference to translators and -graphic designers. To have a clean definition of translation markers -is what makes possible that translators and graphic designers can work -together but independently one another. - -\section{Translation Rendering} -\hypertarget{sec:Concepts:Translations:Rendering}{} - -Translation paths and files ---also known as the translation -structure--- are produced using the \texttt{render.sh} translation -script, available in the current translation directory. - -The \texttt{render.sh} translation script combines the content of a -translation template directory ---holding common information--- with -the release-specific information you provide as argument when -executing the script. As result, the \texttt{render.sh} translation -script produces the translation structure that \texttt{render.sh} -identity script needs to create translated images. - -\section{Translation Rendering Script} -\hypertarget{sec:Concepts:Translations:RenderingScripts}{} - -The \texttt{render.sh} translation script produces release-specific -translation directories. Use the \texttt{render.sh} translation script -whenever you need to create a new release-specific translation -directory based on translation template directory. The \texttt{render.sh} -translation script has the following syntax: - -\begin{quote} -\texttt{./render.sh RELEASE ...} -\end{quote} - -The RELEASE argument defines the release number used to create the -release-specific translation directory. You can pass many RELEASE -arguments, separated by one or more spaces, to \texttt{render.sh} -translation script in a single call. If no RELEASE argument is passed -to \texttt{render.sh} translation script then all release-specific -translation directories, available in the current translation -directory, are updated using the translation template as reference. - -Default behaviour of \texttt{render.sh} translation script may be -usefull if all your release-specific translation directories always -have the same information that translation template does. If this is -the case, you only need to maintain the translation template and use -the \texttt{render.sh} translation script to propagate changes to each -release-specific translation directory. - -In contrast, if you are using the \texttt{render.sh} translation -script to create release-specific translation directories that use -translation template as base to introduce non-reusable translations, -you should take care when executing the \texttt{render.sh} translation -script. Otherwise, your non-reusable translations may be replaced -with those in template. - -Inside CentOS Artwork Repository, all translation directories -(reusable and non-reusable) are versioned. If you accidentally -propagate template content to a non-reusable translation, you have the -Subversion's \texttt{revert} and \texttt{update} commands to undo the -mess. - -As general rule, when you use the \texttt{render.sh} translations -script, take care of details and check twice before commit your -translation changes up to CentOS Artwork Repository. - -\section{Translation Template Directory} -\hypertarget{sec:Concepts:Translations:TemplateDirectory}{} - -The translation template directory is located in the current -translation directory and contains common translations for all -release-specific translation directories. It is also used as base to -build non-reusable translation. diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/typeface.tex b/Manuals/Filesystem/filesystem-latex/Concepts/typeface.tex deleted file mode 100644 index 6f2f78e..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/typeface.tex +++ /dev/null @@ -1,11 +0,0 @@ -% Part : Concepts -% Chapter: The CentOS Typeface -% ------------------------------------------------------------ -% $Id: typeface.tex 6191 2010-08-02 02:36:14Z al $ -% ------------------------------------------------------------ - -\section{Construction} -\section{Usage} -\section{Colors} -\section{Reductions} -\section{Prohibitions} diff --git a/Manuals/Filesystem/filesystem-latex/Concepts/typography.tex b/Manuals/Filesystem/filesystem-latex/Concepts/typography.tex deleted file mode 100644 index 0de93dc..0000000 --- a/Manuals/Filesystem/filesystem-latex/Concepts/typography.tex +++ /dev/null @@ -1,8 +0,0 @@ -% Part : Concepts -% Chapter: The CentOS Typography -% ------------------------------------------------------------ -% $Id: typography.tex 6191 2010-08-02 02:36:14Z al $ -% ------------------------------------------------------------ - -\section{Usage} -\section{Colors} diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Firstboot/framework.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Firstboot/framework.tex deleted file mode 100644 index 81bbbd8..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Firstboot/framework.tex +++ /dev/null @@ -1,233 +0,0 @@ -\section{Identity} -\hypertarget{sec:Distribution:Anaconda:Firstboot:Identity}{} -\label{sec:Distribution:Anaconda:Firstboot:Identity} - -\begin{description} -\item[framework:] -trunk/Identity/Themes/\$THEME/Distro/Anaconda/Firstboot/ -\end{description} - -\noindent Here is where CentOS firstboot design templates and image -rendering take place. Firstboot identity file structure is illustrated -in \autoref{fig:Distribution:Anaconda:Firstboot:Identity} and -described in the following sections. - -\begin{figure} -\hrulefill -\begin{verbatim} -trunk/Identity/Themes/$THEME/Distro/Anaconda/Firstboot/ -|-- img -| |-- 3 -| | `-- splash-small.png -| |-- 4 -| | `-- splash-small.png -| |-- 5 -| | `-- splash-small.png -| |-- ... (more releases here) -| `-- firstboot-left.png -|-- render.sh -`-- tpl - |-- firstboot-left.svg - `-- splash-small.svg -\end{verbatim} -\hrulefill -\caption{Firstboot identity framework.% - \label{fig:Distribution:Anaconda:Firstboot:Identity}} -\end{figure} - -\subsection{Design Templates} - -\begin{description} -\item[framework:] -trunk/Identity/Themes/\$THEME/Distro/Anaconda/Firstboot/Tpl/ -\end{description} - -\noindent Here is where Firstboot design templates are stored. -Firstboot design templates control Firstboot's visual style. - -\begin{description} - -\item[firstboot-left.svg:] This design is common for all major -releases of CentOS Distribution. It is visible in all firstboot -screens. In -\autoref{fig:Distribution:Anaconda:Firstboot:Identity:Models}, this -design is illustraded by the number 8. - -\item[splash-small.svg:] This design is specific for each major -release of CentOS Distribution. There is one splash-small.png image -for each major release of CentOS Distribution. This image is visible -only in the first (Welcome) screen of Firstboot. In -\autoref{fig:Distribution:Anaconda:Firstboot:Identity:Models}, this -design is illustraded by number 5. - -\end{description} - -\subsection{Design Models} - -\begin{description} -\item[framework:] -trunk/Identity/Models/Distro/Anaconda/Firstboot/ -\end{description} - -\noindent Here is where firstboot design models are stored. Firstboot -design model is shown in -\autoref{fig:Distribution:Anaconda:Firstboot:Identity:Models} and described -below: - -\begin{figure} -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% -../Identity/Models/Img/en/Distro/Anaconda/Firstboot/splash-small.pdf}} -\end{center} -\caption{Firstboot design model.% - \label{fig:Distribution:Anaconda:Firstboot:Identity:Models}} -\end{figure} - -\begin{description} - -\item[1:] List of labels and a pointer showing in which configuration -screen you are. - -\item[2:] Screen icon. The screen icon is visible in all firstboot -screens. Each firsboot screen may have its own screen icon. - -\item[3:] Screen label. - -\item[4:] Screen description. - -\item[5:] Splash image (splash-small.png). The splash -image is visible in firstboot welcome screen only. - -\item[6:] Configuration stuff. - -\item[7:] Navigation area. Basically two buttons to navegate -configuration back and forward. - -\item[8:] List of labels' background image (firtboot-left.png). This -image is visible in all firstboot screens. - -\end{description} - -\subsection{Image Files} -\hypertarget{sec:Distribution:Anaconda:Firstboot:Identity:Images}{} -\label{sec:Distribution:Anaconda:Firstboot:Identity:Images} - -\begin{description} -\item[framework:] -trunk/Identity/Themes/\$THEME/Distro/Anaconda/Firstboot/Img/ -\end{description} - -\noindent Here is where firstboot final images are stored. - -\subsection{Image Files Rendering} -\hypertarget{sec:Distribution:Anaconda:Firstboot:Identity:ImagesRendering}{} -\label{sec:Distribution:Anaconda:Firstboot:Identity:ImagesRendering} - -\begin{description} -\item[framework:] -trunk/Identity/Themes/\$THEME/Distro/Anaconda/Firstboot/ -\end{description} - -\noindent Here is where you produce firstboot images. The following -rendering examples, based on -\autoref{fig:Distribution:Anaconda:Firstboot:Translations}, illustrate -the firstboot image files rendering process.\\ -\\ -\fbox{\texttt{./render.sh}}\\ -\\ -\fbox{\texttt{./render.sh '(5|6)/splash'}}\\ -\\ -\fbox{\texttt{./render.sh '(firstboot-left|5|4)/splash'}} - -\section{Translations} -\hypertarget{sec:Distribution:Anaconda:Firstboot:Translations}{} -\label{sec:Distribution:Anaconda:Firstboot:Translations} - -\begin{description} -\item[framework:] -trunk/Translations/Identity/Themes/Distro/Anaconda/Firstboot -\end{description} - -\noindent Here is where translators locale firstboot images. Image -localization is defined inside .sed files, also known as translation -files. Translation files can be common or specific. The given -organization of translation files defines the translation path. - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -trunk/Translations/Identity/Themes/Distro/Anaconda/Firstboot -|-- 3 -| `-- splash-small.sed -|-- 4 -| `-- splash-small.sed -|-- 5 -| `-- splash-small.sed -|-- ... (more release directories) -`-- firstboot-left.sed -\end{verbatim} -\hrulefill -\caption{Firstboot translation path.% - \label{fig:Distribution:Anaconda:Firstboot:Translations}} -\end{figure} - -\subsection{Translation Markers} - -In firstboot, markers are used in the file splash-small.svg only, -specifically to set the major release number of CentOS Distribution in -CentOS Release Brand. Since firstboot-left.svg design is common for -all CentOS Distribution there is no need to set any marker on it. - -Markers used in firstboot design templates and translation files are -described in \autoref{tab:Distribution:Anaconda:Firstboot:Markers}. - -\begin{table} -\centering -\begin{tabular}{rl} -\hline -\textbf{Marker} & \textbf{Description}\\ -\hline -=MAJOR\_RELEASE= & Major release number of CentOS Distribution.\\ -\hline -\end{tabular} -\caption{Firstboot translation markers.% - \label{tab:Distribution:Anaconda:Firstboot:Markers}} -\end{table} - -\section{Manuals} -\hypertarget{sec:Distribution:Anaconda:Firstboot:Manuals}{} -\label{sec:Distribution:Anaconda:Firstboot:Manuals} - -\begin{description} -\item[framework:] -trunk/Manuals/Distribution/Anaconda/Firstboot/ -\end{description} - -\noindent Here is where firstboot documentation is stored. If you -want to help improving Firstboot documentation this is the place you -need to go. - -\section{Scripts} -\hypertarget{sec:Distribution:Anaconda:Firstboot:Scripts}{} - -\begin{description} -\item[framework:] trunk/Scripts/Config/Identity/Themes/Distro/Anaconda/Firstboot/ -\end{description} - -\noindent Here is stored the Firstboot \texttt{render.conf.sh} -configuration script. To render Firstboot images correctly, the -\texttt{ARTCOMP} configuration variable inside Anaconda progress -configuration script should be defined as illustrated in -\autoref{fig:Distribution:Anaconda:Firstboot:Scripts:Config}. - -\begin{figure} -\hrulefill -\begin{verbatim} -# Define artwork component. -ARTCOMP='Identity/Themes/Distro/Anaconda/Firstboot' -\end{verbatim} -\hrulefill -\caption{Firstboot configuration layout.% - \label{fig:Distribution:Anaconda:Firstboot:Scripts:Config}} -\end{figure} - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Firstboot/introduction.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Firstboot/introduction.tex deleted file mode 100644 index fd02e0a..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Firstboot/introduction.tex +++ /dev/null @@ -1,8 +0,0 @@ -This chapter describes the visual style of CentOS firstboot -(1.4.27.3-1.el5.centos). Firstboot is the initial system configuration -utility that guides you through a series of steps for easier -configuration of the machine (keyboard layout, language, time zone, -etc.). Firstboot takes place the first time you boot up your installed -system. Firstboot visual style is controlled by a left banner, always -visible, and a splash image, shown on the welcome screen only. - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Firstboot/rebranding.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Firstboot/rebranding.tex deleted file mode 100644 index 42080e5..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Firstboot/rebranding.tex +++ /dev/null @@ -1,126 +0,0 @@ -\section{Rebranding} - -\subsection{Package: redhat-logos} - -The \texttt{redhat-logos} package contains files created by the CentOS -Project to replace the Red Hat ``Shadow Man'' logo and RPM logo. The -Red Hat ``Shadow Man'' logo, RPM, and the RPM logo are trademarks or -registered trademarks of Red Hat, Inc. Firstboot images that need to -be rebranded in \texttt{redhat-logos} package are illustrated in -\autoref{fig:Distribution:Anaconda:Firstboot:Rebranding:Logos}. - -Replacements for these files are available in the Firstboot image -directory ( -\autoref{sec:Distribution:Anaconda:Firstboot:Identity:Images}) of -Firstboot (\autoref{cha:Distribution:Anaconda:Firstboot}) inside your -working copy of CentOS Artwork Repository. - -Once you rebrand the image files inside the SRPM package, you need to -rebuild it with the new brand information. - -\subsection{Package: redhat-artwork} - -The \texttt{redhat-artworks} package contains the themes and icons -that make up the CentOS default look and feel. Relevant files to -firstboot rebranding are described below: - -The following files in \texttt{redhat-artwork} need to be rebranded: - -Once you rebrand the image files inside the \texttt{redhat-artwork} -SRPM package, you need to rebuild it with the new brand information. - -\subsection{Package: firstboot} - -Firstboot messages locale contains the upstream brand, so they need to -be rebranded too. The .po files you need to rebrand are inside the -firstboot package. The \texttt{firstboot} package contains the -firstboot utility that runs after installation. Once you rebrand the -content of .po files inside \texttt{firstboot} SRPM package, you need -to rebuild it with the new brand information. The rebranded .mo files -are created in the installation process. - -\subsection{Package: firstboot-tui} - -The \texttt{firstboot-tui} package contains a text interface for the -\texttt{firstboot} package. Once you rebrand the content of -\texttt{.po} files inside the \texttt{firstboot-tui} SRPM package, you -need to rebuild it with the new brand information. The rebranded -\texttt{.mo} files are created in the installation process. - -\subsection{Package: centos-release} - -The CentOS License Agreement, shown after the welcome screen of -firstboot, is controled by the file \texttt{eula.en\_US} which is -controlled by the \texttt{centos-release} package. The -\texttt{centos-release} package contains the CentOS release notes and -eula files. - -The file \texttt{eula.en\_US} contains the English translation of -CentOS License Agreement. English language is the reference for -specific language translations of CentOS License Agreement. Specific -language translations of CentOS License Agreement are accepted by -Firstboot in the path \texttt{/usr/share/eula/}. - -File names of eula specific language translations should have the -format \texttt{eula.lang} or \texttt{eula.lang\_COUNTRY}. Where -\texttt{lang} is a two-lowercase-letters code representing the -translation language and \texttt{COUNTRY} a two-uppercase-letters code -representing the country of that translation language. Languages' and -countries' codes are specified as described in the standards ISO639 -and ISO3166 respectively. - -When using Anaconda in a language different from English firstboot -checks if there is any eula translation file for the currenct -language. If so, the specific language eula file is loaded and shown -to the user. Otherwise the \texttt{eula.en\_US} file is used. - -The CentOS eula files, described in the previous list, have their own -framework inside CentOS Artwork Repository. They are rendered similar -to images using templates and translation files, as well as rendering -scripts. - -The files \texttt{EULA} and \texttt{eula.en\_US} should have the same -information. The \texttt{GPL} file contains the GPL license with a -brief description of how it applies to CentOS Distribution. - -Once you rebrand the text files inside the \texttt{centos-release} -SRPM package, you need to rebuild it with the new brand information. - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -/usr/share/firstboot/pixmaps/ -|-- shadowman-round-48.png -\end{verbatim} -\hrulefill -\caption{Firstboot rebranding (package: redhat-logos)% - \label{fig:Distribution:Anaconda:Firstboot:Rebranding:Logos}} -\end{figure} - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -/usr/share/firstboot/pixmaps/ -|-- firstboot-left.png -|-- splash-small.png -\end{verbatim} -\hrulefill -\caption{Firstboot rebranding (package: redhat-artwork)% - \label{fig:Distribution:Anaconda:Firstboot:Rebranding:Artwork}} -\end{figure} - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -/usr/share/eula/ -|-- eula.en_US -/usr/share/doc/centos-release-5/ -|-- EULA -|-- GPL -\end{verbatim} -\hrulefill -\caption{Firstboot rebranding (package: centos-release)% - \label{fig:Distribution:Anaconda:Firstboot:Rebranding:Release}} -\end{figure} -\begin{verbatim} -\end{verbatim} diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/chapter.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/chapter.tex deleted file mode 100644 index ad5e616..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/chapter.tex +++ /dev/null @@ -1,29 +0,0 @@ -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ - -\section{Identity} -\hypertarget{sec:Distribution:Anaconda:Header:Identity}{} -\label{sec:Distribution:Anaconda:Header:Identity} -\input{Distribution/Anaconda/Header/identity.tex} - -\section{Translations} -\hypertarget{sec:Distribution:Anaconda:Header:Translations}{} -\label{sec:Distribution:Anaconda:Header:Translations} -\input{Distribution/Anaconda/Header/translations.tex} - -\section{Manuals} -\hypertarget{sec:Distribution:Anaconda:Header:Manuals}{} -\label{sec:Distribution:Anaconda:Header:Manuals} -\input{Distribution/Anaconda/Header/manuals.tex} - -\section{Scripts} -\hypertarget{sec:Distribution:Anaconda:Header:Scripts}{} -\label{sec:Distribution:Anaconda:Header:Scripts} -\input{./Distribution/Anaconda/Header/scripts.tex} - -\section{Packages} -\hypertarget{sec:Distribution:Anaconda:Header:Packages}{} -\label{sec:Distribution:Anaconda:Header:Packages} -\input{Distribution/Anaconda/Header/packages.tex} - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/identity.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/identity.tex deleted file mode 100644 index d249404..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/identity.tex +++ /dev/null @@ -1,85 +0,0 @@ -% Part : Distribution -% Chapter: Anaconda Header -% Section: Identity -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -trunk/Identity/Themes/$THEME/Distro/Anaconda/Header/ -|-- img -| |-- 3 -| | |-- anaconda_header.png.png -| |-- 4 -| |-- 5 -| `-- ... more major releases -|-- render.sh -`-- tpl - `-- anaconda_header.png.svg -\end{verbatim} -\hrulefill -\caption{Anaconda header identity's framework.% - \label{fig:Distribution:Anaconda:Header:Identity}} -\end{figure} - -\subsection{Designs Templates} -\hypertarget{sec:Distribution:Anaconda:Header:Identity:Templates}{} -\label{sec:Distribution:Anaconda:Header:Identity:Templates} - -\begin{itemize} -\item trunk/Identity/Themes/\$THEME/Distro/Anaconda/Header/tpl -\end{itemize} - -\subsection{Design Models} - -\begin{itemize} -\item trunk/Identity/Models/Tpl/Distro/Anaconda/Header/ -\item trunk/Identity/Models/Img/Distro/Anaconda/Header/ -\end{itemize} - -\begin{figure}[!hbp] -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Models/Img/en/Distro/Anaconda/Header/fig-1-anaconda_header.pdf}} -\end{center} -\caption{Anaconda header design model.% - \label{fig:Distribution:Anaconda:Header:Models:Fig1}} -\end{figure} - -\begin{figure}[!hbp] -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Models/Img/en/Distro/Anaconda/Header/fig-2-anaconda_header.pdf}} -\end{center} -\caption{Anaconda header position in the screen.% - \label{fig:Distribution:Anaconda:Header:Models:Fig2}} -\end{figure} - -\subsection{Image Files} -\hypertarget{sec:Distribution:Anaconda:Header:Identity:Images}{} -\label{sec:Distribution:Anaconda:Header:Identity:Images} - -\begin{itemize} -\item \texttt{anaconda\_header.png}: base image format. -\end{itemize} - -\subsection{Image Files Rendering} -\hypertarget{sec:Distribution:Anaconda:Header:Identity:Issues}{} -\label{sec:Distribution:Anaconda:Header:Identity:Issues} -\fbox{\texttt{./render.sh}} -\fbox{\texttt{./render.sh '5'}} -\fbox{\texttt{./render.sh '(3|4|5)'}} - -\subsection{Color Limitations} -\hypertarget{sec:Distribution:Anaconda:Header:Identity:Colors}{} -\label{sec:Distribution:Anaconda:Header:Identity:Colors} - -Anaconda Header does not have color limitations. - -\subsection{Issues} -\hypertarget{sec:Distribution:Anaconda:Header:Issues}{} -\label{sec:Distribution:Anaconda:Header:Issues} - -No one known. diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/manuals.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/manuals.tex deleted file mode 100644 index dfe7989..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/manuals.tex +++ /dev/null @@ -1,10 +0,0 @@ -% Part : Distribution -% Chapter: Anaconda Header -% Section: Scripts -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ -\begin{itemize} -\item trunk/Manuals/Identity/Themes/Distro/Anaconda/Header/ -\end{itemize} - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/packages.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/packages.tex deleted file mode 100644 index 1ac4fc4..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/packages.tex +++ /dev/null @@ -1,9 +0,0 @@ -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ -\begin{itemize} -\item \texttt{redhat-logo} -\begin{itemize} -\item /usr/share/anaconda/pixmaps/anaconda\_header.png -\end{itemize} -\end{itemize} diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/scripts.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/scripts.tex deleted file mode 100644 index 4c44bd6..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/scripts.tex +++ /dev/null @@ -1,9 +0,0 @@ -% Part : Distribution -% Chapter: Anaconda Header -% Section: Scripts -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ -\begin{itemize} -\item trunk/Scripts/Identity/Themes/Distro/Anaconda/Header/ -\end{itemize} diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/translations.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/translations.tex deleted file mode 100644 index 86d13e9..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Header/translations.tex +++ /dev/null @@ -1,30 +0,0 @@ -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ -\begin{figure} -\hrulefill -\begin{verbatim} -trunk/Translations/Identity/Themes/Distro/Anaconda/Header/ -|-- 3 -| `-- anaconda_header.sed -|-- 4 -|-- 5 -|-- ... more major releases -|-- render.sh -`-- tpl - `-- anaconda_header.sed -\end{verbatim} -\hrulefill -\caption{Anaconda header translation framework.% - \label{fig:Distribution:Anaconda:Header:Translations}} -\end{figure} - -% ------------------------------------------------------------ -\subsection{Translation Markers} -\hypertarget{sec:Distribution:Anaconda:Header:Translations:Markers}{} -\label{sec:Distribution:Anaconda:Header:Translations:Markers} - -\begin{itemize} -\item \texttt{=VERSION=}: Major release number of CentOS distribution. -\end{itemize} - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Progress/framework.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Progress/framework.tex deleted file mode 100644 index b33d62a..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Progress/framework.tex +++ /dev/null @@ -1,360 +0,0 @@ -% Part: Distribution -% Chapter: Anaconda progress - Framework -% ------------------------------------------------------------ -% $Id: framework.tex 6207 2010-08-05 13:11:13Z al $ -% ------------------------------------------------------------ - \section{Identity} -\hypertarget{sec:Distribution:Anaconda:Progress:Identity}{} - \label{sec:Distribution:Anaconda:Progress:Identity} - -\begin{description} -\item[framework:] trunk/Identity/Themes/\$THEME/Distro/Anaconda/Progress/ -\end{description} - -\noindent Anaconda progress identity's framework is stored here. -Anaconda progress identity's framework is illustrated in -\autoref{fig:Distribution:Anaconda:Progress:Identity} and described in -the following sections. - -\begin{figure} -\hrulefill -\begin{verbatim} -trunk/Identity/Themes/$THEME/Distro/Anaconda/Progress/ -|-- img -| |-- 3 -| | |-- bn_IN -| | | |-- 01-welcome.png -| | | |-- 02-donate.png -| | | |-- 03-yum.png -| | | `-- ... (more bn_IN language-specific images) -| | |-- cs -| | | |-- 01-welcome.png -| | | |-- 02-donate.png -| | | |-- 03-yum.png -| | | `-- ... (more cs language-specific images) -| | |-- ... (more languages here) -| | |-- first-lowres.png -| | |-- first.png -| | |-- ... (more language directories) -| | |-- progress_first-lowres.png -| | |-- progress_first.png -| | `-- ... (more language directories) -| |-- 4 -| |-- 5 -| `-- ... (more release directories) -|-- render.sh -`-- tpl - |-- first-lowres.svg - |-- first.svg - |-- list.svg - `-- paragraph.svg -\end{verbatim} -\hrulefill -\caption{Anaconda progress identity's framework.% - \label{fig:Distribution:Anaconda:Progress:Identity}} -\end{figure} - -% ------------------------------------------------------------ - \subsection{Design Templates} -\hypertarget{sec:Distribution:Anaconda:Progress:Identity:Templates}{} - \label{sec:Distribution:Anaconda:Progress:Identity:Templates} - -\begin{description} -\item[framework:] trunk/Identity/Themes/\$THEME/Distro/Anaconda/Progress/Tpl/ -\end{description} - -\noindent Anaconda progress design templates are stored here. -Anaconda progress design templates are organized in: Anaconda progress -first slide and Anaconda progress language-specific slides set of -images. - -Anaconda progress first slide is the one used to open the package -installation process. Anaconda progress first slide design has no -translation. It is used just as it is, no matter what the current -Anaconda's installation language be. Anaconda progress first slide -design is controlled by \texttt{first.svg}, and -\texttt{first-lowres.svg} design templates -(\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:First}). -If the screen resolution is less than 800 x 600 pixels, the -\texttt{first-lowres.svg} design is used. If the screen resolution is -equal or greater that 800 x 600 pixels, the \texttt{first.svg} design -is used. - -Anaconda progress language-specific slides set of images start to -rotate a few seconds after progress first slide. Anaconda progress -language-specific slides set of images design is defined by -\texttt{list.svg} -(\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:Paragraph}) -and \texttt{paragraph.svg} -(\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:List}) -design templates. - -Anaconda progress language-specific slides set of images resumes -relevant features coming on the CentOS distribution that is being -installed. As graphic designer, you need not to care very much about -translating Anaconda progress language-specific slides set of images, -this is job for translators. As graphic designer, most of your -attention is focused on how the slides set of images looks like. - -Anaconda progress language-specific slides set of images are loaded -based on Anaconda's installation language. By default, Anaconda's -installation language is English. But you can change Anaconda's -default language in the screen ``Installation Language'' to whatever -your preferred language be. - -If Anaconda's installation language is English, Anaconda progress -language-specific slides set of images are loaded in English. If -Anaconda's installation language is different from English, Anaconda -looks for the language-specific slides set of images that matches the -current Anaconda's installation language and uses them in the -rotation, if that slides set of images exists of course. If there is -no language-specific slides set of images available for the current -Anaconda's installation language, Anaconda uses the English slides set -of images. - -To verify the final look and feel of your Anaconda progress slide -images, you need to render them. To render Anaconda progress slide -images you use the \texttt{render.sh} identity script as described in -``\hyperlink{sec:Distribution:Anaconda:Progress:Identity:Image:Rendering}{Image -Files Rendering}'' -(\autoref{sec:Distribution:Anaconda:Progress:Identity:Image:Rendering}). -The \texttt{render.sh} identity script helps you automate the -rendering process of Anaconda progress slide images. - -% ------------------------------------------------------------ - \subsection{Design Models} -\hypertarget{sec:Distribution:Anaconda:Progress:Identity:Models}{} - \label{sec:Distribution:Anaconda:Progress:Identity:Models} - -\begin{description} -\item[framework:] trunk/Identity/Models/Tpl/Distro/Anaconda/Progress/ -\end{description} - -\noindent Anaconda progress design models are stored here. Anaconda -progress design models are described in -\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:Slides}, -\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:Release}, -\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:First}, -\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:Paragraph}, -and \autoref{fig:Distribution:Anaconda:Progress:Identity:Models:List}. - -\begin{figure}[!hbp] -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% -../Identity/Models/Img/en/Distro/Anaconda/Progress/view-1.pdf}} -\end{center} -\caption[Anaconda progress design model]{Anaconda progress design\ -model. A = ``Header'', B = ``Slide rotation'', C =\ -``Action/Navigation''.% - \label{fig:Distribution:Anaconda:Progress:Identity:Models:Slides}} -\end{figure} - -\begin{figure}[!hbp] -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% -../Identity/Models/Img/en/Distro/Anaconda/Progress/view-2.pdf}} -\end{center} -\caption[Anaconda progress release notes]{Anaconda progress release\ -notes. A = ``Release notes'', B = ``Action/Navigation''.% - \label{fig:Distribution:Anaconda:Progress:Identity:Models:Release}} -\end{figure} - - -\begin{figure}[!hbp] -\begin{center} -\includegraphics[width=0.8\textwidth]{% -../Identity/Models/Img/en/Distro/Anaconda/Progress/first.pdf} -\end{center} -\caption[Anaconda progress first slide template]{Anaconda progress\ -first slide template. A = ``The CentOS Symbol'', B = ``The CentOS\ -Default Artistic Motif'', C = ``The CentOS Release Brand'', D = ``The\ -CentOS Copyright''.% - \label{fig:Distribution:Anaconda:Progress:Identity:Models:First}} -\end{figure} - -\begin{figure}[!hbp] -\begin{center} -\includegraphics[width=0.8\textwidth]{% -../Identity/Models/Img/en/Distro/Anaconda/Progress/list.pdf} -\end{center} -\caption{Anaconda progress list template.% - \label{fig:Distribution:Anaconda:Progress:Identity:Models:Paragraph}} -\end{figure} - -\begin{figure}[!hbp] -\begin{center} -\includegraphics[width=0.8\textwidth]{% -../Identity/Models/Img/en/Distro/Anaconda/Progress/paragraph.pdf} -\end{center} -\caption{Anaconda progress paragraph template.% - \label{fig:Distribution:Anaconda:Progress:Identity:Models:List}} -\end{figure} - -% ------------------------------------------------------------ - \subsection{Image Files} -\hypertarget{sec:Distribution:Anaconda:Progress:Identity:Image}{} - \label{sec:Distribution:Anaconda:Progress:Identity:Image} - -\begin{description} -\item[framework:] trunk/Identity/Themes/\$THEME/Distro/Anaconda/Progress/Img/ -\end{description} - -\noindent Anaconda progress final images are stored here. - -% ------------------------------------------------------------ - \subsection{Image Files Rendering} -\hypertarget{sec:Distribution:Anaconda:Progress:Identity:Image:Rendering}{} - \label{sec:Distribution:Anaconda:Progress:Identity:Image:Rendering} - -\begin{description} -\item[framework:] trunk/Identity/Themes/\$THEME/Distro/Anaconda/Progress/ -\end{description} - -\noindent Here is where you produce Anaconda progress slide images. -Take a look at the following rendering examples based on the -translation path shown in -\autoref{fig:Distribution:Anaconda:Progress:Translations}:\\ -\\ -\fbox{\texttt{./render.sh}}\\ -\\ -\fbox{\texttt{./render.sh '5'}}\\ -\\ -\fbox{\texttt{./render.sh '(3|4|5)'}}\\ -\\ -\fbox{\texttt{./render.sh '5/(progress|first|en)'}}\\ -\\ -\fbox{\texttt{./render.sh '(4|5)/(progress|first|en|es)'}}\\ -\\ -\fbox{\texttt{./render.sh '(4|5)/(en|es)/01-welcome'}} - -% ------------------------------------------------------------ - \section{Translations} -\hypertarget{sec:Distribution:Anaconda:Progress:Translations}{} - \label{sec:Distribution:Anaconda:Progress:Translations}{} - -\begin{description} -\item[framework:] trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ -\end{description} - -\noindent Here is where translators locale Anaconda progress -language-specific slide set of images. Anaconda progress translation -framework is illustrated in -\autoref{fig:Distribution:Anaconda:Progress:Translations}. Anaconda -progress translation framework defines the Anaconda progress slide -images translation path. The translation path shown in -\autoref{fig:Distribution:Anaconda:Progress:Translations} is an -incomplet version of the real one. It was cropped in the sake of -keeping it in just one page. To make yourself a better idea of the -real Anaconda progress translation path, check the one inside your -working copy of CentOS Artwork Repository. That is the one you should -use in order to build your REGEX patterns when rendering Anaconda -progress slide images. - -\begin{figure} -\hrulefill -\begin{verbatim} -trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ -|-- 3 -| |-- bn_IN -| | |-- 01-welcome.sed -| | |-- 02-donate.sed -| | |-- 03-yum.sed -| | `-- ... (more bn_IN translation files) -| |-- ... (more language directories) -| |-- first-lowres.sed -| |-- first.sed -| |-- ... (more language directories) -| |-- progress_first-lowres.sed -| |-- progress_first.sed -| `-- ... (more language directories) -|-- 4 -|-- 5 -|-- ... (more release directories) -|-- render.sh -`-- tpl - |-- bn_IN - | |-- 01-welcome.sed - | |-- 02-donate.sed - | |-- 03-yum.sed - | `-- ... (more bn_IN translation files) - |-- ... (more language directories) - |-- first-lowres.sed - |-- first.sed - |-- ... (more language directories) - |-- progress_first-lowres.sed - |-- progress_first.sed - `-- ... (more language directories) -\end{verbatim} -\hrulefill -\caption{Anaconda progress translation framework.% - \label{fig:Distribution:Anaconda:Progress:Translations}} -\end{figure} - -% ------------------------------------------------------------ - \subsection{Translation Markers} -\hypertarget{sec:Distribution:Anaconda:Progress:Translations:Markers}{} - \label{sec:Distribution:Anaconda:Progress:Translations:Markers} - -In Anaconda progress, translation files and design templates use the -translation markers specified in -\autoref{tab:Distribution:Identity:Markers}. - -\begin{table}[!hbp] -\centering -\begin{tabular}{ll} -\hline -\textbf{Marker}& \textbf{Description}\\ -\hline -=TITLE= & Slide's title.\\ -=DESCRIPTION= & Slide's list description.\\ -=TEXT1-12= & Slide's content.\\ -=URL= & Slide's URL.\\ -=COPYRIGHT= & Copyright notice.\\ -=RELEASE= & CentOS Distribution full release number.\\ -=MAJOR\_RELEASE= & CentOS Distribution major release number.\\ -=MINOR\_RELEASE= & CentOS Distribution update release number.\\ -\hline -\end{tabular} -\caption{Anaconda progress translation markers.% - \label{tab:Distribution:Identity:Markers}} -\end{table} - -% ------------------------------------------------------------ - \section{Manuals} -\hypertarget{sec:Distribution:Anaconda:Progress:Manuals}{} - \label{sec:Distribution:Anaconda:Progress:Manuals} - -\begin{description} -\item[framework:] trunk/Manuals/Distribution/Anaconda/Progress/ -\end{description} - -\noindent Anaconda progress documentation files are prepared here. If -you want to help improving Anaconda progress documentation this is -where you need to go. - -% ------------------------------------------------------------ - \section{Scripts} -\hypertarget{sec:Distribution:Anaconda:Progress:Scripts}{} - \label{sec:Distribution:Anaconda:Progress:Scripts} - -\begin{description} -\item[framework:] trunk/Scripts/Config/Identity/Themes/Distro/Anaconda/Progress/ -\end{description} - -\noindent Here is stored the Anaconda progress \texttt{render.conf.sh} -configuration script. To render Anaconda progress slide images -correctly, the \texttt{ARTCOMP} configuration variable inside Anaconda -progress configuration script should be defined as illustrated in -\autoref{fig:Distribution:Anaconda:Progress:Scripts:Config}. - -\begin{figure} -\hrulefill -\begin{verbatim} -# Define artwork component. -ARTCOMP='Distro/Anaconda/Progress' -\end{verbatim} -\hrulefill -\caption{Anaconda progress configuration layout.% - \label{fig:Distribution:Anaconda:Progress:Scripts:Config}} -\end{figure} - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Progress/introduction.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Progress/introduction.tex deleted file mode 100644 index 3718297..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Progress/introduction.tex +++ /dev/null @@ -1,18 +0,0 @@ -% Part: Distribution -% Chapter: Anaconda Progress - Introduction -% ------------------------------------------------------------ -% $Id: introduction.tex 6019 2010-06-26 06:42:08Z al $ -% ------------------------------------------------------------ - -Anaconda progress takes place after configuration screens and while -packages are being installed. Anaconda progress visual style is -controlled by ``\hyperlink{cha:Distribution:Anaconda:Header}{Anaconda -Header}'' (\autoref{cha:Distribution:Anaconda:Header}), Anaconda -progress first slide, and Anaconda progress language-specific slides -set of images. Anaconda progress language-specific slides set of -images start rotating a few seconds after Anaconda progress first -slide. It is possible for the user to alternate between Anaconda -progress slides and CentOS distribution -``\hyperlink{cha:Distribution:ReleaseNotes}{Release Notes}'' -(\autoref{cha:Distribution:ReleaseNotes}). - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Progress/rebranding.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Progress/rebranding.tex deleted file mode 100644 index d964bd3..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Progress/rebranding.tex +++ /dev/null @@ -1,108 +0,0 @@ -% Part: Distribution -% Chapter: Anaconda Progress - Rebranding -% ------------------------------------------------------------ -% $Id: rebranding.tex 6019 2010-06-26 06:42:08Z al $ -% ------------------------------------------------------------ - -\section{Rebranding} - -\subsection{Package: redhat-logos} - -The \texttt{redhat-logos} package contains files created by the CentOS -Project to replace the Red Hat ``Shadow Man'' logo and RPM logo. The -Red Hat ``Shadow Man'' logo, RPM, and the RPM logo are trademarks or -registered trademarks of Red Hat, Inc. Anaconda Progres images that -need to be rebranded in \texttt{redhat-logos} package are illustrated -in \autoref{fig:Distribution:Anaconda:Progress:Rebranding:Images}. - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -/usr/share/anaconda/pixmaps/ -|-- first-lowres.png -|-- first.png -|-- progress_first-lowres.png -|-- progress_first.png -|-- rnotes -| |-- 01-centos5-welcome.png -| |-- 02-centos5-donate.png -| |-- 03-centos5-yum.png -| |-- 04-centos5-repos.png -| |-- 05-centos5-centosplus.png -| |-- 06-centos5-support.png -| |-- 07-centos5-docs.png -| |-- 08-centos5-wiki.png -| |-- 09-centos5-virtualization.png -| |-- cs -| | |-- 01-centos5-welcome.png -| | |-- 02-centos5-donate.png -| | |-- 03-centos5-yum.png -| | |-- 04-centos5-repos.png -| | |-- 05-centos5-centosplus.png -| | |-- 06-centos5-support.png -| | |-- 07-centos5-docs.png -| | |-- 08-centos5-wiki.png -| | `-- 09-centos5-virtualization.png -| |-- ... (more languages here) -\end{verbatim} -\hrulefill -\caption{Anaconda Progress slide images.% - \label{fig:Distribution:Anaconda:Progress:Rebranding:Images}} -\end{figure} - -Replacements for these files are available in the -\hyperlink{sec:Distribution:Anaconda:Progress:Identity:Image}{Anaconda -Progress image directory} (see -\autoref{sec:Distribution:Anaconda:Progress:Identity:Image}) of -\hyperlink{sec:Distribution:Anaconda:Progress:Identity}{Anaconda -Progress Identity} (see -\autoref{sec:Distribution:Anaconda:Progress:Identity}) inside your -working copy of CentOS Artwork Repository. - -Once you rebrand the image files inside \texttt{redhat-logos} SRPM -package, you need to rebuild it with the new brand information. - -\subsection{Package: centos-release-notes} - -During the installation process Anaconda provides a button labeled -``Release Notes'' (see -\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:Slides}). -When this button is pressed the header and slide areas get hidden and -the available space is used to display CentOS release notes (see -\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:Release}). - -Presently, CentOS release notes are managed online and they don't -appear in Anaconda's release notes screen. A few paragraphs are used -instead to describe how CentOS release notes are managed and how they -can be accessed. - -The \texttt{centos-release-notes} package contains Anaconda Progress -release notes files. Anaconda Progress release notes files are -illustrated in \autoref{fig:Distribution:Anaconda:Progress:Rebranding:ReleaseNotes:Files}. - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -/usr/share/doc/centos-release-notes-5.2/ -|-- RELEASE-NOTES-cs -|-- RELEASE-NOTES-cs.html -|-- RELEASE-NOTES-de -|-- RELEASE-NOTES-de.html -|-- RELEASE-NOTES-en -|-- RELEASE-NOTES-en.html -|-- RELEASE-NOTES-es -|-- RELEASE-NOTES-es.html -`-- ... (more language-specific release notes) -\end{verbatim} -\hrulefill -\caption{Anaconda Progress release notes files.% - \label{fig:Distribution:Anaconda:Progress:Rebranding:ReleaseNotes:Files}} -\end{figure} - -Files in -\autoref{fig:Distribution:Anaconda:Progress:Rebranding:ReleaseNotes:Files} -have their own framework inside CentOS Artwork Repository. Anaconda -Progress release notes are rendered similar to images, using templates -and translation files, as well as rendering scripts. For more -information about release notes rendering see the chapter -``\hyperlink{cha:Distribution:ReleaseNotes}{Release Notes}''. diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/chapter.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/chapter.tex deleted file mode 100644 index 90f8ba0..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/chapter.tex +++ /dev/null @@ -1,31 +0,0 @@ -% part : Distribution -% chapter: Anaconda Prompt -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ - -\section{Identity} -\hypertarget{sec:Distribution:Anaconda:Prompt:Identity}{} -\label{sec:Distribution:Anaconda:Prompt:Identity} -\input{Distribution/Anaconda/Prompt/identity.tex} - -\section{Translations} -\hypertarget{sec:Distribution:Anaconda:Prompt:Translations}{} -\label{sec:Distribution:Anaconda:Prompt:Translations} -\input{Distribution/Anaconda/Prompt/translations.tex} - -\section{Manuals} -\hypertarget{sec:Distribution:Anaconda:Prompt:Manuals}{} -\label{sec:Distribution:Anaconda:Prompt:Manuals} -\input{Distribution/Anaconda/Prompt/manuals.tex} - -\section{Scripts} -\hypertarget{sec:Distribution:Anaconda:Prompt:Scripts}{} -\label{sec:Distribution:Anaconda:Prompt:Scripts} -\input{Distribution/Anaconda/Prompt/scripts.tex} - -\section{Packages} -\hypertarget{sec:Distribution:Anaconda:Prompt:Packages}{} -\label{sec:Distribution:Anaconda:Prompt:Packages} -\input{Distribution/Anaconda/Prompt/packages.tex} - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/identity.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/identity.tex deleted file mode 100644 index 37aac96..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/identity.tex +++ /dev/null @@ -1,129 +0,0 @@ -% Part : Distribution -% Chapter: Anaconda Prompt -% Section: Identity -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -trunk/Identity/Themes/$THEME/Distro/Anaconda/Prompt/ -|-- img -| |-- 3 -| | |-- syslinux-splash-16c.png -| | |-- syslinux-splash-16c.pnm -| | |-- syslinux-splash.log -| | |-- syslinux-splash.lss -| | |-- syslinux-splash.png -| | |-- syslinux-splash.pnm -| | `-- syslinux-splash.ppm -| |-- 4 -| |-- 5 -| `-- ... more major releases -|-- render.sh -`-- tpl - `-- syslinux-splash.svg -\end{verbatim} -\hrulefill -\caption{Anaconda prompt identity's framework.% - \label{fig:Distribution:Anaconda:Prompt:Identity}} -\end{figure} - -\subsection{Designs Templates} -\hypertarget{sec:Distribution:Anaconda:Prompt:Identity:Templates}{} -\label{sec:Distribution:Anaconda:Prompt:Identity:Templates} - -\begin{itemize} -\item trunk/Identity/Themes/\$THEME/Distro/Anaconda/Prompt/tpl -\end{itemize} - -\subsection{Design Models} - -\begin{itemize} -\item trunk/Identity/Models/Tpl/Distro/Anaconda/Prompt/ -\item trunk/Identity/Models/Img/Distro/Anaconda/Prompt/ -\end{itemize} - -\begin{figure}[!hbp] -\begin{center} -\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Models/Img/en/Distro/Anaconda/Prompt/syslinux-splash.pdf} -\end{center} -\caption{Anaconda prompt design model.% - \label{fig:Distribution:Anaconda:Model}} -\end{figure} - -\begin{figure}[!hbp] -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Models/Img/en/Distro/Anaconda/Prompt/fig-1-syslinux-splash.pdf}} -\end{center} -\caption{Anaconda prompt position in the screen.% - \label{fig:Distribution:Anaconda:Prompt:Models:Fig2}} -\end{figure} - -\subsection{Image Files} -\hypertarget{sec:Distribution:Anaconda:Prompt:Identity:Images}{} -\label{sec:Distribution:Anaconda:Prompt:Identity:Images} - -\begin{itemize} -\item \texttt{syslinux-splash.png}: base image format. -\item \texttt{syslinux-splash.ppm}: auxiliar format. -\item \texttt{syslinux-splash.pnm}: auxiliar format. -\item \texttt{syslinux-splash.lss}: image format used by syslinux. -\item \texttt{syslinux-splash-16c.pnm}: 16 colors auxiliar format. -\item \texttt{syslinux-splash-16c.png}: 16 colors auxiliar format. -\item \texttt{syslinux-splash.log}: describes image convertion steps. -\end{itemize} - -\subsection{Image Files Rendering} -\hypertarget{sec:Distribution:Anaconda:Prompt:Identity:Issues}{} -\label{sec:Distribution:Anaconda:Prompt:Identity:Issues} -\fbox{\texttt{./render.sh}} -\fbox{\texttt{./render.sh '5'}} -\fbox{\texttt{./render.sh '(3|4|5)'}} - -\subsection{Color Limitations} -\hypertarget{sec:Distribution:Anaconda:Prompt:Identity:Colors}{} -\label{sec:Distribution:Anaconda:Prompt:Identity:Colors} - -Anaconda Prompt does have color limitations. Initially, Anaconda -Prompt images are rendered without color limitation and later they are -indexed to 16 colors and converted to LSS16 format, as described in -\autoref{sec:Concepts:Identity:Themes:Palettes}. - -\subsection{Issues} -\hypertarget{sec:Distribution:Anaconda:Prompt:Issues}{} -\label{sec:Distribution:Anaconda:Prompt:Issues} - -When creating Anaconda Prompt images some issues were found. They are -described below: - -\begin{itemize} - -\item \textbf{Many Different Colors:} - -As more different colors you have on your design, more are the -possibilities of increasing the amount of noise in your design after -indexing to 16 colors. For example, if you include the actual CentOS -symbol in this image, it ocupies 3 colors (for the orange, green, -violet) in the indexed image which are completely different and -non-reusable in the blue toned background image. - -\item \textbf{The CentOS Symbol:} - -As previously said, if we include the CentOS default symbol in -Anaconda Prompt there is a color degradation and a reduction of -available colors to use in the 16 colors indexed image. - -Some tests were made with variants of CentOS default symbol, but they -all were declined because they bring confusion about which is the -CentOS default symbol. - -It would be very convenient to CentOS visual identity if the CentOS -default symbol could be included, \textit{exactly as it is}, in -Anaconda Prompt images. - -\end{itemize} - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/manuals.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/manuals.tex deleted file mode 100644 index ae24120..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/manuals.tex +++ /dev/null @@ -1,9 +0,0 @@ -% Part : Distribution -% Chapter: Anaconda Prompt -% Section: Manuals -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ -\begin{itemize} -\item trunk/Manuals/Identity/Themes/Distro/Anaconda/Prompt/ -\end{itemize} diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/packages.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/packages.tex deleted file mode 100644 index e3078fb..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/packages.tex +++ /dev/null @@ -1,25 +0,0 @@ -% Part : Distribution -% Chapter: Anaconda Prompt -% Section: Packages -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ - -\begin{itemize} - -\item \textbf{redhat-logos} - -\begin{itemize} -\item /usr/lib/anaconda-runtime/boot/syslinux-splash.png -\item /usr/share/anaconda/pixmaps/syslinux-splash.png -\end{itemize} - -\item \textbf{syslinux} - -\begin{itemize} -\item /isolinux/splash.lss -\end{itemize} -\end{itemize} - -Anaconda Prompt doesn't have messages locale. - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/scripts.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/scripts.tex deleted file mode 100644 index c8e28f1..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/scripts.tex +++ /dev/null @@ -1,9 +0,0 @@ -% Part : Distribution -% Chapter: Anaconda Prompt -% Section: Scripts -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ -\begin{itemize} -\item trunk/Scripts/Identity/Themes/Distro/Anaconda/Prompt/ -\end{itemize} diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/translations.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/translations.tex deleted file mode 100644 index 8e902b1..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Prompt/translations.tex +++ /dev/null @@ -1,33 +0,0 @@ -% Part : Distribution -% Chapter: Anaconda Prompt -% Section: Translations -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -trunk/Translations/Identity/Themes/Distro/Anaconda/Prompt/ -|-- 3 -| `-- syslinux-splash.sed -|-- 4 -|-- 5 -|-- ... more major releases -|-- render.sh -`-- tpl - `-- syslinux-splash.sed -\end{verbatim} -\hrulefill -\caption{Anaconda prompt translation framework.% - \label{fig:Distribution:Anaconda:Prompt:Translations}} -\end{figure} - -% ------------------------------------------------------------ -\subsection{Translation Markers} -\hypertarget{sec:Distribution:Anaconda:Prompt:Translations:Markers}{} -\label{sec:Distribution:Anaconda:Prompt:Translations:Markers} - -\begin{itemize} -\item \texttt{=VERSION=}: Major release number of CentOS Distribution. -\end{itemize} - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/chapter.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/chapter.tex deleted file mode 100644 index 085965e..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/chapter.tex +++ /dev/null @@ -1,29 +0,0 @@ -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ - -\section{Identity} -\hypertarget{sec:Distribution:Anaconda:Splash:Identity}{} -\label{sec:Distribution:Anaconda:Splash:Identity} -\input{Distribution/Anaconda/Splash/identity.tex} - -\section{Translations} -\hypertarget{sec:Distribution:Anaconda:Splash:Translations}{} -\label{sec:Distribution:Anaconda:Splash:Translations} -\input{Distribution/Anaconda/Splash/translations.tex} - -\section{Manuals} -\hypertarget{sec:Distribution:Anaconda:Splash:Manuals}{} -\label{sec:Distribution:Anaconda:Splash:Manuals} -\input{Distribution/Anaconda/Splash/manuals.tex} - -\section{Scripts} -\hypertarget{sec:Distribution:Anaconda:Splash:Scripts}{} -\label{sec:Distribution:Anaconda:Splash:Scripts} -\input{./Distribution/Anaconda/Splash/scripts.tex} - -\section{Packages} -\hypertarget{sec:Distribution:Anaconda:Splash:Packages}{} -\label{sec:Distribution:Anaconda:Splash:Packages} -\input{Distribution/Anaconda/Splash/packages.tex} - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/identity.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/identity.tex deleted file mode 100644 index 0a44087..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/identity.tex +++ /dev/null @@ -1,76 +0,0 @@ -% Part : Distribution -% Chapter: Anaconda Splash -% Section: Identity -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -trunk/Identity/Themes/$THEME/Distro/Anaconda/Splash/ -|-- img -| |-- 3 -| | |-- splash.png.png -| |-- 4 -| |-- 5 -| `-- ... more major releases -|-- render.sh -`-- tpl - `-- splash.png.svg -\end{verbatim} -\hrulefill -\caption{Anaconda splash identity's framework.% - \label{fig:Distribution:Anaconda:Splash:Identity}} -\end{figure} - -\subsection{Designs Templates} -\hypertarget{sec:Distribution:Anaconda:Splash:Identity:Templates}{} -\label{sec:Distribution:Anaconda:Splash:Identity:Templates} - -\begin{itemize} -\item trunk/Identity/Themes/\$THEME/Distro/Anaconda/Splash/tpl -\end{itemize} - -\subsection{Design Models} - -\begin{itemize} -\item trunk/Identity/Models/Tpl/Distro/Anaconda/Splash/ -\item trunk/Identity/Models/Img/Distro/Anaconda/Splash/ -\end{itemize} - -\begin{figure}[!hbp] -\begin{center} -\fbox{\includegraphics[width=0.8\textwidth]{% - /home/centos/artwork/trunk/Identity/Models/Img/en/Distro/Anaconda/Splash/splash.pdf}} -\end{center} -\caption{Anaconda splash design model.% - \label{fig:Distribution:Anaconda:Splash:Models:Fig1}} -\end{figure} - -\subsection{Image Files} -\hypertarget{sec:Distribution:Anaconda:Splash:Identity:Images}{} -\label{sec:Distribution:Anaconda:Splash:Identity:Images} - -\begin{itemize} -\item \texttt{splash.png}: base image format. -\end{itemize} - -\subsection{Image Files Rendering} -\hypertarget{sec:Distribution:Anaconda:Splash:Identity:Issues}{} -\label{sec:Distribution:Anaconda:Splash:Identity:Issues} -\fbox{\texttt{./render.sh}} -\fbox{\texttt{./render.sh '5'}} -\fbox{\texttt{./render.sh '(3|4|5)'}} - -\subsection{Color Limitations} -\hypertarget{sec:Distribution:Anaconda:Splash:Identity:Colors}{} -\label{sec:Distribution:Anaconda:Splash:Identity:Colors} - -Anaconda Splash does not have color limitations. - -\subsection{Issues} -\hypertarget{sec:Distribution:Anaconda:Splash:Issues}{} -\label{sec:Distribution:Anaconda:Splash:Issues} - -No one known. diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/manuals.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/manuals.tex deleted file mode 100644 index ccc01bb..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/manuals.tex +++ /dev/null @@ -1,10 +0,0 @@ -% Part : Distribution -% Chapter: Anaconda Splash -% Section: Scripts -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ -\begin{itemize} -\item trunk/Manuals/Identity/Themes/Distro/Anaconda/Splash/ -\end{itemize} - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/packages.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/packages.tex deleted file mode 100644 index 37ddf15..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/packages.tex +++ /dev/null @@ -1,9 +0,0 @@ -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ -\begin{itemize} -\item \texttt{redhat-logo} -\begin{itemize} -\item /usr/share/anaconda/pixmaps/splash.png -\end{itemize} -\end{itemize} diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/scripts.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/scripts.tex deleted file mode 100644 index 2c93f52..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/scripts.tex +++ /dev/null @@ -1,9 +0,0 @@ -% Part : Distribution -% Chapter: Anaconda Splash -% Section: Scripts -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ -\begin{itemize} -\item trunk/Scripts/Identity/Themes/Distro/Anaconda/Splash/ -\end{itemize} diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/translations.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/translations.tex deleted file mode 100644 index cbf3aac..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Anaconda/Splash/translations.tex +++ /dev/null @@ -1,30 +0,0 @@ -% ------------------------------------------------------------ -% $Id$ -% ------------------------------------------------------------ -\begin{figure} -\hrulefill -\begin{verbatim} -trunk/Translations/Identity/Themes/Distro/Anaconda/Splash/ -|-- 3 -| `-- anaconda_splash.sed -|-- 4 -|-- 5 -|-- ... more major releases -|-- render.sh -`-- tpl - `-- anaconda_splash.sed -\end{verbatim} -\hrulefill -\caption{Anaconda splash translation framework.% - \label{fig:Distribution:Anaconda:Splash:Translations}} -\end{figure} - -% ------------------------------------------------------------ -\subsection{Translation Markers} -\hypertarget{sec:Distribution:Anaconda:Splash:Translations:Markers}{} -\label{sec:Distribution:Anaconda:Splash:Translations:Markers} - -\begin{itemize} -\item \texttt{=VERSION=}: Major release number of CentOS distribution. -\end{itemize} - diff --git a/Manuals/Filesystem/filesystem-latex/Distribution/Backgrounds/introduction.tex b/Manuals/Filesystem/filesystem-latex/Distribution/Backgrounds/introduction.tex deleted file mode 100644 index 459d5b8..0000000 --- a/Manuals/Filesystem/filesystem-latex/Distribution/Backgrounds/introduction.tex +++ /dev/null @@ -1,89 +0,0 @@ -The Backgrounds directory is probably the Themes' core compoent. -Inside Backgrounds/ directory you produce background images that are -reused by almost all theme's art works (e.g., Distribution, Websites, -Promotion, etc.). - -The Backgrounds/ directory structure can contain directories to help -you organize the design process. - - Img/: In this directory is where you store all background images - (e.g., .png, .jpg, .xpm, etc.). This directory is required - by rendering scripts. - - Tpl/: In this directory is where you store all scalable vector - graphics (e.g., .svg) files. This directory is required by - rendering scripts. - - Xcf/: In this directory is where you store all Gimp's project - files (e.g, .xcf). This directory is optional. If you can - create a beautiful background images using scalable vector - graphics only, then there is no need to use Gimp to produce - background images. Of course, you can merge Gimp's power - with Inkscape's power to produce images based on them. In - this last case you need this directory. - -Inside Backgrounds/ you can create your vectorial designs using -Inkscape and your background images using Gimp. Later you can export -your background image as png and load it in your vectorial design -using Inkscape's import feautre. Note that 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 \textit{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. - diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.aux deleted file mode 100644 index a75eddf..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.aux +++ /dev/null @@ -1,102 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{3}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Installation}{3}{section.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Subversion}{3}{subsection.2.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}ImageMagick}{4}{subsection.2.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{5}{subsection.2.6}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Configuration}{6}{section.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{8}{subsubsection.3.4.1}} -\newlabel{sec:Configuration:Account}{{3.4.1}{8}{Account Registration\relax }{subsubsection.3.4.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2}} -\newlabel{sec:Configuration:User:Privileges}{{3.4.2}{9}{Account Privileges\relax }{subsubsection.3.4.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5}} -\newlabel{sec:Configuration:Environment}{{3.5}{9}{Shell Environment\relax }{subsection.3.5}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Framework}{10}{section.4}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3}} -\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Firstboot translation markers.}}{12}{table.1}} -\newlabel{tab:Identity:Markers}{{1}{12}{Markers\relax }{table.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.4}Images}{12}{subsubsection.4.1.4}} -\newlabel{sec:Identity:Images}{{4.1.4}{12}{Images\relax }{subsubsection.4.1.4}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.5}Models}{12}{subsubsection.4.1.5}} -\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Firstboot design model.}}{13}{figure.1}} -\newlabel{fig:Identity:Design:Model}{{1}{13}{Models\relax }{figure.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.6}Rendering}{14}{subsubsection.4.1.6}} -\newlabel{sec:Identity:Rendering}{{4.1.6}{14}{Rendering\relax }{subsubsection.4.1.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.2}Translations}{14}{subsection.4.2}} -\newlabel{sec:Translations}{{4.2}{14}{Translations\relax }{subsection.4.2}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{15}{subsubsection.4.2.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{15}{subsubsection.4.2.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{15}{subsubsection.4.2.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}Manuals}{16}{subsection.4.3}} -\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces Firstboot translation path.}}{16}{figure.2}} -\newlabel{fig:Translation:Path}{{2}{16}{Translation Path\relax }{figure.2}{}} -\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Rendering design model.}}{17}{figure.3}} -\newlabel{fig:Scripts:Rendering}{{3}{17}{Rendering\relax }{figure.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Scripts}{17}{subsection.4.4}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{17}{subsubsection.4.4.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{18}{subsubsection.4.4.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{18}{subsubsection.4.4.3}} -\@writefile{toc}{\contentsline {section}{\numberline {5}Rebranding}{18}{section.5}} -\newlabel{sec:Rebranding}{{5}{18}{Rebranding\relax }{section.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}Images}{19}{subsection.5.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{19}{subsubsection.5.1.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.1.2}redhat-artwork}{19}{subsubsection.5.1.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Messages Locale}{20}{subsection.5.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.2.1}firstboot}{20}{subsubsection.5.2.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.2.2}firstboot-tui}{20}{subsubsection.5.2.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {5.3}License Agreement}{20}{subsection.5.3}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.3.1}centos-release}{20}{subsubsection.5.3.1}} -\@writefile{toc}{\contentsline {section}{\numberline {6}GNU Free Documentation License}{21}{section.6}} -\newlabel{sec:License-GFDL-0}{{6}{22}{Preamble\relax }{section*.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{22}{subsection.6.1}} -\newlabel{sec:License-GFDL-1}{{6.1}{22}{Applicability And Definitions\relax }{subsection.6.1}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{24}{subsection.6.2}} -\newlabel{sec:License-GFDL-2}{{6.2}{24}{Verbatim Copying\relax }{subsection.6.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{24}{subsection.6.3}} -\newlabel{sec:License-GFDL-3}{{6.3}{24}{Copying In Quantity\relax }{subsection.6.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.4}Modifications}{25}{subsection.6.4}} -\newlabel{sec:License-GFDL-4}{{6.4}{25}{Modifications\relax }{subsection.6.4}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.5}Combining Documents}{28}{subsection.6.5}} -\newlabel{sec:License-GFDL-5}{{6.5}{28}{Combining Documents\relax }{subsection.6.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{28}{subsection.6.6}} -\newlabel{sec:License-GFDL-6}{{6.6}{28}{Collections Of Documents\relax }{subsection.6.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{28}{subsection.6.7}} -\newlabel{sec:License-GFDL-7}{{6.7}{28}{Aggregation With Independent Works\relax }{subsection.6.7}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.8}Translation}{29}{subsection.6.8}} -\newlabel{sec:License-GFDL-8}{{6.8}{29}{Translation\relax }{subsection.6.8}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.9}Termination}{29}{subsection.6.9}} -\newlabel{sec:License-GFDL-9}{{6.9}{29}{Termination\relax }{subsection.6.9}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{30}{subsection.6.10}} -\newlabel{sec:License-GFDL-10}{{6.10}{30}{Future Revisions Of This License\relax }{subsection.6.10}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{30}{subsection.6.11}} -\newlabel{sec:License-GFDL-11}{{6.11}{30}{How to use this License for your documents\relax }{subsection.6.11}{}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.log deleted file mode 100644 index 6ca2c6b..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.log +++ /dev/null @@ -1,352 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 31 MAR 2010 11:07 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size12.clo -File: size12.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/graphics/graphicx.sty -Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks14 -) -(/usr/share/texmf/tex/latex/graphics/graphics.sty -Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/trig.sty -Package: trig 1999/03/16 v1.09 sin cos tan (DPC) -) -(/usr/share/texmf/tex/latex/graphics/graphics.cfg -File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive -) -Package graphics Info: Driver file: pdftex.def on input line 80. - -(/usr/share/texmf/tex/latex/graphics/pdftex.def -File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex -\Gread@gobject=\count87 -)) -\Gin@req@height=\dimen103 -\Gin@req@width=\dimen104 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX -\@linkdim=\dimen105 -\Hy@linkcounter=\count88 -\Hy@pagecounter=\count89 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count90 -\Field@Width=\dimen106 -\Fld@charsize=\dimen107 -\Choice@toks=\toks15 -\Field@toks=\toks16 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count91 -\c@Hfootnote=\count92 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count93 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 16. -LaTeX Font Info: ... okay on input line 16. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 16. -LaTeX Font Info: ... okay on input line 16. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 16. -LaTeX Font Info: ... okay on input line 16. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 16. -LaTeX Font Info: ... okay on input line 16. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 16. -LaTeX Font Info: ... okay on input line 16. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 16. -LaTeX Font Info: ... okay on input line 16. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 16. -LaTeX Font Info: ... okay on input line 16. - -(/usr/share/texmf/tex/context/base/supp-pdf.tex -(/usr/share/texmf/tex/context/base/supp-mis.tex -loading : Context Support Macros / Miscellaneous (2004.10.26) -\protectiondepth=\count94 -\scratchcounter=\count95 -\scratchtoks=\toks17 -\scratchdimen=\dimen108 -\scratchskip=\skip43 -\scratchmuskip=\muskip11 -\scratchbox=\box26 -\scratchread=\read1 -\scratchwrite=\write4 -\zeropoint=\dimen109 -\onepoint=\dimen110 -\onebasepoint=\dimen111 -\minusone=\count96 -\thousandpoint=\dimen112 -\onerealpoint=\dimen113 -\emptytoks=\toks18 -\nextbox=\box27 -\nextdepth=\dimen114 -\everyline=\toks19 -\!!counta=\count97 -\!!countb=\count98 -\recursecounter=\count99 -) -loading : Context Support Macros / PDF (2004.03.26) -\nofMPsegments=\count100 -\nofMParguments=\count101 -\MPscratchCnt=\count102 -\MPscratchDim=\dimen115 -\MPnumerator=\count103 -\everyMPtoPDFconversion=\toks20 -) -Package hyperref Info: Link coloring OFF on input line 16. - (/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count104 -) -LaTeX Info: Redefining \ref on input line 16. -LaTeX Info: Redefining \pageref on input line 16. - (./Manual.out) -(./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <14.4> on input line 19. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 19. -LaTeX Font Info: Try loading font information for OMS+cmr on input line 29. - (/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10.95> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 29. - (./Manual.toc -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 3. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 3. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 3. - -[1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] [2]) -\tf@toc=\write5 -\openout5 = `Manual.toc'. - - -(./sections/introduction.tex) (../../../../../installation.tex -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 25. - [3] -Overfull \hbox (8.37456pt too wide) in paragraph at lines 53--54 -[][]$\OT1/cmtt/m/n/12 http : / / wiki . centos . org / AdditionalResources / Re -positories$[] - [] - -Missing character: There is no � in font cmr12! -Missing character: There is no � in font cmr12! -[4] -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <12> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 94. - [5]) (../../../../../configuration.tex [6] -Overfull \hbox (11.3752pt too wide) in paragraph at lines 64--64 -[]\OT1/cmtt/m/n/12 # Squid only knows about standardized HTTP request met -hods.[] - [] - - -Overfull \hbox (11.3752pt too wide) in paragraph at lines 64--64 -[]\OT1/cmtt/m/n/12 # You can add up to 20 additional "extension" methods -here.[] - [] - -[7] -Overfull \hbox (23.88292pt too wide) in paragraph at lines 96--97 -[]\OT1/cmtt/m/n/12 svn co https://projects.centos.org/svn/artwork $\OMS/cmsy/m/ -n/12 ^^X$\OT1/cmtt/m/n/12 /Desktop/ - [] - -[8] -Overfull \hbox (32.24086pt too wide) in paragraph at lines 161--168 -\OT1/cmr/m/n/12 CentOS Art-work Repos-i-tory, we de-cided to de-fine the \OT1/c -mr/bx/n/12 CentOS[]ARTWORK[]WC - [] - -[9]) (./sections/framework.tex -Underfull \hbox (badness 10000) in paragraph at lines 9--10 - - [] - - -Underfull \hbox (badness 10000) in paragraph at lines 16--17 - - [] - -[10] -Overfull \hbox (15.76491pt too wide) in paragraph at lines 63--68 -\OT1/cmr/m/n/12 ex-ported as PNG im-age. As con-ven-tion, we use the word `CENT -OSARTWORK' - [] - -[11] -Underfull \hbox (badness 10000) in paragraph at lines 104--105 - - [] - - -Underfull \hbox (badness 10000) in paragraph at lines 117--118 - - [] - - -<../../../../../../Identity/Models/Distro/Anaconda/Firstboot/img/build-0.pdf, i -d=416, 642.4pt x 481.8pt> -File: ../../../../../../Identity/Models/Distro/Anaconda/Firstboot/img/build-0.p -df Graphic file (type pdf) - - [12] [13 <../../../../../../Identity/Models/Distro/Anaconda/Firstboot/img/bu -ild-0.pdf>] -Underfull \hbox (badness 10000) in paragraph at lines 180--181 - - [] - -[14] [15] -Underfull \hbox (badness 10000) in paragraph at lines 269--270 - - [] - -[16] -<../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf, id=458, 5 -28.97626pt x 519.9425pt> -File: ../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf Graph -ic file (type pdf) - - -Underfull \hbox (badness 10000) in paragraph at lines 297--298 - - [] - -[17 <../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf>]) -(./sections/rebranding.tex -Overfull \hbox (2.56557pt too wide) in paragraph at lines 13--16 -[]\OT1/cmr/m/n/12 CentOS Brands and art-works are or-ga-nized in-side CentOS Ar -t-work Repos- - [] - -[18] [19] [20]) (../../../../../Licenses/GFDL.tex -Underfull \hbox (badness 10000) in paragraph at lines 5--14 - - [] - -[21] [22] [23] [24] [25] [26] [27] [28] [29] -Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 document under the terms of the GNU Free Documentation Li -cense,[] - [] - - -Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 Version 1.2 or any later version published by the Free So -ftware[] - [] - - -Overfull \hbox (5.2002pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 Foundation; with no Invariant Sections, no Front-Cover Te -xts,[] - [] - - -Overfull \hbox (11.3752pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 and no Back-Cover Texts. A copy of the license is includ -ed in[] - [] - - -Overfull \hbox (5.2002pt too wide) in paragraph at lines 425--425 -[] \OT1/cmtt/m/n/12 with the Invariant Sections being LIST THEIR TITLES, with - the[] - [] - -) [30] [31] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 2822 strings out of 94500 - 38867 string characters out of 1176766 - 89311 words of memory out of 1000000 - 5861 multiletter control sequences out of 10000+50000 - 11008 words of font info for 39 fonts, out of 500000 for 2000 - 582 hyphenation exceptions out of 1000 - 27i,8n,36p,222b,267s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 540 PDF objects out of 300000 - 108 named destinations out of 131072 - 523 words of extra memory for PDF output out of 65536 - -Output written on Manual.pdf (31 pages, 274955 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.out deleted file mode 100644 index f51c4dd..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.out +++ /dev/null @@ -1,62 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Introduction}{} -\BOOKMARK [1][-]{section.2}{Installation}{} -\BOOKMARK [2][-]{subsection.2.1}{Subversion}{section.2} -\BOOKMARK [2][-]{subsection.2.2}{Inkscape}{section.2} -\BOOKMARK [2][-]{subsection.2.3}{ImageMagick}{section.2} -\BOOKMARK [2][-]{subsection.2.4}{Netpbm}{section.2} -\BOOKMARK [2][-]{subsection.2.5}{Syslinux}{section.2} -\BOOKMARK [2][-]{subsection.2.6}{GNU Image Manipulation Program}{section.2} -\BOOKMARK [2][-]{subsection.2.7}{GNU Core Utilities}{section.2} -\BOOKMARK [2][-]{subsection.2.8}{LaTeX}{section.2} -\BOOKMARK [1][-]{section.3}{Configuration}{} -\BOOKMARK [2][-]{subsection.3.1}{Firewall}{section.3} -\BOOKMARK [2][-]{subsection.3.2}{Subversion Behind Squid}{section.3} -\BOOKMARK [3][-]{subsubsection.3.2.1}{Subversion Client Configuration}{subsection.3.2} -\BOOKMARK [3][-]{subsubsection.3.2.2}{Squid Server Configuration}{subsection.3.2} -\BOOKMARK [2][-]{subsection.3.3}{Working Copy}{section.3} -\BOOKMARK [2][-]{subsection.3.4}{User Identification}{section.3} -\BOOKMARK [3][-]{subsubsection.3.4.1}{Account Registration}{subsection.3.4} -\BOOKMARK [3][-]{subsubsection.3.4.2}{Account Privileges}{subsection.3.4} -\BOOKMARK [2][-]{subsection.3.5}{Shell Environment}{section.3} -\BOOKMARK [3][-]{subsubsection.3.5.1}{Relative Paths}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.2}{Absolute Paths}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.3}{Environment Variable Definition}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.4}{Environment Variable Initialization}{subsection.3.5} -\BOOKMARK [1][-]{section.4}{Framework}{} -\BOOKMARK [2][-]{subsection.4.1}{Identity}{section.4} -\BOOKMARK [3][-]{subsubsection.4.1.1}{Designs}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.2}{Export Id}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.3}{Markers}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.4}{Images}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.5}{Models}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.6}{Rendering}{subsection.4.1} -\BOOKMARK [2][-]{subsection.4.2}{Translations}{section.4} -\BOOKMARK [3][-]{subsubsection.4.2.1}{Common Translations}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.2}{Specific Translations}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.3}{Translation Path}{subsection.4.2} -\BOOKMARK [2][-]{subsection.4.3}{Manuals}{section.4} -\BOOKMARK [2][-]{subsection.4.4}{Scripts}{section.4} -\BOOKMARK [3][-]{subsubsection.4.4.1}{Rendering}{subsection.4.4} -\BOOKMARK [3][-]{subsubsection.4.4.2}{Pre-rendering}{subsection.4.4} -\BOOKMARK [3][-]{subsubsection.4.4.3}{Post-rendering}{subsection.4.4} -\BOOKMARK [1][-]{section.5}{Rebranding}{} -\BOOKMARK [2][-]{subsection.5.1}{Images}{section.5} -\BOOKMARK [3][-]{subsubsection.5.1.1}{redhat-logos}{subsection.5.1} -\BOOKMARK [3][-]{subsubsection.5.1.2}{redhat-artwork}{subsection.5.1} -\BOOKMARK [2][-]{subsection.5.2}{Messages Locale}{section.5} -\BOOKMARK [3][-]{subsubsection.5.2.1}{firstboot}{subsection.5.2} -\BOOKMARK [3][-]{subsubsection.5.2.2}{firstboot-tui}{subsection.5.2} -\BOOKMARK [2][-]{subsection.5.3}{License Agreement}{section.5} -\BOOKMARK [3][-]{subsubsection.5.3.1}{centos-release}{subsection.5.3} -\BOOKMARK [1][-]{section.6}{GNU Free Documentation License}{} -\BOOKMARK [2][-]{subsection.6.1}{Applicability And Definitions}{section.6} -\BOOKMARK [2][-]{subsection.6.2}{Verbatim Copying}{section.6} -\BOOKMARK [2][-]{subsection.6.3}{Copying In Quantity}{section.6} -\BOOKMARK [2][-]{subsection.6.4}{Modifications}{section.6} -\BOOKMARK [2][-]{subsection.6.5}{Combining Documents}{section.6} -\BOOKMARK [2][-]{subsection.6.6}{Collections Of Documents}{section.6} -\BOOKMARK [2][-]{subsection.6.7}{Aggregation With Independent Works}{section.6} -\BOOKMARK [2][-]{subsection.6.8}{Translation}{section.6} -\BOOKMARK [2][-]{subsection.6.9}{Termination}{section.6} -\BOOKMARK [2][-]{subsection.6.10}{Future Revisions Of This License}{section.6} -\BOOKMARK [2][-]{subsection.6.11}{How to use this License for your documents}{section.6} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.pdf deleted file mode 100644 index a1f66d8..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.toc deleted file mode 100644 index b7d919a..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.toc +++ /dev/null @@ -1,62 +0,0 @@ -\contentsline {section}{\numberline {1}Introduction}{3}{section.1} -\contentsline {section}{\numberline {2}Installation}{3}{section.2} -\contentsline {subsection}{\numberline {2.1}Subversion}{3}{subsection.2.1} -\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2} -\contentsline {subsection}{\numberline {2.3}ImageMagick}{4}{subsection.2.3} -\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4} -\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5} -\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{5}{subsection.2.6} -\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7} -\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8} -\contentsline {section}{\numberline {3}Configuration}{6}{section.3} -\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1} -\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2} -\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1} -\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2} -\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3} -\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4} -\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{8}{subsubsection.3.4.1} -\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2} -\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5} -\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1} -\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2} -\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3} -\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4} -\contentsline {section}{\numberline {4}Framework}{10}{section.4} -\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1} -\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1} -\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2} -\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3} -\contentsline {subsubsection}{\numberline {4.1.4}Images}{12}{subsubsection.4.1.4} -\contentsline {subsubsection}{\numberline {4.1.5}Models}{12}{subsubsection.4.1.5} -\contentsline {subsubsection}{\numberline {4.1.6}Rendering}{14}{subsubsection.4.1.6} -\contentsline {subsection}{\numberline {4.2}Translations}{14}{subsection.4.2} -\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{15}{subsubsection.4.2.1} -\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{15}{subsubsection.4.2.2} -\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{15}{subsubsection.4.2.3} -\contentsline {subsection}{\numberline {4.3}Manuals}{16}{subsection.4.3} -\contentsline {subsection}{\numberline {4.4}Scripts}{17}{subsection.4.4} -\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{17}{subsubsection.4.4.1} -\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{18}{subsubsection.4.4.2} -\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{18}{subsubsection.4.4.3} -\contentsline {section}{\numberline {5}Rebranding}{18}{section.5} -\contentsline {subsection}{\numberline {5.1}Images}{19}{subsection.5.1} -\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{19}{subsubsection.5.1.1} -\contentsline {subsubsection}{\numberline {5.1.2}redhat-artwork}{19}{subsubsection.5.1.2} -\contentsline {subsection}{\numberline {5.2}Messages Locale}{20}{subsection.5.2} -\contentsline {subsubsection}{\numberline {5.2.1}firstboot}{20}{subsubsection.5.2.1} -\contentsline {subsubsection}{\numberline {5.2.2}firstboot-tui}{20}{subsubsection.5.2.2} -\contentsline {subsection}{\numberline {5.3}License Agreement}{20}{subsection.5.3} -\contentsline {subsubsection}{\numberline {5.3.1}centos-release}{20}{subsubsection.5.3.1} -\contentsline {section}{\numberline {6}GNU Free Documentation License}{21}{section.6} -\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{22}{subsection.6.1} -\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{24}{subsection.6.2} -\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{24}{subsection.6.3} -\contentsline {subsection}{\numberline {6.4}Modifications}{25}{subsection.6.4} -\contentsline {subsection}{\numberline {6.5}Combining Documents}{28}{subsection.6.5} -\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{28}{subsection.6.6} -\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{28}{subsection.6.7} -\contentsline {subsection}{\numberline {6.8}Translation}{29}{subsection.6.8} -\contentsline {subsection}{\numberline {6.9}Termination}{29}{subsection.6.9} -\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{30}{subsection.6.10} -\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{30}{subsection.6.11} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/manual.tex deleted file mode 100644 index cf74a63..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/manual.tex +++ /dev/null @@ -1,49 +0,0 @@ -\documentclass[12pt]{article} -\usepackage[pdftex]{graphicx} -\usepackage{hyperref} -\hypersetup{pdfauthor={Alain Reguera Delgado},% - pdftitle={Firstboot Visual Style},% - pdfsubject={CentOS Corporate Visual Identity}% - } - -% Tell LaTeX how to hyphenate a word. Don't hyphenate the following -% words: -\hyphenation{CentOS CENTOSARTWORK} - -\title{Firstboot Visual Style} -\author{Alain Reguera Delgado} - -\begin{document} - -\maketitle - -\begin{abstract} - -This article describes the visual style of CentOS firstboot -(1.4.27.3-1.el5.centos). Firstboot is the initial system configuration -utility that guides you through a series of steps for easier -configuration of the machine (keyboard layout, language, time zone, -etc.). Firstboot takes place the first time you boot up your installed -system. - -Copyright \copyright\ 2010 The CentOS Project. Permission is granted -to copy, distribute and/or modify this document under the terms of the -GNU Free Documentation License, Version 1.2 or any later version -published by the Free Software Foundation; with no Invariant Sections, -no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled ``GNU Free Documentation -License''. - -\end{abstract} - -\tableofcontents - -\input{sections/introduction.tex} -\input{../../../../../installation.tex} -\input{../../../../../configuration.tex} -\input{sections/framework.tex} -\input{sections/rebranding.tex} - -\input{../../../../../Licenses/GFDL.tex} - -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.aux deleted file mode 100644 index 2213323..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.aux +++ /dev/null @@ -1,100 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{3}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Installation}{3}{section.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Subversion}{3}{subsection.2.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}ImageMagick}{4}{subsection.2.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{5}{subsection.2.6}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{5}{subsection.2.7}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Configuration}{6}{section.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{6}{subsection.3.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{6}{subsubsection.3.2.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{8}{subsubsection.3.4.1}} -\newlabel{sec:Configuration:Account}{{3.4.1}{8}{Account Registration\relax }{subsubsection.3.4.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{8}{subsubsection.3.4.2}} -\newlabel{sec:Configuration:User:Privileges}{{3.4.2}{8}{Account Privileges\relax }{subsubsection.3.4.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5}} -\newlabel{sec:Configuration:Environment}{{3.5}{9}{Shell Environment\relax }{subsection.3.5}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{9}{subsubsection.3.5.4}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Framework}{10}{section.4}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1}} -\newlabel{sec:Identity}{{4.1}{10}{Identity\relax }{subsection.4.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1}} -\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Anaconda Header translation markers.}}{11}{table.1}} -\newlabel{tab:Identity:Markers}{{1}{11}{Markers\relax }{table.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.4}Images}{11}{subsubsection.4.1.4}} -\newlabel{sec:Identity:Images}{{4.1.4}{11}{Images\relax }{subsubsection.4.1.4}{}} -\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Anaconda Header design model. A = 800 pixels, B = 48 pixels, C = 88 pixels.}}{12}{figure.1}} -\newlabel{fig:Identity:Design:Model0}{{1}{12}{Models\relax }{figure.1}{}} -\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces Anaconda Header left side. A = 20 pixels.}}{12}{figure.2}} -\newlabel{fig:Identity:Design:Model1}{{2}{12}{Models\relax }{figure.2}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.5}Models}{12}{subsubsection.4.1.5}} -\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Anaconda Header right side. A = 20 pixels.}}{12}{figure.3}} -\newlabel{fig:Identity:Design:Model2}{{3}{12}{Models\relax }{figure.3}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.6}Rendering}{13}{subsubsection.4.1.6}} -\newlabel{sec:Identity:Rendering}{{4.1.6}{13}{Rendering\relax }{subsubsection.4.1.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.2}Translations}{13}{subsection.4.2}} -\newlabel{sec:Translations}{{4.2}{13}{Translations\relax }{subsection.4.2}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{13}{subsubsection.4.2.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{13}{subsubsection.4.2.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{14}{subsubsection.4.2.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}Manuals}{14}{subsection.4.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Scripts}{15}{subsection.4.4}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{15}{subsubsection.4.4.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{15}{subsubsection.4.4.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{15}{subsubsection.4.4.3}} -\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces Rendering design model.}}{16}{figure.4}} -\newlabel{fig:Scripts:Rendering}{{4}{16}{Rendering\relax }{figure.4}{}} -\@writefile{toc}{\contentsline {section}{\numberline {5}Rebranding}{17}{section.5}} -\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}Images}{17}{subsection.5.1}} -\newlabel{sec:Rebranding:Images}{{5.1}{17}{Images\relax }{subsection.5.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{17}{subsubsection.5.1.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Messages Locale}{17}{subsection.5.2}} -\@writefile{toc}{\contentsline {section}{\numberline {6}GNU Free Documentation License}{18}{section.6}} -\newlabel{sec:License-GFDL-0}{{6}{18}{Preamble\relax }{section*.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{18}{subsection.6.1}} -\newlabel{sec:License-GFDL-1}{{6.1}{18}{Applicability And Definitions\relax }{subsection.6.1}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{20}{subsection.6.2}} -\newlabel{sec:License-GFDL-2}{{6.2}{20}{Verbatim Copying\relax }{subsection.6.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{21}{subsection.6.3}} -\newlabel{sec:License-GFDL-3}{{6.3}{21}{Copying In Quantity\relax }{subsection.6.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.4}Modifications}{21}{subsection.6.4}} -\newlabel{sec:License-GFDL-4}{{6.4}{21}{Modifications\relax }{subsection.6.4}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.5}Combining Documents}{24}{subsection.6.5}} -\newlabel{sec:License-GFDL-5}{{6.5}{24}{Combining Documents\relax }{subsection.6.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{24}{subsection.6.6}} -\newlabel{sec:License-GFDL-6}{{6.6}{24}{Collections Of Documents\relax }{subsection.6.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{25}{subsection.6.7}} -\newlabel{sec:License-GFDL-7}{{6.7}{25}{Aggregation With Independent Works\relax }{subsection.6.7}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.8}Translation}{25}{subsection.6.8}} -\newlabel{sec:License-GFDL-8}{{6.8}{25}{Translation\relax }{subsection.6.8}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.9}Termination}{26}{subsection.6.9}} -\newlabel{sec:License-GFDL-9}{{6.9}{26}{Termination\relax }{subsection.6.9}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{26}{subsection.6.10}} -\newlabel{sec:License-GFDL-10}{{6.10}{26}{Future Revisions Of This License\relax }{subsection.6.10}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{26}{subsection.6.11}} -\newlabel{sec:License-GFDL-11}{{6.11}{26}{How to use this License for your documents\relax }{subsection.6.11}{}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.log deleted file mode 100644 index 77c0e24..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.log +++ /dev/null @@ -1,380 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 12 MAR 2010 14:17 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size12.clo -File: size12.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/tools/longtable.sty -Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) -\LTleft=\skip43 -\LTright=\skip44 -\LTpre=\skip45 -\LTpost=\skip46 -\LTchunksize=\count87 -\LTcapwidth=\dimen103 -\LT@head=\box26 -\LT@firsthead=\box27 -\LT@foot=\box28 -\LT@lastfoot=\box29 -\LT@cols=\count88 -\LT@rows=\count89 -\c@LT@tables=\count90 -\c@LT@chunks=\count91 -\LT@p@ftn=\toks14 -) -(/usr/share/texmf/tex/latex/graphics/graphicx.sty -Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks15 -) -(/usr/share/texmf/tex/latex/graphics/graphics.sty -Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/trig.sty -Package: trig 1999/03/16 v1.09 sin cos tan (DPC) -) -(/usr/share/texmf/tex/latex/graphics/graphics.cfg -File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive -) -Package graphics Info: Driver file: pdftex.def on input line 80. - -(/usr/share/texmf/tex/latex/graphics/pdftex.def -File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex -\Gread@gobject=\count92 -)) -\Gin@req@height=\dimen104 -\Gin@req@width=\dimen105 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX -\@linkdim=\dimen106 -\Hy@linkcounter=\count93 -\Hy@pagecounter=\count94 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count95 -\Field@Width=\dimen107 -\Fld@charsize=\dimen108 -\Choice@toks=\toks16 -\Field@toks=\toks17 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count96 -\c@Hfootnote=\count97 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count98 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. - -(/usr/share/texmf/tex/context/base/supp-pdf.tex -(/usr/share/texmf/tex/context/base/supp-mis.tex -loading : Context Support Macros / Miscellaneous (2004.10.26) -\protectiondepth=\count99 -\scratchcounter=\count100 -\scratchtoks=\toks18 -\scratchdimen=\dimen109 -\scratchskip=\skip47 -\scratchmuskip=\muskip11 -\scratchbox=\box30 -\scratchread=\read1 -\scratchwrite=\write4 -\zeropoint=\dimen110 -\onepoint=\dimen111 -\onebasepoint=\dimen112 -\minusone=\count101 -\thousandpoint=\dimen113 -\onerealpoint=\dimen114 -\emptytoks=\toks19 -\nextbox=\box31 -\nextdepth=\dimen115 -\everyline=\toks20 -\!!counta=\count102 -\!!countb=\count103 -\recursecounter=\count104 -) -loading : Context Support Macros / PDF (2004.03.26) -\nofMPsegments=\count105 -\nofMParguments=\count106 -\MPscratchCnt=\count107 -\MPscratchDim=\dimen116 -\MPnumerator=\count108 -\everyMPtoPDFconversion=\toks21 -) -Package hyperref Info: Link coloring OFF on input line 17. - (/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count109 -) -LaTeX Info: Redefining \ref on input line 17. -LaTeX Info: Redefining \pageref on input line 17. - (./Manual.out) -(./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <14.4> on input line 20. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 20. - (./Manual.toc -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 3. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 3. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 3. - [1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] [2]) -\tf@toc=\write5 -\openout5 = `Manual.toc'. - - (./sections/introduction.tex) (../../../../../installation.tex -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 25. - -[3] -Overfull \hbox (8.37456pt too wide) in paragraph at lines 53--54 -[][]$\OT1/cmtt/m/n/12 http : / / wiki . centos . org / AdditionalResources / Re -positories$[] - [] - -Missing character: There is no � in font cmr12! -Missing character: There is no � in font cmr12! -[4] -LaTeX Font Info: Try loading font information for OMS+cmr on input line 94. - (/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <12> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 94. - [5]) -(../../../../../configuration.tex [6] -Overfull \hbox (11.3752pt too wide) in paragraph at lines 60--60 -[]\OT1/cmtt/m/n/12 # Squid only knows about standardized HTTP request met -hods.[] - [] - - -Overfull \hbox (11.3752pt too wide) in paragraph at lines 60--60 -[]\OT1/cmtt/m/n/12 # You can add up to 20 additional "extension" methods -here.[] - [] - -[7] -Overfull \hbox (23.88292pt too wide) in paragraph at lines 92--93 -[]\OT1/cmtt/m/n/12 svn co https://projects.centos.org/svn/artwork $\OMS/cmsy/m/ -n/12 ^^X$\OT1/cmtt/m/n/12 /Desktop/ - [] - -[8] -LaTeX Font Info: Font shape `OT1/cmtt/bx/n' in size <12> not available -(Font) Font shape `OT1/cmtt/m/n' tried instead on input line 162. - [9]) (./sections/framework.tex -Underfull \hbox (badness 10000) in paragraph at lines 10--11 - - [] - -[10] -Overfull \hbox (4.34142pt too wide) in paragraph at lines 52--57 -\OT1/cmr/m/n/12 ported as PNG im-age. As con-ven-tion, we use the word `CENTOSA -RTWORK' - [] - - -Overfull \hbox (7.31615pt too wide) in paragraph at lines 70--73 -[]\OT1/cmr/m/n/12 In Ana-conda Header, mark-ers are used only in the file ana-c -onda[]header.svg, - [] - - -Overfull \hbox (0.77798pt too wide) in paragraph at lines 70--73 -\OT1/cmr/m/n/12 specif-i-cally to set the ma-jor re-lease num-ber of CentOS Dis --tri-bu-tion in CentOS - [] - - -Underfull \hbox (badness 10000) in paragraph at lines 98--99 - - [] - -[11] -<../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-0.pdf, id=3 -91, 734.745pt x 233.87375pt> -File: ../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-0.pdf -Graphic file (type pdf) - - -<../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-1.pdf, id=3 -92, 608.2725pt x 123.46124pt> -File: ../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-1.pdf -Graphic file (type pdf) - - -<../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-2.pdf, id=3 -93, 608.2725pt x 123.46124pt> -File: ../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-2.pdf -Graphic file (type pdf) - - -[12 <../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-0.pdf> -<../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-1.pdf> <../ -../../../../../Identity/Models/Distro/Anaconda/Header/img/build-2.pdf>] -Underfull \hbox (badness 10000) in paragraph at lines 157--158 - - [] - -[13] -Underfull \hbox (badness 10000) in paragraph at lines 222--223 - - [] - -[14] -<../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf, id=438, 5 -29.98pt x 589.20125pt> -File: ../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf Graph -ic file (type pdf) - - -Underfull \hbox (badness 10000) in paragraph at lines 250--251 - - [] - -) (./sections/rebranding.tex [15] [16 <../../../../../../Identity/Models/Script -s/Rendering/img/build-0.pdf>] -Overfull \hbox (2.56557pt too wide) in paragraph at lines 12--15 -[]\OT1/cmr/m/n/12 CentOS Brands and art-works are or-ga-nized in-side CentOS Ar -t-work Repos- - [] - -) (../../../../../Licenses/GFDL.tex -Underfull \hbox (badness 10000) in paragraph at lines 5--14 - - [] - -[17] [18] [19] [20] [21] [22] [23] [24] [25] -Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 document under the terms of the GNU Free Documentation Li -cense,[] - [] - - -Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 Version 1.2 or any later version published by the Free So -ftware[] - [] - - -Overfull \hbox (5.2002pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 Foundation; with no Invariant Sections, no Front-Cover Te -xts,[] - [] - - -Overfull \hbox (11.3752pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 and no Back-Cover Texts. A copy of the license is includ -ed in[] - [] - - -Overfull \hbox (5.2002pt too wide) in paragraph at lines 425--425 -[] \OT1/cmtt/m/n/12 with the Invariant Sections being LIST THEIR TITLES, with - the[] - [] - -[26]) [27] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 2901 strings out of 94500 - 40239 string characters out of 1176766 - 91168 words of memory out of 1000000 - 5944 multiletter control sequences out of 10000+50000 - 10751 words of font info for 38 fonts, out of 500000 for 2000 - 582 hyphenation exceptions out of 1000 - 27i,8n,36p,222b,267s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 513 PDF objects out of 300000 - 98 named destinations out of 131072 - 493 words of extra memory for PDF output out of 65536 - - -Output written on Manual.pdf (27 pages, 296612 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.out deleted file mode 100644 index 9b9b706..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.out +++ /dev/null @@ -1,57 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Introduction}{} -\BOOKMARK [1][-]{section.2}{Installation}{} -\BOOKMARK [2][-]{subsection.2.1}{Subversion}{section.2} -\BOOKMARK [2][-]{subsection.2.2}{Inkscape}{section.2} -\BOOKMARK [2][-]{subsection.2.3}{ImageMagick}{section.2} -\BOOKMARK [2][-]{subsection.2.4}{Netpbm}{section.2} -\BOOKMARK [2][-]{subsection.2.5}{Syslinux}{section.2} -\BOOKMARK [2][-]{subsection.2.6}{GNU Image Manipulation Program}{section.2} -\BOOKMARK [2][-]{subsection.2.7}{GNU Core Utilities}{section.2} -\BOOKMARK [2][-]{subsection.2.8}{LaTeX}{section.2} -\BOOKMARK [1][-]{section.3}{Configuration}{} -\BOOKMARK [2][-]{subsection.3.1}{Firewall}{section.3} -\BOOKMARK [2][-]{subsection.3.2}{Subversion Behind Squid}{section.3} -\BOOKMARK [3][-]{subsubsection.3.2.1}{Subversion Client Configuration}{subsection.3.2} -\BOOKMARK [3][-]{subsubsection.3.2.2}{Squid Server Configuration}{subsection.3.2} -\BOOKMARK [2][-]{subsection.3.3}{Working Copy}{section.3} -\BOOKMARK [2][-]{subsection.3.4}{User Identification}{section.3} -\BOOKMARK [3][-]{subsubsection.3.4.1}{Account Registration}{subsection.3.4} -\BOOKMARK [3][-]{subsubsection.3.4.2}{Account Privileges}{subsection.3.4} -\BOOKMARK [2][-]{subsection.3.5}{Shell Environment}{section.3} -\BOOKMARK [3][-]{subsubsection.3.5.1}{Relative Paths}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.2}{Absolute Paths}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.3}{Environment Variable Definition}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.4}{Environment Variable Initialization}{subsection.3.5} -\BOOKMARK [1][-]{section.4}{Framework}{} -\BOOKMARK [2][-]{subsection.4.1}{Identity}{section.4} -\BOOKMARK [3][-]{subsubsection.4.1.1}{Designs}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.2}{Export Id}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.3}{Markers}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.4}{Images}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.5}{Models}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.6}{Rendering}{subsection.4.1} -\BOOKMARK [2][-]{subsection.4.2}{Translations}{section.4} -\BOOKMARK [3][-]{subsubsection.4.2.1}{Common Translations}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.2}{Specific Translations}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.3}{Translation Path}{subsection.4.2} -\BOOKMARK [2][-]{subsection.4.3}{Manuals}{section.4} -\BOOKMARK [2][-]{subsection.4.4}{Scripts}{section.4} -\BOOKMARK [3][-]{subsubsection.4.4.1}{Rendering}{subsection.4.4} -\BOOKMARK [3][-]{subsubsection.4.4.2}{Pre-rendering}{subsection.4.4} -\BOOKMARK [3][-]{subsubsection.4.4.3}{Post-rendering}{subsection.4.4} -\BOOKMARK [1][-]{section.5}{Rebranding}{} -\BOOKMARK [2][-]{subsection.5.1}{Images}{section.5} -\BOOKMARK [3][-]{subsubsection.5.1.1}{redhat-logos}{subsection.5.1} -\BOOKMARK [2][-]{subsection.5.2}{Messages Locale}{section.5} -\BOOKMARK [1][-]{section.6}{GNU Free Documentation License}{} -\BOOKMARK [2][-]{subsection.6.1}{Applicability And Definitions}{section.6} -\BOOKMARK [2][-]{subsection.6.2}{Verbatim Copying}{section.6} -\BOOKMARK [2][-]{subsection.6.3}{Copying In Quantity}{section.6} -\BOOKMARK [2][-]{subsection.6.4}{Modifications}{section.6} -\BOOKMARK [2][-]{subsection.6.5}{Combining Documents}{section.6} -\BOOKMARK [2][-]{subsection.6.6}{Collections Of Documents}{section.6} -\BOOKMARK [2][-]{subsection.6.7}{Aggregation With Independent Works}{section.6} -\BOOKMARK [2][-]{subsection.6.8}{Translation}{section.6} -\BOOKMARK [2][-]{subsection.6.9}{Termination}{section.6} -\BOOKMARK [2][-]{subsection.6.10}{Future Revisions Of This License}{section.6} -\BOOKMARK [2][-]{subsection.6.11}{How to use this License for your documents}{section.6} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.pdf deleted file mode 100644 index 04868a4..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.toc deleted file mode 100644 index 548e728..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.toc +++ /dev/null @@ -1,57 +0,0 @@ -\contentsline {section}{\numberline {1}Introduction}{3}{section.1} -\contentsline {section}{\numberline {2}Installation}{3}{section.2} -\contentsline {subsection}{\numberline {2.1}Subversion}{3}{subsection.2.1} -\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2} -\contentsline {subsection}{\numberline {2.3}ImageMagick}{4}{subsection.2.3} -\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4} -\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5} -\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{5}{subsection.2.6} -\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{5}{subsection.2.7} -\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8} -\contentsline {section}{\numberline {3}Configuration}{6}{section.3} -\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1} -\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{6}{subsection.3.2} -\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{6}{subsubsection.3.2.1} -\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2} -\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3} -\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4} -\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{8}{subsubsection.3.4.1} -\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{8}{subsubsection.3.4.2} -\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5} -\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1} -\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2} -\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3} -\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{9}{subsubsection.3.5.4} -\contentsline {section}{\numberline {4}Framework}{10}{section.4} -\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1} -\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1} -\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2} -\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3} -\contentsline {subsubsection}{\numberline {4.1.4}Images}{11}{subsubsection.4.1.4} -\contentsline {subsubsection}{\numberline {4.1.5}Models}{12}{subsubsection.4.1.5} -\contentsline {subsubsection}{\numberline {4.1.6}Rendering}{13}{subsubsection.4.1.6} -\contentsline {subsection}{\numberline {4.2}Translations}{13}{subsection.4.2} -\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{13}{subsubsection.4.2.1} -\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{13}{subsubsection.4.2.2} -\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{14}{subsubsection.4.2.3} -\contentsline {subsection}{\numberline {4.3}Manuals}{14}{subsection.4.3} -\contentsline {subsection}{\numberline {4.4}Scripts}{15}{subsection.4.4} -\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{15}{subsubsection.4.4.1} -\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{15}{subsubsection.4.4.2} -\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{15}{subsubsection.4.4.3} -\contentsline {section}{\numberline {5}Rebranding}{17}{section.5} -\contentsline {subsection}{\numberline {5.1}Images}{17}{subsection.5.1} -\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{17}{subsubsection.5.1.1} -\contentsline {subsection}{\numberline {5.2}Messages Locale}{17}{subsection.5.2} -\contentsline {section}{\numberline {6}GNU Free Documentation License}{18}{section.6} -\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{18}{subsection.6.1} -\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{20}{subsection.6.2} -\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{21}{subsection.6.3} -\contentsline {subsection}{\numberline {6.4}Modifications}{21}{subsection.6.4} -\contentsline {subsection}{\numberline {6.5}Combining Documents}{24}{subsection.6.5} -\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{24}{subsection.6.6} -\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{25}{subsection.6.7} -\contentsline {subsection}{\numberline {6.8}Translation}{25}{subsection.6.8} -\contentsline {subsection}{\numberline {6.9}Termination}{26}{subsection.6.9} -\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{26}{subsection.6.10} -\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{26}{subsection.6.11} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/manual.tex deleted file mode 100644 index 9e18572..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/manual.tex +++ /dev/null @@ -1,49 +0,0 @@ -\documentclass[12pt]{article} -\usepackage{longtable} -\usepackage[pdftex]{graphicx} -\usepackage{hyperref} -\hypersetup{pdfauthor={Alain Reguera Delgado},% - pdftitle={Anaconda Header Visual Style},% - pdfsubject={CentOS Corporate Visual Identity}% - } - -% Tell LaTeX how to hyphenate a word. Don't hyphenate the following -% words: -\hyphenation{CentOS CENTOSARTWORK} - -\title{Anaconda Header Visual Style} -\author{Alain Reguera Delgado} - -\begin{document} - -\maketitle - -\begin{abstract} - -This article describes the visual style of Anaconda Header. Anaconda -is the name of the install program used by CentOS. It is python-based -with some custom modules written in C. The anaconda installer works on -a wide variety of Linux-based computing architectures (ia32, Itanium, -Alpha, S/390, PowerPC), and is designed to make it easy to add -platforms. - -Copyright (C) 2010 The CentOS Project. Permission is granted to copy, -distribute and/or modify this document under the terms of the GNU Free -Documentation License, Version 1.2 or any later version published by -the Free Software Foundation; with no Invariant Sections, no -Front-Cover Texts, and no Back-Cover Texts. A copy of the license is -included in the section entitled ``GNU Free Documentation License''. - -\end{abstract} - -\tableofcontents - -\input{sections/introduction.tex} -\input{../../../../../installation.tex} -\input{../../../../../configuration.tex} -\input{sections/framework.tex} -\input{sections/rebranding.tex} - -\input{../../../../../Licenses/GFDL.tex} - -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.aux deleted file mode 100644 index bb0cdd1..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.aux +++ /dev/null @@ -1,130 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{3}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Installation}{4}{section.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Subversion}{4}{subsection.2.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}ImageMagick}{5}{subsection.2.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{6}{subsection.2.6}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Configuration}{7}{section.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}Firewall}{7}{subsection.3.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Working Copy}{8}{subsection.3.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.4}User Identification}{9}{subsection.3.4}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{9}{subsubsection.3.4.1}} -\newlabel{sec:Configuration:Account}{{3.4.1}{9}{Account Registration\relax }{subsubsection.3.4.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2}} -\newlabel{sec:Configuration:User:Privileges}{{3.4.2}{9}{Account Privileges\relax }{subsubsection.3.4.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5}} -\newlabel{sec:Configuration:Environment}{{3.5}{9}{Shell Environment\relax }{subsection.3.5}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{10}{subsubsection.3.5.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{10}{subsubsection.3.5.3}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Framework}{10}{section.4}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Identity}{11}{subsection.4.1}} -\newlabel{sec:Framework:Identity}{{4.1}{11}{Identity\relax }{subsection.4.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.1}Design Templates}{11}{subsubsection.4.1.1}} -\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Anaconda Progress identity framework.}}{12}{figure.1}} -\newlabel{fig:Framework:Identity}{{1}{12}{Identity\relax }{figure.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.2}Design Templates Export Id}{13}{subsubsection.4.1.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.3}Design Models}{13}{subsubsection.4.1.3}} -\newlabel{sec:Framework:Identity:Models}{{4.1.3}{13}{Design Models\relax }{subsubsection.4.1.3}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.4}Image Files}{13}{subsubsection.4.1.4}} -\newlabel{sec:Framework:Identity:Images}{{4.1.4}{13}{Image Files\relax }{subsubsection.4.1.4}{}} -\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces Anaconda Progress design models framework.}}{14}{figure.2}} -\newlabel{fig:Framework:Identity:Models}{{2}{14}{Design Models\relax }{figure.2}{}} -\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Anaconda Progress slide images. A = ``Header'', B = ``Slide\ rotation'', C = ``Action/Navigation''.}}{14}{figure.3}} -\newlabel{fig:Identity:Models:Progress:Slides}{{3}{14}{Design Models\relax }{figure.3}{}} -\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces Anaconda Progress release notes. A = ``Release\ notes'', B =\ ``Action/Navigation''.}}{15}{figure.4}} -\newlabel{fig:Identity:Models:Progress:Release}{{4}{15}{Design Models\relax }{figure.4}{}} -\@writefile{lof}{\contentsline {figure}{\numberline {5}{\ignorespaces Anaconda Progress first slide template. A = ``The CentOS\ Symbol'', B = ``The CentOS Default Artistic Motif'', C = ``The CentOS\ Release Brand'', D = ``The CentOS Copyright''.}}{16}{figure.5}} -\newlabel{fig:Identity:Models:First}{{5}{16}{Design Models\relax }{figure.5}{}} -\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces Anaconda Progress list template.}}{17}{figure.6}} -\newlabel{fig:Identity:Models:Paragraph}{{6}{17}{Design Models\relax }{figure.6}{}} -\@writefile{lof}{\contentsline {figure}{\numberline {7}{\ignorespaces Anaconda Progress paragraph template.}}{17}{figure.7}} -\newlabel{fig:Identity:Models:List}{{7}{17}{Design Models\relax }{figure.7}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.5}Image Files Rendering}{18}{subsubsection.4.1.5}} -\newlabel{sec:Framework:Identity:Rendering}{{4.1.5}{18}{Image Files Rendering\relax }{subsubsection.4.1.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.2}Translations}{18}{subsection.4.2}} -\newlabel{sec:Framework:Translations}{{4.2}{18}{Translations\relax }{subsection.4.2}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{18}{subsubsection.4.2.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{18}{subsubsection.4.2.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{19}{subsubsection.4.2.3}} -\@writefile{lof}{\contentsline {figure}{\numberline {8}{\ignorespaces Anaconda Progress translation framework.}}{20}{figure.8}} -\newlabel{fig:Framework:Translation}{{8}{20}{Translation Path\relax }{figure.8}{}} -\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Anaconda Progress translation markers.}}{21}{table.1}} -\newlabel{tab:Framework:Identity:Markers}{{1}{21}{Translation Markers\relax }{table.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.4}Translation Markers}{21}{subsubsection.4.2.4}} -\newlabel{sec:Framework:Translations:Markers}{{4.2.4}{21}{Translation Markers\relax }{subsubsection.4.2.4}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.5}Translation Rendering}{21}{subsubsection.4.2.5}} -\@writefile{lof}{\contentsline {figure}{\numberline {9}{\ignorespaces English translation file for CentOS 5 Anaconda Progress\ `welcome' slide. Files like this are used by \texttt {render.sh} identity\ script to produce translated images.}}{22}{figure.9}} -\newlabel{fig:Framework:Translations:Markers}{{9}{22}{Translation Markers\relax }{figure.9}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.6}Translation Rendering Script}{23}{subsubsection.4.2.6}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.7}Translation Template Directory}{24}{subsubsection.4.2.7}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}Manuals}{24}{subsection.4.3}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.3.1}Writing Style}{24}{subsubsection.4.3.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.3.2}File Structure}{24}{subsubsection.4.3.2}} -\@writefile{lof}{\contentsline {figure}{\numberline {10}{\ignorespaces Specific documentation files. These files are specific to Anaconda Progress Visual Style manual only.}}{25}{figure.10}} -\newlabel{fig:Framework:Manuals:Structure:Specific}{{10}{25}{File Structure\relax }{figure.10}{}} -\@writefile{lof}{\contentsline {figure}{\numberline {11}{\ignorespaces Common documentation files. These files are reused by all\ manuals.}}{25}{figure.11}} -\newlabel{fig:Framework:Manuals:Structure:Common}{{11}{25}{File Structure\relax }{figure.11}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.3.3}Exporting To PDF}{26}{subsubsection.4.3.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Scripts}{26}{subsection.4.4}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.1}Invocation Scripts}{27}{subsubsection.4.4.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.2}Configuration Scripts}{27}{subsubsection.4.4.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.3}Function Scripts}{27}{subsubsection.4.4.3}} -\@writefile{lof}{\contentsline {figure}{\numberline {12}{\ignorespaces Anaconda Progress configuration layout.}}{28}{figure.12}} -\newlabel{fig:Framework:Scripts:Config}{{12}{28}{Configuration Scripts\relax }{figure.12}{}} -\@writefile{toc}{\contentsline {section}{\numberline {5}Rebranding}{29}{section.5}} -\newlabel{sec:Rebranding}{{5}{29}{Rebranding\relax }{section.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}Images}{29}{subsection.5.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{29}{subsubsection.5.1.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Messages Locale}{29}{subsection.5.2}} -\@writefile{lof}{\contentsline {figure}{\numberline {13}{\ignorespaces Anaconda Progress slide images.}}{30}{figure.13}} -\newlabel{fig:Rebranding:Images}{{13}{30}{redhat-logos\relax }{figure.13}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {5.3}Release Notes}{31}{subsection.5.3}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.3.1}centos-release-notes}{31}{subsubsection.5.3.1}} -\@writefile{lof}{\contentsline {figure}{\numberline {14}{\ignorespaces Anaconda Progress release notes files.}}{31}{figure.14}} -\newlabel{fig:Rebranding:ReleaseNotes:Files}{{14}{31}{centos-release-notes\relax }{figure.14}{}} -\@writefile{toc}{\contentsline {section}{\numberline {6}GNU Free Documentation License}{32}{section.6}} -\newlabel{sec:License-GFDL-0}{{6}{32}{Preamble\relax }{section*.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{32}{subsection.6.1}} -\newlabel{sec:License-GFDL-1}{{6.1}{32}{Applicability And Definitions\relax }{subsection.6.1}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{34}{subsection.6.2}} -\newlabel{sec:License-GFDL-2}{{6.2}{34}{Verbatim Copying\relax }{subsection.6.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{35}{subsection.6.3}} -\newlabel{sec:License-GFDL-3}{{6.3}{35}{Copying In Quantity\relax }{subsection.6.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.4}Modifications}{35}{subsection.6.4}} -\newlabel{sec:License-GFDL-4}{{6.4}{35}{Modifications\relax }{subsection.6.4}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.5}Combining Documents}{38}{subsection.6.5}} -\newlabel{sec:License-GFDL-5}{{6.5}{38}{Combining Documents\relax }{subsection.6.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{38}{subsection.6.6}} -\newlabel{sec:License-GFDL-6}{{6.6}{38}{Collections Of Documents\relax }{subsection.6.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{39}{subsection.6.7}} -\newlabel{sec:License-GFDL-7}{{6.7}{39}{Aggregation With Independent Works\relax }{subsection.6.7}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.8}Translation}{39}{subsection.6.8}} -\newlabel{sec:License-GFDL-8}{{6.8}{39}{Translation\relax }{subsection.6.8}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.9}Termination}{40}{subsection.6.9}} -\newlabel{sec:License-GFDL-9}{{6.9}{40}{Termination\relax }{subsection.6.9}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{40}{subsection.6.10}} -\newlabel{sec:License-GFDL-10}{{6.10}{40}{Future Revisions Of This License\relax }{subsection.6.10}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{40}{subsection.6.11}} -\newlabel{sec:License-GFDL-11}{{6.11}{40}{How to use this License for your documents\relax }{subsection.6.11}{}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.log deleted file mode 100644 index ed6ad65..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.log +++ /dev/null @@ -1,431 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 30 MAR 2010 23:16 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size12.clo -File: size12.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/graphics/graphicx.sty -Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks14 -) -(/usr/share/texmf/tex/latex/graphics/graphics.sty -Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/trig.sty -Package: trig 1999/03/16 v1.09 sin cos tan (DPC) -) -(/usr/share/texmf/tex/latex/graphics/graphics.cfg -File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive -) -Package graphics Info: Driver file: pdftex.def on input line 80. - -(/usr/share/texmf/tex/latex/graphics/pdftex.def -File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex -\Gread@gobject=\count87 -)) -\Gin@req@height=\dimen103 -\Gin@req@width=\dimen104 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX -\@linkdim=\dimen105 -\Hy@linkcounter=\count88 -\Hy@pagecounter=\count89 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count90 -\Field@Width=\dimen106 -\Fld@charsize=\dimen107 -\Choice@toks=\toks15 -\Field@toks=\toks16 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count91 -\c@Hfootnote=\count92 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count93 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 16. -LaTeX Font Info: ... okay on input line 16. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 16. -LaTeX Font Info: ... okay on input line 16. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 16. -LaTeX Font Info: ... okay on input line 16. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 16. -LaTeX Font Info: ... okay on input line 16. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 16. -LaTeX Font Info: ... okay on input line 16. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 16. -LaTeX Font Info: ... okay on input line 16. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 16. -LaTeX Font Info: ... okay on input line 16. - -(/usr/share/texmf/tex/context/base/supp-pdf.tex -(/usr/share/texmf/tex/context/base/supp-mis.tex -loading : Context Support Macros / Miscellaneous (2004.10.26) -\protectiondepth=\count94 -\scratchcounter=\count95 -\scratchtoks=\toks17 -\scratchdimen=\dimen108 -\scratchskip=\skip43 -\scratchmuskip=\muskip11 -\scratchbox=\box26 -\scratchread=\read1 -\scratchwrite=\write4 -\zeropoint=\dimen109 -\onepoint=\dimen110 -\onebasepoint=\dimen111 -\minusone=\count96 -\thousandpoint=\dimen112 -\onerealpoint=\dimen113 -\emptytoks=\toks18 -\nextbox=\box27 -\nextdepth=\dimen114 -\everyline=\toks19 -\!!counta=\count97 -\!!countb=\count98 -\recursecounter=\count99 -) -loading : Context Support Macros / PDF (2004.03.26) -\nofMPsegments=\count100 -\nofMParguments=\count101 -\MPscratchCnt=\count102 -\MPscratchDim=\dimen115 -\MPnumerator=\count103 -\everyMPtoPDFconversion=\toks20 -) -Package hyperref Info: Link coloring OFF on input line 16. - (/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count104 -) -LaTeX Info: Redefining \ref on input line 16. -LaTeX Info: Redefining \pageref on input line 16. - (./Manual.out) -(./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <14.4> on input line 19. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 19. -LaTeX Font Info: Try loading font information for OMS+cmr on input line 36. - (/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10.95> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 36. - (./Manual.toc -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 3. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 3. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 3. - -[1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] [2]) -\tf@toc=\write5 -\openout5 = `Manual.toc'. - - -(./sections/introduction.tex) (../../../../../installation.tex [3] -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 25. - -Overfull \hbox (8.37456pt too wide) in paragraph at lines 53--54 -[][]$\OT1/cmtt/m/n/12 http : / / wiki . centos . org / AdditionalResources / Re -positories$[] - [] - -[4] -Missing character: There is no � in font cmr12! -Missing character: There is no � in font cmr12! -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <12> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 94. - [5]) (../../../../../configuration.tex [6] -Overfull \hbox (11.3752pt too wide) in paragraph at lines 64--64 -[]\OT1/cmtt/m/n/12 # Squid only knows about standardized HTTP request met -hods.[] - [] - -[7] -Overfull \hbox (11.3752pt too wide) in paragraph at lines 64--64 -[]\OT1/cmtt/m/n/12 # You can add up to 20 additional "extension" methods -here.[] - [] - - -Overfull \hbox (23.88292pt too wide) in paragraph at lines 96--97 -[]\OT1/cmtt/m/n/12 svn co https://projects.centos.org/svn/artwork $\OMS/cmsy/m/ -n/12 ^^X$\OT1/cmtt/m/n/12 /Desktop/ - [] - -[8] [9] -Overfull \hbox (32.24086pt too wide) in paragraph at lines 161--168 -\OT1/cmr/m/n/12 CentOS Art-work Repos-i-tory, we de-cided to de-fine the \OT1/c -mr/bx/n/12 CentOS[]ARTWORK[]WC - [] - -) (./sections/framework.tex -Underfull \hbox (badness 10000) in paragraph at lines 9--10 - - [] - -[10] -Underfull \hbox (badness 10000) in paragraph at lines 57--58 - - [] - -[11] [12] -Underfull \hbox (badness 10000) in paragraph at lines 122--123 - - [] - - -<../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-3.pdf, id -=436, 691.58376pt x 481.8pt> -File: ../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-3.pd -f Graphic file (type pdf) - - -<../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-4.pdf, id -=437, 691.58376pt x 481.8pt> -File: ../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-4.pd -f Graphic file (type pdf) - - -<../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-0.pdf, id -=438, 393.47pt x 332.24126pt> -File: ../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-0.pd -f Graphic file (type pdf) - - -<../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-1.pdf, id -=439, 393.47pt x 232.87pt> -File: ../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-1.pd -f Graphic file (type pdf) - - -<../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-2.pdf, id -=440, 393.47pt x 232.87pt> -File: ../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-2.pd -f Graphic file (type pdf) - - -Underfull \hbox (badness 10000) in paragraph at lines 214--215 - - [] - -[13] [14 <../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build- -3.pdf>] [15 <../../../../../../Identity/Models/Distro/Anaconda/Progress/img/bui -ld-4.pdf>] [16 <../../../../../../Identity/Models/Distro/Anaconda/Progress/img/ -build-0.pdf>] [17 <../../../../../../Identity/Models/Distro/Anaconda/Progress/i -mg/build-1.pdf> <../../../../../../Identity/Models/Distro/Anaconda/Progress/img -/build-2.pdf>] -Underfull \hbox (badness 10000) in paragraph at lines 247--248 - - [] - -[18] [19] [20] -Overfull \hbox (11.3752pt too wide) in paragraph at lines 423--423 -[]\OT1/cmtt/m/n/12 # Warning: Do not modify this file directly. This file is cr -eated[] - [] - - -Overfull \hbox (17.5502pt too wide) in paragraph at lines 423--423 -[]\OT1/cmtt/m/n/12 # automatically using render.sh translation script. Any chan -ge you[] - [] - - -Overfull \hbox (5.2002pt too wide) in paragraph at lines 423--423 -[]\OT1/cmtt/m/n/12 # translation script. If you want to improve the content of -this[] - [] - - -Overfull \hbox (11.3752pt too wide) in paragraph at lines 423--423 -[]\OT1/cmtt/m/n/12 # translation file, improve its template file instead and ru -n the[] - [] - - -Overfull \hbox (23.7252pt too wide) in paragraph at lines 423--423 -[]\OT1/cmtt/m/n/12 s/=TEXT2=/CentOS is an enterprise-class Linux Distribution d -erived\[] - [] - - -Overfull \hbox (5.2002pt too wide) in paragraph at lines 423--423 -[]\OT1/cmtt/m/n/12 from sources freely provided to the public by a prominent No -rth\[] - [] - - -Overfull \hbox (29.9002pt too wide) in paragraph at lines 423--423 -[]\OT1/cmtt/m/n/12 redistribution policy and aims to be 100% binary compatible. - CentOS\[] - [] - -[21] [22] [23] -Underfull \hbox (badness 10000) in paragraph at lines 512--513 - - [] - -[24] [25] -Overfull \hbox (18.05084pt too wide) in paragraph at lines 608--613 -[]\OT1/cmr/m/n/12 provides in-for-ma-tion about how to re-brand Ana-conda Progr -ess - [] - - -Overfull \hbox (15.44675pt too wide) in paragraph at lines 608--613 -\OT1/cmr/m/n/12 Progress Vi-sual Style \OT1/cmtt/m/n/12 rebranding.tex \OT1/cmr -/m/n/12 file is spe-cific to Ana-conda Progress - [] - -[26] -Underfull \hbox (badness 10000) in paragraph at lines 647--648 - - [] - - -Overfull \hbox (42.25021pt too wide) in paragraph at lines 695--695 -[]\OT1/cmtt/m/n/12 # Template and Translation matching list. Define which desig -n template[] - [] - -) (./sections/rebranding.tex [27] [28] -Overfull \hbox (2.56557pt too wide) in paragraph at lines 13--16 -[]\OT1/cmr/m/n/12 CentOS Brands and art-works are or-ga-nized in-side CentOS Ar -t-work Repos- - [] - -[29] [30]) (../../../../../Licenses/GFDL.tex -Underfull \hbox (badness 10000) in paragraph at lines 5--14 - - [] - -[31] [32] [33] [34] [35] [36] [37] [38] [39] -Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 document under the terms of the GNU Free Documentation Li -cense,[] - [] - - -Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 Version 1.2 or any later version published by the Free So -ftware[] - [] - - -Overfull \hbox (5.2002pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 Foundation; with no Invariant Sections, no Front-Cover Te -xts,[] - [] - - -Overfull \hbox (11.3752pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 and no Back-Cover Texts. A copy of the license is includ -ed in[] - [] - - -Overfull \hbox (5.2002pt too wide) in paragraph at lines 425--425 -[] \OT1/cmtt/m/n/12 with the Invariant Sections being LIST THEIR TITLES, with - the[] - [] - -[40]) [41] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 2872 strings out of 94500 - 40567 string characters out of 1176766 - 90951 words of memory out of 1000000 - 5890 multiletter control sequences out of 10000+50000 - 11008 words of font info for 39 fonts, out of 500000 for 2000 - 582 hyphenation exceptions out of 1000 - 27i,8n,36p,297b,267s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 650 PDF objects out of 300000 - 126 named destinations out of 131072 - 562 words of extra memory for PDF output out of 65536 - - -Output written on Manual.pdf (41 pages, 342886 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.lot b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.lot deleted file mode 100644 index aff46bf..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.lot +++ /dev/null @@ -1,24 +0,0 @@ -\contentsline {table}{\numberline {1}{Files related to the First Slide of Anaconda Progress.}}{2}{table.1} -\contentsline {table}{\numberline {1}{Files related to the First Slide of Anaconda Progress. (continued)}}{3}{table.1} -\contentsline {table}{\numberline {2}{Files related to English Slides of Anaconda Progress.}}{3}{table.2} -\contentsline {table}{\numberline {2}{Files related to English Slides of Anaconda Progress. (continued)}}{4}{table.2} -\contentsline {table}{\numberline {3}{Files related to Czech Slides of Anaconda Progress.}}{4}{table.3} -\contentsline {table}{\numberline {3}{Files related to Czech Slides of Anaconda Progress. (continued)}}{5}{table.3} -\contentsline {table}{\numberline {4}{Files related to German Slides of Anaconda Progress.}}{5}{table.4} -\contentsline {table}{\numberline {4}{Files related to German Slides of Anaconda Progress. (continued)}}{6}{table.4} -\contentsline {table}{\numberline {5}{Files related to Spanish Slides of Anaconda Progress.}}{6}{table.5} -\contentsline {table}{\numberline {5}{Files related to Spanish Slides of Anaconda Progress. (continued)}}{7}{table.5} -\contentsline {table}{\numberline {6}{Files related to French Slides of Anaconda Progress.}}{7}{table.6} -\contentsline {table}{\numberline {7}{Files related to Italian Slides of Anaconda Progress.}}{8}{table.7} -\contentsline {table}{\numberline {8}{Files related to Japanese Slides of Anaconda Progress.}}{8}{table.8} -\contentsline {table}{\numberline {8}{Files related to Japanese Slides of Anaconda Progress. (continued)}}{9}{table.8} -\contentsline {table}{\numberline {9}{Files related to Dutch Slides of Anaconda Progress.}}{9}{table.9} -\contentsline {table}{\numberline {9}{Files related to Dutch Slides of Anaconda Progress. (continued)}}{10}{table.9} -\contentsline {table}{\numberline {10}{Files related to Portuguese Slides of Anaconda Progress.}}{10}{table.10} -\contentsline {table}{\numberline {10}{Files related to Portuguese Slides of Anaconda Progress. (continued)}}{11}{table.10} -\contentsline {table}{\numberline {11}{Files related to Romanian Slides of Anaconda Progress.}}{11}{table.11} -\contentsline {table}{\numberline {11}{Files related to Romanian Slides of Anaconda Progress. (continued)}}{12}{table.11} -\contentsline {table}{\numberline {12}{Files related to Russian Slides of Anaconda Progress.}}{12}{table.12} -\contentsline {table}{\numberline {12}{Files related to Russian Slides of Anaconda Progress. (continued)}}{13}{table.12} -\contentsline {table}{\numberline {13}{Files related to Portuguese du Brasil Slides of Anaconda Progress.}}{13}{table.13} -\contentsline {table}{\numberline {13}{Files related to Portuguese du Brasil Slides of Anaconda Progress. (continued)}}{14}{table.13} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.out deleted file mode 100644 index 34e2b08..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.out +++ /dev/null @@ -1,65 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Introduction}{} -\BOOKMARK [1][-]{section.2}{Installation}{} -\BOOKMARK [2][-]{subsection.2.1}{Subversion}{section.2} -\BOOKMARK [2][-]{subsection.2.2}{Inkscape}{section.2} -\BOOKMARK [2][-]{subsection.2.3}{ImageMagick}{section.2} -\BOOKMARK [2][-]{subsection.2.4}{Netpbm}{section.2} -\BOOKMARK [2][-]{subsection.2.5}{Syslinux}{section.2} -\BOOKMARK [2][-]{subsection.2.6}{GNU Image Manipulation Program}{section.2} -\BOOKMARK [2][-]{subsection.2.7}{GNU Core Utilities}{section.2} -\BOOKMARK [2][-]{subsection.2.8}{LaTeX}{section.2} -\BOOKMARK [1][-]{section.3}{Configuration}{} -\BOOKMARK [2][-]{subsection.3.1}{Firewall}{section.3} -\BOOKMARK [2][-]{subsection.3.2}{Subversion Behind Squid}{section.3} -\BOOKMARK [3][-]{subsubsection.3.2.1}{Subversion Client Configuration}{subsection.3.2} -\BOOKMARK [3][-]{subsubsection.3.2.2}{Squid Server Configuration}{subsection.3.2} -\BOOKMARK [2][-]{subsection.3.3}{Working Copy}{section.3} -\BOOKMARK [2][-]{subsection.3.4}{User Identification}{section.3} -\BOOKMARK [3][-]{subsubsection.3.4.1}{Account Registration}{subsection.3.4} -\BOOKMARK [3][-]{subsubsection.3.4.2}{Account Privileges}{subsection.3.4} -\BOOKMARK [2][-]{subsection.3.5}{Shell Environment}{section.3} -\BOOKMARK [3][-]{subsubsection.3.5.1}{Relative Paths}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.2}{Absolute Paths}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.3}{Environment Variable Definition}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.4}{Environment Variable Initialization}{subsection.3.5} -\BOOKMARK [1][-]{section.4}{Framework}{} -\BOOKMARK [2][-]{subsection.4.1}{Identity}{section.4} -\BOOKMARK [3][-]{subsubsection.4.1.1}{Design Templates}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.2}{Design Templates Export Id}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.3}{Design Models}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.4}{Image Files}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.5}{Image Files Rendering}{subsection.4.1} -\BOOKMARK [2][-]{subsection.4.2}{Translations}{section.4} -\BOOKMARK [3][-]{subsubsection.4.2.1}{Common Translations}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.2}{Specific Translations}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.3}{Translation Path}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.4}{Translation Markers}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.5}{Translation Rendering}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.6}{Translation Rendering Script}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.7}{Translation Template Directory}{subsection.4.2} -\BOOKMARK [2][-]{subsection.4.3}{Manuals}{section.4} -\BOOKMARK [3][-]{subsubsection.4.3.1}{Writing Style}{subsection.4.3} -\BOOKMARK [3][-]{subsubsection.4.3.2}{File Structure}{subsection.4.3} -\BOOKMARK [3][-]{subsubsection.4.3.3}{Exporting To PDF}{subsection.4.3} -\BOOKMARK [2][-]{subsection.4.4}{Scripts}{section.4} -\BOOKMARK [3][-]{subsubsection.4.4.1}{Invocation Scripts}{subsection.4.4} -\BOOKMARK [3][-]{subsubsection.4.4.2}{Configuration Scripts}{subsection.4.4} -\BOOKMARK [3][-]{subsubsection.4.4.3}{Function Scripts}{subsection.4.4} -\BOOKMARK [1][-]{section.5}{Rebranding}{} -\BOOKMARK [2][-]{subsection.5.1}{Images}{section.5} -\BOOKMARK [3][-]{subsubsection.5.1.1}{redhat-logos}{subsection.5.1} -\BOOKMARK [2][-]{subsection.5.2}{Messages Locale}{section.5} -\BOOKMARK [2][-]{subsection.5.3}{Release Notes}{section.5} -\BOOKMARK [3][-]{subsubsection.5.3.1}{centos-release-notes}{subsection.5.3} -\BOOKMARK [1][-]{section.6}{GNU Free Documentation License}{} -\BOOKMARK [2][-]{subsection.6.1}{Applicability And Definitions}{section.6} -\BOOKMARK [2][-]{subsection.6.2}{Verbatim Copying}{section.6} -\BOOKMARK [2][-]{subsection.6.3}{Copying In Quantity}{section.6} -\BOOKMARK [2][-]{subsection.6.4}{Modifications}{section.6} -\BOOKMARK [2][-]{subsection.6.5}{Combining Documents}{section.6} -\BOOKMARK [2][-]{subsection.6.6}{Collections Of Documents}{section.6} -\BOOKMARK [2][-]{subsection.6.7}{Aggregation With Independent Works}{section.6} -\BOOKMARK [2][-]{subsection.6.8}{Translation}{section.6} -\BOOKMARK [2][-]{subsection.6.9}{Termination}{section.6} -\BOOKMARK [2][-]{subsection.6.10}{Future Revisions Of This License}{section.6} -\BOOKMARK [2][-]{subsection.6.11}{How to use this License for your documents}{section.6} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.pdf deleted file mode 100644 index 863a047..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.toc deleted file mode 100644 index 8e72aa2..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.toc +++ /dev/null @@ -1,65 +0,0 @@ -\contentsline {section}{\numberline {1}Introduction}{3}{section.1} -\contentsline {section}{\numberline {2}Installation}{4}{section.2} -\contentsline {subsection}{\numberline {2.1}Subversion}{4}{subsection.2.1} -\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2} -\contentsline {subsection}{\numberline {2.3}ImageMagick}{5}{subsection.2.3} -\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4} -\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5} -\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{6}{subsection.2.6} -\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7} -\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8} -\contentsline {section}{\numberline {3}Configuration}{7}{section.3} -\contentsline {subsection}{\numberline {3.1}Firewall}{7}{subsection.3.1} -\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2} -\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1} -\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2} -\contentsline {subsection}{\numberline {3.3}Working Copy}{8}{subsection.3.3} -\contentsline {subsection}{\numberline {3.4}User Identification}{9}{subsection.3.4} -\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{9}{subsubsection.3.4.1} -\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2} -\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5} -\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1} -\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{10}{subsubsection.3.5.2} -\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{10}{subsubsection.3.5.3} -\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4} -\contentsline {section}{\numberline {4}Framework}{10}{section.4} -\contentsline {subsection}{\numberline {4.1}Identity}{11}{subsection.4.1} -\contentsline {subsubsection}{\numberline {4.1.1}Design Templates}{11}{subsubsection.4.1.1} -\contentsline {subsubsection}{\numberline {4.1.2}Design Templates Export Id}{13}{subsubsection.4.1.2} -\contentsline {subsubsection}{\numberline {4.1.3}Design Models}{13}{subsubsection.4.1.3} -\contentsline {subsubsection}{\numberline {4.1.4}Image Files}{13}{subsubsection.4.1.4} -\contentsline {subsubsection}{\numberline {4.1.5}Image Files Rendering}{18}{subsubsection.4.1.5} -\contentsline {subsection}{\numberline {4.2}Translations}{18}{subsection.4.2} -\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{18}{subsubsection.4.2.1} -\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{18}{subsubsection.4.2.2} -\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{19}{subsubsection.4.2.3} -\contentsline {subsubsection}{\numberline {4.2.4}Translation Markers}{21}{subsubsection.4.2.4} -\contentsline {subsubsection}{\numberline {4.2.5}Translation Rendering}{21}{subsubsection.4.2.5} -\contentsline {subsubsection}{\numberline {4.2.6}Translation Rendering Script}{23}{subsubsection.4.2.6} -\contentsline {subsubsection}{\numberline {4.2.7}Translation Template Directory}{24}{subsubsection.4.2.7} -\contentsline {subsection}{\numberline {4.3}Manuals}{24}{subsection.4.3} -\contentsline {subsubsection}{\numberline {4.3.1}Writing Style}{24}{subsubsection.4.3.1} -\contentsline {subsubsection}{\numberline {4.3.2}File Structure}{24}{subsubsection.4.3.2} -\contentsline {subsubsection}{\numberline {4.3.3}Exporting To PDF}{26}{subsubsection.4.3.3} -\contentsline {subsection}{\numberline {4.4}Scripts}{26}{subsection.4.4} -\contentsline {subsubsection}{\numberline {4.4.1}Invocation Scripts}{27}{subsubsection.4.4.1} -\contentsline {subsubsection}{\numberline {4.4.2}Configuration Scripts}{27}{subsubsection.4.4.2} -\contentsline {subsubsection}{\numberline {4.4.3}Function Scripts}{27}{subsubsection.4.4.3} -\contentsline {section}{\numberline {5}Rebranding}{29}{section.5} -\contentsline {subsection}{\numberline {5.1}Images}{29}{subsection.5.1} -\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{29}{subsubsection.5.1.1} -\contentsline {subsection}{\numberline {5.2}Messages Locale}{29}{subsection.5.2} -\contentsline {subsection}{\numberline {5.3}Release Notes}{31}{subsection.5.3} -\contentsline {subsubsection}{\numberline {5.3.1}centos-release-notes}{31}{subsubsection.5.3.1} -\contentsline {section}{\numberline {6}GNU Free Documentation License}{32}{section.6} -\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{32}{subsection.6.1} -\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{34}{subsection.6.2} -\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{35}{subsection.6.3} -\contentsline {subsection}{\numberline {6.4}Modifications}{35}{subsection.6.4} -\contentsline {subsection}{\numberline {6.5}Combining Documents}{38}{subsection.6.5} -\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{38}{subsection.6.6} -\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{39}{subsection.6.7} -\contentsline {subsection}{\numberline {6.8}Translation}{39}{subsection.6.8} -\contentsline {subsection}{\numberline {6.9}Termination}{40}{subsection.6.9} -\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{40}{subsection.6.10} -\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{40}{subsection.6.11} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/manual.tex deleted file mode 100644 index 6858918..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/manual.tex +++ /dev/null @@ -1,56 +0,0 @@ -\documentclass[12pt]{article} -\usepackage[pdftex]{graphicx} -\usepackage{hyperref} -\hypersetup{pdfauthor={Alain Reguera Delgado},% - pdftitle={Anaconda Progress Visual Style},% - pdfsubject={CentOS Corporate Visual Identity}% - } - -% Tell LaTeX how to hyphenate a word. Don't hyphenate the following -% words: -\hyphenation{CentOS CENTOSARTWORK} - -\title{Anaconda Progress Visual Style} -\author{Alain Reguera Delgado} - -\begin{document} - -\maketitle - -\begin{abstract} - -This article describes the visual style of Anaconda Progress. -Anaconda Progress screen is shown after configuration and while -packages are installed. Anaconda Progress screen has a header, and -slide images which alternate with release notes texts. This article -describes Anaconda Progress slide images and release notes only. The -header component of Anaconda Progress is described in the document -``Anaconda Header Visual Style''. - -Anaconda is the name of the install program used by CentOS. It is -python-based with some custom modules written in C. The Anaconda -installer works on a wide variety of Linux-based computing -architectures (ia32, Itanium, Alpha, S/390, PowerPC), and is designed -to make it easy to add platforms. - -Copyright \copyright\ 2010 The CentOS Project. Permission is granted -to copy, distribute and/or modify this document under the terms of the -GNU Free Documentation License, Version 1.2 or any later version -published by the Free Software Foundation; with no Invariant Sections, -no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled ``GNU Free Documentation -License''. - -\end{abstract} - -\tableofcontents - -\input{sections/introduction.tex} -\input{../../../../../installation.tex} -\input{../../../../../configuration.tex} -\input{sections/framework.tex} -\input{sections/rebranding.tex} - -\input{../../../../../Licenses/GFDL.tex} - -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.aux deleted file mode 100644 index 6e38102..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.aux +++ /dev/null @@ -1,104 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{3}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Installation}{3}{section.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Subversion}{4}{subsection.2.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}ImageMagick}{5}{subsection.2.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{6}{subsection.2.6}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Configuration}{6}{section.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{9}{subsubsection.3.4.1}} -\newlabel{sec:Configuration:Account}{{3.4.1}{9}{Account Registration\relax }{subsubsection.3.4.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2}} -\newlabel{sec:Configuration:User:Privileges}{{3.4.2}{9}{Account Privileges\relax }{subsubsection.3.4.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5}} -\newlabel{sec:Configuration:Environment}{{3.5}{9}{Shell Environment\relax }{subsection.3.5}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Framework}{10}{section.4}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1}} -\newlabel{sec:Identity}{{4.1}{10}{Identity\relax }{subsection.4.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3}} -\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Anaconda Prompt translation markers.}}{12}{table.1}} -\newlabel{tab:Identity:Markers}{{1}{12}{Markers\relax }{table.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.4}Images}{12}{subsubsection.4.1.4}} -\newlabel{sec:Identity:Images}{{4.1.4}{12}{Images\relax }{subsubsection.4.1.4}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.5}Color Limitations}{12}{subsubsection.4.1.5}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.6}Color Palettes}{12}{subsubsection.4.1.6}} -\newlabel{sec:Identity:Palettes}{{4.1.6}{12}{Color Palettes\relax }{subsubsection.4.1.6}{}} -\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Color position in \texttt {Syslinux.ppm} image. Syslinux background color (A) is in the position 0. Syslinux foreground color (B) is in the position 7.}}{13}{figure.1}} -\newlabel{fig:Identity:Palette}{{1}{13}{Color Palettes\relax }{figure.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.7}Models}{14}{subsubsection.4.1.7}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.8}Rendering}{14}{subsubsection.4.1.8}} -\newlabel{sec:Identity:Rendering}{{4.1.8}{14}{Rendering\relax }{subsubsection.4.1.8}{}} -\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces Anaconda Prompt design model.}}{15}{figure.2}} -\newlabel{fig:Identity:Design:Model}{{2}{15}{Models\relax }{figure.2}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.9}Issues}{15}{subsubsection.4.1.9}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.2}Translations}{16}{subsection.4.2}} -\newlabel{sec:Translations}{{4.2}{16}{Translations\relax }{subsection.4.2}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{16}{subsubsection.4.2.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{16}{subsubsection.4.2.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{16}{subsubsection.4.2.3}} -\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Anaconda Prompt translation path.}}{17}{figure.3}} -\newlabel{fig:Translation:Path}{{3}{17}{Translation Path\relax }{figure.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}Manuals}{18}{subsection.4.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Scripts}{18}{subsection.4.4}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{18}{subsubsection.4.4.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{18}{subsubsection.4.4.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{18}{subsubsection.4.4.3}} -\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces Rendering design model.}}{19}{figure.4}} -\newlabel{fig:Scripts:Rendering}{{4}{19}{Rendering\relax }{figure.4}{}} -\@writefile{toc}{\contentsline {section}{\numberline {5}Rebranding}{20}{section.5}} -\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}Images}{20}{subsection.5.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{20}{subsubsection.5.1.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Syslinux}{21}{subsection.5.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {5.3}Messages Locale}{21}{subsection.5.3}} -\@writefile{toc}{\contentsline {section}{\numberline {6}GNU Free Documentation License}{22}{section.6}} -\newlabel{sec:License-GFDL-0}{{6}{22}{Preamble\relax }{section*.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{22}{subsection.6.1}} -\newlabel{sec:License-GFDL-1}{{6.1}{22}{Applicability And Definitions\relax }{subsection.6.1}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{24}{subsection.6.2}} -\newlabel{sec:License-GFDL-2}{{6.2}{24}{Verbatim Copying\relax }{subsection.6.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{25}{subsection.6.3}} -\newlabel{sec:License-GFDL-3}{{6.3}{25}{Copying In Quantity\relax }{subsection.6.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.4}Modifications}{25}{subsection.6.4}} -\newlabel{sec:License-GFDL-4}{{6.4}{25}{Modifications\relax }{subsection.6.4}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.5}Combining Documents}{28}{subsection.6.5}} -\newlabel{sec:License-GFDL-5}{{6.5}{28}{Combining Documents\relax }{subsection.6.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{28}{subsection.6.6}} -\newlabel{sec:License-GFDL-6}{{6.6}{28}{Collections Of Documents\relax }{subsection.6.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{29}{subsection.6.7}} -\newlabel{sec:License-GFDL-7}{{6.7}{29}{Aggregation With Independent Works\relax }{subsection.6.7}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.8}Translation}{29}{subsection.6.8}} -\newlabel{sec:License-GFDL-8}{{6.8}{29}{Translation\relax }{subsection.6.8}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.9}Termination}{30}{subsection.6.9}} -\newlabel{sec:License-GFDL-9}{{6.9}{30}{Termination\relax }{subsection.6.9}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{30}{subsection.6.10}} -\newlabel{sec:License-GFDL-10}{{6.10}{30}{Future Revisions Of This License\relax }{subsection.6.10}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{30}{subsection.6.11}} -\newlabel{sec:License-GFDL-11}{{6.11}{30}{How to use this License for your documents\relax }{subsection.6.11}{}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.log deleted file mode 100644 index 2eb3ce6..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.log +++ /dev/null @@ -1,404 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 12 MAR 2010 14:17 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size12.clo -File: size12.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/tools/longtable.sty -Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) -\LTleft=\skip43 -\LTright=\skip44 -\LTpre=\skip45 -\LTpost=\skip46 -\LTchunksize=\count87 -\LTcapwidth=\dimen103 -\LT@head=\box26 -\LT@firsthead=\box27 -\LT@foot=\box28 -\LT@lastfoot=\box29 -\LT@cols=\count88 -\LT@rows=\count89 -\c@LT@tables=\count90 -\c@LT@chunks=\count91 -\LT@p@ftn=\toks14 -) -(/usr/share/texmf/tex/latex/graphics/graphicx.sty -Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks15 -) -(/usr/share/texmf/tex/latex/graphics/graphics.sty -Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/trig.sty -Package: trig 1999/03/16 v1.09 sin cos tan (DPC) -) -(/usr/share/texmf/tex/latex/graphics/graphics.cfg -File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive -) -Package graphics Info: Driver file: pdftex.def on input line 80. - -(/usr/share/texmf/tex/latex/graphics/pdftex.def -File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex -\Gread@gobject=\count92 -)) -\Gin@req@height=\dimen104 -\Gin@req@width=\dimen105 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX -\@linkdim=\dimen106 -\Hy@linkcounter=\count93 -\Hy@pagecounter=\count94 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count95 -\Field@Width=\dimen107 -\Fld@charsize=\dimen108 -\Choice@toks=\toks16 -\Field@toks=\toks17 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count96 -\c@Hfootnote=\count97 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count98 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. - -(/usr/share/texmf/tex/context/base/supp-pdf.tex -(/usr/share/texmf/tex/context/base/supp-mis.tex -loading : Context Support Macros / Miscellaneous (2004.10.26) -\protectiondepth=\count99 -\scratchcounter=\count100 -\scratchtoks=\toks18 -\scratchdimen=\dimen109 -\scratchskip=\skip47 -\scratchmuskip=\muskip11 -\scratchbox=\box30 -\scratchread=\read1 -\scratchwrite=\write4 -\zeropoint=\dimen110 -\onepoint=\dimen111 -\onebasepoint=\dimen112 -\minusone=\count101 -\thousandpoint=\dimen113 -\onerealpoint=\dimen114 -\emptytoks=\toks19 -\nextbox=\box31 -\nextdepth=\dimen115 -\everyline=\toks20 -\!!counta=\count102 -\!!countb=\count103 -\recursecounter=\count104 -) -loading : Context Support Macros / PDF (2004.03.26) -\nofMPsegments=\count105 -\nofMParguments=\count106 -\MPscratchCnt=\count107 -\MPscratchDim=\dimen116 -\MPnumerator=\count108 -\everyMPtoPDFconversion=\toks21 -) -Package hyperref Info: Link coloring OFF on input line 17. - (/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count109 -) -LaTeX Info: Redefining \ref on input line 17. -LaTeX Info: Redefining \pageref on input line 17. - (./Manual.out) -(./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <14.4> on input line 20. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 20. - (./Manual.toc -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 3. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 3. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 3. - [1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] [2]) -\tf@toc=\write5 -\openout5 = `Manual.toc'. - - (./sections/introduction.tex) (../../../../../installation.tex -[3] -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 25. - -Overfull \hbox (8.37456pt too wide) in paragraph at lines 53--54 -[][]$\OT1/cmtt/m/n/12 http : / / wiki . centos . org / AdditionalResources / Re -positories$[] - [] - -Missing character: There is no � in font cmr12! -Missing character: There is no � in font cmr12! -[4] -LaTeX Font Info: Try loading font information for OMS+cmr on input line 94. - (/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <12> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 94. - [5]) -(../../../../../configuration.tex [6] -Overfull \hbox (11.3752pt too wide) in paragraph at lines 60--60 -[]\OT1/cmtt/m/n/12 # Squid only knows about standardized HTTP request met -hods.[] - [] - - -Overfull \hbox (11.3752pt too wide) in paragraph at lines 60--60 -[]\OT1/cmtt/m/n/12 # You can add up to 20 additional "extension" methods -here.[] - [] - -[7] -Overfull \hbox (23.88292pt too wide) in paragraph at lines 92--93 -[]\OT1/cmtt/m/n/12 svn co https://projects.centos.org/svn/artwork $\OMS/cmsy/m/ -n/12 ^^X$\OT1/cmtt/m/n/12 /Desktop/ - [] - -[8] -LaTeX Font Info: Font shape `OT1/cmtt/bx/n' in size <12> not available -(Font) Font shape `OT1/cmtt/m/n' tried instead on input line 162. - [9]) (./sections/framework.tex -Underfull \hbox (badness 10000) in paragraph at lines 10--11 - - [] - - -Overfull \hbox (6.44574pt too wide) in paragraph at lines 24--28 -[]\OT1/cmr/m/n/12 This de-sign is com-mon to each ma-jor re-lease of CentOS - [] - -[10] -Overfull \hbox (15.76491pt too wide) in paragraph at lines 51--56 -\OT1/cmr/m/n/12 ex-ported as PNG im-age. As con-ven-tion, we use the word `CENT -OSARTWORK' - [] - -[11] -Underfull \hbox (badness 10000) in paragraph at lines 102--103 - - [] - -[12] -Overfull \hbox (1.18143pt too wide) in paragraph at lines 143--145 -[]\OT1/cmr/m/n/12 Fill its pix-els with the col-ors spec-i-fied in the \OT1/cmt -t/m/n/12 Syslinux.gpl \OT1/cmr/m/n/12 palette. - [] - - -Overfull \hbox (4.80638pt too wide) in paragraph at lines 146--151 -[]\OT1/cmr/m/n/12 Set the ap-pro-pri-ate or-der of col-ors in-side the \OT1/cmt -t/m/n/12 Syslinux.ppm \OT1/cmr/m/n/12 palette. - [] - - -Overfull \hbox (12.90079pt too wide) in paragraph at lines 166--172 -\OT1/cmr/m/n/12 adec-i-mal color in-for-ma-tion and its in-dex po-si-tion de-fi -ned in \OT1/cmtt/m/n/12 Syslinux.ppm - [] - - -<../../../../../../Identity/Models/Distro/Anaconda/Prompt/img/build-1.pdf, id=4 -19, 467.7475pt x 132.495pt> -File: ../../../../../../Identity/Models/Distro/Anaconda/Prompt/img/build-1.pdf -Graphic file (type pdf) - - -[13 <../../../../../../Identity/Models/Distro/Anaconda/Prompt/img/build-1.pdf>] - -Underfull \hbox (badness 10000) in paragraph at lines 211--212 - - [] - - -<../../../../../../Identity/Models/Distro/Anaconda/Prompt/img/build-0.pdf, id=4 -38, 554.07pt x 385.44pt> -File: ../../../../../../Identity/Models/Distro/Anaconda/Prompt/img/build-0.pdf -Graphic file (type pdf) - - -[14] [15 <../../../../../../Identity/Models/Distro/Anaconda/Prompt/img/build-0. -pdf>] -Underfull \hbox (badness 10000) in paragraph at lines 279--280 - - [] - -[16] -Underfull \hbox (badness 10000) in paragraph at lines 364--365 - - [] - -[17] -<../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf, id=471, 5 -29.98pt x 589.20125pt> -File: ../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf Graph -ic file (type pdf) - - -Underfull \hbox (badness 10000) in paragraph at lines 392--393 - - [] - -[18] [19 <../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf>] -) (./sections/rebranding.tex -Overfull \hbox (2.56557pt too wide) in paragraph at lines 12--15 -[]\OT1/cmr/m/n/12 CentOS Brands and art-works are or-ga-nized in-side CentOS Ar -t-work Repos- - [] - -[20] -Overfull \hbox (11.3752pt too wide) in paragraph at lines 46--46 -[]\OT1/cmtt/m/n/12 trunk/Identity/Themes/$THEME/Distro/Anaconda/Prompt/img/$VER -SION/[] - [] - - -Overfull \hbox (11.3752pt too wide) in paragraph at lines 69--69 -[]\OT1/cmtt/m/n/12 trunk/Identity/Themes/$THEME/Distro/Anaconda/Prompt/img/$VER -SION/[] - [] - -) (../../../../../Licenses/GFDL.tex -Underfull \hbox (badness 10000) in paragraph at lines 5--14 - - [] - -[21] [22] [23] [24] [25] [26] [27] [28] [29] -Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 document under the terms of the GNU Free Documentation Li -cense,[] - [] - - -Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 Version 1.2 or any later version published by the Free So -ftware[] - [] - - -Overfull \hbox (5.2002pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 Foundation; with no Invariant Sections, no Front-Cover Te -xts,[] - [] - - -Overfull \hbox (11.3752pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 and no Back-Cover Texts. A copy of the license is includ -ed in[] - [] - - -Overfull \hbox (5.2002pt too wide) in paragraph at lines 425--425 -[] \OT1/cmtt/m/n/12 with the Invariant Sections being LIST THEIR TITLES, with - the[] - [] - -[30]) [31] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 2918 strings out of 94500 - 40182 string characters out of 1176766 - 91201 words of memory out of 1000000 - 5947 multiletter control sequences out of 10000+50000 - 11266 words of font info for 40 fonts, out of 500000 for 2000 - 582 hyphenation exceptions out of 1000 - 27i,8n,36p,274b,267s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 551 PDF objects out of 300000 - 112 named destinations out of 131072 - 520 words of extra memory for PDF output out of 65536 - - -Output written on Manual.pdf (31 pages, 313018 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.out deleted file mode 100644 index 5f4414a..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.out +++ /dev/null @@ -1,61 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Introduction}{} -\BOOKMARK [1][-]{section.2}{Installation}{} -\BOOKMARK [2][-]{subsection.2.1}{Subversion}{section.2} -\BOOKMARK [2][-]{subsection.2.2}{Inkscape}{section.2} -\BOOKMARK [2][-]{subsection.2.3}{ImageMagick}{section.2} -\BOOKMARK [2][-]{subsection.2.4}{Netpbm}{section.2} -\BOOKMARK [2][-]{subsection.2.5}{Syslinux}{section.2} -\BOOKMARK [2][-]{subsection.2.6}{GNU Image Manipulation Program}{section.2} -\BOOKMARK [2][-]{subsection.2.7}{GNU Core Utilities}{section.2} -\BOOKMARK [2][-]{subsection.2.8}{LaTeX}{section.2} -\BOOKMARK [1][-]{section.3}{Configuration}{} -\BOOKMARK [2][-]{subsection.3.1}{Firewall}{section.3} -\BOOKMARK [2][-]{subsection.3.2}{Subversion Behind Squid}{section.3} -\BOOKMARK [3][-]{subsubsection.3.2.1}{Subversion Client Configuration}{subsection.3.2} -\BOOKMARK [3][-]{subsubsection.3.2.2}{Squid Server Configuration}{subsection.3.2} -\BOOKMARK [2][-]{subsection.3.3}{Working Copy}{section.3} -\BOOKMARK [2][-]{subsection.3.4}{User Identification}{section.3} -\BOOKMARK [3][-]{subsubsection.3.4.1}{Account Registration}{subsection.3.4} -\BOOKMARK [3][-]{subsubsection.3.4.2}{Account Privileges}{subsection.3.4} -\BOOKMARK [2][-]{subsection.3.5}{Shell Environment}{section.3} -\BOOKMARK [3][-]{subsubsection.3.5.1}{Relative Paths}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.2}{Absolute Paths}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.3}{Environment Variable Definition}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.4}{Environment Variable Initialization}{subsection.3.5} -\BOOKMARK [1][-]{section.4}{Framework}{} -\BOOKMARK [2][-]{subsection.4.1}{Identity}{section.4} -\BOOKMARK [3][-]{subsubsection.4.1.1}{Designs}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.2}{Export Id}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.3}{Markers}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.4}{Images}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.5}{Color Limitations}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.6}{Color Palettes}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.7}{Models}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.8}{Rendering}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.9}{Issues}{subsection.4.1} -\BOOKMARK [2][-]{subsection.4.2}{Translations}{section.4} -\BOOKMARK [3][-]{subsubsection.4.2.1}{Common Translations}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.2}{Specific Translations}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.3}{Translation Path}{subsection.4.2} -\BOOKMARK [2][-]{subsection.4.3}{Manuals}{section.4} -\BOOKMARK [2][-]{subsection.4.4}{Scripts}{section.4} -\BOOKMARK [3][-]{subsubsection.4.4.1}{Rendering}{subsection.4.4} -\BOOKMARK [3][-]{subsubsection.4.4.2}{Pre-rendering}{subsection.4.4} -\BOOKMARK [3][-]{subsubsection.4.4.3}{Post-rendering}{subsection.4.4} -\BOOKMARK [1][-]{section.5}{Rebranding}{} -\BOOKMARK [2][-]{subsection.5.1}{Images}{section.5} -\BOOKMARK [3][-]{subsubsection.5.1.1}{redhat-logos}{subsection.5.1} -\BOOKMARK [2][-]{subsection.5.2}{Syslinux}{section.5} -\BOOKMARK [2][-]{subsection.5.3}{Messages Locale}{section.5} -\BOOKMARK [1][-]{section.6}{GNU Free Documentation License}{} -\BOOKMARK [2][-]{subsection.6.1}{Applicability And Definitions}{section.6} -\BOOKMARK [2][-]{subsection.6.2}{Verbatim Copying}{section.6} -\BOOKMARK [2][-]{subsection.6.3}{Copying In Quantity}{section.6} -\BOOKMARK [2][-]{subsection.6.4}{Modifications}{section.6} -\BOOKMARK [2][-]{subsection.6.5}{Combining Documents}{section.6} -\BOOKMARK [2][-]{subsection.6.6}{Collections Of Documents}{section.6} -\BOOKMARK [2][-]{subsection.6.7}{Aggregation With Independent Works}{section.6} -\BOOKMARK [2][-]{subsection.6.8}{Translation}{section.6} -\BOOKMARK [2][-]{subsection.6.9}{Termination}{section.6} -\BOOKMARK [2][-]{subsection.6.10}{Future Revisions Of This License}{section.6} -\BOOKMARK [2][-]{subsection.6.11}{How to use this License for your documents}{section.6} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.pdf deleted file mode 100644 index e673587..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.toc deleted file mode 100644 index 195feab..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.toc +++ /dev/null @@ -1,61 +0,0 @@ -\contentsline {section}{\numberline {1}Introduction}{3}{section.1} -\contentsline {section}{\numberline {2}Installation}{3}{section.2} -\contentsline {subsection}{\numberline {2.1}Subversion}{4}{subsection.2.1} -\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2} -\contentsline {subsection}{\numberline {2.3}ImageMagick}{5}{subsection.2.3} -\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4} -\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5} -\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{6}{subsection.2.6} -\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7} -\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8} -\contentsline {section}{\numberline {3}Configuration}{6}{section.3} -\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1} -\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2} -\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1} -\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2} -\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3} -\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4} -\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{9}{subsubsection.3.4.1} -\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2} -\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5} -\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1} -\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2} -\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3} -\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4} -\contentsline {section}{\numberline {4}Framework}{10}{section.4} -\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1} -\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1} -\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2} -\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3} -\contentsline {subsubsection}{\numberline {4.1.4}Images}{12}{subsubsection.4.1.4} -\contentsline {subsubsection}{\numberline {4.1.5}Color Limitations}{12}{subsubsection.4.1.5} -\contentsline {subsubsection}{\numberline {4.1.6}Color Palettes}{12}{subsubsection.4.1.6} -\contentsline {subsubsection}{\numberline {4.1.7}Models}{14}{subsubsection.4.1.7} -\contentsline {subsubsection}{\numberline {4.1.8}Rendering}{14}{subsubsection.4.1.8} -\contentsline {subsubsection}{\numberline {4.1.9}Issues}{15}{subsubsection.4.1.9} -\contentsline {subsection}{\numberline {4.2}Translations}{16}{subsection.4.2} -\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{16}{subsubsection.4.2.1} -\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{16}{subsubsection.4.2.2} -\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{16}{subsubsection.4.2.3} -\contentsline {subsection}{\numberline {4.3}Manuals}{18}{subsection.4.3} -\contentsline {subsection}{\numberline {4.4}Scripts}{18}{subsection.4.4} -\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{18}{subsubsection.4.4.1} -\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{18}{subsubsection.4.4.2} -\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{18}{subsubsection.4.4.3} -\contentsline {section}{\numberline {5}Rebranding}{20}{section.5} -\contentsline {subsection}{\numberline {5.1}Images}{20}{subsection.5.1} -\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{20}{subsubsection.5.1.1} -\contentsline {subsection}{\numberline {5.2}Syslinux}{21}{subsection.5.2} -\contentsline {subsection}{\numberline {5.3}Messages Locale}{21}{subsection.5.3} -\contentsline {section}{\numberline {6}GNU Free Documentation License}{22}{section.6} -\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{22}{subsection.6.1} -\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{24}{subsection.6.2} -\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{25}{subsection.6.3} -\contentsline {subsection}{\numberline {6.4}Modifications}{25}{subsection.6.4} -\contentsline {subsection}{\numberline {6.5}Combining Documents}{28}{subsection.6.5} -\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{28}{subsection.6.6} -\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{29}{subsection.6.7} -\contentsline {subsection}{\numberline {6.8}Translation}{29}{subsection.6.8} -\contentsline {subsection}{\numberline {6.9}Termination}{30}{subsection.6.9} -\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{30}{subsection.6.10} -\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{30}{subsection.6.11} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/manual.tex deleted file mode 100644 index e46842a..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/manual.tex +++ /dev/null @@ -1,56 +0,0 @@ -\documentclass[12pt]{article} -\usepackage{longtable} -\usepackage[pdftex]{graphicx} -\usepackage{hyperref} -\hypersetup{pdfauthor={Alain Reguera Delgado},% - pdftitle={Anaconda Prompt Visual Style},% - pdfsubject={CentOS Corporate Visual Identity}% - } - -% Tell LaTeX how to hyphenate a word. Don't hyphenate the following -% words: -\hyphenation{CentOS CENTOSARTWORK} - -\title{Anaconda Prompt Visual Style} -\author{Alain Reguera Delgado} - -\begin{document} - -\maketitle - -\begin{abstract} - -This article describes Anaconda Prompt. Anaconda Prompt is the first -screen shown after booting up with the install CD/DVD medium. Anaconda -Prompt is based on H. Peter Anvin's syslinux suite of bootloaders, -specifically on the \texttt{isolinux} bootloader. The -\texttt{syslinux} suite and its documentation come inside the -\texttt{syslinux} package, available through \texttt{yum} in the -\texttt{[base]} repository of CentOS Distribution. - -Anaconda is the name of the install program used by CentOS. It is -python-based with some custom modules written in C. The anaconda -installer works on a wide variety of Linux-based computing -architectures (ia32, Itanium, Alpha, S/390, PowerPC), and is designed -to make it easy to add platforms. - -Copyright (C) 2010 The CentOS Project. Permission is granted to copy, -distribute and/or modify this document under the terms of the GNU Free -Documentation License, Version 1.2 or any later version published by -the Free Software Foundation; with no Invariant Sections, no -Front-Cover Texts, and no Back-Cover Texts. A copy of the license is -included in the section entitled ``GNU Free Documentation License''. - -\end{abstract} - -\tableofcontents - -\input{sections/introduction.tex} -\input{../../../../../installation.tex} -\input{../../../../../configuration.tex} -\input{sections/framework.tex} -\input{sections/rebranding.tex} - -\input{../../../../../Licenses/GFDL.tex} - -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.aux deleted file mode 100644 index bb89e14..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.aux +++ /dev/null @@ -1,97 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{3}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Installation}{3}{section.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Subversion}{3}{subsection.2.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}ImageMagick}{4}{subsection.2.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{5}{subsection.2.6}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7}} -\@writefile{toc}{\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Configuration}{6}{section.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{9}{subsubsection.3.4.1}} -\newlabel{sec:Configuration:Account}{{3.4.1}{9}{Account Registration\relax }{subsubsection.3.4.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2}} -\newlabel{sec:Configuration:User:Privileges}{{3.4.2}{9}{Account Privileges\relax }{subsubsection.3.4.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5}} -\newlabel{sec:Configuration:Environment}{{3.5}{9}{Shell Environment\relax }{subsection.3.5}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Framework}{10}{section.4}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1}} -\newlabel{sec:Identity}{{4.1}{10}{Identity\relax }{subsection.4.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3}} -\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Anaconda Splash translation markers.}}{12}{table.1}} -\newlabel{tab:Identity:Markers}{{1}{12}{Markers\relax }{table.1}{}} -\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Anaconda Splash design model.}}{12}{figure.1}} -\newlabel{fig:Identity:Design:Model}{{1}{12}{Models\relax }{figure.1}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.4}Images}{12}{subsubsection.4.1.4}} -\newlabel{sec:Identity:Images}{{4.1.4}{12}{Images\relax }{subsubsection.4.1.4}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.5}Models}{12}{subsubsection.4.1.5}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.6}Rendering}{13}{subsubsection.4.1.6}} -\newlabel{sec:Identity:Rendering}{{4.1.6}{13}{Rendering\relax }{subsubsection.4.1.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.2}Translations}{13}{subsection.4.2}} -\newlabel{sec:Translations}{{4.2}{13}{Translations\relax }{subsection.4.2}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{13}{subsubsection.4.2.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{13}{subsubsection.4.2.2}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{14}{subsubsection.4.2.3}} -\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces Anaconda Splash translation path.}}{14}{figure.2}} -\newlabel{fig:Translation:Path}{{2}{14}{Translation Path\relax }{figure.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}Manuals}{15}{subsection.4.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Scripts}{15}{subsection.4.4}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{15}{subsubsection.4.4.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{15}{subsubsection.4.4.2}} -\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Rendering design model.}}{16}{figure.3}} -\newlabel{fig:Scripts:Rendering}{{3}{16}{Rendering\relax }{figure.3}{}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{17}{subsubsection.4.4.3}} -\@writefile{toc}{\contentsline {section}{\numberline {5}Rebranding}{17}{section.5}} -\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}Images}{18}{subsection.5.1}} -\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{18}{subsubsection.5.1.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Messages Locale}{18}{subsection.5.2}} -\@writefile{toc}{\contentsline {section}{\numberline {6}GNU Free Documentation License}{18}{section.6}} -\newlabel{sec:License-GFDL-0}{{6}{19}{Preamble\relax }{section*.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{19}{subsection.6.1}} -\newlabel{sec:License-GFDL-1}{{6.1}{19}{Applicability And Definitions\relax }{subsection.6.1}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{21}{subsection.6.2}} -\newlabel{sec:License-GFDL-2}{{6.2}{21}{Verbatim Copying\relax }{subsection.6.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{21}{subsection.6.3}} -\newlabel{sec:License-GFDL-3}{{6.3}{21}{Copying In Quantity\relax }{subsection.6.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.4}Modifications}{22}{subsection.6.4}} -\newlabel{sec:License-GFDL-4}{{6.4}{22}{Modifications\relax }{subsection.6.4}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.5}Combining Documents}{25}{subsection.6.5}} -\newlabel{sec:License-GFDL-5}{{6.5}{25}{Combining Documents\relax }{subsection.6.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{25}{subsection.6.6}} -\newlabel{sec:License-GFDL-6}{{6.6}{25}{Collections Of Documents\relax }{subsection.6.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{25}{subsection.6.7}} -\newlabel{sec:License-GFDL-7}{{6.7}{25}{Aggregation With Independent Works\relax }{subsection.6.7}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.8}Translation}{26}{subsection.6.8}} -\newlabel{sec:License-GFDL-8}{{6.8}{26}{Translation\relax }{subsection.6.8}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.9}Termination}{26}{subsection.6.9}} -\newlabel{sec:License-GFDL-9}{{6.9}{26}{Termination\relax }{subsection.6.9}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{27}{subsection.6.10}} -\newlabel{sec:License-GFDL-10}{{6.10}{27}{Future Revisions Of This License\relax }{subsection.6.10}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{27}{subsection.6.11}} -\newlabel{sec:License-GFDL-11}{{6.11}{27}{How to use this License for your documents\relax }{subsection.6.11}{}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.log deleted file mode 100644 index 2c24e55..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.log +++ /dev/null @@ -1,361 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 12 MAR 2010 14:17 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size12.clo -File: size12.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/tools/longtable.sty -Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) -\LTleft=\skip43 -\LTright=\skip44 -\LTpre=\skip45 -\LTpost=\skip46 -\LTchunksize=\count87 -\LTcapwidth=\dimen103 -\LT@head=\box26 -\LT@firsthead=\box27 -\LT@foot=\box28 -\LT@lastfoot=\box29 -\LT@cols=\count88 -\LT@rows=\count89 -\c@LT@tables=\count90 -\c@LT@chunks=\count91 -\LT@p@ftn=\toks14 -) -(/usr/share/texmf/tex/latex/graphics/graphicx.sty -Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks15 -) -(/usr/share/texmf/tex/latex/graphics/graphics.sty -Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/trig.sty -Package: trig 1999/03/16 v1.09 sin cos tan (DPC) -) -(/usr/share/texmf/tex/latex/graphics/graphics.cfg -File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive -) -Package graphics Info: Driver file: pdftex.def on input line 80. - -(/usr/share/texmf/tex/latex/graphics/pdftex.def -File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex -\Gread@gobject=\count92 -)) -\Gin@req@height=\dimen104 -\Gin@req@width=\dimen105 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX -\@linkdim=\dimen106 -\Hy@linkcounter=\count93 -\Hy@pagecounter=\count94 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count95 -\Field@Width=\dimen107 -\Fld@charsize=\dimen108 -\Choice@toks=\toks16 -\Field@toks=\toks17 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count96 -\c@Hfootnote=\count97 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count98 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 17. -LaTeX Font Info: ... okay on input line 17. - -(/usr/share/texmf/tex/context/base/supp-pdf.tex -(/usr/share/texmf/tex/context/base/supp-mis.tex -loading : Context Support Macros / Miscellaneous (2004.10.26) -\protectiondepth=\count99 -\scratchcounter=\count100 -\scratchtoks=\toks18 -\scratchdimen=\dimen109 -\scratchskip=\skip47 -\scratchmuskip=\muskip11 -\scratchbox=\box30 -\scratchread=\read1 -\scratchwrite=\write4 -\zeropoint=\dimen110 -\onepoint=\dimen111 -\onebasepoint=\dimen112 -\minusone=\count101 -\thousandpoint=\dimen113 -\onerealpoint=\dimen114 -\emptytoks=\toks19 -\nextbox=\box31 -\nextdepth=\dimen115 -\everyline=\toks20 -\!!counta=\count102 -\!!countb=\count103 -\recursecounter=\count104 -) -loading : Context Support Macros / PDF (2004.03.26) -\nofMPsegments=\count105 -\nofMParguments=\count106 -\MPscratchCnt=\count107 -\MPscratchDim=\dimen116 -\MPnumerator=\count108 -\everyMPtoPDFconversion=\toks21 -) -Package hyperref Info: Link coloring OFF on input line 17. - (/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count109 -) -LaTeX Info: Redefining \ref on input line 17. -LaTeX Info: Redefining \pageref on input line 17. - (./Manual.out) -(./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <14.4> on input line 20. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 20. - (./Manual.toc -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 3. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 3. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 3. - [1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] [2]) -\tf@toc=\write5 -\openout5 = `Manual.toc'. - - (./sections/introduction.tex) (../../../../../installation.tex -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 25. - -[3] -Overfull \hbox (8.37456pt too wide) in paragraph at lines 53--54 -[][]$\OT1/cmtt/m/n/12 http : / / wiki . centos . org / AdditionalResources / Re -positories$[] - [] - -Missing character: There is no � in font cmr12! -Missing character: There is no � in font cmr12! -[4] -LaTeX Font Info: Try loading font information for OMS+cmr on input line 94. - (/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <12> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 94. - [5]) -(../../../../../configuration.tex [6] -Overfull \hbox (11.3752pt too wide) in paragraph at lines 60--60 -[]\OT1/cmtt/m/n/12 # Squid only knows about standardized HTTP request met -hods.[] - [] - - -Overfull \hbox (11.3752pt too wide) in paragraph at lines 60--60 -[]\OT1/cmtt/m/n/12 # You can add up to 20 additional "extension" methods -here.[] - [] - -[7] -Overfull \hbox (23.88292pt too wide) in paragraph at lines 92--93 -[]\OT1/cmtt/m/n/12 svn co https://projects.centos.org/svn/artwork $\OMS/cmsy/m/ -n/12 ^^X$\OT1/cmtt/m/n/12 /Desktop/ - [] - -[8] -LaTeX Font Info: Font shape `OT1/cmtt/bx/n' in size <12> not available -(Font) Font shape `OT1/cmtt/m/n' tried instead on input line 162. - [9]) (./sections/framework.tex -Underfull \hbox (badness 10000) in paragraph at lines 10--11 - - [] - -[10] -Overfull \hbox (15.76491pt too wide) in paragraph at lines 51--56 -\OT1/cmr/m/n/12 ex-ported as PNG im-age. As con-ven-tion, we use the word `CENT -OSARTWORK' - [] - -[11] -Underfull \hbox (badness 10000) in paragraph at lines 94--95 - - [] - - -<../../../../../../Identity/Models/Distro/Anaconda/Splash/img/build-0.pdf, id=3 -87, 691.58376pt x 481.8pt> -File: ../../../../../../Identity/Models/Distro/Anaconda/Splash/img/build-0.pdf -Graphic file (type pdf) - - -[12 <../../../../../../Identity/Models/Distro/Anaconda/Splash/img/build-0.pdf>] - -Underfull \hbox (badness 10000) in paragraph at lines 132--133 - - [] - -[13] [14] -Underfull \hbox (badness 10000) in paragraph at lines 217--218 - - [] - - -<../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf, id=416, 5 -29.98pt x 589.20125pt> -File: ../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf Graph -ic file (type pdf) - - -Underfull \hbox (badness 10000) in paragraph at lines 245--246 - - [] - -[15] [16 <../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf>] -) (./sections/rebranding.tex -Overfull \hbox (2.56557pt too wide) in paragraph at lines 12--15 -[]\OT1/cmr/m/n/12 CentOS Brands and art-works are or-ga-nized in-side CentOS Ar -t-work Repos- - [] - -[17] -Overfull \hbox (11.3752pt too wide) in paragraph at lines 46--46 -[]\OT1/cmtt/m/n/12 trunk/Identity/Themes/$THEME/Distro/Anaconda/Splash/img/$VER -SION/[] - [] - -) (../../../../../Licenses/GFDL.tex -Underfull \hbox (badness 10000) in paragraph at lines 5--14 - - [] - -[18] [19] [20] [21] [22] [23] [24] [25] [26] -Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 document under the terms of the GNU Free Documentation Li -cense,[] - [] - - -Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 Version 1.2 or any later version published by the Free So -ftware[] - [] - - -Overfull \hbox (5.2002pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 Foundation; with no Invariant Sections, no Front-Cover Te -xts,[] - [] - - -Overfull \hbox (11.3752pt too wide) in paragraph at lines 416--416 -[] \OT1/cmtt/m/n/12 and no Back-Cover Texts. A copy of the license is includ -ed in[] - [] - - -Overfull \hbox (5.2002pt too wide) in paragraph at lines 425--425 -[] \OT1/cmtt/m/n/12 with the Invariant Sections being LIST THEIR TITLES, with - the[] - [] - -) [27] [28] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 2888 strings out of 94500 - 39538 string characters out of 1176766 - 91110 words of memory out of 1000000 - 5934 multiletter control sequences out of 10000+50000 - 10751 words of font info for 38 fonts, out of 500000 for 2000 - 582 hyphenation exceptions out of 1000 - 27i,8n,36p,222b,267s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 495 PDF objects out of 300000 - 97 named destinations out of 131072 - 483 words of extra memory for PDF output out of 65536 - -Output written on Manual.pdf (28 pages, 272117 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.out deleted file mode 100644 index 9b9b706..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.out +++ /dev/null @@ -1,57 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Introduction}{} -\BOOKMARK [1][-]{section.2}{Installation}{} -\BOOKMARK [2][-]{subsection.2.1}{Subversion}{section.2} -\BOOKMARK [2][-]{subsection.2.2}{Inkscape}{section.2} -\BOOKMARK [2][-]{subsection.2.3}{ImageMagick}{section.2} -\BOOKMARK [2][-]{subsection.2.4}{Netpbm}{section.2} -\BOOKMARK [2][-]{subsection.2.5}{Syslinux}{section.2} -\BOOKMARK [2][-]{subsection.2.6}{GNU Image Manipulation Program}{section.2} -\BOOKMARK [2][-]{subsection.2.7}{GNU Core Utilities}{section.2} -\BOOKMARK [2][-]{subsection.2.8}{LaTeX}{section.2} -\BOOKMARK [1][-]{section.3}{Configuration}{} -\BOOKMARK [2][-]{subsection.3.1}{Firewall}{section.3} -\BOOKMARK [2][-]{subsection.3.2}{Subversion Behind Squid}{section.3} -\BOOKMARK [3][-]{subsubsection.3.2.1}{Subversion Client Configuration}{subsection.3.2} -\BOOKMARK [3][-]{subsubsection.3.2.2}{Squid Server Configuration}{subsection.3.2} -\BOOKMARK [2][-]{subsection.3.3}{Working Copy}{section.3} -\BOOKMARK [2][-]{subsection.3.4}{User Identification}{section.3} -\BOOKMARK [3][-]{subsubsection.3.4.1}{Account Registration}{subsection.3.4} -\BOOKMARK [3][-]{subsubsection.3.4.2}{Account Privileges}{subsection.3.4} -\BOOKMARK [2][-]{subsection.3.5}{Shell Environment}{section.3} -\BOOKMARK [3][-]{subsubsection.3.5.1}{Relative Paths}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.2}{Absolute Paths}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.3}{Environment Variable Definition}{subsection.3.5} -\BOOKMARK [3][-]{subsubsection.3.5.4}{Environment Variable Initialization}{subsection.3.5} -\BOOKMARK [1][-]{section.4}{Framework}{} -\BOOKMARK [2][-]{subsection.4.1}{Identity}{section.4} -\BOOKMARK [3][-]{subsubsection.4.1.1}{Designs}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.2}{Export Id}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.3}{Markers}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.4}{Images}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.5}{Models}{subsection.4.1} -\BOOKMARK [3][-]{subsubsection.4.1.6}{Rendering}{subsection.4.1} -\BOOKMARK [2][-]{subsection.4.2}{Translations}{section.4} -\BOOKMARK [3][-]{subsubsection.4.2.1}{Common Translations}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.2}{Specific Translations}{subsection.4.2} -\BOOKMARK [3][-]{subsubsection.4.2.3}{Translation Path}{subsection.4.2} -\BOOKMARK [2][-]{subsection.4.3}{Manuals}{section.4} -\BOOKMARK [2][-]{subsection.4.4}{Scripts}{section.4} -\BOOKMARK [3][-]{subsubsection.4.4.1}{Rendering}{subsection.4.4} -\BOOKMARK [3][-]{subsubsection.4.4.2}{Pre-rendering}{subsection.4.4} -\BOOKMARK [3][-]{subsubsection.4.4.3}{Post-rendering}{subsection.4.4} -\BOOKMARK [1][-]{section.5}{Rebranding}{} -\BOOKMARK [2][-]{subsection.5.1}{Images}{section.5} -\BOOKMARK [3][-]{subsubsection.5.1.1}{redhat-logos}{subsection.5.1} -\BOOKMARK [2][-]{subsection.5.2}{Messages Locale}{section.5} -\BOOKMARK [1][-]{section.6}{GNU Free Documentation License}{} -\BOOKMARK [2][-]{subsection.6.1}{Applicability And Definitions}{section.6} -\BOOKMARK [2][-]{subsection.6.2}{Verbatim Copying}{section.6} -\BOOKMARK [2][-]{subsection.6.3}{Copying In Quantity}{section.6} -\BOOKMARK [2][-]{subsection.6.4}{Modifications}{section.6} -\BOOKMARK [2][-]{subsection.6.5}{Combining Documents}{section.6} -\BOOKMARK [2][-]{subsection.6.6}{Collections Of Documents}{section.6} -\BOOKMARK [2][-]{subsection.6.7}{Aggregation With Independent Works}{section.6} -\BOOKMARK [2][-]{subsection.6.8}{Translation}{section.6} -\BOOKMARK [2][-]{subsection.6.9}{Termination}{section.6} -\BOOKMARK [2][-]{subsection.6.10}{Future Revisions Of This License}{section.6} -\BOOKMARK [2][-]{subsection.6.11}{How to use this License for your documents}{section.6} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.pdf deleted file mode 100644 index d79853a..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.toc deleted file mode 100644 index 170bf03..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.toc +++ /dev/null @@ -1,57 +0,0 @@ -\contentsline {section}{\numberline {1}Introduction}{3}{section.1} -\contentsline {section}{\numberline {2}Installation}{3}{section.2} -\contentsline {subsection}{\numberline {2.1}Subversion}{3}{subsection.2.1} -\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2} -\contentsline {subsection}{\numberline {2.3}ImageMagick}{4}{subsection.2.3} -\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4} -\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5} -\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{5}{subsection.2.6} -\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7} -\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8} -\contentsline {section}{\numberline {3}Configuration}{6}{section.3} -\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1} -\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2} -\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1} -\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2} -\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3} -\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4} -\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{9}{subsubsection.3.4.1} -\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2} -\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5} -\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1} -\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2} -\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3} -\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4} -\contentsline {section}{\numberline {4}Framework}{10}{section.4} -\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1} -\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1} -\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2} -\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3} -\contentsline {subsubsection}{\numberline {4.1.4}Images}{12}{subsubsection.4.1.4} -\contentsline {subsubsection}{\numberline {4.1.5}Models}{12}{subsubsection.4.1.5} -\contentsline {subsubsection}{\numberline {4.1.6}Rendering}{13}{subsubsection.4.1.6} -\contentsline {subsection}{\numberline {4.2}Translations}{13}{subsection.4.2} -\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{13}{subsubsection.4.2.1} -\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{13}{subsubsection.4.2.2} -\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{14}{subsubsection.4.2.3} -\contentsline {subsection}{\numberline {4.3}Manuals}{15}{subsection.4.3} -\contentsline {subsection}{\numberline {4.4}Scripts}{15}{subsection.4.4} -\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{15}{subsubsection.4.4.1} -\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{15}{subsubsection.4.4.2} -\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{17}{subsubsection.4.4.3} -\contentsline {section}{\numberline {5}Rebranding}{17}{section.5} -\contentsline {subsection}{\numberline {5.1}Images}{18}{subsection.5.1} -\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{18}{subsubsection.5.1.1} -\contentsline {subsection}{\numberline {5.2}Messages Locale}{18}{subsection.5.2} -\contentsline {section}{\numberline {6}GNU Free Documentation License}{18}{section.6} -\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{19}{subsection.6.1} -\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{21}{subsection.6.2} -\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{21}{subsection.6.3} -\contentsline {subsection}{\numberline {6.4}Modifications}{22}{subsection.6.4} -\contentsline {subsection}{\numberline {6.5}Combining Documents}{25}{subsection.6.5} -\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{25}{subsection.6.6} -\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{25}{subsection.6.7} -\contentsline {subsection}{\numberline {6.8}Translation}{26}{subsection.6.8} -\contentsline {subsection}{\numberline {6.9}Termination}{26}{subsection.6.9} -\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{27}{subsection.6.10} -\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{27}{subsection.6.11} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/manual.tex deleted file mode 100644 index e9f2c56..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/manual.tex +++ /dev/null @@ -1,51 +0,0 @@ -\documentclass[12pt]{article} -\usepackage{longtable} -\usepackage[pdftex]{graphicx} -\usepackage{hyperref} -\hypersetup{pdfauthor={Alain Reguera Delgado},% - pdftitle={Anaconda Splash Visual Style},% - pdfsubject={CentOS Corporate Visual Identity}% - } - -% Tell LaTeX how to hyphenate a word. Don't hyphenate the following -% words: -\hyphenation{CentOS CENTOSARTWORK} - -\title{Anaconda Splash Visual Style} -\author{Alain Reguera Delgado} - -\begin{document} - -\maketitle - -\begin{abstract} - -This article describes Anaconda Splash screen. This screen is shown -after Anaconda Prompt screen. - -Anaconda is the name of the install program used by CentOS. It is -python-based with some custom modules written in C. The anaconda -installer works on a wide variety of Linux-based computing -architectures (ia32, Itanium, Alpha, S/390, PowerPC), and is designed -to make it easy to add platforms. - -Copyright (C) 2010 The CentOS Project. Permission is granted to copy, -distribute and/or modify this document under the terms of the GNU Free -Documentation License, Version 1.2 or any later version published by -the Free Software Foundation; with no Invariant Sections, no -Front-Cover Texts, and no Back-Cover Texts. A copy of the license is -included in the section entitled ``GNU Free Documentation License''. - -\end{abstract} - -\tableofcontents - -\input{sections/introduction.tex} -\input{../../../../../installation.tex} -\input{../../../../../configuration.tex} -\input{sections/framework.tex} -\input{sections/rebranding.tex} - -\input{../../../../../Licenses/GFDL.tex} - -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.aux deleted file mode 100644 index 3cbc687..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.aux +++ /dev/null @@ -1,50 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\gdef \LT@i {\LT@entry - {1}{72.64pt}\LT@entry - {1}{297.61168pt}} -\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{2}{section.3}} -\gdef \LT@ii {\LT@entry - {1}{72.64pt}\LT@entry - {1}{261.17276pt}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Rendering}{3}{section.4}} -\@writefile{toc}{\contentsline {section}{\numberline {5}Configuration}{3}{section.5}} -\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{4}{section.6}} -\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{4}{section.7}} -\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{4}{section.8}} -\newlabel{sec:License-GFDL-0}{{8}{5}{Preamble\relax }{section*.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{5}{subsection.8.1}} -\newlabel{sec:License-GFDL-1}{{8.1}{5}{Applicability And Definitions\relax }{subsection.8.1}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{7}{subsection.8.2}} -\newlabel{sec:License-GFDL-2}{{8.2}{7}{Verbatim Copying\relax }{subsection.8.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{7}{subsection.8.3}} -\newlabel{sec:License-GFDL-3}{{8.3}{7}{Copying In Quantity\relax }{subsection.8.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{8}{subsection.8.4}} -\newlabel{sec:License-GFDL-4}{{8.4}{8}{Modifications\relax }{subsection.8.4}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{9}{subsection.8.5}} -\newlabel{sec:License-GFDL-5}{{8.5}{9}{Combining Documents\relax }{subsection.8.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{10}{subsection.8.6}} -\newlabel{sec:License-GFDL-6}{{8.6}{10}{Collections Of Documents\relax }{subsection.8.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{10}{subsection.8.7}} -\newlabel{sec:License-GFDL-7}{{8.7}{10}{Aggregation With Independent Works\relax }{subsection.8.7}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{11}{subsection.8.8}} -\newlabel{sec:License-GFDL-8}{{8.8}{11}{Translation\relax }{subsection.8.8}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{11}{subsection.8.9}} -\newlabel{sec:License-GFDL-9}{{8.9}{11}{Termination\relax }{subsection.8.9}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{11}{subsection.8.10}} -\newlabel{sec:License-GFDL-10}{{8.10}{11}{Future Revisions OF This License\relax }{subsection.8.10}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{11}{subsection.8.11}} -\newlabel{sec:License-GFDL-11}{{8.11}{11}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.log deleted file mode 100644 index ef922fd..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.log +++ /dev/null @@ -1,315 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size10.clo -File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/tools/longtable.sty -Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) -\LTleft=\skip43 -\LTright=\skip44 -\LTpre=\skip45 -\LTpost=\skip46 -\LTchunksize=\count87 -\LTcapwidth=\dimen103 -\LT@head=\box26 -\LT@firsthead=\box27 -\LT@foot=\box28 -\LT@lastfoot=\box29 -\LT@cols=\count88 -\LT@rows=\count89 -\c@LT@tables=\count90 -\c@LT@chunks=\count91 -\LT@p@ftn=\toks14 -) -(/usr/share/texmf/tex/latex/graphics/graphicx.sty -Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks15 -) -(/usr/share/texmf/tex/latex/graphics/graphics.sty -Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/trig.sty -Package: trig 1999/03/16 v1.09 sin cos tan (DPC) -) -(/usr/share/texmf/tex/latex/graphics/graphics.cfg -File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive -) -Package graphics Info: Driver file: pdftex.def on input line 80. - -(/usr/share/texmf/tex/latex/graphics/pdftex.def -File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex -\Gread@gobject=\count92 -)) -\Gin@req@height=\dimen104 -\Gin@req@width=\dimen105 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX -\@linkdim=\dimen106 -\Hy@linkcounter=\count93 -\Hy@pagecounter=\count94 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count95 -\Field@Width=\dimen107 -\Fld@charsize=\dimen108 -\Choice@toks=\toks16 -\Field@toks=\toks17 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count96 -\c@Hfootnote=\count97 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count98 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. - -(/usr/share/texmf/tex/context/base/supp-pdf.tex -(/usr/share/texmf/tex/context/base/supp-mis.tex -loading : Context Support Macros / Miscellaneous (2004.10.26) -\protectiondepth=\count99 -\scratchcounter=\count100 -\scratchtoks=\toks18 -\scratchdimen=\dimen109 -\scratchskip=\skip47 -\scratchmuskip=\muskip11 -\scratchbox=\box30 -\scratchread=\read1 -\scratchwrite=\write4 -\zeropoint=\dimen110 -\onepoint=\dimen111 -\onebasepoint=\dimen112 -\minusone=\count101 -\thousandpoint=\dimen113 -\onerealpoint=\dimen114 -\emptytoks=\toks19 -\nextbox=\box31 -\nextdepth=\dimen115 -\everyline=\toks20 -\!!counta=\count102 -\!!countb=\count103 -\recursecounter=\count104 -) -loading : Context Support Macros / PDF (2004.03.26) -\nofMPsegments=\count105 -\nofMParguments=\count106 -\MPscratchCnt=\count107 -\MPscratchDim=\dimen116 -\MPnumerator=\count108 -\everyMPtoPDFconversion=\toks21 -) -Package hyperref Info: Link coloring OFF on input line 13. - (/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count109 -) -LaTeX Info: Redefining \ref on input line 13. -LaTeX Info: Redefining \pageref on input line 13. - (./Manual.out) -(./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 16. -LaTeX Font Info: Try loading font information for OMS+cmr on input line 23. - (/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 23. - (./Manual.toc -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 9. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 9. - -[1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) -\tf@toc=\write5 -\openout5 = `Manual.toc'. - -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 37. - -(./table-theme.tex -Overfull \hbox (25.25168pt too wide) in alignment at lines 1--23 - [] [] - [] - - -Underfull \vbox (badness 10000) detected at line 23 - [] - - -Overfull \hbox (25.25168pt too wide) in alignment at lines 23--29 - [] [] - [] - -) [2] (./table-config.tex -Underfull \vbox (badness 10000) detected at line 23 - [] - -) -Overfull \hbox (49.8004pt too wide) in paragraph at lines 62--67 -[]\OT1/cmr/m/n/10 : The \OT1/cmtt/m/n/10 desktop[]gnome[]background.schemas \OT -1/cmr/m/n/10 and \OT1/cmtt/m/n/10 %gconf-tree.xml - [] - - -Overfull \hbox (26.49701pt too wide) in paragraph at lines 86--86 - [] \OT1/cmtt/m/n/10 2| /schemas/desktop/gnome/background/picture_filenam -e[] - [] - - -Overfull \hbox (26.49701pt too wide) in paragraph at lines 86--86 - [] \OT1/cmtt/m/n/10 3| /desktop/gnome/background/picture_filename[] - [] - - -Overfull \hbox (21.24706pt too wide) in paragraph at lines 86--86 - [] \OT1/cmtt/m/n/10 6| /usr/share/backgrounds/images/default.png[] - [] - -[3] -Overfull \hbox (189.24559pt too wide) in paragraph at lines 102--102 - []\OT1/cmtt/m/n/10 1| [] - [] - - -Overfull \hbox (5.4972pt too wide) in paragraph at lines 102--102 - []\OT1/cmtt/m/n/10 2| [] - [] - - -Overfull \hbox (105.24632pt too wide) in paragraph at lines 102--102 - []\OT1/cmtt/m/n/10 4| /usr/share/backgrounds/images/def -ault.png[] - [] - - -Overfull \hbox (31.74696pt too wide) in paragraph at lines 102--102 - []\OT1/cmtt/m/n/10 6| File to use for the background image[] - [] - -(../../../../Licenses/GFDL.tex -Underfull \hbox (badness 10000) in paragraph at lines 5--14 - - [] - -[4] [5] -Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 -\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple - HTML, PostScript - [] - -[6] [7] [8] [9] [10] [11]) [12] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 2749 strings out of 94500 - 36599 string characters out of 1176766 - 89641 words of memory out of 1000000 - 5870 multiletter control sequences out of 10000+50000 - 9615 words of font info for 34 fonts, out of 500000 for 2000 - 580 hyphenation exceptions out of 1000 - 27i,6n,36p,222b,318s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 194 PDF objects out of 300000 - 36 named destinations out of 131072 - 169 words of extra memory for PDF output out of 65536 - -Output written on Manual.pdf (12 pages, 126301 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.out deleted file mode 100644 index a194701..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.out +++ /dev/null @@ -1,19 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Workplace}{} -\BOOKMARK [1][-]{section.2}{Theme}{} -\BOOKMARK [1][-]{section.3}{Design}{} -\BOOKMARK [1][-]{section.4}{Rendering}{} -\BOOKMARK [1][-]{section.5}{Configuration}{} -\BOOKMARK [1][-]{section.6}{Testing}{} -\BOOKMARK [1][-]{section.7}{Issues}{} -\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} -\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} -\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} -\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} -\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} -\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} -\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} -\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} -\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} -\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.pdf deleted file mode 100644 index 5b8a4c0..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.toc deleted file mode 100644 index 17e027e..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.toc +++ /dev/null @@ -1,19 +0,0 @@ -\contentsline {section}{\numberline {1}Workplace}{2}{section.1} -\contentsline {section}{\numberline {2}Theme}{2}{section.2} -\contentsline {section}{\numberline {3}Design}{2}{section.3} -\contentsline {section}{\numberline {4}Rendering}{3}{section.4} -\contentsline {section}{\numberline {5}Configuration}{3}{section.5} -\contentsline {section}{\numberline {6}Testing}{4}{section.6} -\contentsline {section}{\numberline {7}Issues}{4}{section.7} -\contentsline {section}{\numberline {8}GNU Free Documentation License}{4}{section.8} -\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{5}{subsection.8.1} -\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{7}{subsection.8.2} -\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{7}{subsection.8.3} -\contentsline {subsection}{\numberline {8.4}Modifications}{8}{subsection.8.4} -\contentsline {subsection}{\numberline {8.5}Combining Documents}{9}{subsection.8.5} -\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{10}{subsection.8.6} -\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{10}{subsection.8.7} -\contentsline {subsection}{\numberline {8.8}Translation}{11}{subsection.8.8} -\contentsline {subsection}{\numberline {8.9}Termination}{11}{subsection.8.9} -\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{11}{subsection.8.10} -\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{11}{subsection.8.11} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/build.sh b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/build.sh deleted file mode 100755 index c7286c4..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/build.sh +++ /dev/null @@ -1,58 +0,0 @@ -#!/bin/bash -# -# Build Background tables for LaTeX documents. -# -# Copyright (C) 2009 Alain Reguera Delgado -# -# 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:$ -#-------------------------------------- - -# Load dependencies. -. ~/artwork/trunk/Scripts/Bash/loadFunctions.sh - -# Define the names of your tables. -FILES="table-theme.tex - table-config.tex" - -for FILE in $FILES;do - - # Let know which table we are creating. - echo $FILE - - # Define what to do with each table you define on FILES. - case $FILE in - - table-theme.tex ) - # Create table holding theme files. - ROWS="$(getFiles '/usr/share/backgrounds' 'default.*\.(jpg|png)')" - ;; - - table-config.tex ) - # Create table holding configuration files. - ROWS="$(getFiles '/etc/gdm' '\.conf$' '/default\.(jpg|png)') - $(getFiles '/etc/gconf' '\.(schemas|xml)$' '/default.*\.(jpg|png)') - $(getFiles '/usr/share/config' 'rc$' 'default.*\.(jpg|png)')" - ;; - - esac - - # Create table. - createTable "$ROWS" "" "" > $FILE - -done diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/manual.tex deleted file mode 100644 index 64edf65..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/manual.tex +++ /dev/null @@ -1,136 +0,0 @@ -\documentclass{article} -\usepackage{longtable} -\usepackage[pdftex]{graphicx} -\usepackage{hyperref} -\hypersetup{pdfauthor={CentOS Documentation SIG},% - pdftitle={GNOME Backgrounds},% - pdfsubject={CentOS Corporate Visual Identity}% - } - -\title{Backgrounds} -\author{CentOS Documentation SIG} - -\begin{document} - -\maketitle - -\begin{abstract} -This article describes GNOME and KDE background images. The first -time a user's session has been loaded, the default background image is -shown on the screen as desktop background. Background image remains -visible in the screen as long as the user's session remains open. - -Copyright \copyright\ 2010\ The CentOS Project. Permission is -granted to copy, distribute and/or modify this document under the -terms of the GNU Free Documentation License, Version 1.2 or any later -version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the -license is included in the section entitled ``GNU Free Documentation -License''. -\end{abstract} - -\tableofcontents - -\section{Workplace} - -\begin{itemize} -\item SVN:trunk/Identity/Themes/\$THEME/Distro/Backgrounds/ -\end{itemize} - -\section{Theme} - -\input{table-theme.tex} - -\section{Design} - -Background design is based on CentOS Default Artistic Motif. - -\begin{itemize} -\item There is no color limitation in this section. -\item There is no translation in these images. -\item There is no version, or textual information in these images. -\end{itemize} - -\section{Rendering} - -\section{Configuration} - -\input{table-config.tex} - -\begin{description} - -\item[Default background]: The -\texttt{desktop\_gnome\_background.schemas} and \texttt{\%gconf-tree.xml} -files control which is the default background image loaded when new -users open their GNOME session for first time and as long as no change -be made in its ``Desktop Background Preferences''. - -Inside \texttt{desktop\_gnome\_background.schemas} file the default -background image is defined in the line 6 of the following piece of -code: - -\begin{verbatim} -... - 1| - 2| /schemas/desktop/gnome/background/picture_filename - 3| /desktop/gnome/background/picture_filename - 4| gnome - 5| string - 6| /usr/share/backgrounds/images/default.png - 7| - 8| Picture Filename - 9| File to use for the background image -10| -11| -... -\end{verbatim} - -Inside \texttt{\%gconf-tree.xml} file, the default background image is -defined in the line 4 of the following piece of code: - -\begin{verbatim} -... -1| -2| -3| -4| /usr/share/backgrounds/images/default.png -5| -6| File to use for the background image -7| -8| -... -\end{verbatim} - -In both files \texttt{desktop\_gnome\_background.schemas} and -\texttt{\%gconf-tree.xml}, the image file name should be the same. - -The \texttt{kdesktoprc} file controls KDE desktop configuration file. -The following lines were taken from that file and show the variables -that control default background on KDE desktop. - -\begin{verbatim} -Wallpaper=/usr/share/backgrounds/images/default.png -WallpaperMode=Scaled -\end{verbatim} - -\end{description} - -\section{Testing} - -\section{Issues} - -\begin{description} - -\item[Image format definition]: Images controlling default desktop -backgrounds are in JPG format. Nevertheless this doesn't match with -the definition in the configuration file -\texttt{desktop-backgrounds-basic.xml} which mention them as PNG format. -This issue makes those images not to be displayed in the GNOME -``Desktop Background Preferences''. - -\end{description} - -% License section -\input{../../../../Licenses/GFDL.tex} - -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-1.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-1.tex deleted file mode 100644 index e3bcbd2..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-1.tex +++ /dev/null @@ -1,26 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/backgrounds/images/default-5\_4.png\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & PNG image data, 2048 x 1536, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/backgrounds/images/default-dual.png\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & PNG image data, 2560 x 1240, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/backgrounds/images/default-dual-wide.png\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & PNG image data, 3271 x 1227, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/backgrounds/images/default.png\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & PNG image data, 2048 x 1536, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/backgrounds/images/default-wide.png\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & PNG image data, 1680 x 1050, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\hline -\multicolumn{2}{l}{\ }\\ -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-2.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-2.tex deleted file mode 100644 index 8a08e7c..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-2.tex +++ /dev/null @@ -1,22 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gnome-background-properties/desktop-backgrounds-basic.xml\\ -\textbf{Package}: & desktop-backgrounds-basic\\ -\textbf{Description}: & XML 1.0 document text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /etc/gconf/schemas/desktop\_gnome\_background.schemas\\ -\textbf{Package}: & libgnome\\ -\textbf{Description}: & UTF-8 Unicode English text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /etc/gconf/gconf.xml.defaults/\%gconf-tree.xml\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & XML 1.0 document text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/config/kdesktoprc\\ -\textbf{Package}: & kdebase\\ -\textbf{Description}: & ASCII text\\ -\multicolumn{2}{l}{\ }\\ -\hline -\multicolumn{2}{l}{\ }\\ -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-config.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-config.tex deleted file mode 100644 index ef96a5c..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-config.tex +++ /dev/null @@ -1,25 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /etc/gdm/custom.conf\\ -\textbf{Package}: & gdm\\ -\textbf{Description}: & ASCII English text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /etc/gconf/gconf.xml.defaults/\%gconf-tree.xml\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & XML 1.0 document text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /etc/gconf/schemas/desktop\_gnome\_background.schemas\\ -\textbf{Package}: & libgnome\\ -\textbf{Description}: & UTF-8 Unicode English text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/config/kdesktoprc\\ -\textbf{Package}: & kdebase\\ -\textbf{Description}: & ASCII text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/config/kdm/backgroundrc\\ -\textbf{Package}: & kdebase\\ -\textbf{Description}: & ASCII text\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-theme.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-theme.tex deleted file mode 100644 index be90910..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-theme.tex +++ /dev/null @@ -1,29 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/backgrounds/images/default-5\_4.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 2048 x 1536, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/backgrounds/images/default-dual.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 2560 x 1240, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/backgrounds/images/default-dual-wide.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 3271 x 1227, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/backgrounds/images/default.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 2048 x 1536, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/backgrounds/images/default-wide.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 1680 x 1050, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/backgrounds/tiles/default\_blue.jpg\\ -\textbf{Package}: & desktop-backgrounds-basic\\ -\textbf{Description}: & JPEG image data, JFIF standard 1.02\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.aux deleted file mode 100644 index 7d62833..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.aux +++ /dev/null @@ -1,47 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} -\gdef \LT@i {\LT@entry - {1}{72.64pt}\LT@entry - {1}{292.61166pt}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{3}{section.3}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Configuration}{3}{section.4}} -\@writefile{toc}{\contentsline {section}{\numberline {5}Rendering}{4}{section.5}} -\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{4}{section.6}} -\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{4}{section.7}} -\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{5}{section.8}} -\newlabel{sec:License-GFDL-0}{{8}{5}{Preamble\relax }{section*.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{5}{subsection.8.1}} -\newlabel{sec:License-GFDL-1}{{8.1}{5}{Applicability And Definitions\relax }{subsection.8.1}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{7}{subsection.8.2}} -\newlabel{sec:License-GFDL-2}{{8.2}{7}{Verbatim Copying\relax }{subsection.8.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{7}{subsection.8.3}} -\newlabel{sec:License-GFDL-3}{{8.3}{7}{Copying In Quantity\relax }{subsection.8.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{8}{subsection.8.4}} -\newlabel{sec:License-GFDL-4}{{8.4}{8}{Modifications\relax }{subsection.8.4}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{9}{subsection.8.5}} -\newlabel{sec:License-GFDL-5}{{8.5}{9}{Combining Documents\relax }{subsection.8.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{10}{subsection.8.6}} -\newlabel{sec:License-GFDL-6}{{8.6}{10}{Collections Of Documents\relax }{subsection.8.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{10}{subsection.8.7}} -\newlabel{sec:License-GFDL-7}{{8.7}{10}{Aggregation With Independent Works\relax }{subsection.8.7}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{11}{subsection.8.8}} -\newlabel{sec:License-GFDL-8}{{8.8}{11}{Translation\relax }{subsection.8.8}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{11}{subsection.8.9}} -\newlabel{sec:License-GFDL-9}{{8.9}{11}{Termination\relax }{subsection.8.9}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{11}{subsection.8.10}} -\newlabel{sec:License-GFDL-10}{{8.10}{11}{Future Revisions OF This License\relax }{subsection.8.10}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{11}{subsection.8.11}} -\newlabel{sec:License-GFDL-11}{{8.11}{11}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.log deleted file mode 100644 index 4d9a7d5..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.log +++ /dev/null @@ -1,287 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size10.clo -File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/tools/longtable.sty -Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) -\LTleft=\skip43 -\LTright=\skip44 -\LTpre=\skip45 -\LTpost=\skip46 -\LTchunksize=\count87 -\LTcapwidth=\dimen103 -\LT@head=\box26 -\LT@firsthead=\box27 -\LT@foot=\box28 -\LT@lastfoot=\box29 -\LT@cols=\count88 -\LT@rows=\count89 -\c@LT@tables=\count90 -\c@LT@chunks=\count91 -\LT@p@ftn=\toks14 -) -(/usr/share/texmf/tex/latex/graphics/graphicx.sty -Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks15 -) -(/usr/share/texmf/tex/latex/graphics/graphics.sty -Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/trig.sty -Package: trig 1999/03/16 v1.09 sin cos tan (DPC) -) -(/usr/share/texmf/tex/latex/graphics/graphics.cfg -File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive -) -Package graphics Info: Driver file: pdftex.def on input line 80. - -(/usr/share/texmf/tex/latex/graphics/pdftex.def -File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex -\Gread@gobject=\count92 -)) -\Gin@req@height=\dimen104 -\Gin@req@width=\dimen105 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX -\@linkdim=\dimen106 -\Hy@linkcounter=\count93 -\Hy@pagecounter=\count94 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count95 -\Field@Width=\dimen107 -\Fld@charsize=\dimen108 -\Choice@toks=\toks16 -\Field@toks=\toks17 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count96 -\c@Hfootnote=\count97 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count98 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. - -(/usr/share/texmf/tex/context/base/supp-pdf.tex -(/usr/share/texmf/tex/context/base/supp-mis.tex -loading : Context Support Macros / Miscellaneous (2004.10.26) -\protectiondepth=\count99 -\scratchcounter=\count100 -\scratchtoks=\toks18 -\scratchdimen=\dimen109 -\scratchskip=\skip47 -\scratchmuskip=\muskip11 -\scratchbox=\box30 -\scratchread=\read1 -\scratchwrite=\write4 -\zeropoint=\dimen110 -\onepoint=\dimen111 -\onebasepoint=\dimen112 -\minusone=\count101 -\thousandpoint=\dimen113 -\onerealpoint=\dimen114 -\emptytoks=\toks19 -\nextbox=\box31 -\nextdepth=\dimen115 -\everyline=\toks20 -\!!counta=\count102 -\!!countb=\count103 -\recursecounter=\count104 -) -loading : Context Support Macros / PDF (2004.03.26) -\nofMPsegments=\count105 -\nofMParguments=\count106 -\MPscratchCnt=\count107 -\MPscratchDim=\dimen116 -\MPnumerator=\count108 -\everyMPtoPDFconversion=\toks21 -) -Package hyperref Info: Link coloring OFF on input line 13. - (/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count109 -) -LaTeX Info: Redefining \ref on input line 13. -LaTeX Info: Redefining \pageref on input line 13. - (./Manual.out) -(./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 16. -LaTeX Font Info: Try loading font information for OMS+cmr on input line 25. - (/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 25. - (./Manual.toc -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 9. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 9. - -[1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) -\tf@toc=\write5 -\openout5 = `Manual.toc'. - -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 39. - -(./table-theme.tex -Overfull \hbox (20.25166pt too wide) in alignment at lines 1--23 - [] [] - [] - - -Underfull \vbox (badness 10000) detected at line 23 - [] - - -Overfull \hbox (20.25166pt too wide) in alignment at lines 23--43 - [] [] - [] - - -Overfull \hbox (20.25166pt too wide) in alignment at lines 43--45 - [] [] - [] - -[2]) -Overfull \hbox (31.52852pt too wide) in paragraph at lines 55--59 -\OT1/cmr/m/n/10 col-lects all in-for-ma-tion, groups it and stores it un-der tg -z/$VERSION/$RESOLUTION/ - [] - - -Overfull \hbox (6.83415pt too wide) in paragraph at lines 70--71 -[]\OT1/cmr/m/n/10 gnome-help file:///usr/share/gnome/help/gdm/C/gdm.xml#themema -nual - [] - - -Underfull \hbox (badness 10000) in paragraph at lines 81--82 - - [] - -[3] (../../../../../Licenses/GFDL.tex -Underfull \hbox (badness 10000) in paragraph at lines 5--14 - - [] - -[4] [5] -Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 -\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple - HTML, PostScript - [] - -[6] [7] [8] [9] [10] [11]) [12] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 2746 strings out of 94500 - 36564 string characters out of 1176766 - 90637 words of memory out of 1000000 - 5869 multiletter control sequences out of 10000+50000 - 9961 words of font info for 35 fonts, out of 500000 for 2000 - 580 hyphenation exceptions out of 1000 - 27i,8n,36p,222b,222s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 207 PDF objects out of 300000 - 36 named destinations out of 131072 - 169 words of extra memory for PDF output out of 65536 - -Output written on Manual.pdf (12 pages, 149237 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.out deleted file mode 100644 index 2f29f36..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.out +++ /dev/null @@ -1,19 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Workplace}{} -\BOOKMARK [1][-]{section.2}{Theme}{} -\BOOKMARK [1][-]{section.3}{Design}{} -\BOOKMARK [1][-]{section.4}{Configuration}{} -\BOOKMARK [1][-]{section.5}{Rendering}{} -\BOOKMARK [1][-]{section.6}{Testing}{} -\BOOKMARK [1][-]{section.7}{Issues}{} -\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} -\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} -\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} -\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} -\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} -\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} -\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} -\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} -\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} -\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.pdf deleted file mode 100644 index ceb279f..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.toc deleted file mode 100644 index b0c70e5..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.toc +++ /dev/null @@ -1,19 +0,0 @@ -\contentsline {section}{\numberline {1}Workplace}{2}{section.1} -\contentsline {section}{\numberline {2}Theme}{2}{section.2} -\contentsline {section}{\numberline {3}Design}{3}{section.3} -\contentsline {section}{\numberline {4}Configuration}{3}{section.4} -\contentsline {section}{\numberline {5}Rendering}{4}{section.5} -\contentsline {section}{\numberline {6}Testing}{4}{section.6} -\contentsline {section}{\numberline {7}Issues}{4}{section.7} -\contentsline {section}{\numberline {8}GNU Free Documentation License}{5}{section.8} -\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{5}{subsection.8.1} -\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{7}{subsection.8.2} -\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{7}{subsection.8.3} -\contentsline {subsection}{\numberline {8.4}Modifications}{8}{subsection.8.4} -\contentsline {subsection}{\numberline {8.5}Combining Documents}{9}{subsection.8.5} -\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{10}{subsection.8.6} -\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{10}{subsection.8.7} -\contentsline {subsection}{\numberline {8.8}Translation}{11}{subsection.8.8} -\contentsline {subsection}{\numberline {8.9}Termination}{11}{subsection.8.9} -\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{11}{subsection.8.10} -\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{11}{subsection.8.11} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/build.sh b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/build.sh deleted file mode 100755 index 2e9187b..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/build.sh +++ /dev/null @@ -1,55 +0,0 @@ -#!/bin/bash -# -# Build GDM tables for LaTeX documents. -# -# Copyright (C) 2009 Alain Reguera Delgado -# -# 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:$ -#-------------------------------------- - -# Load functions. -. ~/artwork/trunk/Scripts/Bash/loadFunctions. - -# Define the names of your tables. -FILES="table-theme.tex - table-config.tex" - -for FILE in $FILES;do - - # Let know what table we are creating. - echo $FILE - - case $FILE in - - table-theme.tex ) - # Create table holding theme files. - ROWS="$(getFiles '/usr/share/gdm/themes' '/Modern/.*')" - ;; - - table-config.tex ) - # Create table holding configuration files. - ROWS="$(getFiles '/{etc,usr/share}/gdm' '\.conf')" - ;; - - esac - - # Create table. - createTable "$ROWS" "" "" > $FILE - -done diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/manual.tex deleted file mode 100644 index 7e7f4b4..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/manual.tex +++ /dev/null @@ -1,150 +0,0 @@ -\documentclass{article} -\usepackage{longtable} -\usepackage[pdftex]{graphicx} -\usepackage{hyperref} -\hypersetup{pdfauthor={CentOS Documentation SIG},% - pdftitle={GNOME Display Manager (GDM)},% - pdfsubject={CentOS Corporate Visual Identity}% - } - -\title{GNOME Display Manager (GDM)} -\author{CentOS Documentation SIG} - -\begin{document} - -\maketitle - -\begin{abstract} -This article describes the GDM Visual Style for CentOS Distribution. -GDM is the first choice defined as CentOS Display Manager (DM). If -users leave their computers on all the time and don't share their -system, they won't see this as often as users who share a desktop -system with other users on the system or laptop users who reboot and -login more frequently. - -Copyright \copyright\ 2010\ The CentOS Project. Permission is -granted to copy, distribute and/or modify this document under the -terms of the GNU Free Documentation License, Version 1.2 or any later -version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the -license is included in the section entitled ``GNU Free Documentation -License''. -\end{abstract} - -\tableofcontents - -\section{Workplace} - -\begin{itemize} -\item SVN:trunk/Identity/Themes/\$THEME/Distro/BootUp/GDM/ -\item SVN:trunk/Translations/Identity/Themes/Distro/BootUp/GDM/ -\item SVN:trunk/Scripts/Identity/Themes/Distro/BootUp/GDM/ -\end{itemize} - -\section{Theme} - -\input{table-theme.tex} - -\section{Design} - -The centos-release.png and screenshot.png images are rendered for each -major release of CentOS. This task is done using the rendering script -(render.sh) available in the workplace. This script creates the -appropriate PNG images under img/\$VERSION/ directory. - -The background.png image is taken from Backgrounds section. This task -is done using the building script(build.sh) available in the -workplace. This script collects all information, groups it and stores -it under tgz/\$VERSION/\$RESOLUTION/ with the form \$THEME.tar.gz. - -Whith the building script you can create GDM themes for specific -CentOS major releases, and inside each major release for specific -screen resolutions. - -More information about GDM theming is available in the \emph{GNOME -Display Manager Reference Manual}. This guide is available online and -inside your system's help. As shortcut to get that help, you can run -the following command: - -\begin{itemize} -\item gnome-help file:///usr/share/gnome/help/gdm/C/gdm.xml\#thememanual -\end{itemize} - -\section{Configuration} - -\begin{description} - -\item[GraphicalTheme]: The graphical theme that the Themed Greeter -should use. It should refer to a directory in the theme directory set -by \emph{GraphicalThemeDir}. - -\texttt{GraphicalTheme=\$THEME}\\ - -\item[GraphicalThemeDir]: The directory where themes for the Themed -Greeter are installed. - -\texttt{GraphicalThemeDir=/usr/share/gdm/themes/} - -\item[BackgroundColor]: The Standard greeter (gdmlogin) background -color. If the BackgroundType is 2, use this color in the background of -the greeter. Also use it as the back of transparent images set on the -background and if the BackgroundRemoteOnlyColor is set and this is a -remote display. This only affects the GTK+ Greeter. - -\texttt{BackgroundColor=\#204C8D} - -\item[GraphicalThemeColor]: Use this color in the background of the -Themed Greeter. This only affects the Themed Greeter. - -\texttt{GraphicalThemeColor=\#000000} - -\end{description} - -More information about GDM and its configuration can be found in its -reference guide. As shortcut to get that help, you can run the -following command: - -\begin{itemize} -\item gnome-help file:///usr/share/gnome/help/gdm/C/gdm.xml\#index -\end{itemize} - -\section{Rendering} -\section{Testing} -\section{Issues} - -\begin{description} - -\item[Transition from Greeter to Desktop]: This seems to be available -when using the variable \emph{BackgroundImage} in GTK+ Greeter only. -In Themed Greeter the best we have is the variable -\emph{GraphicalThemedColor} to specify the background color of the -transition. - -\item[Different resolutions]: Designing of GDM theme needs to be -expandable through different screen resolutions. By default, GDM theme -uses a background image of 2048x1536 pixels. When screen resolution -changes the predifined behaviour is to scale this image to fit the -current display resolution. If the screen resolution is higher, or -differs in ratio (for example when it a wide screens) the design of -GDM them could loose quality or look different from the original one. - -As a workaround, if GDM theme looks narrow or deformed to you, use the -building script to create the GDM theme in your specific screen -resolution. - -\item[GDM theme installation]: Use the login screen administrator -(gdmsetup). This action requires you to have \emph{root} privileges. - -\item[Default Display Manager]: By default GDM is the first display -manager choice\footnote{See the file /etc/X11/prefdm.}. If you -changed this and want to go back then, run the following command (as -\emph{root}) and reboot: - -\texttt{echo "DISPLAYMANAGER=GNOME" > /etc/sysconfig/desktop} - -\end{description} - -% License section -\input{../../../../../Licenses/GFDL.tex} - -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-1.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-1.tex deleted file mode 100644 index a0c3022..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-1.tex +++ /dev/null @@ -1,45 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/background.png\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & PNG image data, 1024 x 768, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/centos-release.png\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & PNG image data, 181 x 48, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/centos-symbol.png\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & PNG image data, 48 x 48, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/GdmGreeterTheme.desktop\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & UTF-8 Unicode English text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-language.png\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-reboot.png\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-session.png\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-shutdown.png\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/Modern.xml\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & XML 1.0 document text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/screenshot.png\\ -\textbf{Package}: & \textbf{None!}\\ -\textbf{Description}: & PNG image data, 200 x 150, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-config.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-config.tex deleted file mode 100644 index a42f07e..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-config.tex +++ /dev/null @@ -1,5 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-theme.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-theme.tex deleted file mode 100644 index f0212d5..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-theme.tex +++ /dev/null @@ -1,45 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/background.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 1024 x 768, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/centos-release.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 181 x 48, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/centos-symbol.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 48 x 48, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/GdmGreeterTheme.desktop\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & UTF-8 Unicode English text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-language.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-reboot.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-session.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-shutdown.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/Modern.xml\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & XML 1.0 document text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/gdm/themes/Modern/screenshot.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 200 x 150, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.aux deleted file mode 100644 index d09c94b..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.aux +++ /dev/null @@ -1,47 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\gdef \LT@i {\LT@entry - {1}{72.64pt}\LT@entry - {1}{419.19533pt}} -\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{2}{section.3}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Configuration}{3}{section.4}} -\@writefile{toc}{\contentsline {section}{\numberline {5}Rendering}{3}{section.5}} -\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{3}{section.6}} -\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{3}{section.7}} -\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8}} -\newlabel{sec:License-GFDL-0}{{8}{3}{Preamble\relax }{section*.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{4}{subsection.8.1}} -\newlabel{sec:License-GFDL-1}{{8.1}{4}{Applicability And Definitions\relax }{subsection.8.1}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{5}{subsection.8.2}} -\newlabel{sec:License-GFDL-2}{{8.2}{5}{Verbatim Copying\relax }{subsection.8.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{6}{subsection.8.3}} -\newlabel{sec:License-GFDL-3}{{8.3}{6}{Copying In Quantity\relax }{subsection.8.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{6}{subsection.8.4}} -\newlabel{sec:License-GFDL-4}{{8.4}{6}{Modifications\relax }{subsection.8.4}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5}} -\newlabel{sec:License-GFDL-5}{{8.5}{8}{Combining Documents\relax }{subsection.8.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{9}{subsection.8.6}} -\newlabel{sec:License-GFDL-6}{{8.6}{9}{Collections Of Documents\relax }{subsection.8.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{9}{subsection.8.7}} -\newlabel{sec:License-GFDL-7}{{8.7}{9}{Aggregation With Independent Works\relax }{subsection.8.7}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{9}{subsection.8.8}} -\newlabel{sec:License-GFDL-8}{{8.8}{9}{Translation\relax }{subsection.8.8}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{10}{subsection.8.9}} -\newlabel{sec:License-GFDL-9}{{8.9}{10}{Termination\relax }{subsection.8.9}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{10}{subsection.8.10}} -\newlabel{sec:License-GFDL-10}{{8.10}{10}{Future Revisions OF This License\relax }{subsection.8.10}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11}} -\newlabel{sec:License-GFDL-11}{{8.11}{10}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.log deleted file mode 100644 index 4faaf90..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.log +++ /dev/null @@ -1,267 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size10.clo -File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/tools/longtable.sty -Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) -\LTleft=\skip43 -\LTright=\skip44 -\LTpre=\skip45 -\LTpost=\skip46 -\LTchunksize=\count87 -\LTcapwidth=\dimen103 -\LT@head=\box26 -\LT@firsthead=\box27 -\LT@foot=\box28 -\LT@lastfoot=\box29 -\LT@cols=\count88 -\LT@rows=\count89 -\c@LT@tables=\count90 -\c@LT@chunks=\count91 -\LT@p@ftn=\toks14 -) -(/usr/share/texmf/tex/latex/graphics/graphicx.sty -Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks15 -) -(/usr/share/texmf/tex/latex/graphics/graphics.sty -Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/trig.sty -Package: trig 1999/03/16 v1.09 sin cos tan (DPC) -) -(/usr/share/texmf/tex/latex/graphics/graphics.cfg -File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive -) -Package graphics Info: Driver file: pdftex.def on input line 80. - -(/usr/share/texmf/tex/latex/graphics/pdftex.def -File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex -\Gread@gobject=\count92 -)) -\Gin@req@height=\dimen104 -\Gin@req@width=\dimen105 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX -\@linkdim=\dimen106 -\Hy@linkcounter=\count93 -\Hy@pagecounter=\count94 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count95 -\Field@Width=\dimen107 -\Fld@charsize=\dimen108 -\Choice@toks=\toks16 -\Field@toks=\toks17 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count96 -\c@Hfootnote=\count97 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count98 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. - -(/usr/share/texmf/tex/context/base/supp-pdf.tex -(/usr/share/texmf/tex/context/base/supp-mis.tex -loading : Context Support Macros / Miscellaneous (2004.10.26) -\protectiondepth=\count99 -\scratchcounter=\count100 -\scratchtoks=\toks18 -\scratchdimen=\dimen109 -\scratchskip=\skip47 -\scratchmuskip=\muskip11 -\scratchbox=\box30 -\scratchread=\read1 -\scratchwrite=\write4 -\zeropoint=\dimen110 -\onepoint=\dimen111 -\onebasepoint=\dimen112 -\minusone=\count101 -\thousandpoint=\dimen113 -\onerealpoint=\dimen114 -\emptytoks=\toks19 -\nextbox=\box31 -\nextdepth=\dimen115 -\everyline=\toks20 -\!!counta=\count102 -\!!countb=\count103 -\recursecounter=\count104 -) -loading : Context Support Macros / PDF (2004.03.26) -\nofMPsegments=\count105 -\nofMParguments=\count106 -\MPscratchCnt=\count107 -\MPscratchDim=\dimen116 -\MPnumerator=\count108 -\everyMPtoPDFconversion=\toks21 -) -Package hyperref Info: Link coloring OFF on input line 13. - (/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count109 -) -LaTeX Info: Redefining \ref on input line 13. -LaTeX Info: Redefining \pageref on input line 13. - (./Manual.out) -(./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 16. -LaTeX Font Info: Try loading font information for OMS+cmr on input line 22. - (/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 22. - (./Manual.toc -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 9. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 9. - -[1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) -\tf@toc=\write5 -\openout5 = `Manual.toc'. - -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 36. - -(./table-theme.tex -Overfull \hbox (146.83533pt too wide) in alignment at lines 1--9 - [] [] - [] - - -Underfull \vbox (badness 10000) detected at line 9 - [] - -) -Overfull \hbox (10.12134pt too wide) in paragraph at lines 82--84 -\OT1/cmr/m/n/10 The fol-low-ing is-sues were seen on a video card \OT1/cmr/m/it -/10 Tri-dent Mi-crosysmtes Cy-berBlade/i1 - [] - -[2] (../../../../../Licenses/GFDL.tex -Underfull \hbox (badness 10000) in paragraph at lines 5--14 - - [] - -[3] [4] -Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 -\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple - HTML, PostScript - [] - -[5] [6] [7] [8] [9]) [10] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 2750 strings out of 94500 - 36602 string characters out of 1176766 - 89642 words of memory out of 1000000 - 5871 multiletter control sequences out of 10000+50000 - 10666 words of font info for 37 fonts, out of 500000 for 2000 - 580 hyphenation exceptions out of 1000 - 27i,8n,36p,222b,214s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 204 PDF objects out of 300000 - 36 named destinations out of 131072 - 169 words of extra memory for PDF output out of 65536 - -Output written on Manual.pdf (10 pages, 143812 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.out deleted file mode 100644 index 2f29f36..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.out +++ /dev/null @@ -1,19 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Workplace}{} -\BOOKMARK [1][-]{section.2}{Theme}{} -\BOOKMARK [1][-]{section.3}{Design}{} -\BOOKMARK [1][-]{section.4}{Configuration}{} -\BOOKMARK [1][-]{section.5}{Rendering}{} -\BOOKMARK [1][-]{section.6}{Testing}{} -\BOOKMARK [1][-]{section.7}{Issues}{} -\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} -\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} -\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} -\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} -\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} -\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} -\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} -\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} -\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} -\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.pdf deleted file mode 100644 index 5173294..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.toc deleted file mode 100644 index 2d89c1f..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.toc +++ /dev/null @@ -1,19 +0,0 @@ -\contentsline {section}{\numberline {1}Workplace}{2}{section.1} -\contentsline {section}{\numberline {2}Theme}{2}{section.2} -\contentsline {section}{\numberline {3}Design}{2}{section.3} -\contentsline {section}{\numberline {4}Configuration}{3}{section.4} -\contentsline {section}{\numberline {5}Rendering}{3}{section.5} -\contentsline {section}{\numberline {6}Testing}{3}{section.6} -\contentsline {section}{\numberline {7}Issues}{3}{section.7} -\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8} -\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{4}{subsection.8.1} -\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{5}{subsection.8.2} -\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{6}{subsection.8.3} -\contentsline {subsection}{\numberline {8.4}Modifications}{6}{subsection.8.4} -\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5} -\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{9}{subsection.8.6} -\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{9}{subsection.8.7} -\contentsline {subsection}{\numberline {8.8}Translation}{9}{subsection.8.8} -\contentsline {subsection}{\numberline {8.9}Termination}{10}{subsection.8.9} -\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{10}{subsection.8.10} -\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/build.sh b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/build.sh deleted file mode 100755 index c810485..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/build.sh +++ /dev/null @@ -1,56 +0,0 @@ -#!/bin/bash -# -# Build GRUB tables for LaTeX documents. -# -# Copyright (C) 2009 Alain Reguera Delgado -# -# 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:$ -#-------------------------------------- - -# Load functions. -. ~/artwork/trunk/Scripts/Bash/loadFunctions.sh - -# Define the names of your tables. -FILES="table-theme.tex - table-config.tex" - -for FILE in $FILES;do - - # Let know which table we are creating. - echo $FILE - - # Define what to do with each table you define on FILES. - case $FILE in - - table-theme.tex ) - # Create table holding theme files. - ROWS="$(getFiles '/boot/grub' 'splash.xpm.gz')" - ;; - - table-config.tex ) - # Create table holding configuration files. - ROWS="$(getFiles '/{boot/grub,etc}' '(\.lst|grub|\.conf)$')" - ;; - - esac - - # Create table. - createTable "$ROWS" "" "" > $FILE - -done diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/manual.tex deleted file mode 100644 index 9efcae8..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/manual.tex +++ /dev/null @@ -1,109 +0,0 @@ -\documentclass{article} -\usepackage{longtable} -\usepackage[pdftex]{graphicx} -\usepackage{hyperref} -\hypersetup{pdfauthor={CentOS Documentation SIG},% - pdftitle={Grand Unified Bootloader (GRUB)},% - pdfsubject={CentOS Corporate Visual Identity}% - } - -\title{Grand Unified Bootloader (GRUB)} -\author{CentOS Documentation SIG} - -\begin{document} - -\maketitle - -\begin{abstract} -This article describes GRUB Visual Style for CentOS Distribution. -This screen is where the selection of which kernel to run and other -boot-time options, are made. It is seen every time the computer boots. - -Copyright \copyright\ 2010\ The CentOS Project. Permission is -granted to copy, distribute and/or modify this document under the -terms of the GNU Free Documentation License, Version 1.2 or any later -version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the -license is included in the section entitled ``GNU Free Documentation -License''. -\end{abstract} - -\tableofcontents - -\section{Workplace} - -\begin{itemize} -\item SVN:trunk/Identity/Themes/\$THEME/Distro/BootUp/GRUB/ -\item SVN:trunk/Translations/Identity/Themes/Distro/BootUp/GRUB/ -\item SVN:trunk/Scripts/Identity/Themes/Distro/BootUp/GRUB/ -\end{itemize} - -\section{Theme} - -\input{table-theme.tex} - -\section{Design} - -Initially, \emph{splash.xpm.gz} is a PNG image (splash.png) which is -converted to xpm.gz. \emph{splash.png} image is rendered for each -major release of CentOS distribution. Each image is based in the same -Artistic Motif and has the following components: - -\begin{enumerate} -\item The CentOS Release Brand. -\item The CentOS Default Artistic Motif. -\end{enumerate} - -Image rendering is done using the rendering script (\emph{render.sh}) -available in the workplace of this section. This script creates -the appropriate PNG images under \emph{img/\$VERSION/} -directory. - -After image rendering, each \emph{img/\$VERSION/splash.png} image -should be indexed to 14 colors. This can be done using an image -manipulation tool like GIMP, or ImageMagick. This color reduction -could bring some noise to your design. If that is the case, you need -to retouch your design in a 14 colors basis. - -The final step is to convert the 14 colors indexed \emph{splash.png} -image into \emph{splash.xpm.gz}. To do so, use the command -\emph{convert2xpm.sh} provided in the workplace. This command -explores the \emph{img/\$VERSION/} directories and -converts\footnote{\emph{convert splash.png splash.xpm \&\& gzip -splash.xpm}} each \emph{splash.png} image indexed to 14 colors to its -\emph{.xpm.gz} equivalent. The converted images are saved under -\emph{xpm/\$VERSION/} directories. - -\section{Configuration} -\section{Rendering} -\section{Testing} -\section{Issues} - -The following issues were seen on a video card \emph{Trident -Microsysmtes CyberBlade/i1 (cyblafb)}: - -\begin{description} - -\item[Different colors]: As more different colors you have on your -design, more are the possibilities of increasing the amount of noise -in your design after indexing to 14 colors. For example, if you -include the actual CentOS symbol in this image, it ocupies 3 colors -(for the orange, green, violet) which are completely different and -non-reusable in the blue toned background image. - -\item [CentOS Symbol]: If the CentOS symbol is included in -this image, colors used in the symbol after indexing the image -are not the defaults colors defined as CentOS Symbol Colors. - -To workaround this, in first place, I used a variant of CentOS symbol -without background colors, just the white borders. Later, I desided to -remove it completely because that symbol could confuse people about -which is the CentOS default symbol (see ``The CentOS Brand'' manual). -Finally, I ended up using just the plain word CentOS to brand the -GRUB. - -\end{description} - -% License section -\input{../../../../../Licenses/GFDL.tex} -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-1.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-1.tex deleted file mode 100644 index 6c1e19a..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-1.tex +++ /dev/null @@ -1,10 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /boot/grub/splash.xpm.gz\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & gzip compressed data, was "splash.xpm".\\ -\multicolumn{2}{l}{\ }\\ -\hline -\multicolumn{2}{l}{\ }\\ -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-config.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-config.tex deleted file mode 100644 index a42f07e..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-config.tex +++ /dev/null @@ -1,5 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-theme.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-theme.tex deleted file mode 100644 index e6bf302..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-theme.tex +++ /dev/null @@ -1,9 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /boot/grub/splash.xpm.gz\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & gzip compressed data, was "splash.xpm", from Unix, last modified: Sat Jan 16 01:17:29 2010\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.aux deleted file mode 100644 index e04ca12..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.aux +++ /dev/null @@ -1,47 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\gdef \LT@i {\LT@entry - {1}{0.0pt}\LT@entry - {1}{124.66689pt}} -\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{2}{section.3}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Configuration}{3}{section.4}} -\@writefile{toc}{\contentsline {section}{\numberline {5}Rendering}{3}{section.5}} -\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{3}{section.6}} -\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{3}{section.7}} -\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8}} -\newlabel{sec:License-GFDL-0}{{8}{3}{Preamble\relax }{section*.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{3}{subsection.8.1}} -\newlabel{sec:License-GFDL-1}{{8.1}{3}{Applicability And Definitions\relax }{subsection.8.1}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{5}{subsection.8.2}} -\newlabel{sec:License-GFDL-2}{{8.2}{5}{Verbatim Copying\relax }{subsection.8.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{5}{subsection.8.3}} -\newlabel{sec:License-GFDL-3}{{8.3}{5}{Copying In Quantity\relax }{subsection.8.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{6}{subsection.8.4}} -\newlabel{sec:License-GFDL-4}{{8.4}{6}{Modifications\relax }{subsection.8.4}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5}} -\newlabel{sec:License-GFDL-5}{{8.5}{8}{Combining Documents\relax }{subsection.8.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{8}{subsection.8.6}} -\newlabel{sec:License-GFDL-6}{{8.6}{8}{Collections Of Documents\relax }{subsection.8.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{8}{subsection.8.7}} -\newlabel{sec:License-GFDL-7}{{8.7}{8}{Aggregation With Independent Works\relax }{subsection.8.7}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{9}{subsection.8.8}} -\newlabel{sec:License-GFDL-8}{{8.8}{9}{Translation\relax }{subsection.8.8}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{9}{subsection.8.9}} -\newlabel{sec:License-GFDL-9}{{8.9}{9}{Termination\relax }{subsection.8.9}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{9}{subsection.8.10}} -\newlabel{sec:License-GFDL-10}{{8.10}{9}{Future Revisions OF This License\relax }{subsection.8.10}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11}} -\newlabel{sec:License-GFDL-11}{{8.11}{10}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.log deleted file mode 100644 index 05d0467..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.log +++ /dev/null @@ -1,256 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size10.clo -File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/tools/longtable.sty -Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) -\LTleft=\skip43 -\LTright=\skip44 -\LTpre=\skip45 -\LTpost=\skip46 -\LTchunksize=\count87 -\LTcapwidth=\dimen103 -\LT@head=\box26 -\LT@firsthead=\box27 -\LT@foot=\box28 -\LT@lastfoot=\box29 -\LT@cols=\count88 -\LT@rows=\count89 -\c@LT@tables=\count90 -\c@LT@chunks=\count91 -\LT@p@ftn=\toks14 -) -(/usr/share/texmf/tex/latex/graphics/graphicx.sty -Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks15 -) -(/usr/share/texmf/tex/latex/graphics/graphics.sty -Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/trig.sty -Package: trig 1999/03/16 v1.09 sin cos tan (DPC) -) -(/usr/share/texmf/tex/latex/graphics/graphics.cfg -File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive -) -Package graphics Info: Driver file: pdftex.def on input line 80. - -(/usr/share/texmf/tex/latex/graphics/pdftex.def -File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex -\Gread@gobject=\count92 -)) -\Gin@req@height=\dimen104 -\Gin@req@width=\dimen105 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX -\@linkdim=\dimen106 -\Hy@linkcounter=\count93 -\Hy@pagecounter=\count94 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count95 -\Field@Width=\dimen107 -\Fld@charsize=\dimen108 -\Choice@toks=\toks16 -\Field@toks=\toks17 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count96 -\c@Hfootnote=\count97 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count98 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. - -(/usr/share/texmf/tex/context/base/supp-pdf.tex -(/usr/share/texmf/tex/context/base/supp-mis.tex -loading : Context Support Macros / Miscellaneous (2004.10.26) -\protectiondepth=\count99 -\scratchcounter=\count100 -\scratchtoks=\toks18 -\scratchdimen=\dimen109 -\scratchskip=\skip47 -\scratchmuskip=\muskip11 -\scratchbox=\box30 -\scratchread=\read1 -\scratchwrite=\write4 -\zeropoint=\dimen110 -\onepoint=\dimen111 -\onebasepoint=\dimen112 -\minusone=\count101 -\thousandpoint=\dimen113 -\onerealpoint=\dimen114 -\emptytoks=\toks19 -\nextbox=\box31 -\nextdepth=\dimen115 -\everyline=\toks20 -\!!counta=\count102 -\!!countb=\count103 -\recursecounter=\count104 -) -loading : Context Support Macros / PDF (2004.03.26) -\nofMPsegments=\count105 -\nofMParguments=\count106 -\MPscratchCnt=\count107 -\MPscratchDim=\dimen116 -\MPnumerator=\count108 -\everyMPtoPDFconversion=\toks21 -) -Package hyperref Info: Link coloring OFF on input line 13. - (/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count109 -) -LaTeX Info: Redefining \ref on input line 13. -LaTeX Info: Redefining \pageref on input line 13. - (./Manual.out) -(./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <9> on input line 21. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 21. -LaTeX Font Info: Try loading font information for OMS+cmr on input line 26. - (/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 26. - (./Manual.toc -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 9. - -[1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) -\tf@toc=\write5 -\openout5 = `Manual.toc'. - -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 39. - -(./table-theme.tex -Underfull \vbox (badness 10000) detected at line 6 - [] - -) (../../../../../Licenses/GFDL.tex -Underfull \hbox (badness 10000) in paragraph at lines 5--14 - - [] - -[2] [3] -Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 -\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple - HTML, PostScript - [] - -[4] [5] [6] [7] [8] [9]) [10] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 2750 strings out of 94500 - 36599 string characters out of 1176766 - 88600 words of memory out of 1000000 - 5871 multiletter control sequences out of 10000+50000 - 10141 words of font info for 36 fonts, out of 500000 for 2000 - 580 hyphenation exceptions out of 1000 - 27i,8n,36p,222b,259s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 199 PDF objects out of 300000 - 37 named destinations out of 131072 - 169 words of extra memory for PDF output out of 65536 - -Output written on Manual.pdf (10 pages, 130753 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.out deleted file mode 100644 index 2f29f36..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.out +++ /dev/null @@ -1,19 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Workplace}{} -\BOOKMARK [1][-]{section.2}{Theme}{} -\BOOKMARK [1][-]{section.3}{Design}{} -\BOOKMARK [1][-]{section.4}{Configuration}{} -\BOOKMARK [1][-]{section.5}{Rendering}{} -\BOOKMARK [1][-]{section.6}{Testing}{} -\BOOKMARK [1][-]{section.7}{Issues}{} -\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} -\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} -\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} -\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} -\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} -\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} -\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} -\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} -\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} -\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.pdf deleted file mode 100644 index 917b0e4..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.toc deleted file mode 100644 index 100ecb7..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.toc +++ /dev/null @@ -1,19 +0,0 @@ -\contentsline {section}{\numberline {1}Workplace}{2}{section.1} -\contentsline {section}{\numberline {2}Theme}{2}{section.2} -\contentsline {section}{\numberline {3}Design}{2}{section.3} -\contentsline {section}{\numberline {4}Configuration}{3}{section.4} -\contentsline {section}{\numberline {5}Rendering}{3}{section.5} -\contentsline {section}{\numberline {6}Testing}{3}{section.6} -\contentsline {section}{\numberline {7}Issues}{3}{section.7} -\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8} -\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{3}{subsection.8.1} -\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{5}{subsection.8.2} -\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{5}{subsection.8.3} -\contentsline {subsection}{\numberline {8.4}Modifications}{6}{subsection.8.4} -\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5} -\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{8}{subsection.8.6} -\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{8}{subsection.8.7} -\contentsline {subsection}{\numberline {8.8}Translation}{9}{subsection.8.8} -\contentsline {subsection}{\numberline {8.9}Termination}{9}{subsection.8.9} -\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{9}{subsection.8.10} -\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/build.sh b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/build.sh deleted file mode 100755 index 66fb822..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/build.sh +++ /dev/null @@ -1,55 +0,0 @@ -#!/bin/bash -# -# Build GSplash tables for LaTeX document. -# -# Copyright (C) 2009 Alain Reguera Delgado -# -# 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:$ -#-------------------------------------- - -# Load functions. -. ~/artwork/trunk/Scripts/Bash/loadFunctions. - -# Define the names of your tables. -FILES="table-theme.tex - table-config.tex" - -for FILE in $FILES;do - - # Let know what table we are creating. - echo $FILE - - case $FILE in - - table-theme.tex ) - # Create table holding theme files. - ROWS="$(getFiles '/usr/share/pixmaps' 'gnome-splash')" - ;; - - table-config.tex ) - # Create table holding configuration files. - ROWS="$(getFiles '/etc/gconf' 'gnome-splash')" - ;; - - esac - - # Create table. - createTable "$ROWS" "" "" > $FILE - -done diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/manual.tex deleted file mode 100644 index 7287877..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/manual.tex +++ /dev/null @@ -1,74 +0,0 @@ -\documentclass{article} -\usepackage{longtable} -\usepackage[pdftex]{graphicx} -\usepackage{hyperref} -\hypersetup{pdfauthor={CentOS Documentation SIG},% - pdftitle={GNOME Splash)},% - pdfsubject={CentOS Corporate Visual Identity}% - } - -\title{GNOME Splash} -\author{CentOS Documentation SIG} - -\begin{document} - -\maketitle - -\begin{abstract} - -This article describes the GNOME Splash Visual Style for CentOS -Distribution. By default this image is disabled to make GNOME session -load faster. If you enable it,\footnote{To enable GNOME Splash image -go to: \texttt{System > Preferences > More Preferences > Sessions} and -check the item \texttt{Show splash screen on login}.} this image is -displayed after login screen, and while GNOME session is being loaded. - -Copyright \copyright\ 2010\ The CentOS Project. Permission is -granted to copy, distribute and/or modify this document under the -terms of the GNU Free Documentation License, Version 1.2 or any later -version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the -license is included in the section entitled ``GNU Free Documentation -License''. -\end{abstract} - -\tableofcontents - -\section{Workplace} -\begin{itemize} -\item SVN:trunk/Identity/Themes/\$THEME/Distro/BootUp/GSplash/ -\item SVN:trunk/Translations/Identity/Themes/Distro/BootUp/GSplash/ -\item SVN:trunk/Scripts/Identity/Themes/Distro/BootUp/GSplash/ -\end{itemize} - -\section{Theme} - -\input{table-theme.tex} - -\section{Design} - -GNOME Splash is rendered for each major release of CentOS -Distribution. Each image is based in the same Artistic Motif and has -the following components: - -\begin{enumerate} -\item The CentOS Symbol. -\item The CentOS Release Brand. -\item The CentOS Default Artistic Motif. -\end{enumerate} - -Image rendering is done using the script render.sh available in the -workplace. This script creates the appropriate PNG images under -img/\$VERSION/. - -There is no color limitation in this section. - -\section{Configuration} -\section{Rendering} -\section{Testing} -\section{Issues} - -% License section -\input{../../../../../Licenses/GFDL.tex} - -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-1.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-1.tex deleted file mode 100644 index 21701c3..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-1.tex +++ /dev/null @@ -1,14 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/pixmaps/gnome-splash.png\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & PNG image data, 380 x 325, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/pixmaps/splash/gnome-splash.png\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & PNG image data, 380 x 325, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\hline -\multicolumn{2}{l}{\ }\\ -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-config.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-config.tex deleted file mode 100644 index 8c6b743..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-config.tex +++ /dev/null @@ -1,6 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\multicolumn{2}{l}{Sorry, this table is empty.}\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-theme.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-theme.tex deleted file mode 100644 index 8c6b743..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-theme.tex +++ /dev/null @@ -1,6 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\multicolumn{2}{l}{Sorry, this table is empty.}\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.aux deleted file mode 100644 index 2ba08bc..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.aux +++ /dev/null @@ -1,50 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} -\gdef \LT@i {\LT@entry - {1}{72.64pt}\LT@entry - {1}{308.11174pt}} -\gdef \LT@ii {\LT@entry - {1}{72.64pt}\LT@entry - {1}{176.94485pt}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{3}{section.3}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Configuration}{3}{section.4}} -\@writefile{toc}{\contentsline {section}{\numberline {5}Rendering}{4}{section.5}} -\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{4}{section.6}} -\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{4}{section.7}} -\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{5}{section.8}} -\newlabel{sec:License-GFDL-0}{{8}{6}{Preamble\relax }{section*.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{6}{subsection.8.1}} -\newlabel{sec:License-GFDL-1}{{8.1}{6}{Applicability And Definitions\relax }{subsection.8.1}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{8}{subsection.8.2}} -\newlabel{sec:License-GFDL-2}{{8.2}{8}{Verbatim Copying\relax }{subsection.8.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{8}{subsection.8.3}} -\newlabel{sec:License-GFDL-3}{{8.3}{8}{Copying In Quantity\relax }{subsection.8.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{9}{subsection.8.4}} -\newlabel{sec:License-GFDL-4}{{8.4}{9}{Modifications\relax }{subsection.8.4}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{10}{subsection.8.5}} -\newlabel{sec:License-GFDL-5}{{8.5}{10}{Combining Documents\relax }{subsection.8.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{11}{subsection.8.6}} -\newlabel{sec:License-GFDL-6}{{8.6}{11}{Collections Of Documents\relax }{subsection.8.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{11}{subsection.8.7}} -\newlabel{sec:License-GFDL-7}{{8.7}{11}{Aggregation With Independent Works\relax }{subsection.8.7}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{12}{subsection.8.8}} -\newlabel{sec:License-GFDL-8}{{8.8}{12}{Translation\relax }{subsection.8.8}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{12}{subsection.8.9}} -\newlabel{sec:License-GFDL-9}{{8.9}{12}{Termination\relax }{subsection.8.9}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{12}{subsection.8.10}} -\newlabel{sec:License-GFDL-10}{{8.10}{12}{Future Revisions OF This License\relax }{subsection.8.10}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{12}{subsection.8.11}} -\newlabel{sec:License-GFDL-11}{{8.11}{12}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.log deleted file mode 100644 index 509d0d9..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.log +++ /dev/null @@ -1,302 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size10.clo -File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/tools/longtable.sty -Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) -\LTleft=\skip43 -\LTright=\skip44 -\LTpre=\skip45 -\LTpost=\skip46 -\LTchunksize=\count87 -\LTcapwidth=\dimen103 -\LT@head=\box26 -\LT@firsthead=\box27 -\LT@foot=\box28 -\LT@lastfoot=\box29 -\LT@cols=\count88 -\LT@rows=\count89 -\c@LT@tables=\count90 -\c@LT@chunks=\count91 -\LT@p@ftn=\toks14 -) -(/usr/share/texmf/tex/latex/graphics/graphicx.sty -Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks15 -) -(/usr/share/texmf/tex/latex/graphics/graphics.sty -Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/trig.sty -Package: trig 1999/03/16 v1.09 sin cos tan (DPC) -) -(/usr/share/texmf/tex/latex/graphics/graphics.cfg -File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive -) -Package graphics Info: Driver file: pdftex.def on input line 80. - -(/usr/share/texmf/tex/latex/graphics/pdftex.def -File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex -\Gread@gobject=\count92 -)) -\Gin@req@height=\dimen104 -\Gin@req@width=\dimen105 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX -\@linkdim=\dimen106 -\Hy@linkcounter=\count93 -\Hy@pagecounter=\count94 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count95 -\Field@Width=\dimen107 -\Fld@charsize=\dimen108 -\Choice@toks=\toks16 -\Field@toks=\toks17 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count96 -\c@Hfootnote=\count97 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count98 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. - -(/usr/share/texmf/tex/context/base/supp-pdf.tex -(/usr/share/texmf/tex/context/base/supp-mis.tex -loading : Context Support Macros / Miscellaneous (2004.10.26) -\protectiondepth=\count99 -\scratchcounter=\count100 -\scratchtoks=\toks18 -\scratchdimen=\dimen109 -\scratchskip=\skip47 -\scratchmuskip=\muskip11 -\scratchbox=\box30 -\scratchread=\read1 -\scratchwrite=\write4 -\zeropoint=\dimen110 -\onepoint=\dimen111 -\onebasepoint=\dimen112 -\minusone=\count101 -\thousandpoint=\dimen113 -\onerealpoint=\dimen114 -\emptytoks=\toks19 -\nextbox=\box31 -\nextdepth=\dimen115 -\everyline=\toks20 -\!!counta=\count102 -\!!countb=\count103 -\recursecounter=\count104 -) -loading : Context Support Macros / PDF (2004.03.26) -\nofMPsegments=\count105 -\nofMParguments=\count106 -\MPscratchCnt=\count107 -\MPscratchDim=\dimen116 -\MPnumerator=\count108 -\everyMPtoPDFconversion=\toks21 -) -Package hyperref Info: Link coloring OFF on input line 13. - (/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count109 -) -LaTeX Info: Redefining \ref on input line 13. -LaTeX Info: Redefining \pageref on input line 13. - (./Manual.out) -(./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 16. -LaTeX Font Info: Try loading font information for OMS+cmr on input line 25. - (/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 25. - (./Manual.toc -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 9. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 9. - -[1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) -\tf@toc=\write5 -\openout5 = `Manual.toc'. - -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 39. - -(./table-theme.tex -Overfull \hbox (35.75174pt too wide) in alignment at lines 1--23 - [] [] - [] - - -Underfull \vbox (badness 10000) detected at line 23 - [] - - -Overfull \hbox (35.75174pt too wide) in alignment at lines 23--43 - [] [] - [] - - -Overfull \hbox (35.75174pt too wide) in alignment at lines 43--45 - [] [] - [] - -[2]) -Overfull \hbox (15.50415pt too wide) in paragraph at lines 50--54 -\OT1/cmr/m/n/10 work-place. This script cre-ates the ap-pro-pri-ate PNG im-ages - un-der img/$VERSION/ - [] - - -Overfull \hbox (17.0285pt too wide) in paragraph at lines 55--59 -\OT1/cmr/m/n/10 in-for-ma-tion needed, groups it and stores it un-der tgz/$VERS -ION/$RESOLUTION/ - [] - - -Overfull \hbox (6.83415pt too wide) in paragraph at lines 71--72 -[]\OT1/cmr/m/n/10 gnome-help file:///usr/share/gnome/help/gdm/C/gdm.xml#themema -nual - [] - -(./table-config.tex -Underfull \vbox (badness 10000) detected at line 13 - [] - - -Overfull \vbox (4.47491pt too high) has occurred while \output is active [] - - -[3]) -Overfull \hbox (0.71486pt too wide) in paragraph at lines 125--128 -[]\OT1/cmr/m/n/10 : KDM and GDM themes[][][] - [] - -[4] (../../../../../Licenses/GFDL.tex -Underfull \hbox (badness 10000) in paragraph at lines 5--14 - - [] - -[5] [6] -Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 -\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple - HTML, PostScript - [] - -[7] [8] [9] [10] [11] [12]) [13] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 2759 strings out of 94500 - 36683 string characters out of 1176766 - 90666 words of memory out of 1000000 - 5871 multiletter control sequences out of 10000+50000 - 10313 words of font info for 36 fonts, out of 500000 for 2000 - 580 hyphenation exceptions out of 1000 - 27i,8n,36p,222b,263s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 222 PDF objects out of 300000 - 43 named destinations out of 131072 - 169 words of extra memory for PDF output out of 65536 - -Output written on Manual.pdf (13 pages, 158058 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.out deleted file mode 100644 index 2f29f36..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.out +++ /dev/null @@ -1,19 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Workplace}{} -\BOOKMARK [1][-]{section.2}{Theme}{} -\BOOKMARK [1][-]{section.3}{Design}{} -\BOOKMARK [1][-]{section.4}{Configuration}{} -\BOOKMARK [1][-]{section.5}{Rendering}{} -\BOOKMARK [1][-]{section.6}{Testing}{} -\BOOKMARK [1][-]{section.7}{Issues}{} -\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} -\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} -\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} -\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} -\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} -\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} -\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} -\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} -\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} -\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.pdf deleted file mode 100644 index 6b2811f..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.toc deleted file mode 100644 index e9d6105..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.toc +++ /dev/null @@ -1,19 +0,0 @@ -\contentsline {section}{\numberline {1}Workplace}{2}{section.1} -\contentsline {section}{\numberline {2}Theme}{2}{section.2} -\contentsline {section}{\numberline {3}Design}{3}{section.3} -\contentsline {section}{\numberline {4}Configuration}{3}{section.4} -\contentsline {section}{\numberline {5}Rendering}{4}{section.5} -\contentsline {section}{\numberline {6}Testing}{4}{section.6} -\contentsline {section}{\numberline {7}Issues}{4}{section.7} -\contentsline {section}{\numberline {8}GNU Free Documentation License}{5}{section.8} -\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{6}{subsection.8.1} -\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{8}{subsection.8.2} -\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{8}{subsection.8.3} -\contentsline {subsection}{\numberline {8.4}Modifications}{9}{subsection.8.4} -\contentsline {subsection}{\numberline {8.5}Combining Documents}{10}{subsection.8.5} -\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{11}{subsection.8.6} -\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{11}{subsection.8.7} -\contentsline {subsection}{\numberline {8.8}Translation}{12}{subsection.8.8} -\contentsline {subsection}{\numberline {8.9}Termination}{12}{subsection.8.9} -\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{12}{subsection.8.10} -\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{12}{subsection.8.11} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/build.sh b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/build.sh deleted file mode 100755 index 70bef88..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/build.sh +++ /dev/null @@ -1,56 +0,0 @@ -#!/bin/bash -# -# Build KDM tables for LaTeX documents. -# -# Copyright (C) 2009 Alain Reguera Delgado -# -# 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:$ -#-------------------------------------- - -# Load functions. -. ~/artwork/trunk/Scripts/Bash/loadFunctions.sh - -# Define the names of your tables. -FILES="table-theme.tex - table-config.tex" - -for FILE in $FILES;do - - # Let know which table we are creating. - echo $FILE - - # Define what to do with each table you define on FILES. - case $FILE in - - table-theme.tex ) - # Create table holding theme files. - ROWS="$(getFiles '/usr/share/apps/kdm/themes' '/Modern/.*')" - ;; - - table-config.tex ) - # Create table holding configuration files. - ROWS="$(getFiles '/usr/share/config/kdm' 'rc$')" - ;; - - esac - - # Create table. - createTable "$ROWS" "" "" > $FILE - -done diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/manual.tex deleted file mode 100644 index d2b7848..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/manual.tex +++ /dev/null @@ -1,190 +0,0 @@ -\documentclass{article} -\usepackage{longtable} -\usepackage[pdftex]{graphicx} -\usepackage{hyperref} -\hypersetup{pdfauthor={CentOS Documentation SIG},% - pdftitle={KDE Display Manager (KDM)},% - pdfsubject={CentOS Corporate Visual Identity}% - } - -\title{KDE Display Manager (KDM)} -\author{CentOS Documentation SIG} - -\begin{document} - -\maketitle - -\begin{abstract} -This article describes the KDM Visual Style for CentOS Distribution. -KDE Display Manager (KDM) is the second choice defined as CentOS -Display Manager. If users leave their computers on all the time and -don't share their system, they won't see this as often as users who -share a desktop system with other users on the system or laptop users -who reboot and login more frequently. - -Copyright \copyright\ 2010\ The CentOS Project. Permission is -granted to copy, distribute and/or modify this document under the -terms of the GNU Free Documentation License, Version 1.2 or any later -version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the -license is included in the section entitled ``GNU Free Documentation -License''. -\end{abstract} - -\tableofcontents - -\section{Workplace} - -\begin{itemize} -\item SVN:trunk/Identity/Themes/\$THEME/Distro/BootUp/KDM/ -\item SVN:trunk/Translations/Identity/Themes/Distro/BootUp/KDM/ -\item SVN:trunk/Scripts/Identity/Themes/Distro/BootUp/KDM/ -\end{itemize} - -\section{Theme} - -\input{table-theme.tex} - -\section{Design} - -The centos-release.png and screenshot.png images are rendered for each -major release of CentOS. This task is done using the script render.sh -available in the workplace. This script creates the appropriate PNG -images under img/\$VERSION/ directory. - -The background.png image is taken from Backgrounds section. This task -is done using the script build.sh available in the workplace. This -script collects all information needed, groups it and stores it under -tgz/\$VERSION/\$RESOLUTION/ with the form \$THEME.tar.gz. - -Whith the build.sh script you can create KDM themes for specific -CentOS major releases, and inside each major release for specific -screen resolutions. - -KDM theme uses the same standard that GDM theme does. More information -about GDM theming is available in the \textit{GNOME Display Manager -Reference Manual}. This guide is available online and inside your -system's help. As shortcut to get that help, you can run the following -command: - -\begin{itemize} -\item gnome-help file:///usr/share/gnome/help/gdm/C/gdm.xml\#thememanual -\end{itemize} - -\section{Configuration} - -\input{table-config.tex} - -\begin{description} - -\item[Theme]: In the file \emph{kdmrc}, \texttt{Theme} defines which -is the KDM theme used by default. - -\texttt{Theme=/usr/share/apps/kdm/themes/Modern/} - -\item[UseTheme]: In the file \emph{kdmrc}, \texttt{UseTheme} defines -the precedence of background. If true KDM theme background image takes -precedence against KDM background. - -\texttt{UseTheme=true} - -\item[Wallpaper]: In the file \emph{backgroundrc}, \texttt{Wallpaper} -defines the default configuration for KDM background. - -\texttt{Wallpaper=/usr/share/backgrounds/images/default.png} - -\end{description} - -The background image used on KDM is one file, and the background image -used on KDM theme is another file. Even they are independent files, -the monolithic visual structure requires the same visual information -in these images. - -More information about KDE login screen, KDM and its configuration can -be found in KDE help. As shortcut to get that help, you can run the -following commands: - -\begin{itemize} -\item khelpcenter help:/kdm/login.html -\item khelpcenter help:/kdm/configuring-kdm.html -\item khelpcenter help:/kdm/kdm-files.html -\end{itemize} - -\section{Rendering} -\section{Testing} -\section{Issues} - -\begin{description} - -\item[Transition from Greeter to Desktop]: If KDE desktop background -and KDM background are the same (and they should because the -monolithic visual structure) the transition from login screen to -desktop is ``smooth'' because the background image is always visible -on the screen. - -\item[Differences between KDM and GDM themes]: KDM and GDM -themes\footnote{It refers to the \emph{.xml} files and its related -files.} are basically the same except for the following differences: - -\begin{enumerate} - -\item KDM theme requires the ``user-entry'' and ``pw-entry'' stocks. -This forces the using of two boxes, one for username and one for -password. This boxes are visibly appart one from another. In GDM we -use just one box (the ``user-pw-entry'' stock), both for -username and password. - -\item In KDM theme, messages were centered on the screen to fit the -KDM two-boxes design. In GDM they are centered to the -``user-pw-entry'' stock width. - -\item In KDM theme, the ``language'' stock shows nothing. It creates -an empty space in the screen. The language block was commented to save -space on the screen. In GDM laguage buttom is present and when clicked -a box pops up with a list of languages to choose. - -\item Both KDM and GDM themes use the same font defintion in the -\emph{.xml} file, but in presentation they look quiet different. For -example the KDM clock's \emph{Sans 10 Bold} theme definition does not -take effect. Probably font definition in \emph{kdmrc} file takes -precedence against theme's one. - -\end{enumerate} - -\item[Different resolutions]: Designing of KDM theme needs to be -expandable through different screen resolutions. By default, KDM theme -uses a background image of 2048x1536 pixels. When screen resolution -changes the predifined behaviour is to scale this image to fit the -current display resolution. If the screen resolution is higher, or -differs in ratio (for example when it is a wide screens) the design of -KDM theme could loose quality or look different from the original one. - -As a workaround, if KDM theme looks narrow or deformed to you, use the -build.sh script to create the KDM theme in your specific screen -resolution. - -\item[KDM theme installation]: To install a KDM theme you need to copy -its files from the workplace to its location in the filesytem. If you -want to make that KDM theme your default one, then you also need to -update the KDM configuration files to match your theme location. Both -of these actions require you to have \emph{root} privileges. - -\item[Default Display Manager]: By default KDM is the second display -manager choice\footnote{See the file \emph{/etc/X11/prefdm}.}. To use -KDM as first choise, run the following command (as \emph{root}) and -reboot: - -\texttt{echo "DISPLAYMANAGER=KDE" > /etc/sysconfig/desktop} - -\item[Package content]: CentOS Default KDM Theme seems to be inside -the package redhat-artwork. In contrast with GDM which has some files in -redhat-logos and others in redhat-artwork. Could we standardize this ? -All files in just one package (redhat-artwork) or files divided in two -packages (redhat-artwork, and redhat-logos). - -\end{description} - -% License section -\input{../../../../../Licenses/GFDL.tex} - -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-1.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-1.tex deleted file mode 100644 index 5f0c0d3..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-1.tex +++ /dev/null @@ -1,45 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/background.png\\ -\textbf{Package}: & redhat-artwork\\ -\textbf{Description}: & PNG image data, 1024 x 768, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/centos-release.png\\ -\textbf{Package}: & redhat-artwork\\ -\textbf{Description}: & PNG image data, 181 x 48, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/centos-symbol.png\\ -\textbf{Package}: & redhat-artwork\\ -\textbf{Description}: & PNG image data, 48 x 48, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/GdmGreeterTheme.desktop\\ -\textbf{Package}: & redhat-artwork\\ -\textbf{Description}: & UTF-8 Unicode English text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-language.png\\ -\textbf{Package}: & redhat-artwork\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-reboot.png\\ -\textbf{Package}: & redhat-artwork\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-session.png\\ -\textbf{Package}: & redhat-artwork\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-shutdown.png\\ -\textbf{Package}: & redhat-artwork\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/Modern.xml\\ -\textbf{Package}: & redhat-artwork\\ -\textbf{Description}: & XML 1.0 document text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/screenshot.png\\ -\textbf{Package}: & redhat-artwork\\ -\textbf{Description}: & PNG image data, 200 x 150, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-2.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-2.tex deleted file mode 100644 index 598664e..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-2.tex +++ /dev/null @@ -1,13 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/config/kdm/kdmrc\\ -\textbf{Package}: & kdebase\\ -\textbf{Description}: & ASCII text, with very long lines\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/config/kdm/backgroundrc\\ -\textbf{Package}: & kdebase\\ -\textbf{Description}: & ASCII text\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-config.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-config.tex deleted file mode 100644 index 7c4232e..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-config.tex +++ /dev/null @@ -1,13 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/config/kdm/backgroundrc\\ -\textbf{Package}: & kdebase\\ -\textbf{Description}: & ASCII text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/config/kdm/kdmrc\\ -\textbf{Package}: & kdebase\\ -\textbf{Description}: & ASCII text, with very long lines\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-theme.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-theme.tex deleted file mode 100644 index fa0231c..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-theme.tex +++ /dev/null @@ -1,45 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/background.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 1024 x 768, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/centos-release.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 181 x 48, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/centos-symbol.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 48 x 48, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/GdmGreeterTheme.desktop\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & UTF-8 Unicode English text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-language.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-reboot.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-session.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-shutdown.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/Modern.xml\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & XML 1.0 document text\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/screenshot.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 200 x 150, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.aux deleted file mode 100644 index 4483cd3..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.aux +++ /dev/null @@ -1,50 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\gdef \LT@i {\LT@entry - {1}{72.64pt}\LT@entry - {1}{304.47844pt}} -\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{2}{section.3}} -\gdef \LT@ii {\LT@entry - {1}{72.64pt}\LT@entry - {1}{134.25027pt}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Configuration}{3}{section.4}} -\@writefile{toc}{\contentsline {section}{\numberline {5}Rendering}{3}{section.5}} -\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{3}{section.6}} -\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{3}{section.7}} -\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8}} -\newlabel{sec:License-GFDL-0}{{8}{4}{Preamble\relax }{section*.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{4}{subsection.8.1}} -\newlabel{sec:License-GFDL-1}{{8.1}{4}{Applicability And Definitions\relax }{subsection.8.1}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{6}{subsection.8.2}} -\newlabel{sec:License-GFDL-2}{{8.2}{6}{Verbatim Copying\relax }{subsection.8.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{6}{subsection.8.3}} -\newlabel{sec:License-GFDL-3}{{8.3}{6}{Copying In Quantity\relax }{subsection.8.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{7}{subsection.8.4}} -\newlabel{sec:License-GFDL-4}{{8.4}{7}{Modifications\relax }{subsection.8.4}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5}} -\newlabel{sec:License-GFDL-5}{{8.5}{8}{Combining Documents\relax }{subsection.8.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{9}{subsection.8.6}} -\newlabel{sec:License-GFDL-6}{{8.6}{9}{Collections Of Documents\relax }{subsection.8.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{9}{subsection.8.7}} -\newlabel{sec:License-GFDL-7}{{8.7}{9}{Aggregation With Independent Works\relax }{subsection.8.7}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{10}{subsection.8.8}} -\newlabel{sec:License-GFDL-8}{{8.8}{10}{Translation\relax }{subsection.8.8}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{10}{subsection.8.9}} -\newlabel{sec:License-GFDL-9}{{8.9}{10}{Termination\relax }{subsection.8.9}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{10}{subsection.8.10}} -\newlabel{sec:License-GFDL-10}{{8.10}{10}{Future Revisions OF This License\relax }{subsection.8.10}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11}} -\newlabel{sec:License-GFDL-11}{{8.11}{10}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.log deleted file mode 100644 index a6762c0..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.log +++ /dev/null @@ -1,273 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size10.clo -File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/tools/longtable.sty -Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) -\LTleft=\skip43 -\LTright=\skip44 -\LTpre=\skip45 -\LTpost=\skip46 -\LTchunksize=\count87 -\LTcapwidth=\dimen103 -\LT@head=\box26 -\LT@firsthead=\box27 -\LT@foot=\box28 -\LT@lastfoot=\box29 -\LT@cols=\count88 -\LT@rows=\count89 -\c@LT@tables=\count90 -\c@LT@chunks=\count91 -\LT@p@ftn=\toks14 -) -(/usr/share/texmf/tex/latex/graphics/graphicx.sty -Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks15 -) -(/usr/share/texmf/tex/latex/graphics/graphics.sty -Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/trig.sty -Package: trig 1999/03/16 v1.09 sin cos tan (DPC) -) -(/usr/share/texmf/tex/latex/graphics/graphics.cfg -File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive -) -Package graphics Info: Driver file: pdftex.def on input line 80. - -(/usr/share/texmf/tex/latex/graphics/pdftex.def -File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex -\Gread@gobject=\count92 -)) -\Gin@req@height=\dimen104 -\Gin@req@width=\dimen105 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX -\@linkdim=\dimen106 -\Hy@linkcounter=\count93 -\Hy@pagecounter=\count94 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count95 -\Field@Width=\dimen107 -\Fld@charsize=\dimen108 -\Choice@toks=\toks16 -\Field@toks=\toks17 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count96 -\c@Hfootnote=\count97 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count98 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. - -(/usr/share/texmf/tex/context/base/supp-pdf.tex -(/usr/share/texmf/tex/context/base/supp-mis.tex -loading : Context Support Macros / Miscellaneous (2004.10.26) -\protectiondepth=\count99 -\scratchcounter=\count100 -\scratchtoks=\toks18 -\scratchdimen=\dimen109 -\scratchskip=\skip47 -\scratchmuskip=\muskip11 -\scratchbox=\box30 -\scratchread=\read1 -\scratchwrite=\write4 -\zeropoint=\dimen110 -\onepoint=\dimen111 -\onebasepoint=\dimen112 -\minusone=\count101 -\thousandpoint=\dimen113 -\onerealpoint=\dimen114 -\emptytoks=\toks19 -\nextbox=\box31 -\nextdepth=\dimen115 -\everyline=\toks20 -\!!counta=\count102 -\!!countb=\count103 -\recursecounter=\count104 -) -loading : Context Support Macros / PDF (2004.03.26) -\nofMPsegments=\count105 -\nofMParguments=\count106 -\MPscratchCnt=\count107 -\MPscratchDim=\dimen116 -\MPnumerator=\count108 -\everyMPtoPDFconversion=\toks21 -) -Package hyperref Info: Link coloring OFF on input line 13. - (/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count109 -) -LaTeX Info: Redefining \ref on input line 13. -LaTeX Info: Redefining \pageref on input line 13. - (./Manual.out) -(./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 16. -LaTeX Font Info: Try loading font information for OMS+cmr on input line 23. - (/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 23. - (./Manual.toc -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 9. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 9. - -[1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) -\tf@toc=\write5 -\openout5 = `Manual.toc'. - -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 37. - -(./table-theme.tex -Overfull \hbox (32.11844pt too wide) in alignment at lines 1--23 - [] [] - [] - - -Underfull \vbox (badness 10000) detected at line 23 - [] - - -Overfull \hbox (32.11844pt too wide) in alignment at lines 23--29 - [] [] - [] - -) [2] -Overfull \hbox (38.08037pt too wide) in paragraph at lines 62--65 -\OT1/cmr/m/n/10 shown in the bot-tom. This im-age has the same back-ground colo -r of splas[]inactive[]bar.png - [] - -(./table-config.tex -Underfull \vbox (badness 10000) detected at line 9 - [] - -) (../../../../../Licenses/GFDL.tex -Underfull \hbox (badness 10000) in paragraph at lines 5--14 - - [] - -[3] [4] -Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 -\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple - HTML, PostScript - [] - -[5] [6] [7] [8] [9] [10]) [11] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 2751 strings out of 94500 - 36619 string characters out of 1176766 - 89633 words of memory out of 1000000 - 5870 multiletter control sequences out of 10000+50000 - 9615 words of font info for 34 fonts, out of 500000 for 2000 - 580 hyphenation exceptions out of 1000 - 27i,6n,36p,222b,214s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 193 PDF objects out of 300000 - 38 named destinations out of 131072 - 169 words of extra memory for PDF output out of 65536 - -Output written on Manual.pdf (11 pages, 118515 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.out deleted file mode 100644 index 2f29f36..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.out +++ /dev/null @@ -1,19 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Workplace}{} -\BOOKMARK [1][-]{section.2}{Theme}{} -\BOOKMARK [1][-]{section.3}{Design}{} -\BOOKMARK [1][-]{section.4}{Configuration}{} -\BOOKMARK [1][-]{section.5}{Rendering}{} -\BOOKMARK [1][-]{section.6}{Testing}{} -\BOOKMARK [1][-]{section.7}{Issues}{} -\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} -\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} -\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} -\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} -\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} -\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} -\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} -\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} -\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} -\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.pdf deleted file mode 100644 index 499b4e2..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.toc deleted file mode 100644 index dd5b675..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.toc +++ /dev/null @@ -1,19 +0,0 @@ -\contentsline {section}{\numberline {1}Workplace}{2}{section.1} -\contentsline {section}{\numberline {2}Theme}{2}{section.2} -\contentsline {section}{\numberline {3}Design}{2}{section.3} -\contentsline {section}{\numberline {4}Configuration}{3}{section.4} -\contentsline {section}{\numberline {5}Rendering}{3}{section.5} -\contentsline {section}{\numberline {6}Testing}{3}{section.6} -\contentsline {section}{\numberline {7}Issues}{3}{section.7} -\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8} -\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{4}{subsection.8.1} -\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{6}{subsection.8.2} -\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{6}{subsection.8.3} -\contentsline {subsection}{\numberline {8.4}Modifications}{7}{subsection.8.4} -\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5} -\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{9}{subsection.8.6} -\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{9}{subsection.8.7} -\contentsline {subsection}{\numberline {8.8}Translation}{10}{subsection.8.8} -\contentsline {subsection}{\numberline {8.9}Termination}{10}{subsection.8.9} -\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{10}{subsection.8.10} -\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/build.sh b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/build.sh deleted file mode 100755 index d166fec..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/build.sh +++ /dev/null @@ -1,55 +0,0 @@ -#!/bin/bash -# -# Build KSplash tables for LaTeX document. -# -# Copyright (C) 2009 Alain Reguera Delgado -# -# 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:$ -#-------------------------------------- - -# Load functions. -. ~/artwork/trunk/Scripts/Bash/loadFunctions. - -# Define the names of your tables. -FILES="table-theme.tex - table-config.tex" - -for FILE in $FILES;do - - # Let know what table we are creating. - echo $FILE - - case $FILE in - - table-theme.tex ) - # Create table holding theme files. - ROWS="$(getFiles '/usr/share/apps/ksplash/Themes' '/Modern/.*')" - ;; - - table-config.tex ) - # Create table holding configuration files. - ROWS="$(getFiles '/usr/share/config' 'ksplashrc')" - ;; - - esac - - # Create table. - createTable "$ROWS" "" "" > $FILE - -done diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/manual.tex deleted file mode 100644 index e7588d4..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/manual.tex +++ /dev/null @@ -1,95 +0,0 @@ -\documentclass{article} -\usepackage{longtable} -\usepackage[pdftex]{graphicx} -\usepackage{hyperref} -\hypersetup{pdfauthor={CentOS Documentation SIG},% - pdftitle={KDE Splash)},% - pdfsubject={CentOS Corporate Visual Identity}% - } - -\title{KDE Splash} -\author{CentOS Documentation SIG} - -\begin{document} - -\maketitle - -\begin{abstract} - -This article describes the KDE Splash Visual Style for CentOS -Distribution. This image is displayed after login screen, while KDE -session is being loaded. - -Copyright \copyright\ 2010\ The CentOS Project. Permission is -granted to copy, distribute and/or modify this document under the -terms of the GNU Free Documentation License, Version 1.2 or any later -version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the -license is included in the section entitled ``GNU Free Documentation -License''. -\end{abstract} - -\tableofcontents - - -\section{Workplace} -\begin{itemize} -\item SVN:trunk/Identity/Themes/\$THEME/Distro/BootUp/KSplash/ -\item SVN:trunk/Translations/Identity/Themes/Distro/BootUp/KSplash/ -\item SVN:trunk/Scripts/Identity/Themes/Distro/BootUp/KSplash/ -\end{itemize} - -\section{Theme} - -\input{table-theme.tex} - -\section{Design} - -KDE Splash Preview.png and splash\_top\_bar.png images are rendered -for each major release of CentOS Distribution. Each image is based in -the same Artistic Motif and has the following components: - -\begin{enumerate} -\item The CentOS Symbol. -\item The CentOS Release Brand. -\item The CentOS Default Artistic Motif. -\end{enumerate} - -KDE Splash splash\_inactive\_bar.png and splash\_active\_bar.png are -used to create the progress effect while loading. They both have the -same background color. - -KDE Splash splash\_bottom\_bar.png is used to as background to the -label shown in the bottom. This image has the same background color of -splas\_inactive\_bar.png and splash\_active\_bar.png. - -KDE Splash theme definitions are in the file Theme.rc. Among available -definitions are the splash name, description, version, author, -engine, icons flashing, always show progress, and label foreground. - -Image rendering is done using the script render.sh available in the -workplace. This script creates the appropriate PNG images under -img/\$VERSION/. - -There is no color limitation in this section. - -\section{Configuration} - -\input{table-config.tex} - -\begin{description} - -\item[Theme]: Defines the default splash theme. The name should match -a directory name under /usr/share/ksplash/Themes/. - -\texttt{Theme=Modern} -\end{description} - -\section{Rendering} -\section{Testing} -\section{Issues} - -% License section -\input{../../../../../Licenses/GFDL.tex} - -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-1.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-1.tex deleted file mode 100644 index 19455f1..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-1.tex +++ /dev/null @@ -1,29 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/Preview.png\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & PNG image data, 400 x 322, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_active\_bar.png\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & PNG image data, 400 x 61, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_bottom.png\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & PNG image data, 400 x 16, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_inactive\_bar.png\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & PNG image data, 400 x 61, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_top.png\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & PNG image data, 400 x 245, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/Theme.rc\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & ASCII English text\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-2.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-2.tex deleted file mode 100644 index 1d5c195..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-2.tex +++ /dev/null @@ -1,9 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/config/ksplashrc\\ -\textbf{Package}: & kdebase\\ -\textbf{Description}: & ASCII text\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-config.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-config.tex deleted file mode 100644 index 1d5c195..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-config.tex +++ /dev/null @@ -1,9 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/config/ksplashrc\\ -\textbf{Package}: & kdebase\\ -\textbf{Description}: & ASCII text\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-theme.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-theme.tex deleted file mode 100644 index 0c70e78..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-theme.tex +++ /dev/null @@ -1,29 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/Preview.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 400 x 322, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_active\_bar.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 400 x 61, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_bottom.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 400 x 16, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_inactive\_bar.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 400 x 61, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_top.png\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & PNG image data, 400 x 245, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/Theme.rc\\ -\textbf{Package}: & \textbf{Unknown!}\\ -\textbf{Description}: & ASCII English text\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.aux deleted file mode 100644 index 06c3696..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.aux +++ /dev/null @@ -1,47 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\gdef \LT@i {\LT@entry - {1}{72.64pt}\LT@entry - {1}{287.61165pt}} -\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{3}{section.3}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Configuration}{3}{section.4}} -\@writefile{toc}{\contentsline {section}{\numberline {5}Rendering}{3}{section.5}} -\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{3}{section.6}} -\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{3}{section.7}} -\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8}} -\newlabel{sec:License-GFDL-0}{{8}{3}{Preamble\relax }{section*.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{3}{subsection.8.1}} -\newlabel{sec:License-GFDL-1}{{8.1}{3}{Applicability And Definitions\relax }{subsection.8.1}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{5}{subsection.8.2}} -\newlabel{sec:License-GFDL-2}{{8.2}{5}{Verbatim Copying\relax }{subsection.8.2}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{5}{subsection.8.3}} -\newlabel{sec:License-GFDL-3}{{8.3}{5}{Copying In Quantity\relax }{subsection.8.3}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{6}{subsection.8.4}} -\newlabel{sec:License-GFDL-4}{{8.4}{6}{Modifications\relax }{subsection.8.4}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5}} -\newlabel{sec:License-GFDL-5}{{8.5}{8}{Combining Documents\relax }{subsection.8.5}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{8}{subsection.8.6}} -\newlabel{sec:License-GFDL-6}{{8.6}{8}{Collections Of Documents\relax }{subsection.8.6}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{8}{subsection.8.7}} -\newlabel{sec:License-GFDL-7}{{8.7}{8}{Aggregation With Independent Works\relax }{subsection.8.7}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{9}{subsection.8.8}} -\newlabel{sec:License-GFDL-8}{{8.8}{9}{Translation\relax }{subsection.8.8}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{9}{subsection.8.9}} -\newlabel{sec:License-GFDL-9}{{8.9}{9}{Termination\relax }{subsection.8.9}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{9}{subsection.8.10}} -\newlabel{sec:License-GFDL-10}{{8.10}{9}{Future Revisions OF This License\relax }{subsection.8.10}{}} -\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11}} -\newlabel{sec:License-GFDL-11}{{8.11}{10}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.log deleted file mode 100644 index 1d33b78..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.log +++ /dev/null @@ -1,258 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size10.clo -File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/tools/longtable.sty -Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) -\LTleft=\skip43 -\LTright=\skip44 -\LTpre=\skip45 -\LTpost=\skip46 -\LTchunksize=\count87 -\LTcapwidth=\dimen103 -\LT@head=\box26 -\LT@firsthead=\box27 -\LT@foot=\box28 -\LT@lastfoot=\box29 -\LT@cols=\count88 -\LT@rows=\count89 -\c@LT@tables=\count90 -\c@LT@chunks=\count91 -\LT@p@ftn=\toks14 -) -(/usr/share/texmf/tex/latex/graphics/graphicx.sty -Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks15 -) -(/usr/share/texmf/tex/latex/graphics/graphics.sty -Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) - -(/usr/share/texmf/tex/latex/graphics/trig.sty -Package: trig 1999/03/16 v1.09 sin cos tan (DPC) -) -(/usr/share/texmf/tex/latex/graphics/graphics.cfg -File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive -) -Package graphics Info: Driver file: pdftex.def on input line 80. - -(/usr/share/texmf/tex/latex/graphics/pdftex.def -File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex -\Gread@gobject=\count92 -)) -\Gin@req@height=\dimen104 -\Gin@req@width=\dimen105 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX -\@linkdim=\dimen106 -\Hy@linkcounter=\count93 -\Hy@pagecounter=\count94 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count95 -\Field@Width=\dimen107 -\Fld@charsize=\dimen108 -\Choice@toks=\toks16 -\Field@toks=\toks17 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count96 -\c@Hfootnote=\count97 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count98 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. -LaTeX Font Info: ... okay on input line 13. - -(/usr/share/texmf/tex/context/base/supp-pdf.tex -(/usr/share/texmf/tex/context/base/supp-mis.tex -loading : Context Support Macros / Miscellaneous (2004.10.26) -\protectiondepth=\count99 -\scratchcounter=\count100 -\scratchtoks=\toks18 -\scratchdimen=\dimen109 -\scratchskip=\skip47 -\scratchmuskip=\muskip11 -\scratchbox=\box30 -\scratchread=\read1 -\scratchwrite=\write4 -\zeropoint=\dimen110 -\onepoint=\dimen111 -\onebasepoint=\dimen112 -\minusone=\count101 -\thousandpoint=\dimen113 -\onerealpoint=\dimen114 -\emptytoks=\toks19 -\nextbox=\box31 -\nextdepth=\dimen115 -\everyline=\toks20 -\!!counta=\count102 -\!!countb=\count103 -\recursecounter=\count104 -) -loading : Context Support Macros / PDF (2004.03.26) -\nofMPsegments=\count105 -\nofMParguments=\count106 -\MPscratchCnt=\count107 -\MPscratchDim=\dimen116 -\MPnumerator=\count108 -\everyMPtoPDFconversion=\toks21 -) -Package hyperref Info: Link coloring OFF on input line 13. - (/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count109 -) -LaTeX Info: Redefining \ref on input line 13. -LaTeX Info: Redefining \pageref on input line 13. - (./Manual.out) -(./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 16. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 16. -LaTeX Font Info: Try loading font information for OMS+cmr on input line 23. - (/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 23. - (./Manual.toc -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 9. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 9. - -[1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) -\tf@toc=\write5 -\openout5 = `Manual.toc'. - -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 37. - -(./table-theme.tex -Overfull \hbox (15.25165pt too wide) in alignment at lines 1--21 - [] [] - [] - - -Underfull \vbox (badness 10000) detected at line 21 - [] - -) (../../../../../Licenses/GFDL.tex -Underfull \hbox (badness 10000) in paragraph at lines 5--14 - - [] - -[2] [3] -Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 -\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple - HTML, PostScript - [] - -[4] [5] [6] [7] [8] [9]) [10] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 2741 strings out of 94500 - 36518 string characters out of 1176766 - 89618 words of memory out of 1000000 - 5868 multiletter control sequences out of 10000+50000 - 9615 words of font info for 34 fonts, out of 500000 for 2000 - 580 hyphenation exceptions out of 1000 - 27i,6n,36p,222b,214s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 185 PDF objects out of 300000 - 33 named destinations out of 131072 - 169 words of extra memory for PDF output out of 65536 - -Output written on Manual.pdf (10 pages, 115636 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.out deleted file mode 100644 index 2f29f36..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.out +++ /dev/null @@ -1,19 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Workplace}{} -\BOOKMARK [1][-]{section.2}{Theme}{} -\BOOKMARK [1][-]{section.3}{Design}{} -\BOOKMARK [1][-]{section.4}{Configuration}{} -\BOOKMARK [1][-]{section.5}{Rendering}{} -\BOOKMARK [1][-]{section.6}{Testing}{} -\BOOKMARK [1][-]{section.7}{Issues}{} -\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} -\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} -\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} -\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} -\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} -\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} -\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} -\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} -\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} -\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} -\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.pdf deleted file mode 100644 index e01a152..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.toc deleted file mode 100644 index ca825b6..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.toc +++ /dev/null @@ -1,19 +0,0 @@ -\contentsline {section}{\numberline {1}Workplace}{2}{section.1} -\contentsline {section}{\numberline {2}Theme}{2}{section.2} -\contentsline {section}{\numberline {3}Design}{3}{section.3} -\contentsline {section}{\numberline {4}Configuration}{3}{section.4} -\contentsline {section}{\numberline {5}Rendering}{3}{section.5} -\contentsline {section}{\numberline {6}Testing}{3}{section.6} -\contentsline {section}{\numberline {7}Issues}{3}{section.7} -\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8} -\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{3}{subsection.8.1} -\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{5}{subsection.8.2} -\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{5}{subsection.8.3} -\contentsline {subsection}{\numberline {8.4}Modifications}{6}{subsection.8.4} -\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5} -\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{8}{subsection.8.6} -\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{8}{subsection.8.7} -\contentsline {subsection}{\numberline {8.8}Translation}{9}{subsection.8.8} -\contentsline {subsection}{\numberline {8.9}Termination}{9}{subsection.8.9} -\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{9}{subsection.8.10} -\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/build.sh b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/build.sh deleted file mode 100755 index 5fa8a04..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/build.sh +++ /dev/null @@ -1,50 +0,0 @@ -#!/bin/bash -# -# Build RHGB tables for LaTeX documents. -# -# Copyright (C) 2009 Alain Reguera Delgado -# -# 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:$ -#-------------------------------------- - -# Load functions. -. ~/artwork/trunk/Scripts/Bash/loadFunctions.sh - -# Define the names of your tables. -FILES="table-theme.tex" - -for FILE in $FILES;do - - # Let know which table we are creating. - echo $FILE - - # Define what to do with each table you define on FILES. - case $FILE in - - table-theme.tex ) - # Create table holding theme files. - ROWS="$(getFiles '/usr/share/rhgb' '.*\.png')" - ;; - - esac - - # Create table. - createTable "$ROWS" "" "" > $FILE - -done diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/manual.tex deleted file mode 100644 index d8bab77..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/manual.tex +++ /dev/null @@ -1,60 +0,0 @@ -\documentclass{article} -\usepackage{longtable} -\usepackage[pdftex]{graphicx} -\usepackage{hyperref} -\hypersetup{pdfauthor={CentOS Documentation SIG},% - pdftitle={Graphic Boot (RHGB))},% - pdfsubject={CentOS Corporate Visual Identity}% - } - -\title{Graphic Boot (RHGB)} -\author{CentOS Documentation SIG} - -\begin{document} - -\maketitle - -\begin{abstract} - -This article describes the RHGB Visual Style for CentOS Distribution. -This screen is shown as the machine starts up. Users can toggle -between graphic ``Hide Detail'' mode text ``Show Detail'' mode. - -Copyright \copyright\ 2010\ The CentOS Project. Permission is -granted to copy, distribute and/or modify this document under the -terms of the GNU Free Documentation License, Version 1.2 or any later -version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the -license is included in the section entitled ``GNU Free Documentation -License''. -\end{abstract} - -\tableofcontents - -\section{Workplace} - -\begin{itemize} -\item SVN:trunk/Identity/Themes/\$THEME/Distro/BootUp/RHGB/ -\item SVN:trunk/Translations/Identity/Themes/Distro/BootUp/RHGB/ -\item SVN:trunk/Scripts/Identity/Themes/Distro/BootUp/RHGB/ -\end{itemize} - -\section{Theme} - -\input{table-theme.tex} - -The system-logo.png image is rendered for each major release of -CentOS. This task is done using the script render.sh available in the -workplace. This script creates the appropriate PNG images under -img/\$VERSION/ directory. - -\section{Design} -\section{Configuration} -\section{Rendering} -\section{Testing} -\section{Issues} - -% License section -\input{../../../../../Licenses/GFDL.tex} - -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/table-1.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/table-1.tex deleted file mode 100644 index a6a140c..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/table-1.tex +++ /dev/null @@ -1,21 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/rhgb/large-computer.png\\ -\textbf{Package}: & rhgb\\ -\textbf{Description}: & PNG image data, 520 x 230, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/rhgb/main-logo.png\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & PNG image data, 497 x 166, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/rhgb/system-logo.png\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & PNG image data, 147 x 39, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/rhgb/throbber-anim.png\\ -\textbf{Package}: & rhgb\\ -\textbf{Description}: & PNG image data, 288 x 24, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/table-theme.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/table-theme.tex deleted file mode 100644 index b9b3d6f..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/table-theme.tex +++ /dev/null @@ -1,21 +0,0 @@ -\begin{longtable}{rl} -\hline -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/rhgb/large-computer.png\\ -\textbf{Package}: & rhgb\\ -\textbf{Description}: & PNG image data, 530 x 240, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/rhgb/main-logo.png\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & PNG image data, 497 x 166, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/rhgb/system-logo.png\\ -\textbf{Package}: & redhat-logos\\ -\textbf{Description}: & PNG image data, 147 x 39, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\textbf{Target}: & /usr/share/rhgb/throbber-anim.png\\ -\textbf{Package}: & rhgb\\ -\textbf{Description}: & PNG image data, 288 x 24, 8-bit/color RGBA, non-interlaced\\ -\multicolumn{2}{l}{\ }\\ -\hline -\end{longtable} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.aux deleted file mode 100644 index db1ff68..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.aux +++ /dev/null @@ -1,17 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{1}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Workplace}{2}{section.2}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{2}{section.3}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Rendering}{3}{section.4}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.log deleted file mode 100644 index ca0bde3..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.log +++ /dev/null @@ -1,163 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 31 JAN 2010 19:04 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size10.clo -File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks14 -) -\@linkdim=\dimen103 -\Hy@linkcounter=\count87 -\Hy@pagecounter=\count88 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count89 -\Field@Width=\dimen104 -\Fld@charsize=\dimen105 -\Choice@toks=\toks15 -\Field@toks=\toks16 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count90 -\c@Hfootnote=\count91 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count92 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 11. -LaTeX Font Info: ... okay on input line 11. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 11. -LaTeX Font Info: ... okay on input line 11. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 11. -LaTeX Font Info: ... okay on input line 11. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 11. -LaTeX Font Info: ... okay on input line 11. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 11. -LaTeX Font Info: ... okay on input line 11. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 11. -LaTeX Font Info: ... okay on input line 11. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 11. -LaTeX Font Info: ... okay on input line 11. -Package hyperref Info: Link coloring OFF on input line 11. - -(/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count93 -) -LaTeX Info: Redefining \ref on input line 11. -LaTeX Info: Redefining \pageref on input line 11. - (./Manual.out) (./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 14. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 14. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 14. -(./Manual.toc) -\tf@toc=\write4 -\openout4 = `Manual.toc'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 24. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 24. - [1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] -LaTeX Font Info: Try loading font information for OMS+cmr on input line 66. - -(/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 66. - [2] [3] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 1960 strings out of 94500 - 26775 string characters out of 1176766 - 75186 words of memory out of 1000000 - 5140 multiletter control sequences out of 10000+50000 - 9399 words of font info for 33 fonts, out of 500000 for 2000 - 580 hyphenation exceptions out of 1000 - 27i,8n,36p,148b,266s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 85 PDF objects out of 300000 - 12 named destinations out of 131072 - 49 words of extra memory for PDF output out of 65536 - -Output written on Manual.pdf (3 pages, 74579 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.out deleted file mode 100644 index f48d4c8..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.out +++ /dev/null @@ -1,4 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Introduction}{} -\BOOKMARK [1][-]{section.2}{Workplace}{} -\BOOKMARK [1][-]{section.3}{Design}{} -\BOOKMARK [1][-]{section.4}{Rendering}{} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.pdf deleted file mode 100644 index 3be2e1b..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.toc deleted file mode 100644 index 796149c..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/Manual.toc +++ /dev/null @@ -1,4 +0,0 @@ -\contentsline {section}{\numberline {1}Introduction}{1}{section.1} -\contentsline {section}{\numberline {2}Workplace}{2}{section.2} -\contentsline {section}{\numberline {3}Design}{2}{section.3} -\contentsline {section}{\numberline {4}Rendering}{3}{section.4} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/manual.tex deleted file mode 100644 index d78644f..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Distro/Releases/manual.tex +++ /dev/null @@ -1,101 +0,0 @@ -% -% Describe The CentOS Distribution Release Schema. -% -\documentclass{article} - -\usepackage{hyperref} - -\title{The CentOS Release Brand} -\author{Alain Reguera Delgado} - -\begin{document} - -\maketitle - -\begin{abstract} -This is abstract. -\end{abstract} - -\tableofcontents - -\section{Introduction} - -The upstream vendor has released 3 versions of Enterprise Linux that -CentOS Project rebuilds the freely available SRPMS for\footnote{ -\url{http://wiki.centos.org/About}}. So, the major CentOS releases are -CentOS 3, CentOS 4 and CentOS 5. The upstream vendor releases security -updates as required by circumstances. CentOS Project releases rebuilds -of security updates as soon as possible. Usually within 24 hours (our -stated goal is with 72 hours, but we are usually much faster). - -The upstream vendor also releases numbered update sets for Version 3, -Version 4 and Version 5 of their product (i.e. EL 3 update 9, EL 4 -update 6 and EL 5 update 1) 2 to 4 times per year. There are new ISOs -from the upstream vendor provided for these update sets. Update sets -will be completed as soon as possible after the vendor releases their -version\ldots generally within 2 weeks. CentOS Project follows these -conventions as well, so CentOS 3.9 correlates with EL 3 update 9 and -CentOS 4.6 correlates with EL 4 update 6, CentOS 5.1 correlates to EL -5 update 1, etc. - -One thing some people have problems understanding is that if you have -any CentOS-3 product and update it, you will be updated to the latest -CentOS-3.x version. The same is true for CentOS-4 and CentOS 5. If you -update any CentOS-4 product, you will be updated to the latest -CentOS-4.x version, or to the latest CentOS 5.x version if you are -updating a CentOS 5 system. This is exactly the same behavior as the -upstream product. Let's assume that the latest EL4 product is update -6. If you install the upstream original EL4 CDs (the ones before any -update set) and upgrade via their up2date, you will have latest update -set installed (EL4 update 6 in our example). - -Since all updates within a major release (CentOS 3, CentOS 4, CentOS -5) always upgrade to the latest version when updates are performed -(thus mimicking upstream behavior), only the latest version is -maintained in each main tree on the CentOS -Mirrors\footnote{\url{http://mirrors.centos.org/}}. - -There is a CentOS Vault\footnote{\url{http://vault.centos.org/}} -containing old CentOS trees. This vault is a picture of the older tree -when it was removed from the main tree, and does not receive updates. -It should only be used for reference. - -\section{Workplace} - -\begin{itemize} -\item SVN:trunk/Identity/Logos/svg/type/2c-tmr.svg -\item SVN:trunk/Identity/Logos/svg/type/build/tmr3.svg -\item SVN:trunk/Identity/Logos/svg/type/build/tmr4.svg -\item SVN:trunk/Identity/Logos/svg/type/build/tmr5.svg -\end{itemize} - -\section{Design} - -It is very important that people differentiate which is the major -release of CentOS Distribution they are using. To achive this, we use -a special brand called \textit{The Release Brand} of CentOS -Distribution. - -There is one Release Brand for each Major Release of CentOS -Distribution. The Release Brand of CentOS Distribution is placed on -images controlling the CentOS Distribution Visual Style. - -The Release Brand of CentOS Distribution is built using two -components: 1. The CentOS Trademark, 2. The Major Release Number of -CentOS Distribution. - -The height of the Release Number is twice the CentOS Trademark height -and it is placed on the right side of CentOS Trademark, both bottom -aligned. - -Sometimes The CentOS Message can be added as third component to The -Release Brand. In these cases The CentOS Message remains on English -language, it is not translated. Because of this, The Release Brand -that includes The CentOS Message should be avoided or used in places -where there is no posibility for the user to select a different -language but English. Examples of these kind of images are Anaconda -Prompt and GRUB. - -\section{Rendering} - -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.aux b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.aux deleted file mode 100644 index d4e6ed1..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.aux +++ /dev/null @@ -1,19 +0,0 @@ -\relax -\ifx\hyper@anchor\@undefined -\global \let \oldcontentsline\contentsline -\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} -\global \let \oldnewlabel\newlabel -\gdef \newlabel#1#2{\newlabelxx{#1}#2} -\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} -\AtEndDocument{\let \contentsline\oldcontentsline -\let \newlabel\oldnewlabel} -\else -\global \let \hyper@last\relax -\fi - -\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{1}{section.1}} -\@writefile{toc}{\contentsline {section}{\numberline {2}Workplace}{2}{section.2}} -\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{2}{section.3}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}The CentOS Motif Brand}{2}{subsection.3.1}} -\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Recommendations}{2}{subsection.3.2}} -\@writefile{toc}{\contentsline {section}{\numberline {4}Rendering}{3}{section.4}} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.log b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.log deleted file mode 100644 index 88450e0..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.log +++ /dev/null @@ -1,171 +0,0 @@ -This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 1 FEB 2010 00:49 -entering extended mode -**Manual.tex -(./Manual.tex -LaTeX2e <2003/12/01> -Babel and hyphenation patterns for american, french, german, ngerman, b -ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e -stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis -h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur -kish, ukrainian, nohyphenation, loaded. -(/usr/share/texmf/tex/latex/base/article.cls -Document Class: article 2004/02/16 v1.4f Standard LaTeX document class -(/usr/share/texmf/tex/latex/base/size10.clo -File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) -) -\c@part=\count79 -\c@section=\count80 -\c@subsection=\count81 -\c@subsubsection=\count82 -\c@paragraph=\count83 -\c@subparagraph=\count84 -\c@figure=\count85 -\c@table=\count86 -\abovecaptionskip=\skip41 -\belowcaptionskip=\skip42 -\bibindent=\dimen102 -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.sty -Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX - -(/usr/share/texmf/tex/latex/graphics/keyval.sty -Package: keyval 1999/03/16 v1.13 key=value parser (DPC) -\KV@toks@=\toks14 -) -\@linkdim=\dimen103 -\Hy@linkcounter=\count87 -\Hy@pagecounter=\count88 - -(/usr/share/texmf/tex/latex/hyperref/pd1enc.def -File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) -) -(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg -File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX -) -Package hyperref Info: Hyper figures OFF on input line 1880. -Package hyperref Info: Link nesting OFF on input line 1885. -Package hyperref Info: Hyper index ON on input line 1888. -Package hyperref Info: Plain pages ON on input line 1893. -Package hyperref Info: Backreferencing OFF on input line 1900. - -Implicit mode ON; LaTeX internals redefined -Package hyperref Info: Bookmarks ON on input line 2004. -(/usr/share/texmf/tex/latex/url/url.sty -\Urlmuskip=\muskip10 -Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. -) -LaTeX Info: Redefining \url on input line 2143. -\Fld@menulength=\count89 -\Field@Width=\dimen104 -\Fld@charsize=\dimen105 -\Choice@toks=\toks15 -\Field@toks=\toks16 -Package hyperref Info: Hyper figures OFF on input line 2618. -Package hyperref Info: Link nesting OFF on input line 2623. -Package hyperref Info: Hyper index ON on input line 2626. -Package hyperref Info: backreferencing OFF on input line 2633. -Package hyperref Info: Link coloring OFF on input line 2638. -\c@Item=\count90 -\c@Hfootnote=\count91 -) -*hyperref using default driver hpdftex* -(/usr/share/texmf/tex/latex/hyperref/hpdftex.def -File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX - -(/usr/share/texmf/tex/latex/psnfss/pifont.sty -Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) -LaTeX Font Info: Try loading font information for U+pzd on input line 63. - -(/usr/share/texmf/tex/latex/psnfss/upzd.fd -File: upzd.fd 2001/06/04 font definitions for U/pzd. -) -LaTeX Font Info: Try loading font information for U+psy on input line 64. - -(/usr/share/texmf/tex/latex/psnfss/upsy.fd -File: upsy.fd 2001/06/04 font definitions for U/psy. -)) -\Fld@listcount=\count92 -\@outlinefile=\write3 -) (./Manual.aux) -\openout1 = `Manual.aux'. - -LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 10. -LaTeX Font Info: ... okay on input line 10. -LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 10. -LaTeX Font Info: ... okay on input line 10. -LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 10. -LaTeX Font Info: ... okay on input line 10. -LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 10. -LaTeX Font Info: ... okay on input line 10. -LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 10. -LaTeX Font Info: ... okay on input line 10. -LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 10. -LaTeX Font Info: ... okay on input line 10. -LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 10. -LaTeX Font Info: ... okay on input line 10. -Package hyperref Info: Link coloring OFF on input line 10. - -(/usr/share/texmf/tex/latex/hyperref/nameref.sty -Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section -\c@section@level=\count93 -) -LaTeX Info: Redefining \ref on input line 10. -LaTeX Info: Redefining \pageref on input line 10. - (./Manual.out) (./Manual.out) -\openout3 = `Manual.out'. - -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <12> on input line 13. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <8> on input line 13. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <6> on input line 13. -(./Manual.toc -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <7> on input line 4. -LaTeX Font Info: External font `cmex10' loaded for size -(Font) <5> on input line 4. -) -\tf@toc=\write4 -\openout4 = `Manual.toc'. - - [1 - -{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] -LaTeX Font Info: Try loading font information for OMS+cmr on input line 78. - -(/usr/share/texmf/tex/latex/base/omscmr.fd -File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions -) -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available -(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 78. - -Overfull \hbox (70.63863pt too wide) in paragraph at lines 101--104 -\OT1/cmr/m/n/10 Cen-tOS Palette is avail-able at SVN:trunk/Identity/Themes/Mode -rn/Palettes/Default.gpl. - [] - -[2] [3] (./Manual.aux) ) -Here is how much of TeX's memory you used: - 1964 strings out of 94500 - 26838 string characters out of 1176766 - 75178 words of memory out of 1000000 - 5143 multiletter control sequences out of 10000+50000 - 10065 words of font info for 35 fonts, out of 500000 for 2000 - 580 hyphenation exceptions out of 1000 - 27i,8n,36p,148b,214s stack positions out of 1500i,500n,5000p,200000b,5000s -PDF statistics: - 96 PDF objects out of 300000 - 12 named destinations out of 131072 - 65 words of extra memory for PDF output out of 65536 - -Output written on Manual.pdf (3 pages, 90737 bytes). diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.out b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.out deleted file mode 100644 index 2a281ab..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.out +++ /dev/null @@ -1,6 +0,0 @@ -\BOOKMARK [1][-]{section.1}{Introduction}{} -\BOOKMARK [1][-]{section.2}{Workplace}{} -\BOOKMARK [1][-]{section.3}{Design}{} -\BOOKMARK [2][-]{subsection.3.1}{The CentOS Motif Brand}{section.3} -\BOOKMARK [2][-]{subsection.3.2}{Recommendations}{section.3} -\BOOKMARK [1][-]{section.4}{Rendering}{} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.pdf b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.pdf deleted file mode 100644 index 4615239..0000000 Binary files a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.toc b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.toc deleted file mode 100644 index 3aa28c6..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/Manual.toc +++ /dev/null @@ -1,6 +0,0 @@ -\contentsline {section}{\numberline {1}Introduction}{1}{section.1} -\contentsline {section}{\numberline {2}Workplace}{2}{section.2} -\contentsline {section}{\numberline {3}Design}{2}{section.3} -\contentsline {subsection}{\numberline {3.1}The CentOS Motif Brand}{2}{subsection.3.1} -\contentsline {subsection}{\numberline {3.2}Recommendations}{2}{subsection.3.2} -\contentsline {section}{\numberline {4}Rendering}{3}{section.4} diff --git a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/manual.tex b/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/manual.tex deleted file mode 100644 index fef6047..0000000 --- a/Manuals/Filesystem/filesystem-latex/Identity/Themes/Motif/manual.tex +++ /dev/null @@ -1,124 +0,0 @@ -% -% Describe The CentOS Motif. -% -\documentclass{article} -\usepackage{hyperref} - -\title{The CentOS Motif} -\author{Alain Reguera Delgado} - -\begin{document} - -\maketitle - -\begin{abstract} -This manual describes the workplace, design, and rendering of CentOS -Artistic Motifs, both default and alternatives. -\end{abstract} - -\tableofcontents - -\section{Introduction} - -The CentOS Artistic Motif is an image used to enforce the CentOS -Project Visual Identity. The Artistic Motif is a pattern design used -to define the CentOS Visual Style. - -Due to our Monolithic Visual Structure, the CentOS Project's Visual -Identity is attached to one unique Visual Style, that is the CentOS -Default Visual Style. CentOS Default Visual Style is based on one -unique CentOS Artistic Motif, that is the CentOS Default Artistic -Motif. - -Changing the CentOS Default Visual Style is not very convenient -because that affects the ``recognition'' of CentOS Project. -Nevertheless, we want to see what do you have. Specially if your work -is an improvement to the base idea of CentOS Default Visual Style -(\emph{\textbf{Modern}, squares and circles flowing up.}). - -Additionally to the CentOS Default Artistic Motif, there are CentOS -Alternative Motifs. CentOS Alternative Motifs may or may not be -related with the current CentOS Default Artistic Motif. CentOS -Alternative Motfis are an space for new art creation, for designing -new and completely exiting artistic ideas. This place doesn't pretend -to replace sites like devianart.org, but to collect Artistic Motifs -focused on The CentOS Project and what it is. - -If you are not happy with the actual CentOS Default Artistic Motif, -you can look inside CentOS Alternative Motifs and if someone is -interesting enough you can download it from the CentOS Artwork -Repository and test it. If it turns popular enough it has posibilities -of become the CentOS Default Artistic Motif and by extension the -CentOS Default Visual Style. - -If you are not happy with CentOS Alternative Motifs either, then go an -design your own CentOS Alternative Artistic Moif and propose it in -\href{mailto:centos-devel@centos.org}{centos-devel@centos.org}. - -CentOS Default Artistic Motif and CentOS Alternative Motifs are -maintain by CentOS Community People. Generally, one person proposes -the first idea, later others join the effort to make that idea better. -The first person who proposes the idea is known as the Motif Author -and is she/he who owns the copyright of that work. People joinning the -effort are known as Motif Contributors. - -The CentOS Project is using the Creative Common Share-Alike -License\footnote{http://creativecommons.org/licenses/by-sa/3.0/} in -both CentOS Default Artistic Motif and CentOS Alternative Motifs. This -is, in order to brand an Artistic Motif as CentOS Motif, her/his -author should release her/his work under the previously mentioned -license. - -Only Artistic Motifs branded as CentOS Motif, both Default and -Alternatives, are hosted on CentOS Artwork Repository. - -\section{Workplace} - -\begin{itemize} -\item SVN:trunk/Identity/Themes/\$THEME/Motif/ -\item SVN:trunk/Manuals/Identity/Themes/Motif/ -\end{itemize} - -\section{Design} - -\subsection{The CentOS Motif Brand} - -\subsection{Recommendations} - -When designing Motifs for CentOS, consider the following -recommendations: - -\begin{itemize} - -\item Give a unique (case-sensitive) name to your Motif. This name is -used as value wherever \$THEME variable is. Optionally, you can add a -description about inspiration and concepts behind your work. - -\item Use the location SVN:trunk/Identity/Themes/\$THEME/Motif/ to -store your work. If it doesn't exist create it. Note that this require -you to have previous commit access in CentOS Artwork Repository. - -\item Use the CentOS Default Artistic Motif's Palette as base to your -work. CentOS Palette is available at -SVN:trunk/Identity/Themes/Modern/Palettes/Default.gpl. - -\item Make your work completely vectorial. Do not add raster images -inside it. - -\item Feel free to make your art enterprise-level and beautiful. - -\item Add the following information on your artwork (both in a visible -design area, and inside inkscape document metadata section wherever it -be possible): - -\begin{itemize} -\item The CentOS Motif Brand. -\item The name of your artistic motif. -\item The copyright sentence: \texttt{Copyright (C) YEAR YOURNAME} -\item The license under which the work is released. -\end{itemize} -\end{itemize} - -\section{Rendering} - -\end{document} diff --git a/Manuals/Filesystem/filesystem-latex/Licenses/centos-redistribution.tex b/Manuals/Filesystem/filesystem-latex/Licenses/centos-redistribution.tex deleted file mode 100644 index b4adf87..0000000 --- a/Manuals/Filesystem/filesystem-latex/Licenses/centos-redistribution.tex +++ /dev/null @@ -1,51 +0,0 @@ -% -% CentOS Redistribution License. -% -\chapter{CentOS Redistribution License} -\noindent Revision 1.0, March 2010\\ -\noindent Copyright \copyright\ 2010 The CentOS Project.\\ -\\ -\noindent The \texttt{redhat-logos} and \texttt{redhat-artwork} -packages (the ``Packages'') contain image files which incorporate the -CentOS trademark, and CentOS logo (the ``Marks''). - -The CentOS Project grants you the right to use the Packages during the -normal operation of other software programs that call upon the -Packages. The CentOS Project grants to you the right and license to -copy and redistribute the unaltered Packages for both commerical and -non-commercial purposes. - -If you are rebranding or modifying the underlying distribution, or the -Packages, you must remove ``the Marks'' and rename the distribution -something other than CentOS. - -When redistributing using this license, the following applies: - -\begin{enumerate} - -\item The above copyright notice and this license are included with -each copy you make, and they remain intact and are not altered, -deleted, or modified in any way; - -\item You do not modify the appearance of any or all of the Logos in -any manner; and - -\item You do not use any or all of the Logos as, or as part of, a -trademark, trade name, or trade identifier; or in any other fashion -except as set forth in this license. - -\item No Warranty. The Packages are provided ``as are'' and any -express or implied warranties, including, but not limited to, the -implied warranties of merchantability and fitness for a particular -purpose are disclaimed. In no event shall the CentOS Project be liable -for any direct, indirect, incidental, special, exemplary, or -consequential damages ---including, but not limited to, procurement of -substitute goods or services; loss of use, data or profits; or -business interruption--- however caused and on any theory of -liability, whether in contract, strict liability, or tort ---including -negligence or otherwise--- arising in any way out of the use of this -package, even if advised of the possibility of such damage. - -\end{enumerate} - - diff --git a/Manuals/Filesystem/filesystem-latex/Licenses/gfdl.tex b/Manuals/Filesystem/filesystem-latex/Licenses/gfdl.tex deleted file mode 100644 index 60e6413..0000000 --- a/Manuals/Filesystem/filesystem-latex/Licenses/gfdl.tex +++ /dev/null @@ -1,437 +0,0 @@ -% Verbatim copy of GNU Free Documentation License. The License under -% which this document is released. -\chapter{GNU Free Documentation License} -\hypertarget{cha:Licenses:GFDL}{} -\label{cha:Licenses:GFDL} - -Version 1.2, November 2002 -\\ -\\ -Copyright \copyright\ 2000,2001,2002 Free Software Foundation, Inc. -\\ -59 Temple Place, Suite 330, Boston, MA 02111-1307, USA -\\ -Everyone is permitted to copy and distribute verbatim copies of this -license document, but changing it is not allowed. - -\section*{Preamble} -\label{sec:License-GFDL-0} - -The purpose of this License is to make a manual, textbook, or other -functional and useful document ``free'' in the sense of freedom: to -assure everyone the effective freedom to copy and redistribute it, -with or without modifying it, either commercially or noncommercially. -Secondarily, this License preserves for the author and publisher a way -to get credit for their work, while not being considered responsible -for modifications made by others. - -This License is a kind of ``copyleft'', which means that derivative -works of the document must themselves be free in the same sense. It -complements the GNU General Public License, which is a copyleft -license designed for free software. - -We have designed this License in order to use it for manuals for free -software, because free software needs free documentation: a free -program should come with manuals providing the same freedoms that the -software does. But this License is not limited to software manuals; -it can be used for any textual work, regardless of subject matter or -whether it is published as a printed book. We recommend this License -principally for works whose purpose is instruction or reference. - -\section{Applicability And Definitions} -\label{sec:License-GFDL-1} - -This License applies to any manual or other work, in any medium, that -contains a notice placed by the copyright holder saying it can be -distributed under the terms of this License. Such a notice grants a -world-wide, royalty-free license, unlimited in duration, to use that -work under the conditions stated herein. The ``Document'', below, -refers to any such manual or work. Any member of the public is a -licensee, and is addressed as ``you''. You accept the license if you -copy, modify or distribute the work in a way requiring permission -under copyright law. - -A ``Modified Version'' of the Document means any work containing the -Document or a portion of it, either copied verbatim, or with -modifications and/or translated into another language. - -A ``Secondary Section'' is a named appendix or a front-matter section of -the Document that deals exclusively with the relationship of the -publishers or authors of the Document to the Document's overall -subject (or to related matters) and contains nothing that could fall -directly within that overall subject. (Thus, if the Document is in -part a textbook of mathematics, a Secondary Section may not explain -any mathematics.) The relationship could be a matter of historical -connection with the subject or with related matters, or of legal, -commercial, philosophical, ethical or political position regarding -them. - -The ``Invariant Sections'' are certain Secondary Sections whose titles -are designated, as being those of Invariant Sections, in the notice -that says that the Document is released under this License. If a -section does not fit the above definition of Secondary then it is not -allowed to be designated as Invariant. The Document may contain zero -Invariant Sections. If the Document does not identify any Invariant -Sections then there are none. - -The ``Cover Texts'' are certain short passages of text that are listed, -as Front-Cover Texts or Back-Cover Texts, in the notice that says that -the Document is released under this License. A Front-Cover Text may -be at most 5 words, and a Back-Cover Text may be at most 25 words. - -A ``Transparent'' copy of the Document means a machine-readable copy, -represented in a format whose specification is available to the -general public, that is suitable for revising the document -straightforwardly with generic text editors or (for images composed of -pixels) generic paint programs or (for drawings) some widely available -drawing editor, and that is suitable for input to text formatters or -for automatic translation to a variety of formats suitable for input -to text formatters. A copy made in an otherwise Transparent file -format whose markup, or absence of markup, has been arranged to thwart -or discourage subsequent modification by readers is not Transparent. -An image format is not Transparent if used for any substantial amount -of text. A copy that is not ``Transparent'' is called ``Opaque''. - -Examples of suitable formats for Transparent copies include plain -ASCII without markup, Texinfo input format, \LaTeX\ input format, SGML -or XML using a publicly available DTD, and standard-conforming simple -HTML, PostScript or PDF designed for human modification. Examples of -transparent image formats include PNG, XCF and JPG. Opaque formats -include proprietary formats that can be read and edited only by -proprietary word processors, SGML or XML for which the DTD and/or -processing tools are not generally available, and the -machine-generated HTML, PostScript or PDF produced by some word -processors for output purposes only. - -The ``Title Page'' means, for a printed book, the title page itself, -plus such following pages as are needed to hold, legibly, the material -this License requires to appear in the title page. For works in -formats which do not have any title page as such, ``Title Page'' means -the text near the most prominent appearance of the work's title, -preceding the beginning of the body of the text. - -A section ``Entitled XYZ'' means a named subunit of the Document whose -title either is precisely XYZ or contains XYZ in parentheses following -text that translates XYZ in another language. (Here XYZ stands for a -specific section name mentioned below, such as ``Acknowledgements'', -``Dedications'', ``Endorsements'', or ``History''.) To ``Preserve the -Title'' of such a section when you modify the Document means that it -remains a section ``Entitled XYZ'' according to this definition. - -The Document may include Warranty Disclaimers next to the notice which -states that this License applies to the Document. These Warranty -Disclaimers are considered to be included by reference in this -License, but only as regards disclaiming warranties: any other -implication that these Warranty Disclaimers may have is void and has -no effect on the meaning of this License. - -\section{Verbatim Copying} -\label{sec:License-GFDL-2} - -You may copy and distribute the Document in any medium, either -commercially or noncommercially, provided that this License, the -copyright notices, and the license notice saying this License applies -to the Document are reproduced in all copies, and that you add no -other conditions whatsoever to those of this License. You may not use -technical measures to obstruct or control the reading or further -copying of the copies you make or distribute. However, you may accept -compensation in exchange for copies. If you distribute a large enough -number of copies you must also follow the conditions in section -\ref{sec:License-GFDL-3}. - -You may also lend copies, under the same conditions stated above, and -you may publicly display copies. - -\section{Copying In Quantity} -\label{sec:License-GFDL-3} - -If you publish printed copies (or copies in media that commonly have -printed covers) of the Document, numbering more than 100, and the -Document's license notice requires Cover Texts, you must enclose the -copies in covers that carry, clearly and legibly, all these Cover -Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on -the back cover. Both covers must also clearly and legibly identify -you as the publisher of these copies. The front cover must present -the full title with all words of the title equally prominent and -visible. You may add other material on the covers in addition. -Copying with changes limited to the covers, as long as they preserve -the title of the Document and satisfy these conditions, can be treated -as verbatim copying in other respects. - -If the required texts for either cover are too voluminous to fit -legibly, you should put the first ones listed (as many as fit -reasonably) on the actual cover, and continue the rest onto adjacent -pages. - -If you publish or distribute Opaque copies of the Document numbering -more than 100, you must either include a machine-readable Transparent -copy along with each Opaque copy, or state in or with each Opaque copy -a computer-network location from which the general network-using -public has access to download using public-standard network protocols -a complete Transparent copy of the Document, free of added material. -If you use the latter option, you must take reasonably prudent steps, -when you begin distribution of Opaque copies in quantity, to ensure -that this Transparent copy will remain thus accessible at the stated -location until at least one year after the last time you distribute an -Opaque copy (directly or through your agents or retailers) of that -edition to the public. - -It is requested, but not required, that you contact the authors of the -Document well before redistributing any large number of copies, to -give them a chance to provide you with an updated version of the -Document. - -\section{Modifications} -\label{sec:License-GFDL-4} - -You may copy and distribute a Modified Version of the Document under -the conditions of sections \ref{sec:License-GFDL-2} and -\ref{sec:License-GFDL-3} above, provided that you release the Modified -Version under precisely this License, with the Modified Version -filling the role of the Document, thus licensing distribution and -modification of the Modified Version to whoever possesses a copy of -it. In addition, you must do these things in the Modified Version: - -\begin{itemize} - -\item [A.] Use in the Title Page (and on the covers, if any) a title -distinct from that of the Document, and from those of previous -versions (which should, if there were any, be listed in the History -section of the Document). You may use the same title as a previous -version if the original publisher of that version gives permission. - -\item [B.] List on the Title Page, as authors, one or more persons or -entities responsible for authorship of the modifications in the -Modified Version, together with at least five of the principal authors -of the Document (all of its principal authors, if it has fewer than -five), unless they release you from this requirement. - -\item [C.] State on the Title page the name of the publisher of the -Modified Version, as the publisher. - -\item [D.] Preserve all the copyright notices of the Document. - -\item [E.] Add an appropriate copyright notice for your modifications -adjacent to the other copyright notices. - -\item [F.] Include, immediately after the copyright notices, a license -notice giving the public permission to use the Modified Version under -the terms of this License, in the form shown in the Addendum below. - -\item [G.] Preserve in that license notice the full lists of Invariant -Sections and required Cover Texts given in the Document's license -notice. - -\item [H.] Include an unaltered copy of this License. - -\item [I.] Preserve the section Entitled ``History'', Preserve its -Title, and add to it an item stating at least the title, year, new -authors, and publisher of the Modified Version as given on the Title -Page. If there is no section Entitled ``History'' in the Document, -create one stating the title, year, authors, and publisher of the -Document as given on its Title Page, then add an item describing the -Modified Version as stated in the previous sentence. - -\item [J.] Preserve the network location, if any, given in the -Document for public access to a Transparent copy of the Document, and -likewise the network locations given in the Document for previous -versions it was based on. These may be placed in the ``History'' -section. You may omit a network location for a work that was -published at least four years before the Document itself, or if the -original publisher of the version it refers to gives permission. - -\item [K.] For any section Entitled ``Acknowledgements'' or -``Dedications'', Preserve the Title of the section, and preserve in -the section all the substance and tone of each of the contributor -acknowledgements and/or dedications given therein. - -\item [L.] Preserve all the Invariant Sections of the Document, -unaltered in their text and in their titles. Section numbers or the -equivalent are not considered part of the section titles. - -\item [M.] Delete any section Entitled ``Endorsements''. Such a -section may not be included in the Modified Version. - -\item [N.] Do not retitle any existing section to be Entitled -``Endorsements'' or to conflict in title with any Invariant Section. - -\item [O.] Preserve any Warranty Disclaimers. -\end{itemize} - -If the Modified Version includes new front-matter sections or -appendices that qualify as Secondary Sections and contain no material -copied from the Document, you may at your option designate some or all -of these sections as invariant. To do this, add their titles to the -list of Invariant Sections in the Modified Version's license notice. -These titles must be distinct from any other section titles. - -You may add a section Entitled ``Endorsements'', provided it contains -nothing but endorsements of your Modified Version by various -parties--for example, statements of peer review or that the text has -been approved by an organization as the authoritative definition of a -standard. - -You may add a passage of up to five words as a Front-Cover Text, and a -passage of up to 25 words as a Back-Cover Text, to the end of the list -of Cover Texts in the Modified Version. Only one passage of -Front-Cover Text and one of Back-Cover Text may be added by (or -through arrangements made by) any one entity. If the Document already -includes a cover text for the same cover, previously added by you or -by arrangement made by the same entity you are acting on behalf of, -you may not add another; but you may replace the old one, on explicit -permission from the previous publisher that added the old one. - -The author(s) and publisher(s) of the Document do not by this License -give permission to use their names for publicity for or to assert or -imply endorsement of any Modified Version. - -\section{Combining Documents} -\label{sec:License-GFDL-5} - -You may combine the Document with other documents released under this -License, under the terms defined in section \ref{sec:License-GFDL-4} -above for modified versions, provided that you include in the -combination all of the Invariant Sections of all of the original -documents, unmodified, and list them all as Invariant Sections of your -combined work in its license notice, and that you preserve all their -Warranty Disclaimers. - -The combined work need only contain one copy of this License, and -multiple identical Invariant Sections may be replaced with a single -copy. If there are multiple Invariant Sections with the same name but -different contents, make the title of each such section unique by -adding at the end of it, in parentheses, the name of the original -author or publisher of that section if known, or else a unique number. -Make the same adjustment to the section titles in the list of -Invariant Sections in the license notice of the combined work. - -In the combination, you must combine any sections Entitled ``History'' -in the various original documents, forming one section Entitled -``History''; likewise combine any sections Entitled -``Acknowledgements'', -and any sections Entitled ``Dedications''. You must delete all sections -Entitled ``Endorsements''. - -\section{Collections Of Documents} -\label{sec:License-GFDL-6} - -You may make a collection consisting of the Document and other -documents released under this License, and replace the individual -copies of this License in the various documents with a single copy -that is included in the collection, provided that you follow the rules -of this License for verbatim copying of each of the documents in all -other respects. - -You may extract a single document from such a collection, and -distribute it individually under this License, provided you insert a -copy of this License into the extracted document, and follow this -License in all other respects regarding verbatim copying of that -document. - -\section{Aggregation With Independent Works} -\label{sec:License-GFDL-7} - -A compilation of the Document or its derivatives with other separate -and independent documents or works, in or on a volume of a storage or -distribution medium, is called an ``aggregate'' if the copyright -resulting from the compilation is not used to limit the legal rights -of the compilation's users beyond what the individual works permit. -When the Document is included in an aggregate, this License does not -apply to the other works in the aggregate which are not themselves -derivative works of the Document. - -If the Cover Text requirement of section \ref{sec:License-GFDL-3} is -applicable to these copies of the Document, then if the Document is -less than one half of the entire aggregate, the Document's Cover Texts -may be placed on covers that bracket the Document within the -aggregate, or the electronic equivalent of covers if the Document is -in electronic form. Otherwise they must appear on printed covers that -bracket the whole aggregate. - -\section{Translation} -\label{sec:License-GFDL-8} - -Translation is considered a kind of modification, so you may -distribute translations of the Document under the terms of section -\ref{sec:License-GFDL-4}. Replacing Invariant Sections with -translations requires special permission from their copyright holders, -but you may include translations of some or all Invariant Sections in -addition to the original versions of these Invariant Sections. You -may include a translation of this License, and all the license notices -in the Document, and any Warranty Disclaimers, provided that you also -include the original English version of this License and the original -versions of those notices and disclaimers. In case of a disagreement -between the translation and the original version of this License or a -notice or disclaimer, the original version will prevail. - -If a section in the Document is Entitled ``Acknowledgements'', -``Dedications'', or ``History'', the requirement (section -\ref{sec:License-GFDL-4}) to Preserve its Title (section -\ref{sec:License-GFDL-1}) will typically require changing the actual -title. - -\section{Termination} -\label{sec:License-GFDL-9} - -You may not copy, modify, sublicense, or distribute the Document -except as expressly provided for under this License. Any other -attempt to copy, modify, sublicense or distribute the Document is -void, and will automatically terminate your rights under this License. -However, parties who have received copies, or rights, from you under -this License will not have their licenses terminated so long as such -parties remain in full compliance. - -\section{Future Revisions Of This License} -\label{sec:License-GFDL-10} - -The Free Software Foundation may publish new, revised versions of the -GNU Free Documentation License from time to time. Such new versions -will be similar in spirit to the present version, but may differ in -detail to address new problems or concerns. See -\url{http://www.gnu.org/copyleft/}. - -Each version of the License is given a distinguishing version number. -If the Document specifies that a particular numbered version of this -License ``or any later version'' applies to it, you have the option of -following the terms and conditions either of that specified version or -of any later version that has been published (not as a draft) by the -Free Software Foundation. If the Document does not specify a version -number of this License, you may choose any version ever published (not -as a draft) by the Free Software Foundation. - -\section{How to use this License for your documents} -\label{sec:License-GFDL-11} - -To use this License in a document you have written, include a copy of -the License in the document and put the following copyright and -license notices just after the title page: - -\begin{verbatim} - Copyright (C) YEAR YOUR NAME. - - Permission is granted to copy, distribute and/or modify this - document under the terms of the GNU Free Documentation License, - Version 1.2 or any later version published by the Free Software - Foundation; with no Invariant Sections, no Front-Cover Texts, - and no Back-Cover Texts. A copy of the license is included in - the section entitled ``GNU Free Documentation License''. -\end{verbatim} - -If you have Invariant Sections, Front-Cover Texts and Back-Cover -Texts, replace the ``with...Texts''. line with this: - -\begin{verbatim} - with the Invariant Sections being LIST THEIR TITLES, with the - Front-Cover Texts being LIST, and with the Back-Cover Texts - being LIST. -\end{verbatim} - -If you have Invariant Sections without Cover Texts, or some other -combination of the three, merge those two alternatives to suit the -situation. - -If your document contains nontrivial examples of program code, we -recommend releasing these examples in parallel under your choice of -free software license, such as the GNU General Public License, to -permit their use in free software. - diff --git a/Manuals/Filesystem/filesystem-latex/Translations/iso639.tex b/Manuals/Filesystem/filesystem-latex/Translations/iso639.tex deleted file mode 100644 index 307e14f..0000000 --- a/Manuals/Filesystem/filesystem-latex/Translations/iso639.tex +++ /dev/null @@ -1,564 +0,0 @@ -\chapter{ISO 639 Language Codes} -\label{cha:Appendix:ISO639} - -The ISO 639 standard defines two character codes for many languages. -All abbreviations for languages used in the Translation Project should -come from this standard. - -\begin{description} -\item[aa] -Afar. - -\item[ab] -Abkhazian. - -\item[ae] -Avestan. - -\item[af] -Afrikaans. - -\item[ak] -Akan. - -\item[am] -Amharic. - -\item[an] -Aragonese. - -\item[ar] -Arabic. - -\item[as] -Assamese. - -\item[av] -Avaric. - -\item[ay] -Aymara. - -\item[az] -Azerbaijani. - -\item[ba] -Bashkir. - -\item[be] -Byelorussian; Belarusian. - -\item[bg] -Bulgarian. - -\item[bh] -Bihari. - -\item[bi] -Bislama. - -\item[bm] -Bambara. - -\item[bn] -Bengali; Bangla. - -\item[bo] -Tibetan. - -\item[br] -Breton. - -\item[bs] -Bosnian. - -\item[ca] -Catalan. - -\item[ce] -Chechen. - -\item[ch] -Chamorro. - -\item[co] -Corsican. - -\item[cr] -Cree. - -\item[cs] -Czech. - -\item[cu] -Church Slavic. - -\item[cv] -Chuvash. - -\item[cy] -Welsh. - -\item[da] -Danish. - -\item[de] -German. - -\item[dv] -Divehi. - -\item[dz] -Dzongkha; Bhutani. - -\item[ee] -E'we'. - -\item[el] -Greek. - -\item[en] -English. - -\item[eo] -Esperanto. - -\item[es] -Spanish. - -\item[et] -Estonian. - -\item[eu] -Basque. - -\item[fa] -Persian. - -\item[ff] -Fulah. - -\item[fi] -Finnish. - -\item[fj] -Fijian; Fiji. - -\item[fo] -Faroese. - -\item[fr] -French. - -\item[fy] -Frisian. - -\item[ga] -Irish. - -\item[gd] -Scots; Gaelic. - -\item[gl] -Gallegan; Galician. - -\item[gn] -Guarani. - -\item[gu] -Gujarati. - -\item[gv] -Manx. - -\item[ha] -Hausa (?). - -\item[he] -Hebrew (formerly iw). - -\item[hi] -Hindi. - -\item[ho] -Hiri Motu. - -\item[hr] -Croatian. - -\item[ht] -Haitian; Haitian Creole. - -\item[hu] -Hungarian. - -\item[hy] -Armenian. - -\item[hz] -Herero. - -\item[ia] -Interlingua. - -\item[id] -Indonesian (formerly in). - -\item[ie] -Interlingue. - -\item[ig] -Igbo. - -\item[ii] -Sichuan Yi. - -\item[ik] -Inupiak. - -\item[io] -Ido. - -\item[is] -Icelandic. - -\item[it] -Italian. - -\item[iu] -Inuktitut. - -\item[ja] -Japanese. - -\item[jv] -Javanese. - -\item[ka] -Georgian. - -\item[kg] -Kongo. - -\item[ki] -Kikuyu. - -\item[kj] -Kuanyama. - -\item[kk] -Kazakh. - -\item[kl] -Kalaallisut; Greenlandic. - -\item[km] -Khmer; Cambodian. - -\item[kn] -Kannada. - -\item[ko] -Korean. - -\item[kr] -Kanuri. - -\item[ks] -Kashmiri. - -\item[ku] -Kurdish. - -\item[kv] -Komi. - -\item[kw] -Cornish. - -\item[ky] -Kirghiz. - -\item[la] -Latin. - -\item[lb] -Letzeburgesch. - -\item[lg] -Ganda. - -\item[li] -Limburgish; Limburger; Limburgan. - -\item[ln] -Lingala. - -\item[lo] -Lao; Laotian. - -\item[lt] -Lithuanian. - -\item[lu] -Luba-Katanga. - -\item[lv] -Latvian; Lettish. - -\item[mg] -Malagasy. - -\item[mh] -Marshall. - -\item[mi] -Maori. - -\item[mk] -Macedonian. - -\item[ml] -Malayalam. - -\item[mn] -Mongolian. - -\item[mo] -Moldavian. - -\item[mr] -Marathi. - -\item[ms] -Malay. - -\item[mt] -Maltese. - -\item[my] -Burmese. - -\item[na] -Nauru. - -\item[nb] -Norwegian Bokmaal. - -\item[nd] -Ndebele, North. - -\item[ne] -Nepali. - -\item[ng] -Ndonga. - -\item[nl] -Dutch. - -\item[nn] -Norwegian Nynorsk. - -\item[no] -Norwegian. - -\item[nr] -Ndebele, South. - -\item[nv] -Navajo. - -\item[ny] -Chichewa; Nyanja. - -\item[oc] -Occitan; Provenc,al. - -\item[oj] -Ojibwa. - -\item[om] -(Afan) Oromo. - -\item[or] -Oriya. - -\item[os] -Ossetian; Ossetic. - -\item[pa] -Panjabi; Punjabi. - -\item[pi] -Pali. - -\item[pl] -Polish. - -\item[ps] -Pashto, Pushto. - -\item[pt] -Portuguese. - -\item[qu] -Quechua. - -\item[rm] -Rhaeto-Romance. - -\item[rn] -Rundi; Kirundi. - -\item[ro] -Romanian. - -\item[ru] -Russian. - -\item[rw] -Kinyarwanda. - -\item[sa] -Sanskrit. - -\item[sc] -Sardinian. - -\item[sd] -Sindhi. - -\item[se] -Northern Sami. - -\item[sg] -Sango; Sangro. - -\item[si] -Sinhalese. - -\item[sk] -Slovak. - -\item[sl] -Slovenian. - -\item[sm] -Samoan. - -\item[sn] -Shona. - -\item[so] -Somali. - -\item[sq] -Albanian. - -\item[sr] -Serbian. - -\item[ss] -Swati; Siswati. - -\item[st] -Sesotho; Sotho, Southern. - -\item[su] -Sundanese. - -\item[sv] -Swedish. - -\item[sw] -Swahili. - -\item[ta] -Tamil. - -\item[te] -Telugu. - -\item[tg] -Tajik. - -\item[th] -Thai. - -\item[ti] -Tigrinya. - -\item[tk] -Turkmen. - -\item[tl] -Tagalog. - -\item[tn] -Tswana; Setswana. - -\item[to] -Tonga (?). - -\item[tr] -Turkish. - -\item[ts] -Tsonga. - -\item[tt] -Tatar. - -\item[tw] -Twi. - -\item[ty] -Tahitian. - -\item[ug] -Uighur. - -\item[uk] -Ukrainian. - -\item[ur] -Urdu. - -\item[uz] -Uzbek. - -\item[ve] -Venda. - -\item[vi] -Vietnamese. - -\item[vo] -Volapu"k; Volapuk. - -\item[wa] -Walloon. - -\item[wo] -Wolof. - -\item[xh] -Xhosa. - -\item[yi] -Yiddish (formerly ji). - -\item[yo] -Yoruba. - -\item[za] -Zhuang. - -\item[zh] -Chinese. - -\item[zu] -Zulu. -\end{description} - diff --git a/Manuals/Filesystem/filesystem-latex/Workstation/configuration.tex b/Manuals/Filesystem/filesystem-latex/Workstation/configuration.tex deleted file mode 100644 index ecfc67d..0000000 --- a/Manuals/Filesystem/filesystem-latex/Workstation/configuration.tex +++ /dev/null @@ -1,180 +0,0 @@ -% Part : Preparing Your Workstation -% Chapter: Configuration -% ------------------------------------------------------------ -% $Id: configuration.tex 6191 2010-08-02 02:36:14Z al $ -% ------------------------------------------------------------ - -This chapter describes configurations you need to set up before using -CentOS Artwork Repository. - -\section{Firewall} - -The CentOS Artwork Repository lives on the following URL: - -\begin{quote} -https://projects.centos.org/svn/artwork/ -\end{quote} - -To reach this location you need to have Internet access and be sure no -rule in your firewall is denying this site. Note that the URL uses the -SSL protocol (port 443). - -\section{Subversion Behind Squid} - -Sometimes it is convenient to proxy Subversion client's requests -through a proxy-cache server like Squid. In cases like this, the Squid -proxy server is in the middle between you and CentOS Artwork -Repository. If you want to proxy Subversion client's requests through -Squid proxy-cache server, you need to configure your Subversion client -and your Squid proxy server to do so. - -\subsection{Subversion Client Configuration} - -Subversion client needs to be configured to send requests to your -Squid proxy-cache server. This configuration takes place in the file -\texttt{$\sim$/.subversion/servers}. - -\subsection{Squid Server Configuration} - -Squid proxy-cache server needs to be configured to accept the -extension methods \texttt{REPORT MERGE MKACTIVITY CHECKOUT MKCOL}. -This configuration takes place in the file -\texttt{/etc/squid/squid.conf}, specifically in the configuration tag -illustrated in \autoref{fig:Workstation:Configuration:Squid}. - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -# TAG: extension_methods -# Squid only knows about standardized HTTP request methods. -# You can add up to 20 additional "extension" methods here. -# -#Default: -# none -extension_methods REPORT MERGE MKACTIVITY CHECKOUT MKCOL -\end{verbatim} -\hrulefill -\caption{Squid configuration to proxy Subversion client's requests.% - \label{fig:Workstation:Configuration:Squid}} -\end{figure} - -\section{Working Copy} - -A Subversion working copy is an ordinary directory tree on your local -system, containing a collection of files (i.e. Translations, Designs, -Manuals, and Scripts). You can edit these files however you wish. Your -working copy is your own private work area: Subversion will never -incorporate other people's changes, nor make your own changes -available to others, until you explicitly tell it to do so. You can -even have multiple working copies of the same project.\footnote{Even -this is basically correct, doing so when using CentOS Artowrk -Repository can bring some confusion when executing scripts. Presently, -only one absolute path can be defined as absolute path for scripts' -execution. You can have as many working copies of CentOS Artwork -Repository as you want but scripts will be executed from just one -working copy absolute path. That is, the one stored under -\texttt{/home/centos/artwork/}}. - -Once you've made some changes to your working copy files and verified -that they work properly, Subversion provides you with commands to -``publish'' your changes to the other people working with you on your -project (by writing to the repository). If other people publish their -own changes, Subversion provides you with commands to merge those -changes into your working directory (by reading from the repository). - -\begin{figure}[!hbp] -\hrulefill -\begin{verbatim} -svn co https://projects.centos.org/svn/artwork /home/centos/ -\end{verbatim} -\hrulefill -\caption{Subversion command used to download the working copy.% - \label{fig:Workstation:WC:Download}} -\end{figure} - -The subversion command illustrated in -\autoref{fig:Workstation:WC:Download} brings a CentOS Artwork -Repository working copy down to your workstation, specifically to your -home directory (\texttt{/home/centos/artwork/}). This process may take -some time. Once the working copy is available in your workstation, -you are ready to start exploring and improving available works. - -Note that you need to have a username called \texttt{centos} in your -system. If you don't have it, you can create it using the comand -\texttt{useradd} as superuser (\texttt{root}). - -\subsection{Standardizing Absolute Path} - -When using Inkscape to import raster images inside SVG files the -absolute image path is required. If everyone stores the working copy -on a different absolute path imported images will not be loaded in -those location different from those they were conceived. There is no -way to find the right absolute image path but defining a convenction -about it. - -On a path string (e.g., /home/centos/artwork/trunk/) the username -(`centos') is the variable component, so it is the component we need -to standardize--in the sake of keeping the working copy inside user's -/home/ structure. Thus, analysing which username to use, the CentOS -Project is what join us all together, so the `centos' word in -lower-case seems to be a nice choise for us to use as common username. - -\section{User Identification} - -At this point you probably have made some changes inside your working -copy and wish to publish them. To publish your changes on CentOS -Artwork Repository you need to have a registered account with commit -privilege in CentOS Artwork Repository. - -If you are new in CentOS Artwork Repository it is possible that you -can't commit your changes. That is because new registered accounts -haven't commit privilege set by default. In order for your registered -account to have commit privilege inside CentOS Artwork Repository you -need to request it. See section -\ref{sec:Configuration:User:Privileges}. - -\subsection{User Account Registration} -\label{sec:Configuration:Account} - -To register a user account inside CentOS Artwork Repository, you need -to go to the following URL: - -\begin{quote} -\url{https://projects.centos.org/trac/artwork/} -\end{quote} - -\subsection{User Account Privileges} -\label{sec:Configuration:User:Privileges} - -To have commit privileges in CentOS Artwork Repository it is needed -that you show your interest first, preferably with something useful -like a new or improved design, translation, manual, or script. As -convenction, people working on CentOS Artwork Repository share ideas -in the mailing list -\href{mailto:centos-devel@centos.org}{centos-devel@centos.org}. If you -are interested in joining us go there and express yourself. - -\section{Repository Tagged Revisions} - -The CentOS Artwork Repository is also available as tagged revisions. -Tagged revisions are checkpoints on the CentOS Artwork Repository -developing lifetime. They are inmutable copies of the CentOS Artwork -Repository state through time. Tagged revisions contain the files -used to produce images but not images themselves. Inside tagged -revisions you can find scripts (\texttt{.sh}), design templates -(\texttt{.svg}), translation files (\texttt{\.sed}), gimp projects -(\texttt{.xcf}), and documetation files (\texttt{.tex}). - -CentOS Artowrk Repository tagged revisions are available for -downloading in the following location: - -\begin{description} -\item[URL:] https://projects.centos.org/svn/artwork/tags -\end{description} - -and alternatively, you can find references in the CentOS Project's -wiki, specifically in the ArtWork page: - -\begin{description} -\item[URL:] http://wiki.centos.org/ArtWork -\end{description} diff --git a/Manuals/Filesystem/filesystem-latex/Workstation/installation.tex b/Manuals/Filesystem/filesystem-latex/Workstation/installation.tex deleted file mode 100644 index 4a8e3ea..0000000 --- a/Manuals/Filesystem/filesystem-latex/Workstation/installation.tex +++ /dev/null @@ -1,139 +0,0 @@ -% Part : Preparing Your Workstation -% Chapter: Installation -% ------------------------------------------------------------ -% $Id: installation.tex 6191 2010-08-02 02:36:14Z al $ -% ------------------------------------------------------------ - -This chapter describes tools you need to have installed in your CentOS -workstation before using CentOS Artwork Repository. - -\section{Subversion} - -Subversion is a version control system, which allows you to keep old -versions of files and directories (usually source code), keep a log of -who, when, and why changes occurred, etc., like CVS, RCS or -SCCS.\footnote{More documentation about Subversion and its tools, -including detailed usage explanations of the svn, svnadmin, svnserve -and svnlook programs, historical background, philosophical approaches -and reasonings, etc., can be found at -\url{http://svnbook.red-bean.com/.}} - -To install Subversion client tools in your workstation you can use the -following command: - -\begin{quote} -yum install subversion -\end{quote} - -\section{Inkscape} - -Inkscape is a GUI editor for Scalable Vector Graphics (SVG) format -drawing files, with capabilities similar to Adobe Illustrator, -CorelDraw, Visio, etc. Inkscape features include versatile shapes, -bezier paths, freehand drawing, multiline text, text on path, alpha -blending, arbitrary affine transforms, gradient and pattern fills, -node editing, SVG-to-PNG export, grouping, layers, live clones, and -more. - -Note that Inkscape is not inside CentOS Distribution, so you need to -configure a third party repository like RPMForge or EPEL to install -Inkscape. Installation of a third party repositories inside CentOS -Distribution is described in the following URL: - -\begin{quote} -\url{http://wiki.centos.org/AdditionalResources/Repositories} -\end{quote} - -Once you have configured the third party repository you can install -Inkscape using the following command: - -\begin{quote} -yum install inkscape -\end{quote} - -\section{ImageMagick} - -ImageMagick is a free software suite for the creation, modification -and display of bitmap images. It can read, convert and write images -in a large variety of formats. Images can be cropped, colors can be -changed, various effects can be applied, images can be rotated and -combined, and text, lines, polygons, ellipses and Bézier curves can -be added to images and stretched and rotated. - -To install ImageMagick in your workstation you can run the following -command: - -\begin{quote} -yum install ImageMagick -\end{quote} - -\section{Netpbm} - -Netpbm is a toolkit for manipulation of graphic images, including -conversion of images between a variety of different formats. There -are over 300 separate tools in the package including converters for -about 100 graphics formats. - -To install Netpbm in your workstation you can run the following -command: - -\begin{quote} -yum install netpbm\{-progs\} -\end{quote} - -\section{Syslinux} - -Syslinux is a suite of bootloaders, currently supporting DOS FAT -filesystems, Linux ext2/ext3 filesystems (EXTLINUX), PXE network boots -(PXELINUX), or ISO 9660 CD-ROMs (ISOLINUX). It also includes a tool, -MEMDISK, which loads legacy operating systems from these media. The -package \texttt{syslinux} provides the programs \texttt{ppmtolss16} -and \texttt{lss16toppm} which are used to produce Anaconda Prompt -images. The \texttt{ppmtolss16} Perl program also includes the file -format specification. - -To install Syslinux in your workstation you can run the following -command: - -\begin{quote} -yum install syslinux -\end{quote} - -\section{GNU Image Manipulation Program} - -GNU Image Manipulation Program (GIMP) is used to manipulate images -inside CentOS Artwork Repository. - -To install GIMP in your workstation you can run the following command: - -\begin{quote} -yum install gimp -\end{quote} - -\section{GNU Core Utilities} - -The GNU core utilities are a set of tools commonly used in shell -scripts. - -To install the GNU core utilities in your workstation you can run the -following command: - -\begin{quote} -yum install core-utils -\end{quote} - -\section{\LaTeX} - -\LaTeX\ is a document preparation system implemented as a macro -package for Donald E. Knuth's \TeX\ typesetting program. The \LaTeX\ -command typesets a file of text using the \TeX\ program and the LaTeX -Macro package for \TeX. To be more specific, it processes an input -file containing the text of a document with interspersed commands that -describe how the text should be formatted. - -To install \LaTeX\ in your workstation you can run the following -command: - -\begin{quote} -yum install tetex-\{latex,fonts,doc,xdiv,dvips\} -\end{quote} diff --git a/Manuals/Filesystem/filesystem-latex/convenctions.tex b/Manuals/Filesystem/filesystem-latex/convenctions.tex deleted file mode 100644 index ea33699..0000000 --- a/Manuals/Filesystem/filesystem-latex/convenctions.tex +++ /dev/null @@ -1,5 +0,0 @@ -% Part : Frontmatter -% Chapter: Convenctions -% ------------------------------------------------------------ -% $Id: convenctions.tex 6260 2010-08-15 02:36:26Z al $ -% ------------------------------------------------------------ diff --git a/Manuals/Filesystem/filesystem-latex/repository.tex b/Manuals/Filesystem/filesystem-latex/repository.tex deleted file mode 100644 index 89ed1a9..0000000 --- a/Manuals/Filesystem/filesystem-latex/repository.tex +++ /dev/null @@ -1,307 +0,0 @@ -% ------------------------------------------------------------ -% $Id: repository.tex 6260 2010-08-15 02:36:26Z al $ -% ------------------------------------------------------------ -\documentclass[12pt]{book} -\usepackage{fancyhdr} -\renewcommand{\chaptermark}[1]{\markboth{#1}{}} -\fancyhf{} % delete current setting for header and footer -\fancyhead[RO,LE]{\bfseries\thepage} -\fancyhead[LO]{\bfseries\leftmark} -\fancyhead[RE]{\bfseries\leftmark} -\renewcommand{\headrulewidth}{0.5pt} -\renewcommand{\footrulewidth}{0pt} -\addtolength{\headheight}{0.5pt} % make space for the rule -\fancypagestyle{plain}{% - \fancyhead{} % get rid of headers on plain pages - \renewcommand{\headrulewidth}{0pt} % and the line - } -\usepackage[pdftex]{graphicx} -\usepackage{hyperref} -\hypersetup{pdfauthor={Alain Reguera Delgado},% - pdftitle={The CentOS Project - Artwork Repository},% - pdfsubject={CentOS Corporate Visual Identity}% - } - -\title{The CentOS Project - Artwork Repository} -\author{Alain Reguera Delgado} - -% Define words you don't want to split. -\hyphenation{CentOS} - -\begin{document} - -\pagestyle{empty} - -% Half title: The first page is a recto half title page with no folio. -% The page is very simple and displays just the main title of the book -% — no subtitle, author, or other information. One purported purpose -% of this page is to protect the main title page. -\begin{titlepage} -\begin{flushright} -\noindent\includegraphics[width=1\textwidth]{% - /home/centos/artwork/trunk/Identity/Models/Img/en/Promo/Stationery/motif-propagation.pdf}\\ -\vspace*{150pt} -\Huge\textbf{The CentOS Project} -\rule{\textwidth}{5pt} -\large -\textbf{Artwork Repository}\\ -\vspace*{150pt} -\normalsize -\today -\end{flushright} -\end{titlepage} - -% Page title: The title page is recto and contains the full title of -% the work, the names of the author(s) or editor(s), and often at the -% bottom of the page the name of the publisher, together with the -% publisher’s logo if it has one. -\begin{titlepage} -\begin{flushright} -\noindent\includegraphics[width=1\textwidth]{% - /home/centos/artwork/trunk/Identity/Models/Img/en/Promo/Stationery/motif-propagation.pdf}\\ -\vspace*{150pt} -\Huge\textbf{The CentOS Project} -\rule{\textwidth}{5pt} -\large -\textbf{Artwork Repository}\\ -\vspace*{150pt} -\normalsize -Alain Reguera Delgado $<$alain.reguera@gmail.com$>$\\ -\end{flushright} -\end{titlepage} - -% Copyright: The copyright page is verso and contains the copyright -% notice, the publishing/printing history, the country where printed, -% ISBN and/or CIP information. The page is usually typeset in a -% smaller font than the normal text. - -\noindent Copyright \copyright\ 2009, 2010 Alain Reguera Delgado. All\ -rights reserved.\\ -\\ -\noindent Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, -Version 1.2 or any later version published by the Free Software -Foundation; with no Invariant Sections, no Front-Cover Texts, and no -Back-Cover Texts. A copy of the license is included in the section -entitled ``\hyperlink{cha:Licenses:GFDL}{GNU Free Documentation -License}''. - -\frontmatter -\pagestyle{fancy} - -% Listings: -\tableofcontents -\listoftables -\listoffigures - -% Reset fancyhdr marks. -\renewcommand{\chaptermark}[1]{\markboth{#1}{}} - -% Dedication: -%\chapter*{Dedication} - -% Forewords: There may be a foreword after the listings, with no blank -% separator. A foreword is usually written by someone other than the -% author, preferably an eminent person, and is signed by the writer. -% The writer’s signature is often typeset in small caps after the end -% of the piece. -%\chapter{Forewords} - -% Preface: A preface is normally written by the author, in which he -% includes reasons why he wrote the work in the first place, and -% perhaps to provide some more personal comments than would be -% justified in the body. A preface starts on the page immediately -% following a foreword, or the lists. -%\chapter{Preface} - -\mainmatter - -% Reset fancyhdr marks. -\renewcommand{\chaptermark}[1]{\markboth{% - \chaptername\ \thechapter.\ #1}{}} - -\part{Concepts} - -\chapter{The CentOS Project} - \hypertarget{cha:Concepts:CentOS}{} - \label{cha:Concepts:CentOS} - \input{Concepts/CentOS/introduction.tex} - \input{Concepts/CentOS/incorporation.tex} - \input{Concepts/CentOS/philosophy.tex} - \input{Concepts/CentOS/mission.tex} - \input{Concepts/CentOS/distribution.tex} - \input{Concepts/CentOS/community.tex} - \input{Concepts/CentOS/release.tex} - -\chapter{Frameworks} - \hypertarget{cha:Concepts:frameworks}{} - \label{cha:Concepts:Frameworks} - \input{Concepts/Frameworks/introduction.tex} - \input{Concepts/Frameworks/templates.tex} - \input{Concepts/Frameworks/files.tex} - \input{Concepts/Frameworks/rendering.tex} - -\chapter{Corporate Identity} - \hypertarget{cha:Concepts:Identity}{} - \label{cha:Concepts:Identity} - \input{Concepts/Identity/introduction.tex} - \input{Concepts/Identity/structure.tex} - \input{Concepts/Identity/brands.tex} - \input{Concepts/Identity/release.tex} - \input{Concepts/Identity/themes.tex} - \input{Concepts/Identity/icons.tex} - \input{Concepts/Identity/models.tex} - \input{Concepts/Identity/widgets.tex} - -\chapter{Translations} - \hypertarget{cha:Concepts:Translations}{} - \label{cha:Concepts:Translations} - \input{Concepts/translations.tex} - -\chapter{Manuals} - \hypertarget{cha:Concepts:Manuals}{} - \label{cha:Concepts:Manuals} - \input{Concepts/manuals.tex} - -\chapter{Scripts} - \hypertarget{cha:Concepts:Scripts}{} - \label{cha:Concepts:Scripts} - \input{Concepts/scripts.tex} - -\chapter{Rebranding} - \hypertarget{cha:Concepts:rebranding}{} - \label{cha:Concepts:rebranding} - \input{Concepts/rebranding.tex} - -\part{Preparing Your Workstation} - -\chapter{Installation} - \hypertarget{cha:Workstation:Installation}{} - \label{cha:Workstation:Installation} - \input{Workstation/installation.tex} - -\chapter{Configuration} - \hypertarget{cha:Workstation:Configuration}{} - \label{cha:Workstation:Configuration} - \input{Workstation/configuration.tex} - -\part{Distribution} - \hypertarget{par:Distribution}{} - \label{par:Distribution} - -\chapter{Anaconda Prompt} - \hypertarget{cha:Distribution:Anaconda:Prompt}{} - \label{cha:Distribution:Anaconda:Prompt} - \input{Distribution/Anaconda/Prompt/chapter.tex} - -\chapter{Anaconda Header} - \hypertarget{cha:Distribution:Anaconda:Header}{} - \label{cha:Distribution:Anaconda:Header} - \input{Distribution/Anaconda/Header/chapter.tex} - -\chapter{Anaconda Splash} - \hypertarget{cha:Distribution:Anaconda:Splash}{} - \label{cha:Distribution:Anaconda:Splash} - \input{Distribution/Anaconda/Splash/chapter.tex} - -\chapter{Anaconda Progress} - \hypertarget{cha:Distribution:Anaconda:Progress}{} - \label{cha:Distribution:Anaconda:Progress} - \input{Distribution/Anaconda/Progress/introduction.tex} - \input{Distribution/Anaconda/Progress/framework.tex} - \input{Distribution/Anaconda/Progress/rebranding.tex} - -\chapter{Firstboot} - \hypertarget{cha:Distribution:Anaconda:Firstboot}{} - \label{cha:Distribution:Anaconda:Firstboot} - \input{Distribution/Anaconda/Firstboot/introduction.tex} - \input{Distribution/Anaconda/Firstboot/framework.tex} - \input{Distribution/Anaconda/Firstboot/rebranding.tex} - -\chapter{GNOME Display Manager (GDM)} - \hypertarget{cha:Distribution:BootUp:GDM}{} - \label{cha:Distribution:BootUp:GDM} - -\chapter{GRand Unified Bootloader (GRUB)} - \hypertarget{cha:Distribution:BootUp:GRUB}{} - \label{cha:Distribution:BootUp:GRUB} - -\chapter{GNOME Splash} - \hypertarget{cha:Distribution:BootUp:GSplash}{} - \label{cha:Distribution:BootUp:GSplash} - -\chapter{KDE Display Manager (KDM)} - \hypertarget{cha:Distribution:BootUp:KDM}{} - \label{cha:Distribution:BootUp:KDM} - -\chapter{KDE Splash} - \hypertarget{cha:Distribution:BootUp:KSplash}{} - \label{cha:Distribution:BootUp:KSplash} - -\chapter{Graphical Boot (RHGB)} - \hypertarget{cha:Distribution:BootUp:RHGB}{} - \label{cha:Distribution:BootUp:RHGB} - -\chapter{Backgrounds} - \hypertarget{cha:Distribution:Backgrounds}{} - \label{cha:Distribution:Backgrounds} - \input{Distribution/Backgrounds/introduction.tex} - \input{Distribution/Backgrounds/framework.tex} - \input{Distribution/Backgrounds/rebranding.tex} - -\chapter{Release Notes} - \hypertarget{cha:Distribution:ReleaseNotes}{} - \label{cha:Distribution:ReleaseNotes} - -\part{Promotion} - -\chapter{Cards} - \hypertarget{cha:Promotion:Cards}{} - \label{cha:Promotion:Cards} - -\chapter{Clothes} - \hypertarget{cha:Promotion:Clothes}{} - \label{cha:Promotion:Clothes} - -\chapter{Flags} - \hypertarget{cha:Promotion:Flags}{} - \label{cha:Promotion:Flags} - -\chapter{Media} - \hypertarget{cha:Promotion:Media}{} - \label{cha:Promotion:Media} - -\chapter{Posters} - \hypertarget{cha:Promotion:Posters}{} - \label{cha:Promotion:Posters} - -\chapter{Releases} - \hypertarget{cha:Promotion:Releases}{} - \label{cha:Promotion:Releases} - -\chapter{Stands} - \hypertarget{cha:Promotion:Stands}{} - \label{cha:Promotion:Stands} - -\chapter{Stationery} - \hypertarget{cha:Promotion:Stationery}{} - \label{cha:Promotion:Stationery} - -\chapter{Sticky} - \hypertarget{cha:Promotion:Sticky}{} - \label{cha:Promotion:Sticky} - -\part{Licenses} -\appendix -\input{Licenses/centos-redistribution.tex} -\input{Licenses/gfdl.tex} - -\backmatter - -% Bibliographies: BibTeX automates much of the job of typesetting -% bibliographies, and makes bibliography entries reusable in many -% different contexts. - -% Indexing table: - -\end{document} diff --git a/Manuals/Filesystem/filesystem-menu.texi b/Manuals/Filesystem/filesystem-menu.texi deleted file mode 100644 index da7aeff..0000000 --- a/Manuals/Filesystem/filesystem-menu.texi +++ /dev/null @@ -1,7 +0,0 @@ -@menu -* branches:: -* tags:: -* trunk:: -* Index:: -* List of Figures:: -@end menu diff --git a/Manuals/Filesystem/filesystem-nodes.texi b/Manuals/Filesystem/filesystem-nodes.texi deleted file mode 100644 index 7ede600..0000000 --- a/Manuals/Filesystem/filesystem-nodes.texi +++ /dev/null @@ -1,3 +0,0 @@ -@include branches/chapter.texi -@include tags/chapter.texi -@include trunk/chapter.texi diff --git a/Manuals/Filesystem/filesystem.info.bz2 b/Manuals/Filesystem/filesystem.info.bz2 deleted file mode 100644 index d6174e4..0000000 Binary files a/Manuals/Filesystem/filesystem.info.bz2 and /dev/null differ diff --git a/Manuals/Filesystem/filesystem.pdf b/Manuals/Filesystem/filesystem.pdf deleted file mode 100644 index d653c09..0000000 Binary files a/Manuals/Filesystem/filesystem.pdf and /dev/null differ diff --git a/Manuals/Filesystem/filesystem.texi b/Manuals/Filesystem/filesystem.texi deleted file mode 100644 index a04227e..0000000 --- a/Manuals/Filesystem/filesystem.texi +++ /dev/null @@ -1,52 +0,0 @@ -\input texinfo @c -*-texinfo-*- -@c $Id: repository.texi 33 2010-09-13 11:36:41Z al $ -@setfilename filesystem.info -@settitle CentOS Artwork Repository - File System -@afourpaper -@finalout - -@c -- Summary Description and Copyright ----------------------- -@copying -Copyright @copyright{} 2009-2011 Alain Reguera Delgado - -Permission is granted to copy, distribute and/or modify this document -under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no -Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A -copy of the license is included in the section entitled GNU Free -Documentation License. -@end copying - -@c -- Titlepage, Contents, Copyright --------------------------- - -@titlepage -@title CentOS Artwork Repository -@subtitle File System -@author Alain Reguera Delgado -@page -@vskip 0pt plus 1filll -@insertcopying -@end titlepage - -@contents - -@c -- `Top' Node and Master Menu ------------------------------- - -@ifnottex -@node Top -@top CentOS Artwork Repository - File System - -@insertcopying -@end ifnottex - -@include filesystem-menu.texi - -@c -- The Body of the Document -------------------------------- - -@include filesystem-nodes.texi - -@c -- The End of the Document --------------------------------- - -@include filesystem-index.texi - -@bye diff --git a/Manuals/Filesystem/filesystem.txt b/Manuals/Filesystem/filesystem.txt deleted file mode 100644 index cc497bc..0000000 --- a/Manuals/Filesystem/filesystem.txt +++ /dev/null @@ -1,6032 +0,0 @@ -Table of Contents -***************** - -CentOS Artwork Repository - File System -1 branches -2 tags -3 trunk - 3.1 trunk/Identity - 3.1.1 Goals - 3.1.2 Description - 3.1.3 Usage - 3.1.4 File name convenctions - 3.1.4.1 When text-based files are rendered - 3.1.4.2 When image-based files are rendered - 3.1.5 See also - 3.1.6 References - 3.2 trunk/Identity/Brands - 3.2.1 Goals - 3.2.2 Description - 3.2.3 Usage - 3.2.4 See also - 3.3 trunk/Identity/Fonts - 3.3.1 Goals - 3.3.2 Description - 3.3.3 Usage - 3.3.4 See also - 3.4 trunk/Identity/Icons - 3.4.1 Goals - 3.4.2 Description - 3.4.3 Usage - 3.4.4 See also - 3.5 trunk/Identity/Isolinux - 3.5.1 Goals - 3.5.2 Description - 3.5.3 Usage - 3.5.4 See also - 3.6 trunk/Identity/Models - 3.6.1 Goals - 3.6.2 Description - 3.6.3 Usage - 3.6.4 See also - 3.7 trunk/Identity/Models/Css - 3.7.1 Goals - 3.7.2 Description - 3.7.3 Usage - 3.7.4 See also - 3.8 trunk/Identity/Models/Html - 3.8.1 Goals - 3.8.2 Description - 3.8.3 Usage - 3.8.4 See also - 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.10 trunk/Identity/Models/Tpl - 3.10.1 Goals - 3.10.2 Description - 3.10.3 Usage - 3.10.4 See also - 3.11 trunk/Identity/Models/Tpl/Promo/Web - 3.11.1 Goals - 3.11.2 The CentOS web environment - 3.11.2.1 Design model (without ads) - 3.11.2.2 Design model (with ads) - 3.11.2.3 HTML definitions - 3.11.2.4 Controlling visual style - 3.11.2.5 Producing visual style - 3.11.2.6 Navigation - 3.11.2.7 Development and release cycle - 3.11.2.8 The [webenv-test] repository - 3.11.2.9 The [webenv] repository - 3.11.2.10 Priority configuration - 3.11.3 Usage - 3.11.4 See also - 3.12 trunk/Identity/Models/Xcf - 3.12.1 Goals - 3.12.2 Description - 3.12.3 Usage - 3.12.4 See also - 3.13 trunk/Identity/Release - 3.13.1 Goals - 3.13.2 Description - 3.13.3 Usage - 3.13.4 See also - 3.14 trunk/Identity/Themes - 3.14.1 Goals - 3.14.2 Description - 3.14.3 Usage - 3.14.4 See also - 3.15 trunk/Identity/Themes/Models - 3.15.1 Goals - 3.15.2 Description - 3.15.3 Usage - 3.15.4 See also - 3.16 trunk/Identity/Themes/Models/Alternative - 3.16.1 Goals - 3.16.2 Description - 3.16.3 Usage - 3.16.4 See also - 3.17 trunk/Identity/Themes/Models/Default - 3.17.1 Goals - 3.17.2 Description - 3.17.3 Usage - 3.17.4 See also - 3.18 trunk/Identity/Themes/Models/Default/Distro - 3.18.1 Goals - 3.18.2 Description - 3.18.2.1 One theme for all major releases - 3.18.2.2 One theme for each major release - 3.18.3 Usage - 3.18.4 See also - 3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda - 3.19.1 Goals - 3.19.2 Description - 3.19.3 Usage - 3.19.4 See also - 3.20 trunk/Identity/Themes/Models/Default/Promo - 3.20.1 Goals - 3.20.2 Description - 3.20.3 Usage - 3.20.4 See also - 3.21 trunk/Identity/Themes/Models/Default/Web - 3.21.1 Goals - 3.21.2 Description - 3.21.3 Usage - 3.21.4 See also - 3.22 trunk/Identity/Themes/Motifs - 3.22.1 Goals - 3.22.2 Description - 3.22.3 Usage - 3.22.4 See also - 3.23 trunk/Identity/Themes/Motifs/Flame - 3.23.1 Goals - 3.23.2 Description - 3.23.3 Construction - 3.23.3.1 Step 1: Set image size - 3.23.3.2 Step 2: Add base color and pattern information - 3.23.3.3 Step 3: Add flame motif - 3.23.3.4 Step 4: Add foreground color - 3.23.4 See also - 3.24 trunk/Identity/Themes/Motifs/Modern - 3.24.1 Presentation - 3.24.2 Construction - 3.24.3 Usage - 3.24.4 See also - 3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds - 3.25.1 Goals - 3.25.2 Description - 3.25.3 Usage - 3.25.4 See also - 3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img - 3.26.1 Goals - 3.26.2 Description - 3.26.3 Usage - 3.26.4 See also - 3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl - 3.27.1 Goals - 3.27.2 Description - 3.27.3 Usage - 3.27.4 See also - 3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf - 3.28.1 Goals - 3.28.2 Description - 3.28.3 Usage - 3.28.4 See also - 3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress - 3.29.1 Goals - 3.29.2 Description - 3.29.3 Usage - 3.29.4 See also - 3.30 trunk/Identity/Themes/Motifs/Modern/Palettes - 3.30.1 Goals - 3.30.2 Description - 3.30.3 Usage - 3.30.4 See also - 3.31 trunk/Identity/Themes/Motifs/TreeFlower - 3.31.1 Goals - 3.31.2 Description - 3.31.3 Usage - 3.31.4 See also - 3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds - 3.32.1 Goals - 3.32.2 Description - 3.32.2.1 Desktop background - 3.32.2.2 Anaconda Prompt (syslinux) background - 3.32.2.3 Grub background - 3.32.3 Usage - 3.32.4 See also - 3.33 trunk/Identity/Widgets - 3.33.1 Goals - 3.33.2 Description - 3.33.3 Usage - 3.33.4 See also - 3.34 trunk/Locales - 3.35 trunk/Locales/Identity - 3.35.1 Goals - 3.35.2 Description - 3.35.3 Usage - 3.35.4 See also - 3.36 trunk/Locales/Identity/Brands - 3.36.1 Goals - 3.36.2 Description - 3.36.2.1 Conventional file names - 3.36.2.2 Numeric file names - 3.36.2.3 Translation markers - 3.36.3 Usage - 3.36.4 See also - 3.37 trunk/Locales/Identity/Brands/Tpl - 3.37.1 Goals - 3.37.2 Description - 3.37.3 Usage - 3.37.4 See also - 3.38 trunk/Locales/Identity/Fonts - 3.38.1 Goals - 3.38.2 Description - 3.38.2.1 Translation Markers - 3.38.3 Usage - 3.38.4 See also - 3.39 trunk/Locales/Identity/Models - 3.39.1 Goals - 3.39.2 Description - 3.39.3 Usage - 3.39.4 See also - 3.40 trunk/Locales/Identity/Release - 3.40.1 Goals - 3.40.2 Description - 3.40.3 Usage - 3.40.4 See also - 3.41 trunk/Locales/Identity/Themes - 3.41.1 Goals - 3.41.2 Description - 3.41.3 Usage - 3.41.4 See also - 3.42 trunk/Locales/Identity/Themes/Backgrounds - 3.42.1 Goals - 3.42.2 Description - 3.42.3 Usage - 3.42.4 See also - 3.43 trunk/Locales/Identity/Themes/Distro/Anaconda/Progress - 3.43.1 Goals - 3.43.2 Description - 3.43.3 Usage - 3.43.4 See also - 3.44 trunk/Locales/Identity/Widgets - 3.44.1 Goals - 3.44.2 Description - 3.44.3 Usage - 3.44.4 See also - 3.45 trunk/Manuals - 3.45.1 Goals - 3.45.2 Description - 3.45.3 Usage - 3.45.4 See also - 3.46 trunk/Scripts - 3.46.1 Goals - 3.46.2 Description - 3.46.3 Usage - 3.46.4 See also - 3.47 trunk/Scripts/Bash - 3.47.1 Goals - 3.47.2 Description - 3.47.3 Usage - 3.47.4 See also - 3.48 trunk/Scripts/Bash/Cli - 3.49 trunk/Scripts/Bash/Cli/Functions - 3.49.1 Goals - 3.49.2 Description - 3.49.3 Usage - 3.49.3.1 Global variables - 3.49.3.2 Global functions - 3.49.3.3 Specific functions - 3.49.4 See also - 3.50 trunk/Scripts/Bash/Cli/Functions/Help - 3.50.1 Goals - 3.50.2 Description - 3.50.3 Usage - 3.50.4 See also - 3.51 trunk/Scripts/Bash/Cli/Functions/Html - 3.51.1 Goals - 3.51.2 Description - 3.51.3 Usage - 3.51.4 See also - 3.52 trunk/Scripts/Bash/Cli/Functions/Locale - 3.52.1 Goals - 3.52.2 Description - 3.52.3 Usage - 3.52.4 See also - 3.53 trunk/Scripts/Bash/Cli/Functions/Manual - 3.53.1 Goals - 3.53.2 Description - 3.53.3 Usage - 3.53.4 See also - 3.54 trunk/Scripts/Bash/Cli/Functions/Path - 3.54.1 Goals - 3.54.2 Description - 3.54.2.1 Repository layout - 3.54.2.2 Repository name convenctions - 3.54.2.3 Repository work flow - 3.54.2.4 Parallel directories - 3.54.2.5 Syncronizing path information - 3.54.2.6 What is the right place to store it? - 3.54.3 Usage - 3.54.4 See also - 3.55 trunk/Scripts/Bash/Cli/Functions/Render - 3.55.1 Renderable identity directory structures - 3.55.1.1 Design template without translation - 3.55.1.2 Design template with translation (one-to-one) - 3.55.1.3 Design template with translation (optimized) - 3.55.1.4 Design template with translation (optimized+flexibility) - 3.55.2 Renderable translation directory structures - 3.55.3 Copying renderable directory structures - 3.55.4 Usage - 3.55.5 See also - 3.56 trunk/Scripts/Bash/Cli/Functions/Render/Config - 3.56.1 Goals - 3.56.2 Description - 3.56.2.1 The `render.conf.sh' identity model - 3.56.2.2 The `render.conf.sh' translation model - 3.56.2.3 The `render.conf.sh' rendering actions - 3.56.3 Usage - 3.56.4 See also - 3.57 trunk/Scripts/Bash/Cli/Functions/Shell - 3.57.1 Goals - 3.57.2 Description - 3.57.3 Usage - 3.57.4 See also - 3.58 trunk/Scripts/Bash/Cli/Functions/Svg - 3.58.1 Goals - 3.58.2 Description - 3.58.2.1 Metadata maintainance - 3.58.2.2 Unused definitions - 3.58.3 Usage - 3.58.4 See also - 3.59 trunk/Scripts/Bash/Cli/Functions/Verify - 3.59.1 Goals - 3.59.2 Description - 3.59.2.1 Packages - 3.59.2.2 Links - 3.59.2.3 Environment variables - 3.59.3 Usage - 3.59.4 See also - 3.60 trunk/Scripts/Python - 3.60.1 Goals - 3.60.2 Description - 3.60.3 Usage - 3.60.4 See also -Index -List of Figures - - -CentOS Artwork Repository - File System -*************************************** - -Copyright (C) 2009-2011 Alain Reguera Delgado - - Permission is granted to copy, distribute and/or modify this document -under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no -Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A -copy of the license is included in the section entitled GNU Free -Documentation License. - -1 branches -********** - -2 tags -****** - -3 trunk -******* - -3.1 trunk/Identity -================== - -3.1.1 Goals ------------ - -The `trunk/Identity' directory exists to organize CentOS corporate -identity artworks. - -3.1.2 Description ------------------ - -The CentOS Project corporate identity is the "persona" of the -organization known as The CentOS Project. The CentOS Project corporate -identity plays a significant role in the way the CentOS Project, as -organization, presents itself to both internal and external -stakeholders. In general terms, the CentOS Project corporate visual -identity expresses the values and ambitions of the CentOS Project -organization, its business, and its characteristics. - - The CentOS Project corporate identity provides visibility, -recognizability, reputation, structure and identification to the CentOS -Project organization by means of corporate design, corporate -communication, and corporate behaviour. - - The CentOS Project settles down its corporate visual identity on a -"monolithic corporate visual identity structure". In this structure The -CentOS Project uses one unique name (The CentOS Brand) and one unique -visual style (The CentOS Default Theme) in all its manifestations. - -*The CentOS Brands* - The CentOS brand is the name or trademark that conncects the - producer with their products. In this case, the producer is The - CentOS Project and the products are the CentOS distributions, the - CentOS web sites, the CentOS promotion stuff, etc. - - *Note trunk Identity Brands::, for more information. - -*The CentOS Themes* - The CentOS themes are a set of image files connected all together - by one unique visual style. Each theme is organized in different - visual manifestations, in order to cover each visual manifestation - of The CentOS Project (i.e., distributions, websites, promotion - stuff, etc.). *Note trunk Identity Themes::, for more information. - - Inside a monolithic corporate visual identity structure, internal and -external stakeholders use to feel a strong sensation of uniformity, -orientation, and identification with the organization. No matter if you -are visiting websites, using the distribution, or acting on social -events, the one unique name and one unique visual style conect them all -to say: Hey! we are all parts of the CentOS project. And, probably, -some vister will say: Can I join the party? Yes you can, it is free. :) - -3.1.3 Usage ------------ - -To produce identity artworks, use the following commands: - -`centos-art render 'path/to/dir'' - When `path/to/dir' refers to one renderable directory under - `trunk/Identity', this command renders identity artworks using - both related design models and related translation files. - -`centos-art render 'path/to/dir' --filter='pattern'' - When `path/to/dir' refers to one renderable directory under - `trunk/Identity', this command renders identity artworks using - both related design models and related translation files that match - the regular expression passed in `--filter='pattern'' argument. - - To control the number of files produced by `centos-art' command, - you need to look into the translation path and provide a regular - expression pattern that matches the translation path, or paths, - related to the file, or files, you want to produce. - - The regular expression pattern you provide to `centos-art' command - is applied to the translation path from its very beginning. It is - not the same to say `5/en/01-welcome' that `01-welcome', the frist - expression matches but the last one does not. - - When using `--filter='pattern'' you don't need to specify the file - extension. It is removed from translation path before applying the - pattern, so it doesn't count here. - -3.1.4 File name convenctions ----------------------------- - -As file name convenction, inside CentOS Artwork Repository, both -text-based and image-based file name produced by `centos-art.sh' script -has the same name of their translation files without the `.sed' -extension. The file extension is set as follow: - -3.1.4.1 When text-based files are rendered -.......................................... - -Text-based files end up having the same extension of their design -template file. - -3.1.4.2 When image-based files are rendered -........................................... - -Image-based files always end up having the `.png' extension. - - *Tip* Once `.png' images are created, other image formats may be - created using the `renderFormats' post-rendering action, inside - the image-based related pre-rendering configuration script. - - *Note trunk Scripts Bash::, for more information. - -3.1.5 See also --------------- - -3.1.6 References ----------------- - - * `http://en.wikipedia.org/Corporate_identity' (and related links). - -3.2 trunk/Identity/Brands -========================= - -3.2.1 Goals ------------ - - * ... - -3.2.2 Description ------------------ - -3.2.3 Usage ------------ - -3.2.4 See also --------------- - -3.3 trunk/Identity/Fonts -======================== - -3.3.1 Goals ------------ - -This section exists to organize digital typographies used by the CentOS -project. - -3.3.2 Description ------------------ - -3.3.3 Usage ------------ - -The CentOS corporate identity is attached to `DejaVu LGC' font-family. -Whatever artwork you design for CentOS project, that requires -typography usage, must be done using `DejaVu LGC' font-family. - -*Recommendation-1:* - For screen desings (e.g., anything that final destination will - never be printed on paper or any medium outside computer screens) - use `DejaVu LGC Sans' font-family. - -*Recommendation-2:* - For non-screen designs (e.g., anything that final desition will be - printed on paper or any other medium outside computer screens) use - `DejaVu LGC Serif' font-family. As convenction files described in - this rule are stored under `Stationery' directories. - - The only execption for the two recommendations above is the -typography used inside CentOS logo. The CentOS logo is the main visual -representation of the CentOS project so the typography used in it must -be the same always, no matter where it be shown. It also has to be -clear enough to dismiss any confussion between similar typefaces (e.g., -the number one (1) sometimes is confuesed with the letter `el' (l) or -letter `ai' (i)). - - As CentOS logo typography convenction, the word `CentOS' uses -`Denmark' typography as base, both for the word `CentOS' and the phrase -`Community Enterprise Operating System'. The phrase size of CentOS logo -is half the size in poits the word `CentOS' has and it below `CentOS' -word and aligned with it on the left. The distance between `CentOS' -word and phrase `Community Enterprise Operating System' have the size -in points the phrase has. - - When the CentOS release brand is built, use `Denmark' typography for -the release number. The release number size is two times larger (in -height) than default `CentOS' word. The separation between release -number and `CentOS' word is twice the size in points of separation -between `CentOS' word and phrase `Community Enterprise Operating -System'. - - Another component inside CentOS logo is the trademark symbol (TM). -This symbol specifies that the CentOS logo must be consider a product -brand, even it is not a registered one. The trademark symbol uses -DejaVu LGC Sans Regular typography. The trademark symbol is aligned -right-top on the outter side of `CentOS' word. The trademark symbol -must not exceed haf the distance, in points, between `CentOS' word and -the release number on its right. - - It would be very convenient for the CentOS Project and its community -to to make a registered trademark (®) of CentOS logo. To make a -register trademark of CentOS Logo prevents legal complications in the -market place of brands. It grants the consistency, through time, of -CentOS project corporate visual identity. - - *Note* The information about trademarks and corporate identity is - my personal interpretation of - `http://en.wikipedia.org/Corporate_identity' and - `http://en.wikipedia.org/Trademark' description. If you have - practical experiences with these affairs, please serve yourself to - improve this section with your reasons. - -3.3.4 See also --------------- - -3.4 trunk/Identity/Icons -======================== - -3.4.1 Goals ------------ - - * ... - -3.4.2 Description ------------------ - -3.4.3 Usage ------------ - -3.4.4 See also --------------- - -3.5 trunk/Identity/Isolinux -=========================== - -3.5.1 Goals ------------ - - * ... - -3.5.2 Description ------------------ - -3.5.3 Usage ------------ - -3.5.4 See also --------------- - -3.6 trunk/Identity/Models -========================= - -3.6.1 Goals ------------ - -This section exists to organize design models. - -3.6.2 Description ------------------ - -Design models are representative designs useful to understand how to -build artworks. - -3.6.3 Usage ------------ - -3.6.4 See also --------------- - -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 ------------------ - - * ... - -3.7.3 Usage ------------ - - * ... - -3.7.4 See also --------------- - -3.8 trunk/Identity/Models/Html -============================== - -3.8.1 Goals ------------ - - * ... - -3.8.2 Description ------------------ - - * ... - -3.8.3 Usage ------------ - - * ... - -3.8.4 See also --------------- - -3.9 trunk/Identity/Models/Img/Promo/Web -======================================= - -3.9.1 Goals ------------ - - * Provide images related to CentOS web interface. - -3.9.2 Description ------------------ - - * ... - -3.9.3 Usage ------------ - - * ... - -3.9.4 See also --------------- - -3.10 trunk/Identity/Models/Tpl -============================== - -3.10.1 Goals ------------- - - * ... - -3.10.2 Description ------------------- - - * ... - -3.10.3 Usage ------------- - - * ... - -3.10.4 See also ---------------- - -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: - - * One unique name and one unique visual style to all web - applications used inside the web environment. - - * One-step navigation to web applications inside the environment. - - * High degree of customization to change the visual style of all web - applications with few changes (e.g, updating just two or three - images plus common style sheet [CSS] definitions). - - The CentOS project is attached to a monolithic corporate visual -identity (*note 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 that used by -MoinMoin. - - This visual style diversity complicates our goal of one unique visual -style for all web applications. So, if we want one unique visual style -for all web applications used, it is innevitable to modify the web -applications in order to implement the CentOS one unique visual style -customization in them. Direct modification of upstream applications is -not convenient because upstream applications come with their one visual -style and administrators take the risk of loosing all customization -changes the next time the application be updated (since not all -upstream web applications, used in CentOS web environment, separate -presentation from logic). - - To solve the "one unique visual style" issue, installation and -actualization of web applications --used inside CentOS web -environment-- need to be independent from upstream web applications -development line; in a way that CentOS web environment administrators -can install and update web applications freely without risk of loosing -the one unique visual style customization changes. - - At the surface of this issue we can see the need of one specific yum -repository to store CentOS web environment customized web applications. - -3.11.2.1 Design model (without ads) -................................... - -3.11.2.2 Design model (with ads) -................................ - -3.11.2.3 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. - -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* 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. - - *Tip* Use the `diff' command of Subversion 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. - - *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. - - *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 ------------- - - * ... - -3.11.4 See also ---------------- - ----------- Footnotes ---------- - - (1) The theme support of Mailman may be introduced in mailman-3.x.x -release. - -3.12 trunk/Identity/Models/Xcf -============================== - -3.12.1 Goals ------------- - - * ... - -3.12.2 Description ------------------- - - * ... - -3.12.3 Usage ------------- - - * ... - -3.12.4 See also ---------------- - -3.13 trunk/Identity/Release -=========================== - -3.13.1 Goals ------------- - - * ... - -3.13.2 Description ------------------- - -3.13.3 Usage ------------- - -3.13.4 See also ---------------- - -3.14 trunk/Identity/Themes -========================== - -3.14.1 Goals ------------- - -The `trunk/Identity/Themes/' directory exists to organize production of -CentOS themes. - -3.14.2 Description ------------------- - -3.14.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.14.4 See also ---------------- - -3.15 trunk/Identity/Themes/Models -================================= - -3.15.1 Goals ------------- - - * Organize theme models. - -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 `*Note Default: trunk -Identity Themes Models Default,' and `*Note Alternative: trunk Identity -Themes Models Alternative,' ready-to-use theme models. - -3.15.4 See also ---------------- - -3.16 trunk/Identity/Themes/Models/Alternative -============================================= - -3.16.1 Goals ------------- - - * ... - -3.16.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.16.3 Usage ------------- - - * ... - -3.16.4 See also ---------------- - -3.17 trunk/Identity/Themes/Models/Default -========================================= - -3.17.1 Goals ------------- - -This location stores CentOS default theme model. The default theme -model of CentOS is used in all visual manifestations of CentOS Project -corporate visual identity (e.g., distributions, web sites, promotion, -etc.). - -3.17.2 Description ------------------- - -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 *Note Theme Motifs: trunk Identity Themes Motifs. - -3.17.4 See also ---------------- - -3.18 trunk/Identity/Themes/Models/Default/Distro -================================================ - -3.18.1 Goals ------------- - - * ... - -3.18.2 Description ------------------- - -It applies to all major releases of CentOS distribution. - -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. - - 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* 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. - -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. - - 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.18.3 Usage ------------- - -3.18.4 See also ---------------- - -3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda -========================================================= - -3.19.1 Goals ------------- - - * ... - -3.19.2 Description ------------------- - -3.19.3 Usage ------------- - -3.19.4 See also ---------------- - -3.20 trunk/Identity/Themes/Models/Default/Promo -=============================================== - -3.20.1 Goals ------------- - - * ... - -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 ------------- - - * ... - -3.20.4 See also ---------------- - -3.21 trunk/Identity/Themes/Models/Default/Web -============================================= - -3.21.1 Goals ------------- - - * ... - -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 ------------- - - * ... - -3.21.4 See also ---------------- - -3.22 trunk/Identity/Themes/Motifs -================================= - -3.22.1 Goals ------------- - -The `trunk/Identity/Themes/Motifs' directory exists to: - - * Organize CentOS themes' artistic motifs. - -3.22.2 Description ------------------- - -The artistic motif of theme is a graphic design component that provides -the visual style of themes, it is used as pattern to connect all visual -manifestations inside one unique theme. - - Artistic motifs are based on conceptual ideas. Conceptual ideas bring -the motivation, they are fuel for the engines of human imagination. -Good conceptual ideas may produce good motivation to produce almost -anything, and art works don't escape from it. - -`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 the name of your artistic motif. If possible, -when creating new conceptual ideas for CentOS, think about what CentOS -means for you, what does it makes you feel, take your time, think deep, -and share; you can improve the idea as time goes on. - - Once you have defined a name for your theme, you need to create the -motif structure of your theme. The motif structure is the basic -direcotry structure you'll use to work your ideas. Here is where you -organize your graphic design projects. - - To add a new motif structure to CentOS Artwork Repository, you need -to use the `centos-art' command line in the `Identity/Themes/Motifs/' -directory as described below: - - centos-art add --motif=ThemeName - - The previous command will create the basic structure of themes 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 ------------- - -When designing artistic motifs for CentOS, consider the following -recommendations: - - * Give a unique (case-sensitive) name to your Motif. This name is - used as value wherever theme variable ($THEME) or translation - marker (=THEME=) is. Optionally, you can add a description about - inspiration and concepts behind your work. - - * Use the location `trunk/Identity/Themes/Motifs/$THEME/' to store - your work. If it doesn't exist create it. Note that this require - you to have previous commit access in CentOS Artwork Repository. - - * The CentOS Project is using the blue color (#204c8d) as base color - for its corporate visual identity. Use such base corporate color - information as much as possible in your artistic motif designs. - - * Try to make your design fit one of the theme models. - - * Feel free to make your art enterprise-level and beautiful. - - * Add the following information on your artwork (both in a visible - design area and document metadata): - - * The name (or logo) of your artistic motif. - - * The copyright sentence: Copyright (C) YEAR YOURNAME - - * The license under which the work is released. All CentOS Art - works are released under Creative Common Share-Alike License - 3.0 (http://creativecommons.org/licenses/by-sa/3.0/) - (`http://creativecommons.org/licenses/by-sa/3.0/'). - - -3.22.4 See also ---------------- - -3.23 trunk/Identity/Themes/Motifs/Flame -======================================= - -3.23.1 Goals ------------- - -This section describes the steps we followed to construct the _Flame_ -artistic motif. This section may be useful for anyone interested in -reproducing the _Flame_ artistic motif, or in creating new artistic -motifs for The CentOS Project corporate visual identity (*note trunk -Identity::). - -3.23.2 Description ------------------- - -The _Flame_ artistic motif was built using the flame filter of Gimp 2.2 -in CentOS 5.5. - - The flame filter of Gimp can produce stunning, randomly generated -fractal patterns. The flame filter of Gimp gives us a great oportunity -to reduce the time used to produce new artistic motifs, because of its -"randomly generated" nature. Once the artistic motif be created, it is -propagated through all visual manifestations of CentOS Project -corporate visual identity using the `centos-art.sh' script (*note trunk -Scripts Bash::) inside the CentOS Artwork Repository. - - To set the time intervals between each new visual style production, -we could reuse the CentOS distribution major release schema. I.e., we -could produce a new visual style, every two years, based on a new -"randomly generated" flame pattern, and publish the whole corporate -visual identity (i.e., distribution stuff, promotion stuff, websites -stuff, etc.) with the new major release of CentOS distribution all -together at once. - - Producing a new visual style is not one day's task. Once we have -defined the artistic motif, we need to propagate it through all visual -manifestations of The CentOS Project corporate visual identity. When we -say that we could produce one new visual style every two years we -really mean: to work two years long in order to propagate a new visual -style to all visual manifestations of The CentOS Project corporate -visual identity. - - Obviously, in order to propagate one visual style to all different -visual manifestations of The CentOS Project corporate visual identity, -we need first to know which the visual manifestations are. To define -which visual manifestations are inside The CentOS Project corporate -visual identity is one of the goals the CentOS Artwork Repository and -this documentation manual are both aimed to satisfy. - - Once we define which the visual manifestation are, it is possible to -define how to produce them, and this way, organize the automation -process. Such automation process is one of the goals of `centos-art.sh' -script. - - With the combination of both CentOS Artwork Repository and -`centos-art.sh' scripts we define work lines where translators, -programmers, and graphic designers work together to distribute and -reduce the amount of time employed to produce The CentOS Project -monolithic corporate identity. - - From a monolithic corporate visual identity point of view, notice -that we are producing a new visual style for the same theme (i.e., -_Flame_). It would be another flame design but still a flame design. -This idea is very important to be aware of, because we are somehow -"refreshing" the theme, not changing it at all. - - This way, as we are "refreshing" the theme, we still keep oursleves -inside the monolithic conception we are trying to be attached to (i.e., -one unique name, and one unique visual style for all visual -manifestations). - - Producing artistic motifs is a creative process that may consume long -time, specially for people without experienced knowledge on graphic -design land. Using "randomly generated" conception to produce artistic -motifs could be, practically, a way for anyone to follow in order to -produce maintainable artistic motifs in few steps. - - Due to the "randomly generated" nature of Flame filter, we find that -_Flame_ pattern is not always the same when we use _Flame_ filter -interface. - - Using the same pattern design for each visual manifestation is -essential in order to maintain the visual connection among all visual -manifestations inside the same theme. Occasionally, we may introduce -pattern variations in opacity, size, or even position but never change -the pattern design itself, nor the color information used by images -considered part of the same theme. - - *Important* When we design background images, which are considered - part of the same theme, it is essential to use the same design - pattern always. This is what makes theme images to be visually - connected among themeselves, and so, the reason we use to define - the word "theme" as: a set of images visually connected among - themeselves. - - In order for us to reproduce the same flame pattern always, _Flame_ -filter interface provides the `Save' and `Open' options. The `Save' -option brings up a file save dialog that allows you to save the current -Flame settings for the plug-in, so that you can recreate them later. -The `Open' option brings up a file selector that allows you to open a -previously saved Flame settings file. - - The Flame settings we used in our example are saved in the file: - - -trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def - -3.23.3 Construction -------------------- - -3.23.3.1 Step 1: Set image size -............................... - -Create an empty image and fill the `Background' layer with black -(`000000') color. Image dimensions depend on the final destination you -plan to use the image for. For the sake of our construction example we -used an image of 640x480 pixels and 300 pixels per inch (ppi). - -3.23.3.2 Step 2: Add base color and pattern information -....................................................... - -Create a new layer named `Base', place it over `Background' layer and -fill it with the base color (`7800ff') you want to have your background -image set in. Add a mask to `Base' layer using radial gradient and -blur it. You may need to repeat this step more than once in order to -achieve a confortable black radial degradation on the right side of -your design. - - Duplicate `Base' layer and name it `Paper'. Place `Paper' layer over -`Base' layer. Remove content of `Paper' layer and fill it with `Paper -(100x100)' pattern. Once you've done with black radial degradation, -reduce the `Paper' layer opacity to 20%. - - Notice that when we duplicate one layer, the mask information related -to layer is preserved from previous to next layer. This saves us some -of the time required to produce different layers with the same mask -information on them. - - Duplicate `Paper' layer and rename it `Stripes'. Remove paper -pattern from `Stripes' layer. Fill `Stripes' layer with `Stripes -(48x48)' pattern and reduce the `Stripes' layer opacity to 15%. - -3.23.3.3 Step 3: Add flame motif -................................ - -Create a new layer named `Flame'. Set the foreground (`003cff') and -background (`0084ff') colors to the gradient you want to build the -flame motif. - - To build flame motif, use the flame filter (`Filters > Render > -Nature > Flame...') on `Flame' layer. We used a layer mask, with a -radial gradient on it to control the boundaries of flame motif on -`Flame' layer. - - Duplicate `Flame' layer and rename it `Flame Blur'. Place `Flame -Blur' below `Flame' layer. Apply Gussian blur filter (`Filters > Blur > -Gussian Blur...') until reaching the desiered effect. - - The opacity value, in `Flame' layers, may vary from one image to -another based on the place the image will be finally placed on. For -example, images used as desktop background have the `Flame' layer -opacity set at 100% but `Flame Blur' is set to 70%. However, you may -find that background images used in anaconda progress slides have -opacity reduced differently, in order to reduce brightness in a way -that texts could look clean and readable over it. - -3.23.3.4 Step 4: Add foreground color -..................................... - -Create a new layer named `Color', place it on top of all visible layers -and fill it with plain color (`4c005a'). Reduce `Color' layer opacity -to 20%. You can use the `Color' layer to control the right side color -information you want to produce the image for. - - Duplicate `Flame' layer and create a new layer named `Color#1'. -Place `Color#1' layer on top of layer named `Color'. Remove the mask -information from `Color#1' layer and recreate a new one using an -inverted alpha channel as reference. Remove `Color#1' layer content -and fill it back with plain black (`000000') color. Reduce `Color#1' -opacity to 20%. In this step we created a mask to protect the flame -artistic motif from black color, so when we decrement or increment the -opacity of layer, the flame artistic motif wouldn't be affected, just -the environment suround it. - - When you set color information, remember that the same artistic motif -needs to be indexed to 14 and 16 colors, in order to produce Grub and -Syslinux visual manifestations respectively. Using many different -colors in the artistic motif may reduce the possibility of your design -to fix all different situations in. Likewise, using more colors in one -design, and less colors in another design will reduce the connectivity -among your designs, since color information is relevant to visual -identity. - - When you propagate your artistic motif visual style to different -visual manifestations of CentOS Project corporate visual identity, it -is up to you to find out justice and compromise among all possible -variables you may face. - -3.23.4 See also ---------------- - -3.24 trunk/Identity/Themes/Motifs/Modern -======================================== - -3.24.1 Presentation -------------------- - -3.24.2 Construction -------------------- - -3.24.3 Usage ------------- - - * ... - -3.24.4 See also ---------------- - -3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds -==================================================== - -3.25.1 Goals ------------- - - * Organize background images for Modern theme. - -3.25.2 Description ------------------- - -Inside `Motifs' directory, the `Backgrounds/' directory is used to -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 the import feautre of Inkscape. - - 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 (e.g. Anaconda), 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 artistic motif. - - Background images are linked (using the import feature of Inkscape) -inside almost all theme art works. This structure let you make -centralized changes on the visual identity and propagate them quickly -to other areas. - - In this structure you design background images for different screen -resolutions based on the theme artistic motif. - - You may create different artistic motifs propositions based on the -same conceptual idea. The conceptual idea is what defines a theme. -Artistic motifs are interpretations of that idea. - - Inside this directory artistic motifs are organized by name (e.g., -TreeFlower, Modern, etc.). - - Each artistic motif directory represents just one unique artistic -motif. - - The artistic motif is graphic design used as common pattern to -connect all visual manifestations inside one unique theme. The -artistic motif is based on a conceptual idea. Artistic motifs provide -visual style to themes. - - Designing artistic motifs is for anyone interested in creating -beautiful themes for CentOS. When building a theme for CentOS, the -first design you need to define is the artistic motif. - - Inside CentOS Artwork Repository, theme visual styles (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 `Motifs/' directory using the model name, and -the model directory structure as reference. - - The artistic motif base structure is used by `centos-art' to produce -images automatically. This section describes each directory of CentOS -artistic motif base structure. - -3.25.3 Usage ------------- - -The `Backgrounds/' directory is probably the core component, inside -`Motifs/' directory structure. Inside `Backgrounds/' directory you -produce background images used by almost all theme models (e.g., -Distribution, Websites, Promotion, etc.). The `Backgrounds/' directory -can contain subdirectories to help you organize the design process. - -3.25.4 See also ---------------- - -3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img -======================================================== - -3.26.1 Goals ------------- - - * ... - -3.26.2 Description ------------------- - -3.26.3 Usage ------------- - -In this directory is where you store all background images (e.g., .png, -.jpg, .xpm, etc.). This directory is required by `centos-art' command -line interface. - -3.26.4 See also ---------------- - -3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl -======================================================== - -3.27.1 Goals ------------- - - * ... - -3.27.2 Description ------------------- - -3.27.3 Usage ------------- - -In this directory is where you store all the scalable vector graphics -(e.g., .svg) files. This directory is required by `centos-art' command -line interface. - -3.27.4 See also ---------------- - -3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf -======================================================== - -3.28.1 Goals ------------- - - * ... - -3.28.2 Description ------------------- - - * ... - -3.28.3 Usage ------------- - -In this directory is where you store the project files (e.g, .xcf) of -Gimp. 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 background projects. Of course, you can merge both -Gimp and Inkscape power to produce images based on them. In this last -case you need the `Xcf/' directory. - -3.28.4 See also ---------------- - -3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress -================================================================= - -3.29.1 Goals ------------- - - * ... - -3.29.2 Description ------------------- - -3.29.3 Usage ------------- - -To render Anaconda progress slide images using the _Modern_ artistic -motif design, the Default theme model, and available translation files -(-- *Removed*(pxref:trunk Translations Identity Themes Distro Anaconda -Progress) --); use the following commands: - - cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ - centos-art render --identity - - The above command will create the following structure: - - trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress - |-- 3 - | |-- en - | | |-- 01-welcome.png - | | |-- 02-donate.png - | | `-- 03-yum.png - | `-- es - | |-- 01-welcome.png - | |-- 02-donate.png - | `-- 03-yum.png - |-- 4 - | |-- en - | | |-- 01-welcome.png - | | |-- 02-donate.png - | | `-- 03-yum.png - | `-- es - | |-- 01-welcome.png - | |-- 02-donate.png - | `-- 03-yum.png - `-- 5 - |-- en - | |-- 01-welcome.png - | |-- 02-donate.png - | `-- 03-yum.png - `-- es - |-- 01-welcome.png - |-- 02-donate.png - `-- 03-yum.png - -3.29.4 See also ---------------- - -3.30 trunk/Identity/Themes/Motifs/Modern/Palettes -================================================= - -3.30.1 Goals ------------- - - * Organize palette files for Modern theme. - -3.30.2 Description ------------------- - -3.30.3 Usage ------------- - -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 the unique color information required by theme. - -3.30.4 See also ---------------- - -3.31 trunk/Identity/Themes/Motifs/TreeFlower -============================================ - -3.31.1 Goals ------------- - - * ... - -3.31.2 Description ------------------- - -3.31.3 Usage ------------- - -3.31.4 See also ---------------- - -3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds -======================================================== - -3.32.1 Goals ------------- - -This section exists to orgnize backgrounds of _TreeFlower_ artistic -motif. - -3.32.2 Description ------------------- - -3.32.2.1 Desktop background -........................... - -Once you have defined the vectorial artistic motif design, use the -`centos-art.sh' script (as described in usage section below) to produce -the png version of it. With the png version of your vectorial design do -the following: - - Open the png version with GIMP. - - Save the png version as a project of GIMP inside -`trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Xcf' directory, -using the same name of your vectorial design but with the `.xcf' -extension. - - Now use GIMP to improve your design. Here you may add one layer for -pattern, another for colors, and so on until you find yourself -confortable with your artwork. For example, the following layer -distribution (from bottom to top) was used to build revision 285 of -file `1360x768.xcf' using _TreeFlower_ artistic motif at revision 241. - -*Layer 1: Background* - The first thing we did with GIMP was to create a layer named - `Background' to store the artistic motif (File > Open as layer). - This layer is the lowest layer in the image. Later, we started to - create layers one upon another to change the artistic motif visual - style. - -*Layer 2: Shadow#1* - This layer is above `Background' and contains a linear gradient - from left (000000) to right (transparent) covering the whole image. - This layer masks the artistic motif to avoid the effect of linear - gradient. This layer is 100% of opacity. - -*Layer 3: Shadow#2* - This layer is above `Shadow#1' and contains a linear gradient from - left (000000) to right (transparent) covering just the 70% of the - whole image aproximatly. This layer doesn't mask the artistic motif - which make the left part of it fall into the dark of linear - gradient. This layer is 100% of opacity. - -*Layer 4: Pattern (Paper)* - This layer is above `Shadow#2' an contains the paper pattern - shipped with GIMP 2.2. This layer doesn't mask the artistic motif - so the pattern is applied over the whole image. This layer is set - to 15% of opacity. - -*Layer 5: Pattern (Stripes)* - This layer is above `Pattern (Paper)' and contains the stripes - used over the artistic motif. This layer do masks the artistic - motif so the stripes are only applied to it. This layer is set to - 10% of opacity. - -*Layer 6: Shadow#3* - This layer is above `Pattern (Stripes)' and contains a linear - gradient from right (6600ff) to left (transparent). This layer - masks the artistic motif so the linear gradient doesn't affect it. - This layer is set to 15% of opacity. - -*Layer 7: Shadow#4* - This layer is above `Shadow#3' and contains a linear gradient from - left (000000) to right (transparent). This layer do masks the - artistic motif so the linear gradient doesn't affect it. This - layer is set to 10% of opacity. - -*Layer 8: Color#1* - This layer is above `Shadow#4' and is filled with orange (ffae00) - color over the whole image. This layer is set to 10% of opacity. - -*Layer 9: Color#2* - This layer is above `Color#1' and is filled with blue (010a88) - color over the whole image. This layer is set to 10% of opacity. - - - *Note* There is no definite combination. To get the appropriate - visual design is a matter of constant testing and personal taste. - - Finally, use `Save as copy ...' option to export the final design. -To export the final design use the same name of your vectorial design -plus `-final.png' extension. - - You can repeat these steps to create images for other screen -resolutions. - -3.32.2.2 Anaconda Prompt (syslinux) background -.............................................. - -When building syslinux backgrounds it is needed to take into account -that the final image is reduced to 16 colors. In desktop background -there is no color limitation but syslinux does have. The goal of this -section is achieving a final syslinux background as close as possible -to desktop backgrounds using 16 colors only. - - Another point to consider is the forground and background definition -used by syslinux. The syslinux documentation says that the color set in -position 0 is the background and color set in position 7 is the -forground. The final palette of color used by our background will match -that specification. For great contrast we'll use black as background -and white as forground. At this poing we have black (000000) and white -(ffffff) colors in our syslinux palette, which left us with 14 colors -to play with. - - Let's begin with `Xcf/640x300.xcf' layer distribution from bottom to -top: - -*Layer 1: Background* - This layer is the lowest layer in the image composition and - contains the artistic motif image rendered for the same resolution - (i.e., `Img/Png/640x300.png'). This layer is set to 100% of - opacity. - -*Layer 2: Pattern (Paper)* - This layer is placed above `Background' layer and contains the - paper pattern shipped with GIMP 2.2. This layer doesn't mask the - artistic motif. This layer is set to 30% of opacity. - -*Layer 3: Pattern (Stripes)* - This layer is placed above `Pattern (Paper)' layer and contains - the stripes pattern shipped with GIMP 2.2. This layer does mask the - artistic motif in order to apply the stripes over it only. The - background is not affected by the stripes pattern just the artistic - motif. This layer is set to 20% of opacity. - -*Layer 4: Shadow#1* - This layer is placed above `Pattern (Stripes)' layer and fills the - entire layer area with violet (6600ff) color. This layer do mask - the artistic motif in order to applied the violet color to the - background area outside the artistic motif only. This layer is set - to 15% of opacity. - -*Layer 5: Color#1* - This layer is above `Shadow#1' and is filled with orange (ffae00) - color to cover the whole image. This layer is set to 10% of - opacity. - -*Layer 6: Color#2* - This layer is above `Color#1' and is filled with blue (010a88) - color to cover the whole image. This layer is set to 10% of - opacity. - -*Layer 7: Shadow#2* - This layer is above `Color#1' and contains a linear gradient from - left (000000) to right (transparent) covering 70% of the image - approximately. - - - At this point we have the composition and should look like the -desktop backgrounds. Compared with desktop backgrounds there are some -differences in opacity. This is because in our testings the final color -information found with this composition produces an acceptable 16 color -image. Of course this is something we haven't seen yet. - - To define the color information of our current coposition, save the -syslinux background composition we've done using `File > Save as Copy -...' option in the following location: - - -trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Img/Png/640x300-final.png - - Now, create the final png version of syslinux backgrounds using the -following command: - - -centos-art render --entry=trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Prompt - - This command will create syslinux-splash final images for all major -releases of CentOS distribution the repository has been configured to. -The important files here are `syslinux-splash.png', other files may -contain the wrong information because we haven't defined yet the -correct color information to use. - - Open one `syslinux-splash.png' file with GIMP and use the `Image > -Mode > Indexed' to reduce image colors up to 16 colors, using the -`Generate optimum palette' feature of GIMP. If the image looks -aceptable after reducing colors, use the `Palettes' menu (Ctrl+P) of -GIMP to import a new palette from file and name it -`CentOS-TreeFlower-Syslinux'. Once you've saved the palette, the color -information is stored at: - - -~/.gimp-2.2/palettes/CentOS-TreeFlower-Syslinux.gpl - - You need to edit `CentOS-TreeFlower-Syslinux.gpl' file in order to -set the appropriate order of colors. Remember black (000000) in -position 0, and white (ffffff) in position 7. Other positions are -irrelevant. When editing this file you may find that color reduction -did not set black and white colors to their respective values exactly. -Change that manually. For example, consider the following palette: - - -GIMP Palette -Name: CentOS-TreeFlower-Syslinux -Columns: 16 -# - 0 0 0 Background (black) - 23 20 35 Untitled - 34 25 48 Untitled - 37 35 60 Untitled - 47 36 68 Untitled - 37 54 86 Untitled - 60 48 90 Untitled -255 255 255 Foreground (white) - 66 54 99 Untitled - 74 61 98 Untitled - 49 78 126 Untitled - 43 87 151 Untitled - 92 89 95 Untitled - 54 104 183 Untitled -158 153 156 Untitled -201 196 195 Untitled - - Update the `Palettes' menu to get the new color positions from the -file you just edited and open the palette with double click. - - Update the `syslinux.gpl' file copying the following file: - - -~/.gimp-2.2/palettes/CentOS-TreeFlower-Syslinux.gpl - - to - - -trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.gpl - - With the `CentOS-TreeFlower-Syslinux' palette opened in the `Palette -Editor', open (Ctrl+O) the following file: - - -trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.ppm - - and replace its color information with that one in -`CentOS-TreeFlower-Syslinux' palette. When you are replacing color -information inside `syslilnux.ppm', remember to keep the order of -colors just as they are in the `CentOS-TreeFlower-Palette' palette. - - The `syslinux.ppm' file is 16 pixels width and 1 pixel height, so -you probably need to zoom it a bit to set the color information in -their place when using the pen tool with the brush `Circle (01) (1 x -1)'. - - Once you've updated the `syslinux.ppm' file, it is time to update -the following file: - - -trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.hex - - The `syslinux.hex' file contains the color information in -hexadecimal notation. The color information in hexadecimal notation is -required by `ppmtolss16' command. The `ppmtolss16' command produces -the final LSS16 image format that is used by syslinux program inside -CentOS distribution. - - The color information inside `syslinux.hex' must match the one in -`syslinux.ppm' and `syslinux.gpl'. For example, based on -`CentOS-TreeFlower-Syslinux' palette of colors above, consider the -following `syslinux.hex' file: - - -#000000=0 -#171423=1 -#221930=2 -#25233c=3 -#2f2444=4 -#253656=5 -#3c305a=6 -#ffffff=7 -#423663=8 -#4a3d62=9 -#314e7e=10 -#2b5797=11 -#5c595f=12 -#3668b7=13 -#9e999c=14 -#c9c4c3=15 - -3.32.2.3 Grub background -........................ - -3.32.3 Usage ------------- - - * ... - -3.32.4 See also ---------------- - -3.33 trunk/Identity/Widgets -=========================== - -3.33.1 Goals ------------- - - * ... - -3.33.2 Description ------------------- - -3.33.3 Usage ------------- - -3.33.4 See also ---------------- - -3.34 trunk/Locales -================== - -The `trunk/Locales' directory exists to store the translation messages -used to produce content in different languages. - - Translation messages are organized using the directory structure of -the component being translated. For example, if we want to provide -translation messages for `trunk/Manuals/Filesystem', then the -`trunk/Locales/Manuals/Filesystem' directory needs to be created. - - Once the locale directory exists for the component we want to provide -translation messages for, it is necessary to create the translation -files where translation messages are. The translation files follows the -concepts of `xml2po' and GNU `gettext' tools. - - The basic translation process is as follow: first, translatable -strings are extracted from files and a portable object template (.pot) -is created or updated with the information. Using the portable object -template, a portable object (.po) is created or updated for translator -to locale the messages retrived. Finally, a machine object (.mo) is -created from portable object to sotore the translated messages. - - Inside the repository there are two ways to retrive translatable -strings from files. The first one is through `xml2po' command and the -second through `xgettext' command. The `xml2po' is used to retrive -translatable strings from XML files (e.g., Scalable Vector Graphics, -DocBook, etc.) and the `xgettext' command is used to retrive -translatable strings from shell scripts files (e.g., the files that -make the `centos-art.sh' command-line interface). - - When translatable strings are retrived from XML files, using the -`xml2po' command, there is no need to create the machine object as we -do when translatable strings ar retrived from shell files, using the -`xgettext' command. The `xml2po' produces a temporal machine object in -order to create a translated XML file. Once the translated XML file has -been created the machine object is no longer needed. On the other hand, -the machine object produced by the `xgettext' command is required by -the system in order for the show shell script localized messages. - - Another difference between `xml2po' and `xgettext' we need to be -aware of is the directory structure used to store machine objects. In -`xml2po', the machine object is created in the current working -directory as `.xml2po.mo' and can be safetly removed once the -translated XML file has been created. In the case of `xgettext', the -machine object needs to be stored in the -`$TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo' file in order for the -system to interpret it and should not be removed since it is the file -that contain the translation messages themselves. - - Automation of localization tasks is achived through the `locale' -functionality of command-line interface. - -3.35 trunk/Locales/Identity -=========================== - -3.35.1 Goals ------------- - - * ... - -3.35.2 Description ------------------- - - * ... - -3.35.3 Usage ------------- - - * ... - -3.35.4 See also ---------------- - -3.36 trunk/Locales/Identity/Brands -================================== - -3.36.1 Goals ------------- - - * Organize brands' translation files. - -3.36.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.36.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.36.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 designing ratio. - - For example, if your design template has 400x200 pixels of dimension, -and you apply a translation file named `300.sed' to it, the final image -you get as result will have 300x100 pixels of dimension. The same is -true if you use higher numbers like `1024.sed', `2048.sed', etc. In -these cases you have bigger images proportionally. - - As we are using scalable vector graphics to design identity -templates, the image size you produce is not limitted in size. You can -use one design template produced in 400x200 pixels to produce larger or -shorter PNG images using numeric translation files as described above. - -3.36.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. - - *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.36.3 Usage ------------- - -To render brands' translation files, use the following command: - - -centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands - -3.36.4 See also ---------------- - -3.37 trunk/Locales/Identity/Brands/Tpl -====================================== - -3.37.1 Goals ------------- - -3.37.2 Description ------------------- - -3.37.3 Usage ------------- - -3.37.4 See also ---------------- - -3.38 trunk/Locales/Identity/Fonts -================================= - -3.38.1 Goals ------------- - -This section exists to organize fonts translation files. - -3.38.2 Description ------------------- - -Translation files, inside `trunk/Translations/Fonts', have the -following structure: - - -s!font-family:Denmark!font-family:DejaVu LGC Sans! -s!font-weight:normal!font-weight:bold! -s!font-style:normal!font-style:italic! - - Inside `trunk/Translations/Fonts', there is one translation file for -each font preview image you want to produce. This way, we create one -translation file for each font-family we use somewhere inside CentOS -visual identity. - - *Important* Do not create translation files for font-families not - used somewhere inside CentOS visual identity. The identity of font - entry (*note trunk Identity Fonts::) is used as reference when - someone needs to know which font-families are allowed to use - inside CentOS visual identity. - -3.38.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.38.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.38.4 See also ---------------- - -3.39 trunk/Locales/Identity/Models -================================== - -3.39.1 Goals ------------- - -3.39.2 Description ------------------- - -3.39.3 Usage ------------- - -3.39.4 See also ---------------- - -3.40 trunk/Locales/Identity/Release -=================================== - -3.40.1 Goals ------------- - -3.40.2 Description ------------------- - -3.40.3 Usage ------------- - -3.40.4 See also ---------------- - -3.41 trunk/Locales/Identity/Themes -================================== - -3.41.1 Goals ------------- - -3.41.2 Description ------------------- - -3.41.3 Usage ------------- - -3.41.4 See also ---------------- - -3.42 trunk/Locales/Identity/Themes/Backgrounds -============================================== - -3.42.1 Goals ------------- - - * ... - -3.42.2 Description ------------------- - - * ... - -3.42.3 Usage ------------- - - * ... - -3.42.4 See also ---------------- - -3.43 trunk/Locales/Identity/Themes/Distro/Anaconda/Progress -=========================================================== - -3.43.1 Goals ------------- - - * Organize Anaconda progress translation templates. - - * Organize Anaconda progress translation files in several languages - and major releases of CentOS distribution. - -3.43.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. - - * *Note trunk Identity Themes Motifs Modern Distro Anaconda - Progress::. - -3.43.3 Usage ------------- - -Translation rendering is described in `trunk/Translations' -documentation entry (-- *Removed*(pxref:trunk Translations) --). - -3.43.4 See also ---------------- - -3.44 trunk/Locales/Identity/Widgets -=================================== - -3.44.1 Goals ------------- - - * ... - -3.44.2 Description ------------------- - - * ... - -3.44.3 Usage ------------- - - * ... - -3.44.4 See also ---------------- - -3.45 trunk/Manuals -================== - -3.45.1 Goals ------------- - - * ... - -3.45.2 Description ------------------- - - * ... - -3.45.3 Usage ------------- - - * ... - -3.45.4 See also ---------------- - -3.46 trunk/Scripts -================== - -3.46.1 Goals ------------- - -The `trunk/Scripts' directory exists to: - - * Organize the "trunk" development line of automation scripts by - programming language. - -3.46.2 Description ------------------- - - * ... - -3.46.3 Usage ------------- - - * ... - -3.46.4 See also ---------------- - -3.47 trunk/Scripts/Bash -======================= - -3.47.1 Goals ------------- - -The `trunk/Scripts/Bash' directory exists to organize the trunk -development line of `centos-art.sh' automation script. The -`centos-art.sh' script standardizes frequent tasks inside your working -copy of CentOS Artwork Repository. - -3.47.2 Description ------------------- - -The best way to understand `centos-art.sh' automation script is -studying its source code. However, as start point, you may prefer to -read an introductory resume before diving into the source code details. - - The `centos-art.sh' script is written in Bash. Most tasks, inside -`centos-art.sh' script, have been organized in many specific -functionalities that you can invoke from the `centos-art' command-line -interface. - - 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 location. If your system was prepared to use CentOS Artwork -Repository correctly (-- *Removed*(pxref:trunk Scripts Bash Functions -Verify) --), you should have a symbolic link inside `~/bin/' directory -that points to the `centos-art.sh' script file. As `~/bin/' directory -is, by default, inside PATH environment variable, the execution of -`centos-art' command runs the `centos-art.sh' script. - - When `centos-art.sh' script is executed, the first it does is -executing the `trunk/Scripts/Bash/initEnvironment.sh' script to -initialize global variables (e.g., `gettext' variables) and global -function scripts. Global function scripts are located inside -`trunk/Scripts/Bash/Functions' directory and their file names begin -with `cli'. Global function scripts provide common functionalities that -can be used anywhere inside `centos-art.sh' script execution -environment. - - Once global variables and function scripts have been loaded, -`centos-art.sh' script executes the `cli' global function from `cli.sh' -function script to retrive command-line arguments and define some -default values that may be used later by specific function scripts (-- -*Removed*(pxref:trunk Scripts Bash Functions) --). - - As convenction, the `centos-art.sh' command-line arguments have the -following format: - - -centos-art arg1 --arg2=val2 --arg3=val3 - - In the above example, `centos-art' is the command you use to invoke -`centos-art.sh' script. The `arg1' is required and represents the -functionality you want to perform (e.g., `verify', `render', `locale', -`manual', etc.). The remaining arguments are modifiers to `arg1'. The -`--arg2' definition is required and represets, specifically, the action -inside the functionality you want to perform. The `--arg3' and on, are -optional. - - Once command-line arguments have been retrived, the `centos-art.sh' -script loads specific functionalities using the `cli_getFunctions.sh' -function script. Only one specific functionality can be loaded at one -script execution I.e., you run `centos-art.sh' script to run just one -functionality. - - -+----------------------------------------------------------------------+ -| [centos@host]$ centos-art function --action='value' --option='value' | -+----------------------------------------------------------------------+ -| ~/bin/centos-art --> ~/artwork/trunk/Scripts/Bash/centos-art.sh | -+---v-----------------------------------------v------------------------+ - | centos-art.sh | - +---v---------------------------------v---+ - . | initEnvironment.sh | . - . +---------------------------------+ . - . | cli $@ | . - . +---v-------------------------v---+ . - . . | cli_getFunctions | . . - . . +---v-----------------v---+ . . - . . . | function1 | . . . - . . . | function2 | . . . - . . . | function3 | . . . - . . . +-----------------+ . . . - . . ........................... . . - . ................................... . - ........................................... - -Figure 3.1: The functionalities initialization environment. - - Functionalities are implemented by means of actions. Once the -functionality has been initiazalized, actions initialization take place -for that functionality. Actions initialization model is very similar to -functions initialization model. But with the difference, that actions -are loaded inside function environment, and so, share variables and -functions defined inside function environment. - - -+--------------------------------------+ -| cli_getFunctions | -+---v------------------------------v---+ -. | function1 | . -. +---v----------------------v---+ . -. . | function1_getActions | . . -. . +---v--------------v---+ . . -. . . | action 1 | . . . -. . . | action 2 | . . . -. . . | action n | . . . -. . . +--------------+ . . . -. . ........................ . . -. ................................ . -. +------------------------------+ . -. | function2 | . -. +---v----------------------v---+ . -. . | function2_getActions | . . -. . +---v--------------v---+ . . -. . . | action 1 | . . . -. . . | action 2 | . . . -. . . | action n | . . . -. . . +--------------+ . . . -. . ........................ . . -. ................................ . -. +------------------------------+ . -. | function3 | . -. +---v----------------------v---+ . -. . | function3_getActions | . . -. . +---v--------------v---+ . . -. . . | action 1 | . . . -. . . | action 2 | . . . -. . . | action n | . . . -. . . +--------------+ . . . -. . ........................ . . -. ................................ . -........................................ - -Figure 3.2: The actions initialization environment. - -3.47.3 Usage ------------- - -The `centos-art.sh' script usage information is described inside each -specific function documentation (-- *Removed*(pxref:trunk Scripts Bash -Functions) --). - -3.47.4 See also ---------------- - -3.48 trunk/Scripts/Bash/Cli -=========================== - -3.49 trunk/Scripts/Bash/Cli/Functions -===================================== - -3.49.1 Goals ------------- - -The `trunk/Scripts/Bash/Functions' directory exists to organize -`centos-art.sh' specific functionalities. - -3.49.2 Description ------------------- - -The specific functions of `centos-art.sh' script are designed with -"Software Toolbox" philosophy (*note Toolbox introduction: -(coreutils.info)Toolbox introduction.) in mind: each program "should do -one thing well". Inside `centos-art.sh' script, each specific -functionality is considered a program that should do one thing well. -Of course, if you find that they still don't do it, feel free to -improve them in order for them to do so. - - The specific functions of `centos-art.sh' script are organized -inside specific directories under `trunk/Scripts/Bash/Functions' -location. Each specific function directory should be named as the -function it represents, with the first letter in uppercase. For -example, if the function name is `render', the specific function -directory for it would be `trunk/Scripts/Bash/Functions/Render'. - - To better understand how specific functions of `centos-art.sh' -script are designed, lets create one function which only goal is to -output different kind of greetings to your screen. - - When we create specific functions for `centos-art.sh' script it is -crucial to know what these functions will do exactly and if there is -any function that already does what we intend to do. If there is no -one, it is good time to create them then. Otherwise, if functionalities -already available don't do what you exactly expect, contact their -authors and work together to improve them. - - *Tip* Join CentOS developers mailing list - to share your ideas. - - It is also worth to know what global functions and variables do we -have available inside `centos-art.sh' script, so advantage can be taken -from them. Global variables are defined inside global function scripts. -Global functions scripts are stored immediatly under -`trunk/Scripts/Bash/Functions' directory, in files begining with `cli' -prefix. - - OK, let's begin with our functionality example. - - What function name do we use? Well, lets use `greet'. Note that -`hello' word is not a verb; but an expression, a kind of greeting, an -interjection specifically. In contrast, `greet' is a verb and describes -what we do when we say `Hello!', `Hi!', and similar expressions. - - So far, we've gathered the following function information: - - -Name: greet -Path: trunk/Scripts/Bash/Functions/Greet -File: trunk/Scripts/Bash/Functions/Greet/greet.sh - - The `greet.sh' function script is the first file `centos-art.sh' -script loads when the `greet' functionality is called using commands -like `centos-art greet --hello='World''. The `greet.sh' function -script contains the `greet' function definition. - - Inside `centos-art.sh' script, as convenction, each function script -has one top commentary, followed by one blank line, and then one -function defintion below it only. - - Inside `centos-art.sh' script functions, top commentaries have the -following components: the functionality description, one-line for -copyright note with your personal information, the license under which -the function source code is released --the `centos-art.sh' script is -released as GPL, so do all its functions--, the `$Id$' keyword of -Subversion is later expanded by `svn propset' command. - - In our `greet' function example, top commentary for `greet.sh' -function script would look like the following: - - -#!/bin/bash -# -# greet.sh -- This function outputs different kind of greetings to -# your screen. Use this function to understand how centos-art.sh -# script specific functionalities work. -# -# Copyright (C) YEAR YOURFULLNAME -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -# General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 -# USA. -# -# ---------------------------------------------------------------------- -# $Id$ -# ---------------------------------------------------------------------- - - After top commentary, separated by one blank line, the `greet' -function definition would look like the following: - - -function greet { - - # Define global variables. - - # Define command-line interface. - greet_getActions - -} - - The first definition inside `greet' function, are global variables -that will be available along `greet' function execution environment. -This time we didn't use global variable definitions for `greet' -function execution environment, so we left that section empty. - - Later, we call `greet_getActions' function to define the -command-line interface of `greet' functionality. The command-line -interface of `greet' functionality defines what and how actions are -performed, based on arguments combination passed to `centos-art.sh' -script. - - -function greet_getActions { - - case "$ACTIONNAM" in - - --hello ) - greet_doHello - ;; - - --bye ) - greet_doBye - ;; - - * ) - cli_printMessage "`gettext "The option provided is not valid."`" - cli_printMessage "$(caller)" 'AsToKnowMoreLine' - - esac - -} - - The ACTIONNAM global variable is defined in `cli.sh' function script -and contains the value passed before the equal sign (i.e., `=') in the -second command-line argument of `centos-art.sh' script. For example, if -the second command-line argument is `--hello='World'', the value of -ACTIONNAM variable would be `--hello'. Using this configuration let us -deside which action to perform based on the action name passed to -`centos-art.sh' script as second argument. - - The `greet' function definition makes available two valid greetings -through `--hello' and `--bye' options. If no one of them is provided -as second command-line argument, the `*' case is evaluated instead. - - The `*' case and its two lines further on should always be present -in `_getActions.sh' function scripts, no matter what specific -functionality you are creating. This convenction helps the user to find -out documentation about current functionality in use, when no valid -action is provided. - - The `greet_doHello' and `greet_doBye' function definitions are the -core of `greet' specific functionality. In such function definitions -we set what our `greet' function really does: to output different kinds -of greetings. - - -function greet_doHello { - - cli_printMessage "`gettext "Hello"` $ACTIONVAL" - -} - - The `greet_doHello' function definition is stored in -`greet_doHello.sh' function script. - - -function greet_doBye { - - cli_printMessage "`gettext "Goodbye"` $ACTIONVAL" - -} - - The `greet_doBye' function definition is stored in the -`greet_doBye.sh' function script. - - Both `greet_doHello.sh' and `greet_doBye.sh' function scripts are -stored inside `greet' function directory path (i.e. -`trunk/Scripts/Bash/Functions/Greet'). - - The ACTIONVAL global variable is defined in `cli.sh' function script -and contains the value passed after the equal sign (i.e., `=') in the -second command-line argument of `centos-art.sh' script. For example, if -the second command-line argument is `--hello='World'', the value of -ACTIONVAL variable would be `World' without quotes. - - Let's see how `greet' specific functionality files are organzied -under `greet' function directory. To see file organization we use the -`tree' command: - - -trunk/Scripts/Bash/Functions/Greet -|-- greet_doBye.sh -|-- greet_doHello.sh -|-- greet_getActions.sh -`-- greet.sh - - To try the `greet' specific functionality we've just created, pass -the function name (i.e., `greet') as first argument to `centos-art.sh' -script, and any of the valid options as second argument. Some examples -are illustrated below: - - -[centos@projects ~]$ centos-art greet --hello='World' -Hello World -[centos@projects ~]$ centos-art greet --bye='World' -Goodbye World -[centos@projects ~]$ - - The word `World' in the examples above can be anything. In fact, -change it to have a little fun. - - Now that we have a specific function that works as we expect, it is -time to document it. To document `greet' specific functionality, we -use its directory path and the `manual' functionality (-- -*Removed*(pxref:trunk Scripts Bash Functions Manual) --) of -`centos-art.sh' script, just as the following command illustrates: - - -centos-art manual --edit=trunk/Scripts/Bash/Functions/Greet - - To have a well documented function helps user to understand how your -function really works, and how it should be used. When no valid action -is passed to a function, the `centos-art.sh' script uses the function -documentation entry as vehicle to communicate which the valid functions -are. When no documentation entry exists for a function, the -`centos-art.sh' script informs that no documentation entry exists for -such function and requests user to create it right at that time. - - Now that we have documented our function, it is time to translate its -output messages to different languages. To translate specific -functionality output messages to different languages we use the -`locale' functionality (-- *Removed*(pxref:trunk Scripts Bash Functions -Locale) --) of `centos-art.sh' script, just as the following command -illustrates: - - -centos-art locale --edit - - *Warning* To translate output messages in different languages, - your system locale information --as in `LANG' environment - variable-- must be set to that locale you want to produce - translated messages for. For example, if you want to produce - translated messages for Spanish language, your system locale - information must be set to `es_ES.UTF-8', or similar, first. - - Well, it seems that our example is rather complete by now. - - In `greet' function example we've described so far, we only use -`cli_printMessage' global function in action specific function -definitions in order to print messages, but more interesting things can -be achieved inside action specific function definitions. For example, -if you pass a directory path as action value in second argument, you -could retrive a list of files from therein, and process them. If the -list of files turns too long or you just want to control which files to -process, you could add the third argument in the form -`--filter='regex'' and reduce the amount of files to process using a -regular expression pattern. - - The `greet' function described in this section may serve you as an -introduction to understand how specific functionalities work inside -`centos-art.sh' script. With some of luck this introduction will also -serve you as motivation to create your own `centos-art.sh' script -specific functionalities. - - By the way, the `greet' functionality doesn't exist inside -`centos-art.sh' script yet. Would you like to create it? - -3.49.3 Usage ------------- - -3.49.3.1 Global variables -......................... - -The following global variables of `centos-art.sh' script, are available -for you to use inside specific functions: - - -- Variable: TEXTDOMAIN - Default domain used to retrieve translated messages. This value is - set in `initFunctions.sh' and shouldn't be changed. - - -- Variable: TEXTDOMAINDIR - Default directory used to retrieve translated messages. This value - is set in `initFunctions.sh' and shouldn't be changed. - - -- Variable: FUNCNAM - Define function name. - - Function names associate sets of actions. There is one set of - actions for each unique function name inside `centos-art.sh' - script. - - Dunction names are passed as first argument in `centos-art.sh' - command-line interface. For example, in the command `centos-art - render --entry=path/to/dir --filter=regex', the ACTION passed to - `centos-art.sh' script is `render'. - - When first argument is not provided, the `centos-art.sh' script - immediatly ends its execution. - - -- Variable: FUNCDIR - - -- Variable: FUNCDIRNAME - - -- Variable: FUNCSCRIPT - - -- Variable: FUNCCONFIG - - -- Variable: ACTIONNAM - Define action name. - - Each action name identifies an specific action to perform, inside - an specific function. - - Action name names aare passed as second argument in - `centos-art.sh' command-line interface. For example, in the - command `centos-art render --entry=path/to/dir --filter=regex', - the ACTIONNAM passed to `centos-art.sh' script is `--entry'. - - When second argument is not provided, the `centos-art.sh' script - immediatly ends its execution. - - -- Variable: ACTIONVAL - Define action value. - - Action values are associated to just one action name. Action values - contain the working copy entry over which its associated action - will be performed in. Working copy entries can be files or - directories inside the working copy. - - -- Variable: REGEX - Define regular expression used as pattern to build the list of - files to process. - - By default, REGEX variable is set to `.+' to match all files. - - Functions that need to build a list of files to process use the - option `--filter' to redefine REGEX variable default value, and - so, control the amount of files to process. - - -- Variable: ARGUMENTS - Define optional arguments. - - Optional arguments, inside `centos-art.sh' script, are considered - as all command-line arguments passed to `centos-art.sh' script, - from third argument position on. For example, in the command - `centos-art render --entry=path/to/dir --filter=regex' , the - optional arguments are from `--filter=regex' argument on. - - Optional arguments are parsed using `getopt' command through the - following base construction: - - - # Define short options we want to support. - local ARGSS="" - - # Define long options we want to support. - local ARGSL="filter:,to:" - - # Parse arguments using getopt(1) command parser. - cli_doParseArguments - - # Reset positional parameters using output from (getopt) argument - # parser. - eval set -- "$ARGUMENTS" - - # Define action to take for each option passed. - while true; do - case "$1" in - --filter ) - REGEX="$2" - shift 2 - ;; - --to ) - TARGET="$2" - shift 2 - ;; - * ) - break - esac - done - - Optional arguments provide support to command options inside - `centos-art.sh' script. For instance, consider the Subversion - (`svn') command, where there are many options (e.g., `copy', - `delete', `move', etc), and inside each option there are several - modifiers (e.g., `--revision', `--message', `--username', etc.) - that can be combined one another in their short or long variants. - - The ARGUMENTS variable is used to store arguments passed from - command-line for later use inside `centos-art.sh' script. Storing - arguments is specially useful when we want to run a command with - some specific options from them. Consider the following command: - - - centos-art path --copy=SOURCE --to=TARGET --message="The commit message goes here." --username='johndoe' - - In the above command, the `--message', and `--username' options - are specific to `svn copy' command. In such cases, options are not - interpreted by `centos-art.sh' script itself. Instead, the - `centos-art.sh' script uses `getopt' to retrive them and store - them in the ARGUMENTS variable for later use, as described in the - following command: - - - # Build subversion command to duplicate locations inside the - # workstation. - eval svn copy $SOURCE $TARGET --quiet $ARGUMENTS - - When `getopt' parses ARGUMENTS, we may use short options (e.g., - `-m') or long options (e.g., `--message'). When we use short - options, arguments are separated by one space from the option - (e.g., `-m 'This is a commit message.''). When we use long - options arguments are separated by an equal sign (`=') (e.g., - `--message='This is a commit message''). - - In order for `getopt' to parse ARGUMENTS correctly, it is required - to provide the short and long definition of options that will be - passed or at least supported by the command performing the final - action the function script exists for. - - As convenction, inside `centos-art.sh' script, short option - definitions are set in the ARGSS variable; and long option - definitions are set in the ARGSL variable. - - When you define short and long options, it may be needed to define - which of these option arguments are required and which not. To - define an option argument as required, you need to set one colon - `:' after the option definition (e.g., `-o m: -l message:'). On - the other hand, to define an option argument as not required, you - need to set two colons `::' after the option definition (e.g., `-o - m:: -l message::'). - - -- Variable: EDITOR - Default text editor. - - The `centos-art.sh' script uses default text `EDITOR' to edit - pre-commit subversion messages, translation files, configuration - files, script files, and similar text-based files. - - If `EDITOR' environment variable is not set, `centos-art.sh' - script uses `/usr/bin/vim' as default text editor. Otherwise, the - following values are recognized by `centos-art.sh' script: - - * `/usr/bin/vim' - - * `/usr/bin/emacs' - - * `/usr/bin/nano' - - If no one of these values is set in `EDITOR' environment variable, - `centos-art.sh' uses `/usr/bin/vim' text editor by default. - -3.49.3.2 Global functions -......................... - -Function scripts stored directly under `trunk/Scripts/Bash/Functions/' -directory are used to define global functions. Global functions can be -used inside action specific functionalities and or even be reused -inside themselves. This section provides introductory information to -global functions you can use inside `centos-art.sh' script. - - -- Function: cli_checkActionArguments - Validate action value (ACTIONVAL) variable. - - The action value variable can take one of the following values: - - 1. Path to one directory inside the local working copy, - - 2. Path to one file inside the local working copy, - - If another value different from that specified above is passed to - action value variable, the `centos-art.sh' script prints an error - message and ends script execution. - - -- Function: cli_checkFiles FILE [TYPE] - Verify file existence. - - `cli_checkFiles' receives a FILE absolute path and performs file - verification as specified in TYPE. When TYPE is not specified, - `cli_checkFiles' verifies FILE existence, no matter what kind of - file it be. If TYPE is specified, use one of the following values: - - `d' - `directory' - Ends script execution if FILE is not a directory. - - When you verify directories with cli_checkFiles, if directory - doesn't exist, `centos-art.sh' script asks you for - confirmation in order to create that directory. If you answer - positively, `centos-art.sh' script creates that directory and - continues script flows normally. Otherwise, if you answer - negatively, `centos-art.sh' ends script execution with an - error and documentation message. - - `f' - - `regular-file' - Ends script execution if FILE is not a regular file. - - `h' - `symbolic-link' - Ends script execution if FILE is not a symbolic link. - - `x' - `execution' - Ends script execution if FILE is not executable. - - `fh' - Ends script execution if FILE is neither a regular file nor a - symbolic link. - - `fd' - Ends script execution if FILE is neither a regular file nor a - directory. - - `isInWorkingCopy' - Ends script execution if FILE is not inside the working copy. - - As default behaviour, if FILE passes all verifications, - `centos-art.sh' script continues with its normal flow. - - -- Function: cli_commitRepoChanges [LOCATION] - Syncronize changes between repository and working copy. - - The `cli_commitRepoChanges' function brings changes from the - central repository down to the working copy--using `svn update'--, - checks the working copy changes--using `svn status' command--, - prints status report--using both `svn update' and `svn status' - commands output, and finally, commits recent changes from the - working copy up to the repository--using `svn commit' command--. - - Previous to commit the working copy changes up to the central - repository, the `cli_commitRepoChanges' function asks you to - verify changes--using `svn diff' command--, and later, another - confirmation question is shown to be sure you really want to - commit changes up to central repository. - - If LOCATION argument is not specified, the value of ACTIONVAL - variable is used as reference instead. - - - ---------------------------------------------------------------------- - --> Bringing changes from the repository into the working copy - --> Checking changes in the working copy - ---------------------------------------------------------------------- - Added 0 file from the repository. - Deleted 0 file from the repository. - Updated 0 file from the repository. - Conflicted 0 file from the repository. - Merged 0 file from the repository. - Modified 4 files from the working copy. - Unversioned 0 file from the working copy. - Deleted 0 file from the working copy. - Added 0 file from the working copy. - ---------------------------------------------------------------------- - - Figure 3.3: The `cli_commitRepoChanges' function output. - - Call the `cli_commitRepoChanges' function before or/and after - calling functions that modify files or directories inside the - working copy as you may need to. - - -- Function: cli_doParseArguments - Redefine arguments (ARGUMENTS) global variable using `getopt' - command output. For more information about how to use - `cli_doParseArguments' function, see ARGUMENTS variable - description above. - - -- Function: cli_doParseArgumentsReDef $@ - Initialize/reset arguments (ARGUMENTS) global variable using - positional parameters variable ($@) as reference. - - When we work inside function definitions, positional parameters are - reset to the last function definition positional parameters. If - you need to redefine positional parameters from one specific - function, you need to call `cli_doParseArgumentsReDef' with the - positional parameters variable ($@), set as first argument, to that - specific function you want to redefine positional parameters at. - - -- Function: cli_getArguments - Initialize function name (FUNCNAM), action name (ACTIONNAM), and - action value (ACTIONVAL) global variables, using positional - parameters passed in $@ variable. - - The `cli_getArguments' function is called from `cli.sh' function - script, using `cli' function positional parameters (i.e., the - positional parameters passed as arguments in the command-line) as - first function argument. - - Once command-line positional parameters are accesible to - `centos-art.sh' script execution evironment, `cli_getArguments' - uses regular expression to retrive action variables from first and - second argument. The first argument defines the value used as - function name (FUNCNAM), and the second argument defines both - values used as action name (ACTIONNAM) and action value - (ACTIONVAL), respectively. - - The first argument is a word in lower case. This word specifies the - name of the functionality you want to use (e.g., `render' to - render images, `manual' to work on documentation, and so on.) - - The second argument has a long option style (e.g., - `--option=value'). The `--option' represents the action name - (ACTIONNAM), and the characters inbetween the equal sign (`=') and - the first space character, are considered as the action value - (ACTIONVAL). In order to provide action values with space - characters inbetween you need to enclose action value with quotes - like in `--option='This is long value with spaces inbetween''. - Generally, action values are used to specify paths over which the - action name acts on. - - Once action related variables (i.e., FUNCNAM, ACTIONNAM, and - ACTIONVAL) are defined and validated, `cli_getArguments' shifts - the positional arguments to remove the first two arguments passed - (i.e., those used to retrive action related variables) and - redefine the arguments (ARGUMENTS) global variable with the new - positional parameters information. - - -- Function: cli_getFunctions - Initialize funtionalities supported by `centos-art.sh' script. - - Functionalities supported by `centos-art.sh' script are organized - in functionality directories under `trunk/Scripts/Bash/Functions/' - directory. Each functionality directory stores function scripts to - the functionality such directory was created for. Function scripts - contain function definitions. Function definitions contain - several commands focused on achieving one specific task only - (i.e., the one such functionality was created for). - - In order for `centos-art.sh' script to recognize a functionality, - such functionality needs to be stored under - `trunk/Scripts/Bash/Functions/' in a directory written capitalized - (i.e., the whole name is written in lowercase except the first - character which is in uppercase). The directory where one specific - functionality is stored is known as the `functionality directory'. - - Inside each functionality directory, the functionalty itself is - implemented through function scripts. Function scripts are - organized in files independently one another and written in - `camelCase' format with the function name as prefix. Separation - between prefix and description is done using underscore (`_') - character. - - In order for `centos-art.sh' script to load functionalities - correctly, function definition inside function scripts should be - set using the `function' reserved word, just as in the following - example: - - - function prefix_doSomething { - - # Do something here... - - } - - The above function definition is just a convenction we use, in - order to make identification of function names easier read and - automate by `centos-art.sh' script initialization commands, once - `centos-art.sh' script determines which functionality directory to - use. Specifically, in order to initialize and export functions, - `centos-art.sh' script executes all function scripts inside the - functionality directory, and later `grep' on them using a regular - expression pattern, where the `function' reserved word is used as - reference to retrive the function names and export them to - `centos-art.sh' script execution environment, and so, make - function definitions --from function scripts inside the - functionality directory-- available for further calls. - - If the functionality specified in the command-line first argument - doesn't have a functionality directory, `centos-art.sh' script - considers the functionality provided in the command-line as invalid - functionality and immediatly stops script execution with an error - message. - - In order to keep visual consistency among function scripts, please - consider using the following function script design model as - template for your own function scripts: - - - #!/bin/bash - # - # prefix_doSomething.sh -- This function illustrates function scripts - # design model you can use to create your own function scripts inside - # centos-art.sh script. - # - # Copyright (C) YEAR YOURFULLNAME - # - # This program is free software; you can redistribute it and/or modify - # it under the terms of the GNU General Public License as published by - # the Free Software Foundation; either version 2 of the License, or - # (at your option) any later version. - # - # This program is distributed in the hope that it will be useful, but - # WITHOUT ANY WARRANTY; without even the implied warranty of - # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU - # General Public License for more details. - # - # You should have received a copy of the GNU General Public License - # along with this program; if not, write to the Free Software - # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 - # USA. - # - # ---------------------------------------------------------------------- - # $Id$ - # ---------------------------------------------------------------------- - - function prefix_doSomething { - - # Do something here... - - } - - -- Function: cli_getCountryCodes [FILTER] - Output country codes supported by `centos-art.sh' script. - - The `cli_getCountryCodes' function outputs a list with country - codes as defined in ISO3166 standard. When FILTER is provided, - `cli_getCountryCodes' outputs country codes that match FILTER - regular expression pattern. - - -- Function: cli_getCountryName [FILTER] - Outputs country name supported by `centos-art.sh' script. - - The `cli_getCountryName' function reads one language locale code - in the format LL_CC and outputs the name of its related country as - in ISO3166. If filter is specified, `cli_getCountryName' returns - the country name that matches the locale code specified in FILTER, - exactly. - - -- Function: cli_getCurrentLocale - Output current locale used by `centos-art.sh' script. - - The `cli_getCurrentLocale' function uses `LANG' environment - variable to build a locale pattern that is later applied to - `cli_getLocales' function output in order to return the current - locale that `centos-art.sh' script works with. - - The current locale information, returned by - `cli_getCurrentLocale', is output from more specific to less - specific. For example, if `en_GB' locale exists in - `cli_getLocales' function output, the `en_GB' locale would take - precedence before `en' locale. - - Locale precedence selection is quite important in order to define - the locale type we use for message translations. For example, if - `en_GB' is used, we are also saying that the common language - specification for English language (i.e., `en') is no longer used. - Instead, we are using English non-common country-specific language - specifications like `en_AU', `en_BW', `en_GB', `en_US', etc., for - message translations. - - Use `cli_getCurrentLocale' function to know what current locale - information to use inside `centos-art.sh' script. - - -- Function: cli_getFilesList [LOCATION] - Output list of files to process. - - The `cli_getFilesList' function uses LOCATION variable as source - location to build a list of files just as specified by regular - expression (REGEX) global variable. Essentially, what the - `cli_getFilesList' function does is using `find' command to look - for files in the location (LOCATION) just as posix-egrep regular - expression (REGEX) specifies. - - If LOCATION is not specified when `cli_getFilesList' function is - called, the action value (ACTIONVAL) global variable is used as - location value instead. - - By default, if the regular expression (REGEX) global variable is - not redefined after its first definition in the `cli' function, - all files that match default regular expression value (i.e., `.+') - will be added to the list of files to process. Otherwise, if you - redefine the regular expression global variable after its first - definition in the `cli' function and before calling - `cli_getFilesList' function, the last value you specifed is used - instead. - - When you need to customize the regular expression (REGEX) global - variable value inside a function, do not redefine the global - variable (at least you be absolutly convinced you need to). - Instead, set the regular expression global variable as `local' to - the function you need a customized regular expression value for. - If we don't redefine the regular expression global variable as - local to the function, or use another name for the regular - expression variable (which is not very convenient in order to keep - the amount of names to remember low), you may experiment undesired - concantenation issues that make your regular expression to be - something different from that you expect them to be, specially if - the function where you are doing the variable redefinition is - called several times during the same script execution. - - As result, the `cli_getFilesList' re-defines the value of FILES - variable with the list of files the `find' command returned. As - example, consider the following construction: - - - function prefix_doSomething { - - # Initialize the list of files to process. - local FILES='' - - # Initialize location. - local LOCATION=/home/centos/artwork/trunk/Identity/Themes/Models/Default - - # Re-define regular expression to match scalable vector graphic - # files only. Note how we use the global value of REGEX to build a - # new local REGEX value here. - local REGEX="${REGEX}.*\.(svgz|svg)" - - # Redefine list of files to process. - cli_getFilesList $LOCATION - - # Process list of files. - for FILE in $FILES;do - cli_printMessages "$FILE" 'AsResponseLine' - # Do something else here on... - done - - } - - - -- Function: cli_getLangCodes [FILTER] - Outputs language codes supported by `centos-art.sh' script. - - `cli_getLangCodes' function outputs a list of language codes as - defined in ISO639 standard. When FILTER is provided, - `cli_getLangCodes' outputs language codes that match FILTER - regular expression pattern. - - -- Function: cli_getLangName [FILTER] - Outputs language names supported by `centos-art.sh' script. - - `cli_getLangName' function reads one language locale code in the - format LL_CC and outputs the language related name as in ISO639. If - filter is specified, `cli_getLangName' returns the language name - that matches the locale code specified in FILTER, exactly. - - -- Function: cli_getLocales - Output locale codes supported by `centos-art.sh' script. - - Occasionally, you use `cli_getLocales' function to add locale - information in non-common country-specific language (`LL_CC') - format for those languages (e.g., `bn_IN', `pt_BR', etc.) which - locale differences cannot be solved using common language - specifications (`LL') into one unique common locale specification - (e.g., `bn', `pt', etc.). - - -- Function: cli_getRepoName NAME TYPE - Sanitate file names. - - Inside `centos-art.sh' script, specific functionalities rely both - in `cli_getRepoName' and repository file system organization to - achieve their goals. Consider `cli_getRepoName' function as - central place to manage file name convenctions for other functions - inside `centos-art.sh' script. - - *Important* `cli_getRepoName' function doesn't verify file or - directory existence, for that purpose use `cli_checkFiles' - function instead. - - The NAME variable contains the file name or directory name you - want to sanitate. - - The TYPE variable specifies what type of sanitation you want to - perform on NAME. The TYPE can be one of the following values: - - `d' - `directory' - Sanitate directory NAMEs. - - `f' - - `regular-file' - Sanitate regular file NAMEs. - - Use `cli_getRepoName' function to sanitate file names and - directory names before their utilization. - - Use `cli_getRepoName' when you need to change file name - convenctions inside `centos-art.sh' script. - - When we change file name convenctions inside `cli_getRepoName' - what we are really changing is the way functions interpret - repository file system organization. Notice that when we change a - file name (e.g., a function name), it is necessary to update all - files where such file name is placed on. This may require a - massive substitution inside the repository, each time we change - name convenctions in the repository (-- *Removed*(pxref:trunk - Scripts Bash Functions Path) --, for more information). - - -- Function: cli_getRepoStatus [LOCATION] - Request repository status. - - This function requests the status of a LOCATION inside the working - copy using the `svn status' command and returns the first - character in the output line, just as described in `svn help - status'. If LOCATION is not a regular file or a directory, inside - the working copy, the `centos-art.sh' script prints a message and - ends its execution. - - Use this function to perform verifications based a repository - LOCATION status. - - -- Function: cli_getTemporalFile NAME - Output absolute path to temporal file NAME. - - The `cli_getTemporalFile' function uses `/tmp' directory as source - location to store temporal files, the `centos-art.sh' script name, - and a random identification string to let you run more than one - `centos-art.sh' script simultaneously on the same user session. - For example, due the following temporal file defintion: - - - cli_getTemporalFile $FILE - - If FILE name is `instance.svg' and the unique random string is - `f16f7b51-ac12-4b7f-9e66-72df847f12de', the final temporal file, - built from previous temporal file definition, would be: - - - /tmp/centos-art.sh-f16f7b51-ac12-4b7f-9e66-72df847f12de-instance.svg - - When you use the `cli_getTemporalFile' function to create temporal - files, be sure to remove temporal files created once you've ended - up with them. For example, consider the following construction: - - - for FILE in $FILES;do - - # Initialize temporal instance of file. - INSTANCE=$(cli_getTemporalFile $FILE) - - # Do something ... - - # Remove temporal instance of file. - if [[ -f $INSTANCE ]];then - rm $INSTANCE - fi - - done - - Use the `cli_getTemporalFile' function whenever you need to create - temporal files inside `centos-art.sh' script. - - -- Function: cli_getThemeName - Output theme name. - - In order for `cli_getThemeName' function to extract theme name - correctly, the ACTIONVAL variable must contain a directory path - under `trunk/Identity/Themes/Motifs/' directory structure. - Otherwise, `cli_getThemeName' returns an empty string. - - -- Function: cli_printMessage MESSAGE [FORMAT] - Define standard output message definition supported by - `centos-art.sh' script. - - When FORMAT is not specified, `cli_printMessage' outputs - information just as it was passed in MESSAGE variable. Otherwise, - FORMAT can take one of the following values: - - `AsHeadingLine' - To print heading messages. - ---------------------------------------------------------------------- - $MESSAGE - ---------------------------------------------------------------------- - - `AsWarningLine' - To print warning messages. - ---------------------------------------------------------------------- - WARNING: $MESSAGE - ---------------------------------------------------------------------- - - `AsNoteLine' - To print note messages. - ---------------------------------------------------------------------- - NOTE: $MESSAGE - ---------------------------------------------------------------------- - - `AsUpdatingLine' - To print `Updating' messages on two-columns format. - Updating $MESSAGE - - `AsRemovingLine' - To print `Removing' messages on two-columns format. - Removing $MESSAGE - - `AsCheckingLine' - To print `Checking' messages on two-columns format. - Checking $MESSAGE - - `AsCreatingLine' - To print `Creating' messages on two-columns format. - Creating $MESSAGE - - `AsSavedAsLine' - To print `Saved as' messages on two-columns format. - Saved as $MESSAGE - - `AsLinkToLine' - To print `Linked to' messages on two-columns format. - Linked to $MESSAGE - - `AsMovedToLine' - To print `Moved to' messages on two-columns format. - Moved to $MESSAGE - - `AsTranslationLine' - To print `Translation' messages on two-columns format. - Translation $MESSAGE - - `AsConfigurationLine' - To print `Configuration' messages on two-columns format. - Configuration $MESSAGE - - `AsResponseLine' - To print response messages on one-column format. - --> $MESSAGE - - `AsRequestLine' - To print request messages on one-column format. Request - messages output messages with one colon (`:') and without - trailing newline (`\n') at message end. - $MESSAGE: - - `AsYesOrNoRequestLine' - To print `yes or no' request messages on one-column format. If - something different from `y' is answered (when using - `en_US.UTF-8' locale), script execution ends immediatly. - - - $MESSAGE [y/N]: - - When we use `centos-art.sh' script in a locale different from - `en_US.UTF-8', confirmation answer may be different from `y'. - For example, if you use `es_ES.UTF-8' locale, the - confirmation question would look like: - - - $MESSAGE [s/N]: - - and the confirmation answer would be `s', as it is on Spanish - `sí' word. - - Definition of which confirmation word to use is set on - translation messages for your specific locale information. -- - *Removed*(xref:trunk Scripts Bash Functions Locale) --, for - more information about locale-specific translation messages. - - `AsToKnowMoreLine' - To standardize `to know more, run the following command:' - messages. When the `AsToKnowMoreLine' option is used, the - MESSAGE value should be set to `"$(caller)"'. `caller' is a - Bash builtin that returns the context of the current - subroutine call. `AsToKnowMoreLine' option uses `caller' - builtin output to build documentation entries dynamically. - - - ---------------------------------------------------------------------- - To know more, run the following command: - centos-art manual --read='path/to/dir' - ---------------------------------------------------------------------- - - Use `AsToKnowMoreLine' option after errors and for intentional - script termination. - - `AsRegularLine' - To standardize regular messages on one-column format. - - When MESSAGE contains a colon inside (e.g., `description: - message'), the `cli_printMessage' function outputs MESSAGE on - two-columns format. - - Use `cli_printMessage' function whenever you need to output - information from `centos-art.sh' script. - - *Tip* To improve two-columns format, change the following - file: - trunk/Scripts/Bash/Styles/output_forTwoColumns.awk - -3.49.3.3 Specific functions -........................... - -The following specific functions of `centos-art.sh' script, are -available for you to use: - -3.49.4 See also ---------------- - -3.50 trunk/Scripts/Bash/Cli/Functions/Help -========================================== - -3.50.1 Goals ------------- - - * ... - -3.50.2 Description ------------------- - - * ... - -3.50.3 Usage ------------- - - * ... - -3.50.4 See also ---------------- - -3.51 trunk/Scripts/Bash/Cli/Functions/Html -========================================== - -3.51.1 Goals ------------- - - * ... - -3.51.2 Description ------------------- - - * ... - -3.51.3 Usage ------------- - - * ... - -3.51.4 See also ---------------- - -3.52 trunk/Scripts/Bash/Cli/Functions/Locale -============================================ - -3.52.1 Goals ------------- - - * ... - -3.52.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 finishd PO file edition and quit text editor, the -`centos-art' command creates the related machine object in the location -`$CLI_LANG/LC_MESSAGES/$TEXTDOMAIN.mo'. - - At this point, all translations you made in the PO file should be -available to your language when runing `centos-art.sh' script. - - In order to make the `centos-art.sh' internationalization, the -`centos-art.sh' script was modified as described in the `gettext' info -documentation (`info gettext'). You can find such modifications in the -following files: - - * `trunk/Scripts/Bash/initFunctions.sh' - - * `trunk/Scripts/Bash/Functions/Help/cli_localeMessages.sh' - - * `trunk/Scripts/Bash/Functions/Help/cli_localeMessagesStatus.sh' - - * ... - -3.52.3 Usage ------------- - -`centos-art locale --edit' - Use this command to translate command-line interface output - messages in the current system locale you are using (as specified - in `LANG' environment variable). - -`centos-art locale --list' - Use this command to see the command-line interface locale report. - -3.52.4 See also ---------------- - -3.53 trunk/Scripts/Bash/Cli/Functions/Manual -============================================ - -3.53.1 Goals ------------- - - * ... - -3.53.2 Description ------------------- - - * ... - -3.53.3 Usage ------------- - - * ... - -3.53.4 See also ---------------- - -3.54 trunk/Scripts/Bash/Cli/Functions/Path -========================================== - -3.54.1 Goals ------------- - -This section exists to organize files related to `path' -functiontionality. The `path' functionality standardizes movement, -syncronization, branching, tagging, and general file maintainance -inside the repository. - -3.54.2 Description ------------------- - -_"CentOS like trees, has roots, trunk, branches, leaves and flowers. -Day by day they work together in freedom, ruled by the laws of nature -and open standards, to show the beauty of its existence."_ - -3.54.2.1 Repository layout -.......................... - -The repository layout describes organization of files and directories -inside the repository. The repository layout provides the standard -backend required for automation scripts to work correctly. If such -layout changes unexpectedly, automation scripts may confuse themselves -and stop doing what we expect from them to do. - - As convenction, inside CentOS Artwork Repository, we organize files -and directories related to CentOS corporate visual identity under three -top level directories named: `trunk/', `branches/', and `tags/'. - - The `trunk/' directory (*note trunk::) organizes the main -development line of CentOS corporate visual identity. Inside `trunk/' -directory structure, the CentOS corporate visual identity concepts are -implemented using directories. There is one directory level for each -relevant concept inside the repository. The `trunk/' directory -structure is mainly used to perform development tasks related to CentOS -corporate visual identity. - - The `branches/' directory (*note branches::) oranizes parallel -development lines to `trunk/' directory. The `branches/' directory is -used to set points in time where develpment lines are devided one from -another taking separte and idependent lives that share a common past -from the point they were devided on. The `branches/' directory is -mainly used to perform quality assurance tasks related to CentOS -corporate visual identity. - - The `tags/' directory (*note tags::) organizes parallel frozen lines -to `branches/' directory. The parallel frozen lines are immutable, -nothing change inside them once they has been created. The `tags/' -directory is mainly used to publish final releases of CentOS corporate -visual identity. - - The CentOS Artwork Repository layout is firmly grounded on a -Subversion base. Subversion (`http://subversion.tigris.org') is a -version control system, which allows you to keep old versions of files -and directories (usually source code), keep a log of who, when, and why -changes occurred, etc., like CVS, RCS or SCCS. Subversion keeps a -single copy of the master sources. This copy is called the source -"repository"; it contains all the information to permit extracting -previous versions of those files at any time. - -3.54.2.2 Repository name convenctions -..................................... - -Repository name convenctions help us to maintain consistency of names -inside the repository. - - Repository name convenctions are applied to files and directories -inside the repository layout. As convenction, inside the repository -layout, file names are all written in lowercase (`01-welcome.png', -`splash.png', `anaconda_header.png', etc.) and directory names are all -written capitalized (e.g., `Identity', `Themes', `Motifs', `TreeFlower', -etc.). - - Repository name convenctions are implemented inside the -`cli_getRepoName' function of `centos-art.sh' script. With -`cli_getRepoName' function we reduce the amount of commands and -convenctions to remember, concentrating them in just one single place -to look for fixes and improvements. - -3.54.2.3 Repository work flow -............................. - -Repository work flow describes the steps and time intervals used to -produce CentOS corporate visual identity inside CentOS Artwork -Repository. - - To illustrate repository work flow let's consider themes' development -cycle. - - Initially, we start working themes on their trunk development line -(e.g., `trunk/Identity/Themes/Motifs/TreeFlower/'), here we organize -information that cannot be produced automatically (i.e., background -images, concepts, color information, screenshots, etc.). - - Later, when theme trunk development line is considered "ready" for -implementation (e.g., all required backgrounds have been designed), we -create a branch for it (e.g., -`branches/Identity/Themes/Motifs/TreeFlower/1/'). Once the branch has -been created, we forget that branch and continue working the trunk -development line while others (e.g., an artwork quality assurance team) -test the new branch for tunning it up. - - Once the branch has been tunned up, and considered "ready" for -release, it is freezed under `tags/' directory (e.g., -`tags/Identity/Themes/Motifs/TreeFower/1.0/') for packagers, -webmasters, promoters, and anyone who needs images from that CentOS -theme the tag was created for. - - Both branches and tags, inside CentOS Artwork Repository, use -numerical values to identify themselves under the same location. -Branches start at one (i.e., `1') and increment one unit for each -branch created from the same trunk development line. Tags start at -zero (i.e., `0') and increment one unit for each tag created from the -same branch development line. - - *Convenction* Do not freeze trunk development lines using tags - directly. If you think you need to freeze a trunk development - line, create a branch for it and then freeze that branch instead. - - The trunk development line may introduce problems we cannot see -immediatly. Certainly, the high changable nature of trunk development -line complicates finding and fixing such problems. On the other hand, -the branched development lines provide a more predictable area where -only fixes/corrections to current content are commited up to repository. - - If others find and fix bugs inside the branched development line, we -could merge such changes/experiences back to trunk development line -(not visversa) in order for future branches, created from trunk, to -benefit. - - Time intervals used to create branches and tags may vary, just as -different needs may arrive. For example, consider the release schema of -CentOS distribution: one major release every 2 years, security updates -every 6 months, support for 7 years long. Each time a CentOS -distribution is released, specially if it is a major release, there is -a theme need in order to cover CentOS distribution artwork -requirements. At this point, is where CentOS Artwork Repository comes -up to scene. - - Before releasing a new major release of CentOS distribution we create -a branch for one of several theme development lines available inside -the CentOS Artwork Repository, perform quality assurance on it, and -later, freeze that branch using tags. Once a the theme branch has been -frozen (under `tags/' directory), CentOS Packagers (the persons whom -build CentOS distribution) can use that frozen branch as source -location to fulfill CentOS distribution artwork needs. The same applies -to CentOS Webmasters (the persons whom build CentOS websites), and any -other visual manifestation required by the project. - -3.54.2.4 Parallel directories -............................. - -Inside CentOS Artwork Repository, parallel directories are simple -directory entries built from a common parent directory and placed in a -location different to that, the common parent directory is placed on. -Parallel directories are useful to create branches, tags, translations, -documentation, pre-rendering configuration script, and similar -directory structures. - - Parallel directories take their structure from one unique parent -directory. Inside CentOS Artwork Repository, this unique parent -directory is under `trunk/Identity' location. The `trunk/Identity' -location must be considered the reference for whatever information you -plan to create inside the repository. - - In some circumstances, parallel directories may be created removing -uncommon information from their paths. Uncommon path information refers -to those directory levels in the path which are not common for other -parallel directories. For example, when rendering -`trunk/Identity/Themes/Motifs/TreeFlower/Distro' directory structure, -the `centos-art.sh' script removes the `Motifs/TreeFlower/' directory -levels from path, in order to build the parallel directory used to -retrived translations, and pre-rendering configuration scripts required -by `render' functionality. - - Another example of parallel directory is the documentation structure -created by `manual' functionality. This time, `centos-art.sh' script -uses parallel directory information with uncommon directory levels to -build the documentation entry required by Texinfo documentation system, -inside the repository. - - Othertimes, parallel directories may add uncommon information to -their paths. This is the case we use to create branches and tags. When -we create branches and tags, a numerical identifier is added to parallel -directory structure path. The place where the numerical identifier is -set on is relevant to corporate visual identity structure and should be -carefully considered where it will be. - - When one parent directory changes, all their related parallel -directories need to be changed too. This is required in order for -parallel directories to retain their relation with the parent directory -structure. In the other hand, parallel directories should never be -modified under no reason but to satisfy the relation to their parent -directory structure. Liberal change of parallel directories may -suppresses the conceptual idea they were initially created for; and -certainly, things may stop working the way they should do. - -3.54.2.5 Syncronizing path information -...................................... - -Parallel directories are very useful to keep repository organized but -introduce some complications. For instance, consider what would happen -to functionalities like `manual' (`trunk Scripts Bash Functions -Manual') that rely on parent directory structures to create -documentation entries (using parallel directory structures) if one of -those parent directory structures suddenly changes after the -documentation entry has been already created for it? - - In such cases, functionalities like `manual' may confuse themselves -if path information is not updated to reflect the relation with its -parent directory. Such functionalities work with parent directory -structure as reference; if a parent directory changes, the -functionalities dont't even note it because they work with the last -parent directory structure available in the repository, no matter what -it is. - - In the specific case of documentation (the `manual' functionality), -the problem mentioned above provokes that older parent directories, -already documented, remain inside documentation directory structures as -long as you get your hands into the documentation directory structure -(`trunk/Manuals') and change what must be changed to match the new -parent directory structure. - - There is no immediate way for `manual', and similar functionalities -that use parent directories as reference, to know when and how -directory movements take place inside the repository. Such information -is available only when the file movement itself takes place inside the -repository. So, is there, at the moment of moving files, when we need -to syncronize parallel directories with their unique parent directory -structure. - - *Warning* There is not support for URL reference inside - `centos-art.sh' script. The `centos-art.sh' script is designed to - work with local files inside the working copy only. - - As CentOS Artwork Repository is built over a version control system, -file movements inside the repository are considered repository changes. -In order for these repository changes to be versioned, we need to, -firstly, add changes into the version control system, commit them, and -later, perform movement actions using version control system commands. -This configuration makes possible for everyone to know about changes -details inside the repository; and if needed, revert or update them -back to a previous revision. - - Finally, once all path information has been corrected, it is time to -take care of information inside the files. For instance, considere what -would happen if you make a reference to a documentation node, and later -the documentation node you refere to is deleted. That would make -Texinfo to produce error messages at export time. So, the -`centos-art.sh' script needs to know when such changes happen, in a way -they could be noted and handled without producing errors. - -3.54.2.6 What is the right place to store it? -............................................. - -Occasionly, you may find that new corporate visual identity components -need to be added to the repository. If that is your case, the first -question you need to ask yourself, before start to create directories -blindly all over, is: What is the right place to store it? - - The CentOS Community different free support vains (see: -`http://wiki.centos.org/GettingHelp') are the best place to find -answers to your question, but going there with hands empty is not good -idea. It may give the impression you don't really care about. Instead, -consider the following suggestions to find your own comprehension and -so, make your propositions based on it. - - When we are looking for the correct place to store new files, to bear -in mind the corporate visual identity structure used inside the CentOS -Artwork Repository (*note trunk Identity::) would be probaly the best -advice we could offer, the rest is just matter of choosing appropriate -names. To illustrate this desition process let's consider the -`trunk/Identity/Themes/Motifs/TreeFlower' directory as example. It is -the trunk development line of _TreeFlower_ artistic motif. Artistic -motifs are considered part of themes, which in turn are considered part -of CentOS corporate visual identity. - - When building parent directory structures, you may find that reaching -an acceptable location may take some time, and as it uses to happen -most of time; once you've find it, that may be not a definite solution. -There are many concepts that you need to play with, in order to find a -result that match the conceptual idea you try to implement in the new -directory location. To know which these concepts are, split the -location in words and read its documentation entry from less specific -to more specific. - - For example, the `trunk/Identity/Themes/Motifs/TreeFlower' location -evolved through several months of contant work and there is no certain -it won't change in the future, even it fixes quite well the concept we -are trying to implement. The concepts used in -`trunk/Identity/Themes/Distro/Motifs/TreeFlower' location are described -in the following commands, respectively: - - -centos-art manual --read=turnk/ -centos-art manual --read=turnk/Identity/ -centos-art manual --read=turnk/Identity/Themes/ -centos-art manual --read=turnk/Identity/Themes/Motifs/ -centos-art manual --read=turnk/Identity/Themes/Motifs/TreeFlower/ - - Other location concepts can be found similary as we did above, just -change the location we used above by the one you are trying to know -concepts for. - -3.54.3 Usage ------------- - -`centos-art path --copy='SRC' --to='DST'' - Copy `SRC' to `DST' and schedule `DST' for addition (with - history). In this command, `SRC' and `DST' are both working copy - (WC) entries. - -`centos-art path --delete='SRC'' - Delete `DST'. In order for this command to work the file or - directory you intend to delete should be under version control - first. In this command, `SRC' is a working copy (WC) entry. - - -3.54.4 See also ---------------- - -3.55 trunk/Scripts/Bash/Cli/Functions/Render -============================================ - -The `render' functionality exists to produce both identity and -translation files on different levels of information (i.e., different -languages, release numbers, architectures, etc.). - - The `render' functionality relies on "renderable directory -structures" to produce files. Renderable directory structures can be -either "identity directory structures" or "translation directory -structures" with special directories inside. - -3.55.1 Renderable identity directory structures ------------------------------------------------ - -Renderable identity directory structures are the starting point of -identity rendition. Whenever we want to render a component of CentOS -corporate visual identity, we need to point `centos-art.sh' to a -renderable identity directory structure. If such renderable identity -directory structure doesn't exist, then it is good time to create it. - - Inside the working copy, one renderable identity directory structures -represents one visual manifestation of CentOS corporate visual -identity, or said differently, each visual manifestation of CentOS -corporate visual identity should have one renderable identity directory -structure. - - Inside renderable identity directory structures, `centos-art.sh' can -render both image-based and text-based files. Specification of whether -a renderable identity directory structure produces image-based or -text-based content is a configuration action that takes place in the -pre-rendition configuration script of that renderable identity -directory structure. - - Inside renderable identity directory structures, content production -is organized in different configurations. A content production -configuration is a unique combination of the components that make an -identity directory structure renderable. One content production -configuration does one thing only (e.g., to produce untranslated -images), but it can be extended (e.g., adding translation files) to -achieve different needs (e.g., to produce translated images). - -3.55.1.1 Design template without translation -............................................ - -The design template without translation configuration is based on a -renderable identity directory structure with an empty translation -directory structure. In this configuration, one design template -produces one untranslated file. Both design templates and final -untranslated files share the same file name, but they differ one -another in file-type and file-extension. - - For example, to produce images without translations (there is no much -use in producing text-based files without translations), consider the -following configuration: - -*One renderable identity directory structure:* - In this example we used `Identity/Path/To/Dir' as the identity - component we want to produce untranslated images for. Identity - components can be either under `trunk/' or `branches/' directory - structure. - - The identity component (i.e., `Identity/Path/To/Dir', in this - case) is also the bond component we use to connect the identity - directory structures with their respective auxiliar directories - (i.e., translation directory structres and pre-rendition - configuration structures). The bond component is the path - convenction that `centos-art.sh' uses to know where to look for - related translations, configuration scripts and whatever auxiliar - thing a renderable directory structure may need to have. - - - | The bond component - |----------------->| - trunk/Identity/Path/To/Dir <-- Renderable identity directory structure. - |-- Tpl <-- Design template directory. - | `-- file.svg <-- Design template file. - `-- Img <-- Directory used to store final files. - `-- file.png <-- Final image-based file produced from - design template file. - - Inside design template directory, design template files are based - on SVG (Scalable Vector Graphics) and use the extension `.svg'. - Design template files can be organized using several directory - levels to create a simple but extensible configuration, specially - if translated images are not required. - - In order for SVG (Scalable Vector Graphics) files to be considered - "design template" files, they should be placed under the design - template directory and to have set a `CENTOSARTWORK' object id - inside. - - The `CENTOSARTWORK' word itself is a convenction name we use to - define which object/design area, inside a design template, the - `centos-art.sh' script will use to export as PNG (Portable Network - Graphic) image at rendition time. Whithout such object id - specification, the `centos-art.sh' script cannot know what - object/design area you (as designer) want to export as PNG - (Portable Network Graphic) image file. - - *Note* At rendition time, the content of `Img/' directory - structure is produced by `centos-art.sh' automatically. - - When a renderable identity directory structure is configured to - produce image-based content, `centos-art.sh' produces PNG - (Portable Network Graphics) files with the `.png' extension. Once - the base image format has been produced, it is possible for - `centos-art.sh' to use it in order to automatically create other - image formats that may be needed (-- *Removed*(pxref:trunk Scripts - Bash Functions Render Config) --). - - Inside the working copy, you can find an example of "design - template without translation" configuration at - `trunk/Identity/Models/'. - - *Note trunk Identity::, for more information. - -*One translation directory structure:* - In order for an identity entry to be considered an identity - renderable directory structure, it should have a translation - entry. The content of the translation entry is relevant to - determine how to process the identity renderable directory entry. - - If the translation entry is empty (i.e., there is no file inside - it), `centos-art.sh' interprets the identity renderable directory - structure as a "design templates without translation" - configuration. - - - | The bond component - |----------------->| - trunk/Translations/Identity/Path/To/Dir - `-- (empty) - - If the translation entry is not empty, `centos-art.sh' can - interpret the identity renderable directory structure as one of the - following configurations: "design template with translation - (one-to-one)" or "design template with translation (optimized)". - Which one of these configurations is used depends on the value - assigned to the matching list (MATCHINGLIST) variable in the - pre-rendition configuration script of the renderable identity - directory structure we are producing images for. - - If the matching list variable is empty (as it is by default), then - "design template with translation (one-to-one)" configuration is - used. In this configuration it is required that both design - templates and translation files have the same file names. This - way, _one_ translation files is applied to _one_ design template, - to produce _one_ translated image. - - If the matching list variable is not empty (because you redefine - it in the pre-rendition configuration script), then "design - template with translation (optimized)" configuration is used - instead. In this configuration, design templates and translation - files don't need to have the same names since such name - relationship between them is specified in the matching list - properly. - - -- *Removed*(xref:trunk Translations) --, for more information. - -*One pre-rendition configuration script:* - In order to make an identity directory structure renderable, a - pre-rendition configuration script should exist for it. The - pre-rendition configuration script specifies what type of rendition - does `centos-art.sh' will perform over the identity directory - structure and how does it do that. - - - | The bond component - |----------------->| - trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir - `-- render.conf.sh - - In this configuration the pre-rendition configuration script - (`render.conf.sh') would look like the following: - - - function render_loadConfig { - - # Define rendition actions. - ACTIONS[0]='BASE:renderImage' - - } - - Since translation directory structure is empty, `centos-art.sh' - assumes a "design template without translation" configuration to - produce untranslated images. - - To produce untranslated images, `centos-art.sh' takes one design - template and creates one temporal instance from it. Later, - `centos-art.sh' uses the temporal design template instance as - source file to export the final untranslated image. The action of - exporting images from SVG (Scalable Vector Graphics) to PNG - (Portable Network Graphics) is possible thanks to Inkscape's - command-line interface and the `CENTOSARTWORK' object id we - previously set inside design templates. - - - centos-art.sh render --identity=trunk/Identity/Path/To/Dir - ------------------------------------------------- - 0 | Execute centos-art.sh on renderable identity directory structure. - --v---------------------------------------------- - trunk/Identity/Path/To/Dir/Tpl/file.svg - ------------------------------------------------- - 1 | Create instance from design template. - --v---------------------------------------------- - /tmp/centos-art.sh-a07e824a-5953-4c21-90ae-f5e8e9781f5f-file.svg - ------------------------------------------------- - 2 | Render untranslated image from design template instance. - --v---------------------------------------------- - trunk/Identity/NewDir/Img/file.png - ------------------------------------------------- - 3 | Remove design template instance. - - Finally, when the untranslated image has been created, the temporal - design template instance is removed. At this point, - `centos-art.sh' takes the next design template and repeats the - whole production flow once again (design template by design - template), until all design templates be processed. - - -- *Removed*(xref:trunk Scripts Bash Functions Render Config) --, - for more information. - -3.55.1.2 Design template with translation (one-to-one) -...................................................... - -Producing untranslated images is fine in many cases, but not always. -Sometimes it is required to produce images in different languages and -that is something that untrasnlated image production cannot achieve. -However, if we fill its empty translation entry with translation files -(one for each design template) we extend the production flow from -untranslated image production to translated image production. - - In order for `centos-art.sh' to produce images correctly, each -design template should have one translation file and each translation -file should have one design template. Otherwise, if there is a missing -design template or a missing translation file, `centos-art.sh' will not -produce the final image related to the missing component. - - In order for `centos-art.sh' to know which is the relation between -translation files and design templates the translation directory -structure is taken as reference. For example, the -`trunk/Translations/Identity/Path/To/Dir/file.sed' translation file -does match `trunk/Identity/Path/To/Dir/Tpl/file.svg' design template, -but it doesn't match `trunk/Identity/Path/To/Dir/File.svg' or -`trunk/Identity/Path/To/Dir/Tpl/File.svg' or -`trunk/Identity/Path/To/Dir/Tpl/SubDir/file.svg' design templates. - - The pre-rendition configuration script used to produce untranslated -images is the same we use to produce translated images. There is no -need to modify it. So, as we are using the same pre-rendition -configuration script, we can say that translated image production is -somehow an extended/improved version of untranslated image production. - - *Note* If we use no translation file in the translation entry - (i.e., an empty directory), `centos-art.sh' assumes the - untranslated image production. If we fill the translation entry - with translation files, `centos-art.sh' assumes the translated - image production. - - To produce final images, `centos-art.sh' applies one translation -file to one design template and produce a translated design template -instance. Later, `centos-art.sh' uses the translated template instance -to produce the translated image. Finally, when the translated image has -been produced, `centos-art.sh' removes the translated design template -instance. This production flow is repeated for each translation file -available in the translatio entry. - - -centos-art.sh render --identity=trunk/Identity/Path/To/Dir -------------------------------------------------- -0 | Execute centos-art.sh on directory structure. ---v---------------------------------------------- -trunk/Translations/Identity/Path/To/Dir/file.sed -------------------------------------------------- -1 | Apply translation to design template. ---v---------------------------------------------- -trunk/Identity/Path/To/Dir/Tpl/file.svg -------------------------------------------------- -2 | Create design template instance. ---v---------------------------------------------- -/tmp/centos-art.sh-a07e824a-5953-4c21-90ae-f5e8e9781f5f-file.svg -------------------------------------------------- -3 | Render PNG image from template instance. ---v---------------------------------------------- -trunk/Identity/NewDir/Img/file.png -------------------------------------------------- -4 | Remove design template instance. - -3.55.1.3 Design template with translation (optimized) -..................................................... - -Producing translated images satisfies almost all our production images -needs, but there is still a pitfall in them. In order to produce -translated images as in the "one-to-one" configuration describes -previously, it is required that one translation file has one design -template. That's useful in many cases, but what would happen if we need -to apply many different translation files to the same design template? -Should we have to duplicate the same design template file for each -translation file, in order to satisfy the "one-to-one" relation? What -if we need to assign translation files to design templates arbitrarily? - - Certenly, that's something the "one-to-one" configuration cannot -handle. So, that's why we had to "optimize" it. The optimized -configuration consists on using a matching list (MATCHINGLIST) variable -that specifies the relationship between translation files and design -templates in an arbitrary way. Using such matching list between -translation files and design templates let us use as many assignment -combinations as translation files and design templates we are working -with. - - The MATCHINGLIST variable is set in the pre-rendition configuration -script of the component we want to produce images for. By default, the -MATCHINGLIST variable is empty which means no matching list is used. -Otherwise, if MATCHINGLIST variable has a value different to empty -value then, `centos-art.sh' interprets the matching list in order to -know how translation files are applied to design templates. - - For example, consider the following configuration: - -*One entry under `trunk/Identity/':* - In this configuration we want to produce three images using a - paragraph-based style, controlled by `paragraph.svg' design - template; and one image using a list-based style, controlled by - `list.svg' design template. - - - trunk/Identity/Path/To/Dir - |-- Tpl - | |-- paragraph.svg - | `-- list.svg - `-- Img - |-- 01-welcome.png - |-- 02-donate.png - |-- 03-docs.png - `-- 04-support.png - -*One entry under `trunk/Translations/':* - In order to produce translated images we need to have one - translation file for each translated image we want to produce. - Notice how translation names do match final image file names, but - how translation names do not match design template names. When we - use matching list there is no need for translation files to match - the names of design templates, such name relation is set inside - the matching list itself. - - - trunk/Translations/Identity/Path/To/Dir - |-- 01-welcome.sed - |-- 02-donate.sed - |-- 03-docs.sed - `-- 04-support.sed - -*One entry under `trunk/trunk/Scripts/Bash/Functions/Render/Config/':* - In order to produce different translated images using specific - design templates, we need to specify the relation between - translation files and design templates in a way that - `centos-art.sh' could know exactly what translation file to apply - to what design template. This relation between translation files - and design templates is set using the matching list MATCHINGLIST - variable inside the pre-rendition configuration script of the - component we want to produce images for. - - - trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir - `-- render.conf.sh - - In this configuration the pre-rendition configuration script - (`render.conf.sh') would look like the following: - - - function render_loadConfig { - - # Define rendition actions. - ACTIONS[0]='BASE:renderImage' - - # Define matching list. - MATCHINGLIST="\ - paragraph.svg:\ - 01-welcome.sed\ - 02-donate.sed\ - 04-support.sed - list.svg:\ - 03-docs.sed - " - - } - - As result, `centos-art.sh' will produce `01-welcome.png', - `02-donate.png' and `04-support.png' using the paragraph-based - design template, but `03-docs.png' using the list-based design - template. - -3.55.1.4 Design template with translation (optimized+flexibility) -................................................................. - -In the production models we've seen so far, there are design templates -to produce untranslated images and translation files which combiend -with design templates produce translated images. That may seems like -all our needs are covered, doesn't it? Well, it _almost_ does. - - Generally, we use design templates to define how final images will -look like. Generally, each renderable directory structure has one -`Tpl/' directory where we organize design templates for that identity -component. So, we can say that there is only one unique design template -definition for each identity component; or what is the same, said -differently, identity components can be produced in one way only, the -way its own design template directory specifies. This is not enough -for theme production. It is a limitation, indeed. - - Initially, to create one theme, we created one renderable directory -structure for each theme component. When we found ourselves with many -themes, and components inside them, it was obvious that the same design -model was duplicated inside each theme. As design models were -independently one another, if we changed one theme's design model, that -change was useless to other themes. So, in order to reuse design model -changes, we unified design models into one common directory structure. - - With design models unified in a common structure, another problem -rose up. As design models also had the visual style of theme components, -there was no difference between themes, so there was no apparent need -to have an independent theme directory structure for each different -theme. So, it was also needed to separate visual styles from design -models. - - At this point there are two independent worklines: one directory -structure to store design models (the final image characteristics -[i.e., dimensions, translation markers, etc.]) and one directory -structure to store visual styles (the final image visual style [i.e., -the image look and feel]). So, it is possible to handle both different -design models and different visual styles independtly one another and -later create combinations among them using `centos-art.sh'. - - For example, consider the following configuration: - -*One entry under `trunk/Identity/Themes/Models/':* - The design model entry exists to organize design model files - (similar to design templates). Both design models and design - templates are very similar; they both should have the - `CENTOSARTWORK' export id present to identify the exportation - area, translation marks, etc. However, design models do use - dynamic backgrounds inclusion while design templates don't. - - - THEMEMODEL | | The bond component - |<----| |--------------------->| - trunk/Identity/Themes/Models/Default/Distro/Anaconda/Progress/ - |-- paragraph.svg - `-- list.svg - - Inisde design models, dynamic backgrounds are required in order for - different artistic motifs to reuse common design models. Firstly, - in order to create dynamic backgrounds inside design models, we - import a bitmap to cover design model's background and later, - update design model's path information to replace fixed values to - dynamic values. - -*One entry under `trunk/Identity/Themes/Motifs/':* - The artistic motif entry defines the visual style we want to - produce images for, only. Final images (i.e., those built from - combining both design models and artistic motif backrounds) are - not stored here, but under branches directory structure. In the - artistic motif entry, we only define those images that cannot be - produced automatically by `centos-art.sh' (e.g., Backgrounds, - Color information, Screenshots, etc.). - - - Artistic motif name | | Artistic motif backgrounds - |<-------| |-------->| - trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/ - |-- Img - | |-- Png - | | |-- 510x300.png - | | `-- 510x300-final.png - | `-- Jpg - | |-- 510x300.jpg - | `-- 510x300-final.jpg - |-- Tpl - | `-- 510x300.svg - `-- Xcf - `-- 510x300.xcf - -*One entry under `trunk/Translations/':* - The translation entry specifies, by means of translation files, the - language-specific information we want to produce image for. When we - create the translation entry we don't use the name of neither - design model nor artistic motif, just the design model component - we want to produce images for. - - - | The bond component - |--------------------->| - trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ - `-- 5 - |-- en - | |-- 01-welcome.sed - | |-- 02-donate.sed - | `-- 03-docs.sed - `-- es - |-- 01-welcome.sed - |-- 02-donate.sed - `-- 03-docs.sed - -*One entry under `trunk/Scripts/Bash/Functions/Render/Config/':* - There is one pre-rendition configuration script for each theme - component. So, each time a theme component is rendered, its - pre-rendition configuration script is evaluated to teach - `centos-art.sh' how to render the component. - - - trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Distro/Anaconda/Progress/ - `-- render.conf.sh - - In this configuration the pre-rendition configuration script - (`render.conf.sh') would look like the following: - - - function render_loadConfig { - - # Define rendition actions. - ACTIONS[0]='BASE:renderImage' - - # Define matching list. - MATCHINGLIST="\ - paragraph.svg:\ - 01-welcome.sed\ - 02-donate.sed - list.svg:\ - 03-docs.sed - " - - # Deifne theme model. - THEMEMODEL='Default' - - } - - The production flow of "optimize+flexibility" configuration... - -3.55.2 Renderable translation directory structures --------------------------------------------------- - -Translation directory structures are auxiliar structures of renderable -identity directory structures. There is one translation directory -structure for each renderable identity directory structure. Inside -translation directory structures we organize translation files used by -renderable identity directory structures that produce translated -images. Renderable identity directory structures that produce -untranslated images don't use translation files, but they do use a -translation directory structure, an empty translation directory -structure, to be precise. - - In order to aliviate production of translation file, we made -translation directory structures renderable adding a template (`Tpl/') -directory structure to handle common content inside translation files. -This way, we work on translation templates and later use -`centos-art.sh' to produce specific translation files (based on -translation templates) for different information (e.g., languages, -release numbers, architectures, etc.). - - If for some reason, translation files get far from translation -templates and translation templates become incovenient to produce such -translation files then, care should be taken to avoid replacing the -content of translation files with the content of translation templates -when `centos-art.sh' is executed to produce translation files from -translation templates. - - Inside renderable translation directory structures, `centos-art.sh' -can produce text-based files only. - -3.55.3 Copying renderable directory structures ----------------------------------------------- - -A renderable layout is formed by design models, design images, -pre-rendition configuration scripts and translations files. This way, -when we say to duplicate rendition stuff we are saying to duplicate -these four directory structures (i.e., design models, design images, -pre-rendition configuration scripts, and related translations files). - - When we duplicate directories, inside `trunk/Identity' directory -structure, we need to be aware of renderable layout described above and -the source location used to perform the duplication action. The source -location is relevant to centos-art.sh script in order to determine the -required auxiliar information inside directory structures that need to -be copied too (otherwise we may end up with orphan directory structures -unable to be rendered, due the absence of required information). - - In order for a renderable directory structure to be valid, the new -directory structure copied should match the following conditions: - - 1. To have a unique directory structure under `trunk/Identity', - organized by any one of the above organizational designs above. - - 2. To have a unique directory structure under `trunk/Translations' to - store translation files. - - 3. To have a unique directory structure under - `trunk/Scripts/Bash/Functions/Render/Config' to set pre-rendition - configuration script. - - As convenction, the `render_doCopy' function uses `trunk/Identity' -directory structure as source location. Once the `trunk/Identity' -directory structure has been specified and verified, the related path -information is built from it and copied automatically to the new -location specified by FLAG_TO variable. - - Design templates + No translation: - - Command: - centos-art render -copy=trunk/Identity/Path/To/Dir --to=trunk/Identity/NewPath/To/Dir - - Sources: - trunk/Identity/Path/To/Dir - -trunk/Translations/Identity/Path/To/Dir - -trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir - - Targets: - trunk/Identity/NewPath/To/Dir - -trunk/Translations/Identity/NewPath/To/Dir - -trunk/Scripts/Bash/Functions/Render/Config/Identity/NewPath/To/Dir - - Renderable layout 2: - - Command: - centos-art render --copy=trunk/Identity/Themes/Motifs/TreeFlower \ --to=trunk/Identity/Themes/Motifs/NewPath/To/Dir - - Sources: - trunk/Identity/Themes/Motifs/TreeFlower - -trunk/Translations/Identity/Themes - -trunk/Translations/Identity/Themes/Motifs/TreeFlower - -trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes - -trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/TreeFlower - - Targets: - trunk/Identity/Themes/Motifs/NewPath/To/Dir - -trunk/Translations/Identity/Themes - -trunk/Translations/Identity/Themes/Motifs/NewPath/To/Dir - -trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes - -trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewPath/To/Dir - - Notice that design models are not included in source or target -locations. This is intentional. In "Renderable layout 2", design models -live by their own, they just exist, they are there, available for any -artistic motif to use. By default `Themes/Models/Default' design model -directory structure is used, but other design models directory -structures (under Themes/Models/) can be created and used changing the -value of THEMEMODEL variable inside the pre-rendition configuration -script of the artistic motif source location you want to produce. - - Notice how translations and pre-rendition configuration scripts may -both be equal in source and target. This is because such structures are -common to all artistic motifs (the default values to use when no -specific values are provided). - - - The common directory structures are not copied or deleted. We -cannot copy a directory structure to itself. - - - The common directory structures represent the default value to use - when no specific translations and/or pre-rendition configuration -script are provided inside source location. - - - The specific directory structures, if present, are both copiable -and removable. This is, when you perform a copy or delete action from - source, that source specific auxiliar directories are transfered in -the copy action to a new location (that specified by FLAG_TO -variable). - - - When translations and/or pre-rendition configuration scripts are -found inside the source directory structure, the centos-art.sh script -loads common auxiliar directories first and later specific auxiliar -directories. This way, identity rendition of source locations can be -customized idividually over the base of common default values. - - - The specific auxiliar directories are optional. - - - The common auxiliar directories should be present always. This is, - in order to provide the information required by render functionality -(i.e., to make it functional in the more basic level of its -existence). - - Notice how the duplication process is done from `trunk/Identity' on, -not the oposite. If you try to duplicate a translation structure (or -similar auxiliar directory structures like pre-rendition configuration -scripts), the `trunk/Identity' for that translation is not created. -This limitation is impossed by the fact that many `trunk/Identity' -directory structures may reuse/share the same translation directory -structure. We cannot delete one translation (or similar) directory -structures while a related `trunk/Identity/' directory structure is -still in need of it. - - The `render_doCopy' functionality does duplicate directory structures -directly involved in rendition process only. Once such directories have -been duplicated, the functionality stops thereat. - -3.55.4 Usage ------------- - - * ... - -3.55.5 See also ---------------- - -3.56 trunk/Scripts/Bash/Cli/Functions/Render/Config -=================================================== - -3.56.1 Goals ------------- - -The `trunk/Scripts/Bash/Config' directory exists to oraganize -pre-rendering configuration scripts. - -3.56.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.56.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.56.2.2 The `render.conf.sh' translation model -............................................... - -Translation pre-rendering configuration scripts take precedence before -default translation rendering action. Translation pre-rendering actions -are useful when default translation rendering action do not fit itself -to translation entry rendering requirements. - -3.56.2.3 The `render.conf.sh' rendering actions -............................................... - -Inside both image-based and text-based identity pre-rendering -configuration scripts, we use the `ACTIONS' array variable to define -the way `centos-art.sh' script performs identity rendering. Identity -rendering is organized by one `BASE' action, and optional `POST' and -`LAST' rendering actions. - - The `BASE' action specifies what kind of rendering does the -`centos-art.sh' script will perform with the files related to the -pre-rendering configuration script. The `BASE' action is required. -Possible values to `BASE' action are either `renderImage' or -`renderText' only. - - To specify the `BASE' action you need to set the `BASE:' string -followed by one of the possible values. For example, if you want to -render images, consider the following definition of `BASE' action: - - -ACTIONS[0]='BASE:renderImage' - - Only one `BASE' action must be specified. If more than one `BASE' -action is specified, the last one is used. If no `BASE' action is -specified at all, an error is triggered and the `centos-art.sh' script -ends its execution. - - The `POST' action specifies which action to apply for each file -rendered (at the rendering time). This action is optional. You can set -many different `POST' actions to apply many different actions over the -same already rendered file. Possible values to `POST' action are -`renderFormats', `renderSyslinux', `renderGrub', etc. - - To specify the `POST' action, you need to use set the `POST:' -followed by the function name of the action you want to perform. The -exact form depends on your needs. For example, consider the following -example to produce `xpm', `jpg', and `tif' images, based on already -rendered `png' image, and also organize the produced files in -directories named as their own extensions: - - -ACTIONS[0]='BASE:renderImage' -ACTIONS[1]='POST:renderFormats: xpm jpg tif' -ACTIONS[2]='POST:groupByFormat: png xpm jpg tif' - - In the previous example, file organization takes place at the moment -of rendering, just after producing the `png' base file and before going -to the next file in the list of files to render. If you don't want to -organized the produced files in directories named as their own -extensions, just remove the `POST:groupByFormat' action line: - - -ACTIONS[0]='BASE:renderImage' -ACTIONS[1]='POST:renderFormats: xpm jpg tif' - - The `LAST' action specifies which actions to apply once the last -file in the list of files to process has been rendered. The `LAST' -action is optional. Possible values for `LAST' actions may be -`groupByFormat', `renderGdmTgz', etc. - - *Note* -- *Removed*(xref: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.56.3 Usage ------------- - -Use the following commands to administer both identity and translation -pre-rendering configuration scripts: - -`centos-art config --create='path/to/dir/'' - Use this command to create `path/to/dir' related pre-rendering - configuration script. - -`centos-art config --edit='path/to/dir/'' - Use this command to edit `path/to/dir' related pre-rendering - configuration script. - -`centos-art config --read='path/to/dir/'' - Use this command to read `path/to/dir' related pre-rendering - configuration script. - -`centos-art config --remove='path/to/dir/'' - 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.56.4 See also ---------------- - -3.57 trunk/Scripts/Bash/Cli/Functions/Shell -=========================================== - -3.57.1 Goals ------------- - -This section exists to organize files related to `shell' functionality -of `centos-art.sh' script. - -3.57.2 Description ------------------- - -The `shell' functionality of `centos-art.sh' script helps you to -maintain bash scripts inside repository. For example, suppose you've -created many functionalities for `centos-art.sh' script, and you want -to use a common copyright and license note for consistency in all your -script files. If you have a bunch of files, doing this one by one -wouldn't be a big deal. In contrast, if the amount of files grows, -updating the copyright and license note for all of them would be a task -rather tedious. The `shell' functionality exists to solve maintainance -tasks just as the one previously mentioned. - - When you use `shell' functionality to update copyright inside script -files, it is required that your script files contain (at least) the -following top commentary structure: - - - 1| #!/bin/bash - 2| # - 3| # doSomething.sh -- The function description goes here. - 4| # - 5| # Copyright - 6| # - 7| # ... - 8| # - 9| # ---------------------------------------------------------------------- -10| # $Id$ -11| # ---------------------------------------------------------------------- -12| -13| function doSomething { -14| -15| } - -Figure 3.4: The functions script base comment structure - - Relevant lines in the above structure are lines from 5 to 9. -Everything else in the file is left immutable. - - When you are updating copyright through `shell' functionality, the -`centos-art.sh' script replaces everything in-between line 5 --the -first one matching `^# Copyright .+$' string-- and line 9--the first -long dash separator matching `^# -+$'-- with the content of copyright -template instance. - - *Caution* Be sure to add the long dash separator that matches `^# - -+$' regular expression _before_ the function definition. - Otherwise, if the `Copyright' line is present but no long dash - separator exists, `centos-art.sh' will remove anything in-between - the `Copyright' line and the end of file. This way you may lost - your function definitions entirely. - - The copyright template instance is created from one copyright -template stored in the `Config/tpl_forCopyright.sed' file. The template -instance is created once, and later removed when no longer needed. At -this moment, when template instance is created, the `centos-art.sh' -script takes advantage of automation in order to set copyright full -name and date dynamically. - - When you use `shell' functionality to update copyright, the first -thing `shell' functionality does is requesting copyright information to -user, and later, if values were left empty (i.e., no value was typed -before pressing key), the `shell' functionality uses its own -default values. - - When `shell' functionality uses its own default values, the final -copyright note looks like the following: - - - 1| #!/bin/bash - 2| # - 3| # doSomthing.sh -- The function description goes here. - 4| # - 5| # Copyright (C) 2003, 2010 The CentOS Project - 6| # - 7| # This program is free software; you can redistribute it and/or modify - 8| # it under the terms of the GNU General Public License as published by - 9| # the Free Software Foundation; either version 2 of the License, or -10| # (at your option) any later version. -11| # -12| # This program is distributed in the hope that it will be useful, but -13| # WITHOUT ANY WARRANTY; without even the implied warranty of -14| # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -15| # General Public License for more details. -16| # -17| # You should have received a copy of the GNU General Public License -18| # along with this program; if not, write to the Free Software -19| # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 -20| # USA. -21| # -22| # ---------------------------------------------------------------------- -23| # $Id$ -24| # ---------------------------------------------------------------------- -25| -26| function doSomething { -27| -28| } - -Figure 3.5: The function script comment example - - Relevant lines in the above structure are lines from 5 to 22. Pay -attention how the copyright line was built, and how the license was -added into the top comment where previously was just three dots. -Everything else in the file was left immutable. - - To change copyright information (i.e., full name or year -information), run the `shell' functionality over the root directory -containing the script files you want to update copyright in and enter -the appropriate information when it be requested. You can run the -`shell' functionality as many times as you need to. - - To change copyright license (i.e., the text in-between lines 7 and -20), you need to edit the `Config/tpl_forCopyright.sed' file, set the -appropriate information, and run the `shell' functionality once again -for changes to take effect over the files you specify. - - *Important* The `centos-art.sh' script is released as: - - - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 - - Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. - - Do not change the license information under which `centos-art.sh' - script is released. Instead, if you think a different license must - be used, please share your reasons at CentOS Developers mailing - list . - -3.57.3 Usage ------------- - -`centos-art sh --update-copyright='path/to/dir'' -`centos-art sh --update-copyright='path/to/dir' --filter='regex'' - Use these commands to update copyright information in `.sh' files - under `path/to/dir' directory. - - When you provide `--filter='regex'' argument, the list of files to -process is reduced as specified in `regex' regular expression. Inside -`centos-art.sh' script, the `regex' regular expression is used in -combination with `find' command to look for files matching the regular -expression path pattern. - - *Warning* In order for `regex' regular expression to match a file, - the `regex' regular expresion must match the whole file path not - just the file name. - - For example, if you want to match all `render.conf.sh' files inside -`path/to/dir', use the `.+/render.conf' regular expression. Later, -`centos-art.sh' script uses this value inside `^$REGEX\.sh$' expression -in order to build the final regular expression (i.e., -`^.+/render.conf\.sh$') that is evaluated against available file paths -inside the list of files to process. - - Exceptionally, when you provide `--filter='regex'' in the way that -`regex', appended to `path/to/dir/' (i.e. `path/to/dir/regex'), -matches a regular file; the `centos-art.sh' script uses the file -matching as only file in the list of files to process. - -3.57.4 See also ---------------- - -3.58 trunk/Scripts/Bash/Cli/Functions/Svg -========================================= - -3.58.1 Goals ------------- - -This section exists to organize files related to `svg' functionality of -`centos-art.sh' script. - -3.58.2 Description ------------------- - -The `svg' functionality of `centos-art.sh' script helps you to maintain -scalable vector graphics (SVG) inside repository. For example, suppose -you've been working in CentOS default design models under -`trunk/Identity/Themes/Models/', and you want to set common metadata to -all of them, and later remove all unused SVG defintions from `*.svg' -files. Doing so file by file may be a tedious task, so the -`centos-art.sh' script provides the `svg' functionality to aid you -maintain such actions. - -3.58.2.1 Metadata maintainance -.............................. - -The metadata used is defined by Inkscape 0.46 using the SVG standard -markup. The `centos-art.sh' script replaces everything in-between -`' tags with a predefined metadata template -we've set for this purpose. - - The metadata template was created using the metadata information of a -file which, using Inkscape 0.46, all metadata fields were set. This -created a complete markup representation of how SVG metadata would look -like. Later, we replaced every single static value with a translation -marker in the form `=SOMETEXT=', where `SOMETEXT' is the name of its -main opening tag. Later, we transform the metadata template into a sed -replacement set of commads escaping new lines at the end of each line. - - With metadata template in place, the `centos-art.sh' script uses it -to create a metadata template instance for the file being processed -currently. The metadata template instance contains the metadata -portion of sed replacement commands with translation markers already -traduced. In this action, instance creation, is where we take -advantage of automation and generate metadata values like title, date, -keywords, source, identifier, and relation dynamically, based on the -file path `centos-art.sh' script is currently creating metadata -information for. - - With metadata template instance in place, the `centos-art.sh' script -uses it to replace real values inside all `.svg' files under the -current location you're running the `centos-art.sh' script on. Default -behaviour is to ask user to enter each metadatum required, one by one. -If user leaves metadatum empty, by pressing key, `centos-art.sh' -uses its default value. - - The `centos-art.sh' script modifies the following metadata: - -`Title' - Name by which this document is formally known. If no value is set - here, `centos-art.sh' script uses the file name as title. - -`Date' - Date associated with the creation of this document (YYYY-MM-DD). - If no value is set here, `centos-art.sh' script uses the current - date information as in `date +%Y-%m-%d'. - -`Creator' - Name of entity primarily responsible for making the content of this - document. If no value is set here, `centos-art.sh' script uses the - string `The CentOS Project'. - -`Rights' - Name of entity with rights to the intellectual Property of this - document. If no value is set here, `centos-art.sh' script uses the - string `The CentOS Project'. - -`Publisher' - Name of entity responsible for making this document available. If - no value is set here, `centos-art.sh' script uses the string `The - CentOS Project'. - -`Identifier' - Unique URI to reference this document. If no value is set here, - `centos-art.sh' script uses the current file path to build the - related url that points to current file location inside repository - central server. - -`Source' - Unique URI to reference the source of this document. If no value is - set here, `centos-art.sh' script uses current file path to build - the related url that points to current file location inside - repository central server. - -`Relation' - Unique URI to a related document. If no value is set here, - `centos-art.sh' script uses current file path to build the related - url that points to current file location inside repository central - server. - -`Language' - Two-letter language tag with optional subtags for the language of - this document. (e.g. `en-GB'). If no value is set here, - `centos-art.sh' script uses the current locale information as in - `cli_getCurrentLocale' function. - -`Keywords' - The topic of this document as comma-separated key words, prhases, - or classifications. If no value is set here, `centos-art.sh' script - uses file path to build - -`Coverage' - Extent or scope of this document. If no value is set here, - `centos-art.sh' script uses the string `The CentOS Project'. - -`Description' - Description about the document. If no value is set here, - `centos-art.sh' script uses uses empty value as default. - -`Contributors' - People that contributes in the creation/maintainance of the - document. If no value is set here, `centos-art.sh' script uses - uses empty value as default. - - The `License' metadatum is not set as a choise, by now. It is fixed -Creative Common Attribution Share-Alike 3.0 License -(http://creativecommons.org/licenses/by-sa/3.0/). This is done in order -to grant license consistency among all SVG files we manage inside CentOS -Artwork Repository. - -3.58.2.2 Unused definitions -........................... - -Many of the no-longer-used gradients, patterns, and markers (more -precisely, those which you edited manually) remain in the corresponding -palettes and can be reused for new objects. However if you want to -optimize your document, use the `Vacuum Defs' command in `File' menu. -It will remove any gradients, patterns, or markers which are not used -by anything in the document, making the file smaller. - - If you have one or two couple of files, removing unused definitions -using the graphical interface may be enough to you. In contrast, if -you have dozens or even houndreds of scalable vector graphics files to -maintain it is not a fun task to use the graphical interface to remove -unused definitions editing those files one by one. - - To remove unused definitions from several scalable vector graphics -files, the `centos-art.sh' script uses Inkscape command-line interface, -specifically with the `--vaccum-defs' option. - -3.58.3 Usage ------------- - -`centos-art svg --update-metadata='path/to/dir'' - -`centos-art svg --update-metadata='path/to/dir' --filter='regex'' - Use these commands to update metadata information to `.svg' files - under `path/to/dir' directory. - -`centos-art svg --vacuum-defs='path/to/dir'' - -`centos-art svg --vacuum-defs='path/to/dir' --filter='regex'' - Use these commands to remove unused definitions inside `.svg' - files under `path/to/dir' directory. - - When you provide `--filter='regex'' argument, the list of files to -process is reduced as specified in `regex' regular expression. Inside -`centos-art.sh' script, the `regex' regular expression is used in -combination with `find' command to look for files matching the regular -expression path pattern. - - *Warning* In order for `regex' regular expression to match a file, - the `regex' regular expresion must match the whole file path not - just the file name. - - For example, if you want to match all `summary.svg' files inside -`path/to/dir', use the `.+/summary' regular expression. Later, -`centos-art.sh' script uses this value inside `^$REGEX\.svg$' -expression in order to build the final regular expression (i.e., -`^.+/summary\.svg$') that is evaluated against available file paths -inside the list of files to process. - - Exceptionally, when you provide `--filter='regex'' in the way that -`regex', appended to `path/to/dir/' (i.e. `path/to/dir/regex'), -matches a regular file; the `centos-art.sh' script uses the file -matching as only file in the list of files to process. - -3.58.4 See also ---------------- - -3.59 trunk/Scripts/Bash/Cli/Functions/Verify -============================================ - -3.59.1 Goals ------------- - -This section exists to organize files related to `centos-art.sh' script -`verify' functionality. The `verify' functionality of `centos-art.sh' -script helps you to verify the workstation configuration you are -planning to use as host for your working copy of CentOS Artwork -Repository. - -3.59.2 Description ------------------- - -The first time you download CentOS Artwork Repository you need to -configure your workstation in order to use `centos-art.sh' script. -These preliminar configurations are based mainly on auxiliar RPM -packages installation, symbolic links creations, and environment -variables definitions. The `verify' functionality of `centos-art.sh' -script guides you through this preliminar configuration process. - - If this is the first time you run `centos-art.sh' script, the -appropriate way to use its `verify' functionality is not using the -`centos-art.sh' script directly, but the absolute path to -`centos-art.sh' script instead (i.e., -`~/artwork/trunk/Scripts/Bash/centos-art.sh'). This is necessary -because `centos-art' symbolic link, under `~/bin/' directory, has not -been created yet. - -3.59.2.1 Packages -................. - -Installation of auxiliar RPM packages provides the software required to -manipulate files inside the repository (e.g., image files, -documentation files, translation files, script files, etc.). Most of -RPM packages `centos-art.sh' script uses are shipped with CentOS -distribution, and can be installed from CentOS base repository. The -only exception is `inkscape', the package we use to manipulate SVG -files. The `inkscape' package is not inside CentOS distribution so it -needs to be installed from third party repositories. - - *Note* Configuration of third party repositories inside CentOS - distribution is described in CentOS wiki, specifically in the - following URL: - `http://wiki.centos.org/AdditionalResources/Repositories' - - Before installing packages, the `centos-art.sh' script uses `sudo' -to request root privileges to execute `yum' installation functionality. -If your user isn't defined as a privileged user--at least to run `yum' -commands-- inside `/etc/sudoers' configuration file, you will not be -able to perform package installation tasks as set in `centos-art.sh' -script `verify' functionality. - - Setting sudo privileges to users is an administrative task you have -to do by yourself. If you don't have experience with `sudo' command, -please read its man page running the command: `man sudo'. This reading -will be very useful, and with some practice, you will be able to -configure your users to have `sudo' privileges. - -3.59.2.2 Links -.............. - -Creation of symbolic links helps us to alternate between different -implementations of `centos-art.sh' script-line (e.g., `centos-art.sh', -for Bash implementation; `centos-art.py', for Python implementation; -`centos-art.pl', for Perl implementation; and so on for other -implementations). The `centos-art.sh' script-line definition takes -place inside your personal binary (`~/bin/') directory in order to make -the script implementation --the one that `centos-art' links to-- -available to PATH environment variable. - - Creation of symbolic links helps us to reuse components from -repository working copy. For example, color information files -maintained inside your working copy must never be duplicated inside -program-specific configuration directories that uses them in your -workstation (e.g., Gimp, Inkscape, etc.). Instead, a symbolic link -must be created for each one of them, from program-specific -configuration directories to files in the working copy. In this -configuration, when someone commits changes to color information files -up to central repository, they--the changes committed-- will be -immediatly available to your programs the next time you update your -working copy --the place inside your workstation those color -information files are stored--. - - Creation of symbolic links helps us to make `centos-art.sh' script -functionalities available outside `trunk/' repository directory -structure, but at its same level in repository tree. This is useful if -you need to use the "render" functionality of `centos-art.sh' under -`branches/' repository directory structure as you usually do inside -`trunk/' repository directory structure. As consequence of this -configuration, automation scripts cannot be branched under -`branches/Scripts' directory structure. - -3.59.2.3 Environment variables -.............................. - -Definition of environemnt variables helps us to set default values to -our user session life. The user session environment variable defintion -takes place in the user's `~/.bash_profile' file. The `verify' -functionality of `centos-art.sh' script doesn't modify your -`~/.bash_profile' file. - - The `verify' functionality of `centos-art.sh' script evaluates the -following environment variables: - -`EDITOR' - Default text editor. - - The `centos-art.sh' script uses default text `EDITOR' to edit - pre-commit subversion messages, translation files, configuration - files, script files, and similar text-based files. - - If `EDITOR' environment variable is not set, `centos-art.sh' - script uses `/usr/bin/vim' as default text editor. Otherwise, the - following values are recognized by `centos-art.sh' script: - - * `/usr/bin/vim' - - * `/usr/bin/emacs' - - * `/usr/bin/nano' - - If no one of these values is set in `EDITOR' environment variable, - `centos-art.sh' uses `/usr/bin/vim' text editor by default. - -`TEXTDOMAIN' - Default domain used to retrieve translated messages. This - variable is set in `initFunctions.sh' and shouldn't be changed. - -`TEXTDOMAINDIR' - Default directory used to retrieve translated messages. This - variable is set in `initFunctions.sh' and shouldn't be changed. - -`LANG' - Default locale information. - - This variable is initially set in the configuration process of - CentOS distribution installer (i.e., Anaconda), specifically in the - `Language' step; or once installed using the - `system-config-language' tool. - - The `centos-art.sh' script uses the LANG environment variable to - know in which language the script messages are printed out. - -`TZ' - Default time zone representation. - - This variable is initially set in the configuration process of - CentOS distribution installer (i.e., Anaconda), specifically in the - `Date and time' step; or once installed using the - `system-config-date' tool. - - The `centos-art.sh' script doesn't use the TZ environment variable - information at all. Instead, this variable is used by the system - shell to show the time information according to your phisical - location on planet Earth. - - Inside your computer, the time information is firstly set in the - BIOS clock (which may need correction), and later in the - configuration process of CentOS distribution installer (or later, - by any of the related configuration tools inside CentOS - distribution). Generally, setting time information is a - straight-forward task and configuration tools available do cover - most relevant location. However, if you need a time precision not - provided by the configuration tools available inside CentOS - distribution then, using TZ variable may be necessary. - - *Convenction* In order to keep changes syncronized between - central repository and its working copies: configure both - repository server and workstations (i.e., the place where - each working copy is set on) to use Coordinated Universal - Time (UTC) as base time representation. Later, correct the - time information for your specific location using time zone - correction. - - The format of TZ environment variable is described in `tzset(3)' - manual page. - - -3.59.3 Usage ------------- - -`centos-art verify --packages' - Verify required packages your workstation needs in order to run the - `centos-art.sh' script correctly. If there are missing packages, - the `centos-art.sh' script asks you to confirm their installation. - When installing packages, the `centos-art.sh' script uses the - `yum' application in order to achieve the task. - - In case all packages required by `centos-art.sh' script are - already installed in your workstation, the message `The required - packages are already installed.' is output for you to know. - -`centos-art verify --links' - Verify required links your workstation needs in order to run the - centos-art command correctly. If any required link is missing, the - `centos-art.sh' script asks you to confirm their installation. To - install required links, the `centos-art.sh' script uses the `ln' - command. - - In case all links required by `centos-art.sh' script are already - created in your workstation, the message `The required links are - already installed.' is output for you to know. - - In case a regular file exists with the same name of a required - link, the `centos-art.sh' script outputs the `Already exists as - regular file.' message when listing required links that will be - installed. Of course, as there is already a regular file where - must be a link, no link is created. In such cases the - `centos-art.sh' script will fall into a continue installation - request for that missing link. To end this continue request you - can answer `No', or remove the existent regular file to let - `centos-art.sh' script install the link on its place. - -`centos-art verify --environment' -`centos-art verify --environment --filter='regex'' - Output a brief description of environment variables used by - `centos-art.sh' script. - - If `--filter' option is provided, output is reduced as defined in - the `regex' regular expression value. If `--filter' option is - specified but `regex' value is not, the `centos-art.sh' script - outputs information as if `--filter' option had not been provided - at all. - - -3.59.4 See also ---------------- - -3.60 trunk/Scripts/Python -========================= - -3.60.1 Goals ------------- - - * ... - -3.60.2 Description ------------------- - - * ... - -3.60.3 Usage ------------- - - * ... - -3.60.4 See also ---------------- - -Index -***** - -branches: See 1. (line 368) -How to render brands' translation files: See 3.36.3. (line 2425) -How to render fonts' translation files: See 3.38.3. (line 2498) -Metadata maintainance: See 3.58.2. (line 5534) -tags: See 2. (line 371) -Translation brands file names: See 3.36.2.1. (line 2382) -trunk: See 3. (line 374) -trunk Identity: See 3.1. (line 377) -trunk Identity Brands: See 3.2. (line 493) -trunk Identity Fonts: See 3.3. (line 510) -trunk Identity Icons: See 3.4. (line 587) -trunk Identity Isolinux: See 3.5. (line 604) -trunk Identity Models: See 3.6. (line 621) -trunk Identity Models Css: See 3.7. (line 641) -trunk Identity Models Html: See 3.8. (line 663) -trunk Identity Models Img Promo Web: See 3.9. (line 684) -trunk Identity Models Tpl: See 3.10. (line 705) -trunk Identity Models Tpl Promo Web: See 3.11. (line 726) -trunk Identity Models Xcf: See 3.12. (line 1040) -trunk Identity Release: See 3.13. (line 1061) -trunk Identity Themes: See 3.14. (line 1078) -trunk Identity Themes Models: See 3.15. (line 1102) -trunk Identity Themes Models Alternative: See 3.16. (line 1135) -trunk Identity Themes Models Default: See 3.17. (line 1162) -trunk Identity Themes Models Default Distro: See 3.18. (line 1194) -trunk Identity Themes Models Default Distro Anaconda:See 3.19. - (line 1278) -trunk Identity Themes Models Default Promo: See 3.20. (line 1295) -trunk Identity Themes Models Default Web: See 3.21. (line 1321) -trunk Identity Themes Motifs: See 3.22. (line 1346) -trunk Identity Themes Motifs Flame: See 3.23. (line 1449) -trunk Identity Themes Motifs Modern: See 3.24. (line 1650) -trunk Identity Themes Motifs Modern Backgrounds:See 3.25. (line 1667) -trunk Identity Themes Motifs Modern Backgrounds Img:See 3.26. - (line 1788) -trunk Identity Themes Motifs Modern Backgrounds Tpl:See 3.27. - (line 1809) -trunk Identity Themes Motifs Modern Backgrounds Xcf:See 3.28. - (line 1830) -trunk Identity Themes Motifs Modern Distro Anaconda Progress:See 3.29. - (line 1857) -trunk Identity Themes Motifs Modern Palettes: See 3.30. (line 1913) -trunk Identity Themes Motifs TreeFlower: See 3.31. (line 1935) -trunk Identity Themes Motifs TreeFlower Backgrounds:See 3.32. - (line 1952) -trunk Identity Widgets: See 3.33. (line 2250) -trunk Locales: See 3.34. (line 2267) -trunk Locales Identity: See 3.35. (line 2320) -trunk Locales Identity Brands: See 3.36. (line 2341) -trunk Locales Identity Brands Tpl: See 3.37. (line 2436) -trunk Locales Identity Fonts: See 3.38. (line 2451) -trunk Locales Identity Models: See 3.39. (line 2514) -trunk Locales Identity Release: See 3.40. (line 2529) -trunk Locales Identity Themes: See 3.41. (line 2544) -trunk Locales Identity Themes Backgrounds: See 3.42. (line 2559) -trunk Locales Identity Themes Distro Anaconda Progress:See 3.43. - (line 2580) -trunk Locales Identity Widgets: See 3.44. (line 2673) -trunk Manuals: See 3.45. (line 2694) -trunk Scripts: See 3.46. (line 2715) -trunk Scripts Bash: See 3.47. (line 2739) -trunk Scripts Bash Cli: See 3.48. (line 2889) -trunk Scripts Bash Cli Functions: See 3.49. (line 2892) -trunk Scripts Bash Cli Functions Help: See 3.50. (line 4002) -trunk Scripts Bash Cli Functions Html: See 3.51. (line 4023) -trunk Scripts Bash Cli Functions Locale: See 3.52. (line 4044) -trunk Scripts Bash Cli Functions Manual: See 3.53. (line 4124) -trunk Scripts Bash Cli Functions Path: See 3.54. (line 4145) -trunk Scripts Bash Cli Functions Render: See 3.55. (line 4468) -trunk Scripts Bash Cli Functions Render Config:See 3.56. (line 5166) -trunk Scripts Bash Cli Functions Shell: See 3.57. (line 5344) -trunk Scripts Bash Cli Functions Svg: See 3.58. (line 5516) -trunk Scripts Bash Cli Functions Verify: See 3.59. (line 5704) -trunk Scripts Python: See 3.60. (line 5934) -Unused definitions: See 3.58.2.1. (line 5641) -List of Figures -*************** - diff --git a/Manuals/Filesystem/filesystem.xml b/Manuals/Filesystem/filesystem.xml deleted file mode 100644 index 1865c26..0000000 --- a/Manuals/Filesystem/filesystem.xml +++ /dev/null @@ -1,5421 +0,0 @@ - - - - filesystem.xml - CentOS Artwork Repository - File System - - Copyright ©right; 2009-2011 Alain Reguera Delgado - Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. - - - CentOS Artwork Repository - File System - Alain Reguera Delgado - Copyright ©right; 2009-2011 Alain Reguera Delgado - Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. - - - - - Top - (dir) - - CentOS Artwork Repository - File System - Copyright ©right; 2009-2011 Alain Reguera Delgado - Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. - - - branches - branches - - - - tags - tags - - - - trunk - trunk - - - - Index - Index - - - - List of Figures - List of Figures - - - - - - - - branches - tags - Top - Top - - branches - branches - - - - tags - trunk - branches - Top - - tags - tags - - - - trunk - Index - tags - Top - - trunk - trunk - - - trunk Identity - trunk Identity - - - - trunk Identity Brands - trunk Identity Brands - - - - trunk Identity Fonts - trunk Identity Fonts - - - - trunk Identity Icons - trunk Identity Icons - - - - trunk Identity Isolinux - trunk Identity Isolinux - - - - trunk Identity Models - trunk Identity Models - - - - trunk Identity Models Css - trunk Identity Models Css - - - - trunk Identity Models Html - trunk Identity Models Html - - - - trunk Identity Models Img Promo Web - trunk Identity Models Img Promo Web - - - - trunk Identity Models Tpl - trunk Identity Models Tpl - - - - trunk Identity Models Tpl Promo Web - trunk Identity Models Tpl Promo Web - - - - trunk Identity Models Xcf - trunk Identity Models Xcf - - - - trunk Identity Release - trunk Identity Release - - - - trunk Identity Themes - trunk Identity Themes - - - - trunk Identity Themes Models - trunk Identity Themes Models - - - - trunk Identity Themes Models Alternative - trunk Identity Themes Models Alternative - - - - trunk Identity Themes Models Default - trunk Identity Themes Models Default - - - - trunk Identity Themes Models Default Distro - trunk Identity Themes Models Default Distro - - - - trunk Identity Themes Models Default Distro Anaconda - trunk Identity Themes Models Default Distro Anaconda - - - - trunk Identity Themes Models Default Promo - trunk Identity Themes Models Default Promo - - - - trunk Identity Themes Models Default Web - trunk Identity Themes Models Default Web - - - - trunk Identity Themes Motifs - trunk Identity Themes Motifs - - - - trunk Identity Themes Motifs Flame - trunk Identity Themes Motifs Flame - - - - trunk Identity Themes Motifs Modern - trunk Identity Themes Motifs Modern - - - - trunk Identity Themes Motifs Modern Backgrounds - trunk Identity Themes Motifs Modern Backgrounds - - - - trunk Identity Themes Motifs Modern Backgrounds Img - trunk Identity Themes Motifs Modern Backgrounds Img - - - - trunk Identity Themes Motifs Modern Backgrounds Tpl - trunk Identity Themes Motifs Modern Backgrounds Tpl - - - - trunk Identity Themes Motifs Modern Backgrounds Xcf - trunk Identity Themes Motifs Modern Backgrounds Xcf - - - - trunk Identity Themes Motifs Modern Distro Anaconda Progress - trunk Identity Themes Motifs Modern Distro Anaconda Progress - - - - trunk Identity Themes Motifs Modern Palettes - trunk Identity Themes Motifs Modern Palettes - - - - trunk Identity Themes Motifs TreeFlower - trunk Identity Themes Motifs TreeFlower - - - - trunk Identity Themes Motifs TreeFlower Backgrounds - trunk Identity Themes Motifs TreeFlower Backgrounds - - - - trunk Identity Widgets - trunk Identity Widgets - - - - trunk Locales - trunk Locales - - - - trunk Locales Identity - trunk Locales Identity - - - - trunk Locales Identity Brands - trunk Locales Identity Brands - - - - trunk Locales Identity Brands Tpl - trunk Locales Identity Brands Tpl - - - - trunk Locales Identity Fonts - trunk Locales Identity Fonts - - - - trunk Locales Identity Models - trunk Locales Identity Models - - - - trunk Locales Identity Release - trunk Locales Identity Release - - - - trunk Locales Identity Themes - trunk Locales Identity Themes - - - - trunk Locales Identity Themes Backgrounds - trunk Locales Identity Themes Backgrounds - - - - trunk Locales Identity Themes Distro Anaconda Progress - trunk Locales Identity Themes Distro Anaconda Progress - - - - trunk Locales Identity Widgets - trunk Locales Identity Widgets - - - - trunk Manuals - trunk Manuals - - - - trunk Scripts - trunk Scripts - - - - trunk Scripts Bash - trunk Scripts Bash - - - - trunk Scripts Bash Cli - trunk Scripts Bash Cli - - - - trunk Scripts Bash Cli Functions - trunk Scripts Bash Cli Functions - - - - trunk Scripts Bash Cli Functions Help - trunk Scripts Bash Cli Functions Help - - - - trunk Scripts Bash Cli Functions Html - trunk Scripts Bash Cli Functions Html - - - - trunk Scripts Bash Cli Functions Locale - trunk Scripts Bash Cli Functions Locale - - - - trunk Scripts Bash Cli Functions Manual - trunk Scripts Bash Cli Functions Manual - - - - trunk Scripts Bash Cli Functions Path - trunk Scripts Bash Cli Functions Path - - - - trunk Scripts Bash Cli Functions Render - trunk Scripts Bash Cli Functions Render - - - - trunk Scripts Bash Cli Functions Render Config - trunk Scripts Bash Cli Functions Render Config - - - - trunk Scripts Bash Cli Functions Shell - trunk Scripts Bash Cli Functions Shell - - - - trunk Scripts Bash Cli Functions Svg - trunk Scripts Bash Cli Functions Svg - - - - trunk Scripts Bash Cli Functions Verify - trunk Scripts Bash Cli Functions Verify - - - - trunk Scripts Python - trunk Scripts Python - - - - - - - trunk Identity - trunk Identity Brands - trunk -
- trunk/Identity - trunk Identity - - Goals - The trunk/Identity directory exists to organize CentOS corporate identity artworks. - - - - Description - The CentOS Project corporate identity is the “persona” of the organization known as The CentOS Project. The CentOS Project corporate identity plays a significant role in the way the CentOS Project, as organization, presents itself to both internal and external stakeholders. In general terms, the CentOS Project corporate visual identity expresses the values and ambitions of the CentOS Project organization, its business, and its characteristics. - The CentOS Project corporate identity provides visibility, recognizability, reputation, structure and identification to the CentOS Project organization by means of corporate design, corporate communication, and corporate behaviour. - The CentOS Project settles down its corporate visual identity on a “monolithic corporate visual identity structure”. In this structure The CentOS Project uses one unique name (The CentOS Brand) and one unique visual style (The CentOS Default Theme) in all its manifestations. - - - The CentOS Brands - - The CentOS brand is the name or trademark that conncects the producer with their products. In this case, the producer is The CentOS Project and the products are the CentOS distributions, the CentOS web sites, the CentOS promotion stuff, etc. - See trunk Identity Brands, for more information. - - - - The CentOS Themes - - The CentOS themes are a set of image files connected all together by one unique visual style. Each theme is organized in different visual manifestations, in order to cover each visual manifestation of The CentOS Project (i.e., distributions, websites, promotion stuff, etc.). See trunk Identity Themes, for more information. - - -
- Inside a monolithic corporate visual identity structure, internal and external stakeholders use to feel a strong sensation of uniformity, orientation, and identification with the organization. No matter if you are visiting websites, using the distribution, or acting on social events, the one unique name and one unique visual style conect them all to say: Hey! we are all parts of the CentOS project. And, probably, some vister will say: Can I join the party? Yes you can, it is free. :) - - - - Usage - To produce identity artworks, use the following commands: - - - centos-art render 'path/to/dir' - - When path/to/dir refers to one renderable directory under trunk/Identity, this command renders identity artworks using both related design models and related translation files. - - - - centos-art render 'path/to/dir' --filter='pattern' - - When path/to/dir refers to one renderable directory under trunk/Identity, this command renders identity artworks using both related design models and related translation files that match the regular expression passed in --filter='pattern' argument. - To control the number of files produced by centos-art command, you need to look into the translation path and provide a regular expression pattern that matches the translation path, or paths, related to the file, or files, you want to produce. - The regular expression pattern you provide to centos-art command is applied to the translation path from its very beginning. It is not the same to say 5/en/01-welcome that 01-welcome, the frist expression matches but the last one does not. - When using --filter='pattern' you don't need to specify the file extension. It is removed from translation path before applying the pattern, so it doesn't count here. - - -
- - - - File name convenctions - As file name convenction, inside CentOS Artwork Repository, both text-based and image-based file name produced by centos-art.sh script has the same name of their translation files without the .sed extension. The file extension is set as follow: - - - When text-based files are rendered - Text-based files end up having the same extension of their design template file. - - - - When image-based files are rendered - Image-based files always end up having the .png extension. - - Tip Once .png images are created, other image formats may be created using the renderFormats post-rendering action, inside the image-based related pre-rendering configuration script. - See trunk Scripts Bash, for more information. - - - - - - See also - - - - - - - References - - • - - http://en.wikipedia.org/Corporate_identity (and related links). - - - -
- - - trunk Identity Brands - trunk Identity Fonts - trunk Identity - trunk -
- trunk/Identity/Brands - trunk Identity Brands - - Goals - - • - - ... - - - - - - Description - - - - Usage - - - - See also - - - -
- - - trunk Identity Fonts - trunk Identity Icons - trunk Identity Brands - trunk -
- trunk/Identity/Fonts - trunk Identity Fonts - - Goals - This section exists to organize digital typographies used by the CentOS project. - - - - Description - - - - Usage - The CentOS corporate identity is attached to DejaVu LGC font-family. Whatever artwork you design for CentOS project, that requires typography usage, must be done using DejaVu LGC font-family. - - - Recommendation-1: - - For screen desings (e.g., anything that final destination will never be printed on paper or any medium outside computer screens) use DejaVu LGC Sans font-family. - - - - Recommendation-2: - - For non-screen designs (e.g., anything that final desition will be printed on paper or any other medium outside computer screens) use DejaVu LGC Serif font-family. As convenction files described in this rule are stored under Stationery directories. - - -
- The only execption for the two recommendations above is the typography used inside CentOS logo. The CentOS logo is the main visual representation of the CentOS project so the typography used in it must be the same always, no matter where it be shown. It also has to be clear enough to dismiss any confussion between similar typefaces (e.g., the number one (1) sometimes is confuesed with the letter el (l) or letter ai (i)). - As CentOS logo typography convenction, the word CentOS uses Denmark typography as base, both for the word CentOS and the phrase Community Enterprise Operating System. The phrase size of CentOS logo is half the size in poits the word CentOS has and it below CentOS word and aligned with it on the left. The distance between CentOS word and phrase Community Enterprise Operating System have the size in points the phrase has. - When the CentOS release brand is built, use Denmark typography for the release number. The release number size is two times larger (in height) than default CentOS word. The separation between release number and CentOS word is twice the size in points of separation between CentOS word and phrase Community Enterprise Operating System. - Another component inside CentOS logo is the trademark symbol (TM). This symbol specifies that the CentOS logo must be consider a product brand, even it is not a registered one. The trademark symbol uses DejaVu LGC Sans Regular typography. The trademark symbol is aligned right-top on the outter side of CentOS word. The trademark symbol must not exceed haf the distance, in points, between CentOS word and the release number on its right. - It would be very convenient for the CentOS Project and its community to to make a registered trademark (®) of CentOS logo. To make a register trademark of CentOS Logo prevents legal complications in the market place of brands. It grants the consistency, through time, of CentOS project corporate visual identity. - - Note The information about trademarks and corporate identity is my personal interpretation of http://en.wikipedia.org/Corporate_identity and http://en.wikipedia.org/Trademark description. If you have practical experiences with these affairs, please serve yourself to improve this section with your reasons. - - - - - See also - - - -
- - - trunk Identity Icons - trunk Identity Isolinux - trunk Identity Fonts - trunk -
- trunk/Identity/Icons - trunk Identity Icons - - Goals - - • - - ... - - - - - - Description - - - - Usage - - - - See also - - - -
- - - trunk Identity Isolinux - trunk Identity Models - trunk Identity Icons - trunk -
- trunk/Identity/Isolinux - trunk Identity Isolinux - - Goals - - • - - ... - - - - - - Description - - - - Usage - - - - See also - - - -
- - - trunk Identity Models - trunk Identity Models Css - trunk Identity Isolinux - trunk -
- trunk/Identity/Models - trunk Identity Models - - Goals - This section exists to organize design models. - - - - Description - Design models are representative designs useful to understand how to build artworks. - - - - Usage - - - - See also - - - trunk Identity Models Html - trunk Identity Models Html - - - - trunk Identity Models Css - trunk Identity Models Css - - - - trunk Identity Models Tpl - trunk Identity Models Tpl - - - - trunk Identity Models Xcf - trunk Identity Models Xcf - - - - -
- - - trunk Identity Models Css - trunk Identity Models Html - trunk Identity Models - trunk -
- trunk/Identity/Models/Css - trunk Identity Models Css - - Goals - This directory exists to provide common style sheets (CSS) definitions to HTML design models. - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Identity Models Html - trunk Identity Models Img Promo Web - trunk Identity Models Css - trunk -
- trunk/Identity/Models/Html - trunk Identity Models Html - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Identity Models Img Promo Web - trunk Identity Models Tpl - trunk Identity Models Html - trunk -
- trunk/Identity/Models/Img/Promo/Web - trunk Identity Models Img Promo Web - - Goals - - • - - Provide images related to CentOS web interface. - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - trunk Identity Models Tpl Promo Web - trunk Identity Models Tpl Promo Web - - - - -
- - - trunk Identity Models Tpl - trunk Identity Models Tpl Promo Web - trunk Identity Models Img Promo Web - trunk -
- trunk/Identity/Models/Tpl - trunk Identity Models Tpl - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Identity Models Tpl Promo Web - trunk Identity Models Xcf - trunk Identity Models Tpl - trunk -
- trunk/Identity/Models/Tpl/Promo/Web - trunk Identity Models Tpl Promo Web - - Goals - Organize scalable vector graphics (svg) to help describe the CentOS web environment. - - - - 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: - - • - - One unique name and one unique visual style to all web applications used inside the web environment. - - - One-step navigation to web applications inside the environment. - - - High degree of customization to change the visual style of all web applications with few changes (e.g, updating just two or three images plus common style sheet [CSS] definitions). - - - The CentOS project is attached to a monolithic corporate visual identity (see 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 supportThe theme support of Mailman may be introduced in mailman-3.x.x release. a customization system that separates presentation from logic, similar to that used by MoinMoin. - This visual style diversity complicates our goal of one unique visual style for all web applications. So, if we want one unique visual style for all web applications used, it is innevitable to modify the web applications in order to implement the CentOS one unique visual style customization in them. Direct modification of upstream applications is not convenient because upstream applications come with their one visual style and administrators take the risk of loosing all customization changes the next time the application be updated (since not all upstream web applications, used in CentOS web environment, separate presentation from logic). - To solve the “one unique visual style” issue, installation and actualization of web applications —used inside CentOS web environment— need to be independent from upstream web applications development line; in a way that CentOS web environment administrators can install and update web applications freely without risk of loosing the one unique visual style customization changes. - At the surface of this issue we can see the need of one specific yum repository to store CentOS web environment customized web applications. - - - Design model (without ads) - - - - Design model (with ads) - - - - HTML definitions - - - - Controlling visual style - Inside CentOS web environment, the visual style is controlled by the following compenents: - - - Webenv header background - - - - - - CSS definitions - - - - -
- - - - Producing visual style - The visual style of CentOS web environment is defined in the following files: - - 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. - - 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. - - - - 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. - - - - 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 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: - - - - - 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: - - The command above creates the following structure: - - 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. - - Tip Use the diff command of Subversion 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. - - - - - 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. - - 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. - - 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. - - - -
- - - - The [webenv-test] repository - - - - - - The [webenv] repository - - - - - - Priority configuration - Both [webenv] and [webenv-test] repositories update packages inside CentOS [base] and CentOS [updates] repositories. - - - - - Usage - - • - - ... - - - - - - See also - - - trunk Identity Models Img Promo Web - trunk Identity Models Img Promo Web - - - - -
- - - trunk Identity Models Xcf - trunk Identity Release - trunk Identity Models Tpl Promo Web - trunk -
- trunk/Identity/Models/Xcf - trunk Identity Models Xcf - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Identity Release - trunk Identity Themes - trunk Identity Models Xcf - trunk -
- trunk/Identity/Release - trunk Identity Release - - Goals - - • - - ... - - - - - - Description - - - - Usage - - - - See also - - - -
- - - trunk Identity Themes - trunk Identity Themes Models - trunk Identity Release - trunk -
- trunk/Identity/Themes - trunk Identity Themes - - Goals - The trunk/Identity/Themes/ directory exists to organize production of CentOS themes. - - - - Description - - - - 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. - - - trunk Identity Themes Models - trunk Identity Themes Models - - - - trunk Identity Themes Motifs - trunk Identity Themes Motifs - - - - - - - See also - - - trunk Identity - trunk Identity - - - - trunk - trunk - - - - -
- - - trunk Identity Themes Models - trunk Identity Themes Models Alternative - trunk Identity Themes - trunk -
- trunk/Identity/Themes/Models - trunk Identity Themes Models - - Goals - - • - - Organize theme models. - - - - - - 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. - - - - 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 trunk Identity Themes Models DefaultDefault,' and `See trunk Identity Themes Models AlternativeAlternative,' ready-to-use theme models. - - - - See also - - - -
- - - trunk Identity Themes Models Alternative - trunk Identity Themes Models Default - trunk Identity Themes Models - trunk -
- trunk/Identity/Themes/Models/Alternative - trunk Identity Themes Models Alternative - - Goals - - • - - ... - - - - - - 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. - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Identity Themes Models Default - trunk Identity Themes Models Default Distro - trunk Identity Themes Models Alternative - trunk -
- trunk/Identity/Themes/Models/Default - trunk Identity Themes Models Default - - Goals - This location stores CentOS default theme model. The default theme model of CentOS is used in all visual manifestations of CentOS Project corporate visual identity (e.g., distributions, web sites, promotion, etc.). - - - - Description - - - - 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 trunk Identity Themes MotifsTheme Motifs. - - - - See also - - - -
- - - trunk Identity Themes Models Default Distro - trunk Identity Themes Models Default Distro Anaconda - trunk Identity Themes Models Default - trunk -
- trunk/Identity/Themes/Models/Default/Distro - trunk Identity Themes Models Default Distro - - Goals - - • - - ... - - - - - - Description - It applies to all major releases of CentOS distribution. - - - 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. - 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 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. - - - - 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. - - - - - Usage - - - - See also - - - -
- - - trunk Identity Themes Models Default Distro Anaconda - trunk Identity Themes Models Default Promo - trunk Identity Themes Models Default Distro - trunk -
- trunk/Identity/Themes/Models/Default/Distro/Anaconda - trunk Identity Themes Models Default Distro Anaconda - - Goals - - • - - ... - - - - - - Description - - - - Usage - - - - See also - - - -
- - - trunk Identity Themes Models Default Promo - trunk Identity Themes Models Default Web - trunk Identity Themes Models Default Distro Anaconda - trunk -
- trunk/Identity/Themes/Models/Default/Promo - trunk Identity Themes Models Default Promo - - Goals - - • - - ... - - - - - - 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. - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Identity Themes Models Default Web - trunk Identity Themes Motifs - trunk Identity Themes Models Default Promo - trunk -
- trunk/Identity/Themes/Models/Default/Web - trunk Identity Themes Models Default Web - - Goals - - • - - ... - - - - - - 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. - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Identity Themes Motifs - trunk Identity Themes Motifs Flame - trunk Identity Themes Models Default Web - trunk -
- trunk/Identity/Themes/Motifs - trunk Identity Themes Motifs - - Goals - The trunk/Identity/Themes/Motifs directory exists to: - - • - - Organize CentOS themes' artistic motifs. - - - - - - Description - The artistic motif of theme is a graphic design component that provides the visual style of themes, it is used as pattern to connect all visual manifestations inside one unique theme. - Artistic motifs are based on conceptual ideas. Conceptual ideas bring the motivation, they are fuel for the engines of human imagination. Good conceptual ideas may produce good motivation to produce almost anything, and art works don't escape from it. - - - 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 the name of your artistic motif. If possible, when creating new conceptual ideas for CentOS, think about what CentOS means for you, what does it makes you feel, take your time, think deep, and share; you can improve the idea as time goes on. - Once you have defined a name for your theme, you need to create the motif structure of your theme. The motif structure is the basic direcotry structure you'll use to work your ideas. Here is where you organize your graphic design projects. - To add a new motif structure to CentOS Artwork Repository, you need to use the centos-art command line in the Identity/Themes/Motifs/ directory as described below: - centos-art add --motif=ThemeName - The previous command will create the basic structure of themes 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 - - - - Usage - When designing artistic motifs for CentOS, consider the following recommendations: - - • - - Give a unique (case-sensitive) name to your Motif. This name is used as value wherever theme variable ($THEME) or translation marker (=THEME=) is. Optionally, you can add a description about inspiration and concepts behind your work. - - - Use the location trunk/Identity/Themes/Motifs/$THEME/ to store your work. If it doesn't exist create it. Note that this require you to have previous commit access in CentOS Artwork Repository. - - - The CentOS Project is using the blue color (#204c8d) as base color for its corporate visual identity. Use such base corporate color information as much as possible in your artistic motif designs. - - - Try to make your design fit one of the theme models. - - - Feel free to make your art enterprise-level and beautiful. - - - Add the following information on your artwork (both in a visible design area and document metadata): - - • - - The name (or logo) of your artistic motif. - - - The copyright sentence: Copyright (C) YEAR YOURNAME - - - The license under which the work is released. All CentOS Art works are released under http://creativecommons.org/licenses/by-sa/3.0/Creative Common Share-Alike License 3.0 (http://creativecommons.org/licenses/by-sa/3.0/). - - - - - - - - See also - - - trunk Identity Themes - trunk Identity Themes - - - - trunk Identity - trunk Identity - - - - trunk - trunk - - - - -
- - - trunk Identity Themes Motifs Flame - trunk Identity Themes Motifs Modern - trunk Identity Themes Motifs - trunk -
- trunk/Identity/Themes/Motifs/Flame - trunk Identity Themes Motifs Flame - - Goals - This section describes the steps we followed to construct the Flame artistic motif. This section may be useful for anyone interested in reproducing the Flame artistic motif, or in creating new artistic motifs for The CentOS Project corporate visual identity (see trunk Identity). - - - - Description - The Flame artistic motif was built using the flame filter of Gimp 2.2 in CentOS 5.5. - The flame filter of Gimp can produce stunning, randomly generated fractal patterns. The flame filter of Gimp gives us a great oportunity to reduce the time used to produce new artistic motifs, because of its “randomly generated” nature. Once the artistic motif be created, it is propagated through all visual manifestations of CentOS Project corporate visual identity using the centos-art.sh script (see trunk Scripts Bash) inside the CentOS Artwork Repository. - To set the time intervals between each new visual style production, we could reuse the CentOS distribution major release schema. I.e., we could produce a new visual style, every two years, based on a new “randomly generated” flame pattern, and publish the whole corporate visual identity (i.e., distribution stuff, promotion stuff, websites stuff, etc.) with the new major release of CentOS distribution all together at once. - Producing a new visual style is not one day's task. Once we have defined the artistic motif, we need to propagate it through all visual manifestations of The CentOS Project corporate visual identity. When we say that we could produce one new visual style every two years we really mean: to work two years long in order to propagate a new visual style to all visual manifestations of The CentOS Project corporate visual identity. - Obviously, in order to propagate one visual style to all different visual manifestations of The CentOS Project corporate visual identity, we need first to know which the visual manifestations are. To define which visual manifestations are inside The CentOS Project corporate visual identity is one of the goals the CentOS Artwork Repository and this documentation manual are both aimed to satisfy. - Once we define which the visual manifestation are, it is possible to define how to produce them, and this way, organize the automation process. Such automation process is one of the goals of centos-art.sh script. - With the combination of both CentOS Artwork Repository and centos-art.sh scripts we define work lines where translators, programmers, and graphic designers work together to distribute and reduce the amount of time employed to produce The CentOS Project monolithic corporate identity. - From a monolithic corporate visual identity point of view, notice that we are producing a new visual style for the same theme (i.e., Flame). It would be another flame design but still a flame design. This idea is very important to be aware of, because we are somehow “refreshing” the theme, not changing it at all. - This way, as we are “refreshing” the theme, we still keep oursleves inside the monolithic conception we are trying to be attached to (i.e., one unique name, and one unique visual style for all visual manifestations). - Producing artistic motifs is a creative process that may consume long time, specially for people without experienced knowledge on graphic design land. Using “randomly generated” conception to produce artistic motifs could be, practically, a way for anyone to follow in order to produce maintainable artistic motifs in few steps. - Due to the “randomly generated” nature of Flame filter, we find that Flame pattern is not always the same when we use Flame filter interface. - Using the same pattern design for each visual manifestation is essential in order to maintain the visual connection among all visual manifestations inside the same theme. Occasionally, we may introduce pattern variations in opacity, size, or even position but never change the pattern design itself, nor the color information used by images considered part of the same theme. - - Important When we design background images, which are considered part of the same theme, it is essential to use the same design pattern always. This is what makes theme images to be visually connected among themeselves, and so, the reason we use to define the word “theme” as: a set of images visually connected among themeselves. - - In order for us to reproduce the same flame pattern always, Flame filter interface provides the Save and Open options. The Save option brings up a file save dialog that allows you to save the current Flame settings for the plug-in, so that you can recreate them later. The Open option brings up a file selector that allows you to open a previously saved Flame settings file. - The Flame settings we used in our example are saved in the file: - - - - - Construction - - Step 1: Set image size - Create an empty image and fill the Background layer with black (000000) color. Image dimensions depend on the final destination you plan to use the image for. For the sake of our construction example we used an image of 640x480 pixels and 300 pixels per inch (ppi). - - - - Step 2: Add base color and pattern information - Create a new layer named Base, place it over Background layer and fill it with the base color (7800ff) you want to have your background image set in. Add a mask to Base layer using radial gradient and blur it. You may need to repeat this step more than once in order to achieve a confortable black radial degradation on the right side of your design. - Duplicate Base layer and name it Paper. Place Paper layer over Base layer. Remove content of Paper layer and fill it with Paper (100x100) pattern. Once you've done with black radial degradation, reduce the Paper layer opacity to 20%. - Notice that when we duplicate one layer, the mask information related to layer is preserved from previous to next layer. This saves us some of the time required to produce different layers with the same mask information on them. - Duplicate Paper layer and rename it Stripes. Remove paper pattern from Stripes layer. Fill Stripes layer with Stripes (48x48) pattern and reduce the Stripes layer opacity to 15%. - - - - Step 3: Add flame motif - Create a new layer named Flame. Set the foreground (003cff) and background (0084ff) colors to the gradient you want to build the flame motif. - To build flame motif, use the flame filter (Filters > Render > Nature > Flame...) on Flame layer. We used a layer mask, with a radial gradient on it to control the boundaries of flame motif on Flame layer. - Duplicate Flame layer and rename it `Flame Blur'. Place `Flame Blur' below Flame layer. Apply Gussian blur filter (Filters > Blur > Gussian Blur...) until reaching the desiered effect. - The opacity value, in Flame layers, may vary from one image to another based on the place the image will be finally placed on. For example, images used as desktop background have the Flame layer opacity set at 100% but Flame Blur is set to 70%. However, you may find that background images used in anaconda progress slides have opacity reduced differently, in order to reduce brightness in a way that texts could look clean and readable over it. - - - - Step 4: Add foreground color - Create a new layer named Color, place it on top of all visible layers and fill it with plain color (4c005a). Reduce Color layer opacity to 20%. You can use the Color layer to control the right side color information you want to produce the image for. - Duplicate Flame layer and create a new layer named Color#1. Place Color#1 layer on top of layer named Color. Remove the mask information from Color#1 layer and recreate a new one using an inverted alpha channel as reference. Remove Color#1 layer content and fill it back with plain black (000000) color. Reduce Color#1 opacity to 20%. In this step we created a mask to protect the flame artistic motif from black color, so when we decrement or increment the opacity of layer, the flame artistic motif wouldn't be affected, just the environment suround it. - When you set color information, remember that the same artistic motif needs to be indexed to 14 and 16 colors, in order to produce Grub and Syslinux visual manifestations respectively. Using many different colors in the artistic motif may reduce the possibility of your design to fix all different situations in. Likewise, using more colors in one design, and less colors in another design will reduce the connectivity among your designs, since color information is relevant to visual identity. - When you propagate your artistic motif visual style to different visual manifestations of CentOS Project corporate visual identity, it is up to you to find out justice and compromise among all possible variables you may face. - - - - - See also - - - trunk Identity Themes Motifs - trunk Identity Themes Motifs - - - - trunk Identity Themes - trunk Identity Themes - - - - trunk Identity - trunk Identity - - - - trunk - trunk - - - - -
- - - trunk Identity Themes Motifs Modern - trunk Identity Themes Motifs Modern Backgrounds - trunk Identity Themes Motifs Flame - trunk -
- trunk/Identity/Themes/Motifs/Modern - trunk Identity Themes Motifs Modern - - Presentation - - - - Construction - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Identity Themes Motifs Modern Backgrounds - trunk Identity Themes Motifs Modern Backgrounds Img - trunk Identity Themes Motifs Modern - trunk -
- trunk/Identity/Themes/Motifs/Modern/Backgrounds - trunk Identity Themes Motifs Modern Backgrounds - - Goals - - • - - Organize background images for Modern theme. - - - - - - Description - Inside Motifs directory, the Backgrounds/ directory is used to 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 the import feautre of Inkscape. - 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 (e.g. Anaconda), 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 artistic motif. - Background images are linked (using the import feature of Inkscape) inside almost all theme art works. This structure let you make centralized changes on the visual identity and propagate them quickly to other areas. - In this structure you design background images for different screen resolutions based on the theme artistic motif. - You may create different artistic motifs propositions based on the same conceptual idea. The conceptual idea is what defines a theme. Artistic motifs are interpretations of that idea. - Inside this directory artistic motifs are organized by name (e.g., TreeFlower, Modern, etc.). - Each artistic motif directory represents just one unique artistic motif. - The artistic motif is graphic design used as common pattern to connect all visual manifestations inside one unique theme. The artistic motif is based on a conceptual idea. Artistic motifs provide visual style to themes. - Designing artistic motifs is for anyone interested in creating beautiful themes for CentOS. When building a theme for CentOS, the first design you need to define is the artistic motif. - Inside CentOS Artwork Repository, theme visual styles (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 Motifs/ directory using the model name, and 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. - - - - Usage - The Backgrounds/ directory is probably the core component, inside Motifs/ directory structure. Inside Backgrounds/ directory you produce background images used by almost all theme models (e.g., Distribution, Websites, Promotion, etc.). The Backgrounds/ directory can contain subdirectories to help you organize the design process. - - - - See also - - - trunk Identity Themes Motifs Modern Backgrounds Img - trunk Identity Themes Motifs Modern Backgrounds Img - - - - trunk Identity Themes Motifs Modern Backgrounds Tpl - trunk Identity Themes Motifs Modern Backgrounds Tpl - - - - trunk Identity Themes Motifs Modern Backgrounds Xcf - trunk Identity Themes Motifs Modern Backgrounds Xcf - - - - - -
- - - trunk Identity Themes Motifs Modern Backgrounds Img - trunk Identity Themes Motifs Modern Backgrounds Tpl - trunk Identity Themes Motifs Modern Backgrounds - trunk -
- trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img - trunk Identity Themes Motifs Modern Backgrounds Img - - Goals - - • - - ... - - - - - - Description - - - - 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. - - - - See also - - - -
- - - trunk Identity Themes Motifs Modern Backgrounds Tpl - trunk Identity Themes Motifs Modern Backgrounds Xcf - trunk Identity Themes Motifs Modern Backgrounds Img - trunk -
- trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl - trunk Identity Themes Motifs Modern Backgrounds Tpl - - Goals - - • - - ... - - - - - - Description - - - - 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. - - - - See also - - - -
- - - trunk Identity Themes Motifs Modern Backgrounds Xcf - trunk Identity Themes Motifs Modern Distro Anaconda Progress - trunk Identity Themes Motifs Modern Backgrounds Tpl - trunk -
- trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf - trunk Identity Themes Motifs Modern Backgrounds Xcf - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - In this directory is where you store the project files (e.g, .xcf) of Gimp. 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 background projects. Of course, you can merge both Gimp and Inkscape power to produce images based on them. In this last case you need the Xcf/ directory. - - - - See also - - - -
- - - trunk Identity Themes Motifs Modern Distro Anaconda Progress - trunk Identity Themes Motifs Modern Palettes - trunk Identity Themes Motifs Modern Backgrounds Xcf - trunk -
- trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress - trunk Identity Themes Motifs Modern Distro Anaconda Progress - - Goals - - • - - ... - - - - - - Description - - - - Usage - To render Anaconda progress slide images using the Modern artistic motif design, the Default theme model, and available translation files (— Removed(pxref:trunk Translations Identity Themes Distro Anaconda Progress) —); use the following commands: - cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ -centos-art render --identity - The above command will create the following structure: - trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress -|-- 3 -| |-- en -| | |-- 01-welcome.png -| | |-- 02-donate.png -| | `-- 03-yum.png -| `-- es -| |-- 01-welcome.png -| |-- 02-donate.png -| `-- 03-yum.png -|-- 4 -| |-- en -| | |-- 01-welcome.png -| | |-- 02-donate.png -| | `-- 03-yum.png -| `-- es -| |-- 01-welcome.png -| |-- 02-donate.png -| `-- 03-yum.png -`-- 5 - |-- en - | |-- 01-welcome.png - | |-- 02-donate.png - | `-- 03-yum.png - `-- es - |-- 01-welcome.png - |-- 02-donate.png - `-- 03-yum.png - - - - See also - - - -
- - - trunk Identity Themes Motifs Modern Palettes - trunk Identity Themes Motifs TreeFlower - trunk Identity Themes Motifs Modern Distro Anaconda Progress - trunk -
- trunk/Identity/Themes/Motifs/Modern/Palettes - trunk Identity Themes Motifs Modern Palettes - - Goals - - • - - Organize palette files for Modern theme. - - - - - - Description - - - - 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 the unique color information required by theme. - - - - See also - - - -
- - - trunk Identity Themes Motifs TreeFlower - trunk Identity Themes Motifs TreeFlower Backgrounds - trunk Identity Themes Motifs Modern Palettes - trunk -
- trunk/Identity/Themes/Motifs/TreeFlower - trunk Identity Themes Motifs TreeFlower - - Goals - - • - - ... - - - - - - Description - - - - Usage - - - - See also - - - -
- - - trunk Identity Themes Motifs TreeFlower Backgrounds - trunk Identity Widgets - trunk Identity Themes Motifs TreeFlower - trunk -
- trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds - trunk Identity Themes Motifs TreeFlower Backgrounds - - Goals - This section exists to orgnize backgrounds of TreeFlower artistic motif. - - - - Description - - Desktop background - Once you have defined the vectorial artistic motif design, use the centos-art.sh script (as described in usage section below) to produce the png version of it. With the png version of your vectorial design do the following: - Open the png version with GIMP. - Save the png version as a project of GIMP inside trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Xcf directory, using the same name of your vectorial design but with the .xcf extension. - Now use GIMP to improve your design. Here you may add one layer for pattern, another for colors, and so on until you find yourself confortable with your artwork. For example, the following layer distribution (from bottom to top) was used to build revision 285 of file 1360x768.xcf using TreeFlower artistic motif at revision 241. - - - Layer 1: Background - - The first thing we did with GIMP was to create a layer named Background to store the artistic motif (File > Open as layer). This layer is the lowest layer in the image. Later, we started to create layers one upon another to change the artistic motif visual style. - - - - Layer 2: Shadow#1 - - This layer is above Background and contains a linear gradient from left (000000) to right (transparent) covering the whole image. This layer masks the artistic motif to avoid the effect of linear gradient. This layer is 100% of opacity. - - - - Layer 3: Shadow#2 - - This layer is above Shadow#1 and contains a linear gradient from left (000000) to right (transparent) covering just the 70% of the whole image aproximatly. This layer doesn't mask the artistic motif which make the left part of it fall into the dark of linear gradient. This layer is 100% of opacity. - - - - Layer 4: Pattern (Paper) - - This layer is above Shadow#2 an contains the paper pattern shipped with GIMP 2.2. This layer doesn't mask the artistic motif so the pattern is applied over the whole image. This layer is set to 15% of opacity. - - - - Layer 5: Pattern (Stripes) - - This layer is above Pattern (Paper) and contains the stripes used over the artistic motif. This layer do masks the artistic motif so the stripes are only applied to it. This layer is set to 10% of opacity. - - - - Layer 6: Shadow#3 - - This layer is above Pattern (Stripes) and contains a linear gradient from right (6600ff) to left (transparent). This layer masks the artistic motif so the linear gradient doesn't affect it. This layer is set to 15% of opacity. - - - - Layer 7: Shadow#4 - - This layer is above Shadow#3 and contains a linear gradient from left (000000) to right (transparent). This layer do masks the artistic motif so the linear gradient doesn't affect it. This layer is set to 10% of opacity. - - - - Layer 8: Color#1 - - This layer is above Shadow#4 and is filled with orange (ffae00) color over the whole image. This layer is set to 10% of opacity. - - - - Layer 9: Color#2 - - This layer is above Color#1 and is filled with blue (010a88) color over the whole image. This layer is set to 10% of opacity. - - -
- - Note There is no definite combination. To get the appropriate visual design is a matter of constant testing and personal taste. - - Finally, use Save as copy ... option to export the final design. To export the final design use the same name of your vectorial design plus -final.png extension. - You can repeat these steps to create images for other screen resolutions. - - - - Anaconda Prompt (syslinux) background - When building syslinux backgrounds it is needed to take into account that the final image is reduced to 16 colors. In desktop background there is no color limitation but syslinux does have. The goal of this section is achieving a final syslinux background as close as possible to desktop backgrounds using 16 colors only. - Another point to consider is the forground and background definition used by syslinux. The syslinux documentation says that the color set in position 0 is the background and color set in position 7 is the forground. The final palette of color used by our background will match that specification. For great contrast we'll use black as background and white as forground. At this poing we have black (000000) and white (ffffff) colors in our syslinux palette, which left us with 14 colors to play with. - Let's begin with Xcf/640x300.xcf layer distribution from bottom to top: - - - Layer 1: Background - - This layer is the lowest layer in the image composition and contains the artistic motif image rendered for the same resolution (i.e., Img/Png/640x300.png). This layer is set to 100% of opacity. - - - - Layer 2: Pattern (Paper) - - This layer is placed above Background layer and contains the paper pattern shipped with GIMP 2.2. This layer doesn't mask the artistic motif. This layer is set to 30% of opacity. - - - - Layer 3: Pattern (Stripes) - - This layer is placed above Pattern (Paper) layer and contains the stripes pattern shipped with GIMP 2.2. This layer does mask the artistic motif in order to apply the stripes over it only. The background is not affected by the stripes pattern just the artistic motif. This layer is set to 20% of opacity. - - - - Layer 4: Shadow#1 - - This layer is placed above Pattern (Stripes) layer and fills the entire layer area with violet (6600ff) color. This layer do mask the artistic motif in order to applied the violet color to the background area outside the artistic motif only. This layer is set to 15% of opacity. - - - - Layer 5: Color#1 - - This layer is above Shadow#1 and is filled with orange (ffae00) color to cover the whole image. This layer is set to 10% of opacity. - - - - Layer 6: Color#2 - - This layer is above Color#1 and is filled with blue (010a88) color to cover the whole image. This layer is set to 10% of opacity. - - - - Layer 7: Shadow#2 - - This layer is above Color#1 and contains a linear gradient from left (000000) to right (transparent) covering 70% of the image approximately. - - -
- At this point we have the composition and should look like the desktop backgrounds. Compared with desktop backgrounds there are some differences in opacity. This is because in our testings the final color information found with this composition produces an acceptable 16 color image. Of course this is something we haven't seen yet. - To define the color information of our current coposition, save the syslinux background composition we've done using File > Save as Copy ... option in the following location: - - Now, create the final png version of syslinux backgrounds using the following command: - - This command will create syslinux-splash final images for all major releases of CentOS distribution the repository has been configured to. The important files here are syslinux-splash.png, other files may contain the wrong information because we haven't defined yet the correct color information to use. - Open one syslinux-splash.png file with GIMP and use the Image > Mode > Indexed to reduce image colors up to 16 colors, using the Generate optimum palette feature of GIMP. If the image looks aceptable after reducing colors, use the Palettes menu (Ctrl+P) of GIMP to import a new palette from file and name it CentOS-TreeFlower-Syslinux. Once you've saved the palette, the color information is stored at: - - You need to edit CentOS-TreeFlower-Syslinux.gpl file in order to set the appropriate order of colors. Remember black (000000) in position 0, and white (ffffff) in position 7. Other positions are irrelevant. When editing this file you may find that color reduction did not set black and white colors to their respective values exactly. Change that manually. For example, consider the following palette: - - Update the Palettes menu to get the new color positions from the file you just edited and open the palette with double click. - Update the syslinux.gpl file copying the following file: - - to - - With the CentOS-TreeFlower-Syslinux palette opened in the Palette Editor, open (Ctrl+O) the following file: - - and replace its color information with that one in CentOS-TreeFlower-Syslinux palette. When you are replacing color information inside syslilnux.ppm, remember to keep the order of colors just as they are in the CentOS-TreeFlower-Palette palette. - The syslinux.ppm file is 16 pixels width and 1 pixel height, so you probably need to zoom it a bit to set the color information in their place when using the pen tool with the brush Circle (01) (1 x 1). - Once you've updated the syslinux.ppm file, it is time to update the following file: - - The syslinux.hex file contains the color information in hexadecimal notation. The color information in hexadecimal notation is required by ppmtolss16 command. The ppmtolss16 command produces the final LSS16 image format that is used by syslinux program inside CentOS distribution. - The color information inside syslinux.hex must match the one in syslinux.ppm and syslinux.gpl. For example, based on CentOS-TreeFlower-Syslinux palette of colors above, consider the following syslinux.hex file: - - - - - Grub background - - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Identity Widgets - trunk Locales - trunk Identity Themes Motifs TreeFlower Backgrounds - trunk -
- trunk/Identity/Widgets - trunk Identity Widgets - - Goals - - • - - ... - - - - - - Description - - - - Usage - - - - See also - - - -
- - - trunk Locales - trunk Locales Identity - trunk Identity Widgets - trunk -
- trunk/Locales - trunk LocalesThe trunk/Locales directory exists to store the translation messages used to produce content in different languages. - Translation messages are organized using the directory structure of the component being translated. For example, if we want to provide translation messages for trunk/Manuals/Filesystem, then the trunk/Locales/Manuals/Filesystem directory needs to be created. - Once the locale directory exists for the component we want to provide translation messages for, it is necessary to create the translation files where translation messages are. The translation files follows the concepts of xml2po and GNU gettext tools. - The basic translation process is as follow: first, translatable strings are extracted from files and a portable object template (.pot) is created or updated with the information. Using the portable object template, a portable object (.po) is created or updated for translator to locale the messages retrived. Finally, a machine object (.mo) is created from portable object to sotore the translated messages. - Inside the repository there are two ways to retrive translatable strings from files. The first one is through xml2po command and the second through xgettext command. The xml2po is used to retrive translatable strings from XML files (e.g., Scalable Vector Graphics, DocBook, etc.) and the xgettext command is used to retrive translatable strings from shell scripts files (e.g., the files that make the centos-art.sh command-line interface). - When translatable strings are retrived from XML files, using the xml2po command, there is no need to create the machine object as we do when translatable strings ar retrived from shell files, using the xgettext command. The xml2po produces a temporal machine object in order to create a translated XML file. Once the translated XML file has been created the machine object is no longer needed. On the other hand, the machine object produced by the xgettext command is required by the system in order for the show shell script localized messages. - Another difference between xml2po and xgettext we need to be aware of is the directory structure used to store machine objects. In xml2po, the machine object is created in the current working directory as .xml2po.mo and can be safetly removed once the translated XML file has been created. In the case of xgettext, the machine object needs to be stored in the $TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo file in order for the system to interpret it and should not be removed since it is the file that contain the translation messages themselves. - Automation of localization tasks is achived through the locale functionality of command-line interface. - - - trunk Scripts Bash Cli Functions Locale - trunk Scripts Bash Cli Functions Locale - - - -
- - - trunk Locales Identity - trunk Locales Identity Brands - trunk Locales - trunk -
- trunk/Locales/Identity - trunk Locales Identity - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - - - - - - - trunk Identity - trunk Identity - - - - -
- - - trunk Locales Identity Brands - trunk Locales Identity Brands Tpl - trunk Locales Identity - trunk -
- trunk/Locales/Identity/Brands - trunk Locales Identity Brands - - Goals - - • - - Organize brands' translation files. - - - - - - 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: - - 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: - - - Conventional file names - Translation brands 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. - - - - Numeric file names - Translation brands 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 designing ratio. - For example, if your design template has 400x200 pixels of dimension, and you apply a translation file named `300.sed' to it, the final image you get as result will have 300x100 pixels of dimension. The same is true if you use higher numbers like `1024.sed', `2048.sed', etc. In these cases you have bigger images proportionally. - As we are using scalable vector graphics to design identity templates, the image size you produce is not limitted in size. You can use one design template produced in 400x200 pixels to produce larger or shorter PNG images using numeric translation files as described above. - - - - Translation markers - Inside trunk/Translations/Identity/Brands/, translation files combine the following translation markers: - - - #000000 - - Specify which color to use when rendering brand images. - - 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. - - - -
- - - - - Usage - How to render brands' translation files To render brands' translation files, use the following command: - - - - - See also - - - - trunk Identity Brands - trunk Identity Brands - - - - -
- - - trunk Locales Identity Brands Tpl - trunk Locales Identity Fonts - trunk Locales Identity Brands - trunk -
- trunk/Locales/Identity/Brands/Tpl - trunk Locales Identity Brands Tpl - - Goals - - - - Description - - - - Usage - - - - See also - - - -
- - - trunk Locales Identity Fonts - trunk Locales Identity Models - trunk Locales Identity Brands Tpl - trunk -
- trunk/Locales/Identity/Fonts - trunk Locales Identity Fonts - - Goals - This section exists to organize fonts translation files. - - - - Description - Translation files, inside trunk/Translations/Fonts, have the following structure: - - 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 Do not create translation files for font-families not used somewhere inside CentOS visual identity. The identity of font entry (see trunk Identity Fonts) is used as reference when someone needs to know which font-families are allowed to use inside CentOS visual identity. - - - - 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. - - -
- - - - - Usage - How to render fonts' translation files 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: - - - - - See also - - - trunk Identity Fonts - trunk Identity Fonts - - - - -
- - - trunk Locales Identity Models - trunk Locales Identity Release - trunk Locales Identity Fonts - trunk -
- trunk/Locales/Identity/Models - trunk Locales Identity Models - - Goals - - - - Description - - - - Usage - - - - See also - - - -
- - - trunk Locales Identity Release - trunk Locales Identity Themes - trunk Locales Identity Models - trunk -
- trunk/Locales/Identity/Release - trunk Locales Identity Release - - Goals - - - - Description - - - - Usage - - - - See also - - - -
- - - trunk Locales Identity Themes - trunk Locales Identity Themes Backgrounds - trunk Locales Identity Release - trunk -
- trunk/Locales/Identity/Themes - trunk Locales Identity Themes - - Goals - - - - Description - - - - Usage - - - - See also - - - -
- - - trunk Locales Identity Themes Backgrounds - trunk Locales Identity Themes Distro Anaconda Progress - trunk Locales Identity Themes - trunk -
- trunk/Locales/Identity/Themes/Backgrounds - trunk Locales Identity Themes Backgrounds - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Locales Identity Themes Distro Anaconda Progress - trunk Locales Identity Widgets - trunk Locales Identity Themes Backgrounds - trunk -
- trunk/Locales/Identity/Themes/Distro/Anaconda/Progress - trunk Locales Identity Themes Distro Anaconda Progress - - Goals - - • - - Organize Anaconda progress translation templates. - - - Organize Anaconda progress translation files in several languages and major releases of CentOS distribution. - - - - - - 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. - - • - - See trunk Identity Themes Motifs Modern Distro Anaconda Progress. - - - - - - Usage - Translation rendering is described in trunk/Translations documentation entry (— Removed(pxref:trunk Translations) —). - - - - See also - -
- - - trunk Locales Identity Widgets - trunk Manuals - trunk Locales Identity Themes Distro Anaconda Progress - trunk -
- trunk/Locales/Identity/Widgets - trunk Locales Identity Widgets - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - - -
- - - trunk Manuals - trunk Scripts - trunk Locales Identity Widgets - trunk -
- trunk/Manuals - trunk Manuals - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Scripts - trunk Scripts Bash - trunk Manuals - trunk -
- trunk/Scripts - trunk Scripts - - Goals - The trunk/Scripts directory exists to: - - • - - Organize the “trunk” development line of automation scripts by programming language. - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Scripts Bash - trunk Scripts Bash Cli - trunk Scripts - trunk -
- trunk/Scripts/Bash - trunk Scripts Bash - - Goals - The trunk/Scripts/Bash directory exists to organize the trunk development line of centos-art.sh automation script. The centos-art.sh script standardizes frequent tasks inside your working copy of CentOS Artwork Repository. - - - - Description - The best way to understand centos-art.sh automation script is studying its source code. However, as start point, you may prefer to read an introductory resume before diving into the source code details. - The centos-art.sh script is written in Bash. Most tasks, inside centos-art.sh script, have been organized in many specific functionalities that you can invoke from the centos-art command-line interface. - 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 location. If your system was prepared to use CentOS Artwork Repository correctly (— Removed(pxref:trunk Scripts Bash Functions Verify) —), you should have a symbolic link inside ~/bin/ directory that points to the centos-art.sh script file. As ~/bin/ directory is, by default, inside PATH environment variable, the execution of centos-art command runs the centos-art.sh script. - When centos-art.sh script is executed, the first it does is executing the trunk/Scripts/Bash/initEnvironment.sh script to initialize global variables (e.g., gettext variables) and global function scripts. Global function scripts are located inside trunk/Scripts/Bash/Functions directory and their file names begin with cli. Global function scripts provide common functionalities that can be used anywhere inside centos-art.sh script execution environment. - Once global variables and function scripts have been loaded, centos-art.sh script executes the cli global function from cli.sh function script to retrive command-line arguments and define some default values that may be used later by specific function scripts (— Removed(pxref:trunk Scripts Bash Functions) —). - As convenction, the centos-art.sh command-line arguments have the following format: - - In the above example, centos-art is the command you use to invoke centos-art.sh script. The arg1 is required and represents the functionality you want to perform (e.g., , , , , etc.). The remaining arguments are modifiers to . The definition is required and represets, specifically, the action inside the functionality you want to perform. The and on, are optional. - Once command-line arguments have been retrived, the centos-art.sh script loads specific functionalities using the cli_getFunctions.sh function script. Only one specific functionality can be loaded at one script execution I.e., you run centos-art.sh script to run just one functionality. - - Figure - - ~/artwork/trunk/Scripts/Bash/centos-art.sh | -+---v-----------------------------------------v------------------------+ - | centos-art.sh | - +---v---------------------------------v---+ - . | initEnvironment.sh | . - . +---------------------------------+ . - . | cli $@ | . - . +---v-------------------------v---+ . - . . | cli_getFunctions | . . - . . +---v-----------------v---+ . . - . . . | function1 | . . . - . . . | function2 | . . . - . . . | function3 | . . . - . . . +-----------------+ . . . - . . ........................... . . - . ................................... . - ........................................... -]]> - The functionalities initialization environment. - - Functionalities are implemented by means of actions. Once the functionality has been initiazalized, actions initialization take place for that functionality. Actions initialization model is very similar to functions initialization model. But with the difference, that actions are loaded inside function environment, and so, share variables and functions defined inside function environment. - - Figure - - - The actions initialization environment. - - - - - Usage - The centos-art.sh script usage information is described inside each specific function documentation (— Removed(pxref:trunk Scripts Bash Functions) —). - - - - See also - - - trunk Scripts - trunk Scripts - - - - - - -
- - - trunk Scripts Bash Cli - trunk Scripts Bash Cli Functions - trunk Scripts Bash - trunk -
- trunk/Scripts/Bash/Cli - trunk Scripts Bash Cli -
- - - trunk Scripts Bash Cli Functions - trunk Scripts Bash Cli Functions Help - trunk Scripts Bash Cli - trunk -
- trunk/Scripts/Bash/Cli/Functions - trunk Scripts Bash Cli Functions - - Goals - The trunk/Scripts/Bash/Functions directory exists to organize centos-art.sh specific functionalities. - - - - Description - The specific functions of centos-art.sh script are designed with “Software Toolbox” philosophy (see Toolbox introductioncoreutils.info) in mind: each program “should do one thing well”. Inside centos-art.sh script, each specific functionality is considered a program that should do one thing well. Of course, if you find that they still don't do it, feel free to improve them in order for them to do so. - The specific functions of centos-art.sh script are organized inside specific directories under trunk/Scripts/Bash/Functions location. Each specific function directory should be named as the function it represents, with the first letter in uppercase. For example, if the function name is render, the specific function directory for it would be trunk/Scripts/Bash/Functions/Render. - To better understand how specific functions of centos-art.sh script are designed, lets create one function which only goal is to output different kind of greetings to your screen. - When we create specific functions for centos-art.sh script it is crucial to know what these functions will do exactly and if there is any function that already does what we intend to do. If there is no one, it is good time to create them then. Otherwise, if functionalities already available don't do what you exactly expect, contact their authors and work together to improve them. - - Tip Join CentOS developers mailing list centos-art@centos.org to share your ideas. - - It is also worth to know what global functions and variables do we have available inside centos-art.sh script, so advantage can be taken from them. Global variables are defined inside global function scripts. Global functions scripts are stored immediatly under trunk/Scripts/Bash/Functions directory, in files begining with cli prefix. - OK, let's begin with our functionality example. - What function name do we use? Well, lets use greet. Note that hello word is not a verb; but an expression, a kind of greeting, an interjection specifically. In contrast, greet is a verb and describes what we do when we say Hello!, Hi!, and similar expressions. - So far, we've gathered the following function information: - - The greet.sh function script is the first file centos-art.sh script loads when the greet functionality is called using commands like centos-art greet --hello='World'. The greet.sh function script contains the greet function definition. - Inside centos-art.sh script, as convenction, each function script has one top commentary, followed by one blank line, and then one function defintion below it only. - Inside centos-art.sh script functions, top commentaries have the following components: the functionality description, one-line for copyright note with your personal information, the license under which the function source code is released —the centos-art.sh script is released as GPL, so do all its functions—, the $Id$ keyword of Subversion is later expanded by svn propset command. - In our greet function example, top commentary for greet.sh function script would look like the following: - - After top commentary, separated by one blank line, the greet function definition would look like the following: - - The first definition inside greet function, are global variables that will be available along greet function execution environment. This time we didn't use global variable definitions for greet function execution environment, so we left that section empty. - Later, we call greet_getActions function to define the command-line interface of greet functionality. The command-line interface of greet functionality defines what and how actions are performed, based on arguments combination passed to centos-art.sh script. - - The ACTIONNAM global variable is defined in cli.sh function script and contains the value passed before the equal sign (i.e., =) in the second command-line argument of centos-art.sh script. For example, if the second command-line argument is , the value of ACTIONNAM variable would be --hello. Using this configuration let us deside which action to perform based on the action name passed to centos-art.sh script as second argument. - The greet function definition makes available two valid greetings through and options. If no one of them is provided as second command-line argument, the * case is evaluated instead. - The * case and its two lines further on should always be present in _getActions.sh function scripts, no matter what specific functionality you are creating. This convenction helps the user to find out documentation about current functionality in use, when no valid action is provided. - The greet_doHello and greet_doBye function definitions are the core of greet specific functionality. In such function definitions we set what our greet function really does: to output different kinds of greetings. - - The greet_doHello function definition is stored in greet_doHello.sh function script. - - The greet_doBye function definition is stored in the greet_doBye.sh function script. - Both greet_doHello.sh and greet_doBye.sh function scripts are stored inside greet function directory path (i.e. trunk/Scripts/Bash/Functions/Greet). - The ACTIONVAL global variable is defined in cli.sh function script and contains the value passed after the equal sign (i.e., =) in the second command-line argument of centos-art.sh script. For example, if the second command-line argument is , the value of ACTIONVAL variable would be World without quotes. - Let's see how greet specific functionality files are organzied under greet function directory. To see file organization we use the tree command: - - To try the greet specific functionality we've just created, pass the function name (i.e., greet) as first argument to centos-art.sh script, and any of the valid options as second argument. Some examples are illustrated below: - - The word World in the examples above can be anything. In fact, change it to have a little fun. - Now that we have a specific function that works as we expect, it is time to document it. To document greet specific functionality, we use its directory path and the manual functionality (— Removed(pxref:trunk Scripts Bash Functions Manual) —) of centos-art.sh script, just as the following command illustrates: - - To have a well documented function helps user to understand how your function really works, and how it should be used. When no valid action is passed to a function, the centos-art.sh script uses the function documentation entry as vehicle to communicate which the valid functions are. When no documentation entry exists for a function, the centos-art.sh script informs that no documentation entry exists for such function and requests user to create it right at that time. - Now that we have documented our function, it is time to translate its output messages to different languages. To translate specific functionality output messages to different languages we use the locale functionality (— Removed(pxref:trunk Scripts Bash Functions Locale) —) of centos-art.sh script, just as the following command illustrates: - - - Warning To translate output messages in different languages, your system locale information —as in LANG environment variable— must be set to that locale you want to produce translated messages for. For example, if you want to produce translated messages for Spanish language, your system locale information must be set to es_ES.UTF-8, or similar, first. - - Well, it seems that our example is rather complete by now. - In greet function example we've described so far, we only use cli_printMessage global function in action specific function definitions in order to print messages, but more interesting things can be achieved inside action specific function definitions. For example, if you pass a directory path as action value in second argument, you could retrive a list of files from therein, and process them. If the list of files turns too long or you just want to control which files to process, you could add the third argument in the form and reduce the amount of files to process using a regular expression pattern. - The greet function described in this section may serve you as an introduction to understand how specific functionalities work inside centos-art.sh script. With some of luck this introduction will also serve you as motivation to create your own centos-art.sh script specific functionalities. - By the way, the greet functionality doesn't exist inside centos-art.sh script yet. Would you like to create it? - - - - Usage - - Global variables - The following global variables of centos-art.sh script, are available for you to use inside specific functions: - - TEXTDOMAIN - Variable - TEXTDOMAIN - - - Default domain used to retrieve translated messages. This value is set in initFunctions.sh and shouldn't be changed. - - - - TEXTDOMAINDIR - Variable - TEXTDOMAINDIR - - - Default directory used to retrieve translated messages. This value is set in initFunctions.sh and shouldn't be changed. - - - - FUNCNAM - Variable - FUNCNAM - - - Define function name. - Function names associate sets of actions. There is one set of actions for each unique function name inside centos-art.sh script. - Dunction names are passed as first argument in centos-art.sh command-line interface. For example, in the command centos-art render --entry=path/to/dir --filter=regex, the ACTION passed to centos-art.sh script is . - When first argument is not provided, the centos-art.sh script immediatly ends its execution. - - - - FUNCDIR - Variable - FUNCDIR - - - - FUNCDIRNAME - Variable - FUNCDIRNAME - - - - FUNCSCRIPT - Variable - FUNCSCRIPT - - - - FUNCCONFIG - Variable - FUNCCONFIG - - - - ACTIONNAM - Variable - ACTIONNAM - - - Define action name. - Each action name identifies an specific action to perform, inside an specific function. - Action name names aare passed as second argument in centos-art.sh command-line interface. For example, in the command centos-art render --entry=path/to/dir --filter=regex, the ACTIONNAM passed to centos-art.sh script is . - When second argument is not provided, the centos-art.sh script immediatly ends its execution. - - - - ACTIONVAL - Variable - ACTIONVAL - - - Define action value. - Action values are associated to just one action name. Action values contain the working copy entry over which its associated action will be performed in. Working copy entries can be files or directories inside the working copy. - - - - REGEX - Variable - REGEX - - - Define regular expression used as pattern to build the list of files to process. - By default, REGEX variable is set to .+ to match all files. - Functions that need to build a list of files to process use the option to redefine REGEX variable default value, and so, control the amount of files to process. - - - - ARGUMENTS - Variable - ARGUMENTS - - - Define optional arguments. - Optional arguments, inside centos-art.sh script, are considered as all command-line arguments passed to centos-art.sh script, from third argument position on. For example, in the command centos-art render --entry=path/to/dir --filter=regex , the optional arguments are from --filter=regex argument on. - Optional arguments are parsed using getopt command through the following base construction: - - Optional arguments provide support to command options inside centos-art.sh script. For instance, consider the Subversion (svn) command, where there are many options (e.g., , , , etc), and inside each option there are several modifiers (e.g., --revision, --message, --username, etc.) that can be combined one another in their short or long variants. - The ARGUMENTS variable is used to store arguments passed from command-line for later use inside centos-art.sh script. Storing arguments is specially useful when we want to run a command with some specific options from them. Consider the following command: - - In the above command, the , and options are specific to svn copy command. In such cases, options are not interpreted by centos-art.sh script itself. Instead, the centos-art.sh script uses getopt to retrive them and store them in the ARGUMENTS variable for later use, as described in the following command: - - When getopt parses ARGUMENTS, we may use short options (e.g., ) or long options (e.g., ). When we use short options, arguments are separated by one space from the option (e.g., ). When we use long options arguments are separated by an equal sign (=) (e.g., ). - In order for getopt to parse ARGUMENTS correctly, it is required to provide the short and long definition of options that will be passed or at least supported by the command performing the final action the function script exists for. - As convenction, inside centos-art.sh script, short option definitions are set in the ARGSS variable; and long option definitions are set in the ARGSL variable. - When you define short and long options, it may be needed to define which of these option arguments are required and which not. To define an option argument as required, you need to set one colon : after the option definition (e.g., ). On the other hand, to define an option argument as not required, you need to set two colons :: after the option definition (e.g., ). - - - - EDITOR - Variable - EDITOR - - - Default text editor. - The centos-art.sh script uses default text EDITOR to edit pre-commit subversion messages, translation files, configuration files, script files, and similar text-based files. - If EDITOR environment variable is not set, centos-art.sh script uses /usr/bin/vim as default text editor. Otherwise, the following values are recognized by centos-art.sh script: - - • - - /usr/bin/vim - - - /usr/bin/emacs - - - /usr/bin/nano - - - If no one of these values is set in EDITOR environment variable, centos-art.sh uses /usr/bin/vim text editor by default. - - - - - - Global functions - Function scripts stored directly under trunk/Scripts/Bash/Functions/ directory are used to define global functions. Global functions can be used inside action specific functionalities and or even be reused inside themselves. This section provides introductory information to global functions you can use inside centos-art.sh script. - - cli_checkActionArguments - Function - cli_checkActionArguments - - - Validate action value (ACTIONVAL) variable. - The action value variable can take one of the following values: - - - Path to one directory inside the local working copy, - - - Path to one file inside the local working copy, - - - If another value different from that specified above is passed to action value variable, the centos-art.sh script prints an error message and ends script execution. - - - - cli_checkFiles - Function - cli_checkFiles - FILE - [ - TYPE - ] - - - Verify file existence. - cli_checkFiles receives a FILE absolute path and performs file verification as specified in TYPE. When TYPE is not specified, cli_checkFiles verifies FILE existence, no matter what kind of file it be. If TYPE is specified, use one of the following values: - - - - - - Ends script execution if FILE is not a directory. - When you verify directories with cli_checkFiles, if directory doesn't exist, centos-art.sh script asks you for confirmation in order to create that directory. If you answer positively, centos-art.sh script creates that directory and continues script flows normally. Otherwise, if you answer negatively, centos-art.sh ends script execution with an error and documentation message. - - - - - - - Ends script execution if FILE is not a regular file. - - - - - - - Ends script execution if FILE is not a symbolic link. - - - - - - - Ends script execution if FILE is not executable. - - - - - - Ends script execution if FILE is neither a regular file nor a symbolic link. - - - - - - Ends script execution if FILE is neither a regular file nor a directory. - - - - - - Ends script execution if FILE is not inside the working copy. - - -
- As default behaviour, if FILE passes all verifications, centos-art.sh script continues with its normal flow. - - - - cli_commitRepoChanges - Function - cli_commitRepoChanges - [ - LOCATION - ] - - - Syncronize changes between repository and working copy. - The cli_commitRepoChanges function brings changes from the central repository down to the working copy—using svn update—, checks the working copy changes—using svn status command—, prints status report—using both svn update and svn status commands output, and finally, commits recent changes from the working copy up to the repository—using svn commit command—. - Previous to commit the working copy changes up to the central repository, the cli_commitRepoChanges function asks you to verify changes—using svn diff command—, and later, another confirmation question is shown to be sure you really want to commit changes up to central repository. - If LOCATION argument is not specified, the value of ACTIONVAL variable is used as reference instead. - - Figure - - Bringing changes from the repository into the working copy ---> Checking changes in the working copy ----------------------------------------------------------------------- -Added 0 file from the repository. -Deleted 0 file from the repository. -Updated 0 file from the repository. -Conflicted 0 file from the repository. -Merged 0 file from the repository. -Modified 4 files from the working copy. -Unversioned 0 file from the working copy. -Deleted 0 file from the working copy. -Added 0 file from the working copy. ----------------------------------------------------------------------- -]]> - The cli_commitRepoChanges function output. - - Call the cli_commitRepoChanges function before or/and after calling functions that modify files or directories inside the working copy as you may need to. - - - - cli_doParseArguments - Function - cli_doParseArguments - - - Redefine arguments (ARGUMENTS) global variable using getopt command output. For more information about how to use cli_doParseArguments function, see ARGUMENTS variable description above. - - - - cli_doParseArgumentsReDef - Function - cli_doParseArgumentsReDef - $ - @ - - - Initialize/reset arguments (ARGUMENTS) global variable using positional parameters variable ($@) as reference. - When we work inside function definitions, positional parameters are reset to the last function definition positional parameters. If you need to redefine positional parameters from one specific function, you need to call cli_doParseArgumentsReDef with the positional parameters variable ($@), set as first argument, to that specific function you want to redefine positional parameters at. - - - - cli_getArguments - Function - cli_getArguments - - - Initialize function name (FUNCNAM), action name (ACTIONNAM), and action value (ACTIONVAL) global variables, using positional parameters passed in $@ variable. - The cli_getArguments function is called from cli.sh function script, using cli function positional parameters (i.e., the positional parameters passed as arguments in the command-line) as first function argument. - Once command-line positional parameters are accesible to centos-art.sh script execution evironment, cli_getArguments uses regular expression to retrive action variables from first and second argument. The first argument defines the value used as function name (FUNCNAM), and the second argument defines both values used as action name (ACTIONNAM) and action value (ACTIONVAL), respectively. - The first argument is a word in lower case. This word specifies the name of the functionality you want to use (e.g., render to render images, manual to work on documentation, and so on.) - The second argument has a long option style (e.g., --option=value). The --option represents the action name (ACTIONNAM), and the characters inbetween the equal sign (=) and the first space character, are considered as the action value (ACTIONVAL). In order to provide action values with space characters inbetween you need to enclose action value with quotes like in --option='This is long value with spaces inbetween'. Generally, action values are used to specify paths over which the action name acts on. - Once action related variables (i.e., FUNCNAM, ACTIONNAM, and ACTIONVAL) are defined and validated, cli_getArguments shifts the positional arguments to remove the first two arguments passed (i.e., those used to retrive action related variables) and redefine the arguments (ARGUMENTS) global variable with the new positional parameters information. - - - - cli_getFunctions - Function - cli_getFunctions - - - Initialize funtionalities supported by centos-art.sh script. - Functionalities supported by centos-art.sh script are organized in functionality directories under trunk/Scripts/Bash/Functions/ directory. Each functionality directory stores function scripts to the functionality such directory was created for. Function scripts contain function definitions. Function definitions contain several commands focused on achieving one specific task only (i.e., the one such functionality was created for). - In order for centos-art.sh script to recognize a functionality, such functionality needs to be stored under trunk/Scripts/Bash/Functions/ in a directory written capitalized (i.e., the whole name is written in lowercase except the first character which is in uppercase). The directory where one specific functionality is stored is known as the functionality directory. - Inside each functionality directory, the functionalty itself is implemented through function scripts. Function scripts are organized in files independently one another and written in camelCase format with the function name as prefix. Separation between prefix and description is done using underscore (_) character. - In order for centos-art.sh script to load functionalities correctly, function definition inside function scripts should be set using the function reserved word, just as in the following example: - - The above function definition is just a convenction we use, in order to make identification of function names easier read and automate by centos-art.sh script initialization commands, once centos-art.sh script determines which functionality directory to use. Specifically, in order to initialize and export functions, centos-art.sh script executes all function scripts inside the functionality directory, and later grep on them using a regular expression pattern, where the function reserved word is used as reference to retrive the function names and export them to centos-art.sh script execution environment, and so, make function definitions —from function scripts inside the functionality directory— available for further calls. - If the functionality specified in the command-line first argument doesn't have a functionality directory, centos-art.sh script considers the functionality provided in the command-line as invalid functionality and immediatly stops script execution with an error message. - In order to keep visual consistency among function scripts, please consider using the following function script design model as template for your own function scripts: - - - - - cli_getCountryCodes - Function - cli_getCountryCodes - [ - FILTER - ] - - - Output country codes supported by centos-art.sh script. - The cli_getCountryCodes function outputs a list with country codes as defined in ISO3166 standard. When FILTER is provided, cli_getCountryCodes outputs country codes that match FILTER regular expression pattern. - - - - cli_getCountryName - Function - cli_getCountryName - [ - FILTER - ] - - - Outputs country name supported by centos-art.sh script. - The cli_getCountryName function reads one language locale code in the format LL_CC and outputs the name of its related country as in ISO3166. If filter is specified, cli_getCountryName returns the country name that matches the locale code specified in FILTER, exactly. - - - - cli_getCurrentLocale - Function - cli_getCurrentLocale - - - Output current locale used by centos-art.sh script. - The cli_getCurrentLocale function uses LANG environment variable to build a locale pattern that is later applied to cli_getLocales function output in order to return the current locale that centos-art.sh script works with. - The current locale information, returned by cli_getCurrentLocale, is output from more specific to less specific. For example, if en_GB locale exists in cli_getLocales function output, the en_GB locale would take precedence before en locale. - Locale precedence selection is quite important in order to define the locale type we use for message translations. For example, if en_GB is used, we are also saying that the common language specification for English language (i.e., en) is no longer used. Instead, we are using English non-common country-specific language specifications like en_AU, en_BW, en_GB, en_US, etc., for message translations. - Use cli_getCurrentLocale function to know what current locale information to use inside centos-art.sh script. - - - - cli_getFilesList - Function - cli_getFilesList - [ - LOCATION - ] - - - Output list of files to process. - The cli_getFilesList function uses LOCATION variable as source location to build a list of files just as specified by regular expression (REGEX) global variable. Essentially, what the cli_getFilesList function does is using find command to look for files in the location (LOCATION) just as posix-egrep regular expression (REGEX) specifies. - If LOCATION is not specified when cli_getFilesList function is called, the action value (ACTIONVAL) global variable is used as location value instead. - By default, if the regular expression (REGEX) global variable is not redefined after its first definition in the cli function, all files that match default regular expression value (i.e., .+) will be added to the list of files to process. Otherwise, if you redefine the regular expression global variable after its first definition in the cli function and before calling cli_getFilesList function, the last value you specifed is used instead. - When you need to customize the regular expression (REGEX) global variable value inside a function, do not redefine the global variable (at least you be absolutly convinced you need to). Instead, set the regular expression global variable as local to the function you need a customized regular expression value for. If we don't redefine the regular expression global variable as local to the function, or use another name for the regular expression variable (which is not very convenient in order to keep the amount of names to remember low), you may experiment undesired concantenation issues that make your regular expression to be something different from that you expect them to be, specially if the function where you are doing the variable redefinition is called several times during the same script execution. - As result, the cli_getFilesList re-defines the value of FILES variable with the list of files the find command returned. As example, consider the following construction: - - - - - cli_getLangCodes - Function - cli_getLangCodes - [ - FILTER - ] - - - Outputs language codes supported by centos-art.sh script. - cli_getLangCodes function outputs a list of language codes as defined in ISO639 standard. When FILTER is provided, cli_getLangCodes outputs language codes that match FILTER regular expression pattern. - - - - cli_getLangName - Function - cli_getLangName - [ - FILTER - ] - - - Outputs language names supported by centos-art.sh script. - cli_getLangName function reads one language locale code in the format LL_CC and outputs the language related name as in ISO639. If filter is specified, cli_getLangName returns the language name that matches the locale code specified in FILTER, exactly. - - - - cli_getLocales - Function - cli_getLocales - - - Output locale codes supported by centos-art.sh script. - Occasionally, you use cli_getLocales function to add locale information in non-common country-specific language (LL_CC) format for those languages (e.g., bn_IN, pt_BR, etc.) which locale differences cannot be solved using common language specifications (LL) into one unique common locale specification (e.g., bn, pt, etc.). - - - - cli_getRepoName - Function - cli_getRepoName - NAME - TYPE - - - Sanitate file names. - Inside centos-art.sh script, specific functionalities rely both in cli_getRepoName and repository file system organization to achieve their goals. Consider cli_getRepoName function as central place to manage file name convenctions for other functions inside centos-art.sh script. - - Important cli_getRepoName function doesn't verify file or directory existence, for that purpose use cli_checkFiles function instead. - - The NAME variable contains the file name or directory name you want to sanitate. - The TYPE variable specifies what type of sanitation you want to perform on NAME. The TYPE can be one of the following values: - - - - - - Sanitate directory NAMEs. - - - - - - - Sanitate regular file NAMEs. - - -
- Use cli_getRepoName function to sanitate file names and directory names before their utilization. - Use cli_getRepoName when you need to change file name convenctions inside centos-art.sh script. - When we change file name convenctions inside cli_getRepoName what we are really changing is the way functions interpret repository file system organization. Notice that when we change a file name (e.g., a function name), it is necessary to update all files where such file name is placed on. This may require a massive substitution inside the repository, each time we change name convenctions in the repository (— Removed(pxref:trunk Scripts Bash Functions Path) —, for more information). - - - - cli_getRepoStatus - Function - cli_getRepoStatus - [ - LOCATION - ] - - - Request repository status. - This function requests the status of a LOCATION inside the working copy using the svn status command and returns the first character in the output line, just as described in svn help status. If LOCATION is not a regular file or a directory, inside the working copy, the centos-art.sh script prints a message and ends its execution. - Use this function to perform verifications based a repository LOCATION status. - - - - cli_getTemporalFile - Function - cli_getTemporalFile - NAME - - - Output absolute path to temporal file NAME. - The cli_getTemporalFile function uses /tmp directory as source location to store temporal files, the centos-art.sh script name, and a random identification string to let you run more than one centos-art.sh script simultaneously on the same user session. For example, due the following temporal file defintion: - - If FILE name is instance.svg and the unique random string is f16f7b51-ac12-4b7f-9e66-72df847f12de, the final temporal file, built from previous temporal file definition, would be: - - When you use the cli_getTemporalFile function to create temporal files, be sure to remove temporal files created once you've ended up with them. For example, consider the following construction: - - Use the cli_getTemporalFile function whenever you need to create temporal files inside centos-art.sh script. - - - - cli_getThemeName - Function - cli_getThemeName - - - Output theme name. - In order for cli_getThemeName function to extract theme name correctly, the ACTIONVAL variable must contain a directory path under trunk/Identity/Themes/Motifs/ directory structure. Otherwise, cli_getThemeName returns an empty string. - - - - cli_printMessage - Function - cli_printMessage - MESSAGE - [ - FORMAT - ] - - - Define standard output message definition supported by centos-art.sh script. - When FORMAT is not specified, cli_printMessage outputs information just as it was passed in MESSAGE variable. Otherwise, FORMAT can take one of the following values: - - - - - To print heading messages. - - - - - - - To print warning messages. - - - - - - - To print note messages. - - - - - - - To print Updating messages on two-columns format. - - - - - - - To print Removing messages on two-columns format. - - - - - - - To print Checking messages on two-columns format. - - - - - - - To print Creating messages on two-columns format. - - - - - - - To print Saved as messages on two-columns format. - - - - - - - To print Linked to messages on two-columns format. - - - - - - - To print Moved to messages on two-columns format. - - - - - - - To print Translation messages on two-columns format. - - - - - - - To print Configuration messages on two-columns format. - - - - - - - To print response messages on one-column format. - $MESSAGE -]]> - - - - - - To print request messages on one-column format. Request messages output messages with one colon (:) and without trailing newline (\n) at message end. - - - - - - - To print yes or no request messages on one-column format. If something different from y is answered (when using en_US.UTF-8 locale), script execution ends immediatly. - - When we use centos-art.sh script in a locale different from en_US.UTF-8, confirmation answer may be different from y. For example, if you use es_ES.UTF-8 locale, the confirmation question would look like: - - and the confirmation answer would be s, as it is on Spanish sí word. - Definition of which confirmation word to use is set on translation messages for your specific locale information. — Removed(xref:trunk Scripts Bash Functions Locale) —, for more information about locale-specific translation messages. - - - - - - To standardize to know more, run the following command: messages. When the option is used, the MESSAGE value should be set to "$(caller)". caller is a Bash builtin that returns the context of the current subroutine call. option uses caller builtin output to build documentation entries dynamically. - - Use option after errors and for intentional script termination. - - - - - - To standardize regular messages on one-column format. - When MESSAGE contains a colon inside (e.g., description: message), the cli_printMessage function outputs MESSAGE on two-columns format. - - -
- Use cli_printMessage function whenever you need to output information from centos-art.sh script. - - Tip To improve two-columns format, change the following file: - - - - - - - - Specific functions - The following specific functions of centos-art.sh script, are available for you to use: - - - - - - - - - - - - - - - - See also - - - trunk Scripts Bash - trunk Scripts Bash - - - - - -
- - - trunk Scripts Bash Cli Functions Help - trunk Scripts Bash Cli Functions Html - trunk Scripts Bash Cli Functions - trunk -
- trunk/Scripts/Bash/Cli/Functions/Help - trunk Scripts Bash Cli Functions Help - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Scripts Bash Cli Functions Html - trunk Scripts Bash Cli Functions Locale - trunk Scripts Bash Cli Functions Help - trunk -
- trunk/Scripts/Bash/Cli/Functions/Html - trunk Scripts Bash Cli Functions Html - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Scripts Bash Cli Functions Locale - trunk Scripts Bash Cli Functions Manual - trunk Scripts Bash Cli Functions Html - trunk -
- trunk/Scripts/Bash/Cli/Functions/Locale - trunk Scripts Bash Cli Functions Locale - - Goals - - • - - ... - - - - - - 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 finishd PO file edition and quit text editor, the centos-art command creates the related machine object in the location $CLI_LANG/LC_MESSAGES/$TEXTDOMAIN.mo. - At this point, all translations you made in the PO file should be available to your language when runing centos-art.sh script. - In order to make the centos-art.sh internationalization, the centos-art.sh script was modified as described in the gettext info documentation (info gettext). You can find such modifications in the following files: - - • - - trunk/Scripts/Bash/initFunctions.sh - - - trunk/Scripts/Bash/Functions/Help/cli_localeMessages.sh - - - trunk/Scripts/Bash/Functions/Help/cli_localeMessagesStatus.sh - - - - • - - ... - - - - - - Usage - - - centos-art locale --edit - - Use this command to translate command-line interface output messages in the current system locale you are using (as specified in LANG environment variable). - - - - centos-art locale --list - - Use this command to see the command-line interface locale report. - - -
- - - - See also - - - -
- - - trunk Scripts Bash Cli Functions Manual - trunk Scripts Bash Cli Functions Path - trunk Scripts Bash Cli Functions Locale - trunk -
- trunk/Scripts/Bash/Cli/Functions/Manual - trunk Scripts Bash Cli Functions Manual - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - -
- - - trunk Scripts Bash Cli Functions Path - trunk Scripts Bash Cli Functions Render - trunk Scripts Bash Cli Functions Manual - trunk -
- trunk/Scripts/Bash/Cli/Functions/Path - trunk Scripts Bash Cli Functions Path - - Goals - This section exists to organize files related to path functiontionality. The path functionality standardizes movement, syncronization, branching, tagging, and general file maintainance inside the repository. - - - - Description - ”CentOS like trees, has roots, trunk, branches, leaves and flowers. Day by day they work together in freedom, ruled by the laws of nature and open standards, to show the beauty of its existence.” - - - Repository layout - The repository layout describes organization of files and directories inside the repository. The repository layout provides the standard backend required for automation scripts to work correctly. If such layout changes unexpectedly, automation scripts may confuse themselves and stop doing what we expect from them to do. - As convenction, inside CentOS Artwork Repository, we organize files and directories related to CentOS corporate visual identity under three top level directories named: trunk/, branches/, and tags/. - The trunk/ directory (see trunk) organizes the main development line of CentOS corporate visual identity. Inside trunk/ directory structure, the CentOS corporate visual identity concepts are implemented using directories. There is one directory level for each relevant concept inside the repository. The trunk/ directory structure is mainly used to perform development tasks related to CentOS corporate visual identity. - The branches/ directory (see branches) oranizes parallel development lines to trunk/ directory. The branches/ directory is used to set points in time where develpment lines are devided one from another taking separte and idependent lives that share a common past from the point they were devided on. The branches/ directory is mainly used to perform quality assurance tasks related to CentOS corporate visual identity. - The tags/ directory (see tags) organizes parallel frozen lines to branches/ directory. The parallel frozen lines are immutable, nothing change inside them once they has been created. The tags/ directory is mainly used to publish final releases of CentOS corporate visual identity. - The CentOS Artwork Repository layout is firmly grounded on a Subversion base. Subversion (http://subversion.tigris.org) is a version control system, which allows you to keep old versions of files and directories (usually source code), keep a log of who, when, and why changes occurred, etc., like CVS, RCS or SCCS. Subversion keeps a single copy of the master sources. This copy is called the source “repository”; it contains all the information to permit extracting previous versions of those files at any time. - - - - Repository name convenctions - Repository name convenctions help us to maintain consistency of names inside the repository. - Repository name convenctions are applied to files and directories inside the repository layout. As convenction, inside the repository layout, file names are all written in lowercase (01-welcome.png, splash.png, anaconda_header.png, etc.) and directory names are all written capitalized (e.g., Identity, Themes, Motifs, TreeFlower, etc.). - Repository name convenctions are implemented inside the cli_getRepoName function of centos-art.sh script. With cli_getRepoName function we reduce the amount of commands and convenctions to remember, concentrating them in just one single place to look for fixes and improvements. - - - - Repository work flow - Repository work flow describes the steps and time intervals used to produce CentOS corporate visual identity inside CentOS Artwork Repository. - To illustrate repository work flow let's consider themes' development cycle. - Initially, we start working themes on their trunk development line (e.g., trunk/Identity/Themes/Motifs/TreeFlower/), here we organize information that cannot be produced automatically (i.e., background images, concepts, color information, screenshots, etc.). - Later, when theme trunk development line is considered “ready” for implementation (e.g., all required backgrounds have been designed), we create a branch for it (e.g., branches/Identity/Themes/Motifs/TreeFlower/1/). Once the branch has been created, we forget that branch and continue working the trunk development line while others (e.g., an artwork quality assurance team) test the new branch for tunning it up. - Once the branch has been tunned up, and considered “ready” for release, it is freezed under tags/ directory (e.g., tags/Identity/Themes/Motifs/TreeFower/1.0/) for packagers, webmasters, promoters, and anyone who needs images from that CentOS theme the tag was created for. - Both branches and tags, inside CentOS Artwork Repository, use numerical values to identify themselves under the same location. Branches start at one (i.e., 1) and increment one unit for each branch created from the same trunk development line. Tags start at zero (i.e., 0) and increment one unit for each tag created from the same branch development line. - - Convenction Do not freeze trunk development lines using tags directly. If you think you need to freeze a trunk development line, create a branch for it and then freeze that branch instead. - - The trunk development line may introduce problems we cannot see immediatly. Certainly, the high changable nature of trunk development line complicates finding and fixing such problems. On the other hand, the branched development lines provide a more predictable area where only fixes/corrections to current content are commited up to repository. - If others find and fix bugs inside the branched development line, we could merge such changes/experiences back to trunk development line (not visversa) in order for future branches, created from trunk, to benefit. - Time intervals used to create branches and tags may vary, just as different needs may arrive. For example, consider the release schema of CentOS distribution: one major release every 2 years, security updates every 6 months, support for 7 years long. Each time a CentOS distribution is released, specially if it is a major release, there is a theme need in order to cover CentOS distribution artwork requirements. At this point, is where CentOS Artwork Repository comes up to scene. - Before releasing a new major release of CentOS distribution we create a branch for one of several theme development lines available inside the CentOS Artwork Repository, perform quality assurance on it, and later, freeze that branch using tags. Once a the theme branch has been frozen (under tags/ directory), CentOS Packagers (the persons whom build CentOS distribution) can use that frozen branch as source location to fulfill CentOS distribution artwork needs. The same applies to CentOS Webmasters (the persons whom build CentOS websites), and any other visual manifestation required by the project. - - - - Parallel directories - Inside CentOS Artwork Repository, parallel directories are simple directory entries built from a common parent directory and placed in a location different to that, the common parent directory is placed on. Parallel directories are useful to create branches, tags, translations, documentation, pre-rendering configuration script, and similar directory structures. - Parallel directories take their structure from one unique parent directory. Inside CentOS Artwork Repository, this unique parent directory is under trunk/Identity location. The trunk/Identity location must be considered the reference for whatever information you plan to create inside the repository. - In some circumstances, parallel directories may be created removing uncommon information from their paths. Uncommon path information refers to those directory levels in the path which are not common for other parallel directories. For example, when rendering trunk/Identity/Themes/Motifs/TreeFlower/Distro directory structure, the centos-art.sh script removes the Motifs/TreeFlower/ directory levels from path, in order to build the parallel directory used to retrived translations, and pre-rendering configuration scripts required by render functionality. - Another example of parallel directory is the documentation structure created by manual functionality. This time, centos-art.sh script uses parallel directory information with uncommon directory levels to build the documentation entry required by Texinfo documentation system, inside the repository. - Othertimes, parallel directories may add uncommon information to their paths. This is the case we use to create branches and tags. When we create branches and tags, a numerical identifier is added to parallel directory structure path. The place where the numerical identifier is set on is relevant to corporate visual identity structure and should be carefully considered where it will be. - When one parent directory changes, all their related parallel directories need to be changed too. This is required in order for parallel directories to retain their relation with the parent directory structure. In the other hand, parallel directories should never be modified under no reason but to satisfy the relation to their parent directory structure. Liberal change of parallel directories may suppresses the conceptual idea they were initially created for; and certainly, things may stop working the way they should do. - - - - Syncronizing path information - Parallel directories are very useful to keep repository organized but introduce some complications. For instance, consider what would happen to functionalities like manual (trunk Scripts Bash Functions Manual) that rely on parent directory structures to create documentation entries (using parallel directory structures) if one of those parent directory structures suddenly changes after the documentation entry has been already created for it? - In such cases, functionalities like manual may confuse themselves if path information is not updated to reflect the relation with its parent directory. Such functionalities work with parent directory structure as reference; if a parent directory changes, the functionalities dont't even note it because they work with the last parent directory structure available in the repository, no matter what it is. - In the specific case of documentation (the manual functionality), the problem mentioned above provokes that older parent directories, already documented, remain inside documentation directory structures as long as you get your hands into the documentation directory structure (trunk/Manuals) and change what must be changed to match the new parent directory structure. - There is no immediate way for manual, and similar functionalities that use parent directories as reference, to know when and how directory movements take place inside the repository. Such information is available only when the file movement itself takes place inside the repository. So, is there, at the moment of moving files, when we need to syncronize parallel directories with their unique parent directory structure. - - Warning There is not support for URL reference inside centos-art.sh script. The centos-art.sh script is designed to work with local files inside the working copy only. - - As CentOS Artwork Repository is built over a version control system, file movements inside the repository are considered repository changes. In order for these repository changes to be versioned, we need to, firstly, add changes into the version control system, commit them, and later, perform movement actions using version control system commands. This configuration makes possible for everyone to know about changes details inside the repository; and if needed, revert or update them back to a previous revision. - Finally, once all path information has been corrected, it is time to take care of information inside the files. For instance, considere what would happen if you make a reference to a documentation node, and later the documentation node you refere to is deleted. That would make Texinfo to produce error messages at export time. So, the centos-art.sh script needs to know when such changes happen, in a way they could be noted and handled without producing errors. - - - - What is the right place to store it? - Occasionly, you may find that new corporate visual identity components need to be added to the repository. If that is your case, the first question you need to ask yourself, before start to create directories blindly all over, is: What is the right place to store it? - The CentOS Community different free support vains (see: http://wiki.centos.org/GettingHelp) are the best place to find answers to your question, but going there with hands empty is not good idea. It may give the impression you don't really care about. Instead, consider the following suggestions to find your own comprehension and so, make your propositions based on it. - When we are looking for the correct place to store new files, to bear in mind the corporate visual identity structure used inside the CentOS Artwork Repository (see trunk Identity) would be probaly the best advice we could offer, the rest is just matter of choosing appropriate names. To illustrate this desition process let's consider the trunk/Identity/Themes/Motifs/TreeFlower directory as example. It is the trunk development line of TreeFlower artistic motif. Artistic motifs are considered part of themes, which in turn are considered part of CentOS corporate visual identity. - When building parent directory structures, you may find that reaching an acceptable location may take some time, and as it uses to happen most of time; once you've find it, that may be not a definite solution. There are many concepts that you need to play with, in order to find a result that match the conceptual idea you try to implement in the new directory location. To know which these concepts are, split the location in words and read its documentation entry from less specific to more specific. - For example, the trunk/Identity/Themes/Motifs/TreeFlower location evolved through several months of contant work and there is no certain it won't change in the future, even it fixes quite well the concept we are trying to implement. The concepts used in trunk/Identity/Themes/Distro/Motifs/TreeFlower location are described in the following commands, respectively: - - Other location concepts can be found similary as we did above, just change the location we used above by the one you are trying to know concepts for. - - - - - Usage - - - centos-art path --copy='SRC' --to='DST' - - Copy to and schedule for addition (with history). In this command, SRC and DST are both working copy (WC) entries. - - - - centos-art path --delete='SRC' - - Delete . In order for this command to work the file or directory you intend to delete should be under version control first. In this command, SRC is a working copy (WC) entry. - - -
- - - - See also - - - trunk Scripts Bash - trunk Scripts Bash - - - - - -
- - - trunk Scripts Bash Cli Functions Render - trunk Scripts Bash Cli Functions Render Config - trunk Scripts Bash Cli Functions Path - trunk -
- trunk/Scripts/Bash/Cli/Functions/Render - trunk Scripts Bash Cli Functions RenderThe render functionality exists to produce both identity and translation files on different levels of information (i.e., different languages, release numbers, architectures, etc.). - The render functionality relies on “renderable directory structures” to produce files. Renderable directory structures can be either “identity directory structures” or “translation directory structures” with special directories inside. - - - Renderable identity directory structures - Renderable identity directory structures are the starting point of identity rendition. Whenever we want to render a component of CentOS corporate visual identity, we need to point centos-art.sh to a renderable identity directory structure. If such renderable identity directory structure doesn't exist, then it is good time to create it. - Inside the working copy, one renderable identity directory structures represents one visual manifestation of CentOS corporate visual identity, or said differently, each visual manifestation of CentOS corporate visual identity should have one renderable identity directory structure. - Inside renderable identity directory structures, centos-art.sh can render both image-based and text-based files. Specification of whether a renderable identity directory structure produces image-based or text-based content is a configuration action that takes place in the pre-rendition configuration script of that renderable identity directory structure. - Inside renderable identity directory structures, content production is organized in different configurations. A content production configuration is a unique combination of the components that make an identity directory structure renderable. One content production configuration does one thing only (e.g., to produce untranslated images), but it can be extended (e.g., adding translation files) to achieve different needs (e.g., to produce translated images). - - - Design template without translation - The design template without translation configuration is based on a renderable identity directory structure with an empty translation directory structure. In this configuration, one design template produces one untranslated file. Both design templates and final untranslated files share the same file name, but they differ one another in file-type and file-extension. - For example, to produce images without translations (there is no much use in producing text-based files without translations), consider the following configuration: - - - One renderable identity directory structure: - - In this example we used Identity/Path/To/Dir as the identity component we want to produce untranslated images for. Identity components can be either under trunk/ or branches/ directory structure. - The identity component (i.e., Identity/Path/To/Dir, in this case) is also the bond component we use to connect the identity directory structures with their respective auxiliar directories (i.e., translation directory structres and pre-rendition configuration structures). The bond component is the path convenction that centos-art.sh uses to know where to look for related translations, configuration scripts and whatever auxiliar thing a renderable directory structure may need to have. - | -trunk/Identity/Path/To/Dir <-- Renderable identity directory structure. -|-- Tpl <-- Design template directory. -| `-- file.svg <-- Design template file. -`-- Img <-- Directory used to store final files. - `-- file.png <-- Final image-based file produced from - design template file. -]]> - Inside design template directory, design template files are based on SVGScalable Vector Graphics and use the extension .svg. Design template files can be organized using several directory levels to create a simple but extensible configuration, specially if translated images are not required. - In order for SVGScalable Vector Graphics files to be considered “design template” files, they should be placed under the design template directory and to have set a CENTOSARTWORK object id inside. - The CENTOSARTWORK word itself is a convenction name we use to define which object/design area, inside a design template, the centos-art.sh script will use to export as PNGPortable Network Graphic image at rendition time. Whithout such object id specification, the centos-art.sh script cannot know what object/design area you (as designer) want to export as PNGPortable Network Graphic image file. - - Note At rendition time, the content of Img/ directory structure is produced by centos-art.sh automatically. - - When a renderable identity directory structure is configured to produce image-based content, centos-art.sh produces PNGPortable Network Graphics files with the .png extension. Once the base image format has been produced, it is possible for centos-art.sh to use it in order to automatically create other image formats that may be needed (— Removed(pxref:trunk Scripts Bash Functions Render Config) —). - Inside the working copy, you can find an example of “design template without translation” configuration at trunk/Identity/Models/. - See trunk Identity, for more information. - - - - One translation directory structure: - - In order for an identity entry to be considered an identity renderable directory structure, it should have a translation entry. The content of the translation entry is relevant to determine how to process the identity renderable directory entry. - If the translation entry is empty (i.e., there is no file inside it), centos-art.sh interprets the identity renderable directory structure as a “design templates without translation” configuration. - | -trunk/Translations/Identity/Path/To/Dir -`-- (empty) -]]> - If the translation entry is not empty, centos-art.sh can interpret the identity renderable directory structure as one of the following configurations: “design template with translation (one-to-one)” or “design template with translation (optimized)”. Which one of these configurations is used depends on the value assigned to the matching list (MATCHINGLIST) variable in the pre-rendition configuration script of the renderable identity directory structure we are producing images for. - If the matching list variable is empty (as it is by default), then “design template with translation (one-to-one)” configuration is used. In this configuration it is required that both design templates and translation files have the same file names. This way, one translation files is applied to one design template, to produce one translated image. - If the matching list variable is not empty (because you redefine it in the pre-rendition configuration script), then “design template with translation (optimized)” configuration is used instead. In this configuration, design templates and translation files don't need to have the same names since such name relationship between them is specified in the matching list properly. - — Removed(xref:trunk Translations) —, for more information. - - - - One pre-rendition configuration script: - - In order to make an identity directory structure renderable, a pre-rendition configuration script should exist for it. The pre-rendition configuration script specifies what type of rendition does centos-art.sh will perform over the identity directory structure and how does it do that. - | -trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir -`-- render.conf.sh -]]> - In this configuration the pre-rendition configuration script (render.conf.sh) would look like the following: - - Since translation directory structure is empty, centos-art.sh assumes a “design template without translation” configuration to produce untranslated images. - To produce untranslated images, centos-art.sh takes one design template and creates one temporal instance from it. Later, centos-art.sh uses the temporal design template instance as source file to export the final untranslated image. The action of exporting images from SVGScalable Vector Graphics to PNGPortable Network Graphics is possible thanks to Inkscape's command-line interface and the CENTOSARTWORK object id we previously set inside design templates. - - Finally, when the untranslated image has been created, the temporal design template instance is removed. At this point, centos-art.sh takes the next design template and repeats the whole production flow once again (design template by design template), until all design templates be processed. - — Removed(xref:trunk Scripts Bash Functions Render Config) —, for more information. - - -
- - - - Design template with translation (one-to-one) - Producing untranslated images is fine in many cases, but not always. Sometimes it is required to produce images in different languages and that is something that untrasnlated image production cannot achieve. However, if we fill its empty translation entry with translation files (one for each design template) we extend the production flow from untranslated image production to translated image production. - In order for centos-art.sh to produce images correctly, each design template should have one translation file and each translation file should have one design template. Otherwise, if there is a missing design template or a missing translation file, centos-art.sh will not produce the final image related to the missing component. - In order for centos-art.sh to know which is the relation between translation files and design templates the translation directory structure is taken as reference. For example, the trunk/Translations/Identity/Path/To/Dir/file.sed translation file does match trunk/Identity/Path/To/Dir/Tpl/file.svg design template, but it doesn't match trunk/Identity/Path/To/Dir/File.svg or trunk/Identity/Path/To/Dir/Tpl/File.svg or trunk/Identity/Path/To/Dir/Tpl/SubDir/file.svg design templates. - The pre-rendition configuration script used to produce untranslated images is the same we use to produce translated images. There is no need to modify it. So, as we are using the same pre-rendition configuration script, we can say that translated image production is somehow an extended/improved version of untranslated image production. - - Note If we use no translation file in the translation entry (i.e., an empty directory), centos-art.sh assumes the untranslated image production. If we fill the translation entry with translation files, centos-art.sh assumes the translated image production. - - To produce final images, centos-art.sh applies one translation file to one design template and produce a translated design template instance. Later, centos-art.sh uses the translated template instance to produce the translated image. Finally, when the translated image has been produced, centos-art.sh removes the translated design template instance. This production flow is repeated for each translation file available in the translatio entry. - - - - - Design template with translation (optimized) - Producing translated images satisfies almost all our production images needs, but there is still a pitfall in them. In order to produce translated images as in the “one-to-one” configuration describes previously, it is required that one translation file has one design template. That's useful in many cases, but what would happen if we need to apply many different translation files to the same design template? Should we have to duplicate the same design template file for each translation file, in order to satisfy the “one-to-one” relation? What if we need to assign translation files to design templates arbitrarily? - Certenly, that's something the “one-to-one” configuration cannot handle. So, that's why we had to “optimize” it. The optimized configuration consists on using a matching list (MATCHINGLIST) variable that specifies the relationship between translation files and design templates in an arbitrary way. Using such matching list between translation files and design templates let us use as many assignment combinations as translation files and design templates we are working with. - The MATCHINGLIST variable is set in the pre-rendition configuration script of the component we want to produce images for. By default, the MATCHINGLIST variable is empty which means no matching list is used. Otherwise, if MATCHINGLIST variable has a value different to empty value then, centos-art.sh interprets the matching list in order to know how translation files are applied to design templates. - For example, consider the following configuration: - - - One entry under trunk/Identity/: - - In this configuration we want to produce three images using a paragraph-based style, controlled by paragraph.svg design template; and one image using a list-based style, controlled by list.svg design template. - - - - - One entry under trunk/Translations/: - - In order to produce translated images we need to have one translation file for each translated image we want to produce. Notice how translation names do match final image file names, but how translation names do not match design template names. When we use matching list there is no need for translation files to match the names of design templates, such name relation is set inside the matching list itself. - - - - - One entry under trunk/trunk/Scripts/Bash/Functions/Render/Config/: - - In order to produce different translated images using specific design templates, we need to specify the relation between translation files and design templates in a way that centos-art.sh could know exactly what translation file to apply to what design template. This relation between translation files and design templates is set using the matching list MATCHINGLIST variable inside the pre-rendition configuration script of the component we want to produce images for. - - In this configuration the pre-rendition configuration script (render.conf.sh) would look like the following: - - As result, centos-art.sh will produce 01-welcome.png, 02-donate.png and 04-support.png using the paragraph-based design template, but 03-docs.png using the list-based design template. - - -
- - - - Design template with translation (optimized+flexibility) - In the production models we've seen so far, there are design templates to produce untranslated images and translation files which combiend with design templates produce translated images. That may seems like all our needs are covered, doesn't it? Well, it almost does. - Generally, we use design templates to define how final images will look like. Generally, each renderable directory structure has one Tpl/ directory where we organize design templates for that identity component. So, we can say that there is only one unique design template definition for each identity component; or what is the same, said differently, identity components can be produced in one way only, the way its own design template directory specifies. This is not enough for theme production. It is a limitation, indeed. - Initially, to create one theme, we created one renderable directory structure for each theme component. When we found ourselves with many themes, and components inside them, it was obvious that the same design model was duplicated inside each theme. As design models were independently one another, if we changed one theme's design model, that change was useless to other themes. So, in order to reuse design model changes, we unified design models into one common directory structure. - With design models unified in a common structure, another problem rose up. As design models also had the visual style of theme components, there was no difference between themes, so there was no apparent need to have an independent theme directory structure for each different theme. So, it was also needed to separate visual styles from design models. - At this point there are two independent worklines: one directory structure to store design models (the final image characteristics [i.e., dimensions, translation markers, etc.]) and one directory structure to store visual styles (the final image visual style [i.e., the image look and feel]). So, it is possible to handle both different design models and different visual styles independtly one another and later create combinations among them using centos-art.sh. - For example, consider the following configuration: - - - One entry under trunk/Identity/Themes/Models/: - - The design model entry exists to organize design model files (similar to design templates). Both design models and design templates are very similar; they both should have the CENTOSARTWORK export id present to identify the exportation area, translation marks, etc. However, design models do use dynamic backgrounds inclusion while design templates don't. - | -trunk/Identity/Themes/Models/Default/Distro/Anaconda/Progress/ -|-- paragraph.svg -`-- list.svg -]]> - Inisde design models, dynamic backgrounds are required in order for different artistic motifs to reuse common design models. Firstly, in order to create dynamic backgrounds inside design models, we import a bitmap to cover design model's background and later, update design model's path information to replace fixed values to dynamic values. - - - - One entry under trunk/Identity/Themes/Motifs/: - - The artistic motif entry defines the visual style we want to produce images for, only. Final images (i.e., those built from combining both design models and artistic motif backrounds) are not stored here, but under branches directory structure. In the artistic motif entry, we only define those images that cannot be produced automatically by centos-art.sh (e.g., Backgrounds, Color information, Screenshots, etc.). - | -trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/ -|-- Img -| |-- Png -| | |-- 510x300.png -| | `-- 510x300-final.png -| `-- Jpg -| |-- 510x300.jpg -| `-- 510x300-final.jpg -|-- Tpl -| `-- 510x300.svg -`-- Xcf - `-- 510x300.xcf -]]> - - - - One entry under trunk/Translations/: - - The translation entry specifies, by means of translation files, the language-specific information we want to produce image for. When we create the translation entry we don't use the name of neither design model nor artistic motif, just the design model component we want to produce images for. - | -trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ -`-- 5 - |-- en - | |-- 01-welcome.sed - | |-- 02-donate.sed - | `-- 03-docs.sed - `-- es - |-- 01-welcome.sed - |-- 02-donate.sed - `-- 03-docs.sed -]]> - - - - One entry under trunk/Scripts/Bash/Functions/Render/Config/: - - There is one pre-rendition configuration script for each theme component. So, each time a theme component is rendered, its pre-rendition configuration script is evaluated to teach centos-art.sh how to render the component. - - In this configuration the pre-rendition configuration script (render.conf.sh) would look like the following: - - - -
- The production flow of “optimize+flexibility” configuration&dots; - - - - - Renderable translation directory structures - Translation directory structures are auxiliar structures of renderable identity directory structures. There is one translation directory structure for each renderable identity directory structure. Inside translation directory structures we organize translation files used by renderable identity directory structures that produce translated images. Renderable identity directory structures that produce untranslated images don't use translation files, but they do use a translation directory structure, an empty translation directory structure, to be precise. - In order to aliviate production of translation file, we made translation directory structures renderable adding a template (Tpl/) directory structure to handle common content inside translation files. This way, we work on translation templates and later use centos-art.sh to produce specific translation files (based on translation templates) for different information (e.g., languages, release numbers, architectures, etc.). - If for some reason, translation files get far from translation templates and translation templates become incovenient to produce such translation files then, care should be taken to avoid replacing the content of translation files with the content of translation templates when centos-art.sh is executed to produce translation files from translation templates. - Inside renderable translation directory structures, centos-art.sh can produce text-based files only. - - - - Copying renderable directory structures - A renderable layout is formed by design models, design images, pre-rendition configuration scripts and translations files. This way, when we say to duplicate rendition stuff we are saying to duplicate these four directory structures (i.e., design models, design images, pre-rendition configuration scripts, and related translations files). - When we duplicate directories, inside `trunk/Identity' directory structure, we need to be aware of renderable layout described above and the source location used to perform the duplication action. The source location is relevant to centos-art.sh script in order to determine the required auxiliar information inside directory structures that need to be copied too (otherwise we may end up with orphan directory structures unable to be rendered, due the absence of required information). - In order for a renderable directory structure to be valid, the new directory structure copied should match the following conditions: - - - To have a unique directory structure under trunk/Identity, organized by any one of the above organizational designs above. - - - To have a unique directory structure under trunk/Translations to store translation files. - - - To have a unique directory structure under trunk/Scripts/Bash/Functions/Render/Config to set pre-rendition configuration script. - - - As convenction, the render_doCopy function uses trunk/Identity directory structure as source location. Once the trunk/Identity directory structure has been specified and verified, the related path information is built from it and copied automatically to the new location specified by FLAG_TO variable. - Design templates + No translation: - Command: - centos-art render –copy=trunk/Identity/Path/To/Dir –to=trunk/Identity/NewPath/To/Dir - Sources: - trunk/Identity/Path/To/Dir - trunk/Translations/Identity/Path/To/Dir - trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir - Targets: - trunk/Identity/NewPath/To/Dir - trunk/Translations/Identity/NewPath/To/Dir - trunk/Scripts/Bash/Functions/Render/Config/Identity/NewPath/To/Dir - Renderable layout 2: - Command: - centos-art render –copy=trunk/Identity/Themes/Motifs/TreeFlower \ –to=trunk/Identity/Themes/Motifs/NewPath/To/Dir - Sources: - trunk/Identity/Themes/Motifs/TreeFlower - trunk/Translations/Identity/Themes - trunk/Translations/Identity/Themes/Motifs/TreeFlower - trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes - trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/TreeFlower - Targets: - trunk/Identity/Themes/Motifs/NewPath/To/Dir - trunk/Translations/Identity/Themes - trunk/Translations/Identity/Themes/Motifs/NewPath/To/Dir - trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes - trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewPath/To/Dir - Notice that design models are not included in source or target locations. This is intentional. In “Renderable layout 2”, design models live by their own, they just exist, they are there, available for any artistic motif to use. By default `Themes/Models/Default' design model directory structure is used, but other design models directory structures (under Themes/Models/) can be created and used changing the value of THEMEMODEL variable inside the pre-rendition configuration script of the artistic motif source location you want to produce. - Notice how translations and pre-rendition configuration scripts may both be equal in source and target. This is because such structures are common to all artistic motifs (the default values to use when no specific values are provided). - - The common directory structures are not copied or deleted. We cannot copy a directory structure to itself. - - The common directory structures represent the default value to use when no specific translations and/or pre-rendition configuration script are provided inside source location. - - The specific directory structures, if present, are both copiable and removable. This is, when you perform a copy or delete action from source, that source specific auxiliar directories are transfered in the copy action to a new location (that specified by FLAG_TO variable). - - When translations and/or pre-rendition configuration scripts are found inside the source directory structure, the centos-art.sh script loads common auxiliar directories first and later specific auxiliar directories. This way, identity rendition of source locations can be customized idividually over the base of common default values. - - The specific auxiliar directories are optional. - - The common auxiliar directories should be present always. This is, in order to provide the information required by render functionality (i.e., to make it functional in the more basic level of its existence). - Notice how the duplication process is done from `trunk/Identity' on, not the oposite. If you try to duplicate a translation structure (or similar auxiliar directory structures like pre-rendition configuration scripts), the `trunk/Identity' for that translation is not created. This limitation is impossed by the fact that many `trunk/Identity' directory structures may reuse/share the same translation directory structure. We cannot delete one translation (or similar) directory structures while a related `trunk/Identity/' directory structure is still in need of it. - The `render_doCopy' functionality does duplicate directory structures directly involved in rendition process only. Once such directories have been duplicated, the functionality stops thereat. - - - - Usage - - • - - ... - - - - - - See also - - - - -
- - - trunk Scripts Bash Cli Functions Render Config - trunk Scripts Bash Cli Functions Shell - trunk Scripts Bash Cli Functions Render - trunk -
- trunk/Scripts/Bash/Cli/Functions/Render/Config - trunk Scripts Bash Cli Functions Render Config - - Goals - The trunk/Scripts/Bash/Config directory exists to oraganize pre-rendering configuration scripts. - - - - Description - Pre-rendering configuration scripts let you customize the way centos-art.sh script renders identity and translation repository entries. Pre-rendering configuration scripts are render.conf.sh files with render_loadConfig function definition inside. - There is one render.conf.sh file for each pre-rendering configuration entry. Pre-rendering configuration entries can be based both on identity and translation repository entires. Pre-rendering configuration entries are required for each identity entry, but not for translation entries. - - - The <file>render.conf.sh</file> 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: - - Inside identity pre-rendering configuration scripts, text-based pre-rendering configuration scripts look like the following: - - 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. - - - - The <file>render.conf.sh</file> translation model - Translation pre-rendering configuration scripts take precedence before default translation rendering action. Translation pre-rendering actions are useful when default translation rendering action do not fit itself to translation entry rendering requirements. - - - - The <file>render.conf.sh</file> rendering actions - Inside both image-based and text-based identity pre-rendering configuration scripts, we use the ACTIONS array variable to define the way centos-art.sh script performs identity rendering. Identity rendering is organized by one BASE action, and optional POST and LAST rendering actions. - The BASE action specifies what kind of rendering does the centos-art.sh script will perform with the files related to the pre-rendering configuration script. The BASE action is required. Possible values to BASE action are either renderImage or renderText only. - To specify the BASE action you need to set the BASE: string followed by one of the possible values. For example, if you want to render images, consider the following definition of BASE action: - - 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: - - 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: - - 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. - - Note — Removed(xref: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: - - - - - - Usage - Use the following commands to administer both identity and translation pre-rendering configuration scripts: - - - centos-art config --create='path/to/dir/' - - Use this command to create path/to/dir related pre-rendering configuration script. - - - - centos-art config --edit='path/to/dir/' - - Use this command to edit path/to/dir related pre-rendering configuration script. - - - - centos-art config --read='path/to/dir/' - - Use this command to read path/to/dir related pre-rendering configuration script. - - - - centos-art config --remove='path/to/dir/' - - 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. - - - - See also - - - trunk Scripts Bash - trunk Scripts Bash - - - - - - -
- - - trunk Scripts Bash Cli Functions Shell - trunk Scripts Bash Cli Functions Svg - trunk Scripts Bash Cli Functions Render Config - trunk -
- trunk/Scripts/Bash/Cli/Functions/Shell - trunk Scripts Bash Cli Functions Shell - - Goals - This section exists to organize files related to shell functionality of centos-art.sh script. - - - - Description - The shell functionality of centos-art.sh script helps you to maintain bash scripts inside repository. For example, suppose you've created many functionalities for centos-art.sh script, and you want to use a common copyright and license note for consistency in all your script files. If you have a bunch of files, doing this one by one wouldn't be a big deal. In contrast, if the amount of files grows, updating the copyright and license note for all of them would be a task rather tedious. The shell functionality exists to solve maintainance tasks just as the one previously mentioned. - When you use shell functionality to update copyright inside script files, it is required that your script files contain (at least) the following top commentary structure: - - Figure - - - The functions script base comment structure - - Relevant lines in the above structure are lines from 5 to 9. Everything else in the file is left immutable. - When you are updating copyright through shell functionality, the centos-art.sh script replaces everything in-between line 5 —the first one matching ^# Copyright .+$ string— and line 9—the first long dash separator matching ^# -+$— with the content of copyright template instance. - - Caution Be sure to add the long dash separator that matches ^# -+$ regular expression before the function definition. Otherwise, if the Copyright line is present but no long dash separator exists, centos-art.sh will remove anything in-between the Copyright line and the end of file. This way you may lost your function definitions entirely. - - The copyright template instance is created from one copyright template stored in the Config/tpl_forCopyright.sed file. The template instance is created once, and later removed when no longer needed. At this moment, when template instance is created, the centos-art.sh script takes advantage of automation in order to set copyright full name and date dynamically. - When you use shell functionality to update copyright, the first thing shell functionality does is requesting copyright information to user, and later, if values were left empty (i.e., no value was typed before pressing RET key), the shell functionality uses its own default values. - When shell functionality uses its own default values, the final copyright note looks like the following: - - Figure - - - The function script comment example - - Relevant lines in the above structure are lines from 5 to 22. Pay attention how the copyright line was built, and how the license was added into the top comment where previously was just three dots. Everything else in the file was left immutable. - To change copyright information (i.e., full name or year information), run the shell functionality over the root directory containing the script files you want to update copyright in and enter the appropriate information when it be requested. You can run the shell functionality as many times as you need to. - To change copyright license (i.e., the text in-between lines 7 and 20), you need to edit the Config/tpl_forCopyright.sed file, set the appropriate information, and run the shell functionality once again for changes to take effect over the files you specify. - - Important The centos-art.sh script is released as: - - Do not change the license information under which centos-art.sh script is released. Instead, if you think a different license must be used, please share your reasons at centos-devel@centos-art.shCentOS Developers mailing list. - - - - - Usage - - - centos-art sh --update-copyright='path/to/dir' - centos-art sh --update-copyright='path/to/dir' --filter='regex' - - Use these commands to update copyright information in .sh files under path/to/dir directory. - - -
- When you provide argument, the list of files to process is reduced as specified in regex regular expression. Inside centos-art.sh script, the regex regular expression is used in combination with find command to look for files matching the regular expression path pattern. - - Warning In order for regex regular expression to match a file, the regex regular expresion must match the whole file path not just the file name. - - For example, if you want to match all render.conf.sh files inside path/to/dir, use the .+/render.conf regular expression. Later, centos-art.sh script uses this value inside ^$REGEX\.sh$ expression in order to build the final regular expression (i.e., ^.+/render.conf\.sh$) that is evaluated against available file paths inside the list of files to process. - Exceptionally, when you provide in the way that regex, appended to path/to/dir/ (i.e. path/to/dir/regex), matches a regular file; the centos-art.sh script uses the file matching as only file in the list of files to process. - - - - See also - - - trunk Scripts Bash - trunk Scripts Bash - - - - - -
- - - trunk Scripts Bash Cli Functions Svg - trunk Scripts Bash Cli Functions Verify - trunk Scripts Bash Cli Functions Shell - trunk -
- trunk/Scripts/Bash/Cli/Functions/Svg - trunk Scripts Bash Cli Functions Svg - - Goals - This section exists to organize files related to svg functionality of centos-art.sh script. - - - - Description - The svg functionality of centos-art.sh script helps you to maintain scalable vector graphics (SVG) inside repository. For example, suppose you've been working in CentOS default design models under trunk/Identity/Themes/Models/, and you want to set common metadata to all of them, and later remove all unused SVG defintions from *.svg files. Doing so file by file may be a tedious task, so the centos-art.sh script provides the svg functionality to aid you maintain such actions. - Metadata maintainance - - Metadata maintainance - The metadata used is defined by Inkscape 0.46 using the SVG standard markup. The centos-art.sh script replaces everything in-between <metadata and </metadata> tags with a predefined metadata template we've set for this purpose. - The metadata template was created using the metadata information of a file which, using Inkscape 0.46, all metadata fields were set. This created a complete markup representation of how SVG metadata would look like. Later, we replaced every single static value with a translation marker in the form =SOMETEXT=, where SOMETEXT is the name of its main opening tag. Later, we transform the metadata template into a sed replacement set of commads escaping new lines at the end of each line. - With metadata template in place, the centos-art.sh script uses it to create a metadata template instance for the file being processed currently. The metadata template instance contains the metadata portion of sed replacement commands with translation markers already traduced. In this action, instance creation, is where we take advantage of automation and generate metadata values like title, date, keywords, source, identifier, and relation dynamically, based on the file path centos-art.sh script is currently creating metadata information for. - With metadata template instance in place, the centos-art.sh script uses it to replace real values inside all .svg files under the current location you're running the centos-art.sh script on. Default behaviour is to ask user to enter each metadatum required, one by one. If user leaves metadatum empty, by pressing RET key, centos-art.sh uses its default value. - The centos-art.sh script modifies the following metadata: - - - Title - - Name by which this document is formally known. If no value is set here, centos-art.sh script uses the file name as title. - - - - Date - - Date associated with the creation of this document (YYYY-MM-DD). If no value is set here, centos-art.sh script uses the current date information as in date +%Y-%m-%d. - - - - Creator - - Name of entity primarily responsible for making the content of this document. If no value is set here, centos-art.sh script uses the string The CentOS Project. - - - - Rights - - Name of entity with rights to the intellectual Property of this document. If no value is set here, centos-art.sh script uses the string The CentOS Project. - - - - Publisher - - Name of entity responsible for making this document available. If no value is set here, centos-art.sh script uses the string The CentOS Project. - - - - Identifier - - Unique URI to reference this document. If no value is set here, centos-art.sh script uses the current file path to build the related url that points to current file location inside repository central server. - - - - Source - - Unique URI to reference the source of this document. If no value is set here, centos-art.sh script uses current file path to build the related url that points to current file location inside repository central server. - - - - Relation - - Unique URI to a related document. If no value is set here, centos-art.sh script uses current file path to build the related url that points to current file location inside repository central server. - - - - Language - - Two-letter language tag with optional subtags for the language of this document. (e.g. en-GB). If no value is set here, centos-art.sh script uses the current locale information as in cli_getCurrentLocale function. - - - - Keywords - - The topic of this document as comma-separated key words, prhases, or classifications. If no value is set here, centos-art.sh script uses file path to build - - - - Coverage - - Extent or scope of this document. If no value is set here, centos-art.sh script uses the string The CentOS Project. - - - - Description - - Description about the document. If no value is set here, centos-art.sh script uses uses empty value as default. - - - - Contributors - - People that contributes in the creation/maintainance of the document. If no value is set here, centos-art.sh script uses uses empty value as default. - - -
- The License metadatum is not set as a choise, by now. It is fixed http://creativecommons.org/licenses/by-sa/3.0/Creative Common Attribution Share-Alike 3.0 License. This is done in order to grant license consistency among all SVG files we manage inside CentOS Artwork Repository. - Unused definitions - - - - Unused definitions - Many of the no-longer-used gradients, patterns, and markers (more precisely, those which you edited manually) remain in the corresponding palettes and can be reused for new objects. However if you want to optimize your document, use the Vacuum Defs command in File menu. It will remove any gradients, patterns, or markers which are not used by anything in the document, making the file smaller. - If you have one or two couple of files, removing unused definitions using the graphical interface may be enough to you. In contrast, if you have dozens or even houndreds of scalable vector graphics files to maintain it is not a fun task to use the graphical interface to remove unused definitions editing those files one by one. - To remove unused definitions from several scalable vector graphics files, the centos-art.sh script uses Inkscape command-line interface, specifically with the option. - - - - - Usage - - - centos-art svg --update-metadata='path/to/dir' - centos-art svg --update-metadata='path/to/dir' --filter='regex' - - Use these commands to update metadata information to .svg files under path/to/dir directory. - - - - centos-art svg --vacuum-defs='path/to/dir' - centos-art svg --vacuum-defs='path/to/dir' --filter='regex' - - Use these commands to remove unused definitions inside .svg files under path/to/dir directory. - - -
- When you provide argument, the list of files to process is reduced as specified in regex regular expression. Inside centos-art.sh script, the regex regular expression is used in combination with find command to look for files matching the regular expression path pattern. - - Warning In order for regex regular expression to match a file, the regex regular expresion must match the whole file path not just the file name. - - For example, if you want to match all summary.svg files inside path/to/dir, use the .+/summary regular expression. Later, centos-art.sh script uses this value inside ^$REGEX\.svg$ expression in order to build the final regular expression (i.e., ^.+/summary\.svg$) that is evaluated against available file paths inside the list of files to process. - Exceptionally, when you provide in the way that regex, appended to path/to/dir/ (i.e. path/to/dir/regex), matches a regular file; the centos-art.sh script uses the file matching as only file in the list of files to process. - - - - See also - - - trunk Scripts Bash - trunk Scripts Bash - - - - - -
- - - trunk Scripts Bash Cli Functions Verify - trunk Scripts Python - trunk Scripts Bash Cli Functions Svg - trunk -
- trunk/Scripts/Bash/Cli/Functions/Verify - trunk Scripts Bash Cli Functions Verify - - Goals - This section exists to organize files related to centos-art.sh script verify functionality. The verify functionality of centos-art.sh script helps you to verify the workstation configuration you are planning to use as host for your working copy of CentOS Artwork Repository. - - - - Description - The first time you download CentOS Artwork Repository you need to configure your workstation in order to use centos-art.sh script. These preliminar configurations are based mainly on auxiliar RPM packages installation, symbolic links creations, and environment variables definitions. The verify functionality of centos-art.sh script guides you through this preliminar configuration process. - If this is the first time you run centos-art.sh script, the appropriate way to use its verify functionality is not using the centos-art.sh script directly, but the absolute path to centos-art.sh script instead (i.e., ~/artwork/trunk/Scripts/Bash/centos-art.sh). This is necessary because centos-art symbolic link, under ~/bin/ directory, has not been created yet. - - - Packages - Installation of auxiliar RPM packages provides the software required to manipulate files inside the repository (e.g., image files, documentation files, translation files, script files, etc.). Most of RPM packages centos-art.sh script uses are shipped with CentOS distribution, and can be installed from CentOS base repository. The only exception is inkscape, the package we use to manipulate SVG files. The inkscape package is not inside CentOS distribution so it needs to be installed from third party repositories. - - Note Configuration of third party repositories inside CentOS distribution is described in CentOS wiki, specifically in the following URL: http://wiki.centos.org/AdditionalResources/Repositories - - Before installing packages, the centos-art.sh script uses sudo to request root privileges to execute yum installation functionality. If your user isn't defined as a privileged user—at least to run yum commands— inside /etc/sudoers configuration file, you will not be able to perform package installation tasks as set in centos-art.sh script verify functionality. - Setting sudo privileges to users is an administrative task you have to do by yourself. If you don't have experience with sudo command, please read its man page running the command: man sudo. This reading will be very useful, and with some practice, you will be able to configure your users to have sudo privileges. - - - - Links - Creation of symbolic links helps us to alternate between different implementations of centos-art.sh script-line (e.g., centos-art.sh, for Bash implementation; centos-art.py, for Python implementation; centos-art.pl, for Perl implementation; and so on for other implementations). The centos-art.sh script-line definition takes place inside your personal binary (~/bin/) directory in order to make the script implementation —the one that centos-art links to— available to PATH environment variable. - Creation of symbolic links helps us to reuse components from repository working copy. For example, color information files maintained inside your working copy must never be duplicated inside program-specific configuration directories that uses them in your workstation (e.g., Gimp, Inkscape, etc.). Instead, a symbolic link must be created for each one of them, from program-specific configuration directories to files in the working copy. In this configuration, when someone commits changes to color information files up to central repository, they—the changes committed— will be immediatly available to your programs the next time you update your working copy —the place inside your workstation those color information files are stored—. - Creation of symbolic links helps us to make centos-art.sh script functionalities available outside trunk/ repository directory structure, but at its same level in repository tree. This is useful if you need to use the “render” functionality of centos-art.sh under branches/ repository directory structure as you usually do inside trunk/ repository directory structure. As consequence of this configuration, automation scripts cannot be branched under branches/Scripts directory structure. - - - - Environment variables - Definition of environemnt variables helps us to set default values to our user session life. The user session environment variable defintion takes place in the user's ~/.bash_profile file. The verify functionality of centos-art.sh script doesn't modify your ~/.bash_profile file. - The verify functionality of centos-art.sh script evaluates the following environment variables: - - - EDITOR - - Default text editor. - The centos-art.sh script uses default text EDITOR to edit pre-commit subversion messages, translation files, configuration files, script files, and similar text-based files. - If EDITOR environment variable is not set, centos-art.sh script uses /usr/bin/vim as default text editor. Otherwise, the following values are recognized by centos-art.sh script: - - • - - /usr/bin/vim - - - /usr/bin/emacs - - - /usr/bin/nano - - - If no one of these values is set in EDITOR environment variable, centos-art.sh uses /usr/bin/vim text editor by default. - - - - TEXTDOMAIN - - Default domain used to retrieve translated messages. This variable is set in initFunctions.sh and shouldn't be changed. - - - - TEXTDOMAINDIR - - Default directory used to retrieve translated messages. This variable is set in initFunctions.sh and shouldn't be changed. - - - - LANG - - Default locale information. - This variable is initially set in the configuration process of CentOS distribution installer (i.e., Anaconda), specifically in the Language step; or once installed using the system-config-language tool. - The centos-art.sh script uses the LANG environment variable to know in which language the script messages are printed out. - - - - TZ - - Default time zone representation. - This variable is initially set in the configuration process of CentOS distribution installer (i.e., Anaconda), specifically in the Date and time step; or once installed using the system-config-date tool. - The centos-art.sh script doesn't use the TZ environment variable information at all. Instead, this variable is used by the system shell to show the time information according to your phisical location on planet Earth. - Inside your computer, the time information is firstly set in the BIOS clock (which may need correction), and later in the configuration process of CentOS distribution installer (or later, by any of the related configuration tools inside CentOS distribution). Generally, setting time information is a straight-forward task and configuration tools available do cover most relevant location. However, if you need a time precision not provided by the configuration tools available inside CentOS distribution then, using TZ variable may be necessary. - - Convenction In order to keep changes syncronized between central repository and its working copies: configure both repository server and workstations (i.e., the place where each working copy is set on) to use Coordinated Universal Time (UTC) as base time representation. Later, correct the time information for your specific location using time zone correction. - - The format of TZ environment variable is described in tzset(3) manual page. - - -
- - - - - Usage - - - centos-art verify --packages - - Verify required packages your workstation needs in order to run the centos-art.sh script correctly. If there are missing packages, the centos-art.sh script asks you to confirm their installation. When installing packages, the centos-art.sh script uses the yum application in order to achieve the task. - In case all packages required by centos-art.sh script are already installed in your workstation, the message The required packages are already installed. is output for you to know. - - - - centos-art verify --links - - Verify required links your workstation needs in order to run the centos-art command correctly. If any required link is missing, the centos-art.sh script asks you to confirm their installation. To install required links, the centos-art.sh script uses the ln command. - In case all links required by centos-art.sh script are already created in your workstation, the message The required links are already installed. is output for you to know. - In case a regular file exists with the same name of a required link, the centos-art.sh script outputs the Already exists as regular file. message when listing required links that will be installed. Of course, as there is already a regular file where must be a link, no link is created. In such cases the centos-art.sh script will fall into a continue installation request for that missing link. To end this continue request you can answer No, or remove the existent regular file to let centos-art.sh script install the link on its place. - - - - centos-art verify --environment - centos-art verify --environment --filter='regex' - - Output a brief description of environment variables used by centos-art.sh script. - If --filter option is provided, output is reduced as defined in the regex regular expression value. If --filter option is specified but regex value is not, the centos-art.sh script outputs information as if --filter option had not been provided at all. - - -
- - - - See also - - - trunk Scripts Bash - trunk Scripts Bash - - - - - -
- - - trunk Scripts Python - trunk Scripts Bash Cli Functions Verify - trunk -
- trunk/Scripts/Python - trunk Scripts Python - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - - -
- - - Index - List of Figures - trunk - Top - - Index - cp - - - - List of Figures - Index - Top - - List of Figures - - - - - diff --git a/Manuals/Filesystem/tags/chapter-intro.texi b/Manuals/Filesystem/tags/chapter-intro.texi deleted file mode 100644 index e69de29..0000000 --- a/Manuals/Filesystem/tags/chapter-intro.texi +++ /dev/null diff --git a/Manuals/Filesystem/tags/chapter-menu.texi b/Manuals/Filesystem/tags/chapter-menu.texi deleted file mode 100644 index 8b13789..0000000 --- a/Manuals/Filesystem/tags/chapter-menu.texi +++ /dev/null @@ -1 +0,0 @@ - diff --git a/Manuals/Filesystem/tags/chapter-nodes.texi b/Manuals/Filesystem/tags/chapter-nodes.texi deleted file mode 100644 index 8b13789..0000000 --- a/Manuals/Filesystem/tags/chapter-nodes.texi +++ /dev/null @@ -1 +0,0 @@ - diff --git a/Manuals/Filesystem/tags/chapter.texi b/Manuals/Filesystem/tags/chapter.texi deleted file mode 100644 index 2b05ba0..0000000 --- a/Manuals/Filesystem/tags/chapter.texi +++ /dev/null @@ -1,6 +0,0 @@ -@node tags -@chapter tags -@cindex tags -@include tags/chapter-intro.texi -@include tags/chapter-menu.texi -@include tags/chapter-nodes.texi diff --git a/Manuals/Filesystem/trunk/Identity.texi b/Manuals/Filesystem/trunk/Identity.texi deleted file mode 100644 index 65f22ca..0000000 --- a/Manuals/Filesystem/trunk/Identity.texi +++ /dev/null @@ -1,126 +0,0 @@ -@subsection Goals - -The @file{trunk/Identity} directory exists to organize CentOS -corporate identity artworks. - -@subsection Description - -The CentOS Project corporate identity is the ``persona'' of the -organization known as The CentOS Project. The CentOS Project -corporate identity plays a significant role in the way the CentOS -Project, as organization, presents itself to both internal and -external stakeholders. In general terms, the CentOS Project corporate -visual identity expresses the values and ambitions of the CentOS -Project organization, its business, and its characteristics. - -The CentOS Project corporate identity provides visibility, -recognizability, reputation, structure and identification to the -CentOS Project organization by means of corporate design, corporate -communication, and corporate behaviour. - -The CentOS Project settles down its corporate visual identity on a -``monolithic corporate visual identity structure''. In this structure -The CentOS Project uses one unique name (The CentOS Brand) and one -unique visual style (The CentOS Default Theme) in all its -manifestations. - -@table @strong - -@item The CentOS Brands -The CentOS brand is the name or trademark that conncects the producer -with their products. In this case, the producer is The CentOS Project -and the products are the CentOS distributions, the CentOS web sites, -the CentOS promotion stuff, etc. - -@xref{trunk Identity Brands}, for more information. - -@item The CentOS Themes - -The CentOS themes are a set of image files connected all together by -one unique visual style. Each theme is organized in different visual -manifestations, in order to cover each visual manifestation of The -CentOS Project (i.e., distributions, websites, promotion stuff, etc.). -@xref{trunk Identity Themes}, for more information. -@end table - -Inside a monolithic corporate visual identity structure, internal and -external stakeholders use to feel a strong sensation of uniformity, -orientation, and identification with the organization. No matter if -you are visiting websites, using the distribution, or acting on social -events, the one unique name and one unique visual style conect them -all to say: Hey! we are all parts of the CentOS project. And, -probably, some vister will say: Can I join the party? Yes you can, it -is free. :) - -@subsection Usage - -To produce identity artworks, use the following commands: - -@table @samp -@item centos-art render 'path/to/dir' - -When @samp{path/to/dir} refers to one renderable directory under -@file{trunk/Identity}, this command renders identity artworks using -both related design models and related translation files. - -@item centos-art render 'path/to/dir' --filter='pattern' - -When @samp{path/to/dir} refers to one renderable directory under -@file{trunk/Identity}, this command renders identity artworks using -both related design models and related translation files that match -the regular expression passed in @samp{--filter='pattern'} argument. - -To control the number of files produced by @command{centos-art} -command, you need to look into the translation path and provide a -regular expression pattern that matches the translation path, or -paths, related to the file, or files, you want to produce. - -The regular expression pattern you provide to @command{centos-art} -command is applied to the translation path from its very beginning. -It is not the same to say @samp{5/en/01-welcome} that -@samp{01-welcome}, the frist expression matches but the last one does -not. - -When using @samp{--filter='pattern'} you don't need to specify the -file extension. It is removed from translation path before applying -the pattern, so it doesn't count here. -@end table - -@subsection File name convenctions - -As file name convenction, inside CentOS Artwork Repository, both -text-based and image-based file name produced by @command{centos-art.sh} -script has the same name of their translation files without -the @samp{.sed} extension. The file extension is set as follow: - -@subsubsection When text-based files are rendered - -Text-based files end up having the same extension of their design -template file. - -@subsubsection When image-based files are rendered - -Image-based files always end up having the @file{.png} extension. - -@quotation -@strong{Tip} Once @file{.png} images are created, other image formats -may be created using the @command{renderFormats} post-rendering -action, inside the image-based related pre-rendering configuration -script. - -@xref{trunk Scripts Bash}, for more information. -@end quotation - -@subsection See also - -@menu -@comment --- Removed(* trunk Translations::) --- -@end menu - -@subsection References - -@itemize -@item @url{http://en.wikipedia.org/Corporate_identity} (and related -links). -@end itemize - diff --git a/Manuals/Filesystem/trunk/Identity/Brands.texi b/Manuals/Filesystem/trunk/Identity/Brands.texi deleted file mode 100644 index 9cf9a6e..0000000 --- a/Manuals/Filesystem/trunk/Identity/Brands.texi +++ /dev/null @@ -1,14 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@subsection Usage - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Fonts.texi b/Manuals/Filesystem/trunk/Identity/Fonts.texi deleted file mode 100644 index ef6730a..0000000 --- a/Manuals/Filesystem/trunk/Identity/Fonts.texi +++ /dev/null @@ -1,79 +0,0 @@ -@subsection Goals - -This section exists to organize digital typographies used by the -CentOS project. - -@subsection Description - -@subsection Usage - -The CentOS corporate identity is attached to @samp{DejaVu LGC} -font-family. Whatever artwork you design for CentOS project, that -requires typography usage, must be done using @samp{DejaVu LGC} -font-family. - -@table @strong -@item Recommendation-1: - -For screen desings (e.g., anything that final destination will never -be printed on paper or any medium outside computer screens) use -@samp{DejaVu LGC Sans} font-family. - -@item Recommendation-2: - -For non-screen designs (e.g., anything that final desition will be -printed on paper or any other medium outside computer screens) use -@samp{DejaVu LGC Serif} font-family. As convenction files described in -this rule are stored under @samp{Stationery} directories. -@end table - -The only execption for the two recommendations above is the typography -used inside CentOS logo. The CentOS logo is the main visual -representation of the CentOS project so the typography used in it must -be the same always, no matter where it be shown. It also has to be -clear enough to dismiss any confussion between similar typefaces -(e.g., the number one (1) sometimes is confuesed with the letter -@samp{el} (l) or letter @samp{ai} (i)). - -As CentOS logo typography convenction, the word @samp{CentOS} uses -@samp{Denmark} typography as base, both for the word @samp{CentOS} and -the phrase @samp{Community Enterprise Operating System}. The phrase -size of CentOS logo is half the size in poits the word @samp{CentOS} -has and it below @samp{CentOS} word and aligned with it on the left. -The distance between @samp{CentOS} word and phrase @samp{Community -Enterprise Operating System} have the size in points the phrase has. - -When the CentOS release brand is built, use @samp{Denmark} typography -for the release number. The release number size is two times larger -(in height) than default @samp{CentOS} word. The separation between -release number and @samp{CentOS} word is twice the size in points of -separation between @samp{CentOS} word and phrase @samp{Community -Enterprise Operating System}. - -Another component inside CentOS logo is the trademark symbol (TM). -This symbol specifies that the CentOS logo must be consider a product -brand, even it is not a registered one. The trademark symbol uses -DejaVu LGC Sans Regular typography. The trademark symbol is aligned -right-top on the outter side of @samp{CentOS} word. The trademark -symbol must not exceed haf the distance, in points, between -@samp{CentOS} word and the release number on its right. - -It would be very convenient for the CentOS Project and its community -to to make a registered trademark (®) of CentOS logo. To make a -register trademark of CentOS Logo prevents legal complications in the -market place of brands. It grants the consistency, through time, of -CentOS project corporate visual identity. - -@quotation -@strong{Note} The information about trademarks and corporate identity -is my personal interpretation of -@url{http://en.wikipedia.org/Corporate_identity} and -@url{http://en.wikipedia.org/Trademark} description. If you have -practical experiences with these affairs, please serve yourself to -improve this section with your reasons. -@end quotation - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Icons.texi b/Manuals/Filesystem/trunk/Identity/Icons.texi deleted file mode 100644 index 9cf9a6e..0000000 --- a/Manuals/Filesystem/trunk/Identity/Icons.texi +++ /dev/null @@ -1,14 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@subsection Usage - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Isolinux.texi b/Manuals/Filesystem/trunk/Identity/Isolinux.texi deleted file mode 100644 index 9cf9a6e..0000000 --- a/Manuals/Filesystem/trunk/Identity/Isolinux.texi +++ /dev/null @@ -1,14 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@subsection Usage - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Models.texi b/Manuals/Filesystem/trunk/Identity/Models.texi deleted file mode 100644 index 3973252..0000000 --- a/Manuals/Filesystem/trunk/Identity/Models.texi +++ /dev/null @@ -1,19 +0,0 @@ -@subsection Goals - -This section exists to organize design models. - -@subsection Description - -Design models are representative designs useful to understand how -to build artworks. - -@subsection Usage - -@subsection See also - -@menu -* trunk Identity Models Html:: -* trunk Identity Models Css:: -* trunk Identity Models Tpl:: -* trunk Identity Models Xcf:: -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Models/Css.texi b/Manuals/Filesystem/trunk/Identity/Models/Css.texi deleted file mode 100644 index 5639459..0000000 --- a/Manuals/Filesystem/trunk/Identity/Models/Css.texi +++ /dev/null @@ -1,21 +0,0 @@ -@subsection Goals - -This directory exists to provide common style sheets (CSS) definitions -to HTML design models. - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Models/Html.texi b/Manuals/Filesystem/trunk/Identity/Models/Html.texi deleted file mode 100644 index fb39647..0000000 --- a/Manuals/Filesystem/trunk/Identity/Models/Html.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Models/Img/Promo/Web.texi b/Manuals/Filesystem/trunk/Identity/Models/Img/Promo/Web.texi deleted file mode 100644 index ec9b88b..0000000 --- a/Manuals/Filesystem/trunk/Identity/Models/Img/Promo/Web.texi +++ /dev/null @@ -1,23 +0,0 @@ -@subsection Goals - -@itemize -@item Provide images related to CentOS web interface. -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -* trunk Identity Models Tpl Promo Web:: -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Models/Tpl.texi b/Manuals/Filesystem/trunk/Identity/Models/Tpl.texi deleted file mode 100644 index fb39647..0000000 --- a/Manuals/Filesystem/trunk/Identity/Models/Tpl.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Models/Tpl/Promo/Web.texi b/Manuals/Filesystem/trunk/Identity/Models/Tpl/Promo/Web.texi deleted file mode 100644 index 56b7f37..0000000 --- a/Manuals/Filesystem/trunk/Identity/Models/Tpl/Promo/Web.texi +++ /dev/null @@ -1,329 +0,0 @@ -@subsection Goals - -Organize scalable vector graphics (svg) to help describe the CentOS -web environment. - -@subsection 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: - -@itemize -@item One unique name and one unique visual style to all web -applications used inside the web environment. - -@item One-step navigation to web applications inside the environment. - -@item High degree of customization to change the visual style of all -web applications with few changes (e.g, updating just two or three -images plus common style sheet [CSS] definitions). -@end itemize - -The CentOS project is attached to a monolithic corporate visual -identity (@pxref{trunk Identity}), where all visual manifestations -have one unique name and one unique visual style. This way, the CentOS -web environment has one unique name (the CentOS brand) and one unique -visual style (the CentOS default theme) for all its visual -manifestations, the web applications in this case. - -Since a maintainance point of view, achiving the one unique visual -style inside CentOS web environment is not a simple task. The CentOS -web environment is built upon many different web applications which -have different visual styles and different internal ways to customize -their own visual styles. For example: MoinMoin, the web application -used to support the CentOS wiki (@url{http://wiki.centos.org/}) is -highly customizable but Mailman (in its 2.x.x serie), the web -application used to support the CentOS mailing list, doesn't -support@footnote{The theme support of Mailman may be introduced in -mailman-3.x.x release.} a customization system that separates -presentation from logic, similar to that used by MoinMoin. - -This visual style diversity complicates our goal of one unique visual -style for all web applications. So, if we want one unique visual style -for all web applications used, it is innevitable to modify the web -applications in order to implement the CentOS one unique visual style -customization in them. Direct modification of upstream applications is -not convenient because upstream applications come with their one -visual style and administrators take the risk of loosing all -customization changes the next time the application be updated (since -not all upstream web applications, used in CentOS web environment, -separate presentation from logic). - -To solve the ``one unique visual style'' issue, installation and -actualization of web applications ---used inside CentOS web -environment--- need to be independent from upstream web applications -development line; in a way that CentOS web environment administrators -can install and update web applications freely without risk of loosing -the one unique visual style customization changes. - -At the surface of this issue we can see the need of one specific yum -repository to store CentOS web environment customized web applications. - -@subsubsection Design model (without ads) - -@subsubsection Design model (with ads) - -@subsubsection HTML definitions - -@subsubsection Controlling visual style - -Inside CentOS web environment, the visual style is controlled by the -following compenents: - -@table @strong -@item Webenv header background -@verbatim -trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Img/1024x250.png -@end verbatim - -@item CSS definitions -@verbatim -trunk/Identity/Themes/Models/Default/Promo/Web/CSS/stylesheet.css -@end verbatim -@end table - -@subsubsection Producing visual style - -The visual style of CentOS web environment is defined in the following -files: - -@verbatim -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 -@end verbatim - -As graphic designer you use @file{1024x250.xcf} file to produce -@file{1024x250-bg.png} file. Later, inside @file{1024x250.svg} file, -you use the @file{1024x250-bg.png} file as background layer to draw -your vectorial design. When you consider you artwork ready, use the -@command{centos-art.sh} script, as described below, to produce the -visual style controller images of CentOS web environment. - -@verbatim -centos-art render --entry=trunk/Identity/Themes/Motifs/$THEME/Backgrounds --filter='1024x250' -@end verbatim - -Once you have rendered required image files, changing the visual style -of CentOS web environment is a matter of replacing old image files -with new ones, inside webenv repository file system structure. The -visual style changes will take effect the next time customization line -of CentOS web applications be packaged, uploded, and installed from -[webenv] or [webenv-test] repositories. - -@subsubsection 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. - -@subsubsection Development and release cycle - -The CentOS web environment development and relase cycle is described -below: - -@table @strong - -@item Download - -The first action is download the source code of web applications we -want to use inside CentOS web environment. - -@quotation -@strong{Important} The source location from which web application are -downloaded is very important. Use SRPMs from CentOS @strong{[base]} -and @strong{[updates]} repositories as first choise, and third party -repositories (e.g. RPMForge, EPEL, etc.) as last resource. -@end quotation - -@item Prepare - -Once web application source code has been downloaded, our duty is -organize its files inside @samp{webenv} version controlled repository. - -When preparing the structure keep in mind that different web -applications have different visual styles, and also different ways to -implement it. A convenient way to organize the file system structure -would be create one development line for each web application we use -inside CentOS web environment. For example, consider the following -file system structure: - -@verbatim -https://projects.centos.org/svn/webenv/trunk/ -|-- WebApp1/ -| |-- Sources/ -| | `-- webapp1-0.0.1/ -| |-- Rpms/ -| | `-- webapp1-0.0.1.rpm -| |-- Srpms/ -| | `-- webapp1-0.0.1.srpm -| `-- Specs/ -| `-- webapp1-0.0.1.spec -|-- WebApp2/ -`-- WebAppN/ -@end verbatim - -@item Customize - -Once web applications have been organized inside the version -controlled repository file system, use subversion to create the CentOS -customization development line of web applications source code. For -example, using the above file system structure, you can create the -customization development line of @file{webapp1-0.0.1/} with the -following command: - -@verbatim -svn cp trunk/WebApp1/Sources/webapp1-0.0.1 trunk/WebApp1/Sources/webapp1-0.0.1-webenv -@end verbatim - -The command above creates the following structure: - -@verbatim -https://projects.centos.org/svn/webenv/trunk/ -|-- WebApp1/ -| |-- Sources/ -| | |-- webapp1-0.0.1/ -| | `-- webapp1-0.0.1-webenv/ -| |-- Rpms/ -| | `-- webapp1-0.0.1.rpm -| |-- Srpms/ -| | `-- webapp1-0.0.1.srpm -| `-- Specs/ -| `-- webapp1-0.0.1.spec -|-- WebApp2/ -`-- WebAppN/ -@end verbatim - -In the above structure, the @file{webapp1-0.0.1-webenv/} directory is -the place where you customize the visual style of -@file{webapp1-0.0.1/} web application. - -@quotation -@strong{Tip} Use the @command{diff} command of Subversion between -CentOS customization and upstream development lines to know what you -are changing exactly. -@end quotation - -@item Build packages - -When web application has been customized, build the web application -RPM and SRPM using the source location with @samp{-webenv} prefix. - -@verbatim -https://projects.centos.org/svn/webenv/trunk/ -|-- WebApp1/ -| |-- Sources/ -| | |-- webapp1-0.0.1/ -| | `-- webapp1-0.0.1-webenv/ -| |-- Rpms/ -| | |-- webapp1-0.0.1.rpm -| | `-- webapp1-0.0.1-webenv.rpm -| |-- Srpms/ -| | |-- webapp1-0.0.1.srpm -| | `-- webapp1-0.0.1-webenv.srpm -| `-- Specs/ -| |-- webapp1-0.0.1.spec -| `-- webapp1-0.0.1-webenv.spec -|-- WebApp2/ -`-- WebAppN/ -@end verbatim - -@item Release for testing - -When the customized web application has been packaged, make packages -available for testing and quality assurance. This can be achives using -a [webenv-test] yum repository. - -@quotation -@strong{Note} The [webenv-test] repository is not shipped inside -CentOS distribution default yum configuraiton. In order to use -[webenv-test] repository you need to configure it first. -@end quotation - -If some problem is found to install/update/use the customized version -of web application, the problem is notified somewhere (a bugtracker -maybe) and the customization face is repated in order to fix the -problem. To release the new package add a number after @samp{-webenv} -prefix. For example, if some problem is found in -@file{webapp1-0.0.1-webenv.rpm}, when it be fixed the new package will -be named @file{webapp1-0.0.1-webenv-1.rpm}. If a problem is found in -@file{webapp1-0.0.1-webenv-1.rpm}, when it be fixed the new package -will be named @file{webapp1-0.0.1-webenv-2.rpm}, and so on. - -The ``customization --- release for testing'' process is repeated -until CentOS quality assurance team considers the package is ready for -production. - -@item Release for production - -When customized web application packages are considered ready for -production they are moved from [webenv-test] to [webenv] repository. -This action is commited by CentOS quality assurance team. - -@quotation -@strong{Note} The [webenv] repository is not shipped inside CentOS -distribution default yum configuraiton. In order to use [webenv] -repository you need to configure it first. -@end quotation -@end table - -@subsubsection The [webenv-test] repository - -@verbatim -/etc/yum.repos.d/CentOS-Webenv-test.repo -@end verbatim - -@verbatim -[webenv-test] -name=CentOS-$releasever - Webenv-test -mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv-test -#baseurl=http://mirror.centos.org/centos/$releasever/webenv-test/$basearch/ -gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever -enabled=1 -priority=10 -@end verbatim - -@subsubsection The [webenv] repository - -@verbatim -/etc/yum.repos.d/CentOS-Webenv.repo -@end verbatim - -@verbatim -[webenv] -name=CentOS-$releasever - Webenv -mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv -#baseurl=http://mirror.centos.org/centos/$releasever/webenv/$basearch/ -gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever -enabled=1 -priority=10 -@end verbatim - -@subsubsection Priority configuration - -Both [webenv] and [webenv-test] repositories update packages inside -CentOS [base] and CentOS [updates] repositories. - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -* trunk Identity Models Img Promo Web:: -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Models/Xcf.texi b/Manuals/Filesystem/trunk/Identity/Models/Xcf.texi deleted file mode 100644 index fb39647..0000000 --- a/Manuals/Filesystem/trunk/Identity/Models/Xcf.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Release.texi b/Manuals/Filesystem/trunk/Identity/Release.texi deleted file mode 100644 index 9cf9a6e..0000000 --- a/Manuals/Filesystem/trunk/Identity/Release.texi +++ /dev/null @@ -1,14 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@subsection Usage - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes.texi b/Manuals/Filesystem/trunk/Identity/Themes.texi deleted file mode 100644 index 01a20c1..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes.texi +++ /dev/null @@ -1,26 +0,0 @@ -@subsection Goals - -The @file{trunk/Identity/Themes/} directory exists to organize -production of CentOS themes. - -@subsection Description - -@subsection 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. - -@menu -* trunk Identity Themes Models:: -* trunk Identity Themes Motifs:: -@end menu - -@subsection See also - -@menu -* trunk Identity:: -* trunk:: -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Models.texi b/Manuals/Filesystem/trunk/Identity/Themes/Models.texi deleted file mode 100644 index b91973a..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Models.texi +++ /dev/null @@ -1,30 +0,0 @@ -@subsection Goals - -@itemize -@item Organize theme models. -@end itemize - -@subsection 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. - -@subsection 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 `@xref{trunk Identity -Themes Models Default, Default},' and `@xref{trunk Identity Themes -Models Alternative, Alternative},' ready-to-use theme models. - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Models/Alternative.texi b/Manuals/Filesystem/trunk/Identity/Themes/Models/Alternative.texi deleted file mode 100644 index 483226a..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Models/Alternative.texi +++ /dev/null @@ -1,26 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection 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. - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Models/Default.texi b/Manuals/Filesystem/trunk/Identity/Themes/Models/Default.texi deleted file mode 100644 index 6ce9103..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Models/Default.texi +++ /dev/null @@ -1,27 +0,0 @@ -@subsection Goals - -This location stores CentOS default theme model. The default theme -model of CentOS is used in all visual manifestations of CentOS Project -corporate visual identity (e.g., distributions, web sites, promotion, -etc.). - -@subsection Description - -@subsection 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 (@strong{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 @xref{trunk Identity Themes Motifs, Theme Motifs}. - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Models/Default/Distro.texi b/Manuals/Filesystem/trunk/Identity/Themes/Models/Default/Distro.texi deleted file mode 100644 index d10a829..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Models/Default/Distro.texi +++ /dev/null @@ -1,83 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -It applies to all major releases of CentOS distribution. - -@subsubsection 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. - -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. - -@quotation -@strong{Important} Remarking the CentOS release schema inside each -major release of CentOS distribution ---or similar visual -manifestation--- takes @emph{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. -@end quotation - -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 -@emph{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. - -@subsubsection One theme for each major release - -Other way we've been using to remark CentOS release schema is -applying one unique theme for @emph{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 @emph{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 @emph{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. - -@subsection Usage - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Models/Default/Distro/Anaconda.texi b/Manuals/Filesystem/trunk/Identity/Themes/Models/Default/Distro/Anaconda.texi deleted file mode 100644 index 9cf9a6e..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Models/Default/Distro/Anaconda.texi +++ /dev/null @@ -1,14 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@subsection Usage - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Models/Default/Promo.texi b/Manuals/Filesystem/trunk/Identity/Themes/Models/Default/Promo.texi deleted file mode 100644 index 7bfbe48..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Models/Default/Promo.texi +++ /dev/null @@ -1,27 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection 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. - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Models/Default/Web.texi b/Manuals/Filesystem/trunk/Identity/Themes/Models/Default/Web.texi deleted file mode 100644 index 427850f..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Models/Default/Web.texi +++ /dev/null @@ -1,26 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection 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. - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Motifs.texi b/Manuals/Filesystem/trunk/Identity/Themes/Motifs.texi deleted file mode 100644 index 7b8c0e0..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Motifs.texi +++ /dev/null @@ -1,114 +0,0 @@ -@subsection Goals - -The @file{trunk/Identity/Themes/Motifs} directory exists to: - -@itemize -@item Organize CentOS themes' artistic motifs. -@end itemize - -@subsection Description - -The artistic motif of theme is a graphic design component that -provides the visual style of themes, it is used as pattern to connect -all visual manifestations inside one unique theme. - -Artistic motifs are based on conceptual ideas. Conceptual ideas bring -the motivation, they are fuel for the engines of human imagination. -Good conceptual ideas may produce good motivation to produce almost -anything, and art works don't escape from it. - -@table @samp -@item TreeFlower -CentOS like trees, has roots, trunk, branches, leaves and flowers. Day -by day they work together in freedom, ruled by the laws of nature and -open standards, to show the beauty of its existence. -@item Modern -Modern, squares and circles flowing up. -@end table - -If you have new conceptual ideas for CentOS, then you can say that you -want to create a new artistic motif for CentOS. To create a new -artistic motif you need to create a directory under -@file{Identity/Themes/Motifs/} using a name coherent with your -conceptual idea. That name will be the name of your artistic motif. If -possible, when creating new conceptual ideas for CentOS, think about -what CentOS means for you, what does it makes you feel, take your -time, think deep, and share; you can improve the idea as time goes on. - -Once you have defined a name for your theme, you need to create the -motif structure of your theme. The motif structure is the basic -direcotry structure you'll use to work your ideas. Here is where you -organize your graphic design projects. - -To add a new motif structure to CentOS Artwork Repository, you need to -use the @command{centos-art} command line in the -@file{Identity/Themes/Motifs/} directory as described below: - -@example -centos-art add --motif=ThemeName -@end example - -The previous command will create the basic structure of themes for -you. The basic structure produced by @command{centos-art} command is -illustrated in the following figure: - -@example -trunk/Identity/Themes/Motifs/$ThemeName/ -|-- Backgrounds -| |-- Img -| `-- Tpl -|-- Info -| |-- Img -| `-- Tpl -|-- Palettes -`-- Screenshots -@end example - -@subsection Usage - -When designing artistic motifs for CentOS, consider the following -recommendations: - -@itemize -@item Give a unique (case-sensitive) name to your Motif. This name is -used as value wherever theme variable (@b{$THEME}) or translation marker -(@b{=THEME=}) is. Optionally, you can add a description about -inspiration and concepts behind your work. - -@item Use the location @file{trunk/Identity/Themes/Motifs/$THEME/} to -store your work. If it doesn't exist create it. Note that this require -you to have previous commit access in CentOS Artwork Repository. - -@item The CentOS Project is using the blue color (@b{#204c8d}) as base -color for its corporate visual identity. Use such base corporate color -information as much as possible in your artistic motif designs. - -@item Try to make your design fit one of the theme models. - -@item Feel free to make your art enterprise-level and beautiful. - -@item Add the following information on your artwork (both in a visible -design area and document metadata): - -@itemize - -@item The name (or logo) of your artistic motif. - -@item The copyright sentence: @b{Copyright (C) YEAR YOURNAME} - -@item The license under which the work is released. All CentOS Art -works are released under -@url{http://creativecommons.org/licenses/by-sa/3.0/,Creative Common -Share-Alike License 3.0} -(@url{http://creativecommons.org/licenses/by-sa/3.0/}). - -@end itemize -@end itemize - -@subsection See also - -@menu -* trunk Identity Themes:: -* trunk Identity:: -* trunk:: -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Flame.texi b/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Flame.texi deleted file mode 100644 index b9e787a..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Flame.texi +++ /dev/null @@ -1,206 +0,0 @@ -@subsection Goals - -This section describes the steps we followed to construct the -@emph{Flame} artistic motif. This section may be useful for anyone -interested in reproducing the @emph{Flame} artistic motif, or in -creating new artistic motifs for The CentOS Project corporate visual -identity (@pxref{trunk Identity}). - -@subsection Description - -The @emph{Flame} artistic motif was built using the flame filter of -Gimp 2.2 in CentOS 5.5. - -The flame filter of Gimp can produce stunning, randomly generated -fractal patterns. The flame filter of Gimp gives us a great oportunity -to reduce the time used to produce new artistic motifs, because of its -``randomly generated'' nature. Once the artistic motif be created, it -is propagated through all visual manifestations of CentOS Project -corporate visual identity using the @file{centos-art.sh} script -(@pxref{trunk Scripts Bash}) inside the CentOS Artwork Repository. - -To set the time intervals between each new visual style production, we -could reuse the CentOS distribution major release schema. I.e., we -could produce a new visual style, every two years, based on a new -``randomly generated'' flame pattern, and publish the whole corporate -visual identity (i.e., distribution stuff, promotion stuff, websites -stuff, etc.) with the new major release of CentOS distribution all -together at once. - -Producing a new visual style is not one day's task. Once we have -defined the artistic motif, we need to propagate it through all visual -manifestations of The CentOS Project corporate visual identity. When -we say that we could produce one new visual style every two years we -really mean: to work two years long in order to propagate a new visual -style to all visual manifestations of The CentOS Project corporate -visual identity. - -Obviously, in order to propagate one visual style to all different -visual manifestations of The CentOS Project corporate visual identity, -we need first to know which the visual manifestations are. To define -which visual manifestations are inside The CentOS Project corporate -visual identity is one of the goals the CentOS Artwork Repository and -this documentation manual are both aimed to satisfy. - -Once we define which the visual manifestation are, it is possible to -define how to produce them, and this way, organize the automation -process. Such automation process is one of the goals of -@file{centos-art.sh} script. - -With the combination of both CentOS Artwork Repository and -@file{centos-art.sh} scripts we define work lines where translators, -programmers, and graphic designers work together to distribute and -reduce the amount of time employed to produce The CentOS Project -monolithic corporate identity. - -From a monolithic corporate visual identity point of view, notice that -we are producing a new visual style for the same theme (i.e., -@emph{Flame}). It would be another flame design but still a flame -design. This idea is very important to be aware of, because we are -somehow ``refreshing'' the theme, not changing it at all. - -This way, as we are ``refreshing'' the theme, we still keep oursleves -inside the monolithic conception we are trying to be attached to -(i.e., one unique name, and one unique visual style for all visual -manifestations). - -Producing artistic motifs is a creative process that may consume long -time, specially for people without experienced knowledge on graphic -design land. Using ``randomly generated'' conception to produce -artistic motifs could be, practically, a way for anyone to follow in -order to produce maintainable artistic motifs in few steps. - -Due to the ``randomly generated'' nature of Flame filter, we find that -@emph{Flame} pattern is not always the same when we use @emph{Flame} -filter interface. - -Using the same pattern design for each visual manifestation is -essential in order to maintain the visual connection among all visual -manifestations inside the same theme. Occasionally, we may introduce -pattern variations in opacity, size, or even position but never change -the pattern design itself, nor the color information used by images -considered part of the same theme. - -@quotation -@strong{Important} -When we design background images, which are considered part of the -same theme, it is essential to use the same design pattern always. -This is what makes theme images to be visually connected among -themeselves, and so, the reason we use to define the word ``theme'' -as: a set of images visually connected among themeselves. -@end quotation - -In order for us to reproduce the same flame pattern always, -@emph{Flame} filter interface provides the @samp{Save} and @samp{Open} -options. The @samp{Save} option brings up a file save dialog that -allows you to save the current Flame settings for the plug-in, so that -you can recreate them later. The @samp{Open} option brings up a file -selector that allows you to open a previously saved Flame settings -file. - -The Flame settings we used in our example are saved in the file: - -@verbatim -trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def -@end verbatim - -@subsection Construction - -@subsubsection Step 1: Set image size - -Create an empty image and fill the @samp{Background} layer with black -(@code{000000}) color. Image dimensions depend on the final -destination you plan to use the image for. For the sake of our -construction example we used an image of 640x480 pixels and 300 pixels -per inch (ppi). - -@subsubsection Step 2: Add base color and pattern information - -Create a new layer named @samp{Base}, place it over @samp{Background} -layer and fill it with the base color (@code{7800ff}) you want to have -your background image set in. Add a mask to @samp{Base} layer using -radial gradient and blur it. You may need to repeat this step more -than once in order to achieve a confortable black radial degradation -on the right side of your design. - -Duplicate @samp{Base} layer and name it @samp{Paper}. Place -@samp{Paper} layer over @samp{Base} layer. Remove content of -@samp{Paper} layer and fill it with @samp{Paper (100x100)} pattern. -Once you've done with black radial degradation, reduce the -@samp{Paper} layer opacity to 20%. - -Notice that when we duplicate one layer, the mask information related -to layer is preserved from previous to next layer. This saves us some -of the time required to produce different layers with the same mask -information on them. - -Duplicate @samp{Paper} layer and rename it @samp{Stripes}. Remove -paper pattern from @samp{Stripes} layer. Fill @samp{Stripes} layer -with @samp{Stripes (48x48)} pattern and reduce the @samp{Stripes} -layer opacity to 15%. - -@subsubsection Step 3: Add flame motif - -Create a new layer named @samp{Flame}. Set the foreground -(@code{003cff}) and background (@code{0084ff}) colors to the gradient -you want to build the flame motif. - -To build flame motif, use the flame filter (@samp{Filters > Render > -Nature > Flame...}) on @samp{Flame} layer. We used a layer mask, with -a radial gradient on it to control the boundaries of flame motif on -@samp{Flame} layer. - -Duplicate @samp{Flame} layer and rename it `Flame Blur'. Place `Flame -Blur' below @samp{Flame} layer. Apply Gussian blur filter -(@samp{Filters > Blur > Gussian Blur...}) until reaching the desiered -effect. - -The opacity value, in @samp{Flame} layers, may vary from one image to -another based on the place the image will be finally placed on. For -example, images used as desktop background have the @samp{Flame} layer -opacity set at 100% but @samp{Flame Blur} is set to 70%. However, you -may find that background images used in anaconda progress slides have -opacity reduced differently, in order to reduce brightness in a way -that texts could look clean and readable over it. - -@subsubsection Step 4: Add foreground color - -Create a new layer named @samp{Color}, place it on top of all visible -layers and fill it with plain color (@code{4c005a}). Reduce -@samp{Color} layer opacity to 20%. You can use the @samp{Color} layer -to control the right side color information you want to produce the -image for. - -Duplicate @samp{Flame} layer and create a new layer named -@samp{Color#1}. Place @samp{Color#1} layer on top of layer named -@samp{Color}. Remove the mask information from @samp{Color#1} layer -and recreate a new one using an inverted alpha channel as reference. -Remove @samp{Color#1} layer content and fill it back with plain black -(@code{000000}) color. Reduce @samp{Color#1} opacity to 20%. In this -step we created a mask to protect the flame artistic motif from black -color, so when we decrement or increment the opacity of layer, the -flame artistic motif wouldn't be affected, just the environment -suround it. - -When you set color information, remember that the same artistic motif -needs to be indexed to 14 and 16 colors, in order to produce Grub and -Syslinux visual manifestations respectively. Using many different -colors in the artistic motif may reduce the possibility of your design -to fix all different situations in. Likewise, using more colors in -one design, and less colors in another design will reduce the -connectivity among your designs, since color information is relevant -to visual identity. - -When you propagate your artistic motif visual style to different -visual manifestations of CentOS Project corporate visual identity, it -is up to you to find out justice and compromise among all possible -variables you may face. - -@subsection See also - -@menu -* trunk Identity Themes Motifs:: -* trunk Identity Themes:: -* trunk Identity:: -* trunk:: -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern.texi b/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern.texi deleted file mode 100644 index 306ab79..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern.texi +++ /dev/null @@ -1,14 +0,0 @@ -@subsection Presentation - -@subsection Construction - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi b/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi deleted file mode 100644 index adda528..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi +++ /dev/null @@ -1,143 +0,0 @@ -@subsection Goals - -@itemize -@item Organize background images for Modern theme. -@end itemize - -@subsection Description - -Inside @file{Motifs} directory, the @file{Backgrounds/} directory is -used to create vectorial designs using Inkscape and background images -using Gimp. Later, you can export background images as @file{.png} and -load them in your vectorial design project using the import feautre of -Inkscape. - -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: - -@example -xcf/800x600.xcf -@end example - -to produce the background image: - -@example -img/800x600-bg.png -@end example - -which is loaded in: - -@example -svg/800x600.svg -@end example - -to produce the final background image: - -@example -img/800x600.png -@end example - -The @file{img/800x600.png} background image is produced automatically -by means of rendering scripts. - -In other cases (e.g. Anaconda), 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: - -@example -xcf/800x600-anaconda.xcf -@end example - -to produce the background image: - -@example -img/800x600-anaconda-bg.png -@end example - -which is loaded in: - -@example -svg/800x600-anaconda.svg -@end example - -to produce the file: - -@example -img/800x600-anaconda.png -@end example - -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 artistic -motif. - -Background images are linked (using the @b{import} feature of -Inkscape) inside almost all theme art works. This structure let you -make centralized changes on the visual identity and propagate them -quickly to other areas. - -In this structure you design background images for different screen -resolutions based on the theme artistic motif. - -You may create different artistic motifs propositions based -on the same conceptual idea. The conceptual idea is what defines a -theme. Artistic motifs are interpretations of that idea. - -Inside this directory artistic motifs are organized by name (e.g., -TreeFlower, Modern, etc.). - -Each artistic motif directory represents just one unique artistic -motif. - -The artistic motif is graphic design used as common pattern to connect -all visual manifestations inside one unique theme. The artistic motif -is based on a conceptual idea. Artistic motifs provide visual style -to themes. - -Designing artistic motifs is for anyone interested in creating -beautiful themes for CentOS. When building a theme for CentOS, the -first design you need to define is the artistic motif. - - -Inside CentOS Artwork Repository, theme visual styles (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 @command{centos-art} command line -interface to render the visual style, you are currently producing, -against an already-made theme model in order to produce the final -result. Final images are stored under @file{Motifs/} directory using -the model name, and the model directory structure as reference. - -The artistic motif base structure is used by @command{centos-art} to -produce images automatically. This section describes each directory of -CentOS artistic motif base structure. - -@subsection Usage - -The @file{Backgrounds/} directory is probably the core component, -inside @file{Motifs/} directory structure. Inside @file{Backgrounds/} -directory you produce background images used by almost all theme -models (e.g., Distribution, Websites, Promotion, etc.). The -@file{Backgrounds/} directory can contain subdirectories to help you -organize the design process. - -@subsection See also - -@menu -* trunk Identity Themes Motifs Modern Backgrounds Img:: -* trunk Identity Themes Motifs Modern Backgrounds Tpl:: -* trunk Identity Themes Motifs Modern Backgrounds Xcf:: -@comment --- Removed(* trunk Translations Identity Themes Backgrounds::) --- -@end menu - diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img.texi b/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img.texi deleted file mode 100644 index fc1ecfb..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img.texi +++ /dev/null @@ -1,19 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@subsection Usage - -In this directory is where you store all background images (e.g., -.png, .jpg, .xpm, etc.). This directory is required by -@file{centos-art} command line interface. - -@subsection See also - -@menu -@end menu - diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl.texi b/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl.texi deleted file mode 100644 index 4b3308a..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl.texi +++ /dev/null @@ -1,18 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@subsection Usage - -In this directory is where you store all the scalable vector graphics -(e.g., .svg) files. This directory is required by @file{centos-art} -command line interface. - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf.texi b/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf.texi deleted file mode 100644 index b572a3d..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf.texi +++ /dev/null @@ -1,27 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - - -@subsection Usage - -In this directory is where you store the project files (e.g, .xcf) of -Gimp. This directory is not required by @file{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 -@file{Xcf/} directory to store background projects. Of course, you can -merge both Gimp and Inkscape power to produce images based on them. -In this last case you need the @file{Xcf/} directory. - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi b/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi deleted file mode 100644 index 8735b28..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi +++ /dev/null @@ -1,59 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@subsection Usage - -To render Anaconda progress slide images using the @emph{Modern} -artistic motif design, the Default theme model, and available -translation files (--- @strong{Removed}(pxref:trunk Translations Identity Themes Distro -Anaconda Progress) ---); use the following commands: - -@example -cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ -centos-art render --identity -@end example - -The above command will create the following structure: - -@example -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 -@end example - - -@subsection See also - -@menu -@end menu - diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Palettes.texi b/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Palettes.texi deleted file mode 100644 index 79765d1..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/Modern/Palettes.texi +++ /dev/null @@ -1,20 +0,0 @@ -@subsection Goals - -@itemize -@item Organize palette files for Modern theme. -@end itemize - -@subsection Description - -@subsection 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 the unique color information -required by theme. - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/TreeFlower.texi b/Manuals/Filesystem/trunk/Identity/Themes/Motifs/TreeFlower.texi deleted file mode 100644 index 9cf9a6e..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/TreeFlower.texi +++ /dev/null @@ -1,14 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@subsection Usage - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds.texi b/Manuals/Filesystem/trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds.texi deleted file mode 100644 index 32e0626..0000000 --- a/Manuals/Filesystem/trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds.texi +++ /dev/null @@ -1,323 +0,0 @@ -@subsection Goals - -This section exists to orgnize backgrounds of @emph{TreeFlower} -artistic motif. - -@subsection Description - -@subsubsection Desktop background - -Once you have defined the vectorial artistic motif design, use the -@command{centos-art.sh} script (as described in usage section below) -to produce the png version of it. With the png version of your -vectorial design do the following: - -Open the png version with GIMP. - -Save the png version as a project of GIMP inside -@file{trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Xcf} -directory, using the same name of your vectorial design but with the -@samp{.xcf} extension. - -Now use GIMP to improve your design. Here you may add one layer for -pattern, another for colors, and so on until you find yourself -confortable with your artwork. For example, the following layer -distribution (from bottom to top) was used to build revision 285 of -file @file{1360x768.xcf} using @emph{TreeFlower} artistic motif at -revision 241. - -@table @strong -@item Layer 1: Background - -The first thing we did with GIMP was to create a layer named -@samp{Background} to store the artistic motif (File > Open as layer). -This layer is the lowest layer in the image. Later, we started to -create layers one upon another to change the artistic motif visual -style. - -@item Layer 2: Shadow#1 - -This layer is above @samp{Background} and contains a linear gradient -from left (000000) to right (transparent) covering the whole image. -This layer masks the artistic motif to avoid the effect of linear -gradient. This layer is 100% of opacity. - -@item Layer 3: Shadow#2 - -This layer is above @samp{Shadow#1} and contains a linear gradient -from left (000000) to right (transparent) covering just the 70% of the -whole image aproximatly. This layer doesn't mask the artistic motif -which make the left part of it fall into the dark of linear gradient. -This layer is 100% of opacity. - -@item Layer 4: Pattern (Paper) - -This layer is above @samp{Shadow#2} an contains the paper pattern -shipped with GIMP 2.2. This layer doesn't mask the artistic motif so -the pattern is applied over the whole image. This layer is set to 15% -of opacity. - -@item Layer 5: Pattern (Stripes) - -This layer is above @samp{Pattern (Paper)} and contains the stripes -used over the artistic motif. This layer do masks the artistic motif -so the stripes are only applied to it. This layer is set to 10% of -opacity. - -@item Layer 6: Shadow#3 - -This layer is above @samp{Pattern (Stripes)} and contains a linear -gradient from right (6600ff) to left (transparent). This layer masks -the artistic motif so the linear gradient doesn't affect it. This -layer is set to 15% of opacity. - -@item Layer 7: Shadow#4 - -This layer is above @samp{Shadow#3} and contains a -linear gradient from left (000000) to right (transparent). This layer -do masks the artistic motif so the linear gradient doesn't affect it. -This layer is set to 10% of opacity. - -@item Layer 8: Color#1 - -This layer is above @samp{Shadow#4} and is filled with orange (ffae00) -color over the whole image. This layer is set to 10% of opacity. - -@item Layer 9: Color#2 - -This layer is above @samp{Color#1} and is filled with -blue (010a88) color over the whole image. This layer is set to 10% of -opacity. - -@end table - -@quotation -@strong{Note} There is no definite combination. To get the appropriate -visual design is a matter of constant testing and personal taste. -@end quotation - -Finally, use @samp{Save as copy ...} option to export the final -design. To export the final design use the same name of your vectorial -design plus @samp{-final.png} extension. - -You can repeat these steps to create images for other screen -resolutions. - -@subsubsection Anaconda Prompt (syslinux) background - -When building syslinux backgrounds it is needed to take into account -that the final image is reduced to 16 colors. In desktop background -there is no color limitation but syslinux does have. The goal of this -section is achieving a final syslinux background as close as possible -to desktop backgrounds using 16 colors only. - -Another point to consider is the forground and background definition -used by syslinux. The syslinux documentation says that the color set -in position 0 is the background and color set in position 7 is the -forground. The final palette of color used by our background will -match that specification. For great contrast we'll use black as -background and white as forground. At this poing we have black -(000000) and white (ffffff) colors in our syslinux palette, which left -us with 14 colors to play with. - -Let's begin with @file{Xcf/640x300.xcf} layer distribution from bottom -to top: - -@table @strong -@item Layer 1: Background - -This layer is the lowest layer in the image composition and contains -the artistic motif image rendered for the same resolution (i.e., -@file{Img/Png/640x300.png}). This layer is set to 100% of opacity. - -@item Layer 2: Pattern (Paper) - -This layer is placed above @samp{Background} layer and contains the -paper pattern shipped with GIMP 2.2. This layer doesn't mask the -artistic motif. This layer is set to 30% of opacity. - -@item Layer 3: Pattern (Stripes) - -This layer is placed above @samp{Pattern (Paper)} layer and contains -the stripes pattern shipped with GIMP 2.2. This layer does mask the -artistic motif in order to apply the stripes over it only. The -background is not affected by the stripes pattern just the artistic -motif. This layer is set to 20% of opacity. - -@item Layer 4: Shadow#1 - -This layer is placed above @samp{Pattern (Stripes)} layer and fills -the entire layer area with violet (6600ff) color. This layer do mask -the artistic motif in order to applied the violet color to the -background area outside the artistic motif only. This layer is set to -15% of opacity. - -@item Layer 5: Color#1 - -This layer is above @samp{Shadow#1} and is filled with orange (ffae00) -color to cover the whole image. This layer is set to 10% of opacity. - -@item Layer 6: Color#2 - -This layer is above @samp{Color#1} and is filled with blue (010a88) -color to cover the whole image. This layer is set to 10% of opacity. - -@item Layer 7: Shadow#2 - -This layer is above @samp{Color#1} and contains a linear gradient from -left (000000) to right (transparent) covering 70% of the image -approximately. - -@end table - -At this point we have the composition and should look like the desktop -backgrounds. Compared with desktop backgrounds there are some -differences in opacity. This is because in our testings the final -color information found with this composition produces an acceptable -16 color image. Of course this is something we haven't seen yet. - -To define the color information of our current coposition, save the -syslinux background composition we've done using @samp{File > Save as -Copy ...} option in the following location: - -@verbatim -trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Img/Png/640x300-final.png -@end verbatim - -Now, create the final png version of syslinux backgrounds using the -following command: - -@verbatim -centos-art render --entry=trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Prompt -@end verbatim - -This command will create syslinux-splash final images for all major -releases of CentOS distribution the repository has been configured to. -The important files here are @file{syslinux-splash.png}, other -files may contain the wrong information because we haven't defined yet -the correct color information to use. - -Open one @file{syslinux-splash.png} file with GIMP and use the -@samp{Image > Mode > Indexed} to reduce image colors up to 16 colors, -using the @samp{Generate optimum palette} feature of GIMP. If the -image looks aceptable after reducing colors, use the @samp{Palettes} -menu (Ctrl+P) of GIMP to import a new palette from file and name it -@samp{CentOS-TreeFlower-Syslinux}. Once you've saved the palette, the -color information is stored at: - -@verbatim -~/.gimp-2.2/palettes/CentOS-TreeFlower-Syslinux.gpl -@end verbatim - -You need to edit @file{CentOS-TreeFlower-Syslinux.gpl} file in order -to set the appropriate order of colors. Remember black (000000) in -position 0, and white (ffffff) in position 7. Other positions are -irrelevant. When editing this file you may find that color reduction -did not set black and white colors to their respective values exactly. -Change that manually. For example, consider the following palette: - -@verbatim -GIMP Palette -Name: CentOS-TreeFlower-Syslinux -Columns: 16 -# - 0 0 0 Background (black) - 23 20 35 Untitled - 34 25 48 Untitled - 37 35 60 Untitled - 47 36 68 Untitled - 37 54 86 Untitled - 60 48 90 Untitled -255 255 255 Foreground (white) - 66 54 99 Untitled - 74 61 98 Untitled - 49 78 126 Untitled - 43 87 151 Untitled - 92 89 95 Untitled - 54 104 183 Untitled -158 153 156 Untitled -201 196 195 Untitled -@end verbatim - -Update the @samp{Palettes} menu to get the new color positions from -the file you just edited and open the palette with double click. - -Update the @file{syslinux.gpl} file copying the following file: - -@verbatim -~/.gimp-2.2/palettes/CentOS-TreeFlower-Syslinux.gpl -@end verbatim - -to - -@verbatim -trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.gpl -@end verbatim - -With the @samp{CentOS-TreeFlower-Syslinux} palette opened in the -@samp{Palette Editor}, open (Ctrl+O) the following file: - -@verbatim -trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.ppm -@end verbatim - -and replace its color information with that one in -@samp{CentOS-TreeFlower-Syslinux} palette. When you are replacing -color information inside @file{syslilnux.ppm}, remember to keep the -order of colors just as they are in the -@samp{CentOS-TreeFlower-Palette} palette. - -The @file{syslinux.ppm} file is 16 pixels width and 1 pixel height, so -you probably need to zoom it a bit to set the color information in -their place when using the pen tool with the brush @samp{Circle (01) -(1 x 1)}. - -Once you've updated the @samp{syslinux.ppm} file, it is time to update -the following file: - -@verbatim -trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.hex -@end verbatim - -The @file{syslinux.hex} file contains the color information in -hexadecimal notation. The color information in hexadecimal notation -is required by @command{ppmtolss16} command. The @command{ppmtolss16} -command produces the final LSS16 image format that is used by syslinux -program inside CentOS distribution. - -The color information inside @file{syslinux.hex} must match the one in -@file{syslinux.ppm} and @file{syslinux.gpl}. For example, based on -@file{CentOS-TreeFlower-Syslinux} palette of colors above, consider -the following @file{syslinux.hex} file: - -@verbatim -#000000=0 -#171423=1 -#221930=2 -#25233c=3 -#2f2444=4 -#253656=5 -#3c305a=6 -#ffffff=7 -#423663=8 -#4a3d62=9 -#314e7e=10 -#2b5797=11 -#5c595f=12 -#3668b7=13 -#9e999c=14 -#c9c4c3=15 -@end verbatim - -@subsubsection Grub background - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Identity/Widgets.texi b/Manuals/Filesystem/trunk/Identity/Widgets.texi deleted file mode 100644 index 9cf9a6e..0000000 --- a/Manuals/Filesystem/trunk/Identity/Widgets.texi +++ /dev/null @@ -1,14 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@subsection Usage - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Locales.texi b/Manuals/Filesystem/trunk/Locales.texi deleted file mode 100644 index 98a4746..0000000 --- a/Manuals/Filesystem/trunk/Locales.texi +++ /dev/null @@ -1,56 +0,0 @@ -The @file{trunk/Locales} directory exists to store the translation -messages used to produce content in different languages. - -Translation messages are organized using the directory structure of -the component being translated. For example, if we want to provide -translation messages for @file{trunk/Manuals/Filesystem}, then the -@file{trunk/Locales/Manuals/Filesystem} directory needs to be created. - -Once the locale directory exists for the component we want to provide -translation messages for, it is necessary to create the translation -files where translation messages are. The translation files follows -the concepts of @command{xml2po} and GNU @command{gettext} tools. - -The basic translation process is as follow: first, translatable -strings are extracted from files and a portable object template (.pot) -is created or updated with the information. Using the portable object -template, a portable object (.po) is created or updated for translator -to locale the messages retrived. Finally, a machine object (.mo) is -created from portable object to sotore the translated messages. - -Inside the repository there are two ways to retrive translatable -strings from files. The first one is through @command{xml2po} command -and the second through @command{xgettext} command. The @command{xml2po} -is used to retrive translatable strings from XML files (e.g., Scalable -Vector Graphics, DocBook, etc.) and the @command{xgettext} command is -used to retrive translatable strings from shell scripts files (e.g., -the files that make the @command{centos-art.sh} command-line -interface). - -When translatable strings are retrived from XML files, using the -@command{xml2po} command, there is no need to create the machine -object as we do when translatable strings ar retrived from shell -files, using the @command{xgettext} command. The @command{xml2po} -produces a temporal machine object in order to create a translated XML -file. Once the translated XML file has been created the machine object -is no longer needed. On the other hand, the machine object produced by -the @command{xgettext} command is required by the system in order for -the show shell script localized messages. - -Another difference between @command{xml2po} and @command{xgettext} we -need to be aware of is the directory structure used to store machine -objects. In @command{xml2po}, the machine object is created in the -current working directory as @file{.xml2po.mo} and can be safetly -removed once the translated XML file has been created. In the case of -@command{xgettext}, the machine object needs to be stored in the -@file{$TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo} file in order -for the system to interpret it and should not be removed since it is -the file that contain the translation messages themselves. - -Automation of localization tasks is achived through the @code{locale} -functionality of command-line interface. - -@menu -* trunk Scripts Bash Cli Functions Locale:: -@end menu - diff --git a/Manuals/Filesystem/trunk/Locales/Identity.texi b/Manuals/Filesystem/trunk/Locales/Identity.texi deleted file mode 100644 index 5bf1b70..0000000 --- a/Manuals/Filesystem/trunk/Locales/Identity.texi +++ /dev/null @@ -1,29 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@comment --- Removed(* trunk Translations Identity Brands::) --- -@comment --- Removed(* trunk Translations Identity Fonts::) --- -@comment --- Removed(* trunk Translations Identity Models::) --- -@comment --- Removed(* trunk Translations Identity Release::) --- -@comment --- Removed(* trunk Translations Identity Themes::) --- -@comment --- Removed(* trunk Translations Identity Widgets::) --- -* trunk Identity:: -@end menu diff --git a/Manuals/Filesystem/trunk/Locales/Identity/Brands.texi b/Manuals/Filesystem/trunk/Locales/Identity/Brands.texi deleted file mode 100644 index 6f771ef..0000000 --- a/Manuals/Filesystem/trunk/Locales/Identity/Brands.texi +++ /dev/null @@ -1,105 +0,0 @@ -@subsection Goals - -@itemize -@item Organize brands' translation files. -@end itemize - -@subsection Description - -Translation files, inside @file{trunk/Translations/Identity/Brands} -translation entry, don't use default rendering translation -functionality, they use the following translation pre-rendering -configuration file instead: - -@verbatim -/home/centos/artwork/trunk/Translation/Identity/Brands/render.conf.sh -@end verbatim - -Inside @file{trunk/Translations/Identity/Brands} translation entry, -translation files are symbolic links pointing to the common template -translation structure, inside the translation template (@samp{Tpl/}) -directory. - -Inside @file{trunk/Translations/Identity/Brands} translation entry, -translation files are created using identity design templates as -reference. The translation pre-rendering script creates a translation -structure where the translation template (@samp{Tpl/}) directory -structure applies to each single design template available. - -For example, if the brands' translation template (@samp{Tpl/}) -directory has 30 translation files, and there are 20 design templates; -the brands' translation pre-rendering script creates a translation -structure of symbolic links where the 30 translation files apply the -20 design templates one by one, producing 600 translation symbolic -links as result. At this point, when rendering identity, the -@command{centos-art} script considers translation symbolic links as -translation files. - -Translation file names, inside brands' translation template -(@samp{Tpl}) directory have special meaning: - -@subsubsection Conventional file names -@cindex Translation brands file names - -Convenctional file names look like @file{blue.sed}, @file{2c-a.sed}, -etc. Replacement commands inside translation file are applied to -design templates and translation file names are used as final image -name. The image dimensions use the same dimensions that design -template has. - -@subsubsection Numeric file names -@cindex Translation brands file names - -Numeric file names look like @file{300.sed}, @file{200.sed}, etc. -Replacements commands inside translation files are applied to design -templates, and translation file names are used as final image name. -The final image is saved using an specific @samp{width} defined by the -number part of the translation file name. The image @samp{height} is -automatically scaled based on the previous @samp{width} definition to -maintain the designing ratio. - -For example, if your design template has 400x200 pixels of dimension, -and you apply a translation file named `300.sed' to it, the final -image you get as result will have 300x100 pixels of dimension. The -same is true if you use higher numbers like `1024.sed', `2048.sed', -etc. In these cases you have bigger images proportionally. - -As we are using scalable vector graphics to design identity templates, -the image size you produce is not limitted in size. You can use one -design template produced in 400x200 pixels to produce larger or -shorter PNG images using numeric translation files as described -above. - -@subsubsection Translation markers - -Inside @file{trunk/Translations/Identity/Brands/}, translation files -combine the following translation markers: - -@table @samp -@item #000000 - -Specify which color to use when rendering brand images. - -@quotation -@strong{Note} As translation files inside -@file{trunk/Translations/Identity/Brands} are symbolic links that -point to template translation files, translation markers are defined -inside template translation files. -@end quotation -@end table - -@subsection Usage -@cindex How to render brands' translation files - -To render brands' translation files, use the following command: - -@verbatim -centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands -@end verbatim - -@subsection See also - -@menu -@comment --- Removed(* trunk Translations Identity Brands Tpl::) --- -* trunk Identity Brands:: -@end menu diff --git a/Manuals/Filesystem/trunk/Locales/Identity/Brands/Tpl.texi b/Manuals/Filesystem/trunk/Locales/Identity/Brands/Tpl.texi deleted file mode 100644 index b53171e..0000000 --- a/Manuals/Filesystem/trunk/Locales/Identity/Brands/Tpl.texi +++ /dev/null @@ -1,10 +0,0 @@ -@subsection Goals - -@subsection Description - -@subsection Usage - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Locales/Identity/Fonts.texi b/Manuals/Filesystem/trunk/Locales/Identity/Fonts.texi deleted file mode 100644 index 2699334..0000000 --- a/Manuals/Filesystem/trunk/Locales/Identity/Fonts.texi +++ /dev/null @@ -1,62 +0,0 @@ -@subsection Goals - -This section exists to organize fonts translation files. -@subsection Description - -Translation files, inside @file{trunk/Translations/Fonts}, have the -following structure: - -@verbatim -s!font-family:Denmark!font-family:DejaVu LGC Sans! -s!font-weight:normal!font-weight:bold! -s!font-style:normal!font-style:italic! -@end verbatim - -Inside @file{trunk/Translations/Fonts}, there is one translation file -for each font preview image you want to produce. This way, we create -one translation file for each font-family we use somewhere inside -CentOS visual identity. - -@quotation -@strong{Important} Do not create translation files for -font-families not used somewhere inside CentOS visual identity. The -identity of font entry (@pxref{trunk Identity Fonts}) is used as -reference when someone needs to know which font-families are allowed -to use inside CentOS visual identity. -@end quotation - -@subsubsection Translation Markers - -Inside @file{trunk/Translations/Identity/Fonts}, translation files -combine the following translation markers: - -@table @samp -@item font-family:Denmark -Specify which font family to use when rendering font preview images. -@item font-weight:normal -Specify which font weight to use when rendering font preview images. -@item font-style:normal -Specify which font style to use when rendering font preview images. -@end table - -@subsection Usage -@cindex How to render fonts' translation files - -Inside @file{trunk/Translations/Fonts} you use your favorite text -editor to create translation files. Inside -@file{trunk/Translations/Fonts} there is not translation template -directory (@file{Tpl/}), nor translation rendering using -@command{centos-art} script. For example, to create the -@file{dejavu_lgc_sans-boldoblique.sed} translation file using -@command{vim} editor, type the following command: - -@verbatim -vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed -@end verbatim - -@subsection See also - -@menu -* trunk Identity Fonts:: -@end menu - diff --git a/Manuals/Filesystem/trunk/Locales/Identity/Models.texi b/Manuals/Filesystem/trunk/Locales/Identity/Models.texi deleted file mode 100644 index b53171e..0000000 --- a/Manuals/Filesystem/trunk/Locales/Identity/Models.texi +++ /dev/null @@ -1,10 +0,0 @@ -@subsection Goals - -@subsection Description - -@subsection Usage - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Locales/Identity/Release.texi b/Manuals/Filesystem/trunk/Locales/Identity/Release.texi deleted file mode 100644 index b53171e..0000000 --- a/Manuals/Filesystem/trunk/Locales/Identity/Release.texi +++ /dev/null @@ -1,10 +0,0 @@ -@subsection Goals - -@subsection Description - -@subsection Usage - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Locales/Identity/Themes.texi b/Manuals/Filesystem/trunk/Locales/Identity/Themes.texi deleted file mode 100644 index b53171e..0000000 --- a/Manuals/Filesystem/trunk/Locales/Identity/Themes.texi +++ /dev/null @@ -1,10 +0,0 @@ -@subsection Goals - -@subsection Description - -@subsection Usage - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Locales/Identity/Themes/Backgrounds.texi b/Manuals/Filesystem/trunk/Locales/Identity/Themes/Backgrounds.texi deleted file mode 100644 index fb39647..0000000 --- a/Manuals/Filesystem/trunk/Locales/Identity/Themes/Backgrounds.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Locales/Identity/Themes/Distro/Anaconda/Progress.texi b/Manuals/Filesystem/trunk/Locales/Identity/Themes/Distro/Anaconda/Progress.texi deleted file mode 100644 index f2d99e2..0000000 --- a/Manuals/Filesystem/trunk/Locales/Identity/Themes/Distro/Anaconda/Progress.texi +++ /dev/null @@ -1,94 +0,0 @@ -@subsection Goals - -@itemize -@item Organize Anaconda progress translation templates. -@item Organize Anaconda progress translation files in several -languages and major releases of CentOS distribution. -@end itemize - -@subsection Description - -Use the following command to produce translation files based: - -@example -trunk/Translations/Identity/Themes/Distro/Anaconda/Progress -`-- Tpl - |-- en - | |-- 01-welcome.sed - | |-- 02-donate.sed - | `-- 03-yum.sed - `-- es - |-- 01-welcome.sed - |-- 02-donate.sed - `-- 03-yum.sed -@end example - -In order to produce the slide images in PNG format we need to have the -translation files first. So we use the following commands to create -translation files for CentOS 3, 4, and 5 major releases: - -@example -centos-art render --translation --filter='3,4,5' -@end example - -The above commands will produce the following translation structure: - -@example -trunk/Translations/Identity/Themes/Distro/Anaconda/Progress -|-- 3 -| |-- en -| | |-- 01-welcome.sed -| | |-- 02-donate.sed -| | `-- 03-yum.sed -| `-- es -| |-- 01-welcome.sed -| |-- 02-donate.sed -| `-- 03-yum.sed -|-- 4 -| |-- en -| | |-- 01-welcome.sed -| | |-- 02-donate.sed -| | `-- 03-yum.sed -| `-- es -| |-- 01-welcome.sed -| |-- 02-donate.sed -| `-- 03-yum.sed -|-- 5 -| |-- en -| | |-- 01-welcome.sed -| | |-- 02-donate.sed -| | `-- 03-yum.sed -| `-- es -| |-- 01-welcome.sed -| |-- 02-donate.sed -| `-- 03-yum.sed -`-- Tpl - |-- en - | |-- 01-welcome.sed - | |-- 02-donate.sed - | `-- 03-yum.sed - `-- es - |-- 01-welcome.sed - |-- 02-donate.sed - `-- 03-yum.sed -@end example - -At this point we have all the translation files we need to produce -Anaconda progress welcome, donate and yum slides images; in English -and Spanish languages; for CentOS 3, CentOS 4, and CentOS 5. That is, -a sum of 18 images around. - -Now, with translation files in place, let's move to -@file{trunk/Identity} structure and render them. - -@itemize -@item @xref{trunk Identity Themes Motifs Modern Distro Anaconda Progress}. -@end itemize - -@subsection Usage - -Translation rendering is described in @samp{trunk/Translations} -documentation entry (--- @strong{Removed}(pxref:trunk Translations) ---). - - -@subsection See also diff --git a/Manuals/Filesystem/trunk/Locales/Identity/Widgets.texi b/Manuals/Filesystem/trunk/Locales/Identity/Widgets.texi deleted file mode 100644 index fda4863..0000000 --- a/Manuals/Filesystem/trunk/Locales/Identity/Widgets.texi +++ /dev/null @@ -1,23 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@comment --- Removed(* trunk Translations Identity Widgets::) --- -@end menu diff --git a/Manuals/Filesystem/trunk/Manuals.texi b/Manuals/Filesystem/trunk/Manuals.texi deleted file mode 100644 index fb39647..0000000 --- a/Manuals/Filesystem/trunk/Manuals.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts.texi b/Manuals/Filesystem/trunk/Scripts.texi deleted file mode 100644 index c9b371f..0000000 --- a/Manuals/Filesystem/trunk/Scripts.texi +++ /dev/null @@ -1,25 +0,0 @@ -@subsection Goals - -The @file{trunk/Scripts} directory exists to: - -@itemize -@item Organize the ``trunk'' development line of automation scripts by -programming language. -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts/Bash.texi b/Manuals/Filesystem/trunk/Scripts/Bash.texi deleted file mode 100644 index 0b387e6..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Bash.texi +++ /dev/null @@ -1,156 +0,0 @@ -@subsection Goals - -The @file{trunk/Scripts/Bash} directory exists to organize the trunk -development line of @file{centos-art.sh} automation script. The -@file{centos-art.sh} script standardizes frequent tasks inside your -working copy of CentOS Artwork Repository. - -@subsection Description - -The best way to understand @file{centos-art.sh} automation script is -studying its source code. However, as start point, you may prefer to -read an introductory resume before diving into the source code -details. - -The @file{centos-art.sh} script is written in Bash. Most tasks, inside -@file{centos-art.sh} script, have been organized in many specific -functionalities that you can invoke from the @command{centos-art} -command-line interface. - -When you type the @command{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 @var{PATH} environment variable to look for -that command location. If your system was prepared to use CentOS -Artwork Repository correctly (--- @strong{Removed}(pxref:trunk Scripts Bash Functions -Verify) ---), you should have a symbolic link inside @file{~/bin/} -directory that points to the @file{centos-art.sh} script file. As -@file{~/bin/} directory is, by default, inside @var{PATH} environment -variable, the execution of @command{centos-art} command runs the -@file{centos-art.sh} script. - -When @file{centos-art.sh} script is executed, the first it does is -executing the @file{trunk/Scripts/Bash/initEnvironment.sh} script to -initialize global variables (e.g., @command{gettext} variables) and -global function scripts. Global function scripts are located inside -@file{trunk/Scripts/Bash/Functions} directory and their file names -begin with @samp{cli}. Global function scripts provide common -functionalities that can be used anywhere inside @file{centos-art.sh} -script execution environment. - -Once global variables and function scripts have been loaded, -@file{centos-art.sh} script executes the @command{cli} global function -from @file{cli.sh} function script to retrive command-line arguments -and define some default values that may be used later by specific -function scripts (--- @strong{Removed}(pxref:trunk Scripts Bash Functions) ---). - -As convenction, the @file{centos-art.sh} command-line arguments have -the following format: - -@verbatim -centos-art arg1 --arg2=val2 --arg3=val3 -@end verbatim - -In the above example, @samp{centos-art} is the command you use to -invoke @file{centos-art.sh} script. The @samp{arg1} is required and -represents the functionality you want to perform (e.g., -@option{verify}, @option{render}, @option{locale}, @option{manual}, -etc.). The remaining arguments are modifiers to @option{arg1}. The -@option{--arg2} definition is required and represets, specifically, -the action inside the functionality you want to perform. The -@option{--arg3} and on, are optional. - -Once command-line arguments have been retrived, the -@file{centos-art.sh} script loads specific functionalities using the -@file{cli_getFunctions.sh} function script. Only one specific -functionality can be loaded at one script execution I.e., you run -@command{centos-art.sh} script to run just one functionality. - -@float Figure,fig:trunk/Scripts/Bash:Initialization -@verbatim -+----------------------------------------------------------------------+ -| [centos@host]$ centos-art function --action='value' --option='value' | -+----------------------------------------------------------------------+ -| ~/bin/centos-art --> ~/artwork/trunk/Scripts/Bash/centos-art.sh | -+---v-----------------------------------------v------------------------+ - | centos-art.sh | - +---v---------------------------------v---+ - . | initEnvironment.sh | . - . +---------------------------------+ . - . | cli $@ | . - . +---v-------------------------v---+ . - . . | cli_getFunctions | . . - . . +---v-----------------v---+ . . - . . . | function1 | . . . - . . . | function2 | . . . - . . . | function3 | . . . - . . . +-----------------+ . . . - . . ........................... . . - . ................................... . - ........................................... -@end verbatim -@caption{The functionalities initialization environment.} -@end float - -Functionalities are implemented by means of actions. Once the -functionality has been initiazalized, actions initialization take -place for that functionality. Actions initialization model is very -similar to functions initialization model. But with the difference, -that actions are loaded inside function environment, and so, share -variables and functions defined inside function environment. - -@float Figure,fig:trunk/Scripts/Bash/Functions:Initialization -@verbatim -+--------------------------------------+ -| cli_getFunctions | -+---v------------------------------v---+ -. | function1 | . -. +---v----------------------v---+ . -. . | function1_getActions | . . -. . +---v--------------v---+ . . -. . . | action 1 | . . . -. . . | action 2 | . . . -. . . | action n | . . . -. . . +--------------+ . . . -. . ........................ . . -. ................................ . -. +------------------------------+ . -. | function2 | . -. +---v----------------------v---+ . -. . | function2_getActions | . . -. . +---v--------------v---+ . . -. . . | action 1 | . . . -. . . | action 2 | . . . -. . . | action n | . . . -. . . +--------------+ . . . -. . ........................ . . -. ................................ . -. +------------------------------+ . -. | function3 | . -. +---v----------------------v---+ . -. . | function3_getActions | . . -. . +---v--------------v---+ . . -. . . | action 1 | . . . -. . . | action 2 | . . . -. . . | action n | . . . -. . . +--------------+ . . . -. . ........................ . . -. ................................ . -........................................ -@end verbatim -@caption{The actions initialization environment.} -@end float - -@subsection Usage - -The @file{centos-art.sh} script usage information is described inside -each specific function documentation (--- @strong{Removed}(pxref:trunk Scripts Bash -Functions) ---). - -@subsection See also - -@menu -* trunk Scripts:: -@comment --- Removed(* trunk Scripts Bash Functions::) --- -@comment --- Removed(* trunk Scripts Bash Locale::) --- -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts/Bash/Cli.texi b/Manuals/Filesystem/trunk/Scripts/Bash/Cli.texi deleted file mode 100755 index e69de29..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Bash/Cli.texi +++ /dev/null diff --git a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions.texi b/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions.texi deleted file mode 100755 index 2a421ab..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions.texi +++ /dev/null @@ -1,1222 +0,0 @@ -@subsection Goals - -The @file{trunk/Scripts/Bash/Functions} directory exists to organize -@file{centos-art.sh} specific functionalities. - -@subsection Description - -The specific functions of @file{centos-art.sh} script are designed -with ``Software Toolbox'' philosophy (@pxref{Toolbox -introduction,,,coreutils.info}) in mind: each program ``should do one -thing well''. Inside @file{centos-art.sh} script, each specific -functionality is considered a program that should do one thing well. -Of course, if you find that they still don't do it, feel free to -improve them in order for them to do so. - -The specific functions of @file{centos-art.sh} script are organized -inside specific directories under @file{trunk/Scripts/Bash/Functions} -location. Each specific function directory should be named as the -function it represents, with the first letter in uppercase. For -example, if the function name is @code{render}, the specific function -directory for it would be @samp{trunk/Scripts/Bash/Functions/Render}. - -To better understand how specific functions of @file{centos-art.sh} -script are designed, lets create one function which only goal is to -output different kind of greetings to your screen. - -When we create specific functions for @file{centos-art.sh} script it -is crucial to know what these functions will do exactly and if there -is any function that already does what we intend to do. If there is no -one, it is good time to create them then. Otherwise, if -functionalities already available don't do what you exactly expect, -contact their authors and work together to improve them. - -@quotation -@strong{Tip} Join CentOS developers mailing list -@email{centos-art@@centos.org} to share your ideas. -@end quotation - -It is also worth to know what global functions and variables do we -have available inside @file{centos-art.sh} script, so advantage can be -taken from them. Global variables are defined inside global function -scripts. Global functions scripts are stored immediatly under -@file{trunk/Scripts/Bash/Functions} directory, in files begining with -@samp{cli} prefix. - -OK, let's begin with our functionality example. - -What function name do we use? Well, lets use @code{greet}. Note that -@samp{hello} word is not a verb; but an expression, a kind of -greeting, an interjection specifically. In contrast, @samp{greet} is a -verb and describes what we do when we say @samp{Hello!}, @samp{Hi!}, -and similar expressions. - -So far, we've gathered the following function information: - -@verbatim -Name: greet -Path: trunk/Scripts/Bash/Functions/Greet -File: trunk/Scripts/Bash/Functions/Greet/greet.sh -@end verbatim - -The @file{greet.sh} function script is the first file -@file{centos-art.sh} script loads when the @samp{greet} functionality -is called using commands like @samp{centos-art greet --hello='World'}. -The @file{greet.sh} function script contains the @code{greet} function -definition. - -Inside @file{centos-art.sh} script, as convenction, each function -script has one top commentary, followed by one blank line, and then -one function defintion below it only. - -Inside @file{centos-art.sh} script functions, top commentaries have -the following components: the functionality description, one-line for -copyright note with your personal information, the license under -which the function source code is released ---the @file{centos-art.sh} -script is released as GPL, so do all its functions---, the @code{$Id$} -keyword of Subversion is later expanded by @command{svn propset} -command. - -In our @code{greet} function example, top commentary for -@file{greet.sh} function script would look like the following: - -@verbatim -#!/bin/bash -# -# greet.sh -- This function outputs different kind of greetings to -# your screen. Use this function to understand how centos-art.sh -# script specific functionalities work. -# -# Copyright (C) YEAR YOURFULLNAME -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -# General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 -# USA. -# -# ---------------------------------------------------------------------- -# $Id$ -# ---------------------------------------------------------------------- -@end verbatim - -After top commentary, separated by one blank line, the @code{greet} -function definition would look like the following: - -@verbatim -function greet { - - # Define global variables. - - # Define command-line interface. - greet_getActions - -} -@end verbatim - -The first definition inside @code{greet} function, are global -variables that will be available along @code{greet} function execution -environment. This time we didn't use global variable definitions for -@code{greet} function execution environment, so we left that section -empty. - -Later, we call @code{greet_getActions} function to define the -command-line interface of @code{greet} functionality. The command-line -interface of @code{greet} functionality defines what and how actions -are performed, based on arguments combination passed to -@file{centos-art.sh} script. - -@verbatim -function greet_getActions { - - case "$ACTIONNAM" in - - --hello ) - greet_doHello - ;; - - --bye ) - greet_doBye - ;; - - * ) - cli_printMessage "`gettext "The option provided is not valid."`" - cli_printMessage "$(caller)" 'AsToKnowMoreLine' - - esac - -} -@end verbatim - -The @var{ACTIONNAM} global variable is defined in @file{cli.sh} -function script and contains the value passed before the equal sign -(i.e., @samp{=}) in the second command-line argument of -@file{centos-art.sh} script. For example, if the second command-line -argument is @option{--hello='World'}, the value of @var{ACTIONNAM} -variable would be @samp{--hello}. Using this configuration let us -deside which action to perform based on the action name passed to -@file{centos-art.sh} script as second argument. - -The @code{greet} function definition makes available two valid -greetings through @option{--hello} and @option{--bye} options. If no -one of them is provided as second command-line argument, the @samp{*} -case is evaluated instead. - -The @samp{*} case and its two lines further on should always be -present in @file{_getActions.sh} function scripts, no matter what -specific functionality you are creating. This convenction helps the -user to find out documentation about current functionality in use, -when no valid action is provided. - -The @code{greet_doHello} and @code{greet_doBye} function definitions -are the core of @code{greet} specific functionality. In such function -definitions we set what our @code{greet} function really does: to -output different kinds of greetings. - -@verbatim -function greet_doHello { - - cli_printMessage "`gettext "Hello"` $ACTIONVAL" - -} -@end verbatim - -The @code{greet_doHello} function definition is stored in -@file{greet_doHello.sh} function script. - -@verbatim -function greet_doBye { - - cli_printMessage "`gettext "Goodbye"` $ACTIONVAL" - -} -@end verbatim - -The @code{greet_doBye} function definition is stored in the -@file{greet_doBye.sh} function script. - -Both @file{greet_doHello.sh} and @file{greet_doBye.sh} function -scripts are stored inside @code{greet} function directory path (i.e. -@file{trunk/Scripts/Bash/Functions/Greet}). - -The @var{ACTIONVAL} global variable is defined in @file{cli.sh} -function script and contains the value passed after the equal sign -(i.e., @samp{=}) in the second command-line argument of -@file{centos-art.sh} script. For example, if the second command-line -argument is @option{--hello='World'}, the value of @var{ACTIONVAL} -variable would be @samp{World} without quotes. - -Let's see how @code{greet} specific functionality files are organzied -under @code{greet} function directory. To see file organization we use -the @command{tree} command: - -@verbatim -trunk/Scripts/Bash/Functions/Greet -|-- greet_doBye.sh -|-- greet_doHello.sh -|-- greet_getActions.sh -`-- greet.sh -@end verbatim - -To try the @code{greet} specific functionality we've just created, -pass the function name (i.e., @samp{greet}) as first argument to -@file{centos-art.sh} script, and any of the valid options as second -argument. Some examples are illustrated below: - -@verbatim -[centos@projects ~]$ centos-art greet --hello='World' -Hello World -[centos@projects ~]$ centos-art greet --bye='World' -Goodbye World -[centos@projects ~]$ -@end verbatim - -The word @samp{World} in the examples above can be anything. In fact, -change it to have a little fun. - -Now that we have a specific function that works as we expect, it is -time to document it. To document @code{greet} specific functionality, -we use its directory path and the @code{manual} functionality -(--- @strong{Removed}(pxref:trunk Scripts Bash Functions Manual) ---) of @file{centos-art.sh} -script, just as the following command illustrates: - -@verbatim -centos-art manual --edit=trunk/Scripts/Bash/Functions/Greet -@end verbatim - -To have a well documented function helps user to understand how your -function really works, and how it should be used. When no valid -action is passed to a function, the @file{centos-art.sh} script uses -the function documentation entry as vehicle to communicate which the -valid functions are. When no documentation entry exists for a -function, the @file{centos-art.sh} script informs that no -documentation entry exists for such function and requests user to -create it right at that time. - -Now that we have documented our function, it is time to translate its -output messages to different languages. To translate specific -functionality output messages to different languages we use the -@code{locale} functionality (--- @strong{Removed}(pxref:trunk Scripts Bash Functions -Locale) ---) of @file{centos-art.sh} script, just as the following command -illustrates: - -@verbatim -centos-art locale --edit -@end verbatim - -@quotation -@strong{Warning} To translate output messages in different languages, -your system locale information ---as in @env{LANG} environment -variable--- must be set to that locale you want to produce translated -messages for. For example, if you want to produce translated messages -for Spanish language, your system locale information must be set to -@samp{es_ES.UTF-8}, or similar, first. -@end quotation - -Well, it seems that our example is rather complete by now. - -In @code{greet} function example we've described so far, we only use -@command{cli_printMessage} global function in action specific function -definitions in order to print messages, but more interesting things -can be achieved inside action specific function definitions. For -example, if you pass a directory path as action value in second -argument, you could retrive a list of files from therein, and process -them. If the list of files turns too long or you just want to control -which files to process, you could add the third argument in the form -@option{--filter='regex'} and reduce the amount of files to process -using a regular expression pattern. - -The @code{greet} function described in this section may serve you as -an introduction to understand how specific functionalities work inside -@file{centos-art.sh} script. With some of luck this introduction will -also serve you as motivation to create your own @file{centos-art.sh} -script specific functionalities. - -By the way, the @code{greet} functionality doesn't exist inside -@file{centos-art.sh} script yet. Would you like to create it? - -@subsection Usage - -@subsubsection Global variables - -The following global variables of @file{centos-art.sh} script, are -available for you to use inside specific functions: - -@defvar TEXTDOMAIN -Default domain used to retrieve translated messages. This value is set -in @file{initFunctions.sh} and shouldn't be changed. -@end defvar - -@defvar TEXTDOMAINDIR -Default directory used to retrieve translated messages. This value is -set in @file{initFunctions.sh} and shouldn't be changed. -@end defvar - -@defvar FUNCNAM -Define function name. - -Function names associate sets of actions. There is one set of actions -for each unique function name inside @file{centos-art.sh} script. - -Dunction names are passed as first argument in @file{centos-art.sh} -command-line interface. For example, in the command @samp{centos-art -render --entry=path/to/dir --filter=regex}, the @var{ACTION} passed to -@file{centos-art.sh} script is @option{render}. - -When first argument is not provided, the @file{centos-art.sh} script -immediatly ends its execution. -@end defvar - -@defvar FUNCDIR -@end defvar - -@defvar FUNCDIRNAME -@end defvar - -@defvar FUNCSCRIPT -@end defvar - -@defvar FUNCCONFIG -@end defvar - -@defvar ACTIONNAM -Define action name. - -Each action name identifies an specific action to perform, inside an -specific function. - -Action name names aare passed as second argument in -@file{centos-art.sh} command-line interface. For example, in the -command @samp{centos-art render --entry=path/to/dir --filter=regex}, -the @var{ACTIONNAM} passed to @file{centos-art.sh} script is -@option{--entry}. - -When second argument is not provided, the @file{centos-art.sh} script -immediatly ends its execution. -@end defvar - -@defvar ACTIONVAL -Define action value. - -Action values are associated to just one action name. Action values -contain the working copy entry over which its associated action will be -performed in. Working copy entries can be files or directories inside -the working copy. -@end defvar - -@defvar REGEX -Define regular expression used as pattern to build the list of files -to process. - -By default, @var{REGEX} variable is set to @code{.+} to match all -files. - -Functions that need to build a list of files to process use the option -@option{--filter} to redefine @var{REGEX} variable default value, and -so, control the amount of files to process. -@end defvar - -@defvar ARGUMENTS -Define optional arguments. - -Optional arguments, inside @file{centos-art.sh} script, are considered -as all command-line arguments passed to @file{centos-art.sh} script, -from third argument position on. For example, in the command -@samp{centos-art render --entry=path/to/dir --filter=regex} , the -optional arguments are from @samp{--filter=regex} argument on. - -Optional arguments are parsed using @command{getopt} command through -the following base construction: - -@verbatim -# Define short options we want to support. -local ARGSS="" - -# Define long options we want to support. -local ARGSL="filter:,to:" - -# Parse arguments using getopt(1) command parser. -cli_doParseArguments - -# Reset positional parameters using output from (getopt) argument -# parser. -eval set -- "$ARGUMENTS" - -# Define action to take for each option passed. -while true; do - case "$1" in - --filter ) - REGEX="$2" - shift 2 - ;; - --to ) - TARGET="$2" - shift 2 - ;; - * ) - break - esac -done -@end verbatim - -Optional arguments provide support to command options inside -@file{centos-art.sh} script. For instance, consider the Subversion -(@command{svn}) command, where there are many options (e.g., -@option{copy}, @option{delete}, @option{move}, etc), and inside each -option there are several modifiers (e.g., @samp{--revision}, -@samp{--message}, @samp{--username}, etc.) that can be combined one -another in their short or long variants. - -The @var{ARGUMENTS} variable is used to store arguments passed from -command-line for later use inside @file{centos-art.sh} script. Storing -arguments is specially useful when we want to run a command with some -specific options from them. Consider the following command: - -@verbatim -centos-art path --copy=SOURCE --to=TARGET --message="The commit message goes here." --username='johndoe' -@end verbatim - -In the above command, the @option{--message}, and @option{--username} -options are specific to @command{svn copy} command. In such cases, -options are not interpreted by @file{centos-art.sh} script itself. -Instead, the @file{centos-art.sh} script uses @command{getopt} to -retrive them and store them in the @var{ARGUMENTS} variable for later -use, as described in the following command: - -@verbatim -# Build subversion command to duplicate locations inside the -# workstation. -eval svn copy $SOURCE $TARGET --quiet $ARGUMENTS -@end verbatim - -When @command{getopt} parses @var{ARGUMENTS}, we may use short options -(e.g., @option{-m}) or long options (e.g., @option{--message}). When -we use short options, arguments are separated by one space from the -option (e.g., @option{-m 'This is a commit message.'}). When we use -long options arguments are separated by an equal sign (@samp{=}) -(e.g., @option{--message='This is a commit message'}). - -In order for @command{getopt} to parse @var{ARGUMENTS} correctly, it -is required to provide the short and long definition of options that -will be passed or at least supported by the command performing the -final action the function script exists for. - -As convenction, inside @file{centos-art.sh} script, short option -definitions are set in the @var{ARGSS} variable; and long option -definitions are set in the @var{ARGSL} variable. - -When you define short and long options, it may be needed to define -which of these option arguments are required and which not. To define -an option argument as required, you need to set one colon @samp{:} -after the option definition (e.g., @option{-o m: -l message:}). On -the other hand, to define an option argument as not required, you need -to set two colons @samp{::} after the option definition (e.g., -@option{-o m:: -l message::}). -@end defvar - -@defvar EDITOR -Default text editor. - -The @file{centos-art.sh} script uses default text @env{EDITOR} to edit -pre-commit subversion messages, translation files, configuration -files, script files, and similar text-based files. - -If @env{EDITOR} environment variable is not set, @file{centos-art.sh} -script uses @file{/usr/bin/vim} as default text editor. Otherwise, the -following values are recognized by @file{centos-art.sh} script: - -@itemize -@item @file{/usr/bin/vim} -@item @file{/usr/bin/emacs} -@item @file{/usr/bin/nano} -@end itemize - -If no one of these values is set in @env{EDITOR} environment variable, -@file{centos-art.sh} uses @file{/usr/bin/vim} text editor by default. -@end defvar - -@subsubsection Global functions - -Function scripts stored directly under -@file{trunk/Scripts/Bash/Functions/} directory are used to define -global functions. Global functions can be used inside action specific -functionalities and or even be reused inside themselves. This section -provides introductory information to global functions you can use -inside @file{centos-art.sh} script. - -@defun cli_checkActionArguments -Validate action value (@var{ACTIONVAL}) variable. - -The action value variable can take one of the following values: - -@enumerate -@item Path to one directory inside the local working copy, -@item Path to one file inside the local working copy, -@end enumerate - -If another value different from that specified above is passed to -action value variable, the @file{centos-art.sh} script prints an error -message and ends script execution. -@end defun - -@defun cli_checkFiles FILE [TYPE] -Verify file existence. - -@code{cli_checkFiles} receives a @var{FILE} absolute path and performs -file verification as specified in @var{TYPE}. When @var{TYPE} is not -specified, @code{cli_checkFiles} verifies @var{FILE} existence, no -matter what kind of file it be. If @var{TYPE} is specified, use one -of the following values: - -@table @option -@item d -@itemx directory -Ends script execution if @var{FILE} is not a directory. - -When you verify directories with cli_checkFiles, if directory doesn't -exist, @file{centos-art.sh} script asks you for confirmation in order -to create that directory. If you answer positively, -@file{centos-art.sh} script creates that directory and continues -script flows normally. Otherwise, if you answer negatively, -@file{centos-art.sh} ends script execution with an error and -documentation message. - -@item f -@item regular-file -Ends script execution if @var{FILE} is not a regular file. -@item h -@itemx symbolic-link -Ends script execution if @var{FILE} is not a symbolic link. -@item x -@itemx execution -Ends script execution if @var{FILE} is not executable. -@item fh -Ends script execution if @var{FILE} is neither a regular file nor a -symbolic link. -@item fd -Ends script execution if @var{FILE} is neither a regular file nor a -directory. -@item isInWorkingCopy -Ends script execution if @var{FILE} is not inside the working copy. -@end table - -As default behaviour, if @var{FILE} passes all verifications, -@file{centos-art.sh} script continues with its normal flow. -@end defun - -@defun cli_commitRepoChanges [LOCATION] - -Syncronize changes between repository and working copy. - -The @code{cli_commitRepoChanges} function brings changes from the -central repository down to the working copy---using @command{svn -update}---, checks the working copy changes---using @command{svn -status} command---, prints status report---using both @command{svn -update} and @command{svn status} commands output, and finally, commits -recent changes from the working copy up to the repository---using -@command{svn commit} command---. - -Previous to commit the working copy changes up to the central -repository, the @code{cli_commitRepoChanges} function asks you to -verify changes---using @command{svn diff} command---, and later, -another confirmation question is shown to be sure you really want to -commit changes up to central repository. - -If @var{LOCATION} argument is not specified, the value of -@var{ACTIONVAL} variable is used as reference instead. - -@float Figure, trunk/Scripts/Bash/Functions/cli_commitRepoChanges -@verbatim ----------------------------------------------------------------------- ---> Bringing changes from the repository into the working copy ---> Checking changes in the working copy ----------------------------------------------------------------------- -Added 0 file from the repository. -Deleted 0 file from the repository. -Updated 0 file from the repository. -Conflicted 0 file from the repository. -Merged 0 file from the repository. -Modified 4 files from the working copy. -Unversioned 0 file from the working copy. -Deleted 0 file from the working copy. -Added 0 file from the working copy. ----------------------------------------------------------------------- -@end verbatim -@caption{The @code{cli_commitRepoChanges} function output.} -@end float - -Call the @code{cli_commitRepoChanges} function before or/and after -calling functions that modify files or directories inside the working -copy as you may need to. -@end defun - -@defun cli_doParseArguments -Redefine arguments (@var{ARGUMENTS}) global variable using -@command{getopt} command output. For more information about how to use -@code{cli_doParseArguments} function, see @var{ARGUMENTS} variable -description above. -@end defun - -@defun cli_doParseArgumentsReDef $@@ -Initialize/reset arguments (@var{ARGUMENTS}) global variable using -positional parameters variable (@var{$@@}) as reference. - -When we work inside function definitions, positional parameters are -reset to the last function definition positional parameters. If you -need to redefine positional parameters from one specific function, you -need to call @code{cli_doParseArgumentsReDef} with the positional -parameters variable (@var{$@@}), set as first argument, to that -specific function you want to redefine positional parameters at. -@end defun - -@defun cli_getArguments - -Initialize function name (@var{FUNCNAM}), action name -(@var{ACTIONNAM}), and action value (@var{ACTIONVAL}) global -variables, using positional parameters passed in @var{$@@} variable. - -The @code{cli_getArguments} function is called from @code{cli.sh} -function script, using @code{cli} function positional parameters -(i.e., the positional parameters passed as arguments in the -command-line) as first function argument. - -Once command-line positional parameters are accesible to -@file{centos-art.sh} script execution evironment, -@code{cli_getArguments} uses regular expression to retrive -action variables from first and second argument. The first argument -defines the value used as function name (@var{FUNCNAM}), and the -second argument defines both values used as action name -(@var{ACTIONNAM}) and action value (@var{ACTIONVAL}), respectively. - -The first argument is a word in lower case. This word specifies the -name of the functionality you want to use (e.g., @samp{render} to -render images, @samp{manual} to work on documentation, and so on.) - -The second argument has a long option style (e.g., -@samp{--option=value}). The @samp{--option} represents the action name -(@var{ACTIONNAM}), and the characters inbetween the equal sign -(@samp{=}) and the first space character, are considered as the action -value (@var{ACTIONVAL}). In order to provide action values with space -characters inbetween you need to enclose action value with quotes like -in @samp{--option='This is long value with spaces inbetween'}. -Generally, action values are used to specify paths over which the -action name acts on. - -Once action related variables (i.e., @var{FUNCNAM}, @var{ACTIONNAM}, -and @var{ACTIONVAL}) are defined and validated, -@code{cli_getArguments} shifts the positional arguments to remove the -first two arguments passed (i.e., those used to retrive action related -variables) and redefine the arguments (@var{ARGUMENTS}) global -variable with the new positional parameters information. -@end defun - -@defun cli_getFunctions -Initialize funtionalities supported by @file{centos-art.sh} script. - -Functionalities supported by @file{centos-art.sh} script are organized -in functionality directories under -@file{trunk/Scripts/Bash/Functions/} directory. Each functionality -directory stores function scripts to the functionality such directory -was created for. Function scripts contain function definitions. -Function definitions contain several commands focused on achieving one -specific task only (i.e., the one such functionality was created for). - -In order for @file{centos-art.sh} script to recognize a functionality, -such functionality needs to be stored under -@file{trunk/Scripts/Bash/Functions/} in a directory written -capitalized (i.e., the whole name is written in lowercase except the -first character which is in uppercase). The directory where one -specific functionality is stored is known as the @samp{functionality -directory}. - -Inside each functionality directory, the functionalty itself is -implemented through function scripts. Function scripts are organized -in files independently one another and written in @samp{camelCase} -format with the function name as prefix. Separation between prefix -and description is done using underscore (@samp{_}) character. - -In order for @file{centos-art.sh} script to load functionalities -correctly, function definition inside function scripts should be set -using the @samp{function} reserved word, just as in the following -example: - -@verbatim -function prefix_doSomething { - - # Do something here... - -} -@end verbatim - -The above function definition is just a convenction we use, in order -to make identification of function names easier read and automate by -@file{centos-art.sh} script initialization commands, once -@file{centos-art.sh} script determines which functionality directory -to use. Specifically, in order to initialize and export functions, -@file{centos-art.sh} script executes all function scripts inside the -functionality directory, and later @command{grep} on them using a -regular expression pattern, where the @samp{function} reserved word is -used as reference to retrive the function names and export them to -@file{centos-art.sh} script execution environment, and so, make -function definitions ---from function scripts inside the functionality -directory--- available for further calls. - -If the functionality specified in the command-line first argument -doesn't have a functionality directory, @file{centos-art.sh} script -considers the functionality provided in the command-line as invalid -functionality and immediatly stops script execution with an error -message. - -In order to keep visual consistency among function scripts, please -consider using the following function script design model as template -for your own function scripts: - -@verbatim -#!/bin/bash -# -# prefix_doSomething.sh -- This function illustrates function scripts -# design model you can use to create your own function scripts inside -# centos-art.sh script. -# -# Copyright (C) YEAR YOURFULLNAME -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -# General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 -# USA. -# -# ---------------------------------------------------------------------- -# $Id$ -# ---------------------------------------------------------------------- - -function prefix_doSomething { - - # Do something here... - -} -@end verbatim -@end defun - -@defun cli_getCountryCodes [FILTER] -Output country codes supported by @file{centos-art.sh} script. - -The @code{cli_getCountryCodes} function outputs a list with country -codes as defined in ISO3166 standard. When @var{FILTER} is provided, -@code{cli_getCountryCodes} outputs country codes that match -@var{FILTER} regular expression pattern. -@end defun - -@defun cli_getCountryName [FILTER] -Outputs country name supported by @file{centos-art.sh} script. - -The @code{cli_getCountryName} function reads one language locale code -in the format LL_CC and outputs the name of its related country as in -ISO3166. If filter is specified, @code{cli_getCountryName} returns the -country name that matches the locale code specified in @var{FILTER}, -exactly. -@end defun - -@defun cli_getCurrentLocale -Output current locale used by @file{centos-art.sh} script. - -The @code{cli_getCurrentLocale} function uses @env{LANG} environment -variable to build a locale pattern that is later applied to -@code{cli_getLocales} function output in order to return the current -locale that @file{centos-art.sh} script works with. - -The current locale information, returned by -@code{cli_getCurrentLocale}, is output from more specific to less -specific. For example, if @samp{en_GB} locale exists in -@code{cli_getLocales} function output, the @samp{en_GB} locale would -take precedence before @samp{en} locale. - -Locale precedence selection is quite important in order to define the -locale type we use for message translations. For example, if -@samp{en_GB} is used, we are also saying that the common language -specification for English language (i.e., @samp{en}) is no longer -used. Instead, we are using English non-common country-specific -language specifications like @samp{en_AU}, @samp{en_BW}, @samp{en_GB}, -@samp{en_US}, etc., for message translations. - -Use @code{cli_getCurrentLocale} function to know what current locale -information to use inside @file{centos-art.sh} script. -@end defun - -@defun cli_getFilesList [LOCATION] -Output list of files to process. - -The @code{cli_getFilesList} function uses @var{LOCATION} variable as -source location to build a list of files just as specified by regular -expression (@var{REGEX}) global variable. Essentially, what the -@code{cli_getFilesList} function does is using @command{find} command -to look for files in the location (@var{LOCATION}) just as posix-egrep -regular expression (@var{REGEX}) specifies. - -If @var{LOCATION} is not specified when @code{cli_getFilesList} -function is called, the action value (@var{ACTIONVAL}) global variable -is used as location value instead. - -By default, if the regular expression (@var{REGEX}) global variable is -not redefined after its first definition in the @code{cli} function, -all files that match default regular expression value (i.e., -@samp{.+}) will be added to the list of files to process. Otherwise, -if you redefine the regular expression global variable after its first -definition in the @code{cli} function and before calling -@code{cli_getFilesList} function, the last value you specifed is used -instead. - -When you need to customize the regular expression (@var{REGEX}) global -variable value inside a function, do not redefine the global variable -(at least you be absolutly convinced you need to). Instead, set the -regular expression global variable as @samp{local} to the function you -need a customized regular expression value for. If we don't redefine -the regular expression global variable as local to the function, or -use another name for the regular expression variable (which is not -very convenient in order to keep the amount of names to remember low), -you may experiment undesired concantenation issues that make your -regular expression to be something different from that you expect them -to be, specially if the function where you are doing the variable -redefinition is called several times during the same script execution. - -As result, the @code{cli_getFilesList} re-defines the value of -@var{FILES} variable with the list of files the @command{find} command -returned. As example, consider the following construction: - -@verbatim -function prefix_doSomething { - - # Initialize the list of files to process. - local FILES='' - - # Initialize location. - local LOCATION=/home/centos/artwork/trunk/Identity/Themes/Models/Default - - # Re-define regular expression to match scalable vector graphic - # files only. Note how we use the global value of REGEX to build a - # new local REGEX value here. - local REGEX="${REGEX}.*\.(svgz|svg)" - - # Redefine list of files to process. - cli_getFilesList $LOCATION - - # Process list of files. - for FILE in $FILES;do - cli_printMessages "$FILE" 'AsResponseLine' - # Do something else here on... - done - -} -@end verbatim - -@end defun - -@defun cli_getLangCodes [FILTER] -Outputs language codes supported by @file{centos-art.sh} script. - -@code{cli_getLangCodes} function outputs a list of language codes as -defined in ISO639 standard. When @var{FILTER} is provided, -@code{cli_getLangCodes} outputs language codes that match @var{FILTER} -regular expression pattern. -@end defun - -@defun cli_getLangName [FILTER] -Outputs language names supported by @file{centos-art.sh} script. - -@code{cli_getLangName} function reads one language locale code in the -format LL_CC and outputs the language related name as in ISO639. If -filter is specified, @code{cli_getLangName} returns the language name -that matches the locale code specified in @var{FILTER}, exactly. -@end defun - -@defun cli_getLocales -Output locale codes supported by @file{centos-art.sh} script. - -Occasionally, you use @code{cli_getLocales} function to add locale -information in non-common country-specific language (@samp{LL_CC}) -format for those languages (e.g., @samp{bn_IN}, @samp{pt_BR}, etc.) -which locale differences cannot be solved using common language -specifications (@samp{LL}) into one unique common locale specification -(e.g., @samp{bn}, @samp{pt}, etc.). -@end defun - -@defun cli_getRepoName NAME TYPE -Sanitate file names. - -Inside @file{centos-art.sh} script, specific functionalities rely both -in @code{cli_getRepoName} and repository file system organization to -achieve their goals. Consider @code{cli_getRepoName} function as -central place to manage file name convenctions for other functions -inside @file{centos-art.sh} script. - -@quotation -@strong{Important} @code{cli_getRepoName} function doesn't verify file -or directory existence, for that purpose use @code{cli_checkFiles} -function instead. -@end quotation - -The @var{NAME} variable contains the file name or directory name you -want to sanitate. - -The @var{TYPE} variable specifies what type of sanitation you want to -perform on @var{NAME}. The @var{TYPE} can be one of the following -values: - -@table @option -@item d -@itemx directory -Sanitate directory @var{NAME}s. -@item f -@item regular-file -Sanitate regular file @var{NAME}s. -@end table - -Use @code{cli_getRepoName} function to sanitate file names and -directory names before their utilization. - -Use @code{cli_getRepoName} when you need to change file name -convenctions inside @file{centos-art.sh} script. - -When we change file name convenctions inside @code{cli_getRepoName} -what we are really changing is the way functions interpret repository -file system organization. Notice that when we change a file name -(e.g., a function name), it is necessary to update all files where -such file name is placed on. This may require a massive substitution -inside the repository, each time we change name convenctions in the -repository (--- @strong{Removed}(pxref:trunk Scripts Bash Functions Path) ---, for more -information). -@end defun - -@defun cli_getRepoStatus [LOCATION] -Request repository status. - -This function requests the status of a @var{LOCATION} inside the -working copy using the @command{svn status} command and returns the -first character in the output line, just as described in @command{svn -help status}. If @var{LOCATION} is not a regular file or a directory, -inside the working copy, the @file{centos-art.sh} script prints a -message and ends its execution. - -Use this function to perform verifications based a repository -@var{LOCATION} status. -@end defun - -@defun cli_getTemporalFile @var{NAME} -Output absolute path to temporal file @var{NAME}. - -The @code{cli_getTemporalFile} function uses @file{/tmp} directory as -source location to store temporal files, the @file{centos-art.sh} -script name, and a random identification string to let you run more -than one @file{centos-art.sh} script simultaneously on the same user -session. For example, due the following temporal file defintion: - -@verbatim -cli_getTemporalFile $FILE -@end verbatim - -If @var{FILE} name is @file{instance.svg} and the unique random string -is @samp{f16f7b51-ac12-4b7f-9e66-72df847f12de}, the final temporal -file, built from previous temporal file definition, would be: - -@verbatim -/tmp/centos-art.sh-f16f7b51-ac12-4b7f-9e66-72df847f12de-instance.svg -@end verbatim - -When you use the @code{cli_getTemporalFile} function to create -temporal files, be sure to remove temporal files created once you've -ended up with them. For example, consider the following construction: - -@verbatim -for FILE in $FILES;do - - # Initialize temporal instance of file. - INSTANCE=$(cli_getTemporalFile $FILE) - - # Do something ... - - # Remove temporal instance of file. - if [[ -f $INSTANCE ]];then - rm $INSTANCE - fi - -done -@end verbatim - -Use the @code{cli_getTemporalFile} function whenever you need to -create temporal files inside @file{centos-art.sh} script. -@end defun - -@defun cli_getThemeName -Output theme name. - -In order for @code{cli_getThemeName} function to extract theme name -correctly, the @var{ACTIONVAL} variable must contain a directory path -under @file{trunk/Identity/Themes/Motifs/} directory structure. -Otherwise, @code{cli_getThemeName} returns an empty string. -@end defun - -@defun cli_printMessage MESSAGE [FORMAT] -Define standard output message definition supported by -@file{centos-art.sh} script. - -When @var{FORMAT} is not specified, @code{cli_printMessage} outputs -information just as it was passed in @var{MESSAGE} variable. -Otherwise, @var{FORMAT} can take one of the following values: - -@table @option -@item AsHeadingLine -To print heading messages. -@verbatim ----------------------------------------------------------------------- -$MESSAGE ----------------------------------------------------------------------- -@end verbatim - -@item AsWarningLine -To print warning messages. -@verbatim ----------------------------------------------------------------------- -WARNING: $MESSAGE ----------------------------------------------------------------------- -@end verbatim - -@item AsNoteLine -To print note messages. -@verbatim ----------------------------------------------------------------------- -NOTE: $MESSAGE ----------------------------------------------------------------------- -@end verbatim - -@item AsUpdatingLine -To print @samp{Updating} messages on two-columns format. -@verbatim -Updating $MESSAGE -@end verbatim - -@item AsRemovingLine -To print @samp{Removing} messages on two-columns format. -@verbatim -Removing $MESSAGE -@end verbatim - -@item AsCheckingLine -To print @samp{Checking} messages on two-columns format. -@verbatim -Checking $MESSAGE -@end verbatim - -@item AsCreatingLine -To print @samp{Creating} messages on two-columns format. -@verbatim -Creating $MESSAGE -@end verbatim - -@item AsSavedAsLine -To print @samp{Saved as} messages on two-columns format. -@verbatim -Saved as $MESSAGE -@end verbatim - -@item AsLinkToLine -To print @samp{Linked to} messages on two-columns format. -@verbatim -Linked to $MESSAGE -@end verbatim - -@item AsMovedToLine -To print @samp{Moved to} messages on two-columns format. -@verbatim -Moved to $MESSAGE -@end verbatim - -@item AsTranslationLine -To print @samp{Translation} messages on two-columns format. -@verbatim -Translation $MESSAGE -@end verbatim - -@item AsConfigurationLine -To print @samp{Configuration} messages on two-columns format. -@verbatim -Configuration $MESSAGE -@end verbatim - -@item AsResponseLine -To print response messages on one-column format. -@verbatim ---> $MESSAGE -@end verbatim - -@item AsRequestLine -To print request messages on one-column format. Request messages -output messages with one colon (@samp{:}) and without trailing newline -(@samp{\n}) at message end. -@verbatim -$MESSAGE: -@end verbatim - -@item AsYesOrNoRequestLine -To print @samp{yes or no} request messages on one-column format. If -something different from @samp{y} is answered (when using -@code{en_US.UTF-8} locale), script execution ends immediatly. - -@verbatim -$MESSAGE [y/N]: -@end verbatim - -When we use @file{centos-art.sh} script in a locale different from -@code{en_US.UTF-8}, confirmation answer may be different from -@samp{y}. For example, if you use @code{es_ES.UTF-8} locale, the -confirmation question would look like: - -@verbatim -$MESSAGE [s/N]: -@end verbatim - -and the confirmation answer would be @samp{s}, as it is on Spanish -@samp{sí} word. - -Definition of which confirmation word to use is set on translation -messages for your specific locale information. --- @strong{Removed}(xref:trunk Scripts -Bash Functions Locale) ---, for more information about locale-specific -translation messages. - -@item AsToKnowMoreLine -To standardize @samp{to know more, run the following command:} -messages. When the @option{AsToKnowMoreLine} option is used, the -@var{MESSAGE} value should be set to @code{"$(caller)"}. @code{caller} -is a Bash builtin that returns the context of the current subroutine -call. @option{AsToKnowMoreLine} option uses @code{caller} builtin -output to build documentation entries dynamically. - -@verbatim ----------------------------------------------------------------------- -To know more, run the following command: -centos-art manual --read='path/to/dir' ----------------------------------------------------------------------- -@end verbatim - -Use @option{AsToKnowMoreLine} option after errors and for intentional -script termination. - -@item AsRegularLine -To standardize regular messages on one-column format. - -When @var{MESSAGE} contains a colon inside (e.g., @samp{description: -message}), the @code{cli_printMessage} function outputs @var{MESSAGE} -on two-columns format. -@end table - -Use @code{cli_printMessage} function whenever you need to output -information from @file{centos-art.sh} script. - -@quotation -@strong{Tip} To improve two-columns format, change the following file: -@verbatim -trunk/Scripts/Bash/Styles/output_forTwoColumns.awk -@end verbatim -@end quotation -@end defun - -@subsubsection Specific functions - -The following specific functions of @file{centos-art.sh} script, are -available for you to use: - -@menu -@comment --- Removed(* trunk Scripts Bash Functions Html::) --- -@comment --- Removed(* trunk Scripts Bash Functions Locale::) --- -@comment --- Removed(* trunk Scripts Bash Functions Manual::) --- -@comment --- Removed(* trunk Scripts Bash Functions Path::) --- -@comment --- Removed(* trunk Scripts Bash Functions Render::) --- -@comment --- Removed(* trunk Scripts Bash Functions Render Config::) --- -@comment --- Removed(* trunk Scripts Bash Functions Shell::) --- -@comment --- Removed(* trunk Scripts Bash Functions Svg::) --- -@comment --- Removed(* trunk Scripts Bash Functions Verify::) --- -@end menu - -@subsection See also - -@menu -* trunk Scripts Bash:: -@comment --- Removed(* trunk Scripts Bash Locale::) --- -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Help.texi b/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Help.texi deleted file mode 100644 index fb39647..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Help.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Html.texi b/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Html.texi deleted file mode 100644 index fb39647..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Html.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Locale.texi b/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Locale.texi deleted file mode 100644 index bf264c9..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Locale.texi +++ /dev/null @@ -1,85 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -This command looks for @samp{.sh} files inside Bash directory and -extracts translatable strings from files, using @command{xgettext} -command, in order to create a portable object template -(@file{centos-art.sh.pot}) file for them. - -With the @file{centos-art.sh.pot} file up to date, the -@command{centos-art} command removes the temporal list of files sotred -inside @file{/tmp} directory and checks the current language of your -user's session to create a portable object file for it, in the -location @file{$CLI_LANG/$CLI_LANG.po}. - -The @var{CLI_LANG} variable discribes the locale language used to -output messages inside @command{centos-art} command. The locale -language used inside @command{centos-art} command is taken from the -@env{LANG} environment variable. The @var{CLI_LANG} variable has the -@samp{LL_CC} format, where @samp{LL} is a language code from the -ISO-639 standard, and @samp{CC} a country code from the ISO-3166 -standard. - -The @env{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 @env{LANG} -environment variable to the correct value. On the other side, if you -are using a text session edit your @file{~/.bash_profile} file to set -and export the @env{LANG} environment variable to your native locale -as defines the @command{locale -a} command output; do logout, and do -login again. - -At this point, the @env{LANG} environment variable has the appropriate -value you need, in order to translate @command{centos-art.sh} messages -to your native language (the one set in @env{LANG} environment -variable). - -With the @file{$CLI_LANG/$CLI_LANG.po} file up to date, the -@command{centos-art} opens it for you to update translation strings. -The @command{centos-art} command uses the value of @var{EDITOR} -environment variable to determine your favorite text editor. If no -value is defined on @var{EDITOR}, the @file{/usr/bin/vim} text editor -is used as default. - -When you finishd PO file edition and quit text editor, the -@command{centos-art} command creates the related machine object in the -location @file{$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 @command{centos-art.sh} script. - -In order to make the @command{centos-art.sh} internationalization, the -@command{centos-art.sh} script was modified as described in the -@command{gettext} info documentation (@command{info gettext}). You -can find such modifications in the following files: - -@itemize -@item @file{trunk/Scripts/Bash/initFunctions.sh} -@item @file{trunk/Scripts/Bash/Functions/Help/cli_localeMessages.sh} -@item @file{trunk/Scripts/Bash/Functions/Help/cli_localeMessagesStatus.sh} -@end itemize - -@itemize -@item ... -@end itemize - -@subsection Usage - -@table @samp -@item centos-art locale --edit -Use this command to translate command-line interface output messages -in the current system locale you are using (as specified in @env{LANG} -environment variable). -@item centos-art locale --list -Use this command to see the command-line interface locale report. -@end table - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Manual.texi b/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Manual.texi deleted file mode 100644 index fb39647..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Manual.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Path.texi b/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Path.texi deleted file mode 100644 index a7c6c55..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Path.texi +++ /dev/null @@ -1,327 +0,0 @@ -@subsection Goals - -This section exists to organize files related to @code{path} -functiontionality. The @code{path} functionality standardizes -movement, syncronization, branching, tagging, and general file -maintainance inside the repository. - -@subsection Description - -@emph{''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.''} - -@subsubsection Repository layout - -The repository layout describes organization of files and directories -inside the repository. The repository layout provides the standard -backend required for automation scripts to work correctly. If such -layout changes unexpectedly, automation scripts may confuse themselves -and stop doing what we expect from them to do. - -As convenction, inside CentOS Artwork Repository, we organize files -and directories related to CentOS corporate visual identity under -three top level directories named: @file{trunk/}, @file{branches/}, -and @file{tags/}. - -The @file{trunk/} directory (@pxref{trunk}) organizes the main -development line of CentOS corporate visual identity. Inside -@file{trunk/} directory structure, the CentOS corporate visual -identity concepts are implemented using directories. There is one -directory level for each relevant concept inside the repository. The -@file{trunk/} directory structure is mainly used to perform -development tasks related to CentOS corporate visual identity. - -The @file{branches/} directory (@pxref{branches}) oranizes parallel -development lines to @file{trunk/} directory. The @file{branches/} -directory is used to set points in time where develpment lines are -devided one from another taking separte and idependent lives that -share a common past from the point they were devided on. The -@file{branches/} directory is mainly used to perform quality assurance -tasks related to CentOS corporate visual identity. - -The @file{tags/} directory (@pxref{tags}) organizes parallel frozen -lines to @file{branches/} directory. The parallel frozen lines are -immutable, nothing change inside them once they has been created. The -@file{tags/} directory is mainly used to publish final releases of -CentOS corporate visual identity. - -The CentOS Artwork Repository layout is firmly grounded on a -Subversion base. Subversion (@url{http://subversion.tigris.org}) is a -version control system, which allows you to keep old versions of files -and directories (usually source code), keep a log of who, when, and -why changes occurred, etc., like CVS, RCS or SCCS. Subversion keeps a -single copy of the master sources. This copy is called the source -``repository''; it contains all the information to permit extracting -previous versions of those files at any time. - -@subsubsection Repository name convenctions - -Repository name convenctions help us to maintain consistency of names -inside the repository. - -Repository name convenctions are applied to files and directories -inside the repository layout. As convenction, inside the repository -layout, file names are all written in lowercase -(@samp{01-welcome.png}, @samp{splash.png}, @samp{anaconda_header.png}, -etc.) and directory names are all written capitalized (e.g., -@samp{Identity}, @samp{Themes}, @samp{Motifs}, @samp{TreeFlower}, -etc.). - -Repository name convenctions are implemented inside the -@code{cli_getRepoName} function of @file{centos-art.sh} script. With -@code{cli_getRepoName} function we reduce the amount of commands and -convenctions to remember, concentrating them in just one single place -to look for fixes and improvements. - -@subsubsection Repository work flow - -Repository work flow describes the steps and time intervals used to -produce CentOS corporate visual identity inside CentOS Artwork -Repository. - -To illustrate repository work flow let's consider themes' development -cycle. - -Initially, we start working themes on their trunk development line -(e.g., @file{trunk/Identity/Themes/Motifs/TreeFlower/}), here we -organize information that cannot be produced automatically (i.e., -background images, concepts, color information, screenshots, etc.). - -Later, when theme trunk development line is considered ``ready'' for -implementation (e.g., all required backgrounds have been designed), -we create a branch for it (e.g., -@file{branches/Identity/Themes/Motifs/TreeFlower/1/}). Once the -branch has been created, we forget that branch and continue working -the trunk development line while others (e.g., an artwork quality -assurance team) test the new branch for tunning it up. - -Once the branch has been tunned up, and considered ``ready'' for -release, it is freezed under @file{tags/} directory (e.g., -@file{tags/Identity/Themes/Motifs/TreeFower/1.0/}) for packagers, -webmasters, promoters, and anyone who needs images from that CentOS -theme the tag was created for. - -Both branches and tags, inside CentOS Artwork Repository, use -numerical values to identify themselves under the same location. -Branches start at one (i.e., @samp{1}) and increment one unit for each -branch created from the same trunk development line. Tags start at -zero (i.e., @samp{0}) and increment one unit for each tag created from -the same branch development line. - -@quotation -@strong{Convenction} Do not freeze trunk development lines using tags -directly. If you think you need to freeze a trunk development line, -create a branch for it and then freeze that branch instead. -@end quotation - -The trunk development line may introduce problems we cannot see -immediatly. Certainly, the high changable nature of trunk development -line complicates finding and fixing such problems. On the other hand, -the branched development lines provide a more predictable area where -only fixes/corrections to current content are commited up to -repository. - -If others find and fix bugs inside the branched development line, we -could merge such changes/experiences back to trunk development line -(not visversa) in order for future branches, created from trunk, to -benefit. - -Time intervals used to create branches and tags may vary, just as -different needs may arrive. For example, consider the release schema -of CentOS distribution: one major release every 2 years, security -updates every 6 months, support for 7 years long. Each time a CentOS -distribution is released, specially if it is a major release, there is -a theme need in order to cover CentOS distribution artwork -requirements. At this point, is where CentOS Artwork Repository comes -up to scene. - -Before releasing a new major release of CentOS distribution we create -a branch for one of several theme development lines available inside -the CentOS Artwork Repository, perform quality assurance on it, and -later, freeze that branch using tags. Once a the theme branch has been -frozen (under @file{tags/} directory), CentOS Packagers (the persons -whom build CentOS distribution) can use that frozen branch as source -location to fulfill CentOS distribution artwork needs. The same -applies to CentOS Webmasters (the persons whom build CentOS websites), -and any other visual manifestation required by the project. - -@subsubsection Parallel directories - -Inside CentOS Artwork Repository, parallel directories are simple -directory entries built from a common parent directory and placed in a -location different to that, the common parent directory is placed on. -Parallel directories are useful to create branches, tags, -translations, documentation, pre-rendering configuration script, and -similar directory structures. - -Parallel directories take their structure from one unique parent -directory. Inside CentOS Artwork Repository, this unique parent -directory is under @file{trunk/Identity} location. The -@file{trunk/Identity} location must be considered the reference for -whatever information you plan to create inside the repository. - -In some circumstances, parallel directories may be created removing -uncommon information from their paths. Uncommon path information -refers to those directory levels in the path which are not common for -other parallel directories. For example, when rendering -@file{trunk/Identity/Themes/Motifs/TreeFlower/Distro} directory -structure, the @file{centos-art.sh} script removes the -@file{Motifs/TreeFlower/} directory levels from path, in order to -build the parallel directory used to retrived translations, and -pre-rendering configuration scripts required by @code{render} -functionality. - -Another example of parallel directory is the documentation structure -created by @code{manual} functionality. This time, -@file{centos-art.sh} script uses parallel directory information with -uncommon directory levels to build the documentation entry required by -Texinfo documentation system, inside the repository. - -Othertimes, parallel directories may add uncommon information to their -paths. This is the case we use to create branches and tags. When we -create branches and tags, a numerical identifier is added to parallel -directory structure path. The place where the numerical identifier is -set on is relevant to corporate visual identity structure and should -be carefully considered where it will be. - -When one parent directory changes, all their related parallel -directories need to be changed too. This is required in order for -parallel directories to retain their relation with the parent -directory structure. In the other hand, parallel directories should -never be modified under no reason but to satisfy the relation to their -parent directory structure. Liberal change of parallel directories -may suppresses the conceptual idea they were initially created for; -and certainly, things may stop working the way they should do. - -@subsubsection Syncronizing path information - -Parallel directories are very useful to keep repository organized but -introduce some complications. For instance, consider what would -happen to functionalities like @code{manual} (@samp{trunk Scripts Bash -Functions Manual}) that rely on parent directory structures to create -documentation entries (using parallel directory structures) if one of -those parent directory structures suddenly changes after the -documentation entry has been already created for it? - -In such cases, functionalities like @code{manual} may confuse -themselves if path information is not updated to reflect the relation -with its parent directory. Such functionalities work with parent -directory structure as reference; if a parent directory changes, the -functionalities dont't even note it because they work with the last -parent directory structure available in the repository, no matter what -it is. - -In the specific case of documentation (the @code{manual} -functionality), the problem mentioned above provokes that older parent -directories, already documented, remain inside documentation directory -structures as long as you get your hands into the documentation -directory structure (@file{trunk/Manuals}) and change what must be -changed to match the new parent directory structure. - -There is no immediate way for @code{manual}, and similar -functionalities that use parent directories as reference, to know when -and how directory movements take place inside the repository. Such -information is available only when the file movement itself takes -place inside the repository. So, is there, at the moment of moving -files, when we need to syncronize parallel directories with their -unique parent directory structure. - -@quotation -@strong{Warning} There is not support for URL reference inside -@file{centos-art.sh} script. The @file{centos-art.sh} script is -designed to work with local files inside the working copy only. -@end quotation - -As CentOS Artwork Repository is built over a version control system, -file movements inside the repository are considered repository -changes. In order for these repository changes to be versioned, we -need to, firstly, add changes into the version control system, commit -them, and later, perform movement actions using version control system -commands. This configuration makes possible for everyone to know about -changes details inside the repository; and if needed, revert or update -them back to a previous revision. - -Finally, once all path information has been corrected, it is time to -take care of information inside the files. For instance, considere -what would happen if you make a reference to a documentation node, and -later the documentation node you refere to is deleted. That would make -Texinfo to produce error messages at export time. So, the -@file{centos-art.sh} script needs to know when such changes happen, in -a way they could be noted and handled without producing errors. - -@subsubsection What is the right place to store it? - -Occasionly, you may find that new corporate visual identity components -need to be added to the repository. If that is your case, the first -question you need to ask yourself, before start to create directories -blindly all over, is: What is the right place to store it? - -The CentOS Community different free support vains (see: -@url{http://wiki.centos.org/GettingHelp}) are the best place to find -answers to your question, but going there with hands empty is not good -idea. It may give the impression you don't really care about. Instead, -consider the following suggestions to find your own comprehension and -so, make your propositions based on it. - -When we are looking for the correct place to store new files, to bear -in mind the corporate visual identity structure used inside the CentOS -Artwork Repository (@pxref{trunk Identity}) would be probaly the best -advice we could offer, the rest is just matter of choosing appropriate -names. To illustrate this desition process let's consider the -@file{trunk/Identity/Themes/Motifs/TreeFlower} directory as example. -It is the trunk development line of @emph{TreeFlower} artistic motif. -Artistic motifs are considered part of themes, which in turn are -considered part of CentOS corporate visual identity. - -When building parent directory structures, you may find that reaching -an acceptable location may take some time, and as it uses to happen -most of time; once you've find it, that may be not a definite -solution. There are many concepts that you need to play with, in -order to find a result that match the conceptual idea you try to -implement in the new directory location. To know which these concepts -are, split the location in words and read its documentation entry from -less specific to more specific. - -For example, the @file{trunk/Identity/Themes/Motifs/TreeFlower} -location evolved through several months of contant work and there is -no certain it won't change in the future, even it fixes quite well the -concept we are trying to implement. The concepts used in -@file{trunk/Identity/Themes/Distro/Motifs/TreeFlower} location are -described in the following commands, respectively: - -@verbatim -centos-art manual --read=turnk/ -centos-art manual --read=turnk/Identity/ -centos-art manual --read=turnk/Identity/Themes/ -centos-art manual --read=turnk/Identity/Themes/Motifs/ -centos-art manual --read=turnk/Identity/Themes/Motifs/TreeFlower/ -@end verbatim - -Other location concepts can be found similary as we did above, just -change the location we used above by the one you are trying to know -concepts for. - -@subsection Usage - -@table @command -@item centos-art path --copy='SRC' --to='DST' - -Copy @option{SRC} to @option{DST} and schedule @option{DST} for -addition (with history). In this command, @file{SRC} and @file{DST} -are both working copy (WC) entries. - -@item centos-art path --delete='SRC' - -Delete @option{DST}. In order for this command to work the file or -directory you intend to delete should be under version control first. -In this command, @file{SRC} is a working copy (WC) entry. - -@end table - -@subsection See also - -@menu -* trunk Scripts Bash:: -@comment --- Removed(* trunk Scripts Bash Functions::) --- -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Render.texi b/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Render.texi deleted file mode 100644 index 7dfe2c5..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Render.texi +++ /dev/null @@ -1,736 +0,0 @@ -The @code{render} functionality exists to produce both identity and -translation files on different levels of information (i.e., different -languages, release numbers, architectures, etc.). - -The @code{render} functionality relies on ``renderable directory -structures'' to produce files. Renderable directory structures can be -either ``identity directory structures'' or ``translation directory -structures'' with special directories inside. - -@subsection Renderable identity directory structures - -Renderable identity directory structures are the starting point of -identity rendition. Whenever we want to render a component of CentOS -corporate visual identity, we need to point @file{centos-art.sh} to a -renderable identity directory structure. If such renderable identity -directory structure doesn't exist, then it is good time to create it. - -Inside the working copy, one renderable identity directory structures -represents one visual manifestation of CentOS corporate visual -identity, or said differently, each visual manifestation of CentOS -corporate visual identity should have one renderable identity -directory structure. - -Inside renderable identity directory structures, @file{centos-art.sh} -can render both image-based and text-based files. Specification of -whether a renderable identity directory structure produces image-based -or text-based content is a configuration action that takes place in -the pre-rendition configuration script of that renderable identity -directory structure. - -Inside renderable identity directory structures, content production is -organized in different configurations. A content production -configuration is a unique combination of the components that make an -identity directory structure renderable. One content production -configuration does one thing only (e.g., to produce untranslated -images), but it can be extended (e.g., adding translation files) to -achieve different needs (e.g., to produce translated images). - -@subsubsection Design template without translation - -The design template without translation configuration is based on a -renderable identity directory structure with an empty translation -directory structure. In this configuration, one design template -produces one untranslated file. Both design templates and final -untranslated files share the same file name, but they differ one -another in file-type and file-extension. - -For example, to produce images without translations (there is no much -use in producing text-based files without translations), consider the -following configuration: - -@table @strong -@item One renderable identity directory structure: - -In this example we used @file{Identity/Path/To/Dir} as the identity -component we want to produce untranslated images for. Identity -components can be either under @file{trunk/} or @file{branches/} -directory structure. - -The identity component (i.e., @file{Identity/Path/To/Dir}, in this -case) is also the bond component we use to connect the identity -directory structures with their respective auxiliar directories (i.e., -translation directory structres and pre-rendition configuration -structures). The bond component is the path convenction that -@file{centos-art.sh} uses to know where to look for related -translations, configuration scripts and whatever auxiliar thing a -renderable directory structure may need to have. - -@verbatim - | The bond component - |----------------->| -trunk/Identity/Path/To/Dir <-- Renderable identity directory structure. -|-- Tpl <-- Design template directory. -| `-- file.svg <-- Design template file. -`-- Img <-- Directory used to store final files. - `-- file.png <-- Final image-based file produced from - design template file. -@end verbatim - -Inside design template directory, design template files are based on -@acronym{SVG,Scalable Vector Graphics} and use the extension -@code{.svg}. Design template files can be organized using several -directory levels to create a simple but extensible configuration, -specially if translated images are not required. - -In order for @acronym{SVG,Scalable Vector Graphics} files to be -considered ``design template'' files, they should be placed under the -design template directory and to have set a @code{CENTOSARTWORK} -object id inside. - -The @code{CENTOSARTWORK} word itself is a convenction name we use to -define which object/design area, inside a design template, the -@file{centos-art.sh} script will use to export as -@acronym{PNG,Portable Network Graphic} image at rendition time. -Whithout such object id specification, the @file{centos-art.sh} script -cannot know what object/design area you (as designer) want to export -as @acronym{PNG,Portable Network Graphic} image file. - -@quotation -@strong{Note} At rendition time, the content of @file{Img/} directory -structure is produced by @file{centos-art.sh} automatically. -@end quotation - -When a renderable identity directory structure is configured to -produce image-based content, @file{centos-art.sh} produces -@acronym{PNG,Portable Network Graphics} files with the @code{.png} -extension. Once the base image format has been produced, it is -possible for @file{centos-art.sh} to use it in order to automatically -create other image formats that may be needed (--- @strong{Removed}(pxref:trunk Scripts -Bash Functions Render Config) ---). - -Inside the working copy, you can find an example of ``design template -without translation'' configuration at @file{trunk/Identity/Models/}. - -@xref{trunk Identity}, for more information. - -@item One translation directory structure: - -In order for an identity entry to be considered an identity renderable -directory structure, it should have a translation entry. The content -of the translation entry is relevant to determine how to process the -identity renderable directory entry. - -If the translation entry is empty (i.e., there is no file inside it), -@file{centos-art.sh} interprets the identity renderable directory -structure as a ``design templates without translation'' configuration. - -@verbatim - | The bond component - |----------------->| -trunk/Translations/Identity/Path/To/Dir -`-- (empty) -@end verbatim - -If the translation entry is not empty, @file{centos-art.sh} can -interpret the identity renderable directory structure as one of the -following configurations: ``design template with translation -(one-to-one)'' or ``design template with translation (optimized)''. -Which one of these configurations is used depends on the value -assigned to the matching list (@var{MATCHINGLIST}) variable in the -pre-rendition configuration script of the renderable identity -directory structure we are producing images for. - -If the matching list variable is empty (as it is by default), then -``design template with translation (one-to-one)'' configuration is -used. In this configuration it is required that both design templates -and translation files have the same file names. This way, @emph{one} -translation files is applied to @emph{one} design template, to produce -@emph{one} translated image. - -If the matching list variable is not empty (because you redefine it in -the pre-rendition configuration script), then ``design template with -translation (optimized)'' configuration is used instead. In this -configuration, design templates and translation files don't need to -have the same names since such name relationship between them is -specified in the matching list properly. - ---- @strong{Removed}(xref:trunk Translations) ---, for more information. - -@item One pre-rendition configuration script: - -In order to make an identity directory structure renderable, a -pre-rendition configuration script should exist for it. The -pre-rendition configuration script specifies what type of rendition -does @file{centos-art.sh} will perform over the identity directory -structure and how does it do that. - -@verbatim - | The bond component - |----------------->| -trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir -`-- render.conf.sh -@end verbatim - -In this configuration the pre-rendition configuration script -(@file{render.conf.sh}) would look like the following: - -@verbatim -function render_loadConfig { - - # Define rendition actions. - ACTIONS[0]='BASE:renderImage' - -} -@end verbatim - -Since translation directory structure is empty, @file{centos-art.sh} -assumes a ``design template without translation'' configuration to -produce untranslated images. - -To produce untranslated images, @file{centos-art.sh} takes one design -template and creates one temporal instance from it. Later, -@file{centos-art.sh} uses the temporal design template instance as -source file to export the final untranslated image. The action of -exporting images from @acronym{SVG,Scalable Vector Graphics} to -@acronym{PNG,Portable Network Graphics} is possible thanks to -Inkscape's command-line interface and the @code{CENTOSARTWORK} object -id we previously set inside design templates. - -@verbatim -centos-art.sh render --identity=trunk/Identity/Path/To/Dir -------------------------------------------------- -0 | Execute centos-art.sh on renderable identity directory structure. ---v---------------------------------------------- -trunk/Identity/Path/To/Dir/Tpl/file.svg -------------------------------------------------- -1 | Create instance from design template. ---v---------------------------------------------- -/tmp/centos-art.sh-a07e824a-5953-4c21-90ae-f5e8e9781f5f-file.svg -------------------------------------------------- -2 | Render untranslated image from design template instance. ---v---------------------------------------------- -trunk/Identity/NewDir/Img/file.png -------------------------------------------------- -3 | Remove design template instance. -@end verbatim - -Finally, when the untranslated image has been created, the temporal -design template instance is removed. At this point, -@file{centos-art.sh} takes the next design template and repeats the -whole production flow once again (design template by design template), -until all design templates be processed. - ---- @strong{Removed}(xref:trunk Scripts Bash Functions Render Config) ---, for more -information. -@end table - -@subsubsection Design template with translation (one-to-one) - -Producing untranslated images is fine in many cases, but not always. -Sometimes it is required to produce images in different languages and -that is something that untrasnlated image production cannot achieve. -However, if we fill its empty translation entry with translation files -(one for each design template) we extend the production flow from -untranslated image production to translated image production. - -In order for @file{centos-art.sh} to produce images correctly, each -design template should have one translation file and each translation -file should have one design template. Otherwise, if there is a -missing design template or a missing translation file, -@file{centos-art.sh} will not produce the final image related to the -missing component. - -In order for @file{centos-art.sh} to know which is the relation -between translation files and design templates the translation -directory structure is taken as reference. For example, the -@file{trunk/Translations/Identity/Path/To/Dir/file.sed} translation -file does match @file{trunk/Identity/Path/To/Dir/Tpl/file.svg} design -template, but it doesn't match -@file{trunk/Identity/Path/To/Dir/File.svg} or -@file{trunk/Identity/Path/To/Dir/Tpl/File.svg} or -@file{trunk/Identity/Path/To/Dir/Tpl/SubDir/file.svg} design -templates. - -The pre-rendition configuration script used to produce untranslated -images is the same we use to produce translated images. There is no -need to modify it. So, as we are using the same pre-rendition -configuration script, we can say that translated image production is -somehow an extended/improved version of untranslated image production. - -@quotation -@strong{Note} If we use no translation file in the translation entry -(i.e., an empty directory), @file{centos-art.sh} assumes the -untranslated image production. If we fill the translation entry with -translation files, @file{centos-art.sh} assumes the translated image -production. -@end quotation - -To produce final images, @file{centos-art.sh} applies one translation -file to one design template and produce a translated design template -instance. Later, @file{centos-art.sh} uses the translated template -instance to produce the translated image. Finally, when the translated -image has been produced, @file{centos-art.sh} removes the translated -design template instance. This production flow is repeated for each -translation file available in the translatio entry. - -@verbatim -centos-art.sh render --identity=trunk/Identity/Path/To/Dir -------------------------------------------------- -0 | Execute centos-art.sh on directory structure. ---v---------------------------------------------- -trunk/Translations/Identity/Path/To/Dir/file.sed -------------------------------------------------- -1 | Apply translation to design template. ---v---------------------------------------------- -trunk/Identity/Path/To/Dir/Tpl/file.svg -------------------------------------------------- -2 | Create design template instance. ---v---------------------------------------------- -/tmp/centos-art.sh-a07e824a-5953-4c21-90ae-f5e8e9781f5f-file.svg -------------------------------------------------- -3 | Render PNG image from template instance. ---v---------------------------------------------- -trunk/Identity/NewDir/Img/file.png -------------------------------------------------- -4 | Remove design template instance. -@end verbatim - -@subsubsection Design template with translation (optimized) - -Producing translated images satisfies almost all our production images -needs, but there is still a pitfall in them. In order to produce -translated images as in the ``one-to-one'' configuration describes -previously, it is required that one translation file has one design -template. That's useful in many cases, but what would happen if we -need to apply many different translation files to the same design -template? Should we have to duplicate the same design template file -for each translation file, in order to satisfy the ``one-to-one'' -relation? What if we need to assign translation files to design -templates arbitrarily? - -Certenly, that's something the ``one-to-one'' configuration cannot -handle. So, that's why we had to ``optimize'' it. The optimized -configuration consists on using a matching list (@var{MATCHINGLIST}) -variable that specifies the relationship between translation files and -design templates in an arbitrary way. Using such matching list between -translation files and design templates let us use as many assignment -combinations as translation files and design templates we are working -with. - -The @var{MATCHINGLIST} variable is set in the pre-rendition -configuration script of the component we want to produce images for. -By default, the @var{MATCHINGLIST} variable is empty which means no -matching list is used. Otherwise, if @var{MATCHINGLIST} variable has a -value different to empty value then, @file{centos-art.sh} interprets -the matching list in order to know how translation files are applied -to design templates. - -For example, consider the following configuration: - -@table @strong -@item One entry under @file{trunk/Identity/}: - -In this configuration we want to produce three images using a -paragraph-based style, controlled by @file{paragraph.svg} design -template; and one image using a list-based style, controlled by -@file{list.svg} design template. - -@verbatim -trunk/Identity/Path/To/Dir -|-- Tpl -| |-- paragraph.svg -| `-- list.svg -`-- Img - |-- 01-welcome.png - |-- 02-donate.png - |-- 03-docs.png - `-- 04-support.png -@end verbatim - -@item One entry under @file{trunk/Translations/}: - -In order to produce translated images we need to have one translation -file for each translated image we want to produce. Notice how -translation names do match final image file names, but how translation -names do not match design template names. When we use matching list -there is no need for translation files to match the names of design -templates, such name relation is set inside the matching list itself. - -@verbatim -trunk/Translations/Identity/Path/To/Dir -|-- 01-welcome.sed -|-- 02-donate.sed -|-- 03-docs.sed -`-- 04-support.sed -@end verbatim - -@item One entry under @file{trunk/trunk/Scripts/Bash/Functions/Render/Config/}: - -In order to produce different translated images using specific design -templates, we need to specify the relation between translation files -and design templates in a way that @file{centos-art.sh} could know -exactly what translation file to apply to what design template. This -relation between translation files and design templates is set using -the matching list @var{MATCHINGLIST} variable inside the pre-rendition -configuration script of the component we want to produce images for. - -@verbatim -trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir -`-- render.conf.sh -@end verbatim - -In this configuration the pre-rendition configuration script -(@file{render.conf.sh}) would look like the following: - -@verbatim -function render_loadConfig { - - # Define rendition actions. - ACTIONS[0]='BASE:renderImage' - - # Define matching list. - MATCHINGLIST="\ - paragraph.svg:\ - 01-welcome.sed\ - 02-donate.sed\ - 04-support.sed - list.svg:\ - 03-docs.sed - " - -} -@end verbatim - -As result, @file{centos-art.sh} will produce @file{01-welcome.png}, -@file{02-donate.png} and @file{04-support.png} using the -paragraph-based design template, but @file{03-docs.png} using the -list-based design template. -@end table - -@subsubsection Design template with translation (optimized+flexibility) - -In the production models we've seen so far, there are design templates -to produce untranslated images and translation files which combiend -with design templates produce translated images. That may seems like -all our needs are covered, doesn't it? Well, it @emph{almost} does. - -Generally, we use design templates to define how final images will -look like. Generally, each renderable directory structure has one -@file{Tpl/} directory where we organize design templates for that -identity component. So, we can say that there is only one unique -design template definition for each identity component; or what is the -same, said differently, identity components can be produced in one way -only, the way its own design template directory specifies. This is -not enough for theme production. It is a limitation, indeed. - -Initially, to create one theme, we created one renderable directory -structure for each theme component. When we found ourselves with many -themes, and components inside them, it was obvious that the same -design model was duplicated inside each theme. As design models were -independently one another, if we changed one theme's design model, -that change was useless to other themes. So, in order to reuse design -model changes, we unified design models into one common directory -structure. - -With design models unified in a common structure, another problem rose -up. As design models also had the visual style of theme components, -there was no difference between themes, so there was no apparent need -to have an independent theme directory structure for each different -theme. So, it was also needed to separate visual styles from design -models. - -At this point there are two independent worklines: one directory -structure to store design models (the final image characteristics -[i.e., dimensions, translation markers, etc.]) and one directory -structure to store visual styles (the final image visual style [i.e., -the image look and feel]). So, it is possible to handle both -different design models and different visual styles independtly one -another and later create combinations among them using -@file{centos-art.sh}. - -For example, consider the following configuration: - -@table @strong -@item One entry under @file{trunk/Identity/Themes/Models/}: - -The design model entry exists to organize design model files (similar -to design templates). Both design models and design templates are very -similar; they both should have the @code{CENTOSARTWORK} export id -present to identify the exportation area, translation marks, etc. -However, design models do use dynamic backgrounds inclusion while -design templates don't. - -@verbatim - THEMEMODEL | | The bond component - |<----| |--------------------->| -trunk/Identity/Themes/Models/Default/Distro/Anaconda/Progress/ -|-- paragraph.svg -`-- list.svg -@end verbatim - -Inisde design models, dynamic backgrounds are required in order for -different artistic motifs to reuse common design models. Firstly, in -order to create dynamic backgrounds inside design models, we import a -bitmap to cover design model's background and later, update design -model's path information to replace fixed values to dynamic values. - -@item One entry under @file{trunk/Identity/Themes/Motifs/}: - -The artistic motif entry defines the visual style we want to produce -images for, only. Final images (i.e., those built from combining both -design models and artistic motif backrounds) are not stored here, but -under branches directory structure. In the artistic motif entry, we -only define those images that cannot be produced automatically by -@file{centos-art.sh} (e.g., Backgrounds, Color information, -Screenshots, etc.). - -@verbatim - Artistic motif name | | Artistic motif backgrounds - |<-------| |-------->| -trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/ -|-- Img -| |-- Png -| | |-- 510x300.png -| | `-- 510x300-final.png -| `-- Jpg -| |-- 510x300.jpg -| `-- 510x300-final.jpg -|-- Tpl -| `-- 510x300.svg -`-- Xcf - `-- 510x300.xcf -@end verbatim - -@item One entry under @file{trunk/Translations/}: - -The translation entry specifies, by means of translation files, the -language-specific information we want to produce image for. When we -create the translation entry we don't use the name of neither design -model nor artistic motif, just the design model component we want to -produce images for. - -@verbatim - | The bond component - |--------------------->| -trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ -`-- 5 - |-- en - | |-- 01-welcome.sed - | |-- 02-donate.sed - | `-- 03-docs.sed - `-- es - |-- 01-welcome.sed - |-- 02-donate.sed - `-- 03-docs.sed -@end verbatim - -@item One entry under @file{trunk/Scripts/Bash/Functions/Render/Config/}: - -There is one pre-rendition configuration script for each theme -component. So, each time a theme component is rendered, its -pre-rendition configuration script is evaluated to teach -@file{centos-art.sh} how to render the component. - -@verbatim -trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Distro/Anaconda/Progress/ -`-- render.conf.sh -@end verbatim - -In this configuration the pre-rendition configuration script -(@file{render.conf.sh}) would look like the following: - -@verbatim -function render_loadConfig { - - # Define rendition actions. - ACTIONS[0]='BASE:renderImage' - - # Define matching list. - MATCHINGLIST="\ - paragraph.svg:\ - 01-welcome.sed\ - 02-donate.sed - list.svg:\ - 03-docs.sed - " - - # Deifne theme model. - THEMEMODEL='Default' - -} -@end verbatim -@end table - -The production flow of ``optimize+flexibility'' configuration@dots{} -@subsection Renderable translation directory structures - -Translation directory structures are auxiliar structures of renderable -identity directory structures. There is one translation directory -structure for each renderable identity directory structure. Inside -translation directory structures we organize translation files used by -renderable identity directory structures that produce translated -images. Renderable identity directory structures that produce -untranslated images don't use translation files, but they do use a -translation directory structure, an empty translation directory -structure, to be precise. - -In order to aliviate production of translation file, we made -translation directory structures renderable adding a template -(@file{Tpl/}) directory structure to handle common content inside -translation files. This way, we work on translation templates and -later use @file{centos-art.sh} to produce specific translation files -(based on translation templates) for different information (e.g., -languages, release numbers, architectures, etc.). - -If for some reason, translation files get far from translation -templates and translation templates become incovenient to produce such -translation files then, care should be taken to avoid replacing the -content of translation files with the content of translation templates -when @file{centos-art.sh} is executed to produce translation files -from translation templates. - -Inside renderable translation directory structures, -@file{centos-art.sh} can produce text-based files only. - -@subsection Copying renderable directory structures - -A renderable layout is formed by design models, design images, -pre-rendition configuration scripts and translations files. This way, -when we say to duplicate rendition stuff we are saying to duplicate -these four directory structures (i.e., design models, design images, -pre-rendition configuration scripts, and related translations files). - -When we duplicate directories, inside `trunk/Identity' directory -structure, we need to be aware of renderable layout described above -and the source location used to perform the duplication action. The -source location is relevant to centos-art.sh script in order to -determine the required auxiliar information inside directory -structures that need to be copied too (otherwise we may end up with -orphan directory structures unable to be rendered, due the absence of -required information). - -In order for a renderable directory structure to be valid, the new -directory structure copied should match the following conditions: - -@enumerate -@item To have a unique directory structure under -@file{trunk/Identity}, organized by any one of the above -organizational designs above. - -@item To have a unique directory structure under -@file{trunk/Translations} to store translation files. - -@item To have a unique directory structure under -@file{trunk/Scripts/Bash/Functions/Render/Config} to set pre-rendition -configuration script. -@end enumerate - -As convenction, the @code{render_doCopy} function uses -@file{trunk/Identity} directory structure as source location. Once -the @file{trunk/Identity} directory structure has been specified and -verified, the related path information is built from it and copied -automatically to the new location specified by @var{FLAG_TO} variable. - -Design templates + No translation: - -Command: -- centos-art render --copy=trunk/Identity/Path/To/Dir --to=trunk/Identity/NewPath/To/Dir - -Sources: -- trunk/Identity/Path/To/Dir -- trunk/Translations/Identity/Path/To/Dir -- trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir - -Targets: -- trunk/Identity/NewPath/To/Dir -- trunk/Translations/Identity/NewPath/To/Dir -- trunk/Scripts/Bash/Functions/Render/Config/Identity/NewPath/To/Dir - -Renderable layout 2: - -Command: -- centos-art render --copy=trunk/Identity/Themes/Motifs/TreeFlower \ - --to=trunk/Identity/Themes/Motifs/NewPath/To/Dir - -Sources: -- trunk/Identity/Themes/Motifs/TreeFlower -- trunk/Translations/Identity/Themes -- trunk/Translations/Identity/Themes/Motifs/TreeFlower -- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes -- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/TreeFlower - -Targets: -- trunk/Identity/Themes/Motifs/NewPath/To/Dir -- trunk/Translations/Identity/Themes -- trunk/Translations/Identity/Themes/Motifs/NewPath/To/Dir -- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes -- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewPath/To/Dir - -Notice that design models are not included in source or target -locations. This is intentional. In ``Renderable layout 2'', design -models live by their own, they just exist, they are there, available -for any artistic motif to use. By default `Themes/Models/Default' -design model directory structure is used, but other design models -directory structures (under Themes/Models/) can be created and used -changing the value of THEMEMODEL variable inside the pre-rendition -configuration script of the artistic motif source location you want to -produce. - -Notice how translations and pre-rendition configuration scripts may -both be equal in source and target. This is because such structures -are common to all artistic motifs (the default values to use when no -specific values are provided). - -- The common directory structures are not copied or deleted. We cannot - copy a directory structure to itself. - -- The common directory structures represent the default value to use - when no specific translations and/or pre-rendition configuration - script are provided inside source location. - -- The specific directory structures, if present, are both copiable and - removable. This is, when you perform a copy or delete action from - source, that source specific auxiliar directories are transfered in - the copy action to a new location (that specified by FLAG_TO - variable). - -- When translations and/or pre-rendition configuration scripts are - found inside the source directory structure, the centos-art.sh - script loads common auxiliar directories first and later specific - auxiliar directories. This way, identity rendition of source - locations can be customized idividually over the base of common - default values. - -- The specific auxiliar directories are optional. - -- The common auxiliar directories should be present always. This is, - in order to provide the information required by render functionality - (i.e., to make it functional in the more basic level of its - existence). - -Notice how the duplication process is done from `trunk/Identity' on, -not the oposite. If you try to duplicate a translation structure (or -similar auxiliar directory structures like pre-rendition configuration -scripts), the `trunk/Identity' for that translation is not created. -This limitation is impossed by the fact that many `trunk/Identity' -directory structures may reuse/share the same translation directory -structure. We cannot delete one translation (or similar) directory -structures while a related `trunk/Identity/' directory structure is -still in need of it. - -The `render_doCopy' functionality does duplicate directory structures -directly involved in rendition process only. Once such directories -have been duplicated, the functionality stops thereat. - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@comment --- Removed(* trunk Scripts Bash Functions Render Config::) --- -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Render/Config.texi b/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Render/Config.texi deleted file mode 100644 index 3b3322b..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Render/Config.texi +++ /dev/null @@ -1,192 +0,0 @@ -@subsection Goals - -The @file{trunk/Scripts/Bash/Config} directory exists to oraganize -pre-rendering configuration scripts. - -@subsection Description - -Pre-rendering configuration scripts let you customize the way -@command{centos-art.sh} script renders identity and translation -repository entries. Pre-rendering configuration scripts are -@file{render.conf.sh} files with @command{render_loadConfig} function -definition inside. - -There is one @file{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. - -@subsubsection The @file{render.conf.sh} identity model - -Inside CentOS Artwork Repository, we consider identity entries to all -directories under @file{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: - -@verbatim -#!/bin/bash - -function render_loadConfig { - - # Define rendering actions. - ACTIONS[0]='BASE:renderImage' - ACTIONS[1]='POST:renderFormats: tif xpm pdf ppm' - -} -@end verbatim - -Inside identity pre-rendering configuration scripts, text-based -pre-rendering configuration scripts look like the following: - -@verbatim -#!/bin/bash - -function render_loadConfig { - - # Define rendering actions. - ACTIONS[0]='BASE:renderText' - ACTIONS[1]='POST:formatText: --width=70 --uniform-spacing' - -} -@end verbatim - -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. - -@subsubsection The @file{render.conf.sh} translation model - -Translation pre-rendering configuration scripts take precedence before -default translation rendering action. Translation pre-rendering -actions are useful when default translation rendering action do not -fit itself to translation entry rendering requirements. - -@subsubsection The @file{render.conf.sh} rendering actions - -Inside both image-based and text-based identity pre-rendering -configuration scripts, we use the @samp{ACTIONS} array variable to -define the way @command{centos-art.sh} script performs identity -rendering. Identity rendering is organized by one @samp{BASE} action, -and optional @samp{POST} and @samp{LAST} rendering actions. - -The @samp{BASE} action specifies what kind of rendering does the -@command{centos-art.sh} script will perform with the files related to -the pre-rendering configuration script. The @samp{BASE} action is -required. Possible values to @samp{BASE} action are either -@samp{renderImage} or @samp{renderText} only. - -To specify the @samp{BASE} action you need to set the @samp{BASE:} -string followed by one of the possible values. For example, if you -want to render images, consider the following definition of -@samp{BASE} action: - -@verbatim -ACTIONS[0]='BASE:renderImage' -@end verbatim - -Only one @samp{BASE} action must be specified. If more than one -@samp{BASE} action is specified, the last one is used. If no -@samp{BASE} action is specified at all, an error is triggered and the -@command{centos-art.sh} script ends its execution. - -The @samp{POST} action specifies which action to apply for -each file rendered (at the rendering time). This action is optional. -You can set many different @samp{POST} actions to apply many different -actions over the same already rendered file. Possible values to -@samp{POST} action are @samp{renderFormats}, @samp{renderSyslinux}, -@samp{renderGrub}, etc. - -To specify the @samp{POST} action, you need to use set the -@samp{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 @samp{xpm}, @samp{jpg}, and -@samp{tif} images, based on already rendered @samp{png} image, and -also organize the produced files in directories named as their own -extensions: - -@verbatim -ACTIONS[0]='BASE:renderImage' -ACTIONS[1]='POST:renderFormats: xpm jpg tif' -ACTIONS[2]='POST:groupByFormat: png xpm jpg tif' -@end verbatim - -In the previous example, file organization takes place at the moment -of rendering, just after producing the @samp{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 @samp{POST:groupByFormat} action line: - -@verbatim -ACTIONS[0]='BASE:renderImage' -ACTIONS[1]='POST:renderFormats: xpm jpg tif' -@end verbatim - -The @samp{LAST} action specifies which actions to apply once the last -file in the list of files to process has been rendered. The -@samp{LAST} action is optional. Possible values for @samp{LAST} -actions may be @samp{groupByFormat}, @samp{renderGdmTgz}, etc. - -@quotation -@strong{Note} --- @strong{Removed}(xref:trunk Scripts Bash Functions Render) ---, to know more -about possible values for @samp{BASE}, @samp{POST} and @samp{LAST} -action definitions. -@end quotation - -To specify the @samp{LAST} action, you need to set the @samp{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: - -@verbatim -ACTIONS[0]='BASE:renderImage' -ACTIONS[1]='POST:renderFormats: xpm jpg tif' -ACTIONS[2]='LAST:groupByformat: png xpm jpg tif' -@end verbatim - -@subsection Usage - -Use the following commands to administer both identity and translation -pre-rendering configuration scripts: - -@table @samp - -@item centos-art config --create='path/to/dir/' - -Use this command to create @samp{path/to/dir} related pre-rendering -configuration script. - -@item centos-art config --edit='path/to/dir/' - -Use this command to edit @samp{path/to/dir} related pre-rendering -configuration script. - -@item centos-art config --read='path/to/dir/' - -Use this command to read @samp{path/to/dir} related pre-rendering -configuration script. - -@item centos-art config --remove='path/to/dir/' - -Use this command to remove @samp{path/to/dir} related pre-rendering -configuration script. - -@end table - -In the commands above, @samp{path/to/dir} refers to one renderable -directory path under @file{trunk/Identity} or -@file{trunk/Translations} structures only. - -@subsection See also - -@menu -* trunk Scripts Bash:: -@comment --- Removed(* trunk Scripts Bash Functions::) --- -@comment --- Removed(* trunk Scripts Bash Functions Render::) --- -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Shell.texi b/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Shell.texi deleted file mode 100644 index a5016fe..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Shell.texi +++ /dev/null @@ -1,184 +0,0 @@ -@subsection Goals - -This section exists to organize files related to @code{shell} -functionality of @file{centos-art.sh} script. - -@subsection Description - -The @code{shell} functionality of @file{centos-art.sh} script helps -you to maintain bash scripts inside repository. For example, suppose -you've created many functionalities for @file{centos-art.sh} script, -and you want to use a common copyright and license note for -consistency in all your script files. If you have a bunch of files, -doing this one by one wouldn't be a big deal. In contrast, if the -amount of files grows, updating the copyright and license note for all -of them would be a task rather tedious. The @code{shell} functionality -exists to solve maintainance tasks just as the one previously -mentioned. - -When you use @code{shell} functionality to update copyright inside -script files, it is required that your script files contain (at least) -the following top commentary structure: - -@float Figure,fig:trunk/Scripts/Bash/Functions/Shell:1 -@verbatim - 1| #!/bin/bash - 2| # - 3| # doSomething.sh -- The function description goes here. - 4| # - 5| # Copyright - 6| # - 7| # ... - 8| # - 9| # ---------------------------------------------------------------------- -10| # $Id$ -11| # ---------------------------------------------------------------------- -12| -13| function doSomething { -14| -15| } -@end verbatim -@caption{The functions script base comment structure} -@end float - -Relevant lines in the above structure are lines from 5 to 9. -Everything else in the file is left immutable. - -When you are updating copyright through @code{shell} -functionality, the @file{centos-art.sh} script replaces everything -in-between line 5 ---the first one matching @samp{^# Copyright .+$} -string--- and line 9---the first long dash separator matching @samp{^# --+$}--- with the content of copyright template instance. - -@quotation -@strong{Caution} Be sure to add the long dash separator that matches -@samp{^# -+$} regular expression @emph{before} the function -definition. Otherwise, if the @samp{Copyright} line is present but no -long dash separator exists, @file{centos-art.sh} will remove anything -in-between the @samp{Copyright} line and the end of file. This way you -may lost your function definitions entirely. -@end quotation - -The copyright template instance is created from one copyright template -stored in the @file{Config/tpl_forCopyright.sed} file. The template -instance is created once, and later removed when no longer needed. At -this moment, when template instance is created, the -@file{centos-art.sh} script takes advantage of automation in order to -set copyright full name and date dynamically. - -When you use @code{shell} functionality to update copyright, the first -thing @file{shell} functionality does is requesting copyright -information to user, and later, if values were left empty (i.e., no -value was typed before pressing @key{RET} key), the @file{shell} -functionality uses its own default values. - -When @code{shell} functionality uses its own default values, the final -copyright note looks like the following: - -@float Figure,fig:trunk/Scripts/Bash/Functions/Shell:2 -@verbatim - 1| #!/bin/bash - 2| # - 3| # doSomthing.sh -- The function description goes here. - 4| # - 5| # Copyright (C) 2003, 2010 The CentOS Project - 6| # - 7| # This program is free software; you can redistribute it and/or modify - 8| # it under the terms of the GNU General Public License as published by - 9| # the Free Software Foundation; either version 2 of the License, or -10| # (at your option) any later version. -11| # -12| # This program is distributed in the hope that it will be useful, but -13| # WITHOUT ANY WARRANTY; without even the implied warranty of -14| # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -15| # General Public License for more details. -16| # -17| # You should have received a copy of the GNU General Public License -18| # along with this program; if not, write to the Free Software -19| # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 -20| # USA. -21| # -22| # ---------------------------------------------------------------------- -23| # $Id$ -24| # ---------------------------------------------------------------------- -25| -26| function doSomething { -27| -28| } -@end verbatim -@caption{The function script comment example} -@end float - -Relevant lines in the above structure are lines from 5 to 22. Pay -attention how the copyright line was built, and how the license was -added into the top comment where previously was just three dots. -Everything else in the file was left immutable. - -To change copyright information (i.e., full name or year information), -run the @code{shell} functionality over the root directory containing -the script files you want to update copyright in and enter the -appropriate information when it be requested. You can run the -@code{shell} functionality as many times as you need to. - -To change copyright license (i.e., the text in-between lines 7 and -20), you need to edit the @file{Config/tpl_forCopyright.sed} file, set -the appropriate information, and run the @code{shell} functionality -once again for changes to take effect over the files you specify. - -@quotation -@strong{Important} The @file{centos-art.sh} script is released as: - -@verbatim -GNU GENERAL PUBLIC LICENSE -Version 2, June 1991 - -Copyright (C) 1989, 1991 Free Software Foundation, Inc. -59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. -@end verbatim - -Do not change the license information under which @file{centos-art.sh} -script is released. Instead, if you think a different license must be -used, please share your reasons at @email{centos-devel@@centos-art.sh, -CentOS Developers mailing list}. -@end quotation - -@subsection Usage - -@table @command -@item centos-art sh --update-copyright='path/to/dir' -@itemx centos-art sh --update-copyright='path/to/dir' --filter='regex' -Use these commands to update copyright information in @samp{.sh} files -under @samp{path/to/dir} directory. -@end table - -When you provide @option{--filter='regex'} argument, the list of files -to process is reduced as specified in @samp{regex} regular expression. -Inside @file{centos-art.sh} script, the @samp{regex} regular -expression is used in combination with @command{find} command to look -for files matching the regular expression path pattern. - -@quotation -@strong{Warning} In order for @samp{regex} regular expression to match -a file, the @samp{regex} regular expresion must match the whole file -path not just the file name. -@end quotation - -For example, if you want to match all @file{render.conf.sh} files -inside @file{path/to/dir}, use the @code{.+/render.conf} regular -expression. Later, @file{centos-art.sh} script uses this value inside -@code{^$REGEX\.sh$} expression in order to build the final regular -expression (i.e., @code{^.+/render.conf\.sh$}) that is evaluated -against available file paths inside the list of files to process. - -Exceptionally, when you provide @option{--filter='regex'} in the way -that @samp{regex}, appended to @samp{path/to/dir/} (i.e. -@samp{path/to/dir/regex}), matches a regular file; the -@file{centos-art.sh} script uses the file matching as only file in the -list of files to process. - -@subsection See also - -@menu -* trunk Scripts Bash:: -@comment --- Removed(* trunk Scripts Bash Functions::) --- -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Svg.texi b/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Svg.texi deleted file mode 100644 index 341745d..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Svg.texi +++ /dev/null @@ -1,192 +0,0 @@ -@subsection Goals - -This section exists to organize files related to @code{svg} -functionality of @file{centos-art.sh} script. - -@subsection Description - -The @code{svg} functionality of @file{centos-art.sh} script helps you -to maintain scalable vector graphics (SVG) inside repository. For -example, suppose you've been working in CentOS default design models -under @file{trunk/Identity/Themes/Models/}, and you want to set common -metadata to all of them, and later remove all unused SVG defintions -from @samp{*.svg} files. Doing so file by file may be a tedious task, -so the @file{centos-art.sh} script provides the @code{svg} -functionality to aid you maintain such actions. - -@cindex Metadata maintainance -@subsubsection Metadata maintainance - -The metadata used is defined by Inkscape 0.46 using the SVG standard -markup. The @file{centos-art.sh} script replaces everything -in-between @code{} tags with a -predefined metadata template we've set for this purpose. - -The metadata template was created using the metadata information of a -file which, using Inkscape 0.46, all metadata fields were set. This -created a complete markup representation of how SVG metadata would -look like. Later, we replaced every single static value with a -translation marker in the form @samp{=SOMETEXT=}, where -@code{SOMETEXT} is the name of its main opening tag. Later, we -transform the metadata template into a sed replacement set of commads -escaping new lines at the end of each line. - -With metadata template in place, the @file{centos-art.sh} script uses -it to create a metadata template instance for the file being processed -currently. The metadata template instance contains the metadata -portion of sed replacement commands with translation markers already -traduced. In this action, instance creation, is where we take -advantage of automation and generate metadata values like title, date, -keywords, source, identifier, and relation dynamically, based on the -file path @file{centos-art.sh} script is currently creating metadata -information for. - -With metadata template instance in place, the @file{centos-art.sh} -script uses it to replace real values inside all @samp{.svg} files -under the current location you're running the @file{centos-art.sh} -script on. Default behaviour is to ask user to enter each metadatum -required, one by one. If user leaves metadatum empty, by pressing -@key{RET} key, @file{centos-art.sh} uses its default value. - -The @file{centos-art.sh} script modifies the following metadata: - -@table @samp -@item Title -Name by which this document is formally known. If no value is set -here, @file{centos-art.sh} script uses the file name as title. - -@item Date -Date associated with the creation of this document (YYYY-MM-DD). If no -value is set here, @file{centos-art.sh} script uses the current date -information as in @command{date +%Y-%m-%d}. - -@item Creator -Name of entity primarily responsible for making the content of this -document. If no value is set here, @file{centos-art.sh} script uses -the string @samp{The CentOS Project}. - -@item Rights -Name of entity with rights to the intellectual Property of this -document. If no value is set here, @file{centos-art.sh} script uses -the string @samp{The CentOS Project}. - -@item Publisher -Name of entity responsible for making this document available. If no -value is set here, @file{centos-art.sh} script uses the string -@samp{The CentOS Project}. - -@item Identifier -Unique URI to reference this document. If no value is set here, -@file{centos-art.sh} script uses the current file path to build the -related url that points to current file location inside repository -central server. - -@item Source -Unique URI to reference the source of this document. If no value is -set here, @file{centos-art.sh} script uses current file path to build -the related url that points to current file location inside repository -central server. - -@item Relation -Unique URI to a related document. If no value is set here, -@file{centos-art.sh} script uses current file path to build the -related url that points to current file location inside repository -central server. - -@item Language -Two-letter language tag with optional subtags for the language of this -document. (e.g. @samp{en-GB}). If no value is set here, -@file{centos-art.sh} script uses the current locale information as in -@code{cli_getCurrentLocale} function. - -@item Keywords -The topic of this document as comma-separated key words, prhases, or -classifications. If no value is set here, @file{centos-art.sh} script -uses file path to build - -@item Coverage -Extent or scope of this document. If no value is set here, -@file{centos-art.sh} script uses the string @samp{The CentOS Project}. - -@item Description -Description about the document. If no value is set here, -@file{centos-art.sh} script uses uses empty value as default. - -@item Contributors -People that contributes in the creation/maintainance of the document. -If no value is set here, @file{centos-art.sh} script uses uses empty -value as default. -@end table - -The @samp{License} metadatum is not set as a choise, by now. It is -fixed @url{http://creativecommons.org/licenses/by-sa/3.0/, Creative -Common Attribution Share-Alike 3.0 License}. This is done in order to -grant license consistency among all SVG files we manage inside CentOS -Artwork Repository. - -@cindex Unused definitions -@subsubsection Unused definitions - -Many of the no-longer-used gradients, patterns, and markers (more -precisely, those which you edited manually) remain in the -corresponding palettes and can be reused for new objects. However if -you want to optimize your document, use the @samp{Vacuum Defs} command -in @samp{File} menu. It will remove any gradients, patterns, or -markers which are not used by anything in the document, making the -file smaller. - -If you have one or two couple of files, removing unused definitions -using the graphical interface may be enough to you. In contrast, if -you have dozens or even houndreds of scalable vector graphics files to -maintain it is not a fun task to use the graphical interface to remove -unused definitions editing those files one by one. - -To remove unused definitions from several scalable vector graphics -files, the @file{centos-art.sh} script uses Inkscape command-line -interface, specifically with the @option{--vaccum-defs} option. - -@subsection Usage - -@table @command -@item centos-art svg --update-metadata='path/to/dir' -@item centos-art svg --update-metadata='path/to/dir' --filter='regex' -Use these commands to update metadata information to @samp{.svg} files -under @samp{path/to/dir} directory. - -@item centos-art svg --vacuum-defs='path/to/dir' -@item centos-art svg --vacuum-defs='path/to/dir' --filter='regex' -Use these commands to remove unused definitions inside @samp{.svg} -files under @samp{path/to/dir} directory. -@end table - -When you provide @option{--filter='regex'} argument, the list of files -to process is reduced as specified in @samp{regex} regular expression. -Inside @file{centos-art.sh} script, the @samp{regex} regular -expression is used in combination with @command{find} command to look -for files matching the regular expression path pattern. - -@quotation -@strong{Warning} In order for @samp{regex} regular expression to match -a file, the @samp{regex} regular expresion must match the whole file -path not just the file name. -@end quotation - -For example, if you want to match all @file{summary.svg} files inside -@file{path/to/dir}, use the @code{.+/summary} regular expression. -Later, @file{centos-art.sh} script uses this value inside -@code{^$REGEX\.svg$} expression in order to build the final regular -expression (i.e., @code{^.+/summary\.svg$}) that is evaluated against -available file paths inside the list of files to process. - -Exceptionally, when you provide @option{--filter='regex'} in the way -that @samp{regex}, appended to @samp{path/to/dir/} (i.e. -@samp{path/to/dir/regex}), matches a regular file; the -@file{centos-art.sh} script uses the file matching as only file in the -list of files to process. - -@subsection See also - -@menu -* trunk Scripts Bash:: -@comment --- Removed(* trunk Scripts Bash Functions::) --- -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Verify.texi b/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Verify.texi deleted file mode 100644 index ff98b51..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Bash/Cli/Functions/Verify.texi +++ /dev/null @@ -1,245 +0,0 @@ -@subsection Goals - -This section exists to organize files related to @file{centos-art.sh} -script @samp{verify} functionality. The @samp{verify} -functionality of @file{centos-art.sh} script helps you to verify the -workstation configuration you are planning to use as host for your -working copy of CentOS Artwork Repository. - -@subsection Description - -The first time you download CentOS Artwork Repository you need to -configure your workstation in order to use @file{centos-art.sh} -script. These preliminar configurations are based mainly on auxiliar -RPM packages installation, symbolic links creations, and environment -variables definitions. The @samp{verify} functionality of -@file{centos-art.sh} script guides you through this preliminar -configuration process. - -If this is the first time you run @file{centos-art.sh} script, the -appropriate way to use its @samp{verify} functionality is not using -the @file{centos-art.sh} script directly, but the absolute path to -@command{centos-art.sh} script instead (i.e., -@file{~/artwork/trunk/Scripts/Bash/centos-art.sh}). This is necessary -because @file{centos-art} symbolic link, under @file{~/bin/} -directory, has not been created yet. - -@subsubsection Packages - -Installation of auxiliar RPM packages provides the software required -to manipulate files inside the repository (e.g., image files, -documentation files, translation files, script files, etc.). Most of -RPM packages @command{centos-art.sh} script uses are shipped with -CentOS distribution, and can be installed from CentOS base repository. -The only exception is @samp{inkscape}, the package we use to -manipulate SVG files. The @samp{inkscape} package is not inside -CentOS distribution so it needs to be installed from third party -repositories. - -@quotation -@strong{Note} Configuration of third party repositories inside CentOS -distribution is described in CentOS wiki, specifically in the -following URL: -@url{http://wiki.centos.org/AdditionalResources/Repositories} -@end quotation - -Before installing packages, the @file{centos-art.sh} script uses -@command{sudo} to request root privileges to execute @command{yum} -installation functionality. If your user isn't defined as a -privileged user---at least to run @command{yum} commands--- inside -@file{/etc/sudoers} configuration file, you will not be able to -perform package installation tasks as set in @file{centos-art.sh} -script @samp{verify} functionality. - -Setting sudo privileges to users is an administrative task you have to -do by yourself. If you don't have experience with @command{sudo} -command, please read its man page running the command: @command{man -sudo}. This reading will be very useful, and with some practice, you -will be able to configure your users to have @command{sudo} -privileges. - -@subsubsection Links - -Creation of symbolic links helps us to alternate between different -implementations of @file{centos-art.sh} script-line (e.g., -@file{centos-art.sh}, for Bash implementation; @file{centos-art.py}, -for Python implementation; @file{centos-art.pl}, for Perl -implementation; and so on for other implementations). The -@file{centos-art.sh} script-line definition takes place inside your -personal binary (@file{~/bin/}) directory in order to make the script -implementation ---the one that @file{centos-art} links to--- available -to @var{PATH} environment variable. - -Creation of symbolic links helps us to reuse components from repository -working copy. For example, color information files maintained inside -your working copy must never be duplicated inside program-specific -configuration directories that uses them in your workstation (e.g., -Gimp, Inkscape, etc.). Instead, a symbolic link must be created for -each one of them, from program-specific configuration directories to -files in the working copy. In this configuration, when someone -commits changes to color information files up to central repository, -they---the changes committed--- will be immediatly available to your -programs the next time you update your working copy ---the place -inside your workstation those color information files are stored---. - -Creation of symbolic links helps us to make @file{centos-art.sh} -script functionalities available outside @file{trunk/} repository -directory structure, but at its same level in repository tree. This is -useful if you need to use the ``render'' functionality of -@command{centos-art.sh} under @file{branches/} repository directory -structure as you usually do inside @file{trunk/} repository directory -structure. As consequence of this configuration, automation scripts -cannot be branched under @file{branches/Scripts} directory structure. - -@subsubsection Environment variables - -Definition of environemnt variables helps us to set default values to -our user session life. The user session environment variable defintion -takes place in the user's @file{~/.bash_profile} file. The -@samp{verify} functionality of @file{centos-art.sh} script doesn't -modify your @file{~/.bash_profile} file. - -The @samp{verify} functionality of @file{centos-art.sh} script -evaluates the following environment variables: - -@table @env -@item EDITOR -Default text editor. - -The @file{centos-art.sh} script uses default text @env{EDITOR} to edit -pre-commit subversion messages, translation files, configuration -files, script files, and similar text-based files. - -If @env{EDITOR} environment variable is not set, @file{centos-art.sh} -script uses @file{/usr/bin/vim} as default text editor. Otherwise, the -following values are recognized by @file{centos-art.sh} script: - -@itemize -@item @file{/usr/bin/vim} -@item @file{/usr/bin/emacs} -@item @file{/usr/bin/nano} -@end itemize - -If no one of these values is set in @env{EDITOR} environment variable, -@file{centos-art.sh} uses @file{/usr/bin/vim} text editor by default. - -@item TEXTDOMAIN - -Default domain used to retrieve translated messages. This variable is -set in @file{initFunctions.sh} and shouldn't be changed. - -@item TEXTDOMAINDIR - -Default directory used to retrieve translated messages. This variable -is set in @file{initFunctions.sh} and shouldn't be changed. - -@item LANG - -Default locale information. - -This variable is initially set in the configuration process of CentOS -distribution installer (i.e., Anaconda), specifically in the -@samp{Language} step; or once installed using the -@command{system-config-language} tool. - -The @file{centos-art.sh} script uses the @var{LANG} environment -variable to know in which language the script messages are printed -out. - -@item TZ - -Default time zone representation. - -This variable is initially set in the configuration process of CentOS -distribution installer (i.e., Anaconda), specifically in the -@samp{Date and time} step; or once installed using the -@command{system-config-date} tool. - -The @file{centos-art.sh} script doesn't use the @var{TZ} environment -variable information at all. Instead, this variable is used by the -system shell to show the time information according to your phisical -location on planet Earth. - -Inside your computer, the time information is firstly set in the BIOS -clock (which may need correction), and later in the configuration -process of CentOS distribution installer (or later, by any of the -related configuration tools inside CentOS distribution). Generally, -setting time information is a straight-forward task and configuration -tools available do cover most relevant location. However, if you need -a time precision not provided by the configuration tools available -inside CentOS distribution then, using @var{TZ} variable may be -necessary. - -@quotation -@strong{Convenction} In order to keep changes syncronized between -central repository and its working copies: configure both repository -server and workstations (i.e., the place where each working copy is -set on) to use Coordinated Universal Time (UTC) as base time -representation. Later, correct the time information for your specific -location using time zone correction. -@end quotation - -The format of @var{TZ} environment variable is described in -@file{tzset(3)} manual page. - -@end table - -@subsection Usage - -@table @command - -@item centos-art verify --packages - -Verify required packages your workstation needs in order to run the -@file{centos-art.sh} script correctly. If there are missing packages, -the @file{centos-art.sh} script asks you to confirm their -installation. When installing packages, the @file{centos-art.sh} -script uses the @command{yum} application in order to achieve the -task. - -In case all packages required by @file{centos-art.sh} script are -already installed in your workstation, the message @samp{The required -packages are already installed.} is output for you to know. - -@item centos-art verify --links - -Verify required links your workstation needs in order to run the -centos-art command correctly. If any required link is missing, the -@command{centos-art.sh} script asks you to confirm their installation. -To install required links, the @command{centos-art.sh} script uses the -@command{ln} command. - -In case all links required by @file{centos-art.sh} script are already -created in your workstation, the message @samp{The required links are -already installed.} is output for you to know. - -In case a regular file exists with the same name of a required link, -the @file{centos-art.sh} script outputs the @samp{Already exists as -regular file.} message when listing required links that will be -installed. Of course, as there is already a regular file where must be -a link, no link is created. In such cases the @file{centos-art.sh} -script will fall into a continue installation request for that missing -link. To end this continue request you can answer @samp{No}, or -remove the existent regular file to let @file{centos-art.sh} script -install the link on its place. - -@item centos-art verify --environment -@itemx centos-art verify --environment --filter='regex' - -Output a brief description of environment variables used by -@file{centos-art.sh} script. - -If @samp{--filter} option is provided, output is reduced as defined in -the @samp{regex} regular expression value. If @samp{--filter} option -is specified but @samp{regex} value is not, the @file{centos-art.sh} -script outputs information as if @samp{--filter} option had not been -provided at all. - -@end table - -@subsection See also - -@menu -* trunk Scripts Bash:: -@comment --- Removed(* trunk Scripts Bash Functions::) --- -@end menu diff --git a/Manuals/Filesystem/trunk/Scripts/Python.texi b/Manuals/Filesystem/trunk/Scripts/Python.texi deleted file mode 100644 index fb39647..0000000 --- a/Manuals/Filesystem/trunk/Scripts/Python.texi +++ /dev/null @@ -1,22 +0,0 @@ -@subsection Goals - -@itemize -@item ... -@end itemize - -@subsection Description - -@itemize -@item ... -@end itemize - -@subsection Usage - -@itemize -@item ... -@end itemize - -@subsection See also - -@menu -@end menu diff --git a/Manuals/Filesystem/trunk/chapter-intro.texi b/Manuals/Filesystem/trunk/chapter-intro.texi deleted file mode 100644 index e69de29..0000000 --- a/Manuals/Filesystem/trunk/chapter-intro.texi +++ /dev/null diff --git a/Manuals/Filesystem/trunk/chapter-menu.texi b/Manuals/Filesystem/trunk/chapter-menu.texi deleted file mode 100644 index 1dace8c..0000000 --- a/Manuals/Filesystem/trunk/chapter-menu.texi +++ /dev/null @@ -1,62 +0,0 @@ -@menu -* trunk Identity:: -* trunk Identity Brands:: -* trunk Identity Fonts:: -* trunk Identity Icons:: -* trunk Identity Isolinux:: -* trunk Identity Models:: -* trunk Identity Models Css:: -* trunk Identity Models Html:: -* trunk Identity Models Img Promo Web:: -* trunk Identity Models Tpl:: -* trunk Identity Models Tpl Promo Web:: -* trunk Identity Models Xcf:: -* trunk Identity Release:: -* trunk Identity Themes:: -* trunk Identity Themes Models:: -* trunk Identity Themes Models Alternative:: -* trunk Identity Themes Models Default:: -* trunk Identity Themes Models Default Distro:: -* trunk Identity Themes Models Default Distro Anaconda:: -* trunk Identity Themes Models Default Promo:: -* trunk Identity Themes Models Default Web:: -* trunk Identity Themes Motifs:: -* trunk Identity Themes Motifs Flame:: -* trunk Identity Themes Motifs Modern:: -* trunk Identity Themes Motifs Modern Backgrounds:: -* trunk Identity Themes Motifs Modern Backgrounds Img:: -* trunk Identity Themes Motifs Modern Backgrounds Tpl:: -* trunk Identity Themes Motifs Modern Backgrounds Xcf:: -* trunk Identity Themes Motifs Modern Distro Anaconda Progress:: -* trunk Identity Themes Motifs Modern Palettes:: -* trunk Identity Themes Motifs TreeFlower:: -* trunk Identity Themes Motifs TreeFlower Backgrounds:: -* trunk Identity Widgets:: -* trunk Locales:: -* trunk Locales Identity:: -* trunk Locales Identity Brands:: -* trunk Locales Identity Brands Tpl:: -* trunk Locales Identity Fonts:: -* trunk Locales Identity Models:: -* trunk Locales Identity Release:: -* trunk Locales Identity Themes:: -* trunk Locales Identity Themes Backgrounds:: -* trunk Locales Identity Themes Distro Anaconda Progress:: -* trunk Locales Identity Widgets:: -* trunk Manuals:: -* trunk Scripts:: -* trunk Scripts Bash:: -* trunk Scripts Bash Cli:: -* trunk Scripts Bash Cli Functions:: -* trunk Scripts Bash Cli Functions Help:: -* trunk Scripts Bash Cli Functions Html:: -* trunk Scripts Bash Cli Functions Locale:: -* trunk Scripts Bash Cli Functions Manual:: -* trunk Scripts Bash Cli Functions Path:: -* trunk Scripts Bash Cli Functions Render:: -* trunk Scripts Bash Cli Functions Render Config:: -* trunk Scripts Bash Cli Functions Shell:: -* trunk Scripts Bash Cli Functions Svg:: -* trunk Scripts Bash Cli Functions Verify:: -* trunk Scripts Python:: -@end menu diff --git a/Manuals/Filesystem/trunk/chapter-nodes.texi b/Manuals/Filesystem/trunk/chapter-nodes.texi deleted file mode 100644 index 2ab21f1..0000000 --- a/Manuals/Filesystem/trunk/chapter-nodes.texi +++ /dev/null @@ -1,300 +0,0 @@ -@node trunk Identity -@section trunk/Identity -@cindex trunk Identity -@include trunk/Identity.texi - -@node trunk Identity Brands -@section trunk/Identity/Brands -@cindex trunk Identity Brands -@include trunk/Identity/Brands.texi - -@node trunk Identity Fonts -@section trunk/Identity/Fonts -@cindex trunk Identity Fonts -@include trunk/Identity/Fonts.texi - -@node trunk Identity Icons -@section trunk/Identity/Icons -@cindex trunk Identity Icons -@include trunk/Identity/Icons.texi - -@node trunk Identity Isolinux -@section trunk/Identity/Isolinux -@cindex trunk Identity Isolinux -@include trunk/Identity/Isolinux.texi - -@node trunk Identity Models -@section trunk/Identity/Models -@cindex trunk Identity Models -@include trunk/Identity/Models.texi - -@node trunk Identity Models Css -@section trunk/Identity/Models/Css -@cindex trunk Identity Models Css -@include trunk/Identity/Models/Css.texi - -@node trunk Identity Models Html -@section trunk/Identity/Models/Html -@cindex trunk Identity Models Html -@include trunk/Identity/Models/Html.texi - -@node trunk Identity Models Img Promo Web -@section trunk/Identity/Models/Img/Promo/Web -@cindex trunk Identity Models Img Promo Web -@include trunk/Identity/Models/Img/Promo/Web.texi - -@node trunk Identity Models Tpl -@section trunk/Identity/Models/Tpl -@cindex trunk Identity Models Tpl -@include trunk/Identity/Models/Tpl.texi - -@node trunk Identity Models Tpl Promo Web -@section trunk/Identity/Models/Tpl/Promo/Web -@cindex trunk Identity Models Tpl Promo Web -@include trunk/Identity/Models/Tpl/Promo/Web.texi - -@node trunk Identity Models Xcf -@section trunk/Identity/Models/Xcf -@cindex trunk Identity Models Xcf -@include trunk/Identity/Models/Xcf.texi - -@node trunk Identity Release -@section trunk/Identity/Release -@cindex trunk Identity Release -@include trunk/Identity/Release.texi - -@node trunk Identity Themes -@section trunk/Identity/Themes -@cindex trunk Identity Themes -@include trunk/Identity/Themes.texi - -@node trunk Identity Themes Models -@section trunk/Identity/Themes/Models -@cindex trunk Identity Themes Models -@include trunk/Identity/Themes/Models.texi - -@node trunk Identity Themes Models Alternative -@section trunk/Identity/Themes/Models/Alternative -@cindex trunk Identity Themes Models Alternative -@include trunk/Identity/Themes/Models/Alternative.texi - -@node trunk Identity Themes Models Default -@section trunk/Identity/Themes/Models/Default -@cindex trunk Identity Themes Models Default -@include trunk/Identity/Themes/Models/Default.texi - -@node trunk Identity Themes Models Default Distro -@section trunk/Identity/Themes/Models/Default/Distro -@cindex trunk Identity Themes Models Default Distro -@include trunk/Identity/Themes/Models/Default/Distro.texi - -@node trunk Identity Themes Models Default Distro Anaconda -@section trunk/Identity/Themes/Models/Default/Distro/Anaconda -@cindex trunk Identity Themes Models Default Distro Anaconda -@include trunk/Identity/Themes/Models/Default/Distro/Anaconda.texi - -@node trunk Identity Themes Models Default Promo -@section trunk/Identity/Themes/Models/Default/Promo -@cindex trunk Identity Themes Models Default Promo -@include trunk/Identity/Themes/Models/Default/Promo.texi - -@node trunk Identity Themes Models Default Web -@section trunk/Identity/Themes/Models/Default/Web -@cindex trunk Identity Themes Models Default Web -@include trunk/Identity/Themes/Models/Default/Web.texi - -@node trunk Identity Themes Motifs -@section trunk/Identity/Themes/Motifs -@cindex trunk Identity Themes Motifs -@include trunk/Identity/Themes/Motifs.texi - -@node trunk Identity Themes Motifs Flame -@section trunk/Identity/Themes/Motifs/Flame -@cindex trunk Identity Themes Motifs Flame -@include trunk/Identity/Themes/Motifs/Flame.texi - -@node trunk Identity Themes Motifs Modern -@section trunk/Identity/Themes/Motifs/Modern -@cindex trunk Identity Themes Motifs Modern -@include trunk/Identity/Themes/Motifs/Modern.texi - -@node trunk Identity Themes Motifs Modern Backgrounds -@section trunk/Identity/Themes/Motifs/Modern/Backgrounds -@cindex trunk Identity Themes Motifs Modern Backgrounds -@include trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi - -@node trunk Identity Themes Motifs Modern Backgrounds Img -@section trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img -@cindex trunk Identity Themes Motifs Modern Backgrounds Img -@include trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img.texi - -@node trunk Identity Themes Motifs Modern Backgrounds Tpl -@section trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl -@cindex trunk Identity Themes Motifs Modern Backgrounds Tpl -@include trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl.texi - -@node trunk Identity Themes Motifs Modern Backgrounds Xcf -@section trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf -@cindex trunk Identity Themes Motifs Modern Backgrounds Xcf -@include trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf.texi - -@node trunk Identity Themes Motifs Modern Distro Anaconda Progress -@section trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress -@cindex trunk Identity Themes Motifs Modern Distro Anaconda Progress -@include trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi - -@node trunk Identity Themes Motifs Modern Palettes -@section trunk/Identity/Themes/Motifs/Modern/Palettes -@cindex trunk Identity Themes Motifs Modern Palettes -@include trunk/Identity/Themes/Motifs/Modern/Palettes.texi - -@node trunk Identity Themes Motifs TreeFlower -@section trunk/Identity/Themes/Motifs/TreeFlower -@cindex trunk Identity Themes Motifs TreeFlower -@include trunk/Identity/Themes/Motifs/TreeFlower.texi - -@node trunk Identity Themes Motifs TreeFlower Backgrounds -@section trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds -@cindex trunk Identity Themes Motifs TreeFlower Backgrounds -@include trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds.texi - -@node trunk Identity Widgets -@section trunk/Identity/Widgets -@cindex trunk Identity Widgets -@include trunk/Identity/Widgets.texi - -@node trunk Locales -@section trunk/Locales -@cindex trunk Locales -@include trunk/Locales.texi - -@node trunk Locales Identity -@section trunk/Locales/Identity -@cindex trunk Locales Identity -@include trunk/Locales/Identity.texi - -@node trunk Locales Identity Brands -@section trunk/Locales/Identity/Brands -@cindex trunk Locales Identity Brands -@include trunk/Locales/Identity/Brands.texi - -@node trunk Locales Identity Brands Tpl -@section trunk/Locales/Identity/Brands/Tpl -@cindex trunk Locales Identity Brands Tpl -@include trunk/Locales/Identity/Brands/Tpl.texi - -@node trunk Locales Identity Fonts -@section trunk/Locales/Identity/Fonts -@cindex trunk Locales Identity Fonts -@include trunk/Locales/Identity/Fonts.texi - -@node trunk Locales Identity Models -@section trunk/Locales/Identity/Models -@cindex trunk Locales Identity Models -@include trunk/Locales/Identity/Models.texi - -@node trunk Locales Identity Release -@section trunk/Locales/Identity/Release -@cindex trunk Locales Identity Release -@include trunk/Locales/Identity/Release.texi - -@node trunk Locales Identity Themes -@section trunk/Locales/Identity/Themes -@cindex trunk Locales Identity Themes -@include trunk/Locales/Identity/Themes.texi - -@node trunk Locales Identity Themes Backgrounds -@section trunk/Locales/Identity/Themes/Backgrounds -@cindex trunk Locales Identity Themes Backgrounds -@include trunk/Locales/Identity/Themes/Backgrounds.texi - -@node trunk Locales Identity Themes Distro Anaconda Progress -@section trunk/Locales/Identity/Themes/Distro/Anaconda/Progress -@cindex trunk Locales Identity Themes Distro Anaconda Progress -@include trunk/Locales/Identity/Themes/Distro/Anaconda/Progress.texi - -@node trunk Locales Identity Widgets -@section trunk/Locales/Identity/Widgets -@cindex trunk Locales Identity Widgets -@include trunk/Locales/Identity/Widgets.texi - -@node trunk Manuals -@section trunk/Manuals -@cindex trunk Manuals -@include trunk/Manuals.texi - -@node trunk Scripts -@section trunk/Scripts -@cindex trunk Scripts -@include trunk/Scripts.texi - -@node trunk Scripts Bash -@section trunk/Scripts/Bash -@cindex trunk Scripts Bash -@include trunk/Scripts/Bash.texi - -@node trunk Scripts Bash Cli -@section trunk/Scripts/Bash/Cli -@cindex trunk Scripts Bash Cli -@include trunk/Scripts/Bash/Cli.texi - -@node trunk Scripts Bash Cli Functions -@section trunk/Scripts/Bash/Cli/Functions -@cindex trunk Scripts Bash Cli Functions -@include trunk/Scripts/Bash/Cli/Functions.texi - -@node trunk Scripts Bash Cli Functions Help -@section trunk/Scripts/Bash/Cli/Functions/Help -@cindex trunk Scripts Bash Cli Functions Help -@include trunk/Scripts/Bash/Cli/Functions/Help.texi - -@node trunk Scripts Bash Cli Functions Html -@section trunk/Scripts/Bash/Cli/Functions/Html -@cindex trunk Scripts Bash Cli Functions Html -@include trunk/Scripts/Bash/Cli/Functions/Html.texi - -@node trunk Scripts Bash Cli Functions Locale -@section trunk/Scripts/Bash/Cli/Functions/Locale -@cindex trunk Scripts Bash Cli Functions Locale -@include trunk/Scripts/Bash/Cli/Functions/Locale.texi - -@node trunk Scripts Bash Cli Functions Manual -@section trunk/Scripts/Bash/Cli/Functions/Manual -@cindex trunk Scripts Bash Cli Functions Manual -@include trunk/Scripts/Bash/Cli/Functions/Manual.texi - -@node trunk Scripts Bash Cli Functions Path -@section trunk/Scripts/Bash/Cli/Functions/Path -@cindex trunk Scripts Bash Cli Functions Path -@include trunk/Scripts/Bash/Cli/Functions/Path.texi - -@node trunk Scripts Bash Cli Functions Render -@section trunk/Scripts/Bash/Cli/Functions/Render -@cindex trunk Scripts Bash Cli Functions Render -@include trunk/Scripts/Bash/Cli/Functions/Render.texi - -@node trunk Scripts Bash Cli Functions Render Config -@section trunk/Scripts/Bash/Cli/Functions/Render/Config -@cindex trunk Scripts Bash Cli Functions Render Config -@include trunk/Scripts/Bash/Cli/Functions/Render/Config.texi - -@node trunk Scripts Bash Cli Functions Shell -@section trunk/Scripts/Bash/Cli/Functions/Shell -@cindex trunk Scripts Bash Cli Functions Shell -@include trunk/Scripts/Bash/Cli/Functions/Shell.texi - -@node trunk Scripts Bash Cli Functions Svg -@section trunk/Scripts/Bash/Cli/Functions/Svg -@cindex trunk Scripts Bash Cli Functions Svg -@include trunk/Scripts/Bash/Cli/Functions/Svg.texi - -@node trunk Scripts Bash Cli Functions Verify -@section trunk/Scripts/Bash/Cli/Functions/Verify -@cindex trunk Scripts Bash Cli Functions Verify -@include trunk/Scripts/Bash/Cli/Functions/Verify.texi - -@node trunk Scripts Python -@section trunk/Scripts/Python -@cindex trunk Scripts Python -@include trunk/Scripts/Python.texi - diff --git a/Manuals/Filesystem/trunk/chapter.texi b/Manuals/Filesystem/trunk/chapter.texi deleted file mode 100644 index 73ba088..0000000 --- a/Manuals/Filesystem/trunk/chapter.texi +++ /dev/null @@ -1,6 +0,0 @@ -@node trunk -@chapter trunk -@cindex trunk -@include trunk/chapter-intro.texi -@include trunk/chapter-menu.texi -@include trunk/chapter-nodes.texi diff --git a/Manuals/Repository/branches/chapter-intro.texi b/Manuals/Repository/branches/chapter-intro.texi new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/Manuals/Repository/branches/chapter-intro.texi diff --git a/Manuals/Repository/branches/chapter-menu.texi b/Manuals/Repository/branches/chapter-menu.texi new file mode 100644 index 0000000..8b13789 --- /dev/null +++ b/Manuals/Repository/branches/chapter-menu.texi @@ -0,0 +1 @@ + diff --git a/Manuals/Repository/branches/chapter-nodes.texi b/Manuals/Repository/branches/chapter-nodes.texi new file mode 100644 index 0000000..8b13789 --- /dev/null +++ b/Manuals/Repository/branches/chapter-nodes.texi @@ -0,0 +1 @@ + diff --git a/Manuals/Repository/branches/chapter.texi b/Manuals/Repository/branches/chapter.texi new file mode 100644 index 0000000..e053279 --- /dev/null +++ b/Manuals/Repository/branches/chapter.texi @@ -0,0 +1,6 @@ +@node branches +@chapter branches +@cindex branches +@include branches/chapter-intro.texi +@include branches/chapter-menu.texi +@include branches/chapter-nodes.texi diff --git a/Manuals/Repository/filesystem-html/filesystem.html b/Manuals/Repository/filesystem-html/filesystem.html new file mode 100644 index 0000000..0a61430 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem.html @@ -0,0 +1,105 @@ + + + + + + +CentOS Artwork Repository - File System: CentOS Artwork Repository - File System + + + + + + + + + + + + + + + + + + + + + +
[Top][Contents][Index][ ? ]
+

CentOS Artwork Repository - File System

+ +

Copyright © 2009-2011 Alain Reguera Delgado +

+

Permission is granted to copy, distribute and/or modify this document +under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no +Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A +copy of the license is included in the section entitled GNU Free +Documentation License. +

+ + + + + + + +
1. branches   +
2. tags   +
3. trunk   +
Index   +
List of Figures   +
+ + + + + + + + + + +
[Top][Contents][Index][ ? ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_1.html b/Manuals/Repository/filesystem-html/filesystem_1.html new file mode 100644 index 0000000..dabf03b --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_1.html @@ -0,0 +1,96 @@ + + + + + + +CentOS Artwork Repository - File System: 1. branches + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

1. branches

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_10.html b/Manuals/Repository/filesystem-html/filesystem_10.html new file mode 100644 index 0000000..7f1e92f --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_10.html @@ -0,0 +1,119 @@ + + + + + + +CentOS Artwork Repository - File System: 3.7 trunk/Identity/Models/Css + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+ +
    +
  • ... +
+ + + +

3.7.3 Usage

+ +
    +
  • ... +
+ + + +

3.7.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_11.html b/Manuals/Repository/filesystem-html/filesystem_11.html new file mode 100644 index 0000000..5a1c1e9 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_11.html @@ -0,0 +1,120 @@ + + + + + + +CentOS Artwork Repository - File System: 3.8 trunk/Identity/Models/Html + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.8 trunk/Identity/Models/Html

+ + + +

3.8.1 Goals

+ +
    +
  • ... +
+ + + +

3.8.2 Description

+ +
    +
  • ... +
+ + + +

3.8.3 Usage

+ +
    +
  • ... +
+ + + +

3.8.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_12.html b/Manuals/Repository/filesystem-html/filesystem_12.html new file mode 100644 index 0000000..8601e56 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_12.html @@ -0,0 +1,124 @@ + + + + + + +CentOS Artwork Repository - File System: 3.9 trunk/Identity/Models/Img/Promo/Web + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+ + + +

3.9.1 Goals

+ +
    +
  • Provide images related to CentOS web interface. +
+ + + +

3.9.2 Description

+ +
    +
  • ... +
+ + + +

3.9.3 Usage

+ +
    +
  • ... +
+ + + +

3.9.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_13.html b/Manuals/Repository/filesystem-html/filesystem_13.html new file mode 100644 index 0000000..dccc572 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_13.html @@ -0,0 +1,120 @@ + + + + + + +CentOS Artwork Repository - File System: 3.10 trunk/Identity/Models/Tpl + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.10 trunk/Identity/Models/Tpl

+ + + +

3.10.1 Goals

+ +
    +
  • ... +
+ + + +

3.10.2 Description

+ +
    +
  • ... +
+ + + +

3.10.3 Usage

+ +
    +
  • ... +
+ + + +

3.10.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_14.html b/Manuals/Repository/filesystem-html/filesystem_14.html new file mode 100644 index 0000000..224e014 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_14.html @@ -0,0 +1,428 @@ + + + + + + +CentOS Artwork Repository - File System: 3.11 trunk/Identity/Models/Tpl/Promo/Web + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+
    +
  • One unique name and one unique visual style to all web +applications used inside the web environment. + +
  • One-step navigation to web applications inside the environment. + +
  • High degree of customization to change the visual style of all +web applications with few changes (e.g, updating just two or three +images plus common style sheet [CSS] definitions). +
+ +

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 that used by MoinMoin. +

+

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

+

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

+

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

+ + +

3.11.2.1 Design model (without ads)

+ + + +

3.11.2.2 Design model (with ads)

+ + + +

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

+ + +

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 the diff command of Subversion 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

+ +
    +
  • ... +
+ + + +

3.11.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_15.html b/Manuals/Repository/filesystem-html/filesystem_15.html new file mode 100644 index 0000000..23e7f95 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_15.html @@ -0,0 +1,120 @@ + + + + + + +CentOS Artwork Repository - File System: 3.12 trunk/Identity/Models/Xcf + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.12 trunk/Identity/Models/Xcf

+ + + +

3.12.1 Goals

+ +
    +
  • ... +
+ + + +

3.12.2 Description

+ +
    +
  • ... +
+ + + +

3.12.3 Usage

+ +
    +
  • ... +
+ + + +

3.12.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_16.html b/Manuals/Repository/filesystem-html/filesystem_16.html new file mode 100644 index 0000000..1f74aac --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_16.html @@ -0,0 +1,112 @@ + + + + + + +CentOS Artwork Repository - File System: 3.13 trunk/Identity/Release + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.13 trunk/Identity/Release

+ + + +

3.13.1 Goals

+ +
    +
  • ... +
+ + + +

3.13.2 Description

+ + + +

3.13.3 Usage

+ + + +

3.13.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_17.html b/Manuals/Repository/filesystem-html/filesystem_17.html new file mode 100644 index 0000000..8dc944c --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_17.html @@ -0,0 +1,130 @@ + + + + + + +CentOS Artwork Repository - File System: 3.14 trunk/Identity/Themes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.14 trunk/Identity/Themes

+ + + +

3.14.1 Goals

+ +

The `trunk/Identity/Themes/' directory exists to organize +production of CentOS themes. +

+ + +

3.14.2 Description

+ + + +

3.14.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.15 trunk/Identity/Themes/Models   +
3.22 trunk/Identity/Themes/Motifs   +
+ + + +

3.14.4 See also

+ + + + +
3.1 trunk/Identity   +
3. trunk   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_18.html b/Manuals/Repository/filesystem-html/filesystem_18.html new file mode 100644 index 0000000..c7ac743 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_18.html @@ -0,0 +1,126 @@ + + + + + + +CentOS Artwork Repository - File System: 3.15 trunk/Identity/Themes/Models + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.15 trunk/Identity/Themes/Models

+ + + +

3.15.1 Goals

+ +
    +
  • Organize theme models. +
+ + + +

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_19.html b/Manuals/Repository/filesystem-html/filesystem_19.html new file mode 100644 index 0000000..456cc70 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_19.html @@ -0,0 +1,124 @@ + + + + + + +CentOS Artwork Repository - File System: 3.16 trunk/Identity/Themes/Models/Alternative + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.16 trunk/Identity/Themes/Models/Alternative

+ + + +

3.16.1 Goals

+ +
    +
  • ... +
+ + + +

3.16.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.16.3 Usage

+ +
    +
  • ... +
+ + + +

3.16.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_2.html b/Manuals/Repository/filesystem-html/filesystem_2.html new file mode 100644 index 0000000..d24ef20 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_2.html @@ -0,0 +1,96 @@ + + + + + + +CentOS Artwork Repository - File System: 2. tags + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

2. tags

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_20.html b/Manuals/Repository/filesystem-html/filesystem_20.html new file mode 100644 index 0000000..fcb397b --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_20.html @@ -0,0 +1,125 @@ + + + + + + +CentOS Artwork Repository - File System: 3.17 trunk/Identity/Themes/Models/Default + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.17 trunk/Identity/Themes/Models/Default

+ + + +

3.17.1 Goals

+ +

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

+ + +

3.17.2 Description

+ + + +

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_21.html b/Manuals/Repository/filesystem-html/filesystem_21.html new file mode 100644 index 0000000..04deb2c --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_21.html @@ -0,0 +1,184 @@ + + + + + + +CentOS Artwork Repository - File System: 3.18 trunk/Identity/Themes/Models/Default/Distro + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+ + + +

3.18.1 Goals

+ +
    +
  • ... +
+ + + +

3.18.2 Description

+ +

It applies to all major releases of CentOS distribution. +

+ + +

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

+

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

+ + +

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

+

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

+ + + +

3.18.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_22.html b/Manuals/Repository/filesystem-html/filesystem_22.html new file mode 100644 index 0000000..a3752c0 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_22.html @@ -0,0 +1,112 @@ + + + + + + +CentOS Artwork Repository - File System: 3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+ + + +

3.19.1 Goals

+ +
    +
  • ... +
+ + + +

3.19.2 Description

+ + + +

3.19.3 Usage

+ + + +

3.19.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_23.html b/Manuals/Repository/filesystem-html/filesystem_23.html new file mode 100644 index 0000000..4ace555 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_23.html @@ -0,0 +1,125 @@ + + + + + + +CentOS Artwork Repository - File System: 3.20 trunk/Identity/Themes/Models/Default/Promo + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+ + + +

3.20.1 Goals

+ +
    +
  • ... +
+ + + +

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

+ +
    +
  • ... +
+ + + +

3.20.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_24.html b/Manuals/Repository/filesystem-html/filesystem_24.html new file mode 100644 index 0000000..7fd1cf6 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_24.html @@ -0,0 +1,124 @@ + + + + + + +CentOS Artwork Repository - File System: 3.21 trunk/Identity/Themes/Models/Default/Web + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+ + + +

3.21.1 Goals

+ +
    +
  • ... +
+ + + +

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

+ +
    +
  • ... +
+ + + +

3.21.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_25.html b/Manuals/Repository/filesystem-html/filesystem_25.html new file mode 100644 index 0000000..92bb64d --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_25.html @@ -0,0 +1,214 @@ + + + + + + +CentOS Artwork Repository - File System: 3.22 trunk/Identity/Themes/Motifs + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.22 trunk/Identity/Themes/Motifs

+ + + +

3.22.1 Goals

+ +

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

+
    +
  • Organize CentOS themes' artistic motifs. +
+ + + + +

3.22.2 Description

+ +

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

+

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

+
+
`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 the name of your artistic motif. If +possible, when creating new conceptual ideas for CentOS, think about +what CentOS means for you, what does it makes you feel, take your +time, think deep, and share; you can improve the idea as time goes on. +

+

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

+

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

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

The previous command will create the basic structure of themes 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

+ +

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

+
    +
  • Give a unique (case-sensitive) name to your Motif. This name is +used as value wherever theme variable ($THEME) or translation marker +(=THEME=) is. Optionally, you can add a description about +inspiration and concepts behind your work. + +
  • Use the location `trunk/Identity/Themes/Motifs/$THEME/' to +store your work. If it doesn't exist create it. Note that this require +you to have previous commit access in CentOS Artwork Repository. + +
  • The CentOS Project is using the blue color (#204c8d) as base +color for its corporate visual identity. Use such base corporate color +information as much as possible in your artistic motif designs. + +
  • Try to make your design fit one of the theme models. + +
  • Feel free to make your art enterprise-level and beautiful. + +
  • Add the following information on your artwork (both in a visible +design area and document metadata): + + +
+ + + +

3.22.4 See also

+ + + + + +
3.14 trunk/Identity/Themes   +
3.1 trunk/Identity   +
3. trunk   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_26.html b/Manuals/Repository/filesystem-html/filesystem_26.html new file mode 100644 index 0000000..fed8f16 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_26.html @@ -0,0 +1,315 @@ + + + + + + +CentOS Artwork Repository - File System: 3.23 trunk/Identity/Themes/Motifs/Flame + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.23 trunk/Identity/Themes/Motifs/Flame

+ + + +

3.23.1 Goals

+ +

This section describes the steps we followed to construct the +Flame artistic motif. This section may be useful for anyone +interested in reproducing the Flame artistic motif, or in +creating new artistic motifs for The CentOS Project corporate visual +identity (see section trunk/Identity). +

+ + +

3.23.2 Description

+ +

The Flame artistic motif was built using the flame filter of +Gimp 2.2 in CentOS 5.5. +

+

The flame filter of Gimp can produce stunning, randomly generated +fractal patterns. The flame filter of Gimp gives us a great oportunity +to reduce the time used to produce new artistic motifs, because of its +"randomly generated" nature. Once the artistic motif be created, it +is propagated through all visual manifestations of CentOS Project +corporate visual identity using the `centos-art.sh' script +(see section trunk/Scripts/Bash) inside the CentOS Artwork Repository. +

+

To set the time intervals between each new visual style production, we +could reuse the CentOS distribution major release schema. I.e., we +could produce a new visual style, every two years, based on a new +"randomly generated" flame pattern, and publish the whole corporate +visual identity (i.e., distribution stuff, promotion stuff, websites +stuff, etc.) with the new major release of CentOS distribution all +together at once. +

+

Producing a new visual style is not one day's task. Once we have +defined the artistic motif, we need to propagate it through all visual +manifestations of The CentOS Project corporate visual identity. When +we say that we could produce one new visual style every two years we +really mean: to work two years long in order to propagate a new visual +style to all visual manifestations of The CentOS Project corporate +visual identity. +

+

Obviously, in order to propagate one visual style to all different +visual manifestations of The CentOS Project corporate visual identity, +we need first to know which the visual manifestations are. To define +which visual manifestations are inside The CentOS Project corporate +visual identity is one of the goals the CentOS Artwork Repository and +this documentation manual are both aimed to satisfy. +

+

Once we define which the visual manifestation are, it is possible to +define how to produce them, and this way, organize the automation +process. Such automation process is one of the goals of +`centos-art.sh' script. +

+

With the combination of both CentOS Artwork Repository and +`centos-art.sh' scripts we define work lines where translators, +programmers, and graphic designers work together to distribute and +reduce the amount of time employed to produce The CentOS Project +monolithic corporate identity. +

+

From a monolithic corporate visual identity point of view, notice that +we are producing a new visual style for the same theme (i.e., +Flame). It would be another flame design but still a flame +design. This idea is very important to be aware of, because we are +somehow "refreshing" the theme, not changing it at all. +

+

This way, as we are "refreshing" the theme, we still keep oursleves +inside the monolithic conception we are trying to be attached to +(i.e., one unique name, and one unique visual style for all visual +manifestations). +

+

Producing artistic motifs is a creative process that may consume long +time, specially for people without experienced knowledge on graphic +design land. Using "randomly generated" conception to produce +artistic motifs could be, practically, a way for anyone to follow in +order to produce maintainable artistic motifs in few steps. +

+

Due to the "randomly generated" nature of Flame filter, we find that +Flame pattern is not always the same when we use Flame +filter interface. +

+

Using the same pattern design for each visual manifestation is +essential in order to maintain the visual connection among all visual +manifestations inside the same theme. Occasionally, we may introduce +pattern variations in opacity, size, or even position but never change +the pattern design itself, nor the color information used by images +considered part of the same theme. +

+
Important

Important

+When we design background images, which are considered part of the +same theme, it is essential to use the same design pattern always. +This is what makes theme images to be visually connected among +themeselves, and so, the reason we use to define the word "theme" +as: a set of images visually connected among themeselves. +

+ +

In order for us to reproduce the same flame pattern always, +Flame filter interface provides the `Save' and `Open' +options. The `Save' option brings up a file save dialog that +allows you to save the current Flame settings for the plug-in, so that +you can recreate them later. The `Open' option brings up a file +selector that allows you to open a previously saved Flame settings +file. +

+

The Flame settings we used in our example are saved in the file: +

+
trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def
+
+ + +

3.23.3 Construction

+ + + +

3.23.3.1 Step 1: Set image size

+ +

Create an empty image and fill the `Background' layer with black +(000000) color. Image dimensions depend on the final +destination you plan to use the image for. For the sake of our +construction example we used an image of 640x480 pixels and 300 pixels +per inch (ppi). +

+ + +

3.23.3.2 Step 2: Add base color and pattern information

+ +

Create a new layer named `Base', place it over `Background' +layer and fill it with the base color (7800ff) you want to have +your background image set in. Add a mask to `Base' layer using +radial gradient and blur it. You may need to repeat this step more +than once in order to achieve a confortable black radial degradation +on the right side of your design. +

+

Duplicate `Base' layer and name it `Paper'. Place +`Paper' layer over `Base' layer. Remove content of +`Paper' layer and fill it with `Paper (100x100)' pattern. +Once you've done with black radial degradation, reduce the +`Paper' layer opacity to 20%. +

+

Notice that when we duplicate one layer, the mask information related +to layer is preserved from previous to next layer. This saves us some +of the time required to produce different layers with the same mask +information on them. +

+

Duplicate `Paper' layer and rename it `Stripes'. Remove +paper pattern from `Stripes' layer. Fill `Stripes' layer +with `Stripes (48x48)' pattern and reduce the `Stripes' +layer opacity to 15%. +

+ + +

3.23.3.3 Step 3: Add flame motif

+ +

Create a new layer named `Flame'. Set the foreground +(003cff) and background (0084ff) colors to the gradient +you want to build the flame motif. +

+

To build flame motif, use the flame filter (`Filters > Render > +Nature > Flame...') on `Flame' layer. We used a layer mask, with +a radial gradient on it to control the boundaries of flame motif on +`Flame' layer. +

+

Duplicate `Flame' layer and rename it `Flame Blur'. Place `Flame +Blur' below `Flame' layer. Apply Gussian blur filter +(`Filters > Blur > Gussian Blur...') until reaching the desiered +effect. +

+

The opacity value, in `Flame' layers, may vary from one image to +another based on the place the image will be finally placed on. For +example, images used as desktop background have the `Flame' layer +opacity set at 100% but `Flame Blur' is set to 70%. However, you +may find that background images used in anaconda progress slides have +opacity reduced differently, in order to reduce brightness in a way +that texts could look clean and readable over it. +

+ + +

3.23.3.4 Step 4: Add foreground color

+ +

Create a new layer named `Color', place it on top of all visible +layers and fill it with plain color (4c005a). Reduce +`Color' layer opacity to 20%. You can use the `Color' layer +to control the right side color information you want to produce the +image for. +

+

Duplicate `Flame' layer and create a new layer named +`Color#1'. Place `Color#1' layer on top of layer named +`Color'. Remove the mask information from `Color#1' layer +and recreate a new one using an inverted alpha channel as reference. +Remove `Color#1' layer content and fill it back with plain black +(000000) color. Reduce `Color#1' opacity to 20%. In this +step we created a mask to protect the flame artistic motif from black +color, so when we decrement or increment the opacity of layer, the +flame artistic motif wouldn't be affected, just the environment +suround it. +

+

When you set color information, remember that the same artistic motif +needs to be indexed to 14 and 16 colors, in order to produce Grub and +Syslinux visual manifestations respectively. Using many different +colors in the artistic motif may reduce the possibility of your design +to fix all different situations in. Likewise, using more colors in +one design, and less colors in another design will reduce the +connectivity among your designs, since color information is relevant +to visual identity. +

+

When you propagate your artistic motif visual style to different +visual manifestations of CentOS Project corporate visual identity, it +is up to you to find out justice and compromise among all possible +variables you may face. +

+ + +

3.23.4 See also

+ + + + + + +
3.22 trunk/Identity/Themes/Motifs   +
3.14 trunk/Identity/Themes   +
3.1 trunk/Identity   +
3. trunk   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_27.html b/Manuals/Repository/filesystem-html/filesystem_27.html new file mode 100644 index 0000000..73182d3 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_27.html @@ -0,0 +1,112 @@ + + + + + + +CentOS Artwork Repository - File System: 3.24 trunk/Identity/Themes/Motifs/Modern + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.24 trunk/Identity/Themes/Motifs/Modern

+ + + +

3.24.1 Presentation

+ + + +

3.24.2 Construction

+ + + +

3.24.3 Usage

+ +
    +
  • ... +
+ + + +

3.24.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_28.html b/Manuals/Repository/filesystem-html/filesystem_28.html new file mode 100644 index 0000000..e143fa0 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_28.html @@ -0,0 +1,229 @@ + + + + + + +CentOS Artwork Repository - File System: 3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+ + + +

3.25.1 Goals

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

3.25.2 Description

+ +

Inside `Motifs' directory, the `Backgrounds/' directory is +used to 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 the import feautre of +Inkscape. +

+

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 (e.g. Anaconda), 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 artistic +motif. +

+

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

+

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

+

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

+

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

+

Each artistic motif directory represents just one unique artistic +motif. +

+

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

+

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

+ +

Inside CentOS Artwork Repository, theme visual styles (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 `Motifs/' directory using +the model name, and the model directory structure as reference. +

+

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

+ + +

3.25.3 Usage

+ +

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

+ + +

3.25.4 See also

+ + + + + +
3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img   +
3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl   +
3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf   +
+ + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_29.html b/Manuals/Repository/filesystem-html/filesystem_29.html new file mode 100644 index 0000000..8aa6f9c --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_29.html @@ -0,0 +1,117 @@ + + + + + + +CentOS Artwork Repository - File System: 3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+ + + +

3.26.1 Goals

+ +
    +
  • ... +
+ + + +

3.26.2 Description

+ + + +

3.26.3 Usage

+ +

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

+ + +

3.26.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_3.html b/Manuals/Repository/filesystem-html/filesystem_3.html new file mode 100644 index 0000000..d8922c3 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_3.html @@ -0,0 +1,215 @@ + + + + + + +CentOS Artwork Repository - File System: 3. trunk + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3. trunk

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
3.1 trunk/Identity   +
3.2 trunk/Identity/Brands   +
3.3 trunk/Identity/Fonts   +
3.4 trunk/Identity/Icons   +
3.5 trunk/Identity/Isolinux   +
3.6 trunk/Identity/Models   +
3.7 trunk/Identity/Models/Css   +
3.8 trunk/Identity/Models/Html   +
3.9 trunk/Identity/Models/Img/Promo/Web   +
3.10 trunk/Identity/Models/Tpl   +
3.11 trunk/Identity/Models/Tpl/Promo/Web   +
3.12 trunk/Identity/Models/Xcf   +
3.13 trunk/Identity/Release   +
3.14 trunk/Identity/Themes   +
3.15 trunk/Identity/Themes/Models   +
3.16 trunk/Identity/Themes/Models/Alternative   +
3.17 trunk/Identity/Themes/Models/Default   +
3.18 trunk/Identity/Themes/Models/Default/Distro   +
3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda   +
3.20 trunk/Identity/Themes/Models/Default/Promo   +
3.21 trunk/Identity/Themes/Models/Default/Web   +
3.22 trunk/Identity/Themes/Motifs   +
3.23 trunk/Identity/Themes/Motifs/Flame   +
3.24 trunk/Identity/Themes/Motifs/Modern   +
3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds   +
3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img   +
3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl   +
3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf   +
3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress   +
3.30 trunk/Identity/Themes/Motifs/Modern/Palettes   +
3.31 trunk/Identity/Themes/Motifs/TreeFlower   +
3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds   +
3.33 trunk/Identity/Widgets   +
3.34 trunk/Locales   +
3.35 trunk/Locales/Identity   +
3.36 trunk/Locales/Identity/Brands   +
3.37 trunk/Locales/Identity/Brands/Tpl   +
3.38 trunk/Locales/Identity/Fonts   +
3.39 trunk/Locales/Identity/Models   +
3.40 trunk/Locales/Identity/Release   +
3.41 trunk/Locales/Identity/Themes   +
3.42 trunk/Locales/Identity/Themes/Backgrounds   +
3.43 trunk/Locales/Identity/Themes/Distro/Anaconda/Progress   +
3.44 trunk/Locales/Identity/Widgets   +
3.45 trunk/Manuals   +
3.46 trunk/Scripts   +
3.47 trunk/Scripts/Bash   +
3.48 trunk/Scripts/Bash/Cli   +
3.49 trunk/Scripts/Bash/Cli/Functions   +
3.50 trunk/Scripts/Bash/Cli/Functions/Help   +
3.51 trunk/Scripts/Bash/Cli/Functions/Html   +
3.52 trunk/Scripts/Bash/Cli/Functions/Locale   +
3.53 trunk/Scripts/Bash/Cli/Functions/Manual   +
3.54 trunk/Scripts/Bash/Cli/Functions/Path   +
3.55 trunk/Scripts/Bash/Cli/Functions/Render   +
3.56 trunk/Scripts/Bash/Cli/Functions/Render/Config   +
3.57 trunk/Scripts/Bash/Cli/Functions/Shell   +
3.58 trunk/Scripts/Bash/Cli/Functions/Svg   +
3.59 trunk/Scripts/Bash/Cli/Functions/Verify   +
3.60 trunk/Scripts/Python   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_30.html b/Manuals/Repository/filesystem-html/filesystem_30.html new file mode 100644 index 0000000..7a62563 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_30.html @@ -0,0 +1,116 @@ + + + + + + +CentOS Artwork Repository - File System: 3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+ + + +

3.27.1 Goals

+ +
    +
  • ... +
+ + + +

3.27.2 Description

+ + + +

3.27.3 Usage

+ +

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

+ + +

3.27.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_31.html b/Manuals/Repository/filesystem-html/filesystem_31.html new file mode 100644 index 0000000..9635974 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_31.html @@ -0,0 +1,125 @@ + + + + + + +CentOS Artwork Repository - File System: 3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+ + + +

3.28.1 Goals

+ +
    +
  • ... +
+ + + +

3.28.2 Description

+ +
    +
  • ... +
+ + + + +

3.28.3 Usage

+ +

In this directory is where you store the project files (e.g, .xcf) of +Gimp. 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 background projects. Of course, you can +merge both Gimp and Inkscape power to produce images based on them. +In this last case you need the `Xcf/' directory. +

+ + +

3.28.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_32.html b/Manuals/Repository/filesystem-html/filesystem_32.html new file mode 100644 index 0000000..87ff40b --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_32.html @@ -0,0 +1,153 @@ + + + + + + +CentOS Artwork Repository - File System: 3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+ + + +

3.29.1 Goals

+ +
    +
  • ... +
+ + + +

3.29.2 Description

+ + + +

3.29.3 Usage

+ +

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

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

The above command will create the following structure: +

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

3.29.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_33.html b/Manuals/Repository/filesystem-html/filesystem_33.html new file mode 100644 index 0000000..17e301e --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_33.html @@ -0,0 +1,118 @@ + + + + + + +CentOS Artwork Repository - File System: 3.30 trunk/Identity/Themes/Motifs/Modern/Palettes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+ + + +

3.30.1 Goals

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

3.30.2 Description

+ + + +

3.30.3 Usage

+ +

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 the unique color information +required by theme. +

+ + +

3.30.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_34.html b/Manuals/Repository/filesystem-html/filesystem_34.html new file mode 100644 index 0000000..c0995a1 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_34.html @@ -0,0 +1,112 @@ + + + + + + +CentOS Artwork Repository - File System: 3.31 trunk/Identity/Themes/Motifs/TreeFlower + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.31 trunk/Identity/Themes/Motifs/TreeFlower

+ + + +

3.31.1 Goals

+ +
    +
  • ... +
+ + + +

3.31.2 Description

+ + + +

3.31.3 Usage

+ + + +

3.31.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_35.html b/Manuals/Repository/filesystem-html/filesystem_35.html new file mode 100644 index 0000000..84faa76 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_35.html @@ -0,0 +1,424 @@ + + + + + + +CentOS Artwork Repository - File System: 3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

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

+ + + +

3.32.1 Goals

+ +

This section exists to orgnize backgrounds of TreeFlower +artistic motif. +

+ + +

3.32.2 Description

+ + + +

3.32.2.1 Desktop background

+ +

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

+

Open the png version with GIMP. +

+

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

+

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

+
+
Layer 1: Background
+
+

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

+
+
Layer 2: Shadow#1
+
+

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

+
+
Layer 3: Shadow#2
+
+

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

+
+
Layer 4: Pattern (Paper)
+
+

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

+
+
Layer 5: Pattern (Stripes)
+
+

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

+
+
Layer 6: Shadow#3
+
+

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

+
+
Layer 7: Shadow#4
+
+

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

+
+
Layer 8: Color#1
+
+

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

+
+
Layer 9: Color#2
+
+

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

+
+
+ +
info

Note

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

+ +

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

+

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

+ + +

3.32.2.2 Anaconda Prompt (syslinux) background

+ +

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

+

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

+

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

+
+
Layer 1: Background
+
+

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

+
+
Layer 2: Pattern (Paper)
+
+

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

+
+
Layer 3: Pattern (Stripes)
+
+

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

+
+
Layer 4: Shadow#1
+
+

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

+
+
Layer 5: Color#1
+
+

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

+
+
Layer 6: Color#2
+
+

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

+
+
Layer 7: Shadow#2
+
+

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

+
+
+ +

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

+

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

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

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

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

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

+

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

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

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

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

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

+

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

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

to +

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

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

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

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

+

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

+

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

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

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

+

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

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

3.32.2.3 Grub background

+ + + +

3.32.3 Usage

+ +
    +
  • ... +
+ + + +

3.32.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_36.html b/Manuals/Repository/filesystem-html/filesystem_36.html new file mode 100644 index 0000000..0f90440 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_36.html @@ -0,0 +1,112 @@ + + + + + + +CentOS Artwork Repository - File System: 3.33 trunk/Identity/Widgets + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.33 trunk/Identity/Widgets

+ + + +

3.33.1 Goals

+ +
    +
  • ... +
+ + + +

3.33.2 Description

+ + + +

3.33.3 Usage

+ + + +

3.33.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_37.html b/Manuals/Repository/filesystem-html/filesystem_37.html new file mode 100644 index 0000000..3297d47 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_37.html @@ -0,0 +1,149 @@ + + + + + + +CentOS Artwork Repository - File System: 3.34 trunk/Locales + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.34 trunk/Locales

+ +

The `trunk/Locales' directory exists to store the translation +messages used to produce content in different languages. +

+

Translation messages are organized using the directory structure of +the component being translated. For example, if we want to provide +translation messages for `trunk/Manuals/Filesystem', then the +`trunk/Locales/Manuals/Filesystem' directory needs to be created. +

+

Once the locale directory exists for the component we want to provide +translation messages for, it is necessary to create the translation +files where translation messages are. The translation files follows +the concepts of xml2po and GNU gettext tools. +

+

The basic translation process is as follow: first, translatable +strings are extracted from files and a portable object template (.pot) +is created or updated with the information. Using the portable object +template, a portable object (.po) is created or updated for translator +to locale the messages retrived. Finally, a machine object (.mo) is +created from portable object to sotore the translated messages. +

+

Inside the repository there are two ways to retrive translatable +strings from files. The first one is through xml2po command +and the second through xgettext command. The xml2po +is used to retrive translatable strings from XML files (e.g., Scalable +Vector Graphics, DocBook, etc.) and the xgettext command is +used to retrive translatable strings from shell scripts files (e.g., +the files that make the centos-art.sh command-line +interface). +

+

When translatable strings are retrived from XML files, using the +xml2po command, there is no need to create the machine +object as we do when translatable strings ar retrived from shell +files, using the xgettext command. The xml2po +produces a temporal machine object in order to create a translated XML +file. Once the translated XML file has been created the machine object +is no longer needed. On the other hand, the machine object produced by +the xgettext command is required by the system in order for +the show shell script localized messages. +

+

Another difference between xml2po and xgettext we +need to be aware of is the directory structure used to store machine +objects. In xml2po, the machine object is created in the +current working directory as `.xml2po.mo' and can be safetly +removed once the translated XML file has been created. In the case of +xgettext, the machine object needs to be stored in the +`$TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo' file in order +for the system to interpret it and should not be removed since it is +the file that contain the translation messages themselves. +

+

Automation of localization tasks is achived through the locale +functionality of command-line interface. +

+ + +
3.52 trunk/Scripts/Bash/Cli/Functions/Locale   +
+ + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_38.html b/Manuals/Repository/filesystem-html/filesystem_38.html new file mode 100644 index 0000000..0113c6b --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_38.html @@ -0,0 +1,124 @@ + + + + + + +CentOS Artwork Repository - File System: 3.35 trunk/Locales/Identity + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.35 trunk/Locales/Identity

+ + + +

3.35.1 Goals

+ +
    +
  • ... +
+ + + +

3.35.2 Description

+ +
    +
  • ... +
+ + + +

3.35.3 Usage

+ +
    +
  • ... +
+ + + +

3.35.4 See also

+ + + +
3.1 trunk/Identity   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_39.html b/Manuals/Repository/filesystem-html/filesystem_39.html new file mode 100644 index 0000000..310233c --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_39.html @@ -0,0 +1,204 @@ + + + + + + +CentOS Artwork Repository - File System: 3.36 trunk/Locales/Identity/Brands + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.36 trunk/Locales/Identity/Brands

+ + + +

3.36.1 Goals

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

3.36.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.36.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.36.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 designing ratio. +

+

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

+

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

+ + +

3.36.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.36.3 Usage

+ +

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

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

3.36.4 See also

+ + + +
3.2 trunk/Identity/Brands   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_4.html b/Manuals/Repository/filesystem-html/filesystem_4.html new file mode 100644 index 0000000..83184c6 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_4.html @@ -0,0 +1,233 @@ + + + + + + +CentOS Artwork Repository - File System: 3.1 trunk/Identity + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.1 trunk/Identity

+ + + +

3.1.1 Goals

+ +

The `trunk/Identity' directory exists to organize CentOS +corporate identity artworks. +

+ + +

3.1.2 Description

+ +

The CentOS Project corporate identity is the "persona" of the +organization known as The CentOS Project. The CentOS Project +corporate identity plays a significant role in the way the CentOS +Project, as organization, presents itself to both internal and +external stakeholders. In general terms, the CentOS Project corporate +visual identity expresses the values and ambitions of the CentOS +Project organization, its business, and its characteristics. +

+

The CentOS Project corporate identity provides visibility, +recognizability, reputation, structure and identification to the +CentOS Project organization by means of corporate design, corporate +communication, and corporate behaviour. +

+

The CentOS Project settles down its corporate visual identity on a +"monolithic corporate visual identity structure". In this structure +The CentOS Project uses one unique name (The CentOS Brand) and one +unique visual style (The CentOS Default Theme) in all its +manifestations. +

+
+
The CentOS Brands
+

The CentOS brand is the name or trademark that conncects the producer +with their products. In this case, the producer is The CentOS Project +and the products are the CentOS distributions, the CentOS web sites, +the CentOS promotion stuff, etc. +

+

See section trunk/Identity/Brands, for more information. +

+
+
The CentOS Themes
+
+

The CentOS themes are a set of image files connected all together by +one unique visual style. Each theme is organized in different visual +manifestations, in order to cover each visual manifestation of The +CentOS Project (i.e., distributions, websites, promotion stuff, etc.). +See section trunk/Identity/Themes, for more information. +

+
+ +

Inside a monolithic corporate visual identity structure, internal and +external stakeholders use to feel a strong sensation of uniformity, +orientation, and identification with the organization. No matter if +you are visiting websites, using the distribution, or acting on social +events, the one unique name and one unique visual style conect them +all to say: Hey! we are all parts of the CentOS project. And, +probably, some vister will say: Can I join the party? Yes you can, it +is free. :) +

+ + +

3.1.3 Usage

+ +

To produce identity artworks, use the following commands: +

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

When `path/to/dir' refers to one renderable directory under +`trunk/Identity', this command renders identity artworks using +both related design models and related translation files. +

+
+
`centos-art render 'path/to/dir' --filter='pattern''
+
+

When `path/to/dir' refers to one renderable directory under +`trunk/Identity', this command renders identity artworks using +both related design models and related translation files that match +the regular expression passed in `--filter='pattern'' argument. +

+

To control the number of files produced by centos-art +command, you need to look into the translation path and provide a +regular expression pattern that matches the translation path, or +paths, related to the file, or files, you want to produce. +

+

The regular expression pattern you provide to centos-art +command is applied to the translation path from its very beginning. +It is not the same to say `5/en/01-welcome' that +`01-welcome', the frist expression matches but the last one does +not. +

+

When using `--filter='pattern'' you don't need to specify the +file extension. It is removed from translation path before applying +the pattern, so it doesn't count here. +

+
+ + + +

3.1.4 File name convenctions

+ +

As file name convenction, inside CentOS Artwork Repository, both +text-based and image-based file name produced by centos-art.sh +script has the same name of their translation files without +the `.sed' extension. The file extension is set as follow: +

+ + +

3.1.4.1 When text-based files are rendered

+ +

Text-based files end up having the same extension of their design +template file. +

+ + +

3.1.4.2 When image-based files are rendered

+ +

Image-based files always end up having the `.png' extension. +

+
Info

Tip

Once `.png' images are created, other image formats +may be created using the renderFormats post-rendering +action, inside the image-based related pre-rendering configuration +script. +

+

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

+ + + +

3.1.5 See also

+ + + + +

3.1.6 References

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_40.html b/Manuals/Repository/filesystem-html/filesystem_40.html new file mode 100644 index 0000000..1f791dd --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_40.html @@ -0,0 +1,108 @@ + + + + + + +CentOS Artwork Repository - File System: 3.37 trunk/Locales/Identity/Brands/Tpl + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.37 trunk/Locales/Identity/Brands/Tpl

+ + + +

3.37.1 Goals

+ + + +

3.37.2 Description

+ + + +

3.37.3 Usage

+ + + +

3.37.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_41.html b/Manuals/Repository/filesystem-html/filesystem_41.html new file mode 100644 index 0000000..e47ea70 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_41.html @@ -0,0 +1,162 @@ + + + + + + +CentOS Artwork Repository - File System: 3.38 trunk/Locales/Identity/Fonts + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.38 trunk/Locales/Identity/Fonts

+ + + +

3.38.1 Goals

+ +

This section exists to organize fonts translation files. +

+ +

3.38.2 Description

+ +

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

+
s!font-family:Denmark!font-family:DejaVu LGC Sans!
+s!font-weight:normal!font-weight:bold!
+s!font-style:normal!font-style:italic!
+
+

Inside `trunk/Translations/Fonts', there is one translation file +for each font preview image you want to produce. This way, we create +one translation file for each font-family we use somewhere inside +CentOS visual identity. +

+
Important

Important

Do not create translation files for +font-families not used somewhere inside CentOS visual identity. The +identity of font 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.38.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.38.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.38.4 See also

+ + + +
3.3 trunk/Identity/Fonts   +
+ + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_42.html b/Manuals/Repository/filesystem-html/filesystem_42.html new file mode 100644 index 0000000..20f2397 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_42.html @@ -0,0 +1,108 @@ + + + + + + +CentOS Artwork Repository - File System: 3.39 trunk/Locales/Identity/Models + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.39 trunk/Locales/Identity/Models

+ + + +

3.39.1 Goals

+ + + +

3.39.2 Description

+ + + +

3.39.3 Usage

+ + + +

3.39.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_43.html b/Manuals/Repository/filesystem-html/filesystem_43.html new file mode 100644 index 0000000..6622bd2 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_43.html @@ -0,0 +1,108 @@ + + + + + + +CentOS Artwork Repository - File System: 3.40 trunk/Locales/Identity/Release + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.40 trunk/Locales/Identity/Release

+ + + +

3.40.1 Goals

+ + + +

3.40.2 Description

+ + + +

3.40.3 Usage

+ + + +

3.40.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_44.html b/Manuals/Repository/filesystem-html/filesystem_44.html new file mode 100644 index 0000000..c2113bc --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_44.html @@ -0,0 +1,108 @@ + + + + + + +CentOS Artwork Repository - File System: 3.41 trunk/Locales/Identity/Themes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.41 trunk/Locales/Identity/Themes

+ + + +

3.41.1 Goals

+ + + +

3.41.2 Description

+ + + +

3.41.3 Usage

+ + + +

3.41.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_45.html b/Manuals/Repository/filesystem-html/filesystem_45.html new file mode 100644 index 0000000..5ad2c4b --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_45.html @@ -0,0 +1,120 @@ + + + + + + +CentOS Artwork Repository - File System: 3.42 trunk/Locales/Identity/Themes/Backgrounds + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.42 trunk/Locales/Identity/Themes/Backgrounds

+ + + +

3.42.1 Goals

+ +
    +
  • ... +
+ + + +

3.42.2 Description

+ +
    +
  • ... +
+ + + +

3.42.3 Usage

+ +
    +
  • ... +
+ + + +

3.42.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_46.html b/Manuals/Repository/filesystem-html/filesystem_46.html new file mode 100644 index 0000000..bbf0368 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_46.html @@ -0,0 +1,188 @@ + + + + + + +CentOS Artwork Repository - File System: 3.43 trunk/Locales/Identity/Themes/Distro/Anaconda/Progress + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.43 trunk/Locales/Identity/Themes/Distro/Anaconda/Progress

+ + + +

3.43.1 Goals

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

3.43.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.43.3 Usage

+ +

Translation rendering is described in `trunk/Translations' +documentation entry (-- Removed(pxref:trunk Translations) --). +

+ + + +

3.43.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_47.html b/Manuals/Repository/filesystem-html/filesystem_47.html new file mode 100644 index 0000000..b309d57 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_47.html @@ -0,0 +1,120 @@ + + + + + + +CentOS Artwork Repository - File System: 3.44 trunk/Locales/Identity/Widgets + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.44 trunk/Locales/Identity/Widgets

+ + + +

3.44.1 Goals

+ +
    +
  • ... +
+ + + +

3.44.2 Description

+ +
    +
  • ... +
+ + + +

3.44.3 Usage

+ +
    +
  • ... +
+ + + +

3.44.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_48.html b/Manuals/Repository/filesystem-html/filesystem_48.html new file mode 100644 index 0000000..14a65d2 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_48.html @@ -0,0 +1,120 @@ + + + + + + +CentOS Artwork Repository - File System: 3.45 trunk/Manuals + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.45 trunk/Manuals

+ + + +

3.45.1 Goals

+ +
    +
  • ... +
+ + + +

3.45.2 Description

+ +
    +
  • ... +
+ + + +

3.45.3 Usage

+ +
    +
  • ... +
+ + + +

3.45.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_49.html b/Manuals/Repository/filesystem-html/filesystem_49.html new file mode 100644 index 0000000..16c9320 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_49.html @@ -0,0 +1,123 @@ + + + + + + +CentOS Artwork Repository - File System: 3.46 trunk/Scripts + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.46 trunk/Scripts

+ + + +

3.46.1 Goals

+ +

The `trunk/Scripts' directory exists to: +

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

3.46.2 Description

+ +
    +
  • ... +
+ + + +

3.46.3 Usage

+ +
    +
  • ... +
+ + + +

3.46.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_5.html b/Manuals/Repository/filesystem-html/filesystem_5.html new file mode 100644 index 0000000..829b8ee --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_5.html @@ -0,0 +1,112 @@ + + + + + + +CentOS Artwork Repository - File System: 3.2 trunk/Identity/Brands + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.2 trunk/Identity/Brands

+ + + +

3.2.1 Goals

+ +
    +
  • ... +
+ + + +

3.2.2 Description

+ + + +

3.2.3 Usage

+ + + +

3.2.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_50.html b/Manuals/Repository/filesystem-html/filesystem_50.html new file mode 100644 index 0000000..09be060 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_50.html @@ -0,0 +1,251 @@ + + + + + + +CentOS Artwork Repository - File System: 3.47 trunk/Scripts/Bash + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.47 trunk/Scripts/Bash

+ + + +

3.47.1 Goals

+ +

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

+ + +

3.47.2 Description

+ +

The best way to understand `centos-art.sh' automation script is +studying its source code. However, as start point, you may prefer to +read an introductory resume before diving into the source code +details. +

+

The `centos-art.sh' script is written in Bash. Most tasks, inside +`centos-art.sh' script, have been organized in many specific +functionalities that you can invoke from the centos-art +command-line interface. +

+

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 location. If your system was prepared to use CentOS +Artwork Repository correctly (-- Removed(pxref:trunk Scripts Bash Functions +Verify) --), you should have a symbolic link inside `~/bin/' +directory that points to the `centos-art.sh' script file. As +`~/bin/' directory is, by default, inside PATH environment +variable, the execution of centos-art command runs the +`centos-art.sh' script. +

+

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

+

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

+

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

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

In the above example, `centos-art' is the command you use to +invoke `centos-art.sh' script. The `arg1' is required and +represents the functionality you want to perform (e.g., +`verify', `render', `locale', `manual', +etc.). The remaining arguments are modifiers to `arg1'. The +`--arg2' definition is required and represets, specifically, +the action inside the functionality you want to perform. The +`--arg3' and on, are optional. +

+

Once command-line arguments have been retrived, the +`centos-art.sh' script loads specific functionalities using the +`cli_getFunctions.sh' function script. Only one specific +functionality can be loaded at one script execution I.e., you run +centos-art.sh script to run just one functionality. +

+
+
+----------------------------------------------------------------------+
+| [centos@host]$ centos-art function --action='value' --option='value' |
++----------------------------------------------------------------------+
+| ~/bin/centos-art --> ~/artwork/trunk/Scripts/Bash/centos-art.sh      |
++---v-----------------------------------------v------------------------+
+    | centos-art.sh                           |
+    +---v---------------------------------v---+
+    .   | initEnvironment.sh              |   .
+    .   +---------------------------------+   .
+    .   | cli $@                          |   .
+    .   +---v-------------------------v---+   .
+    .   .   | cli_getFunctions        |   .   .
+    .   .   +---v-----------------v---+   .   .
+    .   .   .   | function1       |   .   .   .
+    .   .   .   | function2       |   .   .   .
+    .   .   .   | function3       |   .   .   .
+    .   .   .   +-----------------+   .   .   .
+    .   .   ...........................   .   .
+    .   ...................................   .
+    ...........................................
+
+

Figure 3.1: The functionalities initialization environment. + +

+

Functionalities are implemented by means of actions. Once the +functionality has been initiazalized, actions initialization take +place for that functionality. Actions initialization model is very +similar to functions initialization model. But with the difference, +that actions are loaded inside function environment, and so, share +variables and functions defined inside function environment. +

+
+
+--------------------------------------+
+| cli_getFunctions                     |
++---v------------------------------v---+
+.   | function1                    |   .
+.   +---v----------------------v---+   .
+.   .   | function1_getActions |   .   .
+.   .   +---v--------------v---+   .   .
+.   .   .   | action 1     |   .   .   .
+.   .   .   | action 2     |   .   .   .
+.   .   .   | action n     |   .   .   .
+.   .   .   +--------------+   .   .   .
+.   .   ........................   .   .
+.   ................................   .
+.   +------------------------------+   .
+.   | function2                    |   .
+.   +---v----------------------v---+   .
+.   .   | function2_getActions |   .   .
+.   .   +---v--------------v---+   .   .
+.   .   .   | action 1     |   .   .   .
+.   .   .   | action 2     |   .   .   .
+.   .   .   | action n     |   .   .   .
+.   .   .   +--------------+   .   .   .
+.   .   ........................   .   .
+.   ................................   .
+.   +------------------------------+   .
+.   | function3                    |   .
+.   +---v----------------------v---+   .
+.   .   | function3_getActions |   .   .
+.   .   +---v--------------v---+   .   .
+.   .   .   | action 1     |   .   .   .
+.   .   .   | action 2     |   .   .   .
+.   .   .   | action n     |   .   .   .
+.   .   .   +--------------+   .   .   .
+.   .   ........................   .   .
+.   ................................   .
+........................................
+
+

Figure 3.2: The actions initialization environment. + +

+ + +

3.47.3 Usage

+ +

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

+ + +

3.47.4 See also

+ + + +
3.46 trunk/Scripts   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_51.html b/Manuals/Repository/filesystem-html/filesystem_51.html new file mode 100644 index 0000000..372472e --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_51.html @@ -0,0 +1,92 @@ + + + + + + +CentOS Artwork Repository - File System: 3.48 trunk/Scripts/Bash/Cli + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.48 trunk/Scripts/Bash/Cli

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_52.html b/Manuals/Repository/filesystem-html/filesystem_52.html new file mode 100644 index 0000000..c39421c --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_52.html @@ -0,0 +1,1354 @@ + + + + + + +CentOS Artwork Repository - File System: 3.49 trunk/Scripts/Bash/Cli/Functions + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.49 trunk/Scripts/Bash/Cli/Functions

+ + + +

3.49.1 Goals

+ +

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

+ + +

3.49.2 Description

+ +

The specific functions of `centos-art.sh' script are designed +with "Software Toolbox" philosophy (see (coreutils.info)Toolbox introduction) in mind: each program "should do one +thing well". Inside `centos-art.sh' script, each specific +functionality is considered a program that should do one thing well. +Of course, if you find that they still don't do it, feel free to +improve them in order for them to do so. +

+

The specific functions of `centos-art.sh' script are organized +inside specific directories under `trunk/Scripts/Bash/Functions' +location. Each specific function directory should be named as the +function it represents, with the first letter in uppercase. For +example, if the function name is render, the specific function +directory for it would be `trunk/Scripts/Bash/Functions/Render'. +

+

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

+

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

+
Info

Tip

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

+ +

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

+

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

+

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

+

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

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

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

+

Inside `centos-art.sh' script, as convenction, each function +script has one top commentary, followed by one blank line, and then +one function defintion below it only. +

+

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

+

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

+
#!/bin/bash
+#
+# greet.sh -- This function outputs different kind of greetings to
+# your screen. Use this function to understand how centos-art.sh
+# script specific functionalities work.
+#
+# Copyright (C) YEAR YOURFULLNAME
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+# 
+# This program is distributed in the hope that it will be useful, but
+# WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+# General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
+# USA.
+# 
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+

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

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

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

+

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

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

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

+

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

+

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

+

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

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

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

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

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

+

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

+

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

+

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

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

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

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

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

+

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

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

To have a well documented function helps user to understand how your +function really works, and how it should be used. When no valid +action is passed to a function, the `centos-art.sh' script uses +the function documentation entry as vehicle to communicate which the +valid functions are. When no documentation entry exists for a +function, the `centos-art.sh' script informs that no +documentation entry exists for such function and requests user to +create it right at that time. +

+

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

+
centos-art locale --edit
+
+
Warning

Warning

To translate output messages in different languages, +your system locale information --as in LANG environment +variable-- must be set to that locale you want to produce translated +messages for. For example, if you want to produce translated messages +for Spanish language, your system locale information must be set to +`es_ES.UTF-8', or similar, first. +

+ +

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

+

In greet function example we've described so far, we only use +cli_printMessage global function in action specific function +definitions in order to print messages, but more interesting things +can be achieved inside action specific function definitions. For +example, if you pass a directory path as action value in second +argument, you could retrive a list of files from therein, and process +them. If the list of files turns too long or you just want to control +which files to process, you could add the third argument in the form +`--filter='regex'' and reduce the amount of files to process +using a regular expression pattern. +

+

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

+

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

+ + +

3.49.3 Usage

+ + + +

3.49.3.1 Global variables

+ +

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

+
+
Variable: TEXTDOMAIN + +
+

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

+ +
+
Variable: TEXTDOMAINDIR + +
+

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

+ +
+
Variable: FUNCNAM + +
+

Define function name. +

+

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

+

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

+

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

+ +
+
Variable: FUNCDIR + +
+
+ +
+
Variable: FUNCDIRNAME + +
+
+ +
+
Variable: FUNCSCRIPT + +
+
+ +
+
Variable: FUNCCONFIG + +
+
+ +
+
Variable: ACTIONNAM + +
+

Define action name. +

+

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

+

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

+

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

+ +
+
Variable: ACTIONVAL + +
+

Define action value. +

+

Action values are associated to just one action name. Action values +contain the working copy entry over which its associated action will be +performed in. Working copy entries can be files or directories inside +the working copy. +

+ +
+
Variable: REGEX + +
+

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

+

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

+

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

+ +
+
Variable: ARGUMENTS + +
+

Define optional arguments. +

+

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

+

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

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

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

+

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

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

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

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

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

+

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

+

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

+

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

+ +
+
Variable: EDITOR + +
+

Default text editor. +

+

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

+

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

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

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

+ + + +

3.49.3.2 Global functions

+ +

Function scripts stored directly under +`trunk/Scripts/Bash/Functions/' directory are used to define +global functions. Global functions can be used inside action specific +functionalities and or even be reused inside themselves. This section +provides introductory information to global functions you can use +inside `centos-art.sh' script. +

+
+
Function: cli_checkActionArguments + +
+

Validate action value (ACTIONVAL) variable. +

+

The action value variable can take one of the following values: +

+
    +
  1. Path to one directory inside the local working copy, +
  2. Path to one file inside the local working copy, +
+ +

If another value different from that specified above is passed to +action value variable, the `centos-art.sh' script prints an error +message and ends script execution. +

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

Verify file existence. +

+

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

+
+
`d'
+
`directory'
+

Ends script execution if FILE is not a directory. +

+

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

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

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

+
`h'
+
`symbolic-link'
+

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

+
`x'
+
`execution'
+

Ends script execution if FILE is not executable. +

+
`fh'
+

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

+
`fd'
+

Ends script execution if FILE is neither a regular file nor a +directory. +

+
`isInWorkingCopy'
+

Ends script execution if FILE is not inside the working copy. +

+
+ +

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

+ +
+
Function: cli_commitRepoChanges [LOCATION] + +
+

Syncronize changes between repository and working copy. +

+

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

+

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

+

If LOCATION argument is not specified, the value of +ACTIONVAL variable is used as reference instead. +

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

Figure 3.3: The cli_commitRepoChanges function output. + +

+

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

+ +
+
Function: cli_doParseArguments + +
+

Redefine arguments (ARGUMENTS) global variable using +getopt command output. For more information about how to use +cli_doParseArguments function, see ARGUMENTS variable +description above. +

+ +
+
Function: cli_doParseArgumentsReDef $@ + +
+

Initialize/reset arguments (ARGUMENTS) global variable using +positional parameters variable ($@) as reference. +

+

When we work inside function definitions, positional parameters are +reset to the last function definition positional parameters. If you +need to redefine positional parameters from one specific function, you +need to call cli_doParseArgumentsReDef with the positional +parameters variable ($@), set as first argument, to that +specific function you want to redefine positional parameters at. +

+ +
+
Function: cli_getArguments + +
+

Initialize function name (FUNCNAM), action name +(ACTIONNAM), and action value (ACTIONVAL) global +variables, using positional parameters passed in $@ variable. +

+

The cli_getArguments function is called from cli.sh +function script, using cli function positional parameters +(i.e., the positional parameters passed as arguments in the +command-line) as first function argument. +

+

Once command-line positional parameters are accesible to +`centos-art.sh' script execution evironment, +cli_getArguments uses regular expression to retrive +action variables from first and second argument. The first argument +defines the value used as function name (FUNCNAM), and the +second argument defines both values used as action name +(ACTIONNAM) and action value (ACTIONVAL), respectively. +

+

The first argument is a word in lower case. This word specifies the +name of the functionality you want to use (e.g., `render' to +render images, `manual' to work on documentation, and so on.) +

+

The second argument has a long option style (e.g., +`--option=value'). The `--option' represents the action name +(ACTIONNAM), and the characters inbetween the equal sign +(`=') and the first space character, are considered as the action +value (ACTIONVAL). In order to provide action values with space +characters inbetween you need to enclose action value with quotes like +in `--option='This is long value with spaces inbetween''. +Generally, action values are used to specify paths over which the +action name acts on. +

+

Once action related variables (i.e., FUNCNAM, ACTIONNAM, +and ACTIONVAL) are defined and validated, +cli_getArguments shifts the positional arguments to remove the +first two arguments passed (i.e., those used to retrive action related +variables) and redefine the arguments (ARGUMENTS) global +variable with the new positional parameters information. +

+ +
+
Function: cli_getFunctions + +
+

Initialize funtionalities supported by `centos-art.sh' script. +

+

Functionalities supported by `centos-art.sh' script are organized +in functionality directories under +`trunk/Scripts/Bash/Functions/' directory. Each functionality +directory stores function scripts to the functionality such directory +was created for. Function scripts contain function definitions. +Function definitions contain several commands focused on achieving one +specific task only (i.e., the one such functionality was created for). +

+

In order for `centos-art.sh' script to recognize a functionality, +such functionality needs to be stored under +`trunk/Scripts/Bash/Functions/' in a directory written +capitalized (i.e., the whole name is written in lowercase except the +first character which is in uppercase). The directory where one +specific functionality is stored is known as the `functionality +directory'. +

+

Inside each functionality directory, the functionalty itself is +implemented through function scripts. Function scripts are organized +in files independently one another and written in `camelCase' +format with the function name as prefix. Separation between prefix +and description is done using underscore (`_') character. +

+

In order for `centos-art.sh' script to load functionalities +correctly, function definition inside function scripts should be set +using the `function' reserved word, just as in the following +example: +

+
function prefix_doSomething {
+
+    # Do something here...
+
+}
+
+

The above function definition is just a convenction we use, in order +to make identification of function names easier read and automate by +`centos-art.sh' script initialization commands, once +`centos-art.sh' script determines which functionality directory +to use. Specifically, in order to initialize and export functions, +`centos-art.sh' script executes all function scripts inside the +functionality directory, and later grep on them using a +regular expression pattern, where the `function' reserved word is +used as reference to retrive the function names and export them to +`centos-art.sh' script execution environment, and so, make +function definitions --from function scripts inside the functionality +directory-- available for further calls. +

+

If the functionality specified in the command-line first argument +doesn't have a functionality directory, `centos-art.sh' script +considers the functionality provided in the command-line as invalid +functionality and immediatly stops script execution with an error +message. +

+

In order to keep visual consistency among function scripts, please +consider using the following function script design model as template +for your own function scripts: +

+
#!/bin/bash
+#
+# prefix_doSomething.sh -- This function illustrates function scripts
+# design model you can use to create your own function scripts inside
+# centos-art.sh script.
+#
+# Copyright (C) YEAR YOURFULLNAME
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+# 
+# This program is distributed in the hope that it will be useful, but
+# WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+# General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
+# USA.
+# 
+# ----------------------------------------------------------------------
+# $Id$
+# ----------------------------------------------------------------------
+
+function prefix_doSomething {
+
+    # Do something here...
+
+}
+
+ +
+
Function: cli_getCountryCodes [FILTER] + +
+

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

+

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

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

Outputs country name supported by `centos-art.sh' script. +

+

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

+ +
+
Function: cli_getCurrentLocale + +
+

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

+

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

+

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

+

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

+

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

+ +
+
Function: cli_getFilesList [LOCATION] + +
+

Output list of files to process. +

+

The cli_getFilesList function uses LOCATION variable as +source location to build a list of files just as specified by regular +expression (REGEX) global variable. Essentially, what the +cli_getFilesList function does is using find command +to look for files in the location (LOCATION) just as posix-egrep +regular expression (REGEX) specifies. +

+

If LOCATION is not specified when cli_getFilesList +function is called, the action value (ACTIONVAL) global variable +is used as location value instead. +

+

By default, if the regular expression (REGEX) global variable is +not redefined after its first definition in the cli function, +all files that match default regular expression value (i.e., +`.+') will be added to the list of files to process. Otherwise, +if you redefine the regular expression global variable after its first +definition in the cli function and before calling +cli_getFilesList function, the last value you specifed is used +instead. +

+

When you need to customize the regular expression (REGEX) global +variable value inside a function, do not redefine the global variable +(at least you be absolutly convinced you need to). Instead, set the +regular expression global variable as `local' to the function you +need a customized regular expression value for. If we don't redefine +the regular expression global variable as local to the function, or +use another name for the regular expression variable (which is not +very convenient in order to keep the amount of names to remember low), +you may experiment undesired concantenation issues that make your +regular expression to be something different from that you expect them +to be, specially if the function where you are doing the variable +redefinition is called several times during the same script execution. +

+

As result, the cli_getFilesList re-defines the value of +FILES variable with the list of files the find command +returned. As example, consider the following construction: +

+
function prefix_doSomething {
+
+    # Initialize the list of files to process.
+    local FILES=''
+
+    # Initialize location.
+    local LOCATION=/home/centos/artwork/trunk/Identity/Themes/Models/Default
+
+    # Re-define regular expression to match scalable vector graphic
+    # files only. Note how we use the global value of REGEX to build a
+    # new local REGEX value here.
+    local REGEX="${REGEX}.*\.(svgz|svg)"
+
+    # Redefine list of files to process.
+    cli_getFilesList $LOCATION
+
+    # Process list of files.
+    for FILE in $FILES;do
+        cli_printMessages "$FILE" 'AsResponseLine'
+        # Do something else here on...
+    done
+
+}
+
+
+ +
+
Function: cli_getLangCodes [FILTER] + +
+

Outputs language codes supported by `centos-art.sh' script. +

+

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

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

Outputs language names supported by `centos-art.sh' script. +

+

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

+ +
+
Function: cli_getLocales + +
+

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

+

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

+ +
+
Function: cli_getRepoName NAME TYPE + +
+

Sanitate file names. +

+

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

+
Important

Important

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

+ +

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

+

The TYPE variable specifies what type of sanitation you want to +perform on NAME. The TYPE can be one of the following +values: +

+
+
`d'
+
`directory'
+

Sanitate directory NAMEs. +

+
`f'
+
`regular-file'
+

Sanitate regular file NAMEs. +

+
+ +

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

+

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

+

When we change file name convenctions inside cli_getRepoName +what we are really changing is the way functions interpret repository +file system organization. Notice that when we change a file name +(e.g., a function name), it is necessary to update all files where +such file name is placed on. This may require a massive substitution +inside the repository, each time we change name convenctions in the +repository (-- Removed(pxref:trunk Scripts Bash Functions Path) --, for more +information). +

+ +
+
Function: cli_getRepoStatus [LOCATION] + +
+

Request repository status. +

+

This function requests the status of a LOCATION inside the +working copy using the svn status command and returns the +first character in the output line, just as described in svn +help status. If LOCATION is not a regular file or a directory, +inside the working copy, the `centos-art.sh' script prints a +message and ends its execution. +

+

Use this function to perform verifications based a repository +LOCATION status. +

+ +
+
Function: cli_getTemporalFile NAME + +
+

Output absolute path to temporal file NAME. +

+

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

+
cli_getTemporalFile $FILE
+
+

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

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

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

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

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

+ +
+
Function: cli_getThemeName + +
+

Output theme name. +

+

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

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

Define standard output message definition supported by +`centos-art.sh' script. +

+

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

+
+
`AsHeadingLine'
+

To print heading messages. +

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

To print warning messages. +

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

To print note messages. +

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

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

Updating        $MESSAGE
+
+
+
`AsRemovingLine'
+

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

Removing        $MESSAGE
+
+
+
`AsCheckingLine'
+

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

Checking        $MESSAGE
+
+
+
`AsCreatingLine'
+

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

Creating        $MESSAGE
+
+
+
`AsSavedAsLine'
+

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

Saved as        $MESSAGE
+
+
+
`AsLinkToLine'
+

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

Linked to       $MESSAGE
+
+
+
`AsMovedToLine'
+

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

Moved to        $MESSAGE
+
+
+
`AsTranslationLine'
+

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

Translation     $MESSAGE
+
+
+
`AsConfigurationLine'
+

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

Configuration   $MESSAGE
+
+
+
`AsResponseLine'
+

To print response messages on one-column format. +

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

To print request messages on one-column format. Request messages +output messages with one colon (`:') and without trailing newline +(`\n') at message end. +

$MESSAGE:
+
+
+
`AsYesOrNoRequestLine'
+

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

+
$MESSAGE [y/N]:
+
+

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

+
$MESSAGE [s/N]:
+
+

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

+

Definition of which confirmation word to use is set on translation +messages for your specific locale information. -- Removed(xref:trunk Scripts +Bash Functions Locale) --, for more information about locale-specific +translation messages. +

+
+
`AsToKnowMoreLine'
+

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

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

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

+
+
`AsRegularLine'
+

To standardize regular messages on one-column format. +

+

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

+
+ +

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

+
Info

Tip

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

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

3.49.3.3 Specific functions

+ +

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

+ + + +

3.49.4 See also

+ + + +
3.47 trunk/Scripts/Bash   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_53.html b/Manuals/Repository/filesystem-html/filesystem_53.html new file mode 100644 index 0000000..b0455ba --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_53.html @@ -0,0 +1,120 @@ + + + + + + +CentOS Artwork Repository - File System: 3.50 trunk/Scripts/Bash/Cli/Functions/Help + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.50 trunk/Scripts/Bash/Cli/Functions/Help

+ + + +

3.50.1 Goals

+ +
    +
  • ... +
+ + + +

3.50.2 Description

+ +
    +
  • ... +
+ + + +

3.50.3 Usage

+ +
    +
  • ... +
+ + + +

3.50.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_54.html b/Manuals/Repository/filesystem-html/filesystem_54.html new file mode 100644 index 0000000..da714b6 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_54.html @@ -0,0 +1,120 @@ + + + + + + +CentOS Artwork Repository - File System: 3.51 trunk/Scripts/Bash/Cli/Functions/Html + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.51 trunk/Scripts/Bash/Cli/Functions/Html

+ + + +

3.51.1 Goals

+ +
    +
  • ... +
+ + + +

3.51.2 Description

+ +
    +
  • ... +
+ + + +

3.51.3 Usage

+ +
    +
  • ... +
+ + + +

3.51.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_55.html b/Manuals/Repository/filesystem-html/filesystem_55.html new file mode 100644 index 0000000..dd32a24 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_55.html @@ -0,0 +1,185 @@ + + + + + + +CentOS Artwork Repository - File System: 3.52 trunk/Scripts/Bash/Cli/Functions/Locale + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.52 trunk/Scripts/Bash/Cli/Functions/Locale

+ + + +

3.52.1 Goals

+ +
    +
  • ... +
+ + + +

3.52.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 finishd PO file edition and quit text editor, the +centos-art command creates the related machine object in the +location `$CLI_LANG/LC_MESSAGES/$TEXTDOMAIN.mo'. +

+

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

+

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

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

3.52.3 Usage

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

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

+
`centos-art locale --list'
+

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

+
+ + + +

3.52.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_56.html b/Manuals/Repository/filesystem-html/filesystem_56.html new file mode 100644 index 0000000..fa1b0ba --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_56.html @@ -0,0 +1,120 @@ + + + + + + +CentOS Artwork Repository - File System: 3.53 trunk/Scripts/Bash/Cli/Functions/Manual + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.53 trunk/Scripts/Bash/Cli/Functions/Manual

+ + + +

3.53.1 Goals

+ +
    +
  • ... +
+ + + +

3.53.2 Description

+ +
    +
  • ... +
+ + + +

3.53.3 Usage

+ +
    +
  • ... +
+ + + +

3.53.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_57.html b/Manuals/Repository/filesystem-html/filesystem_57.html new file mode 100644 index 0000000..cb1f243 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_57.html @@ -0,0 +1,437 @@ + + + + + + +CentOS Artwork Repository - File System: 3.54 trunk/Scripts/Bash/Cli/Functions/Path + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.54 trunk/Scripts/Bash/Cli/Functions/Path

+ + + +

3.54.1 Goals

+ +

This section exists to organize files related to path +functiontionality. The path functionality standardizes +movement, syncronization, branching, tagging, and general file +maintainance inside the repository. +

+ + +

3.54.2 Description

+ +

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

+ + +

3.54.2.1 Repository layout

+ +

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

+

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

+

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

+

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

+

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

+

The CentOS Artwork Repository layout is firmly grounded on a +Subversion base. Subversion (http://subversion.tigris.org) is a +version control system, which allows you to keep old versions of files +and directories (usually source code), keep a log of who, when, and +why changes occurred, etc., like CVS, RCS or SCCS. Subversion keeps a +single copy of the master sources. This copy is called the source +"repository"; it contains all the information to permit extracting +previous versions of those files at any time. +

+ + +

3.54.2.2 Repository name convenctions

+ +

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

+

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

+

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

+ + +

3.54.2.3 Repository work flow

+ +

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

+

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

+

Initially, we start working themes on their trunk development line +(e.g., `trunk/Identity/Themes/Motifs/TreeFlower/'), here we +organize information that cannot be produced automatically (i.e., +background images, concepts, color information, screenshots, etc.). +

+

Later, when theme trunk development line is considered "ready" for +implementation (e.g., all required backgrounds have been designed), +we create a branch for it (e.g., +`branches/Identity/Themes/Motifs/TreeFlower/1/'). Once the +branch has been created, we forget that branch and continue working +the trunk development line while others (e.g., an artwork quality +assurance team) test the new branch for tunning it up. +

+

Once the branch has been tunned up, and considered "ready" for +release, it is freezed under `tags/' directory (e.g., +`tags/Identity/Themes/Motifs/TreeFower/1.0/') for packagers, +webmasters, promoters, and anyone who needs images from that CentOS +theme the tag was created for. +

+

Both branches and tags, inside CentOS Artwork Repository, use +numerical values to identify themselves under the same location. +Branches start at one (i.e., `1') and increment one unit for each +branch created from the same trunk development line. Tags start at +zero (i.e., `0') and increment one unit for each tag created from +the same branch development line. +

+
Convenction

Convenction

Do not freeze trunk development lines using tags +directly. If you think you need to freeze a trunk development line, +create a branch for it and then freeze that branch instead. +

+ +

The trunk development line may introduce problems we cannot see +immediatly. Certainly, the high changable nature of trunk development +line complicates finding and fixing such problems. On the other hand, +the branched development lines provide a more predictable area where +only fixes/corrections to current content are commited up to +repository. +

+

If others find and fix bugs inside the branched development line, we +could merge such changes/experiences back to trunk development line +(not visversa) in order for future branches, created from trunk, to +benefit. +

+

Time intervals used to create branches and tags may vary, just as +different needs may arrive. For example, consider the release schema +of CentOS distribution: one major release every 2 years, security +updates every 6 months, support for 7 years long. Each time a CentOS +distribution is released, specially if it is a major release, there is +a theme need in order to cover CentOS distribution artwork +requirements. At this point, is where CentOS Artwork Repository comes +up to scene. +

+

Before releasing a new major release of CentOS distribution we create +a branch for one of several theme development lines available inside +the CentOS Artwork Repository, perform quality assurance on it, and +later, freeze that branch using tags. Once a the theme branch has been +frozen (under `tags/' directory), CentOS Packagers (the persons +whom build CentOS distribution) can use that frozen branch as source +location to fulfill CentOS distribution artwork needs. The same +applies to CentOS Webmasters (the persons whom build CentOS websites), +and any other visual manifestation required by the project. +

+ + +

3.54.2.4 Parallel directories

+ +

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

+

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

+

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

+

Another example of parallel directory is the documentation structure +created by manual functionality. This time, +`centos-art.sh' script uses parallel directory information with +uncommon directory levels to build the documentation entry required by +Texinfo documentation system, inside the repository. +

+

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

+

When one parent directory changes, all their related parallel +directories need to be changed too. This is required in order for +parallel directories to retain their relation with the parent +directory structure. In the other hand, parallel directories should +never be modified under no reason but to satisfy the relation to their +parent directory structure. Liberal change of parallel directories +may suppresses the conceptual idea they were initially created for; +and certainly, things may stop working the way they should do. +

+ + +

3.54.2.5 Syncronizing path information

+ +

Parallel directories are very useful to keep repository organized but +introduce some complications. For instance, consider what would +happen to functionalities like manual (`trunk Scripts Bash +Functions Manual') that rely on parent directory structures to create +documentation entries (using parallel directory structures) if one of +those parent directory structures suddenly changes after the +documentation entry has been already created for it? +

+

In such cases, functionalities like manual may confuse +themselves if path information is not updated to reflect the relation +with its parent directory. Such functionalities work with parent +directory structure as reference; if a parent directory changes, the +functionalities dont't even note it because they work with the last +parent directory structure available in the repository, no matter what +it is. +

+

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

+

There is no immediate way for manual, and similar +functionalities that use parent directories as reference, to know when +and how directory movements take place inside the repository. Such +information is available only when the file movement itself takes +place inside the repository. So, is there, at the moment of moving +files, when we need to syncronize parallel directories with their +unique parent directory structure. +

+
Warning

Warning

There is not support for URL reference inside +`centos-art.sh' script. The `centos-art.sh' script is +designed to work with local files inside the working copy only. +

+ +

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

+

Finally, once all path information has been corrected, it is time to +take care of information inside the files. For instance, considere +what would happen if you make a reference to a documentation node, and +later the documentation node you refere to is deleted. That would make +Texinfo to produce error messages at export time. So, the +`centos-art.sh' script needs to know when such changes happen, in +a way they could be noted and handled without producing errors. +

+ + +

3.54.2.6 What is the right place to store it?

+ +

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

+

The CentOS Community different free support vains (see: +http://wiki.centos.org/GettingHelp) are the best place to find +answers to your question, but going there with hands empty is not good +idea. It may give the impression you don't really care about. Instead, +consider the following suggestions to find your own comprehension and +so, make your propositions based on it. +

+

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

+

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

+

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

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

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

+ + +

3.54.3 Usage

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

Copy `SRC' to `DST' and schedule `DST' for +addition (with history). In this command, `SRC' and `DST' +are both working copy (WC) entries. +

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

Delete `DST'. In order for this command to work the file or +directory you intend to delete should be under version control first. +In this command, `SRC' is a working copy (WC) entry. +

+
+
+ + + +

3.54.4 See also

+ + + +
3.47 trunk/Scripts/Bash   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_58.html b/Manuals/Repository/filesystem-html/filesystem_58.html new file mode 100644 index 0000000..6380525 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_58.html @@ -0,0 +1,821 @@ + + + + + + +CentOS Artwork Repository - File System: 3.55 trunk/Scripts/Bash/Cli/Functions/Render + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.55 trunk/Scripts/Bash/Cli/Functions/Render

+ +

The render functionality exists to produce both identity and +translation files on different levels of information (i.e., different +languages, release numbers, architectures, etc.). +

+

The render functionality relies on "renderable directory +structures" to produce files. Renderable directory structures can be +either "identity directory structures" or "translation directory +structures" with special directories inside. +

+ + +

3.55.1 Renderable identity directory structures

+ +

Renderable identity directory structures are the starting point of +identity rendition. Whenever we want to render a component of CentOS +corporate visual identity, we need to point `centos-art.sh' to a +renderable identity directory structure. If such renderable identity +directory structure doesn't exist, then it is good time to create it. +

+

Inside the working copy, one renderable identity directory structures +represents one visual manifestation of CentOS corporate visual +identity, or said differently, each visual manifestation of CentOS +corporate visual identity should have one renderable identity +directory structure. +

+

Inside renderable identity directory structures, `centos-art.sh' +can render both image-based and text-based files. Specification of +whether a renderable identity directory structure produces image-based +or text-based content is a configuration action that takes place in +the pre-rendition configuration script of that renderable identity +directory structure. +

+

Inside renderable identity directory structures, content production is +organized in different configurations. A content production +configuration is a unique combination of the components that make an +identity directory structure renderable. One content production +configuration does one thing only (e.g., to produce untranslated +images), but it can be extended (e.g., adding translation files) to +achieve different needs (e.g., to produce translated images). +

+ + +

3.55.1.1 Design template without translation

+ +

The design template without translation configuration is based on a +renderable identity directory structure with an empty translation +directory structure. In this configuration, one design template +produces one untranslated file. Both design templates and final +untranslated files share the same file name, but they differ one +another in file-type and file-extension. +

+

For example, to produce images without translations (there is no much +use in producing text-based files without translations), consider the +following configuration: +

+
+
One renderable identity directory structure:
+
+

In this example we used `Identity/Path/To/Dir' as the identity +component we want to produce untranslated images for. Identity +components can be either under `trunk/' or `branches/' +directory structure. +

+

The identity component (i.e., `Identity/Path/To/Dir', in this +case) is also the bond component we use to connect the identity +directory structures with their respective auxiliar directories (i.e., +translation directory structres and pre-rendition configuration +structures). The bond component is the path convenction that +`centos-art.sh' uses to know where to look for related +translations, configuration scripts and whatever auxiliar thing a +renderable directory structure may need to have. +

+
      | The bond component
+      |----------------->|
+trunk/Identity/Path/To/Dir  <-- Renderable identity directory structure.
+|-- Tpl                     <-- Design template directory.
+|   `-- file.svg            <-- Design template file.
+`-- Img                     <-- Directory used to store final files.
+    `-- file.png            <-- Final image-based file produced from
+                                design template file.
+
+

Inside design template directory, design template files are based on +SVG (Scalable Vector Graphics) and use the extension +.svg. Design template files can be organized using several +directory levels to create a simple but extensible configuration, +specially if translated images are not required. +

+

In order for SVG (Scalable Vector Graphics) files to be +considered "design template" files, they should be placed under the +design template directory and to have set a CENTOSARTWORK +object id inside. +

+

The CENTOSARTWORK word itself is a convenction name we use to +define which object/design area, inside a design template, the +`centos-art.sh' script will use to export as +PNG (Portable Network Graphic) image at rendition time. +Whithout such object id specification, the `centos-art.sh' script +cannot know what object/design area you (as designer) want to export +as PNG (Portable Network Graphic) image file. +

+
info

Note

At rendition time, the content of `Img/' directory +structure is produced by `centos-art.sh' automatically. +

+ +

When a renderable identity directory structure is configured to +produce image-based content, `centos-art.sh' produces +PNG (Portable Network Graphics) files with the .png +extension. Once the base image format has been produced, it is +possible for `centos-art.sh' to use it in order to automatically +create other image formats that may be needed (-- Removed(pxref:trunk Scripts +Bash Functions Render Config) --). +

+

Inside the working copy, you can find an example of "design template +without translation" configuration at `trunk/Identity/Models/'. +

+

See section trunk/Identity, for more information. +

+
+
One translation directory structure:
+
+

In order for an identity entry to be considered an identity renderable +directory structure, it should have a translation entry. The content +of the translation entry is relevant to determine how to process the +identity renderable directory entry. +

+

If the translation entry is empty (i.e., there is no file inside it), +`centos-art.sh' interprets the identity renderable directory +structure as a "design templates without translation" configuration. +

+
                   | The bond component
+                   |----------------->|
+trunk/Translations/Identity/Path/To/Dir
+`-- (empty)
+
+

If the translation entry is not empty, `centos-art.sh' can +interpret the identity renderable directory structure as one of the +following configurations: "design template with translation +(one-to-one)" or "design template with translation (optimized)". +Which one of these configurations is used depends on the value +assigned to the matching list (MATCHINGLIST) variable in the +pre-rendition configuration script of the renderable identity +directory structure we are producing images for. +

+

If the matching list variable is empty (as it is by default), then +"design template with translation (one-to-one)" configuration is +used. In this configuration it is required that both design templates +and translation files have the same file names. This way, one +translation files is applied to one design template, to produce +one translated image. +

+

If the matching list variable is not empty (because you redefine it in +the pre-rendition configuration script), then "design template with +translation (optimized)" configuration is used instead. In this +configuration, design templates and translation files don't need to +have the same names since such name relationship between them is +specified in the matching list properly. +

+

-- Removed(xref:trunk Translations) --, for more information. +

+
+
One pre-rendition configuration script:
+
+

In order to make an identity directory structure renderable, a +pre-rendition configuration script should exist for it. The +pre-rendition configuration script specifies what type of rendition +does `centos-art.sh' will perform over the identity directory +structure and how does it do that. +

+
                                           | The bond component
+                                           |----------------->|
+trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir
+`-- render.conf.sh
+
+

In this configuration the pre-rendition configuration script +(`render.conf.sh') would look like the following: +

+
function render_loadConfig {
+
+    # Define rendition actions.
+    ACTIONS[0]='BASE:renderImage'
+
+}
+
+

Since translation directory structure is empty, `centos-art.sh' +assumes a "design template without translation" configuration to +produce untranslated images. +

+

To produce untranslated images, `centos-art.sh' takes one design +template and creates one temporal instance from it. Later, +`centos-art.sh' uses the temporal design template instance as +source file to export the final untranslated image. The action of +exporting images from SVG (Scalable Vector Graphics) to +PNG (Portable Network Graphics) is possible thanks to +Inkscape's command-line interface and the CENTOSARTWORK object +id we previously set inside design templates. +

+
centos-art.sh render --identity=trunk/Identity/Path/To/Dir
+-------------------------------------------------
+0 | Execute centos-art.sh on renderable identity directory structure.
+--v----------------------------------------------
+trunk/Identity/Path/To/Dir/Tpl/file.svg
+-------------------------------------------------
+1 | Create instance from design template.
+--v----------------------------------------------
+/tmp/centos-art.sh-a07e824a-5953-4c21-90ae-f5e8e9781f5f-file.svg
+-------------------------------------------------
+2 | Render untranslated image from design template instance.
+--v----------------------------------------------
+trunk/Identity/NewDir/Img/file.png
+-------------------------------------------------
+3 | Remove design template instance.
+
+

Finally, when the untranslated image has been created, the temporal +design template instance is removed. At this point, +`centos-art.sh' takes the next design template and repeats the +whole production flow once again (design template by design template), +until all design templates be processed. +

+

-- Removed(xref:trunk Scripts Bash Functions Render Config) --, for more +information. +

+
+ + + +

3.55.1.2 Design template with translation (one-to-one)

+ +

Producing untranslated images is fine in many cases, but not always. +Sometimes it is required to produce images in different languages and +that is something that untrasnlated image production cannot achieve. +However, if we fill its empty translation entry with translation files +(one for each design template) we extend the production flow from +untranslated image production to translated image production. +

+

In order for `centos-art.sh' to produce images correctly, each +design template should have one translation file and each translation +file should have one design template. Otherwise, if there is a +missing design template or a missing translation file, +`centos-art.sh' will not produce the final image related to the +missing component. +

+

In order for `centos-art.sh' to know which is the relation +between translation files and design templates the translation +directory structure is taken as reference. For example, the +`trunk/Translations/Identity/Path/To/Dir/file.sed' translation +file does match `trunk/Identity/Path/To/Dir/Tpl/file.svg' design +template, but it doesn't match +`trunk/Identity/Path/To/Dir/File.svg' or +`trunk/Identity/Path/To/Dir/Tpl/File.svg' or +`trunk/Identity/Path/To/Dir/Tpl/SubDir/file.svg' design +templates. +

+

The pre-rendition configuration script used to produce untranslated +images is the same we use to produce translated images. There is no +need to modify it. So, as we are using the same pre-rendition +configuration script, we can say that translated image production is +somehow an extended/improved version of untranslated image production. +

+
info

Note

If we use no translation file in the translation entry +(i.e., an empty directory), `centos-art.sh' assumes the +untranslated image production. If we fill the translation entry with +translation files, `centos-art.sh' assumes the translated image +production. +

+ +

To produce final images, `centos-art.sh' applies one translation +file to one design template and produce a translated design template +instance. Later, `centos-art.sh' uses the translated template +instance to produce the translated image. Finally, when the translated +image has been produced, `centos-art.sh' removes the translated +design template instance. This production flow is repeated for each +translation file available in the translatio entry. +

+
centos-art.sh render --identity=trunk/Identity/Path/To/Dir
+-------------------------------------------------
+0 | Execute centos-art.sh on directory structure.
+--v----------------------------------------------
+trunk/Translations/Identity/Path/To/Dir/file.sed
+-------------------------------------------------
+1 | Apply translation to design template.
+--v----------------------------------------------
+trunk/Identity/Path/To/Dir/Tpl/file.svg
+-------------------------------------------------
+2 | Create design template instance.
+--v----------------------------------------------
+/tmp/centos-art.sh-a07e824a-5953-4c21-90ae-f5e8e9781f5f-file.svg
+-------------------------------------------------
+3 | Render PNG image from template instance.
+--v----------------------------------------------
+trunk/Identity/NewDir/Img/file.png
+-------------------------------------------------
+4 | Remove design template instance.
+
+ + +

3.55.1.3 Design template with translation (optimized)

+ +

Producing translated images satisfies almost all our production images +needs, but there is still a pitfall in them. In order to produce +translated images as in the "one-to-one" configuration describes +previously, it is required that one translation file has one design +template. That's useful in many cases, but what would happen if we +need to apply many different translation files to the same design +template? Should we have to duplicate the same design template file +for each translation file, in order to satisfy the "one-to-one" +relation? What if we need to assign translation files to design +templates arbitrarily? +

+

Certenly, that's something the "one-to-one" configuration cannot +handle. So, that's why we had to "optimize" it. The optimized +configuration consists on using a matching list (MATCHINGLIST) +variable that specifies the relationship between translation files and +design templates in an arbitrary way. Using such matching list between +translation files and design templates let us use as many assignment +combinations as translation files and design templates we are working +with. +

+

The MATCHINGLIST variable is set in the pre-rendition +configuration script of the component we want to produce images for. +By default, the MATCHINGLIST variable is empty which means no +matching list is used. Otherwise, if MATCHINGLIST variable has a +value different to empty value then, `centos-art.sh' interprets +the matching list in order to know how translation files are applied +to design templates. +

+

For example, consider the following configuration: +

+
+
One entry under `trunk/Identity/':
+
+

In this configuration we want to produce three images using a +paragraph-based style, controlled by `paragraph.svg' design +template; and one image using a list-based style, controlled by +`list.svg' design template. +

+
trunk/Identity/Path/To/Dir
+|-- Tpl
+|   |-- paragraph.svg
+|   `-- list.svg
+`-- Img
+    |-- 01-welcome.png
+    |-- 02-donate.png
+    |-- 03-docs.png
+    `-- 04-support.png
+
+
+
One entry under `trunk/Translations/':
+
+

In order to produce translated images we need to have one translation +file for each translated image we want to produce. Notice how +translation names do match final image file names, but how translation +names do not match design template names. When we use matching list +there is no need for translation files to match the names of design +templates, such name relation is set inside the matching list itself. +

+
trunk/Translations/Identity/Path/To/Dir
+|-- 01-welcome.sed
+|-- 02-donate.sed
+|-- 03-docs.sed
+`-- 04-support.sed
+
+
+
One entry under `trunk/trunk/Scripts/Bash/Functions/Render/Config/':
+
+

In order to produce different translated images using specific design +templates, we need to specify the relation between translation files +and design templates in a way that `centos-art.sh' could know +exactly what translation file to apply to what design template. This +relation between translation files and design templates is set using +the matching list MATCHINGLIST variable inside the pre-rendition +configuration script of the component we want to produce images for. +

+
trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir
+`-- render.conf.sh
+
+

In this configuration the pre-rendition configuration script +(`render.conf.sh') would look like the following: +

+
function render_loadConfig {
+
+    # Define rendition actions.
+    ACTIONS[0]='BASE:renderImage'
+
+    # Define matching list.
+    MATCHINGLIST="\
+    paragraph.svg:\
+        01-welcome.sed\
+        02-donate.sed\
+        04-support.sed
+    list.svg:\
+        03-docs.sed
+    "
+
+}
+
+

As result, `centos-art.sh' will produce `01-welcome.png', +`02-donate.png' and `04-support.png' using the +paragraph-based design template, but `03-docs.png' using the +list-based design template. +

+
+ + + +

3.55.1.4 Design template with translation (optimized+flexibility)

+ +

In the production models we've seen so far, there are design templates +to produce untranslated images and translation files which combiend +with design templates produce translated images. That may seems like +all our needs are covered, doesn't it? Well, it almost does. +

+

Generally, we use design templates to define how final images will +look like. Generally, each renderable directory structure has one +`Tpl/' directory where we organize design templates for that +identity component. So, we can say that there is only one unique +design template definition for each identity component; or what is the +same, said differently, identity components can be produced in one way +only, the way its own design template directory specifies. This is +not enough for theme production. It is a limitation, indeed. +

+

Initially, to create one theme, we created one renderable directory +structure for each theme component. When we found ourselves with many +themes, and components inside them, it was obvious that the same +design model was duplicated inside each theme. As design models were +independently one another, if we changed one theme's design model, +that change was useless to other themes. So, in order to reuse design +model changes, we unified design models into one common directory +structure. +

+

With design models unified in a common structure, another problem rose +up. As design models also had the visual style of theme components, +there was no difference between themes, so there was no apparent need +to have an independent theme directory structure for each different +theme. So, it was also needed to separate visual styles from design +models. +

+

At this point there are two independent worklines: one directory +structure to store design models (the final image characteristics +[i.e., dimensions, translation markers, etc.]) and one directory +structure to store visual styles (the final image visual style [i.e., +the image look and feel]). So, it is possible to handle both +different design models and different visual styles independtly one +another and later create combinations among them using +`centos-art.sh'. +

+

For example, consider the following configuration: +

+
+
One entry under `trunk/Identity/Themes/Models/':
+
+

The design model entry exists to organize design model files (similar +to design templates). Both design models and design templates are very +similar; they both should have the CENTOSARTWORK export id +present to identify the exportation area, translation marks, etc. +However, design models do use dynamic backgrounds inclusion while +design templates don't. +

+
                        THEMEMODEL | | The bond component
+                             |<----| |--------------------->|
+trunk/Identity/Themes/Models/Default/Distro/Anaconda/Progress/
+|-- paragraph.svg
+`-- list.svg
+
+

Inisde design models, dynamic backgrounds are required in order for +different artistic motifs to reuse common design models. Firstly, in +order to create dynamic backgrounds inside design models, we import a +bitmap to cover design model's background and later, update design +model's path information to replace fixed values to dynamic values. +

+
+
One entry under `trunk/Identity/Themes/Motifs/':
+
+

The artistic motif entry defines the visual style we want to produce +images for, only. Final images (i.e., those built from combining both +design models and artistic motif backrounds) are not stored here, but +under branches directory structure. In the artistic motif entry, we +only define those images that cannot be produced automatically by +`centos-art.sh' (e.g., Backgrounds, Color information, +Screenshots, etc.). +

+
                  Artistic motif name | | Artistic motif backgrounds
+                             |<-------| |-------->|
+trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/
+|-- Img
+|   |-- Png
+|   |   |-- 510x300.png
+|   |   `-- 510x300-final.png
+|   `-- Jpg
+|       |-- 510x300.jpg
+|       `-- 510x300-final.jpg
+|-- Tpl
+|   `-- 510x300.svg
+`-- Xcf
+    `-- 510x300.xcf
+
+
+
One entry under `trunk/Translations/':
+
+

The translation entry specifies, by means of translation files, the +language-specific information we want to produce image for. When we +create the translation entry we don't use the name of neither design +model nor artistic motif, just the design model component we want to +produce images for. +

+
                                   | The bond component
+                                   |--------------------->|
+trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/
+`-- 5
+    |-- en
+    |   |-- 01-welcome.sed
+    |   |-- 02-donate.sed
+    |   `-- 03-docs.sed
+    `-- es
+        |-- 01-welcome.sed
+        |-- 02-donate.sed
+        `-- 03-docs.sed
+
+
+
One entry under `trunk/Scripts/Bash/Functions/Render/Config/':
+
+

There is one pre-rendition configuration script for each theme +component. So, each time a theme component is rendered, its +pre-rendition configuration script is evaluated to teach +`centos-art.sh' how to render the component. +

+
trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Distro/Anaconda/Progress/
+`-- render.conf.sh
+
+

In this configuration the pre-rendition configuration script +(`render.conf.sh') would look like the following: +

+
function render_loadConfig {
+
+    # Define rendition actions.
+    ACTIONS[0]='BASE:renderImage'
+
+    # Define matching list.
+    MATCHINGLIST="\
+    paragraph.svg:\
+        01-welcome.sed\
+        02-donate.sed
+    list.svg:\
+        03-docs.sed
+        "
+
+    # Deifne theme model.
+    THEMEMODEL='Default'
+
+}
+
+
+ +

The production flow of "optimize+flexibility" configuration… +

+ +

3.55.2 Renderable translation directory structures

+ +

Translation directory structures are auxiliar structures of renderable +identity directory structures. There is one translation directory +structure for each renderable identity directory structure. Inside +translation directory structures we organize translation files used by +renderable identity directory structures that produce translated +images. Renderable identity directory structures that produce +untranslated images don't use translation files, but they do use a +translation directory structure, an empty translation directory +structure, to be precise. +

+

In order to aliviate production of translation file, we made +translation directory structures renderable adding a template +(`Tpl/') directory structure to handle common content inside +translation files. This way, we work on translation templates and +later use `centos-art.sh' to produce specific translation files +(based on translation templates) for different information (e.g., +languages, release numbers, architectures, etc.). +

+

If for some reason, translation files get far from translation +templates and translation templates become incovenient to produce such +translation files then, care should be taken to avoid replacing the +content of translation files with the content of translation templates +when `centos-art.sh' is executed to produce translation files +from translation templates. +

+

Inside renderable translation directory structures, +`centos-art.sh' can produce text-based files only. +

+ + +

3.55.3 Copying renderable directory structures

+ +

A renderable layout is formed by design models, design images, +pre-rendition configuration scripts and translations files. This way, +when we say to duplicate rendition stuff we are saying to duplicate +these four directory structures (i.e., design models, design images, +pre-rendition configuration scripts, and related translations files). +

+

When we duplicate directories, inside `trunk/Identity' directory +structure, we need to be aware of renderable layout described above +and the source location used to perform the duplication action. The +source location is relevant to centos-art.sh script in order to +determine the required auxiliar information inside directory +structures that need to be copied too (otherwise we may end up with +orphan directory structures unable to be rendered, due the absence of +required information). +

+

In order for a renderable directory structure to be valid, the new +directory structure copied should match the following conditions: +

+
    +
  1. To have a unique directory structure under +`trunk/Identity', organized by any one of the above +organizational designs above. + +
  2. To have a unique directory structure under +`trunk/Translations' to store translation files. + +
  3. To have a unique directory structure under +`trunk/Scripts/Bash/Functions/Render/Config' to set pre-rendition +configuration script. +
+ +

As convenction, the render_doCopy function uses +`trunk/Identity' directory structure as source location. Once +the `trunk/Identity' directory structure has been specified and +verified, the related path information is built from it and copied +automatically to the new location specified by FLAG_TO variable. +

+

Design templates + No translation: +

+

Command: +- centos-art render -copy=trunk/Identity/Path/To/Dir -to=trunk/Identity/NewPath/To/Dir +

+

Sources: +- trunk/Identity/Path/To/Dir +- trunk/Translations/Identity/Path/To/Dir +- trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir +

+

Targets: +- trunk/Identity/NewPath/To/Dir +- trunk/Translations/Identity/NewPath/To/Dir +- trunk/Scripts/Bash/Functions/Render/Config/Identity/NewPath/To/Dir +

+

Renderable layout 2: +

+

Command: +- centos-art render -copy=trunk/Identity/Themes/Motifs/TreeFlower \ + -to=trunk/Identity/Themes/Motifs/NewPath/To/Dir +

+

Sources: +- trunk/Identity/Themes/Motifs/TreeFlower +- trunk/Translations/Identity/Themes +- trunk/Translations/Identity/Themes/Motifs/TreeFlower +- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes +- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/TreeFlower +

+

Targets: +- trunk/Identity/Themes/Motifs/NewPath/To/Dir +- trunk/Translations/Identity/Themes +- trunk/Translations/Identity/Themes/Motifs/NewPath/To/Dir +- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes +- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewPath/To/Dir +

+

Notice that design models are not included in source or target +locations. This is intentional. In "Renderable layout 2", design +models live by their own, they just exist, they are there, available +for any artistic motif to use. By default `Themes/Models/Default' +design model directory structure is used, but other design models +directory structures (under Themes/Models/) can be created and used +changing the value of THEMEMODEL variable inside the pre-rendition +configuration script of the artistic motif source location you want to +produce. +

+

Notice how translations and pre-rendition configuration scripts may +both be equal in source and target. This is because such structures +are common to all artistic motifs (the default values to use when no +specific values are provided). +

+

- The common directory structures are not copied or deleted. We cannot + copy a directory structure to itself. +

+

- The common directory structures represent the default value to use + when no specific translations and/or pre-rendition configuration + script are provided inside source location. +

+

- The specific directory structures, if present, are both copiable and + removable. This is, when you perform a copy or delete action from + source, that source specific auxiliar directories are transfered in + the copy action to a new location (that specified by FLAG_TO + variable). +

+

- When translations and/or pre-rendition configuration scripts are + found inside the source directory structure, the centos-art.sh + script loads common auxiliar directories first and later specific + auxiliar directories. This way, identity rendition of source + locations can be customized idividually over the base of common + default values. +

+

- The specific auxiliar directories are optional. +

+

- The common auxiliar directories should be present always. This is, + in order to provide the information required by render functionality + (i.e., to make it functional in the more basic level of its + existence). +

+

Notice how the duplication process is done from `trunk/Identity' on, +not the oposite. If you try to duplicate a translation structure (or +similar auxiliar directory structures like pre-rendition configuration +scripts), the `trunk/Identity' for that translation is not created. +This limitation is impossed by the fact that many `trunk/Identity' +directory structures may reuse/share the same translation directory +structure. We cannot delete one translation (or similar) directory +structures while a related `trunk/Identity/' directory structure is +still in need of it. +

+

The `render_doCopy' functionality does duplicate directory structures +directly involved in rendition process only. Once such directories +have been duplicated, the functionality stops thereat. +

+ + +

3.55.4 Usage

+ +
    +
  • ... +
+ + + +

3.55.5 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_59.html b/Manuals/Repository/filesystem-html/filesystem_59.html new file mode 100644 index 0000000..21185a0 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_59.html @@ -0,0 +1,287 @@ + + + + + + +CentOS Artwork Repository - File System: 3.56 trunk/Scripts/Bash/Cli/Functions/Render/Config + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.56 trunk/Scripts/Bash/Cli/Functions/Render/Config

+ + + +

3.56.1 Goals

+ +

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

+ + +

3.56.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.56.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.56.2.2 The `render.conf.sh' translation model

+ +

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

+ + +

3.56.2.3 The `render.conf.sh' rendering actions

+ +

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

+

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

+

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

+
ACTIONS[0]='BASE:renderImage'
+
+

Only one `BASE' action must be specified. If more than one +`BASE' action is specified, the last one is used. If no +`BASE' action is specified at all, an error is triggered and the +centos-art.sh script ends its execution. +

+

The `POST' action specifies which action to apply for +each file rendered (at the rendering time). This action is optional. +You can set many different `POST' actions to apply many different +actions over the same already rendered file. Possible values to +`POST' action are `renderFormats', `renderSyslinux', +`renderGrub', etc. +

+

To specify the `POST' action, you need to use set the +`POST:' followed by the function name of the action you want to +perform. The exact form depends on your needs. For example, consider +the following example to produce `xpm', `jpg', and +`tif' images, based on already rendered `png' image, and +also organize the produced files in directories named as their own +extensions: +

+
ACTIONS[0]='BASE:renderImage'
+ACTIONS[1]='POST:renderFormats: xpm jpg tif'
+ACTIONS[2]='POST:groupByFormat: png xpm jpg tif'
+
+

In the previous example, file organization takes place at the moment +of rendering, just after producing the `png' base file and before +going to the next file in the list of files to render. If you don't +want to organized the produced files in directories named as their own +extensions, just remove the `POST:groupByFormat' action line: +

+
ACTIONS[0]='BASE:renderImage'
+ACTIONS[1]='POST:renderFormats: xpm jpg tif'
+
+

The `LAST' action specifies which actions to apply once the last +file in the list of files to process has been rendered. The +`LAST' action is optional. Possible values for `LAST' +actions may be `groupByFormat', `renderGdmTgz', etc. +

+
info

Note

-- Removed(xref: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.56.3 Usage

+ +

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

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

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

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

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

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

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

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

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

+ + + +
3.47 trunk/Scripts/Bash   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_6.html b/Manuals/Repository/filesystem-html/filesystem_6.html new file mode 100644 index 0000000..9c940b7 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_6.html @@ -0,0 +1,178 @@ + + + + + + +CentOS Artwork Repository - File System: 3.3 trunk/Identity/Fonts + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.3 trunk/Identity/Fonts

+ + + +

3.3.1 Goals

+ +

This section exists to organize digital typographies used by the +CentOS project. +

+ + +

3.3.2 Description

+ + + +

3.3.3 Usage

+ +

The CentOS corporate identity is attached to `DejaVu LGC' +font-family. Whatever artwork you design for CentOS project, that +requires typography usage, must be done using `DejaVu LGC' +font-family. +

+
+
Recommendation-1:
+
+

For screen desings (e.g., anything that final destination will never +be printed on paper or any medium outside computer screens) use +`DejaVu LGC Sans' font-family. +

+
+
Recommendation-2:
+
+

For non-screen designs (e.g., anything that final desition will be +printed on paper or any other medium outside computer screens) use +`DejaVu LGC Serif' font-family. As convenction files described in +this rule are stored under `Stationery' directories. +

+
+ +

The only execption for the two recommendations above is the typography +used inside CentOS logo. The CentOS logo is the main visual +representation of the CentOS project so the typography used in it must +be the same always, no matter where it be shown. It also has to be +clear enough to dismiss any confussion between similar typefaces +(e.g., the number one (1) sometimes is confuesed with the letter +`el' (l) or letter `ai' (i)). +

+

As CentOS logo typography convenction, the word `CentOS' uses +`Denmark' typography as base, both for the word `CentOS' and +the phrase `Community Enterprise Operating System'. The phrase +size of CentOS logo is half the size in poits the word `CentOS' +has and it below `CentOS' word and aligned with it on the left. +The distance between `CentOS' word and phrase `Community +Enterprise Operating System' have the size in points the phrase has. +

+

When the CentOS release brand is built, use `Denmark' typography +for the release number. The release number size is two times larger +(in height) than default `CentOS' word. The separation between +release number and `CentOS' word is twice the size in points of +separation between `CentOS' word and phrase `Community +Enterprise Operating System'. +

+

Another component inside CentOS logo is the trademark symbol (TM). +This symbol specifies that the CentOS logo must be consider a product +brand, even it is not a registered one. The trademark symbol uses +DejaVu LGC Sans Regular typography. The trademark symbol is aligned +right-top on the outter side of `CentOS' word. The trademark +symbol must not exceed haf the distance, in points, between +`CentOS' word and the release number on its right. +

+

It would be very convenient for the CentOS Project and its community +to to make a registered trademark (®) of CentOS logo. To make a +register trademark of CentOS Logo prevents legal complications in the +market place of brands. It grants the consistency, through time, of +CentOS project corporate visual identity. +

+
info

Note

The information about trademarks and corporate identity +is my personal interpretation of +http://en.wikipedia.org/Corporate_identity and +http://en.wikipedia.org/Trademark description. If you have +practical experiences with these affairs, please serve yourself to +improve this section with your reasons. +

+ + + +

3.3.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_60.html b/Manuals/Repository/filesystem-html/filesystem_60.html new file mode 100644 index 0000000..e3425ad --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_60.html @@ -0,0 +1,277 @@ + + + + + + +CentOS Artwork Repository - File System: 3.57 trunk/Scripts/Bash/Cli/Functions/Shell + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.57 trunk/Scripts/Bash/Cli/Functions/Shell

+ + + +

3.57.1 Goals

+ +

This section exists to organize files related to shell +functionality of `centos-art.sh' script. +

+ + +

3.57.2 Description

+ +

The shell functionality of `centos-art.sh' script helps +you to maintain bash scripts inside repository. For example, suppose +you've created many functionalities for `centos-art.sh' script, +and you want to use a common copyright and license note for +consistency in all your script files. If you have a bunch of files, +doing this one by one wouldn't be a big deal. In contrast, if the +amount of files grows, updating the copyright and license note for all +of them would be a task rather tedious. The shell functionality +exists to solve maintainance tasks just as the one previously +mentioned. +

+

When you use shell functionality to update copyright inside +script files, it is required that your script files contain (at least) +the following top commentary structure: +

+
+
 1| #!/bin/bash
+ 2| #
+ 3| # doSomething.sh -- The function description goes here.
+ 4| # 
+ 5| # Copyright
+ 6| #
+ 7| # ...
+ 8| #
+ 9| # ----------------------------------------------------------------------
+10| # $Id$
+11| # ----------------------------------------------------------------------
+12|
+13| function doSomething {
+14|     
+15| }
+
+

Figure 3.4: The functions script base comment structure + +

+

Relevant lines in the above structure are lines from 5 to 9. +Everything else in the file is left immutable. +

+

When you are updating copyright through shell +functionality, the `centos-art.sh' script replaces everything +in-between line 5 --the first one matching `^# Copyright .+$' +string-- and line 9--the first long dash separator matching `^# +-+$'-- with the content of copyright template instance. +

+
Caution

Caution

Be sure to add the long dash separator that matches +`^# -+$' regular expression before the function +definition. Otherwise, if the `Copyright' line is present but no +long dash separator exists, `centos-art.sh' will remove anything +in-between the `Copyright' line and the end of file. This way you +may lost your function definitions entirely. +

+ +

The copyright template instance is created from one copyright template +stored in the `Config/tpl_forCopyright.sed' file. The template +instance is created once, and later removed when no longer needed. At +this moment, when template instance is created, the +`centos-art.sh' script takes advantage of automation in order to +set copyright full name and date dynamically. +

+

When you use shell functionality to update copyright, the first +thing `shell' functionality does is requesting copyright +information to user, and later, if values were left empty (i.e., no +value was typed before pressing RET key), the `shell' +functionality uses its own default values. +

+

When shell functionality uses its own default values, the final +copyright note looks like the following: +

+
+
 1| #!/bin/bash
+ 2| #
+ 3| # doSomthing.sh -- The function description goes here.
+ 4| #
+ 5| # Copyright (C) 2003, 2010 The CentOS Project
+ 6| # 
+ 7| # This program is free software; you can redistribute it and/or modify
+ 8| # it under the terms of the GNU General Public License as published by
+ 9| # the Free Software Foundation; either version 2 of the License, or
+10| # (at your option) any later version.
+11| # 
+12| # This program is distributed in the hope that it will be useful, but
+13| # WITHOUT ANY WARRANTY; without even the implied warranty of
+14| # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+15| # General Public License for more details.
+16| #
+17| # You should have received a copy of the GNU General Public License
+18| # along with this program; if not, write to the Free Software
+19| # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
+20| # USA.
+21| #
+22| # ----------------------------------------------------------------------
+23| # $Id$
+24| # ----------------------------------------------------------------------
+25|
+26| function doSomething {
+27|
+28| }
+
+

Figure 3.5: The function script comment example + +

+

Relevant lines in the above structure are lines from 5 to 22. Pay +attention how the copyright line was built, and how the license was +added into the top comment where previously was just three dots. +Everything else in the file was left immutable. +

+

To change copyright information (i.e., full name or year information), +run the shell functionality over the root directory containing +the script files you want to update copyright in and enter the +appropriate information when it be requested. You can run the +shell functionality as many times as you need to. +

+

To change copyright license (i.e., the text in-between lines 7 and +20), you need to edit the `Config/tpl_forCopyright.sed' file, set +the appropriate information, and run the shell functionality +once again for changes to take effect over the files you specify. +

+
Important

Important

The `centos-art.sh' script is released as: +

+
GNU GENERAL PUBLIC LICENSE
+Version 2, June 1991
+
+Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+
+

Do not change the license information under which `centos-art.sh' +script is released. Instead, if you think a different license must be +used, please share your reasons at CentOS Developers mailing list. +

+ + + +

3.57.3 Usage

+ +
+
centos-art sh --update-copyright='path/to/dir'
+
centos-art sh --update-copyright='path/to/dir' --filter='regex'
+

Use these commands to update copyright information in `.sh' files +under `path/to/dir' directory. +

+
+ +

When you provide `--filter='regex'' argument, the list of files +to process is reduced as specified in `regex' regular expression. +Inside `centos-art.sh' script, the `regex' regular +expression is used in combination with find command to look +for files matching the regular expression path pattern. +

+
Warning

Warning

In order for `regex' regular expression to match +a file, the `regex' regular expresion must match the whole file +path not just the file name. +

+ +

For example, if you want to match all `render.conf.sh' files +inside `path/to/dir', use the .+/render.conf regular +expression. Later, `centos-art.sh' script uses this value inside +^$REGEX\.sh$ expression in order to build the final regular +expression (i.e., ^.+/render.conf\.sh$) that is evaluated +against available file paths inside the list of files to process. +

+

Exceptionally, when you provide `--filter='regex'' in the way +that `regex', appended to `path/to/dir/' (i.e. +`path/to/dir/regex'), matches a regular file; the +`centos-art.sh' script uses the file matching as only file in the +list of files to process. +

+ + +

3.57.4 See also

+ + + +
3.47 trunk/Scripts/Bash   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_61.html b/Manuals/Repository/filesystem-html/filesystem_61.html new file mode 100644 index 0000000..10c9a6d --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_61.html @@ -0,0 +1,309 @@ + + + + + + +CentOS Artwork Repository - File System: 3.58 trunk/Scripts/Bash/Cli/Functions/Svg + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.58 trunk/Scripts/Bash/Cli/Functions/Svg

+ + + +

3.58.1 Goals

+ +

This section exists to organize files related to svg +functionality of `centos-art.sh' script. +

+ + +

3.58.2 Description

+ +

The svg functionality of `centos-art.sh' script helps you +to maintain scalable vector graphics (SVG) inside repository. For +example, suppose you've been working in CentOS default design models +under `trunk/Identity/Themes/Models/', and you want to set common +metadata to all of them, and later remove all unused SVG defintions +from `*.svg' files. Doing so file by file may be a tedious task, +so the `centos-art.sh' script provides the svg +functionality to aid you maintain such actions. +

+ + + +

3.58.2.1 Metadata maintainance

+ +

The metadata used is defined by Inkscape 0.46 using the SVG standard +markup. The `centos-art.sh' script replaces everything +in-between <metadata and </metadata> tags with a +predefined metadata template we've set for this purpose. +

+

The metadata template was created using the metadata information of a +file which, using Inkscape 0.46, all metadata fields were set. This +created a complete markup representation of how SVG metadata would +look like. Later, we replaced every single static value with a +translation marker in the form `=SOMETEXT=', where +SOMETEXT is the name of its main opening tag. Later, we +transform the metadata template into a sed replacement set of commads +escaping new lines at the end of each line. +

+

With metadata template in place, the `centos-art.sh' script uses +it to create a metadata template instance for the file being processed +currently. The metadata template instance contains the metadata +portion of sed replacement commands with translation markers already +traduced. In this action, instance creation, is where we take +advantage of automation and generate metadata values like title, date, +keywords, source, identifier, and relation dynamically, based on the +file path `centos-art.sh' script is currently creating metadata +information for. +

+

With metadata template instance in place, the `centos-art.sh' +script uses it to replace real values inside all `.svg' files +under the current location you're running the `centos-art.sh' +script on. Default behaviour is to ask user to enter each metadatum +required, one by one. If user leaves metadatum empty, by pressing +RET key, `centos-art.sh' uses its default value. +

+

The `centos-art.sh' script modifies the following metadata: +

+
+
`Title'
+

Name by which this document is formally known. If no value is set +here, `centos-art.sh' script uses the file name as title. +

+
+
`Date'
+

Date associated with the creation of this document (YYYY-MM-DD). If no +value is set here, `centos-art.sh' script uses the current date +information as in date +%Y-%m-%d. +

+
+
`Creator'
+

Name of entity primarily responsible for making the content of this +document. If no value is set here, `centos-art.sh' script uses +the string `The CentOS Project'. +

+
+
`Rights'
+

Name of entity with rights to the intellectual Property of this +document. If no value is set here, `centos-art.sh' script uses +the string `The CentOS Project'. +

+
+
`Publisher'
+

Name of entity responsible for making this document available. If no +value is set here, `centos-art.sh' script uses the string +`The CentOS Project'. +

+
+
`Identifier'
+

Unique URI to reference this document. If no value is set here, +`centos-art.sh' script uses the current file path to build the +related url that points to current file location inside repository +central server. +

+
+
`Source'
+

Unique URI to reference the source of this document. If no value is +set here, `centos-art.sh' script uses current file path to build +the related url that points to current file location inside repository +central server. +

+
+
`Relation'
+

Unique URI to a related document. If no value is set here, +`centos-art.sh' script uses current file path to build the +related url that points to current file location inside repository +central server. +

+
+
`Language'
+

Two-letter language tag with optional subtags for the language of this +document. (e.g. `en-GB'). If no value is set here, +`centos-art.sh' script uses the current locale information as in +cli_getCurrentLocale function. +

+
+
`Keywords'
+

The topic of this document as comma-separated key words, prhases, or +classifications. If no value is set here, `centos-art.sh' script +uses file path to build +

+
+
`Coverage'
+

Extent or scope of this document. If no value is set here, +`centos-art.sh' script uses the string `The CentOS Project'. +

+
+
`Description'
+

Description about the document. If no value is set here, +`centos-art.sh' script uses uses empty value as default. +

+
+
`Contributors'
+

People that contributes in the creation/maintainance of the document. +If no value is set here, `centos-art.sh' script uses uses empty +value as default. +

+
+ +

The `License' metadatum is not set as a choise, by now. It is +fixed Creative Common Attribution Share-Alike 3.0 License. This is done in order to +grant license consistency among all SVG files we manage inside CentOS +Artwork Repository. +

+ + + +

3.58.2.2 Unused definitions

+ +

Many of the no-longer-used gradients, patterns, and markers (more +precisely, those which you edited manually) remain in the +corresponding palettes and can be reused for new objects. However if +you want to optimize your document, use the `Vacuum Defs' command +in `File' menu. It will remove any gradients, patterns, or +markers which are not used by anything in the document, making the +file smaller. +

+

If you have one or two couple of files, removing unused definitions +using the graphical interface may be enough to you. In contrast, if +you have dozens or even houndreds of scalable vector graphics files to +maintain it is not a fun task to use the graphical interface to remove +unused definitions editing those files one by one. +

+

To remove unused definitions from several scalable vector graphics +files, the `centos-art.sh' script uses Inkscape command-line +interface, specifically with the `--vaccum-defs' option. +

+ + +

3.58.3 Usage

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

Use these commands to update metadata information to `.svg' files +under `path/to/dir' directory. +

+
+
centos-art svg --vacuum-defs='path/to/dir'
+
centos-art svg --vacuum-defs='path/to/dir' --filter='regex'
+

Use these commands to remove unused definitions inside `.svg' +files under `path/to/dir' directory. +

+
+ +

When you provide `--filter='regex'' argument, the list of files +to process is reduced as specified in `regex' regular expression. +Inside `centos-art.sh' script, the `regex' regular +expression is used in combination with find command to look +for files matching the regular expression path pattern. +

+
Warning

Warning

In order for `regex' regular expression to match +a file, the `regex' regular expresion must match the whole file +path not just the file name. +

+ +

For example, if you want to match all `summary.svg' files inside +`path/to/dir', use the .+/summary regular expression. +Later, `centos-art.sh' script uses this value inside +^$REGEX\.svg$ expression in order to build the final regular +expression (i.e., ^.+/summary\.svg$) that is evaluated against +available file paths inside the list of files to process. +

+

Exceptionally, when you provide `--filter='regex'' in the way +that `regex', appended to `path/to/dir/' (i.e. +`path/to/dir/regex'), matches a regular file; the +`centos-art.sh' script uses the file matching as only file in the +list of files to process. +

+ + +

3.58.4 See also

+ + + +
3.47 trunk/Scripts/Bash   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_62.html b/Manuals/Repository/filesystem-html/filesystem_62.html new file mode 100644 index 0000000..7f832b4 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_62.html @@ -0,0 +1,356 @@ + + + + + + +CentOS Artwork Repository - File System: 3.59 trunk/Scripts/Bash/Cli/Functions/Verify + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.59 trunk/Scripts/Bash/Cli/Functions/Verify

+ + + +

3.59.1 Goals

+ +

This section exists to organize files related to `centos-art.sh' +script `verify' functionality. The `verify' +functionality of `centos-art.sh' script helps you to verify the +workstation configuration you are planning to use as host for your +working copy of CentOS Artwork Repository. +

+ + +

3.59.2 Description

+ +

The first time you download CentOS Artwork Repository you need to +configure your workstation in order to use `centos-art.sh' +script. These preliminar configurations are based mainly on auxiliar +RPM packages installation, symbolic links creations, and environment +variables definitions. The `verify' functionality of +`centos-art.sh' script guides you through this preliminar +configuration process. +

+

If this is the first time you run `centos-art.sh' script, the +appropriate way to use its `verify' functionality is not using +the `centos-art.sh' script directly, but the absolute path to +centos-art.sh script instead (i.e., +`~/artwork/trunk/Scripts/Bash/centos-art.sh'). This is necessary +because `centos-art' symbolic link, under `~/bin/' +directory, has not been created yet. +

+ + +

3.59.2.1 Packages

+ +

Installation of auxiliar RPM packages provides the software required +to manipulate files inside the repository (e.g., image files, +documentation files, translation files, script files, etc.). Most of +RPM packages centos-art.sh script uses are shipped with +CentOS distribution, and can be installed from CentOS base repository. +The only exception is `inkscape', the package we use to +manipulate SVG files. The `inkscape' package is not inside +CentOS distribution so it needs to be installed from third party +repositories. +

+
info

Note

Configuration of third party repositories inside CentOS +distribution is described in CentOS wiki, specifically in the +following URL: +http://wiki.centos.org/AdditionalResources/Repositories +

+ +

Before installing packages, the `centos-art.sh' script uses +sudo to request root privileges to execute yum +installation functionality. If your user isn't defined as a +privileged user--at least to run yum commands-- inside +`/etc/sudoers' configuration file, you will not be able to +perform package installation tasks as set in `centos-art.sh' +script `verify' functionality. +

+

Setting sudo privileges to users is an administrative task you have to +do by yourself. If you don't have experience with sudo +command, please read its man page running the command: man +sudo. This reading will be very useful, and with some practice, you +will be able to configure your users to have sudo +privileges. +

+ + +

3.59.2.2 Links

+ +

Creation of symbolic links helps us to alternate between different +implementations of `centos-art.sh' script-line (e.g., +`centos-art.sh', for Bash implementation; `centos-art.py', +for Python implementation; `centos-art.pl', for Perl +implementation; and so on for other implementations). The +`centos-art.sh' script-line definition takes place inside your +personal binary (`~/bin/') directory in order to make the script +implementation --the one that `centos-art' links to-- available +to PATH environment variable. +

+

Creation of symbolic links helps us to reuse components from repository +working copy. For example, color information files maintained inside +your working copy must never be duplicated inside program-specific +configuration directories that uses them in your workstation (e.g., +Gimp, Inkscape, etc.). Instead, a symbolic link must be created for +each one of them, from program-specific configuration directories to +files in the working copy. In this configuration, when someone +commits changes to color information files up to central repository, +they--the changes committed-- will be immediatly available to your +programs the next time you update your working copy --the place +inside your workstation those color information files are stored--. +

+

Creation of symbolic links helps us to make `centos-art.sh' +script functionalities available outside `trunk/' repository +directory structure, but at its same level in repository tree. This is +useful if you need to use the "render" functionality of +centos-art.sh under `branches/' repository directory +structure as you usually do inside `trunk/' repository directory +structure. As consequence of this configuration, automation scripts +cannot be branched under `branches/Scripts' directory structure. +

+ + +

3.59.2.3 Environment variables

+ +

Definition of environemnt variables helps us to set default values to +our user session life. The user session environment variable defintion +takes place in the user's `~/.bash_profile' file. The +`verify' functionality of `centos-art.sh' script doesn't +modify your `~/.bash_profile' file. +

+

The `verify' functionality of `centos-art.sh' script +evaluates the following environment variables: +

+
+
EDITOR
+

Default text editor. +

+

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

+

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

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

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

+
+
TEXTDOMAIN
+
+

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

+
+
TEXTDOMAINDIR
+
+

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

+
+
LANG
+
+

Default locale information. +

+

This variable is initially set in the configuration process of CentOS +distribution installer (i.e., Anaconda), specifically in the +`Language' step; or once installed using the +system-config-language tool. +

+

The `centos-art.sh' script uses the LANG environment +variable to know in which language the script messages are printed +out. +

+
+
TZ
+
+

Default time zone representation. +

+

This variable is initially set in the configuration process of CentOS +distribution installer (i.e., Anaconda), specifically in the +`Date and time' step; or once installed using the +system-config-date tool. +

+

The `centos-art.sh' script doesn't use the TZ environment +variable information at all. Instead, this variable is used by the +system shell to show the time information according to your phisical +location on planet Earth. +

+

Inside your computer, the time information is firstly set in the BIOS +clock (which may need correction), and later in the configuration +process of CentOS distribution installer (or later, by any of the +related configuration tools inside CentOS distribution). Generally, +setting time information is a straight-forward task and configuration +tools available do cover most relevant location. However, if you need +a time precision not provided by the configuration tools available +inside CentOS distribution then, using TZ variable may be +necessary. +

+
Convenction

Convenction

In order to keep changes syncronized between +central repository and its working copies: configure both repository +server and workstations (i.e., the place where each working copy is +set on) to use Coordinated Universal Time (UTC) as base time +representation. Later, correct the time information for your specific +location using time zone correction. +

+ +

The format of TZ environment variable is described in +`tzset(3)' manual page. +

+
+
+ + + +

3.59.3 Usage

+ +
+
centos-art verify --packages
+
+

Verify required packages your workstation needs in order to run the +`centos-art.sh' script correctly. If there are missing packages, +the `centos-art.sh' script asks you to confirm their +installation. When installing packages, the `centos-art.sh' +script uses the yum application in order to achieve the +task. +

+

In case all packages required by `centos-art.sh' script are +already installed in your workstation, the message `The required +packages are already installed.' is output for you to know. +

+
+
centos-art verify --links
+
+

Verify required links your workstation needs in order to run the +centos-art command correctly. If any required link is missing, the +centos-art.sh script asks you to confirm their installation. +To install required links, the centos-art.sh script uses the +ln command. +

+

In case all links required by `centos-art.sh' script are already +created in your workstation, the message `The required links are +already installed.' is output for you to know. +

+

In case a regular file exists with the same name of a required link, +the `centos-art.sh' script outputs the `Already exists as +regular file.' message when listing required links that will be +installed. Of course, as there is already a regular file where must be +a link, no link is created. In such cases the `centos-art.sh' +script will fall into a continue installation request for that missing +link. To end this continue request you can answer `No', or +remove the existent regular file to let `centos-art.sh' script +install the link on its place. +

+
+
centos-art verify --environment
+
centos-art verify --environment --filter='regex'
+
+

Output a brief description of environment variables used by +`centos-art.sh' script. +

+

If `--filter' option is provided, output is reduced as defined in +the `regex' regular expression value. If `--filter' option +is specified but `regex' value is not, the `centos-art.sh' +script outputs information as if `--filter' option had not been +provided at all. +

+
+
+ + + +

3.59.4 See also

+ + + +
3.47 trunk/Scripts/Bash   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_63.html b/Manuals/Repository/filesystem-html/filesystem_63.html new file mode 100644 index 0000000..ed7e391 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_63.html @@ -0,0 +1,123 @@ + + + + + + +CentOS Artwork Repository - File System: 3.60 trunk/Scripts/Python + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.60 trunk/Scripts/Python

+ + + +

3.60.1 Goals

+ +
    +
  • ... +
+ + + +

3.60.2 Description

+ +
    +
  • ... +
+ + + +

3.60.3 Usage

+ +
    +
  • ... +
+ + + +

3.60.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_64.html b/Manuals/Repository/filesystem-html/filesystem_64.html new file mode 100644 index 0000000..96bed8d --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_64.html @@ -0,0 +1,196 @@ + + + + + + +CentOS Artwork Repository - File System: Index + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

Index

+
Jump to:   B +   +H +   +M +   +T +   +U +   +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Index Entry Section
B
branches1. branches
H
How to render brands' translation files3.36.3 Usage
How to render fonts' translation files3.38.3 Usage
M
Metadata maintainance3.58.2 Description
T
tags2. tags
Translation brands file names3.36.2.1 Conventional file names
Translation brands file names3.36.2.2 Numeric file names
trunk3. trunk
trunk Identity3.1 trunk/Identity
trunk Identity Brands3.2 trunk/Identity/Brands
trunk Identity Fonts3.3 trunk/Identity/Fonts
trunk Identity Icons3.4 trunk/Identity/Icons
trunk Identity Isolinux3.5 trunk/Identity/Isolinux
trunk Identity Models3.6 trunk/Identity/Models
trunk Identity Models Css3.7 trunk/Identity/Models/Css
trunk Identity Models Html3.8 trunk/Identity/Models/Html
trunk Identity Models Img Promo Web3.9 trunk/Identity/Models/Img/Promo/Web
trunk Identity Models Tpl3.10 trunk/Identity/Models/Tpl
trunk Identity Models Tpl Promo Web3.11 trunk/Identity/Models/Tpl/Promo/Web
trunk Identity Models Xcf3.12 trunk/Identity/Models/Xcf
trunk Identity Release3.13 trunk/Identity/Release
trunk Identity Themes3.14 trunk/Identity/Themes
trunk Identity Themes Models3.15 trunk/Identity/Themes/Models
trunk Identity Themes Models Alternative3.16 trunk/Identity/Themes/Models/Alternative
trunk Identity Themes Models Default3.17 trunk/Identity/Themes/Models/Default
trunk Identity Themes Models Default Distro3.18 trunk/Identity/Themes/Models/Default/Distro
trunk Identity Themes Models Default Distro Anaconda3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda
trunk Identity Themes Models Default Promo3.20 trunk/Identity/Themes/Models/Default/Promo
trunk Identity Themes Models Default Web3.21 trunk/Identity/Themes/Models/Default/Web
trunk Identity Themes Motifs3.22 trunk/Identity/Themes/Motifs
trunk Identity Themes Motifs Flame3.23 trunk/Identity/Themes/Motifs/Flame
trunk Identity Themes Motifs Modern3.24 trunk/Identity/Themes/Motifs/Modern
trunk Identity Themes Motifs Modern Backgrounds3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds
trunk Identity Themes Motifs Modern Backgrounds Img3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img
trunk Identity Themes Motifs Modern Backgrounds Tpl3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl
trunk Identity Themes Motifs Modern Backgrounds Xcf3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf
trunk Identity Themes Motifs Modern Distro Anaconda Progress3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress
trunk Identity Themes Motifs Modern Palettes3.30 trunk/Identity/Themes/Motifs/Modern/Palettes
trunk Identity Themes Motifs TreeFlower3.31 trunk/Identity/Themes/Motifs/TreeFlower
trunk Identity Themes Motifs TreeFlower Backgrounds3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds
trunk Identity Widgets3.33 trunk/Identity/Widgets
trunk Locales3.34 trunk/Locales
trunk Locales Identity3.35 trunk/Locales/Identity
trunk Locales Identity Brands3.36 trunk/Locales/Identity/Brands
trunk Locales Identity Brands Tpl3.37 trunk/Locales/Identity/Brands/Tpl
trunk Locales Identity Fonts3.38 trunk/Locales/Identity/Fonts
trunk Locales Identity Models3.39 trunk/Locales/Identity/Models
trunk Locales Identity Release3.40 trunk/Locales/Identity/Release
trunk Locales Identity Themes3.41 trunk/Locales/Identity/Themes
trunk Locales Identity Themes Backgrounds3.42 trunk/Locales/Identity/Themes/Backgrounds
trunk Locales Identity Themes Distro Anaconda Progress3.43 trunk/Locales/Identity/Themes/Distro/Anaconda/Progress
trunk Locales Identity Widgets3.44 trunk/Locales/Identity/Widgets
trunk Manuals3.45 trunk/Manuals
trunk Scripts3.46 trunk/Scripts
trunk Scripts Bash3.47 trunk/Scripts/Bash
trunk Scripts Bash Cli3.48 trunk/Scripts/Bash/Cli
trunk Scripts Bash Cli Functions3.49 trunk/Scripts/Bash/Cli/Functions
trunk Scripts Bash Cli Functions Help3.50 trunk/Scripts/Bash/Cli/Functions/Help
trunk Scripts Bash Cli Functions Html3.51 trunk/Scripts/Bash/Cli/Functions/Html
trunk Scripts Bash Cli Functions Locale3.52 trunk/Scripts/Bash/Cli/Functions/Locale
trunk Scripts Bash Cli Functions Manual3.53 trunk/Scripts/Bash/Cli/Functions/Manual
trunk Scripts Bash Cli Functions Path3.54 trunk/Scripts/Bash/Cli/Functions/Path
trunk Scripts Bash Cli Functions Render3.55 trunk/Scripts/Bash/Cli/Functions/Render
trunk Scripts Bash Cli Functions Render Config3.56 trunk/Scripts/Bash/Cli/Functions/Render/Config
trunk Scripts Bash Cli Functions Shell3.57 trunk/Scripts/Bash/Cli/Functions/Shell
trunk Scripts Bash Cli Functions Svg3.58 trunk/Scripts/Bash/Cli/Functions/Svg
trunk Scripts Bash Cli Functions Verify3.59 trunk/Scripts/Bash/Cli/Functions/Verify
trunk Scripts Python3.60 trunk/Scripts/Python
U
Unused definitions3.58.2.1 Metadata maintainance
+
Jump to:   B +   +H +   +M +   +T +   +U +   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_65.html b/Manuals/Repository/filesystem-html/filesystem_65.html new file mode 100644 index 0000000..06499ed --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_65.html @@ -0,0 +1,103 @@ + + + + + + +CentOS Artwork Repository - File System: List of Figures + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

List of Figures

+
+
Figure 3.1

The functionalities initialization environment. +

+
Figure 3.2

The actions initialization environment. +

+
Figure 3.3

The cli_commitRepoChanges function output. +

+
Figure 3.4

The functions script base comment structure +

+
Figure 3.5

The function script comment example +

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_66.html b/Manuals/Repository/filesystem-html/filesystem_66.html new file mode 100644 index 0000000..8f7f279 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_66.html @@ -0,0 +1,103 @@ + + + + + + +CentOS Artwork Repository - Filesystem: List of Figures + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

List of Figures

+
+
Figure 3.1

The functionalities initialization environment. +

+
Figure 3.2

The actions initialization environment. +

+
Figure 3.3

The cli_commitRepoChanges function output. +

+
Figure 3.4

The functions script base comment structure +

+
Figure 3.5

The function script comment example +

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

+ + This document was generated on February, 28 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_67.html b/Manuals/Repository/filesystem-html/filesystem_67.html new file mode 100644 index 0000000..35705dd --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_67.html @@ -0,0 +1,103 @@ + + + + + + +CentOS Artwork Repository - Filesystem: List of Figures + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

List of Figures

+
+
Figure 3.1

The functionalities initialization environment. +

+
Figure 3.2

The actions initialization environment. +

+
Figure 3.3

The cli_commitRepoChanges function output. +

+
Figure 3.4

The functions script base comment structure +

+
Figure 3.5

The function script comment example +

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

+ + This document was generated on February, 28 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_7.html b/Manuals/Repository/filesystem-html/filesystem_7.html new file mode 100644 index 0000000..50e776a --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_7.html @@ -0,0 +1,112 @@ + + + + + + +CentOS Artwork Repository - File System: 3.4 trunk/Identity/Icons + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.4 trunk/Identity/Icons

+ + + +

3.4.1 Goals

+ +
    +
  • ... +
+ + + +

3.4.2 Description

+ + + +

3.4.3 Usage

+ + + +

3.4.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_8.html b/Manuals/Repository/filesystem-html/filesystem_8.html new file mode 100644 index 0000000..ec115b2 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_8.html @@ -0,0 +1,112 @@ + + + + + + +CentOS Artwork Repository - File System: 3.5 trunk/Identity/Isolinux + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.5 trunk/Identity/Isolinux

+ + + +

3.5.1 Goals

+ +
    +
  • ... +
+ + + +

3.5.2 Description

+ + + +

3.5.3 Usage

+ + + +

3.5.4 See also

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

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_9.html b/Manuals/Repository/filesystem-html/filesystem_9.html new file mode 100644 index 0000000..2d21314 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_9.html @@ -0,0 +1,123 @@ + + + + + + +CentOS Artwork Repository - File System: 3.6 trunk/Identity/Models + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]         [Top][Contents][Index][ ? ]
+ + +

3.6 trunk/Identity/Models

+ + + +

3.6.1 Goals

+ +

This section exists to organize design models. +

+ + +

3.6.2 Description

+ +

Design models are representative designs useful to understand how +to build artworks. +

+ + +

3.6.3 Usage

+ + + +

3.6.4 See also

+ + + + + + +
3.8 trunk/Identity/Models/Html   +
3.7 trunk/Identity/Models/Css   +
3.10 trunk/Identity/Models/Tpl   +
3.12 trunk/Identity/Models/Xcf   +
+ + + + + + + + + +
[ < ][ > ]   [ << ][ Up ][ >> ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_abt.html b/Manuals/Repository/filesystem-html/filesystem_abt.html new file mode 100644 index 0000000..a6c2ab8 --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_abt.html @@ -0,0 +1,177 @@ + + + + + + +CentOS Artwork Repository - File System: About This Document + + + + + + + + + + + + + + + + + + + + +
[Top][Contents][Index][ ? ]
+

About This Document

+

+ This document was generated on March, 1 2011 using texi2html 1.76. +

+

+ The buttons in the navigation panels have the following meaning: +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Button Name Go to From 1.2.3 go to
[ < ] Backprevious section in reading order1.2.2
[ > ] Forwardnext section in reading order1.2.4
[ << ] FastBackbeginning of this chapter or previous chapter1
[ Up ] Upup section1.2
[ >> ] FastForwardnext chapter2
[Top] Topcover (top) of document  
[Contents] Contentstable of contents  
[Index] Indexindex  
[ ? ] Aboutabout (help)  
+ +

+ where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure: +

+ +
    +
  • 1. Section One +
      +
    • 1.1 Subsection One-One +
        +
      • ...
        • +
      +
      • +
    • 1.2 Subsection One-Two +
        +
      • 1.2.1 Subsubsection One-Two-One
        • +
      • 1.2.2 Subsubsection One-Two-Two
        • +
      • 1.2.3 Subsubsection One-Two-Three     + <== Current Position
        • +
      • 1.2.4 Subsubsection One-Two-Four
        • +
      +
      • +
    • 1.3 Subsection One-Three +
        +
      • ...
        • +
      +
      • +
    • 1.4 Subsection One-Four
      • +
    +
    • +
+ + + + + + + +
[Top][Contents][Index][ ? ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_fot.html b/Manuals/Repository/filesystem-html/filesystem_fot.html new file mode 100644 index 0000000..d2d8b3e --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_fot.html @@ -0,0 +1,80 @@ + + + + + + +CentOS Artwork Repository - File System: Footnotes + + + + + + + + + + + + + + + + + + + + +
[Top][Contents][Index][ ? ]
+

Footnotes

+

(1)

+

The theme support of Mailman may be introduced in +mailman-3.x.x release. +

+ + + + + +
[Top][Contents][Index][ ? ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-html/filesystem_toc.html b/Manuals/Repository/filesystem-html/filesystem_toc.html new file mode 100644 index 0000000..f3cebbf --- /dev/null +++ b/Manuals/Repository/filesystem-html/filesystem_toc.html @@ -0,0 +1,573 @@ + + + + + + +CentOS Artwork Repository - File System: Table of Contents + + + + + + + + + + + + + + + + + + + + +
[Top][Contents][Index][ ? ]
+

Table of Contents

+
+ + +
+ + + + + + +
[Top][Contents][Index][ ? ]
+

+ + This document was generated on March, 1 2011 using texi2html 1.76. + +
+ +

+ + diff --git a/Manuals/Repository/filesystem-index.texi b/Manuals/Repository/filesystem-index.texi new file mode 100644 index 0000000..a6413a5 --- /dev/null +++ b/Manuals/Repository/filesystem-index.texi @@ -0,0 +1,9 @@ +@node Index +@unnumbered Index +@printindex cp + +@node List of Figures +@unnumbered List of Figures +@ifnotinfo +@listoffloats Figure +@end ifnotinfo diff --git a/Manuals/Repository/filesystem-latex/Concepts/CentOS/community.tex b/Manuals/Repository/filesystem-latex/Concepts/CentOS/community.tex new file mode 100644 index 0000000..34d8eff --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/CentOS/community.tex @@ -0,0 +1,23 @@ +% ------------------------------------------------------------ +% $Id: community.tex 6024 2010-06-28 04:28:27Z al $ +% ------------------------------------------------------------ + \section{The CentOS Community} +\hypertarget{sec:Concepts:CentOS:Community}{} + \label{sec:Concepts:CentOS:Community} + +The CentOS Project is designed for people who need an enterprise class +operating system without the cost or support of the prominent North +American Enterprise Linux vendor. + +\begin{description} + +\item[CentOS Administrators:] People building CentOS Distribution and +its infrastructure are considered CentOS Administrators. Each CentOS +Distribution has an Administrator Leader. + +\item[CentOS Community Members:] People using CentOS Distribution are +concidered CentOS Community Members. Inside CentOS Community, Members +affiliate Special Interest Groups (SIGs). Special Interest Groups help +to organize and distribute work inside The CentOS Project. + +\end{description} diff --git a/Manuals/Repository/filesystem-latex/Concepts/CentOS/distribution.tex b/Manuals/Repository/filesystem-latex/Concepts/CentOS/distribution.tex new file mode 100644 index 0000000..bdf41ed --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/CentOS/distribution.tex @@ -0,0 +1,30 @@ +% ------------------------------------------------------------ +% $Id: distribution.tex 6024 2010-06-28 04:28:27Z al $ +% ------------------------------------------------------------ + \section{The CentOS Distribution} +\hypertarget{sec:Concepts:CentOS:Distribution}{} + \label{sec:Concepts:CentOS:Distribution} + +The CentOS Distribution is a free enterprise class computing platform +to anyone who wishes to use it. The CentOS Distribution is built from +publicly available open source SRPMS provided by a prominent North +American Enterprise Linux vendor. The CentOS Distribution conforms +fully with the upstream vendors redistribution policies and aims to be +100\% binary compatible (The CentOS Project mainly changes packages to +remove upstream vendor branding and artwork.). + +The CentOS Project releases its CentOS Distribution as a GPL work. The +GPL applies to the software collection known as the CentOS +Distribution. Individual packages included in the distribution +include their own licenses and the GPL applies to all packages that it +does not clash with. If there is a clash between the GPL and +individual package licenses, the individual package license applies +instead. + +Neither the CentOS Project (we who build CentOS Distribution) nor any +version of CentOS Distribution is affiliated with, produced by, or +supported by the prominent North American Enterprise Linux vendor. +Neither does our software contain the upstream vendor's product \dots +although it is built from the same open source SRPMS as the upstream +enterprise products. + diff --git a/Manuals/Repository/filesystem-latex/Concepts/CentOS/incorporation.tex b/Manuals/Repository/filesystem-latex/Concepts/CentOS/incorporation.tex new file mode 100644 index 0000000..3cf5003 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/CentOS/incorporation.tex @@ -0,0 +1,6 @@ + +\section{The CentOS Incorporation} + +The CentOS Project is a legal entity separate from the persons who own +it or the persons who manage or operate it. + diff --git a/Manuals/Repository/filesystem-latex/Concepts/CentOS/introduction.tex b/Manuals/Repository/filesystem-latex/Concepts/CentOS/introduction.tex new file mode 100644 index 0000000..0bbe3ef --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/CentOS/introduction.tex @@ -0,0 +1,8 @@ + +This chapter describes the CentOS Project as legal entity. It +describes how the incorporation would survive longer than the lives of +any particular member, existing in perpetuity. Information in this +chapter provides the emotional tools that CentOS Community needs, in +order to create a strong feeling of identification with the CentOS +Project and its mission. + diff --git a/Manuals/Repository/filesystem-latex/Concepts/CentOS/mission.tex b/Manuals/Repository/filesystem-latex/Concepts/CentOS/mission.tex new file mode 100644 index 0000000..c3dd2bf --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/CentOS/mission.tex @@ -0,0 +1,9 @@ +% ------------------------------------------------------------ +% $Id: mission.tex 6024 2010-06-28 04:28:27Z al $ +% ------------------------------------------------------------ + \section{The CentOS Mission} +\hypertarget{sec:Concepts:CentOS:Mission}{} + \label{sec:Concepts:CentOS:Mission} + +The CentOS Project exists to provide the CentOS Distribution. + diff --git a/Manuals/Repository/filesystem-latex/Concepts/CentOS/organization.tex b/Manuals/Repository/filesystem-latex/Concepts/CentOS/organization.tex new file mode 100644 index 0000000..08c9ec6 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/CentOS/organization.tex @@ -0,0 +1,12 @@ + +\section{The CentOS Organization} + +The CentOS Project is organized and managed on Internet by a group of +Administrators which provide their knowledge and personal resources to +build the different major releases of CentOS Distribution and maintain +the required infrastructure. + +The CentOS Project exists by its own, it is not affilieted with any +other organization. The only source of hardware or funding to +distribute the CentOS Distribution is by donations. + diff --git a/Manuals/Repository/filesystem-latex/Concepts/CentOS/philosophy.tex b/Manuals/Repository/filesystem-latex/Concepts/CentOS/philosophy.tex new file mode 100644 index 0000000..0110ad4 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/CentOS/philosophy.tex @@ -0,0 +1,5 @@ + +\section{The CentOS Philosophy} + +The CentOS Project is higly based on meritocracy. + diff --git a/Manuals/Repository/filesystem-latex/Concepts/CentOS/release.tex b/Manuals/Repository/filesystem-latex/Concepts/CentOS/release.tex new file mode 100644 index 0000000..2ce9409 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/CentOS/release.tex @@ -0,0 +1,46 @@ +% ------------------------------------------------------------ +% $Id: release.tex 6024 2010-06-28 04:28:27Z al $ +% ------------------------------------------------------------ + \section{The CentOS Release Schema} +\hypertarget{sec:Concepts:CentOS:Release}{} + \label{sec:Concepts:CentOS:Release} + +The upstream vendor has released 4 versions of enterprise Linux that +CentOS rebuilds the freely available SRPMS for. So, the major CentOS +releases are CentOS 2, CentOS 3, CentOS 4 and CentOS 5. The upstream +vendor releases security updates as required by circumstances. CentOS +releases rebuilds of security updates as soon as possible. Usually +within 24 hours (our stated goal is with 72 hours, but we are usually +much faster). + +The upstream vendor also releases numbered update sets for Version 3, +Version 4 and Version 5 of their product (Currently EL 3 update 9, EL +4 update 6 and EL 5 update 1) 2 to 4 times per year. There are new +ISOs from the upstream vendor provided for these update sets. Update +sets will be completed as soon as possible after the vendor releases +their version ... generally within 2 weeks. CentOS follows these +conventions as well, so CentOS 3.9 correlates with EL 3 update 9 and +CentOS 4.6 correlates with EL 4 update 6, CentOS 5.1 correlates to EL +5 update 1, etc. + +One thing some people have problems understanding is that if you have +any CentOS-3 product and update it, you will be updated to the latest +CentOS-3.x version. + +The same is true for CentOS-4 and CentOS 5. If you update any CentOS-4 +product, you will be updated to the latest CentOS-4.x version, or to +the latest CentOS 5.x version if you are updating a CentOS 5 system. +This is exactly the same behavior as the upstream product. Let's +assume that the latest EL4 product is update 6. If you install the +upstream original EL4 CDs (the ones before any update set) and upgrade +via their up2date, you will have latest update set installed (EL4 +update 6 in our example). Since all updates within a major release +(CentOS 2, CentOS 3, CentOS 4, CentOS 5) always upgrade to the latest +version when updates are performed (thus mimicking upstream behavior), +only the latest version is maintained in each main tree on the CentOS +mirrors. + +There is a CentOS Vault containing old CentOS trees. This vault is a +picture of the older tree when it was removed from the main tree, and +does not receive updates. It should only be used for reference. + diff --git a/Manuals/Repository/filesystem-latex/Concepts/Frameworks/files.tex b/Manuals/Repository/filesystem-latex/Concepts/Frameworks/files.tex new file mode 100644 index 0000000..e78a961 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/Frameworks/files.tex @@ -0,0 +1,53 @@ +% Part : Concepts +% Chapter: Frameworks +% ------------------------------------------------------------ +% $Id: files.tex 6044 2010-07-11 07:49:09Z al $ +% ------------------------------------------------------------ + +\section{File Types} + +Inside CentOS Artwork Repository, there are ``image files'' and ``text +files''. + +\subsection{Image Files} +\hypertarget{sec:Concepts:Frameworks:Image}{} + +Image files are used to implement the CentOS visual style on all +CentOS visual manifestations where image files are involved (i.e. +CentOS distribution, CentOS web sites, CentOS promotion, etc.). Image +files are inside identity frameworks. + +Image files may be available in different formats. Image files in +different formats are produced taking the PNG format as base. The PNG +format is the Inkscape's export format used by \texttt{render.sh} +indentity script to produce a image copy of the SVG design templates. +The \texttt{render.sh} identity script uses command line image +manipulation tools, like ImageMagick and Netpbm, to do image format +convertions from PNG to the formats you specify. You can produce as +many image formats as supported by the previously mentioned command +line image maipulation tools. + +Image files production in different formats is specified inside +configuration scripts, specifically in the variable +\hyperlink{sec:Concepts:Scripts:Configuration:ACTIONS}{\texttt{ACTIONS}} +(\autoref{sec:Concepts:Scripts:Configuration:ACTIONS}). + +Inside frameworks, image files are stored in a directory named `img'. +This name is a convenction that scripts use to store framework's +produced images. If you want to change the image directory's name to +something different from `img', you need to set the same name in all +images' directories along the CentOS Artwork Repository, and update +scripts to recognize the new name you set. This is something you +problably don't need to do, but if you still want to, please share +your reasons in +\href{mailto:centos-devel@centos.org}{centos-devel@centos.org} before +commit your changes. Changing the image directory's name is a big +chanage that needs to be discussed in the community. + +\subsection{Text Files} +\hypertarget{sec:Concepts:Frameworks:Files:Text}{} + +Text files are used to implement the CentOS visual style on all CentOS +visual manifestations where text files are involved (i.e. eula files +and release notes used by Anaconda, etc.). Text files are inside +identity frameworks. diff --git a/Manuals/Repository/filesystem-latex/Concepts/Frameworks/introduction.tex b/Manuals/Repository/filesystem-latex/Concepts/Frameworks/introduction.tex new file mode 100755 index 0000000..82c884d --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/Frameworks/introduction.tex @@ -0,0 +1,26 @@ +% Part : Concepts +% Chapter: Frameworks +% ------------------------------------------------------------ +% $Id: introduction.tex 6023 2010-06-27 10:09:48Z al $ +% ------------------------------------------------------------ + +Inside CentOS Artwork Repository, CentOS visual identity has been +organized in ``frameworks'', which have been divided in two major +groups: ``translations'', and ``identity''. These two groups of +frameworks are very similar in organization, they both have ``design +templates'' ---to define how things look like---, ``rendering script'' +---to automate the way things are produced---, and ``translated +files'' ---to store the final result of things being produced---. But +their files differ in content and type. + +The identity frameworks are focused on image conception (i.e. image +designing, image rendering, etc.). The translation frameworks are +focused on translation files conception (i.e. translation path +definition, file name definitions, translation markers definition, +etc.). + +Generally, one identity framework has one translation framework +associeted to it. When you render images inside identity frameworks, +the related translation framework is used as translation source and +file name definition. + diff --git a/Manuals/Repository/filesystem-latex/Concepts/Frameworks/rendering.tex b/Manuals/Repository/filesystem-latex/Concepts/Frameworks/rendering.tex new file mode 100644 index 0000000..c7baa89 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/Frameworks/rendering.tex @@ -0,0 +1,45 @@ +% Part : Concepts +% Chapter: Frameworks +% ------------------------------------------------------------ +% $Id: rendering.tex 6023 2010-06-27 10:09:48Z al $ +% ------------------------------------------------------------ + +\section{Rendering} +\hypertarget{sec:Concepts:Frameworks:Rendering}{} + +Rendering is the process by which you produce translated content based +on design templates and translation files. Inside CentOS Artwork +Repository you can render images and texts. + +\subsection{Image Rendering} +\hypertarget{sec:Concepts:Frameworks:Rendering:Image}{} + +Image files are rendered using the \texttt{render.sh} identity script. +The \texttt{render.sh} identity script is available in the framework +containing the image files you want to produce. To execute the +\texttt{render.sh} identity script, you need to be inside framework's +directory and use the following syntax: + +\begin{quote} +\texttt{./render.sh 'REGEX'} +\end{quote} + +The REGEX argument is optional. It is used to reduce the amount of +files you want to render. It is a posix-egrep regular expression +pattern, applied against the translation path. + +\subsection{Text Rendering} + +Text files are rendered using the \texttt{render.sh} identity script. +The \texttt{render.sh} identity script is available in the framework +containing the text files you want to produce. To execute the +\texttt{render.sh} identity script, you need to be inside framework's +directory and use the following syntax: + +\begin{quote} +\texttt{./render.sh 'REGEX'} +\end{quote} + +The REGEX argument is optional. It is used to reduce the amount of +files you want to render. It is a posix-egrep regular expression +pattern, applied against the translation path. diff --git a/Manuals/Repository/filesystem-latex/Concepts/Frameworks/templates.tex b/Manuals/Repository/filesystem-latex/Concepts/Frameworks/templates.tex new file mode 100644 index 0000000..13a7ca4 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/Frameworks/templates.tex @@ -0,0 +1,113 @@ +% Part : Concepts +% Chapter: Frameworks +% ------------------------------------------------------------ +% $Id: templates.tex 6207 2010-08-05 13:11:13Z al $ +% ------------------------------------------------------------ + +\section{Design Templates} +\hypertarget{sec:Concepts:Frameworks:Templates}{} +\label{sec:Concepts:Frameworks:Templates} + +Design templates are plain text files. Design templates may or may not +contain translation markers inside. Design templates are used to +define the CentOS visual style (the look and feel) of CentOS corporate +identity in all its manifestations. Design templates are the +documents you need to create or edit in order to implement or maintain +the monolithic CentOS corporate visual structure. Design templates +are normative documents that need to be conceived carefully. + +Design templates may be based on specific markups (i.e. XHTML, SVG, +CSS, etc.). If that is the case, translation markers may be combined +inside the specific markup design template to create a translatable +markup-specific design template. In contrast, if design templates do +not have specific markup inside, they are considered the simpliest +design templates because they only have translation markers inside. + +Design templates can be read, edited, and studied using your favorite +text editor. + +Design templates are specific to frameworks using design patterns to +define the visual style of content produced inside them. This is the +case of frameworks inside ``trunk/Identity/'', where design templates +are used to define images' visual style; and ``trunk/Translations/'', +where design tempates are used to define translations' common files. + +Inside frameworks, design templates are stored in a directory named +`tpl'. This name is a convenction that scripts use to find framework's +design tempate files. If you want to change the design template +directory's name to something different from `tpl', you need to set +the same name in all design templates' directories along the CentOS +Artwork Repository, and update scripts to recognize the new name you +set. This is something you problably don't need to do, but if you +still want to, please share your reasons in +\href{mailto:centos-devel@centos.org}{centos-devel@centos.org} before +commit your changes. Changing the design template directory's name is +a big chanage that needs to be discussed in the community. + +\subsection{Simpliest Design Templates} + +The simpliest design templates are inside identity frameworks. The +simpliest design tempaltes are plain text files with translation +markers only. These kind of design templates are used to define +information like ``eula files'' (i.e trunk/Identity/Release/Tpl/eula) +used by Anaconda and similar files. The simpliest design template +files do not use extension. + +\subsection{Translation Design Templates} + +The translation design templates are inside translation frameworks. +The translation design templats are plain text documents whithout any +kind of markup. Instead, they contain sed's replacements commands. +As convenction, translation file names end with the extension `.sed'. +Translation files are created and edited using your favorite text +editor. + +\subsection{SVG Design Templates} + +The scalar vector graphics (SVG) design templates are inside identity +frameworks. The SVG design templates are plain text files with +markup, based on SVG standard. The SVG standard is described at +\href{http://www.w3.org/2000/svg}{http://www.w3.org/2000/svg}. + +Even SVG design templates can be read and edited with your favorite +text editor, it is better to use a SVG editor like +\href{http://www.inkscape.org/}{Inkscape} (see +http://www.inkscape.org/) to create and edit them. The SVG design +template files are used to define the visual style of images +controlling the visual style of CentOS distribution, CentOS web sites, +CentOS promotion, etc. + +Inside SVG design templates, each object has an ``Id'' property. By +default the object's Id is a combination of letters and numbers +granting its uniqueness inside the entire document. + +Inside CentOS Artwork Repository, SVG design templates are rendered +automatically using the \texttt{render.sh} identity script. The +\texttt{render.sh} identity script looks for the object's Id property +containing the CENTOSARTWORK uppercase word and exports its area as +bitmap, automatically. + +If you are designing SVG templates for CentOS Artwork Repository, and +you are using the \texttt{render.sh} identity script to render them, +you need to set the CENTOSARTWORK uppercase word as object's Id on the +design object you want to export as bitmap during the rendering +process. The CENTOSARTWORK uppercase word is a convenction used by +scripts to find the export area on your SVG design templates. + +In CentOS Artwork Repository, SVG design templates are released under +the \href{http://creativecommons.org/licenses/by-sa/3.0/}{Creative +Common Share-Alike License 3.0}.\footnote{See +http://creativecommons.org/licenses/by-sa/3.0/} In Inkscape, you say +so in the ``Document Metadata'' panel, available in the ``File'' menu. + +\subsection{XHTML Design Templates} + +The XHTML design templates are inside identity frameworks. They are +plain text with markup, based on the +\href{http://www.w3.org/TR/xhtml1}{XHTML standard} described at +\href{http://www.w3.org/TR/xhtml1}{http://www.w3.org/TR/xhtml1}. These +files are created and edited using your favorite text editor. XHTML +design templates are used to define the visual style of files like the +``Release Notes'' (trunk/Identity/Release/Tpl/release-notes.html) used +by Anaconda. + diff --git a/Manuals/Repository/filesystem-latex/Concepts/Identity/brands.tex b/Manuals/Repository/filesystem-latex/Concepts/Identity/brands.tex new file mode 100644 index 0000000..67a8543 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/Identity/brands.tex @@ -0,0 +1,249 @@ +% Part : Concepts +% Chapter: Corporate Identity +% ------------------------------------------------------------ +% $Id: brands.tex 6207 2010-08-05 13:11:13Z al $ +% ------------------------------------------------------------ + +\section{The CentOS Brand} +\hypertarget{sec:Concepts:Identity:Brands}{} +\label{sec:Concepts:Identity:Brands} + +\begin{description} +\item[framework:] trunk/Identity/Brands/ +\end{description} + +\noindent The CentOS brand is the name or trademark that conncects the +producer with their products. In this case, the producer is The CentOS +Project and the products are the CentOS distributions, the CentOS web +sites, the CentOS promotion, etc. + +The CentOS Project uses the CentOS brand inside its GNU/Linux +enterprise distributions, web sites, and promotions to connect them +all visually and this way committing the monolithic visual structure +where one unique name and one unique visual style is used in all +visual manifestations. + +% ------------------------------------------------------------ +\section{The CentOS Logotype} +\hypertarget{sec:Concepts:Identity:Brands:Logotype}{} +\label{sec:Concepts:Identity:Brands:Logotype} + +\begin{description} +\item[framework:] trunk/Identity/Brands/Type +\end{description} + +\noindent The CentOS Logotype is represented by the word ``CentOS'' +using \texttt{denmark.ttf} typography. See +\autoref{fig:Concepts:Identity:Brands:Logotype}. + +\begin{figure} +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Brands/Img/CentOS/Type/Build/a/801.pdf}} +\end{center} +\caption{The CentOS Logotype.% + \label{fig:Concepts:Identity:Brands:Logotype}} +\end{figure} + +% ------------------------------------------------------------ +\section{The CentOS Symbol} +\hypertarget{sec:Concepts:Identity:Brands:Symbol}{} +\label{sec:Concepts:Identity:Brands:Symbol} + +\begin{description} +\item[framework:] trunk/Identity/Brands/Symbol +\end{description} + +\noindent The CentOS Symbol is the main visual representation of The +CentOS Project, and probably the most importat visual component inside +CentOS corporate identity. See +\autoref{fig:Concepts:Identity:Brands:Symbol}. Due the CentOS symbol +is graphical element, without any kind of embedded typography, it +provides an efficient way of identification in a multi-language +environments. + +\begin{figure} +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Brands/Img/CentOS/Symbol/Build/5c-a/801.pdf}} +\end{center} +\caption{The CentOS Symbol.% + \label{fig:Concepts:Identity:Brands:Symbol}} +\end{figure} + +% ------------------------------------------------------------ +\section{The Concept Behind CentOS Symbol} +\hypertarget{sec:Concepts:Identity:Brands:SymbolConcept}{} +\label{sec:Concepts:Identity:Brands:SymbolConcept} + +At the moment of writting these lines, I haven't found any reference +about the author who worked out the CentOS symbol and the concept +behind its design. That information would be useful as motivation +source. The CentOS symbol is the visual representation of that the +CentOS community is working for, it would be very nice to have that +information available somewhere. Until then, all we can do is giving +interpretations about it. + +I will take the adventure of describing my personal interpretation +about the CentOS symbol design and the concept behind it. This +interpretation is not definite, nor a final concept. Certainly, this +interpretation may have nothing in common with the one used by the +author of CentOS symbol. The ideas written in this section may change +in the future in the sake of reaching a better CentOS symbol +interpretation for the CentOS community to stand on.\footnote{This is +probably an interesting topic to debate at +``\href{mailto:centos-devel@centos.org}{centos-devel@centos.org}'' +mailing list.} + +The first thing, in order to interpret the CentOS symbol, is to know +which is ``\hyperlink{sec:Concepts:CentOS:Mission}{The CentOS Project +Mission}'' (\autoref{sec:Concepts:CentOS:Mission}) and feel a deep +compromise with it. Later on, take a look to the CentOS symbol and +try to identify each component its design is based on. If you take a +careful look at \autoref{fig:Concepts:Identity:Brands:Symbol} you find +that the CentOS symbol is based on squares, arrows and different +colors. + +The square is a geometrical figure that has four parallel sides of +equal dimensions. The equal dimensions brings the idea of justice +among all parts involved. That is, each part is in harmony one +another. This kind of harmony could be verified at simple sight, or +you can take a rule and messure each side to see that they have the +same dimensions. As long as we can verify this harmony is true, it +starts to be a fact of reason that we can rely on. + +In a second state, the CentOS symbol is built of four identical +$90^{\circ}$ squares filled with unique colors. The squares provide +reason based pragmatic facts. The colors provide emotions. So, in this +design state we could say that different emotions are controlled by +the same pragmatic reasons. + +In a third state, the $90^{\circ}$ set of squares is duplicated to +create a new set of squares. In this new set of squares fill colors +were removed and the whole squares set was rotated $45^{\circ}$. At +this point eight arrows, pointing the outside, are immediatly visible. +Emotions are so strong that they found a way to expand themselves out +of $90^{\circ}$ pragmatic reasons. But reason evolves with changes +and takes new forms ---the $45^{\circ}$ squares set--- to let flow off +the emotions' nature, and thus, uses that enormous expansion force to +create an infinite loop of common benefits, still controlled by the +reason of pragmatic facts. + +At this point the CentOS symbol has been completed. + +% ------------------------------------------------------------ +\section{The CentOS Trademark} +\hypertarget{sec:Concepts:Identity:Brands:Trademark}{} +\label{sec:Concepts:Identity:Brands:Trademark} + +\begin{description} +\item[framework:] trunk/Identity/Brands/Type/Tpl/2c-tm.svg +\end{description} + +\noindent The CentOS Trademark is a distinctive sign or indicator used +by The CentOS Project (as legal entity) to identify that its product +(The CentOS Distribution) or services to consumers with which the +trademark appears originate from a unique source, and to distinguish +its products or services from those of other entities. + +\begin{figure} +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Brands/Img/CentOS/Type/Build/tm/801.pdf}} +\end{center} +\caption{The CentOS Trademark.% + \label{fig:Concepts:Identity:Brands:Trademark}} +\end{figure} + +A trademark is designated by the following symbols: + +\begin{itemize} + +\item $^{\textup{\textsc{tm}}}$ (for an unregistered trademark, that +is, a mark used to promote or brand goods); + +\item $^{\textup{\textsc{sm}}}$ (for an unregistered service mark, +that is, a mark used to promote or brand services); and + +\item \textregistered\ (for a registered trademark). + +\end{itemize} + +% ------------------------------------------------------------ +\section{The CentOS Release Trademark} +\hypertarget{sec:Concepts:Identity:Brands:Release}{} +\label{sec:Concepts:Identity:Brands:Release} + +\begin{description} +\item[framework:] trunk/Identity/Brands/Type/Tpl/2c-tmr.svg +\end{description} + +\noindent The CentOS Release Trademark combines the CentOS trademark +and one decimal number. Based on +``\hyperlink{sec:Concepts:CentOS:Release}{The CentOS Release Schema}'' +(\autoref{sec:Concepts:CentOS:Release}), the CentOS project uses the +CentOS release trademak to identify CentOS visual manifestations that +share common visual structures with internal differences (i.e., The +CentOS Distributions and their installation media). + +Construction of CentOS release trademark, for major releases 4 and 5, +are illustrated on \autoref{fig:Concepts:Identity:Brands:Release:4} +and \autoref{fig:Concepts:Identity:Brands:Release:5}, respectively. + +\begin{figure} +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Brands/Img/CentOS/Type/Build/tmr4/801.pdf}} +\end{center} +\caption{The CentOS trademark for major release number four.% + \label{fig:Concepts:Identity:Brands:Release:4}} +\end{figure} + +\begin{figure} +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Brands/Img/CentOS/Type/Build/tmr5/801.pdf}} +\end{center} +\caption{The CentOS trademark for major release number five.% + \label{fig:Concepts:Identity:Brands:Release:5}} +\end{figure} + +Another way is to copy the release trademark SVG artwork and paste it +on the SVG design template you want it to appear in. Done that, +replace the decimal number with the string \texttt{=MAJOR\_RELEASE=}, +exactly. + +When you render the artwork component, that where you pasted the +release trademark SVG artwork in, you are producing the same artwork +component design for as many major releases as you have specified in +the translation structure of that artwork component being rendered. +Note that, in order for this translation mechanism to work correctly, +the translation structure should be prepared to support the major +release schema first, as described in +``\hyperlink{cha:Concepts:Translations}{Translation}'' +(\autoref{cha:Concepts:Translations}) and +``\hyperlink{sec:Concepts:CentOS:Release}{The CentOS Release Schema}'' +(\autoref{sec:Concepts:CentOS:Release}). + +% ------------------------------------------------------------ +\section{The CentOS Logo} +\hypertarget{sec:Concepts:Identity:Brands:Logos}{} +\label{sec:Concepts:Identity:Brands:Logos} + +\begin{description} +\item[framework:] trunk/Identity/Brands/Logos +\end{description} + +\noindent The CentOS Logo is a graphical element (ideogram, symbol, +emblem, icon, sign) that, together with its logotype (a uniquely set +and arranged typeface) form The CentOS Trademark or commercial brand. +See \autoref{fig:Concepts:Identity:Brands:Logos:Horizontal}. + +\begin{figure} +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Brands/Img/CentOS/Logo/Horizontal/Build/5c-tm/801.pdf}} +\end{center} +\caption{The CentOS Logo (horizontal) with trademark (TM) included.% + \label{fig:Concepts:Identity:Brands:Logos:Horizontal}} +\end{figure} diff --git a/Manuals/Repository/filesystem-latex/Concepts/Identity/icons.tex b/Manuals/Repository/filesystem-latex/Concepts/Identity/icons.tex new file mode 100644 index 0000000..b87e77e --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/Identity/icons.tex @@ -0,0 +1,14 @@ +% Part : Concepts +% Chapter: Corporate Identity +% ------------------------------------------------------------ +% $Id: icons.tex 6023 2010-06-27 10:09:48Z al $ +% ------------------------------------------------------------ + +\section{Icons} +\hypertarget{sec:Concepts:Identity:Icons}{} +\label{sec:Concepts:Identity:Icons} + +\begin{description} +\item[framework:] trunk/Identity/Icons/ +\end{description} + diff --git a/Manuals/Repository/filesystem-latex/Concepts/Identity/introduction.tex b/Manuals/Repository/filesystem-latex/Concepts/Identity/introduction.tex new file mode 100644 index 0000000..111f6f4 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/Identity/introduction.tex @@ -0,0 +1,24 @@ +% Part : Concepts +% Chapter: The CentOS Visual Identity +% ------------------------------------------------------------ +% $Id: introduction.tex 6019 2010-06-26 06:42:08Z al $ +% ------------------------------------------------------------ + +\begin{description} +\item[framework:] trunk/Identity/ +\end{description} + +\noindent This chapter describes the CentOS Project corporate +identity. The CentOS Project corporate identity is the ``persona'' of +the organization known as The CentOS Project. The CentOS Project +corporate identity plays a significant role in the way the CentOS +Project, as organization, presents itself to both internal and +external stakeholders. In general terms, the CentOS Project corporate +visual identity expresses the values and ambitions of the CentOS +Project organization, its business, and its characteristics. + +The CentOS Project corporate identity provides visibility, +recognizability, reputation, structure and identification to the +CentOS Project organization by means of corporate design, corporate +communication, and corporate behaviour. + diff --git a/Manuals/Repository/filesystem-latex/Concepts/Identity/models.tex b/Manuals/Repository/filesystem-latex/Concepts/Identity/models.tex new file mode 100644 index 0000000..a7f7c53 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/Identity/models.tex @@ -0,0 +1,24 @@ +% Part : Concepts +% Chapter: Corporate Identity +% ------------------------------------------------------------ +% $Id: models.tex 6023 2010-06-27 10:09:48Z al $ +% ------------------------------------------------------------ + +\section{Models} +\hypertarget{sec:Concepts:Identity:Models}{} +\label{sec:Concepts:Identity:Models} + +\begin{description} +\item[framework:] trunk/Identity/Models/ +\end{description} + +\noindent Here is where you find design models. Design models are +representative images used to illustrate key components inside a +specific design. Design models are frequently used to make +documentation clearer. + +When designing models, try to make them language independent so they +can be reused in differet language documents. For example, you can use +letters or numbers to identify areas in the model and later use the +figure's caption to describe the meaning of those letters and numbers, +respectively. diff --git a/Manuals/Repository/filesystem-latex/Concepts/Identity/release.tex b/Manuals/Repository/filesystem-latex/Concepts/Identity/release.tex new file mode 100644 index 0000000..8aa299c --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/Identity/release.tex @@ -0,0 +1,19 @@ +% Part : Concepts +% Chapter: Corporate Identity +% ------------------------------------------------------------ +% $Id: release.tex 6023 2010-06-27 10:09:48Z al $ +% ------------------------------------------------------------ + +\section{Release} +\hypertarget{sec:Concepts:Identity:Release}{} +\label{sec:Concepts:Identity:Release} + +\begin{description} +\item[framework:] trunk/Identity/Release/ +\end{description} + +\noindent Here is where CentOS Distribution release-specific files are +produced. This framework contains textual templates that produce +textual files, like ``release notes'' and ``eula files'' used by +Anaconda. + diff --git a/Manuals/Repository/filesystem-latex/Concepts/Identity/structure.tex b/Manuals/Repository/filesystem-latex/Concepts/Identity/structure.tex new file mode 100644 index 0000000..2542eba --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/Identity/structure.tex @@ -0,0 +1,87 @@ +% ------------------------------------------------------------ +% $Id: structure.tex 6024 2010-06-28 04:28:27Z al $ +% ------------------------------------------------------------ + \section{Visual Structure} +\hypertarget{sec:Concepts:Identity:Structure}{} + \label{sec:Concepts:Identity:Structure} + +The CentOS Project settles down its corporate visual identity on a +``monolithic corporate visual identity structure''. In this structure +The CentOS Project uses one unique name +(``\hyperlink{sec:Concepts:Identity:Brands}{The CentOS Brand}'') and +one unique visual style +(``\hyperlink{sec:Concepts:Identity:Themes:Default}{The CentOS Default +Theme}'') in all its manifestations. + +The CentOS Project organizes its visual manifestation in four top +level structures: The CentOS Distribution, The CentOS Web, The CentOS +Promotion, and The CentOS Behaiviour. The CentOS Distribution , The +CentOS Web, and The CentOS Promotion use one unique name and one +unique visual style in all its manifestations. + +% ------------------------------------------------------------ + \subsection{Distribution Visual Structure} +\hypertarget{sec:Concepts:Identity:Structure:Distribution}{} + \label{sec:Concepts:Identity:Structure:Distribution} + +It applies to all major releases of CentOS distribution. + +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, 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 components are made +of software improved constantly. + +The software constant improvement is reflected on a numbered release +schema, described in ``\hyperlink{sec:Concepts:CentOS:Release}{The +CentOS Release Schema}'' (\autoref{sec:Concepts:CentOS:Release}). The CentOS release schema is a tool to +provide exact information, specific to one release at any given time. + +People can use this release schema to know the software details that +they are using on their computers, report bugs, fixes, suggestions, or +simply any kind of usefull information; in the same exact basis. + +Remarking the CentOS release schema inside each major release of +CentOS Distribution ---or similar visual manifestation--- takes high +attention in the sake of The CentOS Project corporate visual identity. +For archiving that purpose, graphic designers use ``The CentOS Release +Brand'' in all artwork components controlling the visual style of +CentOS Distribution ---or similar--- visual manifestation. + +Artwork components controlling the visual style of CentOS Distribution +visual manifestation are described in +``\hyperlink{par:Distribution}{Distribution}'' +(\autoref{par:Distribution}). + +% ------------------------------------------------------------ + \subsection{Web Visual Structure} +\hypertarget{sec:Concepts:Identity:Structure:Web}{} + \label{sec:Concepts:Identity:Structure:Web} + +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. + +% ------------------------------------------------------------ + \subsection{Promotion Visual Structure} +\hypertarget{sec:Concepts:Identity:Structure:Promotion}{} + \label{sec:Concepts:Identity:Structure:Promotion} + +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. + +% ------------------------------------------------------------ + \subsection{Behaviour Visual Structure} +\hypertarget{sec:Concepts:Identity:Structure:Behaviour}{} + \label{sec:Concepts:Identity:Structure:Behaviour} + +It applies to CentOS community's social behavior. To what we do and +how we do it. + diff --git a/Manuals/Repository/filesystem-latex/Concepts/Identity/themes.tex b/Manuals/Repository/filesystem-latex/Concepts/Identity/themes.tex new file mode 100644 index 0000000..f7a34e9 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/Identity/themes.tex @@ -0,0 +1,544 @@ +% Part : Concepts +% Chapter: Corporate Identity +% ------------------------------------------------------------ +% $Id: themes.tex 6207 2010-08-05 13:11:13Z al $ +% ------------------------------------------------------------ +\section{Themes} +\hypertarget{sec:Concepts:Identity:Themes}{} +\label{sec:Concepts:Identity:Themes} + +\begin{description} +\item[framework:] trunk/Identity/Themes/ +\end{description} + +\noindent Here is where themes are produced. In the above framework +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. + +% ------------------------------------------------------------ +\section{CentOS Default Theme} +\hypertarget{sec:Concepts:Identity:Themes:Default}{} +\label{sec:Concepts:Identity:Themes:Default} + +The CentOS default theme is used in all visual manifestations of +CentOS Project's corporate visual identity (e.g., distributions, web +sites, promotion, etc.). + +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 +(\textbf{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 ``\hyperlink{sec:Concepts:Identity:Themes:Motifs}{Theme +Motifs}'' (\autoref{sec:Concepts:Identity:Themes:Motifs}). + +% ------------------------------------------------------------ +\section{CentOS Alternative Themes} +\hypertarget{sec:Concepts:Identity:Themes:Alternative}{} +\label{sec:Concepts:Identity:Themes:Alternative} + +CentOS alternative themes 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. + +% ------------------------------------------------------------ +\section{Theme Transition} +\hypertarget{sec:Concepts:Identity:Themes:Transition}{} +\label{sec:Concepts:Identity:Themes:Transition} + +Theme transition is the action of moving a theme from alternative to +default. This transition begins when an alternative theme gets +popular enough inside CentOS Comminity, and both CentOS Administrators +and CentOS Comunity Members want to extend it to all CentOS Visual +Manifestations. + +Once the popular alternative theme has been extended through all +CentOS visual manifestations, the alternative theme implementation +phase starts. The alternative theme implementation phase is where +default theme art work is replaced with alternative theme ones. After +the implementation phase, the previous default theme is tagged as +alternative and the implemented alternative as default. + +Theme Transition has a huge impact in CentOS Corporate Visual +Identity, it should be done only if absolutly necessary. Generally, it +is better to improve the current default theme, based on its concept, +than create a completly new one. + +% ------------------------------------------------------------ +\section{Theme Models} +\hypertarget{sec:Concepts:Identity:Themes:Models}{} +\label{sec:Concepts:Identity:Themes:Models} + +\begin{description} +\item[framework:] trunk/Identity/Themes/Models/ +\end{description} + +\noindent Here is where theme models are stored. 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. + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +trunk/Identity/Themes/ +|-- Models +| |-- Default <-- theme's model name. +| | |-- Distro +| | | |-- Anaconda +| | | | |-- Header +| | | | |-- Progress +| | | | |-- Prompt +| | | | `-- Splash +| | | `-- BootUp +| | | |-- Firstboot +| | | |-- GDM +| | | |-- GRUB +| | | |-- GSplash +| | | |-- KDM +| | | |-- KSplash +| | | |-- RHGB +| | | `-- Plymouth +| | |-- Promo +| | |-- Web +| |-- Alternative <-- theme's model name. +| | |-- Distro +| | | `-- BootUp +| | | |-- Firstboot +| | | |-- GDM +| | | |-- GRUB +| | | |-- GSplash +| | | |-- KDM +| | | |-- KSplash +| | | |-- RHGB +| | | `-- Plymouth +| |-- ... more theme models. +\end{verbatim} +\hrulefill +\caption{Theme models structure.% + \label{fig:Concepts:Identity:Themes:Models}} +\end{figure} + +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. + +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 following +ready-to-use theme models: + +\begin{itemize} + +\item \textbf{Default:} Stores the theme model used to produce +``\hyperlink{sec:Concepts:Identity:Themes:Default}{CentOS +Default Theme}'' +(\autoref{sec:Concepts:Identity:Themes:Default}). + +\item \textbf{Alternative:} Stores the theme model used to produce +``\hyperlink{sec:Concepts:Identity:Themes:Alternative}{CentOS +Alternative Themes}'' +(\autoref{sec:Concepts:Identity:Themes:Alternative}). + +\end{itemize} + +\begin{figure} +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Models/Img/en/Corporate/common-design-model-fig1.pdf}} +\end{center} +\caption{Anaconda theme model producing three different visual +styles.} +\end{figure} + +\begin{figure} +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Models/Img/en/Corporate/common-design-model-fig2.pdf}} +\end{center} +\caption{Firstboot theme model producing three different visual +styles.} +\end{figure} + +% ------------------------------------------------------------ +\section{Theme Motifs} +\hypertarget{sec:Concepts:Identity:Themes:Motifs}{} +\label{sec:Concepts:Identity:Themes:Motifs} + +\begin{description} +\item[framework:] trunk/Identity/Themes/Motifs/ +\end{description} + +\noindent Here is where the themes' artistic motifs are produced. The +artistic motif is a graphic design used as common pattern to connect +all CentOS Project's visual manifestations inside the same theme. + +Inside the framework location above, artistic motifs are organized by +names inside the standard file structure illustrated in +\autoref{fig:Concepts:Identity:Themes:Motifs:Default} and +\autoref{fig:Concepts:Identity:Themes:Motifs:Alternative}. + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +trunk/Identity/Themes/ +|-- Motifs +| |-- Modern <-- theme name. +| | |-- Backgrounds +| | |-- Distro +| | | |-- Anaconda +| | | | |-- Header +| | | | |-- Progress +| | | | |-- Prompt +| | | | `-- Splash +| | | |-- BootUp +| | | | |-- Firstboot +| | | | |-- GDM +| | | | |-- GRUB +| | | | |-- GSplash +| | | | |-- KDM +| | | | |-- KSplash +| | | | |-- RHGB +| | | | `-- Plymouth +| | | `-- Desktop +| | |-- Info +| | |-- Palettes +| | |-- Promo +| | |-- Screenshots +| | `-- Web +| |-- ... more theme names. +\end{verbatim} +\hrulefill +\caption{Theme motifs default structure.% + \label{fig:Concepts:Identity:Themes:Motifs:Default}} +\end{figure} + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +trunk/Identity/Themes/ +|-- Motifs +| |-- TreeFlower <-- theme name. +| | |-- Backgrounds +| | |-- Distro +| | | |-- BootUp +| | | | |-- Firstboot +| | | | |-- GDM +| | | | |-- GRUB +| | | | |-- GSplash +| | | | |-- KDM +| | | | |-- KSplash +| | | | |-- RHGB +| | | | `-- Plymouth +| | | `-- Desktop +| | |-- Info +| | |-- Palettes +| | |-- Screenshots +| |-- ... more theme names. +\end{verbatim} +\hrulefill +\caption{Theme motifs alternative structure.% + \label{fig:Concepts:Identity:Themes:Motifs:Alternative}} +\end{figure} + +When designing artistic motifs for CentOS, consider the following +recommendations: + +\begin{itemize} + +\item Give a unique (case-sensitive) name to your Motif. This name is +used as value wherever theme variable (\$THEME) or translation marker +(\texttt{=THEME=}) is. Optionally, you can add a description about +inspiration and concepts behind your work. + +\item Use the location trunk/Identity/Themes/Motifs/\$THEME/ to store +your work. If it doesn't exist create it. Note that this require you +to have previous commit access in CentOS Artwork Repository. + +\item The CentOS Project is using the blue color (\texttt{\#204c8d}) +as base for its corporate visual identity. Use the CentOS Project's +base corporate color as much as possible in your artistic motif +designs. + +\item Try to make your design fit one of the +``\hyperlink{sec:Concepts:Identity:Themes:Models}{Theme Models}'' +(\autoref{sec:Concepts:Identity:Themes:Models}). + +\item Feel free to make your art enterprise-level and beautiful. + +\item Add the following information on your art work (both in a visible +design area, and inside Inkscape's document metadata section wherever +it be possible): + +\begin{itemize} + +\item The name (or logo) of your artistic motif. + +\item The copyright sentence: \texttt{Copyright (C) YEAR YOURNAME} + +\item The license under which the work is released. All CentOS Art +works are released under +\href{http://creativecommons.org/licenses/by-sa/3.0/}{Creative Common +Share-Alike License 3.0} +(\href{http://creativecommons.org/licenses/by-sa/3.0/}{http://creativecommons.org/licenses/by-sa/3.0/}). + +\end{itemize} + +\end{itemize} +% ------------------------------------------------------------ +\section{Theme Palettes} +\hypertarget{sec:Concepts:Identity:Themes:Palettes}{} +\label{sec:Concepts:Identity:Themes:Palettes} + +\begin{description} +\item[framework:] turnk/Identity/Themes/Motifs/\$THEME/Palettes/\\ +\end{description} + +\noindent 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. +\autoref{tab:Concepts:Identity:Themes:Palettes:Files}. + +% ------------------------------------------------------------ +\section{Theme Palettes Creation} +\hypertarget{sec:Concepts:Identity:Themes:Palettes:Creation}{} +\label{sec:Concepts:Identity:Themes:Palettes:Creation} + +Theme palettes are based on art works' specific color information you +are creating palettes for. As we write this section, there are two art +works that require color limitations. They are Grub and Syslinux art +works. + +This section describes a generic procedure you can use to create theme +palettes for art works which need to be produced with color +limitations. + +\begin{enumerate} + +\item As first step, you need to produce a PNG file with the final +design of that art work you are creating palettes for. You can do +this by using the \texttt{render.sh} script available in the art +work's identity framework. + +\item Secondly, you need to generate the limited color information for +that PNG file the three different file formats (See +\autoref{tab:Concepts:Identity:Themes:Palettes:Files}). You can do +this by using the Gimp as described below: + +\begin{table}[!hbp] +\center +\begin{tabular}{ll} +\hline +\textbf{File} & \textbf{Description}\\ +\hline +\texttt{.gpl} & Gimp palette files.\\ +\texttt{.ppm} & Portable Pixel Map palette files.\\ +\texttt{.hex} & Hexadecimal auxiliar palette files.\\ +\hline +\end{tabular} +\caption{Palette file types.% + \label{tab:Concepts:Identity:Themes:Palettes:Files}} +\end{table} + +\end{enumerate} + +To create the \texttt{.gpl} file: + +\begin{enumerate} + +\item Open the Gimp (\textit{Applications / Graphics / The Gimp}). + +\item Open the PNG format file you want to generate the limited color +information for (\textit{File / Open ...}). + +\item Index the image (\textit{Image / Mode / Indexed...}). This will +open the window ``Indexed Color Conversion''. Use this window to +``Generate optimum palette'' by setting the maximum number of colors +you want to have in the final indexed image. In this window, by the +default, Gimp has set 255 as the maximum number of colors, you should +change this value to fit the art work color limitation requirements +(i.e. 14 colors for Grub's splash, and 16 colors for Syslinux splash, +etc.). Another option you can play with is ``Color dithering'' at the +window's bottom, particularly the ``Floyd-Steinberg (reduced color +dithering)'' option which seems to archive the best results. + +\item At this point you have reduced color information and indexed the +image. This let you save the color information as a Gimp palette file +(.gpl) for further using. + +To export the color information as Gimp palette you need to open the +palette window (\textit{Ctrl+P}) and go to the action ``Import +Palette...'' inside ``Palettes Menu''. This will open the window +``Import Palette''. In this window you need to specify the source from +where you will retrive color information and the name of the palette +file. Use ``Image'' as source to create your palette and the +appropriate name (e.g., \texttt{centos-\$themename-grub}).\footnote{in +\texttt{centos-\$themename-grub} file name, the \texttt{\$themename} +part is the theme's name you are working on (e.g., Modern, TreeFlower, +etc.) for Grub's palette, \texttt{centos-\$themename-syslinux} for +Syslinux palette, etc.} + +\end{enumerate} + +To create the \texttt{.ppm} file: + +\begin{enumerate} + +\item Use the Gimp to create a new image (\textit{Ctrl+N}) of 16 x 1 +pixels of dimension. That is 16 pixels width and 1 pixel height. + +\item That is a rather small image so you problably want to zoom it in +to better see what you are doing. In a 1024x768 screen resolution, +zoom the 16 x 1 pixel image to 4500\% makes things clear enough. If +you are using a different screen resolution you probably need to zoom +in to a different value. + +\item Now it's time to fill up the empty image with the color +information we created previously. You do this using the pen tool +(\textit{N}) with a 1x1 brush (\textit{Shit+Ctrl+B}). At this point it +is a good time to open the ``Palette Editor'' window and use the Gimp +palette file with the color information we created (\textit{Ctrl+P / +doble click on the palette file}). + +\begin{quote} + +\textbf{Caution!:} If you are creating \texttt{.ppm} palettes for +Anaconda prompt (syslinux), the order used to set the color +information is relevant. Relevant values in the image are positions: 0 +and 7. Position 0 is used as background color, which is black +(\texttt{\#000000}) generally and position 7 is used as forground +color, which is white (\texttt{\#ffffff}) generally. This, in order to +grant the highest contrast. See +\autoref{fig:Concepts:Identity:Themes:Palettes:Syslinux}. + +\end{quote} + +\end{enumerate} + +To create the (\texttt{.hex}) file: + +\begin{enumerate} + +\item Create a plain text file and put the hexadecimal color +information and its index position defined in \texttt{.ppm} palette +inside the file, one definition by line. The format used to create +the \texttt{.hex} file is \texttt{\#rrbbgg=i \dots}. Where +\texttt{\#rrggbb=i} indicates that the color \texttt{\#rrggbb} (hex) +should be assigned index i (decimal). + +\begin{quote} +\textbf{Caution!:} In order to produce Anaconda prompt (syslinux) +images correctly, both \texttt{.hex} and \texttt{.ppm} color and index +information should match. +\end{quote} + +\end{enumerate} + +\begin{figure}[!hbp] +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Models/Img/en/Distro/Anaconda/Prompt/syslinux-palette.pdf}} +\end{center} +\caption{Palette's background (A) and forground (B) color position.% + \label{fig:Concepts:Identity:Themes:Palettes:Syslinux}} +\end{figure} + +% ------------------------------------------------------------ +\section{Theme File Structure} +\hypertarget{sec:Concepts:Identity:Themes:Files}{} +\label{sec:Concepts:Identity:Themes:Files} + +Inside CentOS Artwork Repository, each theme has a name and a +directory for it. Inside each theme directory, the CentOS Project +visual style is organized in the directories: Distro, Info, Palettes, +Promo, Screenshots, and Web. + +% ------------------------------------------------------------ +\subsection{The \texttt{Distro} Directory} +\hypertarget{sec:Concepts:Identity:Themes:Files:Distro}{} +\label{sec:Concepts:Identity:Themes:Files:Distro} + +Here is where image files controlling CentOS Distribution visual style +are produced. + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +turnk/Identity/Themes/Motifs/$THEME/Distro/ +|-- Anaconda +| |-- Header +| |-- Progress +| |-- Prompt +| `-- Splash +|-- BootUp +| |-- Firstboot +| |-- GDM +| |-- GRUB +| |-- GSplash +| |-- KDM +| |-- KSplash +| `-- RHGB +`-- Desktop +\end{verbatim} +\hrulefill +\caption{The CentOS distribution theme structure.} +\end{figure} + +% ------------------------------------------------------------ +\subsection{The \texttt{Palettes} Directory} +\hypertarget{sec:Concepts:Identity:Themes:Files:Palettes}{} +\label{sec:Concepts:Identity:Themes:Files:Palettes} + +Here is where theme's palettes are sotred. Palettes are used to +automate image rendering in cases where a limited amount of color need +to be specified. Before you could render color-limited art works (e.g. +Grub, and Syslinux), you need to create their color-limited palettes +first. See +``\hyperlink{sec:Concepts:Identity:Themes:Palettes:Creation}{Theme +Palette Creation}'' +(\autoref{sec:Concepts:Identity:Themes:Palettes:Creation}). + +% ------------------------------------------------------------ +\subsection{The \texttt{Promo} Directory} +\hypertarget{sec:Concepts:Identity:Themes:Files:Promo}{} +\label{sec:Concepts:Identity:Themes:Files:Promo} + +Here is where image files controlling CentOS promotion visual style +are produced. + +% ------------------------------------------------------------ +\subsection{The \texttt{Screenshots} Directory} +\hypertarget{sec:Concepts:Identity:Themes:Files:Screenshots}{} +\label{sec:Concepts:Identity:Themes:Files:Screenshots} + +Here is where theme's screenshots are stored. The purpose of this +directory is to collect theme's implementation graphical history +through time. Inside this directory you can have distribution +screenshots, web sites screenshtos, and promotion screenshots. If +theme has been implemented out of computers like would be the case of +events, stands, etc. those photos can be added here too, in the +promotion screenshot section. + +% ------------------------------------------------------------ +\subsection{The \texttt{Web} Directory} +\hypertarget{sec:Concepts:Identity:Themes:Files:Web}{} +\label{sec:Concepts:Identity:Themes:Files:Web} + +Here is where image files controlling CentOS Web sites visual style +are produced. diff --git a/Manuals/Repository/filesystem-latex/Concepts/Identity/widgets.tex b/Manuals/Repository/filesystem-latex/Concepts/Identity/widgets.tex new file mode 100644 index 0000000..5cd8db2 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/Identity/widgets.tex @@ -0,0 +1,13 @@ +% Part : Concepts +% Chapter: Corporate Identity +% ------------------------------------------------------------ +% $Id: widgets.tex 6023 2010-06-27 10:09:48Z al $ +% ------------------------------------------------------------ + +\section{Widgets} +\hypertarget{sec:Concepts:Identity:Widgets}{} +\label{sec:Concepts:Identity:Widgets} + +\begin{description} +\item[framework:] trunk/Identity/Widgets/ +\end{description} diff --git a/Manuals/Repository/filesystem-latex/Concepts/logo.tex b/Manuals/Repository/filesystem-latex/Concepts/logo.tex new file mode 100644 index 0000000..b9fa0a1 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/logo.tex @@ -0,0 +1,17 @@ +% Part : Concepts +% Chapter: The CentOS Logo +% ------------------------------------------------------------ +% $Id: logo.tex 6191 2010-08-02 02:36:14Z al $ +% ------------------------------------------------------------ + +\section{Horizontal} +\hypertarget{sec:Concepts:Logo:Horizontal}{} +\label{sec:Concepts:Logo:Horizontal} + +\section{Pyramidal} +\section{Circular} +\section{Construction} +\section{Usage} +\section{Colors} +\section{Reductions} +\section{Prohibitions} diff --git a/Manuals/Repository/filesystem-latex/Concepts/manuals.tex b/Manuals/Repository/filesystem-latex/Concepts/manuals.tex new file mode 100644 index 0000000..2d783d6 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/manuals.tex @@ -0,0 +1,288 @@ +% Part : Concepts +% Chapter: Manuals +% ------------------------------------------------------------ +% $Id: manuals.tex 6191 2010-08-02 02:36:14Z al $ +% ------------------------------------------------------------ + +\begin{description} +\item[framework:] trunk/Manuals/ +\end{description} + +\noindent This chapter describes the CentOS Artwork Repository User +Guide. The CentOS Artwork Repository User Guide is the book you are +reading right now. The main goals of this book is helping you to +understand how CentOS Artwork Repository works, and what you can do to +get the best of it. It is also an excuse for you to join us and help +improving it. + +\section{Structure} + +Inside CentOS Artwork Repository, documentation is conceived using +\LaTeX's book class. Instead of having the entire document in a single +file, information has been spread in separated files under Manuals +framework structure. The Manuals framework structure is illustrated in +\autoref{fig:Concepts:Manuals:Structure} and described in +``\hyperlink{sec:Concepts:Manuals:Files}{Relevant Files}'' (see +\autoref{sec:Concepts:Manuals:Files}) and +``\hyperlink{sec:Concepts:Manuals:Directories}{Relevant Directories}'' +(see \autoref{sec:Concepts:Manuals:Directories}). + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +trunk/Manuals/ +|-- Concepts +| |-- CentOS +| |-- Frameworks +| |-- Identity +| `-- ... +|-- Distribution +| |-- Anaconda +| | |-- Firstboot +| | |-- Header +| | |-- Progress +| | `-- ... +| |-- Backgrounds +| |-- BootUp +| | |-- GDM +| | |-- GRUB +| | `-- ... +| `-- Release +|-- Licenses +|-- Translations +|-- Workstation +|-- convenctions.tex +|-- repository.aux +|-- repository.lof +|-- repository.log +|-- repository.lot +|-- repository.out +|-- repository.pdf +|-- repository.tex +`-- repository.toc +\end{verbatim} +\hrulefill +\caption{Manuals framework structure.% + \label{fig:Concepts:Manuals:Structure}} +\end{figure} + +\section{Writing Style} + +When writing for CentOS Artwork Repository User Guide, keep in mind +the following quote taken from the online ``BBC News Styleguide'': +---The key to good writing is \textbf{simple thoughts simply +expressed}. Use short sentences and short words. Anything which is +confused, complicated, poorly written or capable of being +misunderstood risks losing the listener or viewer, and once you have +done that, you might just as well not have come to work---. + +If you need to express complicated ideas, try to split them out in +smaller and simpler ideas as much as possible. If you consider it +appropriate, try to use +``\hyperlink{sec:Concepts:Identity:Models}{Design Models}'' (see +\autoref{sec:Concepts:Identity:Models}) to illustrate your thoughts. + +\subsection{Cross References} + +When you create \LaTeX's cross references, you need to define targets +and links. Targets are the specific locations in the document that +links point to. In \LaTeX, these cross reference targets and links +can be defined in many ways, so we need to standardize the way we use +inside CentOS Artwork Repository User Guide to make it look uniform +and easy to read. + +Inside CentOS Artwork Repository User Guide, cross references look +like illustrated in +\autoref{fig:Concepts:Manuals:CrossRef:Presentation}. Cross reference +targets are defined as illustrated in +\autoref{fig:Concepts:Manuals:CrossRef:Targets}, and links to those +targets are defined as illustrated in +\autoref{fig:Concepts:Manuals:CrossRef:Links}. + +Note that we use both \texttt{hypertarget} and \texttt{label} commands +to define targets, and \texttt{hyperlink} and \texttt{autoref} to +define links. With \texttt{hyperlink} we create long text links +---usefull when reading in the coputer---, and with \texttt{autoref} +we create numbered links ---usefull when reading in a printed copy---. + +\begin{figure}[!hbp] +\hrulefill +\begin{flushleft} +\dots you can find more information in +``\hyperlink{sec:Concepts:Identity:Brands}{Logos}'' (see +\autoref{sec:Concepts:Identity:Brands}), specifically in +\hyperlink{sec:Concepts:Identity:Brands:Logos}{the horizontal version} (see +\autoref{sec:Concepts:Identity:Brands:Logos}). +\end{flushleft} +\hrulefill +\caption{Cross reference link presentation.% + \label{fig:Concepts:Manuals:CrossRef:Presentation}} +\end{figure} + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +\part{Concepts} +... +\chapter{The CentOS Logo} +\hypertarget{sec:Concepts:Logo}{} +\label{sec:Concepts:Logo} +... +\section{Horizontal} +\hypertarget{sec:Concepts:Identity:Brands}{} +\label{sec:Concepts:Identity:Brands} +... +\end{verbatim} +\hrulefill +\caption{\LaTeX's definition for cross reference targets.% + \label{fig:Concepts:Manuals:CrossRef:Targets}} +\end{figure} + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +\dots you can find more information in +``\hyperlink{sec:Concepts:Identity:Brands}{The CentOS Logo}'' +(see \autoref{sec:Concepts:Identity:Brands}), specifically in +\hyperlink{sec:Concepts:Identity:Brands:Logos}{the horizontal version} +(see \autoref{sec:Concepts:Identity:Brands:Logos}). +\end{verbatim} +\hrulefill +\caption{\LaTeX's definition for cross reference links.% + \label{fig:Concepts:Manuals:CrossRef:Links}} +\end{figure} + +\subsection{Figures} + +Inside CentOS Artwork Repository User Guide, illustrations (i.e. +images, framework structures, source code, commands, etc.) are shown +using \LaTeX's \texttt{figure} environment. An example of +\texttt{figure} environment definition is illustrated in +\autoref{fig:Concepts:Manuals:Figures}. More information about +\LaTeX's \texttt{figure} environment can be found in \LaTeX's info +manual. To read the \LaTeX's info manual, execute in your terminal the +command: \texttt{info latex}. + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +\begin{figure}[!hbp] +\hrulefill +... +\hrulefill +\caption{... .% + \label{fig:...}} +\end{figure} +\end{verbatim} +\hrulefill +\caption{\LaTeX's definition for \texttt{figure} environment.% + \label{fig:Concepts:Manuals:Figures}} +\end{figure} + +\subsection{Tables} + +Inside CentOS Artwork Repository User Guide, tabular information (i.e. +translation markers, etc.) is shown using \LaTeX's \texttt{table} +environment. An example of \texttt{table} environment definition is +illustrated in \autoref{fig:Concepts:Manuals:Tables}. More +information about \LaTeX's \texttt{table} environment can be found in +\LaTeX's info manual. To read the \LaTeX's info manual, execute in +your terminal the command: \texttt{info latex}. + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +\begin{table}[!hbp] +\centering +\begin{tabular}[pos]{cols} +\hline +... +\hline +\end{tabular} +\caption{... .% + \label{tab:...}} +\end{table} +\end{verbatim} +\hrulefill +\caption{\LaTeX's definition for \texttt{table} environment.% + \label{fig:Concepts:Manuals:Tables}} +\end{figure} + +\section{Relevant Files} +\hypertarget{sec:Concepts:Manuals:Files}{} +\label{sec:Concepts:Manuals:Files} + +\subsection{repository.tex} + +The \texttt{repository.tex} file is the main book's file. Here is +where you define specific book information like class, title, authors, +etc. Inside \texttt{repository.tex} you organize chapters and load +their sections. + +\subsection{introduction.tex} + +The \texttt{Introduction.tex} file introduces a specific artwork +component: what it does, where and when it appears in, etc. + +\subsection{framework.tex} + +The \texttt{rramework.tex} file describes how to interact with a +specific artwork component: where to find the artwork component inside +CentOS Artwork Repository, how to render their images, how to render +their translations, their specific translation markers, etc. + +\subsection{rebranding.tex} + +The \texttt{rebranding.tex} file describes how to rebrand a specific +artwork component: where to find the arwork component inside CentOS +Distribution, related packages you need to modify, etc. + +\section{Relevant Directories} +\hypertarget{sec:Concepts:Manuals:Directories}{} +\label{sec:Concepts:Manuals:Directories} + +\subsection{Concepts} + +The \texttt{Concepts} directory organizes chapters related to +``Concepts'' part. Files in this directory describe concepts used +inside CentOS Artwork Repository. + +\subsection{Workstation} + +The \texttt{Workstation} directory organizes chapters related to +``Preparing Your Workstation'' part. Files in this directory describe +actions (i.e. installation and configuration) you need to do before +using CentOS Artwork Repository. + +\subsection{Distribution} + +The \texttt{Distribution} directory organizes chapters releated to +``Distribution'' part. This part gets its attention into the different +artwork components of CentOS Distribution, using a subdirectory +structure to organize them and the files \texttt{introduction.tex}, +\texttt{framework.tex}, and \texttt{rebranding.tex} to describe them. + +\subsection{Licenses} + +The \texttt{Licenses} directory organizes licenses used in this book. + +\section{Revisions} +\hypertarget{sec:Concepts:Manuals:Revisions}{} +\label{sec:Concepts:Manuals:Revisions} + +Revisions are a way of organizing changes committed to CentOS Artwork +Repository User Guide. Revisions have the format ``Revision M.N'', +where M is the major revision number, and N is the update revision +number. Revision update number (N) may increase by one every month to +release that month's changes. Once the six month cycle is reached, +major revision number (M) is increased by one and update revision +number (N) is reset to 0. + +\section{Export to PDF} + +To produce the file \texttt{repository.pdf}, you need to get inside +the Manual's framework and execute the command: + +\begin{quote} +\texttt{pdflatex repository.tex} +\end{quote} diff --git a/Manuals/Repository/filesystem-latex/Concepts/motif.tex b/Manuals/Repository/filesystem-latex/Concepts/motif.tex new file mode 100644 index 0000000..0ddcd27 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/motif.tex @@ -0,0 +1,9 @@ +% Part : Concepts +% Chapter: The CentOS Artistic Motif +% ------------------------------------------------------------ +% $Id: motif.tex 6191 2010-08-02 02:36:14Z al $ +% ------------------------------------------------------------ + +\section{CentOS Default Artistic Motif} +\section{CentOS Alternative Artistic Motif} +\section{CentOS Artistic Motif License} diff --git a/Manuals/Repository/filesystem-latex/Concepts/rebranding.tex b/Manuals/Repository/filesystem-latex/Concepts/rebranding.tex new file mode 100644 index 0000000..780477b --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/rebranding.tex @@ -0,0 +1,28 @@ +% Part : Concepts +% Chapter: Rebranding +% ------------------------------------------------------------ +% $Id: rebranding.tex 6191 2010-08-02 02:36:14Z al $ +% ------------------------------------------------------------ + +To comply with upstream redistribution policy, the CentOS Project +removes all upstream brands and artworks from CentOS Distribution. The +CentOS Project has its own brand and its own artwork. The CentOS Brand +and CentOS Artwork are what the CentOS Project uses in CentOS +Distribution. + +The action of removing upstream brands and artworks and add CentOS +brands and artworks is what we call rebranding. + +CentOS Brands and artworks are organized inside CentOS Artwork +Repository. The CentOS Artwork Repository is maintain by CentOS +Artwork SIG which is formed by CentOS Community People. + +\section{General Suggestions} + +\begin{itemize} + +\item Use original names as much as possible. Do not rename original +file names if you don't need to. + +\end{itemize} + diff --git a/Manuals/Repository/filesystem-latex/Concepts/release.tex b/Manuals/Repository/filesystem-latex/Concepts/release.tex new file mode 100644 index 0000000..3f0ca92 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/release.tex @@ -0,0 +1,11 @@ +% Part : Concepts +% Chapter: The CentOS Release Brand +% ------------------------------------------------------------ +% $Id: release.tex 6191 2010-08-02 02:36:14Z al $ +% ------------------------------------------------------------ + +\section{Construction} +\section{Usage} +\section{Colors} +\section{Reductions} +\section{Prohibitions} diff --git a/Manuals/Repository/filesystem-latex/Concepts/scripts.tex b/Manuals/Repository/filesystem-latex/Concepts/scripts.tex new file mode 100644 index 0000000..660bcba --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/scripts.tex @@ -0,0 +1,395 @@ +% Part : Concepts +% Chapter: Scripts +% ------------------------------------------------------------ +% $Id: scripts.tex 6207 2010-08-05 13:11:13Z al $ +% ------------------------------------------------------------ + +\begin{description} +\item[framework:] trunk/Scripts/ +\end{description} + +\noindent Inside CentOS Artwork Repository, scripts are organized in +three groups: ``invocation scripts'', ``configuration scripts'' and +``function scripts''. Scripts are mainly used to help you automate and +standardize tasks. A graphical representation of how scripts are +organized inside CentOS Artwork Repository is illustrated in +\autoref{fig:Concepts:Scripts}. + +\begin{figure}[!hbp] +\centering +\includegraphics[width=0.8\textwidth]{% + ../Identity/Models/Img/en/Scripts/initFunctions.pdf} +\caption{The scripts organization model.% + \label{fig:Concepts:Scripts}} +\end{figure} + +\section{Invocation Scripts} +\hypertarget{sec:Concepts:Scripts:Invocation}{} +\label{sec:Concepts:Scripts:Invocation} + +Invocation scripts are identified by the name \texttt{render.sh}. You +may find invocation scripts inside \texttt{trunk/Translations/} and +\texttt{trunk/Identity/} structures. Invocation scripts' main purpose +is calling the appropriate configuration script. + +\section{Configuration Scripts} +\hypertarget{sec:Concepts:Scripts:Configuration}{} +\label{sec:Concepts:Scripts:Configuration} + +\begin{description} +\item[framework:] trunk/Scripts/Config/ +\end{description} + +\noindent Configuration scripts are identified by the name +\texttt{render.conf.sh}. In the script organization model +(\autoref{fig:Concepts:Scripts}), configuration scripts are the first +scripts executed by you after running the invocation script +(\texttt{render.sh}). Generally, configuration scripts are short +files that initialize functions, set variable definitions, and call +the appropriate function to start rendering. + +\subsection{Initialize Functions} + +Function initialization is the first action you do inside +configuration scripts. By default, functions are initialized using +the \texttt{initFunctions.sh} script, as illustrated in +\autoref{fig:Concepts:Scripts:Configuration:initFunctions}. The +\texttt{initFunctions.sh} script looks for functions definitions in +files that match the expansion \texttt{*.sh} inside the +\texttt{trunk/Scripts/Functions/} path, and exports them to the +current shell environment, that created when you ran the invocation +script. + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +# Initialize functions. +. /home/centos/artwork/trunk/Scripts/initFunctions.sh +\end{verbatim} +\hrulefill +\caption{Function initialization inside configuration scripts.% + \label{fig:Concepts:Scripts:Configuration:initFunctions}} +\end{figure} + +Once functions are initialized, they are ready to be used by you, in +any point after its initialization. This initialization arms you with +a customizable set of functionalities that can be used on +configuration scripts and reused inside functions themselves. + +\subsection{Define Artwork Component} + +The \texttt{ARTCOMP} variable defines the artwork component you want +to render. The \texttt{ARTCOMP}'s value defines the specific artwork +component's matching list and Themes' translation path. The +\texttt{ARTCOMP}'s value is built using the translation path structure +as reference. For example, if you want to render Anaconda progress +files, you need to know that artwork component's translation path +which is:\\ +\\ +\fbox{trunk/Translations/Identity/Themes/Distro/Anaconda/Progress}\\ +\\ +and then, go to its \texttt{render.conf.sh} file to define +\texttt{ARTCOMP} as the following:\\ +\\ +\fbox{ARTCOMP='Distro/Anaconda/Progress'}\\ +\\ +The \texttt{ARTCOMP}'s value is processed by \texttt{getMatchingList} +function to determine the specific artwork component's +translation-design matching list. The matching list function is +described in \autoref{sec:Concepts:Scripts:Function:getMatchingList}. + +\subsection{Define Filtering Pattern} + +The \texttt{REGEX} variable defines a regular expression as filtering +pattern. If the filtering pattern is specified, the rendering process +is limited to the amount of files matching the filtering pattern. By +default, this value is set to receive the shell's first argument +(\texttt{\$1}). This let you pass the filtering pattern on the +command line, at rendering time. If you need a fixed value for the +filtering pattern, you can change the \texttt{REGEX}'s value on your +working copy to whatever you need, but please do no commit that. + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +# Define filtering pattern. This is a regular expression +# matching the translation path. +REGEX="$1" +\end{verbatim} +\hrulefill +\caption{Define filtering pattern inside configuration scripts.% + \label{fig:Concepts:Scripts:Configuration:REGEX}} +\end{figure} + +\subsection{Define Post-rendering Actions} +\hypertarget{sec:Concepts:Scripts:Configuration:ACTIONS}{} +\label{sec:Concepts:Scripts:Configuration:ACTIONS} + +Post-rendering actions are specific functionalities applied to the +final files produced by base rendering functions like +\texttt{renderImage} and \texttt{renderText}. Post-rendering actions +are defined by the \texttt{ACTIONS} array variable. By default, the +\texttt{ACTIONS}'s value is set to empty (\texttt{ACTIONS[0]=''}) +which provokes no post-rendering action to be applied. A different +configuration is illustrated on +\autoref{fig:Concepts:Scripts:Configuration:ACTIONS}. + +When rendering images, using \texttt{renderImage}, the only result you +get is in PNG format. This is enough most of the time. But in some +other situations, you need to produce the same image in many different +formats (i.e. xpm, pdf, tiff, xbm, etc.). These tasks are very +specific and are not included inside \texttt{renderImage} function. +Instead, the \texttt{renderFormats} function was created and used as +post-rendering action in these situations. + +When rendering texts, using \texttt{renderText}, the only result you +get is in plain text format. Again, this is enough most of the time. +But in some other situations, you need to modify the final result to +provide some standardizations like: maximum line width, indentation of +first line different from second, one space between words, two after +sentences, etc. These tasks are very specific and are not included +inside \texttt{renderText} function. Instead, the \texttt{formatText} +function was created and used as post-rendering action in these +situations. + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +# Define post-rendering actions. An empty value means that no +# post-rendering action is applied. +ACTIONS[0]='renderFormats: tif xpm pdf ppm' +ACTIONS[1]='groupByFormat: png tif xpm pdf ppm' +\end{verbatim} +\hrulefill +\caption[Define post-rendering actions.]{Define post-rendering\ +actions. In this figure, post-rendering actions are used to produce\ +tif, xpm, pdf, ppm, image formats (from the base PNG image format)\ +and group them (PNG format included) inside directories. This is, all\ +png files are stored inside a png directory, all xpm files are\ +stored inside a xpm directory, and so on.% + \label{fig:Concepts:Scripts:Configuration:ACTIONS}} +\end{figure} + +\subsection{Start Rendering} + +The start rendering section defines the base action to do when the +current configuration script is called. In this section what you do is +calling one of the following functions: \texttt{renderImage} +(\autoref{sec:Concepts:Scripts:Function:renderImage}), or +\texttt{renderText} +(\autoref{sec:Concepts:Scripts:Function:renderText}). + +\section{Function Scripts} +\hypertarget{sec:Concepts:Scripts:Function}{} +\label{sec:Concepts:Scripts:Function} + +\begin{description} +\item[framework:] trunk/Scripts/Functions/ +\end{description} + +\noindent Function scripts are, in fact, shell functions. A shell +function stores a series of commands for later execution. When the +name of a shell function is used as a simple command name, the list of +commands associated with that function name is executed. Functions +are executed in the context of the current shell; no new process is +created to interpret them (contrast this with the execution of a +shell script). + +\subsection{renderImage} +\hypertarget{sec:Concepts:Scripts:Function:renderImage}{} +\label{sec:Concepts:Scripts:Function:renderImage} + +Inside CentOS Artwork Repository, the \texttt{renderImage} function is +the heart of image production. The \texttt{renderImage} function takes +translation files and apply them to design templates, as specified in +the artwork componet's matching list that is been rendered. The final +result are PNG images based on design templates and translation files. + +Additionally, the \texttt{renderImage} function accepts the following +post-rendering actions: + +\begin{description} + +\item[renderFormats:] The \texttt{renderFormats} function let you +produce different image formats from the base PNG image format. The +amount of image formats you can produce with \texttt{renderFormats} is +limited to the amount of image formats that ImageMagick command line +image manipulation tool can support. + +\item[groupByFormat:] The \texttt{renderByFormat} function let you +group similar image formats inside common directories. + +\item[renderGrub:] The \texttt{renderGrub} function let you produce 14 +colors images from the base PNG image format. The \texttt{renderGrub} +function is used to automate GRUB artwork component image production. +For this function to work, it is required to define the +\texttt{grub.ppm} palette first. + +\item[renderSyslinux:] The \texttt{renderSyslinux} function let you +produce LSS16 images from the base PNG image format. The +\texttt{renderSyslinux} function is used to automate Anaconda prompt +artwork component image production. For this function to work, it is +required to define the \texttt{syslinux.ppm} and \texttt{syslinux.hex} +palettes first. + +\item[renderBrands:] The \texttt{renderBrands} function let you +produce different image formats from the base PNG image format. +Basically, it is does the same of \texttt{renderFormats}, plus two +colors grayscale, and emboss effect convertions that are not included +inside \texttt{renderFormats}. + +\end{description} + +\subsection{renderText} +\hypertarget{sec:Concepts:Scripts:Function:renderText}{} +\label{sec:Concepts:Scripts:Function:renderText} + +The \texttt{renderText} function produce plain text files from text +plain design tempaltes and translation files. The \texttt{renderText} +standardize the text rendering process inside CentOS Artwork +Repository. Additionally, the \texttt{renderText} function accepts the +following post-rendering actions: + +\begin{description} + +\item[formatText:] The \texttt{formatText} function, let you format +plain text files. This function uses the GNU's \texttt{fmt} tool as +base to do all modifications. + +\end{description} + +\subsection{getMatchingList} +\hypertarget{sec:Concepts:Scripts:Function:getMatchingList}{} +\label{sec:Concepts:Scripts:Function:getMatchingList} + +The matching list specifies the relation between design templates and +translation files that artwork components have. The +\texttt{renderImage} and \texttt{renderText} functions require this +information in order to work properly. + +Initially, the matching list was defined explicitly and independently +inside each artwork component's configuration script. Later, as many +of these components had just the same configuration stuff, the code +was reduced and unified inside \texttt{getMatchingList} function. +Inside \texttt{getMatchingList}, there is a case selection statement +where specific matching lists cases are defined, and one default +behaivour that match in thoses cases where none else does. + +The matching list code reduction changed the way you customize artwork +component's matching list. From now on, you look inside configuration +files to be sure that \texttt{ARTCOMP} variable refers to the +appropriate artwork component, and inside \texttt{getMatchingList} +function to define its matching list. For example, when rendering +Anaconda progress, its matching list specifies which translation files +apply which design templates. So, to change the matching list of this +artwork component, you need to edit the function +\texttt{getMatchingList} and set the appropriate relation there, in +the Anaconda progress matching list specification. + +When setting artwork components' matching list, you can use any of the +following configuration available: + +\begin{description} + +\item[Configuration 1:] Specific translation files are applied to +specific design templates. In this configuration you have detailed +control over which translation files are applied to which design +template. + +\begin{verbatim} +MATCHINGLIST="\ +design-template-A.svg: translation-file-1.sed translation-file-2.sed +design-template-B.svg: translation-file-3.sed translation-file-4.sed +" +\end{verbatim} + +Another way to write the previous example is: + +\begin{verbatim} +MATCHINGLIST="\ +design-template-A.svg:\ + translation-file-1.sed\ + translation-file-2.sed +design-template-B.svg:\ + translation-file-3.sed\ + translation-file-4.sed +" +\end{verbatim} + +In the above examples translation files 1 and 2 apply +design-template-A.svg. Likewise, translation files 3 and 4 apply +design-template-B.svg. That was a simple case, but what about if you +have hundreds of translation files to apply to specific design +templates? Lets say, translation files from 1 to 49 apply +design-template-A.svg and translation files from 50 to 99 apply +design-template-B.svg. It would be tiresome to write down the name of +every single file in the above configuration. In these situations you +can ``generate'' the translation files as shown below: + +\begin{verbatim} +MATCHINGLIST="\ +design-template-A.svg:\ + $(for NUMBER in $(sed 1 49);do + echo -n translation-file-${NUMBER}.sed ' ' + done) +design-template-B.svg:\ + $(for NUMBER in $(sed 50 99);do + echo -n translation-file-${NUMBER}.sed ' ' + done) +" +\end{verbatim} + +Another interesting case is when you need to apply hundreds of +translation files to hundreds of design templates, in a file structure +where they both share a common bond path. That is the +\texttt{Identity/Brands} artwork component case. Writing down such a +matching list consumes lot of time. So you can ``generate'' the +entire matching list like the following: + +\begin{verbatim} +MATCHINGLIST="\ +$(for TEMPLATE in $(find $(getPath 'trunk/Identity/Brands')/tpl \ + -name '*.svg' | sed -r 's!.*/Brands/Tpl/(.*)$!\1!' | sort );do + + TRANSLATION=$(find $(getPath \ + 'trunk/Translations/Identity/Brands')/$(echo $TEMPLATE \ + | sed 's!\.svg!!') -name '*.sed' \ + | sed -r 's!^.*/Brands/(.*)$!\1!' \ + | sort | tr '\n' ' ') + + echo $TEMPLATE: $TRANSLATION + done) +" +\end{verbatim} + +\item[Configuration 2:] All translation files are applied to a single +design template. In this configuration all artwork component's +translation files are applied to one design template +(design-template-A.svg for the matter of this case). + +\begin{verbatim} +MATCHINGLIST="design-template-A.svg" +\end{verbatim} + +\item[Configuration 3:] Translation files are applied to design +templates that share a common name. In this configuration translation +files are applied to design templates taking the name part, without +extension, as reference. This means that, if you have a translation +file named \texttt{File-1.sed} you need to have a \texttt{File-1.svg} +inside design templates. This way, \texttt{File-1.sed} can be applied +to \texttt{File-1.svg} and, as result, produce the \texttt{File-1.png} +file. This is the default matching list behaivour. + +\begin{verbatim} +MATCHINGLIST="" +\end{verbatim} + +\end{description} + +\subsection{getPath} + +The \texttt{getPath} function creates the artwork component's absolute +path. Before output the absolute path, \texttt{getPath} removes any +``strange'' character from the final path. For \texttt{getPath} to +work, the relative path to the artwork component should be provided +from \texttt{trunk/}'s directory level on. diff --git a/Manuals/Repository/filesystem-latex/Concepts/structure.tex b/Manuals/Repository/filesystem-latex/Concepts/structure.tex new file mode 100644 index 0000000..f9faf32 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/structure.tex @@ -0,0 +1,8 @@ +% Part : Concepts +% Chapter: The CentOS Visual Structure +% ------------------------------------------------------------ +% $Id: structure.tex 6191 2010-08-02 02:36:14Z al $ +% ------------------------------------------------------------ + +\section{Monolithic Structure} + diff --git a/Manuals/Repository/filesystem-latex/Concepts/symbol.tex b/Manuals/Repository/filesystem-latex/Concepts/symbol.tex new file mode 100644 index 0000000..c6b26bf --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/symbol.tex @@ -0,0 +1,11 @@ +% Part : Concepts +% Chapter: The CentOS Symbol +% ------------------------------------------------------------ +% $Id: symbol.tex 6191 2010-08-02 02:36:14Z al $ +% ------------------------------------------------------------ + +\section{Construction} +\section{Usage} +\section{Colors} +\section{Reductions} +\section{Prohibitions} diff --git a/Manuals/Repository/filesystem-latex/Concepts/translations.tex b/Manuals/Repository/filesystem-latex/Concepts/translations.tex new file mode 100644 index 0000000..c892f28 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/translations.tex @@ -0,0 +1,147 @@ +% Part : Concepts +% Chapter: Translations +% ------------------------------------------------------------ +% $Id: translations.tex 6191 2010-08-02 02:36:14Z al $ +% ------------------------------------------------------------ + +\begin{description} +\item[framework:] trunk/Translations/ +\end{description} + +\noindent Here is where translators locale images. Image localization +is defined inside \texttt{.sed} files, also known as translation +files. Translation files can be common or specific. The given +organization of translation files defines the translation path. + +\section{Common Translations} +\hypertarget{sec:Concepts:Translations:Common}{} + +Common translation files contain common localization or no +localization at all for their related images. They are in the root +directory of the translation path. Common translation files create +common images for all major releases of CentOS Distribution. + +\section{Specific Translations} +\hypertarget{sec:Concepts:Translations:Specific}{} + +Specific translation files contain specific localization for their +related images. Specific translation files are not in the root +directory of the translation path. Specific translation files are +inside directories which describe the type of translation they are +doing. + +\section{Translation Path} +\hypertarget{sec:Concepts:Translations:Path}{} + +Translation path is where we organize common and specific translation +files. Translation path is also used as reference to build the path of +rendered images inside image directory (see +\hyperlink{sec:Concepts:Frameworks:Image}{Image Files}). + +When rendering images, if no REGEX argument is provided to +\texttt{render.sh} identity script, all translation files in the +translation path are read and applied one by one to its related design +template ---as defined in \texttt{getMatchingList} function--- to +produce a translated image. Images produced using the +\texttt{render.sh} identity script have the same name of its +translation file, but with the \texttt{.png} extension instead. + +To control the number of images produced by \texttt{render.sh} +identity script, you need to look into the translation path and +provide a regular expression pattern that matches the translation +path, or paths, related to the image, or images, you want to produce. + +The regular expression pattern you provide to \texttt{render.sh} +identity script is applied to the translation path from its very +beginning. It is not the same to say \texttt{5/es/01-welcome} that +\texttt{01-welcome}, the frist expression matches but the last one +does not. + +When using REGEX you don't need to specify the file extension. It is +removed from translation path before applying the REGEX pattern, so it +doesn't count here. + +\section{Translation Markers} +\hypertarget{sec:Concepts:Translations:Markers}{} + +Translation markers are used in design templates and translation files +as replacement pattern to commit image translation. When +\texttt{render.sh} identity script renders images, translation files +are applied to design templates to get a PNG translated image as +result. In order to have the appropriate translation on the PNG +image, marker defintion in translation files should match markers in +design templates. + +Translation markers can be whatever text you want, but as convenction +we've defined those we use inside CentOS Artwork Repository. This +definition creates a common point of reference to translators and +graphic designers. To have a clean definition of translation markers +is what makes possible that translators and graphic designers can work +together but independently one another. + +\section{Translation Rendering} +\hypertarget{sec:Concepts:Translations:Rendering}{} + +Translation paths and files ---also known as the translation +structure--- are produced using the \texttt{render.sh} translation +script, available in the current translation directory. + +The \texttt{render.sh} translation script combines the content of a +translation template directory ---holding common information--- with +the release-specific information you provide as argument when +executing the script. As result, the \texttt{render.sh} translation +script produces the translation structure that \texttt{render.sh} +identity script needs to create translated images. + +\section{Translation Rendering Script} +\hypertarget{sec:Concepts:Translations:RenderingScripts}{} + +The \texttt{render.sh} translation script produces release-specific +translation directories. Use the \texttt{render.sh} translation script +whenever you need to create a new release-specific translation +directory based on translation template directory. The \texttt{render.sh} +translation script has the following syntax: + +\begin{quote} +\texttt{./render.sh RELEASE ...} +\end{quote} + +The RELEASE argument defines the release number used to create the +release-specific translation directory. You can pass many RELEASE +arguments, separated by one or more spaces, to \texttt{render.sh} +translation script in a single call. If no RELEASE argument is passed +to \texttt{render.sh} translation script then all release-specific +translation directories, available in the current translation +directory, are updated using the translation template as reference. + +Default behaviour of \texttt{render.sh} translation script may be +usefull if all your release-specific translation directories always +have the same information that translation template does. If this is +the case, you only need to maintain the translation template and use +the \texttt{render.sh} translation script to propagate changes to each +release-specific translation directory. + +In contrast, if you are using the \texttt{render.sh} translation +script to create release-specific translation directories that use +translation template as base to introduce non-reusable translations, +you should take care when executing the \texttt{render.sh} translation +script. Otherwise, your non-reusable translations may be replaced +with those in template. + +Inside CentOS Artwork Repository, all translation directories +(reusable and non-reusable) are versioned. If you accidentally +propagate template content to a non-reusable translation, you have the +Subversion's \texttt{revert} and \texttt{update} commands to undo the +mess. + +As general rule, when you use the \texttt{render.sh} translations +script, take care of details and check twice before commit your +translation changes up to CentOS Artwork Repository. + +\section{Translation Template Directory} +\hypertarget{sec:Concepts:Translations:TemplateDirectory}{} + +The translation template directory is located in the current +translation directory and contains common translations for all +release-specific translation directories. It is also used as base to +build non-reusable translation. diff --git a/Manuals/Repository/filesystem-latex/Concepts/typeface.tex b/Manuals/Repository/filesystem-latex/Concepts/typeface.tex new file mode 100644 index 0000000..6f2f78e --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/typeface.tex @@ -0,0 +1,11 @@ +% Part : Concepts +% Chapter: The CentOS Typeface +% ------------------------------------------------------------ +% $Id: typeface.tex 6191 2010-08-02 02:36:14Z al $ +% ------------------------------------------------------------ + +\section{Construction} +\section{Usage} +\section{Colors} +\section{Reductions} +\section{Prohibitions} diff --git a/Manuals/Repository/filesystem-latex/Concepts/typography.tex b/Manuals/Repository/filesystem-latex/Concepts/typography.tex new file mode 100644 index 0000000..0de93dc --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Concepts/typography.tex @@ -0,0 +1,8 @@ +% Part : Concepts +% Chapter: The CentOS Typography +% ------------------------------------------------------------ +% $Id: typography.tex 6191 2010-08-02 02:36:14Z al $ +% ------------------------------------------------------------ + +\section{Usage} +\section{Colors} diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Firstboot/framework.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Firstboot/framework.tex new file mode 100644 index 0000000..81bbbd8 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Firstboot/framework.tex @@ -0,0 +1,233 @@ +\section{Identity} +\hypertarget{sec:Distribution:Anaconda:Firstboot:Identity}{} +\label{sec:Distribution:Anaconda:Firstboot:Identity} + +\begin{description} +\item[framework:] +trunk/Identity/Themes/\$THEME/Distro/Anaconda/Firstboot/ +\end{description} + +\noindent Here is where CentOS firstboot design templates and image +rendering take place. Firstboot identity file structure is illustrated +in \autoref{fig:Distribution:Anaconda:Firstboot:Identity} and +described in the following sections. + +\begin{figure} +\hrulefill +\begin{verbatim} +trunk/Identity/Themes/$THEME/Distro/Anaconda/Firstboot/ +|-- img +| |-- 3 +| | `-- splash-small.png +| |-- 4 +| | `-- splash-small.png +| |-- 5 +| | `-- splash-small.png +| |-- ... (more releases here) +| `-- firstboot-left.png +|-- render.sh +`-- tpl + |-- firstboot-left.svg + `-- splash-small.svg +\end{verbatim} +\hrulefill +\caption{Firstboot identity framework.% + \label{fig:Distribution:Anaconda:Firstboot:Identity}} +\end{figure} + +\subsection{Design Templates} + +\begin{description} +\item[framework:] +trunk/Identity/Themes/\$THEME/Distro/Anaconda/Firstboot/Tpl/ +\end{description} + +\noindent Here is where Firstboot design templates are stored. +Firstboot design templates control Firstboot's visual style. + +\begin{description} + +\item[firstboot-left.svg:] This design is common for all major +releases of CentOS Distribution. It is visible in all firstboot +screens. In +\autoref{fig:Distribution:Anaconda:Firstboot:Identity:Models}, this +design is illustraded by the number 8. + +\item[splash-small.svg:] This design is specific for each major +release of CentOS Distribution. There is one splash-small.png image +for each major release of CentOS Distribution. This image is visible +only in the first (Welcome) screen of Firstboot. In +\autoref{fig:Distribution:Anaconda:Firstboot:Identity:Models}, this +design is illustraded by number 5. + +\end{description} + +\subsection{Design Models} + +\begin{description} +\item[framework:] +trunk/Identity/Models/Distro/Anaconda/Firstboot/ +\end{description} + +\noindent Here is where firstboot design models are stored. Firstboot +design model is shown in +\autoref{fig:Distribution:Anaconda:Firstboot:Identity:Models} and described +below: + +\begin{figure} +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% +../Identity/Models/Img/en/Distro/Anaconda/Firstboot/splash-small.pdf}} +\end{center} +\caption{Firstboot design model.% + \label{fig:Distribution:Anaconda:Firstboot:Identity:Models}} +\end{figure} + +\begin{description} + +\item[1:] List of labels and a pointer showing in which configuration +screen you are. + +\item[2:] Screen icon. The screen icon is visible in all firstboot +screens. Each firsboot screen may have its own screen icon. + +\item[3:] Screen label. + +\item[4:] Screen description. + +\item[5:] Splash image (splash-small.png). The splash +image is visible in firstboot welcome screen only. + +\item[6:] Configuration stuff. + +\item[7:] Navigation area. Basically two buttons to navegate +configuration back and forward. + +\item[8:] List of labels' background image (firtboot-left.png). This +image is visible in all firstboot screens. + +\end{description} + +\subsection{Image Files} +\hypertarget{sec:Distribution:Anaconda:Firstboot:Identity:Images}{} +\label{sec:Distribution:Anaconda:Firstboot:Identity:Images} + +\begin{description} +\item[framework:] +trunk/Identity/Themes/\$THEME/Distro/Anaconda/Firstboot/Img/ +\end{description} + +\noindent Here is where firstboot final images are stored. + +\subsection{Image Files Rendering} +\hypertarget{sec:Distribution:Anaconda:Firstboot:Identity:ImagesRendering}{} +\label{sec:Distribution:Anaconda:Firstboot:Identity:ImagesRendering} + +\begin{description} +\item[framework:] +trunk/Identity/Themes/\$THEME/Distro/Anaconda/Firstboot/ +\end{description} + +\noindent Here is where you produce firstboot images. The following +rendering examples, based on +\autoref{fig:Distribution:Anaconda:Firstboot:Translations}, illustrate +the firstboot image files rendering process.\\ +\\ +\fbox{\texttt{./render.sh}}\\ +\\ +\fbox{\texttt{./render.sh '(5|6)/splash'}}\\ +\\ +\fbox{\texttt{./render.sh '(firstboot-left|5|4)/splash'}} + +\section{Translations} +\hypertarget{sec:Distribution:Anaconda:Firstboot:Translations}{} +\label{sec:Distribution:Anaconda:Firstboot:Translations} + +\begin{description} +\item[framework:] +trunk/Translations/Identity/Themes/Distro/Anaconda/Firstboot +\end{description} + +\noindent Here is where translators locale firstboot images. Image +localization is defined inside .sed files, also known as translation +files. Translation files can be common or specific. The given +organization of translation files defines the translation path. + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +trunk/Translations/Identity/Themes/Distro/Anaconda/Firstboot +|-- 3 +| `-- splash-small.sed +|-- 4 +| `-- splash-small.sed +|-- 5 +| `-- splash-small.sed +|-- ... (more release directories) +`-- firstboot-left.sed +\end{verbatim} +\hrulefill +\caption{Firstboot translation path.% + \label{fig:Distribution:Anaconda:Firstboot:Translations}} +\end{figure} + +\subsection{Translation Markers} + +In firstboot, markers are used in the file splash-small.svg only, +specifically to set the major release number of CentOS Distribution in +CentOS Release Brand. Since firstboot-left.svg design is common for +all CentOS Distribution there is no need to set any marker on it. + +Markers used in firstboot design templates and translation files are +described in \autoref{tab:Distribution:Anaconda:Firstboot:Markers}. + +\begin{table} +\centering +\begin{tabular}{rl} +\hline +\textbf{Marker} & \textbf{Description}\\ +\hline +=MAJOR\_RELEASE= & Major release number of CentOS Distribution.\\ +\hline +\end{tabular} +\caption{Firstboot translation markers.% + \label{tab:Distribution:Anaconda:Firstboot:Markers}} +\end{table} + +\section{Manuals} +\hypertarget{sec:Distribution:Anaconda:Firstboot:Manuals}{} +\label{sec:Distribution:Anaconda:Firstboot:Manuals} + +\begin{description} +\item[framework:] +trunk/Manuals/Distribution/Anaconda/Firstboot/ +\end{description} + +\noindent Here is where firstboot documentation is stored. If you +want to help improving Firstboot documentation this is the place you +need to go. + +\section{Scripts} +\hypertarget{sec:Distribution:Anaconda:Firstboot:Scripts}{} + +\begin{description} +\item[framework:] trunk/Scripts/Config/Identity/Themes/Distro/Anaconda/Firstboot/ +\end{description} + +\noindent Here is stored the Firstboot \texttt{render.conf.sh} +configuration script. To render Firstboot images correctly, the +\texttt{ARTCOMP} configuration variable inside Anaconda progress +configuration script should be defined as illustrated in +\autoref{fig:Distribution:Anaconda:Firstboot:Scripts:Config}. + +\begin{figure} +\hrulefill +\begin{verbatim} +# Define artwork component. +ARTCOMP='Identity/Themes/Distro/Anaconda/Firstboot' +\end{verbatim} +\hrulefill +\caption{Firstboot configuration layout.% + \label{fig:Distribution:Anaconda:Firstboot:Scripts:Config}} +\end{figure} + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Firstboot/introduction.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Firstboot/introduction.tex new file mode 100644 index 0000000..fd02e0a --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Firstboot/introduction.tex @@ -0,0 +1,8 @@ +This chapter describes the visual style of CentOS firstboot +(1.4.27.3-1.el5.centos). Firstboot is the initial system configuration +utility that guides you through a series of steps for easier +configuration of the machine (keyboard layout, language, time zone, +etc.). Firstboot takes place the first time you boot up your installed +system. Firstboot visual style is controlled by a left banner, always +visible, and a splash image, shown on the welcome screen only. + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Firstboot/rebranding.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Firstboot/rebranding.tex new file mode 100644 index 0000000..42080e5 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Firstboot/rebranding.tex @@ -0,0 +1,126 @@ +\section{Rebranding} + +\subsection{Package: redhat-logos} + +The \texttt{redhat-logos} package contains files created by the CentOS +Project to replace the Red Hat ``Shadow Man'' logo and RPM logo. The +Red Hat ``Shadow Man'' logo, RPM, and the RPM logo are trademarks or +registered trademarks of Red Hat, Inc. Firstboot images that need to +be rebranded in \texttt{redhat-logos} package are illustrated in +\autoref{fig:Distribution:Anaconda:Firstboot:Rebranding:Logos}. + +Replacements for these files are available in the Firstboot image +directory ( +\autoref{sec:Distribution:Anaconda:Firstboot:Identity:Images}) of +Firstboot (\autoref{cha:Distribution:Anaconda:Firstboot}) inside your +working copy of CentOS Artwork Repository. + +Once you rebrand the image files inside the SRPM package, you need to +rebuild it with the new brand information. + +\subsection{Package: redhat-artwork} + +The \texttt{redhat-artworks} package contains the themes and icons +that make up the CentOS default look and feel. Relevant files to +firstboot rebranding are described below: + +The following files in \texttt{redhat-artwork} need to be rebranded: + +Once you rebrand the image files inside the \texttt{redhat-artwork} +SRPM package, you need to rebuild it with the new brand information. + +\subsection{Package: firstboot} + +Firstboot messages locale contains the upstream brand, so they need to +be rebranded too. The .po files you need to rebrand are inside the +firstboot package. The \texttt{firstboot} package contains the +firstboot utility that runs after installation. Once you rebrand the +content of .po files inside \texttt{firstboot} SRPM package, you need +to rebuild it with the new brand information. The rebranded .mo files +are created in the installation process. + +\subsection{Package: firstboot-tui} + +The \texttt{firstboot-tui} package contains a text interface for the +\texttt{firstboot} package. Once you rebrand the content of +\texttt{.po} files inside the \texttt{firstboot-tui} SRPM package, you +need to rebuild it with the new brand information. The rebranded +\texttt{.mo} files are created in the installation process. + +\subsection{Package: centos-release} + +The CentOS License Agreement, shown after the welcome screen of +firstboot, is controled by the file \texttt{eula.en\_US} which is +controlled by the \texttt{centos-release} package. The +\texttt{centos-release} package contains the CentOS release notes and +eula files. + +The file \texttt{eula.en\_US} contains the English translation of +CentOS License Agreement. English language is the reference for +specific language translations of CentOS License Agreement. Specific +language translations of CentOS License Agreement are accepted by +Firstboot in the path \texttt{/usr/share/eula/}. + +File names of eula specific language translations should have the +format \texttt{eula.lang} or \texttt{eula.lang\_COUNTRY}. Where +\texttt{lang} is a two-lowercase-letters code representing the +translation language and \texttt{COUNTRY} a two-uppercase-letters code +representing the country of that translation language. Languages' and +countries' codes are specified as described in the standards ISO639 +and ISO3166 respectively. + +When using Anaconda in a language different from English firstboot +checks if there is any eula translation file for the currenct +language. If so, the specific language eula file is loaded and shown +to the user. Otherwise the \texttt{eula.en\_US} file is used. + +The CentOS eula files, described in the previous list, have their own +framework inside CentOS Artwork Repository. They are rendered similar +to images using templates and translation files, as well as rendering +scripts. + +The files \texttt{EULA} and \texttt{eula.en\_US} should have the same +information. The \texttt{GPL} file contains the GPL license with a +brief description of how it applies to CentOS Distribution. + +Once you rebrand the text files inside the \texttt{centos-release} +SRPM package, you need to rebuild it with the new brand information. + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +/usr/share/firstboot/pixmaps/ +|-- shadowman-round-48.png +\end{verbatim} +\hrulefill +\caption{Firstboot rebranding (package: redhat-logos)% + \label{fig:Distribution:Anaconda:Firstboot:Rebranding:Logos}} +\end{figure} + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +/usr/share/firstboot/pixmaps/ +|-- firstboot-left.png +|-- splash-small.png +\end{verbatim} +\hrulefill +\caption{Firstboot rebranding (package: redhat-artwork)% + \label{fig:Distribution:Anaconda:Firstboot:Rebranding:Artwork}} +\end{figure} + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +/usr/share/eula/ +|-- eula.en_US +/usr/share/doc/centos-release-5/ +|-- EULA +|-- GPL +\end{verbatim} +\hrulefill +\caption{Firstboot rebranding (package: centos-release)% + \label{fig:Distribution:Anaconda:Firstboot:Rebranding:Release}} +\end{figure} +\begin{verbatim} +\end{verbatim} diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/chapter.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/chapter.tex new file mode 100644 index 0000000..ad5e616 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/chapter.tex @@ -0,0 +1,29 @@ +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ + +\section{Identity} +\hypertarget{sec:Distribution:Anaconda:Header:Identity}{} +\label{sec:Distribution:Anaconda:Header:Identity} +\input{Distribution/Anaconda/Header/identity.tex} + +\section{Translations} +\hypertarget{sec:Distribution:Anaconda:Header:Translations}{} +\label{sec:Distribution:Anaconda:Header:Translations} +\input{Distribution/Anaconda/Header/translations.tex} + +\section{Manuals} +\hypertarget{sec:Distribution:Anaconda:Header:Manuals}{} +\label{sec:Distribution:Anaconda:Header:Manuals} +\input{Distribution/Anaconda/Header/manuals.tex} + +\section{Scripts} +\hypertarget{sec:Distribution:Anaconda:Header:Scripts}{} +\label{sec:Distribution:Anaconda:Header:Scripts} +\input{./Distribution/Anaconda/Header/scripts.tex} + +\section{Packages} +\hypertarget{sec:Distribution:Anaconda:Header:Packages}{} +\label{sec:Distribution:Anaconda:Header:Packages} +\input{Distribution/Anaconda/Header/packages.tex} + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/identity.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/identity.tex new file mode 100644 index 0000000..d249404 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/identity.tex @@ -0,0 +1,85 @@ +% Part : Distribution +% Chapter: Anaconda Header +% Section: Identity +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +trunk/Identity/Themes/$THEME/Distro/Anaconda/Header/ +|-- img +| |-- 3 +| | |-- anaconda_header.png.png +| |-- 4 +| |-- 5 +| `-- ... more major releases +|-- render.sh +`-- tpl + `-- anaconda_header.png.svg +\end{verbatim} +\hrulefill +\caption{Anaconda header identity's framework.% + \label{fig:Distribution:Anaconda:Header:Identity}} +\end{figure} + +\subsection{Designs Templates} +\hypertarget{sec:Distribution:Anaconda:Header:Identity:Templates}{} +\label{sec:Distribution:Anaconda:Header:Identity:Templates} + +\begin{itemize} +\item trunk/Identity/Themes/\$THEME/Distro/Anaconda/Header/tpl +\end{itemize} + +\subsection{Design Models} + +\begin{itemize} +\item trunk/Identity/Models/Tpl/Distro/Anaconda/Header/ +\item trunk/Identity/Models/Img/Distro/Anaconda/Header/ +\end{itemize} + +\begin{figure}[!hbp] +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Models/Img/en/Distro/Anaconda/Header/fig-1-anaconda_header.pdf}} +\end{center} +\caption{Anaconda header design model.% + \label{fig:Distribution:Anaconda:Header:Models:Fig1}} +\end{figure} + +\begin{figure}[!hbp] +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Models/Img/en/Distro/Anaconda/Header/fig-2-anaconda_header.pdf}} +\end{center} +\caption{Anaconda header position in the screen.% + \label{fig:Distribution:Anaconda:Header:Models:Fig2}} +\end{figure} + +\subsection{Image Files} +\hypertarget{sec:Distribution:Anaconda:Header:Identity:Images}{} +\label{sec:Distribution:Anaconda:Header:Identity:Images} + +\begin{itemize} +\item \texttt{anaconda\_header.png}: base image format. +\end{itemize} + +\subsection{Image Files Rendering} +\hypertarget{sec:Distribution:Anaconda:Header:Identity:Issues}{} +\label{sec:Distribution:Anaconda:Header:Identity:Issues} +\fbox{\texttt{./render.sh}} +\fbox{\texttt{./render.sh '5'}} +\fbox{\texttt{./render.sh '(3|4|5)'}} + +\subsection{Color Limitations} +\hypertarget{sec:Distribution:Anaconda:Header:Identity:Colors}{} +\label{sec:Distribution:Anaconda:Header:Identity:Colors} + +Anaconda Header does not have color limitations. + +\subsection{Issues} +\hypertarget{sec:Distribution:Anaconda:Header:Issues}{} +\label{sec:Distribution:Anaconda:Header:Issues} + +No one known. diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/manuals.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/manuals.tex new file mode 100644 index 0000000..dfe7989 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/manuals.tex @@ -0,0 +1,10 @@ +% Part : Distribution +% Chapter: Anaconda Header +% Section: Scripts +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ +\begin{itemize} +\item trunk/Manuals/Identity/Themes/Distro/Anaconda/Header/ +\end{itemize} + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/packages.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/packages.tex new file mode 100644 index 0000000..1ac4fc4 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/packages.tex @@ -0,0 +1,9 @@ +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ +\begin{itemize} +\item \texttt{redhat-logo} +\begin{itemize} +\item /usr/share/anaconda/pixmaps/anaconda\_header.png +\end{itemize} +\end{itemize} diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/scripts.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/scripts.tex new file mode 100644 index 0000000..4c44bd6 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/scripts.tex @@ -0,0 +1,9 @@ +% Part : Distribution +% Chapter: Anaconda Header +% Section: Scripts +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ +\begin{itemize} +\item trunk/Scripts/Identity/Themes/Distro/Anaconda/Header/ +\end{itemize} diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/translations.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/translations.tex new file mode 100644 index 0000000..86d13e9 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Header/translations.tex @@ -0,0 +1,30 @@ +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ +\begin{figure} +\hrulefill +\begin{verbatim} +trunk/Translations/Identity/Themes/Distro/Anaconda/Header/ +|-- 3 +| `-- anaconda_header.sed +|-- 4 +|-- 5 +|-- ... more major releases +|-- render.sh +`-- tpl + `-- anaconda_header.sed +\end{verbatim} +\hrulefill +\caption{Anaconda header translation framework.% + \label{fig:Distribution:Anaconda:Header:Translations}} +\end{figure} + +% ------------------------------------------------------------ +\subsection{Translation Markers} +\hypertarget{sec:Distribution:Anaconda:Header:Translations:Markers}{} +\label{sec:Distribution:Anaconda:Header:Translations:Markers} + +\begin{itemize} +\item \texttt{=VERSION=}: Major release number of CentOS distribution. +\end{itemize} + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Progress/framework.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Progress/framework.tex new file mode 100644 index 0000000..b33d62a --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Progress/framework.tex @@ -0,0 +1,360 @@ +% Part: Distribution +% Chapter: Anaconda progress - Framework +% ------------------------------------------------------------ +% $Id: framework.tex 6207 2010-08-05 13:11:13Z al $ +% ------------------------------------------------------------ + \section{Identity} +\hypertarget{sec:Distribution:Anaconda:Progress:Identity}{} + \label{sec:Distribution:Anaconda:Progress:Identity} + +\begin{description} +\item[framework:] trunk/Identity/Themes/\$THEME/Distro/Anaconda/Progress/ +\end{description} + +\noindent Anaconda progress identity's framework is stored here. +Anaconda progress identity's framework is illustrated in +\autoref{fig:Distribution:Anaconda:Progress:Identity} and described in +the following sections. + +\begin{figure} +\hrulefill +\begin{verbatim} +trunk/Identity/Themes/$THEME/Distro/Anaconda/Progress/ +|-- img +| |-- 3 +| | |-- bn_IN +| | | |-- 01-welcome.png +| | | |-- 02-donate.png +| | | |-- 03-yum.png +| | | `-- ... (more bn_IN language-specific images) +| | |-- cs +| | | |-- 01-welcome.png +| | | |-- 02-donate.png +| | | |-- 03-yum.png +| | | `-- ... (more cs language-specific images) +| | |-- ... (more languages here) +| | |-- first-lowres.png +| | |-- first.png +| | |-- ... (more language directories) +| | |-- progress_first-lowres.png +| | |-- progress_first.png +| | `-- ... (more language directories) +| |-- 4 +| |-- 5 +| `-- ... (more release directories) +|-- render.sh +`-- tpl + |-- first-lowres.svg + |-- first.svg + |-- list.svg + `-- paragraph.svg +\end{verbatim} +\hrulefill +\caption{Anaconda progress identity's framework.% + \label{fig:Distribution:Anaconda:Progress:Identity}} +\end{figure} + +% ------------------------------------------------------------ + \subsection{Design Templates} +\hypertarget{sec:Distribution:Anaconda:Progress:Identity:Templates}{} + \label{sec:Distribution:Anaconda:Progress:Identity:Templates} + +\begin{description} +\item[framework:] trunk/Identity/Themes/\$THEME/Distro/Anaconda/Progress/Tpl/ +\end{description} + +\noindent Anaconda progress design templates are stored here. +Anaconda progress design templates are organized in: Anaconda progress +first slide and Anaconda progress language-specific slides set of +images. + +Anaconda progress first slide is the one used to open the package +installation process. Anaconda progress first slide design has no +translation. It is used just as it is, no matter what the current +Anaconda's installation language be. Anaconda progress first slide +design is controlled by \texttt{first.svg}, and +\texttt{first-lowres.svg} design templates +(\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:First}). +If the screen resolution is less than 800 x 600 pixels, the +\texttt{first-lowres.svg} design is used. If the screen resolution is +equal or greater that 800 x 600 pixels, the \texttt{first.svg} design +is used. + +Anaconda progress language-specific slides set of images start to +rotate a few seconds after progress first slide. Anaconda progress +language-specific slides set of images design is defined by +\texttt{list.svg} +(\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:Paragraph}) +and \texttt{paragraph.svg} +(\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:List}) +design templates. + +Anaconda progress language-specific slides set of images resumes +relevant features coming on the CentOS distribution that is being +installed. As graphic designer, you need not to care very much about +translating Anaconda progress language-specific slides set of images, +this is job for translators. As graphic designer, most of your +attention is focused on how the slides set of images looks like. + +Anaconda progress language-specific slides set of images are loaded +based on Anaconda's installation language. By default, Anaconda's +installation language is English. But you can change Anaconda's +default language in the screen ``Installation Language'' to whatever +your preferred language be. + +If Anaconda's installation language is English, Anaconda progress +language-specific slides set of images are loaded in English. If +Anaconda's installation language is different from English, Anaconda +looks for the language-specific slides set of images that matches the +current Anaconda's installation language and uses them in the +rotation, if that slides set of images exists of course. If there is +no language-specific slides set of images available for the current +Anaconda's installation language, Anaconda uses the English slides set +of images. + +To verify the final look and feel of your Anaconda progress slide +images, you need to render them. To render Anaconda progress slide +images you use the \texttt{render.sh} identity script as described in +``\hyperlink{sec:Distribution:Anaconda:Progress:Identity:Image:Rendering}{Image +Files Rendering}'' +(\autoref{sec:Distribution:Anaconda:Progress:Identity:Image:Rendering}). +The \texttt{render.sh} identity script helps you automate the +rendering process of Anaconda progress slide images. + +% ------------------------------------------------------------ + \subsection{Design Models} +\hypertarget{sec:Distribution:Anaconda:Progress:Identity:Models}{} + \label{sec:Distribution:Anaconda:Progress:Identity:Models} + +\begin{description} +\item[framework:] trunk/Identity/Models/Tpl/Distro/Anaconda/Progress/ +\end{description} + +\noindent Anaconda progress design models are stored here. Anaconda +progress design models are described in +\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:Slides}, +\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:Release}, +\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:First}, +\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:Paragraph}, +and \autoref{fig:Distribution:Anaconda:Progress:Identity:Models:List}. + +\begin{figure}[!hbp] +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% +../Identity/Models/Img/en/Distro/Anaconda/Progress/view-1.pdf}} +\end{center} +\caption[Anaconda progress design model]{Anaconda progress design\ +model. A = ``Header'', B = ``Slide rotation'', C =\ +``Action/Navigation''.% + \label{fig:Distribution:Anaconda:Progress:Identity:Models:Slides}} +\end{figure} + +\begin{figure}[!hbp] +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% +../Identity/Models/Img/en/Distro/Anaconda/Progress/view-2.pdf}} +\end{center} +\caption[Anaconda progress release notes]{Anaconda progress release\ +notes. A = ``Release notes'', B = ``Action/Navigation''.% + \label{fig:Distribution:Anaconda:Progress:Identity:Models:Release}} +\end{figure} + + +\begin{figure}[!hbp] +\begin{center} +\includegraphics[width=0.8\textwidth]{% +../Identity/Models/Img/en/Distro/Anaconda/Progress/first.pdf} +\end{center} +\caption[Anaconda progress first slide template]{Anaconda progress\ +first slide template. A = ``The CentOS Symbol'', B = ``The CentOS\ +Default Artistic Motif'', C = ``The CentOS Release Brand'', D = ``The\ +CentOS Copyright''.% + \label{fig:Distribution:Anaconda:Progress:Identity:Models:First}} +\end{figure} + +\begin{figure}[!hbp] +\begin{center} +\includegraphics[width=0.8\textwidth]{% +../Identity/Models/Img/en/Distro/Anaconda/Progress/list.pdf} +\end{center} +\caption{Anaconda progress list template.% + \label{fig:Distribution:Anaconda:Progress:Identity:Models:Paragraph}} +\end{figure} + +\begin{figure}[!hbp] +\begin{center} +\includegraphics[width=0.8\textwidth]{% +../Identity/Models/Img/en/Distro/Anaconda/Progress/paragraph.pdf} +\end{center} +\caption{Anaconda progress paragraph template.% + \label{fig:Distribution:Anaconda:Progress:Identity:Models:List}} +\end{figure} + +% ------------------------------------------------------------ + \subsection{Image Files} +\hypertarget{sec:Distribution:Anaconda:Progress:Identity:Image}{} + \label{sec:Distribution:Anaconda:Progress:Identity:Image} + +\begin{description} +\item[framework:] trunk/Identity/Themes/\$THEME/Distro/Anaconda/Progress/Img/ +\end{description} + +\noindent Anaconda progress final images are stored here. + +% ------------------------------------------------------------ + \subsection{Image Files Rendering} +\hypertarget{sec:Distribution:Anaconda:Progress:Identity:Image:Rendering}{} + \label{sec:Distribution:Anaconda:Progress:Identity:Image:Rendering} + +\begin{description} +\item[framework:] trunk/Identity/Themes/\$THEME/Distro/Anaconda/Progress/ +\end{description} + +\noindent Here is where you produce Anaconda progress slide images. +Take a look at the following rendering examples based on the +translation path shown in +\autoref{fig:Distribution:Anaconda:Progress:Translations}:\\ +\\ +\fbox{\texttt{./render.sh}}\\ +\\ +\fbox{\texttt{./render.sh '5'}}\\ +\\ +\fbox{\texttt{./render.sh '(3|4|5)'}}\\ +\\ +\fbox{\texttt{./render.sh '5/(progress|first|en)'}}\\ +\\ +\fbox{\texttt{./render.sh '(4|5)/(progress|first|en|es)'}}\\ +\\ +\fbox{\texttt{./render.sh '(4|5)/(en|es)/01-welcome'}} + +% ------------------------------------------------------------ + \section{Translations} +\hypertarget{sec:Distribution:Anaconda:Progress:Translations}{} + \label{sec:Distribution:Anaconda:Progress:Translations}{} + +\begin{description} +\item[framework:] trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ +\end{description} + +\noindent Here is where translators locale Anaconda progress +language-specific slide set of images. Anaconda progress translation +framework is illustrated in +\autoref{fig:Distribution:Anaconda:Progress:Translations}. Anaconda +progress translation framework defines the Anaconda progress slide +images translation path. The translation path shown in +\autoref{fig:Distribution:Anaconda:Progress:Translations} is an +incomplet version of the real one. It was cropped in the sake of +keeping it in just one page. To make yourself a better idea of the +real Anaconda progress translation path, check the one inside your +working copy of CentOS Artwork Repository. That is the one you should +use in order to build your REGEX patterns when rendering Anaconda +progress slide images. + +\begin{figure} +\hrulefill +\begin{verbatim} +trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ +|-- 3 +| |-- bn_IN +| | |-- 01-welcome.sed +| | |-- 02-donate.sed +| | |-- 03-yum.sed +| | `-- ... (more bn_IN translation files) +| |-- ... (more language directories) +| |-- first-lowres.sed +| |-- first.sed +| |-- ... (more language directories) +| |-- progress_first-lowres.sed +| |-- progress_first.sed +| `-- ... (more language directories) +|-- 4 +|-- 5 +|-- ... (more release directories) +|-- render.sh +`-- tpl + |-- bn_IN + | |-- 01-welcome.sed + | |-- 02-donate.sed + | |-- 03-yum.sed + | `-- ... (more bn_IN translation files) + |-- ... (more language directories) + |-- first-lowres.sed + |-- first.sed + |-- ... (more language directories) + |-- progress_first-lowres.sed + |-- progress_first.sed + `-- ... (more language directories) +\end{verbatim} +\hrulefill +\caption{Anaconda progress translation framework.% + \label{fig:Distribution:Anaconda:Progress:Translations}} +\end{figure} + +% ------------------------------------------------------------ + \subsection{Translation Markers} +\hypertarget{sec:Distribution:Anaconda:Progress:Translations:Markers}{} + \label{sec:Distribution:Anaconda:Progress:Translations:Markers} + +In Anaconda progress, translation files and design templates use the +translation markers specified in +\autoref{tab:Distribution:Identity:Markers}. + +\begin{table}[!hbp] +\centering +\begin{tabular}{ll} +\hline +\textbf{Marker}& \textbf{Description}\\ +\hline +=TITLE= & Slide's title.\\ +=DESCRIPTION= & Slide's list description.\\ +=TEXT1-12= & Slide's content.\\ +=URL= & Slide's URL.\\ +=COPYRIGHT= & Copyright notice.\\ +=RELEASE= & CentOS Distribution full release number.\\ +=MAJOR\_RELEASE= & CentOS Distribution major release number.\\ +=MINOR\_RELEASE= & CentOS Distribution update release number.\\ +\hline +\end{tabular} +\caption{Anaconda progress translation markers.% + \label{tab:Distribution:Identity:Markers}} +\end{table} + +% ------------------------------------------------------------ + \section{Manuals} +\hypertarget{sec:Distribution:Anaconda:Progress:Manuals}{} + \label{sec:Distribution:Anaconda:Progress:Manuals} + +\begin{description} +\item[framework:] trunk/Manuals/Distribution/Anaconda/Progress/ +\end{description} + +\noindent Anaconda progress documentation files are prepared here. If +you want to help improving Anaconda progress documentation this is +where you need to go. + +% ------------------------------------------------------------ + \section{Scripts} +\hypertarget{sec:Distribution:Anaconda:Progress:Scripts}{} + \label{sec:Distribution:Anaconda:Progress:Scripts} + +\begin{description} +\item[framework:] trunk/Scripts/Config/Identity/Themes/Distro/Anaconda/Progress/ +\end{description} + +\noindent Here is stored the Anaconda progress \texttt{render.conf.sh} +configuration script. To render Anaconda progress slide images +correctly, the \texttt{ARTCOMP} configuration variable inside Anaconda +progress configuration script should be defined as illustrated in +\autoref{fig:Distribution:Anaconda:Progress:Scripts:Config}. + +\begin{figure} +\hrulefill +\begin{verbatim} +# Define artwork component. +ARTCOMP='Distro/Anaconda/Progress' +\end{verbatim} +\hrulefill +\caption{Anaconda progress configuration layout.% + \label{fig:Distribution:Anaconda:Progress:Scripts:Config}} +\end{figure} + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Progress/introduction.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Progress/introduction.tex new file mode 100644 index 0000000..3718297 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Progress/introduction.tex @@ -0,0 +1,18 @@ +% Part: Distribution +% Chapter: Anaconda Progress - Introduction +% ------------------------------------------------------------ +% $Id: introduction.tex 6019 2010-06-26 06:42:08Z al $ +% ------------------------------------------------------------ + +Anaconda progress takes place after configuration screens and while +packages are being installed. Anaconda progress visual style is +controlled by ``\hyperlink{cha:Distribution:Anaconda:Header}{Anaconda +Header}'' (\autoref{cha:Distribution:Anaconda:Header}), Anaconda +progress first slide, and Anaconda progress language-specific slides +set of images. Anaconda progress language-specific slides set of +images start rotating a few seconds after Anaconda progress first +slide. It is possible for the user to alternate between Anaconda +progress slides and CentOS distribution +``\hyperlink{cha:Distribution:ReleaseNotes}{Release Notes}'' +(\autoref{cha:Distribution:ReleaseNotes}). + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Progress/rebranding.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Progress/rebranding.tex new file mode 100644 index 0000000..d964bd3 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Progress/rebranding.tex @@ -0,0 +1,108 @@ +% Part: Distribution +% Chapter: Anaconda Progress - Rebranding +% ------------------------------------------------------------ +% $Id: rebranding.tex 6019 2010-06-26 06:42:08Z al $ +% ------------------------------------------------------------ + +\section{Rebranding} + +\subsection{Package: redhat-logos} + +The \texttt{redhat-logos} package contains files created by the CentOS +Project to replace the Red Hat ``Shadow Man'' logo and RPM logo. The +Red Hat ``Shadow Man'' logo, RPM, and the RPM logo are trademarks or +registered trademarks of Red Hat, Inc. Anaconda Progres images that +need to be rebranded in \texttt{redhat-logos} package are illustrated +in \autoref{fig:Distribution:Anaconda:Progress:Rebranding:Images}. + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +/usr/share/anaconda/pixmaps/ +|-- first-lowres.png +|-- first.png +|-- progress_first-lowres.png +|-- progress_first.png +|-- rnotes +| |-- 01-centos5-welcome.png +| |-- 02-centos5-donate.png +| |-- 03-centos5-yum.png +| |-- 04-centos5-repos.png +| |-- 05-centos5-centosplus.png +| |-- 06-centos5-support.png +| |-- 07-centos5-docs.png +| |-- 08-centos5-wiki.png +| |-- 09-centos5-virtualization.png +| |-- cs +| | |-- 01-centos5-welcome.png +| | |-- 02-centos5-donate.png +| | |-- 03-centos5-yum.png +| | |-- 04-centos5-repos.png +| | |-- 05-centos5-centosplus.png +| | |-- 06-centos5-support.png +| | |-- 07-centos5-docs.png +| | |-- 08-centos5-wiki.png +| | `-- 09-centos5-virtualization.png +| |-- ... (more languages here) +\end{verbatim} +\hrulefill +\caption{Anaconda Progress slide images.% + \label{fig:Distribution:Anaconda:Progress:Rebranding:Images}} +\end{figure} + +Replacements for these files are available in the +\hyperlink{sec:Distribution:Anaconda:Progress:Identity:Image}{Anaconda +Progress image directory} (see +\autoref{sec:Distribution:Anaconda:Progress:Identity:Image}) of +\hyperlink{sec:Distribution:Anaconda:Progress:Identity}{Anaconda +Progress Identity} (see +\autoref{sec:Distribution:Anaconda:Progress:Identity}) inside your +working copy of CentOS Artwork Repository. + +Once you rebrand the image files inside \texttt{redhat-logos} SRPM +package, you need to rebuild it with the new brand information. + +\subsection{Package: centos-release-notes} + +During the installation process Anaconda provides a button labeled +``Release Notes'' (see +\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:Slides}). +When this button is pressed the header and slide areas get hidden and +the available space is used to display CentOS release notes (see +\autoref{fig:Distribution:Anaconda:Progress:Identity:Models:Release}). + +Presently, CentOS release notes are managed online and they don't +appear in Anaconda's release notes screen. A few paragraphs are used +instead to describe how CentOS release notes are managed and how they +can be accessed. + +The \texttt{centos-release-notes} package contains Anaconda Progress +release notes files. Anaconda Progress release notes files are +illustrated in \autoref{fig:Distribution:Anaconda:Progress:Rebranding:ReleaseNotes:Files}. + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +/usr/share/doc/centos-release-notes-5.2/ +|-- RELEASE-NOTES-cs +|-- RELEASE-NOTES-cs.html +|-- RELEASE-NOTES-de +|-- RELEASE-NOTES-de.html +|-- RELEASE-NOTES-en +|-- RELEASE-NOTES-en.html +|-- RELEASE-NOTES-es +|-- RELEASE-NOTES-es.html +`-- ... (more language-specific release notes) +\end{verbatim} +\hrulefill +\caption{Anaconda Progress release notes files.% + \label{fig:Distribution:Anaconda:Progress:Rebranding:ReleaseNotes:Files}} +\end{figure} + +Files in +\autoref{fig:Distribution:Anaconda:Progress:Rebranding:ReleaseNotes:Files} +have their own framework inside CentOS Artwork Repository. Anaconda +Progress release notes are rendered similar to images, using templates +and translation files, as well as rendering scripts. For more +information about release notes rendering see the chapter +``\hyperlink{cha:Distribution:ReleaseNotes}{Release Notes}''. diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/chapter.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/chapter.tex new file mode 100644 index 0000000..90f8ba0 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/chapter.tex @@ -0,0 +1,31 @@ +% part : Distribution +% chapter: Anaconda Prompt +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ + +\section{Identity} +\hypertarget{sec:Distribution:Anaconda:Prompt:Identity}{} +\label{sec:Distribution:Anaconda:Prompt:Identity} +\input{Distribution/Anaconda/Prompt/identity.tex} + +\section{Translations} +\hypertarget{sec:Distribution:Anaconda:Prompt:Translations}{} +\label{sec:Distribution:Anaconda:Prompt:Translations} +\input{Distribution/Anaconda/Prompt/translations.tex} + +\section{Manuals} +\hypertarget{sec:Distribution:Anaconda:Prompt:Manuals}{} +\label{sec:Distribution:Anaconda:Prompt:Manuals} +\input{Distribution/Anaconda/Prompt/manuals.tex} + +\section{Scripts} +\hypertarget{sec:Distribution:Anaconda:Prompt:Scripts}{} +\label{sec:Distribution:Anaconda:Prompt:Scripts} +\input{Distribution/Anaconda/Prompt/scripts.tex} + +\section{Packages} +\hypertarget{sec:Distribution:Anaconda:Prompt:Packages}{} +\label{sec:Distribution:Anaconda:Prompt:Packages} +\input{Distribution/Anaconda/Prompt/packages.tex} + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/identity.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/identity.tex new file mode 100644 index 0000000..37aac96 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/identity.tex @@ -0,0 +1,129 @@ +% Part : Distribution +% Chapter: Anaconda Prompt +% Section: Identity +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +trunk/Identity/Themes/$THEME/Distro/Anaconda/Prompt/ +|-- img +| |-- 3 +| | |-- syslinux-splash-16c.png +| | |-- syslinux-splash-16c.pnm +| | |-- syslinux-splash.log +| | |-- syslinux-splash.lss +| | |-- syslinux-splash.png +| | |-- syslinux-splash.pnm +| | `-- syslinux-splash.ppm +| |-- 4 +| |-- 5 +| `-- ... more major releases +|-- render.sh +`-- tpl + `-- syslinux-splash.svg +\end{verbatim} +\hrulefill +\caption{Anaconda prompt identity's framework.% + \label{fig:Distribution:Anaconda:Prompt:Identity}} +\end{figure} + +\subsection{Designs Templates} +\hypertarget{sec:Distribution:Anaconda:Prompt:Identity:Templates}{} +\label{sec:Distribution:Anaconda:Prompt:Identity:Templates} + +\begin{itemize} +\item trunk/Identity/Themes/\$THEME/Distro/Anaconda/Prompt/tpl +\end{itemize} + +\subsection{Design Models} + +\begin{itemize} +\item trunk/Identity/Models/Tpl/Distro/Anaconda/Prompt/ +\item trunk/Identity/Models/Img/Distro/Anaconda/Prompt/ +\end{itemize} + +\begin{figure}[!hbp] +\begin{center} +\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Models/Img/en/Distro/Anaconda/Prompt/syslinux-splash.pdf} +\end{center} +\caption{Anaconda prompt design model.% + \label{fig:Distribution:Anaconda:Model}} +\end{figure} + +\begin{figure}[!hbp] +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Models/Img/en/Distro/Anaconda/Prompt/fig-1-syslinux-splash.pdf}} +\end{center} +\caption{Anaconda prompt position in the screen.% + \label{fig:Distribution:Anaconda:Prompt:Models:Fig2}} +\end{figure} + +\subsection{Image Files} +\hypertarget{sec:Distribution:Anaconda:Prompt:Identity:Images}{} +\label{sec:Distribution:Anaconda:Prompt:Identity:Images} + +\begin{itemize} +\item \texttt{syslinux-splash.png}: base image format. +\item \texttt{syslinux-splash.ppm}: auxiliar format. +\item \texttt{syslinux-splash.pnm}: auxiliar format. +\item \texttt{syslinux-splash.lss}: image format used by syslinux. +\item \texttt{syslinux-splash-16c.pnm}: 16 colors auxiliar format. +\item \texttt{syslinux-splash-16c.png}: 16 colors auxiliar format. +\item \texttt{syslinux-splash.log}: describes image convertion steps. +\end{itemize} + +\subsection{Image Files Rendering} +\hypertarget{sec:Distribution:Anaconda:Prompt:Identity:Issues}{} +\label{sec:Distribution:Anaconda:Prompt:Identity:Issues} +\fbox{\texttt{./render.sh}} +\fbox{\texttt{./render.sh '5'}} +\fbox{\texttt{./render.sh '(3|4|5)'}} + +\subsection{Color Limitations} +\hypertarget{sec:Distribution:Anaconda:Prompt:Identity:Colors}{} +\label{sec:Distribution:Anaconda:Prompt:Identity:Colors} + +Anaconda Prompt does have color limitations. Initially, Anaconda +Prompt images are rendered without color limitation and later they are +indexed to 16 colors and converted to LSS16 format, as described in +\autoref{sec:Concepts:Identity:Themes:Palettes}. + +\subsection{Issues} +\hypertarget{sec:Distribution:Anaconda:Prompt:Issues}{} +\label{sec:Distribution:Anaconda:Prompt:Issues} + +When creating Anaconda Prompt images some issues were found. They are +described below: + +\begin{itemize} + +\item \textbf{Many Different Colors:} + +As more different colors you have on your design, more are the +possibilities of increasing the amount of noise in your design after +indexing to 16 colors. For example, if you include the actual CentOS +symbol in this image, it ocupies 3 colors (for the orange, green, +violet) in the indexed image which are completely different and +non-reusable in the blue toned background image. + +\item \textbf{The CentOS Symbol:} + +As previously said, if we include the CentOS default symbol in +Anaconda Prompt there is a color degradation and a reduction of +available colors to use in the 16 colors indexed image. + +Some tests were made with variants of CentOS default symbol, but they +all were declined because they bring confusion about which is the +CentOS default symbol. + +It would be very convenient to CentOS visual identity if the CentOS +default symbol could be included, \textit{exactly as it is}, in +Anaconda Prompt images. + +\end{itemize} + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/manuals.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/manuals.tex new file mode 100644 index 0000000..ae24120 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/manuals.tex @@ -0,0 +1,9 @@ +% Part : Distribution +% Chapter: Anaconda Prompt +% Section: Manuals +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ +\begin{itemize} +\item trunk/Manuals/Identity/Themes/Distro/Anaconda/Prompt/ +\end{itemize} diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/packages.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/packages.tex new file mode 100644 index 0000000..e3078fb --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/packages.tex @@ -0,0 +1,25 @@ +% Part : Distribution +% Chapter: Anaconda Prompt +% Section: Packages +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ + +\begin{itemize} + +\item \textbf{redhat-logos} + +\begin{itemize} +\item /usr/lib/anaconda-runtime/boot/syslinux-splash.png +\item /usr/share/anaconda/pixmaps/syslinux-splash.png +\end{itemize} + +\item \textbf{syslinux} + +\begin{itemize} +\item /isolinux/splash.lss +\end{itemize} +\end{itemize} + +Anaconda Prompt doesn't have messages locale. + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/scripts.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/scripts.tex new file mode 100644 index 0000000..c8e28f1 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/scripts.tex @@ -0,0 +1,9 @@ +% Part : Distribution +% Chapter: Anaconda Prompt +% Section: Scripts +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ +\begin{itemize} +\item trunk/Scripts/Identity/Themes/Distro/Anaconda/Prompt/ +\end{itemize} diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/translations.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/translations.tex new file mode 100644 index 0000000..8e902b1 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Prompt/translations.tex @@ -0,0 +1,33 @@ +% Part : Distribution +% Chapter: Anaconda Prompt +% Section: Translations +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +trunk/Translations/Identity/Themes/Distro/Anaconda/Prompt/ +|-- 3 +| `-- syslinux-splash.sed +|-- 4 +|-- 5 +|-- ... more major releases +|-- render.sh +`-- tpl + `-- syslinux-splash.sed +\end{verbatim} +\hrulefill +\caption{Anaconda prompt translation framework.% + \label{fig:Distribution:Anaconda:Prompt:Translations}} +\end{figure} + +% ------------------------------------------------------------ +\subsection{Translation Markers} +\hypertarget{sec:Distribution:Anaconda:Prompt:Translations:Markers}{} +\label{sec:Distribution:Anaconda:Prompt:Translations:Markers} + +\begin{itemize} +\item \texttt{=VERSION=}: Major release number of CentOS Distribution. +\end{itemize} + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/chapter.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/chapter.tex new file mode 100644 index 0000000..085965e --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/chapter.tex @@ -0,0 +1,29 @@ +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ + +\section{Identity} +\hypertarget{sec:Distribution:Anaconda:Splash:Identity}{} +\label{sec:Distribution:Anaconda:Splash:Identity} +\input{Distribution/Anaconda/Splash/identity.tex} + +\section{Translations} +\hypertarget{sec:Distribution:Anaconda:Splash:Translations}{} +\label{sec:Distribution:Anaconda:Splash:Translations} +\input{Distribution/Anaconda/Splash/translations.tex} + +\section{Manuals} +\hypertarget{sec:Distribution:Anaconda:Splash:Manuals}{} +\label{sec:Distribution:Anaconda:Splash:Manuals} +\input{Distribution/Anaconda/Splash/manuals.tex} + +\section{Scripts} +\hypertarget{sec:Distribution:Anaconda:Splash:Scripts}{} +\label{sec:Distribution:Anaconda:Splash:Scripts} +\input{./Distribution/Anaconda/Splash/scripts.tex} + +\section{Packages} +\hypertarget{sec:Distribution:Anaconda:Splash:Packages}{} +\label{sec:Distribution:Anaconda:Splash:Packages} +\input{Distribution/Anaconda/Splash/packages.tex} + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/identity.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/identity.tex new file mode 100644 index 0000000..0a44087 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/identity.tex @@ -0,0 +1,76 @@ +% Part : Distribution +% Chapter: Anaconda Splash +% Section: Identity +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +trunk/Identity/Themes/$THEME/Distro/Anaconda/Splash/ +|-- img +| |-- 3 +| | |-- splash.png.png +| |-- 4 +| |-- 5 +| `-- ... more major releases +|-- render.sh +`-- tpl + `-- splash.png.svg +\end{verbatim} +\hrulefill +\caption{Anaconda splash identity's framework.% + \label{fig:Distribution:Anaconda:Splash:Identity}} +\end{figure} + +\subsection{Designs Templates} +\hypertarget{sec:Distribution:Anaconda:Splash:Identity:Templates}{} +\label{sec:Distribution:Anaconda:Splash:Identity:Templates} + +\begin{itemize} +\item trunk/Identity/Themes/\$THEME/Distro/Anaconda/Splash/tpl +\end{itemize} + +\subsection{Design Models} + +\begin{itemize} +\item trunk/Identity/Models/Tpl/Distro/Anaconda/Splash/ +\item trunk/Identity/Models/Img/Distro/Anaconda/Splash/ +\end{itemize} + +\begin{figure}[!hbp] +\begin{center} +\fbox{\includegraphics[width=0.8\textwidth]{% + /home/centos/artwork/trunk/Identity/Models/Img/en/Distro/Anaconda/Splash/splash.pdf}} +\end{center} +\caption{Anaconda splash design model.% + \label{fig:Distribution:Anaconda:Splash:Models:Fig1}} +\end{figure} + +\subsection{Image Files} +\hypertarget{sec:Distribution:Anaconda:Splash:Identity:Images}{} +\label{sec:Distribution:Anaconda:Splash:Identity:Images} + +\begin{itemize} +\item \texttt{splash.png}: base image format. +\end{itemize} + +\subsection{Image Files Rendering} +\hypertarget{sec:Distribution:Anaconda:Splash:Identity:Issues}{} +\label{sec:Distribution:Anaconda:Splash:Identity:Issues} +\fbox{\texttt{./render.sh}} +\fbox{\texttt{./render.sh '5'}} +\fbox{\texttt{./render.sh '(3|4|5)'}} + +\subsection{Color Limitations} +\hypertarget{sec:Distribution:Anaconda:Splash:Identity:Colors}{} +\label{sec:Distribution:Anaconda:Splash:Identity:Colors} + +Anaconda Splash does not have color limitations. + +\subsection{Issues} +\hypertarget{sec:Distribution:Anaconda:Splash:Issues}{} +\label{sec:Distribution:Anaconda:Splash:Issues} + +No one known. diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/manuals.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/manuals.tex new file mode 100644 index 0000000..ccc01bb --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/manuals.tex @@ -0,0 +1,10 @@ +% Part : Distribution +% Chapter: Anaconda Splash +% Section: Scripts +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ +\begin{itemize} +\item trunk/Manuals/Identity/Themes/Distro/Anaconda/Splash/ +\end{itemize} + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/packages.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/packages.tex new file mode 100644 index 0000000..37ddf15 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/packages.tex @@ -0,0 +1,9 @@ +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ +\begin{itemize} +\item \texttt{redhat-logo} +\begin{itemize} +\item /usr/share/anaconda/pixmaps/splash.png +\end{itemize} +\end{itemize} diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/scripts.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/scripts.tex new file mode 100644 index 0000000..2c93f52 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/scripts.tex @@ -0,0 +1,9 @@ +% Part : Distribution +% Chapter: Anaconda Splash +% Section: Scripts +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ +\begin{itemize} +\item trunk/Scripts/Identity/Themes/Distro/Anaconda/Splash/ +\end{itemize} diff --git a/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/translations.tex b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/translations.tex new file mode 100644 index 0000000..cbf3aac --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Anaconda/Splash/translations.tex @@ -0,0 +1,30 @@ +% ------------------------------------------------------------ +% $Id$ +% ------------------------------------------------------------ +\begin{figure} +\hrulefill +\begin{verbatim} +trunk/Translations/Identity/Themes/Distro/Anaconda/Splash/ +|-- 3 +| `-- anaconda_splash.sed +|-- 4 +|-- 5 +|-- ... more major releases +|-- render.sh +`-- tpl + `-- anaconda_splash.sed +\end{verbatim} +\hrulefill +\caption{Anaconda splash translation framework.% + \label{fig:Distribution:Anaconda:Splash:Translations}} +\end{figure} + +% ------------------------------------------------------------ +\subsection{Translation Markers} +\hypertarget{sec:Distribution:Anaconda:Splash:Translations:Markers}{} +\label{sec:Distribution:Anaconda:Splash:Translations:Markers} + +\begin{itemize} +\item \texttt{=VERSION=}: Major release number of CentOS distribution. +\end{itemize} + diff --git a/Manuals/Repository/filesystem-latex/Distribution/Backgrounds/introduction.tex b/Manuals/Repository/filesystem-latex/Distribution/Backgrounds/introduction.tex new file mode 100644 index 0000000..459d5b8 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Distribution/Backgrounds/introduction.tex @@ -0,0 +1,89 @@ +The Backgrounds directory is probably the Themes' core compoent. +Inside Backgrounds/ directory you produce background images that are +reused by almost all theme's art works (e.g., Distribution, Websites, +Promotion, etc.). + +The Backgrounds/ directory structure can contain directories to help +you organize the design process. + + Img/: In this directory is where you store all background images + (e.g., .png, .jpg, .xpm, etc.). This directory is required + by rendering scripts. + + Tpl/: In this directory is where you store all scalable vector + graphics (e.g., .svg) files. This directory is required by + rendering scripts. + + Xcf/: In this directory is where you store all Gimp's project + files (e.g, .xcf). This directory is optional. If you can + create a beautiful background images using scalable vector + graphics only, then there is no need to use Gimp to produce + background images. Of course, you can merge Gimp's power + with Inkscape's power to produce images based on them. In + this last case you need this directory. + +Inside Backgrounds/ you can create your vectorial designs using +Inkscape and your background images using Gimp. Later you can export +your background image as png and load it in your vectorial design +using Inkscape's import feautre. Note that 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 \textit{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. + diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.aux new file mode 100644 index 0000000..a75eddf --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.aux @@ -0,0 +1,102 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{3}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Installation}{3}{section.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Subversion}{3}{subsection.2.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}ImageMagick}{4}{subsection.2.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{5}{subsection.2.6}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Configuration}{6}{section.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{8}{subsubsection.3.4.1}} +\newlabel{sec:Configuration:Account}{{3.4.1}{8}{Account Registration\relax }{subsubsection.3.4.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2}} +\newlabel{sec:Configuration:User:Privileges}{{3.4.2}{9}{Account Privileges\relax }{subsubsection.3.4.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5}} +\newlabel{sec:Configuration:Environment}{{3.5}{9}{Shell Environment\relax }{subsection.3.5}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Framework}{10}{section.4}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3}} +\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Firstboot translation markers.}}{12}{table.1}} +\newlabel{tab:Identity:Markers}{{1}{12}{Markers\relax }{table.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.4}Images}{12}{subsubsection.4.1.4}} +\newlabel{sec:Identity:Images}{{4.1.4}{12}{Images\relax }{subsubsection.4.1.4}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.5}Models}{12}{subsubsection.4.1.5}} +\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Firstboot design model.}}{13}{figure.1}} +\newlabel{fig:Identity:Design:Model}{{1}{13}{Models\relax }{figure.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.6}Rendering}{14}{subsubsection.4.1.6}} +\newlabel{sec:Identity:Rendering}{{4.1.6}{14}{Rendering\relax }{subsubsection.4.1.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.2}Translations}{14}{subsection.4.2}} +\newlabel{sec:Translations}{{4.2}{14}{Translations\relax }{subsection.4.2}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{15}{subsubsection.4.2.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{15}{subsubsection.4.2.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{15}{subsubsection.4.2.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}Manuals}{16}{subsection.4.3}} +\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces Firstboot translation path.}}{16}{figure.2}} +\newlabel{fig:Translation:Path}{{2}{16}{Translation Path\relax }{figure.2}{}} +\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Rendering design model.}}{17}{figure.3}} +\newlabel{fig:Scripts:Rendering}{{3}{17}{Rendering\relax }{figure.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Scripts}{17}{subsection.4.4}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{17}{subsubsection.4.4.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{18}{subsubsection.4.4.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{18}{subsubsection.4.4.3}} +\@writefile{toc}{\contentsline {section}{\numberline {5}Rebranding}{18}{section.5}} +\newlabel{sec:Rebranding}{{5}{18}{Rebranding\relax }{section.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}Images}{19}{subsection.5.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{19}{subsubsection.5.1.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.1.2}redhat-artwork}{19}{subsubsection.5.1.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Messages Locale}{20}{subsection.5.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.2.1}firstboot}{20}{subsubsection.5.2.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.2.2}firstboot-tui}{20}{subsubsection.5.2.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {5.3}License Agreement}{20}{subsection.5.3}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.3.1}centos-release}{20}{subsubsection.5.3.1}} +\@writefile{toc}{\contentsline {section}{\numberline {6}GNU Free Documentation License}{21}{section.6}} +\newlabel{sec:License-GFDL-0}{{6}{22}{Preamble\relax }{section*.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{22}{subsection.6.1}} +\newlabel{sec:License-GFDL-1}{{6.1}{22}{Applicability And Definitions\relax }{subsection.6.1}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{24}{subsection.6.2}} +\newlabel{sec:License-GFDL-2}{{6.2}{24}{Verbatim Copying\relax }{subsection.6.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{24}{subsection.6.3}} +\newlabel{sec:License-GFDL-3}{{6.3}{24}{Copying In Quantity\relax }{subsection.6.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.4}Modifications}{25}{subsection.6.4}} +\newlabel{sec:License-GFDL-4}{{6.4}{25}{Modifications\relax }{subsection.6.4}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.5}Combining Documents}{28}{subsection.6.5}} +\newlabel{sec:License-GFDL-5}{{6.5}{28}{Combining Documents\relax }{subsection.6.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{28}{subsection.6.6}} +\newlabel{sec:License-GFDL-6}{{6.6}{28}{Collections Of Documents\relax }{subsection.6.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{28}{subsection.6.7}} +\newlabel{sec:License-GFDL-7}{{6.7}{28}{Aggregation With Independent Works\relax }{subsection.6.7}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.8}Translation}{29}{subsection.6.8}} +\newlabel{sec:License-GFDL-8}{{6.8}{29}{Translation\relax }{subsection.6.8}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.9}Termination}{29}{subsection.6.9}} +\newlabel{sec:License-GFDL-9}{{6.9}{29}{Termination\relax }{subsection.6.9}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{30}{subsection.6.10}} +\newlabel{sec:License-GFDL-10}{{6.10}{30}{Future Revisions Of This License\relax }{subsection.6.10}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{30}{subsection.6.11}} +\newlabel{sec:License-GFDL-11}{{6.11}{30}{How to use this License for your documents\relax }{subsection.6.11}{}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.log new file mode 100644 index 0000000..6ca2c6b --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.log @@ -0,0 +1,352 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 31 MAR 2010 11:07 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size12.clo +File: size12.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/graphics/graphicx.sty +Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks14 +) +(/usr/share/texmf/tex/latex/graphics/graphics.sty +Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/trig.sty +Package: trig 1999/03/16 v1.09 sin cos tan (DPC) +) +(/usr/share/texmf/tex/latex/graphics/graphics.cfg +File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive +) +Package graphics Info: Driver file: pdftex.def on input line 80. + +(/usr/share/texmf/tex/latex/graphics/pdftex.def +File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex +\Gread@gobject=\count87 +)) +\Gin@req@height=\dimen103 +\Gin@req@width=\dimen104 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX +\@linkdim=\dimen105 +\Hy@linkcounter=\count88 +\Hy@pagecounter=\count89 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count90 +\Field@Width=\dimen106 +\Fld@charsize=\dimen107 +\Choice@toks=\toks15 +\Field@toks=\toks16 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count91 +\c@Hfootnote=\count92 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count93 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 16. +LaTeX Font Info: ... okay on input line 16. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 16. +LaTeX Font Info: ... okay on input line 16. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 16. +LaTeX Font Info: ... okay on input line 16. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 16. +LaTeX Font Info: ... okay on input line 16. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 16. +LaTeX Font Info: ... okay on input line 16. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 16. +LaTeX Font Info: ... okay on input line 16. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 16. +LaTeX Font Info: ... okay on input line 16. + +(/usr/share/texmf/tex/context/base/supp-pdf.tex +(/usr/share/texmf/tex/context/base/supp-mis.tex +loading : Context Support Macros / Miscellaneous (2004.10.26) +\protectiondepth=\count94 +\scratchcounter=\count95 +\scratchtoks=\toks17 +\scratchdimen=\dimen108 +\scratchskip=\skip43 +\scratchmuskip=\muskip11 +\scratchbox=\box26 +\scratchread=\read1 +\scratchwrite=\write4 +\zeropoint=\dimen109 +\onepoint=\dimen110 +\onebasepoint=\dimen111 +\minusone=\count96 +\thousandpoint=\dimen112 +\onerealpoint=\dimen113 +\emptytoks=\toks18 +\nextbox=\box27 +\nextdepth=\dimen114 +\everyline=\toks19 +\!!counta=\count97 +\!!countb=\count98 +\recursecounter=\count99 +) +loading : Context Support Macros / PDF (2004.03.26) +\nofMPsegments=\count100 +\nofMParguments=\count101 +\MPscratchCnt=\count102 +\MPscratchDim=\dimen115 +\MPnumerator=\count103 +\everyMPtoPDFconversion=\toks20 +) +Package hyperref Info: Link coloring OFF on input line 16. + (/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count104 +) +LaTeX Info: Redefining \ref on input line 16. +LaTeX Info: Redefining \pageref on input line 16. + (./Manual.out) +(./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <14.4> on input line 19. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 19. +LaTeX Font Info: Try loading font information for OMS+cmr on input line 29. + (/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10.95> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 29. + (./Manual.toc +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 3. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 3. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 3. + +[1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] [2]) +\tf@toc=\write5 +\openout5 = `Manual.toc'. + + +(./sections/introduction.tex) (../../../../../installation.tex +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 25. + [3] +Overfull \hbox (8.37456pt too wide) in paragraph at lines 53--54 +[][]$\OT1/cmtt/m/n/12 http : / / wiki . centos . org / AdditionalResources / Re +positories$[] + [] + +Missing character: There is no � in font cmr12! +Missing character: There is no � in font cmr12! +[4] +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <12> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 94. + [5]) (../../../../../configuration.tex [6] +Overfull \hbox (11.3752pt too wide) in paragraph at lines 64--64 +[]\OT1/cmtt/m/n/12 # Squid only knows about standardized HTTP request met +hods.[] + [] + + +Overfull \hbox (11.3752pt too wide) in paragraph at lines 64--64 +[]\OT1/cmtt/m/n/12 # You can add up to 20 additional "extension" methods +here.[] + [] + +[7] +Overfull \hbox (23.88292pt too wide) in paragraph at lines 96--97 +[]\OT1/cmtt/m/n/12 svn co https://projects.centos.org/svn/artwork $\OMS/cmsy/m/ +n/12 ^^X$\OT1/cmtt/m/n/12 /Desktop/ + [] + +[8] +Overfull \hbox (32.24086pt too wide) in paragraph at lines 161--168 +\OT1/cmr/m/n/12 CentOS Art-work Repos-i-tory, we de-cided to de-fine the \OT1/c +mr/bx/n/12 CentOS[]ARTWORK[]WC + [] + +[9]) (./sections/framework.tex +Underfull \hbox (badness 10000) in paragraph at lines 9--10 + + [] + + +Underfull \hbox (badness 10000) in paragraph at lines 16--17 + + [] + +[10] +Overfull \hbox (15.76491pt too wide) in paragraph at lines 63--68 +\OT1/cmr/m/n/12 ex-ported as PNG im-age. As con-ven-tion, we use the word `CENT +OSARTWORK' + [] + +[11] +Underfull \hbox (badness 10000) in paragraph at lines 104--105 + + [] + + +Underfull \hbox (badness 10000) in paragraph at lines 117--118 + + [] + + +<../../../../../../Identity/Models/Distro/Anaconda/Firstboot/img/build-0.pdf, i +d=416, 642.4pt x 481.8pt> +File: ../../../../../../Identity/Models/Distro/Anaconda/Firstboot/img/build-0.p +df Graphic file (type pdf) + + [12] [13 <../../../../../../Identity/Models/Distro/Anaconda/Firstboot/img/bu +ild-0.pdf>] +Underfull \hbox (badness 10000) in paragraph at lines 180--181 + + [] + +[14] [15] +Underfull \hbox (badness 10000) in paragraph at lines 269--270 + + [] + +[16] +<../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf, id=458, 5 +28.97626pt x 519.9425pt> +File: ../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf Graph +ic file (type pdf) + + +Underfull \hbox (badness 10000) in paragraph at lines 297--298 + + [] + +[17 <../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf>]) +(./sections/rebranding.tex +Overfull \hbox (2.56557pt too wide) in paragraph at lines 13--16 +[]\OT1/cmr/m/n/12 CentOS Brands and art-works are or-ga-nized in-side CentOS Ar +t-work Repos- + [] + +[18] [19] [20]) (../../../../../Licenses/GFDL.tex +Underfull \hbox (badness 10000) in paragraph at lines 5--14 + + [] + +[21] [22] [23] [24] [25] [26] [27] [28] [29] +Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 document under the terms of the GNU Free Documentation Li +cense,[] + [] + + +Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 Version 1.2 or any later version published by the Free So +ftware[] + [] + + +Overfull \hbox (5.2002pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 Foundation; with no Invariant Sections, no Front-Cover Te +xts,[] + [] + + +Overfull \hbox (11.3752pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 and no Back-Cover Texts. A copy of the license is includ +ed in[] + [] + + +Overfull \hbox (5.2002pt too wide) in paragraph at lines 425--425 +[] \OT1/cmtt/m/n/12 with the Invariant Sections being LIST THEIR TITLES, with + the[] + [] + +) [30] [31] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 2822 strings out of 94500 + 38867 string characters out of 1176766 + 89311 words of memory out of 1000000 + 5861 multiletter control sequences out of 10000+50000 + 11008 words of font info for 39 fonts, out of 500000 for 2000 + 582 hyphenation exceptions out of 1000 + 27i,8n,36p,222b,267s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 540 PDF objects out of 300000 + 108 named destinations out of 131072 + 523 words of extra memory for PDF output out of 65536 + +Output written on Manual.pdf (31 pages, 274955 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.out new file mode 100644 index 0000000..f51c4dd --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.out @@ -0,0 +1,62 @@ +\BOOKMARK [1][-]{section.1}{Introduction}{} +\BOOKMARK [1][-]{section.2}{Installation}{} +\BOOKMARK [2][-]{subsection.2.1}{Subversion}{section.2} +\BOOKMARK [2][-]{subsection.2.2}{Inkscape}{section.2} +\BOOKMARK [2][-]{subsection.2.3}{ImageMagick}{section.2} +\BOOKMARK [2][-]{subsection.2.4}{Netpbm}{section.2} +\BOOKMARK [2][-]{subsection.2.5}{Syslinux}{section.2} +\BOOKMARK [2][-]{subsection.2.6}{GNU Image Manipulation Program}{section.2} +\BOOKMARK [2][-]{subsection.2.7}{GNU Core Utilities}{section.2} +\BOOKMARK [2][-]{subsection.2.8}{LaTeX}{section.2} +\BOOKMARK [1][-]{section.3}{Configuration}{} +\BOOKMARK [2][-]{subsection.3.1}{Firewall}{section.3} +\BOOKMARK [2][-]{subsection.3.2}{Subversion Behind Squid}{section.3} +\BOOKMARK [3][-]{subsubsection.3.2.1}{Subversion Client Configuration}{subsection.3.2} +\BOOKMARK [3][-]{subsubsection.3.2.2}{Squid Server Configuration}{subsection.3.2} +\BOOKMARK [2][-]{subsection.3.3}{Working Copy}{section.3} +\BOOKMARK [2][-]{subsection.3.4}{User Identification}{section.3} +\BOOKMARK [3][-]{subsubsection.3.4.1}{Account Registration}{subsection.3.4} +\BOOKMARK [3][-]{subsubsection.3.4.2}{Account Privileges}{subsection.3.4} +\BOOKMARK [2][-]{subsection.3.5}{Shell Environment}{section.3} +\BOOKMARK [3][-]{subsubsection.3.5.1}{Relative Paths}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.2}{Absolute Paths}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.3}{Environment Variable Definition}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.4}{Environment Variable Initialization}{subsection.3.5} +\BOOKMARK [1][-]{section.4}{Framework}{} +\BOOKMARK [2][-]{subsection.4.1}{Identity}{section.4} +\BOOKMARK [3][-]{subsubsection.4.1.1}{Designs}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.2}{Export Id}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.3}{Markers}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.4}{Images}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.5}{Models}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.6}{Rendering}{subsection.4.1} +\BOOKMARK [2][-]{subsection.4.2}{Translations}{section.4} +\BOOKMARK [3][-]{subsubsection.4.2.1}{Common Translations}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.2}{Specific Translations}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.3}{Translation Path}{subsection.4.2} +\BOOKMARK [2][-]{subsection.4.3}{Manuals}{section.4} +\BOOKMARK [2][-]{subsection.4.4}{Scripts}{section.4} +\BOOKMARK [3][-]{subsubsection.4.4.1}{Rendering}{subsection.4.4} +\BOOKMARK [3][-]{subsubsection.4.4.2}{Pre-rendering}{subsection.4.4} +\BOOKMARK [3][-]{subsubsection.4.4.3}{Post-rendering}{subsection.4.4} +\BOOKMARK [1][-]{section.5}{Rebranding}{} +\BOOKMARK [2][-]{subsection.5.1}{Images}{section.5} +\BOOKMARK [3][-]{subsubsection.5.1.1}{redhat-logos}{subsection.5.1} +\BOOKMARK [3][-]{subsubsection.5.1.2}{redhat-artwork}{subsection.5.1} +\BOOKMARK [2][-]{subsection.5.2}{Messages Locale}{section.5} +\BOOKMARK [3][-]{subsubsection.5.2.1}{firstboot}{subsection.5.2} +\BOOKMARK [3][-]{subsubsection.5.2.2}{firstboot-tui}{subsection.5.2} +\BOOKMARK [2][-]{subsection.5.3}{License Agreement}{section.5} +\BOOKMARK [3][-]{subsubsection.5.3.1}{centos-release}{subsection.5.3} +\BOOKMARK [1][-]{section.6}{GNU Free Documentation License}{} +\BOOKMARK [2][-]{subsection.6.1}{Applicability And Definitions}{section.6} +\BOOKMARK [2][-]{subsection.6.2}{Verbatim Copying}{section.6} +\BOOKMARK [2][-]{subsection.6.3}{Copying In Quantity}{section.6} +\BOOKMARK [2][-]{subsection.6.4}{Modifications}{section.6} +\BOOKMARK [2][-]{subsection.6.5}{Combining Documents}{section.6} +\BOOKMARK [2][-]{subsection.6.6}{Collections Of Documents}{section.6} +\BOOKMARK [2][-]{subsection.6.7}{Aggregation With Independent Works}{section.6} +\BOOKMARK [2][-]{subsection.6.8}{Translation}{section.6} +\BOOKMARK [2][-]{subsection.6.9}{Termination}{section.6} +\BOOKMARK [2][-]{subsection.6.10}{Future Revisions Of This License}{section.6} +\BOOKMARK [2][-]{subsection.6.11}{How to use this License for your documents}{section.6} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.pdf new file mode 100644 index 0000000..a1f66d8 Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.toc new file mode 100644 index 0000000..b7d919a --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/Manual.toc @@ -0,0 +1,62 @@ +\contentsline {section}{\numberline {1}Introduction}{3}{section.1} +\contentsline {section}{\numberline {2}Installation}{3}{section.2} +\contentsline {subsection}{\numberline {2.1}Subversion}{3}{subsection.2.1} +\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2} +\contentsline {subsection}{\numberline {2.3}ImageMagick}{4}{subsection.2.3} +\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4} +\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5} +\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{5}{subsection.2.6} +\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7} +\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8} +\contentsline {section}{\numberline {3}Configuration}{6}{section.3} +\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1} +\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2} +\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1} +\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2} +\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3} +\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4} +\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{8}{subsubsection.3.4.1} +\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2} +\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5} +\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1} +\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2} +\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3} +\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4} +\contentsline {section}{\numberline {4}Framework}{10}{section.4} +\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1} +\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1} +\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2} +\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3} +\contentsline {subsubsection}{\numberline {4.1.4}Images}{12}{subsubsection.4.1.4} +\contentsline {subsubsection}{\numberline {4.1.5}Models}{12}{subsubsection.4.1.5} +\contentsline {subsubsection}{\numberline {4.1.6}Rendering}{14}{subsubsection.4.1.6} +\contentsline {subsection}{\numberline {4.2}Translations}{14}{subsection.4.2} +\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{15}{subsubsection.4.2.1} +\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{15}{subsubsection.4.2.2} +\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{15}{subsubsection.4.2.3} +\contentsline {subsection}{\numberline {4.3}Manuals}{16}{subsection.4.3} +\contentsline {subsection}{\numberline {4.4}Scripts}{17}{subsection.4.4} +\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{17}{subsubsection.4.4.1} +\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{18}{subsubsection.4.4.2} +\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{18}{subsubsection.4.4.3} +\contentsline {section}{\numberline {5}Rebranding}{18}{section.5} +\contentsline {subsection}{\numberline {5.1}Images}{19}{subsection.5.1} +\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{19}{subsubsection.5.1.1} +\contentsline {subsubsection}{\numberline {5.1.2}redhat-artwork}{19}{subsubsection.5.1.2} +\contentsline {subsection}{\numberline {5.2}Messages Locale}{20}{subsection.5.2} +\contentsline {subsubsection}{\numberline {5.2.1}firstboot}{20}{subsubsection.5.2.1} +\contentsline {subsubsection}{\numberline {5.2.2}firstboot-tui}{20}{subsubsection.5.2.2} +\contentsline {subsection}{\numberline {5.3}License Agreement}{20}{subsection.5.3} +\contentsline {subsubsection}{\numberline {5.3.1}centos-release}{20}{subsubsection.5.3.1} +\contentsline {section}{\numberline {6}GNU Free Documentation License}{21}{section.6} +\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{22}{subsection.6.1} +\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{24}{subsection.6.2} +\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{24}{subsection.6.3} +\contentsline {subsection}{\numberline {6.4}Modifications}{25}{subsection.6.4} +\contentsline {subsection}{\numberline {6.5}Combining Documents}{28}{subsection.6.5} +\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{28}{subsection.6.6} +\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{28}{subsection.6.7} +\contentsline {subsection}{\numberline {6.8}Translation}{29}{subsection.6.8} +\contentsline {subsection}{\numberline {6.9}Termination}{29}{subsection.6.9} +\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{30}{subsection.6.10} +\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{30}{subsection.6.11} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/manual.tex new file mode 100644 index 0000000..cf74a63 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Firstboot/manual.tex @@ -0,0 +1,49 @@ +\documentclass[12pt]{article} +\usepackage[pdftex]{graphicx} +\usepackage{hyperref} +\hypersetup{pdfauthor={Alain Reguera Delgado},% + pdftitle={Firstboot Visual Style},% + pdfsubject={CentOS Corporate Visual Identity}% + } + +% Tell LaTeX how to hyphenate a word. Don't hyphenate the following +% words: +\hyphenation{CentOS CENTOSARTWORK} + +\title{Firstboot Visual Style} +\author{Alain Reguera Delgado} + +\begin{document} + +\maketitle + +\begin{abstract} + +This article describes the visual style of CentOS firstboot +(1.4.27.3-1.el5.centos). Firstboot is the initial system configuration +utility that guides you through a series of steps for easier +configuration of the machine (keyboard layout, language, time zone, +etc.). Firstboot takes place the first time you boot up your installed +system. + +Copyright \copyright\ 2010 The CentOS Project. Permission is granted +to copy, distribute and/or modify this document under the terms of the +GNU Free Documentation License, Version 1.2 or any later version +published by the Free Software Foundation; with no Invariant Sections, +no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled ``GNU Free Documentation +License''. + +\end{abstract} + +\tableofcontents + +\input{sections/introduction.tex} +\input{../../../../../installation.tex} +\input{../../../../../configuration.tex} +\input{sections/framework.tex} +\input{sections/rebranding.tex} + +\input{../../../../../Licenses/GFDL.tex} + +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.aux new file mode 100644 index 0000000..2213323 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.aux @@ -0,0 +1,100 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{3}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Installation}{3}{section.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Subversion}{3}{subsection.2.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}ImageMagick}{4}{subsection.2.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{5}{subsection.2.6}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{5}{subsection.2.7}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Configuration}{6}{section.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{6}{subsection.3.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{6}{subsubsection.3.2.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{8}{subsubsection.3.4.1}} +\newlabel{sec:Configuration:Account}{{3.4.1}{8}{Account Registration\relax }{subsubsection.3.4.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{8}{subsubsection.3.4.2}} +\newlabel{sec:Configuration:User:Privileges}{{3.4.2}{8}{Account Privileges\relax }{subsubsection.3.4.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5}} +\newlabel{sec:Configuration:Environment}{{3.5}{9}{Shell Environment\relax }{subsection.3.5}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{9}{subsubsection.3.5.4}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Framework}{10}{section.4}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1}} +\newlabel{sec:Identity}{{4.1}{10}{Identity\relax }{subsection.4.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1}} +\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Anaconda Header translation markers.}}{11}{table.1}} +\newlabel{tab:Identity:Markers}{{1}{11}{Markers\relax }{table.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.4}Images}{11}{subsubsection.4.1.4}} +\newlabel{sec:Identity:Images}{{4.1.4}{11}{Images\relax }{subsubsection.4.1.4}{}} +\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Anaconda Header design model. A = 800 pixels, B = 48 pixels, C = 88 pixels.}}{12}{figure.1}} +\newlabel{fig:Identity:Design:Model0}{{1}{12}{Models\relax }{figure.1}{}} +\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces Anaconda Header left side. A = 20 pixels.}}{12}{figure.2}} +\newlabel{fig:Identity:Design:Model1}{{2}{12}{Models\relax }{figure.2}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.5}Models}{12}{subsubsection.4.1.5}} +\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Anaconda Header right side. A = 20 pixels.}}{12}{figure.3}} +\newlabel{fig:Identity:Design:Model2}{{3}{12}{Models\relax }{figure.3}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.6}Rendering}{13}{subsubsection.4.1.6}} +\newlabel{sec:Identity:Rendering}{{4.1.6}{13}{Rendering\relax }{subsubsection.4.1.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.2}Translations}{13}{subsection.4.2}} +\newlabel{sec:Translations}{{4.2}{13}{Translations\relax }{subsection.4.2}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{13}{subsubsection.4.2.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{13}{subsubsection.4.2.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{14}{subsubsection.4.2.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}Manuals}{14}{subsection.4.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Scripts}{15}{subsection.4.4}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{15}{subsubsection.4.4.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{15}{subsubsection.4.4.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{15}{subsubsection.4.4.3}} +\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces Rendering design model.}}{16}{figure.4}} +\newlabel{fig:Scripts:Rendering}{{4}{16}{Rendering\relax }{figure.4}{}} +\@writefile{toc}{\contentsline {section}{\numberline {5}Rebranding}{17}{section.5}} +\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}Images}{17}{subsection.5.1}} +\newlabel{sec:Rebranding:Images}{{5.1}{17}{Images\relax }{subsection.5.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{17}{subsubsection.5.1.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Messages Locale}{17}{subsection.5.2}} +\@writefile{toc}{\contentsline {section}{\numberline {6}GNU Free Documentation License}{18}{section.6}} +\newlabel{sec:License-GFDL-0}{{6}{18}{Preamble\relax }{section*.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{18}{subsection.6.1}} +\newlabel{sec:License-GFDL-1}{{6.1}{18}{Applicability And Definitions\relax }{subsection.6.1}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{20}{subsection.6.2}} +\newlabel{sec:License-GFDL-2}{{6.2}{20}{Verbatim Copying\relax }{subsection.6.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{21}{subsection.6.3}} +\newlabel{sec:License-GFDL-3}{{6.3}{21}{Copying In Quantity\relax }{subsection.6.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.4}Modifications}{21}{subsection.6.4}} +\newlabel{sec:License-GFDL-4}{{6.4}{21}{Modifications\relax }{subsection.6.4}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.5}Combining Documents}{24}{subsection.6.5}} +\newlabel{sec:License-GFDL-5}{{6.5}{24}{Combining Documents\relax }{subsection.6.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{24}{subsection.6.6}} +\newlabel{sec:License-GFDL-6}{{6.6}{24}{Collections Of Documents\relax }{subsection.6.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{25}{subsection.6.7}} +\newlabel{sec:License-GFDL-7}{{6.7}{25}{Aggregation With Independent Works\relax }{subsection.6.7}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.8}Translation}{25}{subsection.6.8}} +\newlabel{sec:License-GFDL-8}{{6.8}{25}{Translation\relax }{subsection.6.8}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.9}Termination}{26}{subsection.6.9}} +\newlabel{sec:License-GFDL-9}{{6.9}{26}{Termination\relax }{subsection.6.9}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{26}{subsection.6.10}} +\newlabel{sec:License-GFDL-10}{{6.10}{26}{Future Revisions Of This License\relax }{subsection.6.10}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{26}{subsection.6.11}} +\newlabel{sec:License-GFDL-11}{{6.11}{26}{How to use this License for your documents\relax }{subsection.6.11}{}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.log new file mode 100644 index 0000000..77c0e24 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.log @@ -0,0 +1,380 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 12 MAR 2010 14:17 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size12.clo +File: size12.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/tools/longtable.sty +Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) +\LTleft=\skip43 +\LTright=\skip44 +\LTpre=\skip45 +\LTpost=\skip46 +\LTchunksize=\count87 +\LTcapwidth=\dimen103 +\LT@head=\box26 +\LT@firsthead=\box27 +\LT@foot=\box28 +\LT@lastfoot=\box29 +\LT@cols=\count88 +\LT@rows=\count89 +\c@LT@tables=\count90 +\c@LT@chunks=\count91 +\LT@p@ftn=\toks14 +) +(/usr/share/texmf/tex/latex/graphics/graphicx.sty +Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks15 +) +(/usr/share/texmf/tex/latex/graphics/graphics.sty +Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/trig.sty +Package: trig 1999/03/16 v1.09 sin cos tan (DPC) +) +(/usr/share/texmf/tex/latex/graphics/graphics.cfg +File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive +) +Package graphics Info: Driver file: pdftex.def on input line 80. + +(/usr/share/texmf/tex/latex/graphics/pdftex.def +File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex +\Gread@gobject=\count92 +)) +\Gin@req@height=\dimen104 +\Gin@req@width=\dimen105 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX +\@linkdim=\dimen106 +\Hy@linkcounter=\count93 +\Hy@pagecounter=\count94 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count95 +\Field@Width=\dimen107 +\Fld@charsize=\dimen108 +\Choice@toks=\toks16 +\Field@toks=\toks17 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count96 +\c@Hfootnote=\count97 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count98 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. + +(/usr/share/texmf/tex/context/base/supp-pdf.tex +(/usr/share/texmf/tex/context/base/supp-mis.tex +loading : Context Support Macros / Miscellaneous (2004.10.26) +\protectiondepth=\count99 +\scratchcounter=\count100 +\scratchtoks=\toks18 +\scratchdimen=\dimen109 +\scratchskip=\skip47 +\scratchmuskip=\muskip11 +\scratchbox=\box30 +\scratchread=\read1 +\scratchwrite=\write4 +\zeropoint=\dimen110 +\onepoint=\dimen111 +\onebasepoint=\dimen112 +\minusone=\count101 +\thousandpoint=\dimen113 +\onerealpoint=\dimen114 +\emptytoks=\toks19 +\nextbox=\box31 +\nextdepth=\dimen115 +\everyline=\toks20 +\!!counta=\count102 +\!!countb=\count103 +\recursecounter=\count104 +) +loading : Context Support Macros / PDF (2004.03.26) +\nofMPsegments=\count105 +\nofMParguments=\count106 +\MPscratchCnt=\count107 +\MPscratchDim=\dimen116 +\MPnumerator=\count108 +\everyMPtoPDFconversion=\toks21 +) +Package hyperref Info: Link coloring OFF on input line 17. + (/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count109 +) +LaTeX Info: Redefining \ref on input line 17. +LaTeX Info: Redefining \pageref on input line 17. + (./Manual.out) +(./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <14.4> on input line 20. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 20. + (./Manual.toc +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 3. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 3. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 3. + [1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] [2]) +\tf@toc=\write5 +\openout5 = `Manual.toc'. + + (./sections/introduction.tex) (../../../../../installation.tex +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 25. + +[3] +Overfull \hbox (8.37456pt too wide) in paragraph at lines 53--54 +[][]$\OT1/cmtt/m/n/12 http : / / wiki . centos . org / AdditionalResources / Re +positories$[] + [] + +Missing character: There is no � in font cmr12! +Missing character: There is no � in font cmr12! +[4] +LaTeX Font Info: Try loading font information for OMS+cmr on input line 94. + (/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <12> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 94. + [5]) +(../../../../../configuration.tex [6] +Overfull \hbox (11.3752pt too wide) in paragraph at lines 60--60 +[]\OT1/cmtt/m/n/12 # Squid only knows about standardized HTTP request met +hods.[] + [] + + +Overfull \hbox (11.3752pt too wide) in paragraph at lines 60--60 +[]\OT1/cmtt/m/n/12 # You can add up to 20 additional "extension" methods +here.[] + [] + +[7] +Overfull \hbox (23.88292pt too wide) in paragraph at lines 92--93 +[]\OT1/cmtt/m/n/12 svn co https://projects.centos.org/svn/artwork $\OMS/cmsy/m/ +n/12 ^^X$\OT1/cmtt/m/n/12 /Desktop/ + [] + +[8] +LaTeX Font Info: Font shape `OT1/cmtt/bx/n' in size <12> not available +(Font) Font shape `OT1/cmtt/m/n' tried instead on input line 162. + [9]) (./sections/framework.tex +Underfull \hbox (badness 10000) in paragraph at lines 10--11 + + [] + +[10] +Overfull \hbox (4.34142pt too wide) in paragraph at lines 52--57 +\OT1/cmr/m/n/12 ported as PNG im-age. As con-ven-tion, we use the word `CENTOSA +RTWORK' + [] + + +Overfull \hbox (7.31615pt too wide) in paragraph at lines 70--73 +[]\OT1/cmr/m/n/12 In Ana-conda Header, mark-ers are used only in the file ana-c +onda[]header.svg, + [] + + +Overfull \hbox (0.77798pt too wide) in paragraph at lines 70--73 +\OT1/cmr/m/n/12 specif-i-cally to set the ma-jor re-lease num-ber of CentOS Dis +-tri-bu-tion in CentOS + [] + + +Underfull \hbox (badness 10000) in paragraph at lines 98--99 + + [] + +[11] +<../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-0.pdf, id=3 +91, 734.745pt x 233.87375pt> +File: ../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-0.pdf +Graphic file (type pdf) + + +<../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-1.pdf, id=3 +92, 608.2725pt x 123.46124pt> +File: ../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-1.pdf +Graphic file (type pdf) + + +<../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-2.pdf, id=3 +93, 608.2725pt x 123.46124pt> +File: ../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-2.pdf +Graphic file (type pdf) + + +[12 <../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-0.pdf> +<../../../../../../Identity/Models/Distro/Anaconda/Header/img/build-1.pdf> <../ +../../../../../Identity/Models/Distro/Anaconda/Header/img/build-2.pdf>] +Underfull \hbox (badness 10000) in paragraph at lines 157--158 + + [] + +[13] +Underfull \hbox (badness 10000) in paragraph at lines 222--223 + + [] + +[14] +<../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf, id=438, 5 +29.98pt x 589.20125pt> +File: ../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf Graph +ic file (type pdf) + + +Underfull \hbox (badness 10000) in paragraph at lines 250--251 + + [] + +) (./sections/rebranding.tex [15] [16 <../../../../../../Identity/Models/Script +s/Rendering/img/build-0.pdf>] +Overfull \hbox (2.56557pt too wide) in paragraph at lines 12--15 +[]\OT1/cmr/m/n/12 CentOS Brands and art-works are or-ga-nized in-side CentOS Ar +t-work Repos- + [] + +) (../../../../../Licenses/GFDL.tex +Underfull \hbox (badness 10000) in paragraph at lines 5--14 + + [] + +[17] [18] [19] [20] [21] [22] [23] [24] [25] +Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 document under the terms of the GNU Free Documentation Li +cense,[] + [] + + +Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 Version 1.2 or any later version published by the Free So +ftware[] + [] + + +Overfull \hbox (5.2002pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 Foundation; with no Invariant Sections, no Front-Cover Te +xts,[] + [] + + +Overfull \hbox (11.3752pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 and no Back-Cover Texts. A copy of the license is includ +ed in[] + [] + + +Overfull \hbox (5.2002pt too wide) in paragraph at lines 425--425 +[] \OT1/cmtt/m/n/12 with the Invariant Sections being LIST THEIR TITLES, with + the[] + [] + +[26]) [27] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 2901 strings out of 94500 + 40239 string characters out of 1176766 + 91168 words of memory out of 1000000 + 5944 multiletter control sequences out of 10000+50000 + 10751 words of font info for 38 fonts, out of 500000 for 2000 + 582 hyphenation exceptions out of 1000 + 27i,8n,36p,222b,267s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 513 PDF objects out of 300000 + 98 named destinations out of 131072 + 493 words of extra memory for PDF output out of 65536 + + +Output written on Manual.pdf (27 pages, 296612 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.out new file mode 100644 index 0000000..9b9b706 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.out @@ -0,0 +1,57 @@ +\BOOKMARK [1][-]{section.1}{Introduction}{} +\BOOKMARK [1][-]{section.2}{Installation}{} +\BOOKMARK [2][-]{subsection.2.1}{Subversion}{section.2} +\BOOKMARK [2][-]{subsection.2.2}{Inkscape}{section.2} +\BOOKMARK [2][-]{subsection.2.3}{ImageMagick}{section.2} +\BOOKMARK [2][-]{subsection.2.4}{Netpbm}{section.2} +\BOOKMARK [2][-]{subsection.2.5}{Syslinux}{section.2} +\BOOKMARK [2][-]{subsection.2.6}{GNU Image Manipulation Program}{section.2} +\BOOKMARK [2][-]{subsection.2.7}{GNU Core Utilities}{section.2} +\BOOKMARK [2][-]{subsection.2.8}{LaTeX}{section.2} +\BOOKMARK [1][-]{section.3}{Configuration}{} +\BOOKMARK [2][-]{subsection.3.1}{Firewall}{section.3} +\BOOKMARK [2][-]{subsection.3.2}{Subversion Behind Squid}{section.3} +\BOOKMARK [3][-]{subsubsection.3.2.1}{Subversion Client Configuration}{subsection.3.2} +\BOOKMARK [3][-]{subsubsection.3.2.2}{Squid Server Configuration}{subsection.3.2} +\BOOKMARK [2][-]{subsection.3.3}{Working Copy}{section.3} +\BOOKMARK [2][-]{subsection.3.4}{User Identification}{section.3} +\BOOKMARK [3][-]{subsubsection.3.4.1}{Account Registration}{subsection.3.4} +\BOOKMARK [3][-]{subsubsection.3.4.2}{Account Privileges}{subsection.3.4} +\BOOKMARK [2][-]{subsection.3.5}{Shell Environment}{section.3} +\BOOKMARK [3][-]{subsubsection.3.5.1}{Relative Paths}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.2}{Absolute Paths}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.3}{Environment Variable Definition}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.4}{Environment Variable Initialization}{subsection.3.5} +\BOOKMARK [1][-]{section.4}{Framework}{} +\BOOKMARK [2][-]{subsection.4.1}{Identity}{section.4} +\BOOKMARK [3][-]{subsubsection.4.1.1}{Designs}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.2}{Export Id}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.3}{Markers}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.4}{Images}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.5}{Models}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.6}{Rendering}{subsection.4.1} +\BOOKMARK [2][-]{subsection.4.2}{Translations}{section.4} +\BOOKMARK [3][-]{subsubsection.4.2.1}{Common Translations}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.2}{Specific Translations}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.3}{Translation Path}{subsection.4.2} +\BOOKMARK [2][-]{subsection.4.3}{Manuals}{section.4} +\BOOKMARK [2][-]{subsection.4.4}{Scripts}{section.4} +\BOOKMARK [3][-]{subsubsection.4.4.1}{Rendering}{subsection.4.4} +\BOOKMARK [3][-]{subsubsection.4.4.2}{Pre-rendering}{subsection.4.4} +\BOOKMARK [3][-]{subsubsection.4.4.3}{Post-rendering}{subsection.4.4} +\BOOKMARK [1][-]{section.5}{Rebranding}{} +\BOOKMARK [2][-]{subsection.5.1}{Images}{section.5} +\BOOKMARK [3][-]{subsubsection.5.1.1}{redhat-logos}{subsection.5.1} +\BOOKMARK [2][-]{subsection.5.2}{Messages Locale}{section.5} +\BOOKMARK [1][-]{section.6}{GNU Free Documentation License}{} +\BOOKMARK [2][-]{subsection.6.1}{Applicability And Definitions}{section.6} +\BOOKMARK [2][-]{subsection.6.2}{Verbatim Copying}{section.6} +\BOOKMARK [2][-]{subsection.6.3}{Copying In Quantity}{section.6} +\BOOKMARK [2][-]{subsection.6.4}{Modifications}{section.6} +\BOOKMARK [2][-]{subsection.6.5}{Combining Documents}{section.6} +\BOOKMARK [2][-]{subsection.6.6}{Collections Of Documents}{section.6} +\BOOKMARK [2][-]{subsection.6.7}{Aggregation With Independent Works}{section.6} +\BOOKMARK [2][-]{subsection.6.8}{Translation}{section.6} +\BOOKMARK [2][-]{subsection.6.9}{Termination}{section.6} +\BOOKMARK [2][-]{subsection.6.10}{Future Revisions Of This License}{section.6} +\BOOKMARK [2][-]{subsection.6.11}{How to use this License for your documents}{section.6} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.pdf new file mode 100644 index 0000000..04868a4 Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.toc new file mode 100644 index 0000000..548e728 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/Manual.toc @@ -0,0 +1,57 @@ +\contentsline {section}{\numberline {1}Introduction}{3}{section.1} +\contentsline {section}{\numberline {2}Installation}{3}{section.2} +\contentsline {subsection}{\numberline {2.1}Subversion}{3}{subsection.2.1} +\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2} +\contentsline {subsection}{\numberline {2.3}ImageMagick}{4}{subsection.2.3} +\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4} +\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5} +\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{5}{subsection.2.6} +\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{5}{subsection.2.7} +\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8} +\contentsline {section}{\numberline {3}Configuration}{6}{section.3} +\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1} +\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{6}{subsection.3.2} +\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{6}{subsubsection.3.2.1} +\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2} +\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3} +\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4} +\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{8}{subsubsection.3.4.1} +\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{8}{subsubsection.3.4.2} +\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5} +\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1} +\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2} +\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3} +\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{9}{subsubsection.3.5.4} +\contentsline {section}{\numberline {4}Framework}{10}{section.4} +\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1} +\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1} +\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2} +\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3} +\contentsline {subsubsection}{\numberline {4.1.4}Images}{11}{subsubsection.4.1.4} +\contentsline {subsubsection}{\numberline {4.1.5}Models}{12}{subsubsection.4.1.5} +\contentsline {subsubsection}{\numberline {4.1.6}Rendering}{13}{subsubsection.4.1.6} +\contentsline {subsection}{\numberline {4.2}Translations}{13}{subsection.4.2} +\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{13}{subsubsection.4.2.1} +\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{13}{subsubsection.4.2.2} +\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{14}{subsubsection.4.2.3} +\contentsline {subsection}{\numberline {4.3}Manuals}{14}{subsection.4.3} +\contentsline {subsection}{\numberline {4.4}Scripts}{15}{subsection.4.4} +\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{15}{subsubsection.4.4.1} +\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{15}{subsubsection.4.4.2} +\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{15}{subsubsection.4.4.3} +\contentsline {section}{\numberline {5}Rebranding}{17}{section.5} +\contentsline {subsection}{\numberline {5.1}Images}{17}{subsection.5.1} +\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{17}{subsubsection.5.1.1} +\contentsline {subsection}{\numberline {5.2}Messages Locale}{17}{subsection.5.2} +\contentsline {section}{\numberline {6}GNU Free Documentation License}{18}{section.6} +\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{18}{subsection.6.1} +\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{20}{subsection.6.2} +\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{21}{subsection.6.3} +\contentsline {subsection}{\numberline {6.4}Modifications}{21}{subsection.6.4} +\contentsline {subsection}{\numberline {6.5}Combining Documents}{24}{subsection.6.5} +\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{24}{subsection.6.6} +\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{25}{subsection.6.7} +\contentsline {subsection}{\numberline {6.8}Translation}{25}{subsection.6.8} +\contentsline {subsection}{\numberline {6.9}Termination}{26}{subsection.6.9} +\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{26}{subsection.6.10} +\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{26}{subsection.6.11} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/manual.tex new file mode 100644 index 0000000..9e18572 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Header/manual.tex @@ -0,0 +1,49 @@ +\documentclass[12pt]{article} +\usepackage{longtable} +\usepackage[pdftex]{graphicx} +\usepackage{hyperref} +\hypersetup{pdfauthor={Alain Reguera Delgado},% + pdftitle={Anaconda Header Visual Style},% + pdfsubject={CentOS Corporate Visual Identity}% + } + +% Tell LaTeX how to hyphenate a word. Don't hyphenate the following +% words: +\hyphenation{CentOS CENTOSARTWORK} + +\title{Anaconda Header Visual Style} +\author{Alain Reguera Delgado} + +\begin{document} + +\maketitle + +\begin{abstract} + +This article describes the visual style of Anaconda Header. Anaconda +is the name of the install program used by CentOS. It is python-based +with some custom modules written in C. The anaconda installer works on +a wide variety of Linux-based computing architectures (ia32, Itanium, +Alpha, S/390, PowerPC), and is designed to make it easy to add +platforms. + +Copyright (C) 2010 The CentOS Project. Permission is granted to copy, +distribute and/or modify this document under the terms of the GNU Free +Documentation License, Version 1.2 or any later version published by +the Free Software Foundation; with no Invariant Sections, no +Front-Cover Texts, and no Back-Cover Texts. A copy of the license is +included in the section entitled ``GNU Free Documentation License''. + +\end{abstract} + +\tableofcontents + +\input{sections/introduction.tex} +\input{../../../../../installation.tex} +\input{../../../../../configuration.tex} +\input{sections/framework.tex} +\input{sections/rebranding.tex} + +\input{../../../../../Licenses/GFDL.tex} + +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.aux new file mode 100644 index 0000000..bb0cdd1 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.aux @@ -0,0 +1,130 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{3}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Installation}{4}{section.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Subversion}{4}{subsection.2.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}ImageMagick}{5}{subsection.2.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{6}{subsection.2.6}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Configuration}{7}{section.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}Firewall}{7}{subsection.3.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Working Copy}{8}{subsection.3.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.4}User Identification}{9}{subsection.3.4}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{9}{subsubsection.3.4.1}} +\newlabel{sec:Configuration:Account}{{3.4.1}{9}{Account Registration\relax }{subsubsection.3.4.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2}} +\newlabel{sec:Configuration:User:Privileges}{{3.4.2}{9}{Account Privileges\relax }{subsubsection.3.4.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5}} +\newlabel{sec:Configuration:Environment}{{3.5}{9}{Shell Environment\relax }{subsection.3.5}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{10}{subsubsection.3.5.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{10}{subsubsection.3.5.3}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Framework}{10}{section.4}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Identity}{11}{subsection.4.1}} +\newlabel{sec:Framework:Identity}{{4.1}{11}{Identity\relax }{subsection.4.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.1}Design Templates}{11}{subsubsection.4.1.1}} +\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Anaconda Progress identity framework.}}{12}{figure.1}} +\newlabel{fig:Framework:Identity}{{1}{12}{Identity\relax }{figure.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.2}Design Templates Export Id}{13}{subsubsection.4.1.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.3}Design Models}{13}{subsubsection.4.1.3}} +\newlabel{sec:Framework:Identity:Models}{{4.1.3}{13}{Design Models\relax }{subsubsection.4.1.3}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.4}Image Files}{13}{subsubsection.4.1.4}} +\newlabel{sec:Framework:Identity:Images}{{4.1.4}{13}{Image Files\relax }{subsubsection.4.1.4}{}} +\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces Anaconda Progress design models framework.}}{14}{figure.2}} +\newlabel{fig:Framework:Identity:Models}{{2}{14}{Design Models\relax }{figure.2}{}} +\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Anaconda Progress slide images. A = ``Header'', B = ``Slide\ rotation'', C = ``Action/Navigation''.}}{14}{figure.3}} +\newlabel{fig:Identity:Models:Progress:Slides}{{3}{14}{Design Models\relax }{figure.3}{}} +\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces Anaconda Progress release notes. A = ``Release\ notes'', B =\ ``Action/Navigation''.}}{15}{figure.4}} +\newlabel{fig:Identity:Models:Progress:Release}{{4}{15}{Design Models\relax }{figure.4}{}} +\@writefile{lof}{\contentsline {figure}{\numberline {5}{\ignorespaces Anaconda Progress first slide template. A = ``The CentOS\ Symbol'', B = ``The CentOS Default Artistic Motif'', C = ``The CentOS\ Release Brand'', D = ``The CentOS Copyright''.}}{16}{figure.5}} +\newlabel{fig:Identity:Models:First}{{5}{16}{Design Models\relax }{figure.5}{}} +\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces Anaconda Progress list template.}}{17}{figure.6}} +\newlabel{fig:Identity:Models:Paragraph}{{6}{17}{Design Models\relax }{figure.6}{}} +\@writefile{lof}{\contentsline {figure}{\numberline {7}{\ignorespaces Anaconda Progress paragraph template.}}{17}{figure.7}} +\newlabel{fig:Identity:Models:List}{{7}{17}{Design Models\relax }{figure.7}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.5}Image Files Rendering}{18}{subsubsection.4.1.5}} +\newlabel{sec:Framework:Identity:Rendering}{{4.1.5}{18}{Image Files Rendering\relax }{subsubsection.4.1.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.2}Translations}{18}{subsection.4.2}} +\newlabel{sec:Framework:Translations}{{4.2}{18}{Translations\relax }{subsection.4.2}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{18}{subsubsection.4.2.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{18}{subsubsection.4.2.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{19}{subsubsection.4.2.3}} +\@writefile{lof}{\contentsline {figure}{\numberline {8}{\ignorespaces Anaconda Progress translation framework.}}{20}{figure.8}} +\newlabel{fig:Framework:Translation}{{8}{20}{Translation Path\relax }{figure.8}{}} +\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Anaconda Progress translation markers.}}{21}{table.1}} +\newlabel{tab:Framework:Identity:Markers}{{1}{21}{Translation Markers\relax }{table.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.4}Translation Markers}{21}{subsubsection.4.2.4}} +\newlabel{sec:Framework:Translations:Markers}{{4.2.4}{21}{Translation Markers\relax }{subsubsection.4.2.4}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.5}Translation Rendering}{21}{subsubsection.4.2.5}} +\@writefile{lof}{\contentsline {figure}{\numberline {9}{\ignorespaces English translation file for CentOS 5 Anaconda Progress\ `welcome' slide. Files like this are used by \texttt {render.sh} identity\ script to produce translated images.}}{22}{figure.9}} +\newlabel{fig:Framework:Translations:Markers}{{9}{22}{Translation Markers\relax }{figure.9}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.6}Translation Rendering Script}{23}{subsubsection.4.2.6}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.7}Translation Template Directory}{24}{subsubsection.4.2.7}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}Manuals}{24}{subsection.4.3}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.3.1}Writing Style}{24}{subsubsection.4.3.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.3.2}File Structure}{24}{subsubsection.4.3.2}} +\@writefile{lof}{\contentsline {figure}{\numberline {10}{\ignorespaces Specific documentation files. These files are specific to Anaconda Progress Visual Style manual only.}}{25}{figure.10}} +\newlabel{fig:Framework:Manuals:Structure:Specific}{{10}{25}{File Structure\relax }{figure.10}{}} +\@writefile{lof}{\contentsline {figure}{\numberline {11}{\ignorespaces Common documentation files. These files are reused by all\ manuals.}}{25}{figure.11}} +\newlabel{fig:Framework:Manuals:Structure:Common}{{11}{25}{File Structure\relax }{figure.11}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.3.3}Exporting To PDF}{26}{subsubsection.4.3.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Scripts}{26}{subsection.4.4}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.1}Invocation Scripts}{27}{subsubsection.4.4.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.2}Configuration Scripts}{27}{subsubsection.4.4.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.3}Function Scripts}{27}{subsubsection.4.4.3}} +\@writefile{lof}{\contentsline {figure}{\numberline {12}{\ignorespaces Anaconda Progress configuration layout.}}{28}{figure.12}} +\newlabel{fig:Framework:Scripts:Config}{{12}{28}{Configuration Scripts\relax }{figure.12}{}} +\@writefile{toc}{\contentsline {section}{\numberline {5}Rebranding}{29}{section.5}} +\newlabel{sec:Rebranding}{{5}{29}{Rebranding\relax }{section.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}Images}{29}{subsection.5.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{29}{subsubsection.5.1.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Messages Locale}{29}{subsection.5.2}} +\@writefile{lof}{\contentsline {figure}{\numberline {13}{\ignorespaces Anaconda Progress slide images.}}{30}{figure.13}} +\newlabel{fig:Rebranding:Images}{{13}{30}{redhat-logos\relax }{figure.13}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {5.3}Release Notes}{31}{subsection.5.3}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.3.1}centos-release-notes}{31}{subsubsection.5.3.1}} +\@writefile{lof}{\contentsline {figure}{\numberline {14}{\ignorespaces Anaconda Progress release notes files.}}{31}{figure.14}} +\newlabel{fig:Rebranding:ReleaseNotes:Files}{{14}{31}{centos-release-notes\relax }{figure.14}{}} +\@writefile{toc}{\contentsline {section}{\numberline {6}GNU Free Documentation License}{32}{section.6}} +\newlabel{sec:License-GFDL-0}{{6}{32}{Preamble\relax }{section*.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{32}{subsection.6.1}} +\newlabel{sec:License-GFDL-1}{{6.1}{32}{Applicability And Definitions\relax }{subsection.6.1}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{34}{subsection.6.2}} +\newlabel{sec:License-GFDL-2}{{6.2}{34}{Verbatim Copying\relax }{subsection.6.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{35}{subsection.6.3}} +\newlabel{sec:License-GFDL-3}{{6.3}{35}{Copying In Quantity\relax }{subsection.6.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.4}Modifications}{35}{subsection.6.4}} +\newlabel{sec:License-GFDL-4}{{6.4}{35}{Modifications\relax }{subsection.6.4}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.5}Combining Documents}{38}{subsection.6.5}} +\newlabel{sec:License-GFDL-5}{{6.5}{38}{Combining Documents\relax }{subsection.6.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{38}{subsection.6.6}} +\newlabel{sec:License-GFDL-6}{{6.6}{38}{Collections Of Documents\relax }{subsection.6.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{39}{subsection.6.7}} +\newlabel{sec:License-GFDL-7}{{6.7}{39}{Aggregation With Independent Works\relax }{subsection.6.7}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.8}Translation}{39}{subsection.6.8}} +\newlabel{sec:License-GFDL-8}{{6.8}{39}{Translation\relax }{subsection.6.8}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.9}Termination}{40}{subsection.6.9}} +\newlabel{sec:License-GFDL-9}{{6.9}{40}{Termination\relax }{subsection.6.9}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{40}{subsection.6.10}} +\newlabel{sec:License-GFDL-10}{{6.10}{40}{Future Revisions Of This License\relax }{subsection.6.10}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{40}{subsection.6.11}} +\newlabel{sec:License-GFDL-11}{{6.11}{40}{How to use this License for your documents\relax }{subsection.6.11}{}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.log new file mode 100644 index 0000000..ed6ad65 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.log @@ -0,0 +1,431 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 30 MAR 2010 23:16 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size12.clo +File: size12.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/graphics/graphicx.sty +Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks14 +) +(/usr/share/texmf/tex/latex/graphics/graphics.sty +Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/trig.sty +Package: trig 1999/03/16 v1.09 sin cos tan (DPC) +) +(/usr/share/texmf/tex/latex/graphics/graphics.cfg +File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive +) +Package graphics Info: Driver file: pdftex.def on input line 80. + +(/usr/share/texmf/tex/latex/graphics/pdftex.def +File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex +\Gread@gobject=\count87 +)) +\Gin@req@height=\dimen103 +\Gin@req@width=\dimen104 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX +\@linkdim=\dimen105 +\Hy@linkcounter=\count88 +\Hy@pagecounter=\count89 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count90 +\Field@Width=\dimen106 +\Fld@charsize=\dimen107 +\Choice@toks=\toks15 +\Field@toks=\toks16 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count91 +\c@Hfootnote=\count92 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count93 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 16. +LaTeX Font Info: ... okay on input line 16. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 16. +LaTeX Font Info: ... okay on input line 16. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 16. +LaTeX Font Info: ... okay on input line 16. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 16. +LaTeX Font Info: ... okay on input line 16. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 16. +LaTeX Font Info: ... okay on input line 16. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 16. +LaTeX Font Info: ... okay on input line 16. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 16. +LaTeX Font Info: ... okay on input line 16. + +(/usr/share/texmf/tex/context/base/supp-pdf.tex +(/usr/share/texmf/tex/context/base/supp-mis.tex +loading : Context Support Macros / Miscellaneous (2004.10.26) +\protectiondepth=\count94 +\scratchcounter=\count95 +\scratchtoks=\toks17 +\scratchdimen=\dimen108 +\scratchskip=\skip43 +\scratchmuskip=\muskip11 +\scratchbox=\box26 +\scratchread=\read1 +\scratchwrite=\write4 +\zeropoint=\dimen109 +\onepoint=\dimen110 +\onebasepoint=\dimen111 +\minusone=\count96 +\thousandpoint=\dimen112 +\onerealpoint=\dimen113 +\emptytoks=\toks18 +\nextbox=\box27 +\nextdepth=\dimen114 +\everyline=\toks19 +\!!counta=\count97 +\!!countb=\count98 +\recursecounter=\count99 +) +loading : Context Support Macros / PDF (2004.03.26) +\nofMPsegments=\count100 +\nofMParguments=\count101 +\MPscratchCnt=\count102 +\MPscratchDim=\dimen115 +\MPnumerator=\count103 +\everyMPtoPDFconversion=\toks20 +) +Package hyperref Info: Link coloring OFF on input line 16. + (/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count104 +) +LaTeX Info: Redefining \ref on input line 16. +LaTeX Info: Redefining \pageref on input line 16. + (./Manual.out) +(./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <14.4> on input line 19. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 19. +LaTeX Font Info: Try loading font information for OMS+cmr on input line 36. + (/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10.95> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 36. + (./Manual.toc +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 3. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 3. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 3. + +[1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] [2]) +\tf@toc=\write5 +\openout5 = `Manual.toc'. + + +(./sections/introduction.tex) (../../../../../installation.tex [3] +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 25. + +Overfull \hbox (8.37456pt too wide) in paragraph at lines 53--54 +[][]$\OT1/cmtt/m/n/12 http : / / wiki . centos . org / AdditionalResources / Re +positories$[] + [] + +[4] +Missing character: There is no � in font cmr12! +Missing character: There is no � in font cmr12! +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <12> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 94. + [5]) (../../../../../configuration.tex [6] +Overfull \hbox (11.3752pt too wide) in paragraph at lines 64--64 +[]\OT1/cmtt/m/n/12 # Squid only knows about standardized HTTP request met +hods.[] + [] + +[7] +Overfull \hbox (11.3752pt too wide) in paragraph at lines 64--64 +[]\OT1/cmtt/m/n/12 # You can add up to 20 additional "extension" methods +here.[] + [] + + +Overfull \hbox (23.88292pt too wide) in paragraph at lines 96--97 +[]\OT1/cmtt/m/n/12 svn co https://projects.centos.org/svn/artwork $\OMS/cmsy/m/ +n/12 ^^X$\OT1/cmtt/m/n/12 /Desktop/ + [] + +[8] [9] +Overfull \hbox (32.24086pt too wide) in paragraph at lines 161--168 +\OT1/cmr/m/n/12 CentOS Art-work Repos-i-tory, we de-cided to de-fine the \OT1/c +mr/bx/n/12 CentOS[]ARTWORK[]WC + [] + +) (./sections/framework.tex +Underfull \hbox (badness 10000) in paragraph at lines 9--10 + + [] + +[10] +Underfull \hbox (badness 10000) in paragraph at lines 57--58 + + [] + +[11] [12] +Underfull \hbox (badness 10000) in paragraph at lines 122--123 + + [] + + +<../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-3.pdf, id +=436, 691.58376pt x 481.8pt> +File: ../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-3.pd +f Graphic file (type pdf) + + +<../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-4.pdf, id +=437, 691.58376pt x 481.8pt> +File: ../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-4.pd +f Graphic file (type pdf) + + +<../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-0.pdf, id +=438, 393.47pt x 332.24126pt> +File: ../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-0.pd +f Graphic file (type pdf) + + +<../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-1.pdf, id +=439, 393.47pt x 232.87pt> +File: ../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-1.pd +f Graphic file (type pdf) + + +<../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-2.pdf, id +=440, 393.47pt x 232.87pt> +File: ../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build-2.pd +f Graphic file (type pdf) + + +Underfull \hbox (badness 10000) in paragraph at lines 214--215 + + [] + +[13] [14 <../../../../../../Identity/Models/Distro/Anaconda/Progress/img/build- +3.pdf>] [15 <../../../../../../Identity/Models/Distro/Anaconda/Progress/img/bui +ld-4.pdf>] [16 <../../../../../../Identity/Models/Distro/Anaconda/Progress/img/ +build-0.pdf>] [17 <../../../../../../Identity/Models/Distro/Anaconda/Progress/i +mg/build-1.pdf> <../../../../../../Identity/Models/Distro/Anaconda/Progress/img +/build-2.pdf>] +Underfull \hbox (badness 10000) in paragraph at lines 247--248 + + [] + +[18] [19] [20] +Overfull \hbox (11.3752pt too wide) in paragraph at lines 423--423 +[]\OT1/cmtt/m/n/12 # Warning: Do not modify this file directly. This file is cr +eated[] + [] + + +Overfull \hbox (17.5502pt too wide) in paragraph at lines 423--423 +[]\OT1/cmtt/m/n/12 # automatically using render.sh translation script. Any chan +ge you[] + [] + + +Overfull \hbox (5.2002pt too wide) in paragraph at lines 423--423 +[]\OT1/cmtt/m/n/12 # translation script. If you want to improve the content of +this[] + [] + + +Overfull \hbox (11.3752pt too wide) in paragraph at lines 423--423 +[]\OT1/cmtt/m/n/12 # translation file, improve its template file instead and ru +n the[] + [] + + +Overfull \hbox (23.7252pt too wide) in paragraph at lines 423--423 +[]\OT1/cmtt/m/n/12 s/=TEXT2=/CentOS is an enterprise-class Linux Distribution d +erived\[] + [] + + +Overfull \hbox (5.2002pt too wide) in paragraph at lines 423--423 +[]\OT1/cmtt/m/n/12 from sources freely provided to the public by a prominent No +rth\[] + [] + + +Overfull \hbox (29.9002pt too wide) in paragraph at lines 423--423 +[]\OT1/cmtt/m/n/12 redistribution policy and aims to be 100% binary compatible. + CentOS\[] + [] + +[21] [22] [23] +Underfull \hbox (badness 10000) in paragraph at lines 512--513 + + [] + +[24] [25] +Overfull \hbox (18.05084pt too wide) in paragraph at lines 608--613 +[]\OT1/cmr/m/n/12 provides in-for-ma-tion about how to re-brand Ana-conda Progr +ess + [] + + +Overfull \hbox (15.44675pt too wide) in paragraph at lines 608--613 +\OT1/cmr/m/n/12 Progress Vi-sual Style \OT1/cmtt/m/n/12 rebranding.tex \OT1/cmr +/m/n/12 file is spe-cific to Ana-conda Progress + [] + +[26] +Underfull \hbox (badness 10000) in paragraph at lines 647--648 + + [] + + +Overfull \hbox (42.25021pt too wide) in paragraph at lines 695--695 +[]\OT1/cmtt/m/n/12 # Template and Translation matching list. Define which desig +n template[] + [] + +) (./sections/rebranding.tex [27] [28] +Overfull \hbox (2.56557pt too wide) in paragraph at lines 13--16 +[]\OT1/cmr/m/n/12 CentOS Brands and art-works are or-ga-nized in-side CentOS Ar +t-work Repos- + [] + +[29] [30]) (../../../../../Licenses/GFDL.tex +Underfull \hbox (badness 10000) in paragraph at lines 5--14 + + [] + +[31] [32] [33] [34] [35] [36] [37] [38] [39] +Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 document under the terms of the GNU Free Documentation Li +cense,[] + [] + + +Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 Version 1.2 or any later version published by the Free So +ftware[] + [] + + +Overfull \hbox (5.2002pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 Foundation; with no Invariant Sections, no Front-Cover Te +xts,[] + [] + + +Overfull \hbox (11.3752pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 and no Back-Cover Texts. A copy of the license is includ +ed in[] + [] + + +Overfull \hbox (5.2002pt too wide) in paragraph at lines 425--425 +[] \OT1/cmtt/m/n/12 with the Invariant Sections being LIST THEIR TITLES, with + the[] + [] + +[40]) [41] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 2872 strings out of 94500 + 40567 string characters out of 1176766 + 90951 words of memory out of 1000000 + 5890 multiletter control sequences out of 10000+50000 + 11008 words of font info for 39 fonts, out of 500000 for 2000 + 582 hyphenation exceptions out of 1000 + 27i,8n,36p,297b,267s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 650 PDF objects out of 300000 + 126 named destinations out of 131072 + 562 words of extra memory for PDF output out of 65536 + + +Output written on Manual.pdf (41 pages, 342886 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.lot b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.lot new file mode 100644 index 0000000..aff46bf --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.lot @@ -0,0 +1,24 @@ +\contentsline {table}{\numberline {1}{Files related to the First Slide of Anaconda Progress.}}{2}{table.1} +\contentsline {table}{\numberline {1}{Files related to the First Slide of Anaconda Progress. (continued)}}{3}{table.1} +\contentsline {table}{\numberline {2}{Files related to English Slides of Anaconda Progress.}}{3}{table.2} +\contentsline {table}{\numberline {2}{Files related to English Slides of Anaconda Progress. (continued)}}{4}{table.2} +\contentsline {table}{\numberline {3}{Files related to Czech Slides of Anaconda Progress.}}{4}{table.3} +\contentsline {table}{\numberline {3}{Files related to Czech Slides of Anaconda Progress. (continued)}}{5}{table.3} +\contentsline {table}{\numberline {4}{Files related to German Slides of Anaconda Progress.}}{5}{table.4} +\contentsline {table}{\numberline {4}{Files related to German Slides of Anaconda Progress. (continued)}}{6}{table.4} +\contentsline {table}{\numberline {5}{Files related to Spanish Slides of Anaconda Progress.}}{6}{table.5} +\contentsline {table}{\numberline {5}{Files related to Spanish Slides of Anaconda Progress. (continued)}}{7}{table.5} +\contentsline {table}{\numberline {6}{Files related to French Slides of Anaconda Progress.}}{7}{table.6} +\contentsline {table}{\numberline {7}{Files related to Italian Slides of Anaconda Progress.}}{8}{table.7} +\contentsline {table}{\numberline {8}{Files related to Japanese Slides of Anaconda Progress.}}{8}{table.8} +\contentsline {table}{\numberline {8}{Files related to Japanese Slides of Anaconda Progress. (continued)}}{9}{table.8} +\contentsline {table}{\numberline {9}{Files related to Dutch Slides of Anaconda Progress.}}{9}{table.9} +\contentsline {table}{\numberline {9}{Files related to Dutch Slides of Anaconda Progress. (continued)}}{10}{table.9} +\contentsline {table}{\numberline {10}{Files related to Portuguese Slides of Anaconda Progress.}}{10}{table.10} +\contentsline {table}{\numberline {10}{Files related to Portuguese Slides of Anaconda Progress. (continued)}}{11}{table.10} +\contentsline {table}{\numberline {11}{Files related to Romanian Slides of Anaconda Progress.}}{11}{table.11} +\contentsline {table}{\numberline {11}{Files related to Romanian Slides of Anaconda Progress. (continued)}}{12}{table.11} +\contentsline {table}{\numberline {12}{Files related to Russian Slides of Anaconda Progress.}}{12}{table.12} +\contentsline {table}{\numberline {12}{Files related to Russian Slides of Anaconda Progress. (continued)}}{13}{table.12} +\contentsline {table}{\numberline {13}{Files related to Portuguese du Brasil Slides of Anaconda Progress.}}{13}{table.13} +\contentsline {table}{\numberline {13}{Files related to Portuguese du Brasil Slides of Anaconda Progress. (continued)}}{14}{table.13} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.out new file mode 100644 index 0000000..34e2b08 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.out @@ -0,0 +1,65 @@ +\BOOKMARK [1][-]{section.1}{Introduction}{} +\BOOKMARK [1][-]{section.2}{Installation}{} +\BOOKMARK [2][-]{subsection.2.1}{Subversion}{section.2} +\BOOKMARK [2][-]{subsection.2.2}{Inkscape}{section.2} +\BOOKMARK [2][-]{subsection.2.3}{ImageMagick}{section.2} +\BOOKMARK [2][-]{subsection.2.4}{Netpbm}{section.2} +\BOOKMARK [2][-]{subsection.2.5}{Syslinux}{section.2} +\BOOKMARK [2][-]{subsection.2.6}{GNU Image Manipulation Program}{section.2} +\BOOKMARK [2][-]{subsection.2.7}{GNU Core Utilities}{section.2} +\BOOKMARK [2][-]{subsection.2.8}{LaTeX}{section.2} +\BOOKMARK [1][-]{section.3}{Configuration}{} +\BOOKMARK [2][-]{subsection.3.1}{Firewall}{section.3} +\BOOKMARK [2][-]{subsection.3.2}{Subversion Behind Squid}{section.3} +\BOOKMARK [3][-]{subsubsection.3.2.1}{Subversion Client Configuration}{subsection.3.2} +\BOOKMARK [3][-]{subsubsection.3.2.2}{Squid Server Configuration}{subsection.3.2} +\BOOKMARK [2][-]{subsection.3.3}{Working Copy}{section.3} +\BOOKMARK [2][-]{subsection.3.4}{User Identification}{section.3} +\BOOKMARK [3][-]{subsubsection.3.4.1}{Account Registration}{subsection.3.4} +\BOOKMARK [3][-]{subsubsection.3.4.2}{Account Privileges}{subsection.3.4} +\BOOKMARK [2][-]{subsection.3.5}{Shell Environment}{section.3} +\BOOKMARK [3][-]{subsubsection.3.5.1}{Relative Paths}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.2}{Absolute Paths}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.3}{Environment Variable Definition}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.4}{Environment Variable Initialization}{subsection.3.5} +\BOOKMARK [1][-]{section.4}{Framework}{} +\BOOKMARK [2][-]{subsection.4.1}{Identity}{section.4} +\BOOKMARK [3][-]{subsubsection.4.1.1}{Design Templates}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.2}{Design Templates Export Id}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.3}{Design Models}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.4}{Image Files}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.5}{Image Files Rendering}{subsection.4.1} +\BOOKMARK [2][-]{subsection.4.2}{Translations}{section.4} +\BOOKMARK [3][-]{subsubsection.4.2.1}{Common Translations}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.2}{Specific Translations}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.3}{Translation Path}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.4}{Translation Markers}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.5}{Translation Rendering}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.6}{Translation Rendering Script}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.7}{Translation Template Directory}{subsection.4.2} +\BOOKMARK [2][-]{subsection.4.3}{Manuals}{section.4} +\BOOKMARK [3][-]{subsubsection.4.3.1}{Writing Style}{subsection.4.3} +\BOOKMARK [3][-]{subsubsection.4.3.2}{File Structure}{subsection.4.3} +\BOOKMARK [3][-]{subsubsection.4.3.3}{Exporting To PDF}{subsection.4.3} +\BOOKMARK [2][-]{subsection.4.4}{Scripts}{section.4} +\BOOKMARK [3][-]{subsubsection.4.4.1}{Invocation Scripts}{subsection.4.4} +\BOOKMARK [3][-]{subsubsection.4.4.2}{Configuration Scripts}{subsection.4.4} +\BOOKMARK [3][-]{subsubsection.4.4.3}{Function Scripts}{subsection.4.4} +\BOOKMARK [1][-]{section.5}{Rebranding}{} +\BOOKMARK [2][-]{subsection.5.1}{Images}{section.5} +\BOOKMARK [3][-]{subsubsection.5.1.1}{redhat-logos}{subsection.5.1} +\BOOKMARK [2][-]{subsection.5.2}{Messages Locale}{section.5} +\BOOKMARK [2][-]{subsection.5.3}{Release Notes}{section.5} +\BOOKMARK [3][-]{subsubsection.5.3.1}{centos-release-notes}{subsection.5.3} +\BOOKMARK [1][-]{section.6}{GNU Free Documentation License}{} +\BOOKMARK [2][-]{subsection.6.1}{Applicability And Definitions}{section.6} +\BOOKMARK [2][-]{subsection.6.2}{Verbatim Copying}{section.6} +\BOOKMARK [2][-]{subsection.6.3}{Copying In Quantity}{section.6} +\BOOKMARK [2][-]{subsection.6.4}{Modifications}{section.6} +\BOOKMARK [2][-]{subsection.6.5}{Combining Documents}{section.6} +\BOOKMARK [2][-]{subsection.6.6}{Collections Of Documents}{section.6} +\BOOKMARK [2][-]{subsection.6.7}{Aggregation With Independent Works}{section.6} +\BOOKMARK [2][-]{subsection.6.8}{Translation}{section.6} +\BOOKMARK [2][-]{subsection.6.9}{Termination}{section.6} +\BOOKMARK [2][-]{subsection.6.10}{Future Revisions Of This License}{section.6} +\BOOKMARK [2][-]{subsection.6.11}{How to use this License for your documents}{section.6} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.pdf new file mode 100644 index 0000000..863a047 Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.toc new file mode 100644 index 0000000..8e72aa2 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/Manual.toc @@ -0,0 +1,65 @@ +\contentsline {section}{\numberline {1}Introduction}{3}{section.1} +\contentsline {section}{\numberline {2}Installation}{4}{section.2} +\contentsline {subsection}{\numberline {2.1}Subversion}{4}{subsection.2.1} +\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2} +\contentsline {subsection}{\numberline {2.3}ImageMagick}{5}{subsection.2.3} +\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4} +\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5} +\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{6}{subsection.2.6} +\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7} +\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8} +\contentsline {section}{\numberline {3}Configuration}{7}{section.3} +\contentsline {subsection}{\numberline {3.1}Firewall}{7}{subsection.3.1} +\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2} +\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1} +\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2} +\contentsline {subsection}{\numberline {3.3}Working Copy}{8}{subsection.3.3} +\contentsline {subsection}{\numberline {3.4}User Identification}{9}{subsection.3.4} +\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{9}{subsubsection.3.4.1} +\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2} +\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5} +\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1} +\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{10}{subsubsection.3.5.2} +\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{10}{subsubsection.3.5.3} +\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4} +\contentsline {section}{\numberline {4}Framework}{10}{section.4} +\contentsline {subsection}{\numberline {4.1}Identity}{11}{subsection.4.1} +\contentsline {subsubsection}{\numberline {4.1.1}Design Templates}{11}{subsubsection.4.1.1} +\contentsline {subsubsection}{\numberline {4.1.2}Design Templates Export Id}{13}{subsubsection.4.1.2} +\contentsline {subsubsection}{\numberline {4.1.3}Design Models}{13}{subsubsection.4.1.3} +\contentsline {subsubsection}{\numberline {4.1.4}Image Files}{13}{subsubsection.4.1.4} +\contentsline {subsubsection}{\numberline {4.1.5}Image Files Rendering}{18}{subsubsection.4.1.5} +\contentsline {subsection}{\numberline {4.2}Translations}{18}{subsection.4.2} +\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{18}{subsubsection.4.2.1} +\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{18}{subsubsection.4.2.2} +\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{19}{subsubsection.4.2.3} +\contentsline {subsubsection}{\numberline {4.2.4}Translation Markers}{21}{subsubsection.4.2.4} +\contentsline {subsubsection}{\numberline {4.2.5}Translation Rendering}{21}{subsubsection.4.2.5} +\contentsline {subsubsection}{\numberline {4.2.6}Translation Rendering Script}{23}{subsubsection.4.2.6} +\contentsline {subsubsection}{\numberline {4.2.7}Translation Template Directory}{24}{subsubsection.4.2.7} +\contentsline {subsection}{\numberline {4.3}Manuals}{24}{subsection.4.3} +\contentsline {subsubsection}{\numberline {4.3.1}Writing Style}{24}{subsubsection.4.3.1} +\contentsline {subsubsection}{\numberline {4.3.2}File Structure}{24}{subsubsection.4.3.2} +\contentsline {subsubsection}{\numberline {4.3.3}Exporting To PDF}{26}{subsubsection.4.3.3} +\contentsline {subsection}{\numberline {4.4}Scripts}{26}{subsection.4.4} +\contentsline {subsubsection}{\numberline {4.4.1}Invocation Scripts}{27}{subsubsection.4.4.1} +\contentsline {subsubsection}{\numberline {4.4.2}Configuration Scripts}{27}{subsubsection.4.4.2} +\contentsline {subsubsection}{\numberline {4.4.3}Function Scripts}{27}{subsubsection.4.4.3} +\contentsline {section}{\numberline {5}Rebranding}{29}{section.5} +\contentsline {subsection}{\numberline {5.1}Images}{29}{subsection.5.1} +\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{29}{subsubsection.5.1.1} +\contentsline {subsection}{\numberline {5.2}Messages Locale}{29}{subsection.5.2} +\contentsline {subsection}{\numberline {5.3}Release Notes}{31}{subsection.5.3} +\contentsline {subsubsection}{\numberline {5.3.1}centos-release-notes}{31}{subsubsection.5.3.1} +\contentsline {section}{\numberline {6}GNU Free Documentation License}{32}{section.6} +\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{32}{subsection.6.1} +\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{34}{subsection.6.2} +\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{35}{subsection.6.3} +\contentsline {subsection}{\numberline {6.4}Modifications}{35}{subsection.6.4} +\contentsline {subsection}{\numberline {6.5}Combining Documents}{38}{subsection.6.5} +\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{38}{subsection.6.6} +\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{39}{subsection.6.7} +\contentsline {subsection}{\numberline {6.8}Translation}{39}{subsection.6.8} +\contentsline {subsection}{\numberline {6.9}Termination}{40}{subsection.6.9} +\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{40}{subsection.6.10} +\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{40}{subsection.6.11} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/manual.tex new file mode 100644 index 0000000..6858918 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Progress/manual.tex @@ -0,0 +1,56 @@ +\documentclass[12pt]{article} +\usepackage[pdftex]{graphicx} +\usepackage{hyperref} +\hypersetup{pdfauthor={Alain Reguera Delgado},% + pdftitle={Anaconda Progress Visual Style},% + pdfsubject={CentOS Corporate Visual Identity}% + } + +% Tell LaTeX how to hyphenate a word. Don't hyphenate the following +% words: +\hyphenation{CentOS CENTOSARTWORK} + +\title{Anaconda Progress Visual Style} +\author{Alain Reguera Delgado} + +\begin{document} + +\maketitle + +\begin{abstract} + +This article describes the visual style of Anaconda Progress. +Anaconda Progress screen is shown after configuration and while +packages are installed. Anaconda Progress screen has a header, and +slide images which alternate with release notes texts. This article +describes Anaconda Progress slide images and release notes only. The +header component of Anaconda Progress is described in the document +``Anaconda Header Visual Style''. + +Anaconda is the name of the install program used by CentOS. It is +python-based with some custom modules written in C. The Anaconda +installer works on a wide variety of Linux-based computing +architectures (ia32, Itanium, Alpha, S/390, PowerPC), and is designed +to make it easy to add platforms. + +Copyright \copyright\ 2010 The CentOS Project. Permission is granted +to copy, distribute and/or modify this document under the terms of the +GNU Free Documentation License, Version 1.2 or any later version +published by the Free Software Foundation; with no Invariant Sections, +no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled ``GNU Free Documentation +License''. + +\end{abstract} + +\tableofcontents + +\input{sections/introduction.tex} +\input{../../../../../installation.tex} +\input{../../../../../configuration.tex} +\input{sections/framework.tex} +\input{sections/rebranding.tex} + +\input{../../../../../Licenses/GFDL.tex} + +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.aux new file mode 100644 index 0000000..6e38102 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.aux @@ -0,0 +1,104 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{3}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Installation}{3}{section.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Subversion}{4}{subsection.2.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}ImageMagick}{5}{subsection.2.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{6}{subsection.2.6}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Configuration}{6}{section.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{9}{subsubsection.3.4.1}} +\newlabel{sec:Configuration:Account}{{3.4.1}{9}{Account Registration\relax }{subsubsection.3.4.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2}} +\newlabel{sec:Configuration:User:Privileges}{{3.4.2}{9}{Account Privileges\relax }{subsubsection.3.4.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5}} +\newlabel{sec:Configuration:Environment}{{3.5}{9}{Shell Environment\relax }{subsection.3.5}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Framework}{10}{section.4}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1}} +\newlabel{sec:Identity}{{4.1}{10}{Identity\relax }{subsection.4.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3}} +\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Anaconda Prompt translation markers.}}{12}{table.1}} +\newlabel{tab:Identity:Markers}{{1}{12}{Markers\relax }{table.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.4}Images}{12}{subsubsection.4.1.4}} +\newlabel{sec:Identity:Images}{{4.1.4}{12}{Images\relax }{subsubsection.4.1.4}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.5}Color Limitations}{12}{subsubsection.4.1.5}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.6}Color Palettes}{12}{subsubsection.4.1.6}} +\newlabel{sec:Identity:Palettes}{{4.1.6}{12}{Color Palettes\relax }{subsubsection.4.1.6}{}} +\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Color position in \texttt {Syslinux.ppm} image. Syslinux background color (A) is in the position 0. Syslinux foreground color (B) is in the position 7.}}{13}{figure.1}} +\newlabel{fig:Identity:Palette}{{1}{13}{Color Palettes\relax }{figure.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.7}Models}{14}{subsubsection.4.1.7}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.8}Rendering}{14}{subsubsection.4.1.8}} +\newlabel{sec:Identity:Rendering}{{4.1.8}{14}{Rendering\relax }{subsubsection.4.1.8}{}} +\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces Anaconda Prompt design model.}}{15}{figure.2}} +\newlabel{fig:Identity:Design:Model}{{2}{15}{Models\relax }{figure.2}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.9}Issues}{15}{subsubsection.4.1.9}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.2}Translations}{16}{subsection.4.2}} +\newlabel{sec:Translations}{{4.2}{16}{Translations\relax }{subsection.4.2}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{16}{subsubsection.4.2.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{16}{subsubsection.4.2.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{16}{subsubsection.4.2.3}} +\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Anaconda Prompt translation path.}}{17}{figure.3}} +\newlabel{fig:Translation:Path}{{3}{17}{Translation Path\relax }{figure.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}Manuals}{18}{subsection.4.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Scripts}{18}{subsection.4.4}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{18}{subsubsection.4.4.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{18}{subsubsection.4.4.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{18}{subsubsection.4.4.3}} +\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces Rendering design model.}}{19}{figure.4}} +\newlabel{fig:Scripts:Rendering}{{4}{19}{Rendering\relax }{figure.4}{}} +\@writefile{toc}{\contentsline {section}{\numberline {5}Rebranding}{20}{section.5}} +\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}Images}{20}{subsection.5.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{20}{subsubsection.5.1.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Syslinux}{21}{subsection.5.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {5.3}Messages Locale}{21}{subsection.5.3}} +\@writefile{toc}{\contentsline {section}{\numberline {6}GNU Free Documentation License}{22}{section.6}} +\newlabel{sec:License-GFDL-0}{{6}{22}{Preamble\relax }{section*.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{22}{subsection.6.1}} +\newlabel{sec:License-GFDL-1}{{6.1}{22}{Applicability And Definitions\relax }{subsection.6.1}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{24}{subsection.6.2}} +\newlabel{sec:License-GFDL-2}{{6.2}{24}{Verbatim Copying\relax }{subsection.6.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{25}{subsection.6.3}} +\newlabel{sec:License-GFDL-3}{{6.3}{25}{Copying In Quantity\relax }{subsection.6.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.4}Modifications}{25}{subsection.6.4}} +\newlabel{sec:License-GFDL-4}{{6.4}{25}{Modifications\relax }{subsection.6.4}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.5}Combining Documents}{28}{subsection.6.5}} +\newlabel{sec:License-GFDL-5}{{6.5}{28}{Combining Documents\relax }{subsection.6.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{28}{subsection.6.6}} +\newlabel{sec:License-GFDL-6}{{6.6}{28}{Collections Of Documents\relax }{subsection.6.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{29}{subsection.6.7}} +\newlabel{sec:License-GFDL-7}{{6.7}{29}{Aggregation With Independent Works\relax }{subsection.6.7}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.8}Translation}{29}{subsection.6.8}} +\newlabel{sec:License-GFDL-8}{{6.8}{29}{Translation\relax }{subsection.6.8}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.9}Termination}{30}{subsection.6.9}} +\newlabel{sec:License-GFDL-9}{{6.9}{30}{Termination\relax }{subsection.6.9}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{30}{subsection.6.10}} +\newlabel{sec:License-GFDL-10}{{6.10}{30}{Future Revisions Of This License\relax }{subsection.6.10}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{30}{subsection.6.11}} +\newlabel{sec:License-GFDL-11}{{6.11}{30}{How to use this License for your documents\relax }{subsection.6.11}{}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.log new file mode 100644 index 0000000..2eb3ce6 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.log @@ -0,0 +1,404 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 12 MAR 2010 14:17 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size12.clo +File: size12.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/tools/longtable.sty +Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) +\LTleft=\skip43 +\LTright=\skip44 +\LTpre=\skip45 +\LTpost=\skip46 +\LTchunksize=\count87 +\LTcapwidth=\dimen103 +\LT@head=\box26 +\LT@firsthead=\box27 +\LT@foot=\box28 +\LT@lastfoot=\box29 +\LT@cols=\count88 +\LT@rows=\count89 +\c@LT@tables=\count90 +\c@LT@chunks=\count91 +\LT@p@ftn=\toks14 +) +(/usr/share/texmf/tex/latex/graphics/graphicx.sty +Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks15 +) +(/usr/share/texmf/tex/latex/graphics/graphics.sty +Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/trig.sty +Package: trig 1999/03/16 v1.09 sin cos tan (DPC) +) +(/usr/share/texmf/tex/latex/graphics/graphics.cfg +File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive +) +Package graphics Info: Driver file: pdftex.def on input line 80. + +(/usr/share/texmf/tex/latex/graphics/pdftex.def +File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex +\Gread@gobject=\count92 +)) +\Gin@req@height=\dimen104 +\Gin@req@width=\dimen105 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX +\@linkdim=\dimen106 +\Hy@linkcounter=\count93 +\Hy@pagecounter=\count94 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count95 +\Field@Width=\dimen107 +\Fld@charsize=\dimen108 +\Choice@toks=\toks16 +\Field@toks=\toks17 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count96 +\c@Hfootnote=\count97 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count98 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. + +(/usr/share/texmf/tex/context/base/supp-pdf.tex +(/usr/share/texmf/tex/context/base/supp-mis.tex +loading : Context Support Macros / Miscellaneous (2004.10.26) +\protectiondepth=\count99 +\scratchcounter=\count100 +\scratchtoks=\toks18 +\scratchdimen=\dimen109 +\scratchskip=\skip47 +\scratchmuskip=\muskip11 +\scratchbox=\box30 +\scratchread=\read1 +\scratchwrite=\write4 +\zeropoint=\dimen110 +\onepoint=\dimen111 +\onebasepoint=\dimen112 +\minusone=\count101 +\thousandpoint=\dimen113 +\onerealpoint=\dimen114 +\emptytoks=\toks19 +\nextbox=\box31 +\nextdepth=\dimen115 +\everyline=\toks20 +\!!counta=\count102 +\!!countb=\count103 +\recursecounter=\count104 +) +loading : Context Support Macros / PDF (2004.03.26) +\nofMPsegments=\count105 +\nofMParguments=\count106 +\MPscratchCnt=\count107 +\MPscratchDim=\dimen116 +\MPnumerator=\count108 +\everyMPtoPDFconversion=\toks21 +) +Package hyperref Info: Link coloring OFF on input line 17. + (/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count109 +) +LaTeX Info: Redefining \ref on input line 17. +LaTeX Info: Redefining \pageref on input line 17. + (./Manual.out) +(./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <14.4> on input line 20. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 20. + (./Manual.toc +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 3. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 3. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 3. + [1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] [2]) +\tf@toc=\write5 +\openout5 = `Manual.toc'. + + (./sections/introduction.tex) (../../../../../installation.tex +[3] +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 25. + +Overfull \hbox (8.37456pt too wide) in paragraph at lines 53--54 +[][]$\OT1/cmtt/m/n/12 http : / / wiki . centos . org / AdditionalResources / Re +positories$[] + [] + +Missing character: There is no � in font cmr12! +Missing character: There is no � in font cmr12! +[4] +LaTeX Font Info: Try loading font information for OMS+cmr on input line 94. + (/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <12> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 94. + [5]) +(../../../../../configuration.tex [6] +Overfull \hbox (11.3752pt too wide) in paragraph at lines 60--60 +[]\OT1/cmtt/m/n/12 # Squid only knows about standardized HTTP request met +hods.[] + [] + + +Overfull \hbox (11.3752pt too wide) in paragraph at lines 60--60 +[]\OT1/cmtt/m/n/12 # You can add up to 20 additional "extension" methods +here.[] + [] + +[7] +Overfull \hbox (23.88292pt too wide) in paragraph at lines 92--93 +[]\OT1/cmtt/m/n/12 svn co https://projects.centos.org/svn/artwork $\OMS/cmsy/m/ +n/12 ^^X$\OT1/cmtt/m/n/12 /Desktop/ + [] + +[8] +LaTeX Font Info: Font shape `OT1/cmtt/bx/n' in size <12> not available +(Font) Font shape `OT1/cmtt/m/n' tried instead on input line 162. + [9]) (./sections/framework.tex +Underfull \hbox (badness 10000) in paragraph at lines 10--11 + + [] + + +Overfull \hbox (6.44574pt too wide) in paragraph at lines 24--28 +[]\OT1/cmr/m/n/12 This de-sign is com-mon to each ma-jor re-lease of CentOS + [] + +[10] +Overfull \hbox (15.76491pt too wide) in paragraph at lines 51--56 +\OT1/cmr/m/n/12 ex-ported as PNG im-age. As con-ven-tion, we use the word `CENT +OSARTWORK' + [] + +[11] +Underfull \hbox (badness 10000) in paragraph at lines 102--103 + + [] + +[12] +Overfull \hbox (1.18143pt too wide) in paragraph at lines 143--145 +[]\OT1/cmr/m/n/12 Fill its pix-els with the col-ors spec-i-fied in the \OT1/cmt +t/m/n/12 Syslinux.gpl \OT1/cmr/m/n/12 palette. + [] + + +Overfull \hbox (4.80638pt too wide) in paragraph at lines 146--151 +[]\OT1/cmr/m/n/12 Set the ap-pro-pri-ate or-der of col-ors in-side the \OT1/cmt +t/m/n/12 Syslinux.ppm \OT1/cmr/m/n/12 palette. + [] + + +Overfull \hbox (12.90079pt too wide) in paragraph at lines 166--172 +\OT1/cmr/m/n/12 adec-i-mal color in-for-ma-tion and its in-dex po-si-tion de-fi +ned in \OT1/cmtt/m/n/12 Syslinux.ppm + [] + + +<../../../../../../Identity/Models/Distro/Anaconda/Prompt/img/build-1.pdf, id=4 +19, 467.7475pt x 132.495pt> +File: ../../../../../../Identity/Models/Distro/Anaconda/Prompt/img/build-1.pdf +Graphic file (type pdf) + + +[13 <../../../../../../Identity/Models/Distro/Anaconda/Prompt/img/build-1.pdf>] + +Underfull \hbox (badness 10000) in paragraph at lines 211--212 + + [] + + +<../../../../../../Identity/Models/Distro/Anaconda/Prompt/img/build-0.pdf, id=4 +38, 554.07pt x 385.44pt> +File: ../../../../../../Identity/Models/Distro/Anaconda/Prompt/img/build-0.pdf +Graphic file (type pdf) + + +[14] [15 <../../../../../../Identity/Models/Distro/Anaconda/Prompt/img/build-0. +pdf>] +Underfull \hbox (badness 10000) in paragraph at lines 279--280 + + [] + +[16] +Underfull \hbox (badness 10000) in paragraph at lines 364--365 + + [] + +[17] +<../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf, id=471, 5 +29.98pt x 589.20125pt> +File: ../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf Graph +ic file (type pdf) + + +Underfull \hbox (badness 10000) in paragraph at lines 392--393 + + [] + +[18] [19 <../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf>] +) (./sections/rebranding.tex +Overfull \hbox (2.56557pt too wide) in paragraph at lines 12--15 +[]\OT1/cmr/m/n/12 CentOS Brands and art-works are or-ga-nized in-side CentOS Ar +t-work Repos- + [] + +[20] +Overfull \hbox (11.3752pt too wide) in paragraph at lines 46--46 +[]\OT1/cmtt/m/n/12 trunk/Identity/Themes/$THEME/Distro/Anaconda/Prompt/img/$VER +SION/[] + [] + + +Overfull \hbox (11.3752pt too wide) in paragraph at lines 69--69 +[]\OT1/cmtt/m/n/12 trunk/Identity/Themes/$THEME/Distro/Anaconda/Prompt/img/$VER +SION/[] + [] + +) (../../../../../Licenses/GFDL.tex +Underfull \hbox (badness 10000) in paragraph at lines 5--14 + + [] + +[21] [22] [23] [24] [25] [26] [27] [28] [29] +Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 document under the terms of the GNU Free Documentation Li +cense,[] + [] + + +Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 Version 1.2 or any later version published by the Free So +ftware[] + [] + + +Overfull \hbox (5.2002pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 Foundation; with no Invariant Sections, no Front-Cover Te +xts,[] + [] + + +Overfull \hbox (11.3752pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 and no Back-Cover Texts. A copy of the license is includ +ed in[] + [] + + +Overfull \hbox (5.2002pt too wide) in paragraph at lines 425--425 +[] \OT1/cmtt/m/n/12 with the Invariant Sections being LIST THEIR TITLES, with + the[] + [] + +[30]) [31] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 2918 strings out of 94500 + 40182 string characters out of 1176766 + 91201 words of memory out of 1000000 + 5947 multiletter control sequences out of 10000+50000 + 11266 words of font info for 40 fonts, out of 500000 for 2000 + 582 hyphenation exceptions out of 1000 + 27i,8n,36p,274b,267s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 551 PDF objects out of 300000 + 112 named destinations out of 131072 + 520 words of extra memory for PDF output out of 65536 + + +Output written on Manual.pdf (31 pages, 313018 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.out new file mode 100644 index 0000000..5f4414a --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.out @@ -0,0 +1,61 @@ +\BOOKMARK [1][-]{section.1}{Introduction}{} +\BOOKMARK [1][-]{section.2}{Installation}{} +\BOOKMARK [2][-]{subsection.2.1}{Subversion}{section.2} +\BOOKMARK [2][-]{subsection.2.2}{Inkscape}{section.2} +\BOOKMARK [2][-]{subsection.2.3}{ImageMagick}{section.2} +\BOOKMARK [2][-]{subsection.2.4}{Netpbm}{section.2} +\BOOKMARK [2][-]{subsection.2.5}{Syslinux}{section.2} +\BOOKMARK [2][-]{subsection.2.6}{GNU Image Manipulation Program}{section.2} +\BOOKMARK [2][-]{subsection.2.7}{GNU Core Utilities}{section.2} +\BOOKMARK [2][-]{subsection.2.8}{LaTeX}{section.2} +\BOOKMARK [1][-]{section.3}{Configuration}{} +\BOOKMARK [2][-]{subsection.3.1}{Firewall}{section.3} +\BOOKMARK [2][-]{subsection.3.2}{Subversion Behind Squid}{section.3} +\BOOKMARK [3][-]{subsubsection.3.2.1}{Subversion Client Configuration}{subsection.3.2} +\BOOKMARK [3][-]{subsubsection.3.2.2}{Squid Server Configuration}{subsection.3.2} +\BOOKMARK [2][-]{subsection.3.3}{Working Copy}{section.3} +\BOOKMARK [2][-]{subsection.3.4}{User Identification}{section.3} +\BOOKMARK [3][-]{subsubsection.3.4.1}{Account Registration}{subsection.3.4} +\BOOKMARK [3][-]{subsubsection.3.4.2}{Account Privileges}{subsection.3.4} +\BOOKMARK [2][-]{subsection.3.5}{Shell Environment}{section.3} +\BOOKMARK [3][-]{subsubsection.3.5.1}{Relative Paths}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.2}{Absolute Paths}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.3}{Environment Variable Definition}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.4}{Environment Variable Initialization}{subsection.3.5} +\BOOKMARK [1][-]{section.4}{Framework}{} +\BOOKMARK [2][-]{subsection.4.1}{Identity}{section.4} +\BOOKMARK [3][-]{subsubsection.4.1.1}{Designs}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.2}{Export Id}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.3}{Markers}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.4}{Images}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.5}{Color Limitations}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.6}{Color Palettes}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.7}{Models}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.8}{Rendering}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.9}{Issues}{subsection.4.1} +\BOOKMARK [2][-]{subsection.4.2}{Translations}{section.4} +\BOOKMARK [3][-]{subsubsection.4.2.1}{Common Translations}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.2}{Specific Translations}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.3}{Translation Path}{subsection.4.2} +\BOOKMARK [2][-]{subsection.4.3}{Manuals}{section.4} +\BOOKMARK [2][-]{subsection.4.4}{Scripts}{section.4} +\BOOKMARK [3][-]{subsubsection.4.4.1}{Rendering}{subsection.4.4} +\BOOKMARK [3][-]{subsubsection.4.4.2}{Pre-rendering}{subsection.4.4} +\BOOKMARK [3][-]{subsubsection.4.4.3}{Post-rendering}{subsection.4.4} +\BOOKMARK [1][-]{section.5}{Rebranding}{} +\BOOKMARK [2][-]{subsection.5.1}{Images}{section.5} +\BOOKMARK [3][-]{subsubsection.5.1.1}{redhat-logos}{subsection.5.1} +\BOOKMARK [2][-]{subsection.5.2}{Syslinux}{section.5} +\BOOKMARK [2][-]{subsection.5.3}{Messages Locale}{section.5} +\BOOKMARK [1][-]{section.6}{GNU Free Documentation License}{} +\BOOKMARK [2][-]{subsection.6.1}{Applicability And Definitions}{section.6} +\BOOKMARK [2][-]{subsection.6.2}{Verbatim Copying}{section.6} +\BOOKMARK [2][-]{subsection.6.3}{Copying In Quantity}{section.6} +\BOOKMARK [2][-]{subsection.6.4}{Modifications}{section.6} +\BOOKMARK [2][-]{subsection.6.5}{Combining Documents}{section.6} +\BOOKMARK [2][-]{subsection.6.6}{Collections Of Documents}{section.6} +\BOOKMARK [2][-]{subsection.6.7}{Aggregation With Independent Works}{section.6} +\BOOKMARK [2][-]{subsection.6.8}{Translation}{section.6} +\BOOKMARK [2][-]{subsection.6.9}{Termination}{section.6} +\BOOKMARK [2][-]{subsection.6.10}{Future Revisions Of This License}{section.6} +\BOOKMARK [2][-]{subsection.6.11}{How to use this License for your documents}{section.6} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.pdf new file mode 100644 index 0000000..e673587 Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.toc new file mode 100644 index 0000000..195feab --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/Manual.toc @@ -0,0 +1,61 @@ +\contentsline {section}{\numberline {1}Introduction}{3}{section.1} +\contentsline {section}{\numberline {2}Installation}{3}{section.2} +\contentsline {subsection}{\numberline {2.1}Subversion}{4}{subsection.2.1} +\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2} +\contentsline {subsection}{\numberline {2.3}ImageMagick}{5}{subsection.2.3} +\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4} +\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5} +\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{6}{subsection.2.6} +\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7} +\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8} +\contentsline {section}{\numberline {3}Configuration}{6}{section.3} +\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1} +\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2} +\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1} +\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2} +\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3} +\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4} +\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{9}{subsubsection.3.4.1} +\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2} +\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5} +\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1} +\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2} +\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3} +\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4} +\contentsline {section}{\numberline {4}Framework}{10}{section.4} +\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1} +\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1} +\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2} +\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3} +\contentsline {subsubsection}{\numberline {4.1.4}Images}{12}{subsubsection.4.1.4} +\contentsline {subsubsection}{\numberline {4.1.5}Color Limitations}{12}{subsubsection.4.1.5} +\contentsline {subsubsection}{\numberline {4.1.6}Color Palettes}{12}{subsubsection.4.1.6} +\contentsline {subsubsection}{\numberline {4.1.7}Models}{14}{subsubsection.4.1.7} +\contentsline {subsubsection}{\numberline {4.1.8}Rendering}{14}{subsubsection.4.1.8} +\contentsline {subsubsection}{\numberline {4.1.9}Issues}{15}{subsubsection.4.1.9} +\contentsline {subsection}{\numberline {4.2}Translations}{16}{subsection.4.2} +\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{16}{subsubsection.4.2.1} +\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{16}{subsubsection.4.2.2} +\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{16}{subsubsection.4.2.3} +\contentsline {subsection}{\numberline {4.3}Manuals}{18}{subsection.4.3} +\contentsline {subsection}{\numberline {4.4}Scripts}{18}{subsection.4.4} +\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{18}{subsubsection.4.4.1} +\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{18}{subsubsection.4.4.2} +\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{18}{subsubsection.4.4.3} +\contentsline {section}{\numberline {5}Rebranding}{20}{section.5} +\contentsline {subsection}{\numberline {5.1}Images}{20}{subsection.5.1} +\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{20}{subsubsection.5.1.1} +\contentsline {subsection}{\numberline {5.2}Syslinux}{21}{subsection.5.2} +\contentsline {subsection}{\numberline {5.3}Messages Locale}{21}{subsection.5.3} +\contentsline {section}{\numberline {6}GNU Free Documentation License}{22}{section.6} +\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{22}{subsection.6.1} +\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{24}{subsection.6.2} +\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{25}{subsection.6.3} +\contentsline {subsection}{\numberline {6.4}Modifications}{25}{subsection.6.4} +\contentsline {subsection}{\numberline {6.5}Combining Documents}{28}{subsection.6.5} +\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{28}{subsection.6.6} +\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{29}{subsection.6.7} +\contentsline {subsection}{\numberline {6.8}Translation}{29}{subsection.6.8} +\contentsline {subsection}{\numberline {6.9}Termination}{30}{subsection.6.9} +\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{30}{subsection.6.10} +\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{30}{subsection.6.11} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/manual.tex new file mode 100644 index 0000000..e46842a --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Prompt/manual.tex @@ -0,0 +1,56 @@ +\documentclass[12pt]{article} +\usepackage{longtable} +\usepackage[pdftex]{graphicx} +\usepackage{hyperref} +\hypersetup{pdfauthor={Alain Reguera Delgado},% + pdftitle={Anaconda Prompt Visual Style},% + pdfsubject={CentOS Corporate Visual Identity}% + } + +% Tell LaTeX how to hyphenate a word. Don't hyphenate the following +% words: +\hyphenation{CentOS CENTOSARTWORK} + +\title{Anaconda Prompt Visual Style} +\author{Alain Reguera Delgado} + +\begin{document} + +\maketitle + +\begin{abstract} + +This article describes Anaconda Prompt. Anaconda Prompt is the first +screen shown after booting up with the install CD/DVD medium. Anaconda +Prompt is based on H. Peter Anvin's syslinux suite of bootloaders, +specifically on the \texttt{isolinux} bootloader. The +\texttt{syslinux} suite and its documentation come inside the +\texttt{syslinux} package, available through \texttt{yum} in the +\texttt{[base]} repository of CentOS Distribution. + +Anaconda is the name of the install program used by CentOS. It is +python-based with some custom modules written in C. The anaconda +installer works on a wide variety of Linux-based computing +architectures (ia32, Itanium, Alpha, S/390, PowerPC), and is designed +to make it easy to add platforms. + +Copyright (C) 2010 The CentOS Project. Permission is granted to copy, +distribute and/or modify this document under the terms of the GNU Free +Documentation License, Version 1.2 or any later version published by +the Free Software Foundation; with no Invariant Sections, no +Front-Cover Texts, and no Back-Cover Texts. A copy of the license is +included in the section entitled ``GNU Free Documentation License''. + +\end{abstract} + +\tableofcontents + +\input{sections/introduction.tex} +\input{../../../../../installation.tex} +\input{../../../../../configuration.tex} +\input{sections/framework.tex} +\input{sections/rebranding.tex} + +\input{../../../../../Licenses/GFDL.tex} + +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.aux new file mode 100644 index 0000000..bb89e14 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.aux @@ -0,0 +1,97 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{3}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Installation}{3}{section.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}Subversion}{3}{subsection.2.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}ImageMagick}{4}{subsection.2.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{5}{subsection.2.6}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7}} +\@writefile{toc}{\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Configuration}{6}{section.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{9}{subsubsection.3.4.1}} +\newlabel{sec:Configuration:Account}{{3.4.1}{9}{Account Registration\relax }{subsubsection.3.4.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2}} +\newlabel{sec:Configuration:User:Privileges}{{3.4.2}{9}{Account Privileges\relax }{subsubsection.3.4.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5}} +\newlabel{sec:Configuration:Environment}{{3.5}{9}{Shell Environment\relax }{subsection.3.5}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Framework}{10}{section.4}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1}} +\newlabel{sec:Identity}{{4.1}{10}{Identity\relax }{subsection.4.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3}} +\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Anaconda Splash translation markers.}}{12}{table.1}} +\newlabel{tab:Identity:Markers}{{1}{12}{Markers\relax }{table.1}{}} +\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces Anaconda Splash design model.}}{12}{figure.1}} +\newlabel{fig:Identity:Design:Model}{{1}{12}{Models\relax }{figure.1}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.4}Images}{12}{subsubsection.4.1.4}} +\newlabel{sec:Identity:Images}{{4.1.4}{12}{Images\relax }{subsubsection.4.1.4}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.5}Models}{12}{subsubsection.4.1.5}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.1.6}Rendering}{13}{subsubsection.4.1.6}} +\newlabel{sec:Identity:Rendering}{{4.1.6}{13}{Rendering\relax }{subsubsection.4.1.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.2}Translations}{13}{subsection.4.2}} +\newlabel{sec:Translations}{{4.2}{13}{Translations\relax }{subsection.4.2}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{13}{subsubsection.4.2.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{13}{subsubsection.4.2.2}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{14}{subsubsection.4.2.3}} +\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces Anaconda Splash translation path.}}{14}{figure.2}} +\newlabel{fig:Translation:Path}{{2}{14}{Translation Path\relax }{figure.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}Manuals}{15}{subsection.4.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Scripts}{15}{subsection.4.4}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{15}{subsubsection.4.4.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{15}{subsubsection.4.4.2}} +\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Rendering design model.}}{16}{figure.3}} +\newlabel{fig:Scripts:Rendering}{{3}{16}{Rendering\relax }{figure.3}{}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{17}{subsubsection.4.4.3}} +\@writefile{toc}{\contentsline {section}{\numberline {5}Rebranding}{17}{section.5}} +\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}Images}{18}{subsection.5.1}} +\@writefile{toc}{\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{18}{subsubsection.5.1.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Messages Locale}{18}{subsection.5.2}} +\@writefile{toc}{\contentsline {section}{\numberline {6}GNU Free Documentation License}{18}{section.6}} +\newlabel{sec:License-GFDL-0}{{6}{19}{Preamble\relax }{section*.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{19}{subsection.6.1}} +\newlabel{sec:License-GFDL-1}{{6.1}{19}{Applicability And Definitions\relax }{subsection.6.1}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{21}{subsection.6.2}} +\newlabel{sec:License-GFDL-2}{{6.2}{21}{Verbatim Copying\relax }{subsection.6.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{21}{subsection.6.3}} +\newlabel{sec:License-GFDL-3}{{6.3}{21}{Copying In Quantity\relax }{subsection.6.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.4}Modifications}{22}{subsection.6.4}} +\newlabel{sec:License-GFDL-4}{{6.4}{22}{Modifications\relax }{subsection.6.4}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.5}Combining Documents}{25}{subsection.6.5}} +\newlabel{sec:License-GFDL-5}{{6.5}{25}{Combining Documents\relax }{subsection.6.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{25}{subsection.6.6}} +\newlabel{sec:License-GFDL-6}{{6.6}{25}{Collections Of Documents\relax }{subsection.6.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{25}{subsection.6.7}} +\newlabel{sec:License-GFDL-7}{{6.7}{25}{Aggregation With Independent Works\relax }{subsection.6.7}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.8}Translation}{26}{subsection.6.8}} +\newlabel{sec:License-GFDL-8}{{6.8}{26}{Translation\relax }{subsection.6.8}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.9}Termination}{26}{subsection.6.9}} +\newlabel{sec:License-GFDL-9}{{6.9}{26}{Termination\relax }{subsection.6.9}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{27}{subsection.6.10}} +\newlabel{sec:License-GFDL-10}{{6.10}{27}{Future Revisions Of This License\relax }{subsection.6.10}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{27}{subsection.6.11}} +\newlabel{sec:License-GFDL-11}{{6.11}{27}{How to use this License for your documents\relax }{subsection.6.11}{}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.log new file mode 100644 index 0000000..2c24e55 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.log @@ -0,0 +1,361 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 12 MAR 2010 14:17 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size12.clo +File: size12.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/tools/longtable.sty +Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) +\LTleft=\skip43 +\LTright=\skip44 +\LTpre=\skip45 +\LTpost=\skip46 +\LTchunksize=\count87 +\LTcapwidth=\dimen103 +\LT@head=\box26 +\LT@firsthead=\box27 +\LT@foot=\box28 +\LT@lastfoot=\box29 +\LT@cols=\count88 +\LT@rows=\count89 +\c@LT@tables=\count90 +\c@LT@chunks=\count91 +\LT@p@ftn=\toks14 +) +(/usr/share/texmf/tex/latex/graphics/graphicx.sty +Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks15 +) +(/usr/share/texmf/tex/latex/graphics/graphics.sty +Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/trig.sty +Package: trig 1999/03/16 v1.09 sin cos tan (DPC) +) +(/usr/share/texmf/tex/latex/graphics/graphics.cfg +File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive +) +Package graphics Info: Driver file: pdftex.def on input line 80. + +(/usr/share/texmf/tex/latex/graphics/pdftex.def +File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex +\Gread@gobject=\count92 +)) +\Gin@req@height=\dimen104 +\Gin@req@width=\dimen105 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX +\@linkdim=\dimen106 +\Hy@linkcounter=\count93 +\Hy@pagecounter=\count94 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count95 +\Field@Width=\dimen107 +\Fld@charsize=\dimen108 +\Choice@toks=\toks16 +\Field@toks=\toks17 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count96 +\c@Hfootnote=\count97 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count98 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 17. +LaTeX Font Info: ... okay on input line 17. + +(/usr/share/texmf/tex/context/base/supp-pdf.tex +(/usr/share/texmf/tex/context/base/supp-mis.tex +loading : Context Support Macros / Miscellaneous (2004.10.26) +\protectiondepth=\count99 +\scratchcounter=\count100 +\scratchtoks=\toks18 +\scratchdimen=\dimen109 +\scratchskip=\skip47 +\scratchmuskip=\muskip11 +\scratchbox=\box30 +\scratchread=\read1 +\scratchwrite=\write4 +\zeropoint=\dimen110 +\onepoint=\dimen111 +\onebasepoint=\dimen112 +\minusone=\count101 +\thousandpoint=\dimen113 +\onerealpoint=\dimen114 +\emptytoks=\toks19 +\nextbox=\box31 +\nextdepth=\dimen115 +\everyline=\toks20 +\!!counta=\count102 +\!!countb=\count103 +\recursecounter=\count104 +) +loading : Context Support Macros / PDF (2004.03.26) +\nofMPsegments=\count105 +\nofMParguments=\count106 +\MPscratchCnt=\count107 +\MPscratchDim=\dimen116 +\MPnumerator=\count108 +\everyMPtoPDFconversion=\toks21 +) +Package hyperref Info: Link coloring OFF on input line 17. + (/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count109 +) +LaTeX Info: Redefining \ref on input line 17. +LaTeX Info: Redefining \pageref on input line 17. + (./Manual.out) +(./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <14.4> on input line 20. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 20. + (./Manual.toc +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 3. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 3. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 3. + [1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] [2]) +\tf@toc=\write5 +\openout5 = `Manual.toc'. + + (./sections/introduction.tex) (../../../../../installation.tex +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 25. + +[3] +Overfull \hbox (8.37456pt too wide) in paragraph at lines 53--54 +[][]$\OT1/cmtt/m/n/12 http : / / wiki . centos . org / AdditionalResources / Re +positories$[] + [] + +Missing character: There is no � in font cmr12! +Missing character: There is no � in font cmr12! +[4] +LaTeX Font Info: Try loading font information for OMS+cmr on input line 94. + (/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <12> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 94. + [5]) +(../../../../../configuration.tex [6] +Overfull \hbox (11.3752pt too wide) in paragraph at lines 60--60 +[]\OT1/cmtt/m/n/12 # Squid only knows about standardized HTTP request met +hods.[] + [] + + +Overfull \hbox (11.3752pt too wide) in paragraph at lines 60--60 +[]\OT1/cmtt/m/n/12 # You can add up to 20 additional "extension" methods +here.[] + [] + +[7] +Overfull \hbox (23.88292pt too wide) in paragraph at lines 92--93 +[]\OT1/cmtt/m/n/12 svn co https://projects.centos.org/svn/artwork $\OMS/cmsy/m/ +n/12 ^^X$\OT1/cmtt/m/n/12 /Desktop/ + [] + +[8] +LaTeX Font Info: Font shape `OT1/cmtt/bx/n' in size <12> not available +(Font) Font shape `OT1/cmtt/m/n' tried instead on input line 162. + [9]) (./sections/framework.tex +Underfull \hbox (badness 10000) in paragraph at lines 10--11 + + [] + +[10] +Overfull \hbox (15.76491pt too wide) in paragraph at lines 51--56 +\OT1/cmr/m/n/12 ex-ported as PNG im-age. As con-ven-tion, we use the word `CENT +OSARTWORK' + [] + +[11] +Underfull \hbox (badness 10000) in paragraph at lines 94--95 + + [] + + +<../../../../../../Identity/Models/Distro/Anaconda/Splash/img/build-0.pdf, id=3 +87, 691.58376pt x 481.8pt> +File: ../../../../../../Identity/Models/Distro/Anaconda/Splash/img/build-0.pdf +Graphic file (type pdf) + + +[12 <../../../../../../Identity/Models/Distro/Anaconda/Splash/img/build-0.pdf>] + +Underfull \hbox (badness 10000) in paragraph at lines 132--133 + + [] + +[13] [14] +Underfull \hbox (badness 10000) in paragraph at lines 217--218 + + [] + + +<../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf, id=416, 5 +29.98pt x 589.20125pt> +File: ../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf Graph +ic file (type pdf) + + +Underfull \hbox (badness 10000) in paragraph at lines 245--246 + + [] + +[15] [16 <../../../../../../Identity/Models/Scripts/Rendering/img/build-0.pdf>] +) (./sections/rebranding.tex +Overfull \hbox (2.56557pt too wide) in paragraph at lines 12--15 +[]\OT1/cmr/m/n/12 CentOS Brands and art-works are or-ga-nized in-side CentOS Ar +t-work Repos- + [] + +[17] +Overfull \hbox (11.3752pt too wide) in paragraph at lines 46--46 +[]\OT1/cmtt/m/n/12 trunk/Identity/Themes/$THEME/Distro/Anaconda/Splash/img/$VER +SION/[] + [] + +) (../../../../../Licenses/GFDL.tex +Underfull \hbox (badness 10000) in paragraph at lines 5--14 + + [] + +[18] [19] [20] [21] [22] [23] [24] [25] [26] +Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 document under the terms of the GNU Free Documentation Li +cense,[] + [] + + +Overfull \hbox (17.5502pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 Version 1.2 or any later version published by the Free So +ftware[] + [] + + +Overfull \hbox (5.2002pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 Foundation; with no Invariant Sections, no Front-Cover Te +xts,[] + [] + + +Overfull \hbox (11.3752pt too wide) in paragraph at lines 416--416 +[] \OT1/cmtt/m/n/12 and no Back-Cover Texts. A copy of the license is includ +ed in[] + [] + + +Overfull \hbox (5.2002pt too wide) in paragraph at lines 425--425 +[] \OT1/cmtt/m/n/12 with the Invariant Sections being LIST THEIR TITLES, with + the[] + [] + +) [27] [28] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 2888 strings out of 94500 + 39538 string characters out of 1176766 + 91110 words of memory out of 1000000 + 5934 multiletter control sequences out of 10000+50000 + 10751 words of font info for 38 fonts, out of 500000 for 2000 + 582 hyphenation exceptions out of 1000 + 27i,8n,36p,222b,267s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 495 PDF objects out of 300000 + 97 named destinations out of 131072 + 483 words of extra memory for PDF output out of 65536 + +Output written on Manual.pdf (28 pages, 272117 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.out new file mode 100644 index 0000000..9b9b706 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.out @@ -0,0 +1,57 @@ +\BOOKMARK [1][-]{section.1}{Introduction}{} +\BOOKMARK [1][-]{section.2}{Installation}{} +\BOOKMARK [2][-]{subsection.2.1}{Subversion}{section.2} +\BOOKMARK [2][-]{subsection.2.2}{Inkscape}{section.2} +\BOOKMARK [2][-]{subsection.2.3}{ImageMagick}{section.2} +\BOOKMARK [2][-]{subsection.2.4}{Netpbm}{section.2} +\BOOKMARK [2][-]{subsection.2.5}{Syslinux}{section.2} +\BOOKMARK [2][-]{subsection.2.6}{GNU Image Manipulation Program}{section.2} +\BOOKMARK [2][-]{subsection.2.7}{GNU Core Utilities}{section.2} +\BOOKMARK [2][-]{subsection.2.8}{LaTeX}{section.2} +\BOOKMARK [1][-]{section.3}{Configuration}{} +\BOOKMARK [2][-]{subsection.3.1}{Firewall}{section.3} +\BOOKMARK [2][-]{subsection.3.2}{Subversion Behind Squid}{section.3} +\BOOKMARK [3][-]{subsubsection.3.2.1}{Subversion Client Configuration}{subsection.3.2} +\BOOKMARK [3][-]{subsubsection.3.2.2}{Squid Server Configuration}{subsection.3.2} +\BOOKMARK [2][-]{subsection.3.3}{Working Copy}{section.3} +\BOOKMARK [2][-]{subsection.3.4}{User Identification}{section.3} +\BOOKMARK [3][-]{subsubsection.3.4.1}{Account Registration}{subsection.3.4} +\BOOKMARK [3][-]{subsubsection.3.4.2}{Account Privileges}{subsection.3.4} +\BOOKMARK [2][-]{subsection.3.5}{Shell Environment}{section.3} +\BOOKMARK [3][-]{subsubsection.3.5.1}{Relative Paths}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.2}{Absolute Paths}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.3}{Environment Variable Definition}{subsection.3.5} +\BOOKMARK [3][-]{subsubsection.3.5.4}{Environment Variable Initialization}{subsection.3.5} +\BOOKMARK [1][-]{section.4}{Framework}{} +\BOOKMARK [2][-]{subsection.4.1}{Identity}{section.4} +\BOOKMARK [3][-]{subsubsection.4.1.1}{Designs}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.2}{Export Id}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.3}{Markers}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.4}{Images}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.5}{Models}{subsection.4.1} +\BOOKMARK [3][-]{subsubsection.4.1.6}{Rendering}{subsection.4.1} +\BOOKMARK [2][-]{subsection.4.2}{Translations}{section.4} +\BOOKMARK [3][-]{subsubsection.4.2.1}{Common Translations}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.2}{Specific Translations}{subsection.4.2} +\BOOKMARK [3][-]{subsubsection.4.2.3}{Translation Path}{subsection.4.2} +\BOOKMARK [2][-]{subsection.4.3}{Manuals}{section.4} +\BOOKMARK [2][-]{subsection.4.4}{Scripts}{section.4} +\BOOKMARK [3][-]{subsubsection.4.4.1}{Rendering}{subsection.4.4} +\BOOKMARK [3][-]{subsubsection.4.4.2}{Pre-rendering}{subsection.4.4} +\BOOKMARK [3][-]{subsubsection.4.4.3}{Post-rendering}{subsection.4.4} +\BOOKMARK [1][-]{section.5}{Rebranding}{} +\BOOKMARK [2][-]{subsection.5.1}{Images}{section.5} +\BOOKMARK [3][-]{subsubsection.5.1.1}{redhat-logos}{subsection.5.1} +\BOOKMARK [2][-]{subsection.5.2}{Messages Locale}{section.5} +\BOOKMARK [1][-]{section.6}{GNU Free Documentation License}{} +\BOOKMARK [2][-]{subsection.6.1}{Applicability And Definitions}{section.6} +\BOOKMARK [2][-]{subsection.6.2}{Verbatim Copying}{section.6} +\BOOKMARK [2][-]{subsection.6.3}{Copying In Quantity}{section.6} +\BOOKMARK [2][-]{subsection.6.4}{Modifications}{section.6} +\BOOKMARK [2][-]{subsection.6.5}{Combining Documents}{section.6} +\BOOKMARK [2][-]{subsection.6.6}{Collections Of Documents}{section.6} +\BOOKMARK [2][-]{subsection.6.7}{Aggregation With Independent Works}{section.6} +\BOOKMARK [2][-]{subsection.6.8}{Translation}{section.6} +\BOOKMARK [2][-]{subsection.6.9}{Termination}{section.6} +\BOOKMARK [2][-]{subsection.6.10}{Future Revisions Of This License}{section.6} +\BOOKMARK [2][-]{subsection.6.11}{How to use this License for your documents}{section.6} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.pdf new file mode 100644 index 0000000..d79853a Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.toc new file mode 100644 index 0000000..170bf03 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/Manual.toc @@ -0,0 +1,57 @@ +\contentsline {section}{\numberline {1}Introduction}{3}{section.1} +\contentsline {section}{\numberline {2}Installation}{3}{section.2} +\contentsline {subsection}{\numberline {2.1}Subversion}{3}{subsection.2.1} +\contentsline {subsection}{\numberline {2.2}Inkscape}{4}{subsection.2.2} +\contentsline {subsection}{\numberline {2.3}ImageMagick}{4}{subsection.2.3} +\contentsline {subsection}{\numberline {2.4}Netpbm}{5}{subsection.2.4} +\contentsline {subsection}{\numberline {2.5}Syslinux}{5}{subsection.2.5} +\contentsline {subsection}{\numberline {2.6}GNU Image Manipulation Program}{5}{subsection.2.6} +\contentsline {subsection}{\numberline {2.7}GNU Core Utilities}{6}{subsection.2.7} +\contentsline {subsection}{\numberline {2.8}\LaTeX }{6}{subsection.2.8} +\contentsline {section}{\numberline {3}Configuration}{6}{section.3} +\contentsline {subsection}{\numberline {3.1}Firewall}{6}{subsection.3.1} +\contentsline {subsection}{\numberline {3.2}Subversion Behind Squid}{7}{subsection.3.2} +\contentsline {subsubsection}{\numberline {3.2.1}Subversion Client Configuration}{7}{subsubsection.3.2.1} +\contentsline {subsubsection}{\numberline {3.2.2}Squid Server Configuration}{7}{subsubsection.3.2.2} +\contentsline {subsection}{\numberline {3.3}Working Copy}{7}{subsection.3.3} +\contentsline {subsection}{\numberline {3.4}User Identification}{8}{subsection.3.4} +\contentsline {subsubsection}{\numberline {3.4.1}Account Registration}{9}{subsubsection.3.4.1} +\contentsline {subsubsection}{\numberline {3.4.2}Account Privileges}{9}{subsubsection.3.4.2} +\contentsline {subsection}{\numberline {3.5}Shell Environment}{9}{subsection.3.5} +\contentsline {subsubsection}{\numberline {3.5.1}Relative Paths}{9}{subsubsection.3.5.1} +\contentsline {subsubsection}{\numberline {3.5.2}Absolute Paths}{9}{subsubsection.3.5.2} +\contentsline {subsubsection}{\numberline {3.5.3}Environment Variable Definition}{9}{subsubsection.3.5.3} +\contentsline {subsubsection}{\numberline {3.5.4}Environment Variable Initialization}{10}{subsubsection.3.5.4} +\contentsline {section}{\numberline {4}Framework}{10}{section.4} +\contentsline {subsection}{\numberline {4.1}Identity}{10}{subsection.4.1} +\contentsline {subsubsection}{\numberline {4.1.1}Designs}{10}{subsubsection.4.1.1} +\contentsline {subsubsection}{\numberline {4.1.2}Export Id}{11}{subsubsection.4.1.2} +\contentsline {subsubsection}{\numberline {4.1.3}Markers}{11}{subsubsection.4.1.3} +\contentsline {subsubsection}{\numberline {4.1.4}Images}{12}{subsubsection.4.1.4} +\contentsline {subsubsection}{\numberline {4.1.5}Models}{12}{subsubsection.4.1.5} +\contentsline {subsubsection}{\numberline {4.1.6}Rendering}{13}{subsubsection.4.1.6} +\contentsline {subsection}{\numberline {4.2}Translations}{13}{subsection.4.2} +\contentsline {subsubsection}{\numberline {4.2.1}Common Translations}{13}{subsubsection.4.2.1} +\contentsline {subsubsection}{\numberline {4.2.2}Specific Translations}{13}{subsubsection.4.2.2} +\contentsline {subsubsection}{\numberline {4.2.3}Translation Path}{14}{subsubsection.4.2.3} +\contentsline {subsection}{\numberline {4.3}Manuals}{15}{subsection.4.3} +\contentsline {subsection}{\numberline {4.4}Scripts}{15}{subsection.4.4} +\contentsline {subsubsection}{\numberline {4.4.1}Rendering}{15}{subsubsection.4.4.1} +\contentsline {subsubsection}{\numberline {4.4.2}Pre-rendering}{15}{subsubsection.4.4.2} +\contentsline {subsubsection}{\numberline {4.4.3}Post-rendering}{17}{subsubsection.4.4.3} +\contentsline {section}{\numberline {5}Rebranding}{17}{section.5} +\contentsline {subsection}{\numberline {5.1}Images}{18}{subsection.5.1} +\contentsline {subsubsection}{\numberline {5.1.1}redhat-logos}{18}{subsubsection.5.1.1} +\contentsline {subsection}{\numberline {5.2}Messages Locale}{18}{subsection.5.2} +\contentsline {section}{\numberline {6}GNU Free Documentation License}{18}{section.6} +\contentsline {subsection}{\numberline {6.1}Applicability And Definitions}{19}{subsection.6.1} +\contentsline {subsection}{\numberline {6.2}Verbatim Copying}{21}{subsection.6.2} +\contentsline {subsection}{\numberline {6.3}Copying In Quantity}{21}{subsection.6.3} +\contentsline {subsection}{\numberline {6.4}Modifications}{22}{subsection.6.4} +\contentsline {subsection}{\numberline {6.5}Combining Documents}{25}{subsection.6.5} +\contentsline {subsection}{\numberline {6.6}Collections Of Documents}{25}{subsection.6.6} +\contentsline {subsection}{\numberline {6.7}Aggregation With Independent Works}{25}{subsection.6.7} +\contentsline {subsection}{\numberline {6.8}Translation}{26}{subsection.6.8} +\contentsline {subsection}{\numberline {6.9}Termination}{26}{subsection.6.9} +\contentsline {subsection}{\numberline {6.10}Future Revisions Of This License}{27}{subsection.6.10} +\contentsline {subsection}{\numberline {6.11}How to use this License for your documents}{27}{subsection.6.11} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/manual.tex new file mode 100644 index 0000000..e9f2c56 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Anaconda/Splash/manual.tex @@ -0,0 +1,51 @@ +\documentclass[12pt]{article} +\usepackage{longtable} +\usepackage[pdftex]{graphicx} +\usepackage{hyperref} +\hypersetup{pdfauthor={Alain Reguera Delgado},% + pdftitle={Anaconda Splash Visual Style},% + pdfsubject={CentOS Corporate Visual Identity}% + } + +% Tell LaTeX how to hyphenate a word. Don't hyphenate the following +% words: +\hyphenation{CentOS CENTOSARTWORK} + +\title{Anaconda Splash Visual Style} +\author{Alain Reguera Delgado} + +\begin{document} + +\maketitle + +\begin{abstract} + +This article describes Anaconda Splash screen. This screen is shown +after Anaconda Prompt screen. + +Anaconda is the name of the install program used by CentOS. It is +python-based with some custom modules written in C. The anaconda +installer works on a wide variety of Linux-based computing +architectures (ia32, Itanium, Alpha, S/390, PowerPC), and is designed +to make it easy to add platforms. + +Copyright (C) 2010 The CentOS Project. Permission is granted to copy, +distribute and/or modify this document under the terms of the GNU Free +Documentation License, Version 1.2 or any later version published by +the Free Software Foundation; with no Invariant Sections, no +Front-Cover Texts, and no Back-Cover Texts. A copy of the license is +included in the section entitled ``GNU Free Documentation License''. + +\end{abstract} + +\tableofcontents + +\input{sections/introduction.tex} +\input{../../../../../installation.tex} +\input{../../../../../configuration.tex} +\input{sections/framework.tex} +\input{sections/rebranding.tex} + +\input{../../../../../Licenses/GFDL.tex} + +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.aux new file mode 100644 index 0000000..3cbc687 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.aux @@ -0,0 +1,50 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\gdef \LT@i {\LT@entry + {1}{72.64pt}\LT@entry + {1}{297.61168pt}} +\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{2}{section.3}} +\gdef \LT@ii {\LT@entry + {1}{72.64pt}\LT@entry + {1}{261.17276pt}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Rendering}{3}{section.4}} +\@writefile{toc}{\contentsline {section}{\numberline {5}Configuration}{3}{section.5}} +\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{4}{section.6}} +\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{4}{section.7}} +\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{4}{section.8}} +\newlabel{sec:License-GFDL-0}{{8}{5}{Preamble\relax }{section*.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{5}{subsection.8.1}} +\newlabel{sec:License-GFDL-1}{{8.1}{5}{Applicability And Definitions\relax }{subsection.8.1}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{7}{subsection.8.2}} +\newlabel{sec:License-GFDL-2}{{8.2}{7}{Verbatim Copying\relax }{subsection.8.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{7}{subsection.8.3}} +\newlabel{sec:License-GFDL-3}{{8.3}{7}{Copying In Quantity\relax }{subsection.8.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{8}{subsection.8.4}} +\newlabel{sec:License-GFDL-4}{{8.4}{8}{Modifications\relax }{subsection.8.4}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{9}{subsection.8.5}} +\newlabel{sec:License-GFDL-5}{{8.5}{9}{Combining Documents\relax }{subsection.8.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{10}{subsection.8.6}} +\newlabel{sec:License-GFDL-6}{{8.6}{10}{Collections Of Documents\relax }{subsection.8.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{10}{subsection.8.7}} +\newlabel{sec:License-GFDL-7}{{8.7}{10}{Aggregation With Independent Works\relax }{subsection.8.7}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{11}{subsection.8.8}} +\newlabel{sec:License-GFDL-8}{{8.8}{11}{Translation\relax }{subsection.8.8}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{11}{subsection.8.9}} +\newlabel{sec:License-GFDL-9}{{8.9}{11}{Termination\relax }{subsection.8.9}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{11}{subsection.8.10}} +\newlabel{sec:License-GFDL-10}{{8.10}{11}{Future Revisions OF This License\relax }{subsection.8.10}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{11}{subsection.8.11}} +\newlabel{sec:License-GFDL-11}{{8.11}{11}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.log new file mode 100644 index 0000000..ef922fd --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.log @@ -0,0 +1,315 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size10.clo +File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/tools/longtable.sty +Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) +\LTleft=\skip43 +\LTright=\skip44 +\LTpre=\skip45 +\LTpost=\skip46 +\LTchunksize=\count87 +\LTcapwidth=\dimen103 +\LT@head=\box26 +\LT@firsthead=\box27 +\LT@foot=\box28 +\LT@lastfoot=\box29 +\LT@cols=\count88 +\LT@rows=\count89 +\c@LT@tables=\count90 +\c@LT@chunks=\count91 +\LT@p@ftn=\toks14 +) +(/usr/share/texmf/tex/latex/graphics/graphicx.sty +Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks15 +) +(/usr/share/texmf/tex/latex/graphics/graphics.sty +Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/trig.sty +Package: trig 1999/03/16 v1.09 sin cos tan (DPC) +) +(/usr/share/texmf/tex/latex/graphics/graphics.cfg +File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive +) +Package graphics Info: Driver file: pdftex.def on input line 80. + +(/usr/share/texmf/tex/latex/graphics/pdftex.def +File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex +\Gread@gobject=\count92 +)) +\Gin@req@height=\dimen104 +\Gin@req@width=\dimen105 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX +\@linkdim=\dimen106 +\Hy@linkcounter=\count93 +\Hy@pagecounter=\count94 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count95 +\Field@Width=\dimen107 +\Fld@charsize=\dimen108 +\Choice@toks=\toks16 +\Field@toks=\toks17 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count96 +\c@Hfootnote=\count97 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count98 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. + +(/usr/share/texmf/tex/context/base/supp-pdf.tex +(/usr/share/texmf/tex/context/base/supp-mis.tex +loading : Context Support Macros / Miscellaneous (2004.10.26) +\protectiondepth=\count99 +\scratchcounter=\count100 +\scratchtoks=\toks18 +\scratchdimen=\dimen109 +\scratchskip=\skip47 +\scratchmuskip=\muskip11 +\scratchbox=\box30 +\scratchread=\read1 +\scratchwrite=\write4 +\zeropoint=\dimen110 +\onepoint=\dimen111 +\onebasepoint=\dimen112 +\minusone=\count101 +\thousandpoint=\dimen113 +\onerealpoint=\dimen114 +\emptytoks=\toks19 +\nextbox=\box31 +\nextdepth=\dimen115 +\everyline=\toks20 +\!!counta=\count102 +\!!countb=\count103 +\recursecounter=\count104 +) +loading : Context Support Macros / PDF (2004.03.26) +\nofMPsegments=\count105 +\nofMParguments=\count106 +\MPscratchCnt=\count107 +\MPscratchDim=\dimen116 +\MPnumerator=\count108 +\everyMPtoPDFconversion=\toks21 +) +Package hyperref Info: Link coloring OFF on input line 13. + (/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count109 +) +LaTeX Info: Redefining \ref on input line 13. +LaTeX Info: Redefining \pageref on input line 13. + (./Manual.out) +(./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 16. +LaTeX Font Info: Try loading font information for OMS+cmr on input line 23. + (/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 23. + (./Manual.toc +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 9. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 9. + +[1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) +\tf@toc=\write5 +\openout5 = `Manual.toc'. + +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 37. + +(./table-theme.tex +Overfull \hbox (25.25168pt too wide) in alignment at lines 1--23 + [] [] + [] + + +Underfull \vbox (badness 10000) detected at line 23 + [] + + +Overfull \hbox (25.25168pt too wide) in alignment at lines 23--29 + [] [] + [] + +) [2] (./table-config.tex +Underfull \vbox (badness 10000) detected at line 23 + [] + +) +Overfull \hbox (49.8004pt too wide) in paragraph at lines 62--67 +[]\OT1/cmr/m/n/10 : The \OT1/cmtt/m/n/10 desktop[]gnome[]background.schemas \OT +1/cmr/m/n/10 and \OT1/cmtt/m/n/10 %gconf-tree.xml + [] + + +Overfull \hbox (26.49701pt too wide) in paragraph at lines 86--86 + [] \OT1/cmtt/m/n/10 2| /schemas/desktop/gnome/background/picture_filenam +e[] + [] + + +Overfull \hbox (26.49701pt too wide) in paragraph at lines 86--86 + [] \OT1/cmtt/m/n/10 3| /desktop/gnome/background/picture_filename[] + [] + + +Overfull \hbox (21.24706pt too wide) in paragraph at lines 86--86 + [] \OT1/cmtt/m/n/10 6| /usr/share/backgrounds/images/default.png[] + [] + +[3] +Overfull \hbox (189.24559pt too wide) in paragraph at lines 102--102 + []\OT1/cmtt/m/n/10 1| [] + [] + + +Overfull \hbox (5.4972pt too wide) in paragraph at lines 102--102 + []\OT1/cmtt/m/n/10 2| [] + [] + + +Overfull \hbox (105.24632pt too wide) in paragraph at lines 102--102 + []\OT1/cmtt/m/n/10 4| /usr/share/backgrounds/images/def +ault.png[] + [] + + +Overfull \hbox (31.74696pt too wide) in paragraph at lines 102--102 + []\OT1/cmtt/m/n/10 6| File to use for the background image[] + [] + +(../../../../Licenses/GFDL.tex +Underfull \hbox (badness 10000) in paragraph at lines 5--14 + + [] + +[4] [5] +Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 +\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple + HTML, PostScript + [] + +[6] [7] [8] [9] [10] [11]) [12] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 2749 strings out of 94500 + 36599 string characters out of 1176766 + 89641 words of memory out of 1000000 + 5870 multiletter control sequences out of 10000+50000 + 9615 words of font info for 34 fonts, out of 500000 for 2000 + 580 hyphenation exceptions out of 1000 + 27i,6n,36p,222b,318s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 194 PDF objects out of 300000 + 36 named destinations out of 131072 + 169 words of extra memory for PDF output out of 65536 + +Output written on Manual.pdf (12 pages, 126301 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.out new file mode 100644 index 0000000..a194701 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.out @@ -0,0 +1,19 @@ +\BOOKMARK [1][-]{section.1}{Workplace}{} +\BOOKMARK [1][-]{section.2}{Theme}{} +\BOOKMARK [1][-]{section.3}{Design}{} +\BOOKMARK [1][-]{section.4}{Rendering}{} +\BOOKMARK [1][-]{section.5}{Configuration}{} +\BOOKMARK [1][-]{section.6}{Testing}{} +\BOOKMARK [1][-]{section.7}{Issues}{} +\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} +\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} +\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} +\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} +\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} +\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} +\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} +\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} +\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} +\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.pdf new file mode 100644 index 0000000..5b8a4c0 Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.toc new file mode 100644 index 0000000..17e027e --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/Manual.toc @@ -0,0 +1,19 @@ +\contentsline {section}{\numberline {1}Workplace}{2}{section.1} +\contentsline {section}{\numberline {2}Theme}{2}{section.2} +\contentsline {section}{\numberline {3}Design}{2}{section.3} +\contentsline {section}{\numberline {4}Rendering}{3}{section.4} +\contentsline {section}{\numberline {5}Configuration}{3}{section.5} +\contentsline {section}{\numberline {6}Testing}{4}{section.6} +\contentsline {section}{\numberline {7}Issues}{4}{section.7} +\contentsline {section}{\numberline {8}GNU Free Documentation License}{4}{section.8} +\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{5}{subsection.8.1} +\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{7}{subsection.8.2} +\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{7}{subsection.8.3} +\contentsline {subsection}{\numberline {8.4}Modifications}{8}{subsection.8.4} +\contentsline {subsection}{\numberline {8.5}Combining Documents}{9}{subsection.8.5} +\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{10}{subsection.8.6} +\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{10}{subsection.8.7} +\contentsline {subsection}{\numberline {8.8}Translation}{11}{subsection.8.8} +\contentsline {subsection}{\numberline {8.9}Termination}{11}{subsection.8.9} +\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{11}{subsection.8.10} +\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{11}{subsection.8.11} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/build.sh b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/build.sh new file mode 100755 index 0000000..c7286c4 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/build.sh @@ -0,0 +1,58 @@ +#!/bin/bash +# +# Build Background tables for LaTeX documents. +# +# Copyright (C) 2009 Alain Reguera Delgado +# +# 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:$ +#-------------------------------------- + +# Load dependencies. +. ~/artwork/trunk/Scripts/Bash/loadFunctions.sh + +# Define the names of your tables. +FILES="table-theme.tex + table-config.tex" + +for FILE in $FILES;do + + # Let know which table we are creating. + echo $FILE + + # Define what to do with each table you define on FILES. + case $FILE in + + table-theme.tex ) + # Create table holding theme files. + ROWS="$(getFiles '/usr/share/backgrounds' 'default.*\.(jpg|png)')" + ;; + + table-config.tex ) + # Create table holding configuration files. + ROWS="$(getFiles '/etc/gdm' '\.conf$' '/default\.(jpg|png)') + $(getFiles '/etc/gconf' '\.(schemas|xml)$' '/default.*\.(jpg|png)') + $(getFiles '/usr/share/config' 'rc$' 'default.*\.(jpg|png)')" + ;; + + esac + + # Create table. + createTable "$ROWS" "" "" > $FILE + +done diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/manual.tex new file mode 100644 index 0000000..64edf65 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/manual.tex @@ -0,0 +1,136 @@ +\documentclass{article} +\usepackage{longtable} +\usepackage[pdftex]{graphicx} +\usepackage{hyperref} +\hypersetup{pdfauthor={CentOS Documentation SIG},% + pdftitle={GNOME Backgrounds},% + pdfsubject={CentOS Corporate Visual Identity}% + } + +\title{Backgrounds} +\author{CentOS Documentation SIG} + +\begin{document} + +\maketitle + +\begin{abstract} +This article describes GNOME and KDE background images. The first +time a user's session has been loaded, the default background image is +shown on the screen as desktop background. Background image remains +visible in the screen as long as the user's session remains open. + +Copyright \copyright\ 2010\ The CentOS Project. Permission is +granted to copy, distribute and/or modify this document under the +terms of the GNU Free Documentation License, Version 1.2 or any later +version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the +license is included in the section entitled ``GNU Free Documentation +License''. +\end{abstract} + +\tableofcontents + +\section{Workplace} + +\begin{itemize} +\item SVN:trunk/Identity/Themes/\$THEME/Distro/Backgrounds/ +\end{itemize} + +\section{Theme} + +\input{table-theme.tex} + +\section{Design} + +Background design is based on CentOS Default Artistic Motif. + +\begin{itemize} +\item There is no color limitation in this section. +\item There is no translation in these images. +\item There is no version, or textual information in these images. +\end{itemize} + +\section{Rendering} + +\section{Configuration} + +\input{table-config.tex} + +\begin{description} + +\item[Default background]: The +\texttt{desktop\_gnome\_background.schemas} and \texttt{\%gconf-tree.xml} +files control which is the default background image loaded when new +users open their GNOME session for first time and as long as no change +be made in its ``Desktop Background Preferences''. + +Inside \texttt{desktop\_gnome\_background.schemas} file the default +background image is defined in the line 6 of the following piece of +code: + +\begin{verbatim} +... + 1| + 2| /schemas/desktop/gnome/background/picture_filename + 3| /desktop/gnome/background/picture_filename + 4| gnome + 5| string + 6| /usr/share/backgrounds/images/default.png + 7| + 8| Picture Filename + 9| File to use for the background image +10| +11| +... +\end{verbatim} + +Inside \texttt{\%gconf-tree.xml} file, the default background image is +defined in the line 4 of the following piece of code: + +\begin{verbatim} +... +1| +2| +3| +4| /usr/share/backgrounds/images/default.png +5| +6| File to use for the background image +7| +8| +... +\end{verbatim} + +In both files \texttt{desktop\_gnome\_background.schemas} and +\texttt{\%gconf-tree.xml}, the image file name should be the same. + +The \texttt{kdesktoprc} file controls KDE desktop configuration file. +The following lines were taken from that file and show the variables +that control default background on KDE desktop. + +\begin{verbatim} +Wallpaper=/usr/share/backgrounds/images/default.png +WallpaperMode=Scaled +\end{verbatim} + +\end{description} + +\section{Testing} + +\section{Issues} + +\begin{description} + +\item[Image format definition]: Images controlling default desktop +backgrounds are in JPG format. Nevertheless this doesn't match with +the definition in the configuration file +\texttt{desktop-backgrounds-basic.xml} which mention them as PNG format. +This issue makes those images not to be displayed in the GNOME +``Desktop Background Preferences''. + +\end{description} + +% License section +\input{../../../../Licenses/GFDL.tex} + +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-1.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-1.tex new file mode 100644 index 0000000..e3bcbd2 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-1.tex @@ -0,0 +1,26 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/backgrounds/images/default-5\_4.png\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & PNG image data, 2048 x 1536, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/backgrounds/images/default-dual.png\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & PNG image data, 2560 x 1240, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/backgrounds/images/default-dual-wide.png\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & PNG image data, 3271 x 1227, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/backgrounds/images/default.png\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & PNG image data, 2048 x 1536, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/backgrounds/images/default-wide.png\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & PNG image data, 1680 x 1050, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\hline +\multicolumn{2}{l}{\ }\\ +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-2.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-2.tex new file mode 100644 index 0000000..8a08e7c --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-2.tex @@ -0,0 +1,22 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gnome-background-properties/desktop-backgrounds-basic.xml\\ +\textbf{Package}: & desktop-backgrounds-basic\\ +\textbf{Description}: & XML 1.0 document text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /etc/gconf/schemas/desktop\_gnome\_background.schemas\\ +\textbf{Package}: & libgnome\\ +\textbf{Description}: & UTF-8 Unicode English text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /etc/gconf/gconf.xml.defaults/\%gconf-tree.xml\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & XML 1.0 document text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/config/kdesktoprc\\ +\textbf{Package}: & kdebase\\ +\textbf{Description}: & ASCII text\\ +\multicolumn{2}{l}{\ }\\ +\hline +\multicolumn{2}{l}{\ }\\ +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-config.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-config.tex new file mode 100644 index 0000000..ef96a5c --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-config.tex @@ -0,0 +1,25 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /etc/gdm/custom.conf\\ +\textbf{Package}: & gdm\\ +\textbf{Description}: & ASCII English text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /etc/gconf/gconf.xml.defaults/\%gconf-tree.xml\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & XML 1.0 document text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /etc/gconf/schemas/desktop\_gnome\_background.schemas\\ +\textbf{Package}: & libgnome\\ +\textbf{Description}: & UTF-8 Unicode English text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/config/kdesktoprc\\ +\textbf{Package}: & kdebase\\ +\textbf{Description}: & ASCII text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/config/kdm/backgroundrc\\ +\textbf{Package}: & kdebase\\ +\textbf{Description}: & ASCII text\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-theme.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-theme.tex new file mode 100644 index 0000000..be90910 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Backgrounds/table-theme.tex @@ -0,0 +1,29 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/backgrounds/images/default-5\_4.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 2048 x 1536, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/backgrounds/images/default-dual.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 2560 x 1240, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/backgrounds/images/default-dual-wide.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 3271 x 1227, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/backgrounds/images/default.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 2048 x 1536, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/backgrounds/images/default-wide.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 1680 x 1050, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/backgrounds/tiles/default\_blue.jpg\\ +\textbf{Package}: & desktop-backgrounds-basic\\ +\textbf{Description}: & JPEG image data, JFIF standard 1.02\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.aux new file mode 100644 index 0000000..7d62833 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.aux @@ -0,0 +1,47 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} +\gdef \LT@i {\LT@entry + {1}{72.64pt}\LT@entry + {1}{292.61166pt}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{3}{section.3}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Configuration}{3}{section.4}} +\@writefile{toc}{\contentsline {section}{\numberline {5}Rendering}{4}{section.5}} +\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{4}{section.6}} +\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{4}{section.7}} +\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{5}{section.8}} +\newlabel{sec:License-GFDL-0}{{8}{5}{Preamble\relax }{section*.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{5}{subsection.8.1}} +\newlabel{sec:License-GFDL-1}{{8.1}{5}{Applicability And Definitions\relax }{subsection.8.1}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{7}{subsection.8.2}} +\newlabel{sec:License-GFDL-2}{{8.2}{7}{Verbatim Copying\relax }{subsection.8.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{7}{subsection.8.3}} +\newlabel{sec:License-GFDL-3}{{8.3}{7}{Copying In Quantity\relax }{subsection.8.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{8}{subsection.8.4}} +\newlabel{sec:License-GFDL-4}{{8.4}{8}{Modifications\relax }{subsection.8.4}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{9}{subsection.8.5}} +\newlabel{sec:License-GFDL-5}{{8.5}{9}{Combining Documents\relax }{subsection.8.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{10}{subsection.8.6}} +\newlabel{sec:License-GFDL-6}{{8.6}{10}{Collections Of Documents\relax }{subsection.8.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{10}{subsection.8.7}} +\newlabel{sec:License-GFDL-7}{{8.7}{10}{Aggregation With Independent Works\relax }{subsection.8.7}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{11}{subsection.8.8}} +\newlabel{sec:License-GFDL-8}{{8.8}{11}{Translation\relax }{subsection.8.8}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{11}{subsection.8.9}} +\newlabel{sec:License-GFDL-9}{{8.9}{11}{Termination\relax }{subsection.8.9}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{11}{subsection.8.10}} +\newlabel{sec:License-GFDL-10}{{8.10}{11}{Future Revisions OF This License\relax }{subsection.8.10}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{11}{subsection.8.11}} +\newlabel{sec:License-GFDL-11}{{8.11}{11}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.log new file mode 100644 index 0000000..4d9a7d5 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.log @@ -0,0 +1,287 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size10.clo +File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/tools/longtable.sty +Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) +\LTleft=\skip43 +\LTright=\skip44 +\LTpre=\skip45 +\LTpost=\skip46 +\LTchunksize=\count87 +\LTcapwidth=\dimen103 +\LT@head=\box26 +\LT@firsthead=\box27 +\LT@foot=\box28 +\LT@lastfoot=\box29 +\LT@cols=\count88 +\LT@rows=\count89 +\c@LT@tables=\count90 +\c@LT@chunks=\count91 +\LT@p@ftn=\toks14 +) +(/usr/share/texmf/tex/latex/graphics/graphicx.sty +Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks15 +) +(/usr/share/texmf/tex/latex/graphics/graphics.sty +Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/trig.sty +Package: trig 1999/03/16 v1.09 sin cos tan (DPC) +) +(/usr/share/texmf/tex/latex/graphics/graphics.cfg +File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive +) +Package graphics Info: Driver file: pdftex.def on input line 80. + +(/usr/share/texmf/tex/latex/graphics/pdftex.def +File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex +\Gread@gobject=\count92 +)) +\Gin@req@height=\dimen104 +\Gin@req@width=\dimen105 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX +\@linkdim=\dimen106 +\Hy@linkcounter=\count93 +\Hy@pagecounter=\count94 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count95 +\Field@Width=\dimen107 +\Fld@charsize=\dimen108 +\Choice@toks=\toks16 +\Field@toks=\toks17 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count96 +\c@Hfootnote=\count97 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count98 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. + +(/usr/share/texmf/tex/context/base/supp-pdf.tex +(/usr/share/texmf/tex/context/base/supp-mis.tex +loading : Context Support Macros / Miscellaneous (2004.10.26) +\protectiondepth=\count99 +\scratchcounter=\count100 +\scratchtoks=\toks18 +\scratchdimen=\dimen109 +\scratchskip=\skip47 +\scratchmuskip=\muskip11 +\scratchbox=\box30 +\scratchread=\read1 +\scratchwrite=\write4 +\zeropoint=\dimen110 +\onepoint=\dimen111 +\onebasepoint=\dimen112 +\minusone=\count101 +\thousandpoint=\dimen113 +\onerealpoint=\dimen114 +\emptytoks=\toks19 +\nextbox=\box31 +\nextdepth=\dimen115 +\everyline=\toks20 +\!!counta=\count102 +\!!countb=\count103 +\recursecounter=\count104 +) +loading : Context Support Macros / PDF (2004.03.26) +\nofMPsegments=\count105 +\nofMParguments=\count106 +\MPscratchCnt=\count107 +\MPscratchDim=\dimen116 +\MPnumerator=\count108 +\everyMPtoPDFconversion=\toks21 +) +Package hyperref Info: Link coloring OFF on input line 13. + (/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count109 +) +LaTeX Info: Redefining \ref on input line 13. +LaTeX Info: Redefining \pageref on input line 13. + (./Manual.out) +(./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 16. +LaTeX Font Info: Try loading font information for OMS+cmr on input line 25. + (/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 25. + (./Manual.toc +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 9. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 9. + +[1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) +\tf@toc=\write5 +\openout5 = `Manual.toc'. + +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 39. + +(./table-theme.tex +Overfull \hbox (20.25166pt too wide) in alignment at lines 1--23 + [] [] + [] + + +Underfull \vbox (badness 10000) detected at line 23 + [] + + +Overfull \hbox (20.25166pt too wide) in alignment at lines 23--43 + [] [] + [] + + +Overfull \hbox (20.25166pt too wide) in alignment at lines 43--45 + [] [] + [] + +[2]) +Overfull \hbox (31.52852pt too wide) in paragraph at lines 55--59 +\OT1/cmr/m/n/10 col-lects all in-for-ma-tion, groups it and stores it un-der tg +z/$VERSION/$RESOLUTION/ + [] + + +Overfull \hbox (6.83415pt too wide) in paragraph at lines 70--71 +[]\OT1/cmr/m/n/10 gnome-help file:///usr/share/gnome/help/gdm/C/gdm.xml#themema +nual + [] + + +Underfull \hbox (badness 10000) in paragraph at lines 81--82 + + [] + +[3] (../../../../../Licenses/GFDL.tex +Underfull \hbox (badness 10000) in paragraph at lines 5--14 + + [] + +[4] [5] +Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 +\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple + HTML, PostScript + [] + +[6] [7] [8] [9] [10] [11]) [12] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 2746 strings out of 94500 + 36564 string characters out of 1176766 + 90637 words of memory out of 1000000 + 5869 multiletter control sequences out of 10000+50000 + 9961 words of font info for 35 fonts, out of 500000 for 2000 + 580 hyphenation exceptions out of 1000 + 27i,8n,36p,222b,222s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 207 PDF objects out of 300000 + 36 named destinations out of 131072 + 169 words of extra memory for PDF output out of 65536 + +Output written on Manual.pdf (12 pages, 149237 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.out new file mode 100644 index 0000000..2f29f36 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.out @@ -0,0 +1,19 @@ +\BOOKMARK [1][-]{section.1}{Workplace}{} +\BOOKMARK [1][-]{section.2}{Theme}{} +\BOOKMARK [1][-]{section.3}{Design}{} +\BOOKMARK [1][-]{section.4}{Configuration}{} +\BOOKMARK [1][-]{section.5}{Rendering}{} +\BOOKMARK [1][-]{section.6}{Testing}{} +\BOOKMARK [1][-]{section.7}{Issues}{} +\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} +\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} +\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} +\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} +\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} +\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} +\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} +\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} +\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} +\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.pdf new file mode 100644 index 0000000..ceb279f Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.toc new file mode 100644 index 0000000..b0c70e5 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/Manual.toc @@ -0,0 +1,19 @@ +\contentsline {section}{\numberline {1}Workplace}{2}{section.1} +\contentsline {section}{\numberline {2}Theme}{2}{section.2} +\contentsline {section}{\numberline {3}Design}{3}{section.3} +\contentsline {section}{\numberline {4}Configuration}{3}{section.4} +\contentsline {section}{\numberline {5}Rendering}{4}{section.5} +\contentsline {section}{\numberline {6}Testing}{4}{section.6} +\contentsline {section}{\numberline {7}Issues}{4}{section.7} +\contentsline {section}{\numberline {8}GNU Free Documentation License}{5}{section.8} +\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{5}{subsection.8.1} +\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{7}{subsection.8.2} +\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{7}{subsection.8.3} +\contentsline {subsection}{\numberline {8.4}Modifications}{8}{subsection.8.4} +\contentsline {subsection}{\numberline {8.5}Combining Documents}{9}{subsection.8.5} +\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{10}{subsection.8.6} +\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{10}{subsection.8.7} +\contentsline {subsection}{\numberline {8.8}Translation}{11}{subsection.8.8} +\contentsline {subsection}{\numberline {8.9}Termination}{11}{subsection.8.9} +\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{11}{subsection.8.10} +\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{11}{subsection.8.11} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/build.sh b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/build.sh new file mode 100755 index 0000000..2e9187b --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/build.sh @@ -0,0 +1,55 @@ +#!/bin/bash +# +# Build GDM tables for LaTeX documents. +# +# Copyright (C) 2009 Alain Reguera Delgado +# +# 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:$ +#-------------------------------------- + +# Load functions. +. ~/artwork/trunk/Scripts/Bash/loadFunctions. + +# Define the names of your tables. +FILES="table-theme.tex + table-config.tex" + +for FILE in $FILES;do + + # Let know what table we are creating. + echo $FILE + + case $FILE in + + table-theme.tex ) + # Create table holding theme files. + ROWS="$(getFiles '/usr/share/gdm/themes' '/Modern/.*')" + ;; + + table-config.tex ) + # Create table holding configuration files. + ROWS="$(getFiles '/{etc,usr/share}/gdm' '\.conf')" + ;; + + esac + + # Create table. + createTable "$ROWS" "" "" > $FILE + +done diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/manual.tex new file mode 100644 index 0000000..7e7f4b4 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/manual.tex @@ -0,0 +1,150 @@ +\documentclass{article} +\usepackage{longtable} +\usepackage[pdftex]{graphicx} +\usepackage{hyperref} +\hypersetup{pdfauthor={CentOS Documentation SIG},% + pdftitle={GNOME Display Manager (GDM)},% + pdfsubject={CentOS Corporate Visual Identity}% + } + +\title{GNOME Display Manager (GDM)} +\author{CentOS Documentation SIG} + +\begin{document} + +\maketitle + +\begin{abstract} +This article describes the GDM Visual Style for CentOS Distribution. +GDM is the first choice defined as CentOS Display Manager (DM). If +users leave their computers on all the time and don't share their +system, they won't see this as often as users who share a desktop +system with other users on the system or laptop users who reboot and +login more frequently. + +Copyright \copyright\ 2010\ The CentOS Project. Permission is +granted to copy, distribute and/or modify this document under the +terms of the GNU Free Documentation License, Version 1.2 or any later +version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the +license is included in the section entitled ``GNU Free Documentation +License''. +\end{abstract} + +\tableofcontents + +\section{Workplace} + +\begin{itemize} +\item SVN:trunk/Identity/Themes/\$THEME/Distro/BootUp/GDM/ +\item SVN:trunk/Translations/Identity/Themes/Distro/BootUp/GDM/ +\item SVN:trunk/Scripts/Identity/Themes/Distro/BootUp/GDM/ +\end{itemize} + +\section{Theme} + +\input{table-theme.tex} + +\section{Design} + +The centos-release.png and screenshot.png images are rendered for each +major release of CentOS. This task is done using the rendering script +(render.sh) available in the workplace. This script creates the +appropriate PNG images under img/\$VERSION/ directory. + +The background.png image is taken from Backgrounds section. This task +is done using the building script(build.sh) available in the +workplace. This script collects all information, groups it and stores +it under tgz/\$VERSION/\$RESOLUTION/ with the form \$THEME.tar.gz. + +Whith the building script you can create GDM themes for specific +CentOS major releases, and inside each major release for specific +screen resolutions. + +More information about GDM theming is available in the \emph{GNOME +Display Manager Reference Manual}. This guide is available online and +inside your system's help. As shortcut to get that help, you can run +the following command: + +\begin{itemize} +\item gnome-help file:///usr/share/gnome/help/gdm/C/gdm.xml\#thememanual +\end{itemize} + +\section{Configuration} + +\begin{description} + +\item[GraphicalTheme]: The graphical theme that the Themed Greeter +should use. It should refer to a directory in the theme directory set +by \emph{GraphicalThemeDir}. + +\texttt{GraphicalTheme=\$THEME}\\ + +\item[GraphicalThemeDir]: The directory where themes for the Themed +Greeter are installed. + +\texttt{GraphicalThemeDir=/usr/share/gdm/themes/} + +\item[BackgroundColor]: The Standard greeter (gdmlogin) background +color. If the BackgroundType is 2, use this color in the background of +the greeter. Also use it as the back of transparent images set on the +background and if the BackgroundRemoteOnlyColor is set and this is a +remote display. This only affects the GTK+ Greeter. + +\texttt{BackgroundColor=\#204C8D} + +\item[GraphicalThemeColor]: Use this color in the background of the +Themed Greeter. This only affects the Themed Greeter. + +\texttt{GraphicalThemeColor=\#000000} + +\end{description} + +More information about GDM and its configuration can be found in its +reference guide. As shortcut to get that help, you can run the +following command: + +\begin{itemize} +\item gnome-help file:///usr/share/gnome/help/gdm/C/gdm.xml\#index +\end{itemize} + +\section{Rendering} +\section{Testing} +\section{Issues} + +\begin{description} + +\item[Transition from Greeter to Desktop]: This seems to be available +when using the variable \emph{BackgroundImage} in GTK+ Greeter only. +In Themed Greeter the best we have is the variable +\emph{GraphicalThemedColor} to specify the background color of the +transition. + +\item[Different resolutions]: Designing of GDM theme needs to be +expandable through different screen resolutions. By default, GDM theme +uses a background image of 2048x1536 pixels. When screen resolution +changes the predifined behaviour is to scale this image to fit the +current display resolution. If the screen resolution is higher, or +differs in ratio (for example when it a wide screens) the design of +GDM them could loose quality or look different from the original one. + +As a workaround, if GDM theme looks narrow or deformed to you, use the +building script to create the GDM theme in your specific screen +resolution. + +\item[GDM theme installation]: Use the login screen administrator +(gdmsetup). This action requires you to have \emph{root} privileges. + +\item[Default Display Manager]: By default GDM is the first display +manager choice\footnote{See the file /etc/X11/prefdm.}. If you +changed this and want to go back then, run the following command (as +\emph{root}) and reboot: + +\texttt{echo "DISPLAYMANAGER=GNOME" > /etc/sysconfig/desktop} + +\end{description} + +% License section +\input{../../../../../Licenses/GFDL.tex} + +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-1.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-1.tex new file mode 100644 index 0000000..a0c3022 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-1.tex @@ -0,0 +1,45 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/background.png\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & PNG image data, 1024 x 768, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/centos-release.png\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & PNG image data, 181 x 48, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/centos-symbol.png\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & PNG image data, 48 x 48, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/GdmGreeterTheme.desktop\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & UTF-8 Unicode English text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-language.png\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-reboot.png\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-session.png\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-shutdown.png\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/Modern.xml\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & XML 1.0 document text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/screenshot.png\\ +\textbf{Package}: & \textbf{None!}\\ +\textbf{Description}: & PNG image data, 200 x 150, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-config.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-config.tex new file mode 100644 index 0000000..a42f07e --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-config.tex @@ -0,0 +1,5 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-theme.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-theme.tex new file mode 100644 index 0000000..f0212d5 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GDM/table-theme.tex @@ -0,0 +1,45 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/background.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 1024 x 768, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/centos-release.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 181 x 48, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/centos-symbol.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 48 x 48, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/GdmGreeterTheme.desktop\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & UTF-8 Unicode English text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-language.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-reboot.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-session.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/icon-shutdown.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/Modern.xml\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & XML 1.0 document text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/gdm/themes/Modern/screenshot.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 200 x 150, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.aux new file mode 100644 index 0000000..d09c94b --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.aux @@ -0,0 +1,47 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\gdef \LT@i {\LT@entry + {1}{72.64pt}\LT@entry + {1}{419.19533pt}} +\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{2}{section.3}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Configuration}{3}{section.4}} +\@writefile{toc}{\contentsline {section}{\numberline {5}Rendering}{3}{section.5}} +\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{3}{section.6}} +\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{3}{section.7}} +\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8}} +\newlabel{sec:License-GFDL-0}{{8}{3}{Preamble\relax }{section*.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{4}{subsection.8.1}} +\newlabel{sec:License-GFDL-1}{{8.1}{4}{Applicability And Definitions\relax }{subsection.8.1}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{5}{subsection.8.2}} +\newlabel{sec:License-GFDL-2}{{8.2}{5}{Verbatim Copying\relax }{subsection.8.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{6}{subsection.8.3}} +\newlabel{sec:License-GFDL-3}{{8.3}{6}{Copying In Quantity\relax }{subsection.8.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{6}{subsection.8.4}} +\newlabel{sec:License-GFDL-4}{{8.4}{6}{Modifications\relax }{subsection.8.4}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5}} +\newlabel{sec:License-GFDL-5}{{8.5}{8}{Combining Documents\relax }{subsection.8.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{9}{subsection.8.6}} +\newlabel{sec:License-GFDL-6}{{8.6}{9}{Collections Of Documents\relax }{subsection.8.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{9}{subsection.8.7}} +\newlabel{sec:License-GFDL-7}{{8.7}{9}{Aggregation With Independent Works\relax }{subsection.8.7}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{9}{subsection.8.8}} +\newlabel{sec:License-GFDL-8}{{8.8}{9}{Translation\relax }{subsection.8.8}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{10}{subsection.8.9}} +\newlabel{sec:License-GFDL-9}{{8.9}{10}{Termination\relax }{subsection.8.9}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{10}{subsection.8.10}} +\newlabel{sec:License-GFDL-10}{{8.10}{10}{Future Revisions OF This License\relax }{subsection.8.10}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11}} +\newlabel{sec:License-GFDL-11}{{8.11}{10}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.log new file mode 100644 index 0000000..4faaf90 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.log @@ -0,0 +1,267 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size10.clo +File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/tools/longtable.sty +Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) +\LTleft=\skip43 +\LTright=\skip44 +\LTpre=\skip45 +\LTpost=\skip46 +\LTchunksize=\count87 +\LTcapwidth=\dimen103 +\LT@head=\box26 +\LT@firsthead=\box27 +\LT@foot=\box28 +\LT@lastfoot=\box29 +\LT@cols=\count88 +\LT@rows=\count89 +\c@LT@tables=\count90 +\c@LT@chunks=\count91 +\LT@p@ftn=\toks14 +) +(/usr/share/texmf/tex/latex/graphics/graphicx.sty +Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks15 +) +(/usr/share/texmf/tex/latex/graphics/graphics.sty +Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/trig.sty +Package: trig 1999/03/16 v1.09 sin cos tan (DPC) +) +(/usr/share/texmf/tex/latex/graphics/graphics.cfg +File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive +) +Package graphics Info: Driver file: pdftex.def on input line 80. + +(/usr/share/texmf/tex/latex/graphics/pdftex.def +File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex +\Gread@gobject=\count92 +)) +\Gin@req@height=\dimen104 +\Gin@req@width=\dimen105 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX +\@linkdim=\dimen106 +\Hy@linkcounter=\count93 +\Hy@pagecounter=\count94 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count95 +\Field@Width=\dimen107 +\Fld@charsize=\dimen108 +\Choice@toks=\toks16 +\Field@toks=\toks17 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count96 +\c@Hfootnote=\count97 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count98 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. + +(/usr/share/texmf/tex/context/base/supp-pdf.tex +(/usr/share/texmf/tex/context/base/supp-mis.tex +loading : Context Support Macros / Miscellaneous (2004.10.26) +\protectiondepth=\count99 +\scratchcounter=\count100 +\scratchtoks=\toks18 +\scratchdimen=\dimen109 +\scratchskip=\skip47 +\scratchmuskip=\muskip11 +\scratchbox=\box30 +\scratchread=\read1 +\scratchwrite=\write4 +\zeropoint=\dimen110 +\onepoint=\dimen111 +\onebasepoint=\dimen112 +\minusone=\count101 +\thousandpoint=\dimen113 +\onerealpoint=\dimen114 +\emptytoks=\toks19 +\nextbox=\box31 +\nextdepth=\dimen115 +\everyline=\toks20 +\!!counta=\count102 +\!!countb=\count103 +\recursecounter=\count104 +) +loading : Context Support Macros / PDF (2004.03.26) +\nofMPsegments=\count105 +\nofMParguments=\count106 +\MPscratchCnt=\count107 +\MPscratchDim=\dimen116 +\MPnumerator=\count108 +\everyMPtoPDFconversion=\toks21 +) +Package hyperref Info: Link coloring OFF on input line 13. + (/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count109 +) +LaTeX Info: Redefining \ref on input line 13. +LaTeX Info: Redefining \pageref on input line 13. + (./Manual.out) +(./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 16. +LaTeX Font Info: Try loading font information for OMS+cmr on input line 22. + (/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 22. + (./Manual.toc +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 9. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 9. + +[1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) +\tf@toc=\write5 +\openout5 = `Manual.toc'. + +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 36. + +(./table-theme.tex +Overfull \hbox (146.83533pt too wide) in alignment at lines 1--9 + [] [] + [] + + +Underfull \vbox (badness 10000) detected at line 9 + [] + +) +Overfull \hbox (10.12134pt too wide) in paragraph at lines 82--84 +\OT1/cmr/m/n/10 The fol-low-ing is-sues were seen on a video card \OT1/cmr/m/it +/10 Tri-dent Mi-crosysmtes Cy-berBlade/i1 + [] + +[2] (../../../../../Licenses/GFDL.tex +Underfull \hbox (badness 10000) in paragraph at lines 5--14 + + [] + +[3] [4] +Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 +\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple + HTML, PostScript + [] + +[5] [6] [7] [8] [9]) [10] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 2750 strings out of 94500 + 36602 string characters out of 1176766 + 89642 words of memory out of 1000000 + 5871 multiletter control sequences out of 10000+50000 + 10666 words of font info for 37 fonts, out of 500000 for 2000 + 580 hyphenation exceptions out of 1000 + 27i,8n,36p,222b,214s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 204 PDF objects out of 300000 + 36 named destinations out of 131072 + 169 words of extra memory for PDF output out of 65536 + +Output written on Manual.pdf (10 pages, 143812 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.out new file mode 100644 index 0000000..2f29f36 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.out @@ -0,0 +1,19 @@ +\BOOKMARK [1][-]{section.1}{Workplace}{} +\BOOKMARK [1][-]{section.2}{Theme}{} +\BOOKMARK [1][-]{section.3}{Design}{} +\BOOKMARK [1][-]{section.4}{Configuration}{} +\BOOKMARK [1][-]{section.5}{Rendering}{} +\BOOKMARK [1][-]{section.6}{Testing}{} +\BOOKMARK [1][-]{section.7}{Issues}{} +\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} +\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} +\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} +\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} +\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} +\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} +\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} +\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} +\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} +\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.pdf new file mode 100644 index 0000000..5173294 Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.toc new file mode 100644 index 0000000..2d89c1f --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/Manual.toc @@ -0,0 +1,19 @@ +\contentsline {section}{\numberline {1}Workplace}{2}{section.1} +\contentsline {section}{\numberline {2}Theme}{2}{section.2} +\contentsline {section}{\numberline {3}Design}{2}{section.3} +\contentsline {section}{\numberline {4}Configuration}{3}{section.4} +\contentsline {section}{\numberline {5}Rendering}{3}{section.5} +\contentsline {section}{\numberline {6}Testing}{3}{section.6} +\contentsline {section}{\numberline {7}Issues}{3}{section.7} +\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8} +\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{4}{subsection.8.1} +\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{5}{subsection.8.2} +\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{6}{subsection.8.3} +\contentsline {subsection}{\numberline {8.4}Modifications}{6}{subsection.8.4} +\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5} +\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{9}{subsection.8.6} +\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{9}{subsection.8.7} +\contentsline {subsection}{\numberline {8.8}Translation}{9}{subsection.8.8} +\contentsline {subsection}{\numberline {8.9}Termination}{10}{subsection.8.9} +\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{10}{subsection.8.10} +\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/build.sh b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/build.sh new file mode 100755 index 0000000..c810485 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/build.sh @@ -0,0 +1,56 @@ +#!/bin/bash +# +# Build GRUB tables for LaTeX documents. +# +# Copyright (C) 2009 Alain Reguera Delgado +# +# 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:$ +#-------------------------------------- + +# Load functions. +. ~/artwork/trunk/Scripts/Bash/loadFunctions.sh + +# Define the names of your tables. +FILES="table-theme.tex + table-config.tex" + +for FILE in $FILES;do + + # Let know which table we are creating. + echo $FILE + + # Define what to do with each table you define on FILES. + case $FILE in + + table-theme.tex ) + # Create table holding theme files. + ROWS="$(getFiles '/boot/grub' 'splash.xpm.gz')" + ;; + + table-config.tex ) + # Create table holding configuration files. + ROWS="$(getFiles '/{boot/grub,etc}' '(\.lst|grub|\.conf)$')" + ;; + + esac + + # Create table. + createTable "$ROWS" "" "" > $FILE + +done diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/manual.tex new file mode 100644 index 0000000..9efcae8 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/manual.tex @@ -0,0 +1,109 @@ +\documentclass{article} +\usepackage{longtable} +\usepackage[pdftex]{graphicx} +\usepackage{hyperref} +\hypersetup{pdfauthor={CentOS Documentation SIG},% + pdftitle={Grand Unified Bootloader (GRUB)},% + pdfsubject={CentOS Corporate Visual Identity}% + } + +\title{Grand Unified Bootloader (GRUB)} +\author{CentOS Documentation SIG} + +\begin{document} + +\maketitle + +\begin{abstract} +This article describes GRUB Visual Style for CentOS Distribution. +This screen is where the selection of which kernel to run and other +boot-time options, are made. It is seen every time the computer boots. + +Copyright \copyright\ 2010\ The CentOS Project. Permission is +granted to copy, distribute and/or modify this document under the +terms of the GNU Free Documentation License, Version 1.2 or any later +version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the +license is included in the section entitled ``GNU Free Documentation +License''. +\end{abstract} + +\tableofcontents + +\section{Workplace} + +\begin{itemize} +\item SVN:trunk/Identity/Themes/\$THEME/Distro/BootUp/GRUB/ +\item SVN:trunk/Translations/Identity/Themes/Distro/BootUp/GRUB/ +\item SVN:trunk/Scripts/Identity/Themes/Distro/BootUp/GRUB/ +\end{itemize} + +\section{Theme} + +\input{table-theme.tex} + +\section{Design} + +Initially, \emph{splash.xpm.gz} is a PNG image (splash.png) which is +converted to xpm.gz. \emph{splash.png} image is rendered for each +major release of CentOS distribution. Each image is based in the same +Artistic Motif and has the following components: + +\begin{enumerate} +\item The CentOS Release Brand. +\item The CentOS Default Artistic Motif. +\end{enumerate} + +Image rendering is done using the rendering script (\emph{render.sh}) +available in the workplace of this section. This script creates +the appropriate PNG images under \emph{img/\$VERSION/} +directory. + +After image rendering, each \emph{img/\$VERSION/splash.png} image +should be indexed to 14 colors. This can be done using an image +manipulation tool like GIMP, or ImageMagick. This color reduction +could bring some noise to your design. If that is the case, you need +to retouch your design in a 14 colors basis. + +The final step is to convert the 14 colors indexed \emph{splash.png} +image into \emph{splash.xpm.gz}. To do so, use the command +\emph{convert2xpm.sh} provided in the workplace. This command +explores the \emph{img/\$VERSION/} directories and +converts\footnote{\emph{convert splash.png splash.xpm \&\& gzip +splash.xpm}} each \emph{splash.png} image indexed to 14 colors to its +\emph{.xpm.gz} equivalent. The converted images are saved under +\emph{xpm/\$VERSION/} directories. + +\section{Configuration} +\section{Rendering} +\section{Testing} +\section{Issues} + +The following issues were seen on a video card \emph{Trident +Microsysmtes CyberBlade/i1 (cyblafb)}: + +\begin{description} + +\item[Different colors]: As more different colors you have on your +design, more are the possibilities of increasing the amount of noise +in your design after indexing to 14 colors. For example, if you +include the actual CentOS symbol in this image, it ocupies 3 colors +(for the orange, green, violet) which are completely different and +non-reusable in the blue toned background image. + +\item [CentOS Symbol]: If the CentOS symbol is included in +this image, colors used in the symbol after indexing the image +are not the defaults colors defined as CentOS Symbol Colors. + +To workaround this, in first place, I used a variant of CentOS symbol +without background colors, just the white borders. Later, I desided to +remove it completely because that symbol could confuse people about +which is the CentOS default symbol (see ``The CentOS Brand'' manual). +Finally, I ended up using just the plain word CentOS to brand the +GRUB. + +\end{description} + +% License section +\input{../../../../../Licenses/GFDL.tex} +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-1.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-1.tex new file mode 100644 index 0000000..6c1e19a --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-1.tex @@ -0,0 +1,10 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /boot/grub/splash.xpm.gz\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & gzip compressed data, was "splash.xpm".\\ +\multicolumn{2}{l}{\ }\\ +\hline +\multicolumn{2}{l}{\ }\\ +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-config.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-config.tex new file mode 100644 index 0000000..a42f07e --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-config.tex @@ -0,0 +1,5 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-theme.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-theme.tex new file mode 100644 index 0000000..e6bf302 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GRUB/table-theme.tex @@ -0,0 +1,9 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /boot/grub/splash.xpm.gz\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & gzip compressed data, was "splash.xpm", from Unix, last modified: Sat Jan 16 01:17:29 2010\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.aux new file mode 100644 index 0000000..e04ca12 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.aux @@ -0,0 +1,47 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\gdef \LT@i {\LT@entry + {1}{0.0pt}\LT@entry + {1}{124.66689pt}} +\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{2}{section.3}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Configuration}{3}{section.4}} +\@writefile{toc}{\contentsline {section}{\numberline {5}Rendering}{3}{section.5}} +\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{3}{section.6}} +\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{3}{section.7}} +\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8}} +\newlabel{sec:License-GFDL-0}{{8}{3}{Preamble\relax }{section*.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{3}{subsection.8.1}} +\newlabel{sec:License-GFDL-1}{{8.1}{3}{Applicability And Definitions\relax }{subsection.8.1}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{5}{subsection.8.2}} +\newlabel{sec:License-GFDL-2}{{8.2}{5}{Verbatim Copying\relax }{subsection.8.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{5}{subsection.8.3}} +\newlabel{sec:License-GFDL-3}{{8.3}{5}{Copying In Quantity\relax }{subsection.8.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{6}{subsection.8.4}} +\newlabel{sec:License-GFDL-4}{{8.4}{6}{Modifications\relax }{subsection.8.4}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5}} +\newlabel{sec:License-GFDL-5}{{8.5}{8}{Combining Documents\relax }{subsection.8.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{8}{subsection.8.6}} +\newlabel{sec:License-GFDL-6}{{8.6}{8}{Collections Of Documents\relax }{subsection.8.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{8}{subsection.8.7}} +\newlabel{sec:License-GFDL-7}{{8.7}{8}{Aggregation With Independent Works\relax }{subsection.8.7}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{9}{subsection.8.8}} +\newlabel{sec:License-GFDL-8}{{8.8}{9}{Translation\relax }{subsection.8.8}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{9}{subsection.8.9}} +\newlabel{sec:License-GFDL-9}{{8.9}{9}{Termination\relax }{subsection.8.9}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{9}{subsection.8.10}} +\newlabel{sec:License-GFDL-10}{{8.10}{9}{Future Revisions OF This License\relax }{subsection.8.10}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11}} +\newlabel{sec:License-GFDL-11}{{8.11}{10}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.log new file mode 100644 index 0000000..05d0467 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.log @@ -0,0 +1,256 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size10.clo +File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/tools/longtable.sty +Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) +\LTleft=\skip43 +\LTright=\skip44 +\LTpre=\skip45 +\LTpost=\skip46 +\LTchunksize=\count87 +\LTcapwidth=\dimen103 +\LT@head=\box26 +\LT@firsthead=\box27 +\LT@foot=\box28 +\LT@lastfoot=\box29 +\LT@cols=\count88 +\LT@rows=\count89 +\c@LT@tables=\count90 +\c@LT@chunks=\count91 +\LT@p@ftn=\toks14 +) +(/usr/share/texmf/tex/latex/graphics/graphicx.sty +Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks15 +) +(/usr/share/texmf/tex/latex/graphics/graphics.sty +Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/trig.sty +Package: trig 1999/03/16 v1.09 sin cos tan (DPC) +) +(/usr/share/texmf/tex/latex/graphics/graphics.cfg +File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive +) +Package graphics Info: Driver file: pdftex.def on input line 80. + +(/usr/share/texmf/tex/latex/graphics/pdftex.def +File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex +\Gread@gobject=\count92 +)) +\Gin@req@height=\dimen104 +\Gin@req@width=\dimen105 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX +\@linkdim=\dimen106 +\Hy@linkcounter=\count93 +\Hy@pagecounter=\count94 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count95 +\Field@Width=\dimen107 +\Fld@charsize=\dimen108 +\Choice@toks=\toks16 +\Field@toks=\toks17 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count96 +\c@Hfootnote=\count97 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count98 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. + +(/usr/share/texmf/tex/context/base/supp-pdf.tex +(/usr/share/texmf/tex/context/base/supp-mis.tex +loading : Context Support Macros / Miscellaneous (2004.10.26) +\protectiondepth=\count99 +\scratchcounter=\count100 +\scratchtoks=\toks18 +\scratchdimen=\dimen109 +\scratchskip=\skip47 +\scratchmuskip=\muskip11 +\scratchbox=\box30 +\scratchread=\read1 +\scratchwrite=\write4 +\zeropoint=\dimen110 +\onepoint=\dimen111 +\onebasepoint=\dimen112 +\minusone=\count101 +\thousandpoint=\dimen113 +\onerealpoint=\dimen114 +\emptytoks=\toks19 +\nextbox=\box31 +\nextdepth=\dimen115 +\everyline=\toks20 +\!!counta=\count102 +\!!countb=\count103 +\recursecounter=\count104 +) +loading : Context Support Macros / PDF (2004.03.26) +\nofMPsegments=\count105 +\nofMParguments=\count106 +\MPscratchCnt=\count107 +\MPscratchDim=\dimen116 +\MPnumerator=\count108 +\everyMPtoPDFconversion=\toks21 +) +Package hyperref Info: Link coloring OFF on input line 13. + (/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count109 +) +LaTeX Info: Redefining \ref on input line 13. +LaTeX Info: Redefining \pageref on input line 13. + (./Manual.out) +(./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <9> on input line 21. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 21. +LaTeX Font Info: Try loading font information for OMS+cmr on input line 26. + (/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 26. + (./Manual.toc +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 9. + +[1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) +\tf@toc=\write5 +\openout5 = `Manual.toc'. + +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 39. + +(./table-theme.tex +Underfull \vbox (badness 10000) detected at line 6 + [] + +) (../../../../../Licenses/GFDL.tex +Underfull \hbox (badness 10000) in paragraph at lines 5--14 + + [] + +[2] [3] +Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 +\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple + HTML, PostScript + [] + +[4] [5] [6] [7] [8] [9]) [10] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 2750 strings out of 94500 + 36599 string characters out of 1176766 + 88600 words of memory out of 1000000 + 5871 multiletter control sequences out of 10000+50000 + 10141 words of font info for 36 fonts, out of 500000 for 2000 + 580 hyphenation exceptions out of 1000 + 27i,8n,36p,222b,259s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 199 PDF objects out of 300000 + 37 named destinations out of 131072 + 169 words of extra memory for PDF output out of 65536 + +Output written on Manual.pdf (10 pages, 130753 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.out new file mode 100644 index 0000000..2f29f36 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.out @@ -0,0 +1,19 @@ +\BOOKMARK [1][-]{section.1}{Workplace}{} +\BOOKMARK [1][-]{section.2}{Theme}{} +\BOOKMARK [1][-]{section.3}{Design}{} +\BOOKMARK [1][-]{section.4}{Configuration}{} +\BOOKMARK [1][-]{section.5}{Rendering}{} +\BOOKMARK [1][-]{section.6}{Testing}{} +\BOOKMARK [1][-]{section.7}{Issues}{} +\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} +\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} +\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} +\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} +\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} +\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} +\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} +\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} +\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} +\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.pdf new file mode 100644 index 0000000..917b0e4 Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.toc new file mode 100644 index 0000000..100ecb7 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/Manual.toc @@ -0,0 +1,19 @@ +\contentsline {section}{\numberline {1}Workplace}{2}{section.1} +\contentsline {section}{\numberline {2}Theme}{2}{section.2} +\contentsline {section}{\numberline {3}Design}{2}{section.3} +\contentsline {section}{\numberline {4}Configuration}{3}{section.4} +\contentsline {section}{\numberline {5}Rendering}{3}{section.5} +\contentsline {section}{\numberline {6}Testing}{3}{section.6} +\contentsline {section}{\numberline {7}Issues}{3}{section.7} +\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8} +\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{3}{subsection.8.1} +\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{5}{subsection.8.2} +\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{5}{subsection.8.3} +\contentsline {subsection}{\numberline {8.4}Modifications}{6}{subsection.8.4} +\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5} +\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{8}{subsection.8.6} +\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{8}{subsection.8.7} +\contentsline {subsection}{\numberline {8.8}Translation}{9}{subsection.8.8} +\contentsline {subsection}{\numberline {8.9}Termination}{9}{subsection.8.9} +\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{9}{subsection.8.10} +\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/build.sh b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/build.sh new file mode 100755 index 0000000..66fb822 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/build.sh @@ -0,0 +1,55 @@ +#!/bin/bash +# +# Build GSplash tables for LaTeX document. +# +# Copyright (C) 2009 Alain Reguera Delgado +# +# 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:$ +#-------------------------------------- + +# Load functions. +. ~/artwork/trunk/Scripts/Bash/loadFunctions. + +# Define the names of your tables. +FILES="table-theme.tex + table-config.tex" + +for FILE in $FILES;do + + # Let know what table we are creating. + echo $FILE + + case $FILE in + + table-theme.tex ) + # Create table holding theme files. + ROWS="$(getFiles '/usr/share/pixmaps' 'gnome-splash')" + ;; + + table-config.tex ) + # Create table holding configuration files. + ROWS="$(getFiles '/etc/gconf' 'gnome-splash')" + ;; + + esac + + # Create table. + createTable "$ROWS" "" "" > $FILE + +done diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/manual.tex new file mode 100644 index 0000000..7287877 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/manual.tex @@ -0,0 +1,74 @@ +\documentclass{article} +\usepackage{longtable} +\usepackage[pdftex]{graphicx} +\usepackage{hyperref} +\hypersetup{pdfauthor={CentOS Documentation SIG},% + pdftitle={GNOME Splash)},% + pdfsubject={CentOS Corporate Visual Identity}% + } + +\title{GNOME Splash} +\author{CentOS Documentation SIG} + +\begin{document} + +\maketitle + +\begin{abstract} + +This article describes the GNOME Splash Visual Style for CentOS +Distribution. By default this image is disabled to make GNOME session +load faster. If you enable it,\footnote{To enable GNOME Splash image +go to: \texttt{System > Preferences > More Preferences > Sessions} and +check the item \texttt{Show splash screen on login}.} this image is +displayed after login screen, and while GNOME session is being loaded. + +Copyright \copyright\ 2010\ The CentOS Project. Permission is +granted to copy, distribute and/or modify this document under the +terms of the GNU Free Documentation License, Version 1.2 or any later +version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the +license is included in the section entitled ``GNU Free Documentation +License''. +\end{abstract} + +\tableofcontents + +\section{Workplace} +\begin{itemize} +\item SVN:trunk/Identity/Themes/\$THEME/Distro/BootUp/GSplash/ +\item SVN:trunk/Translations/Identity/Themes/Distro/BootUp/GSplash/ +\item SVN:trunk/Scripts/Identity/Themes/Distro/BootUp/GSplash/ +\end{itemize} + +\section{Theme} + +\input{table-theme.tex} + +\section{Design} + +GNOME Splash is rendered for each major release of CentOS +Distribution. Each image is based in the same Artistic Motif and has +the following components: + +\begin{enumerate} +\item The CentOS Symbol. +\item The CentOS Release Brand. +\item The CentOS Default Artistic Motif. +\end{enumerate} + +Image rendering is done using the script render.sh available in the +workplace. This script creates the appropriate PNG images under +img/\$VERSION/. + +There is no color limitation in this section. + +\section{Configuration} +\section{Rendering} +\section{Testing} +\section{Issues} + +% License section +\input{../../../../../Licenses/GFDL.tex} + +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-1.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-1.tex new file mode 100644 index 0000000..21701c3 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-1.tex @@ -0,0 +1,14 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/pixmaps/gnome-splash.png\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & PNG image data, 380 x 325, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/pixmaps/splash/gnome-splash.png\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & PNG image data, 380 x 325, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\hline +\multicolumn{2}{l}{\ }\\ +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-config.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-config.tex new file mode 100644 index 0000000..8c6b743 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-config.tex @@ -0,0 +1,6 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\multicolumn{2}{l}{Sorry, this table is empty.}\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-theme.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-theme.tex new file mode 100644 index 0000000..8c6b743 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/GSplash/table-theme.tex @@ -0,0 +1,6 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\multicolumn{2}{l}{Sorry, this table is empty.}\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.aux new file mode 100644 index 0000000..2ba08bc --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.aux @@ -0,0 +1,50 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} +\gdef \LT@i {\LT@entry + {1}{72.64pt}\LT@entry + {1}{308.11174pt}} +\gdef \LT@ii {\LT@entry + {1}{72.64pt}\LT@entry + {1}{176.94485pt}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{3}{section.3}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Configuration}{3}{section.4}} +\@writefile{toc}{\contentsline {section}{\numberline {5}Rendering}{4}{section.5}} +\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{4}{section.6}} +\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{4}{section.7}} +\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{5}{section.8}} +\newlabel{sec:License-GFDL-0}{{8}{6}{Preamble\relax }{section*.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{6}{subsection.8.1}} +\newlabel{sec:License-GFDL-1}{{8.1}{6}{Applicability And Definitions\relax }{subsection.8.1}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{8}{subsection.8.2}} +\newlabel{sec:License-GFDL-2}{{8.2}{8}{Verbatim Copying\relax }{subsection.8.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{8}{subsection.8.3}} +\newlabel{sec:License-GFDL-3}{{8.3}{8}{Copying In Quantity\relax }{subsection.8.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{9}{subsection.8.4}} +\newlabel{sec:License-GFDL-4}{{8.4}{9}{Modifications\relax }{subsection.8.4}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{10}{subsection.8.5}} +\newlabel{sec:License-GFDL-5}{{8.5}{10}{Combining Documents\relax }{subsection.8.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{11}{subsection.8.6}} +\newlabel{sec:License-GFDL-6}{{8.6}{11}{Collections Of Documents\relax }{subsection.8.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{11}{subsection.8.7}} +\newlabel{sec:License-GFDL-7}{{8.7}{11}{Aggregation With Independent Works\relax }{subsection.8.7}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{12}{subsection.8.8}} +\newlabel{sec:License-GFDL-8}{{8.8}{12}{Translation\relax }{subsection.8.8}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{12}{subsection.8.9}} +\newlabel{sec:License-GFDL-9}{{8.9}{12}{Termination\relax }{subsection.8.9}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{12}{subsection.8.10}} +\newlabel{sec:License-GFDL-10}{{8.10}{12}{Future Revisions OF This License\relax }{subsection.8.10}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{12}{subsection.8.11}} +\newlabel{sec:License-GFDL-11}{{8.11}{12}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.log new file mode 100644 index 0000000..509d0d9 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.log @@ -0,0 +1,302 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size10.clo +File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/tools/longtable.sty +Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) +\LTleft=\skip43 +\LTright=\skip44 +\LTpre=\skip45 +\LTpost=\skip46 +\LTchunksize=\count87 +\LTcapwidth=\dimen103 +\LT@head=\box26 +\LT@firsthead=\box27 +\LT@foot=\box28 +\LT@lastfoot=\box29 +\LT@cols=\count88 +\LT@rows=\count89 +\c@LT@tables=\count90 +\c@LT@chunks=\count91 +\LT@p@ftn=\toks14 +) +(/usr/share/texmf/tex/latex/graphics/graphicx.sty +Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks15 +) +(/usr/share/texmf/tex/latex/graphics/graphics.sty +Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/trig.sty +Package: trig 1999/03/16 v1.09 sin cos tan (DPC) +) +(/usr/share/texmf/tex/latex/graphics/graphics.cfg +File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive +) +Package graphics Info: Driver file: pdftex.def on input line 80. + +(/usr/share/texmf/tex/latex/graphics/pdftex.def +File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex +\Gread@gobject=\count92 +)) +\Gin@req@height=\dimen104 +\Gin@req@width=\dimen105 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX +\@linkdim=\dimen106 +\Hy@linkcounter=\count93 +\Hy@pagecounter=\count94 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count95 +\Field@Width=\dimen107 +\Fld@charsize=\dimen108 +\Choice@toks=\toks16 +\Field@toks=\toks17 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count96 +\c@Hfootnote=\count97 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count98 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. + +(/usr/share/texmf/tex/context/base/supp-pdf.tex +(/usr/share/texmf/tex/context/base/supp-mis.tex +loading : Context Support Macros / Miscellaneous (2004.10.26) +\protectiondepth=\count99 +\scratchcounter=\count100 +\scratchtoks=\toks18 +\scratchdimen=\dimen109 +\scratchskip=\skip47 +\scratchmuskip=\muskip11 +\scratchbox=\box30 +\scratchread=\read1 +\scratchwrite=\write4 +\zeropoint=\dimen110 +\onepoint=\dimen111 +\onebasepoint=\dimen112 +\minusone=\count101 +\thousandpoint=\dimen113 +\onerealpoint=\dimen114 +\emptytoks=\toks19 +\nextbox=\box31 +\nextdepth=\dimen115 +\everyline=\toks20 +\!!counta=\count102 +\!!countb=\count103 +\recursecounter=\count104 +) +loading : Context Support Macros / PDF (2004.03.26) +\nofMPsegments=\count105 +\nofMParguments=\count106 +\MPscratchCnt=\count107 +\MPscratchDim=\dimen116 +\MPnumerator=\count108 +\everyMPtoPDFconversion=\toks21 +) +Package hyperref Info: Link coloring OFF on input line 13. + (/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count109 +) +LaTeX Info: Redefining \ref on input line 13. +LaTeX Info: Redefining \pageref on input line 13. + (./Manual.out) +(./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 16. +LaTeX Font Info: Try loading font information for OMS+cmr on input line 25. + (/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 25. + (./Manual.toc +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 9. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 9. + +[1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) +\tf@toc=\write5 +\openout5 = `Manual.toc'. + +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 39. + +(./table-theme.tex +Overfull \hbox (35.75174pt too wide) in alignment at lines 1--23 + [] [] + [] + + +Underfull \vbox (badness 10000) detected at line 23 + [] + + +Overfull \hbox (35.75174pt too wide) in alignment at lines 23--43 + [] [] + [] + + +Overfull \hbox (35.75174pt too wide) in alignment at lines 43--45 + [] [] + [] + +[2]) +Overfull \hbox (15.50415pt too wide) in paragraph at lines 50--54 +\OT1/cmr/m/n/10 work-place. This script cre-ates the ap-pro-pri-ate PNG im-ages + un-der img/$VERSION/ + [] + + +Overfull \hbox (17.0285pt too wide) in paragraph at lines 55--59 +\OT1/cmr/m/n/10 in-for-ma-tion needed, groups it and stores it un-der tgz/$VERS +ION/$RESOLUTION/ + [] + + +Overfull \hbox (6.83415pt too wide) in paragraph at lines 71--72 +[]\OT1/cmr/m/n/10 gnome-help file:///usr/share/gnome/help/gdm/C/gdm.xml#themema +nual + [] + +(./table-config.tex +Underfull \vbox (badness 10000) detected at line 13 + [] + + +Overfull \vbox (4.47491pt too high) has occurred while \output is active [] + + +[3]) +Overfull \hbox (0.71486pt too wide) in paragraph at lines 125--128 +[]\OT1/cmr/m/n/10 : KDM and GDM themes[][][] + [] + +[4] (../../../../../Licenses/GFDL.tex +Underfull \hbox (badness 10000) in paragraph at lines 5--14 + + [] + +[5] [6] +Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 +\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple + HTML, PostScript + [] + +[7] [8] [9] [10] [11] [12]) [13] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 2759 strings out of 94500 + 36683 string characters out of 1176766 + 90666 words of memory out of 1000000 + 5871 multiletter control sequences out of 10000+50000 + 10313 words of font info for 36 fonts, out of 500000 for 2000 + 580 hyphenation exceptions out of 1000 + 27i,8n,36p,222b,263s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 222 PDF objects out of 300000 + 43 named destinations out of 131072 + 169 words of extra memory for PDF output out of 65536 + +Output written on Manual.pdf (13 pages, 158058 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.out new file mode 100644 index 0000000..2f29f36 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.out @@ -0,0 +1,19 @@ +\BOOKMARK [1][-]{section.1}{Workplace}{} +\BOOKMARK [1][-]{section.2}{Theme}{} +\BOOKMARK [1][-]{section.3}{Design}{} +\BOOKMARK [1][-]{section.4}{Configuration}{} +\BOOKMARK [1][-]{section.5}{Rendering}{} +\BOOKMARK [1][-]{section.6}{Testing}{} +\BOOKMARK [1][-]{section.7}{Issues}{} +\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} +\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} +\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} +\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} +\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} +\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} +\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} +\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} +\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} +\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.pdf new file mode 100644 index 0000000..6b2811f Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.toc new file mode 100644 index 0000000..e9d6105 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/Manual.toc @@ -0,0 +1,19 @@ +\contentsline {section}{\numberline {1}Workplace}{2}{section.1} +\contentsline {section}{\numberline {2}Theme}{2}{section.2} +\contentsline {section}{\numberline {3}Design}{3}{section.3} +\contentsline {section}{\numberline {4}Configuration}{3}{section.4} +\contentsline {section}{\numberline {5}Rendering}{4}{section.5} +\contentsline {section}{\numberline {6}Testing}{4}{section.6} +\contentsline {section}{\numberline {7}Issues}{4}{section.7} +\contentsline {section}{\numberline {8}GNU Free Documentation License}{5}{section.8} +\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{6}{subsection.8.1} +\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{8}{subsection.8.2} +\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{8}{subsection.8.3} +\contentsline {subsection}{\numberline {8.4}Modifications}{9}{subsection.8.4} +\contentsline {subsection}{\numberline {8.5}Combining Documents}{10}{subsection.8.5} +\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{11}{subsection.8.6} +\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{11}{subsection.8.7} +\contentsline {subsection}{\numberline {8.8}Translation}{12}{subsection.8.8} +\contentsline {subsection}{\numberline {8.9}Termination}{12}{subsection.8.9} +\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{12}{subsection.8.10} +\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{12}{subsection.8.11} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/build.sh b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/build.sh new file mode 100755 index 0000000..70bef88 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/build.sh @@ -0,0 +1,56 @@ +#!/bin/bash +# +# Build KDM tables for LaTeX documents. +# +# Copyright (C) 2009 Alain Reguera Delgado +# +# 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:$ +#-------------------------------------- + +# Load functions. +. ~/artwork/trunk/Scripts/Bash/loadFunctions.sh + +# Define the names of your tables. +FILES="table-theme.tex + table-config.tex" + +for FILE in $FILES;do + + # Let know which table we are creating. + echo $FILE + + # Define what to do with each table you define on FILES. + case $FILE in + + table-theme.tex ) + # Create table holding theme files. + ROWS="$(getFiles '/usr/share/apps/kdm/themes' '/Modern/.*')" + ;; + + table-config.tex ) + # Create table holding configuration files. + ROWS="$(getFiles '/usr/share/config/kdm' 'rc$')" + ;; + + esac + + # Create table. + createTable "$ROWS" "" "" > $FILE + +done diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/manual.tex new file mode 100644 index 0000000..d2b7848 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/manual.tex @@ -0,0 +1,190 @@ +\documentclass{article} +\usepackage{longtable} +\usepackage[pdftex]{graphicx} +\usepackage{hyperref} +\hypersetup{pdfauthor={CentOS Documentation SIG},% + pdftitle={KDE Display Manager (KDM)},% + pdfsubject={CentOS Corporate Visual Identity}% + } + +\title{KDE Display Manager (KDM)} +\author{CentOS Documentation SIG} + +\begin{document} + +\maketitle + +\begin{abstract} +This article describes the KDM Visual Style for CentOS Distribution. +KDE Display Manager (KDM) is the second choice defined as CentOS +Display Manager. If users leave their computers on all the time and +don't share their system, they won't see this as often as users who +share a desktop system with other users on the system or laptop users +who reboot and login more frequently. + +Copyright \copyright\ 2010\ The CentOS Project. Permission is +granted to copy, distribute and/or modify this document under the +terms of the GNU Free Documentation License, Version 1.2 or any later +version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the +license is included in the section entitled ``GNU Free Documentation +License''. +\end{abstract} + +\tableofcontents + +\section{Workplace} + +\begin{itemize} +\item SVN:trunk/Identity/Themes/\$THEME/Distro/BootUp/KDM/ +\item SVN:trunk/Translations/Identity/Themes/Distro/BootUp/KDM/ +\item SVN:trunk/Scripts/Identity/Themes/Distro/BootUp/KDM/ +\end{itemize} + +\section{Theme} + +\input{table-theme.tex} + +\section{Design} + +The centos-release.png and screenshot.png images are rendered for each +major release of CentOS. This task is done using the script render.sh +available in the workplace. This script creates the appropriate PNG +images under img/\$VERSION/ directory. + +The background.png image is taken from Backgrounds section. This task +is done using the script build.sh available in the workplace. This +script collects all information needed, groups it and stores it under +tgz/\$VERSION/\$RESOLUTION/ with the form \$THEME.tar.gz. + +Whith the build.sh script you can create KDM themes for specific +CentOS major releases, and inside each major release for specific +screen resolutions. + +KDM theme uses the same standard that GDM theme does. More information +about GDM theming is available in the \textit{GNOME Display Manager +Reference Manual}. This guide is available online and inside your +system's help. As shortcut to get that help, you can run the following +command: + +\begin{itemize} +\item gnome-help file:///usr/share/gnome/help/gdm/C/gdm.xml\#thememanual +\end{itemize} + +\section{Configuration} + +\input{table-config.tex} + +\begin{description} + +\item[Theme]: In the file \emph{kdmrc}, \texttt{Theme} defines which +is the KDM theme used by default. + +\texttt{Theme=/usr/share/apps/kdm/themes/Modern/} + +\item[UseTheme]: In the file \emph{kdmrc}, \texttt{UseTheme} defines +the precedence of background. If true KDM theme background image takes +precedence against KDM background. + +\texttt{UseTheme=true} + +\item[Wallpaper]: In the file \emph{backgroundrc}, \texttt{Wallpaper} +defines the default configuration for KDM background. + +\texttt{Wallpaper=/usr/share/backgrounds/images/default.png} + +\end{description} + +The background image used on KDM is one file, and the background image +used on KDM theme is another file. Even they are independent files, +the monolithic visual structure requires the same visual information +in these images. + +More information about KDE login screen, KDM and its configuration can +be found in KDE help. As shortcut to get that help, you can run the +following commands: + +\begin{itemize} +\item khelpcenter help:/kdm/login.html +\item khelpcenter help:/kdm/configuring-kdm.html +\item khelpcenter help:/kdm/kdm-files.html +\end{itemize} + +\section{Rendering} +\section{Testing} +\section{Issues} + +\begin{description} + +\item[Transition from Greeter to Desktop]: If KDE desktop background +and KDM background are the same (and they should because the +monolithic visual structure) the transition from login screen to +desktop is ``smooth'' because the background image is always visible +on the screen. + +\item[Differences between KDM and GDM themes]: KDM and GDM +themes\footnote{It refers to the \emph{.xml} files and its related +files.} are basically the same except for the following differences: + +\begin{enumerate} + +\item KDM theme requires the ``user-entry'' and ``pw-entry'' stocks. +This forces the using of two boxes, one for username and one for +password. This boxes are visibly appart one from another. In GDM we +use just one box (the ``user-pw-entry'' stock), both for +username and password. + +\item In KDM theme, messages were centered on the screen to fit the +KDM two-boxes design. In GDM they are centered to the +``user-pw-entry'' stock width. + +\item In KDM theme, the ``language'' stock shows nothing. It creates +an empty space in the screen. The language block was commented to save +space on the screen. In GDM laguage buttom is present and when clicked +a box pops up with a list of languages to choose. + +\item Both KDM and GDM themes use the same font defintion in the +\emph{.xml} file, but in presentation they look quiet different. For +example the KDM clock's \emph{Sans 10 Bold} theme definition does not +take effect. Probably font definition in \emph{kdmrc} file takes +precedence against theme's one. + +\end{enumerate} + +\item[Different resolutions]: Designing of KDM theme needs to be +expandable through different screen resolutions. By default, KDM theme +uses a background image of 2048x1536 pixels. When screen resolution +changes the predifined behaviour is to scale this image to fit the +current display resolution. If the screen resolution is higher, or +differs in ratio (for example when it is a wide screens) the design of +KDM theme could loose quality or look different from the original one. + +As a workaround, if KDM theme looks narrow or deformed to you, use the +build.sh script to create the KDM theme in your specific screen +resolution. + +\item[KDM theme installation]: To install a KDM theme you need to copy +its files from the workplace to its location in the filesytem. If you +want to make that KDM theme your default one, then you also need to +update the KDM configuration files to match your theme location. Both +of these actions require you to have \emph{root} privileges. + +\item[Default Display Manager]: By default KDM is the second display +manager choice\footnote{See the file \emph{/etc/X11/prefdm}.}. To use +KDM as first choise, run the following command (as \emph{root}) and +reboot: + +\texttt{echo "DISPLAYMANAGER=KDE" > /etc/sysconfig/desktop} + +\item[Package content]: CentOS Default KDM Theme seems to be inside +the package redhat-artwork. In contrast with GDM which has some files in +redhat-logos and others in redhat-artwork. Could we standardize this ? +All files in just one package (redhat-artwork) or files divided in two +packages (redhat-artwork, and redhat-logos). + +\end{description} + +% License section +\input{../../../../../Licenses/GFDL.tex} + +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-1.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-1.tex new file mode 100644 index 0000000..5f0c0d3 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-1.tex @@ -0,0 +1,45 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/background.png\\ +\textbf{Package}: & redhat-artwork\\ +\textbf{Description}: & PNG image data, 1024 x 768, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/centos-release.png\\ +\textbf{Package}: & redhat-artwork\\ +\textbf{Description}: & PNG image data, 181 x 48, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/centos-symbol.png\\ +\textbf{Package}: & redhat-artwork\\ +\textbf{Description}: & PNG image data, 48 x 48, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/GdmGreeterTheme.desktop\\ +\textbf{Package}: & redhat-artwork\\ +\textbf{Description}: & UTF-8 Unicode English text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-language.png\\ +\textbf{Package}: & redhat-artwork\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-reboot.png\\ +\textbf{Package}: & redhat-artwork\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-session.png\\ +\textbf{Package}: & redhat-artwork\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-shutdown.png\\ +\textbf{Package}: & redhat-artwork\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/Modern.xml\\ +\textbf{Package}: & redhat-artwork\\ +\textbf{Description}: & XML 1.0 document text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/screenshot.png\\ +\textbf{Package}: & redhat-artwork\\ +\textbf{Description}: & PNG image data, 200 x 150, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-2.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-2.tex new file mode 100644 index 0000000..598664e --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-2.tex @@ -0,0 +1,13 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/config/kdm/kdmrc\\ +\textbf{Package}: & kdebase\\ +\textbf{Description}: & ASCII text, with very long lines\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/config/kdm/backgroundrc\\ +\textbf{Package}: & kdebase\\ +\textbf{Description}: & ASCII text\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-config.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-config.tex new file mode 100644 index 0000000..7c4232e --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-config.tex @@ -0,0 +1,13 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/config/kdm/backgroundrc\\ +\textbf{Package}: & kdebase\\ +\textbf{Description}: & ASCII text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/config/kdm/kdmrc\\ +\textbf{Package}: & kdebase\\ +\textbf{Description}: & ASCII text, with very long lines\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-theme.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-theme.tex new file mode 100644 index 0000000..fa0231c --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KDM/table-theme.tex @@ -0,0 +1,45 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/background.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 1024 x 768, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/centos-release.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 181 x 48, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/centos-symbol.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 48 x 48, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/GdmGreeterTheme.desktop\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & UTF-8 Unicode English text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-language.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-reboot.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-session.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/icon-shutdown.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 32 x 32, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/Modern.xml\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & XML 1.0 document text\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/kdm/themes/Modern/screenshot.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 200 x 150, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.aux new file mode 100644 index 0000000..4483cd3 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.aux @@ -0,0 +1,50 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\gdef \LT@i {\LT@entry + {1}{72.64pt}\LT@entry + {1}{304.47844pt}} +\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{2}{section.3}} +\gdef \LT@ii {\LT@entry + {1}{72.64pt}\LT@entry + {1}{134.25027pt}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Configuration}{3}{section.4}} +\@writefile{toc}{\contentsline {section}{\numberline {5}Rendering}{3}{section.5}} +\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{3}{section.6}} +\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{3}{section.7}} +\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8}} +\newlabel{sec:License-GFDL-0}{{8}{4}{Preamble\relax }{section*.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{4}{subsection.8.1}} +\newlabel{sec:License-GFDL-1}{{8.1}{4}{Applicability And Definitions\relax }{subsection.8.1}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{6}{subsection.8.2}} +\newlabel{sec:License-GFDL-2}{{8.2}{6}{Verbatim Copying\relax }{subsection.8.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{6}{subsection.8.3}} +\newlabel{sec:License-GFDL-3}{{8.3}{6}{Copying In Quantity\relax }{subsection.8.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{7}{subsection.8.4}} +\newlabel{sec:License-GFDL-4}{{8.4}{7}{Modifications\relax }{subsection.8.4}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5}} +\newlabel{sec:License-GFDL-5}{{8.5}{8}{Combining Documents\relax }{subsection.8.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{9}{subsection.8.6}} +\newlabel{sec:License-GFDL-6}{{8.6}{9}{Collections Of Documents\relax }{subsection.8.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{9}{subsection.8.7}} +\newlabel{sec:License-GFDL-7}{{8.7}{9}{Aggregation With Independent Works\relax }{subsection.8.7}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{10}{subsection.8.8}} +\newlabel{sec:License-GFDL-8}{{8.8}{10}{Translation\relax }{subsection.8.8}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{10}{subsection.8.9}} +\newlabel{sec:License-GFDL-9}{{8.9}{10}{Termination\relax }{subsection.8.9}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{10}{subsection.8.10}} +\newlabel{sec:License-GFDL-10}{{8.10}{10}{Future Revisions OF This License\relax }{subsection.8.10}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11}} +\newlabel{sec:License-GFDL-11}{{8.11}{10}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.log new file mode 100644 index 0000000..a6762c0 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.log @@ -0,0 +1,273 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size10.clo +File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/tools/longtable.sty +Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) +\LTleft=\skip43 +\LTright=\skip44 +\LTpre=\skip45 +\LTpost=\skip46 +\LTchunksize=\count87 +\LTcapwidth=\dimen103 +\LT@head=\box26 +\LT@firsthead=\box27 +\LT@foot=\box28 +\LT@lastfoot=\box29 +\LT@cols=\count88 +\LT@rows=\count89 +\c@LT@tables=\count90 +\c@LT@chunks=\count91 +\LT@p@ftn=\toks14 +) +(/usr/share/texmf/tex/latex/graphics/graphicx.sty +Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks15 +) +(/usr/share/texmf/tex/latex/graphics/graphics.sty +Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/trig.sty +Package: trig 1999/03/16 v1.09 sin cos tan (DPC) +) +(/usr/share/texmf/tex/latex/graphics/graphics.cfg +File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive +) +Package graphics Info: Driver file: pdftex.def on input line 80. + +(/usr/share/texmf/tex/latex/graphics/pdftex.def +File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex +\Gread@gobject=\count92 +)) +\Gin@req@height=\dimen104 +\Gin@req@width=\dimen105 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX +\@linkdim=\dimen106 +\Hy@linkcounter=\count93 +\Hy@pagecounter=\count94 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count95 +\Field@Width=\dimen107 +\Fld@charsize=\dimen108 +\Choice@toks=\toks16 +\Field@toks=\toks17 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count96 +\c@Hfootnote=\count97 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count98 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. + +(/usr/share/texmf/tex/context/base/supp-pdf.tex +(/usr/share/texmf/tex/context/base/supp-mis.tex +loading : Context Support Macros / Miscellaneous (2004.10.26) +\protectiondepth=\count99 +\scratchcounter=\count100 +\scratchtoks=\toks18 +\scratchdimen=\dimen109 +\scratchskip=\skip47 +\scratchmuskip=\muskip11 +\scratchbox=\box30 +\scratchread=\read1 +\scratchwrite=\write4 +\zeropoint=\dimen110 +\onepoint=\dimen111 +\onebasepoint=\dimen112 +\minusone=\count101 +\thousandpoint=\dimen113 +\onerealpoint=\dimen114 +\emptytoks=\toks19 +\nextbox=\box31 +\nextdepth=\dimen115 +\everyline=\toks20 +\!!counta=\count102 +\!!countb=\count103 +\recursecounter=\count104 +) +loading : Context Support Macros / PDF (2004.03.26) +\nofMPsegments=\count105 +\nofMParguments=\count106 +\MPscratchCnt=\count107 +\MPscratchDim=\dimen116 +\MPnumerator=\count108 +\everyMPtoPDFconversion=\toks21 +) +Package hyperref Info: Link coloring OFF on input line 13. + (/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count109 +) +LaTeX Info: Redefining \ref on input line 13. +LaTeX Info: Redefining \pageref on input line 13. + (./Manual.out) +(./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 16. +LaTeX Font Info: Try loading font information for OMS+cmr on input line 23. + (/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 23. + (./Manual.toc +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 9. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 9. + +[1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) +\tf@toc=\write5 +\openout5 = `Manual.toc'. + +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 37. + +(./table-theme.tex +Overfull \hbox (32.11844pt too wide) in alignment at lines 1--23 + [] [] + [] + + +Underfull \vbox (badness 10000) detected at line 23 + [] + + +Overfull \hbox (32.11844pt too wide) in alignment at lines 23--29 + [] [] + [] + +) [2] +Overfull \hbox (38.08037pt too wide) in paragraph at lines 62--65 +\OT1/cmr/m/n/10 shown in the bot-tom. This im-age has the same back-ground colo +r of splas[]inactive[]bar.png + [] + +(./table-config.tex +Underfull \vbox (badness 10000) detected at line 9 + [] + +) (../../../../../Licenses/GFDL.tex +Underfull \hbox (badness 10000) in paragraph at lines 5--14 + + [] + +[3] [4] +Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 +\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple + HTML, PostScript + [] + +[5] [6] [7] [8] [9] [10]) [11] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 2751 strings out of 94500 + 36619 string characters out of 1176766 + 89633 words of memory out of 1000000 + 5870 multiletter control sequences out of 10000+50000 + 9615 words of font info for 34 fonts, out of 500000 for 2000 + 580 hyphenation exceptions out of 1000 + 27i,6n,36p,222b,214s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 193 PDF objects out of 300000 + 38 named destinations out of 131072 + 169 words of extra memory for PDF output out of 65536 + +Output written on Manual.pdf (11 pages, 118515 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.out new file mode 100644 index 0000000..2f29f36 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.out @@ -0,0 +1,19 @@ +\BOOKMARK [1][-]{section.1}{Workplace}{} +\BOOKMARK [1][-]{section.2}{Theme}{} +\BOOKMARK [1][-]{section.3}{Design}{} +\BOOKMARK [1][-]{section.4}{Configuration}{} +\BOOKMARK [1][-]{section.5}{Rendering}{} +\BOOKMARK [1][-]{section.6}{Testing}{} +\BOOKMARK [1][-]{section.7}{Issues}{} +\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} +\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} +\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} +\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} +\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} +\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} +\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} +\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} +\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} +\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.pdf new file mode 100644 index 0000000..499b4e2 Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.toc new file mode 100644 index 0000000..dd5b675 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/Manual.toc @@ -0,0 +1,19 @@ +\contentsline {section}{\numberline {1}Workplace}{2}{section.1} +\contentsline {section}{\numberline {2}Theme}{2}{section.2} +\contentsline {section}{\numberline {3}Design}{2}{section.3} +\contentsline {section}{\numberline {4}Configuration}{3}{section.4} +\contentsline {section}{\numberline {5}Rendering}{3}{section.5} +\contentsline {section}{\numberline {6}Testing}{3}{section.6} +\contentsline {section}{\numberline {7}Issues}{3}{section.7} +\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8} +\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{4}{subsection.8.1} +\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{6}{subsection.8.2} +\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{6}{subsection.8.3} +\contentsline {subsection}{\numberline {8.4}Modifications}{7}{subsection.8.4} +\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5} +\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{9}{subsection.8.6} +\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{9}{subsection.8.7} +\contentsline {subsection}{\numberline {8.8}Translation}{10}{subsection.8.8} +\contentsline {subsection}{\numberline {8.9}Termination}{10}{subsection.8.9} +\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{10}{subsection.8.10} +\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/build.sh b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/build.sh new file mode 100755 index 0000000..d166fec --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/build.sh @@ -0,0 +1,55 @@ +#!/bin/bash +# +# Build KSplash tables for LaTeX document. +# +# Copyright (C) 2009 Alain Reguera Delgado +# +# 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:$ +#-------------------------------------- + +# Load functions. +. ~/artwork/trunk/Scripts/Bash/loadFunctions. + +# Define the names of your tables. +FILES="table-theme.tex + table-config.tex" + +for FILE in $FILES;do + + # Let know what table we are creating. + echo $FILE + + case $FILE in + + table-theme.tex ) + # Create table holding theme files. + ROWS="$(getFiles '/usr/share/apps/ksplash/Themes' '/Modern/.*')" + ;; + + table-config.tex ) + # Create table holding configuration files. + ROWS="$(getFiles '/usr/share/config' 'ksplashrc')" + ;; + + esac + + # Create table. + createTable "$ROWS" "" "" > $FILE + +done diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/manual.tex new file mode 100644 index 0000000..e7588d4 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/manual.tex @@ -0,0 +1,95 @@ +\documentclass{article} +\usepackage{longtable} +\usepackage[pdftex]{graphicx} +\usepackage{hyperref} +\hypersetup{pdfauthor={CentOS Documentation SIG},% + pdftitle={KDE Splash)},% + pdfsubject={CentOS Corporate Visual Identity}% + } + +\title{KDE Splash} +\author{CentOS Documentation SIG} + +\begin{document} + +\maketitle + +\begin{abstract} + +This article describes the KDE Splash Visual Style for CentOS +Distribution. This image is displayed after login screen, while KDE +session is being loaded. + +Copyright \copyright\ 2010\ The CentOS Project. Permission is +granted to copy, distribute and/or modify this document under the +terms of the GNU Free Documentation License, Version 1.2 or any later +version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the +license is included in the section entitled ``GNU Free Documentation +License''. +\end{abstract} + +\tableofcontents + + +\section{Workplace} +\begin{itemize} +\item SVN:trunk/Identity/Themes/\$THEME/Distro/BootUp/KSplash/ +\item SVN:trunk/Translations/Identity/Themes/Distro/BootUp/KSplash/ +\item SVN:trunk/Scripts/Identity/Themes/Distro/BootUp/KSplash/ +\end{itemize} + +\section{Theme} + +\input{table-theme.tex} + +\section{Design} + +KDE Splash Preview.png and splash\_top\_bar.png images are rendered +for each major release of CentOS Distribution. Each image is based in +the same Artistic Motif and has the following components: + +\begin{enumerate} +\item The CentOS Symbol. +\item The CentOS Release Brand. +\item The CentOS Default Artistic Motif. +\end{enumerate} + +KDE Splash splash\_inactive\_bar.png and splash\_active\_bar.png are +used to create the progress effect while loading. They both have the +same background color. + +KDE Splash splash\_bottom\_bar.png is used to as background to the +label shown in the bottom. This image has the same background color of +splas\_inactive\_bar.png and splash\_active\_bar.png. + +KDE Splash theme definitions are in the file Theme.rc. Among available +definitions are the splash name, description, version, author, +engine, icons flashing, always show progress, and label foreground. + +Image rendering is done using the script render.sh available in the +workplace. This script creates the appropriate PNG images under +img/\$VERSION/. + +There is no color limitation in this section. + +\section{Configuration} + +\input{table-config.tex} + +\begin{description} + +\item[Theme]: Defines the default splash theme. The name should match +a directory name under /usr/share/ksplash/Themes/. + +\texttt{Theme=Modern} +\end{description} + +\section{Rendering} +\section{Testing} +\section{Issues} + +% License section +\input{../../../../../Licenses/GFDL.tex} + +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-1.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-1.tex new file mode 100644 index 0000000..19455f1 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-1.tex @@ -0,0 +1,29 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/Preview.png\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & PNG image data, 400 x 322, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_active\_bar.png\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & PNG image data, 400 x 61, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_bottom.png\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & PNG image data, 400 x 16, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_inactive\_bar.png\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & PNG image data, 400 x 61, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_top.png\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & PNG image data, 400 x 245, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/Theme.rc\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & ASCII English text\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-2.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-2.tex new file mode 100644 index 0000000..1d5c195 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-2.tex @@ -0,0 +1,9 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/config/ksplashrc\\ +\textbf{Package}: & kdebase\\ +\textbf{Description}: & ASCII text\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-config.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-config.tex new file mode 100644 index 0000000..1d5c195 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-config.tex @@ -0,0 +1,9 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/config/ksplashrc\\ +\textbf{Package}: & kdebase\\ +\textbf{Description}: & ASCII text\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-theme.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-theme.tex new file mode 100644 index 0000000..0c70e78 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/KSplash/table-theme.tex @@ -0,0 +1,29 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/Preview.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 400 x 322, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_active\_bar.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 400 x 61, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_bottom.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 400 x 16, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_inactive\_bar.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 400 x 61, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/splash\_top.png\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & PNG image data, 400 x 245, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/apps/ksplash/Themes/Modern/Theme.rc\\ +\textbf{Package}: & \textbf{Unknown!}\\ +\textbf{Description}: & ASCII English text\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.aux new file mode 100644 index 0000000..06c3696 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.aux @@ -0,0 +1,47 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\gdef \LT@i {\LT@entry + {1}{72.64pt}\LT@entry + {1}{287.61165pt}} +\@writefile{toc}{\contentsline {section}{\numberline {1}Workplace}{2}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Theme}{2}{section.2}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{3}{section.3}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Configuration}{3}{section.4}} +\@writefile{toc}{\contentsline {section}{\numberline {5}Rendering}{3}{section.5}} +\@writefile{toc}{\contentsline {section}{\numberline {6}Testing}{3}{section.6}} +\@writefile{toc}{\contentsline {section}{\numberline {7}Issues}{3}{section.7}} +\@writefile{toc}{\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8}} +\newlabel{sec:License-GFDL-0}{{8}{3}{Preamble\relax }{section*.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{3}{subsection.8.1}} +\newlabel{sec:License-GFDL-1}{{8.1}{3}{Applicability And Definitions\relax }{subsection.8.1}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{5}{subsection.8.2}} +\newlabel{sec:License-GFDL-2}{{8.2}{5}{Verbatim Copying\relax }{subsection.8.2}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{5}{subsection.8.3}} +\newlabel{sec:License-GFDL-3}{{8.3}{5}{Copying In Quantity\relax }{subsection.8.3}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.4}Modifications}{6}{subsection.8.4}} +\newlabel{sec:License-GFDL-4}{{8.4}{6}{Modifications\relax }{subsection.8.4}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5}} +\newlabel{sec:License-GFDL-5}{{8.5}{8}{Combining Documents\relax }{subsection.8.5}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{8}{subsection.8.6}} +\newlabel{sec:License-GFDL-6}{{8.6}{8}{Collections Of Documents\relax }{subsection.8.6}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{8}{subsection.8.7}} +\newlabel{sec:License-GFDL-7}{{8.7}{8}{Aggregation With Independent Works\relax }{subsection.8.7}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.8}Translation}{9}{subsection.8.8}} +\newlabel{sec:License-GFDL-8}{{8.8}{9}{Translation\relax }{subsection.8.8}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.9}Termination}{9}{subsection.8.9}} +\newlabel{sec:License-GFDL-9}{{8.9}{9}{Termination\relax }{subsection.8.9}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{9}{subsection.8.10}} +\newlabel{sec:License-GFDL-10}{{8.10}{9}{Future Revisions OF This License\relax }{subsection.8.10}{}} +\@writefile{toc}{\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11}} +\newlabel{sec:License-GFDL-11}{{8.11}{10}{How to use this License for your documents\relax }{subsection.8.11}{}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.log new file mode 100644 index 0000000..1d33b78 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.log @@ -0,0 +1,258 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 5 FEB 2010 15:47 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size10.clo +File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/tools/longtable.sty +Package: longtable 2004/02/01 v4.11 Multi-page Table package (DPC) +\LTleft=\skip43 +\LTright=\skip44 +\LTpre=\skip45 +\LTpost=\skip46 +\LTchunksize=\count87 +\LTcapwidth=\dimen103 +\LT@head=\box26 +\LT@firsthead=\box27 +\LT@foot=\box28 +\LT@lastfoot=\box29 +\LT@cols=\count88 +\LT@rows=\count89 +\c@LT@tables=\count90 +\c@LT@chunks=\count91 +\LT@p@ftn=\toks14 +) +(/usr/share/texmf/tex/latex/graphics/graphicx.sty +Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks15 +) +(/usr/share/texmf/tex/latex/graphics/graphics.sty +Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) + +(/usr/share/texmf/tex/latex/graphics/trig.sty +Package: trig 1999/03/16 v1.09 sin cos tan (DPC) +) +(/usr/share/texmf/tex/latex/graphics/graphics.cfg +File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive +) +Package graphics Info: Driver file: pdftex.def on input line 80. + +(/usr/share/texmf/tex/latex/graphics/pdftex.def +File: pdftex.def 2002/06/19 v0.03k graphics/color for pdftex +\Gread@gobject=\count92 +)) +\Gin@req@height=\dimen104 +\Gin@req@width=\dimen105 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX +\@linkdim=\dimen106 +\Hy@linkcounter=\count93 +\Hy@pagecounter=\count94 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count95 +\Field@Width=\dimen107 +\Fld@charsize=\dimen108 +\Choice@toks=\toks16 +\Field@toks=\toks17 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count96 +\c@Hfootnote=\count97 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count98 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 13. +LaTeX Font Info: ... okay on input line 13. + +(/usr/share/texmf/tex/context/base/supp-pdf.tex +(/usr/share/texmf/tex/context/base/supp-mis.tex +loading : Context Support Macros / Miscellaneous (2004.10.26) +\protectiondepth=\count99 +\scratchcounter=\count100 +\scratchtoks=\toks18 +\scratchdimen=\dimen109 +\scratchskip=\skip47 +\scratchmuskip=\muskip11 +\scratchbox=\box30 +\scratchread=\read1 +\scratchwrite=\write4 +\zeropoint=\dimen110 +\onepoint=\dimen111 +\onebasepoint=\dimen112 +\minusone=\count101 +\thousandpoint=\dimen113 +\onerealpoint=\dimen114 +\emptytoks=\toks19 +\nextbox=\box31 +\nextdepth=\dimen115 +\everyline=\toks20 +\!!counta=\count102 +\!!countb=\count103 +\recursecounter=\count104 +) +loading : Context Support Macros / PDF (2004.03.26) +\nofMPsegments=\count105 +\nofMParguments=\count106 +\MPscratchCnt=\count107 +\MPscratchDim=\dimen116 +\MPnumerator=\count108 +\everyMPtoPDFconversion=\toks21 +) +Package hyperref Info: Link coloring OFF on input line 13. + (/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count109 +) +LaTeX Info: Redefining \ref on input line 13. +LaTeX Info: Redefining \pageref on input line 13. + (./Manual.out) +(./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 16. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 16. +LaTeX Font Info: Try loading font information for OMS+cmr on input line 23. + (/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 23. + (./Manual.toc +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 9. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 9. + +[1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]) +\tf@toc=\write5 +\openout5 = `Manual.toc'. + +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 37. + +(./table-theme.tex +Overfull \hbox (15.25165pt too wide) in alignment at lines 1--21 + [] [] + [] + + +Underfull \vbox (badness 10000) detected at line 21 + [] + +) (../../../../../Licenses/GFDL.tex +Underfull \hbox (badness 10000) in paragraph at lines 5--14 + + [] + +[2] [3] +Overfull \hbox (3.86182pt too wide) in paragraph at lines 93--103 +\OT1/cmr/m/n/10 ing a pub-licly avail-able DTD, and standard-conforming sim-ple + HTML, PostScript + [] + +[4] [5] [6] [7] [8] [9]) [10] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 2741 strings out of 94500 + 36518 string characters out of 1176766 + 89618 words of memory out of 1000000 + 5868 multiletter control sequences out of 10000+50000 + 9615 words of font info for 34 fonts, out of 500000 for 2000 + 580 hyphenation exceptions out of 1000 + 27i,6n,36p,222b,214s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 185 PDF objects out of 300000 + 33 named destinations out of 131072 + 169 words of extra memory for PDF output out of 65536 + +Output written on Manual.pdf (10 pages, 115636 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.out new file mode 100644 index 0000000..2f29f36 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.out @@ -0,0 +1,19 @@ +\BOOKMARK [1][-]{section.1}{Workplace}{} +\BOOKMARK [1][-]{section.2}{Theme}{} +\BOOKMARK [1][-]{section.3}{Design}{} +\BOOKMARK [1][-]{section.4}{Configuration}{} +\BOOKMARK [1][-]{section.5}{Rendering}{} +\BOOKMARK [1][-]{section.6}{Testing}{} +\BOOKMARK [1][-]{section.7}{Issues}{} +\BOOKMARK [1][-]{section.8}{GNU Free Documentation License}{} +\BOOKMARK [2][-]{subsection.8.1}{Applicability And Definitions}{section.8} +\BOOKMARK [2][-]{subsection.8.2}{Verbatim Copying}{section.8} +\BOOKMARK [2][-]{subsection.8.3}{Copying In Quantity}{section.8} +\BOOKMARK [2][-]{subsection.8.4}{Modifications}{section.8} +\BOOKMARK [2][-]{subsection.8.5}{Combining Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.6}{Collections Of Documents}{section.8} +\BOOKMARK [2][-]{subsection.8.7}{Aggregation With Independent Works}{section.8} +\BOOKMARK [2][-]{subsection.8.8}{Translation}{section.8} +\BOOKMARK [2][-]{subsection.8.9}{Termination}{section.8} +\BOOKMARK [2][-]{subsection.8.10}{Future Revisions OF This License}{section.8} +\BOOKMARK [2][-]{subsection.8.11}{How to use this License for your documents}{section.8} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.pdf new file mode 100644 index 0000000..e01a152 Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.toc new file mode 100644 index 0000000..ca825b6 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/Manual.toc @@ -0,0 +1,19 @@ +\contentsline {section}{\numberline {1}Workplace}{2}{section.1} +\contentsline {section}{\numberline {2}Theme}{2}{section.2} +\contentsline {section}{\numberline {3}Design}{3}{section.3} +\contentsline {section}{\numberline {4}Configuration}{3}{section.4} +\contentsline {section}{\numberline {5}Rendering}{3}{section.5} +\contentsline {section}{\numberline {6}Testing}{3}{section.6} +\contentsline {section}{\numberline {7}Issues}{3}{section.7} +\contentsline {section}{\numberline {8}GNU Free Documentation License}{3}{section.8} +\contentsline {subsection}{\numberline {8.1}Applicability And Definitions}{3}{subsection.8.1} +\contentsline {subsection}{\numberline {8.2}Verbatim Copying}{5}{subsection.8.2} +\contentsline {subsection}{\numberline {8.3}Copying In Quantity}{5}{subsection.8.3} +\contentsline {subsection}{\numberline {8.4}Modifications}{6}{subsection.8.4} +\contentsline {subsection}{\numberline {8.5}Combining Documents}{8}{subsection.8.5} +\contentsline {subsection}{\numberline {8.6}Collections Of Documents}{8}{subsection.8.6} +\contentsline {subsection}{\numberline {8.7}Aggregation With Independent Works}{8}{subsection.8.7} +\contentsline {subsection}{\numberline {8.8}Translation}{9}{subsection.8.8} +\contentsline {subsection}{\numberline {8.9}Termination}{9}{subsection.8.9} +\contentsline {subsection}{\numberline {8.10}Future Revisions OF This License}{9}{subsection.8.10} +\contentsline {subsection}{\numberline {8.11}How to use this License for your documents}{10}{subsection.8.11} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/build.sh b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/build.sh new file mode 100755 index 0000000..5fa8a04 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/build.sh @@ -0,0 +1,50 @@ +#!/bin/bash +# +# Build RHGB tables for LaTeX documents. +# +# Copyright (C) 2009 Alain Reguera Delgado +# +# 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:$ +#-------------------------------------- + +# Load functions. +. ~/artwork/trunk/Scripts/Bash/loadFunctions.sh + +# Define the names of your tables. +FILES="table-theme.tex" + +for FILE in $FILES;do + + # Let know which table we are creating. + echo $FILE + + # Define what to do with each table you define on FILES. + case $FILE in + + table-theme.tex ) + # Create table holding theme files. + ROWS="$(getFiles '/usr/share/rhgb' '.*\.png')" + ;; + + esac + + # Create table. + createTable "$ROWS" "" "" > $FILE + +done diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/manual.tex new file mode 100644 index 0000000..d8bab77 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/manual.tex @@ -0,0 +1,60 @@ +\documentclass{article} +\usepackage{longtable} +\usepackage[pdftex]{graphicx} +\usepackage{hyperref} +\hypersetup{pdfauthor={CentOS Documentation SIG},% + pdftitle={Graphic Boot (RHGB))},% + pdfsubject={CentOS Corporate Visual Identity}% + } + +\title{Graphic Boot (RHGB)} +\author{CentOS Documentation SIG} + +\begin{document} + +\maketitle + +\begin{abstract} + +This article describes the RHGB Visual Style for CentOS Distribution. +This screen is shown as the machine starts up. Users can toggle +between graphic ``Hide Detail'' mode text ``Show Detail'' mode. + +Copyright \copyright\ 2010\ The CentOS Project. Permission is +granted to copy, distribute and/or modify this document under the +terms of the GNU Free Documentation License, Version 1.2 or any later +version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the +license is included in the section entitled ``GNU Free Documentation +License''. +\end{abstract} + +\tableofcontents + +\section{Workplace} + +\begin{itemize} +\item SVN:trunk/Identity/Themes/\$THEME/Distro/BootUp/RHGB/ +\item SVN:trunk/Translations/Identity/Themes/Distro/BootUp/RHGB/ +\item SVN:trunk/Scripts/Identity/Themes/Distro/BootUp/RHGB/ +\end{itemize} + +\section{Theme} + +\input{table-theme.tex} + +The system-logo.png image is rendered for each major release of +CentOS. This task is done using the script render.sh available in the +workplace. This script creates the appropriate PNG images under +img/\$VERSION/ directory. + +\section{Design} +\section{Configuration} +\section{Rendering} +\section{Testing} +\section{Issues} + +% License section +\input{../../../../../Licenses/GFDL.tex} + +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/table-1.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/table-1.tex new file mode 100644 index 0000000..a6a140c --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/table-1.tex @@ -0,0 +1,21 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/rhgb/large-computer.png\\ +\textbf{Package}: & rhgb\\ +\textbf{Description}: & PNG image data, 520 x 230, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/rhgb/main-logo.png\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & PNG image data, 497 x 166, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/rhgb/system-logo.png\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & PNG image data, 147 x 39, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/rhgb/throbber-anim.png\\ +\textbf{Package}: & rhgb\\ +\textbf{Description}: & PNG image data, 288 x 24, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/table-theme.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/table-theme.tex new file mode 100644 index 0000000..b9b3d6f --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/BootUp/RHGB/table-theme.tex @@ -0,0 +1,21 @@ +\begin{longtable}{rl} +\hline +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/rhgb/large-computer.png\\ +\textbf{Package}: & rhgb\\ +\textbf{Description}: & PNG image data, 530 x 240, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/rhgb/main-logo.png\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & PNG image data, 497 x 166, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/rhgb/system-logo.png\\ +\textbf{Package}: & redhat-logos\\ +\textbf{Description}: & PNG image data, 147 x 39, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\textbf{Target}: & /usr/share/rhgb/throbber-anim.png\\ +\textbf{Package}: & rhgb\\ +\textbf{Description}: & PNG image data, 288 x 24, 8-bit/color RGBA, non-interlaced\\ +\multicolumn{2}{l}{\ }\\ +\hline +\end{longtable} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.aux new file mode 100644 index 0000000..db1ff68 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.aux @@ -0,0 +1,17 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{1}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Workplace}{2}{section.2}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{2}{section.3}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Rendering}{3}{section.4}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.log new file mode 100644 index 0000000..ca0bde3 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.log @@ -0,0 +1,163 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 31 JAN 2010 19:04 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size10.clo +File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks14 +) +\@linkdim=\dimen103 +\Hy@linkcounter=\count87 +\Hy@pagecounter=\count88 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count89 +\Field@Width=\dimen104 +\Fld@charsize=\dimen105 +\Choice@toks=\toks15 +\Field@toks=\toks16 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count90 +\c@Hfootnote=\count91 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count92 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 11. +LaTeX Font Info: ... okay on input line 11. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 11. +LaTeX Font Info: ... okay on input line 11. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 11. +LaTeX Font Info: ... okay on input line 11. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 11. +LaTeX Font Info: ... okay on input line 11. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 11. +LaTeX Font Info: ... okay on input line 11. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 11. +LaTeX Font Info: ... okay on input line 11. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 11. +LaTeX Font Info: ... okay on input line 11. +Package hyperref Info: Link coloring OFF on input line 11. + +(/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count93 +) +LaTeX Info: Redefining \ref on input line 11. +LaTeX Info: Redefining \pageref on input line 11. + (./Manual.out) (./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 14. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 14. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 14. +(./Manual.toc) +\tf@toc=\write4 +\openout4 = `Manual.toc'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 24. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 24. + [1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] +LaTeX Font Info: Try loading font information for OMS+cmr on input line 66. + +(/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 66. + [2] [3] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 1960 strings out of 94500 + 26775 string characters out of 1176766 + 75186 words of memory out of 1000000 + 5140 multiletter control sequences out of 10000+50000 + 9399 words of font info for 33 fonts, out of 500000 for 2000 + 580 hyphenation exceptions out of 1000 + 27i,8n,36p,148b,266s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 85 PDF objects out of 300000 + 12 named destinations out of 131072 + 49 words of extra memory for PDF output out of 65536 + +Output written on Manual.pdf (3 pages, 74579 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.out new file mode 100644 index 0000000..f48d4c8 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.out @@ -0,0 +1,4 @@ +\BOOKMARK [1][-]{section.1}{Introduction}{} +\BOOKMARK [1][-]{section.2}{Workplace}{} +\BOOKMARK [1][-]{section.3}{Design}{} +\BOOKMARK [1][-]{section.4}{Rendering}{} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.pdf new file mode 100644 index 0000000..3be2e1b Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.toc new file mode 100644 index 0000000..796149c --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/Manual.toc @@ -0,0 +1,4 @@ +\contentsline {section}{\numberline {1}Introduction}{1}{section.1} +\contentsline {section}{\numberline {2}Workplace}{2}{section.2} +\contentsline {section}{\numberline {3}Design}{2}{section.3} +\contentsline {section}{\numberline {4}Rendering}{3}{section.4} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/manual.tex new file mode 100644 index 0000000..d78644f --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Distro/Releases/manual.tex @@ -0,0 +1,101 @@ +% +% Describe The CentOS Distribution Release Schema. +% +\documentclass{article} + +\usepackage{hyperref} + +\title{The CentOS Release Brand} +\author{Alain Reguera Delgado} + +\begin{document} + +\maketitle + +\begin{abstract} +This is abstract. +\end{abstract} + +\tableofcontents + +\section{Introduction} + +The upstream vendor has released 3 versions of Enterprise Linux that +CentOS Project rebuilds the freely available SRPMS for\footnote{ +\url{http://wiki.centos.org/About}}. So, the major CentOS releases are +CentOS 3, CentOS 4 and CentOS 5. The upstream vendor releases security +updates as required by circumstances. CentOS Project releases rebuilds +of security updates as soon as possible. Usually within 24 hours (our +stated goal is with 72 hours, but we are usually much faster). + +The upstream vendor also releases numbered update sets for Version 3, +Version 4 and Version 5 of their product (i.e. EL 3 update 9, EL 4 +update 6 and EL 5 update 1) 2 to 4 times per year. There are new ISOs +from the upstream vendor provided for these update sets. Update sets +will be completed as soon as possible after the vendor releases their +version\ldots generally within 2 weeks. CentOS Project follows these +conventions as well, so CentOS 3.9 correlates with EL 3 update 9 and +CentOS 4.6 correlates with EL 4 update 6, CentOS 5.1 correlates to EL +5 update 1, etc. + +One thing some people have problems understanding is that if you have +any CentOS-3 product and update it, you will be updated to the latest +CentOS-3.x version. The same is true for CentOS-4 and CentOS 5. If you +update any CentOS-4 product, you will be updated to the latest +CentOS-4.x version, or to the latest CentOS 5.x version if you are +updating a CentOS 5 system. This is exactly the same behavior as the +upstream product. Let's assume that the latest EL4 product is update +6. If you install the upstream original EL4 CDs (the ones before any +update set) and upgrade via their up2date, you will have latest update +set installed (EL4 update 6 in our example). + +Since all updates within a major release (CentOS 3, CentOS 4, CentOS +5) always upgrade to the latest version when updates are performed +(thus mimicking upstream behavior), only the latest version is +maintained in each main tree on the CentOS +Mirrors\footnote{\url{http://mirrors.centos.org/}}. + +There is a CentOS Vault\footnote{\url{http://vault.centos.org/}} +containing old CentOS trees. This vault is a picture of the older tree +when it was removed from the main tree, and does not receive updates. +It should only be used for reference. + +\section{Workplace} + +\begin{itemize} +\item SVN:trunk/Identity/Logos/svg/type/2c-tmr.svg +\item SVN:trunk/Identity/Logos/svg/type/build/tmr3.svg +\item SVN:trunk/Identity/Logos/svg/type/build/tmr4.svg +\item SVN:trunk/Identity/Logos/svg/type/build/tmr5.svg +\end{itemize} + +\section{Design} + +It is very important that people differentiate which is the major +release of CentOS Distribution they are using. To achive this, we use +a special brand called \textit{The Release Brand} of CentOS +Distribution. + +There is one Release Brand for each Major Release of CentOS +Distribution. The Release Brand of CentOS Distribution is placed on +images controlling the CentOS Distribution Visual Style. + +The Release Brand of CentOS Distribution is built using two +components: 1. The CentOS Trademark, 2. The Major Release Number of +CentOS Distribution. + +The height of the Release Number is twice the CentOS Trademark height +and it is placed on the right side of CentOS Trademark, both bottom +aligned. + +Sometimes The CentOS Message can be added as third component to The +Release Brand. In these cases The CentOS Message remains on English +language, it is not translated. Because of this, The Release Brand +that includes The CentOS Message should be avoided or used in places +where there is no posibility for the user to select a different +language but English. Examples of these kind of images are Anaconda +Prompt and GRUB. + +\section{Rendering} + +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.aux b/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.aux new file mode 100644 index 0000000..d4e6ed1 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.aux @@ -0,0 +1,19 @@ +\relax +\ifx\hyper@anchor\@undefined +\global \let \oldcontentsline\contentsline +\gdef \contentsline#1#2#3#4{\oldcontentsline{#1}{#2}{#3}} +\global \let \oldnewlabel\newlabel +\gdef \newlabel#1#2{\newlabelxx{#1}#2} +\gdef \newlabelxx#1#2#3#4#5#6{\oldnewlabel{#1}{{#2}{#3}}} +\AtEndDocument{\let \contentsline\oldcontentsline +\let \newlabel\oldnewlabel} +\else +\global \let \hyper@last\relax +\fi + +\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction}{1}{section.1}} +\@writefile{toc}{\contentsline {section}{\numberline {2}Workplace}{2}{section.2}} +\@writefile{toc}{\contentsline {section}{\numberline {3}Design}{2}{section.3}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.1}The CentOS Motif Brand}{2}{subsection.3.1}} +\@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Recommendations}{2}{subsection.3.2}} +\@writefile{toc}{\contentsline {section}{\numberline {4}Rendering}{3}{section.4}} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.log b/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.log new file mode 100644 index 0000000..88450e0 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.log @@ -0,0 +1,171 @@ +This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (format=pdflatex 2009.1.14) 1 FEB 2010 00:49 +entering extended mode +**Manual.tex +(./Manual.tex +LaTeX2e <2003/12/01> +Babel and hyphenation patterns for american, french, german, ngerman, b +ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e +stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis +h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur +kish, ukrainian, nohyphenation, loaded. +(/usr/share/texmf/tex/latex/base/article.cls +Document Class: article 2004/02/16 v1.4f Standard LaTeX document class +(/usr/share/texmf/tex/latex/base/size10.clo +File: size10.clo 2004/02/16 v1.4f Standard LaTeX file (size option) +) +\c@part=\count79 +\c@section=\count80 +\c@subsection=\count81 +\c@subsubsection=\count82 +\c@paragraph=\count83 +\c@subparagraph=\count84 +\c@figure=\count85 +\c@table=\count86 +\abovecaptionskip=\skip41 +\belowcaptionskip=\skip42 +\bibindent=\dimen102 +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.sty +Package: hyperref 2003/11/30 v6.74m Hypertext links for LaTeX + +(/usr/share/texmf/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV@toks@=\toks14 +) +\@linkdim=\dimen103 +\Hy@linkcounter=\count87 +\Hy@pagecounter=\count88 + +(/usr/share/texmf/tex/latex/hyperref/pd1enc.def +File: pd1enc.def 2003/11/30 v6.74m Hyperref: PDFDocEncoding definition (HO) +) +(/usr/share/texmf/tex/latex/hyperref/hyperref.cfg +File: hyperref.cfg 2002/06/06 v1.2 hyperref configuration of TeXLive and teTeX +) +Package hyperref Info: Hyper figures OFF on input line 1880. +Package hyperref Info: Link nesting OFF on input line 1885. +Package hyperref Info: Hyper index ON on input line 1888. +Package hyperref Info: Plain pages ON on input line 1893. +Package hyperref Info: Backreferencing OFF on input line 1900. + +Implicit mode ON; LaTeX internals redefined +Package hyperref Info: Bookmarks ON on input line 2004. +(/usr/share/texmf/tex/latex/url/url.sty +\Urlmuskip=\muskip10 +Package: url 2004/03/15 ver 3.1 Verb mode for urls, etc. +) +LaTeX Info: Redefining \url on input line 2143. +\Fld@menulength=\count89 +\Field@Width=\dimen104 +\Fld@charsize=\dimen105 +\Choice@toks=\toks15 +\Field@toks=\toks16 +Package hyperref Info: Hyper figures OFF on input line 2618. +Package hyperref Info: Link nesting OFF on input line 2623. +Package hyperref Info: Hyper index ON on input line 2626. +Package hyperref Info: backreferencing OFF on input line 2633. +Package hyperref Info: Link coloring OFF on input line 2638. +\c@Item=\count90 +\c@Hfootnote=\count91 +) +*hyperref using default driver hpdftex* +(/usr/share/texmf/tex/latex/hyperref/hpdftex.def +File: hpdftex.def 2003/11/30 v6.74m Hyperref driver for pdfTeX + +(/usr/share/texmf/tex/latex/psnfss/pifont.sty +Package: pifont 2004/09/15 PSNFSS-v9.2 Pi font support (SPQR) +LaTeX Font Info: Try loading font information for U+pzd on input line 63. + +(/usr/share/texmf/tex/latex/psnfss/upzd.fd +File: upzd.fd 2001/06/04 font definitions for U/pzd. +) +LaTeX Font Info: Try loading font information for U+psy on input line 64. + +(/usr/share/texmf/tex/latex/psnfss/upsy.fd +File: upsy.fd 2001/06/04 font definitions for U/psy. +)) +\Fld@listcount=\count92 +\@outlinefile=\write3 +) (./Manual.aux) +\openout1 = `Manual.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 10. +LaTeX Font Info: ... okay on input line 10. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 10. +LaTeX Font Info: ... okay on input line 10. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 10. +LaTeX Font Info: ... okay on input line 10. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 10. +LaTeX Font Info: ... okay on input line 10. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 10. +LaTeX Font Info: ... okay on input line 10. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 10. +LaTeX Font Info: ... okay on input line 10. +LaTeX Font Info: Checking defaults for PD1/pdf/m/n on input line 10. +LaTeX Font Info: ... okay on input line 10. +Package hyperref Info: Link coloring OFF on input line 10. + +(/usr/share/texmf/tex/latex/hyperref/nameref.sty +Package: nameref 2003/12/03 v2.21 Cross-referencing by name of section +\c@section@level=\count93 +) +LaTeX Info: Redefining \ref on input line 10. +LaTeX Info: Redefining \pageref on input line 10. + (./Manual.out) (./Manual.out) +\openout3 = `Manual.out'. + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <12> on input line 13. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <8> on input line 13. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 13. +(./Manual.toc +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 4. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 4. +) +\tf@toc=\write4 +\openout4 = `Manual.toc'. + + [1 + +{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] +LaTeX Font Info: Try loading font information for OMS+cmr on input line 78. + +(/usr/share/texmf/tex/latex/base/omscmr.fd +File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions +) +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available +(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 78. + +Overfull \hbox (70.63863pt too wide) in paragraph at lines 101--104 +\OT1/cmr/m/n/10 Cen-tOS Palette is avail-able at SVN:trunk/Identity/Themes/Mode +rn/Palettes/Default.gpl. + [] + +[2] [3] (./Manual.aux) ) +Here is how much of TeX's memory you used: + 1964 strings out of 94500 + 26838 string characters out of 1176766 + 75178 words of memory out of 1000000 + 5143 multiletter control sequences out of 10000+50000 + 10065 words of font info for 35 fonts, out of 500000 for 2000 + 580 hyphenation exceptions out of 1000 + 27i,8n,36p,148b,214s stack positions out of 1500i,500n,5000p,200000b,5000s +PDF statistics: + 96 PDF objects out of 300000 + 12 named destinations out of 131072 + 65 words of extra memory for PDF output out of 65536 + +Output written on Manual.pdf (3 pages, 90737 bytes). diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.out b/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.out new file mode 100644 index 0000000..2a281ab --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.out @@ -0,0 +1,6 @@ +\BOOKMARK [1][-]{section.1}{Introduction}{} +\BOOKMARK [1][-]{section.2}{Workplace}{} +\BOOKMARK [1][-]{section.3}{Design}{} +\BOOKMARK [2][-]{subsection.3.1}{The CentOS Motif Brand}{section.3} +\BOOKMARK [2][-]{subsection.3.2}{Recommendations}{section.3} +\BOOKMARK [1][-]{section.4}{Rendering}{} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.pdf b/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.pdf new file mode 100644 index 0000000..4615239 Binary files /dev/null and b/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.pdf differ diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.toc b/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.toc new file mode 100644 index 0000000..3aa28c6 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/Manual.toc @@ -0,0 +1,6 @@ +\contentsline {section}{\numberline {1}Introduction}{1}{section.1} +\contentsline {section}{\numberline {2}Workplace}{2}{section.2} +\contentsline {section}{\numberline {3}Design}{2}{section.3} +\contentsline {subsection}{\numberline {3.1}The CentOS Motif Brand}{2}{subsection.3.1} +\contentsline {subsection}{\numberline {3.2}Recommendations}{2}{subsection.3.2} +\contentsline {section}{\numberline {4}Rendering}{3}{section.4} diff --git a/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/manual.tex b/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/manual.tex new file mode 100644 index 0000000..fef6047 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Identity/Themes/Motif/manual.tex @@ -0,0 +1,124 @@ +% +% Describe The CentOS Motif. +% +\documentclass{article} +\usepackage{hyperref} + +\title{The CentOS Motif} +\author{Alain Reguera Delgado} + +\begin{document} + +\maketitle + +\begin{abstract} +This manual describes the workplace, design, and rendering of CentOS +Artistic Motifs, both default and alternatives. +\end{abstract} + +\tableofcontents + +\section{Introduction} + +The CentOS Artistic Motif is an image used to enforce the CentOS +Project Visual Identity. The Artistic Motif is a pattern design used +to define the CentOS Visual Style. + +Due to our Monolithic Visual Structure, the CentOS Project's Visual +Identity is attached to one unique Visual Style, that is the CentOS +Default Visual Style. CentOS Default Visual Style is based on one +unique CentOS Artistic Motif, that is the CentOS Default Artistic +Motif. + +Changing the CentOS Default Visual Style is not very convenient +because that affects the ``recognition'' of CentOS Project. +Nevertheless, we want to see what do you have. Specially if your work +is an improvement to the base idea of CentOS Default Visual Style +(\emph{\textbf{Modern}, squares and circles flowing up.}). + +Additionally to the CentOS Default Artistic Motif, there are CentOS +Alternative Motifs. CentOS Alternative Motifs may or may not be +related with the current CentOS Default Artistic Motif. CentOS +Alternative Motfis are an space for new art creation, for designing +new and completely exiting artistic ideas. This place doesn't pretend +to replace sites like devianart.org, but to collect Artistic Motifs +focused on The CentOS Project and what it is. + +If you are not happy with the actual CentOS Default Artistic Motif, +you can look inside CentOS Alternative Motifs and if someone is +interesting enough you can download it from the CentOS Artwork +Repository and test it. If it turns popular enough it has posibilities +of become the CentOS Default Artistic Motif and by extension the +CentOS Default Visual Style. + +If you are not happy with CentOS Alternative Motifs either, then go an +design your own CentOS Alternative Artistic Moif and propose it in +\href{mailto:centos-devel@centos.org}{centos-devel@centos.org}. + +CentOS Default Artistic Motif and CentOS Alternative Motifs are +maintain by CentOS Community People. Generally, one person proposes +the first idea, later others join the effort to make that idea better. +The first person who proposes the idea is known as the Motif Author +and is she/he who owns the copyright of that work. People joinning the +effort are known as Motif Contributors. + +The CentOS Project is using the Creative Common Share-Alike +License\footnote{http://creativecommons.org/licenses/by-sa/3.0/} in +both CentOS Default Artistic Motif and CentOS Alternative Motifs. This +is, in order to brand an Artistic Motif as CentOS Motif, her/his +author should release her/his work under the previously mentioned +license. + +Only Artistic Motifs branded as CentOS Motif, both Default and +Alternatives, are hosted on CentOS Artwork Repository. + +\section{Workplace} + +\begin{itemize} +\item SVN:trunk/Identity/Themes/\$THEME/Motif/ +\item SVN:trunk/Manuals/Identity/Themes/Motif/ +\end{itemize} + +\section{Design} + +\subsection{The CentOS Motif Brand} + +\subsection{Recommendations} + +When designing Motifs for CentOS, consider the following +recommendations: + +\begin{itemize} + +\item Give a unique (case-sensitive) name to your Motif. This name is +used as value wherever \$THEME variable is. Optionally, you can add a +description about inspiration and concepts behind your work. + +\item Use the location SVN:trunk/Identity/Themes/\$THEME/Motif/ to +store your work. If it doesn't exist create it. Note that this require +you to have previous commit access in CentOS Artwork Repository. + +\item Use the CentOS Default Artistic Motif's Palette as base to your +work. CentOS Palette is available at +SVN:trunk/Identity/Themes/Modern/Palettes/Default.gpl. + +\item Make your work completely vectorial. Do not add raster images +inside it. + +\item Feel free to make your art enterprise-level and beautiful. + +\item Add the following information on your artwork (both in a visible +design area, and inside inkscape document metadata section wherever it +be possible): + +\begin{itemize} +\item The CentOS Motif Brand. +\item The name of your artistic motif. +\item The copyright sentence: \texttt{Copyright (C) YEAR YOURNAME} +\item The license under which the work is released. +\end{itemize} +\end{itemize} + +\section{Rendering} + +\end{document} diff --git a/Manuals/Repository/filesystem-latex/Licenses/centos-redistribution.tex b/Manuals/Repository/filesystem-latex/Licenses/centos-redistribution.tex new file mode 100644 index 0000000..b4adf87 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Licenses/centos-redistribution.tex @@ -0,0 +1,51 @@ +% +% CentOS Redistribution License. +% +\chapter{CentOS Redistribution License} +\noindent Revision 1.0, March 2010\\ +\noindent Copyright \copyright\ 2010 The CentOS Project.\\ +\\ +\noindent The \texttt{redhat-logos} and \texttt{redhat-artwork} +packages (the ``Packages'') contain image files which incorporate the +CentOS trademark, and CentOS logo (the ``Marks''). + +The CentOS Project grants you the right to use the Packages during the +normal operation of other software programs that call upon the +Packages. The CentOS Project grants to you the right and license to +copy and redistribute the unaltered Packages for both commerical and +non-commercial purposes. + +If you are rebranding or modifying the underlying distribution, or the +Packages, you must remove ``the Marks'' and rename the distribution +something other than CentOS. + +When redistributing using this license, the following applies: + +\begin{enumerate} + +\item The above copyright notice and this license are included with +each copy you make, and they remain intact and are not altered, +deleted, or modified in any way; + +\item You do not modify the appearance of any or all of the Logos in +any manner; and + +\item You do not use any or all of the Logos as, or as part of, a +trademark, trade name, or trade identifier; or in any other fashion +except as set forth in this license. + +\item No Warranty. The Packages are provided ``as are'' and any +express or implied warranties, including, but not limited to, the +implied warranties of merchantability and fitness for a particular +purpose are disclaimed. In no event shall the CentOS Project be liable +for any direct, indirect, incidental, special, exemplary, or +consequential damages ---including, but not limited to, procurement of +substitute goods or services; loss of use, data or profits; or +business interruption--- however caused and on any theory of +liability, whether in contract, strict liability, or tort ---including +negligence or otherwise--- arising in any way out of the use of this +package, even if advised of the possibility of such damage. + +\end{enumerate} + + diff --git a/Manuals/Repository/filesystem-latex/Licenses/gfdl.tex b/Manuals/Repository/filesystem-latex/Licenses/gfdl.tex new file mode 100644 index 0000000..60e6413 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Licenses/gfdl.tex @@ -0,0 +1,437 @@ +% Verbatim copy of GNU Free Documentation License. The License under +% which this document is released. +\chapter{GNU Free Documentation License} +\hypertarget{cha:Licenses:GFDL}{} +\label{cha:Licenses:GFDL} + +Version 1.2, November 2002 +\\ +\\ +Copyright \copyright\ 2000,2001,2002 Free Software Foundation, Inc. +\\ +59 Temple Place, Suite 330, Boston, MA 02111-1307, USA +\\ +Everyone is permitted to copy and distribute verbatim copies of this +license document, but changing it is not allowed. + +\section*{Preamble} +\label{sec:License-GFDL-0} + +The purpose of this License is to make a manual, textbook, or other +functional and useful document ``free'' in the sense of freedom: to +assure everyone the effective freedom to copy and redistribute it, +with or without modifying it, either commercially or noncommercially. +Secondarily, this License preserves for the author and publisher a way +to get credit for their work, while not being considered responsible +for modifications made by others. + +This License is a kind of ``copyleft'', which means that derivative +works of the document must themselves be free in the same sense. It +complements the GNU General Public License, which is a copyleft +license designed for free software. + +We have designed this License in order to use it for manuals for free +software, because free software needs free documentation: a free +program should come with manuals providing the same freedoms that the +software does. But this License is not limited to software manuals; +it can be used for any textual work, regardless of subject matter or +whether it is published as a printed book. We recommend this License +principally for works whose purpose is instruction or reference. + +\section{Applicability And Definitions} +\label{sec:License-GFDL-1} + +This License applies to any manual or other work, in any medium, that +contains a notice placed by the copyright holder saying it can be +distributed under the terms of this License. Such a notice grants a +world-wide, royalty-free license, unlimited in duration, to use that +work under the conditions stated herein. The ``Document'', below, +refers to any such manual or work. Any member of the public is a +licensee, and is addressed as ``you''. You accept the license if you +copy, modify or distribute the work in a way requiring permission +under copyright law. + +A ``Modified Version'' of the Document means any work containing the +Document or a portion of it, either copied verbatim, or with +modifications and/or translated into another language. + +A ``Secondary Section'' is a named appendix or a front-matter section of +the Document that deals exclusively with the relationship of the +publishers or authors of the Document to the Document's overall +subject (or to related matters) and contains nothing that could fall +directly within that overall subject. (Thus, if the Document is in +part a textbook of mathematics, a Secondary Section may not explain +any mathematics.) The relationship could be a matter of historical +connection with the subject or with related matters, or of legal, +commercial, philosophical, ethical or political position regarding +them. + +The ``Invariant Sections'' are certain Secondary Sections whose titles +are designated, as being those of Invariant Sections, in the notice +that says that the Document is released under this License. If a +section does not fit the above definition of Secondary then it is not +allowed to be designated as Invariant. The Document may contain zero +Invariant Sections. If the Document does not identify any Invariant +Sections then there are none. + +The ``Cover Texts'' are certain short passages of text that are listed, +as Front-Cover Texts or Back-Cover Texts, in the notice that says that +the Document is released under this License. A Front-Cover Text may +be at most 5 words, and a Back-Cover Text may be at most 25 words. + +A ``Transparent'' copy of the Document means a machine-readable copy, +represented in a format whose specification is available to the +general public, that is suitable for revising the document +straightforwardly with generic text editors or (for images composed of +pixels) generic paint programs or (for drawings) some widely available +drawing editor, and that is suitable for input to text formatters or +for automatic translation to a variety of formats suitable for input +to text formatters. A copy made in an otherwise Transparent file +format whose markup, or absence of markup, has been arranged to thwart +or discourage subsequent modification by readers is not Transparent. +An image format is not Transparent if used for any substantial amount +of text. A copy that is not ``Transparent'' is called ``Opaque''. + +Examples of suitable formats for Transparent copies include plain +ASCII without markup, Texinfo input format, \LaTeX\ input format, SGML +or XML using a publicly available DTD, and standard-conforming simple +HTML, PostScript or PDF designed for human modification. Examples of +transparent image formats include PNG, XCF and JPG. Opaque formats +include proprietary formats that can be read and edited only by +proprietary word processors, SGML or XML for which the DTD and/or +processing tools are not generally available, and the +machine-generated HTML, PostScript or PDF produced by some word +processors for output purposes only. + +The ``Title Page'' means, for a printed book, the title page itself, +plus such following pages as are needed to hold, legibly, the material +this License requires to appear in the title page. For works in +formats which do not have any title page as such, ``Title Page'' means +the text near the most prominent appearance of the work's title, +preceding the beginning of the body of the text. + +A section ``Entitled XYZ'' means a named subunit of the Document whose +title either is precisely XYZ or contains XYZ in parentheses following +text that translates XYZ in another language. (Here XYZ stands for a +specific section name mentioned below, such as ``Acknowledgements'', +``Dedications'', ``Endorsements'', or ``History''.) To ``Preserve the +Title'' of such a section when you modify the Document means that it +remains a section ``Entitled XYZ'' according to this definition. + +The Document may include Warranty Disclaimers next to the notice which +states that this License applies to the Document. These Warranty +Disclaimers are considered to be included by reference in this +License, but only as regards disclaiming warranties: any other +implication that these Warranty Disclaimers may have is void and has +no effect on the meaning of this License. + +\section{Verbatim Copying} +\label{sec:License-GFDL-2} + +You may copy and distribute the Document in any medium, either +commercially or noncommercially, provided that this License, the +copyright notices, and the license notice saying this License applies +to the Document are reproduced in all copies, and that you add no +other conditions whatsoever to those of this License. You may not use +technical measures to obstruct or control the reading or further +copying of the copies you make or distribute. However, you may accept +compensation in exchange for copies. If you distribute a large enough +number of copies you must also follow the conditions in section +\ref{sec:License-GFDL-3}. + +You may also lend copies, under the same conditions stated above, and +you may publicly display copies. + +\section{Copying In Quantity} +\label{sec:License-GFDL-3} + +If you publish printed copies (or copies in media that commonly have +printed covers) of the Document, numbering more than 100, and the +Document's license notice requires Cover Texts, you must enclose the +copies in covers that carry, clearly and legibly, all these Cover +Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on +the back cover. Both covers must also clearly and legibly identify +you as the publisher of these copies. The front cover must present +the full title with all words of the title equally prominent and +visible. You may add other material on the covers in addition. +Copying with changes limited to the covers, as long as they preserve +the title of the Document and satisfy these conditions, can be treated +as verbatim copying in other respects. + +If the required texts for either cover are too voluminous to fit +legibly, you should put the first ones listed (as many as fit +reasonably) on the actual cover, and continue the rest onto adjacent +pages. + +If you publish or distribute Opaque copies of the Document numbering +more than 100, you must either include a machine-readable Transparent +copy along with each Opaque copy, or state in or with each Opaque copy +a computer-network location from which the general network-using +public has access to download using public-standard network protocols +a complete Transparent copy of the Document, free of added material. +If you use the latter option, you must take reasonably prudent steps, +when you begin distribution of Opaque copies in quantity, to ensure +that this Transparent copy will remain thus accessible at the stated +location until at least one year after the last time you distribute an +Opaque copy (directly or through your agents or retailers) of that +edition to the public. + +It is requested, but not required, that you contact the authors of the +Document well before redistributing any large number of copies, to +give them a chance to provide you with an updated version of the +Document. + +\section{Modifications} +\label{sec:License-GFDL-4} + +You may copy and distribute a Modified Version of the Document under +the conditions of sections \ref{sec:License-GFDL-2} and +\ref{sec:License-GFDL-3} above, provided that you release the Modified +Version under precisely this License, with the Modified Version +filling the role of the Document, thus licensing distribution and +modification of the Modified Version to whoever possesses a copy of +it. In addition, you must do these things in the Modified Version: + +\begin{itemize} + +\item [A.] Use in the Title Page (and on the covers, if any) a title +distinct from that of the Document, and from those of previous +versions (which should, if there were any, be listed in the History +section of the Document). You may use the same title as a previous +version if the original publisher of that version gives permission. + +\item [B.] List on the Title Page, as authors, one or more persons or +entities responsible for authorship of the modifications in the +Modified Version, together with at least five of the principal authors +of the Document (all of its principal authors, if it has fewer than +five), unless they release you from this requirement. + +\item [C.] State on the Title page the name of the publisher of the +Modified Version, as the publisher. + +\item [D.] Preserve all the copyright notices of the Document. + +\item [E.] Add an appropriate copyright notice for your modifications +adjacent to the other copyright notices. + +\item [F.] Include, immediately after the copyright notices, a license +notice giving the public permission to use the Modified Version under +the terms of this License, in the form shown in the Addendum below. + +\item [G.] Preserve in that license notice the full lists of Invariant +Sections and required Cover Texts given in the Document's license +notice. + +\item [H.] Include an unaltered copy of this License. + +\item [I.] Preserve the section Entitled ``History'', Preserve its +Title, and add to it an item stating at least the title, year, new +authors, and publisher of the Modified Version as given on the Title +Page. If there is no section Entitled ``History'' in the Document, +create one stating the title, year, authors, and publisher of the +Document as given on its Title Page, then add an item describing the +Modified Version as stated in the previous sentence. + +\item [J.] Preserve the network location, if any, given in the +Document for public access to a Transparent copy of the Document, and +likewise the network locations given in the Document for previous +versions it was based on. These may be placed in the ``History'' +section. You may omit a network location for a work that was +published at least four years before the Document itself, or if the +original publisher of the version it refers to gives permission. + +\item [K.] For any section Entitled ``Acknowledgements'' or +``Dedications'', Preserve the Title of the section, and preserve in +the section all the substance and tone of each of the contributor +acknowledgements and/or dedications given therein. + +\item [L.] Preserve all the Invariant Sections of the Document, +unaltered in their text and in their titles. Section numbers or the +equivalent are not considered part of the section titles. + +\item [M.] Delete any section Entitled ``Endorsements''. Such a +section may not be included in the Modified Version. + +\item [N.] Do not retitle any existing section to be Entitled +``Endorsements'' or to conflict in title with any Invariant Section. + +\item [O.] Preserve any Warranty Disclaimers. +\end{itemize} + +If the Modified Version includes new front-matter sections or +appendices that qualify as Secondary Sections and contain no material +copied from the Document, you may at your option designate some or all +of these sections as invariant. To do this, add their titles to the +list of Invariant Sections in the Modified Version's license notice. +These titles must be distinct from any other section titles. + +You may add a section Entitled ``Endorsements'', provided it contains +nothing but endorsements of your Modified Version by various +parties--for example, statements of peer review or that the text has +been approved by an organization as the authoritative definition of a +standard. + +You may add a passage of up to five words as a Front-Cover Text, and a +passage of up to 25 words as a Back-Cover Text, to the end of the list +of Cover Texts in the Modified Version. Only one passage of +Front-Cover Text and one of Back-Cover Text may be added by (or +through arrangements made by) any one entity. If the Document already +includes a cover text for the same cover, previously added by you or +by arrangement made by the same entity you are acting on behalf of, +you may not add another; but you may replace the old one, on explicit +permission from the previous publisher that added the old one. + +The author(s) and publisher(s) of the Document do not by this License +give permission to use their names for publicity for or to assert or +imply endorsement of any Modified Version. + +\section{Combining Documents} +\label{sec:License-GFDL-5} + +You may combine the Document with other documents released under this +License, under the terms defined in section \ref{sec:License-GFDL-4} +above for modified versions, provided that you include in the +combination all of the Invariant Sections of all of the original +documents, unmodified, and list them all as Invariant Sections of your +combined work in its license notice, and that you preserve all their +Warranty Disclaimers. + +The combined work need only contain one copy of this License, and +multiple identical Invariant Sections may be replaced with a single +copy. If there are multiple Invariant Sections with the same name but +different contents, make the title of each such section unique by +adding at the end of it, in parentheses, the name of the original +author or publisher of that section if known, or else a unique number. +Make the same adjustment to the section titles in the list of +Invariant Sections in the license notice of the combined work. + +In the combination, you must combine any sections Entitled ``History'' +in the various original documents, forming one section Entitled +``History''; likewise combine any sections Entitled +``Acknowledgements'', +and any sections Entitled ``Dedications''. You must delete all sections +Entitled ``Endorsements''. + +\section{Collections Of Documents} +\label{sec:License-GFDL-6} + +You may make a collection consisting of the Document and other +documents released under this License, and replace the individual +copies of this License in the various documents with a single copy +that is included in the collection, provided that you follow the rules +of this License for verbatim copying of each of the documents in all +other respects. + +You may extract a single document from such a collection, and +distribute it individually under this License, provided you insert a +copy of this License into the extracted document, and follow this +License in all other respects regarding verbatim copying of that +document. + +\section{Aggregation With Independent Works} +\label{sec:License-GFDL-7} + +A compilation of the Document or its derivatives with other separate +and independent documents or works, in or on a volume of a storage or +distribution medium, is called an ``aggregate'' if the copyright +resulting from the compilation is not used to limit the legal rights +of the compilation's users beyond what the individual works permit. +When the Document is included in an aggregate, this License does not +apply to the other works in the aggregate which are not themselves +derivative works of the Document. + +If the Cover Text requirement of section \ref{sec:License-GFDL-3} is +applicable to these copies of the Document, then if the Document is +less than one half of the entire aggregate, the Document's Cover Texts +may be placed on covers that bracket the Document within the +aggregate, or the electronic equivalent of covers if the Document is +in electronic form. Otherwise they must appear on printed covers that +bracket the whole aggregate. + +\section{Translation} +\label{sec:License-GFDL-8} + +Translation is considered a kind of modification, so you may +distribute translations of the Document under the terms of section +\ref{sec:License-GFDL-4}. Replacing Invariant Sections with +translations requires special permission from their copyright holders, +but you may include translations of some or all Invariant Sections in +addition to the original versions of these Invariant Sections. You +may include a translation of this License, and all the license notices +in the Document, and any Warranty Disclaimers, provided that you also +include the original English version of this License and the original +versions of those notices and disclaimers. In case of a disagreement +between the translation and the original version of this License or a +notice or disclaimer, the original version will prevail. + +If a section in the Document is Entitled ``Acknowledgements'', +``Dedications'', or ``History'', the requirement (section +\ref{sec:License-GFDL-4}) to Preserve its Title (section +\ref{sec:License-GFDL-1}) will typically require changing the actual +title. + +\section{Termination} +\label{sec:License-GFDL-9} + +You may not copy, modify, sublicense, or distribute the Document +except as expressly provided for under this License. Any other +attempt to copy, modify, sublicense or distribute the Document is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + +\section{Future Revisions Of This License} +\label{sec:License-GFDL-10} + +The Free Software Foundation may publish new, revised versions of the +GNU Free Documentation License from time to time. Such new versions +will be similar in spirit to the present version, but may differ in +detail to address new problems or concerns. See +\url{http://www.gnu.org/copyleft/}. + +Each version of the License is given a distinguishing version number. +If the Document specifies that a particular numbered version of this +License ``or any later version'' applies to it, you have the option of +following the terms and conditions either of that specified version or +of any later version that has been published (not as a draft) by the +Free Software Foundation. If the Document does not specify a version +number of this License, you may choose any version ever published (not +as a draft) by the Free Software Foundation. + +\section{How to use this License for your documents} +\label{sec:License-GFDL-11} + +To use this License in a document you have written, include a copy of +the License in the document and put the following copyright and +license notices just after the title page: + +\begin{verbatim} + Copyright (C) YEAR YOUR NAME. + + Permission is granted to copy, distribute and/or modify this + document under the terms of the GNU Free Documentation License, + Version 1.2 or any later version published by the Free Software + Foundation; with no Invariant Sections, no Front-Cover Texts, + and no Back-Cover Texts. A copy of the license is included in + the section entitled ``GNU Free Documentation License''. +\end{verbatim} + +If you have Invariant Sections, Front-Cover Texts and Back-Cover +Texts, replace the ``with...Texts''. line with this: + +\begin{verbatim} + with the Invariant Sections being LIST THEIR TITLES, with the + Front-Cover Texts being LIST, and with the Back-Cover Texts + being LIST. +\end{verbatim} + +If you have Invariant Sections without Cover Texts, or some other +combination of the three, merge those two alternatives to suit the +situation. + +If your document contains nontrivial examples of program code, we +recommend releasing these examples in parallel under your choice of +free software license, such as the GNU General Public License, to +permit their use in free software. + diff --git a/Manuals/Repository/filesystem-latex/Translations/iso639.tex b/Manuals/Repository/filesystem-latex/Translations/iso639.tex new file mode 100644 index 0000000..307e14f --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Translations/iso639.tex @@ -0,0 +1,564 @@ +\chapter{ISO 639 Language Codes} +\label{cha:Appendix:ISO639} + +The ISO 639 standard defines two character codes for many languages. +All abbreviations for languages used in the Translation Project should +come from this standard. + +\begin{description} +\item[aa] +Afar. + +\item[ab] +Abkhazian. + +\item[ae] +Avestan. + +\item[af] +Afrikaans. + +\item[ak] +Akan. + +\item[am] +Amharic. + +\item[an] +Aragonese. + +\item[ar] +Arabic. + +\item[as] +Assamese. + +\item[av] +Avaric. + +\item[ay] +Aymara. + +\item[az] +Azerbaijani. + +\item[ba] +Bashkir. + +\item[be] +Byelorussian; Belarusian. + +\item[bg] +Bulgarian. + +\item[bh] +Bihari. + +\item[bi] +Bislama. + +\item[bm] +Bambara. + +\item[bn] +Bengali; Bangla. + +\item[bo] +Tibetan. + +\item[br] +Breton. + +\item[bs] +Bosnian. + +\item[ca] +Catalan. + +\item[ce] +Chechen. + +\item[ch] +Chamorro. + +\item[co] +Corsican. + +\item[cr] +Cree. + +\item[cs] +Czech. + +\item[cu] +Church Slavic. + +\item[cv] +Chuvash. + +\item[cy] +Welsh. + +\item[da] +Danish. + +\item[de] +German. + +\item[dv] +Divehi. + +\item[dz] +Dzongkha; Bhutani. + +\item[ee] +E'we'. + +\item[el] +Greek. + +\item[en] +English. + +\item[eo] +Esperanto. + +\item[es] +Spanish. + +\item[et] +Estonian. + +\item[eu] +Basque. + +\item[fa] +Persian. + +\item[ff] +Fulah. + +\item[fi] +Finnish. + +\item[fj] +Fijian; Fiji. + +\item[fo] +Faroese. + +\item[fr] +French. + +\item[fy] +Frisian. + +\item[ga] +Irish. + +\item[gd] +Scots; Gaelic. + +\item[gl] +Gallegan; Galician. + +\item[gn] +Guarani. + +\item[gu] +Gujarati. + +\item[gv] +Manx. + +\item[ha] +Hausa (?). + +\item[he] +Hebrew (formerly iw). + +\item[hi] +Hindi. + +\item[ho] +Hiri Motu. + +\item[hr] +Croatian. + +\item[ht] +Haitian; Haitian Creole. + +\item[hu] +Hungarian. + +\item[hy] +Armenian. + +\item[hz] +Herero. + +\item[ia] +Interlingua. + +\item[id] +Indonesian (formerly in). + +\item[ie] +Interlingue. + +\item[ig] +Igbo. + +\item[ii] +Sichuan Yi. + +\item[ik] +Inupiak. + +\item[io] +Ido. + +\item[is] +Icelandic. + +\item[it] +Italian. + +\item[iu] +Inuktitut. + +\item[ja] +Japanese. + +\item[jv] +Javanese. + +\item[ka] +Georgian. + +\item[kg] +Kongo. + +\item[ki] +Kikuyu. + +\item[kj] +Kuanyama. + +\item[kk] +Kazakh. + +\item[kl] +Kalaallisut; Greenlandic. + +\item[km] +Khmer; Cambodian. + +\item[kn] +Kannada. + +\item[ko] +Korean. + +\item[kr] +Kanuri. + +\item[ks] +Kashmiri. + +\item[ku] +Kurdish. + +\item[kv] +Komi. + +\item[kw] +Cornish. + +\item[ky] +Kirghiz. + +\item[la] +Latin. + +\item[lb] +Letzeburgesch. + +\item[lg] +Ganda. + +\item[li] +Limburgish; Limburger; Limburgan. + +\item[ln] +Lingala. + +\item[lo] +Lao; Laotian. + +\item[lt] +Lithuanian. + +\item[lu] +Luba-Katanga. + +\item[lv] +Latvian; Lettish. + +\item[mg] +Malagasy. + +\item[mh] +Marshall. + +\item[mi] +Maori. + +\item[mk] +Macedonian. + +\item[ml] +Malayalam. + +\item[mn] +Mongolian. + +\item[mo] +Moldavian. + +\item[mr] +Marathi. + +\item[ms] +Malay. + +\item[mt] +Maltese. + +\item[my] +Burmese. + +\item[na] +Nauru. + +\item[nb] +Norwegian Bokmaal. + +\item[nd] +Ndebele, North. + +\item[ne] +Nepali. + +\item[ng] +Ndonga. + +\item[nl] +Dutch. + +\item[nn] +Norwegian Nynorsk. + +\item[no] +Norwegian. + +\item[nr] +Ndebele, South. + +\item[nv] +Navajo. + +\item[ny] +Chichewa; Nyanja. + +\item[oc] +Occitan; Provenc,al. + +\item[oj] +Ojibwa. + +\item[om] +(Afan) Oromo. + +\item[or] +Oriya. + +\item[os] +Ossetian; Ossetic. + +\item[pa] +Panjabi; Punjabi. + +\item[pi] +Pali. + +\item[pl] +Polish. + +\item[ps] +Pashto, Pushto. + +\item[pt] +Portuguese. + +\item[qu] +Quechua. + +\item[rm] +Rhaeto-Romance. + +\item[rn] +Rundi; Kirundi. + +\item[ro] +Romanian. + +\item[ru] +Russian. + +\item[rw] +Kinyarwanda. + +\item[sa] +Sanskrit. + +\item[sc] +Sardinian. + +\item[sd] +Sindhi. + +\item[se] +Northern Sami. + +\item[sg] +Sango; Sangro. + +\item[si] +Sinhalese. + +\item[sk] +Slovak. + +\item[sl] +Slovenian. + +\item[sm] +Samoan. + +\item[sn] +Shona. + +\item[so] +Somali. + +\item[sq] +Albanian. + +\item[sr] +Serbian. + +\item[ss] +Swati; Siswati. + +\item[st] +Sesotho; Sotho, Southern. + +\item[su] +Sundanese. + +\item[sv] +Swedish. + +\item[sw] +Swahili. + +\item[ta] +Tamil. + +\item[te] +Telugu. + +\item[tg] +Tajik. + +\item[th] +Thai. + +\item[ti] +Tigrinya. + +\item[tk] +Turkmen. + +\item[tl] +Tagalog. + +\item[tn] +Tswana; Setswana. + +\item[to] +Tonga (?). + +\item[tr] +Turkish. + +\item[ts] +Tsonga. + +\item[tt] +Tatar. + +\item[tw] +Twi. + +\item[ty] +Tahitian. + +\item[ug] +Uighur. + +\item[uk] +Ukrainian. + +\item[ur] +Urdu. + +\item[uz] +Uzbek. + +\item[ve] +Venda. + +\item[vi] +Vietnamese. + +\item[vo] +Volapu"k; Volapuk. + +\item[wa] +Walloon. + +\item[wo] +Wolof. + +\item[xh] +Xhosa. + +\item[yi] +Yiddish (formerly ji). + +\item[yo] +Yoruba. + +\item[za] +Zhuang. + +\item[zh] +Chinese. + +\item[zu] +Zulu. +\end{description} + diff --git a/Manuals/Repository/filesystem-latex/Workstation/configuration.tex b/Manuals/Repository/filesystem-latex/Workstation/configuration.tex new file mode 100644 index 0000000..ecfc67d --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Workstation/configuration.tex @@ -0,0 +1,180 @@ +% Part : Preparing Your Workstation +% Chapter: Configuration +% ------------------------------------------------------------ +% $Id: configuration.tex 6191 2010-08-02 02:36:14Z al $ +% ------------------------------------------------------------ + +This chapter describes configurations you need to set up before using +CentOS Artwork Repository. + +\section{Firewall} + +The CentOS Artwork Repository lives on the following URL: + +\begin{quote} +https://projects.centos.org/svn/artwork/ +\end{quote} + +To reach this location you need to have Internet access and be sure no +rule in your firewall is denying this site. Note that the URL uses the +SSL protocol (port 443). + +\section{Subversion Behind Squid} + +Sometimes it is convenient to proxy Subversion client's requests +through a proxy-cache server like Squid. In cases like this, the Squid +proxy server is in the middle between you and CentOS Artwork +Repository. If you want to proxy Subversion client's requests through +Squid proxy-cache server, you need to configure your Subversion client +and your Squid proxy server to do so. + +\subsection{Subversion Client Configuration} + +Subversion client needs to be configured to send requests to your +Squid proxy-cache server. This configuration takes place in the file +\texttt{$\sim$/.subversion/servers}. + +\subsection{Squid Server Configuration} + +Squid proxy-cache server needs to be configured to accept the +extension methods \texttt{REPORT MERGE MKACTIVITY CHECKOUT MKCOL}. +This configuration takes place in the file +\texttt{/etc/squid/squid.conf}, specifically in the configuration tag +illustrated in \autoref{fig:Workstation:Configuration:Squid}. + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +# TAG: extension_methods +# Squid only knows about standardized HTTP request methods. +# You can add up to 20 additional "extension" methods here. +# +#Default: +# none +extension_methods REPORT MERGE MKACTIVITY CHECKOUT MKCOL +\end{verbatim} +\hrulefill +\caption{Squid configuration to proxy Subversion client's requests.% + \label{fig:Workstation:Configuration:Squid}} +\end{figure} + +\section{Working Copy} + +A Subversion working copy is an ordinary directory tree on your local +system, containing a collection of files (i.e. Translations, Designs, +Manuals, and Scripts). You can edit these files however you wish. Your +working copy is your own private work area: Subversion will never +incorporate other people's changes, nor make your own changes +available to others, until you explicitly tell it to do so. You can +even have multiple working copies of the same project.\footnote{Even +this is basically correct, doing so when using CentOS Artowrk +Repository can bring some confusion when executing scripts. Presently, +only one absolute path can be defined as absolute path for scripts' +execution. You can have as many working copies of CentOS Artwork +Repository as you want but scripts will be executed from just one +working copy absolute path. That is, the one stored under +\texttt{/home/centos/artwork/}}. + +Once you've made some changes to your working copy files and verified +that they work properly, Subversion provides you with commands to +``publish'' your changes to the other people working with you on your +project (by writing to the repository). If other people publish their +own changes, Subversion provides you with commands to merge those +changes into your working directory (by reading from the repository). + +\begin{figure}[!hbp] +\hrulefill +\begin{verbatim} +svn co https://projects.centos.org/svn/artwork /home/centos/ +\end{verbatim} +\hrulefill +\caption{Subversion command used to download the working copy.% + \label{fig:Workstation:WC:Download}} +\end{figure} + +The subversion command illustrated in +\autoref{fig:Workstation:WC:Download} brings a CentOS Artwork +Repository working copy down to your workstation, specifically to your +home directory (\texttt{/home/centos/artwork/}). This process may take +some time. Once the working copy is available in your workstation, +you are ready to start exploring and improving available works. + +Note that you need to have a username called \texttt{centos} in your +system. If you don't have it, you can create it using the comand +\texttt{useradd} as superuser (\texttt{root}). + +\subsection{Standardizing Absolute Path} + +When using Inkscape to import raster images inside SVG files the +absolute image path is required. If everyone stores the working copy +on a different absolute path imported images will not be loaded in +those location different from those they were conceived. There is no +way to find the right absolute image path but defining a convenction +about it. + +On a path string (e.g., /home/centos/artwork/trunk/) the username +(`centos') is the variable component, so it is the component we need +to standardize--in the sake of keeping the working copy inside user's +/home/ structure. Thus, analysing which username to use, the CentOS +Project is what join us all together, so the `centos' word in +lower-case seems to be a nice choise for us to use as common username. + +\section{User Identification} + +At this point you probably have made some changes inside your working +copy and wish to publish them. To publish your changes on CentOS +Artwork Repository you need to have a registered account with commit +privilege in CentOS Artwork Repository. + +If you are new in CentOS Artwork Repository it is possible that you +can't commit your changes. That is because new registered accounts +haven't commit privilege set by default. In order for your registered +account to have commit privilege inside CentOS Artwork Repository you +need to request it. See section +\ref{sec:Configuration:User:Privileges}. + +\subsection{User Account Registration} +\label{sec:Configuration:Account} + +To register a user account inside CentOS Artwork Repository, you need +to go to the following URL: + +\begin{quote} +\url{https://projects.centos.org/trac/artwork/} +\end{quote} + +\subsection{User Account Privileges} +\label{sec:Configuration:User:Privileges} + +To have commit privileges in CentOS Artwork Repository it is needed +that you show your interest first, preferably with something useful +like a new or improved design, translation, manual, or script. As +convenction, people working on CentOS Artwork Repository share ideas +in the mailing list +\href{mailto:centos-devel@centos.org}{centos-devel@centos.org}. If you +are interested in joining us go there and express yourself. + +\section{Repository Tagged Revisions} + +The CentOS Artwork Repository is also available as tagged revisions. +Tagged revisions are checkpoints on the CentOS Artwork Repository +developing lifetime. They are inmutable copies of the CentOS Artwork +Repository state through time. Tagged revisions contain the files +used to produce images but not images themselves. Inside tagged +revisions you can find scripts (\texttt{.sh}), design templates +(\texttt{.svg}), translation files (\texttt{\.sed}), gimp projects +(\texttt{.xcf}), and documetation files (\texttt{.tex}). + +CentOS Artowrk Repository tagged revisions are available for +downloading in the following location: + +\begin{description} +\item[URL:] https://projects.centos.org/svn/artwork/tags +\end{description} + +and alternatively, you can find references in the CentOS Project's +wiki, specifically in the ArtWork page: + +\begin{description} +\item[URL:] http://wiki.centos.org/ArtWork +\end{description} diff --git a/Manuals/Repository/filesystem-latex/Workstation/installation.tex b/Manuals/Repository/filesystem-latex/Workstation/installation.tex new file mode 100644 index 0000000..4a8e3ea --- /dev/null +++ b/Manuals/Repository/filesystem-latex/Workstation/installation.tex @@ -0,0 +1,139 @@ +% Part : Preparing Your Workstation +% Chapter: Installation +% ------------------------------------------------------------ +% $Id: installation.tex 6191 2010-08-02 02:36:14Z al $ +% ------------------------------------------------------------ + +This chapter describes tools you need to have installed in your CentOS +workstation before using CentOS Artwork Repository. + +\section{Subversion} + +Subversion is a version control system, which allows you to keep old +versions of files and directories (usually source code), keep a log of +who, when, and why changes occurred, etc., like CVS, RCS or +SCCS.\footnote{More documentation about Subversion and its tools, +including detailed usage explanations of the svn, svnadmin, svnserve +and svnlook programs, historical background, philosophical approaches +and reasonings, etc., can be found at +\url{http://svnbook.red-bean.com/.}} + +To install Subversion client tools in your workstation you can use the +following command: + +\begin{quote} +yum install subversion +\end{quote} + +\section{Inkscape} + +Inkscape is a GUI editor for Scalable Vector Graphics (SVG) format +drawing files, with capabilities similar to Adobe Illustrator, +CorelDraw, Visio, etc. Inkscape features include versatile shapes, +bezier paths, freehand drawing, multiline text, text on path, alpha +blending, arbitrary affine transforms, gradient and pattern fills, +node editing, SVG-to-PNG export, grouping, layers, live clones, and +more. + +Note that Inkscape is not inside CentOS Distribution, so you need to +configure a third party repository like RPMForge or EPEL to install +Inkscape. Installation of a third party repositories inside CentOS +Distribution is described in the following URL: + +\begin{quote} +\url{http://wiki.centos.org/AdditionalResources/Repositories} +\end{quote} + +Once you have configured the third party repository you can install +Inkscape using the following command: + +\begin{quote} +yum install inkscape +\end{quote} + +\section{ImageMagick} + +ImageMagick is a free software suite for the creation, modification +and display of bitmap images. It can read, convert and write images +in a large variety of formats. Images can be cropped, colors can be +changed, various effects can be applied, images can be rotated and +combined, and text, lines, polygons, ellipses and Bézier curves can +be added to images and stretched and rotated. + +To install ImageMagick in your workstation you can run the following +command: + +\begin{quote} +yum install ImageMagick +\end{quote} + +\section{Netpbm} + +Netpbm is a toolkit for manipulation of graphic images, including +conversion of images between a variety of different formats. There +are over 300 separate tools in the package including converters for +about 100 graphics formats. + +To install Netpbm in your workstation you can run the following +command: + +\begin{quote} +yum install netpbm\{-progs\} +\end{quote} + +\section{Syslinux} + +Syslinux is a suite of bootloaders, currently supporting DOS FAT +filesystems, Linux ext2/ext3 filesystems (EXTLINUX), PXE network boots +(PXELINUX), or ISO 9660 CD-ROMs (ISOLINUX). It also includes a tool, +MEMDISK, which loads legacy operating systems from these media. The +package \texttt{syslinux} provides the programs \texttt{ppmtolss16} +and \texttt{lss16toppm} which are used to produce Anaconda Prompt +images. The \texttt{ppmtolss16} Perl program also includes the file +format specification. + +To install Syslinux in your workstation you can run the following +command: + +\begin{quote} +yum install syslinux +\end{quote} + +\section{GNU Image Manipulation Program} + +GNU Image Manipulation Program (GIMP) is used to manipulate images +inside CentOS Artwork Repository. + +To install GIMP in your workstation you can run the following command: + +\begin{quote} +yum install gimp +\end{quote} + +\section{GNU Core Utilities} + +The GNU core utilities are a set of tools commonly used in shell +scripts. + +To install the GNU core utilities in your workstation you can run the +following command: + +\begin{quote} +yum install core-utils +\end{quote} + +\section{\LaTeX} + +\LaTeX\ is a document preparation system implemented as a macro +package for Donald E. Knuth's \TeX\ typesetting program. The \LaTeX\ +command typesets a file of text using the \TeX\ program and the LaTeX +Macro package for \TeX. To be more specific, it processes an input +file containing the text of a document with interspersed commands that +describe how the text should be formatted. + +To install \LaTeX\ in your workstation you can run the following +command: + +\begin{quote} +yum install tetex-\{latex,fonts,doc,xdiv,dvips\} +\end{quote} diff --git a/Manuals/Repository/filesystem-latex/convenctions.tex b/Manuals/Repository/filesystem-latex/convenctions.tex new file mode 100644 index 0000000..ea33699 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/convenctions.tex @@ -0,0 +1,5 @@ +% Part : Frontmatter +% Chapter: Convenctions +% ------------------------------------------------------------ +% $Id: convenctions.tex 6260 2010-08-15 02:36:26Z al $ +% ------------------------------------------------------------ diff --git a/Manuals/Repository/filesystem-latex/repository.tex b/Manuals/Repository/filesystem-latex/repository.tex new file mode 100644 index 0000000..89ed1a9 --- /dev/null +++ b/Manuals/Repository/filesystem-latex/repository.tex @@ -0,0 +1,307 @@ +% ------------------------------------------------------------ +% $Id: repository.tex 6260 2010-08-15 02:36:26Z al $ +% ------------------------------------------------------------ +\documentclass[12pt]{book} +\usepackage{fancyhdr} +\renewcommand{\chaptermark}[1]{\markboth{#1}{}} +\fancyhf{} % delete current setting for header and footer +\fancyhead[RO,LE]{\bfseries\thepage} +\fancyhead[LO]{\bfseries\leftmark} +\fancyhead[RE]{\bfseries\leftmark} +\renewcommand{\headrulewidth}{0.5pt} +\renewcommand{\footrulewidth}{0pt} +\addtolength{\headheight}{0.5pt} % make space for the rule +\fancypagestyle{plain}{% + \fancyhead{} % get rid of headers on plain pages + \renewcommand{\headrulewidth}{0pt} % and the line + } +\usepackage[pdftex]{graphicx} +\usepackage{hyperref} +\hypersetup{pdfauthor={Alain Reguera Delgado},% + pdftitle={The CentOS Project - Artwork Repository},% + pdfsubject={CentOS Corporate Visual Identity}% + } + +\title{The CentOS Project - Artwork Repository} +\author{Alain Reguera Delgado} + +% Define words you don't want to split. +\hyphenation{CentOS} + +\begin{document} + +\pagestyle{empty} + +% Half title: The first page is a recto half title page with no folio. +% The page is very simple and displays just the main title of the book +% — no subtitle, author, or other information. One purported purpose +% of this page is to protect the main title page. +\begin{titlepage} +\begin{flushright} +\noindent\includegraphics[width=1\textwidth]{% + /home/centos/artwork/trunk/Identity/Models/Img/en/Promo/Stationery/motif-propagation.pdf}\\ +\vspace*{150pt} +\Huge\textbf{The CentOS Project} +\rule{\textwidth}{5pt} +\large +\textbf{Artwork Repository}\\ +\vspace*{150pt} +\normalsize +\today +\end{flushright} +\end{titlepage} + +% Page title: The title page is recto and contains the full title of +% the work, the names of the author(s) or editor(s), and often at the +% bottom of the page the name of the publisher, together with the +% publisher’s logo if it has one. +\begin{titlepage} +\begin{flushright} +\noindent\includegraphics[width=1\textwidth]{% + /home/centos/artwork/trunk/Identity/Models/Img/en/Promo/Stationery/motif-propagation.pdf}\\ +\vspace*{150pt} +\Huge\textbf{The CentOS Project} +\rule{\textwidth}{5pt} +\large +\textbf{Artwork Repository}\\ +\vspace*{150pt} +\normalsize +Alain Reguera Delgado $<$alain.reguera@gmail.com$>$\\ +\end{flushright} +\end{titlepage} + +% Copyright: The copyright page is verso and contains the copyright +% notice, the publishing/printing history, the country where printed, +% ISBN and/or CIP information. The page is usually typeset in a +% smaller font than the normal text. + +\noindent Copyright \copyright\ 2009, 2010 Alain Reguera Delgado. All\ +rights reserved.\\ +\\ +\noindent Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, +Version 1.2 or any later version published by the Free Software +Foundation; with no Invariant Sections, no Front-Cover Texts, and no +Back-Cover Texts. A copy of the license is included in the section +entitled ``\hyperlink{cha:Licenses:GFDL}{GNU Free Documentation +License}''. + +\frontmatter +\pagestyle{fancy} + +% Listings: +\tableofcontents +\listoftables +\listoffigures + +% Reset fancyhdr marks. +\renewcommand{\chaptermark}[1]{\markboth{#1}{}} + +% Dedication: +%\chapter*{Dedication} + +% Forewords: There may be a foreword after the listings, with no blank +% separator. A foreword is usually written by someone other than the +% author, preferably an eminent person, and is signed by the writer. +% The writer’s signature is often typeset in small caps after the end +% of the piece. +%\chapter{Forewords} + +% Preface: A preface is normally written by the author, in which he +% includes reasons why he wrote the work in the first place, and +% perhaps to provide some more personal comments than would be +% justified in the body. A preface starts on the page immediately +% following a foreword, or the lists. +%\chapter{Preface} + +\mainmatter + +% Reset fancyhdr marks. +\renewcommand{\chaptermark}[1]{\markboth{% + \chaptername\ \thechapter.\ #1}{}} + +\part{Concepts} + +\chapter{The CentOS Project} + \hypertarget{cha:Concepts:CentOS}{} + \label{cha:Concepts:CentOS} + \input{Concepts/CentOS/introduction.tex} + \input{Concepts/CentOS/incorporation.tex} + \input{Concepts/CentOS/philosophy.tex} + \input{Concepts/CentOS/mission.tex} + \input{Concepts/CentOS/distribution.tex} + \input{Concepts/CentOS/community.tex} + \input{Concepts/CentOS/release.tex} + +\chapter{Frameworks} + \hypertarget{cha:Concepts:frameworks}{} + \label{cha:Concepts:Frameworks} + \input{Concepts/Frameworks/introduction.tex} + \input{Concepts/Frameworks/templates.tex} + \input{Concepts/Frameworks/files.tex} + \input{Concepts/Frameworks/rendering.tex} + +\chapter{Corporate Identity} + \hypertarget{cha:Concepts:Identity}{} + \label{cha:Concepts:Identity} + \input{Concepts/Identity/introduction.tex} + \input{Concepts/Identity/structure.tex} + \input{Concepts/Identity/brands.tex} + \input{Concepts/Identity/release.tex} + \input{Concepts/Identity/themes.tex} + \input{Concepts/Identity/icons.tex} + \input{Concepts/Identity/models.tex} + \input{Concepts/Identity/widgets.tex} + +\chapter{Translations} + \hypertarget{cha:Concepts:Translations}{} + \label{cha:Concepts:Translations} + \input{Concepts/translations.tex} + +\chapter{Manuals} + \hypertarget{cha:Concepts:Manuals}{} + \label{cha:Concepts:Manuals} + \input{Concepts/manuals.tex} + +\chapter{Scripts} + \hypertarget{cha:Concepts:Scripts}{} + \label{cha:Concepts:Scripts} + \input{Concepts/scripts.tex} + +\chapter{Rebranding} + \hypertarget{cha:Concepts:rebranding}{} + \label{cha:Concepts:rebranding} + \input{Concepts/rebranding.tex} + +\part{Preparing Your Workstation} + +\chapter{Installation} + \hypertarget{cha:Workstation:Installation}{} + \label{cha:Workstation:Installation} + \input{Workstation/installation.tex} + +\chapter{Configuration} + \hypertarget{cha:Workstation:Configuration}{} + \label{cha:Workstation:Configuration} + \input{Workstation/configuration.tex} + +\part{Distribution} + \hypertarget{par:Distribution}{} + \label{par:Distribution} + +\chapter{Anaconda Prompt} + \hypertarget{cha:Distribution:Anaconda:Prompt}{} + \label{cha:Distribution:Anaconda:Prompt} + \input{Distribution/Anaconda/Prompt/chapter.tex} + +\chapter{Anaconda Header} + \hypertarget{cha:Distribution:Anaconda:Header}{} + \label{cha:Distribution:Anaconda:Header} + \input{Distribution/Anaconda/Header/chapter.tex} + +\chapter{Anaconda Splash} + \hypertarget{cha:Distribution:Anaconda:Splash}{} + \label{cha:Distribution:Anaconda:Splash} + \input{Distribution/Anaconda/Splash/chapter.tex} + +\chapter{Anaconda Progress} + \hypertarget{cha:Distribution:Anaconda:Progress}{} + \label{cha:Distribution:Anaconda:Progress} + \input{Distribution/Anaconda/Progress/introduction.tex} + \input{Distribution/Anaconda/Progress/framework.tex} + \input{Distribution/Anaconda/Progress/rebranding.tex} + +\chapter{Firstboot} + \hypertarget{cha:Distribution:Anaconda:Firstboot}{} + \label{cha:Distribution:Anaconda:Firstboot} + \input{Distribution/Anaconda/Firstboot/introduction.tex} + \input{Distribution/Anaconda/Firstboot/framework.tex} + \input{Distribution/Anaconda/Firstboot/rebranding.tex} + +\chapter{GNOME Display Manager (GDM)} + \hypertarget{cha:Distribution:BootUp:GDM}{} + \label{cha:Distribution:BootUp:GDM} + +\chapter{GRand Unified Bootloader (GRUB)} + \hypertarget{cha:Distribution:BootUp:GRUB}{} + \label{cha:Distribution:BootUp:GRUB} + +\chapter{GNOME Splash} + \hypertarget{cha:Distribution:BootUp:GSplash}{} + \label{cha:Distribution:BootUp:GSplash} + +\chapter{KDE Display Manager (KDM)} + \hypertarget{cha:Distribution:BootUp:KDM}{} + \label{cha:Distribution:BootUp:KDM} + +\chapter{KDE Splash} + \hypertarget{cha:Distribution:BootUp:KSplash}{} + \label{cha:Distribution:BootUp:KSplash} + +\chapter{Graphical Boot (RHGB)} + \hypertarget{cha:Distribution:BootUp:RHGB}{} + \label{cha:Distribution:BootUp:RHGB} + +\chapter{Backgrounds} + \hypertarget{cha:Distribution:Backgrounds}{} + \label{cha:Distribution:Backgrounds} + \input{Distribution/Backgrounds/introduction.tex} + \input{Distribution/Backgrounds/framework.tex} + \input{Distribution/Backgrounds/rebranding.tex} + +\chapter{Release Notes} + \hypertarget{cha:Distribution:ReleaseNotes}{} + \label{cha:Distribution:ReleaseNotes} + +\part{Promotion} + +\chapter{Cards} + \hypertarget{cha:Promotion:Cards}{} + \label{cha:Promotion:Cards} + +\chapter{Clothes} + \hypertarget{cha:Promotion:Clothes}{} + \label{cha:Promotion:Clothes} + +\chapter{Flags} + \hypertarget{cha:Promotion:Flags}{} + \label{cha:Promotion:Flags} + +\chapter{Media} + \hypertarget{cha:Promotion:Media}{} + \label{cha:Promotion:Media} + +\chapter{Posters} + \hypertarget{cha:Promotion:Posters}{} + \label{cha:Promotion:Posters} + +\chapter{Releases} + \hypertarget{cha:Promotion:Releases}{} + \label{cha:Promotion:Releases} + +\chapter{Stands} + \hypertarget{cha:Promotion:Stands}{} + \label{cha:Promotion:Stands} + +\chapter{Stationery} + \hypertarget{cha:Promotion:Stationery}{} + \label{cha:Promotion:Stationery} + +\chapter{Sticky} + \hypertarget{cha:Promotion:Sticky}{} + \label{cha:Promotion:Sticky} + +\part{Licenses} +\appendix +\input{Licenses/centos-redistribution.tex} +\input{Licenses/gfdl.tex} + +\backmatter + +% Bibliographies: BibTeX automates much of the job of typesetting +% bibliographies, and makes bibliography entries reusable in many +% different contexts. + +% Indexing table: + +\end{document} diff --git a/Manuals/Repository/filesystem-menu.texi b/Manuals/Repository/filesystem-menu.texi new file mode 100644 index 0000000..da7aeff --- /dev/null +++ b/Manuals/Repository/filesystem-menu.texi @@ -0,0 +1,7 @@ +@menu +* branches:: +* tags:: +* trunk:: +* Index:: +* List of Figures:: +@end menu diff --git a/Manuals/Repository/filesystem-nodes.texi b/Manuals/Repository/filesystem-nodes.texi new file mode 100644 index 0000000..7ede600 --- /dev/null +++ b/Manuals/Repository/filesystem-nodes.texi @@ -0,0 +1,3 @@ +@include branches/chapter.texi +@include tags/chapter.texi +@include trunk/chapter.texi diff --git a/Manuals/Repository/filesystem.info.bz2 b/Manuals/Repository/filesystem.info.bz2 new file mode 100644 index 0000000..d6174e4 Binary files /dev/null and b/Manuals/Repository/filesystem.info.bz2 differ diff --git a/Manuals/Repository/filesystem.pdf b/Manuals/Repository/filesystem.pdf new file mode 100644 index 0000000..d653c09 Binary files /dev/null and b/Manuals/Repository/filesystem.pdf differ diff --git a/Manuals/Repository/filesystem.texi b/Manuals/Repository/filesystem.texi new file mode 100644 index 0000000..a04227e --- /dev/null +++ b/Manuals/Repository/filesystem.texi @@ -0,0 +1,52 @@ +\input texinfo @c -*-texinfo-*- +@c $Id: repository.texi 33 2010-09-13 11:36:41Z al $ +@setfilename filesystem.info +@settitle CentOS Artwork Repository - File System +@afourpaper +@finalout + +@c -- Summary Description and Copyright ----------------------- +@copying +Copyright @copyright{} 2009-2011 Alain Reguera Delgado + +Permission is granted to copy, distribute and/or modify this document +under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no +Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A +copy of the license is included in the section entitled GNU Free +Documentation License. +@end copying + +@c -- Titlepage, Contents, Copyright --------------------------- + +@titlepage +@title CentOS Artwork Repository +@subtitle File System +@author Alain Reguera Delgado +@page +@vskip 0pt plus 1filll +@insertcopying +@end titlepage + +@contents + +@c -- `Top' Node and Master Menu ------------------------------- + +@ifnottex +@node Top +@top CentOS Artwork Repository - File System + +@insertcopying +@end ifnottex + +@include filesystem-menu.texi + +@c -- The Body of the Document -------------------------------- + +@include filesystem-nodes.texi + +@c -- The End of the Document --------------------------------- + +@include filesystem-index.texi + +@bye diff --git a/Manuals/Repository/filesystem.txt b/Manuals/Repository/filesystem.txt new file mode 100644 index 0000000..cc497bc --- /dev/null +++ b/Manuals/Repository/filesystem.txt @@ -0,0 +1,6032 @@ +Table of Contents +***************** + +CentOS Artwork Repository - File System +1 branches +2 tags +3 trunk + 3.1 trunk/Identity + 3.1.1 Goals + 3.1.2 Description + 3.1.3 Usage + 3.1.4 File name convenctions + 3.1.4.1 When text-based files are rendered + 3.1.4.2 When image-based files are rendered + 3.1.5 See also + 3.1.6 References + 3.2 trunk/Identity/Brands + 3.2.1 Goals + 3.2.2 Description + 3.2.3 Usage + 3.2.4 See also + 3.3 trunk/Identity/Fonts + 3.3.1 Goals + 3.3.2 Description + 3.3.3 Usage + 3.3.4 See also + 3.4 trunk/Identity/Icons + 3.4.1 Goals + 3.4.2 Description + 3.4.3 Usage + 3.4.4 See also + 3.5 trunk/Identity/Isolinux + 3.5.1 Goals + 3.5.2 Description + 3.5.3 Usage + 3.5.4 See also + 3.6 trunk/Identity/Models + 3.6.1 Goals + 3.6.2 Description + 3.6.3 Usage + 3.6.4 See also + 3.7 trunk/Identity/Models/Css + 3.7.1 Goals + 3.7.2 Description + 3.7.3 Usage + 3.7.4 See also + 3.8 trunk/Identity/Models/Html + 3.8.1 Goals + 3.8.2 Description + 3.8.3 Usage + 3.8.4 See also + 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.10 trunk/Identity/Models/Tpl + 3.10.1 Goals + 3.10.2 Description + 3.10.3 Usage + 3.10.4 See also + 3.11 trunk/Identity/Models/Tpl/Promo/Web + 3.11.1 Goals + 3.11.2 The CentOS web environment + 3.11.2.1 Design model (without ads) + 3.11.2.2 Design model (with ads) + 3.11.2.3 HTML definitions + 3.11.2.4 Controlling visual style + 3.11.2.5 Producing visual style + 3.11.2.6 Navigation + 3.11.2.7 Development and release cycle + 3.11.2.8 The [webenv-test] repository + 3.11.2.9 The [webenv] repository + 3.11.2.10 Priority configuration + 3.11.3 Usage + 3.11.4 See also + 3.12 trunk/Identity/Models/Xcf + 3.12.1 Goals + 3.12.2 Description + 3.12.3 Usage + 3.12.4 See also + 3.13 trunk/Identity/Release + 3.13.1 Goals + 3.13.2 Description + 3.13.3 Usage + 3.13.4 See also + 3.14 trunk/Identity/Themes + 3.14.1 Goals + 3.14.2 Description + 3.14.3 Usage + 3.14.4 See also + 3.15 trunk/Identity/Themes/Models + 3.15.1 Goals + 3.15.2 Description + 3.15.3 Usage + 3.15.4 See also + 3.16 trunk/Identity/Themes/Models/Alternative + 3.16.1 Goals + 3.16.2 Description + 3.16.3 Usage + 3.16.4 See also + 3.17 trunk/Identity/Themes/Models/Default + 3.17.1 Goals + 3.17.2 Description + 3.17.3 Usage + 3.17.4 See also + 3.18 trunk/Identity/Themes/Models/Default/Distro + 3.18.1 Goals + 3.18.2 Description + 3.18.2.1 One theme for all major releases + 3.18.2.2 One theme for each major release + 3.18.3 Usage + 3.18.4 See also + 3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda + 3.19.1 Goals + 3.19.2 Description + 3.19.3 Usage + 3.19.4 See also + 3.20 trunk/Identity/Themes/Models/Default/Promo + 3.20.1 Goals + 3.20.2 Description + 3.20.3 Usage + 3.20.4 See also + 3.21 trunk/Identity/Themes/Models/Default/Web + 3.21.1 Goals + 3.21.2 Description + 3.21.3 Usage + 3.21.4 See also + 3.22 trunk/Identity/Themes/Motifs + 3.22.1 Goals + 3.22.2 Description + 3.22.3 Usage + 3.22.4 See also + 3.23 trunk/Identity/Themes/Motifs/Flame + 3.23.1 Goals + 3.23.2 Description + 3.23.3 Construction + 3.23.3.1 Step 1: Set image size + 3.23.3.2 Step 2: Add base color and pattern information + 3.23.3.3 Step 3: Add flame motif + 3.23.3.4 Step 4: Add foreground color + 3.23.4 See also + 3.24 trunk/Identity/Themes/Motifs/Modern + 3.24.1 Presentation + 3.24.2 Construction + 3.24.3 Usage + 3.24.4 See also + 3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds + 3.25.1 Goals + 3.25.2 Description + 3.25.3 Usage + 3.25.4 See also + 3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img + 3.26.1 Goals + 3.26.2 Description + 3.26.3 Usage + 3.26.4 See also + 3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl + 3.27.1 Goals + 3.27.2 Description + 3.27.3 Usage + 3.27.4 See also + 3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf + 3.28.1 Goals + 3.28.2 Description + 3.28.3 Usage + 3.28.4 See also + 3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress + 3.29.1 Goals + 3.29.2 Description + 3.29.3 Usage + 3.29.4 See also + 3.30 trunk/Identity/Themes/Motifs/Modern/Palettes + 3.30.1 Goals + 3.30.2 Description + 3.30.3 Usage + 3.30.4 See also + 3.31 trunk/Identity/Themes/Motifs/TreeFlower + 3.31.1 Goals + 3.31.2 Description + 3.31.3 Usage + 3.31.4 See also + 3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds + 3.32.1 Goals + 3.32.2 Description + 3.32.2.1 Desktop background + 3.32.2.2 Anaconda Prompt (syslinux) background + 3.32.2.3 Grub background + 3.32.3 Usage + 3.32.4 See also + 3.33 trunk/Identity/Widgets + 3.33.1 Goals + 3.33.2 Description + 3.33.3 Usage + 3.33.4 See also + 3.34 trunk/Locales + 3.35 trunk/Locales/Identity + 3.35.1 Goals + 3.35.2 Description + 3.35.3 Usage + 3.35.4 See also + 3.36 trunk/Locales/Identity/Brands + 3.36.1 Goals + 3.36.2 Description + 3.36.2.1 Conventional file names + 3.36.2.2 Numeric file names + 3.36.2.3 Translation markers + 3.36.3 Usage + 3.36.4 See also + 3.37 trunk/Locales/Identity/Brands/Tpl + 3.37.1 Goals + 3.37.2 Description + 3.37.3 Usage + 3.37.4 See also + 3.38 trunk/Locales/Identity/Fonts + 3.38.1 Goals + 3.38.2 Description + 3.38.2.1 Translation Markers + 3.38.3 Usage + 3.38.4 See also + 3.39 trunk/Locales/Identity/Models + 3.39.1 Goals + 3.39.2 Description + 3.39.3 Usage + 3.39.4 See also + 3.40 trunk/Locales/Identity/Release + 3.40.1 Goals + 3.40.2 Description + 3.40.3 Usage + 3.40.4 See also + 3.41 trunk/Locales/Identity/Themes + 3.41.1 Goals + 3.41.2 Description + 3.41.3 Usage + 3.41.4 See also + 3.42 trunk/Locales/Identity/Themes/Backgrounds + 3.42.1 Goals + 3.42.2 Description + 3.42.3 Usage + 3.42.4 See also + 3.43 trunk/Locales/Identity/Themes/Distro/Anaconda/Progress + 3.43.1 Goals + 3.43.2 Description + 3.43.3 Usage + 3.43.4 See also + 3.44 trunk/Locales/Identity/Widgets + 3.44.1 Goals + 3.44.2 Description + 3.44.3 Usage + 3.44.4 See also + 3.45 trunk/Manuals + 3.45.1 Goals + 3.45.2 Description + 3.45.3 Usage + 3.45.4 See also + 3.46 trunk/Scripts + 3.46.1 Goals + 3.46.2 Description + 3.46.3 Usage + 3.46.4 See also + 3.47 trunk/Scripts/Bash + 3.47.1 Goals + 3.47.2 Description + 3.47.3 Usage + 3.47.4 See also + 3.48 trunk/Scripts/Bash/Cli + 3.49 trunk/Scripts/Bash/Cli/Functions + 3.49.1 Goals + 3.49.2 Description + 3.49.3 Usage + 3.49.3.1 Global variables + 3.49.3.2 Global functions + 3.49.3.3 Specific functions + 3.49.4 See also + 3.50 trunk/Scripts/Bash/Cli/Functions/Help + 3.50.1 Goals + 3.50.2 Description + 3.50.3 Usage + 3.50.4 See also + 3.51 trunk/Scripts/Bash/Cli/Functions/Html + 3.51.1 Goals + 3.51.2 Description + 3.51.3 Usage + 3.51.4 See also + 3.52 trunk/Scripts/Bash/Cli/Functions/Locale + 3.52.1 Goals + 3.52.2 Description + 3.52.3 Usage + 3.52.4 See also + 3.53 trunk/Scripts/Bash/Cli/Functions/Manual + 3.53.1 Goals + 3.53.2 Description + 3.53.3 Usage + 3.53.4 See also + 3.54 trunk/Scripts/Bash/Cli/Functions/Path + 3.54.1 Goals + 3.54.2 Description + 3.54.2.1 Repository layout + 3.54.2.2 Repository name convenctions + 3.54.2.3 Repository work flow + 3.54.2.4 Parallel directories + 3.54.2.5 Syncronizing path information + 3.54.2.6 What is the right place to store it? + 3.54.3 Usage + 3.54.4 See also + 3.55 trunk/Scripts/Bash/Cli/Functions/Render + 3.55.1 Renderable identity directory structures + 3.55.1.1 Design template without translation + 3.55.1.2 Design template with translation (one-to-one) + 3.55.1.3 Design template with translation (optimized) + 3.55.1.4 Design template with translation (optimized+flexibility) + 3.55.2 Renderable translation directory structures + 3.55.3 Copying renderable directory structures + 3.55.4 Usage + 3.55.5 See also + 3.56 trunk/Scripts/Bash/Cli/Functions/Render/Config + 3.56.1 Goals + 3.56.2 Description + 3.56.2.1 The `render.conf.sh' identity model + 3.56.2.2 The `render.conf.sh' translation model + 3.56.2.3 The `render.conf.sh' rendering actions + 3.56.3 Usage + 3.56.4 See also + 3.57 trunk/Scripts/Bash/Cli/Functions/Shell + 3.57.1 Goals + 3.57.2 Description + 3.57.3 Usage + 3.57.4 See also + 3.58 trunk/Scripts/Bash/Cli/Functions/Svg + 3.58.1 Goals + 3.58.2 Description + 3.58.2.1 Metadata maintainance + 3.58.2.2 Unused definitions + 3.58.3 Usage + 3.58.4 See also + 3.59 trunk/Scripts/Bash/Cli/Functions/Verify + 3.59.1 Goals + 3.59.2 Description + 3.59.2.1 Packages + 3.59.2.2 Links + 3.59.2.3 Environment variables + 3.59.3 Usage + 3.59.4 See also + 3.60 trunk/Scripts/Python + 3.60.1 Goals + 3.60.2 Description + 3.60.3 Usage + 3.60.4 See also +Index +List of Figures + + +CentOS Artwork Repository - File System +*************************************** + +Copyright (C) 2009-2011 Alain Reguera Delgado + + Permission is granted to copy, distribute and/or modify this document +under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no +Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A +copy of the license is included in the section entitled GNU Free +Documentation License. + +1 branches +********** + +2 tags +****** + +3 trunk +******* + +3.1 trunk/Identity +================== + +3.1.1 Goals +----------- + +The `trunk/Identity' directory exists to organize CentOS corporate +identity artworks. + +3.1.2 Description +----------------- + +The CentOS Project corporate identity is the "persona" of the +organization known as The CentOS Project. The CentOS Project corporate +identity plays a significant role in the way the CentOS Project, as +organization, presents itself to both internal and external +stakeholders. In general terms, the CentOS Project corporate visual +identity expresses the values and ambitions of the CentOS Project +organization, its business, and its characteristics. + + The CentOS Project corporate identity provides visibility, +recognizability, reputation, structure and identification to the CentOS +Project organization by means of corporate design, corporate +communication, and corporate behaviour. + + The CentOS Project settles down its corporate visual identity on a +"monolithic corporate visual identity structure". In this structure The +CentOS Project uses one unique name (The CentOS Brand) and one unique +visual style (The CentOS Default Theme) in all its manifestations. + +*The CentOS Brands* + The CentOS brand is the name or trademark that conncects the + producer with their products. In this case, the producer is The + CentOS Project and the products are the CentOS distributions, the + CentOS web sites, the CentOS promotion stuff, etc. + + *Note trunk Identity Brands::, for more information. + +*The CentOS Themes* + The CentOS themes are a set of image files connected all together + by one unique visual style. Each theme is organized in different + visual manifestations, in order to cover each visual manifestation + of The CentOS Project (i.e., distributions, websites, promotion + stuff, etc.). *Note trunk Identity Themes::, for more information. + + Inside a monolithic corporate visual identity structure, internal and +external stakeholders use to feel a strong sensation of uniformity, +orientation, and identification with the organization. No matter if you +are visiting websites, using the distribution, or acting on social +events, the one unique name and one unique visual style conect them all +to say: Hey! we are all parts of the CentOS project. And, probably, +some vister will say: Can I join the party? Yes you can, it is free. :) + +3.1.3 Usage +----------- + +To produce identity artworks, use the following commands: + +`centos-art render 'path/to/dir'' + When `path/to/dir' refers to one renderable directory under + `trunk/Identity', this command renders identity artworks using + both related design models and related translation files. + +`centos-art render 'path/to/dir' --filter='pattern'' + When `path/to/dir' refers to one renderable directory under + `trunk/Identity', this command renders identity artworks using + both related design models and related translation files that match + the regular expression passed in `--filter='pattern'' argument. + + To control the number of files produced by `centos-art' command, + you need to look into the translation path and provide a regular + expression pattern that matches the translation path, or paths, + related to the file, or files, you want to produce. + + The regular expression pattern you provide to `centos-art' command + is applied to the translation path from its very beginning. It is + not the same to say `5/en/01-welcome' that `01-welcome', the frist + expression matches but the last one does not. + + When using `--filter='pattern'' you don't need to specify the file + extension. It is removed from translation path before applying the + pattern, so it doesn't count here. + +3.1.4 File name convenctions +---------------------------- + +As file name convenction, inside CentOS Artwork Repository, both +text-based and image-based file name produced by `centos-art.sh' script +has the same name of their translation files without the `.sed' +extension. The file extension is set as follow: + +3.1.4.1 When text-based files are rendered +.......................................... + +Text-based files end up having the same extension of their design +template file. + +3.1.4.2 When image-based files are rendered +........................................... + +Image-based files always end up having the `.png' extension. + + *Tip* Once `.png' images are created, other image formats may be + created using the `renderFormats' post-rendering action, inside + the image-based related pre-rendering configuration script. + + *Note trunk Scripts Bash::, for more information. + +3.1.5 See also +-------------- + +3.1.6 References +---------------- + + * `http://en.wikipedia.org/Corporate_identity' (and related links). + +3.2 trunk/Identity/Brands +========================= + +3.2.1 Goals +----------- + + * ... + +3.2.2 Description +----------------- + +3.2.3 Usage +----------- + +3.2.4 See also +-------------- + +3.3 trunk/Identity/Fonts +======================== + +3.3.1 Goals +----------- + +This section exists to organize digital typographies used by the CentOS +project. + +3.3.2 Description +----------------- + +3.3.3 Usage +----------- + +The CentOS corporate identity is attached to `DejaVu LGC' font-family. +Whatever artwork you design for CentOS project, that requires +typography usage, must be done using `DejaVu LGC' font-family. + +*Recommendation-1:* + For screen desings (e.g., anything that final destination will + never be printed on paper or any medium outside computer screens) + use `DejaVu LGC Sans' font-family. + +*Recommendation-2:* + For non-screen designs (e.g., anything that final desition will be + printed on paper or any other medium outside computer screens) use + `DejaVu LGC Serif' font-family. As convenction files described in + this rule are stored under `Stationery' directories. + + The only execption for the two recommendations above is the +typography used inside CentOS logo. The CentOS logo is the main visual +representation of the CentOS project so the typography used in it must +be the same always, no matter where it be shown. It also has to be +clear enough to dismiss any confussion between similar typefaces (e.g., +the number one (1) sometimes is confuesed with the letter `el' (l) or +letter `ai' (i)). + + As CentOS logo typography convenction, the word `CentOS' uses +`Denmark' typography as base, both for the word `CentOS' and the phrase +`Community Enterprise Operating System'. The phrase size of CentOS logo +is half the size in poits the word `CentOS' has and it below `CentOS' +word and aligned with it on the left. The distance between `CentOS' +word and phrase `Community Enterprise Operating System' have the size +in points the phrase has. + + When the CentOS release brand is built, use `Denmark' typography for +the release number. The release number size is two times larger (in +height) than default `CentOS' word. The separation between release +number and `CentOS' word is twice the size in points of separation +between `CentOS' word and phrase `Community Enterprise Operating +System'. + + Another component inside CentOS logo is the trademark symbol (TM). +This symbol specifies that the CentOS logo must be consider a product +brand, even it is not a registered one. The trademark symbol uses +DejaVu LGC Sans Regular typography. The trademark symbol is aligned +right-top on the outter side of `CentOS' word. The trademark symbol +must not exceed haf the distance, in points, between `CentOS' word and +the release number on its right. + + It would be very convenient for the CentOS Project and its community +to to make a registered trademark (®) of CentOS logo. To make a +register trademark of CentOS Logo prevents legal complications in the +market place of brands. It grants the consistency, through time, of +CentOS project corporate visual identity. + + *Note* The information about trademarks and corporate identity is + my personal interpretation of + `http://en.wikipedia.org/Corporate_identity' and + `http://en.wikipedia.org/Trademark' description. If you have + practical experiences with these affairs, please serve yourself to + improve this section with your reasons. + +3.3.4 See also +-------------- + +3.4 trunk/Identity/Icons +======================== + +3.4.1 Goals +----------- + + * ... + +3.4.2 Description +----------------- + +3.4.3 Usage +----------- + +3.4.4 See also +-------------- + +3.5 trunk/Identity/Isolinux +=========================== + +3.5.1 Goals +----------- + + * ... + +3.5.2 Description +----------------- + +3.5.3 Usage +----------- + +3.5.4 See also +-------------- + +3.6 trunk/Identity/Models +========================= + +3.6.1 Goals +----------- + +This section exists to organize design models. + +3.6.2 Description +----------------- + +Design models are representative designs useful to understand how to +build artworks. + +3.6.3 Usage +----------- + +3.6.4 See also +-------------- + +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 +----------------- + + * ... + +3.7.3 Usage +----------- + + * ... + +3.7.4 See also +-------------- + +3.8 trunk/Identity/Models/Html +============================== + +3.8.1 Goals +----------- + + * ... + +3.8.2 Description +----------------- + + * ... + +3.8.3 Usage +----------- + + * ... + +3.8.4 See also +-------------- + +3.9 trunk/Identity/Models/Img/Promo/Web +======================================= + +3.9.1 Goals +----------- + + * Provide images related to CentOS web interface. + +3.9.2 Description +----------------- + + * ... + +3.9.3 Usage +----------- + + * ... + +3.9.4 See also +-------------- + +3.10 trunk/Identity/Models/Tpl +============================== + +3.10.1 Goals +------------ + + * ... + +3.10.2 Description +------------------ + + * ... + +3.10.3 Usage +------------ + + * ... + +3.10.4 See also +--------------- + +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: + + * One unique name and one unique visual style to all web + applications used inside the web environment. + + * One-step navigation to web applications inside the environment. + + * High degree of customization to change the visual style of all web + applications with few changes (e.g, updating just two or three + images plus common style sheet [CSS] definitions). + + The CentOS project is attached to a monolithic corporate visual +identity (*note 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 that used by +MoinMoin. + + This visual style diversity complicates our goal of one unique visual +style for all web applications. So, if we want one unique visual style +for all web applications used, it is innevitable to modify the web +applications in order to implement the CentOS one unique visual style +customization in them. Direct modification of upstream applications is +not convenient because upstream applications come with their one visual +style and administrators take the risk of loosing all customization +changes the next time the application be updated (since not all +upstream web applications, used in CentOS web environment, separate +presentation from logic). + + To solve the "one unique visual style" issue, installation and +actualization of web applications --used inside CentOS web +environment-- need to be independent from upstream web applications +development line; in a way that CentOS web environment administrators +can install and update web applications freely without risk of loosing +the one unique visual style customization changes. + + At the surface of this issue we can see the need of one specific yum +repository to store CentOS web environment customized web applications. + +3.11.2.1 Design model (without ads) +................................... + +3.11.2.2 Design model (with ads) +................................ + +3.11.2.3 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. + +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* 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. + + *Tip* Use the `diff' command of Subversion 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. + + *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. + + *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 +------------ + + * ... + +3.11.4 See also +--------------- + +---------- Footnotes ---------- + + (1) The theme support of Mailman may be introduced in mailman-3.x.x +release. + +3.12 trunk/Identity/Models/Xcf +============================== + +3.12.1 Goals +------------ + + * ... + +3.12.2 Description +------------------ + + * ... + +3.12.3 Usage +------------ + + * ... + +3.12.4 See also +--------------- + +3.13 trunk/Identity/Release +=========================== + +3.13.1 Goals +------------ + + * ... + +3.13.2 Description +------------------ + +3.13.3 Usage +------------ + +3.13.4 See also +--------------- + +3.14 trunk/Identity/Themes +========================== + +3.14.1 Goals +------------ + +The `trunk/Identity/Themes/' directory exists to organize production of +CentOS themes. + +3.14.2 Description +------------------ + +3.14.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.14.4 See also +--------------- + +3.15 trunk/Identity/Themes/Models +================================= + +3.15.1 Goals +------------ + + * Organize theme models. + +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 `*Note Default: trunk +Identity Themes Models Default,' and `*Note Alternative: trunk Identity +Themes Models Alternative,' ready-to-use theme models. + +3.15.4 See also +--------------- + +3.16 trunk/Identity/Themes/Models/Alternative +============================================= + +3.16.1 Goals +------------ + + * ... + +3.16.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.16.3 Usage +------------ + + * ... + +3.16.4 See also +--------------- + +3.17 trunk/Identity/Themes/Models/Default +========================================= + +3.17.1 Goals +------------ + +This location stores CentOS default theme model. The default theme +model of CentOS is used in all visual manifestations of CentOS Project +corporate visual identity (e.g., distributions, web sites, promotion, +etc.). + +3.17.2 Description +------------------ + +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 *Note Theme Motifs: trunk Identity Themes Motifs. + +3.17.4 See also +--------------- + +3.18 trunk/Identity/Themes/Models/Default/Distro +================================================ + +3.18.1 Goals +------------ + + * ... + +3.18.2 Description +------------------ + +It applies to all major releases of CentOS distribution. + +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. + + 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* 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. + +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. + + 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.18.3 Usage +------------ + +3.18.4 See also +--------------- + +3.19 trunk/Identity/Themes/Models/Default/Distro/Anaconda +========================================================= + +3.19.1 Goals +------------ + + * ... + +3.19.2 Description +------------------ + +3.19.3 Usage +------------ + +3.19.4 See also +--------------- + +3.20 trunk/Identity/Themes/Models/Default/Promo +=============================================== + +3.20.1 Goals +------------ + + * ... + +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 +------------ + + * ... + +3.20.4 See also +--------------- + +3.21 trunk/Identity/Themes/Models/Default/Web +============================================= + +3.21.1 Goals +------------ + + * ... + +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 +------------ + + * ... + +3.21.4 See also +--------------- + +3.22 trunk/Identity/Themes/Motifs +================================= + +3.22.1 Goals +------------ + +The `trunk/Identity/Themes/Motifs' directory exists to: + + * Organize CentOS themes' artistic motifs. + +3.22.2 Description +------------------ + +The artistic motif of theme is a graphic design component that provides +the visual style of themes, it is used as pattern to connect all visual +manifestations inside one unique theme. + + Artistic motifs are based on conceptual ideas. Conceptual ideas bring +the motivation, they are fuel for the engines of human imagination. +Good conceptual ideas may produce good motivation to produce almost +anything, and art works don't escape from it. + +`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 the name of your artistic motif. If possible, +when creating new conceptual ideas for CentOS, think about what CentOS +means for you, what does it makes you feel, take your time, think deep, +and share; you can improve the idea as time goes on. + + Once you have defined a name for your theme, you need to create the +motif structure of your theme. The motif structure is the basic +direcotry structure you'll use to work your ideas. Here is where you +organize your graphic design projects. + + To add a new motif structure to CentOS Artwork Repository, you need +to use the `centos-art' command line in the `Identity/Themes/Motifs/' +directory as described below: + + centos-art add --motif=ThemeName + + The previous command will create the basic structure of themes 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 +------------ + +When designing artistic motifs for CentOS, consider the following +recommendations: + + * Give a unique (case-sensitive) name to your Motif. This name is + used as value wherever theme variable ($THEME) or translation + marker (=THEME=) is. Optionally, you can add a description about + inspiration and concepts behind your work. + + * Use the location `trunk/Identity/Themes/Motifs/$THEME/' to store + your work. If it doesn't exist create it. Note that this require + you to have previous commit access in CentOS Artwork Repository. + + * The CentOS Project is using the blue color (#204c8d) as base color + for its corporate visual identity. Use such base corporate color + information as much as possible in your artistic motif designs. + + * Try to make your design fit one of the theme models. + + * Feel free to make your art enterprise-level and beautiful. + + * Add the following information on your artwork (both in a visible + design area and document metadata): + + * The name (or logo) of your artistic motif. + + * The copyright sentence: Copyright (C) YEAR YOURNAME + + * The license under which the work is released. All CentOS Art + works are released under Creative Common Share-Alike License + 3.0 (http://creativecommons.org/licenses/by-sa/3.0/) + (`http://creativecommons.org/licenses/by-sa/3.0/'). + + +3.22.4 See also +--------------- + +3.23 trunk/Identity/Themes/Motifs/Flame +======================================= + +3.23.1 Goals +------------ + +This section describes the steps we followed to construct the _Flame_ +artistic motif. This section may be useful for anyone interested in +reproducing the _Flame_ artistic motif, or in creating new artistic +motifs for The CentOS Project corporate visual identity (*note trunk +Identity::). + +3.23.2 Description +------------------ + +The _Flame_ artistic motif was built using the flame filter of Gimp 2.2 +in CentOS 5.5. + + The flame filter of Gimp can produce stunning, randomly generated +fractal patterns. The flame filter of Gimp gives us a great oportunity +to reduce the time used to produce new artistic motifs, because of its +"randomly generated" nature. Once the artistic motif be created, it is +propagated through all visual manifestations of CentOS Project +corporate visual identity using the `centos-art.sh' script (*note trunk +Scripts Bash::) inside the CentOS Artwork Repository. + + To set the time intervals between each new visual style production, +we could reuse the CentOS distribution major release schema. I.e., we +could produce a new visual style, every two years, based on a new +"randomly generated" flame pattern, and publish the whole corporate +visual identity (i.e., distribution stuff, promotion stuff, websites +stuff, etc.) with the new major release of CentOS distribution all +together at once. + + Producing a new visual style is not one day's task. Once we have +defined the artistic motif, we need to propagate it through all visual +manifestations of The CentOS Project corporate visual identity. When we +say that we could produce one new visual style every two years we +really mean: to work two years long in order to propagate a new visual +style to all visual manifestations of The CentOS Project corporate +visual identity. + + Obviously, in order to propagate one visual style to all different +visual manifestations of The CentOS Project corporate visual identity, +we need first to know which the visual manifestations are. To define +which visual manifestations are inside The CentOS Project corporate +visual identity is one of the goals the CentOS Artwork Repository and +this documentation manual are both aimed to satisfy. + + Once we define which the visual manifestation are, it is possible to +define how to produce them, and this way, organize the automation +process. Such automation process is one of the goals of `centos-art.sh' +script. + + With the combination of both CentOS Artwork Repository and +`centos-art.sh' scripts we define work lines where translators, +programmers, and graphic designers work together to distribute and +reduce the amount of time employed to produce The CentOS Project +monolithic corporate identity. + + From a monolithic corporate visual identity point of view, notice +that we are producing a new visual style for the same theme (i.e., +_Flame_). It would be another flame design but still a flame design. +This idea is very important to be aware of, because we are somehow +"refreshing" the theme, not changing it at all. + + This way, as we are "refreshing" the theme, we still keep oursleves +inside the monolithic conception we are trying to be attached to (i.e., +one unique name, and one unique visual style for all visual +manifestations). + + Producing artistic motifs is a creative process that may consume long +time, specially for people without experienced knowledge on graphic +design land. Using "randomly generated" conception to produce artistic +motifs could be, practically, a way for anyone to follow in order to +produce maintainable artistic motifs in few steps. + + Due to the "randomly generated" nature of Flame filter, we find that +_Flame_ pattern is not always the same when we use _Flame_ filter +interface. + + Using the same pattern design for each visual manifestation is +essential in order to maintain the visual connection among all visual +manifestations inside the same theme. Occasionally, we may introduce +pattern variations in opacity, size, or even position but never change +the pattern design itself, nor the color information used by images +considered part of the same theme. + + *Important* When we design background images, which are considered + part of the same theme, it is essential to use the same design + pattern always. This is what makes theme images to be visually + connected among themeselves, and so, the reason we use to define + the word "theme" as: a set of images visually connected among + themeselves. + + In order for us to reproduce the same flame pattern always, _Flame_ +filter interface provides the `Save' and `Open' options. The `Save' +option brings up a file save dialog that allows you to save the current +Flame settings for the plug-in, so that you can recreate them later. +The `Open' option brings up a file selector that allows you to open a +previously saved Flame settings file. + + The Flame settings we used in our example are saved in the file: + + +trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def + +3.23.3 Construction +------------------- + +3.23.3.1 Step 1: Set image size +............................... + +Create an empty image and fill the `Background' layer with black +(`000000') color. Image dimensions depend on the final destination you +plan to use the image for. For the sake of our construction example we +used an image of 640x480 pixels and 300 pixels per inch (ppi). + +3.23.3.2 Step 2: Add base color and pattern information +....................................................... + +Create a new layer named `Base', place it over `Background' layer and +fill it with the base color (`7800ff') you want to have your background +image set in. Add a mask to `Base' layer using radial gradient and +blur it. You may need to repeat this step more than once in order to +achieve a confortable black radial degradation on the right side of +your design. + + Duplicate `Base' layer and name it `Paper'. Place `Paper' layer over +`Base' layer. Remove content of `Paper' layer and fill it with `Paper +(100x100)' pattern. Once you've done with black radial degradation, +reduce the `Paper' layer opacity to 20%. + + Notice that when we duplicate one layer, the mask information related +to layer is preserved from previous to next layer. This saves us some +of the time required to produce different layers with the same mask +information on them. + + Duplicate `Paper' layer and rename it `Stripes'. Remove paper +pattern from `Stripes' layer. Fill `Stripes' layer with `Stripes +(48x48)' pattern and reduce the `Stripes' layer opacity to 15%. + +3.23.3.3 Step 3: Add flame motif +................................ + +Create a new layer named `Flame'. Set the foreground (`003cff') and +background (`0084ff') colors to the gradient you want to build the +flame motif. + + To build flame motif, use the flame filter (`Filters > Render > +Nature > Flame...') on `Flame' layer. We used a layer mask, with a +radial gradient on it to control the boundaries of flame motif on +`Flame' layer. + + Duplicate `Flame' layer and rename it `Flame Blur'. Place `Flame +Blur' below `Flame' layer. Apply Gussian blur filter (`Filters > Blur > +Gussian Blur...') until reaching the desiered effect. + + The opacity value, in `Flame' layers, may vary from one image to +another based on the place the image will be finally placed on. For +example, images used as desktop background have the `Flame' layer +opacity set at 100% but `Flame Blur' is set to 70%. However, you may +find that background images used in anaconda progress slides have +opacity reduced differently, in order to reduce brightness in a way +that texts could look clean and readable over it. + +3.23.3.4 Step 4: Add foreground color +..................................... + +Create a new layer named `Color', place it on top of all visible layers +and fill it with plain color (`4c005a'). Reduce `Color' layer opacity +to 20%. You can use the `Color' layer to control the right side color +information you want to produce the image for. + + Duplicate `Flame' layer and create a new layer named `Color#1'. +Place `Color#1' layer on top of layer named `Color'. Remove the mask +information from `Color#1' layer and recreate a new one using an +inverted alpha channel as reference. Remove `Color#1' layer content +and fill it back with plain black (`000000') color. Reduce `Color#1' +opacity to 20%. In this step we created a mask to protect the flame +artistic motif from black color, so when we decrement or increment the +opacity of layer, the flame artistic motif wouldn't be affected, just +the environment suround it. + + When you set color information, remember that the same artistic motif +needs to be indexed to 14 and 16 colors, in order to produce Grub and +Syslinux visual manifestations respectively. Using many different +colors in the artistic motif may reduce the possibility of your design +to fix all different situations in. Likewise, using more colors in one +design, and less colors in another design will reduce the connectivity +among your designs, since color information is relevant to visual +identity. + + When you propagate your artistic motif visual style to different +visual manifestations of CentOS Project corporate visual identity, it +is up to you to find out justice and compromise among all possible +variables you may face. + +3.23.4 See also +--------------- + +3.24 trunk/Identity/Themes/Motifs/Modern +======================================== + +3.24.1 Presentation +------------------- + +3.24.2 Construction +------------------- + +3.24.3 Usage +------------ + + * ... + +3.24.4 See also +--------------- + +3.25 trunk/Identity/Themes/Motifs/Modern/Backgrounds +==================================================== + +3.25.1 Goals +------------ + + * Organize background images for Modern theme. + +3.25.2 Description +------------------ + +Inside `Motifs' directory, the `Backgrounds/' directory is used to +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 the import feautre of Inkscape. + + 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 (e.g. Anaconda), 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 artistic motif. + + Background images are linked (using the import feature of Inkscape) +inside almost all theme art works. This structure let you make +centralized changes on the visual identity and propagate them quickly +to other areas. + + In this structure you design background images for different screen +resolutions based on the theme artistic motif. + + You may create different artistic motifs propositions based on the +same conceptual idea. The conceptual idea is what defines a theme. +Artistic motifs are interpretations of that idea. + + Inside this directory artistic motifs are organized by name (e.g., +TreeFlower, Modern, etc.). + + Each artistic motif directory represents just one unique artistic +motif. + + The artistic motif is graphic design used as common pattern to +connect all visual manifestations inside one unique theme. The +artistic motif is based on a conceptual idea. Artistic motifs provide +visual style to themes. + + Designing artistic motifs is for anyone interested in creating +beautiful themes for CentOS. When building a theme for CentOS, the +first design you need to define is the artistic motif. + + Inside CentOS Artwork Repository, theme visual styles (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 `Motifs/' directory using the model name, and +the model directory structure as reference. + + The artistic motif base structure is used by `centos-art' to produce +images automatically. This section describes each directory of CentOS +artistic motif base structure. + +3.25.3 Usage +------------ + +The `Backgrounds/' directory is probably the core component, inside +`Motifs/' directory structure. Inside `Backgrounds/' directory you +produce background images used by almost all theme models (e.g., +Distribution, Websites, Promotion, etc.). The `Backgrounds/' directory +can contain subdirectories to help you organize the design process. + +3.25.4 See also +--------------- + +3.26 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img +======================================================== + +3.26.1 Goals +------------ + + * ... + +3.26.2 Description +------------------ + +3.26.3 Usage +------------ + +In this directory is where you store all background images (e.g., .png, +.jpg, .xpm, etc.). This directory is required by `centos-art' command +line interface. + +3.26.4 See also +--------------- + +3.27 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl +======================================================== + +3.27.1 Goals +------------ + + * ... + +3.27.2 Description +------------------ + +3.27.3 Usage +------------ + +In this directory is where you store all the scalable vector graphics +(e.g., .svg) files. This directory is required by `centos-art' command +line interface. + +3.27.4 See also +--------------- + +3.28 trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf +======================================================== + +3.28.1 Goals +------------ + + * ... + +3.28.2 Description +------------------ + + * ... + +3.28.3 Usage +------------ + +In this directory is where you store the project files (e.g, .xcf) of +Gimp. 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 background projects. Of course, you can merge both +Gimp and Inkscape power to produce images based on them. In this last +case you need the `Xcf/' directory. + +3.28.4 See also +--------------- + +3.29 trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress +================================================================= + +3.29.1 Goals +------------ + + * ... + +3.29.2 Description +------------------ + +3.29.3 Usage +------------ + +To render Anaconda progress slide images using the _Modern_ artistic +motif design, the Default theme model, and available translation files +(-- *Removed*(pxref:trunk Translations Identity Themes Distro Anaconda +Progress) --); use the following commands: + + cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ + centos-art render --identity + + The above command will create the following structure: + + trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress + |-- 3 + | |-- en + | | |-- 01-welcome.png + | | |-- 02-donate.png + | | `-- 03-yum.png + | `-- es + | |-- 01-welcome.png + | |-- 02-donate.png + | `-- 03-yum.png + |-- 4 + | |-- en + | | |-- 01-welcome.png + | | |-- 02-donate.png + | | `-- 03-yum.png + | `-- es + | |-- 01-welcome.png + | |-- 02-donate.png + | `-- 03-yum.png + `-- 5 + |-- en + | |-- 01-welcome.png + | |-- 02-donate.png + | `-- 03-yum.png + `-- es + |-- 01-welcome.png + |-- 02-donate.png + `-- 03-yum.png + +3.29.4 See also +--------------- + +3.30 trunk/Identity/Themes/Motifs/Modern/Palettes +================================================= + +3.30.1 Goals +------------ + + * Organize palette files for Modern theme. + +3.30.2 Description +------------------ + +3.30.3 Usage +------------ + +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 the unique color information required by theme. + +3.30.4 See also +--------------- + +3.31 trunk/Identity/Themes/Motifs/TreeFlower +============================================ + +3.31.1 Goals +------------ + + * ... + +3.31.2 Description +------------------ + +3.31.3 Usage +------------ + +3.31.4 See also +--------------- + +3.32 trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds +======================================================== + +3.32.1 Goals +------------ + +This section exists to orgnize backgrounds of _TreeFlower_ artistic +motif. + +3.32.2 Description +------------------ + +3.32.2.1 Desktop background +........................... + +Once you have defined the vectorial artistic motif design, use the +`centos-art.sh' script (as described in usage section below) to produce +the png version of it. With the png version of your vectorial design do +the following: + + Open the png version with GIMP. + + Save the png version as a project of GIMP inside +`trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Xcf' directory, +using the same name of your vectorial design but with the `.xcf' +extension. + + Now use GIMP to improve your design. Here you may add one layer for +pattern, another for colors, and so on until you find yourself +confortable with your artwork. For example, the following layer +distribution (from bottom to top) was used to build revision 285 of +file `1360x768.xcf' using _TreeFlower_ artistic motif at revision 241. + +*Layer 1: Background* + The first thing we did with GIMP was to create a layer named + `Background' to store the artistic motif (File > Open as layer). + This layer is the lowest layer in the image. Later, we started to + create layers one upon another to change the artistic motif visual + style. + +*Layer 2: Shadow#1* + This layer is above `Background' and contains a linear gradient + from left (000000) to right (transparent) covering the whole image. + This layer masks the artistic motif to avoid the effect of linear + gradient. This layer is 100% of opacity. + +*Layer 3: Shadow#2* + This layer is above `Shadow#1' and contains a linear gradient from + left (000000) to right (transparent) covering just the 70% of the + whole image aproximatly. This layer doesn't mask the artistic motif + which make the left part of it fall into the dark of linear + gradient. This layer is 100% of opacity. + +*Layer 4: Pattern (Paper)* + This layer is above `Shadow#2' an contains the paper pattern + shipped with GIMP 2.2. This layer doesn't mask the artistic motif + so the pattern is applied over the whole image. This layer is set + to 15% of opacity. + +*Layer 5: Pattern (Stripes)* + This layer is above `Pattern (Paper)' and contains the stripes + used over the artistic motif. This layer do masks the artistic + motif so the stripes are only applied to it. This layer is set to + 10% of opacity. + +*Layer 6: Shadow#3* + This layer is above `Pattern (Stripes)' and contains a linear + gradient from right (6600ff) to left (transparent). This layer + masks the artistic motif so the linear gradient doesn't affect it. + This layer is set to 15% of opacity. + +*Layer 7: Shadow#4* + This layer is above `Shadow#3' and contains a linear gradient from + left (000000) to right (transparent). This layer do masks the + artistic motif so the linear gradient doesn't affect it. This + layer is set to 10% of opacity. + +*Layer 8: Color#1* + This layer is above `Shadow#4' and is filled with orange (ffae00) + color over the whole image. This layer is set to 10% of opacity. + +*Layer 9: Color#2* + This layer is above `Color#1' and is filled with blue (010a88) + color over the whole image. This layer is set to 10% of opacity. + + + *Note* There is no definite combination. To get the appropriate + visual design is a matter of constant testing and personal taste. + + Finally, use `Save as copy ...' option to export the final design. +To export the final design use the same name of your vectorial design +plus `-final.png' extension. + + You can repeat these steps to create images for other screen +resolutions. + +3.32.2.2 Anaconda Prompt (syslinux) background +.............................................. + +When building syslinux backgrounds it is needed to take into account +that the final image is reduced to 16 colors. In desktop background +there is no color limitation but syslinux does have. The goal of this +section is achieving a final syslinux background as close as possible +to desktop backgrounds using 16 colors only. + + Another point to consider is the forground and background definition +used by syslinux. The syslinux documentation says that the color set in +position 0 is the background and color set in position 7 is the +forground. The final palette of color used by our background will match +that specification. For great contrast we'll use black as background +and white as forground. At this poing we have black (000000) and white +(ffffff) colors in our syslinux palette, which left us with 14 colors +to play with. + + Let's begin with `Xcf/640x300.xcf' layer distribution from bottom to +top: + +*Layer 1: Background* + This layer is the lowest layer in the image composition and + contains the artistic motif image rendered for the same resolution + (i.e., `Img/Png/640x300.png'). This layer is set to 100% of + opacity. + +*Layer 2: Pattern (Paper)* + This layer is placed above `Background' layer and contains the + paper pattern shipped with GIMP 2.2. This layer doesn't mask the + artistic motif. This layer is set to 30% of opacity. + +*Layer 3: Pattern (Stripes)* + This layer is placed above `Pattern (Paper)' layer and contains + the stripes pattern shipped with GIMP 2.2. This layer does mask the + artistic motif in order to apply the stripes over it only. The + background is not affected by the stripes pattern just the artistic + motif. This layer is set to 20% of opacity. + +*Layer 4: Shadow#1* + This layer is placed above `Pattern (Stripes)' layer and fills the + entire layer area with violet (6600ff) color. This layer do mask + the artistic motif in order to applied the violet color to the + background area outside the artistic motif only. This layer is set + to 15% of opacity. + +*Layer 5: Color#1* + This layer is above `Shadow#1' and is filled with orange (ffae00) + color to cover the whole image. This layer is set to 10% of + opacity. + +*Layer 6: Color#2* + This layer is above `Color#1' and is filled with blue (010a88) + color to cover the whole image. This layer is set to 10% of + opacity. + +*Layer 7: Shadow#2* + This layer is above `Color#1' and contains a linear gradient from + left (000000) to right (transparent) covering 70% of the image + approximately. + + + At this point we have the composition and should look like the +desktop backgrounds. Compared with desktop backgrounds there are some +differences in opacity. This is because in our testings the final color +information found with this composition produces an acceptable 16 color +image. Of course this is something we haven't seen yet. + + To define the color information of our current coposition, save the +syslinux background composition we've done using `File > Save as Copy +...' option in the following location: + + +trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Img/Png/640x300-final.png + + Now, create the final png version of syslinux backgrounds using the +following command: + + +centos-art render --entry=trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Prompt + + This command will create syslinux-splash final images for all major +releases of CentOS distribution the repository has been configured to. +The important files here are `syslinux-splash.png', other files may +contain the wrong information because we haven't defined yet the +correct color information to use. + + Open one `syslinux-splash.png' file with GIMP and use the `Image > +Mode > Indexed' to reduce image colors up to 16 colors, using the +`Generate optimum palette' feature of GIMP. If the image looks +aceptable after reducing colors, use the `Palettes' menu (Ctrl+P) of +GIMP to import a new palette from file and name it +`CentOS-TreeFlower-Syslinux'. Once you've saved the palette, the color +information is stored at: + + +~/.gimp-2.2/palettes/CentOS-TreeFlower-Syslinux.gpl + + You need to edit `CentOS-TreeFlower-Syslinux.gpl' file in order to +set the appropriate order of colors. Remember black (000000) in +position 0, and white (ffffff) in position 7. Other positions are +irrelevant. When editing this file you may find that color reduction +did not set black and white colors to their respective values exactly. +Change that manually. For example, consider the following palette: + + +GIMP Palette +Name: CentOS-TreeFlower-Syslinux +Columns: 16 +# + 0 0 0 Background (black) + 23 20 35 Untitled + 34 25 48 Untitled + 37 35 60 Untitled + 47 36 68 Untitled + 37 54 86 Untitled + 60 48 90 Untitled +255 255 255 Foreground (white) + 66 54 99 Untitled + 74 61 98 Untitled + 49 78 126 Untitled + 43 87 151 Untitled + 92 89 95 Untitled + 54 104 183 Untitled +158 153 156 Untitled +201 196 195 Untitled + + Update the `Palettes' menu to get the new color positions from the +file you just edited and open the palette with double click. + + Update the `syslinux.gpl' file copying the following file: + + +~/.gimp-2.2/palettes/CentOS-TreeFlower-Syslinux.gpl + + to + + +trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.gpl + + With the `CentOS-TreeFlower-Syslinux' palette opened in the `Palette +Editor', open (Ctrl+O) the following file: + + +trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.ppm + + and replace its color information with that one in +`CentOS-TreeFlower-Syslinux' palette. When you are replacing color +information inside `syslilnux.ppm', remember to keep the order of +colors just as they are in the `CentOS-TreeFlower-Palette' palette. + + The `syslinux.ppm' file is 16 pixels width and 1 pixel height, so +you probably need to zoom it a bit to set the color information in +their place when using the pen tool with the brush `Circle (01) (1 x +1)'. + + Once you've updated the `syslinux.ppm' file, it is time to update +the following file: + + +trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.hex + + The `syslinux.hex' file contains the color information in +hexadecimal notation. The color information in hexadecimal notation is +required by `ppmtolss16' command. The `ppmtolss16' command produces +the final LSS16 image format that is used by syslinux program inside +CentOS distribution. + + The color information inside `syslinux.hex' must match the one in +`syslinux.ppm' and `syslinux.gpl'. For example, based on +`CentOS-TreeFlower-Syslinux' palette of colors above, consider the +following `syslinux.hex' file: + + +#000000=0 +#171423=1 +#221930=2 +#25233c=3 +#2f2444=4 +#253656=5 +#3c305a=6 +#ffffff=7 +#423663=8 +#4a3d62=9 +#314e7e=10 +#2b5797=11 +#5c595f=12 +#3668b7=13 +#9e999c=14 +#c9c4c3=15 + +3.32.2.3 Grub background +........................ + +3.32.3 Usage +------------ + + * ... + +3.32.4 See also +--------------- + +3.33 trunk/Identity/Widgets +=========================== + +3.33.1 Goals +------------ + + * ... + +3.33.2 Description +------------------ + +3.33.3 Usage +------------ + +3.33.4 See also +--------------- + +3.34 trunk/Locales +================== + +The `trunk/Locales' directory exists to store the translation messages +used to produce content in different languages. + + Translation messages are organized using the directory structure of +the component being translated. For example, if we want to provide +translation messages for `trunk/Manuals/Filesystem', then the +`trunk/Locales/Manuals/Filesystem' directory needs to be created. + + Once the locale directory exists for the component we want to provide +translation messages for, it is necessary to create the translation +files where translation messages are. The translation files follows the +concepts of `xml2po' and GNU `gettext' tools. + + The basic translation process is as follow: first, translatable +strings are extracted from files and a portable object template (.pot) +is created or updated with the information. Using the portable object +template, a portable object (.po) is created or updated for translator +to locale the messages retrived. Finally, a machine object (.mo) is +created from portable object to sotore the translated messages. + + Inside the repository there are two ways to retrive translatable +strings from files. The first one is through `xml2po' command and the +second through `xgettext' command. The `xml2po' is used to retrive +translatable strings from XML files (e.g., Scalable Vector Graphics, +DocBook, etc.) and the `xgettext' command is used to retrive +translatable strings from shell scripts files (e.g., the files that +make the `centos-art.sh' command-line interface). + + When translatable strings are retrived from XML files, using the +`xml2po' command, there is no need to create the machine object as we +do when translatable strings ar retrived from shell files, using the +`xgettext' command. The `xml2po' produces a temporal machine object in +order to create a translated XML file. Once the translated XML file has +been created the machine object is no longer needed. On the other hand, +the machine object produced by the `xgettext' command is required by +the system in order for the show shell script localized messages. + + Another difference between `xml2po' and `xgettext' we need to be +aware of is the directory structure used to store machine objects. In +`xml2po', the machine object is created in the current working +directory as `.xml2po.mo' and can be safetly removed once the +translated XML file has been created. In the case of `xgettext', the +machine object needs to be stored in the +`$TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo' file in order for the +system to interpret it and should not be removed since it is the file +that contain the translation messages themselves. + + Automation of localization tasks is achived through the `locale' +functionality of command-line interface. + +3.35 trunk/Locales/Identity +=========================== + +3.35.1 Goals +------------ + + * ... + +3.35.2 Description +------------------ + + * ... + +3.35.3 Usage +------------ + + * ... + +3.35.4 See also +--------------- + +3.36 trunk/Locales/Identity/Brands +================================== + +3.36.1 Goals +------------ + + * Organize brands' translation files. + +3.36.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.36.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.36.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 designing ratio. + + For example, if your design template has 400x200 pixels of dimension, +and you apply a translation file named `300.sed' to it, the final image +you get as result will have 300x100 pixels of dimension. The same is +true if you use higher numbers like `1024.sed', `2048.sed', etc. In +these cases you have bigger images proportionally. + + As we are using scalable vector graphics to design identity +templates, the image size you produce is not limitted in size. You can +use one design template produced in 400x200 pixels to produce larger or +shorter PNG images using numeric translation files as described above. + +3.36.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. + + *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.36.3 Usage +------------ + +To render brands' translation files, use the following command: + + +centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands + +3.36.4 See also +--------------- + +3.37 trunk/Locales/Identity/Brands/Tpl +====================================== + +3.37.1 Goals +------------ + +3.37.2 Description +------------------ + +3.37.3 Usage +------------ + +3.37.4 See also +--------------- + +3.38 trunk/Locales/Identity/Fonts +================================= + +3.38.1 Goals +------------ + +This section exists to organize fonts translation files. + +3.38.2 Description +------------------ + +Translation files, inside `trunk/Translations/Fonts', have the +following structure: + + +s!font-family:Denmark!font-family:DejaVu LGC Sans! +s!font-weight:normal!font-weight:bold! +s!font-style:normal!font-style:italic! + + Inside `trunk/Translations/Fonts', there is one translation file for +each font preview image you want to produce. This way, we create one +translation file for each font-family we use somewhere inside CentOS +visual identity. + + *Important* Do not create translation files for font-families not + used somewhere inside CentOS visual identity. The identity of font + entry (*note trunk Identity Fonts::) is used as reference when + someone needs to know which font-families are allowed to use + inside CentOS visual identity. + +3.38.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.38.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.38.4 See also +--------------- + +3.39 trunk/Locales/Identity/Models +================================== + +3.39.1 Goals +------------ + +3.39.2 Description +------------------ + +3.39.3 Usage +------------ + +3.39.4 See also +--------------- + +3.40 trunk/Locales/Identity/Release +=================================== + +3.40.1 Goals +------------ + +3.40.2 Description +------------------ + +3.40.3 Usage +------------ + +3.40.4 See also +--------------- + +3.41 trunk/Locales/Identity/Themes +================================== + +3.41.1 Goals +------------ + +3.41.2 Description +------------------ + +3.41.3 Usage +------------ + +3.41.4 See also +--------------- + +3.42 trunk/Locales/Identity/Themes/Backgrounds +============================================== + +3.42.1 Goals +------------ + + * ... + +3.42.2 Description +------------------ + + * ... + +3.42.3 Usage +------------ + + * ... + +3.42.4 See also +--------------- + +3.43 trunk/Locales/Identity/Themes/Distro/Anaconda/Progress +=========================================================== + +3.43.1 Goals +------------ + + * Organize Anaconda progress translation templates. + + * Organize Anaconda progress translation files in several languages + and major releases of CentOS distribution. + +3.43.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. + + * *Note trunk Identity Themes Motifs Modern Distro Anaconda + Progress::. + +3.43.3 Usage +------------ + +Translation rendering is described in `trunk/Translations' +documentation entry (-- *Removed*(pxref:trunk Translations) --). + +3.43.4 See also +--------------- + +3.44 trunk/Locales/Identity/Widgets +=================================== + +3.44.1 Goals +------------ + + * ... + +3.44.2 Description +------------------ + + * ... + +3.44.3 Usage +------------ + + * ... + +3.44.4 See also +--------------- + +3.45 trunk/Manuals +================== + +3.45.1 Goals +------------ + + * ... + +3.45.2 Description +------------------ + + * ... + +3.45.3 Usage +------------ + + * ... + +3.45.4 See also +--------------- + +3.46 trunk/Scripts +================== + +3.46.1 Goals +------------ + +The `trunk/Scripts' directory exists to: + + * Organize the "trunk" development line of automation scripts by + programming language. + +3.46.2 Description +------------------ + + * ... + +3.46.3 Usage +------------ + + * ... + +3.46.4 See also +--------------- + +3.47 trunk/Scripts/Bash +======================= + +3.47.1 Goals +------------ + +The `trunk/Scripts/Bash' directory exists to organize the trunk +development line of `centos-art.sh' automation script. The +`centos-art.sh' script standardizes frequent tasks inside your working +copy of CentOS Artwork Repository. + +3.47.2 Description +------------------ + +The best way to understand `centos-art.sh' automation script is +studying its source code. However, as start point, you may prefer to +read an introductory resume before diving into the source code details. + + The `centos-art.sh' script is written in Bash. Most tasks, inside +`centos-art.sh' script, have been organized in many specific +functionalities that you can invoke from the `centos-art' command-line +interface. + + 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 location. If your system was prepared to use CentOS Artwork +Repository correctly (-- *Removed*(pxref:trunk Scripts Bash Functions +Verify) --), you should have a symbolic link inside `~/bin/' directory +that points to the `centos-art.sh' script file. As `~/bin/' directory +is, by default, inside PATH environment variable, the execution of +`centos-art' command runs the `centos-art.sh' script. + + When `centos-art.sh' script is executed, the first it does is +executing the `trunk/Scripts/Bash/initEnvironment.sh' script to +initialize global variables (e.g., `gettext' variables) and global +function scripts. Global function scripts are located inside +`trunk/Scripts/Bash/Functions' directory and their file names begin +with `cli'. Global function scripts provide common functionalities that +can be used anywhere inside `centos-art.sh' script execution +environment. + + Once global variables and function scripts have been loaded, +`centos-art.sh' script executes the `cli' global function from `cli.sh' +function script to retrive command-line arguments and define some +default values that may be used later by specific function scripts (-- +*Removed*(pxref:trunk Scripts Bash Functions) --). + + As convenction, the `centos-art.sh' command-line arguments have the +following format: + + +centos-art arg1 --arg2=val2 --arg3=val3 + + In the above example, `centos-art' is the command you use to invoke +`centos-art.sh' script. The `arg1' is required and represents the +functionality you want to perform (e.g., `verify', `render', `locale', +`manual', etc.). The remaining arguments are modifiers to `arg1'. The +`--arg2' definition is required and represets, specifically, the action +inside the functionality you want to perform. The `--arg3' and on, are +optional. + + Once command-line arguments have been retrived, the `centos-art.sh' +script loads specific functionalities using the `cli_getFunctions.sh' +function script. Only one specific functionality can be loaded at one +script execution I.e., you run `centos-art.sh' script to run just one +functionality. + + ++----------------------------------------------------------------------+ +| [centos@host]$ centos-art function --action='value' --option='value' | ++----------------------------------------------------------------------+ +| ~/bin/centos-art --> ~/artwork/trunk/Scripts/Bash/centos-art.sh | ++---v-----------------------------------------v------------------------+ + | centos-art.sh | + +---v---------------------------------v---+ + . | initEnvironment.sh | . + . +---------------------------------+ . + . | cli $@ | . + . +---v-------------------------v---+ . + . . | cli_getFunctions | . . + . . +---v-----------------v---+ . . + . . . | function1 | . . . + . . . | function2 | . . . + . . . | function3 | . . . + . . . +-----------------+ . . . + . . ........................... . . + . ................................... . + ........................................... + +Figure 3.1: The functionalities initialization environment. + + Functionalities are implemented by means of actions. Once the +functionality has been initiazalized, actions initialization take place +for that functionality. Actions initialization model is very similar to +functions initialization model. But with the difference, that actions +are loaded inside function environment, and so, share variables and +functions defined inside function environment. + + ++--------------------------------------+ +| cli_getFunctions | ++---v------------------------------v---+ +. | function1 | . +. +---v----------------------v---+ . +. . | function1_getActions | . . +. . +---v--------------v---+ . . +. . . | action 1 | . . . +. . . | action 2 | . . . +. . . | action n | . . . +. . . +--------------+ . . . +. . ........................ . . +. ................................ . +. +------------------------------+ . +. | function2 | . +. +---v----------------------v---+ . +. . | function2_getActions | . . +. . +---v--------------v---+ . . +. . . | action 1 | . . . +. . . | action 2 | . . . +. . . | action n | . . . +. . . +--------------+ . . . +. . ........................ . . +. ................................ . +. +------------------------------+ . +. | function3 | . +. +---v----------------------v---+ . +. . | function3_getActions | . . +. . +---v--------------v---+ . . +. . . | action 1 | . . . +. . . | action 2 | . . . +. . . | action n | . . . +. . . +--------------+ . . . +. . ........................ . . +. ................................ . +........................................ + +Figure 3.2: The actions initialization environment. + +3.47.3 Usage +------------ + +The `centos-art.sh' script usage information is described inside each +specific function documentation (-- *Removed*(pxref:trunk Scripts Bash +Functions) --). + +3.47.4 See also +--------------- + +3.48 trunk/Scripts/Bash/Cli +=========================== + +3.49 trunk/Scripts/Bash/Cli/Functions +===================================== + +3.49.1 Goals +------------ + +The `trunk/Scripts/Bash/Functions' directory exists to organize +`centos-art.sh' specific functionalities. + +3.49.2 Description +------------------ + +The specific functions of `centos-art.sh' script are designed with +"Software Toolbox" philosophy (*note Toolbox introduction: +(coreutils.info)Toolbox introduction.) in mind: each program "should do +one thing well". Inside `centos-art.sh' script, each specific +functionality is considered a program that should do one thing well. +Of course, if you find that they still don't do it, feel free to +improve them in order for them to do so. + + The specific functions of `centos-art.sh' script are organized +inside specific directories under `trunk/Scripts/Bash/Functions' +location. Each specific function directory should be named as the +function it represents, with the first letter in uppercase. For +example, if the function name is `render', the specific function +directory for it would be `trunk/Scripts/Bash/Functions/Render'. + + To better understand how specific functions of `centos-art.sh' +script are designed, lets create one function which only goal is to +output different kind of greetings to your screen. + + When we create specific functions for `centos-art.sh' script it is +crucial to know what these functions will do exactly and if there is +any function that already does what we intend to do. If there is no +one, it is good time to create them then. Otherwise, if functionalities +already available don't do what you exactly expect, contact their +authors and work together to improve them. + + *Tip* Join CentOS developers mailing list + to share your ideas. + + It is also worth to know what global functions and variables do we +have available inside `centos-art.sh' script, so advantage can be taken +from them. Global variables are defined inside global function scripts. +Global functions scripts are stored immediatly under +`trunk/Scripts/Bash/Functions' directory, in files begining with `cli' +prefix. + + OK, let's begin with our functionality example. + + What function name do we use? Well, lets use `greet'. Note that +`hello' word is not a verb; but an expression, a kind of greeting, an +interjection specifically. In contrast, `greet' is a verb and describes +what we do when we say `Hello!', `Hi!', and similar expressions. + + So far, we've gathered the following function information: + + +Name: greet +Path: trunk/Scripts/Bash/Functions/Greet +File: trunk/Scripts/Bash/Functions/Greet/greet.sh + + The `greet.sh' function script is the first file `centos-art.sh' +script loads when the `greet' functionality is called using commands +like `centos-art greet --hello='World''. The `greet.sh' function +script contains the `greet' function definition. + + Inside `centos-art.sh' script, as convenction, each function script +has one top commentary, followed by one blank line, and then one +function defintion below it only. + + Inside `centos-art.sh' script functions, top commentaries have the +following components: the functionality description, one-line for +copyright note with your personal information, the license under which +the function source code is released --the `centos-art.sh' script is +released as GPL, so do all its functions--, the `$Id$' keyword of +Subversion is later expanded by `svn propset' command. + + In our `greet' function example, top commentary for `greet.sh' +function script would look like the following: + + +#!/bin/bash +# +# greet.sh -- This function outputs different kind of greetings to +# your screen. Use this function to understand how centos-art.sh +# script specific functionalities work. +# +# Copyright (C) YEAR YOURFULLNAME +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, but +# WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +# General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 +# USA. +# +# ---------------------------------------------------------------------- +# $Id$ +# ---------------------------------------------------------------------- + + After top commentary, separated by one blank line, the `greet' +function definition would look like the following: + + +function greet { + + # Define global variables. + + # Define command-line interface. + greet_getActions + +} + + The first definition inside `greet' function, are global variables +that will be available along `greet' function execution environment. +This time we didn't use global variable definitions for `greet' +function execution environment, so we left that section empty. + + Later, we call `greet_getActions' function to define the +command-line interface of `greet' functionality. The command-line +interface of `greet' functionality defines what and how actions are +performed, based on arguments combination passed to `centos-art.sh' +script. + + +function greet_getActions { + + case "$ACTIONNAM" in + + --hello ) + greet_doHello + ;; + + --bye ) + greet_doBye + ;; + + * ) + cli_printMessage "`gettext "The option provided is not valid."`" + cli_printMessage "$(caller)" 'AsToKnowMoreLine' + + esac + +} + + The ACTIONNAM global variable is defined in `cli.sh' function script +and contains the value passed before the equal sign (i.e., `=') in the +second command-line argument of `centos-art.sh' script. For example, if +the second command-line argument is `--hello='World'', the value of +ACTIONNAM variable would be `--hello'. Using this configuration let us +deside which action to perform based on the action name passed to +`centos-art.sh' script as second argument. + + The `greet' function definition makes available two valid greetings +through `--hello' and `--bye' options. If no one of them is provided +as second command-line argument, the `*' case is evaluated instead. + + The `*' case and its two lines further on should always be present +in `_getActions.sh' function scripts, no matter what specific +functionality you are creating. This convenction helps the user to find +out documentation about current functionality in use, when no valid +action is provided. + + The `greet_doHello' and `greet_doBye' function definitions are the +core of `greet' specific functionality. In such function definitions +we set what our `greet' function really does: to output different kinds +of greetings. + + +function greet_doHello { + + cli_printMessage "`gettext "Hello"` $ACTIONVAL" + +} + + The `greet_doHello' function definition is stored in +`greet_doHello.sh' function script. + + +function greet_doBye { + + cli_printMessage "`gettext "Goodbye"` $ACTIONVAL" + +} + + The `greet_doBye' function definition is stored in the +`greet_doBye.sh' function script. + + Both `greet_doHello.sh' and `greet_doBye.sh' function scripts are +stored inside `greet' function directory path (i.e. +`trunk/Scripts/Bash/Functions/Greet'). + + The ACTIONVAL global variable is defined in `cli.sh' function script +and contains the value passed after the equal sign (i.e., `=') in the +second command-line argument of `centos-art.sh' script. For example, if +the second command-line argument is `--hello='World'', the value of +ACTIONVAL variable would be `World' without quotes. + + Let's see how `greet' specific functionality files are organzied +under `greet' function directory. To see file organization we use the +`tree' command: + + +trunk/Scripts/Bash/Functions/Greet +|-- greet_doBye.sh +|-- greet_doHello.sh +|-- greet_getActions.sh +`-- greet.sh + + To try the `greet' specific functionality we've just created, pass +the function name (i.e., `greet') as first argument to `centos-art.sh' +script, and any of the valid options as second argument. Some examples +are illustrated below: + + +[centos@projects ~]$ centos-art greet --hello='World' +Hello World +[centos@projects ~]$ centos-art greet --bye='World' +Goodbye World +[centos@projects ~]$ + + The word `World' in the examples above can be anything. In fact, +change it to have a little fun. + + Now that we have a specific function that works as we expect, it is +time to document it. To document `greet' specific functionality, we +use its directory path and the `manual' functionality (-- +*Removed*(pxref:trunk Scripts Bash Functions Manual) --) of +`centos-art.sh' script, just as the following command illustrates: + + +centos-art manual --edit=trunk/Scripts/Bash/Functions/Greet + + To have a well documented function helps user to understand how your +function really works, and how it should be used. When no valid action +is passed to a function, the `centos-art.sh' script uses the function +documentation entry as vehicle to communicate which the valid functions +are. When no documentation entry exists for a function, the +`centos-art.sh' script informs that no documentation entry exists for +such function and requests user to create it right at that time. + + Now that we have documented our function, it is time to translate its +output messages to different languages. To translate specific +functionality output messages to different languages we use the +`locale' functionality (-- *Removed*(pxref:trunk Scripts Bash Functions +Locale) --) of `centos-art.sh' script, just as the following command +illustrates: + + +centos-art locale --edit + + *Warning* To translate output messages in different languages, + your system locale information --as in `LANG' environment + variable-- must be set to that locale you want to produce + translated messages for. For example, if you want to produce + translated messages for Spanish language, your system locale + information must be set to `es_ES.UTF-8', or similar, first. + + Well, it seems that our example is rather complete by now. + + In `greet' function example we've described so far, we only use +`cli_printMessage' global function in action specific function +definitions in order to print messages, but more interesting things can +be achieved inside action specific function definitions. For example, +if you pass a directory path as action value in second argument, you +could retrive a list of files from therein, and process them. If the +list of files turns too long or you just want to control which files to +process, you could add the third argument in the form +`--filter='regex'' and reduce the amount of files to process using a +regular expression pattern. + + The `greet' function described in this section may serve you as an +introduction to understand how specific functionalities work inside +`centos-art.sh' script. With some of luck this introduction will also +serve you as motivation to create your own `centos-art.sh' script +specific functionalities. + + By the way, the `greet' functionality doesn't exist inside +`centos-art.sh' script yet. Would you like to create it? + +3.49.3 Usage +------------ + +3.49.3.1 Global variables +......................... + +The following global variables of `centos-art.sh' script, are available +for you to use inside specific functions: + + -- Variable: TEXTDOMAIN + Default domain used to retrieve translated messages. This value is + set in `initFunctions.sh' and shouldn't be changed. + + -- Variable: TEXTDOMAINDIR + Default directory used to retrieve translated messages. This value + is set in `initFunctions.sh' and shouldn't be changed. + + -- Variable: FUNCNAM + Define function name. + + Function names associate sets of actions. There is one set of + actions for each unique function name inside `centos-art.sh' + script. + + Dunction names are passed as first argument in `centos-art.sh' + command-line interface. For example, in the command `centos-art + render --entry=path/to/dir --filter=regex', the ACTION passed to + `centos-art.sh' script is `render'. + + When first argument is not provided, the `centos-art.sh' script + immediatly ends its execution. + + -- Variable: FUNCDIR + + -- Variable: FUNCDIRNAME + + -- Variable: FUNCSCRIPT + + -- Variable: FUNCCONFIG + + -- Variable: ACTIONNAM + Define action name. + + Each action name identifies an specific action to perform, inside + an specific function. + + Action name names aare passed as second argument in + `centos-art.sh' command-line interface. For example, in the + command `centos-art render --entry=path/to/dir --filter=regex', + the ACTIONNAM passed to `centos-art.sh' script is `--entry'. + + When second argument is not provided, the `centos-art.sh' script + immediatly ends its execution. + + -- Variable: ACTIONVAL + Define action value. + + Action values are associated to just one action name. Action values + contain the working copy entry over which its associated action + will be performed in. Working copy entries can be files or + directories inside the working copy. + + -- Variable: REGEX + Define regular expression used as pattern to build the list of + files to process. + + By default, REGEX variable is set to `.+' to match all files. + + Functions that need to build a list of files to process use the + option `--filter' to redefine REGEX variable default value, and + so, control the amount of files to process. + + -- Variable: ARGUMENTS + Define optional arguments. + + Optional arguments, inside `centos-art.sh' script, are considered + as all command-line arguments passed to `centos-art.sh' script, + from third argument position on. For example, in the command + `centos-art render --entry=path/to/dir --filter=regex' , the + optional arguments are from `--filter=regex' argument on. + + Optional arguments are parsed using `getopt' command through the + following base construction: + + + # Define short options we want to support. + local ARGSS="" + + # Define long options we want to support. + local ARGSL="filter:,to:" + + # Parse arguments using getopt(1) command parser. + cli_doParseArguments + + # Reset positional parameters using output from (getopt) argument + # parser. + eval set -- "$ARGUMENTS" + + # Define action to take for each option passed. + while true; do + case "$1" in + --filter ) + REGEX="$2" + shift 2 + ;; + --to ) + TARGET="$2" + shift 2 + ;; + * ) + break + esac + done + + Optional arguments provide support to command options inside + `centos-art.sh' script. For instance, consider the Subversion + (`svn') command, where there are many options (e.g., `copy', + `delete', `move', etc), and inside each option there are several + modifiers (e.g., `--revision', `--message', `--username', etc.) + that can be combined one another in their short or long variants. + + The ARGUMENTS variable is used to store arguments passed from + command-line for later use inside `centos-art.sh' script. Storing + arguments is specially useful when we want to run a command with + some specific options from them. Consider the following command: + + + centos-art path --copy=SOURCE --to=TARGET --message="The commit message goes here." --username='johndoe' + + In the above command, the `--message', and `--username' options + are specific to `svn copy' command. In such cases, options are not + interpreted by `centos-art.sh' script itself. Instead, the + `centos-art.sh' script uses `getopt' to retrive them and store + them in the ARGUMENTS variable for later use, as described in the + following command: + + + # Build subversion command to duplicate locations inside the + # workstation. + eval svn copy $SOURCE $TARGET --quiet $ARGUMENTS + + When `getopt' parses ARGUMENTS, we may use short options (e.g., + `-m') or long options (e.g., `--message'). When we use short + options, arguments are separated by one space from the option + (e.g., `-m 'This is a commit message.''). When we use long + options arguments are separated by an equal sign (`=') (e.g., + `--message='This is a commit message''). + + In order for `getopt' to parse ARGUMENTS correctly, it is required + to provide the short and long definition of options that will be + passed or at least supported by the command performing the final + action the function script exists for. + + As convenction, inside `centos-art.sh' script, short option + definitions are set in the ARGSS variable; and long option + definitions are set in the ARGSL variable. + + When you define short and long options, it may be needed to define + which of these option arguments are required and which not. To + define an option argument as required, you need to set one colon + `:' after the option definition (e.g., `-o m: -l message:'). On + the other hand, to define an option argument as not required, you + need to set two colons `::' after the option definition (e.g., `-o + m:: -l message::'). + + -- Variable: EDITOR + Default text editor. + + The `centos-art.sh' script uses default text `EDITOR' to edit + pre-commit subversion messages, translation files, configuration + files, script files, and similar text-based files. + + If `EDITOR' environment variable is not set, `centos-art.sh' + script uses `/usr/bin/vim' as default text editor. Otherwise, the + following values are recognized by `centos-art.sh' script: + + * `/usr/bin/vim' + + * `/usr/bin/emacs' + + * `/usr/bin/nano' + + If no one of these values is set in `EDITOR' environment variable, + `centos-art.sh' uses `/usr/bin/vim' text editor by default. + +3.49.3.2 Global functions +......................... + +Function scripts stored directly under `trunk/Scripts/Bash/Functions/' +directory are used to define global functions. Global functions can be +used inside action specific functionalities and or even be reused +inside themselves. This section provides introductory information to +global functions you can use inside `centos-art.sh' script. + + -- Function: cli_checkActionArguments + Validate action value (ACTIONVAL) variable. + + The action value variable can take one of the following values: + + 1. Path to one directory inside the local working copy, + + 2. Path to one file inside the local working copy, + + If another value different from that specified above is passed to + action value variable, the `centos-art.sh' script prints an error + message and ends script execution. + + -- Function: cli_checkFiles FILE [TYPE] + Verify file existence. + + `cli_checkFiles' receives a FILE absolute path and performs file + verification as specified in TYPE. When TYPE is not specified, + `cli_checkFiles' verifies FILE existence, no matter what kind of + file it be. If TYPE is specified, use one of the following values: + + `d' + `directory' + Ends script execution if FILE is not a directory. + + When you verify directories with cli_checkFiles, if directory + doesn't exist, `centos-art.sh' script asks you for + confirmation in order to create that directory. If you answer + positively, `centos-art.sh' script creates that directory and + continues script flows normally. Otherwise, if you answer + negatively, `centos-art.sh' ends script execution with an + error and documentation message. + + `f' + + `regular-file' + Ends script execution if FILE is not a regular file. + + `h' + `symbolic-link' + Ends script execution if FILE is not a symbolic link. + + `x' + `execution' + Ends script execution if FILE is not executable. + + `fh' + Ends script execution if FILE is neither a regular file nor a + symbolic link. + + `fd' + Ends script execution if FILE is neither a regular file nor a + directory. + + `isInWorkingCopy' + Ends script execution if FILE is not inside the working copy. + + As default behaviour, if FILE passes all verifications, + `centos-art.sh' script continues with its normal flow. + + -- Function: cli_commitRepoChanges [LOCATION] + Syncronize changes between repository and working copy. + + The `cli_commitRepoChanges' function brings changes from the + central repository down to the working copy--using `svn update'--, + checks the working copy changes--using `svn status' command--, + prints status report--using both `svn update' and `svn status' + commands output, and finally, commits recent changes from the + working copy up to the repository--using `svn commit' command--. + + Previous to commit the working copy changes up to the central + repository, the `cli_commitRepoChanges' function asks you to + verify changes--using `svn diff' command--, and later, another + confirmation question is shown to be sure you really want to + commit changes up to central repository. + + If LOCATION argument is not specified, the value of ACTIONVAL + variable is used as reference instead. + + + ---------------------------------------------------------------------- + --> Bringing changes from the repository into the working copy + --> Checking changes in the working copy + ---------------------------------------------------------------------- + Added 0 file from the repository. + Deleted 0 file from the repository. + Updated 0 file from the repository. + Conflicted 0 file from the repository. + Merged 0 file from the repository. + Modified 4 files from the working copy. + Unversioned 0 file from the working copy. + Deleted 0 file from the working copy. + Added 0 file from the working copy. + ---------------------------------------------------------------------- + + Figure 3.3: The `cli_commitRepoChanges' function output. + + Call the `cli_commitRepoChanges' function before or/and after + calling functions that modify files or directories inside the + working copy as you may need to. + + -- Function: cli_doParseArguments + Redefine arguments (ARGUMENTS) global variable using `getopt' + command output. For more information about how to use + `cli_doParseArguments' function, see ARGUMENTS variable + description above. + + -- Function: cli_doParseArgumentsReDef $@ + Initialize/reset arguments (ARGUMENTS) global variable using + positional parameters variable ($@) as reference. + + When we work inside function definitions, positional parameters are + reset to the last function definition positional parameters. If + you need to redefine positional parameters from one specific + function, you need to call `cli_doParseArgumentsReDef' with the + positional parameters variable ($@), set as first argument, to that + specific function you want to redefine positional parameters at. + + -- Function: cli_getArguments + Initialize function name (FUNCNAM), action name (ACTIONNAM), and + action value (ACTIONVAL) global variables, using positional + parameters passed in $@ variable. + + The `cli_getArguments' function is called from `cli.sh' function + script, using `cli' function positional parameters (i.e., the + positional parameters passed as arguments in the command-line) as + first function argument. + + Once command-line positional parameters are accesible to + `centos-art.sh' script execution evironment, `cli_getArguments' + uses regular expression to retrive action variables from first and + second argument. The first argument defines the value used as + function name (FUNCNAM), and the second argument defines both + values used as action name (ACTIONNAM) and action value + (ACTIONVAL), respectively. + + The first argument is a word in lower case. This word specifies the + name of the functionality you want to use (e.g., `render' to + render images, `manual' to work on documentation, and so on.) + + The second argument has a long option style (e.g., + `--option=value'). The `--option' represents the action name + (ACTIONNAM), and the characters inbetween the equal sign (`=') and + the first space character, are considered as the action value + (ACTIONVAL). In order to provide action values with space + characters inbetween you need to enclose action value with quotes + like in `--option='This is long value with spaces inbetween''. + Generally, action values are used to specify paths over which the + action name acts on. + + Once action related variables (i.e., FUNCNAM, ACTIONNAM, and + ACTIONVAL) are defined and validated, `cli_getArguments' shifts + the positional arguments to remove the first two arguments passed + (i.e., those used to retrive action related variables) and + redefine the arguments (ARGUMENTS) global variable with the new + positional parameters information. + + -- Function: cli_getFunctions + Initialize funtionalities supported by `centos-art.sh' script. + + Functionalities supported by `centos-art.sh' script are organized + in functionality directories under `trunk/Scripts/Bash/Functions/' + directory. Each functionality directory stores function scripts to + the functionality such directory was created for. Function scripts + contain function definitions. Function definitions contain + several commands focused on achieving one specific task only + (i.e., the one such functionality was created for). + + In order for `centos-art.sh' script to recognize a functionality, + such functionality needs to be stored under + `trunk/Scripts/Bash/Functions/' in a directory written capitalized + (i.e., the whole name is written in lowercase except the first + character which is in uppercase). The directory where one specific + functionality is stored is known as the `functionality directory'. + + Inside each functionality directory, the functionalty itself is + implemented through function scripts. Function scripts are + organized in files independently one another and written in + `camelCase' format with the function name as prefix. Separation + between prefix and description is done using underscore (`_') + character. + + In order for `centos-art.sh' script to load functionalities + correctly, function definition inside function scripts should be + set using the `function' reserved word, just as in the following + example: + + + function prefix_doSomething { + + # Do something here... + + } + + The above function definition is just a convenction we use, in + order to make identification of function names easier read and + automate by `centos-art.sh' script initialization commands, once + `centos-art.sh' script determines which functionality directory to + use. Specifically, in order to initialize and export functions, + `centos-art.sh' script executes all function scripts inside the + functionality directory, and later `grep' on them using a regular + expression pattern, where the `function' reserved word is used as + reference to retrive the function names and export them to + `centos-art.sh' script execution environment, and so, make + function definitions --from function scripts inside the + functionality directory-- available for further calls. + + If the functionality specified in the command-line first argument + doesn't have a functionality directory, `centos-art.sh' script + considers the functionality provided in the command-line as invalid + functionality and immediatly stops script execution with an error + message. + + In order to keep visual consistency among function scripts, please + consider using the following function script design model as + template for your own function scripts: + + + #!/bin/bash + # + # prefix_doSomething.sh -- This function illustrates function scripts + # design model you can use to create your own function scripts inside + # centos-art.sh script. + # + # Copyright (C) YEAR YOURFULLNAME + # + # This program is free software; you can redistribute it and/or modify + # it under the terms of the GNU General Public License as published by + # the Free Software Foundation; either version 2 of the License, or + # (at your option) any later version. + # + # This program is distributed in the hope that it will be useful, but + # WITHOUT ANY WARRANTY; without even the implied warranty of + # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + # General Public License for more details. + # + # You should have received a copy of the GNU General Public License + # along with this program; if not, write to the Free Software + # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 + # USA. + # + # ---------------------------------------------------------------------- + # $Id$ + # ---------------------------------------------------------------------- + + function prefix_doSomething { + + # Do something here... + + } + + -- Function: cli_getCountryCodes [FILTER] + Output country codes supported by `centos-art.sh' script. + + The `cli_getCountryCodes' function outputs a list with country + codes as defined in ISO3166 standard. When FILTER is provided, + `cli_getCountryCodes' outputs country codes that match FILTER + regular expression pattern. + + -- Function: cli_getCountryName [FILTER] + Outputs country name supported by `centos-art.sh' script. + + The `cli_getCountryName' function reads one language locale code + in the format LL_CC and outputs the name of its related country as + in ISO3166. If filter is specified, `cli_getCountryName' returns + the country name that matches the locale code specified in FILTER, + exactly. + + -- Function: cli_getCurrentLocale + Output current locale used by `centos-art.sh' script. + + The `cli_getCurrentLocale' function uses `LANG' environment + variable to build a locale pattern that is later applied to + `cli_getLocales' function output in order to return the current + locale that `centos-art.sh' script works with. + + The current locale information, returned by + `cli_getCurrentLocale', is output from more specific to less + specific. For example, if `en_GB' locale exists in + `cli_getLocales' function output, the `en_GB' locale would take + precedence before `en' locale. + + Locale precedence selection is quite important in order to define + the locale type we use for message translations. For example, if + `en_GB' is used, we are also saying that the common language + specification for English language (i.e., `en') is no longer used. + Instead, we are using English non-common country-specific language + specifications like `en_AU', `en_BW', `en_GB', `en_US', etc., for + message translations. + + Use `cli_getCurrentLocale' function to know what current locale + information to use inside `centos-art.sh' script. + + -- Function: cli_getFilesList [LOCATION] + Output list of files to process. + + The `cli_getFilesList' function uses LOCATION variable as source + location to build a list of files just as specified by regular + expression (REGEX) global variable. Essentially, what the + `cli_getFilesList' function does is using `find' command to look + for files in the location (LOCATION) just as posix-egrep regular + expression (REGEX) specifies. + + If LOCATION is not specified when `cli_getFilesList' function is + called, the action value (ACTIONVAL) global variable is used as + location value instead. + + By default, if the regular expression (REGEX) global variable is + not redefined after its first definition in the `cli' function, + all files that match default regular expression value (i.e., `.+') + will be added to the list of files to process. Otherwise, if you + redefine the regular expression global variable after its first + definition in the `cli' function and before calling + `cli_getFilesList' function, the last value you specifed is used + instead. + + When you need to customize the regular expression (REGEX) global + variable value inside a function, do not redefine the global + variable (at least you be absolutly convinced you need to). + Instead, set the regular expression global variable as `local' to + the function you need a customized regular expression value for. + If we don't redefine the regular expression global variable as + local to the function, or use another name for the regular + expression variable (which is not very convenient in order to keep + the amount of names to remember low), you may experiment undesired + concantenation issues that make your regular expression to be + something different from that you expect them to be, specially if + the function where you are doing the variable redefinition is + called several times during the same script execution. + + As result, the `cli_getFilesList' re-defines the value of FILES + variable with the list of files the `find' command returned. As + example, consider the following construction: + + + function prefix_doSomething { + + # Initialize the list of files to process. + local FILES='' + + # Initialize location. + local LOCATION=/home/centos/artwork/trunk/Identity/Themes/Models/Default + + # Re-define regular expression to match scalable vector graphic + # files only. Note how we use the global value of REGEX to build a + # new local REGEX value here. + local REGEX="${REGEX}.*\.(svgz|svg)" + + # Redefine list of files to process. + cli_getFilesList $LOCATION + + # Process list of files. + for FILE in $FILES;do + cli_printMessages "$FILE" 'AsResponseLine' + # Do something else here on... + done + + } + + + -- Function: cli_getLangCodes [FILTER] + Outputs language codes supported by `centos-art.sh' script. + + `cli_getLangCodes' function outputs a list of language codes as + defined in ISO639 standard. When FILTER is provided, + `cli_getLangCodes' outputs language codes that match FILTER + regular expression pattern. + + -- Function: cli_getLangName [FILTER] + Outputs language names supported by `centos-art.sh' script. + + `cli_getLangName' function reads one language locale code in the + format LL_CC and outputs the language related name as in ISO639. If + filter is specified, `cli_getLangName' returns the language name + that matches the locale code specified in FILTER, exactly. + + -- Function: cli_getLocales + Output locale codes supported by `centos-art.sh' script. + + Occasionally, you use `cli_getLocales' function to add locale + information in non-common country-specific language (`LL_CC') + format for those languages (e.g., `bn_IN', `pt_BR', etc.) which + locale differences cannot be solved using common language + specifications (`LL') into one unique common locale specification + (e.g., `bn', `pt', etc.). + + -- Function: cli_getRepoName NAME TYPE + Sanitate file names. + + Inside `centos-art.sh' script, specific functionalities rely both + in `cli_getRepoName' and repository file system organization to + achieve their goals. Consider `cli_getRepoName' function as + central place to manage file name convenctions for other functions + inside `centos-art.sh' script. + + *Important* `cli_getRepoName' function doesn't verify file or + directory existence, for that purpose use `cli_checkFiles' + function instead. + + The NAME variable contains the file name or directory name you + want to sanitate. + + The TYPE variable specifies what type of sanitation you want to + perform on NAME. The TYPE can be one of the following values: + + `d' + `directory' + Sanitate directory NAMEs. + + `f' + + `regular-file' + Sanitate regular file NAMEs. + + Use `cli_getRepoName' function to sanitate file names and + directory names before their utilization. + + Use `cli_getRepoName' when you need to change file name + convenctions inside `centos-art.sh' script. + + When we change file name convenctions inside `cli_getRepoName' + what we are really changing is the way functions interpret + repository file system organization. Notice that when we change a + file name (e.g., a function name), it is necessary to update all + files where such file name is placed on. This may require a + massive substitution inside the repository, each time we change + name convenctions in the repository (-- *Removed*(pxref:trunk + Scripts Bash Functions Path) --, for more information). + + -- Function: cli_getRepoStatus [LOCATION] + Request repository status. + + This function requests the status of a LOCATION inside the working + copy using the `svn status' command and returns the first + character in the output line, just as described in `svn help + status'. If LOCATION is not a regular file or a directory, inside + the working copy, the `centos-art.sh' script prints a message and + ends its execution. + + Use this function to perform verifications based a repository + LOCATION status. + + -- Function: cli_getTemporalFile NAME + Output absolute path to temporal file NAME. + + The `cli_getTemporalFile' function uses `/tmp' directory as source + location to store temporal files, the `centos-art.sh' script name, + and a random identification string to let you run more than one + `centos-art.sh' script simultaneously on the same user session. + For example, due the following temporal file defintion: + + + cli_getTemporalFile $FILE + + If FILE name is `instance.svg' and the unique random string is + `f16f7b51-ac12-4b7f-9e66-72df847f12de', the final temporal file, + built from previous temporal file definition, would be: + + + /tmp/centos-art.sh-f16f7b51-ac12-4b7f-9e66-72df847f12de-instance.svg + + When you use the `cli_getTemporalFile' function to create temporal + files, be sure to remove temporal files created once you've ended + up with them. For example, consider the following construction: + + + for FILE in $FILES;do + + # Initialize temporal instance of file. + INSTANCE=$(cli_getTemporalFile $FILE) + + # Do something ... + + # Remove temporal instance of file. + if [[ -f $INSTANCE ]];then + rm $INSTANCE + fi + + done + + Use the `cli_getTemporalFile' function whenever you need to create + temporal files inside `centos-art.sh' script. + + -- Function: cli_getThemeName + Output theme name. + + In order for `cli_getThemeName' function to extract theme name + correctly, the ACTIONVAL variable must contain a directory path + under `trunk/Identity/Themes/Motifs/' directory structure. + Otherwise, `cli_getThemeName' returns an empty string. + + -- Function: cli_printMessage MESSAGE [FORMAT] + Define standard output message definition supported by + `centos-art.sh' script. + + When FORMAT is not specified, `cli_printMessage' outputs + information just as it was passed in MESSAGE variable. Otherwise, + FORMAT can take one of the following values: + + `AsHeadingLine' + To print heading messages. + ---------------------------------------------------------------------- + $MESSAGE + ---------------------------------------------------------------------- + + `AsWarningLine' + To print warning messages. + ---------------------------------------------------------------------- + WARNING: $MESSAGE + ---------------------------------------------------------------------- + + `AsNoteLine' + To print note messages. + ---------------------------------------------------------------------- + NOTE: $MESSAGE + ---------------------------------------------------------------------- + + `AsUpdatingLine' + To print `Updating' messages on two-columns format. + Updating $MESSAGE + + `AsRemovingLine' + To print `Removing' messages on two-columns format. + Removing $MESSAGE + + `AsCheckingLine' + To print `Checking' messages on two-columns format. + Checking $MESSAGE + + `AsCreatingLine' + To print `Creating' messages on two-columns format. + Creating $MESSAGE + + `AsSavedAsLine' + To print `Saved as' messages on two-columns format. + Saved as $MESSAGE + + `AsLinkToLine' + To print `Linked to' messages on two-columns format. + Linked to $MESSAGE + + `AsMovedToLine' + To print `Moved to' messages on two-columns format. + Moved to $MESSAGE + + `AsTranslationLine' + To print `Translation' messages on two-columns format. + Translation $MESSAGE + + `AsConfigurationLine' + To print `Configuration' messages on two-columns format. + Configuration $MESSAGE + + `AsResponseLine' + To print response messages on one-column format. + --> $MESSAGE + + `AsRequestLine' + To print request messages on one-column format. Request + messages output messages with one colon (`:') and without + trailing newline (`\n') at message end. + $MESSAGE: + + `AsYesOrNoRequestLine' + To print `yes or no' request messages on one-column format. If + something different from `y' is answered (when using + `en_US.UTF-8' locale), script execution ends immediatly. + + + $MESSAGE [y/N]: + + When we use `centos-art.sh' script in a locale different from + `en_US.UTF-8', confirmation answer may be different from `y'. + For example, if you use `es_ES.UTF-8' locale, the + confirmation question would look like: + + + $MESSAGE [s/N]: + + and the confirmation answer would be `s', as it is on Spanish + `sí' word. + + Definition of which confirmation word to use is set on + translation messages for your specific locale information. -- + *Removed*(xref:trunk Scripts Bash Functions Locale) --, for + more information about locale-specific translation messages. + + `AsToKnowMoreLine' + To standardize `to know more, run the following command:' + messages. When the `AsToKnowMoreLine' option is used, the + MESSAGE value should be set to `"$(caller)"'. `caller' is a + Bash builtin that returns the context of the current + subroutine call. `AsToKnowMoreLine' option uses `caller' + builtin output to build documentation entries dynamically. + + + ---------------------------------------------------------------------- + To know more, run the following command: + centos-art manual --read='path/to/dir' + ---------------------------------------------------------------------- + + Use `AsToKnowMoreLine' option after errors and for intentional + script termination. + + `AsRegularLine' + To standardize regular messages on one-column format. + + When MESSAGE contains a colon inside (e.g., `description: + message'), the `cli_printMessage' function outputs MESSAGE on + two-columns format. + + Use `cli_printMessage' function whenever you need to output + information from `centos-art.sh' script. + + *Tip* To improve two-columns format, change the following + file: + trunk/Scripts/Bash/Styles/output_forTwoColumns.awk + +3.49.3.3 Specific functions +........................... + +The following specific functions of `centos-art.sh' script, are +available for you to use: + +3.49.4 See also +--------------- + +3.50 trunk/Scripts/Bash/Cli/Functions/Help +========================================== + +3.50.1 Goals +------------ + + * ... + +3.50.2 Description +------------------ + + * ... + +3.50.3 Usage +------------ + + * ... + +3.50.4 See also +--------------- + +3.51 trunk/Scripts/Bash/Cli/Functions/Html +========================================== + +3.51.1 Goals +------------ + + * ... + +3.51.2 Description +------------------ + + * ... + +3.51.3 Usage +------------ + + * ... + +3.51.4 See also +--------------- + +3.52 trunk/Scripts/Bash/Cli/Functions/Locale +============================================ + +3.52.1 Goals +------------ + + * ... + +3.52.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 finishd PO file edition and quit text editor, the +`centos-art' command creates the related machine object in the location +`$CLI_LANG/LC_MESSAGES/$TEXTDOMAIN.mo'. + + At this point, all translations you made in the PO file should be +available to your language when runing `centos-art.sh' script. + + In order to make the `centos-art.sh' internationalization, the +`centos-art.sh' script was modified as described in the `gettext' info +documentation (`info gettext'). You can find such modifications in the +following files: + + * `trunk/Scripts/Bash/initFunctions.sh' + + * `trunk/Scripts/Bash/Functions/Help/cli_localeMessages.sh' + + * `trunk/Scripts/Bash/Functions/Help/cli_localeMessagesStatus.sh' + + * ... + +3.52.3 Usage +------------ + +`centos-art locale --edit' + Use this command to translate command-line interface output + messages in the current system locale you are using (as specified + in `LANG' environment variable). + +`centos-art locale --list' + Use this command to see the command-line interface locale report. + +3.52.4 See also +--------------- + +3.53 trunk/Scripts/Bash/Cli/Functions/Manual +============================================ + +3.53.1 Goals +------------ + + * ... + +3.53.2 Description +------------------ + + * ... + +3.53.3 Usage +------------ + + * ... + +3.53.4 See also +--------------- + +3.54 trunk/Scripts/Bash/Cli/Functions/Path +========================================== + +3.54.1 Goals +------------ + +This section exists to organize files related to `path' +functiontionality. The `path' functionality standardizes movement, +syncronization, branching, tagging, and general file maintainance +inside the repository. + +3.54.2 Description +------------------ + +_"CentOS like trees, has roots, trunk, branches, leaves and flowers. +Day by day they work together in freedom, ruled by the laws of nature +and open standards, to show the beauty of its existence."_ + +3.54.2.1 Repository layout +.......................... + +The repository layout describes organization of files and directories +inside the repository. The repository layout provides the standard +backend required for automation scripts to work correctly. If such +layout changes unexpectedly, automation scripts may confuse themselves +and stop doing what we expect from them to do. + + As convenction, inside CentOS Artwork Repository, we organize files +and directories related to CentOS corporate visual identity under three +top level directories named: `trunk/', `branches/', and `tags/'. + + The `trunk/' directory (*note trunk::) organizes the main +development line of CentOS corporate visual identity. Inside `trunk/' +directory structure, the CentOS corporate visual identity concepts are +implemented using directories. There is one directory level for each +relevant concept inside the repository. The `trunk/' directory +structure is mainly used to perform development tasks related to CentOS +corporate visual identity. + + The `branches/' directory (*note branches::) oranizes parallel +development lines to `trunk/' directory. The `branches/' directory is +used to set points in time where develpment lines are devided one from +another taking separte and idependent lives that share a common past +from the point they were devided on. The `branches/' directory is +mainly used to perform quality assurance tasks related to CentOS +corporate visual identity. + + The `tags/' directory (*note tags::) organizes parallel frozen lines +to `branches/' directory. The parallel frozen lines are immutable, +nothing change inside them once they has been created. The `tags/' +directory is mainly used to publish final releases of CentOS corporate +visual identity. + + The CentOS Artwork Repository layout is firmly grounded on a +Subversion base. Subversion (`http://subversion.tigris.org') is a +version control system, which allows you to keep old versions of files +and directories (usually source code), keep a log of who, when, and why +changes occurred, etc., like CVS, RCS or SCCS. Subversion keeps a +single copy of the master sources. This copy is called the source +"repository"; it contains all the information to permit extracting +previous versions of those files at any time. + +3.54.2.2 Repository name convenctions +..................................... + +Repository name convenctions help us to maintain consistency of names +inside the repository. + + Repository name convenctions are applied to files and directories +inside the repository layout. As convenction, inside the repository +layout, file names are all written in lowercase (`01-welcome.png', +`splash.png', `anaconda_header.png', etc.) and directory names are all +written capitalized (e.g., `Identity', `Themes', `Motifs', `TreeFlower', +etc.). + + Repository name convenctions are implemented inside the +`cli_getRepoName' function of `centos-art.sh' script. With +`cli_getRepoName' function we reduce the amount of commands and +convenctions to remember, concentrating them in just one single place +to look for fixes and improvements. + +3.54.2.3 Repository work flow +............................. + +Repository work flow describes the steps and time intervals used to +produce CentOS corporate visual identity inside CentOS Artwork +Repository. + + To illustrate repository work flow let's consider themes' development +cycle. + + Initially, we start working themes on their trunk development line +(e.g., `trunk/Identity/Themes/Motifs/TreeFlower/'), here we organize +information that cannot be produced automatically (i.e., background +images, concepts, color information, screenshots, etc.). + + Later, when theme trunk development line is considered "ready" for +implementation (e.g., all required backgrounds have been designed), we +create a branch for it (e.g., +`branches/Identity/Themes/Motifs/TreeFlower/1/'). Once the branch has +been created, we forget that branch and continue working the trunk +development line while others (e.g., an artwork quality assurance team) +test the new branch for tunning it up. + + Once the branch has been tunned up, and considered "ready" for +release, it is freezed under `tags/' directory (e.g., +`tags/Identity/Themes/Motifs/TreeFower/1.0/') for packagers, +webmasters, promoters, and anyone who needs images from that CentOS +theme the tag was created for. + + Both branches and tags, inside CentOS Artwork Repository, use +numerical values to identify themselves under the same location. +Branches start at one (i.e., `1') and increment one unit for each +branch created from the same trunk development line. Tags start at +zero (i.e., `0') and increment one unit for each tag created from the +same branch development line. + + *Convenction* Do not freeze trunk development lines using tags + directly. If you think you need to freeze a trunk development + line, create a branch for it and then freeze that branch instead. + + The trunk development line may introduce problems we cannot see +immediatly. Certainly, the high changable nature of trunk development +line complicates finding and fixing such problems. On the other hand, +the branched development lines provide a more predictable area where +only fixes/corrections to current content are commited up to repository. + + If others find and fix bugs inside the branched development line, we +could merge such changes/experiences back to trunk development line +(not visversa) in order for future branches, created from trunk, to +benefit. + + Time intervals used to create branches and tags may vary, just as +different needs may arrive. For example, consider the release schema of +CentOS distribution: one major release every 2 years, security updates +every 6 months, support for 7 years long. Each time a CentOS +distribution is released, specially if it is a major release, there is +a theme need in order to cover CentOS distribution artwork +requirements. At this point, is where CentOS Artwork Repository comes +up to scene. + + Before releasing a new major release of CentOS distribution we create +a branch for one of several theme development lines available inside +the CentOS Artwork Repository, perform quality assurance on it, and +later, freeze that branch using tags. Once a the theme branch has been +frozen (under `tags/' directory), CentOS Packagers (the persons whom +build CentOS distribution) can use that frozen branch as source +location to fulfill CentOS distribution artwork needs. The same applies +to CentOS Webmasters (the persons whom build CentOS websites), and any +other visual manifestation required by the project. + +3.54.2.4 Parallel directories +............................. + +Inside CentOS Artwork Repository, parallel directories are simple +directory entries built from a common parent directory and placed in a +location different to that, the common parent directory is placed on. +Parallel directories are useful to create branches, tags, translations, +documentation, pre-rendering configuration script, and similar +directory structures. + + Parallel directories take their structure from one unique parent +directory. Inside CentOS Artwork Repository, this unique parent +directory is under `trunk/Identity' location. The `trunk/Identity' +location must be considered the reference for whatever information you +plan to create inside the repository. + + In some circumstances, parallel directories may be created removing +uncommon information from their paths. Uncommon path information refers +to those directory levels in the path which are not common for other +parallel directories. For example, when rendering +`trunk/Identity/Themes/Motifs/TreeFlower/Distro' directory structure, +the `centos-art.sh' script removes the `Motifs/TreeFlower/' directory +levels from path, in order to build the parallel directory used to +retrived translations, and pre-rendering configuration scripts required +by `render' functionality. + + Another example of parallel directory is the documentation structure +created by `manual' functionality. This time, `centos-art.sh' script +uses parallel directory information with uncommon directory levels to +build the documentation entry required by Texinfo documentation system, +inside the repository. + + Othertimes, parallel directories may add uncommon information to +their paths. This is the case we use to create branches and tags. When +we create branches and tags, a numerical identifier is added to parallel +directory structure path. The place where the numerical identifier is +set on is relevant to corporate visual identity structure and should be +carefully considered where it will be. + + When one parent directory changes, all their related parallel +directories need to be changed too. This is required in order for +parallel directories to retain their relation with the parent directory +structure. In the other hand, parallel directories should never be +modified under no reason but to satisfy the relation to their parent +directory structure. Liberal change of parallel directories may +suppresses the conceptual idea they were initially created for; and +certainly, things may stop working the way they should do. + +3.54.2.5 Syncronizing path information +...................................... + +Parallel directories are very useful to keep repository organized but +introduce some complications. For instance, consider what would happen +to functionalities like `manual' (`trunk Scripts Bash Functions +Manual') that rely on parent directory structures to create +documentation entries (using parallel directory structures) if one of +those parent directory structures suddenly changes after the +documentation entry has been already created for it? + + In such cases, functionalities like `manual' may confuse themselves +if path information is not updated to reflect the relation with its +parent directory. Such functionalities work with parent directory +structure as reference; if a parent directory changes, the +functionalities dont't even note it because they work with the last +parent directory structure available in the repository, no matter what +it is. + + In the specific case of documentation (the `manual' functionality), +the problem mentioned above provokes that older parent directories, +already documented, remain inside documentation directory structures as +long as you get your hands into the documentation directory structure +(`trunk/Manuals') and change what must be changed to match the new +parent directory structure. + + There is no immediate way for `manual', and similar functionalities +that use parent directories as reference, to know when and how +directory movements take place inside the repository. Such information +is available only when the file movement itself takes place inside the +repository. So, is there, at the moment of moving files, when we need +to syncronize parallel directories with their unique parent directory +structure. + + *Warning* There is not support for URL reference inside + `centos-art.sh' script. The `centos-art.sh' script is designed to + work with local files inside the working copy only. + + As CentOS Artwork Repository is built over a version control system, +file movements inside the repository are considered repository changes. +In order for these repository changes to be versioned, we need to, +firstly, add changes into the version control system, commit them, and +later, perform movement actions using version control system commands. +This configuration makes possible for everyone to know about changes +details inside the repository; and if needed, revert or update them +back to a previous revision. + + Finally, once all path information has been corrected, it is time to +take care of information inside the files. For instance, considere what +would happen if you make a reference to a documentation node, and later +the documentation node you refere to is deleted. That would make +Texinfo to produce error messages at export time. So, the +`centos-art.sh' script needs to know when such changes happen, in a way +they could be noted and handled without producing errors. + +3.54.2.6 What is the right place to store it? +............................................. + +Occasionly, you may find that new corporate visual identity components +need to be added to the repository. If that is your case, the first +question you need to ask yourself, before start to create directories +blindly all over, is: What is the right place to store it? + + The CentOS Community different free support vains (see: +`http://wiki.centos.org/GettingHelp') are the best place to find +answers to your question, but going there with hands empty is not good +idea. It may give the impression you don't really care about. Instead, +consider the following suggestions to find your own comprehension and +so, make your propositions based on it. + + When we are looking for the correct place to store new files, to bear +in mind the corporate visual identity structure used inside the CentOS +Artwork Repository (*note trunk Identity::) would be probaly the best +advice we could offer, the rest is just matter of choosing appropriate +names. To illustrate this desition process let's consider the +`trunk/Identity/Themes/Motifs/TreeFlower' directory as example. It is +the trunk development line of _TreeFlower_ artistic motif. Artistic +motifs are considered part of themes, which in turn are considered part +of CentOS corporate visual identity. + + When building parent directory structures, you may find that reaching +an acceptable location may take some time, and as it uses to happen +most of time; once you've find it, that may be not a definite solution. +There are many concepts that you need to play with, in order to find a +result that match the conceptual idea you try to implement in the new +directory location. To know which these concepts are, split the +location in words and read its documentation entry from less specific +to more specific. + + For example, the `trunk/Identity/Themes/Motifs/TreeFlower' location +evolved through several months of contant work and there is no certain +it won't change in the future, even it fixes quite well the concept we +are trying to implement. The concepts used in +`trunk/Identity/Themes/Distro/Motifs/TreeFlower' location are described +in the following commands, respectively: + + +centos-art manual --read=turnk/ +centos-art manual --read=turnk/Identity/ +centos-art manual --read=turnk/Identity/Themes/ +centos-art manual --read=turnk/Identity/Themes/Motifs/ +centos-art manual --read=turnk/Identity/Themes/Motifs/TreeFlower/ + + Other location concepts can be found similary as we did above, just +change the location we used above by the one you are trying to know +concepts for. + +3.54.3 Usage +------------ + +`centos-art path --copy='SRC' --to='DST'' + Copy `SRC' to `DST' and schedule `DST' for addition (with + history). In this command, `SRC' and `DST' are both working copy + (WC) entries. + +`centos-art path --delete='SRC'' + Delete `DST'. In order for this command to work the file or + directory you intend to delete should be under version control + first. In this command, `SRC' is a working copy (WC) entry. + + +3.54.4 See also +--------------- + +3.55 trunk/Scripts/Bash/Cli/Functions/Render +============================================ + +The `render' functionality exists to produce both identity and +translation files on different levels of information (i.e., different +languages, release numbers, architectures, etc.). + + The `render' functionality relies on "renderable directory +structures" to produce files. Renderable directory structures can be +either "identity directory structures" or "translation directory +structures" with special directories inside. + +3.55.1 Renderable identity directory structures +----------------------------------------------- + +Renderable identity directory structures are the starting point of +identity rendition. Whenever we want to render a component of CentOS +corporate visual identity, we need to point `centos-art.sh' to a +renderable identity directory structure. If such renderable identity +directory structure doesn't exist, then it is good time to create it. + + Inside the working copy, one renderable identity directory structures +represents one visual manifestation of CentOS corporate visual +identity, or said differently, each visual manifestation of CentOS +corporate visual identity should have one renderable identity directory +structure. + + Inside renderable identity directory structures, `centos-art.sh' can +render both image-based and text-based files. Specification of whether +a renderable identity directory structure produces image-based or +text-based content is a configuration action that takes place in the +pre-rendition configuration script of that renderable identity +directory structure. + + Inside renderable identity directory structures, content production +is organized in different configurations. A content production +configuration is a unique combination of the components that make an +identity directory structure renderable. One content production +configuration does one thing only (e.g., to produce untranslated +images), but it can be extended (e.g., adding translation files) to +achieve different needs (e.g., to produce translated images). + +3.55.1.1 Design template without translation +............................................ + +The design template without translation configuration is based on a +renderable identity directory structure with an empty translation +directory structure. In this configuration, one design template +produces one untranslated file. Both design templates and final +untranslated files share the same file name, but they differ one +another in file-type and file-extension. + + For example, to produce images without translations (there is no much +use in producing text-based files without translations), consider the +following configuration: + +*One renderable identity directory structure:* + In this example we used `Identity/Path/To/Dir' as the identity + component we want to produce untranslated images for. Identity + components can be either under `trunk/' or `branches/' directory + structure. + + The identity component (i.e., `Identity/Path/To/Dir', in this + case) is also the bond component we use to connect the identity + directory structures with their respective auxiliar directories + (i.e., translation directory structres and pre-rendition + configuration structures). The bond component is the path + convenction that `centos-art.sh' uses to know where to look for + related translations, configuration scripts and whatever auxiliar + thing a renderable directory structure may need to have. + + + | The bond component + |----------------->| + trunk/Identity/Path/To/Dir <-- Renderable identity directory structure. + |-- Tpl <-- Design template directory. + | `-- file.svg <-- Design template file. + `-- Img <-- Directory used to store final files. + `-- file.png <-- Final image-based file produced from + design template file. + + Inside design template directory, design template files are based + on SVG (Scalable Vector Graphics) and use the extension `.svg'. + Design template files can be organized using several directory + levels to create a simple but extensible configuration, specially + if translated images are not required. + + In order for SVG (Scalable Vector Graphics) files to be considered + "design template" files, they should be placed under the design + template directory and to have set a `CENTOSARTWORK' object id + inside. + + The `CENTOSARTWORK' word itself is a convenction name we use to + define which object/design area, inside a design template, the + `centos-art.sh' script will use to export as PNG (Portable Network + Graphic) image at rendition time. Whithout such object id + specification, the `centos-art.sh' script cannot know what + object/design area you (as designer) want to export as PNG + (Portable Network Graphic) image file. + + *Note* At rendition time, the content of `Img/' directory + structure is produced by `centos-art.sh' automatically. + + When a renderable identity directory structure is configured to + produce image-based content, `centos-art.sh' produces PNG + (Portable Network Graphics) files with the `.png' extension. Once + the base image format has been produced, it is possible for + `centos-art.sh' to use it in order to automatically create other + image formats that may be needed (-- *Removed*(pxref:trunk Scripts + Bash Functions Render Config) --). + + Inside the working copy, you can find an example of "design + template without translation" configuration at + `trunk/Identity/Models/'. + + *Note trunk Identity::, for more information. + +*One translation directory structure:* + In order for an identity entry to be considered an identity + renderable directory structure, it should have a translation + entry. The content of the translation entry is relevant to + determine how to process the identity renderable directory entry. + + If the translation entry is empty (i.e., there is no file inside + it), `centos-art.sh' interprets the identity renderable directory + structure as a "design templates without translation" + configuration. + + + | The bond component + |----------------->| + trunk/Translations/Identity/Path/To/Dir + `-- (empty) + + If the translation entry is not empty, `centos-art.sh' can + interpret the identity renderable directory structure as one of the + following configurations: "design template with translation + (one-to-one)" or "design template with translation (optimized)". + Which one of these configurations is used depends on the value + assigned to the matching list (MATCHINGLIST) variable in the + pre-rendition configuration script of the renderable identity + directory structure we are producing images for. + + If the matching list variable is empty (as it is by default), then + "design template with translation (one-to-one)" configuration is + used. In this configuration it is required that both design + templates and translation files have the same file names. This + way, _one_ translation files is applied to _one_ design template, + to produce _one_ translated image. + + If the matching list variable is not empty (because you redefine + it in the pre-rendition configuration script), then "design + template with translation (optimized)" configuration is used + instead. In this configuration, design templates and translation + files don't need to have the same names since such name + relationship between them is specified in the matching list + properly. + + -- *Removed*(xref:trunk Translations) --, for more information. + +*One pre-rendition configuration script:* + In order to make an identity directory structure renderable, a + pre-rendition configuration script should exist for it. The + pre-rendition configuration script specifies what type of rendition + does `centos-art.sh' will perform over the identity directory + structure and how does it do that. + + + | The bond component + |----------------->| + trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir + `-- render.conf.sh + + In this configuration the pre-rendition configuration script + (`render.conf.sh') would look like the following: + + + function render_loadConfig { + + # Define rendition actions. + ACTIONS[0]='BASE:renderImage' + + } + + Since translation directory structure is empty, `centos-art.sh' + assumes a "design template without translation" configuration to + produce untranslated images. + + To produce untranslated images, `centos-art.sh' takes one design + template and creates one temporal instance from it. Later, + `centos-art.sh' uses the temporal design template instance as + source file to export the final untranslated image. The action of + exporting images from SVG (Scalable Vector Graphics) to PNG + (Portable Network Graphics) is possible thanks to Inkscape's + command-line interface and the `CENTOSARTWORK' object id we + previously set inside design templates. + + + centos-art.sh render --identity=trunk/Identity/Path/To/Dir + ------------------------------------------------- + 0 | Execute centos-art.sh on renderable identity directory structure. + --v---------------------------------------------- + trunk/Identity/Path/To/Dir/Tpl/file.svg + ------------------------------------------------- + 1 | Create instance from design template. + --v---------------------------------------------- + /tmp/centos-art.sh-a07e824a-5953-4c21-90ae-f5e8e9781f5f-file.svg + ------------------------------------------------- + 2 | Render untranslated image from design template instance. + --v---------------------------------------------- + trunk/Identity/NewDir/Img/file.png + ------------------------------------------------- + 3 | Remove design template instance. + + Finally, when the untranslated image has been created, the temporal + design template instance is removed. At this point, + `centos-art.sh' takes the next design template and repeats the + whole production flow once again (design template by design + template), until all design templates be processed. + + -- *Removed*(xref:trunk Scripts Bash Functions Render Config) --, + for more information. + +3.55.1.2 Design template with translation (one-to-one) +...................................................... + +Producing untranslated images is fine in many cases, but not always. +Sometimes it is required to produce images in different languages and +that is something that untrasnlated image production cannot achieve. +However, if we fill its empty translation entry with translation files +(one for each design template) we extend the production flow from +untranslated image production to translated image production. + + In order for `centos-art.sh' to produce images correctly, each +design template should have one translation file and each translation +file should have one design template. Otherwise, if there is a missing +design template or a missing translation file, `centos-art.sh' will not +produce the final image related to the missing component. + + In order for `centos-art.sh' to know which is the relation between +translation files and design templates the translation directory +structure is taken as reference. For example, the +`trunk/Translations/Identity/Path/To/Dir/file.sed' translation file +does match `trunk/Identity/Path/To/Dir/Tpl/file.svg' design template, +but it doesn't match `trunk/Identity/Path/To/Dir/File.svg' or +`trunk/Identity/Path/To/Dir/Tpl/File.svg' or +`trunk/Identity/Path/To/Dir/Tpl/SubDir/file.svg' design templates. + + The pre-rendition configuration script used to produce untranslated +images is the same we use to produce translated images. There is no +need to modify it. So, as we are using the same pre-rendition +configuration script, we can say that translated image production is +somehow an extended/improved version of untranslated image production. + + *Note* If we use no translation file in the translation entry + (i.e., an empty directory), `centos-art.sh' assumes the + untranslated image production. If we fill the translation entry + with translation files, `centos-art.sh' assumes the translated + image production. + + To produce final images, `centos-art.sh' applies one translation +file to one design template and produce a translated design template +instance. Later, `centos-art.sh' uses the translated template instance +to produce the translated image. Finally, when the translated image has +been produced, `centos-art.sh' removes the translated design template +instance. This production flow is repeated for each translation file +available in the translatio entry. + + +centos-art.sh render --identity=trunk/Identity/Path/To/Dir +------------------------------------------------- +0 | Execute centos-art.sh on directory structure. +--v---------------------------------------------- +trunk/Translations/Identity/Path/To/Dir/file.sed +------------------------------------------------- +1 | Apply translation to design template. +--v---------------------------------------------- +trunk/Identity/Path/To/Dir/Tpl/file.svg +------------------------------------------------- +2 | Create design template instance. +--v---------------------------------------------- +/tmp/centos-art.sh-a07e824a-5953-4c21-90ae-f5e8e9781f5f-file.svg +------------------------------------------------- +3 | Render PNG image from template instance. +--v---------------------------------------------- +trunk/Identity/NewDir/Img/file.png +------------------------------------------------- +4 | Remove design template instance. + +3.55.1.3 Design template with translation (optimized) +..................................................... + +Producing translated images satisfies almost all our production images +needs, but there is still a pitfall in them. In order to produce +translated images as in the "one-to-one" configuration describes +previously, it is required that one translation file has one design +template. That's useful in many cases, but what would happen if we need +to apply many different translation files to the same design template? +Should we have to duplicate the same design template file for each +translation file, in order to satisfy the "one-to-one" relation? What +if we need to assign translation files to design templates arbitrarily? + + Certenly, that's something the "one-to-one" configuration cannot +handle. So, that's why we had to "optimize" it. The optimized +configuration consists on using a matching list (MATCHINGLIST) variable +that specifies the relationship between translation files and design +templates in an arbitrary way. Using such matching list between +translation files and design templates let us use as many assignment +combinations as translation files and design templates we are working +with. + + The MATCHINGLIST variable is set in the pre-rendition configuration +script of the component we want to produce images for. By default, the +MATCHINGLIST variable is empty which means no matching list is used. +Otherwise, if MATCHINGLIST variable has a value different to empty +value then, `centos-art.sh' interprets the matching list in order to +know how translation files are applied to design templates. + + For example, consider the following configuration: + +*One entry under `trunk/Identity/':* + In this configuration we want to produce three images using a + paragraph-based style, controlled by `paragraph.svg' design + template; and one image using a list-based style, controlled by + `list.svg' design template. + + + trunk/Identity/Path/To/Dir + |-- Tpl + | |-- paragraph.svg + | `-- list.svg + `-- Img + |-- 01-welcome.png + |-- 02-donate.png + |-- 03-docs.png + `-- 04-support.png + +*One entry under `trunk/Translations/':* + In order to produce translated images we need to have one + translation file for each translated image we want to produce. + Notice how translation names do match final image file names, but + how translation names do not match design template names. When we + use matching list there is no need for translation files to match + the names of design templates, such name relation is set inside + the matching list itself. + + + trunk/Translations/Identity/Path/To/Dir + |-- 01-welcome.sed + |-- 02-donate.sed + |-- 03-docs.sed + `-- 04-support.sed + +*One entry under `trunk/trunk/Scripts/Bash/Functions/Render/Config/':* + In order to produce different translated images using specific + design templates, we need to specify the relation between + translation files and design templates in a way that + `centos-art.sh' could know exactly what translation file to apply + to what design template. This relation between translation files + and design templates is set using the matching list MATCHINGLIST + variable inside the pre-rendition configuration script of the + component we want to produce images for. + + + trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir + `-- render.conf.sh + + In this configuration the pre-rendition configuration script + (`render.conf.sh') would look like the following: + + + function render_loadConfig { + + # Define rendition actions. + ACTIONS[0]='BASE:renderImage' + + # Define matching list. + MATCHINGLIST="\ + paragraph.svg:\ + 01-welcome.sed\ + 02-donate.sed\ + 04-support.sed + list.svg:\ + 03-docs.sed + " + + } + + As result, `centos-art.sh' will produce `01-welcome.png', + `02-donate.png' and `04-support.png' using the paragraph-based + design template, but `03-docs.png' using the list-based design + template. + +3.55.1.4 Design template with translation (optimized+flexibility) +................................................................. + +In the production models we've seen so far, there are design templates +to produce untranslated images and translation files which combiend +with design templates produce translated images. That may seems like +all our needs are covered, doesn't it? Well, it _almost_ does. + + Generally, we use design templates to define how final images will +look like. Generally, each renderable directory structure has one +`Tpl/' directory where we organize design templates for that identity +component. So, we can say that there is only one unique design template +definition for each identity component; or what is the same, said +differently, identity components can be produced in one way only, the +way its own design template directory specifies. This is not enough +for theme production. It is a limitation, indeed. + + Initially, to create one theme, we created one renderable directory +structure for each theme component. When we found ourselves with many +themes, and components inside them, it was obvious that the same design +model was duplicated inside each theme. As design models were +independently one another, if we changed one theme's design model, that +change was useless to other themes. So, in order to reuse design model +changes, we unified design models into one common directory structure. + + With design models unified in a common structure, another problem +rose up. As design models also had the visual style of theme components, +there was no difference between themes, so there was no apparent need +to have an independent theme directory structure for each different +theme. So, it was also needed to separate visual styles from design +models. + + At this point there are two independent worklines: one directory +structure to store design models (the final image characteristics +[i.e., dimensions, translation markers, etc.]) and one directory +structure to store visual styles (the final image visual style [i.e., +the image look and feel]). So, it is possible to handle both different +design models and different visual styles independtly one another and +later create combinations among them using `centos-art.sh'. + + For example, consider the following configuration: + +*One entry under `trunk/Identity/Themes/Models/':* + The design model entry exists to organize design model files + (similar to design templates). Both design models and design + templates are very similar; they both should have the + `CENTOSARTWORK' export id present to identify the exportation + area, translation marks, etc. However, design models do use + dynamic backgrounds inclusion while design templates don't. + + + THEMEMODEL | | The bond component + |<----| |--------------------->| + trunk/Identity/Themes/Models/Default/Distro/Anaconda/Progress/ + |-- paragraph.svg + `-- list.svg + + Inisde design models, dynamic backgrounds are required in order for + different artistic motifs to reuse common design models. Firstly, + in order to create dynamic backgrounds inside design models, we + import a bitmap to cover design model's background and later, + update design model's path information to replace fixed values to + dynamic values. + +*One entry under `trunk/Identity/Themes/Motifs/':* + The artistic motif entry defines the visual style we want to + produce images for, only. Final images (i.e., those built from + combining both design models and artistic motif backrounds) are + not stored here, but under branches directory structure. In the + artistic motif entry, we only define those images that cannot be + produced automatically by `centos-art.sh' (e.g., Backgrounds, + Color information, Screenshots, etc.). + + + Artistic motif name | | Artistic motif backgrounds + |<-------| |-------->| + trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/ + |-- Img + | |-- Png + | | |-- 510x300.png + | | `-- 510x300-final.png + | `-- Jpg + | |-- 510x300.jpg + | `-- 510x300-final.jpg + |-- Tpl + | `-- 510x300.svg + `-- Xcf + `-- 510x300.xcf + +*One entry under `trunk/Translations/':* + The translation entry specifies, by means of translation files, the + language-specific information we want to produce image for. When we + create the translation entry we don't use the name of neither + design model nor artistic motif, just the design model component + we want to produce images for. + + + | The bond component + |--------------------->| + trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ + `-- 5 + |-- en + | |-- 01-welcome.sed + | |-- 02-donate.sed + | `-- 03-docs.sed + `-- es + |-- 01-welcome.sed + |-- 02-donate.sed + `-- 03-docs.sed + +*One entry under `trunk/Scripts/Bash/Functions/Render/Config/':* + There is one pre-rendition configuration script for each theme + component. So, each time a theme component is rendered, its + pre-rendition configuration script is evaluated to teach + `centos-art.sh' how to render the component. + + + trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Distro/Anaconda/Progress/ + `-- render.conf.sh + + In this configuration the pre-rendition configuration script + (`render.conf.sh') would look like the following: + + + function render_loadConfig { + + # Define rendition actions. + ACTIONS[0]='BASE:renderImage' + + # Define matching list. + MATCHINGLIST="\ + paragraph.svg:\ + 01-welcome.sed\ + 02-donate.sed + list.svg:\ + 03-docs.sed + " + + # Deifne theme model. + THEMEMODEL='Default' + + } + + The production flow of "optimize+flexibility" configuration... + +3.55.2 Renderable translation directory structures +-------------------------------------------------- + +Translation directory structures are auxiliar structures of renderable +identity directory structures. There is one translation directory +structure for each renderable identity directory structure. Inside +translation directory structures we organize translation files used by +renderable identity directory structures that produce translated +images. Renderable identity directory structures that produce +untranslated images don't use translation files, but they do use a +translation directory structure, an empty translation directory +structure, to be precise. + + In order to aliviate production of translation file, we made +translation directory structures renderable adding a template (`Tpl/') +directory structure to handle common content inside translation files. +This way, we work on translation templates and later use +`centos-art.sh' to produce specific translation files (based on +translation templates) for different information (e.g., languages, +release numbers, architectures, etc.). + + If for some reason, translation files get far from translation +templates and translation templates become incovenient to produce such +translation files then, care should be taken to avoid replacing the +content of translation files with the content of translation templates +when `centos-art.sh' is executed to produce translation files from +translation templates. + + Inside renderable translation directory structures, `centos-art.sh' +can produce text-based files only. + +3.55.3 Copying renderable directory structures +---------------------------------------------- + +A renderable layout is formed by design models, design images, +pre-rendition configuration scripts and translations files. This way, +when we say to duplicate rendition stuff we are saying to duplicate +these four directory structures (i.e., design models, design images, +pre-rendition configuration scripts, and related translations files). + + When we duplicate directories, inside `trunk/Identity' directory +structure, we need to be aware of renderable layout described above and +the source location used to perform the duplication action. The source +location is relevant to centos-art.sh script in order to determine the +required auxiliar information inside directory structures that need to +be copied too (otherwise we may end up with orphan directory structures +unable to be rendered, due the absence of required information). + + In order for a renderable directory structure to be valid, the new +directory structure copied should match the following conditions: + + 1. To have a unique directory structure under `trunk/Identity', + organized by any one of the above organizational designs above. + + 2. To have a unique directory structure under `trunk/Translations' to + store translation files. + + 3. To have a unique directory structure under + `trunk/Scripts/Bash/Functions/Render/Config' to set pre-rendition + configuration script. + + As convenction, the `render_doCopy' function uses `trunk/Identity' +directory structure as source location. Once the `trunk/Identity' +directory structure has been specified and verified, the related path +information is built from it and copied automatically to the new +location specified by FLAG_TO variable. + + Design templates + No translation: + + Command: - centos-art render -copy=trunk/Identity/Path/To/Dir +-to=trunk/Identity/NewPath/To/Dir + + Sources: - trunk/Identity/Path/To/Dir - +trunk/Translations/Identity/Path/To/Dir - +trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir + + Targets: - trunk/Identity/NewPath/To/Dir - +trunk/Translations/Identity/NewPath/To/Dir - +trunk/Scripts/Bash/Functions/Render/Config/Identity/NewPath/To/Dir + + Renderable layout 2: + + Command: - centos-art render +-copy=trunk/Identity/Themes/Motifs/TreeFlower \ +-to=trunk/Identity/Themes/Motifs/NewPath/To/Dir + + Sources: - trunk/Identity/Themes/Motifs/TreeFlower - +trunk/Translations/Identity/Themes - +trunk/Translations/Identity/Themes/Motifs/TreeFlower - +trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes - +trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/TreeFlower + + Targets: - trunk/Identity/Themes/Motifs/NewPath/To/Dir - +trunk/Translations/Identity/Themes - +trunk/Translations/Identity/Themes/Motifs/NewPath/To/Dir - +trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes - +trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewPath/To/Dir + + Notice that design models are not included in source or target +locations. This is intentional. In "Renderable layout 2", design models +live by their own, they just exist, they are there, available for any +artistic motif to use. By default `Themes/Models/Default' design model +directory structure is used, but other design models directory +structures (under Themes/Models/) can be created and used changing the +value of THEMEMODEL variable inside the pre-rendition configuration +script of the artistic motif source location you want to produce. + + Notice how translations and pre-rendition configuration scripts may +both be equal in source and target. This is because such structures are +common to all artistic motifs (the default values to use when no +specific values are provided). + + - The common directory structures are not copied or deleted. We +cannot copy a directory structure to itself. + + - The common directory structures represent the default value to use + when no specific translations and/or pre-rendition configuration +script are provided inside source location. + + - The specific directory structures, if present, are both copiable +and removable. This is, when you perform a copy or delete action from + source, that source specific auxiliar directories are transfered in +the copy action to a new location (that specified by FLAG_TO +variable). + + - When translations and/or pre-rendition configuration scripts are +found inside the source directory structure, the centos-art.sh script +loads common auxiliar directories first and later specific auxiliar +directories. This way, identity rendition of source locations can be +customized idividually over the base of common default values. + + - The specific auxiliar directories are optional. + + - The common auxiliar directories should be present always. This is, + in order to provide the information required by render functionality +(i.e., to make it functional in the more basic level of its +existence). + + Notice how the duplication process is done from `trunk/Identity' on, +not the oposite. If you try to duplicate a translation structure (or +similar auxiliar directory structures like pre-rendition configuration +scripts), the `trunk/Identity' for that translation is not created. +This limitation is impossed by the fact that many `trunk/Identity' +directory structures may reuse/share the same translation directory +structure. We cannot delete one translation (or similar) directory +structures while a related `trunk/Identity/' directory structure is +still in need of it. + + The `render_doCopy' functionality does duplicate directory structures +directly involved in rendition process only. Once such directories have +been duplicated, the functionality stops thereat. + +3.55.4 Usage +------------ + + * ... + +3.55.5 See also +--------------- + +3.56 trunk/Scripts/Bash/Cli/Functions/Render/Config +=================================================== + +3.56.1 Goals +------------ + +The `trunk/Scripts/Bash/Config' directory exists to oraganize +pre-rendering configuration scripts. + +3.56.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.56.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.56.2.2 The `render.conf.sh' translation model +............................................... + +Translation pre-rendering configuration scripts take precedence before +default translation rendering action. Translation pre-rendering actions +are useful when default translation rendering action do not fit itself +to translation entry rendering requirements. + +3.56.2.3 The `render.conf.sh' rendering actions +............................................... + +Inside both image-based and text-based identity pre-rendering +configuration scripts, we use the `ACTIONS' array variable to define +the way `centos-art.sh' script performs identity rendering. Identity +rendering is organized by one `BASE' action, and optional `POST' and +`LAST' rendering actions. + + The `BASE' action specifies what kind of rendering does the +`centos-art.sh' script will perform with the files related to the +pre-rendering configuration script. The `BASE' action is required. +Possible values to `BASE' action are either `renderImage' or +`renderText' only. + + To specify the `BASE' action you need to set the `BASE:' string +followed by one of the possible values. For example, if you want to +render images, consider the following definition of `BASE' action: + + +ACTIONS[0]='BASE:renderImage' + + Only one `BASE' action must be specified. If more than one `BASE' +action is specified, the last one is used. If no `BASE' action is +specified at all, an error is triggered and the `centos-art.sh' script +ends its execution. + + The `POST' action specifies which action to apply for each file +rendered (at the rendering time). This action is optional. You can set +many different `POST' actions to apply many different actions over the +same already rendered file. Possible values to `POST' action are +`renderFormats', `renderSyslinux', `renderGrub', etc. + + To specify the `POST' action, you need to use set the `POST:' +followed by the function name of the action you want to perform. The +exact form depends on your needs. For example, consider the following +example to produce `xpm', `jpg', and `tif' images, based on already +rendered `png' image, and also organize the produced files in +directories named as their own extensions: + + +ACTIONS[0]='BASE:renderImage' +ACTIONS[1]='POST:renderFormats: xpm jpg tif' +ACTIONS[2]='POST:groupByFormat: png xpm jpg tif' + + In the previous example, file organization takes place at the moment +of rendering, just after producing the `png' base file and before going +to the next file in the list of files to render. If you don't want to +organized the produced files in directories named as their own +extensions, just remove the `POST:groupByFormat' action line: + + +ACTIONS[0]='BASE:renderImage' +ACTIONS[1]='POST:renderFormats: xpm jpg tif' + + The `LAST' action specifies which actions to apply once the last +file in the list of files to process has been rendered. The `LAST' +action is optional. Possible values for `LAST' actions may be +`groupByFormat', `renderGdmTgz', etc. + + *Note* -- *Removed*(xref: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.56.3 Usage +------------ + +Use the following commands to administer both identity and translation +pre-rendering configuration scripts: + +`centos-art config --create='path/to/dir/'' + Use this command to create `path/to/dir' related pre-rendering + configuration script. + +`centos-art config --edit='path/to/dir/'' + Use this command to edit `path/to/dir' related pre-rendering + configuration script. + +`centos-art config --read='path/to/dir/'' + Use this command to read `path/to/dir' related pre-rendering + configuration script. + +`centos-art config --remove='path/to/dir/'' + 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.56.4 See also +--------------- + +3.57 trunk/Scripts/Bash/Cli/Functions/Shell +=========================================== + +3.57.1 Goals +------------ + +This section exists to organize files related to `shell' functionality +of `centos-art.sh' script. + +3.57.2 Description +------------------ + +The `shell' functionality of `centos-art.sh' script helps you to +maintain bash scripts inside repository. For example, suppose you've +created many functionalities for `centos-art.sh' script, and you want +to use a common copyright and license note for consistency in all your +script files. If you have a bunch of files, doing this one by one +wouldn't be a big deal. In contrast, if the amount of files grows, +updating the copyright and license note for all of them would be a task +rather tedious. The `shell' functionality exists to solve maintainance +tasks just as the one previously mentioned. + + When you use `shell' functionality to update copyright inside script +files, it is required that your script files contain (at least) the +following top commentary structure: + + + 1| #!/bin/bash + 2| # + 3| # doSomething.sh -- The function description goes here. + 4| # + 5| # Copyright + 6| # + 7| # ... + 8| # + 9| # ---------------------------------------------------------------------- +10| # $Id$ +11| # ---------------------------------------------------------------------- +12| +13| function doSomething { +14| +15| } + +Figure 3.4: The functions script base comment structure + + Relevant lines in the above structure are lines from 5 to 9. +Everything else in the file is left immutable. + + When you are updating copyright through `shell' functionality, the +`centos-art.sh' script replaces everything in-between line 5 --the +first one matching `^# Copyright .+$' string-- and line 9--the first +long dash separator matching `^# -+$'-- with the content of copyright +template instance. + + *Caution* Be sure to add the long dash separator that matches `^# + -+$' regular expression _before_ the function definition. + Otherwise, if the `Copyright' line is present but no long dash + separator exists, `centos-art.sh' will remove anything in-between + the `Copyright' line and the end of file. This way you may lost + your function definitions entirely. + + The copyright template instance is created from one copyright +template stored in the `Config/tpl_forCopyright.sed' file. The template +instance is created once, and later removed when no longer needed. At +this moment, when template instance is created, the `centos-art.sh' +script takes advantage of automation in order to set copyright full +name and date dynamically. + + When you use `shell' functionality to update copyright, the first +thing `shell' functionality does is requesting copyright information to +user, and later, if values were left empty (i.e., no value was typed +before pressing key), the `shell' functionality uses its own +default values. + + When `shell' functionality uses its own default values, the final +copyright note looks like the following: + + + 1| #!/bin/bash + 2| # + 3| # doSomthing.sh -- The function description goes here. + 4| # + 5| # Copyright (C) 2003, 2010 The CentOS Project + 6| # + 7| # This program is free software; you can redistribute it and/or modify + 8| # it under the terms of the GNU General Public License as published by + 9| # the Free Software Foundation; either version 2 of the License, or +10| # (at your option) any later version. +11| # +12| # This program is distributed in the hope that it will be useful, but +13| # WITHOUT ANY WARRANTY; without even the implied warranty of +14| # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +15| # General Public License for more details. +16| # +17| # You should have received a copy of the GNU General Public License +18| # along with this program; if not, write to the Free Software +19| # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 +20| # USA. +21| # +22| # ---------------------------------------------------------------------- +23| # $Id$ +24| # ---------------------------------------------------------------------- +25| +26| function doSomething { +27| +28| } + +Figure 3.5: The function script comment example + + Relevant lines in the above structure are lines from 5 to 22. Pay +attention how the copyright line was built, and how the license was +added into the top comment where previously was just three dots. +Everything else in the file was left immutable. + + To change copyright information (i.e., full name or year +information), run the `shell' functionality over the root directory +containing the script files you want to update copyright in and enter +the appropriate information when it be requested. You can run the +`shell' functionality as many times as you need to. + + To change copyright license (i.e., the text in-between lines 7 and +20), you need to edit the `Config/tpl_forCopyright.sed' file, set the +appropriate information, and run the `shell' functionality once again +for changes to take effect over the files you specify. + + *Important* The `centos-art.sh' script is released as: + + + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. + + Do not change the license information under which `centos-art.sh' + script is released. Instead, if you think a different license must + be used, please share your reasons at CentOS Developers mailing + list . + +3.57.3 Usage +------------ + +`centos-art sh --update-copyright='path/to/dir'' +`centos-art sh --update-copyright='path/to/dir' --filter='regex'' + Use these commands to update copyright information in `.sh' files + under `path/to/dir' directory. + + When you provide `--filter='regex'' argument, the list of files to +process is reduced as specified in `regex' regular expression. Inside +`centos-art.sh' script, the `regex' regular expression is used in +combination with `find' command to look for files matching the regular +expression path pattern. + + *Warning* In order for `regex' regular expression to match a file, + the `regex' regular expresion must match the whole file path not + just the file name. + + For example, if you want to match all `render.conf.sh' files inside +`path/to/dir', use the `.+/render.conf' regular expression. Later, +`centos-art.sh' script uses this value inside `^$REGEX\.sh$' expression +in order to build the final regular expression (i.e., +`^.+/render.conf\.sh$') that is evaluated against available file paths +inside the list of files to process. + + Exceptionally, when you provide `--filter='regex'' in the way that +`regex', appended to `path/to/dir/' (i.e. `path/to/dir/regex'), +matches a regular file; the `centos-art.sh' script uses the file +matching as only file in the list of files to process. + +3.57.4 See also +--------------- + +3.58 trunk/Scripts/Bash/Cli/Functions/Svg +========================================= + +3.58.1 Goals +------------ + +This section exists to organize files related to `svg' functionality of +`centos-art.sh' script. + +3.58.2 Description +------------------ + +The `svg' functionality of `centos-art.sh' script helps you to maintain +scalable vector graphics (SVG) inside repository. For example, suppose +you've been working in CentOS default design models under +`trunk/Identity/Themes/Models/', and you want to set common metadata to +all of them, and later remove all unused SVG defintions from `*.svg' +files. Doing so file by file may be a tedious task, so the +`centos-art.sh' script provides the `svg' functionality to aid you +maintain such actions. + +3.58.2.1 Metadata maintainance +.............................. + +The metadata used is defined by Inkscape 0.46 using the SVG standard +markup. The `centos-art.sh' script replaces everything in-between +`' tags with a predefined metadata template +we've set for this purpose. + + The metadata template was created using the metadata information of a +file which, using Inkscape 0.46, all metadata fields were set. This +created a complete markup representation of how SVG metadata would look +like. Later, we replaced every single static value with a translation +marker in the form `=SOMETEXT=', where `SOMETEXT' is the name of its +main opening tag. Later, we transform the metadata template into a sed +replacement set of commads escaping new lines at the end of each line. + + With metadata template in place, the `centos-art.sh' script uses it +to create a metadata template instance for the file being processed +currently. The metadata template instance contains the metadata +portion of sed replacement commands with translation markers already +traduced. In this action, instance creation, is where we take +advantage of automation and generate metadata values like title, date, +keywords, source, identifier, and relation dynamically, based on the +file path `centos-art.sh' script is currently creating metadata +information for. + + With metadata template instance in place, the `centos-art.sh' script +uses it to replace real values inside all `.svg' files under the +current location you're running the `centos-art.sh' script on. Default +behaviour is to ask user to enter each metadatum required, one by one. +If user leaves metadatum empty, by pressing key, `centos-art.sh' +uses its default value. + + The `centos-art.sh' script modifies the following metadata: + +`Title' + Name by which this document is formally known. If no value is set + here, `centos-art.sh' script uses the file name as title. + +`Date' + Date associated with the creation of this document (YYYY-MM-DD). + If no value is set here, `centos-art.sh' script uses the current + date information as in `date +%Y-%m-%d'. + +`Creator' + Name of entity primarily responsible for making the content of this + document. If no value is set here, `centos-art.sh' script uses the + string `The CentOS Project'. + +`Rights' + Name of entity with rights to the intellectual Property of this + document. If no value is set here, `centos-art.sh' script uses the + string `The CentOS Project'. + +`Publisher' + Name of entity responsible for making this document available. If + no value is set here, `centos-art.sh' script uses the string `The + CentOS Project'. + +`Identifier' + Unique URI to reference this document. If no value is set here, + `centos-art.sh' script uses the current file path to build the + related url that points to current file location inside repository + central server. + +`Source' + Unique URI to reference the source of this document. If no value is + set here, `centos-art.sh' script uses current file path to build + the related url that points to current file location inside + repository central server. + +`Relation' + Unique URI to a related document. If no value is set here, + `centos-art.sh' script uses current file path to build the related + url that points to current file location inside repository central + server. + +`Language' + Two-letter language tag with optional subtags for the language of + this document. (e.g. `en-GB'). If no value is set here, + `centos-art.sh' script uses the current locale information as in + `cli_getCurrentLocale' function. + +`Keywords' + The topic of this document as comma-separated key words, prhases, + or classifications. If no value is set here, `centos-art.sh' script + uses file path to build + +`Coverage' + Extent or scope of this document. If no value is set here, + `centos-art.sh' script uses the string `The CentOS Project'. + +`Description' + Description about the document. If no value is set here, + `centos-art.sh' script uses uses empty value as default. + +`Contributors' + People that contributes in the creation/maintainance of the + document. If no value is set here, `centos-art.sh' script uses + uses empty value as default. + + The `License' metadatum is not set as a choise, by now. It is fixed +Creative Common Attribution Share-Alike 3.0 License +(http://creativecommons.org/licenses/by-sa/3.0/). This is done in order +to grant license consistency among all SVG files we manage inside CentOS +Artwork Repository. + +3.58.2.2 Unused definitions +........................... + +Many of the no-longer-used gradients, patterns, and markers (more +precisely, those which you edited manually) remain in the corresponding +palettes and can be reused for new objects. However if you want to +optimize your document, use the `Vacuum Defs' command in `File' menu. +It will remove any gradients, patterns, or markers which are not used +by anything in the document, making the file smaller. + + If you have one or two couple of files, removing unused definitions +using the graphical interface may be enough to you. In contrast, if +you have dozens or even houndreds of scalable vector graphics files to +maintain it is not a fun task to use the graphical interface to remove +unused definitions editing those files one by one. + + To remove unused definitions from several scalable vector graphics +files, the `centos-art.sh' script uses Inkscape command-line interface, +specifically with the `--vaccum-defs' option. + +3.58.3 Usage +------------ + +`centos-art svg --update-metadata='path/to/dir'' + +`centos-art svg --update-metadata='path/to/dir' --filter='regex'' + Use these commands to update metadata information to `.svg' files + under `path/to/dir' directory. + +`centos-art svg --vacuum-defs='path/to/dir'' + +`centos-art svg --vacuum-defs='path/to/dir' --filter='regex'' + Use these commands to remove unused definitions inside `.svg' + files under `path/to/dir' directory. + + When you provide `--filter='regex'' argument, the list of files to +process is reduced as specified in `regex' regular expression. Inside +`centos-art.sh' script, the `regex' regular expression is used in +combination with `find' command to look for files matching the regular +expression path pattern. + + *Warning* In order for `regex' regular expression to match a file, + the `regex' regular expresion must match the whole file path not + just the file name. + + For example, if you want to match all `summary.svg' files inside +`path/to/dir', use the `.+/summary' regular expression. Later, +`centos-art.sh' script uses this value inside `^$REGEX\.svg$' +expression in order to build the final regular expression (i.e., +`^.+/summary\.svg$') that is evaluated against available file paths +inside the list of files to process. + + Exceptionally, when you provide `--filter='regex'' in the way that +`regex', appended to `path/to/dir/' (i.e. `path/to/dir/regex'), +matches a regular file; the `centos-art.sh' script uses the file +matching as only file in the list of files to process. + +3.58.4 See also +--------------- + +3.59 trunk/Scripts/Bash/Cli/Functions/Verify +============================================ + +3.59.1 Goals +------------ + +This section exists to organize files related to `centos-art.sh' script +`verify' functionality. The `verify' functionality of `centos-art.sh' +script helps you to verify the workstation configuration you are +planning to use as host for your working copy of CentOS Artwork +Repository. + +3.59.2 Description +------------------ + +The first time you download CentOS Artwork Repository you need to +configure your workstation in order to use `centos-art.sh' script. +These preliminar configurations are based mainly on auxiliar RPM +packages installation, symbolic links creations, and environment +variables definitions. The `verify' functionality of `centos-art.sh' +script guides you through this preliminar configuration process. + + If this is the first time you run `centos-art.sh' script, the +appropriate way to use its `verify' functionality is not using the +`centos-art.sh' script directly, but the absolute path to +`centos-art.sh' script instead (i.e., +`~/artwork/trunk/Scripts/Bash/centos-art.sh'). This is necessary +because `centos-art' symbolic link, under `~/bin/' directory, has not +been created yet. + +3.59.2.1 Packages +................. + +Installation of auxiliar RPM packages provides the software required to +manipulate files inside the repository (e.g., image files, +documentation files, translation files, script files, etc.). Most of +RPM packages `centos-art.sh' script uses are shipped with CentOS +distribution, and can be installed from CentOS base repository. The +only exception is `inkscape', the package we use to manipulate SVG +files. The `inkscape' package is not inside CentOS distribution so it +needs to be installed from third party repositories. + + *Note* Configuration of third party repositories inside CentOS + distribution is described in CentOS wiki, specifically in the + following URL: + `http://wiki.centos.org/AdditionalResources/Repositories' + + Before installing packages, the `centos-art.sh' script uses `sudo' +to request root privileges to execute `yum' installation functionality. +If your user isn't defined as a privileged user--at least to run `yum' +commands-- inside `/etc/sudoers' configuration file, you will not be +able to perform package installation tasks as set in `centos-art.sh' +script `verify' functionality. + + Setting sudo privileges to users is an administrative task you have +to do by yourself. If you don't have experience with `sudo' command, +please read its man page running the command: `man sudo'. This reading +will be very useful, and with some practice, you will be able to +configure your users to have `sudo' privileges. + +3.59.2.2 Links +.............. + +Creation of symbolic links helps us to alternate between different +implementations of `centos-art.sh' script-line (e.g., `centos-art.sh', +for Bash implementation; `centos-art.py', for Python implementation; +`centos-art.pl', for Perl implementation; and so on for other +implementations). The `centos-art.sh' script-line definition takes +place inside your personal binary (`~/bin/') directory in order to make +the script implementation --the one that `centos-art' links to-- +available to PATH environment variable. + + Creation of symbolic links helps us to reuse components from +repository working copy. For example, color information files +maintained inside your working copy must never be duplicated inside +program-specific configuration directories that uses them in your +workstation (e.g., Gimp, Inkscape, etc.). Instead, a symbolic link +must be created for each one of them, from program-specific +configuration directories to files in the working copy. In this +configuration, when someone commits changes to color information files +up to central repository, they--the changes committed-- will be +immediatly available to your programs the next time you update your +working copy --the place inside your workstation those color +information files are stored--. + + Creation of symbolic links helps us to make `centos-art.sh' script +functionalities available outside `trunk/' repository directory +structure, but at its same level in repository tree. This is useful if +you need to use the "render" functionality of `centos-art.sh' under +`branches/' repository directory structure as you usually do inside +`trunk/' repository directory structure. As consequence of this +configuration, automation scripts cannot be branched under +`branches/Scripts' directory structure. + +3.59.2.3 Environment variables +.............................. + +Definition of environemnt variables helps us to set default values to +our user session life. The user session environment variable defintion +takes place in the user's `~/.bash_profile' file. The `verify' +functionality of `centos-art.sh' script doesn't modify your +`~/.bash_profile' file. + + The `verify' functionality of `centos-art.sh' script evaluates the +following environment variables: + +`EDITOR' + Default text editor. + + The `centos-art.sh' script uses default text `EDITOR' to edit + pre-commit subversion messages, translation files, configuration + files, script files, and similar text-based files. + + If `EDITOR' environment variable is not set, `centos-art.sh' + script uses `/usr/bin/vim' as default text editor. Otherwise, the + following values are recognized by `centos-art.sh' script: + + * `/usr/bin/vim' + + * `/usr/bin/emacs' + + * `/usr/bin/nano' + + If no one of these values is set in `EDITOR' environment variable, + `centos-art.sh' uses `/usr/bin/vim' text editor by default. + +`TEXTDOMAIN' + Default domain used to retrieve translated messages. This + variable is set in `initFunctions.sh' and shouldn't be changed. + +`TEXTDOMAINDIR' + Default directory used to retrieve translated messages. This + variable is set in `initFunctions.sh' and shouldn't be changed. + +`LANG' + Default locale information. + + This variable is initially set in the configuration process of + CentOS distribution installer (i.e., Anaconda), specifically in the + `Language' step; or once installed using the + `system-config-language' tool. + + The `centos-art.sh' script uses the LANG environment variable to + know in which language the script messages are printed out. + +`TZ' + Default time zone representation. + + This variable is initially set in the configuration process of + CentOS distribution installer (i.e., Anaconda), specifically in the + `Date and time' step; or once installed using the + `system-config-date' tool. + + The `centos-art.sh' script doesn't use the TZ environment variable + information at all. Instead, this variable is used by the system + shell to show the time information according to your phisical + location on planet Earth. + + Inside your computer, the time information is firstly set in the + BIOS clock (which may need correction), and later in the + configuration process of CentOS distribution installer (or later, + by any of the related configuration tools inside CentOS + distribution). Generally, setting time information is a + straight-forward task and configuration tools available do cover + most relevant location. However, if you need a time precision not + provided by the configuration tools available inside CentOS + distribution then, using TZ variable may be necessary. + + *Convenction* In order to keep changes syncronized between + central repository and its working copies: configure both + repository server and workstations (i.e., the place where + each working copy is set on) to use Coordinated Universal + Time (UTC) as base time representation. Later, correct the + time information for your specific location using time zone + correction. + + The format of TZ environment variable is described in `tzset(3)' + manual page. + + +3.59.3 Usage +------------ + +`centos-art verify --packages' + Verify required packages your workstation needs in order to run the + `centos-art.sh' script correctly. If there are missing packages, + the `centos-art.sh' script asks you to confirm their installation. + When installing packages, the `centos-art.sh' script uses the + `yum' application in order to achieve the task. + + In case all packages required by `centos-art.sh' script are + already installed in your workstation, the message `The required + packages are already installed.' is output for you to know. + +`centos-art verify --links' + Verify required links your workstation needs in order to run the + centos-art command correctly. If any required link is missing, the + `centos-art.sh' script asks you to confirm their installation. To + install required links, the `centos-art.sh' script uses the `ln' + command. + + In case all links required by `centos-art.sh' script are already + created in your workstation, the message `The required links are + already installed.' is output for you to know. + + In case a regular file exists with the same name of a required + link, the `centos-art.sh' script outputs the `Already exists as + regular file.' message when listing required links that will be + installed. Of course, as there is already a regular file where + must be a link, no link is created. In such cases the + `centos-art.sh' script will fall into a continue installation + request for that missing link. To end this continue request you + can answer `No', or remove the existent regular file to let + `centos-art.sh' script install the link on its place. + +`centos-art verify --environment' +`centos-art verify --environment --filter='regex'' + Output a brief description of environment variables used by + `centos-art.sh' script. + + If `--filter' option is provided, output is reduced as defined in + the `regex' regular expression value. If `--filter' option is + specified but `regex' value is not, the `centos-art.sh' script + outputs information as if `--filter' option had not been provided + at all. + + +3.59.4 See also +--------------- + +3.60 trunk/Scripts/Python +========================= + +3.60.1 Goals +------------ + + * ... + +3.60.2 Description +------------------ + + * ... + +3.60.3 Usage +------------ + + * ... + +3.60.4 See also +--------------- + +Index +***** + +branches: See 1. (line 368) +How to render brands' translation files: See 3.36.3. (line 2425) +How to render fonts' translation files: See 3.38.3. (line 2498) +Metadata maintainance: See 3.58.2. (line 5534) +tags: See 2. (line 371) +Translation brands file names: See 3.36.2.1. (line 2382) +trunk: See 3. (line 374) +trunk Identity: See 3.1. (line 377) +trunk Identity Brands: See 3.2. (line 493) +trunk Identity Fonts: See 3.3. (line 510) +trunk Identity Icons: See 3.4. (line 587) +trunk Identity Isolinux: See 3.5. (line 604) +trunk Identity Models: See 3.6. (line 621) +trunk Identity Models Css: See 3.7. (line 641) +trunk Identity Models Html: See 3.8. (line 663) +trunk Identity Models Img Promo Web: See 3.9. (line 684) +trunk Identity Models Tpl: See 3.10. (line 705) +trunk Identity Models Tpl Promo Web: See 3.11. (line 726) +trunk Identity Models Xcf: See 3.12. (line 1040) +trunk Identity Release: See 3.13. (line 1061) +trunk Identity Themes: See 3.14. (line 1078) +trunk Identity Themes Models: See 3.15. (line 1102) +trunk Identity Themes Models Alternative: See 3.16. (line 1135) +trunk Identity Themes Models Default: See 3.17. (line 1162) +trunk Identity Themes Models Default Distro: See 3.18. (line 1194) +trunk Identity Themes Models Default Distro Anaconda:See 3.19. + (line 1278) +trunk Identity Themes Models Default Promo: See 3.20. (line 1295) +trunk Identity Themes Models Default Web: See 3.21. (line 1321) +trunk Identity Themes Motifs: See 3.22. (line 1346) +trunk Identity Themes Motifs Flame: See 3.23. (line 1449) +trunk Identity Themes Motifs Modern: See 3.24. (line 1650) +trunk Identity Themes Motifs Modern Backgrounds:See 3.25. (line 1667) +trunk Identity Themes Motifs Modern Backgrounds Img:See 3.26. + (line 1788) +trunk Identity Themes Motifs Modern Backgrounds Tpl:See 3.27. + (line 1809) +trunk Identity Themes Motifs Modern Backgrounds Xcf:See 3.28. + (line 1830) +trunk Identity Themes Motifs Modern Distro Anaconda Progress:See 3.29. + (line 1857) +trunk Identity Themes Motifs Modern Palettes: See 3.30. (line 1913) +trunk Identity Themes Motifs TreeFlower: See 3.31. (line 1935) +trunk Identity Themes Motifs TreeFlower Backgrounds:See 3.32. + (line 1952) +trunk Identity Widgets: See 3.33. (line 2250) +trunk Locales: See 3.34. (line 2267) +trunk Locales Identity: See 3.35. (line 2320) +trunk Locales Identity Brands: See 3.36. (line 2341) +trunk Locales Identity Brands Tpl: See 3.37. (line 2436) +trunk Locales Identity Fonts: See 3.38. (line 2451) +trunk Locales Identity Models: See 3.39. (line 2514) +trunk Locales Identity Release: See 3.40. (line 2529) +trunk Locales Identity Themes: See 3.41. (line 2544) +trunk Locales Identity Themes Backgrounds: See 3.42. (line 2559) +trunk Locales Identity Themes Distro Anaconda Progress:See 3.43. + (line 2580) +trunk Locales Identity Widgets: See 3.44. (line 2673) +trunk Manuals: See 3.45. (line 2694) +trunk Scripts: See 3.46. (line 2715) +trunk Scripts Bash: See 3.47. (line 2739) +trunk Scripts Bash Cli: See 3.48. (line 2889) +trunk Scripts Bash Cli Functions: See 3.49. (line 2892) +trunk Scripts Bash Cli Functions Help: See 3.50. (line 4002) +trunk Scripts Bash Cli Functions Html: See 3.51. (line 4023) +trunk Scripts Bash Cli Functions Locale: See 3.52. (line 4044) +trunk Scripts Bash Cli Functions Manual: See 3.53. (line 4124) +trunk Scripts Bash Cli Functions Path: See 3.54. (line 4145) +trunk Scripts Bash Cli Functions Render: See 3.55. (line 4468) +trunk Scripts Bash Cli Functions Render Config:See 3.56. (line 5166) +trunk Scripts Bash Cli Functions Shell: See 3.57. (line 5344) +trunk Scripts Bash Cli Functions Svg: See 3.58. (line 5516) +trunk Scripts Bash Cli Functions Verify: See 3.59. (line 5704) +trunk Scripts Python: See 3.60. (line 5934) +Unused definitions: See 3.58.2.1. (line 5641) +List of Figures +*************** + diff --git a/Manuals/Repository/filesystem.xml b/Manuals/Repository/filesystem.xml new file mode 100644 index 0000000..1865c26 --- /dev/null +++ b/Manuals/Repository/filesystem.xml @@ -0,0 +1,5421 @@ + + + + filesystem.xml + CentOS Artwork Repository - File System + + Copyright ©right; 2009-2011 Alain Reguera Delgado + Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. + + + CentOS Artwork Repository + File System + Alain Reguera Delgado + Copyright ©right; 2009-2011 Alain Reguera Delgado + Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. + + + + + Top + (dir) + + CentOS Artwork Repository - File System + Copyright ©right; 2009-2011 Alain Reguera Delgado + Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. + + + branches + branches + + + + tags + tags + + + + trunk + trunk + + + + Index + Index + + + + List of Figures + List of Figures + + + + + + + + branches + tags + Top + Top + + branches + branches + + + + tags + trunk + branches + Top + + tags + tags + + + + trunk + Index + tags + Top + + trunk + trunk + + + trunk Identity + trunk Identity + + + + trunk Identity Brands + trunk Identity Brands + + + + trunk Identity Fonts + trunk Identity Fonts + + + + trunk Identity Icons + trunk Identity Icons + + + + trunk Identity Isolinux + trunk Identity Isolinux + + + + trunk Identity Models + trunk Identity Models + + + + trunk Identity Models Css + trunk Identity Models Css + + + + trunk Identity Models Html + trunk Identity Models Html + + + + trunk Identity Models Img Promo Web + trunk Identity Models Img Promo Web + + + + trunk Identity Models Tpl + trunk Identity Models Tpl + + + + trunk Identity Models Tpl Promo Web + trunk Identity Models Tpl Promo Web + + + + trunk Identity Models Xcf + trunk Identity Models Xcf + + + + trunk Identity Release + trunk Identity Release + + + + trunk Identity Themes + trunk Identity Themes + + + + trunk Identity Themes Models + trunk Identity Themes Models + + + + trunk Identity Themes Models Alternative + trunk Identity Themes Models Alternative + + + + trunk Identity Themes Models Default + trunk Identity Themes Models Default + + + + trunk Identity Themes Models Default Distro + trunk Identity Themes Models Default Distro + + + + trunk Identity Themes Models Default Distro Anaconda + trunk Identity Themes Models Default Distro Anaconda + + + + trunk Identity Themes Models Default Promo + trunk Identity Themes Models Default Promo + + + + trunk Identity Themes Models Default Web + trunk Identity Themes Models Default Web + + + + trunk Identity Themes Motifs + trunk Identity Themes Motifs + + + + trunk Identity Themes Motifs Flame + trunk Identity Themes Motifs Flame + + + + trunk Identity Themes Motifs Modern + trunk Identity Themes Motifs Modern + + + + trunk Identity Themes Motifs Modern Backgrounds + trunk Identity Themes Motifs Modern Backgrounds + + + + trunk Identity Themes Motifs Modern Backgrounds Img + trunk Identity Themes Motifs Modern Backgrounds Img + + + + trunk Identity Themes Motifs Modern Backgrounds Tpl + trunk Identity Themes Motifs Modern Backgrounds Tpl + + + + trunk Identity Themes Motifs Modern Backgrounds Xcf + trunk Identity Themes Motifs Modern Backgrounds Xcf + + + + trunk Identity Themes Motifs Modern Distro Anaconda Progress + trunk Identity Themes Motifs Modern Distro Anaconda Progress + + + + trunk Identity Themes Motifs Modern Palettes + trunk Identity Themes Motifs Modern Palettes + + + + trunk Identity Themes Motifs TreeFlower + trunk Identity Themes Motifs TreeFlower + + + + trunk Identity Themes Motifs TreeFlower Backgrounds + trunk Identity Themes Motifs TreeFlower Backgrounds + + + + trunk Identity Widgets + trunk Identity Widgets + + + + trunk Locales + trunk Locales + + + + trunk Locales Identity + trunk Locales Identity + + + + trunk Locales Identity Brands + trunk Locales Identity Brands + + + + trunk Locales Identity Brands Tpl + trunk Locales Identity Brands Tpl + + + + trunk Locales Identity Fonts + trunk Locales Identity Fonts + + + + trunk Locales Identity Models + trunk Locales Identity Models + + + + trunk Locales Identity Release + trunk Locales Identity Release + + + + trunk Locales Identity Themes + trunk Locales Identity Themes + + + + trunk Locales Identity Themes Backgrounds + trunk Locales Identity Themes Backgrounds + + + + trunk Locales Identity Themes Distro Anaconda Progress + trunk Locales Identity Themes Distro Anaconda Progress + + + + trunk Locales Identity Widgets + trunk Locales Identity Widgets + + + + trunk Manuals + trunk Manuals + + + + trunk Scripts + trunk Scripts + + + + trunk Scripts Bash + trunk Scripts Bash + + + + trunk Scripts Bash Cli + trunk Scripts Bash Cli + + + + trunk Scripts Bash Cli Functions + trunk Scripts Bash Cli Functions + + + + trunk Scripts Bash Cli Functions Help + trunk Scripts Bash Cli Functions Help + + + + trunk Scripts Bash Cli Functions Html + trunk Scripts Bash Cli Functions Html + + + + trunk Scripts Bash Cli Functions Locale + trunk Scripts Bash Cli Functions Locale + + + + trunk Scripts Bash Cli Functions Manual + trunk Scripts Bash Cli Functions Manual + + + + trunk Scripts Bash Cli Functions Path + trunk Scripts Bash Cli Functions Path + + + + trunk Scripts Bash Cli Functions Render + trunk Scripts Bash Cli Functions Render + + + + trunk Scripts Bash Cli Functions Render Config + trunk Scripts Bash Cli Functions Render Config + + + + trunk Scripts Bash Cli Functions Shell + trunk Scripts Bash Cli Functions Shell + + + + trunk Scripts Bash Cli Functions Svg + trunk Scripts Bash Cli Functions Svg + + + + trunk Scripts Bash Cli Functions Verify + trunk Scripts Bash Cli Functions Verify + + + + trunk Scripts Python + trunk Scripts Python + + + + + + + trunk Identity + trunk Identity Brands + trunk +
+ trunk/Identity + trunk Identity + + Goals + The trunk/Identity directory exists to organize CentOS corporate identity artworks. + + + + Description + The CentOS Project corporate identity is the “persona” of the organization known as The CentOS Project. The CentOS Project corporate identity plays a significant role in the way the CentOS Project, as organization, presents itself to both internal and external stakeholders. In general terms, the CentOS Project corporate visual identity expresses the values and ambitions of the CentOS Project organization, its business, and its characteristics. + The CentOS Project corporate identity provides visibility, recognizability, reputation, structure and identification to the CentOS Project organization by means of corporate design, corporate communication, and corporate behaviour. + The CentOS Project settles down its corporate visual identity on a “monolithic corporate visual identity structure”. In this structure The CentOS Project uses one unique name (The CentOS Brand) and one unique visual style (The CentOS Default Theme) in all its manifestations. + + + The CentOS Brands + + The CentOS brand is the name or trademark that conncects the producer with their products. In this case, the producer is The CentOS Project and the products are the CentOS distributions, the CentOS web sites, the CentOS promotion stuff, etc. + See trunk Identity Brands, for more information. + + + + The CentOS Themes + + The CentOS themes are a set of image files connected all together by one unique visual style. Each theme is organized in different visual manifestations, in order to cover each visual manifestation of The CentOS Project (i.e., distributions, websites, promotion stuff, etc.). See trunk Identity Themes, for more information. + + +
+ Inside a monolithic corporate visual identity structure, internal and external stakeholders use to feel a strong sensation of uniformity, orientation, and identification with the organization. No matter if you are visiting websites, using the distribution, or acting on social events, the one unique name and one unique visual style conect them all to say: Hey! we are all parts of the CentOS project. And, probably, some vister will say: Can I join the party? Yes you can, it is free. :) + + + + Usage + To produce identity artworks, use the following commands: + + + centos-art render 'path/to/dir' + + When path/to/dir refers to one renderable directory under trunk/Identity, this command renders identity artworks using both related design models and related translation files. + + + + centos-art render 'path/to/dir' --filter='pattern' + + When path/to/dir refers to one renderable directory under trunk/Identity, this command renders identity artworks using both related design models and related translation files that match the regular expression passed in --filter='pattern' argument. + To control the number of files produced by centos-art command, you need to look into the translation path and provide a regular expression pattern that matches the translation path, or paths, related to the file, or files, you want to produce. + The regular expression pattern you provide to centos-art command is applied to the translation path from its very beginning. It is not the same to say 5/en/01-welcome that 01-welcome, the frist expression matches but the last one does not. + When using --filter='pattern' you don't need to specify the file extension. It is removed from translation path before applying the pattern, so it doesn't count here. + + +
+ + + + File name convenctions + As file name convenction, inside CentOS Artwork Repository, both text-based and image-based file name produced by centos-art.sh script has the same name of their translation files without the .sed extension. The file extension is set as follow: + + + When text-based files are rendered + Text-based files end up having the same extension of their design template file. + + + + When image-based files are rendered + Image-based files always end up having the .png extension. + + Tip Once .png images are created, other image formats may be created using the renderFormats post-rendering action, inside the image-based related pre-rendering configuration script. + See trunk Scripts Bash, for more information. + + + + + + See also + + + + + + + References + + • + + http://en.wikipedia.org/Corporate_identity (and related links). + + + +
+ + + trunk Identity Brands + trunk Identity Fonts + trunk Identity + trunk +
+ trunk/Identity/Brands + trunk Identity Brands + + Goals + + • + + ... + + + + + + Description + + + + Usage + + + + See also + + + +
+ + + trunk Identity Fonts + trunk Identity Icons + trunk Identity Brands + trunk +
+ trunk/Identity/Fonts + trunk Identity Fonts + + Goals + This section exists to organize digital typographies used by the CentOS project. + + + + Description + + + + Usage + The CentOS corporate identity is attached to DejaVu LGC font-family. Whatever artwork you design for CentOS project, that requires typography usage, must be done using DejaVu LGC font-family. + + + Recommendation-1: + + For screen desings (e.g., anything that final destination will never be printed on paper or any medium outside computer screens) use DejaVu LGC Sans font-family. + + + + Recommendation-2: + + For non-screen designs (e.g., anything that final desition will be printed on paper or any other medium outside computer screens) use DejaVu LGC Serif font-family. As convenction files described in this rule are stored under Stationery directories. + + +
+ The only execption for the two recommendations above is the typography used inside CentOS logo. The CentOS logo is the main visual representation of the CentOS project so the typography used in it must be the same always, no matter where it be shown. It also has to be clear enough to dismiss any confussion between similar typefaces (e.g., the number one (1) sometimes is confuesed with the letter el (l) or letter ai (i)). + As CentOS logo typography convenction, the word CentOS uses Denmark typography as base, both for the word CentOS and the phrase Community Enterprise Operating System. The phrase size of CentOS logo is half the size in poits the word CentOS has and it below CentOS word and aligned with it on the left. The distance between CentOS word and phrase Community Enterprise Operating System have the size in points the phrase has. + When the CentOS release brand is built, use Denmark typography for the release number. The release number size is two times larger (in height) than default CentOS word. The separation between release number and CentOS word is twice the size in points of separation between CentOS word and phrase Community Enterprise Operating System. + Another component inside CentOS logo is the trademark symbol (TM). This symbol specifies that the CentOS logo must be consider a product brand, even it is not a registered one. The trademark symbol uses DejaVu LGC Sans Regular typography. The trademark symbol is aligned right-top on the outter side of CentOS word. The trademark symbol must not exceed haf the distance, in points, between CentOS word and the release number on its right. + It would be very convenient for the CentOS Project and its community to to make a registered trademark (®) of CentOS logo. To make a register trademark of CentOS Logo prevents legal complications in the market place of brands. It grants the consistency, through time, of CentOS project corporate visual identity. + + Note The information about trademarks and corporate identity is my personal interpretation of http://en.wikipedia.org/Corporate_identity and http://en.wikipedia.org/Trademark description. If you have practical experiences with these affairs, please serve yourself to improve this section with your reasons. + + + + + See also + + + +
+ + + trunk Identity Icons + trunk Identity Isolinux + trunk Identity Fonts + trunk +
+ trunk/Identity/Icons + trunk Identity Icons + + Goals + + • + + ... + + + + + + Description + + + + Usage + + + + See also + + + +
+ + + trunk Identity Isolinux + trunk Identity Models + trunk Identity Icons + trunk +
+ trunk/Identity/Isolinux + trunk Identity Isolinux + + Goals + + • + + ... + + + + + + Description + + + + Usage + + + + See also + + + +
+ + + trunk Identity Models + trunk Identity Models Css + trunk Identity Isolinux + trunk +
+ trunk/Identity/Models + trunk Identity Models + + Goals + This section exists to organize design models. + + + + Description + Design models are representative designs useful to understand how to build artworks. + + + + Usage + + + + See also + + + trunk Identity Models Html + trunk Identity Models Html + + + + trunk Identity Models Css + trunk Identity Models Css + + + + trunk Identity Models Tpl + trunk Identity Models Tpl + + + + trunk Identity Models Xcf + trunk Identity Models Xcf + + + + +
+ + + trunk Identity Models Css + trunk Identity Models Html + trunk Identity Models + trunk +
+ trunk/Identity/Models/Css + trunk Identity Models Css + + Goals + This directory exists to provide common style sheets (CSS) definitions to HTML design models. + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Identity Models Html + trunk Identity Models Img Promo Web + trunk Identity Models Css + trunk +
+ trunk/Identity/Models/Html + trunk Identity Models Html + + Goals + + • + + ... + + + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Identity Models Img Promo Web + trunk Identity Models Tpl + trunk Identity Models Html + trunk +
+ trunk/Identity/Models/Img/Promo/Web + trunk Identity Models Img Promo Web + + Goals + + • + + Provide images related to CentOS web interface. + + + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + trunk Identity Models Tpl Promo Web + trunk Identity Models Tpl Promo Web + + + + +
+ + + trunk Identity Models Tpl + trunk Identity Models Tpl Promo Web + trunk Identity Models Img Promo Web + trunk +
+ trunk/Identity/Models/Tpl + trunk Identity Models Tpl + + Goals + + • + + ... + + + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Identity Models Tpl Promo Web + trunk Identity Models Xcf + trunk Identity Models Tpl + trunk +
+ trunk/Identity/Models/Tpl/Promo/Web + trunk Identity Models Tpl Promo Web + + Goals + Organize scalable vector graphics (svg) to help describe the CentOS web environment. + + + + 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: + + • + + One unique name and one unique visual style to all web applications used inside the web environment. + + + One-step navigation to web applications inside the environment. + + + High degree of customization to change the visual style of all web applications with few changes (e.g, updating just two or three images plus common style sheet [CSS] definitions). + + + The CentOS project is attached to a monolithic corporate visual identity (see 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 supportThe theme support of Mailman may be introduced in mailman-3.x.x release. a customization system that separates presentation from logic, similar to that used by MoinMoin. + This visual style diversity complicates our goal of one unique visual style for all web applications. So, if we want one unique visual style for all web applications used, it is innevitable to modify the web applications in order to implement the CentOS one unique visual style customization in them. Direct modification of upstream applications is not convenient because upstream applications come with their one visual style and administrators take the risk of loosing all customization changes the next time the application be updated (since not all upstream web applications, used in CentOS web environment, separate presentation from logic). + To solve the “one unique visual style” issue, installation and actualization of web applications —used inside CentOS web environment— need to be independent from upstream web applications development line; in a way that CentOS web environment administrators can install and update web applications freely without risk of loosing the one unique visual style customization changes. + At the surface of this issue we can see the need of one specific yum repository to store CentOS web environment customized web applications. + + + Design model (without ads) + + + + Design model (with ads) + + + + HTML definitions + + + + Controlling visual style + Inside CentOS web environment, the visual style is controlled by the following compenents: + + + Webenv header background + + + + + + CSS definitions + + + + +
+ + + + Producing visual style + The visual style of CentOS web environment is defined in the following files: + + 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. + + 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. + + + + 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. + + + + 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 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: + + + + + 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: + + The command above creates the following structure: + + 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. + + Tip Use the diff command of Subversion 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. + + + + + 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. + + 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. + + 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. + + + +
+ + + + The [webenv-test] repository + + + + + + The [webenv] repository + + + + + + Priority configuration + Both [webenv] and [webenv-test] repositories update packages inside CentOS [base] and CentOS [updates] repositories. + + + + + Usage + + • + + ... + + + + + + See also + + + trunk Identity Models Img Promo Web + trunk Identity Models Img Promo Web + + + + +
+ + + trunk Identity Models Xcf + trunk Identity Release + trunk Identity Models Tpl Promo Web + trunk +
+ trunk/Identity/Models/Xcf + trunk Identity Models Xcf + + Goals + + • + + ... + + + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Identity Release + trunk Identity Themes + trunk Identity Models Xcf + trunk +
+ trunk/Identity/Release + trunk Identity Release + + Goals + + • + + ... + + + + + + Description + + + + Usage + + + + See also + + + +
+ + + trunk Identity Themes + trunk Identity Themes Models + trunk Identity Release + trunk +
+ trunk/Identity/Themes + trunk Identity Themes + + Goals + The trunk/Identity/Themes/ directory exists to organize production of CentOS themes. + + + + Description + + + + 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. + + + trunk Identity Themes Models + trunk Identity Themes Models + + + + trunk Identity Themes Motifs + trunk Identity Themes Motifs + + + + + + + See also + + + trunk Identity + trunk Identity + + + + trunk + trunk + + + + +
+ + + trunk Identity Themes Models + trunk Identity Themes Models Alternative + trunk Identity Themes + trunk +
+ trunk/Identity/Themes/Models + trunk Identity Themes Models + + Goals + + • + + Organize theme models. + + + + + + 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. + + + + 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 trunk Identity Themes Models DefaultDefault,' and `See trunk Identity Themes Models AlternativeAlternative,' ready-to-use theme models. + + + + See also + + + +
+ + + trunk Identity Themes Models Alternative + trunk Identity Themes Models Default + trunk Identity Themes Models + trunk +
+ trunk/Identity/Themes/Models/Alternative + trunk Identity Themes Models Alternative + + Goals + + • + + ... + + + + + + 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. + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Identity Themes Models Default + trunk Identity Themes Models Default Distro + trunk Identity Themes Models Alternative + trunk +
+ trunk/Identity/Themes/Models/Default + trunk Identity Themes Models Default + + Goals + This location stores CentOS default theme model. The default theme model of CentOS is used in all visual manifestations of CentOS Project corporate visual identity (e.g., distributions, web sites, promotion, etc.). + + + + Description + + + + 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 trunk Identity Themes MotifsTheme Motifs. + + + + See also + + + +
+ + + trunk Identity Themes Models Default Distro + trunk Identity Themes Models Default Distro Anaconda + trunk Identity Themes Models Default + trunk +
+ trunk/Identity/Themes/Models/Default/Distro + trunk Identity Themes Models Default Distro + + Goals + + • + + ... + + + + + + Description + It applies to all major releases of CentOS distribution. + + + 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. + 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 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. + + + + 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. + + + + + Usage + + + + See also + + + +
+ + + trunk Identity Themes Models Default Distro Anaconda + trunk Identity Themes Models Default Promo + trunk Identity Themes Models Default Distro + trunk +
+ trunk/Identity/Themes/Models/Default/Distro/Anaconda + trunk Identity Themes Models Default Distro Anaconda + + Goals + + • + + ... + + + + + + Description + + + + Usage + + + + See also + + + +
+ + + trunk Identity Themes Models Default Promo + trunk Identity Themes Models Default Web + trunk Identity Themes Models Default Distro Anaconda + trunk +
+ trunk/Identity/Themes/Models/Default/Promo + trunk Identity Themes Models Default Promo + + Goals + + • + + ... + + + + + + 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. + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Identity Themes Models Default Web + trunk Identity Themes Motifs + trunk Identity Themes Models Default Promo + trunk +
+ trunk/Identity/Themes/Models/Default/Web + trunk Identity Themes Models Default Web + + Goals + + • + + ... + + + + + + 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. + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Identity Themes Motifs + trunk Identity Themes Motifs Flame + trunk Identity Themes Models Default Web + trunk +
+ trunk/Identity/Themes/Motifs + trunk Identity Themes Motifs + + Goals + The trunk/Identity/Themes/Motifs directory exists to: + + • + + Organize CentOS themes' artistic motifs. + + + + + + Description + The artistic motif of theme is a graphic design component that provides the visual style of themes, it is used as pattern to connect all visual manifestations inside one unique theme. + Artistic motifs are based on conceptual ideas. Conceptual ideas bring the motivation, they are fuel for the engines of human imagination. Good conceptual ideas may produce good motivation to produce almost anything, and art works don't escape from it. + + + 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 the name of your artistic motif. If possible, when creating new conceptual ideas for CentOS, think about what CentOS means for you, what does it makes you feel, take your time, think deep, and share; you can improve the idea as time goes on. + Once you have defined a name for your theme, you need to create the motif structure of your theme. The motif structure is the basic direcotry structure you'll use to work your ideas. Here is where you organize your graphic design projects. + To add a new motif structure to CentOS Artwork Repository, you need to use the centos-art command line in the Identity/Themes/Motifs/ directory as described below: + centos-art add --motif=ThemeName + The previous command will create the basic structure of themes 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 + + + + Usage + When designing artistic motifs for CentOS, consider the following recommendations: + + • + + Give a unique (case-sensitive) name to your Motif. This name is used as value wherever theme variable ($THEME) or translation marker (=THEME=) is. Optionally, you can add a description about inspiration and concepts behind your work. + + + Use the location trunk/Identity/Themes/Motifs/$THEME/ to store your work. If it doesn't exist create it. Note that this require you to have previous commit access in CentOS Artwork Repository. + + + The CentOS Project is using the blue color (#204c8d) as base color for its corporate visual identity. Use such base corporate color information as much as possible in your artistic motif designs. + + + Try to make your design fit one of the theme models. + + + Feel free to make your art enterprise-level and beautiful. + + + Add the following information on your artwork (both in a visible design area and document metadata): + + • + + The name (or logo) of your artistic motif. + + + The copyright sentence: Copyright (C) YEAR YOURNAME + + + The license under which the work is released. All CentOS Art works are released under http://creativecommons.org/licenses/by-sa/3.0/Creative Common Share-Alike License 3.0 (http://creativecommons.org/licenses/by-sa/3.0/). + + + + + + + + See also + + + trunk Identity Themes + trunk Identity Themes + + + + trunk Identity + trunk Identity + + + + trunk + trunk + + + + +
+ + + trunk Identity Themes Motifs Flame + trunk Identity Themes Motifs Modern + trunk Identity Themes Motifs + trunk +
+ trunk/Identity/Themes/Motifs/Flame + trunk Identity Themes Motifs Flame + + Goals + This section describes the steps we followed to construct the Flame artistic motif. This section may be useful for anyone interested in reproducing the Flame artistic motif, or in creating new artistic motifs for The CentOS Project corporate visual identity (see trunk Identity). + + + + Description + The Flame artistic motif was built using the flame filter of Gimp 2.2 in CentOS 5.5. + The flame filter of Gimp can produce stunning, randomly generated fractal patterns. The flame filter of Gimp gives us a great oportunity to reduce the time used to produce new artistic motifs, because of its “randomly generated” nature. Once the artistic motif be created, it is propagated through all visual manifestations of CentOS Project corporate visual identity using the centos-art.sh script (see trunk Scripts Bash) inside the CentOS Artwork Repository. + To set the time intervals between each new visual style production, we could reuse the CentOS distribution major release schema. I.e., we could produce a new visual style, every two years, based on a new “randomly generated” flame pattern, and publish the whole corporate visual identity (i.e., distribution stuff, promotion stuff, websites stuff, etc.) with the new major release of CentOS distribution all together at once. + Producing a new visual style is not one day's task. Once we have defined the artistic motif, we need to propagate it through all visual manifestations of The CentOS Project corporate visual identity. When we say that we could produce one new visual style every two years we really mean: to work two years long in order to propagate a new visual style to all visual manifestations of The CentOS Project corporate visual identity. + Obviously, in order to propagate one visual style to all different visual manifestations of The CentOS Project corporate visual identity, we need first to know which the visual manifestations are. To define which visual manifestations are inside The CentOS Project corporate visual identity is one of the goals the CentOS Artwork Repository and this documentation manual are both aimed to satisfy. + Once we define which the visual manifestation are, it is possible to define how to produce them, and this way, organize the automation process. Such automation process is one of the goals of centos-art.sh script. + With the combination of both CentOS Artwork Repository and centos-art.sh scripts we define work lines where translators, programmers, and graphic designers work together to distribute and reduce the amount of time employed to produce The CentOS Project monolithic corporate identity. + From a monolithic corporate visual identity point of view, notice that we are producing a new visual style for the same theme (i.e., Flame). It would be another flame design but still a flame design. This idea is very important to be aware of, because we are somehow “refreshing” the theme, not changing it at all. + This way, as we are “refreshing” the theme, we still keep oursleves inside the monolithic conception we are trying to be attached to (i.e., one unique name, and one unique visual style for all visual manifestations). + Producing artistic motifs is a creative process that may consume long time, specially for people without experienced knowledge on graphic design land. Using “randomly generated” conception to produce artistic motifs could be, practically, a way for anyone to follow in order to produce maintainable artistic motifs in few steps. + Due to the “randomly generated” nature of Flame filter, we find that Flame pattern is not always the same when we use Flame filter interface. + Using the same pattern design for each visual manifestation is essential in order to maintain the visual connection among all visual manifestations inside the same theme. Occasionally, we may introduce pattern variations in opacity, size, or even position but never change the pattern design itself, nor the color information used by images considered part of the same theme. + + Important When we design background images, which are considered part of the same theme, it is essential to use the same design pattern always. This is what makes theme images to be visually connected among themeselves, and so, the reason we use to define the word “theme” as: a set of images visually connected among themeselves. + + In order for us to reproduce the same flame pattern always, Flame filter interface provides the Save and Open options. The Save option brings up a file save dialog that allows you to save the current Flame settings for the plug-in, so that you can recreate them later. The Open option brings up a file selector that allows you to open a previously saved Flame settings file. + The Flame settings we used in our example are saved in the file: + + + + + Construction + + Step 1: Set image size + Create an empty image and fill the Background layer with black (000000) color. Image dimensions depend on the final destination you plan to use the image for. For the sake of our construction example we used an image of 640x480 pixels and 300 pixels per inch (ppi). + + + + Step 2: Add base color and pattern information + Create a new layer named Base, place it over Background layer and fill it with the base color (7800ff) you want to have your background image set in. Add a mask to Base layer using radial gradient and blur it. You may need to repeat this step more than once in order to achieve a confortable black radial degradation on the right side of your design. + Duplicate Base layer and name it Paper. Place Paper layer over Base layer. Remove content of Paper layer and fill it with Paper (100x100) pattern. Once you've done with black radial degradation, reduce the Paper layer opacity to 20%. + Notice that when we duplicate one layer, the mask information related to layer is preserved from previous to next layer. This saves us some of the time required to produce different layers with the same mask information on them. + Duplicate Paper layer and rename it Stripes. Remove paper pattern from Stripes layer. Fill Stripes layer with Stripes (48x48) pattern and reduce the Stripes layer opacity to 15%. + + + + Step 3: Add flame motif + Create a new layer named Flame. Set the foreground (003cff) and background (0084ff) colors to the gradient you want to build the flame motif. + To build flame motif, use the flame filter (Filters > Render > Nature > Flame...) on Flame layer. We used a layer mask, with a radial gradient on it to control the boundaries of flame motif on Flame layer. + Duplicate Flame layer and rename it `Flame Blur'. Place `Flame Blur' below Flame layer. Apply Gussian blur filter (Filters > Blur > Gussian Blur...) until reaching the desiered effect. + The opacity value, in Flame layers, may vary from one image to another based on the place the image will be finally placed on. For example, images used as desktop background have the Flame layer opacity set at 100% but Flame Blur is set to 70%. However, you may find that background images used in anaconda progress slides have opacity reduced differently, in order to reduce brightness in a way that texts could look clean and readable over it. + + + + Step 4: Add foreground color + Create a new layer named Color, place it on top of all visible layers and fill it with plain color (4c005a). Reduce Color layer opacity to 20%. You can use the Color layer to control the right side color information you want to produce the image for. + Duplicate Flame layer and create a new layer named Color#1. Place Color#1 layer on top of layer named Color. Remove the mask information from Color#1 layer and recreate a new one using an inverted alpha channel as reference. Remove Color#1 layer content and fill it back with plain black (000000) color. Reduce Color#1 opacity to 20%. In this step we created a mask to protect the flame artistic motif from black color, so when we decrement or increment the opacity of layer, the flame artistic motif wouldn't be affected, just the environment suround it. + When you set color information, remember that the same artistic motif needs to be indexed to 14 and 16 colors, in order to produce Grub and Syslinux visual manifestations respectively. Using many different colors in the artistic motif may reduce the possibility of your design to fix all different situations in. Likewise, using more colors in one design, and less colors in another design will reduce the connectivity among your designs, since color information is relevant to visual identity. + When you propagate your artistic motif visual style to different visual manifestations of CentOS Project corporate visual identity, it is up to you to find out justice and compromise among all possible variables you may face. + + + + + See also + + + trunk Identity Themes Motifs + trunk Identity Themes Motifs + + + + trunk Identity Themes + trunk Identity Themes + + + + trunk Identity + trunk Identity + + + + trunk + trunk + + + + +
+ + + trunk Identity Themes Motifs Modern + trunk Identity Themes Motifs Modern Backgrounds + trunk Identity Themes Motifs Flame + trunk +
+ trunk/Identity/Themes/Motifs/Modern + trunk Identity Themes Motifs Modern + + Presentation + + + + Construction + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Identity Themes Motifs Modern Backgrounds + trunk Identity Themes Motifs Modern Backgrounds Img + trunk Identity Themes Motifs Modern + trunk +
+ trunk/Identity/Themes/Motifs/Modern/Backgrounds + trunk Identity Themes Motifs Modern Backgrounds + + Goals + + • + + Organize background images for Modern theme. + + + + + + Description + Inside Motifs directory, the Backgrounds/ directory is used to 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 the import feautre of Inkscape. + 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 (e.g. Anaconda), 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 artistic motif. + Background images are linked (using the import feature of Inkscape) inside almost all theme art works. This structure let you make centralized changes on the visual identity and propagate them quickly to other areas. + In this structure you design background images for different screen resolutions based on the theme artistic motif. + You may create different artistic motifs propositions based on the same conceptual idea. The conceptual idea is what defines a theme. Artistic motifs are interpretations of that idea. + Inside this directory artistic motifs are organized by name (e.g., TreeFlower, Modern, etc.). + Each artistic motif directory represents just one unique artistic motif. + The artistic motif is graphic design used as common pattern to connect all visual manifestations inside one unique theme. The artistic motif is based on a conceptual idea. Artistic motifs provide visual style to themes. + Designing artistic motifs is for anyone interested in creating beautiful themes for CentOS. When building a theme for CentOS, the first design you need to define is the artistic motif. + Inside CentOS Artwork Repository, theme visual styles (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 Motifs/ directory using the model name, and 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. + + + + Usage + The Backgrounds/ directory is probably the core component, inside Motifs/ directory structure. Inside Backgrounds/ directory you produce background images used by almost all theme models (e.g., Distribution, Websites, Promotion, etc.). The Backgrounds/ directory can contain subdirectories to help you organize the design process. + + + + See also + + + trunk Identity Themes Motifs Modern Backgrounds Img + trunk Identity Themes Motifs Modern Backgrounds Img + + + + trunk Identity Themes Motifs Modern Backgrounds Tpl + trunk Identity Themes Motifs Modern Backgrounds Tpl + + + + trunk Identity Themes Motifs Modern Backgrounds Xcf + trunk Identity Themes Motifs Modern Backgrounds Xcf + + + + + +
+ + + trunk Identity Themes Motifs Modern Backgrounds Img + trunk Identity Themes Motifs Modern Backgrounds Tpl + trunk Identity Themes Motifs Modern Backgrounds + trunk +
+ trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img + trunk Identity Themes Motifs Modern Backgrounds Img + + Goals + + • + + ... + + + + + + Description + + + + 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. + + + + See also + + + +
+ + + trunk Identity Themes Motifs Modern Backgrounds Tpl + trunk Identity Themes Motifs Modern Backgrounds Xcf + trunk Identity Themes Motifs Modern Backgrounds Img + trunk +
+ trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl + trunk Identity Themes Motifs Modern Backgrounds Tpl + + Goals + + • + + ... + + + + + + Description + + + + 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. + + + + See also + + + +
+ + + trunk Identity Themes Motifs Modern Backgrounds Xcf + trunk Identity Themes Motifs Modern Distro Anaconda Progress + trunk Identity Themes Motifs Modern Backgrounds Tpl + trunk +
+ trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf + trunk Identity Themes Motifs Modern Backgrounds Xcf + + Goals + + • + + ... + + + + + + Description + + • + + ... + + + + + + Usage + In this directory is where you store the project files (e.g, .xcf) of Gimp. 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 background projects. Of course, you can merge both Gimp and Inkscape power to produce images based on them. In this last case you need the Xcf/ directory. + + + + See also + + + +
+ + + trunk Identity Themes Motifs Modern Distro Anaconda Progress + trunk Identity Themes Motifs Modern Palettes + trunk Identity Themes Motifs Modern Backgrounds Xcf + trunk +
+ trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress + trunk Identity Themes Motifs Modern Distro Anaconda Progress + + Goals + + • + + ... + + + + + + Description + + + + Usage + To render Anaconda progress slide images using the Modern artistic motif design, the Default theme model, and available translation files (— Removed(pxref:trunk Translations Identity Themes Distro Anaconda Progress) —); use the following commands: + cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ +centos-art render --identity + The above command will create the following structure: + trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress +|-- 3 +| |-- en +| | |-- 01-welcome.png +| | |-- 02-donate.png +| | `-- 03-yum.png +| `-- es +| |-- 01-welcome.png +| |-- 02-donate.png +| `-- 03-yum.png +|-- 4 +| |-- en +| | |-- 01-welcome.png +| | |-- 02-donate.png +| | `-- 03-yum.png +| `-- es +| |-- 01-welcome.png +| |-- 02-donate.png +| `-- 03-yum.png +`-- 5 + |-- en + | |-- 01-welcome.png + | |-- 02-donate.png + | `-- 03-yum.png + `-- es + |-- 01-welcome.png + |-- 02-donate.png + `-- 03-yum.png + + + + See also + + + +
+ + + trunk Identity Themes Motifs Modern Palettes + trunk Identity Themes Motifs TreeFlower + trunk Identity Themes Motifs Modern Distro Anaconda Progress + trunk +
+ trunk/Identity/Themes/Motifs/Modern/Palettes + trunk Identity Themes Motifs Modern Palettes + + Goals + + • + + Organize palette files for Modern theme. + + + + + + Description + + + + 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 the unique color information required by theme. + + + + See also + + + +
+ + + trunk Identity Themes Motifs TreeFlower + trunk Identity Themes Motifs TreeFlower Backgrounds + trunk Identity Themes Motifs Modern Palettes + trunk +
+ trunk/Identity/Themes/Motifs/TreeFlower + trunk Identity Themes Motifs TreeFlower + + Goals + + • + + ... + + + + + + Description + + + + Usage + + + + See also + + + +
+ + + trunk Identity Themes Motifs TreeFlower Backgrounds + trunk Identity Widgets + trunk Identity Themes Motifs TreeFlower + trunk +
+ trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds + trunk Identity Themes Motifs TreeFlower Backgrounds + + Goals + This section exists to orgnize backgrounds of TreeFlower artistic motif. + + + + Description + + Desktop background + Once you have defined the vectorial artistic motif design, use the centos-art.sh script (as described in usage section below) to produce the png version of it. With the png version of your vectorial design do the following: + Open the png version with GIMP. + Save the png version as a project of GIMP inside trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Xcf directory, using the same name of your vectorial design but with the .xcf extension. + Now use GIMP to improve your design. Here you may add one layer for pattern, another for colors, and so on until you find yourself confortable with your artwork. For example, the following layer distribution (from bottom to top) was used to build revision 285 of file 1360x768.xcf using TreeFlower artistic motif at revision 241. + + + Layer 1: Background + + The first thing we did with GIMP was to create a layer named Background to store the artistic motif (File > Open as layer). This layer is the lowest layer in the image. Later, we started to create layers one upon another to change the artistic motif visual style. + + + + Layer 2: Shadow#1 + + This layer is above Background and contains a linear gradient from left (000000) to right (transparent) covering the whole image. This layer masks the artistic motif to avoid the effect of linear gradient. This layer is 100% of opacity. + + + + Layer 3: Shadow#2 + + This layer is above Shadow#1 and contains a linear gradient from left (000000) to right (transparent) covering just the 70% of the whole image aproximatly. This layer doesn't mask the artistic motif which make the left part of it fall into the dark of linear gradient. This layer is 100% of opacity. + + + + Layer 4: Pattern (Paper) + + This layer is above Shadow#2 an contains the paper pattern shipped with GIMP 2.2. This layer doesn't mask the artistic motif so the pattern is applied over the whole image. This layer is set to 15% of opacity. + + + + Layer 5: Pattern (Stripes) + + This layer is above Pattern (Paper) and contains the stripes used over the artistic motif. This layer do masks the artistic motif so the stripes are only applied to it. This layer is set to 10% of opacity. + + + + Layer 6: Shadow#3 + + This layer is above Pattern (Stripes) and contains a linear gradient from right (6600ff) to left (transparent). This layer masks the artistic motif so the linear gradient doesn't affect it. This layer is set to 15% of opacity. + + + + Layer 7: Shadow#4 + + This layer is above Shadow#3 and contains a linear gradient from left (000000) to right (transparent). This layer do masks the artistic motif so the linear gradient doesn't affect it. This layer is set to 10% of opacity. + + + + Layer 8: Color#1 + + This layer is above Shadow#4 and is filled with orange (ffae00) color over the whole image. This layer is set to 10% of opacity. + + + + Layer 9: Color#2 + + This layer is above Color#1 and is filled with blue (010a88) color over the whole image. This layer is set to 10% of opacity. + + +
+ + Note There is no definite combination. To get the appropriate visual design is a matter of constant testing and personal taste. + + Finally, use Save as copy ... option to export the final design. To export the final design use the same name of your vectorial design plus -final.png extension. + You can repeat these steps to create images for other screen resolutions. + + + + Anaconda Prompt (syslinux) background + When building syslinux backgrounds it is needed to take into account that the final image is reduced to 16 colors. In desktop background there is no color limitation but syslinux does have. The goal of this section is achieving a final syslinux background as close as possible to desktop backgrounds using 16 colors only. + Another point to consider is the forground and background definition used by syslinux. The syslinux documentation says that the color set in position 0 is the background and color set in position 7 is the forground. The final palette of color used by our background will match that specification. For great contrast we'll use black as background and white as forground. At this poing we have black (000000) and white (ffffff) colors in our syslinux palette, which left us with 14 colors to play with. + Let's begin with Xcf/640x300.xcf layer distribution from bottom to top: + + + Layer 1: Background + + This layer is the lowest layer in the image composition and contains the artistic motif image rendered for the same resolution (i.e., Img/Png/640x300.png). This layer is set to 100% of opacity. + + + + Layer 2: Pattern (Paper) + + This layer is placed above Background layer and contains the paper pattern shipped with GIMP 2.2. This layer doesn't mask the artistic motif. This layer is set to 30% of opacity. + + + + Layer 3: Pattern (Stripes) + + This layer is placed above Pattern (Paper) layer and contains the stripes pattern shipped with GIMP 2.2. This layer does mask the artistic motif in order to apply the stripes over it only. The background is not affected by the stripes pattern just the artistic motif. This layer is set to 20% of opacity. + + + + Layer 4: Shadow#1 + + This layer is placed above Pattern (Stripes) layer and fills the entire layer area with violet (6600ff) color. This layer do mask the artistic motif in order to applied the violet color to the background area outside the artistic motif only. This layer is set to 15% of opacity. + + + + Layer 5: Color#1 + + This layer is above Shadow#1 and is filled with orange (ffae00) color to cover the whole image. This layer is set to 10% of opacity. + + + + Layer 6: Color#2 + + This layer is above Color#1 and is filled with blue (010a88) color to cover the whole image. This layer is set to 10% of opacity. + + + + Layer 7: Shadow#2 + + This layer is above Color#1 and contains a linear gradient from left (000000) to right (transparent) covering 70% of the image approximately. + + +
+ At this point we have the composition and should look like the desktop backgrounds. Compared with desktop backgrounds there are some differences in opacity. This is because in our testings the final color information found with this composition produces an acceptable 16 color image. Of course this is something we haven't seen yet. + To define the color information of our current coposition, save the syslinux background composition we've done using File > Save as Copy ... option in the following location: + + Now, create the final png version of syslinux backgrounds using the following command: + + This command will create syslinux-splash final images for all major releases of CentOS distribution the repository has been configured to. The important files here are syslinux-splash.png, other files may contain the wrong information because we haven't defined yet the correct color information to use. + Open one syslinux-splash.png file with GIMP and use the Image > Mode > Indexed to reduce image colors up to 16 colors, using the Generate optimum palette feature of GIMP. If the image looks aceptable after reducing colors, use the Palettes menu (Ctrl+P) of GIMP to import a new palette from file and name it CentOS-TreeFlower-Syslinux. Once you've saved the palette, the color information is stored at: + + You need to edit CentOS-TreeFlower-Syslinux.gpl file in order to set the appropriate order of colors. Remember black (000000) in position 0, and white (ffffff) in position 7. Other positions are irrelevant. When editing this file you may find that color reduction did not set black and white colors to their respective values exactly. Change that manually. For example, consider the following palette: + + Update the Palettes menu to get the new color positions from the file you just edited and open the palette with double click. + Update the syslinux.gpl file copying the following file: + + to + + With the CentOS-TreeFlower-Syslinux palette opened in the Palette Editor, open (Ctrl+O) the following file: + + and replace its color information with that one in CentOS-TreeFlower-Syslinux palette. When you are replacing color information inside syslilnux.ppm, remember to keep the order of colors just as they are in the CentOS-TreeFlower-Palette palette. + The syslinux.ppm file is 16 pixels width and 1 pixel height, so you probably need to zoom it a bit to set the color information in their place when using the pen tool with the brush Circle (01) (1 x 1). + Once you've updated the syslinux.ppm file, it is time to update the following file: + + The syslinux.hex file contains the color information in hexadecimal notation. The color information in hexadecimal notation is required by ppmtolss16 command. The ppmtolss16 command produces the final LSS16 image format that is used by syslinux program inside CentOS distribution. + The color information inside syslinux.hex must match the one in syslinux.ppm and syslinux.gpl. For example, based on CentOS-TreeFlower-Syslinux palette of colors above, consider the following syslinux.hex file: + + + + + Grub background + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Identity Widgets + trunk Locales + trunk Identity Themes Motifs TreeFlower Backgrounds + trunk +
+ trunk/Identity/Widgets + trunk Identity Widgets + + Goals + + • + + ... + + + + + + Description + + + + Usage + + + + See also + + + +
+ + + trunk Locales + trunk Locales Identity + trunk Identity Widgets + trunk +
+ trunk/Locales + trunk LocalesThe trunk/Locales directory exists to store the translation messages used to produce content in different languages. + Translation messages are organized using the directory structure of the component being translated. For example, if we want to provide translation messages for trunk/Manuals/Filesystem, then the trunk/Locales/Manuals/Filesystem directory needs to be created. + Once the locale directory exists for the component we want to provide translation messages for, it is necessary to create the translation files where translation messages are. The translation files follows the concepts of xml2po and GNU gettext tools. + The basic translation process is as follow: first, translatable strings are extracted from files and a portable object template (.pot) is created or updated with the information. Using the portable object template, a portable object (.po) is created or updated for translator to locale the messages retrived. Finally, a machine object (.mo) is created from portable object to sotore the translated messages. + Inside the repository there are two ways to retrive translatable strings from files. The first one is through xml2po command and the second through xgettext command. The xml2po is used to retrive translatable strings from XML files (e.g., Scalable Vector Graphics, DocBook, etc.) and the xgettext command is used to retrive translatable strings from shell scripts files (e.g., the files that make the centos-art.sh command-line interface). + When translatable strings are retrived from XML files, using the xml2po command, there is no need to create the machine object as we do when translatable strings ar retrived from shell files, using the xgettext command. The xml2po produces a temporal machine object in order to create a translated XML file. Once the translated XML file has been created the machine object is no longer needed. On the other hand, the machine object produced by the xgettext command is required by the system in order for the show shell script localized messages. + Another difference between xml2po and xgettext we need to be aware of is the directory structure used to store machine objects. In xml2po, the machine object is created in the current working directory as .xml2po.mo and can be safetly removed once the translated XML file has been created. In the case of xgettext, the machine object needs to be stored in the $TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo file in order for the system to interpret it and should not be removed since it is the file that contain the translation messages themselves. + Automation of localization tasks is achived through the locale functionality of command-line interface. + + + trunk Scripts Bash Cli Functions Locale + trunk Scripts Bash Cli Functions Locale + + + +
+ + + trunk Locales Identity + trunk Locales Identity Brands + trunk Locales + trunk +
+ trunk/Locales/Identity + trunk Locales Identity + + Goals + + • + + ... + + + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + + + + + + + trunk Identity + trunk Identity + + + + +
+ + + trunk Locales Identity Brands + trunk Locales Identity Brands Tpl + trunk Locales Identity + trunk +
+ trunk/Locales/Identity/Brands + trunk Locales Identity Brands + + Goals + + • + + Organize brands' translation files. + + + + + + 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: + + 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: + + + Conventional file names + Translation brands 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. + + + + Numeric file names + Translation brands 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 designing ratio. + For example, if your design template has 400x200 pixels of dimension, and you apply a translation file named `300.sed' to it, the final image you get as result will have 300x100 pixels of dimension. The same is true if you use higher numbers like `1024.sed', `2048.sed', etc. In these cases you have bigger images proportionally. + As we are using scalable vector graphics to design identity templates, the image size you produce is not limitted in size. You can use one design template produced in 400x200 pixels to produce larger or shorter PNG images using numeric translation files as described above. + + + + Translation markers + Inside trunk/Translations/Identity/Brands/, translation files combine the following translation markers: + + + #000000 + + Specify which color to use when rendering brand images. + + 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. + + + +
+ + + + + Usage + How to render brands' translation files To render brands' translation files, use the following command: + + + + + See also + + + + trunk Identity Brands + trunk Identity Brands + + + + +
+ + + trunk Locales Identity Brands Tpl + trunk Locales Identity Fonts + trunk Locales Identity Brands + trunk +
+ trunk/Locales/Identity/Brands/Tpl + trunk Locales Identity Brands Tpl + + Goals + + + + Description + + + + Usage + + + + See also + + + +
+ + + trunk Locales Identity Fonts + trunk Locales Identity Models + trunk Locales Identity Brands Tpl + trunk +
+ trunk/Locales/Identity/Fonts + trunk Locales Identity Fonts + + Goals + This section exists to organize fonts translation files. + + + + Description + Translation files, inside trunk/Translations/Fonts, have the following structure: + + 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 Do not create translation files for font-families not used somewhere inside CentOS visual identity. The identity of font entry (see trunk Identity Fonts) is used as reference when someone needs to know which font-families are allowed to use inside CentOS visual identity. + + + + 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. + + +
+ + + + + Usage + How to render fonts' translation files 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: + + + + + See also + + + trunk Identity Fonts + trunk Identity Fonts + + + + +
+ + + trunk Locales Identity Models + trunk Locales Identity Release + trunk Locales Identity Fonts + trunk +
+ trunk/Locales/Identity/Models + trunk Locales Identity Models + + Goals + + + + Description + + + + Usage + + + + See also + + + +
+ + + trunk Locales Identity Release + trunk Locales Identity Themes + trunk Locales Identity Models + trunk +
+ trunk/Locales/Identity/Release + trunk Locales Identity Release + + Goals + + + + Description + + + + Usage + + + + See also + + + +
+ + + trunk Locales Identity Themes + trunk Locales Identity Themes Backgrounds + trunk Locales Identity Release + trunk +
+ trunk/Locales/Identity/Themes + trunk Locales Identity Themes + + Goals + + + + Description + + + + Usage + + + + See also + + + +
+ + + trunk Locales Identity Themes Backgrounds + trunk Locales Identity Themes Distro Anaconda Progress + trunk Locales Identity Themes + trunk +
+ trunk/Locales/Identity/Themes/Backgrounds + trunk Locales Identity Themes Backgrounds + + Goals + + • + + ... + + + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Locales Identity Themes Distro Anaconda Progress + trunk Locales Identity Widgets + trunk Locales Identity Themes Backgrounds + trunk +
+ trunk/Locales/Identity/Themes/Distro/Anaconda/Progress + trunk Locales Identity Themes Distro Anaconda Progress + + Goals + + • + + Organize Anaconda progress translation templates. + + + Organize Anaconda progress translation files in several languages and major releases of CentOS distribution. + + + + + + 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. + + • + + See trunk Identity Themes Motifs Modern Distro Anaconda Progress. + + + + + + Usage + Translation rendering is described in trunk/Translations documentation entry (— Removed(pxref:trunk Translations) —). + + + + See also + +
+ + + trunk Locales Identity Widgets + trunk Manuals + trunk Locales Identity Themes Distro Anaconda Progress + trunk +
+ trunk/Locales/Identity/Widgets + trunk Locales Identity Widgets + + Goals + + • + + ... + + + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + + +
+ + + trunk Manuals + trunk Scripts + trunk Locales Identity Widgets + trunk +
+ trunk/Manuals + trunk Manuals + + Goals + + • + + ... + + + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Scripts + trunk Scripts Bash + trunk Manuals + trunk +
+ trunk/Scripts + trunk Scripts + + Goals + The trunk/Scripts directory exists to: + + • + + Organize the “trunk” development line of automation scripts by programming language. + + + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Scripts Bash + trunk Scripts Bash Cli + trunk Scripts + trunk +
+ trunk/Scripts/Bash + trunk Scripts Bash + + Goals + The trunk/Scripts/Bash directory exists to organize the trunk development line of centos-art.sh automation script. The centos-art.sh script standardizes frequent tasks inside your working copy of CentOS Artwork Repository. + + + + Description + The best way to understand centos-art.sh automation script is studying its source code. However, as start point, you may prefer to read an introductory resume before diving into the source code details. + The centos-art.sh script is written in Bash. Most tasks, inside centos-art.sh script, have been organized in many specific functionalities that you can invoke from the centos-art command-line interface. + 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 location. If your system was prepared to use CentOS Artwork Repository correctly (— Removed(pxref:trunk Scripts Bash Functions Verify) —), you should have a symbolic link inside ~/bin/ directory that points to the centos-art.sh script file. As ~/bin/ directory is, by default, inside PATH environment variable, the execution of centos-art command runs the centos-art.sh script. + When centos-art.sh script is executed, the first it does is executing the trunk/Scripts/Bash/initEnvironment.sh script to initialize global variables (e.g., gettext variables) and global function scripts. Global function scripts are located inside trunk/Scripts/Bash/Functions directory and their file names begin with cli. Global function scripts provide common functionalities that can be used anywhere inside centos-art.sh script execution environment. + Once global variables and function scripts have been loaded, centos-art.sh script executes the cli global function from cli.sh function script to retrive command-line arguments and define some default values that may be used later by specific function scripts (— Removed(pxref:trunk Scripts Bash Functions) —). + As convenction, the centos-art.sh command-line arguments have the following format: + + In the above example, centos-art is the command you use to invoke centos-art.sh script. The arg1 is required and represents the functionality you want to perform (e.g., , , , , etc.). The remaining arguments are modifiers to . The definition is required and represets, specifically, the action inside the functionality you want to perform. The and on, are optional. + Once command-line arguments have been retrived, the centos-art.sh script loads specific functionalities using the cli_getFunctions.sh function script. Only one specific functionality can be loaded at one script execution I.e., you run centos-art.sh script to run just one functionality. + + Figure + + ~/artwork/trunk/Scripts/Bash/centos-art.sh | ++---v-----------------------------------------v------------------------+ + | centos-art.sh | + +---v---------------------------------v---+ + . | initEnvironment.sh | . + . +---------------------------------+ . + . | cli $@ | . + . +---v-------------------------v---+ . + . . | cli_getFunctions | . . + . . +---v-----------------v---+ . . + . . . | function1 | . . . + . . . | function2 | . . . + . . . | function3 | . . . + . . . +-----------------+ . . . + . . ........................... . . + . ................................... . + ........................................... +]]> + The functionalities initialization environment. + + Functionalities are implemented by means of actions. Once the functionality has been initiazalized, actions initialization take place for that functionality. Actions initialization model is very similar to functions initialization model. But with the difference, that actions are loaded inside function environment, and so, share variables and functions defined inside function environment. + + Figure + + + The actions initialization environment. + + + + + Usage + The centos-art.sh script usage information is described inside each specific function documentation (— Removed(pxref:trunk Scripts Bash Functions) —). + + + + See also + + + trunk Scripts + trunk Scripts + + + + + + +
+ + + trunk Scripts Bash Cli + trunk Scripts Bash Cli Functions + trunk Scripts Bash + trunk +
+ trunk/Scripts/Bash/Cli + trunk Scripts Bash Cli +
+ + + trunk Scripts Bash Cli Functions + trunk Scripts Bash Cli Functions Help + trunk Scripts Bash Cli + trunk +
+ trunk/Scripts/Bash/Cli/Functions + trunk Scripts Bash Cli Functions + + Goals + The trunk/Scripts/Bash/Functions directory exists to organize centos-art.sh specific functionalities. + + + + Description + The specific functions of centos-art.sh script are designed with “Software Toolbox” philosophy (see Toolbox introductioncoreutils.info) in mind: each program “should do one thing well”. Inside centos-art.sh script, each specific functionality is considered a program that should do one thing well. Of course, if you find that they still don't do it, feel free to improve them in order for them to do so. + The specific functions of centos-art.sh script are organized inside specific directories under trunk/Scripts/Bash/Functions location. Each specific function directory should be named as the function it represents, with the first letter in uppercase. For example, if the function name is render, the specific function directory for it would be trunk/Scripts/Bash/Functions/Render. + To better understand how specific functions of centos-art.sh script are designed, lets create one function which only goal is to output different kind of greetings to your screen. + When we create specific functions for centos-art.sh script it is crucial to know what these functions will do exactly and if there is any function that already does what we intend to do. If there is no one, it is good time to create them then. Otherwise, if functionalities already available don't do what you exactly expect, contact their authors and work together to improve them. + + Tip Join CentOS developers mailing list centos-art@centos.org to share your ideas. + + It is also worth to know what global functions and variables do we have available inside centos-art.sh script, so advantage can be taken from them. Global variables are defined inside global function scripts. Global functions scripts are stored immediatly under trunk/Scripts/Bash/Functions directory, in files begining with cli prefix. + OK, let's begin with our functionality example. + What function name do we use? Well, lets use greet. Note that hello word is not a verb; but an expression, a kind of greeting, an interjection specifically. In contrast, greet is a verb and describes what we do when we say Hello!, Hi!, and similar expressions. + So far, we've gathered the following function information: + + The greet.sh function script is the first file centos-art.sh script loads when the greet functionality is called using commands like centos-art greet --hello='World'. The greet.sh function script contains the greet function definition. + Inside centos-art.sh script, as convenction, each function script has one top commentary, followed by one blank line, and then one function defintion below it only. + Inside centos-art.sh script functions, top commentaries have the following components: the functionality description, one-line for copyright note with your personal information, the license under which the function source code is released —the centos-art.sh script is released as GPL, so do all its functions—, the $Id$ keyword of Subversion is later expanded by svn propset command. + In our greet function example, top commentary for greet.sh function script would look like the following: + + After top commentary, separated by one blank line, the greet function definition would look like the following: + + The first definition inside greet function, are global variables that will be available along greet function execution environment. This time we didn't use global variable definitions for greet function execution environment, so we left that section empty. + Later, we call greet_getActions function to define the command-line interface of greet functionality. The command-line interface of greet functionality defines what and how actions are performed, based on arguments combination passed to centos-art.sh script. + + The ACTIONNAM global variable is defined in cli.sh function script and contains the value passed before the equal sign (i.e., =) in the second command-line argument of centos-art.sh script. For example, if the second command-line argument is , the value of ACTIONNAM variable would be --hello. Using this configuration let us deside which action to perform based on the action name passed to centos-art.sh script as second argument. + The greet function definition makes available two valid greetings through and options. If no one of them is provided as second command-line argument, the * case is evaluated instead. + The * case and its two lines further on should always be present in _getActions.sh function scripts, no matter what specific functionality you are creating. This convenction helps the user to find out documentation about current functionality in use, when no valid action is provided. + The greet_doHello and greet_doBye function definitions are the core of greet specific functionality. In such function definitions we set what our greet function really does: to output different kinds of greetings. + + The greet_doHello function definition is stored in greet_doHello.sh function script. + + The greet_doBye function definition is stored in the greet_doBye.sh function script. + Both greet_doHello.sh and greet_doBye.sh function scripts are stored inside greet function directory path (i.e. trunk/Scripts/Bash/Functions/Greet). + The ACTIONVAL global variable is defined in cli.sh function script and contains the value passed after the equal sign (i.e., =) in the second command-line argument of centos-art.sh script. For example, if the second command-line argument is , the value of ACTIONVAL variable would be World without quotes. + Let's see how greet specific functionality files are organzied under greet function directory. To see file organization we use the tree command: + + To try the greet specific functionality we've just created, pass the function name (i.e., greet) as first argument to centos-art.sh script, and any of the valid options as second argument. Some examples are illustrated below: + + The word World in the examples above can be anything. In fact, change it to have a little fun. + Now that we have a specific function that works as we expect, it is time to document it. To document greet specific functionality, we use its directory path and the manual functionality (— Removed(pxref:trunk Scripts Bash Functions Manual) —) of centos-art.sh script, just as the following command illustrates: + + To have a well documented function helps user to understand how your function really works, and how it should be used. When no valid action is passed to a function, the centos-art.sh script uses the function documentation entry as vehicle to communicate which the valid functions are. When no documentation entry exists for a function, the centos-art.sh script informs that no documentation entry exists for such function and requests user to create it right at that time. + Now that we have documented our function, it is time to translate its output messages to different languages. To translate specific functionality output messages to different languages we use the locale functionality (— Removed(pxref:trunk Scripts Bash Functions Locale) —) of centos-art.sh script, just as the following command illustrates: + + + Warning To translate output messages in different languages, your system locale information —as in LANG environment variable— must be set to that locale you want to produce translated messages for. For example, if you want to produce translated messages for Spanish language, your system locale information must be set to es_ES.UTF-8, or similar, first. + + Well, it seems that our example is rather complete by now. + In greet function example we've described so far, we only use cli_printMessage global function in action specific function definitions in order to print messages, but more interesting things can be achieved inside action specific function definitions. For example, if you pass a directory path as action value in second argument, you could retrive a list of files from therein, and process them. If the list of files turns too long or you just want to control which files to process, you could add the third argument in the form and reduce the amount of files to process using a regular expression pattern. + The greet function described in this section may serve you as an introduction to understand how specific functionalities work inside centos-art.sh script. With some of luck this introduction will also serve you as motivation to create your own centos-art.sh script specific functionalities. + By the way, the greet functionality doesn't exist inside centos-art.sh script yet. Would you like to create it? + + + + Usage + + Global variables + The following global variables of centos-art.sh script, are available for you to use inside specific functions: + + TEXTDOMAIN + Variable + TEXTDOMAIN + + + Default domain used to retrieve translated messages. This value is set in initFunctions.sh and shouldn't be changed. + + + + TEXTDOMAINDIR + Variable + TEXTDOMAINDIR + + + Default directory used to retrieve translated messages. This value is set in initFunctions.sh and shouldn't be changed. + + + + FUNCNAM + Variable + FUNCNAM + + + Define function name. + Function names associate sets of actions. There is one set of actions for each unique function name inside centos-art.sh script. + Dunction names are passed as first argument in centos-art.sh command-line interface. For example, in the command centos-art render --entry=path/to/dir --filter=regex, the ACTION passed to centos-art.sh script is . + When first argument is not provided, the centos-art.sh script immediatly ends its execution. + + + + FUNCDIR + Variable + FUNCDIR + + + + FUNCDIRNAME + Variable + FUNCDIRNAME + + + + FUNCSCRIPT + Variable + FUNCSCRIPT + + + + FUNCCONFIG + Variable + FUNCCONFIG + + + + ACTIONNAM + Variable + ACTIONNAM + + + Define action name. + Each action name identifies an specific action to perform, inside an specific function. + Action name names aare passed as second argument in centos-art.sh command-line interface. For example, in the command centos-art render --entry=path/to/dir --filter=regex, the ACTIONNAM passed to centos-art.sh script is . + When second argument is not provided, the centos-art.sh script immediatly ends its execution. + + + + ACTIONVAL + Variable + ACTIONVAL + + + Define action value. + Action values are associated to just one action name. Action values contain the working copy entry over which its associated action will be performed in. Working copy entries can be files or directories inside the working copy. + + + + REGEX + Variable + REGEX + + + Define regular expression used as pattern to build the list of files to process. + By default, REGEX variable is set to .+ to match all files. + Functions that need to build a list of files to process use the option to redefine REGEX variable default value, and so, control the amount of files to process. + + + + ARGUMENTS + Variable + ARGUMENTS + + + Define optional arguments. + Optional arguments, inside centos-art.sh script, are considered as all command-line arguments passed to centos-art.sh script, from third argument position on. For example, in the command centos-art render --entry=path/to/dir --filter=regex , the optional arguments are from --filter=regex argument on. + Optional arguments are parsed using getopt command through the following base construction: + + Optional arguments provide support to command options inside centos-art.sh script. For instance, consider the Subversion (svn) command, where there are many options (e.g., , , , etc), and inside each option there are several modifiers (e.g., --revision, --message, --username, etc.) that can be combined one another in their short or long variants. + The ARGUMENTS variable is used to store arguments passed from command-line for later use inside centos-art.sh script. Storing arguments is specially useful when we want to run a command with some specific options from them. Consider the following command: + + In the above command, the , and options are specific to svn copy command. In such cases, options are not interpreted by centos-art.sh script itself. Instead, the centos-art.sh script uses getopt to retrive them and store them in the ARGUMENTS variable for later use, as described in the following command: + + When getopt parses ARGUMENTS, we may use short options (e.g., ) or long options (e.g., ). When we use short options, arguments are separated by one space from the option (e.g., ). When we use long options arguments are separated by an equal sign (=) (e.g., ). + In order for getopt to parse ARGUMENTS correctly, it is required to provide the short and long definition of options that will be passed or at least supported by the command performing the final action the function script exists for. + As convenction, inside centos-art.sh script, short option definitions are set in the ARGSS variable; and long option definitions are set in the ARGSL variable. + When you define short and long options, it may be needed to define which of these option arguments are required and which not. To define an option argument as required, you need to set one colon : after the option definition (e.g., ). On the other hand, to define an option argument as not required, you need to set two colons :: after the option definition (e.g., ). + + + + EDITOR + Variable + EDITOR + + + Default text editor. + The centos-art.sh script uses default text EDITOR to edit pre-commit subversion messages, translation files, configuration files, script files, and similar text-based files. + If EDITOR environment variable is not set, centos-art.sh script uses /usr/bin/vim as default text editor. Otherwise, the following values are recognized by centos-art.sh script: + + • + + /usr/bin/vim + + + /usr/bin/emacs + + + /usr/bin/nano + + + If no one of these values is set in EDITOR environment variable, centos-art.sh uses /usr/bin/vim text editor by default. + + + + + + Global functions + Function scripts stored directly under trunk/Scripts/Bash/Functions/ directory are used to define global functions. Global functions can be used inside action specific functionalities and or even be reused inside themselves. This section provides introductory information to global functions you can use inside centos-art.sh script. + + cli_checkActionArguments + Function + cli_checkActionArguments + + + Validate action value (ACTIONVAL) variable. + The action value variable can take one of the following values: + + + Path to one directory inside the local working copy, + + + Path to one file inside the local working copy, + + + If another value different from that specified above is passed to action value variable, the centos-art.sh script prints an error message and ends script execution. + + + + cli_checkFiles + Function + cli_checkFiles + FILE + [ + TYPE + ] + + + Verify file existence. + cli_checkFiles receives a FILE absolute path and performs file verification as specified in TYPE. When TYPE is not specified, cli_checkFiles verifies FILE existence, no matter what kind of file it be. If TYPE is specified, use one of the following values: + + + + + + Ends script execution if FILE is not a directory. + When you verify directories with cli_checkFiles, if directory doesn't exist, centos-art.sh script asks you for confirmation in order to create that directory. If you answer positively, centos-art.sh script creates that directory and continues script flows normally. Otherwise, if you answer negatively, centos-art.sh ends script execution with an error and documentation message. + + + + + + + Ends script execution if FILE is not a regular file. + + + + + + + Ends script execution if FILE is not a symbolic link. + + + + + + + Ends script execution if FILE is not executable. + + + + + + Ends script execution if FILE is neither a regular file nor a symbolic link. + + + + + + Ends script execution if FILE is neither a regular file nor a directory. + + + + + + Ends script execution if FILE is not inside the working copy. + + +
+ As default behaviour, if FILE passes all verifications, centos-art.sh script continues with its normal flow. + + + + cli_commitRepoChanges + Function + cli_commitRepoChanges + [ + LOCATION + ] + + + Syncronize changes between repository and working copy. + The cli_commitRepoChanges function brings changes from the central repository down to the working copy—using svn update—, checks the working copy changes—using svn status command—, prints status report—using both svn update and svn status commands output, and finally, commits recent changes from the working copy up to the repository—using svn commit command—. + Previous to commit the working copy changes up to the central repository, the cli_commitRepoChanges function asks you to verify changes—using svn diff command—, and later, another confirmation question is shown to be sure you really want to commit changes up to central repository. + If LOCATION argument is not specified, the value of ACTIONVAL variable is used as reference instead. + + Figure + + Bringing changes from the repository into the working copy +--> Checking changes in the working copy +---------------------------------------------------------------------- +Added 0 file from the repository. +Deleted 0 file from the repository. +Updated 0 file from the repository. +Conflicted 0 file from the repository. +Merged 0 file from the repository. +Modified 4 files from the working copy. +Unversioned 0 file from the working copy. +Deleted 0 file from the working copy. +Added 0 file from the working copy. +---------------------------------------------------------------------- +]]> + The cli_commitRepoChanges function output. + + Call the cli_commitRepoChanges function before or/and after calling functions that modify files or directories inside the working copy as you may need to. + + + + cli_doParseArguments + Function + cli_doParseArguments + + + Redefine arguments (ARGUMENTS) global variable using getopt command output. For more information about how to use cli_doParseArguments function, see ARGUMENTS variable description above. + + + + cli_doParseArgumentsReDef + Function + cli_doParseArgumentsReDef + $ + @ + + + Initialize/reset arguments (ARGUMENTS) global variable using positional parameters variable ($@) as reference. + When we work inside function definitions, positional parameters are reset to the last function definition positional parameters. If you need to redefine positional parameters from one specific function, you need to call cli_doParseArgumentsReDef with the positional parameters variable ($@), set as first argument, to that specific function you want to redefine positional parameters at. + + + + cli_getArguments + Function + cli_getArguments + + + Initialize function name (FUNCNAM), action name (ACTIONNAM), and action value (ACTIONVAL) global variables, using positional parameters passed in $@ variable. + The cli_getArguments function is called from cli.sh function script, using cli function positional parameters (i.e., the positional parameters passed as arguments in the command-line) as first function argument. + Once command-line positional parameters are accesible to centos-art.sh script execution evironment, cli_getArguments uses regular expression to retrive action variables from first and second argument. The first argument defines the value used as function name (FUNCNAM), and the second argument defines both values used as action name (ACTIONNAM) and action value (ACTIONVAL), respectively. + The first argument is a word in lower case. This word specifies the name of the functionality you want to use (e.g., render to render images, manual to work on documentation, and so on.) + The second argument has a long option style (e.g., --option=value). The --option represents the action name (ACTIONNAM), and the characters inbetween the equal sign (=) and the first space character, are considered as the action value (ACTIONVAL). In order to provide action values with space characters inbetween you need to enclose action value with quotes like in --option='This is long value with spaces inbetween'. Generally, action values are used to specify paths over which the action name acts on. + Once action related variables (i.e., FUNCNAM, ACTIONNAM, and ACTIONVAL) are defined and validated, cli_getArguments shifts the positional arguments to remove the first two arguments passed (i.e., those used to retrive action related variables) and redefine the arguments (ARGUMENTS) global variable with the new positional parameters information. + + + + cli_getFunctions + Function + cli_getFunctions + + + Initialize funtionalities supported by centos-art.sh script. + Functionalities supported by centos-art.sh script are organized in functionality directories under trunk/Scripts/Bash/Functions/ directory. Each functionality directory stores function scripts to the functionality such directory was created for. Function scripts contain function definitions. Function definitions contain several commands focused on achieving one specific task only (i.e., the one such functionality was created for). + In order for centos-art.sh script to recognize a functionality, such functionality needs to be stored under trunk/Scripts/Bash/Functions/ in a directory written capitalized (i.e., the whole name is written in lowercase except the first character which is in uppercase). The directory where one specific functionality is stored is known as the functionality directory. + Inside each functionality directory, the functionalty itself is implemented through function scripts. Function scripts are organized in files independently one another and written in camelCase format with the function name as prefix. Separation between prefix and description is done using underscore (_) character. + In order for centos-art.sh script to load functionalities correctly, function definition inside function scripts should be set using the function reserved word, just as in the following example: + + The above function definition is just a convenction we use, in order to make identification of function names easier read and automate by centos-art.sh script initialization commands, once centos-art.sh script determines which functionality directory to use. Specifically, in order to initialize and export functions, centos-art.sh script executes all function scripts inside the functionality directory, and later grep on them using a regular expression pattern, where the function reserved word is used as reference to retrive the function names and export them to centos-art.sh script execution environment, and so, make function definitions —from function scripts inside the functionality directory— available for further calls. + If the functionality specified in the command-line first argument doesn't have a functionality directory, centos-art.sh script considers the functionality provided in the command-line as invalid functionality and immediatly stops script execution with an error message. + In order to keep visual consistency among function scripts, please consider using the following function script design model as template for your own function scripts: + + + + + cli_getCountryCodes + Function + cli_getCountryCodes + [ + FILTER + ] + + + Output country codes supported by centos-art.sh script. + The cli_getCountryCodes function outputs a list with country codes as defined in ISO3166 standard. When FILTER is provided, cli_getCountryCodes outputs country codes that match FILTER regular expression pattern. + + + + cli_getCountryName + Function + cli_getCountryName + [ + FILTER + ] + + + Outputs country name supported by centos-art.sh script. + The cli_getCountryName function reads one language locale code in the format LL_CC and outputs the name of its related country as in ISO3166. If filter is specified, cli_getCountryName returns the country name that matches the locale code specified in FILTER, exactly. + + + + cli_getCurrentLocale + Function + cli_getCurrentLocale + + + Output current locale used by centos-art.sh script. + The cli_getCurrentLocale function uses LANG environment variable to build a locale pattern that is later applied to cli_getLocales function output in order to return the current locale that centos-art.sh script works with. + The current locale information, returned by cli_getCurrentLocale, is output from more specific to less specific. For example, if en_GB locale exists in cli_getLocales function output, the en_GB locale would take precedence before en locale. + Locale precedence selection is quite important in order to define the locale type we use for message translations. For example, if en_GB is used, we are also saying that the common language specification for English language (i.e., en) is no longer used. Instead, we are using English non-common country-specific language specifications like en_AU, en_BW, en_GB, en_US, etc., for message translations. + Use cli_getCurrentLocale function to know what current locale information to use inside centos-art.sh script. + + + + cli_getFilesList + Function + cli_getFilesList + [ + LOCATION + ] + + + Output list of files to process. + The cli_getFilesList function uses LOCATION variable as source location to build a list of files just as specified by regular expression (REGEX) global variable. Essentially, what the cli_getFilesList function does is using find command to look for files in the location (LOCATION) just as posix-egrep regular expression (REGEX) specifies. + If LOCATION is not specified when cli_getFilesList function is called, the action value (ACTIONVAL) global variable is used as location value instead. + By default, if the regular expression (REGEX) global variable is not redefined after its first definition in the cli function, all files that match default regular expression value (i.e., .+) will be added to the list of files to process. Otherwise, if you redefine the regular expression global variable after its first definition in the cli function and before calling cli_getFilesList function, the last value you specifed is used instead. + When you need to customize the regular expression (REGEX) global variable value inside a function, do not redefine the global variable (at least you be absolutly convinced you need to). Instead, set the regular expression global variable as local to the function you need a customized regular expression value for. If we don't redefine the regular expression global variable as local to the function, or use another name for the regular expression variable (which is not very convenient in order to keep the amount of names to remember low), you may experiment undesired concantenation issues that make your regular expression to be something different from that you expect them to be, specially if the function where you are doing the variable redefinition is called several times during the same script execution. + As result, the cli_getFilesList re-defines the value of FILES variable with the list of files the find command returned. As example, consider the following construction: + + + + + cli_getLangCodes + Function + cli_getLangCodes + [ + FILTER + ] + + + Outputs language codes supported by centos-art.sh script. + cli_getLangCodes function outputs a list of language codes as defined in ISO639 standard. When FILTER is provided, cli_getLangCodes outputs language codes that match FILTER regular expression pattern. + + + + cli_getLangName + Function + cli_getLangName + [ + FILTER + ] + + + Outputs language names supported by centos-art.sh script. + cli_getLangName function reads one language locale code in the format LL_CC and outputs the language related name as in ISO639. If filter is specified, cli_getLangName returns the language name that matches the locale code specified in FILTER, exactly. + + + + cli_getLocales + Function + cli_getLocales + + + Output locale codes supported by centos-art.sh script. + Occasionally, you use cli_getLocales function to add locale information in non-common country-specific language (LL_CC) format for those languages (e.g., bn_IN, pt_BR, etc.) which locale differences cannot be solved using common language specifications (LL) into one unique common locale specification (e.g., bn, pt, etc.). + + + + cli_getRepoName + Function + cli_getRepoName + NAME + TYPE + + + Sanitate file names. + Inside centos-art.sh script, specific functionalities rely both in cli_getRepoName and repository file system organization to achieve their goals. Consider cli_getRepoName function as central place to manage file name convenctions for other functions inside centos-art.sh script. + + Important cli_getRepoName function doesn't verify file or directory existence, for that purpose use cli_checkFiles function instead. + + The NAME variable contains the file name or directory name you want to sanitate. + The TYPE variable specifies what type of sanitation you want to perform on NAME. The TYPE can be one of the following values: + + + + + + Sanitate directory NAMEs. + + + + + + + Sanitate regular file NAMEs. + + +
+ Use cli_getRepoName function to sanitate file names and directory names before their utilization. + Use cli_getRepoName when you need to change file name convenctions inside centos-art.sh script. + When we change file name convenctions inside cli_getRepoName what we are really changing is the way functions interpret repository file system organization. Notice that when we change a file name (e.g., a function name), it is necessary to update all files where such file name is placed on. This may require a massive substitution inside the repository, each time we change name convenctions in the repository (— Removed(pxref:trunk Scripts Bash Functions Path) —, for more information). + + + + cli_getRepoStatus + Function + cli_getRepoStatus + [ + LOCATION + ] + + + Request repository status. + This function requests the status of a LOCATION inside the working copy using the svn status command and returns the first character in the output line, just as described in svn help status. If LOCATION is not a regular file or a directory, inside the working copy, the centos-art.sh script prints a message and ends its execution. + Use this function to perform verifications based a repository LOCATION status. + + + + cli_getTemporalFile + Function + cli_getTemporalFile + NAME + + + Output absolute path to temporal file NAME. + The cli_getTemporalFile function uses /tmp directory as source location to store temporal files, the centos-art.sh script name, and a random identification string to let you run more than one centos-art.sh script simultaneously on the same user session. For example, due the following temporal file defintion: + + If FILE name is instance.svg and the unique random string is f16f7b51-ac12-4b7f-9e66-72df847f12de, the final temporal file, built from previous temporal file definition, would be: + + When you use the cli_getTemporalFile function to create temporal files, be sure to remove temporal files created once you've ended up with them. For example, consider the following construction: + + Use the cli_getTemporalFile function whenever you need to create temporal files inside centos-art.sh script. + + + + cli_getThemeName + Function + cli_getThemeName + + + Output theme name. + In order for cli_getThemeName function to extract theme name correctly, the ACTIONVAL variable must contain a directory path under trunk/Identity/Themes/Motifs/ directory structure. Otherwise, cli_getThemeName returns an empty string. + + + + cli_printMessage + Function + cli_printMessage + MESSAGE + [ + FORMAT + ] + + + Define standard output message definition supported by centos-art.sh script. + When FORMAT is not specified, cli_printMessage outputs information just as it was passed in MESSAGE variable. Otherwise, FORMAT can take one of the following values: + + + + + To print heading messages. + + + + + + + To print warning messages. + + + + + + + To print note messages. + + + + + + + To print Updating messages on two-columns format. + + + + + + + To print Removing messages on two-columns format. + + + + + + + To print Checking messages on two-columns format. + + + + + + + To print Creating messages on two-columns format. + + + + + + + To print Saved as messages on two-columns format. + + + + + + + To print Linked to messages on two-columns format. + + + + + + + To print Moved to messages on two-columns format. + + + + + + + To print Translation messages on two-columns format. + + + + + + + To print Configuration messages on two-columns format. + + + + + + + To print response messages on one-column format. + $MESSAGE +]]> + + + + + + To print request messages on one-column format. Request messages output messages with one colon (:) and without trailing newline (\n) at message end. + + + + + + + To print yes or no request messages on one-column format. If something different from y is answered (when using en_US.UTF-8 locale), script execution ends immediatly. + + When we use centos-art.sh script in a locale different from en_US.UTF-8, confirmation answer may be different from y. For example, if you use es_ES.UTF-8 locale, the confirmation question would look like: + + and the confirmation answer would be s, as it is on Spanish sí word. + Definition of which confirmation word to use is set on translation messages for your specific locale information. — Removed(xref:trunk Scripts Bash Functions Locale) —, for more information about locale-specific translation messages. + + + + + + To standardize to know more, run the following command: messages. When the option is used, the MESSAGE value should be set to "$(caller)". caller is a Bash builtin that returns the context of the current subroutine call. option uses caller builtin output to build documentation entries dynamically. + + Use option after errors and for intentional script termination. + + + + + + To standardize regular messages on one-column format. + When MESSAGE contains a colon inside (e.g., description: message), the cli_printMessage function outputs MESSAGE on two-columns format. + + +
+ Use cli_printMessage function whenever you need to output information from centos-art.sh script. + + Tip To improve two-columns format, change the following file: + + + + + + + + Specific functions + The following specific functions of centos-art.sh script, are available for you to use: + + + + + + + + + + + + + + + + See also + + + trunk Scripts Bash + trunk Scripts Bash + + + + + +
+ + + trunk Scripts Bash Cli Functions Help + trunk Scripts Bash Cli Functions Html + trunk Scripts Bash Cli Functions + trunk +
+ trunk/Scripts/Bash/Cli/Functions/Help + trunk Scripts Bash Cli Functions Help + + Goals + + • + + ... + + + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Scripts Bash Cli Functions Html + trunk Scripts Bash Cli Functions Locale + trunk Scripts Bash Cli Functions Help + trunk +
+ trunk/Scripts/Bash/Cli/Functions/Html + trunk Scripts Bash Cli Functions Html + + Goals + + • + + ... + + + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Scripts Bash Cli Functions Locale + trunk Scripts Bash Cli Functions Manual + trunk Scripts Bash Cli Functions Html + trunk +
+ trunk/Scripts/Bash/Cli/Functions/Locale + trunk Scripts Bash Cli Functions Locale + + Goals + + • + + ... + + + + + + 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 finishd PO file edition and quit text editor, the centos-art command creates the related machine object in the location $CLI_LANG/LC_MESSAGES/$TEXTDOMAIN.mo. + At this point, all translations you made in the PO file should be available to your language when runing centos-art.sh script. + In order to make the centos-art.sh internationalization, the centos-art.sh script was modified as described in the gettext info documentation (info gettext). You can find such modifications in the following files: + + • + + trunk/Scripts/Bash/initFunctions.sh + + + trunk/Scripts/Bash/Functions/Help/cli_localeMessages.sh + + + trunk/Scripts/Bash/Functions/Help/cli_localeMessagesStatus.sh + + + + • + + ... + + + + + + Usage + + + centos-art locale --edit + + Use this command to translate command-line interface output messages in the current system locale you are using (as specified in LANG environment variable). + + + + centos-art locale --list + + Use this command to see the command-line interface locale report. + + +
+ + + + See also + + + +
+ + + trunk Scripts Bash Cli Functions Manual + trunk Scripts Bash Cli Functions Path + trunk Scripts Bash Cli Functions Locale + trunk +
+ trunk/Scripts/Bash/Cli/Functions/Manual + trunk Scripts Bash Cli Functions Manual + + Goals + + • + + ... + + + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + trunk Scripts Bash Cli Functions Path + trunk Scripts Bash Cli Functions Render + trunk Scripts Bash Cli Functions Manual + trunk +
+ trunk/Scripts/Bash/Cli/Functions/Path + trunk Scripts Bash Cli Functions Path + + Goals + This section exists to organize files related to path functiontionality. The path functionality standardizes movement, syncronization, branching, tagging, and general file maintainance inside the repository. + + + + Description + ”CentOS like trees, has roots, trunk, branches, leaves and flowers. Day by day they work together in freedom, ruled by the laws of nature and open standards, to show the beauty of its existence.” + + + Repository layout + The repository layout describes organization of files and directories inside the repository. The repository layout provides the standard backend required for automation scripts to work correctly. If such layout changes unexpectedly, automation scripts may confuse themselves and stop doing what we expect from them to do. + As convenction, inside CentOS Artwork Repository, we organize files and directories related to CentOS corporate visual identity under three top level directories named: trunk/, branches/, and tags/. + The trunk/ directory (see trunk) organizes the main development line of CentOS corporate visual identity. Inside trunk/ directory structure, the CentOS corporate visual identity concepts are implemented using directories. There is one directory level for each relevant concept inside the repository. The trunk/ directory structure is mainly used to perform development tasks related to CentOS corporate visual identity. + The branches/ directory (see branches) oranizes parallel development lines to trunk/ directory. The branches/ directory is used to set points in time where develpment lines are devided one from another taking separte and idependent lives that share a common past from the point they were devided on. The branches/ directory is mainly used to perform quality assurance tasks related to CentOS corporate visual identity. + The tags/ directory (see tags) organizes parallel frozen lines to branches/ directory. The parallel frozen lines are immutable, nothing change inside them once they has been created. The tags/ directory is mainly used to publish final releases of CentOS corporate visual identity. + The CentOS Artwork Repository layout is firmly grounded on a Subversion base. Subversion (http://subversion.tigris.org) is a version control system, which allows you to keep old versions of files and directories (usually source code), keep a log of who, when, and why changes occurred, etc., like CVS, RCS or SCCS. Subversion keeps a single copy of the master sources. This copy is called the source “repository”; it contains all the information to permit extracting previous versions of those files at any time. + + + + Repository name convenctions + Repository name convenctions help us to maintain consistency of names inside the repository. + Repository name convenctions are applied to files and directories inside the repository layout. As convenction, inside the repository layout, file names are all written in lowercase (01-welcome.png, splash.png, anaconda_header.png, etc.) and directory names are all written capitalized (e.g., Identity, Themes, Motifs, TreeFlower, etc.). + Repository name convenctions are implemented inside the cli_getRepoName function of centos-art.sh script. With cli_getRepoName function we reduce the amount of commands and convenctions to remember, concentrating them in just one single place to look for fixes and improvements. + + + + Repository work flow + Repository work flow describes the steps and time intervals used to produce CentOS corporate visual identity inside CentOS Artwork Repository. + To illustrate repository work flow let's consider themes' development cycle. + Initially, we start working themes on their trunk development line (e.g., trunk/Identity/Themes/Motifs/TreeFlower/), here we organize information that cannot be produced automatically (i.e., background images, concepts, color information, screenshots, etc.). + Later, when theme trunk development line is considered “ready” for implementation (e.g., all required backgrounds have been designed), we create a branch for it (e.g., branches/Identity/Themes/Motifs/TreeFlower/1/). Once the branch has been created, we forget that branch and continue working the trunk development line while others (e.g., an artwork quality assurance team) test the new branch for tunning it up. + Once the branch has been tunned up, and considered “ready” for release, it is freezed under tags/ directory (e.g., tags/Identity/Themes/Motifs/TreeFower/1.0/) for packagers, webmasters, promoters, and anyone who needs images from that CentOS theme the tag was created for. + Both branches and tags, inside CentOS Artwork Repository, use numerical values to identify themselves under the same location. Branches start at one (i.e., 1) and increment one unit for each branch created from the same trunk development line. Tags start at zero (i.e., 0) and increment one unit for each tag created from the same branch development line. + + Convenction Do not freeze trunk development lines using tags directly. If you think you need to freeze a trunk development line, create a branch for it and then freeze that branch instead. + + The trunk development line may introduce problems we cannot see immediatly. Certainly, the high changable nature of trunk development line complicates finding and fixing such problems. On the other hand, the branched development lines provide a more predictable area where only fixes/corrections to current content are commited up to repository. + If others find and fix bugs inside the branched development line, we could merge such changes/experiences back to trunk development line (not visversa) in order for future branches, created from trunk, to benefit. + Time intervals used to create branches and tags may vary, just as different needs may arrive. For example, consider the release schema of CentOS distribution: one major release every 2 years, security updates every 6 months, support for 7 years long. Each time a CentOS distribution is released, specially if it is a major release, there is a theme need in order to cover CentOS distribution artwork requirements. At this point, is where CentOS Artwork Repository comes up to scene. + Before releasing a new major release of CentOS distribution we create a branch for one of several theme development lines available inside the CentOS Artwork Repository, perform quality assurance on it, and later, freeze that branch using tags. Once a the theme branch has been frozen (under tags/ directory), CentOS Packagers (the persons whom build CentOS distribution) can use that frozen branch as source location to fulfill CentOS distribution artwork needs. The same applies to CentOS Webmasters (the persons whom build CentOS websites), and any other visual manifestation required by the project. + + + + Parallel directories + Inside CentOS Artwork Repository, parallel directories are simple directory entries built from a common parent directory and placed in a location different to that, the common parent directory is placed on. Parallel directories are useful to create branches, tags, translations, documentation, pre-rendering configuration script, and similar directory structures. + Parallel directories take their structure from one unique parent directory. Inside CentOS Artwork Repository, this unique parent directory is under trunk/Identity location. The trunk/Identity location must be considered the reference for whatever information you plan to create inside the repository. + In some circumstances, parallel directories may be created removing uncommon information from their paths. Uncommon path information refers to those directory levels in the path which are not common for other parallel directories. For example, when rendering trunk/Identity/Themes/Motifs/TreeFlower/Distro directory structure, the centos-art.sh script removes the Motifs/TreeFlower/ directory levels from path, in order to build the parallel directory used to retrived translations, and pre-rendering configuration scripts required by render functionality. + Another example of parallel directory is the documentation structure created by manual functionality. This time, centos-art.sh script uses parallel directory information with uncommon directory levels to build the documentation entry required by Texinfo documentation system, inside the repository. + Othertimes, parallel directories may add uncommon information to their paths. This is the case we use to create branches and tags. When we create branches and tags, a numerical identifier is added to parallel directory structure path. The place where the numerical identifier is set on is relevant to corporate visual identity structure and should be carefully considered where it will be. + When one parent directory changes, all their related parallel directories need to be changed too. This is required in order for parallel directories to retain their relation with the parent directory structure. In the other hand, parallel directories should never be modified under no reason but to satisfy the relation to their parent directory structure. Liberal change of parallel directories may suppresses the conceptual idea they were initially created for; and certainly, things may stop working the way they should do. + + + + Syncronizing path information + Parallel directories are very useful to keep repository organized but introduce some complications. For instance, consider what would happen to functionalities like manual (trunk Scripts Bash Functions Manual) that rely on parent directory structures to create documentation entries (using parallel directory structures) if one of those parent directory structures suddenly changes after the documentation entry has been already created for it? + In such cases, functionalities like manual may confuse themselves if path information is not updated to reflect the relation with its parent directory. Such functionalities work with parent directory structure as reference; if a parent directory changes, the functionalities dont't even note it because they work with the last parent directory structure available in the repository, no matter what it is. + In the specific case of documentation (the manual functionality), the problem mentioned above provokes that older parent directories, already documented, remain inside documentation directory structures as long as you get your hands into the documentation directory structure (trunk/Manuals) and change what must be changed to match the new parent directory structure. + There is no immediate way for manual, and similar functionalities that use parent directories as reference, to know when and how directory movements take place inside the repository. Such information is available only when the file movement itself takes place inside the repository. So, is there, at the moment of moving files, when we need to syncronize parallel directories with their unique parent directory structure. + + Warning There is not support for URL reference inside centos-art.sh script. The centos-art.sh script is designed to work with local files inside the working copy only. + + As CentOS Artwork Repository is built over a version control system, file movements inside the repository are considered repository changes. In order for these repository changes to be versioned, we need to, firstly, add changes into the version control system, commit them, and later, perform movement actions using version control system commands. This configuration makes possible for everyone to know about changes details inside the repository; and if needed, revert or update them back to a previous revision. + Finally, once all path information has been corrected, it is time to take care of information inside the files. For instance, considere what would happen if you make a reference to a documentation node, and later the documentation node you refere to is deleted. That would make Texinfo to produce error messages at export time. So, the centos-art.sh script needs to know when such changes happen, in a way they could be noted and handled without producing errors. + + + + What is the right place to store it? + Occasionly, you may find that new corporate visual identity components need to be added to the repository. If that is your case, the first question you need to ask yourself, before start to create directories blindly all over, is: What is the right place to store it? + The CentOS Community different free support vains (see: http://wiki.centos.org/GettingHelp) are the best place to find answers to your question, but going there with hands empty is not good idea. It may give the impression you don't really care about. Instead, consider the following suggestions to find your own comprehension and so, make your propositions based on it. + When we are looking for the correct place to store new files, to bear in mind the corporate visual identity structure used inside the CentOS Artwork Repository (see trunk Identity) would be probaly the best advice we could offer, the rest is just matter of choosing appropriate names. To illustrate this desition process let's consider the trunk/Identity/Themes/Motifs/TreeFlower directory as example. It is the trunk development line of TreeFlower artistic motif. Artistic motifs are considered part of themes, which in turn are considered part of CentOS corporate visual identity. + When building parent directory structures, you may find that reaching an acceptable location may take some time, and as it uses to happen most of time; once you've find it, that may be not a definite solution. There are many concepts that you need to play with, in order to find a result that match the conceptual idea you try to implement in the new directory location. To know which these concepts are, split the location in words and read its documentation entry from less specific to more specific. + For example, the trunk/Identity/Themes/Motifs/TreeFlower location evolved through several months of contant work and there is no certain it won't change in the future, even it fixes quite well the concept we are trying to implement. The concepts used in trunk/Identity/Themes/Distro/Motifs/TreeFlower location are described in the following commands, respectively: + + Other location concepts can be found similary as we did above, just change the location we used above by the one you are trying to know concepts for. + + + + + Usage + + + centos-art path --copy='SRC' --to='DST' + + Copy to and schedule for addition (with history). In this command, SRC and DST are both working copy (WC) entries. + + + + centos-art path --delete='SRC' + + Delete . In order for this command to work the file or directory you intend to delete should be under version control first. In this command, SRC is a working copy (WC) entry. + + +
+ + + + See also + + + trunk Scripts Bash + trunk Scripts Bash + + + + + +
+ + + trunk Scripts Bash Cli Functions Render + trunk Scripts Bash Cli Functions Render Config + trunk Scripts Bash Cli Functions Path + trunk +
+ trunk/Scripts/Bash/Cli/Functions/Render + trunk Scripts Bash Cli Functions RenderThe render functionality exists to produce both identity and translation files on different levels of information (i.e., different languages, release numbers, architectures, etc.). + The render functionality relies on “renderable directory structures” to produce files. Renderable directory structures can be either “identity directory structures” or “translation directory structures” with special directories inside. + + + Renderable identity directory structures + Renderable identity directory structures are the starting point of identity rendition. Whenever we want to render a component of CentOS corporate visual identity, we need to point centos-art.sh to a renderable identity directory structure. If such renderable identity directory structure doesn't exist, then it is good time to create it. + Inside the working copy, one renderable identity directory structures represents one visual manifestation of CentOS corporate visual identity, or said differently, each visual manifestation of CentOS corporate visual identity should have one renderable identity directory structure. + Inside renderable identity directory structures, centos-art.sh can render both image-based and text-based files. Specification of whether a renderable identity directory structure produces image-based or text-based content is a configuration action that takes place in the pre-rendition configuration script of that renderable identity directory structure. + Inside renderable identity directory structures, content production is organized in different configurations. A content production configuration is a unique combination of the components that make an identity directory structure renderable. One content production configuration does one thing only (e.g., to produce untranslated images), but it can be extended (e.g., adding translation files) to achieve different needs (e.g., to produce translated images). + + + Design template without translation + The design template without translation configuration is based on a renderable identity directory structure with an empty translation directory structure. In this configuration, one design template produces one untranslated file. Both design templates and final untranslated files share the same file name, but they differ one another in file-type and file-extension. + For example, to produce images without translations (there is no much use in producing text-based files without translations), consider the following configuration: + + + One renderable identity directory structure: + + In this example we used Identity/Path/To/Dir as the identity component we want to produce untranslated images for. Identity components can be either under trunk/ or branches/ directory structure. + The identity component (i.e., Identity/Path/To/Dir, in this case) is also the bond component we use to connect the identity directory structures with their respective auxiliar directories (i.e., translation directory structres and pre-rendition configuration structures). The bond component is the path convenction that centos-art.sh uses to know where to look for related translations, configuration scripts and whatever auxiliar thing a renderable directory structure may need to have. + | +trunk/Identity/Path/To/Dir <-- Renderable identity directory structure. +|-- Tpl <-- Design template directory. +| `-- file.svg <-- Design template file. +`-- Img <-- Directory used to store final files. + `-- file.png <-- Final image-based file produced from + design template file. +]]> + Inside design template directory, design template files are based on SVGScalable Vector Graphics and use the extension .svg. Design template files can be organized using several directory levels to create a simple but extensible configuration, specially if translated images are not required. + In order for SVGScalable Vector Graphics files to be considered “design template” files, they should be placed under the design template directory and to have set a CENTOSARTWORK object id inside. + The CENTOSARTWORK word itself is a convenction name we use to define which object/design area, inside a design template, the centos-art.sh script will use to export as PNGPortable Network Graphic image at rendition time. Whithout such object id specification, the centos-art.sh script cannot know what object/design area you (as designer) want to export as PNGPortable Network Graphic image file. + + Note At rendition time, the content of Img/ directory structure is produced by centos-art.sh automatically. + + When a renderable identity directory structure is configured to produce image-based content, centos-art.sh produces PNGPortable Network Graphics files with the .png extension. Once the base image format has been produced, it is possible for centos-art.sh to use it in order to automatically create other image formats that may be needed (— Removed(pxref:trunk Scripts Bash Functions Render Config) —). + Inside the working copy, you can find an example of “design template without translation” configuration at trunk/Identity/Models/. + See trunk Identity, for more information. + + + + One translation directory structure: + + In order for an identity entry to be considered an identity renderable directory structure, it should have a translation entry. The content of the translation entry is relevant to determine how to process the identity renderable directory entry. + If the translation entry is empty (i.e., there is no file inside it), centos-art.sh interprets the identity renderable directory structure as a “design templates without translation” configuration. + | +trunk/Translations/Identity/Path/To/Dir +`-- (empty) +]]> + If the translation entry is not empty, centos-art.sh can interpret the identity renderable directory structure as one of the following configurations: “design template with translation (one-to-one)” or “design template with translation (optimized)”. Which one of these configurations is used depends on the value assigned to the matching list (MATCHINGLIST) variable in the pre-rendition configuration script of the renderable identity directory structure we are producing images for. + If the matching list variable is empty (as it is by default), then “design template with translation (one-to-one)” configuration is used. In this configuration it is required that both design templates and translation files have the same file names. This way, one translation files is applied to one design template, to produce one translated image. + If the matching list variable is not empty (because you redefine it in the pre-rendition configuration script), then “design template with translation (optimized)” configuration is used instead. In this configuration, design templates and translation files don't need to have the same names since such name relationship between them is specified in the matching list properly. + — Removed(xref:trunk Translations) —, for more information. + + + + One pre-rendition configuration script: + + In order to make an identity directory structure renderable, a pre-rendition configuration script should exist for it. The pre-rendition configuration script specifies what type of rendition does centos-art.sh will perform over the identity directory structure and how does it do that. + | +trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir +`-- render.conf.sh +]]> + In this configuration the pre-rendition configuration script (render.conf.sh) would look like the following: + + Since translation directory structure is empty, centos-art.sh assumes a “design template without translation” configuration to produce untranslated images. + To produce untranslated images, centos-art.sh takes one design template and creates one temporal instance from it. Later, centos-art.sh uses the temporal design template instance as source file to export the final untranslated image. The action of exporting images from SVGScalable Vector Graphics to PNGPortable Network Graphics is possible thanks to Inkscape's command-line interface and the CENTOSARTWORK object id we previously set inside design templates. + + Finally, when the untranslated image has been created, the temporal design template instance is removed. At this point, centos-art.sh takes the next design template and repeats the whole production flow once again (design template by design template), until all design templates be processed. + — Removed(xref:trunk Scripts Bash Functions Render Config) —, for more information. + + +
+ + + + Design template with translation (one-to-one) + Producing untranslated images is fine in many cases, but not always. Sometimes it is required to produce images in different languages and that is something that untrasnlated image production cannot achieve. However, if we fill its empty translation entry with translation files (one for each design template) we extend the production flow from untranslated image production to translated image production. + In order for centos-art.sh to produce images correctly, each design template should have one translation file and each translation file should have one design template. Otherwise, if there is a missing design template or a missing translation file, centos-art.sh will not produce the final image related to the missing component. + In order for centos-art.sh to know which is the relation between translation files and design templates the translation directory structure is taken as reference. For example, the trunk/Translations/Identity/Path/To/Dir/file.sed translation file does match trunk/Identity/Path/To/Dir/Tpl/file.svg design template, but it doesn't match trunk/Identity/Path/To/Dir/File.svg or trunk/Identity/Path/To/Dir/Tpl/File.svg or trunk/Identity/Path/To/Dir/Tpl/SubDir/file.svg design templates. + The pre-rendition configuration script used to produce untranslated images is the same we use to produce translated images. There is no need to modify it. So, as we are using the same pre-rendition configuration script, we can say that translated image production is somehow an extended/improved version of untranslated image production. + + Note If we use no translation file in the translation entry (i.e., an empty directory), centos-art.sh assumes the untranslated image production. If we fill the translation entry with translation files, centos-art.sh assumes the translated image production. + + To produce final images, centos-art.sh applies one translation file to one design template and produce a translated design template instance. Later, centos-art.sh uses the translated template instance to produce the translated image. Finally, when the translated image has been produced, centos-art.sh removes the translated design template instance. This production flow is repeated for each translation file available in the translatio entry. + + + + + Design template with translation (optimized) + Producing translated images satisfies almost all our production images needs, but there is still a pitfall in them. In order to produce translated images as in the “one-to-one” configuration describes previously, it is required that one translation file has one design template. That's useful in many cases, but what would happen if we need to apply many different translation files to the same design template? Should we have to duplicate the same design template file for each translation file, in order to satisfy the “one-to-one” relation? What if we need to assign translation files to design templates arbitrarily? + Certenly, that's something the “one-to-one” configuration cannot handle. So, that's why we had to “optimize” it. The optimized configuration consists on using a matching list (MATCHINGLIST) variable that specifies the relationship between translation files and design templates in an arbitrary way. Using such matching list between translation files and design templates let us use as many assignment combinations as translation files and design templates we are working with. + The MATCHINGLIST variable is set in the pre-rendition configuration script of the component we want to produce images for. By default, the MATCHINGLIST variable is empty which means no matching list is used. Otherwise, if MATCHINGLIST variable has a value different to empty value then, centos-art.sh interprets the matching list in order to know how translation files are applied to design templates. + For example, consider the following configuration: + + + One entry under trunk/Identity/: + + In this configuration we want to produce three images using a paragraph-based style, controlled by paragraph.svg design template; and one image using a list-based style, controlled by list.svg design template. + + + + + One entry under trunk/Translations/: + + In order to produce translated images we need to have one translation file for each translated image we want to produce. Notice how translation names do match final image file names, but how translation names do not match design template names. When we use matching list there is no need for translation files to match the names of design templates, such name relation is set inside the matching list itself. + + + + + One entry under trunk/trunk/Scripts/Bash/Functions/Render/Config/: + + In order to produce different translated images using specific design templates, we need to specify the relation between translation files and design templates in a way that centos-art.sh could know exactly what translation file to apply to what design template. This relation between translation files and design templates is set using the matching list MATCHINGLIST variable inside the pre-rendition configuration script of the component we want to produce images for. + + In this configuration the pre-rendition configuration script (render.conf.sh) would look like the following: + + As result, centos-art.sh will produce 01-welcome.png, 02-donate.png and 04-support.png using the paragraph-based design template, but 03-docs.png using the list-based design template. + + +
+ + + + Design template with translation (optimized+flexibility) + In the production models we've seen so far, there are design templates to produce untranslated images and translation files which combiend with design templates produce translated images. That may seems like all our needs are covered, doesn't it? Well, it almost does. + Generally, we use design templates to define how final images will look like. Generally, each renderable directory structure has one Tpl/ directory where we organize design templates for that identity component. So, we can say that there is only one unique design template definition for each identity component; or what is the same, said differently, identity components can be produced in one way only, the way its own design template directory specifies. This is not enough for theme production. It is a limitation, indeed. + Initially, to create one theme, we created one renderable directory structure for each theme component. When we found ourselves with many themes, and components inside them, it was obvious that the same design model was duplicated inside each theme. As design models were independently one another, if we changed one theme's design model, that change was useless to other themes. So, in order to reuse design model changes, we unified design models into one common directory structure. + With design models unified in a common structure, another problem rose up. As design models also had the visual style of theme components, there was no difference between themes, so there was no apparent need to have an independent theme directory structure for each different theme. So, it was also needed to separate visual styles from design models. + At this point there are two independent worklines: one directory structure to store design models (the final image characteristics [i.e., dimensions, translation markers, etc.]) and one directory structure to store visual styles (the final image visual style [i.e., the image look and feel]). So, it is possible to handle both different design models and different visual styles independtly one another and later create combinations among them using centos-art.sh. + For example, consider the following configuration: + + + One entry under trunk/Identity/Themes/Models/: + + The design model entry exists to organize design model files (similar to design templates). Both design models and design templates are very similar; they both should have the CENTOSARTWORK export id present to identify the exportation area, translation marks, etc. However, design models do use dynamic backgrounds inclusion while design templates don't. + | +trunk/Identity/Themes/Models/Default/Distro/Anaconda/Progress/ +|-- paragraph.svg +`-- list.svg +]]> + Inisde design models, dynamic backgrounds are required in order for different artistic motifs to reuse common design models. Firstly, in order to create dynamic backgrounds inside design models, we import a bitmap to cover design model's background and later, update design model's path information to replace fixed values to dynamic values. + + + + One entry under trunk/Identity/Themes/Motifs/: + + The artistic motif entry defines the visual style we want to produce images for, only. Final images (i.e., those built from combining both design models and artistic motif backrounds) are not stored here, but under branches directory structure. In the artistic motif entry, we only define those images that cannot be produced automatically by centos-art.sh (e.g., Backgrounds, Color information, Screenshots, etc.). + | +trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/ +|-- Img +| |-- Png +| | |-- 510x300.png +| | `-- 510x300-final.png +| `-- Jpg +| |-- 510x300.jpg +| `-- 510x300-final.jpg +|-- Tpl +| `-- 510x300.svg +`-- Xcf + `-- 510x300.xcf +]]> + + + + One entry under trunk/Translations/: + + The translation entry specifies, by means of translation files, the language-specific information we want to produce image for. When we create the translation entry we don't use the name of neither design model nor artistic motif, just the design model component we want to produce images for. + | +trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ +`-- 5 + |-- en + | |-- 01-welcome.sed + | |-- 02-donate.sed + | `-- 03-docs.sed + `-- es + |-- 01-welcome.sed + |-- 02-donate.sed + `-- 03-docs.sed +]]> + + + + One entry under trunk/Scripts/Bash/Functions/Render/Config/: + + There is one pre-rendition configuration script for each theme component. So, each time a theme component is rendered, its pre-rendition configuration script is evaluated to teach centos-art.sh how to render the component. + + In this configuration the pre-rendition configuration script (render.conf.sh) would look like the following: + + + +
+ The production flow of “optimize+flexibility” configuration&dots; + + + + + Renderable translation directory structures + Translation directory structures are auxiliar structures of renderable identity directory structures. There is one translation directory structure for each renderable identity directory structure. Inside translation directory structures we organize translation files used by renderable identity directory structures that produce translated images. Renderable identity directory structures that produce untranslated images don't use translation files, but they do use a translation directory structure, an empty translation directory structure, to be precise. + In order to aliviate production of translation file, we made translation directory structures renderable adding a template (Tpl/) directory structure to handle common content inside translation files. This way, we work on translation templates and later use centos-art.sh to produce specific translation files (based on translation templates) for different information (e.g., languages, release numbers, architectures, etc.). + If for some reason, translation files get far from translation templates and translation templates become incovenient to produce such translation files then, care should be taken to avoid replacing the content of translation files with the content of translation templates when centos-art.sh is executed to produce translation files from translation templates. + Inside renderable translation directory structures, centos-art.sh can produce text-based files only. + + + + Copying renderable directory structures + A renderable layout is formed by design models, design images, pre-rendition configuration scripts and translations files. This way, when we say to duplicate rendition stuff we are saying to duplicate these four directory structures (i.e., design models, design images, pre-rendition configuration scripts, and related translations files). + When we duplicate directories, inside `trunk/Identity' directory structure, we need to be aware of renderable layout described above and the source location used to perform the duplication action. The source location is relevant to centos-art.sh script in order to determine the required auxiliar information inside directory structures that need to be copied too (otherwise we may end up with orphan directory structures unable to be rendered, due the absence of required information). + In order for a renderable directory structure to be valid, the new directory structure copied should match the following conditions: + + + To have a unique directory structure under trunk/Identity, organized by any one of the above organizational designs above. + + + To have a unique directory structure under trunk/Translations to store translation files. + + + To have a unique directory structure under trunk/Scripts/Bash/Functions/Render/Config to set pre-rendition configuration script. + + + As convenction, the render_doCopy function uses trunk/Identity directory structure as source location. Once the trunk/Identity directory structure has been specified and verified, the related path information is built from it and copied automatically to the new location specified by FLAG_TO variable. + Design templates + No translation: + Command: - centos-art render –copy=trunk/Identity/Path/To/Dir –to=trunk/Identity/NewPath/To/Dir + Sources: - trunk/Identity/Path/To/Dir - trunk/Translations/Identity/Path/To/Dir - trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir + Targets: - trunk/Identity/NewPath/To/Dir - trunk/Translations/Identity/NewPath/To/Dir - trunk/Scripts/Bash/Functions/Render/Config/Identity/NewPath/To/Dir + Renderable layout 2: + Command: - centos-art render –copy=trunk/Identity/Themes/Motifs/TreeFlower \ –to=trunk/Identity/Themes/Motifs/NewPath/To/Dir + Sources: - trunk/Identity/Themes/Motifs/TreeFlower - trunk/Translations/Identity/Themes - trunk/Translations/Identity/Themes/Motifs/TreeFlower - trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes - trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/TreeFlower + Targets: - trunk/Identity/Themes/Motifs/NewPath/To/Dir - trunk/Translations/Identity/Themes - trunk/Translations/Identity/Themes/Motifs/NewPath/To/Dir - trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes - trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewPath/To/Dir + Notice that design models are not included in source or target locations. This is intentional. In “Renderable layout 2”, design models live by their own, they just exist, they are there, available for any artistic motif to use. By default `Themes/Models/Default' design model directory structure is used, but other design models directory structures (under Themes/Models/) can be created and used changing the value of THEMEMODEL variable inside the pre-rendition configuration script of the artistic motif source location you want to produce. + Notice how translations and pre-rendition configuration scripts may both be equal in source and target. This is because such structures are common to all artistic motifs (the default values to use when no specific values are provided). + - The common directory structures are not copied or deleted. We cannot copy a directory structure to itself. + - The common directory structures represent the default value to use when no specific translations and/or pre-rendition configuration script are provided inside source location. + - The specific directory structures, if present, are both copiable and removable. This is, when you perform a copy or delete action from source, that source specific auxiliar directories are transfered in the copy action to a new location (that specified by FLAG_TO variable). + - When translations and/or pre-rendition configuration scripts are found inside the source directory structure, the centos-art.sh script loads common auxiliar directories first and later specific auxiliar directories. This way, identity rendition of source locations can be customized idividually over the base of common default values. + - The specific auxiliar directories are optional. + - The common auxiliar directories should be present always. This is, in order to provide the information required by render functionality (i.e., to make it functional in the more basic level of its existence). + Notice how the duplication process is done from `trunk/Identity' on, not the oposite. If you try to duplicate a translation structure (or similar auxiliar directory structures like pre-rendition configuration scripts), the `trunk/Identity' for that translation is not created. This limitation is impossed by the fact that many `trunk/Identity' directory structures may reuse/share the same translation directory structure. We cannot delete one translation (or similar) directory structures while a related `trunk/Identity/' directory structure is still in need of it. + The `render_doCopy' functionality does duplicate directory structures directly involved in rendition process only. Once such directories have been duplicated, the functionality stops thereat. + + + + Usage + + • + + ... + + + + + + See also + + + + +
+ + + trunk Scripts Bash Cli Functions Render Config + trunk Scripts Bash Cli Functions Shell + trunk Scripts Bash Cli Functions Render + trunk +
+ trunk/Scripts/Bash/Cli/Functions/Render/Config + trunk Scripts Bash Cli Functions Render Config + + Goals + The trunk/Scripts/Bash/Config directory exists to oraganize pre-rendering configuration scripts. + + + + Description + Pre-rendering configuration scripts let you customize the way centos-art.sh script renders identity and translation repository entries. Pre-rendering configuration scripts are render.conf.sh files with render_loadConfig function definition inside. + There is one render.conf.sh file for each pre-rendering configuration entry. Pre-rendering configuration entries can be based both on identity and translation repository entires. Pre-rendering configuration entries are required for each identity entry, but not for translation entries. + + + The <file>render.conf.sh</file> 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: + + Inside identity pre-rendering configuration scripts, text-based pre-rendering configuration scripts look like the following: + + 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. + + + + The <file>render.conf.sh</file> translation model + Translation pre-rendering configuration scripts take precedence before default translation rendering action. Translation pre-rendering actions are useful when default translation rendering action do not fit itself to translation entry rendering requirements. + + + + The <file>render.conf.sh</file> rendering actions + Inside both image-based and text-based identity pre-rendering configuration scripts, we use the ACTIONS array variable to define the way centos-art.sh script performs identity rendering. Identity rendering is organized by one BASE action, and optional POST and LAST rendering actions. + The BASE action specifies what kind of rendering does the centos-art.sh script will perform with the files related to the pre-rendering configuration script. The BASE action is required. Possible values to BASE action are either renderImage or renderText only. + To specify the BASE action you need to set the BASE: string followed by one of the possible values. For example, if you want to render images, consider the following definition of BASE action: + + 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: + + 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: + + 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. + + Note — Removed(xref: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: + + + + + + Usage + Use the following commands to administer both identity and translation pre-rendering configuration scripts: + + + centos-art config --create='path/to/dir/' + + Use this command to create path/to/dir related pre-rendering configuration script. + + + + centos-art config --edit='path/to/dir/' + + Use this command to edit path/to/dir related pre-rendering configuration script. + + + + centos-art config --read='path/to/dir/' + + Use this command to read path/to/dir related pre-rendering configuration script. + + + + centos-art config --remove='path/to/dir/' + + 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. + + + + See also + + + trunk Scripts Bash + trunk Scripts Bash + + + + + + +
+ + + trunk Scripts Bash Cli Functions Shell + trunk Scripts Bash Cli Functions Svg + trunk Scripts Bash Cli Functions Render Config + trunk +
+ trunk/Scripts/Bash/Cli/Functions/Shell + trunk Scripts Bash Cli Functions Shell + + Goals + This section exists to organize files related to shell functionality of centos-art.sh script. + + + + Description + The shell functionality of centos-art.sh script helps you to maintain bash scripts inside repository. For example, suppose you've created many functionalities for centos-art.sh script, and you want to use a common copyright and license note for consistency in all your script files. If you have a bunch of files, doing this one by one wouldn't be a big deal. In contrast, if the amount of files grows, updating the copyright and license note for all of them would be a task rather tedious. The shell functionality exists to solve maintainance tasks just as the one previously mentioned. + When you use shell functionality to update copyright inside script files, it is required that your script files contain (at least) the following top commentary structure: + + Figure + + + The functions script base comment structure + + Relevant lines in the above structure are lines from 5 to 9. Everything else in the file is left immutable. + When you are updating copyright through shell functionality, the centos-art.sh script replaces everything in-between line 5 —the first one matching ^# Copyright .+$ string— and line 9—the first long dash separator matching ^# -+$— with the content of copyright template instance. + + Caution Be sure to add the long dash separator that matches ^# -+$ regular expression before the function definition. Otherwise, if the Copyright line is present but no long dash separator exists, centos-art.sh will remove anything in-between the Copyright line and the end of file. This way you may lost your function definitions entirely. + + The copyright template instance is created from one copyright template stored in the Config/tpl_forCopyright.sed file. The template instance is created once, and later removed when no longer needed. At this moment, when template instance is created, the centos-art.sh script takes advantage of automation in order to set copyright full name and date dynamically. + When you use shell functionality to update copyright, the first thing shell functionality does is requesting copyright information to user, and later, if values were left empty (i.e., no value was typed before pressing RET key), the shell functionality uses its own default values. + When shell functionality uses its own default values, the final copyright note looks like the following: + + Figure + + + The function script comment example + + Relevant lines in the above structure are lines from 5 to 22. Pay attention how the copyright line was built, and how the license was added into the top comment where previously was just three dots. Everything else in the file was left immutable. + To change copyright information (i.e., full name or year information), run the shell functionality over the root directory containing the script files you want to update copyright in and enter the appropriate information when it be requested. You can run the shell functionality as many times as you need to. + To change copyright license (i.e., the text in-between lines 7 and 20), you need to edit the Config/tpl_forCopyright.sed file, set the appropriate information, and run the shell functionality once again for changes to take effect over the files you specify. + + Important The centos-art.sh script is released as: + + Do not change the license information under which centos-art.sh script is released. Instead, if you think a different license must be used, please share your reasons at centos-devel@centos-art.shCentOS Developers mailing list. + + + + + Usage + + + centos-art sh --update-copyright='path/to/dir' + centos-art sh --update-copyright='path/to/dir' --filter='regex' + + Use these commands to update copyright information in .sh files under path/to/dir directory. + + +
+ When you provide argument, the list of files to process is reduced as specified in regex regular expression. Inside centos-art.sh script, the regex regular expression is used in combination with find command to look for files matching the regular expression path pattern. + + Warning In order for regex regular expression to match a file, the regex regular expresion must match the whole file path not just the file name. + + For example, if you want to match all render.conf.sh files inside path/to/dir, use the .+/render.conf regular expression. Later, centos-art.sh script uses this value inside ^$REGEX\.sh$ expression in order to build the final regular expression (i.e., ^.+/render.conf\.sh$) that is evaluated against available file paths inside the list of files to process. + Exceptionally, when you provide in the way that regex, appended to path/to/dir/ (i.e. path/to/dir/regex), matches a regular file; the centos-art.sh script uses the file matching as only file in the list of files to process. + + + + See also + + + trunk Scripts Bash + trunk Scripts Bash + + + + + +
+ + + trunk Scripts Bash Cli Functions Svg + trunk Scripts Bash Cli Functions Verify + trunk Scripts Bash Cli Functions Shell + trunk +
+ trunk/Scripts/Bash/Cli/Functions/Svg + trunk Scripts Bash Cli Functions Svg + + Goals + This section exists to organize files related to svg functionality of centos-art.sh script. + + + + Description + The svg functionality of centos-art.sh script helps you to maintain scalable vector graphics (SVG) inside repository. For example, suppose you've been working in CentOS default design models under trunk/Identity/Themes/Models/, and you want to set common metadata to all of them, and later remove all unused SVG defintions from *.svg files. Doing so file by file may be a tedious task, so the centos-art.sh script provides the svg functionality to aid you maintain such actions. + Metadata maintainance + + Metadata maintainance + The metadata used is defined by Inkscape 0.46 using the SVG standard markup. The centos-art.sh script replaces everything in-between <metadata and </metadata> tags with a predefined metadata template we've set for this purpose. + The metadata template was created using the metadata information of a file which, using Inkscape 0.46, all metadata fields were set. This created a complete markup representation of how SVG metadata would look like. Later, we replaced every single static value with a translation marker in the form =SOMETEXT=, where SOMETEXT is the name of its main opening tag. Later, we transform the metadata template into a sed replacement set of commads escaping new lines at the end of each line. + With metadata template in place, the centos-art.sh script uses it to create a metadata template instance for the file being processed currently. The metadata template instance contains the metadata portion of sed replacement commands with translation markers already traduced. In this action, instance creation, is where we take advantage of automation and generate metadata values like title, date, keywords, source, identifier, and relation dynamically, based on the file path centos-art.sh script is currently creating metadata information for. + With metadata template instance in place, the centos-art.sh script uses it to replace real values inside all .svg files under the current location you're running the centos-art.sh script on. Default behaviour is to ask user to enter each metadatum required, one by one. If user leaves metadatum empty, by pressing RET key, centos-art.sh uses its default value. + The centos-art.sh script modifies the following metadata: + + + Title + + Name by which this document is formally known. If no value is set here, centos-art.sh script uses the file name as title. + + + + Date + + Date associated with the creation of this document (YYYY-MM-DD). If no value is set here, centos-art.sh script uses the current date information as in date +%Y-%m-%d. + + + + Creator + + Name of entity primarily responsible for making the content of this document. If no value is set here, centos-art.sh script uses the string The CentOS Project. + + + + Rights + + Name of entity with rights to the intellectual Property of this document. If no value is set here, centos-art.sh script uses the string The CentOS Project. + + + + Publisher + + Name of entity responsible for making this document available. If no value is set here, centos-art.sh script uses the string The CentOS Project. + + + + Identifier + + Unique URI to reference this document. If no value is set here, centos-art.sh script uses the current file path to build the related url that points to current file location inside repository central server. + + + + Source + + Unique URI to reference the source of this document. If no value is set here, centos-art.sh script uses current file path to build the related url that points to current file location inside repository central server. + + + + Relation + + Unique URI to a related document. If no value is set here, centos-art.sh script uses current file path to build the related url that points to current file location inside repository central server. + + + + Language + + Two-letter language tag with optional subtags for the language of this document. (e.g. en-GB). If no value is set here, centos-art.sh script uses the current locale information as in cli_getCurrentLocale function. + + + + Keywords + + The topic of this document as comma-separated key words, prhases, or classifications. If no value is set here, centos-art.sh script uses file path to build + + + + Coverage + + Extent or scope of this document. If no value is set here, centos-art.sh script uses the string The CentOS Project. + + + + Description + + Description about the document. If no value is set here, centos-art.sh script uses uses empty value as default. + + + + Contributors + + People that contributes in the creation/maintainance of the document. If no value is set here, centos-art.sh script uses uses empty value as default. + + +
+ The License metadatum is not set as a choise, by now. It is fixed http://creativecommons.org/licenses/by-sa/3.0/Creative Common Attribution Share-Alike 3.0 License. This is done in order to grant license consistency among all SVG files we manage inside CentOS Artwork Repository. + Unused definitions + + + + Unused definitions + Many of the no-longer-used gradients, patterns, and markers (more precisely, those which you edited manually) remain in the corresponding palettes and can be reused for new objects. However if you want to optimize your document, use the Vacuum Defs command in File menu. It will remove any gradients, patterns, or markers which are not used by anything in the document, making the file smaller. + If you have one or two couple of files, removing unused definitions using the graphical interface may be enough to you. In contrast, if you have dozens or even houndreds of scalable vector graphics files to maintain it is not a fun task to use the graphical interface to remove unused definitions editing those files one by one. + To remove unused definitions from several scalable vector graphics files, the centos-art.sh script uses Inkscape command-line interface, specifically with the option. + + + + + Usage + + + centos-art svg --update-metadata='path/to/dir' + centos-art svg --update-metadata='path/to/dir' --filter='regex' + + Use these commands to update metadata information to .svg files under path/to/dir directory. + + + + centos-art svg --vacuum-defs='path/to/dir' + centos-art svg --vacuum-defs='path/to/dir' --filter='regex' + + Use these commands to remove unused definitions inside .svg files under path/to/dir directory. + + +
+ When you provide argument, the list of files to process is reduced as specified in regex regular expression. Inside centos-art.sh script, the regex regular expression is used in combination with find command to look for files matching the regular expression path pattern. + + Warning In order for regex regular expression to match a file, the regex regular expresion must match the whole file path not just the file name. + + For example, if you want to match all summary.svg files inside path/to/dir, use the .+/summary regular expression. Later, centos-art.sh script uses this value inside ^$REGEX\.svg$ expression in order to build the final regular expression (i.e., ^.+/summary\.svg$) that is evaluated against available file paths inside the list of files to process. + Exceptionally, when you provide in the way that regex, appended to path/to/dir/ (i.e. path/to/dir/regex), matches a regular file; the centos-art.sh script uses the file matching as only file in the list of files to process. + + + + See also + + + trunk Scripts Bash + trunk Scripts Bash + + + + + +
+ + + trunk Scripts Bash Cli Functions Verify + trunk Scripts Python + trunk Scripts Bash Cli Functions Svg + trunk +
+ trunk/Scripts/Bash/Cli/Functions/Verify + trunk Scripts Bash Cli Functions Verify + + Goals + This section exists to organize files related to centos-art.sh script verify functionality. The verify functionality of centos-art.sh script helps you to verify the workstation configuration you are planning to use as host for your working copy of CentOS Artwork Repository. + + + + Description + The first time you download CentOS Artwork Repository you need to configure your workstation in order to use centos-art.sh script. These preliminar configurations are based mainly on auxiliar RPM packages installation, symbolic links creations, and environment variables definitions. The verify functionality of centos-art.sh script guides you through this preliminar configuration process. + If this is the first time you run centos-art.sh script, the appropriate way to use its verify functionality is not using the centos-art.sh script directly, but the absolute path to centos-art.sh script instead (i.e., ~/artwork/trunk/Scripts/Bash/centos-art.sh). This is necessary because centos-art symbolic link, under ~/bin/ directory, has not been created yet. + + + Packages + Installation of auxiliar RPM packages provides the software required to manipulate files inside the repository (e.g., image files, documentation files, translation files, script files, etc.). Most of RPM packages centos-art.sh script uses are shipped with CentOS distribution, and can be installed from CentOS base repository. The only exception is inkscape, the package we use to manipulate SVG files. The inkscape package is not inside CentOS distribution so it needs to be installed from third party repositories. + + Note Configuration of third party repositories inside CentOS distribution is described in CentOS wiki, specifically in the following URL: http://wiki.centos.org/AdditionalResources/Repositories + + Before installing packages, the centos-art.sh script uses sudo to request root privileges to execute yum installation functionality. If your user isn't defined as a privileged user—at least to run yum commands— inside /etc/sudoers configuration file, you will not be able to perform package installation tasks as set in centos-art.sh script verify functionality. + Setting sudo privileges to users is an administrative task you have to do by yourself. If you don't have experience with sudo command, please read its man page running the command: man sudo. This reading will be very useful, and with some practice, you will be able to configure your users to have sudo privileges. + + + + Links + Creation of symbolic links helps us to alternate between different implementations of centos-art.sh script-line (e.g., centos-art.sh, for Bash implementation; centos-art.py, for Python implementation; centos-art.pl, for Perl implementation; and so on for other implementations). The centos-art.sh script-line definition takes place inside your personal binary (~/bin/) directory in order to make the script implementation —the one that centos-art links to— available to PATH environment variable. + Creation of symbolic links helps us to reuse components from repository working copy. For example, color information files maintained inside your working copy must never be duplicated inside program-specific configuration directories that uses them in your workstation (e.g., Gimp, Inkscape, etc.). Instead, a symbolic link must be created for each one of them, from program-specific configuration directories to files in the working copy. In this configuration, when someone commits changes to color information files up to central repository, they—the changes committed— will be immediatly available to your programs the next time you update your working copy —the place inside your workstation those color information files are stored—. + Creation of symbolic links helps us to make centos-art.sh script functionalities available outside trunk/ repository directory structure, but at its same level in repository tree. This is useful if you need to use the “render” functionality of centos-art.sh under branches/ repository directory structure as you usually do inside trunk/ repository directory structure. As consequence of this configuration, automation scripts cannot be branched under branches/Scripts directory structure. + + + + Environment variables + Definition of environemnt variables helps us to set default values to our user session life. The user session environment variable defintion takes place in the user's ~/.bash_profile file. The verify functionality of centos-art.sh script doesn't modify your ~/.bash_profile file. + The verify functionality of centos-art.sh script evaluates the following environment variables: + + + EDITOR + + Default text editor. + The centos-art.sh script uses default text EDITOR to edit pre-commit subversion messages, translation files, configuration files, script files, and similar text-based files. + If EDITOR environment variable is not set, centos-art.sh script uses /usr/bin/vim as default text editor. Otherwise, the following values are recognized by centos-art.sh script: + + • + + /usr/bin/vim + + + /usr/bin/emacs + + + /usr/bin/nano + + + If no one of these values is set in EDITOR environment variable, centos-art.sh uses /usr/bin/vim text editor by default. + + + + TEXTDOMAIN + + Default domain used to retrieve translated messages. This variable is set in initFunctions.sh and shouldn't be changed. + + + + TEXTDOMAINDIR + + Default directory used to retrieve translated messages. This variable is set in initFunctions.sh and shouldn't be changed. + + + + LANG + + Default locale information. + This variable is initially set in the configuration process of CentOS distribution installer (i.e., Anaconda), specifically in the Language step; or once installed using the system-config-language tool. + The centos-art.sh script uses the LANG environment variable to know in which language the script messages are printed out. + + + + TZ + + Default time zone representation. + This variable is initially set in the configuration process of CentOS distribution installer (i.e., Anaconda), specifically in the Date and time step; or once installed using the system-config-date tool. + The centos-art.sh script doesn't use the TZ environment variable information at all. Instead, this variable is used by the system shell to show the time information according to your phisical location on planet Earth. + Inside your computer, the time information is firstly set in the BIOS clock (which may need correction), and later in the configuration process of CentOS distribution installer (or later, by any of the related configuration tools inside CentOS distribution). Generally, setting time information is a straight-forward task and configuration tools available do cover most relevant location. However, if you need a time precision not provided by the configuration tools available inside CentOS distribution then, using TZ variable may be necessary. + + Convenction In order to keep changes syncronized between central repository and its working copies: configure both repository server and workstations (i.e., the place where each working copy is set on) to use Coordinated Universal Time (UTC) as base time representation. Later, correct the time information for your specific location using time zone correction. + + The format of TZ environment variable is described in tzset(3) manual page. + + +
+ + + + + Usage + + + centos-art verify --packages + + Verify required packages your workstation needs in order to run the centos-art.sh script correctly. If there are missing packages, the centos-art.sh script asks you to confirm their installation. When installing packages, the centos-art.sh script uses the yum application in order to achieve the task. + In case all packages required by centos-art.sh script are already installed in your workstation, the message The required packages are already installed. is output for you to know. + + + + centos-art verify --links + + Verify required links your workstation needs in order to run the centos-art command correctly. If any required link is missing, the centos-art.sh script asks you to confirm their installation. To install required links, the centos-art.sh script uses the ln command. + In case all links required by centos-art.sh script are already created in your workstation, the message The required links are already installed. is output for you to know. + In case a regular file exists with the same name of a required link, the centos-art.sh script outputs the Already exists as regular file. message when listing required links that will be installed. Of course, as there is already a regular file where must be a link, no link is created. In such cases the centos-art.sh script will fall into a continue installation request for that missing link. To end this continue request you can answer No, or remove the existent regular file to let centos-art.sh script install the link on its place. + + + + centos-art verify --environment + centos-art verify --environment --filter='regex' + + Output a brief description of environment variables used by centos-art.sh script. + If --filter option is provided, output is reduced as defined in the regex regular expression value. If --filter option is specified but regex value is not, the centos-art.sh script outputs information as if --filter option had not been provided at all. + + +
+ + + + See also + + + trunk Scripts Bash + trunk Scripts Bash + + + + + +
+ + + trunk Scripts Python + trunk Scripts Bash Cli Functions Verify + trunk +
+ trunk/Scripts/Python + trunk Scripts Python + + Goals + + • + + ... + + + + + + Description + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + + +
+ + + Index + List of Figures + trunk + Top + + Index + cp + + + + List of Figures + Index + Top + + List of Figures + + + + + diff --git a/Manuals/Repository/tags/chapter-intro.texi b/Manuals/Repository/tags/chapter-intro.texi new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/Manuals/Repository/tags/chapter-intro.texi diff --git a/Manuals/Repository/tags/chapter-menu.texi b/Manuals/Repository/tags/chapter-menu.texi new file mode 100644 index 0000000..8b13789 --- /dev/null +++ b/Manuals/Repository/tags/chapter-menu.texi @@ -0,0 +1 @@ + diff --git a/Manuals/Repository/tags/chapter-nodes.texi b/Manuals/Repository/tags/chapter-nodes.texi new file mode 100644 index 0000000..8b13789 --- /dev/null +++ b/Manuals/Repository/tags/chapter-nodes.texi @@ -0,0 +1 @@ + diff --git a/Manuals/Repository/tags/chapter.texi b/Manuals/Repository/tags/chapter.texi new file mode 100644 index 0000000..2b05ba0 --- /dev/null +++ b/Manuals/Repository/tags/chapter.texi @@ -0,0 +1,6 @@ +@node tags +@chapter tags +@cindex tags +@include tags/chapter-intro.texi +@include tags/chapter-menu.texi +@include tags/chapter-nodes.texi diff --git a/Manuals/Repository/trunk/Identity.texi b/Manuals/Repository/trunk/Identity.texi new file mode 100644 index 0000000..65f22ca --- /dev/null +++ b/Manuals/Repository/trunk/Identity.texi @@ -0,0 +1,126 @@ +@subsection Goals + +The @file{trunk/Identity} directory exists to organize CentOS +corporate identity artworks. + +@subsection Description + +The CentOS Project corporate identity is the ``persona'' of the +organization known as The CentOS Project. The CentOS Project +corporate identity plays a significant role in the way the CentOS +Project, as organization, presents itself to both internal and +external stakeholders. In general terms, the CentOS Project corporate +visual identity expresses the values and ambitions of the CentOS +Project organization, its business, and its characteristics. + +The CentOS Project corporate identity provides visibility, +recognizability, reputation, structure and identification to the +CentOS Project organization by means of corporate design, corporate +communication, and corporate behaviour. + +The CentOS Project settles down its corporate visual identity on a +``monolithic corporate visual identity structure''. In this structure +The CentOS Project uses one unique name (The CentOS Brand) and one +unique visual style (The CentOS Default Theme) in all its +manifestations. + +@table @strong + +@item The CentOS Brands +The CentOS brand is the name or trademark that conncects the producer +with their products. In this case, the producer is The CentOS Project +and the products are the CentOS distributions, the CentOS web sites, +the CentOS promotion stuff, etc. + +@xref{trunk Identity Brands}, for more information. + +@item The CentOS Themes + +The CentOS themes are a set of image files connected all together by +one unique visual style. Each theme is organized in different visual +manifestations, in order to cover each visual manifestation of The +CentOS Project (i.e., distributions, websites, promotion stuff, etc.). +@xref{trunk Identity Themes}, for more information. +@end table + +Inside a monolithic corporate visual identity structure, internal and +external stakeholders use to feel a strong sensation of uniformity, +orientation, and identification with the organization. No matter if +you are visiting websites, using the distribution, or acting on social +events, the one unique name and one unique visual style conect them +all to say: Hey! we are all parts of the CentOS project. And, +probably, some vister will say: Can I join the party? Yes you can, it +is free. :) + +@subsection Usage + +To produce identity artworks, use the following commands: + +@table @samp +@item centos-art render 'path/to/dir' + +When @samp{path/to/dir} refers to one renderable directory under +@file{trunk/Identity}, this command renders identity artworks using +both related design models and related translation files. + +@item centos-art render 'path/to/dir' --filter='pattern' + +When @samp{path/to/dir} refers to one renderable directory under +@file{trunk/Identity}, this command renders identity artworks using +both related design models and related translation files that match +the regular expression passed in @samp{--filter='pattern'} argument. + +To control the number of files produced by @command{centos-art} +command, you need to look into the translation path and provide a +regular expression pattern that matches the translation path, or +paths, related to the file, or files, you want to produce. + +The regular expression pattern you provide to @command{centos-art} +command is applied to the translation path from its very beginning. +It is not the same to say @samp{5/en/01-welcome} that +@samp{01-welcome}, the frist expression matches but the last one does +not. + +When using @samp{--filter='pattern'} you don't need to specify the +file extension. It is removed from translation path before applying +the pattern, so it doesn't count here. +@end table + +@subsection File name convenctions + +As file name convenction, inside CentOS Artwork Repository, both +text-based and image-based file name produced by @command{centos-art.sh} +script has the same name of their translation files without +the @samp{.sed} extension. The file extension is set as follow: + +@subsubsection When text-based files are rendered + +Text-based files end up having the same extension of their design +template file. + +@subsubsection When image-based files are rendered + +Image-based files always end up having the @file{.png} extension. + +@quotation +@strong{Tip} Once @file{.png} images are created, other image formats +may be created using the @command{renderFormats} post-rendering +action, inside the image-based related pre-rendering configuration +script. + +@xref{trunk Scripts Bash}, for more information. +@end quotation + +@subsection See also + +@menu +@comment --- Removed(* trunk Translations::) --- +@end menu + +@subsection References + +@itemize +@item @url{http://en.wikipedia.org/Corporate_identity} (and related +links). +@end itemize + diff --git a/Manuals/Repository/trunk/Identity/Brands.texi b/Manuals/Repository/trunk/Identity/Brands.texi new file mode 100644 index 0000000..9cf9a6e --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Brands.texi @@ -0,0 +1,14 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@subsection Usage + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Fonts.texi b/Manuals/Repository/trunk/Identity/Fonts.texi new file mode 100644 index 0000000..ef6730a --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Fonts.texi @@ -0,0 +1,79 @@ +@subsection Goals + +This section exists to organize digital typographies used by the +CentOS project. + +@subsection Description + +@subsection Usage + +The CentOS corporate identity is attached to @samp{DejaVu LGC} +font-family. Whatever artwork you design for CentOS project, that +requires typography usage, must be done using @samp{DejaVu LGC} +font-family. + +@table @strong +@item Recommendation-1: + +For screen desings (e.g., anything that final destination will never +be printed on paper or any medium outside computer screens) use +@samp{DejaVu LGC Sans} font-family. + +@item Recommendation-2: + +For non-screen designs (e.g., anything that final desition will be +printed on paper or any other medium outside computer screens) use +@samp{DejaVu LGC Serif} font-family. As convenction files described in +this rule are stored under @samp{Stationery} directories. +@end table + +The only execption for the two recommendations above is the typography +used inside CentOS logo. The CentOS logo is the main visual +representation of the CentOS project so the typography used in it must +be the same always, no matter where it be shown. It also has to be +clear enough to dismiss any confussion between similar typefaces +(e.g., the number one (1) sometimes is confuesed with the letter +@samp{el} (l) or letter @samp{ai} (i)). + +As CentOS logo typography convenction, the word @samp{CentOS} uses +@samp{Denmark} typography as base, both for the word @samp{CentOS} and +the phrase @samp{Community Enterprise Operating System}. The phrase +size of CentOS logo is half the size in poits the word @samp{CentOS} +has and it below @samp{CentOS} word and aligned with it on the left. +The distance between @samp{CentOS} word and phrase @samp{Community +Enterprise Operating System} have the size in points the phrase has. + +When the CentOS release brand is built, use @samp{Denmark} typography +for the release number. The release number size is two times larger +(in height) than default @samp{CentOS} word. The separation between +release number and @samp{CentOS} word is twice the size in points of +separation between @samp{CentOS} word and phrase @samp{Community +Enterprise Operating System}. + +Another component inside CentOS logo is the trademark symbol (TM). +This symbol specifies that the CentOS logo must be consider a product +brand, even it is not a registered one. The trademark symbol uses +DejaVu LGC Sans Regular typography. The trademark symbol is aligned +right-top on the outter side of @samp{CentOS} word. The trademark +symbol must not exceed haf the distance, in points, between +@samp{CentOS} word and the release number on its right. + +It would be very convenient for the CentOS Project and its community +to to make a registered trademark (®) of CentOS logo. To make a +register trademark of CentOS Logo prevents legal complications in the +market place of brands. It grants the consistency, through time, of +CentOS project corporate visual identity. + +@quotation +@strong{Note} The information about trademarks and corporate identity +is my personal interpretation of +@url{http://en.wikipedia.org/Corporate_identity} and +@url{http://en.wikipedia.org/Trademark} description. If you have +practical experiences with these affairs, please serve yourself to +improve this section with your reasons. +@end quotation + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Icons.texi b/Manuals/Repository/trunk/Identity/Icons.texi new file mode 100644 index 0000000..9cf9a6e --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Icons.texi @@ -0,0 +1,14 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@subsection Usage + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Isolinux.texi b/Manuals/Repository/trunk/Identity/Isolinux.texi new file mode 100644 index 0000000..9cf9a6e --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Isolinux.texi @@ -0,0 +1,14 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@subsection Usage + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Models.texi b/Manuals/Repository/trunk/Identity/Models.texi new file mode 100644 index 0000000..3973252 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Models.texi @@ -0,0 +1,19 @@ +@subsection Goals + +This section exists to organize design models. + +@subsection Description + +Design models are representative designs useful to understand how +to build artworks. + +@subsection Usage + +@subsection See also + +@menu +* trunk Identity Models Html:: +* trunk Identity Models Css:: +* trunk Identity Models Tpl:: +* trunk Identity Models Xcf:: +@end menu diff --git a/Manuals/Repository/trunk/Identity/Models/Css.texi b/Manuals/Repository/trunk/Identity/Models/Css.texi new file mode 100644 index 0000000..5639459 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Models/Css.texi @@ -0,0 +1,21 @@ +@subsection Goals + +This directory exists to provide common style sheets (CSS) definitions +to HTML design models. + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Models/Html.texi b/Manuals/Repository/trunk/Identity/Models/Html.texi new file mode 100644 index 0000000..fb39647 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Models/Html.texi @@ -0,0 +1,22 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Models/Img/Promo/Web.texi b/Manuals/Repository/trunk/Identity/Models/Img/Promo/Web.texi new file mode 100644 index 0000000..ec9b88b --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Models/Img/Promo/Web.texi @@ -0,0 +1,23 @@ +@subsection Goals + +@itemize +@item Provide images related to CentOS web interface. +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +* trunk Identity Models Tpl Promo Web:: +@end menu diff --git a/Manuals/Repository/trunk/Identity/Models/Tpl.texi b/Manuals/Repository/trunk/Identity/Models/Tpl.texi new file mode 100644 index 0000000..fb39647 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Models/Tpl.texi @@ -0,0 +1,22 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Models/Tpl/Promo/Web.texi b/Manuals/Repository/trunk/Identity/Models/Tpl/Promo/Web.texi new file mode 100644 index 0000000..56b7f37 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Models/Tpl/Promo/Web.texi @@ -0,0 +1,329 @@ +@subsection Goals + +Organize scalable vector graphics (svg) to help describe the CentOS +web environment. + +@subsection 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: + +@itemize +@item One unique name and one unique visual style to all web +applications used inside the web environment. + +@item One-step navigation to web applications inside the environment. + +@item High degree of customization to change the visual style of all +web applications with few changes (e.g, updating just two or three +images plus common style sheet [CSS] definitions). +@end itemize + +The CentOS project is attached to a monolithic corporate visual +identity (@pxref{trunk Identity}), where all visual manifestations +have one unique name and one unique visual style. This way, the CentOS +web environment has one unique name (the CentOS brand) and one unique +visual style (the CentOS default theme) for all its visual +manifestations, the web applications in this case. + +Since a maintainance point of view, achiving the one unique visual +style inside CentOS web environment is not a simple task. The CentOS +web environment is built upon many different web applications which +have different visual styles and different internal ways to customize +their own visual styles. For example: MoinMoin, the web application +used to support the CentOS wiki (@url{http://wiki.centos.org/}) is +highly customizable but Mailman (in its 2.x.x serie), the web +application used to support the CentOS mailing list, doesn't +support@footnote{The theme support of Mailman may be introduced in +mailman-3.x.x release.} a customization system that separates +presentation from logic, similar to that used by MoinMoin. + +This visual style diversity complicates our goal of one unique visual +style for all web applications. So, if we want one unique visual style +for all web applications used, it is innevitable to modify the web +applications in order to implement the CentOS one unique visual style +customization in them. Direct modification of upstream applications is +not convenient because upstream applications come with their one +visual style and administrators take the risk of loosing all +customization changes the next time the application be updated (since +not all upstream web applications, used in CentOS web environment, +separate presentation from logic). + +To solve the ``one unique visual style'' issue, installation and +actualization of web applications ---used inside CentOS web +environment--- need to be independent from upstream web applications +development line; in a way that CentOS web environment administrators +can install and update web applications freely without risk of loosing +the one unique visual style customization changes. + +At the surface of this issue we can see the need of one specific yum +repository to store CentOS web environment customized web applications. + +@subsubsection Design model (without ads) + +@subsubsection Design model (with ads) + +@subsubsection HTML definitions + +@subsubsection Controlling visual style + +Inside CentOS web environment, the visual style is controlled by the +following compenents: + +@table @strong +@item Webenv header background +@verbatim +trunk/Identity/Themes/Motifs/$THEME/Backgrounds/Img/1024x250.png +@end verbatim + +@item CSS definitions +@verbatim +trunk/Identity/Themes/Models/Default/Promo/Web/CSS/stylesheet.css +@end verbatim +@end table + +@subsubsection Producing visual style + +The visual style of CentOS web environment is defined in the following +files: + +@verbatim +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 +@end verbatim + +As graphic designer you use @file{1024x250.xcf} file to produce +@file{1024x250-bg.png} file. Later, inside @file{1024x250.svg} file, +you use the @file{1024x250-bg.png} file as background layer to draw +your vectorial design. When you consider you artwork ready, use the +@command{centos-art.sh} script, as described below, to produce the +visual style controller images of CentOS web environment. + +@verbatim +centos-art render --entry=trunk/Identity/Themes/Motifs/$THEME/Backgrounds --filter='1024x250' +@end verbatim + +Once you have rendered required image files, changing the visual style +of CentOS web environment is a matter of replacing old image files +with new ones, inside webenv repository file system structure. The +visual style changes will take effect the next time customization line +of CentOS web applications be packaged, uploded, and installed from +[webenv] or [webenv-test] repositories. + +@subsubsection 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. + +@subsubsection Development and release cycle + +The CentOS web environment development and relase cycle is described +below: + +@table @strong + +@item Download + +The first action is download the source code of web applications we +want to use inside CentOS web environment. + +@quotation +@strong{Important} The source location from which web application are +downloaded is very important. Use SRPMs from CentOS @strong{[base]} +and @strong{[updates]} repositories as first choise, and third party +repositories (e.g. RPMForge, EPEL, etc.) as last resource. +@end quotation + +@item Prepare + +Once web application source code has been downloaded, our duty is +organize its files inside @samp{webenv} version controlled repository. + +When preparing the structure keep in mind that different web +applications have different visual styles, and also different ways to +implement it. A convenient way to organize the file system structure +would be create one development line for each web application we use +inside CentOS web environment. For example, consider the following +file system structure: + +@verbatim +https://projects.centos.org/svn/webenv/trunk/ +|-- WebApp1/ +| |-- Sources/ +| | `-- webapp1-0.0.1/ +| |-- Rpms/ +| | `-- webapp1-0.0.1.rpm +| |-- Srpms/ +| | `-- webapp1-0.0.1.srpm +| `-- Specs/ +| `-- webapp1-0.0.1.spec +|-- WebApp2/ +`-- WebAppN/ +@end verbatim + +@item Customize + +Once web applications have been organized inside the version +controlled repository file system, use subversion to create the CentOS +customization development line of web applications source code. For +example, using the above file system structure, you can create the +customization development line of @file{webapp1-0.0.1/} with the +following command: + +@verbatim +svn cp trunk/WebApp1/Sources/webapp1-0.0.1 trunk/WebApp1/Sources/webapp1-0.0.1-webenv +@end verbatim + +The command above creates the following structure: + +@verbatim +https://projects.centos.org/svn/webenv/trunk/ +|-- WebApp1/ +| |-- Sources/ +| | |-- webapp1-0.0.1/ +| | `-- webapp1-0.0.1-webenv/ +| |-- Rpms/ +| | `-- webapp1-0.0.1.rpm +| |-- Srpms/ +| | `-- webapp1-0.0.1.srpm +| `-- Specs/ +| `-- webapp1-0.0.1.spec +|-- WebApp2/ +`-- WebAppN/ +@end verbatim + +In the above structure, the @file{webapp1-0.0.1-webenv/} directory is +the place where you customize the visual style of +@file{webapp1-0.0.1/} web application. + +@quotation +@strong{Tip} Use the @command{diff} command of Subversion between +CentOS customization and upstream development lines to know what you +are changing exactly. +@end quotation + +@item Build packages + +When web application has been customized, build the web application +RPM and SRPM using the source location with @samp{-webenv} prefix. + +@verbatim +https://projects.centos.org/svn/webenv/trunk/ +|-- WebApp1/ +| |-- Sources/ +| | |-- webapp1-0.0.1/ +| | `-- webapp1-0.0.1-webenv/ +| |-- Rpms/ +| | |-- webapp1-0.0.1.rpm +| | `-- webapp1-0.0.1-webenv.rpm +| |-- Srpms/ +| | |-- webapp1-0.0.1.srpm +| | `-- webapp1-0.0.1-webenv.srpm +| `-- Specs/ +| |-- webapp1-0.0.1.spec +| `-- webapp1-0.0.1-webenv.spec +|-- WebApp2/ +`-- WebAppN/ +@end verbatim + +@item Release for testing + +When the customized web application has been packaged, make packages +available for testing and quality assurance. This can be achives using +a [webenv-test] yum repository. + +@quotation +@strong{Note} The [webenv-test] repository is not shipped inside +CentOS distribution default yum configuraiton. In order to use +[webenv-test] repository you need to configure it first. +@end quotation + +If some problem is found to install/update/use the customized version +of web application, the problem is notified somewhere (a bugtracker +maybe) and the customization face is repated in order to fix the +problem. To release the new package add a number after @samp{-webenv} +prefix. For example, if some problem is found in +@file{webapp1-0.0.1-webenv.rpm}, when it be fixed the new package will +be named @file{webapp1-0.0.1-webenv-1.rpm}. If a problem is found in +@file{webapp1-0.0.1-webenv-1.rpm}, when it be fixed the new package +will be named @file{webapp1-0.0.1-webenv-2.rpm}, and so on. + +The ``customization --- release for testing'' process is repeated +until CentOS quality assurance team considers the package is ready for +production. + +@item Release for production + +When customized web application packages are considered ready for +production they are moved from [webenv-test] to [webenv] repository. +This action is commited by CentOS quality assurance team. + +@quotation +@strong{Note} The [webenv] repository is not shipped inside CentOS +distribution default yum configuraiton. In order to use [webenv] +repository you need to configure it first. +@end quotation +@end table + +@subsubsection The [webenv-test] repository + +@verbatim +/etc/yum.repos.d/CentOS-Webenv-test.repo +@end verbatim + +@verbatim +[webenv-test] +name=CentOS-$releasever - Webenv-test +mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv-test +#baseurl=http://mirror.centos.org/centos/$releasever/webenv-test/$basearch/ +gpgcheck=1 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever +enabled=1 +priority=10 +@end verbatim + +@subsubsection The [webenv] repository + +@verbatim +/etc/yum.repos.d/CentOS-Webenv.repo +@end verbatim + +@verbatim +[webenv] +name=CentOS-$releasever - Webenv +mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=webenv +#baseurl=http://mirror.centos.org/centos/$releasever/webenv/$basearch/ +gpgcheck=1 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever +enabled=1 +priority=10 +@end verbatim + +@subsubsection Priority configuration + +Both [webenv] and [webenv-test] repositories update packages inside +CentOS [base] and CentOS [updates] repositories. + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +* trunk Identity Models Img Promo Web:: +@end menu diff --git a/Manuals/Repository/trunk/Identity/Models/Xcf.texi b/Manuals/Repository/trunk/Identity/Models/Xcf.texi new file mode 100644 index 0000000..fb39647 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Models/Xcf.texi @@ -0,0 +1,22 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Release.texi b/Manuals/Repository/trunk/Identity/Release.texi new file mode 100644 index 0000000..9cf9a6e --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Release.texi @@ -0,0 +1,14 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@subsection Usage + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes.texi b/Manuals/Repository/trunk/Identity/Themes.texi new file mode 100644 index 0000000..01a20c1 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes.texi @@ -0,0 +1,26 @@ +@subsection Goals + +The @file{trunk/Identity/Themes/} directory exists to organize +production of CentOS themes. + +@subsection Description + +@subsection 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. + +@menu +* trunk Identity Themes Models:: +* trunk Identity Themes Motifs:: +@end menu + +@subsection See also + +@menu +* trunk Identity:: +* trunk:: +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Models.texi b/Manuals/Repository/trunk/Identity/Themes/Models.texi new file mode 100644 index 0000000..b91973a --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Models.texi @@ -0,0 +1,30 @@ +@subsection Goals + +@itemize +@item Organize theme models. +@end itemize + +@subsection 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. + +@subsection 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 `@xref{trunk Identity +Themes Models Default, Default},' and `@xref{trunk Identity Themes +Models Alternative, Alternative},' ready-to-use theme models. + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Models/Alternative.texi b/Manuals/Repository/trunk/Identity/Themes/Models/Alternative.texi new file mode 100644 index 0000000..483226a --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Models/Alternative.texi @@ -0,0 +1,26 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection 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. + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Models/Default.texi b/Manuals/Repository/trunk/Identity/Themes/Models/Default.texi new file mode 100644 index 0000000..6ce9103 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Models/Default.texi @@ -0,0 +1,27 @@ +@subsection Goals + +This location stores CentOS default theme model. The default theme +model of CentOS is used in all visual manifestations of CentOS Project +corporate visual identity (e.g., distributions, web sites, promotion, +etc.). + +@subsection Description + +@subsection 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 (@strong{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 @xref{trunk Identity Themes Motifs, Theme Motifs}. + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Models/Default/Distro.texi b/Manuals/Repository/trunk/Identity/Themes/Models/Default/Distro.texi new file mode 100644 index 0000000..d10a829 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Models/Default/Distro.texi @@ -0,0 +1,83 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +It applies to all major releases of CentOS distribution. + +@subsubsection 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. + +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. + +@quotation +@strong{Important} Remarking the CentOS release schema inside each +major release of CentOS distribution ---or similar visual +manifestation--- takes @emph{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. +@end quotation + +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 +@emph{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. + +@subsubsection One theme for each major release + +Other way we've been using to remark CentOS release schema is +applying one unique theme for @emph{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 @emph{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 @emph{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. + +@subsection Usage + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Models/Default/Distro/Anaconda.texi b/Manuals/Repository/trunk/Identity/Themes/Models/Default/Distro/Anaconda.texi new file mode 100644 index 0000000..9cf9a6e --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Models/Default/Distro/Anaconda.texi @@ -0,0 +1,14 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@subsection Usage + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Models/Default/Promo.texi b/Manuals/Repository/trunk/Identity/Themes/Models/Default/Promo.texi new file mode 100644 index 0000000..7bfbe48 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Models/Default/Promo.texi @@ -0,0 +1,27 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection 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. + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Models/Default/Web.texi b/Manuals/Repository/trunk/Identity/Themes/Models/Default/Web.texi new file mode 100644 index 0000000..427850f --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Models/Default/Web.texi @@ -0,0 +1,26 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection 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. + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Motifs.texi b/Manuals/Repository/trunk/Identity/Themes/Motifs.texi new file mode 100644 index 0000000..7b8c0e0 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Motifs.texi @@ -0,0 +1,114 @@ +@subsection Goals + +The @file{trunk/Identity/Themes/Motifs} directory exists to: + +@itemize +@item Organize CentOS themes' artistic motifs. +@end itemize + +@subsection Description + +The artistic motif of theme is a graphic design component that +provides the visual style of themes, it is used as pattern to connect +all visual manifestations inside one unique theme. + +Artistic motifs are based on conceptual ideas. Conceptual ideas bring +the motivation, they are fuel for the engines of human imagination. +Good conceptual ideas may produce good motivation to produce almost +anything, and art works don't escape from it. + +@table @samp +@item TreeFlower +CentOS like trees, has roots, trunk, branches, leaves and flowers. Day +by day they work together in freedom, ruled by the laws of nature and +open standards, to show the beauty of its existence. +@item Modern +Modern, squares and circles flowing up. +@end table + +If you have new conceptual ideas for CentOS, then you can say that you +want to create a new artistic motif for CentOS. To create a new +artistic motif you need to create a directory under +@file{Identity/Themes/Motifs/} using a name coherent with your +conceptual idea. That name will be the name of your artistic motif. If +possible, when creating new conceptual ideas for CentOS, think about +what CentOS means for you, what does it makes you feel, take your +time, think deep, and share; you can improve the idea as time goes on. + +Once you have defined a name for your theme, you need to create the +motif structure of your theme. The motif structure is the basic +direcotry structure you'll use to work your ideas. Here is where you +organize your graphic design projects. + +To add a new motif structure to CentOS Artwork Repository, you need to +use the @command{centos-art} command line in the +@file{Identity/Themes/Motifs/} directory as described below: + +@example +centos-art add --motif=ThemeName +@end example + +The previous command will create the basic structure of themes for +you. The basic structure produced by @command{centos-art} command is +illustrated in the following figure: + +@example +trunk/Identity/Themes/Motifs/$ThemeName/ +|-- Backgrounds +| |-- Img +| `-- Tpl +|-- Info +| |-- Img +| `-- Tpl +|-- Palettes +`-- Screenshots +@end example + +@subsection Usage + +When designing artistic motifs for CentOS, consider the following +recommendations: + +@itemize +@item Give a unique (case-sensitive) name to your Motif. This name is +used as value wherever theme variable (@b{$THEME}) or translation marker +(@b{=THEME=}) is. Optionally, you can add a description about +inspiration and concepts behind your work. + +@item Use the location @file{trunk/Identity/Themes/Motifs/$THEME/} to +store your work. If it doesn't exist create it. Note that this require +you to have previous commit access in CentOS Artwork Repository. + +@item The CentOS Project is using the blue color (@b{#204c8d}) as base +color for its corporate visual identity. Use such base corporate color +information as much as possible in your artistic motif designs. + +@item Try to make your design fit one of the theme models. + +@item Feel free to make your art enterprise-level and beautiful. + +@item Add the following information on your artwork (both in a visible +design area and document metadata): + +@itemize + +@item The name (or logo) of your artistic motif. + +@item The copyright sentence: @b{Copyright (C) YEAR YOURNAME} + +@item The license under which the work is released. All CentOS Art +works are released under +@url{http://creativecommons.org/licenses/by-sa/3.0/,Creative Common +Share-Alike License 3.0} +(@url{http://creativecommons.org/licenses/by-sa/3.0/}). + +@end itemize +@end itemize + +@subsection See also + +@menu +* trunk Identity Themes:: +* trunk Identity:: +* trunk:: +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Motifs/Flame.texi b/Manuals/Repository/trunk/Identity/Themes/Motifs/Flame.texi new file mode 100644 index 0000000..b9e787a --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Motifs/Flame.texi @@ -0,0 +1,206 @@ +@subsection Goals + +This section describes the steps we followed to construct the +@emph{Flame} artistic motif. This section may be useful for anyone +interested in reproducing the @emph{Flame} artistic motif, or in +creating new artistic motifs for The CentOS Project corporate visual +identity (@pxref{trunk Identity}). + +@subsection Description + +The @emph{Flame} artistic motif was built using the flame filter of +Gimp 2.2 in CentOS 5.5. + +The flame filter of Gimp can produce stunning, randomly generated +fractal patterns. The flame filter of Gimp gives us a great oportunity +to reduce the time used to produce new artistic motifs, because of its +``randomly generated'' nature. Once the artistic motif be created, it +is propagated through all visual manifestations of CentOS Project +corporate visual identity using the @file{centos-art.sh} script +(@pxref{trunk Scripts Bash}) inside the CentOS Artwork Repository. + +To set the time intervals between each new visual style production, we +could reuse the CentOS distribution major release schema. I.e., we +could produce a new visual style, every two years, based on a new +``randomly generated'' flame pattern, and publish the whole corporate +visual identity (i.e., distribution stuff, promotion stuff, websites +stuff, etc.) with the new major release of CentOS distribution all +together at once. + +Producing a new visual style is not one day's task. Once we have +defined the artistic motif, we need to propagate it through all visual +manifestations of The CentOS Project corporate visual identity. When +we say that we could produce one new visual style every two years we +really mean: to work two years long in order to propagate a new visual +style to all visual manifestations of The CentOS Project corporate +visual identity. + +Obviously, in order to propagate one visual style to all different +visual manifestations of The CentOS Project corporate visual identity, +we need first to know which the visual manifestations are. To define +which visual manifestations are inside The CentOS Project corporate +visual identity is one of the goals the CentOS Artwork Repository and +this documentation manual are both aimed to satisfy. + +Once we define which the visual manifestation are, it is possible to +define how to produce them, and this way, organize the automation +process. Such automation process is one of the goals of +@file{centos-art.sh} script. + +With the combination of both CentOS Artwork Repository and +@file{centos-art.sh} scripts we define work lines where translators, +programmers, and graphic designers work together to distribute and +reduce the amount of time employed to produce The CentOS Project +monolithic corporate identity. + +From a monolithic corporate visual identity point of view, notice that +we are producing a new visual style for the same theme (i.e., +@emph{Flame}). It would be another flame design but still a flame +design. This idea is very important to be aware of, because we are +somehow ``refreshing'' the theme, not changing it at all. + +This way, as we are ``refreshing'' the theme, we still keep oursleves +inside the monolithic conception we are trying to be attached to +(i.e., one unique name, and one unique visual style for all visual +manifestations). + +Producing artistic motifs is a creative process that may consume long +time, specially for people without experienced knowledge on graphic +design land. Using ``randomly generated'' conception to produce +artistic motifs could be, practically, a way for anyone to follow in +order to produce maintainable artistic motifs in few steps. + +Due to the ``randomly generated'' nature of Flame filter, we find that +@emph{Flame} pattern is not always the same when we use @emph{Flame} +filter interface. + +Using the same pattern design for each visual manifestation is +essential in order to maintain the visual connection among all visual +manifestations inside the same theme. Occasionally, we may introduce +pattern variations in opacity, size, or even position but never change +the pattern design itself, nor the color information used by images +considered part of the same theme. + +@quotation +@strong{Important} +When we design background images, which are considered part of the +same theme, it is essential to use the same design pattern always. +This is what makes theme images to be visually connected among +themeselves, and so, the reason we use to define the word ``theme'' +as: a set of images visually connected among themeselves. +@end quotation + +In order for us to reproduce the same flame pattern always, +@emph{Flame} filter interface provides the @samp{Save} and @samp{Open} +options. The @samp{Save} option brings up a file save dialog that +allows you to save the current Flame settings for the plug-in, so that +you can recreate them later. The @samp{Open} option brings up a file +selector that allows you to open a previously saved Flame settings +file. + +The Flame settings we used in our example are saved in the file: + +@verbatim +trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def +@end verbatim + +@subsection Construction + +@subsubsection Step 1: Set image size + +Create an empty image and fill the @samp{Background} layer with black +(@code{000000}) color. Image dimensions depend on the final +destination you plan to use the image for. For the sake of our +construction example we used an image of 640x480 pixels and 300 pixels +per inch (ppi). + +@subsubsection Step 2: Add base color and pattern information + +Create a new layer named @samp{Base}, place it over @samp{Background} +layer and fill it with the base color (@code{7800ff}) you want to have +your background image set in. Add a mask to @samp{Base} layer using +radial gradient and blur it. You may need to repeat this step more +than once in order to achieve a confortable black radial degradation +on the right side of your design. + +Duplicate @samp{Base} layer and name it @samp{Paper}. Place +@samp{Paper} layer over @samp{Base} layer. Remove content of +@samp{Paper} layer and fill it with @samp{Paper (100x100)} pattern. +Once you've done with black radial degradation, reduce the +@samp{Paper} layer opacity to 20%. + +Notice that when we duplicate one layer, the mask information related +to layer is preserved from previous to next layer. This saves us some +of the time required to produce different layers with the same mask +information on them. + +Duplicate @samp{Paper} layer and rename it @samp{Stripes}. Remove +paper pattern from @samp{Stripes} layer. Fill @samp{Stripes} layer +with @samp{Stripes (48x48)} pattern and reduce the @samp{Stripes} +layer opacity to 15%. + +@subsubsection Step 3: Add flame motif + +Create a new layer named @samp{Flame}. Set the foreground +(@code{003cff}) and background (@code{0084ff}) colors to the gradient +you want to build the flame motif. + +To build flame motif, use the flame filter (@samp{Filters > Render > +Nature > Flame...}) on @samp{Flame} layer. We used a layer mask, with +a radial gradient on it to control the boundaries of flame motif on +@samp{Flame} layer. + +Duplicate @samp{Flame} layer and rename it `Flame Blur'. Place `Flame +Blur' below @samp{Flame} layer. Apply Gussian blur filter +(@samp{Filters > Blur > Gussian Blur...}) until reaching the desiered +effect. + +The opacity value, in @samp{Flame} layers, may vary from one image to +another based on the place the image will be finally placed on. For +example, images used as desktop background have the @samp{Flame} layer +opacity set at 100% but @samp{Flame Blur} is set to 70%. However, you +may find that background images used in anaconda progress slides have +opacity reduced differently, in order to reduce brightness in a way +that texts could look clean and readable over it. + +@subsubsection Step 4: Add foreground color + +Create a new layer named @samp{Color}, place it on top of all visible +layers and fill it with plain color (@code{4c005a}). Reduce +@samp{Color} layer opacity to 20%. You can use the @samp{Color} layer +to control the right side color information you want to produce the +image for. + +Duplicate @samp{Flame} layer and create a new layer named +@samp{Color#1}. Place @samp{Color#1} layer on top of layer named +@samp{Color}. Remove the mask information from @samp{Color#1} layer +and recreate a new one using an inverted alpha channel as reference. +Remove @samp{Color#1} layer content and fill it back with plain black +(@code{000000}) color. Reduce @samp{Color#1} opacity to 20%. In this +step we created a mask to protect the flame artistic motif from black +color, so when we decrement or increment the opacity of layer, the +flame artistic motif wouldn't be affected, just the environment +suround it. + +When you set color information, remember that the same artistic motif +needs to be indexed to 14 and 16 colors, in order to produce Grub and +Syslinux visual manifestations respectively. Using many different +colors in the artistic motif may reduce the possibility of your design +to fix all different situations in. Likewise, using more colors in +one design, and less colors in another design will reduce the +connectivity among your designs, since color information is relevant +to visual identity. + +When you propagate your artistic motif visual style to different +visual manifestations of CentOS Project corporate visual identity, it +is up to you to find out justice and compromise among all possible +variables you may face. + +@subsection See also + +@menu +* trunk Identity Themes Motifs:: +* trunk Identity Themes:: +* trunk Identity:: +* trunk:: +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern.texi b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern.texi new file mode 100644 index 0000000..306ab79 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern.texi @@ -0,0 +1,14 @@ +@subsection Presentation + +@subsection Construction + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi new file mode 100644 index 0000000..adda528 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi @@ -0,0 +1,143 @@ +@subsection Goals + +@itemize +@item Organize background images for Modern theme. +@end itemize + +@subsection Description + +Inside @file{Motifs} directory, the @file{Backgrounds/} directory is +used to create vectorial designs using Inkscape and background images +using Gimp. Later, you can export background images as @file{.png} and +load them in your vectorial design project using the import feautre of +Inkscape. + +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: + +@example +xcf/800x600.xcf +@end example + +to produce the background image: + +@example +img/800x600-bg.png +@end example + +which is loaded in: + +@example +svg/800x600.svg +@end example + +to produce the final background image: + +@example +img/800x600.png +@end example + +The @file{img/800x600.png} background image is produced automatically +by means of rendering scripts. + +In other cases (e.g. Anaconda), 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: + +@example +xcf/800x600-anaconda.xcf +@end example + +to produce the background image: + +@example +img/800x600-anaconda-bg.png +@end example + +which is loaded in: + +@example +svg/800x600-anaconda.svg +@end example + +to produce the file: + +@example +img/800x600-anaconda.png +@end example + +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 artistic +motif. + +Background images are linked (using the @b{import} feature of +Inkscape) inside almost all theme art works. This structure let you +make centralized changes on the visual identity and propagate them +quickly to other areas. + +In this structure you design background images for different screen +resolutions based on the theme artistic motif. + +You may create different artistic motifs propositions based +on the same conceptual idea. The conceptual idea is what defines a +theme. Artistic motifs are interpretations of that idea. + +Inside this directory artistic motifs are organized by name (e.g., +TreeFlower, Modern, etc.). + +Each artistic motif directory represents just one unique artistic +motif. + +The artistic motif is graphic design used as common pattern to connect +all visual manifestations inside one unique theme. The artistic motif +is based on a conceptual idea. Artistic motifs provide visual style +to themes. + +Designing artistic motifs is for anyone interested in creating +beautiful themes for CentOS. When building a theme for CentOS, the +first design you need to define is the artistic motif. + + +Inside CentOS Artwork Repository, theme visual styles (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 @command{centos-art} command line +interface to render the visual style, you are currently producing, +against an already-made theme model in order to produce the final +result. Final images are stored under @file{Motifs/} directory using +the model name, and the model directory structure as reference. + +The artistic motif base structure is used by @command{centos-art} to +produce images automatically. This section describes each directory of +CentOS artistic motif base structure. + +@subsection Usage + +The @file{Backgrounds/} directory is probably the core component, +inside @file{Motifs/} directory structure. Inside @file{Backgrounds/} +directory you produce background images used by almost all theme +models (e.g., Distribution, Websites, Promotion, etc.). The +@file{Backgrounds/} directory can contain subdirectories to help you +organize the design process. + +@subsection See also + +@menu +* trunk Identity Themes Motifs Modern Backgrounds Img:: +* trunk Identity Themes Motifs Modern Backgrounds Tpl:: +* trunk Identity Themes Motifs Modern Backgrounds Xcf:: +@comment --- Removed(* trunk Translations Identity Themes Backgrounds::) --- +@end menu + diff --git a/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img.texi b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img.texi new file mode 100644 index 0000000..fc1ecfb --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img.texi @@ -0,0 +1,19 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@subsection Usage + +In this directory is where you store all background images (e.g., +.png, .jpg, .xpm, etc.). This directory is required by +@file{centos-art} command line interface. + +@subsection See also + +@menu +@end menu + diff --git a/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl.texi b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl.texi new file mode 100644 index 0000000..4b3308a --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl.texi @@ -0,0 +1,18 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@subsection Usage + +In this directory is where you store all the scalable vector graphics +(e.g., .svg) files. This directory is required by @file{centos-art} +command line interface. + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf.texi b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf.texi new file mode 100644 index 0000000..b572a3d --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf.texi @@ -0,0 +1,27 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + + +@subsection Usage + +In this directory is where you store the project files (e.g, .xcf) of +Gimp. This directory is not required by @file{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 +@file{Xcf/} directory to store background projects. Of course, you can +merge both Gimp and Inkscape power to produce images based on them. +In this last case you need the @file{Xcf/} directory. + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi new file mode 100644 index 0000000..8735b28 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi @@ -0,0 +1,59 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@subsection Usage + +To render Anaconda progress slide images using the @emph{Modern} +artistic motif design, the Default theme model, and available +translation files (--- @strong{Removed}(pxref:trunk Translations Identity Themes Distro +Anaconda Progress) ---); use the following commands: + +@example +cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ +centos-art render --identity +@end example + +The above command will create the following structure: + +@example +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 +@end example + + +@subsection See also + +@menu +@end menu + diff --git a/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Palettes.texi b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Palettes.texi new file mode 100644 index 0000000..79765d1 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Motifs/Modern/Palettes.texi @@ -0,0 +1,20 @@ +@subsection Goals + +@itemize +@item Organize palette files for Modern theme. +@end itemize + +@subsection Description + +@subsection 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 the unique color information +required by theme. + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Motifs/TreeFlower.texi b/Manuals/Repository/trunk/Identity/Themes/Motifs/TreeFlower.texi new file mode 100644 index 0000000..9cf9a6e --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Motifs/TreeFlower.texi @@ -0,0 +1,14 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@subsection Usage + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds.texi b/Manuals/Repository/trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds.texi new file mode 100644 index 0000000..32e0626 --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds.texi @@ -0,0 +1,323 @@ +@subsection Goals + +This section exists to orgnize backgrounds of @emph{TreeFlower} +artistic motif. + +@subsection Description + +@subsubsection Desktop background + +Once you have defined the vectorial artistic motif design, use the +@command{centos-art.sh} script (as described in usage section below) +to produce the png version of it. With the png version of your +vectorial design do the following: + +Open the png version with GIMP. + +Save the png version as a project of GIMP inside +@file{trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Xcf} +directory, using the same name of your vectorial design but with the +@samp{.xcf} extension. + +Now use GIMP to improve your design. Here you may add one layer for +pattern, another for colors, and so on until you find yourself +confortable with your artwork. For example, the following layer +distribution (from bottom to top) was used to build revision 285 of +file @file{1360x768.xcf} using @emph{TreeFlower} artistic motif at +revision 241. + +@table @strong +@item Layer 1: Background + +The first thing we did with GIMP was to create a layer named +@samp{Background} to store the artistic motif (File > Open as layer). +This layer is the lowest layer in the image. Later, we started to +create layers one upon another to change the artistic motif visual +style. + +@item Layer 2: Shadow#1 + +This layer is above @samp{Background} and contains a linear gradient +from left (000000) to right (transparent) covering the whole image. +This layer masks the artistic motif to avoid the effect of linear +gradient. This layer is 100% of opacity. + +@item Layer 3: Shadow#2 + +This layer is above @samp{Shadow#1} and contains a linear gradient +from left (000000) to right (transparent) covering just the 70% of the +whole image aproximatly. This layer doesn't mask the artistic motif +which make the left part of it fall into the dark of linear gradient. +This layer is 100% of opacity. + +@item Layer 4: Pattern (Paper) + +This layer is above @samp{Shadow#2} an contains the paper pattern +shipped with GIMP 2.2. This layer doesn't mask the artistic motif so +the pattern is applied over the whole image. This layer is set to 15% +of opacity. + +@item Layer 5: Pattern (Stripes) + +This layer is above @samp{Pattern (Paper)} and contains the stripes +used over the artistic motif. This layer do masks the artistic motif +so the stripes are only applied to it. This layer is set to 10% of +opacity. + +@item Layer 6: Shadow#3 + +This layer is above @samp{Pattern (Stripes)} and contains a linear +gradient from right (6600ff) to left (transparent). This layer masks +the artistic motif so the linear gradient doesn't affect it. This +layer is set to 15% of opacity. + +@item Layer 7: Shadow#4 + +This layer is above @samp{Shadow#3} and contains a +linear gradient from left (000000) to right (transparent). This layer +do masks the artistic motif so the linear gradient doesn't affect it. +This layer is set to 10% of opacity. + +@item Layer 8: Color#1 + +This layer is above @samp{Shadow#4} and is filled with orange (ffae00) +color over the whole image. This layer is set to 10% of opacity. + +@item Layer 9: Color#2 + +This layer is above @samp{Color#1} and is filled with +blue (010a88) color over the whole image. This layer is set to 10% of +opacity. + +@end table + +@quotation +@strong{Note} There is no definite combination. To get the appropriate +visual design is a matter of constant testing and personal taste. +@end quotation + +Finally, use @samp{Save as copy ...} option to export the final +design. To export the final design use the same name of your vectorial +design plus @samp{-final.png} extension. + +You can repeat these steps to create images for other screen +resolutions. + +@subsubsection Anaconda Prompt (syslinux) background + +When building syslinux backgrounds it is needed to take into account +that the final image is reduced to 16 colors. In desktop background +there is no color limitation but syslinux does have. The goal of this +section is achieving a final syslinux background as close as possible +to desktop backgrounds using 16 colors only. + +Another point to consider is the forground and background definition +used by syslinux. The syslinux documentation says that the color set +in position 0 is the background and color set in position 7 is the +forground. The final palette of color used by our background will +match that specification. For great contrast we'll use black as +background and white as forground. At this poing we have black +(000000) and white (ffffff) colors in our syslinux palette, which left +us with 14 colors to play with. + +Let's begin with @file{Xcf/640x300.xcf} layer distribution from bottom +to top: + +@table @strong +@item Layer 1: Background + +This layer is the lowest layer in the image composition and contains +the artistic motif image rendered for the same resolution (i.e., +@file{Img/Png/640x300.png}). This layer is set to 100% of opacity. + +@item Layer 2: Pattern (Paper) + +This layer is placed above @samp{Background} layer and contains the +paper pattern shipped with GIMP 2.2. This layer doesn't mask the +artistic motif. This layer is set to 30% of opacity. + +@item Layer 3: Pattern (Stripes) + +This layer is placed above @samp{Pattern (Paper)} layer and contains +the stripes pattern shipped with GIMP 2.2. This layer does mask the +artistic motif in order to apply the stripes over it only. The +background is not affected by the stripes pattern just the artistic +motif. This layer is set to 20% of opacity. + +@item Layer 4: Shadow#1 + +This layer is placed above @samp{Pattern (Stripes)} layer and fills +the entire layer area with violet (6600ff) color. This layer do mask +the artistic motif in order to applied the violet color to the +background area outside the artistic motif only. This layer is set to +15% of opacity. + +@item Layer 5: Color#1 + +This layer is above @samp{Shadow#1} and is filled with orange (ffae00) +color to cover the whole image. This layer is set to 10% of opacity. + +@item Layer 6: Color#2 + +This layer is above @samp{Color#1} and is filled with blue (010a88) +color to cover the whole image. This layer is set to 10% of opacity. + +@item Layer 7: Shadow#2 + +This layer is above @samp{Color#1} and contains a linear gradient from +left (000000) to right (transparent) covering 70% of the image +approximately. + +@end table + +At this point we have the composition and should look like the desktop +backgrounds. Compared with desktop backgrounds there are some +differences in opacity. This is because in our testings the final +color information found with this composition produces an acceptable +16 color image. Of course this is something we haven't seen yet. + +To define the color information of our current coposition, save the +syslinux background composition we've done using @samp{File > Save as +Copy ...} option in the following location: + +@verbatim +trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Img/Png/640x300-final.png +@end verbatim + +Now, create the final png version of syslinux backgrounds using the +following command: + +@verbatim +centos-art render --entry=trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Prompt +@end verbatim + +This command will create syslinux-splash final images for all major +releases of CentOS distribution the repository has been configured to. +The important files here are @file{syslinux-splash.png}, other +files may contain the wrong information because we haven't defined yet +the correct color information to use. + +Open one @file{syslinux-splash.png} file with GIMP and use the +@samp{Image > Mode > Indexed} to reduce image colors up to 16 colors, +using the @samp{Generate optimum palette} feature of GIMP. If the +image looks aceptable after reducing colors, use the @samp{Palettes} +menu (Ctrl+P) of GIMP to import a new palette from file and name it +@samp{CentOS-TreeFlower-Syslinux}. Once you've saved the palette, the +color information is stored at: + +@verbatim +~/.gimp-2.2/palettes/CentOS-TreeFlower-Syslinux.gpl +@end verbatim + +You need to edit @file{CentOS-TreeFlower-Syslinux.gpl} file in order +to set the appropriate order of colors. Remember black (000000) in +position 0, and white (ffffff) in position 7. Other positions are +irrelevant. When editing this file you may find that color reduction +did not set black and white colors to their respective values exactly. +Change that manually. For example, consider the following palette: + +@verbatim +GIMP Palette +Name: CentOS-TreeFlower-Syslinux +Columns: 16 +# + 0 0 0 Background (black) + 23 20 35 Untitled + 34 25 48 Untitled + 37 35 60 Untitled + 47 36 68 Untitled + 37 54 86 Untitled + 60 48 90 Untitled +255 255 255 Foreground (white) + 66 54 99 Untitled + 74 61 98 Untitled + 49 78 126 Untitled + 43 87 151 Untitled + 92 89 95 Untitled + 54 104 183 Untitled +158 153 156 Untitled +201 196 195 Untitled +@end verbatim + +Update the @samp{Palettes} menu to get the new color positions from +the file you just edited and open the palette with double click. + +Update the @file{syslinux.gpl} file copying the following file: + +@verbatim +~/.gimp-2.2/palettes/CentOS-TreeFlower-Syslinux.gpl +@end verbatim + +to + +@verbatim +trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.gpl +@end verbatim + +With the @samp{CentOS-TreeFlower-Syslinux} palette opened in the +@samp{Palette Editor}, open (Ctrl+O) the following file: + +@verbatim +trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.ppm +@end verbatim + +and replace its color information with that one in +@samp{CentOS-TreeFlower-Syslinux} palette. When you are replacing +color information inside @file{syslilnux.ppm}, remember to keep the +order of colors just as they are in the +@samp{CentOS-TreeFlower-Palette} palette. + +The @file{syslinux.ppm} file is 16 pixels width and 1 pixel height, so +you probably need to zoom it a bit to set the color information in +their place when using the pen tool with the brush @samp{Circle (01) +(1 x 1)}. + +Once you've updated the @samp{syslinux.ppm} file, it is time to update +the following file: + +@verbatim +trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.hex +@end verbatim + +The @file{syslinux.hex} file contains the color information in +hexadecimal notation. The color information in hexadecimal notation +is required by @command{ppmtolss16} command. The @command{ppmtolss16} +command produces the final LSS16 image format that is used by syslinux +program inside CentOS distribution. + +The color information inside @file{syslinux.hex} must match the one in +@file{syslinux.ppm} and @file{syslinux.gpl}. For example, based on +@file{CentOS-TreeFlower-Syslinux} palette of colors above, consider +the following @file{syslinux.hex} file: + +@verbatim +#000000=0 +#171423=1 +#221930=2 +#25233c=3 +#2f2444=4 +#253656=5 +#3c305a=6 +#ffffff=7 +#423663=8 +#4a3d62=9 +#314e7e=10 +#2b5797=11 +#5c595f=12 +#3668b7=13 +#9e999c=14 +#c9c4c3=15 +@end verbatim + +@subsubsection Grub background + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Identity/Widgets.texi b/Manuals/Repository/trunk/Identity/Widgets.texi new file mode 100644 index 0000000..9cf9a6e --- /dev/null +++ b/Manuals/Repository/trunk/Identity/Widgets.texi @@ -0,0 +1,14 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@subsection Usage + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Locales.texi b/Manuals/Repository/trunk/Locales.texi new file mode 100644 index 0000000..98a4746 --- /dev/null +++ b/Manuals/Repository/trunk/Locales.texi @@ -0,0 +1,56 @@ +The @file{trunk/Locales} directory exists to store the translation +messages used to produce content in different languages. + +Translation messages are organized using the directory structure of +the component being translated. For example, if we want to provide +translation messages for @file{trunk/Manuals/Filesystem}, then the +@file{trunk/Locales/Manuals/Filesystem} directory needs to be created. + +Once the locale directory exists for the component we want to provide +translation messages for, it is necessary to create the translation +files where translation messages are. The translation files follows +the concepts of @command{xml2po} and GNU @command{gettext} tools. + +The basic translation process is as follow: first, translatable +strings are extracted from files and a portable object template (.pot) +is created or updated with the information. Using the portable object +template, a portable object (.po) is created or updated for translator +to locale the messages retrived. Finally, a machine object (.mo) is +created from portable object to sotore the translated messages. + +Inside the repository there are two ways to retrive translatable +strings from files. The first one is through @command{xml2po} command +and the second through @command{xgettext} command. The @command{xml2po} +is used to retrive translatable strings from XML files (e.g., Scalable +Vector Graphics, DocBook, etc.) and the @command{xgettext} command is +used to retrive translatable strings from shell scripts files (e.g., +the files that make the @command{centos-art.sh} command-line +interface). + +When translatable strings are retrived from XML files, using the +@command{xml2po} command, there is no need to create the machine +object as we do when translatable strings ar retrived from shell +files, using the @command{xgettext} command. The @command{xml2po} +produces a temporal machine object in order to create a translated XML +file. Once the translated XML file has been created the machine object +is no longer needed. On the other hand, the machine object produced by +the @command{xgettext} command is required by the system in order for +the show shell script localized messages. + +Another difference between @command{xml2po} and @command{xgettext} we +need to be aware of is the directory structure used to store machine +objects. In @command{xml2po}, the machine object is created in the +current working directory as @file{.xml2po.mo} and can be safetly +removed once the translated XML file has been created. In the case of +@command{xgettext}, the machine object needs to be stored in the +@file{$TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo} file in order +for the system to interpret it and should not be removed since it is +the file that contain the translation messages themselves. + +Automation of localization tasks is achived through the @code{locale} +functionality of command-line interface. + +@menu +* trunk Scripts Bash Cli Functions Locale:: +@end menu + diff --git a/Manuals/Repository/trunk/Locales/Identity.texi b/Manuals/Repository/trunk/Locales/Identity.texi new file mode 100644 index 0000000..5bf1b70 --- /dev/null +++ b/Manuals/Repository/trunk/Locales/Identity.texi @@ -0,0 +1,29 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@comment --- Removed(* trunk Translations Identity Brands::) --- +@comment --- Removed(* trunk Translations Identity Fonts::) --- +@comment --- Removed(* trunk Translations Identity Models::) --- +@comment --- Removed(* trunk Translations Identity Release::) --- +@comment --- Removed(* trunk Translations Identity Themes::) --- +@comment --- Removed(* trunk Translations Identity Widgets::) --- +* trunk Identity:: +@end menu diff --git a/Manuals/Repository/trunk/Locales/Identity/Brands.texi b/Manuals/Repository/trunk/Locales/Identity/Brands.texi new file mode 100644 index 0000000..6f771ef --- /dev/null +++ b/Manuals/Repository/trunk/Locales/Identity/Brands.texi @@ -0,0 +1,105 @@ +@subsection Goals + +@itemize +@item Organize brands' translation files. +@end itemize + +@subsection Description + +Translation files, inside @file{trunk/Translations/Identity/Brands} +translation entry, don't use default rendering translation +functionality, they use the following translation pre-rendering +configuration file instead: + +@verbatim +/home/centos/artwork/trunk/Translation/Identity/Brands/render.conf.sh +@end verbatim + +Inside @file{trunk/Translations/Identity/Brands} translation entry, +translation files are symbolic links pointing to the common template +translation structure, inside the translation template (@samp{Tpl/}) +directory. + +Inside @file{trunk/Translations/Identity/Brands} translation entry, +translation files are created using identity design templates as +reference. The translation pre-rendering script creates a translation +structure where the translation template (@samp{Tpl/}) directory +structure applies to each single design template available. + +For example, if the brands' translation template (@samp{Tpl/}) +directory has 30 translation files, and there are 20 design templates; +the brands' translation pre-rendering script creates a translation +structure of symbolic links where the 30 translation files apply the +20 design templates one by one, producing 600 translation symbolic +links as result. At this point, when rendering identity, the +@command{centos-art} script considers translation symbolic links as +translation files. + +Translation file names, inside brands' translation template +(@samp{Tpl}) directory have special meaning: + +@subsubsection Conventional file names +@cindex Translation brands file names + +Convenctional file names look like @file{blue.sed}, @file{2c-a.sed}, +etc. Replacement commands inside translation file are applied to +design templates and translation file names are used as final image +name. The image dimensions use the same dimensions that design +template has. + +@subsubsection Numeric file names +@cindex Translation brands file names + +Numeric file names look like @file{300.sed}, @file{200.sed}, etc. +Replacements commands inside translation files are applied to design +templates, and translation file names are used as final image name. +The final image is saved using an specific @samp{width} defined by the +number part of the translation file name. The image @samp{height} is +automatically scaled based on the previous @samp{width} definition to +maintain the designing ratio. + +For example, if your design template has 400x200 pixels of dimension, +and you apply a translation file named `300.sed' to it, the final +image you get as result will have 300x100 pixels of dimension. The +same is true if you use higher numbers like `1024.sed', `2048.sed', +etc. In these cases you have bigger images proportionally. + +As we are using scalable vector graphics to design identity templates, +the image size you produce is not limitted in size. You can use one +design template produced in 400x200 pixels to produce larger or +shorter PNG images using numeric translation files as described +above. + +@subsubsection Translation markers + +Inside @file{trunk/Translations/Identity/Brands/}, translation files +combine the following translation markers: + +@table @samp +@item #000000 + +Specify which color to use when rendering brand images. + +@quotation +@strong{Note} As translation files inside +@file{trunk/Translations/Identity/Brands} are symbolic links that +point to template translation files, translation markers are defined +inside template translation files. +@end quotation +@end table + +@subsection Usage +@cindex How to render brands' translation files + +To render brands' translation files, use the following command: + +@verbatim +centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands +@end verbatim + +@subsection See also + +@menu +@comment --- Removed(* trunk Translations Identity Brands Tpl::) --- +* trunk Identity Brands:: +@end menu diff --git a/Manuals/Repository/trunk/Locales/Identity/Brands/Tpl.texi b/Manuals/Repository/trunk/Locales/Identity/Brands/Tpl.texi new file mode 100644 index 0000000..b53171e --- /dev/null +++ b/Manuals/Repository/trunk/Locales/Identity/Brands/Tpl.texi @@ -0,0 +1,10 @@ +@subsection Goals + +@subsection Description + +@subsection Usage + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Locales/Identity/Fonts.texi b/Manuals/Repository/trunk/Locales/Identity/Fonts.texi new file mode 100644 index 0000000..2699334 --- /dev/null +++ b/Manuals/Repository/trunk/Locales/Identity/Fonts.texi @@ -0,0 +1,62 @@ +@subsection Goals + +This section exists to organize fonts translation files. +@subsection Description + +Translation files, inside @file{trunk/Translations/Fonts}, have the +following structure: + +@verbatim +s!font-family:Denmark!font-family:DejaVu LGC Sans! +s!font-weight:normal!font-weight:bold! +s!font-style:normal!font-style:italic! +@end verbatim + +Inside @file{trunk/Translations/Fonts}, there is one translation file +for each font preview image you want to produce. This way, we create +one translation file for each font-family we use somewhere inside +CentOS visual identity. + +@quotation +@strong{Important} Do not create translation files for +font-families not used somewhere inside CentOS visual identity. The +identity of font entry (@pxref{trunk Identity Fonts}) is used as +reference when someone needs to know which font-families are allowed +to use inside CentOS visual identity. +@end quotation + +@subsubsection Translation Markers + +Inside @file{trunk/Translations/Identity/Fonts}, translation files +combine the following translation markers: + +@table @samp +@item font-family:Denmark +Specify which font family to use when rendering font preview images. +@item font-weight:normal +Specify which font weight to use when rendering font preview images. +@item font-style:normal +Specify which font style to use when rendering font preview images. +@end table + +@subsection Usage +@cindex How to render fonts' translation files + +Inside @file{trunk/Translations/Fonts} you use your favorite text +editor to create translation files. Inside +@file{trunk/Translations/Fonts} there is not translation template +directory (@file{Tpl/}), nor translation rendering using +@command{centos-art} script. For example, to create the +@file{dejavu_lgc_sans-boldoblique.sed} translation file using +@command{vim} editor, type the following command: + +@verbatim +vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed +@end verbatim + +@subsection See also + +@menu +* trunk Identity Fonts:: +@end menu + diff --git a/Manuals/Repository/trunk/Locales/Identity/Models.texi b/Manuals/Repository/trunk/Locales/Identity/Models.texi new file mode 100644 index 0000000..b53171e --- /dev/null +++ b/Manuals/Repository/trunk/Locales/Identity/Models.texi @@ -0,0 +1,10 @@ +@subsection Goals + +@subsection Description + +@subsection Usage + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Locales/Identity/Release.texi b/Manuals/Repository/trunk/Locales/Identity/Release.texi new file mode 100644 index 0000000..b53171e --- /dev/null +++ b/Manuals/Repository/trunk/Locales/Identity/Release.texi @@ -0,0 +1,10 @@ +@subsection Goals + +@subsection Description + +@subsection Usage + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Locales/Identity/Themes.texi b/Manuals/Repository/trunk/Locales/Identity/Themes.texi new file mode 100644 index 0000000..b53171e --- /dev/null +++ b/Manuals/Repository/trunk/Locales/Identity/Themes.texi @@ -0,0 +1,10 @@ +@subsection Goals + +@subsection Description + +@subsection Usage + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Locales/Identity/Themes/Backgrounds.texi b/Manuals/Repository/trunk/Locales/Identity/Themes/Backgrounds.texi new file mode 100644 index 0000000..fb39647 --- /dev/null +++ b/Manuals/Repository/trunk/Locales/Identity/Themes/Backgrounds.texi @@ -0,0 +1,22 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Locales/Identity/Themes/Distro/Anaconda/Progress.texi b/Manuals/Repository/trunk/Locales/Identity/Themes/Distro/Anaconda/Progress.texi new file mode 100644 index 0000000..f2d99e2 --- /dev/null +++ b/Manuals/Repository/trunk/Locales/Identity/Themes/Distro/Anaconda/Progress.texi @@ -0,0 +1,94 @@ +@subsection Goals + +@itemize +@item Organize Anaconda progress translation templates. +@item Organize Anaconda progress translation files in several +languages and major releases of CentOS distribution. +@end itemize + +@subsection Description + +Use the following command to produce translation files based: + +@example +trunk/Translations/Identity/Themes/Distro/Anaconda/Progress +`-- Tpl + |-- en + | |-- 01-welcome.sed + | |-- 02-donate.sed + | `-- 03-yum.sed + `-- es + |-- 01-welcome.sed + |-- 02-donate.sed + `-- 03-yum.sed +@end example + +In order to produce the slide images in PNG format we need to have the +translation files first. So we use the following commands to create +translation files for CentOS 3, 4, and 5 major releases: + +@example +centos-art render --translation --filter='3,4,5' +@end example + +The above commands will produce the following translation structure: + +@example +trunk/Translations/Identity/Themes/Distro/Anaconda/Progress +|-- 3 +| |-- en +| | |-- 01-welcome.sed +| | |-- 02-donate.sed +| | `-- 03-yum.sed +| `-- es +| |-- 01-welcome.sed +| |-- 02-donate.sed +| `-- 03-yum.sed +|-- 4 +| |-- en +| | |-- 01-welcome.sed +| | |-- 02-donate.sed +| | `-- 03-yum.sed +| `-- es +| |-- 01-welcome.sed +| |-- 02-donate.sed +| `-- 03-yum.sed +|-- 5 +| |-- en +| | |-- 01-welcome.sed +| | |-- 02-donate.sed +| | `-- 03-yum.sed +| `-- es +| |-- 01-welcome.sed +| |-- 02-donate.sed +| `-- 03-yum.sed +`-- Tpl + |-- en + | |-- 01-welcome.sed + | |-- 02-donate.sed + | `-- 03-yum.sed + `-- es + |-- 01-welcome.sed + |-- 02-donate.sed + `-- 03-yum.sed +@end example + +At this point we have all the translation files we need to produce +Anaconda progress welcome, donate and yum slides images; in English +and Spanish languages; for CentOS 3, CentOS 4, and CentOS 5. That is, +a sum of 18 images around. + +Now, with translation files in place, let's move to +@file{trunk/Identity} structure and render them. + +@itemize +@item @xref{trunk Identity Themes Motifs Modern Distro Anaconda Progress}. +@end itemize + +@subsection Usage + +Translation rendering is described in @samp{trunk/Translations} +documentation entry (--- @strong{Removed}(pxref:trunk Translations) ---). + + +@subsection See also diff --git a/Manuals/Repository/trunk/Locales/Identity/Widgets.texi b/Manuals/Repository/trunk/Locales/Identity/Widgets.texi new file mode 100644 index 0000000..fda4863 --- /dev/null +++ b/Manuals/Repository/trunk/Locales/Identity/Widgets.texi @@ -0,0 +1,23 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@comment --- Removed(* trunk Translations Identity Widgets::) --- +@end menu diff --git a/Manuals/Repository/trunk/Manuals.texi b/Manuals/Repository/trunk/Manuals.texi new file mode 100644 index 0000000..fb39647 --- /dev/null +++ b/Manuals/Repository/trunk/Manuals.texi @@ -0,0 +1,22 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Scripts.texi b/Manuals/Repository/trunk/Scripts.texi new file mode 100644 index 0000000..c9b371f --- /dev/null +++ b/Manuals/Repository/trunk/Scripts.texi @@ -0,0 +1,25 @@ +@subsection Goals + +The @file{trunk/Scripts} directory exists to: + +@itemize +@item Organize the ``trunk'' development line of automation scripts by +programming language. +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Scripts/Bash.texi b/Manuals/Repository/trunk/Scripts/Bash.texi new file mode 100644 index 0000000..0b387e6 --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Bash.texi @@ -0,0 +1,156 @@ +@subsection Goals + +The @file{trunk/Scripts/Bash} directory exists to organize the trunk +development line of @file{centos-art.sh} automation script. The +@file{centos-art.sh} script standardizes frequent tasks inside your +working copy of CentOS Artwork Repository. + +@subsection Description + +The best way to understand @file{centos-art.sh} automation script is +studying its source code. However, as start point, you may prefer to +read an introductory resume before diving into the source code +details. + +The @file{centos-art.sh} script is written in Bash. Most tasks, inside +@file{centos-art.sh} script, have been organized in many specific +functionalities that you can invoke from the @command{centos-art} +command-line interface. + +When you type the @command{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 @var{PATH} environment variable to look for +that command location. If your system was prepared to use CentOS +Artwork Repository correctly (--- @strong{Removed}(pxref:trunk Scripts Bash Functions +Verify) ---), you should have a symbolic link inside @file{~/bin/} +directory that points to the @file{centos-art.sh} script file. As +@file{~/bin/} directory is, by default, inside @var{PATH} environment +variable, the execution of @command{centos-art} command runs the +@file{centos-art.sh} script. + +When @file{centos-art.sh} script is executed, the first it does is +executing the @file{trunk/Scripts/Bash/initEnvironment.sh} script to +initialize global variables (e.g., @command{gettext} variables) and +global function scripts. Global function scripts are located inside +@file{trunk/Scripts/Bash/Functions} directory and their file names +begin with @samp{cli}. Global function scripts provide common +functionalities that can be used anywhere inside @file{centos-art.sh} +script execution environment. + +Once global variables and function scripts have been loaded, +@file{centos-art.sh} script executes the @command{cli} global function +from @file{cli.sh} function script to retrive command-line arguments +and define some default values that may be used later by specific +function scripts (--- @strong{Removed}(pxref:trunk Scripts Bash Functions) ---). + +As convenction, the @file{centos-art.sh} command-line arguments have +the following format: + +@verbatim +centos-art arg1 --arg2=val2 --arg3=val3 +@end verbatim + +In the above example, @samp{centos-art} is the command you use to +invoke @file{centos-art.sh} script. The @samp{arg1} is required and +represents the functionality you want to perform (e.g., +@option{verify}, @option{render}, @option{locale}, @option{manual}, +etc.). The remaining arguments are modifiers to @option{arg1}. The +@option{--arg2} definition is required and represets, specifically, +the action inside the functionality you want to perform. The +@option{--arg3} and on, are optional. + +Once command-line arguments have been retrived, the +@file{centos-art.sh} script loads specific functionalities using the +@file{cli_getFunctions.sh} function script. Only one specific +functionality can be loaded at one script execution I.e., you run +@command{centos-art.sh} script to run just one functionality. + +@float Figure,fig:trunk/Scripts/Bash:Initialization +@verbatim ++----------------------------------------------------------------------+ +| [centos@host]$ centos-art function --action='value' --option='value' | ++----------------------------------------------------------------------+ +| ~/bin/centos-art --> ~/artwork/trunk/Scripts/Bash/centos-art.sh | ++---v-----------------------------------------v------------------------+ + | centos-art.sh | + +---v---------------------------------v---+ + . | initEnvironment.sh | . + . +---------------------------------+ . + . | cli $@ | . + . +---v-------------------------v---+ . + . . | cli_getFunctions | . . + . . +---v-----------------v---+ . . + . . . | function1 | . . . + . . . | function2 | . . . + . . . | function3 | . . . + . . . +-----------------+ . . . + . . ........................... . . + . ................................... . + ........................................... +@end verbatim +@caption{The functionalities initialization environment.} +@end float + +Functionalities are implemented by means of actions. Once the +functionality has been initiazalized, actions initialization take +place for that functionality. Actions initialization model is very +similar to functions initialization model. But with the difference, +that actions are loaded inside function environment, and so, share +variables and functions defined inside function environment. + +@float Figure,fig:trunk/Scripts/Bash/Functions:Initialization +@verbatim ++--------------------------------------+ +| cli_getFunctions | ++---v------------------------------v---+ +. | function1 | . +. +---v----------------------v---+ . +. . | function1_getActions | . . +. . +---v--------------v---+ . . +. . . | action 1 | . . . +. . . | action 2 | . . . +. . . | action n | . . . +. . . +--------------+ . . . +. . ........................ . . +. ................................ . +. +------------------------------+ . +. | function2 | . +. +---v----------------------v---+ . +. . | function2_getActions | . . +. . +---v--------------v---+ . . +. . . | action 1 | . . . +. . . | action 2 | . . . +. . . | action n | . . . +. . . +--------------+ . . . +. . ........................ . . +. ................................ . +. +------------------------------+ . +. | function3 | . +. +---v----------------------v---+ . +. . | function3_getActions | . . +. . +---v--------------v---+ . . +. . . | action 1 | . . . +. . . | action 2 | . . . +. . . | action n | . . . +. . . +--------------+ . . . +. . ........................ . . +. ................................ . +........................................ +@end verbatim +@caption{The actions initialization environment.} +@end float + +@subsection Usage + +The @file{centos-art.sh} script usage information is described inside +each specific function documentation (--- @strong{Removed}(pxref:trunk Scripts Bash +Functions) ---). + +@subsection See also + +@menu +* trunk Scripts:: +@comment --- Removed(* trunk Scripts Bash Functions::) --- +@comment --- Removed(* trunk Scripts Bash Locale::) --- +@end menu diff --git a/Manuals/Repository/trunk/Scripts/Bash/Cli.texi b/Manuals/Repository/trunk/Scripts/Bash/Cli.texi new file mode 100755 index 0000000..e69de29 --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Bash/Cli.texi diff --git a/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions.texi b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions.texi new file mode 100755 index 0000000..2a421ab --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions.texi @@ -0,0 +1,1222 @@ +@subsection Goals + +The @file{trunk/Scripts/Bash/Functions} directory exists to organize +@file{centos-art.sh} specific functionalities. + +@subsection Description + +The specific functions of @file{centos-art.sh} script are designed +with ``Software Toolbox'' philosophy (@pxref{Toolbox +introduction,,,coreutils.info}) in mind: each program ``should do one +thing well''. Inside @file{centos-art.sh} script, each specific +functionality is considered a program that should do one thing well. +Of course, if you find that they still don't do it, feel free to +improve them in order for them to do so. + +The specific functions of @file{centos-art.sh} script are organized +inside specific directories under @file{trunk/Scripts/Bash/Functions} +location. Each specific function directory should be named as the +function it represents, with the first letter in uppercase. For +example, if the function name is @code{render}, the specific function +directory for it would be @samp{trunk/Scripts/Bash/Functions/Render}. + +To better understand how specific functions of @file{centos-art.sh} +script are designed, lets create one function which only goal is to +output different kind of greetings to your screen. + +When we create specific functions for @file{centos-art.sh} script it +is crucial to know what these functions will do exactly and if there +is any function that already does what we intend to do. If there is no +one, it is good time to create them then. Otherwise, if +functionalities already available don't do what you exactly expect, +contact their authors and work together to improve them. + +@quotation +@strong{Tip} Join CentOS developers mailing list +@email{centos-art@@centos.org} to share your ideas. +@end quotation + +It is also worth to know what global functions and variables do we +have available inside @file{centos-art.sh} script, so advantage can be +taken from them. Global variables are defined inside global function +scripts. Global functions scripts are stored immediatly under +@file{trunk/Scripts/Bash/Functions} directory, in files begining with +@samp{cli} prefix. + +OK, let's begin with our functionality example. + +What function name do we use? Well, lets use @code{greet}. Note that +@samp{hello} word is not a verb; but an expression, a kind of +greeting, an interjection specifically. In contrast, @samp{greet} is a +verb and describes what we do when we say @samp{Hello!}, @samp{Hi!}, +and similar expressions. + +So far, we've gathered the following function information: + +@verbatim +Name: greet +Path: trunk/Scripts/Bash/Functions/Greet +File: trunk/Scripts/Bash/Functions/Greet/greet.sh +@end verbatim + +The @file{greet.sh} function script is the first file +@file{centos-art.sh} script loads when the @samp{greet} functionality +is called using commands like @samp{centos-art greet --hello='World'}. +The @file{greet.sh} function script contains the @code{greet} function +definition. + +Inside @file{centos-art.sh} script, as convenction, each function +script has one top commentary, followed by one blank line, and then +one function defintion below it only. + +Inside @file{centos-art.sh} script functions, top commentaries have +the following components: the functionality description, one-line for +copyright note with your personal information, the license under +which the function source code is released ---the @file{centos-art.sh} +script is released as GPL, so do all its functions---, the @code{$Id$} +keyword of Subversion is later expanded by @command{svn propset} +command. + +In our @code{greet} function example, top commentary for +@file{greet.sh} function script would look like the following: + +@verbatim +#!/bin/bash +# +# greet.sh -- This function outputs different kind of greetings to +# your screen. Use this function to understand how centos-art.sh +# script specific functionalities work. +# +# Copyright (C) YEAR YOURFULLNAME +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, but +# WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +# General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 +# USA. +# +# ---------------------------------------------------------------------- +# $Id$ +# ---------------------------------------------------------------------- +@end verbatim + +After top commentary, separated by one blank line, the @code{greet} +function definition would look like the following: + +@verbatim +function greet { + + # Define global variables. + + # Define command-line interface. + greet_getActions + +} +@end verbatim + +The first definition inside @code{greet} function, are global +variables that will be available along @code{greet} function execution +environment. This time we didn't use global variable definitions for +@code{greet} function execution environment, so we left that section +empty. + +Later, we call @code{greet_getActions} function to define the +command-line interface of @code{greet} functionality. The command-line +interface of @code{greet} functionality defines what and how actions +are performed, based on arguments combination passed to +@file{centos-art.sh} script. + +@verbatim +function greet_getActions { + + case "$ACTIONNAM" in + + --hello ) + greet_doHello + ;; + + --bye ) + greet_doBye + ;; + + * ) + cli_printMessage "`gettext "The option provided is not valid."`" + cli_printMessage "$(caller)" 'AsToKnowMoreLine' + + esac + +} +@end verbatim + +The @var{ACTIONNAM} global variable is defined in @file{cli.sh} +function script and contains the value passed before the equal sign +(i.e., @samp{=}) in the second command-line argument of +@file{centos-art.sh} script. For example, if the second command-line +argument is @option{--hello='World'}, the value of @var{ACTIONNAM} +variable would be @samp{--hello}. Using this configuration let us +deside which action to perform based on the action name passed to +@file{centos-art.sh} script as second argument. + +The @code{greet} function definition makes available two valid +greetings through @option{--hello} and @option{--bye} options. If no +one of them is provided as second command-line argument, the @samp{*} +case is evaluated instead. + +The @samp{*} case and its two lines further on should always be +present in @file{_getActions.sh} function scripts, no matter what +specific functionality you are creating. This convenction helps the +user to find out documentation about current functionality in use, +when no valid action is provided. + +The @code{greet_doHello} and @code{greet_doBye} function definitions +are the core of @code{greet} specific functionality. In such function +definitions we set what our @code{greet} function really does: to +output different kinds of greetings. + +@verbatim +function greet_doHello { + + cli_printMessage "`gettext "Hello"` $ACTIONVAL" + +} +@end verbatim + +The @code{greet_doHello} function definition is stored in +@file{greet_doHello.sh} function script. + +@verbatim +function greet_doBye { + + cli_printMessage "`gettext "Goodbye"` $ACTIONVAL" + +} +@end verbatim + +The @code{greet_doBye} function definition is stored in the +@file{greet_doBye.sh} function script. + +Both @file{greet_doHello.sh} and @file{greet_doBye.sh} function +scripts are stored inside @code{greet} function directory path (i.e. +@file{trunk/Scripts/Bash/Functions/Greet}). + +The @var{ACTIONVAL} global variable is defined in @file{cli.sh} +function script and contains the value passed after the equal sign +(i.e., @samp{=}) in the second command-line argument of +@file{centos-art.sh} script. For example, if the second command-line +argument is @option{--hello='World'}, the value of @var{ACTIONVAL} +variable would be @samp{World} without quotes. + +Let's see how @code{greet} specific functionality files are organzied +under @code{greet} function directory. To see file organization we use +the @command{tree} command: + +@verbatim +trunk/Scripts/Bash/Functions/Greet +|-- greet_doBye.sh +|-- greet_doHello.sh +|-- greet_getActions.sh +`-- greet.sh +@end verbatim + +To try the @code{greet} specific functionality we've just created, +pass the function name (i.e., @samp{greet}) as first argument to +@file{centos-art.sh} script, and any of the valid options as second +argument. Some examples are illustrated below: + +@verbatim +[centos@projects ~]$ centos-art greet --hello='World' +Hello World +[centos@projects ~]$ centos-art greet --bye='World' +Goodbye World +[centos@projects ~]$ +@end verbatim + +The word @samp{World} in the examples above can be anything. In fact, +change it to have a little fun. + +Now that we have a specific function that works as we expect, it is +time to document it. To document @code{greet} specific functionality, +we use its directory path and the @code{manual} functionality +(--- @strong{Removed}(pxref:trunk Scripts Bash Functions Manual) ---) of @file{centos-art.sh} +script, just as the following command illustrates: + +@verbatim +centos-art manual --edit=trunk/Scripts/Bash/Functions/Greet +@end verbatim + +To have a well documented function helps user to understand how your +function really works, and how it should be used. When no valid +action is passed to a function, the @file{centos-art.sh} script uses +the function documentation entry as vehicle to communicate which the +valid functions are. When no documentation entry exists for a +function, the @file{centos-art.sh} script informs that no +documentation entry exists for such function and requests user to +create it right at that time. + +Now that we have documented our function, it is time to translate its +output messages to different languages. To translate specific +functionality output messages to different languages we use the +@code{locale} functionality (--- @strong{Removed}(pxref:trunk Scripts Bash Functions +Locale) ---) of @file{centos-art.sh} script, just as the following command +illustrates: + +@verbatim +centos-art locale --edit +@end verbatim + +@quotation +@strong{Warning} To translate output messages in different languages, +your system locale information ---as in @env{LANG} environment +variable--- must be set to that locale you want to produce translated +messages for. For example, if you want to produce translated messages +for Spanish language, your system locale information must be set to +@samp{es_ES.UTF-8}, or similar, first. +@end quotation + +Well, it seems that our example is rather complete by now. + +In @code{greet} function example we've described so far, we only use +@command{cli_printMessage} global function in action specific function +definitions in order to print messages, but more interesting things +can be achieved inside action specific function definitions. For +example, if you pass a directory path as action value in second +argument, you could retrive a list of files from therein, and process +them. If the list of files turns too long or you just want to control +which files to process, you could add the third argument in the form +@option{--filter='regex'} and reduce the amount of files to process +using a regular expression pattern. + +The @code{greet} function described in this section may serve you as +an introduction to understand how specific functionalities work inside +@file{centos-art.sh} script. With some of luck this introduction will +also serve you as motivation to create your own @file{centos-art.sh} +script specific functionalities. + +By the way, the @code{greet} functionality doesn't exist inside +@file{centos-art.sh} script yet. Would you like to create it? + +@subsection Usage + +@subsubsection Global variables + +The following global variables of @file{centos-art.sh} script, are +available for you to use inside specific functions: + +@defvar TEXTDOMAIN +Default domain used to retrieve translated messages. This value is set +in @file{initFunctions.sh} and shouldn't be changed. +@end defvar + +@defvar TEXTDOMAINDIR +Default directory used to retrieve translated messages. This value is +set in @file{initFunctions.sh} and shouldn't be changed. +@end defvar + +@defvar FUNCNAM +Define function name. + +Function names associate sets of actions. There is one set of actions +for each unique function name inside @file{centos-art.sh} script. + +Dunction names are passed as first argument in @file{centos-art.sh} +command-line interface. For example, in the command @samp{centos-art +render --entry=path/to/dir --filter=regex}, the @var{ACTION} passed to +@file{centos-art.sh} script is @option{render}. + +When first argument is not provided, the @file{centos-art.sh} script +immediatly ends its execution. +@end defvar + +@defvar FUNCDIR +@end defvar + +@defvar FUNCDIRNAME +@end defvar + +@defvar FUNCSCRIPT +@end defvar + +@defvar FUNCCONFIG +@end defvar + +@defvar ACTIONNAM +Define action name. + +Each action name identifies an specific action to perform, inside an +specific function. + +Action name names aare passed as second argument in +@file{centos-art.sh} command-line interface. For example, in the +command @samp{centos-art render --entry=path/to/dir --filter=regex}, +the @var{ACTIONNAM} passed to @file{centos-art.sh} script is +@option{--entry}. + +When second argument is not provided, the @file{centos-art.sh} script +immediatly ends its execution. +@end defvar + +@defvar ACTIONVAL +Define action value. + +Action values are associated to just one action name. Action values +contain the working copy entry over which its associated action will be +performed in. Working copy entries can be files or directories inside +the working copy. +@end defvar + +@defvar REGEX +Define regular expression used as pattern to build the list of files +to process. + +By default, @var{REGEX} variable is set to @code{.+} to match all +files. + +Functions that need to build a list of files to process use the option +@option{--filter} to redefine @var{REGEX} variable default value, and +so, control the amount of files to process. +@end defvar + +@defvar ARGUMENTS +Define optional arguments. + +Optional arguments, inside @file{centos-art.sh} script, are considered +as all command-line arguments passed to @file{centos-art.sh} script, +from third argument position on. For example, in the command +@samp{centos-art render --entry=path/to/dir --filter=regex} , the +optional arguments are from @samp{--filter=regex} argument on. + +Optional arguments are parsed using @command{getopt} command through +the following base construction: + +@verbatim +# Define short options we want to support. +local ARGSS="" + +# Define long options we want to support. +local ARGSL="filter:,to:" + +# Parse arguments using getopt(1) command parser. +cli_doParseArguments + +# Reset positional parameters using output from (getopt) argument +# parser. +eval set -- "$ARGUMENTS" + +# Define action to take for each option passed. +while true; do + case "$1" in + --filter ) + REGEX="$2" + shift 2 + ;; + --to ) + TARGET="$2" + shift 2 + ;; + * ) + break + esac +done +@end verbatim + +Optional arguments provide support to command options inside +@file{centos-art.sh} script. For instance, consider the Subversion +(@command{svn}) command, where there are many options (e.g., +@option{copy}, @option{delete}, @option{move}, etc), and inside each +option there are several modifiers (e.g., @samp{--revision}, +@samp{--message}, @samp{--username}, etc.) that can be combined one +another in their short or long variants. + +The @var{ARGUMENTS} variable is used to store arguments passed from +command-line for later use inside @file{centos-art.sh} script. Storing +arguments is specially useful when we want to run a command with some +specific options from them. Consider the following command: + +@verbatim +centos-art path --copy=SOURCE --to=TARGET --message="The commit message goes here." --username='johndoe' +@end verbatim + +In the above command, the @option{--message}, and @option{--username} +options are specific to @command{svn copy} command. In such cases, +options are not interpreted by @file{centos-art.sh} script itself. +Instead, the @file{centos-art.sh} script uses @command{getopt} to +retrive them and store them in the @var{ARGUMENTS} variable for later +use, as described in the following command: + +@verbatim +# Build subversion command to duplicate locations inside the +# workstation. +eval svn copy $SOURCE $TARGET --quiet $ARGUMENTS +@end verbatim + +When @command{getopt} parses @var{ARGUMENTS}, we may use short options +(e.g., @option{-m}) or long options (e.g., @option{--message}). When +we use short options, arguments are separated by one space from the +option (e.g., @option{-m 'This is a commit message.'}). When we use +long options arguments are separated by an equal sign (@samp{=}) +(e.g., @option{--message='This is a commit message'}). + +In order for @command{getopt} to parse @var{ARGUMENTS} correctly, it +is required to provide the short and long definition of options that +will be passed or at least supported by the command performing the +final action the function script exists for. + +As convenction, inside @file{centos-art.sh} script, short option +definitions are set in the @var{ARGSS} variable; and long option +definitions are set in the @var{ARGSL} variable. + +When you define short and long options, it may be needed to define +which of these option arguments are required and which not. To define +an option argument as required, you need to set one colon @samp{:} +after the option definition (e.g., @option{-o m: -l message:}). On +the other hand, to define an option argument as not required, you need +to set two colons @samp{::} after the option definition (e.g., +@option{-o m:: -l message::}). +@end defvar + +@defvar EDITOR +Default text editor. + +The @file{centos-art.sh} script uses default text @env{EDITOR} to edit +pre-commit subversion messages, translation files, configuration +files, script files, and similar text-based files. + +If @env{EDITOR} environment variable is not set, @file{centos-art.sh} +script uses @file{/usr/bin/vim} as default text editor. Otherwise, the +following values are recognized by @file{centos-art.sh} script: + +@itemize +@item @file{/usr/bin/vim} +@item @file{/usr/bin/emacs} +@item @file{/usr/bin/nano} +@end itemize + +If no one of these values is set in @env{EDITOR} environment variable, +@file{centos-art.sh} uses @file{/usr/bin/vim} text editor by default. +@end defvar + +@subsubsection Global functions + +Function scripts stored directly under +@file{trunk/Scripts/Bash/Functions/} directory are used to define +global functions. Global functions can be used inside action specific +functionalities and or even be reused inside themselves. This section +provides introductory information to global functions you can use +inside @file{centos-art.sh} script. + +@defun cli_checkActionArguments +Validate action value (@var{ACTIONVAL}) variable. + +The action value variable can take one of the following values: + +@enumerate +@item Path to one directory inside the local working copy, +@item Path to one file inside the local working copy, +@end enumerate + +If another value different from that specified above is passed to +action value variable, the @file{centos-art.sh} script prints an error +message and ends script execution. +@end defun + +@defun cli_checkFiles FILE [TYPE] +Verify file existence. + +@code{cli_checkFiles} receives a @var{FILE} absolute path and performs +file verification as specified in @var{TYPE}. When @var{TYPE} is not +specified, @code{cli_checkFiles} verifies @var{FILE} existence, no +matter what kind of file it be. If @var{TYPE} is specified, use one +of the following values: + +@table @option +@item d +@itemx directory +Ends script execution if @var{FILE} is not a directory. + +When you verify directories with cli_checkFiles, if directory doesn't +exist, @file{centos-art.sh} script asks you for confirmation in order +to create that directory. If you answer positively, +@file{centos-art.sh} script creates that directory and continues +script flows normally. Otherwise, if you answer negatively, +@file{centos-art.sh} ends script execution with an error and +documentation message. + +@item f +@item regular-file +Ends script execution if @var{FILE} is not a regular file. +@item h +@itemx symbolic-link +Ends script execution if @var{FILE} is not a symbolic link. +@item x +@itemx execution +Ends script execution if @var{FILE} is not executable. +@item fh +Ends script execution if @var{FILE} is neither a regular file nor a +symbolic link. +@item fd +Ends script execution if @var{FILE} is neither a regular file nor a +directory. +@item isInWorkingCopy +Ends script execution if @var{FILE} is not inside the working copy. +@end table + +As default behaviour, if @var{FILE} passes all verifications, +@file{centos-art.sh} script continues with its normal flow. +@end defun + +@defun cli_commitRepoChanges [LOCATION] + +Syncronize changes between repository and working copy. + +The @code{cli_commitRepoChanges} function brings changes from the +central repository down to the working copy---using @command{svn +update}---, checks the working copy changes---using @command{svn +status} command---, prints status report---using both @command{svn +update} and @command{svn status} commands output, and finally, commits +recent changes from the working copy up to the repository---using +@command{svn commit} command---. + +Previous to commit the working copy changes up to the central +repository, the @code{cli_commitRepoChanges} function asks you to +verify changes---using @command{svn diff} command---, and later, +another confirmation question is shown to be sure you really want to +commit changes up to central repository. + +If @var{LOCATION} argument is not specified, the value of +@var{ACTIONVAL} variable is used as reference instead. + +@float Figure, trunk/Scripts/Bash/Functions/cli_commitRepoChanges +@verbatim +---------------------------------------------------------------------- +--> Bringing changes from the repository into the working copy +--> Checking changes in the working copy +---------------------------------------------------------------------- +Added 0 file from the repository. +Deleted 0 file from the repository. +Updated 0 file from the repository. +Conflicted 0 file from the repository. +Merged 0 file from the repository. +Modified 4 files from the working copy. +Unversioned 0 file from the working copy. +Deleted 0 file from the working copy. +Added 0 file from the working copy. +---------------------------------------------------------------------- +@end verbatim +@caption{The @code{cli_commitRepoChanges} function output.} +@end float + +Call the @code{cli_commitRepoChanges} function before or/and after +calling functions that modify files or directories inside the working +copy as you may need to. +@end defun + +@defun cli_doParseArguments +Redefine arguments (@var{ARGUMENTS}) global variable using +@command{getopt} command output. For more information about how to use +@code{cli_doParseArguments} function, see @var{ARGUMENTS} variable +description above. +@end defun + +@defun cli_doParseArgumentsReDef $@@ +Initialize/reset arguments (@var{ARGUMENTS}) global variable using +positional parameters variable (@var{$@@}) as reference. + +When we work inside function definitions, positional parameters are +reset to the last function definition positional parameters. If you +need to redefine positional parameters from one specific function, you +need to call @code{cli_doParseArgumentsReDef} with the positional +parameters variable (@var{$@@}), set as first argument, to that +specific function you want to redefine positional parameters at. +@end defun + +@defun cli_getArguments + +Initialize function name (@var{FUNCNAM}), action name +(@var{ACTIONNAM}), and action value (@var{ACTIONVAL}) global +variables, using positional parameters passed in @var{$@@} variable. + +The @code{cli_getArguments} function is called from @code{cli.sh} +function script, using @code{cli} function positional parameters +(i.e., the positional parameters passed as arguments in the +command-line) as first function argument. + +Once command-line positional parameters are accesible to +@file{centos-art.sh} script execution evironment, +@code{cli_getArguments} uses regular expression to retrive +action variables from first and second argument. The first argument +defines the value used as function name (@var{FUNCNAM}), and the +second argument defines both values used as action name +(@var{ACTIONNAM}) and action value (@var{ACTIONVAL}), respectively. + +The first argument is a word in lower case. This word specifies the +name of the functionality you want to use (e.g., @samp{render} to +render images, @samp{manual} to work on documentation, and so on.) + +The second argument has a long option style (e.g., +@samp{--option=value}). The @samp{--option} represents the action name +(@var{ACTIONNAM}), and the characters inbetween the equal sign +(@samp{=}) and the first space character, are considered as the action +value (@var{ACTIONVAL}). In order to provide action values with space +characters inbetween you need to enclose action value with quotes like +in @samp{--option='This is long value with spaces inbetween'}. +Generally, action values are used to specify paths over which the +action name acts on. + +Once action related variables (i.e., @var{FUNCNAM}, @var{ACTIONNAM}, +and @var{ACTIONVAL}) are defined and validated, +@code{cli_getArguments} shifts the positional arguments to remove the +first two arguments passed (i.e., those used to retrive action related +variables) and redefine the arguments (@var{ARGUMENTS}) global +variable with the new positional parameters information. +@end defun + +@defun cli_getFunctions +Initialize funtionalities supported by @file{centos-art.sh} script. + +Functionalities supported by @file{centos-art.sh} script are organized +in functionality directories under +@file{trunk/Scripts/Bash/Functions/} directory. Each functionality +directory stores function scripts to the functionality such directory +was created for. Function scripts contain function definitions. +Function definitions contain several commands focused on achieving one +specific task only (i.e., the one such functionality was created for). + +In order for @file{centos-art.sh} script to recognize a functionality, +such functionality needs to be stored under +@file{trunk/Scripts/Bash/Functions/} in a directory written +capitalized (i.e., the whole name is written in lowercase except the +first character which is in uppercase). The directory where one +specific functionality is stored is known as the @samp{functionality +directory}. + +Inside each functionality directory, the functionalty itself is +implemented through function scripts. Function scripts are organized +in files independently one another and written in @samp{camelCase} +format with the function name as prefix. Separation between prefix +and description is done using underscore (@samp{_}) character. + +In order for @file{centos-art.sh} script to load functionalities +correctly, function definition inside function scripts should be set +using the @samp{function} reserved word, just as in the following +example: + +@verbatim +function prefix_doSomething { + + # Do something here... + +} +@end verbatim + +The above function definition is just a convenction we use, in order +to make identification of function names easier read and automate by +@file{centos-art.sh} script initialization commands, once +@file{centos-art.sh} script determines which functionality directory +to use. Specifically, in order to initialize and export functions, +@file{centos-art.sh} script executes all function scripts inside the +functionality directory, and later @command{grep} on them using a +regular expression pattern, where the @samp{function} reserved word is +used as reference to retrive the function names and export them to +@file{centos-art.sh} script execution environment, and so, make +function definitions ---from function scripts inside the functionality +directory--- available for further calls. + +If the functionality specified in the command-line first argument +doesn't have a functionality directory, @file{centos-art.sh} script +considers the functionality provided in the command-line as invalid +functionality and immediatly stops script execution with an error +message. + +In order to keep visual consistency among function scripts, please +consider using the following function script design model as template +for your own function scripts: + +@verbatim +#!/bin/bash +# +# prefix_doSomething.sh -- This function illustrates function scripts +# design model you can use to create your own function scripts inside +# centos-art.sh script. +# +# Copyright (C) YEAR YOURFULLNAME +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, but +# WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +# General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 +# USA. +# +# ---------------------------------------------------------------------- +# $Id$ +# ---------------------------------------------------------------------- + +function prefix_doSomething { + + # Do something here... + +} +@end verbatim +@end defun + +@defun cli_getCountryCodes [FILTER] +Output country codes supported by @file{centos-art.sh} script. + +The @code{cli_getCountryCodes} function outputs a list with country +codes as defined in ISO3166 standard. When @var{FILTER} is provided, +@code{cli_getCountryCodes} outputs country codes that match +@var{FILTER} regular expression pattern. +@end defun + +@defun cli_getCountryName [FILTER] +Outputs country name supported by @file{centos-art.sh} script. + +The @code{cli_getCountryName} function reads one language locale code +in the format LL_CC and outputs the name of its related country as in +ISO3166. If filter is specified, @code{cli_getCountryName} returns the +country name that matches the locale code specified in @var{FILTER}, +exactly. +@end defun + +@defun cli_getCurrentLocale +Output current locale used by @file{centos-art.sh} script. + +The @code{cli_getCurrentLocale} function uses @env{LANG} environment +variable to build a locale pattern that is later applied to +@code{cli_getLocales} function output in order to return the current +locale that @file{centos-art.sh} script works with. + +The current locale information, returned by +@code{cli_getCurrentLocale}, is output from more specific to less +specific. For example, if @samp{en_GB} locale exists in +@code{cli_getLocales} function output, the @samp{en_GB} locale would +take precedence before @samp{en} locale. + +Locale precedence selection is quite important in order to define the +locale type we use for message translations. For example, if +@samp{en_GB} is used, we are also saying that the common language +specification for English language (i.e., @samp{en}) is no longer +used. Instead, we are using English non-common country-specific +language specifications like @samp{en_AU}, @samp{en_BW}, @samp{en_GB}, +@samp{en_US}, etc., for message translations. + +Use @code{cli_getCurrentLocale} function to know what current locale +information to use inside @file{centos-art.sh} script. +@end defun + +@defun cli_getFilesList [LOCATION] +Output list of files to process. + +The @code{cli_getFilesList} function uses @var{LOCATION} variable as +source location to build a list of files just as specified by regular +expression (@var{REGEX}) global variable. Essentially, what the +@code{cli_getFilesList} function does is using @command{find} command +to look for files in the location (@var{LOCATION}) just as posix-egrep +regular expression (@var{REGEX}) specifies. + +If @var{LOCATION} is not specified when @code{cli_getFilesList} +function is called, the action value (@var{ACTIONVAL}) global variable +is used as location value instead. + +By default, if the regular expression (@var{REGEX}) global variable is +not redefined after its first definition in the @code{cli} function, +all files that match default regular expression value (i.e., +@samp{.+}) will be added to the list of files to process. Otherwise, +if you redefine the regular expression global variable after its first +definition in the @code{cli} function and before calling +@code{cli_getFilesList} function, the last value you specifed is used +instead. + +When you need to customize the regular expression (@var{REGEX}) global +variable value inside a function, do not redefine the global variable +(at least you be absolutly convinced you need to). Instead, set the +regular expression global variable as @samp{local} to the function you +need a customized regular expression value for. If we don't redefine +the regular expression global variable as local to the function, or +use another name for the regular expression variable (which is not +very convenient in order to keep the amount of names to remember low), +you may experiment undesired concantenation issues that make your +regular expression to be something different from that you expect them +to be, specially if the function where you are doing the variable +redefinition is called several times during the same script execution. + +As result, the @code{cli_getFilesList} re-defines the value of +@var{FILES} variable with the list of files the @command{find} command +returned. As example, consider the following construction: + +@verbatim +function prefix_doSomething { + + # Initialize the list of files to process. + local FILES='' + + # Initialize location. + local LOCATION=/home/centos/artwork/trunk/Identity/Themes/Models/Default + + # Re-define regular expression to match scalable vector graphic + # files only. Note how we use the global value of REGEX to build a + # new local REGEX value here. + local REGEX="${REGEX}.*\.(svgz|svg)" + + # Redefine list of files to process. + cli_getFilesList $LOCATION + + # Process list of files. + for FILE in $FILES;do + cli_printMessages "$FILE" 'AsResponseLine' + # Do something else here on... + done + +} +@end verbatim + +@end defun + +@defun cli_getLangCodes [FILTER] +Outputs language codes supported by @file{centos-art.sh} script. + +@code{cli_getLangCodes} function outputs a list of language codes as +defined in ISO639 standard. When @var{FILTER} is provided, +@code{cli_getLangCodes} outputs language codes that match @var{FILTER} +regular expression pattern. +@end defun + +@defun cli_getLangName [FILTER] +Outputs language names supported by @file{centos-art.sh} script. + +@code{cli_getLangName} function reads one language locale code in the +format LL_CC and outputs the language related name as in ISO639. If +filter is specified, @code{cli_getLangName} returns the language name +that matches the locale code specified in @var{FILTER}, exactly. +@end defun + +@defun cli_getLocales +Output locale codes supported by @file{centos-art.sh} script. + +Occasionally, you use @code{cli_getLocales} function to add locale +information in non-common country-specific language (@samp{LL_CC}) +format for those languages (e.g., @samp{bn_IN}, @samp{pt_BR}, etc.) +which locale differences cannot be solved using common language +specifications (@samp{LL}) into one unique common locale specification +(e.g., @samp{bn}, @samp{pt}, etc.). +@end defun + +@defun cli_getRepoName NAME TYPE +Sanitate file names. + +Inside @file{centos-art.sh} script, specific functionalities rely both +in @code{cli_getRepoName} and repository file system organization to +achieve their goals. Consider @code{cli_getRepoName} function as +central place to manage file name convenctions for other functions +inside @file{centos-art.sh} script. + +@quotation +@strong{Important} @code{cli_getRepoName} function doesn't verify file +or directory existence, for that purpose use @code{cli_checkFiles} +function instead. +@end quotation + +The @var{NAME} variable contains the file name or directory name you +want to sanitate. + +The @var{TYPE} variable specifies what type of sanitation you want to +perform on @var{NAME}. The @var{TYPE} can be one of the following +values: + +@table @option +@item d +@itemx directory +Sanitate directory @var{NAME}s. +@item f +@item regular-file +Sanitate regular file @var{NAME}s. +@end table + +Use @code{cli_getRepoName} function to sanitate file names and +directory names before their utilization. + +Use @code{cli_getRepoName} when you need to change file name +convenctions inside @file{centos-art.sh} script. + +When we change file name convenctions inside @code{cli_getRepoName} +what we are really changing is the way functions interpret repository +file system organization. Notice that when we change a file name +(e.g., a function name), it is necessary to update all files where +such file name is placed on. This may require a massive substitution +inside the repository, each time we change name convenctions in the +repository (--- @strong{Removed}(pxref:trunk Scripts Bash Functions Path) ---, for more +information). +@end defun + +@defun cli_getRepoStatus [LOCATION] +Request repository status. + +This function requests the status of a @var{LOCATION} inside the +working copy using the @command{svn status} command and returns the +first character in the output line, just as described in @command{svn +help status}. If @var{LOCATION} is not a regular file or a directory, +inside the working copy, the @file{centos-art.sh} script prints a +message and ends its execution. + +Use this function to perform verifications based a repository +@var{LOCATION} status. +@end defun + +@defun cli_getTemporalFile @var{NAME} +Output absolute path to temporal file @var{NAME}. + +The @code{cli_getTemporalFile} function uses @file{/tmp} directory as +source location to store temporal files, the @file{centos-art.sh} +script name, and a random identification string to let you run more +than one @file{centos-art.sh} script simultaneously on the same user +session. For example, due the following temporal file defintion: + +@verbatim +cli_getTemporalFile $FILE +@end verbatim + +If @var{FILE} name is @file{instance.svg} and the unique random string +is @samp{f16f7b51-ac12-4b7f-9e66-72df847f12de}, the final temporal +file, built from previous temporal file definition, would be: + +@verbatim +/tmp/centos-art.sh-f16f7b51-ac12-4b7f-9e66-72df847f12de-instance.svg +@end verbatim + +When you use the @code{cli_getTemporalFile} function to create +temporal files, be sure to remove temporal files created once you've +ended up with them. For example, consider the following construction: + +@verbatim +for FILE in $FILES;do + + # Initialize temporal instance of file. + INSTANCE=$(cli_getTemporalFile $FILE) + + # Do something ... + + # Remove temporal instance of file. + if [[ -f $INSTANCE ]];then + rm $INSTANCE + fi + +done +@end verbatim + +Use the @code{cli_getTemporalFile} function whenever you need to +create temporal files inside @file{centos-art.sh} script. +@end defun + +@defun cli_getThemeName +Output theme name. + +In order for @code{cli_getThemeName} function to extract theme name +correctly, the @var{ACTIONVAL} variable must contain a directory path +under @file{trunk/Identity/Themes/Motifs/} directory structure. +Otherwise, @code{cli_getThemeName} returns an empty string. +@end defun + +@defun cli_printMessage MESSAGE [FORMAT] +Define standard output message definition supported by +@file{centos-art.sh} script. + +When @var{FORMAT} is not specified, @code{cli_printMessage} outputs +information just as it was passed in @var{MESSAGE} variable. +Otherwise, @var{FORMAT} can take one of the following values: + +@table @option +@item AsHeadingLine +To print heading messages. +@verbatim +---------------------------------------------------------------------- +$MESSAGE +---------------------------------------------------------------------- +@end verbatim + +@item AsWarningLine +To print warning messages. +@verbatim +---------------------------------------------------------------------- +WARNING: $MESSAGE +---------------------------------------------------------------------- +@end verbatim + +@item AsNoteLine +To print note messages. +@verbatim +---------------------------------------------------------------------- +NOTE: $MESSAGE +---------------------------------------------------------------------- +@end verbatim + +@item AsUpdatingLine +To print @samp{Updating} messages on two-columns format. +@verbatim +Updating $MESSAGE +@end verbatim + +@item AsRemovingLine +To print @samp{Removing} messages on two-columns format. +@verbatim +Removing $MESSAGE +@end verbatim + +@item AsCheckingLine +To print @samp{Checking} messages on two-columns format. +@verbatim +Checking $MESSAGE +@end verbatim + +@item AsCreatingLine +To print @samp{Creating} messages on two-columns format. +@verbatim +Creating $MESSAGE +@end verbatim + +@item AsSavedAsLine +To print @samp{Saved as} messages on two-columns format. +@verbatim +Saved as $MESSAGE +@end verbatim + +@item AsLinkToLine +To print @samp{Linked to} messages on two-columns format. +@verbatim +Linked to $MESSAGE +@end verbatim + +@item AsMovedToLine +To print @samp{Moved to} messages on two-columns format. +@verbatim +Moved to $MESSAGE +@end verbatim + +@item AsTranslationLine +To print @samp{Translation} messages on two-columns format. +@verbatim +Translation $MESSAGE +@end verbatim + +@item AsConfigurationLine +To print @samp{Configuration} messages on two-columns format. +@verbatim +Configuration $MESSAGE +@end verbatim + +@item AsResponseLine +To print response messages on one-column format. +@verbatim +--> $MESSAGE +@end verbatim + +@item AsRequestLine +To print request messages on one-column format. Request messages +output messages with one colon (@samp{:}) and without trailing newline +(@samp{\n}) at message end. +@verbatim +$MESSAGE: +@end verbatim + +@item AsYesOrNoRequestLine +To print @samp{yes or no} request messages on one-column format. If +something different from @samp{y} is answered (when using +@code{en_US.UTF-8} locale), script execution ends immediatly. + +@verbatim +$MESSAGE [y/N]: +@end verbatim + +When we use @file{centos-art.sh} script in a locale different from +@code{en_US.UTF-8}, confirmation answer may be different from +@samp{y}. For example, if you use @code{es_ES.UTF-8} locale, the +confirmation question would look like: + +@verbatim +$MESSAGE [s/N]: +@end verbatim + +and the confirmation answer would be @samp{s}, as it is on Spanish +@samp{sí} word. + +Definition of which confirmation word to use is set on translation +messages for your specific locale information. --- @strong{Removed}(xref:trunk Scripts +Bash Functions Locale) ---, for more information about locale-specific +translation messages. + +@item AsToKnowMoreLine +To standardize @samp{to know more, run the following command:} +messages. When the @option{AsToKnowMoreLine} option is used, the +@var{MESSAGE} value should be set to @code{"$(caller)"}. @code{caller} +is a Bash builtin that returns the context of the current subroutine +call. @option{AsToKnowMoreLine} option uses @code{caller} builtin +output to build documentation entries dynamically. + +@verbatim +---------------------------------------------------------------------- +To know more, run the following command: +centos-art manual --read='path/to/dir' +---------------------------------------------------------------------- +@end verbatim + +Use @option{AsToKnowMoreLine} option after errors and for intentional +script termination. + +@item AsRegularLine +To standardize regular messages on one-column format. + +When @var{MESSAGE} contains a colon inside (e.g., @samp{description: +message}), the @code{cli_printMessage} function outputs @var{MESSAGE} +on two-columns format. +@end table + +Use @code{cli_printMessage} function whenever you need to output +information from @file{centos-art.sh} script. + +@quotation +@strong{Tip} To improve two-columns format, change the following file: +@verbatim +trunk/Scripts/Bash/Styles/output_forTwoColumns.awk +@end verbatim +@end quotation +@end defun + +@subsubsection Specific functions + +The following specific functions of @file{centos-art.sh} script, are +available for you to use: + +@menu +@comment --- Removed(* trunk Scripts Bash Functions Html::) --- +@comment --- Removed(* trunk Scripts Bash Functions Locale::) --- +@comment --- Removed(* trunk Scripts Bash Functions Manual::) --- +@comment --- Removed(* trunk Scripts Bash Functions Path::) --- +@comment --- Removed(* trunk Scripts Bash Functions Render::) --- +@comment --- Removed(* trunk Scripts Bash Functions Render Config::) --- +@comment --- Removed(* trunk Scripts Bash Functions Shell::) --- +@comment --- Removed(* trunk Scripts Bash Functions Svg::) --- +@comment --- Removed(* trunk Scripts Bash Functions Verify::) --- +@end menu + +@subsection See also + +@menu +* trunk Scripts Bash:: +@comment --- Removed(* trunk Scripts Bash Locale::) --- +@end menu diff --git a/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Help.texi b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Help.texi new file mode 100644 index 0000000..fb39647 --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Help.texi @@ -0,0 +1,22 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Html.texi b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Html.texi new file mode 100644 index 0000000..fb39647 --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Html.texi @@ -0,0 +1,22 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Locale.texi b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Locale.texi new file mode 100644 index 0000000..bf264c9 --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Locale.texi @@ -0,0 +1,85 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +This command looks for @samp{.sh} files inside Bash directory and +extracts translatable strings from files, using @command{xgettext} +command, in order to create a portable object template +(@file{centos-art.sh.pot}) file for them. + +With the @file{centos-art.sh.pot} file up to date, the +@command{centos-art} command removes the temporal list of files sotred +inside @file{/tmp} directory and checks the current language of your +user's session to create a portable object file for it, in the +location @file{$CLI_LANG/$CLI_LANG.po}. + +The @var{CLI_LANG} variable discribes the locale language used to +output messages inside @command{centos-art} command. The locale +language used inside @command{centos-art} command is taken from the +@env{LANG} environment variable. The @var{CLI_LANG} variable has the +@samp{LL_CC} format, where @samp{LL} is a language code from the +ISO-639 standard, and @samp{CC} a country code from the ISO-3166 +standard. + +The @env{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 @env{LANG} +environment variable to the correct value. On the other side, if you +are using a text session edit your @file{~/.bash_profile} file to set +and export the @env{LANG} environment variable to your native locale +as defines the @command{locale -a} command output; do logout, and do +login again. + +At this point, the @env{LANG} environment variable has the appropriate +value you need, in order to translate @command{centos-art.sh} messages +to your native language (the one set in @env{LANG} environment +variable). + +With the @file{$CLI_LANG/$CLI_LANG.po} file up to date, the +@command{centos-art} opens it for you to update translation strings. +The @command{centos-art} command uses the value of @var{EDITOR} +environment variable to determine your favorite text editor. If no +value is defined on @var{EDITOR}, the @file{/usr/bin/vim} text editor +is used as default. + +When you finishd PO file edition and quit text editor, the +@command{centos-art} command creates the related machine object in the +location @file{$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 @command{centos-art.sh} script. + +In order to make the @command{centos-art.sh} internationalization, the +@command{centos-art.sh} script was modified as described in the +@command{gettext} info documentation (@command{info gettext}). You +can find such modifications in the following files: + +@itemize +@item @file{trunk/Scripts/Bash/initFunctions.sh} +@item @file{trunk/Scripts/Bash/Functions/Help/cli_localeMessages.sh} +@item @file{trunk/Scripts/Bash/Functions/Help/cli_localeMessagesStatus.sh} +@end itemize + +@itemize +@item ... +@end itemize + +@subsection Usage + +@table @samp +@item centos-art locale --edit +Use this command to translate command-line interface output messages +in the current system locale you are using (as specified in @env{LANG} +environment variable). +@item centos-art locale --list +Use this command to see the command-line interface locale report. +@end table + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Manual.texi b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Manual.texi new file mode 100644 index 0000000..fb39647 --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Manual.texi @@ -0,0 +1,22 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Path.texi b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Path.texi new file mode 100644 index 0000000..a7c6c55 --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Path.texi @@ -0,0 +1,327 @@ +@subsection Goals + +This section exists to organize files related to @code{path} +functiontionality. The @code{path} functionality standardizes +movement, syncronization, branching, tagging, and general file +maintainance inside the repository. + +@subsection Description + +@emph{''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.''} + +@subsubsection Repository layout + +The repository layout describes organization of files and directories +inside the repository. The repository layout provides the standard +backend required for automation scripts to work correctly. If such +layout changes unexpectedly, automation scripts may confuse themselves +and stop doing what we expect from them to do. + +As convenction, inside CentOS Artwork Repository, we organize files +and directories related to CentOS corporate visual identity under +three top level directories named: @file{trunk/}, @file{branches/}, +and @file{tags/}. + +The @file{trunk/} directory (@pxref{trunk}) organizes the main +development line of CentOS corporate visual identity. Inside +@file{trunk/} directory structure, the CentOS corporate visual +identity concepts are implemented using directories. There is one +directory level for each relevant concept inside the repository. The +@file{trunk/} directory structure is mainly used to perform +development tasks related to CentOS corporate visual identity. + +The @file{branches/} directory (@pxref{branches}) oranizes parallel +development lines to @file{trunk/} directory. The @file{branches/} +directory is used to set points in time where develpment lines are +devided one from another taking separte and idependent lives that +share a common past from the point they were devided on. The +@file{branches/} directory is mainly used to perform quality assurance +tasks related to CentOS corporate visual identity. + +The @file{tags/} directory (@pxref{tags}) organizes parallel frozen +lines to @file{branches/} directory. The parallel frozen lines are +immutable, nothing change inside them once they has been created. The +@file{tags/} directory is mainly used to publish final releases of +CentOS corporate visual identity. + +The CentOS Artwork Repository layout is firmly grounded on a +Subversion base. Subversion (@url{http://subversion.tigris.org}) is a +version control system, which allows you to keep old versions of files +and directories (usually source code), keep a log of who, when, and +why changes occurred, etc., like CVS, RCS or SCCS. Subversion keeps a +single copy of the master sources. This copy is called the source +``repository''; it contains all the information to permit extracting +previous versions of those files at any time. + +@subsubsection Repository name convenctions + +Repository name convenctions help us to maintain consistency of names +inside the repository. + +Repository name convenctions are applied to files and directories +inside the repository layout. As convenction, inside the repository +layout, file names are all written in lowercase +(@samp{01-welcome.png}, @samp{splash.png}, @samp{anaconda_header.png}, +etc.) and directory names are all written capitalized (e.g., +@samp{Identity}, @samp{Themes}, @samp{Motifs}, @samp{TreeFlower}, +etc.). + +Repository name convenctions are implemented inside the +@code{cli_getRepoName} function of @file{centos-art.sh} script. With +@code{cli_getRepoName} function we reduce the amount of commands and +convenctions to remember, concentrating them in just one single place +to look for fixes and improvements. + +@subsubsection Repository work flow + +Repository work flow describes the steps and time intervals used to +produce CentOS corporate visual identity inside CentOS Artwork +Repository. + +To illustrate repository work flow let's consider themes' development +cycle. + +Initially, we start working themes on their trunk development line +(e.g., @file{trunk/Identity/Themes/Motifs/TreeFlower/}), here we +organize information that cannot be produced automatically (i.e., +background images, concepts, color information, screenshots, etc.). + +Later, when theme trunk development line is considered ``ready'' for +implementation (e.g., all required backgrounds have been designed), +we create a branch for it (e.g., +@file{branches/Identity/Themes/Motifs/TreeFlower/1/}). Once the +branch has been created, we forget that branch and continue working +the trunk development line while others (e.g., an artwork quality +assurance team) test the new branch for tunning it up. + +Once the branch has been tunned up, and considered ``ready'' for +release, it is freezed under @file{tags/} directory (e.g., +@file{tags/Identity/Themes/Motifs/TreeFower/1.0/}) for packagers, +webmasters, promoters, and anyone who needs images from that CentOS +theme the tag was created for. + +Both branches and tags, inside CentOS Artwork Repository, use +numerical values to identify themselves under the same location. +Branches start at one (i.e., @samp{1}) and increment one unit for each +branch created from the same trunk development line. Tags start at +zero (i.e., @samp{0}) and increment one unit for each tag created from +the same branch development line. + +@quotation +@strong{Convenction} Do not freeze trunk development lines using tags +directly. If you think you need to freeze a trunk development line, +create a branch for it and then freeze that branch instead. +@end quotation + +The trunk development line may introduce problems we cannot see +immediatly. Certainly, the high changable nature of trunk development +line complicates finding and fixing such problems. On the other hand, +the branched development lines provide a more predictable area where +only fixes/corrections to current content are commited up to +repository. + +If others find and fix bugs inside the branched development line, we +could merge such changes/experiences back to trunk development line +(not visversa) in order for future branches, created from trunk, to +benefit. + +Time intervals used to create branches and tags may vary, just as +different needs may arrive. For example, consider the release schema +of CentOS distribution: one major release every 2 years, security +updates every 6 months, support for 7 years long. Each time a CentOS +distribution is released, specially if it is a major release, there is +a theme need in order to cover CentOS distribution artwork +requirements. At this point, is where CentOS Artwork Repository comes +up to scene. + +Before releasing a new major release of CentOS distribution we create +a branch for one of several theme development lines available inside +the CentOS Artwork Repository, perform quality assurance on it, and +later, freeze that branch using tags. Once a the theme branch has been +frozen (under @file{tags/} directory), CentOS Packagers (the persons +whom build CentOS distribution) can use that frozen branch as source +location to fulfill CentOS distribution artwork needs. The same +applies to CentOS Webmasters (the persons whom build CentOS websites), +and any other visual manifestation required by the project. + +@subsubsection Parallel directories + +Inside CentOS Artwork Repository, parallel directories are simple +directory entries built from a common parent directory and placed in a +location different to that, the common parent directory is placed on. +Parallel directories are useful to create branches, tags, +translations, documentation, pre-rendering configuration script, and +similar directory structures. + +Parallel directories take their structure from one unique parent +directory. Inside CentOS Artwork Repository, this unique parent +directory is under @file{trunk/Identity} location. The +@file{trunk/Identity} location must be considered the reference for +whatever information you plan to create inside the repository. + +In some circumstances, parallel directories may be created removing +uncommon information from their paths. Uncommon path information +refers to those directory levels in the path which are not common for +other parallel directories. For example, when rendering +@file{trunk/Identity/Themes/Motifs/TreeFlower/Distro} directory +structure, the @file{centos-art.sh} script removes the +@file{Motifs/TreeFlower/} directory levels from path, in order to +build the parallel directory used to retrived translations, and +pre-rendering configuration scripts required by @code{render} +functionality. + +Another example of parallel directory is the documentation structure +created by @code{manual} functionality. This time, +@file{centos-art.sh} script uses parallel directory information with +uncommon directory levels to build the documentation entry required by +Texinfo documentation system, inside the repository. + +Othertimes, parallel directories may add uncommon information to their +paths. This is the case we use to create branches and tags. When we +create branches and tags, a numerical identifier is added to parallel +directory structure path. The place where the numerical identifier is +set on is relevant to corporate visual identity structure and should +be carefully considered where it will be. + +When one parent directory changes, all their related parallel +directories need to be changed too. This is required in order for +parallel directories to retain their relation with the parent +directory structure. In the other hand, parallel directories should +never be modified under no reason but to satisfy the relation to their +parent directory structure. Liberal change of parallel directories +may suppresses the conceptual idea they were initially created for; +and certainly, things may stop working the way they should do. + +@subsubsection Syncronizing path information + +Parallel directories are very useful to keep repository organized but +introduce some complications. For instance, consider what would +happen to functionalities like @code{manual} (@samp{trunk Scripts Bash +Functions Manual}) that rely on parent directory structures to create +documentation entries (using parallel directory structures) if one of +those parent directory structures suddenly changes after the +documentation entry has been already created for it? + +In such cases, functionalities like @code{manual} may confuse +themselves if path information is not updated to reflect the relation +with its parent directory. Such functionalities work with parent +directory structure as reference; if a parent directory changes, the +functionalities dont't even note it because they work with the last +parent directory structure available in the repository, no matter what +it is. + +In the specific case of documentation (the @code{manual} +functionality), the problem mentioned above provokes that older parent +directories, already documented, remain inside documentation directory +structures as long as you get your hands into the documentation +directory structure (@file{trunk/Manuals}) and change what must be +changed to match the new parent directory structure. + +There is no immediate way for @code{manual}, and similar +functionalities that use parent directories as reference, to know when +and how directory movements take place inside the repository. Such +information is available only when the file movement itself takes +place inside the repository. So, is there, at the moment of moving +files, when we need to syncronize parallel directories with their +unique parent directory structure. + +@quotation +@strong{Warning} There is not support for URL reference inside +@file{centos-art.sh} script. The @file{centos-art.sh} script is +designed to work with local files inside the working copy only. +@end quotation + +As CentOS Artwork Repository is built over a version control system, +file movements inside the repository are considered repository +changes. In order for these repository changes to be versioned, we +need to, firstly, add changes into the version control system, commit +them, and later, perform movement actions using version control system +commands. This configuration makes possible for everyone to know about +changes details inside the repository; and if needed, revert or update +them back to a previous revision. + +Finally, once all path information has been corrected, it is time to +take care of information inside the files. For instance, considere +what would happen if you make a reference to a documentation node, and +later the documentation node you refere to is deleted. That would make +Texinfo to produce error messages at export time. So, the +@file{centos-art.sh} script needs to know when such changes happen, in +a way they could be noted and handled without producing errors. + +@subsubsection What is the right place to store it? + +Occasionly, you may find that new corporate visual identity components +need to be added to the repository. If that is your case, the first +question you need to ask yourself, before start to create directories +blindly all over, is: What is the right place to store it? + +The CentOS Community different free support vains (see: +@url{http://wiki.centos.org/GettingHelp}) are the best place to find +answers to your question, but going there with hands empty is not good +idea. It may give the impression you don't really care about. Instead, +consider the following suggestions to find your own comprehension and +so, make your propositions based on it. + +When we are looking for the correct place to store new files, to bear +in mind the corporate visual identity structure used inside the CentOS +Artwork Repository (@pxref{trunk Identity}) would be probaly the best +advice we could offer, the rest is just matter of choosing appropriate +names. To illustrate this desition process let's consider the +@file{trunk/Identity/Themes/Motifs/TreeFlower} directory as example. +It is the trunk development line of @emph{TreeFlower} artistic motif. +Artistic motifs are considered part of themes, which in turn are +considered part of CentOS corporate visual identity. + +When building parent directory structures, you may find that reaching +an acceptable location may take some time, and as it uses to happen +most of time; once you've find it, that may be not a definite +solution. There are many concepts that you need to play with, in +order to find a result that match the conceptual idea you try to +implement in the new directory location. To know which these concepts +are, split the location in words and read its documentation entry from +less specific to more specific. + +For example, the @file{trunk/Identity/Themes/Motifs/TreeFlower} +location evolved through several months of contant work and there is +no certain it won't change in the future, even it fixes quite well the +concept we are trying to implement. The concepts used in +@file{trunk/Identity/Themes/Distro/Motifs/TreeFlower} location are +described in the following commands, respectively: + +@verbatim +centos-art manual --read=turnk/ +centos-art manual --read=turnk/Identity/ +centos-art manual --read=turnk/Identity/Themes/ +centos-art manual --read=turnk/Identity/Themes/Motifs/ +centos-art manual --read=turnk/Identity/Themes/Motifs/TreeFlower/ +@end verbatim + +Other location concepts can be found similary as we did above, just +change the location we used above by the one you are trying to know +concepts for. + +@subsection Usage + +@table @command +@item centos-art path --copy='SRC' --to='DST' + +Copy @option{SRC} to @option{DST} and schedule @option{DST} for +addition (with history). In this command, @file{SRC} and @file{DST} +are both working copy (WC) entries. + +@item centos-art path --delete='SRC' + +Delete @option{DST}. In order for this command to work the file or +directory you intend to delete should be under version control first. +In this command, @file{SRC} is a working copy (WC) entry. + +@end table + +@subsection See also + +@menu +* trunk Scripts Bash:: +@comment --- Removed(* trunk Scripts Bash Functions::) --- +@end menu diff --git a/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Render.texi b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Render.texi new file mode 100644 index 0000000..7dfe2c5 --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Render.texi @@ -0,0 +1,736 @@ +The @code{render} functionality exists to produce both identity and +translation files on different levels of information (i.e., different +languages, release numbers, architectures, etc.). + +The @code{render} functionality relies on ``renderable directory +structures'' to produce files. Renderable directory structures can be +either ``identity directory structures'' or ``translation directory +structures'' with special directories inside. + +@subsection Renderable identity directory structures + +Renderable identity directory structures are the starting point of +identity rendition. Whenever we want to render a component of CentOS +corporate visual identity, we need to point @file{centos-art.sh} to a +renderable identity directory structure. If such renderable identity +directory structure doesn't exist, then it is good time to create it. + +Inside the working copy, one renderable identity directory structures +represents one visual manifestation of CentOS corporate visual +identity, or said differently, each visual manifestation of CentOS +corporate visual identity should have one renderable identity +directory structure. + +Inside renderable identity directory structures, @file{centos-art.sh} +can render both image-based and text-based files. Specification of +whether a renderable identity directory structure produces image-based +or text-based content is a configuration action that takes place in +the pre-rendition configuration script of that renderable identity +directory structure. + +Inside renderable identity directory structures, content production is +organized in different configurations. A content production +configuration is a unique combination of the components that make an +identity directory structure renderable. One content production +configuration does one thing only (e.g., to produce untranslated +images), but it can be extended (e.g., adding translation files) to +achieve different needs (e.g., to produce translated images). + +@subsubsection Design template without translation + +The design template without translation configuration is based on a +renderable identity directory structure with an empty translation +directory structure. In this configuration, one design template +produces one untranslated file. Both design templates and final +untranslated files share the same file name, but they differ one +another in file-type and file-extension. + +For example, to produce images without translations (there is no much +use in producing text-based files without translations), consider the +following configuration: + +@table @strong +@item One renderable identity directory structure: + +In this example we used @file{Identity/Path/To/Dir} as the identity +component we want to produce untranslated images for. Identity +components can be either under @file{trunk/} or @file{branches/} +directory structure. + +The identity component (i.e., @file{Identity/Path/To/Dir}, in this +case) is also the bond component we use to connect the identity +directory structures with their respective auxiliar directories (i.e., +translation directory structres and pre-rendition configuration +structures). The bond component is the path convenction that +@file{centos-art.sh} uses to know where to look for related +translations, configuration scripts and whatever auxiliar thing a +renderable directory structure may need to have. + +@verbatim + | The bond component + |----------------->| +trunk/Identity/Path/To/Dir <-- Renderable identity directory structure. +|-- Tpl <-- Design template directory. +| `-- file.svg <-- Design template file. +`-- Img <-- Directory used to store final files. + `-- file.png <-- Final image-based file produced from + design template file. +@end verbatim + +Inside design template directory, design template files are based on +@acronym{SVG,Scalable Vector Graphics} and use the extension +@code{.svg}. Design template files can be organized using several +directory levels to create a simple but extensible configuration, +specially if translated images are not required. + +In order for @acronym{SVG,Scalable Vector Graphics} files to be +considered ``design template'' files, they should be placed under the +design template directory and to have set a @code{CENTOSARTWORK} +object id inside. + +The @code{CENTOSARTWORK} word itself is a convenction name we use to +define which object/design area, inside a design template, the +@file{centos-art.sh} script will use to export as +@acronym{PNG,Portable Network Graphic} image at rendition time. +Whithout such object id specification, the @file{centos-art.sh} script +cannot know what object/design area you (as designer) want to export +as @acronym{PNG,Portable Network Graphic} image file. + +@quotation +@strong{Note} At rendition time, the content of @file{Img/} directory +structure is produced by @file{centos-art.sh} automatically. +@end quotation + +When a renderable identity directory structure is configured to +produce image-based content, @file{centos-art.sh} produces +@acronym{PNG,Portable Network Graphics} files with the @code{.png} +extension. Once the base image format has been produced, it is +possible for @file{centos-art.sh} to use it in order to automatically +create other image formats that may be needed (--- @strong{Removed}(pxref:trunk Scripts +Bash Functions Render Config) ---). + +Inside the working copy, you can find an example of ``design template +without translation'' configuration at @file{trunk/Identity/Models/}. + +@xref{trunk Identity}, for more information. + +@item One translation directory structure: + +In order for an identity entry to be considered an identity renderable +directory structure, it should have a translation entry. The content +of the translation entry is relevant to determine how to process the +identity renderable directory entry. + +If the translation entry is empty (i.e., there is no file inside it), +@file{centos-art.sh} interprets the identity renderable directory +structure as a ``design templates without translation'' configuration. + +@verbatim + | The bond component + |----------------->| +trunk/Translations/Identity/Path/To/Dir +`-- (empty) +@end verbatim + +If the translation entry is not empty, @file{centos-art.sh} can +interpret the identity renderable directory structure as one of the +following configurations: ``design template with translation +(one-to-one)'' or ``design template with translation (optimized)''. +Which one of these configurations is used depends on the value +assigned to the matching list (@var{MATCHINGLIST}) variable in the +pre-rendition configuration script of the renderable identity +directory structure we are producing images for. + +If the matching list variable is empty (as it is by default), then +``design template with translation (one-to-one)'' configuration is +used. In this configuration it is required that both design templates +and translation files have the same file names. This way, @emph{one} +translation files is applied to @emph{one} design template, to produce +@emph{one} translated image. + +If the matching list variable is not empty (because you redefine it in +the pre-rendition configuration script), then ``design template with +translation (optimized)'' configuration is used instead. In this +configuration, design templates and translation files don't need to +have the same names since such name relationship between them is +specified in the matching list properly. + +--- @strong{Removed}(xref:trunk Translations) ---, for more information. + +@item One pre-rendition configuration script: + +In order to make an identity directory structure renderable, a +pre-rendition configuration script should exist for it. The +pre-rendition configuration script specifies what type of rendition +does @file{centos-art.sh} will perform over the identity directory +structure and how does it do that. + +@verbatim + | The bond component + |----------------->| +trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir +`-- render.conf.sh +@end verbatim + +In this configuration the pre-rendition configuration script +(@file{render.conf.sh}) would look like the following: + +@verbatim +function render_loadConfig { + + # Define rendition actions. + ACTIONS[0]='BASE:renderImage' + +} +@end verbatim + +Since translation directory structure is empty, @file{centos-art.sh} +assumes a ``design template without translation'' configuration to +produce untranslated images. + +To produce untranslated images, @file{centos-art.sh} takes one design +template and creates one temporal instance from it. Later, +@file{centos-art.sh} uses the temporal design template instance as +source file to export the final untranslated image. The action of +exporting images from @acronym{SVG,Scalable Vector Graphics} to +@acronym{PNG,Portable Network Graphics} is possible thanks to +Inkscape's command-line interface and the @code{CENTOSARTWORK} object +id we previously set inside design templates. + +@verbatim +centos-art.sh render --identity=trunk/Identity/Path/To/Dir +------------------------------------------------- +0 | Execute centos-art.sh on renderable identity directory structure. +--v---------------------------------------------- +trunk/Identity/Path/To/Dir/Tpl/file.svg +------------------------------------------------- +1 | Create instance from design template. +--v---------------------------------------------- +/tmp/centos-art.sh-a07e824a-5953-4c21-90ae-f5e8e9781f5f-file.svg +------------------------------------------------- +2 | Render untranslated image from design template instance. +--v---------------------------------------------- +trunk/Identity/NewDir/Img/file.png +------------------------------------------------- +3 | Remove design template instance. +@end verbatim + +Finally, when the untranslated image has been created, the temporal +design template instance is removed. At this point, +@file{centos-art.sh} takes the next design template and repeats the +whole production flow once again (design template by design template), +until all design templates be processed. + +--- @strong{Removed}(xref:trunk Scripts Bash Functions Render Config) ---, for more +information. +@end table + +@subsubsection Design template with translation (one-to-one) + +Producing untranslated images is fine in many cases, but not always. +Sometimes it is required to produce images in different languages and +that is something that untrasnlated image production cannot achieve. +However, if we fill its empty translation entry with translation files +(one for each design template) we extend the production flow from +untranslated image production to translated image production. + +In order for @file{centos-art.sh} to produce images correctly, each +design template should have one translation file and each translation +file should have one design template. Otherwise, if there is a +missing design template or a missing translation file, +@file{centos-art.sh} will not produce the final image related to the +missing component. + +In order for @file{centos-art.sh} to know which is the relation +between translation files and design templates the translation +directory structure is taken as reference. For example, the +@file{trunk/Translations/Identity/Path/To/Dir/file.sed} translation +file does match @file{trunk/Identity/Path/To/Dir/Tpl/file.svg} design +template, but it doesn't match +@file{trunk/Identity/Path/To/Dir/File.svg} or +@file{trunk/Identity/Path/To/Dir/Tpl/File.svg} or +@file{trunk/Identity/Path/To/Dir/Tpl/SubDir/file.svg} design +templates. + +The pre-rendition configuration script used to produce untranslated +images is the same we use to produce translated images. There is no +need to modify it. So, as we are using the same pre-rendition +configuration script, we can say that translated image production is +somehow an extended/improved version of untranslated image production. + +@quotation +@strong{Note} If we use no translation file in the translation entry +(i.e., an empty directory), @file{centos-art.sh} assumes the +untranslated image production. If we fill the translation entry with +translation files, @file{centos-art.sh} assumes the translated image +production. +@end quotation + +To produce final images, @file{centos-art.sh} applies one translation +file to one design template and produce a translated design template +instance. Later, @file{centos-art.sh} uses the translated template +instance to produce the translated image. Finally, when the translated +image has been produced, @file{centos-art.sh} removes the translated +design template instance. This production flow is repeated for each +translation file available in the translatio entry. + +@verbatim +centos-art.sh render --identity=trunk/Identity/Path/To/Dir +------------------------------------------------- +0 | Execute centos-art.sh on directory structure. +--v---------------------------------------------- +trunk/Translations/Identity/Path/To/Dir/file.sed +------------------------------------------------- +1 | Apply translation to design template. +--v---------------------------------------------- +trunk/Identity/Path/To/Dir/Tpl/file.svg +------------------------------------------------- +2 | Create design template instance. +--v---------------------------------------------- +/tmp/centos-art.sh-a07e824a-5953-4c21-90ae-f5e8e9781f5f-file.svg +------------------------------------------------- +3 | Render PNG image from template instance. +--v---------------------------------------------- +trunk/Identity/NewDir/Img/file.png +------------------------------------------------- +4 | Remove design template instance. +@end verbatim + +@subsubsection Design template with translation (optimized) + +Producing translated images satisfies almost all our production images +needs, but there is still a pitfall in them. In order to produce +translated images as in the ``one-to-one'' configuration describes +previously, it is required that one translation file has one design +template. That's useful in many cases, but what would happen if we +need to apply many different translation files to the same design +template? Should we have to duplicate the same design template file +for each translation file, in order to satisfy the ``one-to-one'' +relation? What if we need to assign translation files to design +templates arbitrarily? + +Certenly, that's something the ``one-to-one'' configuration cannot +handle. So, that's why we had to ``optimize'' it. The optimized +configuration consists on using a matching list (@var{MATCHINGLIST}) +variable that specifies the relationship between translation files and +design templates in an arbitrary way. Using such matching list between +translation files and design templates let us use as many assignment +combinations as translation files and design templates we are working +with. + +The @var{MATCHINGLIST} variable is set in the pre-rendition +configuration script of the component we want to produce images for. +By default, the @var{MATCHINGLIST} variable is empty which means no +matching list is used. Otherwise, if @var{MATCHINGLIST} variable has a +value different to empty value then, @file{centos-art.sh} interprets +the matching list in order to know how translation files are applied +to design templates. + +For example, consider the following configuration: + +@table @strong +@item One entry under @file{trunk/Identity/}: + +In this configuration we want to produce three images using a +paragraph-based style, controlled by @file{paragraph.svg} design +template; and one image using a list-based style, controlled by +@file{list.svg} design template. + +@verbatim +trunk/Identity/Path/To/Dir +|-- Tpl +| |-- paragraph.svg +| `-- list.svg +`-- Img + |-- 01-welcome.png + |-- 02-donate.png + |-- 03-docs.png + `-- 04-support.png +@end verbatim + +@item One entry under @file{trunk/Translations/}: + +In order to produce translated images we need to have one translation +file for each translated image we want to produce. Notice how +translation names do match final image file names, but how translation +names do not match design template names. When we use matching list +there is no need for translation files to match the names of design +templates, such name relation is set inside the matching list itself. + +@verbatim +trunk/Translations/Identity/Path/To/Dir +|-- 01-welcome.sed +|-- 02-donate.sed +|-- 03-docs.sed +`-- 04-support.sed +@end verbatim + +@item One entry under @file{trunk/trunk/Scripts/Bash/Functions/Render/Config/}: + +In order to produce different translated images using specific design +templates, we need to specify the relation between translation files +and design templates in a way that @file{centos-art.sh} could know +exactly what translation file to apply to what design template. This +relation between translation files and design templates is set using +the matching list @var{MATCHINGLIST} variable inside the pre-rendition +configuration script of the component we want to produce images for. + +@verbatim +trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir +`-- render.conf.sh +@end verbatim + +In this configuration the pre-rendition configuration script +(@file{render.conf.sh}) would look like the following: + +@verbatim +function render_loadConfig { + + # Define rendition actions. + ACTIONS[0]='BASE:renderImage' + + # Define matching list. + MATCHINGLIST="\ + paragraph.svg:\ + 01-welcome.sed\ + 02-donate.sed\ + 04-support.sed + list.svg:\ + 03-docs.sed + " + +} +@end verbatim + +As result, @file{centos-art.sh} will produce @file{01-welcome.png}, +@file{02-donate.png} and @file{04-support.png} using the +paragraph-based design template, but @file{03-docs.png} using the +list-based design template. +@end table + +@subsubsection Design template with translation (optimized+flexibility) + +In the production models we've seen so far, there are design templates +to produce untranslated images and translation files which combiend +with design templates produce translated images. That may seems like +all our needs are covered, doesn't it? Well, it @emph{almost} does. + +Generally, we use design templates to define how final images will +look like. Generally, each renderable directory structure has one +@file{Tpl/} directory where we organize design templates for that +identity component. So, we can say that there is only one unique +design template definition for each identity component; or what is the +same, said differently, identity components can be produced in one way +only, the way its own design template directory specifies. This is +not enough for theme production. It is a limitation, indeed. + +Initially, to create one theme, we created one renderable directory +structure for each theme component. When we found ourselves with many +themes, and components inside them, it was obvious that the same +design model was duplicated inside each theme. As design models were +independently one another, if we changed one theme's design model, +that change was useless to other themes. So, in order to reuse design +model changes, we unified design models into one common directory +structure. + +With design models unified in a common structure, another problem rose +up. As design models also had the visual style of theme components, +there was no difference between themes, so there was no apparent need +to have an independent theme directory structure for each different +theme. So, it was also needed to separate visual styles from design +models. + +At this point there are two independent worklines: one directory +structure to store design models (the final image characteristics +[i.e., dimensions, translation markers, etc.]) and one directory +structure to store visual styles (the final image visual style [i.e., +the image look and feel]). So, it is possible to handle both +different design models and different visual styles independtly one +another and later create combinations among them using +@file{centos-art.sh}. + +For example, consider the following configuration: + +@table @strong +@item One entry under @file{trunk/Identity/Themes/Models/}: + +The design model entry exists to organize design model files (similar +to design templates). Both design models and design templates are very +similar; they both should have the @code{CENTOSARTWORK} export id +present to identify the exportation area, translation marks, etc. +However, design models do use dynamic backgrounds inclusion while +design templates don't. + +@verbatim + THEMEMODEL | | The bond component + |<----| |--------------------->| +trunk/Identity/Themes/Models/Default/Distro/Anaconda/Progress/ +|-- paragraph.svg +`-- list.svg +@end verbatim + +Inisde design models, dynamic backgrounds are required in order for +different artistic motifs to reuse common design models. Firstly, in +order to create dynamic backgrounds inside design models, we import a +bitmap to cover design model's background and later, update design +model's path information to replace fixed values to dynamic values. + +@item One entry under @file{trunk/Identity/Themes/Motifs/}: + +The artistic motif entry defines the visual style we want to produce +images for, only. Final images (i.e., those built from combining both +design models and artistic motif backrounds) are not stored here, but +under branches directory structure. In the artistic motif entry, we +only define those images that cannot be produced automatically by +@file{centos-art.sh} (e.g., Backgrounds, Color information, +Screenshots, etc.). + +@verbatim + Artistic motif name | | Artistic motif backgrounds + |<-------| |-------->| +trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/ +|-- Img +| |-- Png +| | |-- 510x300.png +| | `-- 510x300-final.png +| `-- Jpg +| |-- 510x300.jpg +| `-- 510x300-final.jpg +|-- Tpl +| `-- 510x300.svg +`-- Xcf + `-- 510x300.xcf +@end verbatim + +@item One entry under @file{trunk/Translations/}: + +The translation entry specifies, by means of translation files, the +language-specific information we want to produce image for. When we +create the translation entry we don't use the name of neither design +model nor artistic motif, just the design model component we want to +produce images for. + +@verbatim + | The bond component + |--------------------->| +trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ +`-- 5 + |-- en + | |-- 01-welcome.sed + | |-- 02-donate.sed + | `-- 03-docs.sed + `-- es + |-- 01-welcome.sed + |-- 02-donate.sed + `-- 03-docs.sed +@end verbatim + +@item One entry under @file{trunk/Scripts/Bash/Functions/Render/Config/}: + +There is one pre-rendition configuration script for each theme +component. So, each time a theme component is rendered, its +pre-rendition configuration script is evaluated to teach +@file{centos-art.sh} how to render the component. + +@verbatim +trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Distro/Anaconda/Progress/ +`-- render.conf.sh +@end verbatim + +In this configuration the pre-rendition configuration script +(@file{render.conf.sh}) would look like the following: + +@verbatim +function render_loadConfig { + + # Define rendition actions. + ACTIONS[0]='BASE:renderImage' + + # Define matching list. + MATCHINGLIST="\ + paragraph.svg:\ + 01-welcome.sed\ + 02-donate.sed + list.svg:\ + 03-docs.sed + " + + # Deifne theme model. + THEMEMODEL='Default' + +} +@end verbatim +@end table + +The production flow of ``optimize+flexibility'' configuration@dots{} +@subsection Renderable translation directory structures + +Translation directory structures are auxiliar structures of renderable +identity directory structures. There is one translation directory +structure for each renderable identity directory structure. Inside +translation directory structures we organize translation files used by +renderable identity directory structures that produce translated +images. Renderable identity directory structures that produce +untranslated images don't use translation files, but they do use a +translation directory structure, an empty translation directory +structure, to be precise. + +In order to aliviate production of translation file, we made +translation directory structures renderable adding a template +(@file{Tpl/}) directory structure to handle common content inside +translation files. This way, we work on translation templates and +later use @file{centos-art.sh} to produce specific translation files +(based on translation templates) for different information (e.g., +languages, release numbers, architectures, etc.). + +If for some reason, translation files get far from translation +templates and translation templates become incovenient to produce such +translation files then, care should be taken to avoid replacing the +content of translation files with the content of translation templates +when @file{centos-art.sh} is executed to produce translation files +from translation templates. + +Inside renderable translation directory structures, +@file{centos-art.sh} can produce text-based files only. + +@subsection Copying renderable directory structures + +A renderable layout is formed by design models, design images, +pre-rendition configuration scripts and translations files. This way, +when we say to duplicate rendition stuff we are saying to duplicate +these four directory structures (i.e., design models, design images, +pre-rendition configuration scripts, and related translations files). + +When we duplicate directories, inside `trunk/Identity' directory +structure, we need to be aware of renderable layout described above +and the source location used to perform the duplication action. The +source location is relevant to centos-art.sh script in order to +determine the required auxiliar information inside directory +structures that need to be copied too (otherwise we may end up with +orphan directory structures unable to be rendered, due the absence of +required information). + +In order for a renderable directory structure to be valid, the new +directory structure copied should match the following conditions: + +@enumerate +@item To have a unique directory structure under +@file{trunk/Identity}, organized by any one of the above +organizational designs above. + +@item To have a unique directory structure under +@file{trunk/Translations} to store translation files. + +@item To have a unique directory structure under +@file{trunk/Scripts/Bash/Functions/Render/Config} to set pre-rendition +configuration script. +@end enumerate + +As convenction, the @code{render_doCopy} function uses +@file{trunk/Identity} directory structure as source location. Once +the @file{trunk/Identity} directory structure has been specified and +verified, the related path information is built from it and copied +automatically to the new location specified by @var{FLAG_TO} variable. + +Design templates + No translation: + +Command: +- centos-art render --copy=trunk/Identity/Path/To/Dir --to=trunk/Identity/NewPath/To/Dir + +Sources: +- trunk/Identity/Path/To/Dir +- trunk/Translations/Identity/Path/To/Dir +- trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir + +Targets: +- trunk/Identity/NewPath/To/Dir +- trunk/Translations/Identity/NewPath/To/Dir +- trunk/Scripts/Bash/Functions/Render/Config/Identity/NewPath/To/Dir + +Renderable layout 2: + +Command: +- centos-art render --copy=trunk/Identity/Themes/Motifs/TreeFlower \ + --to=trunk/Identity/Themes/Motifs/NewPath/To/Dir + +Sources: +- trunk/Identity/Themes/Motifs/TreeFlower +- trunk/Translations/Identity/Themes +- trunk/Translations/Identity/Themes/Motifs/TreeFlower +- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes +- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/TreeFlower + +Targets: +- trunk/Identity/Themes/Motifs/NewPath/To/Dir +- trunk/Translations/Identity/Themes +- trunk/Translations/Identity/Themes/Motifs/NewPath/To/Dir +- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes +- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewPath/To/Dir + +Notice that design models are not included in source or target +locations. This is intentional. In ``Renderable layout 2'', design +models live by their own, they just exist, they are there, available +for any artistic motif to use. By default `Themes/Models/Default' +design model directory structure is used, but other design models +directory structures (under Themes/Models/) can be created and used +changing the value of THEMEMODEL variable inside the pre-rendition +configuration script of the artistic motif source location you want to +produce. + +Notice how translations and pre-rendition configuration scripts may +both be equal in source and target. This is because such structures +are common to all artistic motifs (the default values to use when no +specific values are provided). + +- The common directory structures are not copied or deleted. We cannot + copy a directory structure to itself. + +- The common directory structures represent the default value to use + when no specific translations and/or pre-rendition configuration + script are provided inside source location. + +- The specific directory structures, if present, are both copiable and + removable. This is, when you perform a copy or delete action from + source, that source specific auxiliar directories are transfered in + the copy action to a new location (that specified by FLAG_TO + variable). + +- When translations and/or pre-rendition configuration scripts are + found inside the source directory structure, the centos-art.sh + script loads common auxiliar directories first and later specific + auxiliar directories. This way, identity rendition of source + locations can be customized idividually over the base of common + default values. + +- The specific auxiliar directories are optional. + +- The common auxiliar directories should be present always. This is, + in order to provide the information required by render functionality + (i.e., to make it functional in the more basic level of its + existence). + +Notice how the duplication process is done from `trunk/Identity' on, +not the oposite. If you try to duplicate a translation structure (or +similar auxiliar directory structures like pre-rendition configuration +scripts), the `trunk/Identity' for that translation is not created. +This limitation is impossed by the fact that many `trunk/Identity' +directory structures may reuse/share the same translation directory +structure. We cannot delete one translation (or similar) directory +structures while a related `trunk/Identity/' directory structure is +still in need of it. + +The `render_doCopy' functionality does duplicate directory structures +directly involved in rendition process only. Once such directories +have been duplicated, the functionality stops thereat. + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@comment --- Removed(* trunk Scripts Bash Functions Render Config::) --- +@end menu diff --git a/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Render/Config.texi b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Render/Config.texi new file mode 100644 index 0000000..3b3322b --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Render/Config.texi @@ -0,0 +1,192 @@ +@subsection Goals + +The @file{trunk/Scripts/Bash/Config} directory exists to oraganize +pre-rendering configuration scripts. + +@subsection Description + +Pre-rendering configuration scripts let you customize the way +@command{centos-art.sh} script renders identity and translation +repository entries. Pre-rendering configuration scripts are +@file{render.conf.sh} files with @command{render_loadConfig} function +definition inside. + +There is one @file{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. + +@subsubsection The @file{render.conf.sh} identity model + +Inside CentOS Artwork Repository, we consider identity entries to all +directories under @file{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: + +@verbatim +#!/bin/bash + +function render_loadConfig { + + # Define rendering actions. + ACTIONS[0]='BASE:renderImage' + ACTIONS[1]='POST:renderFormats: tif xpm pdf ppm' + +} +@end verbatim + +Inside identity pre-rendering configuration scripts, text-based +pre-rendering configuration scripts look like the following: + +@verbatim +#!/bin/bash + +function render_loadConfig { + + # Define rendering actions. + ACTIONS[0]='BASE:renderText' + ACTIONS[1]='POST:formatText: --width=70 --uniform-spacing' + +} +@end verbatim + +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. + +@subsubsection The @file{render.conf.sh} translation model + +Translation pre-rendering configuration scripts take precedence before +default translation rendering action. Translation pre-rendering +actions are useful when default translation rendering action do not +fit itself to translation entry rendering requirements. + +@subsubsection The @file{render.conf.sh} rendering actions + +Inside both image-based and text-based identity pre-rendering +configuration scripts, we use the @samp{ACTIONS} array variable to +define the way @command{centos-art.sh} script performs identity +rendering. Identity rendering is organized by one @samp{BASE} action, +and optional @samp{POST} and @samp{LAST} rendering actions. + +The @samp{BASE} action specifies what kind of rendering does the +@command{centos-art.sh} script will perform with the files related to +the pre-rendering configuration script. The @samp{BASE} action is +required. Possible values to @samp{BASE} action are either +@samp{renderImage} or @samp{renderText} only. + +To specify the @samp{BASE} action you need to set the @samp{BASE:} +string followed by one of the possible values. For example, if you +want to render images, consider the following definition of +@samp{BASE} action: + +@verbatim +ACTIONS[0]='BASE:renderImage' +@end verbatim + +Only one @samp{BASE} action must be specified. If more than one +@samp{BASE} action is specified, the last one is used. If no +@samp{BASE} action is specified at all, an error is triggered and the +@command{centos-art.sh} script ends its execution. + +The @samp{POST} action specifies which action to apply for +each file rendered (at the rendering time). This action is optional. +You can set many different @samp{POST} actions to apply many different +actions over the same already rendered file. Possible values to +@samp{POST} action are @samp{renderFormats}, @samp{renderSyslinux}, +@samp{renderGrub}, etc. + +To specify the @samp{POST} action, you need to use set the +@samp{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 @samp{xpm}, @samp{jpg}, and +@samp{tif} images, based on already rendered @samp{png} image, and +also organize the produced files in directories named as their own +extensions: + +@verbatim +ACTIONS[0]='BASE:renderImage' +ACTIONS[1]='POST:renderFormats: xpm jpg tif' +ACTIONS[2]='POST:groupByFormat: png xpm jpg tif' +@end verbatim + +In the previous example, file organization takes place at the moment +of rendering, just after producing the @samp{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 @samp{POST:groupByFormat} action line: + +@verbatim +ACTIONS[0]='BASE:renderImage' +ACTIONS[1]='POST:renderFormats: xpm jpg tif' +@end verbatim + +The @samp{LAST} action specifies which actions to apply once the last +file in the list of files to process has been rendered. The +@samp{LAST} action is optional. Possible values for @samp{LAST} +actions may be @samp{groupByFormat}, @samp{renderGdmTgz}, etc. + +@quotation +@strong{Note} --- @strong{Removed}(xref:trunk Scripts Bash Functions Render) ---, to know more +about possible values for @samp{BASE}, @samp{POST} and @samp{LAST} +action definitions. +@end quotation + +To specify the @samp{LAST} action, you need to set the @samp{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: + +@verbatim +ACTIONS[0]='BASE:renderImage' +ACTIONS[1]='POST:renderFormats: xpm jpg tif' +ACTIONS[2]='LAST:groupByformat: png xpm jpg tif' +@end verbatim + +@subsection Usage + +Use the following commands to administer both identity and translation +pre-rendering configuration scripts: + +@table @samp + +@item centos-art config --create='path/to/dir/' + +Use this command to create @samp{path/to/dir} related pre-rendering +configuration script. + +@item centos-art config --edit='path/to/dir/' + +Use this command to edit @samp{path/to/dir} related pre-rendering +configuration script. + +@item centos-art config --read='path/to/dir/' + +Use this command to read @samp{path/to/dir} related pre-rendering +configuration script. + +@item centos-art config --remove='path/to/dir/' + +Use this command to remove @samp{path/to/dir} related pre-rendering +configuration script. + +@end table + +In the commands above, @samp{path/to/dir} refers to one renderable +directory path under @file{trunk/Identity} or +@file{trunk/Translations} structures only. + +@subsection See also + +@menu +* trunk Scripts Bash:: +@comment --- Removed(* trunk Scripts Bash Functions::) --- +@comment --- Removed(* trunk Scripts Bash Functions Render::) --- +@end menu diff --git a/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Shell.texi b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Shell.texi new file mode 100644 index 0000000..a5016fe --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Shell.texi @@ -0,0 +1,184 @@ +@subsection Goals + +This section exists to organize files related to @code{shell} +functionality of @file{centos-art.sh} script. + +@subsection Description + +The @code{shell} functionality of @file{centos-art.sh} script helps +you to maintain bash scripts inside repository. For example, suppose +you've created many functionalities for @file{centos-art.sh} script, +and you want to use a common copyright and license note for +consistency in all your script files. If you have a bunch of files, +doing this one by one wouldn't be a big deal. In contrast, if the +amount of files grows, updating the copyright and license note for all +of them would be a task rather tedious. The @code{shell} functionality +exists to solve maintainance tasks just as the one previously +mentioned. + +When you use @code{shell} functionality to update copyright inside +script files, it is required that your script files contain (at least) +the following top commentary structure: + +@float Figure,fig:trunk/Scripts/Bash/Functions/Shell:1 +@verbatim + 1| #!/bin/bash + 2| # + 3| # doSomething.sh -- The function description goes here. + 4| # + 5| # Copyright + 6| # + 7| # ... + 8| # + 9| # ---------------------------------------------------------------------- +10| # $Id$ +11| # ---------------------------------------------------------------------- +12| +13| function doSomething { +14| +15| } +@end verbatim +@caption{The functions script base comment structure} +@end float + +Relevant lines in the above structure are lines from 5 to 9. +Everything else in the file is left immutable. + +When you are updating copyright through @code{shell} +functionality, the @file{centos-art.sh} script replaces everything +in-between line 5 ---the first one matching @samp{^# Copyright .+$} +string--- and line 9---the first long dash separator matching @samp{^# +-+$}--- with the content of copyright template instance. + +@quotation +@strong{Caution} Be sure to add the long dash separator that matches +@samp{^# -+$} regular expression @emph{before} the function +definition. Otherwise, if the @samp{Copyright} line is present but no +long dash separator exists, @file{centos-art.sh} will remove anything +in-between the @samp{Copyright} line and the end of file. This way you +may lost your function definitions entirely. +@end quotation + +The copyright template instance is created from one copyright template +stored in the @file{Config/tpl_forCopyright.sed} file. The template +instance is created once, and later removed when no longer needed. At +this moment, when template instance is created, the +@file{centos-art.sh} script takes advantage of automation in order to +set copyright full name and date dynamically. + +When you use @code{shell} functionality to update copyright, the first +thing @file{shell} functionality does is requesting copyright +information to user, and later, if values were left empty (i.e., no +value was typed before pressing @key{RET} key), the @file{shell} +functionality uses its own default values. + +When @code{shell} functionality uses its own default values, the final +copyright note looks like the following: + +@float Figure,fig:trunk/Scripts/Bash/Functions/Shell:2 +@verbatim + 1| #!/bin/bash + 2| # + 3| # doSomthing.sh -- The function description goes here. + 4| # + 5| # Copyright (C) 2003, 2010 The CentOS Project + 6| # + 7| # This program is free software; you can redistribute it and/or modify + 8| # it under the terms of the GNU General Public License as published by + 9| # the Free Software Foundation; either version 2 of the License, or +10| # (at your option) any later version. +11| # +12| # This program is distributed in the hope that it will be useful, but +13| # WITHOUT ANY WARRANTY; without even the implied warranty of +14| # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +15| # General Public License for more details. +16| # +17| # You should have received a copy of the GNU General Public License +18| # along with this program; if not, write to the Free Software +19| # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 +20| # USA. +21| # +22| # ---------------------------------------------------------------------- +23| # $Id$ +24| # ---------------------------------------------------------------------- +25| +26| function doSomething { +27| +28| } +@end verbatim +@caption{The function script comment example} +@end float + +Relevant lines in the above structure are lines from 5 to 22. Pay +attention how the copyright line was built, and how the license was +added into the top comment where previously was just three dots. +Everything else in the file was left immutable. + +To change copyright information (i.e., full name or year information), +run the @code{shell} functionality over the root directory containing +the script files you want to update copyright in and enter the +appropriate information when it be requested. You can run the +@code{shell} functionality as many times as you need to. + +To change copyright license (i.e., the text in-between lines 7 and +20), you need to edit the @file{Config/tpl_forCopyright.sed} file, set +the appropriate information, and run the @code{shell} functionality +once again for changes to take effect over the files you specify. + +@quotation +@strong{Important} The @file{centos-art.sh} script is released as: + +@verbatim +GNU GENERAL PUBLIC LICENSE +Version 2, June 1991 + +Copyright (C) 1989, 1991 Free Software Foundation, Inc. +59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. +@end verbatim + +Do not change the license information under which @file{centos-art.sh} +script is released. Instead, if you think a different license must be +used, please share your reasons at @email{centos-devel@@centos-art.sh, +CentOS Developers mailing list}. +@end quotation + +@subsection Usage + +@table @command +@item centos-art sh --update-copyright='path/to/dir' +@itemx centos-art sh --update-copyright='path/to/dir' --filter='regex' +Use these commands to update copyright information in @samp{.sh} files +under @samp{path/to/dir} directory. +@end table + +When you provide @option{--filter='regex'} argument, the list of files +to process is reduced as specified in @samp{regex} regular expression. +Inside @file{centos-art.sh} script, the @samp{regex} regular +expression is used in combination with @command{find} command to look +for files matching the regular expression path pattern. + +@quotation +@strong{Warning} In order for @samp{regex} regular expression to match +a file, the @samp{regex} regular expresion must match the whole file +path not just the file name. +@end quotation + +For example, if you want to match all @file{render.conf.sh} files +inside @file{path/to/dir}, use the @code{.+/render.conf} regular +expression. Later, @file{centos-art.sh} script uses this value inside +@code{^$REGEX\.sh$} expression in order to build the final regular +expression (i.e., @code{^.+/render.conf\.sh$}) that is evaluated +against available file paths inside the list of files to process. + +Exceptionally, when you provide @option{--filter='regex'} in the way +that @samp{regex}, appended to @samp{path/to/dir/} (i.e. +@samp{path/to/dir/regex}), matches a regular file; the +@file{centos-art.sh} script uses the file matching as only file in the +list of files to process. + +@subsection See also + +@menu +* trunk Scripts Bash:: +@comment --- Removed(* trunk Scripts Bash Functions::) --- +@end menu diff --git a/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Svg.texi b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Svg.texi new file mode 100644 index 0000000..341745d --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Svg.texi @@ -0,0 +1,192 @@ +@subsection Goals + +This section exists to organize files related to @code{svg} +functionality of @file{centos-art.sh} script. + +@subsection Description + +The @code{svg} functionality of @file{centos-art.sh} script helps you +to maintain scalable vector graphics (SVG) inside repository. For +example, suppose you've been working in CentOS default design models +under @file{trunk/Identity/Themes/Models/}, and you want to set common +metadata to all of them, and later remove all unused SVG defintions +from @samp{*.svg} files. Doing so file by file may be a tedious task, +so the @file{centos-art.sh} script provides the @code{svg} +functionality to aid you maintain such actions. + +@cindex Metadata maintainance +@subsubsection Metadata maintainance + +The metadata used is defined by Inkscape 0.46 using the SVG standard +markup. The @file{centos-art.sh} script replaces everything +in-between @code{} tags with a +predefined metadata template we've set for this purpose. + +The metadata template was created using the metadata information of a +file which, using Inkscape 0.46, all metadata fields were set. This +created a complete markup representation of how SVG metadata would +look like. Later, we replaced every single static value with a +translation marker in the form @samp{=SOMETEXT=}, where +@code{SOMETEXT} is the name of its main opening tag. Later, we +transform the metadata template into a sed replacement set of commads +escaping new lines at the end of each line. + +With metadata template in place, the @file{centos-art.sh} script uses +it to create a metadata template instance for the file being processed +currently. The metadata template instance contains the metadata +portion of sed replacement commands with translation markers already +traduced. In this action, instance creation, is where we take +advantage of automation and generate metadata values like title, date, +keywords, source, identifier, and relation dynamically, based on the +file path @file{centos-art.sh} script is currently creating metadata +information for. + +With metadata template instance in place, the @file{centos-art.sh} +script uses it to replace real values inside all @samp{.svg} files +under the current location you're running the @file{centos-art.sh} +script on. Default behaviour is to ask user to enter each metadatum +required, one by one. If user leaves metadatum empty, by pressing +@key{RET} key, @file{centos-art.sh} uses its default value. + +The @file{centos-art.sh} script modifies the following metadata: + +@table @samp +@item Title +Name by which this document is formally known. If no value is set +here, @file{centos-art.sh} script uses the file name as title. + +@item Date +Date associated with the creation of this document (YYYY-MM-DD). If no +value is set here, @file{centos-art.sh} script uses the current date +information as in @command{date +%Y-%m-%d}. + +@item Creator +Name of entity primarily responsible for making the content of this +document. If no value is set here, @file{centos-art.sh} script uses +the string @samp{The CentOS Project}. + +@item Rights +Name of entity with rights to the intellectual Property of this +document. If no value is set here, @file{centos-art.sh} script uses +the string @samp{The CentOS Project}. + +@item Publisher +Name of entity responsible for making this document available. If no +value is set here, @file{centos-art.sh} script uses the string +@samp{The CentOS Project}. + +@item Identifier +Unique URI to reference this document. If no value is set here, +@file{centos-art.sh} script uses the current file path to build the +related url that points to current file location inside repository +central server. + +@item Source +Unique URI to reference the source of this document. If no value is +set here, @file{centos-art.sh} script uses current file path to build +the related url that points to current file location inside repository +central server. + +@item Relation +Unique URI to a related document. If no value is set here, +@file{centos-art.sh} script uses current file path to build the +related url that points to current file location inside repository +central server. + +@item Language +Two-letter language tag with optional subtags for the language of this +document. (e.g. @samp{en-GB}). If no value is set here, +@file{centos-art.sh} script uses the current locale information as in +@code{cli_getCurrentLocale} function. + +@item Keywords +The topic of this document as comma-separated key words, prhases, or +classifications. If no value is set here, @file{centos-art.sh} script +uses file path to build + +@item Coverage +Extent or scope of this document. If no value is set here, +@file{centos-art.sh} script uses the string @samp{The CentOS Project}. + +@item Description +Description about the document. If no value is set here, +@file{centos-art.sh} script uses uses empty value as default. + +@item Contributors +People that contributes in the creation/maintainance of the document. +If no value is set here, @file{centos-art.sh} script uses uses empty +value as default. +@end table + +The @samp{License} metadatum is not set as a choise, by now. It is +fixed @url{http://creativecommons.org/licenses/by-sa/3.0/, Creative +Common Attribution Share-Alike 3.0 License}. This is done in order to +grant license consistency among all SVG files we manage inside CentOS +Artwork Repository. + +@cindex Unused definitions +@subsubsection Unused definitions + +Many of the no-longer-used gradients, patterns, and markers (more +precisely, those which you edited manually) remain in the +corresponding palettes and can be reused for new objects. However if +you want to optimize your document, use the @samp{Vacuum Defs} command +in @samp{File} menu. It will remove any gradients, patterns, or +markers which are not used by anything in the document, making the +file smaller. + +If you have one or two couple of files, removing unused definitions +using the graphical interface may be enough to you. In contrast, if +you have dozens or even houndreds of scalable vector graphics files to +maintain it is not a fun task to use the graphical interface to remove +unused definitions editing those files one by one. + +To remove unused definitions from several scalable vector graphics +files, the @file{centos-art.sh} script uses Inkscape command-line +interface, specifically with the @option{--vaccum-defs} option. + +@subsection Usage + +@table @command +@item centos-art svg --update-metadata='path/to/dir' +@item centos-art svg --update-metadata='path/to/dir' --filter='regex' +Use these commands to update metadata information to @samp{.svg} files +under @samp{path/to/dir} directory. + +@item centos-art svg --vacuum-defs='path/to/dir' +@item centos-art svg --vacuum-defs='path/to/dir' --filter='regex' +Use these commands to remove unused definitions inside @samp{.svg} +files under @samp{path/to/dir} directory. +@end table + +When you provide @option{--filter='regex'} argument, the list of files +to process is reduced as specified in @samp{regex} regular expression. +Inside @file{centos-art.sh} script, the @samp{regex} regular +expression is used in combination with @command{find} command to look +for files matching the regular expression path pattern. + +@quotation +@strong{Warning} In order for @samp{regex} regular expression to match +a file, the @samp{regex} regular expresion must match the whole file +path not just the file name. +@end quotation + +For example, if you want to match all @file{summary.svg} files inside +@file{path/to/dir}, use the @code{.+/summary} regular expression. +Later, @file{centos-art.sh} script uses this value inside +@code{^$REGEX\.svg$} expression in order to build the final regular +expression (i.e., @code{^.+/summary\.svg$}) that is evaluated against +available file paths inside the list of files to process. + +Exceptionally, when you provide @option{--filter='regex'} in the way +that @samp{regex}, appended to @samp{path/to/dir/} (i.e. +@samp{path/to/dir/regex}), matches a regular file; the +@file{centos-art.sh} script uses the file matching as only file in the +list of files to process. + +@subsection See also + +@menu +* trunk Scripts Bash:: +@comment --- Removed(* trunk Scripts Bash Functions::) --- +@end menu diff --git a/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Verify.texi b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Verify.texi new file mode 100644 index 0000000..ff98b51 --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Bash/Cli/Functions/Verify.texi @@ -0,0 +1,245 @@ +@subsection Goals + +This section exists to organize files related to @file{centos-art.sh} +script @samp{verify} functionality. The @samp{verify} +functionality of @file{centos-art.sh} script helps you to verify the +workstation configuration you are planning to use as host for your +working copy of CentOS Artwork Repository. + +@subsection Description + +The first time you download CentOS Artwork Repository you need to +configure your workstation in order to use @file{centos-art.sh} +script. These preliminar configurations are based mainly on auxiliar +RPM packages installation, symbolic links creations, and environment +variables definitions. The @samp{verify} functionality of +@file{centos-art.sh} script guides you through this preliminar +configuration process. + +If this is the first time you run @file{centos-art.sh} script, the +appropriate way to use its @samp{verify} functionality is not using +the @file{centos-art.sh} script directly, but the absolute path to +@command{centos-art.sh} script instead (i.e., +@file{~/artwork/trunk/Scripts/Bash/centos-art.sh}). This is necessary +because @file{centos-art} symbolic link, under @file{~/bin/} +directory, has not been created yet. + +@subsubsection Packages + +Installation of auxiliar RPM packages provides the software required +to manipulate files inside the repository (e.g., image files, +documentation files, translation files, script files, etc.). Most of +RPM packages @command{centos-art.sh} script uses are shipped with +CentOS distribution, and can be installed from CentOS base repository. +The only exception is @samp{inkscape}, the package we use to +manipulate SVG files. The @samp{inkscape} package is not inside +CentOS distribution so it needs to be installed from third party +repositories. + +@quotation +@strong{Note} Configuration of third party repositories inside CentOS +distribution is described in CentOS wiki, specifically in the +following URL: +@url{http://wiki.centos.org/AdditionalResources/Repositories} +@end quotation + +Before installing packages, the @file{centos-art.sh} script uses +@command{sudo} to request root privileges to execute @command{yum} +installation functionality. If your user isn't defined as a +privileged user---at least to run @command{yum} commands--- inside +@file{/etc/sudoers} configuration file, you will not be able to +perform package installation tasks as set in @file{centos-art.sh} +script @samp{verify} functionality. + +Setting sudo privileges to users is an administrative task you have to +do by yourself. If you don't have experience with @command{sudo} +command, please read its man page running the command: @command{man +sudo}. This reading will be very useful, and with some practice, you +will be able to configure your users to have @command{sudo} +privileges. + +@subsubsection Links + +Creation of symbolic links helps us to alternate between different +implementations of @file{centos-art.sh} script-line (e.g., +@file{centos-art.sh}, for Bash implementation; @file{centos-art.py}, +for Python implementation; @file{centos-art.pl}, for Perl +implementation; and so on for other implementations). The +@file{centos-art.sh} script-line definition takes place inside your +personal binary (@file{~/bin/}) directory in order to make the script +implementation ---the one that @file{centos-art} links to--- available +to @var{PATH} environment variable. + +Creation of symbolic links helps us to reuse components from repository +working copy. For example, color information files maintained inside +your working copy must never be duplicated inside program-specific +configuration directories that uses them in your workstation (e.g., +Gimp, Inkscape, etc.). Instead, a symbolic link must be created for +each one of them, from program-specific configuration directories to +files in the working copy. In this configuration, when someone +commits changes to color information files up to central repository, +they---the changes committed--- will be immediatly available to your +programs the next time you update your working copy ---the place +inside your workstation those color information files are stored---. + +Creation of symbolic links helps us to make @file{centos-art.sh} +script functionalities available outside @file{trunk/} repository +directory structure, but at its same level in repository tree. This is +useful if you need to use the ``render'' functionality of +@command{centos-art.sh} under @file{branches/} repository directory +structure as you usually do inside @file{trunk/} repository directory +structure. As consequence of this configuration, automation scripts +cannot be branched under @file{branches/Scripts} directory structure. + +@subsubsection Environment variables + +Definition of environemnt variables helps us to set default values to +our user session life. The user session environment variable defintion +takes place in the user's @file{~/.bash_profile} file. The +@samp{verify} functionality of @file{centos-art.sh} script doesn't +modify your @file{~/.bash_profile} file. + +The @samp{verify} functionality of @file{centos-art.sh} script +evaluates the following environment variables: + +@table @env +@item EDITOR +Default text editor. + +The @file{centos-art.sh} script uses default text @env{EDITOR} to edit +pre-commit subversion messages, translation files, configuration +files, script files, and similar text-based files. + +If @env{EDITOR} environment variable is not set, @file{centos-art.sh} +script uses @file{/usr/bin/vim} as default text editor. Otherwise, the +following values are recognized by @file{centos-art.sh} script: + +@itemize +@item @file{/usr/bin/vim} +@item @file{/usr/bin/emacs} +@item @file{/usr/bin/nano} +@end itemize + +If no one of these values is set in @env{EDITOR} environment variable, +@file{centos-art.sh} uses @file{/usr/bin/vim} text editor by default. + +@item TEXTDOMAIN + +Default domain used to retrieve translated messages. This variable is +set in @file{initFunctions.sh} and shouldn't be changed. + +@item TEXTDOMAINDIR + +Default directory used to retrieve translated messages. This variable +is set in @file{initFunctions.sh} and shouldn't be changed. + +@item LANG + +Default locale information. + +This variable is initially set in the configuration process of CentOS +distribution installer (i.e., Anaconda), specifically in the +@samp{Language} step; or once installed using the +@command{system-config-language} tool. + +The @file{centos-art.sh} script uses the @var{LANG} environment +variable to know in which language the script messages are printed +out. + +@item TZ + +Default time zone representation. + +This variable is initially set in the configuration process of CentOS +distribution installer (i.e., Anaconda), specifically in the +@samp{Date and time} step; or once installed using the +@command{system-config-date} tool. + +The @file{centos-art.sh} script doesn't use the @var{TZ} environment +variable information at all. Instead, this variable is used by the +system shell to show the time information according to your phisical +location on planet Earth. + +Inside your computer, the time information is firstly set in the BIOS +clock (which may need correction), and later in the configuration +process of CentOS distribution installer (or later, by any of the +related configuration tools inside CentOS distribution). Generally, +setting time information is a straight-forward task and configuration +tools available do cover most relevant location. However, if you need +a time precision not provided by the configuration tools available +inside CentOS distribution then, using @var{TZ} variable may be +necessary. + +@quotation +@strong{Convenction} In order to keep changes syncronized between +central repository and its working copies: configure both repository +server and workstations (i.e., the place where each working copy is +set on) to use Coordinated Universal Time (UTC) as base time +representation. Later, correct the time information for your specific +location using time zone correction. +@end quotation + +The format of @var{TZ} environment variable is described in +@file{tzset(3)} manual page. + +@end table + +@subsection Usage + +@table @command + +@item centos-art verify --packages + +Verify required packages your workstation needs in order to run the +@file{centos-art.sh} script correctly. If there are missing packages, +the @file{centos-art.sh} script asks you to confirm their +installation. When installing packages, the @file{centos-art.sh} +script uses the @command{yum} application in order to achieve the +task. + +In case all packages required by @file{centos-art.sh} script are +already installed in your workstation, the message @samp{The required +packages are already installed.} is output for you to know. + +@item centos-art verify --links + +Verify required links your workstation needs in order to run the +centos-art command correctly. If any required link is missing, the +@command{centos-art.sh} script asks you to confirm their installation. +To install required links, the @command{centos-art.sh} script uses the +@command{ln} command. + +In case all links required by @file{centos-art.sh} script are already +created in your workstation, the message @samp{The required links are +already installed.} is output for you to know. + +In case a regular file exists with the same name of a required link, +the @file{centos-art.sh} script outputs the @samp{Already exists as +regular file.} message when listing required links that will be +installed. Of course, as there is already a regular file where must be +a link, no link is created. In such cases the @file{centos-art.sh} +script will fall into a continue installation request for that missing +link. To end this continue request you can answer @samp{No}, or +remove the existent regular file to let @file{centos-art.sh} script +install the link on its place. + +@item centos-art verify --environment +@itemx centos-art verify --environment --filter='regex' + +Output a brief description of environment variables used by +@file{centos-art.sh} script. + +If @samp{--filter} option is provided, output is reduced as defined in +the @samp{regex} regular expression value. If @samp{--filter} option +is specified but @samp{regex} value is not, the @file{centos-art.sh} +script outputs information as if @samp{--filter} option had not been +provided at all. + +@end table + +@subsection See also + +@menu +* trunk Scripts Bash:: +@comment --- Removed(* trunk Scripts Bash Functions::) --- +@end menu diff --git a/Manuals/Repository/trunk/Scripts/Python.texi b/Manuals/Repository/trunk/Scripts/Python.texi new file mode 100644 index 0000000..fb39647 --- /dev/null +++ b/Manuals/Repository/trunk/Scripts/Python.texi @@ -0,0 +1,22 @@ +@subsection Goals + +@itemize +@item ... +@end itemize + +@subsection Description + +@itemize +@item ... +@end itemize + +@subsection Usage + +@itemize +@item ... +@end itemize + +@subsection See also + +@menu +@end menu diff --git a/Manuals/Repository/trunk/chapter-intro.texi b/Manuals/Repository/trunk/chapter-intro.texi new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/Manuals/Repository/trunk/chapter-intro.texi diff --git a/Manuals/Repository/trunk/chapter-menu.texi b/Manuals/Repository/trunk/chapter-menu.texi new file mode 100644 index 0000000..1dace8c --- /dev/null +++ b/Manuals/Repository/trunk/chapter-menu.texi @@ -0,0 +1,62 @@ +@menu +* trunk Identity:: +* trunk Identity Brands:: +* trunk Identity Fonts:: +* trunk Identity Icons:: +* trunk Identity Isolinux:: +* trunk Identity Models:: +* trunk Identity Models Css:: +* trunk Identity Models Html:: +* trunk Identity Models Img Promo Web:: +* trunk Identity Models Tpl:: +* trunk Identity Models Tpl Promo Web:: +* trunk Identity Models Xcf:: +* trunk Identity Release:: +* trunk Identity Themes:: +* trunk Identity Themes Models:: +* trunk Identity Themes Models Alternative:: +* trunk Identity Themes Models Default:: +* trunk Identity Themes Models Default Distro:: +* trunk Identity Themes Models Default Distro Anaconda:: +* trunk Identity Themes Models Default Promo:: +* trunk Identity Themes Models Default Web:: +* trunk Identity Themes Motifs:: +* trunk Identity Themes Motifs Flame:: +* trunk Identity Themes Motifs Modern:: +* trunk Identity Themes Motifs Modern Backgrounds:: +* trunk Identity Themes Motifs Modern Backgrounds Img:: +* trunk Identity Themes Motifs Modern Backgrounds Tpl:: +* trunk Identity Themes Motifs Modern Backgrounds Xcf:: +* trunk Identity Themes Motifs Modern Distro Anaconda Progress:: +* trunk Identity Themes Motifs Modern Palettes:: +* trunk Identity Themes Motifs TreeFlower:: +* trunk Identity Themes Motifs TreeFlower Backgrounds:: +* trunk Identity Widgets:: +* trunk Locales:: +* trunk Locales Identity:: +* trunk Locales Identity Brands:: +* trunk Locales Identity Brands Tpl:: +* trunk Locales Identity Fonts:: +* trunk Locales Identity Models:: +* trunk Locales Identity Release:: +* trunk Locales Identity Themes:: +* trunk Locales Identity Themes Backgrounds:: +* trunk Locales Identity Themes Distro Anaconda Progress:: +* trunk Locales Identity Widgets:: +* trunk Manuals:: +* trunk Scripts:: +* trunk Scripts Bash:: +* trunk Scripts Bash Cli:: +* trunk Scripts Bash Cli Functions:: +* trunk Scripts Bash Cli Functions Help:: +* trunk Scripts Bash Cli Functions Html:: +* trunk Scripts Bash Cli Functions Locale:: +* trunk Scripts Bash Cli Functions Manual:: +* trunk Scripts Bash Cli Functions Path:: +* trunk Scripts Bash Cli Functions Render:: +* trunk Scripts Bash Cli Functions Render Config:: +* trunk Scripts Bash Cli Functions Shell:: +* trunk Scripts Bash Cli Functions Svg:: +* trunk Scripts Bash Cli Functions Verify:: +* trunk Scripts Python:: +@end menu diff --git a/Manuals/Repository/trunk/chapter-nodes.texi b/Manuals/Repository/trunk/chapter-nodes.texi new file mode 100644 index 0000000..2ab21f1 --- /dev/null +++ b/Manuals/Repository/trunk/chapter-nodes.texi @@ -0,0 +1,300 @@ +@node trunk Identity +@section trunk/Identity +@cindex trunk Identity +@include trunk/Identity.texi + +@node trunk Identity Brands +@section trunk/Identity/Brands +@cindex trunk Identity Brands +@include trunk/Identity/Brands.texi + +@node trunk Identity Fonts +@section trunk/Identity/Fonts +@cindex trunk Identity Fonts +@include trunk/Identity/Fonts.texi + +@node trunk Identity Icons +@section trunk/Identity/Icons +@cindex trunk Identity Icons +@include trunk/Identity/Icons.texi + +@node trunk Identity Isolinux +@section trunk/Identity/Isolinux +@cindex trunk Identity Isolinux +@include trunk/Identity/Isolinux.texi + +@node trunk Identity Models +@section trunk/Identity/Models +@cindex trunk Identity Models +@include trunk/Identity/Models.texi + +@node trunk Identity Models Css +@section trunk/Identity/Models/Css +@cindex trunk Identity Models Css +@include trunk/Identity/Models/Css.texi + +@node trunk Identity Models Html +@section trunk/Identity/Models/Html +@cindex trunk Identity Models Html +@include trunk/Identity/Models/Html.texi + +@node trunk Identity Models Img Promo Web +@section trunk/Identity/Models/Img/Promo/Web +@cindex trunk Identity Models Img Promo Web +@include trunk/Identity/Models/Img/Promo/Web.texi + +@node trunk Identity Models Tpl +@section trunk/Identity/Models/Tpl +@cindex trunk Identity Models Tpl +@include trunk/Identity/Models/Tpl.texi + +@node trunk Identity Models Tpl Promo Web +@section trunk/Identity/Models/Tpl/Promo/Web +@cindex trunk Identity Models Tpl Promo Web +@include trunk/Identity/Models/Tpl/Promo/Web.texi + +@node trunk Identity Models Xcf +@section trunk/Identity/Models/Xcf +@cindex trunk Identity Models Xcf +@include trunk/Identity/Models/Xcf.texi + +@node trunk Identity Release +@section trunk/Identity/Release +@cindex trunk Identity Release +@include trunk/Identity/Release.texi + +@node trunk Identity Themes +@section trunk/Identity/Themes +@cindex trunk Identity Themes +@include trunk/Identity/Themes.texi + +@node trunk Identity Themes Models +@section trunk/Identity/Themes/Models +@cindex trunk Identity Themes Models +@include trunk/Identity/Themes/Models.texi + +@node trunk Identity Themes Models Alternative +@section trunk/Identity/Themes/Models/Alternative +@cindex trunk Identity Themes Models Alternative +@include trunk/Identity/Themes/Models/Alternative.texi + +@node trunk Identity Themes Models Default +@section trunk/Identity/Themes/Models/Default +@cindex trunk Identity Themes Models Default +@include trunk/Identity/Themes/Models/Default.texi + +@node trunk Identity Themes Models Default Distro +@section trunk/Identity/Themes/Models/Default/Distro +@cindex trunk Identity Themes Models Default Distro +@include trunk/Identity/Themes/Models/Default/Distro.texi + +@node trunk Identity Themes Models Default Distro Anaconda +@section trunk/Identity/Themes/Models/Default/Distro/Anaconda +@cindex trunk Identity Themes Models Default Distro Anaconda +@include trunk/Identity/Themes/Models/Default/Distro/Anaconda.texi + +@node trunk Identity Themes Models Default Promo +@section trunk/Identity/Themes/Models/Default/Promo +@cindex trunk Identity Themes Models Default Promo +@include trunk/Identity/Themes/Models/Default/Promo.texi + +@node trunk Identity Themes Models Default Web +@section trunk/Identity/Themes/Models/Default/Web +@cindex trunk Identity Themes Models Default Web +@include trunk/Identity/Themes/Models/Default/Web.texi + +@node trunk Identity Themes Motifs +@section trunk/Identity/Themes/Motifs +@cindex trunk Identity Themes Motifs +@include trunk/Identity/Themes/Motifs.texi + +@node trunk Identity Themes Motifs Flame +@section trunk/Identity/Themes/Motifs/Flame +@cindex trunk Identity Themes Motifs Flame +@include trunk/Identity/Themes/Motifs/Flame.texi + +@node trunk Identity Themes Motifs Modern +@section trunk/Identity/Themes/Motifs/Modern +@cindex trunk Identity Themes Motifs Modern +@include trunk/Identity/Themes/Motifs/Modern.texi + +@node trunk Identity Themes Motifs Modern Backgrounds +@section trunk/Identity/Themes/Motifs/Modern/Backgrounds +@cindex trunk Identity Themes Motifs Modern Backgrounds +@include trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi + +@node trunk Identity Themes Motifs Modern Backgrounds Img +@section trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img +@cindex trunk Identity Themes Motifs Modern Backgrounds Img +@include trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img.texi + +@node trunk Identity Themes Motifs Modern Backgrounds Tpl +@section trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl +@cindex trunk Identity Themes Motifs Modern Backgrounds Tpl +@include trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl.texi + +@node trunk Identity Themes Motifs Modern Backgrounds Xcf +@section trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf +@cindex trunk Identity Themes Motifs Modern Backgrounds Xcf +@include trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf.texi + +@node trunk Identity Themes Motifs Modern Distro Anaconda Progress +@section trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress +@cindex trunk Identity Themes Motifs Modern Distro Anaconda Progress +@include trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi + +@node trunk Identity Themes Motifs Modern Palettes +@section trunk/Identity/Themes/Motifs/Modern/Palettes +@cindex trunk Identity Themes Motifs Modern Palettes +@include trunk/Identity/Themes/Motifs/Modern/Palettes.texi + +@node trunk Identity Themes Motifs TreeFlower +@section trunk/Identity/Themes/Motifs/TreeFlower +@cindex trunk Identity Themes Motifs TreeFlower +@include trunk/Identity/Themes/Motifs/TreeFlower.texi + +@node trunk Identity Themes Motifs TreeFlower Backgrounds +@section trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds +@cindex trunk Identity Themes Motifs TreeFlower Backgrounds +@include trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds.texi + +@node trunk Identity Widgets +@section trunk/Identity/Widgets +@cindex trunk Identity Widgets +@include trunk/Identity/Widgets.texi + +@node trunk Locales +@section trunk/Locales +@cindex trunk Locales +@include trunk/Locales.texi + +@node trunk Locales Identity +@section trunk/Locales/Identity +@cindex trunk Locales Identity +@include trunk/Locales/Identity.texi + +@node trunk Locales Identity Brands +@section trunk/Locales/Identity/Brands +@cindex trunk Locales Identity Brands +@include trunk/Locales/Identity/Brands.texi + +@node trunk Locales Identity Brands Tpl +@section trunk/Locales/Identity/Brands/Tpl +@cindex trunk Locales Identity Brands Tpl +@include trunk/Locales/Identity/Brands/Tpl.texi + +@node trunk Locales Identity Fonts +@section trunk/Locales/Identity/Fonts +@cindex trunk Locales Identity Fonts +@include trunk/Locales/Identity/Fonts.texi + +@node trunk Locales Identity Models +@section trunk/Locales/Identity/Models +@cindex trunk Locales Identity Models +@include trunk/Locales/Identity/Models.texi + +@node trunk Locales Identity Release +@section trunk/Locales/Identity/Release +@cindex trunk Locales Identity Release +@include trunk/Locales/Identity/Release.texi + +@node trunk Locales Identity Themes +@section trunk/Locales/Identity/Themes +@cindex trunk Locales Identity Themes +@include trunk/Locales/Identity/Themes.texi + +@node trunk Locales Identity Themes Backgrounds +@section trunk/Locales/Identity/Themes/Backgrounds +@cindex trunk Locales Identity Themes Backgrounds +@include trunk/Locales/Identity/Themes/Backgrounds.texi + +@node trunk Locales Identity Themes Distro Anaconda Progress +@section trunk/Locales/Identity/Themes/Distro/Anaconda/Progress +@cindex trunk Locales Identity Themes Distro Anaconda Progress +@include trunk/Locales/Identity/Themes/Distro/Anaconda/Progress.texi + +@node trunk Locales Identity Widgets +@section trunk/Locales/Identity/Widgets +@cindex trunk Locales Identity Widgets +@include trunk/Locales/Identity/Widgets.texi + +@node trunk Manuals +@section trunk/Manuals +@cindex trunk Manuals +@include trunk/Manuals.texi + +@node trunk Scripts +@section trunk/Scripts +@cindex trunk Scripts +@include trunk/Scripts.texi + +@node trunk Scripts Bash +@section trunk/Scripts/Bash +@cindex trunk Scripts Bash +@include trunk/Scripts/Bash.texi + +@node trunk Scripts Bash Cli +@section trunk/Scripts/Bash/Cli +@cindex trunk Scripts Bash Cli +@include trunk/Scripts/Bash/Cli.texi + +@node trunk Scripts Bash Cli Functions +@section trunk/Scripts/Bash/Cli/Functions +@cindex trunk Scripts Bash Cli Functions +@include trunk/Scripts/Bash/Cli/Functions.texi + +@node trunk Scripts Bash Cli Functions Help +@section trunk/Scripts/Bash/Cli/Functions/Help +@cindex trunk Scripts Bash Cli Functions Help +@include trunk/Scripts/Bash/Cli/Functions/Help.texi + +@node trunk Scripts Bash Cli Functions Html +@section trunk/Scripts/Bash/Cli/Functions/Html +@cindex trunk Scripts Bash Cli Functions Html +@include trunk/Scripts/Bash/Cli/Functions/Html.texi + +@node trunk Scripts Bash Cli Functions Locale +@section trunk/Scripts/Bash/Cli/Functions/Locale +@cindex trunk Scripts Bash Cli Functions Locale +@include trunk/Scripts/Bash/Cli/Functions/Locale.texi + +@node trunk Scripts Bash Cli Functions Manual +@section trunk/Scripts/Bash/Cli/Functions/Manual +@cindex trunk Scripts Bash Cli Functions Manual +@include trunk/Scripts/Bash/Cli/Functions/Manual.texi + +@node trunk Scripts Bash Cli Functions Path +@section trunk/Scripts/Bash/Cli/Functions/Path +@cindex trunk Scripts Bash Cli Functions Path +@include trunk/Scripts/Bash/Cli/Functions/Path.texi + +@node trunk Scripts Bash Cli Functions Render +@section trunk/Scripts/Bash/Cli/Functions/Render +@cindex trunk Scripts Bash Cli Functions Render +@include trunk/Scripts/Bash/Cli/Functions/Render.texi + +@node trunk Scripts Bash Cli Functions Render Config +@section trunk/Scripts/Bash/Cli/Functions/Render/Config +@cindex trunk Scripts Bash Cli Functions Render Config +@include trunk/Scripts/Bash/Cli/Functions/Render/Config.texi + +@node trunk Scripts Bash Cli Functions Shell +@section trunk/Scripts/Bash/Cli/Functions/Shell +@cindex trunk Scripts Bash Cli Functions Shell +@include trunk/Scripts/Bash/Cli/Functions/Shell.texi + +@node trunk Scripts Bash Cli Functions Svg +@section trunk/Scripts/Bash/Cli/Functions/Svg +@cindex trunk Scripts Bash Cli Functions Svg +@include trunk/Scripts/Bash/Cli/Functions/Svg.texi + +@node trunk Scripts Bash Cli Functions Verify +@section trunk/Scripts/Bash/Cli/Functions/Verify +@cindex trunk Scripts Bash Cli Functions Verify +@include trunk/Scripts/Bash/Cli/Functions/Verify.texi + +@node trunk Scripts Python +@section trunk/Scripts/Python +@cindex trunk Scripts Python +@include trunk/Scripts/Python.texi + diff --git a/Manuals/Repository/trunk/chapter.texi b/Manuals/Repository/trunk/chapter.texi new file mode 100644 index 0000000..73ba088 --- /dev/null +++ b/Manuals/Repository/trunk/chapter.texi @@ -0,0 +1,6 @@ +@node trunk +@chapter trunk +@cindex trunk +@include trunk/chapter-intro.texi +@include trunk/chapter-menu.texi +@include trunk/chapter-nodes.texi